Related
Hi there everyone,
I have a huge problem. Last night i bricked my xoom. I was following a tutorial on this forum. and after unlocking the bootloader it told to flash a file called boot.img after doing so and typing fastboot reboot, the device wouldnt start behind the motorola logo. i tried allot of thing and also did flash some other stock android 4.0.4 boot.img files now with the last one mentioned i managed to get the xoom (wifi) to boot a little further. because the ripple movie with the motorola logo is shown. but it stucks at that movie.
Does anyone know if i can flash an image on the xoom that will atleast fix the problem of not rebooting so i can try another tutorial.
I have searched the internet for solutions, many of them linked to threads on this forum. but almost all download links in these tutorials are old and broken.
Can someone please help me unbrick my device? And maybe a link to a good working unroot tutorial for my xoom wifi with android 4.0.4.
Try get back to Stock.
Download from HERE
and do some OTA updates afterwards so everything will be up to date.
Then wipe and try again from scratch..
Worked for me perfectly just a few days ago.
If you can still get into fastboot, then its not bricked.
Get some stock images and flash them via fastboot and you'll be fine.
Cubanluke88 said:
If you can still get into fastboot, then its not bricked.
Get some stock images and flash them via fastboot and you'll be fine.
Click to expand...
Click to collapse
Indeed it worked. i downloaded the official images and flashed them im on android 3.0.1 again and all seems to work just fine now.
Next problem is i cant find a descent tutorial on this forum how to root the xoom. all download links are either removed due to copyright issues or the links are just broken.
How does it work actually?
1. I unlocked the boot loader wich is very easy.
but then? Do i need to flash a rooted image over the existing? i dont really understand how this works. I rooted my Desire HD with a good tutorial in minutes. Not many people seems to really know how to root the Xoom.
Also i would like to know if the different tutorials are for different android versions or can i aply all tutorials of rooting when i stay on android 3.0.1?
I also tried to flash a recovery.img to the recovery partition and press volume down 3 seconds after the moto logo apears but when i do i get an android robot with a big " ! " on his belly and it takes 5 minutes to load the menu. when im in it tells me there is no sdcard present when i try to flash a rooted rom (zip file).
Is there someone reading this thats willin to explain to me how to do a root the easiest way? Please if links are posted be sure everything on that thread is working. Im pretty sure i will pull it off with some push in the right direction.
Thank you!
(edit) omg im stupid, offcourse the sdcard wont work... it never worked at 3.0.1. on the xoom. can i follow this tutorial:
http://rootzwiki.com/topic/451-how-to-root-the-wifi-only-xoom-301/
Could someone read over it and see if this is a good tutorial? last time i flashed a boot.img the whole xoom got stuck... is that because i had the wrong boot.img on the wrong android version? or should boot.img always work?
Do you plan on flashing to a custom rom after rooting? If so, you can just skip rooting altogether.
I say this because I'm not particularly familiar with that rooting method you linked (though reading through it, it makes sense, all its doing is pushing the necessary files for root access to the xoom via adb). I used a rooting script flashed through a custom recovery over a year ago - unfortunately the download link seems to be broken (I might have a copy at home).
So there's a few things you can do:
1. If you just want a custom rom - download the rom zip file and store on your device. Flash TWRP (my preferred recovery) in fastboot. Boot into TWRP and flash the rom zip file.
2. If you want stock OS root access -
a) Follow those steps you linked and see what happens. If things go wrong, you should be able to just flash those stock images again.
b) Wait for me to get home and see if I have the root script. You'll need to flash a custom recovery though in order to use it.
Cubanluke88 said:
Do you plan on flashing to a custom rom after rooting? If so, you can just skip rooting altogether.
I say this because I'm not particularly familiar with that rooting method you linked (though reading through it, it makes sense, all its doing is pushing the necessary files for root access to the xoom via adb). I used a rooting script flashed through a custom recovery over a year ago - unfortunately the download link seems to be broken (I might have a copy at home).
So there's a few things you can do:
1. If you just want a custom rom - download the rom zip file and store on your device. Flash TWRP (my preferred recovery) in fastboot. Boot into TWRP and flash the rom zip file.
2. If you want stock OS root access -
a) Follow those steps you linked and see what happens. If things go wrong, you should be able to just flash those stock images again.
b) Wait for me to get home and see if I have the root script. You'll need to flash a custom recovery though in order to use it.
Click to expand...
Click to collapse
Ok thanks for your answer. Ill try to unroot with that method flashing directly to the recovery.img i also know now what i did wrong. i flashed the recovery.img not to the recovery partition but to the boot partition LOL. thats why the xoom didnt boot anymore
I see allot about Nightlies Eos, 4.1.1. is that a good rom? Does it look like the stock version?
eos 4.1.1 is simply awesome and its also pre rooted' so your bootloader is unlocked, all you gotta do now is install twrp recovery via fastboot ( my preffered recovery) then flash eos via recovery
Sent from my Xoom using XDA Premium App
sygys said:
Ok thanks for your answer. Ill try to unroot with that method flashing directly to the recovery.img i also know now what i did wrong. i flashed the recovery.img not to the recovery partition but to the boot partition LOL. thats why the xoom didnt boot anymore
I see allot about Nightlies Eos, 4.1.1. is that a good rom? Does it look like the stock version?
Click to expand...
Click to collapse
EOS is a pretty AOSP rom. No theme, though you can apply one if you like and change a few colors. There are various toggle additions you can add that make the user experience much better. It also comes with an overclockable kernel and is very very stable (despite being a nightly) The team has been supporting the Xoom for over a year and is very committed to the Xoom.
---------- Post added at 01:15 PM ---------- Previous post was at 01:11 PM ----------
sygys said:
Ok thanks for your answer. Ill try to unroot with that method flashing directly to the recovery.img i also know now what i did wrong. i flashed the recovery.img not to the recovery partition but to the boot partition LOL. thats why the xoom didnt boot anymore
I see allot about Nightlies Eos, 4.1.1. is that a good rom? Does it look like the stock version?
Click to expand...
Click to collapse
As for flashing, just gotta make sure your text is good before hitting the enter key. Recovery flash should look something like this:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Some instructions for flashing can be found here
While that page is specifically for locking and flashing to return to stock, the commands are universal for fastboot. Hell, if you wanted to, you could manually restore a nandroid backup via fastboot and flashing images.
Alright, so here's the issue. I tried to flash a version of CW onto my HDMaxx (XT926) and it failed, saying the file size was incorrect. Now, whenever I boot, it goes to the same recovery screen and says that the flash failed, even when I don't boot into recovery. After many failed attempts, I still cannot reflash the recovery. It still boots if I manually go into the bootloader and just select normal bootup, but as you can imagine, it gets pretty old having to do that. I just installed OTA JB yesterday, and it worked fine (after manually installing the zip myself) but the same problem still occurs on boot. Any help? Thanks in advance.
Action123 said:
Alright, so here's the issue. I tried to flash a version of CW onto my HDMaxx (XT926) and it failed, saying the file size was incorrect. Now, whenever I boot, it goes to the same recovery screen and says that the flash failed, even when I don't boot into recovery. After many failed attempts, I still cannot reflash the recovery. It still boots if I manually go into the bootloader and just select normal bootup, but as you can imagine, it gets pretty old having to do that. I just installed OTA JB yesterday, and it worked fine (after manually installing the zip myself) but the same problem still occurs on boot. Any help? Thanks in advance.
Click to expand...
Click to collapse
Reflash stock firmware. Check the stock firmware thread for your device in development subforum.
Its usually a good idea to flash to stock before upgrading os anyway.
Action123 said:
Alright, so here's the issue. I tried to flash a version of CW onto my HDMaxx (XT926) and it failed, saying the file size was incorrect. Now, whenever I boot, it goes to the same recovery screen and says that the flash failed, even when I don't boot into recovery. After many failed attempts, I still cannot reflash the recovery. It still boots if I manually go into the bootloader and just select normal bootup, but as you can imagine, it gets pretty old having to do that. I just installed OTA JB yesterday, and it worked fine (after manually installing the zip myself) but the same problem still occurs on boot. Any help? Thanks in advance.
Click to expand...
Click to collapse
you said HDMaxx? do you have a retail verizon razr hd? because clockwork is only for developer devices unlocked. and im pretty sure they dont have a developer Maxx HD
You need to successfully flash any of your partitions with a signed image in fast boot. Pick a small and relatively minor one like device tree.
The bootup error you are seeing means that an unsigned image was attempted to be flashed on a locked boot loader device and should go away once any properly signed image is flashed again afterwards. You could just flash the stock recovery image from the full XML fast boot file too.
The device should boot normally again thereafter.
zooyork0721 said:
you said HDMaxx? do you have a retail verizon razr hd? because clockwork is only for developer devices unlocked. and im pretty sure they dont have a developer Maxx HD
Click to expand...
Click to collapse
cellzealot said:
You need to successfully flash any of your partitions with a signed image in fast boot. Pick a small and relatively minor one like device tree.
The bootup error you are seeing means that an unsigned image was attempted to be flashed on a locked boot loader device and should go away once any properly signed image is flashed again afterwards. You could just flash the stock recovery image from the full XML fast boot file too.
The device should boot normally again thereafter.
Click to expand...
Click to collapse
No, It is an HDMaxx. It has the version XT926, but it is stock Verizon. Does anyone have any knowledge of a thread with an instructional for unlocking my bootloader and a clockwork/Amon Ra/etc. flash? I'm just struggling to find anything. Almost seems like very few people are working with my device as of this moment.
Action123 said:
No, It is an HDMaxx. It has the version XT926, but it is stock Verizon. Does anyone have any knowledge of a thread with an instructional for unlocking my bootloader and a clockwork/Amon Ra/etc. flash? I'm just struggling to find anything. Almost seems like very few people are working with my device as of this moment.
Click to expand...
Click to collapse
Verizon branded XT926 are bootloader locked, period. Verizon insisted it be that way. Since the HD Maxx doesn't have a developer's edition (which you can unlock the bootloader on), you are limited to hacks/workarounds that use a signed kernel to load a custom one. Check the Developers forum for hack posts.
EdwardN said:
Verizon branded XT926 are bootloader locked, period. Verizon insisted it be that way. Since the HD Maxx doesn't have a developer's edition (which you can unlock the bootloader on), you are limited to hacks/workarounds that use a signed kernel to load a custom one. Check the Developers forum for hack posts.
Click to expand...
Click to collapse
Thank you sir.
Action123 said:
No, It is an HDMaxx. It has the version XT926, but it is stock Verizon. Does anyone have any knowledge of a thread with an instructional for unlocking my bootloader and a clockwork/Amon Ra/etc. flash? I'm just struggling to find anything. Almost seems like very few people are working with my device as of this moment.
Click to expand...
Click to collapse
Google safe strap for this device. We don't have clockwork on the consumer version but we do have safestrap which uses TWRP recovery. I use that to flash stuff. It's actually better because you leave your stock rom on the safe side and flash on the other partition and don't have to worry about bricking anything.
Sent from my DROID RAZR HD using xda premium
clouse2013 said:
Google safe strap for this device. We don't have clockwork on the consumer version but we do have safestrap which uses TWRP recovery. I use that to flash stuff. It's actually better because you leave your stock rom on the safe side and flash on the other partition and don't have to worry about bricking anything.
Sent from my DROID RAZR HD using xda premium
Click to expand...
Click to collapse
I did read up on TWRP a while ago. It kinda looked like a pain to me. I don't know, but I just want to be able to boot straight into my ROM of choice immediately without having to go through a bootloader (for someone other than myself, not in the knowing of what they're doing ICE). I used to have an N1 running CM7 and it was just what I wanted. Are there any downfalls of using this method that you have seen?
So i have a Droid Razr Maxx HD xt926
it is on the latest 4.2.1 ota
It was starting to run slow, so i figured it was time to root and get a custom rom. but what i didn't realize is you cant unlock boot-loader.
So i rooted the phone, no issues. i tried to flash TWRP and CWM and both failed.
So when i go to recovery all i get is a black screen with white writiing that says
AP Fastboot Flash Mode (s)
10.9B(#) (sha-1e9f, 2013-05-25 01:04:26)
eMMC info: Size 32GB
Divice is LOCKED, Status Code: 0
Battery OK
Connect USB
Data Cable
Failed to hab check for recovery: 0x56
Fastboot Reason: Boot Failure
I can exit out and get back to android.
Since i can get the bootloader unlocked (at least i dont think there is a way) i want to flash everything back to factory, it can be unrooted as well. just want a clean start on it.
any help would be great thanks.
Can't flash twrp or cm on locked bootloader.
Sent from my DROID RAZR HD using xda app-developers app
xlow78 said:
Can't flash twrp or cm on locked bootloader.
Sent from my DROID RAZR HD using xda app-developers app
Click to expand...
Click to collapse
Yea i figured that out, so i was triing to get it back to stock.
Figured too late though .
Did you try rsd lite?
Sent from my DROID RAZR HD using xda app-developers app
soloblazer said:
So i have a Droid Razr Maxx HD xt926
it is on the latest 4.2.1 ota
It was starting to run slow, so i figured it was time to root and get a custom rom. but what i didn't realize is you cant unlock boot-loader.
So i rooted the phone, no issues. i tried to flash TWRP and CWM and both failed.
.............
any help would be great thanks.
Click to expand...
Click to collapse
sounds like you jacked stock recovery. if it will boot up, try using this http://www.mediafire.com/download/tt7cwwua49n24uv/Razr_HD_Recovery_Flasher_V7.rar to put the stock recovery back on. i cant say for sure it will work but i think it will.
bweN diorD said:
sounds like you jacked stock recovery. if it will boot up, try using this http://www.mediafire.com/download/tt7cwwua49n24uv/Razr_HD_Recovery_Flasher_V7.rar to put the stock recovery back on. i cant say for sure it will work but i think it will.
Click to expand...
Click to collapse
If the bootloader is locked, it's highly unlikely that attempting to flash a recovery would've touched the stock recovery. With that being said, you can use one of the utilities to flash back to completely stock or use RSD and flash the most up-to-date XML from here:
http://sbf.droid-developers.org/vanquish/list.php
RikRong said:
If the bootloader is locked, it's highly unlikely that attempting to flash a recovery would've touched the stock recovery. With that being said, you can use one of the utilities to flash back to completely stock or use RSD and flash the most up-to-date XML from here:
http://sbf.droid-developers.org/vanquish/list.php
Click to expand...
Click to collapse
true but you have to modify files before rsd will work, and the utilities say dont use on the latest update (locked) unless there is one i haven't seen, correct?
bweN diorD said:
true but you have to modify files before rsd will work, and the utilities say dont use on the latest update (locked) unless there is one i haven't seen, correct?
Click to expand...
Click to collapse
I've never had to modify the XMLs to work in RSD, but you might have to for some of them. You can swap files in the utilities and put the newest update in there. Also, flashing your zip or any other zip should clear the flash fail.
RikRong said:
I've never had to modify the XMLs to work in RSD, but you might have to for some of them. You can swap files in the utilities and put the newest update in there. Also, flashing your zip or any other zip should clear the flash fail.
Click to expand...
Click to collapse
Hey guys thanks for all the answers, i will try this monday, sorry for late reply, had some things come up this weekend, so wont have time to work on it. I just want to get it back to completely stock since i cant unlock the bootloader and isntall custom rom.
soloblazer said:
Hey guys thanks for all the answers, i will try this monday, sorry for late reply, had some things come up this weekend, so wont have time to work on it. I just want to get it back to completely stock since i cant unlock the bootloader and isntall custom rom.
Click to expand...
Click to collapse
Ok guys i am ready to try. How do i flash a zip file if i cant get into recovery?
What should i try first?
soloblazer said:
Ok guys i am ready to try. How do i flash a zip file if i cant get into recovery?
What should i try first?
Click to expand...
Click to collapse
boot the phone up (just power on), after on plug it into your pc, use the tool i posted in #5 (just going off what RikRong said, any successful flash should clear the failure) flash "stock recovery", let it reboot and see if its fixed.
if its not fixed, im still under the impression you will have to do one of 2 things to fix it from what i read others post previously,
-replace the files in matts utility with the latest ones from the stock files, or
-modify the xml file in the latest sbf to get rsd to work without failing
bweN diorD said:
boot the phone up (just power on), after on plug it into your pc, use the tool i posted in #5 (just going off what RikRong said, any successful flash should clear the failure) flash "stock recovery", let it reboot and see if its fixed.
if its not fixed, im still under the impression you will have to do one of 2 things to fix it from what i read others post previously,
-replace the files in matts utility with the latest ones from the stock files, or
-modify the xml file in the latest sbf to get rsd to work without failing
Click to expand...
Click to collapse
First one worked, thanks guys, phone is good to go. Does anyone know if there will ever be a unlocker for the bootloader?
soloblazer said:
First one worked, thanks guys, phone is good to go. Does anyone know if there will ever be a unlocker for the bootloader?
Click to expand...
Click to collapse
unlikely
btw, i swapped the files in Matts utility for the latest update if you want it. im working on switching out the root method in it too to the new one.
its posted in the dev forum
CM10.1 Android 4.2.2 Razr HD XT925
Already installed various recoveries only my device so enter the stock recovery, bootloader unlocked with this, I want to install cm10.1.3 4.2.2 and I can not, can someone help me?
My Droid Razr HD is doing the same thing
My screen says all of that also.
its says its locked and the battery is ok and all of that
I was trying to root my phone which was unsuccessful.
Now I cannot start and run my phone properly.
when it comes on it has me choose a language and press start and then acts like its loading and says it may take a few minutes. It will do that for hours and never move on to the next step.
How did you fix yours and recover it?
None of the other options on the reboot screen work...
I had tried:
normal start up
AP fast Boot
Recovery
BP Tools
They all lead to the same thing with the language selection and so on.
What can I do?
McmanisCody said:
My screen says all of that also.
its says its locked and the battery is ok and all of that
I was trying to root my phone which was unsuccessful.
Now I cannot start and run my phone properly.
when it comes on it has me choose a language and press start and then acts like its loading and says it may take a few minutes. It will do that for hours and never move on to the next step.
How did you fix yours and recover it?
None of the other options on the reboot screen work...
I had tried:
normal start up
AP fast Boot
Recovery
BP Tools
They all lead to the same thing with the language selection and so on.
What can I do?
Click to expand...
Click to collapse
assuming you have a 926, re-flash it with this.
if you have a 925 do NOT use ^^ that. you will have to use rsd instead.
I am having a similar issue but my bootloader is unlocked and no matter what I flash to recovery recovery won't work anymore whether it being a factory reset or trying to just plain boot in to it.
CONC3PT said:
I am having a similar issue but my bootloader is unlocked and no matter what I flash to recovery recovery won't work anymore whether it being a factory reset or trying to just plain boot in to it.
Click to expand...
Click to collapse
on the bootloader screen it says "status code 3" correct?
you cant flash cwm or twrp with fastboot?
what exactly is it doing or not doing and does the flash dialog indicate it flashing ok?
you imply, you cant boot into recovery, then say a factory reset wont work. what happens exactly in either of those attempts?
after you flash a custom recovery, you have to power off the phone and boot right into it and flash the su zip (do not boot the system in between), you know that correct?
any other info you can provide that i may have left out could be helpfull in getting this working for you.
Hello everyone,
I know this tread is old but, I have a problem and I hope someone here can help me. I have a mot razr 926 with these specs:
android version 4.1.2;
System version 9.30.1.XT926.Verizon
Kernel 3.0.31 ( I believe is stock)
Build number 9.8.1Q-94-1
My phone was rooted before with stock rom; I had to do a factory reset; so I reset, rooted again and my mistake it was trying to unlock the bootloader ( I know, I know, it's 9.30....)
Now my problem is that I don't have "recovery" or I don't have access to it. Things that I have tried:
Moto utility 1.34
Moto utility 1.3 gpt fix
Razr HD Recovery flasher V7 (tried to install cwm and stock)
I'm just trying to get any recovery working.... any help would be appreciated
Thanks
kpitao said:
Hello everyone,
I know this tread is old but, I have a problem and I hope someone here can help me. I have a mot razr 926 with these specs:
android version 4.1.2;
System version 9.30.1.XT926.Verizon
Kernel 3.0.31 ( I believe is stock)
Build number 9.8.1Q-94-1
My phone was rooted before with stock rom; I had to do a factory reset; so I reset, rooted again and my mistake it was trying to unlock the bootloader ( I know, I know, it's 9.30....)
Now my problem is that I don't have "recovery" or I don't have access to it. Things that I have tried:
Moto utility 1.34
Moto utility 1.3 gpt fix
Razr HD Recovery flasher V7 (tried to install cwm and stock)
I'm just trying to get any recovery working.... any help would be appreciated
Thanks
Click to expand...
Click to collapse
Have you tried the stock recovery??, it can be tricky to get into stock recovery by pressing the correct combination of buttons
EDIT: You can use RSD Lite to update your phone to 182.46.10 and use Towelroot to re-root the phone. Once rooted, you can use Motoapocalypse to unlock bootloader.
EDIT 2: Read this thread: http://forum.xda-developers.com/droid-razr-hd/general/index-motorola-droid-razr-hd-2015-t3167557
Anyone know where I can get the latest stock ROM for a RAZR HD XT926 from a trusted source? I'm a bit nervous about downloading just any old file that claims to be a stock ROM. Who knows what could be embedded in it.
The latest OTA update from Verizon contains a bug fix that I desperately need, but my phone refuses to apply the update. I've given up working with Verizon and Motorola on this. Motorola level 2 support says they won't help because the phone is rooted, even though it wasn't at the time I spoke to them on the phone.
I've decided to go the route of flashing the ROM myself. I'm now rooted, bootloader is unlocked, safestrap is installed, and I've backed up the my working system with it. I've also installed rootkeeper so I can temporarily unroot before flashing.
Also after doing this will I need to reinstall and reconfigure all my apps? If so is there an easy way to back that all up so all I need to do is restore the backup?
Here you go!
chuckh1958 said:
Anyone know where I can get the latest stock ROM for a RAZR HD XT926 from a trusted source? I'm a bit nervous about downloading just any old file that claims to be a stock ROM. Who knows what could be embedded in it.
The latest OTA update from Verizon contains a bug fix that I desperately need, but my phone refuses to apply the update. I've given up working with Verizon and Motorola on this. Motorola level 2 support says they won't help because the phone is rooted, even though it wasn't at the time I spoke to them on the phone.
I've decided to go the route of flashing the ROM myself. I'm now rooted, bootloader is unlocked, safestrap is installed, and I've backed up the my working system with it. I've also installed rootkeeper so I can temporarily unroot before flashing.
Also after doing this will I need to reinstall and reconfigure all my apps? If so is there an easy way to back that all up so all I need to do is restore the backup?
Click to expand...
Click to collapse
Go to sbf dot droid-developers dot org That's where you'll find them!
Thanks. Are you pretty confident that they are clean?
Clean
chuckh1958 said:
Thanks. Are you pretty confident that they are clean?
Click to expand...
Click to collapse
Yes. I'm very confident they are. I've always used these to restore mine to stock when needed.
Awesome! Thanks. Now I just need to figure out how to flash the one I want. This is my first time. I'm guessing I just put the zip file on my sdcard and tell SafeStrap to recover using it.
Will I need to reinstall all my apps? Is there a way to prevent that? Mostly I'm concerned about apps that I've spent a lot of time setting up custom configurations for.
Back to Stock
chuckh1958 said:
Awesome! Thanks. Now I just need to figure out how to flash the one I want. This is my first time. I'm guessing I just put the zip file on my sdcard and tell SafeStrap to recover using it.
Will I need to reinstall all my apps? Is there a way to prevent that? Mostly I'm concerned about apps that I've spent a lot of time setting up custom configurations for.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2176753
That post will walk you through how to flash back to stock.
So I can't use safestrap to flash the stock ROMs downloaded from sbf dor droid-developers dot org?
Safestrap
chuckh1958 said:
So I can't use safestrap to flash the stock ROMs downloaded from sbf dor droid-developers dot org?
Click to expand...
Click to collapse
No you cannot.
I've got RSD Lite installed now and it successfully detects the device is fastboot mode. Next step is to unzip the XML file I downloaded and plug it into RSD Lite. Right?
How much risk do you think there is that I end up bricking the phone? Keep in mind that OTA updates always fail because the hash on the build.prop file doesnt match what its expecting even though I've never changed the build.prop file.
Will I be able to use SafeStrap recovery if the phone gets bricked?
Like I said this is the first time I've tried this and I'm trying to cover all the bases before I do anything dangerous.
chuckh1958 said:
I've got RSD Lite installed now and it successfully detects the device is fastboot mode. Next step is to unzip the XML file I downloaded and plug it into RSD Lite. Right?
How much risk do you think there is that I end up bricking the phone? Keep in mind that OTA updates always fail because the hash on the build.prop file doesnt match what its expecting even though I've never changed the build.prop file.
Will I be able to use SafeStrap recovery if the phone gets bricked?
Like I said this is the first time I've tried this and I'm trying to cover all the bases before I do anything dangerous.
Click to expand...
Click to collapse
You don't unzip the .xml, you just flash it in RSD. When you use RSD, you will no longer have SafeStrap installed. SafeStrap is only an app, not a true recovery replacement, it works in conjunction with the stock recovery. You can't use a true recovery replacement since your bootloader is locked.
If you're not comfortable with RSD, try the House of Moto here:
http://www.droidrzr.com/index.php/topic/28162-house-of-moto-20/
RSD Lite failed to flash the phone. Error message was "failed flashing process - unknown fastboot command, (getvar).I do have the latest Android SDK installed (32 bit version) and it's in the my PATH. I can run fastboot from the command line and it does show a getvar command.
Prior to running RSD Lite I did temporarily unroot the phone with rootkeeper. Could that be the problem?
Ok I got to flash by ...
manually extracting the zip file
editing the xml file, and removing 2 lines that contained the text "getvar"
pointed RSDlite to the XML file instead of the zip file
From what I can see everything looks good on the phone. Now I just have to let it finish reinstalling all the apps.
I just wanted to post the steps here in case anyone else stumbles onto this thread and has the same problem.
I did lose root. Any way to get it back?
chuckh1958 said:
I did lose root. Any way to get it back?
Click to expand...
Click to collapse
We have root on the newest build now! In the general forum.
Hi, I recently decided to root my Nexus 5 using this guide on youtube: /watch?v=J1AKqrrf-5o
But after I'm all done with the rooting process, I noticed that my Nexus 5 has lost its LTE signal. Now it onlyy uses 3G. I managed to put it back on LTE by doing: *#*#4636#*#* and changed my prefered network, but by doing so, I lost my service with T-Mobile. Can't call or send messege with LTE on.
Please help me! I'm very new to Android and rooting but this first experience is not so good. Can you tell me what went wrong? Also, I rooted using the Linux guide.
Rooting alone won't mess up Wi-Fi. Don't use you tube use this http://forum.xda-developers.com/showthread.php?p=47025283
You might need this first. http://forum.xda-developers.com/showthread.php?p=47156064
jd1639 said:
Rooting alone won't mess up Wi-Fi. Don't use you tube use this http://forum.xda-developers.com/showthread.php?p=47025283
Click to expand...
Click to collapse
Many thanks, but I what can I do now? I don't want to sound like a jerk but what can the link do if I already rooted using the youtube guide (sorry again if that does sound jerkish).
danny2146 said:
Many thanks, but I what can I do now? I don't want to sound like a jerk but what can the link do if I already rooted using the youtube guide (sorry again if that does sound jerkish).
Click to expand...
Click to collapse
That's why I have you the second link
If all else fails flash the google stock images
Agreed. A root alone should not have caused an issue with your radio unless something went incorrectly. I would ( personally ) flash Google's stock nexus images and then possibly try again. Gaining root access can be done different ways, you may need to read into other alternatives...
I don't know. I use the ChainFIre CF Auto root on Ubuntu. I did unrooted the device earlier and was able to get LTE and service to work. Though after I use this samw method again, LTE stopped working properly, so I guess something is wrong with this method. Will try the "standard" method later though, if I can get a hold of a windows computer.
Let's back track a bit. What is the goal with root? Are you wanting to keep a custom recovery? What network are you using?
If you are going to just root stock and not go for a custom rom, I'd just flash a custom recovery via fastboot then boot to recovery and flash the SuperSU zip from Chainfire. At that point, you're rooted stock. If you decide to take an OTA update then you'll just need to make sure that you have the stock recovery installed. However, it's just as easy to flash the update when one of our devs packages it as a rom zip to flash via custom recovery, if not easier really.
Frankly, at this point my knowledge about android phone is still very hazy as this is acually my first ever phone, let along rooting, but I am eager to learn. So what's wrong if I didn't get a custom recovery? I just followed the instruction that they (chainfire autoroot) have for Linux and got this. Dunno if it was something in my phone nor the root. I am on T-Mobile BTW.
Yea, I'm baffled by that method affecting anything to do with service. It should be one of the least intrusive ways to root. However, weird things happen. So where are we now? Are you still rooted with the service issues? Which update / baseband are you on? You have the correct T-Mobile APNs? Have LTE(Recommended) selected under Preferred Network Mode in Settings / More... /Mobile Networks? Shouldn't really be necessary to mess with changing stuff in the Hidden Menu in this instance.
I'm on T-mobile Nexus 5 KitKat 4.4.2, with LTE in prefered mobile data. I rooted, the problem happened, unrooted this morning, the problem gone, rooted again with same method, the problem came back. I think I have the right APN since there are two with T-mobile options and I have tried both of them. As of now, I am still on root, but thinking of unroot it again...
danny2146 said:
I'm on T-mobile Nexus 5 KitKat 4.4.2, with LTE in prefered mobile data. I rooted, the problem happened, unrooted this morning, the problem gone, rooted again with same method, the problem came back. I think I have the right APN since there are two with T-mobile options and I have tried both of them. As of now, I am still on root, but thinking of unroot it again...
Click to expand...
Click to collapse
Still scratching my head over that, as the whole idea of Chainfire's auto root just literally is only supposed to install the SuperSU app and the binary and make no other changes. Obviously that isn't the case for you though. Are you unrooting via the settings in the SU app or via reflashing the stock img files?
es0tericcha0s said:
Still scratching my head over that, as the whole idea of Chainfire's auto root just literally is only supposed to install the SuperSU app and the binary and make no other changes. Obviously that isn't the case for you though. Are you unrooting via the settings in the SU app or via reflashing the stock img files?
Click to expand...
Click to collapse
I used the stock flashing method. I only unrooted it though, not lock the boot loader.
danny2146 said:
I used the stock flashing method. I only unrooted it though, not lock the boot loader.
Click to expand...
Click to collapse
Ok. So at this point, I would have the SuperSU zip (contains the SuperSU app and su binary) http://download.chainfire.eu/381/SuperSU/UPDATE-SuperSU-v1.91.zip on your phone, then fastboot a custom recovery like TWRP http://techerrata.com/browse/twrp2/hammerhead (fastboot flash recovery nameofrecovery.img), boot into recovery, and flash the zip. No need to wipe anything. Should just be able to flash and go. Then open SuperSU and make sure the binary is updated.
I'm sorry but how does one flash a custom recovery? Do I need a PC alondside or I can just do it entirely on my phone?
danny2146 said:
I'm sorry but how does one flash a custom recovery? Do I need a PC alondside or I can just do it entirely on my phone?
Click to expand...
Click to collapse
I included the command in the parenthesis in the last post.
In bootloader mode on the phone, of course, flash from PC, with the file in your fastboot folder:
fastboot flash recovery nameofrecovery.img (note - you can change the name of the file you download to whatever, as long as you leave the extension .img alone. ex: twrp.img)
If you are rooted already or still, you can flash from the phone either via the GooManager app https://play.google.com/store/apps/details?id=com.s0up.goomanager like this:
Install the app and open it. Tap menu then hit Install OpenRecoveryScript. Tap Yes. Verify that the filename displays your device's code name and hit Yes. The file will download and your device will install the recovery automatically.
or
(Rooted only) You can also use the app Flashify to flash the .img file directly from the phone. https://play.google.com/store/apps/details?id=com.cgollner.flashify
So yea, to solve your issue, I think it would be best to just start clean/stock, then go with the custom recovery flashed from PC + SuperSU zip method. If you can fastboot the other files to return to stock, this is no different and very quick. Should not take more than 5-10 seconds to flash the recovery. The whole operation, starting from scratch should take make 3-5 minutes to flash recovery, boot to it, flash the SuperSU zip then reboot, assuming you have fastboot set up properly and the 2 files you need downloaded already.
es0tericcha0s said:
I included the command in the parenthesis in the last post.
In bootloader mode on the phone, of course, flash from PC, with the file in your fastboot folder:
fastboot flash recovery nameofrecovery.img (note - you can change the name of the file you download to whatever, as long as you leave the extension .img alone. ex: twrp.img)
If you are rooted already or still, you can flash from the phone either via the GooManager app https://play.google.com/store/apps/details?id=com.s0up.goomanager like this:
Install the app and open it. Tap menu then hit Install OpenRecoveryScript. Tap Yes. Verify that the filename displays your device's code name and hit Yes. The file will download and your device will install the recovery automatically.
or
(Rooted only) You can also use the app Flashify to flash the .img file directly from the phone. https://play.google.com/store/apps/details?id=com.cgollner.flashify
So yea, to solve your issue, I think it would be best to just start clean/stock, then go with the custom recovery flashed from PC + SuperSU zip method. If you can fastboot the other files to return to stock, this is no different and very quick. Should not take more than 5-10 seconds to flash the recovery. The whole operation, starting from scratch should take make 3-5 minutes to flash recovery, boot to it, flash the SuperSU zip then reboot, assuming you have fastboot set up properly and the 2 files you need downloaded already.
Click to expand...
Click to collapse
I don't know , but this is very interesting. I now suspect that the problem is from T-Mobile's end, not mine, nor the root. I just dug into my mom,dad's phone and what did I find? 3 goddamn G! Not LTE. But when I tried to force the thing to get LTE, it disconnected from the service. However, when I moved to another location this evening, both the LTE and service came back. I think something odd is happening either in my neighborhood or T-Mobile service. Anyways, seems like nothing of major, might have to have a talk to T-Mobile about this.
But last question, with my CF root now, how can I know if I already have a custom recovery yet? And which one? You know for if I want to flash a ROM in the future. And thank you for your help!
danny2146 said:
I don't know , but this is very interesting. I now suspect that the problem is from T-Mobile's end, not mine, nor the root. I just dug into my mom,dad's phone and what did I find? 3 goddamn G! Not LTE. But when I tried to force the thing to get LTE, it disconnected from the service. However, when I moved to another location this evening, both the LTE and service came back. I think something odd is happening either in my neighborhood or T-Mobile service. Anyways, seems like nothing of major, might have to have a talk to T-Mobile about this.
But last question, with my CF root now, how can I know if I already have a custom recovery yet? And which one? You know for if I want to flash a ROM in the future. And thank you for your help!
Click to expand...
Click to collapse
Just boot into recovery and see what you have.
If you used CF-Root, then it would not have installed a custom recovery. This is something that you would have done on your own and not likely to have forgotten. If you root access is working properly, I'd suggest installing TWRP from the GooManager app as it's pretty easy and no PC required.
http://teamw.in/project/twrp2/205
Then make a nandroid back up of your phone and make sure to back up the EFS folder too and save them to a safe place. You can back that up in TWRP or from the method described here:
http://forum.xda-developers.com/showthread.php?t=2514095
Let's back up here. Why do you think you need root if you have no idea what you are doing? Are you just rooting because you can or do you have a real purpose?
Sent from my Nexus 5