Database Info

[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

[Q] SD no mount, can i replace interna sd card

Hello, so it looks like i screwed up here and got ripped of on ebay. I bought a nexus i9020t for a friend at work to bring back to india.
The seller said it had a rom install badly on it, but it could still get into the bootloader. He claimed with some effort it was likely fixable..which me and 33 other bidders agreed (*dumb move*)
Unfortunately with some further research I think this phone is having the eemc problem where it can't read its internal memory. It is stuck on the google boot screen, but bootload is accessible. When i go to look in the sdcard from recovery, it can't mount it.
"Fastboot oem unlock" won't work and from what i read, its because its trying to wipe the internal memory..but it can't access it, it freezes and when i boot back into bootloader its still locked. Also the phone boots into android every once in a blue moon, like after 20 battery pulls it will boot into 2.3.4. I've tried Wugs tool to try unlock to no avail, driver setup checks out according to the UI.
I need to unlock the bootloader to do anything, i even need to unlock bootloader to put on clockwork mod. Anyone know of a .zip package that will install clockworkmod, so i don't have to do "fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img" because that requires unlock.
Also i'm having trouble seeing the point to all this because even if I get the bootloader unlocked thats not going to help a hardward problem.
The fact it boots into 2.3.4 on ocassion indicates to me that its freezing at boot because the internal memory..i mean if there was no rom on there it would never load jack.
So other than my clockworkmod .zip install question, anyone know if the internal sd card can be replaced? I mean ill go in there if its an actual sd card and not attached to the board or something. Need some guidence here, I see the problem around, but is there reall a solution so this?

Have you tried flashing with odin ? Mabey tick the repartition option.
Sent from my Nexus S using xda app-developers app

Yea I will do that this afternoon, also I will try using the PA drivers and Wugs tool on another machine.

I'm not sure but you could try to root the phone with the gingerbreak exploit over an adb shell. After doing this you could install ROM manager and flash cwm. The ROM manager app doesn't need an unlocked boot loader. It just needs root permissions.
After doing this you should be able to boot into cwm.. BUT I don't how it could help you with your hardware problems.
Sent from my Nexus S using xda premium

I'd get a refund. If it boots once in a blue moon, something isn't right hardware wise. It either boots or never boots, not "when it feels like it".

Yea idk i hoped the guy had just super effed up the software.
Now where i'm at is i got the bootloader unlocked using the fastboot command, i had to try serveral times, but it worked eventually.
Now i need to load something or do something that will alow me to repartition system.
Basically once bootloader was unlocked i used wugs tool to "flash stock + unroot" from "can't boot" status. It worked on recovery, bootloader ect..alle the way up until it tried to write the system, and gave an error "write failed (unable to remote write)" or something like that.
So now i'm basically tyring to get the "sabra root toolkit.zip" on the device so that i can use clockwork to partion the /system. Or some other way of partiioning /system.
But i'm having difficulty pushing files to the device because wugs tool is expecting you to be booted with usb developing on, and i can't boot.
I've tried "pushing files", and "installing .zip packages from my machine" under wugs tool, and it fails every time because adb device not found, and i think its because i'm not fully booted.

Still recommending a refund. This isn't easy to fix, it's actually not fixable by commoners.

Okiedoke here's the update, I got this puppy working. Just as I did with the "fastboot eom unlock" command, I just kept trying the wugfresh "flash stock + unroot" with the "can't boot" option checked. Several times it failed when trying to write to /system, eventually I tried and it worked. Now I havnt had a boot go bad since the fix (knock on wood) and its running jelly bean.
As for the troubles couple things I noticed
1. I don't think ABD works unless you're fully booted and you have USB debugging on.
As a result not much of wugfresh's options work, only the fastboot ones do.
So the "can't boot" option only uses fastboot so it works while in bootloader.
While the unlock option won't work, because it's trying to use ABD in the beginning.
In fact the only option that doesn't use ABD that I can think of is the cant boot.
So if youre locked like I was, you need to use the command line.
2. I think the problem was the rom the guy had on before had a full blown bad flash.
The /system and I think the bootloader was messed up as well.
Luckily sometimes the device could communicate with its storage, but most of the time it couldn't.
3. Getting the drivers right is a total pain, sometimes one set of driver will work for one thing, and fail for others.
I used two laptops and switched back and forth messing with the 3 available driver settings in wugfresh.
For my problem the pnet drivers are not an option...because you have to be booted to install them, so I just switched between signed and raw. Also the USB ports you use deffidently matter so switch between those as well, if using a desktop use only the back ports.
Here are the steps I took, unfortunately they weren't precise so I can't really say what did it.
1. Download wugfresh, do the raw driver install (if you can use another machine and do the signed driver install).
2. Download the adroid sdk.zip, and extract it.
3. Use command line and go to the tools folder in the adroid sdk folder (I forget exact path, but it's the tools folder somewhere in the extracted folder).
4. Now type "fastboot oem unlock".
5. If fastboot is working right you should get the unlock screen, choose yes.
6. Mine froze here and I had to try several times until it worked..switch back and forth between the 2 comps if you have that option.
7. Once unlocked do the wugfresh "flash stock + unroot" with the "can't boot" option checked.
8. It may fail, but again switch back and forth between machines, and USB ports, if it works then you should be good to go.
One thing I noticed is that recovery showed it couldn't mount my sdcard, but after option 7, and it failed to write the /system, my bootloader changed to a more up to date version (android laying down) and it was able to see the sdcard (which shows me the recovery/bootloader where kinda screwed up in the first place). After I tried again after that maybe 1 or 2 times writing system was successful.
Thanks for all your help I'll click thanks on all you guys.

[Q] TWRP asking for password/can't mount E/ROM won't load

I'm still somewhat new to all this but after buying my tf700 last December I've been trying out a few things, unlocked/rooted and I have been happily using TWRP and various versions of Cromi X for months without any problem. Suddenly one day it didn't want to boot the ROM anymore and I have no idea the cuase (didn't just flash some kernel or drop the tablet, etc). I have TWRP 2.5.0.0 and CROMI-X 5.0.2.
I've dug through the forums and there doesn't seem to be anyone I can find who's having exactly the same problems. There was no special data I particuarlly needed on the tablet and I have backups on saved elsewhere so I am totally happy to wipe everything and start from scratch. I just want my tablet back. I'm just looking for the easist way to fix this (and I hope there is a way!) so any help is greatly appreciated.
Info is as follows:
Cromi x won't load stuck on ASUS logo. Same goes for cold booting
When I boot into recovery it says "Key driver not found.. Booting OS" at the top left
[when I enter TWRP it asks for password and says it can't mount E as below
when i "cancel" the password request i am taken to the usual home screen but installing from internal storage shows no files and a size of "0"
strangely I can get into the Micro SD card and load CROMI X from there which all goes through normally but at the finish when I'm going to reboot it says "No OS Installed!" and after restarting i'm back to same problem
I'm not getting the Fastboot USB logo I think I'm supposed to get in recovery when it is plugged it into my PC and ADB sideload in TWRP also not working (not so experienced with these though)
When I try to wipe data in TWRP I get "Failed" the message about being unable to mount E below
E: Unable to find partition size for '/misc'
E: Unable to find partition size for '/staging'
E: Unable to find partition size for '/data'
E: Unable to find partition size for '/boot''
E: Unable to find partition size for '/recovery'
Updating partition details...
E: Unable to mount '/system'
E: Unable to mount '/cache'
E: Unable to mount '/cache'
E:TNFunc::Copy_Log -- Can't open destination log file: '/cache/recovery/log'
E: Unable to set emmc bootloader message.
E: Unable to mount '/cache'
Updating partition details...
E: Unable to mount '/system'
E: Unable to mount '/cache'​

strangestribu said:
E: Unable to mount '/system'
E: Unable to mount '/cache'
Click to expand...
Click to collapse
Looks like some issue with the internal eMMC. Reboot your tablet into TWRP, connect it to your PC and run on the PC:
Code:
adb shell dmesg > dmesg.txt
adb shell ls -l /dev/block/mmc* > mmc.txt
Post the 2 resulting files.

can't seem to connect through PC
_that said:
Looks like some issue with the internal eMMC. Reboot your tablet into TWRP, connect it to your PC and run on the PC:
Code:
adb shell dmesg > dmesg.txt
adb shell ls -l /dev/block/mmc* > mmc.txt
Post the 2 resulting files.
Click to expand...
Click to collapse
Thanks very much for this. The problem I am having is I can't past the "error: device not found" message I get in the CMD on my (windows 7) PC. (yes I am opening the command line window on my android ADB folder). In fact the tablet doesn't appear in the Device Manager either. I'll admit I'm not so experienced working on the tablet through the PC (though I'm guessing I'm about to learn a lot), but I think the fact I get "Failed" when trying to ADB sideload in TWRP and nothing in the Device Manager is a big part of my problem though I'm stumped how to fix it.
Any ideas?

strangestribu said:
In fact the tablet doesn't appear in the Device Manager either.
Click to expand...
Click to collapse
You may not have the correct drivers, but even then it should at least appear as unknown device.
I don't know which drivers you need for Windows (it's easier under Linux) but maybe someone else can help you here. I remember sbdags once posted which drivers worked for him, maybe you find it using the search function.

Try these drivers:

PC doesn't recognize tablet is plugged in
sbdags said:
Try these drivers:
Click to expand...
Click to collapse
_that said:
You may not have the correct drivers, but even then it should at least appear as unknown device.
I don't know which drivers you need for Windows (it's easier under Linux) but maybe someone else can help you here. I remember sbdags once posted which drivers worked for him, maybe you find it using the search function.
Click to expand...
Click to collapse
Thanks both for this, but the problem that I'm facing is I can't seem to get my PC to recognize the existence of the tablet (connected via USB with TWRP running) even as an unknown device. Because of this I'm not sure how to get the drivers loaded. Also have loaded Android SDK Build-Tools and Google USB Driver through the Android SDK Manager. That doesn't seem to solve it either.
Not surprisingly when I run fastboot from a cmd line window and look for adb devices the list is blank.
Not sure what else to do. Would be willing to create a second Ubuntu boot on my machine if using linux would help me get this fixed. Just at a loss about what to do.
Any further insights are welcome!!!

