Develop Bugs

[Q] Boot Loop, Need help!

i have been running the kiss kernel for a while now, last night i tried to flash the hellboy kernel and retern to my pacman rom. but it still boots, i have cleared all my caches formated everything but my sd card, have tried flashing all kiss kernels and multipul hellboy kernels, but never gets passed the boot screen.. any ideas?

i managed to get it to the android is upgrading.. starting apps thing, but it gets stuck there.

Did you wipe anything when you flashed the kernel? If the kernel was for jellybean it shouldn't hang like that... not sure?

lilrob1213 said:
Did you wipe anything when you flashed the kernel? If the kernel was for jellybean it shouldn't hang like that... not sure?
Click to expand...
Click to collapse
yeah i wiped the cache, devlink cache, data, system, and a factory reset, been trying to figure it out all day but have not made much improvement

JARR3DF15CH3R said:
yeah i wiped the cache, devlink cache, data, system, and a factory reset, been trying to figure it out all day but have not made much improvement
Click to expand...
Click to collapse
and you installed a rom after wiping those things right? I'm assuming... but just wondering. What rom did you flash and are you CDMA virgin mobile?

lilrob1213 said:
and you installed a rom after wiping those things right? I'm assuming... but just wondering. What rom did you flash and are you CDMA virgin mobile?
Click to expand...
Click to collapse
yeah i installed it after, pacman http://forum.xda-developers.com/showthread.php?t=1948770&page=12
im with telus gsm. the rom was working fine, but i went to change the kernel to hellboy cause i herd it was a bit better and now im in this bootloop

also not running the newest version of that rom, i am running v15a

Oh okay wellllll I'm on virgin mobile and I don't know much about the primou phones and rom and kernel compatibility so I'm afraid I'll have to leave this to someone who knows more... good luck to you though... maybe try booting into bootloader from the recovery and flash the boot.img you had before then flash the rom again?

lilrob1213 said:
Oh okay wellllll I'm on virgin mobile and I don't know much about the primou phones and rom and kernel compatibility so I'm afraid I'll have to leave this to someone who knows more... good luck to you though... maybe try booting into bootloader from the recovery and flash the boot.img you had before then flash the rom again?
Click to expand...
Click to collapse
thanks anyways, ill be sure to give that a try:silly:

Did u wait Little longer time while first boot???? Choose latest kernel n flash. .
Hit thanks if I helped u!!!

bahubali67 said:
Did u wait Little longer time while first boot???? Choose latest kernel n flash. .
Hit thanks if I helped u!!!
Click to expand...
Click to collapse
yeah i always wait a little while, i have chosen latest kernel, has not made a difference, i have gotten better results using an older one of the titanium kiss, hellboy doesnt seem to work with my phone for some reason

Did you use the command
fastboot flash boot boot.img or just
fastboot boot boot.img?
Also,after flashing it,does the terminal say something like this?
Okay.
Okay.
Finished.
Edit:also,see that you are flashing the kernel in the fastboot screen(where it says 'fastboot usb'),and not in the Hboot(bootloader) screen.

mihirengg19 said:
Did you use the command
fastboot flash boot boot.img or just
fastboot boot boot.img?
Also,after flashing it,does the terminal say something like this?
Okay.
Okay.
Finished.
Edit:also,see that you are flashing the kernel in the fastboot screen(where it says 'fastboot usb'),and not in the Hboot(bootloader) screen.
Click to expand...
Click to collapse
i am using the all in one tool kit to flash my kernel, yes i am in fastboot, a window pops up runs through code and my phone reboots, i have changed the kernel on it before, but for some reason this time it wont boot properly at all, the phone is currently at the " android is upgrading" screen, it was the starting apps box with the spinning circle

if you say that it is stuck at android is upgrading - that's because the dalvik works and it is deodexing your gapps.
so i suppose you flashed kernel, flashed rom and gapps and rebooted. well this works from time to time but you have to reboot between flashing rom and gapps.
1. download this kernel: hellboy
2. go to bootloader and flash the kernel.
3. go to recovery and: do a factory reset + wipe system - no need for wiping dalvik or cache cause factory reset does them both.
4. flash your rom
5. reboot.
6. if it boots properly, reboot to recovery and now flash GAPPS package.

