Develop Bugs

[ROM] Pre-rooted stock 6.2.2

I've put together a pre-rooted version of the stock 6.2.2 update from (link courtesy of b63). I did this like the 6.2.1 pre-rooted zip, in that it's just the stock update without the bootloader/recovery images and with su/Superuser/busybox added. So as a quick summary:
This will format and replace your /system partition, meaning you will need to reinstall anything that was modified or added there (Market, maps framework, etc). This also means it should be good to use as a fresh ROM - I tested by wiping my /system partition and flashing it and it installed just fine.
It's built to be installed via TWRP, or really any custom recovery should work.
Superuser, the su binary, and busybox are pre-installed and symlinked.
This does not have any modifications intended to block OTA updates. Other than the necessary root binaries it is completely stock.
Installing this will not touch your bootloader or recovery partitions. The updated images for both of those have been removed and the script will not attempt to install them.
Wiping /data shouldn't be necessary if you're on another stock build (wasn't needed for my testing).
If you're already on 6.2.2, this won't root you (you want jcase's thread for that).
I have an "unsecure" boot image version and a "secure" boot image version. Unsecure means adbd is running as root so you get a # (root prompt) immediately when you shell in with adb. Secure means you get a $ (user prompt) when you shell and need to use 'su' to elevate to root.
As with most ROMs and such, a backup is recommended before flashing, flash at your own risk, etc etc. I've tested this on my Fire several times and had no issues, but I can't guarantee 100% that it will work for everyone (though I don't see any reason it won't). If you see errors about the '/misc' partition, don't worry - TWRP is looking for it but the KF doesn't have that partition. It won't affect the install.
Enjoy!
Downloads
Mediafire links:
Pre-rooted stock 6.2.2 - unsecure boot image (md5: eb0139533593edb8d7a4a2aae22e1cd8)
Pre-rooted stock 6.2.2 - secure boot image (md5: cdf032c3543da5805a1b1204247876db)​
Multiupload links (appear down, but I'll leave 'em for now in case they come back)
Pre-rooted stock 6.2.2 - unsecure boot image (md5: eb0139533593edb8d7a4a2aae22e1cd8)
Pre-rooted stock 6.2.2 - secure boot image (md5: cdf032c3543da5805a1b1204247876db)​

Well done, sir. I used your pre-rooted 6.2.1 ROM and was quite pleased to discover that it left my Android Market unscathed and was equally pleased to discover the same on this version. Thank you.

I've been using pre-rooted 6.2.1 ROM, will updating to this one reformat the /system partition and wipe out everything?

ch0mch0m said:
I've been using pre-rooted 6.2.1 ROM, will updating to this one reformat the /system partition and wipe out everything?
Click to expand...
Click to collapse
Yes, it will format /system, even if you're running the 6.2.1 I made previously. It's easiest to just think of it as a separate ROM, not an update to the 6.2.1 one (although of course the only difference is Amazon's updates between 6.2.1 and 6.2.2).
FWIW, I just use Titanium to back up the Market and Google Maps and I keep a copy of the maps framework jar/xml files on my sdcard so I can copy them back over. That and if the Market has updated itself it shouldn't get blown out anyway since the Market update apparently installs itself to /data instead of /system. GoogleServicesFramework should stick around in /data, too, but I back that up as well anyway.

Very awesome, thank you!! I just installed over your rooted stock 6.2.1 with a cache/dvalik wipe and everything works. Market and all my installed apps still work like a charm!

Just a thank you for this. Backed up, Flashed, wiped cache/dalvik and am now running 6.2.2 rooted with everything intact. Swift Key keeps force closing but I'll try reinstalling that.
edit: reinstalled Swift Key and I am back 100%. There is a full screen button in Silk and my books aren't distorted in icon form anymore!

Anyone else gettting force closes on google's gmail app?
Edit: I uninstalled and reinstalled gmail and it works fine now.

Thanks ... Market FC on me after update ... restored it from Titanium seems to work

Thank you. Flashed without incident. I did wipe cache and davik-cache first. Market did not have to be reinstalled and worked perfectly, including a download. I'm now 2 for 2 without getting an OTA and still on the original OneClickRoot method (was that what it was called? Seems so long ago!!)

It was SuperOneClick... me too. And, yeah, I almost don't remember it's been so long ago and I've read too many threads about this and that.

Flashed this, watched some amazon video, turned off the screen, and all of a sudden my kindle restarted and now my prerooted 6.2.2 must have been replaced with the ota because twrp is gone. I don't know how this happened, but basically be careful everybody! That's all I can really say...

Worked like charm. Flashed, updated location files and everything was up and running again in a matter of minutes.

DalekCaan said:
Flashed this, watched some amazon video, turned off the screen, and all of a sudden my kindle restarted and now my prerooted 6.2.2 must have been replaced with the ota because twrp is gone. I don't know how this happened, but basically be careful everybody! That's all I can really say...
Click to expand...
Click to collapse
Any more info? Did you lose root too? Which version did you install, the secure or unsecure?

Just flashed this (unsecured), and deleted otacerts.zip as outlined here:
http://forum.xda-developers.com/showthread.php?t=1451328
We'll see if I end up getting the update anyway...

Anybody still have this file, megaupload link is not working.

Willieumm said:
Anybody still have this file, megaupload link is not working.
Click to expand...
Click to collapse
Try the Deposit Files or FileServe links. Those seem to be working still.
I'm guessing some of the others may have disappeared due to the fallout from the giant Megaupload raid/lawsuit...

eldarerathis said:
Try the Deposit Files or FileServe links. Those seem to be working still.
I'm guessing some of the others may have disappeared due to the fallout from the giant Megaupload raid/lawsuit...
Click to expand...
Click to collapse
Can you point me to those other links? I dont see them in this thread.
Thanks
GM

George M said:
Can you point me to those other links? I dont see them in this thread.
Thanks
GM
Click to expand...
Click to collapse
The Multiupload links seem to be down completely now (actually, Multiupload as a whole is just down for me) so I'm going to re-upload them. I'll try Mediafire this time, see if it survives longer

eldarerathis said:
The Multiupload links seem to be down completely now (actually, Multiupload as a whole is just down for me) so I'm going to re-upload them. I'll try Mediafire this time, see if it survives longer
Click to expand...
Click to collapse
That would be great.

George M said:
That would be great.
Click to expand...
Click to collapse
Try one of these links:
Unsecure boot: http://www.mediafire.com/?gtxrohbc4gmu4m8
Secure boot: http://www.mediafire.com/?ttd8t49zosd910b

[Q] Unroot before OTA?

Hey guys,
So I have a rooted phone but everything else is stock, so I'm wondering if I need to unroot before I do the OTA. If I don't, do I need to re-root it after the OTA?

I wouldn't bother unrooting...entirely unneeded...unless you feel like going through the process.
I did mine in about five minutes, using the official sprint update zip that was pushed down to my phone. I've used this method since my EVO OG days and it seems to work very well for my phone...for whatever reason. Some folks have no problem with my method, some folks don't have much luck. Caveat Emptor.
Here's what I did as a synopsis:
**NOTE!!!! I have CWM Recovery v6.0.1.2 on my phone.**
1. Went into Root Explorer and moved the update zip file out of /cache to my external card.
2. Shut down my phone completely.
3. Boot it up holding home+volume up+power until the first flash on the screen, then release. This puts you in CWM Recovery.
4. Flash zip file, and choose your external sdcard and browse to your update zip that you moved in there via Root Explorer. Go ahead and install it. It should only take about a minute or two...it's a small update.
5. After it has completed, go back in the menu, wipe the cache directory, go to advanced and wipe the dalvik cache.
6. Choose to reboot your phone - CWM will WARN YOU that the recovery will be replaced, do you want to fix? Say yes. CWM will WARN YOU that root access may be removed, do you want to fix? SAY yes! (When someone asks if you're a God...you say YESSSSSSSSSSSSSSSS!!!!!!! - sorry...i had to)
7. The phone reboots and you'll see so many android elements being upgraded or optimized. It takes a minute or two.
8. Now that you're in your phone, verify the versions, make sure your root programs work (they should), and enjoy!
This process literally took me five minutes while I was cooking dinner...easy peasy. Not sure if other recovery versions of CWM or other software recovery packages will do exactly what I was able to do. But it's a very easy process for me. On my old OG, I'd had to restore root after the first reboot...kind of sloppy, but got the job done easily enough. This version of CWM Recovery knows that something has been adjusted and will fix it before you really reboot the system. That's slick.

Ytsejamer1 said:
I wouldn't bother unrooting...entirely unneeded...unless you feel like going through the process.
I did mine in about five minutes, using the official sprint update zip that was pushed down to my phone. I've used this method since my EVO OG days and it seems to work very well for my phone...for whatever reason. Some folks have no problem with my method, some folks don't have much luck. Caveat Emptor.
Here's what I did as a synopsis:
**NOTE!!!! I have CWM Recovery v6.0.1.2 on my phone.**
1. Went into Root Explorer and moved the update zip file out to my external card.
2. Shut down my phone completely.
3. Boot it up holding home+volume up+power until the first flash on the screen, then release. This puts me in CWM Recovery.
4. Flash zip file, and choose your external sdcard and browse to your update zip that you moved in there via Root Explorer. Go ahead and install it. It should only take about a minute or two...it's a small update.
5. After it has completed, go back in the menu, wipe the cache directory, go to advanced and wipe the dalvik cache.
6. Choose to reboot your phone - CWM will WARN YOU that the recovery will be replaced, do you want to fix? Say yes. CWM will WARN YOU that root access may be removed, do you want to fix? SAY yes! (When someone asks if you're a God...you say YESSSSSSSSSSSSSSSS!!!!!!! - sorry...i had to)
7. The phone reboots and you'll see so many android elements being upgraded or optimized. It takes a minute or two.
8. Now that you're in your phone, verify the versions, make sure your root programs work (they should), and enjoy!
This process literally took me five minutes while I was cooking dinner...easy peasy. Not sure if other recovery versions of CWM or other software recovery packages will do exactly what I was able to do. But it's a very easy process for me. On my old OG, I'd had to restore root after the first reboot...kind of sloppy, but got the job done easily enough. This version of CWM Recovery knows that something has been adjusted and will fix it before you really reboot the system. That's slick.
Click to expand...
Click to collapse
I can't try that since my external card has become unmounted somehow... But would I still be able to update without un-rooting?

vpy said:
I can't try that since my external card has become unmounted somehow... But would I still be able to update without un-rooting?
Click to expand...
Click to collapse
I did not UN-Rooot first!
If you have the stock recovery you can update via OTA, BUT you will have to re-root when you are done.
Thats what I had to go through anyway.
Moved to stock recovery. Run the OTA update then RE-Root.
I have a post someplace that explains what I went through in slightly more detail.

Ytsejamer1 said:
I wouldn't bother unrooting...entirely unneeded...unless you feel like going through the process.
I did mine in about five minutes, using the official sprint update zip that was pushed down to my phone. I've used this method since my EVO OG days and it seems to work very well for my phone...for whatever reason. Some folks have no problem with my method, some folks don't have much luck. Caveat Emptor.
Here's what I did as a synopsis:
**NOTE!!!! I have CWM Recovery v6.0.1.2 on my phone.**
1. Went into Root Explorer and moved the update zip file out to my external card.
2. Shut down my phone completely.
3. Boot it up holding home+volume up+power until the first flash on the screen, then release. This puts me in CWM Recovery.
4. Flash zip file, and choose your external sdcard and browse to your update zip that you moved in there via Root Explorer. Go ahead and install it. It should only take about a minute or two...it's a small update.
5. After it has completed, go back in the menu, wipe the cache directory, go to advanced and wipe the dalvik cache.
6. Choose to reboot your phone - CWM will WARN YOU that the recovery will be replaced, do you want to fix? Say yes. CWM will WARN YOU that root access may be removed, do you want to fix? SAY yes! (When someone asks if you're a God...you say YESSSSSSSSSSSSSSSS!!!!!!! - sorry...i had to)
7. The phone reboots and you'll see so many android elements being upgraded or optimized. It takes a minute or two.
8. Now that you're in your phone, verify the versions, make sure your root programs work (they should), and enjoy!
This process literally took me five minutes while I was cooking dinner...easy peasy. Not sure if other recovery versions of CWM or other software recovery packages will do exactly what I was able to do. But it's a very easy process for me. On my old OG, I'd had to restore root after the first reboot...kind of sloppy, but got the job done easily enough. This version of CWM Recovery knows that something has been adjusted and will fix it before you really reboot the system. That's slick.
Click to expand...
Click to collapse
What file is the update.zip loacted in. I found this file in the cache named ac3e74a5a71c.update_SPH-L710_LJ7_to_MA6.zip, is that it. Thanks

You WILL lose root when you update, but it will update as long as you are on a stock rom with stock recovery. To make things easier, install Voodoo OTA rootkeeper and use it to back up root before updating. Then all you will have to do to re-root is restore root using Voodoo.

bigblue206 said:
What file is the update.zip loacted in. I found this file in the cache named ac3e74a5a71c.update_SPH-L710_LJ7_to_MA6.zip, is that it. Thanks
Click to expand...
Click to collapse
Yes, it's in /cache. I was thinking that, but my fingers didn't get the memo to type it. My bad. When Sprint downloads the patch to your phone, that's where it goes. I do the update manually, so I move it off to external card.

vpy said:
I can't try that since my external card has become unmounted somehow... But would I still be able to update without un-rooting?
Click to expand...
Click to collapse
You could save the file to /sdcard if you wanted...being that you're not formatting it or wiping it, you should be fine putting it there. Hell...you could leave it in the /cache directory if you really wanted to, however I like moving it out before I flash it.

Ytsejamer1 said:
I wouldn't bother unrooting...entirely unneeded...unless you feel like going through the process.
I did mine in about five minutes, using the official sprint update zip that was pushed down to my phone. I've used this method since my EVO OG days and it seems to work very well for my phone...for whatever reason. Some folks have no problem with my method, some folks don't have much luck. Caveat Emptor.
Here's what I did as a synopsis:
**NOTE!!!! I have CWM Recovery v6.0.1.2 on my phone.**
1. Went into Root Explorer and moved the update zip file out of /cache to my external card.
2. Shut down my phone completely.
3. Boot it up holding home+volume up+power until the first flash on the screen, then release. This puts you in CWM Recovery.
4. Flash zip file, and choose your external sdcard and browse to your update zip that you moved in there via Root Explorer. Go ahead and install it. It should only take about a minute or two...it's a small update.
5. After it has completed, go back in the menu, wipe the cache directory, go to advanced and wipe the dalvik cache.
6. Choose to reboot your phone - CWM will WARN YOU that the recovery will be replaced, do you want to fix? Say yes. CWM will WARN YOU that root access may be removed, do you want to fix? SAY yes! (When someone asks if you're a God...you say YESSSSSSSSSSSSSSSS!!!!!!! - sorry...i had to)
7. The phone reboots and you'll see so many android elements being upgraded or optimized. It takes a minute or two.
8. Now that you're in your phone, verify the versions, make sure your root programs work (they should), and enjoy!
This process literally took me five minutes while I was cooking dinner...easy peasy. Not sure if other recovery versions of CWM or other software recovery packages will do exactly what I was able to do. But it's a very easy process for me. On my old OG, I'd had to restore root after the first reboot...kind of sloppy, but got the job done easily enough. This version of CWM Recovery knows that something has been adjusted and will fix it before you really reboot the system. That's slick.
Click to expand...
Click to collapse
I tried this but it failed for me. I'm running CWM 5.5.0.4 though. How should I update to CWM Recovery v6.0.1.2?

Money24 said:
I tried this but it failed for me. I'm running CWM 5.5.0.4 though. How should I update to CWM Recovery v6.0.1.2?
Click to expand...
Click to collapse
This method doesn't seem to work for some folks...for whatever reason. It doesn't effect anything as the file won't flash, so if you want to upgrade CWM, yeah, give it another shot.

Ytsejamer1 said:
This method doesn't seem to work for some folks...for whatever reason. It doesn't effect anything as the file won't flash, so if you want to upgrade CWM, yeah, give it another shot.
Click to expand...
Click to collapse
Noob alert: So I just flash the CWM recovery 6.0.1.2 file with Odin? Can someone give me a simple walkthrough?

Money24 said:
Noob alert: So I just flash the CWM recovery 6.0.1.2 file with Odin? Can someone give me a simple walkthrough?
Click to expand...
Click to collapse
I don't have a walk through as during my initial root process, I ended up directly on CWM 6.0.1.2. However, a quick search here on XDA seemed to indicate ROM Manager was the easiest way to upgrade CWM versions. http://www.clockworkmod.com/rommanager
You may want to search around to see what you find out.

Ytsejamer1 said:
I don't have a walk through as during my initial root process, I ended up directly on CWM 6.0.1.2. However, a quick search here on XDA seemed to indicate ROM Manager was the easiest way to upgrade CWM versions.
You may want to search around to see what you find out.
Click to expand...
Click to collapse
Will do. Thank you for the help
---------- Post added at 10:43 AM ---------- Previous post was at 09:57 AM ----------
Ytsejamer1 said:
I don't have a walk through as during my initial root process, I ended up directly on CWM 6.0.1.2. However, a quick search here on XDA seemed to indicate ROM Manager was the easiest way to upgrade CWM versions.
You may want to search around to see what you find out.
Click to expand...
Click to collapse
Ok, so I updated with Rom manager and now on 6.0.2.3 and my install failed. Status 7 error or something like that. Any ideas? Thanks.

Money24 said:
Will do. Thank you for the help
---------- Post added at 10:43 AM ---------- Previous post was at 09:57 AM ----------
Ok, so I updated with Rom manager and now on 6.0.2.3 and my install failed. Status 7 error or something like that. Any ideas? Thanks.
Click to expand...
Click to collapse
Yeah, that seems to be the error for folks who can't update via my method...odd. Check this...Skunkape is gracious enough to post instructions and his way to update is fairly bulletproof. http://forums.androidcentral.com/sprint-galaxy-s-iii/257471-your-way-update-mb1.html

Updated MB1 to MD4
I know this is an old thread but just wanted to say I used this method to update to MD4.
I am rooted CMW moved the OTA file to SD card and followed these steps.
Did not lose root and have multi window on my GS3.
Thank you.

Re-installing su on Jelly Bean after removing it with Smelkus

Hi guys, I made a mistake while playing with Smelkus (Ra-supersonic-v4.3-smelkusMOD).
While in recovery, I went into the Developer Menu and entered on the "Install eng (unguarded) su" option, which after rebooting, disabled root access from my EVO. Now, every time I try to get root access I get a segmentation fault error.
I'm using MazWoz 4.2.1 Jelly Bean B4.
Short of re-flashing the ROM, Is there anything I can do to regain root access? I really got it working the way I want it, so I don't want to wipe everything if I can avoid it.
Thanks! Oh, by the way, I made no back up ...(I know, my mistake).

Have done the same thing trying to get SU to work properly with a rom. Easiest way is just to restore a nandroid backup.

Edit: Sorry, earlier it was in the dev section.

connman said:
Have done the same thing trying to get SU to work properly with a rom. Easiest way is just to restore a nandroid backup.
Click to expand...
Click to collapse
Unfortunately, I did not make a nandroid backup for this ROM (been using it for only 2 days!).
Anyway, here's what I did so far:
1)I "Pushed" the Superuser.apk found on the MozWoz Rom to my EVO using "adb."
And it did not work. The superuser application installed properly on my device because I can launch it fine from the app drawer, but it does not give me root privileges.
Any other suggestions?
There's gotta be a way to solving this. Exactly, what does the "Install eng (unguarded) su" option on Smelkus do anyway? Does anybody know?

Krazy4evo said:
Unfortunately, I did not make a nandroid backup for this ROM (been using it for only 2 days!).
Anyway, here's what I did so far:
1)I "Pushed" the Superuser.apk found on the MozWoz Rom to my EVO using "adb."
And it did not work. The superuser application installed properly on my device because I can launch it fine from the app drawer, but it does not give me root privileges.
Any other suggestions?
There's gotta be a way to solving this. Exactly, what does the "Install eng (unguarded) su" option on Smelkus do anyway? Does anybody know?
Click to expand...
Click to collapse
http://androidsu.com/superuser/
Download the ARM zip, flash in recovery. You also need the binary and not just the apk. That's why it still didn't work. If it still fails after this then clean wipe and flash ROM again.
Sent from my Galaxy Nexus using xda premium

the.emilio said:
http://androidsu.com/superuser/
Download the ARM zip, flash in recovery. You also need the binary and not just the apk. That's why it still didn't work. If it still fails after this then clean wipe and flash ROM again.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I flashed the ARM zip files with varying results, but none gave me root access.
Anyway, the only way I gained access was to reflash the ROM....
I hope this saves time for any one who's ran into this issue. Nothing but flashing the ROM seemed to work.

Krazy4evo said:
I flashed the ARM zip files with varying results, but none gave me root access.
Anyway, the only way I gained access was to reflash the ROM....
I hope this saves time for any one who's ran into this issue. Nothing but flashing the ROM seemed to work.
Click to expand...
Click to collapse
Glad that you got it figured out.
Like the.emilio said, there are two parts to the SU. You had just downloaded the apk (the app) but that needs the binary (instructions) to work.
I would have thought that the ARM files would have done this.
At any rate, you're back and working, so that's good news. My advice would be to now go make a nandroid backup. That way as you discover and play with this new rom, if you break something, you can easily return to a known "good" state without too much hassle.
Saved my bacon more than once over the years.

connman said:
Glad that you got it figured out.
Like the.emilio said, there are two parts to the SU. You had just downloaded the apk (the app) but that needs the binary (instructions) to work.
I would have thought that the ARM files would have done this.
At any rate, you're back and working, so that's good news. My advice would be to now go make a nandroid backup. That way as you discover and play with this new rom, if you break something, you can easily return to a known "good" state without too much hassle.
Saved my bacon more than once over the years.
Click to expand...
Click to collapse
I barely ran the ROM for 2 days before realizing I had not made a backup -lol!
My guess is that Smelkus was intended to be used with GB, so it created ROM root privileges that were different from later version of su? Maybe Smelkus needs to do a kernel check before enabling certain options?
Anyway, it's great to be back. And yes, I made a backup shortly after getting everything to work.

Krazy4evo said:
I barely ran the ROM for 2 days before realizing I had not made a backup -lol!
My guess is that Smelkus was intended to be used with GB, so it created ROM root privileges that were different from later version of su? Maybe Smelkus needs to do a kernel check before enabling certain options?
Anyway, it's great to be back. And yes, I made a backup shortly after getting everything to work.
Click to expand...
Click to collapse
Hmm. I'm running Smelkus in Provision/Jellyvision, which is a JB rom (great rom, by the way and very stable on our Evo). In fact, smelkusmod was recommended by the developer of Provision/Jellyvision as the recovery. It's based on AmonRA, so should be pretty compatible regardless.

Install unguarded su installs some old superuser hack as the su binary. Not sure what it was for, but it had a purpose at some point. The regular "Install or fix su & superuser" choice installs a normal (but quite old) version of the superuser.apk and binary and sets their permissions. Both should be avoided at this late stage of Evo use. I think Diablo updated to SuperSU on his version, but if you need to install Superuser (koush), SuperSU, or SuperUser it would be better to use the latest version of their respective flashable zips.
Recovery is entirely separate from the ROM and kernel you are running, so it doesn't matter if you have Jelly Bean, ICS, GB or even Android at all for that matter. All recoveries - stock, CWM, TWRP, RA, etc - are basically a mini-OS with their own kernel and init. It boots and runs the program, recovery. Recovery then executes built in commands and scripts included with it. When a ROM developer recommends a recovery, they are just promoting what they like. Any recovery can do the job in their own manner.
In your case, after installing that unguarded su, you could have done any of the following steps to recover:
Flashed a current Superuser zip if it was already on your phone
adb pushed one and flashed
Booted up the ROM, downloaded one, go back to recovery and flash
Flashed the ROM and gapps again, wiped cache and dalvik and rebooted
Restored backup if available

Rooted 4.1.2 what's the best way to update to 4.2

What's the best way to update since I can't update with the version that sprint pushed out since I'm rooted. Is it like a hacked version of the update that I can just update with? Yeah I'm a noob at this.
Thanks!

Not sure if your talking about 4.2 which is to my knowledge only with cm 10 or liquidsmooth or aokp most likely or 4.1.2 md4 either case download the appropriate file of your choice and flash from recovery do make sure backup amyways hope that answers your question
Sent from my SPH-L710 using XDA Premium HD app

six3onei said:
What's the best way to update since I can't update with the version that sprint pushed out since I'm rooted. Is it like a hacked version of the update that I can just update with? Yeah I'm a noob at this.
Thanks!
Click to expand...
Click to collapse
I think you mean update to 4.1.2. Check your version in settings about device. If it's 4.1.1 go here :
http://forum.xda-developers.com/showthread.php?p=586
Sent from my SPH-L710

Cm10.1
Sent from my SPH-L710 using xda app-developers app

Deviant Xone (linked in my sig). Awesome 4.2.2 ROM.

If you're going to any AOSP rom, be sure to update your recovery to the latest!
Also - Create a 0 folder in the root of your internal storage and move all of your files into /sdcard/0 (and I mean everything, files, folders, etc.) When you boot into latest recovery, it'll treat the sdcard/0 as your sdcard root folder. Once you flash an AOSP based rom, it will always use sdcard/0 as the root so if you create the 0 folder prior to flashing, you'll have all of your internal memory accessible.

Overstew said:
If you're going to any AOSP rom, be sure to update your recovery to the latest!
Also - Create a 0 folder in the root of your internal storage and move all of your files into /sdcard/0 (and I mean everything, files, folders, etc.) When you boot into latest recovery, it'll treat the sdcard/0 as your sdcard root folder. Once you flash an AOSP based rom, it will always use sdcard/0 as the root so if you create the 0 folder prior to flashing, you'll have all of your internal memory accessible.
Click to expand...
Click to collapse
Apparently you can avoid this by updating your recovery....the emulated 0 folder, I mean
Sent from my SPH-L710

Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

I'm running stock rom that I rooted... The phone version as of now is 4.1.2... as of 1 week I recieved an over the air update from sprint. I was thinking its 4.2 something maybe? maybe I wrong. I was wondering how could I get that update to install? Would i have to un-root then re-root?
Thanks!

six3onei said:
I'm running stock rom that I rooted... The phone version as of now is 4.1.2... as of 1 week I recieved an over the air update from sprint. I was thinking its 4.2 something maybe? maybe I wrong. I was wondering how could I get that update to install? Would i have to un-root then re-root?
Thanks!
Click to expand...
Click to collapse
Hey six3onei,
I'm assuming you just got the notification for the OTA (Over-The-Air) update. The newest version of the Stock Rom is MD4 which is still 4.1.2. Android version 4.2.x probably won't come out for your phone for a couple of months (that's my guess with no data to back it up other than my own intuition).
As far as upadating, you actually don't have to apply the OTA to get the latest and greatest for our phone. All you have to do is flash Freeza's Stock Rooted Rom (You'll want the DeOdex MD4 Rom). It'll give you the most up-to-date Stock Rom with Root. I've linked and quoted a previous post I made which will give you directions to flash it. Also, CNexus has done a great guide about OTAs over in the general sub-forum. I suggest giving that a look-through.
Also, just a note on the flashing sequence below: In step 4 below, if you're coming from a stock Rom and you're going to a stock Rom, all you have to do is wipe Cache and Dalvik Cache. If you're going to a different Rom, it's best to do a full wipe (in my opinion).
Ok, let's start at the very beginning (it's a very good place to start).
Before we get started, I'm going to make the following assumptions:
You successfully rooted your phone through Odin.
You currently have a custom recovery (either TWRP or CWM).
You have a Rom you'd like to flash on either your internal storage or your SDcard (I'd recommend the SDcard, but that's your prerogative).
If either of the first two is not true, I'd recommend going back to qbking77's thread and check out the videos on how to use Odin to gain root and a custom recovery.
If number 3 above is not true, download a ROM (nor someone new to flashing/custom Roms, I'd recommend Freeza's stock rooted Rom, as it's identical to stock TW, but just with Root). Once you download a Rom, check it's md5sum to verify that it's a good download. Copy the file to your SD card and get ready to flash (make sure you have decent battery life left, I try to keep at least 50% or more when flashing Roms, although it shouldn't take too long.
I'll give directions on how to flash a Rom below. The instructions will be for TWRP, but CWM has similar options/settings
Turn your phone completely off (hold down power for 3-5 seconds)
Boot your phone into recovery. Hold Up, Menu, and Power for a few seconds (until SAMSUNG appears on your screen and the phone vibrates)
Make a Nandroid backup. I can't emphasize this enough. In flashing, it's almost a certainty that one time, something will mess up. When that happens, you want to be able to restore a backup. In TWRP, just go into Backup Menu and choose where you want it (internal vs. External storage). It takes my phone a few (5-10) minutes to completely backup my data.
In TWRP, click the wipe button, then system. This will completely wipe the Rom from your phone. Doing this will allow you to get a "clean" install, without any settings or leftover files from your old Rom getting in the way. Instead, you could only wipe data (factory reset), which is good enough for most Roms. I'd still recommend a system wipe, though.
Also while in the Wipe menu, wipe Cache and Dalvik Cache.
Go back to the TWRP main menu.
Click Install, then find your Rom zip file (may have to switch from internal to external storage).
Let TWRP do it's thing.
If you're installing a TW-based Rom, chances are it had gapps already installed. If not, you should now flash the correct gapps package from goo.im. Make sure you're flashing the correct one, as if you don't, your google apps will force close upon use.
Reboot into system and give it time to boot (first boot sometimes takes a couple of minutes).
Set up your phone the way you like.
These should be the directions to follow whenever you flash a new Rom. Some Roms have the Aroma installer, so you'll have more options once you choose to flash the Rom zip, but those are typically easy to follow (and vary from Rom to Rom, so I won't be able to give you a good guide on that).
Hope this helps!
Click to expand...
Click to collapse
The rom you want to download off of Freeza's page is:
DeOdex:
Sprint Touchwiz Jelly Bean 4.1.2 L710VPBMD4 | Mirror
MD5: 77262D9D6CF1A6AF30A8981A95A75D57
Click to expand...
Click to collapse

Am I the only one with these bugs?

Hi,
I'm new here so please go easy on this "noob"
It was my first to unlock and root my phone, followed by flashing a stock ROM (Which is exactly why I rooted it)
I flashed this JB 4.2.2 stock build [ROM] [OTA][GSM] Android 4.2.2 JDQ39: Rooted | Galaxy Nexus > XDA for my Galaxy Nexus
Now...
I can't disable Next-word suggestions in the Language & Input -> Google Keyboard Settings
Also, I noticed a few seconds of lag when pressing the power button to unlock the phone, when viewing recent apps (via the soft-key), and when opening the Camera too
Also, when I choose the "Recent Apps" soft key.. it's as the app that's currently being used is minimised and the homescreen is shown without any icons
The Build came with Busybox pre-installed and now its gone after a day of using my phone... I literally can't find it.
I searched in the play store "BusyBox" and the result is 3 different apps with the same name!
Any Advice?

AMKhatri said:
Hi,
I'm new here so please go easy on this "noob"
It was my first to unlock and root my phone, followed by flashing a stock ROM (Which is exactly why I rooted it)
I flashed this JB 4.2.2 stock build [ROM] [OTA][GSM] Android 4.2.2 JDQ39: Rooted | Galaxy Nexus > XDA for my Galaxy Nexus
Now...
I can't disable Next-word suggestions in the Language & Input -> Google Keyboard Settings
Also, I noticed a few seconds of lag when pressing the power button to unlock the phone, when viewing recent apps (via the soft-key), and when opening the Camera too
Also, when I choose the "Recent Apps" soft key.. it's as the app that's currently being used is minimised and the homescreen is shown without any icons
The Build came with Busybox pre-installed and now its gone after a day of using my phone... I literally can't find it.
I searched in the play store "BusyBox" and the result is 3 different apps with the same name!
Any Advice?
Click to expand...
Click to collapse
go back to recovery, format/wipe /system partition, reflash rom.
For your reference, a good app to install bb is stephen (stericsson)'s busybox installer (play store link). Obviously, it needs root.
Next time, read the stickies.
http://forum.xda-developers.com/showthread.php?t=1812959
How do I get “root”?
If you are booted into a custom recovery (recoveries will be covered later), root is enabled by default. If you want root while booted into Android, you will need to place two files on your system partition: an “su” binary which grants root access, and a superuser app that manages that access. The two that are available are ChainsDD’s Superuser and Chainfire’s SuperSU. Usually these files are packaged up in a zip file that is flashable using a custom recovery, but they can be flashed manually using ADB. Both of these methods will be described below.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=26328017&postcount=123
As you probably noticed by now, you didn't need to flash a full "custom stock ROM" to root.

beekay201 said:
go back to recovery, format/wipe /system partition, reflash rom.
For your reference, a good app to install bb is stephen (stericsson)'s busybox installer (play store link). Obviously, it needs root.
Next time, read the stickies.
http://forum.xda-developers.com/showthread.php?t=1812959
http://forum.xda-developers.com/showpost.php?p=26328017&postcount=123
As you probably noticed by now, you didn't need to flash a full "custom stock ROM" to root.
Click to expand...
Click to collapse
Thanks for replying!
I'm totally new to this rooting &/ flashing thing, so please go easy
So, what you're saying is that I should boot into fastboot mode, wipe system partition (this will format the whole SD card right?), install the same ROM again?
I guess I'll need to install Titanium Backup to backup my apps and settings, I'll have to search for an article for the best way to do it as well..
Can I do it like this:
Open "Rom Manager", Select "Install ROM from SD Card", install it.. ???
PS: Do you have a recommendation for a better ROM, perhaps my choice of ROM wasn't correct...

AMKhatri said:
Thanks for replying!
I'm totally new to this rooting &/ flashing thing, so please go easy
So, what you're saying is that I should boot into fastboot mode, wipe system partition (this will format the whole SD card right?), install the same ROM again?
I guess I'll need to install Titanium Backup to backup my apps and settings, I'll have to search for an article for the best way to do it as well..
Can I do it like this:
Open "Rom Manager", Select "Install ROM from SD Card", install it.. ???
PSo you have a recommendation for a better ROM, perhaps my choice of ROM wasn't correct...
Click to expand...
Click to collapse
You can wipe the system partition in a custom recovery (dont know if you can with stock). And yes you could flash via ROM manager but I wouldnt recommend it. I am on XenonHD 11.1 and loving it. But roms are a personal choice so there is no 'best' ROM. Just try out.
Sent from my Galaxy Nexus using XDA Premium HD app

mrgnex said:
You can wipe the system partition in a custom recovery (dont know if you can with stock). And yes you could flash via ROM manager but I wouldnt recommend it. I am on XenonHD 11.1 and loving it. But roms are a personal choice so there is no 'best' ROM. Just try out.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
The tutorial I followed didn't mention using the ROM manager, but I had not choice.. becuase whenever I went into fastboot mode manually, it got stuck on the screen displaying Google (I waited for minutes without any luck)
How would you recommend CyanogenMod 10.1.2 against the stock 4.2.2 which I have currently?
I read these threads as well whereby they said that there is no "real" solution to the issues:
http://forum.xda-developers.com/showthread.php?t=2178962
http://forum.xda-developers.com/showthread.php?t=2363872

AMKhatri said:
Thanks for replying!
I'm totally new to this rooting &/ flashing thing, so please go easy
So, what you're saying is that I should boot into fastboot mode, wipe system partition (this will format the whole SD card right?), install the same ROM again?
I guess I'll need to install Titanium Backup to backup my apps and settings, I'll have to search for an article for the best way to do it as well..
Can I do it like this:
Open "Rom Manager", Select "Install ROM from SD Card", install it.. ???
PS: Do you have a recommendation for a better ROM, perhaps my choice of ROM wasn't correct...
Click to expand...
Click to collapse
Mr., please, read the LINK i gave you! THIS ONE ->>>> http://forum.xda-developers.com/showthread.php?t=1812959
If you read it, you'll stop thinking you need to be doing anything at this point in FASTBOOT interface! Like mrgnex says, you need to be on a custom recovery to format /system. (Have you read the link yet? By now you should know that the /system partition and the /sdcard/ (aka userdata) are 2 different things!)
mrgnex said:
You can wipe the system partition in a custom recovery (dont know if you can with stock). (...) roms are a personal choice so there is no 'best' ROM. Just try out.
Click to expand...
Click to collapse
+1
For your reference, you can't erase /system in stock recovery.
AMKhatri said:
The tutorial I followed didn't mention using the ROM manager, but I had not choice.. becuase whenever I went into fastboot mode manually, it got stuck on the screen displaying Google (I waited for minutes without any luck)
How would you recommend CyanogenMod 10.1.2 against the stock 4.2.2 which I have currently?
I read these threads as well whereby they said that there is no "real" solution to the issues:
http://forum.xda-developers.com/showthread.php?t=2178962
http://forum.xda-developers.com/showthread.php?t=2363872
Click to expand...
Click to collapse
Stop! THERE'S NO NEED FOR FASTBOOT HERE!

Thanks Guys for replying.
Yes, I read the info in the link, it was very helpful.
I'm still confused though.. "Fast boot" and "Recovery" are they the same thing?
I tried a "fix" mentioned by someone about using a live wallpaper such as "Water", I tried it and it's been 1/2 hour and it's really smooth compared to before...
Yes, I do have a custom recovery, actually I don't know why, but It seems I've got two according to ROM Manager.
It says I've got Clockwork Mod Recovery & TWRP.
I also tried going into recovery (Volume up + Down + Power) and it worked this time, when I select recovery, it goes into CWRM
I also did a bit of research about CyanogenMod 10.1.2 and from what I could gather it's liked by people a lot.
I'm guessing that definitely some time ahead it'll get all "laggy" again, Is there any reason according to you why I shouldn't install it compared to the stock 4.2.2 I have?

AMKhatri said:
Thanks Guys for replying.
Yes, I read the info in the link, it was very helpful.
I'm still confused though.. "Fast boot" and "Recovery" are they the same thing?
I tried a "fix" mentioned by someone about using a live wallpaper such as "Water", I tried it and it's been 1/2 hour and it's really smooth compared to before...
Yes, I do have a custom recovery, actually I don't know why, but It seems I've got two according to ROM Manager.
It says I've got Clockwork Mod Recovery & TWRP.
I also tried going into recovery (Volume up + Down + Power) and it worked this time, when I select recovery, it goes into CWRM
I also did a bit of research about CyanogenMod 10.1.2 and from what I could gather it's liked by people a lot.
I'm guessing that definitely some time ahead it'll get all "laggy" again, Is there any reason according to you why I shouldn't install it compared to the stock 4.2.2 I have?
Click to expand...
Click to collapse
So to get things clear:
No fastboot and recovery arent the same thing.
Vol up+down+power brings you into fast boot and not recovery.
Apparently you dont have 2 custom recoverys since you booted into cwm.
Cm10 is great. But there are many great roms out there. You can start off with cm and then (if you please) look further.
I dont see any reason to not install cm10.1.2 since a whole team built and optimized it. So basically it is a better stock.
When you think your phone is slow you should look into the custom kernels. Thats a different story which I will not begin before you want to
Sent from my Galaxy Nexus using XDA Premium HD app

mrgnex said:
So to get things clear:
No fastboot and recovery arent the same thing.
Vol up+down+power brings you into fast boot and not recovery.
Apparently you dont have 2 custom recoverys since you booted into cwm.
Cm10 is great. But there are many great roms out there. You can start off with cm and then (if you please) look further.
I dont see any reason to not install cm10.1.2 since a whole team built and optimized it. So basically it is a better stock.
When you think your phone is slow you should look into the custom kernels. Thats a different story which I will not begin before you want to
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Thanks! Now it's definitely clear!
I'll download CM10.1.2 tomorrow and will decide to install it once Stock JB 4.2.2 starts acting up again.
In the meantime I'll read on about kernels, please keep don't close this thread...yet.

clerk usdEuro
I've decided that I will test out the Rom that I have currently (4.2.2) for a few weeks, and then flash CM.
I wanted to know one more thing, Is it bad to flash ROMs to your phone every now and then?
Because I've seen people flashing different ROMs on their phone, I don't wanna damage my phone as I want it to last as long as I can make it.
(by "Bad" I mean... does it reduce the phone's life or it's hardware's life span)

AMKhatri said:
I've decided that I will test out the Rom that I have currently (4.2.2) for a few weeks, and then flash CM.
I wanted to know one more thing, Is it bad to flash ROMs to your phone every now and then?
Because I've seen people flashing different ROMs on their phone, I don't wanna damage my phone as I want it to last as long as I can make it.
(by "Bad" I mean... does it reduce the phone's life or it's hardware's life span)
Click to expand...
Click to collapse
No it can't. I was a flashaholic (until I discovered XenonHD) and my phone didn't got worse. Only overclocking the CPU and gpu can affect the life of the CPU or gpu (or both XD). Just do a fresh install everytime and read the post of the ROM of your choice to see what to do to get it working optimally. If you have any problems just ask.
Sent from my Galaxy Nexus using XDA Premium HD app

mrgnex said:
No it can't. I was a flashaholic (until I discovered XenonHD) and my phone didn't got worse. Only overclocking the CPU and gpu can affect the life of the CPU or gpu (or both XD). Just do a fresh install everytime and read the post of the ROM of your choice to see what to do to get it working optimally. If you have any problems just ask.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Thanks...
I'll flash CM in a week or two, as I'm on a tight schedule currently, and I also wanna note down the average battery time I get out of 4.2.2

So... since 4.3 is now out, I was thinking it'd be better for me to flash it other than anything else.
I'll most probably download the stock rom from:
https://developers.google.com/android/nexus/images#yakjujwr66v
So far I came across this thread having the steps to flash 4.3
http://forum.xda-developers.com/showthread.php?t=2377307
But I wanna flash it and lose my data, so that it's as fresh as it can be...
Will that work if I use "wugfresh root toolkit"?

AMKhatri said:
So... since 4.3 is now out, I was thinking it'd be better for me to flash it other than anything else.
I'll most probably download the stock rom from:
https://developers.google.com/android/nexus/images#yakjujwr66v
So far I came across this thread having the steps to flash 4.3
http://forum.xda-developers.com/showthread.php?t=2377307
But I wanna flash it and lose my data, so that it's as fresh as it can be...
Will that work if I use "wugfresh root toolkit"?
Click to expand...
Click to collapse
With the stock package there is no need for a toolkit.
Hell, there's no reason for a toolkit any time.
Sent from my Galaxy Nexus

Pirateghost said:
With the stock package there is no need for a toolkit.
Hell, there's no reason for a toolkit any time.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
What was I thinking...
I apologize guys... I guess I wasn't thinking straight as its past midnight here...
So just to clarify stuff so that I don't end up doing something wrong:
-> Head into Recovery Mode (with usb debugging enabled... connect usb cable to phone and pc)
-> Wipe System
-> Wipe Cache
-> Install from SD card (select .zip file)
right?
Also, I performed a backup of the applications I have via Titanium Backup, They'll work on 4.3 when I restore them right? or do you recommend downloading them from the play store again?
Sorry for being such a noob, and Thanks for your responses!

backup everything from your /sdcard to your computer, titanium backups and a nandroid
the google stock package is NOT flashable in CWM/TWRP
if you follow the GOOGLE instructions it WILL wipe your device (remember that backup you made of everything?)
alternatively you can make sure and have adb/fastboot working on your computer properly, extract all the files out of the zip (including the tar.gz located inside), and in recovery, do a factory reset, then boot to fastboot, fastboot flash system and boot ....
as for Titanium Backup, there is a work around to get it working on 4.3, but root is lacking full power.

Pirateghost said:
backup everything from your /sdcard to your computer, titanium backups and a nandroid
the google stock package is NOT flashable in CWM/TWRP
if you follow the GOOGLE instructions it WILL wipe your device (remember that backup you made of everything?)
alternatively you can make sure and have adb/fastboot working on your computer properly, extract all the files out of the zip (including the tar.gz located inside), and in recovery, do a factory reset, then boot to fastboot, fastboot flash system and boot ....
as for Titanium Backup, there is a work around to get it working on 4.3, but root is lacking full power.
Click to expand...
Click to collapse
Thanks!
I'm now on Android 4.3
I'm full of excitement atm :victory:
I took a backup of my apps using titanium backup, I installed it but can't use it, it says I need root (which I already had before).
I read online somewhere that I need to root again, but I don't wanna lose all my data/ apps I installed again...
Any ideas?
If I use Wugfresh Nexus Root Toolkit... will I lose my data?
Thanks for the continued support!

AMKhatri said:
Thanks!
I'm now on Android 4.3
I'm full of excitement atm :victory:
I took a backup of my apps using titanium backup, I installed it but can't use it, it says I need root (which I already had before).
I read online somewhere that I need to root again, but I don't wanna lose all my data/ apps I installed again...
Any ideas?
If I use Wugfresh Nexus Root Toolkit... will I lose my data?
Thanks for the continued support!
Click to expand...
Click to collapse
Seriously, how hard can it be for you people to waste 5, 5!!! minutes to browse the forums.
http://forum.xda-developers.com/showthread.php?t=2377318

Thanks!
According to a friend's recommendation I used Wugfresh Nexus Root Toolkit to Root, and surprisingly didn't lose any of my data!
Once again, Thanks for all the help everyone... You've all been quite helpful.