Related
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:
So I finally got me a sweet deal and got a second hand XT1053.
Unlocked its bootloader, then flashed T-Mobile´s 4.4.3 and finally the OTA to 4.4.4, because here in Mexico all I was able to get was 4.4.2.
Now, I want to try custom ROMs, and Ive been reading about the procedure.
As any sane person would, I want a nandroid backup before messing around. Im guessing flashing TWRP will take care of this, like it did with my LG L9, right?
Is it wise to do this on the verge of Android L being ported to our Moto X?
How difficult is it to get the phone to a fully stock state (minus the bootlader, of course)? As far as I know, I only need to flash my nandroid backup then flash the stock recovery. Is it as simple as that?
I read somewhere that flashing custom ROMs messed up with Motorola´s active display/voice control, and I assumed they meant that custom ROMs lacked these features because of their proprietary nature. Am I correct? Or does some kind of unrepairable damage will forever afflict these features, even if I get back to stock?
And lastly, what ROM do you recommend? I´d like the active display feature if possible, guess I can do without it. CM theme chooser would be nice too.
Thanks in advance, eagerly awaiting some answers before I take a step forwards.
Attached a screenshot of my phone´s info.
You are right about everything you've mentioned. Good research done for sure! ?
Do a backup with twrp. And yes, you can restore it and flash the stock recovery and you're good for the OTA.
Aosp/cm roms don't have the Moto features. But yes, you can return to stock and have them again. There's a few stick based custom roms that of course still have the features. The other roms, unless something changed, do come with some bugs unfortunately as well.
Most use stock, with gravity box for customizing.
And in case you missed it.... Never try to downgrade from 4.4.4....or you risk your device bricking. You can flash lower version custom roms, cause they won't try to change the bootloader. But don't downgrade stock firmware. Ever. ?
Enjoy!
Thank you very much!
As soon as I read this I rooted my phone, I´ll check a ROM or two before settling on one for daily use, have heard nice things about krypto´s one.
And yeah, there can never be enough warnings, I´ll treat the T-Mobile stock ROM as if it were my very first one.
One question though, the latest version of T-Mobile firmware is 4.4.3 under http://sbf.droid-developers.org/phone.php?device=0 so Im gussing I should only use my nandroid backup, right?
Thanks in advance!
no_un_bot said:
Thank you very much!
As soon as I read this I rooted my phone, I´ll check a ROM or two before settling on one for daily use, have heard nice things about krypto´s one.
And yeah, there can never be enough warnings, I´ll treat the T-Mobile stock ROM as if it were my very first one.
One question though, the latest version of T-Mobile firmware is 4.4.3 under http://sbf.droid-developers.org/phone.php?device=0 so Im gussing I should only use my nandroid backup, right?
Thanks in advance!
Click to expand...
Click to collapse
Until there's a 4.4.4 SBF, yes. That's the safest bet.
newbie needs details
no_un_bot said:
So I finally got me a sweet deal and got a second hand XT1053.
Unlocked its bootloader, then flashed T-Mobile´s 4.4.3 and finally the OTA to 4.4.4, because here in Mexico all I was able to get was 4.4.2.
Now, I want to try custom ROMs, and Ive been reading about the procedure.
As any sane person would, I want a nandroid backup before messing around. Im guessing flashing TWRP will take care of this, like it did with my LG L9, right?
Is it wise to do this on the verge of Android L being ported to our Moto X?
How difficult is it to get the phone to a fully stock state (minus the bootlader, of course)? As far as I know, I only need to flash my nandroid backup then flash the stock recovery. Is it as simple as that?
I read somewhere that flashing custom ROMs messed up with Motorola´s active display/voice control, and I assumed they meant that custom ROMs lacked these features because of their proprietary nature. Am I correct? Or does some kind of unrepairable damage will forever afflict these features, even if I get back to stock?
And lastly, what ROM do you recommend? I´d like the active display feature if possible, guess I can do without it. CM theme chooser would be nice too.
Thanks in advance, eagerly awaiting some answers before I take a step forwards.
Attached a screenshot of my phone´s info.
Click to expand...
Click to collapse
hello, i a newbie to all of this
i have the same device as yours, how did you do that? details if it not much trouble
sherif2015 said:
hello, i a newbie to all of this
i have the same device as yours, how did you do that? details if it not much trouble
Click to expand...
Click to collapse
Hi there, Im at work and cannot explain in much detail, but when I get home i will help you out.
You can send me a private message if you want me to explain in español.
no_un_bot said:
Thank you very much!
As soon as I read this I rooted my phone, I´ll check a ROM or two before settling on one for daily use, have heard nice things about krypto´s one.
And yeah, there can never be enough warnings, I´ll treat the T-Mobile stock ROM as if it were my very first one.
One question though, the latest version of T-Mobile firmware is 4.4.3 under http://sbf.droid-developers.org/phone.php?device=0 so Im gussing I should only use my nandroid backup, right?
Thanks in advance!
Click to expand...
Click to collapse
SBF.Droid-Developers.org hasn't been updated in a while, at least as far as the X (2013 or 1st Gen edition) Roms.
Another possible source is -> http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=100&page=1 however, they don't have a 4.4.4 SBF for the XT1053 either.
And you can keep an eye on https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images since Moto should post the 4.4.4 SBF for the Developer Editions. Eventually an XT1053 (GSM) and an XT1060(VZW) 4.4.4 should pop up there, whenever Moto finally gets around to it.
no_un_bot said:
Hi there, Im at work and cannot explain in much detail, but when I get home i will help you out.
You can send me a private message if you want me to explain in español.
Click to expand...
Click to collapse
Hi sorry for bothering you but i really need your help.
English will be fine .
other users might get here so it will be nice to help them as well
thanks for your time
sherif2015 said:
Hi sorry for bothering you but i really need your help.
English will be fine .
other users might get here so it will be nice to help them as well
thanks for your time
Click to expand...
Click to collapse
Alright, guess everything is out there but I don´t mind.
Can you tell me what system version have you got?
Its displayed under Settings > About phone
reply
no_un_bot said:
Alright, guess everything is out there but I don´t mind.
Can you tell me what system version have you got?
Its displayed under Settings > About phone
Click to expand...
Click to collapse
Kitkat 4.4.2 xt1053
same phone, problems loading roms
I have the same phone, I also recently got second hand.
Moto x xt1053 (gsm) carrier unlocked, currently in kitkat4.4.2, running Kangakat 2 rom (came with it), unlocked bootloader, rooted and using SuperSU, newest version of twrp like 2.8 or something like that.
I want to load a custom rom but am having problems, downloaded P.A.C. and AOKP (two i have tried to use) for the device msm8960 using there stable versions not the nightlies. Went into twrp, created backup, factory wiped, flashed rom and g-apps, was "successful" no errors but on reboot of phone it gets stuck in boot loop and won't start up. for the P.A.C i was able to get into twrp and reflash my back up, for the AOKP twrp kept getting stuck on that teamwin image and i could only finally access it by having the usb cable plugged into my computer. I am not a noob, but definately not an expert.
So did you have any luck flashing a new rom to your phone? Does anyone have any advice for me? I really would like to try some different roms.
Thanks
[emoji15]
I hate Tapatalk for all the time spent writing a quick reply and its gone.
Anyways, first of all, make sure you have the latest recovery available, I remember back with my old phone, funky installations happened if you weren't on the latest recovery. I recommend philz one, has support for some pesky partitions that sometimes get messed and other recoveries won't back up.
Now, in my particular case, I first upgraded my 4.4.2 Nextel stock to 4.4.3 T-Mobile stock using RSDLite, then took the OTA to 4.4.4, and until then I figured I'd play with ROMs. Have had no issues other than something I've addressed on another thread and I ultimately fixed.
My suggestion is going back to full stock then doing everything yourself so you know what's actually going on.
You'll have to flash a custom recovery and then root it again but with an unlocked bootloader that's ezpz.
Remember never to downgrade (that is, flashing a lower android version than what you currently run) stock official images (such as the ones from sbf-developers) because you WILL brick your phone. People say you can downgrade when flashing custom ROMs but I wouldn't risk it, and I don't really see why I'd want that.
Double check whatever file you'll try to flash, always use stuff intended for your model, and when that's not possible verify if other users with your model have reported it works for them. As per the version thing, I believe the most recent development unified models under the GHOST parameter but take my words for what they are, that is, my view on things, you should always make one for yourself.
Ask if you don't completely understand a step BEFORE doing it, there's good people willing to help you out.
Best of luck.
I need some help here, and I need to stop bothering the guys in the ROM forum about it so I'm asking here instead.
It's a t-mobile note 4. I was running Dynamic Kat on it and it was suggested I update the modem and bootloader with a partial flash file. Now my phone is stuck in a bootloop.
I CAN get into both download mode and TWRP, however, so it seems like this should be fixable. I'd be happy with even going back to fully stock and rerooting it.
I found this thread: http://forum.xda-developers.com/not...to-downgrade-cod6-to-nk4-upgrade-nk4-t3095585 which seems to about flashing back to stock NK4 or cod6. I know those are bootloaders, but I don't really understand what they mean beyond that.
Or can I just flash to the new stock lollipop t-mobile put out this week? If so, how? If anyone has the time to help me with this, I would really appreciate it.
Edit: I found instructions on sammobile.com. Going to try them. *fixed
Caelrie said:
I need some help here, and I need to stop bothering the guys in the ROM forum about it so I'm asking here instead.
It's a t-mobile note 4. I was running Dynamic Kat on it and it was suggested I update the modem and bootloader with a partial flash file. Now my phone is stuck in a bootloop.
I CAN get into both download mode and TWRP, however, so it seems like this should be fixable. I'd be happy with even going back to fully stock and rerooting it.
I found this thread: http://forum.xda-developers.com/not...to-downgrade-cod6-to-nk4-upgrade-nk4-t3095585 which seems to about flashing back to stock NK4 or cod6. I know those are bootloaders, but I don't really understand what they mean beyond that.
Or can I just flash to the new stock lollipop t-mobile put out this week? If so, how? If anyone has the time to help me with this, I would really appreciate it.
Edit: I found instructions on sammobile.com. Going to try them.
Click to expand...
Click to collapse
Easy fix. ODIN flash the stock COD6 software. Then start over again with cf auto root. There is a thread that had all of the files you need in one zip.
Sent from my SM-N910T using XDA Free mobile app
Yayyy I think it worked! Stock Lollipop is booting up. It's in the Optimizing apps phase.
Caelrie said:
Yayyy I think it worked! Stock Lollipop is booting up. It's in the Optimizing apps phase.
Click to expand...
Click to collapse
Are you the same one who renamed the tar.md5 file to tar? If so, when you ask for help you really should mention all the steps you took to get there. Where it went wrong, etc.
When in doubt, Odin flash full firmware to get back to stock. There are other steps you could have taken as well but Odin is almost always a surefire bet.
(Also remember to hit the thanks button for those who have helped you get things sorted, like that fella above and the people who helped you in the rom thread- not me of course because I didn't do anything but for those who did I'm sure they would appreciate it)
absinthesummer said:
Are you the same one who renamed the tar.md5 file to tar? If so, when you ask for help you really should mention all the steps you took to get there. Where it went wrong, etc.
When in doubt, Odin flash full firmware to get back to stock. There are other steps you could have taken as well but Odin is almost always a surefire bet.
(Also remember to hit the thanks button for those who have helped you get things sorted, like that fella above and the people who helped you in the rom thread- not me of course because I didn't do anything but for those who did I'm sure they would appreciate it)
Click to expand...
Click to collapse
Yah, that was me. I came over here to ask for help instead because I shouldn't be bothering you guys in the ROM thread. I was making progress though. By the time I made this thread, I'd figured out that if I could get into TWRP or download mode, I could odin my way out of it. Just needed some help on that doing that, but then I figured that out too thanks to sammobile
Caelrie said:
Yah, that was me. I came over here to ask for help instead because I shouldn't be bothering you guys in the ROM thread. I was making progress though. By the time I made this thread, I'd figured out that if I could get into TWRP or download mode, I could odin my way out of it. Just needed some help on that doing that, but then I figured that out too thanks to sammobile
Click to expand...
Click to collapse
Cool, glad you got it sorted. Yeah as long as you can access download mode you're golden, and a bonus if you can get into recovery as well.
Excellent job actually searching and reading and fixing your problem, far too many people want answers just handed to them, so kudos to you for that.
Just for the future if you need help, try to remember and list all steps you took (even if you don't know where you went wrong) in excruciating detail because it helps us troubleshoot and figure out what the problem is. Without certain pertinent info it could take a lot longer to solve it.
Overall good job, glad you're up & running.
Go to rapture download the rom and load it to sd card. Then follow directions exactly and u will be ok. No loading anything. Fresh start
BAD ASS NOTE 4
I am in the same boat with the boot loop. I flashed the partial firmware file as well and I did not rename it and the flash went fine. After that it boot to the screen that says powered by Android then it reboots over and over. Currently downloading the stock cod so I can odin that.
ElAguila said:
I am in the same boat with the boot loop. I flashed the partial firmware file as well and I did not rename it and the flash went fine. After that it boot to the screen that says powered by Android then it reboots over and over. Currently downloading the stock cod so I can odin that.
Click to expand...
Click to collapse
Technically you shouldn't be flashing just the partial firmware. It sets up a base so that you can flash a lollipop rom in recovery without issues. I'm not sure why someone is recommending just flashing the partial firmware only. I guess they figured it wouldn't cause issues.
Anyway, here is how the partial firmware should be used:
Flash partial firmware in Odin
Flash flashable stock lollipop in recovery.
Set up rom, make a backup.
From here you can restore your old kitkat backups without the problems that some are seeing (those who Odin the full firmware are having problems restoring kitkat backups/flashing kitkat roms without Odining ank4 first). The partial firmware prevents that but it's designed to be flashed right before flashing a lollipop rom.
I hope that helps some of you who are having issues.
So I've tried installing the various 6.0.1-based ROMs, but every single install results in my phone not detecting my SIM cards. I've looked around for a bit on the various subforums, and it might have something to do with the baseband-version I'm using. Unfortunately, I can't find a single post that explains which version I need or whats steps I need to follow. I've tried these:
Using Odin, first I flashed this stock Indian 4.4.2
Followed by this stock Indian 5.5.1
Flash TWRP via Odin, full wipe and install a 6.0.1 custom ROM + GApps via TWRP
I've also tried a variation with the Russian 4.4.2 / 5.5.1 branch, but no luck there either.
In the end, my G800H will boot up fine, do the whole "starting apps" process and launches the ROM setup introduction, but it fails to detect any of the inserted SIM cards.
I can restore an older version just fine and the SIMs will function again, so I'm guessing it has to do with the firmware... Can anyone tell me which firmwares I need to flash and in which order? Or should I wait till a western European 6.0.1 firmware is released?
Thanks in advance for any help you can give!
You have G800H dual sim, right? Then you need the first Russian Lollipop ROM, which ends in BOI2. You may need to flash it twice to make sure you have the correct bootstack. If your SIMs aren't working with it then first install KitKat (twice again, if needed) then go to Lollipop. Then flash TWRP and then custom ROM.
lfom said:
You have G800H dual sim, right? Then you need the first Russian Lollipop ROM, which ends in BOI2. You may need to flash it twice to make sure you have the correct bootstack. If your SIMs aren't working with it then first install KitKat (twice again, if needed) then go to Lollipop. Then flash TWRP and then custom ROM.
Click to expand...
Click to collapse
Heya, I remember you giving me this reply in another thread (The SlimROM one? Can't recall).
So just to be sure, you mean this order?:
2 x Russian 4.4.2
2 x Russian 5.1.1
Custom ROM
I'll give it a shot, but I doubt these will work - why do I need to flash the same ROM twice? Is this described somewhere? Some file that doesn't get written in the first pass?
Thanks again!
Welp, apparently I'm an idiot. I did what I described above here, and it worked - both SIM cards were detected and everything works perfectly fine (CM 13 by JackEagle). Thanks again for your advice, @lfom - I was skeptical, but flashing the files twice seemed to have done the trick, for some reason I still don't understand.
lfom said:
You have G800H dual sim, right? Then you need the first Russian Lollipop ROM, which ends in BOI2. You may need to flash it twice to make sure you have the correct bootstack. If your SIMs aren't working with it then first install KitKat (twice again, if needed) then go to Lollipop. Then flash TWRP and then custom ROM.
Click to expand...
Click to collapse
Is there only one version that is dual sim? I got G800HXXU1ANK2 will it works with mine?
SomeDuder said:
Welp, apparently I'm an idiot. I did what I described above here, and it worked - both SIM cards were detected and everything works perfectly fine (CM 13 by JackEagle). Thanks again for your advice, @lfom - I was skeptical, but flashing the files twice seemed to have done the trick, for some reason I still don't understand.
Click to expand...
Click to collapse
Many reported downgrade success only after second flash. My guess is Odin gets confused somehow with downgrades and only flashes the full ROM after detecting partitions flashed the first time.
---------- Post added at 05:00 AM ---------- Previous post was at 04:59 AM ----------
Blackrabbit99 said:
Is there only one version that is dual sim? I got G800HXXU1ANK2 will it works with mine?
Click to expand...
Click to collapse
Sorry, I don't understand your question, please elaborate.
Blackrabbit99 said:
Is there only one version that is dual sim? I got G800HXXU1ANK2 will it works with mine?
Click to expand...
Click to collapse
I have no idea how many versions of the G800H/DS there are (Maybe some branded versions by AT&T, Verizon, etc), but unless you bought it from a provider, you probably have an international version. And yes, that is the first firmware you will need to flash - make sure you flash it twice, followed by G800HXXU1BOI2, also twice. After that, use Odin to flash TWRP again and install whatever custom ROM you want (After a full wipe, of course).
Like I said in the SlimROM thread, it's pretty hard to brick these Samsung Androids. While the stock Samsung ROM may be crap, the bootloader, in combination with Odin, will pretty much always allow you to recover your phone. Just make sure you don't do anything dumb like pulling the power or dataconnection while writing and you'll be fine
lfom said:
Many reported downgrade success only after second flash. My guess is Odin gets confused somehow with downgrades and only flashes the full ROM after detecting partitions flashed the first time.
Click to expand...
Click to collapse
Well, that's as good an explaination as any, thanks! :highfive: I only hope this thread helps other G800H users who want to upgrade.
amazing! thanks for posting this fix... i spent 36+ hours over 2.5 days trying to fix this! don't think i've rebooted so much in my life!
initially i was double flashing with a Polish 4.4.2 before the russian 5.1.1 BOI2 but it didn't work until i used the exact same base roms in SomeDuder's post... then i used resurrection remix 6.0.1
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