Hey so I want to start using the CM10.1 ROM that's posted here: http://forum.xda-developers.com/showthread.php?t=1786696. However to use the the proper kernel, you need hboot 1.28+. I'm on 0.96, how the hell do I update? Every time I try and search, it tells me I need my CID, so I used CID Getter and it didn't give me one. My network is O2 UK if that helps, and it is already rooted and CM10 is running on it. I thought about using the stock Nandroid backup thread to grab one (I accidentally deleted my original backup) and then update to Sense Jelly Bean, but it says there you need your CID and I obviously don't know it. Any help would be appreciated!
samsaBEAR said:
Hey so I want to start using the CM10.1 ROM that's posted here: http://forum.xda-developers.com/showthread.php?t=1786696. However to use the the proper kernel, you need hboot 1.28+. I'm on 0.96, how the hell do I update? Every time I try and search, it tells me I need my CID, so I used CID Getter and it didn't give me one. My network is O2 UK if that helps, and it is already rooted and CM10 is running on it. I thought about using the stock Nandroid backup thread to grab one (I accidentally deleted my original backup) and then update to Sense Jelly Bean, but it says there you need your CID and I obviously don't know it. Any help would be appreciated!
Click to expand...
Click to collapse
install the sdk on your computer and then set the right environment variables, then in terminal type with your phone connected
Code:
adb getvar cid
Never used adb before, so I used this: http://www.droidforums.net/forum/droid-hacks/6865-how-use-adb-all-commands-options.html, to help out. Navigated to the place it told me to but every time I type what you told me to, it says 'adb is not recognised as in internal or external command, operable program or batch file.' What am I missing, and apologies if this is really ****ing simple and I'm just being an idiot.
Edit: Navigated to the path the website gave me and found that the adb has moved to another folder. Went to that in terminal, put in what you told me and it just gave me a big old list of adb commands, as opposed to my cid?
samsaBEAR said:
Never used adb before, so I used this: http://www.droidforums.net/forum/droid-hacks/6865-how-use-adb-all-commands-options.html, to help out. Navigated to the place it told me to but every time I type what you told me to, it says 'adb is not recognised as in internal or external command, operable program or batch file.' What am I missing, and apologies if this is really ****ing simple and I'm just being an idiot.
Click to expand...
Click to collapse
follow this guide, it will explain you how to install the sdk and use adb
Right ok, what I actually needed to go was to go into the bootloader and type 'fastboot getvar cid'. That all worked well and good however it said 'CID: none'. Is this good or bad?
Edit: So I've finally found my CID haha, I had to use 'fastboot oem readcid' as the command, which gave '02__001'. How do I know go about updating my hboot? Do I have to download a nandroid backup and relock my device to get the update from HTC, or is there a quicker way to just do the hboot?
ok you need to download this firmware, which is for your specific CID, and then follow these steps:
Download the ROM and place it on your virtual SD card.
Relock your bootloader using the commend 'fastboot oem lock'.
Go into fastboot mode and type 'fastboot oem rebootRUU'.
Flash the new firmware using the commend 'fastboot flash zip firmware.zip'.
On first time running the commend you will see FAILED, don't panic and just run the commend again.
Reunlock your bootloader via HTCDev.
Flash custom recovery using the commend 'fastboot flash recovery recovery.img'.
Download boot.img and flash it using the commend ‘fastboot flash boot boot.img’.
Use the commend 'fastboot erase cache' to avoid boot issues.
Go into recovery and install the ROM.
Reboot your device and enjoy from JB!
Awesome thank you very much for all your help!
samsaBEAR said:
Awesome thank you very much for all your help!
Click to expand...
Click to collapse
glad to help you report back if you succeeded in it
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.
Before you start, you will need to set up your computer to properly recognize the phone. You probably did this when rooting originally, but just in case... Install SDK tools for Android, Java runtime, and HTC Sync.
About HTC Sync: The only reason you need HTC Sync installed is for the USB drivers that come with it. But the program itself has been known to cause conflicts. Make sure that HTC Sync is not running in the background by opening Task Manager in Windows and killing it if you find it lurking in there.
Here we go:
1. Download the correct RUU (ROM Update Utility) for your device from androidfiles.org. Make sure you download a Primo_C RUU for a CDMA device (no sim card) or a Primo_U RUU for a GSM device (uses a sim card)!! Also make sure you get the correct RUU for your carrier.
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 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
7. Re-run the RUU. It will restore the device to it's original condition, locked (though *** RELOCKED ***) and unrooted.
Once the install is done you'll have unlock the bootloader again using the token you already have from the first time, reflash CWM Recovery and re-root. All this will be 10x easier than the first time.
If you do re-root your phone, be 100% you backup the stock ROM in ClockworkMod Recovery before making changes!
Hi
Thanks for that perfect decsription exactly when I needed it
I just had a weired effect with my new windows 7 laptop that I want to share.
I installed the USB drivers and "fastboot devices" showed my HTC fine
but even flashing the stock recovery image was not working.
So it was stucking in the "Sending" part and never continued.
I then moved to my old laptop with Vista did exactly the same things
and there it worked without problems.
I disabled virus scanner, checked for htsync and used the original USB cable
without success.
But now I know why I normally never touch Windows and only
work on linux
Regards
max
---------- Post added at 11:19 PM ---------- Previous post was at 10:33 PM ----------
Hi
CafeKampuchia said:
If you do re-root your phone, be 100% you backup the stock ROM in ClockworkMod Recovery before making changes!
Click to expand...
Click to collapse
I have done that now - compared to my first "try"
Regards
max
hi. thanks for the tips.
however when i do this, i get an error "FAILED <remote: signature verify fail>
Any suggestions?
ur RUU and CID is diff...
ryanlow134 said:
ur RUU and CID is diff...
Click to expand...
Click to collapse
and... how do i make them the same?
lcavada said:
and... how do i make them the same?
Click to expand...
Click to collapse
Use the correct RUU package for your device
regards
max
Another way of saying it is that you downloaded the wrong RUU for your device.
not working
it keeps on saying waiting for device n does not proceed further
i tried installing the drivers again but that doesnt help either
pls help me out
I use fastboot flasher for this.. this tool is good .
sush93 said:
it keeps on saying waiting for device n does not proceed further
i tried installing the drivers again but that doesnt help either
pls help me out
Click to expand...
Click to collapse
"Waiting for Device" at fastboot usually related to bootloader driver. You need Android USB Driver
See : http://developer.android.com/sdk/win-usb.html
Hi folks,
I've bought my One V in late may and I had 2.08 ROM.
Now I've tested some roms and I wanted to revert back to stock rom.
I've downloaded RUU_PRIMO_U_ICS_40A_HTC_Europe_2.08.401.2_Radio_20.72.30.0833U_3831.17.00.18_M_release_263376_signed, and got recovery_signed and boot_signed images. Then I've went to fastboot, did flash recovery and boot partitions, and oem locked bootloader. Afterwards I booted my phone and entered PIN. Then I fired up RUU*.exe file, and I have 155 error. What the heck? Something I missed?
greetings!
run the ruu in hboot..
Sent from my HTC One V
thevilish said:
Hi folks,
I've bought my One V in late may and I had 2.08 ROM.
Now I've tested some roms and I wanted to revert back to stock rom.
I've downloaded RUU_PRIMO_U_ICS_40A_HTC_Europe_2.08.401.2_Radio_20.72.30.0833U_3831.17.00.18_M_release_263376_signed, and got recovery_signed and boot_signed images. Then I've went to fastboot, did flash recovery and boot partitions, and oem locked bootloader. Afterwards I booted my phone and entered PIN. Then I fired up RUU*.exe file, and I have 155 error. What the heck? Something I missed?
greetings!
Click to expand...
Click to collapse
Flashing RUU to revert to stock
- you must have the correct RUU for your device.
- if you are not sure, download CID Getter from Play Store and run it, it will show your CID.
- with your CID, you may be able to find a correct RUU for your device
then (even though some people may not agree with this, but this will bring no harm and it is noob-proof) do this:
1- flash a stock recovery.img
fastboot flash recovery recovery_signed.img
fastboot reboot-bootloader
fastboot erase cache
2- flash a stock boot.img
fastboot flash boot boot_signed.img
fastboot reboot-bootloader
fastboot erase cache
3- re-lock bootloader
fastboot oem lock
fastboot reboot-bootloader
fastboot erase cache
4- flash RUU
NOTE: There is no boot/reboot and enter pin in between.
paarthdesai said:
run the ruu in hboot..
Sent from my HTC One V
Click to expand...
Click to collapse
I've done this before and didn't succeeded, but now it works! Magic
Thanks a lot!
help
CafeKampuchia said:
Before you start, you will need to set up your computer to properly recognize the phone. You probably did this when rooting originally, but just in case... Install SDK tools for Android, Java runtime, and HTC Sync.
About HTC Sync: The only reason you need HTC Sync installed is for the USB drivers that come with it. But the program itself has been known to cause conflicts. Make sure that HTC Sync is not running in the background by opening Task Manager in Windows and killing it if you find it lurking in there.
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
7. Re-run the RUU. It will restore the device to it's original condition, locked (though *** RELOCKED ***) and unrooted.
Once the install is done you'll have unlock the bootloader again using the token you already have from the first time, reflash CWM Recovery and re-root. All this will be 10x easier than the first time.
If you do re-root your phone, be 100% you backup the stock ROM in ClockworkMod Recovery before making changes!
Click to expand...
Click to collapse
PLEASE HELP!
The 5th point does not work for me. I can not run the code.
What can i do?
what do you mean by navigate to the folder where you installed sdk?
brandoncoronado said:
what do you mean by navigate to the folder where you installed sdk?
Click to expand...
Click to collapse
It means that if you installed SDK in c:/android, then u must type.in the command prompt: cd c:/android and hit enter
Cheers
Sent from my HTC One V using xda app-developers app
brandoncoronado said:
what do you mean by navigate to the folder where you installed sdk?
Click to expand...
Click to collapse
where the fastboot.exe is located and stock recovery must be in the same folder for the command to work
[ask] Error 155
hey guys, ive been reading all tutorial for reverting to stock RUU.
the first time i tried, it works prefectly.
then after a few weeks, i tried to revert to stock RUU, it failed .
it show error 155.
i already flash the boot , recovery that i found inside the stock RUU, also I've relock the phone.
but when i relock the phone, it show "info Lock successfully , status read failed no such file / directory"
when i enter bootloader, it show that my device already "relocked"
does the relocked proses is successfully ?
iam running PrimoU 2.09.707.1 with stock bootloader, CWM recovery, and rooted ..
I did exactly as it is mentioned but at the end where there is vertical progress bar it gives me an error of customer Id... Failed to update. What shud i do. How do I check what my customer Id is I can't Download it from play store coz can't boot into normal screen... How do I make ruu and cid same.
Sent from my Galaxy Nexus using xda app-developers app
Hi guys,
Just wanted to put it out there that I'm totally new at this rooting, custom ROM thing, and I got excited which led me to fail the number ONE rule of backing-up your phone!
Anyways, here's the situation
- Rooted my HTC One X
- Tried to install a custom ROM (IceCold Jelly)
- Phone went into bootloop, after the pink unicorn screen
Some facts
- I can get into the bootloader
- When I plug the phone into the PC, PC makes a sound, but it does not recognize the phone at all
- PC detects a "fastboot" device, but no phone
- went through a few "How to save a soft-bricked" phone tutorial to no avail
- fastboot cmd stuff don't work
- i have boot.img, fastboot.exe etc all on my pc
- drivers and htc sync up to date
I'm sorry if its been answered, but in the bunch of threads I've looked at, everything revolves around being able to use the CMD and the PC actually detecting the phone. Couldn't find any way of fixing my phone, as I said above, the PC doesn't register that theres anything connected to it.
I'd appreciate some help, its been a couple of days, and having no phone is really really hurting!
I'm really really new at this, so I apologize in advance if I don't really understand the terminologies used!
Thanks in advance!
What is the output when you run "fastboot devices" from cmd with your HOX connected in fastboot mode?
Michealtbh said:
What is the output when you run "fastboot devices" from cmd with your HOX connected in fastboot mode?
Click to expand...
Click to collapse
when i type fastboot devices, it comes up as a serial number then fastboot
but when i type adb devices, nothing
appasionata said:
when i type fastboot devices, it comes up as a serial number then fastboot
but when i type adb devices, nothing
Click to expand...
Click to collapse
That's good, fastboot works.
Flash the boot.img from the rom you're trying to flash by putting it into your fastboot folder and running "fastboot flash boot boot.img" then "fastboot erase cache". Then boot into recovery and perform a full wipe then reflash the rom.
Michealtbh said:
That's good, fastboot works.
Flash the boot.img from the rom you're trying to flash by putting it into your fastboot folder and running "fastboot flash boot boot.img" then "fastboot erase cache". Then boot into recovery and perform a full wipe then reflash the rom.
Click to expand...
Click to collapse
I tried flashing it, the result on the cmd said something about not recognizable internal or external command
appasionata said:
I tried flashing it, the result on the cmd said something about not recognizable internal or external command
Click to expand...
Click to collapse
Are you sure you're typing it correctly? If "fastboot devices" works then those commands should also work.
Try just "fastboot erase cache", without quotation marks of course
Michealtbh said:
That's good, fastboot works.
Flash the boot.img from the rom you're trying to flash by putting it into your fastboot folder and running "fastboot flash boot boot.img" then "fastboot erase cache". Then boot into recovery and perform a full wipe then reflash the rom.
Click to expand...
Click to collapse
Michealtbh said:
Are you sure you're typing it correctly? If "fastboot devices" works then those commands should also work.
Try just "fastboot erase cache", without quotation marks of course
Click to expand...
Click to collapse
Yeah ofcourse typing the exact same things.
Alright lets clear things up,
where should the fastboot folder be? and I type "fastboot flash boot boot.img" right after i type cmd into the windows search bar. Is there anywhereI should be running the cmd from? like the directory of the cmd?
also what boot.img file should it be? custom rom?
Thanks
appasionata said:
Yeah ofcourse typing the exact same things.
Alright lets clear things up,
where should the fastboot folder be? and I type "fastboot flash boot boot.img" right after i type cmd into the windows search bar. Is there anywhereI should be running the cmd from? like the directory of the cmd?
also what boot.img file should it be? custom rom?
Thanks
Click to expand...
Click to collapse
Go to the folder with boot.img and fast boot exe, hold shift and press right mouse button on this folder. Than choose run cmd here (or smthng like this, I don't know how it called in English). Than type commands
Sent from my HTC One X using xda app-developers app
If you'd like a hand, I could help you do it remotely via TeamViewer.
appasionata said:
Yeah ofcourse typing the exact same things.
Alright lets clear things up,
where should the fastboot folder be? and I type "fastboot flash boot boot.img" right after i type cmd into the windows search bar. Is there anywhereI should be running the cmd from? like the directory of the cmd?
also what boot.img file should it be? custom rom?
Thanks
Click to expand...
Click to collapse
You should be running the fastboot commands from the folder your fastboot file is in. Either open a command prompt and cd to your fastboot folder, or navigate to the folder in Windows Explorer and open a command prompt there by holding shift and right clicking and choosing "open command window here".
Your fastboot folder should be in your Android SDK, probably in the root of your C drive. It could be somewhere else though depending on how you set up fastboot and adb in the first place.
The boot.img you want to flash is the one inside the rom.zip you want to flash, this goes for all roms.
Michealtbh said:
You should be running the fastboot commands from the folder your fastboot file is in. Either open a command prompt and cd to your fastboot folder, or navigate to the folder in Windows Explorer and open a command prompt there by holding shift and right clicking and choosing "open command window here".
Your fastboot folder should be in your Android SDK, probably in the root of your C drive. It could be somewhere else though depending on how you set up fastboot and adb in the first place.
The boot.img you want to flash is the one inside the rom.zip you want to flash, this goes for all roms.
Click to expand...
Click to collapse
Thanks for the help guys, I'll keep trying and will let you guys know. I think the root of the problem is that I'm inputting the fastboot commands right as I enter the cmd prompt from the windows search bar.
Will keep you guys posted, thanks for the help so far. Don't have my phone on me this minute as its with my friend whos trying to fix it too, will get it back in the morning!
Alright,
I've tried it now, and now theres a different problem. When I try to get into recovery from the bootloader, a picture of a htc device and red triangle and exclamation mark appears. And the custom rom load screen no longer appears. PC still does not recognize the phone.
Are u installed custom recovery ? Are u unlocked your device via hrc dev website?
Sent from my HTC One X using xda premium
incident said:
Are u installed custom recovery ? Are u unlocked your device via hrc dev website?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I'm not sure.
How do I install a custom recovery at this point? and how do I unlock my device via htc site. If you're talking about unlocked with operator, then yes, its an unlocked phone.
As far as I've read into this issue, I think the problem is that maybe installed the stock recovery but from a different RUU?
appasionata said:
I'm not sure.
How do I install a custom recovery at this point? and how do I unlock my device via htc site. If you're talking about unlocked with operator, then yes, its an unlocked phone.
As far as I've read into this issue, I think the problem is that maybe installed the stock recovery but from a different RUU?
Click to expand...
Click to collapse
I think he means that have you unlocked your bootloader via the htcdev.com website?
Sent from my HTC One X using xda premium
OP's first post states that he tried to install a rom, so his bootloader must be unlocked and a custom recovery must have been installed at some point.
@OP - all you have to do is download a custom recovery (CWM or TWRP) then flash it using "fastboot flash recovery nameofrecovery.img", then follow the steps previously explained to you in this thread.
Problem is though he says he rooted HOX he has no idea about unlocking bootloader at HTC Dev? So when he says he's rooted did he unlock the bootloader? He mentions he has an "operator" unlocked phone, and I think this is where he's getting confused. Otherwise suggesting further flashing will make a bad problem worse.
Also it sounds like he's trying to run CMD from start menu. He needs to run it from from where the fastboot file is located, or at least "point" to it in CMD.
---------- Post added at 06:54 PM ---------- Previous post was at 06:46 PM ----------
If you can get into bootloader as you stated have you tried a factory reset?
appasionata, my offer of helping you do it remotely still stands. As long as your there to plug in and handle the handset, I'm pretty sure (95%~) that we can recovery your handset.
andyharney said:
appasionata, my offer of helping you do it remotely still stands. As long as your there to plug in and handle the handset, I'm pretty sure (95%~) that we can recovery your handset.
Click to expand...
Click to collapse
Thanks, I really appreciate it, I think I might have to resort to this. How do we go about it? shall we talk about it via PM? I'm pretty busy this whole week, so we can do it on the weekends?
Looks like you have a stock recovery, try to install the correct RUU (stock ROM for your phone, manuals, can be found in a sticky post of the ROMs thread). So first get back to stock, then start over and read the f**king manuals very carefully. no offence.
If you don't know what you are doing, please don't start at all.
Manuals: http://forum.xda-developers.com/showthread.php?t=1832891
Sent from my HTC One X using xda premium
I'm trying to install the latest RUU for my developer edition. The RUU loads till the point where I accept the agreement and then nothing. I'm on Windows 8.1. Here is where I got the RUU from http://www.htc.com/us/support/htc-one-m8/news/
Any idea why is this happening or how to fix it? I'm having all sort of problems with the phone at the moment. I'm giving a RUU a try to see if it fixes it.
Thanks in advance!
Same thing happens to me, no idea why. Works fine in Windows 7. some people say it's to do with needing a C++ Update but that didn't work for me either
What you can do, though, is once at the T&Cs screen, open a run box and type in %temp% and it'll take you to the Temporary Files folder on your PC and if you look at the newest folders there should be 2. One will contain a compressed file called 'rom'. Copy this to your Desktop, then to a microSD card and flash that via HBOOT or flash it via RUU mode using htc_fastboot.exe (which you can find here)
EddyOS said:
Same thing happens to me, no idea why. Works fine in Windows 7. some people say it's to do with needing a C++ Update but that didn't work for me either
What you can do, though, is once at the T&Cs screen, open a run box and type in %temp% and it'll take you to the Temporary Files folder on your PC and if you look at the newest folders there should be 2. One will contain a compressed file called 'rom'. Copy this to your Desktop, then to a microSD card and flash that via HBOOT or flash it via RUU mode using htc_fastboot.exe (which you can find here)
Click to expand...
Click to collapse
Could you refer to this C++ update if you happen to remember which one?
How do I flash the rom file through HBOOT or the RUU mode using htc_fastboot.exe (87.7 KB)?
To flash the ZIP in RUU mode
fastboot oem rebootRUU
htc_fastboot flash zip rom.zip
And unfortunately no, I don't know which update it was as didn't work
EddyOS said:
To flash the ZIP in RUU mode
fastboot oem rebootRUU
htc_fastboot flash zip rom.zip
And unfortunately no, I don't know which update it was as didn't work
Click to expand...
Click to collapse
I've never done this through RUU mode before, so I'll double check with you.
I'll open normal fastboot. Copy the rom.zip to the root of theSD Card or to the same folder where fastboot is? Also where to place HTC_fastboot.exe, same as fastboot or in the root of SD Card? Then I'll enter the command fastboot oem rebootRUU then htc_fastboot flash zip rom.zip? I'm sorry for the basic questions, thanks a lot!
If you're flashing it manually you don't copy it to your phone, just put it in your fastboot folder along with the htc_fastboot file and then do it all with the phone in fastboot mode
This is the same like applying the RUU exe? This will wipe everything and install everything from zero, right? On HBOOT I have a modified software status , is this going to be fixed as well?
Yep, completely resets the phone to factory defaults
EddyOS said:
Yep, completely resets the phone to factory defaults
Click to expand...
Click to collapse
@EddyOS
Sorry for asking more questions, but last time I applied a RUU was with my M7 when I first bought it. If I'm going to apply the RUU exe, does i have to be on fastboot or while the phone is on? Flashing the rom.zip, do I have to flash or format anything through fastboot or should reboot fastboot or simply reboot the phone? Applying RUU, does it reinstall HBOOT? Sorry and thanks again!
My previous post answers your last bit - it puts EVERYTHING back to factory and the latest versions
RUU.exe you can run when in Android or in fastboot mode, RUU.zip HAS to be flashed in RUU mode.
I've said everything you need to know so if you still don't get it, don't bother trying it
EddyOS said:
My previous post answers your last bit - it puts EVERYTHING back to factory and the latest versions
RUU.exe you can run when in Android or in fastboot mode, RUU.zip HAS to be flashed in RUU mode.
I've said everything you need to know so if you still don't get it, don't bother trying it
Click to expand...
Click to collapse
I'm just making sure. I don't have another phone at the moment and limited 3G internet connection, so I don't want to get stuck with the phone not working or downloading things twice. Sorry for repeating the same questions though
hello...sorry for the noob question....is there a way for me to install the RUU in linux....in window 7....it is always askin for me to install drivers...etc...n error msg...device not found...etc....i dont have those errors in linux....
never mind...I found it...
Yesterday I had the excellent idea of rooting my phone and installing a custom ROM. The process was quite easy though it took me like 2 hours. After I was done I found that I didn't really like the Lineage OS on my M8 as it was draining my battery way too fast. So I decided to go back. This is where the problems began. Since being a total noob when it comes to rooting and flashing on Android I had no idea I had to make a backup of my OS(only did one of my data using HTC Sync Manager). I was able to find one online in the end. But when I wanted to update OTA to 6.1.0 it just boots into Recovery Mode. After some research I found out that I also have to flash a stock recovery file. I allegedly did that using a tool I found online (One M8 All in One Kit 2.0). But still I am unable to update OTA. I just want to go back to Marshmallow.
Would really appreciate some help here guys
Thanks.
Tupi311 said:
Yesterday I had the excellent idea of rooting my phone and installing a custom ROM. The process was quite easy though it took me like 2 hours. After I was done I found that I didn't really like the Lineage OS on my M8 as it was draining my battery way too fast. So I decided to go back. This is where the problems began. Since being a total noob when it comes to rooting and flashing on Android I had no idea I had to make a backup of my OS(only did one of my data using HTC Sync Manager). I was able to find one online in the end. But when I wanted to update OTA to 6.1.0 it just boots into Recovery Mode. After some research I found out that I also have to flash a stock recovery file. I allegedly did that using a tool I found online (One M8 All in One Kit 2.0). But still I am unable to update OTA. I just want to go back to Marshmallow.
Would really appreciate some help here guys
Thanks.
Click to expand...
Click to collapse
You could just run an RUU to get back to stock, since you already flashed the stock backup and have lost data now.
What does it say next to "OS" in your bootloader? With that information I can link you to the proper RUU
xunholyx said:
You could just run an RUU to get back to stock, since you already flashed the stock backup and have lost data now.
What does it say next to "OS" in your bootloader? With that information I can link you to the proper RUU
Click to expand...
Click to collapse
6.12.401.4
I don't quite understand how this RUU works. Will it still say in bootloader "Software status:Modified" after I do this? And will I have to unroot it again or how does it work? Cause it still says Unlocked in bootloader.
Tupi311 said:
6.12.401.4
I don't quite understand how this RUU works. Will it still say in bootloader "Software status:Modified" after I do this? And will I have to unroot it again or how does it work? Cause it still says Unlocked in bootloader.
Click to expand...
Click to collapse
The RUU will take you back to stock unrooted.
I forgot to ask if it said S-On or S-Off in your bootloader. I'll give full instructions for both.
Download this RUU.zip and place it into your adb/fastboot folder
Boot to bootloader and plug your phone into your PC, then get into fastboot
If you are S-On, enter fastboot oem lock That will relock your bootloader. If you are S-Off you can skip this step
Then: fastboot oem rebootRUU wait until the phone boots to a black screen with HTC on it
then fastboot flash zip **drag and drop the RUU.zip here**
When the flash is done, fastboot reboot and you'll be back to stock, unrooted
xunholyx said:
The RUU will take you back to stock unrooted.
I forgot to ask if it said S-On or S-Off in your bootloader. I'll give full instructions for both.
Download this RUU.zip and place it into your adb/fastboot folder
Boot to bootloader and plug your phone into your PC, then get into fastboot
If you are S-On, enter fastboot oem lock That will relock your bootloader. If you are S-Off you can skip this step
Then: fastboot oem rebootRUU wait until the phone boots to a black screen with HTC on it
then fastboot flash zip **drag and drop the RUU.zip here**
When the flash is done, fastboot reboot and you'll be back to stock, unrooted
Click to expand...
Click to collapse
This is exactly what I was talking about. I don't understand how to do those "bolded" instructions. Does it have something to do with the Android SDK? I know I read something.
I am on S-ON btw.
Tupi311 said:
This is exactly what I was talking about. I don't understand how to do those "bolded" instructions. Does it have something to do with the Android SDK? I know I read something.
I am on S-ON btw.
Click to expand...
Click to collapse
So there is the main problem with toolkits. I never use them and never recommend them. Reason being: they shortcut the learning process, and teach you just enough to get into trouble. Then you are stuck with no idea how to recover.
Knowing how to use fastboot (at least on a basic level) is absolutely mandatory in order to unlock the bootloader, and flash custom recovery (for the purpose or root or custom ROM). The manufacturers set it up this way, for a reason. Essentially, if a user doesn't know how to use fastboot, they have no business unlocking the bootloader. The makers of the toolkits bypass this requirement with the intent to make it "easier" for folks to root/ flash custom ROM (the toolkit issued fastboot commands, whether you know it or not). But as already mentioned, it's not a good idea to do that.
I don't blame you. You only know what you know, and we all were n00bs at some point, and had to start somewhere. But my advice to you, would be to learn the basics of what fastboot is about, and how to use it. Plus, there is a lot of nuance here. You actually have to use htc_fastboot to flash the RUU (the "generic" Google fastboot can't handle the large file size). You can get it (as well as the RUU) from the following thread:
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
From there, you need to open the command prompt from whatever folder/directory htc_fastboot.exe or fastboot.exe (respectively) are located. There is a shortcut for doing this:
1) Open folder in Windows, where fastboot.exe (htc_fastboot.exe) is located. Different fastboot installers will install it to different places, so you will have to find it yourself.
2) Hover mouse over the folder, press Shift+Right mouse button. This will open a menu, from which you want to select "Open command window here"
3) The command prompt window will open, and that is where you want to type your fastboot commands.
Another note (and I know this will probably be confusing), I think that you can use htc_fastboot for all the fastboot commands (no need to flip flop between htc_fastboot and fastboot). You just have to use "htc_" before all the fastboot commands. For instance:
htc_fastboot oem lock
redpoint73 said:
So there is the main problem with toolkits. I never use them and never recommend them. Reason being: they shortcut the learning process, and teach you just enough to get into trouble. Then you are stuck with no idea how to recover.
Knowing how to use fastboot (at least on a basic level) is absolutely mandatory in order to unlock the bootloader, and flash custom recovery (for the purpose or root or custom ROM). The manufacturers set it up this way, for a reason. Essentially, if a user doesn't know how to use fastboot, they have no business unlocking the bootloader. The makers of the toolkits bypass this requirement with the intent to make it "easier" for folks to root/ flash custom ROM (the toolkit issued fastboot commands, whether you know it or not). But as already mentioned, it's not a good idea to do that.
I don't blame you. You only know what you know, and we all were n00bs at some point, and had to start somewhere. But my advice to you, would be to learn the basics of what fastboot is about, and how to use it. Plus, there is a lot of nuance here. You actually have to use htc_fastboot to flash the RUU (the "generic" Google fastboot can't handle the large file size). You can get it (as well as the RUU) from the following thread:
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
From there, you need to open the command prompt from whatever folder/directory htc_fastboot.exe or fastboot.exe (respectively) are located. There is a shortcut for doing this:
1) Open folder in Windows, where fastboot.exe (htc_fastboot.exe) is located. Different fastboot installers will install it to different places, so you will have to find it yourself.
2) Hover mouse over the folder, press Shift+Right mouse button. This will open a menu, from which you want to select "Open command window here"
3) The command prompt window will open, and that is where you want to type your fastboot commands.
Another note (and I know this will probably be confusing), I think that you can use htc_fastboot for all the fastboot commands (no need to flip flop between htc_fastboot and fastboot). You just have to use "htc_" before all the fastboot commands. For instance:
htc_fastboot oem lock
Click to expand...
Click to collapse
I followed those steps but when I tried and flash it it gave me this error "target reported max download size of 1826418688 bytes" and I found no real solution to this online.
On a side note I already had the HTC Sync manager installed and I used it to backup some stuff so I can't uninstall it(according to the guide I have to uninstall it, but I guess that's just a suggestion since uninstalling it shouldn't interfere).
Though I feel like I'm close to succeeding.
Tupi311 said:
I followed those steps but when I tried and flash it it gave me this error "target reported max download size of 1826418688 bytes" and I found no real solution to this online.
Click to expand...
Click to collapse
Did you use htc_fastboot? The file size error is usually due to using the wrong fastboot (you need to use htc_fastboot, as the "generic" fastboot can't handle the file size).
Tupi311 said:
On a side note I already had the HTC Sync manager installed and I used it to backup some stuff so I can't uninstall it(according to the guide I have to uninstall it, but I guess that's just a suggestion since uninstalling it shouldn't interfere).
Click to expand...
Click to collapse
I've left HTC Sync installed without any issues. Like you said, it's mostly a suggestion.
Also, just a suggestion:but I would recommend to refrain from quoting someone else's long post (like you quoted my last post). I know it is the default when replying, to include the quote. But just delete what you aren't directly replying to (quote few lines at most) to avoid cluttering up the thread with redundant text.
redpoint73 said:
Did you use htc_fastboot? The file size error is usually due to using the wrong fastboot (you need to use htc_fastboot, as the "generic" fastboot can't handle the file size).
Click to expand...
Click to collapse
Seems like my pc didn't like that I was using those commands and I had to use \.htc_fastboot . It's all good now. Thank you very much. Have a good day.