Related
I have been trying to flash TWRP and CWM on Nexus 7 which would not bootup (similar to sleep of death but when I erased data using fastboot it works) but now after unlocking bootloader I can't flash recovery.
In therminal I get "invalid status" after I execute the comand ...............................
Any ideas?
I would sincerely appreciate all your help!
To be more specific
This is what I get in terminal
sending 'bootloader' (7066 KB)...
OKAY [ 0.905s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 1.308s
Click to expand...
Click to collapse
Rename the file to: Recovery
Hi,
My phone pop up messages saying some services stopped. So I turned it off and then it stuck in a boot loop circle. (same problem in this thread, http://forum.xda-developers.com/nexus-4/help/help-im-stuck-bootloop-4-circles-t2864835)
First, I tried to enter recovery mode, failed.
then, I tried to fix my recovery ...
Code:
D:\adt-bundle-windows-x86-20140702\sdk\platform-tools>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.351s]
finished. total time: 0.355s
D:\adt-bundle-windows-x86-20140702\sdk\platform-tools>fastboot flash recovery recovery-clockwork-touch-6.0.4.7-mako.img
sending 'recovery' (8838 KB)...
OKAY [ 0.492s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 0.512s
also tried the latest "openrecovery-twrp-2.7.1.0-mako.img" downloaded from http://techerrata.com/browse/twrp2/mako
same error
Code:
D:\adt-bundle-windows-x86-20140702\sdk\platform-tools>fastboot flash recovery recovery.img
sending 'recovery' (7928 KB)...
OKAY [ 0.454s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 0.473s
here's the fact about my phone:
- CWM (recovery-clockwork-touch-6.0.4.7-mako.img)
- SuperSU (UPDATE-SuperSU-v1.93.zip)
- rooted before the 4.4.4 update, didn't fix the root after ATO update
- Standard Kernel, no custom ROM.
I did suffer the "randomly turning off" problem before (http://forum.xda-developers.com/nexus-4/help/nexus-4-randomly-off-intermittently-t2077148).
What could be the problem for the flash write failure? Is there any other way to recovery the data?
Many Thanks.
Hello gents
The official unlock tool doesn't work for me after running it "Unfortunately, Unlock device tool has stopped. (the unlock tool has never worked for me, even after registering and calling support which was awful)
I have the right version and I'm using a fresh stock MM as of last night.
Any ideas on what I should do next to gain root and unlock the bootloader with this setup?
Much appreciated.
Brett8187 said:
Hello gents
The official unlock tool doesn't work for me after running it "Unfortunately, Unlock device tool has stopped. (the unlock tool has never worked for me, even after registering and calling support which was awful)
I have the right version and I'm using a fresh stock MM as of last night.
Any ideas on what I should do next to gain root and unlock the bootloader with this setup?
Much appreciated.
Click to expand...
Click to collapse
I got my bootloader unlocked without the unlock app using this guide
http://forum.xda-developers.com/showthread.php?p=67547527
Hit thanks if I helped
ZenFreak said:
I got my bootloader unlocked without the unlock app using this guide
http://forum.xda-developers.com/showthread.php?p=67547527#post67547527
Hit thanks if I helped
Click to expand...
Click to collapse
The thread says root required though?
Brett8187 said:
The thread says root required though?
Click to expand...
Click to collapse
There is a link that has a list of all root methods.
I got my ze550kl rooted by only flashing pre-rooted system.img from here http://forum.xda-developers.com/zen...oot-ze550kl-zenfone-laser-z00ld-1-15-t3249326
ZenFreak said:
I got my bootloader unlocked without the unlock app using this guide
http://forum.xda-developers.com/showthread.php?p=67547527
Hit thanks if I helped
Click to expand...
Click to collapse
ZenFreak said:
There is a link that has a list of all root methods.
I got my ze550kl rooted by only flashing pre-rooted system.img from here http://forum.xda-developers.com/zen...oot-ze550kl-zenfone-laser-z00ld-1-15-t3249326
Click to expand...
Click to collapse
Thanks for the input. I'm on the ze551kl, doens't look like anyone has said if it has worked or not for that device. Will the root you used still work on the latest stock firmware/mm build?
I don't think that the Lollipop root img works on MM. The only way to get root is to install the firmware from CM thread and then CM.
SoNic67 said:
I don't think that the Lollipop root img works on MM. The only way to get root is to install the firmware from CM thread and then CM.
Click to expand...
Click to collapse
Alright, to get there I'm assuming i'll need to unlock it. I found a working TWRP img i cant boot to for this but none of the community created unlockers have worked yet. ie this one
(sorry it's been a few years since i've done rooting/unlocking with androids. I used to be really in to it
I used this one because I already had TWRP previously: http://forum.xda-developers.com/showpost.php?p=67558892&postcount=3
Brett8187 said:
Thanks for the input. I'm on the ze551kl, doens't look like anyone has said if it has worked or not for that device. Will the root you used still work on the latest stock firmware/mm build?
Click to expand...
Click to collapse
Go-to this link https://mega.nz/#F!lodnzDhK!H5ChxausDTyko1qGlnF7dw!Fg9FwLoa
This has pre- rooted, locked bootloader flashable system.img for ZE601KL. You can safely flash this on your ze551kl (since both devices are Z00T by their codename)
Just unzip the first system.img.7z.01 file using 7zip. All system.img.7z.0x will automatically merge together to form ~3gb system.img. You can flash this via fastboot command
"fastboot flash system system.img"
Wait for 20 mins, flashing will start only after several minutes since file is huge. Install busybox and then follow the bootloader unlock guide whose link I provided before
ZenFreak said:
Go-to this link https://mega.nz/#F!lodnzDhK!H5ChxausDTyko1qGlnF7dw!Fg9FwLoa
This has pre- rooted, locked bootloader flashable system.img for ZE601KL. You can safely flash this on your ze551kl (since both devices are Z00T by their codename)
Just unzip the first system.img.7z.01 file using 7zip. All system.img.7z.0x will automatically merge together to form ~3gb system.img. You can flash this via fastboot command
"fastboot flash system system.img"
Wait for 20 mins, flashing will start only after several minutes since file is huge. Install busybox and then follow the bootloader unlock guide whose link I provided before
Click to expand...
Click to collapse
Tried this. unzipped to create the combined file. Booted to fastboot and got the following which looked successful:
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 0.542s]
sending sparse 'system' 1/12 (259338 KB)...
OKAY [ 8.913s]
writing 'system' 1/12...
OKAY [ 2.448s]
sending sparse 'system' 2/12 (257277 KB)...
OKAY [ 8.854s]
writing 'system' 2/12...
OKAY [ 2.399s]
sending sparse 'system' 3/12 (257278 KB)...
OKAY [ 8.852s]
writing 'system' 3/12...
OKAY [ 2.491s]
sending sparse 'system' 4/12 (257277 KB)...
OKAY [ 8.839s]
writing 'system' 4/12...
OKAY [ 2.375s]
sending sparse 'system' 5/12 (262102 KB)...
OKAY [ 8.988s]
writing 'system' 5/12...
OKAY [ 2.582s]
sending sparse 'system' 6/12 (257122 KB)...
OKAY [ 8.910s]
writing 'system' 6/12...
OKAY [ 3.241s]
sending sparse 'system' 7/12 (260005 KB)...
OKAY [ 8.924s]
writing 'system' 7/12...
OKAY [ 3.403s]
sending sparse 'system' 8/12 (252193 KB)...
OKAY [ 8.630s]
writing 'system' 8/12...
OKAY [ 2.376s]
sending sparse 'system' 9/12 (258041 KB)...
OKAY [ 8.874s]
writing 'system' 9/12...
OKAY [ 2.379s]
sending sparse 'system' 10/12 (258041 KB)...
OKAY [ 8.882s]
writing 'system' 10/12...
OKAY [ 2.389s]
sending sparse 'system' 11/12 (261502 KB)...
OKAY [ 8.961s]
writing 'system' 11/12...
OKAY [ 2.929s]
sending sparse 'system' 12/12 (139273 KB)...
OKAY [ 4.803s]
writing 'system' 12/12...
OKAY [ 1.791s]
finished. total time: 1503.215s
Rebooted the phone and it's stuck spinning at ASUS logo
So as mentioned in the title, I am stuck in a boot loop after botching the OTA upgrade.
Here's the sequence of events thus far...
Current ROM Pure Nexus (not exactly sure which version, 6.01 something I think, but I hadn't updated it in a bit)
Backed up my ROM with TWRP
Due to the fact that I didn't read anything and got over zealous, I dirty flashed the N OTA over Pure Nexus
After dirty flashing it, N booted up and seemed to work ok until apps started crashing like crazy.
Reflashed TWRP
Restored the backup I previously made
Phone has not been working since; it just boot loops
Wiped data; still boot loops
Attempted flashing older bootloaders, radios, and vendor images back to it to no avail; still boot loops
Finally, I backed up everything on internal storage and flashed the latest factory image (MTC20F) straight from Google
STILL BOOT LOOPS
Reinstalled TWRP, wiped data a few more times... still boot loops
I am officially at a loss here. I can get into fastboot and twrp no problem, but the device won't start.
Current info:
BL: angler-03.54
Baseband: angler-03.61
Device is UNLOCKED.
Qfuse Status: Enabled
Any thoughts would be appreciated! I just want to get it into ANY working state at this point.
Do a full wipe system and vendor and everything, except efs maybe. Flash the twrp 3.0.2 then fastboot flash the factory images of that doesn't work then try to ask Heisenberg.
Done, done, and done, to no avail. Same issue, just a boot loop.
Funkwheat said:
Done, done, and done, to no avail. Same issue, just a boot loop.
Click to expand...
Click to collapse
Just put the phone back to full stock. Follow Heisenberg's guide.
Sent from my Nexus 6P using Tapatalk
Jammol said:
Just put the phone back to full stock. Follow Heisenberg's guide.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Tried that earlier. Did it again just now following his precise instructions and still nothing. Maybe worth noting, though, that I got an error when trying to flash vendor.img. Everything else went fine. Currently not boot looping, but have been at the "Google" screen for about ten minutes.
Funkwheat said:
Tried that earlier. Did it again just now following his precise instructions and still nothing. Maybe worth noting, though, that I got an error when trying to flash vendor.img. Everything else went fine. Currently not boot looping, but have been at the "Google" screen for about ten minutes.
Click to expand...
Click to collapse
Did you wipe data with TWRP?
Heisenberg said:
Did you wipe data with TWRP?
Click to expand...
Click to collapse
I wiped it with factory recovery. I'll try again now with TWRP.
I tried..
Jammol said:
Just put the phone back to full stock. Follow Heisenberg's guide.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I followed the guide to do full stock and I am still getting a loop between the google screen and the can't check this software for corruption screen... HELP!
Should I try locking the boot loader?
ArminasAnarion said:
I followed the guide to do full stock and I am still getting a loop between the google screen and the can't check this software for corruption screen... HELP!
Should I try locking the boot loader?
Click to expand...
Click to collapse
Noooooo! Don't lock the bootloader. If you do that you'll have no way to flash anything and will be royally screwed.
Heisenberg said:
Noooooo! Don't lock the bootloader.
Click to expand...
Click to collapse
I didnt! I realized that would probably brick it
What should i do then? I did the complete back to stock guide and still a loop :C
Heisenberg said:
Did you wipe data with TWRP?
Click to expand...
Click to collapse
I've now flashed TWRP and wiped data with it. Still no luck. Interestingly, though, I'm now getting stuck on the Google screen and not actually technically boot looping.
ArminasAnarion said:
I followed the guide to do full stock and I am still getting a loop between the google screen and the can't check this software for corruption screen... HELP!
Should I try locking the boot loader?
Click to expand...
Click to collapse
Had you flashed Nougat at any point? Not sure if you're having the same issue or not.
ArminasAnarion said:
I didnt! I realized that would probably brick it
What should i do then? I did the complete back to stock guide and still a loop :C
Click to expand...
Click to collapse
Funkwheat said:
I've now flashed TWRP and wiped data with it. Still no luck. Interestingly, though, I'm now getting stuck on the Google screen and not actually technically boot looping.
Click to expand...
Click to collapse
I really don't know what either of you should do. Wiping and flashing the factory images should fix anything on a Nexus.
Funkwheat said:
I've now flashed TWRP and wiped data with it. Still no luck. Interestingly, though, I'm now getting stuck on the Google screen and not actually technically boot looping.
Had you flashed Nougat at any point? Not sure if you're having the same issue or not.
Click to expand...
Click to collapse
Yeah I had flashed Nougat and gotten it to work. But where some root issues so I was going to go back to Pure Nexus, I wiped everything and flash MTC20F boot and radio and vendor and on reboot started having the loop
Heisenberg said:
I really don't know what either of you should do. Wiping and flashing the factory images should fix anything on a Nexus.
Click to expand...
Click to collapse
Agreed! I just went through your guide again, verbatim, this time with a TWRP data wipe beforehand and still no luck. This time everything flashed fine with the latest MTC20F images. Here's a command line transcript...
Code:
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot flash bootloader bootlo
ader-angler-angler-03.54.img
target reported max download size of 494927872 bytes
sending 'bootloader' (3526 KB)...
OKAY [ 0.105s]
writing 'bootloader'...
OKAY [ 0.209s]
finished. total time: 0.316s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.008s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot flash radio radio-angle
r-angler-03.61.img
target reported max download size of 494927872 bytes
sending 'radio' (48600 KB)...
OKAY [ 1.082s]
writing 'radio'...
OKAY [ 2.172s]
finished. total time: 3.255s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.013s]
finished. total time: 0.014s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot flash boot boot.img
target reported max download size of 494927872 bytes
sending 'boot' (12201 KB)...
OKAY [ 0.302s]
writing 'boot'...
OKAY [ 0.182s]
finished. total time: 0.487s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot erase cache
******** Did you mean to fastboot format this ext4 partition?
erasing 'cache'...
OKAY [ 0.030s]
finished. total time: 0.031s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot flash cache cache.img
target reported max download size of 494927872 bytes
erasing 'cache'...
OKAY [ 0.023s]
sending 'cache' (5752 KB)...
OKAY [ 0.150s]
writing 'cache'...
OKAY [ 0.106s]
finished. total time: 0.282s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot flash recovery recovery
.img
target reported max download size of 494927872 bytes
sending 'recovery' (13133 KB)...
OKAY [ 0.321s]
writing 'recovery'...
OKAY [ 0.195s]
finished. total time: 0.517s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot flash system system.img
target reported max download size of 494927872 bytes
erasing 'system'...
OKAY [ 0.397s]
sending sparse 'system' 1/5 (478162 KB)...
OKAY [ 11.178s]
writing 'system' 1/5...
OKAY [ 6.861s]
sending sparse 'system' 2/5 (482961 KB)...
OKAY [ 11.220s]
writing 'system' 2/5...
OKAY [ 7.044s]
sending sparse 'system' 3/5 (480085 KB)...
OKAY [ 11.236s]
writing 'system' 3/5...
OKAY [ 7.268s]
sending sparse 'system' 4/5 (470078 KB)...
OKAY [ 10.822s]
writing 'system' 4/5...
OKAY [ 6.593s]
sending sparse 'system' 5/5 (55832 KB)...
OKAY [ 1.353s]
writing 'system' 5/5...
OKAY [ 0.808s]
finished. total time: 74.788s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot flash vendor vendor.img
target reported max download size of 494927872 bytes
sending 'vendor' (185181 KB)...
OKAY [ 4.125s]
writing 'vendor'...
OKAY [ 2.974s]
finished. total time: 7.100s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>
Btw, how long at the "Google" boot screen should I be waiting before I give up on it ever booting? I've been waiting about ten minutes. I have heard 20 elsewhere, but that sounds excessive.
Well I am doing a complete wipe back to 6.0.0 (MDA89D) I will let you know if it works...
Funkwheat said:
Agreed! I just went through your guide again, verbatim, this time with a TWRP data wipe beforehand and still no luck. This time everything flashed fine with the latest MTC20F images. Here's a command line transcript...
Code:
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot flash bootloader bootlo
ader-angler-angler-03.54.img
target reported max download size of 494927872 bytes
sending 'bootloader' (3526 KB)...
OKAY [ 0.105s]
writing 'bootloader'...
OKAY [ 0.209s]
finished. total time: 0.316s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.008s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot flash radio radio-angle
r-angler-03.61.img
target reported max download size of 494927872 bytes
sending 'radio' (48600 KB)...
OKAY [ 1.082s]
writing 'radio'...
OKAY [ 2.172s]
finished. total time: 3.255s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.013s]
finished. total time: 0.014s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot flash boot boot.img
target reported max download size of 494927872 bytes
sending 'boot' (12201 KB)...
OKAY [ 0.302s]
writing 'boot'...
OKAY [ 0.182s]
finished. total time: 0.487s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot erase cache
******** Did you mean to fastboot format this ext4 partition?
erasing 'cache'...
OKAY [ 0.030s]
finished. total time: 0.031s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot flash cache cache.img
target reported max download size of 494927872 bytes
erasing 'cache'...
OKAY [ 0.023s]
sending 'cache' (5752 KB)...
OKAY [ 0.150s]
writing 'cache'...
OKAY [ 0.106s]
finished. total time: 0.282s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot flash recovery recovery
.img
target reported max download size of 494927872 bytes
sending 'recovery' (13133 KB)...
OKAY [ 0.321s]
writing 'recovery'...
OKAY [ 0.195s]
finished. total time: 0.517s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot flash system system.img
target reported max download size of 494927872 bytes
erasing 'system'...
OKAY [ 0.397s]
sending sparse 'system' 1/5 (478162 KB)...
OKAY [ 11.178s]
writing 'system' 1/5...
OKAY [ 6.861s]
sending sparse 'system' 2/5 (482961 KB)...
OKAY [ 11.220s]
writing 'system' 2/5...
OKAY [ 7.044s]
sending sparse 'system' 3/5 (480085 KB)...
OKAY [ 11.236s]
writing 'system' 3/5...
OKAY [ 7.268s]
sending sparse 'system' 4/5 (470078 KB)...
OKAY [ 10.822s]
writing 'system' 4/5...
OKAY [ 6.593s]
sending sparse 'system' 5/5 (55832 KB)...
OKAY [ 1.353s]
writing 'system' 5/5...
OKAY [ 0.808s]
finished. total time: 74.788s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot flash vendor vendor.img
target reported max download size of 494927872 bytes
sending 'vendor' (185181 KB)...
OKAY [ 4.125s]
writing 'vendor'...
OKAY [ 2.974s]
finished. total time: 7.100s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>
Btw, how long at the "Google" boot screen should I be waiting before I give up on it ever booting? I've been waiting about ten minutes. I have heard 20 elsewhere, but that sounds excessive.
Click to expand...
Click to collapse
It should have booted after 10 minutes, normally. But, if is trying to encrypt it could take a very long time. Were you previously decrypted?
Just did you guide back to 6.0.0 (MDA89D) and the phone is still looping between the google screen and the "cant check for corruption screen"... Am I just bricked?? I have no idea what to even try...
I don't think so, unless that's something that happened automatically. I was on PureNexus (unsure which build).
ArminasAnarion said:
Just did you guide back to 6.0.0 (MDA89D) and the phone is still looping between the google screen and the "cant check for corruption screen"... Am I just bricked?? I have no idea what to even try...
Click to expand...
Click to collapse
Looks like you and I are having the exact same issue... We both went to today's OTA, both ended up attempting to go back, and are both in boot loop states now.... Wonder if this is an actual issue. Hope we can figure it out, cause until then I'm without a phone entirely.
so I am on pure nexus the latest build running xposed and ex kernel. How would I flash android 7..0 and not get this bootloop, if I format completely wipe my phone in twrp would that do it before I flash the ota.zip?
Good afternoon to all, I need a lot of help. I have a p9 lite VNS-L23 C605B120, try to install the rom revolution nougat, unlock the bootloader, install the recovery and from there an update file, when I finish, I reset and the phone left with the black screen, I connect it, the PC and I recognize it: Android bootloader interface, do not enter with the 3 buttons: vol + vol - and button on.
I need help on how I can flash it, with some program or how I can fix it, and what are the necessary files ... Thank you very much already.
Pd: the HiSuit of hawei is opened every time I connect the phone to the PC, but it does not allow me to recover the system, at the beginning it leaves: it is acceded to the system recovery mode, I click to recover system and then leaves, the device Does not support system recovery.
Same here unfortunately
Can you to enter to fastboot? If yes is the bootloader locked or unlocked?
Potato997 said:
Can you to enter to fastboot? If yes is the bootloader locked or unlocked?
Click to expand...
Click to collapse
This is in flashboot mode, and yes unlock bootloader, but black screen, allows to restart with commands, but unfortunately I do not have much knowledge about this, I hope help, what steps can I take to be able to turn it on.
Try to flash again TWRP and boot to recovery.
By fastboot I can reset, install twrp, reboot, but still black screen, there is no vibration, but when connecting the phone, appears in android bootloader interface. What else can I do with commands
As I said, can you boot to TWRP?
Potato997 said:
As I said, can you boot to TWRP?
Click to expand...
Click to collapse
See
hanzox5 said:
See
Click to expand...
Click to collapse
....
But no reboot in recovery
C:\Program Files (x86)\HiSuite\hwtools>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (13810 KB)...
OKAY [ 0.297s]
writing 'boot'...
OKAY [ 0.491s]
finished. total time: 0.788s
C:\Program Files (x86)\HiSuite\hwtools>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (32960 KB)...
OKAY [ 0.704s]
writing 'recovery'...
OKAY [ 1.143s]
finished. total time: 1.862s
C:\Program Files (x86)\HiSuite\hwtools>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (331661 KB)...
OKAY [ 7.077s]
writing 'cust'...
OKAY [ 8.053s]
finished. total time: 15.149s
C:\Program Files (x86)\HiSuite\hwtools>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (452763 KB)...
OKAY [ 10.992s]
writing 'system'...
OKAY [ 11.640s]
sending sparse 'system' (458056 KB)...
OKAY [ 10.877s]
writing 'system'...
OKAY [ 11.137s]
sending sparse 'system' (459104 KB)...
OKAY [ 11.816s]
writing 'system'...
OKAY [ 12.201s]
sending sparse 'system' (457466 KB)...
OKAY [ 11.096s]
writing 'system'...
OKAY [ 11.214s]
sending sparse 'system' (460756 KB)...
OKAY [ 11.049s]
writing 'system'...
OKAY [ 11.190s]
sending sparse 'system' (135249 KB)...
OKAY [ 3.234s]
writing 'system'...
OKAY [ 3.302s]
finished. total time: 119.793s
C:\Program Files (x86)\HiSuite\hwtools>fastboot reboot
rebooting...
finished. total time: 0.016s
C:\Program Files (x86)\HiSuite\hwtools>
Reboot to recovery in this way: shut down the phone, press volume up + power button
Factory reset
Reboot
Do not enter recovery, still on black screen, can tell me which software I can flash it
I already told you like three times.. try both TWRP and stock recovery..
I installed the twrp as the stock recovery and try to enter using press volume up + power button, and nothing
Is there any way to force the phone to enter twrp via fastboot, would help me with commands.
hanzox5 said:
I installed the twrp as the stock recovery and try to enter using press volume up + power button, and nothing
Is there any way to force the phone to enter twrp via fastboot, would help me with commands.
Click to expand...
Click to collapse
fastboot boot recovery.img
Try that.
Also you should try the three buttons method now.
C:\Program Files (x86)\HiSuite\hwtools>fastboot boot recovery.img
creating boot image...
creating boot image - 33753088 bytes
downloading 'boot.img'...
OKAY [ 0.703s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.719s
hanzox5 said:
C:\Program Files (x86)\HiSuite\hwtools>fastboot boot recovery.img
creating boot image...
creating boot image - 33753088 bytes
downloading 'boot.img'...
OKAY [ 0.703s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.719s
Click to expand...
Click to collapse
ಠ_ಠ
Weird.
479/5000
Several times I installed TWRP and stock recovery, and I can not enter any of the 2 forms and even with the three buttons, I even purchase a micro SD of 32gb class 10, with this saying that the SD was the one that did not work.
Please, let's go again, I recommend doing from 0 to try to solve this blessed problem. That I should be doing, it will be possible to clean the cache and user data from fastboot, and from there to do something more.
Have you tried three button method with update.app in dload folder in SD card?
If yes, did it gave you some error/did the update started/when did it stopped?
If I have the sd, and inside the Dload folder, update.app, but it does nothing.