I recieved my CLNR from verizon yesterday.
I unlocked the bootloader
used fastboot to get amonra loaded
downloaded Super SU from the play store
Tried to restore from TiBU, and its saying I'm not rooted.
Where do I go from here?
Worse problem....I have no signal whatsoever. I just tried to check for amonra, it is installed.
Everytime I have turned off the phone and turned it on, its saying I need a sim card. Seemed to be working last night, now, nothing. and yes, the back is on.
So I am stock, unlocked and I thought rooted, but I guess not. Can I root in recovery? I just dont know which one to pick. Ok I rooted in recovery and still nothing. I went into the supersu app and it asked to update binaries, I hit yes and it tried to install but it said installation failed.
Edit, I just flashed a different version on superuser and all is good.
Thanks
Heather
Related
Okay, here's the story.
I rooted my phone, turned S-ON, and installed Cyanogen 7 RC-1. So far so good.
Next I threw on ROM Manager, and got the premium version. I updated CWR to 5.0.2.0. And then went to play.
Well, first thing I noticed was ROM Manager kept erroring out when it rebooted into recovery. The error report is something about being "unable to locate dev/tty0". That was when I noticed something.
In ROM Manager, it says Clockwork is updated to 5.0.2.0
But in Recovery Mode it says 2.5.1.2
So far, I've tried "Erase Recovery", flashing to 3.0.0.8 and seeing if that worked (it didnt'). Then i tried going back up to 5.0.2.0. That didn't work either.
I tried a manual instal of 5.0.2.0 and the system didn't even recognize the file, so I probably did something wrong there.
I'm just lost. Can anyone help me figure out what I'm doing wrong? I just want to flash some ROMs with up to date soft-/firm-ware.
new version is buggy
i had an update for my clockwork mod when i tried to download a rom so installed the updated clockwork but in the end i found the new version 5 to be very buggy but if you want to try just try installing another rom (do a nandroid backup first) and it should install the new recovery but in my oppinion i wouldnt bother upgrading why update something that works thats the common saying
Well, in this case, I'm trying to upgrade from Cyanogen (which I've backed up), to Synergy's GingerSense RS1 for the Droid Incredible. However, while it flashes the ROM, it hangs on the boot up screen when rebooting, so I have to go back to Cyanogen. What got this whole thing started was figuring out what I had to do to get that working.
I'm on HBOOT 079, CWR 2.5.1.2, and none of ROM Managers automated features work because of the "Can't located /dev/tty0" function. The only advice I could find online for that was that 2.5.x is too old, and I need at least 3.0.0.8 to load some of these ROMs.
Small error, I didn't run "unrevoked-forever" so I'm not S-OFF yet.
shadowfyre26 said:
Small error, I didn't run "unrevoked-forever" so I'm not S-OFF yet.
Click to expand...
Click to collapse
You did say you "turned S-ON" but really you just, as you said, didn't have S-OFF. So I'm guessing your problem was solved when you got S-OFF and tried again right?
Yup, I just fixed the S-ON issue into S-OFF, and lo and behold it worked.
*looks around sheepishly* Let us never speak of this again.
Sorry if it has been discussed but I couldn't find any info. I had just got my Amaze yesterday and had it perm rooted, flashed TWRP recovery, installed all my apps and restored most with data from tibu, had everything set up, I let the battery drain to death and then wanted to let it charge full overnight but I had some problems with it charging (led blinking orange) which I found was apparently due to TWRP recovery...?
Well I had it plugged in this morning to my comp and it was actually charging, so I rebooted via adb and found that all my apps I had installed were gone, the bloatware I removed was back on, not quite a factory reset being that my wifi was still connecting as well as my gmail account upon reboot. Any ideas why this happened? No nandroid was created either...oops. I have latest CWM on now.
Did you check if or the SuperUser is still there nor do you install them after the permroot process is occured?
hyperkamote said:
Did you check if or the SuperUser is still there nor do you install them after the permroot process is occured?
Click to expand...
Click to collapse
Superuser is still there. I rooted (with Hasoon2000's toolkit) and then flashed twrp and then installed everything. Since flashing latest cwm it seems to charge fine, so can I assume this is in-fact associated with twrp? I'd hate to have this happen on a regular basis if this phone has issues.
and in what tool or flashable script did you use prior on uninstalling the bloat?
Flashed a new rom yesterday. Actually, I just updated it on top of the previous version. Anyway, after flashing this, I 'lost' root. I thought it had somehow actually unrooted my phone after going into settings and turning superuser back on and it didn't work, so I decided just to root again. Went to do that, said it was already rooted, but I went ahead and rerooted. Did not work. ROM Manager and Titanium Backup will not work. However, I can shut the phone off and manually boot into cwm with no problem. I assumed when I flashed another rom, the issue would be taken care of, but today after not getting any signal, I reflashed a rom I had previously used with no problem, but when the phone is on, it acts as if it is not rooted. Any idea how to get my root back? Also, before you say it, I have never been able to restore any backup I've ever made. They all would say md5 mismatch, and I read the solution to this was to delete that file and just make another with the same name. I did that, but now when I try to restore it says error while restoring /system! Obviously, I do not know much about these things so please go easy on me. Thank you in advance for any help and suggestions!
EDIT: Flashed back to cm 10.1 and root seems to be back, but I would still like some insight into why none of my backups will ever restore. I obviously have to be or have done something wrong.
Celeste8157 said:
Flashed a new rom yesterday. Actually, I just updated it on top of the previous version. Anyway, after flashing this, I 'lost' root. I thought it had somehow actually unrooted my phone after going into settings and turning superuser back on and it didn't work, so I decided just to root again. Went to do that, said it was already rooted, but I went ahead and rerooted. Did not work. ROM Manager and Titanium Backup will not work. However, I can shut the phone off and manually boot into cwm with no problem. I assumed when I flashed another rom, the issue would be taken care of, but today after not getting any signal, I reflashed a rom I had previously used with no problem, but when the phone is on, it acts as if it is not rooted. Any idea how to get my root back? Also, before you say it, I have never been able to restore any backup I've ever made. They all would say md5 mismatch, and I read the solution to this was to delete that file and just make another with the same name. I did that, but now when I try to restore it says error while restoring /system! Obviously, I do not know much about these things so please go easy on me. Thank you in advance for any help and suggestions!
EDIT: Flashed back to cm 10.1 and root seems to be back, but I would still like some insight into why none of my backups will ever restore. I obviously have to be or have done something wrong.
Click to expand...
Click to collapse
Couple of things come to mind...
1) Did you open an app called SuperUser and make sure that TiBu was set to "Okay" or "Allow" whichever the option is
2) When you open terminal and type su does the $ change to a # --- if Yes then you are Rooted
EDIT --
Also what ROM did you flash that seemingly caused you to loose ROOT access?
So it has been a VERY, VERY, long time since I attempted to root a device. I admit, that I completely forgot most of what I knew from back in the day rooting like the Motorola OG Droid. Here's the deal. I tried rooting a USC XT1526 and I had no idea what I was doing. I followed the steps through and managed to install TWRP and SU. So I assume I got full root. Well The issue started after I got an UPDATE AVAILABLE message and tried to go through with the OTA Update. When it got to the point of installing the OTA Update, my device turned off like normal but instead of updating, it booted into TWRP recovery. It didn't update at all and when I booted my phone normally, it kept trying to update so my phone turn off (loop) every time it tried to install the update. I did a factory reset and it stopped rebooting. I later tried to flash back to fully stock but I believe I might have downloaded the wrong file because I now have a device with no WiFi. Can someone please help me.
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).
.