Hello!
I installed Munjeni's special hboot partition (to increase usable space) and wanted to update the phone back to stock (to take back to att).
The RUU utility failed with code of 152.
The partition failed.
Now the phone is "stuck" at the black HTC screen with four warning triangles in each corner.
Any ideas?
I can fastboot and issue some commands...
I am s-on, hboot 1.02.
Thanks in advance!
DanGeorges said:
Hello!
I installed Munjeni's special hboot partition (to increase usable space) and wanted to update the phone back to stock (to take back to att).
The RUU utility failed with code of 152.
The partition failed.
Now the phone is "stuck" at the black HTC screen with four warning triangles in each corner.
Any ideas?
I can fastboot and issue some commands...
I am s-on, hboot 1.02.
Thanks in advance!
Click to expand...
Click to collapse
If the bootloader is accessible, you can try grabbing the rom.zip out of the RUU (run it & let it load, then search in Windows' temporary folder for "rom.zip". If not there's probably a download somewhere), and rename it to "LIBEIMG.zip" on the root of the SD card.
Then boot into the bootloader (vol down) and it should pick it up and start flashing (might be a confirmation before it does)
Edit: Well I looked at the title again... does this mean its not accessible?
It should be if fastboot is, but I've never had the bad triangles so not completely sure..
If not, alternate option that may work: extract the hboot image from rom.zip and flash it with fastboot (if its allowed)
This is the RUU zip: http://www.mediafire.com/?tay1j415ymvukh5
drumist said:
This is the RUU zip: http://www.mediafire.com/?tay1j415ymvukh5
Click to expand...
Click to collapse
Thank you for the link. I'm downloading it now.
I can fastboot, but I'm S-on (from one of my flashes).
What's the fastboot command for flashing the hboot? Will this even let me?
I'll give this a try. Thanks again!
When I try to fastboot flash a recovery, here's what I get:
C:\Mobile\Android\Fastboot and ADB Tool>fastboot flash recovery recovery.img
sending 'recovery' (3716 KB)... OKAY [ 0.875s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 1.578s
C:\Mobile\Android\Fastboot and ADB Tool>
For hboot - does anyone have an idea which hboot I can try flashing?
WinSuk said:
If the bootloader is accessible, you can try grabbing the rom.zip out of the RUU (run it & let it load, then search in Windows' temporary folder for "rom.zip". If not there's probably a download somewhere), and rename it to "LIBEIMG.zip" on the root of the SD card.
Then boot into the bootloader (vol down) and it should pick it up and start flashing (might be a confirmation before it does)
Edit: Well I looked at the title again... does this mean its not accessible?
It should be if fastboot is, but I've never had the bad triangles so not completely sure..
If not, alternate option that may work: extract the hboot image from rom.zip and flash it with fastboot (if its allowed)
Click to expand...
Click to collapse
I'll try the hboot image and see what happens.
What's the fastboot command?
I tried:
fastboot flash hboot
and
fastboot flash boot
Both gave me an invalid signature:
C:\>fastboot flash hboot hboot_liberty_7227_1.02.0000_101104.nb0
sending 'hboot' (512 KB)... OKAY [ 0.234s]
writing 'hboot'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 0.328s
C:\>fastboot flash boot hboot_liberty_7227_1.02.0000_101104.nb0
sending 'boot' (512 KB)... OKAY [ 0.234s]
writing 'boot'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 0.328s
So last week a friend asked me to s-off his phone for him.. The phone ended up bricking (recovery gone, no os, etc...)..
Where I am at:
1. The phone is S-ON (Actually says "Monarudo PVT Ship S-ON"
2. The phone has an unlocked boot loader
3. The phone has TWRP 2.4 installed
4. HBoot 1.33
5. Radio 1.01.01.0110
6. OpenDSP v6.120.274.0114
7. eMMC-boot
8. The phone has a 4.1.1 based rom installed (Tried carbon 4.3 based, same issue and CM 4.2 based, same issue)
I have tried moonshine and face's s-off with no luck. I get about half way through with moonshine and it just sits there counting, adding periods.
I have tried :
1. Flashing a stock hboot 1.15
2. Flashing the stock splash
3. Flashing the stock RUU
Issues :
1. The phone gets NO reception Just the X with empty bars. I don't know if its the radio or something. Every once and a while I get 2 bars for a second but it goes away.
PLEASE HELP! I feel horrible that my buddy has to borrow my bionic until this is fixed.
when I tried the stock RUU from HTC it gets to a point and fails telling me incorrect image or seomthing like that.. Should have written it down, I can run it again if the error helps.
janderson2k said:
when I tried the stock RUU from HTC it gets to a point and fails telling me incorrect image or seomthing like that.. Should have written it down, I can run it again if the error helps.
Click to expand...
Click to collapse
Have you tried doing moonshine in ubuntu live cd/usb?
janderson2k said:
So last week a friend asked me to s-off his phone for him.. The phone ended up bricking (recovery gone, no os, etc...)..
Where I am at:
1. The phone is S-ON (Actually says "Monarudo PVT Ship S-ON"
2. The phone has an unlocked boot loader
3. The phone has TWRP 2.4 installed
4. HBoot 1.33
5. Radio 1.01.01.0110
6. OpenDSP v6.120.274.0114
7. eMMC-boot
8. The phone has a 4.1.1 based rom installed (Tried carbon 4.3 based, same issue and CM 4.2 based, same issue)
I have tried moonshine and face's s-off with no luck. I get about half way through with moonshine and it just sits there counting, adding periods.
I have tried :
1. Flashing a stock hboot 1.15
2. Flashing the stock splash
3. Flashing the stock RUU
Issues :
1. The phone gets NO reception Just the X with empty bars. I don't know if its the radio or something. Every once and a while I get 2 bars for a second but it goes away.
PLEASE HELP! I feel horrible that my buddy has to borrow my bionic until this is fixed.
Click to expand...
Click to collapse
Try
1 You need update to new Firmware 2.06 (for moonshine)
2 You need to Re lock Bootloader in order to RUU
3 you need to downgrade Hboot to 1.15 to RUU ( your phone show 1.33)
http://forum.xda-developers.com/showthread.php?t=2293919&highlight=flash+radio
Hope this help buddy
finanandroid said:
Try
1 You need update to new Firmware 2.06 (for moonshine)
2 You need to Re lock Bootloader in order to RUU
3 you need to downgrade Hboot to 1.15 to RUU ( your phone show 1.33)
http://forum.xda-developers.com/showthread.php?t=2293919&highlight=flash+radio
Hope this help buddy
Click to expand...
Click to collapse
Anyone have a recommended method to downgrade the hboot? I havnt been able to get the 1.15 to flash to the phone.. Relocking the bootloader is cake.
I appreciate your help, Sorry if I sound n00bish.
janderson2k said:
Anyone have a recommended method to downgrade the hboot? I havnt been able to get the 1.15 to flash to the phone.. Relocking the bootloader is cake.
I appreciate your help, Sorry if I sound n00bish.
Click to expand...
Click to collapse
Every one learn everyday.
Download 1.15 stock hboot. Rename to PL83IMG.zip. when u renamed it make sure is not zip.zip cause this file is already zip so u try only to rename it to PL83IMG (right click the file in your pc and check properties to make sure windows got it already as a zip extension) and place in the folder that contains ( in ur pc) your android-adb folder*
there is where any zip should go, with the exception of user preferences location. (or different folder named by the user)
Step 1) adb reboot bootloader
Step 2) fastboot oem rebootRUU
Step 3) Command to directory containing your renamed hboot zip (i.e. C:\android-adb\)
Step 4) fastboot flash zip PL83IMG.zip
*** When it says it is done in the terminal/cmdprompt execute step 5 )
[The green bar only fills up about 75% of the way]
Step 5) fastboot reboot-bootloader
Profit. Put the RUU Folder in same directory. right click and run it as administrator
soff
W00t! S-Off is done.. HBoot time....
?
finanandroid said:
Every one learn everyday.
Download 1.15 stock hboot. Rename to PL83IMG.zip. when u renamed it make sure is not zip.zip cause this file is already zip so u try only to rename it to PL83IMG (right click the file in your pc and check properties to make sure windows got it already as a zip extension) and place in the folder that contains ( in ur pc) your android-adb folder*
there is where any zip should go, with the exception of user preferences location. (or different folder named by the user)
Step 1) adb reboot bootloader
Step 2) fastboot oem rebootRUU
Step 3) Command to directory containing your renamed hboot zip (i.e. C:\android-adb\)
Step 4) fastboot flash zip PL83IMG.zip
*** When it says it is done in the terminal/cmdprompt execute step 5 )
[The green bar only fills up about 75% of the way]
Step 5) fastboot reboot-bootloader
Profit. Put the RUU Folder in same directory. right click and run it as administrator
Click to expand...
Click to collapse
So I am not sure whats up but I went through the process :
Code:
C:\adb>fastboot oem rebootRUU
< waiting for device >
...
(bootloader) Start Verify: 0
OKAY [ 0.051s]
finished. total time: 0.052s
C:\adb>fastboot flash zip PL83IMG.zip
< waiting for device >
sending 'zip' (434 KB)...
OKAY [ 0.218s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping & flushing...
(bootloader) [RUU]UZ,hboot,0
(bootloader) [RUU]UZ,hboot,50
(bootloader) [RUU]UZ,hboot,100
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
OKAY [ 2.020s]
finished. total time: 2.241s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.048s
and when I get back to bootloader it still says HBoot 1.33.. I used this hboot : http://www.mediafire.com/download.php?pj2lknq5gr0jkmf
Any ideas?
I have the same Problem,but my Phone ist S-ON and Locked with H-Boot 1.33
Radio 1.01.04.0308
OpenDSP v4.120.240.0920
No Recovery,no Root,aahh
I can´t Unlock the Bootloader
Error Code: 160.
Error Reason: MID Not Allowed.
I can´t Downgrade to 1.15
c:\ADB>fastboot flash zip PL83IMG
sending 'zip' (434 KB)...
OKAY [ 0.203s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 0.250s
What can i do?
Should I try RUU now or do I need hboot @ 1.15?
janderson2k said:
Should I try RUU now or do I need hboot @ 1.15?
Click to expand...
Click to collapse
yes u need Hboot, but you did before unlock, s-off with moonshine method or revone?
you can try RUU now but If you get an Image 158 error during RUU, try flashing the stock hboot again.
All sorted out.. Thanks everyone. I s offed, unlocked, and flashed new radio. All is well
Sent from my SCH-I605 using Tapatalk 2
letschky said:
I have the same Problem,but my Phone ist S-ON and Locked with H-Boot 1.33
Radio 1.01.04.0308
OpenDSP v4.120.240.0920
No Recovery,no Root,aahh
I can´t Unlock the Bootloader
Error Code: 160.
Error Reason: MID Not Allowed.
I can´t Downgrade to 1.15
c:\ADB>fastboot flash zip PL83IMG
sending 'zip' (434 KB)...
OKAY [ 0.203s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 0.250s
What can i do?
Click to expand...
Click to collapse
Is there no possibility?
I wanted Moonshine S-OFF,'ve updated the firmware and forgot to unlock the bootloader.
Now I have the software version 1.15.605.1, but the HBOOT version is 1.33 wlan can not be switched on and the screen flickers often know clearly wrong boot.img of the software2.06 and the modules from 1.15.
and I can not unlock the bootloader also'm not unlock with my old Unlock_code.bin.
I know now no longer continue...
Go here http://chat.andirc.net:8080/?channels= this People help
Today I had the same problem in my 10 minutes dna worked again
My HTC 3D (CDMI) suddenly broke, during night charge - i just found it at the morning with bright screen and HTC logo on it. It stays like that after power off/on for hours, untill full battery discharge. I don't understand what might happen to it. Any ideas? It was rooted (a year+ ago) and worked just fine untill the last moment.
It boots to recovery mode fine (Power + Vol down), it has HBOOT-1.58.0000 Radio-1.09.000706, OpenADSP-v02.6.0.2226.00.0217. It has TWRP 2.2 (looks the latest from the twrp site, for these phones afaik), so i tried to wipe cache , etc, and reflash CM-11 rom. The log says:
Can't mount /cache
Failed closing /dev/block/mmcblk0p34
Unable to mount '/system' (tw_mount)
Unable to mount '/data' (tw_mount)
Unable to mount '/cache' (tw_mount)
It seems to install VILLUMINATI-12082013-shooter.zip and gapps-20131119.zip, but after reboot i see just the same bright screen with HTC logo, and nothing else.
Any ideas what can i do to fix it? Is it hardware fail or (hopefully) just software glitch? That "Unable to mount" error messages from the recovery seems disturbing.
run an official ruu
Sent from my Evo 3D GSM using XDA Premium 4 mobile app
Anonymuszymus said:
run an official ruu
Sent from my Evo 3D GSM using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well, the phone doesn't seem to be able to flash any update so far, officail or not-official. May be there is a trick to do it?
What ROM were you running?
With hboot 1.58 you can only flash ICS sense....
Sent from my Evo 3D CDMA using xda app-developers app
relock your bootloader,reboot to bootloader ,connect the fastboot and try again
Sent from my Evo 3D GSM using XDA Premium 4 mobile app
Anonymuszymus said:
relock your bootloader,reboot to bootloader ,connect the fastboot and try again
Click to expand...
Click to collapse
The recovery mode screen says "*** LOCKED *** SHOOTER XC SHIP S-OFF RL " on the top, i assume it's locked. I can't get to the system settings and get "USB debugging" to on, but i think it was set that way from the last time i flashed something on the phone (was ~6-9 month ago, i don't remember exactly what ROM/version was that, most probably ENERGY Rom, worked fine).
I use linux to do stuff, so lsusb show this, if i just torn phone on (to the screen with HTC logo):
Bus 002 Device 013: ID 0bb4:0ff9 High Tech Computer Corp. Desire / Desire HD / Hero (Charge Mode)
./adb-linux devices
List of devices attached -- shows nothing.
If i boot it into recovery mode and then choose "fastboot" from the menu, the phone screen shows "FASTBOOT USB" with 4 options: Bootloader, Reboot, Reboot bootloader, Power down, and on the laptop lsusb shows the item without changing mode:
Bus 002 Device 014: ID 0bb4:0ff0 High Tech Computer Corp.
But, ./adb-linux devices
List of devices attached -- still shows nothing.
Any ideas, how to get it connected to adb, or better flash via cf-card?
u dont need to select anything after u selected the FASTBOOT,u can run the RUU with linux Vine tricks or what is that...but i don't know how to resolve the driver problem
Sent from my Evo 3D GSM using XDA Premium 4 mobile app
---------- Post added at 07:31 PM ---------- Previous post was at 07:30 PM ----------
try just to run it...maybe it works without installing any special driver from our PC
Sent from my Evo 3D GSM using XDA Premium 4 mobile app
Anonymuszymus said:
u dont need to select anything after u selected the FASTBOOT,u can run the RUU with linux Vine tricks or what is that...but i don't know how to resolve the driver problem
Click to expand...
Click to collapse
Yes, i didn't choose any of that options in Fastboot menu (in the phone recovery mode). On the laptop i did
sudo ./fastboot devices
HT17AHX00819 fastboot
-- so device was seen by fastboot, finally! (but adb can't see it, still). I try to follow this guide http://forum.xda-developers.com/showthread.php?t=2277112 to install the new image, and got this:
$ sudo ./fastboot erase system -w
fastboot erase system -w
erasing 'system'...
FAILED (remote: not allowed)
finished. total time: 0.002s
$ sudo ./fastboot erase boot
erasing 'boot'...
FAILED (remote: not allowed)
finished. total time: 0.003s
sudo ./fastboot erase cache
erasing 'cache'...
OKAY [ 1.582s]
--------- I tried to install ROM anyway, and it failed (after reading i understand that ONLY OFFICIAL updates have these android-info.txt, android-product.txt files ):
sudo ./fastboot update VILLUMINATI-12082013-shooter.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
So question is how to flash new custom ROMs via flashboot, if they don't have required (is it flashboot hard requrement or it can be skiped?) android-info.txt and android-product.txt, and may be sig files too? Or my options are only official updates now? Official update (from here http://forum.xda-developers.com/wiki/HTC_Evo_3D/CDMA#Official_Rom_Update_Utilities) PG86IMG-Sprint_2.95.651.5_firmware.zip for example doesn't have boot.img:
sudo ./fastboot update PG86IMG-Sprint_2.95.651.5_firmware.zip
archive does not contain 'boot.img'
error: update package missing boot.img
I also found a Win 7 computer, and try to put Stock Rooted Roms with SuperUser 2.89.651.2 Update (4.0.3) - (Tribulattifather-Fixes) (from http://forum.xda-developers.com/wiki/HTC_Evo_3D/CDMA). The updating process starts fine and go till 23%, where it freezes on "Updating Signature" part, where dots (.....) appear on the utility window and nothing happens for 30-40 minutes, until i had to pull the USB cable. Now phone boots to black screen with HTC logo and exclamation sight at each corner. RUU update process freezes at the same point every time i try to repeat it.
Again, adb doesn't see the device, but fastboot sees it.
Any suggestions?
I also found a Win 7 computer, and try to put Stock Rooted Roms with SuperUser 2.89.651.2 Update (4.0.3) - (Tribulattifather-Fixes) (from http://forum.xda-developers.com/wiki/HTC_Evo_3D/CDMA). The updating process starts fine and go till 23%, where it freezes on "Updating Signature" part, where dots (.....) appear on the utility window and nothing happens for 30-50 minutes, until i had to pull the USB cable. Now phone boots to black screen with HTC logo and exclamation sight at each corner. RUU update process freezes at the same point every time i try to repeat it.
Again, adb doesn't see the device, but fastboot sees it.
Any suggestions?
Flash RUU from bootloader using PG86IMG.zip
Sent from my Evo 3D CDMA using Tapatalk
luk1 said:
I also found a Win 7 computer, and try to put Stock Rooted Roms with SuperUser 2.89.651.2 Update (4.0.3) - (Tribulattifather-Fixes) (from http://forum.xda-developers.com/wiki/HTC_Evo_3D/CDMA). The updating process starts fine and go till 23%, where it freezes on "Updating Signature" part, where dots (.....) appear on the utility window and nothing happens for 30-50 minutes, until i had to pull the USB cable. Now phone boots to black screen with HTC logo and exclamation sight at each corner. RUU update process freezes at the same point every time i try to repeat it.
Again, adb doesn't see the device, but fastboot sees it.
Any suggestions?
Click to expand...
Click to collapse
you are stucked in RUU boot,you can exit from it via fastboot typibg fastboot reboot-bootloader...what commands are you used ??
Sent from my Evo 3D GSM using XDA Premium 4 mobile app
As i found here (http://forum.xda-developers.com/showthread.php?t=2226801&page=2 ), to pass the "black screen with exclamation signs on each corner"and flash official RUU in form of zip file, i used these commants, looks like it works:
sudo ./fastboot flash zip PG86IMG-Sprint_2.95.651.5_firmware.zip
sending 'zip' (8408 KB)...
OKAY [ 1.892s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[radio] unzipping & flushing...
(bootloader) [RUU]UZ,radio,0
(bootloader) [RUU]UZ,radio,5
(bootloader) [RUU]UZ,radio,11
(bootloader) [RUU]UZ,radio,17
(bootloader) [RUU]UZ,radio,23
(bootloader) [RUU]UZ,radio,29
(bootloader) [RUU]UZ,radio,35
(bootloader) [RUU]UZ,radio,41
(bootloader) [RUU]UZ,radio,47
(bootloader) [RUU]UZ,radio,52
(bootloader) [RUU]UZ,radio,59
(bootloader) [RUU]UZ,radio,64
(bootloader) [RUU]UZ,radio,71
(bootloader) [RUU]UZ,radio,76
(bootloader) [RUU]UZ,radio,82
(bootloader) [RUU]UZ,radio,88
(bootloader) [RUU]UZ,radio,94
(bootloader) [RUU]UZ,radio,99
(bootloader) [RUU]UZ,radio,100
(bootloader) [RUU]WP,radio,0
(bootloader) [RUU]WP,radio,94
(bootloader) [RUU]WP,radio,100
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) [RUU]UZ,rcdata,0
(bootloader) [RUU]UZ,rcdata,100
(bootloader) [RUU]WP,rcdata,0
(bootloader) [RUU]WP,rcdata,100
OKAY [ 10.500s]
finished. total time: 12.393s
$ sudo ./fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.289s]
finished. total time: 0.289s
The phone rebooted into white screen with HTC logo, then after 3-4 min waiting - into TWRP recovery menu. So i tried to install CM-11 VILLUMINATI-12082013-shooter.zip again. And it failed again with this:
sysmlink: some symlinks failed
E: Error in /sdcard/VILLUMINATI-12082013-shooter.zip (status 7)
E:Unable to moint '/data' (tw_mount)
I don't really know why the flashing fails. May be i need to try another ROM? Also, is there a way to check that internal memory is OK, and there is no hardware problems with a phone?
Error flashing zip '/sdcard/VILLUMINATI-12082013-shooter.zip'
i think the problem is u not cleared the cache before flashing ruu ... the most simply method is to run the .exe version of the ruu,you can run it on linux with Vine...or try again via fastboot and clear the cache before
and be sure u have the latest version of official update not the old and the cdma version not the gsm
Sent from my Evo 3D GSM using XDA Premium 4 mobile app
Ok, the question is now - how to wipe tha cache? If i do it from the TWRP recovery menu, i'm getting this:
E:failed to mount /cache (Invalid argument)
* Verifying filesystems...
* Verifying partition sizes...
E:Unable to mount "/system' (tw_mount)
E:Unable to mount '/data' (tw_mount)
E:Unable to mount '/cache' (tw_mount)
For the Dalvik Cache:
Cleaned: /data/dalvik-cache...
Cleaned: /cache/dalvik-cache...
Cleaned: /cache/dc
/sd-ext not present. skipping
--Dalvik Cache Directories Wipe complete!
E:Unable to mount "/system' (tw_mount)
E:Unable to mount '/data' (tw_mount)
E:Unable to mount '/cache' (tw_mount)
So i'm not sure that wiping is possible that way. But, when i start to flash negalite-blurom_r115.zip (Negalite ROM), the script offers to wipe a cache before installation, and it seems that wipe is complete. Installation script freezes at 40% though, at "Installing all optional Stock files" stage - it stays there for 30-40 mins already
Well, after i choosed "No stock apps" in the Negalite install script, it finally completed the install, the only complain was:
assert failed:write_raw_image("/tmp/newboot.img", "boot").
After reboot it shows well known to me white screen with HTC logo - and nothing else happens
for cache wipe write in fastboot : fastboot erase cache
u can try to wipe the data to:fastboot erase data
Sent from my HTC X515d using XDA Premium 4 mobile app
I wiped the cache as good as i can (via TWRP recovery menu), and again tried to install 2 versions of official RUU. Both stalled at 23-24%, just freezed forever. I restored the normal state via flashing PG86IMG-Sprint_2.95.651.5_firmware, as before:
sudo ./fastboot flash zip PG86IMG-Sprint_2.95.651.5_firmware.zip
Then, it appears that TWRP does have version 2.6.3.0 for this phone (hard to find though, it's only here http://techerrata.com/browse/twrp2/shooter , but not on the unit page http://teamw.in/project/twrp2/67). So, after installing it, wiping the cache etc, i try to install VILLUMINATI-12082013-shooter.zip again. Script works for 5 mins, says it's "successful" at the end. But log shows this:
E:Unable to mount '/cache'
Formatting Cache using mke2fs...
Done
Formatting Data using mke2fs...
Done
Wiping Android Secure
Updating partition details...
Installing '/sdcard/VILLUMINATI-12082013-shooter.zip'
Updating partition details...
E:Unable to mount '/data'
E:Unable to mount '/system'
After the reboot i see the same old white screen with green HTC logo, forever. No system boot, nothing.
So i'm not sure what's going on, was it installed at all? How can i check that something actually was installed? And- How comes that it's Unable to mount '/system' , /data ? Does it mean hardware problem, or something else?
Hey folks,
I'm trying to install a recovery image using fastboot, as per the directions presented here:
http://wiki.cyanogenmod.org/w/Install_CM_for_fireball
When I try flashing the recovery, I get the following error message:
Code:
sudo fastboot flash recovery recovery-clockwork-6.0.4.6-fireball.img
sending 'recovery' (7784 KB)...
OKAY [ 1.117s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.149s
I was able to obtain S-OFF following the directions presented in this thread:
http://forum.xda-developers.com/showthread.php?t=2664460
but I am now currently in "relocked" state because I followed step 5 and tried running DirtyRacun.
Phone: HTC incredible 4g lte.
hboot: 1.15.0000
radio: 1.53.06.0919
OpenDSP-v29.1.0.45.0622
Thanks in advance!
in other news ...
My phone is in an unusable state. I still have access to the bootloader, and when it's plugged into my computer, I have access to it through adb, but otherwise, I can't send or receive phone calls from it.
stringedonbass said:
My phone is in an unusable state. I still have access to the bootloader, and when it's plugged into my computer, I have access to it through adb, but otherwise, I can't send or receive phone calls from it.
Click to expand...
Click to collapse
Apparently shutting down and pulling the battery "fixes" that problem.
Step 5 was not to run dirty racoon it was to flash the engineering hboot from the DirtyRacun webpage, but with S-off you should still be able to flash the hboot and recovery.
I find this page useful when I am working in ADB to keep the ideas fresh. http://forum.xda-developers.com/showthread.php?t=2141817
stringedonbass said:
Hey folks,
I'm trying to install a recovery image using fastboot, as per the directions presented here:
http://wiki.cyanogenmod.org/w/Install_CM_for_fireball
When I try flashing the recovery, I get the following error message:
Code:
sudo fastboot flash recovery recovery-clockwork-6.0.4.6-fireball.img
sending 'recovery' (7784 KB)...
OKAY [ 1.117s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.149s
I was able to obtain S-OFF following the directions presented in this thread:
http://forum.xda-developers.com/showthread.php?t=2664460
but I am now currently in "relocked" state because I followed step 5 and tried running DirtyRacun.
Phone: HTC incredible 4g lte.
hboot: 1.15.0000
radio: 1.53.06.0919
OpenDSP-v29.1.0.45.0622
Thanks in advance!
Click to expand...
Click to collapse
Re: adb guide
wmuflyer said:
Step 5 was not to run dirty racoon it was to flash the engineering hboot from the DirtyRacun webpage, but with S-off you should still be able to flash the hboot and recovery.
I find this page useful when I am working in ADB to keep the ideas fresh. http://forum.xda-developers.com/showthread.php?t=2141817
Click to expand...
Click to collapse
That's a nice guide on the Android Debug Bridge (abd). As a side note, I was pleased to find that fastboot and adb can be found in Ubuntu's repositories.
Update: flashed DirtyRacun's HBOOT
My phone now says
-- DirtyRacun --
at the top of the bootloader. No need to "unlocking" the phone because it was already in S-OFF state. After downloading the HBOOT file from unlimited's fireball website, I typed these commands, also available from their website:
Code:
sudo ./fastboot erase cache
sudo ./fastboot oem rebootRUU
sudo ./fastboot flash zip [file name]
sudo ./fastboot reboot
Happily rooted with CyanogenMOD installed
I'm happily rooted and have CyanogenMOD up and running.
After flashing the engineering hboot onto my phone using unlimited's directions, I was able to install ClockworkMod Recovery for fireball following the directions posted on their website.
Code:
sudo fastboot flash recovery recovery-clockwork-6.0.4.6-fireball.img
sending 'recovery' (7784 KB)...
OKAY [ 1.141s]
writing 'recovery'...
OKAY [ 2.129s]
finished. total time: 3.271s
I then was able to install CyanogenMod from recovery like "clockwork". Of course, "abd reboot-bootloader" is much faster than the crazy key combinations they ask you do to. When asked to install from sdcard, there were two locations to look at.
Cheers everyone! :victory: