Develop Bugs

Stuck at Samsung logo?

Ok so I went back to stock after CM9, all went fine, phone rebooted and does the animation and sound but it won't go any further, I tried getting into the recovery screen but goes as far the little android guy and then reboots. Any ideas?

Reflashed Euro stock and again stuck at boot animation, I can't get into recovery to wipe or anything as it won't go past the little Android guy and reboots any ideas? On my SGS2 what I would of done at this stage is go into recovery and reset all, but can;t do this, gonna try flashing CWM to see if this helps, stock recovery seems fooked.

flash
Hi! You have to flash your phone stock ROM. And then again try to flash the MOD

slugger09 said:
Ok so I went back to stock after CM9, all went fine, phone rebooted and does the animation and sound but it won't go any further, I tried getting into the recovery screen but goes as far the little android guy and then reboots. Any ideas?
Click to expand...
Click to collapse
Have you checked the zip file you downloaded is corrupt or not?
There is a difference 1mb will cause bootlop on your device.

slugger09 said:
Reflashed Euro stock and again stuck at boot animation, I can't get into recovery to wipe or anything as it won't go past the little Android guy and reboots any ideas? On my SGS2 what I would of done at this stage is go into recovery and reset all, but can;t do this, gonna try flashing CWM to see if this helps, stock recovery seems fooked.
Click to expand...
Click to collapse
Ok, recorrect.
I missread.
Have u got an SD card?
Just put a new stable ROM in it.
And befoure installing the new ROM wipe factory settings, cache, dalvik cache.
And make sure it is wiped, then install the new one.
Because it might save some setting from that ROM, and they might be corrupted, so it's recommended to wipe those befoure ROM installing, and after, when the ROM is installed already.
And if you can't get into recovery mode, then ur phone might be bricked.
No idea, how to solve that.
Haven't experienced that at all.

slugger09 said:
Reflashed Euro stock and again stuck at boot animation, I can't get into recovery to wipe or anything as it won't go past the little Android guy and reboots any ideas? On my SGS2 what I would of done at this stage is go into recovery and reset all, but can;t do this, gonna try flashing CWM to see if this helps, stock recovery seems fooked.
Click to expand...
Click to collapse
If you can go into Download Mode, you can try using Odin to fix things up. Otherwise, your phone is hard-bricked, and only SSC can help.
-- xda app / Pristine NoMod CM9b4 / CastagnaIT kernel / GT-I8150 --

Hi!
Try to remove the external sd card!!
My phone had a bootloop like this on every custom rom,(also stock rom but with wipe i had resolved).
So try to remove the sd card!

stuck at google for 2nd time niw!

Hello, this issue has happened to me before , I was on a 4.2.2 ROM , I flashed unofficial cm10.2 4.3 rom by carlos, the ROM was acting buggy, so I rebooted, and then I'm stucked at Google , rebooted into recovery , wiped everything , flashed another ROM , still stuck at Google, I had to wip everything including my SD data ;( , flashed Google factory image , rebooted fine, my question is , why I cannot roll back or install another ROM after flashing a 4.3 ROM? I always has to wipe all my data , I thought twrp was the problem, but this time I was using cwm, I'm so confused right now , I'm scared if I flashed a 4.2.2 ROM , then come back to 4.3 I will get stucked at Google again! What could be the solution to problem?

razi914 said:
Hello, this issue has happened to me before , I was on a 4.2.2 ROM , I flashed unofficial cm10.2 4.3 rom by carlos, the ROM was acting buggy, so I rebooted, and then I'm stucked at Google , rebooted into recovery , wiped everything , flashed another ROM , still stuck at Google, I had to wip everything including my SD data ;( , flashed Google factory image , rebooted fine, my question is , why I cannot roll back or install another ROM after flashing a 4.3 ROM? I always has to wipe all my data , I thought twrp was the problem, but this time I was using cwm, I'm so confused right now , I'm scared if I flashed a 4.2.2 ROM , then come back to 4.3 I will get stucked at Google again! What could be the solution to problem?
Click to expand...
Click to collapse
Ok... so you wrote to my ROM thread about it and I try to help you!
1. Use CWM, I ahve no experience of TWRP and I can't help Nexus users who uses TWRP
2. Flash factory images by wiping everything
3. If you flash a ROM then in CWM wipe data factory reset <-- it keeps files in the internal storage
4. Then flash a ROM
5. If it happens again them maybe something is broken on your Nexus, then I recommend the phone service...
Sorry I'm busy ad I read that quick if I missed some lines or didn't understand something, then I apologize

