Related
Hi everyone..
I'm writing this post after being offline from XDA for quite a long while, so keep it cool when answering since my knowledge of what I'm talking about is very limited by now. I have an Xperia Z with eXistenZ 5.0 installed, Build number 10.4.B.0.569, which is a JB Rom and I'd like to try out some new roms, firmwares, recoveries and so on..
What I am interested in knowing is why does my recovery mod disappear, this has happened a few times, and also can I choose exactly the kernel that I want for any rom or does some roms only support special kernels? And what about the recovery mods? Are they depending on kernel as well? How do I update to a newer kernel from 10.4.B.0.569?
First of, I have unlocked my bootloader a very long time ago and I haven't gone back to Stock since then and I am not planning to do so. However to start updating my Xperia what should be done? I have already backed up my current rom with Titanium Backup.
For some reason I can't access recovery mode when powering on and pressing volume down, but I know for a fact that it's pretty easy to install a recovery again.
It would be very much appreciated if you would explain what should be done and why.
Looking forward to hearing from you..!
BUMP
Hammerbak said:
Hi everyone..
I'm writing this post after being offline from XDA for quite a long while, so keep it cool when answering since my knowledge of what I'm talking about is very limited by now. I have an Xperia Z with eXistenZ 5.0 installed, Build number 10.4.B.0.569, which is a JB Rom and I'd like to try out some new roms, firmwares, recoveries and so on..
What I am interested in knowing is why does my recovery mod disappear, this has happened a few times, and also can I choose exactly the kernel that I want for any rom or does some roms only support special kernels? And what about the recovery mods? Are they depending on kernel as well? How do I update to a newer kernel from 10.4.B.0.569?
First of, I have unlocked my bootloader a very long time ago and I haven't gone back to Stock since then and I am not planning to do so. However to start updating my Xperia what should be done? I have already backed up my current rom with Titanium Backup.
For some reason I can't access recovery mode when powering on and pressing volume down, but I know for a fact that it's pretty easy to install a recovery again.
It would be very much appreciated if you would explain what should be done and why.
Looking forward to hearing from you..!
Click to expand...
Click to collapse
personally I would flash an ftf earlier jellybean firmware then root cwm and unlock bootloader flash custom kernel etc, but you probably know this already.
I know a lot of people are in this sticky situation with me.
But hey guys, XDAers, Googlers, Developers & the rest of y'all
So I have a S3 Mini (with NFC so i8190N) and I hack it a lot, I mod, I do a lot of root-y stuff on it.
Well today's objective for my phone was to flash a Custom ROM that blended together TouchWiz and KitKat since I can't get that officially for my phone, I found LostVirginity V2 from the guy who made the Virginity ROMs (I forgot his name but big ups to him, thanks for the crazy cool ROMs bro!)
So I tried to flash it in TWRP.....and it didn't work because TWRP consistently freezes when I press anything and i have to do a battery pull.
Then I used Odin to flash CWM and it flashed it but when I rebooted it my phone decides to not listen and just go back to CWM like CWM has a leash on it or something, I mean come on! TWRP replaced you for a reason and you're trying to get us all back, you're old and forgotten CWM...
So now I've got that frigging annoying TWRP/CWM loop where whatever you do it just reboots to the custom recovery, pretty much the only thing I can do is use Odin to flash another custom recovery (only ones I can switch between are (any version of) CWM, PhilZ's Advanced CWM and any version of TWRP)
I've been trying everything, some guys on redmondpie, android central and rootzwiki (I think that was the website) fixed the problem on the ASUS Transformer Pad but they installed terminal emulator, I've got that but if I could access that that'd defeat the whole point of this thread because that would mean I'd have access to the Android system.
So my question is: Now that I'm imprisoned by the claws of the custom recovery, how do I escape?
Do I flash another firmware through Odin or something?
Somebody help me, and anybody who's been through this problem or is going through this problem at the moment, tell me what you did/what you're doing so we know what to rule out and stuff
Thanks guys
I can't seem to find a recovery that will flash a rom for MY phone. I have the MetroPCS version/variant of the sgh-t599n and I really want to be able to flash a custom rom to my phone, but I can't seem to find anyone with (codinMetroPCS) files for it. The only reason I say that is because when I finally got CWM 6.0.3.2 downloaded and working, tried to flash beanstalk rom and it told me "THIS ROM IS FOR CODINALTE PHONES NOT CODINMETROPCS PHONES" Is there a different rom for the Metro phones? Or am I doing something wrong....Im rooted through cydiaimpactor, well, i guess technically through the pre-rooted stock rom I had to flash through Odin...BTW-Over the last two weeks I've learned that flashing a rom on a samsung (at least mine) takes a custom recovery, which needs to be flashed via Odin (something I didn't know how to do at the time)...I almost feel like Im starting to get confused with all these different programs needed to run or flash or download this or that....I'm not sure if the info is even in the correct order in my head......could someone please walk me through this? or call me! lmao...this is giving me a headache. lol....but I REALLY REALLY want to know what Im doing.....ANYONE? PLEASE??
Cdbarron727 said:
I can't seem to find a recovery that will flash a rom for MY phone. I have the MetroPCS version/variant of the sgh-t599n and I really want to be able to flash a custom rom to my phone, but I can't seem to find anyone with (codinMetroPCS) files for it. The only reason I say that is because when I finally got CWM 6.0.3.2 downloaded and working, tried to flash beanstalk rom and it told me "THIS ROM IS FOR CODINALTE PHONES NOT CODINMETROPCS PHONES" Is there a different rom for the Metro phones? Or am I doing something wrong....Im rooted through cydiaimpactor, well, i guess technically through the pre-rooted stock rom I had to flash through Odin...BTW-Over the last two weeks I've learned that flashing a rom on a samsung (at least mine) takes a custom recovery, which needs to be flashed via Odin (something I didn't know how to do at the time)...I almost feel like Im starting to get confused with all these different programs needed to run or flash or download this or that....I'm not sure if the info is even in the correct order in my head......could someone please walk me through this? or call me! lmao...this is giving me a headache. lol....but I REALLY REALLY want to know what Im doing.....ANYONE? PLEASE??
Click to expand...
Click to collapse
Just flash the recovery listed in the BeanStalk thread.
There's 3 variants of the phone; T599, T599N, T599V (codinatmo, codinametropcs/codinanewcotmo, codinavid) they're pretty much the same exact phone, there's just slight differences in proprietary files - so the developers decided to unify the all of them into one (codinalte), as it's easier to build for one phone then three seperate times. The recovery's responsible for the phone; which is why the recovery plays a key-role, basically the recovery you have right now can only accept roms that are specifically 'titled' as codinametropcs, and by flashing that recovery, you'll be able to flash any of the 4.4.x roms (BeanStalk, Vanir, OmniROM, CM, AOKP, and soon pure-vanialla AOSP).
ok so....
Exothermic said:
Just flash the recovery listed in the BeanStalk thread.
There's 3 variants of the phone; T599, T599N, T599V (codinatmo, codinametropcs/codinanewcotmo, codinavid) they're pretty much the same exact phone, there's just slight differences in proprietary files - so the developers decided to unify the all of them into one (codinalte), as it's easier to build for one phone then three seperate times. The recovery's responsible for the phone; which is why the recovery plays a key-role, basically the recovery you have right now can only accept roms that are specifically 'titled' as codinametropcs, and by flashing that recovery, you'll be able to flash any of the 4.4.x roms (BeanStalk, Vanir, OmniROM, CM, AOKP, and soon pure-vanialla AOSP).
Click to expand...
Click to collapse
?
When you say flash....you mean through Android System Recovery (stock recovery)? right? ....sry man...back when i was rooting my droid x, I never ran into any issues and it seemed a little easier to flash roms
Cdbarron727 said:
?
When you say flash....you mean through Android System Recovery (stock recovery)? right? ....sry man...back when i was rooting my droid x, I never ran into any issues and it seemed a little easier to flash roms
Click to expand...
Click to collapse
flash it through odin.
Thank you....now....I think I've actually gotten this far already.....had cwm installed...then tried to flash beanstalk with cwm and I got the codin error saying "this is not for codinmetropcs" ...if I get that problem again...is there something conflicting with it in some way? Or where did I go wrong? do i have to have twrp?
sorry to bug bro
Exothermic said:
Just flash the recovery listed in the BeanStalk thread.
There's 3 variants of the phone; T599, T599N, T599V (codinatmo, codinametropcs/codinanewcotmo, codinavid) they're pretty much the same exact phone, there's just slight differences in proprietary files - so the developers decided to unify the all of them into one (codinalte), as it's easier to build for one phone then three seperate times. The recovery's responsible for the phone; which is why the recovery plays a key-role, basically the recovery you have right now can only accept roms that are specifically 'titled' as codinametropcs, and by flashing that recovery, you'll be able to flash any of the 4.4.x roms (BeanStalk, Vanir, OmniROM, CM, AOKP, and soon pure-vanialla AOSP).
Click to expand...
Click to collapse
I just flashed cwm through odin and it passed....I havn't rebooted just yet, but I know it was working before.... But just saw that the cwm I downloaded from the beanstalk thread says its for kitkat builds only. My phone is running 4.1.2..does that matter? or does that mean I just need a 4.4 rom to be flashed with it? Sorry if these are dumb questions
Cdbarron727 said:
I just flashed cwm through odin and it passed....I havn't rebooted just yet, but I know it was working before.... But just saw that the cwm I downloaded from the beanstalk thread says its for kitkat builds only. My phone is running 4.1.2..does that matter? or does that mean I just need a 4.4 rom to be flashed with it? Sorry if these are dumb questions
Click to expand...
Click to collapse
It's cool; it just means you can only flash 4.4 roms, so you cannot flash cm10.1, cm10.2, and pac. It doesn't matter that your phone's running 4.1.2.
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.
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