[Q] Xoom Bootloop - Xoom Q&A, Help & Troubleshooting

My Motorola Xoom is stuck in an BootLoop
It is an European Xoom.
It had 3.1 (OTA).
I unlocked the bootloader, with succes.
Using this guide: http://imransarwar.com/index.php/how-to-unlock-and-re-lock-motorola-xoom-for-flashing/
Then I used this guide:
http://imransarwar.com/index.php/how-to-root-motorola-xoom-wifi-from-stock-3-1/
http://forum.xda-developers.com/showthread.php?t=1078019
After catch-the-boot, I came in the ClockWorkMod Recovery, as expected.
But the clicking on 'Install zip from SD card' showed the contents of the internal storage, not the physical SD.
So I rebooted the device, and have put the Zip-file on the internal Storage.
I went into recovery-again, i selected the zip-file.
It says 'Done '.
I Click on Reboot Device Now.
*BOOT LOOP*
I can still use:
adb reboot
And when i have done 'adb reboot', i can also reach fastboot.
(there is still hope?)
My Assumptions:
As the recovery 'install zip from sd' uses the internal storage,
it has no use to try putting something on the physical sd-card.
Is there a way to get something (read: some fix zip-file) on the internal storage, using nothing but ADB and Fastboot?
like adb push, would that work? if that would work, what do i have to push?
Any help is appreciated !
EDIT:
Found possible solution.
I'll think I should try this:
http://www.dkszone.net/unroot-relock-motorola-xoom-honeycomb-guide
It will get the device back to stock (I hope).
EDIT2:
Ok.. I tried the guide above.
My Device hangs on the Dual Core-screen.
Just found out that the File i have downloaded for the above guide is not the right version for my European Xoom (Wifi).
It was for 3G-Xoom-devices.
Downloading the right version now..
I Hope that i can come into Fastboot again, so i can flash the correct version.
EDIT3:
The device is still hanging on the Dual-Core-Screen,
it does not respond to anything, no buttons, no adb, no fastboot...
I guess i have to wait till the battery is empty, (this might take a while)
then turn it on while holding the volume down button to try to get into fastboot
If I cannot get into fastboot, my device is bricked I guess.

frankkienl said:
My Motorola Xoom is stuck in an BootLoop
It is an European Xoom.
It had 3.1 (OTA).
I unlocked the bootloader, with succes.
Using this guide: http://imransarwar.com/index.php/how-to-unlock-and-re-lock-motorola-xoom-for-flashing/
Then I used this guide:
http://imransarwar.com/index.php/how-to-root-motorola-xoom-wifi-from-stock-3-1/
http://forum.xda-developers.com/showthread.php?t=1078019
After catch-the-boot, I came in the ClockWorkMod Recovery, as expected.
But the clicking on 'Install zip from SD card' showed the contents of the internal storage, not the physical SD.
So I rebooted the device, and have put the Zip-file on the internal Storage.
I went into recovery-again, i selected the zip-file.
It says 'Done '.
I Click on Reboot Device Now.
*BOOT LOOP*
I can still use:
adb reboot
And when i have done 'adb reboot', i can also reach fastboot.
(there is still hope?)
My Assumptions:
As the recovery 'install zip from sd' uses the internal storage,
it has no use to try putting something on the physical sd-card.
Is there a way to get something (read: some fix zip-file) on the internal storage, using nothing but ADB and Fastboot?
like adb push, would that work? if that would work, what do i have to push?
Any help is appreciated !
EDIT:
Found possible solution.
I'll think I should try this:
http://www.dkszone.net/unroot-relock-motorola-xoom-honeycomb-guide
It will get the device back to stock (I hope).
EDIT2:
Ok.. I tried the guide above.
My Device hangs on the Dual Core-screen.
Just found out that the File i have downloaded for the above guide is not the right version for my European Xoom (Wifi).
It was for 3G-Xoom-devices.
Downloading the right version now..
I Hope that i can come into Fastboot again, so i can flash the correct version.
EDIT3:
The device is still hanging on the Dual-Core-Screen,
it does not respond to anything, no buttons, no adb, no fastboot...
I guess i have to wait till the battery is empty, (this might take a while)
then turn it on while holding the volume down button to try to get into fastboot
If I cannot get into fastboot, my device is bricked I guess.
Click to expand...
Click to collapse
It's not bricked. It's really hard (but not impossible) to brick a Xoom. They are hardy beasts.
I do wish you hadn't tried the revert/relock thing. You just made it worse as you tried to flash a 3G image on a WiFi only device.
But don't worry, it is possible to come back from this.
Just so you know, your first mistake was using old guides (though filled with good info, but files are not necessarity right) and mixing the sources. There are much newer guides in the Development section (page 1) for non-US Xoom, and I think people have better result when they stick with one source (in this case xda Xoom forum).
Second mistake is that you used the wrong recovery image...you used the v4.0.0.4 from RomManager, which is not compatible with the external micro sd card. You need the v3.2.0.0 R4c (Tiamat version). That's still the best most current version for the Xoom.
http://forum.xda-developers.com/showthread.php?t=1074979
If you had not gotten impatient and tried to revert/relock, you could have just flashed the proper recovery image and you would be good to go.
Good luck!
You seem to know your way around adb and fastboot so I'm sure you will be able to recover. Find the proper stock images for your Euro WiFi Xoom and flash them, download and flash the correct recovery image and you can take it from there.

