Database Info

If you want to update, but you're rooted/custom recovery/custom kernel...

...and you DON'T want to perform a Factory Reset.
Figured this out while returning to the stock kernel after poor performance on a custom one...
THIS WILL LIKELY NOT WORK IF YOU ARE ON A CUSTOM ROM
If you are still on the Stock ROM you can do this to get new updates from your carrier (I have only tried AT&T):
1. Unfreeze AT&T updater (if you have it frozen)
2. Use ODIN to return to stock WITHOUT performing a factory reset. AdamOutler has a thread HERE with the stock firmware download in the Android Development section
3. Boot up and check for updates
4. After you have updated, root it, apply your custom recovery, and/or kernel again
5. Hit the THANKS button below
All your apps and settings will remain. You may have to re-sign-in to some, but you should be good to go.

joeybear23 said:
Figured this out while returning to the stock kernel after poor performance on a custom one...
THIS WILL LIKELY NOT WORK IF YOU ARE ON A CUSTOM ROM
If you are still on the Stock ROM you can do this to get new updates from your carrier (I have only tried AT&T):
1. Unfreeze AT&T updater (if you have it frozen)
2. Use ODIN to return to stock WITHOUT performing a factory reset. AdamOutler has a thread with the stock firmware download in the Android Development section
3. Boot up and check for updates
4. After you have updated, root it, apply your custom recovery, and/or kernel again
5. Hit the THANKS button below
All your apps and settings will remain. You may have to re-sign-in to some, but you should be good to go.
Click to expand...
Click to collapse
Where can you find out when carrier updates are released?

This will always work no matter what Rom your on...even if your on aosp...Odin is created so that you can return to stock. Once your on stock you can receive any update available...
Sent from my HTC PH39100 using Tapatalk 2

mg2195 said:
This will always work no matter what Rom your on...even if your on aosp...Odin is created so that you can return to stock. Once your on stock you can receive any update available...
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
Yes, however if you are on a custom ROM you must perform a factory reset prior to or after ODIN, which will make you lose your apps, settings, etc.
If you are still on the stock ROM, you don't have to factory reset... which is kind of the point for people who want the update but don't want to factory reset.

blyndfyre said:
Where can you find out when carrier updates are released?
Click to expand...
Click to collapse
Just follow the forum. When an update is released, I guarantee you there will be no less than 50 new threads in here.

joeybear23 said:
Just follow the forum. When an update is released, I guarantee you there will be no less than 50 new threads in here.
Click to expand...
Click to collapse
Assumed as much, but wanted to be sure. I'm on this forum exclusively and hourly anyways lol. So much reading to be done!
Will updates be specific to carrier? For instance I'm on Telus in Canada so I'll need to wait for my specific update, download and flash via ODIN? (Since I'm 'custom' status and won't be able to OTA. Root only, stock recovery, kernel and ROM.)
And thanks btw!

blyndfyre said:
Assumed as much, but wanted to be sure. I'm on this forum exclusively and hourly anyways lol. So much reading to be done!
Will updates be specific to carrier? For instance I'm on Telus in Canada so I'll need to wait for my specific update, download and flash via ODIN? (Since I'm 'custom' status and won't be able to OTA. Root only, stock recovery, kernel and ROM.)
And thanks btw!
Click to expand...
Click to collapse
Unfortunately I can't speak for anything other than AT&T since I don't have the ability to test any other carrier's devices... however the update will likely be pushed by your carrier with their proprietary update mechanism.
If you want to use something other than OTA, you can wait for a flashable zip when it comes available, which will likely be pretty quick after initial release.

joeybear23 said:
Unfortunately I can't speak for anything other than AT&T since I don't have the ability to test any other carrier's devices... however the update will likely be pushed by your carrier with their proprietary update mechanism.
If you want to use something other than OTA, you can wait for a flashable zip when it comes available, which will likely be pretty quick after initial release.
Click to expand...
Click to collapse
Thanks man. One last question, would this flashable zip flash via ODIN or Custom Recovery (TWRP/CWM) or either method?

blyndfyre said:
Thanks man. One last question, would this flashable zip flash via ODIN or Custom Recovery (TWRP/CWM) or either method?
Click to expand...
Click to collapse
Depends on the Developer... most likely a flashable zip for TWRP/CWM

joeybear23 said:
Depends on the Developer... most likely a flashable zip for TWRP/CWM
Click to expand...
Click to collapse
Maybe a tad off topic, but if one were to follow the directions in the OP, wouldn't it still not work? You'd still have the custom unlock button with stock firmware, which would prevent it to look for any OTA update.
Maybe I'm wrong?

MattMJB0188 said:
Maybe a tad off topic, but if one were to follow the directions in the OP, wouldn't it still not work? You'd still have the custom unlock button with stock firmware, which would prevent it to look for any OTA update.
Maybe I'm wrong?
Click to expand...
Click to collapse
I thought the same thing, until I tried it and the OTA came over just fine. That's one of the reason I started this thread, so others would know they can do it.
The ODIN gives you back the stock recovery so you can pull the OTA.

joeybear23 said:
I thought the same thing, until I tried it and the OTA came over just fine. That's one of the reason I started this thread, so others would know they can do it.
The ODIN gives you back the stock recovery so you can pull the OTA.
Click to expand...
Click to collapse
Do you know if doing so removes the custom unlock icon?

If I'm running custom rom s and kernels would the att update even be beneficial?

MattMJB0188 said:
Do you know if doing so removes the custom unlock icon?
Click to expand...
Click to collapse
It will not.
Sent from my SAMSUNG-SGH-I337 using xda premium