strangestribu said:
Thanks both for this, but the problem that I'm facing is I can't seem to get my PC to recognize the existence of the tablet (connected via USB with TWRP running) even as an unknown device.
Click to expand...
Click to collapse
Is the tablet connected directly to the PC? No dock, no USB hub?
To check if your USB cable works, you can boot your tablet into APX mode (hold volume-up while turning on). The screen will stay black but the backlight should be on. You can only do something useful in this mode if you have previously created your blob file for wheelie/nvflash, but at least your PC should recognize the Tegra APX device (vendor 0x0955, device 0x7030).
If that also doesn't work, boot any live Linux distribution and run "lsusb". If that also shows no trace of the tablet (vendor ID should be 0b05 for normal operation or recovery, or 0955 for APX mode), then either your cable or your tablet's USB connection is broken.

Am I bricked?
_that said:
Is the tablet connected directly to the PC? No dock, no USB hub?
To check if your USB cable works, you can boot your tablet into APX mode (hold volume-up while turning on). The screen will stay black but the backlight should be on. You can only do something useful in this mode if you have previously created your blob file for wheelie/nvflash, but at least your PC should recognize the Tegra APX device (vendor 0x0955, device 0x7030).
If that also doesn't work, boot any live Linux distribution and run "lsusb". If that also shows no trace of the tablet (vendor ID should be 0b05 for normal operation or recovery, or 0955 for APX mode), then either your cable or your tablet's USB connection is broken.
Click to expand...
Click to collapse
Well you gave some great advice...I hadn't thought that the cable (which charges the tablet perfectly) could be the issue. I borrowed a cable from a friend who has the same machine and voila, recognized and could get into fastboot.
...and then with that problem solved, things got really bad.
I attempted to reflash TWRP on the tablet by pushing via fastboot as described on TeamWin's website. All was going perfectly until the tablet froze partway through the flash. Now when i power on, whether or not I hold vol down, I get a brief .5 seconds of the "Asus Inspiring innovation..." logo with a blue bar that goes up to about 75%, with "The device is unlocked" in the corner. After this brief 1/2 second it goes directly into APX -- black screen (though possibly back-lit) but, with the working Asus cable, Windows 7 recognizes the tablet as "Unknown Device"
I fear the device is now bricked as all the forums I've read seem to imply this. No, I didn't really know about creating a blob file for wheelie/nvflash before so don't have one (sure have read plenty about it now).
So...is this the end? Can I create a working blob file from my friend's device (I'm guessing not or it would have been thought of before)? or any other solution?
Or if not I've heard you can replace the motherboard though this is really unknown territory for me...I'm a bit curious so would be up for having a go but don't want to sink money into a helpless situation. Plus I don't know why any of this has happened in the first place so i fear there may be other parts that are not working properly.
Any useful insights on how to solve this problem I've created for myself would be greatly appreciated.

