stuck in recovery - Eee Pad Transformer General

I am not a computer guy--tried to install latest update and am now stuck in recovery--I tried to install a recovery off an sd card but seemed to fail and now cant get anywhere. Can anyone walk me through a fix??
Thanks

press ctrl+alt+del
not suer

Need more info. Were you on a stock or custom ROM? Are you stuck in stock or custom recovery? What method did you try to install another recovery?
Sent from my SGH-I777 using xda premium

stuck
I was custom but rooted--tried to update tonight and it failed--then tried to deroot but now stuck un clockwork recovery--I am downloading ics -us but dont even know how to access external card with this file on as recovery lets me only onto internal sd which i think i cannot access
Thanks for the help

this worked for me...my situation sounds very similar to yours....
http://forum.xda-developers.com/showpost.php?p=23587495&postcount=47

ostism attachable
seems to freeze on cold boot??? says cold booting linux but noting happens
I am stuck in something that says clockworkmod Recovery v5.5.0.4

voodoo_dr said:
seems to freeze on cold boot??? says cold booting linux but noting happens
I am stuck in something that says clockworkmod Recovery v5.5.0.4
Click to expand...
Click to collapse
5.5.0.4 from Koush has a known problem
Follow this:
http://forum.xda-developers.com/showthread.php?t=1530337
There are many ways to get out of this situation. Get all the tools (adb, ROM zip files, etc.). Read posts in the thread. Ask for help there.
Good luck.

Put your transformer in APX mode by hold the power button & volume up.. If it turns back on do it again, make sure you have you sync cable plugged in and drivers installed. Now that your in APX download this stock rom then root it with viper (option 1 in viper)
Stock rom
http://forum.xda-developers.com/showthread.php?t=1334673
Viper root works on transformer & prime for root and unroot!!!
http://forum.xda-developers.com/showthread.php?t=1427125

voodoo_dr said:
I was custom but rooted--tried to update tonight and it failed--then tried to deroot but now stuck un clockwork recovery--I am downloading ics -us but dont even know how to access external card with this file on as recovery lets me only onto internal sd which i think i cannot access
Thanks for the help
Click to expand...
Click to collapse
Why you trying a stock ota on a custom rom?
feisty_noodle said:
5.5.0.4 from Koush has a known problem
Follow this:
http://forum.xda-developers.com/showthread.php?t=1530337
There are many ways to get out of this situation. Get all the tools (adb, ROM zip files, etc.). Read posts in the thread. Ask for help there.
Good luck.
Click to expand...
Click to collapse
Yes there's a fix in there towards the bottom of the first post.
If you want to flash another recovery, turn your device on into recovery, connect it to your computer and use adb to push the file to your internal storage.
It should be something like "adb push filename.zip /data/media" then you can use the borked recovery you're on to flash the one you pushed.
tegezee said:
Put your transformer in APX mode by hold the power button & volume up.. If it turns back on do it again, make sure you have you sync cable plugged in and drivers installed. Now that your in APX download this stock rom then root it with viper (option 1 in viper)
Stock rom
http://forum.xda-developers.com/showthread.php?t=1334673
Viper root works on transformer & prime for root and unroot!!!
http://forum.xda-developers.com/showthread.php?t=1427125
Click to expand...
Click to collapse
No, this is overkill and won't fix his issue.

This will work period
fone_fanatic said:
Why you trying a stock ota on a custom rom?
Yes there's a fix in there towards the bottom of the first post.
If you want to flash another recovery, turn your device on into recovery, connect it to your computer and use adb to push the file to your internal storage.
It should be something like "adb push filename.zip /data/media" then you can use the borked recovery you're on to flash the one you pushed.
No, this is overkill and won't fix his issue.
Click to expand...
Click to collapse
Yes it will what are you talking about? If he wants his tablet to work again and if he's not worried about the data on it (since he can't access it anyway) then this will work... Overkill lol , call it what you want it will work and it's simple!

tegezee said:
Yes it will what are you talking about? If he wants his tablet to work again and if he's not worried about the data on it (since he can't access it anyway) then this will work... Overkill lol , call it what you want it will work and it's simple!
Click to expand...
Click to collapse
His problem is with it getting stuck in recovery, which is a known issue with Koush's 5.5.0.4, simple fix with adb. No need to reflash the whole rom.

