Database Users

stock rooted gingerbread??

I am using Froyo stock and rooted right now (my phone is not stable on any roms for some reason). So should i just put my phone back to stock and update then reroot? Or is there a better way? I cant seem to find the stock rom to flash.

You can remove the root and then go to GB and then re-root.
Sent from my SPH-D700 using XDA App

Just remove the root? do you mean flash back to stock using odin? I dont know how else to do it.
Sent from Epic 4g on XDA Premium

NissanNick said:
Just remove the root? do you mean flash back to stock using odin? I dont know how else to do it.
Sent from Epic 4g on XDA Premium
Click to expand...
Click to collapse
That's what I did, I used Odin to flash back to stock EC05 and am waiting for the OTA, then I'll probably reroot when a reliable method has been worked out. It seems right now there's a lot of workarounds to get root and CWM to stay.

Here is how I did it:
Odin to stock EC05
Download update.zip to SD Card and install through samsung stock recovery
Odin mkasic's kernel followed by CWM 3.1.0.1 Purple
Flash SU.zip, GPS-Fix.zip, EC05AdFree.zip
Advanced Restore of /Data through CWM
Up and running with all my existing settings, has been solid for 24hrs with no fc's.

If he's stock EC05 and rooted then you can just use the one click root windows application and remove the root. Then apply the EI22 update.zip and then do the current root method for EI22. He doesn't have to lose everything if he's on stock froyo.
Sent from my SPH-D700 using XDA App

steveo314 said:
If he's stock EC05 and rooted then you can just use the one click root windows application and remove the root. Then apply the EI22 update.zip and then do the current root method for EI22. He doesn't have to lose everything if he's on stock froyo.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Never heard of this before...how can one click root remove root? I used it to put root on!

rando991 said:
That's what I did, I used Odin to flash back to stock EC05 and am waiting for the OTA, then I'll probably reroot when a reliable method has been worked out. It seems right now there's a lot of workarounds to get root and CWM to stay.
Click to expand...
Click to collapse
It will ALWAYS be a workaround solution. So there is no need to wait for that specific aspect... since the wait would be infinite. The problem with recovery not sticking has to do with the new stock kernel. The "workarounds" require a modified kernel.

rando991 said:
Never heard of this before...how can one click root remove root? I used it to put root on!
Click to expand...
Click to collapse
1st use this, there is an un-root option:
http://forum.xda-developers.com/showthread.php?t=803682
then you can load the update.zip in stock recovery
then to get back on root do this:
http://forum.xda-developers.com/showthread.php?t=1339478

I am on stock with bloat removed. Will this work as well or will I have to odin to EC05 and lose everything? I figured I would have to odin back first.
steveo314 said:
If he's stock EC05 and rooted then you can just use the one click root windows application and remove the root. Then apply the EI22 update.zip and then do the current root method for EI22. He doesn't have to lose everything if he's on stock froyo.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse

bgreiwe said:
I am on stock with bloat removed. Will this work as well or will I have to odin to EC05 and lose everything? I figured I would have to odin back first.
Click to expand...
Click to collapse
If all you've done is rooted and removed the bloat it'll work so you don't have to loose everything.
Sent from my SPH-D700 using XDA App

