Related
Alright guys, I've searched and searched and I think I have it all down, just want to lay out my steps and get verification.
I'm on T-Mo ICS, not from OTA, flashed myself
Root
S-Off
4-Ext
I'm sending my phone in and need to go back to stock. I think I would prefer to go back to GB so it's just like from factory with no OTA.
- Download the Stock GB RUU from here - HTC Ruby/Amaze 4G Stock ROMs
- The RUU I want is - PH85IMG_Ruby_TMOUS_1.43.531.3_Radio_1.08.550L.19DC _30.66.550L.08D_release_228638_signed
- Following These Directions I connect via ADB and fastboot oem lock This will show it as Re-Locked, correct?
- Reboot
- Flash the stock RUU I got by placing it in the root of my external sd card and renaming it PH85IMG.zip and rebooting to bootloader. Which is Volume Down + Power? Can someone verify that?
- Then I set the security lock by doing "fastboot oem writesecureflag 3" - This will change the bootloader to show locked, not re-locked, correct? I thought you had to have root to ADB?
At that point I'm back as if I took the phone out of the box for the first time? 4ext will be replaced with Stock Recovery? Thanks in advance. Like I said, I've searched, but there are many conflicting reports. :good:
Minker17 said:
Alright guys, I've searched and searched and I think I have it all down, just want to lay out my steps and get verification.
I'm on T-Mo ICS, not from OTA, flashed myself
Root
S-Off
4-Ext
I'm sending my phone in and need to go back to stock. I think I would prefer to go back to GB so it's just like from factory with no OTA.
- Download the Stock GB RUU from here - HTC Ruby/Amaze 4G Stock ROMs
- The RUU I want is - PH85IMG_Ruby_TMOUS_1.43.531.3_Radio_1.08.550L.19DC _30.66.550L.08D_release_228638_signed
- Following These Directions I connect via ADB and fastboot oem lock This will show it as Re-Locked, correct?
- Reboot
- Flash the stock RUU I got by placing it in the root of my external sd card and renaming it PH85IMG.zip and rebooting to bootloader. Which is Volume Down + Power? Can someone verify that?
- Then I set the security lock by doing "fastboot oem writesecureflag 3" - This will change the bootloader to show locked, not re-locked, correct? I thought you had to have root to ADB?
At that point I'm back as if I took the phone out of the box for the first time? 4ext will be replaced with Stock Recovery? Thanks in advance. Like I said, I've searched, but there are many conflicting reports. :good:
Click to expand...
Click to collapse
In order to flash the factory RUU you need to be either locked or relocked. Then when you flash the factory RUU it should overwrite your hboot which will reset from "relocked" to "locked" then the writesecureflasg function will turn S-ON and you'll be factory.
freakasis said:
In order to flash the factory RUU you need to be either locked or relocked. Then when you flash the factory RUU it should overwrite your hboot which will reset from "relocked" to "locked" then the writesecureflasg function will turn S-ON and you'll be factory.
Click to expand...
Click to collapse
If you're s-off you don't need to lock or relock to flash a stock ruu.
Sent from my SGH-T999 using xda app-developers app
Dark Nightmare said:
If you're s-off you don't need to lock or relock to flash a stock ruu.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Guess that does make sense, huh?
But everything looks OK then?
Update - Downloaded and renamed the RUU, rebooted into recovery and installed everything. Bootloader shows locked and I went ahead and did the ICS Update. Everything is back to factory and I'm ready to send it back.
Final Steps
Minker17 said:
Update - Downloaded and renamed the RUU, rebooted into recovery and installed everything. Bootloader shows locked and I went ahead and did the ICS Update. Everything is back to factory and I'm ready to send it back.
Click to expand...
Click to collapse
Rick. Like you, I want to bring my T-Mobile HTC Amaze back to stock so that I can upgrade to ICS. The phone was bought on eBay with GB and a custom rom. I'd like to follow your steps but it had a lot of question marks and/or needed confirmation. Will you post exactly what you did?
Your steps seems a lot easier than what I've been researching. Is it really that simple? It makes sense. Everyone else uses hasoon2000 toolkit. Thanks for your time!
TheCount01 said:
Rick. Like you, I want to bring my T-Mobile HTC Amaze back to stock so that I can upgrade to ICS. The phone was bought on eBay with GB and a custom rom. I'd like to follow your steps but it had a lot of question marks and/or needed confirmation. Will you post exactly what you did?
Your steps seems a lot easier than what I've been researching. Is it really that simple? It makes sense. Everyone else uses hasoon2000 toolkit. Thanks for your time!
Click to expand...
Click to collapse
You don't need to go back to stock you just need to download the factory ics ruu or a rom that stock like. The hasoon toolkit is more of a guide to help you with the process try to read it an maybe you can rom your cell with a better one!
Sent from my HTC_Amaze_4G using xda app-developers app
S-off
FutureAirways said:
You don't need to go back to stock you just need to download the factory ics ruu or a rom that stock like. The hasoon toolkit is more of a guide to help you with the process try to read it an maybe you can rom your cell with a better one!
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
Thanks for your reply. That makes sense, too. Plus, it'll save me a step. I'm new to Android and got a lot to learn. With the help of xda-developers, I've learned a lot these past three weeks.
From what I've been reading, it's apparent that I need to have S-off before I do any flashing. Like I mentioned, I bought the phone with a custom rom. I'm guessing if it has a custom rom, then it was S-off at one time. If so, I should be able to S-off easily. Since I didn't flash the phone, I'm not sure what program is installed. Your knowledge and experience will be greatly appreciated if you can tell me if I'm able to S-off easily and how. Whenever I go into HBOOT I see the following:
***UNLOCKED***
RUBY PVT SHIP S-ON RL
HBOOT-1.90.0008
eMMC-boot
FASTBOOT
<vol up> to previous item
<vol Down> to next item
<Power>
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
I bought Evo which was already upgraded to ICS (OTA I assume), and it was branded I think. I've unlocked it via HTCDev, flashed '4ext touch recovery' and then rooted. Then I flashed MIUI ICS ROM, and everything is OK for now.
I want to use BootManager to flash multiple ROMs. It requires s-off. I tried it already with s-on, because I've read that SmartFlash (from 4ext recovery) makes my phone like s-off, so ROM on SD card installed, but won't boot. I had many problems going back to my Phone ROM, I restored my backup, wiped many times, installed fresh ROM and still had a bootloop. Finally I got it working again by flashing boot.img via fastboot (glad I did nandroid backup before). I didn't try again with different ROM, because after 2 hours of trying to recover my base ROM I've had enough. So I'm pretty sure BootManager will work better if my phone will be s-off.
So my question is - what to do next? We have so many guides and different comments here, sometimes the same method works for one, and doesn't work for another one, and I'm really confused.
I assume I should follow the instructions here http://forum.xda-developers.com/showthread.php?t=1743466 but I don't understand few things:
friend.evil said:
flash an ICS ROM from recovery(Method B from 10 to 14)
open ICS ROM.zip and extract boot.img to a folder which contains adb, fastboot and AdbWinApi.dll
go to fastboot and type:
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
Do I have to do this if I'm already have MIUI with root privileges? Do I still need that boot.img from MIUI, and put it together with fastboot.exe?
Or should I restore stock ICS? I'm pretty sure I did nandroid backup before flashing MIUI.
friend.evil said:
12_Notice when you s-off the phone the hboot is corrupted i advice after s-off to follow the methods In E_(from 1 to 4)
Click to expand...
Click to collapse
Do I need to fix hboot after s-off? What hboot version I have after doing steps 1 to 4 from section E? There's a big zip file (PG86IMG.zip), is it another ROM or what?
And most important question - if method D doesn't work, method F is recommended, but:
elias17 said:
Hboot s on will only flash roms that are based on ics 3.28xx and sense 4 roms using a special boot.img ! U can never flash GB roms until u go s off like i did its a tricky process but it works and now i can flash any rom in the gsm section
Click to expand...
Click to collapse
friend.evil said:
2_flash Leedroid GB ROM from recovery http://leedroid.ftp.rshost.eu/Shoote....zip(Don't forget to wipe data/factory reset and wipe cache + dalvik)
Click to expand...
Click to collapse
I don't get it - can I flash GB ROM or not if I have hboot 1.53.0007 s-on? Can I use method F if method D fail?
Sorry for my english, I'm from Poland.
Thanks in advance for any tip.
You're confusing yourself, What you need to do my friend is.
1. Download RUU, Run RUU
2. HTC Unlock bootloader again
3. Do the Juopunutbear Wiretrick to get s-off
4. Download the 1.04 ENG hboot (There is one of those for the GSM I think... not sure though)
5. Flash a badass Android 4.2.1 rom. They work.
There's much more detailed guides on what to do, BUT This is a summary of what you want.
Be sure to hit thanks [= I'm almost to 100
Which RUU should I search for? GB or ICS?
But isn't the 1+2 the same as restoring my ICS Stock ROM from backup?
I think hboot 1.49.0007 would be enough, I've read that BootManager works well with that version.
1. Yes you can just restore your stock ics backup BUT you will have to root it using the file provided in method B.
2. Yes the 1.49.0007 hboot is best for gsm
3. You can flash a GB rom with your hboot no problem. It just dont think it will boot. so technically you should be able to do the wire trick with a GB rom flashed(not booted into). You'll be in fastboot mode for the wiretrick. There are different files for GB and ICS when doing the wiretrick
Your best bet is to run an ICS RUU, unlock bootloader, root rom, do the wire trick, change hboot to 1.49.0007 and then flash any rom you want
Backup was made right after I made root, is it enough? I just don't want to go through the entire process from the beginning (unlocking, rooting etc).
mars28 said:
Backup was made right after I made root, is it enough? I just don't want to go through the entire process from the beginning (unlocking, rooting etc).
Click to expand...
Click to collapse
That should work But unlocking again is really easy
You should still have you unlock token in the same place,
You just plug up to the computer hop into fastboot usb and type
Fastboot flash unlocktoken Unlock_Code.bin
to unlock and then
fastboot flash recovery recovery.img
for a recovery,
Then move SU to your sd card and flash it in recovery.
Then your all ready for the wire trick, The more you do these things the more experience you get at them and the better you get with fastboot. I suggest you go through the process opposed to just restoring (First off it's much much safer) and you'll know the ropes if you (or anyone else) has this problem.
Maybe you're right. I'll try with RUU. But I see it's hard to find the correct one these days, some old links died. I have a file called "RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed" which I have downloaded right before I started unlocking my Evo, could it be the correct one?
I didn't know I can use old "unlock_code.bin", I saw that everytime I read the token from the device, it was different. So I assumed that I have to flash bin that match the token.
mars28 said:
Maybe you're right. I'll try with RUU. But I see it's hard to find the correct one these days, some old links died. I have a file called "RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed" which I have downloaded right before I started unlocking my Evo, could it be the correct one?
I didn't know I can use old "unlock_code.bin", I saw that everytime I read the token from the device, it was different. So I assumed that I have to flash bin that match the token.
Click to expand...
Click to collapse
The token and the unlock code are specific to the phone, And doesn't change until you get a new phone.
And that seems to be the right one, Do you live in Europe? lol Shooter u means GSM and ICS means it's the latest RUU.
mars28 said:
Maybe you're right. I'll try with RUU. But I see it's hard to find the correct one these days, some old links died. I have a file called "RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed" which I have downloaded right before I started unlocking my Evo, could it be the correct one?
I didn't know I can use old "unlock_code.bin", I saw that everytime I read the token from the device, it was different. So I assumed that I have to flash bin that match the token.
Click to expand...
Click to collapse
you can easily get a new token from htc dev web site
Sent from my HTC EVO 3D X515m using xda app-developers app
Can't_Live_Without_My_Evo said:
And that seems to be the right one, Do you live in Europe? lol Shooter u means GSM and ICS means it's the latest RUU.
Click to expand...
Click to collapse
I know I use shooter_u, I asked because I've found another RUU which have "Rogers_WWE" in name of the file, and the rest of the file name is identical, and I remember that I had to choose "rogers" when I was unlocking via htcdev. That's why I wasn't 100% sure if I had to choose "HTC_Europe" or "Rogers_WWE".
Another thing which confuses me:
http://forum.xda-developers.com/showthread.php?t=1495358
mpgrimm2 said:
Note 3: If you previously did the HTC Unlock, you'd have to "RELOCK" BEFORE running the RUU.
To do this from fastboot type: fastboot oem lock
Click to expand...
Click to collapse
Should I do this or start directly with RUU.exe? My phone is currently "UNLOCKED, hboot 1.53.0007, s-on".
And what about CID? I've read somewhere that I have to change to supercid or something, to be able to flash zips via fastboot. How to check my current CID?
Search for cid getter on play store to get your cid
You certainly need to relock you hboot before running RUU. For the correct ruu you should check the box that your phone came in. It should have the details (atleast i think so)
P.S. you probably don't need to change cid. Infact i'd recommend you not to do that just yet
Got the CID, it's HTC__032. I want to be prepared, who knows what might come up during the whole process.
friend.evil said:
12_Notice when you s-off the phone the hboot is corrupted i advice after s-off to follow the methods In E_(from 1 to 4)
Click to expand...
Click to collapse
What means "corrupted"? Phone won't boot or what?
Eeh, if I knew that hboot 1.53.x is so problematic, I would buy Evo with GB on-board.
mars28 said:
Got the CID, it's HTC__032. I want to be prepared, who knows what might come up during the whole process.
What means "corrupted"? Phone won't boot or what?
Eeh, if I knew that hboot 1.53.x is so problematic, I would buy Evo with GB on-board.
Click to expand...
Click to collapse
I think yours might be an european model. i had the exact same cid as yours.
when you get to that step of corrupted hboot just follow the steps on this thread and flash hboot 1.49.0007
http://forum.xda-developers.com/showthread.php?t=1906172
Cant kive without my evis comments about the wire trick are bang on. It will fix everything. Having s-off is just much easier so do the wire trick. It will work. My wife and I both have an evo. I had to do the wire trick twice on hers for it to work and four times on mine for it to work. Be patient if it fails the first few times. And if the screen gets stuck on the jounuo whatever screen you can fix that.
If you are stuck at Juopunutbear screen and if you can go to bootloader you need to connect the phone to pc, go to fastboot ( should say fastboot usb)*Go to controlbear folder (from where you ran controlbear to begin withon you pc then open command window in it (hold shift and right click, that willopen command window rigjt there and then*when you get into it you need to enter:
"ControlBear.exe -f" no quotes or "ControlBear f" notice the space after the exe !
Lots of peopke forget to put it in and say it didnt work.
I presume this will fix the problem
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
My phone is now s-off. I didn't flash RUU, just restored stock rooted ROM from backup, did the wire trick (just one time, surprisingly) and everything went nice and smooth. Then I flashed hboot 1.49.0007 with no problems at all. Thanks guys for the tips.
One more thing - my phone state is now "LOCKED" - should I bother?
So I got what I wanted - I've installed ROM in BootManager (the one which doesn't boot before, while phone was 's-on') and this time it booted from SD. Today I'll try more ROMs in BootManager.
Locked doesn't matter as long as you are s-off. It only creates problems if you ever plan on using fastboot commands. Trust me, you dont need to bother with it
But if you really want to know heres a quote from ramjet where he explains it a bit.
ramjet73 said:
Once the RUU.exe is run and the stock bootloader is installed, the phone will be bootloader S-ON regardless of the radio S-OFF status. To run fastboot commands like "flash" and "erase" the stock bootloader needs to be unlocked by the htcdev method or a custom bootloader modified to support those commands needs to be flashed, which requires radio S-OFF.
Click to expand...
Click to collapse
Hey guys. Yes I have searched, but have only found instructions so far for going back to stock gingerbread.
I need to send my amaze in to get fixed under warranty, and I'm assuming they won't like it if I send them the phone with an unlocked bootloader, rooted, and CM10 installed, and that's what I need help with. How can I reinstall stock ICS, unroot, and lock the bootloader of the amaze? And will it show as "relocked" or "locked"? Of course I plan on putting the root and unlocked bootloader and CM10 once I get it back, so I'm looking for a reversible way to do this. Thanks in advance!
Just to be clear. For your bootloader to say 'locked' you'll need to have S-Off and NOT unlock the bootloader again. But once that's done just flash the ICS ruu. Here's a link
http://forum.xda-developers.com/showthread.php?t=1647728
Double0EK said:
Just to be clear. For your bootloader to say 'locked' you'll need to have S-Off and NOT unlock the bootloader again. But once that's done just flash the ICS ruu. Here's a link
http://forum.xda-developers.com/showthread.php?t=1647728
Click to expand...
Click to collapse
Thank you. So I am S-ON right now. In order to make the bootloader say "locked" again to make HTC happy with my warranty, I'd have to be stuck with ICS and whatever updates HTC decides to give us from then on once I got it back from HTC?
No. That's the only way for it to say "locked" if you relock it it will say "relocked"
So if you really want it to say "locked" you'll need to S-Off first. Then flash the RUU.
Once you get it back you can do as you feel.
bruner1981 said:
Thank you. So I am S-ON right now. In order to make the bootloader say "locked" again to make HTC happy with my warranty, I'd have to be stuck with ICS and whatever updates HTC decides to give us from then on once I got it back from HTC?
Click to expand...
Click to collapse
What makes you think you will be stuck with anything? Everything u need to do is reversible and then re-doable.
Im just not really sure which part u think would make it stuck. Let us know and im sure we can explain the cofusion
After unlocking the bootloader with S-ON and installing a custom recovery/rom how do you revert to Stock.
I've tried relocking the bootloader, and using the AllinOneToolkit by Hanson to install the Factory RUU but it keeps failing after the HTC boot logo appears and the zip RUU file gets transferred to the phone. Keeps saying Failed with 12 signatures or something.
Then I read with S-ON that you had to use Hanson's tool and perform Fix Mainver, but that doesnt do anything either. Keeps saying, error cannot find device.
So, how do I go back to Stock?
Would appreciate any help!
Boot into fastboot, type "fastboot OEM lock" in the command prompt. Put the appropriate RUU on your external SD card and rename it PH85ING.zip and boot into bootloader.
Edit: its PH85IMG.zip. sorry about my fatty fingers. Also, make sure to check the md5 sum on the RUU. I always had trouble with the download.
Sent from my HTC Ruby using xda app-developers app
fubag said:
After unlocking the bootloader with S-ON and installing a custom recovery/rom how do you revert to Stock.
I've tried relocking the bootloader, and using the AllinOneToolkit by Hanson to install the Factory RUU but it keeps failing after the HTC boot logo appears and the zip RUU file gets transferred to the phone. Keeps saying Failed with 12 signatures or something.
Then I read with S-ON that you had to use Hanson's tool and perform Fix Mainver, but that doesnt do anything either. Keeps saying, error cannot find device.
So, how do I go back to Stock?
Would appreciate any help!
Click to expand...
Click to collapse
Fails after htc boot logo? If you are flashing an RUU, you should never see any boot screen until after its done flashing. What carrier are you on and what steps exactly r u fillowing to flash the ruu...?
aj_2423 said:
Fails after htc boot logo? If you are flashing an RUU, you should never see any boot screen until after its done flashing. What carrier are you on and what steps exactly r u fillowing to flash the ruu...?
Click to expand...
Click to collapse
its not the actual boot logo but that black screen with the HTC logo that I think is part of the stocky recovery maybe?
I have yet to try the PHS.IMG method in fastboot.
Thanks for the help!
fubag said:
its not the actual boot logo but that black screen with the HTC logo that I think is part of the stocky recovery maybe?
I have yet to try the PHS.IMG method in fastboot.
Thanks for the help!
Click to expand...
Click to collapse
Lol what do you mean you havent tried it? Flashing the PH85IMG.zip though the bootloader is the ONLY way to flash the RUU.
If you are on tmo follow this
http://forum.xda-developers.com/showthread.php?p=24294337
Sent from my
aj_2423 said:
Lol what do you mean you havent tried it? Flashing the PH85IMG.zip though the bootloader is the ONLY way to flash the RUU.
If you are on tmo follow this
http://forum.xda-developers.com/showthread.php?p=24294337
Sent from my
Click to expand...
Click to collapse
This only applies to tmobile versions? What about if we are on another carrier, I tried renaming the OTA updates but it doesnt do anything.
fubag said:
This only applies to tmobile versions? What about if we are on another carrier, I tried renaming the OTA updates but it doesnt do anything.
Click to expand...
Click to collapse
noo it has nothing to do with what carrier you're using at the moment...
Howdy folks...so my buddy picked up an M8 off of Craigslist that was apparently running some sort of vanilla android. It is unlocked and S off..he attempted to flash a Sense ROM and ended up in a boot loop. He's the kind of guy that shouldn't be doing such things...
This is where I come in to the rescue. After some reading this afternoon, I've come to the conclusion he must have a GPE converted phone. I personally have no experience with this device (G2 Verizon owner) but I'm pretty versed in fast boot and ADB.
The phone is currently in fast boot. This is all it has. If I attempt to boot it into recovery, it loops.
Can anyone help me get this thing running by pointing me in the right direction? Ideally, I'd like to have it fully AT&T stock.
My current plan was to push a recovery via fast boot and flash a GPE ROM off of SD. Will this work?
I just don't want to mess the phone up any further.
m8
Can you boot phone into bootloader? If so connect phone and type adb oem getvar all.
Should give you details of cid and rom required to get phone working again.
Googling ruu for cid will help so example is m8 ruu htc_001.
passion8059 said:
Can you boot phone into bootloader? If so connect phone and type adb oem getvar all.
Should give you details of cid and rom required to get phone working again.
Googling ruu for cid will help so example is m8 ruu htc_001.
Click to expand...
Click to collapse
Yes, bootloader is basically all I have. Thank you for the help!
I won't be able to get to work for a few hours, but I'll update with any progress.
OK...so turns out the phone indeed was converted to a GPE device, which caused his problem after attempting to flash a Sense ROM...I successfully flashed TWRP via fast boot and installed a GPE rom...now, just need to go about converting it back for him.
Thanks to member Passion for helping me out.
m8
mulhiny said:
OK...so turns out the phone indeed was converted to a GPE device, which caused his problem after attempting to flash a Sense ROM...I successfully flashed TWRP via fast boot and installed a GPE rom...now, just need to go about converting it back for him.
Thanks to member Passion for helping me out.
Click to expand...
Click to collapse
Change cid to super cid 11111111 (7 ones) by putting phone into fastboot , connect and typing fastboot oem writecid 1111111.
This allows phone to have most stock htc roms to be written to phone.
Find stock rom you require and flash which will revert to stock for you.
Hope this helps!
passion8059 said:
Change cid to super cid 11111111 (7 ones) by putting phone into fastboot , connect and typing fastboot oem writecid 1111111.
This allows phone to have most stock htc roms to be written to phone.
Find stock rom you require and flash which will revert to stock for you.
Click to expand...
Click to collapse
It appears the OP's phone had the full GPE conversion done to it, therefore changing the partitions, and that alone will prevent Sense ROMs for booting. Flashing a ROM in itself will not change the partitions back the Sense partition scheme.
Easiest way to revert is probably RUU. You're right in the OP needs to post getvar all data before all the steps can be laid our correctly. In short, OP needs the proper CID or SuperCID, and relock bootloader (if unlocked) or S-off to run RUU.
redpoint73 said:
It appears the OP's phone had the full GPE conversion done to it, therefore changing the partitions, and that alone will prevent Sense ROMs for booting. Flashing a ROM in itself will not change the partitions back the Sense partition scheme.
Easiest way to revert is probably RUU. You're right in the OP needs to post getvar all data before all the steps can be laid our correctly. In short, OP needs the proper CID or SuperCID, and relock bootloader (if unlocked) or S-off to run RUU.
Click to expand...
Click to collapse
Did gpe conversion with my m7 and had to flash with zip file of ruu in order to change.
I have tried looking myself to point him in the right direction for m8 zip's but have not had had any joy?
passion8059 said:
Did gpe conversion with my m7 and had to flash with zip file of ruu in order to change.
I have tried looking myself to point him in the right direction for m8 zip's but have not had had any joy?
Click to expand...
Click to collapse
Flashing a zip of the RUU isn't necessary. OP can either flash the official exe file: http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Or the bootable RUU here (no PC required): http://forum.xda-developers.com/att-htc-one-m8/general/att-2-23-502-3-bootable-ruu-pc-required-t2860486
redpoint73 said:
Flashing a zip of the RUU isn't necessary. OP can either flash the official exe file: http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Or the bootable RUU here (no PC required): http://forum.xda-developers.com/att-htc-one-m8/general/att-2-23-502-3-bootable-ruu-pc-required-t2860486
Click to expand...
Click to collapse
But doesn't bootloader need to be changed?
As you said partitions are different and ruu would not like it surely?
passion8059 said:
But doesn't bootloader need to be changed?
As you said partitions are different and ruu would not like it surely?
Click to expand...
Click to collapse
RUU will rewrite all partitions including hboot. I have the advice I did for a reason.
Sent from my HTC One_M8 using XDA Free mobile app
redpoint73 said:
RUU will rewrite all partitions including hboot. I have the advice I did for a reason.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
So all I would have to do is run the bootable ruu to bring my gpe converted m8 back to stock sense? Just want to know for future ref
pclaunch said:
So all I would have to do is run the bootable ruu to bring my gpe converted m8 back to stock sense? Just want to know for future ref
Click to expand...
Click to collapse
Yes.
Keep in mind, if you are s-on, you need to have the proper CID or SuperCID. Plus, you can only run an RUU with equal or greater hboot number than the hboot presently installed on the phone.
S-off should bypass both these issuees (CID and hboot version check).
I've got hboot 1.57, 4.4.4., and the latest CM11 nightly. Unlocked bootloader, S-ON. I'm trying to flash the RUU_M7_UL_L50_SENSE60_MR_Cingular_US_7.23.502.1_Radio_4M.32.3218.06_10.46.1718.01L_release_424933_signed_2 rom update from the HTC website. I keep getting an error 155 that it isn't the right rom image for my phone. I'm assuming I need to relock my bootloader for the update to take? Do I need to go back to full stock? I've googled a ton and cannot find an easy way to relock my bootloader. I'm not sure if it matters, but I no longer have the stock HTC usb cable so i'm using one that came with a dell windows tablet. Thanks for any help.
dihnekis said:
I've got hboot 1.57, 4.4.4., and the latest CM11 nightly. Unlocked bootloader, S-ON. I'm trying to flash the RUU_M7_UL_L50_SENSE60_MR_Cingular_US_7.23.502.1_Radio_4M.32.3218.06_10.46.1718.01L_release_424933_signed_2 rom update from the HTC website. I keep getting an error 155 that it isn't the right rom image for my phone. I'm assuming I need to relock my bootloader for the update to take? Do I need to go back to full stock? I've googled a ton and cannot find an easy way to relock my bootloader. I'm not sure if it matters, but I no longer have the stock HTC usb cable so i'm using one that came with a dell windows tablet. Thanks for any help.
Click to expand...
Click to collapse
S on u need to lock the bootloader . Google adb command to lock bootloader or use a tool that does it for you.
Sent from my HTC One using Tapatalk
grigoriisi said:
S on u need to lock the bootloader . Google adb command to lock bootloader or use a tool that does it for you.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Thanks, i got the bootloader locked. I tried to flash the rom and it got stuck at step 1/6 Sending for over an hour. I'm going to retry after uninstalling htc sync and running in xp compatibility mode. If that doesn't work I'll try extracting the rom.zip and manually flashing it with fastboot.