Hi guys! I think I need your massive help...
What I did:
S-OFFed my Desire S with alpharevx - no problem
Rooted with Gingerbreak - no problem
Flashed ClockWorkMod Recovery with RomManager - no problem
Flashed Virtuos Unity ROM with ClockWorkMod - no problem
Tried to boot phone after flashing Virtuos Unity ROM - PROBLEM!
Phone stayed at VU bootscreen for about 30 minutes, not responding to anything.
Only thing to do was to remove battery. After that, it hung at HTC Bootlogo (green on white background), nothing happens.
So, I tried to enter CWM to flash my nandroid backup - wouldn´t accept it.
Tried to flash all other ROMs that I found - always error.
Entered CWM to try to wipe partitions.
First screen shows the menu and below that following message:
ClockworkMod Recovery v3.0.2.6
E:Can´t open /cache/recovery/log
E:Can´t open /cache/recovery/log
E:Can´t open /cache/recovery/last_log
E:Can´t open /cache/recovery/last_log
I can still use the menu however.
Wipe data/factory reset is no problem
Wipe cache partition is ok, but makes the environment REALLY slow!
Always show errormessage when trying to install ROM, when it is trying to format /system, doesn´t matter if it is custom or my nandroid backup.
Errormessage is: Error formatting /system!
Sometime I had an (Status 1) message when trying to install a custom rom. It says that it is an error in the zip file. However, I tried several with the same result.
So, I thought, "Wrong CWM?". Let´s try 4EXTRecovery instead.
Beginning to flash:
assert failed: write_raw_image(“/tmp/recovery.img, “recovery”)
E:Error in /sdcard/4EXTRecovery_v2.0.2_RC2-saga.zip
(Status 7)
Installation aborted.
There´s no error in the file, I tried to download it from several sources.
I can reach the phone thru ADB and Fastboot. I tried a couple of commands I found on the net to wipe cache but only got an error. Don´t know what to type...
When trying to flash a newer Clockwork Mod Recovery with fastbootcommand, sending the file is OK, but when writing ´recovery´ it hangs, nothing happens for 20 minutes. When unplugging the USB cord I get an error (status read failed (Too many links)).
I also tried to flash my .android_secure.img, boot.img, cache.img, data.img, recovery.img and system.img from my nandroidbackup (ex. fastboot flash boot boot.img) with the same results: sending file is ok, when writing the file the phone stops responding until I pull the USB cable, then I get the "Too many links error".
So: Is there anything I can do?
I have all the files .android_secure.img, boot.img, cache.img, data.img, recovery.img and system.img on my computer if that is any good.
I can mount and access the sdcard thru ClockworkMod Recovery.
Both HBOOT (Bootloader?), FASTBOOT and CWMrecovery is responding on phone, there is a working link between computer (ADB and FASTBOOT command), however something seems to be broken as it stops responding.
Is there any command I can use? I really don´t know more than the FLASH and WIPE command so maybe i´m missing something?
I appreciate all your input!
Thanks!
kinda looks familiar...
compare your problem to this:
http://forum.xda-developers.com/showthread.php?t=1150917
F**k... Stupid me, I read that post when it was new. However, I didn´t have that problem myself then...
So, is there a command I can execute to see that the eMMC chip is really broken?
As in that thread, point 8, second infoscreen (DS Brick shows). Just to make sure, I think I have a friend that can replace it for me then...
Hello all,
I've seen multiple people who recently, by one way or another, have a phone that have the bootloader unlocked, device rooted, and a recovery flashed...but for some reason you don't have a ROM flashed and your phone won't boot up past the bootanimation. If you're in that situation, this will hopefully help solve that issue.
What this thread is designed to do is inform you how to flash a ROM.zip file onto your seemingly bricked HTC One S device that you can't boot up. As you know, usually if your phone boots up, you just plug it into your computer, mount it, and just drag and drop the file. Well, for those of you that have no way to do that, I hopefully have a fix for you!
Requirements:
Unlocked Bootloader/Rooted Device
CWM Recovery flashed from fastboot.
Basic knowledge of adb/fastboot commands
Steps:
- Download your ROM of choice (referred to as ROM.zip) and place it wherever your ADB is on computer's harddrive (referred to as c:\AndroidSDK\tools)
- Boot your phone into Recovery and select the "Mounts & Storage" screen
- Plug your phone into your computer using USB Data Transfer Cable
- Ensure in Recovery that your phone shows "Unmount /sdcard/" and "Unmount /system/" (If they do not show this automatically, just press each one once respectively as pressing just toggles Mount and Unmount)
- Open Command Prompt on your computer by doing Start -> Run -> cmd
- In Command Prompt, type "cd c:\AndroidSDK\tools" replacing AndroidSDK\tools with wherever your adb and ROM are located.
- This is probably the most important part - Still in Command Prompt, type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends. This may take a minute or two...or four, but you will see a message in Command Prompt saying something like <12345678kb to 1234567kb>. That is just telling you that the file was pushed properly. (I did not include that message in the picture below)
- Once this has completed, unplug your phone from your computer and close the Command Prompt window
- Back in Recovery, go to Recovery's main screen and Do a "Factory Reset", "Wipe Cache Partition", and "Wipe Dalvik Cache [which is in the Advanced menu of Recovery]"
- When these are all done, from Recovery's main screen, select "Install ZIP from SD Card" and then "Choose file from SD Card" and select the ROM.zip file you just pushed from your computer to the SD Card. If you do not see the file, go back to Mounts and Storage and toggle them to say "Mount /sdcard/" and "Mount /system/" and then go back and try to fine the ROM.zip file. If you still do not see it, it was not pushed correctly...go back and ensure you were letter for letter with the name and the file path.
- Once the screen in Recovery says "Install from SD Card Complete.", go back to Recovery's main screen yet again and select "Reboot system now" - If your device fails to Install the ROM.zip, I had this happen to me. You must push the CWM SuperSU ZIP (the .zip file is found at the end of this thread)file as outlined before and Install THAT .zip file in Recovery, then reboot Recovery and Install the ROM.zip from SD Card.
- Let your phone have some time to boot up...initial boot from installing a new ROM have histories of taking a couple minutes.
- You should now be on a working HTC One S running whatever ROM you decided to flash.
Conclusion:
I hope you got your phone working again and I hope this helped. Please feel free to critique this guide as I am quite new to the HTC One S, but not new to rooting phones at all. If you have questions, please comment and ask or don't hesitate to shoot me a PM...I'm more than willing to help.
I hope this helped all of you who may be in the situation I was in and the situation I've seen a couple of people in.
Thanks for this information goes out to doktortaru, strker45, and torxx.
Don't need this tutorial as im not having this issue but wanted to say thanks for posting it. This should definitely help some people in the future! Great write up!
+1
Sent from my Transformer TF101 using xda premium
Thank you man.
Very informative for self learning!
Nice tutorial. But wrong forum.
Sent from my HTC One S using Tapatalk 2
you don't need to finish the command with rom.zip:
adb push ROM.zip /sdcard
is enough.. Also you should so the ROM.zip in the same folder as ADB, with the your picture.
Zylith I tried that when my phone was messed up, but I couldn't find the SD Card. However when I includes the name of the zip at the end, it worked.
Sent from my HTC VLE_U using xda premium
thanks for the detailed guide! the issue im having is not being able to mount /sdcard in recovery. I can successfully adb push the zip to the sdcard but when i try to flash in recovery, it gives me error mounting /sdcard.
can you post a quick guide on how to flash via fastboot the boot.img and system.img from the RUU? i think thats the only option i have at this point. and thanks again for this guide!
mrroey said:
thanks for the detailed guide! the issue im having is not being able to mount /sdcard in recovery. I can successfully adb push the zip to the sdcard but when i try to flash in recovery, it gives me error mounting /sdcard.
can you post a quick guide on how to flash via fastboot the boot.img and system.img from the RUU? i think thats the only option i have at this point. and thanks again for this guide!
Click to expand...
Click to collapse
When you click to mount /sdcard/ before you push the ROM over, what does Recovery tell you? What error is it?
So when I press mount sdcard it shows me Error mounting /sdcard. Same message when I try to format the sd card.
Adb seems.to push the file to sd card successfully in cmd. However when I go to install from zip it gives me "Cannot mount /sdcard"
I tried partitioning the sd card in recovery but that doesn't seem to have any effect.
mrroey said:
So when I press mount sdcard it shows me Error mounting /sdcard. Same message when I try to format the sd card.
Adb seems.to push the file to sd card successfully in cmd. However when I go to install from zip it gives me "Cannot mount /sdcard"
I tried partitioning the sd card in recovery but that doesn't seem to have any effect.
Click to expand...
Click to collapse
Try my solution here:
http://forum.xda-developers.com/showthread.php?t=1630459
Sent from my HTC One S using Tapatalk 2
Yea, I had trouble mounting anything prior to all of this.
I had to do Clear Storage in the bootloader, reinstall CWM Recovery and SuperSU and I got it to work. Hopefully we don't have too many more people with this issue. If we do, I'll be around to help.
I'm always trying to learn and try new things, so hopefully I'll be able to help with more stuff in the future.
just to make sure, for the T-Mobile One S folks, you guys aren't able to mount /system with adb yet right?
as in.. being able to adb push files to the /system folder ..
in the current state of our root.
I think that this thread is definitely in the RIGHT section !! And i also think it should be stickied !!
Its a very useful thread / Guide as we dont have mount USB storage option working in CWM... So if something fails, And you are left with no flashable ROM on your phone THIS guide will save your life
Thanks to the OP !!
Yes definitely this should be stickied! Saved me a lot of trouble and headache.
can you do one for mac?? please
Can this be moved/stickied possibly? This seems to be a decent size problem for many people.
if adb is too hard then droid explorer does the hard work for you.
Sent from my Amazon Kindle Fire using xda premium
Unable to see how is this tutorial helpful
Its like pushing a FILE to ur SDCARD with ADB
So the title is misleading; as installing a ROM is a different issue
om.thelostone said:
Unable to see how is this tutorial helpful
Its like pushing a FILE to ur SDCARD with ADB
So the title is misleading; as installing a ROM is a different issue
Click to expand...
Click to collapse
There are a lot of users who love to flash new things but who don´t deal with all the computer stuff every day. So when you are addicted to the install instructions but something unexpectful happens and your phone is in boot loop this guide is very useful.
When this is stickied it could a) avoid heard attacks of users who think "OMG I have bricked my phone" and b) avoid that dev threads become off topic.
Can be closed!
Oh man, I read the warning too late.
I had a few issues installing Rayman's 4.2 on my TF101 with clockworkrecovery v5.x (Error was not able to open /cache/recovery/** or so. Shouldn' t matter anymore).
Call it stupidness, I thought using the actual cwm version would solve my problem.
As you can see, it did not.
I flashed v.8, the addons and the gapps. No errormessage (did not get any with the older version either).
But it is stuck in a bootloop.
Not too stupid, I did a backup before - sad but true I can't use it. (E:unknown volume for path[/sdcard/]\\E:Can`t mount /sdcard)
Of course I am not able to flash any other rom from internal sdcard. (not even think about external sd!)
I can push a rom to sdcard via adb push, but can`t use it (>choose zip from sdcard \\ E:unknown volume for path[/sdcard/]\\E: Can`t mount /sdcard/) and after reboot the rom dissapears.
Pushing to /data/media is not possible, as media does not exist.
Fastboot seems not to be a possibility, as I can`t boot in bootloader mode... (but tell me, if I am wrong!)
So if anybody knows a solution - I would be so happy!
Update 1:
I followed these instructions:
www tabletroms.com /forums/transformer-rom-development/1071-asus-transformer-nvflash-stock-3-1-stock-3-2-recovery-roms-unbricking-tools.html
I installed Nvflash on my linux pc.
APX mode works, I just had to do what people told me to. (Press Vol UP(!) and Power Button)
Connect via USB.
Then run sudo ./download.sh
Everything looks fine, but then again: An error occurs:
file not found: recovery.img
failed executing command 2147483647 NvError 0x4
command failure: create failed
Update 2:
I tried another version. For some reason, my TF is not WW, as I thought than US...
Everything is fine, I am happy again. Maybe it helps anybody? And if not - I had my xda rubberduck.
I recently rooted my TF300T Asus tablet and all was well until I tried to flash CM onto my tablet for the giggles of it. I tried using CM 10.0.0 and flash it over but something under the hood went funny and erased all of my memory including a backup I had made on the internal storage (I know not the smartest option but I don't have a SD card for my tablet) now I am trying to flash stock Android back to the tablet using the ADB push and TWRP install but I keep getting
Code:
Error flashing zip '/sdcard/TF300T-US_epad-10_6_1_27_5-UpdateLauncher.zip'
I searched around the internet and saw that sometimes fixing the permissions can help with that but it didn't help. In the mount menu of TWRP I cannot mount System.
Any help would be greatly appreciated!
I managed to figure it out of my own accord. First off for anyone that is following this my tablet ended up being totally blank and TWRP didn't know how to handle that. I had to use ADB to flash the system back using the blob downloaded from the asus website. (google it and you should be able to find it pretty easy, PM me for more detailed instructions) I used the command
Code:
fastboot -i 0x0B05 flash system blob
where blob was extracted from the .zip file from asus. Hopefully those instructions help!
My phone is a Samsung galaxy S3 SCH-S968c, Verizon Networked for Straight Talk. I ran into having my phone stall after the Samsung logos boot up and then the tracfone logo appears and stalls there. The issue started after i tried installing multiple tweeks using a popular app for rooted devices (i cant think of the apps name at the moment). I have a version of CWM on it. After reading threads here in XDA i found that my CWM will not work correctly on this phone. Retired Forum Moderator "edfunkycold" said "It's not really a bug with the recoveries which where modded. It's part of whatever Samsung has done to keep people from rooting and flashing roms." so i downloaded both CWM_mod2.img and TWRP_mod2.img.
So between the soft bricking and the usless cwm i cannot flash anything or access the internal or external sd cards. I tried using ADB and these commands:
adb push .img /sdcard/.img
adb shell
su
dd if=/sdcard/.img of=/dev/block/mmcblk0p18
I just get the Android Debugging Bridge version...............
I also tried other methods found in XDA using ADB.
I tried Samsung Kies, 4 versions of Odin, SkipSoft Android Toolkit and some other java executable program that didnt work.
I can boot into both recovery mode and download mode.
Recovery mode does nothing....
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E: Can't mount /sdcard
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
.....etc. etc.
In Download mode, Odin recognizes that the phone is connected but when i try loading anything it wont connect. example: trying to load a bootchain file it says:
checking MD5 finished successfully..
Leave CS..
All threads completed. (succeed 0 / fail 0)
Other attempts show the RED FAIL square.
Im having trouble finding the correct Files to Flash. Im guessing the SCH-I535 is the non-straight talk equivalent to my straight talk phone so i have downloaded file: Samsung-Updates.com-SCH-I535-VZW-I535VRALF2_Kernel.zip
and Rom: Sons Of Android - cm-10.2-20130928-UNOFFICIAL-jewel.zip
Bottom line is I DONT CARE what version of android (stock or ROM) as long as it's compatible and need the correct flash files necessary. I THINK it originally has jellybean 4.2.2??? PLEASE help. ive been messing with this for 3 weeks now :crying:
Thanks
try "fastboot flash boot boot (recovery.img location on your computer). " It will remove your rom, so put one on the sd card.
jbaker22 said:
try "fastboot flash boot boot (recovery.img location on your computer). " It will remove your rom, so put one on the sd card.
Click to expand...
Click to collapse
ADB is not recognizing my phone. Odin still is. I tried to flash recovery with Odin last night. The process completed with success but when i restarted the phone i was not able to gain access back to the recovery. Now I can only get into download mode. Is this why ADB is not working, cuz it has to be in recovery mode?
Also I am confused on how the file structure should be when i put a rom on the sd card. I know they go in the root..... do i just extract them from the ZIP straight over to the SD? Is there a way to convert ZIP files to an Odin flashable file?
FIXED!!!! w/ Straight Talk Stock Firmware SCH-S968C
I FINALLY found a working download link for the correct firmware!!! Thanks to an old post by Kenny1974 who posted the name of the file. I googled it and found only one available!
https://www.dropbox.com/s/j2uc1hkm4...8CTFNAMH1_1304014_REV09_user_low_ship.tar.md5
I Flashed with Odin and Presto!
If this link becomes invalid, p.m. me and i will send you a link or the file.