Database Users

Need Help - stuck in bootloop and CWM hangs

This is what I did:
1) Made a backup
2) Wiped cache partition/davlik
3) FLashed CM nightly 111
4) Flashed wildmonks kernel 2.6.38.8
5) Reboot
Everything was fine, the phone booted up. Home was defaulted in landscape for some reason, so I adjusted the settings but everything remained in landscape, so I rebooted. The phone wouldn't reboot though. It stuck in bootloop. I tried to go into CWM to revert to a backup. I could get the main menu of CWM, but any action would just make it hang. So no CWM and am stuck in bootloop (after it originally booted fine!).
Not sure how best to proceed here, or what the problem is. Help! Thanks.

That's not enough info for this thread--we don't know your history
What version CWM? Don't use 3.+
Recommend Amon_Ra 2.2.1
Is this the first time you flashed this rom?
What did you flash it over?
Either way if problems persist:
Wipe system 3X and data/caches 5
If no luck--reformat card with sdformatter outside of phone and rewipe as mentioned above
Also, try a new download--did you check md5?
You can also try an earlier nightly or an RC release
Ken

Also, this is the wrong thread
You will be moved to the Q&A section
And try the CM7 thread in Android Development section
Ken

rugmankc said:
That's not enough info for this thread--we don't know your history
What version CWM? Don't use 3.+
Recommend Amon_Ra 2.2.1
Is this the first time you flashed this rom?
What did you flash it over?
Either way if problems persist:
Wipe system 3X and data/caches 5
If no luck--reformat card with sdformatter outside of phone and rewipe as mentioned above
Also, try a new download--did you check md5?
You can also try an earlier nightly or an RC release
Ken
Click to expand...
Click to collapse
CWM is 3.+.
I was coming from an earlier nightly, 80-something.
I can't wipe or flash because I can't get CWM to do anything. I'll try reformatting card later. Thanks.

Not sure about your bootloop
I usually do the 3 finger:
Hold down pwr/vol-/trackball at same time and it takes me to the bootloader screen with the 3 androids then I can get into recovery. It may take awhile to boot into bootloader screen. So, don't release buttons too soon.
From there I wipe all including system 3 to 5 times and do a nandroid
Ken

Do card as I suggested
Probably too many nightlies in between not to do fresh flash and full wipe
Definetly go back to a pre 3. CWM
I had good luck with 2.5.1.4--can flash it from Rom Manager

rugmankc said:
Not sure about your bootloop
I usually do the 3 finger:
Hold down pwr/vol-/trackball at same time and it takes me to the bootloader screen with the 3 androids then I can get into recovery. It may take awhile to boot into bootloader screen. So, don't release buttons too soon.
From there I wipe all including system 3 to 5 times and do a nandroid
Ken
Click to expand...
Click to collapse
I can get into bootloader fine. CWM is just unresponsive. Trying to format SD right now. Thanks for the input!

rugmankc said:
Do card as I suggested
Probably too many nightlies in between not to do fresh flash and full wipe
Definetly go back to a pre 3. CWM
I had good luck with 2.5.1.4--can flash it from Rom Manager
Click to expand...
Click to collapse
Re-formatting SD card didn't accomplish anything. Think I'll try next to re-flash a recovery (Amon-RA) via fastboot and see what happens. Ack.

Good idea--I didn't know if you had fastboot setup--so didn't mention it

rugmankc said:
Good idea--I didn't know if you had fastboot setup--so didn't mention it
Click to expand...
Click to collapse
Didn't have fastboot set up, but once I could shake the family I threw myself in. I only used fastboot once before, a year and a half ago when I unlocked and rooted my phone.
Anyhow, re-flashing a recovery image did the trick. Then I was able to restore a nandroid backup and move on from there. Not sure why the universe went awry, but hey, live and learn. Always backup kids.

Glad you got it.

HELP! Odin and Heimdall won't work... Alternative to flash to stock?

First, let me get the formalities out of the way... long time lurker, first time poster. I hope you guys can help me out!
My GS4 semi-bricked while trying to restore my phone from LiquidSmooth ROM . My phone had no MAC address nor IP address after I flashed to LiquidSmooth, so I figured I needed to restore files I may have accidentally deleted.. The phone became stuck on the splash screen so I tried pulling the battery, going into recovery, and clearing cache/dalvik. No luck.
So then I tried to restore using a backup that I had made before flashing, but then it got stuck on the AT&T screen. Tried to clear cache/dalvik, but it didn't work. I thought maybe the back up didn't work because I was flashed into a different ROM, so I downloaded this stock rom by scrosier, and tried again... but to no avail.
Now I want to try flashing the phone back to stock, but I have a early 2008 MacBook running 10.7.5 (Lion). Odin is windows only, and Heimdall doesn't work on my version of OS X (keeps crashing the moment I open it). I thought maybe updating my MacBook to Mountain Lion (10.8) might work, but Mountain Lion is not supported on my Macbook, thus cannot update OS X... and I don't have access to a PC at this moment either.
Is my only option to go out and buy windows and install on bootcamp? Does anyone know if I could flash my phone back to stock using the computer I have now?
Sorry if my post didn't make any sense. I'm in a hurry and I want to fix my phone already! Thanks in advance
EDIT:
I have TWRP 2.5.0.3 on my phone