Sounds like it is bricked if you can't get into the bootloader.
What was the exact command you used to 'push' TWRP and which file did you use?

strangestribu said:
Well you gave some great advice...I hadn't thought that the cable (which charges the tablet perfectly) could be the issue. I borrowed a cable from a friend who has the same machine and voila, recognized and could get into fastboot.
...and then with that problem solved, things got really bad.
I attempted to reflash TWRP on the tablet by pushing via fastboot as described on TeamWin's website. All was going perfectly until the tablet froze partway through the flash. Now when i power on, whether or not I hold vol down, I get a brief .5 seconds of the "Asus Inspiring innovation..." logo with a blue bar that goes up to about 75%, with "The device is unlocked" in the corner. After this brief 1/2 second it goes directly into APX -- black screen (though possibly back-lit) but, with the working Asus cable, Windows 7 recognizes the tablet as "Unknown Device"
I fear the device is now bricked as all the forums I've read seem to imply this. No, I didn't really know about creating a blob file for wheelie/nvflash before so don't have one (sure have read plenty about it now).
So...is this the end? Can I create a working blob file from my friend's device (I'm guessing not or it would have been thought of before)? or any other solution?
Or if not I've heard you can replace the motherboard though this is really unknown territory for me...I'm a bit curious so would be up for having a go but don't want to sink money into a helpless situation. Plus I don't know why any of this has happened in the first place so i fear there may be other parts that are not working properly.
Any useful insights on how to solve this problem I've created for myself would be greatly appreciated.
Click to expand...
Click to collapse
If you cannot get into the bootloader and APX mode is your only access .... without nvFlash - sorry, it's a brick :crying:
The blobs for nvFlash are device specific, so somebody elses would not help you.
Your only option is to sell it for parts or have the main board replaced.
I don't have experience with that (thank God), but there are tear-down videos and instructions on iFixit.com. Maybe that'll help you decide if it would be something you can do yourself.
Otherwise sending it to Asus and have them fix it would be your only option. It is expensive....
My condolences....
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4

