Database Info

[Q] UK 3G Xoom - Possible brick? Bootloop after Moray update.

Never like to have to resort to posting myself but I've had a decent look around the web and can't seem to find a solid solution to my problem so I'm hoping to get some specific help
So I have a UK MZ601 3G Motorola Xoom which was happily running Moray 2.2.1 and had been rooted using the universal root method. Decided to update to 2.2.2 and now my Xoom is stuck in a boot-loop on the custom rippling water boot animation.
The tablet hangs on the first line when trying to boot into recovery so for all my efforts cannot access CWM and perform a hard reset and fresh rom install.
I've tried - and I'm assuming I'm correct in thinking this means I cannot get the Xoom to any stage where I can use adb to attempt to get in to recovery or push files to the system etc. this way.
From what I've read on other forum posts - booting holding volume up and power puts the device into an 'RSD' state which is another method of reflashing the device? I've read this requires an 'SBF' file - which I have seen for download - but believe it only works for the US models?
I've left the boot screen looping overnight - so its not an issue of it just being slow. Because of the custom boot screen I obviously can't return it to the shop as I presume its an obvious warranty void?
Would massively appreciate any help in bringing whats looking increasingly like a £500 paper weight back to life.
Thanks

crozuk said:
Never like to have to resort to posting myself but I've had a decent look around the web and can't seem to find a solid solution to my problem so I'm hoping to get some specific help
So I have a UK MZ601 3G Motorola Xoom which was happily running Moray 2.2.1 and had been rooted using the universal root method. Decided to update to 2.2.2 and now my Xoom is stuck in a boot-loop on the custom rippling water boot animation.
The tablet hangs on the first line when trying to boot into recovery so for all my efforts cannot access CWM and perform a hard reset and fresh rom install.
I've tried - and I'm assuming I'm correct in thinking this means I cannot get the Xoom to any stage where I can use adb to attempt to get in to recovery or push files to the system etc. this way.
From what I've read on other forum posts - booting holding volume up and power puts the device into an 'RSD' state which is another method of reflashing the device? I've read this requires an 'SBF' file - which I have seen for download - but believe it only works for the US models?
I've left the boot screen looping overnight - so its not an issue of it just being slow. Because of the custom boot screen I obviously can't return it to the shop as I presume its an obvious warranty void?
Would massively appreciate any help in bringing whats looking increasingly like a £500 paper weight back to life.
Thanks
Click to expand...
Click to collapse
When you press volume up and power, and hold it, it reboots, yeah? Then you wait about three seconds on dual core screen and tap volume down...what happens then? Do you see android recovery in upper left? Or starting fastboot protocol? Where does it hang? Just trying to see where things are going wrong. If you can get into starting fastboot protocol you are in good shape. If you can get into cwm recovery you should be in great shape. Check out the Xoom Heaven thread in General for some info on recovery.
You are most likely far from bricked...almost all of us have recovered from worse situations than you are in now so just keep cool.

okantomi said:
When you press volume up and power, and hold it, it reboots, yeah? Then you wait about three seconds on dual core screen and tap volume down...what happens then? Do you see android recovery in upper left? Or starting fastboot protocol? Where does it hang? Just trying to see where things are going wrong. If you can get into starting fastboot protocol you are in good shape. If you can get into cwm recovery you should be in great shape. Check out the Xoom Heaven thread in General for some info on recovery.
You are most likely far from bricked...almost all of us have recovered from worse situations than you are in now so just keep cool.
Click to expand...
Click to collapse
Thanks for your reply - tried numerous times getting into recovery - get stuck with one line of 'starting fastboot protocol' and seems to hang there.
Have experience rooting and flash etc. and have obviously used adb in the past.
If I could just get to recovery - or a state where I could use adb I would be fine. But as I said in my first post - looks like I can only access an 'RSD' state.
Is there any other way of getting adb access from my PC? All the help for bricked xooms seems to concern US models - and don't want to try anything that will completely write it off!
Thanks again for your help.

