Where can I find a stock rooted rom? The two I found one times out during the download and the other fails when I try to flash it.
http://forum.xda-developers.com/showthread.php?t=1890125
http://forum.xda-developers.com/showthread.php?t=1945558
http://forum.xda-developers.com/showthread.php?t=1865590
http://forum.xda-developers.com/showthread.php?t=2021374
Take your pick really. I hope this helps. There are more but they are scattered. Some of these are stock based, but on a few we have there is the option to be completely stock and rooted.
Related
I recently took the ota update to 4.1.2 mb1 and lost root. My question is can I use odin to flash [ROM|Stock Rooted] 3/3/13 Sprint Touchwiz Jelly Bean 4.1.2 (L710VPBMB1) Odex/DeOdex? And If so do I use the full ROM odex? And Do I have to flash anything besides the ROM? Or can I keep everything else stock?
Monoclypsus said:
I recently took the ota update to 4.1.2 mb1 and lost root. My question is can I use odin to flash [ROM|Stock Rooted] 3/3/13 Sprint Touchwiz Jelly Bean 4.1.2 (L710VPBMB1) Odex/DeOdex? And If so do I use the full ROM odex? And Do I have to flash anything besides the ROM? Or can I keep everything else stock?
Click to expand...
Click to collapse
Hey there buddy, welcome to XDA (I see this is your second post).
Anyways, do you still have a custom recovery? I'm assuming you don't, since it sounds like you went all the way back to stock unrooted in order o get the update (in the future, Freeza typically has the update for Root users a week or so after the OTA release, so no need to go back to stock unrooted).
Anyways, back to your current situation. Since you most-likely have the stock recovery, you'll have to go back to being rooted with either CWM or TWRP (I prefer TWRP, but they're both good). I personally use mskip's toolkit, it's fairly straightforward. You could also follow qbking77's rooting method. He does a good job explaining how to root. Samsung hasn't locked their bootloader and don't try to in their updates, so these rooting methods stand the test of time (and updates).
Once you have a custom recovery installed (or if you already have one installed), FIRST THING to do is perform a nandroid backup. THIS IS KEY. Once you have one done, go ahead and flash Freeza's Stock Rooted ROM. I'd recommend doing a clean flash, as it's the best way to minimize the chances of errors and bugs. Just wipe system and cache and dalvik cache, and then flash the downloaded ROM. And speaking of downloading, be sure to check the md5 sum of the download before you flash. Most problems with the stable ROMs here on XDA stem from bad downloads.
You can also check out other ROMs. I won't go too crazy on advertising here, but scroll through these two sub-forums, Android Development and Original Android Development. I've enjoyed most ROMs I've tried.
Hope this helps!
ok
topherk said:
Hey there buddy, welcome to XDA (I see this is your second post).
Anyways, do you still have a custom recovery? I'm assuming you don't, since it sounds like you went all the way back to stock unrooted in order o get the update (in the future, Freeza typically has the update for Root users a week or so after the OTA release, so no need to go back to stock unrooted).
Anyways, back to your current situation. Since you most-likely have the stock recovery, you'll have to go back to being rooted with either CWM or TWRP (I prefer TWRP, but they're both good). I personally use mskip's toolkit, it's fairly straightforward. You could also follow qbking77's rooting method. He does a good job explaining how to root. Samsung hasn't locked their bootloader and don't try to in their updates, so these rooting methods stand the test of time (and updates).
Once you have a custom recovery installed (or if you already have one installed), FIRST THING to do is perform a nandroid backup. THIS IS KEY. Once you have one done, go ahead and flash Freeza's Stock Rooted ROM. I'd recommend doing a clean flash, as it's the best way to minimize the chances of errors and bugs. Just wipe system and cache and dalvik cache, and then flash the downloaded ROM. And speaking of downloading, be sure to check the md5 sum of the download before you flash. Most problems with the stable ROMs here on XDA stem from bad downloads.
You can also check out other ROMs. I won't go too crazy on advertising here, but scroll through these two sub-forums, Android Development and Original Android Development. I've enjoyed most ROMs I've tried.
Hope this helps!
Click to expand...
Click to collapse
Ok, just out of curiousity... Before I took the OTA i was rooted 4.1.1 stock with stock recovery. Is there any way to do it the same? The method I used before was this [HOWTO] [ROOT] No Tripping Flash Counter [SPR L710VPBLJ7] JB 4.1.1. It was super quick and easy.
Monoclypsus said:
Ok, just out of curiousity... Before I took the OTA i was rooted 4.1.1 stock with stock recovery. Is there any way to do it the same? The method I used before was this [HOWTO] [ROOT] No Tripping Flash Counter [SPR L710VPBLJ7] JB 4.1.1. It was super quick and easy.
Click to expand...
Click to collapse
Yeah, that same method should work. I personally like the custom recoveries, but understand your desires to leave it at stock recovery (not triggering the flash counter).
Like I mentioned before, Samsung hasn't (and most likely won't) locked their bootloaders, so any rooting method that has worked in the past should work in the future. Just make sure to read the last 3-4 pages of the thread for whatever method you're trying to use to see if there are any issues. I know an earlier version of mskip's toolkit was having issues with JB for a little bit (it's updated now).
Well I'm gonna give it a shot. Ill let you know how it turns out.
Sent from my SPH-L710 using xda app-developers app
Just went with cf autoroot. Worked fine.
Sent from my SPH-L710 using xda app-developers app
I've got a problem I installed the OTA and now I cant boot into android. Its stuck on starting apps. I have the stock recovery. How can I fix this?. What do I do? I can get to ODIN download mode. *edit** can get into safemode too. And I now have a custom recovery installed.
I still dont know what to do from here. How do I flash the downloaded rom because the new file I downloaded seems to be a zip and can only be flashed with CWM not ODIN. I cant place it in the right directory of my phone to do that.
jkj said:
I've got a problem I installed the OTA and now I cant boot into android. Its stuck on starting apps. I have the stock recovery. How can I fix this?. What do I do? I can get to ODIN download mode. *edit** can get into safemode too. And I now have a custom recovery installed.
I still dont know what to do from here. How do I flash the downloaded rom because the new file I downloaded seems to be a zip and can only be flashed with CWM not ODIN. I cant place it in the right directory of my phone to do that.
Click to expand...
Click to collapse
I replied to your thread. I hope it works for what you need.
Hello, I'm having a strange issue with my GS4. I have rooted it and flashed a couple different custom ROMS on it, but I decided to go back to stock so that I could get the 4.3 OTA. I did the triangle away and then flashed stock 4.2.2 software through odin. However, when I go to search for the update, I get the following message " Your device has been modified. Software updates are not available.". In fact my device status still says CUSTOM under device status in about phone. Could this be because the flash counter is still tripped, or did I flash a bad stock firmware download?
Also strange: I've noticed that the sound my phone makes when I lock it is not the stock sound, it's still the lock sound from wicked V8 Rom.
Any help anyone could give me would be greatly appreciated. Thanks.
thunderstorm116 said:
Hello, I'm having a strange issue with my GS4. I have rooted it and flashed a couple different custom ROMS on it, but I decided to go back to stock so that I could get the 4.3 OTA. I did the triangle away and then flashed stock 4.2.2 software through odin. However, when I go to search for the update, I get the following message " Your device has been modified. Software updates are not available.". In fact my device status still says CUSTOM under device status in about phone. Could this be because the flash counter is still tripped, or did I flash a bad stock firmware download?
Also strange: I've noticed that the sound my phone makes when I lock it is not the stock sound, it's still the lock sound from wicked V8 Rom.
Any help anyone could give me would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
Just my personal experience, but whenever using Odin to revert back to stock, it always works right if I flash a non-TouchWiz ROM via TWRM/CWM THEN use Odin to revert. When reverting via Odin from a modified TW something always tends to stick around.
As far as returning to official status, you should be able to use Triangle-away on a rooted/stock firmware then temporarily unroot to install the OTA. Just a question though; why do the official OTA which introduces the Knox counter? There are CWM-flashable pre-rooted, non-Knox 4.3 TMO TW ROMs out already...
lordcheeto03 said:
Just my personal experience, but whenever using Odin to revert back to stock, it always works right if I flash a non-TouchWiz ROM via TWRM/CWM THEN use Odin to revert. When reverting via Odin from a modified TW something always tends to stick around.
As far as returning to official status, you should be able to use Triangle-away on a rooted/stock firmware then temporarily unroot to install the OTA. Just a question though; why do the official OTA which introduces the Knox counter? There are CWM-flashable pre-rooted, non-Knox 4.3 TMO TW ROMs out already...
Click to expand...
Click to collapse
Thanks for quick response. So you're saying I should root, then flash a stock aosp or gpe rom, and flash stock rom from there? I actually did have a gpe rom on my phone the last time I went back to stock, but I had wicked V8 first and went back to stock in between.
Another question would be if that small thing like the lock sound would be what's making me not be able to get the ota, or is it because the flash counter is tripped still and it's saying that I'm still custom?
noob question sorry, how do you temporarily unroot?
thunderstorm116 said:
Thanks for quick response. So you're saying I should root, then flash a stock aosp or gpe rom, and flash stock rom from there? I actually did have a gpe rom on my phone the last time I went back to stock, but I had wicked V8 first and went back to stock in between.
Another question would be if that small thing like the lock sound would be what's making me not be able to get the ota, or is it because the flash counter is tripped still and it's saying that I'm still custom?
noob question sorry, how do you temporarily unroot?
Click to expand...
Click to collapse
The reason you can't OTA is because your flash counter is still tripped. If it says you are on a custom firmware then you won't be able to update via OTA.
No need to re-root. Just use Odin to flash a custom recovery. Once there, I'd flash whatever non-TouchWiz ROM you have on-hand... Wicked, the TouchWiz Infamous ROMs, GPe ROMs (maybe, I don't know about these) I would avoid. If you already have CM10.x-11, ParanoidAndroid, Liquid, etc readily available, say, on your SD card I'd flash one of them. No need to flash the gapps, kernel, whatever, just the base ROM itself. Once that's done, use Odin to flash the Stock MDL .tar. After that, I'd say flash CF-Auto Root, run Triangle Away, then in the superuser App there should be an option to unroot (or temporarily unroot). Once that's done, you should be able to update via OTA.
lordcheeto03 said:
The reason you can't OTA is because your flash counter is still tripped. If it says you are on a custom firmware then you won't be able to update via OTA.
No need to re-root. Just use Odin to flash a custom recovery. Once there, I'd flash whatever non-TouchWiz ROM you have on-hand... Wicked, the TouchWiz Infamous ROMs, GPe ROMs (maybe, I don't know about these) I would avoid. If you already have CM10.x-11, ParanoidAndroid, Liquid, etc readily available, say, on your SD card I'd flash one of them. No need to flash the gapps, kernel, whatever, just the base ROM itself. Once that's done, use Odin to flash the Stock MDL .tar. After that, I'd say flash CF-Auto Root, run Triangle Away, then in the superuser App there should be an option to unroot (or temporarily unroot). Once that's done, you should be able to update via OTA.
Click to expand...
Click to collapse
Ah, okay. I think I understand that, I'll give that a try. Thanks for all your help.
Okay, so I tried doing everything you told me to do and got some weird results and thought I'd post them for anyone else that may run into this problem.
I flashed a custom recovery through Odin, then flashed the AOSP Liquid Rom like you said. I then flashe the stock MD5 file through Odin and let it do its thing. Once it was done, that's where the weird stuff started. The phone rebooted as it should, but then it got hung on the white T-mobile screen. It just sat there for a very long time. Now I've done this enough times to know when its taking too long and there's a problem.
So I did something that I know probably shouldn't have done and I held down the power button until it turned off. I then tried to boot it again to no avail, same thing.
After this I booted into the stock recovery and decided to do a factory data reset from there. (I was pretty sure there was nothing wrong with the stock Rom as I've used it before; there must have been something still there from the Liquid Rom causing problems.) When I rebooted from the recovery this way, it finally booted right up.
I now thought that I needed to flash CF-AutoRoot and then triangle away, but no, for some strange reason my device status now reads OFFICIAL!
I searched for the update and it is now in the process of downloading.
(Strangely enough though, the lock sound from wicked V8, is STILL there. I don't get it and I don't even want to know anymore.)
Sorry for the super long post, but I thought that if anyone else was having my same problem they should see this.
Thanks again for all your help and I hope you'e having a great Thanksgiving.
So a couple of days ago I got a GS3 running the OTA stock 4.3. I wasn't sure if I wanted to use it because I find Touch Wiz kind of clunky. So I decided I would try out Cyanogenmod. I installed it via their new handy installer (as the sprint GS3 is one of the compatible devices). All went well and I got Cyanogenmod 10.2 running smoothly. Now I want to activate the device, but apparently you can't activate a rooted device on sprint. So now i need to get it back to stock 4.3 and I can only seem to find solutions to his problem for devices that have not gotten the 4.3 OTA update and are still running 4.1.2. On the Cyanogenmod installer guide says:
You may perform a full backup from recovery, after flashing recovery (you will have to do this manually, at the moment) and then copy it off the device, if you don't have an external sdcard. If you've already run the installer, you will have to find stock images and flash them using fastboot or Odin.
Click to expand...
Click to collapse
My problem Is I can't locate any stock 4.3 images with which to try this. If I can get my hands on a stock 4.3 image, would the process be just going into the bootloader and using Odin to flash the 4.3 image?
Can anyone help me out?
You only need to be on a stock tw rom, even if you are rooted it should activate. There are a couple in the development section.
metalfan78 said:
You only need to be on a stock tw rom, even if you are rooted it should activate. There are a couple in the development section.
Click to expand...
Click to collapse
I see, do you know of any any good 4.3 based tw roms? All the ones I'm finding are based on 4.1. Also, do I need to do anything special to flash from Cyanogenmod 10.2 to a touchwiz rom (as Cyanogenmod is AOSP)? I already have ClockworkMod recovery installed.
Nothing special, flash like anything else
http://forum.xda-developers.com/showthread.php?t=2541900
[STOCK ROM] Stock 4.3 MK3 ROM [ROOTED/UNROOTED]
I have a quick question. I am on a stock rooted 4.1.1 att sgs3. I was curious if i flashed this rom/kernal,[ROM/KERNEL][4.4.2] Quantum 3.54 & QuantumKernel 3/7, would i be able to go back to my stock rooted rom if I wanted to? Thanks in advance.
Looks like you are trying to flash a custom ROM. Don't know much about these particular ROMs you mentioned but you need to your research thoroughly on custom ROMs before flashing. You may know most Custom ROMs don't come with their own bootloaders but still have to rely on a manufacturer's bootloader to run. You should, therefore, avoid any ROM that may update your bootloader because this is the only way that you would not be able to return to your previous stock version. If the ROM simply updates the system without mucking with your bootloader, there is no reason why you may not be able to return to stock.
I had an AT&T SG3 on stock 4.1.1 and I was able to flash KitKat (4.4) based CM11 and return to stock 4.1.1 without any hitches. Finally, whilst you are still on stock 4.1.1 I would suggest you take advantage of all the flexibilities offered by this Android version especially free unlocking before you begin tinkering with firmware.
So as long as I dont update my bootloader, I should be fine on going back to stock rooted 4.1.1? Thanks for the info!!
So how do i know what roms dont mess with the bootloader?
Most ROMS do not include an aboot file. I have flashed CM11, Validus, Slim, and Cyanfox and none of these altered the bootloader.
I suggest that you find a ROM you like, unzip the file, and look at the updater script to determine which bootloaders are required to install the ROM on your phone.
Ok guys, thanks for the tips. I just didn't want to get stuck on a firmware where i could not have root anymore or go back to a stock rooted rom.
I followed this guide "[ROM][6.0.1]MODest Rom☆Multi-DPI☆Stock-Modded☆CQL1☆(1/26/18" to get to a custom rom.
I've been looking but can't seem to find a guide to get back to stock. Is it as simple and flashing the stock rom with ODIN?
Depends. Do you want stock w/locked bootloader/recovery? Then yes.
If you want stock unlocked bootloader/rootable that is slightly different.