I'm having an issue with my friend's GN,
He suffers from random reboots which automatically restore the phone information to a specific date in the past.
I tried the toolkit, manual root and unlock but no luck.
the bootloader itself relocks itself right after i try the "fastboot reboot-bootloader" command.
I cant flash CWM permanently.
Can this be the recovery partition kicking in? I tried renaming it and I didn't get an error.
I managed to root the device, but then I cant install any programs from the Market, I was trying to get Root Explorer to work to ensure that the recovery is renamed or removed.
Whenever I flash the bootloader to primela03 it goes back primekk15.
Is this a GSM GNex (i9250)?
i9250
To me it sound like you actually never unlocked the bootloader in the first place..
Edit: To be more constructive... I have no idea what "the toolkit" does or how it works.
To unlock your bootloader you boot into it and run "fastboot oem unlock". That's the whole process. I personally don't see the value of a toolkit obscuring that process.
Unlocking your bootloader will cause your phone to factory reset and wipe everything on it. Have you done this? Have your phone asked you to confirm this? Did you click the volume-rockers to "yes" and then confirm with the power-button? And then, did the phone get wiped?
If you cannot answer "yes" to every question asked above, you have not unlocked the bootloader. End of story.
When you boot the phone up there should also be an unlocked lock icon under the Google logo at the bottom of the screen.
This is a wacky situation,
I tried using GNex toolkit 6 (http://forum.xda-developers.com/showthread.php?t=1392310) and it never worked.
"fastboot oem unlock" unlocks the device, but the as soon as I try "fastboot reboot-bootloader" it goes back to it's locked state.
I tried flashing another bootloader right after I unlocked it, but it reverted to the old one after rebooting.
BlindWolf8 said:
When you boot the phone up there should also be an unlocked lock icon under the Google logo at the bottom of the screen.
Click to expand...
Click to collapse
Did that, but as soon as I reboot the lock icon goes away.
aGoGo said:
Did that, but as soon as I reboot the lock icon goes away.
Click to expand...
Click to collapse
Strange
There is a file that will put the stock recovery back when you reboot. I'm not sure what else that file does but maybe that's your problem?
Going from memory, I think the process is unlock via fast boot, flash clockwork recovery, boot into recovery, flash super user, I also removed that recovery file at this stage via adb even though other directions have you do it later with root explorer. And that was it. If you do it the way others wrote it up (using root explorer) you'll have to reflash the recovery again.
Sent from my Galaxy Nexus using Tapatalk 2
DeezNotes said:
There is a file that will put the stock recovery back when you reboot. I'm not sure what else that file does but maybe that's your problem?
Going from memory, I think the process is unlock via fast boot, flash clockwork recovery, boot into recovery, flash super user, I also removed that recovery file at this stage via adb even though other directions have you do it later with root explorer. And that was it. If you do it the way others wrote it up (using root explorer) you'll have to reflash the recovery again.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Here's what I just did:
1- Unlocked the recovery
2- Booted insecure image
3- pushed superuser
4- installed root explorer, ROM Manager via adb
5- in root explorer I deleted recovery-from-boot.p from /system and it came back then tried "adb shell rm /system/recovery-from-boot.p" and it's gone.
6- Tried downloading CWM from ROM manager and the phone reboots whenever it starts download and goes back to stock
rebooted and the damn thing still living in the past!!! even the recovery file is back!
aGoGo said:
Here's what I just did:
1- Unlocked the recovery
2- Booted insecure image
3- pushed superuser
4- installed root explorer via adb
5- deleted recovery-from-boot.p from /system
rebooted and the damn thing still living in the past!!! even the recovery file is back!
Click to expand...
Click to collapse
You have to go back in and re-apply the recovery. That file "recovery-from-boot.p" is like a "reset" file that puts the stock recovery back during the boot process. I suspect it may be re-locking your bootloader too, but this is just a guess.
After you do step 5, repeat steps 1 and 2.
aGoGo said:
Here's what I just did:
1- Unlocked the recovery
2- Booted insecure image
3- pushed superuser
4- installed root explorer via adb
5- deleted recovery-from-boot.p from /system
rebooted and the damn thing still living in the past!!! even the recovery file is back!
Click to expand...
Click to collapse
When you "Unlock the recovery," do you mean you flash a custom recovery or do you mean you unlock the *bootloader*? It's not the same thing.
aGoGo said:
Here's what I just did:
1- Unlocked the recovery
2- Booted insecure image
3- pushed superuser
4- installed root explorer, ROM Manager via adb
5- in root explorer I deleted recovery-from-boot.p from /system and it came back then tried "adb shell rm /system/recovery-from-boot.p" and it's gone.
6- Tried downloading CWM from ROM manager and the phone reboots whenever it starts download and goes back to stock
rebooted and the damn thing still living in the past!!! even the recovery file is back!
Click to expand...
Click to collapse
O_O
the only thing I can think of is a hardware problem is causing the device to do a hard reset every time you boot.
j.go said:
When you "Unlock the recovery," do you mean you flash a custom recovery or do you mean you unlock the *bootloader*? It's not the same thing.
Click to expand...
Click to collapse
I unlock and then flash or sometimes reboot another boot image.
DeezNotes said:
You have to go back in and re-apply the recovery. That file "recovery-from-boot.p" is like a "reset" file that puts the stock recovery back during the boot process. I suspect it may be re-locking your bootloader too, but this is just a guess.
After you do step 5, repeat steps 1 and 2.
Click to expand...
Click to collapse
Did that, the moment I reboot, everything goes back to normal :s
I'm also unable to wipe from the normal system settings, the phone reboots when we try that.
can it be related to this issue? http://www.galaxynexusforum.com/forum/rescue-squad/4093-data-not-wiping-cant-return-stock-3.html
If you have problems doing data wipe/factory reset, it's quite possible that storage is corrupted/failing. It may be whats causing all the random reboots and reverting to old info. Best to bring to a samsung center and make that warranty claim.
I'm not sure what you're doing wrong... but its something.
You shouldn't have to flash another boot loader. I'm not sure what you would gain from that with the phone being a nexus?
Flashing another recovery is necessary for flashing different roms, kernels, mods, root, etc.
If you are indeed flashing a different boot loader, may i ask why?
Sent from my Galaxy Nexus using Tapatalk 2
Don't just delete the file recovery-from-boot.p, as there's one more file that can do bad things. It's called "install-recovery.sh" and is to be found within /system/etc
Theshawty said:
Don't just delete the file recovery-from-boot.p, as there's one more file that can do bad things. It's called "install-recovery.sh" and is to be found within /system/etc
Click to expand...
Click to collapse
Actually, don't delete either file.
Don't touch recovery-from-boot.p at all, and rename the sh.
If you want to be able to install otas in the future, renaming the patch file will break the MD5 check. The file is harmless if the sh file is out of commission.
DeezNotes said:
I'm not sure what you're doing wrong... but its something.
You shouldn't have to flash another boot loader. I'm not sure what you would gain from that with the phone being a nexus?
Flashing another recovery is necessary for flashing different roms, kernels, mods, root, etc.
If you are indeed flashing a different boot loader, may i ask why?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I'm trying another loader because nothing else works, the phone is stock and running 4.0.2. auto update causes it to crash and reboot.
Related
I'm not sure where to go from here, I rooted my Nexus, installed CWM, and everything was fine. Until my dumbass decided to reboot to recovery from ROM manager, didn't think it would hurt anything. Now, whenever I try to load recovery from my bootloader, the android pops up with the swirling ball for a second, then comes up an android laying down with a red triangle with an ! in it.
I tried factory reset, started from step 1, locked the bootloader and unlocked and rooted again. If I flash CWM, it will work the first time, but anytime after that my little hazardous android symbol pops up again unless I flash CWM again. I'm new to all this obviously, so any help would be very greatly appreciated. Thanks.
I would recommend just flashing a factory .img threw adb. That should do it.
Send, Finally From Lte Galaxy Nexus
I agree. This link helped me do it for mine just a few mins ago.
LTE Instructions:
https://plus.google.com/107538503004482952974/posts/K8wozE8zhzq
GSM Instructions:
http://forum.xda-developers.com/showthread.php?t=1373995
irb123 said:
I'm not sure where to go from here, I rooted my Nexus, installed CWM, and everything was fine. Until my dumbass decided to reboot to recovery from ROM manager, didn't think it would hurt anything. Now, whenever I try to load recovery from my bootloader, the android pops up with the swirling ball for a second, then comes up an android laying down with a red triangle with an ! in it.
I tried factory reset, started from step 1, locked the bootloader and unlocked and rooted again. If I flash CWM, it will work the first time, but anytime after that my little hazardous android symbol pops up again unless I flash CWM again. I'm new to all this obviously, so any help would be very greatly appreciated. Thanks.
Click to expand...
Click to collapse
You're not bricked. Flash CWM and then use Root Explorer or another file browser and navigate to /system and delete reboot-from-recovery.p
You will now be able to boot into recovery.
Awesome thanks for the replies you guys are great. The ordeal ended up causing my phone to reject the sim card for some reason...just got back from Verizon. I'm trying the file manager route first but it's telling the file is read only?
Sent from my Galaxy Nexus using XDA App
Nevermind...hit the r/w...like I said...noob. Checking recovery now thanks again...
Sent from my Galaxy Nexus using XDA App
Andrew C said:
You're not bricked. Flash CWM and then use Root Explorer or another file browser and navigate to /system and delete reboot-from-recovery.p
You will now be able to boot into recovery.
Click to expand...
Click to collapse
What if I don't have the reboot-from-recovery.p file in my /system folder?
ironcx said:
What if I don't have the reboot-from-recovery.p file in my /system folder?
Click to expand...
Click to collapse
Follow the instructions for How to install CWM in this post. Once you've done that, you'll be able to find the reboot-from-recovery.p in /system. Just delete it and you'll be good.
I tried using the franco kernel app to install the kernel on my rooted Galaxy Nexus. There was the "download the .zip" option and the "we'll flash it for you" option. Of course I took the easy option which was probably stupid on my part. My phone downloaded the kernel and then rebooted. Now that it has rebooted... it wont get beyond the black screen that says "Google" and has the little open lock image at the bottom.
Questions:
Has anyone seen this?
Did I brick this thing (I really hope not)?
What steps can I do to try to get it back working?
Or does it just take a long time 20+ minutes to download/install/whatever once it reboots?
patriot95 said:
I tried using the franco kernel app to install the kernel on my rooted Galaxy Nexus. There was the "download the .zip" option and the "we'll flash it for you" option. Of course I took the easy option which was probably stupid on my part. My phone downloaded the kernel and then rebooted. Now that it has rebooted... it wont get beyond the black screen that says "Google" and has the little open lock image at the bottom.
Questions:
Has anyone seen this?
Did I brick this thing (I really hope not)?
What steps can I do to try to get it back working?
Or does it just take a long time 20+ minutes to download/install/whatever once it reboots?
Click to expand...
Click to collapse
i think that flash a new rom would solve this
patriot95 said:
I tried using the franco kernel app to install the kernel on my rooted Galaxy Nexus. There was the "download the .zip" option and the "we'll flash it for you" option. Of course I took the easy option which was probably stupid on my part. My phone downloaded the kernel and then rebooted. Now that it has rebooted... it wont get beyond the black screen that says "Google" and has the little open lock image at the bottom.
Questions:
Has anyone seen this?
Did I brick this thing (I really hope not)?
What steps can I do to try to get it back working?
Or does it just take a long time 20+ minutes to download/install/whatever once it reboots?
Click to expand...
Click to collapse
I did this last night to see, and it didn't work. I had to pull the battery, and reboot. I then just downloaded the new zip, and rebooted into Recovery to flash it as I normally would.
I wanted to do this... but with my root toolkit it looks like my phone doesn't have usb debugging on (which it was before I tried to flash this kernel). And I can't turn my phone on to turn it on... so hmm.
RMarkwald said:
I did this last night to see, and it didn't work. I had to pull the battery, and reboot. I then just downloaded the new zip, and rebooted into Recovery to flash it as I normally would.
Click to expand...
Click to collapse
This is what I want to do. Is I pull the battery and restart... I'm still stuck at the same screen though.
patriot95 said:
This is what I want to do. Is I pull the battery and restart... I'm still stuck at the same screen though.
Click to expand...
Click to collapse
Pull the battery, hold Vol Up/Vol Down/Power to get into Recovery. Do you have the ROM zip file or another kernel on your SD card? You could just re-flash the ROM zip file over your existing installation, which would leave your data alone and install the ROM's kernel. Wipe /cache and Dalvik Cache before flashing.
EDIT: When you get into the bootloader, hit Vol Up until Recovery shows up, then hit the Power button to boot to Recovery.
RMarkwald said:
Pull the battery, hold Vol Up/Vol Down/Power to get into Recovery. Do you have the ROM zip file or another kernel on your SD card? You could just re-flash the ROM zip file over your existing installation, which would leave your data alone and install the ROM's kernel. Wipe /cache and Dalvik Cache before flashing.
EDIT: When you get into the bootloader, hit Vol Up until Recovery shows up, then hit the Power button to boot to Recovery.
Click to expand...
Click to collapse
This is KIND of what I'm doing. I can't access my phone from the computer because of the damn usb thing... but I'm going to try to flash back to stock and see if that works.
It's booting now and it's been on the start screen for a minute or two. How long should it take on a stock flash? Just curious how long to wait before yanking the battery and trying again.
How did you flash stock, using fastboot or a zip? These are the stock images correct?
I boot into Recovery Mode and did the factory reset.
I also have a su.zip on my sdcard that I think is the rooted image that was used when I used the WugFresh root toolkit. But I'm not sure.
Shouldn't the Factory Reset... do a Factory Reset?
Edit: I see it's just data not an actual factory reset as I am thinking.
patriot95 said:
I boot into Recovery Mode and did the factory reset.
I also have a su.zip on my sdcard that I think is the rooted image that was used when I used the WugFresh root toolkit. But I'm not sure.
Shouldn't the Factory Reset... do a Factory Reset?
Edit: I see it's just data not an actual factory reset as I am thinking.
Click to expand...
Click to collapse
If you don't have a ROM or kernel zip file on your SD card, you'll want to put one there. Factory Reset already reset any data you have, so you'll want to flashing a ROM would be recommended here.
You can use ADB to push files to your SD card. You'll need to get into Recovery, mount /data (which is under Mounts and Storage menu), then open a command prompt window and change directories to your Android SDK folder, specifically Platform-tools. Then use ADB to push the zip files to your SD card:
adb push <name of file>.zip /data/media
EDIT 2: You'll want to download and put the zip file in your SDK - Platform-tools folder before you use ADB to push it there.
You can then flash the ROM via Install file from SD card.
Does this make sense?
EDIT: The su.zip is just to get root access, not a full ROM zip.
RMarkwald said:
If you don't have a ROM or kernel zip file on your SD card, you'll want to put one there. Factory Reset already reset any data you have, so you'll want to flashing a ROM would be recommended here.
You can use ADB to push files to your SD card. You'll need to get into Recovery, mount /data (which is under Mounts and Storage menu), then open a command prompt window and change directories to your Android SDK folder, specifically Platform-tools. Then use ADB to push the zip files to your SD card:
adb push <name of file>.zip /data/media
You can then flash the ROM via Install file from SD card.
Does this make sense?
EDIT: The su.zip is just to get root access, not a full ROM zip.
Click to expand...
Click to collapse
It makes sense... but I'm a little new so I will try this. Might take me a while.
By the way... these captcha images suck.
Thank you for the help... I am re-rooting my phone now. I was able to get back to stock.
Good job, glad to help!
RMarkwald said:
Pull the battery, hold Vol Up/Vol Down/Power to get into Recovery.
EDIT: When you get into the bootloader, hit Vol Up until Recovery shows up, then hit the Power button to boot to Recovery.
Click to expand...
Click to collapse
I LOVE YOU!
(I did the same thing with the auto-flash kernel and was stuck. I totally forgot that you had to hold BOTH up/down with the power button.)
Franco's app SUCKS!
Thanks my man!!! :good:
BTW...Jelly Bean rocks!
Hello guys i have tha same problem with patriot95 (black screen Google and one small lock lower) ... my device is optimus 3d p920 and i cant reboot it .
can you help me ? PLz
This is a problem with the toolkit...
Do you have any adb and fastboot downloaded? No? Download it. There's more than enough instructions on that.
You didn't need to factory reset AT ALL. All you needed to do was just re-flash your ROM and you would've been good to go.
Next time learn how to use adb and fastboot command please. Then, there will be less chance of messing it up and not being able to fixing it.
Hi, sorry this thread is kinda old already but I don't really want to start new thread about same problem. So, similar to OP, I stupidly use the 'autoflash' option from franco app, and I'm stuck now. But I can still have access to CWM recovery. I was using the stock 4.2.2 takju before. I already tried to re-flash stock kernel -> fail. Tried re-flash stock rom - fail. Tried wipe cache and dalvik then flash deodexed 4.2.2 -> also fail. Please help me, I really need to use my phone right now.
Are you flashing a 4.2.2 kernel with a 4.2.2 ROM?
What ROM and kernel?
Sent from my Galaxy Nexus using xda premium
I flashed the stock 4.2.2 rom from the google website but it doesn't work. Then I tried the stock 4.2.2 from this link,
http://forum.xda-developers.com/showthread.php?t=1737849 but also failed.
I also flashed the stock kernel from this link
http://forum.xda-developers.com/showthread.php?t=2151154
Hey there
I'm currently working through the below process... on my Verizon CDMA LTE Galaxy Nexus runing 4.0.2 Stock.
http://strifejester.wordpress.com/2012/05/01/imm76k-direct-for-verizon-galaxy-nexus/
Also watched this Video (but he doesn't get the error)
http://www.youtube.com/watch?v=dQ1HuteSnDE
And when i get to the part about running mempodroid as sh I get an error that says the following:
Segmentation fault See the below screen shot.
Does anyone have any advice on how i can get past this? I have restart phone and desktop many times and happens every time. I have the PDAnet drivers installed and everything else adb seems to be working.
Would love some help,thanks in advance. Really want to get this working tonight if possible.
Conty
You are not developing anything
Moved to Q&A
FNM
Sent from my PantechP4100 using xda premium
Why would you temp root? Why not just temp boot to recovery, flash the superuser zip, and then restart. You'll be rooted, and if you don't want CWM installed, since it is only temp flashed, it'll disappear as soon as you restart.
imnuts said:
Why would you temp root? Why not just temp boot to recovery, flash the superuser zip, and then restart. You'll be rooted, and if you don't want CWM installed, since it is only temp flashed, it'll disappear as soon as you restart.
Click to expand...
Click to collapse
I'm just following the process for the 4.0.4 install. How else can i do what i need? I'm quite new to my Nexus, i had a bionic before.
Thanks
Need the temp root to run mempodroid i think, can i do this another way? i honestly don't know
If you are on stock 4.0.2 (ICL53F), download the 4.0.4 OTA update zip that is posted here somewhere and put it on the root of the internal sdcard. Restart your phone into recovery (should be stock recovery) and apply the update. It will verify the system and flash the update if everything checks out.
From there, if you want to be rooted too, download the superuser package from http://androidsu.com/superuser/ and put it on the internal sdcard (location doesn't matter). Use fastboot to temp boot to recovery, you'll need a custom recovery file for this (CWM, CWM Touch, TWRP, etc.). Run fastboot boot <recovery image file> and it will boot into recovery. Select the option to install a zip file, flash the superuser zip you downloaded, then restart and you should be on stock rooted.
imnuts said:
If you are on stock 4.0.2 (ICL53F), download the 4.0.4 OTA update zip that is posted here somewhere and put it on the root of the internal sdcard. Restart your phone into recovery (should be stock recovery) and apply the update. It will verify the system and flash the update if everything checks out.
From there, if you want to be rooted too, download the superuser package from http://androidsu.com/superuser/ and put it on the internal sdcard (location doesn't matter). Use fastboot to temp boot to recovery, you'll need a custom recovery file for this (CWM, CWM Touch, TWRP, etc.). Run fastboot boot <recovery image file> and it will boot into recovery. Select the option to install a zip file, flash the superuser zip you downloaded, then restart and you should be on stock rooted.
Click to expand...
Click to collapse
Which CWM version do i want and will this include the radios if i do it this way, sorry kinda newb at this phone. very different to my bionic.
Thanks so much for your help tho
Eidt
I got into stock recovery and saw the android with the explanation point but when i click Volume up + power i get no menu...
I'm off to bed will check back in the morning and see if you have any ideas, thanks again for the help
Finally got the stock recovery to work, however it only allows flashing from ./cache and i cant get my update.zip to cache without root right?
So decided to just unlock bootloader and then it let me root and push to ./cache and then i flashed the update.zip
All seems to be working now.
Thanks for all the help
I love the fact its so easy to unlock and lock the bootloader. very happy with that lol
is there a way to re root the phone once its on 4.0.4 IMM76K ? as the Galaxy Nexus toolkit stops at IMM30B...
Thanks
Nevermind
Adrynalyne saved the day once again
http://www.droid-life.com/2012/02/06/how-to-root-android-4-0-4-on-the-galaxy-nexus/
Thanks Adrynalyne
I just rooted my phone everything seemed to go the way its supposed to. I have superuser and have downloaded titanium backup and it works fine. I wanted to back up my phone so I can have a stock back up but when I went into fast boot and tries to access clockwork I got the android on his back with the red exclamation mark. I'm not sure what happened. I was able to access it once. Maybe a reboot did something. I'm not new to rooting but I'm new to the galaxy line. Thanks so much for any help its appreciated geeatley.
I rooted using the dev kit v7.0 I'd that helps any.
cyaiphone said:
I just rooted my phone everything seemed to go the way its supposed to. I have superuser and have downloaded titanium backup and it works fine. I wanted to back up my phone so I can have a stock back up but when I went into fast boot and tries to access clockwork I got the android on his back with the red exclamation mark. I'm not sure what happened. I was able to access it once. Maybe a reboot did something. I'm not new to rooting but I'm new to the galaxy line. Thanks so much for any help its appreciated geeatley.
I rooted using the dev kit v7.0 I'd that helps any.
Click to expand...
Click to collapse
Nexus line.
have you tried reflashing cwm recovery via fastboot?
flash CWM via fastboot.
and why do you need a backup of stock? You can always re-flash the stock images to go back to completely stock. Restoring a rooted nandroid backup won't put you back to stock anyways...
OK makes sense. Is there a how to and link to the cwm download? On HTC you used to just download the file rename it pc86img and reboot into fast boot and let it update. Is it the same for the nexus?
cyaiphone said:
OK makes sense. Is there a how to and link to the cwm download? On HTC you used to just download the file rename it pc86img and reboot into fast boot and let it update. Is it the same for the nexus?
Click to expand...
Click to collapse
Similar, except you put it in a folder on your PC and flash it over USB with the command line.
martonikaj said:
Similar, except you put it in a folder on your PC and flash it over USB with the command line.
Click to expand...
Click to collapse
Crap is there a how to any how to do this? I've never used adb or command prompts.
cyaiphone said:
Crap is there a how to anywherebonnhow to do this? I've never used adb or command prompts.
Click to expand...
Click to collapse
Go here: http://forum.xda-developers.com/showthread.php?t=1529058
And look for the "Setting up ADB for our device:" then "Obtaining Root Access and Custom Recovery:".
Can you boot into the OS? If you can, download Rom Manager from the Play Store and use that to install CWM Recovery.
Did you delete recovery-from-boot.p from /system? I had to do this to "permanently" install the recovery. My first Samsung phone, my first Nexus device, so not sure if this has been a regular thing ... never had to "permanently" install a recovery up until then. That fixed my issue as my recovery was only sticking once per boot ... was blowing my mind for a couple hours.
Not sure if root via toolkit solves this, but I did a manny root and had to do this. Hope it helps.
edit-
- remount /system in read/write mode (use something like the Root Explorer app or ES File Explorer; both have root modes (check the app's settings) for remounting /system as writable)
- rename the /system/recovery-from-boot.p to /system/recovery-from-boot.p-bak
(note: you could delete it, but renaming is much safer since its easily reversible)
Click to expand...
Click to collapse
Could also, apparently, rename it. I just reinstalled recovery, deleted, and haven't had a single problem since.
What bleedblue said; now go into fastboot, and reflash cwm.
Sent from my i9250
I just got an HTC one from Best Buy Mobile (Verizon) yesterday. Turned S-Off using runrunner. Verified root but can not access recovery. I had the same issue with a S4 but it was a known issue for all that has updated to the 4.3.
I have tried all the suggestions in flashing TWRP. I am wondering if this is a Verizon related issue? Maybe they are putting something on their phones to prevent recovery?
HELP!!!!
Something is really jacked up with my phone. It kept saying Unfortunately Amazon has stopped. Over and over again. So I gave up and went to do a factory restore and data wipe. I first went to Super user and removed permanent root. I then tried to do a factory wipe through settings/backup & reset reset phone. It still gave me issues trying to enter recovery mode. It would get hung up and then reboot to a sort of safe mode version of the OS. (with a red disclaimer at the bottom). Then I tried to do factory reset by holding the volume down and power. Its doing the same thing. At this point I don't are about root I just want a working phone.
Any suggestions?
Flash twrp from the xda thread here and then flash arom. What exactly are you doing to flash it?
Sent from my One using xda app-developers app
I have tried flashing a recovery. Now I dont have root and cant do anything. It will not let me even upgrade firmware. I tried to get it back to stock. My recovery is jacked up.
adodson927 said:
I have tried flashing a recovery. Now I dont have root and cant do anything. It will not let me even upgrade firmware. I tried to get it back to stock. My recovery is jacked up.
Click to expand...
Click to collapse
OK, so you are s-ff, is your bootloader unlocked?
IF you are not on stock recovery YOU CANNOT run an update
I'm s-off bootloader unlocked. I have no recovery. Not even stock.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
adodson927 said:
I'm s-off bootloader unlocked. I have no recovery. Not even stock.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
.. you have to have a recovery..
I think?
can you successfully fastboot flash a custom recovery? If not can you fastboot the stock recovery..?
To be completely honest, I would just run the RUU. should fix you right up
You could boot into RUU and flash the decrypted stock rom zip to get back to straight stock. The zip reflashes stock recovery. I don't see why that wouldn't work.
Edit: Oops. Didn't even notice andy just recommended the same thing lol. My fault.
adodson927 said:
I'm s-off bootloader unlocked. I have no recovery. Not even stock.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thats odd, i thought you had to have a recovery of some kind.
Here is what I would do:
Lets try Flashing CWM instead of TWRP in fastboot I will post it, and I will also post the stock recovery there to as well.
https://www.dropbox.com/s/kk2esdrx1g1b50p/recovery-clockwork-touch-6.0.4.5-m7vzw.img
the image is easily installed via an unlocked bootloader with the following command:
fastboot flash recovery imagename.img
in this case: fastboot flash recovery recovery-clockwork-touch-6.0.4.5-m7vzw.img
See if it actually takes, and report back any errors.
If for some reason it does not, try booting into bootloader/fastboot then push the stock recovery:
https://www.dropbox.com/s/hgzgq84svzahvnv/htconerecovery_signed.img
Hopefully that will at least take and try to push CWM again , reboot bootloader and reboot into recovery . I am hoping that does it for you.
Go here: http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip and dump SU on the root of your SD card and flash the SU.
I have seen people have all kind of weird issues with rum runner and I am just glad i had the official java card method used on mine. I also tend to just use a stock ROM which is just de-bloated.
Anyways I have used Santod040 roms in case i need to go back to pure stock ROM only: http://forum.xda-developers.com/showthread.php?t=2485319
You will need the odex one to run any OTA
The firmware is a different thing to flash.
here are the checksums:
htconerecovery_signed.img
MD5: E3F5208454689BE7F09835D4A60953A8
SHA-1: 1B0734D97732039528159AD1409AFEE858B5E9F1
SHA3-256: E0741EB77E5DEBEA932EE74F374FAC9E1037776178944279E8B12832C30E2546
recovery-clockwork-touch-6.0.4.5-m7vzw.img
MD5: 21A386CB920C485844E3BE0727351838
SHA-1: 312350D7383850915A648E2060AA2FC72B5EA08F
SHA3-256: 78B0C42CD62D3EB2B18BF62B544FC86878A56199DB96D13F26EA65663A822932
Thanks guys!
I was able to install TWRP and also Superuser.
Here are the instructions I used. Maybe they will help someone else like me.
Power off your device, then press and hold Power and Volume Down until you're in the bootloader menu. Highlight FASTBOOT and press Power. You should see Fastboot USB highlighted in red.
Download the latest version of TWRP for your phone and carrier. Rename file to twrp.img.
Open a command prompt on your computer and navigate to your SDK directory. Type "fastboot flash recovery twrp.img" and hit Enter.
Then I backed up my stock rom using TWRP
In TWRP's main menu, tap Reboot. It will tell you that you're not rooted and ask you to install SuperSU, so swipe to confirm. When you reboot your phone, you should see a notification that you need to install the SuperSU app. Open the notification and select TWRP, since the app from Google Play only works with S-OFF.
Worked flawlessly.
I installed NuSenseONE max and I love it so far.
adodson927 said:
Thanks guys!
I was able to install TWRP and also Superuser.
Here are the instructions I used. Maybe they will help someone else like me.
Power off your device, then press and hold Power and Volume Down until you're in the bootloader menu. Highlight FASTBOOT and press Power. You should see Fastboot USB highlighted in red.
Download the latest version of TWRP for your phone and carrier. Rename file to twrp.img.
Open a command prompt on your computer and navigate to your SDK directory. Type "fastboot flash recovery twrp.img" and hit Enter.
Then I backed up my stock rom using TWRP
In TWRP's main menu, tap Reboot. It will tell you that you're not rooted and ask you to install SuperSU, so swipe to confirm. When you reboot your phone, you should see a notification that you need to install the SuperSU app. Open the notification and select TWRP, since the app from Google Play only works with S-OFF.
Worked flawlessly.
I installed NuSenseONE max and I love it so far.
Click to expand...
Click to collapse
how else were you trying to flash a recovery ?!?
Goo.im app as well as ROM Manager, ROM Toolbox can flash recoveries. I've notice there isn't much compatibility with the m7vzw though. You can also use terminal command's from the device. All of these require root access though.
Sent from my One using XDA Premium 4 mobile app
Hey everyone, so my problem is that i did run rumrummer the way it said on the directions and i double checked my rom version type countless times. It says that i am unlocked and s-off, but i cant access recovery. I tried flashing recovery with fastboot command prompt, and still no luck. It gives me a "error: cannot open 'open.img', I navigated to the folder that it is located in and executed the command properly every time. I also dont know how to flash superuser using flashboot, so any help will be very much appreciated. Also I'm kinda new to rooted, I have some experience from a few years back, but dont remember everything.
Jo5ton1018 said:
Hey everyone, so my problem is that i did run rumrummer the way it said on the directions and i double checked my rom version type countless times. It says that i am unlocked and s-off, but i cant access recovery. I tried flashing recovery with fastboot command prompt, and still no luck. It gives me a "error: cannot open 'open.img', I navigated to the folder that it is located in and executed the command properly every time. I also dont know how to flash superuser using flashboot, so any help will be very much appreciated. Also I'm kinda new to rooted, I have some experience from a few years back, but dont remember everything.
Click to expand...
Click to collapse
place the name.img file in the same folder as the adb and fastboot executables, open command prompt as administrator for that directory, then type "fastboot flash recovery name.img" substitute name.img for the actual name of the file including extension and make sure there are no quotes around it. also, use "fastboot devices" or "adb devices" to make sure your phone is being recognized.
I got it to work, finally. Thanks for the reply pointedge. I beat u to it earlier in the day and forgot to post up again that I got it. It was like u said, I just had the file in the wrong folder.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
nrfitchett4 said:
how else were you trying to flash a recovery ?!?
Click to expand...
Click to collapse
I'm willing to bet he flashed the wrong recovery. It's happened to a lot of people.