sebbo1 said:
First, let me get the formalities out of the way... long time lurker, first time poster. I hope you guys can help me out!
My GS4 semi-bricked while trying to restore my phone from LiquidSmooth ROM . My phone had no MAC address nor IP address after I flashed to LiquidSmooth, so I figured I needed to restore files I may have accidentally deleted.. The phone became stuck on the splash screen so I tried pulling the battery, going into recovery, and clearing cache/dalvik. No luck.
So then I tried to restore using a backup that I had made before flashing, but then it got stuck on the AT&T screen. Tried to clear cache/dalvik, but it didn't work. I thought maybe the back up didn't work because I was flashed into a different ROM, so I downloaded this stock rom by scrosier, and tried again... but to no avail.
Now I want to try flashing the phone back to stock, but I have a early 2008 MacBook running 10.7.5 (Lion). Odin is windows only, and Heimdall doesn't work on my version of OS X (keeps crashing the moment I open it). I thought maybe updating my MacBook to Mountain Lion (10.8) might work, but Mountain Lion is not supported on my Macbook, thus cannot update OS X... and I don't have access to a PC at this moment either.
Is my only option to go out and buy windows and install on bootcamp? Does anyone know if I could flash my phone back to stock using the computer I have now?
Sorry if my post didn't make any sense. I'm in a hurry and I want to fix my phone already! Thanks in advance
Click to expand...
Click to collapse
If you are able to access recovery then do this:
Put Liquid Smooth and its gapps on the external card using a card reader
Go into recovery, factory reset, wipe both caches, format /system, flash the rom and gapps, reboot

Colonel Sanders said:
If you are able to access recovery then do this:
Put Liquid Smooth and its gapps on the external card using a card reader
Go into recovery, factory reset, wipe both caches, format /system, flash the rom and gapps, reboot
Click to expand...
Click to collapse
I actually tried to reflash Liquid Smooth and wiped cache / factory reset, but once it reboots, a screen pops up that says "Android is updating" and updates 120 files. However, when it finishes, it gives me an error along the lines of "Unfortunately... something something," and instantly reboots. Then it hangs on the Liquid Smooth splash screen. Couldn't get a good look at what the message said because it happens so quickly.

sebbo1 said:
I actually tried to reflash Liquid Smooth and wiped cache / factory reset, but once it reboots, a screen pops up that says "Android is updating" and updates 120 files. However, when it finishes, it gives me an error along the lines of "Unfortunately... something something," and instantly reboots. Then it hangs on the Liquid Smooth splash screen. Couldn't get a good look at what the message said because it happens so quickly.
Click to expand...
Click to collapse
Then I suggest you flash a different ROM. Try out Slim. Liquid Smooth is just a Slim ripoff.
Put Slim and the Addons on the SD, and flash it like you would when changing ROMs. A clean wipe.

Colonel Sanders said:
Then I suggest you flash a different ROM. Try out Slim. Liquid Smooth is just a Slim ripoff.
Put Slim and the Addons on the SD, and flash it like you would when changing ROMs. A clean wipe.
Click to expand...
Click to collapse
I'll give that a shot. Do you recommend the new 4.3 Google Edition Slim Rom?

sebbo1 said:
I'll give that a shot. Do you recommend the new 4.3 Google Edition Slim Rom?
Click to expand...
Click to collapse
That's not Slim, he just put Slim because it's slimmed down. I haven't personally tried it. I'm a tester for SlimRoms, so thats all I ever run. Test builds. It does look nice though, but it won't have near the customization of Slim.

Colonel Sanders said:
That's not Slim, he just put Slim because it's slimmed down. I haven't personally tried it. I'm a tester for SlimRoms, so thats all I ever run. Test builds. It does look nice though, but it won't have near the customization of Slim.
Click to expand...
Click to collapse
Are you talking about slimroms.net? If you are, which addons do I download?
EDIT: nevermind. I downloaded the AIO (all in one)

sebbo1 said:
Are you talking about slimroms.net? If you are, which addons do I download?
Click to expand...
Click to collapse
Yes, slimroms.net
It just depends on whether or not you want all of the Google apps typically in a regular gapps pkg, or a stripped down version. I use the AIO_Addons, or you could get the Aroma, so you can pick and choose. The Slim_gapps is a stripped down version.

Colonel Sanders said:
Yes, slimroms.net
It just depends on whether or not you want all of the Google apps typically in a regular gapps pkg, or a stripped down version. I use the AIO_Addons, or you could get the Aroma, so you can pick and choose. The Slim_gapps is a stripped down version.
Click to expand...
Click to collapse
One last question before I flash the rom. Is it loki'd? I don't see the answer on the website

sebbo1 said:
One last question before I flash the rom. Is it loki'd? I don't see the answer on the website
Click to expand...
Click to collapse
Last time I flashed a weekly, it wasn't loki'd, but that was a while back. I'm running test builds from black_jck, and build my own sometimes. I mentioned it to him that the weekly wasn't loki'd but that was a while back, so I can't speak for them now. The official builds are. If you're going to flash the weekly, flash loki_doki just to be safe.

