I'm really having one hell of a time figuring out the most correct steps to rooting the verizon model. What I've always done upon attempting to root a new device is read all available information and decide from there. Between XDA, Reddit, Rootz and YouTube, I have no freaking idea which one is the most tried and true. My previous devices (Nexus 4 and Galaxy Nexus) were a walk in the park - even the droid X2 was a little easier to sift through and I faced less risk of very much destroying something. And after reading roughly 50 pages of threads here, I'm chalking most of this up to the device's immaturity. Regardless, there are people who have tried, succeeded and failed.
New folks need to hear what does and doesnt work in the most clear way possible and thats what I'm asking - what works, what doesnt work, what should I not even bother reading?
SlapMyMoto
nhizzat said:
SlapMyMoto
Click to expand...
Click to collapse
This.
Don't ask any questions, just follow the steps to the letter and you will be fine. I'm on a VZW model that I had to downgrade, and kept asking question after question.
You lose stock custom recovery forever, that's the risk on a non-dev-edition.
jl33 said:
I'm really having one hell of a time figuring out the most correct steps to rooting the verizon model. What I've always done upon attempting to root a new device is read all available information and decide from there. Between XDA, Reddit, Rootz and YouTube, I have no freaking idea which one is the most tried and true. My previous devices (Nexus 4 and Galaxy Nexus) were a walk in the park - even the droid X2 was a little easier to sift through and I faced less risk of very much destroying something. And after reading roughly 50 pages of threads here, I'm chalking most of this up to the device's immaturity. Regardless, there are people who have tried, succeeded and failed.
New folks need to hear what does and doesnt work in the most clear way possible and thats what I'm asking - what works, what doesnt work, what should I not even bother reading?
Click to expand...
Click to collapse
I am in the same boat after recently getting a Moto X and coming from a Galaxy Nexus that seemed to have more consensus, or least clearly indicated. It was a bit daunting to trying to start to learn the process again after over 2 years.
User dray has got you covered though regardless of what Moto X you are using and what version of Android you are on. Go here http://forum.xda-developers.com/showthread.php?t=2603358 and thank dray for his efforts.
I recently finished rooting my xt1060 starting at 4.2.2 and could show you what I did if you are in the same boat.
You can't compare a nexus to a device with a boot loader that can't be unlocked. A little research before purchasing would have shown you that its not as easy to root.
If you had a Moto x with an unlockable boot loader...then it would be just as easy as a nexus to root. Same steps in fact. So its not device immaturity ....its the fault of the particular one you bought.
Just saying.
Sent from my Moto X cellular telephone...
kj2112 said:
You can't compare a nexus to a device with a boot loader that can't be unlocked. A little research before purchasing would have shown you that its not as easy to root.
If you had a Moto x with an unlockable boot loader...then it would be just as easy as a nexus to root. Same steps in fact. So its not device immaturity ....its the fault of the particular one you bought.
Just saying.
Sent from my Moto X cellular telephone...
Click to expand...
Click to collapse
slapmymoto
Just saying.
syntrix said:
slapmymoto
Just saying.
Click to expand...
Click to collapse
That's nothing like the unlocked boot loader method...which is the same as the nexus method. And I can see how it intimidates new people.
So maybe quit quoting me with smart ass comments all over this forum and read the opening posts a bit more carefully.
He knows about slap ....its just a chore was his point...compared to flash recovery in fastboot...say yes to fix root.....reboot and done. Lol
Do us both a favor and put me on your ignore list....before this escalates.
Sent from my Moto X cellular telephone...
jl33 said:
I'm really having one hell of a time figuring out the most correct steps to rooting the verizon model. What I've always done upon attempting to root a new device is read all available information and decide from there. Between XDA, Reddit, Rootz and YouTube, I have no freaking idea which one is the most tried and true. My previous devices (Nexus 4 and Galaxy Nexus) were a walk in the park - even the droid X2 was a little easier to sift through and I faced less risk of very much destroying something. And after reading roughly 50 pages of threads here, I'm chalking most of this up to the device's immaturity. Regardless, there are people who have tried, succeeded and failed.
New folks need to hear what does and doesnt work in the most clear way possible and thats what I'm asking - what works, what doesnt work, what should I not even bother reading?
Click to expand...
Click to collapse
here is a complete guide that i made up hope it helps
http://forum.xda-developers.com/showthread.php?t=2603358
syntrix said:
This.
Don't ask any questions, just follow the steps to the letter and you will be fine. I'm on a VZW model that I had to downgrade, and kept asking question after question.
You lose stock custom recovery forever, that's the risk on a non-dev-edition.
Click to expand...
Click to collapse
Slap was one of the first methods I read about but I was then told that if I ignored the WP fix (like some of the guides leave out), Id have to go into recovery, and then reboot just to make changes to /system, which seems ridiculous. Correct me if I'm wrong.
dray_jr said:
here is a complete guide that i made up hope it helps
http://forum.xda-developers.com/showthread.php?t=2603358
Click to expand...
Click to collapse
I appreciate that thank you.
jl33 said:
Slap was one of the first methods I read about but I was then told that if I ignored the WP fix (like some of the guides leave out), Id have to go into recovery, and then reboot just to make changes to /system, which seems ridiculous. Correct me if I'm wrong.
I appreciate that thank you.
Click to expand...
Click to collapse
np at all let me know if you have any issues
I did it with twrp-2.6.3.1-ghost-4.4.img, i flash it in fastboot, enter the recovery, go to reboot/system, select root, reboot and you are rooted, its simple, its work for me in 4.2.2, 4.4 and 4.4.2
---------- Post added at 02:36 AM ---------- Previous post was at 02:34 AM ----------
if you can read spanish (or translate the page)
http://www.htcmania.com/showthread.php?p=12297991#post12297991
here's everything to change modem, recovery, root and even change the bootloader ulnock logo at the start
rivas1981 said:
I did it with twrp-2.6.3.1-ghost-4.4.img, i flash it in fastboot, enter the recovery, go to reboot/system, select root, reboot and you are rooted, its simple, its work for me in 4.2.2, 4.4 and 4.4.2
---------- Post added at 02:36 AM ---------- Previous post was at 02:34 AM ----------
if you can read spanish (or translate the page)
http://www.htcmania.com/showthread.php?p=12297991#post12297991
here's everything to change modem, recovery, root and even change the bootloader ulnock logo at the start
Click to expand...
Click to collapse
Unfortunately, that method is for unlocked bootloaders
Try it anyways you dont loose anything trying
Enviado desde mi XT1058 mediante Tapatalk
rivas1981 said:
Try it anyways you dont loose anything trying
Enviado desde mi XT1058 mediante Tapatalk
Click to expand...
Click to collapse
Guaranteed it won't work . Otherwise no one would ever unlock their boot loaders.
Sent from my Moto X cellular telephone...
syntrix said:
This.You lose stock custom recovery forever, that's the risk on a non-dev-edition.
Click to expand...
Click to collapse
Not forever. And what's a stock custom recovery? The only thing you lose "forever" is write protection if you use MotoPwnNoMo.
jl33 said:
Slap was one of the first methods I read about but I was then told that if I ignored the WP fix (like some of the guides leave out), Id have to go into recovery, and then reboot just to make changes to /system, which seems ridiculous. Correct me if I'm wrong.
Click to expand...
Click to collapse
I don't find it to be ridiculous at all. Rebooting into "recovery" adds maybe a minute to the whole process.
I'd like the same question as OP answered for the 1053 version. It really grinds my gears that there aren't separate forums for the different versions like they did with the variants of every other god damn phone (Galaxy Nexus as an example).
Sent from my XT1053 using XDA Premium 4 mobile app
elpeterson said:
I'd like the same question as OP answered for the 1053 version. It really grinds my gears that there aren't separate forums for the different versions like they did with the variants of every other god damn phone (Galaxy Nexus as an example).
Sent from my XT1053 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Why do they need separate forums? They all use the same root exploit with firmware specific to their model. There isn't enough development to justify separate forums.
Unlocking the bootloader is the same across the board as is rooting a locked bootloader. The only thing that differs in the entire process is the firmware.
nhizzat said:
Why do they need separate forums? They all use the same root exploit with firmware specific to their model. There isn't enough development to justify separate forums.
Unlocking the bootloader is the same across the board as is rooting a locked bootloader. The only thing that differs in the entire process is the firmware.
Click to expand...
Click to collapse
this phone is very simple let me break it down for you
locked bootloader
unlocked bootloader
lock need to use slapmymoto
unlocked and just install TWRP then install SUPERSU via custom recovery.
my guide tells you what phones can unlock there bootloader and what ones can't.
Related
Hey folks, i know that for some, unlocking bootloaders and rooting for the first time can be a bit overwhelming, so i put together a video, walking you through step by step. I hope this helps at least 1 of you
The toolkit in this video guide was developed by hasson2000, so big props and thanks go out to him! You can find his toolkit here
To the moderators. hasson2000 has asked that folks request his permission to use his work in posts ect.. So i did ask, but he never responded... So since this is doing no harm and only helping people, i assume you won't mind this posted here If you do want to take it down, i won't fight you on it.
If you folks have any questions, i strongly recommend you go to hasson2000s toolkit thread, linked above, and ask there.
Cheers
Very Helpful
I'm still stuck on waiting for device.
I was going in that Tool thread but I'm not allowed to post there yet.
Sent from my HTCONE using Tapatalk 2
Nice. Thanks much!!
Thank you so much for the vid, I used it to unlock my bootloader and also installed TWRP... It worked a treat
My issue is that I want to flash the 1.29 OTA onto my EE-branded 4G HTC One. I've downloaded this version: OTA_M7_UL_JB_50_HTC_Europe_1.29.401.12-1.28.401.7_release_315849_signedp7vl8dqsvls0h1t0.z ip from this thread: http://forum.xda-developers.com/showthread.php?t=2207874. I have attempted to Flash my own recovery, but am unsure as to which .img file to use and also which option in the bootloader to select. I've searched all throughout these forums, but to no avail
If anyone can help, it would be much appreciated.
Many thanks
any one have any alternative link to the all in one toolkit by hasoon looks like the link is broken?
aaroh said:
any one have any alternative link to the all in one toolkit by hasoon looks like the link is broken?
Click to expand...
Click to collapse
right here
Thanks, this worked like a charm!
This is my first Android phone and reading all of this did seem scary, but watching the video and doing it myself.. pretty easy!
So, there is no way to root this device without unlocking it first? I've also read that after you unlock, you loose some apps & obviously OTA updates......4.2.2 is rumored to be out for this device any time now. Is there anyway to preserve those apps, possibly update phone (even manually) or just root without unlocking?
P05TMAN said:
So, there is no way to root this device without unlocking it first? I've also read that after you unlock, you loose some apps & obviously OTA updates......4.2.2 is rumored to be out for this device any time now. Is there anyway to preserve those apps, possibly update phone (even manually) or just root without unlocking?
Click to expand...
Click to collapse
you won't loose any apps if you unlock, you will lose all of your files though... and you can still receive OTAs is you are unlocked, you just need to have the stock rom and a stock recovery...
Success (relatively painless)
I'd like to add my success story as a hopeful note for other noobs who are sweating it.
I'm a complete noob with recovery and rooting. Luckily I had the distinct advantage of skipping the whole bootloader unlocking sequence, thanks to having the Developer Edition whose bootloader comes unlocked. (I wasn't sure if I should use Hasoon2000's T-Mobile kit, since I'm using a T-mo SIM, or if I should use his generic HTC One M7 kit, so I chose the latter and luckily it was a good choice.)
I studied this video tutorial by TheSmokingAndroid, took notes, watched it again, said a little prayer to the green guy in the sky, watched some more tutorials, read some tutorials, read 50 pages of xda forums, panicked, de-panicked, steeled myself, then watched the video again. Then I dove in.
While not every step had the exact results that TheSmokingAndroid depicted in his video (combination of user error by me and the HTC One apparently being somewhat finicky), while not every step was an exact match, a little persistence and staying calm resulted in full root in about 1/2 an hour once I actually got started, and no major calamities.
So thanks TheSmokingAndroid and thanks Hasoon2000!
(If you're a noob, consider making a small donation like I did to keep these guys going.)
Happy rooting.
matt95 said:
you won't loose any apps if you unlock, you will lose all of your files though... and you can still receive OTAs is you are unlocked, you just need to have the stock rom and a stock recovery...
Click to expand...
Click to collapse
So you won't loose torch and some of the other apps I've read you may lose after unlocking?
Sent from my HTC One using xda app-developers app
P05TMAN said:
So you won't loose torch and some of the other apps I've read you may lose after unlocking?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
no, you won't
TheSmokingAndroid said:
To the moderators. hasson2000 has asked that folks request his permission to use his work in posts ect.. So i did ask, but he never responded... So since this is doing no harm and only helping people, i assume you won't mind this posted here If you do want to take it down, i won't fight you on it.
Click to expand...
Click to collapse
I receive tons of PMs and can forget who I responded to, since I am on my phone majority of the time. Anyone is allowed to make a video using my toolkit. I just do not permit people to repost my work on another site. All official toolkit threads will be on XDA and all the toolkits will be uploaded to ONLY my Dev-Host account. I do not authorize mirrors of my toolkits (since anyone can just repack it with a virus and blame me for it). However, my apologies if I did not get back to you. I usually wake up with 10 - 15 PMs, plus more throughout the day!
Shad0wStorm said:
Very Helpful
Click to expand...
Click to collapse
I used that tool yesterday to root mine. I wish I knew of this video though. The device is finicky when trying to get a root!!
HTC One (China model) htc 802w
Getting into the China model of HTC One (htc 802w) bootloader and recovery.
It should work for any model as well.
factory reset
Hi, I recently unlocked my bootloader and rooted my HTC One and flashed the cyanogen rom. However, I want to now go back to the original software that came with my phone, but I did not backup my phone on twrp recovery. I do not care about my user data, I just want to go back to HTC Sense. Could anyone help me go back to the factory default os reset? Also my phone is from T-mobile if that helps.
I'd personally like to know how to pull the stock recovery image from my device for later use, rather than using someone else's. I've already searched but I'm directed to the stock recovery image already posted here. Isn't there a way to make the image flashable rather than pushing it through with ADB?
TheSmokingAndroid said:
Hey folks, i know that for some, unlocking bootloaders and rooting for the first time can be a bit overwhelming, so i put together a video, walking you through step by step. I hope this helps at least 1 of you
The toolkit in this video guide was developed by hasson2000, so big props and thanks go out to him! You can find his toolkit here
To the moderators. hasson2000 has asked that folks request his permission to use his work in posts ect.. So i did ask, but he never responded... So since this is doing no harm and only helping people, i assume you won't mind this posted here If you do want to take it down, i won't fight you on it.
If you folks have any questions, i strongly recommend you go to hasson2000s toolkit thread, linked above, and ask there.
Cheers
Click to expand...
Click to collapse
beginning of the video you said"the first link in the discriptions" where is that link?!i cant find it.the discription of what?
---------- Post added at 07:40 PM ---------- Previous post was at 07:31 PM ----------
TheSmokingAndroid said:
Hey folks, i know that for some, unlocking bootloaders and rooting for the first time can be a bit overwhelming, so i put together a video, walking you through step by step. I hope this helps at least 1 of you
The toolkit in this video guide was developed by hasson2000, so big props and thanks go out to him! You can find his toolkit here
To the moderators. hasson2000 has asked that folks request his permission to use his work in posts ect.. So i did ask, but he never responded... So since this is doing no harm and only helping people, i assume you won't mind this posted here If you do want to take it down, i won't fight you on it.
If you folks have any questions, i strongly recommend you go to hasson2000s toolkit thread, linked above, and ask there.
Cheers
Click to expand...
Click to collapse
the htc driver i got is 3.0.0.007 not the only in ur video 4.1.0.001.
i just cant find that link where you highlighted the new version in the video which was updated on 4.23.13.
thanks plz help me
What does unlocking the bootloader do?
Is it just for installing custom roms?
i am looking to buy a rogers canada HTC one and i need to use it with Bell mobility.
how can i unlock it? do i need to follow the video and unlock the bootloader? is there anything extra that I need to do?
let me know. thanks
Hello everyone! As most of you may know, AT&T pushed out an update today for the MotoX. A few weeks ago, I so happened to root my MotoX using PwnMyMoto. I installed the OTA update, without knowing this would **** my phone up as I had read that if you update using OTA it will just undo the root. Now my phone is in a constant boot loop. I can't do anything. By the time the phone gets loaded up and connects to WiFi or anything it reboots.
I suppose I'm screwed? Thanks.
NicholasJohnson said:
Hello everyone! As most of you may know, AT&T pushed out an update today for the MotoX. A few weeks ago, I so happened to root my MotoX using PwnMyMoto. I installed the OTA update, without knowing this would **** my phone up as I had read that if you update using OTA it will just undo the root. Now my phone is in a constant boot loop. I can't do anything. By the time the phone gets loaded up and connects to WiFi or anything it reboots.
I suppose I'm screwed? Thanks.
Click to expand...
Click to collapse
So many threads already covering this issue. Search, read, and also post to Q&A forum if you have a question.
Sent from my XT1058 using Tapatalk 4
NicholasJohnson said:
Hello everyone! As most of you may know, AT&T pushed out an update today for the MotoX. A few weeks ago, I so happened to root my MotoX using PwnMyMoto. I installed the OTA update, without knowing this would **** my phone up as I had read that if you update using OTA it will just undo the root. Now my phone is in a constant boot loop. I can't do anything. By the time the phone gets loaded up and connects to WiFi or anything it reboots.
I suppose I'm screwed? Thanks.
Click to expand...
Click to collapse
So any luck with this? Im trying to figure out how to save the phone if possible myself. Couldn't find the threads mentioned by ^ post.
ronVnor said:
So any luck with this? Im trying to figure out how to save the phone if possible myself. Couldn't find the threads mentioned by ^ post.
Click to expand...
Click to collapse
Since your phone is now a useless brick can I buy it from you for $20?
Sent from my Moto X.
Please ignore people who are not considerate enough to link to a post when saying "please search" as if they have actually tried using the search to find information. Because if they had, they could have easily linked you to the corresponding topic, and the discussion would have been over, or they would have found (like i did) limited results on the matter.
Here's an image that should be flashable that includes OTA (cannot revert, or root afterwards at this point)
[URL="http://forum.xda-developers.com/showthread.php?t=2471975]http://forum.xda-developers.com/showthread.php?t=2471975[/URL]
I won't claim to know alot, especially about this device, i'm mainly researching because it is my next device I'm purchasing (very soon). Right now there's not alot of information, but there should be official flashable images available for the phone floating around on XDA or some of the other forums.
I wish i could do more to help you in this situation, the last time i bricked a device (HTC Incredible) i was lucky to find an original image to restore it. This is the best method because an unrooted working phone is better than no phone at all, if that AT&T OTA image doesn't flash, my best recommendation is to look for an original motorola firmware and flash it using fastboot, i don't own the device (yet) so i don't have any specific instructions to help you with.
Destreyf said:
Please ignore people who are not considerate enough to link to a post when saying "please search" as if they have actually tried using the search to find information. Because if they had, they could have easily linked you to the corresponding topic, and the discussion would have been over, or they would have found (like i did) limited results on the matter.
Here's an image that should be flashable that includes OTA (cannot revert, or root afterwards at this point)
[URL="http://forum.xda-developers.com/showthread.php?t=2471975]http://forum.xda-developers.com/showthread.php?t=2471975[/URL]
I won't claim to know alot, especially about this device, i'm mainly researching because it is my next device I'm purchasing (very soon). Right now there's not alot of information, but there should be official flashable images available for the phone floating around on XDA or some of the other forums.
I wish i could do more to help you in this situation, the last time i bricked a device (HTC Incredible) i was lucky to find an original image to restore it. This is the best method because an unrooted working phone is better than no phone at all, if that AT&T OTA image doesn't flash, my best recommendation is to look for an original motorola firmware and flash it using fastboot, i don't own the device (yet) so i don't have any specific instructions to help you with.
Click to expand...
Click to collapse
Teach a man to search and he will have near infinite knowledge. Give a man the answer and he will bug the **** out of you every time his brain farts. Jesus said something similar to that. Good stuff.
Lesson: XDA search sucks. Use Google to search XDA. For example use this search phrase: "moto x bootloop after update root site:forum.xda-developers.com"
Consequentially the first result is the one that would get the OP out of his infinite loop of sadness.
Dont cripple people by saying its ok to ask before searching. No one wins.
mentose457 said:
Teach a man to search and he will have near infinite knowledge. Give a man the answer and he will bug the **** out of you every time his brain farts. Jesus said something similar to that. Good stuff.
Lesson: XDA search sucks. Use Google to search XDA. For example use this search phrase: "moto x bootloop after update root site:forum.xda-developers.com"
Consequentially the first result is the one that would get the OP out of his infinite loop of sadness.
Dont cripple people by saying its ok to ask before searching. No one wins.
Click to expand...
Click to collapse
Well in this case as you said yourself, "XDA Search Sucks" even i didn't think of that (and i've been using XDA for several years now) so everyone can learn something by asking questions. (also thank you for the info because now i know a better way to search XDA)
mentose457 said:
Since your phone is now a useless brick can I buy it from you for $20?
Sent from my Moto X.
Click to expand...
Click to collapse
Psshhhh...I'll give you $50, OP.
Anyway, you need to delete the update from cache. If you can't stay booted long enough to do this from the system, you may have to do it from fastboot (use the command "fastboot erase cache" without the quotes).
So i brilliantly unlock the bootloader on the moto x and rooted the phone also installed the su and then the real genius part came out and i accidentally wiped the whole fing phone all the sdcard and the entire os and now all i have is a wonderful beautiful white motorola moto x and cant use it oh and to make things really worth it i just open the account with sprint so the phone is only 3 days old. Can someone Please Help me i am at a lost and dont have a clue what to do. I dont know how to reinstall the OS.:crying::crying::crying:
lsl73 said:
So i brilliantly unlock the bootloader on the moto x and rooted the phone also installed the su and then the real genius part came out and i accidentally wiped the whole fing phone all the sdcard and the entire os and now all i have is a wonderful beautiful white motorola moto x and cant use it oh and to make things really worth it i just open the account with sprint so the phone is only 3 days old. Can someone Please Help me i am at a lost and dont have a clue what to do. I dont know how to reinstall the OS.:crying::crying::crying:
Click to expand...
Click to collapse
I am having somewhat the same issues. Someone is helping me out and if I get an easy solution I will be happy to share.
This should help you:
http://forum.xda-developers.com/showthread.php?t=2446515
superaj13 said:
I am having somewhat the same issues. Someone is helping me out and if I get an easy solution I will be happy to share.
Click to expand...
Click to collapse
Thanks i hope you can get yours going as well
fabriciosr said:
This should help you:
http://forum.xda-developers.com/showthread.php?t=2446515
Click to expand...
Click to collapse
The rsd lite cant see my moto x i can only access it thru the fastboot but when i try the rsd way it doesnt see the phone.
Download/find the correct system.img and boot.img for your device, then push/install them via fastboot. You shouldn't need anything else. Recovery, bootloader, and other firmware should be untouched. Only issue is if it's a safestrap device, then I have no clue.
gokart2 said:
Download/find the correct system.img and boot.img for your device, then push/install them via fastboot. You shouldn't need anything else. Recovery, bootloader, and other firmware should be untouched. Only issue is if it's a safestrap device, then I have no clue.
Click to expand...
Click to collapse
Gokart i have tried that i dont think i am doing it wrong i got the system.img and the boot.img from here but just incase i ride the small yellow bus with a helmet on can you please point me to the direction i need to go AGAIN.
try to
fastboot flash system system.img
The obvious thing is make sure you have fastboot set up correctly... Drivers as well.
Make sure all drivers are installed, trust me redlite works with a soft bricked moto x, I found out today, my phone was bootlooping, nandroids failed soi wiped the sdcard and realized at that point I did the noob thing, well it worked like a charm rsdlite
Sent on my Moto X
this is the error i keep getting
lsl73 said:
this is the error i keep getting
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2489249
i would like to thank all you guys for all the advise that was given to help me bring my moto x back to life i finally got it up and running again using the moto x toolkit it seemed like the only thing that would of work in my situation again thank yall so much :victory::victory::victory:
Who unlocks their bootloader but doesn't know what to do when stuff goes bad, like this?
If you read enough to unlock the bootloader, you should have read enough to know what to do here. Coming here frantic without even checking the eleven billion threads already is silly. We have about 12 threads about the new update and similar high number threads about restoring your phone.
Too many repetitive threads for the Moto X on xda. Some people just need to take 5 minutes and look through general or Q&A before they blindly post. Clutter everywhere.
And finally, dude! I do not have any pity for you. I'm on Verizon and cannot unlock my bootloader maybe that's why I just ranted. Nothing personal, just a general consensus of this section as of late...
Sent from my XT1060 using Tapatalk
oh brother i am not mad at you but as a by the way i DID try different ways of trying to load the os back using this site as a guidance before i made this post this post was a last ditch effort before i smash the moto x and use the insurance claim on it i have been a member of this site since 2010 i just didnt create this account
I have a Moto X Developer Edition rooted on Verizon with TWRP 2.6.3.1 and stock Android 4.4 on it. I have been trying to upgrade to 4.4.2 without doing the OTA, and without having to reflash TWRP.
So far, I have been unsuccessful.
I have tried Blur_Version.140.45.5.ghost_verizon.Verizon.en.US.zip (approximate file size 150MB) from multiple sources as all the posts I read keep saying that is what works. I have also tried a ~650MB version I found somewhere. In addition, I tried the upgrade located here: sbf.droid-developers.org/phone.php?device=0 which is called VZW_XT1060_4.4.2-KXA20.16-1.25.2_CFC_1FF.xml.zip (It's the 4.4.2 upgrade listed under Verizon US).
All of these fail. In TWRP, about 2-3 steps after it verified md5, it simply says "Failed" with no explanation as to why.
Here is my question:
How can I upgrade to 4.4.2 without a data wipe, and without having to reflash TWRP?
I have no interest in going to a ROM, I want to stay stock, and if I must, I will reflash the recovery if I have to, but I *really* don't want to.
Flash stock recovery, take the OTA, flash TWRP again.
It's so simple, so painless, so quick and it will not wipe your data.
tcrews said:
Flash stock recovery, take the OTA, flash TWRP again.
It's so simple, so painless, so quick and it will not wipe your data.
Click to expand...
Click to collapse
I was hoping to avoid that (Yep, I really am that lazy...) but that's what I was going to do tonight if I couldn't get my hands on a .zip to flash.
Ironically, I bought the Dev Edition specifically so things like this would be easy.
It is easy.....just need to do it.
I support my sister, her husband and my wife (as well as my own) who all have Moto X's. 2 seconds to flash recovery, however long it takes for the OTA to install and reboot and then 2 seconds to flash TWRP again. Heck...I'd just leave the stock recovery in place since it's not needed if you don't plan on flashing any ROMs. The OTA doesn't even remove root.
tcrews said:
It is easy.....just need to do it.
I support my sister, her husband and my wife (as well as my own) who all have Moto X's. 2 seconds to flash recovery, however long it takes for the OTA to install and reboot and then 2 seconds to flash TWRP again. Heck...I'd just leave the stock recovery in place since it's not needed if you don't plan on flashing any ROMs. The OTA doesn't even remove root.
Click to expand...
Click to collapse
Oh, that last bit is good to know! Well, I think even if it did remove root, getting it back is easy on the DE.
I think you're right though, I probably won't install TWRP again, I specifically got the Moto X because I was tired of messing around with stuff when I all I want is a rooted, stock Android experience.
So, after several hours of messing with this, and thinking the stock recovery had gotten messed up because the instructions I had for getting in to it were wrong, I finally got the OTA installing...
and it fails.
I don't know why, I haven't seen the error (I'm not looking at the phone when it fails).
So... Awesome.
Taegost said:
So, after several hours of messing with this, and thinking the stock recovery had gotten messed up because the instructions I had for getting in to it were wrong, I finally got the OTA installing...
and it fails.
I don't know why, I haven't seen the error (I'm not looking at the phone when it fails).
So... Awesome.
Click to expand...
Click to collapse
Are there files out so you can just flash 4.4.2 with mfastboot? Would be easiest.
kj2112 said:
Are there files out so you can just flash 4.4.2 with mfastboot? Would be easiest.
Click to expand...
Click to collapse
I assume so, but I haven't found any instructions specifically saying how to do that, except for the ones that tell you how to return to stock without using RSD Lite.
Unfortunately, I don't know enough about how all this stuff works to be able to figure out which bits and pieces to put together to get upgraded without wiping my data.
What really pisses me off is that I specifically bought this phone so I wouldn't have issues like this, and here I am...
BTW: The only thing the error says is "Error". That's it, nothing else.
Taegost said:
I assume so, but I haven't found any instructions specifically saying how to do that, except for the ones that tell you how to return to stock without using RSD Lite.
Unfortunately, I don't know enough about how all this stuff works to be able to figure out which bits and pieces to put together to get upgraded without wiping my data.
What really pisses me off is that I specifically bought this phone so I wouldn't have issues like this, and here I am...
BTW: The only thing the error says is "Error". That's it, nothing else.
Click to expand...
Click to collapse
This guide has a return to stock section. It will tell you how to flash the stock firmware.
http://forum.xda-developers.com/showthread.php?t=2603358
Unfortunately the moto x is not a simple phone for tinkering with, like say a nexus, even the dev edition.
It can be easier once you do fully understand everything. Just gotta know what applies to you...meaning mostly the locked versus unlocked methods for everything.
After owning an s2, a moto x and now an n5 (n7 too...but I don't tinker with it really....its a family device) I've come to the mind set that for flashers and rooters.....nothing at all beats owning a nexus. Every other device has some limitations that a nexus won't have.
kj2112 said:
This guide has a return to stock section. It will tell you how to flash the stock firmware.
http://forum.xda-developers.com/showthread.php?t=2603358
Unfortunately the moto x is not a simple phone for tinkering with, like say a nexus, even the dev edition.
It can be easier once you do fully understand everything. Just gotta know what applies to you...meaning mostly the locked versus unlocked methods for everything.
After owning an s2, a moto x and now an n5 (n7 too...but I don't tinker with it really....its a family device) I've come to the mind set that for flashers and rooters.....nothing at all beats owning a nexus. Every other device has some limitations that a nexus won't have.
Click to expand...
Click to collapse
Yeah, that's the page I was talking about when I said I found the full instructions...
I specifically bought this phone because I didn't want to mess around with it like this, I just wanted to root it so I could use Titantium Backup and be done with it... and now I'm stuck at a halfway point.... Again...
I'll probably end up just doing the full wipe and manually flash to 4.4.2 (RSD Lite doesn't see my device... yay), since I have gone from my mute button not working (with 4.2.2), to a really bad echo for whomever I'm talking to when it's on speakerphone (Even when speakerphone is muted... THAT made for a fun conference call...).
Taegost said:
Yeah, that's the page I was talking about when I said I found the full instructions...
I specifically bought this phone because I didn't want to mess around with it like this, I just wanted to root it so I could use Titantium Backup and be done with it... and now I'm stuck at a halfway point.... Again...
I'll probably end up just doing the full wipe and manually flash to 4.4.2 (RSD Lite doesn't see my device... yay), since I have gone from my mute button not working (with 4.2.2), to a really bad echo for whomever I'm talking to when it's on speakerphone (Even when speakerphone is muted... THAT made for a fun conference call...).
Click to expand...
Click to collapse
Flashing stock and rooting on an unlocked Moto x is basically the same as a nexus. It really is simple, once you are familiar with fastboot.
I guess there are toolkits that automate everything....like Samsung's Odin, and there's a few for nexus....but it really doesn't help anyone learn. And that's kinda what this hobby is all about.
But, I am sorry you're having trouble. Not sure what else to add. The guides are there, and they work. Usually. I can't think of anything to add to whats already been said.
Hope it works out for you!
kj2112 said:
Flashing stock and rooting on an unlocked Moto x is basically the same as a nexus. It really is simple, once you are familiar with fastboot.
I guess there are toolkits that automate everything....like Samsung's Odin, and there's a few for nexus....but it really doesn't help anyone learn. And that's kinda what this hobby is all about.
But, I am sorry you're having trouble. Not sure what else to add. The guides are there, and they work. Usually. I can't think of anything to add to whats already been said.
Hope it works out for you!
Click to expand...
Click to collapse
I don't think I'm articulating my issue properly. I understand how to do everything in the guides you mentioned, they're a piece of cake. That doesn't solve my problem.
My problem is that I want to get to 4.4.2 WITHOUT wiping my data, but can't do the update via OTA or flashing in recovery. RSD Lite doesn't work either.
The ONLY option I have available to me is to manually push the update with fastboot, which I can definitely do with the instructions provided... But those instructions require me to wipe my data.
I know it's possible to apply the update with fastboot without requiring me to wipe my data, but I don't know enough about the inner workings to know which steps to skip, and which need to be modified, in order to make that happen.
Taegost said:
I don't think I'm articulating my issue properly. I understand how to do everything in the guides you mentioned, they're a piece of cake. That doesn't solve my problem.
My problem is that I want to get to 4.4.2 WITHOUT wiping my data, but can't do the update via OTA or flashing in recovery. RSD Lite doesn't work either.
The ONLY option I have available to me is to manually push the update with fastboot, which I can definitely do with the instructions provided... But those instructions require me to wipe my data.
I know it's possible to apply the update with fastboot without requiring me to wipe my data, but I don't know enough about the inner workings to know which steps to skip, and which need to be modified, in order to make that happen.
Click to expand...
Click to collapse
It says right at the bottom of the return to stock section in the guide I linked too.....you can skip
Fastboot erase user data
fastboot erase cache
Though if you have any problems after, you might have to do it again and do erase those, before spending time trying to figure out what's wrong.
kj2112 said:
It says right at the bottom of the return to stock section in the guide I linked too.....you can skip
Fastboot erase user data
fastboot erase cache
Though if you have any problems after, you might have to do it again and do erase those, before spending time trying to figure out what's wrong.
Click to expand...
Click to collapse
Wow... Attention to detail -5
Sorry about that, when I looked through that article, I skimmed through and saw that the "Return to Stock" section was (almost) identical to the other instructions I was reading...But I missed that last paragraph when I looked at the link you provided, the directions I was using referenced that article but did not include that last bit...
Thank you for your patients, I feel like a dumbass now *sheepish grin*
Taegost said:
Wow... Attention to detail -5
Sorry about that, when I looked through that article, I skimmed through and saw that the "Return to Stock" section was (almost) identical to the other instructions I was reading...But I missed that last paragraph when I looked at the link you provided, the directions I was using referenced that article but did not include that last bit...
Thank you for your patients, I feel like a dumbass now *sheepish grin*
Click to expand...
Click to collapse
No worries!! .
And sorry, its userdata. My keyboard split the words up.
---------- Post added at 11:16 AM ---------- Previous post was at 11:15 AM ----------
And, you may very well have issues doing that way. But its worth a shot first. If you do have issues, then you can erase those and repeat the process.
if using fastboot/mfastboot, I would still erase cache, as it doesn't touch your data/apps/config.
Another tip, use this mfastboot -> http://mark.cdmaforums.com/X-STUFF/Mfastboot-4.4.zip
or you can use RSDlite to flash the SBF, but there is a corresponding line for "erase data"
Two helpful links that will help explain what you saw...
Taking the OTA -> http://mark.cdmaforums.com/MotoX-OTA.html
various ways to Return to stock -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html
kj2112 said:
No worries!! .
And sorry, its userdata. My keyboard split the words up.
---------- Post added at 11:16 AM ---------- Previous post was at 11:15 AM ----------
And, you may very well have issues doing that way. But its worth a shot first. If you do have issues, then you can erase those and repeat the process.
Click to expand...
Click to collapse
Alrighty, well I was able to successfully flash to 4.4.2 using the Fastboot instructions. Flashed TWRP afterwards and got root right back. Now that I know, this won't be a trial in the future (fingers crossed!)
Thanks for your help and patience
Hey everyone I'm looking here as my last resort before sending my phone back to Motorola.
Bought a Nexus 6 from motorola uk which was delivered yesterday, switched phone on and all the Google apps on the phone updated, then had a notification OTA to download and install android 5.1 which I did, towards the end of the install process I had an error with the green android and a red exclamation mark.
I powered the device off with the power button and it turned back on and ever since it says "Android is starting" "Optimizing app 1 of 125" once it goes through all the apps it gets to the android boot screen then just goes back to the "Android is starting" "Optimizing app 1 of 125" over and over and over. (Infinite bootloop)
Pointers: The phone is not unlocked or rooted as I'm a noob its just fresh out the box, also I never opened/unlocked the developer options.
I have tried various recovery mode fixes, wiping cache and wiping all data and then rebooting the device with no luck.
Is there anyway I can hook my N6 up to my computer and fix this with a tool kit etc? I'm willing to try but I'd need basic instructions and reassurance it wouldn't muck up my warranty if it didn't work as my only other option is to exchange for a new device.
I'm a noob so I need detailed basic step by step instructions.
Any help, advice etc would be hugely appreciated. Thanks
Just send it back, no point messing about with it if it brand new could down to a fault with the hardware itself.
ixon2001 said:
Just send it back, no point messing about with it if it brand new could down to a fault with the hardware itself.
Click to expand...
Click to collapse
Iv'e heard this is a common problem with the N6 whilst trying to update the OTA 5.1 I had no other apps on the phone it was fresh, I did nothing wrong, I know someone who has been through 4 devices with the same bloody issues! In the end he had to sideload 6.0 and I'm not confident in being able to do that.
Well best bet is to download wugfresh toolkit 2.10 i think is the latest version, follow the instructions carefully because first you need to unlock the bootloader then flash 6.0.1 which has just come out.
Using Wugfresh is the best way to go if your new to flashing & you can't really go wrong with it.
ixon2001 said:
Well best bet is to download wugfresh toolkit 2.10 i think is the latest version, follow the instructions carefully because first you need to unlock the bootloader then flash 6.0.1 which has just come out.
Using Wugfresh is the best way to go if your new to flashing & you can't really go wrong with it.
Click to expand...
Click to collapse
I`am sure most xperienced users (me included) will not agree with you The best way to unlock, flash and root is still adb/fastboot. Especialy for lesser xperienced users that are lost is something goes wrong while using the toolkit, wich happens frequently btw. Just check the help threads.
gee2012 said:
I`am sure most xperienced users (me included) will not agree with you The best way to unlock, flash and root is still adb/fastboot. Especialy for lesser xperienced users that are lost is something goes wrong while using the toolkit, wich happens frequently btw. Just check the help threads.
Click to expand...
Click to collapse
Lol it's not rocket science using adb, been doing that way for years but for somebody that never flashed, rooted ect I still think the toolkit best way to go at first because everything is done for you at a click of a button.
Yes things can go tits up when using toolkits, mainly because they don't follow simple instructions.
ixon2001 said:
Lol it's not rocket science using adb, been doing that way for years but for somebody that never flashed, rooted ect I still think the toolkit best way to go at first because everything is done for you at a click of a button.
Yes things can go tits up when using toolkits, mainly because they don't follow simple instructions.
Click to expand...
Click to collapse
Lets agree to disagree
OK
ixon2001 said:
Yes things can go tits up when using toolkits, mainly because they don't follow simple instructions.
Click to expand...
Click to collapse
No, but because toolkits are always behind at least one version with marshmallow. People kept bricking their devices with toolkits when marshmallow came out and they thought they could root it. As 6.0.1 came out they'll do something else wrong.
Toolkits are not help. It's the lazy way if everything is already working and up to date.
Also what can a toolkit do if this phone doesn't even have developer options turned on? If it's in boot loop, as the OP said, then the Enable OEM unlocking was never set, then the only solution is to send it back. Unless there's a toolkit magic we don't know about.
Sent from my Nexus 6 running cyosp using Tapatalk
istperson said:
N
Also what can a toolkit do if this phone doesn't even have developer options turned on? If it's in boot loop, as the OP said, then the Enable OEM unlocking was never set, then the only solution is to send it back. Unless there's a toolkit magic we don't know about.
Click to expand...
Click to collapse
I think op created another thread http://forum.xda-developers.com/nexus-6/help/nexus-6-stuck-bootloop-trying-to-update-t3266100 for this issue - and was somehow able to unlock the bootloader (not sure how that worked if OEM unlock was never set)
jj14 said:
(not sure how that worked if OEM unlock was never set)
Click to expand...
Click to collapse
It was said that some of the first Nexus 6s with the original 5.0 came out with a bootloader that didn't check for this switch.