Database Develop

[Q] I messed up the RADIO on my i8190L and now stuck in bootloop

Let's start with a little background as to how I got into this mess
- I had a perfectly working i8190L running SlimBean 4.3 from Maclaw (and I should've left it alone since its the wife's phone)
- I wanted to try out the new SlimKat 4.4 (http://get.novafusion.pl/?id=955)
- After a clean flash of slimkat, the new ROM was running fine after I completed setup EXCEPT baseband was 'xxxx'
- I rebooted into recovery and flashed GT-I8190_modem.bin-XXAMJ3-update2.zip because it was in my sdcard. I thought flashing a new radio would change the baseband except now I'm stuck in a bootloop with NO ABILITY TO BOOT TO RECOVERY!!!!
- I can only boot into Download mode, so I can still ODIN flash the system
Can someone suggest how/if I can fix this? I'm just kicking myself for turning a fully working phone into a brick with my wife breathing down my shoulders
my working setup was TWRP 2.7, SlimBean 4.3 and I had no idea which radio the i8190L came with default
I created a nandroid before all this mess, but I just need a way to get back into Recovery

You downloaded the wrong modem file. You need the one for the I8190L, but you flashed one for the I8190.
Sent from Tapatalk on my GT-I8190 running Novafusion's Carbon 4.4.2

chan1628 said:
Let's start with a little background as to how I got into this mess
- I had a perfectly working i8190L running SlimBean 4.3 from Maclaw (and I should've left it alone since its the wife's phone)
- I wanted to try out the new SlimKat 4.4 (http://get.novafusion.pl/?id=955)
- After a clean flash of slimkat, the new ROM was running fine after I completed setup EXCEPT baseband was 'xxxx'
- I rebooted into recovery and flashed GT-I8190_modem.bin-XXAMJ3-update2.zip because it was in my sdcard. I thought flashing a new radio would change the baseband except now I'm stuck in a bootloop with NO ABILITY TO BOOT TO RECOVERY!!!!
- I can only boot into Download mode, so I can still ODIN flash the system
Can someone suggest how/if I can fix this? I'm just kicking myself for turning a fully working phone into a brick with my wife breathing down my shoulders
my working setup was TWRP 2.7, SlimBean 4.3 and I had no idea which radio the i8190L came with default
I created a nandroid before all this mess, but I just need a way to get back into Recovery
Click to expand...
Click to collapse
Sorry but you are going to sleep on the couch tonight I suggest this:
You must download the original rom from SamMobile, install it through Odin and then install again through Odin the Recovery and through Recovery your "old" new Rom. When you are in the new Recovery check for the nandroid backup that you made . If it isnt there look for the couch because the phone is with the "old" new Rom without any of the past data.
Btw if you want you can upgrade your baseband from here:http://forum.xda-developers.com/showthread.php?t=2526831
Good luck

No recovery at all or bootloop in recovery as well?
Sent through time and space from my s3mini/CM11

chan1628 said:
Let's start with a little background as to how I got into this mess
- I had a perfectly working i8190L running SlimBean 4.3 from Maclaw (and I should've left it alone since its the wife's phone)
- I wanted to try out the new SlimKat 4.4 (http://get.novafusion.pl/?id=955)
- After a clean flash of slimkat, the new ROM was running fine after I completed setup EXCEPT baseband was 'xxxx'
- I rebooted into recovery and flashed GT-I8190_modem.bin-XXAMJ3-update2.zip because it was in my sdcard. I thought flashing a new radio would change the baseband except now I'm stuck in a bootloop with NO ABILITY TO BOOT TO RECOVERY!!!!
- I can only boot into Download mode, so I can still ODIN flash the system
Can someone suggest how/if I can fix this? I'm just kicking myself for turning a fully working phone into a brick with my wife breathing down my shoulders
my working setup was TWRP 2.7, SlimBean 4.3 and I had no idea which radio the i8190L came with default
I created a nandroid before all this mess, but I just need a way to get back into Recovery
Click to expand...
Click to collapse
Don't bother trying to flash it if nothing happens, drain the battery, return to seller and get replacement. I got free replacement from Amazon with my bricked rooted S3 mini.

jstath1972 said:
Sorry but you are going to sleep on the couch tonight I suggest this:
You must download the original rom from SamMobile, install it through Odin and then install again through Odin the Recovery and through Recovery your "old" new Rom. When you are in the new Recovery check for the nandroid backup that you made . If it isnt there look for the couch because the phone is with the "old" new Rom without any of the past data.
Btw if you want you can upgrade your baseband from here:http://forum.xda-developers.com/showthread.php?t=2526831
Good luck
Click to expand...
Click to collapse
just to clarify... what is consider "the original rom from SamMobile"? There are plenty of versions and country codes to choose from... I just wanted to make sure I'm downloading the correct one.... i've done enough of using the wrong files already

KoolKid98189 said:
Don't bother trying to flash it if nothing happens, drain the battery, return to seller and get replacement. I got free replacement from Amazon with my bricked rooted S3 mini.
Click to expand...
Click to collapse
its not going to be that easy for me... i've had this phone for almost 2yrs already
tys0n said:
No recovery at all or bootloop in recovery as well?
Sent through time and space from my s3mini/CM11
Click to expand...
Click to collapse
no recovery at all... it bootloops if i power on normally

chan1628 said:
just to clarify... what is consider "the original rom from SamMobile"? There are plenty of versions and country codes to choose from... I just wanted to make sure I'm downloading the correct one.... i've done enough of using the wrong files already
Click to expand...
Click to collapse
It depends on what country you're in and if the phone is locked to any specific carrier.
If it's not locked then I believe any i8190L firmware will do, just to get the phone running again.

chan1628 said:
its not going to be that easy for me... i've had this phone for almost 2yrs already
no recovery at all... it bootloops if i power on normally
Click to expand...
Click to collapse
It was a tough decision for me, it was either stick to a ****ty BlackBerry or get a free replacement and sacrifice the data. Some of it should be synced to your Google account

tys0n said:
It depends on what country you're in and if the phone is locked to any specific carrier.
If it's not locked then I believe any i8190L firmware will do, just to get the phone running again.
Click to expand...
Click to collapse
ok, i will give all this a try and hope for the best
thanks everyone for the quick responses :good:

You could also try to reflash just recovery thru Odin and see if it works.
Sent through time and space from my s3mini/CM11

chan1628 said:
just to clarify... what is consider "the original rom from SamMobile"? There are plenty of versions and country codes to choose from... I just wanted to make sure I'm downloading the correct one.... i've done enough of using the wrong files already
Click to expand...
Click to collapse
You are in Canada but the L version is for the Latin America countries. So the firmware must be from one of that countries. Which one i can't tell you. You should ask your seller.

[problem solved]
Ok, I was able to restore the phone with /u/jstath1972's suggestion
1. I went to http://www.sammobile.com/firmwares/ and downloaded the latest 'L' firmware
2. I used ODIN to flash the firmware
3. the phone REBOOTED!!!
(once the phone rebooted, the rest was easy)
4. powered off and ODIN flashed the lastest TWRP
5. powered off and booted into recovery
6. RESTORED NANDROID so wife would stop giving me the look
7. updated baseband as suggested: http://forum.xda-developers.com/show....php?t=2526831
THANK YOU THANK YOU :good:
side note: i wish my work was this effective in resolving technical issues (just my 2 cents)

chan1628 said:
Ok, I was able to restore the phone with /u/jstath1972's suggestion
1. I went to http://www.sammobile.com/firmwares/ and downloaded the latest 'L' firmware
2. I used ODIN to flash the firmware
3. the phone REBOOTED!!!
(once the phone rebooted, the rest was easy)
4. powered off and ODIN flashed the lastest TWRP
5. powered off and booted into recovery
6. RESTORED NANDROID so wife would stop giving me the look
7. updated baseband as suggested: http://forum.xda-developers.com/show....php?t=2526831
THANK YOU THANK YOU :good:
side note: i wish my work was this effective in resolving technical issues (just my 2 cents)
Click to expand...
Click to collapse
Good sleep tonight, my friend ! :good:

Need help again....pls

ive got safestrap installed. created rom slot. tried to load a rom and nothin. it boots to a wiped stock rom. nothin happens. nothin changes

harley1rocker said:
ive got safestrap installed. created rom slot. tried to load a rom and nothin. it boots to a wiped stock rom. nothin happens. nothin changes
Click to expand...
Click to collapse
You need to provide a lot more information if you want some help. What firmware are you on? What version of SafeStrap did you install? What ROM did you try to install? What steroids did you take? Which modules did you flash? Does your stock ROM boot?
Always provide as much information as possible, it will increase your chances of getting help.

Devo7v said:
You need to provide a lot more information if you want some help. What firmware are you on? What version of SafeStrap did you install? What ROM did you try to install? What steroids did you take? Which modules did you flash? Does your stock ROM boot?
Always provide as much information as possible, it will increase your chances of getting help.
Click to expand...
Click to collapse
Let me try, because I think I have the same issue. I'm running 4.4.2, and I used safestrap 3.73 to create a rom slot and install Hyperdrive. I wiped everything it said to before I installed it, and installed the latest masterpatch after and rebooted. When it rebooted, it appears to have gone into my stock ROM. Everything is the same, except my network doesn't work because it says my SIM card isn't inserted. Any ideas?
---------- Post added at 12:33 AM ---------- Previous post was at 12:20 AM ----------
Caboose27 said:
Let me try, because I think I have the same issue. I'm running 4.4.2, and I used safestrap 3.73 to create a rom slot and install Hyperdrive. I wiped everything it said to before I installed it, and installed the latest masterpatch after and rebooted. When it rebooted, it appears to have gone into my stock ROM. Everything is the same, except my network doesn't work because it says my SIM card isn't inserted. Any ideas?
Click to expand...
Click to collapse
And now I tried to wipe it again, and that ROM slot is gone, and I suddenly don't have room to make a new one.
*edit* apparently a wipe this time around reset my entire phone. No idea why. Is there a manual on this program somewhere? I keep getting told to search and I'll find it, but all I've found is about five lines worth of instructions.

Caboose27 said:
Let me try, because I think I have the same issue. I'm running 4.4.2, and I used safestrap 3.73 to create a rom slot and install Hyperdrive. I wiped everything it said to before I installed it, and installed the latest masterpatch after and rebooted. When it rebooted, it appears to have gone into my stock ROM. Everything is the same, except my network doesn't work because it says my SIM card isn't inserted. Any ideas?
---------- Post added at 12:33 AM ---------- Previous post was at 12:20 AM ----------
And now I tried to wipe it again, and that ROM slot is gone, and I suddenly don't have room to make a new one.
*edit* apparently a wipe this time around reset my entire phone. No idea why. Is there a manual on this program somewhere? I keep getting told to search and I'll find it, but all I've found is about five lines worth of instructions.
Click to expand...
Click to collapse
You cannot use ROM slots with SafeStrap 3.73. You have to install ROMs to your stock ROM slot overwriting your stock ROM. So make a backup before you flash anything. The developer of SafeStrap took a new job and had to abandon development before he could fully implement ROM slots on 4.4.2. I know it's difficult to find but the information is there. Thank you for trying to find it before posting.
EDIT: just so you're aware, I'm still on 4.2.2, so I haven't actually had any experience with SafeStrap on 4.4.2. I'm just relaying information I've read. So definitely do some reading before you do anything in case I'm wrong. If you have more questions I'll do my best to answer them, but make sure you fact check me because i wouldn't want to brick your phone.

Devo7v said:
You cannot use ROM slots with SafeStrap 3.73. You have to install ROMs to your stock ROM slot overwriting your stock ROM. So make a backup before you flash anything. The developer of SafeStrap took a new job and had to abandon development before he could fully implement ROM slots on 4.4.2. I know it's difficult to find but the information is there. Thank you for trying to find it before posting.
Click to expand...
Click to collapse
Yeah, if that information is out there, it's pretty deep. Like, Mariana's Trench deep. At least now it'll be up front. So basically, SafeStrap is a custom recovery in itself, bypassing the need for an unlocked bootloader?

Caboose27 said:
Yeah, if that information is out there, it's pretty deep. Like, Mariana's Trench deep. At least now it'll be up front. So basically, SafeStrap is a custom recovery in itself, bypassing the need for an unlocked bootloader?
Click to expand...
Click to collapse
same version of bootstrap. same prob here. and let me get this str8...over write stock rom slot? isnt that suppose to be like the "safe zone"

Caboose27 said:
Yeah, if that information is out there, it's pretty deep. Like, Mariana's Trench deep. At least now it'll be up front. So basically, SafeStrap is a custom recovery in itself, bypassing the need for an unlocked bootloader?
Click to expand...
Click to collapse
SafeStrap does not bypass the bootloader, it loads after the kernel loads so there is no way to install a custom kernel. This means that you can only use ROMs that are compatible with your stock kernel, no AOSP ROMs and no CM. You can only use TouchWiz-based ROMs.
harley1rocker said:
same version of bootstrap. same prob here. and let me get this str8...over write stock rom slot? isnt that suppose to be like the "safe zone"
Click to expand...
Click to collapse
That is the way it was intended to work, but Samsung changed some things in 4.4.2 and the developer didn't have time to reimplement ROM slots before he left.

Devo7v said:
SafeStrap does not bypass the bootloader, it loads after the kernel loads so there is no way to install a custom kernel. This means that you can only use ROMs that are compatible with your stock kernel, no AOSP ROMs and no CM. You can only use TouchWiz-based ROMs.
That is the way it was intended to work, but Samsung changed some things in 4.4.2 and the developer didn't have time to reimplement ROM slots before he left.
Click to expand...
Click to collapse
I got it working. I have the 4.4.2 kernel and the Graviton ROM flashed after using Safestrap to make a backup. After I flashed the rom, I wiped dalvik and cache, flashed the master patch v.2, wiped again, and rebooted. Everything works except the stock camera app, which I'm currently looking for a fix.

master patch link??

Devo7v said:
You cannot use ROM slots with SafeStrap 3.73. You have to install ROMs to your stock ROM slot overwriting your stock ROM. So make a backup before you flash anything. The developer of SafeStrap took a new job and had to abandon development before he could fully implement ROM slots on 4.4.2. I know it's difficult to find but the information is there. Thank you for trying to find it before posting.
EDIT: just so you're aware, I'm still on 4.2.2, so I haven't actually had any experience with SafeStrap on 4.4.2. I'm just relaying information I've read. So definitely do some reading before you do anything in case I'm wrong. If you have more questions I'll do my best to answer them, but make sure you fact check me because i wouldn't want to brick your phone.
Click to expand...
Click to collapse
DONT TRY OVERWRITING YOUR STOCK ROM SLOT WITH HYPERDRIVE ROM. YOU WILL LOSE SAFESTRAP AND IT BREAKS CAMERA WIFI,basiclly your phone wont work. Ive done it ant now have a s4 active paperweight. Ive tried odin and all the tar,pit and rar files you can find. NOTHIN WORKS. Before any1 says take it to bestbuy....i did. Kies and all the merry samsung reps culdnt put it back together. So before flashing anything over your stock rom slot make dam sure your a rocket scientist or at the very least a software engineer for samsung...

harley1rocker said:
DONT TRY OVERWRITING YOUR STOCK ROM SLOT WITH HYPERDRIVE ROM. YOU WILL LOSE SAFESTRAP AND IT BREAKS CAMERA WIFI,basiclly your phone wont work. Ive done it ant now have a s4 active paperweight. Ive tried odin and all the tar,pit and rar files you can find. NOTHIN WORKS. Before any1 says take it to bestbuy....i did. Kies and all the merry samsung reps culdnt put it back together. So before flashing anything over your stock rom slot make dam sure your a rocket scientist or at the very least a software engineer for samsung...
Click to expand...
Click to collapse
You need to flash the modules after flashing the ROM to get everything working again. Make sure you do it before you allow Hyperdrive to boot for the first time.
Also, in order to use Odin you cannot have Kies installed.

Devo7v said:
You need to flash the modules after flashing the ROM to get everything working again. Make sure you do it before you allow Hyperdrive to boot for the first time.
Also, in order to use Odin you cannot have Kies installed.
Click to expand...
Click to collapse
Way past that dude. The phone only allows me to enter into DL mode as of now. I know i was on ne3 htperdrive when this happened. Can you pls post a link for the correct tar file to use in odin? Ive tried most of those files but none worked. Can u post the correct ones for odin? May the software gods be with me....ima gonna need em....thanx dude

harley1rocker said:
Way past that dude. The phone only allows me to enter into DL mode as of now. I know i was on ne3 htperdrive when this happened. Can you pls post a link for the correct tar file to use in odin? Ive tried most of those files but none worked. Can u post the correct ones for odin? May the software gods be with me....ima gonna need em....thanx dude
Click to expand...
Click to collapse
Follow the instructions and you'll be fine. Remember, since you're on NE3 you can only flash NC9 or NE3.
http://forum.xda-developers.com/showthread.php?t=2835481

All ROM installs a failure except in the beginning

I'm an android ROM newbie, but an old computer geek from way back in the 80's, so I do have some kind of understanding. I own an ATT Note 3.
I've experienced only minor problems with the two main ROM flash tools, that is, Safestrap 3.x and Odin 3.x but that's probably my fault and they don't crash. But Safestrap? Oy vay! That works also, but in the final boot, black screen thereafter, after booting from ANY slot, whether it be stock slot of other slots. Thank God for the backup function and Odin.
But I digress. Right in the beginning of my flashing Odyssey, everything worked fine! Flashed Alliance ROM no problem, as well as Dynamic Kat.
Oh yeah. Confused about all those two letter abbreviations, there's no abbreviation key here on the forums?
I tried the other ROMS in the Note 3 Rom sections and stuck wit that, but then, under Safestrap, the machine would reboot to black screen! No matter what I did, wiping, rooting (of course), re-installing different versions of SafeStrap, from early 3.x versions to 3.75, nothing! Odin gets my machine back to it's (I THINK) original state.
Badly confused. Knox is fine at 0x0. Don't know how to move forward. I would like to continue to try different ROMS but the same thing keeps on happening. Hope someone can help me. If anyone wants some kind of log output, I can do that (just tell me how and where).
Thanks

David Sanborn said:
I'm an android ROM newbie, but an old computer geek from way back in the 80's, so I do have some kind of understanding. I own an ATT Note 3.
I've experienced only minor problems with the two main ROM flash tools, that is, Safestrap 3.x and Odin 3.x but that's probably my fault and they don't crash. But Safestrap? Oy vay! That works also, but in the final boot, black screen thereafter, after booting from ANY slot, whether it be stock slot of other slots. Thank God for the backup function and Odin.
But I digress. Right in the beginning of my flashing Odyssey, everything worked fine! Flashed Alliance ROM no problem, as well as Dynamic Kat.
I tried the other ROMS in the Note 3 Rom sections and stuck wit that, but then, under Safestrap, the machine would reboot to black screen! No matter what I did, wiping, rooting (of course), re-installing different versions of SafeStrap, from early 3.x versions to 3.75, nothing! Odin gets my machine back to it's (I THINK) original state.
Badly confused. Knox is fine at 0x0. Don't know how to move forward. I would like to continue to try different ROMS but the same thing keeps on happening. Hope someone can help me. If anyone wants some kind of log output, I can do that (just tell me how and where).
Thanks
Click to expand...
Click to collapse
Sounds like maybe your flashing kit kat over jellybean or the other way around. Make sure if you have going to different android versions you flash the right Odin files each time. And install the right right version of safe strape. Or you get black screens

David Sanborn said:
I'm an android ROM newbie, but an old computer geek from way back in the 80's, so I do have some kind of understanding. I own an ATT Note 3.
I've experienced only minor problems with the two main ROM flash tools, that is, Safestrap 3.x and Odin 3.x but that's probably my fault and they don't crash. But Safestrap? Oy vay! That works also, but in the final boot, black screen thereafter, after booting from ANY slot, whether it be stock slot of other slots. Thank God for the backup function and Odin.
But I digress. Right in the beginning of my flashing Odyssey, everything worked fine! Flashed Alliance ROM no problem, as well as Dynamic Kat.
Oh yeah. Confused about all those two letter abbreviations, there's no abbreviation key here on the forums?
I tried the other ROMS in the Note 3 Rom sections and stuck wit that, but then, under Safestrap, the machine would reboot to black screen! No matter what I did, wiping, rooting (of course), re-installing different versions of SafeStrap, from early 3.x versions to 3.75, nothing! Odin gets my machine back to it's (I THINK) original state.
Badly confused. Knox is fine at 0x0. Don't know how to move forward. I would like to continue to try different ROMS but the same thing keeps on happening. Hope someone can help me. If anyone wants some kind of log output, I can do that (just tell me how and where).
Thanks
Click to expand...
Click to collapse
We have two versions of safestrap and each one works with a different OS.
1.Safestrap 3.71: that works ONLY with jellybean roms. Use it (If your phone says "4.3 MI9, MJ5, or NB4" in your "about phone" in settings) to flash any jellybean rom. Read the title of any rom you're attempting to flash. If it says "4.4.2 KK or Kitkat or NC2" then stay away.
2. Safestrap 3.72/3.75 ([emoji118] this is recommended) that works ONLY with Kitkat roms. Use it (If your phone says "4.4.2 NC2" in your "about phone" in settings) to flash any Kitkat/NC2 rom. Read the title of any rom you're attempting to flash. If it says "4.3 jellybean or JB" then stay away.

K-alz said:
We have two versions of safestrap and each one works with a different OS.
1.Safestrap 3.71: that works ONLY with jellybean roms. Use it (If your phone says "4.3 MI9, MJ5, or NB4" in your "about phone" in settings) to flash any jellybean rom. Read the title of any rom you're attempting to flash. If it says "4.4.2 KK or Kitkat or NC2" then stay away.
2. Safestrap 3.72/3.75 ([emoji118] this is recommended) that works ONLY with Kitkat roms. Use it (If your phone says "4.4.2 NC2" in your "about phone" in settings) to flash any Kitkat/NC2 rom. Read the title of any rom you're attempting to flash. If it says "4.3 jellybean or JB" then stay away.
Click to expand...
Click to collapse
basicaly what he said.. and since you said you did dynamic kat and alliance.. sounds like you are on the nc2 with Kitkat..
So, best bet is going to be make sure you have ss 3.75 and only flash the kitkat roms.. Dynamic kat, Alliance, Tweaked, Firekat, and you should be fine.. just dont try and flash any that are JB
From my Fired-up Note Pro 12.2!

Thank you. A combo of Android version AND baseband at the end?
Are the version numbers I'm looking for, a combination of the Android version (4.4.2) and the end of the Baseband number (NC2)
Basically I tried everything and your suggestions should very very suspiciously like everything I've done But.. I will give it one more shot.
Any possibility of SafeStrap 3.72 would work as opposed to 3.75 not working?
warfenix said:
Sounds like maybe your flashing kit kat over jellybean or the other way around. Make sure if you have going to different android versions you flash the right Odin files each time. And install the right right version of safe strape. Or you get black screens
Click to expand...
Click to collapse
---------- Post added at 10:51 PM ---------- Previous post was at 10:35 PM ----------
Version 4.42. I'll give everything a shot here although, I've tried all of this but maybe I've missed something. Thank you for responding.
warfenix said:
Sounds like maybe your flashing kit kat over jellybean or the other way around. Make sure if you have going to different android versions you flash the right Odin files each time. And install the right right version of safe strape. Or you get black screens
Click to expand...
Click to collapse

bodycode said:
Are the version numbers I'm looking for, a combination of the Android version (4.4.2) and the end of the Baseband number (NC2)
Basically I tried everything and your suggestions should very very suspiciously like everything I've done But.. I will give it one more shot.
Any possibility of SafeStrap 3.72 would work as opposed to 3.75 not working?
---------- Post added at 10:51 PM ---------- Previous post was at 10:35 PM ----------
Version 4.42. I'll give everything a shot here although, I've tried all of this but maybe I've missed something. Thank you for responding.
Click to expand...
Click to collapse
yeah if you are seeing 4.4.2 and nc2 you are on KK.. just make sure you are on 3.75 and all should be ok with flashing..
if for some reason it is borked,, go down to carls thread for odin files and how to odin back to stock nc2 and then start over and you should be fine
From my Fired-up Note Pro 12.2!

NO good. 3.75/stock slot/Alliance ROM fails.
Same ****. Black screen.
David Sanborn said:
I'm an android ROM newbie, but an old computer geek from way back in the 80's, so I do have some kind of understanding. I own an ATT Note 3.
I've experienced only minor problems with the two main ROM flash tools, that is, Safestrap 3.x and Odin 3.x but that's probably my fault and they don't crash. But Safestrap? Oy vay! That works also, but in the final boot, black screen thereafter, after booting from ANY slot, whether it be stock slot of other slots. Thank God for the backup function and Odin.
But I digress. Right in the beginning of my flashing Odyssey, everything worked fine! Flashed Alliance ROM no problem, as well as Dynamic Kat.
Oh yeah. Confused about all those two letter abbreviations, there's no abbreviation key here on the forums?
I tried the other ROMS in the Note 3 Rom sections and stuck wit that, but then, under Safestrap, the machine would reboot to black screen! No matter what I did, wiping, rooting (of course), re-installing different versions of SafeStrap, from early 3.x versions to 3.75, nothing! Odin gets my machine back to it's (I THINK) original state.
Badly confused. Knox is fine at 0x0. Don't know how to move forward. I would like to continue to try different ROMS but the same thing keeps on happening. Hope someone can help me. If anyone wants some kind of log output, I can do that (just tell me how and where).
Thanks
Click to expand...
Click to collapse

NO good. 3.75 fails!
3.75 and Alliance utterly fails into black screen. Safestrap reboot screen does this, but the other button (restore) gets me back to all the other buttons. Stock slot has size of zero partition size after alliance installation.
warfenix said:
Sounds like maybe your flashing kit kat over jellybean or the other way around. Make sure if you have going to different android versions you flash the right Odin files each time. And install the right right version of safe strape. Or you get black screens
Click to expand...
Click to collapse

AFter creating another slot and wipe, system mounting errors.
System mount errors all over the place after creating another slot, and installing Alliance. What's going on here? Something's really screwed up.
e: unable to mount '/system'
e: unable to mount '/systemorig'
over and over again
Can't check permissions after FActory reset. Please boot rom and try again after you reboot into recovery.
David Sanborn said:
3.75 and Alliance utterly fails into black screen. Safestrap reboot screen does this, but the other button (restore) gets me back to all the other buttons. Stock slot has size of zero partition size after alliance installation.
Click to expand...
Click to collapse

David Sanborn said:
3.75 and Alliance utterly fails into black screen. Safestrap reboot screen does this, but the other button (restore) gets me back to all the other buttons. Stock slot has size of zero partition size after alliance installation.
Click to expand...
Click to collapse
I would simply restore back to mj5 and start over. I did this last night simply to reset my phone cause I flash way to much lol. I would give that a try though. Thread is in the general section

How to restore to Mj5?
How do I downgrade to Mj5 from KK4.2?
Thanks
warfenix said:
I would simply restore back to mj5 and start over. I did this last night simply to reset my phone cause I flash way to much lol. I would give that a try though. Thread is in the general section
Click to expand...
Click to collapse

David Sanborn said:
How do I downgrade to Mj5 from KK4.2?
Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2559715

I know what your problem is brother. This same crap happened to me. To a T! For some reason when u wipe system in safesteap, it wipes everything out. EVERYTHING. except data. I learned the hard way,like u. So when u flash roms, don't wipe system, only factory reset. I wipe it 3× every time. Then install your Rom. You will b fine. I haven't had one problem ever since I stopped wiping system. And no random reboots or anything, Roms now flash, and boot as they should. Hope this helps.

David Sanborn said:
How do I downgrade to Mj5 from KK4.2?
Thanks
Click to expand...
Click to collapse
Dude. If you're on NC2 then don't ever do the MJ5. It'll give the same problem. Just Odin the first four files from this thread http://forum.xda-developers.com/showthread.php?t=2838117 then root with towelroot/install busybox (make sure to install it from within the app as well) then install ss 3.72 or 3.75 then start flashing Kitkat roms.

K-alz said:
Dude. If you're on NC2 then don't ever do the MJ5. It'll give the same problem. Just Odin the first four files from this thread http://forum.xda-developers.com/showthread.php?t=2838117 then root with towelroot/install busybox (make sure to install it from within the app as well) then install ss 3.72 or 3.75 then start flashing Kitkat roms.
Click to expand...
Click to collapse
True but I think his problem is wiping system when he installs roms. If he's still not able to boot up right then ya he needs to use Odin and those files to get up and running again.
I just wish it was like the note 2. With unlocked bootloader and real twrp recovery.

zounduser said:
True but I think his problem is wiping system when he installs roms. If he's still not able to boot up right then ya he needs to use Odin and those files to get up and running again.
I just wish it was like the note 2. With unlocked bootloader and real twrp recovery.
Click to expand...
Click to collapse
These four files are as easy as it gets. Literally, put phone into download mode, load files to their respective slots then hit start. That's all. Saves you much bullshiz

K-alz said:
These four files are as easy as it gets. Literally, put phone into download mode, load files to their respective slots then hit start. That's all. Saves you much bullshiz
Click to expand...
Click to collapse
Oh I agree. I've had to do it. I'm saying going forward so it doesn't happen again.

4 files in odin flash, done that 15 times.
I've flashed Odin stock COUNTLESS times! When I go back to flash kitkat ROMS, same **** all over again. Unbelievable. I'm at my wits end. My phone DOES boot with the Odin files. But when flashing anything else with safestrap, black screen again.
K-alz said:
These four files are as easy as it gets. Literally, put phone into download mode, load files to their respective slots then hit start. That's all. Saves you much bullshiz
Click to expand...
Click to collapse

David Sanborn said:
I've flashed Odin stock COUNTLESS times! When I go back to flash kitkat ROMS, same **** all over again. Unbelievable. I'm at my wits end. My phone DOES boot with the Odin files. But when flashing anything else with safestrap, black screen again.
Click to expand...
Click to collapse
You used the files in the thread I gave you a couple of posts back and it didn't work? Man I hope you still have your warranty. Just flash back to stock and take your phone to the AT&T warranty center and make up and issue with your phone and tell them that you can't deal with your phone anymore and get you a new phone. They believe about anything. If that didn't work then head to bestbuy if there is one by you and ask them to reflash the system for you (that's of course after you flash back to stock).

Not a block screen on Odin and no trips.
Did I mention Odin works fine? Knox is not tripped. All is well right after Odin upload to phone in Download mode. It's only when I flash anything that blackscreen curses me again. heh heh.
K-alz said:
You used the files in the thread I gave you a couple of posts back and it didn't work? Man I hope you still have your warranty. Just flash back to stock and take your phone to the AT&T warranty center and make up and issue with your phone and tell them that you can't deal with your phone anymore and get you a new phone. They believe about anything. If that didn't work then head to bestbuy if there is one by you and ask them to reflash the system for you (that's of course after you flash back to stock).
Click to expand...
Click to collapse

G800H Duos - CM13 / 12.1 / Clone from identical phone

Hi,
I took the plunge and rooted + flashed my phone last week after finding that the CM13 ROM is supposed to support a G800H dual sim. Unfortunately CM13 doesn't find either of my SIM cards.
So I spent a long time reflashing other custom ROMs to see if I could get one to work. I finally managed to find the CM12.1 ROM which finds my SIM cards but the recent and back button isn't functioning and when I try to uninstall an app the phone reboots and the app remains.
Can anyone help me get one of these ROMs to work properly?
Alternatively, my wife has exactly the same phone as me (unrooted and running everything as the it was out of the box), is there a way I can clone her device to mine then factory reset it?
Thanks in advance.

Flash the first Russian Lollipop twice. Yes, it's weird but if you downgrade sometimes you need to flash it twice to fully downgrade, then flash CM. If you still can't get SIMs to work on stock Lollipop, downgrade to KitKat then use OTA to go to Lollipop.
About cloning, to do a full clone you need to use TWRP as far as I know.

@lfom
Thank you for your reply my friend.
I have resorted to using Samsung Smart Switch and re initialised my phone back to stock. I think I am out of my depth as I don't even understand your reply lol!
Thanks again!

jcwd said:
@lfom
Thank you for your reply my friend.
I have resorted to using Samsung Smart Switch and re initialised my phone back to stock. I think I am out of my depth as I don't even understand your reply lol!
Thanks again!
Click to expand...
Click to collapse
Sorry, I will try to explain. You've used Odin to root, right? You have to use Odin to flash any stock ROM that is not to the same country as your original ROM (different CSC code). All Marshmallow ROMs are based on the first Russian Lollipop ROM released by Samsung, that's why if you flash them over other ROMs you have problems like no SIM.

Ahhh I think that might be the problem! (Yes I used Odin.)
In the instructions it clearly says "1. Make sure you have updated to stock 5.1.1" - I didn't do that - what an idiot.
I take it when you say "flash any stock ROM" I need to get a 5.1.1 stock ROM - where would I get one of those from?
EDIT: would this be suitable? http://www.youmobile.org/blogs/entr...-Android-5-1-1-Lollipop-update-is-Rolling-out
Thanks for your persistence.

jcwd said:
Ahhh I think that might be the problem! (Yes I used Odin.)
In the instructions it clearly says "1. Make sure you have updated to stock 5.1.1" - I didn't do that - what an idiot.
I take it when you say "flash any stock ROM" I need to get a 5.1.1 stock ROM - where would I get one of those from?
EDIT: would this be suitable? http://www.youmobile.org/blogs/entr...-Android-5-1-1-Lollipop-update-is-Rolling-out
Thanks for your persistence.
Click to expand...
Click to collapse
To avoid issues, if you want to run any my CM13 (Marshmallow) ROM, you need to flash through Odin the first 5.1.1 Russian version, for what I said before. The common and easiest place, although slow, is from SamMobile website:
http://www.sammobile.com/firmwares/download/56934/G800HXXU1BOI2_G800HOXY1BOI2_SER/

@Ifom Thanks very much I will start the download when I get back from work and install it when it finishes (some time next week).
Thanks again.

I9305 FM Receiver

I've posted about this here and there but I think that I have enough data for a wide audience now.
Let me start at the beginning.
I got an international I9305 from the Nordic region about 2,5 years ago, can't remember exactly which build of Android was on it, but it had a stock FM tuner app which I've used at school to check if the FM transmitter we built over the course of a class project was working. Shortly after that instance I got an OTA update( to 4.3 or 4.4.4, sadly can't recall) after which the app disappeared and I lost FM functionality(I had trouble rooting at the time, so Spirit FM was not helpful)
Currently I'm on a custom stock-based ROM made by @MaHo_66 from his thread here, running the UFPB1 build on NEE CSC(Props to him for doing a fine work with these ROMs ), but either the ROM or AGNi do not implement drivers/libraries/dependencies for FM functionality.
So now I turn to you.
I'm searching for devs that have this device and/or are willing to help with this, I'm way past warranty and will try anything to restore FM functionality, just for the sake of proving that it works. (And maybe this thread helps other people who have this device)
How do I support my statements you ask?
The FM is built into the WiFi/BT chip, which is the BCM4334, or as Samsung references it, the SWB-B53, which is probably a modified/proprietary version of the BCM4334 made by Samsung itself, so not much info on it or a separate datasheet. So we know the chip is there, it's just a matter of gaining access to it. Though the service manual shows the connector to the FM antenna to be grounded, this might not be the case for every single motherboard (as I know mine has worked in the past, there's no way it's grounded(OR it's supposed to be because the headphones are used as the antenna, not sure on this one))
I've attached screenshots of the system info, SD Insider showing that the chip is in fact the one talked about earlier, and shots of the motherboard disassembled. The chip that's right under the power button is the one we're looking for. This proves that the hardware is there, we just need software to run it
Sorry for the long post and thanks for your time in advance, all responses are valued