Bigtjmc said:
If I'm running custom rom s and kernels would the att update even be beneficial?
Click to expand...
Click to collapse
ROMs? No
Kernels only? Yes imho
Sent from my SAMSUNG-SGH-I337 using xda premium

joeybear23 said:
It will not.
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
Ok, how about if one follows your method and then updates via AT&T OTA. Would it then get rid of the custom unlock status? How does one remove this if they're not rooted with 100% stock? I don't get why it still shows it.

MattMJB0188 said:
Ok, how about if one follows your method and then updates via AT&T OTA. Would it then get rid of the custom unlock status? How does one remove this if they're not rooted with 100% stock? I don't get why it still shows it.
Click to expand...
Click to collapse
I am not 100% certain what all gets looked at when the firmware runs its "custom status" check. I do know that there are a wide variety of fixes/solutions that work for some and not for others... I have the custom icon, but it doesn't bother me, so I haven't done too much research into it.

joeybear23 said:
I am not 100% certain what all gets looked at when the firmware runs its "custom status" check. I do know that there are a wide variety of fixes/solutions that work for some and not for others... I have the custom icon, but it doesn't bother me, so I haven't done too much research into it.
Click to expand...
Click to collapse
+1
Doesn't bother me one bit, although my bootloader is unlocked so I don't get the unlock icon boot screen.

Maybe a stupid question, but could one flash SGH-I337 UCUAMDL firmware instead since its the latest, or would it better to flash the original firmware then update?

MattMJB0188 said:
Maybe a stupid question, but could one flash SGH-I337 UCUAMDL firmware instead since its the latest, or would it better to flash the original firmware then update?
Click to expand...
Click to collapse
Not a stupid question at all. Yes you can do that. When I started this thread there was not one available.
Sent from my SAMSUNG-SGH-I337 using xda premium

[Q] Help returning to stock recovery

Hi Guys,
I know this may be frustrating for some of you, but as a complete beginner in using Android, I was wondering whether someone could help me out here. I have tried searching various forums, but my knowledge of androids is limited. I used the tutorial from Rootwiki to successfully unlock my bootloader, install TWRP recovery and root my phone
Does this mean I am not using a stock rom?
Now I sort of regret deciding to do this and would like to return to stock so that I can get any OTA updates without further tampering with my phone. Unfortunately while following the above tutorial, I only made a backup after TWRP was installed and not before, so I need help in going back please.
I can see that there are a few people in my position, so I'm sure others will benefit from this as well.
My software details are:
Android version - 4.2.2.
Software number - 1.33.206.1
HTC SDK API level - 5.41
Network - o2 uk
Can I use any stock recovery file or does it have to be specific to the above?
Can you please provide a step by step guide with a list of files that I will need to download?
or can I simply just factory reset my phone, and everything goes back to normal? I don't mind having to re install apps etc?
Thank you all very much

i have a HTC One mini 4.3 and i am in the exact same situation. i like to get stock recovery but those ive tried hasent been working.

If you didint flash a rom after you installed your recovery, the back up you made is then of stock os
Maybe if you take the ota, it will cancel out ur root and five you stock recovery back, i havent browsed these forums.. Try searching for a RUU and stock recovery, the phone is fairly new, so can take time for someone to put something together
Sent from my HTC6500LVW using xda app-developers app

the stock recovery must match HBOOT /Main-Version....
wich HBOOT do you have?

epolus said:
the stock recovery must match HBOOT /Main-Version....
wich HBOOT do you have?
Click to expand...
Click to collapse
Thank you for your replies, my HBOOT is 2.19.0000

Ok guys, I got the notification for the OTA update today, I have downloaded it but haven't installed it. From a different thread, I found a link for a stock recovery which is about 9.5mb from androidfile host (/?fid=23252070760975668)
can I just flash this recovery and proceed with the update? or will there be compatibility issues with the version I have above?
Thanks

Anyone?
I am getting desperate to the point that I might actually pay HTC to repair it for me

Did u have any look for I'm looking for the same but have an unrooted mini
Sent from my HTC One mini using Tapatalk

nbbcj said:
Did u have any look for I'm looking for the same but have an unrooted mini
Sent from my HTC One mini using Tapatalk
Click to expand...
Click to collapse
not yet, but MirageBlader has been quite helpful and has said the following in a private message to me, which I have yet to try:
"Very easy mate, open your ota and flash the stock recovery from the ota. You can only install it with stock Rom, stock boot and stock recovery. Your bootloader musst be locked and your phone unrooted. s-off is not needed if you already got the ota"

drewkp said:
not yet, but MirageBlader has been quite helpful and has said the following in a private message to me, which I have yet to try:
"Very easy mate, open your ota and flash the stock recovery from the ota. You can only install it with stock Rom, stock boot and stock recovery. Your bootloader musst be locked and your phone unrooted. s-off is not needed if you already got the ota"
Click to expand...
Click to collapse
I'd be very interested to know the results of your attempt to go back to "stock".
Can I ask if you are doing this just to get the 4.3 update? Also, do you plan to root and customise your ROM after the update, or leave it stock?
Thanks, and good luck....
---------- Post added at 01:14 AM ---------- Previous post was at 01:10 AM ----------
nbbcj said:
Did u have any look for I'm looking for the same but have an unrooted mini
Sent from my HTC One mini using Tapatalk
Click to expand...
Click to collapse
If your phone isn't rooted, what exactly is the issue? Do you have a custom recovery installed, and is your bootloader unlocked? If you are looking to upgrade, did you get the OTA download on your phone?