TF300T help
I've worked on this now for about 12 hours. I cannot figure it out. I run into the same roadblocks. I know this is an old thread, hopefully by now there's a solution for this kind of issue.
Can this be fixed in Odin or platform tools or something?
I've got TF300T where I believe I bungled the process by format/wiping from bootloader menu instead of TWRP. It's technically not bricked at all. But it's screwed up in the following ways (I was trying to get it to be a Clean Rom tablet, and there were so many sets of instructions, had them all open, and was trying to be careful about this, I've rooted and ROMed so many times and this is the first time I haven't been able to solve the issue in a reasonable amount of time)
-TWRP 2.5.0.0 asks for password, no pw ever set anywhere, tried all possibles that could feasibly be, but nothing works. This TWRP issue causes all cards to be invisible, it wiped by external SD, shows internal SD as having nothing in it but this is false as the OS boots ok (see below).
-cold boot or reboot leads to going straight into TWRP 2.5.0.0
-issuing command 'adb reboot bootloader' while in TWRP does take me into (bootloader?) 3 iconed menu, this menu is the only way I can boot the tablet into the normal Android system
-cannot factory restore the tablet from normal Android as it goes straight into TWRP following this action
-in the bootloader 3 iconed screen it is not seen by issuing that 'devices' command,
-thus cannot do 'fastboot -i 0x0b05 flash staging blob', TWRP disallows this also as the damn thing is locked down by a non-existent password.
I issued your commands:
DMESG.TXT (output too long to post here, exceeds xda allowable) &
MMC.TXT
brw------- 1 root root 179, 0 Jul 12 00:32 /dev/block/mmcblk0
brw------- 1 root root 179, 1 Jul 12 00:32 /dev/block/mmcblk0p1

Without a working fastboot connection you are one or two steps away from a hard brick. Proceed with caution!
chickenmusket said:
Can this be fixed in Odin or platform tools or something?
Click to expand...
Click to collapse
Odin is for Samsung devices only, the platform tools give you adb and fastboot, see below
TWRP 2.5.0.0 asks for password, no pw ever set anywhere, tried all possibles that could feasibly be, but nothing works. This TWRP issue causes all cards to be invisible, it wiped by external SD, shows internal SD as having nothing in it but this is false as the OS boots ok (see below).
Click to expand...
Click to collapse
Usually the reason if TWRP is asking for a password is a corrupted data partition. The recovery cannot read /data, so it assumes that it's encrypted and it asks for the password. Surprising is that you can boot into Android if your data partition is corrupted!!
-cold boot or reboot leads to going straight into TWRP 2.5.0.0
-issuing command 'adb reboot bootloader' while in TWRP does take me into (bootloader?) 3 iconed menu, this menu is the only way I can boot the tablet into the normal Android system
Click to expand...
Click to collapse
That's what stumps me... Most of the time, if you use the "Wipe Data" option in the bootloader or do a factory reset from within the stock rom with TWRP installed, you end up in a forced reboot to recovery loop - no boot to rom, no boot into the bootloader. So you are saying a normal boot goes straight into TWRP, but you can adb reboot into the bootloader and from there, by selecting the Android icon, boot into the rom??
cannot factory restore the tablet from normal Android as it goes straight into TWRP following this action
Click to expand...
Click to collapse
That's totally normal because the factory reset command calls the recovery to perform a wipe of data. Since you don't have the stock recovery it calls TWRP - but TWRP cannot resolve the command. Read this for background, but you probably don't need bootit.ko since you can boot into the bootloader anyway.. http://www.transformerforums.com/fo...my-transformer-tf700-boots-only-recovery.html
in the bootloader 3 iconed screen it is not seen by issuing that 'devices' command,
-thus cannot do 'fastboot -i 0x0b05 flash staging blob', TWRP disallows this also as the damn thing is locked down by a non-existent password.
Click to expand...
Click to collapse
This is the part that worries me. Without a fastboot connection you could be dead in the water pretty quickly. And that's the problem you should tackle first.
How did you get TWRP installed on the tablet? Not in fastboot? Most often fastboot not working is a PC driver problem. Read this to get fastboot working:
http://forum.xda-developers.com/tra...inners-guide-unlock-custom-rom-tf300-t3061648
There's also one very important information missing from your post: What bootloader are you on? your bootloader and recovery have to match and the rom you flash has to match both.
You COULD try to just format data in TWRP which should take care of the "missing password" problem and then flash the rom you want to run, but you better make sure the bootloader supports the rom!
And again - if that goes wrong and you don't have fastboot working, you could end up with a paperweight. Be careful!

