Database Users

Ive tried everything MF9/MJA stuck at boot

2 days ago i foolishly flashed to a stock rooted deodexed MJA zip from Cyanogenmod 10.2. (NO I DID NOT MAKE A BACK UP. I DID do a full data/cache wipe before i flashed) Things got really weird after that. Phone would not boot past the yellow sprint screen. I had a few different backups that must have been old so i tried restoring to an older Triforce MF9 backup that i had from 2 months ago. After that i was stuck on the triforce boot animation. I thought "maybe my kernel got mixed up when i tried flashing to MJA". Downloaded and flashed stock MF9 kernel NO LUCK.
Ended up using ODIN to install a factory stock .tar of MF9... same boot loop, cleared cache(this succeeded), tried clearing dalvik cache (but it failed). It booted up and YAY stock MF9 WITH ROOT. So after all the sprint bloatware loaded up i was prompted for an OTA 4.3 updated. I foolishly accepted. So my phone shuts down into recovery installs the update then goes to CWM and says "fix root? yes or no" i hit "yes". Since then NOTHING has worked.
I tried to ODIN back to MF9 again as mentioned before, nothing. I thought it may be a kernel issue, I found no info on the new MJA kernel. I successfully used ODIN to flash philz recovery.tar so now im on philz instead of CWM or TWRP. I attempted to flash the original stock rooted MJA.zip that got me into this mess, but no luck. I now can not get passed the "Samsung Galaxy S4 screen" (tried clearing caches, and battery pull too). Im downloading "KERNEL-SPR-L720VPUEMJA-1382157965.tar" & "SPR-L720VPUEMJA-20131030154609.zip" at the moment to flash with ODIN. Also i might add, it seems like any recovery i use, TWRP, CWM, Philz they dont fully install the rom .zip's. I hit "install zip from ext/sd-card" and its like a 2 second installation. NO MATTER WHAT ZIP I TRY. Kernels seem to flash okay.
I dont care about root, or knox. I just want my phone again lol.

Try going here

Tallyphillips said:
2 days ago i foolishly flashed to a stock rooted deodexed MJA zip from Cyanogenmod 10.2. (NO I DID NOT MAKE A BACK UP. I DID do a full data/cache wipe before i flashed) Things got really weird after that. Phone would not boot past the yellow sprint screen. I had a few different backups that must have been old so i tried restoring to an older Triforce MF9 backup that i had from 2 months ago. After that i was stuck on the triforce boot animation. I thought "maybe my kernel got mixed up when i tried flashing to MJA". Downloaded and flashed stock MF9 kernel NO LUCK.
Ended up using ODIN to install a factory stock .tar of MF9... same boot loop, cleared cache(this succeeded), tried clearing dalvik cache (but it failed). It booted up and YAY stock MF9 WITH ROOT. So after all the sprint bloatware loaded up i was prompted for an OTA 4.3 updated. I foolishly accepted. So my phone shuts down into recovery installs the update then goes to CWM and says "fix root? yes or no" i hit "yes". Since then NOTHING has worked.
I tried to ODIN back to MF9 again as mentioned before, nothing. I thought it may be a kernel issue, I found no info on the new MJA kernel. I successfully used ODIN to flash philz recovery.tar so now im on philz instead of CWM or TWRP. I attempted to flash the original stock rooted MJA.zip that got me into this mess, but no luck. I now can not get passed the "Samsung Galaxy S4 screen" (tried clearing caches, and battery pull too). Im downloading "KERNEL-SPR-L720VPUEMJA-1382157965.tar" & "SPR-L720VPUEMJA-20131030154609.zip" at the moment to flash with ODIN. Also i might add, it seems like any recovery i use, TWRP, CWM, Philz they dont fully install the rom .zip's. I hit "install zip from ext/sd-card" and its like a 2 second installation. NO MATTER WHAT ZIP I TRY. Kernels seem to flash okay.
I dont care about root, or knox. I just want my phone again lol.
Click to expand...
Click to collapse
you need to try to install the Triforce MJA/4.3.1 kernal/MJA modem all at the same time. IDK what happened on the first try to boot loop you but once you updated the modem to mja you can't flash MF9 modem/kernel on top of it. Try that and let me know.

