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?
Related
Hi All,
Sometime ago I was able to install android 4.3 using the moonshine method. After sometime, I decided to go back to stock. I followed a tutorial on how to get back to stock RUU.
-Entered Boot loader, typed in cmd prompt "fastboot oem lock" received the word that lock was successful.
-Proceeded to run the RUU executable file 1.15 but received the "158 error"
Now my phone has been wiped of any OS since I relocked the phone, but it still says "moonshine s-off".
I tried to use TWRP recovery adb sideload the proper hboot file to match the RUU but get this message
Failed
Updating partition details...
E:Unable to mount '/cache'
E:Unable to mount '/cache'
E:TWFunc::Copy_Log -- Can't open destination lo
E:Unable to mount '/cache'
Starting ADB sideload feature...
Installing '/data/media/0/sideload.zip
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
WRONG OPERATION!
E:Error executing updater binary in zip'data/
I am at a complete loss as what to do now. I've been at this for 3 hours now and its driving me crazy. PLEASE HELP!
Can anyone walk me through the steps of pushing the hboot zip via adb sideload?
Will adb sideload not work if my fastboot is locked?
I tried to follow this tutorial to go back to stock because I S-OFF'd moonshine
http://forum.xda-developers.com/showthread.php?t=2293919
My issue is trying to copy the lock bootloader zip file to my phone. Adb sideload is not working, there is no OS since I did the "fastboot oem lock" wiped my phone.
I tried to do a restore in TRWP but after it finished, when starting its stuck on the CM splash screen.
Please help.......................
sideshow9090 said:
I tried to follow this tutorial to go back to stock because I S-OFF'd moonshine
http://forum.xda-developers.com/showthread.php?t=2293919
My issue is trying to copy the lock bootloader zip file to my phone. Adb sideload is not working, there is no OS since I did the "fastboot oem lock" wiped my phone.
I tried to do a restore in TRWP but after it finished, when starting its stuck on the CM splash screen.
Please help.......................
Click to expand...
Click to collapse
There use to be a command you could enter to lock it. I would message phaded and ask him for the command sense the zip isn't working.
sideshow9090 said:
Hi All,
Sometime ago I was able to install android 4.3 using the moonshine method. After sometime, I decided to go back to stock. I followed a tutorial on how to get back to stock RUU.
-Entered Boot loader, typed in cmd prompt "fastboot oem lock" received the word that lock was successful.
-Proceeded to run the RUU executable file 1.15 but received the "158 error"
Now my phone has been wiped of any OS since I relocked the phone, but it still says "moonshine s-off".
I tried to use TWRP recovery adb sideload the proper hboot file to match the RUU but get this message
Failed
Updating partition details...
E:Unable to mount '/cache'
E:Unable to mount '/cache'
E:TWFunc::Copy_Log -- Can't open destination lo
E:Unable to mount '/cache'
Starting ADB sideload feature...
Installing '/data/media/0/sideload.zip
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
WRONG OPERATION!
E:Error executing updater binary in zip'data/
I am at a complete loss as what to do now. I've been at this for 3 hours now and its driving me crazy. PLEASE HELP!
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B32gqnbh2ZecTUk4TW5QZ1M4cFU/edit?usp=sharing
MD5: 03C6174C4C5331E84520AD7C32EB2837
download that, and then boot into fastboot usb mode, and
fastboot oem rebootRUU
fastboot flash zip SENSE_5_RUU_ROM.zip
it is essentially an RUU but in zip form
WILL WIPE DEVICE (INCLUDING SDCARD)
if this doesnt work, do an @"my xda handle" and ill come back to this
also the only way to flash firmware is through fastboot, made that clear in my instructions, if you got the download from my thread, if you didnt well... now you know lol
@.torrented
This is what I did in command prompt and my result
C:\Android\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.054s]
finished. total time: 0.054s
C:\Android\sdk\platform-tools>fastboot flash zip SENSE_5_RUU_ROM.zip
sending 'zip' (920285 KB)...
OKAY [ 34.998s]
writing 'zip'...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 22 loading zip info fail)
finished. total time: 41.151s
C:\Android\sdk\platform-tools>
The phone ends up being in the black HTC screen. Am I supposed to do something after this?
sideshow9090 said:
@.torrented
This is what I did in command prompt and my result
C:\Android\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.054s]
finished. total time: 0.054s
C:\Android\sdk\platform-tools>fastboot flash zip SENSE_5_RUU_ROM.zip
sending 'zip' (920285 KB)...
OKAY [ 34.998s]
writing 'zip'...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 22 loading zip info fail)
finished. total time: 41.151s
C:\Android\sdk\platform-tools>
The phone ends up being in the black HTC screen. Am I supposed to do something after this?
Click to expand...
Click to collapse
Also this is what my fastboot screen looks like
moonshine S-OFF
MONARUDO PVT SHIP S-OFF
CID-VZW_001
HBOOT-1.33.4444
RADIO-1.01.04.0308
OpenDSP-v6.120.274.0114
eMMC-boot
Jan 15 2013, 19:37:51:-1
FASTBOOT USB
But when I type in adb devices its just says "List of Devices Attached"
sideshow9090 said:
Also this is what my fastboot screen looks like
moonshine S-OFF
MONARUDO PVT SHIP S-OFF
CID-VZW_001
HBOOT-1.33.4444
RADIO-1.01.04.0308
OpenDSP-v6.120.274.0114
eMMC-boot
Jan 15 2013, 19:37:51:-1
FASTBOOT USB
But when I type in adb devices its just says "List of Devices Attached"
Click to expand...
Click to collapse
I am not a dev but it looks like your bootloader is locked. your cid should be all 11111 or all 222222
I goofed up, You will need to go to the bottom of my COLLECTION thread and follow the instructions posted at the bottom under the RUU LINKS section
not the .exe files
[Collection] HTC Droid DNA Firmware [RADIO][HBOOT][RUU]
@.torrent
YOU ARE THE MAN! Donation coming your way....THANKS AGAIN!
sideshow9090 said:
@.torrent
YOU ARE THE MAN! Donation coming your way....THANKS AGAIN!
Click to expand...
Click to collapse
I take it that it worked?
c:\SDK\platform-tools>fastboot getvar all
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.72.0000
(bootloader) version-baseband: 3.1204.171.33
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.18.401.2
(bootloader) serialno: FA2BRW105444
(bootloader) imei: 353567051447689
(bootloader) product: enrc2b_u
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PM3511000
(bootloader) cidnum: HTC__203
(bootloader) battery-status: good
(bootloader) battery-voltage: 4261mV
(bootloader) devpower: 91
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.520s
c:\SDK\platform-tools>fastboot oem rebootRUU
...
(bootloader) Save data from original MSC...
(bootloader) Save data from SIF...
(bootloader) Update partition data to SIF partition
(bootloader) Update partition data from original MSC...
(bootloader) [MSG] OKAY
OKAY [ 0.190s]
finished. total time: 0.190s
c:\SDK\platform-tools>fastboot flash zip firmware.zip
sending 'zip' (734167 KB)...
OKAY [ 92.812s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 125.302s
---------------------------------------------------
my Device is HTC ONE X+
*** RELOCKED ***
*** Security Warning ***
ENRC2B_U PVT SHIP S--ON RL
HBOOT-1.72.0000
CPLD-None
MICROP-None
RADIO-3.1204.171.33
emmc-bootmode : disabled
CPU-bootmode : disabled
HW Secure boot : enabled
MODEM PATH : OFF
You don't need to update your devices firmware, latest HBOOT (1.72) is already installed. The steps you need to do now:
1. unlock your bootloader
2. install a custom recovery
3. reboot to system and copy rom.zip onto your phone
4. reboot into bootloader (fastboot mode) and flash boot.img
5. enter recovery and flash rom.
at least you need to wipe /data partition before/while flashing rom. i recommend wiping /system, /cache and /data (without /data/media).
Also don't forget to make a backup in recovery anywhere between step 2. and 4. !!!
i can't copy rom.zip in my phone
No operating system on phone now
And I can not get to the internal memory of the device
in fastboot msg failed to open usp master mode
i gave HTCDriver_4.2.0.001 put HTC MTP Device Driver not Install
in recovery mode not see mount sdcard
ezat121 said:
No operating system on phone now
And I can not get to the internal memory of the device
in fastboot msg failed to open usp master mode
i gave HTCDriver_4.2.0.001 put HTC MTP Device Driver not Install
in recovery mode not see mount sdcard
Click to expand...
Click to collapse
I don't know about HTC driver version, safest way would be downloading and isntalling HTC Sync to get the right drivers (you can uninstall sync later and keep the drivers.
MTP devices are not able to mount /sdcard in recovery, so you need to use adb sideload command. In case you don't have ADB/Fastboot on your computer, take a look here.
Copy the rom zip file into your ADB/fastbootfolder on your computer (maybe rename it to something shorter), connect your phone to your computer and start sideload mode in recovery. Type "adb devices" in command line to see if your phone is recognized, if it is not, you may need to wait a bit longer or there's an issue with drivers. As soon as your device is recognized as in sideload mode, you can type "adb sideload <name_of_the_rom>.zip" and it should start copying. Installation process should start automatically after copying, or if it does not, you should find a file called "sideload.zip" on your phones internal memory that you can flash manually.
Thank you
After loading the rum on the device
stops at HTC ONE logo
Why did not complete
Sorry for the inconvenience..
But I'm new in this area
Thank You
AW: [Q] any help plzz flash Android Revolution HD
ezat121 said:
After loading the rum on the device
stops at HTC ONE logo
Why did not complete
Sorry for the inconvenience..
But I'm new in this area
Thank You
Click to expand...
Click to collapse
When you say HTC One logo, I assume you flashed the boot.img.
Did you wipe /system, /data (without /data/media) and /cache in before installing rom?
You solved your issue?
Sent from my HTC One X+ using Tapatalk 2
i flashing boot img
reaper90 said:
When you say HTC One logo, I assume you flashed the boot.img.
Did you wipe /system, /data (without /data/media) and /cache in before installing rom?
Click to expand...
Click to collapse
i flashing boot from link of android revolution is that Flash_boot_8.x_0.1
and im wipe from recovery (dalvik cache-system-cache-data-internal storage ) befor install
no start stop in htc one logo dynamic
put no sound in logo
in installing rom zip Option zip file signature verification not
When i chose failed install and see msg no md5 file fond
ezat121 said:
i flashing boot from link of android revolution is that Flash_boot_8.x_0.1
and im wipe from recovery (dalvik cache-system-cache-data-internal storage ) befor install
no start stop in htc one logo dynamic
put no sound in logo
in installing rom zip Option zip file signature verification not
When i chose failed install and see msg no md5 file fond
Click to expand...
Click to collapse
make sure the download is not corrupted. also first boot may take 5-10 minutes, so give it some time.
zeroth said:
You solved your issue?
Sent from my HTC One X+ using Tapatalk 2
Click to expand...
Click to collapse
Not yet, but I'm trying
reaper90 said:
make sure the download is not corrupted. also first boot may take 5-10 minutes, so give it some time.
Click to expand...
Click to collapse
We have prepared the steps are as follows:
1- wipeing /system /cache/data before flashing rom.
2- install a boot.img (Flash boot 8.x 0.1)
3- reboot into bootloader
4- enter recovery and flash rom
flashing Completed and reboot system
Device freezes at logo htc Third (htc one tm ) Supposed to give a voice put no sound
I waited for more than 20 minutes and do not change
What is the problem and where error ؟
I tried more than once and repeated problem
Thank you very much for your response
ezat121 said:
We have prepared the steps are as follows:
1- wipeing /system /cache/data before flashing rom.
2- install a boot.img (Flash boot 8.x 0.1)
3- reboot into bootloader
4- enter recovery and flash rom
flashing Completed and reboot system
Device freezes at logo htc Third (htc one tm ) Supposed to give a voice put no sound
I waited for more than 20 minutes and do not change
What is the problem and where error ؟
I tried more than once and repeated problem
Thank you very much for your response
Click to expand...
Click to collapse
Steps are correct so far, so it should work... Maybe your download of the rom wasn't complete, try redownloading. Also what recovery do you use?
reaper90 said:
Steps are correct so far, so it should work... Maybe your download of the rom wasn't complete, try redownloading. Also what recovery do you use?
Click to expand...
Click to collapse
i try redownloading newly
i restore the previous steps
Do not change the same problem
i use TWRP v 2.6.3.0
i try Back rom stock from this site
http://forum.xda-developers.com/showthread.php?t=2414238
But I did not know how
ezat121 said:
i try redownloading newly
i restore the previous steps
Do not change the same problem
i use TWRP v 2.6.3.0
i try Back rom stock from this site
http://forum.xda-developers.com/showthread.php?t=2414238
But I did not know how
Click to expand...
Click to collapse
The steps i usually do:
0. If possible (OS is still installed), copy rom onto your phones internal storage
1. reboot into bootloader (fastboot) and flash boot.img
2. reboot into recovery
3. wipe everything except internal storage
4. install rom (sideload if necessary)
5. reboot and wait some minutes for first boot to finish.
Since you have international version of the One X+ (enrc2b) and you use TWRP like i do, this should work. The only reason why it could not work, is that you either did not flash the boot.img (you would only see bootloop on first htc screen) or the rom.zip was corrupted, but then again, there would probably be a failure in aroma installer of ARHD.
This started a few days ago. The phone is running a GPE Rom, unlocked and s-on and randomly restarted on me Monday night. The same ROM has been on the phone for months. I have updates set to off and have not installed anything before this happened for days.
The device reboots when trying to change something in internal memory - ie uninstalling an app, or going to running processes in settings>apps
After the reboot any changes made between boots are gone. I can delete widgets, send messages, phone calls etc and all of them are gone. The phone boots in the same state as it was in at the first reboot from Monday.
I went into TWRP and tried to wipe and reinstall ROM - no dice. The device reboots into the last state. any rom install fails with a symlink error. I have tried to sideload adb and it fails. tried to restore and it fails. tried to fastboot oem reboot ruu and the device just restarts to the lockscreen. It is like there is no memory changing state at all. Tried to run ruu from hboot - no dice. reboots back to same lockscreen. I cannot seem to get the ruu exe to download from htc or I would try that.
I have also tried to flash the stock recovery to the phone to wipe and start from scratch - no dice. I am at a loss as to what to do. Also the phone reboots frequently when plugged into the computer - not nearly as much when standalone (although I can force the failure by looking at running apps or trying to uninstall an app)
If the uninstall doesn't reboot the phone, it shows the app is gone. Once I reboot it is back. I have searched and tried everything in the last two days. Help please
d.l33t said:
This started a few days ago. The phone is running a GPE Rom, unlocked and s-on and randomly restarted on me Monday night. The same ROM has been on the phone for months. I have updates set to off and have not installed anything before this happened for days.
The device reboots when trying to change something in internal memory - ie uninstalling an app, or going to running processes in settings>apps
After the reboot any changes made between boots are gone. I can delete widgets, send messages, phone calls etc and all of them are gone. The phone boots in the same state as it was in at the first reboot from Monday.
I went into TWRP and tried to wipe and reinstall ROM - no dice. The device reboots into the last state. any rom install fails with a symlink error. I have tried to sideload adb and it fails. tried to restore and it fails. tried to fastboot oem reboot ruu and the device just restarts to the lockscreen. It is like there is no memory changing state at all. Tried to run ruu from hboot - no dice. reboots back to same lockscreen. I cannot seem to get the ruu exe to download from htc or I would try that.
I have also tried to flash the stock recovery to the phone to wipe and start from scratch - no dice. I am at a loss as to what to do. Also the phone reboots frequently when plugged into the computer - not nearly as much when standalone (although I can force the failure by looking at running apps or trying to uninstall an app)
If the uninstall doesn't reboot the phone, it shows the app is gone. Once I reboot it is back. I have searched and tried everything in the last two days. Help please
Click to expand...
Click to collapse
Run my bootable at&t ruu. Works perfect. if you are s-on, you will need to lock your boot loader. Please click thanks in my ruu thread if I helped you out
http://forum.xda-developers.com/att-htc-one-m8/general/att-1-58-501-1-bootable-ruu-hboot-t2818556
an0ther said:
Run my bootable at&t ruu. Works perfect. if you are s-on, you will need to lock your boot loader. Please click thanks in my ruu thread if I helped you out
http://forum.xda-developers.com/att-htc-one-m8/general/att-1-58-501-1-bootable-ruu-hboot-t2818556
Click to expand...
Click to collapse
the phone will not even let me lock the bootloader. it fails with this message
...
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
FAILED (status read failed (No such file or directory))
finished. total time: 1.154s
also i did that - copied file to root of extsd and hbooted - it goes through and flashes zip then returns me to hboot menu
d.l33t said:
the phone will not even let me lock the bootloader. it fails with this message
...
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
FAILED (status read failed (No such file or directory))
finished. total time: 1.154s
Click to expand...
Click to collapse
You can try it with the bootlader unlocked.
an0ther said:
You can try it with the bootlader unlocked.
Click to expand...
Click to collapse
it just flashes zip then puts me back to the hboot screen - rebooting the phone takes me back to the GPE Rom
d.l33t said:
it just flashes zip then puts me back to the hboot screen - rebooting the phone takes me back to the GPE Rom
Click to expand...
Click to collapse
what command are you using to relock boot loader? Are you hitting "vol up to update?"
an0ther said:
what command are you using to relock boot loader? Are you hitting "vol up to update?"
Click to expand...
Click to collapse
i am using hasooon2000 for lock bootloader. it never asks me to hit vol up
Toolkit. Urrr. Try
Fastboot oem lock
My ruu will ask you to hit vol up to update.
an0ther said:
Toolkit. Urrr. Try
Fastboot oem lock
My ruu will ask you to hit vol up to update.
Click to expand...
Click to collapse
the ruu flashes zip - parsing then kicks me back to the screen where you can select fastboot/hboot - i have tried with the adb commands and get the same result.
What are the steps you are taking in my bootable ruu?
downloaded the file and copied to extsd root - rebooted into bootloader - selected hboot - finds file. signature checks then starts to flash zip. gets two status bars in and goes to a screen that says parsing in green lettering only - then kicks me back to the hboot menu
Try
Fastboot erase cache
Fastboot reboot-bootloader
Fastboot oem lock
If that fails try
Fastboot oem relock
an0ther said:
Try
Fastboot erase cache
Fastboot reboot-bootloader
Fastboot oem lock
If that fails try
Fastboot oem relock
Click to expand...
Click to collapse
ok so i got the cache erased but anytime i try to reboot fastboot (whether it be ruu or bootloader etc) the device just reboots. its almost like the boot identifier doesnt actually write to the phone and it goes back to booting like normal to the loading screen, hence the seems like read only. tried to relock bootloader and it says it passed. however upon rebooting to fastboot i get the same unlocked message at the top
Thank you for the help btw - i think this thing is uber screwed.
d.l33t said:
ok so i got the cache erased but anytime i try to reboot fastboot (whether it be ruu or bootloader etc) the device just reboots. its almost like the boot identifier doesnt actually write to the phone and it goes back to booting like normal to the loading screen, hence the seems like read only. tried to relock bootloader and it says it passed. however upon rebooting to fastboot i get the same unlocked message at the top
Thank you for the help btw - i think this thing is uber screwed.
Click to expand...
Click to collapse
can you take a pic of your boot loader for me?
an0ther said:
can you take a pic of your boot loader for me?
Click to expand...
Click to collapse
yah give me just a minute
an0ther said:
can you take a pic of your boot loader for me?
Click to expand...
Click to collapse
there you go - also i went ahead and ran getvar to see if you see anything
Take off your getvar post. Your imei is in there.
---------- Post added at 10:36 PM ---------- Previous post was at 10:36 PM ----------
I just want the picture
I know this may not be your issue but do you have the stock HTC cable and did you try removing Sim and SD card before running adb commands? Just trying to see if bare phone will work with least amount of variables. Try another computer?
Sent from my LG-E980 using XDA Free mobile app
an0ther said:
Take off your getvar post. Your imei is in there.
---------- Post added at 10:36 PM ---------- Previous post was at 10:36 PM ----------
I just want the picture
Click to expand...
Click to collapse
sorry - forgot about that. running on little sleep. the picture is attached above
yes i am using the stock htc cable. i have tried without sim and sd installed same thing - also i have tried 3 different computers
can i format the data on the phone using the fastboot erase command?
I've got a friend's HTC One M8 that's stuck in HBOOT. I can't flash a new recovery, I've tried both TWRP and CWM. Either time I get an error message "FAILED (remote: image update error)"
I'm at the end of my thread here with things I can try to fix it. I've searched almost all topics to no avail.
Here's the getvar dump:
C:\Users\Adrian>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 0a41237a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
--
Device says *** UNLOCKED *** on screen, doesn't say TAMPERED (not sure what this is).
Anything fastboot commands usually result in a failed message but the device is recognized if I type "fastboot devices".
Here's a sample when trying to use Squabbi's toolkit:
target reported max download size of 1830727680 bytes
sending 'recovery' (24576 KB)...
OKAY [ 1.607s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.678s
I've tried using an ATT RUU, various recovery files, etc. The phone boots straight into HBOOT. Any other commands apart from fastboot on the device result in a quick flash of another screen and returns to the fastboot USB screen.
What can I do to get this device back up and running? For some reason I just can't get the recovery file to flash so I can move forward already. Am I missing something? I just got the device from a friend. He mentioned he was watching YT when all of a sudden the device went into this boot loop.
Thanks in advance!
adriankeith said:
I've got a friend's HTC One M8 that's stuck in HBOOT. I can't flash a new recovery, I've tried both TWRP and CWM. Either time I get an error message "FAILED (remote: image update error)"
Thanks in advance!
Click to expand...
Click to collapse
Hello
I'm no expert but it sounds like a radio issue
Have you tried a new RUU
Also what is your (bootloader) version-main:
Thanks
jcbjoe said:
Hello
I'm no expert but it sounds like a radio issue
Have you tried a new RUU
Also what is your (bootloader) version-main:
Thanks
Click to expand...
Click to collapse
Admittedly, I've got an iOS device myself so I'm going to have to defer to your expertise. I believe I've tried a new RUU (an ATT .exe file? It was a full blown installer, told me what version i was on, what version it would be updating to.. does this sound right?).
How can I get you the bootloader version?
adriankeith said:
Admittedly, I've got an iOS device myself so I'm going to have to defer to your expertise. I believe I've tried a new RUU (an ATT .exe file? It was a full blown installer, told me what version i was on, what version it would be updating to.. does this sound right?).
How can I get you the bootloader version?
Click to expand...
Click to collapse
C:\Users\Adrian>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: < --
jcbjoe said:
C:\Users\Adrian>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: < --
Click to expand...
Click to collapse
That was a straight copy paste from my command line. So.. I guess if there's nothing there.. ??
RUU
adriankeith said:
That was a straight copy paste from my command line. So.. I guess if there's nothing there.. ??
Click to expand...
Click to collapse
You can try this
1.58.502.1 full RUU
jcbjoe said:
You can try this
1.58.502.1 full RUU
Click to expand...
Click to collapse
Unfortunately, it seems with any of these RUU installers I get a USB connection error. I have to think it has something to do with me being unable to enable the USB Debugging mode of the phone.
Any other ideas?
adriankeith said:
Unfortunately, it seems with any of these RUU installers I get a USB connection error. I have to think it has something to do with me being unable to enable the USB Debugging mode of the phone.
Any other ideas?
Click to expand...
Click to collapse
Can you get into fastboot mode ?
IF you can get into fastboot mode we are fine .. we don't need adb
Think of fastboot as the bios and adb as the software
IF your usb is jacked you need to try another computer
EDIT: If fastboot works go to This Thread
The first download link is the firmware that you need
1. Download the firmware
2. Put your phone in fastboot mode
3. fastboot erase cache
4. fastboot oem rebootRUU
5. fastboot flash zip thefirmwareyoudownload.zip < -- if it fails you might have to do this 2x
6. fastboot reboot-bootloader
7. Tell us what you see after words
jcbjoe said:
Can you get into fastboot mode ?
IF you can get into fastboot mode we are fine .. we don't need adb
Think of fastboot as the bios and adb as the software
IF your usb is jacked you need to try another computer
Click to expand...
Click to collapse
I'm able to get into fastboot USB mode but any of the critical commands I've tried running (fastboot flash recovery image.img) all throw errors.
Like this --
sending 'recovery' (12846 KB)...
OKAY [ 1.272s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.341s
---
edit:
Here's the error I get when trying to erase the cache:
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 0.006s
Click to expand...
Click to collapse
adriankeith said:
I'm able to get into fastboot USB mode but any of the critical commands I've tried running (fastboot flash recovery image.img) all throw errors.
Like this --
sending 'recovery' (12846 KB)...
OKAY [ 1.272s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.341s
---
edit:
Here's the error I get when trying to erase the cache:
Click to expand...
Click to collapse
Did you flash the firmware file from the link i provided ?
Firmware < -- Flash this first .. don't flash anything individually .. you need to update the firmware don't unpack it
jcbjoe said:
Did you flash the firmware file from the link i provided ?
Firmware < -- Flash this first .. don't flash anything individually .. you need to update the firmware don't unpack it
Click to expand...
Click to collapse
How do I flash this file?
adriankeith said:
How do I flash this file?
Click to expand...
Click to collapse
Download it
.. once you download it you will see it says firmware.zip
Then you put it on your desktop or your Downloads folder
Then
1. fastboot erase cache
2. fastboot oem rebootRUU
3. fastboot flash zip firmware.zip < -- if it fails you might have to do this 2x (remember you flash it to where its at .. so if its in windows on your desktop it would be fastboot flash zip ~/Desktop/firmware.zip or in Downloads it would be fastboot flash zip ~/Downloads/firmware.zip
4. fastboot reboot-bootloader
5. Tell us what you see after words
jcbjoe said:
Download it
.. once you download it you will see it says firmware.zip
Then you put it on your desktop or your Downloads folder
Then
1. fastboot erase cache
2. fastboot oem rebootRUU
3. fastboot flash zip firmware.zip < -- if it fails you might have to do this 2x (remember you flash it to where its at .. so if its in windows on your desktop it would be fastboot flash zip ~/Desktop/firmware.zip or in Downloads it would be fastboot flash zip ~/Downloads/firmware.zip
4. fastboot reboot-bootloader
5. Tell us what you see after words
Click to expand...
Click to collapse
Here's the problem when I try to attempt the first command
C:\Users\Adrian>fastboot erase cache
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 0.006s
adriankeith said:
Here's the problem when I try to attempt the first command
C:\Users\Adrian>fastboot erase cache
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 0.006s
Click to expand...
Click to collapse
Can you rename the firmware.zip to 0p6bimg.zip
Once you do that put the file onto the root of your sdcard (meaning not in a folder)
Credits for the Below Method (an0ther Post# 1)
2. Simply move the "0p6bimg.zip" to the ROOT of your EXT micro sd card.
3. Boot to your boot loader. There are many ways to get to your boot loader. A lot of custom roms have it built into the restart menu. If you have usb debugging enabled its just "adb reboot bootloader" If you can't get there with one of these methods, simply make sure phone is on, hold vol up and power for 11 seconds until screen shuts off, let go and hold vol down and power until boot loader comes up. "about 4 seconds"
4. Click HBOOT in your boot loader. Your phone will automatically scan the file and ask if you want to update. Hit vol up for yes or vol down for no.
5. Phone will begin RUU restore. You can watch what it does on the screen as it will go through a list and bypasses are normal. It will reboot boot loader and you can watch progress bars in the top right corner. It goes through a TON of them so do NOT turn off phone for any reason and let it finish. The process takes about 15 minutes give or take. Once it is done, it will say complete, press power to reboot. Again do not power off phone or even touch it for that matter during this process.
jcbjoe said:
Can you rename the firmware.zip to 0p6bimg.zip
Once you do that put the file onto the root of your sdcard (meaning not in a folder)
Credits for the Below Method (an0ther Post# 1)
2. Simply move the "0p6bimg.zip" to the ROOT of your EXT micro sd card.
3. Boot to your boot loader. There are many ways to get to your boot loader. A lot of custom roms have it built into the restart menu. If you have usb debugging enabled its just "adb reboot bootloader" If you can't get there with one of these methods, simply make sure phone is on, hold vol up and power for 11 seconds until screen shuts off, let go and hold vol down and power until boot loader comes up. "about 4 seconds"
4. Click HBOOT in your boot loader. Your phone will automatically scan the file and ask if you want to update. Hit vol up for yes or vol down for no.
5. Phone will begin RUU restore. You can watch what it does on the screen as it will go through a list and bypasses are normal. It will reboot boot loader and you can watch progress bars in the top right corner. It goes through a TON of them so do NOT turn off phone for any reason and let it finish. The process takes about 15 minutes give or take. Once it is done, it will say complete, press power to reboot. Again do not power off phone or even touch it for that matter during this process.
Click to expand...
Click to collapse
Got a wrong zipped image while it was loading the zip file.
adriankeith said:
Got a wrong zipped image while it was loading the zip file.
Click to expand...
Click to collapse
Try any of the links in the Thread
You have to rename it to 0p6bimg.zip
jcbjoe said:
Try any of the links in the Thread
You have to rename it to 0p6bimg.zip
Click to expand...
Click to collapse
Yep, I renamed it to the 0P6BIMG.zip and when it began to load the file it agave me that error. I'll try that thread now.
--
Still getting the "Wrong Zipped Image!" error. I did this previously with a different firmware and it got through some of the process but bombed out after something and put me back in HBOOT. Couldn't launch recovery, couldn't launch anything. Fastboot USB shows up fine.
adriankeith said:
Yep, I renamed it to the 0P6BIMG.zip and when it began to load the file it agave me that error. I'll try that thread now.
--
Still getting the "Wrong Zipped Image!" error. I did this previously with a different firmware and it got through some of the process but bombed out after something and put me back in HBOOT. Couldn't launch recovery, couldn't launch anything. Fastboot USB shows up fine.
Click to expand...
Click to collapse
You Possibly have a bricked device
You can try chatting on freenode via irc
irc.freenode.net #sunshine-support or #htc-dev or #venomroms .. all these channels have htc devices m7 or m8
Thanks
jcbjoe said:
You Possibly have a bricked device
You can try chatting on freenode via irc
irc.freenode.net #sunshine-support or #htc-dev or #venomroms .. all these channels have htc devices m7 or m8
Thanks
Click to expand...
Click to collapse
I was coming to that conclusion quickly.
Thanks for your help though. I appreciate it.
adriankeith said:
Unfortunately, it seems with any of these RUU installers I get a USB connection error. I have to think it has something to do with me being unable to enable the USB Debugging mode of the phone.
Any other ideas?
Click to expand...
Click to collapse
Since you are s-in and bootloader unlocked, you need to relock the bootloader to run an RUU. This shouldn't give you a USB connection error, but its at least worth a try to relock.
Also, try to connect the phone to PC, go into Window Device Manager, and see if you can format the internal memory to FAT32. Some folks have had issues with internal memory corrupted, and cannot install recovery; and this fix worked for them.
---------- Post added at 10:17 AM ---------- Previous post was at 10:13 AM ----------
jcbjoe said:
You Possibly have a bricked device
Click to expand...
Click to collapse
I doubt it. So far, I've only seen on these forums one M8 where the screen still comes on, and extensive help from several folks couldn't get it back up and running. Being able to get into hboot means we can recover, 99.99% of the time.
Still a lot of things left to try.
Hey guys, just ended my contract with Verizon and started using Cricket wireless. Up until this point everything went smoothly, just had to swap out the SIM and not much else. Because I no longer needed/wanted all the bloat and VW apps, I decided to s-off and root; I used Sunshine as I had the stock 4.09.605.5 and no other form of rooting or... soffing?... would work. As of this morning, All of that was accomplished and I was left with a bootloader noted below:
Code:
[COLOR="Magenta"]*** UNLOCKED ***[/COLOR]
[COLOR="Olive"]MONARUDO PVT SHIP S-OFF RH
CID-VZW_001
HBOOT-1.57.0000
RADIO-1.02.01.0818
OpenDSP-v12.120.274.0909
OS-
eMMC-boot 2048MB
Aug 27 2014,13:22:15.0[/COLOR]
So at this point, I still had stock rom, but applied s-off, had root, and importantly - I think - I was using the built in android encryption. So at this point I flashed TWRP successfully using the WinDroid Universal toolkit and started the process of installing a new rom, specifically the ★ ☆ [ROM][5.0.1] Google Play Edition | Lollipop | v2.00 [02-06-15] rom, but ran into a few problems.
first, I could not backup my current rom at all. I even flashed CWM and tried it there but only got 'Waiting to mount SD Card' timeouts so I switched back to TWRP. On my last try, I received nothing but errors, a selection of them below:
Code:
[COLOR="Red"]E:Could not mount /data and unable to find crypto footer.
E:Unable to mount '/data'
E:Unable to recreate /data/media folder.[/COLOR]
Updating partition details...
[COLOR="red"]E:Unable to mount '/data'
E:Unable to mount storage.[/COLOR]
...and so on. I tried searching for fixes to this issue but did not get anywhere, and since I knew i wasn't going back to stock ever again, I pressed on with the install. I used a USB-OTG connection, copied the zip, and installed. There were a couple of similar error messages but the install was reported as successful. Upon rebooting the phone, it loads the Google Play bootloader animation, but the next screen brings up the 'Encryption unsuccessful' notice with the only option to do a factory reset. When I select that, it reboots into recovery, then starts/fails a Factory reset:
Code:
Running OpenRecovertScript
(bunch of errors...)
Then recovery closes, the boot animation starts, and then I'm back at the Encryption Unsuccessful messagebox. At this point I do not know how to proceed with fixing this; I have no problem formatting my phone as all my data is backed up elsewhere.
I've linked a couple of screenshots to show the errors I am getting located here. Any and all help would be welcome here, thanks and please!!
1.) Never use toolkit to do anything. Use fastboot for flashing recovery. 2.) You need stock recovery installed to use fastboot's factory reset option.
I'm going to need some handholding here, bear with me:
1) I can get to the Fastboot page on my phone, and I can plug it in to get FASTBOOT USB, but adb does not see the device. Nevermind, I used adb and not fastboot. Still not sure on which steps I need to take there.
2) How do I go about reinstalling the stock recovery?
Edit: I performed the following fastboot erase functions and got these responses:
Code:
C:\XXXXXXXXXXX>fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
FAILED (remote: not allowed)
finished. total time: 0.010s
C:\XXXXXXXXXXX>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.070s]
finished. total time: 0.070s
Since you're unlocked, use fastboot to flash recovery. Once that's done then flash ROMs in recovery. Doas beaups says and don't use toolkits to flash things.
If you want to start clean from square one, use an ruu to flash the stock ROM, recovery, etc. Then do as I said above: flash recovery in fastboot then flash a ROM in recovery.
So it turns out it had nothing to do with TWRP or the rom. I used the full format option and it worked, then installed the ROM again and everything works.
Mods, feel free to nuke this thread as it's not really helpful in the end.
So the lesson is to make sure your phone is not encrypted before flashing/modifying things,except if you do a full reformat.