Thanks for taking the time to answer. Understanding more of this is helpful (doesn't drive me as mad when I know that I don't need to keep trying passwords in TWRP). I'd like to be in a position where I knew knew all this stuff & could be helping others instead.
I thought the reason for all the lock ups was my wiping data from the 3 iconed menu rather than from twrp (the latter was supposed to do)
YES >>>So you are saying a normal boot goes straight into TWRP, but you can adb reboot into the bootloader and from there, by selecting the Android icon, boot into the rom?? >>>YES
How did you get TWRP installed on the tablet? Not in fastboot? Most often fastboot not working is a PC driver problem.
>>I got TWRP into the tablet by issuing this command
fastboot -i 0x0b05 flash recovery twrp.blob
>>Tablet is already unlocked via the Asus way. Am I supposed to go through a procedure to re-do fastboot somehow?
There's also one very important information missing from your post: What bootloader are you on? your bootloader and recovery have to match and the rom you flash has to match both.
>>Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.27.5-20130902" A03
and when I boot into this OS,
>>Android version 4.2.1
Kernel 3.1.10-g215ae8bf / [email protected]#1
Build: JOP40D.US_epad-10.6.1.27.5-20130902
Pad EC version PAD-EC20T-0216 (too much info?)
You COULD try to just format data in TWRP which should take care of the "missing password" problem and then flash the rom you want to run, but you better make sure the bootloader supports the rom!
>>Cannot format data in TWRP, after entering yes to confirm
E: unable to find partition size for '/misc'
E: ...a bunch of unable to finds, unable to mount, unable to wipe, unable to cache
everything unable to ...
I had tried that already.
Do you think I should try this:
http://forum.xda-developers.com/transformer-tf300t/help/guide-t2854495/page7

chickenmusket said:
Thanks for taking the time to answer. Understanding more of this is helpful (doesn't drive me as mad when I know that I don't need to keep trying passwords in TWRP). I'd like to be in a position where I knew knew all this stuff & could be helping others instead.
Click to expand...
Click to collapse
Stick around enough long enough, read a ton and you will be
I thought the reason for all the lock ups was my wiping data from the 3 iconed menu rather than from twrp (the latter was supposed to do)
Click to expand...
Click to collapse
It probably was. Although with a different effect than usual...
YES >>>So you are saying a normal boot goes straight into TWRP, but you can adb reboot into the bootloader and from there, by selecting the Android icon, boot into the rom?? >>>YES
How did you get TWRP installed on the tablet? Not in fastboot? Most often fastboot not working is a PC driver problem.
>>I got TWRP into the tablet by issuing this command
fastboot -i 0x0b05 flash recovery twrp.blob
>>Tablet is already unlocked via the Asus way. Am I supposed to go through a procedure to re-do fastboot somehow?
There's also one very important information missing from your post: What bootloader are you on? your bootloader and recovery have to match and the rom you flash has to match both.
>>Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.27.5-20130902" A03
and when I boot into this OS,
>>Android version 4.2.1
Kernel 3.1.10-g215ae8bf / [email protected]#1
Build: JOP40D.US_epad-10.6.1.27.5-20130902
Pad EC version PAD-EC20T-0216 (too much info?)
You COULD try to just format data in TWRP which should take care of the "missing password" problem and then flash the rom you want to run, but you better make sure the bootloader supports the rom!
>>Cannot format data in TWRP, after entering yes to confirm
E: unable to find partition size for '/misc'
E: ...a bunch of unable to finds, unable to mount, unable to wipe, unable to cache
everything unable to ...
I had tried that already.
Do you think I should try this:
http://forum.xda-developers.com/transformer-tf300t/help/guide-t2854495/page7
Click to expand...
Click to collapse
Yes. That would be the safest way to go, but you need fastboot for it. I thought you don't get the device ID returned when issuing 'fastboot devices' while in the bootloader??
As long as you can boot into the BL you don't need bootit.ko so follow that guide from the "fastboot devices" input

Correct, I do not have a fastboot ID.

chickenmusket said:
Correct, I do not have a fastboot ID.
Click to expand...
Click to collapse
That's what i mean: Probably a driver problem. Open Device Manager on the PC. then connect/disconnect the tablet while in the bootloader. Check if anything changes, check for yellow triangle next to the driver if it shows as Fastboot interface.
You can also try this in adb shell in recovery since you do have that working. This will also format your data partition:
http://forum.xda-developers.com/showpost.php?p=54521117&postcount=10

The issue was resolved with the help of Joshua Lynch. He saw my post and PMed me. For those that are losing hope like I was, if you're coming back to this old tablet, all is not lost. I will post how this resolved as soon as I have time. Thanks for the answers. Bounty has been claimed.
the issue was a driver. the computer would only have one driver installed at a time and installing fastboot driver again fixed the not seen issue. I had installed another driver (as part of this process, and it eliminated the presence of fastboot driver), and was racking my brains because I didn't think to reinstall the original fastboot driver.

