Database Develop

[Q] Moving from CM11 back to Stock or Otherwise

Hi all,
I have been using CM11 (http://forum.xda-developers.com/showthread.php?t=2494684) for awhile and hoping that they'd fix it so I wouldn't have to go back to stock or install a new ROM, but it seems that isn't going to happen. I guess I'm a beginner with this stuff, only because I only really dig in about twice a year and so I forget everything I learned the last time I had dealt with it.
I'm currently using a nightly from a few weeks ago (haven't bothered updating since... I don't think they're updating them) and I would like to either go back to completely stock and get OTA updates again, or move to another stable ROM. I had a backup from when I first rooted, but have since lost it. I have tried to find out what steps I need to take, but everything in these forums is all over the place and IF this THEN this, and Verizon specifically has to follow these steps, blah blah blah. Long story long, it's very confusing to me and at this point I think I have to follow 4 different guides entirely to get back to something that works (Which makes me think I'm missing something very simple). I figured I'd post and get a direct response to my specific situation.
Android version 4.4.4
Baseband version 11A
Recovery ClockworkMod 6.0.4.4
(Not sure this will help or not, but figured it's worth adding)
I did at one point have TWRP installed, but I had changed it at some point for... Some reason, no idea at this point. I think part of my frustration with trying to fix this is that some instructions tell me to have at least some specific version of TWRP (2.7?) installed, but I could never get it to work. The files for earlier versions were .img and the newer versions were .zips I think, and the process would always error out, no matter what I tried. (extracting contents, using the .img within, changing .zip to .img, maybe others, this was months ago)
Ultimately, I'd like to go to a stable ROM rather than stock, but I really don't want to have to spend hours working on this. I have already spent time looking at different threads piecing together what I need to do and I'm not at all confident that what I've come up with is the easiest or correct way for me to do this. Some people may say "the instructions are on the first post of whatever ROM you want". While that is true, when I have to be on a specific baseband or some such and directions are referenced but aren't linked, and I have to start digging, I lose confidence.
Aaaannyway, if anyone could help I would VERY MUCH APPRECIATE IT. I have been dealing with daily crashes for way too long.

Nicholo said:
Hi all,
I have been using CM11 (http://forum.xda-developers.com/showthread.php?t=2494684) for awhile and hoping that they'd fix it so I wouldn't have to go back to stock or install a new ROM, but it seems that isn't going to happen. I guess I'm a beginner with this stuff, only because I only really dig in about twice a year and so I forget everything I learned the last time I had dealt with it.
I'm currently using a nightly from a few weeks ago (haven't bothered updating since... I don't think they're updating them) and I would like to either go back to completely stock and get OTA updates again, or move to another stable ROM. I had a backup from when I first rooted, but have since lost it. I have tried to find out what steps I need to take, but everything in these forums is all over the place and IF this THEN this, and Verizon specifically has to follow these steps, blah blah blah. Long story long, it's very confusing to me and at this point I think I have to follow 4 different guides entirely to get back to something that works (Which makes me think I'm missing something very simple). I figured I'd post and get a direct response to my specific situation.
Android version 4.4.4
Baseband version 11A
Recovery ClockworkMod 6.0.4.4
(Not sure this will help or not, but figured it's worth adding)
I did at one point have TWRP installed, but I had changed it at some point for... Some reason, no idea at this point. I think part of my frustration with trying to fix this is that some instructions tell me to have at least some specific version of TWRP (2.7?) installed, but I could never get it to work. The files for earlier versions were .img and the newer versions were .zips I think, and the process would always error out, no matter what I tried. (extracting contents, using the .img within, changing .zip to .img, maybe others, this was months ago)
Ultimately, I'd like to go to a stable ROM rather than stock, but I really don't want to have to spend hours working on this. I have already spent time looking at different threads piecing together what I need to do and I'm not at all confident that what I've come up with is the easiest or correct way for me to do this. Some people may say "the instructions are on the first post of whatever ROM you want". While that is true, when I have to be on a specific baseband or some such and directions are referenced but aren't linked, and I have to start digging, I lose confidence.
Aaaannyway, if anyone could help I would VERY MUCH APPRECIATE IT. I have been dealing with daily crashes for way too long.
Click to expand...
Click to collapse
There isn't any developers for cm11 unless you go to some of the unofficials. There is no one to do the work. If your wanting a stable rom check out mahdi works great.

simple_fear85 said:
There isn't any developers for cm11 unless you go to some of the unofficials. There is no one to do the work. If your wanting a stable rom check out mahdi works great.
Click to expand...
Click to collapse
If I'm reading things correctly, in order to use Mahdi I need to...
1) Wipe everything but internal storage.
2) Flash the 11A Kitkat modem for the JB baseband. (I think that makes sense?) (Based on this post) Or maybe I'm supposed to use Cloudyfa's KK modem?
3) Flash Mahdi.
4) Flash patch.
5) Flash Gapps.
Am I close or way off? I guess the modem and baseband stuff is confusing me the most.

