[Q] Baseband Unknown/IMEI etc dissapears after reboot. - Galaxy S II Q&A, Help & Troubleshooting

Hi,
Whenever i turn my phone off and back on again it fails to recognise my baseband or IMEI. I have seen other threads on this forum relating to this but not specifically after a reboot.
If the phone stays on there seems to be no problem and when I rebooted in my flat last night (where I have strongish signal) it doesn't seem to be a problem (though i would need to check this again).
So far my fixes is, and this works everytime:
- Reboot recovery,
- Flash rom/kernel (cmexperimental)
- wipe dalvik
- wipe cache
- reboot.
This is not really feasible long term as it is a battery drain and not how a phone should be! I do have a EFS backup apparently though i did not do this back up intentionally. It is dated the 18th September of this year, i've heard Siyah back ups efs automatically so worse case i should have that there but i know that it's not ideal to mess around with EFS.
Can anybody help me? I can supply further information.
This problem started earlier this week after i flashed PA 2.54 and then restored a nandroid back up of the changmin rom.
I would really appreciate any help. if i've missed anything out i apologise.
Thanks

I have a similar problem and Apparantly you need to restore a backed up efs to fix it there is this app it hasnt worked for me though.
https://play.google.com/store/apps/details?id=com.helroz.GSII_Repair

1Chef said:
I have a similar problem and Apparantly you need to restore a backed up efs to fix it there is this app it hasnt worked for me though.
Click to expand...
Click to collapse
can i ask what you did to cause the issue in the first place? any idea?

