Database Info

How to root my Skyrocket 2.3.6 version

So I can use Titanium backup to freeze things to make the battery last longer? I am about to go back to a iphone if I can't get this battery life situation resolved.

Go here http://forum.xda-developers.com/showthread.php?t=1340526 you need to use that method to root 2.3.6 instructions and files needed are in that thread. Its very easy

Where else can i dl the super one click the link isn't working
Sent from my SAMSUNG-SGH-I727 using XDA App

The one click root will not work on 2.3.6 u need to use the method above

silver03wrx said:
The one click root will not work on 2.3.6 u need to use the method above
Click to expand...
Click to collapse
Silver03wrx: any idea if we can safely unroot with SuperOneClick 2.2 on 2.3.6 if we rooted with it on 2.3.5?
Sent from my SAMSUNG-SGH-I727 using XDA App

I doubt it works. It wont root 2.3.6 so i dont see why it would unroot. If you want to unroot probobly have to odin the stock 2.3.5 tar and take the ota update to unroot

Noob clarification re "internal sd" from Melvins Root guide
When he says " your internal SD",that means NOT the SD card?.. right? Sorry for the request for clarification!

There is an internal 16gb sd card that is not removeable. There is also and external sd slot that is r emoveable

silver03wrx said:
There is an internal 16gb sd card that is not removeable. There is also and external sd slot that is r emoveable
Click to expand...
Click to collapse
Thanks Silver, perhaps I was not being complete in my question? I know that there are both, but my question was specifically related to rooting. In his post " *Put the Superuser .zip file on your internal SD" from these instructions" http://forum.xda-developers.com/showthread.php?t=1311194".
I think it means that you put the. Zip file on the phones internal memory & NOT the removable SD card?

Yes you are correct sir

Thanks SILVER.... it just seemed a little ambiguous, and for a noob, that could be dangerous. ...you were "thanked" .

Uhm, on Melvin's post of Oct 19th...he says to put the Superuser zip on the INTERNAL SD....BUT on Copperhed's post of Nov 10th....he says to put the Superuser file on the EXTERNAL SD? I would imagine that there is something important about where it is located on the phone?
I was pretty sure that I was not losing my mind, I just had to find where I saw the discrepancy

silver03wrx said:
Go here http://forum.xda-developers.com/showthread.php?t=1340526 you need to use that method to root 2.3.6 instructions and files needed are in that thread. Its very easy
Click to expand...
Click to collapse
I just want to root and leave everything stock. I don't feel like dealing with all that custom stuff. Is there a way to just flash a rooted stock rom with odin and be done with it. I'm on 2.3.6 btw

cbs1507 said:
I just want to root and leave everything stock. I don't feel like dealing with all that custom stuff. Is there a way to just flash a rooted stock rom with odin and be done with it. I'm on 2.3.6 btw
Click to expand...
Click to collapse
The GS2 doesn't support booting recoveries via fastboot, so the only way to root (short of using a rooting tool) is to install a custom recovery like TWRP or CWM via Odin, and then root the system from within the recovery. You can restore the stock recovery if you want, but I don't know of any other clean methods to root.
Also, you are aware that there is an official (Samsung provided) Jelly Bean ROM for the GS2, right? While that doesn't get you "up to date", it at least gets you on a 4.x stream, which will dramatically improve app support on the Play Store.

jshamlet said:
The GS2 doesn't support booting recoveries via fastboot, so the only way to root (short of using a rooting tool) is to install a custom recovery like TWRP or CWM via Odin, and then root the system from within the recovery. You can restore the stock recovery if you want, but I don't know of any other clean methods to root.
Also, you are aware that there is an official (Samsung provided) Jelly Bean ROM for the GS2, right? While that doesn't get you "up to date", it at least gets you on a 4.x stream, which will dramatically improve app support on the Play Store.
Click to expand...
Click to collapse
I can't just flash a rooted stock file with odin? I don't understand all that other stuff you're saying/

cbs1507 said:
I can't just flash a rooted stock file with odin? I don't understand all that other stuff you're saying/
Click to expand...
Click to collapse
There may be a way to install a pre-rooted image from Odin, but most folks do it from a recovery. Fortunately, if you can figure out how to just install the recovery, it will be able to root whatever you have installed, and is a heck of a lot safer than messing with the OS image. Unfortunately, how that happens depends on the recovery, but in most cases it will over you the option to fix the su binary when you reboot.
I won't repeat the steps here, as there are several guides for installing recoveries via ODIN. I will point you to the TWRP repository, however -> https://dl.twrp.me/skyrocket/

So let me get this straight, if I flash a normal stock Rom from a recovery it will automatically root it? What is a recovery? Is that the same thing as download mode? I'll try to find a thread, but of course if u could post a the ad link I would appreciate it.

Hi how to upgrade 2.3.6 to latest version andriod samsung galaxy s2 at&t i727 can u please give me instructions

How to upgrade to new latest Asus firmware through custom recovery

