Well, i'm new in this android/root stuff, but to have something to begin with:
I tried rooting my device(i9505) in 4.3(using that "knox-untouching" way) and, it not only didn't worked (can't use SuperSU), it also installed a custom recovery on my device (triggering everything it could) and know i can't OTA.
So I was thinking, can I just download the OTA and install it over ODIN, then wipe data? Or i have to download 4.3, flash it over, wipe, and than install 4.4.2? (For the record, i can't find my 4.3 ZTO version. Even in sam mobile)
Related
I encountered a strange problem while using Mobile Odin Pro v.3.85 with 4.3 MK6
My phone : Samsung Galaxy S3
I usually use Mobile Odin Pro to flash firmware, i enable inject Root and SU so I wont lose Root and dont increase counter, staying all official.
Let me explain what I did.
I started from 4.1.2 all stock with root and MOP v 3.50 (mobile odin pro v 3.50). Downloaded MK6 firmware from thread in general s3 section and flashed using MOP with ever root: everything okay Im on 4.3. I tryied to open SuperSu and it says there isnt any SU binary with a message saying: "if you just updated to 4.3 install root manually". So i used CF Auto Root for S3 and installed it: once rebooted i couldnt find any SU icon in drawer, had to download latest from Play Store and I was rooted but with counters to "Unofficial" since I flashed with odin.
Now I reflashed 4.3 to avoid getting Unofficial Status: updated MOP to 3.85 latest, it auto downloads flash kernel, flashed 4.3 with everroot (I was already on 4.3 but with unofficial status). All I was hoping to achieve was a 4.3 rooted with MOP 3.85 and all counters to official. For past versions like 4.1.2 it worked!
MOP rebooted S3 and started flashing 4.3: at the end it was in a loop, it continued to flash 4.3 over and over.
Why I got that loop? It was an compatibility issue with 4.3 bootloader and MOP flash kernel?
Have I to downgrade bootloader to ICS first (like I had before)?
I had to go in download mode and flash 4.3 using pc odin, I was so scared! Now im on 4.3 without root but id like to have it with counters set to official.
Thank you, steebro.
loop issue
steebro said:
I encountered a strange problem while using Mobile Odin Pro v.3.85 with 4.3 MK6
My phone : Samsung Galaxy S3
I usually use Mobile Odin Pro to flash firmware, i enable inject Root and SU so I wont lose Root and dont increase counter, staying all official.
Let me explain what I did.
I started from 4.1.2 all stock with root and MOP v 3.50 (mobile odin pro v 3.50). Downloaded MK6 firmware from thread in general s3 section and flashed using MOP with ever root: everything okay Im on 4.3. I tryied to open SuperSu and it says there isnt any SU binary with a message saying: "if you just updated to 4.3 install root manually". So i used CF Auto Root for S3 and installed it: once rebooted i couldnt find any SU icon in drawer, had to download latest from Play Store and I was rooted but with counters to "Unofficial" since I flashed with odin.
Now I reflashed 4.3 to avoid getting Unofficial Status: updated MOP to 3.85 latest, it auto downloads flash kernel, flashed 4.3 with everroot (I was already on 4.3 but with unofficial status). All I was hoping to achieve was a 4.3 rooted with MOP 3.85 and all counters to official. For past versions like 4.1.2 it worked!
MOP rebooted S3 and started flashing 4.3: at the end it was in a loop, it continued to flash 4.3 over and over.
Why I got that loop? It was an compatibility issue with 4.3 bootloader and MOP flash kernel?
Have I to downgrade bootloader to ICS first (like I had before)?
I had to go in download mode and flash 4.3 using pc odin, I was so scared! Now im on 4.3 without root but id like to have it with counters set to official.
Thank you, steebro.
Click to expand...
Click to collapse
Hi! Regarding your boot loop problem, may I suggest that after you flash with MOP, do go into recovery (cwm) and first do a wipe data / factory reset, followed by wipe cache partition. This will give you a fresh rom install. I may be wrong, but that is usually where the problem lies (not doing a wipe data / wipe cache after a fresh (official) ROM install. That's what I have read on countless forums. Hope it helps. Good luck!
Device: AT&T Galaxy S III (SGH-I747) Rooted
ROM: Cyanogenmod 11
I have had my phone rooted and running a custom ROM for a few months now and I have decided that I no longer want to run a custom ROM. I looked up how to go back to stock ROM and everything said to: wipe cache and do a factory reset, download latest stock ROM off of Samsung's firmware website and flash the ROM from Odin. Every time that I did this, it would always fail even if i tried to install from recovery mode. I tried a few more times and it still didn't work. One post said that it was because TWRP, i downloaded and installed the stock recovery (which was the only successful install) and the other installs still didn't work through odin or recovery mode.
Is there anything that I am doing wrong, am I leaving a step out, or is something just flat out wrong with my device?
Assistance would be greatly appreciated!
Okay, So the title pretty much says it all. I am stuck at the Samsung boot logo (not bootanimation) and it only shows for about 1 second then reboots and continues.
This started after I tried to flash a rom and it messed up and I tried to flash via odin. I was on MJ9 and and got a bootloop so I did the odin thing. I've used odin before but it is not working well for me now.
I am able to boot into download mode but TWRP no longer works. I was able to flash via odin and it says success but the phone does not reboot like it should.
I have purchased a galaxy nexus on the cheap to hold me over until the nexus 6 is out but if I can fix my note, I would like to.
I know there were other threads about this same issue but it seems that they are all on a different version of the note, or on a s3 or something. Not to mention, I don't see anything that I could try without asking for some help on here. Can someone maybe point me in the direction of the factory firmware (preferably a rootable or already rooted version) that I can flash that will play well with my note.
Thanks guys!!!
amberkalvin said:
Okay, So the title pretty much says it all. I am stuck at the Samsung boot logo (not bootanimation) and it only shows for about 1 second then reboots and continues.
This started after I tried to flash a rom and it messed up and I tried to flash via odin. I was on MJ9 and and got a bootloop so I did the odin thing. I've used odin before but it is not working well for me now.
I am able to boot into download mode but TWRP no longer works. I was able to flash via odin and it says success but the phone does not reboot like it should.
Click to expand...
Click to collapse
Before you tried to flash a custom ROM and things went wonky...were you on Verizon's factory stock 4.3 MJ9 firmware, or on Beanstown106’s modified 4.3 MJ9 with TWRP installed?
Does the phone still boot into stock recovery? If so, you may be able to fix the phone by doing a factory reset.
amberkalvin said:
Can someone maybe point me in the direction of the factory firmware (preferably a rootable or already rooted version) that I can flash that will play well with my note.
Click to expand...
Click to collapse
If you were on Verizon's factory stock 4.3 MJ9, then you won't be able to Odin flash back to 4.1.2 or any earlier Android version because the bootloader has been locked down tight on 4.3 (and 4.4.2) with no current do it yourself method to unlock for those newer versions. You would want to restore the phone back to factory stock 4.3 though, if that's what version you were on before your phone got messed up. You can root the phone on 4.3 with saferoot, then use safestrap recovery to flash some custom Touchwiz ROM's.
If you were on the 4.1.2 based bootloader, (but running Beanstown106’s MJ9 firmware and TWRP), then you would want to restore your phone back to factory stock 4.1.2 and then root and unlock the bootloader again with CASUAL. This would give you the most flexibility with flashing custom kernels, ROM's, etc...
Check out Section 1b in Droidstyle's restore guide at this link: http://forum.xda-developers.com/showthread.php?p=34891181. The guide has download links for the files you'll need to restore the phone back to the correct build version.
I upgraded to LP by Odin flash G900TUVU1DOB1 and then installed [ROM]ViSiON-X US TMO[Android L 5.0][G900TUVU1DOB1] Phone is working fine.
I'd like to revert to my former 4.4.2 "Xtreme Dynamic Kat 1.1" It is a Safestrap AT&T rom that ran on 900T but is flashed without Safestrap and TWRP on 900T.
Would it be ok to just restore my 4.4.2 TWRP backup? Do I have to Odin back to 4.4.2 Firmware first? I don't want to do that and lose Internal Storage or the ability to easily go back and forth between roms .
My first thought is no. I can't restore a 4.4.2 rom over the LP bootloader but I really don't know.
Hi, I saw about the quad rooter issue, and today I checked the ota update. (I never had an ota update because I always been rooted, s3, s5 and g5)
But now it purpose the 10d update. (450mo)
I'm 10c h850 rooted.
Should I make this update?
Will I lose root? (Rooted via twrp super su)
If I have to re install everything (apps, datas, root), maybe should I wait for 7 nougat don't you think?
Thanks.
trotirider said:
Hi, I saw about the quad rooter issue, and today I checked the ota update. (I never had an ota update because I always been rooted, s3, s5 and g5)
But now it purpose the 10d update. (450mo)
I'm 10c h850 rooted.
Should I make this update?
Will I lose root? (Rooted via twrp super su)
If I have to re install everything (apps, datas, root), maybe should I wait for 7 nougat don't you think?
Thanks.
Click to expand...
Click to collapse
It won't install the update anyway with twrp installed. It'll just fail and reboot. Wait until your ROM devs rebase your ROM on the new base.
Thanks, it was stock rom. But yeah I don't think it's worth if I make a fresh install with android 7.
As you said I'm affraid about the bootloop issue.
trotirider said:
Thanks, it was stock rom. But yeah I don't think it's worth if I make a fresh install with android 7.
As you said I'm affraid about the bootloop issue.
Click to expand...
Click to collapse
Not bootloop, just because you have custom recovery installed the stock update process will not complete even on stock Rom, you'd need to wait for a flashable version of the update or you'd have to flash stock recovery back to your device first.
I just used LGUP without any issues. Pretty painless.
Then flashed TWRP again, and flashed my ROM of choice.
The only tricky part was quickly getting into TWRP after you flash TWRP. It reboots and if you're not quick enough, TWRP will be overridden by the stock recovery. Then you just need to repeat (flash TWRP again, get into TWRP and flash ROM).