Hi folks,
I seemed to have really bollixed up my HTC Flyer (BS_US001, HTC__055, U.S. Best Buy WiFi only) in the process of trying to get a custom ROM, any customer ROM, on it.
This device was OTA updated to the official HTC HC release and did work apart from some of the flakiness people have reported with random apps launching (didn't believe it when my daughter told me so but then found confirmation here).
I unlocked the boot loader via the HTC web site. I'm at HBOOT 1.11.0011.
In the process of trying various things I seem to really have clobbered something.
I am now at the point that I cannot flash via fastboot.
For example, I tried to reflash the recovery partition with the stock image from RUU_Flyer_BrightstarUS_WWE_2_27_1540_31_R_Radio_20_3504_30_089BU_3809_07_04_06_M_release_204116_signed.
Here's what I see:
C:\Users\John\Desktop\rom>fastboot flash recovery recovery_signed.img
sending 'recovery' (4156 KB)...
OKAY [ 0.686s]
writing 'recovery'...
I never get past this regardless of whether I'm trying to flash a single image or the entire rom.zip. I cancel with Ctrl-C but HBOOT is locked up at this point and I need to cycle power.
I can boot into CWM via fastboot boot recovery.img. I cannot do the same with the recovery_signed.img from the stock RRU nor with the boot_signed.img. When I try these, I get:
FAILED (remote: reproduce boot image with on-flash ramdisk error)
Even though I can boot into CWM, I cannot apply an update.zip, and I consistently see these messages:
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
When I look at the CWM log, I have the following additional error:
W:failed to mount /dev/block/mmcblk0p30
and occasionally:
W:failed to mount /dev/block/mmcblk0p29
BTW, this device does obviously not boot into HC anymore. I get the white HTC start-up screen, the the screen goes black, sits there for a while, then buzzes, and loops through this again.
Any ideas?
I actually work at a chip company that does Android work and am quite familiar with much of this terminology, just not HTC's specific implementation. I'm getting the impression that I hosed up the image in a particular partition or possibly even the GPTs in the eMMC itself.
I noticed that HBOOT says "eMMC boot" when it starts up? Is there any way to boot from microSD? I know our devices can do so, but, of course, we have to pass the necessary parameters to U-Boot to do as much, and I figure the same would be required with HBOOT.
Is there anyway to get serial console access on this device without actually taking it all apart?
At this point, I'm tempted to just snag another beater tablet from the office (we buy most of them at some point for competitive benchmarking) and let my daughter use that one until she enters middle school, at which point my wife and I will allow her to have a phone. I just wanted to exhaust every last possibility on this device before consigning it to our next E-Waste pickup.
Thanks for any help or insight.
I don't understand why you are trying to flash stock recovery, or update.zip.
Did you try to just flash the zip for a custom ROM in CWM, then flash boot.img for that ROM using fastboot?
redpoint73 said:
I don't understand why you are trying to flash stock recovery, or update.zip.
Did you try to just flash the zip for a custom ROM in CWM, then flash boot.img for that ROM using fastboot?
Click to expand...
Click to collapse
Well, that's the kicker. I couldn't flash any custom ROM, so I figured I at least ought to try to get back to the stock ROM.
For example, if I try ARUwizard.exe, I downloads and tells me it's working then comes back that it could not flash anything.
I see the same errors if I try to flash an entire ROM image with "fastboot flash zip filename.zip".
This is why I attempted to flash individual img files manually.
BTW, I talked with one of my co-workers and have a plan of action. Since I can download and run a recovery image, it means I can run a Linux kernel. His suggestion was to boot a kernel that has the USB Ethernet gadget driver compiled in and runs telnetd/inetd. Then, I could get to the shell prompt on the device, check out the individual partitions to see what's going on, and, update these partitions manually with their respective img files.
So, anyone have a kernel compiled to do this with a root file system either on SD card or via initramfs? I can definitely build one, but it'll be an afternoon project to pull it all together. Maybe not too much of an afternoon since I've more or less just done the same thing for one of the SoCs I work on that does not have much in the way of expandability, e.g. no microSD slot so it's Bluetooth all the way for anything.
Thanks again.
Is your bootloader still unlocked?
You have to relock the bootloader to run the RUU. It might be as simple as that (just relock and run RUU).
But don't know why you can't flash a custom ROM. What happens when you try? The flash fails, or is it successful, but fails to boot?
redpoint73 said:
Is your bootloader still unlocked?
You have to relock the bootloader to run the RUU. It might be as simple as that (just relock and run RUU).
But don't know why you can't flash a custom ROM. What happens when you try? The flash fails, or is it successful, but fails to boot?
Click to expand...
Click to collapse
Yeah, my bootloader is still unlocked. I can try RUU again after relocking. I'll have to get you the specific messages it outputs when it fails, but it is consistent, and I think I got them the one time I tried with the bootloader locked.
fails to boot
Hi redpoint, my flyer flashes ok but still fails to boot, or enter recovery, where am i going wrong?
redpoint73 said:
Is your bootloader still unlocked?
You have to relock the bootloader to run the RUU. It might be as simple as that (just relock and run RUU).
But don't know why you can't flash a custom ROM. What happens when you try? The flash fails, or is it successful, but fails to boot?
Click to expand...
Click to collapse
Related
Got my Evo 3D (UK GSM version) today, what a great phone! Rooted it and flashed a few roms to see what worked best for me, not a problem. Found one that worked and left that running all afternoon customising it all, checking everything worked: sms, phone calls etc.. all fine, again no problems.
Picked up the phone again, flicked through the homescreens, tapped on an icon and it froze, tried pressing home, holding power nothing so I popped the case off and pulled the battery.
I put the battery back in to boot up but it just stuck at the HTC logo so I thought "right, this must be a dodgy rom, i'll do a nandroid restore from recovery" booted into bootloader, hit recovery, took it's time loading then gave me some errors along the lines of:
Can't mount cache/recovery/whatever a few times
Thought that was strange, never seen that before, I'll try clearing the cache before doing anything. Tried that and the recovery menu froze up. Rebooted and tried flashing a rom, that froze too so now I'm thinking "Oh no, i've cocked this one up"
Tried flashing the recovery again through fastboot but that always fails and now I can't even get into the recovery menu.
So anyway, at the current moment in time what I've got is:
Can't boot OS
Can't get into recovery
Trying to flash a recovery through fastboot fails
Trying to flash an RUU rom through either running the .exe fails to restart into bootlader
Trying to flash an RUU (or anything else for that matter) via .zip on the sd card fails with " - Fail-PU" on every line then "Partition update fail! Update fail!" at the end
Factory reset doesn't seem to do anything
Some details
-Revolutionary-
SHHOTER_U PVT SHIP S-OFF RL
HBOOT-1.49.1107
RADIO 10.13.9020.08_2M
eMMC-boot
Jul 12 2011, 15:29:51
I just don't understand how it's managed to get into this state, I've flashed previous android phones before without a problem, I had the rom running fine for hours before it died on me, so confused, feel like crying
I read somewhere something about re-creating partitions on the internal memory but I've no idea how to do that. Is that what I need to do?
Has anyone else cocked their phone up like this?
Any help at all to get this working would be amazing, thanks guys!
so you can't get to recovery? If not find the sticky that has all the stock RUU and push that through adb. maybe that will work. if you can get to recovery try to install the stock rom's .zip.
I think you might be flashing/using the wrong ruu. More than likely the radio that the ruu has isn't compatible with your specific hboot. Try a different ruu with a different radio. But no your phone shouldn't be bricked.
""Shooter on Deck""
Ok I can now get into a recovery image by using "fastboot boot whatever_image.img"
The exact errors I get are
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
I also tried flashing parts of my nandroid backup via hboot and they all fail with the error "Failed (remote? image update error)"
But there was one very interesting error when trying to flash data.img it said "Failed (remote: partition does not exist!)"
Still no luck with flashing ruu roms
Just tried a few more ruu packages, it reboots into bootloader this time and starts sending files across, looks like it's doing something (I got excited and thought I'd fixed it) then it failed again, it told me to unplug USB so I did and it was at the hboot screen and listed all the different parts of the rom with "Fail-PU" on every line
So again this makes me think the partitions on the internal flash are messed up, is there an image I can use to re-create (or even just check) the partitions properly?
Ok, I've got adb working now through clockworkmod recovery image after doing "fastboot boot recovery.img"
Give me some commands I can type to check and fix the partitions table
Just tried a different recovery image, 4ext recovery http://forum.xda-developers.com/showthread.php?t=1378193 and it prints out the partition table when it boots
partition | fs | size | free
system ext4 800 MiB B
data ext4 1195 MiB B
cache ext4 120MiB B
sdcard fat32 30531MiB 27.0Gb
Does that look ok? What does the B mean under free? Buggered up?
So I'm getting this error when booting into recovery:
E: Can't mount /dev/block/mmcblk0p36
(file exists)
E: Can't mount cache: recovery/command
E: Can't mount /dev/block/mmcblk0p36
(file exists)
E: Can't mount CACHE: recovery/log
E: Can't open CACHE: recovery/log
E: Can't mount /dev/block/mmcblk0p36
(file exists)
I can't flash any zips, or restore my nandroid. I think something happened in the process of trying to revert to the stock OTA kernel so I could restore my GB nandroid from ICS.
I'm basically stuck, not sure what to do. Tried reflashing recovery through fastboot. No good.
TeamSPD said:
So I'm getting this error when booting into recovery:
E: Can't mount /dev/block/mmcblk0p36
(file exists)
E: Can't mount cache: recovery/command
E: Can't mount /dev/block/mmcblk0p36
(file exists)
E: Can't mount CACHE: recovery/log
E: Can't open CACHE: recovery/log
E: Can't mount /dev/block/mmcblk0p36
(file exists)
I can't flash any zips, or restore my nandroid. I think something happened in the process of trying to revert to the stock OTA kernel so I could restore my GB nandroid from ICS.
I'm basically stuck, not sure what to do. Tried reflashing recovery through fastboot. No good.
Click to expand...
Click to collapse
Did you relock the bootloader before trying this stuff?
No but I think I may have figured it out. Still not sure what happened but the recovery seems to be working now. Trying to flash the stock OTA ROM for now.
Edit: Back in action. So I was finally able to flash the stock rooted OTA and boot up. Must have messed something up when I was flashing a kernel or something.
TeamSPD said:
No but I think I may have figured it out. Still not sure what happened but the recovery seems to be working now. Trying to flash the stock OTA ROM for now.
Edit: Back in action. So I was finally able to flash the stock rooted OTA and boot up. Must have messed something up when I was flashing a kernel or something.
Click to expand...
Click to collapse
I am having this same issue. And, when I try to run the RUU executable, I get an error, wrong bootloader version. How did you resolve this issue? Thanks in advance.
HELP
Could you please share how to fix? I have reflashed boot.img and recovery.img and nothing seems to work. my phone is basically bricked until I figure this out. Thanks
salesrep2189 said:
Could you please share how to fix? I have reflashed boot.img and recovery.img and nothing seems to work. my phone is basically bricked until I figure this out. Thanks
Click to expand...
Click to collapse
what are u trying to fix?
salesrep2189 said:
Could you please share how to fix? I have reflashed boot.img and recovery.img and nothing seems to work. my phone is basically bricked until I figure this out. Thanks
Click to expand...
Click to collapse
What happens if you use the boot image (PH98IMG.zip) from your current rom that you're running and flash it in hboot and then reboot?
disregard
I used this guide and it worked. http://forum.xda-developers.com/showthread.php?t=1486220
thank god.
I'm the same, I can't restore or back up. I'm on the ICS HBoot and clean 4.3 Rom. I have the v1.4 recovery. I can see my sd card on my phone with es explore and I can see my back ups in recovery. But I get the oops every time when I try to use restore or back up.
Sent from my ADR6425LVW using XDA
salesrep2189 said:
Could you please share how to fix? I have reflashed boot.img and recovery.img and nothing seems to work. my phone is basically bricked until I figure this out. Thanks
Click to expand...
Click to collapse
This will sound bruteforceish, but after some time in a similar spot, I did this and had 100% fixage:
- Flash the latest leaked ICS RUU
- After that, download the PH98IMG version of AmonRa
Assuming you're s-off'd, this will completely wipe your phone, but it should fix your boot issue, any lingering SD issues, and had AmonRa recovery up and running w/o issue.
If need be i uploaded the 2.01.605.11 RUU here http://d-h.st/Ju5
I had the same issue when i obtained s-off and ran that ruu then all was well
Instructions:
1. Download
2. Rename file to PH98IMG
3. Check MD5
4. Load onto root of SDCard
5. Boot into HBOOT
6. Wait for it to finish
Remember you must be S-Off if you're trying to downgrade from the Leaked ICS firmware
Having all kinds of issues with AR. cant nandroid back up, says it fails, cant mount the SD card, cant look at error logs, or move them...
However after beating my brains out for hours with this issue i tried CWM touch ( hope it don't have charging error ), and it works just fine.... hmmmmm
looks like AR cant handle whatever s-off did maybe?
IrvChynaman said:
If need be i uploaded the 2.01.605.11 RUU here http://d-h.st/Ju5
I had the same issue when i obtained s-off and ran that ruu then all was well
Instructions:
1. Download
2. Rename file to PH98IMG
3. Check MD5
4. Load onto root of SDCard
5. Boot into HBOOT
6. Wait for it to finish
Remember you must be S-Off if you're trying to downgrade from the Leaked ICS firmware
Click to expand...
Click to collapse
Is this the GB ruu and if so I follow your instructions flash the ruu in hboot and re-down load the recovery right. I have tried every thing that is a fix for the newest firmware with no luck. When I did the s-off thing I used the ICS hboot. Since we have s-off I could down grade back to GB right. I just would like my sd card and recovery back. I just need some help with this, like I said I tried all the ICS sd card fix with no luck. The only thing I have not done yet is the adb busy box command thing yet. I tried to do it, but it's not working for me. I typed adb shall in cmd and only get a list of adb commands. I've also tried adb devices and it wont list my phone, but if I do a fastboot devices my phone is listed. I'm in fastboot when I try the adb devices. I'll keep reading and learning, something has to work. I learned to unlock, install recovery, install a rom and flash the kernel, s-off my phone and just about every other thing likes mod and how to move files in es explorer. I just need to find a way to fix my recovery... But thanks for every ones help and thanks to the dev for making all the great roms and for getting us s-off.
NAU420 said:
Is this the GB ruu and if so I follow your instructions flash the ruu in hboot and re-down load the recovery right. I have tried every thing that is a fix for the newest firmware with no luck. When I did the s-off thing I used the ICS hboot. Since we have s-off I could down grade back to GB right. I just would like my sd card and recovery back. I just need some help with this, like I said I tried all the ICS sd card fix with no luck. The only thing I have not done yet is the adb busy box command thing yet. I tried to do it, but it's not working for me. I typed adb shall in cmd and only get a list of adb commands. I've also tried adb devices and it wont list my phone, but if I do a fastboot devices my phone is listed. I'm in fastboot when I try the adb devices. I'll keep reading and learning, something has to work. I learned to unlock, install recovery, install a rom and flash the kernel, s-off my phone and just about every other thing likes mod and how to move files in es explorer. I just need to find a way to fix my recovery... But thanks for every ones help and thanks to the dev for making all the great roms and for getting us s-off.
Click to expand...
Click to collapse
Yeah this is the gb ruu. Your firmware and hboot will downgrade but you will keep s-off. I'm not sure if flashing the leaked ics ruu will work but I wouldn't be surprised if it would.
Sent from my ADR6425LVW using XDA
Bricked my HTC Rezound trying to root it today. Need help installing stock RUU, but how do i do this. Push it to my phone with ADB while in fastboot? And if thats how, how is this accomplished? I can only access the bootloader/fastboot.
What exactly were you doing when this happened?
I was in aman ra recovery and i thought i was rooted. I also thought i had done a nandroid backup earlier, but apparently not. I flashed cleanrom, and when i rebooted, it got stuck on the white htc screen
If you are unlocked then just flash the kernel in fastboot.
If you are trying to install cleanrom 4.0 you need to run the leaked ruu first.
Sent from my ADR6425LVW using xda premium
Its literally too late for any of that. I can only access the bootloader or fastboot. There is no recovery installed now because it was only the temp one. If i had a way to get the stock ruu on the storage so it installs in the bootloader, then i may be able to fix my rezound, correct?
do you understand what brick means???
you are simply having user error.
Please re-name this thread!
andybones said:
do you understand what brick means???
you are simply having user error.
Please re-name this thread!
Click to expand...
Click to collapse
I apologize, but last time i checked a phone that doesnt boot is a bricked phone, whether it was user error or a problem with the device that caused it?
mdunn1066 said:
I apologize, but last time i checked a phone that doesnt boot is a bricked phone, whether it was user error or a problem with the device that caused it?
Click to expand...
Click to collapse
When your phone is bricked it literally means its a brick that won't bee good for anything than a paper weight
Your case, all you need to do is flash a new kernel
Sent from my ADR6425LVW using Tapatalk
superchilpil said:
When your phone is bricked it literally means its a brick that won't bee good for anything than a paper weight
Your case, all you need to do is flash a new kernel
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
Thank you for clarifying. Can you help me do this?
Also. Wouldn't it be possible to just fastboot oem lock, then put the RUU on an sd card using an sd card reader, and enter hboot and install that way?
Why do that? If you can fastboot oem lock, why not put the boot image that is in the PH98IMG.zip file, in the same directory as fastboot then type fastboot flash boot boot.img. Now you have your kernel installed.
EmerikL said:
Why do that? If you can fastboot oem lock, why not put the boot image that is in the PH98IMG.zip file, in the same directory as fastboot then type fastboot flash boot boot.img. Now you have your kernel installed.
Click to expand...
Click to collapse
Because I am inexperienced with ADB still and did not know i could, or how, to do that.
So far it looks to be working as its booting up, thanks a million. I feel sheepishly inexperienced but i guess we all start and learn somehow, right?
Yes we all start somewhere. It isn't the end of the world, live and learn.
Am having the same issue here
jmalone1187 said:
Am having the same issue here
Click to expand...
Click to collapse
I was able to fix mine by going to fastboot on the phone, going into the actual zip file that was the rom i flashed on my pc, and extracting the file named boot.img into my adb folder and then in the command window with the phone connected to the pc and in fastboot mode typing fastboot flash boot boot.img
Can you explain this process in a bit more detail?
I'm kind of new to HTC and not familiar with all the terms yet. Same thing happened to me trying to get the ICS leak on my phone.
I'm not familiar with ADB, and have minimal familiarity with ADB.
Am also having the same issue here
---------- Post added at 05:05 AM ---------- Previous post was at 04:38 AM ----------
my steps:
1 anlock from htcdev.com
2 re-lock bootloader
3 flash leaked RUU 3.11.605.22
4 unlock again
5 flash Amon Ra recovery
6 flash Scott's CleanROM ICS Edition Version 4.0
- enjoyed the week
- wanted to flash another rom
I put on the SD card RezROM_ICS_v3.1.zip and began to flash, forgetting the first re-lock, flash leaked RUU 3.11.605.22, unlock and then flash RezROM. (isn't it?)
Phone rebooted and there was a white HTC screen and nothing more.
Then I tried to fix it and flash leaked RUU 3.11.605.22 again (re-lock, put on the SD card PH98IMG.zip, flash, but after reboot I got the same white HTC screen and nothing)
pls someone could instruct me on the right path?
which means in Amon Ra recovery:
E: Can't mount /dev/block/mmcblk0p36 (File exists)
E: Can't mount CACHE: recovery/command
E: Can't mount /dev/block/mmcblk0p36 (File exists)
E: Can't mount CACHE: recovery/log
E: Can't open CACHE: recovery/log
E: Can't mount /dev/block/mmcblk0p36 (File exists)
and so after each attempt to flash any ROM
I can not understand what I do? pls help
Try pulling the battery & SD card, power up without SD. Do a factory reset. Are you currently in an unlocked state with a fresh .22 RUU installed?
Snuzzo said:
Try pulling the battery & SD card, power up without SD. Do a factory reset. Are you currently in an unlocked state with a fresh .22 RUU installed?
Click to expand...
Click to collapse
now I can not really answer, because that I have tried many options to fix this.
I tried it, power up without sd card and battery - factory reset. but in recovery still:
E: Can't mount /dev/block/mmcblk0p36 (File exists)
E: Can't mount CACHE: recovery/command
E: Can't mount /dev/block/mmcblk0p36 (File exists)
E: Can't mount CACHE: recovery/log
E: Can't open CACHE: recovery/log
E: Can't mount /dev/block/mmcblk0p36 (File exists)
in fastboot following info:
TAMPERED
RELOCKED
Security Warning
VIGOR PVT SHIP S-ON RL
HBOOT-2.21.0000
RADIO-1.22.10.0310r/1.22.10.0308r
OpenDSP-v13.6.0.7611.00.0101
eMMC-boot
Mar 11 2012
I also tried to flash original RUU_Vigor_VERIZON_WWE_2.01.605.11_Radio_RS_0.95.00 .1123r_3161E_9K_QMR_release_233635_signed.exe, but when I click the button to proceed and I get an error message stating it failed due to an invalid signature.
You can't RUU backwards and you need to re-unlock before attempting to flash another rom.
I am having one hell of a time installing the new 4.0.3 Android (Ice Cream Sandwich) update. Everything was going smoothly, downloaded update, atempted to install, but then it got stuck on the HTC logo loading screen when I first boot the phone.
Attempted factory reset, did not work. Attempted recovery, which i was prompted with a phone logo with a red exclimation mark. From there, i help Vol up and power button to get to another screen, wiped cache and attempted another factory reset. Nothing.
I have been looking into re-flashing the phone manually ( i know that this may void the warranty, but due to my location, sending it out is NOT an option). I have downloaded a ripped version of the OEM ROM that the phone came stock with, placed it in a freshly reformatted SD card, then i went back into the boot loader. Immediately, the phone picked it up, and I let the phone do its thing, still nothing.
Am I doing something wrong, or is my phone complete botched past the point of no return?
Any help regarding this issue is GREATLY appreciated. Don't make me go back to using my BB Torch >.>
I talked to a rogers customer support agent, who transfered me to a technician. The reason my phone will load the new ROM, but fail to reboot is because the internal memory is fried. The reason the phone failed during an update and not from regular use is because i NEVER shut off my phone, and the OS was always loaded.
Good thing flashing the phone dosen't void the warranty
Akutalji said:
I talked to a rogers customer support agent, who transfered me to a technician. The reason my phone will load the new ROM, but fail to reboot is because the internal memory is fried. The reason the phone failed during an update and not from regular use is because i NEVER shut off my phone, and the OS was always loaded.
Good thing flashing the phone dosen't void the warranty
Click to expand...
Click to collapse
I had the same issue, but could easily pass through.
The thing is that my original rom was android 2.3, and i wanted to update to ics 4
So i restored the original rom then done, like you the htc update.Wehn the phone has reboot, i faced the same problem as yours.
To make the phone boot correctly, i simply get the boot.img from the latest "TeamGenesis3DRom" then "fastboot flash boot boot.img"
then "fastboot reboot" ans the phone starts correctly.
Hope it will help you.
If you are on s-on you will alwais need to flash new roms using fastboot. You need to upload the boot.img in cmd on your computer. I would open the rom and copy it over to the folder that i used to unlockboot loader then open cmd on your computer then type cd \rootevo3dnew then type fastboot flash boot boot.img. Before you download anny other roms you need to get 4ext recovery from play store. That recovery will work every time you want to flash new roms when your on s-on without having to use your computer.
Install Custom Rom
I didnt read ur second post. I was suggesting u to install custom ROM. I hope ur poblem solved by now.
Arceo85 said:
If you are on s-on you will alwais need to flash new roms using fastboot. You need to upload the boot.img in cmd on your computer. I would open the rom and copy it over to the folder that i used to unlockboot loader then open cmd on your computer then type cd \rootevo3dnew then type fastboot flash boot boot.img. Before you download anny other roms you need to get 4ext recovery from play store. That recovery will work every time you want to flash new roms when your on s-on without having to use your computer.
Click to expand...
Click to collapse
I totally agree with.
But this case is very particular.
I can tell because i'm S-OFF and can flash any rom i wanr whithout fastboot.
But in this particular case, even with taking the boot.img from the rom deployed by HTC and then flash it through fastboot, the phone didn't passed the HTC screen.
As i said, i had to take the boot.img from a custom rom (in his case it was a predator or genesis rom).
Akutalji said:
I am having one hell of a time installing the new 4.0.3 Android (Ice Cream Sandwich) update. Everything was going smoothly, downloaded update, atempted to install, but then it got stuck on the HTC logo loading screen when I first boot the phone.
Attempted factory reset, did not work. Attempted recovery, which i was prompted with a phone logo with a red exclimation mark. From there, i help Vol up and power button to get to another screen, wiped cache and attempted another factory reset. Nothing.
I have been looking into re-flashing the phone manually ( i know that this may void the warranty, but due to my location, sending it out is NOT an option). I have downloaded a ripped version of the OEM ROM that the phone came stock with, placed it in a freshly reformatted SD card, then i went back into the boot loader. Immediately, the phone picked it up, and I let the phone do its thing, still nothing.
Am I doing something wrong, or is my phone complete botched past the point of no return?
Any help regarding this issue is GREATLY appreciated. Don't make me go back to using my BB Torch >.>
Click to expand...
Click to collapse
the easiest way to fix your issue is to download the latest RUU from here then just rename it to PG86IMG, but first you have to relock your bootloader, vol down + power, then go to fast boot and type in command prompt "fastboot oem lock" and once you have the RUU on the root of your SD card boot back into bootloader and it will say **relocked** and then it will recognize the "PG86IMG" and it will check the file and ask you if you want to update, it will then install and everything should be hunky dory, I recommend after that, unlock your bootloader again via the HTCdev method and then make your phone s-off and then start flashing roms as often as you want without any issues
Arceo85 said:
If you are on s-on you will alwais need to flash new roms using fastboot. You need to upload the boot.img in cmd on your computer. I would open the rom and copy it over to the folder that i used to unlockboot loader then open cmd on your computer then type cd \rootevo3dnew then type fastboot flash boot boot.img. Before you download anny other roms you need to get 4ext recovery from play store. That recovery will work every time you want to flash new roms when your on s-on without having to use your computer.
Click to expand...
Click to collapse
Just for the hell of it, I tried it.
I downloaded fastboot, and got my hands on the stock .img for the evo. Still the same issue, the bootloader loads the new image but never asks to reboot.
Memory is fried They are now sending me a new phone
Hi there everyone!
My main problem is flashing hboot 1.15
I misinterpreted a sentence of instructions over at ViperDNA ROM thread, and attempted to flash Viper 1.3.0 with a custom kernel (it had been so long, I forget which. Cubed or DSB, idk) and after getting through aroma and successfully installing, it was stuck at a bootloop. Well I went back and read the instructions and comment again and apparently installing with anything other than Stock boot.img is a big no no. Anyways, I am stuck here without any type of ROM (relocking the bootloader to attempt to RUU.exe left my internal storage wiped) and unable to get the RUU.exe method to work (Error 155 most likely because I have hboot version 1.33.0001 and not 1.15). I cannot get the RUU.exe or the RUU.zip flash method to work. I have flashed a stock boot.img since then and have gone through different locked/relocked stages and tried ADB sideloading a stock ROM ("unable to mount /data /system" etc.). Right now, I am trying (using the HTC Droid DNA Toolkit program) to flash the 1.15 hboot, but it is stuck at "<waiting for device>". I have also tried "fastboot.exe fastboot oem rebootRUU" and got the same response. I don't know what else to do and I am deeply worried that I have bricked my DNA. I understand that I am completely responsible for attempting these things and for my errors, but I need help in getting back to any form of android so that I can reinstall Viper 1.3.0 with a stock boot.img (like I should have in the first place).
I appreciate all of your help and I hope someone knows what can be done here! Thank you guys!
Mcsquizzy said:
Hi there everyone!
My main problem is flashing hboot 1.15
I misinterpreted a sentence of instructions over at ViperDNA ROM thread, and attempted to flash Viper 1.3.0 with a custom kernel (it had been so long, I forget which. Cubed or DSB, idk) and after getting through aroma and successfully installing, it was stuck at a bootloop. Well I went back and read the instructions and comment again and apparently installing with anything other than Stock boot.img is a big no no. Anyways, I am stuck here without any type of ROM (relocking the bootloader to attempt to RUU.exe left my internal storage wiped) and unable to get the RUU.exe method to work (Error 155 most likely because I have hboot version 1.33.0001 and not 1.15). I cannot get the RUU.exe or the RUU.zip flash method to work. I have flashed a stock boot.img since then and have gone through different locked/relocked stages and tried ADB sideloading a stock ROM ("unable to mount /data /system" etc.). Right now, I am trying (using the HTC Droid DNA Toolkit program) to flash the 1.15 hboot, but it is stuck at "<waiting for device>". I have also tried "fastboot.exe fastboot oem rebootRUU" and got the same response. I don't know what else to do and I am deeply worried that I have bricked my DNA. I understand that I am completely responsible for attempting these things and for my errors, but I need help in getting back to any form of android so that I can reinstall Viper 1.3.0 with a stock boot.img (like I should have in the first place).
I appreciate all of your help and I hope someone knows what can be done here! Thank you guys!
Click to expand...
Click to collapse
I can tell you that it's not bricked just having a bit of bad luck.
First off try a different USB port, second there really isn't a need to RUU if all you are doing is trying to reflash a rom correctly.
you didnt happen to flash the boot.img to the hboot partiton? cause that would be bad. (DO NOT DO THIS)
try this: boot into recovery and plug the device into the computer then try adb devices and see if the device ID pops up if in fact it does do a:
adb push romzip.zip /sdcard/romzip.zip
or
adb push \path\to\romzip.zip /sdcard/romzip.zip
and it will push it to the /sdcard directory, then reboot the recovery and flash the rom and it should just work
.torrented said:
I can tell you that it's not bricked just having a bit of bad luck.
First off try a different USB port, second there really isn't a need to RUU if all you are doing is trying to reflash a rom correctly.
you didnt happen to flash the boot.img to the hboot partiton? cause that would be bad. (DO NOT DO THIS)
Click to expand...
Click to collapse
I have tried on another (Windows 7 64-bit laptop with correct drivers) computer and multiple USB ports. In the process of unlocking/relocking using an AllInOne Toolkit, it wiped everything from my internal storage (as it said it would). I can flash kernels and recoveries (using TWRP atm) but when I try to flash a ROM (installing using the TWRP recovery) I get messages saying "unable to mount /data" or "unable to mount /cache" and I am unable to check the boxes "Mount Data" and "Mount Cache" within the recovery (I can only check "Mount System" and thus I am unable to wipe/ factory reset/flash a ROM. I have no idea if I flashed a boot.img to the hboot partition, but I have only flashed a boot.img using the Droid DNA All in One Toolkit and also by using the "fastboot flash boot boot.img" command. How can I tell if I flashed it to the hboot partition? I am able to get into bootloader and reboot into RUU using the "oem rebootRUU" command, if that helps determine whether or not I messed up. I recieve a "Error [155]" message every time I use the RUU.exe on both computers, and I read on another post that this could be caused by the wrong hboot version (RUU.exe 'wants' a 1.15 hboot version, but my bootloader is saying I have the 1.33.0001 hboot version) on my DNA. Perhaps this is the cause? In any case, I have been working to flash the 1.15 hboot so that I can successfully flash the RUU.
Thank you for your help and patience!
Mcsquizzy said:
I have tried on another (Windows 7 64-bit laptop with correct drivers) computer and multiple USB ports. In the process of unlocking/relocking using an AllInOne Toolkit, it wiped everything from my internal storage (as it said it would). I can flash kernels and recoveries (using TWRP atm) but when I try to flash a ROM (installing using the TWRP recovery) I get messages saying "unable to mount /data" or "unable to mount /cache" and I am unable to check the boxes "Mount Data" and "Mount Cache" within the recovery (I can only check "Mount System" and thus I am unable to wipe/ factory reset/flash a ROM. I have no idea if I flashed a boot.img to the hboot partition, but I have only flashed a boot.img using the Droid DNA All in One Toolkit and also by using the "fastboot flash boot boot.img" command. How can I tell if I flashed it to the hboot partition? I am able to get into bootloader and reboot into RUU using the "oem rebootRUU" command, if that helps determine whether or not I messed up. I recieve a "Error [155]" message every time I use the RUU.exe on both computers, and I read on another post that this could be caused by the wrong hboot version (RUU.exe 'wants' a 1.15 hboot version, but my bootloader is saying I have the 1.33.0001 hboot version) on my DNA. Perhaps this is the cause? In any case, I have been working to flash the 1.15 hboot so that I can successfully flash the RUU.
Thank you for your help and patience!
Click to expand...
Click to collapse
Well... I just kept trying the RUU.exe over and over and over again and it finally worked I don't believe I did anything different, but I have tried so many different things I completely lost track Anyways, thank you for your help and patience, again
Mcsquizzy said:
Well... I just kept trying the RUU.exe over and over and over again and it finally worked I don't believe I did anything different, but I have tried so many different things I completely lost track Anyways, thank you for your help and patience, again
Click to expand...
Click to collapse
I flashed Viper 1.3.0 with BeastMode 5.9 and it's running fine no bootloops of any sort