Colonel Sanders said:
Last time I flashed a weekly, it wasn't loki'd, but that was a while back. I'm running test builds from black_jck, and build my own sometimes. I mentioned it to him that the weekly wasn't loki'd but that was a while back, so I can't speak for them now. The official builds are. If you're going to flash the weekly, flash loki_doki just to be safe.
Click to expand...
Click to collapse
Alright, so I flashed Slim and the AIO_addons, and rebooted the phone.
Once it was rebooting, the screen i mentioned earlier popped up, that said "Android is updating" and went through 109 files. When it was done, an error popped up quickly, saying that "Unfortunately..." and I couldn't read the rest before the phone rebooted. I let the screen hang for about 10 minutes, pulled the battery, cleared cache and dalvik, and rebooted again. No luck.
I think my best option now would be to return to stock, but I can't using my macbook. So my original question still stands.. How can I return to stock without using Odin and Heimdall?

sebbo1 said:
Alright, so I flashed Slim and the AIO_addons, and rebooted the phone.
Once it was rebooting, the screen i mentioned earlier popped up, that said "Android is updating" and went through 109 files. When it was done, an error popped up quickly, saying that "Unfortunately..." and I couldn't read the rest before the phone rebooted. I let the screen hang for about 10 minutes, pulled the battery, cleared cache and dalvik, and rebooted again. No luck.
I think my best option now would be to return to stock, but I can't using my macbook. So my original question still stands.. How can I return to stock without using Odin and Heimdall?
Click to expand...
Click to collapse
I would say so myself, Odin back to stock, but since you have a mac and I'm not sure if Heimdall support the S4 try this:
Factory Reset
Wipe Cache
Wipe Dalvik
Format /system
Format /data
Format /internal (If CWM-based recovery)
Flash ROM, addons, reboot

sebbo1 said:
Alright, so I flashed Slim and the AIO_addons, and rebooted the phone.
Once it was rebooting, the screen i mentioned earlier popped up, that said "Android is updating" and went through 109 files. When it was done, an error popped up quickly, saying that "Unfortunately..." and I couldn't read the rest before the phone rebooted. I let the screen hang for about 10 minutes, pulled the battery, cleared cache and dalvik, and rebooted again. No luck.
I think my best option now would be to return to stock, but I can't using my macbook. So my original question still stands.. How can I return to stock without using Odin and Heimdall?
Click to expand...
Click to collapse
I forgot to mention, the red LED light flashes every once in a while while on the Slim screen

sebbo1 said:
I forgot to mention, the red LED light flashes every once in a while while on the Slim screen
Click to expand...
Click to collapse
That means the battery is low... Charge it up some... Check your PM for my gmail if you need some help, posting back and forth can take a while.

Well thanks for all your help! Happy that my phone is working again without having to flash to stock.
Phone booted normally once I switched to SlimBean. Much snappier and responsive than LiquidSmooth. Fixed the problems I was having with WiFi also.
Still haven't figured out a way to flash to stock using OS X Lion since Heimdall doesn't work and Odin is Windows only... Mods please lock or close thread because I don't need help anymore

sebbo1 said:
Well thanks for all your help! Happy that my phone is working again without having to flash to stock.
Phone booted normally once I switched to SlimBean. Much snappier and responsive than LiquidSmooth. Fixed the problems I was having with WiFi also.
Still haven't figured out a way to flash to stock using OS X Lion since Heimdall doesn't work and Odin is Windows only... Mods please lock or close thread because I don't need help anymore
Click to expand...
Click to collapse
Glad you got it going man, and enjoy Slim, it's hands down the best ROM there is if you prefer minimal with tons of customization options.

Phone stuck on "Samsung - Custom" screen after creating TWRP backup. Help please?

Phone stuck on "Samsung - Custom" screen after creating TWRP backup. Help please?
I have an ATT S4, that has had CM 10.1 on it running flawlessly pretty much since nightlies started to get released. Decided to try going back to some TW based ROMs. Running the latest nightly, loaded up TWRP, created a backup, as I usually do before swapping roms. Created the backup fine, now it won't boot, it just sits at the Samsung screen with the lock and Custom message. Wiped cache\dalvic, even tried restoring from the backup I just created. Nothing. Tried it with the phone plugged into the computer and without being plugged in (I think I recall it being plugged into USB could cause issues in the past), and still nada. Tried pulling the battery and rebooting about 10 times. Can get into recovery and odin mode perfectly fine still. Any suggestions or ideas? Thanks

Simonzi said:
I have an ATT S4, that has had CM 10.1 on it running flawlessly pretty much since nightlies started to get released. Decided to try going back to some TW based ROMs. Running the latest nightly, loaded up TWRP, created a backup, as I usually do before swapping roms. Created the backup fine, now it won't boot, it just sits at the Samsung screen with the lock and Custom message. Wiped cache\dalvic, even tried restoring from the backup I just created. Nothing. Tried it with the phone plugged into the computer and without being plugged in (I think I recall it being plugged into USB could cause issues in the past), and still nada. Tried pulling the battery and rebooting about 10 times. Can get into recovery and odin mode perfectly fine still. Any suggestions or ideas? Thanks
Click to expand...
Click to collapse
There are no less than a dozen similar threads about similar problems already. Have you looked at those threads for a possible solution yet? You can find them by using the search function or better yet just doing a visual search of the first few pages of the "General" and "Q&A" sections. Good luck.

