Hi All,
Today I decided to "update" TWRP to 2.8. I backed up the old recovery using Flashify, and then performed the update using the same. After a reboot I was treated to Download Mode with a 'Could not do normal boot' error.
I am quickly remembering that I used safestrap back when I originally did this after I got a Secure Magiccode Check Fail via ODIN in an attempt to fix things.
Is there any way for me to atone for sins, and undo the error of my ways?
So, I turned off the phone completely for about 30 minutes to an hour. After that, I started to charge it, and the battery icon came up. I turned it back on, and it jumped right into safestrap and continued working normally as if I had not mangled it. No idea why this happened, but hopefully this can help someone else.
You say TWRP, then safestrap. Those are two completely different things. Safestrap is for LOCKED BOOTLOADER devices. TWRP is for MDK ONLY. Be lucky that you didn't brick it.
Related
Okay. So. After some trouble with houstonn's latest rom's lately (getting stuck on boot), I decided I'd give one more try for the 4/30 release. Clean wipe, flashed it, flashed minimal apps. Stuck on boot. WOOP WHO CARES?
This time was different - I couldn't access recovery. So I tried like 30 more times to access recovery. Couldn't do it. LGNPST back to the ICS stock bin (11c). Get my OTA update to 4.1.2, rooted with this method http://forum.xda-developers.com/showthread.php?t=2006946. After that, I tried to access recovery mode again. Couldn't do it. So, I was like "what the hell, maybe FreeGee will help." So I continued on to unlock the bootloader with FreeGee and with CWM. Installed quickboot and chose to restart to recovery. SAME THING. Black Screen after LG logo. Can't get into recovery.
Now I'm LGNPSTing back to stock to repeat process. Any ideas on what's going on?
Edit: Running into quite a few problems with LGNPST. Gets stuck at 85% and won't boot even after power cycle.
Edit 2: TeenyBin AltBin let me format my partitions and then the LGNPST worked. Got the OTA. Rooted again, used FreeGee, except this time with TWRP 2.5.0.0. Wouldn't reboot afterwards, so moved on to TeenyBin AltBin again. The phone booted up and everything runs fine. One thing to note: I had some wifi problems when I just TeenyBinAltBin'd and used a restore point for stock 4.1.2 which is why I was so adamant to LGNPST like normal. Still can't flash any of the newer ROMs of houstonn's, but I can others. On the good side, I still have a phone. Hopefully if anyone else has the issue, they can follow this and resolve it.
Hello all. Long time lurker, first time poster here with a rooting question/situation. I rooted a Verizon Galaxy Nexus, running Android 4.2.2 today. After rooting, I thought to give Cyanogenmod a try and see how I liked it. It worked great, other than that I couldn't get on my Verizon mobile data, despite setting the APN's correctly (or so I thought...) After messing with that for a while, I decided to go back to Android Jelly Bean. I didn't backup the previous Android, because the phone was freshly wiped and had a factory reset done. After downloading a stock Android ROM.zip, I installed it and went back to Android flawlessly. The version didn't come with SuperSU or Busybox, or Titanium Backup (programs I am customary to using with root access, like many others) I went into Titanium Backup like an idiot and started slashing programs, including another Superuser that had been included in the Android ROM flash that I wasn't aware of. After this, I went into SuperSU and it said I would have to boot the phone in recovery mode to get it to work, so I did. I have CWM custom recovery on this phone. After doing that, the phone started booting normally instead of recovery mode, then showed the CWM custom recovery icon, and continued this process for a while. "bootloop". I went to start the phone normally, and the exact same thing happened. Tried custom recovery again, and same thing. Google icon starts, then the CWD logo comes up and continues in this pattern. I can access the boot loader, but can't start the phone or access recovery. To top it off, I never turned USB Debugging on the phone. Any Ideas?
Hey all,
First, I just wanted to say that I have searched high and low for a solution to this already without much success, so I'm coming to you guys in sheer desperation; normally these forums and/or Google turn up the answer pretty quickly, but for once I am thoroughly stumped, so I'm coming to you sages for help.
tl;dr: After failing to unlock the bootloader through Odin (failure at sboot.bin), I re-installed a previously-working stock VRALJB ROM through Odin only to be met with a frozen Samsung boot logo and an inability to enter into recovery mode. I can get the phone into download mode, but that's it. Leaving the phone on for hours has given me no results, just the Samsung logo.
Background
Before I did anything last night that caused this current situation, the phone was running an unlocked/rooted (but otherwise stock) VRALJB ROM since I purchased it second-hand back in 2013. Actually, the bootloader may not have been unlocked as I had assumed, because what started all of this was me deciding it was time for a newer, better-optimized ROM. It was certainly rooted, as I had no issues running and granting root privileges to CWM and flashing the recovery loader. This was something I have done a dozen times for other people's phones (ah, hubris), so when everything appeared to be in order for me to boot into CWM's recovery mode, I did so, but was immediately greeted with Verizon's wonderfully-annoying Yellow Triangle-o-Death. I guess that's what I get for assuming the bootloader was unlocked.
I wasn't too worried; I had already backed up everything prior to attempting this, and I had Odin and my stock ROM ready to go should anything happen. So, I did exactly that: booted into download mode, connected the phone to Odin, and installed the stock VRALJB ROM. After about 6 minutes, the phone restarted and booted into a fresh, new stock version of Jelly Bean. There were no issues with the install, and the phone was working just as it should.
Where the problem started
So, now that I knew that the bootloader had never in fact been unlocked, I began searching down the process needed to unlock it so that I could then install a custom ROM. I began following the steps found on galaxynote2root.com's page for the SCH-I605, including downloading the "GalaxyNote2UnlockVerizon" archive will all the necessary tools (CASUAL, SuckItVerizon, etc).
**NOTE**: I know, now, that there were other, better options that existed and that I should have taken that path instead, but as it had been about a year since I had attempted any kind of flashing on my phone, I was rusty on the most current best-practices for unlocking the bootloader, and just went with the first tutorial I found that matched my phone model/firmware.
I loaded up Odin, included the option to re-partition with the included .pit file, placed the BootloaderBaseline2.tar.md5 file in the Bootloader section, and hit start. Everything was going great until Odin reached the infamous sboot.bin part of the bootloader; it failed at that moment, giving me the usual error message:
<ID:0/004> sboot.bin
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
"Okay, no biggie," I thought to myself. I must have done something wrong, or maybe the bootloader baseline file was corrupt.
Assuming I had just soft-bricked my phone, I went ahead and reset Odin, loaded up the sch-i605-16gb.pit file, the stock VRALBJ ROM I had just successfully installed 20 minutes earlier, told Odin to erase everything, and hit start.
Odin had no problem re-installing the ROM. It went through the entire process again in about 7 minutes, and I was happy to see the Samsung logo pop up at the end. Only problem was, though, that the Samsung logo stayed there.
"Damn it," I thought. So, I let it sit for a while, thinking that maybe something was happening in the background, but after 10 minutes, the logo was still there. Obviously, something had gone wrong in the install, so I decided I would boot into recovery mode, clear the cache, and to a factory restore now that the ROM was "successfully" installed.
Except I can't get into recovery mode. When I do the usual Volume Up-Home Button-Power Button combo, the Samsung logo appears as it should, but stops right there; it will not enter recovery mode.
Okay, so I can't fix it that way. I'll just go ahead and re-install the ROM through Odin again. After all, I had just used this exact same .md5 ROM file only an hour earlier and the phone booted fully and I had zero issues; so, I knew that the ROM file itself wasn't corrupted.
So I tried re-installing the ROM again through Odin, but got the same result: Samsung logo, with no ability to enter recovery. I tried again and again, and even went and downloaded another copy of the stock VRALBJ ROM in the hopes that maybe something was wrong with the one I was using.
Nope. Same results.
So now my phone is bricked, and I'm at a loss as to how to get it back. I have yet to try newer ROMs, only because I don't want to update to a newer stock version and lose the ability to unlock the bootloader; after all, the entire point behind last night's excursion into madness was so that I could load a custom ROM.
That said, if installing a newer stock ROM from Samsung/Verizon is the only way of fixing this, I will do it, but I was hoping there was another way that may allow me to stay on the VRALBJ ROM as a stepping-stone to another custom ROM.
I appreciate any help I can get, and I apologize for the wall of text, but I know how important background information is when trying to diagnose and fix these kind of problems, so I assumed you guys wouldn't mind
Hey guys, I was running stock ZVC (with stock recovery and bootloader) until just a few minutes ago, when I finally gave in and told the phone to apply the OTA update that was pushed out last week (the "ZVE" one). It started doing its thing, but next time I looked back at the device it was in recovery mode, just sitting there at the menu prompt...
I've since tried rebooting and powering off about half a dozen times, but it just keeps looping back to recovery mode. I also tried wiping the cache and rebooting, with no luck... It still loops back to recovery mode. I don't know what went wrong, but I'm assuming it could be related to one of two things that I didn't think about until afterwards:
1) The phone was rooted via Kingoroot, and root was still active when I tried to apply the update.
2) Just a FEW programs were frozen via TitaniumBackup (as well as Android's own app management system, using the "disable" feature), but these weren't system- or kernel-critical apps. They were things like LG Health, Sprint Money, etc...
Can anyone suggest a fix? Right now it just keeps rebooting into stock recovery and I've never had to deal with an issue like this, so I'm not sure what to do. I was obviously running the stock ROM, so I'm not set up to flash stuff. Although if it can be done with the default recovery, I suppose I could obviously do that... Once again, everything was stock on the phone except for Kingoroot, which was still enabled during the update.
I'm in a pickle here, guys. It's not like I'm any different than everyone who "needs their phone for work," but yeah, I need my phone for work... If I have to wipe data/factory reset, there's probably no way to pull some data off of the phone via PC first, is there? I suppose it's not that big of a deal, but I have some data and some program data that I hadn't gotten around to backing up yet, because I didn't think I'd need to until before I attempted to flash a new ROM or custom recovery.
Any help would be HUGE. Thanks...
EDIT: I took it into the Sprint store today a couple hours after I posted this, and they said I'd have to send it in to LG for warranty service. I don't know if the Sprint tech person knew what she was doing or not (because she had to use Google to figure out how to put the phone into download mode, even though she owns the same model), but she said that she couldn't establish a connection between the PC and the phone...
Now I'm not sure if that's the case, or if she just didn't have the right drivers installed, or if she was even in the right mode (I think she was using some Sprint-made flashing tool, but she did get it into download mode). She also seemed bored and like she just didn't wanna deal with it, so I don't know...
Assuming I can flash back to an earlier build like ZVB (and assuming I can even find it online), is that done from download mode or from recovery? By the way, we also tried just doing a factory reset and that didn't work either; just keeps rebooting to recovery...
Thanks...
EDIT 2: Fixed by flashing to stock via these instructions. Had to select Board DL and use a different key sequence as described here.
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).
.