Issue status: Fixed
Issue details: Bricked device with Bootloader locked.
Issue solution : This thread
Thanks to: devcon69
Special Thanks for information: takagen, lindvall, cebu, darkhelmetnl
File sources: https://forum.xda-developers.com/redmi-note-5-pro/how-to/fix-arb-bricked-device-qfil-t3841780
Info sources: https://forum.xda-developers.com/showpost.php?p=79083641&postcount=38
Been flashing roms, wanted to try them out, and before you ask, yes I wipe cache, system, and data before I do a wipe...
But somewhere down the line, rotation stops working, I don't know why, but it just did and wouldnt work in any rom I tried
Eventually Twrp stopped letting me flash new roms giving me excuses like zip verification failure.
Then it stopped letting me flash other zips like verity disable and gapps.
Being basically locked to Havoc wasn't really an option for me so I decided to go the nuclear route and reflash stock rom+recovery which bricked my device but not before wiping my recovery and locking that pesky bootloader. "SYSTEM DESTROYED"
So here I am with a locked bootloader, only access to Fastboot, and what I believe is EDL as it shows up as Qualcomm driver in device manager if I do it right.
I tried using the same flash tool that bricked my device both in Fastboot and EDL, in Fastboot it tells me my device is locked
In EDL it tells me the device is locked and error getting "hello packet"
And when I try to use the unlock tool, it tells me my current account is not bound to the device, even though it used to be. And I don't have a system to go in to make it so again.
So does anyone know how to flash anything around the locked bootloader?
Hi
I do not have much knowledge of xiaomi, just my mi pad 4 ... But from what I read, you must never relock a bootlader already unlock with fastboot ... It almost systematically causes a hard brick
Try the steps did here ?
https://forum.xda-developers.com/mi-pad-4/help/destroyed-lock-bootloader-t3840762/page5
Zayatoshi said:
Hi
I do not have much knowledge of xiaomi, just my mi pad 4 ... But from what I read, you must never relock a bootlader already unlock with fastboot ... It almost systematically causes a hard brick
Click to expand...
Click to collapse
Doesn't really mention that in the instruction manual. And the flashing tool locks the bootloader anyway and the guides don't mention the bricking issue + anyone that suggests using the flash tool tend to leave that part out, it's only until after I done it and am googling how to undo are people showing up with comments saying "yeah you shouldn't have done that"
Like where were the warnings before?!
takagen said:
Try the steps did here ?
https://forum.xda-developers.com/mi-pad-4/help/destroyed-lock-bootloader-t3840762/page5
Click to expand...
Click to collapse
Hopefully ill have time to try that tomorrow but thank you so much for a suggestion.
I have put my device in EDL I think, kind of hard to tell with the screen off, but when I attempted the flash, the miflash tool told me sry can't do it cause of a lock.
I'll investigate later if it's anything different than what I tried before.
I definitely want to get it back to working order because I have yet actually got a chance to enjoy using it. The first thing I did was try to flash a rom and it's been downhill of trying to troubleshoot onething after another.
I didn't backup via twrp because I forgot, and I didn't anticipate just how locked down and a pain in the ass Xiaomi devices could be, and in the past on other devices, recovering from a bricked state is usually a more simple process.
Thank god my pocophone has a full miui backup via twrp
My device was bricked and the people credited helped me recover it.
Had to take off the back to put the device into EDL mode.
Used specifically the software /files and instructions provided by devcon69, the patches elf file was key
And the information provided by Lind all helped me more than I thought, particularly the part where he/she said "I waited too long"
So as soon as I opened up miflash tool, I clicked flash as fast as I could, maybe the tool goes through some sort of background security check and clicking flash starts before it finishes (I doubt it) , I don't know...
takagen said:
Try the steps did here ?
https://forum.xda-developers.com/mi-pad-4/help/destroyed-lock-bootloader-t3840762/page5
Click to expand...
Click to collapse
You helped me out a ton! Tysm!
Congrats
Related
Hello everyone,
tl;dr version
What's the best way to install a custom rom on the Redmi Note 3 out of the box with a locked bootloader. What is the best rom to use for maximum functionality.
I have been following these forums for a while, but haven't got around to creating an account and posting. I'm new to flashing roms, and my experience goes as far as following guides to flash a Samsung S4, and a Samsung S2. The Samsung phones were really easy to flash, and I just followed guides in a robotic way without ever actually learning anything. For the record, CM12 on the Samsung S2, which I'm using because I smashed my S4, is absolutely unbelievable in regards to the increase of performance.
One of my work friends was telling me that he has a mate who bought a Chinese phone really cheap and flashed it. Getting excited, knowing exactly where I need to look to flash a phone, I impulsively researched these phones and bought a Redmi Note 3 for $173 AUD. It's on the way in the mail. Having looked at the hardware specs, this price is absolutely ridiculous. I was more swayed to buy the Redmi Note 3, because multiple sites reported that the second sim slot can hold a micro SD card. The only downside I can see to this phone is the bloatware and stock rom that it comes with, and the reason for this post is to discuss the best way in which to flash a new rom. If you have managed to read this far, thanks for reading my life story!
Having limited experience in the phone flashing world, from researching it looks like the flashing process is something like:
Unlock the bootloader
Flash a recovery program
Use the recovery to flash rom/app
My understanding of the bootloader and why it needs to be unlocked is limited. I've done some research around it, and this is what I have found. The bootloader is the first thing that runs when the phone starts up, loads the kernel and the rom, and verifies that you have a legit recovery program. It needs to be unlocked so you can put a custom recovery on to your phone. Once you have that sorted, flashing roms from the recovery is a pretty straight forward process. If I'm wrong, please correct me, because this is what I have understood from looking around and I'm not confident about my understanding.
Unlocking the Bootloader On The Redmi Note 3
Having read on multiple sites, this looks like the biggest constraint when trying to flash a custom rom on the Redmi Note 3. This is because Xiaomi have locked the bootloader for this device, when most other phones do not have this problem. Most flashing guides for the Redmi Note 3 assume that the boodloader is unlocked or list it as a pre-requisite, so I'm unsure what path to take here. From research, it looks like there are 3 possible ways to move forward from here:
Official Bootloader Unlock
Unofficial Bootloader Unlock
Bypassing The Bootloader Unlock
Because my account is new, the following links aren't hyperlinked and in a good format due to permissions. Sorry! It'd be sweet if a mod could edit it.
1. Official Bootloader Unlock
This seems like the most legit way to unlock the bootloader. Apparently you just go to: endotmiuidotcom/unlock/ and apply for an unlock by using google translate and creating an account. People have reported response times taking over a month, not getting a successful application, or the unlocking process getting stuck at 50%. To me this doesn't sound appealing and I'm not too keen on waiting a month to find I'm unsuccessful in applying.
2. Unofficial Bootloader Unlock
This process is found here: endotmiuidotcom/thread-253680-1-1.html and looks to be a bit tedious. Apparently there is a high chance for a brick using this method, and some custom recoveries don't work well with it. My other concern is that if the brickrate is high, and this method was released around april, it could be possible that Xiaomi has made some further updates, further increasing the chance for a brick.
3. Bypassing The Bootloader Unlock
I found this process on a post from these forums, which then sourced a reddit post. The reddit post is pretty straight forward and can be found here: wwwdotredditdotcom/r/Xiaomi/comments/5611tg/psa_you_can_flash_twrp_and_subsequently_cm13/ .This process works by flashing a legit miui rom, but by flashing it with a modified recovery image, in particular, a custom recovery like TWRP. Having considered the three methods, this looks like the easiest way of getting it done.
My questions are: has anyone done any of these three methods successfully? What method do you recommend? Have I missed anything? Are there any other methods?
My understanding is once the bootloader is unlocked, you install TWRP. Then once that is installed you flash whatever rom you want, which leads into my next question. What is the best ROM to use?
It looks like the most viable roms are the CM roms. I've seen CM 13 and CM 14, are people running CM 13 instead of 14. Why? Is it more stable? Ideally I'm after the most functionality possible. Are there any other roms that you'd recommend flashing? When flashing roms are you supposed to do all the standard things that you would on other phones, factory wipe/cache wipe/davlik cache wipe, flash rom, flash gapps? I've also seen that CM needs firmware flashed before the rom, will this mess anything up and can it brick? Can you do all this stuff from TWRP with a locked bootlader (method 3)? I really like having notification badges too, what will I need to do for this to happen?
If you have read all of this, I really appreciate you taking the time. I hope I haven't broken any forum rules in the process.
dude,it's too much to read for people. I can't believe i read it,anyway.
about unlocking the bootloader process(I'm telling you about my experience):
---step 1 : you sign up for a mi account,choose your country and verify your phone number>login to your mi account on your device(remember to enable every feature on your mi account on your device,you can disable backup)> go to https://i.mi.com and check your device,it should be there> go to http://en.miui.com/unlock/ , write for example dear sir or madam, I'm an austrailian developer and I want to try and work on projects like cyanogen mods and other custom roms. sincerely,JaFranchise - alright,after finishing the writing go to translate.google.com and translate it to chinese,then paste on the form,then apply,you will confirm your request by entering the code that was sent to you via mi message --- for me it took about 3 to 4 hours to receive my confirmation.
---step 2 : first try this,if you stuck on 50% error,you will try step 3,so here is the instruction,
sign in to your mi account on your device(enable find device),also on i.mi.com(to check your device). enable developer options,OEM unlocking and USB debugging. > download the latest version of MIFlashUnlock tool and log into your account link : http://bigota.d.miui.com/miflashunlock/MiFlashUnlock_1.1.0317.1_en.zip> turn off your device and go to fastboot (press and hold volume - and power button at the same time), connect your device to your PC, click unlock(on MIFlashUnlock tool), after your bootloader successfully unlocked, click on reboot.
---step 3 : this is for kenzo devices(redmi note 3 pro - snapdragon650) - if you're using redmi note 3(mediatekX10), you should download the roms(stable and developer) according to your device
you need to switch from global stable to global developer rom, download the latest global developer rom on android lollipop(5.1). link : http://bigota.d.miui.com/6.8.18/miui_HMNote3ProGlobal_6.8.18_d0da79d09e_5.1.zip> after downloading the rom,rename the file name to Update.zip then copy to internal storage(in downloaded_rom folder).> open updater app, select choose update package, go to downloaded_rom folder and select Update.zip. It will verify your rom and install it. > download the latest global developer rom from en.miui.com/download-301.html , repeat the instruction or just simply download via updater > then follow step 2
I think,It's better you first unlock bootloader,then mention me in the comments to go through that(about cm and aosp roms and flashing instructions) process.
goodluck.
Thanks for your reply and for reading it all. So your advice is unlock the bootloader the official way. I know it's too much to read, that's why I put a tl;dr section, because I probably wouldn't read that much! The last thing I want to do is annoy people.
Cheers for specifically telling me what I'd need to write in the application, massive help. Maybe some people have been unsuccessful because they haven't said the right things.
JaFranchise said:
Thanks for your reply and for reading it all. So your advice is unlock the bootloader the official way. I know it's too much to read, that's why I put a tl;dr section, because I probably wouldn't read that much! The last thing I want to do is annoy people.
Cheers for specifically telling me what I'd need to write in the application, massive help. Maybe some people have been unsuccessful because they haven't said the right things.
Click to expand...
Click to collapse
It's alot easier than it sounds. The hardest part is probably getting the drivers on your computer installed properly to unlock bootloader/miflash. The good thing about this device is if you brick it, it's fairly simple to unbrick via the edl method but yea, official unlock bootloader - flash zcx twrp - make a backup - flash away
Hemphiz said:
It's alot easier than it sounds. The hardest part is probably getting the drivers on your computer installed properly to unlock bootloader/miflash. The good thing about this device is if you brick it, it's fairly simple to unbrick via the edl method but yea, official unlock bootloader - flash zcx twrp - make a backup - flash away
Click to expand...
Click to collapse
So it looks like official unlock is the way to go about things. Why ZCX version of TWRP?
ZCX is essentially the official TWRP, but with some extra stuff in it to allow it to support F2FS, if I'm not mistaken. Since you've decided to unlock your bootloader the official way, both ZCX and the official twrp are fine.
JaFranchise said:
Thanks for your reply and for reading it all. So your advice is unlock the bootloader the official way. I know it's too much to read, that's why I put a tl;dr section, because I probably wouldn't read that much! The last thing I want to do is annoy people.
Cheers for specifically telling me what I'd need to write in the application, massive help. Maybe some people have been unsuccessful because they haven't said the right things.
Click to expand...
Click to collapse
you're welcome,yes if you officially unlock the bootloader,everytime you face an issue,for example got your bootloader locked again,you can use miflashunlock with ease.about the version of the twrp,i should say ZCX_TWRP_0917 is the way to go,it got everything you'll ever needed except for encryption you need lazyflasher-I don't want to go into details to make you confused-for more info about twrp and other roms check these links :
1- ⋆⋆ NEWBIE GUIDE ⋆⋆ [UPDATED] Available TWRPs, Add-On Zips, Root, Flash, Restore, FAQ
http://forum.xda-developers.com/redmi-note-3/how-to/guide-redmi-note-3-available-twrps-t3406708
2-step by step instructions for zcx twrp
http://forum.xda-developers.com/redmi-note-3/how-to/zcx-twrp-install-twrp-flash-supersu-t3462448
3- comprehensive guide for unlocking bootloader process
http://en.miui.com/thread-246705-1-1.html
Something really weird happened while I was installing roms. Someone how my OEM got locked and I flashed and voila stuck on the oneplus logo. I have my fastboot working properly also got twrp installed. The thing is that my bootloader is locked so i cant flash and I cant unlock bootloader because I cant flash and set oem unlock. I know this is ****ed up and also my volume up key is not working so we have to work without that. . Whenevr i turn on the device the powered by android quickly disappears and i am in the fastboot. If I do oem unlock it sends me to the recovery. I am not sure why i can't OEM unlock in fastboot. I don't care about data and stuff. Just want the phone working. The unbrick guide wants me to press the volume up key to get to the qualcomm flashing. Unfortunately i can't do that. Need of dire help please ;_;
I kind of have the same problem as of 2 days (see https://forum.xda-developers.com/android/help/bricked-oneplus-x-unlock-bootloader-t3816387), which is kind of strange, as I haven't read anywhere else about it on the internet.
I'll be following this topic.
Japeroen said:
I kind of have the same problem as of 2 days (see https://forum.xda-developers.com/android/help/bricked-oneplus-x-unlock-bootloader-t3816387), which is kind of strange, as I haven't read anywhere else about it on the internet.
I'll be following this topic.
Click to expand...
Click to collapse
I've solved it bud. IF you have a working recovery and bootloader. Flash the stock OS. It'll flash even though the bootloader is locked and then your can oem unlock and do whatever.
KenSha105 said:
I've solved it bud. IF you have a working recovery and bootloader. Flash the stock OS. It'll flash even though the bootloader is locked and then your can oem unlock and do whatever.
Click to expand...
Click to collapse
That's good news! But I think I've tried that, but had no succes. Can you link me the ROM you've flashed?
Japeroen said:
That's good news! But I think I've tried that, but had no succes. Can you link me the ROM you've flashed?
Click to expand...
Click to collapse
https://downloads.oneplus.com/oneplus-x/oneplus_x_oxygenos_3.1.4/
There.
KenSha105 said:
https://downloads.oneplus.com/oneplus-x/oneplus_x_oxygenos_3.1.4/
There.
Click to expand...
Click to collapse
Thank you. I've tried it, but the problem is that I'm stuck with the Oneplus recovery, as I've mentioned in my post. From there, I have 2 options to flash:
1) from internal memory. When I click this, nothing happens (no new screen or anything, nothing)
2) from USB (adb sideload). When I try to sideload the ROM using this option, it starts promising, but after a few seconds, it just says 'Installation failed' without any reason why. Just like for all other ROMS.
So... No progress here. I've also tried to flash the stock recovery (even though it should be on my phone already, maybe another version) using fastboot, but my OPX won't take it because the bootloader is still locked.
Last resort: I'll try the Oneplus live chat tomorrow, but I do not expect any useful information from that...
Japeroen said:
Thank you. I've tried it, but the problem is that I'm stuck with the Oneplus recovery, as I've mentioned in my post. From there, I have 2 options to flash:
1) from internal memory. When I click this, nothing happens (no new screen or anything, nothing)
2) from USB (adb sideload). When I try to sideload the ROM using this option, it starts promising, but after a few seconds, it just says 'Installation failed' without any reason why. Just like for all other ROMS.
So... No progress here. I've also tried to flash the stock recovery (even though it should be on my phone already, maybe another version) using fastboot, but my OPX won't take it because the bootloader is still locked.
Last resort: I'll try the Oneplus live chat tomorrow, but I do not expect any useful information from that...
Click to expand...
Click to collapse
Well guess what, they could solve it.
Or at least partly. It appears that Oneplus has an updated version of the tool used in the mega unbrick guide: MSMDownloadTool V2.1 instead of V2.0. This tool did it's job perfectly, OOS was also installed, in contrast to V2.0 of the tool. I ****ed it up again after that (oops), but found the tool V2.1 online here (https://github.com/finlayacourt/Oneplus-X-Recovery). Some files are missing here like the system.img, but I just copied them from the folder of tool V2.0 found in the mega unbrick guide. It didn't work as perfectly as Oneplus's tool, but at least I was able to install OOS from the Oneplus bootloader, which I wasn't able to before. So knowing that, in the end, the result is the same as for their tool. A working OS again, perfect! So now I can unlock the bootloader again and continue the adventure.
Now, what I've found is that the mainboard I have on my OPX is a newer version (if you search on Google for 'oneplus E1003_15', you'll find some things about it, not much though). I'm 99% positive that this caused all the problems I've encountered. It is why TWRP couldn't see any storage, why the stock Oneplus recovery couldn't see any storage, why the tool V2.0 didn't work and why V2.1 did work. If I wanted a working TWRP, I had to install a modified version of TWRP which is compatible with the newer version, from here: https://www.android-hilfe.de/forum/...-1-oreo-rom-unofficial-onyx-8-1-x.867374.html (yes, once you're relying on German sites, you know you went very deep). After that, I could install LineageOS 14.1 again. I was unable to install the unofficial LineageOS 15.1 however, but knowing where I came from, what I've gone through and how much time I've lost on all of this, I think I'll just stick with LineageOS 14.1 until this baby can retire...
Got to say I only have very positive experiences with Oneplus and it's customer support, and this only adds to it!
Hi, good evening to the community!
(EDIT: Anyway, I want to apologize if I'm doing something wrong. I recently joined).
I believe I made the biggest mess of my life, and now I'm desperate. I downloaded the latest version of TWRP, to update the one I already used; the problem is that. Now he is no longer in Recovery Mode. And worst of all? I had already deleted my OS. So, there's no way I can authorize OEM unlocking. So I can not use ADB & Fastboot. And I think I have to throw my device away as it is unusable. What should I do? I'm desperate and there are no solutions.
-Thanks
Lord_Miraak said:
Hi, good evening to the community!
(EDIT: Anyway, I want to apologize if I'm doing something wrong. I recently joined).
I believe I made the biggest mess of my life, and now I'm desperate. I downloaded the latest version of TWRP, to update the one I already used; the problem is that. Now he is no longer in Recovery Mode. And worst of all? I had already deleted my OS. So, there's no way I can authorize OEM unlocking. So I can not use ADB & Fastboot. And I think I have to throw my device away as it is unusable. What should I do? I'm desperate and there are no solutions.
-Thanks
Click to expand...
Click to collapse
There is no need to worry if you corrupt you recover, just enter into bootloader mode then flash the recovery.
code:-fastboot flash recovery moto.img
Note:- Moto should be replaced with the recovery name
If you want to return to stock ROM then here is the procedure:-
Firmware:-https://mirrors.lolinet.com/firmware/moto/surnia/official/
Procedure:-https://www.google.com/amp/s/forum....tore-moto-e-2015-stock-firmware-t3044936/amp/
Done now you are now stock ROM .
riyan65 said:
There is no need to worry if you corrupt you recover, just enter into bootloader mode then flash the recovery.
code:-fastboot flash recovery moto.img
Note:- Moto should be replaced with the recovery name
If you want to return to stock ROM then here is the procedure:-
Firmware:-https://mirrors.lolinet.com/firmware/moto/surnia/official/
Procedure:-https://www.google.com/amp/s/forum....tore-moto-e-2015-stock-firmware-t3044936/amp/
Done now you are now stock ROM .
Click to expand...
Click to collapse
Yes thanks! I did it yesterday, watching a Brazilian video. I had to download 3 different ROMs to be able to do such a process; so I did the process through Fastboot. Thank God I did not have to buy another device, hehe. And I'm already using another Custom Rom at the moment (RR, but I plan to change it as soon as I find another great new one that does not bug WhatsApp). Thank you again!
Hi,
I tried to upgrade my US998 from Oreo to Pie using LGUP patched. The upgrade process went well until the phone restarted and have this error message:
"Your device has failed a routine safety check and will not boot..."
I did try using LG Bridge to fix = not working
I did try fastboot boot laf.img (using extracted laf from H93031a_00_OPEN_EU_OP_1105) not working.
Any other solution?
Thanks
This Post got recommended to me. I am a Samsung user so my answer will probably be very stupid.
If you have fastboot, why don't you flash a recovery and a custom rom? Ik stupid but it's the only thing that comes to my mind since i don't have a LG phone lol
JanBoyGamer23 said:
This Post got recommended to me. I am a Samsung user so my answer will probably be very stupid.
If you have fastboot, why don't you flash a recovery and a custom rom? Ik stupid but it's the only thing that comes to my mind since i don't have a LG phone lol
Click to expand...
Click to collapse
Installing TWRP or any recovery wont work for me. The bootloader still locked thou.
jaacoozee said:
Installing TWRP or any recovery wont work for me. The bootloader still locked thou.
Click to expand...
Click to collapse
Is that "Download mode" the same as the Samsung one? How do you NORMALLY access it?
JanBoyGamer23 said:
Is that "Download mode" the same as the Samsung one? How do you NORMALLY access it?
Click to expand...
Click to collapse
I'm not sure. Normally I access download mode using volume up and power button. The download mode was there for a sec and then the screen back to
"Your device has failed a routine safety check and will not boot..."
again.
Ah ok so now I understand.
But why don't you unlock your bootloader then if fastboot works? Do you know for sure that TWRP doesn't work?
I really want to help but I don't have a LG phone
JanBoyGamer23 said:
Ah ok so now I understand.
But why don't you unlock your bootloader then if fastboot works? Do you know for sure that TWRP doesn't work?
I really want to help but I don't have a LG phone
Click to expand...
Click to collapse
EDIT: The LG Bootloader unlocking page is "under construction". Guess you have to bring your phone to LG for them to fix this...
JanBoyGamer23 said:
EDIT: The LG Bootloader unlocking page is "under construction". Guess you have to bring your phone to LG for them to fix this...
Click to expand...
Click to collapse
Unfortunately my LG V30 is US region. The official bootloader site not support my phone. Thanks for your info anyway
I'm not sure why a Samsung user was recommended this post. And no offense to the Samsung user, but the process for unlocking, etc is VERY different for Samsung than it is for LG... so I recommend not worrying about that. Believe me, I know, because I'm researching switching to a Samsung in the future, and the process is very different!
That being said, the best resource here is the WTF thread with the post by ChazzMatt. That post has everything you need in one place.
jacoozie, the error you're getting indicates that you had a non-stock phone when you flashed the KDZ on an unlocked phone. For this reason, it's no surprise you got this error - the phone must be COMPLETELY STOCK for a stock KDZ flash. I'm guessing you had TWRP or something else installed, which is causing this problem. Once you unlock, you cannot just flash things willy nilly... and generally you don't flash with KDZ unless you're trying to change models (aka Frankenstein) or on the way to a custom ROM.
It sounds like you've done some unlocking rooting... if so, I recommend you start over with the WTF thread, read it VERY CAREFULLY and ENTIRELY and then reflash as instructed there. I'm guessing you may need to go back to KDZ Nougat and then work your way forward. If you have questions, ask in that thread... but you shouldn't have any questions as the thread is VERY complete (been updated all the time with very detailed information, so everything is in there).
schwinn8 said:
I'm not sure why a Samsung user was recommended this post. And no offense to the Samsung user, but the process for unlocking, etc is VERY different for Samsung than it is for LG... so I recommend not worrying about that. Believe me, I know, because I'm researching switching to a Samsung in the future, and the process is very different!
That being said, the best resource here is the WTF thread with the post by ChazzMatt. That post has everything you need in one place.
jacoozie, the error you're getting indicates that you had a non-stock phone when you flashed the KDZ on an unlocked phone. For this reason, it's no surprise you got this error - the phone must be COMPLETELY STOCK for a stock KDZ flash. I'm guessing you had TWRP or something else installed, which is causing this problem. Once you unlock, you cannot just flash things willy nilly... and generally you don't flash with KDZ unless you're trying to change models (aka Frankenstein) or on the way to a custom ROM.
It sounds like you've done some unlocking rooting... if so, I recommend you start over with the WTF thread, read it VERY CAREFULLY and ENTIRELY and then reflash as instructed there. I'm guessing you may need to go back to KDZ Nougat and then work your way forward. If you have questions, ask in that thread... but you shouldn't have any questions as the thread is VERY complete (been updated all the time with very detailed information, so everything is in there).
Click to expand...
Click to collapse
Thanks for the reply.
I didnt install TWRP or any recovery tools to my phone. My phone bootloader still locked thou.
I have read the WTF thread but the problem is I cant get into my Download mode.
Ok, what steps are you using to try to get into download mode? Presumably turning off the phone, then holding the volume up button and plugging in the USB cable (other end already connected to a Windows computer), correct? If that doesn't work, can you try other USB cables? Sometimes a bad cable could prevent the phone from going into download mode.
Omarqaissy said:
I have a problem with my device, Google Pixel 7 Pro, after rooting and deleting it, after rebooting it did not work. Code 3 error appears and the phone does not work. Is there a solution for it?
Click to expand...
Click to collapse
Omarqaissy said:
لا يمكنني تشغيل الهاتف لتشغيل وضع المطور وفتح قفل المصنع. تتطلب المشكلة عند تثبيته فتح قفل المصنع
هل هناك طريقة للاتصال بك لإيجاد حل للمشكلة؟
Mod translation:
I can't boot the phone to turn on developer mode and factory unlock. The problem when installing it requires a factory unlock
Is there a way to contact you to find a solution to the problem?
Click to expand...
Click to collapse
My confusion starts with your statement "after rooting and deleting it".
What did you delete?
The gist of your posts seems to be: you did not unlock your bootloader; you tried to use PixelFlasher, but you gave it the wrong file -- you gave it a downloaded OTA file, which is an incremental update, but you were supposed to give it a full system file; somehow this resulted in you damaging your installation.
It is likely that you have already lost all data. If you have not already lost all data, it is likely that anything you do will destroy all data. If it is important to you to recover your data, find an official Google repair shop -- I do not know if your data can be recovered, but I expect an official Google repair shop to have the best chance.
If you accept the total loss of your data, and you want to try to fix the phone yourself, I think your best bet is to find a complete ROM image. It must be an official Google image. With the bootloader still locked, you will not be able to install any image that is not official.
There may be an easy way to install a ROM image. It would start with you booting your phone to recovery mode. This is not the same as booting Android, which you do not seem to be able to do. Try googling "pixel recovery mode".
I do not know if @badabing2003's PixelFlasher will help you. I think before you can use PixelFlasher you need to make sure you have properly installed "adb" and "fastboot". Start by reading instructions for PixelFlasher. Good luck.
J.Michael said:
My confusion starts with your statement "after rooting and deleting it".
What did you delete?
Click to expand...
Click to collapse
I'm confused as well.
One moment it was rooted and another it can't even OEM unlock?
J.Michael said:
The gist of your posts seems to be: you did not unlock your bootloader; you tried to use PixelFlasher, but you gave it the wrong file -- you gave it a downloaded OTA file, which is an incremental update, but you were supposed to give it a full system file; somehow this resulted in you damaging your installation.
Click to expand...
Click to collapse
He couldn't have done this in PF, PF will refuse to work with OTA image to do a full factory flashing.
J.Michael said:
There may be an easy way to install a ROM image. It would start with you booting your phone to recovery mode. This is not the same as booting Android, which you do not seem to be able to do. Try googling "pixel recovery mode".
I do not know if @badabing2003's PixelFlasher will help you. I think before you can use PixelFlasher you need to make sure you have properly installed "adb" and "fastboot". Start by reading instructions for PixelFlasher. Good luck.
Click to expand...
Click to collapse
Yes this is possible in PF,
Custom Flash
Select OTA image
Select SIDELOAD option
Flash
Root is not needed.
But if the device does not respond to adb commands because the author said he can't set the developer options and enable ADB, then it won't work.
badabing2003 said:
I'm confused as well.
One moment it was rooted and another it can't even OEM unlock?
He couldn't have done this in PF, PF will refuse to work with OTA image to do a full factory flashing.
Yes this is possible in PF,
Custom Flash
Select OTA image
Select SIDELOAD option
Flash
Root is not needed.
But if the device does not respond to adb commands because the author said he can't set the developer options and enable ADB, then it won't work.
Click to expand...
Click to collapse
I'm guessing "rooting" really meant "did something in an attempt to root".
I think the first question to answer is, how did he manage to damage his installed system when he hasn't unlocked the bootloader?
Although, if the words mean what they should, it *should* be possible to flash a random image with a locked bootloader, it just shouldn't be possible to boot it. But that is not the way the words seem to work with most of the people who post.