Bear with me guys, this month my phone seems to be having so many issues for no reason at all...
I odin'd today..
and I was going to root just as usual. on stock JFD, going to root by using superonelick - placed phone in usb debugging mode -
started it up and then i get this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
if image not showing: http://grab.by/aC2j
I will root using another method for now, but I'm wondering why it didnt work?
http://forum.xda-developers.com/showthread.php?t=849028
use the update.zip from somewhere in there
superoneclick never worked for me, always ended up not responding just after starting and i had to close it with tas manager
Damn noobs
Sent from my GT-I9000 using XDA App
Try using the Toolbox for Vibrant, you'll find it in the dev section or in the Vibrant bible. For some reason it has always done what or programs couldn't. Good luck.
Sent from my GT-P1000 using XDA Premium App
why root? there is no need to root in JFD to get CWM working. here is the update.zip, put it on sdcard, and boot into it, and then flash CM7 by hand. BAM! you're golden!
no need for root.
Yea just copy update.zip to sd card, reboot into standard recovery, apply update.zip, hit it a second time and then boom your in cwm.
You do have usb debugging enabled when your trying to root right? And usb is not connected as a mass storage device? If you do it wont work...!
Sent from my SGH-T959 using XDA Premium App
the noob guide I wrote has both methods, each with their own update.zip
I don't like superoneclick. neither does your pc's antivirus.
bfranklin1986 said:
Damn noobs
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Hey hey hey..... don't player hate.... player participate. Lol
s15274n said:
the noob guide I wrote has both methods, each with their own update.zip
I don't like superoneclick. neither does your pc's antivirus.
Click to expand...
Click to collapse
Actually. To all mentioning the update that's 'd the method is used and it was from your thread.
Also to the guy calling me a noob.
lol.
geoffcorey said:
why root? there is no need to root in JFD to get CWM working. here is the update.zip, put it on sdcard, and boot into it, and then flash CM7 by hand. BAM! you're golden!
no need for root.
Click to expand...
Click to collapse
That Noob guide is titled for rooting method.
so that thread is misleading because it only install CWM without rooting the vibrant phone.
souleater11 said:
That Noob guide is titled for rooting method.
so that thread is misleading because it only install CWM without rooting the vibrant phone.
Click to expand...
Click to collapse
Option A is for rooting.
Option B is for installing CWR and then flashing a new ROM straight away.
That is actually how I rooted my with Option A and messed around and cleaned the bloat from my stock ROM before I decided on which custom to flash b/c I hate Superoneclick and have never got it to work correctly on any phone. Some others have, I haven't.
Woodrube said:
Option A is for rooting.
Option B is for installing CWR and then flashing a new ROM straight away.
That is actually how I rooted my with Option A and messed around and cleaned the bloat from my stock ROM before I decided on which custom to flash b/c I hate Superoneclick and have never got it to work correctly on any phone. Some others have, I haven't.
Click to expand...
Click to collapse
Thank you for this clarification.
btw, i plan to use method A.
it seems steps 3 to 5 (OP Noob Guide) is exclusively for method B.
1. can you share me your experience in the steps 3 to 5 for using method A?
2. Do I have to Select Reinstall packages again for method A ?
If all you are wanting to do it root your phone, just download Option A.
This is what I did (without ever plugging my phone into PC once).
1. I downloaded Option A to my SDcard.
2. Booted into stock Recovery and since it was already labeled Update.zip, I just installed it that way. (You could rename it something like Rooter.zip and then you would pick the option in Recovery to :install from SD
3. Booted up and made sure Superuser.apk was there. It was.
4. Went to market to download CWR (free version) and installed it.
5. Made back up through CWR
6. Removed Bloater,blah blah blah and not once did I ever plug my phone in. Maybe I got lucky, maybe it was something else, but it worked for me. Later on I did copy all that to my PC because as you know, links do tend to get broken around here.
Less than a week later I had read and picked out custom ROM and flashed that. Most custom ROMs have a recovery already built into them.
Good luck and remember the first thing that you should do whenever you Root a phone is to get into Recovery and make a back up then and there, so that if/when you ever have to warranty your phone, you can restore it and remove the SU.apk and they will be none the wiser.
Note that Option B does have CWR included and I have read here and there that CWR free isn't in the market for some reason. Not sure about that though.
Thanks a lot. its a great help. i will try this.
it seems the free version of ROM manager is not anymore compatible in Android 2.1
Whitehawxx (spelling is probably off on that) has a 2.2 full bloat in the Dev thread if you want to use that and then you can use CWR from market. Just read the OP. Good luck and I am out for the day.
Thanks for the suggestion but I will root from stock 2.1 and just install an old version of ROM manager from 4shared.com
Woodrube said:
If all you are wanting to do it root your phone, just download Option A.
This is what I did (without ever plugging my phone into PC once).
1. I downloaded Option A to my SDcard.
2. Booted into stock Recovery and since it was already labeled Update.zip, I just installed it that way. (You could rename it something like Rooter.zip and then you would pick the option in Recovery to :install from SD
3. Booted up and made sure Superuser.apk was there. It was.
4. Went to market to download CWR (free version) and installed it.
5. Made back up through CWR
6. Removed Bloater,blah blah blah and not once did I ever plug my phone in. Maybe I got lucky, maybe it was something else, but it worked for me. Later on I did copy all that to my PC because as you know, links do tend to get broken around here.
Less than a week later I had read and picked out custom ROM and flashed that. Most custom ROMs have a recovery already built into them.
Good luck and remember the first thing that you should do whenever you Root a phone is to get into Recovery and make a back up then and there, so that if/when you ever have to warranty your phone, you can restore it and remove the SU.apk and they will be none the wiser.
Note that Option B does have CWR included and I have read here and there that CWR free isn't in the market for some reason. Not sure about that though.
Click to expand...
Click to collapse
if I follow your rooting method (A), is it safe to flash a miui gingerbread mod roms (miui nb or miui galnet) ?
to paraphrase, is it safe to flash from a newly rooted Android 2.1 to custom rom Android 2.3 ?
assuming I successfully flashed to Android 2.3, is my Super User still intact?
I just apprehensive about your method A, because some rooting methods (Z4root) when transfer to another firmware can cause a lost of Super user permission.
Related
Three new tools have been released or updated by their developers recently that may have a major impact on how we root and flash our phones. I will need to update the Guides with the new information, but first some confirmations are needed.
1) Chainfire has released a tool called Mobile Odin which will flash roms from the phone. There are two versions, Mobile Odin Pro which is available on the market for a small fee, and Mobile Odin Lite which is available free to xda members. Quoting from his thread: Flashing with Mobile ODIN does NOT increase your custom kernel flash counter or make the yellow warning triangle appear. This tool was updated today (November 28, 2011) to work with a host of new phones, including SGH-I777.
2) DooMLoRD has released DooMLoRD's Easy Rooting Toolkit (zergRush Exploit) which is reported to allow permanant rooting of our SGH-I777 phone without installing a custom kernel. This was most recently updated on November 16, 2011.
3) CLShortFuse developed SuperOneClick Root over a year ago, and recently updated it (November 10, 2011) to include the ZergRush exploit and SU 3.0.
With these tools, if they work as advertised on our phone, it will be possible to root and install custom software without incrementing the flash counter. When you have used one or more of these tools, I would appreciate it if you would post your results back here in this thread so I can gather information to update the [GUIDE] How to Flash Custom Binaries Without Ever Incrementing the Flash Counter!!
Thanks.
I have used the new version of SuperOneClick with the zergRush exploit to successfully root my SG2. However I will mention that the Unroot feature of SuperOneClick did not work. I simply used the unroot script DooMLoRD provided in his thread and I was able to unroot successfully. I am currently still unrooted as I have a business app I have to run that will not if it detects root. However, I assume either SuperOneClick or DooM's script will work once again if needed.
Will any of these tools reset flash counter and warning sign on already rooted phone?
I rooted without knowing these problems. Now I'm stuck with it.
Jig may or may not work, so didn't even try yet.
lambition said:
Will any of these tools reset flash counter and warning sign on already rooted phone?
I rooted without knowing these problems. Now I'm stuck with it.
Jig may or may not work, so didn't even try yet.
Click to expand...
Click to collapse
No. At some point we may figure it out to reset it through software, but until then only jigs reset the counter.
Sent from my páhhōniē
I recently noticed after flashing to UnNamed that the caution sign didn't appear. Has the ROM been developed to not trigger it or does it have to do with using the jig? I bought a jig a month ago from mobiletechvideo and I've only used it once. I've flashed CM7, Galnet MIUI and UnNamed since with no caution sign.
These tools will probably provide a new way to flash custom software without incrementing the flash counter. None of them will remove the warning triangle or reset the flash counter, however.
The only two ways to remove the warning triangle, and get the AT&T boot screen back, are 1) jig and 2) flash a stock kernel with Odin or Heimdall.
The only known way to reset the flash counter is with a jig.
The only thing that causes the I9100 boot screen with the warning triangle and increments the flash counter is flashing a custom kernel with Odin or Heimdall. So, you can flash with adb or Android Terminal Emulator or ClockworkMod Recovery, or appearantly with the new Mobile Odin, without incrementing the flash counter.
I'm definitely interested in hearing about peoples results using these tools. That is the main purpose of this thread. Thanks.
I used the DooMLoRD method, which is really easy, and it's been working for several weeks with no issues. I haven't needed to unroot, so haven't tried that yet.
[Edit] I haven't tried flashing a new rom, so I can't comment on the flashing without triangle. I just wanted root for a couple small issues, I'm going to wait to start flashing until some stable releases of ICS start appearing.
I've used SuperOneClick with Zerg to root, then installed Entropy's Daily Driver through Android Terminal then flashed UnNamed through CWM all without tripping any counters.
Love it!
So just confirming, when I get my S II, using your earlier guide that's a sticky, I'll be able to not increment the flash counter AT ALL (flashing Entropy's kernel through adb, then flashing the unNamed Rom via CWM, and also flashing the su package for root)?
Or should I wait a week or so for you to possibly update your guide, with an even more idiot-proof process?
Thanks again!
Thanks for sharing
avidmovies said:
So just confirming, when I get my S II, using your earlier guide that's a sticky, I'll be able to not increment the flash counter AT ALL (flashing Entropy's kernel through adb, then flashing the unNamed Rom via CWM, and also flashing the su package for root)?
Or should I wait a week or so for you to possibly update your guide, with an even more idiot-proof process?
Thanks again!
Click to expand...
Click to collapse
The guide is still good. I'd like to provide all the options though.
At this point, it is clear that rooting with either SuperOneClick or ZergRush will be part of step 2 in the guide, and may be easier than using Odin or Heimdall.
Still waiting for any information on Mobile Odin. If it's easy to use on our phones, it may be an improvement over steps 3 and 4.
Thanks!
Sent from my Nexus S 4G using Tapatalk
Used the zergrush root and then mobile odin to set my friends sgsii up with unnamed and icsrewed theme. Worked great without one issue.
Sent from my páhhōniē
gr8hairy1 said:
Used the zergrush root and then mobile odin lite to set my friends sgsii up with unnamed and icsrewed theme. Worked great without one issue.
Sent from my páhhōniē
Click to expand...
Click to collapse
Did you use lite or pro?
Could you describe using Mobile Odin, setting it up, how the flashkernel works, etc?
I downloaded the zergrush root package from the op. Then went to (edit):
http://forum.xda-developers.com/showthread.php?t=1347899
and downloaded mobile Odin lite.
First downloaded Samsung kies for the proper drivers then downloaded and opened zergrush. When you first open zergrush by opening 'run me' (i think it was called) it will tell you everything you need to have already done before plugging in your phone. It recommends changing your screen timeout to 10. I'm guessing this is for adb use, as adb can not connect to your phone if the screen is off.
I then plugged the phone in and pressed a key for it to start. All in all it took around 5 minutes. Majority of the time was processes coming up that waited 40 seconds. Guessing the phone was doing things that you couldn't see. At no time did I need to press anything on the keyboard or phone.
After that was done I opened mobile Odin lite. It gives you the choice of downloading the file you need or cancel. I already had the kernel I was going to flash, entropy512's dd, but I clicked download file just in case out would load the file for me. Well it didn't. It took my browser to:
http://forum.xda-developers.com/showthread.php?t=1347899
That's great for most users but I already had the zImage I wanted. I hit the back arrow which took me to a black screen, guessing mobile Odin. Hit back again and was at my home screen. Reopened mobile Odin, and after a few tries found out you need to hit cancel to continue on.
That gives you this screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After that:
The only main option is kennel, and that's all I neededafter choosing it I got:
It was stored on the root of my internal sdcard, so I selected internal and then seen:
It obviously automatically put the kernel at the top by itself. Picked it and then had:
Chose flash kernel, rebooted the phone, and it was done. Downloaded unnamed, used three button hold to get into recovery, sure enough CWM was there, chose unnamed. Rebooted and viola, custom rom. Through this whole process the boot screen never changd to i9100 with the yellow exclamation point or was the flash counter tripped.
Sent from my páhhōniē
(yeah, I typed that all on my phone, talk about a sore hand)
I guess after you open Odin, you pour a Guinness , then download the file you need or cancel?
@gr8hairy1
Nice write up. Very useful. I'll probably get a chance to install this and play around with it tomorrow. Couple questions though.
gr8hairy1 said:
I downloaded the zergrush root package from the op. Then went on the android market and downloaded mobile Odin lite.
Click to expand...
Click to collapse
Did you download the lite version from the market? I only see the pro version on the market, and Chainfire's thread also indicates to download the lite version from his thread.
...
After that was done I opened mobile Odin lite. It gives you the choice of downloading the file you need or cancel. I already had the kernel I was going to flash, entropy512's dd, but I clicked download file just in case it would load the file for me. Well it didn't. It took my browser to:
http://forum.xda-developers.com/showthread.php?t=1347899
That's great for most users but I already had the zImage I wanted. I hit the back arrow which took me to a black screen, guessing mobile Odin. Hit back again and was at my home screen. Reopened mobile Odin, and after a few tries found out you need to hit cancel to continue on...
Click to expand...
Click to collapse
Do you know what Chainfire means in his Mobile Odin thread by flashkernels? Did you have to download one? From your write up, it sounds like you didn't and Entropy's kernel flashed fine.
Thanks.
iainash said:
I guess after you open Odin, you pour a Guinness , then download the file you need or cancel?
Click to expand...
Click to collapse
Yeah buddy! Need to put that step in there.
Though I'm a yengling fan
Edit: lol, just seen my guinness spelling error. Nice to know swype appreciates a good beer
Sent from my páhhōniē
creepyncrawly said:
@gr8hairy1
Nice write up. Very useful. I'll probably get a chance to install this and play around with it tomorrow. Couple questions though.
Did you download the lite version from the market? I only see the pro version on the market, and Chainfire's thread also indicates to download the lite version from his thread.
Do you know what Chainfire means in his Mobile Odin thread by flashkernels? Did you have to download one? From your write up, it sounds like you didn't and Entropy's kernel flashed fine.
Thanks.
Click to expand...
Click to collapse
You're right, I downloaded it from xda. Not sure how I got that mixed up. I'll update my post. Though I had taken a vicodin, alieve, and 2 benedryl around 1am, and it was almost 2am when I posted that. Stupid butt surgery is kicking my butt.
And correct, I did not download his flashkernel. I was tempted to flash it to check out what it did but it wasn't my phone I was working on. I stuck with flashing what I knew would get me cwm, and flashed Entropy512's kernel. Flashed with no issue.
Sent from my páhhōniē
creepyncrawly said:
2) DooMLoRD has released DooMLoRD's Easy Rooting Toolkit (zergRush Exploit) which is reported to allow permanant rooting of our SGH-I777 phone without installing a custom kernel. This was most recently updated on November 16, 2011.
Click to expand...
Click to collapse
First I wanted to say THANK YOU for all your help. I was able to follow your guide to flash my phone with out incrementing the flash counter.
But before I did that I did try DoomLoRD root fix. It worked as advertised and was exactly how the instructions were documented. I had no issues.
Again big thanks to you for all your help!
ICS is on the horizon, and we have already have one update available for the Rezound. So, if you're like me, you want an OTA update to be as hassle-free as possible. I am unlocked through HTC-dev, and I am all stock, so this is mainly for Stock and Rooted users, although it may work for others.
This thread will tell you how to keep your phone OTA-ready, so that your phone updates AND keeps what you want on it, at least, as much as possible. I will also give methods of keeping or regaining root.
Staying OTA-ready, and updating through OTA, while protecting root:
First off, make sure you have installed OTA RootKeeper. OTA RootKeeper has been confirmed to backup superuser and is a simple way of restoring superuser after an OTA.
Second, before uninstalling or freezing bloat, make sure you have them backed up. How you go about this is your choice, but I personally use Titanium Backup. My method is to assign everything I'm going to freeze or Uninstall to a label within Titanium Backup, which makes freezing, unfreezing, installing, or uninstalling that much easier. See my examples:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thirdly, make sure you have a regular or dependable back up program/s. I personally have a scheduled back up with Titanium Backup and Go SMS Pro that backs up everything I want, daily. I also use My Sync Center to back up anything that I want, and anything new in the folders I've selected, every time I connect to my home WiFi network. These are what I use, and will work well, and across many phones, not just through updates, if you put the effort to schedule and set everything up. I don't do anything, and it's all automatic. There are many other options out there, but this is my preferred method of backup.
Now, you are OTA-ready. As soon as you get that OTA update prompt, simply Unfreeze or reinstall your bloat, back up everything to be safe, then install the update. After updating, you should be able to reinstall your root with OTA RootKeeper, and if you use TB like me, just filter your bloat with the label you created, and take care of them in whatever fashion you prefer. That's it. If you lost root, for whatever reason, I also have a method to regaining it, and still being OTA ready afterwards.
I did not lose any internal data, but I still backed everything up. Be safe, and be sure that you always back your stuff up. Even in the best situation, something unplanned could happen.
Regaining Root, if lost, after OTA:
First off, download Scott's CleanFLASH,
con247 said:
amonra
Click to expand...
Click to collapse
, and
andybones said:
stock recovery
Click to expand...
Click to collapse
.
What you will be doing, is flashing two recoveries, or if your prefer, just one. For the purposes of this thread, I will be instructing how to stay OTA-ready, but Amon Ra is a good recovery if you want to make nandroid backups. I currently don't use anything other than the stock recovery, because, like I said, I want to be OTA-ready, and TB meets all my needs for the moment.
Secondly, put all three files on your computer. I made two folders, within the folder I was using, and named them stock and Amonra. I then placed the stock recovery file within the stock folder, and unzipped it within that folder. I did the same with the Amon Ra recovery file, but within the Amon Ra folder. This was to ensure that I didn't flash the wrong recovery file.
Thirdly, back up your phone, in your preferred method. There are some good applications out there, like MyBackup Pro, that can backup a lot of applications and settings, even without root. I did not need to backup anything, as I found out later, but always prepare for the worst. I personally did not lose anything using this method.
You are now ready to flash the recovery. Plug your phone into the computer. You do not need to do anything with it, except to make sure debugging is enabled. Make sure HTC Sync is also disabled on your computer. Place the Amon Ra recovery image into the same folder as the CleanFLASH, then open CleanFLASH. Use option one, just wait, and you're done. Unplug your phone, and go into recovery. You should be at the HBOOT screen at this point, but however you get into the Recovery menu is your choice. Once you are in the Amon Ra recovery menu, go to the Developer option and install superuser there. After completing this, just get out of recover, and reboot your phone.
The next step is to wait after your phone is at the main screen, after booting up. Plug your phone in, like before, and make sure everything is ready again for CleanFLASH. Delete the current recovery image that's in the CleanFLASH folder and put the stock recovery image in it's place. Use CleanFLASH, as before, to flash the Stock Recovery, and after completion, just reboot your phone.
Once your phone is finished rebooting, go into the market and install superuser, then go into the settings of superuser and update the SU binary. See my examples:
You should now be re-rooted successfully and still OTA and ICS ready. Follow my instructions in the other section on how to remove or freeze bloat in such a way that it will be easy to take minimal steps when it's time to install the next OTA update.
I hope this is informative and helpful to someone. Feel free to share your thoughts and/or tips, and I will be updating and changing the OP accordingly, should it be necessary to do so.
Thanks to con247 and andybones for pointing me in the right direction.
I am not responsible for any issues with your phone, so proceed at your own risk.
Thank You!!!!!!!!!!!!!!!!!!!
Hello, I am a noob and I was following a link in the Development section on how to root my phone. But I could not get Terminal Emulator to allow me to change to SU. I kept getting Access Denied. I asked for help but nobody understood why that was happening. I should mention that Root Explorer requested authorization from SuperUser and it was granted. So I started searching under General and I found your post. I followed it step by step and this time the root took with Terminal allowing me to change to SU.
I would like to mention that when you talk about rebooting twice I got lost. I believe when you did this you booted back to bootloader and then did the reboot from there (Yes?). Since at the time I did not understand, I rebooted out of RA which then boots into phone mode. So I shut down and then restarted to get my two times. What I am saying after all of that is maybe adding more detail about that step would be helpful.
Again Thank You for you detailed post.
dnvm said:
Hello, I am a noob and I was following a link in the Development section on how to root my phone. But I could not get Terminal Emulator to allow me to change to SU. I kept getting Access Denied. I asked for help but nobody understood why that was happening. I should mention that Root Explorer requested authorization from SuperUser and it was granted. So I started searching under General and I found your post. I followed it step by step and this time the root took with Terminal allowing me to change to SU.
I would like to mention that when you talk about rebooting twice I got lost. I believe when you did this you booted back to bootloader and then did the reboot from there (Yes?). Since at the time I did not understand, I rebooted out of RA which then boots into phone mode. So I shut down and then restarted to get my two times. What I am saying after all of that is maybe adding more detail about that step would be helpful.
Again Thank You for you detailed post.
Click to expand...
Click to collapse
I'll just remove it. I'm not sure it's even needed.
Sent from my ADR6425LVW... An HTC Rezound
First off...Thanks to Lokifish for all your hard work. I would post this in your thread, but I'm too new to post in the developer forums (though at least I was able to hit the thanks button).
So after reading through the entire deblur thread, being the n00b that I am, I was still hesitant to try it due to my uninformed decision to install the OTA update and not being able to find any post confirming it worked (on a stock phone) after that update. Well, I tried it anyway and just wanted to post somewhere that it worked flawlessly. I also wanted to include my own little "side guide" with precautions I took (after reading through the thread) that weren't in Loki's original guide, in hopes that it may help other n00bs such as myself to feel more comfortable with the process:
Make sure you have the latest drivers installed on you PC for your photon and the correct architecture. <--If you don't know what this means, stop here.
1. Root phone using photon torpedo method. http://www.groovypost.com/howto/motorola-photon-4-g-how-to-root-your-phone/ <--Thanks to kbeatzzz for his post. This method works and is easy to follow/do. <--Also thanks to edgan, obviously, for the photon torpedo method.
2. Install custom bootstrap recovery. <-- Thanks to topolovich for his post in the deblur thread.
This can easily be accomplished by following the "Custom Bootstrap Recovery" how-to video here: http://forum.xda-developers.com/showthread.php?p=17302907 <-- Thanks to qbking77 for these guides! Awesome work.
I think it's best to copy the apk to external sd, but you can copy to internal storage if you want, and just recopy it later.
3. Boot into the custom bootstrap recovery and make a backup to your external sd card.
4. After backup is complete and you rebooted your phone, power off and remove the sd card.
5. Reset to factory defaults <--from Lokifish Marz guide (Don't worry, this will not "unroot" your phone)
6. Install Superuser (by ChainsDD) from android market ...Needed for superuser permissions later, you don't have to do anything other than click allow when superuser asks if the apps can have permissions and make sure that the box is checked so superuser remembers the answer (that's important). Also be sure to update to latest binary from within superuser app.
7. Install BusyBox (by Stephen Stericson) from the market <-- thanks to Lokifish Marz, KyleIsTheBeast, NukeFish posts. This only installs the installer. You have to open it and then click install to actually get busybox installed. Don't mess with any of the settings!!!!
8. Copy the entire "1deblur_lite" folder over to internal storage (latest version) as per Lokifish Marz instructions in the OP of the Deblur Thread
(If you can't figure out how to get to the actual download link, see Post 3 of this thread for more details)
9. Power down and insert sd card, then power up and reinstall the apk for the bootstrap recovery. Make sure to go through all the steps again outlined in the video guide I mentioned earlier. If you copied the apk to your internal storage earlier, you'll have to recopy it, otherwise just install from sd card.
10. After rebooting from bootstrap recovery, unplug the charger, and uninstall any apps that are not included in this guide. (Many of them only allow you to uninstall updates, these apps will be there no matter what so no need to uninstall updates on these) Doing this step was something I added just to make sure there's nothing that will conflict with the script.
11. Turn on Airplane mode <--Thanks to Lokifish Marz suggestion and to ZeroManArmy for experiencing a problem and posting instead of giving up
12. Do not perform this step until you read step 13 and make sure charger is unplugged... Run the script as per instructions outlined by Lokifish Marz in the Deblur thread. Watch the video!
13. WAIT about 5 minutes before removing the battery. <--Thanks to ZeroManArmy for his post
14. Then reinsert battery and power up. You should now have a deblurred phone
If you softbrick the phone, you should be able to boot to the custom bootstrap recovery and restore your backup. (I can't guarantee this because I did not brick my phone, but the recovery mode continues to function normally after running the script) I did run into one little bug where the ringer toggle icon disappears after a while. This is likely an issue with one or more apps I have installed, because I haven't found any posts about this. I will ask in the Q&A forum to see if Lokifish might see it and help me get the icon back. This is a very minor issue though as the toggle still works.
I hope Lokifish does not take offense to the above guide. I just figured since taking these steps helped me to be "brave" and try it, they might help others too.
copy what?
umm on the http://forum.xda-developers.com/showthread.php?t=1575259&highlight=deblur fourm what am i suspose to copy to where
Silverdre said:
umm on the http://forum.xda-developers.com/showthread.php?t=1575259&highlight=deblur fourm what am i suspose to copy to where
Click to expand...
Click to collapse
In the OP of that link, scroll down to the video. Just above the video is a "Downloads:" link. That will take you to the Martian Imperium site. Click Enter. Click Downloads, click Motorola, click the link on the right (v1.0.8). From there you have to do a bit of add dodging (This helps Lokifish host the file and keep track of how many times it's downloaded):
DO NOT click any of the colored stuff, scroll down an click the ACTUAL BUTTON that says "Download or Watch". The new page will have a BIG GREEN ARROW pointing down in the center of the page. Click the "Download" link just below the arrow. Now you have to wait. Eventually it will connect and you can download the zip file. What you need to copy is located in that zip file: The "1deblur_lite" folder.
Note: You're probably going to have to close a bunch of popups. No worries, there's no adware/spyware or anything, just don't click anything you're not supposed to
Hey you have anyidea how to undo this deblur cause I tried asking loki and no reply
Sent from my MB855 using xda app-developers app
Silverdre said:
Hey you have anyidea how to undo this deblur cause I tried asking loki and no reply
Click to expand...
Click to collapse
Did you make a backup first as described in step 3 above? If so, boot into bootstrap recovery and restore from backup. Otherwise, you'll have to flash back to stock or another ROM. If you're on the 2.3.5 OTA update, which I suspect you are, then see below:
You can flash back to stock using a bootstrap flashable zip of the OTA update located here, thanks to mof9336
You can also flash to a De-Blurred Slim ROM that is bootstrap flashable and works with the 2.3.5 kernel/bootloader, also thanks to mof9336. You can find it here
I'm currently using v1 of the above ROM because I ran into some issues with voicemail on v2, but this doesn't seem to be the case with others who are running it, so I would definitely recommend trying v2 first.
Hope this helps
Help please
Hi everyone, im looking for help.
Y succesfully deblured my photon, everything was fine. My wife accidentaly factory reset my phone and now i cant use the phone y gets stucked on the contacting network screen, is there a way to boot to bootstrap recovery to restore my backup ig the phone cant boot? help please
elmaiko said:
Hi everyone, im looking for help.
Y succesfully deblured my photon, everything was fine. My wife accidentaly factory reset my phone and now i cant use the phone y gets stucked on the contacting network screen, is there a way to boot to bootstrap recovery to restore my backup ig the phone cant boot? help please
Click to expand...
Click to collapse
As far as I know, wiping the data partition (factory reset) kills bootstrap recovery because it's not a true custom recovery. The only thing I can think of would be to use RSD Lite. Check out the following post and be prepared to do a lot of reading. http://forum.xda-developers.com/showthread.php?t=1798145
Also, there may actually be a full Photon 2.3.5 SBF available by now, though I haven't found one. You may wanna try looking. If you find it, let me know.
Hope this helps
Keep in mind, I'm still a n00b myself and I am offering suggestions based on limited knowledge.
p0wder2 said:
As far as I know, wiping the data partition (factory reset) kills bootstrap recovery because it's not a true custom recovery. The only thing I can think of would be to use RSD Lite. Check out the following post and be prepared to do a lot of reading. http://forum.xda-developers.com/showthread.php?t=1798145
Also, there may actually be a full Photon 2.3.5 SBF available by now, though I haven't found one. You may wanna try looking. If you find it, let me know.
Hope this helps
Keep in mind, I'm still a n00b myself and I am offering suggestions based on limited knowledge.
Click to expand...
Click to collapse
thanx a lot, i followed that guide and my phone is working again :good:
Glad I could be of assistance
Can't open /sdcard/Universal
I tried following the method mentioned in Loki's post however, i get an error saying -
Script was not run successfully.
Stderr:
sh: can't open /sdcard/Universal
Please help
everything went well and phone is more fluid, faster & responsive.
love the adw launcher and updated it immediately.
but somehow my music & gallery are not working any more
i just get a blank light blue screen like of moto blur.
any idea or suggestion what to do. do i need to get separate apps
for these two things. or remove or reinstall something???
auto downgrade to 2.3.4
i was using deblured ota 2.3.5 for two weeks now.
but i had not reset my mopho.
i felt like doing it today. through keys by android recovery.
after which i found my phone is still deblured and rooted
but android version shows 2.3.4
and system 45.3.7
how is it possible that my rom got downgraded. did it remove the ota
does it mean i can now attempt to unlock.
is it risky, its unbelievable.
please through some light.
Run this in terminal emulator if you're rooted
su
cat /sys/firmware/fuse/ReservedOdm
And post your output
Sent from my sunfire using xda premium
terminal emulator and system info
hoslayer13 said:
run this in terminal emulator if you're rooted
su
cat /sys/firmware/fuse/reservedodm
and post your output
sent from my sunfire using xda premium
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sorry your system was reverted back but your still stuck on the 2.3.5 bud. Your bootloader is locked down still
http://forum.xda-developers.com/showthread.php?p=26014213
Sent from my sunfire using xda premium
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Options:
1) Fresh Root - This is to do a clean root on your stock Asus JB rom or any other custom rom. Great for any users that lost root during an upgrade.
2) Fresh Start - This will give you a clean start by wiping your system partitions (backup your data) then flashing a stock JB image. After the package will do a clean root to the TF201 (Make sure you download the JB update for your region from the Asus site then extract and place the "blob" file in the same folder as this package and rename to "system.blob"
!!! This is for users with from any region with unlocked bootloaders only !!!
I made this because a few users have had trouble with root after the JB update from Asus. What I have made is an automated package that includes the root binaries and the the Team Win Recovery. From FASTBOOT this package will flash a custom recovery then root it. If a previous broken root from an update exist it will remove the old broken root and re-root it. Simple as that!
Additionally I have made another option in this package called "Fresh Start" and what this will do is wipe you tablet clean (backup your data) then flash a new image of JB. Once completed it will flash the custom recovery and root it before you even sign-in and set up the tablet. I recommend this as it will make the tablet nice, clean & speedy.
This assumes you have the correct drivers installed for your device, if not I recommend my Universal Naked Drivers Here
Credits:
Root Binaries - (ChainsDD) http://androidsu.com/superuser/
Recovery - (TeamRecovery) http://www.teamw.in/project/twrp2
**************************************************
This thread is not for help with unlocking your device or the naked drivers.
Hashes:
CRC32: 8C62EA76
MD5: 2E946D245F3778A5DEF2D07C00F8EF4B
SHA-1: 343661C655399CBE77E5D2946B59CFCCB77A1A69
Thanks
*ninja reserved*
I was so happy to see this and miss the "for unlocked bootloader only"
Anyway hope someone could come up for Locked Bootloader.
:EDIT_THANKS
Hey there,
after some issues i made the root!
great work!
thank you 1wayjonny!
:EDIT_SOLVED
think i made it. don´t know why, but after the 30 try the bat said finished, okay...
:EDIT_ORIGINAL
Hey everyone,
i got a problem, i flashed my tf201 with the new JB rom from the asus website, my device is unlocked. no root before. now i can´t root it...
everytime i start the "Fresh Root.bat" or the "Fresh Start.bat" i get multiple lines with
"FAILED (command write failed (Unknown error))"
can anybody help me?
greetz andy
howsed said:
Hey there,
after some issues i made the root!
great work!
thank you 1wayjonny!
Click to expand...
Click to collapse
Thanks for the feedback, being its automated you just have to get use the on screen instructions. I wiped and re-flashed, then rooted about 30x in a row with this package so I thought I would release to others to make their life easier.
If anyone has suggestions for any instructions that were not clear enough let me know and I can update for clarity.
howsed said:
:EDIT_THANKS
Hey there,
after some issues i made the root!
great work!
thank you 1wayjonny!
:EDIT_SOLVED
think i made it. don´t know why, but after the 30 try the bat said finished, okay...
:EDIT_ORIGINAL
Hey everyone,
i got a problem, i flashed my tf201 with the new JB rom from the asus website, my device is unlocked. no root before. now i can´t root it...
everytime i start the "Fresh Root.bat" or the "Fresh Start.bat" i get multiple lines with
"FAILED (command write failed (Unknown error))"
can anybody help me?
greetz andy
Click to expand...
Click to collapse
You have missed the step that mounts the /System from recovery. This has to be done manually then ADB can push ROOT. It said write failed so i assume this is where you got stuck.
1) Make sure you run as "Admin" just in case
2) When you boot into the custom recovery, you must select the "Mount" icon then then select system. After then you continue with the batch file and all should be good.
I can confirm that this worked w/ my TF201. Thanks a bunch!
I was unlocked and had root plus a "backup" according to Voodoo OTA RootKeeper. I manually installed the JB update via sdcard and lost root plus all signs of root. Being unlocked, I used your method in Win7 (parallels virtual machine on mac) running a shell as admin and everything worked without any hitches. I have root and have verified by Voodoo OTA, Root Explorer, and Titanium Backup.
A big thanks to you for this. I now have root again!
Robert
Ha ha ha ha! Root Restored!
Sir, You are a God! I lost root when I manually updated to JB using the Micro SD Card method. Followed your guide and am now rooted on JB! Sixaxis gaming Nirvana restored! Thank you!!!
---------- Post added at 08:25 PM ---------- Previous post was at 08:24 PM ----------
I can also confirm that the Asus Unlock tool worked for me.
I just tried this the total fresh start (blob method ). Got to last stage (mount system). Adb no device found . How can I rectify this .
Edit I updated sdk today .. tried naked drivers etc still cant get it to recognize it
Sent from my GT-I9300 using Tapatalk 2
adz63 said:
I just tried this the total fresh start (blob method ). Got to last stage (mount system). Adb no device found . How can I rectify this .
Edit I updated sdk today .. tried naked drivers etc still cant get it to recognize it
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
For anyone having issues with the ADB command I would manually try ADB before this package. This package assumes you have your drivers working in FASTBOOT & ADB. Or when you get the recovery flash and you have booted the recovery open a second prompt and try the "adb devices" command before this package pushes root.
I see that you have quite a few amount of post and would think you have some experience, since you are still having issues I would say that the drivers are dirty or something else weird is going on.
You have mentioned you get the recovery flash then booted, at this stage can you go to your device manager and take a screen shot of the Android device? You may have to repoint the device to the drivers but non the less a screen shot would help.
is there something like this but not for unlocked bootloader? I lost root on OTA but i didn't have it unlocked and don't want it to be fore now, I'm just using stock.
Works beautifully!
Thanks for root back!
I'm running CM10 unofficial right now but it's giving me some issues I'd rather not deal with right now...it already has the JB bootloader...can I still flash this to go back to stock[JB]?
I was wondering how to reinstall a recovery and to root again... Thanks!
Note: i just copy command lines from the bat file because i'm on linux.
Just wanted to say: it worked perfectly and painlessly on my already unlocked but otherwise stock prime!
Hi,
Coming from Completely Stock Prime with JB update. Unlocked BL via Asus Tool then used this method and everything went Perfect!! Thanks for your Effort.
I have to say that I'm glad to see you made this, worked great. Tried many other ways to root jb after I flashed androwook and lost custom recovery and root.
You're awesome!
Sent from my SGH-T999 using xda premium
Q
Do i lose erverthink or will i keep my current stock rom whitout installing erverthink.
Thanks works like a charm, unlocked my prime and installed the naked driver let the batch file do it work. back on rooted system with everything working
So I'm trying to do the Fresh start but can't for the life of me figure out how to move and rename the blob file unfortunately. I've got the extracted JB update file on my desktop but can't rename the blob file, right clicking it won't give me the option...
I'm supernoob with this device so can anyone please walk me through or figure out what I'm missing? Please...
Edit: well, looks like I've just gotten myself an unrecoverable bootloader...
more detailed instructions would be appreciated
I am a noob to this device and just unlocked the bootloader.
Can you post detailed step-by-step instructions for your method in the OP or PM. I am also wondering if TWRP version has been updated to 2.3.
Thank you very much.
EDIT: I am all set. Thanks.
Unlocking, rooting, relocking and unrooting simplified! (and much more!)
VERSION 2.1.4 - This program will automatically bring together all the files you need to unlock and root your device in a few clicks, or flash it back to stock and re-lock it. You can also use this program to backup/restore all your important data, flash zips, set file permissions, push and pull files, install apps, generate logcats/bugreports, and much more! With the included file association options, you can perform tasks like flashing zips, installing apps, restoring android backup files, and flashing/booting img files with just a double click! The program includes a full featured interface for automating tasks in TWRP, enhanced restore features, an in-built auto-updater/notification system, ‘any build’ mode, advanced restore features,’NRT- Live Log’ for viewing the adb/fastboot cmds that are run in the background, quick tools utilities, and tools for taking screenshots/screen-recordings. All the latest official Android builds and Nexus devices are supported. The program intelligently and selectively downloads the files it needs for your device and makes sure you are using the latest files available. The program can even auto-detect your device and build. This release brings full Marshmallow root support plus all automated features by utilizing a new system that no longer requires modified boot.imgs. Check out the updated changelog for a more comprehensive breakdown of the feature set and changes in this release.
~ my goal for this project is make the entire process as smooth and simple as possible ~
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please read the FAQs before posting questions: http://www.wugfresh.com/nrt/faqs/
Looking for a walk-through? >> Excellent Instructional/How-To Videos: http://www.wugfresh.com/videos/
More information & Download Links: http://www.wugfresh.com/nrt/
Changelog: http://www.wugfresh.com/nrt/changelog/
Enjoy! ^_^
{{ WugFresh }}
Does automatically install Clockwork recovery?
danthepan124 said:
Does automatically install Clockwork recovery?
Click to expand...
Click to collapse
I believe it flashes TWRP recovery. Thats what I got from reading the change log here http://www.wugfresh.com/nrt/changelog/
Great job this looks awesome thank you for putting this together!
danthepan124 said:
Does automatically install Clockwork recovery?
Click to expand...
Click to collapse
If you check the "flash custom recovery" checkbox under root, then yes.. however it defaults to flash TWRP, unless the user selects CWM in the options menu:
It also will take care of renaming the system files to ensure its sticks, and it will install the busybox installer (free) app by Stericson.
{{ WugFresh }}
Nice. Will be nice to have this as a backup option . Definitely easier to use in terms of UI thank the Nexus 4 Root toolkit by mskip heh.
That backup option - is there a way, once unlocked and rooted, to grab my apps from the backup that were wiped, but not the entire thing? I downloaded about 8GB of apps before rooting, so I have no way to backup, I think. :[
Alright did it, rooted. Used the backup option a couple times trying to get it to work all the way, but for some reason, it only backed up about half of my apps.
The best rooting kit in the land
Sent from my Nexus 4 using xda premium
been waiting for this since the release of nexus 4, much thanks!
I've just added this toolkit to the Nexus 4 Complete Index
Sent from my GT-I9100 using xda premium
Just unlocked and rooted my N4 with this... great piece of software as always Wug, thanks Donated you some cash.
Hey guys quick two questions:
1) When I was unrooting through this toolkit, it said that there were three files that were not found in the directory, but continued to go through the process regardless, and it appears that I was successful. I can't remember the names as the command prompt ended before I had the chance to screenshot it. Am I okay?
2) If I go through the unrooting process through this toolkit, and then the OEM Lock process, does that basically put my phone back to the way it was when I received it?
Thanks!
Thanks for this, while I know my way around the manual commands okay, this will make everything a breeze for me tomorrow when my Nexus 4 arrives.
Will turn on, get the newest OTA, then unlock and root with your app.
Out of interest, can you still get OTA updates on stock with a custom recovery installed, or do you need to keep the stock recovery? I plan on sticking with stock until the custom ROMs get more stable, so I will stay on a default recovery if I can't use OTA updates. Otherwise I'll just flash a custom recovery with your app and get it done for future use.
This might be a dumb question.. But can I use this to root my Nexus 4 without unlocking the bootloader (thus wiping data)? Or has there not been a way found to do that yet?
BraydenJames said:
This might be a dumb question.. But can I use this to root my Nexus 4 without unlocking the bootloader (thus wiping data)? Or has there not been a way found to do that yet?
Click to expand...
Click to collapse
Have to unlock 1st. Just back up everything to your pc and restore it after.
Was waiting for this, thanks!
Sent from my Nexus 7
Night Galaxy said:
Hey guys quick two questions:
1) When I was unrooting through this toolkit, it said that there were three files that were not found in the directory, but continued to go through the process regardless, and it appears that I was successful. I can't remember the names as the command prompt ended before I had the chance to screenshot it. Am I okay?
2) If I go through the unrooting process through this toolkit, and then the OEM Lock process, does that basically put my phone back to the way it was when I received it?
Thanks!
Click to expand...
Click to collapse
1.) Yes, those are sig files. They are always missing. For whatever reason google doesn't include sig files in their packages and fastboot still checks for them. I guess google doesn't bother because they are redundant considering you need to be unlocked flash stock with fastboot. I can't suppress that output, so it just always will say that.. no worries.
2.) Yes, not basically.. exactly. Everything will be wiped, and you device will be exactly as it was when you received it.
{{ WugFresh }}
Audioboxer said:
Thanks for this, while I know my way around the manual commands okay, this will make everything a breeze for me tomorrow when my Nexus 4 arrives.
Will turn on, get the newest OTA, then unlock and root with your app.
Out of interest, can you still get OTA updates on stock with a custom recovery installed, or do you need to keep the stock recovery? I plan on sticking with stock until the custom ROMs get more stable, so I will stay on a default recovery if I can't use OTA updates. Otherwise I'll just flash a custom recovery with your app and get it done for future use.
Click to expand...
Click to collapse
No, you need the stock recovery. That said, in advanced utilities of the toolkit their is a button just for restoring stock recovery, so you can just do that if you want to when an OTA comes out (assuming you didn't make any other big system mods) if you had previously flashed a custom recovery. Also.. you can use temp recovery whenever you want as long as you have access to a computer with the toolkit.
{{ WugFresh }}
im having trouble unrooting my device....i get to the part where it says press ok to install please be patient, and then a command pops up but nothing happens, it just stays there...
edit: i keep getting to the Flash stock and Unroot screen, but nothing happens at that point! help!
Are these the steps to unlock and root and be able to receive OTA updates?
1. Click on "Full Driver Installation Guide"
2. Connect phone to computer
3. Click on Unlock
4. Click on Root and leave "Custom Recovery" box unchecked.
Then, after OTA updates are installed, re-click "Root" since OTA update will unroot?