Develop Bugs

[Q} Can't get custom roms to boot past splash screens.

I'm not new to flashing been doing it for going on 5 years. I got an T989 and wanted to put a custom rom on it. I followed instructions to install CWM using ODIN and got my CWM working, I flashed CM10 stable hercules following the instructions exactly (factory wipe, wipe cache, wipe dalvic, flash modem, flash rom, flash gapps, reboot), When it reboots I get the roms splash creen for CM 10 andit stays there forever. I also tried Slim Bean 3.0 and get the same results. I've tried going back to stock ICS and starting over from scratch and each time I get the same result I get to the splash screen and nothing else. I am using CWM 5.0.2.7.
Anyone got any thoughts on what I might be doing wrong I've been reading post after post for about 4 hours now..

jjlwork said:
I'm not new to flashing been doing it for going on 5 years. I got an T989 and wanted to put a custom rom on it. I followed instructions to install CWM using ODIN and got my CWM working, I flashed CM10 stable hercules following the instructions exactly (factory wipe, wipe cache, wipe dalvic, flash modem, flash rom, flash gapps, reboot), When it reboots I get the roms splash creen for CM 10 andit stays there forever. I also tried Slim Bean 3.0 and get the same results. I've tried going back to stock ICS and starting over from scratch and each time I get the same result I get to the splash screen and nothing else. I am using CWM 5.0.2.7.
Anyone got any thoughts on what I might be doing wrong I've been reading post after post for about 4 hours now..
Click to expand...
Click to collapse
When using cwm 5.0.2.7 or below, use the dark side super wipe for all the wiping BEFORE flashing (data, system, cache, etc...)
Sent from my SAMSUNG-SGH-T989 using xda app-developers app

Thanks, I actually just found a thread about the "proper way to flash" and seen that 5.0.2.7 was my issue, I upped to 6.0.1.5 we'll see how that goes

So, I used dark side super wipe, then flashed as per how I listed above and still same results . There has got to be something I am missing.

jjlwork said:
So, I used dark side super wipe, then flashed as per how I listed above and still same results . There has got to be something I am missing.
Click to expand...
Click to collapse
I would suggest using TWRP 2.3.1.1 there are no issues with this and you might find better results... just download goomanager app and press menu and select install openrecoveryscript and go through the setup see if you can flash then and good luck with your ROM flashing

NOthing wants to work for me today. When I try to install TWRP it says there are no recoveries for my device....

Try the flash able zip here http://forum.xda-developers.com/showthread.php?t=1768742
And if you do use TWRP you will NOT need the superwipe scripts

This is very messed up, got the flashable zip, everything wen't fine, tried to wipe cash with twrp and device froze until it rebooted by itself. tried installing rom, and now I when I try to go back into twrp it hangs on the splash screen for TWRP. Now I'll have to ODIN back to stock to get back to functioning....something is definately not right here.

You forgot to wipe system. Factory wipe then system wipe...then dalvik and cache wipe. But darkside superwipe should have done that for you.
Sent from my SGH-T989

No, only use the darkside wipes with CWM 5.0.2.7. With 6.0.1.4+, just wipe manually following those steps I posted in that thread. Although you don't need to flash the radio every time. The radio stays no matter how many times you flash.
To make it easier for you..
Go back to stock. Root and install CWM 5.0.2.7.
When you get into recovery flash the darkside super wipe twice and flash the ROM. Then gapps. Reboot and you're good to go. The issue is that you tried using the dark side wipes when they're only meant to be used with TWRP and versions of CWM 5.0.2.7 and lower.
CWM 5.0.2.7 for this phone didn't function correctly so TDJ made those scripts with fixes included specifically for CWM 5.0.2.7.
Point is.. only use TDJs wipes with TWRP (any version) or CWM 5.0.2.7 or lower. With every other recovery just wipe manually as stated in that thread.
Sent from my SAMSUNG-SGH-T989 using xda premium[/QUOTE]
Sent from my SAMSUNG-SGH-T989 using xda premium

