Related
I'm sure theres a few of you out there who've bricked their Xoom in the same way I did:
Locking the boot loader after having custom rom and kernal running on it or something similar and come across an error upon boot that says
Failed image LNX 0x0002
RSD mode 2 initiated
or something to that respect
Then tried to do fastboot oem unlock, only to have the Xoom not be recognised.
The solution for me was to make a Motorola Factory cable as per guide here
For some reason, the Xoom would be instantly recognised by my computer and all fastboot commands would work, as well as RSD Lite (Did not do me any good as there is no Xoom Wifi SBF released)
That should fix the booting problem
If it still does not, follow one of the other guides on how to flash using fastboot, another rom now that you have fastboot working again!
Cheers!
mowassasin said:
I'm sure theres a few of you out there who've bricked their Xoom in the same way I did:
Locking the boot loader after having custom rom and kernal running on it or something similar and come across an error upon boot that says
Failed image LNX 0x0002
RSD mode 2 initiated
or something to that respect
Then tried to do fastboot oem unlock, only to have the Xoom not be recognised.
The solution for me was to make a Motorola Factory cable as per guide here
For some reason, the Xoom would be instantly recognised by my computer and all fastboot commands would work, as well as RSD Lite (Did not do me any good as there is no Xoom Wifi SBF released)
That should fix the booting problem
If it still does not, follow one of the other guides on how to flash using fastboot, another rom now that you have fastboot working again!
Cheers!
Click to expand...
Click to collapse
So I went and bought the factory cable from the Black Hat guys, and luckily haven't had the need to use it. Any advice you'd like to give in case I need to at some point?
I guess the only advice I can give is: don't re-lock the boot loader when you have a custom rom loaded
You don't need the cable. I have recovered 4 times myself and walked many others through on irc. We all use the stock cable that came with the device.
Sent from my PG86100 using Tapatalk
bwcorvus said:
You don't need the cable. I have recovered 4 times myself and walked many others through on irc. We all use the stock cable that came with the device.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
It wouldn't recognise any fastboot commands nor the RSD Lite program for me.
But if it does, then thats good.
Merely a heads up for those who were in the same situation I was
bwcorvus said:
You don't need the cable. I have recovered 4 times myself and walked many others through on irc. We all use the stock cable that came with the device.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
you won't care to share how you did it? You have no idea how frustrating it is to see someone say they know how to fix something and leave it it at that.
yaturner said:
you won't care to share how you did it? You have no idea how frustrating it is to see someone say they know how to fix something and leave it it at that.
Click to expand...
Click to collapse
Over the course of a few hours I was able to fix this, so I am going to write this little walkthrough for you using a rom from bwcorvus's page (CLICK HERE) and then used the guide from dirtymindedx -(CLICK HERE)
The reason it took me this long (as well as doing other things) was because I used the wrong set up to unroot my tablet. I was using the Unofficial images that are on bwcorvus's link. Because I didn't read thoroughly enough in his breakdown, I made myself look like a fool...
What you want is NOT
UNOFFICIAL STOCK IMAGES
Click to expand...
Click to collapse
because you will not be able to lock the bootloader (IF you want it to be that way, which I did, and so it gave me a 0x000004 Error, and yes i see that you are having a 0x000002 but somewhere i read this could help that.) I just wanted to get rid of Clockwork Recovery Manager cause it was not working on my 3.2 rooted tablet, and thought that because i messed up teh whole image with playing around and upgrading and seeing how i could break the image without overclocking, i thought i should actually try and make it back to stock too. With this... I needed to do these steps...
1. Upgrade the Motorola drivers while the XOOM was plugged in, so then I would be able to use the Fastboot Correctly.
2. Download the correct roms for my tablet, (Wi-Fi is mine, just grab the one that fits your version and just follow along.)
3. Upgrade my ADB from google because for soem odd reason my fastboot did not like the xoom till i did that...
4. Used the STOCK CABLE. I can Confirm that the STOCK CABLE that allows you to recharge the phones, WILL WORK for this...
5. Once the ADB was set up, I restarted it, aka Hit the red X and then loaded it back up and then closed it again, just to make sure the services were updated somewhat...
6. Opened Command prompt and navigated to the folder that help the zipfile for the fastboot flashing guide (aka dirtymindedx's guide at the top), be using CD (Drive Letter):/location/of/the/folder/that/is/unzipped
7. I then checked over the information in the folder by using dir /a and then proceeded to read through the guide
7-1. A note here... I did the fastboot erase userdata instead, because I wanted to see if it would brick it again... (sorry, I was in a fowl mood with the world last night so I was waiting for it to get bricked so i had a reason to use it as an ice scraper on my car... (not like i would really do it... just wanted a reason for justification haha)
8. ???
9. Profit
This is only to get rid of a "already slightly bricked" device... which I had done after relocking the Rom that was not official to Motorola and now, after a few updates, i now have Android 4.0.3 for the Xoom that was OTA'ed, looking to see how easy it will be to root to reload my rpg game saves that i got caught up in (hence my disappearance from the forums haha...) but I hopefully helped you out in a direction to heads towards... and as long as you don't lock the boot-loader (which someone posted about it before i did...) you should be fine with any changes to the rom after the updates... Also, you can skip steps on this too... you can just flash the image and not the recovery menu and so forth, allowing you to keep other settings that are not part associated to the rom image.
Also sorry for the insanity in my words... I have been up for a good 36 hours with a half hour nap somewhere in there...
Hey Everyone,
Im new to android, and having a small issue, I am attempting to root my wifi xoom, I get up to the part where its time to select android recovery so that I can select the root zip, however when I use the volume down key to scroll the options the only 3 available are NVflash, RSD and Fastboot, theres no android recovery option I have searched the forums and googled it, but I seem to be the only one with this issue, my xoom is running 3.1 and bought in Aus, dont know if this makes a difference? any help would be greatly appreciated, I have got an OTG cable and would like to mount my external HDD so I need to get it rooted. Should probably mention I have unlocked it too.
Cheers
ha i just posted a thread with exactly the same issue. Hopefully one of us will get an answer!
djleez82 said:
ha i just posted a thread with exactly the same issue. Hopefully one of us will get an answer!
Click to expand...
Click to collapse
Your post was already answered in the General section. No need to post twice.
The answer did not fix my problem however. Still stuck at the same place as before just like terreboo. Possibly theres an issue with this type of xoom? I bought mine in australia as well. According to my about tablet info it says this:
Firmware Configuration Version: GAS_ASIA_UCAHUBLWFRTIRD_P006 so im assuming this is an asian tab? Just wondering terreboo what does yours say under firmware configuration?
yeah sorry didnt mean to post it in the general section, I alerted it to the mods to delete they just havent got around to it yet, yeah mate I have the same version as you, although I doubt this is the reason, we cant be the only two in Aus trying to root them? I think the problem probably lies else where, it has been suggested I'm getting the timing wrong, so I'll try again and post back my progress or lack of.
---------- Post added at 10:01 PM ---------- Previous post was at 09:45 PM ----------
I have tried it 10+ times now, I'm confident its not the timing of pressing the down key on reboot having varied the length of time everytime I tried, possibly its because of the firmware version? Im at a loss, I have followed the instructions of the root guide to the letter and seem to be one of the only ones with this problem!
this is the guide im using
http://forum.xda-developers.com/showthread.php?t=1078019
Same problem here!
I have the same problem guys.. Any solution?? The developers some help??
Im using the same guide btw....
I've freaked out im trying this for 8 hours now and no results....
im having a similar problem that my factory reset is corrupt or something because it doesnt actually DO anything.
I did the long root method as opposed to the supposedly easier method and thank heavens I got through it unharmed. I was ****ting my pants the whole way through. I wish I were more savvy with this so I can offer help. If I were u guys I would PM the devs from TIAMAT. They are probably the most knowledgeable ppl here to ask.
solution
OK guys i have a solution a guy from #xoom channel told me to write in windows command line
abd recovery reboot
And it worked!
I'm currently posting this from my costum rommed xoom
DrGreem said:
OK guys i have a solution a guy from #xoom channel told me to write in windows command line
abd recovery reboot
And it worked!
I'm currently posting this from my costum rommed xoom
Click to expand...
Click to collapse
Would that be adb recovery reboot? Can you give more information?
assuming you have adb setup on your computer already. Plug your xoom into your comp and make sure its in debug mode. Settings-applications-development. Open a command prompt and type in "adb reboot recovery" without quotes. Your device will then reboot into recovery mode.
I will say I'm having the same issue. I flash the new recovery and I don't see it in the menu. I'm running a US wifi xoom.
okantomi said:
Would that be adb recovery reboot? Can you give more information?
Click to expand...
Click to collapse
Yes that's right. I followed the guide and i waited 3 seconds but i never had the option 'android recovery so i turned on the device and this guy told me to run this command from cmd.
So after that xoom rebooted into clockwork recovery state and i flashed thecostum rom.
According to the guide that were using, if you allow the xoom to boot fully into honeycomb it reinstalls the stock recovery, and you need to redo the process all over. Also, you need to be in honeycomb to use the ADB command, if your in fastboot it won't detect the xoom. This did not work for me. Anyone else try it?
no luck for me here either. I can flash recovery successfully (according to the prompt) no problems there. I just have the exact same trouble booting into it as above.
Vol Down key combo doesn't work and if you leave the OS to boot straight after install, CWM is replaced by stock recovery. No fun at all.
Any further news or suggestions on this?
autodc5 said:
im having a similar problem that my factory reset is corrupt or something because it doesnt actually DO anything.
Click to expand...
Click to collapse
Same as my Xoom, opened a thread just for it, but no one can help
much easier... download rom manager and click boot to recovery haha ...
If not rooted,
adb reboot recovery via a cmdline window works a treat _
fkofilee said:
much easier... download rom manager and click boot to recovery haha ...
If not rooted,
adb reboot recovery via a cmdline window works a treat _
Click to expand...
Click to collapse
Just make sure that Rom Manager doesn't trick you into flashing a non-compatible updated recovery version.
In my experience it doesn't play well with the Xoom.
If all you want is a non manual way to boot into recovery from the OS, download Quick Boot (if rooted) or if you're already on the Tiamat Moray Rom, it's something you can choose when you press the power button on the back.
the problem is that for me and others with this issue, you can't use adb to boot recovery. If you install recovery from fastboot then boot into the regular OS without booting to recovery and rooting, the OS replaces CWM with the stock recovery. This means if you use adb or another app to reboot into recovery, you just get stock recovery which is totally useless. I can't load recovery or root using anay of the universal methods I have come accross. We need a way to boot into recovery without having it replaced with stock or another rooting method or something. Any other ideas?
aussiechris said:
the problem is that for me and others with this issue, you can't use adb to boot recovery. If you install recovery from fastboot then boot into the regular OS without booting to recovery and rooting, the OS replaces CWM with the stock recovery. This means if you use adb or another app to reboot into recovery, you just get stock recovery which is totally useless. I can't load recovery or root using anay of the universal methods I have come accross. We need a way to boot into recovery without having it replaced with stock or another rooting method or something. Any other ideas?
Click to expand...
Click to collapse
Look, this is how I had to flash CWM image file- through adb,/fastboot just like you. No matter what you say, it comes down to a question of timing.
I'm not sure about everyone else with the no recovery option, but timing just isnt the issue for me. Without a lie i've tried to enter recovery over 50 times at various points, 95% of those attempts were at the 3 second mark that is stated in the xda guide we've been using. I'm aware of one other person here whos tried it MUCH more than me with exactly the same result.
However theres one thing that we could narrow it down with. Thus far the people having this issue are using the asian firmware xoom's. Could everyone else having this problem on this thread say whether or not theyre using the asian firmware too? Maybe the asian firmware can't be rooted this way?
I have a 4G xoom that I am trying to return to stock. I have the stock images from Motorola and I am experienced in flashing so normally this would be a simple process for me, But I absolutely can not get past the 0x120000 error. I am using a Motorola cable (Not the one that comes with Xoom, But I don't have that one.) and I am using a port on the back. System.img refuses to flash and I can not understand why... Any help would be appreciated. I have also tried the adb method of flashing and that did not work either, It flashed and then re-booted with the custom rom.
I have searched but I can not find one, I would prefer a simple flash able .zip as I have CWM but ANY help would be appreciated.
I'm sorry if others have helped on this before but I can't find real clean instructions on how to do this. I bought a phone that has CM installed on it but can't active on Sprint because I can't do ##...#. I need to know how to get back to the stock rom that I don't have a back up of. Is there a easy way to reinstall the Sprint made rom? I did not root this phone myself but it came rooted so trying to figure this out with out a lot of back ground knowledge here. Thanks for your help.
adamsmiley said:
I'm sorry if others have helped on this before but I can't find real clean instructions on how to do this. I bought a phone that has CM installed on it but can't active on Sprint because I can't do ##...#. I need to know how to get back to the stock rom that I don't have a back up of. Is there a easy way to reinstall the Sprint made rom? I did not root this phone myself but it came rooted so trying to figure this out with out a lot of back ground knowledge here. Thanks for your help.
Click to expand...
Click to collapse
Use RSD Lite and an appropriate FXZ file from here.
http://forum.xda-developers.com/showthread.php?t=2095536
Do you have any where I can find help on this? I pull in my phone in AP Fastboot like I found on a different site pulled it in and went flashed but it failed with an error of "unknown fastboot command (getvar)"
Do you have any where I can find help on this? I pull in my phone in AP Fastboot like I found on a different site pulled it in and went flashed but it failed with an error of "unknown fastboot command (getvar)"
adamsmiley said:
Do you have any where I can find help on this? I pull in my phone in AP Fastboot like I found on a different site pulled it in and went flashed but it failed with an error of "unknown fastboot command (getvar)"
Click to expand...
Click to collapse
There's a couple of lines you need to remove from the XML file. Read the first post carefully.
Sounds like you put your phone in fastboot mode correctly, so you are almost there.
thanks so much that fixed it. I love the help from this site.
Hey guys!
To start, I want to say what an amazing place XDA is and how much information and knowledge you can get from here and how awesome the moderators are. I don't think I could ever find another amazing and/or helpful community such as those found here! Thanks to all who have helped me out with my Android issues!
Now to my issue and I apologize ahead of time if there is another thread (or related thread) found in the forum.
As the title states, I have a 2013 Motorola Moto G XT1031 Boost Mobile device. I had upgraded it to Lollipop 5.0.2 or 5.1 when it came out (I can't remember which one it was) and I had then decided to root it. I can say that I believe I was successful in rooting the device because I was able to install Supersu and use RootChecker to verify the install. Everything was going okay until i decided to research and eventually install a custom recovery and attempt to install a custom ROM. Well, let's just say that the recovery install was a bust...
In doing my research for a custom recovery, I found that TWRP had a custom recovery for my phone and apparently for my firmware via TWRP's app on the Play Store. So, I searched for my device in their in-app search for a custom recovery, downloaded it and installed it from the app. Now, my gut told me that this probably wouldn't work and that I should probably be installing a custom recovery via CLI. Nope. I didn't do this. Instead, like I said, I installed a custom recovery from the app itself. That screwed things up for me. I have no idea if it was the install, but my phone began to act incredibly strange. When in the TWRP recovery, my screen had this line that would continuously scroll from top to bottom. It wasn't a completely solid line, but it was transparent, almost like an empty thermometer glass stick was going down the screen. It was weird and not normal. I figured the phone's software was partially broken. It only did this in the TWRP recovery. Nowhere else did this happen. It was slightly annoying.
Later on I decided to install a custom ROM. Again, I did the necessary research to find out if there were any ROMs available for my phone (using XDA of course and others) and found that there were a few out there. So, I downloaded one (wish I could remember which one) and attempted to install it...keyword there. After attempting the install, my phone would not boot. Like at all. Dead. So back to the drawing board I went to try and reverse the damage. Using XDA (ironically) and a plethora of other sites, I tried to resurrect my phone and bring it back to life. After countless hours of trying and trying and trying and more and more research, I just gave up. The phone is dead. Great. $170 spent on a phone to break it a year later.
It's been roughly 4-5 months since I have attempted to redo the process and after another minor attempt, somehow I was able to remove the root completely, including the custom recovery and ROM. I don't know what the heck I did, but it worked....sort of. The phone is now stuck in a bootloop on the logo and sometimes the "bootloader has been unlocked" screen when try and factory reset the phone from the default recovery. When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set and to have this and that. I have this and that installed on my PC, but obviously cannot enable USB-debugging which is needed for ADB and fastboot to recognize my device.
So, my question for anyone who would like to help me out is this: what are my options? Is the phone recoverable? Is there any way I can get ADB/fastboot to see my device and finally install the stock firmware on the phone? I have the proper drivers installed and ADB/fastboot are on my PC. Any help would be amazing, even if you have to tell me to junk it.
blckdragn22 said:
When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set
Click to expand...
Click to collapse
This is incorrect, where did you read that? To reinstall the stock firmware using fastboot, you must be able to boot to the bootloader menu only.
I heard this from a few websites actually, although I could never find a situational fix for my phone. I am trying to restore back to Lollipop without a custom recovery, because within the past hour I found out TWRP was never fully removed when I tried booting into recovery from the AP Fastboot menu when doing to power+vol down option. The TWRP logo shows for about 10 seconds and then the phone tries booting normally, showing the unlocked bootloader warning.
So, yes I can boot into the bootloader menu all day long with no problems. It's just an selection I make doesn't get me anywhere. My question I guess now is: how do I go about reinstalling stock firmware via the bootloader menu. I have Minimal ADB and Fastboot installed on my PC. If I need the full ADB, I can download that. And of course I'd need the firmware, too.
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
This thread had the firmware I was looking for thank you. I believe I have the flashing stock firmware process down, I hope. I'l refer to the guide if I need help. Thank you so much!
_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
I am trying to follow the steps listed here http://forum.xda-developers.com/showthread.php?t=2542219&page=35 and for some reason I cannot run any of the commands pertaining to the sparsechunks. This is what I get:
Is there anything you could tell me about that?
Edit: I was able to figure what the issue was when trying to write the sparsechunks. I had to insert a "." after 'sparsechunk' because that is how the file is named in the folder. However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?
blckdragn22 said:
However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?
Click to expand...
Click to collapse
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).
_that said:
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).
Click to expand...
Click to collapse
I will try that. There was a ...sparsechunks.0 as well apart from sparsechunks.1, sparsechunks.2 and sparsechunks.3. Shall I include that, too?
And adding the screenshot was an amateur mistake. My bad.
@_that this worked like a charm. Phone is 100% working ans usable now. Incredibly helpful. Thank you so much!