Develop Bugs

[Q] Can't boot past boot screen after botched ICS theme transition installation.

I was running Starburst v1.9 and saw a thread on Themes & Apps with ICS transitions. I downloaded both just in case (ICS Transitions & Revert back to stock). I went into Root Explorer and checked my Clockwork/Backup and saw that I had a backup in there. I booted into Recovery and flashed the theme transitions for ICS zip and thus problem began.
I then went to restore to restore the backup and it seems like that file was corrupted because it wouldn't restore. I ended up flashing the revert zip file and wiping my rom. It doesn't boot but I can still get into recovery. I believe that the issue is that the theme was made for the v1.9.5 and I had v1.9 of Starburst.
I was messing around with it and I was able to boot back in and click on the Android to set it up. After a while the phone will go crazy and the screen will flicker on and off. The buttons at the bottom became useless. How can I recover from this.
** I used my friend's Sensation and downloaded v.1.9.5 and threw it on my SD. I booted into Recovery and flashed the ROM and it still won't boot up. Any suggestions? **
The phone booting up I think was a luck of the draw thing. Since then the phone has not been able to boot into the actual ROM. I've been without a phone since yesterday and I'm planning on going into the Sprint store and getting it swapped.

Did you wipe system, data, cache, and dalvik?
THEN reflash the rom?

Yes. I was a flashaholic on my Evo.
I notice another thread in q&a with people the same issue as mines. I'm lost and haven't had my phone working for two days now.
Here's what I did:
Delete system, wipe factory reset, cache and dalvik, flashed ROM.
Could it be kernel related? I'm confused. I have a wedding tomorrow and this couldn't have happened at a worse time. Coincidentally something happened on my At&t dumb phone so I'm phoneless.

stupid suggestion...is your battery low?
with the evo it would see corrupted if the battery was low. may not apply, but hey its a shot.
if you cant figure out, theres always Odin to cure your issues

ReDL the ROM and reflash. Try mounting USB storage while in recovery. Alternatively, Odin the stock .tar for a full refresh.

If you've already retired reflashing I'd go with odin back to stock
Sent from my SPH-D710 using xda premium

here is the link for a format all then you can try and flash a rom again if you like. If not I would do like previously suggested and flash return to stock in Odin- link here

playya said:
here is the link for a format all then you can try and flash a rom again if you like. If not I would do like previously suggested and flash return to stock in Odin- link here
Click to expand...
Click to collapse
Awesome. The wedding made me forget about my phone but now that it's over I'm missing it.
I will flash to stock and re-root.
Sent from my Nexus S 4G using XDA App

Can't seem to install custom ROMs

Sorry for the somewhat long post, but I've tried a lot to solve this problem. So the other day, I tried installing the Paradox II Love ROM from Juggernaut 5.0 and followed its instructions exactly. I used both the Super Wipe and Kernel Cleanser and the steps that followed. After my phone rebooted, it would load the new kernel and then immediately reboot into recovery mode.
So after failing to work a few more times, I decided to try Darkside Digital Warfare. Again, the kernel would load, but then this time, it would just get stuck on the kernel logo. I waited over 20 minutes, and it did nothing. In the thread for the ROM, apparently a few people have had the same issue. A possible solution was installing a different kernel. I tried several, and it continued to have the same problem.
So I decided to use my nandroid backup, which didn't work. Something about an md5 mismatch I think. So I decided to try and reflash Juggernaut 5, and that ROM now wouldn't load. So I try GBaxeEX which I was using before Juggernaut and that just reboots to recovery.
So far, all that works are stock ROMs or ROMs that are close to stock. Right now, I'm using a debloated ROM and have no problems. I've found I can load custom kernels, so I'm using Darkside Xv1.
I've tried using Odin to go back to stock before flashing new custom ROMs, I've tried manually wiping system data in recovery before flashing, I've tried not using the Super Wipe, and I've tried redownloading the ROMs in case of an error or incomplete download. I've also tried initiating the install from ROM Manager. My phone just refuses to accept custom ROMs anymore.
Any advice is appreciated. I've been flashing ROMs since the Vibrant first came out and have never had a problem like this.

