Database Users

[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] Stuck on LG logo

I recently purchased a lg g2, the korean variant f320s, it was running kitkat with a lot of bloatware on top. I successfully rooted the phone and after that i found a cwm recovery installer for this version of the phone and i hooked up the phone and ran the installer on my pc, it finished installing and the phone rebooted into the custom recovery which was in chinese i went into a menu option and then pressed the back button on the screen and the phone instantly rebooted and got stuck at lg boot logo. Is there anyway to fix this? i have tried wiping cache, dalvik and factory reset from the recovery that i can access(chinese or something) but to no avail. I can access the download mode but my pc does'nt recognize the phone and this step is crucial for i guess installing the stock rom through lg flash tools. The phone however is recognized when im in recovery and i plug it in but it only shows as a drive that is faded out and entering it shows nothing. please help me i just got it two days ago

Have you tried to use adb to sideload a rom?

playerone_ said:
Have you tried to use adb to sideload a rom?
Click to expand...
Click to collapse
i'm sorry im a complete noob in this regard could you explain a bit on how to go about doing that? i am downloading the stock kitkat rom for the model its in kdz format

.
I flashed cloudy flex rom on it through external sd in recovery and now when i boot it up it stays on lg logo for a while then screen goes black and botts up again directly into CWM recovery, please help someone...

Same problem
sheroy1995 said:
I recently purchased a lg g2, the korean variant f320s, it was running kitkat with a lot of bloatware on top. I successfully rooted the phone and after that i found a cwm recovery installer for this version of the phone and i hooked up the phone and ran the installer on my pc, it finished installing and the phone rebooted into the custom recovery which was in chinese i went into a menu option and then pressed the back button on the screen and the phone instantly rebooted and got stuck at lg boot logo. Is there anyway to fix this? i have tried wiping cache, dalvik and factory reset from the recovery that i can access(chinese or something) but to no avail. I can access the download mode but my pc does'nt recognize the phone and this step is crucial for i guess installing the stock rom through lg flash tools. The phone however is recognized when im in recovery and i plug it in but it only shows as a drive that is faded out and entering it shows nothing. please help me i just got it two days ago
Click to expand...
Click to collapse
EXACT same problem as you... Every detail is exactly the same.
I am trying to find a solution. Any luck?

.
naleyb01 said:
EXACT same problem as you... Every detail is exactly the same.
I am trying to find a solution. Any luck?
Click to expand...
Click to collapse
Yeah you just need to flash a different rom through the sd card i tried cloudy rom but it didnt work then a i tried Lamhoang rom and it did the trick im on jellybean now though and i'll try flashing something else in a month or so

ALL FIXED
You are a legend!! Device back up and running.
Okay so I installed that same rom you did but the home/back/menu buttons weren't working so not wanting to muck around, I did some quick searching (which I should have done before >.<) and worked out how to get the Cloudy roms working on a korean device.
You need "Philz cloudy f320 recovery", the kitkat baseband and the rom. LINK
1 - Install the new recovery from zip and then boot back into recovery after this. You will now be greeted with philz recovery which is awesome.
2 - From here, proceed to install the rom as noted on the rom page.
This process worked for me for the Cloudy G3 V1.3 rom.
Thanks a lot for your help!! happy to return the favour! But i am hoping the above info already does that. :victory:

naleyb01 said:
You are a legend!! Device back up and running.
Okay so I installed that same rom you did but the home/back/menu buttons weren't working so not wanting to muck around, I did some quick searching (which I should have done before >.<) and worked out how to get the Cloudy roms working on a korean device.
You need "Philz cloudy f320 recovery",
1 - Install the new recovery from zip and then boot back into recovery after this. You will now be greeted with philz recovery which is awesome.
2 - From here, proceed to install the rom as noted on the rom page.
This process worked for me for the Cloudy G3 V1.3 rom.
Thanks a lot for your help!! happy to return the favour! But i am hoping the above info already does that. :victory:
Click to expand...
Click to collapse
Good to know you got it working again i still cant figure out why this problem occurred in the first place why did the phone brick from the recovery when the recovery was working fiblne after? Also i can just get the new recovery over the one already on the phone without removing the previous one right? Thanks for the info im gonna try out the cloudy roms soon

