Related
hey guys,
once every serveal months i check for updates for my rom, my recovery, and some apps.
yesterday i wanted to update tp the latest recovery (1.52)
now, the phone connected, driver was installed correctly (windows 7 32-bit)
i used the adb commands as posted in the recovery topic.
now it updated it, but after a few minutes using and wiping the phone, the usb-connection will not come to live (in any way, not even a "unknown device") and when the phone booted it gave a message: "SD removed, please place sd-card." while it has a 8 gb on there. luckily i backed up all data i needed from the sd before i flashed. so i used recovery to recreate partitions and wipe sd. but nothing works anymore... when i select ANY option in recovery wich needs SD access it immediatly gives errors.
also tried a nother microsd of 1 gb which did also not work...
about the usb-connection, it also does not work in Recovery.
but in the bootloader, it installs without any problems the well known "My HTC" device. using fastboot to boot to recovery image works, but again: no usb connection
please guys... help me... without sd-card i find my phone completely useless. (because of many documents and pictures for my work.)
I've had this problem and I had to send my Hero for repair, but it could be difficult if you have custom software in there, thry to flash original rom. Not sure though if it can be done through fast boot.
Also if you have to send it back, pretend to be an idiot and say it just went wrong. "I didn't do anything" could work.
Use fastboot to revert to a stock ROM (update.zip)
This sounds very similar to this issue on Modaco - http://android.modaco.com/content-page/299174/no-adb-no-sd/
Still ongoing, as I (pulser) am trying to guide the OP through making the goldcard (need to find another android phone to do this) and then we need to try an RUU somehow???
adwinp said:
Use fastboot to revert to a stock ROM (update.zip)
Click to expand...
Click to collapse
ok, and how?
thanks for reply.
i was thinking of letting it be repaired, but as you all say, unlocked spl, recovery image, custom rom. it does not look so good when they disver that.
but i am a stupid guy, so pretending to be stupid should be easy for me
If you are just interested in getting it back to stock for returning under guarantee to HTC, here is what I would suggest.
(No guarantees, as I haven't had to try this, and won't, for obvious reasons)
Get the stock RUU file from the hero that you have. I would recommend the oldest one that is available for you. (eg. a 1.73 one).
DISCONNECT your phone, and run the exe file(Yes, sounds strange, but bear with me).
Wait till the splash screen for the RUU is up, asking you to accept the EULA etc.
Now browse in my computer to your temp directory (C:\Users\Username\AppData\Temp in Vista/7, C:\Documents And Settings\Username\Application Data\temp in XP)
Sort the folders/files by date modified, and the most recently modified (or one of the most recently modified) folder should contain the RUU stuff. Inside a subfolder is a file called rom.zip. Copy this file to the desktop or another safe place. Once file is copied, close the RUU.
Now get your phone plugged in and booted into fastboot. (hold back + power)
Then use the command
Code:
fastboot flashall C:\Users\Username\Desktop\rom.zip
No guarantees, but it should get you back to the stock recovery, system and boot (NOT HBOOT or SPL, the actual boot.img that android uses to boot the kernel)
can i also flash custom rom with fastboot? to test if something is wrong with the rom?
That would depend on what version of SPL/HBOOT you have. If it is security off, then maybe. Otherwise I doubt it. You usually need an original, HTC signed file to flash using that method.
Feel free to give it a go, but I don't think it would work.
Hey everyone. I know there are already a few threads with boot loop animations, and am having difficulties finding the same situation as what I'm going through. Here is what the phone used to have before it randomly started looping:
Rooted - with Stock rom, using ClockwordMod Recovery 5.5.0.2
Used Go Launcher Theme ( if that even matters )
No additional roms installed or anything, the phone is 3 months old.
Ok here is where I'm stuck. I understand I should reflash somethings like recovery image or something, but I'm stuck with one big problem. My computer and phone don't recognize using the USB mount.
The message I get is called "Unable to open lunfile ( no such file or directory)
Here's what screens I can get to:
1. Hold vol up/down while holding power ( the little android with its belly open, and the options Start - Restart Bootloader - Recovery mode - Power Off )
2. Hold vol down - ODIN mode, with the START option only
I can access WMD recovery and factory reset, Try to install my old backup, nothing works at all in that area, no matter what I do.
Can someone advise me a step by step way of getting my computer to recognize my phone, so that I am able to do fastboot, or reflash, or anything to get my phone working again. I can't access my internal memory at all.
It's even possible that I've read too much, and my frustration is getting in the way, if so I apologize! Some guidance would be greatly appreciated!
Thanks in advance of course! I need my phone for business!
Cheers,
Install the drivers on a computer then use fastboot oem unlock. Or just factory reset it from within recovery.
Sent from my Galaxy Nexus using Tapatalk 2 Beta-4
Try my siggy.
I'm not sure about the exact error:
But the link there will get you the correct drivers.
Also, as stated...try to factory reset.
You'll lose your apps/data that way though =/
Hopefully you can get the driver installed and get your computer to recognize.
If so, follow this to back up your apps:
http://forum.xda-developers.com/showthread.php?t=1420351
Have exactly the same setup as you (rooted/stock/CWM) and had the animation bootloop - animation would just loop until a battery pull.
Only thing that solved it was a factory reset from recovery. Been working fine for the 4 weeks since. No need for any reflashing etc. Titanium recoveries have all worked fine as well. Didn't try my Nandroid backup as I thought that may still have the 'fault' built in.
I had a boot loop for every from I tried to flash...wat fixed it was before flashing u need to wipe system data and wipe the cache in the recovery...ie a clean install...then every rom I tried worked...so I think ur missing that crucial step coz it worked for me
Sent from my Galaxy Nexus using Tapatalk
Hey guys, as stated above I've done numerous factory resets, it still seems to boot. I will for sure try to get the drivers installed so my phone is recongised by the computer, but would need step-by-step assistance when doing fastboot, or whatever the next step is.
Looking for more help though! Keep em coming!
?
Any other ideas?
Thanks!
Ok guys, so here's where I'm at now. I've used Jubakuba's sticky link, located here:
http://forum.xda-developers.com/showthread.php?t=1529058
Everything is able to be recognized up to the point where it says "Put the su.zip on your phone."
Since I cannot access my phone contents, since I keep getting this "Unable to open lunfile ( no such file or directory), it does not allow me to add anything to my phone.
I re-installed CWD as stated in the list of things to do, and all that went well. But I have the same issue, I tried factory resetting all that. erase cache, and still stuck with the same issue.
What's my next step now peeps? Looking for a quick answer as I have time to do it tonight!
Edit***
Just tried this trick: but it says it does not recognize the device?? what is going on! Please help someone! Thanks!
Panic Section! (Something is Wrong)
Q: My phone won't boot!
A: The easiest option is to get into recovery and restore a nandroid using the above guide (pull battery to put phone in an off-state if needed).
However, more advanced options are available if you don't have a nandroid available (You're naughty).
Do you have another rom .zip available on your SD card? If so, simply use the above guide for installing a rom to get you booting again.
If not, you can download one on your PC. Boot into fastboot (the green Android with open chest menu).
Move the .zip to the C:\android-sdk-windows\platform-tools folder.
Open ADB.
Change the NAMEOFZIP.zip below to the correct file name...and perform the action.
Surely your computer recognizes your phone. Otherwise how were you able to unlock the bootloader and flash the recovery?
And I've never seen that error message before. It doesn't even make any sense to me. Where are you seeing it? On your phone or on your computer? And in what context? What are you trying to do when it shows up?
If your phone isn't booting I'm not sure that you can copy any files to it yet. (Maybe you can use adb in clockworkmod? I'm not sure) What I do know you can do is flash the stock ROM and start over.
Download the image from Google here:
http://code.google.com/android/nexus/images.html
Here's a instructions for the GSM version:
http://forum.xda-developers.com/showthread.php?t=1366806
For the Verizon version, I can't find the thread at the moment but you just replace the filenames and also there's 2 radios to flash so:
fastboot flash radio *filename*
fastboot reboot-bootloader
fastboot flash radio-cmda *filename*
"Unable to open lunfile ( no such file or directory) appears on the phone, in CWD mode, when trying to attempt "mount Usb" to be able to access my internal storage .
I am attempting your thoughts right now.
I will post with results
Ok I tried to do this step. This is the outcome I received on the computer after even typing the first step:
'fastboot-windows' is not recognized as aninternal or external command, operable program or batch file.
A thing to stress, I'm not sure how to do step 1: 1) Take a Nandroid Backup if you have CWM installed.
EDIT***
GREAT NEWS!
used this setup!
http://android.modaco.com/topic/348161-01-feb-r4-superboot-rooting-the-gsm-lte-galaxy-nexus/
and it worked!
Thank you everyone! Going to play with my phone and make sure it all works!
Macinshak said:
Ok here is where I'm stuck. I understand I should reflash somethings like recovery image or something, but I'm stuck with one big problem. My computer and phone don't recognize using the USB mount.
The message I get is called "Unable to open lunfile ( no such file or directory)
Click to expand...
Click to collapse
the problem is when that happen?? when ur phone is booted and u plug the usb cable to ur pc? or when u are under recovery and want mount the usb mass storage? the second one doesn't work
Hi, if you can help me unbrick my phone I'll buy you a beer (or three!)
I have an htc one x which i managed to unlock the bootloader via htcdev as in various tutorials....
I was too lazy to take a backup
I then tried to install cyanogenmod 10 using cwm recovery.... (by flashing a zip file i had downloaded - one of the nightly builds)
I wiped the cache etc in cwm
it got stuck in a boot loop i think as it got to the spinning cyanogen logo then nothing happened...
I've tried to get it working again using lots of different methods - i downloaded some RUU exes which failed because they said they weren't the correct ROM (even though they should be right) - then i read a tutorial about how to use fastboot to flash system.img onto the phone but it fails giving error code 00000006
I can't push any zip files to the phone using ADB as I get permission denied errors
I've also tried to use fastboot to flash various recoveries but I can't apply any zips because I can't get them onto the phone in the first place
I've also flashed various recovery.img files but when they load, I get a red triangle after a few seconds
If someone could tell me how to use ADB to push a zip file to the phone I'd be really grateful - have tried everything but keep getting permission denied errors
Thanks
(oh and if you manage to help me fix it I WILL buy you a beer... or 3)
oh and ....
ALSO I've googled the problem and tried all of the options I can find which could help - please don't just send me a link to a page because i can guarantee I've probably already tried the solution and failed. When I boot into recovery, I can't use adb push to send files to the phone because it says it's not connected even if i try the option for mount data, or mount storage - the only time windows seems to manage to aknowledge it's existence is on the fastboot screen -
lazclark said:
Hi, if you can help me unbrick my phone I'll buy you a beer (or three!)
I have an htc one x which i managed to unlock the bootloader via htcdev as in various tutorials....
I was too lazy to take a backup
I then tried to install cyanogenmod 10 using cwm recovery.... (by flashing a zip file i had downloaded - one of the nightly builds)
I wiped the cache etc in cwm
it got stuck in a boot loop i think as it got to the spinning cyanogen logo then nothing happened...
I've tried to get it working again using lots of different methods - i downloaded some RUU exes which failed because they said they weren't the correct ROM (even though they should be right) - then i read a tutorial about how to use fastboot to flash system.img onto the phone but it fails giving error code 00000006
I can't push any zip files to the phone using ADB as I get permission denied errors
I've also tried to use fastboot to flash various recoveries but I can't apply any zips because I can't get them onto the phone in the first place
I've also flashed various recovery.img files but when they load, I get a red triangle after a few seconds
If someone could tell me how to use ADB to push a zip file to the phone I'd be really grateful - have tried everything but keep getting permission denied errors
Thanks
(oh and if you manage to help me fix it I WILL buy you a beer... or 3)
Click to expand...
Click to collapse
Have you flashed the cm boot IMG and then erased fastboot cache?
fastboot flash boot pathtoboot.IMG
fastboot erase cache
For the RUU to work you need to have stock recovery and a relocked boot loader.
if you download the latest clockworkmod mounting as USB storage is fixed.
Sent from my HTC One X using xda app-developers app
thanks!
wow that was a quick reply - yes I've flashed the cm boot img and erased the cache - which version of CWM is the latest? - When you say mounting as USB storage is fixed, do you mean that windows will be able to see the device and write files to it?
(I'm really sorry for asking these questions - the problem is that I know a BIT about how android works but not as much as I should do)
treebill said:
Have you flashed the cm boot IMG and then erased fastboot cache?
fastboot flash boot pathtoboot.IMG
fastboot erase cache
For the RUU to work you need to have stock recovery and a relocked boot loader.
if you download the latest clockworkmod mounting as USB storage is fixed.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Are you absolutely sure you flashed the boot.img from the rom.zip using fastboot on your computer? Because it really sounds like you didn't
This is a thread I made and it should provide you with a solution if not a starting point if you insist on CM10.
http://forum.xda-developers.com/showthread.php?t=1900127
Good luck!
sorry hope i'm not wasting your time!
I ran the command as follows :-
fastboot flash boot boot_signed.img
(I got the img file from the ruu )
I'm not 100% sure if it worked, but at that stage I didn't see any errors
Michealtbh said:
Are you absolutely sure you flashed the boot.img from the rom.zip using fastboot on your computer? Because it really sounds like you didn't
Click to expand...
Click to collapse
CWM 5.8.4.0 has the USB mounting fixed. You can go to mounts and storage and mount as USB, then the PC will see it.
fastboot flash recovery recovery.img
Wipe cache and dalvik cache.
I'm pretty sure you either didn't flash the boot.img or flashed the wrong one, so get it again to make sure it's the right one and
fastboot flash boot boot.img
And
fastboot erase cache
thanks!
I'll give it a go - to be honest i don't insist on using cm10 at all - i just wanted to see what jellbean was like and it seemed like a reasonable way of achieving that.... i'd be quite happy with any decent rom if it can fix the lag problems i have and some of the other issues.....
great tutorial by the way! - once my phone has charged up again I'll try it
ORStoner said:
This is a thread I made and it should provide you with a solution if not a starting point if you insist on CM10.
http://forum.xda-developers.com/showthread.php?t=1900127
Good luck!
Click to expand...
Click to collapse
ahhhh!
i think i was trying to run CWM 5.8.2.7 which possibly didn't have usb mounting working? Will give that a shot thanks!
BenPope said:
CWM 5.8.4.0 has the USB mounting fixed. You can go to mounts and storage and mount as USB, then the PC will see it.
fastboot flash recovery recovery.img
Wipe cache and dalvik cache.
I'm pretty sure you either didn't flash the boot.img or flashed the wrong one, so get it again to make sure it's the right one and
fastboot flash boot boot.img
And
fastboot erase cache
Click to expand...
Click to collapse
Thanks.
I use CM10 myself at the moment because of the aesthetics, but because of the amount of ram and battery it uses I wish I had stuck with ARHD.
Come October we should see Jellybean ARHD which will have great features like USB OTG without a powered hub.
lazclark said:
i think i was trying to run CWM 5.8.2.7 which possibly didn't have usb mounting working? Will give that a shot thanks!
Click to expand...
Click to collapse
Mount as USB not working on that version, also charging not working either. It was not a great release in terms.of features, but it was updated quickly, that's quite an.old version now.
Do you know which tutorial you followed? It really needs updating, there are a lot of people on this old version struggling more than they need to.
Right, first you're going to flash a recovery which allows you to mount USB storage. Either cwm or TWRP, download the recovery.img and flash through fastboot using fastboot flash recovery rocoveryname.img.
Download a new rom and extract the boot.img from it. Flash that boot.img using the usual fastboot method.
Now boot into the new recovery, connect to your pc and mount USB storage from the option in recovery. Copy over the rom you downloaded. Unmount USB storage. Now do a full wipe through the menu in recovery - format /data, /system and /cache. Now flash the rom and reboot
Dear XDA-members,
This afternoon, I tried to root mij HTC One X and flash it to Cyanogenmod 10.2. During the flashing, I made the mistake to forget to put the boot.img and Google Apps files on my SD card. During the rom installation, I got stuck in the splash screen. For this reason, I formatted my SD kaart in the CWM recoveryscreen but now my phone doesn't have any rom at all. When I turn on my phone, I only get to see the white HTC screen. When I try to connect my phone to my pc, it doesn't get recognized. I just want to get my stock ROM back again to get my phone working. I do have acces to the CWM recoveryscreen.
I downloaded the fastboot and RUU files, but fastboot won't recognize my device through the commandscreen. This is why I can't put the RUU files on my phone.
Can someone please help me? I don't have a clue what to try next to save my phone.
Thanks in advance!
kajvb said:
Dear XDA-members,
This afternoon, I tried to root mij HTC One X and flash it to Cyanogenmod 10.2. During the flashing, I made the mistake to forget to put the boot.img and Google Apps files on my SD card. During the rom installation, I got stuck in the splash screen. For this reason, I formatted my SD kaart in the CWM recoveryscreen but now my phone doesn't have any rom at all. When I turn on my phone, I only get to see the white HTC screen. When I try to connect my phone to my pc, it doesn't get recognized. I just want to get my stock ROM back again to get my phone working. I do have acces to the CWM recoveryscreen.
I downloaded the fastboot and RUU files, but fastboot won't recognize my device through the commandscreen. This is why I can't put the RUU files on my phone.
Can someone please help me? I don't have a clue what to try next to save my phone.
Thanks in advance!
Click to expand...
Click to collapse
Can you mount storage in recovery ? If you can....
Mount storage in recovery and copy/paste rom and kernel on SD, flash rom and kernel, than flash boot.img via fastboot.
Can u do any fastboot commands while phone is on bootloader?
Sent from my HTC One X
Thanks for the quick responses!
Unfortunately, I can't mount storage in recovery so I can't acces my SD card.
I can, however, access the fastboot menu so it's possible to do fastboot commands and get into the CWM menu.
https://www.dropbox.com/s/yqzlpqo8illa53j/Philz recovery 5.15.9.img
Flash this recovery and you can mount the sd
Thanks, but can you explain how to do that?
I don't think I can use fastboot because my phone doesn't get recognized, but maybe I'm doing something wrong.
OK, I found a way to do that via fastboot, but I couldn't mount it just like in CWM. I did download a RUU.exe because I figured that fastboot is working for me! So I tried to install the stock ROM using the RUU.exe and fastboot, but the flashing progress was aborted because apparantly that RUU version was older than the one on my phone. I googled for a newer one, but there are no newer .exe files and according to others I should use a nandroid backup zip file.
How should I do that? Or is there any way that I can make the RUU.exe I downloaded work, because it seemed to me that the program worked fine except for the older version part. Or is it the easiest to flash Cyanogenmod, I've got those files on my pc as well. I wouldn't know how to do that, just by flashing boot.img from the zip file? I really hope you can help me out!
Further notes: during the RUU installation progress, CWM and Philz were wiped from the SD card and I had to relock my phone. I don't know if any of that should cause a problem though.
Flash that philz, enter recovery. Put in the usb cable and mount. Wait until the sdcard pops up on windows. Can take minutes......but works for sure !
Thank you, I'll try that tonight! Then, what kind of files should I copy on the SD card? And can I use the Cyanogenmod files as well as the stock ones? Lastly, do I need to unlock my phone again?
Unlock, flash recovery, flash boot.img, make a full wipe, install CM, install GAPPS ..... reboot
OK, so just to get it straight:
First I unlock it, then flash philz via fastboot. Then enter recovery mode and mount USB. After that, I copy the Cyanogenmod boot.img and the GApps file on the SD card. Lastly, I install the boot.img file via the Philz recovery program and then the GApps, and I reboot.
Is this right or should I do something different?
Thank you so much!
Cm.zip to sdcard, boot.img flash via fastboot. Install CM.zip and gapps via recovery.
Two last questions:
Which boot.img file do I need to use? The one from the CM.zip?
And how should I do the full wipe?
Also, I can not flash my phone because it won't charge properly... When I connect it to the charger, it will charge and I see the red light. After a while, the battery drains and gets empty, while still seeing the red light. I put it on the charger all night and it was totally empty when I checked this morning. Do you have an idea how I can deal with this?
If you can get into philz recovery. Leave it there. The battery charges inside of it.
And yes always boot.img of the rom.zip you want to install.
Sent from my HTC One X using XDA Premium 4 mobile app
I can not flash Philz yet because the bootloader is still locked. It has charged enough now, but when I try to unlock it by typing 'fastboot flash unlock unlock_code.bin' it says:
Sending 'unlock' (0 KB)... OKAY [0.009]
Writing 'unlock' ... FAILED (remote: not allowed)
finished. Total time: 0.219s
Could it be that I need to get a new unlock_code.bin? Now I use the same one as when I first tried to lock it. Or do I need to type another command for reunlocking? The status on my phone still says relocked...
Command is not correct
Fastboot flash unlocktoken unlock_code.bin
Sent from my HTC One X using XDA Premium 4 mobile app
Thank you so much, it worked!
CM10.2 is installed, I've got only one more problem...
When I boot it, and pass the setup wizard, the phone keeps popping up the same message:
Unfortunately, Setup Wizard has stopped. Every second it pops up.
I can acces various programs, so that works, except for that message.
Do you happen to know a solution for that as well?
Anyway, thank you again for your help!
Installed gapps ? The correct one ? Made a proper full wipe full before installing the rom !
Sent from my HTC One X using XDA Premium 4 mobile app
Yes, I got it to work. Now I've got a new problem... For one afternoon, my phone worked perfectly, but since that evening, now two days ago, I can't connect with my mobile services. I can't call, go on internet (only via WiFi), and when I try to create a new APN, it doesn't show. I tried it with two different SIM cards, neither work. Also my battery drains very fast and when I take a look at my battery app it doesn't show Google play services from which I heard is a common cause
Sent from my EndeavorU using xda app-developers app
This is pretty much my first time doing such things in my phone. I rooted my phone and installed ARHD 11.2 without any trouble following the instructions. When ARHD released 21.0, I tried flashing the ROM but my WiFi stopped working which I did my research and found out that it requires a firmware update (3.28.xxxx) to work. So I tried FireWater which didn't work for some reason and bought SunShine which work out as expected and my M8 is now S-OFF & set my CID to 11111111.
Now, here comes the problem. I flashed 3.2.8.401.7 firmware downloaded from ARHD blog and it returns a SUCCESSFUL but with an ERROR 90, which I also did search and said that I just have to flash the firmware again without reboot in between. Now when I boot up my phone, it's stuck on the HTC Logo with an android text below it and doesn't boot up. I went into the bootloader and tried going into recovery but it went to a black screen with and phone with a red triangle and exclamation mark in between. I erased the cache with fastboot erase cache but still didn't work. Also, I noticed that on the top of my bootloader, it says "*** Software status: Modified ***". I don't know if that is supposed to be there. I remembered TAMPERED banner was supposed to be there. My M8 is unlocked as well.
TWRP 2.8.1.0
CID-11111111
HBOOT-3.19.0.0000
RADIO-1.21.21331147A1.19_2G
I followed this guide: VomerGuides [M8]: Bootldr Unlock, S-OFF, SuperCID, Firmware Upgrade & Custom Recovery
EDIT: Solved thanks to lukes91
Solution: Flash custom recovery and then flash ROM via ext_sd and you should be good to go.
Serenity13 said:
This is pretty much my first time doing such things in my phone. I rooted my phone and installed ARHD 11.2 without any trouble following the instructions. When ARHD released 21.0, I tried flashing the ROM but my WiFi stopped working which I did my research and found out that it requires a firmware update (3.28.xxxx) to work. So I tried FireWater which didn't work for some reason and bought SunShine which work out as expected and my M8 is now S-OFF & set my CID to 11111111.
Now, here comes the problem. I flashed 3.2.8.401.7 firmware downloaded from ARHD blog and it returns a SUCCESSFUL but with an ERROR 90, which I also did search and said that I just have to flash the firmware again without reboot in between. Now when I boot up my phone, it's stuck on the HTC Logo with an android text below it and doesn't boot up. I went into the bootloader and tried going into recovery but it went to a black screen with and phone with a red triangle and exclamation mark in between. I erased the cache with fastboot erase cache but still didn't work. Also, I noticed that on the top of my bootloader, it says "*** Software status: Modified ***". I don't know if that is supposed to be there. I remembered TAMPERED banner was supposed to be there. My M8 is unlocked as well.
TWRP 2.8.1.0
CID-11111111
HBOOT-3.19.0.0000
RADIO-1.21.21331147A1.19_2G
I followed this guide: VomerGuides [M8]: Bootldr Unlock, S-OFF, SuperCID, Firmware Upgrade & Custom Recovery
Click to expand...
Click to collapse
it looks like you still have stock recovery... flash a custom one and try to boot, but you might need to reflash the rom... let me know
lukes91 said:
it looks like you still have stock recovery... flash a custom one and try to boot, but you might need to reflash the rom... let me know
Click to expand...
Click to collapse
Thanks lukes91, I noticed that some people said that the Red triangle with a ! mark on it means that it's Stock Recovery. I didn't know why my TWRP got wiped off when I flashed the firmware. I'll give it a try and update this post.
edit: I'm afraid that for some odd reason. I can't get my phone connected with ADB. It's just says device not found when bootloader says FASTBOOT USB. I reinstalled the drivers from HTC Sync and tried it with HTC Sync installed and uninstalled but I still can't get it to work. I'm plugged into USB 2.0 port.
edit2: I tried plugging in my phone while it's stucked on the HTC logo. My computer detects the Phone and opens up the Internal Storage from my Computer. I have bunch of folders inside which is empty and about 0.3GB storage are used. I'm afraid that it might have to do with the USB Debugging option is off which I do not know how to get it on in bootloader.
edit3: Okay I managed to get TWRP flashed finally. How do I get the ARHD 21.1 ZIP into the Phone? I tried ADB Sideload but it just gets stuck at "Starting ADB Sideload feature..." I tried entering the command in CMD and it said Cannot read file "rom.zip"
Serenity13 said:
Thanks lukes91, I noticed that some people said that the Red triangle with a ! mark on it means that it's Stock Recovery. I didn't know why my TWRP got wiped off when I flashed the firmware. I'll give it a try and update this post.
edit: I'm afraid that for some odd reason. I can't get my phone connected with ADB. It's just says device not found when bootloader says FASTBOOT USB. I reinstalled the drivers from HTC Sync and tried it with HTC Sync installed and uninstalled but I still can't get it to work. I'm plugged into USB 2.0 port.
edit2: I tried plugging in my phone while it's stucked on the HTC logo. My computer detects the Phone and opens up the Internal Storage from my Computer. I have bunch of folders inside which is empty and about 0.3GB storage are used. I'm afraid that it might have to do with the USB Debugging option is off which I do not know how to get it on in bootloader.
edit3: Okay I managed to get TWRP flashed finally. How do I get the ARHD 21.1 ZIP into the Phone? I tried ADB Sideload but it just gets stuck at "Starting ADB Sideload feature..." I tried entering the command in CMD and it said Cannot read file "rom.zip"
Click to expand...
Click to collapse
put the rom zip inside ext_sd and flash from there
it's the easiest way...
lukes91 said:
put the rom zip inside ext_sd and flash from there
it's the easiest way...
Click to expand...
Click to collapse
Best answer :good:
lukes91 said:
put the rom zip inside ext_sd and flash from there
it's the easiest way...
Click to expand...
Click to collapse
Alright I'll give it a try. I did try it and placed it in the internal storage but the file went missing after I rebooted into recovery. I'll try your directory instead and give a reply asap.
I actually felt embarrassed on that and my stupidity lol.
edit: Thanks very much! I flashed ARHD 21.1 and now it worked. Now I feel more embarrassed after the ext_sd incident...that actually works.
Serenity13 said:
Alright I'll give it a try. I did try it and placed it in the internal storage but the file went missing after I rebooted into recovery. I'll try your directory instead and give a reply asap.
I actually felt embarrassed on that and my stupidity lol.
edit: Thanks very much! I flashed ARHD 21.1 and now it worked. Now I feel more embarrassed after the ext_sd incident...that actually works.
Click to expand...
Click to collapse
Great! Glad i helped
Sent from here
Serenity13 said:
I noticed that some people said that the Red triangle with a ! mark on it means that it's Stock Recovery. I didn't know why my TWRP got wiped off when I flashed the firmware.
Click to expand...
Click to collapse
If the firmware zip contains stock recovery, of course its going to overwrite TWRP with stock recovery. Sometimes, folks here will intentionally remove stock recovery from the firmware zip (for the express purpose of preventing custom recovery from being wiped when flashing the firmware). But as it comes with an OTA, it will contain stock recovery.
---------- Post added at 10:12 AM ---------- Previous post was at 10:08 AM ----------
Serenity13 said:
edit3: Okay I managed to get TWRP flashed finally. How do I get the ARHD 21.1 ZIP into the Phone? I tried ADB Sideload but it just gets stuck at "Starting ADB Sideload feature..." I tried entering the command in CMD and it said Cannot read file "rom.zip"
Click to expand...
Click to collapse
I know you solved your issue another way. But the adb syntax needs to contain the actual file name, in place of "rom.zip" (with no quotes). This is assuming from the error message that you did not actually rename the file to "rom.zip"(which is another way to do it).
redpoint73 said:
If the firmware zip contains stock recovery, of course its going to overwrite TWRP with stock recovery. Sometimes, folks here will intentionally remove stock recovery from the firmware zip (for the express purpose of preventing custom recovery from being wiped when flashing the firmware). But as it comes with an OTA, it will contain stock recovery.
---------- Post added at 10:12 AM ---------- Previous post was at 10:08 AM ----------
I know you solved your issue another way. But the adb syntax needs to contain the actual file name, in place of "rom.zip" (with no quotes). This is assuming from the error message that you did not actually rename the file to "rom.zip"(which is another way to do it).
Click to expand...
Click to collapse
Well I did rename the original name(Android_Revolution_HD-One_M8_21.1.zip) to rom.zip since it's way long and it didn't work the first time I entered adb side load Android_Revolution_HD-One_M8_21.1.zip. I renamed to rom.zip just to see whether if it works but I still received the same error. It could be something wrong with the ADB Sideload. It got stuck at "Starting ADB Sideload feature..." but "adb devices" listed the device with sideload tag on it. Thanks to lukes91, the method he posted above, which was the most simplest method that I should have done at the first place works perfectly.
Serenity13 said:
It could be something wrong with the ADB Sideload.
Click to expand...
Click to collapse
Could be, I've found adb sideload to be finicky, and adb push to be more reliable. Although sideload is good to have in your bag of tricks "just in case". And of course the method you eventually used (putting it on the removable SD) works, as well.
The other common cause for the error message "cannot read file" is that the file is accidentally named rom.zip.zip due to the user not realizing they have the Windows option selected to hide file extensions (and erroneously adding ".zip" to the file name). But as you loaded and flashed the file successfully by putting it on the removable SD, this likely is not the case either.
You had the ROM zip in the same folder as your adb executable, right (when trying to sideload)? An obvious thing, probably. But just asking, since its sometimes the seemingly obvious things that trip us up.
redpoint73 said:
Could be, I've found adb sideload to be finicky, and adb push to be more reliable. Although sideload is good to have in your bag of tricks "just in case". And of course the method you eventually used (putting it on the removable SD) works, as well.
The other common cause for the error message "cannot read file" is that the file is accidentally named rom.zip.zip due to the user not realizing they have the Windows option selected to hide file extensions (and erroneously adding ".zip" to the file name). But as you loaded and flashed the file successfully by putting it on the removable SD, this likely is not the case either.
You had the ROM zip in the same folder as your adb executable, right (when trying to sideload)? An obvious thing, probably. But just asking, since its sometimes the seemingly obvious things that trip us up.
Click to expand...
Click to collapse
Yep I had the ROM zip at the same folder as the adb executable. I did tried both rom.zip and rom.zip.zip in case it was the extension setting mistake. Still it was a happy ending. I got my firmware and ARHD updated. It feels so good to be updated. :good: