Related
So i read thru a lot of the root threads & none of them made anh sense to me.I downloaded ADB,moto drivers, sdk,jdk,etc.But still none of it made any sense. So i tried the 1 click root & soft bricked my xoom. It gets stuck at the Motorola screen. I tried getting into the options & wiping user data,factory reset.But it would still get stuck at the dual core screen. So i tried a suggestion of using 1 click root to undo the root. But it said the xoom would say "done" twice on the screen but it only said "done" once. So then i relocked it hoping it would reboot & work but it didn't. I see 1 guy was able to fix his using a rooting guide.I hope someone here can help me out.
Sent from my DROIDX using XDA App
Arun01 said:
So i read thru a lot of the root threads & none of them made anh sense to me.I downloaded ADB,moto drivers, sdk,jdk,etc.But still none of it made any sense. So i tried the 1 click root & soft bricked my xoom. It gets stuck at the Motorola screen. I tried getting into the options & wiping user data,factory reset.But it would still get stuck at the dual core screen. So i tried a suggestion of using 1 click root to undo the root. But it said the xoom would say "done" twice on the screen but it only said "done" once. So then i relocked it hoping it would reboot & work but it didn't. I see 1 guy was able to fix his using a rooting guide.I hope someone here can help me out.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Motorola published the factory files for Xoom awhile back so if you still have fastboot, you can recover from it.
http://developer.motorola.com/produ...utm_source=supportforums&utm_term=unlockboard
I relocked it using the 1 click root and all it says now is "Failed to boot LNX 0x0004" "Starting RSD mode 2".I'm now trying to use the 1 click root to try to get it back to where it was..I just don't understand all of the rooting methods even after downloading adb,sdk,,etc..It may as well be written in Chinese.I'm sure if i saw someone actually do it i could catch on to it but right now rooting is confusing..hence i went with the 1 click.I had no problem 1 click rooting my droid x with a 1 click root.
Stop using one click crap. If you don't know what you're then you should not be messing with your device.
Sent from my DROIDX using XDA App
I can. Just won't.
Arun01 said:
I relocked it using the 1 click root and all it says now is "Failed to boot LNX 0x0004" "Starting RSD mode 2".I'm now trying to use the 1 click root to try to get it back to where it was..I just don't understand all of the rooting methods even after downloading adb,sdk,,etc..It may as well be written in Chinese.I'm sure if i saw someone actually do it i could catch on to it but right now rooting is confusing..hence i went with the 1 click.I had no problem 1 click rooting my droid x with a 1 click root.
Click to expand...
Click to collapse
Type oem unlock again and then flash the stock images...youll be good to go...also there are really good stickies in here that help..pleasedont forget to search before starting a new thread.
albundy2010 said:
I can. Just won't.
Click to expand...
Click to collapse
And this is rude and uncalled for
The OP stated he read quides etc and none of it made sense to him etc. So instead of asking for help a explanation he tries a one click method. Which is stupid. He than softbricks the device and asked for help here.
Then he is told that moto released the factory images and use fastboot if he still has it to recover the device. He then decides to ignore that entirely and go back and try to unroot/restore with the one click BS again. Then he tries to use it again to go back to where he was. Just flat out stupid. He did something when he had no idea wtf he was doing. Was told what to do. Did not do it. He even said it is like Chinese to him.
So I told him to stop messing with one click crap. Which is correct. I told him to stop messing with the ****ing thing. Which is also correct. He needs to learn/understand wtf he is doing. Instead of basically button mashing/trying crap and hoping it will basically fix itself.
On top of that this posted in the wrong section. Uncalled for my ass. He is the one that was rude when told to not mess with the one click or the device. Now this part is rude. **** his stupid ass.
csseale said:
Type oem unlock again and then flash the stock images...youll be good to go...also there are really good stickies in here that help..pleasedont forget to search before starting a new thread.
Click to expand...
Click to collapse
How do i get to that ..and where do i type it at ..i looked in device manager & does recognize the xoom..it says "Motorola USB Device:Motorola Flash Interface"..In properties under "Driver" it has options for driver details..update driver..disable & uninstall.Can i do anything with them?
I tried opening SDK manager but it never lets me type anything in the box as it's always trying to do some kind of update in another window so when i close the window it closes all of the windows.
Sent from my DROIDX using XDA App
Arun01 said:
So i read thru a lot of the root threads & none of them made anh sense to me.I downloaded ADB,moto drivers, sdk,jdk,etc.But still none of it made any sense. So i tried the 1 click root & soft bricked my xoom. It gets stuck at the Motorola screen. I tried getting into the options & wiping user data,factory reset.But it would still get stuck at the dual core screen. So i tried a suggestion of using 1 click root to undo the root. But it said the xoom would say "done" twice on the screen but it only said "done" once. So then i relocked it hoping it would reboot & work but it didn't. I see 1 guy was able to fix his using a rooting guide.I hope someone here can help me out.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
If they didnt make sense to you in the first place you probably shoud not be attempting to root... U went straight to an old method that even the developer has marked in hs thread can full brick you and should not be used. The xoom costs like 600 bucks... Why wouldnt you do extensive research on how to root? If you did not understand the terms why didn't you research the methods and learn it?
I hope you can flash the factory imagines back through fastboot and adb, but i just do not understand why people attempt this stuff when they have no idea what the terms even mean...
You need to have sdk, hook up to usb on your computer, and follow one of the unlock guides posted on this site... A real one using adb... Then you need to follow a root one...
Sorry that is not more helpful, but half of this experience is that you need to learn what you are doing and the instructions are out there. If they do not make sense at this point im afraid you are stuck. Now the way your device is you have to figure it out...
Arun01 said:
I relocked it using the 1 click root and all it says now is "Failed to boot LNX 0x0004" "Starting RSD mode 2".I'm now trying to use the 1 click root to try to get it back to where it was..I just don't understand all of the rooting methods even after downloading adb,sdk,,etc..It may as well be written in Chinese.I'm sure if i saw someone actually do it i could catch on to it but right now rooting is confusing..hence i went with the 1 click.I had no problem 1 click rooting my droid x with a 1 click root.
Click to expand...
Click to collapse
Please check out this thread.It is called Root heaven for a reason. Just about every viable rooting guide, all the files and explanations you will need are here.
http://forum.xda-developers.com/showthread.php?t=1209341
I urge you to just calm down, read about what is the sdk, what is adb, how to recover from a soft brick and so on. The xda xoom forum is all about learning and teaching. We were all noobies once. The Xoom is a very complex device with many models and vesions and one clicks just don't cut it. There are rooting methods that are relatively simple but you really need to be prepared before you get started.
Good luck and don't despair. You'll get there.
Thanks for the help guys.I'm reading through all of the threads and i see a typo in a post that in the command window would've never let me find the sdk tools on my c drive. But after i retyped it i did it & a bunch of writing came up. Trying to figure out now how to flash the stock images to the xoom.
Sent from my DROIDX using XDA App
Arun01 said:
Thanks for the help guys.I'm reading through all of the threads and i see a typo in a post that in the command window would've never let me find the sdk tools on my c drive. But after i retyped it i did it & a bunch of writing came up. Trying to figure out now how to flash the stock images to the xoom.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
at first, make sure you install android sdk correctly. then go to android sdk-folder in your computer, u will find a folder named platform-tool. Press shift+ right click on it, then choose open command window here. After that, type in "adb devices" or "fastboot devives" to check if your xoom is connected. If yes,you good to go. If no, check your android sdk installed process
After i type in abd devices it says list of devices attached but shows nothing..i did copy the sdk tools folder to the c drive like i was told.
@OP
If you can't do it yourself, getting somebody to help you (in person) is always an option. If you live in a major city, advertise on Craigslist or some equivalent. Offer $50 for debricking + some tutorial.
In order for the device to show up in adb the device needs to actually booted into the os and have USB debugging enabled. Which you can't do.
What you're supposed to do is use fastboot.
Boot the device into fastboot mode.
Use fastboot devices to see if the computer see's it/everything is set up etc.
If bootloader is locked unlock it with fastboot OEM unlock.
Then flash the official images for your exact device. Fastboot flash boot boot.img and so on.
The last command on restoring to stock guides is optional. Fastboot OEM lock. I would not do it. No reason to relock it. If do learn decide to root later you would have to unlock again and loose all data.
albundy2010 said:
In order for the device to show up in adb the device needs to actually booted into the os and have USB debugging enabled. Which you can't do.
What you're supposed to do is use fastboot.
Boot the device into fastboot mode.
Use fastboot devices to see if the computer see's it/everything is set up etc.
If bootloader is locked unlock it with fastboot OEM unlock.
Then flash the official images for your exact device. Fastboot flash boot boot.img and so on.
The last command on restoring to stock guides is optional. Fastboot OEM lock. I would not do it. No reason to relock it. If do learn decide to root later you would have to unlock again and loose all data.
Click to expand...
Click to collapse
That's good advice...no reason to re-lock. But get back to square one so that you're functional and then when you're ready to try again, do it the right way.
Again, good luck!
albundy2010 said:
In order for the device to show up in adb the device needs to actually booted into the os and have USB debugging enabled. Which you can't do.
What you're supposed to do is use fastboot.
Boot the device into fastboot mode.
Use fastboot devices to see if the computer see's it/everything is set up etc.
If bootloader is locked unlock it with fastboot OEM unlock.
Then flash the official images for your exact device. Fastboot flash boot boot.img and so on.
The last command on restoring to stock guides is optional. Fastboot OEM lock. I would not do it. No reason to relock it. If do learn decide to root later you would have to unlock again and loose all data.
Click to expand...
Click to collapse
Thanks a lot.I was able to unlock it then it rebooted & stopped at the Motorola screen then i started the 1st command: fastboot flash boot boot.img & it says waiting on device..but nothing happens so far.Should i move on to the next step or retry?
Hi
Tried to root my new Nexus 7 on 4.2.1
It failed and somehow I managed to delete the OS??????
I can get it into bootlader and can find TWRP.
When I try to reboot it states NO OS installed.
Any suggestions? I have looked on the forums but cant find anything as I prob dont know what I am looking for.
Thank you in anticipation
Regards
capt208 said:
Hi
Tried to root my new Nexus 7 on 4.2.1
It failed and somehow I managed to delete the OS??????
I can get it into bootlader and can find TWRP.
When I try to reboot it states NO OS installed.
Any suggestions? I have looked on the forums but cant find anything as I prob dont know what I am looking for.
Thank you in anticipation
Regards
Click to expand...
Click to collapse
As long as bootloader is viable, you should be fine.
Download the FULL system image from Google:
https://developers.google.com/android/nexus/images#nakasi
Make sure you chose nakasi for WiFi or nakasig for 3G tablet, depending on the one you own.
Download file, extract tgz and extract zip inside of that.
Make sure you have adb/fastboot installed and in your path and that your tablet is connected and recognized. Boot into bootloader mode (which needs to be unlocked). Then do a full flash (you can omit the -w option to prevent the flash from wiping sdcard).
This will restore your device OS back to stock.
Depending on what you did, which you didn't really explain, there is probably a quicker/easier option. But without more info, the only advice I can give you is what I did, which should work fine for all circumstances.
Sticky post above this one is the solution..
It seems like you from your post you used a tool kit and something went wrong or you missed a step. Follow one of the following guides.
I recommend the first one..
Manual adb/fastboot
http://forum.xda-developers.com/showthread.php?t=1907796
Took Kits Automated flashing/ rom install ..
This one is a Windows interface.
......... http://forum.xda-developers.com/showthread.php?t=1766475..........
CMD Interface.
...............http://forum.xda-developers.com/showthread.php?t=1809195..........
I recommend the Manual method But only after reading post in all the threads. This will help you get a better understanding of Android..
Good Luck... the post above mine is also correct if you already have a adb environmental set up
Thank you
Thank you all for your advise
The nexus is once again alive
Have a very happy holiday season
Regards
Thank you
Thank you all for your advise
The nexus is once again alive
Have a very happy holiday season
Regards
how can I access my nexus, when I am in TWRP? windows cant connect to it cause of no driver..
jonny_pasta said:
how can I access my nexus, when I am in TWRP? windows cant connect to it cause of no driver..
Click to expand...
Click to collapse
Get the driver?
______________________________
Sent from my cellular telephone. Battery problems? >>>> http://forum.xda-developers.com/showthread.php?t=2461864
kj2112 said:
Get the driver?
______________________________
Sent from my cellular telephone. Battery problems? >>>> http://forum.xda-developers.com/showthread.php?t=2461864
Click to expand...
Click to collapse
no, you have to get to bootloader, I figured that out, now I'm sutck on "archive does not contain boot.sig" etc..
Hi
I got the same issue....
I can access the fastboot mode and the recovery mode, but not the bootloader. I go back on fastboot mode if I try to load bootloader...
I want to reinstall but windows doesn't recognize my n7 :/ so I'm stuck at this point :/
So I had the latest version of Paranoid Android on my rooted nexus 10. The keyboard was messing up so i wanted to run a factory reset and go all the way back to stock 4.2.1. In the process I accidentally wiped both the Rom and stock from my nexus 10 leaving it with no OS and nothing but the boot-loader. If i try and go to recovery mode all i get is the android laying down with an exclamation mark in a red triangle in it's stomach or the word Google with and unlocked padlock underneath it.
Any advice/help would be amazing! Thanks!
Download the factory image from Google: https://dl.google.com/dl/android/aosp/mantaray-jop40c-factory-0d641789.tgz
If you don't have fastboot already you need that too: http://downloadandroidrom.com/file/tools/fastboot.zip
Unzip the factory image tgz I linked to with 7zip/winrar etc
Unzip the fastboot.zip contents into the folder you just extracted
open a command prompt in the folder you just unzipped (mantaray-jop40c)
Boot your device into the bootloader by holding down BOTH volume keys and the power button
Connect your Nexus 10 to your PC
At the command prompt type
fastboot flash bootloader bootloader-manta-mantalj12.img
fastboot reboot-bootloader [wait for the device to reboot back to the bootloader]
fastboot -w update image-mantaray-jop40c.zip
This will wipe, repartition and install 4.2 straight from Google back to your device.. You will be prompted to update by Google to install the 4.2.1 update shortly after you boot up.
If you didn't have Fastboot already and had to download the zip I linked to, it's highly suggested to download and install the Android SDK so you have it and more native tools at your disposal. You can do that after the fact though and optional but highly suggested if you plan on learning your device more.
Will this work even if my device WAS Android 4.2.1 JOP40D?
Jamocobi said:
Will this work even if my device WAS Android 4.2.1 JOP40D?
Click to expand...
Click to collapse
Yep.
styckx said:
Yep.
Click to expand...
Click to collapse
Awesome thanks, I'll give it a shot once the files downloaded!
You're welcome. You should be fine.. This will start you right back at square one w/ an unlocked bootloader. You won't have a custom recovery or anything like that but you'll be back at a good starting point if you ever want to go that route again.
If you want to lock your bootloader again. After the device boots into Android reboot back to the bootloader one more time and type
fastboot oem lock
styckx said:
You're welcome. You should be fine.. This will start you right back at square one w/ an unlocked bootloader. You won't have a custom recovery or anything like that but you'll be back at a good starting point if you ever want to go that route again.
If you want to lock your bootloader again. After the device boots into Android reboot back to the bootloader one more time and type
fastboot oem lock
Click to expand...
Click to collapse
Awesome. Thanks so much! Unfortunately the command prompt is just stuck on "sending 'bootloader' <1280KB>..."
It's been over 4 minutes now which doesn't seem right, any ideas?
Jamocobi said:
Awesome. Thanks so much! Unfortunately the command prompt is just stuck on "sending 'bootloader' <1280KB>..."
It's been over 4 minutes now which doesn't seem right, any ideas?
Click to expand...
Click to collapse
How did you unlock and root this device in the first place?
styckx said:
How did you unlock and root this device in the first place?
Click to expand...
Click to collapse
With the WugFresh Nexus Root Toolkit (Sorry, Can't post a link yet)
styckx said:
How did you unlock and root this device in the first place?
Click to expand...
Click to collapse
Okay so after messing around with restarting bootloader i redid the script in command prompt and it is now back to factory settings, thank you so much!
Jamocobi said:
Okay so after messing around with restarting bootloader i redid the script in command prompt and it is now back to factory settings, thank you so much!
Click to expand...
Click to collapse
Figures. I had a long post written up to help you out. ha ha.. Good on ya for figuring it out..
I'm aware of the toolkit and situations like this is why I hate them. Users press a few buttons and `magic happens'.. When that user gets in trouble they now have no idea how to reverse what they did because there is no "Undo the magic" button and they learned nothing from the initial unlocking process because some toolkit did it for them.. Nexus devices can be unlocked and flashed with Google provided tools. Now that you manually did it you probably have a better overall idea of the actual process that is taking place. The more you do it manually, the more it becomes second nature. It's not even all that complicated. It's just a different way of copying files and erasing data.
One thing.. You NEVER.. EVER.. EVER... EVER... want to do is type this
fastboot erase bootloader
^ That is the quickest and easiest way to permanently brick your device.. If anyone ever suggests you do that.. Don't...
styckx said:
Figures. I had a long post written up to help you out. ha ha.. Good on ya for figuring it out..
I'm aware of the toolkit and situations like this is why I hate them. Users press a few buttons and `magic happens'.. When that user gets in trouble they now have no idea how to reverse what they did because there is no "Undo the magic" button and they learned nothing from the initial unlocking process because some toolkit did it for them.. Nexus devices can be unlocked and flashed with Google provided tools. Now that you manually did it you probably have a better overall idea of the actual process that is taking place. The more you do it manually, the more it becomes second nature. It's not even all that complicated. It's just a different way of copying files and erasing data.
One thing.. You NEVER.. EVER.. EVER... EVER... want to do is type this
fastboot erase bootloader
^ That is the quickest and easiest way to permanently brick your device.. If anyone ever suggests you do that.. Don't...
Click to expand...
Click to collapse
Sorry about that, i was hoping you'd see it in time! You're definitely right about that, i was just worried i would totally mess it up if i did it myself but i can do that anyway with a toolkit so next time ill give it a shot without one.
Okay thanks, I'll take note of that one for sure! Really appreciate the help, thought i was doomed! haha!
You're welcome man.. It's no fault of your own for using the toolkit. To new users they're attractive and promise quick results.
Side note. It's extremely, insanely, stupidly hard to permanently screw up a Nexus device by flashing. There is always a way back from `the grave'.
Take care
I flashed the Eclipse ROM via safestrap and then restored the Eclipse ROM onto the stock ROM slot. For some stupid reason, instead of restoring the stock ROM slot before resetting the phone back to stock, I opted to use RSD Lite 6.1.4 and tried to flash the JB firmware (yes, I got into fastboot). When I tried to do this, the phone reboots past the Motorola M insignia, to the droid startup screen (with the flashing red light/circle), but does not get past the startup screen (yes, I gave it 30+ minutes to no avail). I also tried to reflash the JB firmware, but no matter what, I ended up stuck at the bootup screen.
For this reason, I tried to flash the ICS firmware instead (per instructions on XDA and other websites, I removed the lines in the XML file that had the word var, getvar, and oem). This did work! However, after RSD flashed the firmware, rather than restarting into the OS, the phone reboots into a black screen w/ the phrase "Fastboot Reason: Sticky bit factory_fastboot" at the very bottom. Anytime I try to restart the phone, it automatically boots into this screen. If I hold the volume up and down buttons, together w/ the power button, I am able to get back to the option to start normally.
When I tried to do the OTA JB update, the phone downloads the necessary files, but when the phone tries to reboot to install the OS update, it goes back into that black screen and does not install the update. Also, when I finally do get back into the OS, the phone then constantly reboots as if it were trying to install the OTA JB update.
Does anyone know what "Fastboot Reason: Sticky bit factory_fastboot" means? Also, if anyone knows how to "fix" this issue, I'd greatly appreciate it. If the fix requires command line work (like in this thread), I'd greatly appreciate if someone could walk me through it step-by-step, as I am not familiar w/ the command line process.
Thanks!
Edit 1: The next step I will try is to get root back on my phone, install Safestrap, and see whether I can flash a backup that I previously had.
Edit 2: In some threads for other Moto phones, there is some discussion regarding using ADB to fastboot/flash the stock ROM. Anyone know how this is different from using RSD? Also, can anyone walk me through HOW to ADB? I have zero knowledge in this regard.
Have you tried holding the buttons down to enter fast boot again and reflash? Worth a shot if you haven't. You could also attempt a factory reset from the boot menu. Maybe the corrupt file would correct itself.
You should definitely take the time to learn some ADB; at least a working understanding. It helps down the road.
Here's a good tutorial on ADB commands. http://mobile.tutsplus.com/tutorials/android/android-adb-quick-guide/
And to install ADB without Android SDK (app production software) http://mobilecon.info/install-adb-in-windows.html
Sent from my Nexus 7 using xda app-developers app
skippid said:
Have you tried holding the buttons down to enter fast boot again and reflash? Worth a shot if you haven't. You could also attempt a factory reset from the boot menu. Maybe the corrupt file would correct itself.
You should definitely take the time to learn some ADB; at least a working understanding. It helps down the road.
Here's a good tutorial on ADB commands. http://mobile.tutsplus.com/tutorials/android/android-adb-quick-guide/
And to install ADB without Android SDK (app production software) http://mobilecon.info/install-adb-in-windows.html
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes, I attempted to reflash on multiple occasions, both using the stock ICS and the stock JB roms. I must have reflashed close to 10x at this point. In any case, no matter how often I have reflahsed (including after doing a factory reset from within the OS as well as from within recovery), I still get the error. The good news is that I was successfully able to flash the JB ROM and have the phone OS actually start up, whereas, a few days ago, it would be stuck at the red circle/eye thing.
Furthermore, I attempted the command fastboot flash system [system.img], and I got the error:
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
error: cannot load '[system.img]': no error
I saved the system.img in both c:\android, as well as the internal SD card of the phone.
The other good news is that I am still able to use the phone if I get into the boot menu and ask the phone to boot normally. However, I am now unable to get root, and anytime I need to restart the phone, it gives me that error message.
I have also tried the command fastboot reboot bootloader but continue to get the same error message.
OK. Find a JB leak zip or current stock JB zip, access the screen where it asks for AP Fast boot and recovery, choose recovery, then volume up I believe when the phone shows the android with the red exclamation point.. Then choose update with zip. Search your SD card and install. It's worth a try in this manner in case you haven't already.
That's odd that your phone didn't respond well with RSD.
Sent from my XT907 using xda app-developers app
You need to use an updated fastboot binary for the new larger images in these devices.
http://db.tt/AveMC40y
skippid said:
OK. Find a JB leak zip or current stock JB zip, access the screen where it asks for AP Fast boot and recovery, choose recovery, then volume up I believe when the phone shows the android with the red exclamation point.. Then choose update with zip. Search your SD card and install. It's worth a try in this manner in case you haven't already.
That's odd that your phone didn't respond well with RSD.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Skippid, thanks for the suggestions. I tried your method as well. Went into recovery, selected to update from external SD (or something to that effect), selected the JB zip file, and let it flash that way. Unfortunately, I still received the same error message regarding the sticky bit factory_fastboot.
cellzealot said:
You need to use an updated fastboot binary for the new larger images in these devices.
http://db.tt/AveMC40y
Click to expand...
Click to collapse
cellzealot, thank you for the link. I've downloaded the file that you linked to. Could you be so kind as to now give me a step-by-step on how to re-attempt the flashing process?
Quick update - I was able to get root back, installed safestrap, and flashed the nandroid that I had made back when I first flashed Eclipse. However, I am still having the same issue:
Whenever I restart the phone, I get the sticky bit factory_fastboot error. If I use the command fastboot continue, the phone boots up as normal; however, it would be great to not have to do this each and every time I reboot the phone. Any help would be greatly appreciated. Thanks!
More updates (still not fixed):
After getting root, I reflashed my nandroid, factory reset (both within the OS and in recovery), and then tried flashing both the ICS and JB stock ROMs. I tried flashing both using mfastboot, as well RSD Lite. The files flash successfully; however, whenever I restart the phone, I continue to get the stick bit factory_fastboot error.
Also, when I get into recovery, I try to flash via "update from external SD". When I do so, recovery simply restarts without flashing the stock ROM.
Here's my last update as to this issue:
After trying all of the methods that I could think of (RSD Lite, flashing via fastboot and mfastboot, flashing from external), the problem did not correct itself.
I brought my phone into a Verizon store, where they told me that they had never seen that problem before. They agreed to replace my phone pursuant to the one-year warranty (I received my phone in December), which I received today. I've again rooted my phone, but have opted to not screw around w/ safestrap and custom ROMs this time around, as I find the stock JB experience to actually be quite good.
Found the soultion!!!!!!
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Thank you!
cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Thank you! This was the answer I needed after searching and searching trying all the different things for over 3 hours, this 2 second fix worked!
Namanati said:
Thank you! This was the answer I needed after searching and searching trying all the different things for over 3 hours, this 2 second fix worked!
Click to expand...
Click to collapse
#8 > http://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432
ATTACK said:
#8 > http://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432
Click to expand...
Click to collapse
Thanks, but that didn't come up when I googled AP Fastboot: flash failed, and since I didn't get it from rooting or unlocking my phone I didn't think to look for that.
cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Oh my god dude thank you so much. That fixed my bootloader issue that was plaguing me for weeks
Thanks again!!!
cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Thanks Man You really saved my razr.:good:
Edit : Sorry I asked stupid question!
Pierro29 said:
Edit : Sorry I asked stupid question!
Click to expand...
Click to collapse
there are no stupid questions if you question its because you dont know something and would like to fulfill the empty space where a reasonable answer could go. and s thanks for the solution to this error.
Okay, I have a "stupid"/newbie question. I flashed an image and I am getting the sticky boot thing. How to a get to a window to type the lines in?
Thanks!
cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Hey dude ! You save my life
Awesome trick
so my nexus 7 (original) was getting laggy so i tried reflashing the factory image. It wasn't working, so i downloaded the nexus root toolkit and tried flashing the stock ROM. It erases the boot, cache, system, etc, but it keeps getting stuck on the "sending bootloader" part. It just says:
sending 'bootloader' <2100 KB>...
what should i do? is it my computer? i really don't want a bricked nexus. please help...
Try flashing in boot loader
Type : flash fastboot boot boot.img
in C:\Andriod or path of the adb
no one help you - if you can not get access to fastboot - buy new nexus
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
leeamsi97 said:
so my nexus 7 (original) was getting laggy so i tried reflashing the factory image. It wasn't working, so i downloaded the nexus root toolkit and tried flashing the stock ROM. It erases the boot, cache, system, etc, but it keeps getting stuck on the "sending bootloader" part. It just says:
sending 'bootloader' <2100 KB>...
what should i do? is it my computer? i really don't want a bricked nexus. please help...
Click to expand...
Click to collapse
The solution here is at least in part not to use the toolkit so you can see for yourself what is going wrong. Download the appropriate factory image for your device and the Android platform tools, and then you can use fastboot to flash the relevant images over.
The bigger question is what state your device is in. Are you able to kick the machine into fastboot mode still?
sambistt said:
no one help you - if you can not get access to fastboot - buy new nexus
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
This is possibly one of the most useless posts I have yet seen here. We don't even know the status of the OP's device.
This is possibly one of the most useless posts I have yet seen here. We don't even know the status of the OP's device.
Click to expand...
Click to collapse
my post help him, your post just waste of time
- if him can`t access device via fastboot - how can it resolve command from it?
don`t bully this user - you cann`t help him - its not soft bricked !!!
sambistt said:
my post help him, your post just waste of time
- if him can`t access device via fastboot - how can it resolve command from it?
don`t bully this user - you cann`t help him - its not soft bricked !!!
Click to expand...
Click to collapse
Him no say him no can use fastboot. You assume too much and obviously have no clue what you're talking about.
Sent from my Nexus 7 using xda app-developers app
sambistt said:
my post help him, your post just waste of time
- if him can`t access device via fastboot - how can it resolve command from it?
don`t bully this user - you cann`t help him - its not soft bricked !!!
Click to expand...
Click to collapse
I'm not "bullying" anyone, I'm pointing out that your post is based off of nothing but conjecture right now. If OP killed even fastboot then yes, his options are limited, but your post is inviting an even larger waste of time based on inadequate information-- which is exactly how these problems occur.
Solved
Thanks everyone. I got it to work. I should have mentioned that i did use flashboot initially but used the toolkit when it didn't work. In the end, I finally got fastboot to flash the image. Thanks again for replying.