Bootloader only - help - One (M8) Q&A, Help & Troubleshooting

My M8 was once upon a time a Rogers M8.
Quite some time ago i converted it to a GPE with 5.1.
It was rooted and is S-Off.
Last night I pushed the MM RUU from GraphixNYC. It worked and I was happy.
Except I like to teak the DPI so I root it.
This morning I installed TWRP2.8.7.0 recovery and allowed TWRP to SuperSu it.
Now when it boots I don't get past the loading screen.
I can put it in Fastboot, connect to it from my Mac, and to push the LP/MM RUUs.
Both fail in the same way (below). What can I do?
------ 5.1 ----
~/Documents/Android/platform_tools/Mac => ./fastboot devices
SH45LWM0nnnnn fastboot
~/Documents/Android/platform_tools/Mac => ./fastboot flash zip RUU51.zip
target reported max download size of 1826414592 bytes
sending 'zip' (649759 KB)...
OKAY [ 23.080s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 23.085s
~/Documents/Android/platform_tools/Mac =>
----- 6.0 ---
~/Documents/Android/platform_tools/Mac => ./fastboot flash zip RUU60.zip
target reported max download size of 1826414592 bytes
sending 'zip' (633780 KB)...
OKAY [ 22.373s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 22.378s
~/Documents/Android/platform_tools/Mac =>
----

I got this working.
I took the v6 RUU, put it on my external SD, renamed it as 0p6bimg and booted into HBOOT.
I guess I did this: http://forum.xda-developers.com/showthread.php?t=2708589

A second time, carefully following the directions I have MM + systemless root.
http://forum.xda-developers.com/htc-one-m8/general/root-root-marshmallow-gpe-supersu-t3242210

Related

[SOLVED] Can't flash stock recovery 4.20.531.4

I downloaded the stock recovery for 5.0.1 from here http://forum.xda-developers.com/showpost.php?p=51836232&postcount=1
When I go into fastboot and try to flash I get an error:
$ fastboot flash recovery Tmo-M8-4.20.531.4-recovery.img
target reported max download size of 1826152448 bytes
sending 'recovery' (16046 KB)...
OKAY [ 1.753s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
This is with bootloader unlocked, if I try with bootloader locked I get:
$ fastboot flash recovery Tmo-M8-4.20.531.4-recovery.img
target reported max download size of 1826152448 bytes
sending 'recovery' (16046 KB)...
OKAY [ 1.757s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.763s
I notice theres a 1mb difference between twrp-2.8.7.0-m8.img (17.4mb) and Tmo-M8-4.20.531.4-recovery.img (16.4mb)
How am I supposed to get the stock recovery back without erasing anything else?
Device is S-OFF
Wow, turned out to be a bad download :| Redownloaded and it flashed fine
CHECK MD5 SUMS BEFORE FLASHING
Some screwed up stuff could have happened, thankfully even S-OFF does have some precautions.
MOD EDIT

Ascend Mate soft brick (I think)

Dear all, I would reset my Mate and did a factory reset from Android Menu. After that the phone was going to the TWRP Recovery. So I didn't read further tutorials and thought a full wipe would not a bad Idea. But sadly I did not found the old Custom Image ZIP file and would install the factory default firmware. UPDATE.APP. After some doings I lost my TWRP Image (I think by swiping) and now I have only the HUAWEI SDCARD&USB UPDATE AGENT VERSION 2.0 running.
When I try now to update of UPDATE.APP from SDCARD, the error is, the Agent can not mount. I was trying two SD Cards. fresh formatted.
Are all sizes compatible? Or do I have to use a small SD card?
Hi all, I found this instruction: http://forum.xda-developers.com/showthread.php?t=2682979
I tried, but failed...
..........\Downloads\Ascend_Mate_firmware\adb>fastboot flash BOOT BOOT.img
< waiting for device >
target reported max download size of 838860800 bytes
sending 'BOOT' (5308 KB)...
OKAY [ 0.228s]
writing 'BOOT'...
FAILED (remote: partition does not exist)
finished. total time: 0.232s
..........\Downloads\Ascend_Mate_firmware\adb>fastboot flash RECOVERY RECOVERY.img
target reported max download size of 838860800 bytes
sending 'RECOVERY' (7942 KB)...
OKAY [ 0.340s]
writing 'RECOVERY'...
FAILED (remote: partition does not exist)
finished. total time: 0.343s
..........\Downloads\Ascend_Mate_firmware\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.002s

working "RECOVERY"

Just got my phone trying to flash the custom recovery to no joy (bootloader unlocked)
Keep getting
C:\Users\graem\Desktop\1p3>fastboot flash recovery recovery.img
< waiting for device >
target reported max download size of 536870912 bytes
sending 'recovery' (17776 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 0.022s
C:\Users\graem\Desktop\1p3>fastboot flash recovery recovery.img
sending 'recovery' (17776 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.013s
C:\Users\graem\Desktop\1p3>
Any thoughts guys
This was using the [email protected]_radaideh-v2.1
How i got it working was installing stock recovery from tool then install custom and all worked fine.

TWRP problem

Hi,
what i did so far was:
unlocked the bootloader
download the twrp recovery img (...ruu.lalleman.net/HTC_M8S%28QL_UL%29/Recovery/twrp-recovery-2.8.7.0-m8s-qlul/)
set phone on Fastboot USB
over the cmd bar (windows 10) i used fastboot and got this result:
C:\Android>fastboot flash recovery twrp-2.8.7.0-m8s-qlul.img
target reported max download size of 16510976 bytes
Invalid sparse file format at header magi
sending sparse 'recovery' 1/2 (15368 KB)...
OKAY [ 1.899s]
writing 'recovery' 1/2...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.907s
I have no idea what i did wrong or how i can solve the problem. I just wanted run the twrp, use the Superuser. zip to have the rootet htc one m8s.
Thajin said:
Hi,
what i did so far was:
unlocked the bootloader
download the twrp recovery img (...ruu.lalleman.net/HTC_M8S%28QL_UL%29/Recovery/twrp-recovery-2.8.7.0-m8s-qlul/)
set phone on Fastboot USB
over the cmd bar (windows 10) i used fastboot and got this result:
C:\Android>fastboot flash recovery twrp-2.8.7.0-m8s-qlul.img
target reported max download size of 16510976 bytes
Invalid sparse file format at header magi
sending sparse 'recovery' 1/2 (15368 KB)...
OKAY [ 1.899s]
writing 'recovery' 1/2...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.907s
I have no idea what i did wrong or how i can solve the problem. I just wanted run the twrp, use the Superuser. zip to have the rootet htc one m8s.
Click to expand...
Click to collapse
Use HTC_fastboot and not the generic fastboot..
nopynel said:
Use HTC_fastboot and not the generic fastboot..
Click to expand...
Click to collapse
I have the same problem and just ask now because i am really confused about the hole stuff here.. Have we now to tipp in cmd
C:\Android>HTC_fastboot flash recovery twrp-2.8.7.0-m8s-qlul.img ??
Edit: Ok, i find HTC_Fastboot there > ruu.lalleman.net/HTC_M8S%28QL_UL%29/Tools/Fastboot/ and it solve this problem.
But i think its still not everything fine.. if i change to hboot on bootlader i get this infomations
fs5.directupload.net/images/160727/z9lr634u.jpg
whether unlock bootloader?

Stuck on TWRP after accidental factory reset

I was about to manually install the lineageOS update, but I accidentally swiped factory restore. Is there anyway I can get the update file online? I tried starting from the top by wiping everything and reinstalling the rom but it only boots me into TWRP. I also tried restoring backup files but is also boots me into TWRP. I am stuck.
PS: I tried the "fastboot continue" method but it boots me into TWRP.
reboot to fastboot mode. flash stock bootloader and recovery. reboot in stock recovery and then factory reset device and sideload firmware. alternatively you can flash raw firmware manually
sukhwant717 said:
reboot to fastboot mode. flash stock bootloader and recovery. reboot in stock recovery and then factory reset device and sideload firmware. alternatively you can flash raw firmware manually
Click to expand...
Click to collapse
Thank you for your response, Sir. I really appreciate it. Where do I get the stock bootloader and recovery, and how do I flash them? On the alternative method, do you mean I should install the stock rom? I'm sorry. I'm really not good at this; I'm just good at following tutorials. Is this what you're suggesting me to do? (XDA is now allowing me to write outside links. But here is the title of the tutorial from Asus Zentalk)
"[Experience Sharing] How to Relock Bootloader on ZenFone 2(ZE551ML ONLY)"
I have made a backup before I intalled the Lineage OS custom Rom. Can I use that instead of downloading new files, because the internet here is really bad. My problem is how I am going to install it. I tried restoring it but I keep on coming back to the TWRP.
Edit: I am now downloading the stock boot.img and recovery.img. I will be flashing them with ADB the ADB tool. Is this what you want to tell me? Then I will reboot in stock recovery, select factory reset and sideload firmware. I honestly don't get the "sideload firmware" part but can I use the one that I have backed up? How?
lemuelermita said:
Thank you for your response, Sir. I really appreciate it. Where do I get the stock bootloader and recovery, and how do I flash them? On the alternative method, do you mean I should install the stock rom? I'm sorry. I'm really not good at this; I'm just good at following tutorials. Is this what you're suggesting me to do? (XDA is now allowing me to write outside links. But here is the title of the tutorial from Asus Zentalk)
"[Experience Sharing] How to Relock Bootloader on ZenFone 2(ZE551ML ONLY)"
I have made a backup before I intalled the Lineage OS custom Rom. Can I use that instead of downloading new files, because the internet here is really bad. My problem is how I am going to install it. I tried restoring it but I keep on coming back to the TWRP.
Edit: I am now downloading the stock boot.img and recovery.img. I will be flashing them with ADB the ADB tool. Is this what you want to tell me? Then I will reboot in stock recovery, select factory reset and sideload firmware. I honestly don't get the "sideload firmware" part but can I use the one that I have backed up? How?
Click to expand...
Click to collapse
the backup you made you can flash only via twrp. if you have backup simply install it in twrp. but if still bootloops then you have to download firmware either from asus website or raw firmware from any other source. first try to flash backup in twrp. if you are unable to get into system them report back here. i will send you link to download raw firmware and instructions how to flash
sukhwant717 said:
the backup you made you can flash only via twrp. if you have backup simply install it in twrp. but if still bootloops then you have to download firmware either from asus website or raw firmware from any other source. first try to flash backup in twrp. if you are unable to get into system them report back here. i will send you link to download raw firmware and instructions how to flash
Click to expand...
Click to collapse
I tried to flash the backup but still no luck. Yes, please. Thank you very much!
I'm currently downloading the "CleanSTOCK-MM.223-v3.8[STABLE][Z00A]-6 May". I hope this will fix the problem. Do you think this will work 100%? I am afraid that it will boot again to TWRP after installing another rom. Which do you think is more efficient, installing a new rom or installing raw firmware?
lemuelermita said:
I tried to flash the backup but still no luck. Yes, please. Thank you very much!
I'm currently downloading the "CleanSTOCK-MM.223-v3.8[STABLE][Z00A]-6 May". I hope this will fix the problem. Do you think this will work 100%? I am afraid that it will boot again to TWRP after installing another rom. Which do you think is more efficient, installing a new rom or installing raw firmware?
Click to expand...
Click to collapse
raw is definitely best option. are you able to mount data and cache partition in TWRP
sukhwant717 said:
raw is definitely best option. are you able to mount data and cache partition in TWRP
Click to expand...
Click to collapse
I haven't tried that yet. How do I do that? Can you send me the links and instructions needed?
sukhwant717 said:
raw is definitely best option. are you able to mount data and cache partition in TWRP
Click to expand...
Click to collapse
Defensively smartest guy about phones in the world!!! ahaha <3
lemuelermita said:
I haven't tried that yet. How do I do that? Can you send me the links and instructions needed?
Click to expand...
Click to collapse
go to the following guide. see the section flash firmware without AFT and follow the instructions. keep in mind run each and every command even if any of them fails.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
sukhwant717 said:
go to the following guide. see the section flash firmware without AFT and follow the instructions. keep in mind run each and every command even if any of them fails.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Click to expand...
Click to collapse
Thank you very much, Sir! I will give you an update soon.
lemuelermita said:
Thank you very much, Sir! I will give you an update soon.
Click to expand...
Click to collapse
Followed the instructions on the link but my phone boots up on a blinking screen with an android saying "Error". The command prompt failed at steps 4,5, and 11.
C:\Users\Lemuel\Documents\RESTOCK>fastboot devices
F5AZFG14A156 fastboot
C:\Users\Lemuel\Documents\RESTOCK>fastboot oem erase_osip_header
...
OKAY [ 0.217s]
finished. total time: 0.219s
C:\Users\Lemuel\Documents\RESTOCK>fastboot oem start_partitioning
...
(bootloader) Start partitioning
OKAY [ 0.228s]
finished. total time: 0.231s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash /tmp/partition.tbl partition.tbl
target reported max download size of 536870912 bytes
sending '/tmp/partition.tbl' (2 KB)...
OKAY [ 0.194s]
writing '/tmp/partition.tbl'...
FAILED (remote: not allowed to flash this partition)
finished. total time: 0.384s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash /tmp/partition.tbl partition.tbl
target reported max download size of 536870912 bytes
sending '/tmp/partition.tbl' (2 KB)...
OKAY [ 0.205s]
writing '/tmp/partition.tbl'...
FAILED (remote: not allowed to flash this partition)
finished. total time: 0.394s
C:\Users\Lemuel\Documents\RESTOCK>fastboot oem partition /tmp/partition.tbl
...
FAILED (remote: unknown OEM command)
finished. total time: 0.127s
C:\Users\Lemuel\Documents\RESTOCK>fastboot erase system
******** Did you mean to fastboot format this ext4 partition?
erasing 'system'...
OKAY [ 0.560s]
finished. total time: 0.561s
C:\Users\Lemuel\Documents\RESTOCK>fastboot erase cache
******** Did you mean to fastboot format this ext4 partition?
erasing 'cache'...
OKAY [ 0.232s]
finished. total time: 0.234s
C:\Users\Lemuel\Documents\RESTOCK>fastboot erase data
******** Did you mean to fastboot format this ext4 partition?
erasing 'data'...
OKAY [ 1.447s]
finished. total time: 1.448s
C:\Users\Lemuel\Documents\RESTOCK>fastboot erase APD
******** Did you mean to fastboot format this ext4 partition?
erasing 'APD'...
OKAY [ 0.290s]
finished. total time: 0.294s
C:\Users\Lemuel\Documents\RESTOCK>fastboot erase ADF
******** Did you mean to fastboot format this ext4 partition?
erasing 'ADF'...
OKAY [ 0.232s]
finished. total time: 0.234s
C:\Users\Lemuel\Documents\RESTOCK>fastboot oem wipe splashscreen
...
FAILED (remote: unknown OEM command)
finished. total time: 0.127s
C:\Users\Lemuel\Documents\RESTOCK>fastboot oem stop_partitioning
...
(bootloader) Stop partitioning
OKAY [ 0.210s]
finished. total time: 0.212s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash splashscreen splash_sign.bin
target reported max download size of 536870912 bytes
sending 'splashscreen' (270 KB)...
OKAY [ 0.192s]
writing 'splashscreen'...
OKAY [ 0.236s]
finished. total time: 0.431s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash token MFG_BOM_Full.bin
target reported max download size of 536870912 bytes
sending 'token' (3 KB)...
OKAY [ 0.194s]
writing 'token'...
OKAY [ 0.370s]
finished. total time: 0.566s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash ifwi ifwi-prod.bin
target reported max download size of 536870912 bytes
sending 'ifwi' (4096 KB)...
OKAY [ 0.294s]
writing 'ifwi'...
OKAY [ 1.027s]
finished. total time: 1.326s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash boot boot_sign.bin
target reported max download size of 536870912 bytes
sending 'boot' (11870 KB)...
OKAY [ 0.531s]
writing 'boot'...
OKAY [ 0.648s]
finished. total time: 1.182s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash recovery recovery_sign.bin
target reported max download size of 536870912 bytes
sending 'recovery' (11882 KB)...
OKAY [ 0.520s]
writing 'recovery'...
OKAY [ 0.636s]
finished. total time: 1.163s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash fastboot droidboot_sign.bin
target reported max download size of 536870912 bytes
sending 'fastboot' (14824 KB)...
OKAY [ 0.558s]
writing 'fastboot'...
OKAY [ 0.739s]
finished. total time: 1.302s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash APD APD.img
target reported max download size of 536870912 bytes
erasing 'APD'...
OKAY [ 0.204s]
sending 'APD' (183963 KB)...
OKAY [ 4.927s]
writing 'APD'...
OKAY [ 0.912s]
finished. total time: 6.049s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.233s]
sending sparse 'system' 1/5 (518551 KB)...
OKAY [ 27.274s]
writing 'system' 1/5...
OKAY [ 5.563s]
sending sparse 'system' 2/5 (523662 KB)...
OKAY [ 22.886s]
writing 'system' 2/5...
OKAY [ 6.964s]
sending sparse 'system' 3/5 (520607 KB)...
OKAY [ 24.630s]
writing 'system' 3/5...
OKAY [ 8.077s]
sending sparse 'system' 4/5 (500735 KB)...
OKAY [ 23.704s]
writing 'system' 4/5...
OKAY [ 7.983s]
sending sparse 'system' 5/5 (188368 KB)...
OKAY [ 8.849s]
writing 'system' 5/5...
OKAY [ 1.187s]
finished. total time: 137.827s
C:\Users\Lemuel\Documents\RESTOCK>
C:\Users\Lemuel\Documents\RESTOCK>
C:\Users\Lemuel\Documents\RESTOCK>fastboot reboot
rebooting...
finished. total time: 0.126s
lemuelermita said:
Thank you very much, Sir! I will give you an update soon.
Click to expand...
Click to collapse
The command prompt failed at steps 4,5, and 11. It only boots in a blinking screen with an android saying, "Error". Tried it again for the second time but still boots in same screen. I tried to manually boot up the phone without the commands and worked. Thank you very much!
lemuelermita said:
The command prompt failed at steps 4,5, and 11. It only boots in a blinking screen with an android saying, "Error". Tried it again for the second time but still boots in same screen. I tried to manually boot up the phone without the commands and worked. Thank you very much!
Click to expand...
Click to collapse
hmm good to know device working again. strongly recommend you to perform a factory reset even device working perfectly.

Categories

Resources