I have no idea.. something to do with that chinese recovery I am guessing.. There are still a few issues I am going to address but for now my phone is 95% working.
The only issue is that if I try go into download mode, it still doesn't go to the second screen (All i get is the small blue dots). Bit of a pain because that's something nice to fall back on if you ever need to.
I'll search around and try and figure these out in the next week or two, but I am happy with what I have for the moment.
Yep, you literally install the new recovery over your current one and then you can restart phone back into your rom and then reboot back into recovery using an app or the button method.

naleyb01 said:
I have no idea.. something to do with that chinese recovery I am guessing.. There are still a few issues I am going to address but for now my phone is 95% working.
The only issue is that if I try go into download mode, it still doesn't go to the second screen (All i get is the small blue dots). Bit of a pain because that's something nice to fall back on if you ever need to.
I'll search around and try and figure these out in the next week or two, but I am happy with what I have for the moment.
Yep, you literally install the new recovery over your current one and then you can restart phone back into your rom and then reboot back into recovery using an app or the button method.
Click to expand...
Click to collapse
Yeah i have the same issue with the download mode as well and the phone cant seem to sync properly with the lg mobile support tool either.Do let me know if you figure something out

[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.

N910C stuck in frustrating bootloop

Hey wassup. So yesterday I rooted my phone and tried to install CM13 on it. Took a few tries since the rom I got was corrupted but I got it to work. Then I noticed it was guzzling the battery like lemonade (this EXACT same thing happened on my previous S4 too) so I gave up on it and decided to revert back to the stock rom. Everything went well... NOT. I downloaded the stock firmware (3gigs... zzz) and I flashed it with Odin and the phone restarted. The little android robot from the default unrooted recovery popped up and it had below it this: "Installing system update..." and then out of the blue it said "Erasing" and it's gear started rotating backwards. THEN, when it finished the normal Samsung Galaxy Note 4 logo popped up, went away and then CAME BACK AGAIN FOR LIKE 500 TIMES AND COUNTING. AOSP roms work just fine, it's just that touchwiz ones won't work whatsoever (even tried sixperience, no luck)... What should I do? I already lost my S4 due to this...

install TWRP custom recovery, boot up in recovery format system dalvik cache and internal storage then try flashing stock with odin hopefully it will work.

Try to remove battery first.from tsoch recovery wipe data cache and see if it works

dork997 said:
install TWRP custom recovery, boot up in recovery format system dalvik cache and internal storage then try flashing stock with odin hopefully it will work.
Click to expand...
Click to collapse
Been there, done that. Nope, still refuses to work :/

bumpity bump bump

Did you backup your efs partition before you flashed cm13? If not you corrupted your efs and your phone is a wifi tablet now because you cant use your modem.

travis82 said:
Did you backup your efs partition before you flashed cm13? If not you corrupted your efs and your phone is a wifi tablet now because you cant use your modem.
Click to expand...
Click to collapse
this never happened to me with my old s2 or s4
why is it happening now ?

Didn't backup. Now it just won't even work with odin. Whenever I try to just flash anything with it goes off and says 0 successes and 0 fails. What I did notice though was that whenever I installed a stock rom it starts this "Installing system update" with the android robot twingling it's antennaes and then out of nowhere it's blue bar goes away and it says "Erasing" then... bootloop. Now odin won't even work (explained above). Should I just give up and send it in for repairing? Or can ANYONE send me the twrp restore file, please...

Peontikos_Desmos said:
Didn't backup. Now it just won't even work with odin. Whenever I try to just flash anything with it goes off and says 0 successes and 0 fails. What I did notice though was that whenever I installed a stock rom it starts this "Installing system update" with the android robot twingling it's antennaes and then out of nowhere it's blue bar goes away and it says "Erasing" then... bootloop. Now odin won't even work (explained above). Should I just give up and send it in for repairing? Or can ANYONE send me the twrp restore file, please...
Click to expand...
Click to collapse
Hi
Same problem
Any ideas !!!

Hey,
I have the same problem it turns out after flashing, i cant remember, maybe dytto note 4 rom, it got stuck in continous bootloops and the only way it is working for me is when its charging. I know it sounds crazy but its the only way for me, ive tried installing stock different countries firmware and bunch of custom rom with no luck. I sent it to the place where i bought the phone and made myself look dumb asking why it is like that and i told them i had not do anything. After only a week they phoned me and said it was rooted (i did get the root out when i gave it but they somehow knew it was... later i understood that it is all about that stupid Know thing) and refused to cover my warranty. They said that the only way i can get it to work is to pay 300$ for new chip :,(

senon said:
Hey,
I have the same problem it turns out after flashing, i cant remember, maybe dytto note 4 rom, it got stuck in continous bootloops and the only way it is working for me is when its charging. I know it sounds crazy but its the only way for me, ive tried installing stock different countries firmware and bunch of custom rom with no luck. I sent it to the place where i bought the phone and made myself look dumb asking why it is like that and i told them i had not do anything. After only a week they phoned me and said it was rooted (i did get the root out when i gave it but they somehow knew it was... later i understood that it is all about that stupid Know thing) and refused to cover my warranty. They said that the only way i can get it to work is to pay 300$ for new chip :,(
Click to expand...
Click to collapse
ffs i'm not paying another phone's worth in a ****ing motherboard. I tried:
-Flashing the stock bootloader, fails at sboot.img:NAND Write start fail
-Flashing the PIT file, just... wont flash. Successes 0/Fails 0
-Flashing the stock AP file, bootloop
-Flashing the CP and the CSC stock files, serial(com) port cannot be opened.
****ing garbage. For some reason my phone's the only exception to the rule that phones able to boot into download mode are salvageable. It's going in for a repair and if it's more than $50 I'm not rooting again even at gunpoint.

Quick update:
I found a toolkit that has a flash stock boot image option. Had to recover to my cm13 backup to enable usb debugging. Will post results

Nothing of course...

try this step by step,
1. Download stock firmware THE LATEST ONE (n910c v5.1.1) from sammobile.com
2. Download newest Odin and Samsung USB; installed Samsung USB
3. I am assuming you have installed twrp recovery. Boot to twrp recovery and do a full wipe; wipe all!
4. Boot to downloading mode and install stock via odin. That is it.
Ps.... in case of failure, make sure you have installed Samsung USB! Or just reconnect usb cable with other usb ports untill it is working.

Never flach cm if doesn'T HAVE a efs backup if not you will stuck with cm

Oliva.raiders said:
1. Download stock firmware THE LATEST ONE (n910c v5.1.1) from sammobile.com
2. Download newest Odin and Samsung USB; installed Samsung USB
3. I am assuming you have installed twrp recovery. Boot to twrp recovery and do a full wipe; wipe all!
4. Boot to downloading mode and install stock via odin. That is it.
Ps.... in case of failure, make sure you have installed Samsung USB! Or just reconnect usb cable with other usb ports untill it is working.
Click to expand...
Click to collapse
Well, crap I already sent it in for repairing but if the fuqing robbers decide to change the motherboard instead of doing anything to it and charge me 500$ to do so I'm getting it back and I'm trying this one. Already did but it wouldn't hurt retrying... BTW FOR THE LOVE OF GOD DOES SOMEONE HAVE A TWRP BACKUP FILE ON STOCK TOUCHWIZ? JESUS

radium56ad said:
Never flach cm if doesn'T HAVE a efs backup if not you will stuck with cm
Click to expand...
Click to collapse
Is there absolutely NO workaround?

i had the same issue, this is how i solved this (you won't like it):
-deleted efs partition
-restored 5.1.1 coj5 via odin
-then took it to a samsung repair center to restore the imei
paid them like 50 bucks...that sucks. after this im backing up efs folder before flashing a rom.

radium56ad said:
Never flach cm if doesn'T HAVE a efs backup if not you will stuck with cm
Click to expand...
Click to collapse
JuanWilliman said:
i had the same issue, this is how i solved this (you won't like it):
-deleted efs partition
-restored 5.1.1 coj5 via odin
-then took it to a samsung repair center to restore the imei
paid them like 50 bucks...that sucks. after this im backing up efs folder before flashing a rom.
Click to expand...
Click to collapse
Oh that's nothing man. The fuqing scammers told me the whole freaking board had to be replaced...

There's one thing I've noticed though that's PROBABLY gotta be the culprit. Whenever I install a touchwiz rom, the phone boots up fine for once, shows the robot with the "Installing system update" and then it goes off with "Erasing" followed by the bootloop. Could anyone please elaborate on this? I have a feeling this is what's causing this ****fest

Softish Brick Recovery i9505 int

Hi,
My i9505 Intl (Australian Telstra LTE) SGS4 has been rooted for a year at least now, and recently (a few months) had TWRP recovery and CM13 installed and everything was going great. I loved CM!
Anyway I had done a few nightly patches of CM and all seemed good and then a week ago I installed the most recent nightly (possibly this one cm-13.0-20160819-NIGHTLY-jfltexx-recovery.img ). Well the subsequent reboot put the phone into a boot loop. So I thought no problem just boot to recovery and install my recent Nandroid back up. So did that but in my haste didn't clear cache or data. The nandroid reinstall seemed to go ok but a subsequent boot hung at the CM logo (I think it was a while ago now) and I couldn't boot to recovery, just hung with the blue text.
So I fired up Odin and booted to download and reflashed with TWRP. Boot to recovery still didn't work however I could still boot to download.
Tried different USB ports, different versions of Odin, re installed drivers to no avail. Also tried CWM, TWRP and Philz recovery and once I did get it to boot to recovery with Philz. THIS TIME cleared cache and data and loaded a good copy of CM that I had on my SD card. Again stuck in boot. Couldn't get back to recovery.
Tried loading the orginal samsung firmware and they I was stuck with a Samsung logo boot looping. Ditto recovery just hung at the logo and the blue text "recovery booting".
Rinse and repeat a few times and now the phone has started to become difficult to get into download or recovery. If I leave it with the battery out for a while it seems to come good again.
Odin when flashing a new recovery either hangs half way though or completes and says everything is OK. Full blue bar on the phone.
Rebooting however still leaves me in the boot loop.
There is no mention on Odin of any issues with the partition however I have d/l a PIT file from one of samersh72's posts but am not sure if it is the correct one for my Int phone or indeed if I need to use it as Odin doesn't seem to report any partition errors.
If any one has any suggestions I am very receptive to ideas right now.....
Thanks

Did you perform a factory wipe after flashing stock before booting the rom for the first time?

audit13 said:
Did you perform a factory wipe after flashing stock before booting the rom for the first time?
Click to expand...
Click to collapse
I did a factory wipe and then installed CM from my SD card but that is the only time I have able to get into recovery since the first time when I reloaded my nandroid backup

Did you try flashing recovery without selecting auto reboot? Once flashed, remove USB cable, remove battery, replace battery, try to boot into recovery.

audit13 said:
Did you try flashing recovery without selecting auto reboot? Once flashed, remove USB cable, remove battery, replace battery, try to boot into recovery.
Click to expand...
Click to collapse
Yup tried that, as I realised that the auto boot might be overwriting the custom recovery...........however as a new development I haven't been able to boot to download or even the stuck recovery since yesterday.
I think it has now moved to a full hard brick

Is still turns on? You have a USB jig to try?

audit13 said:
Is still turns on? You have a USB jig to try?
Click to expand...
Click to collapse
No I don't have one but I have all the makings of one so i'll put one together and give it a go. Though I have to say that I am not that hopeful as I can't even get a peep out of it now.

A jig may be the last solution before sending it for repair or replacing the motherboard.

audit13 said:
A jig may be the last solution before sending it for repair or replacing the motherboard.
Click to expand...
Click to collapse
Thanks Audit, Ill let you know how I get on. Just looked at some replacement motherboards and they don't seem too common for the LTE version used here in Australia AND USD60......pretty much get a working phone locally here on ebay for that and I get the rest of the parts too.

Have you tried already flashing a stock rom as a tar file from sammobile?

justgamer01 said:
Have you tried already flashing a stock rom as a tar file from sammobile?
Click to expand...
Click to collapse
Yup did that as well!

Ghostdog1 said:
Yup did that as well!
Click to expand...
Click to collapse
I'm not sure if it will work! But try emergency recovery with Smart Switch!

justgamer01 said:
I'm not sure if it will work! But try emergency recovery with Smart Switch!
Click to expand...
Click to collapse
With Smartswitch I get the same outcome as with Kires
"GT-I9505 does not support initialising. Please contact our service centre."
But on the plus side it is actually responding to button presses today. I will pick up some 100K resistors tomorrow and finish off my USB jig. See how that goes.

Well it appears to have finally died fully. No response to any button or combination of button presses. Made up a USB jig but without some response to a boot that won't work either.
Thanks to Audit and Justgamer for your advice. Think it is time to draw a line under this one and move on. Maybe a new Nexus when they drop?