Hello all, long time lurker here.
I was working with my new M3 and ended up bricked. I unlocked bootloader, installed twrp greatslon 3.0.2-0, did an advanced wipe with all options(don't ask me why because I don't know why other than I had been working on it for a long time and was tired.)
Here is where I am:
have access to twrp greatslon
no adb
no hisuite
no files on internal storage
I have HUAWEI MediaPad M3 8 Firmware BTV-W09 CC100B006 EMUI 4.1 Android 6.0
Thanks in advance for your assistance and replies.
Signed,
Dumbass
I can also enter fastboot/rescue mode from twrp reboot to bootloader.
I also downloaded a rom from greatslon for this device and tried to install to receive this message in attachment.
Have you tried the dload method using an sdcard?
jmjm003 said:
Have you tried the dload method using an sdcard?
Click to expand...
Click to collapse
I tried that too. Not exactly sure if it was done correctly. I used the update.app file in the dload folder. I think there was an error because that requires erecovery and that's gone too. If you know definitive instructions I would appreciate a link.
Thanks in advance.
Download and extract in dload folder on a external SD CARD - (BTV-W09 ,C100B006, EMUI4.1+ANDROID 6.0):
http://download-c1.huawei.com/download/downloadCenter?downloadId=94471&version=380540&siteCode=de
Turn off tablet.
Press volume up + volume down + power
It should start the update process.
If you had B006 on device, you should flash only this version.
mph300 said:
I tried that too. Not exactly sure if it was done correctly. I used the update.app file in the dload folder. I think there was an error because that requires erecovery and that's gone too. If you know definitive instructions I would appreciate a link.
Thanks in advance.
Click to expand...
Click to collapse
I've used update extractor and pulled the recovery files and flashed them using fastboot before.
That might work for you just to get recovery back.
30adi said:
Download and extract in dload folder on a external SD CARD - (BTV-W09 ,C100B006, EMUI4.1+ANDROID 6.0):
http://download-c1.huawei.com/download/downloadCenter?downloadId=94471&version=380540&siteCode=de
Turn off tablet.
Press volume up + volume down + power
It should start the update process.
If you had B006 on device, you should flash only this version.
Click to expand...
Click to collapse
I can't say thank you enough. About ten minutes and shiny brand new from a paper weight. Now I can play safely.
It's not worth rooting this tablet. Has all you need.
Do an update to 7.0 and you will love it
30adi said:
It's not worth rooting this tablet. Has all you need.
Do an update to 7.0 and you will love it
Click to expand...
Click to collapse
That's next.
I also have 5ghz network available after the fix. Pleasantly surprised.
i got mine bricked..stucked at huawei logo
sent to the service centre
and huawei replaced mine with a new one without asking any question
btw, im from malaysia
haqiim said:
i got mine bricked..stucked at huawei logo
sent to the service centre
and huawei replaced mine with a new one without asking any question
btw, im from malaysia
Click to expand...
Click to collapse
I chose to fix mine.
mph300 said:
I chose to fix mine.
Click to expand...
Click to collapse
i am not an expert like you dude:silly:
haqiim said:
i am not an expert like you dude:silly:
Click to expand...
Click to collapse
Not expert here or I would not have bricked it to start with. Just determined.
After reading all these threads I am still stuck and not sure what to do.
My Mediapad M3 is imported from China so no warranty. Will have to fix it myself.
Currently the tablet is stuck at reboot loop, always stuck at the MediaPad logo, and reboot itself after it cannot boot up. The power button and volume buttons combination does not seem to work for me as well, as it never shut down completely. And worse of all, the LED is always flashing in red when charging, seems that it can't charge at all..
What I did was trying to upgrade to Nougat manually through dload folder, found that keyboard and many other things missing, trying to flash it back to Marshmallow, then this happened.
Any way to get out of this?
whoelsec said:
After reading all these threads I am still stuck and not sure what to do.
My Mediapad M3 is imported from China so no warranty. Will have to fix it myself.
Currently the tablet is stuck at reboot loop, always stuck at the MediaPad logo, and reboot itself after it cannot boot up. The power button and volume buttons combination does not seem to work for me as well, as it never shut down completely. And worse of all, the LED is always flashing in red when charging, seems that it can't charge at all..
What I did was trying to upgrade to Nougat manually through dload folder, found that keyboard and many other things missing, trying to flash it back to Marshmallow, then this happened.
Any way to get out of this?
Click to expand...
Click to collapse
I'm in the same boat as you. Upgraded to Nougat, then flashed back down to Marshmallow through dload folder. But seems like the tablet can't bootup and hold a charge anymore. Did you bootloader unlock yours? If not, you should be able to bring it back for servicing (although it's in china).
fallen_13 said:
I'm in the same boat as you. Upgraded to Nougat, then flashed back down to Marshmallow through dload folder. But seems like the tablet can't bootup and hold a charge anymore. Did you bootloader unlock yours? If not, you should be able to bring it back for servicing (although it's in china).
Click to expand...
Click to collapse
I'm not even sure if the bootloader is locked or unlocked. Does it need to be unlocked to flash other region's rom? I ordered the tablet from China online, but it came with an international ROM (could be HK region). Are you able to fix yours?
whoelsec said:
I'm not even sure if the bootloader is locked or unlocked. Does it need to be unlocked to flash other region's rom? I ordered the tablet from China online, but it came with an international ROM (could be HK region). Are you able to fix yours?
Click to expand...
Click to collapse
Since you can't tell, your bootloader should be locked then. Once unlocked, Huawei shows a very big warning message everytime you power on the tablet. I bought mine from Malaysia, should be an Asian rom (i believe same as HK).
My bootloader was previously unlocked as i root my tablet. It got relocked after i ran the Marshmellow downgrade through dload. But the tablet just never boot up properly. I was able to get into fastboot though, and thought maybe i can unlock the bootloader again and flash each partition manually. But seems like unlocking the bootloader made it worse. Because after the unlock, i was prompted that data will be wiped and device will be restarted. After which, i could never get into the fastboot menu again. If i had kept it without the "bootloader unlocked" message, it should be possible to get it replaced at the service center easily.
30adi said:
It's not worth rooting this tablet. Has all you need.
Do an update to 7.0 and you will love it
Click to expand...
Click to collapse
For me, it's worth. I rooted mine just to flash MoaAB ad-blocking.
whoelsec said:
After reading all these threads I am still stuck and not sure what to do.
My Mediapad M3 is imported from China so no warranty. Will have to fix it myself.
Currently the tablet is stuck at reboot loop, always stuck at the MediaPad logo, and reboot itself after it cannot boot up. The power button and volume buttons combination does not seem to work for me as well, as it never shut down completely. And worse of all, the LED is always flashing in red when charging, seems that it can't charge at all..
What I did was trying to upgrade to Nougat manually through dload folder, found that keyboard and many other things missing, trying to flash it back to Marshmallow, then this happened.
Any way to get out of this?
Click to expand...
Click to collapse
Did you manage to get it fixed or it has turned into a paperweight?
Related
Hello everybody. Today, i managed to kill my MATE 9.
In short :
MHA-L09C435B156
I wanted to update to a newer fw. Used on forum Guide for debranding,changed oeminfo to c636, flashed with offline_update ,dload method.
It failed at 31%. Tried to fastboot flash boot,userdata,system, fastboot ok,but still bootloop.
I had no twrp full backup.
So i tried this killer method:
Unpacked Update.app with huawei firmware extractor. Created a flashable zip.Flashed in twrp. At the end,i got errors that /system; /product ; /vendor, could not be mounted.
Rebooted the system, ignoring the 'no os installed' warning.
And since then, mate 9 no sign of life.
More details?
Battery was around 45% when started playing with firmwares
Kept power button for 30sec-1 minute,nothing
Plugged charger, usb,nothing
Disassembled the phone,disconnected battery (measured it first,and it was at 3.91v - every phone needs 3.7v to start up),reconnected battery,nothing.
In usb,no message,or sound of device connected.
So,it is really dead.
SO:
Don't make flashable zip with Firmware Extractor Tool.
Anyway, any place to buy Mate 9 Motherboard?
Oh, this is sad. Where did you read to do so?
We have functional guides. They work different.
I guess this what you did, may be similar to that what happened to Luca (shield Rom) when flashing dts.img.
He send the device to Huawei and got a new one. Maybe you are lucky, because this can also happen due to a manufacture error.
My device: Mate 9 superroot, Mediapad X2 GEM 701->703 B212 KangVIP (AJ mod)
well, since there are few methods to flash mate 9, i had that 5 second idea, to use that feature in this tool.
about getting another one..no warranty. bought it second hand but sealed box.no chance to get another one.
when i have time,i will try to revive it. i work in a gsm repair shop, so i think there could be few tools capable of reading mate 9 emmc
only thing i can think of to fix it is fh, im really surprised no one has found a way to spoof huawei servers to push firmware over erecovery.
can you get into erecovery? (button up + power, when vibrates, let go of power, or button up + down + power)
@Monster.Kali,
As @virtyx stated, erecovery may be an option. Also, if you are able to connect to Huawei HiSuite, it may be a second option.
no,it doesn't make nothing.
no erecovery
no fastboot
no recovery
virtyx said:
only thing i can think of to fix it is fh, im really surprised no one has found a way to spoof huawei servers to push firmware over erecovery.
can you get into erecovery? (button up + power, when vibrates, let go of power, or button up + down + power)
Click to expand...
Click to collapse
Really?
That's amazing.
these phones are a total waste, the partitions are stupidly relying on each other. you cant even restore from within TWRP without the entire phone breaking.
well,i had all huawei mate models since first one,until mate 9.
i was happy with them
but this one....
huawei service center in my country, finaly accepted to fix it if i agree to pay, due to not having warranty.
i wait them to receive it, so we'll see.
they said they are able to reflash it,some factory method,without changing the main board.
good !
Gesendet von meinem MHA-L29 mit Tapatalk
@duraaraa
Sir, i want to ask you, because i think you know more things than any of us about Huawei phones / firmwares / bricks
Would have been any chance to fix my hard brick mate 9 at home?
Thank you in advance
And many thanks for the others that tried to help me. Thank you all for your time.
Monster.Kali said:
@duraaraa
Sir, i want to ask you, because i think you know more things than any of us about Huawei phones / firmwares / bricks
Would have been any chance to fix my hard brick mate 9 at home?
Thank you in advance
And many thanks for the others that tried to help me. Thank you all for your time.
Click to expand...
Click to collapse
If you plug it into the USB port of a computer and check device manager, and nothing happens, then no. You can't fix it.
ok, nothing happened when plugging in. so i'm lucky that huawei accepted it for fixing
thank you, sir
e-recovery doesnt work either way for mate 9. try holding vol down + power, while plugged into usb 3 port (not sure why usb2 doesn't work for this in vmware) but then use the hisuite.
One word @op and other pro members can I flash twrp and then phh for root? And then install custom rom.
I have warranty, in Samsung there is knox counter which detects and warranty void, is here is the same case likewise? Can I flash stock fw if dont like the custom rom.. @Tkkg1994 he is very awesome developer and also a best of the best person I know who tried his lvl best to answer and solve the each n everyone's problem but he left this device, hes working on S7/S7E.
I have attached my device info pic
wrecklesswun said:
e-recovery doesnt work either way for mate 9. try holding vol down + power, while plugged into usb 3 port (not sure why usb2 doesn't work for this in vmware) but then use the hisuite.
Click to expand...
Click to collapse
well, this one i didn't tried. but it is already sent for repair
[email protected] said:
One word @op and other pro members can I flash twrp and then phh for root? And then install custom rom.
I have warranty, in Samsung there is knox counter which detects and warranty void, is here is the same case likewise? Can I flash stock fw if dont like the custom rom.. @Tkkg1994 he is very awesome developer and also a best of the best person I know who tried his lvl best to answer and solve the each n everyone's problem but he left this device, hes working on S7/S7E.
I have attached my device info pic
Click to expand...
Click to collapse
Thanks for your kind words heeheh and mentioning me here so I can share my experience!
Monster.Kali said:
Hello everybody. Today, i managed to kill my MATE 9.
In short :
MHA-L09C435B156
I wanted to update to a newer fw. Used on forum Guide for debranding,changed oeminfo to c636, flashed with offline_update ,dload method.
It failed at 31%. Tried to fastboot flash boot,userdata,system, fastboot ok,but still bootloop.
I had no twrp full backup.
So i tried this killer method:
Unpacked Update.app with huawei firmware extractor. Created a flashable zip.Flashed in twrp. At the end,i got errors that /system; /product ; /vendor, could not be mounted.
Rebooted the system, ignoring the 'no os installed' warning.
And since then, mate 9 no sign of life.
More details?
Battery was around 45% when started playing with firmwares
Kept power button for 30sec-1 minute,nothing
Plugged charger, usb,nothing
Disassembled the phone,disconnected battery (measured it first,and it was at 3.91v - every phone needs 3.7v to start up),reconnected battery,nothing.
In usb,no message,or sound of device connected.
So,it is really dead.
SO:
Don't make flashable zip with Firmware Extractor Tool.
Anyway, any place to buy Mate 9 Motherboard?
Click to expand...
Click to collapse
Don't ever flash anything from huawei extractor.
I broke my device twice with this method. First I was so stupid and created a flashable zip of ALL partitions available on the firmware dump (my aim was to provide a full stock upgrade package with TWRP method). Well didn't end so well, my mate 9 was dead. Like dead forever. I sent it back and told them it suddenly didn't start after all. Well they couldn't fix it, couldn't check for unlocked bootloader, received a brand new one.
After that I thought, yeah maybe it was stupid to flash all paritions including xloader and more. So I wanted to test only with ONE file, the dts file. So I flashed it using the twrp .img flash option, rebooted. Dead. Same as you and same as me before, sent it back again, received a new one.
So that's the 3rd phone I got now, I decided to sell it. I mean what should I do with a phone that can't be rescued after a flash with one file? Nothing, I can't experiment, not test out anything otherwise it will be broken again.
Also the fact that huawei seemed to troll me about my open source requests (the wrote me back to google for the opensource kernel code) helped me to decide to ditch huawei.
You won't ever face this issues on samsung devices, not opensource requests for kernel, not for killing device suddenly. I have to say the huawei mate 9 is great if you use this device "as is" without trying to develop anything for it.
I hope I could explain you my point a bit better, I advice you to send the phone back with the same method as I did. :good:
Tkkg1994 said:
Thanks for your kind words heeheh and mentioning me here so I can share my experience!
Don't ever flash anything from huawei extractor.
I broke my device twice with this method. First I was so stupid and created a flashable zip of ALL partitions available on the firmware dump (my aim was to provide a full stock upgrade package with TWRP method). Well didn't end so well, my mate 9 was dead. Like dead forever. I sent it back and told them it suddenly didn't start after all. Well they couldn't fix it, couldn't check for unlocked bootloader, received a brand new one.
After that I thought, yeah maybe it was stupid to flash all paritions including xloader and more. So I wanted to test only with ONE file, the dts file. So I flashed it using the twrp .img flash option, rebooted. Dead. Same as you and same as me before, sent it back again, received a new one.
So that's the 3rd phone I got now, I decided to sell it. I mean what should I do with a phone that can't be rescued after a flash with one file? Nothing, I can't experiment, not test out anything otherwise it will be broken again.
Also the fact that huawei seemed to troll me about my open source requests (the wrote me back to google for the opensource kernel code) helped me to decide to ditch huawei.
You won't ever face this issues on samsung devices, not opensource requests for kernel, not for killing device suddenly. I have to say the huawei mate 9 is great if you use this device "as is" without trying to develop anything for it.
I hope I could explain you my point a bit better, I advice you to send the phone back with the same method as I did. :good:
Click to expand...
Click to collapse
that's sad....and disturbing for me as huawei fan. the biggest problem is the kirin processor. on snapdragons, we have qhusb, which most of time,solves any problem.
the biggest problem for me, is that i don't have warranty.
the official huawei service center in my country, accepted to fix it, after i told them that i pay any price. they told that are able to flash empty boards, like your 2 cases, and mine.
the worst part is they also mentioned pcb replacement. the phone is new, i can't find any pcb for it, so i can't refuse the fix
ok, they f***d me up.....
they wanted to replace the mainboard, at 454 eur.
i paid 505 eur for the full box sealed phone.
bye bye huawei. moving to xiaomi mi 6 plus....waiting it to be released.
Monster.Kali said:
ok, they f***d me up.....
they wanted to replace the mainboard, at 454 eur.
i paid 505 eur for the full box sealed phone.
bye bye huawei. moving to xiaomi mi 6 plus....waiting it to be released.
Click to expand...
Click to collapse
That is horrendous......
Hey a midnight black O3t - you'll even have taxi money.
Sent from my MHA-L29 using XDA-Developers Legacy app
Running on stock 6.0.1 MMB29M
locked bootloader
after recovery reset, the phone went into " Encryption unsuccessful" screen. Even after press reset or do factory reset in recovery again, the phone still bootloop into this page.
Could someone help?
Thanks.
laofan said:
Running on stock 6.0.1 MMB29M
locked bootloader
after recovery reset, the phone went into " Encryption unsuccessful" screen. Even after press reset or do factory reset in recovery again, the phone still bootloop into this page.
Could someone help?
Thanks.
Click to expand...
Click to collapse
Hello... Try sideloading a full OTA of your choice from here: https://developers.google.com/android/ota#angler
It needs to be newer than the installed version. Not sure it will solve your issue though. Maybe someone else will chime in with a better solution...
If nothing works, RMA your device.
Good luck...
Thanks for the advice.
I tried to manually flash OTA but it falied because of the locked bootloader.
I am not sure if there is anyone could point me to do it via ADB. I tried using ADB but the phone is not recognized by my computer yet.
5.1 said:
Hello... Try sideloading a full OTA of your choice from here: https://developers.google.com/android/ota#angler
It needs to be newer than the installed version. Not sure it will solve your issue though. Maybe someone else will chime in with a better solution...
If nothing works, RMA your device.
Good luck...
Click to expand...
Click to collapse
laofan said:
Thanks for the advice.
I tried to manually flash OTA but it falied because of the locked bootloader.
I am not sure if there is anyone could point me to do it via ADB. I tried using ADB but the phone is not recognized by my computer yet.
Click to expand...
Click to collapse
Hey...
Reboot into Bootloader. Select recovery mode with the volume rocker and press power.
Once you see the Android guy laying down with his belly opened, press power and tap volume up once.
On the menu select: apply update from ADB
From here type in a command prompt:
adb sideload "name of the full OTA zip you downloaded without quote"
Supposing you have prior knowledge with ADB. Let me know if something is not clear here...
Good luck...
I finally get ADB recognized Nexus 6p. But the ota stop flash at 46%. failed to read command: No error.
5.1 said:
Hey...
Reboot into Bootloader. Select recovery mode with the volume rocker and press power.
Once you see the Android guy laying down with his belly opened, press power and tap volume up once.
On the menu select: apply update from ADB
From here type in a command prompt:
adb sideload "name of the full OTA zip you downloaded without quote"
Supposing you have prior knowledge with ADB. Let me know if something is not clear here...
Good luck...
Click to expand...
Click to collapse
laofan said:
I finally get ADB recognized Nexus 6p. But the ota stop flash at 46%. failed to read command: No error.
Click to expand...
Click to collapse
You might have to RMA. I believe "no command" means the emmc has died.
dieselbuddeh said:
You might have to RMA. I believe "no command" means the emmc has died.
Click to expand...
Click to collapse
That is too bad. The warranty was expired in January.... It can't be RMA.... I wished there are some hopes there
laofan said:
That is too bad. The warranty was expired in January.... It can't be RMA.... I wished there are some hopes there
Click to expand...
Click to collapse
Hello...
Try sideloading the 7.1.2 OTA. Nothing to loose... If it fails yet, sorry, I don't know what else to do.
Good luck..
laofan said:
That is too bad. The warranty was expired in January.... It can't be RMA.... I wished there are some hopes there
Click to expand...
Click to collapse
If you bought the phone direct from Google, you will likely get a one time exception.
v12xke said:
If you bought the phone direct from Google, you will likely get a one time exception.
Click to expand...
Click to collapse
Yes, call them anyway if you purchased from Google. I was 5 months out of warranty for my 6p and they replaced it because I was having battery issues.
5.1 said:
Hello...
Try sideloading the 7.1.2 OTA. Nothing to loose... If it fails yet, sorry, I don't know what else to do.
Good luck..
Click to expand...
Click to collapse
I almost tried all the major OTA, none of them could pass 46%... oh well......
v12xke said:
If you bought the phone direct from Google, you will likely get a one time exception.
Click to expand...
Click to collapse
tommyg562000 said:
Yes, call them anyway if you purchased from Google. I was 5 months out of warranty for my 6p and they replaced it because I was having battery issues.
Click to expand...
Click to collapse
It is not from google. And the warranty ended in January... I am fxxked.....
Probably so. There is one guy who found a 6P with a shattered screen for sale and paid a local repair shop to have the motherboard swapped out. Claims it cost him less than USD $100 but he is in South Korea. You're probably better off cutting your losses and finding another phone... after Huawei tells you NO three times.
v12xke said:
Probably so. There is one guy who found a 6P with a shattered screen for sale and paid a local repair shop to have the motherboard swapped out. Claims it cost him less than USD $100 but he is in South Korea. You're probably better off cutting your losses and finding another phone... after Huawei tells you NO three times.
Click to expand...
Click to collapse
posted it on craigslist now.
( I noticed that you are in the Woodlands area. I missed the time when I am in Houston. One of the best memories)
just a follow-up to somebody might see encounter the same thing. I was not able to fix the phone.
With a locked bootloader and "encryption unsuccessful" page, you might try warranty first. If that does not work, you might want to take rescue OTA from google and flash it in recovery via " install update via ADB".
Please be aware that rescue OTA is different from system image and should be flash via ADB in recovery.
Good luck.
laofan said:
just a follow-up to somebody might see encounter the same thing. I was not able to fix the phone.
With a locked bootloader and "encryption unsuccessful" page, you might try warranty first. If that does not work, you might want to take rescue OTA from google and flash it in recovery via " install update via ADB".
Please be aware that rescue OTA is different from system image and should be flash via ADB in recovery.
Good luck.
Click to expand...
Click to collapse
Hello,
What rescue OTA? Something different than the usual OTA you would sideload with ADB?
Cheers...
5.1 said:
Hello,
What rescue OTA? Something different than the usual OTA you would sideload with ADB?
Cheers...
Click to expand...
Click to collapse
Here are Rescue OTA. One would need to flash it with ADB in recovery. https://developers.google.com/android/ota
The following one is firmware/factory image. One would need to flash it with fastboot while in bootloader mode : https://developers.google.com/android/images
Use the correct zip file according to your flashing mode ( recovery or bootloader)
laofan said:
Here are Rescue OTA. One would need to flash it with ADB in recovery. https://developers.google.com/android/ota
The following one is firmware/factory image. One would need to flash it with fastboot while in bootloader mode : https://developers.google.com/android/images
Use the correct zip file according to your flashing mode ( recovery or bootloader)
Click to expand...
Click to collapse
Hello,
I see nothing different than hmm an OTA here. I thought that was a "special" OTA, but no.
Not sure why it's called rescue OTA, lol.
Thanks for the links, but i know exactly what an OTA and a factory image are. :good:
Thanks...
Hello!
I have the same "Encryption unsuccessful" issue. It happened many times recently. First I replaced the battery, because it produced early sudden shutdown at 30-40%, and could run only for a few hours from 100% to 40%.
The new battery is enough for 30-40 hours as I use it, and can operate the phone down to 1-2% before shutting down.
But if I have to restart the phone, the encryption unsuccessful problem still comes up randomly after battery replacement. I can restart several times without problem, then randomly just fails. Mostly after software updates I guess... I have stock firmware, stock rom, etc. the only thing was made that I have installed TWRP, and wiped user data. Hope that helps. Can it be the defect of the emmc ? If so, how shall I diagnose it?
I'm very newbie android user, I changed from Windows Phone ( ) only a few months ago...
The question is what could cause the Encryption unsuccessful error? It's interesting, that if I enter any random numbers as unlock code, the phone tells that it appears to be valid, but unfortunately cannot decrypt data.
So I would like only to disable forced encryption, maybe that helps. Could someone point me to the right direction about what exactly should I do? Is it enough to flash a modded kernel to disable encryption? I don't want to root, or experiment with custom roms and I would stick to the factory firmware as much as I can, but without encryption of corse...
thanks!
fredmoro said:
Hello!
I have the same "Encryption unsuccessful" issue. It happened many times recently. First I replaced the battery, because it produced early sudden shutdown at 30-40%, and could run only for a few hours from 100% to 40%.
The new battery is enough for 30-40 hours as I use it, and can operate the phone down to 1-2% before shutting down.
But if I have to restart the phone, the encryption unsuccessful problem still comes up randomly after battery replacement. I can restart several times without problem, then randomly just fails. Mostly after software updates I guess... I have stock firmware, stock rom, etc. the only thing was made that I have installed TWRP, and wiped user data. Hope that helps. Can it be the defect of the emmc ? If so, how shall I diagnose it?
I'm very newbie android user, I changed from Windows Phone ( ) only a few months ago...
The question is what could cause the Encryption unsuccessful error? It's interesting, that if I enter any random numbers as unlock code, the phone tells that it appears to be valid, but unfortunately cannot decrypt data.
So I would like only to disable forced encryption, maybe that helps. Could someone point me to the right direction about what exactly should I do? Is it enough to flash a modded kernel to disable encryption? I don't want to root, or experiment with custom roms and I would stick to the factory firmware as much as I can, but without encryption of corse...
thanks!
Click to expand...
Click to collapse
Same. The data decryption being unsuccessful happened to me as well on stock oreo 8.1.0. not rooted
Anyone know how to fix it and doesn't happen again?
Thanks
So i have this A2017G owned by a cousin of mine. He had never tempered with anything except updating OTAs from the settings app. Meaning Stock everything and BL locked. Now, all of a sudden his device lags a lot (after the N-B06 update). When booting the device the boot animation lags like crazy. And it almost never gets past the boot animation (always restarts at Axon 7). The times it does reach past the boot screen, the device hangs after a minute or so and restarts.
Things that i have tried:
# Factory resetting through stock recovery.
# Downloading update.zips from ZTE and trying SD Card update trough stock recovery. Which always fails saying Signature verification failed.
# Booted to factory test mode and tried adb devices on cmd. Nothing comes up as there is no new device on the device manager. Also no sound.
# Booted to EDL mode and flashed N-B06 from this post: https://forum.xda-developers.com/axon-7/how-to/guide-ztea2017v2-0-0b08-t3658636
Nothing helped. Same old lags. And of course, the device is unusable.
What to do? Suggestions?
nsabir said:
So i have this A2017G owned by a cousin of mine. He had never tempered with anything except updating OTAs from the settings app. Meaning Stock everything and BL locked. Now, all of a sudden his device lags a lot (after the N-B06 update). When booting the device the boot animation lags like crazy. And it almost never gets past the boot animation (always restarts at Axon 7). The times it does reach past the boot screen, the device hangs after a minute or so and restarts.
Things that i have tried:
# Factory resetting through stock recovery.
# Downloading update.zips from ZTE and trying SD Card update trough stock recovery. Which always fails saying Signature verification failed.
# Booted to factory test mode and tried adb devices on cmd. Nothing comes up as there is no new device on the device manager. Also no sound.
# Booted to EDL mode and flashed N-B06 from this post: https://forum.xda-developers.com/axon-7/how-to/guide-ztea2017v2-0-0b08-t3658636
Nothing helped. Same old lags. And of course, the device is unusable.
What to do? Suggestions?
Click to expand...
Click to collapse
Get a new phone. Unfortunately I think it's some hardware that is broken. But in case it's not try to flash b05 instead?
I don't see anything else you could do since adb doesn't seems to work. I'd just RMA it with the warranty still being in effect. And if it was purchased trough amazon you'll probably just get a new one ! (that's what happened to me last time).
nsabir said:
So i have this A2017G owned by a cousin of mine. He had never tempered with anything except updating OTAs from the settings app. Meaning Stock everything and BL locked. Now, all of a sudden his device lags a lot (after the N-B06 update). When booting the device the boot animation lags like crazy. And it almost never gets past the boot animation (always restarts at Axon 7). The times it does reach past the boot screen, the device hangs after a minute or so and restarts.
Things that i have tried:
# Factory resetting through stock recovery.
# Downloading update.zips from ZTE and trying SD Card update trough stock recovery. Which always fails saying Signature verification failed.
# Booted to factory test mode and tried adb devices on cmd. Nothing comes up as there is no new device on the device manager. Also no sound.
# Booted to EDL mode and flashed N-B06 from this post: https://forum.xda-developers.com/axon-7/how-to/guide-ztea2017v2-0-0b08-t3658636
Nothing helped. Same old lags. And of course, the device is unusable.
What to do? Suggestions?
Click to expand...
Click to collapse
Did you try downgrading through EDL? I'll post the link to MM B10 for you to install through EDL, see if that helps. I seriously doubt that it's a hardware issue since it would not even boot if that was the case (take the Nexus 6P and 5X as an example: big cores busted and the phones wouldn't get past the boot logo).
Don't unlock the bootloader if you can't fix it, it'd make matters worse if LOS-based ROMs didn't work.
Edit: Here are a couple of links for B10 from 4pda. should be the same file:
https://drive.google.com/file/d/0Bynn_Z9_tfeOZWZmN1o2U09pWVU/view
https://mega.nz/#!ZhwR1BAD!PuIWa5Vivk3DxZ1Dgk-wAoITxiKmBiR-j1U8wZZidTw
Choose an username... said:
Did you try downgrading through EDL? I'll post the link to MM B10 for you to install through EDL, see if that helps. I seriously doubt that it's a hardware issue since it would not even boot if that was the case (take the Nexus 6P and 5X as an example: big cores busted and the phones wouldn't get past the boot logo).
Don't unlock the bootloader if you can't fix it, it'd make matters worse if LOS-based ROMs didn't work.
Edit: Here are a couple of links for B10 from 4pda. should be the same file:
https://drive.google.com/file/d/0Bynn_Z9_tfeOZWZmN1o2U09pWVU/view
https://mega.nz/#!ZhwR1BAD!PuIWa5Vivk3DxZ1Dgk-wAoITxiKmBiR-j1U8wZZidTw
Click to expand...
Click to collapse
I have tried this EDL package as well. Most of the time it says can not found programmer file. Only once it said can not find hello packet, reset status. That also ended up in error.
The N-B06 EDL package flashes fine. But the problem still persists.
I have also tried replacing N-B06 recovery.img with TWRP recovery.img and flashed it. But that just bricks the recovery.
Currently the 2 EDL packages i know are these two. N-B06 and MM-B10 for the G. The N one works fine while the MM one doesn't. Do u have any other EDL packages?
I too think it's a software problem since he has never dropped the phone and only used it for 2 months.
nsabir said:
I have tried this EDL package as well. Most of the time it says can not found programmer file. Only once it said can not find hello packet, reset status. That also ended up in error.
The N-B06 EDL package flashes fine. But the problem still persists.
I have also tried replacing N-B06 recovery.img with TWRP recovery.img and flashed it. But that just bricks the recovery.
Currently the 2 EDL packages i know are these two. N-B06 and MM-B10 for the G. The N one works fine while the MM one doesn't. Do u have any other EDL packages?
I too think it's a software problem since he has never dropped the phone and only used it for 2 months.
Click to expand...
Click to collapse
I think something is wrong with the hardware. I had a similar problem as u with my last phone a honor 8, it frozed up and it was nothing I couldnt do other than go back to the store with it. I got a new one.
nsabir said:
I have tried this EDL package as well. Most of the time it says can not found programmer file. Only once it said can not find hello packet, reset status. That also ended up in error.
The N-B06 EDL package flashes fine. But the problem still persists.
I have also tried replacing N-B06 recovery.img with TWRP recovery.img and flashed it. But that just bricks the recovery.
Currently the 2 EDL packages i know are these two. N-B06 and MM-B10 for the G. The N one works fine while the MM one doesn't. Do u have any other EDL packages?
I too think it's a software problem since he has never dropped the phone and only used it for 2 months.
Click to expand...
Click to collapse
I got that package from 4pda. if you go to the 4th category brick repair manual, then enter the link that says "Qualcomm drivers and MiFlash" it will redirect you to 4pda. no need to translate: just open the spoilers (I think it's the 2nd) and you'll find all of the images. You obviously have to use the A2017G ones. there's B10, i think B11, B05, B06 and maybe another N package too
The thing is that it'd be best if you could downgrade to Marshmallow, as that would probably do some other stuff that N packages don't do.
Do you have an external SD card plugged in? Try to use without external sd, i already had lags because of a defective sd card (that couldnt be rescued nor reformatted )
Perru said:
Do you have an external SD card plugged in? Try to use without external sd, i already had lags because of a defective sd card (that couldnt be rescued nor reformatted )
Click to expand...
Click to collapse
I was gonna suggest that, but a read-only SD card wouldn't provoke that. I had one that got read-only after using it as swap for a long time, and you would only notice in twrp (booted in ~2 minutes). If he was able to try to install a system update through the recovery, he was able to write to the SD card --> it's not dead
Perru said:
Do you have an external SD card plugged in? Try to use without external sd, i already had lags because of a defective sd card (that couldnt be rescued nor reformatted )
Click to expand...
Click to collapse
It lags the same. Regardless a sd card is inserted or not.
Choose an username... said:
I got that package from 4pda. if you go to the 4th category brick repair manual, then enter the link that says "Qualcomm drivers and MiFlash" it will redirect you to 4pda. no need to translate: just open the spoilers (I think it's the 2nd) and you'll find all of the images. You obviously have to use the A2017G ones. there's B10, i think B11, B05, B06 and maybe another N package too
The thing is that it'd be best if you could downgrade to Marshmallow, as that would probably do some other stuff that N packages don't do.
Click to expand...
Click to collapse
Thank you for mentioning there is EDL packages in 4pda. I just tried the packages that are available for the G variant on 4pda. But the problem still persists.
I was thinking that too. Trying to downgrade through EDL. But so far i've found only one MM so far, B10. But that ends up in error during flashing process.
Is there any way to install TWRP through EDL without unlocking bootloader? Also, is there any way to unlock BL without adb? If i could at least unlock the BL, i could flash twrp through EDL. There are EDL packages available for flashing TWRP.
Thanks.
nsabir said:
Thank you for mentioning there is EDL packages in 4pda. I just tried the packages that are available for the G variant on 4pda. But the problem still persists.
I was thinking that too. Trying to downgrade through EDL. But so far i've found only one MM so far, B10. But that ends up in error during flashing process.
Is there any way to install TWRP through EDL without unlocking bootloader? Also, is there any way to unlock BL without adb? If i could at least unlock the BL, i could flash twrp through EDL. There are EDL packages available for flashing TWRP.
Thanks.
Click to expand...
Click to collapse
Why don't u just go back to the store with it and get a new one? Its clearly something that can't be fixed by yourself unfortunately.
jw1985 said:
Why don't u just go back to the store with it and get a new one? Its clearly something that can't be fixed by yourself unfortunately.
Click to expand...
Click to collapse
Not all that clear, but yeah the last thing I'd do is unlock the bootloader.
Choose an username... said:
Not all that clear, but yeah the last thing I'd do is unlock the bootloader.
Click to expand...
Click to collapse
Mabey but I think as in my case that something has happened with the hardware. I think it is a hardware's fault that has come up to the surface when he updated the phone like it did 2 me. But hey, it's just my theory.
jw1985 said:
Why don't u just go back to the store with it and get a new one? Its clearly something that can't be fixed by yourself unfortunately.
Click to expand...
Click to collapse
Choose an username... said:
Not all that clear, but yeah the last thing I'd do is unlock the bootloader.
Click to expand...
Click to collapse
jw1985 said:
Mabey but I think as in my case that something has happened with the hardware. I think it is a hardware's fault that has come up to the surface when he updated the phone like it did 2 me. But hey, it's just my theory.
Click to expand...
Click to collapse
The problem is axon 7 is not available in our country. If he has to rma it then he has to send it to a relative in Sweden. Then the relative can do that for him. That's why he asked me to do what i can to revive the phone. RMA is the last resort for him.
Now, i guess i will give up and tell him i did everything i could.
Anyways, thank you all for helping.
Yes folks,
As I said, I discovered SUPER BRICK, TOTAL BRICK, COMPLETE FAILURE or whatever yoy want to name this new brick. It has been like this: I was following the instructions to update oreo in HONOR 8 LITE, at the end I had to write some codes in twrp (advance / terminal ...) so it was starting to do the last update (sd card update.zip) and by accident I touched the screen where it appears: REBOOT, so the phone restarted but the screen is not working when it tries to enter erecovery mode, so here is the list of my problems:
- it does not work: erecovery (so I can not recover the phone)
- fastboot works: when I install something (twrp or firmware, I have tried everyone of them) the phone does not start
- if I try to go to TWRP (after installing an oreo one): the screen seems to break and you can not see anything
Please, my phone is 2 months old, man I need to make it work again, I need it.
Help help help
You should post this in Honor 8 lite forum ...
But whatever, you said that fastboot works if so you can try to use huawei update extractor and flash system,boot,recovery,cust that *should* work
Nikola6511 said:
You should post this in Honor 8 lite forum ...
But whatever, you said that fastboot works if so you can try to use huawei update extractor and flash system,boot,recovery,cust that *should* work
Click to expand...
Click to collapse
I wrote it down here because it is fully compatible and there are more roms here than the honor 8 lite forum, that´s why, it was not a mistake it is because I am desperate.
I can not install BOOT, I have tried and it does not work, anyways I need help.
Thanks in advance
alopez_666 said:
I wrote it down here because it is fully compatible and there are more roms here than the honor 8 lite forum, that´s why, it was not a mistake it is because I am desperate.
I can not install BOOT, I have tried and it does not work, anyways I need help.
Thanks in advance
Click to expand...
Click to collapse
Sry i didnt know its the same.
What error do you get when you try to flash boot.img?
Nikola6511 said:
Sry i didnt know its the same.
What error do you get when you try to flash boot.img?
Click to expand...
Click to collapse
I finally installed BOOT properly, but the problem is that I have inside the phone OREO SYSTEM and I can not find BOOT in the updates I am downloading, as I said, once BOOT was installed, it did not work because it came form nougat.
Phone is very dead.
alopez_666 said:
I finally installed BOOT properly, but the problem is that I have inside the phone OREO SYSTEM and I can not find BOOT in the updates I am downloading, as I said, once BOOT was installed, it did not work because it came form nougat.
Phone is very dead.
Click to expand...
Click to collapse
This may be a stupid question..
If i understood correctly, you can install Boot from nougat, right?
If so why dont you flash nougat rom again?
Nikola6511 said:
This may be a stupid question..
If i understood correctly, you can install Boot from nougat, right?
If so why dont you flash nougat rom again?
Click to expand...
Click to collapse
I have tried nougat and oreo, but nothing happens, after I install them the phone starts and suddendly it stays as the picture attached.
I tell you something: I used emui erecovery to get everything back but now it does not work anymore, my phone is dead
alopez_666 said:
I have tried nougat and oreo, but nothing happens, after I install them the phone starts and suddendly it stays as the picture attached.
I tell you something: I used emui erecovery to get everything back but now it does not work anymore, my phone is dead
Click to expand...
Click to collapse
Im really sorry i cant help
There is a way to fix that.. but... Its too complicated and hard to do..
Since your phone is new, you probably dont want to buy new.
This is going to cost you a bit.
First you will need to find honor 8 lite or p8 lite (if you say they are the same)
that is well.. dead, open it take out a memory chip on both phone and place chip from dead phone to yours. If you dont know how to do that take it to the repair shop and they should know how to do that.
As i sad its very hard and it costs, but it works if done properly.
I saved my friends phone like that, idk what he did but phone wasnt visible in adb, fastboot and recovery didnt work just blue screen.
Note:
This needs to be done very carefully or ypur phone will be 100% dead
alopez_666 said:
I have tried nougat and oreo, but nothing happens, after I install them the phone starts and suddendly it stays as the picture attached.
I tell you something: I used emui erecovery to get everything back but now it does not work anymore, my phone is dead
Click to expand...
Click to collapse
I think your EMMC memory might be fried
Nikola6511 said:
Im really sorry i cant help
There is a way to fix that.. but... Its too complicated and hard to do..
Since your phone is new, you probably dont want to buy new.
This is going to cost you a bit.
First you will need to find honor 8 lite or p8 lite (if you say they are the same)
that is well.. dead, open it take out a memory chip on both phone and place chip from dead phone to yours. If you dont know how to do that take it to the repair shop and they should know how to do that.
As i sad its very hard and it costs, but it works if done properly.
I saved my friends phone like that, idk what he did but phone wasnt visible in adb, fastboot and recovery didnt work just blue screen.
Note:
This needs to be done very carefully or ypur phone will be 100% dead
Click to expand...
Click to collapse
What about using DC PHOENIX???? What do you think????
alopez_666 said:
What about using DC PHOENIX???? What do you think????
Click to expand...
Click to collapse
Idk I never tried it, but it costs and it's not guaranteed it will work but it's worth a try
---------- Post added at 09:55 PM ---------- Previous post was at 09:46 PM ----------
If I understood correctly it will flash any file no matter what so technically it should work
Nikola6511 said:
Idk I never tried it, but it costs and it's not guaranteed it will work but it's worth a try
---------- Post added at 09:55 PM ---------- Previous post was at 09:46 PM ----------
If I understood correctly it will flash any file no matter what so technically it should work
Click to expand...
Click to collapse
DC Phoenix worked fine, it's been awesome, I installed the rom and my phone is alive, I wonder: why I couldn't do it with ADB? Why this software is so powerful? And finally, why nobody is making kind of software like this for free? I mean, dc phoenix must be like the software that Huawei technicians use in their lab and samsung has ODIN that is so powerful as well and is free.
Anyway, if anybody has a problem as mine, you have to pay but it has solution. By the way, I went to tech service and they did not do anything because I bought my phone in China and they could not touch more than european phones, but they told me something that made me think that my trouble had a solution: rewrite the rom and that point convinced me that DC Phoenix would work, and so did it. Thank you all for the info.
Same for me, how to fix please. Bricked following this "guide"
https://www.haky86.com/2018/05/12/install-emui-8-0-huawei-p8-lite-2017/
I was on official Emui Nougat, wanted Oreo, forced update with nocheck, everything is broke except fastboot.
When I want to flash his OreoTWRP.img with "fastboot flash recovery_ramdisk /path/to/img" it work but can't reboot to recovery.
I press Power + Vol+ but it reboot "phone untrusted" with Vol+ for going to eRecovery (usualy it's here you can shutdown the phone) but error mode.
Maybe the OreoTWRP work after my command but can't boot into it. Please help.
alopez_666 said:
DC Phoenix worked fine, it's been awesome, I installed the rom and my phone is alive, I wonder: why I couldn't do it with ADB? Why this software is so powerful? And finally, why nobody is making kind of software like this for free? I mean, dc phoenix must be like the software that Huawei technicians use in their lab and samsung has ODIN that is so powerful as well and is free.
Anyway, if anybody has a problem as mine, you have to pay but it has solution. By the way, I went to tech service and they did not do anything because I bought my phone in China and they could not touch more than european phones, but they told me something that made me think that my trouble had a solution: rewrite the rom and that point convinced me that DC Phoenix would work, and so did it. Thank you all for the info.
Click to expand...
Click to collapse
Bro my P8lite is also bricked, I accidentally wiped the EMMC then I showed it to a repairer and he somehow took me to fastboot mode, now I can't flash anything because that repairer has partitioned the EMMC and now it is showing 486mb total storage so no ROM is flashing because of size. Can you please give me your USERNAME and PASSWORD of DC Pheonix as you've already bought it. It will solve my issue and it will also save me some money.... I will be very thankful to you....
WAITING FOR A POSITIVE REPLY.
I bought it some time ago and it was a 72 hours license and it expired so I do not have anything from that situation. I will check my computer but I will not probably find anything.
alopez_666 said:
I have tried nougat and oreo, but nothing happens, after I install them the phone starts and suddendly it stays as the picture attached.
I tell you something: I used emui erecovery to get everything back but now it does not work anymore, my phone is dead
Click to expand...
Click to collapse
Hello just looking at that pic is enough. That happens cause you installed the wrong firmware. Either get a proper nougat rom for your device and install boot, recovery and system images from fastboot or a oreo version. Either way that screen means its the wrong firmware version or wrong zone. for example you can be trying to install a europe rom in a asian device. hope this helps
legionfx said:
Hello just looking at that pic is enough. That happens cause you installed the wrong firmware. Either get a proper nougat rom for your device and install boot, recovery and system images from fastboot or a oreo version. Either way that screen means its the wrong firmware version or wrong zone. for example you can be trying to install a europe rom in a asian device. hope this helps
Click to expand...
Click to collapse
Problem was solved, I used DC Phoenix and installed a rom, but I did it some time ago. Thanks anyway
Hey,
I've been on quite a journey since I attempted to flash the Treble rom for newbies. My phone eventually ended up as DFU'd but, I brought it back to life after a following the DFU Unbrick - Disassembly guide. After doing this, the screen was not responsive to touch at all at the Welcome screen of the EDU ROM. So, my adventure continued as I took the phone apart several times again to make certain things were connected, not damaged, etc..
After flashing TWRP I concluded the screen itself must be fine because I could use TWRP using the screen/touch. I have since tried flashing several different roms, tried many combos of unlocking the bootloader (again, because I assume it was already unlocked due to the bootloader warning screen of can not check for corruption message), tried flashing bootstack and the stock rom from DrakenFX. Used MiFlash, EDM Tool to flash various items.
Each time and currently, when it boots to the Welcome screen it does not respond to touch.
Can anyone please help me with this?
Thank you!
I remember this happened to me some years ago with a different phone, and it was a bad flash.
I resolved it by flashing the stock firmware again.
What did you flash with MiFlash? Stock firmware untouched? You must do this, try with B35 untouched. Don't flash stuff with TWRP.
Untouched? Is there anything on here like that?
https://androidfilehost.com/?fid=962187416754472312 B35 A2017U
https://androidfilehost.com/?fid=746010030569960045 B10 A2017G
https://www.androidfilehost.com/?fid=818070582850490196 B14 A2017CN
Those are "untouched" system images. Replace recovery.img with a proper TWRP version before flashing:
https://androidfilehost.com/?fid=673956719939822011
bornlivedie said:
https://androidfilehost.com/?fid=962187416754472312 B35 A2017U
https://androidfilehost.com/?fid=746010030569960045 B10 A2017G
https://www.androidfilehost.com/?fid=818070582850490196 B14 A2017CN
Those are "untouched" system images. Replace recovery.img with a proper TWRP version before flashing:
https://androidfilehost.com/?fid=673956719939822011
Click to expand...
Click to collapse
Yeah, unfortunately the very first link (since I am in the USA and have a U version) is the very stock EDL version I used with MiFlash rightg after I was successful getting the phone out of DFU. I have tried flashing it twice after and still nothing.
Thank you for helping!!!
djprez said:
Yeah, unfortunately the very first link (since I am in the USA and have a U version) is the very stock EDL version I used with MiFlash rightg after I was successful getting the phone out of DFU. I have tried flashing it twice after and still nothing.
Thank you for helping!!!
Click to expand...
Click to collapse
Sad to hear that... Maybe you can try again? Who knows, with a little bit of luck...
Or try another version, like this one:
https://www.androidfilehost.com/?fid=890129502657579386
btw, did you try every single spot in your screen while in TWRP? Maybe some pins in the connector are broken and some parts work and others doesn't?
And for the sake of it, you could try discharging your battery completely.
Last thing I can think of... is to restore the stock recovery and apply the official update via sdcard:
https://www.dropbox.com/s/xy7nd252f3rcm5y/338450B3220A2017UV1.1.0B35(SD card software).zip?dl=0
It was taken from here:
https://www.zteusa.com/axon-7#support
bornlivedie said:
Sad to hear that... Maybe you can try again? Who knows, with a little bit of luck...
Or try another version, like this one:
https://www.androidfilehost.com/?fid=890129502657579386
btw, did you try every single spot in your screen while in TWRP? Maybe some pins in the connector are broken and some parts work and others doesn't?
And for the sake of it, you could try discharging your battery completely.
Last thing I can think of... is to restore the stock recovery and apply the official update via sdcard:
https://www.dropbox.com/s/xy7nd252f3rcm5y/338450B3220A2017UV1.1.0B35(SD card software).zip?dl=0
It was taken from here:
https://www.zteusa.com/axon-7#support
Click to expand...
Click to collapse
Yeah, the entire screen works perfectly in TWRP. I disassembled it several times before when I thought I may have put it back together wrong or damaged something so, the battery was removed those several times therefore, no power.
I'll try the stock above. I'm actually trying another stock rom atm --- flashing from sdcard
djprez said:
Yeah, the entire screen works perfectly in TWRP. I disassembled it several times before when I thought I may have put it back together wrong or damaged something so, the battery was removed those several times therefore, no power.
I'll try the stock above. I'm actually trying another stock rom atm --- flashing from sdcard
Click to expand...
Click to collapse
Well, EUREKA! I found I had saved the first files you were supposed to load when the Axon was first unlocked ( file name STEP_1_3-B20_FULL_OTA). Flashed it and the screen works fine. Now, I have to remember how to update it...lol I've unlocked the bootloader in Developer mode and I should be on my way..... fingers crossed.
djprez said:
Well, EUREKA! I found I had saved the first files you were supposed to load when the Axon was first unlocked ( file name STEP_1_3-B20_FULL_OTA). Flashed it and the screen works fine. Now, I have to remember how to update it...lol I've unlocked the bootloader in Developer mode and I should be on my way..... fingers crossed.
Click to expand...
Click to collapse
Strange.
Nevertheless, congratulations. Happy for you.
Well, it's great that I now know the screen/hardware is fine but, I am unable to get any further than version B20. OTA doesn't work, the other files to flash (STEP_4-B20_to_B27 and STEP_5-B27_to_B29) won't flash and get aborted due to it expecting a certain version. I've tried DrakenFX Bootstack and then Stock System and it boots to the Welcome screen but the screen is no longer responsive again.
I have been at this all day again and it's shaping up another all night too. I am so baffled!
Restore to stock firmware your phone came shipped with.After that update trough ota or sd card package and maybe dont flash Treble again,its broken
djprez said:
Well, it's great that I now know the screen/hardware is fine but, I am unable to get any further than version B20. OTA doesn't work, the other files to flash (STEP_4-B20_to_B27 and STEP_5-B27_to_B29) won't flash and get aborted due to it expecting a certain version. I've tried DrakenFX Bootstack and then Stock System and it boots to the Welcome screen but the screen is no longer responsive again.
I have been at this all day again and it's shaping up another all night too. I am so baffled!
Click to expand...
Click to collapse
i wish i had seen this sooner, because i have this same exact problem on one of my boards. it will update perfectly to any of the MM sd card update files (see rootjunkys bl unlock video, thanks @Tomsgt) but the board/phone will not retain touch functionality on anything higher than mm b29. i had lost my imei on that board, and actually swapped to another one despite eventually regaining it simply bc i wanted to be on Oreo ROMs. if you find a fix, id love to know about it. i flashed and reflashed every update, sd card versions, edl versions, and OTA updates to no avail. Nougat or above, touchscreen didnt work... mine was a gold a2017u. good luck, man. im glad im not crazy.
Sorry to bump an old(er) thread I started. I wanted to ask if anyone has found a solution to this issue yet?
I have since tried updating using OTA to Nougat and the screen doesn't respond so, I had to flash back to Marshmallow B29. Thank you to anyone who might have an idea!