here is the issue darkside wipe works fine with 5.0.2.7, but I still get just the splash screen of the rom and no boot. When I use a newer CWM and I am preparing to clear cache the phone freezes and goes into a boot loop, same with TWRP. After using TWRP last night I got screwed and couldn't even get back to recovery. I odined a 5.8.1.3 version of CWM to see if I could back into recovery and I can, but it says E:Can't open /cache/recovery/log and E:Can't open /cache/recovery/last_log.I also can't do anythiing in the recovery as every time i press a button it reloads. I'm just waiting for the stock telus rom to d/l and going to odin back to stock. I'm really lost. I'm starting to think I might have bad nand.....is there an app I can check that with?

Finally, the instruction to use 5.0.2.7 and dark wipe 2 times before installing rom worked Thanks for all the help all!

I also use the darkside cache wipe after flashing the ROM/gapps which properly wipes cache/dalvik on cwm 5.0.2.7.
Sent from my SAMSUNG-SGH-T989

mintharis said:
I also use the darkside cache wipe after flashing the ROM/gapps which properly wipes cache/dalvik on cwm 5.0.2.7.
Sent from my SAMSUNG-SGH-T989
Click to expand...
Click to collapse
NO. Only use the cache wipe if you're having issues. Cache wiping after ROM installation is absolutely unnecessary. Let's not muck things up here.
Sent from my SAMSUNG-SGH-T989 using xda premium
---------- Post added at 03:49 PM ---------- Previous post was at 03:47 PM ----------
jjlwork said:
Finally, the instruction to use 5.0.2.7 and dark wipe 2 times before installing rom worked Thanks for all the help all!
Click to expand...
Click to collapse
You're welcome buddy I myself have reverted to using CWM 5.0.2.7 over any other recovery. Works perfectly when using the Dark side scripts.
Sent from my SAMSUNG-SGH-T989 using xda premium

Was having the same issues as OP. Would install fine and then wouldn't get past the animation.
Got dark side super wipe and cache wipe and worked like a charm first time! Thank goodness
Sent from my SAMSUNG-SGH-T989 using xda premium

[Q] Boot Fail after Custom ROM

I have a Samsung Galaxy Nexus GSM and have been trying to install the Paranoid Android flavor custom ROM, I had 2.22 installed not long ago but managed to screw it up when I updated it without clearing my security settings (I had a 4x4 pattern swipe which I couldn't enter with the update which restored it to 3x3 pattern) so I wiped and restored to stock 4.2. I'm now trying to re-install with any custom ROM but it's not working.
Whenever I install a ROM it seems to install ok but when I get to the boot screen it just hangs on the nexus/PA logo.
I've tried with:
Goo Manager
TWRP 2.2
TWRP 2.3
CWM 6.0.1.5
and with
PA 2.22
PA 2.99.1
PA 2.99.5
PA 2.99.6
PA 2.99.7
and I always get the same error, I've tried wiping all options within TWRP and CWM and going from there but that doesn't seem to work, the strange thing for me though is that if I re-install a stock Google ROM it works perfectly fine.
I'm fairly new so please be gentle.

flash the latest twrp and move the rom and gapps to your sdcard then follow this..
1. factory reset
2. wipe system
3. wipe cache
4. wipe dalvik
5. flash rom
6. flash gapps
7. reboot
if it still freezes at boot animation pull battery reboot to recovery wipe cache/dalvik and reboot

Thanks for the suggestion but that didn't work.
Any other suggestions?

When you say TWRP 2.3 do you mean 2.3.2.1? http://teamw.in/project/twrp2/90
Clockwork 6.0.1.5 is also outdated, newest is 6.0.1.9.
You need to update your recoveries for Android 4.2.X which is what PA 2.99 is based off of.

zephiK said:
When you say TWRP 2.3 do you mean 2.3.2.1?
Clockwork 6.0.1.5 is also outdated, newest is 6.0.1.9.
You need to update your recoveries for Android 4.2.X which is what PA 2.99 is based off of.
Click to expand...
Click to collapse
Yes I did mean 2.3.2.1, I wasn't sure what the whole version number was at the time and I was halfway through resetting up stock on my phone at the time so I didn't bother to check exactly. sorry about that.
Is there a way to completely wipe everything on the phone so that it is bare stock? I was just wondering if I would be able to start from a clean phone if it would make any difference. I'm aware of cache/delvik cache/internal storage/(i think it's called "system partition" or something like that).

