ill try and be as concise as possible, any other questions, just ask...ive been running energyrom for a few days now. i decided yesterday that i was going to flash this phone to stock and return it to tmobile (nothing wrong with the phone itself, just cant get used to it). i used the relocker tool and went into hboot where it said "relocked" and "security warning" underneath (never saw that before). so i figured wtf and flashed the stock 1.43 rom to it. well, after boot, **** wouldnt recognize the internal sd or my external one either.
decided to flash the stock rom again, relocked using htc.dev (adb oem relock) and went back to hboot. no more "security warning". flash the stock rom and go into titanium backup to remove bloat and see under "uninstalled" btips, btips_tmp, com.android.htcprofile, cw, and cwtemp. how? i hadnt uninstalled anything and was coming from a fresh flash of the stock rom. anyways, now im having issues with wifi calling not working right. i figured since i flashed nrgz's modified kernel, maybe that had something to do with it, but wouldnt a complete reinstall of the stock rom overwrite the kernel? wtf am i supposed to do now? ive flashed hundreds of times across various devices and never had issues.
I think you may need stock recovery for a reflash of the stock rom to overwrite the kernel. Then again, I may not know wtf I'm talking about.
marleyfan61 said:
I think you may need stock recovery for a reflash of the stock rom to overwrite the kernel. Then again, I may not know wtf I'm talking about.
Click to expand...
Click to collapse
thanks for the response. anyone else have any ideas or should i give the flashing stock recovery a shot? i always thought flashing the ruu overwrote everything
kernel issues, you need to flash the right kernel, you do not need stock recovery to flash kernel...go and read READ me first section...there's all in one tool use it
marleyfan61 said:
I think you may need stock recovery for a reflash of the stock rom to overwrite the kernel. Then again, I may not know wtf I'm talking about.
Click to expand...
Click to collapse
This is right, i had the same problem with the security warning and it was because i didnt have stock recovery
Sent from my NRGized Amaze...
via xda premium
Related
After installing Gingerth3ory and loving it, my friend then applied the speedtweak and i believe its in an undervolted setting that is causing the phone to powercycle. The phone cant go into recovery to reflash the rom to get rid of the tweak because the P50IMG.zip is still on the SD card, so HBOOT is trying to constantly update that. Is there any way to get rid of the tweak so he can boot up the phone?
Pull the SD card and delete the PG05IMG.zip either with another device or card reader
If you're bootlooping and you have the PG05IMG.zip radio file on your sdcard, the first thing you will need to do is get it off. Use an adapter so you can remove the file using a computer or place the sdcard in another phone and remove it that way. Either way, you need to get that file off to get to recovery to fix your bootloops.
Okay he was just able to get the PC to recognize the sd card and pulled the zip. If he reinstalls the rom will that negate the settings of the speedtweak?
Ch0s3n0n3 said:
Okay he was just able to get the PC to recognize the sd card and pulled the zip. If he reinstalls the rom will that negate the settings of the speedtweak?
Click to expand...
Click to collapse
It would help if we knew what the "speedtweak" you are speaking of actually is. Either way, he can flash the rom then try to boot. If it doesn't boot then boot back into recovery and wipe data/cache. Flashing just the rom will probably work though if they were just clock/voltage related tweaks.
Absolute_Zero said:
It would help if we knew what the "speedtweak" you are speaking of actually is. Either way, he can flash the rom then try to boot. If it doesn't boot then boot back into recovery and wipe data/cache. Flashing just the rom will probably work though if they were just clock/voltage related tweaks.
Click to expand...
Click to collapse
Sorry it was Script Fusion, and yes it was a undervolt and overclock tweak. I had him reflash and it seems all is well. I also told him to delete the Script zip until he reads further and learns about it. I really appreciate your help as I am fluent in Droid X not Thunderbolt lol.
Bad timing (almost a pun)
So far I'm having zero luck getting out of the boot loop. Tried hboot w/ the ROM as PG05IMG.zip in the root; no go. Tried wiping cash/data/dalvik in CWR; no go. Tried reflashing the ROM via CWR; reboots before it can complete the operation. Anything else I can try? I guess there's no way to get to the init.d file to wipe the changes made by speedtweak?
Tried the "Normal" setting in speedtweak and that's what started everything.
ProfEngr said:
So far I'm having zero luck getting out of the boot loop. Tried hboot w/ the ROM as PG05IMG.zip in the root; no go. Tried wiping cash/data/dalvik in CWR; no go. Tried reflashing the ROM via CWR; reboots before it can complete the operation. Anything else I can try? I guess there's no way to get to the init.d file to wipe the changes made by speedtweak?
Tried the "Normal" setting in speedtweak and that's what started everything.
Click to expand...
Click to collapse
bootloader flashing isn't for the rom. It needs to be flashed in CWR as you later tried. At this point, the only thing you should be naming PG05IMG.zip, placing on your sdcard, and flashing is a radio (if you need to upgrade). But even then, you should have a booting rom first (not mandatory but encouraged).
You are able to make it to recovery, wipe data/cache, and flash a rom? At what point does the flash fail and is there an error reason stated? If you're in recovery the only thing that should be "preventing" the rom from flashing is the rom itself. The speedtweak files should already be gone before the rom even starts flashing since at that point /data, /cache, and /system have already been wiped.
You could try manually wiping each of those partitions multiple times (which never made complete sense to me) or download another rom or another copy of the current rom and try flashing it.
I got help from an IRC chat. Reloaded the 'upgrade' PG05IMG from the Tbolt root thread via hboot. That got me back online to where I could reflash.
Just for reference though, it was rebooting itself about 30sec into the ROM flash after the ROM notes/info scrolled on the screen.
ProfEngr said:
I got help from an IRC chat. Reloaded the 'upgrade' PG05IMG from the Tbolt root thread via hboot. That got me back online to where I could reflash.
Just for reference though, it was rebooting itself about 30sec into the ROM flash after the ROM notes/info scrolled on the screen.
Click to expand...
Click to collapse
That is weird. A tweak script that forces you to reflash firmware from the bootloader to fix it? Hmm, I suppose I should look up what this SpeadTweak script actually does for future reference. Either way, glad you got it fixed.
Absolute_Zero said:
That is weird. A tweak script that forces you to reflash firmware from the bootloader to fix it? Hmm, I suppose I should look up what this SpeadTweak script actually does for future reference. Either way, glad you got it fixed.
Click to expand...
Click to collapse
No.. Speedtweak.sh is built into imoseyons kernels and it allows you to control your kernel frequencies and governor. You don't have to install via hboot to remove it, all you need to do is flash a new kernel, even one that has Speedtweak.sh would be fine because you need to activate it manually through terminal.
I'm not sure why the OP was rebooting in recovery, that's what all of the phones that were reported as bricks were doing, but they were also rebooting in hboot which the OP wasn't. Obviously it wasn't a brick, but the Speedtweak script doesn't need to be removed via hboot, and it's just weird that the OP was rebooting in recovery.
Sent from my ThunderBolt using XDA Premium App
joshnichols189 said:
No.. Speedtweak.sh is built into imoseyons kernels and it allows you to control your kernel frequencies and governor. You don't have to install via hboot to remove it, all you need to do is flash a new kernel, even one that has Speedtweak.sh would be fine because you need to activate it manually through terminal.
I'm not sure why the OP was rebooting in recovery, that's what all of the phones that were reported as bricks were doing, but they were also rebooting in hboot which the OP wasn't. Obviously it wasn't a brick, but the Speedtweak script doesn't need to be removed via hboot, and it's just weird that the OP was rebooting in recovery.
Sent from my ThunderBolt using XDA Premium App
Click to expand...
Click to collapse
If I understand your terminology, I need to make a clarification.
The phone was stuck in a loop that would make it as far as the 1st HTC boot screen, buzz, hang, then restart the sequence. I was only able to wipe in CWR. It would reboot shortly after starting a ROM flash. hboot still worked as normal.
I'll look into how to flash just a kernel in case this happens again (HOPE NOT!!!)
For another discussion... After I got things sorted and reflashed the MR2 radio, CWR gives me an error when trying to format /system during Nandroid restore of any of my previous backups.
joshnichols189 said:
No.. Speedtweak.sh is built into imoseyons kernels and it allows you to control your kernel frequencies and governor. You don't have to install via hboot to remove it, all you need to do is flash a new kernel, even one that has Speedtweak.sh would be fine because you need to activate it manually through terminal.
I'm not sure why the OP was rebooting in recovery, that's what all of the phones that were reported as bricks were doing, but they were also rebooting in hboot which the OP wasn't. Obviously it wasn't a brick, but the Speedtweak script doesn't need to be removed via hboot, and it's just weird that the OP was rebooting in recovery.
Sent from my ThunderBolt using XDA Premium App
Click to expand...
Click to collapse
It was my understanding from their posts that they couldn't even flash anything. If it's the kernel itself or even init or bash scripts then flashing the rom clearly would fix that but it does little good if your phone reboots before you can even flash something.
Still not clear on what caused the problems of the two users here but the common denominator was that SpeadTweak script which as I said, someone would need to review to determine what may be causing the problem.
Absolute_Zero said:
It was my understanding from their posts that they couldn't even flash anything. If it's the kernel itself or even init or bash scripts then flashing the rom clearly would fix that but it does little good if your phone reboots before you can even flash something.
Still not clear on what caused the problems of the two users here but the common denominator was that SpeadTweak script which as I said, someone would need to review to determine what may be causing the problem.
Click to expand...
Click to collapse
I'm by no means saying you're wrong or anything, I was just letting you know what the speedtweak.sh script was since you had mentioned you weren't completely sure. I'm also unsure as to what was amiss with their phones, I just noted that the people who had bricked their phones (via one way or another), were rebooting in recovery, and that's the only time I had heard of rebooting in recovery. Obviously his hboot was fine, it's just very strange that recovery was rebooting because from my understanding recovery uses a completely different kernel than the main ROM.
Nice(?) to know I have a few people scratching their heads over this. Probably won't work, but I'll try to keep out of trouble on this until someone posts what's up.
That sounds like the boot loop issue that people were having before the MR2 radio came out, doesn't it?
loonatik78 said:
That sounds like the boot loop issue that people were having before the MR2 radio came out, doesn't it?
Click to expand...
Click to collapse
If don't know what issue you mean, there was a bricking issue but this isn't a brick
Sent from my Transformer TF101 using XDA Premium App
joshnichols189 said:
If don't know what issue you mean, there was a bricking issue but this isn't a brick
Sent from my Transformer TF101 using XDA Premium App
Click to expand...
Click to collapse
What they were calling a brick really wasn't much of a brick by definition A) because all it did was boot loop, and B) it was recoverable.
I unlocked the bootloader and rooted it okay... then I flashed a ROM, that also worked fine. I tried to flash a kernel and now it just gets stuck on the HTC screen. I tried restoring my back up, still the same issue. Tried reflashing the ROM, same issue. Not sure how to get it back to normal at this point.
It sounds like the kernel you flashed is either a 2.3.3 kernel that doesn't work on 2.3.4, or it was a bad flash. You should be able to fix this by holding volume down when booting up (opens HBOOT) then choose Recovery and from the recovery you can then either enable USB Mass Storage device and transfer a stock kernel over USB to your SD card then flash the stock kernel, or if you already have a stock kernel on your SD card, you can just select it from the install from zip menu and flash.
This Kernel should work fine (it's stock with CIQ spyware removed):
http://forum.xda-developers.com/showthread.php?t=1224659
and after I flash this kernel it should be back to normal.... or should I try to flash a ROM all over again as well? As long as it can definitely be fixed then that's quite alright.... this phone compared to the Epic (which I came from) seems like it's much less fail safe to me.
Coriolis3ffect said:
and after I flash this kernel it should be back to normal.... or should I try to flash a ROM all over again as well? As long as it can definitely be fixed then that's quite alright.... this phone compared to the Epic (which I came from) seems like it's much less fail safe to me.
Click to expand...
Click to collapse
ROMs usually have kernels. You could just wipe Dalvick cache and cache and flash your original rom (which has it's original kernel). and that should work.
There's a sea of roms. You could try posting on a rom's thread whether a particular kernel is compatible. Just follow the spin of things. Saves from just going round in circles.
Coriolis3ffect said:
and after I flash this kernel it should be back to normal.... or should I try to flash a ROM all over again as well? As long as it can definitely be fixed then that's quite alright.... this phone compared to the Epic (which I came from) seems like it's much less fail safe to me.
Click to expand...
Click to collapse
Here's a scenario: If you installed a rooted stock 2.3.4 rom then decided to install Silverneedle kernel, your phone will get stuck in this boot-loop because the silverneedle kernel is not compatible with 2.3.4 yet. So by flashing a stock kernel over what is already on there, it should fix the problem. Before you flash the stock kernel clear cache and dalvik. After that flash the kernel and reboot the phone. Chances are it will boot normally. I doubt you will have to reflash a ROM to fix this.
Just cleared the dalvik and the cache, reflashed the ROM hoping to start completely fresh and its still getting stuck...
Coriolis3ffect said:
Just cleared the dalvik and the cache, reflashed the ROM hoping to start completely fresh and its still getting stuck...
Click to expand...
Click to collapse
Then flash a stock kernel. I have had the same problem before. I flashed a ROM, installed a kernel and stuck at HTC boot screen. The fix is to either install a stock kernel through bootloader or flash another ROM in recovery. If you want the best chance of it working the first time, then flash the stock rooted 2.3.4 ROM by xhausx. If you want to try other ROMs and kernels, make sure that your ROM and kernel are compatible. Also use the synergy wipe zip file before flashing to make sure everything is formatted properly. Also, did you flash the extra firmwares that came with the 2.3.4 update? If not, make sure you flash those along with the new radio that just came out.
Sent from my PG86100 using Tapatalk
Take it you didn't do a nandroid before flashing?
Sent from my PG86100 using xda premium
Tried to get my nandroid and it still got stuck..
Perhaps I should've also mentioned that my bootloader still says S-ON and I unlocked it using the HTC unlock method.
sn0b0ard said:
Then flash a stock kernel. I have had the same problem before. I flashed a ROM, installed a kernel and stuck at HTC boot screen. The fix is to either install a stock kernel through bootloader or flash another ROM in recovery. If you want the best chance of it working the first time, then flash the stock rooted 2.3.4 ROM by xhausx. If you want to try other ROMs and kernels, make sure that your ROM and kernel are compatible. Also use the synergy wipe zip file before flashing to make sure everything is formatted properly. Also, did you flash the extra firmwares that came with the 2.3.4 update? If not, make sure you flash those along with the new radio that just came out.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Not sure about any extra firmwares actually.... currently going to try flashing xhaus' ROM and hope that works...
Flashed the superwipe before flashing the ROM, then flashed the ROM... it went to the HTC screen for a second then just vibrated and then turned black.
When I go into the bootloader when it is loading up the images.... it kept saying "No Image!" for all of them. I'm not having any luck with this at all.
Coriolis3ffect said:
When I go into the bootloader when it is loading up the images.... it kept saying "No Image!" for all of them. I'm not having any luck with this at all.
Click to expand...
Click to collapse
Do you have it named exactly PG86IMG.ZIP?
Sent from my PG86100 using xda premium
Okay... you mentioned something about firmwares to flash... which ones are they?
I'm kinda lost at this point because I'm not sure about the specific order in which you are supposed to do things.
Which version of hboot do you have?
Sent from my PG86100 using xda premium
1.50.000 or whatever
Just follow this guide easy. Easy step by step.
http://forum.xda-developers.com/showthread.php?t=1231249
jayharper08 said:
Just follow this guide easy. Easy step by step.
http://forum.xda-developers.com/showthread.php?t=1231249
Click to expand...
Click to collapse
+1 on this. RUU method should be bullet proof
Coriolis3ffect said:
Okay... you mentioned something about firmwares to flash... which ones are they?
I'm kinda lost at this point because I'm not sure about the specific order in which you are supposed to do things.
Click to expand...
Click to collapse
It's in the post that xhausx made for the stock rooted 2.08.651.2 ROM.
URL: http://forum.xda-developers.com/showthread.php?t=1223979
List of new firmwares for the 2.08.651.2 update:
(If you do the RUU method, you should have all the firmwares installed automatically btw...)
Radio & PRI Updates Radio 0.97.10.0808 PRI 1.24_003
PG86IMG_radio_pri.zip (MD5: E28414AAC6F91CE9D7B3615B2999AD3A)
RPM Possible fix for Black SOD
PG86IMG_rpm.zip (MD5: DE69396C8922FAD3AC82E5F836EE95FB)
SBL Secure Bootloader?
PG86IMG_sbl.zip (MD5: 5604349AD611241CF1AC152FD3B0DE45)
TZ Trusted Zone - Not sure of it's purpose
PG86IMG_tz.zip (MD5: 75749FBCCE1331A5A85D2A154E15B276)
PG2F2_SPCUSTOM - No idea what it is
PG86IMG_pg2f2_spcustom.zip (MD5: 7A7DE8659A0771919A14B0C299CA18CC)
Click to expand...
Click to collapse
The link posted is for the GSM Evo 3D... will it work on CDMA?
I'm looking for something I can flash through recovery, not the ruu that you have to change to pmg.zip whatever. I've tried doing this and i can't seem to ever get it to work.
When you renamed the zip are you positive you renamed it to just .zip and not .zip.zip? So many people have a problem with this, as windows will not show the file type and they add .zip to the end. In reality the file was already named .zip at the end to begin with.
That being said there are some pretty clean stock-ish ROMS you can flash. Most just have been cleaned up a bit and a few minor tweaks added. I know lots of people like Fresh as his ROM is a cleaned up Stock type ROM.
If I remember in the morning, I'll link to something for you. Go back several pages in the cdma dev section if you're on CDMA. There's a thread for it.
Sent from my PG86100 using XDA App
Yeah I'm pretty sure I've never done the .zip.zip thing. I have a Mac and I've changed it with Astro and its never worked. Is there something I'm missing?
I always go into recovery, wipe everything, and then boot back into hboot, wait for the pmg.zip to load, it says it was successful, and then when I reboot it gets stuck at the HTC screen. I have to pull the battery and go back into recovery to flash something.
did you not make a stock nandroid?
maybe these
http://forum.ppcgeeks.com/htc-evo-3...ck-rooted-htc-evo-3d-shooter-odex-deodex.html
Mr.Esp said:
maybe these
http://forum.ppcgeeks.com/htc-evo-3...ck-rooted-htc-evo-3d-shooter-odex-deodex.html
Click to expand...
Click to collapse
Thanks that's perfect!
z50king said:
did you not make a stock nandroid?
Click to expand...
Click to collapse
I did.... but I wanted to try starting from scratch again.
go to scottsroms.com and he has all the stock roms like the ruu and zip.
I started over a week ago and I had to relock phone then run the ruu and all went well. I then rerooted to a stock rooted rom. Remember you have to relock before running the .zip stock rom.
i have my unlock code stored on my cpu so all i had to do is half the steps on HTC DEV. There is a walk thru on here somewhere to walk you thru unrooting the htc way.
Do we have a purely stock kernal around? I didn't see one.
Sent from my HTC_Amaze_4G using XDA App
jjlean said:
Do we have a purely stock kernal around? I didn't see one.
Sent from my HTC_Amaze_4G using XDA App
Click to expand...
Click to collapse
beastmod and quiksense have stock kernels.
If I go to those and then revert back to rooted stock through cwm will it put back my original kernal. Yes right?
Sent from my HTC_Amaze_4G using XDA App
jjlean said:
If I go to those and then revert back to rooted stock through cwm will it put back my original kernal. Yes right?
Sent from my HTC_Amaze_4G using XDA App
Click to expand...
Click to collapse
the only custom kernel we have for the amaze is faux's kernel. all the rest are stock kernels.
Ok cool. Thanks.
Sent from my HTC_Amaze_4G using XDA App
Doing a restore of one of my backups through cwm will restore the kernal too?
jjlean said:
Doing a restore of one of my backups through cwm will restore the kernal too?
Click to expand...
Click to collapse
Only if your phone was shipped with S-OFF.
So... probably not.
Before I unlocked and rooted, I did an OTA to 1.3, has no Idea at the time. I then unlocked and rooted and was basically on everything stock, with just a different launcher and widgets. Then I flashed Faux's kernel and worked fine. I tried to go back to stock kernel, boot.img as provided by xboarder, bluetooth and wifi stopped working and phone became unstable. I cannot downgrade to any older rom either, when I relock, it gives me a security warning and gets stuck starting in fastboot everytime. As you know I tried scratched my phone screen and am trying to get a replacement. Went to the t-mobile store to exchange and they told me I needed to go back to stock and relock the bootloader which is impossible at this point. I guess I'm stuck at this point with the kernel and this rom.
I am having trouble making the proper clock speed stick with faux's kernel and fauxclock app. I want a clock speed of about 1.5 and prefer not to undervolt too much. Everything sticks except the clock speed, am I doing something wrong. in fauxclock I did click on the button "set on boot" and still nothing...The screen off clock sticks but not the awake clock...I am on ondemand governor does this have something to do with it, sorry I am not very familiar with kernels as I did not play around with them too much before this.
Any help would be appreciated.
seansk said:
Before I unlocked and rooted, I did an OTA to 1.3, has no Idea at the time. I then unlocked and rooted and was basically on everything stock, with just a different launcher and widgets. Then I flashed Faux's kernel and worked fine. I tried to go back to stock kernel, boot.img as provided by xboarder, bluetooth and wifi stopped working and phone became unstable. I cannot downgrade to any older rom either, when I relock, it gives me a security warning and gets stuck starting in fastboot everytime. As you know I tried scratched my phone screen and am trying to get a replacement. Went to the t-mobile store to exchange and they told me I needed to go back to stock and relock the bootloader which is impossible at this point. I guess I'm stuck at this point with the kernel and this rom.
I am having trouble making the proper clock speed stick with faux's kernel and fauxclock app. I want a clock speed of about 1.5 and prefer not to undervolt too much. Everything sticks except the clock speed, am I doing something wrong. in fauxclock I did click on the button "set on boot" and still nothing...The screen off clock sticks but not the awake clock...I am on ondemand governor does this have something to do with it, sorry I am not very familiar with kernels as I did not play around with them too much before this.
Any help would be appreciated.
Click to expand...
Click to collapse
Just use fastboot to flash your roms boot.img file.
Assuming you're using one of xboarders roms like 3.0.0 then use that boot.img file.
With your phone is bootloader mode
fastboot flash boot boot.img and it should push everything over and update your kernel.
Then reboot to recovery and try reflashing the rom. That should do it.
Binary100100 said:
Just use fastboot to flash your roms boot.img file.
Assuming you're using one of xboarders roms like 3.0.0 then use that boot.img file.
With your phone is bootloader mode
fastboot flash boot boot.img and it should push everything over and update your kernel.
Then reboot to recovery and try reflashing the rom. That should do it.
Click to expand...
Click to collapse
1. Ya, I flashed faux's, that's what I can use at the moment only...I flashed back to stock kernel from the original 1.3 and lost bluetooth and wifi.. (not a biggie since I won't be using the stock anyways but still a problem if anyone ever decides to go back to complete stock
2. my main problem clock frequency will not stick (want to underclock back to 1.5) even with enabling set on boot. I use fauxclock's app. perhpas I should contact him about his one....thanks.
seansk said:
1. Ya, I flashed faux's, that's what I can use at the moment only...I flashed back to stock kernel from the original 1.3 and lost bluetooth and wifi.. (not a biggie since I won't be using the stock anyways but still a problem if anyone ever decides to go back to complete stock
2. my main problem clock frequency will not stick (want to underclock back to 1.5) even with enabling set on boot. I use fauxclock's app. perhpas I should contact him about his one....thanks.
Click to expand...
Click to collapse
Don't worry about making it stick. I don't even use any of the apps. Just use the kernel as it is.
Binary100100 said:
Don't worry about making it stick. I don't even use any of the apps. Just use the kernel as it is.
Click to expand...
Click to collapse
yea ok!!! guess a little speed won't hurt, atleast I undervolted, just concerned about battery life!!! don't like carrying battery life around!!! pain in the butt to get my hard case off and replace battery...thanks...
P.S. what kind of battery life you get with this kernel? better same or worse than stock?
cant get back to stock
Hey guys I know i sound like a noob but I am having an issue getting my amaze back to stock. I originally flashed it when it was just out and all that thread seems to have disappeared. I got the all in one tool kit and got the recovery image on there but every time I try to flash the original tmo usa rom it says it cannot open the zip file. I have tried a few diff zip files that i have even for other roms to see whats going on and it cant open any of the zip files. Need to get this back to tmo as I need to send it back in from my warranty exchange. Any help or advice would be great. Been flashing phones since the old mda was out and this is the first time i have had any issues getting it back to stock. Please help me!! When i use the recovery image provided by the tool kit it never shows me the option to flash a zip file just gives me an install option
nightfall987 said:
Hey guys I know i sound like a noob but I am having an issue getting my amaze back to stock. I originally flashed it when it was just out and all that thread seems to have disappeared. I got the all in one tool kit and got the recovery image on there but every time I try to flash the original tmo usa rom it says it cannot open the zip file. I have tried a few diff zip files that i have even for other roms to see whats going on and it cant open any of the zip files. Need to get this back to tmo as I need to send it back in from my warranty exchange. Any help or advice would be great. Been flashing phones since the old mda was out and this is the first time i have had any issues getting it back to stock. Please help me!! When i use the recovery image provided by the tool kit it never shows me the option to flash a zip file just gives me an install option
Click to expand...
Click to collapse
Give me a minute and ill edit this post with what to do...
ok. Tmobile ruu is here, its in the third post http://www.android-dev.us/showthread...ver-Error-Fix! but its a torrent so u will need a torrent client such as utorrent to download it. Make sure u name the ph85img.zip and put it on the root of your external sd card. next relock your bootloader, i believe you can use hasoons toolkit to relock. MAKE SURE U PUT THE PH85IMG.zip ON YOUR SD CARD BEFORE RELOCKING. after you relock, boot your phone into bootloader by holding down power+volume down. when it boots into bootloader it will ask if you want to install update, select yes and it will do the rest from there.
Sent from my NRGized Amaze...
via xda premium
This is embarrassing but I think I might have just bricked my phone. I'm hoping that there is a work around. Please let me know if you need more info to possibly help me.
I was running:
1. SIM Unlocked/Rooted T-Mobile Amaze 4G with 1.43.531.3 Radio
2. BulletProof 2.41 Rom
3. Faux123 Kernal v.0.0.8 [Jan 22]
4. Have Clockwork Recovery Installed
I've been dealing with constant reboots since I bought the phone new. I saw that someone posted in the Energy Rom thread that when they installed his Rom that the reboots went away. So I decided to try his.
I then:
1. Grabbed the Stock Kernal Flasher and tried to flash back to the stock kernal using Xboarders Easy Flasher. Everything seemed to go fine.
2. Phone rebooted and Its just stuck at the HTC Logo.
Any options for me? I did try to restore from my last ROM backup using CWM (which I figured was futile) but that didn't change anything.
Thanks for your help on this. I love this phone but I just couldn't keep dealing with the constant reboots. Now I'm really hosed
Reflash the kernel again...maybe it didn't write everything.
Sent by accident from my Amaze using Tapatalk
Double0EK said:
Reflash the kernel again...maybe it didn't write everything.
Sent by accident from my Amaze using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply,
I used Windows to flash the phone's kernal. It won't recognize the device since its stuck at the logo.
If there is a way to flash the kernal in Recovery (I'm still S-On with unlocked bootloader) please let me know and I'll try it that way..
Stephen
dnslammers said:
Thanks for the reply,
I used Windows to flash the phone's kernal. It won't recognize the device since its stuck at the logo.
If there is a way to flash the kernal in Recovery (I'm still S-On with unlocked bootloader) please let me know and I'll try it that way..
Stephen
Click to expand...
Click to collapse
i think the problem is using the stock kernel.
take out the battery, use the vol down+power buttons to boot into hboot, then boot into fastboot, flash the kernel appropriate to the rom your using, dont just use stock, and then reflash your rom. always remember to do a full wipe
alx294 said:
i think the problem is using the stock kernel.
take out the battery, use the vol down+power buttons to boot into hboot, then boot into fastboot, flash the kernel appropriate to the rom your using, dont just use stock, and then reflash your rom. always remember to do a full wipe
Click to expand...
Click to collapse
Thanks for your suggestion. Before I saw your reply, I decided to flash the Energy Rom since it had the Stock kernal built into it. I fortunately already had the rom on my SD card so I went into Recovery and flash that rom.
FORTUNATELY, the phone rebooted successfully after rom flash to the new rom. My phone is still using Faux123's kernal so the Energy rom didn't flash the stock kernal after all. But my phone is working again!!!
Thanks for everyone's help. I guess I'll just leave the Faux123 kernal on it and be satisfied with that with the Energy rom. Hopefully the constant reboots will go away.
Stephen
dnslammers said:
My phone is still using Faux123's kernal so the Energy rom didn't flash the stock kernal after all.
Click to expand...
Click to collapse
Thanks to S-ON the kernel will not flash when you flash a rom. You have to flash the kernel separately using the kernel flash utility.
I'm running the Energy rom using the stock kernel from his thread and am loving it. Battery life is great. I've heard that battery life is not so good with faux.
No worries needed... glad you figured it out. The good news though about having S=on is that it's virtually impossible to brick. I'm pretty sure I've read posts from members saying good luck trying to brick it.
I'm sure if you edit the right code in the build.prop, you might be able to brick it, but even then you should still be able to boot into recovery.
Sent from my HTC_Amaze_4G using xda premium