I had help from Joshua Lynch a couple months back on this. It turns out that the reason the tablet wasn't seen was indeed a driver issue. What had confused it with me is that I did physically install both drivers fastboot & adb. However, my system only allowed one to be active at a time. So when I was trying to, if I'm remembering this correctly, fastboot into the tablet to console, it wasn't seen because adb was the active driver. All that needed to be done was remove adb & put in fastboot.
Just to let you all know, I did a full one & zero wipe of the tablet & installed Zombi-Pop rom with Joshua's help. The tablet was still slower than hell. Slower than any device I've ever used. I'm talking 5 to 15 second delay time from when touching something & getting a response. I found that disabling everything google (except play store & play services) helped a great deal.
But the tablet has never returned to its former speed prior to the asus update. Tinfoil hat: I have this feeling that they sent out an update that permanently screwed up the hardware on purpose.

berndblb said:
That's what i mean: Probably a driver problem. Open Device Manager on the PC. then connect/disconnect the tablet while in the bootloader. Check if anything changes, check for yellow triangle next to the driver if it shows as Fastboot interface.
You can also try this in adb shell in recovery since you do have that working. This will also format your data partition:
http://forum.xda-developers.com/showpost.php?p=54521117&postcount=10
Click to expand...
Click to collapse
Question: do you know if the original stock software that the tablet came with (before the update) can be installed? Is there a full set of instruction on this (and the stock rom)? I've got a ton of files (some roms, some files from asus website) downloaded for this tablet. I've taken a break from this thing, returning to it now... Ready to take another crack at it.
If someone wants to make some money and help me out with this, I'll pay them a total of 50 if all goes well. First 20 for their service to get the thing back on stock, original out of box software and updates disabled, another 30 when I've seen after a few days, that indeed it was done right and fast like it originally was.
Reason for this is that I already gave someone 50 for their help with this and the outcome wasn't acceptable. I've invested a ton of time in this and the $$ put in so far exceeds the value of the tablet.

[Q] I'm pretty sure I'm screwed. HELP!

Ok so I usually do searching (in this case a few hours of searching), to get help but I am in a very unique situation. Long story.
I tried updating my rooted nexus 5 to android 4.4.3 via CWM Recovery. It seemed to be taking an extremely long time to flash the rom. (I think it was a mod stock rom with root) So I shut it down, of course it wouldnt boot. So I did a whole wipe and reset in CWM, nothing. So I did it using Command prompt with one of the guides here. Worked great! Got it running, apps downloading. Then I noticed that my storage was cut in half. (It said I had 12 gigs and not 28, I have a 32 gig nexus 5) I read up and found someone who re locked, then unlocked hit boot loader. So I did that using Command Prompt. Now im stuck in a boot loop. Here's the kicker, When you lock the bootloader, the phone gets wiped. Well there went my USB debugging mode. So now, Im stuck in a boot loop and no way to get out. Ive tried using CWM to factory reset. Nothing.
I think I may have to get a new phone. From what Ive found theres no other way to get usb debugging mode on unless your in the phone. Without that, I cant do anything with command prompt. I dont post really at all, just read. So for me to do this means I am really stuck. Any advice or ideas would be greatly appreciated! I have all the latest drivers and everything.

Can you access the recovery? If so, format cache partition and then perform a factory reset and try to boot. If it fails, download the factory images and flash it. Factory images are flashed in fastboot mode and doesn't require a working OS or USB Debugging.
Follow the links in my signature and read everything mentioned it those threads. I'm sure your phone will be up and running in no time!

Thanks for the quick reply. Yes I can get into clockwork mod. Ive tried wiping data factory reset, wiping dalvik and cache partitions. When I do a factory data reset, I get this:
Formatting data /data...
error mounting /data...
Skipping format...
Formatting /cahce
Formatting /sd-ext...
E: Unknown volume for path [/sd-ext]
Formatting /sdcard/.android_secure!
Skipping format...
Data Wipe Complete
Still in boot loop.

zeroshift11 said:
Thanks for the quick reply. Yes I can get into clockwork mod. Ive tried wiping data factory reset, wiping dalvik and cache partitions. When I do a factory data reset, I get this:
Formatting data /data...
error mounting /data...
Skipping format...
Formatting /cahce
Formatting /sd-ext...
E: Unknown volume for path [/sd-ext]
Formatting /sdcard/.android_secure!
Skipping format...
Data Wipe Complete
Still in boot loop.
Click to expand...
Click to collapse
Dumb question, but do you have access to your latest back up on your phone?

Boot into recovery and adb push a rom zip
Sent from my Nexus 5 using Tapatalk

