[Q] Questions about Telus RUU and Kernels - HTC Amaze 4G

This is probably better suited for the development section but I do not have ten posts and feel it's ridiculous for me to have to go make 10 posts to ask my simple question so I'm posting it here. I have a Telus Amaze 4g. I had previously tried flashing it with the PH85IMG.zip that I had obtained through the development section but after relocking the bootloader it would not flash, the verification finished then nothing happened I was just back in the bootloader menus. Because I couldn't get this to flash I've been sketchy about flashing faux's kernel because I want to be able to get the stock Telus kernel back if necessary and I'm not sure how to do it other then that. I'm not sure if I can just extract it from the zip and flash it or not. An RUU for the telus amaze was released recently so I relocked my bootloader and flashed that, it worked great. So I know the RUU works but does an RUU flash the kernel as well. I know it flashes almost everything but I didn't see it say flashing kernel while I watched it install. So my questions are, can I extract the stock kernel from the xip and flash it and does the RUU flash the kernel as well?

Snargaflab said:
This is probably better suited for the development section but I do not have ten posts and feel it's ridiculous for me to have to go make 10 posts to ask my simple question so I'm posting it here. I have a Telus Amaze 4g. I had previously tried flashing it with the PH85IMG.zip that I had obtained through the development section but after relocking the bootloader it would not flash, the verification finished then nothing happened I was just back in the bootloader menus. Because I couldn't get this to flash I've been sketchy about flashing faux's kernel because I want to be able to get the stock Telus kernel back if necessary and I'm not sure how to do it other then that. I'm not sure if I can just extract it from the zip and flash it or not. An RUU for the telus amaze was released recently so I relocked my bootloader and flashed that, it worked great. So I know the RUU works but does an RUU flash the kernel as well. I know it flashes almost everything but I didn't see it say flashing kernel while I watched it install. So my questions are, can I extract the stock kernel from the xip and flash it and does the RUU flash the kernel as well?
Click to expand...
Click to collapse
RUU flashes kernel.

Accophox said:
RUU flashes kernel.
Click to expand...
Click to collapse
Ok, what about flashing the boot.img from the PH85IMG.zip? boot.img is the kernel right? Is it encrpyted or something in some way that I can't flash it that way?

Snargaflab said:
Ok, what about flashing the boot.img from the PH85IMG.zip? boot.img is the kernel right? Is it encrpyted or something in some way that I can't flash it that way?
Click to expand...
Click to collapse
Theoretically, with an unlocked bootloader, it should be as simple as...
fastboot flash boot boot.img
If this doesn't work... then maybe HTC did something to the RUU.

Accophox said:
Theoretically, with an unlocked bootloader, it should be as simple as...
fastboot flash boot boot.img
If this doesn't work... then maybe HTC did something to the RUU.
Click to expand...
Click to collapse
I understand how to do it and that it's theoretically possible, just hoping I could get a 100% answer. The reason I was worried is because the zip won't flash properly through hboot and I have no idea why. I just decided to try it, since I could use the RUU if it doesn't work. This is the result of flashing the boot.img from the zip.
D:\Android>fastboot flash boot boot.img
sending 'boot' (3814 KB)...
OKAY [ 0.842s]
writing 'boot'...
OKAY [ 4.711s]
finished. total time: 5.554s
As you can see it appeared to work, so I guess that answers my question, thanks for the help.

