Related
Hey guys,
I have done something stupid.
The phone.
GSM Galaxy Nexus - Android 4.0.2 (ICL53F)
Rooted. otherwise stock.
Current status - will not boot android. Will load fastboot/recovery
I was trying to change the bootanimation.
Could not do it with adb push.
So i tried by copying the .zip file to the phone.
Opened up file File expert (unsure how many use this) clicked on "internal Memory" and tried to mount for read/write.
Copied bootanimation.zip from sd card to /system/media would not paste.
Tried again. Did not paste but it did delete the stock bootanimation.zip file.
Unsure what i clicked but when i tried to open /system/media it try to "execute" it, stated that it could not find a program to do so.
Closed program.
Phone started to come up with differnt apps stating that they have stopped working.
turned off phone, reboot.
Will not load boot animation, just loads to recovery!
I think I will have to flash the stock rom to solve this.
Any help would be great.
Tiggerbits said:
Hey guys,
I have done something stupid.
The phone.
GSM Galaxy Nexus - Android 4.0.2 (ICL53F)
Rooted. otherwise stock.
Current status - will not boot android. Will load fastboot/recovery
I was trying to change the bootanimation.
Could not do it with adb push.
So i tried by copying the .zip file to the phone.
Opened up file File expert (unsure how many use this) clicked on "internal Memory" and tried to mount for read/write.
Copied bootanimation.zip from sd card to /system/media would not paste.
Tried again. Did not paste but it did delete the stock bootanimation.zip file.
Unsure what i clicked but when i tried to open /system/media it try to "execute" it, stated that it could not find a program to do so.
Closed program.
Phone started to come up with differnt apps stating that they have stopped working.
turned off phone, reboot.
Will not load boot animation, just loads to recovery!
I think I will have to flash the stock rom to solve this.
Any help would be great.
Click to expand...
Click to collapse
If this was my phone I'd find a nice rom, stock or not, and install it. I'd follow the dev's installation instructions to a "T".
You could also go this way: http://forum.xda-developers.com/showthread.php?t=1399210
Good luck.
Geezer Squid said:
If this was my phone I'd find a nice rom, stock or not, and install it. I'd follow the dev's installation instructions to a "T".
You could also go this way: http://forum.xda-developers.com/showthread.php?t=1399210
Good luck.
Click to expand...
Click to collapse
I've just flashed the stock image, luck i remembered that i did an adb back up not long ago. so just restoring that.
Than to root and flash cwm and start again. this time i'll be careful
[HOWTO] ClockworkMod Recovery & TWRP - Upgrade/Downgrade (Touch/Non-Touch Recovery)
IF YOU TRASH YOUR PHONE USING THIS PROCEDURE, THEN IT IS A VERY GOOD INDICATION YOU ARE AN IDIOT AND SHOULD NOT BE FLASHING ANY ROMS NOR PARTICIPATING ON THESE FORUMS. . . . JUST SAYIN'. . . .
Please be VERY careful when using this method as you can brick your phone. Make sure you triple check the file you downloaded is the right size and placed in the right area, but most importantly that the command lines you type are exactly right. If you are not comfortable using this method, then please do not and go find a flashable version of these recoveries.
I've posted a procedure to format/'flash' your recovery while on your phone in one of the threads on here and was asked by a Forum Mod to make a quickie guide to be placed as a sticky on the dev boards so others might benefit.
Anyway, here is a very quick and easy way to change your ClockworkMod recovery with a couple of command lines.
The TWRP link is in the second post.
Now for the ClockworkMod Instructions:
1. First, go here and look up your ClockworkMod recovery that pertains to your phone: http://www.clockworkmod.com/rommanager
2. Download the .img file for your phone and save it on your computer.
3. Rename the .img file to recovery.img and save it to your internal sd card of your phone. For example: recovery-clockwork-6.0.1.4-hercules.img ------> recovery.img
4. Open up Terminal Emulator on your phone and type the following 2 commands:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22
(please note the second command is a one line command with spaces between "dd & if=" and ".img & of=")
If your Rom identifies your internal sdcard as /emmc instead of /sdcard, then make the adjustment to command line (dd if=/emmc/recovery.img) instead of what is posted above.
That simple.
You can also issue these commands from adb shell if you are connected to your computer.
If Terminal Emulator does not have Superuser or SuperSU permissions for root privileges then make sure it does. You can also go from NON Touch CWM to Touch CWM using this and vice versa. Simply make sure you have the right recovery for your phone and rename it to recovery.img.
As for explanations:
dd if= command is a common Unix program whose primary purpose is the low-level copying and conversion of raw data.
dd stands for "data description"
if stands for "input file"
of stands for "output file"
the = is the location of the data you are using. ie. /sdcard/recovery.img
the /dev/block/mmcblk0p22 is the location/partition of the recovery on your phone.
So essentially you are doing a low level rewrite of the recovery image on your phone via command lines.
***Also, the best way to remember this command line is to not to. Copy the command line and save it to your own personal contact info in Google under Notes and then you will have it with you wherever you go. You really do not want to mess with getting it wrong. You could brick your phone if you mess things up.
Anyway, I hope this helps. . . . it really is very easy to execute without fault.
Works with TWRP too.
This also works with changing to and from TWRP. Download the image (for our phones it's TWRP 2.3.1.1) rename it to recovery.img and follow the above instructions and you are good to go.
Follow this link to get the image file: http://teamw.in/project/twrp2/101
***I attached the old TWRP 2.2.2.0 is case you run into problems with the newer versions not restoring backups properly or renaming backups correctly.***
Excellent Thread, I hope Dev's requiring specific CWM versions can link to your post.
Thanks for your efforts.
Noellenchris
XDA Forum MOD
Thanks for the instructions! Thanks even more for explaining the command lines.
Just thought I'd point out a small bug with the Touch Recovery. If you flash one of the newer ICS roms like Darkside Evolution through the Touch Recovery, once booted, the ROM WILL NOT SLEEP through time out. I've confirmed this with 2 separate ICS roms. Flashing non-touch recovery through Rom Manager fixes this problem.
Wouldn't it be easier to use gscript and run the commands as you need them?
Thanks for the HOW TO I actually was looking for it.
What is wrong with ROM Manager? I use it to go between Touch and normal all the time and it works flawlessly.
dextroamphetamine said:
What is wrong with ROM Manager? I use it to go between Touch and normal all the time and it works flawlessly.
Click to expand...
Click to collapse
For some people Rom Manager doesn't work. On the T-Mobile SGH-T989 Galaxy SII, Rom Manager will only allow you to go to 5.0.2.6 not 5.0.2.7. And, I think you have to upgrade Rom Manager to go to Touch. I bought Rom Manager, and don't use Touch Recovery, so I am not sure.
I like to use the command structure verses program because I know it works, it's fast, and I can see the results if an error occurs.
Oh yeah...this was really simple...Thanks...went from Touch back to Non Touch.
Give this a try
If you want a simple way to flash the Touch Recovery then give this a try. I will be adding the Hard Recovery as well in the next release.
SGSII T989 Root Toolkit
http://forum.xda-developers.com/showthread.php?t=1650908
http://forum.xda-developers.com/showthread.php?p=26200755
I get a write error: No space left on device. 1001+0 records in 1000+0 records out 512000 bytes transferred in 0.132 secs.
I reboot into recovery and it's still on 5.0.2.6
Edit: so i closed the terminal and I ran it again, and now my phone won't turn on. I get a USB device in windows called QHSUSB_DLOAD. I hold the power button, and the device disappears, but it won't turn on. I let go of the button, the same device reappears.
albanianbrotha said:
Edit: so i closed the terminal and I ran it again, and now my phone won't turn on. I get a USB device in windows called QHSUSB_DLOAD. I hold the power button, and the device disappears, but it won't turn on. I let go of the button, the same device reappears.
Click to expand...
Click to collapse
hate to be the dude that tells you this but i'm pretty sure qhsusb_dload is magic windows talk for "hard bricked phone." had that problem a while back. however all is not lost - these guys have a great reputation for Lazarus-ing dead phones.
hobakill said:
hate to be the dude that tells you this but i'm pretty sure qhsusb_dload is magic windows talk for "hard bricked phone." had that problem a while back. however all is not lost - these guys have a great reputation for Lazarus-ing dead phones.
Click to expand...
Click to collapse
Haha no worries bro. I mean worries that it failed for no reason, but I already sent it in, he just got it today. Same person you linked. Definitely trying to install ics again when i get it. Plus I think the ota ics for tmo came out yesterday or something? Probably a better experience than what was already out there with the radio and stuff.
the files from the CWM site are not .img for me, they are .ndif is it the same procedure?
MustangFTW said:
the files from the CWM site are not .img for me, they are .ndif is it the same procedure?
Click to expand...
Click to collapse
No! Do NOT use this procedure with that file extension!
What recovery are you trying to install? And for what phone? I briefly ran my cursor over the various files and the download links are either .img or .zip files. I did not see .ndif file extension.
PM me if you need additional help.
Would you happen to have the .img file for 5.0.2.7??
Edit* Nvm.. a quick google search and I was able to find it. You are a life saver.. I tried updating my recovery to the 6.0.1.2 Hercules port and for a couple days, it was working great up until an hr. ago. Nothing would flash and it would just hang in recovery... so I found this thread and thankfully I was able to downgrade back down to 5.0.2.7.
If you were local, I would take you out and get you piss drunk for helping me save my device. Cheers!!!!
fresherthanU said:
Would you happen to have the .img file for 5.0.2.7??
Edit* Nvm.. a quick google search and I was able to find it. You are a life saver.. I tried updating my recovery to the 6.0.1.2 Hercules port and for a couple days, it was working great up until an hr. ago. Nothing would flash and it would just hang in recovery... so I found this thread and thankfully I was able to downgrade back down to 5.0.2.7.
If you were local, I would take you out and get you piss drunk for helping me save my device. Cheers!!!!
Click to expand...
Click to collapse
You're welcome, I'm glad I could help you. But, the link to the .img files is in the OP instructions. . . .
Unfortunately this method did not work for me... I have tried many ways to update my CWM and none of them worked, it is almost hopeless for me
Good news! You made front page! http://www.xda-developers.com/andro...gn=Feed:+xda-developers/ShsH+(xda-developers)
Let me make this short for you guys.
I was running carbon rom then decided to try CM 10.1 only because I am a romholic. CM was giving me small quirks so I tried to restore my carbon rom but for some odd reason it wouldnt go pass the samsung logo after it restored successfully. After trying to restore a few times over and over it just decided it was now going to fail. So I tried to go back to CM but now that also failed. So now I was trying to mount usb storage through TWRP but for some odd reason there's no way to do this. After trying to figure out wth was going on I finally made the biggest mistake of completely erasing my internal SD.
So now I am basically in TWRP 2.4.4.0 with no way to access usb storage and not knowing what I should do next.
Please help your fellow romholic
you'll probably have to boot into download mode and use odin to get back to stock and start over.
^^^^^^^^^ That's what you're going to have to do.
There is a way to do ADB sideload through TWRP but you have to edit some files and the Odin method is a lot easier in my opinion. If you want to use ADB Sideload follow my instructions on this thread: http://forum.xda-developers.com/showpost.php?p=39849970&postcount=10. That shows you how to get ADB to recognize your phone in Recovery mode and then the adb sideload command will work.
Odin keep failing. It look like everything is going good then it will get to "get PIT for mapping" stay there for about 7 minutes then fail. I cant believe this:crying:
I would suggest you try my method with ADB sideload, do you know how to use ADB?
Im not familiar with ADB. Any help would be much appreciated.
I got to finding those two lines,
USB\VID_18D1&PID_D001&MI_01
USB\VID_18D1&PID_D001&REV_0228&MI_01
then I got lost.
It says I have to paste those two lines under
[Google.NTx86]
xxxxxx
;Google Nexus (generic)
xxxx
but I am a little lost there.
Here is the guide for setting up ADB: http://forum.xda-developers.com/showthread.php?p=9936674
If you already have done that, then you should navigate to the directory I listed which is where the android_winusb.inf file is, this is the file you edit
sevenpioverthree said:
Here is the guide for setting up ADB: http://forum.xda-developers.com/showthread.php?p=9936674
If you already have done that, then you should navigate to the directory I listed which is where the android_winusb.inf file is, this is the file you edit
Click to expand...
Click to collapse
Thanks for the help. I finally got odin to work after trying a dozen times. This definitely scared me a bit for a minute lol. The only downside now is that I lost about 2 weeks worth of data from my phone since that was my last backup point. Now I know how important back up can be.
Now back to this rooting..if I can remember:silly:
CyberGmonster said:
Let me make this short for you guys.
I was running carbon rom then decided to try CM 10.1 only because I am a romholic. CM was giving me small quirks so I tried to restore my carbon rom but for some odd reason it wouldnt go pass the samsung logo after it restored successfully. After trying to restore a few times over and over it just decided it was now going to fail. So I tried to go back to CM but now that also failed. So now I was trying to mount usb storage through TWRP but for some odd reason there's no way to do this. After trying to figure out wth was going on I finally made the biggest mistake of completely erasing my internal SD.
So now I am basically in TWRP 2.4.4.0 with no way to access usb storage and not knowing what I should do next.
Please help your fellow romholic
Click to expand...
Click to collapse
delete this / I replied after the fact....sorry.
Hello everybody!
The latest install of CyanogenMod Nightly 5. july constantly crashes System UI, whereas I press the OK button, and I got about 1 second before it pops up again. I can see that many others that installed the same nightly is having the same problem, and that there will be a fix in 6. july update.
My problem is that I can't access the Rom Manager to update CyanogenMod (since it crashes when I try to launch), and I seem to not be able to enter recovery mode. Therefore, I have no way to install the 6. july update when it comes out. Sadly, I'm not as skilled as the regular development user, and would be greatful for any help, tip or advice I might get.
I would've posted this in the CyanogenMod Nightly thread, but I haven't posted 10 posts yet.
Thanks
ipi
Maybe,just maybe,download the latest build on pc,then copy it on phone?
Or making a clean install of actual build you are using?
Sent from LG E975 pwd by CM 10.1
Yeah, that could absolutely work, but how can I enter CWM recovery without going through the ROM manager app?? :silly:
You can always use adb to enter recovery mode....
Sent from LG E975 pwd by CM 10.1
kimitza said:
You can always use adb to enter recovery mode....
Sent from LG E975 pwd by CM 10.1
Click to expand...
Click to collapse
I've never really understood adb, how it works or what it actually is. I've tried to look for good tutorials on how to install and how to use adb with my Optimus G, but so far I've only accomplished installing something I don't even think works, and I've never been able to communicate with my phone through any of the programs.
Do you have a link to a decent tutorial?
I would be very greatful!
I'm also unavaiable to find my phone listed as devices on My Computer, where can I find the USB settings on my phone?
EDIT: Ok, I am now able to boot my phone into CWM, only thing I'm missing now is transfering the updated ROM into my SD card, but I am still not able to find my phone on devices. What am I missing?
you can't mount usb on cwm, as you don't have external sdcard.
with adb the command would be
adb push /path/to/local/file /mnt/sdcard/path/to/file
for example,you have the file in D: ,the command would be adb push /D:/cm10.1 /mnt/sdcard/
this means you would copy the file from root of D: partition to root of the internat memory of phone.i just gave you an example.
it's easier to rename the file you are transfering to a short name and put it on root of partition.this way there are less chances to get syntax errors.
kimitza said:
you can't mount usb on cwm, as you don't have external sdcard.
with adb the command would be
adb push /path/to/local/file /mnt/sdcard/path/to/file
for example,you have the file in D: ,the command would be adb push /D:/cm10.1 /mnt/sdcard/
this means you would copy the file from root of D: partition to root of the internat memory of phone.i just gave you an example.
it's easier to rename the file you are transfering to a short name and put it on root of partition.this way there are less chances to get syntax errors.
Click to expand...
Click to collapse
Sounds pretty good, but how do I install adb?
GIYF.
Sent from LG E975 pwd by CM 10.1
nice to see i am not the only one, getting this, from rom cm-10.1-20130704-NIGHTLY-e975.zip to cm-10.1-20130708-NIGHTLY-e975.zip i get this i haven't tried cm-10.1-20130709-NIGHTLY-e975.zip that got out today.
I was running Candy5 ROM ver. 2.5 and saw the thread for the 4.0 ROM. I downloaded it and Gapps and put it on the Fire HD. Rebooted into Recovery and into TWRP. That's when I did one of the most stupid things that I've ever done. I wanted a clean install from scratch. Unfortunately, I erased everything! When I realized what happened I rebooted and the screen goes through the two fire HD logos stopping at the last one. Is there ANYTHING I can do to get an operating Fire HD back up and running, Please!
rebelduke said:
I was running Candy5 ROM ver. 2.5 and saw the thread for the 4.0 ROM. I downloaded it and Gapps and put it on the Fire HD. Rebooted into Recovery and into TWRP. That's when I did one of the most stupid things that I've ever done. I wanted a clean install from scratch. Unfortunately, I erased everything! When I realized what happened I rebooted and the screen goes through the two fire HD logos stopping at the last one. Is there ANYTHING I can do to get an operating Fire HD back up and running, Please!
Click to expand...
Click to collapse
Try to reboot into TWRP (press + hold volume up as soon as you see the first logo, keep holding till you see the TWRP curtain). If you are successful, copy a ROM zip into the kindle's internal storage (gapps are optional, but I recommend you flash them along with your chosen ROM), flash it, reboot, and cross your fingers.
Thank you. I'm making some progress. Your instructions got me into TWRP (ver. 2.8.6). Next step is to get the PC to allow copying of the ROM file. TWRP does recognize that there is no operating system installed. Thanks again!
rebelduke said:
Thank you. I'm making some progress. Your instructions got me into TWRP (ver. 2.8.6). Next step is to get the PC to allow copying of the ROM file. TWRP does recognize that there is no operating system installed. Thanks again!
Click to expand...
Click to collapse
If you can't directly copy it, try adb sideload path/to/ROM.zip (enable sideloading in the advanced menu in TWRP first, or you'll get an error). Make sure you have adb drivers installed and working if your PC's running Windows. Good luck!
monster1612 said:
If you can't directly copy it, try adb sideload path/to/ROM.zip (enable sideloading in the advanced menu in TWRP first, or you'll get an error). Make sure you have adb drivers installed and working if your PC's running Windows. Good luck!
Click to expand...
Click to collapse
Adb sideload worked with the Candy5 4.0 ROM. The Gapps zip failed due to the file size being too great. I can tackle that after the ROM is installed. Another stupid question - any idea where the sideloaded ROM zip file would be internally? I explored using the TWRP file manager and all I have is the directory structure - no actual files. I probably looked in 50+ folders and they were all empty. I think there must be hundreds of directories and subdirectories. I found one folder named sideload thinking I had it but no luck. Worst case I can open every folder and hopefully find the ROM zip file.
rebelduke said:
Adb sideload worked with the Candy5 4.0 ROM. The Gapps zip failed due to the file size being too great. I can tackle that after the ROM is installed. Another stupid question - any idea where the sideloaded ROM zip file would be internally? I explored using the TWRP file manager and all I have is the directory structure - no actual files. I probably looked in 50+ folders and they were all empty. I think there must be hundreds of directories and subdirectories. I found one folder named sideload thinking I had it but no luck. Worst case I can open every folder and hopefully find the ROM zip file.
Click to expand...
Click to collapse
From the TWRP FAQ for the sideloading feature:
TWRP versions 2.8.2.0 and higher will stream the zip from your PC without storing it on your device. If you wish to store the zip on your device for later, you should not use sideload and instead use adb push or some other method to copy the zip to the device.
Click to expand...
Click to collapse
Older TWRP versions used to store the zip file in /sdcard/sideload, but I think versions 2.8.2.0 and higher use it as a temporary buffer and delete the zip after flashing. If you're able to get Android up and running, then you should be able to connect it to your PC, copy the ROM and gapps zips over to the kindle without using adb, and flash the gapps.
monster1612 said:
From the TWRP FAQ for the sideloading feature:
Older TWRP versions used to store the zip file in /sdcard/sideload, but I think versions 2.8.2.0 and higher use it as a temporary buffer and delete the zip after flashing. If you're able to get Android up and running, then you should be able to connect it to your PC, copy the ROM and gapps zips over to the kindle without using adb, and flash the gapps.
Click to expand...
Click to collapse
Thanks very much for all of your advice and suggestions! I'm back up and running. The gapps package was causing an error 70 message. Once I found a smaller file it worked. It certainly was an excellent learning experience. Thank you again.