Im using neat rom (http://forum.xda-developers.com/showthread.php?t=1569686) and I flashed an aroma mod to add more options to it, I then rebooted and I had no signal, imei no anything and this message kept appearing (see pic)
The way I fixed it was to just reflash the rom and it removed the aroma mods, I decided today to just keep the standard rom with no mods and its looking good as ive rebooted 4 times so far and nothings happen except on one reboot i lost 62% wtf. The dev of the rom (salesale) pm'd me and explained how to fix it by editing your efs backup and then placing it back and using command lines to replace the old one, this didnt work for me though.

1Chef said:
Im using neat rom (http://forum.xda-developers.com/showthread.php?t=1569686) and I flashed an aroma mod to add more options to it, I then rebooted and I had no signal, imei no anything and this message kept appearing (see pic)
The way I fixed it was to just reflash the rom and it removed the aroma mods, I decided today to just keep the standard rom with no mods and its looking good as ive rebooted 4 times so far and nothings happen except on one reboot i lost 62% wtf
Click to expand...
Click to collapse
yeh i'm going to try factory reset and a fresh rom install to see if that fixes the problem. nice to hear there is hope and all the time it is working it's not so bad! just have to cut down on the amount of flashing i do!!
Is that neat rom ICS or JB? i really don't want to go back from JB to ICS!

Jelly bean of course its nice and stable, and you can't hide it, if your a flashaholic your gonna flash wow wtf your post was apparantly sent from 01/01/1970

Ok I've done a clean install of neat rom and installed the aroma mods. This has once again deleted all of the IMEI and other data like that, after lots of googling and using the repy from neat roms developer (salesale) I managed to do the steps he posted I also found this forum which outlines the steps of what to do, you will need to do the command lines in recovery, to unmount the efs so youll need this ( I think you should have this anyway as its great) I unfortunately couldn't do this as I get stuck on the last command line with: tar: invalid tar magic I have retreated back to just standard neat rom which for some reason unknown to me will not delete my IMEI but will do so upon the next reboot with aroma mods flashed WTF .

Related

SIM cantread after Nandroid backup :(

Hi guys,
I wonder if someone can help me with this... really annoying problem!
I was checking out various roms i downloaded here, started with 4.0 aokp which was great, then gave cyanogen 4.2 a try, but then i wanted to go back to Aokp 4.0 cause it seemed to run faster
Now first thing, i couldnt get rid of cyanogen (no offense intended) cause when i wiped all data, cache and dalvik it just took aokp a few seconds to install from CWM recov, that doesnt seem right, right?
Then installed GAPPS, but still it ran on Cyanogen
So, i did a NANDROID backup, which made my phone like before i started with all this..
THIS IS WHERE IT WENT WRONG?
now it just wont read my simcard
i tried my sim in my old phone and that works fine, so the problem is in my phone somehow
is it something about the radio settings specific to my phone and network?
how can i change these settings and are they specific for my provider?
you guys always helped me out so i hope you know what i mean..
kipdeontdekker said:
Hi guys,
I wonder if someone can help me with this... really annoying problem!
I was checking out various roms i downloaded here, started with 4.0 aokp which was great, then gave cyanogen 4.2 a try, but then i wanted to go back to Aokp 4.0 cause it seemed to run faster
Now first thing, i couldnt get rid of cyanogen (no offense intended) cause when i wiped all data, cache and dalvik it just took aokp a few seconds to install from CWM recov, that doesnt seem right, right?
Then installed GAPPS, but still it ran on Cyanogen
So, i did a NANDROID backup, which made my phone like before i started with all this..
THIS IS WHERE IT WENT WRONG?
now it just wont read my simcard
i tried my sim in my old phone and that works fine, so the problem is in my phone somehow
is it something about the radio settings specific to my phone and network?
how can i change these settings and are they specific for my provider?
you guys always helped me out so i hope you know what i mean..
Click to expand...
Click to collapse
I've exactly the same problem.
Are your wifi and BT still OK ?
Is your IMEI (*#06#) still the same as under the battery ?
Was your phone locked ? Did you buy it with a SIM ?
My problem appeared after flashing several different modems/RILS : I got no error warning anywhere, but after reboot, I completely lost my netwerk connection. (no voice calls , no mobile data)
At first I thought a bad RIL driver, so I restored my Nandroid backup from the day before (after wipe cache/wipe dalvik/format system), but still no connection with the netwerk. and can't even make voice calls.
Then I was in panic !
After this I did a complete factory reset, and wiped/formatted cache/dalvik/system/data/SD-card and went in to download mode. After loading a stock ELLA for my region using Odin, still no connection. I was also never asked to enter the PIN-code for my SIM to unlock it.
Damned, this is an embarrassing situation : I can't think of loosing my SG3 for several weeks if I have to send it to Samsung !!
Mu phone is bought without SIM, so it's not SIM-locked.
My Wifi and BT are still OK, my IMEI is also still OK.
Any other ideas, please ?
How do I come in the service mode for the Radio ?
This is the way my netwerk is indicated : a circle with a stripe, much like the famous traffic sign.
Its fixed
So i have no idea how it eventually got fixed but if someone else has this problem, heres what i did:
Full wipe/factory reset blablabla all that
Did Nandroid restore again, put the AOKP ROM and GAPPS back on my phone
Installed ROM which was I9300CEDLI1
Used Odin to install latest CWM, which was already on there, but still
Then booted into CWM and installed .zip of course
This still went suspiciously fast since the very first time it took way longer, that worried me but,
Installed GAPPS again,
Rebooted... IT ASKED FOR MY PIN NUMBER!! hell yes that was what i wanted!
So now it again sees my simcard in there, so now i can make calls end use intnet again!
Still i think it started after the nandroid backup for some reason, or it may have been because of wiping Dalvik Cache?
I have no idea if that even makes sense
kipdeontdekker said:
Its fixed
So i have no idea how it eventually got fixed but if someone else has this problem, heres what i did:
Full wipe/factory reset blablabla all that
Did Nandroid restore again, put the AOKP ROM and GAPPS back on my phone
Installed ROM which was I9300CEDLI1
Used Odin to install latest CWM, which was already on there, but still
Then booted into CWM and installed .zip of course
This still went suspiciously fast since the very first time it took way longer, that worried me but,
Installed GAPPS again,
Rebooted... IT ASKED FOR MY PIN NUMBER!! hell yes that was what i wanted!
So now it again sees my simcard in there, so now i can make calls end use intnet again!
Still i think it started after the nandroid backup for some reason, or it may have been because of wiping Dalvik Cache?
I have no idea if that even makes sense
Click to expand...
Click to collapse
Good to hear your problem is fixed !
I'm still not able to make voice calls or enable mobile data : "insert SIM card" is the message I get.
I did already twice a full reset/factory restore and flash a stock ROM using PC Odin, but no avail.
Today I did a restore from my EFS folder using a backup that a had made before the problem appeared, but no avail.
BTW, did you also have the same indication from network status as on my screen-shot ?
Any idea what else I can try ?
I'm getting desperate .....
I'm having the same trouble after doing backup in TWRP when boot up it doesn't recognize the sim card.
I've flash CM10.1 and it only work after i remove the card e put it back on.
Try to see if it something about the simcard.
Regards,
Rui

Unfortunately, system UI has stopped

my phone suddenly restarted while i was launching skype, and when i came back on it showed a "unfortunately system ui has stopped" message. if i tap ok or report it just gives more of the same popup. tried wiping and reflashing but it happened again after 2 hours of usage.
i am using rootbox 3.6
Terens said:
my phone suddenly restarted while i was launching skype, and when i came back on it showed a "unfortunately system ui has stopped" message. if i tap ok or report it just gives more of the same popup. tried wiping and reflashing but it happened again after 2 hours of usage.
i am using rootbox 3.6
Click to expand...
Click to collapse
Oh boy.....read the topic and I thought "reflash".
So....as you have already done the reflash thing, my advice is go stock for a day.
And then go back to rootbox.
And maybe run these scripts that theatheist is promoting. Those are cleaning scripts, could help removing all the previous ROM's waste.
Sent from the little guy
gastonw said:
Oh boy.....read the topic and I thought "reflash".
So....as you have already done the reflash thing, my advice is go stock for a day.
And then go back to rootbox.
And maybe run these scripts that theatheist is promoting. Those are cleaning scripts, could help removing all the previous ROM's waste.
Sent from the little guy
Click to expand...
Click to collapse
^^this
Got the same problem with different rom. It first started t do that with RR 3.1.3 and I thought I'd try the revolt 3.2. Flashed and everything was fine. I really started to love this new rom and then boom "unfortunately system ui has stopped"... I did everything like the instructions said but didn't run any cleaning scripts. Always these things happen to me... How can I get rid of this? Please help, my phone is useless because the warning just keep popping back! How does one run cleaning scripts?
Nuke script.
Sent from the little guy
Thanks for fast reply! I decided to try reflashing first. This time I chose CM10.1 kernel instead of dorimanx 7.46. Everything seems to be ok again but I'm afraid that the warning pops up very soon. I downloaded that nuke script but I hope reflashing helped. So what exactly that script will erase? Can I lose something important?
Is this a known issue? I couldn't find many similar cases and I'm fairly new to using custom roms above android 2.3... I'm just trying to figure out what caused this whole thing. I was installing new apps on the fresh rom and suddenly it popped up. It did this on the last minutes when I was using RR 3.1.3 rom and I have been using that rom for about 2 weeks without that kind of problems.
edit. Holy s***! I figured out what's causing this for me! Atleast I got rid of it for a while now. So I reflashed and did everything as the instructions say; wipe data, cache, dalvik, format /system & flash followed with wiping cache & dalvik. I chose CM10.1 kernel to test if that has anything to do with it. Everything started ok and again I started to customize settings and launcher. I was enabling toggles from the ROM Control menu and when I ticked on the "Profiles" toggle the warning came right away and came back again and again after tapping ok. There's about 0.5 second delay after you tap ok and when the message pops up again. During that delay I was able to go back to toggle settings and untick the "Profiles" toggle. Tapped ok to the warning and suddenly it was gone without coming back! I have always been good at finding bugs and stuff but this must be the first time when I find a solution for it on my own! Feels so good that I'm gonna reward myself with a beer! Hopefully that isn't too early reward... Just an excuse to get a beer =)
Read that script thread, it'll remove all previous ROMs left overs.
The thing about custom ROMs & kernels is that they are not that stable at the time, simply because stock JB is showing some bugs and all.
Siyah v6 final is out know, try that.
Sent from the little guy

[Q] FIXED! ATT SGH-I717 Sim card error!!

*READ BELOW FOR A GUIDE TO FIX*
I've had my note for over a year now and i have had it rooted pretty much the entire time. Never any problems with it up until recently it started doing this thing where it would keep restarting. It would boot up and less than a minute later just restart. Off and on for a few days it was doing this. I was still running 2.3.6 at that point. So i decided to push 4.0.4 via odin since kies didnt support the firmware. Everything was working fine for a few hours then all of the sudden "the ring of death" showing me no service. Went through the phone and noticed it was saying there is no sim inserted. Tested sim on another phone. Works fine. Since then ive figured out via kies i can recovery and update firmware. Tried that. No Bueno. Now im to the point where im on 4.0.4 with no service. I've scoured through forums trying all kinds of different things, pushing different roms and modems via odin and cwm. Still no bueno.
Baseband version
Unknown
Kernel Version
3.0.8
Build Number
IMM76D.UCLF6
If anyone can give me ideas im willing to try them out.
Thanks.
I got it working so heres a direction for anyone else who has this issue!
Replaced Sim&SD card reader-No fix
After flashing all kinds of roms & modems still same issue saying no sim inserted.
Do a hard reset through your settings.
Flash cwm and put the radio from this link on your sd card. Use cwm to flash the radio.
Flash rom http://forum.xda-developers.com/showthread.php?t=2261598 via odin.
The first try i got an error during flash and got stuck on the software download error screen.
Reflashed the JB rom.
After its flashed flash clockwork recovery.
Enter cwm and do a factory reset. Clear cache. Clear dalvik cache. Reboot system.
If you get service, turn off phone. enter cwm and do a backup.
Reboot system.
It should be working.
If not restart and make sure to do a factory reset through your settings in the phone before reflashing rom.
Got the Phone up and running for about 30 mins.
After battery removed it reverted back to no sim card inserted.
Kept reflashing rom until it worked again.
Flashed cwm.(ClockworK recovery mod)
Deleted cache, dalvik cache
Backed up via cwm
If it reverts back to no sim after that restore using the cwm backup.-it worked for me
Now for the tricky part, my phone was getting crappy service...
So heres what i did to fix it.
Settings-more settings-mobile networks-access point names-click on the apn.
Name-
ATT Phone
APN-
Phone
Proxy-
Not set
Port
Not set
User Name-
Not set
Password-
Not set
Server-
Not set
MMSC-
http://mmsc.mobile.att.net
MMS Proxy-
proxy.mobile.att.net
MMS Port-
80
MCC-
310
MNC-
410
Authentication type-
None
APN type-
default,admin,fota,mms,supl,hipri,internet
APN protocol-
IPv4
Enable/disable APN-
(check mark)
Bearer-
Unspecified
Hope this helps anyone else having this issue.
I believe I've read something like this before. I think they fixed it by starting over from scratch. Try returning to stock thru Odin. Then root and flash rom of choice.
440bro said:
I believe I've read something like this before. I think they fixed it by starting over from scratch. Try returning to stock thru Odin. Then root and flash rom of choice.
Click to expand...
Click to collapse
I Started from scratch via "kies emergency recovery".
No luck.
dweeezy said:
I Started from scratch via "kies emergency recovery".
No luck.
Click to expand...
Click to collapse
did you try rolling back to GB? it could be a bad port on your phone. that was my problem.
Stuck power button. Your pants are too tight.
Theoriginalgiga said:
did you try rolling back to GB? it could be a bad port on your phone. that was my problem.
Click to expand...
Click to collapse
i ordered a new sim port to see if that works. what is gb?
Same situation...finally went to ATT and had a "new" phone sent under warranty. Of course NOW I'm pulling my hair out trying to migrate everything over to the new phone. I rooted and every ROM I try and install aborts. **** me. I don't even know where to start anymore
dweeezy said:
i ordered a new sim port to see if that works. what is gb?
Click to expand...
Click to collapse
GB stands for Gingerbread which was the first version of the OS that came with the phone. I believe the number was 2.3.6 (you can take a look in the about section in the settings and it'll tell you what you're currently running). ICS is Ice Cream Sandwhich which for our phone was 4.0.4 i believe. Jelly bean just came out today which you can use Kies to upgrade to and that I believe is 4.1.2. The numbers don't really mean a think, just the classification of what the OS is so if your phone reads something else (say 2.3.4) assume your phone is right and I'm wrong. I can't remember OS versions to save my life haha.
But you can use Kies to do an emergency recovery and I THINK it'll install Gingerbread. that's where I'd start, then test it, and then move to ICS and test, and then move to JB and test. I know long tedious process, but sometimes it's necessary. Imagine how fun I am to talk to on the phone while troubleshooting a computer :laugh:
redman9 said:
Same situation...finally went to ATT and had a "new" phone sent under warranty. Of course NOW I'm pulling my hair out trying to migrate everything over to the new phone. I rooted and every ROM I try and install aborts. **** me. I don't even know where to start anymore
Click to expand...
Click to collapse
what I use to migrate, and I between roms at least once a week with a full wipe because I rely on my phone being stable.
SMS and call logs: SMS Backup + (saves your call logs and sms to your gmail account. Makes a label for it and everything, pretty sweet. You can also restore from it. it takes about an hour for me to restore at 7000+ text messages).
pictures/media: stored on SD card
apps: if rooted and rommed I use titanium backup and run 2 sets. those which I want to keep my data like sms backup + to make restore easier and those I don't care about the data like google voice. If you're stock, just remember to check the little box in the beginning saying backup this phone to google (or something like that) and the next time you have to restore tick the box that says restore from google (or something like that) and it'll reinstall your apps. Mind you not the info, but it'll give you a head start.
As with your issue with installing roms. If you're using CWM i highly recommend switching to TWRP, not saying it's better in fact I like CWM better, but TWRP is the best for our roms and phone. If you have no clue what I mean by CWM or TWRP, read the all info sticky about how to rom thy phone.
I hope that helps.
Thanks OG. Yes, I know CMW and TWRP. I used to switch ROMs a lot. Finally stuck with Collective's latest (the orange one) pretty happy with it except that it's major glitch seems to be reboots whenever an app updates. So I figured unchecking auto update in Gstore should handle that.
You're saying I should try rooting w Odin again, install Superuser, then use TWRP to flash with? I'll be happy to read another 4 hrs of posts/stickies if that'll get me sorted out. I don't expect people like yourself to spend your day helping me. I'm very thankful for your tips here.
I've poured thru the "All things Gnote" threads and Noob Guides. They can be confusing as they always link out to many different threads. There is hardly ever a "Here are the steps 1. 2. 3. 4. 5.
Thanks again OG.
redman9 said:
Thanks OG. Yes, I know CMW and TWRP. I used to switch ROMs a lot. Finally stuck with Collective's latest (the orange one) pretty happy with it except that it's major glitch seems to be reboots whenever an app updates. So I figured unchecking auto update in Gstore should handle that.
You're saying I should try rooting w Odin again, install Superuser, then use TWRP to flash with? I'll be happy to read another 4 hrs of posts/stickies if that'll get me sorted out. I don't expect people like yourself to spend your day helping me. I'm very thankful for your tips here.
I've poured thru the "All things Gnote" threads and Noob Guides. They can be confusing as they always link out to many different threads. There is hardly ever a "Here are the steps 1. 2. 3. 4. 5.
Thanks again OG.
Click to expand...
Click to collapse
No problem always happy to help. since you're used to this sorta thing you don't need to use odin again and reroot. What you can do is either install TWRP through CWM using this file here:
http://goo.im/devs/OpenRecovery/sgh-i717/openrecovery-twrp-2.5.0.0-quincyatt.zip
Or you can install Goo manager, click settings and select Install OpenRecoveryScript (though that's only 2.4.4.0 the link above is 2.5.0.0)
That should change you over to TWRP. and like always do a nandroid backup and then flash to your heart's content!
fixed!
dweeezy said:
fixed!
Click to expand...
Click to collapse
How ?
galinha said:
How ?
Click to expand...
Click to collapse
i have the same issue.....i kn0w its n0t an hardware issue....my ph0ne is fairly new never dr0pped and this started happening 3 days after i p0rted black star jb alpha
I have this same issues ive tried flashing everything ive tried a new sim and replaced the card reader.
What works consistently for me if to flash the latest modem everytime i have to reboot or boot the note. Its my daughters phone now and she drains the battery regularly if it boots after charging or it needs to be rebooted for whatever reason it will come up with the no sim card error. If i flash the modem thru recovery it will work for that boot but only as long as I dont reboot or shut the phone off, then i will have to flash the modem again.
Not fixed
All. This is not fixed. I am having the same issue and if you follow the guide, it works for a day maybe regardless of what rom is loaded or what modems. Has anyone found a real solution to this yet??
i717 running stock GB or ICS or JB roms...
Thanks!
I have the exact same issue. Replaced the sim/sd card slot and still no dice ): Flashed to stock and back. Nope. Still won't work
Kraize said:
I have the exact same issue. Replaced the sim/sd card slot and still no dice ): Flashed to stock and back. Nope. Still won't work
Click to expand...
Click to collapse
I'm having the same problem. There seems to be no set way to get it back to working. Basically any reboot of the phone produces a no sim card error. I have tried flashing the modem through recovery as it was mentioned that will fix the problem. That did not work for me. What does work, sometimes, is one of the following:
1. Full wipe and reinstall
2. Restore backup from Recovery
3. Fix permissions
I just keep doing one of the above listed and eventually it works. However if the phone reboots then it's back to the carousel of trying these options to get it back to working.
I'm running Padawan JB V2
I honestly have no idea what's causing it. I haven't tried to fix permissions before to fix this issue, but if I go into recovery and install the modem again and reboot, it works fine for a while (and by a while, I mean like a few hours at max).
Just started having this issue, myself...after flashing Tmo_SGH-T989_VKL1_radio_ATTNOTE.zip modem on my phone...restoring from a prior backup...
Restoring a backup will not change your modem.

[Q] I got a boot loop and almost bricked my phone and I don´t know why

Before continuing reading, please keep in mind that the problem I am asking support for was already solved for my own. What I want to know is how did it happen. For prevention, you know.
It all started when I flashed the Black Box ROM 2.0.2 (http://forum.xda-developers.com/showthread.php?t=1834915) It flashed normally, without any problem. But, since it lacked the Xposed Framework, I installed it manually, downloading from its thread, and choosing a full install. Using the Framework I downloaded Gravity Box and the Youtube Adaway, before downloading Youtube. Since the modules needed a reboot to work, I rebooted. And this is when the bad things started to happen.
The ROM did not start. It went through the BlackBox logo, but when it appeared that the SIM unlock was going to pop up, then the phone turned off. This happened many times. So I decided to do a full wipe and install another ROM. The problem was that the phone didn´t allowed me to access the recovery.
I was using the PhilZ Touch 6, but when I pressed Volume up+Menu+Power it did not work. The only thing that worked was the Odin Menu, and I got stuck at it, I couldn´t get out the Odin Menu. So, seeing that the phone wasnt going to work anyways, I flashed a 4.3 stock ROM through Odin.
As I suspected, the ROM got stuck at boot, and got a bootloop. So then I flashed another recovery, and flashed good ol´ CWM. And It worked..for a while. The phone would shut down after some seconds. So then I tried to flash TWRP, but it lasted about one second and then the phone shut down again.
Since I was using Odin 3.03, I downloaded Odin 3-04 Moded Edition, from the Modem thread, and then reflashed CWM. In this time, it worked without failing, and I could do a full wipe and flashing an old Cyanogenmod 4.2.2 ROM, finally solving the problem. The day after I flashed Ultima ROM and at the moment it goes fine, without any problem. Which is weird, because it too uses Gravity Box and Xposed Modules. I even installed new modules, rebooted the phone and it works fine, without any problem.
What I want for the people here is that someone explains to me what happened, because the BlackBox ROM looked gorgeous and I wanted to give it a long try. And because I spent an entire night solving that problem, and well, I wont sleep in peace until I get to know what happened to that bastard
r1k1v1 said:
Before continuing reading, please keep in mind that the problem I am asking support for was already solved for my own. What I want to know is how did it happen. For prevention, you know.
It all started when I flashed the Black Box ROM 2.0.2 (http://forum.xda-developers.com/showthread.php?t=1834915) It flashed normally, without any problem. But, since it lacked the Xposed Framework, I installed it manually, downloading from its thread, and choosing a full install. Using the Framework I downloaded Gravity Box and the Youtube Adaway, before downloading Youtube. Since the modules needed a reboot to work, I rebooted. And this is when the bad things started to happen.
The ROM did not start. It went through the BlackBox logo, but when it appeared that the SIM unlock was going to pop up, then the phone turned off. This happened many times. So I decided to do a full wipe and install another ROM. The problem was that the phone didn´t allowed me to access the recovery.
I was using the PhilZ Touch 6, but when I pressed Volume up+Menu+Power it did not work. The only thing that worked was the Odin Menu, and I got stuck at it, I couldn´t get out the Odin Menu. So, seeing that the phone wasnt going to work anyways, I flashed a 4.3 stock ROM through Odin.
As I suspected, the ROM got stuck at boot, and got a bootloop. So then I flashed another recovery, and flashed good ol´ CWM. And It worked..for a while. The phone would shut down after some seconds. So then I tried to flash TWRP, but it lasted about one second and then the phone shut down again.
Since I was using Odin 3.03, I downloaded Odin 3-04 Moded Edition, from the Modem thread, and then reflashed CWM. In this time, it worked without failing, and I could do a full wipe and flashing an old Cyanogenmod 4.2.2 ROM, finally solving the problem. The day after I flashed Ultima ROM and at the moment it goes fine, without any problem. Which is weird, because it too uses Gravity Box and Xposed Modules. I even installed new modules, rebooted the phone and it works fine, without any problem.
What I want for the people here is that someone explains to me what happened, because the BlackBox ROM looked gorgeous and I wanted to give it a long try. And because I spent an entire night solving that problem, and well, I wont sleep in peace until I get to know what happened to that bastard
Click to expand...
Click to collapse
OK first black box already has xposed in ROM control settings.. so maybe because you manually installed it it may have caused conflicts... Don't know why you got a recovery bootloop... but maybe due to same problems... And I am also using blackbox 2.1 and so far it is fantastic...
Sent from my GT-I9300 using xda app-developers app
Partition structure on these phones is very fragile, one bad shutdown can corrupt one or more partitions at the same time. I'd suggest the combination of mods applied caused the kernel panic, while data was being written.
Subsequent events read like normal solution to corruption, it shouldn't happen again but best to apply framework mods one at a time.
Sent from my GT-I9300 using Tapatalk
kunal1540 said:
OK first black box already has xposed in ROM control settings.. so maybe because you manually installed it it may have caused conflicts... Don't know why you got a recovery bootloop... but maybe due to same problems... And I am also using blackbox 2.1 and so far it is fantastic...
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Hmm, I don´t remember that the BlackBox 2.0.2 had any Framework...thats why I did a manual installation. But I will try the new version 2.1. Hopefully the problems may have been solved.
boomboomer said:
Partition structure on these phones is very fragile, one bad shutdown can corrupt one or more partitions at the same time. I'd suggest the combination of mods applied caused the kernel panic, while data was being written.
Subsequent events read like normal solution to corruption, it shouldn't happen again but best to apply framework mods one at a time.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Interesting. So I have to apply mods one by one? Or can I add multiple mods because corruption has already been solved?
On a side note, when I boot the phone the red exclamation mark that used to appear has disappeared. Does that means that I somewhat reseted the flash counter to 0?

[Q] Cannot Install new ROM, Status 7 error

So the other day my S3 gave up the ghost, and developed the hard-brick "QHSUSB_DLOAD" error. I have insurance so I was overnighted a new phone, and am sending the old one away. I believe this was related to a long-term power button issue I was having, perhaps a virus, or something. I had not changed anything to the ROM I was using since about October, and the issue just happened now in May.
At any rate, the new S3 I received is an MJB version, Android 4.3, Knox and all that other good stuff. After several failed attempts, I found a method to root this phone and disable Knox. The Warranty Bit is already tripped, so clearly I'm not sending this phone back until it hard bricks as well. I am trying to install the StockMOD ROM that is very popular, however I am being plagued by problem after problem.
I was able to flash a version of CWM Recovery onto my phone, but it was too old and couldn't mount any of the folders. Using ROM Manager, I was able to flash an update to my Recovery, and now it mounts and views all folders properly. However, when I go to install the StockMOD ROM, I continuously get a Status 7 error, something about "expects 5 args, got 3." I wiped the data, cache, and Dalvik, but kept getting this error. So, I had to recover my backup of stock, which didn't go well either. Once my backup was installed, all of my apps kept crashing. Gapps, ROM Manager, everything kept giving me constant FC errors. I had to wipe my data, cache, and Dalvik again and go back to factory default, and reinitialize the phone. Luckily I haven't installed anything of importance on here yet.
A quick search through here states that I need to use TWRP as my Recovery. I've flashed TWRP several times, first using the 2.6... version and then the most recent 2.7.0.0 version, and neither of these will mount any of my folders. It just gives me a litany of errors trying to mount the various locations. I've done Fix Permissions and everything else, TWRP will just NOT mount anything. Other folks say I need the latest PhilZ Recovery. I've downloaded the latest PhilZ Touch 6 and flashed it via Odin. It is giving me the same errors as regular CWM, Status 7, "expecting 5 args, got 3."
I don't know what else to do. My S3 that ran Android 4.0 was so much easier. I had that thing rooted and running a TW based ROM with Nova launcher in about 30 minutes. This phone has been a disaster since I turned it on. I'm just trying to get a 4.3 TW based ROM. I like the Samsung Camera, Calendar, Clock, Messaging, and Contacts apps far better than AOSP versions. But I also want much more customization to my notification drawer toggles. Stock TW doesn't have the toggles I use frequently like the data toggle as well as the torch toggle.
I don't know what I'm doing wrong, because unlike a lot of folks out there, once I find a ROM I like, I stick with it. I'm not constantly updating, changing, or searching for the newest version of Android. There's nothing wrong with that, it just isn't my cup of tea. So does anyone know what I need to do? At this point, I'm about to just give up and use Nova over top of rooted stock TW and call it a day.
Thanks!
Have you tried to go back stock rom using Odin ? I think it might resolve your recovery problem
nosphor said:
Have you tried to go back stock rom using Odin ? I think it might resolve your recovery problem
Click to expand...
Click to collapse
Everything is stock except the recovery. I'm using CWM 6.0.4.7 with PhilZ Touch 6. I'm still using the stock TW 4.3 ROM that shipped with the phone. The only exception is that I'm rooted now.
I suggest you to go back to a 4.1 official stock rom with odin to be sure to have no more issue.
This can help you : http://forum.xda-developers.com/galaxy-s3/general/restore-to-stock-rom-galaxy-s3-i9300-t2187081
Also, don't forget to backup your apps with titanium backup and all your sms :good:
nosphor said:
I suggest you to go back to a 4.1 official stock rom with odin to be sure to have no more issue.
This can help you : http://forum.xda-developers.com/galaxy-s3/general/restore-to-stock-rom-galaxy-s3-i9300-t2187081
Also, don't forget to backup your apps with titanium backup and all your sms :good:
Click to expand...
Click to collapse
Unfortunately, I've heard that it is not possible to revert to anything prior to 4.3 once a phone comes factory installed with 4.3, due to all of the security enhancements and etc. My kernel, modem, and baseband are all factory stock 4.3 MJB. Everyone else on the boards, under various other topics, warn of immediate and sudden death to the phone if you attempt to install a baseband prior to 4.3 MJB.
I'm very surprised to hear that, because recently i've flash stock 4.3 rom and then go back to 4.1.2 to flash a 4.4 rom without any issue and i've got nothing for issues.
Maybe it depends on which country you are ( i'm from France ) ? For what i know , there is a VERY little chance that this downgrade cause dammage to your phone
nosphor said:
I'm very surprised to hear that, because recently i've flash stock 4.3 rom and then go back to 4.1.2 to flash a 4.4 rom without any issue and i've got nothing for issues.
Maybe it depends on which country you are ( i'm from France ) ? For what i know , there is a VERY little chance that this downgrade cause dammage to your phone
Click to expand...
Click to collapse
I'm in the USA. The security features on the I747 US version are far different. I don't know how everyone else is succeeding. I am completely lost.
You are in the wrong forum, anything you try from here will hard brick your phone.
Sent from my GT-I9300 using Tapatalk
Sorry to tell you that, but what you say is not completely true.
Yes, there is a lot of people that rush to give an answer to the question, but there is also people that really like to help people that are in trouble :good:
Please, don't take most of the case for a generality
http://forum.xda-developers.com/showthread.php?t=1756338
Sent from my GT-I9300 using Tapatalk
Yes, i've read this, i know that, that's why i talk about the difference between country, different phone model
My apologies. Thought this was the 747 board. Go ahead and lock this, I'll repost in the correct forum.
Tried TWRP?

Categories

Resources