So this is probably far fetched and impossible but I got stuck flashing the official firmware from beanstown for a 4.3 rom. I couldn't get the rom to function properly and so i restored my backup via twrp. I unchecked the boot and modem options because i didn't think they were necessary. Now I had a soft brick and eventually led me back to root66 4.1.1. If i were to flash the 4.1.2 VRAMC3 would i be able to reroot and unlock my bootloader via casual, or is it stuck with a 4.3 bootloader?
Note: when i try to boot into recovery, It's the android one and I can't seem to use casual on this rom to install a new bootloader.
yeah u can go back to 4.1.1 or 4.1.2 and reunlock and root your phone as long as u didnt take the official 4.3 ota.
Related
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)
i have this ROM
http://forum.xda-developers.com/showthread.php?p=51796138
i got Ota 4.4.2 to my phone with this ROM
should i upgrade? i am s-on.
is their any problem of that?
will i lose root and twpr recovery?
rowihel2012 said:
i have this ROM
http://forum.xda-developers.com/showthread.php?p=51796138
i got Ota 4.4.2 to my phone with this ROM
should i upgrade? i am s-on.
is their any problem of that?
will i lose root and twpr recovery?
Click to expand...
Click to collapse
You will likely have it fail. OTAs frequently check the /system directory to make sure the expected files are there prior to update. OTAs will likely not flash on a custom rocovery as the firmware portion will not flash from that. Your best bet.. S-off now.... flash stock... take OTA. Then flash TWRP back and flash your custom rom of choice. That will allow you to upgrade to the latest firmware and still run a jelly bean rom. On that custom rom you will still get a nag to update the OS but you can find ways to disable that until the developer updates his rom.
IF you simply wait for him to update his rom, you will still need to manually update the fimware in RUU.
I have a SGH-i527 that got the 4.4.2 OTA update last night. I'm not sure what I did, but I think I tried to flash the 4.2.2 via Odin when I was encountering problems with Kit Kat. Now when trying to boot, I am stuck on the "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." screen.
I have tried to get Kies to go through emergency recovery but the phone never shows up there. And obviously, trying the flash the 4.2.2 firmware in odin will not work. So I am stuck. Any thoughts?
If you did flash the JB ROM after the KitKat update, you will have to flash the KitKat firmware since you cannot downgrade the bootloader and you have probably voided the warranty. Flash the KitKat update for the specific model and DO NOT try to root, flash custom recovery or downgrade to Jellybean since it will trip the Knox boot loader and you will have a brick. Hope this helps
To my understanding, there is not a KK stock rom that I can flash (at least for the i527). And since I can't flash back to 4.2.2, it looks like I'm stuck.
Why flashing 4.2.2 by Odin did not change your situation? Maybe try to flash another ROM?
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.
So I want to put carbon rom on my galaxy s4. (SGH-i337 running rooted 4.4.2)
The current rom I have on it has a locked boot loader so I cannot get TWRP or CWM on it.
I have tried rolling back to 4.2.2 but it will not let me.
Would I be able to load a custom rom or even 4.2.2 with its unlocked bootloader if I load all of the files into Odin and setup all the partitions I need in PIT like you need to do when you brick your device.
This is just a theory but if it should work please let me know.
Bump
Bump