Hello!
I'm new to posting to this forum, so you can call me a noob. I'm sure I am a noob, I'm sure I did something wrong. I was just a customer for the time when GingerDX development started for Xperia X8, my previous phone. I'm not a dev, but I know know to flash stuff and what to avoid or do with care. If this thread is in the wrong section, then sorry, please move it where it should be.
Three months ago I got my new shiny GT-I9305, version for Poland (distributed by Plus), and as I did with my X8 previously, I decided to root it and dive into flashing many custom ROMs.
I made the EFS backup following lyriquidperfection's thread (http://forum.xda-developers.com/showthread.php?t=1946915), so my IMEI and NV items are safe and secure. I also did a backup of a stock 4.1.2 ROM.
I was using many different ROMs and kernels from XDA, both based on CM10.1 and Official Samsung ROM. I had PhilZ Touch 5 recovery installed. Everything worked fine, until I noticed something strange:
After I flashed an unofficial port of SlimBean to I9305 (http://forum.xda-developers.com/showthread.php?t=2297679), and Yank555 kernel for CM10.1 based ROMs, I noticed that in "About phone" section, my phone is shown as "GT-I9300", but I'm 100% sure I flashed the file that had I9305 in the filename, so it couldn't be my mistake. I didn't buy I9305 for 4G, but for 2 GBs of RAM, so I couldn't test if LTE was working (My carrier is T-Mobile.pl, which doesn't have 4G in Poland yet), but I didn't see the option to even search for LTE networks available. I didn't care much about that, since everything else was working just fine.
I decided to flash the previous ROM I was using - Sentinel Rom, because I found the bug with GPS and I wanted to see if the same happens in that rom. I rebooted to recovery, but... I couldn't install the package. It was all giving the "set_perm some changes failed (status 7)" error all the time. The same happened when I tried to install LiquidSmooth for i9305. I just couldn't flash any 4.2.2 ROM, I was able to flash a kernel just fine.
I decided to flash Ripper Rom instead. It installed with no error, it just said: "Root access is missing, root the device?" so I simply said to root it. But the phone couldn't normally boot. It stayed for a while at the "Samsung Galaxy SIII GT-I9305" splash screen with the little red exclamation mark in the top left corner, then it kept rebooting back to recovery. I had no idea what's going on. Wiping data/cache/dalvik cache/system didn't help at all. The only way to make the phone working again was to recover SlimBean from Nandroid backup I had done previously. Sadly, I had no Sentinel Rom backup. Deleted it. Shame on me.
I successfully restored Stock 4.1.2 rom from the nandroid backup, but I still couldn't install any custom ROM via recovery because of the same error.
After several tries to install different ROMs, redownloading everything and going through a lot of stress I gave up. I installed TriangleAway, reset the flash counter and, through Odin, flashed tar.md5 of the stock ROM delivered by Plus, downloaded from here: http://goo.gl/SMWEha. I installed a version build XXBLL3, which later updated itself to XXBMB4, and baseband updated from XXBLL3 to XXBMA2.
Right now, I have Official, Stock 4.1.2 ROM from Plus, with Baseband version I9305XXBMA2, build number JZO54K.I9305XXBMB4 and stock kernel.
What Download mode says:
Product Name: GT-I9305
Custom binary download: No
Current Binary: Samsung Official
System Status: Official
Now to the questions:
Why this started happening? Was the reason the wrong model of the phone in "About phone", hence installing SlimBean?
When I flashed the stock ROM, does it mean that I'm fully back to stock, with everything removed? Does it mean that my phone is like I got it from the box, with warranty? The recovery seems stock as well.
Can I root it again? If yes, how to do it safely, to not make something like that happen again?
Baseband got updated. Does it mean I have to make an EFS partition backup again?
Sorry if I ask too much, but I'm a very careful person, and I want to know everything before I start doing anything risky with my smartphone.
Thanks in advance.
General thread read the basics all stickied .
jje
I read every sticky thread and I can't find the answer to my questions. That's why I'm asking.
When I flashed the stock ROM, does it mean that I'm fully back to stock, with everything removed? Does it mean that my phone is like I got it from the box, with warranty? The recovery seems stock as well.
That is answered in the how to return to stock for warranty thread .
Root again yes follow the instructions .
EFS again that is in the faqs and guides no you dont have to but its safer to do so .
Why this started happening >>> User error who knows where as multiple roms stuff flashed .
jje
I rooted the phone again using the Galaxy S3 toolkit and every time I try to install the custom ROM through TWRP I get the error:
set_perm: some changes failed (status 7)
Then the phone doesn't want to boot (reboots to recovery all the time), only a restore of a Stock 4.1.2 from nandroid backup helps.
Ideas?
Seriously? Anyone?
Flashing 4.1.2 ROM (Ripper Rom) gives the same exact effect. Rom flashes correctly, but the phone cannot boot into system, reboots to recovery.
Related
Hello,
I tried searching for my problem in the forums but I didn't find my exact setup and don't want to brick my phone. (Well maybe it already is)
I had Cyanogenmod 7 for quite a while and tried the Nightlies for 9 some months ago. In the early days of my phone I used ODIN to flash the newest Stock firmwares and then used the chroot kernel to root my phone and install cwm. Since then I installed Cyanogenmod 7 and later Cyanogenmod 9 Nightlies with cwm recover and there was never a problem.
Today I tried the ROM from DerTeufel1980 http://forum.xda-developers.com/showthread.php?p=28819140
I flashed the rom, the addons, the superuser and google now fix. Then I flashed the kernel Devil3_1.0.0-Rc5_datadata_i9000_CFS_BLN_CMC_20120719.zip and fixed permissions. After that my phone wouldn't boot. The boot animation was the old standard android logo.
I managed to get into Devil Kernel Recovery and thought to try a reflash of just the ROM but when I try to "choose a zip" it always tells me
E:can't mount /sdcard/
After that I flashed the kernel with odin and now the phone seems to boot but veeeery slow and it has a ton of flickering the whole time. The bootanimation is the cyanogenmod 9 boot animation. I got into Devil Recovery and I still can't mount the sdcard. And it seems that it doesn't detect my sim card.
I hope you can help me.
Edit: Actually after rebooting several times the boot sped up and I could get into the ROM. I still can't mount the internal sdcard though and I have no phone functionality. It seems that my IMEI number is gone.
Hey
Downgrade your sgs to 2.3.6 valuepack using odin3...
Then root it and use it for a day atleast..
Then flash CM9 nightly..use that for a day too..
Then flash JB...not the same one u did earlier..
Instead Goto teamjellybean.noez.in (ad www.)
Find d latest version of jb and follow the instruction there..
Cheers
Sent from my GT-I9000 using xda app-developers app
Thanks that's exactly what I have done and it worked.
I've seen a lot of folks saying that they might have bricked their phones when some issue occured while flashing a new rom.
Personally whenever I face issues, I just goto the Download mode and Flash a GB rom and then move my way up (GB --> ICS --> JB).
As long as you can go into Download mode, shouldnt be a problem
Fwiw, I lost my IMEI for the first time trying out the JBs. Not sure if it was Slim or DerTeufel's. I ended up with the kind that allows you to connect to your mobile provider, a fake but working IMEI. But when I saw that I tried to go to GB and it didn't come back automagically. And the IMEI was totally wiped so I couldn't even register on the network. Ended up getting to ICS and only then did Root Browser let me write to the efs folder.
Lesson, in short: make a backup zip of your efs folder (to preserve permissions) and double back it up using Nitrality from the Play store.
Glad you got yours back, too.
sent from a telephonic device
tchindalia said:
Hey
Downgrade your sgs to 2.3.6 valuepack using odin3...
Then root it and use it for a day atleast..
Then flash CM9 nightly..use that for a day too..
Then flash JB...not the same one u did earlier..
Click to expand...
Click to collapse
OK, so I'm *definitely* a crappy speed-reader, because I missed this part about waiting on each version. What does the waiting do? I'm now wondering if that means I need to use the phone and, with the restored /efs folder, sometimes later /dev/block/stl3 will repopulate itself with the proper info.
Hey
I asked to wait on roms coz it can just make a few things working...like data..if it doesnt work on 1 rom it would not (probably) work on the next update..(personal experience)..
Cheers
If my post helped, don't mind hitting the Thanks button..
Hello developers from XDA!
I have three questions that I was hoping you guys could answer.
First off, I own a Samsung Galaxy S GT i9000 and I'm currently running on 2.3.6 gingerbread XXJVU rooted.
I have been searching EVERYWHERE for a stable jellybean 4.1.2 ROM for my phone, but there are so many and the instructions are very complicated, resulting me into not really understanding how to flash it..
I have earlier tried to flash and ICS ROM which hugely failed. Flashing the stock rom & rooting it went succesfully, but after trying to install the rom from the recovery menu it didn't work. The result was that it was taking nearly up to an hour to start up. I had taken the battery out the phone and restarted before I waited so long. (Yes, believe it, or not. I have seriously waited an hour for it to start up. It just didn't want to.)
So my questions:
Do any of you from XDA developers know a STABLE jellybean rom which has most of the features available? For instance; calling, SMS, Wi-Fi, 3G, Play Store, USB acces etc.
I've heard that "Cyanogenmod 10" was a good one..
Second question is: IF any of you could provide me with a link to a rom (hopefully as I mentioned before Cyanogenmod 10) can you please provide a link with instruction on how to flash it? I really don't want to spend around 30 minutes to find out what I must do.
Also, I've heard that it's not a good idea to go from 2.3.6 to 4.1.2 instantly. I actually want to take the chances and go to Jellybean instead of first flashing and ICS rom.
And as for my last question: I will of course do a nandroid backup in recovery. But, if the jellybean rom fails to flash will I still be able to use that backup? As I mentioned before, I failed flashing an ICS rom. But when I did my recovery menu changed? It went from ClockWorkMod to a different one with a different colour. I haven't really looked at the backup files in the new recovery menu, but if I flash the jellybean mod I assume my recovery menu will change from CWM to CM, and resulting (I think) removing the backup files?..
If neccessary I'll post my entire device information:
Device information:
Model number: GT-I9000
Android version: GINGERBREAD_MR1 2.3.6 (SDK 10)
Kernel version: 2.6.35.7-i9000XXJVU-CL851880
Buildnumber: GINGERBREAD.XXJVU
I hope these questions could be answered!
Thanks in advance.
P.S.: Sorry if I posted this in the wrong section.
Hey,
so first of all I'd recommend Mackay ROM 1.5.9 which is based on CyanogenMod 10 but tries to stay as close as possible to stock Jelly Bean. You can find it in the development section.
To your second point: Go on CM9 first (twice!) then flash a clean CM10 and afterwards finally Mackay. If you got questions regarding that, you can ask me ofc But to be honest you have to read and try a bit to get into these things. I can explain a lot but you have to think yourself before doing something
Best regards
Sent from my Gameboy Color
inMindAndroid said:
I really don't want to spend around 30 minutes to find out what I must do.
Click to expand...
Click to collapse
:thumbdown:
BlueFlame4 said:
To your second point: Go on CM9 first (twice!) then flash a clean CM10 and afterwards finally Mackay.
Click to expand...
Click to collapse
Alternatively you could just do a factory reset and flash CM10 Fishears since it uses the same partition layout as stock, avoiding the need to flash middlemen and format drives.
Let's start with a little background as to how I got into this mess
- I had a perfectly working i8190L running SlimBean 4.3 from Maclaw (and I should've left it alone since its the wife's phone)
- I wanted to try out the new SlimKat 4.4 (http://get.novafusion.pl/?id=955)
- After a clean flash of slimkat, the new ROM was running fine after I completed setup EXCEPT baseband was 'xxxx'
- I rebooted into recovery and flashed GT-I8190_modem.bin-XXAMJ3-update2.zip because it was in my sdcard. I thought flashing a new radio would change the baseband except now I'm stuck in a bootloop with NO ABILITY TO BOOT TO RECOVERY!!!!
- I can only boot into Download mode, so I can still ODIN flash the system
Can someone suggest how/if I can fix this? I'm just kicking myself for turning a fully working phone into a brick with my wife breathing down my shoulders
my working setup was TWRP 2.7, SlimBean 4.3 and I had no idea which radio the i8190L came with default
I created a nandroid before all this mess, but I just need a way to get back into Recovery
You downloaded the wrong modem file. You need the one for the I8190L, but you flashed one for the I8190.
Sent from Tapatalk on my GT-I8190 running Novafusion's Carbon 4.4.2
chan1628 said:
Let's start with a little background as to how I got into this mess
- I had a perfectly working i8190L running SlimBean 4.3 from Maclaw (and I should've left it alone since its the wife's phone)
- I wanted to try out the new SlimKat 4.4 (http://get.novafusion.pl/?id=955)
- After a clean flash of slimkat, the new ROM was running fine after I completed setup EXCEPT baseband was 'xxxx'
- I rebooted into recovery and flashed GT-I8190_modem.bin-XXAMJ3-update2.zip because it was in my sdcard. I thought flashing a new radio would change the baseband except now I'm stuck in a bootloop with NO ABILITY TO BOOT TO RECOVERY!!!!
- I can only boot into Download mode, so I can still ODIN flash the system
Can someone suggest how/if I can fix this? I'm just kicking myself for turning a fully working phone into a brick with my wife breathing down my shoulders
my working setup was TWRP 2.7, SlimBean 4.3 and I had no idea which radio the i8190L came with default
I created a nandroid before all this mess, but I just need a way to get back into Recovery
Click to expand...
Click to collapse
Sorry but you are going to sleep on the couch tonight I suggest this:
You must download the original rom from SamMobile, install it through Odin and then install again through Odin the Recovery and through Recovery your "old" new Rom. When you are in the new Recovery check for the nandroid backup that you made . If it isnt there look for the couch because the phone is with the "old" new Rom without any of the past data.
Btw if you want you can upgrade your baseband from here:http://forum.xda-developers.com/showthread.php?t=2526831
Good luck
No recovery at all or bootloop in recovery as well?
Sent through time and space from my s3mini/CM11
chan1628 said:
Let's start with a little background as to how I got into this mess
- I had a perfectly working i8190L running SlimBean 4.3 from Maclaw (and I should've left it alone since its the wife's phone)
- I wanted to try out the new SlimKat 4.4 (http://get.novafusion.pl/?id=955)
- After a clean flash of slimkat, the new ROM was running fine after I completed setup EXCEPT baseband was 'xxxx'
- I rebooted into recovery and flashed GT-I8190_modem.bin-XXAMJ3-update2.zip because it was in my sdcard. I thought flashing a new radio would change the baseband except now I'm stuck in a bootloop with NO ABILITY TO BOOT TO RECOVERY!!!!
- I can only boot into Download mode, so I can still ODIN flash the system
Can someone suggest how/if I can fix this? I'm just kicking myself for turning a fully working phone into a brick with my wife breathing down my shoulders
my working setup was TWRP 2.7, SlimBean 4.3 and I had no idea which radio the i8190L came with default
I created a nandroid before all this mess, but I just need a way to get back into Recovery
Click to expand...
Click to collapse
Don't bother trying to flash it if nothing happens, drain the battery, return to seller and get replacement. I got free replacement from Amazon with my bricked rooted S3 mini.
jstath1972 said:
Sorry but you are going to sleep on the couch tonight I suggest this:
You must download the original rom from SamMobile, install it through Odin and then install again through Odin the Recovery and through Recovery your "old" new Rom. When you are in the new Recovery check for the nandroid backup that you made . If it isnt there look for the couch because the phone is with the "old" new Rom without any of the past data.
Btw if you want you can upgrade your baseband from here:http://forum.xda-developers.com/showthread.php?t=2526831
Good luck
Click to expand...
Click to collapse
just to clarify... what is consider "the original rom from SamMobile"? There are plenty of versions and country codes to choose from... I just wanted to make sure I'm downloading the correct one.... i've done enough of using the wrong files already
KoolKid98189 said:
Don't bother trying to flash it if nothing happens, drain the battery, return to seller and get replacement. I got free replacement from Amazon with my bricked rooted S3 mini.
Click to expand...
Click to collapse
its not going to be that easy for me... i've had this phone for almost 2yrs already
tys0n said:
No recovery at all or bootloop in recovery as well?
Sent through time and space from my s3mini/CM11
Click to expand...
Click to collapse
no recovery at all... it bootloops if i power on normally
chan1628 said:
just to clarify... what is consider "the original rom from SamMobile"? There are plenty of versions and country codes to choose from... I just wanted to make sure I'm downloading the correct one.... i've done enough of using the wrong files already
Click to expand...
Click to collapse
It depends on what country you're in and if the phone is locked to any specific carrier.
If it's not locked then I believe any i8190L firmware will do, just to get the phone running again.
chan1628 said:
its not going to be that easy for me... i've had this phone for almost 2yrs already
no recovery at all... it bootloops if i power on normally
Click to expand...
Click to collapse
It was a tough decision for me, it was either stick to a ****ty BlackBerry or get a free replacement and sacrifice the data. Some of it should be synced to your Google account
tys0n said:
It depends on what country you're in and if the phone is locked to any specific carrier.
If it's not locked then I believe any i8190L firmware will do, just to get the phone running again.
Click to expand...
Click to collapse
ok, i will give all this a try and hope for the best
thanks everyone for the quick responses :good:
You could also try to reflash just recovery thru Odin and see if it works.
Sent through time and space from my s3mini/CM11
chan1628 said:
just to clarify... what is consider "the original rom from SamMobile"? There are plenty of versions and country codes to choose from... I just wanted to make sure I'm downloading the correct one.... i've done enough of using the wrong files already
Click to expand...
Click to collapse
You are in Canada but the L version is for the Latin America countries. So the firmware must be from one of that countries. Which one i can't tell you. You should ask your seller.
[problem solved]
Ok, I was able to restore the phone with /u/jstath1972's suggestion
1. I went to http://www.sammobile.com/firmwares/ and downloaded the latest 'L' firmware
2. I used ODIN to flash the firmware
3. the phone REBOOTED!!!
(once the phone rebooted, the rest was easy)
4. powered off and ODIN flashed the lastest TWRP
5. powered off and booted into recovery
6. RESTORED NANDROID so wife would stop giving me the look
7. updated baseband as suggested: http://forum.xda-developers.com/show....php?t=2526831
THANK YOU THANK YOU :good:
side note: i wish my work was this effective in resolving technical issues (just my 2 cents)
chan1628 said:
Ok, I was able to restore the phone with /u/jstath1972's suggestion
1. I went to http://www.sammobile.com/firmwares/ and downloaded the latest 'L' firmware
2. I used ODIN to flash the firmware
3. the phone REBOOTED!!!
(once the phone rebooted, the rest was easy)
4. powered off and ODIN flashed the lastest TWRP
5. powered off and booted into recovery
6. RESTORED NANDROID so wife would stop giving me the look
7. updated baseband as suggested: http://forum.xda-developers.com/show....php?t=2526831
THANK YOU THANK YOU :good:
side note: i wish my work was this effective in resolving technical issues (just my 2 cents)
Click to expand...
Click to collapse
Good sleep tonight, my friend ! :good:
I have just recently restarted using this phone due to my uscellular S4 getting turned off. I am now back on my LG-P990 currently rooted and running CM10.1. BUT most importantly to me is the fact that I have all my wonderful apps on my s4, I want to be able to use them by using the LG phone as a tether and calls not much else BUT CM10.1 tethering does not work, so i find myself flashing rom after rom, avatar rom, older CM mods, none would turn on tethering, so i flashed a modded version of MIUI for this phone and it worked except for ONE thing no signal, tethering turned on just fine so i decided to look around for other roms and found Slimrom TRYED to flash it didnt work, try to flash actual MIUI roms off there site, didnt work, met with an error in CWM Recovery after some searching I found its because Im running the OLD Bootloader -_- THIS is the issue im having IF MIUI does NOT work is it possible to downgrade the bootloader again so i can restore my CM10.1 backup? I have been working at this for a week, if there is something here about this can someone please just point me at it? I would appreciate any help.
On a side note i DID soft brick the phone the other day and found a program called nvflash witch flashed an install of CM mod. Dont know if that will help any.
Jeffril said:
I have just recently restarted using this phone due to my uscellular S4 getting turned off. I am now back on my LG-P990 currently rooted and running CM10.1. BUT most importantly to me is the fact that I have all my wonderful apps on my s4, I want to be able to use them by using the LG phone as a tether and calls not much else BUT CM10.1 tethering does not work, so i find myself flashing rom after rom, avatar rom, older CM mods, none would turn on tethering, so i flashed a modded version of MIUI for this phone and it worked except for ONE thing no signal, tethering turned on just fine so i decided to look around for other roms and found Slimrom TRYED to flash it didnt work, try to flash actual MIUI roms off there site, didnt work, met with an error in CWM Recovery after some searching I found its because Im running the OLD Bootloader -_- THIS is the issue im having IF MIUI does NOT work is it possible to downgrade the bootloader again so i can restore my CM10.1 backup? I have been working at this for a week, if there is something here about this can someone please just point me at it? I would appreciate any help.
On a side note i DID soft brick the phone the other day and found a program called nvflash witch flashed an install of CM mod. Dont know if that will help any.
Click to expand...
Click to collapse
I really do not understand how other ROMs deny Tethering. Did you flash the latest 2.x kernel by pengus77 after installing the rom? Did you make a clean install(wipe everything then install)? On the other hand, yes you can switch bootloaders as much as you like, just remember that changing the bootloader wipes everything on your internal memory, so do a backup. Did you try just plain old stock 4.0.4? Should work there. Ask anything you want, if you're still having questions.
NoDze said:
I really do not understand how other ROMs deny Tethering. Did you flash the latest 2.x kernel by pengus77 after installing the rom? Did you make a clean install(wipe everything then install)? On the other hand, yes you can switch bootloaders as much as you like, just remember that changing the bootloader wipes everything on your internal memory, so do a backup. Did you try just plain old stock 4.0.4? Should work there. Ask anything you want, if you're still having questions.
Click to expand...
Click to collapse
As to the flashing to stock i lost the original rom backup i had made along time ago and cant find the original firmware anywhere online. When I flashed CM 10.1 I just ran with it, when i go to try tethering it says "Turning on portable wifi hotspot." and it stays on that no matter what untill i restart, left the phone running for 2 days once and that was still stuck on that before i restarted. As for flashing a 2.x kernel i had no idea about that. But yes when i did the installs i would do a clean wipe and install. Most of what i read online led me to believe that there was an error with CM 10.1 nightlys that was not being fixed for the tethering. So that is why i decided to go to another rom. Two questions one how do i go about finding the original firmware for this phone and two how would i go about updating or downgrading the bootloaders and could i be pointed to the files please?
Jeffril said:
As to the flashing to stock i lost the original rom backup i had made along time ago and cant find the original firmware anywhere online. When I flashed CM 10.1 I just ran with it, when i go to try tethering it says "Turning on portable wifi hotspot." and it stays on that no matter what untill i restart, left the phone running for 2 days once and that was still stuck on that before i restarted. As for flashing a 2.x kernel i had no idea about that. But yes when i did the installs i would do a clean wipe and install. Most of what i read online led me to believe that there was an error with CM 10.1 nightlys that was not being fixed for the tethering. So that is why i decided to go to another rom. Two questions one how do i go about finding the original firmware for this phone and two how would i go about updating or downgrading the bootloaders and could i be pointed to the files please?
Click to expand...
Click to collapse
Okay, This is SFSP by @sgspluss which is a pretty fast, stable and battery-friendly slimmed down version of stock ICS. It is available for both Old and NewBL, so you might want to try that first. This is AIO Toolkit. I know that you've used it and bricked your phone, but try again, and for the love of God install the nvflash drivers because most people skip that part. You have to do it manually and if you're running Windows 8 you need to disable Driver Signature Verification. But yeah, you switch bootloaders with this.
Today I made a first step towards custom ROM by installing the latest TWRP with Odin and taking a backup of all partitions. Rebooted and unfortunately now I have IMEI null and baseband null (it was originally I9305XXUFOA1 I believe)
Nothing else has been touched, I am still using stock ROM, and reset to factory default did not solve it...
I still have the IMEI number and a backup of the EFS partition. But when I restored this partition with TWRP, I still have No Signal.
I searched the forums and only thing closest is a post about the S4: http://forum.xda-developers.com/showthread.php?t=2370699
Is there any suggestion on what I can try to recover this problem?
If I type *#1234#, I get
AP I9305XXUFOB2
CSC I9305PHNFOB2
But no CP?
Now I did a total restore of the backup made with TWRP, but still "unknown baseband"
In case it helps others, here is what I learned
When flashing TWRP 2.8.7.0 on my 9305 with Odin, my modem becomes unusable every time.
It can be easily restored if you have the modem firmware, so that solved it. But it seems TWRP is very unreliable until I downgraded to an older version of it, 2.7.0.0. Now everything is working, although it can be tricky to get into the recovery mode (holding buttons for up to 30 seconds). I suppose this is normal behaviour...
Help please
cpct said:
In case it helps others, here is what I learned
When flashing TWRP 2.8.7.0 on my 9305 with Odin, my modem becomes unusable every time.
It can be easily restored if you have the modem firmware, so that solved it. But it seems TWRP is very unreliable until I downgraded to an older version of it, 2.7.0.0. Now everything is working, although it can be tricky to get into the recovery mode (holding buttons for up to 30 seconds). I suppose this is normal behaviour...
Click to expand...
Click to collapse
Hi, I'm going nuts reading for the past 5 hours all the info about this issue and the multiple solutions i have tried with no success, i just stumbled in your post which describes exactly my problem, after flashing twrp bam!!
I have no backups, i bought this phone yesterday, unrooted this morning , spent some hours customizing stuff, got to the point to install a recovery to do a nand backup as the phone had all the apps and settings i wanted and this just happened, i am now going to do a complete stock flash, will it repair my modem? If not can you please provide me with a link to the modem firmware? Is it country associated, will i need a specific for my country/operator?
Thanks,
Bruno
bpi_pt said:
Hi, I'm going nuts reading for the past 5 hours all the info about this issue and the multiple solutions i have tried with no success, i just stumbled in your post which describes exactly my problem, after flashing twrp bam!!
I have no backups, i bought this phone yesterday, unrooted this morning , spent some hours customizing stuff, got to the point to install a recovery to do a nand backup as the phone had all the apps and settings i wanted and this just happened, i am now going to do a complete stock flash, will it repair my modem? If not can you please provide me with a link to the modem firmware? Is it country associated, will i need a specific for my country/operator?
Thanks,
Bruno
Click to expand...
Click to collapse
Hi Bruno,
You should try to (re)flash only the modem with Odin. It's not so difficult, just take your time to familiarize with the steps.
To get a modem.bin, either you extract it yourself from a stock rom zip (see http://www.sammobile.com/firmwares/) or get one from the topics at xda (for the 9305 I got XXALK2 from http://forum.xda-developers.com/gal...05/modems-i9305-cwm-flashable-modems-t2010116).
I suppose you have no access to TWRP right now? If so, reflash it with Odin too. I recommend version 2.7.0; it works for me very well. Then immediately take backup of everything (EFS etc) and transfer it to your PC
Let us know how it goes,
SOLVED: Null IMEI and baseband
Hi all,
My problem is solved, after flashing the latest stock ROM for my model (I9300) I got my IMEI back and everything back to normal, as told I could have just the modem.bin flashed but I went for the full re-image.
Then i unrooted using cf-autoroot and flashed twrp version 2.8.6.0 instead of 2.8.7.0, rebooted and everything ok. I already performed a full nand backup and learned various lessons from this. I think guys at TWRP should know that their latest version for the galaxy s3 is causing this problem, i believe most people will send their phones for repair because there are so many possible causes for this problem and so many xdifferent possible solutions that most people will quit solving the problem and will try to return the phone for repair.
Thanks for your reply and for the help. I will send an email to twrp linking to this thread.
Melhores cumprimentos ( portuguese for Best regards)