Using TWRP, wiping cache, dalvik, and system should wipe everything except the sdcard contents. So doing these wipes should make your phone "bare stock" again as you described
Why don't you try downloading another custom ROM or download the same ROM again because maybe it is corrupted or something

osiris231 said:
Yes I did mean 2.3.2.1, I wasn't sure what the whole version number was at the time and I was halfway through resetting up stock on my phone at the time so I didn't bother to check exactly. sorry about that.
Is there a way to completely wipe everything on the phone so that it is bare stock? I was just wondering if I would be able to start from a clean phone if it would make any difference. I'm aware of cache/delvik cache/internal storage/(i think it's called "system partition" or something like that).
Click to expand...
Click to collapse
RANT: huh..... seriously? you couldn't have browsed around, searching for this COMMON issue (which usually comes down to user "error"), read the STICKIES, before posting?
first, internal storage = /data/media aka /storage/sdcard0/ aka /sdcard/
Please read all of this
http://forum.xda-developers.com/showthread.php?t=1626895

[Q] Keeps looping after flash

Hi all, I had flashed successfully before but wanted to flash to a JB rom. I wiped and flashed, but then it just keeps looping the Samsung load screen, then I see the loading bar... and it reboots and goes back to the loading bar... Did I mess something up? Or is it suppose to do this the first time?
Sometimes it gets as far as the t-mobile 4G screen and the loops back again...
Thanks

What did you wipe?
Sent from my SGH-T989 using xda app-developers app

And what did you wipe with?
If you used an older clockwork mod recovery, you probably need to update your recovery or get one of the updated wipe scripts on this forum.
Sent from my Nexus 7 using Tapatalk 4 Beta

Have some question for you:
1/ What JB rom you flash?
2/ What recovery mod u used? (TWRP or CWM?)
3/ Did u wipe data / wipe cache / wipe devil ???

nguyenduytan said:
Have some question for you:
1/ What JB rom you flash?
2/ What recovery mod u used? (TWRP or CWM?)
3/ Did u wipe data / wipe cache / wipe devil ???
Click to expand...
Click to collapse
I tried to flash Infamous S2 as well as Jedi Mind Trick. After more reading, I also flashed the "wipe" zip file that was linked. After I flashed that clean wipe, all is well. For some reason when I did the usual wipe wipe (with CWM), stuff probably didn't get over written.
All is well and working smoothly now with Jedi Mind Trick

sky322 said:
I tried to flash Infamous S2 as well as Jedi Mind Trick. After more reading, I also flashed the "wipe" zip file that was linked. After I flashed that clean wipe, all is well. For some reason when I did the usual wipe wipe (with CWM), stuff probably didn't get over written.
All is well and working smoothly now with Jedi Mind Trick
Click to expand...
Click to collapse
it's a combination of how partition gets accessed vs custom recovery(in this case type of wipe) that cause that bootloop.
Provided you didnt have a bad download(.zip bein flashed) If it's a custom ROM suffice to say u need Darkside super wipe.
Unless its a stock (modded) ROM then Infamous super wipe is the way to go.
Hit thanks if/when it helped.

Cannot boot S4 after custom ROM flashes

