I bought my Moto X Pure used, and the "bootloader unlocked" message pops up everytime I boot up. However, a new security update came out this morning. But, when the update tries to re-boot, I get the TWRP main screen. The update never takes hold and keeps trying to re-boot. Which brings up the TWRP screen over and over. I've never rooted or worked with custom ROMs, so I'm in the dark here. Any ideas how I get out of TWRP Hell? Thanks.
rsdin559 said:
I bought my Moto X Pure used, and the "bootloader unlocked" message pops up everytime I boot up. However, a new security update came out this morning. But, when the update tries to re-boot, I get the TWRP main screen. The update never takes hold and keeps trying to re-boot. Which brings up the TWRP screen over and over. I've never rooted or worked with custom ROMs, so I'm in the dark here. Any ideas how I get out of TWRP Hell? Thanks.
Click to expand...
Click to collapse
Hi,
Your device is on Twrp Recovery, so official stock OTA's won't get installed via custom recovery like TWRP.
They requires stock recovery. Due to scripts / modifications etc..
Meanwhile, ive found this for you, follow that and fix your device.
Good luck!!
Related
I love my new phone, but I can't seem to figure out how to access its recovery. I rooted on the first day(way to go, community!) and have confirmed that root access is working. Titanium is doing its thing without an issue.
My question: How do I access the recovery on my HTC EVO 4G LTE? Read on for what I've done so far that hasn't been successful, to avoid the forum back-and-forth.
I installed a custom recovery(twrp), and I want to access it to confirm it actually did install, but it appears that the recovery is not accessed in the same way as with the OG EVO. I've tried holding down one or both volume buttons as the phone powers on, and all that accomplishes is a quick blinking of the HTC branding splash page, and then a black screen for as long as I hold down the buttons(I've held them for as long as three minutes, and the result is the same). As soon as I let them go, the system boots normally, with no option available to enter the recovery.
I tried asking on the #HTC-EVO-LTE channel, but it wasn't much help as the people there aren't as interested in user q&a as they are in development. That's just fine by me. Just a misstep on my part.
+ewalk486 did PM me and advise me to turn on fastboot, which I did. But the behavior is unchanged. Any help would be great.
try using the goomanager
Goomanager, which is what I used to install my recovery, and what told me that the install had succeeded, booted me to the boot menu. I've noted that the phone still says S-ON, which is troubling.
Anyway, I select BOOTLOADER and then RECOVERY, and it just drops me back to where I was. No recovery comes up.
bahua78 said:
Goomanager, which is what I used to install my recovery, and what told me that the install had succeeded, booted me to the boot menu. I've noted that the phone still says S-ON, which is troubling.
Anyway, I select BOOTLOADER and then RECOVERY, and it just drops me back to where I was. No recovery comes up.
Click to expand...
Click to collapse
there is no s-off yet bro
where did u get that info? lol
What info? I reported what appears to be wrong. I selected BOOTLOADER and then selected RECOVERY, and no recovery came up. That's where the discussion is.
I have a massive issue...
Somehow I lost my TWRP recovery and when I tried to reflash it, I got the "software unauthorized by Verizon error" each time I started my phone.
I thought, no biggy, I'll just reflash back to VRALJB and all will be well with the world. Did it. No problem.
I then tried to unlock the bootloader. This is when all hell broke loose. I had to reflash VRALJB again and since then, I started getting stuck on the "Samsung Galaxy Note 2" screen (the first one, immediately after the phone turns on). I could not enter recovery using the (Volume UP + PWR + HOME) key combo. I could only enter download mode and use odin.
I tried everything. The only thing that worked was downloading the stock 4.4.2 Verizon image released a few days ago from sammobile.com
(I605VRUFND7_I605VZWFND7_VZW).
Now, I do not have root and my bootloader is locked, but at least I have a working phone and KitKat.
Hopefully the above helps someone, but, my question is, where do I go from here?
How do I go about installing a custom recovery and getting root? I would like to keep stock 4.4.2 as well and before anyone asks why, I want custom recovery for the sole purpose of managing my TWRP backups. Stock OS though.
Since you updated to 4.4.2, there isn't much you can do. No root, no recovery, no safestrap...yet. The only thing you can do is wait for developers to find a way to root this version of android.
Hi my friend, I have met the same problem, so could you tell me how to get that I605VZWFND7_VZW rom~
Please~~
I bought a used N9 with 6.0.1 on it. Not my first Nexus, I have a 7 and 6, unlocked and rooted.
I unlocked the bootloader, that went fine. I installed TWRP 3.0.1 and can boot that no issues.
I flashed Pure nexus from TWRP and Gapps, that completed without error.
When I reboot, I get a Dialog box Pure Nexus - Starting Android screen .
Then I get my unlock pattern.
After that infinite boot animation. Yes, I left it for a long time, till the battery went out.. Over an hour.
I'm sure I missed something? Like a fastboot flash step or something? Maybe about de-encription?
Thanks
PS yes I googled and read the forums... no luck yet thus the post.
Jeff_in_LA said:
I bought a used N9 with 6.0.1 on it. Not my first Nexus, I have a 7 and 6, unlocked and rooted.
I unlocked the bootloader, that went fine. I installed TWRP 3.0.1 and can boot that no issues.
I flashed Pure nexus from TWRP and Gapps, that completed without error.
When I reboot, I get a Dialog box Pure Nexus - Starting Android screen .
Then I get my unlock pattern.
After that infinite boot animation. Yes, I left it for a long time, till the battery went out.. Over an hour.
I'm sure I missed something? Like a fastboot flash step or something? Maybe about de-encription?
Thanks
PS yes I googled and read the forums... no luck yet thus the post.
Click to expand...
Click to collapse
Try again, but format data and clean flash this time
Hi all. I just got my factory warranty back and I attempted to root it. Everything went as it should, until just after the install finished. Instead of rebooting normally, it now will only reboot into TWRP. Once there, when I try to flash a custom ROM (in this case, Bliss, but I don't think it matters, I get an error message that says the zip file is corrupt. Then, while still in recovery, when I tried to wipe everything except the sd card, it says mkfs.fat process ended with error. I then powered down and attempted the factory reset. I scrolled down on both screens and it did not say anything about any errors, so I assumed it took. However, it reboots right back into TWRP recovery. It also boots right to TWRP recovery when I try to boot normally. Of course, adb does not recognize the phone in any mode that I can get into (fastboot/recovery/download), so, I can't use LG Bridge to reflash the original firmware. Does anybody have any ideas for a fix? I know that this replacement phone had 6.0 on it. I thought I did everything to a t? TIA...
OK, not sure how I got there, but when I attempt to reboot from TWRP it says No OS Installed! Are you sure you want to reboot? That at least says what the problem is. Does anybody know how to fix this?
you have the latest twrp recovery? Just make sure you have 3.0 or higher and then try flashing again. And IMO the blissrom isnt worth using unless you dont mind smaller screen, no second screen, wonky Bluetooth and no camera.
AwesomeFabe said:
you have the latest twrp recovery? Just make sure you have 3.0 or higher and then try flashing again. And IMO the blissrom isnt worth using unless you dont mind smaller screen, no second screen, wonky Bluetooth and no camera.
Click to expand...
Click to collapse
Hey, I actually just fixed it. I finally was able to get back into download mode and I then used LG Bridge. Restoring now. Yeah, I actually picked it for some reason I cannot remember when I was faced with having to put in a custom rom as my option. I agree. When I had 5.1.1 everything worked after I got the bloatware out. Not going to get too fancy, I had a bit of a scare.
I thought you guys might find this amusing, and hopefully it will help some people that get into a similar situation as myself. First, a little background - I rooted and installed Alliance Rom years ago back before the bootloader was unlocked. This worked amazing for me for a long time but I've recently had some weird issues with my phone so I decided to do a factory reset.
I went into settings, clicked factory reset, and then my phone got into a boot loop on recovery. I remember from before I had to do a regular boot then click recovery at the prompt instead of doing the factory recovery so I did that.
Instead of doing a normal wipe, I wanted to wipe everything on my phone and start from scratch so I did the full wipe (in what I think was TWRP or safestrap or whatever). When I went to reboot my phone it had a message like "are you sure? there's no OS installed" and I clicked ok. Well now I couldn't get the phone to boot into anything except download mode so at least I can use Odin.
I'm frantically searching google to try and find ways to install some sort of recovery so I could load AllianceRom again since I still had the zip file for it. Eureka, I found TWRP for my phone! I tried to flash TWRP through Odin but that doesn't work because my bootloader wasn't unlocked.... I remember this from last time ... all of the places I found online to install any sort of recovery required the phone to be booted into android.
So I'm clicking around and someone has a recovery randomly posted in a thread so I install it thinking, what the hell, what's the worst that could go wrong. So I install it through Odin and boot into normal recovery and I get this message saying my phone has been tampered with and to go to a verizon store immediately! Oops... upon further investigation (looking at the download screen), I tripped the knox flag... oh well, it's not like my phone is in warranty anymore (I got it on release day).
I search around looking for what I should do next and I found a thread that talked about being on complete stock, rooting, then unlocking the bootloader. I download all the files I need (newest firmware here - https://www.sammobile.com/firmwares/galaxy-note3/SM-N900V/ and thread here - https://forum.xda-developers.com/ve...guide-ob6-of1-root-bootloader-unlock-t3439010) to go back to stock and flash in Odin. Actually I didn't download from sammobile.com because it was downloading too slow so I just googled the file name and found it somewhere else faster, go figure.
Everything seems to be going ok then all of a sudden FAIL in Odin... Ahhh what the heck do I do now? Try again obviously! Second try works woo hoo! Phone start booting up, things are looking good!!! hooray!! But wait... it's taking forever to start and it's stuck on the Verizon logo... uh oh... taking way too long to boot up so I pull the battery and try again. Boots right in saying that android is upgrading so I think I'm finally in the home stretch here.
I try to run the ArabicToolApp for Root but I installed the latest firmware which isn't supported DAMN IT! Downloaded the correct firmware (OB6!), flashed in Odin, same problem before where it was stuck on the red verizon screen, pulled battery, rebooted, finally time to get root!
Phone finally boots into OS and I get a popup "unfortunatley com.google.process.gapps has stopped" great... and it keeps coming up over and over again after I hit ok... just my luck! Reboot again to see if that fixes the issue. Seems weird that I didn't have to go through all the initial setup stuff I did on the other version I installed... hmm... or maybe it was because I pulled the battery on the red verizon screen? Whatever. I somehow manage to get to options to do a factory reset and I let the verizon screen stay on a while this time. I'll go take my contacts out and give my wife some love while I wait
Come back and the phone is at the setup wizard, this is good news. Enabled USB debugging, installed root, done! Thank god!
Next I want to unlock the bootloader. I follow the steps here which aren't very clear (I'm guessing on purpose for novice computer users) - https://forum.xda-developers.com/ve...l/official-note-3-verizon-bootloader-t3359370
1. I installed eMMC from the play store to make sure my CID started with a 15, it does so I know I'm good to use the hack.
2. I installed both files in the unlock kit (adb and driver setup)
3. Fired up adb, navigated to where I had unlock_n3, and ran through the first part of the code once, reboot my phone, checked that the CID was the developer CID, and then ran the second part of the code three times before it worked
I verified the bootloader was installed correctly by trying to install TWRP through Odin, which worked!
I'm going to try out Jasmine Rom since it's a popular one that is on 5.0. My SD card only showed 30 megs free or something like that, so I formatted it from within android and copied the zip file over and installed the Rom through TWRP. Rom installed just fine, so I did one last factory reset which worked great and I think I'm finally good to go!
If you have any questions or run into any issues feel free to reply here and I'll try to help as much as I can.
Glad it worked out for you in the end.
From making a few mistakes I know that sinking feeling "oh no, what have I done?"
FWIW, the bootloader unlock method (in principle) works from nearly ANY ROM which is rooted - so, you would have saved yourself a bunch of time if you had started with that before you wiped the Alliance ROM. So long as you have root and a CID value that starts with 0x15, you just need root privileges - no need to return to stock and re-root.
(The "in principle" part is that there were several bugs in the "safety checks" portion of the unlocker binary that were sensitive to the OS revision, so you might have to search through the unlock thread to find a version of the unlock binary that is compatible with whatever rooted ROM is on the phone when the unlocking is attempted.)
good luck
PS The AryaMod ROM (w/ phantomOne kernel) is pretty solid - Marshmallow w/ S-Pen apps, too! As with any other dev ROM, there are a few sharp edges, but mostly everything works (except NFC).
.