jat255 said:
The easiest way to do it, I think, is to do the manual update from stock EC05 to stock EI22. I did this procedure and have had zero problems. I used heimdall personally because I run Linux.
Once you have your stock GB up and running, odin/heimdall your cwm or acs recovery.bin and hold down the three button combo while it auto-reboots.
You'll get into the custom recovery, and you can flash su.zip and anything else you'd like while you're there.
Reboot the phone, and you should see that you're rooted just fine. The problem now is that there is a script that gets run on every startup called "/system/etc/install-recovery.sh" that re-installs the stock recovery on every boot. Now that you're rooted, use whatever means you'd like (file expert, terminal emulator, etc.) to get into /system/etc/ and delete that file.
You'll have to do one final odin/heimdall of the custom recovery.bin, but after that, you should be rooted and have a permanent custom recovery on stock EI22!
Sure, it's a workaround, but it's not that hard, and it works! It's easy to let the devs do everything for us, but every now and again it's good to get into your device and figure out the way things work on your own.
Good luck!
Click to expand...
Click to collapse
Thanks followed this guide made cwm 3.1.0.1 and root sticked. I am like many others likes to have everything as stock and as little changes so i didnt want to flash any custom kernel. This method will retain everything from stock just minus 1 script.
This is my revised method which only need to flash cwm 3.1.0.1 in odin 2 times and it will stick there forever.
Comming from a bone stock EI22
1. flash cwm 3.1.0.1 with reboot checked off (nothing check), put file in pda.
http://drockstar.devphone.org/EpicTar/cwm3.1.0.1.tar.md5
2. when its done, unplug data cable and pull out battery.
without rebooting system.
3. vol down, camera, power, to get into cwm recovery
4. install su.zip and reboot the phone (now you have root)
http://downloads.androidsu.com/superuser/su-3.0-efgh-signed.zip
5. install es explorer from market
5a. under menu/setting check the box root explorer and mount file system
5b. browse into phone /system/etc/install-recovery.sh
delete "install-recovery.sh" script or move it to your sd card if you want to retain a copy.
(long press into that file and delete option will come out)
6. shut off your phone
7. odin cwm 3.1.0.1 again with reboot checked
8. restart, cwm and root will be stick forever.
credit to jat255

rando991 said:
That's what I did, I used Odin to flash back to stock EC05 and am waiting for the OTA, then I'll probably reroot when a reliable method has been worked out. It seems right now there's a lot of workarounds to get root and CWM to stay.
Click to expand...
Click to collapse
Odin back to DG27. It should force the update.

lbe said:
Thanks followed this guide made cwm 3.1.0.1 and root sticked. I am like many others likes to have everything as stock and as little changes so i didnt want to flash any custom kernel. This method will retain everything from stock just minus 1 script.
This is my revised method which only need to flash cwm 3.1.0.1 in odin 2 times and it will stick there forever.
Comming from a bone stock EI22
1. flash cwm 3.1.0.1 with reboot checked off (nothing check), put file in pda.
http://drockstar.devphone.org/EpicTar/cwm3.1.0.1.tar.md5
2. when its done, unplug data cable and pull out battery.
3. vol down, camera, power, to get into cwm recovery
4. install su.zip and reboot the phone (now you have root)
http://downloads.androidsu.com/superuser/su-3.0-efgh-signed.zip
5. install es explorer from market
5a. under menu/setting check the box root explorer and mount file system
5b. browse into phone /system/etc/install-recovery.sh
delete "install-recovery.sh script"
(long press into that file and delete option will come out)
6. shut off your phone
7. odin cwm 3.1.0.1 again
8. restart, cwm and root will be stick forever.
credit to jat255
Click to expand...
Click to collapse
I think it would be a good idea to copy that script and put it somewhere instead of deleting it just in case you want to go back to bone stock in the future (who knows an ICS update LOL). Once copied, then delete the file.
Sent from my SPH-D700 using XDA App

adelmundo said:
I think it would be a good idea to copy that script and put it somewhere instead of deleting it just in case you want to go back to bone stock in the future (who knows an ICS update LOL). Once copied, then delete the file.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
you can odin the ec05 stock rom and update to ei22 and it will put that file back in. doesnt hurt to move that file to your sd card i guess.

Here is the stock EC05 ROM you are looking for. It formats your phone back to the RFS file system, but keeps your phone rooted and with CWM3.1.0.1
There is also a link on that page if you want to make your recovery go back to stock as well.
If you want to just ODIN and get onto EI22 stock, check this out. It's still RFS but it's deodexed, so a little faster. Comes with EC05 modem, which seems to still be more stable than the EI22, especially when it comes to Wifi.
EDIT: I take that back, that EI22 isn't so stock anymore, but it's closest you're going to get to a stock-ish EI22 that actually functions.

Odin back to stock EC05, update.zip, modified kernel patch and cwm the su.zip worked for me.
One question though.. stock OTA/update.zip is ODEXED, correct? Can I deodex what I have or do I need to re-flash a deodex stock rom and would I do it before or after uninstalling bloat?