I won't be able to help that much here but FYI here is an old thread (2012) about this topic in case you missed it: FM Radio Not in most I9305 Firmwares, But it may be Hardware capable.
I take the opportunity to say that your post itself is very clear, well explained and nicely documented and it's a good idea to start it, I really hope you will get some help.
:fingers-crossed:

I've seen that thread, but it seems that the folks back then didn't arrive to a conclusion, and there's not much helpful data on the topic
I've also seen threads like this and this, where there's a lot of speculation talk and little concrete helpful information
And thanks, I study electronics engineering, I am required to provide a lot of data in a clean, well documented manner

xda seems to be choking with traffic today

Nice work! Good to see how we started with a notion and then the process of elimination until we proved it :good::highfive:
The thread @Wood Man mentioned is the one I was referencing to you earlier .:good:
Sent from my Samsung GT-I9305 using XDA Labs

@AlexJumper: I fully concur with the statements of @Wood Man and @alias_ z3d!
Precise, comprehensive where necessary but always concise. I'd be glad if I could read more of such posts on XDA.
Don't know if this thread is helpful; found the thread yesterday after flashing a S3 Mini (i8190) with this ROM.
alias_ z3d said:
Cool I'll have a look and thank your post once I get some back. I think @noc.jfcbs would offer invaluable assistance since he's started a lot of threads I've only got one.
Click to expand...
Click to collapse
But here, alias_z3d is wrong. I've only started three threads and nothing special; maybe a forth is coming soon.
You don't require any support; the way you commenced this thread is excellent.:good:

