Related
Hi folks,
first I apologies for my English!
I have some problems with my Moto G. Bought it very cheap, because it wasn't able to power up.
What I had done already:
It's possible to access the bootloader again. Then I tried to flash a stock firmware.
I got the following error in cmd: (for DE an EU Retail)
C:\Users\Stardust\Desktop\Androidzeug\Moto G\RETAIL-EU_4.4.2_KLB20.9-1.10-1.9_ci
d7_CFC_1FF_v8.xml>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (251136 KB)...
OKAY [ 8.112s]
writing 'system'...
OKAY [ 11.918s]
finished. total time: 20.030s
C:\Users\Stardust\Desktop\Androidzeug\Moto G\RETAIL-EU_4.4.2_KLB20.9-1.10-1.9_ci
d7_CFC_1FF_v8.xml>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (249008 KB)...
OKAY [ 8.034s]
writing 'system'...
OKAY [ 9.454s]
finished. total time: 17.503s
C:\Users\Stardust\Desktop\Androidzeug\Moto G\RETAIL-EU_4.4.2_KLB20.9-1.10-1.9_ci
d7_CFC_1FF_v8.xml>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (214009 KB)...
OKAY [ 6.911s]
writing 'system'...
(bootloader) Failed to validate sparse image
OKAY [ 18.330s]
finished. total time: 25.241s
Click to expand...
Click to collapse
And the Moto G bootloader tells me:
"PIV hash validation failed for PIV entry 0"
Mainly I tried this with many of DE, EU and GB Retails. Also US. (I live in germany)
DE and EU I got the same error. With US the bootloader shows some more errors.
At this state I can try to boot but got sucked in a bootloop sometimes or the Moto G get stacked in a blackscreen after the "bootloaderunlock-warning-logo"
Then i flashed a CWM recovery. And it's possible to enter the Recovery.
And this is the point where i don't know what to do.
I can access bootloader and recovery but can't flash a stock firmware.
Please help me!
PS: Want to past the errors when I flash: US_retail_XT1032_KXB20.9-1.8-1.4_CFC.xml
bootloader inside Moto G:
hab check failed for boot
hab check failed for recovery
hab check failed for system
Invalid PIV signed system image
cmd (last system_sparse.img):
(bootloader) Failed to validate sparse image
ikarugaski said:
Hi folks,
first I apologies for my English!
I have some problems with my Moto G. Bought it very cheap, because it wasn't able to power up.
What I had done already:
It's possible to access the bootloader again. Then I tried to flash a stock firmware.
I got the following error in cmd: (for DE an EU Retail)
And the Moto G bootloader tells me:
"PIV hash validation failed for PIV entry 0"
Mainly I tried this with many of DE, EU and GB Retails. Also US. (I live in germany)
DE and EU I got the same error. With US the bootloader shows some more errors.
At this state I can try to boot but got sucked in a bootloop sometimes or the Moto G get stacked in a blackscreen after the "bootloaderunlock-warning-logo"
Then i flashed a CWM recovery. And it's possible to enter the Recovery.
And this is the point where i don't know what to do.
I can access bootloader and recovery but can't flash a stock firmware.
Please help me!
PS: Want to past the errors when I flash: US_retail_XT1032_KXB20.9-1.8-1.4_CFC.xml
bootloader inside Moto G:
hab check failed for boot
hab check failed for recovery
hab check failed for system
Invalid PIV signed system image
cmd (last system_sparse.img):
(bootloader) Failed to validate sparse image
Click to expand...
Click to collapse
Those Errors are supposed to be normal my Friend!
They shouldn't be an issue!
Did you stop at the error? or did you complete the process?
Thaks for the answer!
Yes, I run it several times until the end. Just followed the "Moto G - Restore stock firmware" guide.
But this little G beast won't boot up.
Sometimes it does something like a bootloop and sometimes it ends in a blackscreen after the logo.
But then.... nothing.
ikarugaski said:
Thaks for the answer!
Yes, I run it several times until the end. Just followed the "Moto G - Restore stock firmware" guide.
But this little G beast won't boot up.
Sometimes it does something like a bootloop and sometimes it ends in a blackscreen after the logo.
But then.... nothing.
Click to expand...
Click to collapse
You own a DE Retail correct?
I'll help you after I write tomorrow's exam
Hi, try this guide, it worked for me.
https://www.youtube.com/watch?v=laU6NQ0LxR0
@deej_roamer
good luck for your exam!
Yeah, I think its an Retail, but maybe it could be an "O2 Germany" (the Moto bill says something of an O2 Combo). As I sayed I buyed it bricked.
Take youre time. I don't have freetime during weekend for the G.
Thanks for the link kirmr. I'll have a look.
I own a Moto G from O2 myself, however I was able to flash the regular german retail version without any errors (except for removing O2's bloatware, but I wouldn't exactly count that as an error ).
You might want to try redownloading the rom, extract it or try the german retail version. The error simply says that the disk image could not be validated. This could be because the sparse-images are defect, got written incorrectly or there might be an actual defect on the disk.
ikarugaski said:
@deej_roamer
good luck for your exam!
Yeah, I think its an Retail, but maybe it could be an "O2 Germany" (the Moto bill says something of an O2 Combo). As I sayed I buyed it bricked.
Take youre time. I don't have freetime during weekend for the G.
Thanks for the link kirmr. I'll have a look.
Click to expand...
Click to collapse
Did you try flshing this firmware?
Thanks for the wishes though!
If that doesnt work!
Please post your bootloader info. Copy what's written when bootloader boots.
That would give a better view!
EDIT: IF you are a lazy ass like me and dont wont to type. I suggest dump output of "fastboot getvar all" here
I'm back and now we can solve the problem hopefully!
I'll post a picture where you can see all firmware i had tried. (thats why i'm thinking all of them can't be defect. )
As you can see the one you suggested is in that list.
Just flashing the firmware again than i'll past the bootloader info here.
{
"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"
}
That's the answer of the getvar all command:
(bootloader) version: 0.5
(bootloader) version-bootloader: 4105
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: ***
(bootloader) cid: 0x0007
(bootloader) uid: 59D062020F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: ***
(bootloader) meid:
(bootloader) date: 01-24-2014
(bootloader) sku: XT1032
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Jan 6 6: 7: 5 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_retde/falcon_umts:
(bootloader) ro.build.fingerprint[1]: 4.3/14.10.0Q3.X-76-LGG-11/57:user/
(bootloader) ro.build.fingerprint[2]: release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.14.91.11.falcon_umts
(bootloader) ro.build.version.full[1]: .Retail.en.DE
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_JB_3.2_RB2.04.03
(bootloader) ro.build.version.qcom[1]: .00.129.057
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.0-g7161c60 ([email protected]
(bootloader) kernel.version[1]: l93lnxdroid92) (gcc version 4.7 (GCC) )
(bootloader) kernel.version[2]: #1 SMP PREEMPT Fri Oct 25 00:41:55 CDT 2
(bootloader) kernel.version[3]: 013
(bootloader) sdi.git: git=MBM-NG-V41.05-0-gac19e15
(bootloader) sbl1.git: git=MBM-NG-V41.05-0-g6863770
(bootloader) rpm.git: git=MBM-NG-V41.05-0-g4018bbe
(bootloader) tz.git: git=MBM-NG-V41.05-0-g11658be
(bootloader) aboot.git: git=MBM-NG-V41.05-0-gf4ab363
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 1/1
all: listed above
finished. total time: 0.109s
Click to expand...
Click to collapse
I have Problems since months to Flash Stock JB or Kitkat. Every Time if i try to Boot, the Phone get stucked..
Only GPE Fastboot Flash Works great for me. After this i van Flash Every Rom with twrp..
Gesendet von meinem Moto G mit Tapatalk
Just now i tried to install something via TWRP / CWM (sideload because i had no assecc
Both are
- unable to mount /system
- unable to mount /data
- unable to mount /cache
ikarugaski said:
Just now i tried to install something via TWRP / CWM (sideload because i had no assecc
Both are
- unable to mount /system
- unable to mount /data
- unable to mount /cache
Click to expand...
Click to collapse
Format all of them! i mean /system /data /cache
I am unable to install Stock Firmware on My MOTO G
hydromän said:
I have Problems since months to Flash Stock JB or Kitkat. Every Time if i try to Boot, the Phone get stucked..
Only GPE Fastboot Flash Works great for me. After this i van Flash Every Rom with twrp..
Gesendet von meinem Moto G mit Tapatalk
Click to expand...
Click to collapse
Plz read this .... Give A Solution ... I hope U can Solve This Problem
I did following steps....
1. Installed motarola usb drivers, minimal adb drives and Adroid sdk
2.Extracted stock firmware by using win.rar (fastboot_falcon_asia_ds_user_4.3_14.10.0Q3.X-84-7-LCG-4_4_release-keys-cid7-AsiaRetail_03.tar.gz) file into folder which contains adb.exe and other stuff (C:\Android-SDK\platform-tools)
3. For Downgrading: i deleted following text and saved
Lines 89-90 in the flashall.bat file:
Code:
CALL :fastboot_flash partition gpt.bin
IF %errorlevel% NEQ 0 EXIT /b 1
Lines 120-121 in the flashall.sh file:
Code:
run $fastboot -s "$serial_number" flash partition gpt.bin
if [ $? -ne 0 ]; then echo "ERROR: fastboot failed."; exit -1; fi
4. Turn off the phone for 5 seconds.
Press and hold Volume Down + Power buttons together for few seconds until a Bootloader mode gets appeared
Connected the device to PC through a USB Cable.
Now on PC, go under the extracted files, there pressed “**** Key + Right Mouse Click” button, then from this selected “open command window here“. A command prompt window will opened.
On command prompt window, typed the following command:
flashall.bat /eu
installed the firmware, it take from 5-10 minutes to complete.
Its done, phone is restarted....
5. After that unlock bootloader warning massage appear for 5sec. then black screen and stacked...
no pink color warning massages while installing
deej_roamer said:
Format all of them! i mean /system /data /cache
Click to expand...
Click to collapse
I think there is the problem...
formatting 'system' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.047s
Click to expand...
Click to collapse
I don't know if it's possible to repair a corrupted filesystem...
ikarugaski said:
I think there is the problem...
I don't know if it's possible to repair a corrupted filesystem...
Click to expand...
Click to collapse
I meant from recovery not fastboot!
Okay, that worked fine for me in CWM!
Could you find something in the "getvar" text btw?
These creepy moto still won't boot. :silly:
Just want to mention that the command format will not work.
Instead you have to use erase.
Is it possible to format boot in CMW somehow?
I don't know how, but today i managed to see the CM logo with the cycling arrow, after flashing CM11 with CMW.
But it doesn't boot up, got stuck in the logo with cycling arrow.
And it only showed up ones, never saw it again.
I don't know what happens to the Moto but everything is quite irregular.
Sometimes it boot recovery (sometimes it won't), sometimes got suck with the "warning bootloader" or after that in blackscreen, ones it shows the CM11 logo....
Hello everyone.
I am hoping someone might be able to help me out.
I had been using the sensation for a while with the s-off bootloader with no problems.
Recently I tried to update it to see how it would work on the lolipop builds that are out.
I updated the recovery to 2.8.3.0 TWRP and tried to flash the rom.
It looked like it completeled normally but when I went to restart the phone it will only boot into the fastboot of the boot loader. I can not get it to boot into the rom or recovery.
I have tried to reflash the recovery using fastboot but get the following error:
FAILED (remote: image update error)
I used the command (fastboot flash recovery recovery.img) to try and flash a previous one that worked.
I can use fastboot to boot the recovery though and then it will load.
But when the recovery is loaded or by using the adb terminal I can not access any of the partitions.
It seems like the partition table is corrupted.
I have been trying to find a hboot to reflash but I also can not seem to use the command
fastboot OEM reboot RUU
That command gives me the following error
...
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(732): error 2
(bootloader) Start Verify: 0
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(732): error 2
(bootloader) Start Verify: 0
(bootloader) erase sector 130560 ~ 131071 (512)
(bootloader) emmc_erase(1852): sd_write_sector failed!
OKAY [ 0.081s]
finished. total time: 0.082s
Currently the phone is on Firmware 3.33
s-off
hboot 1.27.110
Does anyone know where I might be able to find the firmware / hboot to reflash to see if that fixes the partitions on the phone?
Or any other way to fix this?
I am finding it hard to try and dig up files that have working links for this device anymore.
If I am not mistaken, reflashing the firmware should be able to fix it though.
I think I might need to find the RUU and just reflash back to stock and am waiting on the download for that as we speak. Just dreading going through and rerooting the phone again.
The wire part was really tricky.
Any help would be greatly appreciated.
Thank you for your time to read this.
TheArtiszan said:
Hello everyone.
I am hoping someone might be able to help me out.
I had been using the sensation for a while with the s-off bootloader with no problems.
Recently I tried to update it to see how it would work on the lolipop builds that are out.
I updated the recovery to 2.8.3.0 TWRP and tried to flash the rom.
It looked like it completeled normally but when I went to restart the phone it will only boot into the fastboot of the boot loader. I can not get it to boot into the rom or recovery.
I have tried to reflash the recovery using fastboot but get the following error:
FAILED (remote: image update error)
I used the command (fastboot flash recovery recovery.img) to try and flash a previous one that worked.
I can use fastboot to boot the recovery though and then it will load.
But when the recovery is loaded or by using the adb terminal I can not access any of the partitions.
It seems like the partition table is corrupted.
I have been trying to find a hboot to reflash but I also can not seem to use the command
fastboot OEM reboot RUU
That command gives me the following error
...
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(732): error 2
(bootloader) Start Verify: 0
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(732): error 2
(bootloader) Start Verify: 0
(bootloader) erase sector 130560 ~ 131071 (512)
(bootloader) emmc_erase(1852): sd_write_sector failed!
OKAY [ 0.081s]
finished. total time: 0.082s
Currently the phone is on Firmware 3.33
s-off
hboot 1.27.110
Does anyone know where I might be able to find the firmware / hboot to reflash to see if that fixes the partitions on the phone?
Or any other way to fix this?
I am finding it hard to try and dig up files that have working links for this device anymore.
If I am not mistaken, reflashing the firmware should be able to fix it though.
I think I might need to find the RUU and just reflash back to stock and am waiting on the download for that as we speak. Just dreading going through and rerooting the phone again.
The wire part was really tricky.
Any help would be greatly appreciated.
Thank you for your time to read this.
Click to expand...
Click to collapse
Okay so the only good news I can see is that if you can make the RUU run it will not s-on your phone so rooting will be easy but, if fastboot oem reboot RUU doesn't work then your in alot of trouble. When you download the RUU (any I'd one for the sensation of XE will do) run it and then extract the .zip (search on Google if you are unsure how to) when you have that extract everything and then move system.img data.img and anything rom related out of the folder. Your aiming to only have hboot related items and the android txt file in there. Zip it back up by highlighting all the files and make a zip file, not by zipping the folder. Rename the zip file to the device model number with img (i think its pg58img.zip) then pass it to your sdcard and then reboot to hboot.
If your hboot can "update" it will hopefully be able to restore/remake your damaged partition table but if that fails your options are really limited. A J-tag would be able to restore the devices partition tables forcefully but you would need a repair shop to do that.
Sent from my LG-D802 using Tapatalk
heavy_metal_man said:
A J-tag would be able to restore the devices partition tables forcefully but you would need a repair shop to do that.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
or if you know what to do about jtag method see here
http://forum.xda-developers.com/showthread.php?t=2775115
Yeah I think I'm toast then.
I tried grabbing the default Rom .zip and flash with boot loader and that failed.
Not sure if it needed to be on a gold card or not though.
TheArtiszan said:
Yeah I think I'm toast then.
I tried grabbing the default Rom .zip and flash with boot loader and that failed.
Not sure if it needed to be on a gold card or not though.
Click to expand...
Click to collapse
Shouldn't make a difference as you are s-off.
What happens if you issue the command. Fastboot getvar all
Does it work?
Sent from my LG-D802 using Tapatalk
I cant unlock the boot-loader because it sayd the password is wrong
I gave moto the code i got from fastboot oem get_unlock_data
whitch retuned this:
Code:
(bootloader) A000002CE5E9CC00#54413936353043
(bootloader) 38485500585431303331000000#236B
(bootloader) D082967F45C8B0297B92C52C7DBCF8D
(bootloader) 774E9#A1AC35030F000008000000000
(bootloader) 0000000
the email returned with the unlock code:
Code:
6OJPYDKQQXR2DMSL5UHU
but the bootloader is rejecting it saying
Code:
(bootloader) Password incorrect!
(bootloader) OEM unlock failure!
FAILED (remote failure)
finished. total time: 0.316s
what do i do?
Trying a different code. Still failed.
tried again from a diffrent PC and got a diffrent code...
Code:
ROV6AISPVK4CMKGSMLDR
but still replied as werong
I had the same problem. I solved it by following the instructions in this zip. It involves upgrading the bootloader, unlocking, then downgrading it.
I have a Google Fi edition X4, and I may have bricked it. What led to me trying it is that we just got a new ISP and an Eero setup, and the phone just isn't working well with the wifi. My daughter has a retail / Amazon X4, and she's had no problems. I thought flashing it to a different ROM might help. Obviously I screwed up somewhere.
I've been following the instructions at https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348
The ./fastboot devices command works just fine, and it finds the device. I can run other fastboot commands such as ./fastboot getvar all.
However, when I ran the flash-all.sh script, I get a bunch of errors. I've tried again using the Google Fi ROM linked from the article. Here's a sample of the errors I see:
Setting current slot to 'a' FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:modem_a: not found
(bootloader) is-logical:fsg_a: not found
. . . lots of things not found. I also get a big block when it tries to do the system:
(bootloader) WARNING: OEM images are required in the LOCKED state.
(bootloader) Flashing images can result in a non-boot condition.
(bootloader) Flash a proper OEM signed boot.img first.
(bootloader) *****************************************************
(bootloader) flash permission denied
When the phone reboots, I get a setup screen, where it first asks if I have a SIM (I took it out) then it tries to setup wifi, but can't find anything.
Of course, I didn't make a backup before doing any of this. I think somewhere in my subconscious I may be looking for an excuse to get a new phone or something. Any ideas of what I should try next?
Do you have qcn or efs backup , if you have then can you provide that
Hi all,
Maybe someone could push me in the right direction here. I unlocked my HTC U11 and went searching for a good CFW with MHL support. Sadly many don't have decent MHL support, thanks Google! I went into recovery steps, locked the bootloader and flashed official 3.34.401.1 rom. That went fine, but now the phone is stuck at the pattern screen.
Phone works fine, but the pattern is not set by me, almost as if the stock firmware has some secret pattern. It won't ask me to setup my google account and factory defaults doesn't fix the issue.
Current rom file: 2PZCIMG_OCEAN_UHL_P90_SENSE10GP_MR_HTC_Europe_3.34.401.1_Radio_8998-200321-1905141529_release_signed.zip
Device info:
(bootloader) kernel: lk
(bootloader) product: htc_ocnuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1560000000
(bootloader) serialno: xxxx
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: xxxx
(bootloader) version-main: 3.34.401.1
(bootloader) boot-mode: download
(bootloader) version-baseband: 8998-200321-1905141529
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PZC10000
(bootloader) cid: HTC__034
Thanks in advance!
ristodesign said:
Device info:
(bootloader) kernel: lk
(bootloader) product: htc_ocnuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1560000000
(bootloader) serialno: xxxx
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: xxxx
(bootloader) version-main: 3.34.401.1
(bootloader) boot-mode: download
(bootloader) version-baseband: 8998-200321-1905141529
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PZC10000
(bootloader) cid: HTC__034
Click to expand...
Click to collapse
To the one/those answering:
How can one have 0 slots?
That's odd, isn't it? I mean there are a/b partitioned devices and 'a' partioned devices out there.
So the slot-count is either 2 (a/b) or 1 (a).
To @ristodesign: Before flashing you had no pattern? And you did a factory data reset with your recovery?
Hi, yes. I tested LineageOS and Goole PixelExperience, but should have known there was no MHL support. Then I tried Viper and LeeDroid, but those didn't enable Wifi somehow.
Then decided to get back to the stock ROM provided by Ziand: https://androidfilehost.com/?fid=1899786940962575313
Locked the bootloader and renamed the rom file to 2PZCIMG.zip so I could restore from booting in download. File was accepted and everything went back to normal. Got a welcome screen, was forced to enable wifi, then suddenly some pattern lock, which does not give any option to escape. Perviously used patterns are certainly not working.
Factory reset does not clear the pattern lock. Which makes me quite unique I guess. ;-)
ristodesign said:
Hi, yes. I tested LineageOS and Goole PixelExperience, but should have known there was no MHL support. Then I tried Viper and LeeDroid, but those didn't enable Wifi somehow.
Then decided to get back to the stock ROM provided by Ziand: https://androidfilehost.com/?fid=1899786940962575313
Locked the bootloader and renamed the rom file to 2PZCIMG.zip so I could restore from booting in download. File was accepted and everything went back to normal. Got a welcome screen, was forced to enable wifi, then suddenly some pattern lock, which does not give any option to escape. Perviously used patterns are certainly not working.
Factory reset does not clear the pattern lock. Which makes me quite unique I guess. ;-)
Click to expand...
Click to collapse
Maybe you can try to boot twrp and see if it asks to decrypt?
The thing is: Passwords, pins, patterns etc. should be stored in the userdata partition. If you wipe this partition, the pattern should be gone.
However, if you manage to boot twrp and to have the userdata partition decrypted (go to /data and see if those entries aren't "randomized" letters), we should be able to delete this manually.
Else I'd like to know whether that pattern has been coded into the update zip you applied... Don't know how to accomplish that, however. But I'll see if I figure out something for the case twrp doesn't work.
You could also try another file like this one from here: https://htcstockrom.com/htc-u11
Will try to get trwp back on the device. It was removed and USB debugging probably disabled.
I did try the rom at https://htcstockrom.com/htc-u11 , after all those Visual C++ x86/x64 fixes it finally worked to start, but at the end it wouldn't accept to downgrade 3.34.401.1 to 2.42.617.7.
ristodesign said:
Will try to get trwp back on the device. It was removed and USB debugging probably disabled.
I did try the rom at https://htcstockrom.com/htc-u11 , after all those Visual C++ x86/x64 fixes it finally worked to start, but at the end it wouldn't accept to downgrade 3.34.401.1 to 2.42.617.7.
Click to expand...
Click to collapse
I see.
You only need to boot twrp temporarily, no need to flash it. Just do:
Code:
fastboot boot twrp.img
EDIT: What if you reflash LineageOS and then the older firmware mentioned above?
LineageOS should allow downgrades.
Good idea, i tried with this result:
downloading 'boot.img'...
OKAY [2.4sec]
booting...
(Then it stops)
Phone screen shows:
Flash image succes
Start downloading (1/1)
It stops there.
ristodesign said:
Good idea, i tried with this result:
downloading 'boot.img'...
OKAY [2.4sec]
booting...
(Then it stops)
Phone screen shows:
Flash image succes
Start downloading (1/1)
It stops there.
Click to expand...
Click to collapse
Oh, well...
That's strange... Then go for the method you already know.
What did you do earlier to flash twrp? Same command but "flash boot"?
EDIT:
I think you flashed it using
Code:
fastboot flash recovery twrp.img
right?
If so, maybe you can boot it somehow similar like this:
Code:
fastboot boot recovery twrp.img
.
Earlier I had to unlock the phone with the HTC Dev website. I created an Unlock_code.bin file. But if I try to flash now it will not accept.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 1.002s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
So USB debugging and the OEM lock seems to have set to default by flashing the stock rom.
ristodesign said:
Earlier I had to unlock the phone with the HTC Dev website. I created an Unlock_code.bin file. But if I try to flash now it will not accept.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 1.002s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
So USB debugging and the OEM lock seems to have set to default by flashing the stock rom.
Click to expand...
Click to collapse
If you do
Code:
fastboot getvar all
do you get something like this?:
(bootloader) unlocked:yes
Click to expand...
Click to collapse
Nope, it does not. When I try to flash it states that the bootloader is locked. The phone screen shows:
HTC download mode
*** RELOCKED ***
*** PRODUCTION ***
htc_ocnuhl PVT S-ON
yada yada yada... ;-)
ristodesign said:
Nope, it does not. When I try to flash it states that the bootloader is locked. The phone screen shows:
HTC download mode
*** RELOCKED ***
*** PRODUCTION ***
htc_ocnuhl PVT S-ON
yada yada yada... ;-)
Click to expand...
Click to collapse
Well, maybe you should research how to unlock an relocked bootloader.
I heard that some bootloader won't unlock again after relocking, which is why I never relocked my devices bootloader...
Hehe, yes it might be not too smart but it was the fastest solution as I could not find a working MHL CFW. I'll give my kids some money if they can find the pattern lol.