jfg69 said:
Odin back to stock EC05, update.zip, modified kernel patch and cwm the su.zip worked for me.
One question though.. stock OTA/update.zip is ODEXED, correct? Can I deodex what I have or do I need to re-flash a deodex stock rom and would I do it before or after uninstalling bloat?
Click to expand...
Click to collapse
OTA stock is Odexed, correct. Deodexing yourself takes some time... it's not just removing files, you'll have to edit quite a few things. If you're going to deodex your system using the ROM, you just ODIN it from wherever you are now. It will erase everything, like starting from scratch. But you can restore your data on top of it if you backed it up first.

4.1.2 altered build.prop file can't receive OTA update

A while back I altered my build.prop file and accidently deleted it. I didn't make a backup so I restored it with one that someone posted and I haven't had any problems.
However since I did that, the OTA update that I got notified for did not install.
My boot loader is unlocked and I am rooted with stock recovery.
How can I update to 4.1.2 manually and still keep root?
I understand there are plenty of posts about this but everyone has a different problem and I'm just trying to get the correct information. Thanks for any help.
Sent from my Nexus 7 using xda app-developers app

somerandomname1 said:
A while back I altered my build.prop file and accidently deleted it. I didn't make a backup so I restored it with one that someone posted and I haven't had any problems.
However since I did that, the OTA update that I got notified for did not install.
My boot loader is unlocked and I am rooted with stock recovery.
How can I update to 4.1.2 manually and still keep root?
I understand there are plenty of posts about this but everyone has a different problem and I'm just trying to get the correct information. Thanks for any help.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Download the OTA update JZO54K-fromJRO03D
Download SuperSu or Superuser
put the OTA update and SuperSu or Superuser in a in your /sdcard/Download directory
Flash ClockworkMod recovery from fastboot
http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.1.0-grouper.img
Code:
> fastboot flash recovery recovery-clockwork-touch-6.0.1.0-grouper.img
Boot recovery from the fastboot menu
Install the OTA update, then install SuperSu or Superuser.

Thanks man appreciate it.
Sent from my Nexus 7 using xda app-developers app

this actually didn't work...everything was working fine, but it aborted and mentioned my build.prop file as the reason why...

somerandomname1 said:
this actually didn't work...everything was working fine, but it aborted and mentioned my build.prop file as the reason why...
Click to expand...
Click to collapse
Here's the build.prop from JRO03D load that up and try again. If that fails, you can manually update to 4.1.2 from the factory image without modifying user data.

this worked my friend, thanks.

I'm having the exact same problem, same circumstances, down to the update not taking because I accidentally deleted a system file, except the file in question is the gmail .odex file because I deleted that to install the unreleased gmail 4.2 app. Any help?
EDIT: Fixed thanks to user comminus via PM. Cheers.

Can't update to 4.2

Tried to update to 4.2 today used ota with rootkeeper and tried to flash zip with twrp keep getting error md5 won't check right with flash and ota update gets error and boot me to twrp recovery any help would be appreciated
Sent from my Nexus 7 using XDA Premium HD app

ricobudz123 said:
Tried to update to 4.2 today used ota with rootkeeper and tried to flash zip with twrp keep getting error md5 won't check right with flash and ota update gets error and boot me to twrp recovery any help would be appreciated
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Re-download the image your trying to flash.
As an MD5 is a checksum, meaning if the MD5 isn't valid something has gone wrong with the download, hense the Check Sum is incorrect.

ricobudz123 said:
Tried to update to 4.2 today used ota with rootkeeper and tried to flash zip with twrp keep getting error md5 won't check right with flash and ota update gets error and boot me to twrp recovery any help would be appreciated
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Had the same problem myself.
The 4.2 update won't install if you changed anything in /system
An example of how you might have done that is used titanium backup to uninstall a system app or use the integrate updates of system apps into ROM option.
The solution is to restore what has changed. For example, if you removed a system app that came with your nexus such as that Korean keyboard app (which a lot of people seem to have done) you need to somehow get a hold of that apk and put it back into /system/apps or the update will not install.
Sent from my Nexus 7 using Tapatalk 2

