Hey all I followed the http://forum.xda-developers.com/showthread.php?t=1766475 root guide to the letter, drivers, root and cwm all installed perfectly. I immediately booted into cwm after initial setup and did a backup (from bootloader). However the second time I tried to get into it through bootloader it just hangs.
When I installed ROM Manager and clicked 'boot into recovery' it works fine but for obvious reasons I don't trust loading up any kernels, ROMs or mods! Should I try a different recovery? Can I reinstall CWM? I tried several different CWM versions through ROM Manager but still the same result.
Thank you.
this issue has been widely discussed on many threads, it is the same with all recoveries, the only way to cold boot into recovery is by connecting the N7 to a computer via usb and then selecting recovery from the bootloader screen
neilrl79 said:
this issue has been widely discussed on many threads, it is the same with all recoveries, the only way to cold boot into recovery is by connecting the N7 to a computer via usb and then selecting recovery from the bootloader screen
Click to expand...
Click to collapse
My apologies, I did try searching/reading/etc and I really don't like being that guy. This thread can be closed thanks.
Related
I notice that the old standard, ClockworkMod 2.5.1.2, is now old news.
I went to install CWM 5.0.2, attempting both methods (flashing directly from CWM 2.5.1.2, also by booting into the PB31IMG.zip). Neither works, when I reboot, I'm back in 2.5.1.2
I searched here, but I don't see anyone having this issue.
Thank you in advance,
RKM
In rom manager, make sure erase recovery is selected. Then try to flash it twice.
Thank you for the reply.
I had found the posts that suggested that prior to my posting, however, I'm *not* using ROM Manager, I'm using both methods of installing correctly, at boot/recovery.
If it does not work from boot/recovery, no amount of settings in ROM manager will help me, unfortunately.
rkmFL said:
Thank you for the reply.
I had found the posts that suggested that prior to my posting, however, I'm *not* using ROM Manager, I'm using both methods of installing correctly, at boot/recovery.
If it does not work from boot/recovery, no amount of settings in ROM manager will help me, unfortunately.
Click to expand...
Click to collapse
Boot to recovery, go to mounts and storage and format recovery. Reboot the phone.
Download this http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip, and put it on your sdcard in no folders. Then boot to hboot, hboot will find the file and prompt to press vol up to install, and then vol up again to reboot.
Or you could do as sugested earlier and download rom manager, go to its settings and check erase recovery before flashing. Then from the main screen select the top option install cwm recovery.
If that dosent work i would flash back to thr stock recovery, and then back to cwm again, or try amon ra recovery then back to cwm.
If that dosent work, ruu and then flash cwm. Note that cwm 2 backups are not compatible with version 5.
@cmlusco - that's the same file I'm using now and it won't take, on *either* HDR6300 Incredible that I've tested it on. I'm still on 0.92 HBOOT and 2.15.00.07.28 RADIO.
During the HBOOT process, it does recognize the PB31IMG.zip, but it rejects it.
It reminds of of the way the phone reacts when it's S-ON. You know, how it rejects custom PB31IMG's until removing the security flag. Despite that, this is a fully S-OFF phone.
The one thing I had not yet done that you mentioned .. I haven't yet tried to "mounts and storage and format recovery" as you suggested. However, there is no option for "Format Recovery". In CWM 2.5.1.2, the Format options include:
Format Boot
Format System
Format Data
Format Cache
Format SDCard
Format SD-Ext
After reading your post, I tried "Format Boot" and "Format System". Neither one of those helped either.
The thing is, I don't think this is a one-off issue, because the exact same thing is happening on both of my DInc's.
rkmFL said:
@cmlusco - that's the same file I'm using now and it won't take, on *either* HDR6300 Incredible that I've tested it on. I'm still on 0.92 HBOOT and 2.15.00.07.28 RADIO.
During the HBOOT process, it does recognize the PB31IMG.zip, but it rejects it.
It reminds of of the way the phone reacts when it's S-ON. You know, how it rejects custom PB31IMG's until removing the security flag. Despite that, this is a fully S-OFF phone.
The one thing I had not yet done that you mentioned .. I haven't yet tried to "mounts and storage and format recovery" as you suggested. However, there is no option for "Format Recovery". In CWM 2.5.1.2, the Format options include:
Format Boot
Format System
Format Data
Format Cache
Format SDCard
Format SD-Ext
After reading your post, I tried "Format Boot" and "Format System". Neither one of those helped either.
The thing is, I don't think this is a one-off issue, because the exact same thing is happening on both of my DInc's.
Click to expand...
Click to collapse
Have you tried reformating your sdcard fat32? The only 2 reasons a PB31IMG.zip wont get recognized or install is if there is a problem with the sdcard, or its a bad download. Try downloading from a different source http://pvillecomp.com/?page_id=28.
You could run unrevoked with the 5.0.2.0 cmw img (custom recovery) set in unrevoked's menu. You can pull the .img file out of the PB31IMG.zip
I've tested three different SD cards, two different phones, about six different downloads (I've lost count).
I can flash ROM's without any problem. But if I try to flash a radio or recovery (including the stock recovery), it will not work, and this is on both phones. I've tried Stock, RA, CWM 3 and CWM 5. Yet I've tried three different ROM's and they all work fine.
That's a good idea on using Unrevoked and pushing an image. I'm not sure where to specify a custom .img file on Unrevoked, but will try to get through that now.
Thanks again for the ideas!
I pushed the custom recovery by using the CWM v5 .img file as you suggested, but that didn't work either.
The strange thing is how I can install any ROM I like, but CWM or Radios, won't flash. And weirder, is that it's not just a fluke on one phone.
I'm searching everything I can find with no luck. I suppose an RUU is probably the next logical step. I'm just worried because the last I remember, the newer RUU's will cause me to lose S-OFF. I can't remember if that's still the case and the posts don't say definitively.
Why not flash in ROM Manager? Just because it doesn't work in recovery/hboot doesn't mean it won't work in ROM manager. Also what happens if you do
flash_image recovery recovery.img
From either ROM or recovery? Your ROM might not have flash_image but clockwork does.
Sent from my GT-P7510 using Tapatalk
Hi Tiny,
Thank you for the suggestion.
I was previously led to believe that ROM Manager would not work if a straight CWM/Recovery upgrade did not work.
However, you're correct, using ROM manager worked. As a side note: to be safe, I selected "Erase Recovery" and flashed twice, as suggested.
I'm now on our third phone, and not a single one has been able to upgrade CWM coming from 2.5.1.2, but ROM Manager has worked for all of them!
Thanks again!
RKM
I feel compelled to say "Called it."
it'd be good to have hboot able to flash as a safety net but I don't like to bother flashing recovery and finding an hboot compatible zip so I use ROM manager to update. Glad to hear its working.
Sent from my Galaxy Nexus using Tapatalk
i flashed the CWM update zip, booted into CWM, wiped, and now im trying to install the EOS rom
it goes smoothly and i get no errors, but it boots into CWM every single boot now.,,
Pushed the older 6006 cwm and flashed, no errors, still boots into 6010.. ?
http://forum.xda-developers.com/showthread.php?p=22897771
Found this thread. For transformer Prime but hopefully it fixes my issue. If this is a bad idea lmk.
If not, Will try around midnight when I get back home
Woops,
Found this too
http://forum.xda-developers.com/showthread.php?t=1781250
Did you flash the CWM.zip in TWRP? I ask because there was a known issue when flashing CWM from TWRP you would get stuck in a recovery loop. I had the same issue and had to flash the stock .img to get out of it. Good luck.
i flashed the CWM zip that was posted in the CWM thread, bout to try and get myself free..
::success.
booted into bootloader
flashed bootloader, restarted, booted into my rom...
rebooted back into bootloader
flashed recovery
wipe/flash normally
I'm in the same exact situation, Could you share with me how you got it to boot into bootloader? I've been trying for awhile now. As I'm stuck in CWM I'm thus far unable to use adb. I'm a total adb noob so there is probably something quite simple I'm missing. Thanks in advance for any help.
Vektor67 said:
I'm in the same exact situation, Could you share with me how you got it to boot into bootloader? I've been trying for awhile now. As I'm stuck in CWM I'm thus far unable to use adb. I'm a total adb noob so there is probably something quite simple I'm missing. Thanks in advance for any help.
Click to expand...
Click to collapse
Press volume down when it boots (right before and while the Google logo shows up)
jamesst20 said:
Press volume down when it boots (right before and while the Google logo shows up)
Click to expand...
Click to collapse
Thanks for the reply, I've tried that many times. It's not working. I wish I had read this thread carefully and learned that it might be dangerous to flash cwm zip from TWRP, I had no idea.
The thing is is that it never really shuts down properly(thought I remembered a power off option on one of my epic 4g cwm) So when I press the power button while on the reboot system now option, that is what it does but back to recovery. I tried the volume button as you suggested as well as every other combination I could think of. :~(
Well in messing with drivers(uninstalling old drivers/devices installing universal naked driver) I had the nexus 7 q3 tool waiting for adb to enter fastboot and reflash TWRP so I could restore) and the tool suceeded in kicking me into fastboot(with an error in the toolkit) The toolkit stopped communicating though. I want to use the toolkit to reflash back to stock now that I'm in the bootloader screen.
I'm a bit nervous though, some warning about flashing asus stock blobs being a sure way to HardBrick. I think I'll wait until I get better information. I am on the bootloader screen, but I'm certain my bootloader as it sits is messed up from flashing CWM.
*Edit* Success!! I used this ; "[Guide] Returning to Stock and/or Unbricking your device"located here, http://forum.xda-developers.com/showthread.php?t=1781250 (not sure how to go about inserting a descriptive link sry :~( I'm now back to stock and ready to brick it again...umm, I mean, root and flash like there's no tomorrow. hehe Thanks for the input.:good::good:
Apologies, I am sure this has been asked before but I am in such a pickle as I have read all the threads I can find and that's why I am in this state.
I have root access via ODIN So that's a good start.
Tried to install Pacman no joy, tried then with Goo and their custom roms, no joy, installed CWM no joy so I think all the threads have confused me even more.
I cant see the "install from SD card option" when I boot to recoevery.
I have tried the one click rom update but that fails due to failed to verify whole-file signature
So I currently have a working phone with standard rom and SU and Root access but I cant install any ROMs
I am sure I have missed a stage so I wanted to write a new thread to see if we can go back to basics.
Hope you can help
uktotty said:
Apologies, I am sure this has been asked before but I am in such a pickle as I have read all the threads I can find and that's why I am in this state.
I have root access via ODIN So that's a good start.
Tried to install Pacman no joy, tried then with Goo and their custom roms, no joy, installed CWM no joy so I think all the threads have confused me even more.
I cant see the "install from SD card option" when I boot to recoevery.
I have tried the one click rom update but that fails due to failed to verify whole-file signature
So I currently have a working phone with standard rom and SU and Root access but I cant install any ROMs
I am sure I have missed a stage so I wanted to write a new thread to see if we can go back to basics.
Hope you can help
Click to expand...
Click to collapse
Let's see if i follow you here: You have rooted your device and then installed a custom recovery, or is it that the recovery won't install that's the problem? If you have a custom recovery maybe the fault lies with the recovery ittself?
If that is the problem I had that as well, What i did before flashing a new recovery with ODIN was to unable automatic reboot. Then, when the flash was done I took out the battery and made sure the phone was off. After this I booted into recovery and it worked like a charm... My firts tries with TWRP couldn't flash custom roms though, so I had to flash CWM recovery instead, and that worked as a charm.
Soliquidity said:
Let's see if i follow you here: You have rooted your device and then installed a custom recovery, or is it that the recovery won't install that's the problem? If you have a custom recovery maybe the fault lies with the recovery ittself?
If that is the problem I had that as well, What i did before flashing a new recovery with ODIN was to unable automatic reboot. Then, when the flash was done I took out the battery and made sure the phone was off. After this I booted into recovery and it worked like a charm... My firts tries with TWRP couldn't flash custom roms though, so I had to flash CWM recovery instead, and that worked as a charm.
Click to expand...
Click to collapse
Hiya
Ok so not sure about the Custom recovery bit,
I have now done the PhilzTouch thing and installed that via odin also.
What should II be looking for as far as the custom recovery goes?
Hold on a minute!
Looks like PacMan is now loading up, will update in a bit
Hey all, trying to flash CM10.2 on my G2 and I'm not able to boot into a custom recovery. Here's how I did everything.
Rooted - all was successful as far as I can tell. Was able to install Titanium backup and backup files and allow root.
I downloaded ROM Manager and installed CWM. When I went to boot into recovery, i get the error with the Android a red triangle exclamation point above him. So I tried to switch to TWRP through Rom manager, no luck. I tried to 'flash' TWRP through the command prompt and download of the recovery file, no luck.
I saw somewhere to download SuperSU, so I did that and tried again, and same issues. When I 'cleaned' SuperSU, uninstalled and reinstalled it but this time chose 'use custom recovery' - it tied to reboot into recovery, saw a standing up right android with a spinning icon, but then went to the same error.
Obviously I'm missing something somewhere. Can't figure out what.
Thanks for any help!
Don't use rom manager. Either use adb and push the recovery or use the app flashify to install the recovery. There are many threads ids the development sections on how to install recoveries
Sent from my LG-D800 using Tapatalk
tdevaughn said:
Don't use rom manager. Either use adb and push the recovery or use the app flashify to install the recovery. There are many threads ids the development sections on how to install recoveries
Sent from my LG-D800 using Tapatalk
Click to expand...
Click to collapse
Thanks, Is there a way to undo what I've done from rom manager? Because I used adb to push the recovery and still had the same issue, and using flashify to flash the image doesn't seem to work. Booting into recovery just gets me to stock recovery asking 'do you want to factory wipe your device'
Edit: When I boot to recovery from within flashify, it gives a 'boot certification error' upon booting
goldenmonkey1 said:
Thanks, Is there a way to undo what I've done from rom manager? Because I used adb to push the recovery and still had the same issue, and using flashify to flash the image doesn't seem to work. Booting into recovery just gets me to stock recovery asking 'do you want to factory wipe your device'
Edit: When I boot to recovery from within flashify, it gives a 'boot certification error' upon booting
Click to expand...
Click to collapse
Are you using a recovery that has been Loki'd. The G2 needs this to by pass the bootloader. By that error it does not seem you used the correct recovery file.
Jimi Mack said:
Are you using a recovery that has been Loki'd. The G2 needs this to by pass the bootloader. By that error it does not seem you used the correct recovery file.
Click to expand...
Click to collapse
I used the one from here - http://forum.xda-developers.com/showthread.php?t=2449670 - 2.6.3.3 and just flashed it with flashify most recently. But I was having the same issue when I installed it via adb and 'option 1' as shown there.
Yeah, when flashing that recovery image using option 1, I still get "secure booting error - boot certification verify" after I reboot into recovery
Huh, I got it.
Reading this post here - http://forum.xda-developers.com/showpost.php?p=48118278&postcount=567
Someone else was having the same issue as me. The newest recovery gave him that same error. Flashed 2.6.3.2 and it worked fine. (So far)
Glad to hear. Good Luck.
Hello all, I accidentally used ROM Manager to try to install CWM, but when I booted into recovery, it gave me that Android with the red triangle icon. How should I go about removing any remnants and installing TWRP? Thanks for your help!
Sounds like you probably just booted into stock recovery (meaning, CWM didn't install). Try booting into the phone's OS again, then try a different recovery flashing method like loki_flash.
antinorm said:
Sounds like you probably just booted into stock recovery (meaning, CWM didn't install). Try booting into the phone's OS again, then try a different recovery flashing method like loki_flash.
Click to expand...
Click to collapse
Ok, so I booted into the Stock ROM, do I need to do anything other than follow the instructions for Loki_Flash? It's safe even though I already tried installing CWM?
charlesz54 said:
Ok, so I booted into the Stock ROM, do I need to do anything other than follow the instructions for Loki_Flash? It's safe even though I already tried installing CWM?
Click to expand...
Click to collapse
loki_flash performs validation checks that many other methods don't, so it's safer than they are. Just make sure you run it as root, and you have the correct image for your device.