Check the device firmware type by going to Setting - about tablet - built number
Download the right firmware pack for your device.
http://www.asus.com/Tablet/Transformer_Pad/ASUS_Transformer_Pad_Infinity_TF700T/#download
Now extract the zip file and you will have another zip file.
Rename that zip file as "EP201_768_SDUPDATE" and place it to an external sd card if you do not have a custom recovery. If you are rooted and unlocked plus you have a custom recovery you don't need to rename it you can place it in internal sd is well.
Now turn off your device. Hold power button including the volume down button and enter custom recovery. For stock recovery it should detect it automatically and will install. once in custom recovery clear your cache and install the file with the name above or whatever name you have. once installation is complete. reboot the system be patient and you have the latest update.
You can obtain root easily using this method.
Just download the DebugfsRoot_Generic_v2.3.zip file from here
http://forum.xda-developers.com/show....php?t=1706588
extract the content and run RootDebugfs, then follow the on screen instruction and you will have root.
Make sure you have USB debugging on.
To get custom recovery. Download goomanager from playstore and you can install TWRP recovery from the option list. which is Option - install OpenRecoveryScript.
I am not responsible if you mess up your device. do these at your own risk. Nonetheless these steps work perfectly for me.

Renaming is not needed.

lafester said:
Renaming is not needed.
Click to expand...
Click to collapse
Exactly thats for people without custom recovery

Isn't this already covered here? http://forum.xda-developers.com/showthread.php?t=1833212
Sent from my EVO using xda premium

rizanx said:
Exactly thats for people without custom recovery
Click to expand...
Click to collapse
does the update push the stock recovery as well?
and root is lost right?

Yes and yes.
Sent from my HTC One X using xda premium

odeccacccp said:
does the update push the stock recovery as well?
and root is lost right?
Click to expand...
Click to collapse
Yes you will lose root.
But you can obtain root easily using this method.
Just download the DebugfsRoot_Generic_v2.3.zip file from here
http://forum.xda-developers.com/showthread.php?t=1706588
extract the content and run RootDebugfs, then follow the on screen instruction and you will have root.
oh and make sure you have USB debugging on.

sorry for the mix up. yes you do lose recovery. Download goomanager from playstore and you can install TWRP recovery from the option list.

rizanx said:
Through custom recovery stock recovery is not pushed! you will still have custom recovery. You will only lose root.
Click to expand...
Click to collapse
Wrong, flashing an official rom will make you loose the custom recover too, you will have a clean stock rom once you do that. AND also this thread has nothing to share with the development forum.

Pretoriano80 said:
Wrong, flashing an official rom will make you loose the custom recover too, you will have a clean stock rom once you do that. AND also this thread has nothing to share with the development forum.
Click to expand...
Click to collapse
+1 You WILL lose custom recovery with this method. This has all been covered before...
Sent from my EVO using xda premium

Pretoriano80 said:
Wrong, flashing an official rom will make you loose the custom recover too, you will have a clean stock rom once you do that. AND also this thread has nothing to share with the development forum.
Click to expand...
Click to collapse
Thanks for clear up.

MysticMgcn said:
Isn't this already covered here? http://forum.xda-developers.com/showthread.php?t=1833212
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Where in there? Can;t find it?
1) If I am on a custom ROM can I flash the new update or I have to go back to STOCK first?
2) What's the big deal with loosing CWR and Root, it takes like 2 min to put it back, I mean there is another way to not loose it?
Thanks

I also have a question! Will this allow for OTA updates even if our bootloader is unlocked? And will we be able to flash the JB update from ASUS manually if not? Anyone know?

GRIM1337 said:
I also have a question! Will this allow for OTA updates even if our bootloader is unlocked? And will we be able to flash the JB update from ASUS manually if not? Anyone know?
Click to expand...
Click to collapse
No. when you unlocked it clearly stated no more ota updates for you.
Yes. of course you can flash manually just like any other rom.

odeccacccp said:
Where in there? Can;t find it?
1) If I am on a custom ROM can I flash the new update or I have to go back to STOCK first?
2) What's the big deal with loosing CWR and Root, it takes like 2 min to put it back, I mean there is another way to not loose it?
Thanks
Click to expand...
Click to collapse
You don't need to have stock rom. As long as you have the stock kernel your ok. You will of course lose custom recovery but its easy to download again as i have mentioned in my first post.
There is a lengthy way to do this. But why do that when it takes you literally 2 minute to root it with DebugfsRoot .
Hope it went well for you.

[Q] HTC One S Root OTA Update Questions

Hello Everyone,
As of today, my phone received the new OTA Update for my HTC One S. However, obviously I cannot update due to my phone being rooted. As a person who is still relatively new with rooting (about a month rooted with my phone-first time), I have a couple questions.
First and foremost, have you guys enjoyed the OTA Update so far? I have read about the list of improvements, and they look promising.
Secondly, I obviously want to stay rooted, are there any suggestions about how to update and then have my phone rooted? Preferably without losing my root, but I don't think that's possible.
Thirdly, I saw a thread about the viper (I believe that's what it's called) rom and that could be my possible solution. But, I am rooted on stock rom and have never put on another rom before. So what are your thoughts on this rom?
Thanks in advance
Sent from my HTC VLE_U using xda app-developers app