voodoo_dr said:
I am not a computer guy
Thanks
Click to expand...
Click to collapse
Well if he's not good with a computer, my method is the easiest especially if he doesn't have it figured out by now...

Thanks for the help everyone--Ended up using NVflash to load a rom called prime 1.6. 3:30 a.m. and I am as good as new. No ICS but at least it is stable

Good to see you got it back working...

Related

No recovery mode/Phone with Explanation mark

Ok, I have been thrown for a loop and need some help....
I had a Sprint Hero Rooted on 2.1 the .5 sprint update
Tried to run the new update but it kept getting corrupt.
Did a Nandroid backup
So I reverted back to the .5 RUU
Then it wanted me to update to the old .6 update, so I did
Hoping then I would upgrade to the new .6 but it was not able to find a new update?
Wanted to restore my nandroid update.
When I try to boot into the recovery mode I get a picture of a phone with a red Explanation mark in a triangle.
There is a bunch of people on the net that say they have seen or gotten it, but no one says how to get rid of it? So I can not get in to recovery mode at all.
Tried the home+power boot
Tried the volume down + power then home
always ends in the same screen with no recovery.
Tried multiple times to install the .5 RUU
Reset phone
never can get back there to the recovery?
Phone will boot fine into 2.1 and run fine..
Anyone have any ideas, I have tried everything I can think of.
Thanks
Did u try placing the recovery on ur SD card and flashing it threw terminal on ur phone
Root-Hack-Mod-Always™
You lost root, as far as I remember the .6 update was to block the corrent rooting efforts that you see around here, thats why the rooting instruction say to go back to the .5 ruu.
The corrupted update your getting is just sprints server being bogged down.
What you need todo is go back and re-root your phone. Dont worry about the update untill it gets released into one of the current roms or until you here that its safe todo without losing root.
ASimmons said:
You lost root, as far as I remember the .6 update was to block the corrent rooting efforts that you see around here, thats why the rooting instruction say to go back to the .5 ruu.
The corrupted update your getting is just sprints server being bogged down.
What you need todo is go back and re-root your phone. Dont worry about the update untill it gets released into one of the current roms or until you here that its safe todo without losing root.
Click to expand...
Click to collapse
Thanks, I can't believe I missed that! I had never tried a backup before root, so I did not think about that. Now I know and hopefully this will help someone that googles this issue, as there is never a clear answer until yours.
Thanks again...
So in closing of this thread:
if you are trying to get into recovery and see "Phone with Explanation mark" image.
it's because your phone is not rooted
So root your phone and it's all good
Also If you ever run an ruu on your phone you can kiss your root good bye no matter what version you do. but if you have nand backups you can reroot your phone and then restore one of your backups since there stored on your sdcard.
copc said:
So in closing of this thread:
if you are trying to get into recovery and see "Phone with Explanation mark" image.
it's because your phone is not rooted
So root your phone and it's all good
Click to expand...
Click to collapse
Correction: If you see this symbol, it means you don't have a custom recovery image in the phone. You can actually be rooted and still get that symbol if you haven't yet flashed a custom recovery after you rooted. You need to have a custom recovery (that requires root) to avoid getting that symbol when you try to boot into recovery.
Most rooting methods on here automatically include flashing a custom recovery as one of the steps, so this isn't really a big issue....but I just wanted to clarify the specifics of this for anyone else who reads.
copc said:
So in closing of this thread:
if you are trying to get into recovery and see "Phone with Explanation mark" image.
it's because your phone is not rooted
So root your phone and it's all good
Click to expand...
Click to collapse
I am running a rooted 2.1 and get this symbol , i installed rom manager and it asked me to install flash clockworkmod recovery and it booted into recovery straight away allowing me to partition my sd card, but if i want to access this mode i have to run flash clockworkmod recovery everytime or it will not work
Any idea why that is anyone?
brisuth said:
I am running a rooted 2.1 and get this symbol , i installed rom manager and it asked me to install flash clockworkmod recovery and it booted into recovery straight away allowing me to partition my sd card, but if i want to access this mode i have to run flash clockworkmod recovery everytime or it will not work
Any idea why that is anyone?
Click to expand...
Click to collapse
Nope once its on there you should be able to hold the home key while rebooting to get into recovery.
Sent from my HERO200 using XDA App
ASimmons said:
Nope once its on there you should be able to hold the home key while rebooting to get into recovery.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
only way can get there is through flash clockworkmod recovery then select either reboot in recovery mode or turn of handset and restart with home and power button, what ever flash clockworkmod recovery does to make it work as soon as it has been used i am guessing it is deleted or modified,
i have tried running it then checking files on sd card but cant see anything different
brisuth said:
only way can get there is through flash clockworkmod recovery then select either reboot in recovery mode or turn of handset and restart with home and power button, what ever flash clockworkmod recovery does to make it work as soon as it has been used i am guessing it is deleted or modified,
i have tried running it then checking files on sd card but cant see anything different
Click to expand...
Click to collapse
The recovery console isn't on your SD card, it's flashed to a partition inside your phone's memory. So you won't see anything different on your card.
And if you can boot into recovery by "restart with home and power button" like you say, then it's working as it should -- that's how you get into recovery.
chromiumleaf said:
The recovery console isn't on your SD card, it's flashed to a partition inside your phone's memory. So you won't see anything different on your card.
And if you can boot into recovery by "restart with home and power button" like you say, then it's working as it should -- that's how you get into recovery.
Click to expand...
Click to collapse
just had a friendly member point out what i was starting to suspect the problem lies with the custom recovery being flashed back to stock on every restart, the shell command here
/system/etc/install-recovery.sh this stops any custom recovery on reboot. any advice on what tools to edit or remove
Delete that file when you get root I guess. Our as soon as you reboot into clockwork recovery, flash a rom. Use nfinitefx if you want a stock one
Sent from my HERO200 using XDA App
I always had root that was where the confusion was, what i did not know was the script was running with every boot of the handset and removing the recovery that was there as it was identified as unofficial and exclamation mark could be down to me using many methods to flash i may have renamed original recovery so when it goes to exclamation it is because cant find original recovery whether handset is rooted or not.
danaff37 said:
Delete that file when you get root I guess. Our as soon as you reboot into clockwork recovery, flash a rom. Use nfinitefx if you want a stock one
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
would that have worked? i thought about it many many times but as i had never flashed before was unsure how many times phone would reset and if it did before it was installed could i lose my recovery.
on the plus side the 2 months i have spent trying to solve this i have a much broader view of the workings of my handset and without the many members like yourself who take the time to reply and try to help others i would have given up a long time ago.
Brian
I'm sure if you deleted that script a custom recovery would have stuck
Sent from my HERO200 using XDA App