Tallyphillips said:
2 days ago i foolishly flashed to a stock rooted deodexed MJA zip from Cyanogenmod 10.2. (NO I DID NOT MAKE A BACK UP. I DID do a full data/cache wipe before i flashed) Things got really weird after that. Phone would not boot past the yellow sprint screen. I had a few different backups that must have been old so i tried restoring to an older Triforce MF9 backup that i had from 2 months ago. After that i was stuck on the triforce boot animation. I thought "maybe my kernel got mixed up when i tried flashing to MJA". Downloaded and flashed stock MF9 kernel NO LUCK.
Ended up using ODIN to install a factory stock .tar of MF9... same boot loop, cleared cache(this succeeded), tried clearing dalvik cache (but it failed). It booted up and YAY stock MF9 WITH ROOT. So after all the sprint bloatware loaded up i was prompted for an OTA 4.3 updated. I foolishly accepted. So my phone shuts down into recovery installs the update then goes to CWM and says "fix root? yes or no" i hit "yes". Since then NOTHING has worked.
I tried to ODIN back to MF9 again as mentioned before, nothing. I thought it may be a kernel issue, I found no info on the new MJA kernel. I successfully used ODIN to flash philz recovery.tar so now im on philz instead of CWM or TWRP. I attempted to flash the original stock rooted MJA.zip that got me into this mess, but no luck. I now can not get passed the "Samsung Galaxy S4 screen" (tried clearing caches, and battery pull too). Im downloading "KERNEL-SPR-L720VPUEMJA-1382157965.tar" & "SPR-L720VPUEMJA-20131030154609.zip" at the moment to flash with ODIN. Also i might add, it seems like any recovery i use, TWRP, CWM, Philz they dont fully install the rom .zip's. I hit "install zip from ext/sd-card" and its like a 2 second installation. NO MATTER WHAT ZIP I TRY. Kernels seem to flash okay.
I dont care about root, or knox. I just want my phone again lol.
Click to expand...
Click to collapse
You cant go from aosp to tw. You need to go back to stock. Just odin back to mj9 stock. Then reroot and use that rom with philz rec
Sent from my SPH-L720 using xda app-developers app

[Q] 100% failure flashing kitkat roms, pls help a brother out.

