Related
First things first. Im a NOOB, got it. I really want to update to 4.0.4 but haven't been able to acomplish via the posts in the developer forums. I so far have downloaded and installed the GN toolkit, and been able to unlock the bootloader. I have tried to boot to CWM Recovery w/o perm flashing it, to install the update, but I can't get it to work, it just hangs. I don't want to root but I tried that as well via the GN toolkit, it fails out as well. I just want to install the Stock 4.0.4. and relock my bootloader, being back to totally stock, w/the most upto date firmware. PLEASE HELP
1. Go to settings -> about phone -> update (I think, my rom has this feature removed) to get the official OTA from Verizon.
2. If you want to use CWM, you will have to permanently flash it over.
3. If an OTA image is available, you could use fastboot to write it to the system, just make sure you backup everything to a second location as it will often wipe your SD.
flashing CWM is very easy.
download the image for the TORO (galaxy nexus CDMA) version of the nexus from http://www.clockworkmod.com/rommanager
once its downloaded, make sure you are able to use fastboot (should be in the folder for the tool kit)
open a command promt, navigate to the toolkit folder which should have fastboot.exe then type:
fastboot flash recovery cwm-recovery-image-name
let it finish then boot into recovery. this will allow you to flash the 4.0.4 rom.
there is no reason to relock the bootloader and as soon as you boot up, stock recovery will place it self back on the phone since you're not going to root.
Tubes6al4v said:
1. Go to settings -> about phone -> update (I think, my rom has this feature removed) to get the official OTA from Verizon.
2. If you want to use CWM, you will have to permanently flash it over.
3. If an OTA image is available, you could use fastboot to write it to the system, just make sure you backup everything to a second location as it will often wipe your SD.
Click to expand...
Click to collapse
Sadly it isn't truely available OTA. These fourms seem to be the only way it is availble. GN toolkit says it can "boot to CWM Revoery withou Permanently flashing it" but like I said it hangs up on me everytime no matter if I try the standard or the touch version.
Zepius said:
flashing CWM is very easy.
download the image for the TORO (galaxy nexus CDMA) version of the nexus from .....(EDIT)
once its downloaded, make sure you are able to use fastboot (should be in the folder for the tool kit)
open a command promt, navigate to the toolkit folder which should have fastboot.exe then type:
fastboot flash recovery cwm-recovery-image-name
let it finish then boot into recovery. this will allow you to flash the 4.0.4 rom.
there is no reason to relock the bootloader and as soon as you boot up, stock recovery will place it self back on the phone since you're not going to root.
Click to expand...
Click to collapse
the GN toolkit has the disc image file "recovery-cwm-5.5.0.4-toro-lte"
what do you mean when you say make sure I can use fast boot. in the folder I found a application that is named "fastboot-toolkit", but when I click it it opens then closes before I can do anything with it.
also typing in the run box, I'm also not having anyluck, can you be more specific as to what you mean, I tried typing in "fastboot flash recovery cwm-recovery-image-name", and "fastboot flash recovery-cwm-5.5.0.4-toro-lte" because I thought that is the name of the file Im tring to flash, correct?
Is there no way to apply this via the stock recovery?
langman21 said:
the GN toolkit has the disc image file "recovery-cwm-5.5.0.4-toro-lte"
what do you mean when you say make sure I can use fast boot. in the folder I found a application that is named "fastboot-toolkit", but when I click it it opens then closes before I can do anything with it.
also typing in the run box, I'm also not having anyluck, can you be more specific as to what you mean, I tried typing in "fastboot flash recovery cwm-recovery-image-name", and "fastboot flash recovery-cwm-5.5.0.4-toro-lte" because I thought that is the name of the file Im tring to flash, correct?
Is there no way to apply this via the stock recovery?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=20632492&postcount=3'
read this post. it should help you get fastboot setup correctly.
and no, there is no way to apply 4.0.4 via stock recovery that i know of.
Status Update....Phone is unlocked, and connected to Computer via USB Debugging is activatied. It is in Fastboot mode, and I have rebooted and went through the initial setup.
I just installed Java Development Kit because it was "required" for the Android SDK tools install which i am setting up now. This is taking a while....
I have copied the fastboot-windows file into the Android platform-tools folder...
in command prompt I get 'fastboot-windows.exe' is not a recognized as an internal or external command, operable program or batch file
looks like I dont need the .exe, it brought up the a bunch of command options...now what?
okay looks like I got fastboot working, and went back into GN Toolkit and flashed CMW recovery. I was able to boot CWM recovery....now where do I save the update so I can find it? I now have the option to choose zip from SDcard.
langman21 said:
okay looks like I got fastboot working, and went back into GN Toolkit and flashed CMW recovery. I was able to boot CWM recovery....now where do I save the update so I can find it? I now have the option to choose zip from SDcard.
Click to expand...
Click to collapse
you'll want to move the .zip file of the 4.0.4 update to anywhere on the SDcard. basically anywhere you'd download something to from your browser on the phone.
once its there, you'll want to make a backup just in case.
once the backup is complete, you should be able to then install from that zip file and be ok.
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!
hello android geniuses first of sorry about this once my phone is working again i will not mess with it anymore
okay so i was feeling cool and rooted my htc one m7 from verizon then i turned s-off and unlocked bootloader
then i flashed a custom rom it was paranoid android everything worked except i wasnt getting any service on the phone so i was told to flash a verizon htc one rom so i went and flashed viper 6.2 but the phone got stuck in a bootloop so for some reason i thought that doing a factory reset/wipe from the recovery would fix it....it didnt and now i cant reflash the rom either....i tried to sideload but adb wont recognize my device while fastboot recognizes the phone adb wont
what am i to do?
Well im not sure of any other methods to try but i had loads of problems myself pushing files to the SDcard threw twrp and cwm recoveries, so the way I went about it was doing a decrypted RUU to return the phone to stock then once it loaded up in Android I pushed the Rom to the SDcard card then rebooted and started over.
Goto this thread http://forum.xda-developers.com/showpost.php?p=46506621&postcount=2
All the way at the bottom you should see some links for RUU's, I used the one labeled "1.10.605.15 Decrypted RUU" You will flash this the same way as you would a firmware update, if you dont know how thats done that post will explain it all. After you flash the RUU reboot and it should be back to the day you got it, but you will still be s-off, at that point just put a custom recovery back on and flash away, however that RUU will downgrade your firmware so you might wanna update your firmware after you get the phone booted up and your rom placed back on the sdcard
fLaWx said:
Well im not sure of any other methods to try but i had loads of problems myself pushing files to the SDcard threw twrp and cwm recoveries, so the way I went about it was doing a decrypted RUU to return the phone to stock then once it loaded up in Android I pushed the Rom to the SDcard card then rebooted and started over.
Goto this thread http://forum.xda-developers.com/showpost.php?p=46506621&postcount=2
All the way at the bottom you should see some links for RUU's, I used the one labeled "1.10.605.15 Decrypted RUU" You will flash this the same way as you would a firmware update, if you dont know how thats done that post will explain it all. After you flash the RUU reboot and it should be back to the day you got it, but you will still be s-off, at that point just put a custom recovery back on and flash away, however that RUU will downgrade your firmware so you might wanna update your firmware after you get the phone booted up and your rom placed back on the sdcard
Click to expand...
Click to collapse
What he said. Good post dude.
When you enabled adb sideload, what command did you use? Because you don't push files that way. You type "adb sideload Rom.zip", then it will send the file and after it sends immediately start the install. So you will need to wipe in recovery first to make sure it's clean.
Sent from my Lunar Ecliptic One.
i followed your steps i got to the part where fastboot asks to flush the zip again i typed "fastboot flash zip firmware.zip" and it said waiting for device and that never went away so i rebooted into bootloader and now fastboot wont recognize the device however if i go to device manager it says my htc is plugged but has a little yellow icon...the drivers are up to date this is driving me nuts i just want my phone to work
Ruu
sound like you may need to ruu back to total stock there are instruction on doing it here and I do not want to give you the wrong steps. found this but make sure you have the decrypted ruu
1. Download VZW RUU.zip from the following thread 1. Download VZW RUU.zip from the following thread (http://forum.xda-developers.com/show....php?t=2428276)
2. Rename to "ruu.zip"
3. Enter fastboot mode
4. enter "fastboot oem rebootRUU" - You should not see a silver HTC logo on your device.
5. enter "fastboot flash zip ruu.zip" - The first time you execute this command, it only prepares the flash
6. As soon as the flash is done preparing, enter the same exact command again "fastboot flash zip ruu.zip"
7. Now you'll see a little green progress bar on your phone. This does not need to reach 100%. As soon as your command window is finished, you can just "fastboot reboot".
8. You should be set back to fully stock HTC One.
http://www.htc1guru.com/dld/ruu-zip-m7_wl_jb_50_vzw_1-10-605-10_decrypted-zip/
I also use cut and paste when doing this as it stops my crappy spelling from getting in the way
The problem now is that fastboot wont recognize the device, when i type "fastboot devices" its blank
i think i screwed up the firmware becouse in fastboot it says in red os-3.11.605.1 (1.10.605.15) in red
before i remember it was green that spot...oh crap i wont be able o buy a new phone in a long time this is terrible....i still have teamwin recovery can i do anything through that?
quadracorn said:
The problem now is that fastboot wont recognize the device, when i type "fastboot devices" its blank
i think i screwed up the firmware becouse in fastboot it says in red os-3.11.605.1 (1.10.605.15) in red
before i remember it was green that spot...oh crap i wont be able o buy a new phone in a long time this is terrible....i still have teamwin recovery can i do anything through that?
Click to expand...
Click to collapse
You could always use a USB-OTG, place a rom on a flash drive and try to install that way. There may be a simpler way, but that's all i can think of for now.
i guess i have to order an otg cable....oh well...ill have to live without a phone a bit longer until cable shows up haha XD w
quadracorn said:
The problem now is that fastboot wont recognize the device, when i type "fastboot devices" its blank
i think i screwed up the firmware becouse in fastboot it says in red os-3.11.605.1 (1.10.605.15) in red
before i remember it was green that spot...oh crap i wont be able o buy a new phone in a long time this is terrible....i still have teamwin recovery can i do anything through that?
Click to expand...
Click to collapse
Does pc see device in computer?if so down load room onto pc place Rom on root of ad card or in download and reboot phone into recovery ahs flash zip..I also had problem where adb would not see devices cause I had miniadb and the full version of adb and it was a conflict,just my two cents
I don't know if this will help, but I had an issue of my devices not being found so I followed this guy's guide: http://zacktutorials.blogspot.com/2013/04/adb-is-not-recognized-as-internal-or.html
and was able to get my device recognized. Also which recovery are you using? I don't know if it's still an issue but when I was on viper I got stuck in a bootloop with TWRP so I switched to Philz.
If you're able to get into fastboot, follow post #4 http://forum.xda-developers.com/showthread.php?t=2677015 and basically start from the beginning.
Make sure you have the latest recovery, the latest firmware (radios and such), and the correct ROM..
good luck
bregga said:
sound like you may need to ruu back to total stock there are instruction on doing it here and I do not want to give you the wrong steps. found this but make sure you have the decrypted ruu
1. Download VZW RUU.zip from the following thread 1. Download VZW RUU.zip from the following thread (http://forum.xda-developers.com/show....php?t=2428276)
2. Rename to "ruu.zip"
3. Enter fastboot mode
4. enter "fastboot oem rebootRUU" - You should not see a silver HTC logo on your device.
5. enter "fastboot flash zip ruu.zip" - The first time you execute this command, it only prepares the flash
6. As soon as the flash is done preparing, enter the same exact command again "fastboot flash zip ruu.zip"
7. Now you'll see a little green progress bar on your phone. This does not need to reach 100%. As soon as your command window is finished, you can just "fastboot reboot".
8. You should be set back to fully stock HTC One.
http://www.htc1guru.com/dld/ruu-zip-m7_wl_jb_50_vzw_1-10-605-10_decrypted-zip/
I also use cut and paste when doing this as it stops my crappy spelling from getting in the way
Click to expand...
Click to collapse
Hi All,
Do you know is RUU 4.4 has surfaced? please help
For the last two days I tried to revert my HTC One V back to stock android. As in, the way I got it when I first booted it up. I experienced that this progress was pretty difficult. Maybe this was because I was used to the AOSP niceness of Google's LG NExus 4 or because HTC made it very hard to say the least to downgrade/upgrade to their own stock ROM.
I may not have the original sources for all files because I deleted some original .zip files and only have the extracted files.
First off, I wouldn't do any of this if you have important files on your device, I wiped everything from my phone a dozen of times in the process and it didn't care because I didn't had any important files on their.
Alright, so what we want to achieve is to get to the latest version of HTC's RUU version "2.22.401.7". The RUU I could find was "2.22.401.1" so we're gonna have to d/l some OTA's later on via our device if everything is set up.
So obviously everyone who is trying to revert back has somewhere unlocked their bootloader by doing
fastboot oem get_identifier_token
and
fastboot flash unlocktoken Unlock_code.bin
Please remember this: ANY RUU will fail every single time if your device is LOCKED. It will ONLY work if it's unlocked or relocked.
So first off what we gonna have to do is relock/unlock our device. You can relock your device by going into fastboot[1] mode and running the following command:
fastboot oem lock
Myself have expierenced an error that told me it "FAILED". Please reboot your bootload:
fastboot reboot-bootloader
And check the locked status at the top. If it says "RELOCKED", succes! If it didn't, retry the command above.
Next, we're relocked so we can run the RUU. Please look at the text file at the RUU source [2] for the download links. In this .zip file are the files inside the RUU wizard. You can run the wizard by executing "ARUWizard.exe" and you can view the contents of the actual ROM in "rom.zip extracted" and you can find the original ROM in "rom.zip". Since these are the files the wizard will be using (except rom.zip extracted folder) please do not touch them.
Alright, so we've got the extracted files of the RUU and we're ready to update. Please boot your phone in fastboot mode and connect it to your computer via USB. Now run the "ARUWizard.exe" file and let it update. I couldn't think of a situation where this could go wrong, so please ask below if you face any problems.
The wizard will flash stock radio, recovery andsystem.img (the actual ROM you all know) so by doing this you lose your custom revovery.
When your phone boots up you've gotta go through 3-4 updates till it's on "2.22.401.7".
I recommend not flashing a custom recovery right away because when you install/download OTA updates it isn't able to flash it right. In the meantime if you want root[3] use this command:
adb install -s supersu.apk
When you're on the latest version you have to unlock your bootloader, otherwise you cannot flash a custom recovery or kernel or whatever. You can do this via HTC[4]. I think there are enough guides on how to do this, but in short:
- create an account with an legitimate email address
- Select "all other supported devices" from the list
- follow on screen instructions.
Seriously everything is on there, HTC made it really easy.
If you want to install a custom recovery I recommend using TWRP[5]. Please flash TWRP by booting into fastboot and running the following command:
fastboot flash recovery twrp_recovery.img
Troubleshooting
There isn't really a lot that can go wrong if you do this. But when you're stuck on a screen or you think your device is "bricked" or stuck in a bootloop do these things:
- First off, hold the power and volume down button till the device goes down. If it's down, release the buttons and then hold the same buttons again till you're in bootloader
If that doesn't work do either of these commands (make sure your device is connected via USB, hehe)
Make sure fastboot and/or adb is working first:
fastboot devices
adb devices
If fastboot is working:
fastboot reboot-bootloader
If ADB is working:
adb reboot bootloader
adb reboot recovery
If you have any questions, please ask me. I did a dozen of things these two days, I may forgotten something because I did a crapload of things all at once.
Cheers!
Sources:
[1] http://www.technewscentral.co.uk/enter-fastbootbootloader-mode-htc-one/id_7930
[2] http://rg.to/file/aaca8c0c03e655d6df78242b4cea931b/hov.zip.html
http://ul.to/dfmg5dnw
https://mega.co.nz/#!wBcUiIxD!uIkyqZLgFErSItBTu3K7RY3eyUmXVUg60rcB-B-QRWE
Please request other providers below.
[3] http://download.chainfire.eu/supersu
[4] http://www.htcdev.com/bootloader
[5] http://techerrata.com/browse/twrp2/primou
tl;dr
unlock bootloader -> run RUU -> done
This is great and all, but is this for the PRIMO-C or U? US version? etc... etc..