Hi,
I recently bought an HTC Amaze. I have it rooted, bootloader unlocked. Unfortunately, its a SEA (unbranded) version. I tried S-Off so many times but failed. So, I decided to give CM10 and AOKP a try, as I had heard that they don't require S-Off to work on any set.
Firstly, I tried CM10 with TWRP. It didn't work. It was because TWRP doesn't have Smart Flash. So, I switched to 4EXT. It worked. CM10 started, showed me its beauty. Then, suddenly, restarted. And kept restarting. I restored to stock GB ROM. Then, I tried its older builds. Same thing happened. Some people said, kernel could be the issue. So, I decided to try AOKP. Same thing happened. It showed me some screens; select language, lock screen etc. And then restarted. I also tried Dark Glass 0.4, with Mk4 kernel. Same issue happened.
The steps I followed flashing the ROMs are as follows:
For CM10 and AOKP:
1. Wipe data/factory reset
2. Wipe cache/dalvik
3. Format system
For Dark Glass 0.4:
1. Format all partitions except SD
I have been facing this issue. Please help...
Found my answer...
magnum_2007 said:
Hi,
I recently bought an HTC Amaze. I have it rooted, bootloader unlocked. Unfortunately, its a SEA (unbranded) version. I tried S-Off so many times but failed. So, I decided to give CM10 and AOKP a try, as I had heard that they don't require S-Off to work on any set.
Firstly, I tried CM10 with TWRP. It didn't work. It was because TWRP doesn't have Smart Flash. So, I switched to 4EXT. It worked. CM10 started, showed me its beauty. Then, suddenly, restarted. And kept restarting. I restored to stock GB ROM. Then, I tried its older builds. Same thing happened. Some people said, kernel could be the issue. So, I decided to try AOKP. Same thing happened. It showed me some screens; select language, lock screen etc. And then restarted. I also tried Dark Glass 0.4, with Mk4 kernel. Same issue happened.
The steps I followed flashing the ROMs are as follows:
For CM10 and AOKP:
1. Wipe data/factory reset
2. Wipe cache/dalvik
3. Format system
For Dark Glass 0.4:
1. Format all partitions except SD
I have been facing this issue. Please help...
Click to expand...
Click to collapse
Sorry to disturb, I found my answer. To have a ROM based on firmware higher than GB, I need to have that firmware. And to upgrade firmware, I need S-Off. Thanks.
Related
Hello All,
I'm not to this forum. I'm having a very strange issue. I had unlocked and flashed a scotts clean rom to my phone. This rom worked fine. It was the cleanrom standard 4.4. Everything worked fine, but I wanted to try something without sense. So I followed the instructions and ran scott's wipe program that wipes 5 times over. Then I did a wipe on the device. From there it got stuck in a loop where I would boot it into the hboot and it would try to load that weird PH89IMG file and then reboot and do the same thing.
Believe it or not I resolved this by removing the SD card then booting to recovery then slightly lifting the battery and inserting the sd card in and mounting so that I could load another rom after mounting it. Just to be safe I did perform one more wipe. I loaded the CLEANrom tapped edition. It installed and booted up just fine, only one problem. I cannot turn the wifi on.
So I cleared the cache and Dalvik cache, rebooted. still no wifi. It sits on turning on. The wifi mac address is obviously unavailable. It went to an error evetnaully, but there was no detail in it other than the word ERROR. I tried reloading the ICS kernel as well, still nothing. I didn't see anything in the forum on this issue, so I am not sure why it's isolated to my device. can you help me?
Thanks.
I know your tired of wiping and flashing but this has happened to me before on a previous Clean Rom version. Wipe then reinstall ROM. **Caution** Before you boot to Rom, boot to recovery and flash the kernel that came with the Rom. That cleared up my broken wifi. Also beware that if the Clean Rom tapped edition uses a different base ie. 3.14.605.05 or 3.14.605.10. then you have to flash the Stock Rooted RUU of 3.14.605.05 or 3.14.605.10 and then wipe and install ROM. link to stock RUU:
http://forum.xda-developers.com/showthread.php?t=1642217
I have had this issue with a couple newer ICS ROMS I have tried and it all seems to come down to reflashing the Kernel. Even after updating Nils' Roms to newer versions my rezound would load up fine and everything worked except wifi. If I went back into recovery and reflash the kernel wifi would be back to normal again. Make sure you have the correct kernel designated for that ROM as I have noticed some Kernels need to be redownloaded and reinstalled seperately. Good Luck
Hello,
I am having the same problem and I am on Rezound Pure GSM sense 3.6 rom.....I am confused whether to flash the wifi modules for the new kernel from the above link....I don't wanna take any risks as I finally got my GSM working on atnt.
Thanks!!
Hi. i own an HTC EVO V 4G (Virgin Mobile). i used the Search function but sadly didnt found exactly what i needed.
a month or so after activating the phone, i decided to Root, S-off, Flash Recovery, bootloader and a custom Rom. However, its been a while now, that when i do a fresh install i get some inconsistency problems. for example, my first Rom was Harmonia, but later on i switched to MidnightRom. there the problems started to show up. the Sense version was working fine, but then i wanted to try out the Jellybean version. and when i did (after wiping everything, of course) some apps were not working. PlayStore wouldnt let me download anything, Tethering was not working, when using "reboot" the phone would get in a bootloop, which would only go away by removing the battery. and 3D games (Shadowgun, Temple Run, etc.) were graphically laggy. more like, unplayable. the image was distorted to the point it was impossible to see what was going on. messed around with fixing permissions, deleting Cache and Dalvik, re-flashing, and the problem was still there. i tried with other Jellybean Roms (both 4.1 and 4.2) and noticed that the problems were still there. anyways, after deciding to live with the problems (running Wild For the Night). months later i decide to flash MidnightRom again and i see that all the problems are magically gone. to this day ive been running only 4.1+ Roms and i dont have many issues whatsoever. BUT. i tried a Senseless Stock-based Rom the other day (started to miss 3D camera) and it ran well, but the overall behavior of the phone was laggy. it would take longer than usual to do anything. took me about 5 re-flashes to get rid of all the problems. then just yesterday i tried a few other Roms. some worked, though DU was really laggy, and the icons would switch places by themselves at times. as i saw the problem was not going away with re-flashing, fixing permissions and whatnot, i decide to restore to my most stable Flashed Rom.
just to clarify, here is what i do every time im about to flash a new ROM:
Wipe everything except SD card
Wipe Cache and Dalvik
Flash.
Reboot
after i flashed, if something went wrong, or if im flashing something ontop:
Wipe Cache and Dalvik
Fix permissions
Reboot
so question is, is this normal? does this has to do with the phone switching from ICS to JB? or am i doing something wrong?
also, just curious... is there a way one could, say, by some weird reason be "half S-off"? because although my bootloader says S-Off, and i have been able to flash many things, i remember that when doing the Wire thing i experienced many errors, and the thing said it was successful by itself a few seconds later while i wasnt doing anything.
and also, which is the best and most stable Hboot version i could use?
My HBoot version is 1.04.2000 (PG8610000)
Radio is 1.09.00.0706
My Recovery is 4EXT latest version
Thanks in advance
Hellybean is by far the best ROM I've used yet on my Note. It runs almost perfectly. I did have to reboot because my bluetooth wouldn't come on (reboot always fixes that). However, when I rebooted it, the phone tried to restart, I saw the Samsung SGH-I717 screen, and then it went black. It never brings up the Hellybean ring of fire. If I pull the battery I see the ring of fire for about 5 seconds, then it reboots, then black screen.
At this point, the only thing I can do is force the phone into TWRP and restore a previous backup. Does anyone have any idea what could cause the phone to not want to reboot back into the system?
I was on the latest Hellybean build and TWRP is up-to-date as well. I had to revert back to the October 10 build though. I just tried rebooting it after a restore and the same thing happens (so it's not specific to a certain date of ROM). As long as I don't reboot I don't have a problem.
Thanks
Chris
MI_SS_IL said:
Hellybean is by far the best ROM I've used yet on my Note. It runs almost perfectly. I did have to reboot because my bluetooth wouldn't come on (reboot always fixes that). However, when I rebooted it, the phone tried to restart, I saw the Samsung SGH-I717 screen, and then it went black. It never brings up the Hellybean ring of fire. If I pull the battery I see the ring of fire for about 5 seconds, then it reboots, then black screen.
At this point, the only thing I can do is force the phone into TWRP and restore a previous backup. Does anyone have any idea what could cause the phone to not want to reboot back into the system?
I was on the latest Hellybean build and TWRP is up-to-date as well. I had to revert back to the October 10 build though. I just tried rebooting it after a restore and the same thing happens (so it's not specific to a certain date of ROM). As long as I don't reboot I don't have a problem.
Thanks
Chris
Click to expand...
Click to collapse
have you tried any other roms?
I have ran every update of Hellybean since its arrival here. I had made a backup and flashed another rom, didn't like so I went to install back up.
it would not install, just kept looping in the boot screen. had to fresh flash the rom. didn't matter which, just had to reflash. screen never went black though. you issue sounds more similar to a stuck power button, which is why I ask if you have had same problem with another rom.
I find it hard to believe this rom wont restore a back up. others have not chimed in with that specific issue. but you and I may just be 2 that have voiced the issue. wasn't that big of issue for me as I thought it more an oddity. my back up wouldn't install at all in 3 attempts, so again, whyi question your power button.
try another rom real quick if you can. don't have to like or want it, but this is a test right?
let us know what happens
captemo said:
have you tried any other roms?
I have ran every update of Hellybean since its arrival here. I had made a backup and flashed another rom, didn't like so I went to install back up.
it would not install, just kept looping in the boot screen. had to fresh flash the rom. didn't matter which, just had to reflash. screen never went black though. you issue sounds more similar to a stuck power button, which is why I ask if you have had same problem with another rom.
I find it hard to believe this rom wont restore a back up. others have not chimed in with that specific issue. but you and I may just be 2 that have voiced the issue. wasn't that big of issue for me as I thought it more an oddity. my back up wouldn't install at all in 3 attempts, so again, whyi question your power button.
try another rom real quick if you can. don't have to like or want it, but this is a test right?
let us know what happens
Click to expand...
Click to collapse
Let me clarify ... I'm not having a problem restoring or installing Hellybean or any other ROM. It's after I install or restore and the ROM is running fine (for days even) ... at some point I have to reboot for some reason and it's then that it won't boot back into the ROM. In other words I can't reboot my system because it never comes back to the ROM. I have to then boot to TWRP, restore something else and then that will boot to the ROM. If I reboot again after the ROM is up and running, I get the same thing, it won't boot back into the ROM, I have to restore again. That rules out a power button ... if it was stuck I would never get back in.
I've tried most of the ROMs out there, but since Hellybean I haven't tried any others (because this is the best one). You think there's any possibility dirty flashing all of the Hellybean builds over top of each other could cause it? Maybe I'll try installing the latest one from a full wipe.
Thanks
Chris
MI_SS_IL said:
Let me clarify ... I'm not having a problem restoring or installing Hellybean or any other ROM. It's after I install or restore and the ROM is running fine (for days even) ... at some point I have to reboot for some reason and it's then that it won't boot back into the ROM. In other words I can't reboot my system because it never comes back to the ROM. I have to then boot to TWRP, restore something else and then that will boot to the ROM. If I reboot again after the ROM is up and running, I get the same thing, it won't boot back into the ROM, I have to restore again. That rules out a power button ... if it was stuck I would never get back in.
I've tried most of the ROMs out there, but since Hellybean I haven't tried any others (because this is the best one). You think there's any possibility dirty flashing all of the Hellybean builds over top of each other could cause it? Maybe I'll try installing the latest one from a full wipe.
Thanks
Chris
Click to expand...
Click to collapse
I have dirty flashed every one. the only thing I try to do when gong dirty is to still give it that 10 settle time. no particular reason other than my OCD
Okay, thanks for the replies. I'll play around with it some more, maybe try a fresh install and see if that changes anything. I'll let you know if I figure it out.
Chris
I figured it out. Not Hellybean at all. It was TWRP. I reverted back to an early build and then reinstalled 2.6.3.0 and now it reboots fine.
Chris
I guess I can't edit the title to reflect the correct issue? Thread can be deleted if the moderators want. Hellybean is running strong ... it's the first ROM I get 0 random reboots.
Thanks for the help captemo and to the makers of Hellybean.
Chris
beanstalk
I got exactly same problem with beanstalk 4.3.
I tried reinstall recovery but no luck. Every time powering off or rebooting need a fully wipe and restore.
Do you think other or older recovery will work?
hotgly said:
I got exactly same problem with beanstalk 4.3.
I tried reinstall recovery but no luck. Every time powering off or rebooting need a fully wipe and restore.
Do you think other or older recovery will work?
Click to expand...
Click to collapse
Same issue. Any of the 4.3 ROMS.
MI_SS_IL said:
I figured it out. Not Hellybean at all. It was TWRP. I reverted back to an early build and then reinstalled 2.6.3.0 and now it reboots fine.
Chris
Click to expand...
Click to collapse
So did you:
1- restore a stable backup
2- boot to recovery and flash TWRP (which version?)
3- Boot back into recovery
3- wipe and flash HellyBean
Is this correct?
I just installed PM 4.3 and from what i read it should be compatible with newest UBER 3.0 kernal but it just stays stuck in splash (pacman roms, game over, instert coin etc.) I tried downgrading to previous twrp, reflashing rom and gapps, and also tried factory reset. Any help of info would be appreciated, sorry if this is wrong section.
l330n said:
I just installed PM 4.3 and from what i read it should be compatible with newest UBER 3.0 kernal but it just stays stuck in splash (pacman roms, game over, instert coin etc.) I tried downgrading to previous twrp, reflashing rom and gapps, and also tried factory reset. Any help of info would be appreciated, sorry if this is wrong section.
Click to expand...
Click to collapse
there is a compatible Uber for that. most developers will suggest at least 24 hours with kernel included in rom. you don't have to just suggested.
you mentioned a previous TWRP, but you didn't mention any specific versions.
2.6.0.1 is working great for me
2.6.0.3 seemed to have some issues, hence the reason I am still on 0.1
2.6.1.0 is most recent, but until I have problem with 0.1 im sticking with it.
you should always factory reset and it suggested to repeat 3-4 times to clear out any remaining leftover goop.
my routine an also used by others is...........
3 wipes, cleanliness is next to godliness
flash rom alone
flash rom again w/ gapps
wipe davlik and cache
boot up and let settle the 10 mins
reboot and set up
maybe overkill but has not failed me
captemo said:
there is a compatible Uber for that. most developers will suggest at least 24 hours with kernel included in rom. you don't have to just suggested.
you mentioned a previous TWRP, but you didn't mention any specific versions.
2.6.0.1 is working great for me
2.6.0.3 seemed to have some issues, hence the reason I am still on 0.1
2.6.1.0 is most recent, but until I have problem with 0.1 im sticking with it.
you should always factory reset and it suggested to repeat 3-4 times to clear out any remaining leftover goop.
my routine an also used by others is...........
3 wipes, cleanliness is next to godliness
flash rom alone
flash rom again w/ gapps
wipe davlik and cache
boot up and let settle the 10 mins
reboot and set up
maybe overkill but has not failed me
Click to expand...
Click to collapse
Cool, thanks for the tips, ill try them once i get home in the morning from work.
I saw someone recommend twrp 2.6.1.0 (still hangs), at first I had 2.6.3.0 (newest i believe) and still kept hanging on splash
Do you know which uber kernal is the correct one for that rom or is it just the one included in newest pacman rom 4.3?
I may just try out carbon and revolt, seems like more people running those roms. I was messing with some of the color setting in PA and phone locked up on me and it was weird, had like a greenish screen that got brighter and brighter and brighter eventually i just shut it off, it was fine when i restarted. Im not too worried about changing the colors really, i was just tryin it out.
Hi,
I have quite a serious problem with my phone.
I used stable CM11 as my ROM lately, worked nice, seemed to be ok. Now, if I want to boot my phone, it suddenly crashes as soon as I want to enter unlock code. "Funny" thing is, performing a full backup via TWRP didn't help.
So I decided to wipe everything (even sdcard) and do everything from scratch, including flashing boot.img. After flashing the ROM zip, it's still the same.
After that, I flashed boot.img from AOSP 5.1 Unstable, installed this new, different ROM (which I had successfully tested on my device before) and STILL THE SAME?!
What's going on here? It sounds a bit like defective hardware, but I never experienced a crash when I was in Recovery mode, so that's quite unplausible.
My last idea is to flash stock ftf. Perhaps this will help...