Quick update -
Have retried Fastboot - stuck on 'Starting Fastboot protocol support'
Tried Android Recovery - got stuck on a black screen for a long long time but finally booted!
Wiped and re-installed what I know to be a kosher ROM! Was a scary moment there but thanks for your help and reassurance!

crozuk said:
Quick update -
Have retried Fastboot - stuck on 'Starting Fastboot protocol support'
Tried Android Recovery - got stuck on a black screen for a long long time but finally booted!
Wiped and re-installed what I know to be a kosher ROM! Was a scary moment there but thanks for your help and reassurance!
Click to expand...
Click to collapse
If you are still rooted and all, just for safety's sake, make sure to do another nandroid backup and save it to your micro sdcard. Backup, backup, backup. Then also make sure that you have a compatible cwm recovery installed, that will let you access your microsd card. It sounds like you're alright, so, cool.

[Q] Anyone else having issues with custom roms? My rundown of steps.

People that can't get the roms beyond stock to work, are your phones activated?
Is it possible to use the Pac Man Rom or CM10 on an unactivated phone?
I'm having similar issues to others trying to flash Pac Man and CM10.2. The first boot was fine and I can access everything on the phone fine, including settings. I rebooted and the activation screen (which I skipped as this phone doesn't have service) always pops up but I would like to use it without putting it on a cell network. I can skip the screen fine (until I decide to disable it) but then have issues like the keyboard (physical and touch), systemUI or NAV Bar crashing with a constant message pop up telling me it has crashed. I have returned to stock using RSD and reflashed Pac Man and CM10.2 MANY (15+?) times, doing a clean install 99% of the time but also trying a couple dirty installs to cover my bases. I should also note that I flashed the phone to Cricket but have no plans to activate it anytime soon.
Another thing to note is that I had issues getting the custom roms to boot at all as the initial setup would take hours. One time I though it was a boot loop but I left it on all night and it had booted in the morning. I believe it has something to do with the file check at boot (with my 32GB low speed class SD card) but that seems to be resolved and I can get the custom roms to boot fine (on the first boot) even with my 32GB (witch is fine and has no errors nor is generic, before you ask.) I also have tried 2 4GB cards and a 2GB card, all different brands, with no change in behavior.
I have done everything below multiple times and in different orders.(If needed I can give a direct breakdown step by step but if you could do it with the files below, I have probably tried it)
Wipe the phone (including all storage internal and external SDs included)
Using RDS v6.15
RDS asanti_c_sprint-user-4.1.2-9.8.2Q-122_XT897_FFW-5-6-release-keys-cid9.xml.zip (Works 100% of the time and never has issues. I keep reverting back to this if I actually need to use the phone)
RDS ClockworkMod, TWRP, and Open Recovery without TWRP (Tried different versions when available)
Then used each recovery to install Pac Man or CM10.2 (tried 10.1 once but had the same issues and I didn't see the need to troubleshoot a rom people seemed to not want to develop for. So 10.1 was only tried once but has the same issues)
Installed GApps at this point but I also tried alternate versions of GApps and not installing it at all. All have the same effect and don't seem to be contributing to the problems at all.
A few installed I tried wiping the phone again or installing each zip multiple times. I also verified the zips were good when on the device to make sure there was no corruption at transfer.
I also tried multiple (confirmed working) SD cards and installing from the internal storage.
I have tried installing arrrghhh's Kernel too.
The issue ether seems to be boot loop (if it's doing a file check) or more often it works until I get one of the said crashes after a reboot.(blame Tyler message is getting SO old...) The time I see the errors seems to be accelerated if I mess with the settings a lot but I don't believe it is directly related to the settings.
My next recourse is to try and flash it back to Sprint (maybe check my Cricket settings) and see if that helps, without it being activated.
On a separate note.
If people need help I can help get you back to stock easily. The instructions/guides on here are all but useless if you don't know what you are doing already. I have seen down to "USE RDS" or "DELETE LINE MD5" like people would just know what that means. I understand RDS Lite is a standard tool for flashing phones but it's nigh impossible to find real explanations on what stuff does in context. I understand the basics though, so if anyone has any questions I can walk you through it.
To start with if you are stuck in a loop at the start of a new rom and it loops between the 'Welcome' Screen (Select your Language) and Activation screen just skip the initial setup by tapping the corners on your screen in a clockwise manor when on the 'Welcome' screen to skip the setup there is a video to explain it here
pocketnow(can't post links )com/how-to/android-quick-tip-how-to-bypass-touch-the-android-to-begin-video
Without doing this or activating the phone it seems to loop between those 2 screens forever (might indicate part of the problem with customs roms....)
I hope this is enough info to go off of I can give you a play by play with the actual files if you need. Maybe a video if needed and I'm feeling extra fancy.
Thanks for your time.

Hey buddy,
If you're trying to make a guide, make sure you call it what it is properly - RSD Lite.
Also, maybe clean up your post a bit so it's a proper guide (as you point out, it's needed) and make a separate thread for your question.
To answer your question, the unactivated phone shouldn't be an issue in of itself - you'll just get the nag screen like you were talking about.
I know there is an issue some are having with rebooting the 4.3 ROM's. Have you tried any 4.2.2 versions of anything? Carbon, CM10.1?
I wonder if your "flash" to Cricket is causing issue, I'm not sure. Let me know about 4.2.
Edit - I missed this part on my first read of your PM. Taking hours to boot is NOT normal. Perhaps remove the SD card entirely, flash using the internal SD... I've never heard of that. Anything over say 20 minutes is probably cause for concern.

Thanks for taking time to answer me.
In no way was I trying to make a guide yet but I guess I could. I just hate posting stuff without useful content so I figured throwing that in was better than nothing. I'll clean it up and set up some links later today. It's frustrating to try and make a full guide before I can post links that would be needed for it. You are totally right though! (complain about crappy guides and kind of make one... )
Part of my point there was that I can't post out of Q and A and this wasn't really a question so I made a question out of it and that's how my post ended up.
I have flashed many phones before but like I said I'll try and put it back on Sprint later today (probably will be a few hours) as I backed up the settings the phone came with. I know it was a wall of text and not the easiest to read so you probably missed it but I also said in my first post that I tried the internal SD card many times and the taking hours to boot isn't the standard and doesn't seem to happen at 99% of the time. It seems to be related to the recovery software I use as it happened a lot more when I was testing TWRP and none when I use clockwork.
What Recovery do you recommend? I swear they aren't made equal...
I tested CM10.1 once and it had the exact same issues as CM10.2 and Pac Man so I didn't test it further but if you want me to test it I can. I just didn't want the Rom.
I don't want Carbon either but I'll test that and AOKP next. It's just annoying that the stock rom works perfect but I can't get these to function at all. I almost wish I didn't get Pac Man to work at all. I'm very particular about my settings and NEED these features after I tried them Pac Man is AMAZING.
Thank you for the help and I hope I can get this worked out.
PS I saw that you were frustrated about working on a rom you don't have a device for. I hope you don't let a little thing like that stop you as, for the little time I have used it, it's all I want. Thanks again.

Blasz said:
What Recovery do you recommend? I swear they aren't made equal...
Click to expand...
Click to collapse
Well, OpenRecovery has probably the most work done for this device specifically. I liked TWRP, but it seems lately it has been unstable - you're not the first who has reported issues lately. I don't think CWM has been updated, unfortunately - but perhaps that's a good thing, it's stable that's for sure.

Blasz- I was just about to start a thread when I found yours, and it very accurately describes the issues I've been having. Here's my progress so far.
I got my Photon Q with Sprint and used it for a few months before Sprint started finding creative ways to take my "$79.99" bill and make it more like $140 a month. Naturally, I refused to pay. So I had a Photon Q with no cell service. This is fine, as I only need it to work on WiFi, not 2G/3G and there is no 4G in the area. Anyway.
At the time, I had Ice Cream Sandwich on it, using the (latest?) ICS firmware from Motorola. This worked very well, but I later tried to use a newer firmware, and all the custom ROMs had shown up while I hadn't been looking. All of these seemed to be based on JellyBean. First off, I tried CyanogenMod 10.2. Worked amazing well! I had literally no problems at all. However, while I was experimenting with different software for the phone, and wanted to see if "Arrrgghh"(sp?)'s kernels would give me some decent overclocking capability. Turns out, the kernel I picked wasn't compatible with the JB firmwares (I probably picked an older one by mistake.) Needless to say, it now wouldn't boot. It'd go to the "Unlocked bootloader" screen and stay there all night (literally, I tried that.)
So, I went back into CWM, which is the recovery I have installed. I erased /data, /cache and /system, and also the dalvik cache and battery stats for good measure. I also formatted /pds and /modem, I believe, which was probably dumb of me since I'm not sure what those do. Then I tried re-installing CM 10.2 from CWM. The installation went fine, and it works gorgeously. However, there's two weird issues:
1) WiFi and Bluetooth don't even BEGIN to work! Neither does Cell, as far as I can tell, because where CM used to be unable to make calls or access the internet (of course, I've not been paying my bill), it now shows an empty signal bar or "No Signal" (the little red X) in the notification bar ... When I try to turn on WiFi using the slider in Settings, it moves to "ON" (stays gray) and pauses for a few secs, then goes back to OFF. Same thing for BT. If I open the WiFi menu where you select an AP, it tells me to turn on WiFi. I do, using the slider up top, and the same thing happens. WiFi and BT simply won't turn on. Tried fiddling with every setting I can find.
Before this misadventure with the kernel/reinstall, WiFi worked great. I connected to a local AP and was surfing the net and downloading apps.
2) The system takes a VERY long time to boot up. It sits at the "Unlocked Bootloader" screen for up to a whole minute. Then it goes to the Cyanogen screen for about 30 seconds. Then it gets to the homescreen. It's fine so long as you let it boot up, but this doesn't seem normal.
Next I tried other ROMs thinking that might help. I installed AOKP, PacMan, CM1.0, Carbon, SlimBean, and I think a few others without results-- they all work but WiFi and BlueTooth are dead. PacMan is the only exception-- it boots up and then endlessly gives me "Blame Tyler" errors until I force the machine to shut off.
I also tried an older ROM, since these are all JellyBean ROMs and I wanted to get back to ICS (I'm not that fond of JB's interface) anyway. I was unable to find any ZIPs I could install through CWM of the stock firmware. I found some IMGs that it looks like I could install via Fastboot, but I don't currently have a PC with admin priveleges (it's not mine) so I can't install the drivers to use Fastboot or any part of the SDK. (I can, however, put files on my SD card, that doesn't require privleges.) The closest ROM I found to stock was "TwistedAsanti" beta-1 or whatever it's called. That installs fine, but again, it takes about 2 straight minutes to boot and it's useless after that:
It gets stuck at "Starting Services..." and will sit there forever, even left there all night. Behind this, a dialog pops up saying no cell networks were found and asking if I want to switch to GSM. (i've been trying GSM and CDMA ROMs all this time, I don't need cell access so I doubt it matters which I use. I'm in the USA.) You can pull down the notification bar and get into the Settings, and even launch a couple programs, but I can't find ANY way to get to a homescreen. Task manager shows Circles is running, which is a widget on the homescreen, so where the heck is that screen? .. I try, again, to turn on WiFi or BT without success. The friggin thing just won't turn on.
Did I eff it up by erasing the "PDS" or "modem" partition? Am I missing something obvious or is my phone just possessed?
In a few days I should have access to a computer where I can hopefully use Fastboot and see about installing a stock firmware (wish me luck). Until then, does anyone have a ZIP file I can flash from CWM to get back to an ICS firmware? I managed to find a copy of the stock firmware, in the form of a dump done from TWRP (in .win files). But as far as I know the only way to install TWRP is using Fastboot, and I've explained why I can't do that. I don't know a way to install TWRP from CWM. Maybe I can do it from CM10.2, if I can put APKs or something on my SD card. I can't get it on the network, so I have to copy all the files manually. Needless to say, it's a pain.
After my frenzy of ROM installing, I got frustrated and decided to see if TwistedAsanti would do SOMETHING if I let it sit at "Starting Services" overnight. To my mistake, I left it under my pillow and the system was quite toasty, and the battery had run dead. Plugging it back into the charger, it made a few worrying clicking noises from the speaker, then the green LED came on. This LED seems to mean "I'm charging, but the battery is too dead to turn on for a while." After it sits there a while, the green LED turns off and it just goes black. Or it goes to BOOTLOADER UNLOCKED and bootloops, or goes to black untilyou fiddle with the power button some more. I can once in a blue moon get to CWM. Sometimes it gets to the homescreen. It will charge up to about 4-7% and no further (battery got damaged by the heat?) It doesn't reliably work when plugged in, it likes to shut off at random anyway.
So now I'm stuck with a phone I can't seem to charge, or turn on reliably, and if I *do* get it to boot up, there's no way to connect it to a network.
Needless to say I'm pretty darn frustrated..
Thanks for any advice.

Epicenter714 said:
So now I'm stuck with a phone I can't seem to charge, or turn on reliably, and if I *do* get it to boot up, there's no way to connect it to a network.
Needless to say I'm pretty darn frustrated..
Thanks for any advice.
Click to expand...
Click to collapse
Did you try to use RSD Lite and flash the device back to stock?

arrrghhh said:
Did you try to use RSD Lite and flash the device back to stock?
Click to expand...
Click to collapse
Currently, I have no PC to use that has Admin priveleges, so I can't install the USB drivers or RSDLite. I also can't use fastboot to install TWRP to use the TWRP .win backups I found.
I did get a roommate to let me use his laptop for 10 minutes to try RSD Lite, but I had this result: Loaded the ".xml.zip" file for the 4.0.4 and 4.1.2 firmwares (after removing the 'getvar' line that causes problems) and it says the phone reported "FAIL". No further details. MiniRSD gives no info from the phone other than the model (it all stays blank), is that supposed to happen? I have the phone in "AP Fastboot" mode so I don't see the problem.
The guy who let me use his PC momentarily is computer-illiterate and thinks anything will break it, so he only let me use it momentarily, and won't let me touch it because I accidentally left an icon on his desktop. I'll have to ask someone else, I think I may know somone..
If I do, how do I get around this error in RSD Lite? Will keep doing research on my own .. thanks!

Epicenter714 said:
Currently, I have no PC to use that has Admin priveleges, so I can't install the USB drivers or RSDLite. I also can't use fastboot to install TWRP to use the TWRP .win backups I found.
I did get a roommate to let me use his laptop for 10 minutes to try RSD Lite, but I had this result: Loaded the ".xml.zip" file for the 4.0.4 and 4.1.2 firmwares (after removing the 'getvar' line that causes problems) and it says the phone reported "FAIL". No further details. MiniRSD gives no info from the phone other than the model (it all stays blank), is that supposed to happen? I have the phone in "AP Fastboot" mode so I don't see the problem.
The guy who let me use his PC momentarily is computer-illiterate and thinks anything will break it, so he only let me use it momentarily, and won't let me touch it because I accidentally left an icon on his desktop. I'll have to ask someone else, I think I may know somone..
If I do, how do I get around this error in RSD Lite? Will keep doing research on my own .. thanks!
Click to expand...
Click to collapse
Well remember - if you are on JB and you are downgrading to ICS, there are additional lines to remove.
Other than that, not sure why it would fail. Make sure 'fastboot devices' works in the command line before doing RSD perhaps.

arrrghhh said:
Well remember - if you are on JB and you are downgrading to ICS, there are additional lines to remove.
Other than that, not sure why it would fail. Make sure 'fastboot devices' works in the command line before doing RSD perhaps.
Click to expand...
Click to collapse
I'm trying to wipe the device clean and install ICS. Are there any other lines I need to remove? ..
As for Fastboot.. I did 'Fastboot Devices' and got no devices listed. How come it shows up in MiniRSD? .. I have the drivers installed, Windows says it installed an ADB device successfully. What are some reasons that might not work? Is there any sort of guide for this? Thank you
---------- Post added at 05:51 PM ---------- Previous post was at 05:29 PM ----------
Oh, as far as the weird booting problem, it seems the battery is fine and the charger died coincidentally at the same time as the overheating did. So my only problem is software now.. thanks.

Epicenter714 said:
I'm trying to wipe the device clean and install ICS. Are there any other lines I need to remove? ..
As for Fastboot.. I did 'Fastboot Devices' and got no devices listed. How come it shows up in MiniRSD? .. I have the drivers installed, Windows says it installed an ADB device successfully. What are some reasons that might not work? Is there any sort of guide for this? Thank you
---------- Post added at 05:51 PM ---------- Previous post was at 05:29 PM ----------
Oh, as far as the weird booting problem, it seems the battery is fine and the charger died coincidentally at the same time as the overheating did. So my only problem is software now.. thanks.
Click to expand...
Click to collapse
I have no clue what MiniRSD is - you mean RSD Lite?
If it doesn't show up in fastboot devices, sort that out before trying to use RSD.
As I stated previously, if you were on JB and going down to ICS you have additional lines which are needed to remove.

Yes, RSD Lite. I don't know where I got MiniRSD from.
I got it to show up in fastboot devices, but adb devices doesn't show it. Weird. Is that OK?
I was able to flash TWRP to the phone with Fastboot. RSD Lite was unable to find the phone. However, I opened the XML file and was able to figure out the flash commands to enter from a command prompt, so I did that:
I got these results... all of the files flashed successfully to stock, except for two. I forget the first, haven't got it in front of me, but here's the big one: SYSTEM! (Important, no?) Here's the error from fastboot:
>> fastboot flash system system.img.ext4
fastboot said:
target reports max download size 31457280 bytes
Invalid sparse file format at header magi
Click to expand...
Click to collapse
(then, Fastboot crashes.)
Does anyone know how to fix that? Also, the system image is way bigger than 31.4 MB. What is it talking about?
Thanks!

Epicenter714 said:
Yes, RSD Lite. I don't know where I got MiniRSD from.
I got it to show up in fastboot devices, but adb devices doesn't show it. Weird. Is that OK?
I was able to flash TWRP to the phone with Fastboot. RSD Lite was unable to find the phone. However, I opened the XML file and was able to figure out the flash commands to enter from a command prompt, so I did that:
I got these results... all of the files flashed successfully to stock, except for two. I forget the first, haven't got it in front of me, but here's the big one: SYSTEM! (Important, no?) Here's the error from fastboot:
>> fastboot flash system system.img.ext4
(then, Fastboot crashes.)
Does anyone know how to fix that? Also, the system image is way bigger than 31.4 MB. What is it talking about?
Thanks!
Click to expand...
Click to collapse
I would NOT recommend entering those fastboot commands in the XML file manually unless you KNOW what you are doing.
Sort out why RSD isn't working. adb and fastboot are two different things. If fastboot devices shows the device, RSD Lite should work fine. Try again.

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.

Need some guidance on stock-flashing my moto g3 from cyanogen

So I wanted to see how my phone would be in stock firmware / software for a while to use some streaming services flawlessly for a while. The problem is the guides to do so dont seem to be working with my Cyanogen Recovery.
When I try certain guides that recommend using Fastboot or Mfastboot , the device is not authorized or recognized outside of Apply update> ADB sideload. Im guessing its because i need to activate USB debugging. The problem is i already factory reset so the only thing in the phone right now is last weeks NGHTLY mod, and I cant open debugging options without settings freezing. So im technically locked out of USB debugging menu in the phone because it freezes.
I tried loading a few different Zips to see if the phone would take ANYTHING (follow a few guides) and none of them work. A white word saying "error" pops up. I remember one time one of the errors said "footer is wrong".
Anyone have any ideas or run across this situation before? Id be willing to start over with things i've already tried to give you detailed answers about any errors i run into but id appreciate the hand holding since Im generally lost when the guides stop working and I barely have any error messages to google off of.
TLR INFO
Phone: Moto g3 2gb ram 16gb storage (1540)
Cyangenod Recovery
I can get into bootloader
I can get into Cyanogenmod recovery but get a white text saying "error" when loading zips.
I can load the phone with last weeks NGHTLY mod but i cant access USB debugging because the phone seems to freeze when i access develoption options. Almost like its loading insanely slow.

I would suggest factory image here
http://forum.xda-developers.com/201...to-g-factory-firmware-images-t3169639/page160
However I've never used cm recovery.
You could try the more versatile TWRP recovery, and may have better luck with whatever you are trying to do

hossman said:
I would suggest factory image here
http://forum.xda-developers.com/201...to-g-factory-firmware-images-t3169639/page160
However I've never used cm recovery.
You could try the more versatile TWRP recovery, and may have better luck with whatever you are trying to do
Click to expand...
Click to collapse
yeah thats the problem. whenever i load one of these it just says error and stops. ill google how to load twrp recovery and see if i have better luck
edit: this is my issue mainly. i cant enable usb debugging so i cant do the CMD commands to install things like TWRP recovery. do you guys have any alternative to that? Im looking things up in google without much luck
edit: so this is as far as ive gotten since im forced to use this cyanogenmod recovery. no matter what i try to run i get "Verification error" and if i try to install Gapps i get "error 20" and i still cant access usb debugging because it freezes. Any idea on a fancy way to get around this verification issue? Guides suggest using a different recovery but it doesnt seem possible without the google play store or USB debugging.

yeah im not able to do anything without getting verification errors and without a different recovery i cant seem to disable it. hope someone has a direction to point me in.

http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
recovery isnt used since its being updated itself.. duhh
go to bootloader and fastboot flash the firmware files
follow the tutorial above /\

HelpMeruth said:
http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
recovery isnt used since its being updated itself.. duhh
go to bootloader and fastboot flash the firmware files
follow the tutorial above /\
Click to expand...
Click to collapse
oh cracker jacks that did it. im so dumb. whats worse is sometimes i think about learning a programming language and then i see stuff like this and recognize absolutely none of it and just say "forget it.". thanks for the guidance man. if theres something i can do other thank hit the thanks button let me know, you guys are like the free clinic of the internet.

Help for my SM-P900

Hi everyone,
I'm hoping that someone can help me out with my device. I have a rooted sm-p900 that was working fine until a month ago when I tried to flash [ROM][7.1.x|SM-P900| Unofficial LineageOS 14.1 (v1awifi). I was busy multi-tasking and made the stupid mistake of flashing the rom before updating the BL. Since trying to do so, I have not been able to get past the first screen that says "Samsung sm-p900" . After the logo disappears, my screen remains lit but is just black.I could not restore my backup after either.
Where I am now:
- I can still access and use T.W.R.P. (latest 3.1.1) (If TWRP is left alone for too long, the device will reset to the same black screen and hang forever. If flashing a rom is taking long, the device will restart mid-flash as well.)
- I can still access download mode and use odin as well.
- I have since flashed the appropriate BL but that has not changed anything.
-I have tried clean flashing a magnitude of different roms and still come across the same problem.
I honestly have no idea how I can fix the device and have tried everything I know how. I would love to get it back as soon as possible. Any help is greatly appreciated, so thank you in advance!

jp2572 said:
Hi everyone,
I'm hoping that someone can help me out with my device. I have a rooted sm-p900 that was working fine until a month ago when I tried to flash [ROM][7.1.x|SM-P900| Unofficial LineageOS 14.1 (v1awifi). I was busy multi-tasking and made the stupid mistake of flashing the rom before updating the BL. Since trying to do so, I have not been able to get past the first screen that says "Samsung sm-p900" . After the logo disappears, my screen remains lit but is just black.I could not restore my backup after either.
Where I am now:
- I can still access and use T.W.R.P. (latest 3.1.1) (If TWRP is left alone for too long, the device will reset to the same black screen and hang forever. If flashing a rom is taking long, the device will restart mid-flash as well.)
- I can still access download mode and use odin as well.
- I have since flashed the appropriate BL but that has not changed anything.
-I have tried clean flashing a magnitude of different roms and still come across the same problem.
I honestly have no idea how I can fix the device and have tried everything I know how. I would love to get it back as soon as possible. Any help is greatly appreciated, so thank you in advance!
Click to expand...
Click to collapse
Have you tried taking it completely back to stock via Samsung Kies on your PC?
Sorry I don't have complete details, but it goes something like this (and if you search this site or Google, you'll find a good write-up on how to do a complete recovery using Kies):
1. If you can, make a backup using TWRP - if not, you are going to lose everything because of the next steps
2. Download and install the Kies software from the Samsung site and install it on your PC (I grabbed both versions, can install both on the same PC at the same time)
Make sure that it installs the Samsung USB driver
3. Connect to the tablet using the OEM cable - if you get a reaction from Kies, great
4. Somewhere in the Kies menu, you can tell it to do a complete recovery, including bootloader- if I remember correctly, you'll need your serial number (Sorry, been 18 months since I did just about the same thing and was able to recover it from my FUBAR, and I no longer run Windows so I can't step thru it)
It will go through downloading and flashing your tablet back to the state it was when you pulled it out of the box.
If you get to that point, you will have to go the whole route (including loading TWRP) to get it back to Lineage. It took me about two weeks to get it back to the way I had it before I was flashing and reading a book and talking to my wife all at the same time and didn't pay attention to what I touched on screen.
I apologize for the rambling and not having definitive statements, but I'm drugged up and been awake for the last 36 hours, and at my age that isn't a good combination.