Can confirm that any changes to the system in any way will stop the device updating via ota.
I moved apps and froze some installed some custom changes to system ui etc the normal stuff you do when rooted. The update downloaded fine but would not install.
Thankfully I had a cwm stock backup,hid root using voodoo ota rootkeeper then was able to update to 4.2 then restore all apps and data using titanium backup.
Sent from my Nexus 7 using xda premium

Thanks for the help I just used wugfresh and the tgz file for 4.2 wiped everything but no worries there. Got 4.2 running all I have to do is root
Sent from my Nexus 7 using XDA Premium HD app

Stagefright Update Patch A5-CHL Virgin Mobile USA

I just received the Stagefright update patch this morning. The notification mentioned performance and stability improvements along with the Stagefright patch. For those of you wanting to dig through it and try to port it to a flashable zip for rooted users, here it is.
https://drive.google.com/file/d/0B0G3PnBHJjXmdno0cjhod3NNOTA/view?usp=sharing
I am currently running stock, unrooted but with TWRP installed. I had to extract the recovery from the zip file and flash via fastboot as the patch wouldn't flash with TWRP. It took a while to boot due to rewriting the cache, but it's finally up and running. I don't see real noticeable differences, either in look or performance. As long as the patch works, guess I'm OK.

Is there anyway to stop the update notifications?
Sent from my 710C using Tapatalk

I had it too, a5_dwg .. but I'm rooted with TWRP xD
so I'm ganna wait for the flashable zip if anyone still care about this phone anyway to do it

Also rooted and waiting for a .zip

YouArePoop said:
Is there anyway to stop the update notifications?
Sent from my 710C using Tapatalk
Click to expand...
Click to collapse
I froze the updater apk with link2sd....that seemed to do the trick
Sent from my 710C using Tapatalk

Anyone have an unrooted stock lollipop twrp or cwm backup? A5CHL. I want to OTA to this version but I can't go back to stock. the official lollipop RUU keeps failing saying, "RomTool.exe has stopped working." then I have to fastboot reboot to the older version.

I looked in the update, and it appears to be a bunch of patches. I have two ideas for how to make it work:
1 - Figure out how it checks the recovery version and chop that part out.
2 - make a copy of /system on my sdcard, change every instance of /system to /[sdcard-path]/system in binary-script, run script, then repack that as an update.
Sound about right, anyone? I'm tempted to try this out.
Sent from my 710C using XDA Free mobile app

The RUU.exe from HTC.com for a5_chl now includes this patch. So if people don't mind wiping their phone running the .exe and going completely back to stock, the option's there. My laptop still says, "romtool.exe has stopped working." So I'm screwed either way, an OTA or RUU.

Root VZW Dev Edition on 5.1

So today I flashed my VZW Developer edition Moto X back to stock 4.4.4 to download the 5.1 OTA update. I got everything installed an am now trying to obtain root again. Since I have the Dev edition, my bootloader is unlocked so theoretically, I should just be able to flash superuser to get root, right?
Well, I installed my custom recovery TWRP and downloaded the lastest recovery flashable supersu zip file and flashed the zip. When I reboot and open SuperSU it tells my that SU binaries are not installed.
I tried installing both ChainsDD and Clockworkmods version of Superuser as well as SuperSU with TWRP and clockwork recoveries and nothing is working.
Can anyone help me obtain root again?
Thanks!

I flashed this in twrp and it work.
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133

Have you checked this thread out? http://forum.xda-developers.com/showthread.php?t=3140217
[HOW TO] How to Root 5.1 with (unlocked bootloader)
Sent from my XT1575

Thanks guys. Turns out the version of SuperSU I downloaded was not the latest version. I downloaded the beta version and that worked great. Thanks!
Sent from my XT1060 using Tapatalk

