http://www.droid-life.com/2011/08/25/droid3-1-click-easy-root-already-released/
This is a wonderful find. Easily rooted my Droid X running Gingerbread OTA 4.5.602.MB810.
Make sure you go to the originating thread sourced in the article (rootzwiki) to download the latest version (currently v7). The download link from that article goes to v5. You will also see from the source that the script works with Droid 3, Droid X, Droid X2, Cliq and Cliq 2.
Another tip I found was that each time the script restarts your phone (it does this 3 times), you must unlock the screen before it can continue.
Can anyone confirm or deny whether this roots the Droid X OTA Gingerbread?
Sent from my DROIDX using XDA App
infazzdar said:
Can anyone confirm or deny whether this roots the Droid X OTA Gingerbread?
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Yes. roots OTA .602.
So this does it? Even though its for Droid 3 run these same steps and it does the trick?
ktimque said:
So this does it? Even though its for Droid 3 run these same steps and it does the trick?
Click to expand...
Click to collapse
Yep, all droid devices running GB.
Fantastic. So once rooted on OTA will the ROMs that worked on the patched version work? Or do we need to wait for new ones?
That I can't answer sorry.
Ahh alright thanks though.
I'm having an issue. Have .602 and ran this. It went all the way through and says it was successful. I even see Superuser in the application drawer, but it's never popped up for Superuser Request" for permission and no rooted app works. Root Checker says the phone is not rooted.
What am I missing?
Here's a screenshot. It says "server not running" between Part 2 and 3 and then "remount successful". Not sure what that means, but I tried it again and it said the same thing.
{
"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"
}
dornstar said:
I'm having an issue. Have .602 and ran this. It went all the way through and says it was successful. I even see Superuser in the application drawer, but it's never popped up for Superuser Request" for permission and no rooted app works. Root Checker says the phone is not rooted.
What am I missing?
Here's a screenshot. It says "server not running" between Part 2 and 3 and then "remount successful". Not sure what that means, but I tried it again and it said the same thing.
http://pic100.picturetrail.com/VOL875/3165781/20548454/398233346.jpg
Click to expand...
Click to collapse
Did you make sure to unlock the screen every time it rebooted?
If one of the exploits don't go through, the whole thing fails. Server not running likely means it missed that step. You may just want to run it again.
It worked like a charm on my Droid X. Thanks to the developer !!!!
silversonic1 said:
Did you make sure to unlock the screen every time it rebooted?
If one of the exploits don't go through, the whole thing fails. Server not running likely means it missed that step. You may just want to run it again.
Click to expand...
Click to collapse
Did both and it didn't go through. Not sure what's up with it.
The article said they were having problems with previously rooted devices cause superuser was already installed. If you were previously rooted, try uninstalling SU, then try rooting it again. =)
ht tp://rootzwiki.com/showthread.php?t=3714 said:
WARNING for Droid X: Previously rooted DX owners who took an OTA update and then lost root should proceed with caution. This seems to only work flawlessly on SBF'd DX's or fully factory stock ones(read: never been rooted). The problem is with getting Superuser installed because it is already on your phone from when you were rooted previously.
Click to expand...
Click to collapse
Worked like a charm. My Droid x with gingerbread is now rooted. Now I can finally overclock it again.
Sent from my Droid X somewhere in the Bermuda Triangle.
This worked for me but not without problems.
When I ran the script, each time it rebooted the phone it would boot into the bootloader and nothing else would happen.
I read that some folks had success when they were in my situation (stuck in bootloader) I had to disconnect and reboot the phone myself manually between each of the three steps in the script that was supposed to automatically reboot the phone for me. So basically each time the script rebooted the phone into the bootloader I unplugged the usb cable, then rebooted the phone, then waited for the phone to finish booting up, then unlock the screen, and finally reconnect the usb cable. The script would see that the phone was connected again and it would continue on.
Hopefully this info helps some of you.
Stray_Bullet said:
The article said they were having problems with previously rooted devices cause superuser was already installed. If you were previously rooted, try uninstalling SU, then try rooting it again. =)
Click to expand...
Click to collapse
I am one of the ones having this problem, and I cannot remove superuser because I don't have root.
im currently rooted with the 4.5.602 pre-root on my droid-x
could someone be kind enough to tell me exactly what to do to get to the OTA 4.5.602 and rooted?
thanks
Got windows XP SP3 and when I try to run the exe file, get the error pop up saying it has a problem and whether or not to send info to microsoft. Any ideas why the exe won't run correctly?
m16-maniac said:
im currently rooted with the 4.5.602 pre-root on my droid-x
could someone be kind enough to tell me exactly what to do to get to the OTA 4.5.602 and rooted?
thanks
Click to expand...
Click to collapse
I was also on ota gingerbread and rooted. Because I read about users that already were rooted having problems I sbf'd back to froyo then got the official ota update from Verizon. I noticed after I rebooted after the latest official ota was installed that I still had SuperUser installed so I uninstalled SU before running this script. Aside from having to unplug the USB cable in between rebooted by the script this worked for me.
Related
My wife carries the orginal G-Tab and we did the 2.3 update when it became available OTA. Ever since this, the thing is in a violent loop of force closing to the point that she can not really use it. The FC pop ups are out of control.
Verizon will replace the unit, but I thought that since it worked perfectly up until the 2.3.5 OTA, it has to be something that did not work according to the plan with the OTA.
We have done a factory wipe and that did not help anything.
I am set up with ODIN3 and Heimdal on this PC, so If there is a way to push back to 2.2 so that I can try the OTA again, or if I can push a clean non borked 2.3 in that would likely solve the issue and not force me to send it back for a refurb as we purchased this new and up until the OTA have had no issue.
Thank you.
Am I out of luck on getting a stock image to push?
Sent from my HTC Thunderbolt 4G using Tapatalk.
here ya go! no need to go back to 2.2!
http://forum.xda-developers.com/showthread.php?t=1362016&highlight=stock
Yoshi, thank you very much for that link, but may I ask if there is also a non rooted version for if I needed to send the unit back to Verizon for warranty exchange? I would fear that the mighty VZW might attempt to deny warranty coverage on the device because it is rooted... As has been suggested to me over the phone from the customer support rep.
Sent from my HTC Thunderbolt 4G using Tapatalk.
larry0071 said:
Yoshi, thank you very much for that link, but may I ask if there is also a non rooted version for if I needed to send the unit back to Verizon for warranty exchange? I would fear that the mighty VZW might attempt to deny warranty coverage on the device because it is rooted... As has been suggested to me over the phone from the customer support rep.
Sent from my HTC Thunderbolt 4G using Tapatalk.
Click to expand...
Click to collapse
I posted a link to a heimdall file from droidforums.net that worked for me - look in this general forum for "vzw update fix" topic
Sent from my SCH-I800 using XDA App
U can easily un root it with superoneclick
Sent from my SCH-I800 using XDA App
YoshiFan501 said:
U can easily un root it with superoneclick
Sent from my SCH-I800 using XDA App
Click to expand...
Click to collapse
I pushed the stock image with root, but with Superoneclick V 2.2, I go to debugging mode and open the program, i do nothing else but click on Unroot. It goes through steps 1-7, then says install busybox pushfile, then it goes to installing busybox changemode and just stops.
What am I missing?
HTC Thunderbolt 4G using Tapatalk.
Ok, shut down both the pc and the galaxy tab, restarted both and opened up Superoneclick, clicked Unroot and it stopped at the same place.
This where I get to.
{
"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"
}
HTC Thunderbolt 4G using Tapatalk.
Honestly, just delete any root apparently like superuser titanium setcpu and the like if you need to return it. Think about it. These guys get HUNDREDS of rma devices a day. They aren't adbing or checking file systems for each one. They check it for water damage/physical damage then package and ship a refurbished model.
larry0071 said:
I pushed the stock image with root, but with Superoneclick V 2.2, I go to debugging mode and open the program, i do nothing else but click on Unroot. It goes through steps 1-7, then says install busybox pushfile, then it goes to installing busybox changemode and just stops.
What am I missing?
HTC Thunderbolt 4G using Tapatalk.
Click to expand...
Click to collapse
Sent from my LG-P999
Well, for warranty they now make you ship your defective unit in first and then they ship another unit out.
If they turn mine on, within 30 seconds they will see this, assuming they are even moderately intelligent.
I am worried that setting that in kernal will have them doing back flips and voiding the warranty.
HTC Thunderbolt 4G using Tapatalk.
And the update from 2.2 that it wants to install fails as expected because it sees that the thing is rooted. Not that the update is important, but it further indicates to them that I have issues related to a non stock system.
OK, this is what has me confused. I used the files from post #7 on this thread. I loaded in Heimdal, did it twice. Wiped before and after each time.
In his post #1 he talks about applying his update.zip, but that does not exist at his link any longer, nor does he repeat that step in post #7.
So downloading and running these files does throw me back to stock-ish 2.2, but the kernal shows rooted in the about device.
Superoneclick seems helpless for me. It goes so far and dies.
Getting frustrated!
larry0071 said:
OK, this is what has me confused. I used the files from post #7 on this thread. I loaded in Heimdal, did it twice. Wiped before and after each time.
In his post #1 he talks about applying his update.zip, but that does not exist at his link any longer, nor does he repeat that step in post #7.
So downloading and running these files does throw me back to stock-ish 2.2, but the kernal shows rooted in the about device.
Superoneclick seems helpless for me. It goes so far and dies.
Getting frustrated!
Click to expand...
Click to collapse
Use the instructions in this thread
http://www.droidforums.net/forum/sa...-how-flash-stock-rooted-ec02-froyo-2-2-a.html
This will bring you to stock version after dj11, and allow you to download and install verizon 2.3.5 official ota update - after flashing this version, go to settings, system updates, and you should be ready downloading update - follow on screen instructions and you will be good to go
Here is a set of heimdall files that will take you back to stock Verizon EC02 unrooted. Just unzip the file and put the appropriate files in each box. That means zimage in both kernel and recovery along with the other files in their boxes. I have used this many times and it definitely takes it back to stock.
Get the zip (EDIT: UPDATED LINK) here:
leapinlar said:
Here is a set of heimdall files that will take you back to stock Verizon EC02 unrooted. Just unzip the file and put the appropriate files in each box. That means zimage in both kernel and recovery along with the other files in their boxes. I have used this many times and it definitely takes it back to stock.
Get the zip (EDIT: UPDATED LINK) here:
Click to expand...
Click to collapse
That link goes to a DL page but I can not DL it. Can you drop box it for me?
I've downloaded 8 supposedly stock non-rooted VZW Glaxy Tab heimdal packages, and every one of them leaves me rooted with Kernal version 2.6.32.9 [email protected] #3. I really want rid of this so that I do not get burned when I send it in.
What I have tried so far today to get rid of root:
Real_Stock_for_galaxy_tab
Verizon-GTab-Stock-non-root
VZW.2.3.5.Stock.Root
I also tried SuperOneClickv2.2-ShortFuse, but this freezes on my tablet about 8 or 10 steps into the Unroot process.
Anyone know how to get my Kernal to show up as stock?
I went in to your DL link with Chrome and it worked. FOr some reason... IE did not play nice with that Megashares. I'll try yours and let you know what happens.
Larry
OK, the version you provided (SCH-I800_VZW_EC02.zip) does also still show the kernal as 2.6.32.9 [email protected] #3 and it also has SuperUser in the application lists.
So, I give up. I went back to one of the ROMs that has the kernal still listed as rooted but does not have SU installed or anything that is obviously indicating root.
I will send it in, and cross my fingers. Lets hope the guys getting in warranty exchange hardware do not take the time to really look, or I am screwed, blued, and tatooed.
I see no signs of rooting on that page. Or do you mean the [email protected] part? That's normal, and shows on an unrooted device as well! I don't have a VZW (mine's a European GSM), but my Tab is 100% original and unrooted, and it shows Kernel version 2.6.35.7 [email protected] #2. For an ordinary user it's actually not that simple to see if a Tab is rooted. One sign that may show is the presence of the app SuperUser. If you've rooted your Tab with SuperOneClick, it will be present as a system application which you can't remove by ordinary means. You can tell if a ROM is UNrooted by installing an app that needs root and running it, it will complain it needs root.
So the unrooted ROM's you tried may well actually have been unrooted if all you checked is the root part in the Kernel Version!
My wife got me a brand new A500 off ebay a couple of months ago for a Christmas gift(for me it's only three days old). So far I love it but it will not take the OTA update that it keeps bugging me about. The download starts fine but then stalls out mid download. I looked here http://forum.xda-developers.com/showthread.php?t=1113878 but did not see my current version there. Can anyone point me in the direction of the OTA I need to download and flash with recovery? My build is Acer_a500_1.145.09_com_gen1 I'm running 3.0.1. It looks like it's trying to download 4.010.11.
Further info:
According to the log the file name is Acer_A500_1.145.09_4.010.11_com_gen1_1311243587838_bd1ab95c.zip
I can't find that file anywhere on the net.
The reason I would suspect is because someone replaced the stock recovery? Off eBay you say, was it brand new and never used? It sounds like it was used or someone tampered with it?
If that's not the case, then you can just install the update manually. Download the update you want and put it on your external SDCard and then enter recovery (using power and volume). The recovery will install the update for you.
timmyDean said:
The reason I would suspect is because someone replaced the stock recovery? Off eBay you say, was it brand new and never used? It sounds like it was used or someone tampered with it?
Click to expand...
Click to collapse
It said it was brand new. My wife would not buy something like this used. The weird thing is it knows it has an update and it starts to download and get's up to half way downloaded and then it just stops. It shows that it still is pulling data but the downloaded file size doesn't increase anymore after it stalls.
Ive been looking into rooting it and since I'm on 3.0.1 it appears Gingerbreak is all I need. The next question is what rom should I get and how do I go about installing it? I've never rooted droid before and most instructions on XDA are written for the experienced level and not the new guy. I'd like to stay fairly stock but rooted.
Sent from my A500 using Tapatalk
There are reports of others having the same issue. They say that a soft reset often fixes it.
You can use my tool to flash in 3.2.1 which is rooted. http://forum.xda-developers.com/showthread.php?t=1307539&page=14
timmyDean said:
There are reports of others having the same issue. They say that a soft reset often fixes it.
You can use my tool to flash in 3.2.1 which is rooted. http://forum.xda-developers.com/showthread.php?t=1307539&page=14
Click to expand...
Click to collapse
Just to make sure I'm getting it right: I go here http://forum.xda-developers.com/showthread.php?p=20680452 download that to my PC and follow the instructions contained within and I end up with a stock rooted 3.2.1? I don't need to download anything else right? A soft reset for this tab is pusing the little red button on the end by the USB port?
Sent from my A500 using Tapatalk
Yes, if you want to flash 3.2.1 stock with root read the instructions in the download. The download has everything in it.
The soft reset everyone talks about is using the paperclip in that little hole next to the USB port.
timmyDean said:
Yes, if you want to flash 3.2.1 stock with root read the instructions in the download. The download has everything in it.
The soft reset everyone talks about is using the paperclip in that little hole next to the USB port.
Click to expand...
Click to collapse
Sweet. You're a life saver. Thanks for translating it all to noob for me. Will I need to reinstall all of my apps and such afterwards?
Sent from my A500 using Tapatalk
Yes, the flashing tool makes it just like new, out of the box, but with root.
timmyDean said:
Yes, the flashing tool makes it just like new, out of the box, but with root.
Click to expand...
Click to collapse
OK that's not a big deal. The SD card will remain intact though right?
Sent from my A500 using Tapatalk
Jds method does work. But you can also trybthis.
http://forum.xda-developers.com/showthread.php?t=1410802
Simple easy no computer needed
timmyDean said:
Yes, the flashing tool makes it just like new, out of the box, but with root.
Click to expand...
Click to collapse
I tried your method and I get stuck at the serial number part. It says ADB server out of date. What do I do?
{
"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"
}
Edit: Never mind. I got my steps out of order. I was clicking next before running test.cmd
Last edit: It appears to have worked. I'm back to the initial setup screens just like when I first got it.
So this is what I did. (My 1st time)
-Download/update drivers
-attached phone via usb
-turn on usb debugging
-open super one click
-clicked on root
And this is what I got, nothing happened after 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"
}
Any help will be appreciated.
Thanks!
change Exploit Auto to psneuter and give a feedback, if any messege that it is not a proper way, click continue. It depends on your defy ROM
Android version
Which version do you have?
2.2 froyo or 2.3 gingerbread?
Just isr gingerbreak.apk
Sent from my MB525 using XDA
corrinti said:
change Exploit Auto to psneuter and give a feedback, if any messege that it is not a proper way, click continue. It depends on your defy ROM
Click to expand...
Click to collapse
Thanks! that did it for me.
I am having the same problem, but your suggestion failed to get the root to work. It just hangs at "Shell Rooting Device #7 and the software goes "Not responding" (Win 7 64 bit).
I also tried setting the exploit to zergRush with the same result.
As a matter of interest, DoomLord's Version 4 also fails with a number of errors writing files.
I had stuffed up a flash to ICS by flashing the Kernel (I was confused as to why the step was there is it was ????not needed.)
I managed to get a UK Defy+ .sbf file to install, but now I can't root it to allow me to revert to the Nandroid backup I did.
Any suggestions would be most welcome!!!! HELP...........
Cheers
John in Sunny Carnarvon, Western Australia
jblyth said:
I am having the same problem, but your suggestion failed to get the root to work. It just hangs at "Shell Rooting Device #7 and the software goes "Not responding" (Win 7 64 bit).
I also tried setting the exploit to zergRush with the same result.
As a matter of interest, DoomLord's Version 4 also fails with a number of errors writing files.
I had stuffed up a flash to ICS by flashing the Kernel (I was confused as to why the step was there is it was ????not needed.)
I managed to get a UK Defy+ .sbf file to install, but now I can't root it to allow me to revert to the Nandroid backup I did.
Any suggestions would be most welcome!!!! HELP...........
Cheers
John in Sunny Carnarvon, Western Australia
Click to expand...
Click to collapse
Ok, but which CG version you have? Which UK Defy + sbf you mounted and what defy u use?
If it is CG7 version then to root try acc. to http://forum.xda-developers.com/showthread.php?t=1595013 (helpful esp. for defy red and defy +)
addu said:
Thanks! that did it for me.
Click to expand...
Click to collapse
So you are welcome to hit a thanks button ;-)
Sure but i cant find a thanks button when i use xda android application.
Can you also give some info about custom roms? I'm planning to flash to Cm7, should i go ahead or Cm9 / Miui is better?
Sent from my MB525 using XDA
Custom ROMs are something very personal, so my opinion is only mine ;-)
I love CM7 as it is (not only my opinion) the fastest one and all works fine.
CM9 looks nicer but still lacks some features and has some bugs, and is much slower than CM7.
So my proposal is to start with last official CM7 http://get.cm/ choose jordan device or quarx' last nightly from the first post of http://forum.xda-developers.com/showthread.php?t=1033654
I switched to CM9 of quarx or epsylon several times but each time went back to CM7.
Depending on your device (red or green) take care which kernel you use for CM9.
If you like MIUI or WIUI or some other interfaces, you can also try.
In future i recommend using Doomlord's one click root..its very simple..
just double click the file and ur phone is rooted
Resolved issue with SuperOneClick Tool not responding.
jblyth said:
I am having the same problem, but your suggestion failed to get the root to work. It just hangs at "Shell Rooting Device #7 and the software goes "Not responding" (Win 7 64 bit).
Click to expand...
Click to collapse
I had a similar issue when I was trying to root my Defy from Win 7 (32bit), after a few tries, I switched over to my wife's laptop which is on Win XP SP2.
Installed the ADB drivers, connected the Defy through USB (while USB debugging option was checked).
Clicked on 'Root' in the SuperOneClick Tool window.
In about a minute or so the process was done.
The phone was rebooted by the application once in the process.
And now I have a rooted device.
Used SuperOneClick 2.3.3
Hi everyone, posting this as a information about something you should NOT try: upgrade your OTA rom with custom recovery installed, in my case TWRP.
I did this with ignorance of not think that (or search about) the custom rom could interfere at the normal process of OTA upgrade from Lollipop to MarshMallow. Actually I remembered that I was unlocked and rooted the phone but I did not remember I was using custom recovery. AFAIK at this device is impossible to root without unlocking and custom recovery.
{
"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 you are on TWRP don't do this!
For those don't know about TWRP and OTA updates, read this:
https://twrp.me/faq/officialota.html
In short terms: don't try OTA updates (official updates) if you installed custom rom such as TWRP. "Installing official updates from your manufacturer or carrier is not supported by TWRP." "[This] may result in unexpected behavior" "Most of the time the best way to get a new update onto your device is to simply wait a couple of days for ROM makers for your device to come up with ROMs that are based on the new update that you can safely and easily install."
But I did it. And now I'm reporting it for those who are curious. So, what's happened?
Fortunately the device is not bricked as I thought when it reboot to TWRP for flashing the OTA update instead of the stock recovery process! I thought that I messed everything when I see the frozen TWRP for something about 10 minutes or less. After the long 10 minutes of frozen TWRP image I got the recovery working and checked the log:
Of course, errors on the log.
Rebooted and got a frozen background image, after a while a permanent black. When the screen turn off the notification system shows the battery as dead (and it as not). But I could turn it off and gain access to the recovery holding power and volume down buttons.
After two failed reboots to the system with the same result I tried to make a screenshot using the hard buttons and it works (screenshoted the black screen) and suddenly the lock screen shows up. I got into, everything working slow meaning that there was a lot things working in the background. Got some error messages from google service and MMS/SMS communication and minutes later it automatically reboots and booted the TWRP again.
This turned to a loop. I stopped this by going to the system setup - about the device - check for updates. And got a message "the update has failed". Good. After a while the message offering the update shows again... No, thanks...
I rebooted to TWRP and fixed the permissions, maybe this solve some problems.
Right now the phone is working but the rebooting process has unexpected behaviors, some tries result in a normal fast process and other tries result in a long black image and the system/launcher just don't arm up for some minutes, but after a while it works. I'm not confident. Already backed up apps with Titanium backup.
I'm planning to restore everything from the stock using this guide:
http://forum.xda-developers.com/mot...e-restore-moto-e-2015-stock-firmware-t3054303
And them, maybe, update the OTA to marshmallow. Before doing that, I will search and get to know if it is possible to re-root the phone with marshmallow in osprey (that means re-unlock and install TWRP again). Rooted device it's a need for me.
This is what happened to my device when tried to OTA update with TWRP. I had luck not bricking this.
+1 on the dumb attempt. Early morning, excited for the release, upgrade please! Yeah, no good. Is restoring our only option? Seems the upgrade has not even started so what about deleting the downloaded image file or trying to kill the process attempt?
did you really had to make a new thread with that huge wall of text? haha come on man, common knowledge that to take the OTA you need stock recovery ?
Sent from my Nexus 6 using Tapatalk
Seems the upgrade has not even started so what about deleting the downloaded image file or trying to kill the process attempt?
Click to expand...
Click to collapse
Yeah, DON'T proceed with the update! Deleting the downloaded files just break the process... My advise is to make a backup before deleting this.
sgloki77 said:
did you really had to make a new thread with that huge wall of text? haha come on man, common knowledge that to take the OTA you need stock recovery
Click to expand...
Click to collapse
Ok, sorry about the huge wall of text.
No need to adb stock image. A simple factory reset worked for me. Next time will have more caffiene before attempting anything major with my phone.
golgiapp said:
No need to adb stock image. A simple factory reset worked for me. Next time will have more caffiene before attempting anything major with my phone.
Click to expand...
Click to collapse
:good:
Good to know that a factory reset could fix the problems caused by the OTA update with TWRP. But after this it should remain with custom recovery and not possible to OTA update. for stock MM
i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??
gonzodesigns said:
i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??
Click to expand...
Click to collapse
Not sure, but take a look at /cache
gonzodesigns said:
i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??
Click to expand...
Click to collapse
/data/data/com.motorola.ccc.ota/app_download
hp420 said:
/data/data/com.motorola.ccc.ota/app_download
Click to expand...
Click to collapse
found it!!
thanks extracted ok !!
its a zip flashable,can it be converted to install like the oem recovery images using the adb method?
gonzodesigns said:
i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??
Click to expand...
Click to collapse
Thank you for the warning
---------- Post added at 12:58 AM ---------- Previous post was at 12:54 AM ----------
Thank you for the warning
I experience this today, I flashed a stock rom again so I can have the OTA update, but what I can't do is root my device, I flash the custom recovery and then I flash the beta version of SuperSU, and when I reboot my device it bricks in the Motorola Logo, anybody knows how to fix this, or should I wait a little bit longer to root my phone? as the OP I need root too
Use the latest 2.62 superSU zip. And never root with the TWRP option before reboot.
Sent from my MotoG3 using Tapatalk
nelsonw said:
Use the latest 2.62 superSU zip. And never root with the TWRP option before reboot.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Never done that, I tried flashing the superSU 2.52 from a bunch of tutorials I found on Google, but all it does is bricking my phone on the Motorola Logo, then I have to do all the downgrade and update process again
VicSanRED said:
Never done that, I tried flashing the superSU 2.52 from a bunch of tutorials I found on Google, but all it does is bricking my phone on the Motorola Logo, then I have to do all the downgrade and update process again
Click to expand...
Click to collapse
this is a known issue with the mm update. Use 2.61 or newer, only. These are the new systemless root zips.
hp420 said:
this is a known issue with the mm update. Use 2.61 or newer, only. These are the new systemless root zips.
Click to expand...
Click to collapse
I tried with the latest version 2.66 and still the same issue. Don't know what to do now.
So its posible to root MM ?? Safe ,stable?
Supersu v 2.62??
Yeah, 2.62 is the only one working. This worked for me BETA-SuperSU-v2.62-20151210170034
Sent from my MotoG3 using Tapatalk
nelsonw said:
Yeah, 2.62 is the only one working. This worked for me BETA-SuperSU-v2.62-20151210170034
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Can you post a little tutorial?, I wanna be sure I'm doing everything OK.
Easy way to root HH6No Computer needed, just one simple apk and about 10 minutes of your precious Time
1st step: Own Huawei Honor 6
2nd step: Download and install This app
(Remember to allow unknown sources in settings)
3rd step: Launch it, it will say "not supported" but gives you a chanse to give it a go anyway. So do that. It will start rooting. App may close several times but it will not crash. Just open it again from " recent apps" and it will roll again.
Wait for 100% and rooting is done.
Posting pics soon.
You are welcome
{
"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"
}
I don't need to unlock the bootloader first?
Can the rooting be reversed? Is this safe?
Lotroni said:
I don't need to unlock the bootloader first?
Can the rooting be reversed? Is this safe?
Click to expand...
Click to collapse
No unlocking needed, perfectly safe and unroot can be done with same app. (Screenshot of that included in this post)
Spoiler
Sent from my H60-L04 using XDA-Developers mobile app
So I wanted to root my Honor 6, mainly because for Adaway.
This one click root actually worked for rooting(first time got hung up maybe because I lost wifi connection for a while?) but worked when I run it again. The uninstalling got hung up too but it worked after second try I think.
This root wasn't enough for adaway for S-On and S-OFF I think, so I had the bootloader unlocked, got clockwork recovery and tried to root with HONOR Multitool. With multitool rooting with SuperSU it says I need to update SU binary, and I couldn't figure out how to do that. Then I tried rooting again with this one click and it now the Adaway works too so yay and thanks.
Lotroni said:
So I wanted to root my Honor 6, mainly because for Adaway.
This one click root actually worked for rooting(first time got hung up maybe because I lost wifi connection for a while?) but worked when I run it again. The uninstalling got hung up too but it worked after second try I think.
This root wasn't enough for adaway for S-On and S-OFF I think, so I had the bootloader unlocked, got clockwork recovery and tried to root with HONOR Multitool. With multitool rooting with SuperSU it says I need to update SU binary, and I couldn't figure out how to do that. Then I tried rooting again with this one click and it now the Adaway works too so yay and thanks.
Click to expand...
Click to collapse
Thanks for feedback and and good to hear it worked [emoji4]
Sent from my H60-L04 using XDA-Developers mobile app
IMO kingroot is terrible.
a lot of adds and pop up, and it's so unclean.
I've tried to remove it, can't.
I've tried to replace it with SuperSU, can't.
I ended up flashing a new rom to get rid of this.
SM26 said:
IMO kingroot is terrible.
a lot of adds and pop up, and it's so unclean.
I've tried to remove it, can't.
I've tried to replace it with SuperSU, can't.
I ended up flashing a new rom to get rid of this.
Click to expand...
Click to collapse
Yes, i kinda agree with you. It cant be replaced with other root app ( i also tried many times) but this is most likely fastest and easiest way to obtain root acces with honor 6. I havent seen any adds or pop-ups while using kingroot doe. I just deleted purify and disabled all i didnt like in kingroot settings.
Its ok and it can easily be removed and replaced with supersu. Either through terminal or by apps like supersu me.
If you cant replace it, you didnt search enough.
/edit
Ok, Honor strikes again [emoji23]
leechseed said:
Its ok and it can easily be removed and replaced with supersu. Either through terminal or by apps like supersu me.
If you cant replace it, you didnt search enough.
Click to expand...
Click to collapse
I have replaced it with other phones, but with honor, it just doesnt work, it just removes root but supersu stucks abd doesnt grant sudo access. Kingroot itself isnt that bad but supersu is awesome.
Not quite a developer yet, trying tho
Managed to Root my H60-L04 Android M
Hi,
finally managed to root my H60-L04 Android M (B810) via:
http://www.pantomath.xyz/honor-6-root-guide-marshmallow-emui-4-0-twrp/
Really easy, and without any issues
apatrahil said:
Hi,
finally managed to root my H60-L04 Android M (B810) via:
http://www.pantomath.xyz/honor-6-root-guide-marshmallow-emui-4-0-twrp/
Really easy, and without any issues
Click to expand...
Click to collapse
this look just like SRK tool....
Sent from my H60-L12 using Tapatalk
Ranteis said:
Easy way to root HH6No Computer needed, just one simple apk and about 10 minutes of your precious Time
1st step: Own Huawei Honor 6
2nd step: Download and install This app
(Remember to allow unknown sources in settings)
3rd step: Launch it, it will say "not supported" but gives you a chanse to give it a go anyway. So do that. It will start rooting. App may close several times but it will not crash. Just open it again from " recent apps" and it will roll again.
Wait for 100% and rooting is done.
Posting pics soon.
You are welcome
Click to expand...
Click to collapse
kingroot not installed...any ideas??? already install before but its keep crash and unroot itself...i try uninstall and try to do again but kingroot cant be installed...
mrconfius said:
kingroot not installed...any ideas??? already install before but its keep crash and unroot itself...i try uninstall and try to do again but kingroot cant be installed...
Click to expand...
Click to collapse
You have honor 6 L04?
Android version?
Unistalled kingroot before trying again?
Ranteis said:
You have honor 6 L04?
Android version?
Unistalled kingroot before trying again?
Click to expand...
Click to collapse
yeah h06-L04..
emui 4.0 android 6.0
yeah...already uninstalled it and trying again..but not working..app not installed
Same issue
I have h60-l04
Android 6.0
Emui 4.0
I tried rooting but it does not allow me to do so i says theres no root stg for this phone and reguest gor this module
Is there a away to bybass that??
I hope some could help me to root this phone:crying:
Zeyzed said:
I have h60-l04
Android 6.0
Emui 4.0
I tried rooting but it does not allow me to do so i says theres no root stg for this phone and reguest gor this module
Is there a away to bybass that??
I hope some could help me to root this phone:crying:
Click to expand...
Click to collapse
same w/ u but now i using EMUI 4.0.1 kingroot not supported w/ this version:crying:
As in instructions, it says device not supported BUT it gives you option to try anyway. And it works