hey guys im a long time reader here. and i think i bricked my brand new verizon nexus. i just got done doing super boot to unlock it and also put clock mod on there. and now the phone will not boto past the word google. just stays on google for a min or so then reboots. im not sure what to do beause there is no sd card to mount (i dont know how to mount it its not working in recvovery mode.) can any one help me with a step by step to fix this. i cant fugure it out. i guess that was a dumb move on my part. =( please help!
I had this same issue, unlocked the bootloader, but then it would not boot past the white google. I tried so many things. Here is how I fixed mine.
First install 7zip or some sort of program that can deal with .tar and .tgz files assuming you don't already have it.
Download the stock image for your phone, I assume you are talking about the Galaxy Nexus LTE Verizon phone. Get that from here You need the mysid version, not the yakju. For a direct link to download the mysid version, click here
Extract that file to your desktop or wherever, you will have a file called "mysid-icl53f-factory-65895fa8.tar" then extract that so you have the following files visable:
bootloader-toro-primekk15.img
flash-all.sh
image-mysid-icl53f.zip
radio-cdma-toro-i515.ek05.img
radio-toro-i515.ek02.img
You can DELETE the radio-cdma-toro file, you don't need it for the LTE version (i hope, haha)
Put these files in your C:/android-sdk-windows/platform-tools folder. Do NOT further unzip the image.mysid zip file.
Put your phone into bootloader menu, plug in your USB cable to your computer, start your command prompt inside the platform-tools folder (in white space, shift+right click).
Type the following (taken from this thread and modified with correct file names)
Assuming you have windows computer
fastboot flash bootloader bootloader-toro-primekk15.img
fastboot reboot-bootloader
fastboot flash radio radio-toro-i515.ek02.img
fastboot reboot-bootloader
fastboot -w update image-mysid-icl53f.zip
This took a few mins to install, And my phone then rebooted itself and worked! (I don't think I had to manually reboot it).
It took me 5 good hours to find all this info and finally get my phone working again, hope it works for you! I was in a panic, that's for sure!
Btw, the phone's bootloader is still unlocked, but I have not yet tried to gain root access.
Please let me know if this worked for you.
Ive done the same
Can you post what I would need to put in terminal for mac. Im kinda new to this
Hahahahahahahahahahahahahahaahahahahah not even a day
nononononono the same thing happened to me!!
Just do a battery pull and put it back in!
doublea500 said:
nononononono the same thing happened to me!!
Just do a battery pull and put it back in!
Click to expand...
Click to collapse
It does not work for some people. I let mine sit for a half hour and did at least 20 battery pulls. It never went past the white google screen
---------- Post added at 04:13 AM ---------- Previous post was at 04:11 AM ----------
cvv1984 said:
Can you post what I would need to put in terminal for mac. Im kinda new to this
Click to expand...
Click to collapse
I linked to the thread where I got the commands in my post.. anyways.. replace the file names with the ones as above
For OSX, replace "fastboot" with "./fastboot" (i would assume)
Well this did nothing for me. Got to the stage where it rebooted the phone, everything was looking good and reading as "okay" in command prompt. Then when it went to reboot it went right back to google screen. It shows the google logo for about five seconds, then it shuts off for a second, vibrates and logo comes back on. I am at a loss here and don't know what else I can do to fix this thing.
And yes, I just got it today
I followed the instructions to reimage back to stock and still have the same problem. As sublimejhn says it just keeps rebooting in that initial start up screen. Not a fun night.
SlopeSurfer said:
I followed the instructions to reimage back to stock and still have the same problem. As sublimejhn says it just keeps rebooting in that initial start up screen. Not a fun night.
Click to expand...
Click to collapse
I'll keep you posted if I make any progress if you'll do the same!! I have never had an issue rooting, installing roms or anything else on any other phone until now. This is not exactly the phone I want to have bricked, hopefully we can figure this out
Same Problem here, just hangs forever (15min+) at the Google splash screen.
I think I found the problem with mine. I cant mount (or do anything) with the /data part of the phone.
I think its corrupted or something. I realized this when I was trying to do a nandroid restore/backup and could never mount or format the /data
--------edit----------
What Easyski posted work like a charm for me. Thx dude
fly_guy said:
Same Problem here, just hangs for ever (15min+) at the Google splash screen.
I think I found the problem with mine. I can mount (or do anything) with the /data part of the phone.
I think its corrupted or something. I realized this when I was trying to do a nandroid restore/back and could never mount or format the /data
--------edit----------
What Easyski posted work like a charm for me. Thx dude
Click to expand...
Click to collapse
Well that's cool. I have tried it 3 times now and it's a no go for me, but good to hear someone got theirs working again. Now if only the rest of us could get out of this!! At this point I don't even care about root, I just want my phone back
before I tried his steps I flash the stock recovery, stock boot.img, and lock it back.
so maybe try doing that, then use the steps above. I was about to give up myself. Was doing one last scroll of the forums when I saw this thread
Ok, got mine working now. Not sure why this helped, but here's what I did, I typed everything exactly as follows:
fastboot-windows flash bootloader bootloader-toro-primekk15.img
fastboot-windows reboot-bootloader
fastboot-windows flash radio radio-toro-i515.ek02.img
fastboot-windows reboot-bootloader
fastboot-windows -w update image-mysid-icl53f.zip
I don't know if it is the fact that I wasn't using fastboot-windows (can't see why that would matter, since both fastboot and fastboot-windows appear to be the same file), or the addition of that stupid '-w' before the update (got this from another thread), or if the 5th time was just a charm!! But either way, hopefully someone else can get up and running now too
yea 'fastboot' wouldnt work for me, had to use 'fastboot-windows.exe'
I guess the 5th time is a charm. It's working. I didn't think it was going to at first. It did get in the boot animation but then restarted over again. After looping in the boot animation for awhile if finally finished and started working. The only thing I did different on the 5th try was put in the "-w" on the image update.
Persistence counts. Thanks for all the support.
SlopeSurfer said:
I guess the 5th time is a charm. It's working. I didn't think it was going to at first. It did get in the boot animation but then restarted over again. After looping in the boot animation for awhile if finally finished and started working. The only thing I did different on the 5th try was put in the "-w" on the image update.
Persistence counts. Thanks for all the support.
Click to expand...
Click to collapse
that -w makes all the difference.
easyski said:
I had this same issue, unlocked the bootloader, but then it would not boot past the white google. I tried so many things. Here is how I fixed mine.
First install 7zip or some sort of program that can deal with .tar and .tgz files assuming you don't already have it.
Download the stock image for your phone, I assume you are talking about the Galaxy Nexus LTE Verizon phone. Get that from here You need the mysid version, not the yakju. For a direct link to download the mysid version, click here
Extract that file to your desktop or wherever, you will have a file called "mysid-icl53f-factory-65895fa8.tar" then extract that so you have the following files visable:
bootloader-toro-primekk15.img
flash-all.sh
image-mysid-icl53f.zip
radio-cdma-toro-i515.ek05.img
radio-toro-i515.ek02.img
You can DELETE the radio-cdma-toro file, you don't need it for the LTE version (i hope, haha)
Put these files in your C:/android-sdk-windows/platform-tools folder. Do NOT further unzip the image.mysid zip file.
Put your phone into bootloader menu, plug in your USB cable to your computer, start your command prompt inside the platform-tools folder (in white space, shift+right click).
Type the following (taken from this thread and modified with correct file names)
Assuming you have windows computer
fastboot flash bootloader bootloader-toro-primekk15.img
fastboot reboot-bootloader
fastboot flash radio radio-toro-i515.ek02.img
fastboot reboot-bootloader
fastboot update image-mysid-icl53f.zip
This took a few mins to install, And my phone then rebooted itself and worked! (I don't think I had to manually reboot it).
It took me 5 good hours to find all this info and finally get my phone working again, hope it works for you! I was in a panic, that's for sure!
Btw, the phone's bootloader is still unlocked, but I have not yet tried to gain root access.
Please let me know if this worked for you.
Click to expand...
Click to collapse
Hi Guys,
I'm afraid I have the same problem. I was downloading on my Galay Nexus.(GSM version) since I'm in the Netherlands and suddenly the phone rebooted on it's own. Now the phone keeps on rebooting on the splash screen. The bootloader is unlocked and the phone has been rooted. I would like to follow the instructions above only I need the GSM version of the rom of the galaxy nexus. Does anybody have a link to that
Any help would be very much appreciated
Thanks a lot
Edit:addtional information When I try to restore a backup an error is given when trying to restore perhaps something is wrong with the memory?
Looking at all the problems people seem to have gotten from Superboot, I'm glad I rooted mine manually.
Educational with the added bonus of knowing that you cannot **** up your phone like this in the process.
Also: Seriously lol at the phone is available in the US for -1- day and XDA is already filled with "OMG i bricked/ruined my phone"-threads.
You guys are teh best!
josteink said:
Looking at all the problems people seem to have gotten from Superboot, I'm glad I rooted mine manually.
Educational with the added bonus of knowing that you cannot **** up your phone like this in the process.
Also: Seriously lol at the phone is available in the US for -1- day and XDA is already filled with "OMG i bricked/ruined my phone"-threads.
You guys are teh best!
Click to expand...
Click to collapse
The same thing happened on the Galaxy S2 thread when that first got released loads of people bricked their phones by messing about.
I guess some peeps have money to burn!
odd error on update step
I did get an odd error on the update step...
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
but it still installed those in the update sequence...
it seemed to work, but should i be worried?
Related
Hi people. I've just s-off'd my phone. I am now desperate to get all the new space.
However, when i try to use the rename to "PM99IMG.zip" etc, the file is not recognised and i have tried every thing else, remamed it without the zip on the on the end used my goldcard. For whatever reason it won't work.
So, i am going to use ADB.
But i ain't confident with this aspect of andriod, never used a command line in my life, apart from creating my goldcard.
I was kind hoping some kind soul would help me out. I know that there are post on this but i cannot figure them out.
For example after cd ing in to sdk tools and then specifying the file path, there is an instruction "Fastboot reboot-bootloader" . Thats all. Is that a command or someting else. I would massively appreciate any help.
Thanx in advance
Well that is a command yes. But first test if fastboot and adb commands is working by entering the following(after cd'ing into the folder):
"adb devices" (done while the device is booted, and should output your device id if working)
If this works, please enter:
"adb reboot bootloader" (this will make the device reboot to bootloader and you should see the fastboot screen)
Now enter:
"fastboot devices" (again you should see your device listed if it works)
If it worked, you can now flash the new hboot:
"fastboot flash hboot bootloader.img"
Where "bootloader.img" is the path to the img file on your computer.(it's VERY important this is a correct hboot image because otherwise you'll end up with a device that won't ever turn on again due to missing bootloader)
edit:
you can now enter:
"fastboot reboot-bootloader" (to reboot the bootloader so now the screen should show the info of your new hboot)
do "fastboot reboot" to go back to system, but you'll probably need to reflash your system after this procedure.
hi,
agree with motenmhp,
a details, he just fogot the following:
fastboot reboot-bootloader
fastboot erase cache
I would advice to use cmd line (faster and easer) however zip from sd-card should be rename. be caution to download the right bootoader as mortenmhp said...
rename the zip file as PB99IMG.zip and reboot. should be detected by bootloader and flash process start from this.
hope this help
However neither is necessary. There should be no reason to clear cache and rebooting the bootloader is just for seeing if it worked(actually never did this myself, but mentioned it in my edit before you posted )
thanx for your quick replys, you guys have helped me on this whole process. much appreciated.
Just wanted to check. In "bootloader.img" i would put "c:\PM99IMG.zip",(i have changed the name and put in the root of my c drive for ease of use). Do i need o add the ".zip" in the command?
Edit:
I have done all of the test steps and every thing is fine! Just about to do the next bit. Thus the clarification.
2nd Edit: After fastboot devices i get "SH117PL08127 fastboot". Is this correct? Sorry, don't mean to be demanding, but really nervous not to mess up my phone!
copernicus666 said:
thanx for your quick replys, you guys have helped me on this whole process. much appreciated.
Just wanted to check. In "bootloader.img" i would put "c:\PM99IMG.zip",(i have changed the name and put in the root of my c drive for ease of use). Do i need o add the ".zip" in the command?
Edit:
I have done all of the test steps and every thing is fine! Just about to do the next bit. Thus the clarification.
Click to expand...
Click to collapse
If you want to flash if with fastboot, then you have to download hboot .img file from Alpharev, flashing .zip under fastboot wont work and might end up really bad...
Just pray to not have power outtage hehehe..
Sorry wrote that wrong. I have downloaded the IMG, just changed the name did not include the zip bit.
copernicus666 said:
2nd Edit: After fastboot devices i get "SH117PL08127 fastboot". Is this correct? Sorry, don't mean to be demanding, but really nervous not to mess up my phone!
Click to expand...
Click to collapse
That's fine dont worry.
Also i dont see why would you be nervous, sometimes im changing hboot few times a week using third party tools lol. (custom hboots)
Really difficult to screw up. ;-)
copernicus666 said:
thanx for your quick replys, you guys have helped me on this whole process. much appreciated.
Just wanted to check. In "bootloader.img" i would put "c:\PM99IMG.zip",(i have changed the name and put in the root of my c drive for ease of use). Do i need o add the ".zip" in the command?
Edit:
I have done all of the test steps and every thing is fine! Just about to do the next bit. Thus the clarification.
2nd Edit: After fastboot devices i get "SH117PL08127 fastboot". Is this correct? Sorry, don't mean to be demanding, but really nervous not to mess up my phone!
Click to expand...
Click to collapse
Well then that is why you couldn't get the zip file working...
There are 2 files on the site. One in zip format for flashing using the "PB99IMG.ZIP" method and one in .img format for flashing using fastboot commands. Renaming the .img to .zip will not make it a zip file.
But just make sure it's the right one you downloaded(the .img one) and don't rename it. If it's the wrong one, it'll just flash it anyway, and you'll end up with a device that will not come back to life.
THANK YOU!! You guy really know your stuff. All done. Gone from s-on to s-ff and oxygen hboot in 24 hrs. Much and much appreciated
Edit: Just seen your post. i double checked and triple check. i had zip for the easy way and then went back and downloaded img for ADB. Just ignore my post there the whole thing was backward. got mixed up for a second by reading the second reply. it mentions zips.
No problem now dont forget to full wipe/factory reset and cache + dalvik wipe in recovery prior to flashing new ROM.
Also when you'll encounter some reception problems (sometimes it happens when you upgrade to Gingerbread with old radio) you might aswell need to update it, you do it same way as hboot just different command.
fastboot flash radio radio.img
Latest radio images can be found on forums.
I am not taking credit for this in anyway. But since i had to to it and had never done it before i had to look around on how to do it.
This is pulled from
http://www.droid-life.com/2011/12/1...the-bootloader-and-return-to-a-factory-state/
1. Download the Android 4.0.2 factory images to your PC. Download
2. Unzip the file and its contents into your SDK/Tools folder (wherever your adb.exe and fastboot.exe files
are).
*Make sure they are not in their own folder, but have all been extracted to Tools.
3. From within your Tools folder, open a command prompt (SHIFT + right click – “open command prompt here”):
4. Type the following commands, allowing each to finish before moving onto the next:
adb reboot bootloader
fastboot flash bootloader bootloader-toro-primekk15.img
fastboot reboot-bootloader
fastboot flash radio radio-toro-i515.ek02.img
fastboot reboot-bootloader
fastboot flash radio-cdma radio-cdma-toro-i515.ek05.img
fastboot reboot-bootloader
fastboot -w update image-mysid-icl53f.zip
fastboot reboot-bootloader
fastboot oem lock
5. Reboot your phone by highlighting “Start” and pressing the lock switch.
6. It really is as simple as that. Your phone is now back to a 100% stock, unrooted and locked state.
thanks.. nice work
Eh... All I'd want is the back cover with just a Google logo, at this point in time I don't even care if there's bloat. Great guide though, might do it if I'm bored.
Would the files being extracted into tools have anything to do with the files used to root if i decided to re-root? Also my adb.exe and fastboot.exe are in the /platform-tools folder is that ok?
this should get sticky'd in case it becomes an "emergency" in the future and the thread's gotten burried.
how do i get the zip format
i can download the file but it doesnt come as a zip file? im on windows vista.
mikedfromaz said:
i can download the file but it doesnt come as a zip file? im on windows vista.
Click to expand...
Click to collapse
Popular tools like winrar and 7zip will still be able to extract it.
7zip
so i got 7zip to load but the second prompt in the sequence says error cant load bootloader-prime image??
i couldnt see the folder with all the files using winrar, i recommend using 7zip only
I tried these steps 3 times now. Everything seems to go just fine until I'm booted. Cant get a data signal on 3g/4g. Calls/text messages come through fine just missing something with the radios. Anyone else have this problem?
Same issue here. I've tried recovering to a different back up. Also updated radio to the newer leaked ones. Eventually reverted everything back to stock and I am STILL without any data connection.
Rageful said:
Same issue here. I've tried recovering to a different back up. Also updated radio to the newer leaked ones. Eventually reverted everything back to stock and I am STILL without any data connection.
Click to expand...
Click to collapse
I am in NYC and I do not have any data connection either....
I think (hope) it is a Verizon Network issue!!!
Verizon is having a nationwide outage, it affects everyone differently so no worries about loss of data access.
http://phandroid.com/2011/12/21/yes-verizons-data-network-is-experiencing-nationwide-outages-again-new-radios-for-galaxy-nexus-leak-in-the-meantime/
i did all of this this morning, but now everey time i do fastboot reboot-bootloader. i get a waiting for device. prior to this i was able to reboot the bootloader through adb just fine. both of my pc's have the same problem. Is there a problem with the bootloader on the image uploaded versus the one the phone came with? iknow i can boot to the bootloader with vol+ vol- and power. but its just better to doit trough adb. please advice.
Does this also restore the stock recovery? I don't see any fastboot commands to flash recovery. Or is that included in the stock img?
It's in the zip file when you run "fastboot -w update image-mysid-icl53f.zip"
Thank you so much for this! I was trying to root my phone and somehow managed to screw something up and wound up with an infinite boot loop. Followed these simple steps and was able to successfully get out of that mess.
So this puts the stock kernel back on there as well right?
GazaIan said:
Eh... All I'd want is the back cover with just a Google logo, at this point in time I don't even care if there's bloat. Great guide though, might do it if I'm bored.
Click to expand...
Click to collapse
Same here man. I'm coming from a Nexus One on at&t and I hate how Verizon has to put their branding on everything.
Does this still work if I have cwm and a different rom installed or are there more steps to do?
Sent from my Galaxy Nexus using xda premium
Hi I attempted to root my phone, got SU but was having problems flashing any roms, using any apps that required /root or accessing recovery. Figured something might not have worked and tried to unroot and start again. All steps were followed via http://forums.androidcentral.com/ve...-root-unroot-unlock-your-vz-galaxy-nexus.html
I'm stuck in the Google bootscreen with my only other option being bootloader, it still says Locked State - Unlocked. But my computer can't see my phone, Odin doesn't work and I still don't have a definitive method of restoring my phone via a MAC.
This ISN'T Resolved. I get errors when attempting to fastboot the stock image
~/Desktop/adb-fastboot/adb reboot bootloader
brings about the following error
"error: device not found"
I was already in bootloader and tried:
~/Desktop/adb-fastboot/fastboot flash boot ~/Desktop/adb-fastboot/boot.img
I get:
error: cannot load '/Users/grnmons/Desktop/adb-fastboot/boot.img'
If anybody has any ideas please let me know, I really don't know what to do at this point.
grnmons said:
Hi I attempted to root my phone, got SU but was having problems flashing any roms, using any apps that required /root or accessing recovery. Figured something might not have worked and tried to unroot and start again. All steps were followed via http://forums.androidcentral.com/ve...-root-unroot-unlock-your-vz-galaxy-nexus.html
I'm stuck in the Google bootscreen with my only other option being bootloader, it still says Locked State - Unlocked. But my computer can't see my phone, Odin doesn't work and I still don't have a definitive method of restoring my phone via a MAC.
If anybody has any ideas please let me know, I really don't know what to do at this point. Plan B is to use a PC which I can only access later in the week. If you know someone, or have a link I would really appreciate it. Also ask me anything if it can help make this clearer.
Thanks
Click to expand...
Click to collapse
Okay your bootloader is unlocked which is good, but your MAC doesn't see your phone in bootloader mode?
grnmons said:
Plan B is to use a PC which I can only access later in the week.
Click to expand...
Click to collapse
Can you bootcamp or use a virtual machine?
grnmons said:
Hi I attempted to root my phone, got SU but was having problems flashing any roms, using any apps that required /root or accessing recovery. Figured something might not have worked and tried to unroot and start again. All steps were followed via http://forums.androidcentral.com/ve...-root-unroot-unlock-your-vz-galaxy-nexus.html
I'm stuck in the Google bootscreen with my only other option being bootloader, it still says Locked State - Unlocked. But my computer can't see my phone, Odin doesn't work and I still don't have a definitive method of restoring my phone via a MAC.
If anybody has any ideas please let me know, I really don't know what to do at this point. Plan B is to use a PC which I can only access later in the week. If you know someone, or have a link I would really appreciate it. Also ask me anything if it can help make this clearer.
Thanks
Click to expand...
Click to collapse
Wrong section..but
I would def use a PC and use Odin ! Make your life easier...it takes like 3-5 Mins..takes it to stock!
Sent from my Galaxy Nexus using xda premium
All you have to do is fastboot flash those stock images of 4.0.2 google gave us. There's not even any need for Odin. You can do this right on your Mac.
Sent from my Galaxy Nexus using Tapatalk
Please uninstall and reinstall your phones drivers. Your just soft bricked is all. Once your computer sees the device you should be good.
sent from the Almighty One himself....
borgey said:
All you have to do is fastboot flash those stock images of 4.0.2 google gave us. There's not even any need for Odin. You can do this right on your Mac.
Click to expand...
Click to collapse
I can't seem to figure out how to do that. Seems like that's what got me here in the first place, the mac version might be missing files I'm missing the steps to actually do that.
Can't find any forum/site/guide that tells me how to do that. Does anybody have this?
grnmons said:
I can't seem to figure out how to do that. Seems like that's what got me here in the first place, the mac version might be missing files I'm missing the steps to actually do that.
Can't find any forum/site/guide that tells me how to do that. Does anybody have this?
Click to expand...
Click to collapse
fastboot flash (google on how to use these)
you do them when you're in bootloader mode. you need to have a ADB/Fastboot environment set up (look at root guides and do step one of it..... verifying the part of getting the environment, ignore drivers)
stock images are here: http://code.google.com/android/nexus/images.html
zephiK said:
fastboot flash (google on how to use these)
you do them when you're in bootloader mode. you need to have a ADB/Fastboot environment set up (look at root guides and do step one of it..... verifying the part of getting the environment, ignore drivers)
stock images are here: http://code.google.com/android/nexus/images.html
Click to expand...
Click to collapse
Thanks. Can you confirm that these are the steps?
1) Download the latest stock image( i will leave finding that image to you since this post can become outdated)
2) Unzip the files, and place the images into the adb-fastboot folder you created on your desktop above.
3) Open a terminal and use the following commands:
Code:
~/Desktop/adb-fastboot/adb reboot bootloader
4) Wait for bootloader to reboot on phone.
5) Then, in terminal use the following commands:
~/Desktop/adb-fastboot/fastboot flash boot ~/Desktop/adb-fastboot/boot.img
~/Desktop/adb-fastboot/fastboot flash system ~/Desktop/adb-fastboot/system.img
~/Desktop/adb-fastboot/fastboot flash recovery ~/Desktop/adb-fastboot/recovery.img
~/Desktop/adb-fastboot/fastboot flash userdata ~/Desktop/adb-fastboot/userdata.img
~/Desktop/adb-fastboot/fastboot erase cache
~/Desktop/adb-fastboot/fastboot oem lock
6) Reboot to System, and you should be returned to Stock and Unrooted
~/Desktop/adb-fastboot/adb reboot bootloader
brings about the following error
"error: device not found"
I was already in bootloader and tried:
~/Desktop/adb-fastboot/fastboot flash boot ~/Desktop/adb-fastboot/boot.img
I get:
error: cannot load '/Users/grnmons/Desktop/adb-fastboot/boot.img'
anybody have any other suggestions to this? or a follow up?
It should be easy to fix. You do not seem to have the correct driver installed.
Sent from my Galaxy Nexus using xda premium
Understood, I think I definitely did a few things wrong here. But my problem requires some kind of steps to solve. I don't mean to sound lazy but I've been running around the forums for awhile and I'm in way over my head, I was hoping someone could just list a few steps, links, SOMETHING. I'm looking for solvency here.
grnmons said:
Understood, I think I definitely did a few things wrong here. But my problem requires some kind of steps to solve. I don't mean to sound lazy but I've been running around the forums for awhile and I'm in way over my head, I was hoping someone could just list a few steps, links, SOMETHING. I'm looking for solvency here.
Click to expand...
Click to collapse
reinstall the android sdk from here that will get your drivers in order so your computer can see your phone
then fastboot flash recovery
then manually flash su (attached)
ogdobber said:
reinstall the android sdk from here that will get your drivers in order so your computer can see your phone
then fastboot flash recovery
then manually flash su (attached)
Click to expand...
Click to collapse
Thanks muchly, I feel like I'm getting closer but could you elaborate on the manual flash su step? My **** is all over the place now, my desktop is littered with files, should I be in recovery for this or still fastboot? and what is the command if you have?
grnmons said:
Thanks muchly, I feel like I'm getting closer but could you elaborate on the manual flash su step? My **** is all over the place now, my desktop is littered with files, should I be in recovery for this or still fastboot? and what is the command if you have?
Click to expand...
Click to collapse
download the gnex-su.zip and put in in the root of your sd card. then in recovery select "-install zip from sdcard" then "-choose zip from sdcard" then select the gnex-su.zip. this will give you root and install the superuser app
not to get ahead (previous post), but after your computer recognizes the phone you need to flash clockwork recovery
you need to open a terminal in the platform-tools folder of the sdk (also put the recovery.img there) and then
Code:
fastboot flash recovery name-of-recovery.img
Thanks for your help ogdobber, I'm incredibly frustrated and you must be too trying to help me, but I must have done something wrong as after I flash recovery, i still cannot access it - it continues to hang out in the Google screen.
Let me go through my steps with you and you tell me what I might have done wrong. So with my bricked phone, 1. I clicked your link and updated my SDK.
There's no indication that I did anything right here, it just shows that everything is installed and that's all I think I need here.
2. Opened up terminal fastboot flash boot (in this case) bootloader-toro-primekk15.img DONE!
3. Fastboot flash recovery (in this case) recovery-clockwork-5.0.2.0-crespo.img
DONE!
Then... nothing. Recovery doesn't load for me. Just get a boot loop. Anything I might have done wrong prior or inbetween these steps? Also, besides flashing and running commands off terminal - i assume this is considered computer recognizes my phone. Could the problem be there?
Just got your last post, I'm unfamiliar with SDK but I've since put the recovery file in there, not sure how to flash recovery. I have tried flashing recovery through terminal and surprisingly it says "-bash: fastboot: command not found"
grnmons said:
Thanks for your help ogdobber, I'm incredibly frustrated and you must be too trying to help me, but I must have done something wrong as after I flash recovery, i still cannot access it - it continues to hang out in the Google screen.
Let me go through my steps with you and you tell me what I might have done wrong. So with my bricked phone, 1. I clicked your link and updated my SDK.
There's no indication that I did anything right here, it just shows that everything is installed and that's all I think I need here.
2. Opened up terminal fastboot flash boot (in this case) bootloader-toro-primekk15.img DONE!
3. Fastboot flash recovery (in this case) recovery-clockwork-5.0.2.0-crespo.img
DONE!
Then... nothing. Recovery doesn't load for me. Just get a boot loop. Anything I might have done wrong prior or inbetween these steps? Also, besides flashing and running commands off terminal - i assume this is considered computer recognizes my phone. Could the problem be there?
Click to expand...
Click to collapse
that is for the nexus s
check your pm
ogdobber said:
that is for the nexus s
check your pm
Click to expand...
Click to collapse
If you are still having problems ...like I said before ...use Odin......since the simple process of fastboot is not working properly for you.Odin makes things so Much easier
Sent from my Galaxy Nexus using xda premium
Hello everybody,
This is my first post on XDA, although I've visited the site oftne
Anyways:
Yesterday I successfully rooted my One X and unlocked its bootloader. I also installed CWM recovery.
As the day came to a close I tried to install LC_MOD in an attempt to change the multitasking softkey to a menu button.
I did not make a backup, and the phone had no backups.
Needless to say the phone wouldnt boot. I panicked and in blind fear sortof erased everything off of my phone. everything. What I basically did was i went into advanced settings and formatted my /sdcard and all those other folders, hoping that would solve the issue (a simple data/cache wipe didnt work). So much data has been erased from the phone that I cannot even mount usb storage through CWM because im missing a file.
So, I come to you all, you gods of the tech world, with my head bowed, to ask for your help. I have literally tried everything in my power to fix the issue. I tried to install custom roms manually, that didnt work. I tried to install an RUU, and even that didnt work (the software could not detect my device). This was all made even more difficult because I myself have a mac, and much of the software I had to use was windows based, which led me on a journey to create a virtual machine.
I know i messed up, and what I'm really hoping someone out there cn do is upload one of their own backups of their One X's software, and show me how to use that to restore my phone.
Somebody out there please please help me :'(
Hi;
There is a reason all developers here shout out loud:
1- BACKUP YOUR PHONE BEFORE YOU F*** IT UP
2- DO NOT DO ANYTHING UNLESS YOU ABSOLUTELY KNOW HOW TO
But anyways, you ruined it, you should get it back, Hopefully you did not drain the battery below 30%, in that case keep on reading the next paragraph, but if you dropped the battery below 30, you should go to CWM Recovery, connect your phone to charger, and wait until it's charged properly...
After charging the phone, you need the correct RUU for your phone... As it seems, you don't know what you're doing, so go to fastboot, type this command:
Code:
fastboot oem readcid
Then post the code here in this topic, so someone can help you find the correct RUU for your phone...
After that go to THIS topic and follow the part where it says "If you DON'T have custom rom or Nandroid backup on internal SD card"
Thanks
Thanks a bunch bro!! And ye i get that it was completely my fault. I normally do backup before i do anything, but i guess i was just a bit too anxious. And I think you've told me everything i need to know, ill get that code out to you asap... And you're right, i seriously have no clue what im doing ^.^, I've never F***ed up this hard on any phone before
Xial649 said:
Thanks a bunch bro!! And ye i get that it was completely my fault. I normally do backup before i do anything, but i guess i was just a bit too anxious. And I think you've told me everything i need to know, ill get that code out to you asap... And you're right, i seriously have no clue what im doing ^.^, I've never F***ed up this hard on any phone before
Click to expand...
Click to collapse
Don't worry, with the correct version of RUU you can restore your phone...
Sent from my HTC One X using XDA
Next?
Alright I got the code:
<bootloader> DEBUG: cid: VODAP102
Whats next?
Xial649 said:
Alright I got the code:
<bootloader> DEBUG: cid: VODAP102
Whats next?
Click to expand...
Click to collapse
Your phone is from Voda Germany, and most probabely your correct RUU is this:
Code:
http://www.filefactory.com/file/t7qugfd3ey9/n/RUU_ENDEAVOR_U_ICS_40_Vodafone_CH-DE_1.26.166.2_Radio_1.1204.90.13_release_251279_signed.exe
Download it. Hopefully it would be the correct RUU for your phone.
1- Now open the exe file you just downloaded and make sure that it fully started.
2- Don't click anything, just open "Computer" (formerly known as my computer) in windows and enter %temp% in your address bar.
3- You will now see some folders, just search through these folders for the ROM.zip (using windows search function)
4- When you found it, copy it to your desktop.
5- Extract it with WinRar,7-zip or something like that and take the boot_signed.img and system.img.
6- Now copy the two files into the folder where the fastboot.exe is placed (if you have installed the Android SDK, it should be in platform-tools)
7- Go to your One X, go into the bootloader and go into fastboot mode. then connect your phone to computer.
8- Open CMD and navigate to the folder in which you have the two images and the fastboot file. (using cd command and after that the address you want to go to)
9- Now type in that
Code:
fastboot flash boot boot_signed.img
10- Now this one
Code:
fastboot flash system system.img
if all this is successful, you can just reboot your phone and everything is OK.
If you can't do any of these, let us now, we will help you through it...
Good lock
---------- Post added at 03:52 PM ---------- Previous post was at 03:41 PM ----------
In other note, RUUs are build to do an stand alone recovery of your phone. So you can first try, just running the RUU application and following the instruction given in the RUU. it may work correctly
This is good
Alright so i got everything going after downloading the RUU and it was in the process of restoring my phone, but then it said my battery went below 30% so i needed to recharge. At that point i had to leave, and so I noticed that if i left my phone in the booting animation (HTC logo) the LED light indicated that the phone was charging. Since I wasnt entirely convinced that my CWM recovery was actually charging the phone, i left it on booting while connected to my pc and hopefully itll be fully charged and ready to be restored tomorrow..... I really appreciate all the help you've given me man you've practically saved my life here , and I'd like to say that you've made my first cry for help a simple and smooth one.... Thank you very much my friend :victory: :highfive:
Problem
Ok so we have a new problem, the system.img file didnt flash. I tried and it said "FAILED"
What now??
& is the boot image supposed to only be around 4300 kb?
Could the sending of "system" failed because my phone had less than 30% batterylife???? & if its in Clockworkmod recovery5.8.4 while connected to an outlet will it be charging???
Edit: I've searched around and I saw this one guy who extracted the "boot_signed.img" and the "recovery_signed.img" (NOT the system.img), flashed them onto his phone, locked the bootloader with "fastboot oem lock", and then RAN the RUU..... He said he bricked his phone, and the situation he described is similar to mine. Any thoughts on which method of the two (yours and his) i should use?
Thanks again :3
Xial649 said:
Ok so we have a new problem, the system.img file didnt flash. I tried and it said "FAILED"
What now??
& is the boot image supposed to only be around 4300 kb?
Could the sending of "system" failed because my phone had less than 30% batterylife???? & if its in Clockworkmod recovery5.8.4 while connected to an outlet will it be charging???
Edit: I've searched around and I saw this one guy who extracted the "boot_signed.img" and the "recovery_signed.img" (NOT the system.img), flashed them onto his phone, locked the bootloader with "fastboot oem lock", and then RAN the RUU..... He said he bricked his phone, and the situation he described is similar to mine. Any thoughts on which method of the two (yours and his) i should use?
Thanks again :3
Click to expand...
Click to collapse
That's another method you can try, boot_signed is the stock kernel (and yes it's that small) and the recovery_signed is the stock recovery...
Since my previously mentioned method didn't work, do this:
1- flash the boot_signed.img into your device (fastboot flash boot boot_signed.img)
2- flash the recovery_signed.img in the device (fastboot flash recovery recovery_signed.img)
3- erase cache (fastboot erase cache)
4- lock your phone (fastboot oem lock)
5- now try again to flash the system image (fastboot flash system system.img)
And also, try having around 40% battery to do all this, don't let the battery drops under 30%
ALRIGHT!!!!
alright man!!!! that sounds like a plan... First thing tomorrow I'm going to try this method out.... and btw the RUU you linked me wasnt exactly working right (the software kept saying i had the wrong ruu), so i searched around and found someone with the same CID (VODAP102) and apperantly the uk RUU works fine on it, so i guess ill use that one ye? And btw does the bootloader have to be unlocked before i can flash these items? because i do believe its locked atm....
Xial649 said:
alright man!!!! that sounds like a plan... First thing tomorrow I'm going to try this method out.... and btw the RUU you linked me wasnt exactly working right (the software kept saying i had the wrong ruu), so i searched around and found someone with the same CID (VODAP102) and apperantly the uk RUU works fine on it, so i guess ill use that one ye? And btw does the bootloader have to be unlocked before i can flash these items? because i do believe its locked atm....
Click to expand...
Click to collapse
Your phone is "Vodafone Germany" version and the link I gave you is the "Voda DE" which seems right, but you can try that as well, doesn't heart...
No, for original ROM (RUU) you should have a locked boot-loader, unlocking is just for custom ROMs.
ok
ok so this is what ill do tomorrow:
1) make sure bootloader is unlocked
2) fastboot flash boot boot_service.img
3) fastboot flash recovery recovery_service.img
4) fastboot oem lock
5) fastboot flash system system.img
did i get everything?
Xial649 said:
ok so this is what ill do tomorrow:
1) make sure bootloader is unlocked
2) fastboot flash boot boot_service.img
3) fastboot flash recovery recovery_service.img
4) fastboot oem lock
5) fastboot flash system system.img
did i get everything?
Click to expand...
Click to collapse
The two first commands should work on a LOCKED boot-loader, so I think step 1 would not be necessary... If your phone is locked you should be able to do all steps 2, 3, 5 without problem (step 1 and 4 are the exact opposite of each other and if the phone is locked already I think can be skipped)
ok so its still not working.... I managed to flasht he boot_signed.img and the recovery_signed.img, clear cache and lock the bootloader after it, but i still cannot seem to flash the damn system.img... Any thoughts?
what happens is command prompt stays static for a second and then says sending 'system' (1000596 KB)
FAILED (remore: (00000006))
finished. total time: -0.000s
so? What now??
Xial649 said:
ok so its still not working.... I managed to flasht he boot_signed.img and the recovery_signed.img, clear cache and lock the bootloader after it, but i still cannot seem to flash the damn system.img... Any thoughts?
what happens is command prompt stays static for a second and then says sending 'system' (1000596 KB)
FAILED (remore: (00000006))
finished. total time: -0.000s
so? What now??
Click to expand...
Click to collapse
Any luck in running the RUU itself directly?
i gave up
alright so nothig worked. Not the manual flash, and not the RUU itself. So ive resolved to visit my local help center for HTC devices, and see what they can do, if they cant fix it the least they can do is send it to the german branch for repairs. Thanks for all your help mate, you've really proven to be a great guide, but I guess something just isnt clicking in this case :/.......... i love u man
I'm not sure if this would work.
If you are still htcdev unlocked:
1. Enter bootloader in fastboot usb
2. Fasboot flash recovery -your recovery .img here"
3. Boot into recovery
4. Go to "mounts and storage"
5. Mount SD(I think this is right) and your sd should show up in your pc
6. Copy your rom zips and other zips you need/want
7. Unmount SD
8. By this time you should be able to flash your rom
9. Make sure you flash boot.img again in bootloader.
Hope this helps
Sent from my HTC One X using xda app-developers app
Isn't it mount usb storage?
Sent from my HTC One X using XDA Premium App
You couldn't mount the USB storage / sdcard because you were running CWM from the bootloader. If you connect it to the pc you can put the recovery file you flashed into the fastboot folder and do:
fastboot boot *recoveryfilename*.img
Then you can mount the sdcard etc.
If you have photos and things you don't want an ruu to get ride of, you can fix the ROM. You broke it by trying to install an deodrexed mod for an odexed Rom. If you're interested I can tell you how to fix it.
You could also take this opportunity to install a custom Rom, with which I can also help.
I know the feeling! You're all excited because you just unlocked your One V's bootloader, flashed a recovery, and flashed a steamin' hot new ROM. You boot up for the first time and get ecstatic, the tension building as you put in your Gmail info. You finish the start up but OH NO!!! Your phone reboots! You blame yourself... you blame your cat... you blame your wife... you blame the war in the Middle East. You think, I must've done something wrong! Stupid, stupid, stupid! Don't fret! Take my experience with this quite seriously (despite the jokes). For 2 weeks, I retraced my steps and tried EVERYTHING! I thought it was just the ROM's problem, so I flashed one after another to the same end. Finally, I decided to post a new thread asking for help. Nothing became of the first thread, so I posted a second one. To my great relief, along trotted Curiousn00b. After shoving me in the correct direction, I figured out the rest. A big thanks by the way, Curiousn00b! The following is the method that I used to get my phone to finally run a ROM. Also, a thanks to CafeKampuchia for the quoted directions below.
A few things to make sure you have:
Windows (with Administrator's priveleges)
Fastboot installed and working
Your phone (duh!)
A USB cable
Time and patience
The following quote is from CafeKampuchia's thread over here.
Solution #1
CafeKampuchia said:
Here we go:
1. Download the correct RUU for your device from Football's Primo Shipped ROM Collection.
2. Charge the battery above 50% or for at least one hour. If the battery dies during the flashing process, you could hard brick the phone!
3. Run the RUU until the wizard comes up. While the RUU wizard is open, find the temporary folder it created. (Open Explorer in Windows and type %temp% in the navigation bar.) There will be two folders with long encrypted names. In one of them you will find ROM.zip. Open it with 7zip and extract recovery.img or recovery_signed.img. Put it in the location were you've installed Android SDK tools. This is the stock HTC Recovery and it is needed to run the RUU.
4. Boot the phone into bootloader (power off, hold down volume and press power) and highlight FASTBOOT/B] using the volume rocker and pressing power. Then connect the USB cable. You should see FASTBOOT USB.
5. Open a command prompt in Windows and navigate to the folder where you installed Android SDK tools. Flash the stock recovery extracted in step 3 above using the following command:
Code:
fastboot flash recovery recovery.img
or
Code:
fastboot flash recovery recovery_signed.img
6. Relock the bootloader using the following command:
Code:
fastboot oem lock
Click to expand...
Click to collapse
Thus far you should have the stock recovery back and be bootlocked again. Now, back in fastboot mode, you should already be connected to your computer via USB (if you disconnected, just reconnect it and wait for "FASTBOOT" to change to "FASTBOOT USB")
Run this command:
Code:
fastboot oem rebootRUU
Next, start up the RUU program again and let it run through without interruption. After this process is done, the phone should boot up to the stock ROM. Let it do its thing, but this time don't do the OTA update. From here, just unlock the bootloader again, install your recovery of choice, and install your ROM of choice or reroot the stock ROM (I know some want to keep it stock).
As also pointed out by RoyalYeo, you can let HBOOT take care of the problem:
Solution #2
My hunch was correct, the .0928 Radio was causing the bootloop... I managed to flash the 521_2 radio, and now the Sick kernel is working and AOKP JB runs great.
Steps (on windoze):
1) Download the RUU
2) Run the .exe, wait for it to open the first wizard screen.
3) Open a file explorer in c:\users\yourname\AppData\Local\Temp\New_Directory _With_Some_Hexadecimal_name
4) Locate `rom.zip`, copy to the root directory of your sd card, and rename it to PK76IMG.zip
5) Reboot to bootloader, connect usb, and `fastboot oem lock` in cmd shell, at which point it'll reboot
6) Get back to HBOOT, wait for it to notice PK76IMG, confirm, make a pot of coffee, check back in 5-10 minutes.
7) After reboot, phone should now show a 1.00.00.521_2 radio... re-unlock the bootloader in fastboot, re-flash TWRP or whatever, and you should be good to go.
Lemme know if you get it working...
Click to expand...
Click to collapse
My personal solution (Solution #1) is the more technical side of things and also exposes you to the nitty-gritty. Having said this, #1 is quite touchy because if you do something wrong, there is a good chance that you could... well uh, brick your phone to be quite honest. On the other hand, #1 requires no SD card (given the event that your SD card won't mount, your SD reader is broken, or you just plain don't have an SD card). Ultimately, the choice is up to you.
A note for Mods: I'm not sure if this technically falls under Development or Q&A (or both). If it can stay here in Development, I'll also post a thread in Q&A.
hello there,
So i've followed these instructions and I still get a bootloop... Occasionally when i flashed the MIUI.us rom it will get up to the start out screen... then restart... and do it repeatedly... but at the current moment... it's simply bootlooping on the MIUI logo. I've ran RUU approximately 20 times on this phone... i've tried different SD cards because something is recently they have been randomly disconnecting and not showing up... i Plugged my phone in and set it to Disk Drive mode, wrote files to it... and when i check on my phone... all the files are gone except for the original.. so i preceded to take the card out plug it into my computer and format there... i do that... and all the files show back up when i plug into my phone... ALL the original files that i just formatted... i don't know what steps to take next to get any of it working. I've tried flashing sick kernel and the MIUI rom and still nothing has worked... any assistence would be greatly appreciated, I'm tired of resetting my phone EVERY time i try and flash a new rom
I have a thread here but Everything i have tried there has failed to work but you could use some of the info from there to possibly diagnose?
http://forum.xda-developers.com/showthread.php?t=2013489
Thanks a million!