1ceb0x said:
if you say that it is stuck at android is upgrading - that's because the dalvik works and it is deodexing your gapps.
so i suppose you flashed kernel, flashed rom and gapps and rebooted. well this works from time to time but you have to reboot between flashing rom and gapps.
1. download this kernel: hellboy
2. go to bootloader and flash the kernel.
3. go to recovery and: do a factory reset + wipe system - no need for wiping dalvik or cache cause factory reset does them both.
4. flash your rom
5. reboot.
6. if it boots properly, reboot to recovery and now flash GAPPS package.
Click to expand...
Click to collapse
thank you so much 1ceb0x! my phone has been in this bootloop for an entire 24 hours,

1ceb0x said:
if you say that it is stuck at android is upgrading - that's because the dalvik works and it is deodexing your gapps.
so i suppose you flashed kernel, flashed rom and gapps and rebooted. well this works from time to time but you have to reboot between flashing rom and gapps.
1. download this kernel:
2. go to bootloader and flash the kernel.
3. go to recovery and: do a factory reset + wipe system - no need for wiping dalvik or cache cause factory reset does them both.
4. flash your rom
5. reboot.
6. if it boots properly, reboot to recovery and now flash GAPPS package.
Click to expand...
Click to collapse
hey icebox, i have the same problem, stuck on pacman logo
can you tell me which hellboy kernel should i use?
i've flashed the 1st one on the mediafire list. thanks!

chikuera said:
hey icebox, i have the same problem, stuck on pacman logo
can you tell me which hellboy kernel should i use?
i've flashed the 1st one on the mediafire list. thanks!
Click to expand...
Click to collapse
Thats the old version.... See the changelog code and flash dat in future..... Right now.... Here u go....
http://www.mediafire.com/?waggdha1ir1lxz0

[Q] wiping cache and dalvik caused boot loop?

my s2 was being glitchy so i went into recovery to wipe cache and dalvik and then rebooted from recovery. i waited and then it just boooot loops and shuts off. im currently using cwm recovery 5.2.7 or something like that. will i be able to flash the newer roms like CyanogenMod 10.2 with that current recovery? and why did the wiping of cache and dalvik booot looped my phone? i thought wiping those just makes my phone less glitchy

You probably had some other issues to cause phone to be glitchy in the first place.
When flashing a new ROM it's recommend you wipe data, system cache and dalvik cache.(cache and dalvik can be wipe after the ROM install before rebooting)

nooob 4 ever said:
im currently using cwm recovery 5.2.7 or something like that. will i be able to flash the newer roms like CyanogenMod 10.2 with that current recovery?
Click to expand...
Click to collapse
No, you are going to have to update to either the newest TWRP or CWM to flash 4.3 ROMs.

I'm gonna jump in and hope this isn't a hijack. I had a similar experience but I wanted to update to the latest TWRP so I could flash a 4.3 ROM (Simbean) .
I Odined in and flashed TWRP 2.6.3. Was able to flash the Slimbean ROM but on first reboot I can't make it past the Samsung screen.
I can get back into TWRP but everything fails. - typical process. "Fix permissions- Success", then "Full wipe - Success" then "Fix permissions (cause I'm trying anything at this point)- Failed"
In TWRP Restoring backups "Failed" Flashing new image "Failed" In between I've tried Erasing everything but the MicroSD card and starting fresh but Noting will install.
I've reflashed TWRP through ODIN but same issue. A couple of times I've got a restore to work but if the phone sleeps it won't wake up. I can only get back to TWRP.
What is the Nuclear Option? Or have I done that already? I've been flashing for years. I've never seen anything like this.
Help.

pairustwo said:
In TWRP Restoring backups "Failed" Flashing new image "Failed" In between I've tried Erasing everything but the MicroSD card and starting fresh but Noting will install.
I've reflashed TWRP through ODIN but same issue. A couple of times I've got a restore to work but if the phone sleeps it won't wake up. I can only get back to TWRP.
What is the Nuclear Option? Or have I done that already? I've been flashing for years. I've never seen anything like this.
Help.
Click to expand...
Click to collapse
Some people have problems with 2.6.3.0. Try to Odin 2.6.1.0 and see if it helps.
http://techerrata.com/browse/twrp2/hercules

help
so what are my options to fix my phone with the current cwm 5.0.27?

nooob 4 ever said:
so what are my options to fix my phone with the current cwm 5.0.27?
Click to expand...
Click to collapse
i can get into cwm and thats it

