[REMINDER] unlock Bootloader without wipe - Nexus 5 General

I'm short in time right now, so I can't give a full "how to tutorial"
I just want to remind you of a method to unlock the bootloader without wipe.
You are on 4.4.4 Stock, locked bootloader?
use towelroot to root:
http://goo.gl/VaDb77
after that use Nexus Bootloader unlocker tool to unlock without wipe:
http://goo.gl/dfYlgt
after unlock you might want to unroot
Now you should be able to flash the 5.0 factory image step by step manually but without the wipe command
if everything worked fine you should be on lollipop without any data lost
Got to get to work now, won't be able to answer questions in the next hours
Good luck!

Kindly let us know,, whether this works or not?? And can we root Android Lollipop on nexus 5???

I had been wondering if there was a good method to unlock the bootloader on a stock nexus without having to do a full data wipe. To me now seems like a good oportunity to start clean with my stock kitkat nexus while upgrading to lollipop. Its been doing some wierd things of late anyways. So might as well.
I just need to figure out a good foolproof backup method that works with the stock setup before doing so. Something along the lines of a nandroid backup or image was my thinking. But what ive heard that requires root access anyways.

Related

[Q] Bootloader and Rooting - which one does what?

Hello,
I just got my new Xperia Z having used my ancient Iphone 1G for the last 4 years and I have no experience with Android and anything related to it what so ever. I've spent the last 2 days tirelessly working my way through various forums, guides, wikis to get an idea what I'm dealing with here and where to start, but there's an important decision that I could really use your thoughts and tips on.
After reading up on it, I decided I want to root my phone and this seems to be somehow connected to unlocking the bootloader and this is where I'm worried. I read the guide on how to unlock the bootloader and the warning about losing DRM Keys and the consequences of this scared me away from it. Now I'm left wondering, and this is my actual question here:
What is the difference between unlocking the bootloader and rooting my phone and simply rooting without unlocking the bootloader?
And in case the things I want to do are only available with an unlocked bootloader: how damaging is it to lose DRM keys and therefore the bravia engine and gracenote? What made you decided for or against unlocking the bootloader?
Thanks!
Hi,
maybe I can help you.
Bootloader is like the BIOS of a PC. It checks everything at start up.
Locked Bootloader only allows to run the Stock FW and in this case the DRM-Keys are working (everything is checked and safe)
Unlock the Bootloader means you were able to install an modified / other FW and then you loose the DRM-Keys (the manufacturer hasn´t checked the FW and it is in the eyes of an manufacturer "not safe". You will also loose your warranty.
If you unlock the bootloader Root is always possible as I know.
In this case the system is not from the manufacturer and unofficial modification could be done to the system. Normally all modified Systems have Root access. So you were able to do things that the manufacturer has normally not allowed. Modify system files or something like that. Also it could be possible to copy for example a downloaded and payed movie to another device. This is why you were not able to download a movie on the Play Store if you have root. On a locked bootloader the FW (system) does not give you the possibility to copy the movie to an other device and everything is "safe" (from the view of companies). No illegal copies are possible. (DRM-Keys)
Since some days Root is also possible on a locked bootloader.
The bootloader is checking the status (locked) .. then checking the FW (stock) ... DRM-Keys still valid.
But due to the root access you were also able to modify system files and apps can recognize that you have root access. So you can still use the bravia engine for example (DRM-Keys are ok). But the Google Play Store will still recognize that you have root and will not let you download movies.
This is my experience with Root ... If something is not correct, please correct me
UserX10 said:
Hi,
maybe I can help you.
Bootloader is like the BIOS of a PC. It checks everything at start up.
Locked Bootloader only allows to run the Stock FW and in this case the DRM-Keys are working (everything is checked and safe)
Unlock the Bootloader means you were able to install an modified / other FW and then you loose the DRM-Keys (the manufacturer hasn´t checked the FW and it is in the eyes of an manufacturer "not safe". You will also loose your warranty.
If you unlock the bootloader Root is always possible as I know.
In this case the system is not from the manufacturer and unofficial modification could be done to the system. Normally all modified Systems have Root access. So you were able to do things that the manufacturer has normally not allowed. Modify system files or something like that. Also it could be possible to copy for example a downloaded and payed movie to another device. This is why you were not able to download a movie on the Play Store if you have root. On a locked bootloader the FW (system) does not give you the possibility to copy the movie to an other device and everything is "safe" (from the view of companies). No illegal copies are possible. (DRM-Keys)
Since some days Root is also possible on a locked bootloader.
The bootloader is checking the status (locked) .. then checking the FW (stock) ... DRM-Keys still valid.
But due to the root access you were also able to modify system files and apps can recognize that you have root access. So you can still use the bravia engine for example (DRM-Keys are ok). But the Google Play Store will still recognize that you have root and will not let you download movies.
This is my experience with Root ... If something is not correct, please correct me
Click to expand...
Click to collapse
Hi and thanks a lot for your reply, helped me understand the difference of both better!
If I only root but do not unlock my bootloader will I be able to do anything other than using custom firmware (ROMs)? Will I be able to install Apps that require root or install custom modification like the ones offered on this forum that need to be "flashed in recovery" if I only root not unlock my bootloader?
Also, still looking for some pros and cons (my second question in the original post).
Appreciate all your help!
root will give you access to recovery (in time - still in development) and you can install apps that require root access
custom mods - yes you can install them via recovery and some can be installed with root access and without recovery
if u unlock bootloader you will lose bravia engine not sure bout gracenote as i dont use it
you can check this thread http://forum.xda-developers.com/showthread.php?t=2154310 too see what have people wrote bout
rooting with unlocked bootloader
The main thing pointing me towards unlocking bootloader (I'm already rooted on locked bootloader) is being able to install kernels and major roms.
For example, you could flash Doomlords kernel and over clock the processor a bit, but you could also reduce power and save battery
The major roms I speak of are the ones that are kinda cross device: CyanogenMod and Paranoid Android to name 2. CM is based on pure android, no Sony changes so we can't flash that on locked bootloaders as it requires changing kernel. PA is same.
As for the downsides. I'm not too bothered about DRM keys. I use Spotify for music so don't think I need gracenote. Never watched a movie on my phone. BE2 isn't my cup of tea... Over saturates everything.
I'm going to look into DRM keys more tomorrow, but if someone can correct anything I've written then please do
Not being able to restore via Sony tools... Isn't that bad as you're going to be using flash tool a lot so you'll be used to that. Just keep a generic stick firmware .ftf around in case something goes horrendously wrong (usually recovery backup is enough I think).
Sent from my C6603 using Tapatalk 2
Nice thread, I had this question too
It's my first android and I guess I should unlock the bootloader and then root, this way I won't have to wipe my data later when I decide to try cyanogenmod or something else?
Also what happens if sony release 4.2? Will I lose my bootloader unlock and root?
Al Gore said:
Nice thread, I had this question too
It's my first android and I guess I should unlock the bootloader and then root, this way I won't have to wipe my data later when I decide to try cyanogenmod or something else?
Also what happens if sony release 4.2? Will I lose my bootloader unlock and root?
Click to expand...
Click to collapse
I would say root without unlock for now.
When you want to try cyanogenmod or others. Just backup everything using titanium backup and then u can restore after unlocking.
Rooting with a locked bootloader means sony are not aware your bootloader is unlocked
Sent from my C6603 using xda premium
Thanks for all your replies, helped me out a ton!
I think Im gonna root without unlocking bootloader for now to get my feet wet and get a grasp of it's capabilities and limits. Can always restore the phone if I screw up and can always unlock bootloader later if I need it.
Al Gore said:
Nice thread, I had this question too
It's my first android and I guess I should unlock the bootloader and then root, this way I won't have to wipe my data later when I decide to try cyanogenmod or something else?
Also what happens if sony release 4.2? Will I lose my bootloader unlock and root?
Click to expand...
Click to collapse
If you unlock Bootloader, you shouldn't update from Sony. Since you've (hypothetically) already unlocked, you already have 4.2 avaliable from FXP and if you really want the Sony Update maybe you could flash it via flash tool. Bootloader unlock will never be lost (until someone can create an explicit relock file, but customs roms won't relock it). Root maybe lost if you flash a rom without it but you should be able to get it back easy.
With locked bootloader, we have to wait for Sony to bring 4.2 as we can't access the kernel, but we retain the ability to use the official updates. If we're rooted and we update, we are no longer rooted and we may be unable to use the same exploit.
Sent from my C6603 using Tapatalk 2

Question about unlocked/rooted VZW Moto X

So I really miss rooting and modding my phones so I was thinking about do that Chinese method of unlocking my verizon wireless moto x. I just have a couple questions if anyone could answer I'd appreciate it. I can't find much info about 4.4.2 for the verizon moto x because before this unlock discovery, it wasn't possible
1. Once I unlock, is rooting just a simple adb command away?
2. Will I still be able receive android updates via OTA from verizon in the future? Assuming I remain on stock rom and don't flash a rom.
3. My main goal would to be able to tether. So is there a xposed mod to enable tethering on stock rom?
I've only seen this info for DE Moto Xs' and outdated info so I just want to be as updated as possible before I decide to do this.
tu3218 said:
So I really miss rooting and modding my phones so I was thinking about do that Chinese method of unlocking my verizon wireless moto x. I just have a couple questions if anyone could answer I'd appreciate it. I can't find much info about 4.4.2 for the verizon moto x because before this unlock discovery, it wasn't possible
1. Once I unlock, is rooting just a simple adb command away?
2. Will I still be able receive android updates via OTA from verizon in the future? Assuming I remain on stock rom and don't flash a rom.
3. My main goal would to be able to tether. So is there a xposed mod to enable tethering on stock rom?
I've only seen this info for DE Moto Xs' and outdated info so I just want to be as updated as possible before I decide to do this.
Click to expand...
Click to collapse
1. after you unlock the bootloader Rooting is as easy as installed TWRP or CWM then flashing SuperSU flashable sip and your rooted.
2. yes you will still get OTA updates. but in order to use the OTA update you will have to reflash the stock recovery. then take the update and reflash TWRP or CWM and SuperSU and your rooted again.
3.yea there is
hope this answered all your questions.
^^ this
Also, with an unlocked bootloader....you now have a phone that is no different than a dev edition. Aside from your warranty.
There's nothing else special about the dev edition. You keep your warranty on a DE.....that's where its specialness ends.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
dray_jr said:
1. after you unlock the bootloader Rooting is as easy as installed TWRP or CWM then flashing SuperSU flashable sip and your rooted.
2. yes you will still get OTA updates. but in order to use the OTA update you will have to reflash the stock recovery. then take the update and reflash TWRP or CWM and SuperSU and your rooted again.
3.yea there is
hope this answered all your questions.
Click to expand...
Click to collapse
Yeah thanks a lot! My plan would be to just run stock software but just add the tethering xposed module. But my main concern was receiving future OTAs so it's good to know that I still can. Is it pretty safe to root/unlock this phone? My galaxy nexus was a breeze(obviously being a nexus), but like my S3, there was no flashing back to stock recovery, taking OTA, an than flashing CWM again. At least it wasn't as easy as you described lol I think because there was always concern about whether the update removed ability to root access. Is that possible with this phone or with the unlocking of the bootloader, does that take that variable out? Thanks again. Oh yeah last question, once I'm unlocked, can I lock it back up again and go back to completely stock if I wanted to for some reason? Or is it a done deal.
tu3218 said:
Yeah thanks a lot! My plan would be to just run stock software but just add the tethering xposed module. But my main concern was receiving future OTAs so it's good to know that I still can. Is it pretty safe to root/unlock this phone? My galaxy nexus was a breeze(obviously being a nexus), but like my S3, there was no flashing back to stock recovery, taking OTA, an than flashing CWM again. At least it wasn't as easy as you described lol I think because there was always concern about whether the update removed ability to root access. Is that possible with this phone or with the unlocking of the bootloader, does that take that variable out? Thanks again. Oh yeah last question, once I'm unlocked, can I lock it back up again and go back to completely stock if I wanted to for some reason? Or is it a done deal.
Click to expand...
Click to collapse
the unlocking the bootloader process is kind of a pain but not too bad.
custom recovery and root are as simple as one command and one flashable zip
as long as you follow directions and read before doing anything then it should be safe. but rooting and modifying your phone is never %100 save.
when you unlock your bootloader you will always be able to root your phone no matter what android version your on. but it is always possible that they make some crazy change and we have issues.
once unlocked you can relock with with "fastboot oem lock" but that stupid warning msg about you bootloader being unlocked won't go away unless you flash a custom boot screen.
i hope i answered all your questions to your full needs and if you have any more please feel free to ask here or PM me if need be.
Unlocking the bootloader is pretty easy if you have adb setup. Don't forget to backup via helium (download to computer or cloud not local.) since unlocking will delete everything and helium can work without root.
Xposed module is great, less intrusive than flashing roms and you can easily get the tethering, etc.
Sent from my Nexus 7 using Tapatalk

Relocking Bootloader without Unrooting?

Hi all,
Long time lurker and benefactor of all the great advice and wisdom on here. Thanks to everyone for the knowledge you share with the rest of us while we're learning! I have a quick question i can't seem to find the answer to anywhere here. Please forgive me and redirect if I'm being dense and it's somewhere else.
Firstly my One is unlocked, rooted, s-on and running ARHD 71.1
Ideally I want to keep root and my custom rom but if really necessary, I can return to stock and redo the process later.
Ok here's the issue. I didn't avail of the Google Drive storage offer before unlocking my bootloader. Now HTC are telling me I need to relock it to redeem. I'm still pushing them but just in case they hold firm:
1. Can I relock the bootloader without losing root and my custom rom? If so, how? All the guides I can find are about unrooting, locking and returning to stock.
2. If I do relock the bootloader, redeem the storage offer and then later unlock it again, is it going to wipe my data partition again?
Like I said. It's not the end of the world having to return to stock and redo, or having to flash ARHD again if the phone is wiped, but i would prefer a quick, clean and easy method if anyone has any ideas?
You can relock and still have root in the custom rom. How about making a nandroid backup, copy it off the device, relock, redeem the storage, unlock, then restore the /data partition from the backup.
diarm said:
Hi all,
Long time lurker and benefactor of all the great advice and wisdom on here. Thanks to everyone for the knowledge you share with the rest of us while we're learning! I have a quick question i can't seem to find the answer to anywhere here. Please forgive me and redirect if I'm being dense and it's somewhere else.
Firstly my One is unlocked, rooted, s-on and running ARHD 71.1
Ideally I want to keep root and my custom rom but if really necessary, I can return to stock and redo the process later.
Ok here's the issue. I didn't avail of the Google Drive storage offer before unlocking my bootloader. Now HTC are telling me I need to relock it to redeem. I'm still pushing them but just in case they hold firm:
1. Can I relock the bootloader without losing root and my custom rom? If so, how? All the guides I can find are about unrooting, locking and returning to stock.
2. If I do relock the bootloader, redeem the storage offer and then later unlock it again, is it going to wipe my data partition again?
Like I said. It's not the end of the world having to return to stock and redo, or having to flash ARHD again if the phone is wiped, but i would prefer a quick, clean and easy method if anyone has any ideas?
Click to expand...
Click to collapse
I just used @scotty1223 method posted here to lock and unlock
http://forum.xda-developers.com/showthread.php?t=2475914
you'll need s-off first
clsA said:
I just used @scotty1223 method posted here to lock and unlock
http://forum.xda-developers.com/showthread.php?t=2475914
you'll need s-off first
Click to expand...
Click to collapse
cschmitt said:
You can relock and still have root in the custom rom. How about making a nandroid backup, copy it off the device, relock, redeem the storage, unlock, then restore the /data partition from the backup.
Click to expand...
Click to collapse
that looks the best idea. will wait to see if htc get back with good news tomorrow otherwise i'll do this. thanks guys.
i'm having a nightmare here!
first when i relocked the phone it gave me "security warning" in the bootloader and refused to let me reboot the phone or even launch recovery.
i eventually managed to get the phone working again by rebooting the bootloader 7 or 8 times and then unlocking it again with my old unlock code.
then looking for another way to get relocked, i tried to get s-off but as my hboot is 1.55 there seem to be very few ways.
have been trying to use firewater (i'm on ARHD 71) but after going through everything, it tells me "ERROR: kernel contains HTC anti-firewater patch! Try again with a different kernel".
so then I flashed the ElementalX kernel thinking that would work but it gives me the same message.
anyone have any ideas? should i try another kernel? maybe a different ROM? I've tried to restore to the original nandroid backup i made when i first unlocked the thing but that's not working either!

[Q] Fastboot failure help needed

I am running a Verizon Moto X still on 4.2.2. I am rooted. This is NOT the Dev edition. I have plenty of experience with rooting/flashing these phones so back when I first got it the directions on rooting/flashing roms was VERY vague. No one specified you needed the Dev edition to unlock the boot loader. Well I think this came from at one point when I tried to flash TWRP (maybe). Either way, I want to take the OTA update and cannot. Does anyone know how to fix this without doing the RSD, reflash stock method? Here is a picture of what it looks like (thanks for your help in advance):
You should check out the 'Chinese Middleman' thread. If you get the bootloader unlocked you should be able to fix anything.
I can't unlock the bootloader since this is not a Dev edition. Unless something has changed, I'll check it.
You should be able to unlock the boot loader but will not have warranty.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Sent from my XT1053 using Tapatalk
shamelin73 said:
You should be able to unlock the boot loader but will not have warranty.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
Even though it's not a Dev edition?
Yes you should be able too.
Sent from my XT1053 using Tapatalk
danman421 said:
Even though it's not a Dev edition?
Click to expand...
Click to collapse
All XT1053s can be unlocked, yes. Additionally, if you follow my advice, you don't NEED to unlock. If one of the commands fails, simply skip to the next as I previously advised, and TRY flashing with RSD Lite after you have run the commands I listed.
If you want to check and make sure fastboot is working, type:
fastboot devices
if you see your phone and it's serial number listed, you fastboot IS properly communicating with your phone.
You do not need to unlock your BL to do any of this...but if you are interested in ROOTING, you will need to.
All I really want to do is make it so my phone can take the update and any future updates. What do you mean as you previously stated?
shamelin73 said:
You should be able to unlock the boot loader but will not have warranty.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
I tried this as I did before and I get "your device does not qualify for bootloader unlocking". All I need to know is how to fix this from someone.
danman421 said:
All I really want to do is make it so my phone can take the update and any future updates. What do you mean as you previously stated?
Click to expand...
Click to collapse
I confused you with a member I had helped previously - sorry. Please disregard the "previously stated" comment.
danman421 said:
I tried this as I did before and I get "your device does not qualify for bootloader unlocking". All I need to know is how to fix this from someone.
Click to expand...
Click to collapse
It does NOT require unlocking the bootloader to flash your carrier's correct ROM. Simply follow the instructions in the "Return to 100% Stock" thread to flash the XT1053 ROM, and you'll be able to take all future updates.
If you DO unlock the bootloader, flash custom recovery, and root your device, you will have to un-do any modifications made before EVERY OTA. If you don't care about root, don't worry about unlocking.
Additionally, if you DO want to unlock, you could try a different browser and make sure you are inputting the unlock data correctly. It is recommended that you copy the unlock data from the command prompt to notepad, remove all spaces and bootloader messages (you ONLY want the code - as one complete string), then copy from notepad into the Unlock website.
And finally, keep in mind that unless you unlock your BL, you will not be able to root and disable write-protect once you update to the latest version.
The real problem here is that you use an "Exploit" to root your device previously. Now you need to return to full stock to restore your partitions to their factory state.
Simply follow the instructions in the Return to stock thread (in general sub-forum), and be sure to flash the LATEST version for your carrier. It should be 4.4.3.
Good Luck.
samwathegreat said:
I confused you with a member I had helped previously - sorry. Please disregard the "previously stated" comment.
It does NOT require unlocking the bootloader to flash your carrier's correct ROM. Simply follow the instructions in the "Return to 100% Stock" thread to flash the XT1053 ROM, and you'll be able to take all future updates.
If you DO unlock the bootloader, flash custom recovery, and root your device, you will have to un-do any modifications made before EVERY OTA. If you don't care about root, don't worry about unlocking.
Additionally, if you DO want to unlock, you could try a different browser and make sure you are inputting the unlock data correctly. It is recommended that you copy the unlock data from the command prompt to notepad, remove all spaces and bootloader messages (you ONLY want the code - as one complete string), then copy from notepad into the Unlock website.
And finally, keep in mind that unless you unlock your BL, you will not be able to root and disable write-protect once you update to the latest version.
The real problem here is that you use an "Exploit" to root your device previously. Now you need to return to full stock to restore your partitions to their factory state.
Simply follow the instructions in the Return to stock thread (in general sub-forum), and be sure to flash the LATEST version for your carrier. It should be 4.4.3.
Good Luck.
Click to expand...
Click to collapse
So if I am reading this correctly, there is no way to keep all of my data and take the update?
danman421 said:
So if I am reading this correctly, there is no way to keep all of my data and take the update?
Click to expand...
Click to collapse
You can attempt to, by either editing the XML in the SBF and removing the line that says "erase userdata", or by skipping the erase userdata if you use the manual method, but either way CAN mess everything up.
You used an EXPLOIT previously. Any time you use an exploit, you should -expect- to have to wipe everything and re-install from scratch if you want to get back to stock in order to be able to take updates. Keep this in mind if you use any exploits in the future.
Hi! This hasn't seemed to spelled out yet..... But many Moto x's can be unlocked, not just dev editions. However, you stated in the opening post that you have a Verizon Non dev, which can not be unlocked. Only way is to pay the "China middleman" (See thread in general with that name).
And personally.... I would stay on 4.2.2 and do the Slapmymoto method to get root and write protection disabled. That is the best root scenario, aside from unlocking the bootloader.
If you update to 4.4.2 or higher, you will have write protection enabled always, and no root, or sorta root with towelroot and pie. But that will limit what you can do.
See the How do I root my phone sticky thread in general for your options.
I should have posted earlier. I ran RSDLite and put the newest version on. I am unrooted. My Moto X is a Sept '13 version the the middleman probably wont work anyways. Its not worth it with this phone, im tired of the rooting, I guess im at that point in my life... Thanks for all your help though guys!
danman421 said:
I am running a Verizon Moto X still on 4.2.2. I am rooted. This is NOT the Dev edition. I have plenty of experience with rooting/flashing these phones so back when I first got it the directions on rooting/flashing roms was VERY vague. No one specified you needed the Dev edition to unlock the boot loader. Well I think this came from at one point when I tried to flash TWRP (maybe). Either way, I want to take the OTA update and cannot. Does anyone know how to fix this without doing the RSD, reflash stock method? Here is a picture of what it looks like (thanks for your help in advance):
Click to expand...
Click to collapse
Pardon my jumping in here late but..
I see a big issue here.
Based on that screen shot, you have boot loader 30.B4, that is NOT the bootloader that comes wtih 4.2.2. Did you mean to type 4.4.2? or do you really have 4.2.2 on there?
If you really had 4.2.2 on your phone with a 30.B4 bootloader, then you had 4.4.2 on there at one point, and downgraded!! You need to be REALLY CAREFUL or you will brick your phone.
You are correct, I was on 4.4.2. My wife's S4 that I just upgraded was on 4.2.2. Sorry for the confusion.
KidJoe said:
Pardon my jumping in here late but..
I see a big issue here.
Based on that screen shot, you have boot loader 30.B4, that is NOT the bootloader that comes wtih 4.2.2. Did you mean to type 4.4.2? or do you really have 4.2.2 on there?
If you really had 4.2.2 on your phone with a 30.B4 bootloader, then you had 4.4.2 on there at one point, and downgraded!! You need to be REALLY CAREFUL or you will brick your phone.
Click to expand...
Click to collapse
Good catch! ?
OP... Perhaps full disclosure of what you have done on the phone would help.
Or is that how it was?
If it's been downgraded to 4.2.2 after being on 4.4.2... As said above.... You could brick now... Especially if you OTA.
I'd tread lightly at this point.
danman421 said:
You are correct, I was on 4.4.2. My wife's S4 that I just upgraded was on 4.2.2. Sorry for the confusion.
Click to expand...
Click to collapse
so based on post # 14 of this post... it appears you are all good now? is that the case? Or do you still need help?
Oh, and if your bootloader is locked (Verizon non-DE), you can't get code from China Middle man, and you are on 4.4.2, you could try TowelPieRoot for rooting, but write protection is enabled so it will be kind of limited (compared to SlapMyMoto/MotoWPNoMO or if you had an unlocked bootloader), and there is no root for 4.4.4.
Yes, that was a good catch. What I did was RSD Lite to 4.4.4 now which reset all my data.
KidJoe said:
so based on post # 14 of this post... it appears you are all good now? is that the case? Or do you still need help?
Oh, and if your bootloader is locked (Verizon non-DE), you can't get code from China Middle man, and you are on 4.4.2, you could try TowelPieRoot for rooting, but write protection is enabled so it will be kind of limited (compared to SlapMyMoto/MotoWPNoMO or if you had an unlocked bootloader), and there is no root for 4.4.4.
Click to expand...
Click to collapse
Correct, I do not need help anymore but thank you.

Moto X HELP! I think i bricked it after update!

Hello,
I got my Moto X few days back from America, its Verizon model (I live in Europe)
its not developer edition and bootloader is locked
...and first issue i noticed is when i try to reset to factory with power UP + DOWN volume i couldnt get recovery.. when i go to recovery settings i see moto logo and then verizon picture.. there is no "dead android" and phone boots normaly.
...second thing there was android 4.4 on it and i got notifications to update it, so i was like why not, lets do it... and after i decided to update, phone keeps rebooting itself, and i dont know what to do it stays awake like 10-20sec and reboot again. Cant belive i bricked it that way!
Phone seems that its not rooted or anything, but idk maybe it was and then back to stock.. Is there any solution?
Thanks in advance to any1 who can help me slove the problem
Cheers
Resurrecting A Bricked Moto X
drvoje said:
Hello,
I got my Moto X few days back from America, its Verizon model (I live in Europe)
its not developer edition and bootloader is locked
...and first issue i noticed is when i try to reset to factory with power UP + DOWN volume i couldnt get recovery.. when i go to recovery settings i see moto logo and then verizon picture.. there is no "dead android" and phone boots normaly.
...second thing there was android 4.4 on it and i got notifications to update it, so i was like why not, lets do it... and after i decided to update, phone keeps rebooting itself, and i dont know what to do it stays awake like 10-20sec and reboot again. Cant belive i bricked it that way!
Phone seems that its not rooted or anything, but idk maybe it was and then back to stock.. Is there any solution?
Thanks in advance to any1 who can help me slove the problem
Cheers
Click to expand...
Click to collapse
Try this http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057
Is there any way to try to delete chache or factory reset before flashing to stock rom
drvoje said:
Is there any way to try to delete chache or factory reset before flashing to custom rom
Click to expand...
Click to collapse
If its not the developer edition for Verizon, the bootloader is likely locked, so you can NOT flash custom roms (unless you, or a previous owner, got a bootloader unlock code from the China Middleman and used it)
Did you buy the phone used, or new? If used, then it is possible that it was rooted using RockMyMoto, SlapMyMoto or the like... and the boot loop while trying to install an update could be due to that. If so, erasing cache will stop the boot loop. This can be done from stock recovery, or when in Bootloader/FastbootAP mode.
How to Boot into recovery -> http://mark.cdmaforums.com/MotoX-EnterStockRecovery.htm
If that doesn't work, try bootloader/fastboot....
How to get a working AndroidSDK/PlatformTools/ADB/Mfastboot setup -> http://mark.cdmaforums.com/ADB.htm
How to boot the phone into fastboot mode -> http://mark.cdmaforums.com/MotoX-BootloaderMode.htm
from your PC, do a mfastboot erase cache
to reboot the phone, mfastboot reboot
Optionally, you could do a mfastboot erase userdata before rebooting, to remove all data, apps, etc.
If erasing cache fixes the boot loop, you might just want to try using RSDLite and reflashing the STOCK rom, recovery, etc. (Download the Verizon 4.4.4 SBF from -> http://sbf.droid-developers.org/phone.php?device=0 then follow -> http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515 ) It would undo anything that was done to root your device, and put you back to factory fresh. The only reason not to, would be if you care about rooting and disabling write protection..
With a locked bootloader, If your phone is still on 4.4 (aka 4.4.0), and still has that older bootloader and gpt.bin, you could use SlapMyMoto to root, and MotoWpNoMo to disable write protection. Just don't take any updates. You could cause a bootloop, but more importantly it will re-enable write protection with no way to disable it again (unless you can unlock the bootloader).
Once your phone is on 4.4.2 or above, you can't properly downgrade the ROM, bootloader and gpt.bin to use the exploits used by SlapMyMoto/MotoWpNoMo. There is a TowelPieRoot which is a temp root that works on 4.4.2. Temp root in the fact that it doesn't survive power off/on, so it needs to be redone each time. Also it doesn't disable write protection, so any changes made to /system or the like are also lost at power off/on (aka hard boot).
Once on 4.4.4, you can't properly downgrade the ROM, bootloader and gpt.bin, and there are no exploits to root, and no way to disable write protection.
If you can use the China Middleman thread to get a bootloader unlock code, then you don't need to worry about the exploits, and you can then root and disable write protection just as if you had a developer edition. Also JCASE may be updating their Sunshine tool to use the exploit found by Dan Rosenberg to unlock the bootloader on the Moto X, but there is no exact date yet of when it will be available (so far "next few weeks" has been said, but nothing more specific), and there is discussion around will it work for those who took the 4.4.4 update or not (no confirmation yet either way).
KidJoe;55503494
If that doesn't work said:
[*]How to get a working AndroidSDK/PlatformTools/ADB/Mfastboot setup ->
[*]How to boot the phone into fastboot mode ->
[*]from your PC, do a mfastboot erase cache
[*]to reboot the phone, mfastboot reboot
[/list]
Click to expand...
Click to collapse
did this with mfastboot image and worked like charm
bdw now i will need some time reading what is best to do with my unlockable bootloader verizon phone, if u have any sugestions please let me know.
and tnx for the help again mate
drvoje said:
bdw now i will need some time reading what is best to do with my unlockable bootloader verizon phone, if u have any sugestions please let me know.
Click to expand...
Click to collapse
You said its a verizon phone, but not the developer edition..
So at this point, the only way to unlock the bootloader is the China Middleman thread (in the general section). When JCASE updates Sunshine for the X (in the coming week or two), you can try that.
Otherwise, there isn't anything you can do.
and for stock android update? which one is the best for moto x? now it is 4.4.0
shall i rsd lite it to 4.4.2 or 4.4.4 or just stay current one?
bdw i need to rsd lite frimware anyway if i plan to use OTA update again perhaps when android L come? For now i just keep ignoring them
and yes its NOT developer edition phone
drvoje said:
and for stock android update? which one is the best for moto x? now it is 4.4.0
shall i rsd lite it to 4.4.2 or 4.4.4 or just stay current one?
bdw i need to rsd lite frimware anyway if i plan to use OTA update again perhaps when android L come? For now i just keep ignoring them
and yes its NOT developer edition phone
Click to expand...
Click to collapse
THe best depends on what you want to do.
Like I said before. IF you have 4.4 (aka 4.4.0) on the phone, and NEVER had anything newer on there (not 4.4.2 or 4.4.4), then stay there, look at SlapMyMoto and MotoWpNoMo to root and disable write protection.
Once you get 4.4.2 on there, you can root, but its temp root, and write protection can NOT be disabled.
4.4.4 you can't root.
Other than that, I can't say I really find too much difference. The camera is better in 4.4.4, but the battery isn't performing as well lately (could be a recent app update).
can i do this on my phone now - without fear of bricking it:
from my pc to run mfastboot again
then to clear chache
then to delete all user data
then to use rsd lite and flash Android 4.4
Blur_Version.140.45.5.ghost_verizon.Verizon.en.US even i alrdy have 4.4 now?
..because i dont know what is done to my phone before and i want to make sure its like "new" device
i know i can not downgrade, but can i flash same frimware? just to make sure thats all stock again
bdw Im stll unable to enter recovery after fastboot :/ is it that because of locked bootloeader? or because it was rooted with any method? i cant find superuser
and then to wait for solution to unlock bootleader?
Thanks in advance
You can always re-flash the same rom that is on your phone.
You just never want to down grade, or flash something older than what is on your phone.
As for not being able to enter Stock Recovery... early versions of the RockMyMoto and such did a trick which made it so that when you picked boot to recovery, it booted to regular system with write protection disabled. If that was used on your phone before you purchased it, that could be the issue. Using RSDLite and flashing back to 100% stock will undo that.
But You never answered if you got the phone new or used.
IF new, then you have some other issue (either you're not doing it right, or there is something wrong with the phone).
If used, you don't know what was done before you received it. Someone might have rooted, etc.. then just removed SuperSU to appear non-rooted when selling, rather than flashing back to stock.
thanks for the reply...
yes phone is used before but same like new... and what i found that phone was rooted by some method.. i made this screenshots, look in attachment..
bdw i dont see super su anywhere in apps? how to remove?
and i got everything rdy to flash it, i was just waiting you to conform if its doable...
and what did u mean by this:
"With a locked bootloader, If your phone is still on 4.4 (aka 4.4.0), and still has that older bootloader and gpt.bin, you could use SlapMyMoto to root, and MotoWpNoMo to disable write protection. Just don't take any updates. You could cause a bootloop, but more importantly it will re-enable write protection with no way to disable it again (unless you can unlock the bootloader)."
is that what happened to me?
and have question about one more thing
my country does not support lte and in my region 3g is bad... i have stable signal all the time but i would like to use edge only (GSM), can i do that using some widgets and if can which ones?
drvoje said:
thanks for the reply...
yes phone is used before but same like new... and what i found that phone was rooted by some method.. i found this screenshot in phone, look in attachment..
bdw i dont see super su anywhere in apps? how to remove?
and i got everything rdy to flash it, i was just waiting you to conform if its doable...
Click to expand...
Click to collapse
If you mean you don't see a SuperSU icon in the app drawer, then they probably un-installed SuperSU before selling it rather than completely unrooting. If you mean you have an icon in the app drawer, but don't see it to uninstall under Settings -> Apps.. I don't know why that would be.
drvoje said:
and what did u mean by this:
"With a locked bootloader, If your phone is still on 4.4 (aka 4.4.0), and still has that older bootloader and gpt.bin, you could use SlapMyMoto to root, and MotoWpNoMo to disable write protection. Just don't take any updates. You could cause a bootloop, but more importantly it will re-enable write protection with no way to disable it again (unless you can unlock the bootloader)."
is that what happened to me?
Click to expand...
Click to collapse
Yes, that could be what happened to you. There are many reports of locked bootloader users who used those older root processes who then upgraded using the OTA from 4.4 to 4.4.2 that encountered bootloops and other issues. It was often recomended to reflash to 100% stock.
And what I meant is that if you are on 4.4 (aka 4.4.0) with all its parts, it is vulnerable and the older exploits can still be used to root and disable write protection without unlocking your bootloader. Search for SlapMyMoto for more details. Some people tried to be cute and mix/match parts which caused issues. Mostly the issues around downgrading are caused by GPT.BIN and Motoboot.IMG parts, their versions, if they've been upgraded and no longer match the rest of the rom on the phone, etc. (and that is a LONG story...)
drvoje said:
and have question about one more thing
my country does not support lte and in my region 3g is bad... i have stable signal all the time but i would like to use edge only (GSM), can i do that using some widgets and if can which ones?
Click to expand...
Click to collapse
You can TRY using something like LTE On/Off to open the hidden menu and set for GSM Auto (PRL) or LTE GSM Auto(PRL). I'm not sure which would work best.
Oh, and as for unlocking the bootloader, I've mentioned the China Middleman and JCASE's Sunshine so there are the links to read up if you want to do it.
The China Middleman is just like if you got the code directly from Moto. I don't know what the Jcase tool is like yet.
thanks again!
so i dont see a SuperSU icon in the app drawer - uninstalled probably and that is why i can not enter stock recovery
I am still on android 4.4 didnt do anything yet...
what u recommend me to do? to rsd lite it to 4.4 again? right?
than i will root my device
and about bootloader, my device is 9.2013, so i will wait JCASE's Sunshine and support him
ps. wiget works gr8 :good:
Just want to write some words, i just took jcase tool which is very easy to setup (made for noobs like me) and i got bootloader UNLOCKED on my verizon NON developer edition phone
and now i RSD lite to 4.4 stock rom
would like to hear from KidJoe what is best to do with my moto x now thanks
Now you can update to 4.4.4,whichever methods you want, and still root it. Done. ?
drvoje said:
Just want to write some words, i just took jcase tool which is very easy to setup (made for noobs like me) and i got bootloader UNLOCKED on my verizon NON developer edition phone
and now i RSD lite to 4.4 stock rom
would like to hear from KidJoe what is best to do with my moto x now thanks
Click to expand...
Click to collapse
Follow [mention]@KJ[/mention] 's advice and update to 4.4.4, and follow the Dev Edition or Unlocked Bootloader guides to rooting (flash the latest TWRP and root.)

Categories

Resources