My T-Mobile Galaxy s4 M919 will not boot after any custom ROM flashes. I tried 4 different ROMs with success messages. As soon as I reboot my phone after the ROM flash, it's stuck at the Samsung Galaxy S4 logo and would not enter the "phone desktop". I can easily enter download mode and recovery mode without any issue.
Background: I rooted with Odin successfully. (Used both CWM and OUDHS with the same no-boot results after flashing any custom ROMs). I can restore back to stock and phone boot up fine but tried root again and then with custom ROM and it would not boot. Any help would appreciate it.

After flashing a rom, go into recovery, and erase stuff. Like cache and dalvik cache. Possibly even data
Sent from my SGH-M919 using XDA Premium 4 mobile app

Android_Monsters said:
After flashing a rom, go into recovery, and erase stuff. Like cache and dalvik cache. Possibly even data
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I did that after each ROM flash. 1. Wipe data/factory reset, 2. wipe cache part, 3. wipe dalvik cache. Did not fix the problem. No good. Please clarify "possibly even data". I am not sure which wipe is that.

anothersaddream said:
I did that after each ROM flash. 1. Wipe data/factory reset, 2. wipe cache part, 3. wipe dalvik cache. Did not fix the problem. No good. Please clarify "possibly even data". I am not sure which wipe is that.
Click to expand...
Click to collapse
using CWM:
*wipe data/factory reset
*wipe cache
*wipe, dalvik cache
*wipe system
*wipe sdcard (only if you have the ROMs you plan on flashing on your external sdcard, this will erase internal sd)
now flash your ROM of choice. reboot (will take 1-2min on first boot)
use cwm touch. what ROMs have you tried so far?

I am thinking you are flashing something not specific to the TMo S4, so your not getting the right kernel installed. Try installing a TMo specific kernel immediately after flashing a rom and see what happens.

Yeah, what ROMs have you tried already? Have you tried TWRP 2.5 recovery?
Sometimes it'll take up to 10 minutes to boot up (I haven't experienced this yet with the GS4, but I have with other phones). How long did you wait before determining it was just stuck?

I switched to PhilZ Touch Recovery a couple of weeks ago and have not had Any issues as I did before.
TWRP 2.5.0.2 was issue free for months, until I started flashing ROMs with Aroma.
Nothing but issues re Samsung splash screen freezes, different solutions working sometimes and sometimes not, having to ODIN back to stock on many occasions, having to wipe INTERNAL SD on many occasions, etc., etc.
PhilZ was the solution.
This is coming from a hard core TWRP guy......
Check the link in Red in my sig for PhilZ and other good stuff

dynospectrum said:
using CWM:
*wipe data/factory reset
*wipe cache
*wipe, dalvik cache
*wipe system
*wipe sdcard (only if you have the ROMs you plan on flashing on your external sdcard, this will erase internal sd)
now flash your ROM of choice. reboot (will take 1-2min on first boot)
use cwm touch. what ROMs have you tried so far?
Click to expand...
Click to collapse
Where do you "wipe system"? I see a format /system inside Mounts and Storage Menu. Please confirm.

DKYang said:
Yeah, what ROMs have you tried already? Have you tried TWRP 2.5 recovery?
Sometimes it'll take up to 10 minutes to boot up (I haven't experienced this yet with the GS4, but I have with other phones). How long did you wait before determining it was just stuck?
Click to expand...
Click to collapse
I have not tried TWRP 2.5 recovery yet. I mostly use CWM. I have waited 20+ minutes after flashing a custom ROMs but to no success.
I have done the following ROMs:
Insanity v1
VirginROM

stevessvt said:
I am thinking you are flashing something not specific to the TMo S4, so your not getting the right kernel installed. Try installing a TMo specific kernel immediately after flashing a rom and see what happens.
Click to expand...
Click to collapse
I did try the InFamous ROM for Tmobile s4. This ROM also has a kernal. Same results, stuck at Samsung Galaxy s4 Logo screen. It would not go anywhere after that.
Really needing help here.