nooob 4 ever said:
i can get into cwm and thats it
Click to expand...
Click to collapse
Nothing, that recovery is good for 4.1.2 and lower, of u want newer roms u can go to my beanstalk thread or @ThdDude's hellybean thread and the new recoveries are posted...
Sent from a soup'd up Herc while climbing a giant beanstalk to crazy heights.....

what I did is to hold the power button/ remove the battery of your phone. Open it again and wait for it to start. no bootloop.

[SOLVED] Unable to install custom rom after modem upgrade

Hello,
I have a unique issue. I'm having a problem installing any custom rom on my t999 (tmobile). I have been using a custom rom for over a year. Always used TWRP. Started with Paranoid Android and for the last few months I've been using PAC-Man (nightly) roms. I was having gps lock issues, I decided to upgrade the modem to a leaked UVUEMJC, this fixed the gps lock issue. But after the reboot, I was stuck on bootloader screen. The only way I could get the rom to work was to backup the rom, flash the system and data, and after that, the rom would work until reboot. I did this a few times until it stopped working. My efs was corrupted, IMEI missing, To recover it, I went into download mode, and noticed in red Warranty bit =1. I used odin to flashed a rooted cf 4.3 samsung touchwiz rom (root66_TMO_T999UVUEMJC). All imei/efs issues were fixed. I decided to try installing a custom rom again, PAC-Man rom, it installed just fine, all EFS/IMEI info was intact, but at reboot, I got stuck on the CM bootlogo. This happens everytime. IF I recover a backup, it gets stuck on the boot logo. I'm using TWRP v2.6.3.
Anybody have any suggestions on how to fix this issue?
Thanks!

Install TWRP 2.6.3.1. Then take a Nandroid.
Next wipe /Data. Then flash your Custom Rom. Wipe Dalvik + Cache after the Flash. Reboot and report.

Perseus71 said:
Install TWRP 2.6.3.1. Then take a Nandroid.
Next wipe /Data. Then flash your Custom Rom. Wipe Dalvik + Cache after the Flash. Reboot and report.
Click to expand...
Click to collapse
Thanks for the reply Perseus71. I'll give it a shot!

acedik said:
Thanks for the reply Perseus71. I'll give it a shot!
Click to expand...
Click to collapse
Upgrading to the newest TWRP did the trick! Everything is working fine now. :good:
Thanks for the help!

I'm also having trouble flashing PAC-man.
SGH-T999LUVUBMK4
Factory reset everything, wiped SD card.
Tried latest TWRP and CWM.
Suggestions?
D

Donny Orbit said:
I'm also having trouble flashing PAC-man.
SGH-T999LUVUBMK4
Factory reset everything, wiped SD card.
Tried latest TWRP and CWM.
Suggestions?
D
Click to expand...
Click to collapse
You need to post info about the error
Sent from my SGH-M919 using Tapatalk

It says
E: Error executing updater binary in zip '/external
Error flashing zip '/external_sd/pac_d2tmo-night
I tried flashing the Rom that doc fixed specifically for the T999LTE for the CM10.1.2 also with no avail.
Same problem.
D

wipe Dalvik and Cache before trying the rom again. If

Updating to 4.4.4 Sickness

Hi, I'm on the 4.4.2 version of the Sickness, with the MDL bootloader. I've updated the modem to NH7.
Do I need to go through the whole process of updating the firmware, re-rooting, etc., or can I just do a full wipe and update to the Sickness' 4.4.4 V3?
I tried a full wipe and installing it today, but I ran into bootloops/other failures.

its better to use the latest recovery like twrp becuz in twrp 2.8.0.1 which is the latest recovery you can choose wipe and then advance wipe and choose dalvik cache,system,data and cache then wipe and that normally takes care of the boot loops

