Had some issues with my camera recently and decided to do a nandroid restore. Restore didn't turn out well and I ended up with a factory reset device and here's where things get confusing for me.
1. I'm using the A2017G with B03.
2. TWRP installed and phone rooted, but bootloader LOCKED. Previously followed tenfar's guide back in August 2016.
3. Now my phone still has TWRP installed but no longer has root access. I wish to revert everything back to stock (i.e. stock recovery, everything) and do the proper method according to this guide but I do not know where to start as I don't even know the current state of my phone due to the locked bootloader. I fear that if I proceed with Controllerboy's consolidated guide, I may just brick my phone.
Appreciate any help rendered!
Scandiacus said:
Had some issues with my camera recently and decided to do a nandroid restore. Restore didn't turn out well and I ended up with a factory reset device and here's where things get confusing for me.
1. I'm using the A2017G with B03.
2. TWRP installed and phone rooted, but bootloader LOCKED. Previously followed tenfar's guide back in August 2016.
3. Now my phone still has TWRP installed but no longer has root access. I wish to revert everything back to stock (i.e. stock recovery, everything) and do the proper method according to this guide but I do not know where to start as I don't even know the current state of my phone due to the locked bootloader. I fear that if I proceed with Controllerboy's consolidated guide, I may just brick my phone.
Appreciate any help rendered!
Click to expand...
Click to collapse
You can use the MiFlash file to unlock the bootloader just like Controllerboy says in his guide. You don't need to do the TWRP part since you already have it xd
There shouldn't be any trouble since, if you read his guide, you flash TWRP before unlocking the bootloader.
Edit: sorry he doesn't use MiFlash xd. Should still be the same, just use those images he provides to unlock it.
Otherwise you should be able to use MiFlash with some files that the Russians made, there's one called A2017U_FASTBOOT_UNLOCK_EDL which besides from probably unlocking your device, gives you Fastboot if you are on A2017G.
Related
Hello,
So, I got my Nexus 10 today. Super nice tablet. I wanted to root it and unlock the bootloader - unlocking the bootloader went fine, and I managed to flash CWM recovery. However, I forgot the enable USB Debugging under developer tools before I started all this..
My question now, how do I get this thing to boot again? And what is the smartest move now to root it?
Thanks!
What method did you use?
I keep linking these same posts lately. lol
http://forum.xda-developers.com/showpost.php?p=37019359&postcount=10
http://forum.xda-developers.com/showpost.php?p=37020134&postcount=3
If you're stuck in a boot loop after unlocking the bootloader, you may have to perform a factory reset from recovery. I had to do this to get mine booting again after I unlocked it. After the reset, everything worked great.
Of course, this is also assuming you unlocked your bootloader using fastboot , and not a toolkit. Solution might be the same though either way. May be worth a shot.
I also borked the original ROM after unlocking it, before I even flashed a custom recovery using the nexus toolkit (http://forum.xda-developers.com/showthread.php?t=2015467)
However, it is quite easy to reflash the software (you will loose the data though) through the same toolkit. After that I was able to flash TWRP recovery and CM10.1
Thank you all for your help! Got it working using the linux toolkit and perform a factory reset
I want Lollipop and my Nexus 4 won't shut up about the OTA update. Naturally, it failed, and i have since tried to find a fool-proof guide to uptade it WITHOUT LOOSING DATA. Not been so lucky. Theres talk about fastbooting (?) and going back to stock, but not much in the way of step-by-step guides. I think most people with nexus 4 and root are like me - did it because it was easy, not knowing a lot about it...
I have rooted with towelroot, installed TWRP custom recovery with flashify, unlocked bootlocker with Bootunlock, installed Xposed framework and SuperSU. Never used ADB or any commands. Can't be the only one in this exact situation
What excactly do i need to do to get Lollipop without loosing any data (like a regular OTA update)?
Maybe user Titanium Backup or some kinda backup software to backup files and stuff then just go for a fresh installation? Most of the basic settings should be saved to your google account.
This post should help you with setting up ADB in your computer and to get you up to speed with using ADB and Fastbooot
KishanW said:
Maybe user Titanium Backup or some kinda backup software to backup files and stuff then just go for a fresh installation? Most of the basic settings should be saved to your google account.
This post should help you with setting up ADB in your computer and to get you up to speed with using ADB and Fastbooot
Click to expand...
Click to collapse
Thanks for the quick reply! But i was hoping for a solution that DIDN'T wipe my phone. I just wanna undo all the rooting business, so i can do the OTA...
605
tommyhj said:
Thanks for the quick reply! But i was hoping for a solution that DIDN'T wipe my phone. I just wanna undo all the rooting business, so i can do the OTA...
Click to expand...
Click to collapse
That would be interesting if someone has an answer for your question. I can use it too
Sorry that I couldn't help you.
tommyhj said:
I want Lollipop and my Nexus 4 won't shut up about the OTA update. Naturally, it failed, and i have since tried to find a fool-proof guide to uptade it WITHOUT LOOSING DATA. Not been so lucky. Theres talk about fastbooting (?) and going back to stock, but not much in the way of step-by-step guides. I think most people with nexus 4 and root are like me - did it because it was easy, not knowing a lot about it...
I have rooted with towelroot, installed TWRP custom recovery with flashify, unlocked bootlocker with Bootunlock, installed Xposed framework and SuperSU. Never used ADB or any commands. Can't be the only one in this exact situation
What excactly do i need to do to get Lollipop without loosing any data (like a regular OTA update)?
Click to expand...
Click to collapse
Hey,
Follow these instructions http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312.
there are a few things to note:
1. You do not need to unlock the bootloader, you will have done that when you rooted
2. Download the 5.0 image instead of the original stock image when you do this.
3. DO NOT flash userdata.img. That will wipe your data.
Those are the steps I followed to flash over to 5.0 without losing data.
But I would absolutely do a backup anyway, just in case something goes wrong.
gardn227 said:
Hey,
Follow these instructions http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312.
there are a few things to note:
1. You do not need to unlock the bootloader, you will have done that when you rooted
2. Download the 5.0 image instead of the original stock image when you do this.
3. DO NOT flash userdata.img. That will wipe your data.
Those are the steps I followed to flash over to 5.0 without losing data.
But I would absolutely do a backup anyway, just in case something goes wrong.
Click to expand...
Click to collapse
Ok, cool. So you're saying to towel-root my device, unlock bootloader with bootunlocker app, remove root by installing SuperSU and using the clean-up funtion. And then adb fastboot flash boot/recovery/system from the FACTORY img? Why not sideload the OTA instead? Because it wont work unless i reflash stock 4.4.4 completely?
Hi,
I'm not sure if it's the right place to ask this, but I need help. I just got my Axon 7 in the mail today so I was eager to root it and get started. It did not go well.
The version I got was on b27, and it had an update to b29 right out the box. I did not think too much of it and did the update. I realized later that if I wanted to root, I would need to be on b20 instead. No worries, I got into recovery, flashed the b20 stock image, and all went fine. I went on and rooted using tenfar's utility, and it also went fine. I rebooted went with DrakenFX's way to update back to b29, but something went wrong in the process, and I don't remember the exact message. I told myself that it might be cause I wasn't running the latest TWRP. When I first got into recover after using tenfar's utility, I noticed that the TWRP version was not the latest (3-0-2-0? maybe). I had just downloaded the most recent TWRP image from Unjustified Dev (twrp-3.0.2-2-a2017u.img), so I decided to update right away from within TWRP...I guess this is not something you can do.
Long story short, the phone simply won't get into recovery mode now. The led flashes red for a second, then the phone simply shuts down.
The weird part is that it boots just fine, and I can get into ADB and bootloader too. However, my bootloader is locked once more, and root does not work either. I am now on b29, so I cannot use tenfar's utility.
So, am I SOL? Is there a way to restore the stock recovery image via ADB? I tried flashing TWRP again, but I get a "FAILED (remote: Partition flashing is not allowed)" in ADB, most likely because my bootloader is locked again?
The good part is that the phone is usable and everything seems to work, but having no recovery is a bit unnerving...if something goes wrong again, the phone will be a dead brick.
Thank you very much.
OK, I just realized that I could still use tenfar's utility even though I was on b29....pheww, what a relief. Back in TWRP. Sorry, you can delete this thread (I would do it if I knew how )
arky33 said:
OK, I just realized that I could still use tenfar's utility even though I was on b29....pheww, what a relief. Back in TWRP. Sorry, you can delete this thread (I would do it if I knew how )
Click to expand...
Click to collapse
Can you link me in the right direction? I'm having the same problem where I can get to bootloader and fastboot, but no recovery. I'm on a2017u.x.x.b29, too.
Hi,
I am not sure anyone should follow my advice considering how I somehow managed to screw up a relatively simple process, but here's how I fixed it. I used tenfar's utility from this thread to flash TWRP again. Even though I was on B29, I used the B27 package and it worked fine. But don't flash the boot image, just the recovery! After that, I could boot into TWRP again. From there I followed this great instruction thread and got Lineage up and running in minutes.
I hope this helps you get going, but keep in mind that this might not be the proper way to do things, it's just what worked for me. Cheers.
arky33 said:
Hi,
I am not sure anyone should follow my advice considering how I somehow managed to screw up a relatively simple process, but here's how I fixed it. I used tenfar's utility from this thread to flash TWRP again. Even though I was on B29, I used the B27 package and it worked fine. But don't flash the boot image, just the recovery! After that, I could boot into TWRP again. From there I followed this great instruction thread and got Lineage up and running in minutes.
I hope this helps you get going, but keep in mind that this might not be the proper way to do things, it's just what worked for me. Cheers.
Click to expand...
Click to collapse
Thanks, Arky!
I've been away from XDA for quite some time since I've had the S6 Edge on Verizon and there hasn't been any type of root action on it. I really appreciate the links you posted!
I tried to root H918 T-Mobile, and ended up with just an unlocked bootloader, and no TWRP install.
I'd like to re-lock the bootloader, but I can't find any instructions. Any unroot instructions I've seen, include using TWRP.
Thanks!
Same here, before i ended up bootloader unlocked. Well decided to relock the bootloader
Just fastboot oem locked
jay661972 said:
Same here, before i ended up bootloader unlocked. Well decided to relock the bootloader
Just fastboot oem locked
Click to expand...
Click to collapse
OK. Tried this....and now I get:
Your device is corrupt
It cannot be trusted
and will not boot
Please help!
jeffeil said:
OK. Tried this....and now I get:
Your device is corrupt
It cannot be trusted
and will not boot
Please help!
Click to expand...
Click to collapse
have to wipe the whole phone you must have a custom boot.img
the t-mob version is unlocked via lgs website right
Try this method. As far as I know everything is back to stock at least it acts like it is.
https://forum.xda-developers.com/v20/how-to/restore-v20-to-100-stock-bricked-devices-t3524903
Old thread but i found it while trying to restore my US996 back to factory. The kdz method works then you just run the fastboot command to relock the bootloader. Amazing it was that easy to relock the bootloader....
I flashed the 10s update to h918 and very stupidly forgot to flash root so I'm stuck on unrootable 10s. I want to lock my bootloader so can at least have Android Pay working, if i lock it can it be unlocked again or do i have to wait for a root method for the new 10s software?
nymikey said:
I flashed the 10s update to h918 and very stupidly forgot to flash root so I'm stuck on unrootable 10s. I want to lock my bootloader so can at least have Android Pay working, if i lock it can it be unlocked again or do i have to wait for a root method for the new 10s software?
Click to expand...
Click to collapse
I think you can unlock /relock as many times as you want. Root take place after unlocking but you can't do that anymore.
I rooted my v20 f800l a few months ago using dirty Santa method. Everything was going fine until I decided to reset my phone via twrp. I selected system, internal memory, cache and ended up without an os with only access to twrp. I had a nandroid backup but twrp couldnt read or detect the nandroid backup files. With nothing else left to do i flashed it with a kdz file version 10e using lgup software. Now I have my phone running fresh os very smoothly but the bootloader is locked and root/twrp is not there anymore. Now I plan on rooting it again as I'm still on 10e version but I'm not sure if there is a bootloader lock/relock limit, I've already unlocked bootloader once and locked it once, can I do it again? Or is there a limit to it? Please help
lamepsycho said:
I rooted my v20 f800l a few months ago using dirty Santa method. Everything was going fine until I decided to reset my phone via twrp. I selected system, internal memory, cache and ended up without an os with only access to twrp. I had a nandroid backup but twrp couldnt read or detect the nandroid backup files. With nothing else left to do i flashed it with a kdz file version 10e using lgup software. Now I have my phone running fresh os very smoothly but the bootloader is locked and root/twrp is not there anymore. Now I plan on rooting it again as I'm still on 10e version but I'm not sure if there is a bootloader lock/relock limit, I've already unlocked bootloader once and locked it once, can I do it again? Or is there a limit to it? Please help
Click to expand...
Click to collapse
Don't believe there's any limit so go ahead
Sent from my LG-H910 using XDA Labs
I recently tried flashing SuperSU in TWRP. When I rebooted the phone, it showed the boot screen for a split second and rebooted into QFIL mode. I can access fastboot and the stock recovery. What are my options?
EDIT: Forgot to mention that my firmware version is 19S
If you can access fastboot connection, then you should try to adb push. With stock recovery you should use stock rom. Also you can try to wipe, but it's a bit risky.
Top Feel said:
I recently tried flashing SuperSU in TWRP. When I rebooted the phone, it showed the boot screen for a split second and rebooted into QFIL mode. I can access fastboot and the stock recovery. What are my options?
EDIT: Forgot to mention that my firmware version is 19S
Click to expand...
Click to collapse
What pro 3 do you have
Sent from my LEX727 using xda premium
Top Feel said:
I recently tried flashing SuperSU in TWRP. When I rebooted the phone, it showed the boot screen for a split second and rebooted into QFIL mode. I can access fastboot and the stock recovery. What are my options?
EDIT: Forgot to mention that my firmware version is 19S
Click to expand...
Click to collapse
I don't remember the exact options in stock recovery.
But you should have the option to clear cache try that first. If it doesn't work, you will need to choose the option for factory reset.
Be careful.
When you root you should first unlock the bootloader, flash a permanent TWRP recovery and root..........Do all of these steps in succession.
There are plenty of guides, ensure you read them or you will end up with a hard brick.
The X727 is unlike the X720. If you are currently at 5.8.19s, then you can temporarily unlock the bootloader. read the instructions to make it permanent, then with root ( I suggest Magisk) you can install whatever custom Rom you want.
Here is a good set of instructions: https://forum.xda-developers.com/le...7-model-persistent-bootloader-unlock-t3500388
tsongming said:
I don't remember the exact options in stock recovery.
But you should have the option to clear cache try that first. If it doesn't work, you will need to choose the option for factory reset.
Be careful.
When you root you should first unlock the bootloader, flash a permanent TWRP recovery and root..........Do all of these steps in succession.
There are plenty of guides, ensure you read them or you will end up with a hard brick.
The X727 is unlike the X720. If you are currently at 5.8.19s, then you can temporarily unlock the bootloader. read the instructions to make it permanent, then with root ( I suggest Magisk) you can install whatever custom Rom you want.
Here is a good set of instructions: https://forum.xda-developers.com/le...7-model-persistent-bootloader-unlock-t3500388
Click to expand...
Click to collapse
Thank you! This ended up unbricking my phone. I just finished flashing TWRP and Lineage 15.1 yesterday :good:
Top Feel said:
Thank you! This ended up unbricking my phone. I just finished flashing TWRP and Lineage 15.1 yesterday :good:
Click to expand...
Click to collapse
Congratulations!
Thank you so much for letting me know that you successfully un-bricked your phone, that is awesome news!