Try running tdj super wipe. Then flash your rom of choice. I highly recommend darkside rom!
Sent from my SGH-T989 using xda premium

GreggoryD502 said:
Try running tdj super wipe. Then flash your rom of choice. I highly recommend darkside rom!
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Like I said in my original post, I did try the Super Wipe and have tried it multiple times since. I've also tried using the Super Wipe and formatting system data in recovery.

segata said:
Like I said in my original post, I did try the Super Wipe and have tried it multiple times since. I've also tried using the Super Wipe and formatting system data in recovery.
Click to expand...
Click to collapse
You may have to ODIN back to stock then re-root. After that get CWM and start flashing again. This should work.
What I learned from my Vibrant days. If everything else fails, Odin Stock and start all over again.
BTW. Small hint. Use ROM Manager to create a .zip for CWM, rename it update.zip. Doing this will allow you to go directly from Stock recovery (volume +/- and power) to flashing without Rooting the device. Just load stock recovery and install the created update.zip by selecting Install Update. First flash of update.zip will go back to Stock recovery, second will load CWM.

Raistline said:
You may have to ODIN back to stock then re-root. After that get CWM and start flashing again. This should work.
What I learned from my Vibrant days. If everything else fails, Odin Stock and start all over again.
BTW. Small hint. Use ROM Manager to create a .zip for CWM, rename it update.zip. Doing this will allow you to go directly from Stock recovery (volume +/- and power) to flashing without Rooting the device. Just load stock recovery and install the created update.zip by selecting Install Update. First flash of update.zip will go back to Stock recovery, second will load CWM.
Click to expand...
Click to collapse
Again, this was something I tried multiple times and was mentioned in my original post. I was able to fix the md5 mismatch error thanks to a few other XDA threads, so I've restored a previous backup for my Juggernaut 5.0 setup.

Update: Since restoring a previous backup, I've successfully flashed Darkside Digital Warfare. However, Paradox II still refuses to install.

Going back to Stock problems

Hi, I've decided to go back to stock so I flashed the 2.3.6 MD5 file via odin. The flash was successful but when the phone booted up, all i get is FCs and cannot go any further. tried flashing 2.3.5 and 4.0.3 and both ended up with the same results.
does anybody know whats going on?

Not sure what you did wrong or why it's acting up, but odin this one instead
http://forum.xda-developers.com/showthread.php?t=1705565
It's the official ICS and I Odin back to stock using this yesterday and haven't had any problems with this.
If you want to go back to GB let me know and I'll post some files I have for that, but I'm not sure why you would want to.
Powered by the SGSII soon the SGSIII

Finally I got it to work. I flashed the stock ROM and flashed clockwork recovery immediately afterwards. Then I wiped the data, cache, davlik cache, and fixed permissions.
Sent from my SGH-T989 using Tapatalk 2

[Q] Cannot flash roms anymore

I can no longer flash a new rom and boot up successfully. It goes through the entire flash process correctly, but then boots straight into CWM when i restart. I have tried to flashing back to stock via odin, then starting fresh, did a factory reset from standard recovery. I have flashed MANY times prior with no problems. The only way I can get it to boot is when I restore with Odin. Am I missing something? Any help would be greatly appreciated.

ed20910 said:
I can no longer flash a new rom and boot up successfully. It goes through the entire flash process correctly, but then boots straight into CWM when i restart. I have tried to flashing back to stock via odin, then starting fresh, did a factory reset from standard recovery. I have flashed MANY times prior with no problems. The only way I can get it to boot is when I restore with Odin. Am I missing something? Any help would be greatly appreciated.
Click to expand...
Click to collapse
Did you try twrp cwm is a broken recovery and did you flash another carriers rom
Sent from my ADR6300 using Xparent Red Tapatalk 2

I tried TWRP and same issue. Boots straight into whatever recovery I have installed. I have never had a problem with CWM before. I was running Serenity 1.1, noticed my GPS wasn't working and reverted back to stock and did factory reset. Ever since, not able to flash. I had flashed a couple of the Sprint leak roms prior to Serenity with no issues.

