I want to make my HTC 10 look untouched
kewlpanda said:
I want to make my HTC 10 look untouched
Click to expand...
Click to collapse
Cannot currently be done. You can set S- on but you can only get relocked status NOT locked. This will make it clear to anyone looking that the phone has been unlocked and is not untouched.
It's just I've seen HTC m7 and m8 forums made it possible to make it locked status again
kewlpanda said:
It's just I've seen HTC m7 and m8 forums made it possible to make it locked status again
Click to expand...
Click to collapse
I will warn you if you try that you will NOT be happy with the results.
Sent from my SM-T810 using Tapatalk
dottat said:
I will warn you if you try that you will NOT be happy with the results.
Sent from my SM-T810 using Tapatalk
Click to expand...
Click to collapse
Might as well let em do it. Some people just have to learn on their own.
Why won't I like the results?
kewlpanda said:
Why won't I like the results?
Click to expand...
Click to collapse
X2
Sent from my HTC 10 using XDA-Developers mobile app
kewlpanda said:
Why won't I like the results?
Click to expand...
Click to collapse
Because you will BRICK it !
You can always recover from a brick and has locked status been done on HTC 10 yet??
kewlpanda said:
You can always recover from a brick and has locked status been done on HTC 10 yet??
Click to expand...
Click to collapse
You don't fully understand, if you follow any guide from another phone regarding making the phone look s-on and bootloader locked you will BRICK as in you can NOT use the phone anymore at ALL. In the bin....bye bye HTC 10
Mr Hofs said:
You don't fully understand, if you follow any guide from another phone regarding making the phone look s-on and bootloader locked you will BRICK as in you can NOT use the phone anymore at ALL. In the bin....bye bye HTC 10
Click to expand...
Click to collapse
Let him try
And he will have their own answer
kewlpanda said:
You can always recover from a brick and has locked status been done on HTC 10 yet??
Click to expand...
Click to collapse
You seem so confident. Follow your guide and then report back from your iPhone once you've bricked your HTC. Listen to the experienced users who replied to your question, they know what they're saying.
kewlpanda said:
I want to make my HTC 10 look untouched
Click to expand...
Click to collapse
Device need is s-off
http://forum.xda-developers.com/showpost.php?p=66886624&postcount=4
Code:
C:\adb>adb reboot bootloader
C:\adb>fastboot flash pg1fs relocked
htc_fastboot v3.0.9.2 (2015-05-29)
target reported max download size of 536870912 bytes
sending 'pg1fs' (4096 KB)...
OKAY [ 0.132s]
writing 'pg1fs'...
OKAY [ 0.116s]
finished. total time: 0.247s
htc_fastboot finished. total time: 0.447s
C:\adb>fastboot flash pg1fs locked
htc_fastboot v3.0.9.2 (2015-05-29)
target reported max download size of 536870912 bytes
sending 'pg1fs' (4096 KB)...
OKAY [ 0.147s]
writing 'pg1fs'...
OKAY [ 0.100s]
finished. total time: 0.247s
htc_fastboot finished. total time: 0.431s
C:\adb>fastboot flash pg1fs unlocked
htc_fastboot v3.0.9.2 (2015-05-29)
target reported max download size of 536870912 bytes
sending 'pg1fs' (4096 KB)...
OKAY [ 0.131s]
writing 'pg1fs'...
OKAY [ 0.100s]
finished. total time: 0.232s
htc_fastboot finished. total time: 0.416s
S-OFF → S-ON
Code:
fastboot oem writesecureflag 3
nenebear said:
Device need is s-off
http://forum.xda-developers.com/showpost.php?p=66886624&postcount=4
Code:
C:\adb>adb reboot bootloader
C:\adb>fastboot flash pg1fs relocked
htc_fastboot v3.0.9.2 (2015-05-29)
target reported max download size of 536870912 bytes
sending 'pg1fs' (4096 KB)...
OKAY [ 0.132s]
writing 'pg1fs'...
OKAY [ 0.116s]
finished. total time: 0.247s
htc_fastboot finished. total time: 0.447s
C:\adb>fastboot flash pg1fs locked
htc_fastboot v3.0.9.2 (2015-05-29)
target reported max download size of 536870912 bytes
sending 'pg1fs' (4096 KB)...
OKAY [ 0.147s]
writing 'pg1fs'...
OKAY [ 0.100s]
finished. total time: 0.247s
htc_fastboot finished. total time: 0.431s
C:\adb>fastboot flash pg1fs unlocked
htc_fastboot v3.0.9.2 (2015-05-29)
target reported max download size of 536870912 bytes
sending 'pg1fs' (4096 KB)...
OKAY [ 0.131s]
writing 'pg1fs'...
OKAY [ 0.100s]
finished. total time: 0.232s
htc_fastboot finished. total time: 0.416s
S-OFF → S-ON
Code:
fastboot oem writesecureflag 3
Click to expand...
Click to collapse
Why not fully complete the process...go locked and then turn s-on and report back findings. ???
Sent from my HTC6545LVW using Tapatalk
dottat said:
Why not fully complete the process...go locked and then turn s-on and report back findings. ???
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
Thanks for your suggestion,but my English is not good ,it is a very simple way.
This change was made HTC M9 (A9) begins, S-OFF device can with bootloader-mode flash emmc
Code:
fastboot flash <emmc-name> <file-name>
nenebear said:
Thanks for your suggestion,but my English is not good ,it is a very simple way.
This change was made HTC M9 (A9) begins, S-OFF device can with bootloader-mode flash emmc
Code:
fastboot flash <emmc-name> <file-name>
Click to expand...
Click to collapse
OK. Not an HTC 10. Nuff said
Sent from my HTC6545LVW using Tapatalk
Guys STOP comparing commands used for different phones then the HTC 10. Partition tables, sizes, flags can/are changed and all this is VERY DANGEROUS !!!
If you decide to use commands from a completely different device than also give in with the consequences !
You WILL brick the device if you do not have enough solid knowledge !
Has anyone looked at making faux bootloaders? I bet there is something booby trapped now
Deleted
He gon learn today.
Sent from my HTC One M9 using Tapatalk
Related
Hey guys, so I recently got an S6 but was going to sell my m7 for a little extra cash. It had the purple camera issue tho so I was going to return it to stock and send it in for repair. I attempted to follow the return to stock thread but something went wrong. I started out bootloader unlocked via HTCdev and S-off. I thought I had successfully flashed the RUU and proceeded with command to go back to S-on. Well now I can only get to the bootloader. When I try to reboot it always brings me back to the bootloader. Currently it says Tampered, Locked, S-on and I can only do stuff through fastboot. I haven't been able to successfully flash anything from here. Anybody know if there's anything else I can do to get this phone running again? Appreciate any help
What firmware is the phone on? While in fastboot, it will tell you hboot version as well as the os version. If that doesn't work, do fastboot getvar all and post it here with imei and serial removed.
Thanks for the reply. It was on the latest firmware that Santod had posted. OS is 5.28.605.2
If you are on 5.28, the 4.4.3 ruu might work for you.
http://forum.xda-developers.com/showthread.php?t=2919442
EXE RUU VZW M7 4.4.3 S-on users
Sent from my HTC6500LVW using XDA Free mobile app
Uzephi said:
If you are on 5.28, the 4.4.3 ruu might work for you.
http://forum.xda-developers.com/showthread.php?t=2919442
EXE RUU VZW M7 4.4.3 S-on users
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
Whenever I try to use the EXE file I get a connection error. I'm not sure why, the phone's connected and I can still use fastboot. I have the latest HTC sync manager installed so the drivers should be good. If I try to just flash the RUU I get a signature error. Any other ideas that might work?
C:\Users\Rob\Documents\Android Devices\HTC One\Fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.036s]
finished. total time: 0.036s
C:\Users\Rob\Documents\Android Devices\HTC One\Fastboot>fastboot flash zip DOTTA
T_VZW_M7_4.4.3_FUU.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1439606 KB)...
OKAY [ 51.053s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 236.104s
C:\Users\Rob\Documents\Android Devices\HTC One\Fastboot>fastboot reboot-bootload
er
rebooting into bootloader...
OKAY [ 0.036s]
finished. total time: 0.036s
C:\Users\Rob\Documents\Android Devices\HTC One\Fastboot>
Rpowers308 said:
Whenever I try to use the EXE file I get a connection error. I'm not sure why, the phone's connected and I can still use fastboot. I have the latest HTC sync manager installed so the drivers should be good. If I try to just flash the RUU I get a signature error. Any other ideas that might work?
C:\Users\Rob\Documents\Android Devices\HTC One\Fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.036s]
finished. total time: 0.036s
C:\Users\Rob\Documents\Android Devices\HTC One\Fastboot>fastboot flash zip DOTTA
T_VZW_M7_4.4.3_FUU.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1439606 KB)...
OKAY [ 51.053s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 236.104s
C:\Users\Rob\Documents\Android Devices\HTC One\Fastboot>fastboot reboot-bootload
er
rebooting into bootloader...
OKAY [ 0.036s]
finished. total time: 0.036s
C:\Users\Rob\Documents\Android Devices\HTC One\Fastboot>
Click to expand...
Click to collapse
Dude first you have to extract the zip file then run the .exe file just read the instructions in the thread of that RUU. Happy Flashing
OK, I feel like an idiot. I've been trying so many different things to get this to work I copied the section of the command window that I knew wasn't right., however it is still not working. What I have done is extracted the zip from that thread and tried to flash the rom.zip file that was included in it. Unfortunately I still get a signature fail. When I try to use the exe program in that thread I get a USB connection error every time. Thank you both for your replies. It seems that thread is my only shot so I'm going to take my questions over there.
i am trying re-flash STOCK ROM to my Pixel XL and i get this error and i cant figure it out:
C:\Users\Helix\Desktop\Minimal ADB and Fastboot>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader' (32980 KB)...
OKAY [ 1.006s]
writing 'bootloader'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 4.742s]
finished. total time: 5.750s
rebooting into bootloader...
OKAY [ 0.015s]
finished. total time: 0.016s
< waiting for device >
target reported max download size of 536870912 bytes
sending 'radio' (57192 KB)...
OKAY [ 1.708s]
writing 'radio'...
OKAY [ 0.563s]
finished. total time: 2.273s
rebooting into bootloader...
OKAY [ 0.015s]
finished. total time: 0.016s
< waiting for device >
load_file: could not allocate 1850641679 bytes
error: failed to load 'image-marlin-nmf26u.zip': Not enough space
Press any key to exit...
now I'm scared that i have a brick . any help please.
Stop using minimal, it hasn't been updated for our partition size.
ok
ok ill install the Manager thanks
jjdw1970 said:
ok ill install the Manager thanks
Click to expand...
Click to collapse
Use this. Direct from Google and latest update always available. > https://plus.google.com/+ElliottHughes/posts/U3B6H3Sejvv
thanks for the help. Pixel is back up and rocking again. This is a great site.
jjdw1970 said:
This is a great site.
Click to expand...
Click to collapse
Yes, it is.
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.
Hi, Yeah I tried to flash the unlock image,
fastboot -i 0x2b4c flash unlock unlock_bootloader.img
target reported max download size of 1610612736 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.031s]
writing 'unlock'...
FAILED (remote: unlock failed)
finished. total time: 0.053s
Now I am in latest version Nougat
I fixed it ....
Solution ..just try one more time get new unlock_bootloader.IMG then flash it ...Enjoy
viknesh war said:
Hi, Yeah I tried to flash the unlock image,
fastboot -i 0x2b4c flash unlock unlock_bootloader.img
target reported max download size of 1610612736 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.031s]
writing 'unlock'...
FAILED (remote: unlock failed)
finished. total time: 0.053s
Now I am in latest version Nougat
Click to expand...
Click to collapse
Yup i was also facing the same problem a new bootloader image will fix it just request for a new bootloader image from zuk.
viknesh war said:
I fixed it ....
Solution ..just try one more time get new unlock_bootloader.IMG then flash it ...Enjoy
Click to expand...
Click to collapse
Thanks a lot bro.. I downloaded a new unlock_bootloader. Img file, and it worked just fine.
Actually I entered wrong serial number in zuk website while downloading the img file maybe because of that it didn't work at first
HELLO
C:\Users\YOUSSEF\Desktop\OneDrivers_Fastboot\Fastboot>fast
enrecovery-twrp-2.6.3.3-m7.img.
< waiting for device >
target reported max download size of 1826414592 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.185s]
writing 'recovery'...
OKAY [ 0.827s]
finished. total time: 2.027s
C:\Users\YOUSSEF\Desktop\OneDrivers_Fastboot\Fastboot>fast
erasing 'cashe'...
FAILED (remote: not allowed)
finished. total time: 0.000s
C:\Users\YOUSSEF\Desktop\OneDrivers_Fastboot\Fastboot>
some one help me to fixe this problem
i have HTC one M8 T-MOBILE V6.1
+212629891194 its my whatsap
1. What/why M7 recovery for M8
fastboot flash recovery NameOfRecovery.img is correct command
https://twrp.me/htc/htconem8gsm.html
2. cache not cashe
fastboot erase cache is correct command
Kharbas said:
HELLO
C:\Users\YOUSSEF\Desktop\OneDrivers_Fastboot\Fastboot>fast
enrecovery-twrp-2.6.3.3-m7.img.
< waiting for device >
target reported max download size of 1826414592 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.185s]
writing 'recovery'...
OKAY [ 0.827s]
finished. total time: 2.027s
C:\Users\YOUSSEF\Desktop\OneDrivers_Fastboot\Fastboot>fast
erasing 'cashe'...
FAILED (remote: not allowed)
finished. total time: 0.000s
C:\Users\YOUSSEF\Desktop\OneDrivers_Fastboot\Fastboot>
some one help me to fixe this problem
i have HTC one M8 T-MOBILE V6.1
+212629891194 its my whatsap
Click to expand...
Click to collapse
Dude that's a m7 recovery
Sent from my HTC One (M8) using XDA Labs
Always check your command syntax is exactly right, when performing fastboot and adb commands.
And yeah, the proper TWRP for your phone would help.