Nexus S will not start

After power is only a white Google logo in the center of the black screen and then stays.
Can someone help me?
Thanks
I need more information.
Rooted? Rom? Kernel?
What did you do.
Sent from my Nexus S using Tapatalk
Did root. Wanted to put back the original rom will only start after the Google logo
And how did you attempt to put the google rom back on?
Did you have a custom recovery?
Sent from my Nexus S using Tapatalk
I installed the rom on recovery. Unfortunately, the wrong dan grh78 I wanted to make an update on grh41. My Nexus was formerly a rom grh78c
You didnt answer my question. Do you have clockwork recovery or the stock one? If its clockwork then its easy to fix.
Sent from my Nexus S using Tapatalk
Yes i have a clockwork and it isnt working. The problem is that i cannot start my mobile and i just see a google Logo. Unfortunatly i took the wrong rom grh78 instead grh78C. With rom grh78 the startingt phase worked but at the update on grh41 there came a failure message ,,it is not possible to make an update because a wrong rom is installed. I should have taken grh78C,,.
After the failure message I wanted to booten my mobile and after this message there just appears this google Logo.
Thanks for help
deltoro84 said:
Yes i have a clockwork and it isnt working. The problem is that i cannot start my mobile and i just see a google Logo. Unfortunatly i took the wrong rom grh78 instead grh78C. With rom grh78 the startingt phase worked but at the update on grh41 there came a failure message ,,it is not possible to make an update because a wrong rom is installed. I should have taken grh78C,,.
After the failure message I wanted to booten my mobile and after this message there just appears this google Logo.
Thanks for help
Click to expand...
Click to collapse
go into recovery, enable the usb storage option, put the right rom on your "sd" storage, turn off the usb storage option, wipe data(factory reset), flash the right rom, then reboot.
deltoro84 said:
Yes i have a clockwork and it isnt working. The problem is that i cannot start my mobile and i just see a google Logo. Unfortunatly i took the wrong rom grh78 instead grh78C. With rom grh78 the startingt phase worked but at the update on grh41 there came a failure message ,,it is not possible to make an update because a wrong rom is installed. I should have taken grh78C,,.
After the failure message I wanted to booten my mobile and after this message there just appears this google Logo.
Thanks for help
Click to expand...
Click to collapse
Okay heres what you do. Is your phone currently off? If it isn't then, pull the battery out. Put the battery back in.
Hold Volume Up + Power.. KEEP HOLDING THESE TWO and you should be in bootloader. Volume down to Recovery. Does it work? Yeah? Clockwork Recovery?
Okay. Now you have two choices:
1) Stock: download: http://forum.xda-developers.com/showthread.php?t=968403
Mount the phone via USB in Clockwork Recovery. Download that file and put it in /clockworkmod/backup/ (make sure you put it correct.. otherwise Clockwork wont see the file). Unmount, Check nandroid backup/restore is it there? If it isn't, recheck if you put it correctly. If so, reboot into recovery again.
2) Download a custom ROM such as CM7, Axura, GingerS, NSCollab, MIUI, whatever you want.. mount your phone via USB and put it on your sd card.
Wipe dalvik,cache,factory and flash that ROM (if you flash CM7.. you'll have to flash Gapps right after; MIUI.. flash English Language Pack right after).
Reboot. And it should go past the Google screen.
Alternatively, you should be able to plug your phone in the computer and using ADB by typing "adb reboot recovery" should get you into the recovery as well.
Edit: or do what simms suggested. Either way, you have to go into Clockwork Recovery to fix this.
it isnt working. i just come into a fastboot modus. how should i put the rom into a sd???? The mobile is recognized by the usb.
deltoro84 said:
it isnt working. i just come into a fastboot modus. how should i put the rom into a sd???? The mobile is recognized by the usb.
Click to expand...
Click to collapse
yes you're supposed to be on a screen that looks like http://2.bp.blogspot.com/-qW-hye-fsWM/TWJgxyBheCI/AAAAAAAAAEE/dIO-8DPEs1M/s1600/s1.jpg
if you volume down to the third one, it says Recovery.. that should get you into Clockwork Recovery (Orangeish) http://www.addictivetips.com/wp-content/uploads/2010/12/Clockwork-Recovery-3.jpg
if it looks like http://cdn.androidcommunity.com/wp-content/uploads/2010/12/device2-540x324.jpg (yeah aside from Dell) then you dont have clockwork recovery.
When you get into Clockwork recovery, there is a option in there to mount your USB. If you're able to get into Clockwork, I'd go to either of the steps I linked above.
Stock, CM7, Axura, MIUI, ETC. You need to replace your ROM with one of these.
Since you seem pretty new, I'd just stick with stock because that's what you're most comfortable with.
Zephik is trying really hard to help you here man. You need to read what he has written very carefully, supply more information, and follow the instructions really carefully. Then you can fix your phone without a problem.
Let us know how it goes.
zephiK said:
Okay heres what you do. Is your phone currently off? If it isn't then, pull the battery out. Put the battery back in.
Hold Volume Up + Power.. KEEP HOLDING THESE TWO and you should be in bootloader. Volume down to Recovery. Does it work? Yeah? Clockwork Recovery?
Okay. Now you have two choices:
1) Stock: download: http://forum.xda-developers.com/showthread.php?t=968403
Mount the phone via USB in Clockwork Recovery. Download that file and put it in /clockworkmod/backup/ (make sure you put it correct.. otherwise Clockwork wont see the file). Unmount, Check nandroid backup/restore is it there? If it isn't, recheck if you put it correctly. If so, reboot into recovery again.
2) Download a custom ROM such as CM7, Axura, GingerS, NSCollab, MIUI, whatever you want.. mount your phone via USB and put it on your sd card.
Wipe dalvik,cache,factory and flash that ROM (if you flash CM7.. you'll have to flash Gapps right after; MIUI.. flash English Language Pack right after).
Reboot. And it should go past the Google screen.
Alternatively, you should be able to plug your phone in the computer and using ADB by typing "adb reboot recovery" should get you into the recovery as well.
Edit: or do what simms suggested. Either way, you have to go into Clockwork Recovery to fix this.
Click to expand...
Click to collapse
If i go into recovery , i have 4 options.
1. reboot system now
2. apply update from/ sd card
3. wipe data/ factory reset
4. wipe cache partition.
Which obe should i choose? What should i do?
deltoro84 said:
If i go into recovery , i have 4 options.
1. reboot system now
2. apply update from/ sd card
3. wipe data/ factory reset
4. wipe cache partition.
Which obe should i choose? What should i do?
Click to expand...
Click to collapse
You don't have Clockwork Recovery then. Do you have the SDK installed? You need to go through the guides to set up SDK if you don't have it installed already.
- http://forum.xda-developers.com/showthread.php?t=895545
- Nexus S Drivers: http://forum.xda-developers.com/showthread.php?t=878786&highlight=Driver
Pretty much.. you just need to fastboot flash http://koush.tandtgaming.com/recoveries/recovery-clockwork-3.0.0.5-crespo.img
Download the clockwork recovery recovery-clockwork-3.0.0.5-crespo.img image, and save it to the ..\android-sdk-windows\tools directory
renamed it to recovery.img
then type fastboot flash recovery recovery.img and hit enter
you should get something like this, if not your image is corrupted, download it again
Click to expand...
Click to collapse
You need USB drivers for the Nexus S for the device to be recognized on your system.
Once you get Clockwork Recovery up and running (that orangeish recovery that I linked above) you should be able to refer back to my previous post. Once you complete that, your phone should be up and running.
go zephik go!
great display of patience
zephiK said:
yes you're supposed to be on a screen that looks like http://2.bp.blogspot.com/-qW-hye-fsWM/TWJgxyBheCI/AAAAAAAAAEE/dIO-8DPEs1M/s1600/s1.jpg
Snip..
Click to expand...
Click to collapse
This may be the most helpful post ever.
Sent from my Nexus S using Tapatalk
[hfm] said:
This may be the most helpful post ever.
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
cool you love to "troll" me. congratulations
its better than explaining what a bootloader looks like.. especially to a novice user (not insulting anybody).
a picture is a million words. troll me all you want, i really dont care. as long as im helping somebody rather than attempting to insult people over the internet. im doing more than you, so please.. continue "trolling", it'll get you really far in life.
Have you tried using odin to restore to stock?
Sent from my Nexus S using XDA App
bajansurfer said:
Have you tried using odin to restore to stock?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Or that.. but Odin isn't very popular with the Nexus S.
http://forum.xda-developers.com/showthread.php?t=947950
Option is there if you want to go that route. I used to use Odin for the Vibrant but I'm not too familiar with it for the Nexus S as its not as popular. If the OP decides to go with Odin then I can't assist you.
I really want to see how this pans out. He cannot be any more of a noob than I was very recently and I got the hang of it (zephik helped me too) so he should be able to fix it.
It's amazing the help you can get for free on this forum. If zephik was running a mobile phone shop be would be making money with the information he's providing ( although it would be much easier for him to take the phone away from the OP for 15 minutes and flash it himself ;-) ).