It works again !
I Fixed it it works again
( I Do not have Root, but i'm glad its not bricked)
My device was hanging on the Dual-core screen.
So I waited till the battery was empty.
I connected the charger and usb cable, powered it on while holding volume-down.
Guess what, I came into fastboot
I have downloaded the correct images from the motodev-website.
Just followed the instructions (on the motodev site) and was good to go.
All what was left was updating to 3.1. That also worked fine.
I will be more carefull next time I try to Root an Android device, and make sure the guide is not for a different device. I have learned from my mistake.

frankkienl said:
I Fixed it it works again
( I Do not have Root, but i'm glad its not bricked)
My device was hanging on the Dual-core screen.
So I waited till the battery was empty.
I connected the charger and usb cable, powered it on while holding volume-down.
Guess what, I came into fastboot
I have downloaded the correct images from the motodev-website.
Just followed the instructions (on the motodev site) and was good to go.
All what was left was updating to 3.1. That also worked fine.
I will be more carefull next time I try to Root an Android device, and make sure the guide is not for a different device. I have learned from my mistake.
Click to expand...
Click to collapse
Excellent! So glad to hear it. You have skills so I'm sure you will be coool from now on.

just an update
This is an old thread so I'm putting this here for google searchers, like me.
I had the same problem but here's what extra I found/noticed
(1) To restart the xoom when it's in this state hit power button and volume up
(2) You can see that the tablet is still responsive if you hit volume down after 2 seconds as you'll get some options
(3) For me it wouldn't work if I used the motorola cable (yes, the real one) in the front pc usb ports. I had to use the usb 3 ports at the back of my pc. Yes, it's that picky! The difference was when I used fastboot to install the system image. It took 3 minutes then gave up, stuck the cable in the back of the pc instead and it took about 10 seconds and worked first go!
(4) The pc didn't recognise the xoom and adb didn't work, i.e. it said no device attached. However fastboot did recognise it
After point (4) I realised it wasn't bricked and could move forward
thanks to the other posters here for making me realise there was hope

Related

[Q] phone is dead , can only enter in cloxkworkmod recovery

Hi all expert,
my nexus s is unrooted. i installed ADB in my win7. I did wipe out all data/sd card without any back up. so my phone cant go anywhere ,except into clockworkmod recover. when I try to boot, error say it cant find any image. I cant instal image if i cant get in to the phone and set the usb connection. So my question is how to force install image into the phone without enablimg the usb connection? Please help. thank you
rongsokan said:
Hi all expert,
my nexus s is unrooted. i installed ADB in my win7. I did wipe out all data/sd card without any back up. so my phone cant go anywhere ,except into clockworkmod recover. when I try to boot, error say it cant find any image. I cant instal image if i cant get in to the phone and set the usb connection. So my question is how to force install image into the phone without enablimg the usb connection? Please help. thank you
Click to expand...
Click to collapse
you have clockwork recovery right? theres an usb storage option in the recovery itself. connect it to your computer, turn on the usb storage. download a rom(and gapps) to your computer, copy/paste into the device, turn off usb storage, then flash the files in clockwork recovery. then reboot.
After you do what he said, either do alot of research about rooting, and flashing roms and kernels or sell your phone.
Sent from my Nexus S 4G using xda premium
simms22 said:
you have clockwork recovery right? theres an usb storage option in the recovery itself. connect it to your computer, turn on the usb storage. download a rom(and gapps) to your computer, copy/paste into the device, turn off usb storage, then flash the files in clockwork recovery. then reboot.
Click to expand...
Click to collapse
So I did follow your instruction. I went storage->mount usb storage->unmount(I can only select this, I try reboot the phone still give me this only option). so I also tried mount sdcard, mount system, all that.
Finlally, I got removable disk on my computer, but it show 0 byte, when i click on it, it says plz insert a disk into removeable disk. so i went click
property->hardwares->highlight Android UMS composite usb device(type: disk drive) and property. then I select driver-> and there is driver details, update driver. So do I update this driver? If so which driver?
I try to format it, it gives errorlz insert a disk into removeable disk
I have clcokworkmod recovery v5.0.2.0 and it is unrooted. thank you for the help!
I also install PDAnet into my computer but it keep saying connecting to your phone..... I try using different usb port and no luck.
rongsokan said:
So I did follow your instruction. I went storage->mount usb storage->unmount(I can only select this, I try reboot the phone still give me this only option). so I also tried mount sdcard, mount system, all that.
Finlally, I got removable disk on my computer, but it show 0 byte, when i click on it, it says plz insert a disk into removeable disk. so i went click
property->hardwares->highlight Android UMS composite usb device(type: disk drive) and property. then I select driver-> and there is driver details, update driver. So do I update this driver? If so which driver?
I try to format it, it gives errorlz insert a disk into removeable disk
I have clcokworkmod recovery v5.0.2.0 and it is unrooted. thank you for the help!
Click to expand...
Click to collapse
By the way you just click on mount usb storage and LEAVE IT there for a few seconds. It takes a little time for the computer to recognize it usually. You only click unmount when your done...
ok i got it. now i could put files into the sd storage. Do you guys know what i need to put for stock, out-of box image?
I need to reset this to factory setting and root the phone.
I did some serach but the file needed to download is not working anymore. anyone know? thank you
rongsokan said:
ok i got it. now i could put files into the sd storage. Do you guys know what i need to put for stock, out-of box image?
I need to reset this to factory setting and root the phone.
I did some serach but the file needed to download is not working anymore. anyone know? thank you
Click to expand...
Click to collapse
Here is a thought... read some more before messing with your phone instead of asking questions which have been already answered many times.
Sent from my Nexus S 4G
I have been reading reading again... the whole day today. I just dont want to install the wrong drive or file. for nexus s tehre is so many version. the one i got for bootloader is i9020xxka3
for baseband version- i9020xxkf1
fastboot mode stil showing- NO BOOT OR RECOVERY IMG
I give up may be I am too idiot.
obsanity said:
Here is a thought... read some more before messing with your phone instead of asking questions which have been already answered many times.
Sent from my Nexus S 4G
Click to expand...
Click to collapse
Coming from someone that also finds conditions & situations similar but not precisely like my own in the multitude of answered threads..... Some of us can get to a certain point but get stuck, and since these are devices we need to work we want to be sure we don't do something to turn an expensive device into a pretty paperweight.
You learned by fiddling and asking questions did you not? If you are sick of the same old question don't answer the thread.
Sorry, I have no great advice for the OP, you aren't an idiot you are uninformed [just yet] of the proper fix for your problem. I'm still trying to fix something myself so the couple of snipes hit a nerve this morning.
I read read read and read again, its been almost a week. Good god I cant get the solution or may be i dont undderstand it. I try go to cmd prompt and "type fast boot lock" to get it rooted. No luck
my phone situation:
No back up or recovery ( I wipe all sd/back up/system)
fasboot mode-no boot or recovery img
Lock state- unlocked
can only go into clockwork mod
my Goal: lock the phone and flash it to factory stock setting.
I just own nexus s for 7 days and did a ton of research coz stuck at google X animation keep loading and install MIUI and unroot the phone. Soooo stupid of me now that I broke the warranty. Softkeys is no even working!!!!!! when i suscessfully get into the phone.
is there a proper step by step to do this? is there any expert here that can point to the right direction? I am checking this post every 5 minutes
Clearly this is too much phone for you.
Sent from my Nexus S 4G using xda premium
Ok I'll try to help you.
According to what I gather from your posts, you've been successful in unlocking the bootloader and managed to flash CWM recovery, that's a good first step.
Your goal is still unclear. Ok, you want to re-lock the phone and 'restore to factory stock settings'? Does that mean you want a stock firmware on your phone or would you settle for a custom firmware, like Cyanogenmod or MIUI? Either way, visit the Nexus S Development forum, there's a full list of firmwares , just pick whichever you want and download that.
Here's a fantastic topic with a list of all firmwares and also plenty of links to guides:
http://forum.xda-developers.com/showthread.php?t=1067813
Enter CWM recovery mode (VolumeUP + Power button and select Recovery in the Bootloader options).
Go to mounts and storage. We want to mount or SDcard so we can transfer files from the PC to the SDcard as a USB mass storage device. Make sure the phone is connected through USB.
So, select the option: - mount USB Storage. Wait for a few seconds, it takes a while to get initialized by the PC.
Once it's recognized by your PC, copy the downloaded firmware to the SDcard. It should have a .zip extension and be approximately 100mb (of course depending on which flavour you picked, but that's somewhat the standard).
Once it's copied, go back in the CWM main menu and select "Install zip from sdcard". If you want, you can first wipe your cache and Dalvik cache, but since you clearly wiped everything already this shouldn't be necessary, so anyway; install zip from sdcard and select your firmware.zip file. Select it and press the power button to execute the install.
It will install the firmware plus the kernel that it's packed with, all this should be enough to get your phone booted. So reboot your phone and it should work.
Once you've successfully booted into your device, you can do whatever you like. If you want to lock the bootloader again though, you'll need to reverse the steps you took to unlock it. This is through ADB and Fastboot. But this topic explains it step by step and in detail, all credits to the OP: (http://forum.xda-developers.com/showthread.php?t=875630).
If the bootloader is locked again, you shouldn't have any issues with the warranty. It's a Nexus...
Some of your posts were a bit contradictory so I can only assume what your current status is with your phone.
Maybe you should also understand what everything means and does instead of blindy formatting disks and running random commands. Learn what ADB is, learn what Fastboot does. See how the bootloader works and where the recovery comes in, read up on the different firmwares and what kernels do. It might seem like a big investment of your time, but it will help you understand the boot process of the Nexus.
Good luck,
Greetz

[RESOLVED] Screwed up - Recovery will not load, neither will RSDLite - stuck

My phone is a Motorola Milestone A853.
I was testing out the new CM9 mod by kabaldan when I found myself running into a huge screw-up. No, not one that I believe is not reparable. Just one that is hard to get out of. Let me explain:
Having a wi-fi problem on multiple versions of the CM9 alpha ROM for the Milestone, I found myself trying to debug the situation in many ways. i.e. reflashing the ROM, wiping data/caches repeatedly... and trying a purported fix in the CM7 thread that did not work. In the middle of things, I decide do to format my SD card.
Bad idea.
Since the SD card pretty much contains OpenRecovery among other things it got wiped. Now I pretty much cannot access my recovery (which is Androidiani OpenRecovery).
I actually had the OpenRecovery folder backed up onto my hard drive, but copying it back has resolved nothing. It gets to that icon, stays there for a second, then fails and reboots back into the main OS.
This has happened to me before during about when I just got into modding the phone ROM (recovery screw up), which I recovered from using RSDLite to reflash a recovery. But now RSDLite does not even recognize my phone - this may have to do with the fact that it's running the CM9 ICS alpha ROM. So I can't repair the recovery, and I can't get my phone back to where it previously was and solve the wi-fi problem.
Thank goodness this has happened on a free long weekend. My phone is actually okay to use when I turn it on(can make calls, messages) but has none of my apps and whatever on it and I cannot fix anything with recovery, so on-the-go usage is near-useless. At the least I have a backup (Novo 8 tablet) for on-the-go stuff. But I want to get my phone back right away.
I know that there is another way to do this (sbf_flash I believe). I have access to a laptop running Xubuntu Linux (my old laptop, which was replaced by my tablet) to use sbf_flash, but is it possible to use it from Windows? (I think so).
Thanks to anyone that can help. I've done a lot of searching so far but I haven't found a huge amount plus I want to focus on getting this done and fixed sooner. I'm looking forward to full-fledged use of ICS on my Droid; from my experience so far, it's much faster than what I have moved from (latest version of MIUI).
What os do you have now?
You've been flashing stock roms. This restores stock recovery. Hence the need to flash vulnerable recovery or OpenRecovery will not work.
Along with OpenRecovery folder you need update.zip file.
Try to reinstall drivers since RSDLite shouldn't care what OS is on the device. Maybe it'll solve pc->device conectivity.
RSD won't detect device unless in bootloader mode.
If recovery won't boot automatically press volume up + camera.
Everything you might need is on this thread! Look for it.
1) "My phone is a Motorola Milestone A853"
2) "I'm looking forward to full-fledged use of ICS on my Droid"
The second is a pet talk I guess?
I thought RSD required that Phone portal USB connection option through the phone be working for recognition. Nothing happens in bootloader mode, pretty much. But I'll look into it. If RSD really shouldn't care about the OS on the device then I def have some driver reinstalling to do; is that true?
Current OS installed is the CM9.0 (ICS Android 4.0.3) alpha by kabaldan.
Same occurs when doing volume up + camera. Loads for a second, then quits (i.e. files not present, cannot complete loading).
You use RSDLite to flash .sbf files. That works only in bootloader mode.
When in bootloader mode and when you plug in usb cable the device should respond with something like USB OK, don't remember anymore, as should rsd give some info that the device is connected (left and right parts of main window provide info about device and the sbf file, respectively).
RSD finishes, phone boots, you reboot in bootloader, flash vulnerable recovery, prevent booting to OS and instead boot to recovery (OpenRecovery by now) by pressing hw keyboard X, verifiy that /system/etc/install-recovery.sh does not exist but if there delete it! or system will restore stock recovery.
More detailed instructions can be found on this forum and this thread.
Prior doing any of above: verify that you have openrecovery folder and corresponding update.zip in the root of your sdcard. Then try to boot to OpenRecovery as it seems to me that your main (or only) problem is that recovery on sdcard is broken.
or get another sdcard with recovery on it,insert on your phone and tadaa
Actually I tried returning the OpenRecovery folder and files (which I backed up onto my hard drive) onto the SD card and it did not work. I did not, however, move back the update.zip file. Perhaps the update.zip file had something to do with the boot ability? Because when I restored that (I didn't earlier), it finally went into recovery. So, problem solved everyone thanks!
xd_1771 said:
Actually I tried returning the OpenRecovery folder and files (which I backed up onto my hard drive) onto the SD card and it did not work. I did not, however, move back the update.zip file. Perhaps the update.zip file had something to do with the boot ability? Because when I restored that (I didn't earlier), it finally went into recovery. So, problem solved everyone thanks!
Click to expand...
Click to collapse
Just to prevent anyone else from having the same problem, I'm going to point out this:
update.zip from any of the recovery packages is needed every time you boot into recovery. It's a "special" update that is designed to crash the bootloader's update function and run unsigned code, such as a 3rd party recovery. Nothing ever actually gets flashed when this update is run.
Without the update.zip, you have no way to tell your device to launch the custom recovery, as we can not flash a replacement directly to the phone's memory because of Motorola's stupid signed-code-only checks.

B70 bricked - is there no way out?

Been modding android devices since the G1 but never got stuck like this before. Already spent hours of searching and googling but couldn't find any definite answer.
My B70 got bricked when using a program to boot into recovery.
Is there any way out or should I just throw it away?
I have a feeling that the device is looking for a recovery on internal SD card and fails. I can see the unit as ADB unit but when trying to connect it says device is offline both in normal boot or in recovery boot.
Been trying putting stock roms on external SD but it never runs it.
Has anyone solved this problem?
Check your SBK version and try to NVFlash
Try to boot recovery/apx wipe permissions /data if possible
post questions in Q&A not Dev
After a lot of examination it has been decided that you have posted this in the wrong section and we shall place it where it should be. Please make sure you post correctly next time.
Like mentioned already, some B70 are SBKv1 meaning nvflashable.
What app did you use to get into recovery causing the "brick"
Can you still get into cwm recovery, ect.
you still have hope if ADB can see it, try to update your driver.
If it work use ADB to push the file you need.
Sorry for wrong thread.
I probably have SBK2 (how to check) because usb just disconnects as soon as I try to run any nvflash stuff.
I also believe that ADB could be the saviour but it says offline. So this could be due to driver issue? Interesting, I shall try on a 32 bit computer.
If I suceed to connect through ADB, can I then flash CWM recovery?
The app I used to get into recovery was just a random boot into recovery app. It worked many times before. I don't think taht app caused this, maybe the recovery files where deleted?
df9517 said:
Sorry for wrong thread.
I probably have SBK2 (how to check) because usb just disconnects as soon as I try to run any nvflash stuff.
I also believe that ADB could be the saviour but it says offline. So this could be due to driver issue? Interesting, I shall try on a 32 bit computer.
If I suceed to connect through ADB, can I then flash CWM recovery?
Click to expand...
Click to collapse
You can use SBKdetect to check your SBK version (linux)
Did you have CWM before? Are you rooted?
What is your tablet doing right now? Stuck at the start up screen?
My tablet was previously running rooted ICS WW .11 with CWM.
Now its just stuck at the first boot image. I can go into same image where it tries to run recovery image by holding vol down. I guess it is standard brick.
Not getting anywhere with ADB, device is offline
hmm.. can you cold boot? just hold vol-down and wait?
df9517 said:
Not getting anywhere with ADB, device is offline
Click to expand...
Click to collapse
Search on here for the universal naked driver. Try that or sometime if you can try a different usb port.
Can you get into CWM Manually?
Hold VOL DOWN and POWER for about 10-12 seconds until some small text appears.
Quickly (within 5 seconds) release both buttons and hit VOL UP to enter RCK (Recovery).
If you can get into CWM this way you should be able to clear some caches and see if it will boot. If need be, you may be able to flash a new ROM if need be.
I only got the naked ADB drivers to work. The real ASUS ones does not work. Only tries 64 bit though.
Of course I tried to go into recovery manually.
Actually I now remember that just before this happened I updated CWM through the clockwork app. Probably updated to a version that does not work.
Since you have ADB working, download a CWM flashable .zip from your favorite recovery thread and extract the recoveryblob.
adb push it to /temp/dd or something similar, then run adb shell, su, and (you will need root/busybox on here) dd if=/your/blob/here of=/dev/block/mmcblk0p4.
after running that, run reboot, you should see a blue line and be able to get into a good CWM recovery. never use rom manager.
Thing O doom.
It always says my device is offline using ADB. I have only got naked driver to work.
But now I saw the NVflash for B70+ devices in your post. I will try that tonight.
I have not given up.
Yes, that is probably your only hope if you can't get ADB working, and it just came out! Lucky day
Yes, thank you all!! Finally NVflash for B70+ devices saved my day. Reflashed original ROM.

[Q] Soft bricked A200

Do not see a section for the A200..... Someone in A100 said I'd have better luck here.....
OK, so I soft bricked my A200 and need to USB connect to it, so I can use fastboot or some other recovery tool.
Problem is that when I plug the A200 into my computer, it grinds away for a bit then gives a driver failed to install red "X" message.
I've reloaded the Acer USB drivers a couple of time, but no joy there. I've tried two different computers, I've tried XP and W7, nothing seems to help. Looking in the device manager shows an error 10 (device can't start).
Since the PC at least recognizes the A200 when plugging in, I think if I can get the USB talking I can easily unbrick the A200.
When I power it on, it boots to the IconiaTab screen, but no further. It's been rooted and bootloader unlocked using HBWelch's Simple Tool. I can get into fastboot mode by using a convoluted (to me, at least) procedure, that takes 6 fingers to accomplish.
After rooting and UL'ing BL it worked fine for over 6 months. Tried to flash back to stock over the weekend, and that's when I bricked it.
I posted this same message over on Acertabletforums, but so far no response's. Moderator, if you don't mind, please merge my other thread over in the A100 section with this thread.
Help??
Boowho??
Do you know if CWM is available for your A200 ?
If your bootloader is unlocked, i think you can flash a boot or recovery via Fastboot
success anyThan
Shreps said:
Do you know if CWM is available for your A200 ?
If your bootloader is unlocked, i think you can flash a boot or recovery via Fastboot
Click to expand...
Click to collapse
Fastboot appears to need a working USB connection (thru drivers). When I run it on the PC, it hangs with the message "waiting for USB connection". This is with the tablet booted in "fastboot" mode.
I CAN get it to read from update.zip on the SD card. The update.zip I'm using is the completely stock firmware (ROM, recovery, etc).
It starts the update (Android with spinning wire frame ball), gets about 25% done and then the update fails with the "dead android" symbol.
Thanks
Boowho??
Problem solved..... Thanks. Was able to flash via update.zip on SD card.
One damn thing after another!!!
boowho said:
Problem solved..... Thanks. Was able to flash via update.zip on SD card.
Click to expand...
Click to collapse
Everything did work fine for a day. Now I cannot enter recovery using the hardware buttons.
Using an APK called "Quick Boot" I can easily boot into CWM from the home screen and everything is fine. Root is fine, bootloader unlocked properly, etc.
Everything acting as I would expect.... BUT....
Unfortunately, not being able to enter recovery from HARD boot pretty much makes any recovery worthless, right??
Anything besides hardware that could be causing this?? The volume rockers work just fine as volume controls.
Thanks
Boowho??
This problem solved too....... Brainfart!!!
Boowho??

One S dead after trying to flash CM11

Hi there,
i have a huge problem. As there was no warrenty left for my One S I thought about to change the firmware to CM11.
I have to admit that i don't have any experience in doing such things, but i thought, it couldnt go wrong if i follow a tutorial.
So at first i unlocked the bootloader via HTC website and istalled TWRP 2.7.1 (latest version). Everything went well, I placed the ROM into the phones root directory, started the recovery and then whiped it before choosing install and selected the file. After about 30 seconds the phone reported the step was successful and i pressed reboot. Then there was the HTC starting screen and then a black screen.
After that i had no reaction but the blinking buttons when i press the power button for a longer time. But it changes nothing. No normal boot. No access to fastboot. Only if i connect it to my PC there is an aditional device to see, but whitout any access.
I know I did wrong but i have no idea what or how to fix it. I hope you can help me.
ElDorado1993
Now i found a way to get access to fastboot again, but i dont really know what to do now.
Can you give me an detailed tutorial, for jelly bean or kitkat (dont matter) that is surely working now?
My main problem is that i can't copy my files into the root directory as i cant boot the phone.
Does it show up in computer connected devices?
If it does, download stock kernel and ROM and upload to phone and go into recovery[power +volume up while off] and flash them both kernel first.
Sent from my ZTE_N9511 using XDA Free mobile app
The problem is the phone wasnt ever shown as device on the pc (like a flash drive) since version 4.1 so I allways needed some tricks like airdroid. So i suppose i need adb commands to copy files and i dont have so much experience in doing this.
Do you know how to use adb?You don't need adb I just wanted to know to see if it shows up there and not on computer you simply need to install the drivers.Try holding down all 3 buttons to see if it powers down. Do what it says http://www.technewscentral.co.uk/enter-fastbootbootloader-mode-htc-one/id_7930 if works go into fast boot. Does it say locked or unlocked. If unlocked go herehttps://github.com/koush/UniversalAdbDriver and get the windows installer if your on windows.
Sent from my ZTE_N9511
I now found out how adb and fastboot are working, but the main problem now is, that it says the sdcard cant be mounted. I tried this tutorial http://forum.xda-developers.com/showthread.php?p=25557817#post25850720 but i dont know how to do the first step. Du i need an extra file and where do i get it from and how to use it. As long as i dont get back this access, i couldnt install any OS. I tried also sideload. It was able to copy but cant install because of the missing sdcard access.
I hope you can help me to become my phone running again.
Go here http://m.youtube.com/watch?v=xWmnHwkDrKk but first type adb devices in cmd. If it shows ur HTC type adb shell and and type mount sdcard next to the "#" once it appears although you should be using the fastboot shell not adb commands.adb should only work on a powered on device or you can use fast boot in cmd while phone is in fastboot not recovery(you did say the phone can go into fast boot right?). Just make sure you got the right drivers and both fast boot and adb. You should get Koush's Universal drivers from my previous post since some phones have multiple drivers and MAY cause problems with cmd. Also HTC one S doesn't have expandable storage correct?
Sent from my ZTE_N9511
Wow. Now I incidentally soft bricked my phone again if you would believe it and nothing works this time.
Have you been able to fix?
Sent from my ZTE_N9511
Okay, i forgot to write but adb and fastboot are working on my Mac. I use the Mac because Win 8.1 has the known driver problems.
I tried a lot now, but i recognized maybe the main problem. My phone is still S-ON in bootloader. For sure thats the problem. Do I need to get rid of it and how do I do. The tutorial i used hasn't mentioned this step, maybe the person was still S-OFF.
The first thing i try now is to flash the original recovery, lock the bootloader and execute the original signed RUU to get back the original software first. Im going on holiday on tuesday and it would be a pitty without the phone. When I get it working i will leave it, and thy it again, when I'm back. Otherwise.......****
Use this tutorialhttp://htc-one.wonderhowto.com/how-to/fix-soft-bricked-htc-one-by-flashing-new-rom-via-adb-0154361/unless its the one you used already. From boot loader you were supposed to have gone to fastboot.boot loader has to be unlocked.From fast boot you flash TWRP.IMG which happens to have a special adb side load feature under advanced options. There you upload another ROM and kernel.here is the full list of supported devices as I don't know what variant or carrier you havehttp://teamw.in/twrp_view_all_devicesAlso, a stock kernel is optional but it always seems to fix my problems.
Sent from my ZTE_N9511
Thank you. But I already did it like this. The issue is, than after using sideload successfully the installation fails because of the known "unable to mount storage" text. And i don't know what to do wrong.
Like I already said, my phone is still S-ON, but can this make a difference?
Now i got it to bring the stock ROM running again, and as I'm on holiday for a few days I'm happy it is working again.
But one thing is left. It seems like there is no 3G/HSDPA connection now, only EDGE. I dont know what went wrong. Did you hear about this problem.
By the way, my phone is the standalone version whithout any provider.
Search the forums about edge only. There is a huge thread on this.

Categories

Resources