HTC One M8 ATT GSM Converted from Stock Sense > ViperRom > CM11 > GPE Conversion (Firmware Included)
I have two of these devices mine worked fine when I moved to the Skydragon 5.0 Rom, I installed the firmware, followed the instructions in the thread, no issues. On my other phone this has been an issue.
On the phone in questions it is unlocked, rooted, S-Off. Here are the issues I am experiencing and what I have tried.
Issue: Cannot install custom recovery (philz,cwm or TWRP)
- Tried via fastboot - Reports successful, no change.
- Tried via hboot - Reports Update Failed, Reboot, no change.
- Tried via TWRP application - TWRP crashes, no change
Issue: Any changes made to the phone are reverted on reboot including app updates, installations, progress in media, anything.
Issue: In fastboot usb mode, if I enter the command "fastboot oem rebootRUU" the phone will simply reboot, so I have to try to flash firmware via hboot.
Issue: The phone will randomly reboot.
I have tried:
1. Flashing custom recoveries. (multiple ways, multiple version, multiple types)
2. Flashing RUU (multiple via hboot, all fail)
3. Flashing FUU (via windows) (Stock, Full Wipe, It reboots the phones and then claims no USB connection)
4. e2fsck -fn the /dev/block/mmcblk0p47 - Reports Errors cannot be fixed. I can't do anything with the drive mounted, and cannot access adb in recovery so, not sure...
5. wp_mod.ko ( can insmod while the phone is booted, any changes to the install-recovery.sh are lost on reboot so it does not stick)
6. Tried flashing the partition fix 1.54 splash for the GPE converted devices (again via hboot, failed)
7. Different cables, different USB ports, and every other guides I could find on XDA
8. Tried factory reset from recovery and phone OS.
I have available to me on the phone
Stock GPE Recovery - No ADB shell
ADB access while phone is booted, including root shell
Fastboot access in bootloader, minus ability to access rebootRUU
Here is some data output below, and if I can provide anything else I am more than happy to do so. Appreciate any help you all can provide me on this.
--GETVAR--
$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.14.21331931.LA02_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.16.1700.16
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT43KWM01872
(bootloader) imei: <redacted>
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: a1aef34e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.016s
--BANNER--
*** Unlocked ***
M8_UL_CA PVT SHIP S-OFF
CID-GOOGL001
HBOOT-3.18.0.0000
RADIO-1.14.21331931.LA02_2G
OpenDSP-v32.2.2-00542-M8974.0213
OS-1.16.1700.16
eMMC-boot 2048
Mar 21 2014, 22:29:15.0
--ROOT DF--
[email protected]_m8:/ # df
Filesystem Size Used Free Blksize
/dev 913.8M 128.0K 913.6M 4096
/sys/fs/cgroup 913.8M 12.0K 913.7M 4096
/mnt/asec 913.8M 0.0K 913.8M 4096
/mnt/obb 913.8M 0.0K 913.8M 4096
/system 1006.7M 786.2M 220.5M 4096
/data 26.3G 3.6G 22.7G 4096
/cache 678.4M 10.8M 667.6M 4096
/devlog 29.5M 20.4M 9.1M 4096
/fataldevlog 19.6M 13.5M 6.2M 4096
/firmware/radio 199.8M 44.3M 155.5M 4096
/firmware/adsp 199.8M 8.9M 190.9M 4096
/firmware/wcnss 199.8M 3.8M 196.0M 4096
/custdata 49.2M 4.0M 45.2M 4096
/mnt/shell/emulated 26.3G 3.6G 22.7G 4096
/storage/emulated 913.8M 0.0K 913.8M 4096
/mnt/media_rw/ext_sd 29.8G 4.1G 25.8G 4096
--LSMOD--
[email protected]_m8:/ # lsmod
wlan 3543984 0 - Live 0x00000000 (O)
adsprpc 21680 3 - Live 0x00000000
ecryptfs 88689 0 - Live 0x00000000
dm_crypt 22668 0 - Live 0x00000000
texfat 178608 0 - Live 0x00000000 (PO)
--FSCK OUTPUT--
[email protected]_m8:/sdcard2/untitled folder # ./fsck.ext4 -f -n /dev/block/platform/m>
e2fsck 1.42.9 (28-Dec-2013)
Warning! /dev/block/platform/msm_sdcc.1/by-name/userdata is mounted.
Warning: skipping journal recovery because doing a read-only filesystem check.
Pass 1: Checking inodes, blocks, and sizes
Deleted inode 83039 has zero dtime. Fix? no
Inodes that were part of a corrupted orphan linked list found. Fix? no
Inode 164419 was part of the orphaned inode list. IGNORED.
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: -(328880--328887) -524802 +524803 -(560736--560754) -(4719168--4719203) -(4796672--4796759)
Fix? no
Free blocks count wrong for group #17 (13436, counted=13417).
Fix? no
Free blocks count wrong for group #146 (5013, counted=4925).
Fix? no
Free blocks count wrong (5946355, counted=5946561).
Fix? no
Inode bitmap differences: -83039 -164419
Fix? no
Free inodes count wrong (1733054, counted=1733358).
Fix? no
/dev/block/platform/msm_sdcc.1/by-name/userdata: ********** WARNING: Filesystem still has errors **********
/dev/block/platform/msm_sdcc.1/by-name/userdata: 20034/1753088 files (4.8% non-contiguous), 1065997/7012352 blocks
4|[email protected]_m8:/sdcard2/untitled folder #
***UPDATE*** I was able to get the phone into RUU mode via this command:
adb -s HT43KWM01872 shell /system/bin/reboot oem-78
So here is the output of my attempt to flash a custom recovery as well as flash the RUU. The RUU flash completes with the failure, but before I am able to re-flash it. The device reboots and I am back into the OS.
rr at RR-MBP in ~/Desktop
$ fastboot flash recovery openrecovery-twrp-2.6.3.3-m8_0.6.img
target reported max download size of 1830715392 bytes
sending 'recovery' (11164 KB)...
OKAY [ 1.191s]
writing 'recovery'...
OKAY [ 0.674s]
finished. total time: 1.866s
rr at RR-MBP in ~/Desktop
$ fastboot flash zip RUU-HTC_One_M8_GPE_4.4.4-2.12.1700.1.zip
target reported max download size of 1830715392 bytes
sending 'zip' (567002 KB)...
OKAY [ 19.168s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) total_image_number=7
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
(bootloader) current_image_number=0
(bootloader) current_image_number=1
(bootloader) current_image_number=2
(bootloader) current_image_number=3
(bootloader) current_image_number=4
(bootloader) current_image_number=5
(bootloader) current_image_number=6
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 20.477s
I am fully willing to pay for anyone's time in helping solve this, paypal or bitcoin. I am out of ideas.
Ok, have you tried renaming the RUU to 0PBIMG and hboot flashing ? Let me know what happens...the 2.12.1700.1 RUU has stock recovery, so remove it b4 you flash the renamed RUU.
jxcorex28 said:
Ok, have you tried renaming the RUU to 0PBIMG and hboot flashing ? Let me know what happens...the 2.12.1700.1 RUU has stock recovery, so remove it b4 you flash the renamed RUU.
Click to expand...
Click to collapse
Thanks for your response, I appreciate it. I have indeed tried the RUU that way, it will either say "update failed" or it will attempt the update and the phone reboots and I am back to this weird saved state. I had some advice from graffixnyc to try booting from a recovery (non-flased) which I have all cause the phone to reboot and lose any changes. I have also tried the RUU.EXE for the Dev Edition, GPE Edition, Stock and all of them start to run and then reboot and lose connection.
Something on the phone has somehow saved a state that it returns to on every reboot. So you can even rm -rf the entire /system from an adb shell su'd as root. It will delete everything, and when you reboot the phone, its all right back to the same state. You can add, modify, delete, anything on the device you want, but as soon as it reboots it will lose it.
The reboot is what is killing me on every front. The only thing that I found that was odd is yesterday I tried running the RUU.exe for the dev edition and running two at the same time. What happened is the first one detected my firmware as 2.12 which is incorrect, the second one that ran (while the first one was still running) reported the firmware as 1.16 (correct). However while that "seemed" to get farther, the phone rebooted, and...you guessed it... all changes were lost.
So what on earth would allow the device to have this "saved "state" that it returns to? If I delete files via rm -rf then I would expect I am either not actually interacting with the filesystem or it is overwriting it with a saved img from somewhere? Confused as hell by this.
*edit* I even tried DD every partition I could from adb shell and nothing took from a known good stock backup. Nothing took.
Here is the output from trying to run the fastboot commands that graffixnyc had suggested to me.
System> About Phone
--Model Number: HTC ONE_M8
--Android Version: 4.4.4
--Baseband Version: 1.14.21331931.LA02_2G_20.30A.4145.01L
--Kernel Version: 3.4.0-gb1b6fb1 | [email protected] #1v| Mon Jul 16 18:49:22 CST 2014
--Build Number: KTU84P.H1 release keys
Phone:
adb
$ adb devices
List of devices attached
HT43KWM01872 device
$ adb reboot bootloader
*** Unlocked ***
M8_UL_CA PVT SHIP S-OFF
CID-GOOGL001
HBOOT-3.18.0.0000
RADIO-1.14.21331931.LA02_2G
OpenDSP-v32.2.2-00542-M8974.0213
OS-1.16.1700.16
eMMC-boot 2048
Mar 21 2014, 22:29:15.0
$ fastboot devices
HT43KWM01872 fastboot
$ fastboot boot 1.16.1700.16.recoverygpe.img
creating boot image...
creating boot image - 25167872 bytes
downloading 'boot.img'...
OKAY [ 1.607s]
booting...
OKAY [ 0.002s]
finished. total time: 1.608s
Phone Flashed Black Screen then back to bootloader:fastboot usb
$ fastboot boot stock\ recovery\ 1.12.1540.17\ recovery.img
creating boot image...
creating boot image - 25167872 bytes
downloading 'boot.img'...
OKAY [ 1.599s]
booting...
OKAY [ 0.002s]
finished. total time: 1.600s
Phone Flashed Black Screen then back to bootloader:fastboot usb
$ fastboot boot stock\ recovery\ 1.22.980.1\ recovery.img
creating boot image...
creating boot image - 25167872 bytes
downloading 'boot.img'...
OKAY [ 1.592s]
booting...
OKAY [ 0.002s]
finished. total time: 1.594s
Phone Flashed Black Screen then back to bootloader:fastboot usb
$ fastboot boot 3.11.1700.5.recovery.img
creating boot image...
creating boot image - 13539328 bytes
downloading 'boot.img'...
OKAY [ 1.249s]
booting...
OKAY [ 0.002s]
finished. total time: 1.250s
$ fastboot oem writecid 11111111
...
(bootloader) Start Verify: 0
(bootloader) Input CID is super CID
(bootloader) Start Verify: 0
OKAY [ 0.025s]
finished. total time: 0.025s
$ fastboot oem readcid
...
(bootloader) cid: 11111111
OKAY [ 0.010s]
finished. total time: 0.010s
Tried fastboot booting from the 4 recovery again with supercid, but after each phone screen flash to black the cid was reset to GOOGL001
Tried booting to RUU mode and repeating the commands above, with same result.
Just for kicks I tried adb shell , su, remounted / as rw. Then ran "rm -rf /" (don't do that ever) which ran and deleted stuff until the phone rebooted. Well, guess what. Phone rebooted and it's like nothing happened. Right back to the saved state. Time to jtag this thing?
Related
Hi,
Unlocked my wife's Legend using the HTC-Dev method. Installed CM7 and she was happy... Now she is missing the HTC weather animations and wants to go back to the stock Froyo.
I have the correct RUU for her phone, carrier, and region, extracted from:
RUU_Legend_BellMobility_WWE_2.02.666.3_Radio_47.37.35.09_7.08.35.05_release_130094_signed.exe
First I tried to flash by renaming the rom.zip to LEGEIMG.zip. The bootloader saw it and chewed on it for a while, but the RUU ended up not being applied and the phone booted back into CM. Confusing.
Next attempt: fastboot, with bootloader unlocked.
Code:
[[email protected] ruu]# [B]fastboot erase cache[/B]
erasing 'cache'...
OKAY [ 0.258s]
finished. total time: 0.258s
[[email protected] ruu]# [B]fastboot oem rebootRUU[/B]
...
OKAY [ 0.017s]
finished. total time: 0.017s
[[email protected] ruu]# [B]fastboot flash zip rom.zip[/B]
sending 'zip' (124420 KB)...
OKAY [ 12.795s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
[B]FAILED (remote: 99 unknown fail)[/B]
finished. total time: 18.643s
Did some more reading, found that RUUs only apply when the bootloader is locked. So I relocked the bootloader with fastboot oem lock and tried again:
Code:
[[email protected] ruu]# [B]fastboot erase cache[/B]
< waiting for device >
erasing 'cache'...
OKAY [ 0.258s]
finished. total time: 0.258s
[[email protected] ruu]# [B]fastboot oem rebootRUU[/B]
...
OKAY [ 0.017s]
finished. total time: 0.017s
[[email protected] ruu]# [B]fastboot flash zip rom.zip[/B]
sending 'zip' (124420 KB)...
OKAY [ 12.874s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
[B]FAILED (remote: 43 main version check fail)[/B]
finished. total time: 44.062s
And trying the LEGEIMG.zip method after relocking:
Code:
Main version is older!
Update Fail!
Do you want to reboot device?
Here are my bootvars:
Code:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.02.0000
(bootloader) version-baseband: 7.13.35.13
(bootloader) version-cpld: None
(bootloader) version-microp: 0816
(bootloader) version-main: 3.30.0.0
(bootloader) serialno: HT05NRA07XX
(bootloader) imei: XXXXX
(bootloader) product: legend
(bootloader) platform: HBOOT-7227
(bootloader) modelid: PB7611000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3905mV
(bootloader) partition-layout: HTC
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-39ec9098
(bootloader) hbootpreupdate: 11
Apparently this means that I'm trying to flash an RUU that is older than what is on the device. The problem is, the RUU update that I last applied was the HTCDev one to allow unlocking. So the most recent "full" RUU is older than the HTCDev RUU and I can't seem to downgrade.
Am I missing something? I must be missing something. Please help, or the wife will have one up on me. Can't allow that
Hello,
try this ROM from BlaY0, its an improved stock ROM and you keep root.
When I remember right, there was no version check during installation, you can install it with Clockwork mode Recovery.
alligator_asl said:
Hello,
try this ROM from BlaY0, its an improved stock ROM and you keep root.
Click to expand...
Click to collapse
Thanks, that's an acceptable workaround for now. I ended up going this route. Since CWM 5.X doesn't like "amend" scripting, it took some doing though. :highfive:
If anyone knows of a way to downgrade to a stock RUU after applying the HBOOT 1.02 RUU to the Legend, that would be a help.
I'd suggest if you really need to go back stock froyo it can't be done with hboot 1.02, I have tried various different methods with no success.
I can't remember who, but some where on legend forums (I think in the dev section) there is a method to downgrade back to hboot 1.01, if it works you can do it and flash ruu. I can't confirm if it works or not.
Sent from my Legend using xda app-developers app
ranger4740 said:
I can't remember who, but some where on legend forums (I think in the dev section) there is a method to downgrade back to hboot 1.01, if it works you can do it and flash ruu. I can't confirm if it works or not.
Click to expand...
Click to collapse
Yeah, that sounds right.
So for anyone reading this thread in the future, if you've unlocked your bootloader using HTC-dev you will be unable to return to stock Froyo using an official RUU without first downgrading to HBOOT 1.01 or older.
The HBOOT downgrade process is pretty involved. You need a goldcard and the hack4legend kit. See this thread for details.
And for good measure, here's a thread with someone else working out the same problem we just worked out here... :silly:
At the end of the day, if you ran a nandroid backup of your stock ROM before blowing it away, you won't need all this jazz.
ariaxu said:
Since CWM 5.X doesn't like "amend" scripting, it took some doing though.
Click to expand...
Click to collapse
You can take an older Versin of CWM ( recovery-clockwork-2.5.0.7-legend.zip ), ther are no problems with scripting, a google search brings several results.
If necessary, you lan load the old version of CWM from the new version and then you can flash this ROM !
I believe I did all the steps correctly but it did not seem to work. May have not done the 'immediate' step quickly enough (fastboot oem boot)? Anyway, i tried it a few more times again without success. I seemed to not be able to write the 3 files equired at the end specifically #2 + 3. Now it says it can't find my fastboot flash zip (I renamed mine soff.zip) but it is there...Thought I would give it and me space for a while before I try again. Anyone with any suggestions?
The soffbin3 is the file inside the zip... You need to pull that file out and flash that the p830000000-dna.zip is the one you leave alone
Sent from my Nexus 7 using XDA Premium HD app
.torrented said:
The soffbin3 is the file inside the zip... You need to pull that file out and flash that the p830000000-dna.zip is the one you leave alone
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Pretty sure I extracted that but will double check, thanks..
rootntootn said:
Pretty sure I extracted that but will double check, thanks..
Click to expand...
Click to collapse
Posting command file here as it did not work again...... I put the zip file and extracted in my working directory not the phone,is that correct? just occured to me that it may need to be on phone sd card anyway below is what got spit out, any help appreciated.
C:\adt-bundle-windows-x86\sdk\platform-tools>adb reboot bootloader
adb server is out of date. killing...
* daemon started successfully *
C:\adt-bundle-windows-x86\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.047s]
finished. total time: 0.049s
C:\adt-bundle-windows-x86\sdk\platform-tools>fastboot flash zip soff.zip
sending 'zip' (36905 KB)...
OKAY [ 3.370s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 3.595s
C:\adt-bundle-windows-x86\sdk\platform-tools>fastboot oem boot
...
(bootloader) monarudo_vibrate_device_time(): vibrate 200(ms)...
(bootloader) Boot/Recovery signature checking...
(bootloader) TZ_HTC_SVC_HASH ret = 0
(bootloader) setup_tag addr=0x80600100 cmdline add=0x003147C8
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:skuid 0x32401
(bootloader) TAG:hero panel = 0x94005B
(bootloader) TAG:engineerid = 0x0
(bootloader) TAG: PS ID = 0x0
(bootloader) TAG: Gyro ID = 0x1
(bootloader) Device CID is super CID
(bootloader) CID is super CID
(bootloader) Backup CID is empty
(bootloader) setting->cid::22222222
(bootloader) serial number: FA2BAS504674
(bootloader) commandline from head: console=ttyHSL0,115200,n8 androidboot
(bootloader) .hardware=dlx user_debug=31
(bootloader) command line length =796
(bootloader) active commandline: poweron_status=1 reset_status=0 board_mo
(bootloader) narudo.disable_uart3=0 diag.enabled=0 board_monarudo.debug_u
(bootloader) art=0 userdata_sel=0 androidboot.emmc=true androidboot.pages
(bootloader) ize=2048 skuid=0 ddt=20 ats=0 androidboot.lb=1 td.td=1 td.s
(bootloader) f=1 td.ofs=328 td.prd=1 td.dly=0 td.tmo=300 hlog.ofs=628 un.
(bootloader) ofs=694 imc_online_log=0 androidboot.efuse_info=SNSL androi
(bootloader) dboot.baseband=1.00.00.1023_3 androidboot.cid=22222222 andro
(bootloader) idboot.devicerev=3 androidboot.batt_poweron=good_battery and
(bootloader) roidboot.carrier=COM
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=local
(bootloader) aARM_Partion[5].name=cache
(bootloader) aARM_Partion[6].name=userdata
(bootloader) aARM_Partion[7].name=devlog
(bootloader) aARM_Partion[8].name=pdata
(bootloader) aARM_Partion[9].name=extra
(bootloader) aARM_Partion[A].name=radio
(bootloader) aARM_Partion.name=adsp
(bootloader) aARM_Partion[C].name=dsps
(bootloader) aARM_Partion[D].name=radio_config
(bootloader) aARM_Partion[E].name=modem_st1
(bootloader) aARM_Partion[F].name=modem_st2
(bootloader) aARM_Partion[10].name=cdma_record
(bootloader) aARM_Partion[11].name=reserve
(bootloader) partition number=18
(bootloader) Valid partition num=18
(bootloader) setting_get_bootmode() = 9
(bootloader) smem 8CF04000 (phy 8CF04000): TZ_HTC_SVC_UPDATE_SMEM ret = 0
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) TZ_HTC_SVC_DISABLE ret = 205643776 (0xC41E000)
(bootloader) jump_to_kernel: machine_id(4060), tags_addr(0x80600100), ker
(bootloader) nel_addr(0x80608000)
(bootloader) -------------------hboot boot time:156503 msec
FAILED (status read failed (Too many links))
finished. total time: 2.904s
C:\adt-bundle-windows-x86\sdk\platform-tools>
I already see what's wrong..
When you
fastboot flash zip P8300000-DNA.ZIP
you flash that not the soffbin3 file the soffbin3 is for later
Sent from my HTC6435LVW using XDA Premium HD app
.torrented said:
I already see what's wrong..
When you
fastboot flash zip P8300000-DNA.ZIP
you flash that not the soffbin3 file the soffbin3 is for later
Sent from my HTC6435LVW using XDA Premium HD app
Click to expand...
Click to collapse
I did do that, It looks like I didn't because I renamed my P8300000-DNA.ZIP file to soff.zip so I wouldn't have to type all those characters.
rootntootn said:
I did do that, It looks like I didn't because I renamed my P8300000-DNA.ZIP file to soff.zip so I wouldn't have to type all those characters.
Click to expand...
Click to collapse
try putting it back to its orig name and then when your in cmd prmpt just type the P and press tab it will fill the rest in (i dont know the exact name so if i were you i would look it up)
if that doesnt work do a data factory reset in recovery and wipe both caches
.torrented said:
try putting it back to its orig name and then when your in cmd prmpt just type the P and press tab it will fill the rest in (i dont know the exact name so if i were you i would look it up)
if that doesnt work do a data factory reset in recovery and wipe both caches
Click to expand...
Click to collapse
I downloaded the file again and used the original name and still a no go gets the remote 99 unknown fail below
sending 'zip' (36905 KB)...
OKAY [ 3.370s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 3.595s
Is it possible I need stock kernal first?
rootntootn said:
I downloaded the file again and used the original name and still a no go gets the remote 99 unknown fail below
sending 'zip' (36905 KB)...
OKAY [ 3.370s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 3.595s
Is it possible I need stock kernal first?
Click to expand...
Click to collapse
The remote 99 for me and for .torrented the night it was released meant that we had to start over, he restored a nandroid backup from before the process and I just wiped and installed the rom clean.
Mine was because I goofed and ran the flash zip command line twice after the error 92 I ran it one more time because I misinterpreted the message.
So I ended up wiping and reflashing the rom, going into settings/developer options and enabling USB debugging, and doing the process correctly and it worked right off the bat.
But for me at least once I got that error 99 I couldn't get past it until I started with clean system files from before I began pushing the adb lines after the system reboot.
CharliesTheMan said:
The remote 99 for me and for .torrented the night it was released meant that we had to start over, he restored a nandroid backup from before the process and I just wiped and installed the rom clean.
Mine was because I goofed and ran the flash zip command line twice after the error 92 I ran it one more time because I misinterpreted the message.
So I ended up wiping and reflashing the rom, going into settings/developer options and enabling USB debugging, and doing the process correctly and it worked right off the bat.
But for me at least once I got that error 99 I couldn't get past it until I started with clean system files from before I began pushing the adb lines after the system reboot.
Click to expand...
Click to collapse
Thanks! I tried doing factory reset and wiped all cache and that also did not work...will find a backup from earlier and go again, I did do some repeats of commands so this sounds like maybe what I need to do...
rootntootn said:
Thanks! I tried doing factory reset and wiped all cache and that also did not work...will find a backup from earlier and go again, I did do some repeats of commands so this sounds like maybe what I need to do...
Click to expand...
Click to collapse
BINGO! That did it. Thanks for everyones help!!
Hi everyone.
Thanks to all of you who help us non-devs upgrade our phones to be so much better than they would be with just stock software and OS. I'm hoping that someone knows how to fix my phone. I have done a lot of reading, and don't intend to be like the bear in that neat animation, "Trying to give a, Phone Idiot, Support," about the noob who fried his phone and doesn't know what kind of phone he has, or what ROM he flashed.
I read several helpful posts, but am still not sure that I have the tools I need to fix this thing. The best lead so far looks to be deBricker's guide to un-brick a Galaxy S3. After some delayed sleep, I might be sane enough (back to about halfway again) to find the right files for my Evo 3d, and will give that approach a try. But I figured I'd post this in case someone out there sees from the data provided, that doing something similar to what deBricker's guide details for a Galaxy, will make things even worse for me. I would appreciate a lead on where to get the right files for my Evo 3d. I'm at least clued in enough to not try the files for the S3 in my Evo 3d. Oh, and I regularly do Nandroid backups.
I have a hard bricked HTC Evo 3d. It's likely my fault for installing something incorrectly, or something that isn't supposed to go on my phone, or for missing something that I should have done prior to installing. Other ROMs I've tried have worked well.
I installed MNRGS2JB108.zip, aka MidnightRomGS2JB, by xthedakmanx. It looked like it was a neat ROM worth trying. But, it was a bad decision, in my case! No blame to anyone (other than me), though. Responsibility is mine, but I sure would love to have someone be hero of the day and tell me how to fix it!
I ended up with NO MEANS OF LOADING OR FLASHING ANYTHING by a battery pull and volume down + power on. Plus, the phone won't even try to power up. In a darkened room, I can sometimes get, with a fully-charged battery, a super-dim, barely-detectable, red power light to light up.
Early on, I saw the not-uncommon QHSUSB_DLOAD on my Win7 laptop when I connected my phone via USB. After some frantic searching around, I got drivers to allow my laptop to now show it on the device manager under ports as "Qualcomm HS-USB QDLoader9000" on COM4. But that hardly lets me just open up a file explorer and fix things.
When I open a cmd box and try to use fastboot commands to flash and such, my laptop does see my phone, briefly (maybe 8 seconds or so, as others have mentioned in other threads), and while I have been able to successfully use some of the commands. Here's what I was able to do, and the information I was able to pull from my phone, in case it helps you guys to figure out what's wrong, and better still, how I can fix it. I think it might be better to give lots of info rather than leaving people playing 20 questions to understand my particular predicament. But, if the following copy-paste is superfluous and of little value after all, sorry about that.
C:\Users\Hedgehog\Desktop\RootEvo4GNew2>fastboot oem readcid
< waiting for device >
...
(bootloader) cid: 11111111
C:\Users\Hedgehog\Desktop\RootEvo4GNew2>fastboot oem checkSbl1
(bootloader) sbl1 signature checking...
(bootloader) TZ_HTC_SVC_VERIFY_BOOTLOADER ret = 0
(bootloader) sbl1 verified successfully
C:\Users\Hedgehog\Desktop\RootEvo4GNew2>fastboot oem checkHWSecurity
...
(bootloader) HW Security has been enabled !
C:\Users\Hedgehog\Desktop\RootEvo4GNew2>fastboot oem keytest
...
(bootloader) start keypad testing ...
FAILED (status read failed (Too many links))
finished. total time: 8.402s
C:\Users\Hedgehog\Desktop\RootEvo4GNew2>fastboot oem heap
...
(bootloader) Total free heap size: 536784792 Bytes (0x1FFEAF98)
(bootloader) Max. free heap segment size: 536760320 Bytes (0x1FFE5000)
(bootloader) Max. free NPC heap segment size: 536760320 Bytes (0x1FFE5000
(bootloader) )
OKAY [ 0.019s]
C:\Users\Hedgehog\Desktop\RootEvo4GNew2>fastboot oem heap_test
...
(bootloader) ======heap_test (Ver: 1.0)======
(bootloader) heap_test <test_mode> <cyles> <break> <cache/non-cache> <ob
(bootloader) verse/reverse> <seed/pattern>
(bootloader) <test_mode> (0): Mix pattern mode -> heap_test 0 <cy
(bootloader) les> <break>
(bootloader) <test_mode> (1): Fix pattern mode -> heap_test 1 <cy
(bootloader) les> <break>
(bootloader) <test_mode> (2): Random pattern mode -> heap_test 2 <cy
(bootloader) les> <break>
(bootloader) <test_mode> (3): Assign seed mode -> heap_test 3 <cyles
(bootloader) > <break> <cache/non-cache> <obverse/reverse> <seed>
(bootloader) <test_mode> (4): Assign fix pattern mode -> heap_test 4 <cy
(bootloader) les> <break> <cache/non-cache> <obverse/reverse> <pattern>
(bootloader) <cyles> The number of testing cycle
(bootloader) <break> Command break off when RAM issue occurs 0:Not break
(bootloader) off 1:Break off when RAM issue occurs
(bootloader) <cache/non-cache> use cache or non-cache memory space 0:cac
(bootloader) he 1:non-cache
(bootloader) <obverse/reverse> assign the direction of scanning 0bvers
(bootloader) e 1:reverse
(bootloader) <seed/pattern> seed to create random pattern for each byte
(bootloader) / pattern for every byte
C:\Users\Hedgehog\Desktop\RootEvo4GNew2>fastboot oem enableqxdm 0
...
(bootloader) Start Verify: -1
(bootloader) Start Verify: -1
(bootloader) erase sector 130560 ~ 131071 (512)
C:\Users\Hedgehog\Desktop\RootEvo4GNew2>fastboot oem gencheckpt
...
(bootloader) Start Verify: -1
(bootloader) Start Verify: -1
(bootloader) erase sector 130560 ~ 131071 (512)
(bootloader) [DISPLAY_ERR] allocate heap for splash image fail!!!
(bootloader) setup_tag addr=0x48000100 cmdline add=0x801DD990
(bootloader) TAG:Ramdisk OK
FAILED (status read failed (Too many links))
finished. total time: 8.495s
C:\Users\Hedgehog\Desktop\RootEvo4GNew2>fastboot oem boot
...
(bootloader) [DISPLAY_ERR] allocate heap for splash image fail!!!
(bootloader) setup_tag addr=0x48000100 cmdline add=0x801DD990
(bootloader) TAG:Ramdisk OK
FAILED (status read failed (Too many links))
finished. total time: 8.580s
C:\Users\Hedgehog\Desktop\RootEvo4GNew2>fastboot oem readimei
...
(bootloader) imei: [my imei number was here]
C:\Users\Hedgehog\Desktop\RootEvo4GNew2>fastboot oem readsecureflag
...
(bootloader) secure_flag: -1
So at least the thing is showing something still inside my phone, and that it can be read. The trouble is, that I'm not able to get it to receive any changes:
C:\Users\Hedgehog\Desktop\RootEvo4GNew2>fastboot flash recovery recovery-clockwo
rk-touch-5.8.0.1-shooter.img
< waiting for device >
sending 'recovery' (4128 KB)...
OKAY [ 0.566s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.567s
C:\Users\Hedgehog\Desktop\RootEvo4GNew2>
That part about "FAILED (remote: not allowed)," is a little saddening, to say the least. And, I've been struggling and worrying about this, a lot longer than 0.567 second! If not for that "not allowed" error, things might be OK. So, is the deBricker's guide the approach to try next?
FWIW, I do have a broken but not bricked, Evo 3d (bad touch screen but probably good data files) that might help supply data files. Yeah, I ought to try pulling stuff off of it and beat the odds and fix it on my own, but I've been reading and tinkering for a couple of days already, and someone else might know just what to do, hence I am humbly asking for some pointers.
Again, sorry for the size of this post, and thanks for any help!
No adb, no recovery. QHSUSB_DLOAD fastboot gets msg FAILED (remote: not allowed)
hedgehog45ve;43863237
...
Early on said:
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.567s
That part about "FAILED (remote: not allowed)," is a little saddening, to say the least.
Click to expand...
Click to collapse
Some additional information I have gotten out of my phone, in case it helps anyone reading this thread, to come up with a fix, is:
platform: HBOOT-8260
modelid: CΣCΣCΣCΣCΣCΣCΣCΣCΣCΣCΣCΣCΣCΣCΣCΣ
cidnum: C
Σ
C:\Users\Hedgehog\Desktop\RootEvo4GNew2>fastboot getvar battery-voltage [DONE WITH THE BATTERY IN]
< waiting for device >
battery-voltage: 3800mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: UNKNOWN
commitno-bootloader: dirty-3f645641
hbootpreupdate: 11
gencheckpt: 0
The main stumbling block I have right now, in addition to not powering up, especially to recovery, is that the phone doesn't stay connected to fastboot longer, and that whatever I try to do to the phone with fastboot, is always rejected, "FAILED (remote: not allowed)".
Any ideas?
Thanks.
when i reboot it , it can't open
i was unlock BootLoader，
all 7.11 system image was been recovery, not useful
reboot it
your device is it can not be trusted and may not to work properly
visit this link on an other device
g.co/ABH
press power to pause boot
ADB command code
C:\ADB>flash-all
Sending 'bootloader' (2901 KB) OKAY [ 0.212s]
Writing 'bootloader' (bootloader) Device State : Unlocked
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[bct] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[mts_preboot_prod] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[mts_prod] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[hboot] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[nvtboot] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[nvtbootwb0] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[tos] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[sp1] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[gp1] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[pt] unzipping & flashing...
(bootloader) ...... Successful
OKAY [ 5.463s]
Finished. Total time: 5.684s
rebooting into bootloader OKAY [ 0.036s]
Finished. Total time: 0.040s
< waiting for any device >
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: 3.50.0.0143
Baseband Version.....: N/A
Serial Number........: HT4ADJT01784
--------------------------------------------
Checking product OKAY [ 0.003s]
Checking version-bootloader OKAY [ 0.004s]
extracting boot.img (8 MB) to disk... took 0.027s
archive does not contain 'boot.sig'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
archive does not contain 'odm.img'
archive does not contain 'product.img'
extracting recovery.img (10 MB) to disk... took 0.033s
archive does not contain 'recovery.sig'
extracting system.img (1453 MB) to disk... took 8.673s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (122 MB) to disk... took 0.785s
archive does not contain 'vendor.sig'
Couldn't parse erase-block-size '0xUnknown command'.
Couldn't parse logical-block-size '0xUnknown command'.
F2FS-tools: mkfs.f2fs Ver: 1.10.0 (2018-01-30)
Info: Disable heap-based policy
Info: Debug level = 0
Info: Label =
Info: Trim is disabled
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 53714944 (26228 MB)
Info: zone aligned segment0 blkaddr: 512
Info: add quota type = 0 => 4
Info: add quota type = 1 => 5
Info: Overprovision ratio = 1.240%
Info: Overprovision segments = 328 (GC reserved = 169)
Info: format successful
Couldn't parse erase-block-size '0xUnknown command'.
Couldn't parse logical-block-size '0xUnknown command'.
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 65536 4k blocks and 65536 inodes
Filesystem UUID: 177cbd32-7522-11e8-8a10-bd7422ec86f1
Superblock backups stored on blocks:
32768
Allocating group tables: done
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'boot' (8636 KB) OKAY [ 0.552s]
Writing 'boot' (bootloader) Device State : Unlocked
OKAY [ 0.829s]
Sending 'recovery' (11204 KB) OKAY [ 0.662s]
Writing 'recovery' (bootloader) Device State : Unlocked
OKAY [ 0.946s]
Sending sparse 'system' 1/4 (478340 KB) OKAY [ 24.143s]
Writing sparse 'system' 1/4 (bootloader) Device State : Unlocked
OKAY [ 20.047s]
Sending sparse 'system' 2/4 (468227 KB) OKAY [ 23.647s]
Writing sparse 'system' 2/4 (bootloader) Device State : Unlocked
OKAY [ 19.934s]
Sending sparse 'system' 3/4 (499117 KB) FAILED (command write failed (Unknown error))
Finished. Total time: 108.734s
Press any key to exit...
can anybaby help me？ how to fix it？
my English not good。
夏默秋殇 said:
when i reboot it , it can't open
i was unlock BootLoader，
all 7.11 system image was been recovery, not useful
reboot it
your device is it can not be trusted and may not to work properly
visit this link on an other device
g.co/ABH
press power to pause boot
ADB command code
C:\ADB>flash-all
Sending 'bootloader' (2901 KB) OKAY [ 0.212s]
Writing 'bootloader' (bootloader) Device State : Unlocked
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[bct] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[mts_preboot_prod] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[mts_prod] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[hboot] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[nvtboot] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[nvtbootwb0] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[tos] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[sp1] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[gp1] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[pt] unzipping & flashing...
(bootloader) ...... Successful
OKAY [ 5.463s]
Finished. Total time: 5.684s
rebooting into bootloader OKAY [ 0.036s]
Finished. Total time: 0.040s
< waiting for any device >
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: 3.50.0.0143
Baseband Version.....: N/A
Serial Number........: HT4ADJT01784
--------------------------------------------
Checking product OKAY [ 0.003s]
Checking version-bootloader OKAY [ 0.004s]
extracting boot.img (8 MB) to disk... took 0.027s
archive does not contain 'boot.sig'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
archive does not contain 'odm.img'
archive does not contain 'product.img'
extracting recovery.img (10 MB) to disk... took 0.033s
archive does not contain 'recovery.sig'
extracting system.img (1453 MB) to disk... took 8.673s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (122 MB) to disk... took 0.785s
archive does not contain 'vendor.sig'
Couldn't parse erase-block-size '0xUnknown command'.
Couldn't parse logical-block-size '0xUnknown command'.
F2FS-tools: mkfs.f2fs Ver: 1.10.0 (2018-01-30)
Info: Disable heap-based policy
Info: Debug level = 0
Info: Label =
Info: Trim is disabled
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 53714944 (26228 MB)
Info: zone aligned segment0 blkaddr: 512
Info: add quota type = 0 => 4
Info: add quota type = 1 => 5
Info: Overprovision ratio = 1.240%
Info: Overprovision segments = 328 (GC reserved = 169)
Info: format successful
Couldn't parse erase-block-size '0xUnknown command'.
Couldn't parse logical-block-size '0xUnknown command'.
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 65536 4k blocks and 65536 inodes
Filesystem UUID: 177cbd32-7522-11e8-8a10-bd7422ec86f1
Superblock backups stored on blocks:
32768
Allocating group tables: done
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'boot' (8636 KB) OKAY [ 0.552s]
Writing 'boot' (bootloader) Device State : Unlocked
OKAY [ 0.829s]
Sending 'recovery' (11204 KB) OKAY [ 0.662s]
Writing 'recovery' (bootloader) Device State : Unlocked
OKAY [ 0.946s]
Sending sparse 'system' 1/4 (478340 KB) OKAY [ 24.143s]
Writing sparse 'system' 1/4 (bootloader) Device State : Unlocked
OKAY [ 20.047s]
Sending sparse 'system' 2/4 (468227 KB) OKAY [ 23.647s]
Writing sparse 'system' 2/4 (bootloader) Device State : Unlocked
OKAY [ 19.934s]
Sending sparse 'system' 3/4 (499117 KB) FAILED (command write failed (Unknown error))
Finished. Total time: 108.734s
Press any key to exit...
can anybaby help me？ how to fix it？
my English not good。
Click to expand...
Click to collapse
Have you tried flashing images 1 at a time? Fastboot flash system system.img
Fastboot flash vendor vendor.img
Etc.
madbat99 said:
Have you tried flashing images 1 at a time? Fastboot flash system system.img
Fastboot flash vendor vendor.img
Etc.
Click to expand...
Click to collapse
yes ，the code
C:\ADB>fastboot flash bootloader bootloader-flounder-3.50.0.0143.img
Sending 'bootloader' (2901 KB) OKAY [ 0.210s]
Writing 'bootloader' (bootloader) Device State : Unlocked
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[bct] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[mts_preboot_prod] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[mts_prod] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[hboot] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[nvtboot] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[nvtbootwb0] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[tos] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[sp1] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[gp1] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[pt] unzipping & flashing...
(bootloader) ...... Successful
OKAY [ 5.447s]
Finished. Total time: 5.677s
C:\ADB>fastboot reboot-bootloader
rebooting into bootloader OKAY [ 0.040s]
Finished. Total time: 0.040s
C:\ADB>fastboot reboot-bootloader
rebooting into bootloader OKAY [ 0.026s]
Finished. Total time: 0.027s
C:\ADB>fastboot flash boot boot.img
Sending 'boot' (8622 KB) OKAY [ 0.520s]
Writing 'boot' (bootloader) Device State : Unlocked
OKAY [ 0.834s]
Finished. Total time: 1.356s
C:\ADB>fastboot flash system system.img
Sending sparse 'system' 1/4 (478340 KB) OKAY [ 24.182s]
Writing sparse 'system' 1/4 (bootloader) Device State : Unlocked
OKAY [ 19.999s]
Sending sparse 'system' 2/4 (468231 KB) OKAY [ 23.622s]
Writing sparse 'system' 2/4 (bootloader) Device State : Unlocked
OKAY [ 19.938s]
Sending sparse 'system' 3/4 (499117 KB) FAILED (command write failed (Unknown error))
Finished. Total time: 95.634s
C:\ADB>fastboot flash cache cache.img
Sending 'cache' (6248 KB) OKAY [ 0.349s]
Writing 'cache' (bootloader) Device State : Unlocked
OKAY [ 0.712s]
Finished. Total time: 1.073s
C:\ADB>fastboot flash vendor vendor.img
Sending 'vendor' (125361 KB) OKAY [ 5.914s]
Writing 'vendor' (bootloader) Device State : Unlocked
OKAY [ 5.715s]
Finished. Total time: 11.640s
C:\ADB>fastboot reboot
Rebooting
Finished. Total time: 0.057s
C:\ADB>
Not sure why that 3rd system sparse chunk is failing. And not even trying the 4th.
Maybe try flashing twrp to recovery and flash a custom rom. Maybe LineageOS.
the recovery photo 。
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[url]https://forum.xda-developers.com/album.php?albumid=14996&pictureid=57661[/URL]
madbat99 said:
Not sure why that 3rd system sparse chunk is failing. And not even trying the 4th.
Maybe try flashing twrp to recovery and flash a custom rom. Maybe LineageOS.
Click to expand...
Click to collapse
The twrp can't load internal Storage 。 when i select storage ，it's 0 MB
i only try fix it in fastboot。
夏默秋殇 said:
The twrp can't load internal Storage 。 when i select storage ，it's 0 MB
i only try fix it in fastboot。
Click to expand...
Click to collapse
Make sure you have the newest twrp. Format data. Not wipe. Format. In twrp wipe-->advanced wipe-->format-->internal storage. Maybe fastboot erase userdata
madbat99 said:
Make sure you have the newest twrp. Format data. Not wipe. Format. In twrp wipe-->advanced wipe-->format-->internal storage. Maybe fastboot erase userdata
Click to expand...
Click to collapse
it's failed
E:Unable to find partition size for '/boot'
E:Unable to find partition size for '/recovery'
E:Unable to find partition size for '/vebdor_image'
E:Unable to find partition size for '/misc'
E:Unable to find partition size for '/persistent'
E:Unable to find partition size for '/system_image'
E: primary block device 'dev/block/platform/sdhci-tegra.3/by-name/UDA' for mount point '/data' is not present!
E:Unable to set bootlader message.
Failed to mount '/cache'(Invalid argument)
Updating partition details....
Failed to mount '/vendor' (Invalid argument)
Failed to mount '/system' (Invalid argument)
Failed to mount '/data' (Invalid argument)
Failed to mount '/cache' (Invalid argument)
...done
Unable to mount storage
Failed to mount '/data' (Invalid argument)
Failed to mount '/cache' (Invalid argument)
Full SELinux support is present
Failed to mount '/cache' (Invalid argument)
Failed to mount '/cache' (Invalid argument)
Unable to mount /data/media/TWRP/.twrps
MTP Enabled
Unable to wipe Data
can somebody help me?
hello？anybody？
hello？
Please make sure you are on a recent version of the adb tools. links for multi os download
Can you try 'fastboot format system' while in bootloader? Does it do a format? If it does you could try the full flash procedure again.
Perhaps twrp recorvery can also help.
flash twrp on your device by using 'fastboot flash recovery twrp-file-you-downloaded.img & fastboot boot twrp-file-you-downloaded.img'
In twrp you should try the format function.
Hi
Hey all.. Im not exactly new here . I just read and read
FMFL
Got same error while LOCKING Bootloader thingy .....
Just keep trying to boot to recovery (Power and and Vol DN then quickly UP) that took me all of 5 minutes to gain the upper hand but I did prevail.... 9 took me hours to get the nutz to hit the Flash Button kept going back and forth re reading a lot of useless **** on a few other sights dont know why i even looked there When all the stuff is always right here
Really its because of all you people here.
Thank you for all the reading keeps my mind young!
Ron T
IT Dept.
Deskside support partner
AECOM
Mississauga, ON
aecom.com
Imagine it. Delivered
---------- Post added at 01:44 AM ---------- Previous post was at 01:41 AM ----------
wow I cant say ****? Tee Hee
No i dont post nearly enough
Roffl I had a couple sites with forums only for satellite TV Hacking I left everything wide open .. ya a few bans but it was needed i guess LOL
CYa
Thx
Ron T
IT Dept.
Deskside support partner
AECOM
Mississauga, ON
aecom.com
Imagine it. Delivered
hallo
help me with the current image have been destroyed and can not boot
hello xda communities i have a realme c1 device after updates my phone show these thing ,,the current image have been destroyed and can not boot.please flash the corrrect image or contact custamer service,,
also show these options-
power off
restart
recovery mode
fastboot mode
back to previous page
and
i can not flash it because of this -
Device state - Locked:
please help me please
goldi gupta said:
hello xda communities i have a realme c1 device after updates my phone show these thing ,,the current image have been destroyed and can not boot.please flash the corrrect image or contact custamer service,,
also show these options-
power off
restart
recovery mode
fastboot mode
back to previous page
and
i can not flash it because of this -
Device state - Locked:
please help me please
Click to expand...
Click to collapse
Try asking in a Realme forum. You posted in Nexus 9, and old tablet Google produced prior to the Pixel line.
Hi,
I entered 0 (zero) before the serial number (I have 7 digit serial number), got an img file from Lenovo. In the "tool all in one" program I unlocked the bootloader. Unfortunately, after restarting the phone does not turn on. I can see only Lenovo logo. What ideas how to fix it?
I have flashed (fastboot method) twrp.img to my locked device and now I'm stuck at boot. At first I was getting boot loop and "corrupt" message (g.co/ABH). Luckily, I could still access fastboot mode. By looking around, I managed to remedy that a bit by:
Code:
$ wget https://dlcdnets.asus.com/pub/ASUS/ZenFone/AI2202/UL-ASUS_AI2202-ASUS-33.0804.2060.100-1.1.1-2302-user.zip
$ unzip *zip
$ payload_dumper payload.bin
$ for i in boot dtbo vendor_boot vbmeta vbmeta_system
do
fastboot flash $i output/$i.img
done
$ fastboot reboot fastboot
# these will fail due to resizing partitions on a locked device
$ for i in system system_ext product odm vendor
do
fastboot flash $i output/$i.img
done
Resizing partition ... (Can't in locked state)
Now I get bootloader, fastbootd, and stock recovery. Wiping/resetting in recovery mode almost succeeds:
Code:
misc_vab_msg.version: 0x2
misc_vab_msg.magic: ...
misc_vag_msg.merge_status: 0x0
misc_vag_msg.source_slot: 0x1
-- Wiping data...
E:Open failed: /metadata/ota: No such file or directory
-- Clean boot sound files...
Formatting /data...
Formatting /metadata...
-- Data wipe complete.
At this point, restarting the system results in the device turning itself off a few seconds after the ASUS logo.
My phone is on stock firmware 33.0804.2060.100 (android 13). Could someone kindly help me and tell me what to do next?
Here's all the info I can get now:
Code:
$ fastboot oem device-info
(bootloader) Verity mode: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Device authorized: false
(bootloader) Device authorized2: false
(bootloader) WaterMask unlock: N
(bootloader) XBL:
(bootloader) ABL: 0.0.029.0-WW-user
(bootloader) SSN: ...
(bootloader) ISN: ...
(bootloader) IMEI: ...
(bootloader) IMEI2: ...
(bootloader) CID: ASUS
(bootloader) COUNTRY: EU
(bootloader) Project: DAVINCI
(bootloader) DT ID: 66
(bootloader) SB: Y
(bootloader) SBNR: Y
(bootloader) DDR Manufacturer ID: 1
(bootloader) DDR Device Type: 8
(bootloader) TotalDMCounter: 0
(bootloader) DMCounter: 0
(bootloader) SlotARetryCounter: 0
(bootloader) SlotAUnbootableCounter: 0
(bootloader) SlotBRetryCounter: 0
(bootloader) SlotBUnbootableCounter: 0
(bootloader) BOOT_COUNT: 0
(bootloader) LOCK_COUNT: 0
(bootloader) Check_APDP: 1
(bootloader) rawdump_en: false
(bootloader) force start logcat-asdf: false
(bootloader) Current Slot: a
(bootloader) Slot_a bootable: Bootable
(bootloader) AVB Verity: Enable
(bootloader) Verify vbmeta ret: 0
(bootloader) ABL_FTM: FALSE
(bootloader) UART-ON Status: false
I have a feeling that I'm not using the right image for this purpose. I don't know how to get my hands on a RAW image. I keep reading about some android beta page, but just can't find a link for Zenfone 9.
You dont need any raw fw, flash stock recovery and reboot:
fastboot flash recovery recovery.img
Download Data package from February 25th.
Size of the data package: 100 MB. Free transfer of up to 6 GB of photos, videos and documents. Send large files via email or a link to share. No registration, no ads, just simple file sharing!
filetransfer.io
Recovery from UL-ASUS_AI2202-ASUS-33.0804.2060.100
@NisseGurra thanks for your input. I checked the md5sum of your recovery image and the one I extracted from the payload.bin. They are indeed the same. I have flashed it alright:
Code:
$ fastboot flash recovery recovery.img
Sending 'recovery' (102400 KB) OKAY [ 3.396s]
Writing 'recovery' OKAY [ 0.162s]
Finished. Total time: 3.570s
Now, what should I do? reboot to bootloader -> recovery? then what?
Because still letting the device boot normally will lead to its shutdown in 20 seconds.
lordbit said:
@NisseGurra thanks for your input. I checked the md5sum of your recovery image and the one I extracted from the payload.bin. They are indeed the same. I have flashed it alright:
Code:
$ fastboot flash recovery recovery.img
Sending 'recovery' (102400 KB) OKAY [ 3.396s]
Writing 'recovery' OKAY [ 0.162s]
Finished. Total time: 3.570s
Now, what should I do? reboot to bootloader -> recovery? then what?
Because still letting the device boot normally will lead to its shutdown in 20 seconds.
Click to expand...
Click to collapse
Seems something got messed up.
You have some options: find an recovery that have adb sideload support: flash the stock fw from it,
adb sideload xxx.zip
Option 2
Repack the stock fw (use payload dumper to extract all img), create an folder with all extracted img and add adb.exe, fastboot.exe, AdbWinApi.dll, AdbWinUsbApi.dll and install.bat (attached, rename to .bat)
Connect phone, enter fastboot and click on the bat file, it should install full rom.
Thanks! I will try it.
I tried your second method. Most of the images got flashed alright, except these ones:
Code:
Sending 'odm' (1248 KB) OKAY [ 0.055s]
Writing 'odm' FAILED (remote: '(odm_a) No such partition')
fastboot: error: Command failed
Sending sparse 'product' 1/4 (524236 KB) OKAY [ 19.285s]
Writing 'product' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Sending sparse 'system' 1/7 (524232 KB) OKAY [ 19.632s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Sending 'system_ext' (386600 KB) OKAY [ 14.180s]
Writing 'system_ext' FAILED (remote: '(system_ext_a) No such partition')
fastboot: error: Command failed
Sending sparse 'vendor' 1/3 (524176 KB) OKAY [ 18.675s]
Writing 'vendor' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Sending 'vendor_dlkm' (73448 KB) OKAY [ 2.577s]
Writing 'vendor_dlkm' FAILED (remote: '(vendor_dlkm_a) No such partition')
fastboot: error: Command failed
I think those should be flashed after a
Code:
fastboot reboot fastboot
But in that case, the "flash" command will try to resize the partitions and I get an error that says "Resizing in a locked state of the device is not possible". I am paraphrasing here.
Option 3, install https://forum.xda-developers.com/t/paranoid-android-topaz-alpha-1-asus-zenfone-9.4557631/
Use the suggested image way. It install new recovery, if i rember correct it has adb support
Reboot recovery and use option2
@NisseGurra sorry if my question seems dumb. But I have not unlocked my bootloader (when I had the chance). Do these recovery.img methods with adb work for me?
lordbit said:
@NisseGurra sorry if my question seems dumb. But I have not unlocked my bootloader (when I had the chance). Do these recovery.img methods with adb work for me?
Click to expand...
Click to collapse
If you bootloader is locked so you cant flash anything not signed by Asus, no twrp etc, So strange it got messed up
Yeah it's weird that you could flash anything at all, that isn't signed
anyway, it seems like you where able to flash the asus recovery?
can you boot it?
If so try booting it and tipe "adb reboot sideload" if everything goes well it should reboot and allow you to sideload unmodified (asus signed) .zips, do this
Also consider data wipe from recovery
Darkmasterhk said:
Yeah it's weird that you could flash anything at all, that isn't signed
anyway, it seems like you where able to flash the asus recovery?
can you boot it?
If so try booting it and tipe "adb reboot sideload" if everything goes well it should reboot and allow you to sideload unmodified (asus signed) .zips, do this
Also consider data wipe from recovery
Click to expand...
Click to collapse
1. I pressed power button + vol-up, ended up in "bootloader" menu.
2. Chose "Recovery mode"
3. At this point, on my laptop, I executed "adb reboot sideload" as you suggested.
However, I am prompted with an error that this device is unauthorized.
Code:
adb devices
List of devices attached
N...P unauthorized
How can I "authorize" this? When I had access to fully-booted system, I just needed to confirm some dialogue. Here there is no question.
Aww that's bad, I don't know how to allow a device from recovery, sorry.
Usually, if it worked under Android itself, it works in recovery as well.
Just to make sure, it worked under Android, right?
I assume u use a Linux system and I somehow had trouble under Linux, with adb and authorization
Yes, "adb" did work between my Linux system and phone before it gets stuck in this mode.
I managed to fix the problem by using a RAW image from romdevelopers. Extracted the content of the zip file and executed "flashall_AFT.cmd" on a Windows machine with the right drivers installed.
For the record, these posts [1][2] are pretty close to what I did.
Thank you both for your support.
EDIT:
I converted the "flashall_AFT.cmd' to "flashall_AFT.sh", so I could be able to achieve the same on a Linux system. USE IT AT YOUR OWN RISK.