When you flash the RUU it does say flashing boot. I extracted the PH85IMG.zip from the RUU and I used it to flash my phone through hboot just fine so I guess the one in the development section was just corrupt. That link no longer exists (and it wasn't working anyway) so if anyone wants me to upload my PH85IMG then I will, I have crazy fast fibreop internet, just tell me where to upload it. I'd probably have better luck in the dev section but I still don't have ten posts lol, soon. If someone wants to let someone over there know that I've got the confirmed working zip for stock Telus Amaze then it'd be greatly appreciated.

Posting a droobox link
I can relate to the thread count dilemma. Would you mind pm-ing
a link (or whatever is convenient) to that zip?

Just started uploading it to deposit files now. Can I not post that link here?
This is gonna take forever lol. I get 3.7 Megabytes per second upload so I could theoretically upload it in less then 2 minutes but deposit files won't let me upload at over 70kb/s. I'll post as soon as it's finished. Does anyone have a suggestion for a better site to use. I know of a few but they have file size limits that make it impossible without paying.

It's uploaded, what are the rules on posting the link to it? Would it have to be in the development section?

Snargaflab said:
It's uploaded, what are the rules on posting the link to it? Would it have to be in the development section?
Click to expand...
Click to collapse
You still won't be able to add links since you're still under 10 posts, but get 2 more and just create a new thread in the dev section, then we can close this one.

Ah, didn't realize that was how it worked, this is my ninth so I'll just go find something I can comment on in a relevant way lol

Related

My guide (for noobs) on ota firmware to go from stock rooted to full ota

I do not take credit for any of the following, it was all information I have found posted here. Please thank the ops in the threads I link, it is their work that supplied all the information. Thanks.
For all the noobs out there (like me) here is a direct step by step process I used to go from rooted via one click root, to get the new ota, new hboot, and radios.
Thanks to con, andybones, chad, nilsp and everyone else who has answered my questions over the last few days!
I didnt take the ota, I used cons ota rom.. this was my steps for that to stay stock rom but get the ota.
Also, I am running amon ra.
1) download rom from here http://forum.xda-developers.com/showthread.php?t=1467329
2) boot into recovery, flash rom....
here you can go two ways, if you dont want the new baseband, it will flash the ph98img and not do anything, if you want the new radios I will tell you how I did it, then tell you where you need to start if you wont want them. if you dont want the new radios, and are having wifi issues go to step 13 (and be sure to thank andybones for that tutorial hell thank everyone whos threads I have linked to here).
3)perform nandroid back up
4)via adb (thing you used to unlock originally) fastboot oem lock YOU ARE NOW LOCKED.
5)boot into hboot it will flash the ph98img
6) Unlock bootloader (find the email with the unlock.bin code and follow those instructions)
7)Reboot phone
8)connect to pc, charge only usb debugging enabled
9)run one click root
Proceed with this if you get the mainver error ONLY otherwise if having wifi issues, proceed to step 13
10) after rooted follow this post http://forum.xda-developers.com/showthread.php?t=1467099 NOTE, op in the thread supplied his miscnew.img USE IT! (post 29)
11)Read this thread http://forum.xda-developers.com/showthread.php?t=1459347 it will explain how to get the ph98s to work.
11a) do the ph98 file thing to the ph98 img in the amon ra ph98zipto get it to flash in bootloader
12) after amon ra is restored, perform restore nandroid.
If wifi is not working, even if you dont have mainver issues do step 13
13) If having wifi issues as in not working go to this thread http://forum.xda-developers.com/showthread.php?t=1467793 and follow instructions EXACTLY!!!
Now you should be running new radios, hb2.11, the 2.6 kernel etc.
You will have to follow the post in step 11 to get any ph to work from now on.
I AM NOT RESPONSIBLE IF YOU BRICK YOUR PHONE, BURN YOUR HOUSE DOWN OR ABDUCTED BY ALIENS BY FOLLOWING THE ABOVE INSTRUCTIONS.
Thanks for posting this, it should help me. Question: After i do this can i reflash a custom gb rom "like nils p gingersense" and still keep the new radio and other firm ware that came in the ota. Or will it not work?
Tmask32 said:
Thanks for posting this, it should help me. Question: After i do this can i reflash a custom gb rom "like nils p gingersense" and still keep the new radio and other firm ware that came in the ota. Or will it not work?
Click to expand...
Click to collapse
I don't know, you would have to ask someone else about that. I haven't played with custom roms yet.
Sent from my ADR6425LVW using XDA App
remmy5r said:
I don't know, you would have to ask someone else about that. I haven't played with custom roms yet.
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
yes, the firmware will always be there only thing will change is the kernel's and UI depending upon what rom your running.
all of the links in the original post are bad. They all have been trunkated. Use the URL feature of the post (earth with the link on it) to make the URLs work.
con247 said:
all of the links in the original post are bad. They all have been trunkated. Use the URL feature of the post (earth with the link on it) to make the URLs work.
Click to expand...
Click to collapse
Con, links fixed. Thanks for the heads up.