If you want to stick to CM11, you can upgrade your baseband to 24A and use jackpotclavin's build, it works well but it hasn't been updated past 4.4.2 I believe.

Nicholo said:
If I'm reading things correctly, in order to use Mahdi I need to...
1) Wipe everything but internal storage.
2) Flash the 11A Kitkat modem for the JB baseband. (I think that makes sense?) (Based on this post) Or maybe I'm supposed to use Cloudyfa's KK modem?
3) Flash Mahdi.
4) Flash patch.
5) Flash Gapps.
Am I close or way off? I guess the modem and baseband stuff is confusing me the most.[/QUOTE
no go to xdabbes follow his stock method then go back to twrp flash mahdi, the patch, and then gapps
All aosp roms now that are 4.4.4 are running the 24a bootstack or kitkat.
Click to expand...
Click to collapse

no go to xdabbes follow his stock method then go back to twrp flash mahdi, the patch, and then gapps
Click to expand...
Click to collapse
Okay, now this is where I run into the TWRP problem I mentioned. I can't get TWRP 6.3.3+ installed because the file is a zip, and no matter what I do with it (extracting contents and using the .img within, changing .zip to .img) I get some error. I don't actually know what it is off the top of my head, but I tried to do it more than once in the past and always ran into the same problem.

Nicholo said:
Okay, now this is where I run into the TWRP problem I mentioned. I can't get TWRP 6.3.3+ installed because the file is a zip, and no matter what I do with it (extracting contents and using the .img within, changing .zip to .img) I get some error. I don't actually know what it is off the top of my head, but I tried to do it more than once in the past and always ran into the same problem.
Click to expand...
Click to collapse
You use autorec for twrp?
Sent from my LG-VS980 using XDA Free mobile app

Nicholo said:
Okay, now this is where I run into the TWRP problem I mentioned. I can't get TWRP 6.3.3+ installed because the file is a zip, and no matter what I do with it (extracting contents and using the .img within, changing .zip to .img) I get some error. I don't actually know what it is off the top of my head, but I tried to do it more than once in the past and always ran into the same problem.
Click to expand...
Click to collapse
Do you have a custom recovery? If so, flash the 2.7.x.x zip within your current recovery, then reboot recovery. If you don't have a custom recovery, then use autorec or freedom tool to install one.
Sent from my VS980 4G using XDA Premium 4 mobile app

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

Where to find TWRP 3.0.0-0 for i9000?

Hi guys, I have 2 Galaxy S's. It was my first Android and I love it still - however..
One of them is on stock everything 2.3.6 and is lovely and shiny new looking.
The other has dead pixels, is tattered all to hell, but is running the latest A-Rom 6.0.1 build awesomely (I suggest you try it) and has TWRP 3.0.0-0 recovery. It was a recovery flash from a lacklustre 5.1 OMNI (I think) based rom, but no idea when!
I cannot for the life of me remember where I got that recovery file from.. I've googled the heck out of it and got nowhere! I'd really love to get the shiny one running Marshmallow, but it's been years since I last poked around with all the files etc and frankly - i'm a bit lost.
a) Could anyone point me to that recovery file? I just can't find it
b) I've tried using adb to back it up but get permission denied and can't find the option in superSU or the developers section to allow adb access. Where is it??
c) Is there an app I can install which will do it for me? which is supported by this phone?
Help! What's the best thing to do at this point? I'd really like that OS and recovery on both.. though now I'm starting to contemplate taking them both to bits and swapping the internals around which I don't really want to do..