anothersaddream said:
I did try the InFamous ROM for Tmobile s4. This ROM also has a kernal. Same results, stuck at Samsung Galaxy s4 Logo screen. It would not go anywhere after that.
Really needing help here.
Click to expand...
Click to collapse
Okay let's start over from scratch.
First off can you restore the stock ROM using your nandroid backup?
Second, I don't think you are properly wiping everything prior to flashing the new ROM. You need to wipe system, data, dalvik, and cache in the CWM wipe menu prior to flashing the new ROM.
Wipe all 4 things. Wiping any less than all 4 things will cause the problems you are experiencing.
Once you've done that, then flash the ROM.zip and reboot and it should work just fine.

anothersaddream said:
Where do you "wipe system"? I see a format /system inside Mounts and Storage Menu. Please confirm.
Click to expand...
Click to collapse
wipe = format
yes, format system in mounts/storage.

Skipjacks said:
Okay let's start over from scratch.
First off can you restore the stock ROM using your nandroid backup?
Second, I don't think you are properly wiping everything prior to flashing the new ROM. You need to wipe system, data, dalvik, and cache in the CWM wipe menu prior to flashing the new ROM.
Wipe all 4 things. Wiping any less than all 4 things will cause the problems you are experiencing.
Once you've done that, then flash the ROM.zip and reboot and it should work just fine.
Click to expand...
Click to collapse
I did exactly what you stated. Restored to stock. Rooted successfully. Wiped all 4 things. ROM flash stated success. Still NO good. Stuck samsung S4 logo. You think there is something wrong with the hardware???? The s4 does randomly reboot on stock.

anothersaddream said:
I did exactly what you stated. Restored to stock. Rooted successfully. Wiped all 4 things. ROM flash stated success. Still NO good. Stuck samsung g4 logo. You think there is something wrong with the hardware???? The s4 does randomly reboot on stock.
Click to expand...
Click to collapse
When I was flashing ROMs w/Aroma using TWRP 2.5.0.2, I would sometimes get Samsung boot screen freezes. The only way I could resolve this was by wiping Internal SD, in addition to the other wipes mentioned, and flashing the ROM again.

find stock kernel, flash the roms you want and flash the stock kernel after and see if you boot

Biker1 said:
When I was flashing ROMs w/Aroma using TWRP 2.5.0.2, I would sometimes get Samsung boot screen freezes. The only way I could resolve this was by wiping Internal SD, in addition to the other wipes mentioned, and flashing the ROM again.
Click to expand...
Click to collapse
I also tried your suggestion exactly what you stated. Restored to stock. Rooted successfully. Wiped all 4 things + format /sdcard (internal SD). ROM flash stated success. Still NO good. Still Stuck Samsung S4 logo.
Is there any custom ROMs I can flash using odin?

anothersaddream said:
I also tried your suggestion exactly what you stated. Restored to stock. Rooted successfully. Wiped all 4 things + format /sdcard (internal SD). ROM flash stated success. Still NO good. Still Stuck Samsung S4 logo.
Is there any custom ROMs I can flash using odin?
Click to expand...
Click to collapse
ODIN Samsung Stock Firmware.
Boot.
ODIN Custom Recovery.
(I use PhilZ Touch Recovery. Flashes ROMs flawlessly )
Boot.
Flash custom ROM afterwards.
If ROM doesn't have Root, then Root with CF-AUTO-ROOT by Chainfire via ODIN prior to installing Custom Recovery.
Then flash custom ROM.

Biker1 said:
ODIN Samsung Stock Firmware.
Boot.
ODIN Custom Recovery.
(I use PhilZ Touch Recovery. Flashes ROMs flawlessly )
Boot.
Flash custom ROM afterwards.
If ROM doesn't have Root, then Root with CF-AUTO-ROOT by Chainfire via ODIN prior to installing Custom Recovery.
Then flash custom ROM.
Click to expand...
Click to collapse
I did as you stated. I love Philz Touch recovery UI. Very nice. Unfortunately, did not work as well. It stated successfully. I tried 2 rom, Infamous S4 v.2.5 and also the VirginROM v2.3.1. Both stated successful flashed but would not boot into the phone desktop. Stuck for over 10 minutes on black and white "Samsung Galaxy S4" logo.
I will send you a nice Starbucks gift card if anyone can fix this problem.