CM10 Install guide?

I've been (at least trying to) patiently wait for Deck to post full install instructions for CM10 but the CM10 op is still bare as bones. Has anyone else posted an install guide or instructions yet?
I'm currently rooted with RegawMod and running MeanRom 2.1 and it's really terribly laggy and frustrating, I can't wait any longer for CM10. Do I need S-off to install CM10 or do I just wipe, flash, and go?
Thanks for any help or links!
If you are on hboot 1.15 or higher you have to fast boot flash the kernel.
Other than that its just like a normal aosp install. Wipe flash rom flash gapps.
Its been my daily for 3 weeks.
Sent from my EVO using Tapatalk 2
You don't need s-off. You will however have to flash the boot IMG separately by using fastboot or the app flash image GUI and a full wipe is definitely required. There is a helpful thread in Q&A called "don't panic" that will answer all your questions
Good luck
Sent from my EVO using xda app-developers app
corcgaigh said:
You don't need s-off. You will however have to flash the boot IMG separately by using fastboot or the app flash image GUI and a full wipe is definitely required. There is a helpful thread in Q&A called "don't panic" that will answer all your questions
Good luck
Click to expand...
Click to collapse
Dont use flash image gui unless you know how to do it manually through fastboot. You are just asking for issues
Instructions:
http://androidforums.com/evo-4g-lte-all-things-root/606748-how-install-kernels-h-boot-1-15-a.html
Rxpert said:
If you are on hboot 1.15 or higher you have to fast boot flash the kernel.
Other than that its just like a normal aosp install. Wipe flash rom flash gapps.
Click to expand...
Click to collapse
I'm on hboot 1.12, so does that mean I can just flash normally?
edit - From what I can tell from reading, hboot 1.12 doesn't have the same restrictions that 1.15+ do, so I think I'm OK but I would like verification.
Thanks for the help everyone.
Yes hboot 1.12 allows for access to the boot partition
Also luuuuucckkyyyyyy...
EdhyMonker said:
I'm on hboot 1.12, so does that mean I can just flash normally?
edit - From what I can tell from reading, hboot 1.12 doesn't have the same restrictions that 1.15+ do, so I think I'm OK but I would like verification.
Thanks for the help everyone.
Click to expand...
Click to collapse
If you are on Hboot 1.12 I'd strongly suggest looking into getting S-OFF. Theres really no reason not to.
Up to you though, its not required
Bit off topic, anyone check to see if you can push a new splash, right now I'm too lazy to start my PC just to fastboot one measly splash
Rxpert said:
If you are on Hboot 1.12 I'd strongly suggest looking into getting S-OFF. Theres really no reason not to.
Up to you though, its not required
Click to expand...
Click to collapse
The S-OFF guide was way over my head so I just let it be. If there's not a real good reason for doing it, and I can still run CM10, then I'd rather not.
It allows you to directly flash new firmware like radios to fix any problems a device might be having. If you have Son and want the latest firmware you have to revert back to stock and accept ota, then unlock reflash recovery and reflash custom ROM or rooted stock, you could also just flash root installer if you want to just root stock
om4 said:
It allows you to directly flash new firmware like radios to fix any problems a device might be having. If you have Son and want the latest firmware you have to revert back to stock and accept ota, then unlock reflash recovery and reflash custom ROM or rooted stock, you could also just flash root installer if you want to just root stock
Click to expand...
Click to collapse
No, S-ON people with 1.12 H-boot can flash radios and firmware from recovery. They can do whatever they please in recovery just like S-OFF. S-OFF users can flash things from bootloader and even change the appearance of their h-boot to read S-ON and **locked** even though they are S-OFF
To the OP, this is the best rooting guide I've seen. It really explains everything step by step. http://androidforums.com/evo-4g-lte...panda-s-htc-dev-ltevo-root-dummies-guide.html Its recommended to have Linux at least bootable, because in the small chance the phone gets bricked... the unbricker program requires linux.
I ran it in windows before the unbricker was available, no issues here
You basically just hook the phone up to it and run the program like you do for most other root programs. All 1-click
Ah yeah forgot to mention that, most everyone is on 1.15 or 1.19 sorry
om4 said:
Ah yeah forgot to mention that, most everyone is on 1.15 or 1.19 sorry
Click to expand...
Click to collapse
Alright, I got S-Off using Lazy Panda and it went better than expected!
Do I need to flash updated firmware / radios separately from CM10, or does CM10 include latest firmware?
Sorry to ask dumb questions, but I do hope this thread will also be a good resource for others like me.
You don't have to flash any firmware updates. There are a few users with issues although they may be related to the ROM update and not necessarily the firmware included. I haven't really checked since I'm s on. If you want to update the radios there's an update zip here somewhere, be sure to read through everything carefully. Radios are more risky then every day flashing
Alright everyone now I need some help!
I flashed CM10 after s-off, was on stocked 1.13 rooted rom.
Now when CM10 boots up I am faced with a phone activation screen. It says something like "you will not be able to place calls or access the mobile network until the device is activated". I am unable to make calls or receive calls or access the internet. I have tried reflashing cm10 and the problem persists.
In the mean time, I will try flashing a nand backup and see where that gets me. I appreciate any and all help, and I have found no posts in the CM10 thread with a similar issue.
Update: I wiped and restored a back-up, MeanRom 2.1. Upon boot, hands-free activation ran and activated the phone and downloaded a PRL update. Everything is working fine now. Not sure if I should try CM10 again or what? Any advice?
EdhyMonker said:
Alright everyone now I need some help!
I flashed CM10 after s-off, was on stocked 1.13 rooted rom.
Now when CM10 boots up I am faced with a phone activation screen. It says something like "you will not be able to place calls or access the mobile network until the device is activated". I am unable to make calls or receive calls or access the internet. I have tried reflashing cm10 and the problem persists.
In the mean time, I will try flashing a nand backup and see where that gets me. I appreciate any and all help, and I have found no posts in the CM10 thread with a similar issue.
Update: I wiped and restored a back-up, MeanRom 2.1. Upon boot, hands-free activation ran and activated the phone and downloaded a PRL update. Everything is working fine now. Not sure if I should try CM10 again or what? Any advice?
Click to expand...
Click to collapse
ive only ever seen this issue with cyanogenmod and the old htc vogues, still great phones for what they were
EdhyMonker said:
Alright, I got S-Off using Lazy Panda and it went better than expected!
Do I need to flash updated firmware / radios separately from CM10, or does CM10 include latest firmware?
Sorry to ask dumb questions, but I do hope this thread will also be a good resource for others like me.
Click to expand...
Click to collapse
Yes, you should be flashing the upgraded firmware. You'll see the full firmware as the very first downloadable link. Flash that
http://themikmik.com/showthread.php...dio-Collection&p=220556&viewfull=1#post220556
Rename the file to "PJ75IMG.zip", place on root of SD card, and boot into HBOOT to flash. Check the md5 to make sure its right. With radios you want to make sure its the correct file.
Welcome to S-OFF my friend
Rxpert said:
Yes, you should be flashing the upgraded firmware. You'll see the full firmware as the very first downloadable link. Flash that
http://themikmik.com/showthread.php...dio-Collection&p=220556&viewfull=1#post220556
Rename the file to "PJ75IMG.zip", place on root of SD card, and boot into HBOOT to flash. Check the md5 to make sure its right. With radios you want to make sure its the correct file.
Welcome to S-OFF my friend
Click to expand...
Click to collapse
Thanks, but I tried this and it says "no image or wrong image" when trying to flash the PJ75IMG.zip file.
Did you type in PJ75IMG.zip or PJ75IMG and kept it a zip file...you should do the 2nd.
joebarkho said:
Did you type in PJ75IMG.zip or PJ75IMG and kept it a zip file...you should do the 2nd.
Click to expand...
Click to collapse
I thought that might've been the issue so I tried it both ways, didn't work either way. I'll take another shot at it tomorrow.