Problem Fixed
DrOfLife said:
Hello Everyone,
As of today, my phone received the new OTA Update for my HTC One S. However, obviously I cannot update due to my phone being rooted. As a person who is still relatively new with rooting (about a month rooted with my phone-first time), I have a couple questions.
First and foremost, have you guys enjoyed the OTA Update so far? I have read about the list of improvements, and they look promising.
Secondly, I obviously want to stay rooted, are there any suggestions about how to update and then have my phone rooted? Preferably without losing my root, but I don't think that's possible.
Thirdly, I saw a thread about the viper (I believe that's what it's called) rom and that could be my possible solution. But, I am rooted on stock rom and have never put on another rom before. So what are your thoughts on this rom?
Thanks in advance
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Hey Dr.
I had the same issue and fixed it. I'm enjoying the OTA update...seems snappier and the option to change the menu button and get rid of that eyesore at the bottom of the screen is great....See this post on how to fix it:
http://forum.xda-developers.com/showthread.php?p=32069130
All you have to do is download the stock recovery (link located in the post above), rename it "Recovery.IMG" and put it in the /Data/Recoveries folder that your All In One Kit uses. Then open up the All In One root kit, flash the stock recovery, and reboot your phone. It should look the same, and give you the same notification that an update is available. Install the update, and then reflash your TWRP or CWM and reroot (the OTA unroots the device, so you need to reinstall SuperSu.
Thanks to all the people that have helped me do the same!!!

fsustrength said:
Hey Dr.
I had the same issue and fixed it. I'm enjoying the OTA update...seems snappier and the option to change the menu button and get rid of that eyesore at the bottom of the screen is great....See this post on how to fix it:
http://forum.xda-developers.com/showthread.php?p=32069130
All you have to do is download the stock recovery (link located in the post above), rename it "Recovery.IMG" and put it in the /Data/Recoveries folder that your All In One Kit uses. Then open up the All In One root kit, flash the stock recovery, and reboot your phone. It should look the same, and give you the same notification that an update is available. Install the update, and then reflash your TWRP or CWM and reroot (the OTA unroots the device, so you need to reinstall SuperSu.
Thanks to all the people that have helped me do the same!!!
Click to expand...
Click to collapse
I keep flashing the stock recovery with all-in-one and then downloading and installing the update. Everytime, about halfway it goes back to the red triangle with the exclamation point and restarts the phone five minutes later.
I check software and its still 4.0.3 and the update redownloads. I've tried several "stock recoveries" and the update afterwards... never works.

TheAdictsPunk said:
I keep flashing the stock recovery with all-in-one and then downloading and installing the update. Everytime, about halfway it goes back to the red triangle with the exclamation point and restarts the phone five minutes later.
I check software and its still 4.0.3 and the update redownloads. I've tried several "stock recoveries" and the update afterwards... never works.
Click to expand...
Click to collapse
I have also tried the steps and have run into the same problem. All is well when I flash into recovery, but when the phone starts updating about quarter or half-way through it also gives me the same red error message and the phone restarts soon after with no update. I have tried several times with the same problem.
However, thanks fsustrength for the instructions, before I was getting no where, but now I almost got it
Sent from my HTC VLE_U using xda app-developers app

ckpv5 said:
As there are many questions on how to do OTA update & to revert to stock after a device is rooted and bootloader unlocked; I made this simple guide which I hope will help the newbies especially.
NOTE : always do a backup and a nandroid backup before trying any of these.
OTA update:
A) ROM is stock, bootloader unlocked, stock recovery and not rooted.
- just run the OTA update, there is no need to relock the bootloader
B) ROM is stock, bootloader unlocked, CWM recovery and not rooted.
- flash the stock recovery that comes with your RUU, extract the RUU for the stock recovery.
* boot to bootloader
* fastboot flash recovery recovery_signed.img
* fastboot reboot-bootloader
* fastboot erase cache
* fastboot reboot
- run the OTA update
C) ROM is stock, bootloader unlocked, stock recovery and rooted
- download OTA Rootkeeper from Play Store
- run the OTA Rootkeeper and click protect root
- run the OTA update, there is no need to relock bootloader
- Once done, run OTA Rootkeeper and click restore root
D) ROM is stock, bootloader unlocked, CWM recovery and rooted
- download OTA Rootkeeper from Play Store
- run the OTA Rootkeeper and click protect root
- no need to relock bootloader
- boot to bootloader and fastboot flash the stock recovery
- run the OTA update
- Once done, run OTA Rootkeeper and click restore root
E) ROM is custom, bootloader unlocked, CWM recovery and rooted and you have a stock nandroid backup
- flash the stock boot.img if after nandroid restore, you have a bootloop
- flash the stock recovery.img
- relock the bootloader - fastboot oem lock
- boot your device and run the OTA update
F) ROM is custom, bootloader unlocked, CWM recovery and rooted and you don't have a stock nandroid backup
- if you dont have the stock nandroid backup, you need to run RUU
- before you can run the RUU you need to:
* flash the stock recovery.img
* flash the stock boot.img (maybe no need)
* relock the bootloader - fastboot oem lock
* run RUU
- run device setup
- run the OTA update
Flashing RUU to revert to stock or to update your One V after you have a custom ROM installed.
- you must have the correct RUU for your device.
- if you are not sure, download CID Getter from Play Store and run it, it will show your CID.
- with your CID, you may be able to find a correct RUU for your device
then (even though some people may not agree with this, but this will bring no harm and it is noob-proof) do this:
1- flash a stock recovery.img
fastboot flash recovery recovery_signed.img
fastboot reboot-bootloader
fastboot erase cache
2- flash a stock boot.img
fastboot flash boot boot_signed.img
fastboot reboot-bootloader
fastboot erase cache
3- re-lock bootloader
fastboot oem lock
fastboot reboot-bootloader
fastboot erase cache
4- flash RUU
Note : for people with ERROR 155 UNKNOWN ERROR they need to go into HBOOT and select FASTBOOT and run the RUU to revert to stock (thanks Lloir)
And usually:
Error 155 - usually wrong recovery.img /wrong boot.img
Error 140 - wrong bootloader / bootloader unlocked
Error 131 - wrong RUU for your device
Credit to all XDA members that posted all the guides in various forum thread and some from own experience which I compiled here for easy reference.
Click to expand...
Click to collapse
Some wonderful person wrote a guide for the One V. Every though it's not the same phone the rules are the same. If these instructions help you click the link and thank the guy for writing it.
http://forum.xda-developers.com/showpost.php?p=27288357&postcount=1

