I just got by brand new M8 (AT&T, Android 4.4.4). I plan to flash custom roms but in reading about some of the roms it seems I'm better off upgrading to the newest OTA update first. Since I don't have my at&t nano sim yet I figured I'd update manually. I downloaded the ruu from the HTC site along with the HTC sync app. In installed the sync app and connected my phone to it no problem. I then tried to run the ruu. It gives me an error 170. After researching the error and trying a few things still no luck.
I then tried to look in the windows temp files and get the rom.zip file, put that on my sd card, rename it to 0P6BIMG.zip and let the phone flash that. First there are 2 zip files (rom_01.zip and rom_02.zip) in the temp directory and I don't know which to use. I tried the larger of the two files but got an error about large zip file when it tried to flash.
Any suggestions on getting on the latest update before I begin rooting and trying custom roms?
axeman71 said:
I downloaded the ruu from the HTC site I then tried to run the ruu.
Click to expand...
Click to collapse
What version number RUU?
axeman71 said:
It gives me an error 170. After researching the error and trying a few things still no luck.
Click to expand...
Click to collapse
If you don't specifically tell us what you tried, that second sentence isn't particularly useful.
Error 170 is USB connection error. RUU is very finicky, so just because other USB functions work, doesn't mean the RUU will. Try with the phone in bootloader-fastboot mode, try a different USB port, and different cable. USB 2.0 and Win7 have best compatibility with RUU.
axeman71 said:
I then tried to look in the windows temp files and get the rom.zip file, put that on my sd card, rename it to 0P6BIMG.zip and let the phone flash that. First there are 2 zip files (rom_01.zip and rom_02.zip) in the temp directory and I don't know which to use. I tried the larger of the two files but got an error about large zip file when it tried to flash.
Click to expand...
Click to collapse
I'm not familiar with the instance of 2 different ROM.zip files being generated in the temp folder, so its impossible for me to say which to flash, and/or if they are safe.
Large zip file error when flashing zip is usually because there is a new requirement with the MM ROM, where you need to flash the MM firmware.zip before you can RUU. But I can give more guidance once you specify which RUU you are trying.
I am trying to update to RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5_combined. I did try 2 different USB ports and 2 different cables but I was still getting the Error 170 USB error. I have Windows 10, I don't currently have access to a Windows 7 machine.
I thought the 2 roms was strange too. I didn't find reference to it anywhere in my searches.
I have been trying the bootloader-fastboot method but the process hangs at either "Updating...(1/2)Sending" or "Updating...(2/2)Sending". After an hour or and hour and a half I finally just disconnect the phone and reboot it.
axeman71 said:
I am trying to update to RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5_combined. I did try 2 different USB ports and 2 different cables but I was still getting the Error 170 USB error. I have Windows 10, I don't currently have access to a Windows 7 machine.
Click to expand...
Click to collapse
You can't update by RUU to MM, unless you flash the MM firmware.zip first. Its some new requirement HTC added with all the MM RUUs. See the red text under RUU section of my Index thread, for instructions on flashing the firmware: http://forum.xda-developers.com/showthread.php?t=2751432
Although, failure to flash the firmware usually results in Error 155 Unknown Error. I suspect you still have some PC incompatibility with the RUU. Some folks have mentioned you can temporarily "turn off" USB 3.0 (if you have it) and make the port use USB 2.0. I'm not too familiar how to do that, but at least one guy had success with the RUU that way. So may be worth looking into. Otherwise, you may need to try to find a Win7 PC you can use.
The other option is to flash the firmware, then try the ROM zip again by SD card method. But I'm still a bit uneasy why there are 2 ROM zips, so do so at your own risk.
Awesome, flashing the firmware first worked. Strange that HTC would put the file and instructions on their website knowing it's not going to work without the firmware.
Thanks
axeman71 said:
Awesome, flashing the firmware first worked. Strange that HTC would put the file and instructions on their website knowing it's not going to work without the firmware.
Thanks
Click to expand...
Click to collapse
Happy to see it worked for you.
Yeah, I agree its strange. Folks fairly frequently need to resort to RUU to update, due to OTA not working or not available (such as you). So its odd to introduce the requirement to flash the firmware (which the huge majority of users won't have the skills or resources to even figure out is a requirement, must less perform), which AFAIK is present in every MM RUU for the M8 (not just AT&T).
Related
Hey guys/girls
i was messing with my mogul and now its stuck on the tri color screen.
Software
TITA100
SPL-1.20.Olipro
please if any one can help i would appreicate it.
Plug into usb and install your carriers current rom
wont let me. i get a connection error. it stops on 11% when trying to update the rom.
flash by microsd method. This will eliminate all usb problems
drewcam888 said:
flash by microsd method. This will eliminate all usb problems
Click to expand...
Click to collapse
is their any way to send me a link to the right update? because i tried the one from HTC via microcard and it wont load anything.
That would be hard in that I know nothing about your carrier. But I only have Verizon stuff. Maybe add your info to every post.
drewcam888 said:
That would be hard in that I know nothing about your carrier. But I only have Verizon stuff. Maybe add your info to every post.
Click to expand...
Click to collapse
i have sprint.
also i had 6.1 loaded inside
but now its stuck on the loader screen so prob dont have any software.
tank319 said:
wont let me. i get a connection error. it stops on 11% when trying to update the rom.
Click to expand...
Click to collapse
are you using VMWARE Fusion or Parallels Desktop?
If so, update to the lastest version and/or change the settings to "GUEST ONLY" for USB......
I has that issue a while back on a treo, several during the update process it "disconnects" the USB momentarily....
If you had it set to "ask me" then, it would attempt to "ask you.", causing the updater no not see it. (No fusion or parallels, because there is no valid firmware on the device.)
If that was your issue, let me know, please.
Just download the lastest rom and extract the .nbh from the .exe with winrar. Rename it properly and flash away.
Also, you may way to look into either olipro 2.40 or nueSPL 2.47 for your bootloader. It could be that you are trying to load an incompatible ROM. Check the wikis and stickies for a compatibility list of bootloader/radio/ROM.
i got it to turn on and stay on but i cant update it to 6.1 because of the SPL 1.20 bootloader i think how can i update it. i have dcd_2[1].0.0_beta_sprint.exe but it will not load on my phone even if i change the name. any idea's? also i tried to RUU_TITAN_SPRINT_WWE_3.56.651.0_RS_TITAN_3.42.02_SPCS2.04_PPST_0718_Ship.exe flash that on and still gives an error.
BTW thanks alot for helping me out
Look at Step II - 1 in the wiki. http://wiki.xda-developers.com/index.php?pagename=TitanRecentHome
You are also using a pretty old ROM made by DCD. He made a bunch more that worked very well before he stopped posting.
As title says. Had Villain installed on my Hero, and looking to put stock back onto it, I don't care if this "un-roots" it either. Is this possible?
I've tried downloading the normal RRU and that malarky and it just won't recognise the USB through the HTC client, always comes up with the same error. I read around and saw that a ROOT cannot be used / put on without using a custom rom, so is there any way of getting a stock rom on, or reversing things? I think you guys get the idea of what I'm on about.. cheers!
(p.s. Doing this because I've got a Legend now, and selling my Hero soon..).
Re: Reverting to stock ROM from Villian6?
There is a guide by BTDAG in the development section called something like " Setting up drivers for x86 x64", should be on pg 1, 2 or 3 in Development. Use that to make sure the drivers for HTC Sync are set up correct.
-------------------------------------
Sent via the XDA Tapatalk App
I tried the guide you suggested, downloaded it all and so on.
Did it all a few times just to check I was installing my drivers properly.
Everything reads fine now driver wise, but still comes up with the error when running the RRU and analysing my Hero.
Do I need to install a different, fresh OS of some form as something seems wrong with mine now I've probably screwed with it or...?
Help would be appreciated in any form..
00Sparrow said:
I tried the guide you suggested, downloaded it all and so on.
Did it all a few times just to check I was installing my drivers properly.
Everything reads fine now driver wise, but still comes up with the error when running the RRU and analysing my Hero.
Do I need to install a different, fresh OS of some form as something seems wrong with mine now I've probably screwed with it or...?
Help would be appreciated in any form..
Click to expand...
Click to collapse
You got the goldcard in the phone? Or is it a USB error?
ddotpatel said:
There is a guide by BTDAG in the development section called something like " Setting up drivers for x86 x64", should be on pg 1, 2 or 3 in Development. Use that to make sure the drivers for HTC Sync are set up correct.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
I tried the guide you suggested, downloaded it all and so on.
Did it all a few times just to check I was installing my drivers properly.
Everything reads fine now driver wise, but still comes up with the error when running the RRU and analysing my Hero.
Do I need to install a different, fresh OS of some form as something seems wrong with mine now I've probably screwed with it or...?
Help would be appreciated in any form..
anon2122 said:
You got the goldcard in the phone? Or is it a USB error?
Click to expand...
Click to collapse
Goldcard? It says it's a USB error when the prompt comes up.
I had more or less the same problem.
If I'm not wrong, the application "HTC Sync" has to be present on your ROM to make the RUU installation possible.
This application could has been removed from the ROM you're using to save phone memory.
Try to reinstall this "HTC Sync" on your phone and try the RUU again.
And how do you install HTC Sync on your HERO with custom ROM?
I've got the same problem... But I also can't find the RUU for Belgium...
You have to find the apk PCSCII.apk and push it to /system/app of your phone.
Take a look here :
http: //forum. xda-developers. com/showthread.php?t=588351&page=37
Even more simple :
restore the nandroid backup your should have been done before installing the custom ROM your are using, then try to RUU
Funny, i tried goldcard and most of the other guides. But in the end, i found out that it only worked when i flashed the stock rom i wanted to downgrade to, from bootloader.
Then run the RUU setup for the rom you have flashed on the phone..
Worked for me
ueikap said:
You have to find the apk PCSCII.apk and push it to /system/app of your phone.
Take a look here :
http: //forum. xda-developers. com/showthread.php?t=588351&page=37
Click to expand...
Click to collapse
And then my HTC Sync is installed?
Install the application HTC Sync on your pc,
if this application detect your phone and you see sync icon in the notification bar, the RUU should recognise it as well and you would be able to revert to stock.
Hello Everyone
I know, there are many How-To's and ways to achieve what I want. unfortunately non of those I tried have worked.
My goal. I want to unroot my Hero, to send it back to RMA, because the usb controller is not working. And this is the second biggest Problem atm.
All the How-To's to unroot the device an install the original RUU or at least most of them include the use of the USB function. (creating a gold card 4 example or flashing a different bootloader)
To the USB Controller. It is hopeless. I tried everything. I even set up a Linux VM but where ever I plug it in, the system won't recognise my hero. They don't even recognise something.
Lucky me, the Hero is still able to charge the battery.
*****
Ok lets give some details on the actual situation.
I'm able to boot to HBOOT/Fastboot (volume down)
I'm able to boot to Clockwork Mod Recovery 2.5.0.7 (home)
Right now, it's restoring the system to FroydVillain 1.7.1, because i formated the boot partition (After 5 hours, I was tired and did one big mistake)
> The restore worked. I have my old System again.
What I tried to do
1. I downloaded the actual RUU, ran it, got the rom.zip out of it.
2. Booted into Clockwork Mod and tried to install from zip, where i got [Error Message 1]
3. Renamed the rom to update.zip and tried to install toe "normal" way. Also got the same [Error Message 1]
4. Renamed the rom into HEROIMG.zip, ran HBOOT which checks the zip and led me to [Error Message 2]
Error Message 1
Code:
-- Installing: SDCARD:rom.zip
Finding update package ...
Opeing update package...
E:Can't open /sdcard/rom.zip (bad)
Installation aborted
Error Message 2
Code:
SD Checking...
Loading...[HERODIAG.zip]
No image!
Loading...[HERODIA3.nbh]
No image or wrong image!
Loading...[HERODIA2.nbh]
No image or wrong image!
Loading...[HERODIAG.nbh]
No image or wrong image!
Loading...[HEROIMG.zip] // takes about 3 minutes...
Checking HEROIMG.zip // takes about 1 minute...
Main Verion is older!
Update Fail!
I downloaded the actual Hero RUU three times from the website, in case something went wrong while dl.
I got an older RUU from a xda thread and tried it with tis one.
I am not able to create a goldcard, because you have to connect the phone via usb to a computer.
Well Any help is much appreciated.
Regards
mae`
Hey,
really sh*tty that usb ain't working..
having trouble from time to time myself, got a suggestion for ya though
1) find yourself a rom that is very close to a stock rom (suggesting stock WWE,
as can be found on this forum, mr bang, stock wwe rooted)
http://www.romraid.com/paul/hero/upd...5.5-signed.zip (maybe an option)
2) make sure it doesn't have a customized kernel (or flash the stock one )
3) make sure it doesn't have apps2sd
4) use universal androot => UNROOT
5) delete busybox from your phone
guess this should get as close as it can be to a stock sense rom
(meaning unrooted and minor customizations
grtz, [email protected]
Hey mattnmd
Thank you for the hints!
Actually I could not download the ROM because the link seems "wrong" but it pointed me in the right direction.
I found e repacked Stock ROM (1.5) which I was able to flash.
So... My base system is ok for the moment. BUT my recovery is not
There is still clockworkmod recovery installed and it won't let me install updates.
Now in the next step I need a way to flash a different recovery (the original) without the use of USB.
androot does work. btw =)
Thanks a lot
mae` said:
Now in the next step I need a way to flash a different recovery (the original) without the use of USB.
Thanks a lot
Click to expand...
Click to collapse
np man, but here i can't help
never got the problem
grtz
Put the Hero like stock without USB
Is there a solution for this already?!! I've exactly the same problem - USB doesn't works, not even for charge! And I need to make it stock-alike in order to send it to warranty. I managed to install the stock ROM but still, there's the AmonRa Bootloader installed... I created a goldcard without USB using this: w ww.mikesouthby.co.uk/2010/08/htc-desire-creating-goldcard-using-mac-or-linux/
but, when I try to apply the HEROIMG.zip trough Hboot, it says "Main version is older"
What am I missing?! Is the installed radio too recent for the stock image I'm trying to install?!
I have no solution jet. But I'll write as soon as I see a way.
_________________________
HTC Desire S - xda app
Worked for me!!!
Well, I found a way to solve my problem! I needed to put my GSM Hero as stock as possible (without root/custom ROMS/AmonRa/etc) without USB... The only solution, as far as I've read is to flash using a GoldCard the zip file from the RUU *.exe from HTC. I manage to create the GoldenCard without USB but when I tried to flash, it would say "Main Version is Older" after checking the HEROIMG.zip . It finally worked when I used this particular RUU version: RUU_Hero_HTC_WWE_2.73.405.38_WWE_release_signed_No Driver.exe from XDA thread #559622. Give it a try
Finally done
Hey dusturn
You are my (HTC) Hero
I just made the goldcard, and installed the new/old image (2.73.405.38) The Device got the old cupcake 1.5 on it and I was not able to get into recovery anymore!
It finally seems to be ok! Thank you very much!
dusturn said:
Well, I found a way to solve my problem! I needed to put my GSM Hero as stock as possible (without root/custom ROMS/AmonRa/etc) without USB... The only solution, as far as I've read is to flash using a GoldCard the zip file from the RUU *.exe from HTC. I manage to create the GoldenCard without USB but when I tried to flash, it would say "Main Version is Older" after checking the HEROIMG.zip . It finally worked when I used this particular RUU version: RUU_Hero_HTC_WWE_2.73.405.38_WWE_release_signed_No Driver.exe from XDA thread #559622. Give it a try
Click to expand...
Click to collapse
How did you make goldcard without USB? I have the same problem but cannot find a solution.
Hi Guys,
Long-time listener, first-time caller..
I have a feeling I’ve broken my HTC One X+ [enrc2b] (UK Vodafone running CM10.2) due to a bad upgrade.
I had Cyanogen 10.2 installed and have been happily using and updating it via the built in CM update tool.
I went from stable to nightly a couple months ago and have never found any major issues so continued to use nightlies.
On Sunday (12th Jan) a new CM update was made available and I went through the usual process without really looking closely at the update. The update was for CM11. (Shouldn't matter? I've flashed new boot.img's before when required).
The update downloaded so the phone rebooted and went to flash, but failed halfway through due to a corrupt download.
I’m not sure if it was the file on the CM servers or if the download simply corrupted but I’ve never seen a similar issue and didn’t interrupt the update so I’m guessing it was a bad file uploaded for the update.
This is where it gets messy.
I had removed the previous update files so there are none available in the /cmupdate/ folder other than the CM11 version. If I had kept just one I wouldn't be in this situation (lesson learnt!).
My phone DOES NOT have USB debugging turned on, therefore I am not able to use ADB to push files to the device. Is there anyway to send files to the phone without using ADB. I'm pretty familiar with fastboot but can only flash recovery/boot using fastboot (?).
I’ve tried flashing the stock recovery so I can use the RUU for Vodafone UK but the RUU flsah fails. I’ve re-locked the bootloader and have the stock recovery but I get an error when using the RUU.
The RUU is v1.14 and my phone has v1.17 (from CM) so I suspect this is the problem as the version needs to be greater than the current?
The error from the RUU is related to the bootloader (error 140). I’ve tried a couple different versions of RUU such as a Europe one with v1.17 but it throws the wrong region code error when trying to flash.
I don’t have a nandriod back up. I thought I had done when I originally unlocked and rooted the phone. Turns out that it didn’t work.
I have downloaded a couple nandriods that I think would work but because I don’t have ADB working I can’t push the files to the device anyway.
I have CWM recovery installed again now, after the failed RUU update, and a version of hboot (that’ll check when I get home). I think it’s 1.400?
So, is my phone save-able, or is it now a paperweight. Any and all help appreciated.
A lot of the posts relating to fixing similar issues assume you have ADB/USB debug available, and I don’t! I have done a lot of reading over the past couple of days but am no closer to resolving this.
In case it helps, I can grab the zips from the RUU temp folder but wouldn't know how to flash them (does it need ADB?).
Can anyone help?
max3o6 said:
Hi Guys,
Long-time listener, first-time caller..
I have a feeling I’ve broken my HTC One X+ [enrc2b] (UK Vodafone running CM10.2) due to a bad upgrade.
I had Cyanogen 10.2 installed and have been happily using and updating it via the built in CM update tool.
I went from stable to nightly a couple months ago and have never found any major issues so continued to use nightlies.
On Sunday (12th Jan) a new CM update was made available and I went through the usual process without really looking closely at the update. The update was for CM11. (Shouldn't matter? I've flashed new boot.img's before when required).
The update downloaded so the phone rebooted and went to flash, but failed halfway through due to a corrupt download.
I’m not sure if it was the file on the CM servers or if the download simply corrupted but I’ve never seen a similar issue and didn’t interrupt the update so I’m guessing it was a bad file uploaded for the update.
This is where it gets messy.
I had removed the previous update files so there are none available in the /cmupdate/ folder other than the CM11 version. If I had kept just one I wouldn't be in this situation (lesson learnt!).
My phone DOES NOT have USB debugging turned on, therefore I am not able to use ADB to push files to the device. Is there anyway to send files to the phone without using ADB. I'm pretty familiar with fastboot but can only flash recovery/boot using fastboot (?).
I’ve tried flashing the stock recovery so I can use the RUU for Vodafone UK but the RUU flsah fails. I’ve re-locked the bootloader and have the stock recovery but I get an error when using the RUU.
The RUU is v1.14 and my phone has v1.17 (from CM) so I suspect this is the problem as the version needs to be greater than the current?
The error from the RUU is related to the bootloader (error 140). I’ve tried a couple different versions of RUU such as a Europe one with v1.17 but it throws the wrong region code error when trying to flash.
I don’t have a nandriod back up. I thought I had done when I originally unlocked and rooted the phone. Turns out that it didn’t work.
I have downloaded a couple nandriods that I think would work but because I don’t have ADB working I can’t push the files to the device anyway.
I have CWM recovery installed again now, after the failed RUU update, and a version of hboot (that’ll check when I get home). I think it’s 1.400?
So, is my phone save-able, or is it now a paperweight. Any and all help appreciated.
A lot of the posts relating to fixing similar issues assume you have ADB/USB debug available, and I don’t! I have done a lot of reading over the past couple of days but am no closer to resolving this.
In case it helps, I can grab the zips from the RUU temp folder but wouldn't know how to flash them (does it need ADB?).
Can anyone help?
Click to expand...
Click to collapse
the phone when on recovery doesn't need the USB debugging to be turned on....
if u had installed the proper drivers u will be able to see ur phone as on recovery.....
[email protected] said:
the phone when on recovery doesn't need the USB debugging to be turned on....
if u had installed the proper drivers u will be able to see ur phone as on recovery.....
Click to expand...
Click to collapse
Hmm, ok thanks. Maybe I need to reinstall ADB drivers. The HTC USB drivers work ok (fastboot usb is fine) and I do have ADB installed but having meddled with it (reinstalled ADB) I should try pushing again I guess.
Thanks, will try when when home! :good:
ADB without USB debugging turn on
Now sorted!
ADB works when the phone is in recovery, not in hboot. Dur.
Thanks!
So guys, I'm new to this and thought I would jump in at the deep end.
I unlocked my HTC One X+ easily and set about rooting.
I've got TWRP installed but it keeps telling me it needs to install superuser before it can root.
I have totally wiped the phone, how come if Im not rooted?
How do I get an OS and indeed the kernel or ROM onto the phone?
Its and International OX+, I've got the right kernel... what do I need to do?
It was locked to O2 if that makes a difference
I followed the instruction in Hasson but then wiped the OS
I know its a simple procedure but can someone walk me through it please
So I've downloaded Kernel 3.1.10-ge7581e4
I have no idea what to do next, come on guys I know its not difficult for you guys.
eskimosound said:
So I've downloaded Kernel 3.1.10-ge7581e4
I have no idea what to do next, come on guys I know its not difficult for you guys.
Click to expand...
Click to collapse
If you wiped as you said, you need to push with adb a rom of your choice to the internal memory of the phone and then install it within twrp.
Please read instructions 2 or 3 times before attempting anything, seems like you rushed and now you're temporarily without phone till you flash a rom on it again. I doubt any root guide tells you to wipe the phone, your own fault on this.
To sum it up:
Put a rom's zip of your choice in the internal memory with adb push
flash the rom within the twrp recovery (install option)
flash the kernel for the specific rom with fastboot (each rom has a guide and download for it)
You can now search about it more easily, plenty of posts and info about this.
dan_alexandre said:
If you wiped as you said, you need to push with adb a rom of your choice to the internal memory of the phone and then install it within twrp.
Please read instructions 2 or 3 times before attempting anything, seems like you rushed and now you're temporarily without phone till you flash a rom on it again. I doubt any root guide tells you to wipe the phone, your own fault on this.
To sum it up:
Put a rom's zip of your choice in the internal memory with adb push
flash the rom within the twrp recovery (install option)
flash the kernel for the specific rom with fastboot (each rom has a guide and download for it)
You can now search about it more easily, plenty of posts and info about this.
Click to expand...
Click to collapse
Thanks, I did indeed rush into it but I have been meaning to do it for a year and just thought go for it, I know its all salvageable..ish!
So yep, I've got the ROM I want but don't understand the kernel, I see no guide to download it, all I know is I took a note of the Kernel before I wiped my phone and I have managed to find the exact kernel.
The ROM or RUU as it is, is an O2 UK version, I figure it must be the one I want as it was an O2 phone in the UK.
I still don't know what folders to put things in, TWRP can't see a boot.img that I have on the phone when installing, it can only see it through file explorer.
And then, every time I power down the phone TWRP asks to install Superuser, its cant, theres nothing to install it to, so it just keeps asking.
This is all because I hated the Sense 5 update, indeed Im till looking for the Sense 4 ROM fo HOX+
eskimosound said:
Thanks, I did indeed rush into it but I have been meaning to do it for a year and just thought go for it, I know its all salvageable..ish!
So yep, I've got the ROM I want but don't understand the kernel, I see no guide to download it, all I know is I took a note of the Kernel before I wiped my phone and I have managed to find the exact kernel.
The ROM or RUU as it is, is an O2 UK version, I figure it must be the one I want as it was an O2 phone in the UK.
I still don't know what folders to put things in, TWRP can't see a boot.img that I have on the phone when installing, it can only see it through file explorer.
And then, every time I power down the phone TWRP asks to install Superuser, its cant, theres nothing to install it to, so it just keeps asking.
This is all because I hated the Sense 5 update, indeed Im till looking for the Sense 4 ROM fo HOX+
Click to expand...
Click to collapse
Sigh, if you had read carefully you'd know that boot.img need to be flashed through fastboot and not from recovery. Every rom has this info or a batch file for this.
So what exactly are you trying to do? Root the stock rom that came originally with the phone or installing a custom rom?
dan_alexandre said:
Sigh, if you had read carefully you'd know that boot.img need to be flashed through fastboot and not from recovery. Every rom has this info or a batch file for this.
So what exactly are you trying to do? Root the stock rom that came originally with the phone or installing a custom rom?
Click to expand...
Click to collapse
Lols, thanks dan, I hope you don't hate me!
Root the stock ROM
For starters..
The boot.img is the Android Revolution HD
The RUU is O2 UK
I do realise they are two different ways of installing an OS, I would just like one of them to work!
So think install RUU, then kernel
But put them where and how
I bought the Android Hackers book, but theres nothing about HOX+ in it, and seeing as that's the only phone, I've got to practise on I thought I would ask you specifically.
eskimosound said:
Lols, thanks dan, I hope you don't hate me!
Root the stock ROM
For starters..
The boot.img is the Android Revolution HD
The RUU is O2 UK
I do realise they are two different ways of installing an OS, I would just like one of them to work!
So think install RUU, then kernel
But put them where and how
I bought the Android Hackers book, but theres nothing about HOX+ in it, and seeing as that's the only phone, I've got to practise on I thought I would ask you specifically.
Click to expand...
Click to collapse
I see, the easiest ways would be to use a custom rom now. For example, the one you already got the kernel from(android revolution hd)
To root you dont need to install a kernel... just to flash the supersu zip. Using a custom rom's kernel with stock rom might not be a good idea.
Another simple way would be to restore stock rom back to start and try rooting again, this time reading everything carefully
So the two easiest ways i think:
1) flash a custom rom following the instructions they provide in the initial posts for that rom
2) run the o2 correspondent RUU to restore stock rom (you'd need to relock the bootloader), also reading carefully posts in the forum about restoring to stock
Without getting into too much detail, these are the simplest options.
All the info required to do these are on these forums
Aaarrghhh, its driving me insane as I knew it would, just like XP, Vista Seven and Eight!!!
So Im back to being up all night learning..
Well have installed SDK correctly but device is not seen, no serial, nothing.
I can get it to fastboot though, however I don't know any commands so I cant get it to work
Windows 7 keeps moaning about an mpt file which I downloaded and dont know where to extract it to
All I need to do is copy a few files to the phones sd card and install them right?
Whys that so difficult?
I don't know the difference between a rom an ruu and a boot image, in that I don't know where they should all be placed.
Why cant twrp copy and paste from pc...
So Hassooon works sort of but still none the wiser.
Am following tutorial but fastboot commands are not working
Still cant find right driver.....
So CMD lines not working 100%
So am downloading drivers in sdk manager
And how do I flash the supersu zip?
Still no luck with driver, im on windows 7 32bit
OK I cant push using adb it cant find the file or directory,
Hassooon cant detect the phone as cant windroid universal
I dont think the phone is rooted even though i have twrp on it.
Thus can I have wiped the os?
If not can i restore it?
No I didnt make a backup rom..
mmm a zip on the phone doesnt load in bootloader, count that be my os?
Guys, im stranded in the water here...
On boot im getting...
Failed to open usb master mode
[Preload] Failed to open usb master mode
loading PM35IMG.zip image...
Failed to open usb master mode
please plug off usb
Whats PM35IMG.zip?
Is that the OS?
Am I saved?
Is it easy to get that file to unzip and load?
Can anyone help?
So now I need the right RUU.....
2.17.206.3
Is there anyone out there that can help please?
So have managed to install superuser and root my phone, all instructions for doing this were wrong including Hassoon, had to have the phone in System screen to do it, not bootloader or recovery.
Now cant get adb to push file to sdcard...
Man alive, how to make something very easy, sound very difficult.
Would any of you experts care to help?
Just trying to install a ROM.zip to Root and place the boot img in right place.
Well, the instructions are dire but after 10 days of persistance have installed Android Revolution HD 8, finally my phone is up and running better than the bloated os that came with the phone so, you can call this thread resolved.