Unable to boot to CWM

So I've heard that when rooting, there's a bug that stops us from going into the cwm with the physical buttons and are forced to use the software to do it. My question is that when this bug is adressed will we just need to download the newer cw, from the play store and within that app just click flash clockwork mod? Or will we need to roof and do everything again?
Sent from my Nexus 7
Okaay said:
So I've heard that when rooting, there's a bug that stops us from going into the cwm with the physical buttons and are forced to use the software to do it. My question is that when this bug is adressed will we just need to download the newer cw, from the play store and within that app just click flash clockwork mod? Or will we need to roof and do everything again?
Sent from my Nexus 7
Click to expand...
Click to collapse
root the tablet
then install ROM manager and flash the official recovery from there
works perfect
The bug is that you cannot boot into any recovery (cwm/twrp/stock) from bootloader unless you are plugged into you computer via a usb cable. The only other way to boot is to use a script but that requires a working system partition.
Sent from my Nexus 7
I have the same problem and I flashed the official CWM from Rom Manager. I made a nandroid before I messed with it and when I went to change the LCD Density, I don't know what happened but now it won't boot. I can't get into CWM either. I figure I'll use ADB when I get home to try and reboot into recovery, if not I'll search the forums for the stock image and reflash. If there is a HW workaround to get booted into it from the device itself that would be awesome. I had to do a battery pull to keep it from rebooting itself and killing the battery.
I've always had Rom Manager Pro and immediately after rooting, used it to flash backups, update to 6.0 cwm, etc. If your rooted you must have that or Goo Manager for TWRP flashing anyway. Might as well start immediately.
There is a thread somewhere here dealing with changing density. The Nexus7 has problems when you simply use a density changing app.. You must change density by modifying prop.build. You can do this using a root explorer app, or by using Rom Toolbox Pro. I use Rom Toolbox and it worked perfect.
Once I get it up and running again around lunch time, I'll do that. Probably bring my laptop back to work with me. One question I had is will I be able to access CWM recovery by using ADB commands or will it just put me on the Google screen with the padlock?
chrisjm00 said:
Once I get it up and running again around lunch time, I'll do that. Probably bring my laptop back to work with me. One question I had is will I be able to access CWM recovery by using ADB commands or will it just put me on the Google screen with the padlock?
Click to expand...
Click to collapse
You can do fastboot boot recovery.img', or whatnot, even though it can't boot the recovery from the bootloader, at least you won't bork the device if /system gets messed up. 'adb reboot recovery' should work from android too.
I am stuck at the Google screen with the padlock and can't use ADB as it won't even recognize the device.
Is this a 6.0.0.6 issue? 6.0.0.4 worked just fine. I had a bad feeling when I hit upgrade through ROM Manager.
jmhalder said:
You can do fastboot boot recovery.img', or whatnot, even though it can't boot the recovery from the bootloader, at least you won't bork the device if /system gets messed up. 'adb reboot recovery' should work from android too.
Click to expand...
Click to collapse
Will that command allow me to access recovery to restore my backup?
---------- Post added at 02:55 PM ---------- Previous post was at 02:53 PM ----------
yeahthatsme said:
I am stuck at the Google screen with the padlock and can't use ADB as it won't even recognize the device.
Is this a 6.0.0.6 issue? 6.0.0.4 worked just fine. I had a bad feeling when I hit upgrade through ROM Manager.
Click to expand...
Click to collapse
I believe you need to be on the bootloader screen? I haven't flashed anything from Asus in a while, not since my original Transformer.
chrisjm00 said:
Will that command allow me to access recovery to restore my backup?
Click to expand...
Click to collapse
Code:
fastboot boot recovery.img
where recovery.img is a CWM image, should allow you to get into the recovery to fix whatever you messed up. Note that ADB is only functional if you already have CWM or Android booted... in the bootloader, fastboot is all that's available.
I have the same issue. Stuck at the Google logo with a padlock at the bottom. I didn't flash anything with ROM Manager just the recovery.img through fastboot, then did a fastboot reboot. Now I'm lucky if I can get the thing to stay off when I hold the power button it just pops back up to the padlock with Google logo.
When going to recovery from bootloader - freeze at google logo
It works by rebooting into recovery via ROM Manager. Also by the way, can anyone give me a link to the mod for the nexus 7 on jelly bean for the extended power menu?
CooLoserTech said:
When going to recovery from bootloader - freeze at google logo
It works by rebooting into recovery via ROM Manager. Also by the way, can anyone give me a link to the mod for the nexus 7 on jelly bean for the extended power menu?
Click to expand...
Click to collapse
Has anyone figured a way to access recovery using the buttons only? I've tried TWRP 2.2 and the newest cwm, and on a cold start from power off, it sticks at the Google logo. During a bootloop you are screwed unless you have a laptop within arms reach. Until this is rectified I'm leery of flashing anything. The whole point is being able to restore a nandroid in a crisis. I haven't found that ability yet. If anyone knows a way, please educate me!
Guess we can just wait. Besides there's not much development yet anyways. Would love to use AdFree and root explorer though.
Sent from my Nexus 7
chrisjm00 said:
Once I get it up and running again around lunch time, I'll do that. Probably bring my laptop back to work with me. One question I had is will I be able to access CWM recovery by using ADB commands or will it just put me on the Google screen with the padlock?
Click to expand...
Click to collapse
Recommend downloading quickboot. It is a paid app but it boots you to recovery no hassles with the buttons
Sent from my Nexus 7 using Tapatalk 2
Ya i have tried several version of CWM and TWRP and manually reinstalled cwm via adb. but all of them don't let me boot from the bootloader, i get the google logo like everyone else. Not sure what else to try, need to not take any risks until there is a fix i guess ^_^ hope someone gets some ideas

