Related
myxoom wont boot and it stuck at the boot logo! help pls!
Walk back into the store, walk up to customer service and say "It won't turn on"
That's about your only solution when someone loads a 3g kernel.
You might be able to try to Power Off, power on Press and hole Volume up and power when you see the moto logo.
i tried but failed! sad thing is i m staying malaysia n i ordered it via online!!!
pls! help me!
pls! i m gonna cry
Can you get into fastboot? You might want to try reflashing your boot and system partitions. I believe it was BeagleBoy that grabbed them off of a stock Xoom Wi-Fi. You're already unlocked I imagine. Should let you flash those right back in and start fresh.
This guy got out of a semi-brick by doing something similar.
http://forum.xda-developers.com/showthread.php?t=973355
Scourge1024 said:
Can you get into fastboot? You might want to try reflashing your boot and system partitions. I believe it was BeagleBoy that grabbed them off of a stock Xoom Wi-Fi. You're already unlocked I imagine. Should let you flash those right back in and start fresh.
Click to expand...
Click to collapse
If you can get into fastboot, you should be fine. Don't panic just yet.
Try reflashing the stock boot.img and system.img files through fastboot. I did it a few days ago http://forum.xda-developers.com/showpost.php?p=12832155&postcount=33
You can find boot.img and system.img for stock wifi xoom on the OP of that thread.
Failing that try the semi bricked solution.
I hope you solve your problem.
how do i enter fastboot?
sad is, now my machine stucks in boot screen (moto logo) .. n my com have no respond with it at all. any suggestion pls
omnia1994 said:
how do i enter fastboot?
sad is, now my machine stucks in boot screen (moto logo) .. n my com have no respond with it at all. any suggestion pls
Click to expand...
Click to collapse
Power off the device.
Then hold Volume Down and hold Power on at the same time.
it shows "Starting Fastboot protocol support" and stopped there. what this mean? =(
that means you should be able to get it running again.
follow the first message in this thread:
http://forum.xda-developers.com/showthread.php?t=1010568
probably from the stuck at 'dual core technology' bit...
but I think this is what you should follow:
adb reboot bootloader
fastboot flash boot boot.img
fastboot reboot
adb remount
adb push bcm4329.ko /system/lib/modules/bcm4329.ko
adb push tun.ko /system/lib/modules/tun.ko
adb push scsi_wait_scan.ko /system/lib/modules/scsi_wait_scan.ko
adb push cifs.ko /system/lib/modules/cifs.ko
adb push vold.fstab /system/etc/vold.fstab
adb reboot
you might also want to pick up the stock wifi images:
http://forum.xda-developers.com/showthread.php?t=1017398
and flash them using:
fastboot flash system system.img
fastboot flash recovery recovery.img
(you've already flashed boot.img above).
omnia1994 said:
it shows "Starting Fastboot protocol support" and stopped there. what this mean? =(
Click to expand...
Click to collapse
If you're lucky, your computer will connect and typing in "fastboot devices" will show an entry for your Xoom. You do not need to start with ADB if you're already in fastboot mode.
From there, flash the boot.img for the proper Xoom version you have. You may also want to flash the system.img as well.
From there, simply try to reboot using "fastboot reboot". Make sure your Xoom starts up. If it does, you're pretty much good to go. I'd root from there manually.
omnia1994 said:
it shows "Starting Fastboot protocol support" and stopped there. what this mean? =(
Click to expand...
Click to collapse
That means you are in fastboot.
You can now try to follow this http:// http://forum.xda-developers.com/showthread.php?t=1010568 skipping the unlock section. Or as scourge recommended, fastboot flash the stock .img files. You can find them here http://forum.xda-developers.com/showthread.php?t=1017398 and the instructions around post #26 in that thread.
but my com cant sense my device =(
n it stucks at boot screen with the words "Starting fastboot protocol support" but just stuck there, this works?
qubit76 said:
That means you are in fastboot.
You can now try to follow this http:// http://forum.xda-developers.com/showthread.php?t=1010568 skipping the unlock section. Or as scourge recommended, fastboot flash the stock .img files. You can find them here http://forum.xda-developers.com/showthread.php?t=1017398 and the instructions around post #26 in that thread.
Click to expand...
Click to collapse
That's not necessarily true. My PC can no longer detect my Xoom in any way whether or not it says "Starting Fastboot protocol support" or "Starting RSD mode 2". I can't get it to say anything else.
I used to be able to get into fastboot. That's how I bricked my Xoom... By trying to oem lock it with what I was hoping to be clean boot, system and recovery image files for the wifi.
Now, I can't even get back in to oem unlock or flash. RSD lite doesn't pick it up in RSD mode 2, but does pick up my old RAZR phone.
omnia1994 said:
but my com cant sense my device =(
n it stucks at boot screen with the words "Starting fastboot protocol support" but just stuck there, this works?
Click to expand...
Click to collapse
What sort of computer do you have? Can you copy and paste what you see when you type "fastboot devices"?
Copy and paste from your command prompt (or Linux terminal) and let's see what you've got.
ok. will report once tried. thx very much =)
Okay. If you can get into fastboot (check by "fastboot devices"), all you should need to do are these two commands if you're connected:
Code:
fastboot flash boot boot.img
fastboot flash boot system.img
fastboot reboot
That should get you close to stock first.
wth, i cant install the android SDK, it said it needs java to be installed. i ve installed that but still cant install the android sdk. =(
omnia1994 said:
wth, i cant install the android SDK, it said it needs java to be installed. i ve installed that but still cant install the android sdk. =(
Click to expand...
Click to collapse
Where error messages are you getting? Are you running 64bit?
Hiya,
After dealing with a half-bricked Xoom, I did some research on this problem and found a solution.
If in any case, you happen to get stuck on the "Motorola Dual-Core Technology"
Solution to this (For the MZ604, One-Click rooted):
MZ604 Stock .imgs Download: http://developer.motorola.com/products/software/
*Make sure you have fastboot in the same directory as your adb for easy access*
1. Plug in your USB cord
2. Turn off your Xoom (Vol-Up + Power)
3. Boot into fastboot (Vol-Down + Power)
4. On your computer, open up a command prompt, and type the following:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
-or-
Code:
fastboot flash boot <path to boot.img>
fastboot flash system <path to system.img>
fastboot flash recovery <path torecovery.img>
fastboot flash userdata <path userdata.img>
fastboot erase cache
fastboot oem lock
5. Reboot the Xoom
Code:
fastboot reboot
6. There you go, back to stock!
On the real though, if you can get to Fastboot (or even the Moto "Android Recovery" state), you're not THAT bricked you've got to relock and go back to out-of-box; just keep a known-good boot.img around somewhere.
You just saved my life!
Thanks for sharing OP.
I take it this method is the same for 3.1?
I hope this works. Although, I can't turn my xoom off. It also appears that my computer will not recognize my device when it is plugged in. In addition, I can't turn off my Xoom? It just reboots... so I can't enter fastboot mode.
I just posted this in a new thread.
Lcsglvr said:
I tried reverting back to stock using the "one click" root/unroot tool that was the first to come out for the Xoom.
Anyway, I tried the unroot process and everything was going fine, until something occurred. Now, it tries to boot up and says at the Moto Dual Core Technology screen, "Failed to boot LNX 0x0004 // Starting RSD mode 2".
Can someone help
Click to expand...
Click to collapse
Can anyone help!
Lcsglvr said:
I hope this works. Although, I can't turn my xoom off. It also appears that my computer will not recognize my device when it is plugged in. In addition, I can't turn off my Xoom? It just reboots... so I can't enter fastboot mode.
I just posted this in a new thread.
Can anyone help!
Click to expand...
Click to collapse
same here, anyone help ((
Lcsglvr said:
I hope this works. Although, I can't turn my xoom off. It also appears that my computer will not recognize my device when it is plugged in. In addition, I can't turn off my Xoom? It just reboots... so I can't enter fastboot mode.
I just posted this in a new thread.
Can anyone help!
Click to expand...
Click to collapse
You can still enter fastboot if you xoom won't shut off. Just hold the appropria oncete buttons as it reboot. Happened to me last night upgrading to 3.1. It. Wouldn't shut down at all. Once I got into fastboot my computer saw it and I was able to fix
Honestly, I almost went through all of this last night when my WIFI Xoom got stuck in a boot loop.
However, I noticed that when my recovery went to flash the new 3.1 file, I felt like it didn't take as long as it should have. The file was the right size and all and it even said that everything installed successfully, but it just kept boot looping regardless of trying over and over. So I went ahead and re-downloaded the 3.1 file and repeated the steps to flash it and everything worked.
So, before you spend a whole lot of time restoring your Xoom, simply re-download the files and try it one more time. It worked for me.
rebill said:
You can still enter fastboot if you xoom won't shut off. Just hold the appropria oncete buttons as it reboot. Happened to me last night upgrading to 3.1. It. Wouldn't shut down at all. Once I got into fastboot my computer saw it and I was able to fix
Click to expand...
Click to collapse
Thanks! Finally have some hope to recovering. I'll post steps I took later once I get this damn thing fixed.
hmmm... I'm in fastboot supposedly and tried to flash boot.img but it seems to be stuck at <waiting for device>
This happen to anyone else?
After search seems like a driver issue, but I have installed the drivers... I was previous rooted, so I know I have the drivers. Just to be sure, I ran the MotoHelper again. I don't understand. It's just seeing my device on the "Starting Fastboot protocol support."
help?
Lcsglvr said:
hmmm... I'm in fastboot supposedly and tried to flash boot.img but it seems to be stuck at <waiting for device>
This happen to anyone else?
After search seems like a driver issue, but I have installed the drivers... I was previous rooted, so I know I have the drivers. Just to be sure, I ran the MotoHelper again. I don't understand. It's just seeing my device on the "Starting Fastboot protocol support."
help?
Click to expand...
Click to collapse
Yes. How did I fix it? I returned the xoom and had a new one two days later.
If the screen says something like "Entering RSD 2" then you're boned. The xoom won't be recognized in either the current state or in fastboot state by the computer, so no amount of commands will help. Even having the stock images doesn't help with that. Even RSDLite can't see the xoom in that state.
There have been several reports of people just being honest to Motorola and them fixing the device under the warranty.
Hmm honesty. I'll give it a shot.
Sent from my ADR6300 using XDA App
Is the final OEM lock necessary? It's quite a pain as your userdata gets wiped if you unlock it...
I was stuck on bootloop, with unrecognised device, through adb was able to get back into clockwork recovery somehow at first boot, think twice down volume? Could be wrong.
I was able tto rreflash zip 3.1 over thet top again.
sry if this is different and unhelpful, bu imagine things are pretty desperate if you are considering returning the device
zerin said:
Yes. How did I fix it? I returned the xoom and had a new one two days later.
If the screen says something like "Entering RSD 2" then you're boned. The xoom won't be recognized in either the current state or in fastboot state by the computer, so no amount of commands will help. Even having the stock images doesn't help with that. Even RSDLite can't see the xoom in that state.
There have been several reports of people just being honest to Motorola and them fixing the device under the warranty.
Click to expand...
Click to collapse
You're not boned at all. I had that happen to me so I just got back into fastboot, downloaded the files in the OP put ADB, Fastboot and the adb extensions into the file I downloaded then ran the commands and got me XOOM back up and running fine.
jbartcaps said:
You're not boned at all. I had that happen to me so I just got back into fastboot, downloaded the files in the OP put ADB, Fastboot and the adb extensions into the file I downloaded then ran the commands and got me XOOM back up and running fine.
Click to expand...
Click to collapse
You were likely in RSD 3, which is recognized by the computer. RSD 2 means adb and fastboot cannot see the device at all, so no flashing images is possible.
There's several states that all look very similar. Because some success was had with one doesn't mean it works for all. Motorola recognizes and is telling users that, in this state, the device needs to be sent back to them.
Can someone help us wifi xoom. Im stuck on the motorola screen and have a lil experience. I can fast boot reboot/fastboot device and it work but cant get the files from the hwi69 to fastboot on to it. I think im entering the commands wrong. Any advice would be appreciated
TheRedDroid said:
Hiya,
After dealing with a half-bricked Xoom, I did some research on this problem and found a solution.
If in any case, you happen to get stuck on the "Motorola Dual-Core Technology"
Solution to this (For the MZ604, One-Click rooted):
MZ604 Stock .imgs Download: http://developer.motorola.com/products/software/
*Make sure you have fastboot in the same directory as your adb for easy access*
1. Plug in your USB cord
2. Turn off your Xoom (Vol-Up + Power)
3. Boot into fastboot (Vol-Down + Power)
4. On your computer, open up a command prompt, and type the following:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
-or-
Code:
fastboot flash boot <path to boot.img>
fastboot flash system <path to system.img>
fastboot flash recovery <path torecovery.img>
fastboot flash userdata <path userdata.img>
fastboot erase cache
fastboot oem lock
5. Reboot the Xoom
Code:
fastboot reboot
6. There you go, back to stock!
Click to expand...
Click to collapse
Very good info to get into fastboot protocol:
Much thanks for the info. Worked like a champ. On an updated 3.2.1 XOOM I did an unlock, re-locked the wrong way, soft bricked, unbricked back to locked state. Finally followed your steps applied stock files and XOOM is re-locked and stock rocking back at 3.01. I needed to do all this to make sure I could get it back to stock in case it goes back to BB in 2 weeks. I was lucky enough to find one at a BB just not sure if I'll keep it. I plan on trying out some roms plus I heard Motorola is planning on doing an ICS push to the XOOM. ICS is very nice. It runs great on my unlocked Verizon G-Nex.. Again Thanks..
This post not only saved my half-bricked non-rooted Xoom, but also let me flash it from the Singapore firmware (bought if from Amazon, don't ask lol) to the regular USA firmware so that I can properly root it!
Thank you so very much!!
I'm going to probably get a lot of hate for this because there are a ton of forums that might get me here. I did search for about 3 hours tonight and discovered some things but am still confused. I hope someone can help this be more simple. So a friend has a Nexus S that isn't working (I have a Nexus S by the by too). It's unlocked but no ClockWork on it. I can press volume up and power to get to fastboot mode. When I click on "reboot," the phone will just loop on the Google logo. If I click recovery, it starts to boot then shows the triangle with the exclamation mark. From there, I can press power and up or down on volume to get the blue screen which says reboot system now, apply update, wipe, wipe. You get it. I'm stuck...I can also turn off the phone, hold volume up/down and plug in the usb to get to "downloading..."
I want to get this phone working and back to stock. I have the SDK Manager (my phone isn't rooted so I use it to take screenshots) and pda net (which I still don't understand why or how to use with this) and two versions of Odin. It seems like Odin can get this working but I can't get it to work or find a clear guide on how to use it and which ones to use. This is a Tmob Nexus S, I think the i9020. Any help would be so greatly appreciated and I will give you all the credit. Oh, and i can pull up the device on ddms with the sdk manager and can explore the files but there is nothing. I can't find a way to drag a file on the phone to "apply update from /sdcard." Sorry again and thanks again!
callison.168 said:
I'm going to probably get a lot of hate for this because there are a ton of forums that might get me here. I did search for about 3 hours tonight and discovered some things but am still confused. I hope someone can help this be more simple. So a friend has a Nexus S that isn't working (I have a Nexus S by the by too). It's unlocked but no ClockWork on it. I can press volume up and power to get to fastboot mode. When I click on "reboot," the phone will just loop on the Google logo. If I click recovery, it starts to boot then shows the triangle with the exclamation mark. From there, I can press power and up or down on volume to get the blue screen which says reboot system now, apply update, wipe, wipe. You get it. I'm stuck...I can also turn off the phone, hold volume up/down and plug in the usb to get to "downloading..."
I want to get this phone working and back to stock. I have the SDK Manager (my phone isn't rooted so I use it to take screenshots) and pda net (which I still don't understand why or how to use with this) and two versions of Odin. It seems like Odin can get this working but I can't get it to work or find a clear guide on how to use it and which ones to use. This is a Tmob Nexus S, I think the i9020. Any help would be so greatly appreciated and I will give you all the credit. Oh, and i can pull up the device on ddms with the sdk manager and can explore the files but there is nothing. I can't find a way to drag a file on the phone to "apply update from /sdcard." Sorry again and thanks again!
Click to expand...
Click to collapse
It seems your boot.img file either corrupted or missing.
Find a working copy of file, flash it via ADB interface or fastboot. Flash recovery file CWM. If that doesnt work, Try flashing CM7 Rom or someother ROM.
Did you check http://forum.xda-developers.com/showthread.php?t=895545 ?
Odin should be your last resort, if nothing really works for you.
If you want to return to stock, simply flash the NAND backup found here: http://forum.xda-developers.com/showthread.php?t=884093 .
Disclaimer : I take no responsibility of what so ever happens to your phone, however you should be good if you follow proper steps.
Thanks so much for the quick reply. I think I've made some headway...I can "see" the device with cmd by typing adb devices. After that though, I don't understand how to get the stock nexus s rom on the phone. How do I move that file to my phone (what's the line of code I type)? I've tried "adb install <c:\grh78> but it says the syntax isn't correct. Any more help is so greatly appreciated and I appreciate the already prompt response. Thanks!!!
callison.168 said:
Thanks so much for the quick reply. I think I've made some headway...I can "see" the device with cmd by typing adb devices. After that though, I don't understand how to get the stock nexus s rom on the phone. How do I move that file to my phone (what's the line of code I type)? I've tried "adb install <c:\grh78> but it says the syntax isn't correct. Any more help is so greatly appreciated and I appreciate the already prompt response. Thanks!!!
Click to expand...
Click to collapse
Download your rom of choice (stock, custom)
Flash Cwm via fastboot if you haven't already
Boot into recovery.
Use adb push to push your zipped rom to the sdcard (adb push file.zip /sdcard/file.zip)
Use cwm to flash this zip.
Sent from my Nexus S using xda premium
callison.168 said:
Thanks so much for the quick reply. I think I've made some headway...I can "see" the device with cmd by typing adb devices. After that though, I don't understand how to get the stock nexus s rom on the phone. How do I move that file to my phone (what's the line of code I type)? I've tried "adb install <c:\grh78> but it says the syntax isn't correct. Any more help is so greatly appreciated and I appreciate the already prompt response. Thanks!!!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=9866675
http://forum.xda-developers.com/showthread.php?t=884093
These threads should be a complete solution to your issue.
Disclaimer : I take no responsibility of what so ever happens to your phone, however you should be good if you follow proper steps.
Wow fast responses. I bet it's annoying to help yet another person having issues (again, phone was given to me like this but yeah...) while you guys or gals already know how to do these things very well. Here's where I'm stuck. I enter this code in cmd:
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
and it just says < waiting for device >.
Here's a pic of the screen that I'm on with my phone when i enter the command.
http://imgur.com/Pey3W
If I'm just in the first screen by holding volume up and power, the computer won't read the phone. So I click recovery, the screen shows it's trying to install something then the triangle exclamation mark, i press volume up/down with power and get this screen and the computer can "see" my phone on cmd.
How do I get this flipping clockwork on this phone or get the stock image on my sd card? Thanks again for helping me out guys. I have taken a look at the links you have sent me and that's where i found the download as well as the code to enter. I will keep looking at them but if you find a faster solution, please let me know.
One more thing to be super clear on...when I'm on the screen on the Nexus S that says Fastboot Mode on top in red and Lock State - Unlocked...my computer won't read the phone, therefore I cannot fastboot the recovery img...
callison.168 said:
One more thing to be super clear on...when I'm on the screen on the Nexus S that says Fastboot Mode on top in red and Lock State - Unlocked...my computer won't read the phone, therefore I cannot fastboot the recovery img...
Click to expand...
Click to collapse
So you already tried "fastboot devices" while in fastboot mode?
Edit: Actually it sounds you really want stock so download the complete stock OTA ROM (including boot.img etc.), rename it to update.zip and put it on the root of your sdcard. Boot into the stock recovery like you did already and hit apply update.
EDIT: Go here to download the correct OTA http://forum.xda-developers.com/showthread.php?t=1056062
Find the correct 2.3.6 "Full ROM" for your phone model. Sounds like in those instructions you don't need to rename to update.zip. Haven't seen stock recovery for a while so I don't remember.
If there is a wipe option in the stock recovery then do that first.
Yes I have tried fastboot devices in fastboot mode but nothing because my computer doesn't read the phone in that mode. And yes, I want to put the stock rom on there but that's the key, I can't get access to the root of my sdcard. I can't push anything into the sdcard to flash it. Any ideas what to type or how to access the sdcard? Thanks a million, billion.
Also, I can't get the phone to boot at all, like I can't get passed the Google Logo if I reboot so I can't access the sdcard in the traditional way.
callison.168 said:
Yes I have tried fastboot devices in fastboot mode but nothing because my computer doesn't read the phone in that mode. And yes, I want to put the stock rom on there but that's the key, I can't get access to the root of my sdcard. I can't push anything into the sdcard to flash it. Any ideas what to type or how to access the sdcard? Thanks a million, billion.
Click to expand...
Click to collapse
Connect with adb and type this:
adb shell mount /sdcard
Then type:
adb push rom.zip /sdcard/update.zip
callison.168 said:
Yes I have tried fastboot devices in fastboot mode but nothing because my computer doesn't read the phone in that mode. And yes, I want to put the stock rom on there but that's the key, I can't get access to the root of my sdcard. I can't push anything into the sdcard to flash it. Any ideas what to type or how to access the sdcard? Thanks a million, billion.
Click to expand...
Click to collapse
If fastboot devices returns NOTHING then this is most likely a driver issue. Remove the device through device manager, make sure you have a recent SDK (for the USB driver) and let it re-detect.
callison.168 said:
Also, I can't get the phone to boot at all, like I can't turn on the phone so I can't access the sdcard in the traditional way.
Click to expand...
Click to collapse
If you can get into the boot loader and get a proper USB driver you should be able to flash a recovery.
Once you've flashed Clockwork Mod (recovery) you'll be able to push to the sdcard using ADB or possibly mount the sd card through the CWM menu (although I've yet to have that work).
In order to get a recovery flashed though you need to get fastboot to see your device (unless you can already boot into recovery, then just use ADB).
irishrally said:
Connect with adb and type this:
adb shell mount /sdcard
Then type:
adb push rom.zip /sdcard/update.zip
Click to expand...
Click to collapse
If he's stuck at the Google logo and has a trash boot.img it's not likely he'll be able to get a shell via ADB. Now, if the system is hanging starting a device or looping during boot then that's possible.
krohnjw said:
If he's stuck at the Google logo and has a trash boot.img it's not likely he'll be able to get a shell via ADB. Now, if the system is hanging starting a device or looping during boot then that's possible.
Click to expand...
Click to collapse
He said he can access stock recovery and has connected with adb, unless I read wrong.
irishrally said:
He said he can access stock recovery and has connected with adb, unless I read wrong.
Click to expand...
Click to collapse
Indeed - I saw no clockwork and figured he'd toasted his recovery image as well, but it does look like stock recovery is there. ADB should push fine to the sdcard from recovery then.
More...so if i type in adb reboot bootloader in the recovery screen, it does just that...great. But then my computer makes a noise, a double tap if you will...like a dun dun, like something didn't work. When you plug in something to the computer it usually goes like dun na...but the phone clearly won't read when I'm in bootloader/fastboot mode. So when I type a command, nothing will work...
callison.168 said:
More...so if i type in adb reboot bootloader in the recovery screen, it does just that...great. But then my computer makes a noise, a double tap if you will...like a dun dun, like something didn't work. When you plug in something to the computer it usually goes like dun na...but the phone clearly won't read when I'm in bootloader/fastboot mode. So when I type a command, nothing will work...
Click to expand...
Click to collapse
That noise is that it detects a device has been connected (assuming a recent version of windows). If you want to flash CWM you need to get the driver sorted for the device. No amount of plugging/unplugging is going to fix it.
If you have the stock recovery you can boot into the stock recovery, use adb to push the full OTA package to the sd card and then just flash that from the stock recovery.
callison.168 said:
More...so if i type in adb reboot bootloader in the recovery screen, it does just that...great. But then my computer makes a noise, a double tap if you will...like a dun dun, like something didn't work. When you plug in something to the computer it usually goes like dun na...but the phone clearly won't read when I'm in bootloader/fastboot mode. So when I type a command, nothing will work...
Click to expand...
Click to collapse
Go to the stock recovery like you have done before and type the adb command I wrote above.
Thanks is all I can say. Okay so when I type in the command, this is what I get:
- exec '/system/bin/sh' failed: No such file or directory (2) -
the "stock recovery" I can get into is the picture I posted a link for. That's what I can access as well as the fastboot mode when I first turn on the phone with volume up/power. But when my computer makes the noise that it's connected (using Windows 7 64bit) it makes a different sound then the normal "device connected." Like it's corrupted.
by the way...if we can get this working, I'll post a picture of me holding the fixed phone!
A few days ago I tried getting my phone to s-off using the "[how to] manually achieve s-off,simunlock,supercid for Inspire 4g/DHD" guide on the Android forums. (Sorry, I can't post direct links.)
I got to the part where I was supposed to type in "fastboot flash boot boot.img" to the command line but I accidentally skipped that part and typed in "fastboot boot recovery recovery.img". I stopped everything and tried to start over but when I turned my phone back on I was stuck in a boot loop. Going to hboot and trying to choose Recovery or Factory Reset only results in more boot looping.
I've tried putting PD98IMG.zip on the SD card and booting it, but it only reads it and says "Parsing..." before doing nothing. Attempting to enter recovery mode after this makes it enter the boot loop again.
I've also tried using the HTC Sense and RUU from AT&T on my computer to fix the issue. My phone can connect to my PC after choosing fastboot from the hboot menu. The RUU can see the device and it starts recovering it, as my phone shows a black background with HTC on it. But the RUU stops after trying to update the signature saying "The ROM Update Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again." I am 99% positive I am using the correct RUU.
I've searched high and low on the internet for a similar situation, but everyone else seems to have their problems solved using either of these steps. Thanks for any help.
Without knowing what you did (since you haven't given us a step-by-step and can't post links), we don't know how to help.
Sorry about that. I'll try to explain what I did the best I can.
Before using the guide, I managed to root my phone and used it for a few days, so everything was fine then. I later decided to s-off it so I could flash a custom ROM to it. Using the guide I mentioned above, I created a mini-adb directory in my C: drive with the ace-tools.zip that I downloaded. Using the command line I copied my stock boot image, though to where I do not know. (I feel like a fool for doing all this without being sure of what I was doing exactly. I deserve what came to me.) Then, using the command line I made my SD card a gold card. After that I changed the "misc version" (?) to allow installation of the downgrade firmware, and then relocked the boot loader and booted back into fastboot. Then I flashed the downgrade software and unlocked it again. It's here that my phone was supposed to be unable to boot, and I was supposed to flash the boot image but skipped that step.
Now I'm unsure of what I have to do, and I only want to get my device working again.
I wish I could post the link to the exact topic, but since I can't I guess you'd have to search the topic name to see exactly what the directions were trying to get me to do.
Thanks again.
Can you boot the phone into fastboot and flash the boot.img from fastboot?
No, with the PD98IMG.zip file it simply says "Parsing..." and stops there. With any other boot image it doesn't acknowledge it at all. Even though the computer makes the sound that it's connected to the device when it's in fastboot, adb can't recognize that's it's there in the command line.
SammichMonster said:
No, with the PD98IMG.zip file it simply says "Parsing..." and stops there. With any other boot image it doesn't acknowledge it at all. Even though the computer makes the sound that it's connected to the device when it's in fastboot, adb can't recognize that's it's there in the command line.
Click to expand...
Click to collapse
Wait. What? Not PD98IMG.zip from hboot. Extract the boot.img and flash from fastboot, not adb.
Ah, thanks for the clarification. I'm supposed to extract the boot.img to the SD card and enter fastboot on my phone, correct? Because I've just done so and nothing happened. I have the options Bootloader, Reboot, Reboot Bootloader, and Power Down, and the Bootloader option only takes me back to the hboot screen.
Sorry if I've misunderstood you.
SammichMonster said:
Ah, thanks for the clarification. I'm supposed to extract the boot.img to the SD card and enter fastboot on my phone, correct? Because I've just done so and nothing happened. I have the options Bootloader, Reboot, Reboot Bootloader, and Power Down, and the Bootloader option only takes me back to the hboot screen.
Sorry if I've misunderstood you.
Click to expand...
Click to collapse
No, the boot.img needs to be on your computer. Your phone needs to be in fastboot mode. From the folder where the boot.img is saved,
Code:
fastboot flash boot boot.img
I can't use the command prompt to connect with the device because it can't see it. I always get an "error: device not found" instead.
Is your phone in fastboot mode?
Yes. It's odd: the RUU software identifies it and knows it's there, but can't actually fix the issue. The command prompt just doesn't notice it at all.
SammichMonster said:
Yes. It's odd: the RUU software identifies it and knows it's there, but can't actually fix the issue. The command prompt just doesn't notice it at all.
Click to expand...
Click to collapse
So you're booting into hboot, navigating to fastboot with the volume buttons, and selecting it with the power button? What does fastboot devices say?
I'm assuming by "fastboot devices" you mean what it says in the command prompt.
...Well what do you know, it recognized it. I was typing in "adb devices" instead of "fastboot devices". So it can recognize it after all.
I'm assuming I have to load the boot.img now?
Hey hey, wa-hey!
That was much easier than I thought it would be! A simple "fastboot flash boot boot.img" followed by a fastboot flash recovery recovery.img" using some image files I made before messing everything up did the trick. Thank god I did so.
Everything's back to normal; my phone escaped the boot loop. And last but not least, I don't have to buy a new phone.
Thanks so much for helping me out, even if it was clearing a few things up for me. I appreciate it.
SammichMonster said:
...Well what do you know, it recognized it. I was typing in "adb devices" instead of "fastboot devices". So it can recognize it after all.
Click to expand...
Click to collapse
That's what i figured you were doing, so that's why I clarified.
SammichMonster said:
Hey hey, wa-hey!
That was much easier than I thought it would be! A simple "fastboot flash boot boot.img" followed by a fastboot flash recovery recovery.img" using some image files I made before messing everything up did the trick. Thank god I did so.
Everything's back to normal; my phone escaped the boot loop. And last but not least, I don't have to buy a new phone.
Thanks so much for helping me out, even if it was clearing a few things up for me. I appreciate it.
Click to expand...
Click to collapse
You're welcome. You could also have fastboot flashed any custom recovery image, flashed a ROM from recovery, and fastboot flashed that ROM's boot.img. So you weren't too badly off.
I tried to flash a custom rom (KatKiss), and it seems that I did something wrong along the way because the tablet is stuck in a bootloop.
So I rebooted my tablet and access the bootloader ("fastboot devices" recognize my device) and try to go to the recovery (with the TWRP splash screen, "adb devices" recognize my device). Unfortunately after 20 seconds on the splash screen, the tablet reboots (tries to load my katkiss android but bootloop everytime).
Bootloader : 10.6.1.14.10
TWRP : 3.1.1.0
Since the fastboot recognize my device while in bootloader, I think that I should try to flash twrp since it seems to be corrupted somehow.
Every time I flashed a rom nothing went wrong but now that I have a problem I don't want to worsen it and would like some help on the issue.
Did you flash the rom in your current TWRP?
Something is off... Did you possibly flash the TF201 rom version??
Whatever you do - do not use Wipe Data from the bootloader!!
Reflash TWRP, format data, then reflash the rom
And report in more detail what you did
Sent from my Nexus 5X using Tapatalk
Thank you for the fast reply!
I did flash the rom with my current TWRP and only downloaded the rom version for the TF700. Below is what I tried from your suggestion:
I check that my device is recognized:
fastboot device
So I tried flashing TWRP:
fastboot flash recovery twrp-3.1.1-0-tf700t
After it succeeded, I reboot the tablet:
fastboot reboot
And as a result... nothing changes, I don't know if I should try with older version of TWRP. Seems like I only have access to the tablet with the fastboot.
That is very strange indeed. Yes, try a 3.0.2 version of TWRP and see if that works.
If not, I would flash the Asus stock blob in fastboot and start from scratch....
Sent from my TF700T using Tapatalk
Kromlech said:
And as a result... nothing changes, I don't know if I should try with older version of TWRP. Seems like I only have access to the tablet with the fastboot.
Click to expand...
Click to collapse
Not sure if this will help but I had a reboot problem with trying to load into TWRP. I posted my solution into a different thread but will toss it out here..
I just had this problem with a Transformer 201Prime. The cycle went something like this..
Power on.... get ASUS logo in middle, Tegra3 logo on lower right, and bootloader unlocked in upper left....
then a buzz... then reboot.....
So I would try the power button and hold the volume down... that got me into the bootloader but when I hit the volume up button it would give me the TWRP logo... then buzz and reboot...
After much monkeying around... I realized I would have to re install everything. Fortunately I had the original NVFLASH bloob files backed up so I was able to get into the NVFLASH commands.
Here is a great tutorial, it is for the 201 so be sure to download the correct files but the steps are basically the same.
https://forum.xda-developers.com/tra...prime-t3486237
The other problems is I had to download a bloob tool to 'unpack' the necessary .bin and .ebt files that are mentioned in the commands... I used the following link to download the tool.
https://github.com/AndroidRoot/BlobTools
I hope this helps shake loose a few answers.
Once I was able to get a working recovery I could flash an updated ROM. (KatKiss is my current favorite)
I tried to flash version 3.0.2 of TWRP and the problem is still the same.
@Unidave199 the link you put in your post points to a post that doesn't seems to exist anymore, has it been moved?
@berndblb how do I do for flashing a rom with the fastboot? any stock rom to recommend?
double post
Kromlech said:
I tried to flash version 3.0.2 of TWRP and the problem is still the same.
@Unidave199 the link you put in your post points to a post that doesn't seems to exist anymore, has it been moved?
@berndblb how do I do for flashing a rom with the fastboot? any stock rom to recommend?
Click to expand...
Click to collapse
Unidave's link would only help you if you generated your device specific nvflash blobs when the tablet was still functioning. Did you:
flash a specifically modded recovery - flash the moddded bootloader, use wheelie to generate and save your blobs, return everything to factory specs?
I highly doubt it since you would have mentioned...
To flash the stock blob in fastboot you download the Asus firmware from here: https://www.asus.com/my/support/Download/28/1/0/11/29/8/
Extract the zip twice until you see a blob and a meta-inf file.
Move the blob into your fastboot folder, discard the rest of the file
Issue these commands one by one, letting each one finish before starting the next. Some will finish quick, others may take up to 3 minutes:
Code:
fastboot erase system
fastboot erase boot
fastboot erase recovery
fastboot erase misc
fastboot erase cache
fastboot erase userdata
fastboot flash system blob
fastboot reboot
The first boot will take a while, but that should put you back on a stock JB 4.2 system.
Trash all the files you used in your last attempt and redownload the rom, gapps and supersu
Fastboot flash TWRP
Reboot
Format /data in TWRP (this will take up to 1 hour - let it finish!!), then convert /data to f2fs
Flash the rom, gapps, supersu
If you flash Nougatella remember that you have to turn on wifi right after the language selection during setup or Google framework will crash.
Spend the end of the day doing it, but it worked flawlessly! Thanks a lot @berndblb, now I can use my tablet again!
Kromlech said:
I tried to flash version 3.0.2 of TWRP and the problem is still the same.
@Unidave199 the link you put in your post points to a post that doesn't seems to exist anymore, has it been moved?
@berndblb how do I do for flashing a rom with the fastboot? any stock rom to recommend?
Click to expand...
Click to collapse
My apologies for the problem with my link, looks like you resolved it, but wanted to post a correct working link to take someone else into the full conversation and context...
https://forum.xda-developers.com/showpost.php?p=71150385
berndblb said:
To flash the stock blob in fastboot you download the Asus firmware from here: https://www.asus.com/support/Download/28/1/0/11/fq2B3oq64av1O95/8/
Click to expand...
Click to collapse
Broken link ? that post isn't very old, either. ??
berndblb said:
Did you flash the rom in your current TWRP?
Something is off... Did you possibly flash the TF201 rom version??
Whatever you do - do not use Wipe Data from the bootloader!!
Reflash TWRP, format data, then reflash the rom
And report in more detail what you did
Click to expand...
Click to collapse
I did wipe data from bootloader, now I can't go to bootloader. How to revive my tf700t?
Please help
Thanks
ketulharini said:
I did wipe data from bootloader, now I can't go to bootloader. How to revive my tf700t?
Please help
Thanks
Click to expand...
Click to collapse
You'll need to refer to post #8. However, the link to the tf700 stock blob is broken. You'll have to search Google for one. They're out there, but it does require digging .Make sure the one you get is for the proper SKU of your tablet (US, Worldwide, JP, etc.). I completed the process myself maybe a month ago. Good luck!
monogwai said:
You'll need to refer to post #8. However, the link to the tf700 stock blob is broken. You'll have to search Google for one. They're out there, but it does require digging .Make sure the one you get is for the proper SKU of your tablet (US, Worldwide, JP, etc.). I completed the process myself maybe a month ago. Good luck!
Click to expand...
Click to collapse
I got the stock blob ww version.
Just tab doesn't stay on fastboot mode keeps rebooting.
Don't know how to do it.
Is it possible to get stable fastboot screen some how? Or just flash the bootloader to get fastboot working.
May be this noob question but I don't know how to do.
Thanks
ketulharini said:
I got the stock blob ww version.
Just tab doesn't stay on fastboot mode keeps rebooting.
Don't know how to do it.
Is it possible to get stable fastboot screen some how? Or just flash the bootloader to get fastboot working.
May be this noob question but I don't know how to do.
Thanks
Click to expand...
Click to collapse
There is one more piece to the puzzle- hold short while I dig it up.
Here it is: http://www.transformerforums.com/forum/transformer-pad-infinity-tf700-tegra-3-development/46302-guide-help-my-transformer-tf700-boots-only-recovery.html
Do be *very* careful. Read thrice, do it once. Especially if you're feeling noob-y.
monogwai said:
There is one more piece to the puzzle- hold short while I dig it up.
Here it is: http://www.transformerforums.com/fo...my-transformer-tf700-boots-only-recovery.html
Do be *very* careful. Read thrice, do it once. Especially if you're feeling noob-y.
Click to expand...
Click to collapse
Thanks for this information.
One more question,
My tab is keep bootlooping neither it stays on twrp nor bootloader.
It has blue screen of recovery that is twrp after 5 to 10 seconds it boots again.
Is this enough time to execute the commands while it is on blue screen?
Thanks
ketulharini said:
Thanks for this information.
One more question,
My tab is keep bootlooping neither it stays on twrp nor bootloader.
It has blue screen of recovery that is twrp after 5 to 10 seconds it boots again.
Is this enough time to execute the commands while it is on blue screen?
Thanks
Click to expand...
Click to collapse
Well, that depends on several things. What I did was write a short little DOS batch file to process all the fastboot commands. So, with your batch file ready, open your command prompt (change directory to your adb/fastboot directory if it's not set in system's 'path=' environment variable) and have the batch command typed in, ready to hit enter. Tether to pc via USB, proceed to boot to adb. The second you hear windows make the USB notification sound, slap that enter key. It should just process and reset the tab and get you out of TWRP bootloop. Which is just step one.
If you aren't familiar with writing bat files for DOS, let me know.
monogwai said:
Well, that depends on several things. What I did was write a short little DOS batch file to process all the fastboot commands. So, with your batch file ready, open your command prompt (change directory to your adb/fastboot directory if it's not set in system's 'path=' environment variable) and have the batch command typed in, ready to hit enter. Tether to pc via USB, proceed to boot to adb. The second you hear windows make the USB notification sound, slap that enter key. It should just process and reset the tab and get you out of TWRP bootloop. Which is just step one.
If you aren't familiar with writing bat files for DOS, let me know.
Click to expand...
Click to collapse
You mean a batch file with the adb commands right? Once he can boot into fastboot he has all the time in the world to run the commands for the buster99 (description in post #8). Depending on what situation he came from before, it might be a good idea to start all fresh...
The tricky thing are the adb push bootit.ko and the insmod command. Those have to be timed just right to get executed, so a batch file might come in handy. Both commands only take a second or two to execute, so your window of 5 seconds could work. Maybe not in the same session, but they should work.
If the insmod command does not kick the tablet into the bootloader, there are 2 possible reasoons:
adb push bootit.ko did not work
the insmod command did not work
To find out if the file push worked you could add a simple list command for the contents of /sdcard/. Again - tricky, I know since you still are working with the 5 sec window, but that's what you got to work with...
That would look something like in the attached picture. So after pushing bootit.ko you issue:
Code:
adb shell ls /sdcard/
Try it with the batch file, try it with single commands... Don't give up. As long as you have any kind of adb access you should be able to solve it.
Good luck!
berndblb said:
You mean a batch file with the adb commands right?
Click to expand...
Click to collapse
Yeah.
berndblb said:
Once he can boot into fastboot he has all the time in the world to run the commands for the buster99 (description in post #8).
Click to expand...
Click to collapse
Again, mistake in my terminology. What I meant to say is, batch commands for the process involving the Bootit.ko- the adb portion.
Thanks for clearing that up.
@ketulharini
Anyhow, I was unable to get the process to take without having automated *every last step* of the process. Literally open the cmd window, have the command for your batch file typed in ready to go, and plug in. Hear the noise from windows and slap enter asap. That's the only way I could get it in time, and I'm a ridiculously fast typist.
monogwai said:
Yeah.
Again, mistake in my terminology. What I meant to say is, batch commands for the process involving the Bootit.ko- the adb portion.
Thanks for clearing that up.
@ketulharini
Anyhow, I was unable to get the process to take without having automated *every last step* of the process. Literally open the cmd window, have the command for your batch file typed in ready to go, and plug in. Hear the noise from windows and slap enter asap. That's the only way I could get it in time, and I'm a ridiculously fast typist.
Click to expand...
Click to collapse
Care to share the batch file?