Carlos_Manuel said:
Ok... so you wrote to my ROM thread about it and I try to help you!
1. Use CWM, I ahve no experience of TWRP and I can't help Nexus users who uses TWRP
2. Flash factory images by wiping everything
3. If you flash a ROM then in CWM wipe data factory reset <-- it keeps files in the internal storage
4. Then flash a ROM
5. If it happens again them maybe something is broken on your Nexus, then I recommend the phone service...
Sorry I'm busy ad I read that quick if I missed some lines or didn't understand something, then I apologize
Click to expand...
Click to collapse
You better get some rest bro, u didn't read anything,! This issue also happened to you also, you said a 10-15 pages back that ur stuck on google too after rebooting, ! P.s i will install dreams 4.1.x , and wait for a 110% stable cm10.2 by you!

if you're reverting back from 4.3 to 4.2, you should do the Factory/Data Reset and you should boot into OS just fine, i had that problem too and that is how i sorted it out.

lastforone said:
if you're reverting back from 4.3 to 4.2, you should do the Factory/Data Reset and you should boot into OS just fine, i had that problem too and that is how i sorted it out.
Click to expand...
Click to collapse
no didnt worked for me,, had to flash factrory image

S2 Not Booting Up

Hey guys, hope you can help me out.
My brother's phone was running a PacMan rom from June; today I decided to find an update for the rom and did so via Goo.im - I believe I definitely downloaded something completely different (I believe I ended up downloading Chameleon...). Being the idiot that I am, I decided to rename the zip file to update.zip and installed it as an update. When I rebooted the phone, it would not boot up past the Chameleon OS screen.
I've tried to do a factory reset and flash a new rom (Pac-Rom) but it does not boot past the CyanogenMod screen.
What can I do? I can still access the recovery.
Thanks!

You need to factory reset , wipe /system, wipe/cache , wipe dalvic cache. Then proceed to flash what ROM you want again
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

[Q] TWRP 2.7.0.1 Bootloop Issue

Hey guys, Ive had an issue that I just cant seem to fix.
A friend of mine has an LG GPad 8.3 like mine, and it has TWRP custom recovery with one of the new 4.4.2 w/root flashable firmware US version. He made the mistake of going into Backup and Reset in the settings menu in the OS and selected Restore Device to factory settings, and now Its locked into a permanent TWRP boot loop. I've tried everything I know including flashing numerous other ROMs, formatting virtually everything you can format in TWRP. Even after a new rom is successfully flashed, and you factory reset and everything else, upon reboot it will only go back to TWRP again. Over and over. Is there any way you guys can think of that can stop it from going into recovery and click into the proper boot sequence again? Cheers

djleez82 said:
Hey guys, Ive had an issue that I just cant seem to fix.
A friend of mine has an LG GPad 8.3 like mine, and it has TWRP custom recovery with one of the new 4.4.2 w/root flashable firmware US version. He made the mistake of going into Backup and Reset in the settings menu in the OS and selected Restore Device to factory settings, and now Its locked into a permanent TWRP boot loop. I've tried everything I know including flashing numerous other ROMs, formatting virtually everything you can format in TWRP. Even after a new rom is successfully flashed, and you factory reset and everything else, upon reboot it will only go back to TWRP again. Over and over. Is there any way you guys can think of that can stop it from going into recovery and click into the proper boot sequence again? Cheers
Click to expand...
Click to collapse
Reset FOTA? http://forum.xda-developers.com/showthread.php?t=2639822

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