I flashed my amaze with Dark Glass ONE. I first tried flashing version 0.1 but it was stuck on bootloader, as 30 min had passed the new version came out so I tried flashing version 0.2 but it is stuck on the bootloader again, so far it has been stuck for 30 minutes. I wiped cache, partition, and delvik on both occasions. Is anyone else having problems flashing this rom or CM10? Am I missing something?
The phone is S-ON
Carrier: T-mobile
Have flashed before sucsessfuly, last rom was speed rom Project peanut butter ver 7.5
Thanks
geppettto said:
I flashed my amaze with Dark Glass ONE. I first tried flashing version 0.1 but it was stuck on bootloader, as 30 min had passed the new version came out so I tried flashing version 0.2 but it is stuck on the bootloader again, so far it has been stuck for 30 minutes. I wiped cache, partition, and delvik on both occasions. Is anyone else having problems flashing this rom or CM10? Am I missing something?
The phone is S-ON
Carrier: T-mobile
Have flashed before sucsessfuly, last rom was speed rom Project peanut butter ver 7.5
Thanks
Click to expand...
Click to collapse
i recommend you do a full wipe.. then try installing again
You are S-on, and these roms involve kernel changes. You need to be running 4ext recovery with smart flash enabled. S-on devices can't flash kernels without it.
Sent from my HTC_Amaze_4G
Another option is to use adb and flash the boot.img manually but since you're not capable of flashing a Rom correctly then that might be out of the question.
Kobraki17 said:
You are S-on, and these roms involve kernel changes. You need to be running 4ext recovery with smart flash enabled. S-on devices can't flash kernels without it.
Sent from my HTC_Amaze_4G
Click to expand...
Click to collapse
Used 4ext and the flash went through without any problems. Thank you
Related
I have a gsm evo 3d, unlocked and rooted, s-on
I have managed to make ICS Nonsense rom work on the phone, but whenever i try to flash the COOL ICS V2 rom it gets stuck in bootloop.
The process i use is
- In CWM wipe data, cache and dalvik
- install the rom(COOL ICS V2)
- poweroff and reboot into fastboot
- in cmd i use-> fastboot flash boot boot.img (for the boot.img that comes in the rom)
-Then reboot the phone
After this it is stuck in bootloop, does anyone know the Fix? or did i do it wrong as the same process worked for the nonsense rom.
I think its time for you my friend to S-off your phone in order to be full supported-able to run roms/kernels/addons with no problems you better S-OFF it
sgaheer said:
I have a gsm evo 3d, unlocked and rooted, s-on
I have managed to make ICS Nonsense rom work on the phone, but whenever i try to flash the COOL ICS V2 rom it gets stuck in bootloop.
The process i use is
- In CWM wipe data, cache and dalvik
- install the rom(COOL ICS V2)
- poweroff and reboot into fastboot
- in cmd i use-> fastboot flash boot boot.img (for the boot.img that comes in the rom)
-Then reboot the phone
After this it is stuck in bootloop, does anyone know the Fix? or did i do it wrong as the same process worked for the nonsense rom.
Click to expand...
Click to collapse
try flashing the rom with 4EXT recovery, or with Flash Image GUI. With these recovery programmes you have more chance to succeed and you can even flash kernels with them.
Good luck.
The rom does not ask for s-off, and i am still trying to s-off at the moment will try the 4ext and other process
sgaheer said:
I have a gsm evo 3d
After this it is stuck in bootloop, does anyone know the Fix? or did i do it wrong as the same process worked for the nonsense rom.
Click to expand...
Click to collapse
I see cool ice v2 in the CDMA dev forum too. It's a long shot, but make sure you have the GSM version since flashing the wrong one can cause bootloops.
Sent from my PG86100
It is the GSM version, anyone else manage to get rom working with s-on?
sgaheer said:
It is the GSM version, anyone else manage to get rom working with s-on?
Click to expand...
Click to collapse
I don't know how it is on the GSM side, but I know that the ICS ROMs cause bootloops for people who are S-On. It does not happen to everyone, but it seems that almost everyone who has bootloops is s-on. If you can get s-off (again, I don't know much about GSM), you may have better luck.
I heard that I may have to update the kernel on my EVO 3d with HBOOT-1.5 S-on. I have fully wiped my phone a couple of times and reinstalled with no success. Any insight would be greatly appreciated.
I had that issue with any ics rom. So I unlocked the bootloader with the juno method (s-off) and it stopped doing it
Sent from my HTC One X using xda premium
ryan.ellison said:
I heard that I may have to update the kernel on my EVO 3d with HBOOT-1.5 S-on. I have fully wiped my phone a couple of times and reinstalled with no success. Any insight would be greatly appreciated.
Click to expand...
Click to collapse
You have to flash the kernel for MeanRom ICS, since it can't use the stock GB kernel. I used Flash Image GUI(in the Play Store).
1) Open Flash Image GUI and go to your Mean Rom zip to flash the kernel.
2) Boot into recovery from Flash Image GUI.
3) Flash Mean Rom ICS and reboot.
Check out this video.
http://www.youtube.com/watch?v=nDFO6H1XObI
There are other ways of course like going to S-off, but since you are S-on, this should work.
aypanthony said:
You have to flash the kernel for MeanRom ICS, since it can't use the stock GB kernel. I used Flash Image GUI(in the Play Store).
1) Open Flash Image GUI and go to your Mean Rom zip to flash the kernel.
2) Boot into recovery from Flash Image GUI.
3) Flash Mean Rom ICS and reboot.
There are other ways of course like going to S-off, but since you are S-on, this should work.
Click to expand...
Click to collapse
I tried that and I'm still facing boot loop. Thanks very much for your help
Did you try fastboot flashing the boot.img file?
Sent from my HTC One X using xda premium
Yes i tried that as well. for some reason its still rebooting.
So your hboot 1.5 s-on... Hmm did you flash back to 2.17? Cause I say you try to get soff
Sent from my HTC One X using xda premium
I had the same exact problem, yep s-off is necessary in this case
Sent from my PG86100 using xda premium
Issue resolved. just had to flash a different kernel. Still S-on and its working perfectly with meanrom. Thanks everyone for your help
What kernel did you end up going with?
get 4ext recovery, it has smart flash so you won't be having to use guiflash or fastboot.. and boot loops are common with 1.5 hboot
For the future i would recomend installing 4ext recovery its a recovery biult for evo 3d on s-on. It lets you upload difrent roms. You could by that app at the playstore. You shold really check it out.
OK here's what I have have/have done:
HBOOT 1.50, S-ON
I used fastboot to flash 4ext 1.0.0.5 RC5 to the recovery so I wouldn't have to fastboot every time.
I also flashed "AnthraX-htcleak-rls1.zip" (within 4ext) which supposedly fixes reboot loops.
I would perform a "factory wipe" then turn on SmartFlash and then flash an ICS ROM (MeanROM 2.4, Clean ROM ICS RC2, Derp ROM BDM4.1, viperROM B3) and they all rebooted in one of three ways: as soon as I went to unlock, after sitting on the lock screen for about 5 seconds, or without the lock screen ever loading.
I got CleanROM Reborn (gingerbread) to load and I'm using that for now.
PhillyPhoto said:
OK here's what I have have/have done:
HBOOT 1.50, S-ON
I used fastboot to flash 4ext 1.0.0.5 RC5 to the recovery so I wouldn't have to fastboot every time.
I also flashed "AnthraX-htcleak-rls1.zip" (within 4ext) which supposedly fixes reboot loops.
I would perform a "factory wipe" then turn on SmartFlash and then flash an ICS ROM (MeanROM 2.4, Clean ROM ICS RC2, Derp ROM BDM4.1, viperROM B3) and they all rebooted in one of three ways: as soon as I went to unlock, after sitting on the lock screen for about 5 seconds, or without the lock screen ever loading.
I got CleanROM Reborn (gingerbread) to load and I'm using that for now.
Click to expand...
Click to collapse
First off, doing a factory wipe ins't enough generally. Grab superwipe from the first post of MeanROM ICS and flash that first. Do it multiple times to make sure everything gets clean. Then flash the ROM, and finally the AnthraX kernel.
1. superwipe
2. flash ROM
3. flash kernel
It your still have issues after this then you need to get your 3D s-off. Some just have trouble properly flashing the kernel with s-on on an ICS ROM
gonk24 said:
First off, doing a factory wipe ins't enough generally. Grab superwipe from the first post of MeanROM ICS and flash that first. Do it multiple times to make sure everything gets clean. Then flash the ROM, and finally the AnthraX kernel.
1. superwipe
2. flash ROM
3. flash kernel
It your still have issues after this then you need to get your 3D s-off. Some just have trouble properly flashing the kernel with s-on on an ICS ROM
Click to expand...
Click to collapse
OK, so here's what I ended up doing to get it to work:
Unlock the bootloader with the HTC tool
Flash the recovery using fastboot.exe with 4EXT 1.0.0.5 RC5 (I had actually downloaded this on my phone prio to doing anything so I had the zip file with the .img file in it)
Boot in to 4EXT recovery and turn on SmartFlash
Flash the superwipe zip first
Flash the ICS ROM (in this case MeanROM)
Flash the Anthrax zip file
Reboot the phone and let it go through the setup and it was all set!
So the most frustrating part was unlocking the bootloader, because I misread some instructions at first, and it took me a while to realize I could flash 4EXT to recovery to I wouldn't have to keep booting to it through my PC, but it all worked out in the end. I'm now running ICS on my phone and it was still less of a headache than waiting for Sprint.
A lot has changed in the last year and a half or so since I rooted my EVO 4G. Thanks everyone!
I know this has been discussed before but I haven't found a definitinitve answer to my question regarding it. On the Evo 3d I'm Running MikVirgin Rom RC3 (v1.0?) and Hybrid AnthraX kernel 2.6.38.8-3.0.30. I lost my Wifi the first time I flashed both of these but I don't know which one is breaking it. How do I get my wifi back and what numbers do I have to compare to make sure that a Rom is compatible with a certain kernel?
Edit* Can I flash the EMEA ICS update in the forums to my Sprint (US) phone?
Wifi works with the included kernel on Mik's Rom, so I am guessing it's the kernel. If you want help with it please go to infectedrom.com. I wouldn't suggest flashing the euro update, as it's meant for GSM phones, not CDMA. GSM Evo3Ds are rare in the US.
Edit: To fix WiFi just reflash the ROM without wiping....okay maybe wipe dalvik
bcarter2000 said:
Wifi works with the included kernel on Mik's Rom, so I am guessing it's the kernel. If you want help with it please go to infectedrom.com. I wouldn't suggest flashing the euro update, as it's meant for GSM phones, not CDMA. GSM Evo3Ds are rare in the US.
Edit: To fix WiFi just reflash the ROM without wiping....okay maybe wipe dalvik
Click to expand...
Click to collapse
Okay I wiped Dalvik and flashed the ROM again without flashing the kernel and the same kernel is still there. I flashed the Anthrax Kernel with the ROM to get the bootloops to stop (not as fun as fruitloops either) the first time unless Mik's rom comes with the Anthrax kernel it won't flash over it. Wifi still broken.
You should wipe the cache and delvik after you install your rom and kernel. Also if using 4ext disable smart flash and always shutdown to make sure a full restart takes place. I've done this with other ics roms that required that kernel and never had an issue with them
Sent from my PG86100 using xda premium
Are you S-ON? Wifi could be from boot.img not flashing correctly. I haven't used Mik's rom, but ZR3D ICS with that kernel works fine.
I'm S-On Hboot 1.5 and using twrp, I've wiped both, wiped none, reinstalled and still no luck. Any other ideas? How can I flash back to the factory rom and kernel?
compOH said:
I'm S-On Hboot 1.5 and using twrp, I've wiped both, wiped none, reinstalled and still no luck. Any other ideas? How can I flash back to the factory rom and kernel?
Click to expand...
Click to collapse
I know with s-on you have to flash the boot.img separately. That's your problem.
Sent from my PG86100 using xda app-developers app
compOH said:
I'm S-On Hboot 1.5 and using twrp, I've wiped both, wiped none, reinstalled and still no luck. Any other ideas? How can I flash back to the factory rom and kernel?
Click to expand...
Click to collapse
The WiFi is broke because the kernel modules and the Rom don't mix together. Since you are s-on, the boot partition is locked and you can't use twrp to flash to it. 1) You can manually flash the boot.img (boot.img = kernel) using fastboot. The boot.img is found in the Rom.zip Or 2) adb reboot bootloader then manually boot the recovery img through fastboot. If you use the second method, you can just use your recovery as if you are s-off.
With s-on you need to do these workarounds to flash kernels
Hope this helps!
Edited: the phone I had was running with a non-OEM battery I switched the battery over to the extended OEM and the phone has not boot-looped since then.
I was trying to get rooted again on my rezound that is already s-off. I entered the stock recovery on accident and got the red triangle and after that my phone will boot normally and show the homescreen but it randomly restarts within 5- 10 minutes. This is before I accomplished root. I reset the phone after this and it seemed to stop the bootlooping.
Today I powered on the phone and its bootlooping all over again. This time it boots up normally but reboots anywhere from immediately to up to about 20 mins later. I didn't have any personal info or apps installed because I don't plan on using it until I install a custom rom. I went on to flash Amon-ra 3.15 with adb and installed the SuperSU.zip in AmonRA recovery. So I'm rooted right now. I had no bootlooping while in hboot or recovery. I want to backup my current setup so that I can return to a clean rooted stock if needed.
I've read that many people do a wipe with AmonRA and still have the bootlooping issue. I've been reading a ton of threads and I can't figure it out. Can anyone offer insight on what I did wrong/what happened and how I can fix it?
I'm currently S-off, rooted
Have AmonRa Recovery
SuperSU v0.96
Running software: 3.14.605.12 710RD
Kernel version: 3.0.16-gd0049f1
Baseband: 1.22.10.0421r, 1.22.10.0424r
I would just check through the basics. Did you wipe system, cache, dalvik, etc when you went from one rom to the other. I know when I don't delete the ph98img after I flash a rom and that file in bootloader I would get boot looping. Some one should chime in if this didn't help atleast it was bumped
Sent from my ADR6425LVW using xda app-developers app
queenshawtii said:
Edited: the phone I had was running with a non-OEM battery I switched the battery over to the extended OEM and the phone has not boot-looped since then.
I was trying to get rooted again on my rezound that is already s-off. I entered the stock recovery on accident and got the red triangle and after that my phone will boot normally and show the homescreen but it randomly restarts within 5- 10 minutes. This is before I accomplished root. I reset the phone after this and it seemed to stop the bootlooping.
Today I powered on the phone and its bootlooping all over again. This time it boots up normally but reboots anywhere from immediately to up to about 20 mins later. I didn't have any personal info or apps installed because I don't plan on using it until I install a custom rom. I went on to flash Amon-ra 3.15 with adb and installed the SuperSU.zip in AmonRA recovery. So I'm rooted right now. I had no bootlooping while in hboot or recovery. I want to backup my current setup so that I can return to a clean rooted stock if needed.
I've read that many people do a wipe with AmonRA and still have the bootlooping issue. I've been reading a ton of threads and I can't figure it out. Can anyone offer insight on what I did wrong/what happened and how I can fix it?
I'm currently S-off, rooted
Have AmonRa Recovery
SuperSU v0.96
Running software: 3.14.605.12 710RD
Kernel version: 3.0.16-gd0049f1
Baseband: 1.22.10.0421r, 1.22.10.0424r
Click to expand...
Click to collapse
I'd suggest running an ruu and do a full wipe while in that setup.. then try flashing to where you wanna be..
sent from my s-off reZound rockin' viperRez Rom on global ICS firmware
Thanks for the suggestions guys, I'm stock rooted right now, so i've haven't flashed a rom yet. Famouscollin, your saying that I should pretty much return to the stock ruu and re-root to see if that takes care of the problem?
Since I've changed the battery out, I've had no bootlooping.
Can you recommend a full image backup that I can use?
queenshawtii said:
Thanks for the suggestions guys, I'm stock rooted right now, so i've haven't flashed a rom yet. Famouscollin, your saying that I should pretty much return to the stock ruu and re-root to see if that takes care of the problem?
Since I've changed the battery out, I've had no bootlooping.
Can you recommend a full image backup that I can use?
Click to expand...
Click to collapse
yes that would be my first suggestion as where you could use th updated radios anyways.. itll prolly solve your issue as well..
Running ICS rooted S on
flashed "Official jb ruu 3.15.651.16 Odex. zip" using TWRP it said it was successful. Went back to reboot system. The phone got to the htc quietly brilliant screen, then went black. I got a few white bars to pop up on the top of the black screen then nothing.
I then went in and flashed "boot img flasher v1.2 jb.zip" it failed until I cleared the D-cache, then it passed. Back to the reboot screen. reboot system and it did the same thing.
I then recovered ICS and rebooted and the phone is back to the old system
What am I missing?
Would it be easier to take the OTA version and then root to S off?
I've never bothered with RUU's but if I'm not mistaken you have to re-lock your bootloader and run the RUU through the bootloader, not recovery.
With some of the threads popping up about people having issues with the new JB RUU, you might be better off finding a rooted JB ROM, like MeanBean, and run that, instead. You'd be better off getting S-off, then upgrading.
Sent using my HTC EVO LTE and a magic wand
jchtcusre1 said:
Running ICS rooted S on
flashed "Official jb ruu 3.15.651.16 Odex. zip" using TWRP it said it was successful. Went back to reboot system. The phone got to the htc quietly brilliant screen, then went black. I got a few white bars to pop up on the top of the black screen then nothing.
I then went in and flashed "boot img flasher v1.2 jb.zip" it failed until I cleared the D-cache, then it passed. Back to the reboot screen. reboot system and it did the same thing.
I then recovered ICS and rebooted and the phone is back to the old system
What am I missing?
Would it be easier to take the OTA version and then root to S off?
Click to expand...
Click to collapse
If you're s-on, retry flashing...(wipe everything and start over)..you're gonna have to flash jb Roms twice (as long as they are the zip format ones to my knowledge)...s-on is causing the kernel to take 2 flashes to install....first flash will install the kernel and then after that is successful, reflash without wiping anything and the Rom should boot....its a known procedure/hurdle for s-on users...hope that explains the bootloop. Let me know if it works...
Sent from my EVO using xda app-developers app
onefasttreopro said:
If you're s-on, retry flashing...(wipe everything and start over)..you're gonna have to flash jb Roms twice (as long as they are the zip format ones to my knowledge)...s-on is causing the kernel to take 2 flashes to install....first flash will install the kernel and then after that is successful, reflash without wiping anything and the Rom should boot....its a known procedure/hurdle for s-on users...hope that explains the bootloop. Let me know if it works...
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
This is true with MeanBean due to how the kernel installs. You have to basically flash the ROM twice when you're S-on. Some ROM's have a S-on kernel installer, while others don't.
I still say get S-off, upgrade your firmware and install a rooted JB ROM.
Sent using my HTC EVO LTE and a magic wand
Than
Thank you both, I'll give that a try and see what happens. I wished I could have found that info earlier Been reading and messing with this phone for Hours.
Umm boot img flasher is a windows program that you run on a windows pc. You have to extract all the files out of the zip. NOT flash it on your phone. What hboot do you currently have?
Nope still not there. I tired flashing the rom 5 times and although I got to the second HTC quietly Brilliant screen, it still just goes black. I think I'll look into the dirty racun or lazy panda since I'm still at 1.12 h boot.
jchtcusre1 said:
Nope still not there. I tired flashing the rom 5 times and although I got to the second HTC quietly Brilliant screen, it still just goes black. I think I'll look into the dirty racun or lazy panda since I'm still at 1.12 h boot.
Click to expand...
Click to collapse
Did you do a clean install wiping cache/del cache/system/ factory reset then flash the rom?
What version of twrp are you using? v2.3.3.0 is the latest version
Btw RUU's are .exe files not .zip files AFAIK
Since you're on Hboot 1.12, flashing the kernel separately isn't an issue like it is with the newer Hboots. That being said, it sounds like your issue lies elsewhere. Make sure you've got a good download (verify MD5 checksum) and make sure you wipe properly. For me, I'd wipe cache and Dalvik, factory reset and wipe system (this will wipe your current ROM from your phone), then flash the new ROM. Once you've flashed the new ROM, don't wipe anything in recovery, just go ahead and reboot. I'd definitely look at going S-off, as already stated.