Stuck at google logo, recovery mode doesn't work?

I seem to have messed up the process. I successfully unlocked and rooted my Nexus 7 but during wipe process using JROM flasher something didn't go right and now I'm stuck at the google logo screen forever. I can boot into fast recovery mode but that's about it. I can't do anything.
I've had this done before on my nexus phone but it seems I managed to f it up this time.
I thought I had a rom zip file copied on to the Nexus 7 but it doesn't show in the menu. Now I'm stuck at the logo screen not having access to any roms to install. How do I reset all of this to factory? I've already checked most of the threads regarding this and haven't been able to find a solution yet.
calavera-pw said:
I seem to have messed up the process. I successfully unlocked and rooted my Nexus 7 but during wipe process using JROM flasher something didn't go right and now I'm stuck at the google logo screen forever. I can boot into fast recovery mode but that's about it. I can't do anything.
I've had this done before on my nexus phone but it seems I managed to f it up this time.
I thought I had a rom zip file copied on to the Nexus 7 but it doesn't show in the menu. Now I'm stuck at the logo screen not having access to any roms to install. How do I reset all of this to factory? I've already checked most of the threads regarding this and haven't been able to find a solution yet.
Click to expand...
Click to collapse
before you do anything, use your recovery to see if the rom zip is located in /data/media/0/. if its there, flash it from that location.
Are you able to boot into recovery?
If yes, it could be as simple as plugging your tablet into the computer and mounting the usb, drag and drop the rom, and flash it without using a toolkit (only recovery). I'm not familiar with jrom flasher, but i will say the more variables there are, the more chance of a problem.
If no, you're best off running the stock factory image through your computer, found here: https://developers.google.com/android/nexus/images#nakasi. I had your problem at one point, and could not even boot into recovery. After trying to install cwm through adb (which failed), and a number of toolkits, the factory image was what brought my nexus back to life.
I remember reading that sometimes a wipe can delete your recovery as well as your system (and whatever else you have on your n7), although i dont know if that was ever fixed, as i got my tab replaced a month or two ago and havent rooted it again yet. There was some type of command or .zip or something that should be used to keep recovery after wipes. When i expirienced problems such as yours, it was also from a bad wipe from a toolkit. Using just the recovery afterwards, i never expirienced any issues, even without the recovery fix.
I would definitely try simms suggestion first if you can access recovery. If that fails, try one of the above processes.
PS, even if you can access recovery, if at this point you just want to go completely stock, the factory image will work regardless.
cheers
Thanks for the help guys, I've been struggling for the past 3~4 hours but I found a solution.
What I did was use JROMFlasher and upload a rom zip to the sdcard directly and go from there.
calavera-pw said:
Thanks for the help guys, I've been struggling for the past 3~4 hours but I found a solution.
What I did was use JROMFlasher and upload a rom zip to the sdcard directly and go from there.
Click to expand...
Click to collapse
Guys..I have the similar problem..I am not able to upload rom zip to sdcard using JROMFlasher..Also USB mounting is not working for me ..
Is there any other way to move ROM to sdcard?:crying:
appoos said:
Guys..I have the similar problem..I am not able to upload rom zip to sdcard using JROMFlasher..Also USB mounting is not working for me ..
Is there any other way to move ROM to sdcard?:crying:
Click to expand...
Click to collapse
ADB
Sent from my Galaxy Nexus
Pirateghost said:
ADB
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
This dint work in my windows 8
appoos said:
This dint work in my windows 8
Click to expand...
Click to collapse
You're holding it wrong. ADB works on my Win8 machine
Pirateghost said:
You're holding it wrong. ADB works on my Win8 machine
Click to expand...
Click to collapse
can you tell me the procedure..
appoos said:
can you tell me the procedure..
Click to expand...
Click to collapse
no.
in the other thread that YOU created, you were given links to follow and the instructions are already there. i dont hold hands
I could do it with ADB..thanks guys