dgwood12 said:
So today I flashed my VZW Developer edition Moto X back to stock 4.4.4 to download the 5.1 OTA update. I got everything installed an am now trying to obtain root again. Since I have the Dev edition, my bootloader is unlocked so theoretically, I should just be able to flash superuser to get root, right?
Well, I installed my custom recovery TWRP and downloaded the lastest recovery flashable supersu zip file and flashed the zip. When I reboot and open SuperSU it tells my that SU binaries are not installed.
I tried installing both ChainsDD and Clockworkmods version of Superuser as well as SuperSU with TWRP and clockwork recoveries and nothing is working.
Can anyone help me obtain root again?
Thanks!
Click to expand...
Click to collapse
Would you be able to point me to a thread with the steps to flash stock. I haven't done this since I got the phone and it's true what they say. "If you don't use it you lose it." I just want to get rid of this constant reminder that I have an update to install.
Thanks!!

whopua said:
Would you be able to point me to a thread with the steps to flash stock. I haven't done this since I got the phone and it's true what they say. "If you don't use it you lose it." I just want to get rid of this constant reminder that I have an update to install.
Thanks!!
Click to expand...
Click to collapse
visit -> http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425 read post 1 and 2... But Post 2 is mostly what you want.

Anybody figure out to get tether to work?

If you are on Verizon network, all you have to do is add net.tethering.noprovisioning=true to your build.prop. You'll need root for that, and can edit build.prop with any text editor/ root explorer. I can confirm that it works fine with VZW LP 5.1. The benefit of doing this simple procedure instead of using a Xposed module is that you can tethering without having root or Xposed installed. This is especially useful of you plan on using Android Pay which will not work if the phone is rooted.
Sent from my DROID MAXX using Tapatalk

Johnny Wong said:
If you are on Verizon network, all you have to do is add net.tethering.noprovisioning=true to your build.prop. You'll need root for that, and can edit build.prop with any text editor/ root explorer. I can confirm that it works fine with VZW LP 5.1. The benefit of doing this simple procedure instead of using a Xposed module is that you can tethering without having root or Xposed installed. This is especially useful of you plan on using Android Pay which will not work if the phone is rooted.
Sent from my DROID MAXX using Tapatalk
Click to expand...
Click to collapse
Thanks, worked perfect!

KidJoe said:
visit -> http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425 read post 1 and 2... But Post 2 is mostly what you want.
Click to expand...
Click to collapse
Real quick before I get started. It seems like option 6 is the right one. I am rooted really just for tether, root explorer, and call master. How do I check to make sure I didn't download Xposed? I don't think I did but I want to be sure first. I haven't tinkered with this since I got it.
Thanks again!!

how did you flash back to 4.4.4?

Johnny Wong said:
If you are on Verizon network, all you have to do is add net.tethering.noprovisioning=true to your build.prop. You'll need root for that, and can edit build.prop with any text editor/ root explorer. I can confirm that it works fine with VZW LP 5.1. The benefit of doing this simple procedure instead of using a Xposed module is that you can tethering without having root or Xposed installed. This is especially useful of you plan on using Android Pay which will not work if the phone is rooted.
Sent from my DROID MAXX using Tapatalk
Click to expand...
Click to collapse
Android Pay works with root. In order to setup cards you have to uncheck "enable supersu" within supersu first, then setup your cards in Android Pay, then you can go back to supersu and re-enable it by checking the box.
Sent from my Nexus 6 using XDA Free mobile app

whopua said:
Real quick before I get started. It seems like option 6 is the right one. I am rooted really just for tether, root explorer, and call master. How do I check to make sure I didn't download Xposed? I don't think I did but I want to be sure first. I haven't tinkered with this since I got it.
Thanks again!!
Click to expand...
Click to collapse
option 6 only flashes stock recovery.
How did you tether? If you rooted to tether, you likely modified something. You'll need to undo that. Unless you used the Wifi Tether for Root APK, in which case you should be fine with just stock recovery back on there.

Are people getting OTA update on Verizon. It sure sounds like it but I've not got any notification

SR3TLAW said:
Are people getting OTA update on Verizon. It sure sounds like it but I've not got any notification
Click to expand...
Click to collapse
Yes they are, but its rolling out in phases or waves.. so it could be anywhere from a couple of days to a couple of weeks until your phone gets it.
If you can't wait, copies of the OTA Zip files needed were posted in the "waiting room" thread, which you can copy to your phone, and manually install via stock recovery. (Of course just like all past OTA's, your phone has to be stock, stock recovery, no Xposed, etc or the OTA zip wont install)