Wow, that is a very useful guide right there! However, while reading the guide, Step D is exactly what both TheAdictsPunk and I seem to have done (I'm making an assumption that he did). I did in fact have and used the root keeper app, put it on temporary unroot, and flashed the stock rom and ran the update. Yet, I still run into the problem of the red error sign. I'm sure there is a factor that maybe could cause it to stop, but I cannot put a finger on it.
However, I did notice something while following the procedures of the guide on my phone. When I flash the stock rom on my phone, I have to re-download the system update. While downloading the system update I notice that some of my apps get root permissions from SuperSu in the background, even though in root keeper I temporarily took off root. Rootkeeper also states that my phone is unrooted. Could this problem cause the red error message? If so, any way to fix it?
Sent from my HTC VLE_U using xda app-developers app

DrOfLife said:
Wow, that is a very useful guide right there! However, while reading the guide, Step D is exactly what both TheAdictsPunk and I seem to have done (I'm making an assumption that he did).
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
I did! Last night I even tried flashing the recovery image through fastboot instead of the all-in-one kit. Then, even, the recovery image wouldn't flash all the way through... maybe our phones are having a problem with the recovery being reflashed and not the update at all.

I had the same exact issue. I finally got fed up and just flashed the RUU with my computer and then just used the All-in-one program to re-root. I am now enjoying 2.31 and really glad I updated. Obviously the RUU wipes everything, but I had done a full backup using Titanium Backup, and then restored all the important settings and data (like accounts, wifi list, bookmarks, dictionary, etc.) (but not the system apps themselves! ) and it worked out pretty well. Still had some things to adjust, like sounds and such. If you want to keep your SMS's use the built-in backup in the messaging app, then restore after the update.. more reliable than any other app I've tried.

mmceorange said:
I had the same exact issue. I finally got fed up and just flashed the RUU with my computer and then just used the All-in-one program to re-root. I am now enjoying 2.31 and really glad I updated. Obviously the RUU wipes everything, but I had done a full backup using Titanium Backup, and then restored all the important settings and data (like accounts, wifi list, bookmarks, dictionary, etc.) (but not the system apps themselves! ) and it worked out pretty well. Still had some things to adjust, like sounds and such. If you want to keep your SMS's use the built-in backup in the messaging app, then restore after the update.. more reliable than any other app I've tried.
Click to expand...
Click to collapse
I'm strongly considering doing that, I can back all my contacts and apps and sms messages via Mobile Go. So, wiping my phone isn't too big of an issue for me because I can restore almost everything I need back on my phone. If you don't mind me asking, where did you get the source that you got the RUU? Also, I have never flashed an ruu before so is their a guide for our phone to flash a RUU?
Sent from my HTC VLE_U using xda app-developers app

DrOfLife said:
I'm strongly considering doing that, I can back all my contacts and apps and sms messages via Mobile Go. So, wiping my phone isn't too big of an issue for me because I can restore almost everything I need back on my phone. If you don't mind me asking, where did you get the source that you got the RUU? Also, I have never flashed an ruu before so is their a guide for our phone to flash a RUU?
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
http://www.lastnite.de/RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5.exe
Links to downloads are on that page.. just copy/paste.
Basically start your phone in fastboot, connect to usb, then run the ruu with admin privileges. Make sure you are on stock recovery, and already have the USB drivers installed on your PC (unless you're on Linux.. already has them.. and maybe Mac too?)

mmceorange said:
http://www.lastnite.de/RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5.exe
Links to downloads are on that page.. just copy/paste.
Basically start your phone in fastboot, connect to usb, then run the ruu with admin privileges. Make sure you are on stock recovery, and already have the USB drivers installed on your PC (unless you're on Linux.. already has them.. and maybe Mac too?)
Click to expand...
Click to collapse
Well I followed all your steps, and all was going well until I ran across RUU error 130, which states that it was using the incorrect RUU. I looked into it and I found that it was the Europe version, and I have the T-Mobile version of my phone. I'm assuming that this is the issue, am I right? Does the RUU in Europe different than the T-Mobile USA one? If so, are there any RUU's out there that cover my phone? I have searched for them with no luck..
Sent from my HTC VLE_U using xda app-developers app

DrOfLife said:
Well I followed all your steps, and all was going well until I ran across RUU error 130, which states that it was using the incorrect RUU. I looked into it and I found that it was the Europe version, and I have the T-Mobile version of my phone. I'm assuming that this is the issue, am I right? Does the RUU in Europe different than the T-Mobile USA one? If so, are there any RUU's out there that cover my phone? I have searched for them with no luck..
Click to expand...
Click to collapse
Ok I figured out a couple answers to my questions. One, the Europe version and the T-Mobile Version are different. That explains why the RUU did not work and gave me Error 130. However, the T-Mobile RUU, RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S, is the alternate version that also recieves the OTA update. The RUU is found here http://androidforums.com/one-s-all-things-root/560329-ruu-download-mirrors.html
Then, following the steps, I have successfully updated my phone to the newer softeware!
But of course, I run into another problem.... The CWM recovery does not work for my phone. I flashed the recovery via the HTC One S All-in-One Toolkit. But when getting my phone into recovery mode, it "crashes." (By crashes I mean the phone will go into the htc developmental screen, then turn to black, then reload the normal bootup screen and boot normally up) So, I don't have CWM and I'm unable to root my phone again because I don't have CWM to flash SuperSu. Any thoughts on this?

Rerooting
DrOfLife said:
So, I don't have CWM and I'm unable to root my phone again because I don't have CWM to flash SuperSu. Any thoughts on this?
Click to expand...
Click to collapse
I'm still running stock 1.84, but I'm rooted and unlocked. I do not have any kind recovery like CWM or TWRP. You may have to flash a stock recovery image in order to re-install the recovery of your choice. If you want to get rooted again try this method: http://forum.xda-developers.com/showthread.php?t=1577831 It's what I used to gain root. It's a rather easy to follow guide. I used this instead of the AIO kit.
I'm going to try and revert to locked and unroot in order to get the update. Wish me luck.

DrOfLife said:
Well I followed all your steps, and all was going well until I ran across RUU error 130, which states that it was using the incorrect RUU. I looked into it and I found that it was the Europe version, and I have the T-Mobile version of my phone. I'm assuming that this is the issue, am I right? Does the RUU in Europe different than the T-Mobile USA one? If so, are there any RUU's out there that cover my phone? I have searched for them with no luck..
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Oh lol sorry about that.
DrOfLife said:
Ok I figured out a couple answers to my questions. One, the Europe version and the T-Mobile Version are different. That explains why the RUU did not work and gave me Error 130. However, the T-Mobile RUU, RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S, is the alternate version that also recieves the OTA update. The RUU is found here http://androidforums.com/one-s-all-things-root/560329-ruu-download-mirrors.html
Then, following the steps, I have successfully updated my phone to the newer softeware!
Click to expand...
Click to collapse
Awesome!
DrOfLife said:
But of course, I run into another problem.... The CWM recovery does not work for my phone. I flashed the recovery via the HTC One S All-in-One Toolkit. But when getting my phone into recovery mode, it "crashes." (By crashes I mean the phone will go into the htc developmental screen, then turn to black, then reload the normal bootup screen and boot normally up) So, I don't have CWM and I'm unable to root my phone again because I don't have CWM to flash SuperSu. Any thoughts on this?
Click to expand...
Click to collapse
I personally have never encountered that before, so I am of little help here. The suggestion above me sounds like the right direction though.

Red triangle error
dc211 said:
Some wonderful person wrote a guide for the One V. Every though it's not the same phone the rules are the same. If these instructions help you click the link and thank the guy for writing it.
http://forum.xda-developers.com/showpost.php?p=27288357&postcount=1
Click to expand...
Click to collapse
I'm using method C, i still get that red triangle error. Also i can't get the ruu for my phone. I'm desperate can you please help me.

lonegunman0 said:
I'm using method C, i still get that red triangle error. Also i can't get the ruu for my phone. I'm desperate can you please help me.
Click to expand...
Click to collapse
Im getting the same thing. Even after flashing "stock recovery" that i got from the modaco link, I can't update or even go into the stock recovery...I would absolutely love to enjoy the update too!

skidmarc11 said:
Im getting the same thing. Even after flashing "stock recovery" that i got from the modaco link, I can't update or even go into the stock recovery...I would absolutely love to enjoy the update too!
Click to expand...
Click to collapse
If this many people are running into this problem, maybe we can get a role call of whose using what method, if not stock ROM what custom they are using, and what carrier they us?
I'm stock ROM, Stock Recovery, and Tmobile US. I used Method C.
I'm wondering if they have changed the update in a way that is preventing some people from updating. like it detects a certain file before update or something idk. I'm not any sort of advanced android user so I am probably wrong, but it's the first thing that comes to mind. Otherwise, maybe they sent out a bad update file, but I feel like that probably wouldn't be the case since it's been happening for a couple days now.
Thought's ideas anyone, or am I alone in any of these thoughts?

Stock rom
mylegiscramped said:
If this many people are running into this problem, maybe we can get a role call of whose using what method, if not stock ROM what custom they are using, and what carrier they us?
I'm stock ROM, Stock Recovery, and Tmobile US. I used Method C.
I'm wondering if they have changed the update in a way that is preventing some people from updating. like it detects a certain file before update or something idk. I'm not any sort of advanced android user so I am probably wrong, but it's the first thing that comes to mind. Otherwise, maybe they sent out a bad update file, but I feel like that probably wouldn't be the case since it's been happening for a couple days now.
Thought's ideas anyone, or am I alone in any of these thoughts?
Click to expand...
Click to collapse
skidmarc11 said:
Im getting the same thing. Even after flashing "stock recovery" that i got from the modaco link, I can't update or even go into the stock recovery...I would absolutely love to enjoy the update too!
Click to expand...
Click to collapse
Yes i agree about the file detection. I'm running stock rom but i think i've just realised my problem. Although i have a stock rom my problem is that the stock rom i'm running is deodexed. I read somewhere that if the stock rom is tweaked in any way or if any bloatware is deleted you can't get OTA updates.
Hope this helped

Wouldn't an RUU fix any of those problems?

Yes it would
Sent from my HTC One S using xda app-developers app

[HOWTO] [ROOT] [ODIN] No Tripping Flash Counter - Root + [TWRP] - Updated 05.25.2013

This is a root injected Stock I535 (leaked) Odin Flashable Image. You flash this in Odin just as you would the completely stock ROM from samsung. I've simply injected the su binary and SuperSu app so you now have rooted stock image.
So if you want to keep your device stock yet have the functionality of root without tripping the counter or just flashing back to stock yet retaining root for a good baseline to move forward from, then this is a good option.
You can get ODIN here
and the drivers for the SCH-I535 so ODIN can detect your phone can be found at Samsung's site. Click on the Manuals & Downloads tab at the bottom and then on Software for the latest driver.
Instructions:
First, Download Image:
JB Image (4.1.2) Provided by open1your1eyes0 leak
Main Download: No Wipe, latest 4.1.2 Image: root66_VZW_I535VRBMB1.7z
Prior Version:
Mirror 1: root66_VZW_I535VRBMA2.7z - This will wipe everything! Complete factory wipe. Caution, Includes /sdcard.
Mirror 1: root66_VZW_I535VRBMA2_nowipe.7z - This will NOT wipe data or sdcard.
JB Image (4.1.1)
Mirror 1: root66_VZW_I535VRBLK3.7z - This will wipe everything! Complete factory wipe. Caution, Includes /sdcard.
Mirror 1: root66_VZW_I535VRBLK3_nowipe.7z - This will NOT wipe data or sdcard.
Older Leaked JB Image
Mirror 1: root66_VZW_I535VRBLK1.7z - This will wipe everything! Complete factory wipe. Caution, Includes /sdcard.
Mirror 2: root66_VZW_I535VRBLK1.7z - This will wipe everything! Complete factory wipe. Caution, Includes /sdcard.
Mirror 1: root66_VZW_I535VRBLK1_nowipe.7z - This will NOT wipe data or sdcard.
Mirror 2: root66_VZW_I535VRBLK1_nowipe.7z - This will NOT wipe data or sdcard.
Archived Images
Mirror 1: root66_VZW_I535VRBLJ1.7z - This will wipe everything! Complete factory wipe. Caution, Includes /sdcard.
Mirror 1: root66_VZW_I535VRBLJ1_nowipe.7z - This will NOT wipe data or sdcard.
Second, Extract and Flash:
Extract the root66_VZW_I535VRBLK1.tar.md5 from the .7z file you downloaded.
Use Odin, put phone into download mode [with phone off, hold vol. down + home + power ], connect to computer and open Odin.
once in odin click the PDA field and select the root66_VZW_I535VRBLK1.tar.md5 you downloaded.
Leave Auto Reboot and F. Reset Time checked.
click start and
when done let phone reboot.
If you have issues flashing with Odin please ensure you are using the microusb cable that came with the phone, users have had issues using other cables.
If you just want a stock, rooted phone with no custom recovery, no plans to flash custom roms, etc. then you can stop HERE.
Optional, Recovery (may now trip counter):
Loading any custom recovery or custom kernel may now trip the download mode flash counter. Loading a non stock recovery will also prevent you from successfully applying any OTA updates however here is a procedure for any who want a non-stock recovery:
The instructions here are for TWRP but you can follow same procedure for CWM as well.
Option 1: Download GooManager from the Play store. Once installed click the menu and select "Install OpenRecovery Script".
Option 2: Download the TWRP recovery image here. Copy it to the /sdcard of your phone.
Connect your phone to your computer and use adb
type adb shell
once in the shell run su
then
dd if=/sdcard/openrecovery-twrp-2.3.1.0-d2vzw.img of=/dev/block/mmcblk0p18
Alternate if unfamiliar with adb commands
Grab android terminal emulator from the play store and run the same commands starting with su and then the dd command.
Bonus Files
CWM Flashable OTA Upgrade (preserves root and non-stock recovery):
---------------:: root66_OTA_I535_VRBLK3_VRBMB1.zip
CWM Flashable Modems: modem_CWM_I535VRBLK3.zip || modem_CWM_I535VRBMA2.zip
ODIN Flashable Stock Recovery: VZW_recovery_I535VRBLK3.tar.md5 || VZW_recovery_I535VRBMA2.tar.md5
History:
I've injected root into other stock images and those threads have a lot of valuable information which could answer some questions that may arise here. If you have time to do some reading here are a few of the informative ones:
Samsung Galaxy S3 [ATT / Bell / Telus / Rogers / Sasktel ]
Samsung Galaxy S3 [TMO / Wind / Mobilicity]
Also did sprint but there isn't much there that won't be covered above.
FAQ
Does this remove the VZW bloatware?
A: No. It is same as stock, nothing is removed.
Does this use an unlocked boot.img
A: No. This flashes the stock boot.img in the VRBLJ1 image.
Can I still get OTA updates?
A: Yes if you do not load a custom recovery or remove any system apps OTA updates will still come and be able to be successfully applied. If you want to retain root through the OTA process I'd recommend using OTA Rootkeeper.

Awsome! Thanks for this!!

I'd like to add I don't have a VZW S3 so I didn't test those images above. The first person to try please post to confirm they work. Thanks.
EDIT: Anyone reading this, it's been confirmed they work now.

Does this come with the locked boot loader?
Sent from my SCH-I535 using xda premium

hitman980206 said:
Does this come with the locked boot loader?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Yes. In the faq question 2.

This appears to be exactly what I'm looking for (stock/rooted).
Still no power due to Sandy, but has anytime tried this and confirmed it works? I'm on the current official ota with root and no custom recovery now.

hitman980206 said:
Does this come with the locked boot loader?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Yes just use ez unlock
Hit me up on Gtalk if u need help @musclehead84

mrRobinson said:
Yes. In the faq question 2.
Click to expand...
Click to collapse
Sorry I meant unlockable bootloader?
Sent from my SCH-I535 using xda premium

No one tried this yet? Not many people looking only for stock/rooted lb

I installed open1your1eyes0 prior to seeing this or I would have tried it. I can confirm your flash counter will be tripped using that method. Had I seen this first I certainly would have used it as all I want is stock rooted.
Thanks for thinking of us conservative types that only want stock rooted.
Sent from my SCH-I535 using Tapatalk 2

lexluthor said:
No one tried this yet? Not many people looking only for stock/rooted lb
Click to expand...
Click to collapse
I hope at this point most people have their phone how they want it. To me, this is good for 2 things. 1, first get your phone and want completely stock but root. 2, you've played around with other roms, kernels, etc and want to get back to a good baseline ensuring all stock but of course retaining root.
edthesped said:
I installed open1your1eyes0 prior to seeing this or I would have tried it. I can confirm your flash counter will be tripped using that method. Had I seen this first I certainly would have used it as all I want is stock rooted.
Thanks for thinking of us conservative types that only want stock rooted.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Well there have been 30 downloads. maybe someone has tried it at this point. (some people never post) but I'm sure we'll know soon enough.

I rooted my phone via one of the original methods (Odin file) when it first came out. When I put, the first screen says "custom". I don't think that original method tripped the flash counter.
After installing this via Odin, will I still get the "custom" message on boot?
Foxfi no longer works on jb, right?

Worked like a charm!! unlocked with ez unlock and flashed cwm 6.0.1 with ez recovery...no tripped flash counter

droidstyle said:
Worked like a charm!! unlocked with ez unlock and flashed cwm 6.0.1 with ez recovery...no tripped flash counter
Click to expand...
Click to collapse
Confused. Don't you not need to unlock and flash this with Odin?

lexluthor said:
Confused. Don't you not need to unlock and flash this with Odin?
Click to expand...
Click to collapse
you flash with odin, unlock with ez unlock, then use ez recovery to flash a custom recovery...just like we been doin since day 1. reread the op or look up section 1 of my guide

droidstyle said:
you flash with odin, unlock with ez unlock, then use ez recovery to flash a custom recovery...just like we been doin since day 1. reread the op or look up section 1 of my guide
Click to expand...
Click to collapse
I misread. Thought he said flash with cwm.
Anyhow, I'm not doing custom roms, so I'm stopping after Odin. Still interested to the questions I had a couple posts up.

lexluthor said:
I misread. Thought he said flash with cwm.
Anyhow, I'm not doing custom roms, so I'm stopping after Odin. Still interested to the questions I had a couple posts up.
Click to expand...
Click to collapse
the custom screen means your bootloader is locked. No the original method does not trip the flash counter. You basically use this file just like you did way back with VRALF2 root66 that mr. robinson was so kind to provide us with.

I take it this works? I'm thinking of downloading for future use
Sent from my SCH-I535 using Tapatalk 2

edthesped said:
I take it this works? I'm thinking of downloading for future use
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
yeah did you not read my last posts

droidstyle said:
yeah did you not read my last posts
Click to expand...
Click to collapse
I clearly missed it. Spent the last 5 hours at a soccer tournament and the screen on this phone sucks in the sun, and I probably wasn't paying attention either. Downloading now
Sent from my SCH-I535 using Tapatalk 2

[Question]Updating rooted phone without messing up the phone?

Hi,
TL-DR; I rooted my phone, and want to update with minimal loss of data.
Sorry for this newbie question but I really couldn't figure out everything and wanted to confirm before proceeding.
I have MHA-L29C185B138 and rooted step-by-step via the instructions on this link:
HOW TO ROOT YOUR MATE 9 with Decrypted Data in TWRP without needing a patched Boot.img
I want to update. What should I do? I isntalled Firmware Finder and downloaded MHA-L29C185B172 FULLOTA-MF. (downloaded all 3 files)
I couldn't find a complete tutorial for rooted roms. Read different and partial recommendations on different threads. Somewhere I read that I need to restore my boot and recovery partition before update. I backed my boot partition as it was a step in rooting guide but I didn't back up my recovery partition.
So could you please point me a beginner friendly guide that explains step by step updating rooted mate 9?
Thanks in advance.

I bump up this question as I'm interested in that answer also
Sent from my MHA-L29 using Tapatalk

Updating and keeping root is basically not possible, as far as I know.
Regardless of installation method, your phone will be re-locked and wiped when new firmware is installed on a rooted phone.

Same question from me as well. I rooted using the method in the link and I wanted to update to C185B172. No idea what's the safe proof way. As this is my daily driver and only phone I can't risk messing with it.

vipivj said:
Same question from me as well. I rooted using the method in the link and I wanted to update to C185B172. No idea what's the safe proof way. As this is my daily driver and only phone I can't risk messing with it.
Click to expand...
Click to collapse
Whenever you update you have to start all over again with the same process you originally rooted with. Like @duraaraa said your bootloader gets locked back down and your recovery gets flashed to stock. So you have to unlock bootloader, then install TWRP, format your data so that you're unencrypted and flash the public then HW data files for the specific firmware you updated to. Basically follow the steps in the root method you initially used. This has to be done everytime
Sent from my MHA-L29 using XDA-Developers Legacy app

jr313 said:
Whenever you update you have to start all over again with the same process you originally rooted with. Like @duraaraa said your bootloader gets locked back down and your recovery gets flashed to stock. So you have to unlock bootloader, then install TWRP, format your data so that you're unencrypted and flash the public then HW data files for the specific firmware you updated to. Basically follow the steps in the root method you initially used. This has to be done everytime
Click to expand...
Click to collapse
So you meant to say if I download 'latest full package ' from Huawei, I can install it and everything go back to stock?

vipivj said:
So you meant to say if I download 'latest full package ' from Huawei, I can install it and everything go back to stock?
Click to expand...
Click to collapse
Yes sir. But remember if you're rooted with TWRP you will have to flash stock recovery first before you can even think about updating or taking an OTA otherwise​ it will fail.
sent from my rotary phone

jr313 said:
Yes sir. But remember if you're rooted with TWRP you will have to flash stock recovery first before you can even think about updating or taking an OTA otherwise​ it will fail.
sent from my rotary phone
Click to expand...
Click to collapse
Thanks for clarifying but the original question of OP hasn't been answered yet. Where to get the recovery.img from?
I downloaded the full package from firmware finder and extracted everything with 7zip, I found 2 different recovery files with same file size but different content in it.
recovery_a.img and recovery2_a.img
Which one should I use ?
Sent from my MHA-L29 using Tapatalk

itenos said:
Thanks for clarifying but the original question of OP hasn't been answered yet. Where to get the recovery.img from?
I downloaded the full package from firmware finder and extracted everything with 7zip, I found 2 different recovery files with same file size but different content in it.
recovery_a.img and recovery2_a.img
Which one should I use ?
Sent from my MHA-L29 using Tapatalk
Click to expand...
Click to collapse
Sorry about that, you want to use the RECOVERY.img not recovery2. You fastboot that img and you will have stick recovery, and it will place it in the correct spot so need to worry about where you would need to flash it to. Hope that helps
sent from my rotary phone