I just used the all in one tool kit to flash CWM I have a virgin mobile one v. I went into the fastboot after and clicked on recovery, and now I am stuck on a screen with the HTC quietly brilliant. Underneath it says in red letters "this build is for development purposes only Do not distribute outside of HTC without HTC's written permission, etc. Any idea how to get out of it? I tried all the buttons I could think of.
I managed to get it by holding the power button for about 15 seconds. I can't seem to get into the recovery I just supposedly flashed. This isn't normal compared to other androids I'm use to.
Mate.... you flashed a wrong recovery that meant for GSM device.
Use this one : http://forum.xda-developers.com/showthread.php?t=1749798
Nice of the guy to specify in his OP...
Ok well I flashed to new recovery, however I till can't turn my phone on, it stays at that one screen. I can get into bootloader, and fastboot usb, that's about it.
someone please help, i'm stuck
anytime I try to run anything I get "C:\Users\Home\Desktop\data>pause
Press any key to continue . . ." and then it reboots into that HTC quietly brilliant screen with all the red letters on it.
Can you tell how did you flash the CDMA recovery from the link that I gave just now ?
I put it in the data folder for the all in one tool kit, under recoveries and flashed it with the toolkit. I also tried to do it through the fastboot cmd. I also tried TWRP. I was able to get into the custom recovery, but when I make any selection they are all empty(reboot, install zip, wipe date, wipe cache.)
I never use the one tool kit, so I can't comment anything.
But I always use fastboot command. For your CDMA recovery as it is named as cwmrecovery.img
the fastboot command will be:
fastboot flash recovery cwmrecovery.img
fastboot reboot-bootloader
fastboot erase cache
the go to recovery through hboot menu.
what I understand the cwmrecovery.img is non-touch version so you need to use the volume button to scroll and power button to select.
http://forum.xda-developers.com/showpost.php?p=28577991&postcount=13
Or you can try the touch recovery http://forum.xda-developers.com/showthread.php?t=1764183
fastboot flash recovery twrprecovery.img
fastboot reboot-bootloader
fastboot erase cache
If still problem, post your problem in their related thread. The OP may help you.
I can't do much as I own only a GSM device.
ok I followed those instruction, got to the custom recovery and at the bottom it says:
cwm-based recovery v5.5.0.4
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
Nickdroid86 said:
ok I followed those instruction, got to the custom recovery and at the bottom it says:
cwm-based recovery v5.5.0.4
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
Click to expand...
Click to collapse
I should also mention I tried flashing the 1.5Ghz kernel. Through the all in one tool kit, and also tried flashing it through fastboot by renaming it to Boot.img and typing the command for it.
There is no custom kernel for CDMA yet.... that is for GSM only. It will not work for your device, and it won't boot.
And don't worry about those E:Can't mount/cache..bla..bla... , we have that for GSM too.
I think you should stop using the One Tool Kit before it bring more harm to your device. It's nothing wrong with the tool but a user must know how to use it properly for a CDMA device, you need to change a few files on your own before you can safely using it.
Yeah I know what I'm doing, just new to this phone, and the thread for the tool kit didn't seem to mention it being for GSM. Is there a way I can use fastboot to fix this? by flashing a stock rooted rom or something?
Still unable to select anything in the recovery by the way, It just goes blank.
Flash the stock boot.img and see how it goes. If not then you need to run RUU and redo the whole process again.
the stock boot.img for VM/CDMA here : http://forum.xda-developers.com/showpost.php?p=28218226&postcount=11
flash in fastboot? Do you know the commands?
fastboot flash boot boot_signed.img
fastboot reboot-bootloader
fastboot erase cache
Yeah I think I need to use this RUU you speak of, I noticed one thing, when I reboot the bootloader and HBOOT does that scanning thing, the first two say the .img is either missing or damaged.
Downloading the RUU file, what next? Also I downloaded a stock rooted odex'ed .zip if I can just flash that from fastboot?
Related
Hello,
im in some big trouble.
I tried installing the new sense gingerbread rom.
It would not boot and i accidently formatted my sd card.
Now i cant boot the rom (loops at the android splash logo) and can no longer get into clockwork recovery.
All i can do is get into standard android system recovery.
if i use apply sdcard: update.zip i get the feeling it tries to go to clockwork
it says: e:cant mount /dev/block/mmcblk0p1 (invalid argument)
When i try to flash the recovery trough adb it says "flash is not recognized as an internal or external command....
Is there a way to get this phone again...rooted or unrooted?
Please help me
Flash the recovery in fastboot mode with S-Off.
Have you tried formatting card again? And to be sure, is there ext3 after fat32?
i reformatted. i have 7300mb fat32 and 600mb ext3.
cant get into fastboot. it brings me to a black screen with a phone with a red triangle and a explenation mark. it leads me to the standard recovery and says.
e: cant open /cache/recovery/command
its driving me crazy......
Found this on another forum:
When you get the to warning triangle.
hold down the power button, then push vol down, then vol up
Then you get to the system recovery screen.
Click to expand...
Click to collapse
i tried, but then i get to normal recovery, and when i select apply sdcard :update.zip it errors...see first post.
i cant instal RUU either because when i fastboot it wont say fastboot usb but instead go to the red triangle....
so i guess my only option is flash clockwork again but my adb doesnt recognise "flash recovery c:/recovery.img as an internal or external command....
When i use the command "adb devices" when at the red triangle it does find my telephone.
back on track using paul obriens r6 root method.
Thanks everybody.
I have an Incredible that has Cyanogenmod 7 on it. A couple weeks ago it stopped working in that it would just reboot after the white HTC incredible screen. I can get it to go to Hboot, but if I try to go into Recovery it just reboots immediately.
I flashed a new Hboot successfully, but once it reboots I get stuck in the loop again.
Both Clear Storage and Factory Reset start the boot loop as well.
Anyone have an idea of what I can do or does this sound like a hardware issue? My computer recognizes it, but I'm not sure what good that does me since I can't get it to boot or go into Recovery.
Here's the info from Hboot in case it's helps
Code:
INCREDIBLEC XC SHIP S-OFF
HBOOT-0.92.0000
MICROP-0417
TOUCH PANEL-ATMEL24_16ab
RADIO-2.15.00.07.28
Jul 23 2010, 18:06:51
GreyhoundX said:
I have an Incredible that has Cyanogenmod 7 on it. A couple weeks ago it stopped working in that it would just reboot after the white HTC incredible screen. I can get it to go to Hboot, but if I try to go into Recovery it just reboots immediately.
I flashed a new Hboot successfully, but once it reboots I get stuck in the loop again.
Both Clear Storage and Factory Reset start the boot loop as well.
Anyone have an idea of what I can do or does this sound like a hardware issue? My computer recognizes it, but I'm not sure what good that does me since I can't get it to boot or go into Recovery.
Here's the info from Hboot in case it's helps
Code:
INCREDIBLEC XC SHIP S-OFF
HBOOT-0.92.0000
MICROP-0417
TOUCH PANEL-ATMEL24_16ab
RADIO-2.15.00.07.28
Jul 23 2010, 18:06:51
Click to expand...
Click to collapse
I would flash an ruu thru hboot and then do a factory rest from hboot. Then if it boots fine flash cwm recovery thru hboot and then the su binaty thru recovery to regain root. Once you have recovery working again then flash back to cm7 or another rom of your choice thru recovery.
Or you could try to just reflash cwm recovery thru hboot, and then if you can access recovery wipe everything in mounts and storage except sdcard and emmc, and then restore a nandroid or flash a new rom.
RUU's - http://pvillecomp.com/?page_id=22
Latest cwm recovery - http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip
Latest su binary - http://dinc.does-it.net/SuperUser/SuperUser_3.0.7.zip
How to flash with hboot - http://pvillecomp.com/?page_id=79
You may also want to upgrade to the newest radio 2.15.10.07.07 - http://pvillecomp.com/?page_id=18
I flashed the PB31IMG from here (wasn't the newest): http://pvillecomp.com/?page_id=22
The flash seemed to work, but once it rebooted it went into the loop again. All the options in Hboot just throw it into the same white-screen loop, including Factory Reset and Recovery.
The only thing I see different in Hboot is my radio is now 2.15.10.07.07
GreyhoundX said:
I flashed the PB31IMG from here (wasn't the newest): http://pvillecomp.com/?page_id=22
The flash seemed to work, but once it rebooted it went into the loop again. All the options in Hboot just throw it into the same white-screen loop, including Factory Reset and Recovery.
The only thing I see different in Hboot is my radio is now 2.15.10.07.07
Click to expand...
Click to collapse
Try flashing the recovery and then see if you can access it.
If you have adb setup and have fastboot, you can try to erase the recovery partition by typing " fastboot erase recovery " without quotes into a cmd prompt on your pc. And then flash the recovery from above. Sounds like something is either messed up with your boot or recovery partition or img.
You can also try to use fastboot to erase the boot partition " fastboot erase boot " and then try an ruu again.
I tried both Clockwork 5 and Stock HTC from here: http://pvillecomp.com/?page_id=28
They both boot-looped after flashing.
When I try to go into Recovery now, I get the white screen then a quick flash of a phone image with a red triangle on top.
GreyhoundX said:
I tried both Clockwork 5 and Stock HTC from here: http://pvillecomp.com/?page_id=28
They both boot-looped after flashing.
When I try to go into Recovery now, I get the white screen then a quick flash of a phone image with a red triangle on top.
Click to expand...
Click to collapse
That red triangle is the stock recovery, try to do a factory reset now or try the sugestions i added to the post above.
Factory reset doesn't work. It shows me a phone with a green circle then goes into the boot loop.
I'll try the ADB stuff later today when I'm back from work. I've never used it before. Thanks so much for helping.
How do I connect to the phone via ADB when it's in Hboot? I just get "error: device not found" Every tutorial I found requires the phone to be booted to use ADB.
GreyhoundX said:
How do I connect to the phone via ADB when it's in Hboot? I just get "error: device not found" Every tutorial I found requires the phone to be booted to use ADB.
Click to expand...
Click to collapse
Adb will not work in hboot but fastboot will. You can use adb in recovery though, not just booted to the os. The error device not found is probably because you were trying adb from hboot, or because you dont have the correct drivers on your pc. Adb and fastboot are 2 different programs, fastboot is not an adb command. If you need the fastboot.exe file or the drivers you can get them here. http://dinc.does-it.net/ADB/ADB-Fastboot-USB-Drivers_v4_(x86)(x64).zip
I ran "fastboot erase boot" and it said "erasing 'boot'...FAILED (remote: not allowed)". Can I try running or flashing something else?
If I run "fastboot devices" it shows my device ID with fastboot next to it so I know it's connecting.
Thanks for putting up with this, can't imagine what caused this.
Hmm not sure, seems it may be some sort of hardware issue or disk failure. If you cant get it to boot after an ruu, and you cant factory reset or access a custom recovery or get fastboot to erase or flash, im not sure what else you could do. My only other sugestion would be to try the ruu.exe that you do from your pc with the phone connected. Flash the stock recovery PB31IMG.zip first before doing so as i believe its required for the ruu.exe. It may work and it may not im not exactly sure how the ruu.exe works as i have never used one, but i believe you just boot into hboot and then run the exe on your pc.
I haven't flashed through Fastboot because I don't know how. I tried flashing a few of the stock images, but I get errors everytime like "whoops: didn't find expected signature" or "archive does not contain android-info.txt".
Is there something I'm doing wrong?
GreyhoundX said:
I haven't flashed through Fastboot because I don't know how. I tried flashing a few of the stock images, but I get errors everytime like "whoops: didn't find expected signature" or "archive does not contain android-info.txt".
Is there something I'm doing wrong?
Click to expand...
Click to collapse
Take a PB31IMG.zip ruu ( http://pvillecomp.com/?page_id=22 ) and rename it update.zip
Put the update.zip file on your pc in the same folder as the fastboot.exe file. (Where adb is installed)
Boot into hboot with the phone pluged in to the pc. Make sure it says fastboot in red at the top of the hboot screen.
Open a cmd prompt to the directory where fastboot.exe is (eg C:\ADB\)
Type without quotes " fastboot update update.zip " and hit enter.
Here is some good info on fastboot.
http://wiki.cyanogenmod.com/wiki/Fastboot
Should I be able to open the zip on my computer? All the ones I download from that site are invalid according to Windows. This is the one I tried (3rd link on that page): http://pvillecomp.com/wp/wp-content/uploads/Images/Gingerbread-Stock_PB31IMG.zip
I did exactly what you said and got a similar result to before.
Code:
C:\adb>fastboot update update.zip
Whoops: didn't find expected signature
read_central_directory_entry failed
error: failed to access zipdata in 'ö╓°ÑAa.òo♥Gûl╔←☺☼‼6«T▀ésαu*z¿♥M╦▌‼A←4,<Lσ╡≥↕ ªº─ ΦSÉ╢t↕←Θ■√╣F'
GreyhoundX said:
Should I be able to open the zip on my computer? All the ones I download from that site are invalid according to Windows. This is the one I tried (3rd link on that page): http://pvillecomp.com/wp/wp-content/uploads/Images/Gingerbread-Stock_PB31IMG.zip
I did exactly what you said and got a similar result to before.
Code:
C:\adb>fastboot update update.zip
Whoops: didn't find expected signature
read_central_directory_entry failed
error: failed to access zipdata in 'ö╓°ÑAa.òo♥Gûl╔←☺☼‼6«T▀ésαu*z¿♥M╦▌‼A←4,<Lσ╡≥↕ ªº─ ΦSÉ╢t↕←Θ■√╣F'
Click to expand...
Click to collapse
Use 7-zip, winzip and winrar dont work the best for android files.
Think I'm just going to give up on this one since the flashing doesn't work...what a hassle. I wish there was some diagnostics tool that would just tell me if the phone is physically broken.
I have scoured the earth and multiple forums for my answer.
My Device: VZW-toro-GNEX
Current State:
FASTBOOT MODE - OK
ODIN MODE - OK
ANDROID RECOVERY - OK
ADB - OK
RECOVERY MODE - accessible only with fastboot boot foo.img
NORMAL BOOT - 'Unlocked Google Splash' screen freeze
Symptoms:
1) fastboot flash recovery foo_recovery.img returns OKAY [ 0.493s]; finished. ... so far so good...
However, when I select 'Recovery mode' and press power, it boots me back into PRIMELA03 except this time with heading FASTBOOT MODE - NO BOOT OR RECOVERY IMG
2) NORMAL BOOT - After a minute or so, the 'Google Splash' screen begins tearing and fading to gray. I have waited for up to an hour for it to resolve, but always ending up pulling the batt. An image of the screen tearing is attached.
3) fastboot -w update foo_stock_image_from_google.zip reports OKAY, however fixes nothing
4) attempts to access /sdcard/ from within recovery results in E:Can't mount /sdcard/
What I've already tried:
1) flashing a stock image using recovery E:Can't mount /sdcard/
2) flashing a stock image using flashboot - Screen tearing upon boot splash
3) flashing a stock image using Odin3 - Screen tearing upon boot splash
4) using a couple different popular toolkits (wtf, why not) - LOL
5) adb install foo_image.zip - does not contain manifest.xml... Surely I'm not using this command correctly
Any ideas where to go next?
Mind if I ask what is foo? And why are you using this over CWM or TWRP?
Also sdcard can't be mounted, because Gnex has no sdcard to be mounted. It only has internal storage and that's it. You can always use adb when on recovery when you need to transfer files
I would love to help you, but I've never heard of foo.img :/
4) attempts to access /sdcard/ from within recovery [(aka CWM aka TWRP aka FOO )] results in E:Can't mount /sdcard/
Click to expand...
Click to collapse
Yes, I know that there is no physical sd card. I'm not trying to mount an sd card. CWM is trying to *mount* /sdcard. (aka /data/media)
I can transfer files all I want using adb, but even when I do, there is still the issue that CWM can't flash anything because it fails to *mount* /sdcard/ in order to access whatever_image_I_might_be_using_however_it_doesnt_really_matter_in_this_context_hence_I_call_it_foo.zip
This suggests a problem with the partition table, possibly. Also, other posts of users seeing the same error are typically resolved with
just flash a stock image, bro
Click to expand...
Click to collapse
keep in mind that's ultimately what I'm trying to do here.
try to erase all partitions (except bl) from fastboot and reflash with flash-all.sh. run it with root privileges.
the other option could be omapflash, your call.
Sent from my i9250
Hi, my phone is stuck on the Jellytime boot screen, I cant use the Vol + or -. Is there a way to reset or format it? I have tried using ADB.
Please help
Thanks
mordok19 said:
Hi, my phone is stuck on the Jellytime boot screen, I cant use the Vol + or -. Is there a way to reset or format it? I have tried using ADB.
Please help
Thanks
Click to expand...
Click to collapse
This is desire (bravo) thread not desire s (saga).
R ur volume buttons broke? And when u tried adb, what command did u type?
And r u s-on or s-off?
Hi, I've got a HTC Desire HD, S off my volume buttons are broken. I have connected with ADB can reboot into the recovery screen but unable to select anything from there. When I type in ADB Devices I get my SH132RX05051 recovery.
mordok19 said:
Hi, I've got a HTC Desire HD, S off my volume buttons are broken. I have connected with ADB can reboot into the recovery screen but unable to select anything from there. When I type in ADB Devices I get my SH132RX05051 recovery.
Click to expand...
Click to collapse
Ok so all i can think of is that u need to try boot into bootloader/fastboot using adb and then flash 4ext recovery coz its a touch recovery. Try typing adb command
adb reboot bootloader
what is the adb command to flash 4ext recovery?
Thanks
mordok19 said:
what is the adb command to flash 4ext recovery?
Thanks
Click to expand...
Click to collapse
Once ur phone is in fastboot mode, put the recovery.img in the adb & fastboot folder on ur pc, and make sure its named recovery.img, if not just rename it, open command window and type
fastboot flash recovery recovery.img
Hi, I've done that and it remains in the bootloader screen.Do I reboot it?
mordok19 said:
Hi, I've done that and it remains in the bootloader screen.Do I reboot it?
Click to expand...
Click to collapse
No. Use volume buttons to navigate to bootlader and press power button then when in bootloader select recovery and press power and ul enter recovery
Hi, As I said earlier my volume buttons do not work.
mordok19 said:
Hi, As I said earlier my volume buttons do not work.
Click to expand...
Click to collapse
sorry forgot. anyway put ur phone in fastboot mode and plug it in then open fastboot command window and type
fastboot boot recovery.img
hopefully it will boot into recovery
Hi, it boots into recovery mode but I get cant select anything. I also get
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
mordok19 said:
Hi, it boots into recovery mode but I get cant select anything. I also get
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
Click to expand...
Click to collapse
Ok, erm im pretty sure u have a fried eMMC chip. Happens when pulling battery out and in too quick. try booting back into fastboot then type the command
fastboot erase cache
(then)
fastboot reboot-bootloader
(then)
fastboot boot recovery.img
Hopefully that mite work. If not look at this guide below and scroll down towards the bottom and ul see what i mean.
http://forum.xda-developers.com/showthread.php?t=1146601
Hi, Thank for all the Help. I finally got it working after using TWRP.
Hey everyone,
I am one of the people who tried the office bootloader unlock and now I have a problem. My phone will not boot to android. I get the android with the exclamation mark that flashes. I can reboot and select recovery at the bootloader, but when I hit power and vol+ I get the recovery screen for about 4 seconds before it goes back to the android with exclamation mark. I can see the following last few lines repeat:
E: cant mount cache (invalid argument)
E: failed to mount /cache/recovery/locale
I tried to erase the cache in fastboot, but I get the error "FAILED (remote: can not mount the necessary partition)". I cannot access adb as I cannot get the recovery to pull up. I am pretty sure my bootloader is still locked. It is like my partitions have been messed up. I know that Asus is aware of the issue with the bootloader app, but any updates pushed in apk format or that require the recovery will not be of help to me.
Is there anyway to rebuild the partitions or reflash the firmware via fastboot with a locked bootloader? I am used to an old Nook Tablet that you can boot from an sd card to fix issues like this.
Have you tried flashing your device?
http://forum.xda-developers.com/showthread.php?t=3096596
Follow the steps with adb sideload command, hope it'll work out for you.