anothersaddream said:
I did as you stated. I love Philz Touch recovery UI. Very nice. Unfortunately, did not work as well. It stated successfully. I tried 2 rom, Infamous S4 v.2.5 and also the VirginROM v2.3.1. Both stated successful flashed but would not boot into the phone desktop. Stuck for over 10 minutes on black and white "Samsung Galaxy S4" logo.
I will send you a nice Starbucks gift card if anyone can fix this problem.
Click to expand...
Click to collapse
I have no idea why it ain't working for you.
On the plus side, I don't know everything
If you ODINd Stock.
ODINd Recovery.
Did a Md5 Checksum match between the ROM file and your Download.
Wiped Internal SD.
Flashed the ROM......
and you're still having issues.......
I'm at a loss....
Try again is my only suggestion, and insure the steps taken are correct, including ODINing the proper files for your device.
Check & Double check
Including making sure you have a good usb cable, which sometimes can work and sometimes not....

If you haven't, try flashing from internal sd card. Maybe remove th external sd card just in case.

[Q] Bricked GSII SGH-989?

I have a T-Mobile SGH-T989 (Galaxy S2), and for a while I had an ICS darkside ROM on it with CWM 5.0.2.4. This evening, though, I decided to upgrade to an Android KitKat ROM (Beanstalk). I first upgraded CWM to the latest version, and then flashed the ROM. Everything seems to have flashed correctly, and I get the Beanstalk splashscreen, but it never seems to go any further than that. It's hung (for around 30mins) on the Beanstalk splash screen with the beanstalk and rain.
When I go into CWM, I can re-flash just fine, but when I try to do a full wipe or a cache wipe, it also gets hung (I eventually rebooted after about a 10 minute cache wipe attempt). It says that it can't open /cache/recovery/last_install, and that the cache file system is read-only. I also attempted to use the super wipe/cache wipe tools here: http://forum.xda-developers.com/showthread.php?t=2235141&nocache=1 but they also hung.
I'm wondering what the best course of action is at this point? I have a full backup, but since it was made with the previous version of CWM, it also appears to not be working.
Thanks,
~j

jwir3 said:
I have a T-Mobile SGH-T989 (Galaxy S2), and for a while I had an ICS darkside ROM on it with CWM 5.0.2.4. This evening, though, I decided to upgrade to an Android KitKat ROM (Beanstalk). I first upgraded CWM to the latest version, and then flashed the ROM. Everything seems to have flashed correctly, and I get the Beanstalk splashscreen, but it never seems to go any further than that. It's hung (for around 30mins) on the Beanstalk splash screen with the beanstalk and rain.
When I go into CWM, I can re-flash just fine, but when I try to do a full wipe or a cache wipe, it also gets hung (I eventually rebooted after about a 10 minute cache wipe attempt). It says that it can't open /cache/recovery/last_install, and that the cache file system is read-only. I also attempted to use the super wipe/cache wipe tools here: http://forum.xda-developers.com/showthread.php?t=2235141&nocache=1 but they also hung.
I'm wondering what the best course of action is at this point? I have a full backup, but since it was made with the previous version of CWM, it also appears to not be working.
Thanks,
~j
Click to expand...
Click to collapse
When all fails always use ODIN, if you know what you're doing. IDK which ROMs here are flashable via ODIN but use any you can find in the dev section in which somebody has uploaded a flashable .tar version (usually it will be rooted stock). If that doesn't save you, you have big trouble.
Also you should still be able to restore backups between different CWM versions, so yeah there is potentially something wrong with your phone.