So I have tried a bunch of kernels and they all either hang at boot or shortly after. I'd everyone having this issue? I know some are having re-boots. I am stock rooted. Frozen bloat.
Sent from my ADR6400L using XDA App
What kernels are you using? As long as your using Froyo kernels they should work. Wipe cache, wipe dalvic, and flash. I haven't had any kernel issues really. Make sure you flash in recovery!
Need alittle more info. What exactly did you freeze
I'm using Imoseyon's lean kernal and am not having reboot issues. Stock rooted here. Like Smallsz129 is inferring, it may have something to do with what you froze.
Imoseyon has the best kernels. Get his lean edition and unlock 184mhz, it will save a lot if battery.
Sent from my ADR6400L using XDA App
tryceo said:
Imoseyon has the best kernels. Get his lean edition and unlock 184mhz, it will save a lot if battery.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
How do you unlock the 184? I'm running his lean on extreme.
Sent from Thunderbolt, Liquid Thundersense 1.5
It is in the terminal. You have to type:
Su
Speedway.sh
And the look at he options. It should be either 6 or 7.
Make sure you install the right kernel though.
Also, if you are running the extreme version, make sure you run a stress test through setcpu to make sure it doesn't crash. I know that my phone on extreme will crash on 1.4 ghz, but it will run fine on 1.2ghz.
Sent from my ADR6400L using XDA App
tryceo said:
It is in the terminal. You have to type:
Su
Speedway.sh
And the look at he options. It should be either 6 or 7.
Make sure you install the right kernel though.
Also, if you are running the extreme version, make sure you run a stress test through setcpu to make sure it doesn't crash. I know that my phone on extreme will crash on 1.4 ghz, but it will run fine on 1.2ghz.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Thanks for the info.
Sent from Thunderbolt, Liquid Thundersense 1.5
No problem.
Sent from my ADR6400L using XDA App
Im running stock ROM, rooted, and just tried clearing cache and davlik, then flashed imoseyon lean, and im stuck at bootloop also. Had to do a recovery, I can't get his kernel to work either. Whats going on???
wifi is broke and my data is stuck on 1X only now after doing advanced restore-->reboot only.
I just froze bloat. I have tried a few kernels though... Keep freezing on tb boot screen. Not sure why. I must be doing something wrong. I oc all my phone fine, but not this one.
Sent from my ADR6400L using XDA App
mpfstc said:
What kernels are you using? As long as your using Froyo kernels they should work. Wipe cache, wipe dalvic, and flash. I haven't had any kernel issues really. Make sure you flash in recovery!
Click to expand...
Click to collapse
Do you do the full reboot after each one?
Related
when attempting to wipe data for new rom I am getting stuck at
formatting /sdcard / .android_secure
No activity past this point. In order to get out I need to pull battery. What is the importance of this step and how can I correct it? I used two versions of CWM recovery 3.0, one yellow and one red. Happened with both.
Thanks
I believe this has been addressed (assuming you are on a PBJ kernel?)
While it hangs and requires a battery pull, the wipe does complete.
inconvenience yes.. if it bothers you go back to:
http://forum.xda-developers.com/showthread.php?t=1046905
Thanks
Sent from my SCH-I500 using XDA Premium App
Yes, I know there is a problem, and I have an idea for how to fix it, but it is not fixed yet. Possibly in an update later this week or month, depending on time.
i have the same issue with the otb kernel
exzacklyright said:
i have the same issue with the otb kernel
Click to expand...
Click to collapse
Same here. I just battery pulled after a little bit and everything "seemed" to be wiped
Sent from my SCH-I500 using XDA Premium App
So, there is nothing magical about super wipe scripts, but this one seems to have had some serious thought put into it.
http://forum.xda-developers.com/showthread.php?t=834812
I usually wipe manually but was curious what you guys do...
Sent from my EVO using xda app-developers app
adma84 said:
So, there is nothing magical about super wipe scripts, but this one seems to have had some serious thought put into it.
http://forum.xda-developers.com/showthread.php?t=834812
I usually wipe manually but was curious what you guys do...
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
There is only one superwipe for our phone. There is nothing to compare it to, and no need as it works fine. The link you posted has nothing to do with our device.
http://forum.xda-developers.com/showthread.php?p=27166189
Ta da!
I've never understood super wipes. I just do it manually.
No need for a superwipe. Just Factory Reset and wipe System and you're ready to flash. That's never once given me a problem.
I use superwipe mod all the time after a manual wipe. Reason because TWRP does not have option to wipe/format the BOOT partition.
Sent from my EVO using xda premium
theoner1 said:
I use superwipe mod all the time after a manual wipe. Reason because TWRP does not have option to wipe/format the BOOT partition.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
You shouldn't have to wipe boot.
SoraX64 said:
You shouldn't have to wipe boot.
Click to expand...
Click to collapse
Exactly I never even heard of a Superwipe until the 3d came out. Never had to flash one since I had my g1 and i'm not going g to start now
Sent from my EVO using xda premium
SoraX64 said:
You shouldn't have to wipe boot.
Click to expand...
Click to collapse
Install any aosp rom, example deck cm10 8-31-12. The Rom have force close issue with the phone process at the beginning. Now if you want to go back to latest sense Rom, without wiping boot img, you will continue to have the same phone process force close issue even if you're on sense Rom. It just happen to me a couple nights ago. So wiping boot partition is my way of completely getting rid of previous issue on the last install Rom.
Sent from my EVO using xda premium
theoner1 said:
Install any aosp rom, example deck cm10 8-31-12. The Rom have force close issue with the phone process at the beginning. Now if you want to go back to latest sense Rom, without wiping boot img, you will continue to have the same phone process force close issue even if you're on sense Rom. It just happen to me a couple nights ago. So wiping boot partition is my way of completely getting rid of previous issue on the last install Rom.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
I can flash between CM and Sense all I want without the error persisting, maybe you're doing something else wrong?
SoraX64 said:
I can flash between CM and Sense all I want without the error persisting, maybe you're doing something else wrong?
Click to expand...
Click to collapse
I was doing something wrong at the time, I forgot to flash the superwipe. When I first booted into meanrom 3.6 the same phone process force close still there. After realizing I forgot to flash superwipe, went back to recovery, wipe completely manually follow by superwipe then install meanrom 3.6, which booted fine without phone process error. Every time I flash a New Rom I always wipe everything at least twice.
Sent from my EVO using xda premium
theoner1 said:
I was doing something wrong at the time, I forgot to flash the superwipe. When I first booted into meanrom 3.6 the same phone process force close still there. After realizing I forgot to flash superwipe, went back to recovery, wipe completely manually follow by superwipe then install meanrom 3.6, which booted fine without phone process error. Every time I flash a New Rom I always wipe everything at least twice.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Are you by any chance 1.15 S-ON?
Because not a week ago I left CM10 for Viper 4G because I needed the camera to work stably, and I did not receive the force close once.
SoraX64 said:
Are you by any chance 1.15 S-ON?
Because not a week ago I left CM10 for Viper 4G because I needed the camera to work stably, and I did not receive the force close once.
Click to expand...
Click to collapse
Nope orginal hboot 1.12 and s-off
Sent from my EVO using xda premium
theoner1 said:
Nope orginal hboot 1.12 and s-off
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Hmm, interesting because I have gone back and forth between CM10 and MeanRom. I have never had an issue. I love the speed and fluidity of CM10 but the Sense camera is just to good at this point.
I have then same issue...if I don't use sw I have issues bouncing between sense and cmx nands.. can't make calls on sense without it..with it I have no issues
firmbiz94 said:
I have then same issue...if I don't use sw I have issues bouncing between sense and cmx nands.. can't make calls on sense without it..with it I have no issues
Click to expand...
Click to collapse
See what I mean, I'm not the only with this issue. Superwipe work wonders for me too.
Sent from my EVO using xda premium
I think a lot of people got used to using these from the og evo. CWM was thought to have trouble wiping so most would wipe two or three times to make sure it didn't miss anything. I haven't heard of that being an issue for a long, long time though.
One thing that it may help with though is if the ROM doesn't format the system partition. I've spent hours trying to track down bugs only to realize leftover system files were wreaking havoc with the new ROM.
theoner1 said:
See what I mean, I'm not the only with this issue. Superwipe work wonders for me too.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Hmm that's interesting, i remember i flashed tranquility rom and was working great! then tested cmx and at the same time tranquility was updated and that error was still present on the new tranquility rom, but i thought it was the rom so i flashed another sense rom but, this time i used superwipe after manually wiping all and no error anymore, since then i didnt use tranquility thinking it was the new update. now i always use superwipe.
time to go back to tranquility :fingers-crossed::fingers-crossed:
So I have been using Neo's AOSP Rage Rom since about 1.4, and haven't encountered any serious problems (besides some hiccups such as the Trebuchet FC problem in 1.7, although everyone had that). Now, after I have flashed 1.8, I am unable to turn on my Wifi. I checked my md5s, I did 3 clean flashes, and I also flashed the rom with and without the inverted gapps pack.
My Rezound is currently S-ON, and I have no plans to go S-OFF unless necessary.
I'm not sure if this is a kernel problem, or if it's the wifi module, or perhaps something else, but I figured I should ask here first to see if there were others with he same problem.
Most likely kernel, try flashing Snuzzo's kernel
Sent from my ADR6425LVW using xda app-developers app
Squirrel1620 said:
Most likely kernel, try flashing Snuzzo's kernel
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
I've tried that and it didn't help. I tried both of his kernels without success. My problem may be hardware related though. I can't switch back to sense based from without bootlooping. Same thing with flashing ruu.
aftafoya said:
I've tried that and it didn't help. I tried both of his kernels without success. My problem may be hardware related though. I can't switch back to sense based from without bootlooping. Same thing with flashing ruu.
Click to expand...
Click to collapse
If your running an ruu and still boot looping, then something else is wrong. It's gotta be a hardware problem, time for an insurance return
Sent from my ADR6425LVW using xda app-developers app
Well... I figured out what I was doing wrong, which was that I forgot to re-flash the boot.img that came with the Neo's rom. I suppose I forgot to re-flash it because it never said you had to, but I remembered that the rom was intended for S-OFF, and I'm S-ON, so that never occurred to me.
So, yeah, it was basically the kernel.
After I did a clean wipe and flash of Rage again, and flashed the boot.img in the bootloader, everything worked.
Lucasonic said:
Well... I figured out what I was doing wrong, which was that I forgot to re-flash the boot.img that came with the Neo's rom. I suppose I forgot to re-flash it because it never said you had to, but I remembered that the rom was intended for S-OFF, and I'm S-ON, so that never occurred to me.
So, yeah, it was basically the kernel.
After I did a clean wipe and flash of Rage again, and flashed the boot.img in the bootloader, everything worked.
Click to expand...
Click to collapse
Glad to see it works. Yeah so go s off your phone! Lol its worth it
Sent from my ADR6425LVW using xda app-developers app
I've got the same issue. Except wifi, gps, and bluetooth won't turn on. Also, I keep getting the message that my SD card is damaged. I pulled the boot file from the ROM, zipped it, and named it PH89IMG.
So far, everything else seems to work, but this isn't really working for me. Any suggestions?
Are you on ICS firmware or GB firmware? If you are on GB still and trying to flash ICS rom, wifi and sdcard won't work until you flash the old firmware patch.
Sent from my Rezound using Tapatalk 2
Squirrel1620 said:
Glad to see it works. Yeah so go s off your phone! Lol its worth it
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
I second that notion. I've been on 1.8 for a while and I feel like it's been the best version so far (I'm S-OFF). 1.9 is out now, so I'll be trying that later tonight.
Performing S-OFF isn't that bad. I thought it was fun - just follow the directions and you should be fine (like anything else).
So, I've been on 10.1 for a while, and ever since, I can not Reboot to Recovery using normal options.
The only way I can get in to recovery is to open Rom Manager, flash recovery, then reboot recovery from INSIDE rom manager.
No other way works.
It's kind of annoying. I decided today to flash back to stock using ODIN and start fresh again.
From stock, I install CM7. I can reboot to recovery using CM7 no problem.
From CM7, I install CM10.1 nightly (the latest), and after the phone finally gets in to 10.1, I can no longer reboot to recovery from the reboot menu.
I have to install Rom Manager, then flash recovery from it, then reboot from it.
I have to do this process EVERY time I want to reboot recovery.
Any other way I try, it just reboots normally and not in to recovery.
What gives? Anyone else with this problem?
Thanks.
I just tried to use Terminal Emulator and that fails as well.
su
reboot recovery
It just reboots normal.
Have you tried using any other 4.2.1 ROMs?
Sent from my SGH-T959 using xda app-developers app
No, i haven't.
Well then try like hellybean
Sent from my SGH-T959 using xda app-developers app
You should expect to run into problems when using a "nightly" build ROM. Its practically beta stages, find a ROM that is complete like the poster above mentioned. Cant really recommend any 4.2.ROMS , I stick with froyo ROMS for better performance.
Sent from my SGH-T959 using Tapatalk 2
iTz KeeFy said:
You should expect to run into problems when using a "nightly" build ROM. Its practically beta stages, find a ROM that is complete like the poster above mentioned. Cant really recommend any 4.2.ROMS , I stick with froyo ROMS for better performance.
Sent from my SGH-T959 using Tapatalk 2
Click to expand...
Click to collapse
The reason why I recommended that is because he was on a 4.2 ROM that he was having problems with. Sometimes its painful to go to a lower ROM as far as looks and speed goes therefore I recommended a 4.2 that he could try
Sent from my SGH-T959 using xda app-developers app
No one else using this rom has this problem.
dE.fUsEd said:
No one else using this rom has this problem.
Click to expand...
Click to collapse
Well some phones do actually have random differences. On aokp milestone 6 I had to use a linario build because me and like two other people werwbt getting signal
Sent from my SGH-T959 using xda app-developers app
Still having this problem. Using multiple roms. Now I'm on Baked 4.2.2.
Still can't boot to recovery.
This is annoying as hell.
I am having much grief since s-offig last night.
The process succeeded without any issues. I s-offed, re rooted and put on recovery. But when I am going to try new roms, I am having a battle. The only ROM I can get to flash is Stock with Goodies 3.42. CM10, MeanBean, Stock W Goodied 2.08, OMJ will not even flash or boot- it stays on the htc splash for ever/bootloops.
I just tried to flash OMJ again and it froze during Aroma install where you choose the options. Another time it said Symlinks install failed.
Also, I have wiped cache, dalvik, system, and even internal storage and after doing all this, the phone will remember what background I had on the previous flash of Stock with Goodies. !?
I have been flashing for 4 years now. I haven't had so much trouble. Any suggestions? Do I need to flash some Kernel?
It is keeping the wallpaper because you have your Google settings set to back up your phone settings.
For the other stuff. Not sure. What version of twrp are you on?
Sent from my EVO using xda premium
NaterTots said:
It is keeping the wallpaper because you have your Google settings set to back up your phone settings.
For the other stuff. Not sure. What version of twrp are you on?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
The latest TWRP. Just installed it last night.
typhoonikan said:
The latest TWRP. Just installed it last night.
Click to expand...
Click to collapse
Find twrp 2.3.3. If you do not have the latest touch panel. S off is the greatest way to use this phone. That should not be a problem but a solution
Sent from my EVO using xda app-developers app
I would also make sure that your version if software matches the ROM your trying to flash
Sent from my EVO using xda premium