hi all
my galaxy nexus dead, i cant get it to boot
i manage to flash ClockworkMod
my question is how i can transfer files using ClockworkMod
or iד there other method like using adb
saturn said:
hi all
my galaxy nexus dead, i cant get it to boot
i manage to flash ClockworkMod
my question is how i can transfer files using ClockworkMod
or iד there other method like using adb
Click to expand...
Click to collapse
Saturn,
If you managed to flash CWM, your device is not that dead.
First thing I would try, is to load CWM and do a Factory reset, and Wipe cache. Than, reboot your device.
If this doesn't work, I don't see how CWM could help you, as Galaxy Nexus don't have external SD Card.
For CWM to work properly, you must first transfer your files to the virtual sdcard, than reboot to CWM and use that files.
If you can't boot, you can't put your files inside the device, so CWM is useless at this point.
So, what I would do right now, is:
1. Revert your device to stock..
Google for it. You'll use FASTBOOT or ODIN to reflash all partitions to stock ones.
This will even replace CWM for a stock recovery.
2. Flash CWM again.
Your device is probably working at this point. So, you can flash CWM again.
3. Reboot to CWM recovery and perform a backup. Keep it for future use, so you can restore your device at any time.
4. Download any roms you would like to, and have fun playing with your device!
Ps: Now I see that the original post was from Dec/2011.. Sorry for that.
Related
I downloaded superwipe for my phone and ran it and it cleared my phone but the rom I put on the sd card is not showing up so I cant download it!
It is stuck on the black screen with just google on it help!!!
I downloaded a clockmod recovery from the rom manager before I did this but I have no idea how to fix this!!!
How about downloading a rom to your computer and transfer it to the sd card?
Its not showing up on my mac...
How can I get it to show up?
badd99 said:
I downloaded superwipe for my phone and ran it and it cleared my phone but the rom I put on the sd card is not showing up so I cant download it!
It is stuck on the black screen with just google on it help!!!
I downloaded a clockmod recovery from the rom manager before I did this but I have no idea how to fix this!!!
Click to expand...
Click to collapse
You are having exactly the same reaction i've had when i had my first bootloop on my HTC Desire, thanks for the laughs
Super Wipe cleans EVERYTHING, including your SDCARD. Dont worry, your phone is not bricked.
The easiest way for you to boot your phone is to flash a stock image with fastboot or CWM. Follow this great guide:
http://forum.xda-developers.com/showthread.php?t=1392310
haha, Im freaking out
On that guide what part should I follow? I used it to gain root and unlock the boot loader but where on there am I actually going to be restoring it?
if there is a way I can send a .zip file to my phone then I can easily install it form my phone...If only you could remove the sd card!!
That guide seems to tell you how to flash everything...nothing how to restore it.
flakz0r said:
You are having exactly the same reaction i've had when i had my first bootloop on my HTC Desire, thanks for the laughs
Super Wipe cleans EVERYTHING, including your SDCARD. Dont worry, your phone is not bricked.
The easiest way for you to boot your phone is to flash a stock image with fastboot or CWM. Follow this great guide:
http://forum.xda-developers.com/showthread.php?t=1392310
Click to expand...
Click to collapse
Super wipe lite does not wipe the virtual SD card. OP you probably have to flash stock images in fast boot, there is no restoring.
Sent from my Galaxy Nexus using xda premium
Please explain how to do this....
Found someone else did this and the guy who makes the rom posted this:
1. Change ROM name to rom.zip
adb shell
mount /data
exit
adb push rom.zip /data/media
Now reboot into recovery and flash ROM.
Problem is I have no real idea how to do all of this. If anyone could write up how to do it (im on a mac, but can use a pc if have too) then I would SERIOUSLY love them. You have to know the feeling of your brand new phone on day one not working
http://code.google.com/android/nexus/images.html
I believe you put this image on the root of your pc drive, either use adb or fast boot and push it in terminal.
can you explain how to use fastboot to do this? I need steps to follow since im new at android flashing...thank you!
you have to ADB push a rom to your phone.
Send it to the update directory and you can flash it with stock image.
Okay so how do I ADB push a rom?
badd99 said:
can you explain how to use fastboot to do this? I need steps to follow since im new at android flashing...thank you!
Click to expand...
Click to collapse
http://rootzwiki.com/topic/12069-guide-last-resort-fix-for-unfixable-bootloopingpseudo-brickedbricked-phones/
I dropped my phone and broke the screen. While the top 5th of the screen worked initially, it is now completely broken. I have CM9 on it, rooted and unlocked bootloader.
What are the steps I need to take in order to back this thing up to flash the image to a new phone to pick up exactly where I left off?
Should be able to do a nAndroid back up. Than boot back up to android and copy the file to a comp. When you get the new phone rooted and what not put the back up where there normally stored. Dont forget to wipe data, /system and both caches. Not sure but it'd be safe to use the same recovery on your new phone.
Sent from my Galaxy Nexus using XDA
Yes, I'm asking how to do a nandroid backup without using the phones screen
just use adb
adb backup -f filename.bak -all
should backup everything, then when you get the new phone, get the same rom installed and do a restore, no need for CWM
lordgodgeneral said:
just use adb
adb backup -f filename.bak -all
should backup everything, then when you get the new phone, get the same rom installed and do a restore, no need for CWM
Click to expand...
Click to collapse
This command will create a full backup that I can then use CWM to flash to the new phone?
I think I may have disabled debugging.... Is there a way to enable it without the screen?
Was gonna say flash a non touch recovery. But I dunno any way to enable USB debugging if touch input doesn't work. Though if you can put it in fast boot mode flash the non touch cwm and go from there. Don't need USB debugging for that.
Rename recovery to recovery.img for easy sake
Put it in the folder with fast boot
Fastboot flash recovery recovery.img
Sent from my Galaxy Nexus using XDA
armdavid2 said:
Was gonna say flash a non touch recovery. But I dunno any way to enable USB debugging if touch input doesn't work. Though if you can put it in fast boot mode flash the non touch cwm and go from there. Don't need USB debugging for that.
Rename recovery to recovery.img for easy sake
Put it in the folder with fast boot
Fastboot flash recovery recovery.img
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
if i get a different phone, im using a htc sensation now. planning to get a N4, will the back up be compatible? will apps restore to original state before my screen cracked?
Hello I recently messed up my phone trying to get a custom rom onto my phone. (It is a l710 model)
I can boot into Clockwork Recovery and ODIN just fine, but I phone won't start up.
I used GS3 toolkit to root phone and it all worked fine, but then used clockwork to install custom rom.
I want to recover my phone but the only rom on the internal SD is the one that doesn't work.
I have a Nandroid backup I made using the galaxy s3 toolkit, its on the computer and sd card.
However I cannot restore using toolkit since it just waits for the phone to be on and in usb debugging mode to continue
Recovery says "Couldn't open directory" "No files found" when trying to restore backup.
I would try puting another rom on an sd card but it only browses internal storage (internal sd).
I went to mount external sd but didnt seem to help
Not sure if ODIN can do anything...
Don't know what else to try
firesoul453 said:
Hello I recently messed up my phone trying to get a custom rom onto my phone. (It is a l710 model)
I can boot into Clockwork Recovery and ODIN just fine, but I phone won't start up.
I used GS3 toolkit to root phone and it all worked fine, but then used clockwork to install custom rom.
I want to recover my phone but the only rom on the internal SD is the one that doesn't work.
I have a Nandroid backup I made using the galaxy s3 toolkit, its on the computer and sd card.
However I cannot restore using toolkit since it just waits for the phone to be on and in usb debugging mode to continue
Recovery says "Couldn't open directory" "No files found" when trying to restore backup.
I would try puting another rom on an sd card but it only browses internal storage (internal sd).
I went to mount external sd but didnt seem to help
Not sure if ODIN can do anything...
Don't know what else to try
Click to expand...
Click to collapse
If you can get into download mode just flash the stock Odin file
Sent from my SPH-L710 using xda app-developers app
jamcar said:
If you can get into download mode just flash the stock Odin file
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
I tried that but my phone just flashes samsung then the samsung galaxy s III and then turns off (or at least it appears to be off).
Is there a way to restore Nandroid backups with odin?
firesoul453 said:
I tried that but my phone just flashes samsung then the samsung galaxy s III and then turns off (or at least it appears to be off).
Is there a way to restore Nandroid backups with odin?
Click to expand...
Click to collapse
You can get adb/the toolkit to see the phone. Go into the device manager while your phone is plugged in and booted to recovery. You should see a device with a ! next to it should be your phone. If you manually install the driver the toolkit will see it. Have the toolkin boot you into download mode. If you have recovery Odin mode should be okay, u sure ur holdin "vol down,home,pwr"?
Thanks for your time.
I managed to get it working.
What I did was
1. using odin, reflash the insecure boot thing.
2. reinstall the rom through recovery
3. factory reset
and then is wasnt stuck in a boot loop anymore
after that I could access internal storeage sd.
I had this same issue. After using ODIN Rom would hang on boot animation. Would never boot all the way and I gave it close to 45 minutes. I also found the only way to resolve this issue was doing a factory reset after flashing through ODIN. Im using Vzw model so I guess it is happening cross platforms.
firesoul453 said:
Thanks for your time.
I managed to get it working.
What I did was
1. using odin, reflash the insecure boot thing.
2. reinstall the rom through recovery
3. factory reset
and then is wasnt stuck in a boot loop anymore
after that I could access internal storeage sd.
Click to expand...
Click to collapse
stuck in boot loop and cant boot into recovery HELP
hi i am having a similar problem. i am stuck in my boot with the samsung gs 3 screen but i cant boot into recovery at all i can get into download but it says to install rom volume up but then it gets stuck at the download screen forever. i was trying to flash the cm 10.1 rom and did a clean install but this is what ended up happening am still for the most part a noob, if anyone can help it would be much appreciated idk if i lose everything on the phone just need it working
The download mode screen is supposed to stay froze like that. it doesnt have options. just boot to that screen, plug in your phone to pc and run this http://forum.xda-developers.com/showthread.php?t=2017470
billard412 said:
The download mode screen is supposed to stay froze like that. it doesnt have options. just boot to that screen, plug in your phone to pc and run this http://forum.xda-developers.com/showthread.php?t=2017470
Click to expand...
Click to collapse
Thanks man that worked I'm just an idiot and thought I was supposed to have options from there
Sent from my SPH-L710 using xda app-developers app
i tried rooting my galaxy s3 and i followed a guide i apparently cant post cause its an outside link, all was going great but i didnt realize that i wasnt supposed to unzip the Team Epic root from recovery folder, so when i tried to install from zip it wasnt a zip it was unzipped. I was thinking i could just put the zip on the internal but now i cant access it i get the feeling this is because of clockwork... so what should i do? i just need to install the zip folder if i could get it on my internal, if i could figure out how to go to stock thatd be good i just need to access it again. Help anyone? i thought it said something about not booting into the rom cause it deletes some files so it wouldnt work, is it safe to just power off? (i removed the battery once, do it again?)
You need to get the Team Epic zip on your internal sdcard. If you can not get there without rebooting that is ok. You will lose the cwm recovery when you boot. At that point you need to download the team epic zip and start over from the beginning. No harm done.
Sent from my SPH-L710 using xda app-developers app
m20120 said:
You need to get the Team Epic zip on your internal sdcard. If you can not get there without rebooting that is ok. You will lose the cwm recovery when you boot. At that point you need to download the team epic zip and start over from the beginning. No harm done.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
so you are absolutely sure if i remove the battery and boot normally to access the internal that i will be fine and it has not deleted files?
sorry im such a complete noob at rooting and stuff
WARNING: Do not boot into Samsung's ROM without first applying our Root .zip. Samsung's OTA updates install /system/etc/install-recovery.sh and /system/recovery-from-boot.p, which cause Samsung's ROM to replace the recovery image you had just flashed with the stock recovery. Our Root .zip removes these files, thus preserving your custom recovery. Follow the directions below to boot directly into CWM recovery.
Ya all that says is you will lose what you just flashed, basically starting you over.
Sent from my SPH-L710 using xda app-developers app
If you flash a custom recovery and do not also flash the Team Epic Root from Recovery ZIP (or something similar) the ROM will detect that you have a non-stock recovery when it boots. The ROM performs a signature check and if the recovery fails the check it will replace it with the stock recovery. That essentially puts you back at square one.
You can then download the Team Epic Root from Recovery file and save the ZIP to your internal sdcard. Then start all over.
- Power off the phone Boot into Download Mode (Vol-Dwn + Home + Power)
- Run ODIN and connect your phone.
- Load the CWM recovery (do not have Odin reboot when complete).
- Disconnect the phone and pull the battery when complete.
- Power up the phone in Recovery (Vol-UP + Home + Power)
- Flash the Team Epic ZIP.
- Reboot.
- Enjoy your rooted phone.
If you fail to flash the Team Epic file before rebooting the rom will not "delete any files". It will simply restore the stock recovery.
Flash this in Odin instead of the custom recovery. It will root you and reboot. You can then get the custom recovery with goo manager or ROM manager.
I'm a newbie and I am in trouble. I have a rooted Nexus 7 2013 and I have a TWRP Nandroid backup which I had copied to my WIndows PC.
Now my Nexus 7 crashed and won't go beyond the X on bootup. The Nandroid and Titanium backups are on my windows PC.
How do I restore the Nexus 7 to working status by restoring from the Nandroid backup and data I have copied to the PC?
Please help. Thanks.
Guys, someone please help.
I don't know how to get out of this mess. I'm still stuck on X.
I can power off the Nexus 7 and power to the recovery screen where I find Teamwin's menu.
I restored (several times) the nandroid backups I found on this menu (they were all done after the last reset) but rebooting then just gets me back to the X screen and no further.
I have a good nandroid backup on my PC but no way to get it into the tablet so TWRP can restore from it. Is there a way to transfer a file to or from the tablet when it will not boot completely?
The advanced screen of the Teamwin recovery menu lets me access a file manager. Is there any way I can use it to move files on or off the tablet to "anything" else?
The last time the boot froze on the X screen, I was able to go to the recovery screen with the android on his back and an X and from there to a reset. But this time I cannot get there and the recovery screen gets me to the Teamwin recovery menu. This has a wipe option. Will this reset the Nexus if selected. Will it remove root? I don't want to go through rooting it all over again.
Essentially I just want to do 2 things:
a) extract data from the stuck Nexus 7
b) reset and restore the nandroid backup I have on my pc.
Please help.......
Bill235 said:
Guys, someone please help.
I don't know how to get out of this mess. I'm still stuck on X.
I can power off the Nexus 7 and power to the recovery screen where I find Teamwin's menu.
I restored (several times) the nandroid backups I found on this menu (they were all done after the last reset) but rebooting then just gets me back to the X screen and no further.
I have a good nandroid backup on my PC but no way to get it into the tablet so TWRP can restore from it. Is there a way to transfer a file to or from the tablet when it will not boot completely?
The advanced screen of the Teamwin recovery menu lets me access a file manager. Is there any way I can use it to move files on or off the tablet to "anything" else?
The last time the boot froze on the X screen, I was able to go to the recovery screen with the android on his back and an X and from there to a reset. But this time I cannot get there and the recovery screen gets me to the Teamwin recovery menu. This has a wipe option. Will this reset the Nexus if selected. Will it remove root? I don't want to go through rooting it all over again.
Essentially I just want to do 2 things:
a) extract data from the stuck Nexus 7
b) reset and restore the nandroid backup I have on my pc.
Please help.......
Click to expand...
Click to collapse
Just choose the wipe option in twrp.
That should allow you to start android.
Then copy your backup from PC to virtual sdcard, reboot to twrp, and restore.
You can copy files while in recovery but it is more involved so I would try this first.
sfhub said:
Just choose the wipe option in twrp.
That should allow you to start android.
Then copy your backup from PC to virtual sdcard, reboot to twrp, and restore.
You can copy files while in recovery but it is more involved so I would try this first.
Click to expand...
Click to collapse
But will it remove the root I worked so hard to get?
If you worked hard to get root on a Nexus device you did something wrong. It should be as simple as unlocking the bootloader (already done), flashing a custom recovery (already done), and flashing the SuperSU ZIP file (this is the only step you'd need to repeat).
That said, doing a factory reset should not remove root. Even if it does, it would be restored when you restored your rooted Nandroid.
raptir said:
If you worked hard to get root on a Nexus device you did something wrong. It should be as simple as unlocking the bootloader (already done), flashing a custom recovery (already done), and flashing the SuperSU ZIP file (this is the only step you'd need to repeat).
That said, doing a factory reset should not remove root. Even if it does, it would be restored when you restored your rooted Nandroid.
Click to expand...
Click to collapse
Easy for an expert. I'm a newbie. I used the WUGfresh toolkit and it took multiple frustratng attempts and forever for it to finally download the correct adb drivers that would recognize the Nexus 7. Then all went smoothly.
But back to the present. I'm all fine now (till the next time the Nexus 7 crashes on me). For other newbies like me who run into this problem and need simple instructions here is what I did.
The first time this crash with the boot stuck on the X screen happened, going to the recovery screen (Power button + Volume up simultaneously) showed me the android on his back with a red triangle. Pressing power button and briefly volume up gave me the option to reset the tablet without removing root. Because I was traveling and did not have my TWRP backups with me (they were on my laptop 1,000 miles away) this removed all my data and I had to re-install all my apps and everything again.
The second time this happened, the recovery screen took me to the TWRP recovery screen. TWRP recovery had apparently survived the crash. I needed to save my data before reseting the tablet again. By trial and error I discovered that the TWRP menu has under the Advanced Tab a file manager. also discovered that if you connect a flash device to the tablet's usb port the TWRP file manager could read and write to it (!!!) in a folder called usb-otg (but not to my windows laptop). I copied what I wanted to save to the flash drive. Then I used the "wipe" tool to return the tablet to android.
I installed a free app, Recovery Manager, to reinstall TWRP recovery. Copied my previous TWRP nandroid backup to the tablet and restored everything as it was.
Easy as pie if you know how. I hope this helps some other befuddled user.
sfhub and raptir: Do you know what can be done to prevent this from happening again? Could Google Play being conected to in Europe after it was used to being to conected to in the US cause the problem? Both times the crashes happened shortly after I used the tablet in Europe and the the second time after I used it for the first time in the US.
Bill235 said:
sfhub and raptir: Do you know what can be done to prevent this from happening again? Could Google Play being conected to in Europe after it was used to being to conected to in the US cause the problem? Both times the crashes happened shortly after I used the tablet in Europe and the the second time after I used it for the first time in the US.
Click to expand...
Click to collapse
I can't say for sure what is happening in your case, but in my experience getting stuck on X means your user data got corrupted. The cases I've seen fall into 2 categories:
1) faulty EMMC flash memory. Sometimes if you wipe a couple of times the bad blocks get locked out and you don't see the problem anymore. Other times, they keep coming back. In the latter case, return/exchange/rma the unit
2) android crashes (random reboot) and unfinished writes are not completed corrupting the user data. They put in code in the latest ROM to mitigate this so if you think you are suffering from this type of corruption, install the latest ROM if you haven't done so already.
Thank you for the excellent and clear reply. I'll hope the 2 wipes I did may have gotten rid of my bad blocks.
I'll update to the latest stock rom too.
Thank you.
Bill235 said:
Thank you for the excellent and clear reply. I'll hope the 2 wipes I did may have gotten rid of my bad blocks.
I'll update to the latest stock rom too.
Thank you.
Click to expand...
Click to collapse
The updating part got me in trouble.......
I accepted the system update and am now running android 4.3 but lost root.
So I went back to the WUGfresh Nexus Root kit. Updated everything, am now on version 1.7.3 of the toolkit, followed all the instructions (uninstalled and re-installed driveers) and got stuck on the same problem I had the first time I tried rooting: the adb : step3 of the full driver test. adb device not found .
I did reboot twice, am using the oem asus cable, etc. What a pain!!
Unfortunately I am dependant on the toolkit because I do not know enough to root manually.
Suggestions? Thanks.
Bill235 said:
The updating part got me in trouble.......
I accepted the system update and am now running android 4.3 but lost root.
So I went back to the WUGfresh Nexus Root kit. Updated everything, am now on version 1.7.3 of the toolkit, followed all the instructions (uninstalled and re-installed driveers) and got stuck on the same problem I had the first time I tried rooting: the adb : step3 of the full driver test. adb device not found .
I did reboot twice, am using the oem asus cable, etc. What a pain!!
Unfortunately I am dependant on the toolkit because I do not know enough to root manually.
Suggestions? Thanks.
Click to expand...
Click to collapse
So you're stock 4.3 now? Rooting manually isn't hard bud, setting up the toolkit is harder IMO.
You just need to download and install the Android SDK. Then download a custom recovery .img file, and a SuperSU flashable zip. Put the SuperSu flashable zip on your /sdcard. You'll then boot into the bootloader, open a command prompt and change directories to your Android SDK (Ex. mine is at C:\sdk\platform-tools) and run the command: fastboot flash <name of recovery file>.img
Then reboot into recovery, flash the SuperSU zip, reboot, done. You're rooted. There are plenty of How To's stickied in the General Forums for the N7 here.
RMarkwald said:
So you're stock 4.3 now? Rooting manually isn't hard bud, setting up the toolkit is harder IMO.
You just need to download and install the Android SDK. Then download a custom recovery .img file, and a SuperSU flashable zip. Put the SuperSu flashable zip on your /sdcard. You'll then boot into the bootloader, open a command prompt and change directories to your Android SDK (Ex. mine is at C:\sdk\platform-tools) and run the command: fastboot flash <name of recovery file>.img
Then reboot into recovery, flash the SuperSU zip, reboot, done. You're rooted. There are plenty of How To's stickied in the General Forums for the N7 here.
Click to expand...
Click to collapse
Will look into your suggestions later because I am rooted again. It was the adb drivers again. The universal ones just would not work for me. The Samsung signed drivers on the other hand worked smoothly and then the toolkit ran smoothly and I am rooted. But it wiped out my TWRP recovery so I will re-install that next.
Thanks for the help.
About your advice, than you. But as a newbie I need clearer instructions. "download and install the Android SDK". Where? to the pc or the tablet? etc.
I need to learn more so I don't keep getting into these ridiculous binds!
Bill235 said:
Will look into your suggestions later because I am rooted again. It was the adb drivers again. The universal ones just would not work for me. The Samsung signed drivers on the other hand worked smoothly and then the toolkit ran smoothly and I am rooted. But it wiped out my TWRP recovery so I will re-install that next.
Thanks for the help.
About your advice, than you. But as a newbie I need clearer instructions. "download and install the Android SDK". Where? to the pc or the tablet? etc.
I need to learn more so I don't keep getting into these ridiculous binds!
Click to expand...
Click to collapse
Review the General forum for the N7 2013 here, as there are threads stickied to the top of that forum which has write-ups and video how to's that'll explain it all. I suggest to review those FIRST before you try doing things just so you can get a picture of what's going on. It may seem like a lot, but once you do it, it really is not.
The Android SDK is installed on your computer.