Does anyone maybe still have that recovery floating around in their SD root folder? I unfortunately factory reset and wiped mine after installing it..

found it myself - finally!

Bearded_1 said:
found it myself - finally!
Click to expand...
Click to collapse
Any chance you'd share your TWRP? I just realised my old i9000 is still alive, would be interesting to test some MM ROMs
Actually I also found it so I'm all set

Where?? I had to go to stock, flash chainfire for jelly bean, then flash CM 10 stable, then a newer chainfire, then a lollipop rom, THEN on a failed flash of the latest A-Rom marshmallow build it rebooted to recovery 3.0.0-0 so I guess it's part of that build. Not found it anywhere else!

Good start ?

Hi all, glad to find this
I have ..., guess what ? a RAZR i (Ok, it's a friend's one) that I repaired changing the mad battery after factory resets didn't do anything. Then found OTA was available, applied and the RAZR i was 4.1.2 IIRC and the new battery went OK. My mistake, another OTA went soon, which I applied too, making the RAZR i a 4.4.2 kitkat piece of crap (no more write access to sdcard, this is well known ... by the ones aware , know I'm one).
Then I thought I could make the phone free and search the web for days to try to understand, found a french forum which said I can't do anything without unlocking the bootloader, what I did.
They directed me there to remove the boot-logo-warning but that's a razr hd thread and nothing worked for me. I can't remember where I read I should have CWM to do this, but as the french guy said he rather like twrp I didn't do anything at the moment, only failed to flash some logo from fastboot with various errors....
Well, I'm there, and it's cool because I hope this is the good place to have answers to questions that are still in my mind for years, and 2/3 new ones... fortunately they'll overlap and self-resolve once I get one. I'm not at all skilled in android, I only flashed a phone in 2010 and that's why I still have android SKD in my ubuntu (I also have a xp box, but I couldn't do anything for my old Acer LiquidMT). As you see, I'm a vintage things amateur (... okay, I'm vintage too).
Now the scene is built, please let me dare ask what still puzzles me :
1) For the Razr i 4.4.2 (french from sfr-vodafone kia20.74 now used with another carrier) do I have to search a specifically dedicated recovery ? Parsing this RAZR i Q&A, I found twrp seems to the preferred recovery, but I'd rather like to get confirmation from skilled ones, and also for version.
2) And please tell me if I'm wrong thinking the [RECOVERY] Unofficial TWRP 3.0.2-0 thread aim is to bring support to the RAZR i which is not supported by official teamw.in ? (BTW, @Hazou, the 1st link in the thread - DataMedia - is dead)
3) Assumed I have to go the TWRP way and I only have currently the stock recovery, do I guess right the only way is download img.zip and extract then do
Code:
./fastboot flash recovery recovery.img
, then only after that the phone can be rooted ?
4) You see I'm puzzled here because I still don't have understood the logical path: is this one the good ? unlock boot loader -> fastboot flash reco -> is the device rooted at this point ? If not, install su from recovery option "install zip from sdcard", then it's done and I get a so called "rooted stock ROM" ? Then only I can figure installing a custom ROM if exists for the RAZR i ?
5) And I should always flash a custom ROM based on the same 4.4.2 android release as my current stock one AND disable OTA updates ?
I read so many threads with guys having issues with hard-bricked RAZR i and all are about ICS and JB, so I wander the only custom are for ICS or JB, and still don't understand why they want to revert back.
Thanks for advices.