Im completely stuck

today ive got my new tmobile g2. first think i did is to root and install twrp . ive downloaded custom rom and i made i mistake by wiping everything in twrp. And i dint know that i cant mount internal sdcard on my pc in twrp. now im stuck on twrp and bootloop. and cant install LGMLauncher i comes to the 75% and get stock on win 7 64 bit. please help i have no idea what to do now. any way i can mount internal sd card twrp or other solution ? thanks in advance
Sorry mate, I cant help you, Im just wondering why people chose TWRP over CWM recovery? TWRP seems.. Very risky. Wiping everything, breaking on OTAs, etc.
Wouldn't it be safer to go with CWM, assuming its out for your version though?
Didn't even bother with the stock rom huh??
It's such a nice rom too.
LG G2
I think your best bet will be getting ADB installed and get it working on your PC. You should be able to send the file via ADB (command-line) and have it flash while TWRP is running.
Help out google search: "adb push in twrp"
I also disagree with SweStag's opinion about TWRP. It's not worse or risky, just more geared toward a power user. I switch to it when they first got their Touch Recovery interface and I haven't looked back to CWM yet.
chiljig said:
today ive got my new tmobile g2. first think i did is to root and install twrp . ive downloaded custom rom and i made i mistake by wiping everything in twrp. And i dint know that i cant mount internal sdcard on my pc in twrp. now im stuck on twrp and bootloop. and cant install LGMLauncher i comes to the 75% and get stock on win 7 64 bit. please help i have no idea what to do now. any way i can mount internal sd card twrp or other solution ? thanks in advance
Click to expand...
Click to collapse
here is the guide to install cwm. this is also what i use. twrp has never worked right for me in the past, you may be able to install the cwm recovery image through your pc
http://forum.xda-developers.com/showthread.php?t=2468858
if not likes you may have to kdz back to stock.
http://forum.xda-developers.com/showthread.php?t=2432476
SweStag said:
Sorry mate, I cant help you, Im just wondering why people chose TWRP over CWM recovery? TWRP seems.. Very risky. Wiping everything, breaking on OTAs, etc.
Wouldn't it be safer to go with CWM, assuming its out for your version though?
Click to expand...
Click to collapse
FWIW, I've never had any trouble with TWRP.
rfarrah said:
FWIW, I've never had any trouble with TWRP.
Click to expand...
Click to collapse
OK how da heck can I push anything in to this devise. adb doesnt see it any more. even windows is saying faulty driver even it used to work before. phone is completely cut off from outside world. please any sugestiobs ?
chiljig said:
OK how da heck can I push anything in to this devise. adb doesnt see it any more. even windows is saying faulty driver even it used to work before. phone is completely cut off from outside world. please any sugestiobs ?
Click to expand...
Click to collapse
This worked for another person in a similar situation (http://forum.xda-developers.com/showthread.php?t=2492911):
Buy a usb otg cable and use a thumbdrive or better, get a microusb thumbdrive like this one:
http://t2.gstatic.com/images?q=tbn:A...Una2lIDP2w&t=1
Place the image of whatever ROM and mount it?
Or, by connecting the cable mentioned above it would allow you to get into download mode and then heading in this direction: http://forum.xda-developers.com/show....php?t=2471370
Good luck!

Resources