Spirit FM would be a solution, but either the ROM or the kernel I'm running right now doesn't have drivers for FM, so it won't work for me
Basically I'm looking for a way to implement(port?) drivers from firmware that has them to my current ROM, or a way to flash said firmware through custom recovery.
I've tried to downgrade through Odin, but I've been unsuccessful up to this point.

AlexJumper said:
Spirit FM would be a solution, but either the ROM or the kernel I'm running right now doesn't have drivers for FM, so it won't work for me
Basically I'm looking for a way to implement(port?) drivers from firmware that has them to my current ROM, or a way to flash said firmware through custom recovery.
I've tried to downgrade through Odin, but I've been unsuccessful up to this point.
Click to expand...
Click to collapse
What's your problem with Odin? Maybe, someone or me can help? BTW. Which recovery are you using? What's your bootloader?

Before I tried fiddling with rooting and whatnot, I was on stock 4.4.4 so that's definitely the Knox bootloader, after that I got TWRP when Unified Android Toolkit got support for all I9305 builds, then I was able to flash whatever I tried to through TWRP.
I got back to a 4.1.1 build following instructions from this thread, which describes a SIM unlock procedure but it also promises that
You can update, Root, flash custom and stock rom and everything you want. It will stay unlocked
Click to expand...
Click to collapse
(Thinking about it again, I may have misunderstood that )
Anyways, then I got to flashing one of MaHo's ROMs, the build that I'm on right now is I9305XXUFPB1.
But when I was trying to downgrade to find a build that had FM functionality, in one instance I got bootlooping and no recovery access, in another Odin failed to flash(because of it trying to flash an older bootloader over Knox's bootloader) and I had to emergency recover via Smart Switch.
It flashed a newer build though, and since that, every time I flash older firmware through I get bootloops. (Or I just suck at making Odin-flashable packages )
Here's what UAT has to say, seems like I have the latest bootloader now
Oh and I currently have TWRP 2.6.3.0 as custom recovery

noc.jfcbs said:
@AlexJumper: I fully concur with the statements of @Wood Man and @alias_ z3d!
Precise, comprehensive where necessary but always concise. I'd be glad if I could read more of such posts on XDA.
Don't know if this thread is helpful; found the thread yesterday after flashing a S3 Mini (i8190) with this ROM.
But here, alias_z3d is wrong. I've only started three threads and nothing special; maybe a forth is coming soon.
You don't require any support; the way you commenced this thread is excellent.:good:
Click to expand...
Click to collapse
Yes he doesn't need support it looks great I said that in regards to structuring a thread before I checked it out
I think your being modest considering you've got one pinned
Sent from my Samsung GT-I9305 using XDA Labs

AlexJumper said:
Before I tried fiddling with rooting and whatnot, I was on stock 4.4.4 so that's definitely the Knox bootloader, after that I got TWRP when Unified Android Toolkit got support for all I9305 builds, then I was able to flash whatever I tried to through TWRP.
I got back to a 4.1.1 build following instructions from this thread, which describes a SIM unlock procedure but it also promises that
(Thinking about it again, I may have misunderstood that )
Anyways, then I got to flashing one of MaHo's ROMs, the build that I'm on right now is I9305XXUFPB1.
But when I was trying to downgrade to find a build that had FM functionality, in one instance I got bootlooping and no recovery access, in another Odin failed to flash(because of it trying to flash an older bootloader over Knox's bootloader) and I had to emergency recover via Smart Switch.
It flashed a newer build though, and since that, every time I flash older firmware through I get bootloops. (Or I just suck at making Odin-flashable packages )
Here's what UAT has to say, seems like I have the latest bootloader now
View attachment 4168400
Oh and I currently have TWRP 2.6.3.0 as custom recovery
Click to expand...
Click to collapse
In the attached screenshot you see my Bootloader I9305XXUEMKC, I think it's still the one from 4.3 JB. And I definitely suggest to upgrade TWRP to 3.0.2-1 that I also use. I personally won't go to higher custom TWRP versions that are out, because I read about some issues with them; e.g. @alias_ z3d had issued a warning in rodman01's RR thread.
How about just to flash through Odin Chainfire's CF-Auto-Root for Android 4.1.1 again, and - if that works - to start from there
samsung
GT-I9305 m3zh m3 smdk4x12 exynos4 JRO03C.I9305ZHALI8 4.1.1 18 650 167 Download 8319b7feffffdc083ef73450acb1d145 476 430
Click to expand...
Click to collapse
Finally, this week I just rooted an i8190 via Odin and had initially a bad experience but finally a very easy solution. At the end of the ROM flash by Odin, the device automatically booted into system as this was ticked in Odin. It was constantly booting, I assume a bootloop, and after about 2 hours I lost patience. Took the battery out, inserted it again, and started into recovery (home+vol up+pwr). At that time, still the stock recovery was installed i.e. no real capabilities. But at least, I could wipe cache and data. Did that and initiated a boot into system. And that was it. Booting took about 2 minutes, and I had a rooted i8190. Next thing I did, was to flash TWRP 3.0.1 onto the i8190 by Heimdall.

So my course of action is:
1) Go back to 4.1.1
2) Flash CF Auto Root
3) Flash TWRP
4) Flash whatever else
Am I correct?