Sounds like a ROM and kernel issue. Try flashing a ROM with a loki'd kernel.
Tylorw1
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4

Tylorw1 said:
Sounds like a ROM and kernel issue. Try flashing a ROM with a loki'd kernel.
Tylorw1
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
I don't see how that could be the case. I didn't flash anything. I just loaded TWRP, created a backup, and rebooted my phone. No ROM\kernel change. Nothing more than creating a backup in TWRP.
scott14719 said:
There are no less than a dozen similar threads about similar problems already. Have you looked at those threads for a possible solution yet? You can find them by using the search function or better yet just doing a visual search of the first few pages of the "General" and "Q&A" sections. Good luck.
Click to expand...
Click to collapse
I tried searching, the closest one I could find on the first few pages was this one. I just didn't see any specific to my situation because nothing was flashed. Like my response to Tylorw1, all I did was boot into recovery, create a backup, and reboot my phone. Didn't flash a ROM, change a kernel, format anything, etc...

I has this same problem... It happened after every single reboot after flashing various ROMs or anything.. I gave up and went back to CWM and haven't had the problem since :good:
Sent from my SGH-I337 using xda app-developers app

Simonzi said:
I have an ATT S4, that has had CM 10.1 on it running flawlessly pretty much since nightlies started to get released. Decided to try going back to some TW based ROMs. Running the latest nightly, loaded up TWRP, created a backup, as I usually do before swapping roms. Created the backup fine, now it won't boot, it just sits at the Samsung screen with the lock and Custom message. Wiped cache\dalvic, even tried restoring from the backup I just created. Nothing. Tried it with the phone plugged into the computer and without being plugged in (I think I recall it being plugged into USB could cause issues in the past), and still nada. Tried pulling the battery and rebooting about 10 times. Can get into recovery and odin mode perfectly fine still. Any suggestions or ideas? Thanks
Click to expand...
Click to collapse
what version of twrp? if it is 2.6.?.? then get off of it, also, what I did was pull battery for 3min, it booted fine....go back to early version of twrp...

STVERDI said:
I has this same problem... It happened after every single reboot after flashing various ROMs or anything.. I gave up and went back to CWM and haven't had the problem since :good:
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I've wanted to go back to CWM. That's what I had on my S3. Only thing stopping me, is all my nandroid backups for my S4 are done with TWRP, and I don't want to run into a situation where I need them, and them not being compatible
TheAxman said:
what version of twrp? if it is 2.6.?.? then get off of it, also, what I did was pull battery for 3min, it booted fine....go back to early version of twrp...
Click to expand...
Click to collapse
Nope, still on 2.5.0.2. Finally, after a third complete wipe/format and restore from the back I had created (the one that started the whole issue), it works fine. Such a huge pain in the ass.

a user had to boot back into twrp and wipe data/factory reset yesterday to fix this issue.

Simonzi said:
I've wanted to go back to CWM. That's what I had on my S3. Only thing stopping me, is all my nandroid backups for my S4 are done with TWRP, and I don't want to run into a situation where I need them, and them not being compatible
Nope, still on 2.5.0.2. Finally, after a third complete wipe/format and restore from the back I had created (the one that started the whole issue), it works fine. Such a huge pain in the ass.
Click to expand...
Click to collapse
And you have to be ****ing kidding me. I rebooted into recovery while typing my initial response, just to verify I was still on the 2.5.x.x TWRP. Booted up TWRP, verified that, choose "Reboot System", and same thing. Back to sitting at the Samsung screen. Nandroid backups or not, ditching TWRP as soon as I get it able to boot back up.

Even worse off now than when I started. After my last post, where my phone was doing the same "stuck on Samsung logo" thing, just from booting into TWRP, I decided to swap to a different recovery. Searched for "switch from TWRP to CWM", and found my own post I had made a few months ago, but never went through.
Following those instructions now, I decided on the PhilZ CWM. Head over to that thread, grab the loki'd zip, load up TWRP, and flash the zip. Now I can't even boot into recovery!! It just freezes on the Samsung screen with the blue "recovery booting" text.
Can still get into download mode, so I tried using ODIN to flash PhilZ jflteatt.tar.md5 file, and it fails.
At this point, waiting for the stock 1.6 firmware package to download, so I can just ODIN that.
If anyone has any other suggestions though, they'd be great. Have an hour to try while waiting for that to download

somebody had mentioned this...
http://forum.xda-developers.com/showpost.php?p=44629460&postcount=8
make sure you have the correct firmware and proceed as you are. likely your best bet.