Hi all,
For the past few days I've been trying to flash new ROMs. I'm a noon but have previously flashed probably 100 times with no problems at all.
Ive stuck with psx for about 3 months and live it, but as updates for the ROM have become a hasstke to get, I thought I'd try something else, but this time move on to KitKat custom ROMs instead of 4.3.
Now here's the problem. I'm doing everything the same as I usually would, d/l ROM, appropriate gapps, use latest twrp, factory reset, flash and then..... FAILED update : ( : ( Now I am a noobso am I missing something big time???, do I need to completely wipe phone when flashing from 4.3 to KitKat??, pls help, I'm sick to death of going through the fail/restore process
Thanks in advance : )

Are you updating the bootloader and radio when moving from 4.3 to 4.4? Did you try formatting the system before installing?

I transitioned from jellybean to KitKat too yesterday and had that same problem. From what i remember, what I did was when I got that failed update message in twrp, i first clicked home, then click reboot, then select to recovery. It should then warn you're about to reboot w/out a ROM/system. I swiped yes. Then it should prompt u to install supersu. Go ahead and swipe yes. It should then reboot u back to recovery and u can proceed to do your normal install routine. Now I'm adjusting myself to KitKat life!
Sent from my Nexus 4 using Tapatalk

I had that problem flashing ROMs with TWRP as well. I had to unmount the system, then everything flashed successfully!

Use cwrm instead , brotha from another motha twrp has issues with kitkat
Sent from my Nexus 4 using Tapatalk 4

You need a custom boot image for kitkat

Cant figure out how to install custom rom, without loosing root acces

Dear XDA
I have been an android user for many years and rooting has been one of the things I always did to my devices. I am an owner of a Note 3, which I have rooted succesfully and used X-NOTE 13 rom for long time. Last week I wanted to try something new and after that everything seems to be impossible. Before I install any roms I always perfom full wipe of, system, data, cache, dalvik cache etc. (I do it inside the recovery). Afterwards I tried to install CRASH ROM V9 and the progress went fine. When the phone rebooted the strange things started to happened I couldn't find the rom's extra menu and couldnt find any of the functions that the rom contained. I just thought that it was problem with the rom itself therefore I tried to went back to X-NOTE, but without any luck. The X-NOTE installed probably but I couldnt boot into it, it was stucked at the "Samsung Note 3" logo. I tried to wipe cache and dalvik but without any luck and every time I rebooted from the recovery the recovery says "it seems your device doesnt have root access" and the recovery tries to gain root access.
Then I couldnt understand anything of what was happening so I went to stock using ODIN. After installing stock rom I used CF-ROOT and everythings went smooth and I could use SuperSU inside the stock rom. Then I installed a recovery and it didn't mentioned anything about root access, so I was ready to install my custom rom...at least I thought so....I installed X-NOTE again (because I knew that this rom worked before without any problems) and after the progress was done I couldnt boot into the rom again, it was stucked. I wiped the cache and dalvik and as soon I clicked reboot in recovery it tells me that I am not rooted.
Then I did the same thing again, went back to stock, installed CF-ROOT and recovery. This time I installed CRASH ROM instead and I could boot into the system, but the rom still misses the "rooted features" etc.
In other words, what have I done wrong? I cant seem to find the problem and I think that I have tried every possible solution?
Informations:
Model: ​SM-N9005
STOCK ROM: Tried both N9005XXUENB4 (German) and N9005XXUENC2 (Nordic firmware)
Custom Rom: Tried both X-NOTE and CRASH ROM
Recoveries used: TWRP, CWM and Philz CWM
Kernels: Tried with stock one and X-NOTE kernel 1.5
I hope you can help me I cant live with stock roms
Thanks in advance
Regards,
Nepoznati

Nepoznati said:
Dear XDA
I have been an android user for many years and rooting has been one of the things I always did to my devices. I am an owner of a Note 3, which I have rooted succesfully and used X-NOTE 13 rom for long time. Last week I wanted to try something new and after that everything seems to be impossible. Before I install any roms I always perfom full wipe of, system, data, cache, dalvik cache etc. (I do it inside the recovery). Afterwards I tried to install CRASH ROM V9 and the progress went fine. When the phone rebooted the strange things started to happened I couldn't find the rom's extra menu and couldnt find any of the functions that the rom contained. I just thought that it was problem with the rom itself therefore I tried to went back to X-NOTE, but without any luck. The X-NOTE installed probably but I couldnt boot into it, it was stucked at the "Samsung Note 3" logo. I tried to wipe cache and dalvik but without any luck and every time I rebooted from the recovery the recovery says "it seems your device doesnt have root access" and the recovery tries to gain root access.
Then I couldnt understand anything of what was happening so I went to stock using ODIN. After installing stock rom I used CF-ROOT and everythings went smooth and I could use SuperSU inside the stock rom. Then I installed a recovery and it didn't mentioned anything about root access, so I was ready to install my custom rom...at least I thought so....I installed X-NOTE again (because I knew that this rom worked before without any problems) and after the progress was done I couldnt boot into the rom again, it was stucked. I wiped the cache and dalvik and as soon I clicked reboot in recovery it tells me that I am not rooted.
Then I did the same thing again, went back to stock, installed CF-ROOT and recovery. This time I installed CRASH ROM instead and I could boot into the system, but the rom still misses the "rooted features" etc.
In other words, what have I done wrong? I cant seem to find the problem and I think that I have tried every possible solution?
Informations:
Model: ​SM-N9005
STOCK ROM: Tried both N9005XXUENB4 (German) and N9005XXUENC2 (Nordic firmware)
Custom Rom: Tried both X-NOTE and CRASH ROM
Recoveries used: TWRP, CWM and Philz CWM
Kernels: Tried with stock one and X-NOTE kernel 1.5
I hope you can help me I cant live with stock roms
Thanks in advance
Regards,
Nepoznati
Click to expand...
Click to collapse
weird.
all the rom you mentioned xnote & crash come with root access inside.
When you said you used all those 3 recoveries, did you try each rom with each recovery ?
and when you flash those rom, did you follow to do a clean full wipe as mentioned on each OP thread ?
clean full wipe is not only wipe cache and dalvik, but also the data (factory reset).

antique_sonic said:
weird.
all the rom you mentioned xnote & crash come with root access inside.
When you said you used all those 3 recoveries, did you try each rom with each recovery ?
and when you flash those rom, did you follow to do a clean full wipe as mentioned on each OP thread ?
clean full wipe is not only wipe cache and dalvik, but also the data (factory reset).
Click to expand...
Click to collapse
Yes I have and tried several other combinations too. First time I installed X-NOTE I wiped everything and installed X-NOTE without problems.
I cant seem to break the code, I am getting frustrated hour by hour. I have double checked everything, I am on the NC2 bootloader with the NC2 kernel, when trying to install X-NOTE I get stuck at "Samsung Glaxy Note 3" - I cant understand what the problem may be and it is beginning to be personal :/ heheh
But seriously what could I have done wrong?

Nepoznati said:
Yes I have and tried several other combinations too. First time I installed X-NOTE I wiped everything and installed X-NOTE without problems.
I cant seem to break the code, I am getting frustrated hour by hour. I have double checked everything, I am on the NC2 bootloader with the NC2 kernel, when trying to install X-NOTE I get stuck at "Samsung Glaxy Note 3" - I cant understand what the problem may be and it is beginning to be personal :/ heheh
But seriously what could I have done wrong?
Click to expand...
Click to collapse
To be frank... I have no idea. U flash before earlier, means u know how to flash it.
What I could think of, is just the recovery.
I ve been using cwm chenglu all this time (the one reported with less bugs, and most recommended at any rom thread). And jump from rom to rom every 1 week at least with no issue.
I will try tonite use twrp to flash rom. I will let u know if I face any problem.

SOLVED
antique_sonic said:
To be frank... I have no idea. U flash before earlier, means u know how to flash it.
What I could think of, is just the recovery.
I ve been using cwm chenglu all this time (the one reported with less bugs, and most recommended at any rom thread). And jump from rom to rom every 1 week at least with no issue.
I will try tonite use twrp to flash rom. I will let u know if I face any problem.
Click to expand...
Click to collapse
Finally, finally and finally solved!
Well it seems strange but the problem was the official kernel inside the stock roms that made it almost impossible to run any custom rom.
What I did to solve the problem:
1. Went back to stock rom using a rom with the newest baseband NC2, ex. N9005XXUENC2
1a. I did have som problems getting the bootloader updated, which means I was force to install it over ODIN 3.09 - use this bootloader NC2 BOOTLOADER (Thanks soloilmeglio for the bootloader)
2. I used CF-ROOT to gain root access
3. Then I installed CWM 6.0.4.8 recovery as recommended from antique_sonic (Updated few hours ago!)
4. Install the CivZ-SnapKat-Rev3.1-sm_n9005-4.4.2.zip kernel
5. Lets the phone reboot and check that everything works!
7: Boot into recovery and wipe system, data, cache, dalvik cache
8. Install the custom rom
Dont ask me why the kernel wasn't working from beginning and why it was "corrupted" after installing another custom rom - but now everything works as it should!
Thank you very much antique_sonic for helping me!

Nepoznati said:
Finally, finally and finally solved!
Well it seems strange but the problem was the official kernel inside the stock roms that made it almost impossible to run any custom rom.
What I did to solve the problem:
1. Went back to stock rom using a rom with the newest baseband NC2, ex. N9005XXUENC2
1a. I did have som problems getting the bootloader updated, which means I was force to install it over ODIN 3.09 - use this bootloader NC2 BOOTLOADER (Thanks soloilmeglio for the bootloader)
2. I used CF-ROOT to gain root access
3. Then I installed CWM 6.0.4.8 recovery as recommended from antique_sonic (Updated few hours ago!)
4. Install the CivZ-SnapKat-Rev3.1-sm_n9005-4.4.2.zip kernel
5. Lets the phone reboot and check that everything works!
7: Boot into recovery and wipe system, data, cache, dalvik cache
8. Install the custom rom
Dont ask me why the kernel wasn't working from beginning and why it was "corrupted" after installing another custom rom - but now everything works as it should!
Thank you very much antique_sonic for helping me!
Click to expand...
Click to collapse
Good then to know ur phone is okay.
I fully wipe with twrp last nite. And flash xnote. Hang at boot after done.
Fully wipe again, and flash assassins. A lot fc here and there.
I flash back cwm chenglu, full wipe, and flash back xnote. Now it runs nicely.
My phone not suit with twrp.

antique_sonic said:
Good then to know ur phone is okay.
I fully wipe with twrp last nite. And flash xnote. Hang at boot after done.
Fully wipe again, and flash assassins. A lot fc here and there.
I flash back cwm chenglu, full wipe, and flash back xnote. Now it runs nicely.
My phone not suit with twrp.
Click to expand...
Click to collapse
It could probably be a problem with TWRP as you mentioned earlier. After using CWM everything went smooth after updating my kernel. Last night I couldnt hold me back to try one more time, and I flashed X-NOTE with TWRP and I got the same problem as described in #1 post. Then I installed CWM and flashed X-NOTE again and everything got messed up. Then I restored everything, force installed the kernel and bootlaoder. After that installed CWM and then I was able to run X-NOTE without any problem.
I am not a professional developer but I may think that the problem is TWRP when it tries to flash the kernel under the process with may results in some problems. When using CWM from the beginning I do not get any problems but when using TWRP I need to restore everything back.

Am I doing something wrong? I've tried to find the answer. So please delete and refe

Trying to figure this out first off here's the details of the device in question.
Sgh-i377m Canadian koodo. Running stock ROM L 5.0.1
I've rooted with cf-autoroot and then flashified to Philz 6.14 I think. Just because I've never tried it. Then rebooted wiped cache/davlik then rebooted and flashified to the latest twrp 2.8.6 with f2fs support from the optimized 9105 cyanogen mod 12 thread. Everything was solid. I upgraded root to the beta copy in chainfire's supersu thread.
I rebooted several times and was fine. I went to bed and I woke up with my phone unrooted and factory reset asking me to start from the beginning of setting up my phone. So incredibly angry I didn't believe the situation and I setup the phone over again. Then rebooted into recovery and sure as fart that you shouldn't of trusted it was the factory oem recovery. So I attempted to root again and was successful and then upgraded the phone to what flashify lists as the latest twrp for the jfltecan as 2.8.4 and then upgraded to 2.8.6 f2fs from the thread mentioned earlier and sure enough not even 20 min later after I got out of the shower it factory reset itself and installed the factory oem recovery. I made sure this time software update was disabled and rooted again. I flashified to 2.8.4 only as per flashify reporting is the latest and everything seemed fine so I thought maybe the recovery being for the 9105 as the problem. I went to eat and the problem happened again. Am I the only one experiencing this?
Am I doing something wrong ? someone please help.
Signed sincerely,
Getting pissed off of flashing the same damn thing over and over.
Thank u.

"Camera Failed" After Restoring in TWRP

I restored a backup from a few weeks ago after trying out a marshmallow based ROM (I was on lollipop prior) and after the restore process, my old phone interface came up and it was as if I never flashed the newer rom at all as expected, however, now my camera does not work at all and I could use a hand figuring out how to resolve this issue.
Things I've tried:
- Rebooting (obviously)
- Clearing cache/dalvik from recovery
- Clearing the camera app's data and cache
When I restored my backup, I chose not to restore 'boot' and 'recovery' because while I was on the marshmallow rom, I unlocked my phone's bootloader and installed TWRP (as opposed to using SafeStrap) and I didn't want to lose it.
Samsung Galaxy S5 GM-900V
Android 5.0
Baseband: G900VVRU2BOG5
Build: OptimalRom 15-5
Marshmallow rom I referenced: Norma_Note5Port_V3.4_VZW
Any advice?

So I've formatted dalvik/cache/data/internal storage and installed the older rom (OptimalRom 15-2 ) again. Did the initial setup and the camera still didn't work. I tried reflashing a known-good kernel that's compatible with this rom and that didn't seem to help.
Can anyone point me in the right direction on how to resolve this? Something must have been flashed when I installed the Note 5 rom that wasn't when I went back to OptimalRom. I just don't know what. I'll keep searching and experimenting. Thankfully I have a real recovery menu now so softbricking isn't as big of a deal.

GoTeamScotch said:
So I've formatted dalvik/cache/data/internal storage and installed the older rom (OptimalRom 15-2 ) again. Did the initial setup and the camera still didn't work. I tried reflashing a known-good kernel that's compatible with this rom and that didn't seem to help.
Can anyone point me in the right direction on how to resolve this? Something must have been flashed when I installed the Note 5 rom that wasn't when I went back to OptimalRom. I just don't know what. I'll keep searching and experimenting. Thankfully I have a real recovery menu now so softbricking isn't as big of a deal.
Click to expand...
Click to collapse
Since you have TWRP now, try doing a complete and clean wipe. Go into recovery, Wipe, Advance Wipe and select Cache, Dalvik cache, Data and Internal and swipe. Then back out to Wipe and swipe twice on the slider and install the OptimalRom of choice. then install the PB1 firmware NO Bootloader. If you still have an issue then try with the ROM kernal and flash it which I think it'sthe OG5 Kernal No Bootloader. The reason for doing this particular wipe is to get anything that may be left over from a previous ROM. This is my preference and habit from when I started running ROM's on my S3. Beanstown103 and others had recommended doing this in TWRP and haven't had any issues or problems by doing this since. Hope this may help

Thanks al50. I will give that a shot. Sorry but I'm not familiar with "PB1 firmware". what are you referencing there?

GoTeamScotch said:
Thanks al50. I will give that a shot. Sorry but I'm not familiar with "PB1 firmware". what are you referencing there?
Click to expand...
Click to collapse
It's the version that your phone is on. Look in About Phone in settings. Anyways, that’s the Zip file you install after you install the ROM. But if you're already on PB1 then you don't have to worry about that. If you have issues with the camera then try flashing the No bootloader kernal that was made for that ROM, which I believe it was OG5 but check the OP to be for sure