Made a mistake. Maybe a huge one.
Erased stock rom, etc before copying new rom onto sdcard. Now I am stuck with fastboot and recovery. Going to recovery connects "grouper" which I can not find driver for (installed asus drivers, samsung, google usb).
Gonna try to flash stock rom back and do all over
If fastboot recognizes your nexus 7 you can recover. Just flash the Google stock image in fastboot mode.
I don't have the link, it should be easy to find though.
Sent from my Nexus 7 using xda app-developers app
utom3nP .28569
Good news.
After flashing stock image like 10 times I figured out that CW recovery didnt work properly. Tried TWRP and it worked fine.
P1X3 said:
Good news.
After flashing stock image like 10 times I figured out that CW recovery didnt work properly. Tried TWRP and it worked fine.
Click to expand...
Click to collapse
You never updated your bootloader did you? Cwm works fine, but it didn't before I updated the bootloader (and only twrp worked then)
Sent from my SCH-I500 using xda app-developers app
Related
Via ROM manager, I updated CWR to 3.0.2.4 from 3.0.0.5. And now, for some reason when i boot into recovery, I'm greeted by the bootloader saying that there is no recovery or boot img. I don't have access to a PC right now, and I've tried installing older CWR versions, still no luck. Anyone have an idea?
Sent from my Nexus S using XDA App
MrSvedberg said:
Via ROM manager, I updated CWR to 3.0.2.4 from 3.0.0.5. And now, for some reason when i boot into recovery, I'm greeted by the bootloader saying that there is no recovery or boot img. I don't have access to a PC right now, and I've tried installing older CWR versions, still no luck. Anyone have an idea?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I've had intermittent trouble with ROM Manager properly flashing recoveries. Assuming you have the su binary installed already, you could download the img and then use flash_image from a terminal emulator to flash it manually from the phone itself.
Code:
flash_image recovery /sdcard/recovery.img
flash_image: http://cyanogen-files.carneeki.net/flash_image.zip
CWM: http://mirror1.kanged.net/recoveries/recovery-clockwork-3.0.2.4-crespo.img
Code:
Just flash 3.0.0.5 again and it will be fine.
Sent from my Nexus S using XDA Premium App
One thing that I always have to make sure to do whenever I flash a recovery on the Nexus S via ClockworkMod, is to flash it at least three times. For some reason the first time it never sticks - it takes it quite some time to first download it then try to flash it. The subsequent reflashes are (usually...) fairly quick and don't take longer than a couple of seconds - which is how I know that it's properly flashed them.
So go ahead and flash the newest available recovery for your NS, just do it at least three times.
knytphal said:
One thing that I always have to make sure to do whenever I flash a recovery on the Nexus S via ClockworkMod, is to flash it at least three times. For some reason the first time it never sticks - it takes it quite some time to first download it then try to flash it. The subsequent reflashes are (usually...) fairly quick and don't take longer than a couple of seconds - which is how I know that it's properly flashed them.
So go ahead and flash the newest available recovery for your NS, just do it at least three times.
Click to expand...
Click to collapse
Yup, that did it! Just kept doing it till it worked Thnx!
Sent from my Nexus S using XDA App
Ok so heres the story. Ubuntu released a version of it self for the N7 and I went to try it out. Works ok kinda sluggish, but I digress.
Went back to stock and it went smooth as butter. Now I went to flash CWM and it flashed like it was supposed to. Now for some reason my tablet only boots into recovery no matter what. I tried to press power and vol down to get into the bootloader and it just boots recovery.
I used Nexus Root Toolkit v1.5.4 to flash the image.
It's stuck in cwm?
Can you reach it via adb?
If so enter "adb reboot fastboot"
Sent from my Nexus 7 using xda app-developers app
mvmacd said:
It's stuck in cwm?
Can you reach it via adb?
If so enter "adb reboot fastboot"
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Tried that and ADB said there was no device attached. So, I reinstalled my drivers and that worked. Managed to get into fast boot and reflashed stock. I manually flashed cwm and that worked no problem. I'm now back on my own version of cm10.
Sent from my SCH-I535 using xda premium
Just rooted my N7 on 4.2.2 but can't boot into recovery. I just get the "no command" screen. I flashed twrp with the Nexus Root Toolkit and everything seemed to go fine but I can't boot into recovery. Is there another way to flash a custom recover?
Thanks!
Sent from my Nexus 7 using xda app-developers app
fastboot flash recovery recovery-image-file-name.img
while in boot loader mode.
Please use the forum search capability.
christanya99 said:
Just rooted my N7 on 4.2.2 but can't boot into recovery. I just get the "no command" screen. I flashed twrp with the Nexus Root Toolkit and everything seemed to go fine but I can't boot into recovery. Is there another way to flash a custom recover?
Thanks!
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
you probably booted, not flashed the recovery. fastboot flash it via fastboot with the instructions above. or, to make it even easier, download the goo manager app. you can flash twrp recovery with the app. open the app, press the settings option, press install openrecoveryscript, press yes, then let it do its thing.
simms22 said:
you probably booted, not flashed the recovery. fastboot flash it via fastboot with the instructions above. or, to make it even easier, download the goo manager app. you can flash twrp recovery with the app. open the app, press the settings option, press install openrecoveryscript, press yes, then let it do its thing.
Click to expand...
Click to collapse
I have the same problem as the 1st poster, an i did what you said, in regards to letting goomanager do the work but it still didn't work
Sent from my rOot3d Samsung Galaxy S3
http://teamw.in/project/twrp2/103
Read the download instructions at the bottom. Have you done that step?
The stock recovery will be restored on boot otherwise. It's the same procedure for any recovery (CWM) not just TWRP.
Sent from my Desire HD using xda premium
sashank said:
http://teamw.in/project/twrp2/103
Read the download instructions at the bottom. Have you done that step?
The stock recovery will be restored on boot otherwise. It's the same procedure for any recovery (CWM) not just TWRP.
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
No I haven't did that. I'm away from my computer on a trip, an will do this when I get home
Sent from my rOot3d Samsung Galaxy S3
Hi guys im sort of new to the android scene and im having problems with my nexus 4, i downloaded the newest cyanogenmod nightly and flashed it, it messed up part way through. i rebooted the phone and now its just stuck at boot animation. i have wiped the cache the dalvik cache and done a factory restore.
i have tried reflashing the nightly but it stick stops part way through, i want to add the new rom to the /sdcard but i dont know how, its not showing in android file manager and i have tried using adb push command.
im sure its a noob question but any ideas?
P.s sorry i know there are posts similar to mine but tried them and wont work
If adb push won't work in recovery you might try flashing the factory images with fastboot. System.img is really all you'd need.
estallings15 said:
If adb push won't work in recovery you might try flashing the factory images with fastboot. System.img is really all you'd need.
Click to expand...
Click to collapse
sorry i have no idea how to do that, i just need to access the file system so i can dump a rom to install
AW: [Q] Nexus 4 wont work after new cyanogenmod update
You can try to sideload a new ROM via 'adb sideload' in the recovery.
Sent from my Nexus 4 using xda premium
TobiS87 said:
You can try to sideload a new ROM via 'adb sideload' in the recovery.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
i have tried to side load a rom onto it but that didnt work adb gave a error
http://forum.xda-developers.com/showthread.php?t=2010312
Follow the steps, but only flash the system.img. Once it boots, move your ROM over. Reboot into recovery. Flash.
HTC Glacier is rooted running on stock 2.2.1 and unlocked the bootloader and flashed eng bootloader and s off and running TWRP recovery but everytime that i try to flash a rom TWRP verifys the flash and i hit reboot then im just stuck at boot loop for the rom then i try to flash the nandroid backup that i made before that and it will flash but ill just get bootloop so i have to flash the PD15IMG.zip and thats the only thing that I can flash
Ive tryed with TWRP and CWM most recent updated versions of the two
wizbo27 said:
HTC Glacier is rooted running on stock 2.2.1 and unlocked the bootloader and flashed eng bootloader and s off and running TWRP recovery but everytime that i try to flash a rom TWRP verifys the flash and i hit reboot then im just stuck at boot loop for the rom then i try to flash the nandroid backup that i made before that and it will flash but ill just get bootloop so i have to flash the PD15IMG.zip and thats the only thing that I can flash
Ive tryed with TWRP and CWM most recent updated versions of the two
Click to expand...
Click to collapse
Do you wipe data/cache and do a factory reset before flashing new rom? For me, it get stuck at boot screen if I flash a new rom without wiping.
Wiping data and factory reset is so important. When I tried to flash my first ROM it also got stuck. Try using 4ext instead of twrp.
Sent from my myTouch 4g using xda app-developers app
I tried that and still got stuck
I even wiped system and this his coming from stock
Sent from my Amazon Kindle Fire using xda app-developers app
wizbo27 said:
I tried that and still got stuck
I even wiped system and this his coming from stock
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
Naaa. Did you wipe everything?
Sent from my MyTouch 4G using xda app-developers app
I wiped everything cache delvik and system still just loops when I flash roms
maybe its the eng-hboot ?
wizbo27 said:
I wiped everything cache delvik and system still just loops when I flash roms
maybe its the eng-hboot ?
Click to expand...
Click to collapse
There are several more partitions than the ones you listed. Try a different recovery. If that doesnt work, you might return to stock Froyo and try rooting again the right way. I think the problem stems from the method you used to get get the engineering bootloader installed. It will always show S-Off, regardless of the state of the flag. It's possible that because you started off by going through HTC Dev that something is off. In fact, as a test, try flashing your boot.img separately through fastboot and see if it boots.
I tried that and it didn't work even when I relocked the boot loader from the HTC dev site and switched the eng boot.IMG to an updated one and got s off with gfree it boot froyo but would boot any ROM that I flashed with cwm and twrp still yet to try 4ext can't find the file for glacier specifically
Sent from my Amazon Kindle Fire using xda app-developers app
wizbo27 said:
I tried that and it didn't work even when I relocked the boot loader from the HTC dev site and switched the eng boot.IMG to an updated one and got s off with gfree it boot froyo but would boot any ROM that I flashed with cwm and twrp still yet to try 4ext can't find the file for glacier specifically
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
Try 4EXT, it it may fix the problem. Heres a link to the APK. It will install the recovery itself after you install the apk, open it, and click install or whatever it is.
Link for the apk is here --->http://www.4ext.net/get.php?apk
Or you could get it from the google store.
N_otori0us_ said:
Try 4EXT, it it may fix the problem. Heres a link to the APK. It will install the recovery itself after you install the apk, open it, and click install or whatever it is.
Link for the apk is here --->http://www.4ext.net/get.php?apk
Or you could get it from the google store.
Click to expand...
Click to collapse
you wouldnt happen to have the actual .img file would you ?
wizbo27 said:
you wouldnt happen to have the actual .img file would you ?
Click to expand...
Click to collapse
Nope. Don't worry though. The app takes care of everything.
Sent from my MyTouch 4G using xda app-developers app
N_otori0us_ said:
Nope. Don't worry though. The app takes care of everything.
Sent from my MyTouch 4G using xda app-developers app
Click to expand...
Click to collapse
I think he means that he requires the .img because he cannot boot into the OS to run the .apk on his phone.
If it is inappropriate to post a link to this file, I apologize in advance. It is FREE and I take no credit for creating any part of EXT4 Recovery.
wizbo27 said:
you wouldnt happen to have the actual .img file would you ?
Click to expand...
Click to collapse
Here is ver. 1.0.0.5 RC8 downloaded from the 4EXT Updater App for my HTC Glacier/myTouch 4G.
http://d-h.st/Wcm
Problem solved the problem was because the sd-ext wasnt getting wiped and 4ext allowed me to do it now i flashed cm10.1 albinoman jb 4.2.2 and it works like a charm thanks for the link to the .img file
wizbo27 said:
Problem solved the problem was because the sd-ext wasnt getting wiped and 4ext allowed me to do it now i flashed cm10.1 albinoman jb 4.2.2 and it works like a charm thanks for the link to the .img file
Click to expand...
Click to collapse
You're quite welcome! I'm glad you can boot again.
Thanks for the thanks.