Related
Hi,
I've just bought a new nexus one mobile phone from Egypt. Since the mobile was not officially released here, the only shops that sell it are the ones that import it from Europe...so lucky me i got my self a Vodafone Nexus one Mobile running Android 2.1-update1
After a long search on the internet i was able to update it to Android 2.2 (build FRF91). After another very long time trying to find the 2.2.1 update (build FRG83) i discovered that it wasn't released yet for the Vodafone mobiles. but some claim that by installing the FRG33 build Rom your kernel will completely change and thus you become a "Normal" nexus one
My questions are:
-Is the above true?
-How do i install this Rom?
-Does the process of installing the Rom need rooting my device?
-is there a simple tutorial for a noob (running Linux ubuntu) for rooting?
-Is it possible to root the mobile "Temporary" until I get to Build FRG83?
-Is there a high chance of Bricking the device?
Thx in advance!!!
Since you have AMOLED Nexus (otherwise it wouldn't be able to run 2.1), there is no problem flashing stock FRF91 on it.
Of course it requires rooting.
Read my signature, I hope you'll find your way from there easily. If any step in the directions below isn't clear - go to Wiki and find what it means and what needs to be done.
If you want stock 2.2.1:
Use 1-click root, install custom recovery (any), download stock FRF91, use the recovery to flash it, then download FRG83_from_FRF91 upgrade, rename to update.zip and put on SD card, go to the stock recovery (your custom recovery would be overwritten by then), flash update.zip.
If you want custom ROM:
Use 1-click root, install custom recovery, download and install custom ROM of your choice.
I would like to say that Android 2.2.1 has no major changes compare to Android 2.2.
for your questions..
-Is the above true?
I'm not sure about kernel version because I keep using third-party ROMs, but it's possible for FRG83 to have a different kernel than FRG91
-How do i install this Rom?
Stock FRG83 rom should be available to download somewhere, once you have unlocked bootloader and have a recovery (Amon or Clockwerk) installed, you should be able to flash FRG83 rom in recovery.
-Does the process of installing the Rom need rooting my device?
sorry about this
-is there a simple tutorial for a noob (running Linux ubuntu) for rooting?
http://wiki.cyanogenmod.com/index.php?title=Nexus_One
-Is it possible to root the mobile "Temporary" until I get to Build FRG83?
It's not necessary to root device temporarily, because once you have acquired root privilege, you can play a lot more tricky things, so there's no reason to become unrooted again, but I've heard from people who would like to receive update OTA, they have to unroot in order to get OTA update properly.
-Is there a high chance of Bricking the device?
Nexus One is now developer phone, so it's unlikely to be broken only by flashing new ROM
Wrong info. That's exactly why people should read before asking questions - because the answers they get might be partially correct at best.
1. Kernel versions don't matter, the OP just doesn't know ROM from Kernel. He should read more. He wants stock Google ROM.
2. Stock FRG83 is available from the same Wiki I've mentioned above, and some reports say that it doesn't like to be flashed from custom recovery and doesn't proceed. So I didn't suggest it, and suggested FRF91 which 100% flashes.
3. CyanogenMod Wiki only has 1 root method - unlocking the bootloader. It's definitely not the easiest one, and some people might want to keep their bootloader locked. I don't believe OP is one of them, since he bought a phone for unsupported country and warranty won't mean anything to him, but at least he needs to be educated about the differences. In Wiki he does, in your post - he doesn't.
4. When you flash stock ROM, you lose root - as simple as that. If he wants stock FRG83 - he WILL lose root, and if he wants it rooted - he'll have to go to Wiki again and see, how to root. If he has unlocked bootloader - it'll be just a bit easier.
5. Since he already has Froyo, chances are his radio is updated. If they aren't - the stock ROM contains radio, and if it's not up to date on the system - it will be flashed. Flashing radio incorrectly (terminating it in the middle, power failure, etc) is the only way to brick the device. So if his radio is updated - there's no chance he'll brick it, if it's not - it depends on if he'll touch the phone during the radio flash or not.
And this has no place in Development section.
well I'm still kinda confused, so I'll try to explain a little better what I got in mind first.
I read this post (google.com/support/forum/p/android/thread?tid=5fe9454b7c7261e7&hl=en) in the nexus one forums that explains the difference between 2 kernels one exclusive to Vodafone (Europe?) and one to other Carriers in the USA.
The kernel version I have ([email protected] #1) get updates like a month after other one and I believe I have to insert a Vodafone sim for it to work. what I read online (can't remember where) is by installing the FRG33 leaked rom on the device it basically changes the Kernel version to the US version ([email protected]#1) so that I can easily update to FRG83, as till now the Vodafone kernel still didn't receive the FRG83 update OTA.
I tried downloading the file FRG83 from FRF91 and it simply gives me a failed to verify file whole-signature and never completes the update.
So reading online, I'm still confused on what exactly to do to install this leaked rom. Now correct me if I'm wrong but what I understand from this thread I have to gain root privileges to install custom recovery and then install roms and solve my problem. right?
I'll be following this thread (forum.xda-developers.com/showthread.php?t=747598) to root my device is it the correct one?
You need to flash full update of frg33,and after that you'll update OTA to FRG83.Here it is the full rom http://shipped-roms.com/shipped/Pas...le_WWE_2.16.1700.1_FRG33_MFG_Shipment_ROM.zip
Cheers
This is the thread with FRG33->83 OTA, link in the last post:
http://www.google.com/support/forum/p/android/thread?tid=51704fcd145670fb&hl=en
razlken said:
well I'm still kinda confused, so I'll try to explain a little better what I got in mind first.
I read this post (google.com/support/forum/p/android/thread?tid=5fe9454b7c7261e7&hl=en) in the nexus one forums that explains the difference between 2 kernels one exclusive to Vodafone (Europe?) and one to other Carriers in the USA.
The kernel version I have ([email protected] #1) get updates like a month after other one and I believe I have to insert a Vodafone sim for it to work. what I read online (can't remember where) is by installing the FRG33 leaked rom on the device it basically changes the Kernel version to the US version ([email protected]#1) so that I can easily update to FRG83, as till now the Vodafone kernel still didn't receive the FRG83 update OTA.
I tried downloading the file FRG83 from FRF91 and it simply gives me a failed to verify file whole-signature and never completes the update.
So reading online, I'm still confused on what exactly to do to install this leaked rom. Now correct me if I'm wrong but what I understand from this thread I have to gain root privileges to install custom recovery and then install roms and solve my problem. right?
I'll be following this thread (forum.xda-developers.com/showthread.php?t=747598) to root my device is it the correct one?
Click to expand...
Click to collapse
The kernel versions are identifying ROM variants, other than that they're of no use.
You can't apply FRG83-from-FRF91 update to Vodafone ROM, you need to install stock Google ROM first.
Yes, this is the correct thread to root the device.
Or you could do another thing that you wanted, and it'll probably be simpler:
Go to Wiki, download stock FRG33 image, rename to PASSIMG.ZIP, put on SD card, reboot the phone into bootloader. It'll automatically apply.
Then either wait for the OTA to FRG83, or apply the update.zip as I suggested above - only use FRG83-from-FRG33, that you can find linked in the first link, or in Wiki between "All stock ROMs and OTAs".
I've downloaded the FRG33 Rom and installed it using the PASSIMG.zip method. now the last problem, hopefully, is that i can't find a FRG83 from FRG33 OTA and i don't get any automatic OTA on my nexus one phone.
i tried the link but it seems that the any file on the google server was removed or something as it says page cannot be found and i can't find the file on the wiki.
any help here? and way to force the OTA to start on my nexus one or does anyone have the file or a mirror to the download?
Copy-pasted from some Google search:
Open the phone dialer
dial this: *#*#2432546#*#*
you'll see a notification that checkin was successful
Then, hit menu>>about phone>>system updates to see if anything is there.
Still nothing I dial it and get the checkin succeeded notification but when i go to the system updates it just says my system is up to date.
P.S: sorry for not searching but it's like 3 in the morning and I've been dealing with this for like hours....my brain hurts.
edit: tried using the passimg.zip method with this file (dl3.htc.com/RomCode/Source_and_Binaries/signed-passion-img-FRG83_0923.zip) which i found on the rom section of the wiki but after checking the passimg.zip the bootloader just reboots itself and returns to the main menu without doing anything.
Yes, it's reported that FRG83 doesn't like to be installed by PASSIMG method.
You could try renaming to update.zip and flashing in recovery.
Tried that but still nothing gives me an error: E: signature verification failed.
Well, in that case, if you really want FRG83 - you have to root and apply this update through a custom recovery.
The root and the custom recovery will be gone once you apply it.
ok so i rooted my phone using the rageagainstthecage method since the 1 click root does seem work for FRGXX build. then i used Rom Manager to install this file (http://loadbalancing.modaco.com/dow.../update-nexusone-FRG83-stock-radio-signed.zip)
now the last problem, not really sure if it is anyway, after the rom was installed i lost root privileges as u said but the recovery remained custom (clockwork mod) now I don't really care if it's stock or not, but am i going to get OTA updates with no problem even with a custom recovery or do i have to put it back to stock?
EDIT: I've Extracted the recovery.img from a stock FRG83 Rom and installed using the Flash_image method now i've got the stock Recovery back, I believe that this way everything is ok to receive OTAs in the future..
THX a lot to everybody that helped me out Especially Jack_R1
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,
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
Hi I have a few questions for my nexus 6 that I am getting today
1) I am going to flash a the new marshmallow update, which one should I pick because for root you need a specific build but on the google factory images the latest build is not supported? I really don't know.
2) After I flash 6.0 can I just do the fastboot flash recovery twrp.img without flashing the boot.img
3) When I go to a new rom like Chroma by Zephik do I still need to change the boot.img to flash the beta super user
For now these are all my questions and I would really appreciate if you could answer it.
side note: I cannot use NRT becuase I am on a mac, if you guys have any alternatives I would really appreciate it too.
1) Flash any of them, they are all rootable. I would recommend going with the latest one. Unless I am mistaken, I believe K, N, and R each have the same radio so there effectively would be no real difference in the end result, as a custom ROM will overwrite everything else.
2) Yes, there is no need to have a modified boot image or root if you plan on flashing a custom ROM.
3) This depends on the ROM, they should have instructions in their post as to what they require. I am pretty sure Chroma comes with a custom kernel already, and I believe it comes pre-rooted as well. It could be that you have to root the ROM after you flash it if you want root though, there are some ROMs that are like that. The OP should have installation instructions.
As for your side note, I don't recommend using a toolkit of any sort. I recommend learning how to use fastboot, and doing it manually. That way if you were to need to fix something in the future, you would have a general understanding of what you did and why, and perhaps that will help you in how to fix it. Rather than clicking a couple buttons in a toolkit. Also, toolkits can fail, and not tell you why. It is often hard to figure out what went wrong when it is doing multiple steps at once, rather than one at a time like if you were to do it the manual way. It really isn't that difficult, and it is very well documented process at this point with tons of guides with pictures and even videos out there.
cupfulloflol said:
1) Flash any of them, they are all rootable. I would recommend going with the latest one. Unless I am mistaken, I believe K, N, and R each have the same radio so there effectively would be no real difference in the end result, as a custom ROM will overwrite everything else.
2) Yes, there is no need to have a modified boot image or root if you plan on flashing a custom ROM.
3) This depends on the ROM, they should have instructions in their post as to what they require. I am pretty sure Chroma comes with a custom kernel already, and I believe it comes pre-rooted as well. It could be that you have to root the ROM after you flash it if you want root though, there are some ROMs that are like that. The OP should have installation instructions.
As for your side note, I don't recommend using a toolkit of any sort. I recommend learning how to use fastboot, and doing it manually. That way if you were to need to fix something in the future, you would have a general understanding of what you did and why, and perhaps that will help you in how to fix it. Rather than clicking a couple buttons in a toolkit. Also, toolkits can fail, and not tell you why. It is often hard to figure out what went wrong when it is doing multiple steps at once, rather than one at a time like if you were to do it the manual way. It really isn't that difficult, and it is very well documented process at this point with tons of guides with pictures and even videos out there.
Click to expand...
Click to collapse
Thanks so much, I actually used adb/fastboot when I was rooting my mytouch 4g so this knowledge should come in handy, one other question if I were to root the latest factory image can I use the MRA58K.img that Chainfire posted for 6.0 or do I have to find a modified boot img that matches the latest factory image which is MRA58R, thank you so much again
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