Related
Hello everyone. The other day i used revolutionary to Perma-root my evo 3d. Everything was fine, till my text messages were not sending. So i took out the battery and popped it back in, and all i got was the HTC logo, then a dimmed black screen. Yes i can get into hboot, but i have clockworkmod recovery. I seem to be having a difficult time flashing the official sprint evo 3d rom. Any help is appreciated.
Download the pg86100.zip to revert back to stock in the dev section then go into hboot and let it update and you will start back at the stock ROM
Sent from my PG86100 using XDA App
xSpAzzZAttAcK said:
Hello everyone. The other day i used revolutionary to Perma-root my evo 3d. Everything was fine, till my text messages were not sending. So i took out the battery and popped it back in, and all i got was the HTC logo, then a dimmed black screen. Yes i can get into hboot, but i have clockworkmod recovery. I seem to be having a difficult time flashing the official sprint evo 3d rom. Any help is appreciated.
Click to expand...
Click to collapse
try hboot flashing twrp recovery. then if you can boot up update your prl and profile, also make a phone call to see if you got that error 16 thing. Also, did you by chance try to replace your bootanim? If you did, and something like wrong permissions were set, it would still be booting with a black screen, maybe try leaving it alone while it's booting for a bit?
I did the twrp recovery, but i still get the dim black screen. after the dim black screen it goes black for a few seconds, then goes to the HTC logo again. I didnt try to change anything either...
nuggyunlimited said:
Download the pg86100.zip to revert back to stock in the dev section then go into hboot and let it update and you will start back at the stock ROM
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Above is your best solution. From there you can decide to either root again or wait a bit longer. But that should fix the issue and keep you from a boot loop of just the HTC screen.
Well thats where you are wrong. I am still in the boot loop after doing the stock HTC EVO 3d flash.
So the bootloader scanned and flashed the PG86IMG file and you are still showing just the HTC screen?
Did you follow the directions here http://forum.xda-developers.com/showthread.php?t=1194053
Hi where exactly do the adb and fastboot files go when you start to run commands?
Well no i still get the boot loop. guess i have a bricked phone...
xSpAzzZAttAcK said:
Well no i still get the boot loop. guess i have a bricked phone...
Click to expand...
Click to collapse
A brick is when the phone is completely unresponsive and won't boot or give you a charging led. If you can get to hboot you're not bricked. I would do a factory wipe from hboot menu (choose clear storage), and then either run an RUU with your phone in fastboot usb mode, or use a PG86IMG.zip
of an RUU to flash back to stock. That should hopefully fix the loops.
Sent from my PG86100 using XDA App
**** YES! I used the RUU.exe from sprint and now my phone works.
k2buckley said:
A brick is when the phone is completely unresponsive and won't boot or give you a charging led. If you can get to hboot you're not bricked. I would do a factory wipe from hboot menu (choose clear storage), and then either run an RUU with your phone in fastboot usb mode, or use a PG86IMG.zip
of an RUU to flash back to stock. That should hopefully fix the loops.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
From past experiences like this, wipe, flash the bare stock rooted ROM in the development section. Do this in recovery mode. Before wiping you could try just flashing the bare Rom over. That usually worked for me.
Sent From My HTC Evo 3D Using Tapatalk On The Now Network From Sprint!
xSpAzzZAttAcK said:
**** YES! I used the RUU.exe from sprint and now my phone works.
Click to expand...
Click to collapse
Sorry, was a min too late. Glad it works again!
Sent From My HTC Evo 3D Using Tapatalk On The Now Network From Sprint!
xSpAzzZAttAcK said:
**** YES! I used the RUU.exe from sprint and now my phone works.
Click to expand...
Click to collapse
Sweet, glad you got it booting. Now that you've ran the RUU, you'll probably need to run Revolutionary again and then flash TWRP recovery. You should be good to go then. I think your hboot will still be S-off after the RUU, but from reports of other people it acts like it's still S-on and won't let you flash anything, so running Revolutionary again is necessary.
Well i cant use revolutionary...
My device is not supported?
And now i cant make calls or text messages, i get error 16.
any help?
xSpAzzZAttAcK said:
Well i cant use revolutionary...
My device is not supported?
And now i cant make calls or text messages, i get error 16.
any help?
Click to expand...
Click to collapse
Call Sprint. . they can fix it. . .it's actually a common problem after the root. Try to make a call. . .you will get the error message. . .you should hang on the line for a few minutes and it will direct you to sprint. They will call you on another line. . that's not your phone, and have you power the phone off. . .they will wait a few minutes then tell you to turn it on and make a test call. . .they may have you go thru a few things, but I didn't. . .and it will work.
http://forum.xda-developers.com/showthread.php?t=1194460 this forum should answer the question
Help!
I feel like such a freakin noob. My EVO3D is not quite bricked but I think i broke my recovery img AND my ROM. All I can do is turn on Hboot. Tried the stock Sprint RUU to go back to stock and i keep getting an error message everytime it tries to update the ROM image. Have no idea what to do now without being able to go into recovery. Suggestions?
My phone is doing the exact same thing, cept running the ruu.exe didn't fix it. Anyone else have some more ideas?
My original thread http://forum.xda-developers.com/showthread.php?t=1281565
Hello,
I have an unlocked EVO 3D with HBOOT 1.5 S-on.
I flashed the phone and replaced InfectedRom with Warm Two Point Three. After installing new rom and reseting, phone is now stuck on HTC startup screen.
Please help!!! I appreciate and welcome all feedback. Thank you
kongfooey said:
Hello,
I have an unlocked EVO 3D with HBOOT 1.5 S-on.
I flashed the phone and replaced InfectedRom with Warm Two Point Three. After installing new rom and reseting, phone is now stuck on HTC startup screen.
Please help!!! I appreciate and welcome all feedback. Thank you
Click to expand...
Click to collapse
Did you wipe all the way? Also what is your software 2.17 or 2.08 ? Did you fastboot boot recovery.img when you flashed?
kongfooey said:
Hello,
I have an unlocked EVO 3D with HBOOT 1.5 S-on.
I flashed the phone and replaced InfectedRom with Warm Two Point Three. After installing new rom and reseting, phone is now stuck on HTC startup screen.
Please help!!! I appreciate and welcome all feedback. Thank you
Click to expand...
Click to collapse
You need to flash boot.img/kernel using fastboot or Flash image GUI or else you will face issues if the ROM uses kernel other than your current one.
This is the limitation of HTC unlock method (S-ON)
mnomaanw said:
You need to flash boot.img/kernel using fastboot or Flash image GUI or else you will face issues if the ROM uses kernel other than your current one.
This is the limitation of HTC unlock method (S-ON)
Click to expand...
Click to collapse
Thank you!
I flashed the boot.img using fastboot as you suggested. Now the phone is stuck in an endless loop between powering off and the HTC startup logo.
It appears that I am getting closer to fixing the problem but I am still stuck. Can you help further please?
Thanks again!
mnomaanw said:
You need to flash boot.img/kernel using fastboot or Flash image GUI or else you will face issues if the ROM uses kernel other than your current one.
This is the limitation of HTC unlock method (S-ON)
Click to expand...
Click to collapse
Thanks for your reply.
I did wipe all the way. How do I tell whether I have 2.08 or 2.17. if the phone not able to start up?
I flashed boot.img using fastboot. I just realized that the bootloader when doing and Hboot tries to load the image indicates no image or wrong image.
I am either missing a step or did something wrong.
Please help!
did you make a backup of Infected before you flashed?
When you say you installed Warm did you install and actually get it fully booted and set up your home screens and all that and it only stuck on the first reboot after? or was it right after you flashed warm?
Really if you made a backup of infected or what you were running before you should be able to restore that via recovery then boot up normal. Then use FlashImageGUI to flash the kernel needed for Warm, then reboot into recovery mode and flash the other portion of the Rom from the custom recovery.
Unfortunately, I did not back up Infected or other previous roms. I didn't know that I should, I only backed up my apps using Titanium. I now know better.
Still stuck in loop mode. I have been searching the forums for some possible solutions but so far nothing has worked.
I am up the creek without a paddle...
kongfooey said:
I used Titanium Backup to back up apps etc. is that the same as backing up the rom (Infected)?
If I had the backup how do I recover using recovery? I have been reading other posts in the forum and have tried some of the suggestions. I wiped the data and cache.
I am up the creek without a paddle...
Click to expand...
Click to collapse
na TiBackup isn't the same as backing up the Rom itself.
Full backups are done from within the custom recovery...
the boot.img you pushed via fastboot earlier. where did you get it from?
Silly me... I realized that Titanium backup was not the correct backup after I posted.
I took the image from the Warm zip file. I initially thought the problem was fixed until I realized that the phone is in an endless loop...
Still looping
kongfooey said:
Silly me... I realized that Titanium backup was not the correct backup after I posted.
I took the image from the Warm zip file. I initially thought the problem was fixed until I realized that the phone is in an endless loop...
Still looping
Click to expand...
Click to collapse
well to be honest I would just go back and start form scratch at this point since pushing the kernel via fastboot somehow didn't take for you nor did clearing cache's after the fact.
after pushing the kernel via fastboot, have you tried doing that again, and then going into recovery and flashing the rom again? If that doesn't work you might as well just go back to stock and push stock kernel flash stock rooted OTA, boot up, and use FlashImageGUI to push the Warm kernel then go back to flashing the Warm rom in recovery...
really before pushing the stock kernel if you wanna test to see if your initial push of Warm kernel even took fully just fully wipe data and try flashing infected again in recovery. If it boots fine then you know your fastboot push didn't take before to begin with...
Edit:
before i even really get more into this. does Warm even use another kernel beside the stock one? If they dont then all of this could of resulted from a bad download of the rom itself being flashed...
Sgt. Slaughter, I salute you...
I played around with your suggestions. Got it working... I flashed a different boot.img and it solved the problem. I may have gotten a bad Warm rom...
Thanks again!!!
Note: if you took/installed the latest update (2.17.651.5) you won't be able to use roms based off earlier firmware/kernels (ie 2.08.651.2 or 651.3) b/c of kernel differences (I think I've read that somewhere).
I believe Warmtwopointthree and Infected are not using the latest base/kernel.
Edit: saw you posted right before me. So what kernel/boot.img did you use?
kongfooey said:
Sgt. Slaughter, I salute you...
I played around with your suggestions. Got it working... I flashed a different boot.img and it solved the problem. I may have gotten a bad Warm rom...
Thanks again!!!
Click to expand...
Click to collapse
Nice good to hear. Fact you had your phone even semi-booting makes solving anything wrong with it usually trial and error and ends up not being so bad to fix...
I used boot.img from OTXE Titan HD ODEXed New Beats!
I need to educate myself a bit more about the differences between kernel and .imgs etc...
Thanks for your response. I greatly appreciate!!
I'm having a very similar issue, I rooted my Evo using Revolutionary and installed CW Recovery and everything was fine so I tried installing ZR3D and part way through the install, my phone turned off and now it wont get past the HTC boot screen. I went into CW Recovery but nothing is working, no matter what option I choose [even Turn off phone or reboot] it gives me the CW logo but nothing happens.
I have HBOOT 1.49.1107 with S-Off
Try reflashing your recovery threw hboot.
#Root-Hack_Mod*Always\
StoneCold448 said:
I'm having a very similar issue, I rooted my Evo using Revolutionary and installed CW Recovery and everything was fine so I tried installing ZR3D and part way through the install, my phone turned off and now it wont get past the HTC boot screen. I went into CW Recovery but nothing is working, no matter what option I choose [even Turn off phone or reboot] it gives me the CW logo but nothing happens.
I have HBOOT 1.49.1107 with S-Off
Click to expand...
Click to collapse
Can you boot into Fast boot? If so, try connecting your phone to a computer and flashing a recovery through there. Then try to install the ROM.
Sent from my PG86100 using Tapatalk 2 Beta-6
coal686 said:
Can you boot into Fast boot? If so, try connecting your phone to a computer and flashing a recovery through there. Then try to install the ROM.
Click to expand...
Click to collapse
Thanks for your help
Backstory: I tried flashing android revolution for the amaze once, and it didn't work (error 1) left it alone for a bit after recovering it, went back to bulletproof and flashed faux .009 kernel, then decided to try again...
Well I'll try to make this brief, sorry if I'm posting in the wrong subforum but here goes, I tried going from bulletproof 2.5.0 to Android Revolution HD and didn't flash the superwipe .zip (lazy me). The install failed with the same error 1, only this time I can't boot back into recovery. Booting to bootloader works but when I tried going into recovery I see it pop up for maybe a fraction of a second before the phone reboots.
I've tried reflashing clockwork mod but no dice
any sort of tips you folks can give me to steer me in the right direction?
Pulsewave said:
Backstory: I tried flashing android revolution for the amaze once, and it didn't work (error 1) left it alone for a bit after recovering it, went back to bulletproof and flashed faux .009 kernel, then decided to try again...
Well I'll try to make this brief, sorry if I'm posting in the wrong subforum but here goes, I tried going from bulletproof 2.5.0 to Android Revolution HD and didn't flash the superwipe .zip (lazy me). The install failed with the same error 1, only this time I can't boot back into recovery. Booting to bootloader works but when I tried going into recovery I see it pop up for maybe a fraction of a second before the phone reboots.
I've tried reflashing clockwork mod but no dice
any sort of tips you folks can give me to steer me in the right direction?
Click to expand...
Click to collapse
Not sure about the Amaze tbh, but if I had a failed flash on either of my HTC phones, I just re RUU'd.
D'oh! I forgot about that! Had to do that for my buddy's thunderbolt a few times. Lemme give that a shot and I'll report back
Edit: Worked
Edit:double post
im also having this problem, my phone keeps freezing at the startup screen when the htc logo pops up. i dont know much about this kind of stuff so i would really appreciated if anyone could guide me to what to do
the way that my phone froze like that was that i tried to flash a kernel for the Energy rom, i did installed the rom itself
http://forum.xda-developers.com/showthread.php?t=1362759 this is the rom that i wanted to use
and i flashed the kernel that was provided in the 4th post, i downloaded that file, extracted and ran the .bat file and thats how it happened
i would appreciate if anyone could help me with this
Bricked Htc Amaze 4g
I have a bricked HTC Amaze 4g. I had beastmod v2.20 on when i decided i wanted quick sense. After i finished it just froze on the htc startup logo. I played with it and got it into a bootloop. When i try to flash a ruu the blue bar loads up and comes back to the bootloader screen. I can get into recovery but it wont let me flash anything.Thanks to whoever replies I really appreciate it.
lmfaoomg said:
im also having this problem, my phone keeps freezing at the startup screen when the htc logo pops up. i dont know much about this kind of stuff so i would really appreciated if anyone could guide me to what to do
the way that my phone froze like that was that i tried to flash a kernel for the Energy rom, i did installed the rom itself
http://forum.xda-developers.com/showthread.php?t=1362759 this is the rom that i wanted to use
and i flashed the kernel that was provided in the 4th post, i downloaded that file, extracted and ran the .bat file and thats how it happened
i would appreciate if anyone could help me with this
Click to expand...
Click to collapse
You need to superwipe the phone and flash the ROM. After the ROM flashes, you have to flash the kernel twice.
samiaziz said:
I have a bricked HTC Amaze 4g. I had beastmod v2.20 on when i decided i wanted quick sense. After i finished it just froze on the htc startup logo. I played with it and got it into a bootloop. When i try to flash a ruu the blue bar loads up and comes back to the bootloader screen. I really appreciate it.
Click to expand...
Click to collapse
Same with you. You need to superwipe the phone and flash the ROM. After the ROM flashes, you have to flash the kernel twice.
Superwiping the phone removes all the data from the old ROM so you can install a fresh clean ROM.
If you want to install the RUU, you have to relock the bootloader first and then you can reflash the original RUU
Edit: i was misinformed
Sent from my NRGized Amaze...
via xda premium
aj_2423 said:
I dont believe u have to relock
Sent from my NRGized Amaze...
via xda premium
Click to expand...
Click to collapse
To flash an official RUU, you must relock it. I've done so plenty of times lol
Sent From My HTC Amaze 4G via Someone's Room
If the phone wont go into recovery, you have to use ADB and wipe the cache partition for it to go into recovery again. This is apparently a bug with some of recoveries posted by other devs in the development forum. You need to use fastboot.exe to wipe the cache via adb
And if... If the superwipe doesn't work due to recovery version you have try to boot in to your Bootloader run one of hasoon's tool and choose different recovery.. it did happen to me the bootloop before due to the fact the old roms like mike's rom. he doesn't update his script to support the newer recoveries and it doesn't support X's recovery, it will give you an error installation.. just try different recoveries and for sure your problem will be solved..
just make sure boot in your bootloader/H-boot then run hasoon's tool and have enough battery just to make sure...
hasoon2000 said:
To flash an official RUU, you must relock it. I've done so plenty of times lol
Sent From My HTC Amaze 4G via Someone's Room
Click to expand...
Click to collapse
Thanks for the good info Sir but i my HTC Amaze is bootloader locked and S-ON but i cannot find a RUU for T-mobile to unbrick it. Will a Ruu such as this one work?
RUU_Ruby_Videotron_CA_1.46.1530.1_R2_Radio_1.09.550L.17DC_30.68.550L.09_release_227343_signed.exe
My HTC Amaze scans all the versions of the PH85IMG i place on the sd card but goes back to the menu when its down
any advice that could help i will appreciate!
There's a thread in the dev section that has about a dozen RUUs. I don't see how one can miss it.
Thanks for your reply but i was a little unsure and did not want to make my phone any worst than it already is.
Can you explain 1 thing thing for me please - RUU always you to flash the phone via the computer? where as PH85img.zip allows you to flash the phone via sdcard? I hope i am correct here.
but i want to know how can i flash the phone when its connected via HBoot usb cause my pc recognizes it as "Android Composite ADB Interface"
Currently this is what is on my lcd
LOCKED
RUBY PVT SHIP S-ON RL
HBOOT-1.93.0002
EMMC BOOT
MAR 15 2012
i have tried several PH85img.zip files but the phone just scans them and goes back to the menu.
Some help will be appreciated extremely.
---------- Post added at 03:40 PM ---------- Previous post was at 03:33 PM ----------
I forgot to mention it connects to the pc but when i run command adb devices this is what i get
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\rquinlan.GOSL_DOM>adb devices
List of devices attached
C:\Documents and Settings\rquinlan.GOSL_DOM>
The latest ruu would be your best option, do not put the .zip part of the name since its already there, also a ruu may be an exe or zip file, since it is a complete stock file to restore the device, what would your carrier be to be exact? Just not up to reading through everything in this thread to see if you mentioned that piece of info, if its tmobile then the very first file in the stock ruu/ota thread would be the file you need.
Sent from my iPad using Tapatalk HD
thanks for your advice i managed to reboot the phone into recovery but heres whats strange to me the phone is in recovery with HTC on the screen thats it, the pc has recognized it as "MY HTC" in the device manager however, when i run the command adb devices this is what i get "SH218vp00163 offline". i ran the RUU file but i get error 170 usb connection.
so i am a bit lost as device manager can see the phone but the RUU file cannot and i am plugging the phone into the rear of the pc.
any ideas
Linkzz said:
thanks for your advice i managed to reboot the phone into recovery but heres whats strange to me the phone is in recovery with HTC on the screen thats it, the pc has recognized it as "MY HTC" in the device manager however, when i run the command adb devices this is what i get "SH218vp00163 offline". i ran the RUU file but i get error 170 usb connection.
so i am a bit lost as device manager can see the phone but the RUU file cannot and i am plugging the phone into the rear of the pc.
any ideas
Click to expand...
Click to collapse
Why are you using recovery exactly?
RUU's are to be flash via hboot, which is the very first screen you see when you go into the device's bootloader, in the case of exe files, you'll need to flash it via fastboot mode, which happens to be, correct me if I'm wrong, the very first or second option on the hboot menu.
yes you are correct cause i just tried it with an RUU from another carrier. i found out that the phone had 2.14.531 software installed. but the RUU i was using was 1.46 and so i got a signature error 132. now i need to find a way to remove the 2.14.531 software and replace it with a lower version. can you help me here
Linkzz said:
yes you are correct cause i just tried it with an RUU from another carrier. i found out that the phone had 2.14.531 software installed. but the RUU i was using was 1.46 and so i got a signature error 132. now i need to find a way to remove the 2.14.531 software and replace it with a lower version. can you help me here
Click to expand...
Click to collapse
What carrier are you on?
t-mobile
this is the RUU i tried and made a connection but the PH85img.zip are not working no matter how i try
RUU_Ruby_Videotron_CA_1.46.1530.1_R2_Radio_1.09.55 0L.17DC_30.68.550L.09_release_227343_signed.exe
So, I rooted my phone last night and ever since I've been stuck in bootloop. I loaded one rom and it was in bootloop all night until the phone died. I charged the phone up, wiped it and tried another, stuck in bootloop for hours with nothing working. Now, the bigger problem is, I - being an idiot - forgot to do a nandroid backup so there is nothing to restore too, yet when I set it to factory settings it's once again stuck in bootloop.
All my phone now displays is the green HTC logo on the white background, until the phone battery dies.
So... how screwed am I?
EDIT: CDMA, S-on, 1.50, I used HTC dev to root it.
Did you root with HTC dev. You need to flash the boot.IMG using fastboot.
Sent from my HTC Desire S using XDA
MSK01 said:
So, I rooted my phone last night and ever since I've been stuck in bootloop. I loaded one rom and it was in bootloop all night until the phone died. I charged the phone up, wiped it and tried another, stuck in bootloop for hours with nothing working. Now, the bigger problem is, I - being an idiot - forgot to do a nandroid backup so there is nothing to restore too, yet when I set it to factory settings it's once again stuck in bootloop.
All my phone now displays is the green HTC logo on the white background, until the phone battery dies.
So... how screwed am I?
Click to expand...
Click to collapse
We need more info dude.
CMDA or GSM?
what rom did you try to install?
hboot 1.50 or 1.40?
S-On or S-OFF
The more info the more we can help you.
iTzLOLtrain said:
We need more info dude.
CMDA or GSM?
what rom did you try to install?
hboot 1.50 or 1.40?
S-On or S-OFF
The more info the more we can help you.
Click to expand...
Click to collapse
CDMA, S-on, 1.50, I used HTC dev to root it. CM 9 Nightly.
Do what I said. Boot your phone into the boot loader. Select fastboot. Stick the boot.IMG from the Rom you used into the folder on the pc that you used with htcdev.
Connect your device.
Open up command prompt. Navigate to the folder in command prompt where you put the boot.IMG
Type fastboot flash boot boot.IMG
If it works it will say so restart your phone and enjoy.
Sent from my HTC Desire S using XDA
Spazz Monk3y said:
Do what I said. Boot your phone into the boot loader. Select fastboot. Stick the boot.IMG from the Rom you used into the folder on the pc that you used with htcdev.
Connect your device.
Open up command prompt. Navigate to the folder in command prompt where you put the boot.IMG
Type fastboot flash boot boot.IMG
If it works it will say so restart your phone and enjoy.
Sent from my HTC Desire S using XDA
Click to expand...
Click to collapse
If you hadn't said anything I probably would have been running around in circles for the rest of the day. I just did and I'm waiting for it to restart right now. Hopefully it works.
Hopefully it will work. If you flash anymore roms you have to do the same flash boot.img using fastboot since you unlocked with HTC dev.
Sent from my HTC Desire S using XDA
Spazz Monk3y said:
Hopefully it will work. If you flash anymore roms you have to do the same flash boot.img using fastboot since you unlocked with HTC dev.
Sent from my HTC Desire S using XDA
Click to expand...
Click to collapse
Meaning I can just nandroid backup this rom? Or do I have to reflash it then flash the new ones over it?
If you want to flash a new rom do a nandroid backup first and then wipe everything. But everytime you flash a new Rom you have to flash the boot.IMG seperatley that was supplied with the Rom if that makes sense. This also applied when doing a recovery.
Sent from my HTC Desire S using XDA
Spazz Monk3y said:
If you want to flash a new rom do a nandroid backup first and then wipe everything. But everytime you flash a new Rom you have to flash the boot.IMG seperatley that was supplied with the Rom if that makes sense. This also applied when doing a recovery.
Sent from my HTC Desire S using XDA
Click to expand...
Click to collapse
Unless the boot.IMG is automatically with each rom that does not make sense. However, if that means (which I pretty sure it does, I just need that extra clear clarification) that a new boot.IMG is supposed to be supplied with every single new ROM then that would explain why my phone is still in bootloop. No changes since last time I was on, about an hour ago I took the battery out and restarted it.
So it's still in bootloop whenever I try anything.
Help as well...
Stuck in the same problem. Hboot 1.50, S-on, and I'm trying to load Evergreen's CM7 port. I'm also using CWM 4.x (can't remember number, just the non touch version). Whenever I try to start my phone all I get is the white HTC screen with the little vibrate, then the black screen, and then the HTC screen once again and so on. I've tried flashing the boot from the file and then flashing the ROM with and without the boot.img in the .zip file. Help me. Please.
You need to flash the rom first then restart your phone load in to fastboot and flash the boot.img using fastboot. Search the forums there should be a more detailed way on how to do this. But its pretty much the same instructions I gave in previous post.
Try following this if your struggling.
https://www.dropbox.com/s/8qonxj8jsawcesl/Android Fastboot boot.docx
Sent from my HTC Desire S using XDA
If that last reply was meant me, I've already tried that. Doesn't change anything at all.
Ah ok you mentioned you flashed the boot.img first that's all
Also try formatting your sd card or use a spare one and format that and then flashing the Rom and boot.IMG. I had to do that with my desire s.
Sent from my HTC Desire S using XDA
Spazz Monk3y said:
You need to flash the rom first then restart your phone load in to fastboot and flash the boot.img using fastboot. Search the forums there should be a more detailed way on how to do this. But its pretty much the same instructions I gave in previous post.
Try following this if your struggling.
https://www.dropbox.com/s/8qonxj8jsawcesl/Android Fastboot boot.docx
Sent from my HTC Desire S using XDA
Click to expand...
Click to collapse
That worked. Holy ****, that worked! Thank you so much!!
Spazz Monk3y said:
You need to flash the rom first then restart your phone load in to fastboot and flash the boot.img using fastboot. Search the forums there should be a more detailed way on how to do this. But its pretty much the same instructions I gave in previous post.
Try following this if your struggling.
https://www.dropbox.com/s/8qonxj8jsawcesl/Android Fastboot boot.docx
Sent from my HTC Desire S using XDA
Click to expand...
Click to collapse
doesnt work for me :<
Unlocked HBOOT 1.53.0007
rooted with superuser
S-ON
Revolionary CWM v4.0.1.4 (also tried to flash 4EXT but it doesnt work!!:/ )
ROM: cm-9-DevilToast-0.7.5-shooteru.zip
any tips?
sabbath88 said:
doesnt work for me :<
Unlocked HBOOT 1.53.0007
rooted with superuser
S-ON
Revolionary CWM v4.0.1.4 (also tried to flash 4EXT but it doesnt work!!:/ )
ROM: cm-9-DevilToast-0.7.5-shooteru.zip
any tips?
Click to expand...
Click to collapse
Get s-off using the wire trick.
Read, Search, Read again, ... Then Ask with Tapatalk 2
I've been trying to root my HTC Evo 4G LTE phone and I've run into some problems. I was able to root the phone with no problem, however I wasn't able to get S-OFF due to my HBOOT version. I flashed CWM 10 rom so that I could get Jelly Bean on my phone but every time I booted my phone up, it would just hang on the boot logo.
I researched a little more and I found out that I didn't have the right kernel to run that Rom. I read that I was suppose to Flash the boot.img from the Rom I wanted to install using the Flash Image GUI app. I did so, and when my phone rebooted, it goes straight to the Bootloader / Fastboot screen automatically. I can not get it to load the Rom I flashed.
Can anyone help me or lead me in the direction to get the rom to load correctly?
Thanks
juaxoo said:
I've been trying to root my HTC Evo 4G LTE phone and I've run into some problems. I was able to root the phone with no problem, however I wasn't able to get S-OFF due to my HBOOT version. I flashed CWM 10 rom so that I could get Jelly Bean on my phone but every time I booted my phone up, it would just hang on the boot logo.
I researched a little more and I found out that I didn't have the right kernel to run that Rom. I read that I was suppose to Flash the boot.img from the Rom I wanted to install using the Flash Image GUI app. I did so, and when my phone rebooted, it goes straight to the Bootloader / Fastboot screen automatically. I can not get it to load the Rom I flashed.
Can anyone help me or lead me in the direction to get the rom to load correctly?
Thanks
Click to expand...
Click to collapse
I had the same problem when I first Jumped ship from Sense. Since you have S-ON you need to also flash the kernel of any aosp rom. So first things first do you have the android development tools installed on your computer?
T3CHW0LF said:
I had the same problem when I first Jumped ship from Sense. Since you have S-ON you need to also flash the kernel of any aosp rom. So first things first do you have the android development tools installed on your computer?
Click to expand...
Click to collapse
Yes I do. I am using a Mac if that helps in any way