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.
Hello everyone, I am new to this forum but have been rooting androids for years now. I have an issue now that I have never seen before. I have my HTC One rooted, S-OFF, firmware updated, everything as it should be. Heres the problem. Whenever I try to install a rom, (Insert coin, Renovate, etc.) the install goes totally fine. However, whenever I go to reboot into the system, it just hangs at the first splashscreen. The one with the green HTC logo and the powered by android at the bottom. It has sat for 5 minutes before I decided to turn it off. Anyone know a fix to this? thanks,
Parker.
PS. All of these are Aroma install roms, if that matters.
Have you tried flashing a regular Ron without AROMA, like the stock Rooted rom?
Based on the touchscreen issues with AROMA and thus phone, are you certain that you are flashing the correct carrier?
AarSyl said:
Have you tried flashing a regular Ron without AROMA, like the stock Rooted rom?
Based on the touchscreen issues with AROMA and thus phone, are you certain that you are flashing the correct carrier?
Click to expand...
Click to collapse
I've run into this on the 4.4.3 and 4.4.4 ROMs on my S-On HK edition. When the screen does go out after several minutes, I hit the power button and the phone works normally. I'm guessing that it has to do with old firmware being used with the 4.4.3+ ROM bases. I'm going to do Sunshine S-Off today so I can update my firmware and see if that makes a difference.
I have not tried a non aroma rom, that might just be my next step. I know for a fact it is the correct carrier rom, all the ones I have flashed are universal
I will try to do the power button thing you mentioned, thanks for the tip.
After work I will try all of these!
parkerskouson13 said:
I have not tried a non aroma rom, that might just be my next step. I know for a fact it is the correct carrier rom, all the ones I have flashed are universal
I will try to do the power button thing you mentioned, thanks for the tip.
After work I will try all of these!
Click to expand...
Click to collapse
Just got S-Off and upgraded the firmware to the latest. The problem has been solved for me. Boots right up now.
Which firmware did you upgrade to? I tried to upgrade to 2.22xxx and it didn't fix anything for me.
I'm an android ROM newbie, but an old computer geek from way back in the 80's, so I do have some kind of understanding. I own an ATT Note 3.
I've experienced only minor problems with the two main ROM flash tools, that is, Safestrap 3.x and Odin 3.x but that's probably my fault and they don't crash. But Safestrap? Oy vay! That works also, but in the final boot, black screen thereafter, after booting from ANY slot, whether it be stock slot of other slots. Thank God for the backup function and Odin.
But I digress. Right in the beginning of my flashing Odyssey, everything worked fine! Flashed Alliance ROM no problem, as well as Dynamic Kat.
Oh yeah. Confused about all those two letter abbreviations, there's no abbreviation key here on the forums?
I tried the other ROMS in the Note 3 Rom sections and stuck wit that, but then, under Safestrap, the machine would reboot to black screen! No matter what I did, wiping, rooting (of course), re-installing different versions of SafeStrap, from early 3.x versions to 3.75, nothing! Odin gets my machine back to it's (I THINK) original state.
Badly confused. Knox is fine at 0x0. Don't know how to move forward. I would like to continue to try different ROMS but the same thing keeps on happening. Hope someone can help me. If anyone wants some kind of log output, I can do that (just tell me how and where).
Thanks
David Sanborn said:
I'm an android ROM newbie, but an old computer geek from way back in the 80's, so I do have some kind of understanding. I own an ATT Note 3.
I've experienced only minor problems with the two main ROM flash tools, that is, Safestrap 3.x and Odin 3.x but that's probably my fault and they don't crash. But Safestrap? Oy vay! That works also, but in the final boot, black screen thereafter, after booting from ANY slot, whether it be stock slot of other slots. Thank God for the backup function and Odin.
But I digress. Right in the beginning of my flashing Odyssey, everything worked fine! Flashed Alliance ROM no problem, as well as Dynamic Kat.
I tried the other ROMS in the Note 3 Rom sections and stuck wit that, but then, under Safestrap, the machine would reboot to black screen! No matter what I did, wiping, rooting (of course), re-installing different versions of SafeStrap, from early 3.x versions to 3.75, nothing! Odin gets my machine back to it's (I THINK) original state.
Badly confused. Knox is fine at 0x0. Don't know how to move forward. I would like to continue to try different ROMS but the same thing keeps on happening. Hope someone can help me. If anyone wants some kind of log output, I can do that (just tell me how and where).
Thanks
Click to expand...
Click to collapse
Sounds like maybe your flashing kit kat over jellybean or the other way around. Make sure if you have going to different android versions you flash the right Odin files each time. And install the right right version of safe strape. Or you get black screens
David Sanborn said:
I'm an android ROM newbie, but an old computer geek from way back in the 80's, so I do have some kind of understanding. I own an ATT Note 3.
I've experienced only minor problems with the two main ROM flash tools, that is, Safestrap 3.x and Odin 3.x but that's probably my fault and they don't crash. But Safestrap? Oy vay! That works also, but in the final boot, black screen thereafter, after booting from ANY slot, whether it be stock slot of other slots. Thank God for the backup function and Odin.
But I digress. Right in the beginning of my flashing Odyssey, everything worked fine! Flashed Alliance ROM no problem, as well as Dynamic Kat.
Oh yeah. Confused about all those two letter abbreviations, there's no abbreviation key here on the forums?
I tried the other ROMS in the Note 3 Rom sections and stuck wit that, but then, under Safestrap, the machine would reboot to black screen! No matter what I did, wiping, rooting (of course), re-installing different versions of SafeStrap, from early 3.x versions to 3.75, nothing! Odin gets my machine back to it's (I THINK) original state.
Badly confused. Knox is fine at 0x0. Don't know how to move forward. I would like to continue to try different ROMS but the same thing keeps on happening. Hope someone can help me. If anyone wants some kind of log output, I can do that (just tell me how and where).
Thanks
Click to expand...
Click to collapse
We have two versions of safestrap and each one works with a different OS.
1.Safestrap 3.71: that works ONLY with jellybean roms. Use it (If your phone says "4.3 MI9, MJ5, or NB4" in your "about phone" in settings) to flash any jellybean rom. Read the title of any rom you're attempting to flash. If it says "4.4.2 KK or Kitkat or NC2" then stay away.
2. Safestrap 3.72/3.75 ([emoji118] this is recommended) that works ONLY with Kitkat roms. Use it (If your phone says "4.4.2 NC2" in your "about phone" in settings) to flash any Kitkat/NC2 rom. Read the title of any rom you're attempting to flash. If it says "4.3 jellybean or JB" then stay away.
K-alz said:
We have two versions of safestrap and each one works with a different OS.
1.Safestrap 3.71: that works ONLY with jellybean roms. Use it (If your phone says "4.3 MI9, MJ5, or NB4" in your "about phone" in settings) to flash any jellybean rom. Read the title of any rom you're attempting to flash. If it says "4.4.2 KK or Kitkat or NC2" then stay away.
2. Safestrap 3.72/3.75 ([emoji118] this is recommended) that works ONLY with Kitkat roms. Use it (If your phone says "4.4.2 NC2" in your "about phone" in settings) to flash any Kitkat/NC2 rom. Read the title of any rom you're attempting to flash. If it says "4.3 jellybean or JB" then stay away.
Click to expand...
Click to collapse
basicaly what he said.. and since you said you did dynamic kat and alliance.. sounds like you are on the nc2 with Kitkat..
So, best bet is going to be make sure you have ss 3.75 and only flash the kitkat roms.. Dynamic kat, Alliance, Tweaked, Firekat, and you should be fine.. just dont try and flash any that are JB
From my Fired-up Note Pro 12.2!
Thank you. A combo of Android version AND baseband at the end?
Are the version numbers I'm looking for, a combination of the Android version (4.4.2) and the end of the Baseband number (NC2)
Basically I tried everything and your suggestions should very very suspiciously like everything I've done But.. I will give it one more shot.
Any possibility of SafeStrap 3.72 would work as opposed to 3.75 not working?
warfenix said:
Sounds like maybe your flashing kit kat over jellybean or the other way around. Make sure if you have going to different android versions you flash the right Odin files each time. And install the right right version of safe strape. Or you get black screens
Click to expand...
Click to collapse
---------- Post added at 10:51 PM ---------- Previous post was at 10:35 PM ----------
Version 4.42. I'll give everything a shot here although, I've tried all of this but maybe I've missed something. Thank you for responding.
warfenix said:
Sounds like maybe your flashing kit kat over jellybean or the other way around. Make sure if you have going to different android versions you flash the right Odin files each time. And install the right right version of safe strape. Or you get black screens
Click to expand...
Click to collapse
bodycode said:
Are the version numbers I'm looking for, a combination of the Android version (4.4.2) and the end of the Baseband number (NC2)
Basically I tried everything and your suggestions should very very suspiciously like everything I've done But.. I will give it one more shot.
Any possibility of SafeStrap 3.72 would work as opposed to 3.75 not working?
---------- Post added at 10:51 PM ---------- Previous post was at 10:35 PM ----------
Version 4.42. I'll give everything a shot here although, I've tried all of this but maybe I've missed something. Thank you for responding.
Click to expand...
Click to collapse
yeah if you are seeing 4.4.2 and nc2 you are on KK.. just make sure you are on 3.75 and all should be ok with flashing..
if for some reason it is borked,, go down to carls thread for odin files and how to odin back to stock nc2 and then start over and you should be fine
From my Fired-up Note Pro 12.2!
NO good. 3.75/stock slot/Alliance ROM fails.
Same ****. Black screen.
David Sanborn said:
I'm an android ROM newbie, but an old computer geek from way back in the 80's, so I do have some kind of understanding. I own an ATT Note 3.
I've experienced only minor problems with the two main ROM flash tools, that is, Safestrap 3.x and Odin 3.x but that's probably my fault and they don't crash. But Safestrap? Oy vay! That works also, but in the final boot, black screen thereafter, after booting from ANY slot, whether it be stock slot of other slots. Thank God for the backup function and Odin.
But I digress. Right in the beginning of my flashing Odyssey, everything worked fine! Flashed Alliance ROM no problem, as well as Dynamic Kat.
Oh yeah. Confused about all those two letter abbreviations, there's no abbreviation key here on the forums?
I tried the other ROMS in the Note 3 Rom sections and stuck wit that, but then, under Safestrap, the machine would reboot to black screen! No matter what I did, wiping, rooting (of course), re-installing different versions of SafeStrap, from early 3.x versions to 3.75, nothing! Odin gets my machine back to it's (I THINK) original state.
Badly confused. Knox is fine at 0x0. Don't know how to move forward. I would like to continue to try different ROMS but the same thing keeps on happening. Hope someone can help me. If anyone wants some kind of log output, I can do that (just tell me how and where).
Thanks
Click to expand...
Click to collapse
NO good. 3.75 fails!
3.75 and Alliance utterly fails into black screen. Safestrap reboot screen does this, but the other button (restore) gets me back to all the other buttons. Stock slot has size of zero partition size after alliance installation.
warfenix said:
Sounds like maybe your flashing kit kat over jellybean or the other way around. Make sure if you have going to different android versions you flash the right Odin files each time. And install the right right version of safe strape. Or you get black screens
Click to expand...
Click to collapse
AFter creating another slot and wipe, system mounting errors.
System mount errors all over the place after creating another slot, and installing Alliance. What's going on here? Something's really screwed up.
e: unable to mount '/system'
e: unable to mount '/systemorig'
over and over again
Can't check permissions after FActory reset. Please boot rom and try again after you reboot into recovery.
David Sanborn said:
3.75 and Alliance utterly fails into black screen. Safestrap reboot screen does this, but the other button (restore) gets me back to all the other buttons. Stock slot has size of zero partition size after alliance installation.
Click to expand...
Click to collapse
David Sanborn said:
3.75 and Alliance utterly fails into black screen. Safestrap reboot screen does this, but the other button (restore) gets me back to all the other buttons. Stock slot has size of zero partition size after alliance installation.
Click to expand...
Click to collapse
I would simply restore back to mj5 and start over. I did this last night simply to reset my phone cause I flash way to much lol. I would give that a try though. Thread is in the general section
How to restore to Mj5?
How do I downgrade to Mj5 from KK4.2?
Thanks
warfenix said:
I would simply restore back to mj5 and start over. I did this last night simply to reset my phone cause I flash way to much lol. I would give that a try though. Thread is in the general section
Click to expand...
Click to collapse
David Sanborn said:
How do I downgrade to Mj5 from KK4.2?
Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2559715
I know what your problem is brother. This same crap happened to me. To a T! For some reason when u wipe system in safesteap, it wipes everything out. EVERYTHING. except data. I learned the hard way,like u. So when u flash roms, don't wipe system, only factory reset. I wipe it 3× every time. Then install your Rom. You will b fine. I haven't had one problem ever since I stopped wiping system. And no random reboots or anything, Roms now flash, and boot as they should. Hope this helps.
David Sanborn said:
How do I downgrade to Mj5 from KK4.2?
Thanks
Click to expand...
Click to collapse
Dude. If you're on NC2 then don't ever do the MJ5. It'll give the same problem. Just Odin the first four files from this thread http://forum.xda-developers.com/showthread.php?t=2838117 then root with towelroot/install busybox (make sure to install it from within the app as well) then install ss 3.72 or 3.75 then start flashing Kitkat roms.
K-alz said:
Dude. If you're on NC2 then don't ever do the MJ5. It'll give the same problem. Just Odin the first four files from this thread http://forum.xda-developers.com/showthread.php?t=2838117 then root with towelroot/install busybox (make sure to install it from within the app as well) then install ss 3.72 or 3.75 then start flashing Kitkat roms.
Click to expand...
Click to collapse
True but I think his problem is wiping system when he installs roms. If he's still not able to boot up right then ya he needs to use Odin and those files to get up and running again.
I just wish it was like the note 2. With unlocked bootloader and real twrp recovery.
zounduser said:
True but I think his problem is wiping system when he installs roms. If he's still not able to boot up right then ya he needs to use Odin and those files to get up and running again.
I just wish it was like the note 2. With unlocked bootloader and real twrp recovery.
Click to expand...
Click to collapse
These four files are as easy as it gets. Literally, put phone into download mode, load files to their respective slots then hit start. That's all. Saves you much bullshiz
K-alz said:
These four files are as easy as it gets. Literally, put phone into download mode, load files to their respective slots then hit start. That's all. Saves you much bullshiz
Click to expand...
Click to collapse
Oh I agree. I've had to do it. I'm saying going forward so it doesn't happen again.
4 files in odin flash, done that 15 times.
I've flashed Odin stock COUNTLESS times! When I go back to flash kitkat ROMS, same **** all over again. Unbelievable. I'm at my wits end. My phone DOES boot with the Odin files. But when flashing anything else with safestrap, black screen again.
K-alz said:
These four files are as easy as it gets. Literally, put phone into download mode, load files to their respective slots then hit start. That's all. Saves you much bullshiz
Click to expand...
Click to collapse
David Sanborn said:
I've flashed Odin stock COUNTLESS times! When I go back to flash kitkat ROMS, same **** all over again. Unbelievable. I'm at my wits end. My phone DOES boot with the Odin files. But when flashing anything else with safestrap, black screen again.
Click to expand...
Click to collapse
You used the files in the thread I gave you a couple of posts back and it didn't work? Man I hope you still have your warranty. Just flash back to stock and take your phone to the AT&T warranty center and make up and issue with your phone and tell them that you can't deal with your phone anymore and get you a new phone. They believe about anything. If that didn't work then head to bestbuy if there is one by you and ask them to reflash the system for you (that's of course after you flash back to stock).
Not a block screen on Odin and no trips.
Did I mention Odin works fine? Knox is not tripped. All is well right after Odin upload to phone in Download mode. It's only when I flash anything that blackscreen curses me again. heh heh.
K-alz said:
You used the files in the thread I gave you a couple of posts back and it didn't work? Man I hope you still have your warranty. Just flash back to stock and take your phone to the AT&T warranty center and make up and issue with your phone and tell them that you can't deal with your phone anymore and get you a new phone. They believe about anything. If that didn't work then head to bestbuy if there is one by you and ask them to reflash the system for you (that's of course after you flash back to stock).
Click to expand...
Click to collapse
Current situation: pretty much complete newbie. I broke my factory OS after rooting it, I think I deleted something Settings needs, so anytime it needs to access settings I get "Unfortunately, Settings has stopped." I factory reset it hoping that would help, but now after loading it gets stuck on a cycling white screen reporting that error (I think it's trying to set up the phone.) The error message prevents me from doing the touch-four-screen-corners trick I've read about and bypass set up. So, stuck on phone setup errors as near as I can tell.
I do have my user apps backed up with TiBu, but couldn't get the recovery zip from TiBu to work. I downloaded CWM but didn't figure it out yet. Also unfortunately I can't get the USB drivers to work (the LGE Android MTP Device won't install), so I think my only way of getting files to my phone now is using the microSD cards.
I'd love some help! I think my factory OS is FUBAR, so I'm not trying to fix that, instead I'd rather just get a cool ROM loaded so I can continue learning with a working device with said cool ROM. I don't fully understand terms that I know I need to like "bootloader" or what CWM / TWRP actually does or how to use them (I need to make a custom recovery ROM?). Or where to get a cool ROM or which to pick, some step by step basics on from some experienced users would be fantastic! Thank you so much!
So you were on stock, rooted, backed up and then messed the ROM? Flash stock ROM again using LG Flash tool (there is a thread in the main section), it should not wipe your data but you'll lose root. Hard to fix if you're not sure about the problem and have no easy access to files. Just make sure you flash the correct version for your model (D405, D410hn, etc), preferably the same version you have now so you won't need a factory reset after flashing...
lfom said:
So you were on stock, rooted, backed up and then messed the ROM? Flash stock ROM again using LG Flash tool (there is a thread in the main section), it should not wipe your data but you'll lose root. Hard to fix if you're not sure about the problem and have no easy access to files. Just make sure you flash the correct version for your model (D405, D410hn, etc), preferably the same version you have now so you won't need a factory reset after flashing...
Click to expand...
Click to collapse
Thank you, this put me in the right direction. I ended up discovering that even though the " LGE Android MTP Device won't install," the flashing process worked with this program via USB anyway. I'm going to lick my wounds a bit before trying to flash a custom ROM. Thank you!
For the rom installation, after unlocking your bootloader and rooting, download the app Flashify from Google Play, then install TWRP or CWM zip file as recovery image. Then, from there, you can install custom ROMs or make backups of your phone, etc. A cool custom ROM I recommend is CyanogenMod, it ports newer versions for older devices. So, you can have Android 6.0.1 in your phone