Related
Hi,
i found a simliar thread that was talking about a similar subject, but didn't answer my question. i have lost it and cant find that same thread for help.
rooted -flashed bad rom - everything keeps closing(apps, Google sync)--- cant get int to recovery mode because of error
****I unlocked bootloader and rooted my GalaxyNex. then installed ROM maneger. i flashed CWM,then backed up my ROM. i tested it by flashing my backed up ROM, after i had messed around and my phone went back to normal. i was feeling safe. i noticed that i was having trouble getting into the recovery mode because of the belly open with exclamation Point. i read that it is because CWM was losing permission? i found that i just had to re-flash CWM every time right before i go into recover mode. i flashed a ROM from ROM maneger and everything worked until i turned the phone on. i cant sync Google account, and basically all apps close immediately (no key board too). I cant get into recovery mode and i cant down load ROM maneger to try to re-flash CMW to restore from older ROM.
I am sorry if this is already been answered i have try to find my situation but i couldn't.
I tried to re-flash the clock work recover image through the terminal of my mac but it says permission denied... i guessing i need to find a way to re flash to stock from fastboot is this possible ?
Pull the battery and hold power + volume and get into fast boot. Flash stock images from here
Sent from my Galaxy Nexus using xda premium
joshnichols189 said:
Pull the battery and hold power + volume and get into fast boot. Flash stock images from here
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Thanks I got really lucky i was able to re flash Clock work recovery in fast boot with the command
./fastboot flash recovery recovery-clockwork-5.5.0.4-toro.img
then i was able to get into the proper recovery mode and re flash my backed up image.
if i wanted to re flash a original image would the terminal command look like this
./fastboot flash recovery "Imagename" ? i might have just got lucky but i am guessing thats how you re-flash something to your phone?
now that i have gotten back to the beginning, why is it that i have to re flash CMW every time to get in correct recovery mode? or how do i stop it from giving me the recovery error when trying to get to the correct recovery mode?
thanks again
Glad your good! Hate to see these threads but we all go through it sooner or later
Sent from my Galaxy Nexus using xda premium
billycurtis said:
now that i have gotten back to the beginning, why is it that i have to re flash CMW every time to get in correct recovery mode? or how do i stop it from giving me the recovery error when trying to get to the correct recovery mode?
thanks again
Click to expand...
Click to collapse
After you fastboot flash the CWM image, use ADB, a terminal, or a file explore to remove or rename the file /system/recovery-from-boot.p
I was attempting to unlock/root and long story short, now I have TWRP installed, and I can get to FASTBOOT but if i try to boot normally I get the Nexus logo, and no further. When I unlocked, I installed TWRP then loaded it. After leaving TWRP it said 'Seems you are not rooted, want to root"? or something to that effect. I clicked YES and now I'm stuck. Since I had just unlocked it, it *should* have reset my entire device(which was all stock anyway) so I am not sure what went wrong. I have been trying everything I know but I'm now out of ideas. Would appreciate any help. I see now that the version of SuperSu that it would have pushed would have been wrong, would that be preventing the tablet from booting?
If you can mount in fastboot you're not bricked. You tried to check md5 and push the recovery image again? And also try to throw new ROM on it.
Sent from my HTC One using xda app-developers app
ronni.rasmussen said:
If you can mount in fastboot you're not bricked. You tried to check md5 and push the recovery image again? And also try to throw new ROM on it.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
It wont boot so I don't know how to put anything on it, it's empty and doesn't show up in windows. Also I don't know what you meant exactly by push the recovery image again. Twrp is working fine. Sorry I am hardly a pro at this stuff.
Landara said:
It wont boot so I don't know how to put anything on it, it's empty and doesn't show up in windows. Also I don't know what you meant exactly by push the recovery image again. Twrp is working fine. Sorry I am hardly a pro at this stuff.
Click to expand...
Click to collapse
Try to get to fastboot and connect PC and check if it connects. You will need the USB drivers installed
Sent from my HTC One using xda app-developers app
ronni.rasmussen said:
Try to get to fastboot and connect PC and check if it connects. You will need the USB drivers installed
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Oh I can do that no problem, been using ADB. But now it just won't boot normally. But I can use the terminal and everything.
Landara said:
Oh I can do that no problem, been using ADB. But now it just won't boot normally. But I can use the terminal and everything.
Click to expand...
Click to collapse
Then it should be possible to flash and push recovery and ROM to device even get a stock image back.
Which recovery image did you install?
And did you flash any ROM or kernel?
Sent from my HTC One using xda app-developers app
Landara said:
Oh I can do that no problem, been using ADB. But now it just won't boot normally. But I can use the terminal and everything.
Click to expand...
Click to collapse
I would suggest you just restore your N7 back to stock. No need for root yet, seriously! But this should help get you going in the right direction.
Power it off completely. Hold Power + Volume down until it boots into the bootloader. Run the following commands:
fastboot devices (to confirm you are connected)
fastboot flash recovery recovery.img
If you haven't unlocked your N7 yet, run fastboot oem unlock first.
ronni.rasmussen said:
Then it should be possible to flash and push recovery and ROM to device even get a stock image back.
Which recovery image did you install?
And did you flash any ROM or kernel?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I put TWRP on there, immediately after unlocking. So it should have been completely stock since as far as I know it wipes it when you unlock. After putting TWRP on there, i told it to reboot normally(from within TWRP) and it detected that I was not rooted and asked me if I wanted to install SuperSu. I said yes and now it will not boot to the operating system. It boots fine to Bootloader and Recovery. And I am certain it's connected to my PC because I can even tell it ADB REBOOT BOOTLOADER/RECOVERY and that works. But I don't see how I can load a ROM onto it if I can't access it via windows. I don't know how to get a ROM onto the SD card. Surely there could be a way but I don't know it.
Landara said:
I put TWRP on there, immediately after unlocking. So it should have been completely stock since as far as I know it wipes it when you unlock. After putting TWRP on there, i told it to reboot normally(from within TWRP) and it detected that I was not rooted and asked me if I wanted to install SuperSu. I said yes and now it will not boot to the operating system. It boots fine to Bootloader and Recovery. And I am certain it's connected to my PC because I can even tell it ADB REBOOT BOOTLOADER/RECOVERY and that works. But I don't see how I can load a ROM onto it if I can't access it via windows. I don't know how to get a ROM onto the SD card. Surely there could be a way but I don't know it.
Click to expand...
Click to collapse
Start over by downloading recovery, Superuser and a clean stock rom image.
But before that you could try to reset all data in recovery (factory reset) and cache if you haven't tried.
http://forum.xda-developers.com/showthread.php?t=2380913
Thanks to this thread I have booted! Still have to root it but now that I know that you have to flash the NEW SuperSu not the one TWRP flashed for me, I shouldn't have a problem Thanks so much for your help everyone!
Landara said:
http://forum.xda-developers.com/showthread.php?t=2380913
Thanks to this thread I have booted! Still have to root it but now that I know that you have to flash the NEW SuperSu not the one TWRP flashed for me, I shouldn't have a problem Thanks so much for your help everyone!
Click to expand...
Click to collapse
Super
Hello! Hi, I'm kinda new to all of this, and I downloaded all of this today. I've been reading a lot and watching a lot of videos, yet I nothing really seems to fix my devices problem.
I have a HTC One on the Verizon carrier and I have just recently S-Off'd it using Rumrunner (I used the Rom checker to make sure it was unlocked and it even says it is whenever i enter bootloader). Although I was successfully able to unlock my device, I seem to have trouble with entering into recovery mode. Whenever I try to go into Recovery mode, my device reads "Entering Recovery mode" in pink at the top for about 10-20 seconds. Then all of a sudden it just goes black and it reboots as if I had never even chosen to go into recovery mode. I don't know if this holds any significance, but I've noticed that my boot up logo only has "HTC ONE" on it, the writing "simply beautiful" is now removed.
I have tried using cmd and ADB to clear the cache, I've tried using ClockManager from Rom Manager, and I've tried multiple times on regular mode. None of them really seem to work and I don't really understand why. Can anyone please offer me some suggestions? Thank you.
Seriously I only want a transparent theme for my HTC One that's all LOL
@Cinestra hey so I'm also kind of new to this but I can try to help. So what custom recovery did you flash?
Chilidog said:
@Cinestra hey so I'm also kind of new to this but I can try to help. So what custom recovery did you flash?
Click to expand...
Click to collapse
I think the person didn't flash one. Flash twrp through fastboot. Don't use ROM manager cwm is getting old
Sent from my HTC6500LVW using xda app-developers app
cstrife999 said:
I think the person didn't flash one. Flash twrp through fastboot. Don't use ROM manager cwm is getting old
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
Hello, thank you i very much appreciate your advice. I did not try flashing yet.
I just tried to flash TWRP by using Fastboot and the CMD. However I still get no luck. I entered everything in the command prompt fine and it responded nicely. However, whenever I try to go to Recovery mode, the screen just says "entering recovery mode...." and then just turns black 15 seconds later and reboots again :S
Cinestra said:
Hello, thank you i very much appreciate your advice. I did not try flashing yet.
I just tried to flash TWRP by using Fastboot and the CMD. However I still get no luck. I entered everything in the command prompt fine and it responded nicely. However, whenever I try to go to Recovery mode, the screen just says "entering recovery mode...." and then just turns black 15 seconds later and reboots again :S
Click to expand...
Click to collapse
Hmm... That is strange indeed...
Sent from my HTC6500LVW using xda app-developers app
I had the same problem and discovered that when i enter stock recovery, when the black screen appears, i had to press power+vol up to get it to show up. You may have to press them several times to get the timing right. Hope that helps!
cstrife999 said:
I think the person didn't flash one. Flash twrp through fastboot. Don't use ROM manager cwm is getting old
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
when I got my phone back from sonic, twrp wouldn't install for me so I had to use CWM.
OP should probably try both and make sure he's following the instructions here:
http://forum.xda-developers.com/showpost.php?p=45513789&postcount=2
I'm quite new to rooting as well. Seems we are having the same problem. I was able to get beaups' s-off exploit to work without any problems. When I load into HBoot it says the phone is unlocked and I've also used a Root Checker to determine the phone is rooted.
My next step was to try and install TWRP using fastboot. I ran a command prompt window using administrator rights during the whole process. Everything seemed to install just as it should. The problem is when I try to boot into recovery I'm having the same problem as Cinestra. I simply get the HTC logo screen with "Entering Recovery..." in pink letters at the top of the screen for around 15 seconds, then it reboots as if it would normally and restart the phone as usual. I have tried to reinstall the custom recovery step by step, using 'fastboot erase cache' before and after as well as using an older version of TWRP just in case that would help. Again, everything seems to install just fine but I still can not boot into recovery. I've also tried to see if the GooManager app would be of some help, but that is also not working for me.
I've since also tried flashing CWM but the same situation occurs. Install seems fine but no luck booting into recovery. ROM Manager was a no go as well.
I just can't figure this out. I've tried different cables, deleted and reinstalled HTC drivers/adb/fastboot, and multiple recovery images. I just gave beasleyj62's suggestion of holding down the power/volume down buttons after it goes to black when it starts to restart but that just put me into a bootloop sadly. Had to hold down the power button a few times to get it to boot correctly again. Any help on this would be greatly appreciated. Cheers.
I would also just like to add a little more info on my device in case this will help troubleshoot this. I'm using a Verizon HTC One with Software Number 1.10.605.10.
Same problem here. Tried flashing from fastboot, using goomanager, using rom manager, and from within the terminal emulator (can't find the command now but i think it was on the TWRP site).
Fastboot gives every indication it works, goomanager and rom manager give an error, and the emulator method appeared to work.
Tried to fastboot both TWRP and clockworkmod but neither worked.
At work right now but still investigating...
*edit: goomanager error states 'no recoveries found for your device.'
carassius-one said:
Same problem here. Tried flashing from fastboot, using goomanager, using rom manager, and from within the terminal emulator (can't find the command now but i think it was on the TWRP site).
Fastboot gives every indication it works, goomanager and rom manager give an error, and the emulator method appeared to work.
Tried to fastboot both TWRP and clockworkmod but neither worked.
At work right now but still investigating...
*edit: goomanager error states 'no recoveries found for your device.'
Click to expand...
Click to collapse
ROM manager and goomanager are not supported you have to flash Twrp or CWM via fastboot
Sent from my HTC6500LVW using XDA Premium 4 mobile app
---------- Post added at 09:58 AM ---------- Previous post was at 09:54 AM ----------
I wonder if you guys are having problems because you tried to use rom manager or goomanager and it messed something up...
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Chilidog said:
ROM manager and goomanager are not supported you have to flash Twrp or CWM via fastboot
Click to expand...
Click to collapse
Thanks. That answers that part of the question.
Chilidog said:
ROM manager and goomanager are not supported you have to flash Twrp or CWM via fastboot
Sent from my HTC6500LVW using XDA Premium 4 mobile app
---------- Post added at 09:58 AM ---------- Previous post was at 09:54 AM ----------
I wonder if you guys are having problems because you tried to use rom manager or goomanager and it messed something up...
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Didn't realize they weren't supported. Sadly, I don't think they are the culprit here. I tried to flash using fastboot first. I attempted it with 'openrecovery-twrp-2.6.3.0-m7.img' first then with the older version 'openrecovery-twrp-2.6.1.0-m7.img' next. It was the same issue with both. I didn't attempt using GooManager until after I had used fastboot, though GooManager just failed to initialize the install. I mean it didn't even run or change anything as far as I can tell, and simply gave an error back saying "No recoveries were found for your advice".
Did the same thing with CWM and ROM Manager. I installed CWM from fastboot. Only after seeing the same thing happen when I tried to install TWRP did I give ROM Manager a shot. This also just gave an error message without initializing any install. Thanks for the input though.
Prizm432 said:
Didn't realize they weren't supported. Sadly, I don't think they are the culprit here. I tried to flash using fastboot first. I attempted it with 'openrecovery-twrp-2.6.3.0-m7.img' first then with the older version 'openrecovery-twrp-2.6.1.0-m7.img' next. It was the same issue with both. I didn't attempt using GooManager until after I had used fastboot, though GooManager just failed to initialize the install. I mean it didn't even run or change anything as far as I can tell, and simply gave an error back saying "No recoveries were found for your advice".
Did the same thing with CWM and ROM Manager. I installed CWM from fastboot. Only after seeing the same thing happen when I tried to install TWRP did I give ROM Manager a shot. This also just gave an error message without initializing any install. Thanks for the input though.
Click to expand...
Click to collapse
Yeah...I tried the fastboot method first too, for both TWRP and CWM. I really doubt that is the problem.
Two thoughts:
1. Did you have any issues during the S-OFF? How many pours did it take? My thoughts here are that the S-OFF wasn't, for whatever reason, fully clean, which may suggest that you relock and S-ON your phone, and reapply Rumrunner.
2. Did you flash with the decrypted RUU? I would flash the phone with that (the link is somewhere in this subforum) and then try to flash a recovery image.
carassius-one said:
Yeah...I tried the fastboot method first too, for both TWRP and CWM. I really doubt that is the problem.
Click to expand...
Click to collapse
godhamba said:
Two thoughts:
1. Did you have any issues during the S-OFF? How many pours did it take? My thoughts here are that the S-OFF wasn't, for whatever reason, fully clean, which may suggest that you relock and S-ON your phone, and reapply Rumrunner.
2. Did you flash with the decrypted RUU? I would flash the phone with that (the link is somewhere in this subforum) and then try to flash a recovery image.
Click to expand...
Click to collapse
1. I think it was 3 or 4 pours. Seemed to work flawlessly.
2. Still trying to learn which includes learning what an ruu is. Maybe that is my problem. I ran rumrunner and then have been trying to flash a recovery ever since...with no other steps.
godhamba said:
Two thoughts:
1. Did you have any issues during the S-OFF? How many pours did it take? My thoughts here are that the S-OFF wasn't, for whatever reason, fully clean, which may suggest that you relock and S-ON your phone, and reapply Rumrunner.
2. Did you flash with the decrypted RUU? I would flash the phone with that (the link is somewhere in this subforum) and then try to flash a recovery image.
Click to expand...
Click to collapse
1. Nope, I had no issues while doing the S-Off. It took 3 pours for me.
2. I haven't used any RUU for this. So you suggest going back to S-On and locked, then using the RUU? Sorry, still new to the whole process so just want to be clear on procedure. Yeah, I've been considering going back to complete stock and starting from scratch again. I'll give that a go later tonight if I can't come up with anything else.
Thanks.
No, no. The only RUU available is a decrypted one, which can only be flashed while S-OFF. So the ideas I put down were distinct, and not steps. My thought is that either (i) you return yourself to full stock and non-root as is explained in a thread in this subforum, or alternatively, (ii) flash the RUU to get a fully untouched setup (the RUU contains the factory "rom", bootloader and recovery and will return it to being fresh from the factory) on the device and then flash the recovery.
Prizm432 said:
1. Nope, I had no issues while doing the S-Off. It took 3 pours for me.
2. I haven't used any RUU for this. So you suggest going back to S-On and locked, then using the RUU? Sorry, still new to the whole process so just want to be clear on procedure. Yeah, I've been considering going back to complete stock and starting from scratch again. I'll give that a go later tonight if I can't come up with anything else.
Thanks.
Click to expand...
Click to collapse
Cinestra said:
I just tried to flash TWRP by using Fastboot and the CMD. However I still get no luck. I entered everything in the command prompt fine and it responded nicely. However, whenever I try to go to Recovery mode, the screen just says "entering recovery mode...." and then just turns black 15 seconds later and reboots again :S
Click to expand...
Click to collapse
I had the same problem and yesterday I posted my fix in this Forum's TWRP thread.
I had been using
openrecovery-twrp-2.6.3.0-m7.img
What I really needed was
openrecovery-twrp-2.6.3.0-m7vzw.img
Go here: http://goo.im/devs/Flyhalf205/M7VZW/openrecovery-twrp-2.6.3.0-m7vzw.img
beasleyj62 said:
I had the same problem and discovered that when i enter stock recovery, when the black screen appears, i had to press power+vol up to get it to show up. You may have to press them several times to get the timing right. Hope that helps!
Click to expand...
Click to collapse
Thanks for your solution, unfortunately though, it doesn't seem to work.
jpradley said:
I had the same problem and yesterday I posted my fix in this Forum's TWRP thread.
I had been using
openrecovery-twrp-2.6.3.0-m7.img
What I really needed was
openrecovery-twrp-2.6.3.0-m7vzw.img
Click to expand...
Click to collapse
Hmm alright so you suggest flash this other version of TWRP instead? That would make sense because the link looks like it's specialized for Verizon. I will try that out today!
godhamba said:
Two thoughts:
1. Did you have any issues during the S-OFF? How many pours did it take? My thoughts here are that the S-OFF wasn't, for whatever reason, fully clean, which may suggest that you relock and S-ON your phone, and reapply Rumrunner.
2. Did you flash with the decrypted RUU? I would flash the phone with that (the link is somewhere in this subforum) and then try to flash a recovery image.
Click to expand...
Click to collapse
1. It took me about 3 pours. That is an interesting thought and I think it may very well be valid, but I would prefer not to reset or relock my device though.
2. I have not decrypted RUU yet because I was unfamiliar with the term. I may try this if the new TWRP code does not work
@Prizm432 it looks like you are flashing the wrong Twrp zip. It has to end in m7vzw.zip
Sent from my HTC6500LVW using XDA Premium 4 mobile app
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.
Hey guys, new to the forum and am looking for some guidance here. I've had my LGOG going great with CM11 and one day I put it on the charger when the battery got down to 1%. The next morning I grabbed my phone and it was off and refused to turn on. I was able to get it on by holding volume up + power and plugging it into a charger or PC but only when it was plugged in. I replaced the battery already to rule that part out. So now i've followed this guide and everything went fine,I flashed Teenybin SBLunlockhttp://forum.xda-developers.com/showthread.php?t=2230106. Only thing is for some reason i cannot boot into recovery mode, fastboot and download mode work fine but when i choose recovery from fastboot the phone shows a google logo and a small lock on the bottom of the screen and then turns off and show's the charging icon. I've been at it for hours and cannot get into recovery to flash a new rom.
My question for yall is am I wasting my time with this? I'm still not convinced that this is not a hardware failure since nothing on the phone works unless plugged into power. Any thoughts would help a ton otherwise i'll have to just cough up the cash for a new one. Thanks in advance guys.
Nex
nextelhalo said:
Hey guys, new to the forum and am looking for some guidance here. I've had my LGOG going great with CM11 and one day I put it on the charger when the battery got down to 1%. The next morning I grabbed my phone and it was off and refused to turn on. I was able to get it on by holding volume up + power and plugging it into a charger or PC but only when it was plugged in. I replaced the battery already to rule that part out. So now i've followed this guide and everything went fine,I flashed Teenybin SBLunlockhttp://forum.xda-developers.com/showthread.php?t=2230106. Only thing is for some reason i cannot boot into recovery mode, fastboot and download mode work fine but when i choose recovery from fastboot the phone shows a google logo and a small lock on the bottom of the screen and then turns off and show's the charging icon. I've been at it for hours and cannot get into recovery to flash a new rom.
My question for yall is am I wasting my time with this? I'm still not convinced that this is not a hardware failure since nothing on the phone works unless plugged into power. Any thoughts would help a ton otherwise i'll have to just cough up the cash for a new one. Thanks in advance guys.
Nex
Click to expand...
Click to collapse
Your battery was probably fine so I would keep it around. That just seems to happen sometimes.
The recovery that teenybins installs is not CM11 compatable. So you need to install a KK recovery, or ADB sideload a Stockish ROM.
For ADB sideload to install a Stockish Rom go here. http://forum.xda-developers.com/showthread.php?p=36270473
To install a recovery through fastboot, DL it from here. http://downloads.codefi.re/shelnutt2/freegee/LG-LS970/ These are for KK
And to install it using fastboot.
fastboot erase recovery
fastboot flash recovery recovery.img
You may need to do a factory reset to get it to boot.
---------- Post added at 06:06 AM ---------- Previous post was at 05:56 AM ----------
Forgot to tell ya, just pull the recovery image from the zip and use it with fastboot.
engine95 said:
Your battery was probably fine so I would keep it around. That just seems to happen sometimes.
The recovery that teenybins installs is not CM11 compatable. So you need to install a KK recovery, or ADB sideload a Stockish ROM.
For ADB sideload to install a Stockish Rom go here. http://forum.xda-developers.com/showthread.php?p=36270473
To install a recovery through fastboot, DL it from here. http://downloads.codefi.re/shelnutt2/freegee/LG-LS970/ These are for KK
And to install it using fastboot.
fastboot erase recovery
fastboot flash recovery recovery.img
You may need to do a factory reset to get it to boot.
---------- Post added at 06:06 AM ---------- Previous post was at 05:56 AM ----------
Forgot to tell ya, just pull the recovery image from the zip and use it with fastboot.
Click to expand...
Click to collapse
Thanks for the reply, this helped me get along with ADB and SDK but i'm still not clear on it. I've got the recovery image needed and ADB running but not sure how to flash the recovery image to the phone. I tried following the guide in the link you provided but it wants you to get into recovery mode on the phone and enable ADB mode but I cant get into my recovery on the phone. Problem. Again though thanks for you help, much appreciated. This learning process brings me back to my days of modding the old Xbox.
So just thinking about your last post, did you recommend installing a stock rom first and then try to install the new recovery image? I am able to put the phone into download mode and i've used LGNPST to push a full stock ZVB rom to it, seemed to work but I didnt know if that was the right way to go and flashed the Teenybin SBL unlock again.
nextelhalo said:
Thanks for the reply, this helped me get along with ADB and SDK but i'm still not clear on it. I've got the recovery image needed and ADB running but not sure how to flash the recovery image to the phone. I tried following the guide in the link you provided but it wants you to get into recovery mode on the phone and enable ADB mode but I cant get into my recovery on the phone. Problem. Again though thanks for you help, much appreciated. This learning process brings me back to my days of modding the old Xbox.
So just thinking about your last post, did you recommend installing a stock rom first and then try to install the new recovery image? I am able to put the phone into download mode and i've used LGNPST to push a full stock ZVB rom to it, seemed to work but I didnt know if that was the right way to go and flashed the Teenybin SBL unlock again.
Click to expand...
Click to collapse
You said you had fastboot. So you can use fastboot to load the kk recovery using those commands. If unsure just google it. Lots of info on fastboot.
As for sideload that was just to get a stock ROM on your SD.
If you lgnpst zvb then your phone should boot up and needs to update to zvc before you do anything else.
But if you flashed teenybins then you should have recovery and be able to flash the kk recovery. Power+ vol up gets recovery. Dn twice on vol button, then power gets you to recovery.
Check the FAQ and root guide. All this info is in there if it's confusing.
Sent from my LG-LS970 using XDA Premium 4 mobile app
engine95 said:
You said you had fastboot. So you can use fastboot to load the kk recovery using those commands. If unsure just google it. Lots of info on fastboot.
As for sideload that was just to get a stock ROM on your SD.
If you lgnpst zvb then your phone should boot up and needs to update to zvc before you do anything else.
But if you flashed teenybins then you should have recovery and be able to flash the kk recovery. Power+ vol up gets recovery. Dn twice on vol button, then power gets you to recovery.
Check the FAQ and root guide. All this info is in there if it's confusing.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I got ya, so I'm making sense of it all after a bit and I have more info if it helps. I've been able to get ZVB on there (via LGNPST) and i'll update to ZV9 just in case yet no matter what i do i cannot get recovery to boot. I get into fastboot and choose Recovery ( locked and unlocked) but when i hit the power button to choose recovery I get nothing, it shuts down. I'll keep at it and give a progress report if I make any.
UPDATE: Ok so I can only access (on phone) Fastboot when i flash one of the Teenybin files. The stock ZV9 and ZVB just show me the LG logo and go back to the battery icon. So, I flashed teenybin SBL unlock again got the phone into fastboot. I opened a terminal on my PC with ADB running and my phone in Fastboot connected to my PC (LG Drivers installed). When i choose adb sideload recovery.img and it says "device not found". Still working on it but havent gotten past this yet.
Im still wondering if there is hardware failure since I flashed ZVB and the phone still will not boot up period unless it's connected to PC/charger.
Do this then. Grab the zvc bin from the root guide. That is the most current and it has the right modem. Zvb and zv9 have the wrong modem.
Also it sounds like you have stock recovery. Which you will if your using zv? bins.
Then after using zvc bin, use teeny bin. That'll get you to twrp recovery. In twrp flash the kk recovery and you should be good to go.
Sent from my LG-LS970 using XDA Premium 4 mobile app
engine95 said:
Do this then. Grab the zvc bin from the root guide. That is the most current and it has the right modem. Zvb and zv9 have the wrong modem.
Also it sounds like you have stock recovery. Which you will if your using zv? bins.
Then after using zvc bin, use teeny bin. That'll get you to twrp recovery. In twrp flash the kk recovery and you should be good to go.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Gave it a shot, flashed ZVC and then after that did Teenybin SBL unlock and same thing. I get it into fastboot, choose recovery and then the phone show's a google logo with alittle lock on the bottom and then goes to black screen then to charging icon. :silly: I'll keep at it.
Update, a friend gave me some help and I was able to flash the recovery image you linked to me via ADB but still no change in the phone. On teenybin in fastboot, select recovery and still get the same google logo and small lock, then goes to power screen.
Haha, seems you've been down this road before. Found this while searching around, I'm giong to try the steps in the last two post's of the thread. Thanks for the help Engine.
http://forum.xda-developers.com/showthread.php?t=2535874&page=3
UPDATE: unfortunately no change, left the phone on the charger for a few hours but still stuck with no usable recovery mode and phone only responds while plugged in. Think i'll chalk this up to some type of hardware failure.
Will your phone even boot to the stock ROM? If it does, try installing Quickboot from the PlayStore. See if that'll get you into recovery.
I can't remember if it's in the root guide or the FAQ, but I posted another option for a battery issue like yours. Try it and see if it'll do more.
There's some commands that'll wipe through adb. I'll see if I can find them.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Wont boot into stock Rom yet, man i wish i was that far along and i'd be done probably. Thanks for looking at it for me.
nextelhalo said:
Wont boot into stock Rom yet, man i wish i was that far along and i'd be done probably. Thanks for looking at it for me.
Click to expand...
Click to collapse
There's something we're missing here, so lets start at the beginning
LGNPST ZVC again. This SHOULD get you going.
Now you will have stock recovery. To enter stock recovery, press vol down+power The LG logo will come on, then the capacitive lights. Immediately let go when the capacitive lights turn on. It takes a few seconds to work. And maybe a few tries to get it.
IF that all happens, then in stock recovery, do a Factory reset. IT WILL WIPE YOUR SD/INTERNAL STORAGE!!
Now your phone should boot up to stock ROM.
If that doesn't work, go to ADB and issue these:
adb shell
"dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/cache"
adb shell
"dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/userdata"
These will zero out /cache and /data
Reboot your phone and it should boot up
If not, you may need to LGNPST ZVC one more time and you should be good to go
If no dice again, you might need to try a battery pull, which you should know seeing as how you replaced the battery.
That's about all I got....you could also try getting on the irc and see if someone there has more idea's
Good luck! :fingers-crossed:
Edit: I forgot to tell you that in Stock recovery, use the capacitive menu key to select. The Power button doesn't do it in Stock recovery. Menu is the bottom right of the display and I don't think it's lit, but I'm not sure.
Thank you sir, i'll give this a shot tonight when i get back home. I'll keep my fingers crossed but i've located another LGOG on Craigslist for 80$, might not be able to pass up that deal.
Update: still no go, I agree there is something missing here. When i flash ZVC all goes like it should but the phone still just flatout wont do anything unless on external power. I went ahead and did a battery pull but no change. It's like we're doing everything correctly here but it wont let us past fastboot or download mode. Either it's software or this thing may have fried. I'm going to bring it to a friend here in town and see what he can do, he's a guru in this department but I wanted to figure this out on my own. If we get this back up and running I will for sure update this thread, hopefully it can help some folks out there. Thanks again for the help Engine, I wont give up until i know exactly what happened and i'll pass it along.