1stStep said:
Hi all, glad to find this
I have ..., guess what ? a RAZR i (Ok, it's a friend's one) that I repaired changing the mad battery after factory resets didn't do anything. Then found OTA was available, applied and the RAZR i was 4.1.2 IIRC and the new battery went OK. My mistake, another OTA went soon, which I applied too, making the RAZR i a 4.4.2 kitkat piece of crap (no more write access to sdcard, this is well known ... by the ones aware , know I'm one).
Then I thought I could make the phone free and search the web for days to try to understand, found a french forum which said I can't do anything without unlocking the bootloader, what I did.
They directed me there to remove the boot-logo-warning but that's a razr hd thread and nothing worked for me. I can't remember where I read I should have CWM to do this, but as the french guy said he rather like twrp I didn't do anything at the moment, only failed to flash some logo from fastboot with various errors....
Well, I'm there, and it's cool because I hope this is the good place to have answers to questions that are still in my mind for years, and 2/3 new ones... fortunately they'll overlap and self-resolve once I get one. I'm not at all skilled in android, I only flashed a phone in 2010 and that's why I still have android SKD in my ubuntu (I also have a xp box, but I couldn't do anything for my old Acer LiquidMT). As you see, I'm a vintage things amateur (... okay, I'm vintage too).
Now the scene is built, please let me dare ask what still puzzles me :
1) For the Razr i 4.4.2 (french from sfr-vodafone kia20.74 now used with another carrier) do I have to search a specifically dedicated recovery ? Parsing this RAZR i Q&A, I found twrp seems to the preferred recovery, but I'd rather like to get confirmation from skilled ones, and also for version.
2) And please tell me if I'm wrong thinking the [RECOVERY] Unofficial TWRP 3.0.2-0 thread aim is to bring support to the RAZR i which is not supported by official teamw.in ? (BTW, @Hazou, the 1st link in the thread - DataMedia - is dead)
3) Assumed I have to go the TWRP way and I only have currently the stock recovery, do I guess right the only way is download img.zip and extract then do
Code:
./fastboot flash recovery recovery.img
, then only after that the phone can be rooted ?
4) You see I'm puzzled here because I still don't have understood the logical path: is this one the good ? unlock boot loader -> fastboot flash reco -> is the device rooted at this point ? If not, install su from recovery option "install zip from sdcard", then it's done and I get a so called "rooted stock ROM" ? Then only I can figure installing a custom ROM if exists for the RAZR i ?
5) And I should always flash a custom ROM based on the same 4.4.2 android release as my current stock one AND disable OTA updates ?
I read so many threads with guys having issues with hard-bricked RAZR i and all are about ICS and JB, so I wander the only custom are for ICS or JB, and still don't understand why they want to revert back.
Thanks for advices.
Click to expand...
Click to collapse
Hey 1stStep,
A lot off assumptions and questions. And most of them are right.
1. Afaik there are 2 recoveries for the RAZR I. Stock and my build TWRP 3.0.2-0 unofficial. (Thanks for the heads up about the link)
2. Answered in 1.
3. Yep. If your bootloader is unlocked it gives u the function to flash non-stock firmware to the phone. Stock firmware are signed to prevent normal users flashing wrong firmware. Firmware consist of a couple of images. Those images contain data for the partition, just like in your PC. Every image does something else. Most known are boot, data, system, recovery and cache. There are many more. Some needed, some unnecessary.
To answer your question: when u have flashed the TWRP recovery u override the stock one. The TWRP can flash zip files and images to the most known device partitions. From here on u can flash a superuser zip(gives root access on the current ROM/system). Make sure u have the right superuser zip. There are many.
4.
Path to root on stock:
Unlock bootloader->install custom recovery (TWRP)->install superuser zip->reboot and test root on device
Path to custom ROM:
Unlock bootloader->install custom recovery (TWRP)->install ROM zip and extra's if needed like (Gapps(needed for Google playstore and more))->reboot and play with your new ROM.
Off course if u already have the bootloader unlocked and installed a custom recovery, u can skip those.
In the recovery u can also make backups, called nandroid backup. Read up on them and everything u wanna do.
5. The only thing u never want/should do is flashing Android 4.0.4 stock firmware without prior modifications. This is because from 4.0.4 to 4.1.2 there was a change in bootloader (the thing u unlock). If u go back it corrupt a part of the firmware which is difficult to overcome or even impossible without some factory stuff. Everything above 4.1.2 is save. And can always be flashed. The latest stock is 4.4.2 (KIA 20.74) and latest available custom ROM is 4.4.4 (CM11 or soon Lineage 11).
Good luck!

