A while ago I bought a Mediapad M3. Once I realized the 5GHz band was disabled on the US version, I was hellbent on getting it working. I eventually got it working through a bastardized hybrid of the Chinese (BTV-W09C233) and the US (BTV-W09C128) versions. There were a lot of problems with it (e.g. I couldn't install Gboard, I couldn't do a factory reset without losing latin keyboard, etc). I decided to go back to the stock US version and figuring out the minimum change needed to get the 5GHz band working. The tablet just didn't wanna go back to the US version and I wasn't gonna quit. At some point I ****ed up and I'm pretty sure I've hard bricked it dead. Then again many times I've been sure I've totally bricked a device only to stumble across some obscure way to breathe enough life into it to get fastboot or recovery working. I'm hoping this is one of those cases.
The symptoms:
Device is off. Holding the power button for no amount of time has changed that
I've tried a variety of button combos, none seem to do anything
Is there a special download mode like Qualcomm devices where some basic funcionality exists?
Does it respond in fastboot? If so, you might be able to use DC Unlocker(search please.) I haven't been able to try this on my device yet, and probably not for another month.
fargonaz said:
Does it respond in fastboot? If so, you might be able to use DC Unlocker(search please.) I haven't been able to try this on my device yet, and probably not for another month.
Click to expand...
Click to collapse
There would be something on the screen for fastboot, no?
Looking in my dmesg, I don't see any new devices being registered by Linux so I didn't bother with fastboot.
With mine there is no screen activity. If it's not showing up... You could read the DC Unlocker web site, I think there was a hardware method (shorting of test points) to stir the device.
Good Luck!
copolii said:
A while ago I bought a Mediapad M3. Once I realized the 5GHz band was disabled on the US version, I was hellbent on getting it working. I eventually got it working through a bastardized hybrid of the Chinese (BTV-W09C233) and the US (BTV-W09C128) versions. There were a lot of problems with it (e.g. I couldn't install Gboard, I couldn't do a factory reset without losing latin keyboard, etc). I decided to go back to the stock US version and figuring out the minimum change needed to get the 5GHz band working. The tablet just didn't wanna go back to the US version and I wasn't gonna quit. At some point I ****ed up and I'm pretty sure I've hard bricked it dead. Then again many times I've been sure I've totally bricked a device only to stumble across some obscure way to breathe enough life into it to get fastboot or recovery working. I'm hoping this is one of those cases.
The symptoms:
Device is off. Holding the power button for no amount of time has changed that
I've tried a variety of button combos, none seem to do anything
Is there a special download mode like Qualcomm devices where some basic funcionality exists?
Click to expand...
Click to collapse
I am in the same boat.
https://forum.xda-developers.com/mediapad-m3/help/m3-apsabnormal-bricked-t3779100
Will follow this thread will great interest.
Good luck!
I'm on vacation right now and I hate using the laptop for this sort of thing. I'm flying back in the morning and once I'm over the jetlag, I'll see what I can do with the damn thing.
In the meantime, I'd like to punch someone in Huawei for 1- disabling the 5GHz in the NA model and 2- Putting **** software on such great hardware.
Any progress?
Thanks!
Well, hey @copolii. Took a while to find test point as it hasn't been posted or published anywhere. From there it was still a bit tricky. Had to use BTV-DL09 board software to get fastboot only area in ram through factory mode (edl mode). Then fastboot flash the UPDATE.APP to boot to upgrade mode. Then flashed UPDATE.APP with localization files from upgrade mode. After that had to repair serial number and imei in order to get bootloader code. After all that let it update to nougat & emui 5 and it has 5GHz wifi which surprized me a bit. TWRP needs a little tuning and Magisk is working as it should. All of that was accomplished using SigmaKey dongle. Like I said, a bit tricky and don't believe it could have been fixed any other way. Oh, yeah same device, I bought it.
Thanks @tek3195.
I sold the tablet a month ago. Maybe share the info regarding the test pins so that the next person who stumbles upon this here can give it a shot.
copolii said:
Thanks @tek3195.
I sold the tablet a month ago. Maybe share the info regarding the test pins so that the next person who stumbles upon this here can give it a shot.
Click to expand...
Click to collapse
Sorry, I forgot to post this before. So if anyone needs it and I'm sure they will.
Test point for BTV-W09 I would think BTV-DL09 would be the same, both have identical FCCID photos. content://media/external/images/media/28314 . To use test point you must disconnect battery. I would also recommend a little heat at top and bottom of display to remove.
I apologize for no link being posted . I didn't come back and check it , now attached an image hope it works. Don't know where the link went. In the pic there is only one test point as that is all that is used with Kirin devices apparently. The point at end of lime-green line is test point to be grounded with ground pin or any of the heat shields will work. A sharp pair of tweezers works well to make the short and make sure to disconnect battery.
tek3195 said:
Well, hey @copolii. Took a while to find test point as it hasn't been posted or published anywhere. From there it was still a bit tricky. Had to use BTV-DL09 board software to get fastboot only area in ram through factory mode (edl mode). Then fastboot flash the UPDATE.APP to boot to upgrade mode. Then flashed UPDATE.APP with localization files from upgrade mode. After that had to repair serial number and imei in order to get bootloader code. After all that let it update to nougat & emui 5 and it has 5GHz wifi which surprized me a bit. TWRP needs a little tuning and Magisk is working as it should. All of that was accomplished using SigmaKey dongle. Like I said, a bit tricky and don't believe it could have been fixed any other way. Oh, yeah same device, I bought it.
Click to expand...
Click to collapse
Hi @tek3195
I have the same problem.
do you have board software for mediapad m3 BTV DL09 (.xml version)
can you share with me
One more thing, does the process always cause loss of IMEI and serial number.
if so, can we repair it (imei and serial number) without a dongle (maybe via fastboot or twrp)?
I would really appreciate your help
0m M0m0d said:
Hi @tek3195
I have the same problem.
do you have board software for mediapad m3 BTV DL09 (.xml version)
can you share with me
One more thing, does the process always cause loss of IMEI and serial number.
if so, can we repair it (imei and serial number) without a dongle (maybe via fastboot or twrp)?
I would really appreciate your help
Click to expand...
Click to collapse
All I have is .skf format which is for SigmaKey. I have access to paid firmware, I can get .xml format and upload it for you. The only way I know of for xml is IDT which should be packaged with the firmware. What country do you need it for?
Here you should find 2 board software packages with tools and instructions. I've not used IDT before so don't have any insight on it. If you need anything else let me know.
BTV files
tek3195 said:
All I have is .skf format which is for SigmaKey. I have access to paid firmware, I can get .xml format and upload it for you. The only way I know of for xml is IDT which should be packaged with the firmware. What country do you need it for?
Here you should find 2 board software packages with tools and instructions. I've not used IDT before so don't have any insight on it. If you need anything else let me know.
http://www.mediafire.com/folder/43cwcl8hih2u2/BTV-DL09
Click to expand...
Click to collapse
Thank you for replying quickly.
Yes, my plan will be to use idt ver 2.0, because I don't have any dongel :crying:
idt ver 2.0 has a simpler configuration than version 1.0
Actually my devises are btv l0j (mediapa m3 docomo version)
so if you can get the btv l0j version then that would be great.
but if not, then the file that you shared earlier also I think will be enough.
tek3195 said:
... After that had to repair serial number and imei in order to get bootloader code. ..
Click to expand...
Click to collapse
As I have asked before, will this process always cause the loss of IMEI and SN?
if so, can we repair it without a dongle? (via fastboot or twrp maybe)
and once again thank you very much for all your help.
0m M0m0d said:
Thank you for replying quickly.
Yes, my plan will be to use idt ver 2.0, because I don't have any dongel :crying:
idt ver 2.0 has a simpler configuration than version 1.0
Actually my devises are btv l0j (mediapa m3 docomo version)
so if you can get the btv l0j version then that would be great.
but if not, then the file that you shared earlier also I think will be enough.
As I have asked before, will this process always cause the loss of IMEI and SN?
if so, can we repair it without a dongle? (via fastboot or twrp maybe)
and once again thank you very much for all your help.
Click to expand...
Click to collapse
I don't really know as I used sigma's firmware with there software. I have no idea how or what the process are with IDT and the packages I uploaded. Those are straight from easy-firmware, I will look and see if available for l0j.
Added BTV-L0J(2) to MediaFire folder, one 6.0 one 7.0.
tek3195 said:
I don't really know as I used sigma's firmware with there software. I have no idea how or what the process are with IDT and the packages I uploaded. Those are straight from easy-firmware, I will look and see if available for l0j.
Click to expand...
Click to collapse
here is from easy-firmware
https://easy-firmware.com/index.php?a=downloads&b=folder&id=33682
0m M0m0d said:
here is from easy-firmware
https://easy-firmware.com/index.php?a=downloads&b=folder&id=33682
Click to expand...
Click to collapse
Do you have easy-firmware account ?
tek3195 said:
Do you have easy-firmware account ?
Click to expand...
Click to collapse
No, I do not have.
I don't have enough extra money to buy premium easy-firmware. :crying: :crying: :crying:
I am very grateful to you for sharing the board software that I need.
as soon as possible I will try all the files and I will report the results here immediately.
tek3195 said:
I don't really know as I used sigma's firmware with there software. I have no idea how or what the process are with IDT and the packages I uploaded. Those are straight from easy-firmware, I will look and see if available for l0j.
Added BTV-L0J(2) to MediaFire folder, one 6.0 one 7.0.
Click to expand...
Click to collapse
I want to say thank you very much.
I confirm that the file that you shared is working very well.:good::good::good:
I have managed to revive my tab from dead, no power, no recovery, no fast boot, to be normal again. with
slightly modify to the .xml config, skip to the nvme section to avoid missing imei and sn.
The result is i managed to flash board software without losing IMEI and SN.:victory::victory::victory:
once again I really appreciate and thank you for your help.:angel::angel::angel:
tek3195 said:
Sorry, I forgot to post this before. So if anyone needs it and I'm sure they will.
Test point for BTV-W09 I would think BTV-DL09 would be the same, both have identical FCCID photos. content://media/external/images/media/28314 . To use test point you must disconnect battery. I would also recommend a little heat at top and bottom of display to remove.
I apologize for no link being posted . I didn't come back and check it , now attached an image hope it works. Don't know where the link went. In the pic there is only one test point as that is all that is used with Kirin devices apparently. The point at end of lime-green line is test point to be grounded with ground pin or any of the heat shields will work. A sharp pair of tweezers works well to make the short and make sure to disconnect battery.
Click to expand...
Click to collapse
hello i am also having a hard bricked d-01j, is it fixable? please give me detailed instructions, I thank you very much
---------- Post added at 08:04 AM ---------- Previous post was at 07:24 AM ----------
0m M0m0d said:
I want to say thank you very much.
I confirm that the file that you shared is working very well.:good::good::good:
I have managed to revive my tab from dead, no power, no recovery, no fast boot, to be normal again. with
slightly modify to the .xml config, skip to the nvme section to avoid missing imei and sn.
The result is i managed to flash board software without losing IMEI and SN.:victory::victory::victory:
once again I really appreciate and thank you for your help.:angel::angel::angel:
Click to expand...
Click to collapse
Hi, I got hard bricked just like you, have you fixed it? Could you please guide me to fix this error? Thank you very much !!!
0m M0m0d said:
Hi @tek3195
I have the same problem.
do you have board software for mediapad m3 BTV DL09 (.xml version)
can you share with me
One more thing, does the process always cause loss of IMEI and serial number.
if so, can we repair it (imei and serial number) without a dongle (maybe via fastboot or twrp)?
I would really appreciate your help
Click to expand...
Click to collapse
I have the same problem.
do you have board software for mediapad m3 BTV DL09 (.xml version)
can you share with me thank you very much
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
Hey guys
I was wondering if someone here is still on the V6 version of the security update, if you are you can make the TOT file out of the V20 Sprint model. Whoever has the Z3X box for LG, follow these steps:
1. Start the LG Tools
2. Select H918
3. Select the Port 1 in Workspace, in connection put it to: AndroidNet USB Serial Port
4. Search phone button will find the LS997 model.
5. Select the Firmware Maker on the bottom of the right box
This will make the firmware of the version 6, the one that has the hidden menu for the unlock, since we cannot downgrade, maybe we can try it this way, it creates a TOT file that is flashable through the Z3X software
Does anyone have the box with this version, before it was updated. Because I lost that in the hidden menu the unlock function and now I cant even get signal, having issues wanna downgrade.
If someone has this LS997V6, create the firmware so we can flash it and maybe we can go back to that security update before it was patched, been looking around for it. But I dont have that version or else would have created the file to share.
ayoshidage said:
Hey guys
I was wondering if someone here is still on the V6 version of the security update, if you are you can make the TOT file out of the V20 Sprint model. Whoever has the Z3X box for LG, follow these steps:
1. Start the LG Tools
2. Select H918
3. Select the Port 1 in Workspace, in connection put it to: AndroidNet USB Serial Port
4. Search phone button will find the LS997 model.
5. Select the Firmware Maker on the bottom of the right box
This will make the firmware of the version 6, the one that has the hidden menu for the unlock, since we cannot downgrade, maybe we can try it this way, it creates a TOT file that is flashable through the Z3X software
Does anyone have the box with this version, before it was updated. Because I lost that in the hidden menu the unlock function and now I cant even get signal, having issues wanna downgrade.
If someone has this LS997V6, create the firmware so we can flash it and maybe we can go back to that security update before it was patched, been looking around for it. But I dont have that version or else would have created the file to share.
Click to expand...
Click to collapse
But didn’t antirollback change? If so firmware or not you cannot downgrade
Sent from my iPhone using Tapatalk
hyelton said:
But didn’t antirollback change? If so firmware or not you cannot downgrade
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Yes, but I am currently working on it, but I need that firmware version to see what I can do, because I dont have that, I need someone to make a copy of that from their phone using the methods I have provided for me to do the work on it.
ayoshidage said:
Yes, but I am currently working on it, but I need that firmware version to see what I can do, because I dont have that, I need someone to make a copy of that from their phone using the methods I have provided for me to do the work on it.
Click to expand...
Click to collapse
If antirollback did change, there’s no physical possible way to downgrade. It’s not possible, there’s no way around antirollback.
Sent from my iPhone using Tapatalk
hyelton said:
If antirollback did change, there’s no physical possible way to downgrade. It’s not possible, there’s no way around antirollback.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
There is always a way for everything, keep in mind Samsung did the same thing to prevent downgrading the firmware, I have found a way to downgrade that to the first version installed on the device even if you are on the latest version, but took me a very long time to find the exploit for it. So trust me, when I tell you there is always a way. Would I share that, no I wont, because its my business and my hard work alone. But I am willing to share my work for this project.
What is there to lose, you have a person here willing to work for free, and work on this project to share with the community.
ayoshidage said:
There is always a way for everything, keep in mind Samsung did the same thing to prevent downgrading the firmware, I have found a way to downgrade that to the first version installed on the device even if you are on the latest version, but took me a very long time to find the exploit for it. So trust me, when I tell you there is always a way. Would I share that, no I wont, because its my business and my hard work alone. But I am willing to share my work for this project.
What is there to lose, you have a person here willing to work for free, and work on this project to share with the community.
Click to expand...
Click to collapse
Yeah nothing to loose .
Here’s a good post on it. https://forum.xda-developers.com/showpost.php?p=73206763&postcount=3
Here is a post from another thread:
“In short: the ARB is implemented in the bootloader and to be more clear in the certificates within. There is 100% no chance to change this other then when you break the signature algo or find a bug in the implementation”
Good luck, If you get anything be sure to post updates!
Without being able to inject code between the CPU and the NAND, it can't be done. I would LOVE to be proven wrong, but here is a quick overview:
The PBL is located in QFPROM on the CPU. ARB is located in QFPROM on the CPU. The RSA key is located in QFPROM on the CPU.
When you power on the phone, the PBL loads XBL and checks the ARB version. If it is less than what is burned into the CPU, it goes into 9008 mode. It also use the RSA key to verify the signature of XBL. If it is modified -- 9008 mode.
When a phone successfully loads XBL that has a greater ARB version than what is burned into the CPU, it immediately burns the greater ARB version into the CPU.
So there are a couple of attack vectors:
1 - Have some cool hardware that can read the RSA key from the CPU and try and brute force the RSA cert with the key and the sig.
2 - Have some cool hardware that can do a MITM attack on the CPU and NAND replying with a valid return so that the CPU will boot no matter what is on the NAND.
Good luck, I will be following this closely....
-- Brian
runningnak3d said:
Without being able to inject code between the CPU and the NAND, it can't be done. I would LOVE to be proven wrong, but here is a quick overview:
The PBL is located in QFPROM on the CPU. ARB is located in QFPROM on the CPU. The RSA key is located in QFPROM on the CPU.
When you power on the phone, the PBL loads XBL and checks the ARB version. If it is less than what is burned into the CPU, it goes into 9008 mode. It also use the RSA key to verify the signature of XBL. If it is modified -- 9008 mode.
When a phone successfully loads XBL that has a greater ARB version than what is burned into the CPU, it immediately burns the greater ARB version into the CPU.
So there are a couple of attack vectors:
1 - Have some cool hardware that can read the RSA key from the CPU and try and brute force the RSA cert with the key and the sig.
2 - Have some cool hardware that can do a MITM attack on the CPU and NAND replying with a valid return so that the CPU will boot no matter what is on the NAND.
Good luck, I will be following this closely....
-- Brian
Click to expand...
Click to collapse
Hi Brian
Thank you for all the information and all the input, I am gonna try to see what I can do from my end, my issue is this, before the update was patched from the hidden menu. This is the problem that has occured. Before the update, when I got this phone, was running on V6, I believe that was the last version that supported the HiddenMenu.apk, that you were able to change production to lab mode. Now since the mistake I did in updating the security software that has been patched and because of it. I have very weak signal and now also the 4G is gone. Before the update, I had full signal bars and 4G service. Now the bars come and go with the data connected. The phone was unlocked this method (temp method) and then was unlocked using Octopus after the update.
These are the issues:
1. The signal bars goes up and down to 0 and goes up again, I am in a very strong signal area.
2. The 4G was working but not the greatest speeds, was doing like 4-8MB a sec down and 0.1Kbs upload. Which is terrible.
I tried Resetting the Security via box and now the 4G is gone and data. Calls are working but same signal issues.
The issue is I know sprint uses the CDMA technologly, and where I am its GSM network, but my service uses WCDMA because it runs on the AWS network 1700/2100. The problem is this. I can get the HiddenMenu to work again, but that special section in the old version does not exist anymore because it has been patched in the new security update.
I am also able to get in to the band selection, AWS and all other bands are there, but the issue is if you select AWS it says FAILED to connect on any band except on AUTO, so this is why I wanted to have the old version extracted on the version 6, so that I could work on it, since Sprint does not have firmware files you can flash.
So this is the problem. Very stupid the way they did this firmware method OVER THE AIR method. The funny thing is that the it supports all the bands that the GSM supports here and the UMTS.
I just want to get this phone back to full bars with the data restored and have the full speed I had when I did the temp fix, but real solution. I know maybe I can flash a custom rom, but I dont know how reliable that is and if it will resolve the issue.
Whats your input on all of this?
Those issues your having are typical issues of using a sprint device on another carrier. Only fix is flashing a different model firmware which won’t ever be possible for the Sprint model. Never rely on a sprint device unless your using it on sprint.
Sent from my iPhone using Tapatalk
Yes I'm aware of these things of Sprint after finding out. But the weird thing is I never had an issue after that fix for the hidden menu patch that unlocks it when out into lab mode and specifying the APN. Never had a dropped signal once or data. This issued occured after the update. This is my first time owning an Sprint phone so I didn't know there were no firmware which is why I wanted to work on this project.
They say the workround is flashing a DirtySanta ROM. But then again if you fladh that rom would u have those old options back in hidden menu and would it fix the issue. That's the real question.
I am also aware that since you unlock the bootloader and lock it again you can brick the device. Luckly I have made a tot of my whole system firmware image latest version.
What's the best approach to getting this back to working state. My network runs on WCDMA that's why AWS is needed.
Just want to know how to get this working...
> would i share that, no i wont, its my hard work alone ...
>i need someone to ...
I see a hiccup in the reasoning here.
Best of luck. Development on this device came to a screeching halt when ARB hit.r
elijah420 said:
> would i share that, no i wont, its my hard work alone ...
>i need someone to ...
I see a hiccup in the reasoning here.
Best of luck. Development on this device came to a screeching halt when ARB hit.r
Click to expand...
Click to collapse
That's phrase is for the Samsung exploit. Not LG two different phones and companies.
If nobody cares to share that firmware version to extract no worries I won't work on it. Worst comes to worst I'll sell the phone that's all.
Good luck finding a way to do it yourself then. Dont questions others people work when you don't know what skills they have in the mobile field.
Thanks for everyone else for their input.
ayoshidage said:
That's phrase is for the Samsung exploit. Not LG two different phones and companies.
If nobody cares to share that firmware version to extract no worries I won't work on it. Worst comes to worst I'll sell the phone that's all.
Good luck finding a way to do it yourself then. Dont questions others people work when you don't know what skills they have in the mobile field.
Thanks for everyone else for their input.
Click to expand...
Click to collapse
Well thank you, but you fail to understand something very basic here. While there may have been a question mark in there somewhere, in no way was your request a request. It was rather demanding. You demanded someone do something for you, with no reciprocity from you. I think attitudes like that tend to rankle rather than disarm.
As far as the last bit of your snarky comment - bear this in mind - I'm not the one looking for a 'way to do it myself'.
Again, best of luck.
elijah420 said:
Well thank you, but you fail to understand something very basic here. While there may have been a question mark in there somewhere, in no way was your request a request. It was rather demanding. You demanded someone do something for you, with no reciprocity from you. I think attitudes like that tend to rankle rather than disarm.
As far as the last bit of your snarky comment - bear this in mind - I'm not the one looking for a 'way to do it myself'.
Again, best of luck.
Click to expand...
Click to collapse
Thanks for you reply, but I dont think you understood the meaning of what request means? Request means " an act of asking politely or formally for something" I think you should understand what the meaning of request means before commenting no sense. Also I didn't demand someone, I was asking if someone had a dump file or if someone could create a dump file for me to work on the project. I am here to help people out to find solutions, you are here for the purpose of starting rant on the forums. By no means, this was demand or any sort of order in bossing people around. But its all good, I dont have the phone anymore, so no need to work on it anymore, have a great day.
Thanks.
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
My nokia 6.1 plus wont boot or load, it just goes to the android 1 screen then shows the battery life when off. I made this you tube video to show all of the struggles ive had. Any help is appreciated.
Attachments area
Preview YouTube video Nokia 6.1 plus wont boot or load
barrnunn said:
My nokia 6.1 plus wont boot or load, it just goes to the android 1 screen then shows the battery life when off. I made this you tube video to show all of the struggles ive had. Any help is appreciated.
Attachments area
Preview YouTube video Nokia 6.1 plus wont boot or load
https://youtu.be/OiGgNE34Ks4
Attachments area
Preview YouTube video Nokia 6.1 plus wont boot or load
Click to expand...
Click to collapse
here is the linkn
https://youtu.be/OiGgNE34Ks4
Nokia 6.1 Plus
barrnunn said:
here is the linkn
https://youtu.be/OiGgNE34Ks4
Click to expand...
Click to collapse
Hi, is this phone just stock Android?
Have you unlocked the Bootloader? Or done anything ( mods) etc???
Did this phone work at some stage? when did it start to not boot?
Have you updated to Pie?
Have you tried to get into fastboot - https://www.hardreset.info/devices/nokia/nokia-61-plus/fastboot-mode/
We need more information.... Mabybe able to help...
And should be posted over in the Question and Answer Thread.. ?
Your device is safe . Just go to nearest care point tell them software gone and tell them to reflash the software using ost
slysurfer said:
Hi, is this phone just stock Android?
Have you unlocked the Bootloader? Or done anything ( mods) etc???
Did this phone work at some stage? when did it start to not boot?
Have you updated to Pie?
Have you tried to get into fastboot - https://www.hardreset.info/devices/nokia/nokia-61-plus/fastboot-mode/
We need more information.... Mabybe able to help...
Click to expand...
Click to collapse
Not sure on these questions. I believe it is stock. I bought it from an acquaintance that said he was just upgrading. He showed me it working. I got it a week later and its doing this. Trying to see if its fixable before addressing him. I believe it was stock and with oreo. I just know he was saying its the new android 1 and for 2 years of updates.
lilbrat said:
And should be posted over in the Question and Answer Thread.. ?
Click to expand...
Click to collapse
Ok, I wasnt sure since i need recovery help. Can a moderator move it?
Raghu varma said:
Your device is safe . Just go to nearest care point tell them software gone and tell them to reflash the software using ost
Click to expand...
Click to collapse
Thank you for the reply and hope you have given. I am in texas and travel alot for work so what i care point? Is that simply a tech company or do I need to go to them specifically? Will any others be able to do it? Is it something I can do from the nokia site?
barrnunn said:
Thank you for the reply and hope you have given. I am in texas and travel alot for work so what i care point? Is that simply a tech company or do I need to go to them specifically? Will any others be able to do it? Is it something I can do from the nokia site?
Click to expand...
Click to collapse
Google ...Nokia care centre...and find nearest representative.
Wrong place !!!
X1111 said:
Wrong place !!!
Click to expand...
Click to collapse
I get it! what can I do about it? create a duplicate over there? or wait for a moderator to move it?
slysurfer said:
Google ...Nokia care centre...and find nearest representative.
Click to expand...
Click to collapse
I googled and spoke to nokia. there are no help centers in the usa. does anyone have directions or links to reflash it myself? I saw after googling that they released a fix for the 7.1 plus that was bricking due to the update.
Unbrick Nokia 6.1 plus
barrnunn said:
I googled and spoke to nokia. there are no help centers in the usa. does anyone have directions or links to reflash it myself? I saw after googling that they released a fix for the 7.1 plus that was bricking due to the update.
Click to expand...
Click to collapse
Hi, you'll need to unlock the Bootloader first, which is not possible ( i think ) as Nokia does not allow this as yet, for most devices. On my 6.1 OEM unlocking is greyed out and Nokia just said stay tuned when I asked to get an unlock key. Can you get into Fastboot mode - hold Vol down and power ( while you have a usb connected to power / pc )??
https://www.hardreset.info/devices/nokia/nokia-61-plus/fastboot-mode/
It might be worth trying a factory reset FIRST, which could work.. follow this - https://www.hardreset.info/devices/nokia/nokia-61-plus/recovery-mode/
Let me know how you go
slysurfer said:
Hi, you'll need to unlock the Bootloader first, which is not possible ( i think ) as Nokia does not allow this as yet, for most devices. On my 6.1 OEM unlocking is greyed out and Nokia just said stay tuned when I asked to get an unlock key. Can you get into Fastboot mode - hold Vol down and power ( while you have a usb connected to power / pc )??
https://www.hardreset.info/devices/nokia/nokia-61-plus/fastboot-mode/
It might be worth trying a factory reset FIRST, which could work.. follow this - https://www.hardreset.info/devices/nokia/nokia-61-plus/recovery-mode/
Let me know how you go
Click to expand...
Click to collapse
I tried all of this in the youtube video I posted. is like it doesnt have a boot loader information on it. It seems as thought there is zero software in there excpept for the android one screen and the amount of battery life when its off. When not plugged in I get absolutely zero response from the phone, even though its 100% charged. Is there a way I can put something on a memory card and try to access it from there into boot mode, or maybe use some software to access the phones internals to install through a computer usb?
Lost
barrnunn said:
I tried all of this in the youtube video I posted. is like it doesnt have a boot loader information on it. It seems as thought there is zero software in there excpept for the android one screen and the amount of battery life when its off. When not plugged in I get absolutely zero response from the phone, even though its 100% charged. Is there a way I can put something on a memory card and try to access it from there into boot mode, or maybe use some software to access the phones internals to install through a computer usb?
Click to expand...
Click to collapse
Sorry I missed that, I thought you had to be doing something wrong. I've never been in this sort position & I've been flashing phones for years,anyway, I'm a bit lost as to what to do next. Without a care centre to help, i can not find any other way to get that phone to boot. As every method I know and have read about, requires an unlocked bootloader and or getting into download mode or the recovery. The Nokia online service tool (ost), requires an unlocked bootloader to flash firmware. Also if the PC does not recognise the phone is another issue.
I will keep looking into how to correct this issue & if I find anything, I'll let you know.
This maybe worth reading, as it may hold a solution
barrnunn said:
I tried all of this in the youtube video I posted. is like it doesnt have a boot loader information on it. It seems as thought there is zero software in there excpept for the android one screen and the amount of battery life when its off. When not plugged in I get absolutely zero response from the phone, even though its 100% charged. Is there a way I can put something on a memory card and try to access it from there into boot mode, or maybe use some software to access the phones internals to install through a computer usb?
Click to expand...
Click to collapse
I've doing some reading... https://www.getdroidtips.com/nokia-6-1-plus-stock-firmware/
and https://www.youtube.com/watch?v=DR5-x5iAEls
https://www.techmesto.com/download-nokia-online-service-tool-6-0-4-for-all-phones/
I know its not related to your device specifically, though its interesting. If we can get official OST LA software and someone's log in details, we can flash firmware to Nokia's with locked bootloaders... I'll be back in touch soon.
slysurfer said:
I've doing some reading... https://www.getdroidtips.com/nokia-6-1-plus-stock-firmware/
and https://www.youtube.com/watch?v=DR5-x5iAEls
https://www.techmesto.com/download-nokia-online-service-tool-6-0-4-for-all-phones/
I know its not related to your device specifically, though its interesting. If we can get official OST LA software and someone's log in details, we can flash firmware to Nokia's with locked bootloaders... I'll be back in touch soon.
Click to expand...
Click to collapse
Great! I have hope once again! Why doesnt this apply to my phone? They all reference the nokia x6 or 6.1 plus. I will attempt these steps and see if any success or change occurs while awaiting your response.
Fix Nokia 6.1 Plus
barrnunn said:
Great! I have hope once again! Why doesnt this apply to my phone? They all reference the nokia x6 or 6.1 plus. I will attempt these steps and see if any success or change occurs while awaiting your response.
Click to expand...
Click to collapse
I also found this tool, to flash firmware ( .nbo files ) - https://androidmtk.com/use-sut-l3-tool going to have a look for some firmware for you.
This is one option - https://forum.xda-developers.com/nokia-6-2018/help/nokia-x6-nokia-6-1-plus-global-rom-t3822657
I thought i shared a link about other models, with the same issue ( soft brick ). I was wrong.
---------- Post added at 07:05 AM ---------- Previous post was at 06:06 AM ----------
slysurfer said:
I also found this tool, to flash firmware ( .nbo files ) - https://androidmtk.com/use-sut-l3-tool going to have a look for some firmware for you.
This is one option - https://forum.xda-developers.com/nokia-6-2018/help/nokia-x6-nokia-6-1-plus-global-rom-t3822657
I thought i shared a link about other models, with the same issue ( soft brick ). I was wrong.
Click to expand...
Click to collapse
I have been reading, others are reporting, getting into recovery mode can be difficult.
When phone is on connect with USB cable to PC. Turn phone off, immediately press volume up button after this. Wait for the little Android to appear. Press power + volume down to access the recovery menu. -> this might take a few tries cause you have to be really precise, but this was the same on my Nexus 5X.
When you have time and patience, could you try to get into recovery again.
slysurfer said:
I also found this tool, to flash firmware ( .nbo files ) - https://androidmtk.com/use-sut-l3-tool going to have a look for some firmware for you.
This is one option - https://forum.xda-developers.com/nokia-6-2018/help/nokia-x6-nokia-6-1-plus-global-rom-t3822657
I thought i shared a link about other models, with the same issue ( soft brick ). I was wrong.
---------- Post added at 07:05 AM ---------- Previous post was at 06:06 AM ----------
I have been reading, others are reporting, getting into recovery mode can be difficult.
When phone is on connect with USB cable to PC. Turn phone off, immediately press volume up button after this. Wait for the little Android to appear. Press power + volume down to access the recovery menu. -> this might take a few tries cause you have to be really precise, but this was the same on my Nexus 5X.
When you have time and patience, could you try to get into recovery again.
Click to expand...
Click to collapse
I got the ost installed but I either dont have proper firmware or the phone is that bricked that it will not accept any boot. The image shows the result I get.
Does anyone have any or know of any functional firmware for this phone?
When I try to enable wifi (or bluetooth), it says 'Turning on...' underneath the icon but the process never succeeds.
Note:
-Under About > Status I see no MAC address for Wifi or Bluetooth.
-Phone is not rooted.
-Bootloader is unlocked.
-No custom recovery.
-Airplane mode is off.
-I am able to access the internet when I put in my SIM card and use my cellular data.
-EDIT: Model is listed as IN2025. The Build number is Oxygen OS 11.0.2.2.IN11AA.
-EDIT: I keep my SIM out of this phone (it's in my fully working phone). Can insert if need be.
My attempts to solve this issue (none have worked):
-I updated to OxygenOS 11.
-I booted into recovery and wiped everything, including cache. I also did a System Reset.
-I went to Settings > System > Reset Wifi, mobile and Bluetooth. I also did Erase all data (factory reset) in the same place.
Is there anything else left to try? Is there a way to flash the modem image maybe, I remember having to do that with my Nexus 4 many years ago.
Thanks!
A factory reset never finds the root cause. A virus or an old load are the only reasons to use it otherwise find the root cause. Usually a bad setting. If it's software caused the solution is right in front of you.
Network reset, worth a shot.
Clear system cache, can't hurt.
Clear data in sim card tool kit apk.
Both are probably redundant since you already did a hard reset, but try anyway.
Otherwise...
Bad sim card (try reseating it or replace otherwise) , corrupted firmware, or defective hardware.
Which phone do you have? I've seen this when a user has had a Chinese version and converted to global then when they updated to 11 it all went wrong.
If you're not using a converted Chinese phone then it could very well be your boot image. Extract it using payload then flash it.
If not that then MSM restore your current firmware.
dladz said:
Which phone do you have? I've seen this when a user has had a Chinese version and converted to global then when they updated to 11 it all went wrong.
If you're not using a converted Chinese phone then it could very well be your boot image. Extract it using payload then flash it.
If not that then MSM restore your current firmware.
Click to expand...
Click to collapse
Sorry, what is **MSM** restore?
Under About phone the Model is listed as IN2025. The Build number is Oxygen OS 11.0.2.2.IN11AA.
So I extracted all the images(?) using payload and very foolishly decided to
Code:
fastboot flash modem modem.img
The phone doesn't boot up anymore/remains stuck in loading phase (spinner...). I did a
Code:
fastboot flash boot boot.img
+ wipe + factory reset but still stuck in loading phase.
Any ideas as to how I can fix my mistake?
I appreciate all your help guys.
bassamanator said:
Sorry, what is **MSM** restore?
Under About phone the Model is listed as IN2025. The Build number is Oxygen OS 11.0.2.2.IN11AA.
So I extracted all the images(?) using payload and very foolishly decided to
Code:
fastboot flash modem modem.img
The phone doesn't boot up anymore/remains stuck in loading phase (spinner...). I did a
Code:
fastboot flash boot boot.img
+ wipe + factory reset but still stuck in loading phase.
Any ideas as to how I can fix my mistake?
I appreciate all your help guys.
Click to expand...
Click to collapse
Ah yea that's not good. 2025 AFAIK is global mainly sold in the US.
The MSM tool is in discussion I believe and it's a tool you use to restore your phone using EDL mode, to get to EDL.
Power off your phone.
Connect it to your computer (if it turns on again turn it back off)
Then open up the MSM tool and press and hold volume up and down
Your computer will recognise the the device and at this point you should start the process as it will try again to reboot shortly after without any input from you.
This is the thread you need.
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Bare in mind this will relock your bootloader but it's easy to get that back unlocked.
Any questions regarding the tool just ask in the thread.
(you shouldn't need to providing you download the right one)
Download the latest firmware within the tool. If you get stuck don't just guess, ask someone.
@dladz
So I've managed to unbrick the phone using that tool. Thanks.
I'm going to install the latest oxygenos again, extract the boot.img from that zip, and flash it again as per your recommendation.
So I flashed OnePlus8ProOxygen_15.O.32_OTA_0320. No wifi. I extracted the boot.img and then flashed it via fastboot. Still no wifi.
Anything else that I can try?
I guess this is a hardware problem?
bassamanator said:
So I flashed OnePlus8ProOxygen_15.O.32_OTA_0320. No wifi. I extracted the boot.img and then flashed it via fastboot. Still no wifi.
Anything else that I can try?
I guess this is a hardware problem?
Click to expand...
Click to collapse
But now you have bt?
blackhawk said:
But now you have bt?
Click to expand...
Click to collapse
No bluetooth either. Same exact issue as with the Wifi, it says Turning on... then it doesn't.
bassamanator said:
No bluetooth either. Same exact issue as with the Wifi, it says Turning on... then it doesn't.
Click to expand...
Click to collapse
How/when did it start? Anything happen to the phone?
bassamanator said:
@dladz
So I've managed to unbrick the phone using that tool. Thanks.
I'm going to install the latest oxygenos again, extract the boot.img from that zip, and flash it again as per your recommendation.
Click to expand...
Click to collapse
So if you've used that tool then it'll have relocked your bootloader.
Did you unlock it again? AFAIK you can't flash another boot image unless you unlock it again.
The only other thing i can recommend (if you really don't want to RMA)
Would be to downgrade to 10 but in all fairness that really shouldn't even be an option at this point, you've flashed a clean OS back as oxygen would have, you've updated via the official OTA route.
No I think it's time to contact OnePlus for an RMA.
Unless someone else had seen this issue personally I haven't.
Had you rooted in the past btw? Flashed many magisk modules??
I find it highly unlikely that they could survive this but you could potentially try the magisk removal command, can never remember it it's in my payload dumper guide.
If no one else chimes in I'd say it's an RMA, I've not seen it before, it's strange.
Also (and please don't put it on here) but is your IMEI missing too?
This could be your EFS partition if so.
Edit: found this super old thread for the OnePlus one, same issue.
I think this is fixable, potentially remotely from OnePlus and or anyone else who has access to the updated tool, might be worth mentioning in the MSM thread if you haven't already.
PS: don't follow the guide in the link btw it's for the 1+1 lol, in just putting it here as a reference
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
blackhawk said:
How/when did it start? Anything happen to the phone?
Click to expand...
Click to collapse
I got the phone used right before Christmas. It still had the protective plastic on it until I removed it today. It really is in mint condition (or looks to be). I've been away and finally got around to moving things over from my old oneplus 3T.
It's certainly possible that I bought a lemon but at this point I'd like to just fix it if I can.
bassamanator said:
I got the phone used right before Christmas. It still had the protective plastic on it until I removed it today. It really is in mint condition (or looks to be). I've been away and finally got around to moving things over from my old oneplus 3T.
It's certainly possible that I bought a lemon but at this point I'd like to just fix it if I can.
Click to expand...
Click to collapse
I think it's fixable now I really do
From what I've been reading I think it's a mixture of partitions that have been borked z namely the EFS and potentially the persist.img partition if the same position structure exists that did back in the day.
With that in mind are you able to use your fingerprint? I only ask as persist is linked to it so if that's not working then we may have a correlation between problems.
If it is then it's a ? Over the theory.
I'll keep reading but from what I can gather it seems that EFS and persist at least were linked, can't be sure if they are this point.
Have a look at that link I sent see if anything raises a flag for you, bare in mind it's for an older device
dladz said:
So if you've used that tool then it'll have relocked your bootloader.
Did you unlock it again? AFAIK you can't flash another boot image unless you unlock it again.
The only other thing i can recommend (if you really don't want to RMA)
Would be to downgrade to 10 but in all fairness that really shouldn't even be an option at this point, you've flashed a clean OS back as oxygen would have, you've updated via the official OTA route.
No I think it's time to contact OnePlus for an RMA.
Unless someone else had seen this issue personally I haven't.
Had you rooted in the past btw? Flashed many magisk modules??
I find it highly unlikely that they could survive this but you could potentially try the magisk removal command, can never remember it it's in my payload dumper guide.
If no one else chimes in I'd say it's an RMA, I've not seen it before, it's strange.
Also (and please don't put it on here) but is your IMEI missing too?
This could be your EFS partition if so.
Edit: found this super old thread for the OnePlus one, same issue.
I think this is fixable, potentially remotely from OnePlus and or anyone else who has access to the updated tool, might be worth mentioning in the MSM thread if you haven't already.
PS: don't follow the guide in the link btw it's for the 1+1 lol, in just putting it here as a reference
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
Click to expand...
Click to collapse
Yes I had to oem unlock again.
As far as I know the phone was not rooted but it's a used phone. Superficially it's in mint condition, I just removed the plastic film just earlier. I'll post in the MSM thread and checkout the new one you posted.
EDIT: the phone has 2 IMEI numbers.
bassamanator said:
Yes I had to oem unlock again.
As far as I know the phone was not rooted but it's a used phone. Superficially it's in mint condition, I just removed the plastic film just earlier. I'll post in the MSM thread and checkout the new one you posted.
Click to expand...
Click to collapse
I've already posted in the MSM thread for you.
What about your fingerprint? Is that still working?
dladz said:
I think it's fixable now I really do
From what I've been reading I think it's a mixture of partitions that have been borked z namely the EFS and potentially the persist.img partition if the same position structure exists that did back in the day.
With that in mind are you able to use your fingerprint? I only ask as persist is linked to it so if that's not working then we may have a correlation between problems.
If it is then it's a ? Over the theory.
I'll keep reading but from what I can gather it seems that EFS and persist at least were linked, can't be sure if they are this point.
Have a look at that link I sent see if anything raises a flag for you, bare in mind it's for an older device
Click to expand...
Click to collapse
So I've never registered my fingerprint on a smartphone, ever, but I thought I would register one of my toes just to figure this thing out. When I get to the Fingerprint Setup screen I get the following error: Enrollment was not completed. Fingerprint registration error, please try again.
Does this help narrow down the issue?
bassamanator said:
So I've never registered my fingerprint on a smartphone, ever, but I thought I would register one of my toes just to figure this thing out. When I get to the Fingerprint Setup screen I get the following error: Enrollment was not completed. Fingerprint registration error, please try again.
Does this help narrow down the issue?
Click to expand...
Click to collapse
Yea for me it does, it shows there's a correlation between the persist problem and the EFS problem and a direct connection to your IMEI or Mac address issue.
With this in mind I would recommend the persist.img fix thread..
Getting that working may be key to solving the Mac / IMEI problem.
At this point nothing is going to hurt.
Here is the thread you'll need.
[GUIDE] Fix PERSIST.IMG Loss Of Finger Print Sensor
New video guide below VIDEO GUIDE 1. *VERY IMPORTANT* We need to back up your broken persist.img and store it in a safe place. PC preferred. We will need this later. Do not leave the backup on the device as the next step will wipe the device...
forum.xda-developers.com
Now I have not been through this but again it can't hurt at this point.
dladz said:
Here is the thread you'll need.
[GUIDE] Fix PERSIST.IMG Loss Of Finger Print Sensor
New video guide below VIDEO GUIDE 1. *VERY IMPORTANT* We need to back up your broken persist.img and store it in a safe place. PC preferred. We will need this later. Do not leave the backup on the device as the next step will wipe the device...
forum.xda-developers.com
Now I have not been through this but again it can't hurt at this point.
Click to expand...
Click to collapse
I was about to say, I want to try something along the lines of
fastboot erase modemst1
fastboot erase modemst2
fastboot erase persist
Click to expand...
Click to collapse
or something along those lines from this post https://forums.oneplus.com/threads/no-imei-and-no-efs-backup.322534/page-4#post-14545355 on that old oneplus forum thread you posted.
I'll try the new link you posted instead though.
IMEI is fine btw, the phone dials and connects just fine to cellular.
bassamanator said:
I was about to say, I want to try something along the lines of or something along those lines from this post https://forums.oneplus.com/threads/no-imei-and-no-efs-backup.322534/page-4#post-14545355 on that old oneplus forum thread you posted.
I'll try the new link you posted instead though.
IMEI is fine btw, the phone dials and connects just fine to cellular.
Click to expand...
Click to collapse
Ok don't do the EFS fix you do not have an EFS back up.
Give this a shot
go to data/misc/wifi (required root)
-backup file wpa_supplicant.conf in this folder which contains usename and password wifi
- delete all file in this folder
- turn on wifi ( if you careful, you can reboot )
- now you can connect to wifi
- recovery file wpa_supplicant.conf
This isn't my writing. The English is a little broken but you get the point