Related
Is there a way to sim unlock my htc one v?
I've unlocked the bootloader, rooted the device, put it on s-off, installed CyanogenMod Android 4.1.2, kernel version 3.0.16-HELLBOY; i flashed the kernel and rom; i tried to upgrade the ruu but it returned me the error 131 which reffered to some incompatibility ruu, even tho it was the most appropiate one.
another thing i tried was to hack into the mmcblk0p6 and take the un_lock_code but the unlock.sh returned me this error:
[email protected]:/ # IMEI:
[email protected]:/ # UN_Lock_code:
[email protected]:/ # /system/unlock.sh[34]: + + : unexpected 'end of expression'
my radio is 3831.19.00.120. The network is locked on O2, UK. I've tried a lot of things, but nothing worked.
Can you help me guys?
Thanks in advance!
XTZY23 said:
Is there a way to sim unlock my htc one v?
I've unlocked the bootloader, rooted the device, put it on s-off, installed CyanogenMod Android 4.1.2, kernel version 3.0.16-HELLBOY; i flashed the kernel and rom; i tried to upgrade the ruu but it returned me the error 131 which reffered to some incompatibility ruu, even tho it was the most appropiate one.
another thing i tried was to hack into the mmcblk0p6 and take the un_lock_code but the unlock.sh returned me this error:
[email protected]:/ # IMEI:
[email protected]droid:/ # UN_Lock_code:
[email protected]:/ # /system/unlock.sh[34]: + + : unexpected 'end of expression'
my radio is 3831.19.00.120. The network is locked on O2, UK. I've tried a lot of things, but nothing worked.
Can you help me guys?
Thanks in advance!
Click to expand...
Click to collapse
That depends on what fastboot commands your hboot supports. If you have an eng hboot you can remove simlock with fastboot. But I cannot remember the command off hand. Connect up to the pc in fastboot mode and issue the.command fastboot oem h and it will output all the options available. Post them here for us all to learn from please
Sent from my HTC Desire S using Tapatalk
htc one v_commands
heavy_metal_man said:
That depends on what fastboot commands your hboot supports. If you have an eng hboot you can remove simlock with fastboot. But I cannot remember the command off hand. Connect up to the pc in fastboot mode and issue the.command fastboot oem h and it will output all the options available. Post them here for us all to learn from please
Sent from my HTC Desire S using Tapatalk
Click to expand...
Click to collapse
this is what it returned:
C:\Fastboot>fastboot oem h
...
(bootloader) command list
(bootloader) get_identifier_token
(bootloader) checkKeycardID
(bootloader) keytest
(bootloader) heap
(bootloader) boot
(bootloader) reset
(bootloader) powerdown
(bootloader) rebootRUU
(bootloader) heap_test
(bootloader) erase_phone_storage
(bootloader) gotohboot
(bootloader) rtask
(bootloader) task
(bootloader) enableqxdm
(bootloader) gencheckpt
(bootloader) readmeid
(bootloader) lock
(bootloader) writesecureflag
(bootloader) readsecureflag
(bootloader) readsimlocktype
(bootloader) clearsimlocktype
(bootloader) readcid
(bootloader) writecid
(bootloader) list_partition_emmc
(bootloader) load_emmc
(bootloader) check_emmc
(bootloader) check_emmc_mid
(bootloader) read_mmc
(bootloader) read_sandisk_fw
(bootloader) get_wp_info_emmc
(bootloader) send_wp_info_emmc
(bootloader) get_ext_csd_emmc
(bootloader) get_sector_info_emmc
OKAY [ 0.041s]
finished. total time: 0.042s
C:\Fastboot>
XTZY23 said:
(bootloader) readsimlocktype
(bootloader) clearsimlocktype
(bootloader) readcid
(bootloader) writecid
Click to expand...
Click to collapse
I would use these 2 sets here. First make a nandroid backup, just incase
Then issue these fastboot commands one after another and copy the results.
Fastboot oem readcid
Fastboot oem readsimlocktype
All good? Now first we want to change your cid to super. So issue this command
Fastboot oem writecid 11111111
Fastboot reboot bootloader
Fastboot oem readcid
Your cid should now show up as 11111111, that's 8 1's
All good? Lastly we issue these commands.
Fastboot oem clearsimlocktype
Fastboot reboot
Now just check your simcard and all should be well you can now flash any ruu for any carrier without issue, but always check its compatible with your model type first!
Sent from my HTC Desire S using Tapatalk
fisrt step:
C:\Fastboot>fastboot oem readcid
...
(bootloader) cid: O2___001
OKAY [ 0.003s]
finished. total time: 0.004s
C:\Fastboot>fastboot oem readsimlock
type
...
(bootloader) sdcc_init_memory_device done
(bootloader) Wait for AMSS ready
(bootloader) AMSS is ready
(bootloader) readsimlocktype: SimLockType: 0
OKAY [ 21.759s]
finished. total time: 21.760s
step 2:
C:\Fastboot>fastboot oem writecid 11
111111
...
(bootloader) AMSS is ready
(bootloader) buf_addr:4FC300,buf_size:200,start_sector:1739D
(bootloader) sdcc_init_memory_device done
(bootloader) Finish write sector address 1739D ...
(bootloader) writecid: successfully
OKAY [ 0.691s]
finished. total time: 0.692s
C:Fastboot>fastboot reboot-bootload
er
rebooting into bootloader...
OKAY [ 0.151s]
finished. total time: 0.153s
C:\Fastboot>fastboot oem readcid
...
(bootloader) cid: 11111111
OKAY [ 0.004s]
finished. total time: 0.005s
C:\Fastboot>fastboot oem clearsimloc
ktype
...
(bootloader) sdcc_init_memory_device done
(bootloader) Wait for AMSS ready
(bootloader) AMSS is ready
OKAY [ 21.758s]
finished. total time: 21.760s
C:\Fastboot>fastboot reboot
rebooting...
finished. total time: 0.155s
C:\Fastboot>
XTZY23 said:
fisrt step:
C:\Fastboot>fastboot oem readcid
...
(bootloader) cid: O2___001
OKAY [ 0.003s]
finished. total time: 0.004s
C:\Fastboot>fastboot oem readsimlock
type
...
(bootloader) sdcc_init_memory_device done
(bootloader) Wait for AMSS ready
(bootloader) AMSS is ready
(bootloader) readsimlocktype: SimLockType: 0
OKAY [ 21.759s]
finished. total time: 21.760s
step 2:
C:\Fastboot>fastboot oem writecid 11
111111
...
(bootloader) AMSS is ready
(bootloader) buf_addr:4FC300,buf_size:200,start_sector:1739D
(bootloader) sdcc_init_memory_device done
(bootloader) Finish write sector address 1739D ...
(bootloader) writecid: successfully
OKAY [ 0.691s]
finished. total time: 0.692s
C:Fastboot>fastboot reboot-bootload
er
rebooting into bootloader...
OKAY [ 0.151s]
finished. total time: 0.153s
C:\Fastboot>fastboot oem readcid
...
(bootloader) cid: 11111111
OKAY [ 0.004s]
finished. total time: 0.005s
C:\Fastboot>fastboot oem clearsimloc
ktype
...
(bootloader) sdcc_init_memory_device done
(bootloader) Wait for AMSS ready
(bootloader) AMSS is ready
OKAY [ 21.758s]
finished. total time: 21.760s
C:\Fastboot>fastboot reboot
rebooting...
finished. total time: 0.155s
C:\Fastboot>
Click to expand...
Click to collapse
Did it simunlock OK?
Sent from my Nexus 7 using Tapatalk
Hmm, maybe yes maybe not
It passed the sim network locked screen, but now it says "no network available" and when im making a call, it says "mobile network unavailable" \
I REINSTALLED THE RUU i was trying to install it in the first place and it worked. so thanks for your help
PS: the new challenge is this error: mobile network unavailable because it is disconnected
************update***************
1.last night i put s-on on my phone...but
2.even on s-off i could not unlock the bootloader after installing the RUU_PRIMO_U_ICS_40A_HTC_Europe_2.22.401.1_Radio_20.76.30.0835U_3831.19.00.120_release_273801_signed
3. no bootloader unlock->no root->no s-off->no simlock
4. the message header is ****Relocked**** and the error the i receive when i try to unlock the bootloader again is:
C:\Fastboot>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.640s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.650s
***********fixed this one*************
HTC ONE toolkit 2.0-Squabbi-- saved me fro a lot o work! great thanks to squabbi!
XTZY23 said:
It passed the sim network locked screen, but now it says "no network available" and when im making a call, it says "mobile network unavailable" \
I REINSTALLED THE RUU i was trying to install it in the first place and it worked. so thanks for your help
PS: the new challenge is this error: mobile network unavailable because it is disconnected
Click to expand...
Click to collapse
http://www.sieempi.eu/blog/2011/09/22/universal-sim-unlock-for-s-offed-htc-devices-536 ok give this a bash pal. will hopefully fix the issue.
GSM problem/hardware problem
thanks heavy_metal_man for replies!
the config.dat file worked, partially i think, returning only one error: Open Cid file failed.
as i could see my phone does not react to find any mobile network available, even tho my phone is "reading" the simcard now. i can see contacts, messages, etc.
ps: i don't have the back cover. would that be the problem?
XTZY23 said:
thanks heavy_metal_man for replies!
the config.dat file worked, partially i think, returning only one error: Open Cid file failed.
as i could see my phone does not react to find any mobile network available, even tho my phone is "reading" the simcard now. i can see contacts, messages, etc.
ps: i don't have the back cover. would that be the problem?
Click to expand...
Click to collapse
The back cover for these kinds of phones usually have "antenna boosting" pads. My htc sensation gets no signal without the back cover on.
For anyone else I would recommend trying the linked website solution from sieempi before fastboot commands
Sent from my Nexus 7 using Tapatalk
I am fixing a TMO Htc One M8 for a friend. He currently has TWRP recovery but nothing will wipe or flash. I have posted the get var information and the log below along with all the steps I've taken, please share any insight into the matter.
Here is the Get VAR Information. I have tried to fix this device by relocking the Bootloader, flashing stock RUU RUU_M8_TMOUS_1.57.531.7 , Flashing modified firmware.zip, flashing recovery.img, nothing. Then unlocking the bootloader, flashing Philz recovery.img, Twrp.img, still same error. Current TWRP recovery registers nothing but errors. No wiping data, cache, system, etc. No installing backup nandroid, no flashing new rom through external SD card or adb sideload. Literally the phone won't flash anything and the error is error 12, "Remote signature verifiey failed" What kinda insight do you have into this? Anyway to get back to stock?
Thanks!
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.16.21331931.LA24G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA446WM02874
(bootloader) imei: 352628060329457
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(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: 6e0f5a3d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.044s
LOG: D:\All Android Devices\T Mobile HTC One M8>fastboot flash flash TMOUS-M8-1.12.53
1.19.recovery.img
sending 'flash' (24576 KB)...
OKAY [ 1.691s]
writing 'flash'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.953s
D:\All Android Devices\T Mobile HTC One M8>fastboot flash flash philz_touch_6.48
.4-m8.img
sending 'flash' (14436 KB)...
OKAY [ 1.467s]
writing 'flash'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.293s
D:\All Android Devices\T Mobile HTC One M8>fastboot flash flash T_Mo_1.57.531.7_
recovery.img
sending 'flash' (24576 KB)...
OKAY [ 1.688s]
writing 'flash'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.753s
D:\All Android Devices\T Mobile HTC One M8>fastboot oem lock
...
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(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 (Too many links))
finished. total time: 1.132s
twill1987 said:
I am fixing a TMO Htc One M8 for a friend. He currently has TWRP recovery but nothing will wipe or flash. I have posted the get var information and the log below along with all the steps I've taken, please share any insight into the matter.
Here is the Get VAR Information. I have tried to fix this device by relocking the Bootloader, flashing stock RUU RUU_M8_TMOUS_1.57.531.7 , Flashing modified firmware.zip, flashing recovery.img, nothing. Then unlocking the bootloader, flashing Philz recovery.img, Twrp.img, still same error. Current TWRP recovery registers nothing but errors. No wiping data, cache, system, etc. No installing backup nandroid, no flashing new rom through external SD card or adb sideload. Literally the phone won't flash anything and the error is error 12, "Remote signature verifiey failed" What kinda insight do you have into this? Anyway to get back to stock?
Thanks!
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.16.21331931.LA24G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA446WM02874
(bootloader) imei: 352628060329457
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(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: 6e0f5a3d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.044s
LOG: D:\All Android Devices\T Mobile HTC One M8>fastboot flash flash TMOUS-M8-1.12.53
1.19.recovery.img
sending 'flash' (24576 KB)...
OKAY [ 1.691s]
writing 'flash'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.953s
D:\All Android Devices\T Mobile HTC One M8>fastboot flash flash philz_touch_6.48
.4-m8.img
sending 'flash' (14436 KB)...
OKAY [ 1.467s]
writing 'flash'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.293s
D:\All Android Devices\T Mobile HTC One M8>fastboot flash flash T_Mo_1.57.531.7_
recovery.img
sending 'flash' (24576 KB)...
OKAY [ 1.688s]
writing 'flash'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.753s
D:\All Android Devices\T Mobile HTC One M8>fastboot oem lock
...
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(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 (Too many links))
finished. total time: 1.132s
Click to expand...
Click to collapse
okay I'm wondering why the bootloader is 3.18. I just converted my T-Mobile HTC one m8 to dev edition and that's what my bootloader is now.
That device must have been s-off before if it has the 3.18 bootloader. the problem is now you're s-on with the wrong bootloader in the phone. So it's not gonna verify something it can't. U need to unlock the bootloader then try to s-off again. Let me know if u need more help
twinnfamous said:
okay I'm wondering why the bootloader is 3.18. I just converted my T-Mobile HTC one m8 to dev edition and that's what my bootloader is now.
That device must have been s-off before if it has the 3.18 bootloader. the problem is now you're s-on with the wrong bootloader in the phone. So it's not gonna verify something it can't. U need to unlock the bootloader then try to s-off again. Let me know if u need more help
Click to expand...
Click to collapse
Yes, I think the device was S-off before was well. But how can I get the device S-off when I can't load any rom to establish an internet connection?
There's no way to get back to stock, or get an internet connection through the device to obtain S-off. I can unlock the boot-loader,
I've done that a few times, but how to get S-Off when the only two screens I can access are the bootloader and twrp? When bootloader is unlocked. I have used firewater before for S-off and it requires active internet connection on device.
Thanks again for helping
twill1987 said:
Yes, I think the device was S-off before was well. But how can I get the device S-off when I can't load any rom to establish an internet connection?
There's no way to get back to stock, or get an internet connection through the device to obtain S-off. I can unlock the boot-loader,
I've done that a few times, but how to get S-Off when the only two screens I can access are the bootloader and twrp? When bootloader is unlocked. I have used firewater before for S-off and it requires active internet connection on device.
Thanks again for helping
Click to expand...
Click to collapse
Unlock bootloader try to flash the latest open twrp recovery and try to install another Rom or backup. If you can see the roms in the sdcard then you should be able to flash the roms or backup.
If there was a way to get into adb YOU would be able to s-off again.
twinnfamous said:
Unlock bootloader try to flash the latest open twrp recovery and try to install another Rom or backup. If you can see the roms in the sdcard then you should be able to flash the roms or backup.
If there was a way to get into adb YOU would be able to s-off again.
Click to expand...
Click to collapse
I've tried to flash TWRP but I get that error. I tried to flash the newest twrp but it wouldn't flash.
I think the system is no longer mounted, that's why I get this error :"E: Unable to mount 'data'" and "E: Unable to mount internal storage"
twill1987 said:
I've tried to flash TWRP but I get that error. I tried to flash the newest twrp but it wouldn't flash.
I think the system is no longer mounted, that's why I get this error :"E: Unable to mount 'data'" and "E: Unable to mount internal storage"
Click to expand...
Click to collapse
Is there any option in recovery to format? if so have u tried to format each partition manually?
Then try and see if it will flash. Just need something to boot so you can s-off .
You need to get s-off again so you can flash a ruu with lower hboot if formatting doesn't work or you can try to flash the new 4.4.3 ruu when it becomes available. They said the ota should be out on the 11th.
I'll keep looking for ways to s-off without adb .
Well first your doing the wrong command. Its fastboot flash recovery recovery.img, not fastboot flash flash recovery.img.
x714x said:
Well first your doing the wrong command. Its fastboot flash recovery recovery.img, not fastboot flash flash recovery.img.
Click to expand...
Click to collapse
Yes, that was a typo. Every fastboot flash ends with error 12. Remote Signature.
I have tried literally everything with this device. Tried flashing new TWRP, Radio, Firmware, Etc. Nothing works.
Inside TWRP everything finishes with "failed" or "E: Unable to mount cache"
I tried to select cache under the mount in TWRP and it's greyed out. I fastboot erase cache, and it is literally
the only thing that worked for me. But still no way to restore previous Android. Tried flashing stock RUU's for 4.4.2 and 4.4.3, no dice.
Both RUU's get to 6 percent and then say failed. I'm wondering if the device thinks it's a different phone possibly a GPE edition so it won't
go back to stock? Just a thought. I have unlocked, and relocked the bootloader a million times trying different methods as well, not
sure what else there is to do next. This might be the end of the road for this customers phone.
twinnfamous said:
Is there any option in recovery to format? if so have u tried to format each partition manually?
Then try and see if it will flash. Just need something to boot so you can s-off .
You need to get s-off again so you can flash a ruu with lower hboot if formatting doesn't work or you can try to flash the new 4.4.3 ruu when it becomes available. They said the ota should be out on the 11th.
I'll keep looking for ways to s-off without adb .
Click to expand...
Click to collapse
Yes, that was a typo. Every fastboot flash ends with error 12. Remote Signature.
I have tried literally everything with this device. Tried flashing new TWRP, Radio, Firmware, Etc. Nothing works.
Inside TWRP everything finishes with "failed" or "E: Unable to mount cache"
I tried to select cache under the mount in TWRP and it's greyed out. I fastboot erase cache, and it is literally
the only thing that worked for me. But still no way to restore previous Android. Tried flashing stock RUU's for 4.4.2 and 4.4.3, no dice.
Both RUU's get to 6 percent and then say failed. I'm wondering if the device thinks it's a different phone possibly a GPE edition so it won't
go back to stock? Just a thought. I have unlocked, and relocked the bootloader a million times trying different methods as well, not
sure what else there is to do next. This might be the end of the road for this customers phone.
twinnfamous said:
Is there any option in recovery to format? if so have u tried to format each partition manually?
Then try and see if it will flash. Just need something to boot so you can s-off .
You need to get s-off again so you can flash a ruu with lower hboot if formatting doesn't work or you can try to flash the new 4.4.3 ruu when it becomes available. They said the ota should be out on the 11th.
I'll keep looking for ways to s-off without adb .
Click to expand...
Click to collapse
Under TWRP the only option is to format data. I formatted, but it did nothing that I'm aware of.
twill1987 said:
Under TWRP the only option is to format data. I formatted, but it did nothing that I'm aware of.
Click to expand...
Click to collapse
I just tried to reformat data again and it says same error in TWRP E: Cannot mount cache
I am able to flash Viper Rom though, but because it is S ON the rom won't boot past start up screen.
What a bizarre issue
twill1987 said:
Under TWRP the only option is to format data. I formatted, but it did nothing that I'm aware of.
Click to expand...
Click to collapse
There should be a way now that the new T-Mobile update to flash ruu if we can find one.
Edit: found one
http://www.htcdev.com/devcenter/downloads/P00
Just select T-Mobile as carrier and USA as region then you Wil see the latest ruu to download.
twinnfamous said:
There should be a way now that the new T-Mobile update to flash ruu if we can find one.
Click to expand...
Click to collapse
I flashed the 4.4.3 RUU update at HTCDEV.com It failed at the 6 percent mark. http://www.htcdev.com/devcenter/downloads
twill1987 said:
I just tried to reformat data again and it says same error in TWRP E: Cannot mount cache
I am able to flash Viper Rom though, but because it is S ON the rom won't boot past start up screen.
What a bizarre issue
Click to expand...
Click to collapse
the latest viper is from New firmware base so it takes 15 to 20 minutes to boot. Have you waited that long?
---------- Post added at 10:27 PM ---------- Previous post was at 10:24 PM ----------
twill1987 said:
I flashed the 4.4.3 RUU update at HTCDEV.com It failed at the 6 percent mark. http://www.htcdev.com/devcenter/downloads
Click to expand...
Click to collapse
Sorry it seems I'm getting posts in different orders.
Flash viper and wait 15 to 20 minutes. And we can go from there.
I'm pretty sure we can get this resolved.
twinnfamous said:
the latest viper is from New firmware base so it takes 15 to 20 minutes to boot. Have you waited that long?
---------- Post added at 10:27 PM ---------- Previous post was at 10:24 PM ----------
Sorry it seems I'm getting posts in different orders.
Flash viper and wait 15 to 20 minutes. And we can go from there.
I'm pretty sure we can get this resolved.
Click to expand...
Click to collapse
I'll try to flash the latest Viper. The 1.6.0 it says everything flashed correctly, but gets stuck at the HTC boot screen.
I just flashed the 1.8.0 OTA update and everything installs but it sticks at the boot screen.
I see the 2.2.0 update is out so I'm downloading that now, I'll flash and see how it goes.
I'll update, thanks for your help!
Ruu requires the bootloader be locked
Sent from my HTC One_M8 using XDA Free mobile app
It's been a long and wild ride, but I think my device is toasted.. sorta.
I unlocked via HTCDev, installed TWRP, rooted. All went well.
Wanted to test GPE ROM. Downloaded and installed 4.4.3.
It had an OTA. Flashed stock recovery to apply it. BAD MOVE!
Ever since, my white hboot is now black, says version 3.18. This is the GPE hboot.
Trying to manually write a new one with dd fails obviously, read only.
RUU fails, saying error 159 (Wrong RUU for this device. It isnt?)
RUU flashing hboot, "unknown error 99" - assuming because S-On.
Firewater s-off FAILED before this happened, because my device just wasn't compatible with it.
Now running the GPE hboot I tried it again, and it just force closes and kicks me back to a terminal after typing in "Yes"
Only AOSP based ROMs are booting now.
TWRP (Multiple versions) as well as PhilZ CWM both fail on most other roms with "set_perm: some changes failed"
And then kick me to a 2-3 bootloop back into recovery.
What are my options? Thanks guys.
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.16.21331931.LA24G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SUREWHYNOT
(bootloader) imei: YESSIR
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(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: 6e0f5a3d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
xHighAlert said:
It's been a long and wild ride, but I think my device is toasted.. sorta.
I unlocked via HTCDev, installed TWRP, rooted. All went well.
Wanted to test GPE ROM. Downloaded and installed 4.4.3.
It had an OTA. Flashed stock recovery to apply it. BAD MOVE!
Ever since, my white hboot is now black, says version 3.18. This is the GPE hboot.
Trying to manually write a new one with dd fails obviously, read only.
RUU fails, saying error 159 (Wrong RUU for this device. It isnt?)
RUU flashing hboot, "unknown error 99" - assuming because S-On.
Firewater s-off FAILED before this happened, because my device just wasn't compatible with it.
Now running the GPE hboot I tried it again, and it just force closes and kicks me back to a terminal after typing in "Yes"
Only AOSP based ROMs are booting now.
TWRP (Multiple versions) as well as PhilZ CWM both fail on most other roms with "set_perm: some changes failed"
And then kick me to a 2-3 bootloop back into recovery.
What are my options? Thanks guys.
Click to expand...
Click to collapse
You cant ruu because your CID is wrong you should supercid by doing ...
"fastboot oem readcid". Make a note of your original CID.
Then do
"fastboot oem writecid 11111111"
Not including parenthesis. Then try the ruu
iRunLinux said:
You cant ruu because your CID is wrong you should supercid by doing ...
"fastboot oem readcid". Make a note of your original CID.
Then do
"fastboot oem writecid 11111111"
Not including parenthesis. Then try the ruu
Click to expand...
Click to collapse
Reminder that I am S-On. All S-Off methods fail for me.
While in RebootRUU:
Code:
C:\Users\Cody\Desktop\ADB Fastboot>fastboot oem readcid
...
(bootloader) cid: T-MOB010
OKAY [ 0.001s]
finished. total time: 0.001s
C:\Users\Cody\Desktop\ADB Fastboot>fastboot oem writecid 11111111
...
(bootloader) SecuritySDInit: counter = 1
(bootloader) m8_init_sd, SD card already power on
(bootloader) [SPEW] GPIO 0 status is 1
(bootloader) [SD_ERR] No sd card inserted!
(bootloader) usb_hw_init
FAILED (status read failed (Too many links))
finished. total time: 0.053s
While in regular fastboot:
Code:
C:\Users\Cody\Desktop\ADB Fastboot>fastboot oem writecid 11111111
...
(bootloader) [JAVACARD_ERR] SD/USBDISK Init error
OKAY [ 0.002s]
finished. total time: 0.002s
xHighAlert said:
Reminder that I am S-On. All S-Off methods fail for me.
While in RebootRUU:
Code:
C:\Users\Cody\Desktop\ADB Fastboot>fastboot oem readcid
...
(bootloader) cid: T-MOB010
OKAY [ 0.001s]
finished. total time: 0.001s
C:\Users\Cody\Desktop\ADB Fastboot>fastboot oem writecid 11111111
...
(bootloader) SecuritySDInit: counter = 1
(bootloader) m8_init_sd, SD card already power on
(bootloader) [SPEW] GPIO 0 status is 1
(bootloader) [SD_ERR] No sd card inserted!
(bootloader) usb_hw_init
FAILED (status read failed (Too many links))
finished. total time: 0.053s
While in regular fastboot:
Code:
C:\Users\Cody\Desktop\ADB Fastboot>fastboot oem writecid 11111111
...
(bootloader) [JAVACARD_ERR] SD/USBDISK Init error
OKAY [ 0.002s]
finished. total time: 0.002s
Click to expand...
Click to collapse
Personally i would try to s-off u said firewater doesnt work but id just try sunshine s-off it costs money but its worth it.
iRunLinux said:
Personally i would try to s-off u said firewater doesnt work but id just try sunshine s-off it costs money but its worth it.
Click to expand...
Click to collapse
Sunshine wants you to get as close to stock as possible.
I'm running the wrong hboot, and can only boot AOSP roms.
But okay I'll give it a spin.
xHighAlert said:
Sunshine wants you to get as close to stock as possible.
I'm running the wrong hboot, and can only boot AOSP roms.
But okay I'll give it a spin.
Click to expand...
Click to collapse
Use the same method in which u flashed the black hboot to flash the stock hboot
---------- Post added at 03:47 AM ---------- Previous post was at 03:42 AM ----------
xHighAlert said:
Sunshine wants you to get as close to stock as possible.
I'm running the wrong hboot, and can only boot AOSP roms.
But okay I'll give it a spin.
Click to expand...
Click to collapse
And if not try flashing gpe stock rooted rom which should boot since your still using that firmware, then try and s-off with sunshine.
I'm in pretty much the same circumstance. Tried going GPE - installed GPE ROM, flashed GPE Recovery to get the 4.4.4 update and now neither GPE nor Sense Roms will install or boot. I had S-Off before, but I think the GPE Recovery put security back on and now I'm back to S-On.
I've tried GPE, Stock Sense, and custom Recoveries and Firmware - nothing is working... I'm stuck running CM11 at the moment.
If only there was an S-Off method that would actually work under CM.
help me to find a solution on my htc one x at&t
when i try to change cid from 12345678 that i 'v allready change it befor just to try now i can't change it to super cid or original cid
on my CMD
i rooted my phone and i have S-on
ofurtunatly lost system
C:\Users\houssam\Desktop\htc>fastboot oem writecid CWS__001
...
(bootloader) elite_init_sd, SD card already power on
(bootloader) sdhw_7xxx_open: id=0
(bootloader) [SD_HW_ERR] SD: No device attached
(bootloader) 902910 902E20
FAILED (status read failed (No such file or directory))
finished. total time: 1.266s
I got to this point after following a guide here to install magisk and MK100 Nash. I lost baseband, probably because I naively flashed XT1789-05 firmware from the guide, to an 04. Idk, anyway, I hadn't read as much at that point and thought I needed to lock the bootloader again *duh duh.* So I'm reading a lot about how this might be impossible to recover from and it's starting to look like it. I've downloaded 10s of GB of firmware to multiple computers, and I for sure can say that the bootloader is rejecting any flashing of firmware from OCX27.109-51 or OCX27.109-36 that I've tried anyway. There may be yet more stock firmwares to try, but I think I'm missing the point with all that because shouldn't any stock firmware be accepted by the bootloader? Anyway, if I could get people to muster up whatever they can on getting out of this trap I laid myself, I would really appreciate it. I was very foolish to attempt this when my food stamps and college application depend on me having a phone number. Plus this phone was sweet I feel like I betrayed it.
I've been trying to fuss with Qualcomm recovery but either EDL is broken too, since some commands I've tried to get it into EDL just resulted in it going to the ol' "can't be trusted," screen but that might be just that it's not going into EDL anyway. Thinking about getting a deepflash cable or something. I lack the patience and dexterity to rig it myself right now. But I don'y want to get my hopes up if it's screwed.
One fun quirk is that if I fastboot boot boot.img it actually does boot to a broken OS where "pixel setup" infinitely crashes but I can get it to let me use a black desktop with limited settings, like I can use the flashlight haha. No adb or ability to change developer settings though. In case it wasn't clear, I can't use TWRP, factory reset, or anything but fastboot essentially.
I'm wondering if someone knows a shell script I could possibly load into fastboot to enable OEM unlock again? AS in, commands to change the OEM unlock to "enable" in dev ops?
I noticed fastboot has a shell option '-c' which I was hoping to leverage with one of those broken boot.imgs maybe change the settings that way?
Btw I also have tried using the LMSA tool and it's a piece of crap, it never seemed like it would work on my other computer, but it had a weird connection. I installed windows on this one and it seemed to work, possibly a USB 2.0 thing, but as soon as LMSA seemed to actually be maybe doing something, I lost the ability to sign in. It just hangs forever and says it was successful then asks again (or it doesn't). I added a new windows user, tried reinstalling like 40 times, it behaved erratically but ultimately the problem persisted and now it remembers my login info between uninstalls and across new users but can't actually log in.
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_tmo-641a15b-180420
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA_UMTS
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: ZY224TL8V5
(bootloader) cid: 0x0015
(bootloader) channelid: 0x85
(bootloader) uid: 3F57D9A7
(bootloader) securestate: flashing_locked
(bootloader) verity-state: logging (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:<Not zero>
(bootloader) meid:
(bootloader) date: 03-25-2018
(bootloader) sku: XT1789-04
(bootloader) carrier_sku: XT1789-04
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 3748
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash_tmo_c/nash:8.0.0/OCX
(bootloader) ro.build.fingerprint[1]: S27.109-51-7/9:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.241.9.nash_tmo_c.
(bootloader) ro.build.version.full[1]: tmo.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-04300-8x98.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g668a0f8 (huds
bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 20150
(bootloader) kernel.version[2]: 123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Thu Jan 10 22:25:12 CST 2019
(bootloader) git:abl: MBM-3.0-nash_tmo-641a15b-180420
(bootloader) git:xbl: MBM-3.0-nash_tmo-9869834-180420
(bootloader) gitmic: MBM-3.0-nash_tmo-9869834-180420
(bootloader) git:rpm: MBM-3.0-nash_tmo-b13e14f-180420
(bootloader) git:tz: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:hyp: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:devcfg: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:cmnlib: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:cmnlib64: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:keymaster: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:storsec: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) gitrov: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) qe: "qe 1/1"
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: tmo
(bootloader) current-slot: _a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 2
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 0
What -05 firmware did you flash?
41rw4lk said:
What -05 firmware did you flash?
Click to expand...
Click to collapse
I don't even know anymore, it was on a computer that I had to wipe and install windows over in order to try everything I did. The clue in my other computer, which is probably accurate, is NASH_TMO_C_OCXS7.109-51-14-7_subsidy-TMO_RSU_regulatory-default_DEFAULT. I'd be willing to bet that is the firmware that is currently flashed, before it was modified with Magisk v20.4, MindTheGapps-8.1.0-arm-20180808_153837, and either MK100 or MK81 of Mokee. I'm no longer even sure if this firmware is for 05, that's just what the name of some other archive this all got dumped into. It's also the version that the instructions I was following used, before I even knew there were 6 versions.
NASH_TMO_C_OCXS7.109-51-14-7_subsidy-TMO_RSU_regulatory-default_DEFAULT is the last firmware available for TMO, hopefully whatever firmware you've flashed wasn't a pie firmware.
With a locked bootloader you can only flash official signed same version or newer firmware. I would try to flash that again, your goal is to get a booting system that you can enable oem unlocking in. That will give you more flexibility to solve other issues if needed. However if you've flashed a oie firmware you might be out of luck.
41rw4lk said:
NASH_TMO_C_OCXS7.109-51-14-7_subsidy-TMO_RSU_regulatory-default_DEFAULT is the last firmware available for TMO, hopefully whatever firmware you've flashed wasn't a pie firmware.
With a locked bootloader you can only flash official signed same version or newer firmware. I would try to flash that again, your goal is to get a booting system that you can enable oem unlocking in. That will give you more flexibility to solve other issues if needed. However if you've flashed a oie firmware you might be out of luck.
Click to expand...
Click to collapse
Well, I looked up that exact filename and attempted to flash the firmware from it. Am I somehow doing this wrong? (see attached -- fastboot version eac51f2bb6a8-android )
https://postimg dot cc/BPq1sbmS
This matches the firmware from the folder I found everything else in, like magisk and some utilities from the first night of this, so it should be the one that's on there. I don't think I flashed pie firmware, unless I installed a ROM that was Pie I think that I only flashed Oreo stuff. (Were they just unable to think of a desert that starts with Q?)
I'm noticing my build fingerprint and blur version correspond with the firmware OCSX.109-51-7/9, which also tells me this should have worked (that firmware also doesn't work). I lost baseband before this happened though ( that's why I locked it, because I thought that would fix it smh), I don't know what does that besides flashing the wrong firmware or really screwing something else.
urvurm said:
Well, I looked up that exact filename and attempted to flash the firmware from it. Am I somehow doing this wrong? (see attached -- fastboot version eac51f2bb6a8-android )
https://postimg dot cc/BPq1sbmS
This matches the firmware from the folder I found everything else in, like magisk and some utilities from the first night of this, so it should be the one that's on there. I don't think I flashed pie firmware, unless I installed a ROM that was Pie I think that I only flashed Oreo stuff. (Were they just unable to think of a desert that starts with Q?)
I'm noticing my build fingerprint and blur version correspond with the firmware OCSX.109-51-7/9, which also tells me this should have worked (that firmware also doesn't work). I lost baseband before this happened though ( that's why I locked it, because I thought that would fix it smh), I don't know what does that besides flashing the wrong firmware or really screwing something else.
Click to expand...
Click to collapse
I've attached the latest adb/fastboot files and a flashall.bat for TMO. Delete any .bat files in your firmware folder and then extract the attached zip into the same firmware folder. Then try running the flashall and keep track of what flashes and what doesn't. Again the goal is to get a booting system that you can enable oem unlocking on so that you can unlock your bootloader again.
41rw4lk said:
I've attached the latest adb/fastboot files and a flashall.bat for TMO. Delete any .bat files in your firmware folder and then extract the attached zip into the same firmware folder. Then try running the flashall and keep track of what flashes and what doesn't. Again the goal is to get a booting system that you can enable oem unlocking on so that you can unlock your bootloader again.
Click to expand...
Click to collapse
Under way, will update with output from fastboot. Thank you for helping me.
Update, it's acting differently, preliminary results show that it is automatically appending slot names with extra "_". I'm going to edit the bat file and add "--slot all" to the relevant partitions. I am getting flash permission denied for the bootloader though. I want to let it run all the way through with the slot option. Nvm I don't know what "relevant is" Here's the output from the unedited bat so far:
I'm having serious issues with copying from the command line, idk if you've got tricks for that.
Code:
C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot oem fb_mode_set
OKAY [ 0.016s] Finished. Total time: 0.016s C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot getvar max-sparse-size
max-sparse-size: 268435456 Finished. Total time: 0.000s C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot flash gpt gpt.bin
(bootloader) is-logical:gpt: not found
Sending 'gpt' (206 KB) OKAY [ 0.000s]
Writing 'gpt'
(bootloader) Validating 'gpt.default.xml' (bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) - flashing 'gpt_main1.bin' to 'partition:1'
(bootloader) - flashing 'gpt_main2.bin' to 'partition:2'
(bootloader) - flashing 'gpt_main3.bin' to 'partition:3'
(bootloader) - flashing 'gpt_main4.bin' to 'partition:4'
(bootloader) - flashing 'gpt_main5.bin' to 'partition:5' OKAY [ 0.132s] Finished. Total time: 0.138s C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot flash bootloader bootloader.img
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (9884 KB) OKAY [ 0.316s]
Writing 'bootloader'
(bootloader) Validating 'bootloader.default.xml'
(bootloader) flash permission denied (bootloader) flash permission denied (bootloader) flash permission denied (bootloader) flash permission denied (bootloader) flash permission denied (bootloader) flash permission denied (bootloader) flash permission denied (bootloader) flash permission denied (bootloader) flash permission denied (bootloader) flash permission denied (bootloader) flash permission denied (bootloader) flash permission denied (bootloader) Cancelling 'bootloader.default.xml' FAILED (remote: '') fastboot: error: Command failed C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot flash modem NON-HLOS.bin --slot_all
fastboot: unknown option -- slot_all C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot flash modem NON-HLOS.bin
(bootloader) is-logical:modem__a: not found
Sending 'modem__a' (97459 KB) OKAY [ 2.949s]
Writing 'modem__a'
(bootloader) Invalid partition name modem__a FAILED (remote: '')
fastboot: error: Command failed
Sending 'fsg__a' (5596 KB)
OKAY [ 0.185s]
Writing 'fsg__a'
(bootloader) Invalid partition name fsg__a FAILED (remote: '')
fastboot: error: Command failed C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot erase modemst1
Erasing 'modemst1' (bootloader) Permission denied
FAILED (remote: '') fastboot: error: Command failed C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot erase modemst2
Erasing 'modemst2' (bootloader) Permission denied
FAILED (remote: '') fastboot: error: Command failed C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot flash bluetooth BTFM.bin
(bootloader) is-logical:bluetooth__a: not found
Sending 'bluetooth__a' (4500 KB) OKAY [ 0.122s] Writing 'bluetooth__a' (bootloader) Invalid partition name bluetooth__a FAILED (remote: '')
fastboot: error: Command failed C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot flash dsp adspso.bin
(bootloader) is-logical:dsp__a: not found
Sending 'dsp__a' (16384 KB) OKAY [ 0.488s]
Writing 'dsp__a' (bootloader) Invalid partition name dsp__a
FAILED (remote: '')
fastboot: error: Command failed C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot flash logo logo.bin
(bootloader) is-logical:logo__a: not found
Sending 'logo__a' (3151 KB)
OKAY [ 0.100s]
Writing 'logo__a'
(bootloader) Invalid partition name logo__a
FAILED (remote: '')
fastboot: error: Command failed C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot flash boot boot.img
(bootloader) is-logical:boot__a: not found
Sending 'boot__a' (23361 KB)
OKAY [ 0.717s]
Writing 'boot__a'
(bootloader) Invalid partition name boot__a
FAILED (remote: '')
fastboot: error: Command failed C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot flash system system.img_sparsechunk.0
(bootloader) is-logical:system__a: not found
Sending 'system__a' (516201 KB)
OKAY [ 16.302s]
Writing 'system__a'
(bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot flash system system.img_sparsechunk.1
(bootloader) is-logical:system__a: not found
Sending 'system__a' (495129 KB) OKAY [ 15.174s]
Writing 'system__a'
(bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot flash system system.img_sparsechunk.2
(bootloader) is-logical:system__a: not found
Sending 'system__a' (519381 KB) OKAY [ 16.144s]
Writing 'system__a'
(bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot flash system system.img_sparsechunk.3
(bootloader) is-logical:system__a: not found
Sending 'system__a' (523787 KB) OKAY [ 16.147s]
Writing 'system__a'
(bootloader) Invalid partition name system__a FAILED (remote: '')
fastboot: error: Command failed C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot flash system system.img_sparsechunk.4
(bootloader) is-logical:system__a: not found
Sending 'system__a' (516413 KB) OKAY [ 16.205s]
Writing 'system__a'
(bootloader) Invalid partition name system__a FAILED (remote: '')
fastboot: error: Command failed C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot flash system system.img_sparsechunk.5
(bootloader) is-logical:system__a: not found
Sending 'system__a' (420583 KB) OKAY [ 12.854s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot flash system_b system_b.img_sparsechunk.0
(bootloader) is-logical:system_b: not found
Sending 'system_b' (515183 KB) OKAY [ 15.725s]
Writing 'system_b' (bootloader) flash permission denied
FAILED (remote: '')
fastboot: error: Command failed C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot flash system_b system_b.img_sparsechunk.1
(bootloader) is-logical:system_b: not found
Sending 'system_b' (307220 KB) OKAY [ 9.363s]
Writing 'system_b' (bootloader) flash permission denied
FAILED (remote: '')
fastboot: error: Command failed C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot flash oem oem.img
(bootloader) is-logical:oem__a: not found
Try copying the the commands in the flashall one at a time and adjust accordingly.
For example say you post the command fastboot flash logo logo.bin and it returns fastboot: error: Command failed logo__a: not found
You know it's trying to flash the _a slot, which is fine so tell it to do so manually fastboot flash logo_a logo.bin
With a locked bootloader you might get some permissions denied, especially since you flashed the -05 firmware, which might have mismatched a few things. Keep going to the end of your flashall. You need a bootable os so you can get the bootloader unlocked and hopefully overwrite more wrongs and get back to good.
41rw4lk said:
Try copying the the commands in the flashall one at a time and adjust accordingly.
For example say you post the command fastboot flash logo logo.bin and it returns fastboot: error: Command failed logo__a: not found
You know it's trying to flash the _a slot, which is fine so tell it to do so manually fastboot flash logo_a logo.bin
With a locked bootloader you might get some permissions denied, especially since you flashed the -05 firmware, which might have mismatched a few things. Keep going to the end of your flashall. You need a bootable os so you can get the bootloader unlocked and hopefully overwrite more wrongs and get back to good.
Click to expand...
Click to collapse
Well, permission was denied for all slots except for gpt.bin (consistently the only one to work), which I attempted to analyze to better understand the partion table but I think the tool I used was not designed for moto z. Anyway, this is just how it's been. From here, all boot options stop me at the "your software is corrupt you evil hacker anathema to corporate purity"
While I haven't tried it after this round of 100% failed commands, I have used fastboot boot boot.img and been able to enter a dysfunctional wreck of an OS that can almost but not quite get past pixel setup and allow me to edit prefs. Is there maybe a way to bypass setup and edit settings from here? ( It's too broken to launch adb, but it does persist to some degree, I was able to set a pin that remains. It's just infinitely crashing and never makes it past the checkpoint where I disagree to all of tmobiles usage stats agreements,
urvurm said:
Well, permission was denied for all slots except for gpt.bin (consistently the only one to work), which I attempted to analyze to better understand the partion table but I think the tool I used was not designed for moto z. Anyway, this is just how it's been. From here, all boot options stop me at the "your software is corrupt you evil hacker anathema to corporate purity"
Click to expand...
Click to collapse
I assume you mean the lenovo rescue and smart assistant tool. With a mismatch system it might not recognize the phone (which is moto z 2nd gen for the record).
I'll attach a both slot flashall, maybe the other slot can be sorted a little better. For what it is worth, you might boot to recovery and do a factory reset 1st. Then try the other flashall. You might just be out of luck, but it's worth trying a few things before you call it. Same deal with this flashall too, if you need to manually go line by line do it. Also, when it's all said and done, try another factory reset from recovery if needed.
If you see the no command dead android in recovery, just hold pwr and press vol up to get to the actual recovery.
I just seen your edit, no way to get past setup that I know of. Another user tried forever to find away, but I don't think they did. Also, I wouldn't set any screen security until you're in a clean state. It will only hinder what you're trying to do.
41rw4lk said:
I assume you mean the lenovo rescue and smart assistant tool. With a mismatch system it might not recognize the phone (which is moto z 2nd gen for the record)
Click to expand...
Click to collapse
I was actually referring to this: https://androidforums.com/threads/guide-how-to-create-partition-xml-gpt.1125433/
To see if I could get a better Idea of the partition names, since even when I set --slot all, I get the (permission denied) instead of (command fail) or whatever.
And you're right, LMSA wasn't able to do recognize it and I think it's because of mismatched firmware. I'm glad someone else has seen this broken boot ing. thing before. I know setting a pin was a bad idea, I just felt like I was running out of options.
I'll try this modified flashall you sent me.
41rw4lk said:
For what it is worth, you might boot to recovery and do a factory reset 1st. Then try the other flashall. You might just be out of luck, but it's worth trying a few things before you call it. Same deal with this flashall too, if you need to manually go line by line do it. Also, when it's all said and done, try another factory reset from recovery if needed.
Click to expand...
Click to collapse
No dice.. failed uniformly as flash permission denied or permission denied for the erase commands. Tried line by line and got the same result. Only noteworthy things I saw anyway:
Code:
#after any flash attempt, with both invalid and valid partition names, I get this:
(bootloader) is-logical:<Insert whatever partition name I just attempted _a, _b either way>: not found
#it always says flash permission denied, unless I try an invalid partion name, like radio
(bootloader) is-logical:radio: not found Sending 'radio' (97459 KB) OKAY [ 3.039s] Writing 'radio' (bootloader) Invalid partition name radio FAILED (remote: '') fastboot: error: Command failed
C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot --set-active=other
Setting current slot to '`' FAILED (remote: '')
If you see the no command dead android in recovery, just hold pwr and press vol up to get to the actual recovery.
Click to expand...
Click to collapse
I tried booting to recovery from bootloader, holding power+ vol up, and also just booting with power +vol up. I always get to the "corrupted, can't trust" screen. I think it's trying to boot into TWRP but isn't allowed. It's weird though because I remember trying this before and it just restarting the bootloader, but it might have been a dead battery.