Simonzi said:
Even worse off now than when I started. After my last post, where my phone was doing the same "stuck on Samsung logo" thing, just from booting into TWRP, I decided to swap to a different recovery. Searched for "switch from TWRP to CWM", and found my own post I had made a few months ago, but never went through.
Following those instructions now, I decided on the PhilZ CWM. Head over to that thread, grab the loki'd zip, load up TWRP, and flash the zip. Now I can't even boot into recovery!! It just freezes on the Samsung screen with the blue "recovery booting" text.
Can still get into download mode, so I tried using ODIN to flash PhilZ jflteatt.tar.md5 file, and it fails.
At this point, waiting for the stock 1.6 firmware package to download, so I can just ODIN that.
If anyone has any other suggestions though, they'd be great. Have an hour to try while waiting for that to download
Click to expand...
Click to collapse
Stock 1.6 firmware package?
Make sure you get the correct firmware? Go to SamMobile and get the stock firmware from there or go to Adam Outlers "Stock firmware ODIN" thread in the General section (the AMDL firmware link is in that thread you just have to look for it).

scott14719 said:
Stock 1.6 firmware package?
Make sure you get the correct firmware? Go to SamMobile and get the stock firmware from there or go to Adam Outlers "Stock firmware ODIN" thread in the General section (the AMDL firmware link is in that thread you just have to look for it).
Click to expand...
Click to collapse
Yeah, I meant 1.6gb firmware package. Just forgot the "gb". That's what I'm currently downloading, but trying to recover it with Kies while waiting.

I would like to report I had the same problem.
After changing roms and making a nandroid, and then deciding to switch roms again, I ran into the stuck at Samsung Custom with a lock boot screen. Most roms would boot up once, but a restart or power down would lead to being stuck. I was flashing through TWRP.
I went into TWRP and flashed OUDHS recovery which overrode TWRP and wiped/flashed through OUDHS a new rom.
Problem solved.

S3 at&t stuck in TWRP booting screen.
xBeerdroiDx said:
a user had to boot back into twrp and wipe data/factory reset yesterday to fix this issue.
Click to expand...
Click to collapse
Im new to custom roms, I pressed ok for an update on my phone, after the update was complete my phone shut off and booted into TWRP and now I can't get back to my android screen nor make calls etc. HELPPPPPPPP PLEASSSSSEE I have been trying to fix my phone since july and I have been using this cheap phone that don't even get internet. I have an S3 1747 at&t

Lnjames said:
Im new to custom roms, I pressed ok for an update on my phone, after the update was complete my phone shut off and booted into TWRP and now I can't get back to my android screen nor make calls etc. HELPPPPPPPP PLEASSSSSEE I have been trying to fix my phone since july and I have been using this cheap phone that don't even get internet. I have an S3 1747 at&t
Click to expand...
Click to collapse
Wrong forum. Please go to the s3 section with your question.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

Had this problem just now, solved it by fixing permissions.

I am running an MDL based S4, and screwed the pooch. I was going to wipe the internal storage and made the mistake of doing it through TWRP 2.5. Now, I have the same problem of being stuck on the custom boot screen. I have tried to change from TWRP to OUDHS Recovery, but still boot loops to Custom screen. I have tried fresh installs of 4.2 ROMs and 4.4.2 Google Editions. Do I need to flash via ODIN?
Flame away....I know better than this!!!!
Help would be greatly appreciated.
Sent from my GT-N8013 using Tapatalk 4

[Q] Malladus 1.2.5 stuck at boot.

I've heard ranting and raving about Malladus and I decided to flash it yesterday. It won't take the flash no matter what I do.
I've tried: Flashing 1.2.4, downloading both again to make sure it wasn't a download issue, using different gapps package, using a different lg apps package, using CWM, using TWRP, side-loading... ETC
Bottom line: My phone will not take the ROM. It flashes the LG logo and gets stuck at a black screen where the back-light is on but nothing is displayed on the screen.
I am an experienced flasher and I have no idea what is going on. I am backed up and can get into TWRP to restore so I am all good as far as not being bricked goes but I really want to try out this damn rom.
Any help would be much appreciated. Thanks.

Bump I'm having the same problem, I'm on Verizon.

NBushyy said:
Bump I'm having the same problem, I'm on Verizon.
Click to expand...
Click to collapse
Yeah same here. Verizon. Forgot to mention it.

Still a problem. Bumping.

I am in the boat with you. I thought it was just me.

Same Black Screen issue
Did anyone have any luck resolving this? Ive tried with both twrp and cwm and same issue...?

Same problem on my Verizon model. Using twrp 2.6.3.3. Other roms work fine.

How long have you left it at the black screen? Sometimes a fresh load can take up to 10 minutes.
Also, the rom will work without gapps and lgapps, so try just loading the rom. I know you downloaded twice, but did you check the md5 sum either time?