zeroshift11 said:
Ok so I usually do searching (in this case a few hours of searching), to get help but I am in a very unique situation. Long story.
I tried updating my rooted nexus 5 to android 4.4.3 via CWM Recovery. It seemed to be taking an extremely long time to flash the rom. (I think it was a mod stock rom with root) So I shut it down, of course it wouldnt boot. So I did a whole wipe and reset in CWM, nothing. So I did it using Command prompt with one of the guides here. Worked great! Got it running, apps downloading. Then I noticed that my storage was cut in half. (It said I had 12 gigs and not 28, I have a 32 gig nexus 5) I read up and found someone who re locked, then unlocked hit boot loader. So I did that using Command Prompt. Now im stuck in a boot loop. Here's the kicker, When you lock the bootloader, the phone gets wiped. Well there went my USB debugging mode. So now, Im stuck in a boot loop and no way to get out. Ive tried using CWM to factory reset. Nothing.
I think I may have to get a new phone. From what Ive found theres no other way to get usb debugging mode on unless your in the phone. Without that, I cant do anything with command prompt. I dont post really at all, just read. So for me to do this means I am really stuck. Any advice or ideas would be greatly appreciated! I have all the latest drivers and everything.
Click to expand...
Click to collapse
Try changing to TWRP recovery by using - fastboot flash recovery recoveryname.img
Format data, factory reset your devices in TWRP,
Then, install any rom using adb sideload in TWRP

Oh and if you're booting in any way possible, you're never screwed ?
Sent from my Nexus 5 using Tapatalk

zeroshift11 said:
Ok so I usually do searching (in this case a few hours of searching), to get help but I am in a very unique situation. Long story.
I tried updating my rooted nexus 5 to android 4.4.3 via CWM Recovery. It seemed to be taking an extremely long time to flash the rom. (I think it was a mod stock rom with root) So I shut it down, of course it wouldnt boot. So I did a whole wipe and reset in CWM, nothing. So I did it using Command prompt with one of the guides here. Worked great! Got it running, apps downloading. Then I noticed that my storage was cut in half. (It said I had 12 gigs and not 28, I have a 32 gig nexus 5) I read up and found someone who re locked, then unlocked hit boot loader. So I did that using Command Prompt. Now im stuck in a boot loop. Here's the kicker, When you lock the bootloader, the phone gets wiped. Well there went my USB debugging mode. So now, Im stuck in a boot loop and no way to get out. Ive tried using CWM to factory reset. Nothing.
I think I may have to get a new phone. From what Ive found theres no other way to get usb debugging mode on unless your in the phone. Without that, I cant do anything with command prompt. I dont post really at all, just read. So for me to do this means I am really stuck. Any advice or ideas would be greatly appreciated! I have all the latest drivers and everything.
Click to expand...
Click to collapse
First of all you most certainly not screwed.
Now what you have done is oem unlock without google stock recovery.
For the process of wiping userdata to complete , after you type fastboot oem unlock and restart the phone will boot to recovery and execute the wipe.
Because you have cwm recovery the process is stuck and hence the bootloop.
You need to boot to bootloader and type : fastboot -w (press enter) ,it will erase userdata and cache, and restart to system.
You can also try "fastboot format data " and "fastboot format cache" .but if -w worked then no need for that.
If you still stuck in bootloop then you need to flash the stock factory img.

zeroshift11 said:
Thanks for the quick reply. Yes I can get into clockwork mod. Ive tried wiping data factory reset, wiping dalvik and cache partitions. When I do a factory data reset, I get this:
Formatting data /data...
error mounting /data...
Skipping format...
Formatting /cahce
Formatting /sd-ext...
E: Unknown volume for path [/sd-ext]
Formatting /sdcard/.android_secure!
Skipping format...
Data Wipe Complete
Still in boot loop.
Click to expand...
Click to collapse
No need to worry. Download the 4.4.3 factory images and follow the guide "How to flash factory image" which is linked in my signature.
Or, if you want to try out a custom rom, you can push the rom.zip and gapps.zip to your device using "adb push" or sideload it in recovery.

I really appreciate the help guys. Ok I would love to try these, but, I cant do anything with the command prompt. It always says "waiting for device"
I have the latest good drivers installed from ADB. In my device manager the Yellow ! triangle is there beside the android bootloader interface. Ive tried uninstalling the drivers and the software and doing it again and nothing. Mind you, when I do that, it shows up as samsung android devices so that could be a a problem. Im going to try and work on that. Any other ideas?

zeroshift11 said:
I really appreciate the help guys. Ok I would love to try these, but, I cant do anything with the command prompt. It always says "waiting for device"
I have the latest good drivers installed from ADB. In my device manager the Yellow ! triangle is there beside the android bootloader interface. Ive tried uninstalling the drivers and the software and doing it again and nothing. Mind you, when I do that, it shows up as samsung android devices so that could be a a problem. Im going to try and work on that. Any other ideas?
Click to expand...
Click to collapse
I had a similar problem and solved it by going to update driver software, browes my computer, let me pick from a list on the computer. Then find the android adb interface
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
I had a similar problem and solved it by going to update driver software, browes my computer, let me pick from a list on the computer. Then find the android adb interface
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Done that. A few times. Says it's up to date. Problem for me that I can see so far, any tutorial on how to unlock bootloader or side load, requires USB debugging, which is turned off. Thats why I get the waiting for device message in Command Prompt.