KidJoe said:
Yes they are, but its rolling out in phases or waves.. so it could be anywhere from a couple of days to a couple of weeks until your phone gets it.
If you can't wait, copies of the OTA Zip files needed were posted in the "waiting room" thread, which you can copy to your phone, and manually install via stock recovery. (Of course just like all past OTA's, your phone has to be stock, stock recovery, no Xposed, etc or the OTA zip wont install)
Click to expand...
Click to collapse
Thank-you

KidJoe said:
option 6 only flashes stock recovery.
How did you tether? If you rooted to tether, you likely modified something. You'll need to undo that. Unless you used the Wifi Tether for Root APK, in which case you should be fine with just stock recovery back on there.
Click to expand...
Click to collapse
I am using WiFi Tether. So option 6 will unroot my device for the OTA? Also I went to the motorola software image page and they only had KXA21.12-L1.26.1-1 available. I have KXA21.12-L1.26-3. Will this end up being a problem? I cannot find the recovery image for 26-3 anywhere... yet.

whopua said:
I am using WiFi Tether. So option 6 will unroot my device for the OTA? Also I went to the motorola software image page and they only had KXA21.12-L1.26.1-1 available. I have KXA21.12-L1.26-3. Will this end up being a problem? I cannot find the recovery image for 26-3 anywhere... yet.
Click to expand...
Click to collapse
It will be a problem, I experienced it. Fortunately somebody in the waiting room thread posted a link to the stock L26 version of 4.4.4 and that got me my ota. With the L26.1 recovery image I couldn't get past the L26.4 ota on my DE to get the 5.1 ota.
Sent from my Nexus 6 using XDA Free mobile app

Fly135s said:
It will be a problem, I experienced it. Fortunately somebody in the waiting room thread posted a link to the stock L26 version of 4.4.4 and that got me my ota. With the L26.1 recovery image I couldn't get past the L26.4 ota on my DE to get the 5.1 ota.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Is there a link available? I'm trying to get my ducks in a row before I make any attempt.
Thanks

whopua said:
Is there a link available? I'm trying to get my ducks in a row before I make any attempt.
Thanks
Click to expand...
Click to collapse
Keep in mind this was done on my XT1060 developer edition with the bootloader unlocked.
http://forum.xda-developers.com/showthread.php?p=62855579
[Waiting Room]Verizon XT1060 Lollipop (5.1) OTA & FXZ thread
http://forum.xda-developers.com/showthread.php?p=62874513
[Waiting Room]Verizon XT1060 Lollipop (5.1) OTA & FXZ thread
I used the second link in this post labeled "here"
Here's good instructions for dirty flashing to stock, I used option 5:
http://mark.cdmaforums.com/MotoX-ReturnToStock.html
Once I had the 5.1 ota I ensured I had SuperSU 2.46 zip in my download folder. Then I flashed TWRP 2.8.7.0 and immediately rebooted into TWRP recovery and installed the SuperSU zip and had root.
Sent from my Nexus 6 using XDA Free mobile app
---------- Post added at 01:06 PM ---------- Previous post was at 01:05 PM ----------
Fly135s said:
Keep in mind this was done on my XT1060 developer edition with the bootloader unlocked.
http://forum.xda-developers.com/showthread.php?p=62855579
[Waiting Room]Verizon XT1060 Lollipop (5.1) OTA & FXZ thread
http://forum.xda-developers.com/showthread.php?p=62874513
[Waiting Room]Verizon XT1060 Lollipop (5.1) OTA & FXZ thread
I used the second link in this post labeled "here"
Here's good instructions for dirty flashing to stock, I used option 5:
http://mark.cdmaforums.com/MotoX-ReturnToStock.html
Once I had the 5.1 ota I ensured I had SuperSU 2.46 zip in my download folder. Then I flashed TWRP 2.8.7.0 and immediately rebooted into TWRP recovery and installed the SuperSU zip and had root.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
There's also a link to the full 5.1 sbf in the waiting room thread.
Sent from my Nexus 6 using XDA Free mobile app