heleos said:
How long have you left it at the black screen? Sometimes a fresh load can take up to 10 minutes.
Also, the rom will work without gapps and lgapps, so try just loading the rom. I know you downloaded twice, but did you check the md5 sum either time?
Click to expand...
Click to collapse
I left it there for a good 15 minutes. I also had it plugged into my laptop. It kept detecting the phone as plugged in. Seems like it is stuck in a bootloop or something. I also tried installing only the ROM without the gapps and lgapps and had the same result. I also checked the MD5 sum and it matched. (I know I'm kinda hijacking this original post, but I think we are all having the exact same issue)

try this
trackstar1414 said:
I left it there for a good 15 minutes. I also had it plugged into my laptop. It kept detecting the phone as plugged in. Seems like it is stuck in a bootloop or something. I also tried installing only the ROM without the gapps and lgapps and had the same result. I also checked the MD5 sum and it matched. (I know I'm kinda hijacking this original post, but I think we are all having the exact same issue)
Click to expand...
Click to collapse
Can you restore your nandroid and flash say, CleanROM 1.0 or DigitalDream 2.1? OR try this:
1. Hold the power button until the device is OFF.
2. Download LG drivers to the PC (LG VZW_United_WHQL_v2.11.1) and LG mobile support tool (B2CAppSetup).
3. Install these packages.
4. Plug in you USB cable into the phone but not the computer.
5. Hold volume up and insert the USB cable to the PC- the phone should boot to 'download mode'.
6. Open the support tool and click Options>Upgrade Recovery, follow the prompts.
7. At the first prompt indentify your phone using IMEI/ESN, then click OK
8. Let it do its thing, the phone will reboot and most likely have a bunch of error messages and some FC's. Just hit okay to all messages, the phone will settle after 2 minutes or so.
9. Download freegee from market and reflash recovery of your choice.
10. Make sure you have a ROM saved to the SD to flash
11. Use freegee to reboot to recovery
12. Once in recovery you can reflash the ROM as normal.
13. Reboot and Profit!
*$* Or you could go back to Stock and start fresh!
*$* BEFORE ANY FLASH ALWAYS STOP and MAKE A NANDROID BACKUP!
Good Luck and if you get stuck let me know

geosnipe said:
Can you restore your nandroid and flash say, CleanROM 1.0 or DigitalDream 2.1? OR try this:
1. Hold the power button until the device is OFF.
2. Download LG drivers to the PC (LG VZW_United_WHQL_v2.11.1) and LG mobile support tool (B2CAppSetup).
3. Install these packages.
4. Plug in you USB cable into the phone but not the computer.
5. Hold volume up and insert the USB cable to the PC- the phone should boot to 'download mode'.
6. Open the support tool and click Options>Upgrade Recovery, follow the prompts.
7. At the first prompt indentify your phone using IMEI/ESN, then click OK
8. Let it do its thing, the phone will reboot and most likely have a bunch of error messages and some FC's. Just hit okay to all messages, the phone will settle after 2 minutes or so.
9. Download freegee from market and reflash recovery of your choice.
10. Make sure you have a ROM saved to the SD to flash
11. Use freegee to reboot to recovery
12. Once in recovery you can reflash the ROM as normal.
13. Reboot and Profit!
*$* Or you could go back to Stock and start fresh!
*$* BEFORE ANY FLASH ALWAYS STOP and MAKE A NANDROID BACKUP!
Good Luck and if you get stuck let me know
Click to expand...
Click to collapse
I am able to restore my nandroid backup so I'm not completely stuck without a phone. I will try flashing one of the other ROMs and see how it goes now. Thanks for the help so far.

trackstar1414 said:
I am able to restore my nandroid backup so I'm not completely stuck without a phone. I will try flashing one of the other ROMs and see how it goes now. Thanks for the help so far.
Click to expand...
Click to collapse
I was able to install the digital dream rom without any issue. At this point I think its the sequence I did everything. I did the latest ota before installing any Recovery. I used the loki method to install the recovery. In looking at all the roms, it appears that malladus may not be "loki patched" for people already on 12b? Other roms I have tried mention that so thats why I'm speculating this. I am by no means a developer so I might be out in left field on this one. I guess I'll stick with stock or another ROM for now until his next update.
It also looks like people are discussing this on the main ROM forum as well so hopefully it will work in the future.
Thanks again for the help and suggestions.

trackstar1414, say thanks by using the "Thanks' button like this.. keep me informed, CHEERS!

trackstar1414 said:
I was able to install the digital dream rom without any issue. At this point I think its the sequence I did everything. I did the latest ota before installing any Recovery. I used the loki method to install the recovery. In looking at all the roms, it appears that malladus may not be "loki patched" for people already on 12b? Other roms I have tried mention that so thats why I'm speculating this. I am by no means a developer so I might be out in left field on this one. I guess I'll stick with stock or another ROM for now until his next update.
It also looks like people are discussing this on the main ROM forum as well so hopefully it will work in the future.
Thanks again for the help and suggestions.
Click to expand...
Click to collapse
Wanted to share this if you haven't read it..
http://forum.xda-developers.com/showthread.php?t=2449670

I had issues originally and had to flash back to 1.2.3.
What I ended up doing was switching to CWM 6.0.4.4 ( I was using TWRP 2.6.3.3).
His boot skipped the set up wizard as well, which was odd.
His was also the only ROM I ever got stuck on the fastboot screen while using twrp.
Try ( at your own risk obviously) flashing back to an older malladus (wipe all and boot till you get through the set up wizard),
Then back to recovery, do a wipe, without wiping the system partition, Data Cache and Davlik, and flash back to 1.2.5.
I didn't try it on 1.2.5. But that's how I got into 1.2.4.

Srvisg0d said:
I've heard ranting and raving about Malladus and I decided to flash it yesterday. It won't take the flash no matter what I do.
I've tried: Flashing 1.2.4, downloading both again to make sure it wasn't a download issue, using different gapps package, using a different lg apps package, using CWM, using TWRP, side-loading... ETC
Bottom line: My phone will not take the ROM. It flashes the LG logo and gets stuck at a black screen where the back-light is on but nothing is displayed on the screen.
I am an experienced flasher and I have no idea what is going on. I am backed up and can get into TWRP to restore so I am all good as far as not being bricked goes but I really want to try out this damn rom.
Any help would be much appreciated. Thanks.
Click to expand...
Click to collapse
Are you on 12B OTA? If so, that would be your issue. I took the 12B OTA and tried flashing Malladus and got the same issue you have. You can revert your phone to 11A and that should resolve your issue. http://forum.xda-developers.com/showthread.php?t=2448960 it will erase everything on your phone and go back to unroot.

[Q] Help a noob, cannot boot after trying to flash stock rom

So I'm pretty desperate and I apologize if similar info was posted somewhere else. I've been researching several hours but couldn't find anything.
I originally installed CM11 and decided to experiment with a different rom TriForce ROM [TouchWiz]. I put the zip file on my SD card and booted into clockworkmod it gave an error of bad zip. I tried different usb port to transfer the zip, downloaded it multiple times with no result. So I decided to try a different rom Stock_Rooted_Deodexed_MF9_Rom.zip. The installation finished but the phone would not boot.
Recently I flashed the stock rom from odin, it finished successfully but still not boot, Galaxy sreen lights up quickly and that's it.

rmngorelov said:
So I'm pretty desperate and I apologize if similar info was posted somewhere else. I've been researching several hours but couldn't find anything.
I originally installed CM11 and decided to experiment with a different rom TriForce ROM [TouchWiz]. I put the zip file on my SD card and booted into clockworkmod it gave an error of bad zip. I tried different usb port to transfer the zip, downloaded it multiple times with no result. So I decided to try a different rom Stock_Rooted_Deodexed_MF9_Rom.zip. The installation finished but the phone would not boot.
Recently I flashed the stock rom from odin, it finished successfully but still not boot, Galaxy sreen lights up quickly and that's it.
Click to expand...
Click to collapse
Restore from nandroid backup. I hope you made one. Try going into recovery do a factory reset and wipe all cache and data and what not and then install a ROM from Odin.

rmngorelov said:
So I'm pretty desperate and I apologize if similar info was posted somewhere else. I've been researching several hours but couldn't find anything.
I originally installed CM11 and decided to experiment with a different rom TriForce ROM [TouchWiz]. I put the zip file on my SD card and booted into clockworkmod it gave an error of bad zip. I tried different usb port to transfer the zip, downloaded it multiple times with no result. So I decided to try a different rom Stock_Rooted_Deodexed_MF9_Rom.zip. The installation finished but the phone would not boot.
Recently I flashed the stock rom from odin, it finished successfully but still not boot, Galaxy sreen lights up quickly and that's it.
Click to expand...
Click to collapse
Make sure you're using roms for your version of your phone. the MF9 bootloader is really old and probably wont install anymore. My phone did this before and I thought I bricked it, but I kid you not I took the battery out and removed the SIM card and rebooted and it booted up just fine. May not work for you, but I suggest you go back to update stock firmware then try again. If you're using the triband model, there's a post around here somewhere with confirmed roms that wont brick your device. I'm currently using the Google Play Edition Stock ROM and it's working GREAT.
Link for new firmware (NG5 Firmware): https://mega.co.nz/#F!0JdRkIZR!AqqKdbvba_Hpg5VrCmrbPw

i7vSa7vi7y said:
Restore from nandroid backup. I hope you made one. Try going into recovery do a factory reset and wipe all cache and data and what not and then install a ROM from Odin.
Click to expand...
Click to collapse
I restored to this stock ROM before and everything worked well. Currently I can't boot into recovery, Samsung flashes once and that's it, that's why I'm desperate the only thing I can do is boot in to download mode for odin.

silentdeath631 said:
Make sure you're using roms for your version of your phone. the MF9 bootloader is really old and probably wont install anymore. My phone did this before and I thought I bricked it, but I kid you not I took the battery out and removed the SIM card and rebooted and it booted up just fine. May not work for you, but I suggest you go back to update stock firmware then try again. If you're using the triband model, there's a post around here somewhere with confirmed roms that wont brick your device. I'm currently using the Google Play Edition Stock ROM and it's working GREAT.
Link for new firmware (NG5 Firmware):
Click to expand...
Click to collapse
Does it matter that I can't get into recovery to clear the cache first before trying new roms?

silentdeath631 said:
Make sure you're using roms for your version of your phone. the MF9 bootloader is really old and probably wont install anymore. My phone did this before and I thought I bricked it, but I kid you not I took the battery out and removed the SIM card and rebooted and it booted up just fine. May not work for you, but I suggest you go back to update stock firmware then try again. If you're using the triband model, there's a post around here somewhere with confirmed roms that wont brick your device. I'm currently using the Google Play Edition Stock ROM and it's working GREAT.
Link for new firmware (NG5 Firmware):
Click to expand...
Click to collapse
Maybe I'm doing something foolish but every time I try to download files from the link you gave I get a decryption error so I can't download them zip or original.

rmngorelov said:
I restored to this stock ROM before and everything worked well. Currently I can't boot into recovery, Samsung flashes once and that's it, that's why I'm desperate the only thing I can do is boot in to download mode for odin.
Click to expand...
Click to collapse
Just hold home power and volume up. Right when you see text at the top left let go. You have to have the right timing

i7vSa7vi7y said:
Just hold home power and volume up. Right when you see text at the top left let go. You have to have the right timing
Click to expand...
Click to collapse
After almost eight hours of troubleshooting I finally got it to work.
I've tried flashing clockworkmod several times to see if I could get into recovery with no result so I gave up on that and I flashed the newest stock rom I could find L720VPUFNG2_L720SPTFNG2_SPR and it was still not booting. Than I thought maybe twerp would make a difference and god almighty it finally booted! I felt as if I gave birth to a child after eight hours of labor!
Now I'm extremely paranoid about touching anything because it took me forever to do this. Does anyone know why flashing twerp would make such a difference? I know this sort of stuff can get extremely complicated but I'd like to try to understand.
I hope my foolish agony contributed to this community if not in any other way except by the comedic relief caused by my ignorance.

rmngorelov said:
After almost eight hours of troubleshooting I finally got it to work.
I've tried flashing clockworkmod several times to see if I could get into recovery with no result so I gave up on that and I flashed the newest stock rom I could find L720VPUFNG2_L720SPTFNG2_SPR and it was still not booting. Than I thought maybe twerp would make a difference and god almighty it finally booted! I felt as if I gave birth to a child after eight hours of labor!
Now I'm extremely paranoid about touching anything because it took me forever to do this. Does anyone know why flashing twerp would make such a difference? I know this sort of stuff can get extremely complicated but I'd like to try to understand.
I hope my foolish agony contributed to this community if not in any other way except by the comedic relief caused by my ignorance.
Click to expand...
Click to collapse
Depends what recovery you had and what version. I personally like Philz touch recovery but TWRP is good. Now wipe and flash a ROM my friend or restore a backup

rmngorelov said:
After almost eight hours of troubleshooting I finally got it to work.
I've tried flashing clockworkmod several times to see if I could get into recovery with no result so I gave up on that and I flashed the newest stock rom I could find L720VPUFNG2_L720SPTFNG2_SPR and it was still not booting. Than I thought maybe twerp would make a difference and god almighty it finally booted! I felt as if I gave birth to a child after eight hours of labor!
Now I'm extremely paranoid about touching anything because it took me forever to do this. Does anyone know why flashing twerp would make such a difference? I know this sort of stuff can get extremely complicated but I'd like to try to understand.
I hope my foolish agony contributed to this community if not in any other way except by the comedic relief caused by my ignorance.
Click to expand...
Click to collapse
im having similar issues. which version of TWRP worked for you?
thank you

fearthemarchx said:
im having similar issues. which version of TWRP worked for you?
thank you
Click to expand...
Click to collapse
I recommend flashing the newest one here using odin
http://teamw.in/project/twrp2
Then once you are able to boot into recovery go to wipe and perform both factory reset and format data. Then install whatever rom you like, I used Sprint Galaxy S4 SPH-L720 VPUFNAE (Androdi 4.4.2) found here
http://galaxys4root.com/galaxy-s4-stock-firmware/ (or maybe find a newer stock rom if this one gives you errors)
Just copy the zip file to the phone, boot into twrp, do wipe factory reset again, select install then select the zip in whatever directory and you should be good to go. Make sure you do a back up in twrp once you get the phone to boot so you can always revert to stock.
I hope I was thorough enough that some of the information was useful. Let me know if you need any more help.

only certain recoveries will stick. ive tried the most recent twrp, with no luck. only a few versions of philztouch work.
Sent from my LGL34C using XDA Free mobile app

fearthemarchx said:
only certain recoveries will stick. ive tried the most recent twrp, with no luck. only a few versions of philztouch work.
Sent from my LGL34C using XDA Free mobile app
Click to expand...
Click to collapse
Format with philztouch that works then try flashing a new stock rom with odin. That should bring everything back to stock including the recovery.

ive tried. when i flash rom via odin i only get a blue "recovery booting" at the top of boot screen. even when i only power on, not into recovery. im going to attempt to flash rom provided in previous post via philz.
Sent from my LGL34C using XDA Free mobile app

fearthemarchx said:
ive tried. when i flash rom via odin i only get a blue "recovery booting" at the top of boot screen. even when i only power on, not into recovery. im going to attempt to flash rom provided in previous post via philz.
Sent from my LGL34C using XDA Free mobile app
Click to expand...
Click to collapse
You're in download mode when you flash from odin right? If you your getting an error flashing, try a different stock rom after reformating/resetting to factory (it's crucial to clear the cache before trying a different rom). I had to try a few roms before I found one that worked.