HTC EVO 3D X515m

Hello everybody,
It's a question about fixing a HTC EVO 3D X515m device, here we go:
status
----------
- When power on = HTC's logo with a white background in loop reboots
why
-------
- It has been upgraded automatically by the internet to an ics ROM.
bootloader info
----------------------
- Relocked
- Hboot version 1.53
- S-on
recovery partition info
--------------------------------
- no any image exist.
ADB command
----------------------
- not seeing the device.
Fastboot command
-----------------------------
- seeing the device and able to extract its information, but no ability to flash or write anything.
CID
------
HTC__J15
notes
---------
- not getting any PG86IMG.zip updates or ROMs.
- wire trick didn't work.
- actually I can't brick it in order to unbrick it again.
- I have tried many RUUs, with no luck.
Any little tips to fix its situation will be so appreciated, you know I have been working on the device around 48 hours and now I feel that I have to through it away.
bonbonboi said:
Hello everybody,
It's a question about fixing a HTC EVO 3D X515m device, here we go:
status
----------
- When power on = HTC's logo with a white background in loop reboots
why
-------
- It has been upgraded automatically by the internet to an ics ROM.
bootloader info
----------------------
- Relocked
- Hboot version 1.53
- S-on
recovery partition info
--------------------------------
- no any image exist.
ADB command
----------------------
- not seeing the device.
Fastboot command
-----------------------------
- seeing the device and able to extract its information, but no ability to flash or write anything.
CID
------
HTC__J15
notes
---------
- not getting any PG86IMG.zip updates or ROMs.
- wire trick didn't work.
- actually I can't brick it in order to unbrick it again.
- I have tried many RUUs, with no luck.
Any little tips to fix its situation will be so appreciated, you know I have been working on the device around 48 hours and now I feel that I have to through it away.
Click to expand...
Click to collapse
Wrong section to post in. It should be in Q&A. Please delete your thread and post it in the correct one.
listen to the nazi.. you've posted in the wrong section
meanwhile.. use the htc dev method to unlock then flash a recovery then flash a rom..
or jus download the htc_ara form the stock roms and extract its rom.zip and change its name to pg something then use fastboot to update..
and to the nazi, ure useless and no one will like ur post so get over it.
okay i was wrong to post here, still i do not know how to delete my post, and thanks The Troll I will try htcdev again, even i have tried it, just to be sure i will give it another one..
bonbonboi said:
okay i was wrong to post here, still i do not know how to delete my post, and thanks The Troll I will try htcdev again, even i have tried it, just to be sure i will give it another one..
Click to expand...
Click to collapse
if that doesn't work, htc_ara will.. jus download it and extract the rom..
rename it to pg89img.zip or something..
forgot :/
fastboot oem writecid HTC_001. this way you can flash any RUU.
Also thread reported for moving.
A quick reminder. Questions should be posted in the Q&A section. Remember that.
I moved this one.
for warranty purposes, try and NOT to change ur CID..
okay I have managed to unlock the bootloader by htcdev, so now it's unlocked. changed the CID to HTC__001, tried many ROMs.zip through Hboot but after loading it and checking it, it will not tell me to update or install anything.
i wanna mention that before it get stuck it was update to ICS rom.
you shouldnt have changed ur CID..
switch it back to j15
download this
http://www.filefactory.com/file/c20....00_10.15.9020.06_M_release_220917_signed.exe
run it..
then when u see the setup, press ctrl+alt+del and open the task manager..
then open processes tab.. and right click the setup and open file location.. there u'll see a "rom.zip"
thats the stock arab rom..
rename it to pg89img.zip
or whatever the name is.. *google it man.. i dun really remember the tiny details*
place it in ur memcard
reboot into fastboot and let it flash..
Nooo I want to stay with HTC__001, any zipped rom with that ? you know I am not going to use any RUU stuff, I have no time to just relocked and locked
someone tell me .... when i apply a custom ROM through recovery , should the bootloader be relocked or unlocked ? please reply the time is short..
bonbonboi said:
someone tell me .... when i apply a custom ROM through recovery , should the bootloader be relocked or unlocked ? please reply the time is short..
Click to expand...
Click to collapse
If you're s-on, unlocked. If you're s-off, it doesn't matter.
Read, Search, Read again, ... Then Ask with Tapatalk 2
Coal, I didn't get you, i need to know in simple English that... what it can be done with these cases:
S-ON+Unlocked= ???
S-ON+Locked= ???
S-OFF+Locked= ???
S-OFF+Unlocked= ???
bonbonboi said:
Coal, I didn't get you, i need to know in simple English that... what it can be done with these cases:
S-ON+Unlocked= ???
S-ON+Locked= ???
S-OFF+Locked= ???
S-OFF+Unlocked= ???
Click to expand...
Click to collapse
Sorry if the other post wasn't clear. I was on my phone and answered with brevity.
S-on + Unlocked= Can flash custom ROMs but must flash the kernel separately using fastboot or 4ext smartflash.
S-on + Locked= Can't do squat.
S-off + Locked= Can flash custom ROMs and kernels without any special procedures. Can change hboots.
S-off + Unlocked = See S-off + Locked.
So, if you are s-on, you must be unlocked to flash custom ROMs. If you are s-off, you can flash custom ROMs whether your hboot is locked, unlocked, or relocked.
Great, now things are getting clear in my mind...
As I know when you mention a kernel that's mean the "boot.img" file, correct me if am wrong.
Since we can install a custom ROM by a recovery tool, and flash a kernel with fastboot...
why there is something called firmware and people put that on the sdcard like e.g PGxxIMG.zip then let the hboot find it then flash it.
by the way, what is Tapatalk 2 ??
AFAIK, the boot.img is the kernel. It might be more (I'm not sure exactly), but when someone says flash the kernel separately, that's what they mean.
Tapatalk 2 is a forum browsing app that works on thousands of sites, including this one. For me, it's worth the price.
Read, Search, Read again, ... Then Ask with Tapatalk 2
coal686 said:
AFAIK, the boot.img is the kernel. It might be more (I'm not sure exactly), but when someone says flash the kernel separately, that's what they mean.
Tapatalk 2 is a forum browsing app that works on thousands of sites, including this one. For me, it's worth the price.
Click to expand...
Click to collapse
A word of caution on flashing just the boot.img file.
There are multiple ways to do that (fastboot, 4EXT app, etc.) but as coal suggested there is more to the kernel than that, such as the .ko driver files, and often things like WiFi and 4G don't work if you flash only boot.img unless it is the same kernel as the one aleady in place. 4EXT gives a warning in the app when you do that.
It's safer to flash a kernel from a .zip file if it is available since it will contain the necessary files, or from Flash Image GUI if you have a bootable Android system since that app looks for the additional files required in a ROM .zip.
ramjet73
I see, but what about the firmware file like PGxxIMG.zip and should be updates through Hboot...
Why I am asking like that is I like to know how things works together and how to flash a devices piece-by-piece... more than just find an RUU or any GUI tools.
in my experience, I could tell that any device has the following pieces to care about when flashing it...
1.Hboot : on this level we can talk about its version and whether its locked or marked with s-on or off. and radio version.
2. boot.img : it's a loader (bootstrap) going in the place after hboot, means the hboot will look for it and it contains the kernel as well.
3. after this will handle the control for the actual OS..
so nobody out there understood what i was talking about.

[Q]Installation aborted for Android Revolution HD

Every time I try to install the rom, the installation gets aborted. I'm using 4EXT Recovery.
nulcon said:
Every time I try to install the rom, the installation gets aborted. I'm using 4EXT Recovery.
Click to expand...
Click to collapse
More info? Carrier, ROM you were on before, what did you do before install? Is the file a complete download, no damage, etc? Did you let your device boot properly for a first start up, not much I can say if you just say it aborted? Did you try reading the bible thread? Search button is quite useful as well.
Dark Nightmare said:
More info? Carrier, ROM you were on before, what did you do before install? Is the file a complete download, no damage, etc? Did you let your device boot properly for a first start up, not much I can say if you just say it aborted? Did you try reading the bible thread? Search button is quite useful as well.
Click to expand...
Click to collapse
T-Mobile. Bulletless V2.5. I renamed the rom .zip file to "PH85IMG.zip". I'm pretty sure that the file is a complete download, as I downloaded it a second time. I guess. I did read that thread. I used that search button for a while and I'm still stuck on this. Please help out. Thanks
-nulcon
nulcon said:
T-Mobile. Bulletless V2.5. I renamed the rom .zip file to "PH85IMG.zip". I'm pretty sure that the file is a complete download, as I downloaded it a second time. I guess. I did read that thread. I used that search button for a while and I'm still stuck on this. Please help out. Thanks
-nulcon
Click to expand...
Click to collapse
I'll be honest, I don't really believe you, since if you did you'd see even in the past few threads below this one you'd see you need to be on ICS to use an ICS rom.
Here's what you'll need to do and maybe a few things NOT to do, you'll have to do your own leg work though.
1. Update your device to the latest ICS via hboot using a stock ICS ruu file which can be found in the dev section
2. Re-Unlock your device, reinstall a custom recovery and/or root if you want to, all these can be done using Hasoon's tool, found in the dev section as well.
2. Follow the basic instructions of the rom dev of whichever rom you choose to install
Don'ts
You don't need to rename rom files, do read what the dev is specifying you have to rename, if there is anything to be renamed.
Dark Nightmare said:
I'll be honest, I don't really believe you, since if you did you'd see even in the past few threads below this one you'd see you need to be on ICS to use an ICS rom.
Here's what you'll need to do and maybe a few things NOT to do, you'll have to do your own leg work though.
1. Update your device to the latest ICS via hboot using a stock ICS ruu file which can be found in the dev section
2. Re-Unlock your device, reinstall a custom recovery and/or root if you want to, all these can be done using Hasoon's tool, found in the dev section as well.
2. Follow the basic instructions of the rom dev of whichever rom you choose to install
Don'ts
You don't need to rename rom files, do read what the dev is specifying you have to rename, if there is anything to be renamed.
Click to expand...
Click to collapse
Hi, thanks for responding back. I got stuck at the 1st step where you said get a stock ICS "ruu" file. Is the ruu basically the stock ICS rom?
nulcon said:
Hi, thanks for responding back. I got stuck at the 1st step where you said get a stock ICS "ruu" file. Is the ruu basically the stock ICS rom?
Click to expand...
Click to collapse
Yes, get it from the stock RUU/OTA thread in the dev section, rename it PH85IMG and flash via hboot.
Dark Nightmare said:
Yes, get it from the stock RUU/OTA thread in the dev section, rename it PH85IMG and flash via hboot.
Click to expand...
Click to collapse
Wait so flashing via hboot can work in hasoon2000's HTC Amaze 4G S-OFF kit for this particular problem?
nulcon said:
Wait so flashing via hboot can work in hasoon2000's HTC Amaze 4G S-OFF kit for this particular problem?
Click to expand...
Click to collapse
You don't read much huh?
Dark Nightmare said:
You don't read much huh?
Click to expand...
Click to collapse
Just asking to confirm
nulcon said:
Just asking to confirm
Click to expand...
Click to collapse
Hboot and fastboot aren't the same, a little reading of the bible in your spare time would be cool, we put a lot of work into getting even basic things like what is fastboot and stuff sorted out. :good:

[Q] Help with relocking, unrooting and returning to Stock

For returning purposes, how can i return my phone back to stock? Lets just say i want to go back to a stock rom and i want to install the official ICS sprint update. I no longer wish to have a rooted phone because its been going haywire on me lately (ROMs keep going unstable).
Long story short, i guess im done with rooting this phone and i dont know how do i go about returning to stock conditions. Do i need to download a RUU or are there any stock sprint .zips i can flash via recovery? Dont really what to do with RUUs. I know i can just relock it later
EDIT: im on 2.89 base and hboot 1.5 ON via HTC Unlock
All you have to do is download the latest ruu. Which is the ics 35 s 2.89 file that's found in the development section. Relock your bootloader first. Then rename ruu to PG86IMG in all caps and place it on the root of your sdcard. Power down your phone and boot into bootloader. Your phone should then detect it and ask to update your phone. Hit yes and let your phone finish updating. You'll be back on unrooted stock with stock everything.
Please hit the thank you button if I helped you in anyway. It's free.
Jsparta26 said:
All you have to do is download the latest ruu. Which is the ics 35 s 2.89 file that's found in the development section. Relock your bootloader first. Then rename ruu to PG86IMG in all caps and place it on the root of your sdcard. Power down your phone and boot into bootloader. Your phone should then detect it and ask to update your phone. Hit yes and let your phone finish updating. You'll be back on unrooted stock with stock everything.
Click to expand...
Click to collapse
He said he's S-ON so he won't be able to flash the RUU.zip from the bootloader. It's an addition he made right away because there's no timestamp for an edit on his post.
With S-ON, relock the bootloader (fastboot oem lock) and run the RUU.exe from Windows.
We all make mistakes at times, so please don't be so harsh with others on this forum, especially the new users.
ramjet73
ramjet73 said:
He said he's S-ON so he won't be able to flash the RUU.zip from the bootloader. It's an addition he made right away because there's no timestamp for an edit on his post.
With S-ON, relock the bootloader (fastboot oem lock) and run the RUU.exe from Windows.
We all make mistakes at times, so please don't be so harsh with others on this forum, especially the new users.
ramjet73
Click to expand...
Click to collapse
Thanks alot! i couldnt find a .exe but i found a.zip for 2.17 RUU... so i lock the bootloader then how do i "flash" this zip?
Razpr said:
Thanks alot! i couldnt find a .exe but i found a.zip for 2.17 RUU... so i lock the bootloader then how do i "flash" this zip?
Click to expand...
Click to collapse
Look here: http://forum.xda-developers.com/showthread.php?p=19089387
Imagika FTW... with Tapatalk 2
You can't flash the zip if you are S-ON. Use coal's link to download the RUU.exe.
Sent from my PG86100 using Tapatalk 2
ramjet73 said:
He said he's S-ON so he won't be able to flash the RUU.zip from the bootloader. It's an addition he made right away because there's no timestamp for an edit on his post.
With S-ON, relock the bootloader (fastboot oem lock) and run the RUU.exe from Windows.
We all make mistakes at times, so please don't be so harsh with others on this forum, especially the new users.
ramjet73
Click to expand...
Click to collapse
I don't think I was harsh at all. The reason I gave him that solution is from my own experience. Back when I was on gb unlocked. There were a few times I had to relock and go back to stock gb so I relocked my bootloader and ran the ruu file from my bootloader with success everytime. Honestly if my post sounded harsh it wasn't intentionally. I am certainly not questioning anybodies knowledge at all. You guys have been around longer than I have. This piece of information is new to me because I never had to run ruu.exe from a pc. Im am thankful you came in and shed some light. I was just trying to offer a solution. That's all. But thank you for teaching me something new.
Jsparta26 said:
I don't think I was harsh at all. The reason I gave him that solution is from my own experience. Back when I was on gb unlocked. There were a few times I had to relock and go back to stock gb so I relocked my bootloader and ran the ruu file from my bootloader with success everytime. Honestly if my post sounded harsh it wasn't intentionally. I am certainly not questioning anybodies knowledge at all. You guys have been around longer than I have. This piece of information is new to me because I never had to run ruu.exe from a pc. Im am thankful you came in and shed some light. I was just trying to offer a solution. That's all. But thank you for teaching me something new.
Click to expand...
Click to collapse
Actually, it really depends on the source of the RUU.zip. If it was extracted from the RUU.exe and properly signed by HTC it should work flashed through the bootloader with S-ON, but if it is modified in any way (like removing the bootloader) it will fail with S-ON. The RUU.exe is always safer for S-ON users. There were "RUU.zip" files circulating at the time of the VM leak that had all the firmware removed.
I really didn't mean your answers in this thread, but in this forum in general. As someone else pointed out, we were all new at this at some point, and it's better to not answer if you are concerned about someone asking the same question that's been answered many times before, or give the answer but point out that it could have easily been found with a search.
ramjet73

Categories

Resources