rblckmnjr84 said:
its better to use the latest recovery like twrp becuz in twrp 2.8.0.1 which is the latest recovery you can choose wipe and then advance wipe and choose dalvik cache,system,data and cache then wipe and that normally takes care of the boot loops
Click to expand...
Click to collapse
CWM and Philz also allow you to wipe system, data, cache, and even the non-existent Dalvik cache partition.... Your post makes it sound like TWRP is the only recovery that does that Just saying..
jonnyboy2040 said:
Hi, I'm on the 4.4.2 version of the Sickness, with the MDL bootloader. I've updated the modem to NH7.
Do I need to go through the whole process of updating the firmware, re-rooting, etc., or can I just do a full wipe and update to the Sickness' 4.4.4 V3?
I tried a full wipe and installing it today, but I ran into bootloops/other failures.
Click to expand...
Click to collapse
As to your question; you should be able to do a full wipe (system/data/cache and even though it literally does nothing because the partition doesn't exist, dalvik) and then flash with no problems. I would say that since you're still one of us few lucky ones still with MDL bootloaders, try to keep an official update as a very last option!
Were you trying to flash a kernel or any other mods along with the ROM? If so, flash only the ROM itself and see how it works.
You say bootloops/other failures... that means you bootloop a lot, and when you don't bootloop something else happens. Could you be more specific on the "other failures?" Any error messages? Were you able to pull a logcat? Did you compare the MD5's? Doesn't sound like a bad download, but you never know...

i understand what you saying however i ran into the same problem using philz touch and got the latest twrp and havent got stuck in boot loops since i read a forum on this and using older recovery to flash kitkat roms has been having people phones stuck in a boot loop and throwing errors after flashing and they updated the recovery to fix it

Sh*t, I have TWRP 2.6 and never have a problem. IMO (and some others) newer versions don't seem to play well with others. That goes for all Recoveries.
As for your issue, you might have a bad DO. Try re downloading the ROM, full wipe and then flash.

well my phone didn't like philz touch it works better with the latest twrp recovery

I actually ran into this last night with philz.. I tried flashing insane 4.4.4 v3 and got stuck in a bootlooop I couldn't recover from. It flashed v1 just fine, but it just wasn't having any of v3. I had to use Odin to flash the latest TWRP and have had no problems.... :/

lordcheeto03 said:
I actually ran into this last night with philz.. I tried flashing insane 4.4.4 v3 and got stuck in a bootlooop I couldn't recover from. It flashed v1 just fine, but it just wasn't having any of v3. I had to use Odin to flash the latest TWRP and have had no problems.... :/
Click to expand...
Click to collapse
Sickness mentioned something about a script that was causing bootlegs when flashing

SOLVED

Hello,
It sure has been a while since I've posted in this forums. I am having some trouble on my phone. Here's the story: I was on MIUI 7, but didn't like the way it was handling memory. It kept closing apps even when there were only 3 running, so I decided to restore a previous CM backup. So, I did that and rebooted the phone. It gave an error saying that "Encryption was interrupted", yet I have never encrypted my phone. Anyway, I decided to flash CM12 with a zip I had. Rebooted, and same problem occurred. Now, I'm trying to reboot phone into recovery, but whenever I do, the screen goes black and re-displays the teamwin logo, and just does that over and over. I tried flashing recovery through fastboot, but same problem. Is my phone savable? It should be, as it isn't hard-bricked. Any help is appreciated!

How do you solve this problem? When I flash CM12, the phone repeat reboot and can't enter recovery. At last I flash the Omini ROM.

Just flash stock rom
flash stock recovery.. go to wipe data and cache.. it will work.. if not try restoring partition with the stock recovery..
you can find stock recovery in oppo community
JackYao said:
How do you solve this problem? When I flash CM12, the phone repeat reboot and can't enter recovery. At last I flash the Omini ROM.
Click to expand...
Click to collapse

sydtek said:
flash stock rom.. go to wipe data and cache.. it will work.. if not try restoring partition with the stock recovery..
you can find stock recovery in oppo community
Click to expand...
Click to collapse
Thanks, I solved the stock recovery. And wipe data and cache, but still can't flash CM rom. At last, I flash the Omini rom. Problem is it often prompt me "Storage space running out".

Try flashing oppo's stock recovery
You can only instal oppo's rom (I.e. ColorOS) in that recovery.. First you have to flash TWRP recovery and then instal the CM rom.. This will work perfectly fine, but in some case like the above the rom would not boot into CM or whatever custom ROM.. In that case you have to instal OPPO's stock recovery to make it work..
And also the insufficient storage problem can be solved by OPPO's stock recovery by using partition - restore partition..
JackYao said:
Thanks, I solved the stock recovery. And wipe data and cache, but still can't flash CM rom. At last, I flash the Omini rom. Problem is it often prompt me "Storage space running out".
Click to expand...
Click to collapse