zeroshift11 said:
I really appreciate the help guys. Ok I would love to try these, but, I cant do anything with the command prompt. It always says "waiting for device"
I have the latest good drivers installed from ADB. In my device manager the Yellow ! triangle is there beside the android bootloader interface. Ive tried uninstalling the drivers and the software and doing it again and nothing. Mind you, when I do that, it shows up as samsung android devices so that could be a a problem. Im going to try and work on that. Any other ideas?
Click to expand...
Click to collapse
Are you in fastboot mode while running fastboot commands? If so,
Uninstall each and every driver installed on your computer. Download the full android sdk from here: http://developer.android.com/sdk/index.html
Open SDK manager and download all the required tools. Also, download the usb_driver from within the sdk manager. Now connect your device to your computer and let it detect. Now, open device manager, right click on the recognized device (Name of the nexus device may be different. Don't worry). Select update driver. Now navigate to the usb_driver folder which you had downloaded previously and select it. Once the driver is updated, windows might reconnect the device. (Ding ding sounds). Once it does, open cmd from the fastboot folder and try running the commands again.

zeroshift11 said:
Done that. A few times. Says it's up to date. Problem for me that I can see so far, any tutorial on how to unlock bootloader or side load, requires USB debugging, which is turned off. Thats why I get the waiting for device message in Command Prompt.
Click to expand...
Click to collapse
No, pick it yourself, see below the search for driver software
Sent from my Nexus 5 using XDA Free mobile app

vin4yak said:
Are you in fastboot mode while running fastboot commands? If so,
Uninstall each and every driver installed on your computer. Download the full android sdk from here: http://developer.android.com/sdk/index.html
Open SDK manager and download all the required tools. Also, download the usb_driver from within the sdk manager. Now connect your device to your computer and let it detect. Now, open device manager, right click on the recognized device (Name of the nexus device may be different. Don't worry). Select update driver. Now navigate to the usb_driver folder which you had downloaded previously and select it. Once the driver is updated, windows might reconnect the device. (Ding ding sounds). Once it does, open cmd from the fastboot folder and try running the commands again.
Click to expand...
Click to collapse
Doing that again. Maybe I missed a step last time but I tried that already a few times. Im trying again.

zeroshift11 said:
I really appreciate the help guys. Ok I would love to try these, but, I cant do anything with the command prompt. It always says "waiting for device"
I have the latest good drivers installed from ADB. In my device manager the Yellow ! triangle is there beside the android bootloader interface. Ive tried uninstalling the drivers and the software and doing it again and nothing. Mind you, when I do that, it shows up as samsung android devices so that could be a a problem. Im going to try and work on that. Any other ideas?
Click to expand...
Click to collapse
zeroshift11 said:
Done that. A few times. Says it's up to date. Problem for me that I can see so far, any tutorial on how to unlock bootloader or side load, requires USB debugging, which is turned off. Thats why I get the waiting for device message in Command Prompt.
Click to expand...
Click to collapse
I think the drivers aren't installed properly. My phone comes up as Android Device, then in the drilldown Android Composite ADB Interface.
I know you've said you've done it many times, but try reinstalling the drivers manually. Go to whatever it's listed as under Device manager->Right click->Update Driver. I can't remember the exact prompts, but basically don't let it look online. Tell it that you want to install drivers you have on your computer. Navigate to where ever you have driver files and install it.
Try different USB ports/cables. Computers are weird. Sometimes this actually works.

Ok so I uninstalled the drivers from the device manager, went to control panel did it there as well. I have the SDK on my desktop, I installed the google drivers. But I also had downloaded just the google driver manually from their website. Unrared it, plugged my phone in, it detected the phone, I manually updated drivers to the ones I got from the google page. It updated. I was in bootloader mode, and I get that the drivers installed successfully, then it also says Device could not start (error code 10). Anything I type into command prompt still says waiting for device.

Johmama said:
I think the drivers aren't installed properly. My phone comes up as Android Device, then in the drilldown Android Composite ADB Interface.
I know you've said you've done it many times, but try reinstalling the drivers manually. Go to whatever it's listed as under Device manager->Right click->Update Driver. I can't remember the exact prompts, but basically don't let it look online. Tell it that you want to install drivers you have on your computer. Navigate to where ever you have driver files and install it.
Try different USB ports/cables. Computers are weird. Sometimes this actually works.
Click to expand...
Click to collapse
Wow........switching usb ports worked..............Thanks so much! Ok so bootloader unlocked. Now Ill try factory reset, if nothing Ill flash original recovery and do it again. After I sideload the stock zip.

Thanks to everyone here my phone is back up. Who knew the USB would have been the issue I was having. Its up, but again my storage was cut in half. Back to 12 gigs. So Im going to look for a fix unless anyone here has it haha.

zeroshift11 said:
Thanks to everyone here my phone is back up. Who knew the USB would have been the issue I was having. Its up, but again my storage was cut in half. Back to 12 gigs. So Im going to look for a fix unless anyone here has it haha.
Click to expand...
Click to collapse
Clear cache and factory reset in the stock recovery
Sent from my Nexus 5 using XDA Free mobile app

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.