Thanks so mush great dev to spend time and even surely repeat yourself (hope you're not under stress) for a newb.
In your answer for path to custom ROM you say "Unlock bootloader->install custom recovery (TWRP)->install ROM zip and extra's if needed like".
Do I have to understand custom ROMs are yet rooted (OOTB), or root yet made on stock will survive flashing the custom (I though flashing a custom was some kind of infant clear brain graft?
BTW, is it general good advice to test recovery before flashing? I found this in Moto Play unofficial recovery 3.0.2-r5 from Vache:
Code:
fastboot boot recovery.img
?
Thanks again

1stStep said:
Thanks so mush great dev to spend time and even surely repeat yourself (hope you're not under stress) for a newb.
Click to expand...
Click to collapse
Not at all , just replying if I have some time.
1stStep said:
In your answer for path to custom ROM you say "Unlock bootloader->install custom recovery (TWRP)->install ROM zip and extra's if needed like".
Do I have to understand custom ROMs are yet rooted (OOTB), or root yet made on stock will survive flashing the custom (I though flashing a custom was some kind of infant clear brain graft?
BTW, is it general good advice to test recovery before flashing? I found this in Moto Play unofficial recovery 3.0.2-r5 from Vache:
Code:
fastboot boot recovery.img
?
Thanks again
Click to expand...
Click to collapse
- Most custom roms are prerooted.
- Cyanogenmod/LineageOS are prerooted
- Root installed by a zip will not survive any system flashing (rom flashing)
- Any modification to your system partition will not survive and system flashing (rom flashing), though 1 exception:
- installed gapps package (google apps/play store etc.) will survive system flashing on cyanogenmod based roms. But only when updating the rom to a newer version on the same android version. So:
CM11 version 1 to CM11 version 2. (because of a special script in the install zip)
Pre testing a boot or recovery image is blocked on our bootloader. So u can't do it. It's a shame they did it. Working on any boot or recovery changes is a pain in the spoken ass.
If u flash the recovery with:
Code:
fastboot flash recovery recovery.img
there is nothing to be afraid off. The TWRP 3.0.2-0 recovery is well tested on this device.

Thank you again man for all detailed answer.
You're right, it's a shame all these locked things in our phones. I'm sure the guys that agree (our security, blah blah) with these ways to do won't be so happy the day their computers will be locked the same way.
bye bye Hazou.
[Edit] .... hmmm, how long does it take to flash? Yet a 1/4h elapsed and razr still says "Flashing recovery..."
Please, what is the md5 of the image (not the zip, this you give us)? Thanks
[Edit] : Downloaded twice and get md5sum 60dff26f3ee5e9338ee4a6f8cf7df098
but still same forever Flashing recovery ...
[Edit] : I've been puzzled for days being stuck in endless "Flashing recovery ..."
In the ended I decided, after saying 1 hour waiting a hypothetical "success/congrats message", NOT QUITTING the current fastboot screen, to select the recovery option in this very fastboot menu (on a Razr i : Vol- to highlight recovery item, then Vol+ to select) and bang I was in TWRP menu. What to do next once in, it is another story.

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