Hi nelvinchi I am trying to get back to android ver 4.2, I have a stock mini it's not been rooted or mod'd in any way. Just had the 4.3 ota that was update automatically just woke up and my phone had updated looking at settings it was set to auto update and install when on charge Grr dam phone so many probs with this ota
Sent from my HTC One mini using Tapatalk

nelvinchi said:
I'd be very interested to know the results of your attempt to go back to "stock".
Can I ask if you are doing this just to get the 4.3 update? Also, do you plan to root and customise your ROM after the update, or leave it stock?
Thanks, and good luck....
---------- Post added at 01:14 AM ---------- Previous post was at 01:10 AM ----------
If your phone isn't rooted, what exactly is the issue? Do you have a custom recovery installed, and is your bootloader unlocked? If you are looking to upgrade, did you get the OTA download on your phone?
Click to expand...
Click to collapse
I haven't got round to trying this out yet, will update this thread once I do, just quite busy this month and can't afford to mess up my phone. Yep, just doing it for the update, I only rooted my phone in the first place to get rid of bloatware, which i realised is a lot more complicated than just rooting, and all the other benefits of rooting don't really appeal to me, or are too much hassle for a beginner such as myself.
Just need to figure out how to unroot and relock my bootloader before I can go ahead with this :s

Hey nelvinchi. You seem to be knowledgeable enough on the matter and have been looking for help with my device. I posted a separate thread yesterday. If you have time/think you can help, could you take a look? Would much appreciate it.

drewkp said:
I haven't got round to trying this out yet, will update this thread once I do, just quite busy this month and can't afford to mess up my phone. Yep, just doing it for the update, I only rooted my phone in the first place to get rid of bloatware, which i realised is a lot more complicated than just rooting, and all the other benefits of rooting don't really appeal to me, or are too much hassle for a beginner such as myself.
Just need to figure out how to unroot and relock my bootloader before I can go ahead with this :s
Click to expand...
Click to collapse
If you have SuperSU installed on your phone, the app has a settings option called "Full unroot" - this will get rid of root. Relocking your bootloader - there are various methods, you could try HTCDEV site (probably how you unlocked originally), or the revone option which will lock the bootloader and remove the "tampered" label. Try a search, but if you are unsure, jusk ask!

2664963463
Got everything sorted with the great help of Nelvin. I had previously gone to the twrp support IRC and after answering a few questions, they just stopped talking... Glad there are people out there still willing to help! He spent a good hour or so with me making sure everything was working.

nelvinchi said:
If you have SuperSU installed on your phone, the app has a settings option called "Full unroot" - this will get rid of root. Relocking your bootloader - there are various methods, you could try HTCDEV site (probably how you unlocked originally), or the revone option which will lock the bootloader and remove the "tampered" label. Try a search, but if you are unsure, jusk ask!
Click to expand...
Click to collapse
Thanks for your reply nelvinchi, can I just confirm whether the SuperSU app you're talking about it the one by Chainfire in the marketplace? And is it just a matter of installing this from the marketplace to unroot my device, or is it a bit more complicated than that?
I'll do some research on relocking my bootloader with revone.
Also do you reckon the above method of getting the stock recovery from my update file will work?
Thanks for your help

drewkp said:
Thanks for your reply nelvinchi, can I just confirm whether the SuperSU app you're talking about it the one by Chainfire in the marketplace? And is it just a matter of installing this from the marketplace to unroot my device, or is it a bit more complicated than that?
I'll do some research on relocking my bootloader with revone.
Also do you reckon the above method of getting the stock recovery from my update file will work?
Thanks for your help
Click to expand...
Click to collapse
If you are rooted then you more than likely have supersu already installed. Check your app drawer.I rooted using HTC DEV and supersu was flashed to the phone with twrp as part of the process

drewkp said:
Thanks for your reply nelvinchi, can I just confirm whether the SuperSU app you're talking about it the one by Chainfire in the marketplace? And is it just a matter of installing this from the marketplace to unroot my device, or is it a bit more complicated than that?
I'll do some research on relocking my bootloader with revone.
Also do you reckon the above method of getting the stock recovery from my update file will work?
Thanks for your help
Click to expand...
Click to collapse
Can I make a suggestion? Given where you are with your phone currently, It would be much simpler, and virtually risk free, to flash tr1gg3r's Stock Sense 5.5 4.3 rooted deodexed rom from the One Mini Android Development forum.
You will get the 4.3 update, and have a fast and very stable ROM. All future updates will be incorporated into a newer ROM version.
Returning to "stock" carries FAR more risk - and you'll never have true stock because it isn't possible. Soon as the bootloader is unlocked, your phone is tampered, and no tool or utility can change that (other than cosmetically!)
It's your choice obviously, but if I was you, I'd stay rooted and enjoy the benefits it brings!
If you still want to try to go back to stock, I'll help..... But I've now helped three members get out of a soft brick after they attempted to go stock.......