ed20910 said:
I tried TWRP and same issue. Boots straight into whatever recovery I have installed. I have never had a problem with CWM before. I was running Serenity 1.1, noticed my GPS wasn't working and reverted back to stock and did factory reset. Ever since, not able to flash. I had flashed a couple of the Sprint leak roms prior to Serenity with no issues.
Click to expand...
Click to collapse
flash a stock rom using odin should unroot your phone giving you stock recovery again

amzi said:
flash a stock rom using odin should unroot your phone giving you stock recovery again
Click to expand...
Click to collapse
I don't want stock recovery. I want to be able to flash again. I tried using TWRP after fresh install but still have same issue. Either I boot straight into recovery after flashing rom, or it just sits on the SGS III logo. The only thing I can flash is back to stock either already rooted or plain stock. I am at a loss. I have been flashing with no problems since august and have no idea what the problem can be. I have even tried redownloading the roms.

ed20910 said:
I don't want stock recovery. I want to be able to flash again. I tried using TWRP after fresh install but still have same issue. Either I boot straight into recovery after flashing rom, or it just sits on the SGS III logo. The only thing I can flash is back to stock either already rooted or plain stock. I am at a loss. I have been flashing with no problems since august and have no idea what the problem can be. I have even tried redownloading the roms.
Click to expand...
Click to collapse
Well fortunately for you rooting the GS3 is very easy, so do as he says, Odin to stock, re-root and flash. If you are seriously at a loss because you don't want to go through the trouble to be able to flash and root again then I suggest searching forums for someone who might have the same problem.

That's the problem, after flashing back to stock, and re rooting, I have the problem. I cannot flash anything using CWM or TWRP anymore. I am currently rooted and stock. No recovery installed. Not sure what happened and why recoveries are not working. I don't mind flashing back to stock.

Grab a stock image from sammobile.com and try that.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

Evidently fifth time is a charm. Restored back to rooted stock, reinstalled apps, twrp and successfully made a back up and restored. Was able to flash Ariel. Not sure what the difference was but back up and running now. Thanks for all the suggestions.

[Q] Stuck samsung screen even after odin stock

Hey guys hopefully you can help me. I was rooted for like 3 or 4 months now and have had not many problems or not anything I couldn't fix my self. My phone gets stuck on the Samsung Galaxy s4 screen anytime I reboot. I have tried different roms, different kernels, I even odin back to stock. I was using TWRP 6.0 then reverted back to TWRP 5.2 to see if that was causing the problem. Still have problems. I am going to re download the stock tar to see if it was a bad download but Odin checks the md5 and says it was good. Odin says passed every time also. Odin version is 3.07.
I get a error before and when trying to wipe dalvic cashe. I can wipe reg cash no problem. I think my phone is not mounting the internal storage when it reboots. I could be way off but need help asap. If I format super wipe with twrp then restart twrp and then factory reset I can install or restore a rom some times but still cant restart the phone. Any hope would be greatly appreciated.

EDIT
I wanted to edit my previous commet. LiquidSmooth seems to be running fine. So TW roms and GE roms **** up on my phone when I restart. so is it the internal systems when I have TW roms. I think it has something to do with partictions messing around maybe.
I like TW roms and want to continue to use them... Thank you

Get into recovery and do a factory reset, it is a must after you odin back to stock. Make sure you are also using a tmo kernel.
Thanks you

I got this problem a few days ago and found some topic including this one. You should check it out.
Well, what worked for me was Odin to stock firmware, root again, install recovery then custom rom. Now it's working fine. Try to downloading it again to see if it works. I downloaded mine from here, rooted and recovery it using this one.

TheAxman said:
Get into recovery and do a factory reset, it is a must after you odin back to stock. Make sure you are also using a tmo kernel.
Thanks you
Click to expand...
Click to collapse
+1 to what he said. I bet if you go into the stock recovery after odin flashing it will say something like cannot mount /data partition. Factory reset there, and it should fix that and make it mountable. (Its important to use the stock recovery factory reset after the odin, don't flash a custom recovery right after flashing)

This was incredibly helpful. I had the same issue. Thank you.
This is also applicable to the Verizon Wireless model.