AlexJumper said:
So my course of action is:
1) Go back to 4.1.1
2) Flash CF Auto Root
3) Flash TWRP
4) Flash whatever else
Am I correct?
Click to expand...
Click to collapse
Affirmative. If I had to play with this device I'd try the following but not knowing if it works:
NO WARRANTY - Use at your own risk, I'm not responsible for bricking your device.
Flash the above linked CF AutoRoot tar.md5-file through Odin, which hopefully reverts you to the desired 4.1.1 (unless this file works try the other CF AutoRoot for 4.4.4 - that's actually the one, with which I rooted an i9305 months ago)
Flash TWRP 3.0.2-1 via Odin or apps like Flashify (the one I use) or Flashfire etc.
Further flashes depend on your desire. Other ROM (hopefully with FM radio drivers), baseband/modem etc.
Instead of using Odin you could certainly also take Heimdall. I used Heimdall only once thus far for the mentioned i8190 to flash a TWRP-3.0.1.img (explained here and here a bit more in detail).
I searched the web like hell for Samsung ROM FM radio driver but no joy.

Ok so I got back to the 4.1.1 build from the thread I linked in my previous post, apparently my bootloader somehow changed..
The CF Auto Root file though seems to be based on a slightly different build than the one I've got now (JRO03C.I9305ZHALI8 while I have JRO03C.I9305XXALI5), should I flash it or is there a possibility it breaks something?
Nevermind, it worked flawlessly
I also updated TWRP to 3.0.2-1.
Now to find a way to get to the builds I need

AlexJumper said:
Ok so I got back to the 4.1.1 build from the thread I linked in my previous post, apparently my bootloader somehow changed..
View attachment 4169145
The CF Auto Root file though seems to be based on a slightly different build than the one I've got now (JRO03C.I9305ZHALI8 while I have JRO03C.I9305XXALI5), should I flash it or is there a possibility it breaks something?
Click to expand...
Click to collapse
Super. I thought the main intention was to bring the device back to 4.1.1, and that was accomplished.
Is it (still) rooted?
If it is, I wouldn't continue with CF-AutoRoot as its only purpose is to get a device rooted.
If you still need root, I personally would continue but I don't know if you might brick the phone.

noc.jfcbs said:
Super. I thought the main intention was to bring the device back to 4.1.1, and that was accomplished.
Is it (still) rooted?
If it is, I wouldn't continue with CF-AutoRoot as its only purpose is to get a device rooted.
If you still need root, I personally would continue but I don't know if you might brick the phone.
Click to expand...
Click to collapse
No, I needed to get back to 4.1.1 as a start because flashing older builds was a pain with 4.4.4 and its bootloader.

AlexJumper said:
No, I needed to get back to 4.1.1 as a start because flashing older builds was a pain with 4.4.4 and its bootloader.
Click to expand...
Click to collapse
The e.g. i8190 has a FM receiver. Maybe it works if you grab some commits from firmware of the i8190 and incorporate it into your ROM. I know you can't compare S3 LTE and S3 Mini with their totally different hardwares but...

That would require them to have the same FM chip at least(which I doubt), as well as libraries/dependencies I guess.

noc.jfcbs said:
In the attached screenshot you see my Bootloader I9305XXUEMKC, I think it's still the one from 4.3 JB. And I definitely suggest to upgrade TWRP to 3.0.2-1 that I also use. I personally won't go to higher custom TWRP versions that are out, because I read about some issues with them; e.g. @alias_ z3d had issued a warning in rodman01's RR thread.
Click to expand...
Click to collapse
3.1.1-0 was not a custom TWRP!
It was official

Iller Chiller said:
3.1.1-0 was not a custom TWRP!
It was official
Click to expand...
Click to collapse
Yeah it was officiall twrp 3.1.1-0 for me from team win website. However I don't think I made it clear in my post.
Sent from my Samsung GT-I9305 using XDA Labs