Thank you so much for your help! I couldn't end up using that method because kies would not recognize my device for anything. It did get me inspired to try fixing it again however and it worked!
If anyone ever encounters the same or a similar problem, I just tried re-rooting it using odin and cf's autoroot file. It allowed me to be able to install roms again.
rhricik447 said:
Have you tried taking it completely back to stock via Samsung Kies on your PC?
Sorry I don't have complete details, but it goes something like this (and if you search this site or Google, you'll find a good write-up on how to do a complete recovery using Kies):
1. If you can, make a backup using TWRP - if not, you are going to lose everything because of the next steps
2. Download and install the Kies software from the Samsung site and install it on your PC (I grabbed both versions, can install both on the same PC at the same time)
Make sure that it installs the Samsung USB driver
3. Connect to the tablet using the OEM cable - if you get a reaction from Kies, great
4. Somewhere in the Kies menu, you can tell it to do a complete recovery, including bootloader- if I remember correctly, you'll need your serial number (Sorry, been 18 months since I did just about the same thing and was able to recover it from my FUBAR, and I no longer run Windows so I can't step thru it)
It will go through downloading and flashing your tablet back to the state it was when you pulled it out of the box.
If you get to that point, you will have to go the whole route (including loading TWRP) to get it back to Lineage. It took me about two weeks to get it back to the way I had it before I was flashing and reading a book and talking to my wife all at the same time and didn't pay attention to what I touched on screen.
I apologize for the rambling and not having definitive statements, but I'm drugged up and been awake for the last 36 hours, and at my age that isn't a good combination.
Click to expand...
Click to collapse

Try updating the bootloader again using odin
When this has happend factory reset
Flash the rom, addonsu and gapps in the same TWRP session
The rom should work then, I've been happily using it for about 6months now