The [GT-I9505][Leaked firmware] I9505XXUFNA1 (Android 4.4) - Open Europe (OXA) [10-01

The gt-i9005 has a leaked fireware of 4.4. I hope that we get in the next two or there months!
http://forum.xda-developers.com/showthread.php?t=2465713
Sent from my SGH-I337 using xda premium

killer5000 said:
The gt-i9005 has a leaked fireware of 4.4. I hope that we get in the next two or there months!
http://forum.xda-developers.com/showthread.php?t=2465713
Sent from my SGH-I337 using xda premium
Click to expand...
Click to collapse
I just downloaded
Has anyone tried unzipping it and rezipping without the bootloader, etc and tried flashing it rather than using odin and replacing the bootloader everything? I am working on that as we speak, just wondering if someone has done it already and what their experience was as far as what worked. I imagine there will be some issues with wifi or what not.

neo4uo said:
I just downloaded
Has anyone tried unzipping it and rezipping without the bootloader, etc and tried flashing it rather than using odin and replacing the bootloader everything? I am working on that as we speak, just wondering if someone has done it already and what their experience was as far as what worked. I imagine there will be some issues with wifi or what not.
Click to expand...
Click to collapse
If you're on i337 you cannot flash it through Odin, not authorized... I have been tinkering with putting together a zip to flash via recovery...but I'm a novice and couldn't get past the boot animation with sound...

ZPaul2Fresh8 said:
If you're on i337 you cannot flash it through Odin, not authorized... I have been tinkering with putting together a zip to flash via recovery...but I'm a novice and couldn't get past the boot animation with sound...
Click to expand...
Click to collapse
I was working on it the other day and just got to busy. There is a rom already in the I9505 thread...
http://forum.xda-developers.com/showthread.php?t=2555569
The only catch is from what I have read that the Wifi will not work unless you odin the leak first. For some reason it seems that you have to have the new leaked bootloader. I have talked to a couple of the people that made a zip flash keeping the bootloader we are on, but no wifi. I stopped working on making a zip after I found that out. I have thought about using odin to flash the leak then flashing the Rom from the link above, but am not sure if I would be able to go back to the roms that I am running on the old bootloader. I am just going to wait until some people that knows what they are are doing picks the leak apart more. Anywho if you are interested goto that thread above and do some reading. I personally am just going to stay away until we know more about the new bootloader. I know that the leak can be rooted though because chainfire released an update specifically for the 4.4.2 leak.

neo4uo said:
I was working on it the other day and just got to busy. There is a rom already in the I9505 thread...
http://forum.xda-developers.com/showthread.php?t=2555569
The only catch is from what I have read that the Wifi will not work unless you odin the leak first. For some reason it seems that you have to have the new leaked bootloader. I have talked to a couple of the people that made a zip flash keeping the bootloader we are on, but no wifi. I stopped working on making a zip after I found that out. I have thought about using odin to flash the leak then flashing the Rom from the link above, but am not sure if I would be able to go back to the roms that I am running on the old bootloader. I am just going to wait until some people that knows what they are are doing picks the leak apart more. Anywho if you are interested goto that thread above and do some reading. I personally am just going to stay away until we know more about the new bootloader. I know that the leak can be rooted though because chainfire released an update specifically for the 4.4.2 leak.
Click to expand...
Click to collapse
I did try flashing with Odin a day ago, I'm assuming since the Download Mode has "No authorization" it's due to the locked bootloader we have. About 10% into the flash it fails with an authorization error... I'm going to look into that thread to see if I can learn more...trial and error is a great learning tool for me
Downloading now to try it out. The updated link for that referenced rom is http://forum.xda-developers.com/showthread.php?t=2372286...

ZPaul2Fresh8 said:
I did try flashing with Odin a day ago, I'm assuming since the Download Mode has "No authorization" it's due to the locked bootloader we have. About 10% into the flash it fails with an authorization error... I'm going to look into that thread to see if I can learn more...trial and error is a great learning tool for me
Downloading now to try it out. The updated link for that referenced rom is http://forum.xda-developers.com/showthread.php?t=2372286...
Click to expand...
Click to collapse
Let us know, or pm and let me know how it goes

known bugs
Hi so far after using for the last two days I notice when holding the home button for open apps what ever you press will always open the last app used and not what you have selected!
Andy the native Samsung e mail app continuously tells me about e mails I've viewed
That is all so far!

what kernel are you using?

neo4uo said:
Let us know, or pm and let me know how it goes
Click to expand...
Click to collapse
Well after hours of farting around with their build and mine, I pretty much lost interest with the ROM now. Their build definitely has WiFi broken. I'm not sure if it's kernel related or not.
I think I'm with you on waiting for this to improve before using. Besides CM11 with Google Experience Launcher is looking and feeling great this past month...

Here is a like to Echoe13_4.4.2Deodex_12JAN2013.zip it works but you need to loki patch it and wifi don't work.
http://www.androidfilehost.com/?fid=23311191640113279

hello my friends somebody have one solution for the problem of wifi in rom stock o custom deodex of echoe in 4.4.2... And please can explainme what is the loky patch...? tks for your help and sorry for my english..!

Loki only has to be flashed on the At&t variant of the S4 after installing a zip that was not an At&t rom. The WiFi issue I believe is from not updating the bootloader via OTA and possibly kernel tweaks as well but it will get there. We have great devs for this device.
Sent from my SGH-I337 using XDA Premium HD app

scalamusical said:
hello my friends somebody have one solution for the problem of wifi in rom stock o custom deodex of echoe in 4.4.2... And please can explainme what is the loky patch...? tks for your help and sorry for my english..!
Click to expand...
Click to collapse
You need a kernel made from the 4.4.2 source code which has not been released yet for the wifi.
For loki patch on att, download loki-doki, put it on your SD, go to recovery, flash rom,flash loki doki. If you are using a rom made for att chances are the kernel will already be patched.

C13v3r0n3 said:
You need a kernel made from the 4.4.2 source code which has not been released yet for the wifi.
For loki patch on att, download loki-doki, put it on your SD, go to recovery, flash rom,flash loki doki. If you are using a rom made for att chances are the kernel will already be patched.
Click to expand...
Click to collapse
what kernel were you guys using on the echoe roms? I couldn't get past the boot screen and it hung using the i337m Canadian variant which should be the same as their TMO version minus the leaked bootloader.

There is a new NA5 leak out. I am in the I337 and have tried the NA1 leak Roms Indies Omega and Echoe and I always hang up on the boot menu. Guess we will have to wait for the official and the Kernel info for it to work for us.

rfb813 said:
There is a new NA5 leak out. I am in the I337 and have tried the NA1 leak Roms Indies Omega and Echoe and I always hang up on the boot menu. Guess we will have to wait for the official and the Kernel info for it to work for us.
Click to expand...
Click to collapse
You give me a few hrs, at work right now. I will have this running for att the NA5 base...so stay tuned....

TheAxman said:
You give me a few hrs, at work right now. I will have this running for att the NA5 base...so stay tuned....
Click to expand...
Click to collapse
I didn't know there was a nlthread on this on my native device. I Have been posting on the Tmobile thread since the leak first came out.
I also unpacked both Leaks and repacked only their respective boot, system and cache files and successfully flashed via Odin. the cool part was that I didn't lose root and only needed to add the new supersu. I had a titanium backup zip which I also flashed.
the problems are as follows
1. No WiFi. attempting to flash KT kernel bricked it. had to start all over
2. Security settings caused a FC. so couldn't enable installation from unknown sources.
3. Restoring user apps using Titanium backup (after freezing all Knox apps) worked. but adding any system apps caused a bad series of forced closures
so unless u have got an unlimited data plan, this is just something to play around with for now it would seem

AFAIK I337M devices share the same hardware with I9505 ones; so can I flash I9505XXUFNA5 onto my I337m?

guerouig said:
AFAIK I337M devices share the same hardware with I9505 ones; so can I flash I9505XXUFNA5 onto my I337m?
Click to expand...
Click to collapse
The bootloader would block odin from accepting the full package. The best u can do is pick n choose parts to flas like i did. And you'll end up with a similar scenario
But you could use this modified version and search for Magical unicorn kernel and see
http://forum.xda-developers.com/showthread.php?t=2608134

@gangsta101: so what bits did you chose to flash? is AP and CP and exclude BL and CSC for instance?

Questions about flashing 4.4 ROM. Coming from 4.1 Please help!

So like the title says I have been out of the ROM game for a little bit. Every couple of months I check in and see whats new and flash something else.
I was on the Jelly Beans ROM (Build 16 I think) and Android 4.1. I did some searching last night as was going to try flashing Gummy ROM…bad idea. I am guessing I needed something prior to jumping up to a 4.4 base. I booted to recovery and wiped everything and tried to flash with no luck. So the phone would not boot and I could only get into recovery and download mode. I did not have my micro SD adapter in order to get jelly beans back on it to flash so I ended up having to use odin to flash a stock rooted 4.1 image. Finally got everything back up and running but I still want to try some of the 4.4 ROMs. So what exactly do I need first in order to flash one? (Modem maybe)…if you know for sure why that happened and what I need to do please let me know. Thanks!
My Current "About Phone" Info...
Android Version - 4.1.2
Baseband version - I535VRBMB1
Jelly Beans - Build 20
P.S. I have tried doing the research and nothing I have found has been clear but one thing I came across is the official 4.3 update was bad news and broke the root methods? So should I stay away from 4.3 ROMs and is the old root method blocked in 4.4 as well or is that a different case since it wasn't actually released for our phone. If that makes sense lol

aholeinthewor1d said:
So like the title says I have been out of the ROM game for a little bit. Every couple of months I check in and see whats new and flash something else.
I was on the Jelly Beans ROM (Build 16 I think) and Android 4.1. I did some searching last night as was going to try flashing Gummy ROM…bad idea. I am guessing I needed something prior to jumping up to a 4.4 base. I booted to recovery and wiped everything and tried to flash with no luck. So the phone would not boot and I could only get into recovery and download mode. I did not have my micro SD adapter in order to get jelly beans back on it to flash so I ended up having to use odin to flash a stock rooted 4.1 image. Finally got everything back up and running but I still want to try some of the 4.4 ROMs. So what exactly do I need first in order to flash one? (Modem maybe)…if you know for sure why that happened and what I need to do please let me know. Thanks!
P.S. I have tried doing the research and nothing I have found has been clear but one thing I came across is the official 4.3 update was bad news and broke the root methods? So should I stay away from 4.3 ROMs and is the old root method blocked in 4.4 as well or is that a different case since it wasn't actually released for our phone. If that makes sense lol
Click to expand...
Click to collapse
Can't tell you exactly why that happened, but it shouldve worked.
You're right though, stay away from the stock Ota 4.3 update. I'm happy you read first because so many people don't. My guess is your firmware was a little too old. Try to flash the mf1 firmware aio and then try gummy.
To be clear, you can still use any custom rom, even the 4.3 ones, just stay away from the stock rom or anything having to do with 4.3 ML1 firmware
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
Can't tell you exactly why that happened, but it shouldve worked.
You're right though, stay away from the stock Ota 4.3 update. I'm happy you read first because so many people don't. My guess is your firmware was a little too old. Try to flash the mf1 firmware aio and then try gummy.
To be clear, you can still use any custom rom, even the 4.3 ones, just stay away from the stock rom or anything having to do with 4.3 ML1 firmware
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the quick reply. What do you mean try to flash the MF1 firmware...does that mean a 4.2 ROM?
I think I saw the new jellyBeans/alliance ROM was 4.3...or maybe it was something else..either way it would be ok to flash the 4.3 ROM? and if I wanted I could go back to a 4.1 Rom then..

aholeinthewor1d said:
Thanks for the quick reply. What do you mean try to flash the MF1 firmware...does that mean a 4.2 ROM?
I think I saw the new jellyBeans/alliance ROM was 4.3...or maybe it was something else..either way it would be ok to flash the 4.3 ROM? and if I wanted I could go back to a 4.1 Rom then..
Click to expand...
Click to collapse
Yes you can interchange between both of them if you want to.
So go here, read all of the details, and just follow his recommendation:
http://forum.xda-developers.com/showthread.php?t=1788313
Also don't double post, modify your post in the development section and put "wrong section, mod please delete".
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
Yes you can interchange between both of them if you want to.
So go here, read all of the details, and just follow his recommendation:
http://forum.xda-developers.com/showthread.php?t=1788313
Also don't double post, modify your post in the development section and put "wrong section, mod please delete".
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
The reason I have so confused is cause of the link you sent. I read that before and it says..
"You should NOT flash the I535VRUCML1 firmware (or any subsequent releases for that matter). You will brick. This is what vzw/samsung did on the first OTA for the Galaxy S4. They changed the keys they sign the firmware with. This prevents us from 'mis-matching' our firmware like we've been doing all along. We've been leaving aboot (VRUAME6, the african-canadian sock-monkey leaked bootloader) alone and updating everything else. Since they're signing with different keys now, doing this will brick your device. If you update the ENTIRE bootchain (including aboot) you shouldn't brick, but will be stuck with a locked bootloader and any attempt to downgrade (via dd, etc) will brick you as well."
Like i said I have been out for a while and lost track of what firmwares came out and the order of them and which I need to be on to flash a 4.4 ROM. Someone else told me the only reason my first flash failed was because my recovery was older
***EDIT****
Ignore that entire thing I just realized you said to stay away from ML1 and that MF1 is ok..opps

aholeinthewor1d said:
The reason I have so confused is cause of the link you sent. I read that before and it says..
"You should NOT flash the I535VRUCML1 firmware (or any subsequent releases for that matter). You will brick. This is what vzw/samsung did on the first OTA for the Galaxy S4. They changed the keys they sign the firmware with. This prevents us from 'mis-matching' our firmware like we've been doing all along. We've been leaving aboot (VRUAME6, the african-canadian sock-monkey leaked bootloader) alone and updating everything else. Since they're signing with different keys now, doing this will brick your device. If you update the ENTIRE bootchain (including aboot) you shouldn't brick, but will be stuck with a locked bootloader and any attempt to downgrade (via dd, etc) will brick you as well."
Like i said I have been out for a while and lost track of what firmwares came out and the order of them and which I need to be on to flash a 4.4 ROM. Someone else told me the only reason my first flash failed was because my recovery was older
Click to expand...
Click to collapse
I see, that actually makes perfect sense.
I think I read you were on the mb1 firmware, that's new enough to not cause problems.
Basically you can't get the ml1 firmware from that thread I linked you. The only ml1 file available is the modem, and that's perfectly safe to flash.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
I see, that actually makes perfect sense.
I think I read you were on the mb1 firmware, that's new enough to not cause problems.
Basically you can't get the ml1 firmware from that thread I linked you. The only ml1 file available is the modem, and that's perfectly safe to flash.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I think I am getting it... I am on MB1...next was MF1....and then ML1. As long as I have a new recovery I can flash any MF1 based ROM right over MB1...and then I can flash the ML1 modem ONLY. If that is correct let me know..also does it matter if I do MF1 ROM or ML1 modem first?
again just wanted to say thanks for the help I appreciate it

aholeinthewor1d said:
I think I am getting it... I am on MB1...next was MF1....and then ML1. As long as I have a new recovery I can flash any MF1 based ROM right over MB1...and then I can flash the ML1 modem ONLY. If that is correct let me know..also does it matter if I do MF1 ROM or ML1 modem first?
again just wanted to say thanks for the help I appreciate it
Click to expand...
Click to collapse
You're close, firmware is completely independent from rom. You can flash any 4.3, 4.4, or 4.1 rom without changing your firmware.
Right now you can flash mf1 aio package, then ml1 modem, or just flash the ml1 modem over your current mb1 firmware.
Basically you aren't required to be on a specific rom build in order to use a specific modem.
Edit: I think you have the right idea, flash any rom you want, then the mf1 aio package, then the ml1 modem. Your firmware sequence is correct.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
You're close, firmware is completely independent from rom. You can flash any 4.3, 4.4, or 4.1 rom without changing your firmware.
Right now you can flash mf1 aio package, then ml1 modem, or just flash the ml1 modem over your current mb1 firmware.
Basically you aren't required to be on a specific rom build in order to use a specific modem.
Edit: I think you have the right idea, flash any rom you want, then the mf1 aio package, then the ml1 modem. Your firmware sequence is correct.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
ah ok...idk why I was thinking the firmware was what the ROMs were based from....so either way ML1 firmware sucks and I stay away...I guess my last questions are...what would be an advantage of going to the MF1 firmware...
and I always used clockworkmod recovery...do you know the option available now? and maybe some features of each

[Q] Stock NE1 keeping unlocked bootloader possible?

I have spent the last week researching how to proceed with updating my Verizon Galaxy S3, but haven't found a clear concise answer pertaining to my current scenario. I thought a thread with a definitive answer would help others in my same boat save alot of time.
The last time I updated my phone was with a stock rooted MB1 rom with CWM 6023 recovery and 3.0.31-861013 kernel (2/14/13) and unlocked bootloader. Knowing that nothing good has ever come from taking OTA updates, I then removed the OTA Certs. I've kept my fingers crossed with the releases of ML1, MF1, and ND3 hoping that they would be better than MB1 but public opinion of the downsides has kept me from updating to any of these previous versions.
Now I'm DYING to update to Kit Kat and a better modem/radio than what I currently have. I've had really really poor experiences with a variety of handsets over the last 4 years using custom roms like AOSP, Cyanogen, etc. Therefore, I typically like to run a stock rooted version of whatever the current rom at the time is and remove some of the bloat myself or often there will be bloatware free stock roms for various handsets floating around so those are what I gravitate toward. More often than not custom roms have too many bugs (ie, camera not working or mms failures, etc) for production use.
So that being said, what would be the best course of action for someone such as myself to get on NE1 (or a really, really, really solid KitKat with NO bugs) and keep an unlocked bootloader for future flexibility. And, more importantly be able to update the modem/radio without locking the bootloader (as I've read some have found their bootloader locked after modem update)?
Any advice would be greatly appreciated.

Muleguy said:
I have spent the last week researching how to proceed with updating my Verizon Galaxy S3, but haven't found a clear concise answer pertaining to my current scenario. I thought a thread with a definitive answer would help others in my same boat save alot of time.
The last time I updated my phone was with a stock rooted MB1 rom with CWM 6023 recovery and 3.0.31-861013 kernel (2/14/13) and unlocked bootloader. Knowing that nothing good has ever come from taking OTA updates, I then removed the OTA Certs. I've kept my fingers crossed with the releases of ML1, MF1, and ND3 hoping that they would be better than MB1 but public opinion of the downsides has kept me from updating to any of these previous versions.
Now I'm DYING to update to Kit Kat and a better modem/radio than what I currently have. I've had really really poor experiences with a variety of handsets over the last 4 years using custom roms like AOSP, Cyanogen, etc. Therefore, I typically like to run a stock rooted version of whatever the current rom at the time is and remove some of the bloat myself or often there will be bloatware free stock roms for various handsets floating around so those are what I gravitate toward. More often than not custom roms have too many bugs (ie, camera not working or mms failures, etc) for production use.
So that being said, what would be the best course of action for someone such as myself to get on NE1 (or a really, really, really solid KitKat with NO bugs) and keep an unlocked bootloader for future flexibility. And, more importantly be able to update the modem/radio without locking the bootloader (as I've read some have found their bootloader locked after modem update)?
Any advice would be greatly appreciated.
Click to expand...
Click to collapse
Unfortunately, the ML1 update locked the bootloader and that hasn't changed with NC1 or NE1 (as far as we know). MF1 is the latest update I know of that still has the option for an unlocked bootloader. I've never used custom ROMs (but would very much like to) but I am currently on NE1 so I can't. Granted, I will say that Kitkat is a good update and things are running well. HOWEVER, from someone who would LOVE to have that option for an unlocked bootloader, I would personally discourage updates that would lock your bootloader. But the choice is yours.
Quick question (to someone with a little more expertise), If you were still on an update BEFORE MF1, and you had the option to download it OTA, could you extract the update.zip from /cache/fota like we did for the Kitkat update and distribute it so people could then flash it with Odin (and get unlocked bootloaders)? Or am I missing some flaw with that plan?

Muleguy said:
I have spent the last week researching how to proceed with updating my Verizon Galaxy S3, but haven't found a clear concise answer pertaining to my current scenario. I thought a thread with a definitive answer would help others in my same boat save alot of time.
The last time I updated my phone was with a stock rooted MB1 rom with CWM 6023 recovery and 3.0.31-861013 kernel (2/14/13) and unlocked bootloader. Knowing that nothing good has ever come from taking OTA updates, I then removed the OTA Certs. I've kept my fingers crossed with the releases of ML1, MF1, and ND3 hoping that they would be better than MB1 but public opinion of the downsides has kept me from updating to any of these previous versions.
Now I'm DYING to update to Kit Kat and a better modem/radio than what I currently have. I've had really really poor experiences with a variety of handsets over the last 4 years using custom roms like AOSP, Cyanogen, etc. Therefore, I typically like to run a stock rooted version of whatever the current rom at the time is and remove some of the bloat myself or often there will be bloatware free stock roms for various handsets floating around so those are what I gravitate toward. More often than not custom roms have too many bugs (ie, camera not working or mms failures, etc) for production use.
So that being said, what would be the best course of action for someone such as myself to get on NE1 (or a really, really, really solid KitKat with NO bugs) and keep an unlocked bootloader for future flexibility. And, more importantly be able to update the modem/radio without locking the bootloader (as I've read some have found their bootloader locked after modem update)?
Any advice would be greatly appreciated.
Click to expand...
Click to collapse
You are basically going to have to wait until a dev puts out a stock, rooted, knoxless ROM based on NE1. I've never heard of a modem flash locking a bootloader. Modern has nothing to do with the bootloader. Anyone who said this happened to them most likely flashed the firmware or full factory tar instead of the modem file by accident.
Sent from the Shark Tank using XDA Premium 4 mobile app
---------- Post added at 10:26 AM ---------- Previous post was at 10:23 AM ----------
JacobManning17 said:
Unfortunately, the ML1 update locked the bootloader and that hasn't changed with NC1 or NE1 (as far as we know). MF1 is the latest update I know of that still has the option for an unlocked bootloader. I've never used custom ROMs (but would very much like to) but I am currently on NE1 so I can't. Granted, I will say that Kitkat is a good update and things are running well. HOWEVER, from someone who would LOVE to have that option for an unlocked bootloader, I would personally discourage updates that would lock your bootloader. But the choice is yours.
Quick question (to someone with a little more expertise), If you were still on an update BEFORE MF1, and you had the option to download it OTA, could you extract the update.zip from /cache/fota like we did for the Kitkat update and distribute it so people could then flash it with Odin (and get unlocked bootloaders)? Or am I missing some flaw with that plan?
Click to expand...
Click to collapse
Flashing that update.zip file through ODIN before a dev had a chance to remove Knox and the locked down bootloader would be the same exact thing as accepting the OTA. You would then be locked down.
Sent from the Shark Tank using XDA Premium 4 mobile app

landshark68 said:
You are basically going to have to wait until a dev puts out a stock, rooted, knoxless ROM based on NE1. I've never heard of a modem flash locking a bootloader. Modern has nothing to do with the bootloader. Anyone who said this happened to them most likely flashed the firmware or full factory tar instead of the modem file by accident.
Sent from the Shark Tank using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I ran across a thread on here just this morning where someone was trying to update just the modem and ended up with a locked bootloader. The replies suggested that Samsung may have slipped something in with the modem file this go around. That's why I included it in this question. I will have to try to find the link to the other thread when I have more time later.

Muleguy said:
I ran across a thread on here just this morning where someone was trying to update just the modem and ended up with a locked bootloader. The replies suggested that Samsung may have slipped something in with the modem file this go around. That's why I included it in this question. I will have to try to find the link to the other thread when I have more time later.
Click to expand...
Click to collapse
You might be referring to this post in the general section. I am still unsure how they managed to do this if they downloaded the 20 MB VRUCML1 modem from our S3 forum. There is only one person whom I know to have extracted it and that is Invisiblek. Not a single other person before this user has mentioned having their bootloader locked from installing the VRUCML1 modem in CWM or TWRP. I really did not understand what they were trying to say so I just kept the convo moving in a different direction.

landshark68 said:
Flashing that update.zip file through ODIN before a dev had a chance to remove Knox and the locked down bootloader would be the same exact thing as accepting the OTA. You would then be locked down.
Sent from the Shark Tank using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm on ML1 unlocked bootloader/rooted from here
http://forum.xda-developers.com/showthread.php?t=2591895
If I flash NE1 via ODIN will it wipe my phone resulting in a clean NE1 with locked bootloader or will it be a non-destructive upgrade to fully stock/locked NE1?

lexluthor said:
I'm on ML1 unlocked bootloader/rooted from here
http://forum.xda-developers.com/showthread.php?t=2591895
If I flash NE1 via ODIN will it wipe my phone resulting in a clean NE1 with locked bootloader or will it be a non-destructive upgrade to fully stock/locked NE1?
Click to expand...
Click to collapse
Not sure whether the tar file you can download from sammobile will wipe your phone, but the tar file provided by open1your1eyes0 in the below linked thread will not wipe your phone. Either way, you will be on locked down NE1. Read the disclaimer at the top of the OP in open1your1eyes0's thread:
http://forum.xda-developers.com/showthread.php?t=2795659

landshark68 said:
Not sure whether the tar file you can download from sammobile will wipe your phone, but the tar file provided by openyoureyes1 in the below linked thread will not wipe your phone. Either way, you will be on locked down NE1. Read the disclaimer at the top of the OP in openyoureyes1's thread:
http://forum.xda-developers.com/showthread.php?t=2795659
Click to expand...
Click to collapse
I don't care if I'm locked going forward. So if I flash that, after I'll still have all my apps and appdata and be on NE1, locked? And then I can root with towelroot?

lexluthor said:
I don't care if I'm locked going forward. So if I flash that, after I'll still have all my apps and appdata and be on NE1, locked? And then I can root with towelroot?
Click to expand...
Click to collapse
I believe that is correct. I thought I saw a few people in the 4.4.2 update thread post that towelroot worked on NE1. May want to read the last few pages of that thread just to make sure about towelroot.

lexluthor said:
I don't care if I'm locked going forward. So if I flash that, after I'll still have all my apps and appdata and be on NE1, locked? And then I can root with towelroot?
Click to expand...
Click to collapse
That is correct. Towelroot works just fine with NE1
Sent from my SCH-I535 using XDA Premium 4 mobile app

landshark68 said:
I believe that is correct. I thought I saw a few people in the 4.4.2 update thread post that towelroot worked on NE1. May want to read the last few pages of that thread just to make sure about towelroot.
Click to expand...
Click to collapse
So far, looking ok. I flashed via ODIN and now it's at Android is upgrading and it's optimizing 502 apps, so looks like the apps are still there.
Hopefully towelroot works fine and then I can tweak my system settings back, install xposed and I'm good to go.
---------- Post added at 09:17 PM ---------- Previous post was at 08:25 PM ----------
lexluthor said:
So far, looking ok. I flashed via ODIN and now it's at Android is upgrading and it's optimizing 502 apps, so looks like the apps are still there.
Hopefully towelroot works fine and then I can tweak my system settings back, install xposed and I'm good to go.
Click to expand...
Click to collapse
All went great. It took a good half hour after the upgrade for the CPU to stop being pegged at 100% and have the phone be responsive again.
Very easy, it kept all of my applications and settings and I didn't really need to do much other than towelroot and re-install xposed.
I'm due for an upgrade soon anyhow, so I didn't really want to go through a lot of work getting to Kitkat.

Towel root not working any longer. Keep getting unsupported device with NE1 .. Ugh ..