Related
My OnePlus One just went screwy on me and so I tried to do a reset with TWRP. The factory reset didn't work. The phone is in a bootloop as the loading screen stays on and that's it. I noticed in recovery that the " /persist" file could not be mounted so I figure it's corrupted. The problem is this: NO drivers can be loaded and my phone will not be recognized in device manager, OPO toolkit, or any other means! This thing is bricked!! I tried ADB, Google, Samsung, and Universal drivers to no effect. I just don't know how I can get my phone recognized again. It did at one point come up as QSHub or something like that but I can't even get that now. Fastboot mode comes on my phone but does nothing and the MTP USB device driver will not install! I don't know what to do and just wasted 6 hours trying to figure this out! I am not very savvy with phones when it comes to this sort of thing. I can root a phone but that's as far as I can go comfortably. If someone has a solution to this problem, please advise me but you may have to hand hold me through it as I am not really up on how to do things the way they may have to be done. Thanks!
Your phone isn't bricked. Are you making sure that you reboot your PC after each uninstall and install of any drivers?
XDA Moderator
Transmitted via Bacon
Yes, I rebooted after installation of any drivers. It didn't make any difference as my phone still wasn't recognized by my computer.
Alright, maybe try this:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
XDA Moderator
Transmitted via Bacon
Well, my phone is recognized when I type "fastboot devices" but I do not know where to go from here. I got the device to be recognized using info from http://forum.xda-developers.com/show....php?t=2839471. According to your guidelines in [GUIDE] [UNBRICK] Unbrick Oneplus One, I am soft bricked, it would seem. What should my next step be? I tried to unlock the bootloader but it gives me this in the CMD window.
C:\Users\Se7en\Desktop\MTP>fastboot devices
5e1c4e77 fastboot
C:\Users\Se7en\Desktop\MTP>fastboot oem unlock
...
OKAY [ 0.020s]
finished. total time: 0.020s
C:\Users\Se7en\Desktop\MTP>fastboot oem device-in
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.005s]
finished. total time: 0.005s
So what is the next step to get this thing working? Am I heading in the right direction or am I getting ahead of myself?
Thanks in advance for any help
kristorm said:
Well, my phone is recognized when I type "fastboot devices" but I do not know where to go from here. I got the device to be recognized using info from http://forum.xda-developers.com/show....php?t=2839471. According to your guidelines in [GUIDE] [UNBRICK] Unbrick Oneplus One, I am soft bricked, it would seem. What should my next step be? I tried to unlock the bootloader but it gives me this in the CMD window.
C:\Users\Se7en\Desktop\MTP>fastboot devices
5e1c4e77 fastboot
C:\Users\Se7en\Desktop\MTP>fastboot oem unlock
...
OKAY [ 0.020s]
finished. total time: 0.020s
C:\Users\Se7en\Desktop\MTP>fastboot oem device-in
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.005s]
finished. total time: 0.005s
So what is the next step to get this thing working? Am I heading in the right direction or am I getting ahead of myself?
Thanks in advance for any help
Click to expand...
Click to collapse
If you've got fastboot working you're on your way. Your bootloader doesn't seem to be unlocking though, did you relock it at some point? If so, why? As long as you still have TWRP installed you can flash a token to unlock it again (this won't wipe your data). You'll find it in this thread:
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
So just flash that and your bootloader will unlock. Then download this:
https://docs.google.com/file/d/0B98G0KTJwnBFUnJCNldodGs2dE0/edit?usp=docslist_api
Put it in your fastboot folder on your PC, put your phone in fastboot mode and connect it to your PC, then issue these commands:
Code:
fastboot erase persist
fastboot flash persist persist.img
XDA Moderator
Transmitted via Bacon
Heisenberg said:
If you've got fastboot working you're on your way. Your bootloader doesn't seem to be unlocking though, did you relock it at some point? If so, why? As long as you still have TWRP installed you can flash a token to unlock it again (this won't wipe your data). You'll find it in this thread:
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
So just flash that and your bootloader will unlock. Then download this:
https://docs.google.com/file/d/0B98G0KTJwnBFUnJCNldodGs2dE0/edit?usp=docslist_api
Put it in your fastboot folder on your PC, put your phone in fastboot mode and connect it to your PC, then issue these commands:
Code:
fastboot erase persist
fastboot flash persist persist.img
XDA Moderator
Transmitted via Bacon
Click to expand...
Click to collapse
I didn't relock it, at least I didn't set out to intentionally lock it. Through my experimentation to get this phone running again, it is very possible that I may have. I'll try the info you gave me and let you know. Thanks very much!
Sorry for being a noob but do I unzip the Bootunlocker.zip file you directed me to or leave it as is? Secondly, what is the exact procedure to flash this with TWRP? I just don't want to make any mistakes as this is all new to me. Thanks!
kristorm said:
Sorry for being a noob but do I unzip the Bootunlocker.zip file you directed me to or leave it as is? Secondly, what is the exact procedure to flash this with TWRP? I just don't want to make any mistakes as this is all new to me. Thanks!
Click to expand...
Click to collapse
Don't unzip it, just transfer it to your phone, then go to the install menu in TWRP and find the zip on your phone and swipe tip install.
XDA Moderator
Transmitted via Bacon
There's the problem: My phone isn't being recognized in Windows so I cannot transfer anything to it. How can that be remedied? The driver software for QHSUSB cannot be found and MTP device fails to install all the time!
EDIT: I think I got it! I changed the USB ADB interface driver and it recognized my phone as "One". I can now follow your instructions. I will keep you posted.
IT FREAKING WORKED!!! I am sooooo happy right now. Thank you so much!!! You can't believe how grateful I am for your help with this! Fantastic! This is awesome!! I sent you a small token of my appreciation
kristorm said:
IT FREAKING WORKED!!! I am sooooo happy right now. Thank you so much!!! You can't believe how grateful I am for your help with this! Fantastic! This is awesome!!
Click to expand...
Click to collapse
Awesome, I'm very glad to see it worked! You're welcome, happy to help.
XDA Moderator
Transmitted via Bacon
The only thing I can see right now is that I do not have a keyboard. How do I get that back?
kristorm said:
The only thing I can see right now is that I do not have a keyboard. How do I get that back?
Click to expand...
Click to collapse
You don't have a keyboard at all? Haven't seen that before. So there's no keyboard at all showing up when you go into Settings/Language & Input?
XDA Moderator
Transmitted via Bacon
I guess this process wiped all my data because it's asking me to set up my accounts again. However, when I go try to input anything, I only have Google voice and no keyboard. Sometimes I see a keyboard icon but it doesn't respond when I touch it. If I could access my settings, I'm sure I could change things but obviously, I can't at this point.
kristorm said:
I guess this process wiped all my data because it's asking me to set up my accounts again. However, when I go try to input anything, I only have Google voice and no keyboard. Sometimes I see a keyboard icon but it doesn't respond when I touch it. If I could access my settings, I'm sure I could change things but obviously, I can't at this point.
Click to expand...
Click to collapse
What you could do is access the Play Store on your PC and find a free keyboard to install, press the install button in the web browser on your PC and it'll download the keyboard to your phone.
XDA Moderator
Transmitted via Bacon
Great idea. I'll do just that. Thanks!
It doesn't work. The keyboard file isn't being pushed to my phone. SUX! Cannot root either as OPO toolkit says no ADB device detected (debugging on). Also, the log from OPOTK says that my device is unauthorized.
Here's the log:
Information: Checking ADB Status
adb devices
List of devices attached
5e1c4e77 unauthorized
Any thoughts to any of these things mentioned?
kristorm said:
It doesn't work. The keyboard file isn't being pushed to my phone. SUX!
Click to expand...
Click to collapse
Bummer. It might be time to start from scratch. Go to my guide and follow section 8 to flash the stock images with fastboot, just don't flash the userdata image or you'll wipe your internal storage.
http://forum.xda-developers.com/showthread.php?t=2839471
XDA Moderator
Transmitted via Bacon
kristorm said:
It doesn't work. The keyboard file isn't being pushed to my phone. SUX! Cannot root either as OPO toolkit says no ADB device detected (debugging on). Also, the log from OPOTK says that my device is unauthorized.
Here's the log:
Information: Checking ADB Status
adb devices
List of devices attached
5e1c4e77 unauthorized
Any thoughts to any of these things mentioned?
Click to expand...
Click to collapse
Get rid of the toolkit, it really isn't needed for this phone, and they cause more problems than they're worth. If you want to root all you need to do is download the SuperSU zip to your phone and install it with TWRP. I'd suggest flashing the stock images as I've described above though.
XDA Moderator
Transmitted via Bacon
as the title states my device is a pixel 2 walleye android 10 since i got it iv never had a sim in it (i recently tried a virgin sim and it works in the device )but oem unlock stays greyed out i tried every command i could think of in cmd but alas i got nothing i did get a "download mode" to show up in my bootloader but if i boot to it i get an error in yellow at the bottom and none of the commands in cmd work im just trying to oem unlock can anyone help me or is there a place i can trade this garbage to get something worth my time
bootloader is mw8998-002.0079.00
i ran the command fastboot oem device-info and the info i got is
c:\adb>fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
OKAY [ 0.004s]
Finished. Total time: 0.005s
the device is a google edition as far as i knew and it says critical is unlocked tried running the flashall.bat with a stock rom realized i needed oem unlocking for that so that was a no go is there anyone out there in this world that can help
same issue, did you find a solution ?
zouzouille-arie said:
same issue, did you find a solution ?
Click to expand...
Click to collapse
I found out the verison left that unlocked for upgrading the bootloader via registered vw equipment the only way is to rma the **** outta it until they mistakenly send you an unlocked version I did till they fixed
Hi guys, so I recently discovered you can use test point mode on my phone through DC Phoenix to then use HCU to unlock your bootloader and root and flash custom roms etc.
So after unlocking the bootloader which gave a success message. My phone proceeded to reboot into erecovery as there was some red text etc warning me about the system not being verified or trusted or something.
Now i started to download latest software to install through recovery but decided to stop it as i had already downloaded a firmware file 8.1 in full to flash. So i started that. And after flashing the erecovery files it rebooted me into upgrade mode (as it should) but it failed then after a few seconds and then the phone went black screen. I've now only got access to fastboot mode and nothing else. PC picks up the device in FB mode but cant issue any commands. They fail saying remote: failed. So I cannot flash any more files albeit system.img etc.
I have heard of the dload method but i cant seem to get it to work phone just doesnt boot up and start installing or anything.
Worth mentioning I have logs of everything i can post here.
The log from the "Successful" bootloader unlock via HCU: (it relocked after reboot) FRP too I think.
I have also replaced the endings of the imei listings etc with XXXX just as habit. I dont wanan post my IMEI etc online. Call it paranoia lol
25/01/2021 22:49:23
HCU Client v1.0.0.0372
Account: shortyzsly
Before operation turn phone to TestPoint mode:
Turn off phone, then short TestPoint on phone pcb
and plug USB cable
Wait for device "HUAWEI USB COM 1.0" in Ports
Read phone info
2021-01-25 22:49:23.140 Selected Cpu/Bootloader - Kirin970_T1_A8.1_V6
2021-01-25 22:49:23.142 Connecting to server...
2021-01-25 22:49:23.358 Connected!
2021-01-25 22:49:23.939 Find device COM3, handle 9956
BOOTLOADER selected to update:Kirin970_T1_A8.1_V6
2021-01-25 22:49:24.247 Downloading bootloader...
FILE TO download: Kirin970_T1_A8.1_V6_3.dtwork
downloading file Kirin970_T1_A8.1_V6_3.dtwork...
2021-01-25 22:49:26.501 Success
FILE TO download: Kirin970_T1_A8.1_V6_4.dtwork
downloading file Kirin970_T1_A8.1_V6_4.dtwork...
2021-01-25 22:49:27.671 Success
FILE TO download: Kirin970_T1_A8.1_V6_5.dtwork
downloading file Kirin970_T1_A8.1_V6_5.dtwork...
2021-01-25 22:50:22.279 Success
2021-01-25 22:50:22.286 Bootloader write success!
2021-01-25 22:50:22.288 Waiting for device REMOVAL/INSERTION...
2021-01-25 22:50:28.903 Device ready!
2021-01-25 22:50:28.983 Found device in fastboot mode!
2021-01-25 22:50:28.987 Reading info...
2021-01-25 22:50:33.024 Done!
Fastboot provided info:
CPU: kirin970
Model: CLT-L09
Firmware: CLT-L09 9.1.0.372(C782E12R1P11)
Vendor: hw
Country: eu
SN: LCL021XXXXXXXXX
PCB SN: 025DGTXXXXXX
WIFI MAC: 8811XXXXXX
BT MAC: 8811XXXXXXX
Theme color: black
Device color: black
FBLOCK: 1
Bootloader FB lock: unlocked
Bootloader User lock: locked
Found signed IMEI:
IMEI1: 867259XXXXXXXX
IMEI2: 867259XXXXXXXX
SIM NW_LOCK status: UNLOCKED
Found NV data:
Modems: 3
IMEI1: 86725XXXXXXXXX
IMEI2: 86725XXXXXXXXX
IMEI3: 000000000000000
PESN: 8022XXXX
MEID: A0000093XXXXX
Found OEM data:
Model: CLT-L09
Firmware: CLT-L09 9.0.0.168(C782E3R1P9)
Rescue: rescue:Chipset-boston 8.1.0.001(01FL)
Vendor: hw
Country: eu
Version limitation: ON
SIMCARDMODE: single
Bootloader User lock: locked
Click to expand...
Click to collapse
25/01/2021 22:52:35
HCU Client v1.0.0.0372
Account: shortyzsly
Before operation turn phone to TestPoint mode:
Turn off phone, then short TestPoint on phone pcb
and plug USB cable
Wait for device "HUAWEI USB COM 1.0" in Ports
Repair
New FB User Lock : UNLOCKED
New downgrade/customization limitations : UNLOCKED
Selected Cpu/Bootloader - Kirin970_T1_A8.1_V6
2021-01-25 22:52:36.442 Connecting to server...
2021-01-25 22:52:36.708 Connected!
2021-01-25 22:52:37.330 HUAWEI device in Test Point mode Not found!
2021-01-25 22:52:37.402 Reading info...
2021-01-25 22:52:41.275 Done!
Fastboot provided info:
CPU: kirin970
Model: CLT-L09
Firmware: CLT-L09 9.1.0.372(C782E12R1P11)
Vendor: hw
Country: eu
SN: LCL0218717XXXX
PCB SN: 025DGT187D00XXX
WIFI MAC: 88119XXXX
BT MAC: 8811966XXXX
Theme color: black
Device color: black
FBLOCK: 1
Bootloader FB lock: unlocked
Bootloader User lock: locked
Found signed IMEI:
IMEI1: 8672590XXXXX
IMEI2: 8672590XXXXX
SIM NW_LOCK status: UNLOCKED
Found NV data:
Modems: 3
IMEI1: 86725903XXXXXX
IMEI2: 867259035XXXXX
IMEI3: 000000000000000
PESN: 80221B5B
MEID: A00000934BCC82
Found OEM data:
Model: CLT-L09
Firmware: CLT-L09 9.0.0.168(C782E3R1P9)
Rescue: rescue:Chipset-boston 8.1.0.001(01FL)
Vendor: hw
Country: eu
Version limitation: ON
SIMCARDMODE: single
Bootloader User lock: locked
Phone ID: 80A0E6XXXXXXXX
2021-01-25 22:52:45.590 Repairing...
2021-01-25 22:52:45.598 Write FB User lock not supported for this model, skipped!
2021-01-25 22:52:45.611 Write partition oeminfo...
2021-01-25 22:52:47.468 Write partition oeminfo success!
2021-01-25 22:52:47.494 Unlocking restrictions...
2021-01-25 22:52:47.511 Unlock restrictions success!
2021-01-25 22:52:47.514 Done!
Click to expand...
Click to collapse
Basically what I wanna know is, is she dead and gone or can she be saved?
As it turns out, I think it may be an issue with the loader I may have tried to flash 8.1 and it was on 9.1. Any help when you get a chance anyone who's has the same issue. I searched the forums can't find my exact issue.
Hello everybody,
i'm not new in custom roms, but i have a problem, i can't solve by myself:
I flashed an unlocked Mi5 to linageos 19.1 without problems.
I had the bad idea to relock the bootloader due to security reasons (fastboot oem lock).
Now the device is not booting anymore, i can just see the Mi-Logo flashing very shortly.
I can access fastboot, but can't boot into recovery.
I tried to unlock the device again, but the Mi Unlocker fails and prompts me to go to the developer options in Miui, which is clearly impossible.
Any chance to proceed from fastboot (fastboot oem unlock does not work...) ?
Thanks, Jan
congrats, you succesfully hard bricked your phone. please take it for a walk to the xiaomi service and pay for gettting it fixed. who told you it is a good idea to relock the bootloader with a custom rom installed ?
Fytdyh said:
congrats, you succesfully hard bricked your phone. please take it for a walk to the xiaomi service and pay for gettting it fixed. who told you it is a good idea to relock the bootloader with a custom rom installed ?
Click to expand...
Click to collapse
actually, i remember some banking apps complained about the locked bootloader. I thought i can lock/unlock it in fastboot mode, but looks like i was wrong.
I will give the MiFlash Tool a chance, but i have not much hope...
@Fytdyh: do you think, Xiaomi Service can fix it ?
jever2k said:
actually, i remember some banking apps complained about the locked bootloader. I thought i can lock/unlock it in fastboot mode, but looks like i was wrong.
I will give the MiFlash Tool a chance, but i have not much hope...
@Fytdyh: do you think, Xiaomi Service can fix it ?
Click to expand...
Click to collapse
Make sure if your bootloader is really locked or not using fastboot command
fastboot oem device-info
OR,
fastboot getvar unlocked
If it's not locked, you can simply flash your stock rom using flash tool available for mi. Before downloading a rom from internet, take note of your device info using fastboot command ,
fastboot getvar all
And if bootloader is really locked, you have to flash stock rom from EDL mode. You may have to remove back cover to turn on EDL mode. Your device has snapdragon chipset (Plus point). Watch tutorials about xiaomi edl rom flash - snapdragon. You can go to service centre. If they tell you that you have to replace motherboard, don't be agree. Tell them to flash rom using EDL mode.
Tawsif999 said:
Make sure if your bootloader is really locked or not using fastboot command
fastboot oem device-info
OR,
fastboot getvar unlocked
If it's not locked, you can simply flash your stock rom using flash tool available for mi. Before downloading a rom from internet, take note of your device info using fastboot command ,
fastboot getvar all
And if bootloader is really locked, you have to flash stock rom from EDL mode. You may have to remove back cover to turn on EDL mode. Your device has snapdragon chipset (Plus point). Watch tutorials about xiaomi edl rom flash - snapdragon. You can go to service centre. If they tell you that you have to replace motherboard, don't be agree. Tell them to flash rom using EDL mode.
Click to expand...
Click to collapse
looks like i am getting closer... located the two EDL points to short during PC connection, installed the Qualcomm serial driver. For a second i see the device appearing as COM6 but then it disappears again and is not availiable anymore.
Any hints ?
Thanks again, Jan
jever2k said:
looks like i am getting closer... located the two EDL points to short during PC connection, installed the Qualcomm serial driver. For a second i see the device appearing as COM6 but then it disappears again and is not availiable anymore.
Any hints ?
Thanks again, Jan
Click to expand...
Click to collapse
Try this to solve the issue.
If it doesn’t help, read this to boot properly into edl
jever2k said:
Hello everybody,
i'm not new in custom roms, but i have a problem, i can't solve by myself:
I flashed an unlocked Mi5 to linageos 19.1 without problems.
I had the bad idea to relock the bootloader due to security reasons (fastboot oem lock).
Now the device is not booting anymore, i can just see the Mi-Logo flashing very shortly.
I can access fastboot, but can't boot into recovery.
I tried to unlock the device again, but the Mi Unlocker fails and prompts me to go to the developer options in Miui, which is clearly impossible.
Any chance to proceed from fastboot (fastboot oem unlock does not work...) ?
Thanks, Jan
Click to expand...
Click to collapse
Flash stock recovery for your device via fastboot, then you should be able to boot into recovery or flash a stock system.img or your full stock firmware for your device, then unlock the bootloader(fastboot oem unlock) then flash TWRP and LineageOS again.
Droidriven said:
Flash stock recovery for your device via fastboot, then you should be able to boot into recovery or flash a stock system.img or your full stock firmware for your device, then unlock the bootloader(fastboot oem unlock) then flash TWRP and LineageOS again.
Click to expand...
Click to collapse
But he mentioned, bootloader fails to unlock. Actually it's hard brick(Even though he can boot into fastboot,the bootloader is locked. So nothing to do with fastboot).Without unlocked bootloader, flashing something from fastboot will hard brick his device completely (Will not be able to boot into fastboot). Or flashing will be denied
Tawsif999 said:
Try this to solve the issue.
If it doesn’t help, read this to boot properly into edl
Click to expand...
Click to collapse
OK, next level reached. The phone is connected to the com-port and the correct driver is displayed.
The whole procedure is a bit unstable, i need to connect the phone several times, to get a stable EDL mode.
The Xiaomi Flasher recognizes the phone, but flashing does not succeed. Sometimes it's not able to receive a kind of Hello message, sometimes it displays "object reference not set to an instance of an object".
I also downloaded the QPST flasher, but have no plan, how to use it.
I'll keep on trying!
Thanks to all, who helped me to reach this point!
jever2k said:
OK, next level reached. The phone is connected to the com-port and the correct driver is displayed.
The whole prcedure is a bit unstable, i need to connect the phone several times, to get a stable EDL mode.
The Xiaomi Flasher recognizes the phone, but flashing does not succeed. Sometimes it's not able to receive a kind of Hello message, sometimes it displays "object reference not set to an instance of an object".
I also downloaded the QPST flasher, but have no plan, how to use it.
I'll keep on trying!
Thanks to all, who helped me to reach this point!
Click to expand...
Click to collapse
I found something new by watching this video. Maybe you don't understand hindi(India is our relative country, so I do).
Lemme explain,
This guy's xiaomi k20 pro phone hard bricked with a locked bootloader. He tried a lot to repair it(by deep flash or something idk). But everything failed. At last he came to this step of EDL mode. But xiaomi Edl mode flash requires an "AUTHORIZED MI ACCOUNT" . Xiaomi people pay to get authorized account license that normal users don't have. So the guy contacted with them on a telegram page called "Mod Edit: Name Removed" . They told him that they will repair his phone via teamviewer. All he had to do is pay some $ & connect phone in edl mode. Rest of the things were done by them. And his phone repaired successfully! (Watch the video from 4:00)
So In his video, he is telling to go to that page & contact with "Mod Edit: Name Removed" there. They take 20-25$ (depends on device). If you tell them you're from Mod Edit: Name Removed's video, they will give some discount
Tawsif999 said:
But he mentioned, bootloader fails to unlock. Actually it's hard brick(Even though he can boot into fastboot,the bootloader is locked. So nothing to do with fastboot).Without unlocked bootloader, flashing psomething from fastboot will hard brick his device completely (Will not be able to boot into fastboot). Or flashing will be denied
Click to expand...
Click to collapse
Yeah, I jumped the gun and posted before seeing all the replies in the thread describing their whole scenario, should've known better.
They obviously need a hardware approach, i.e. JTAG/RIFF/Octoplus or replace motherboard.
Tawsif999 said:
I found something new by watching this video. Maybe you don't understand hindi(India is our relative country, so I do).
Lemme explain,
This guy's xiaomi k20 pro phone hard bricked with a locked bootloader. He tried a lot to repair it(by deep flash or something idk). But everything failed. At last he came to this step of EDL mode. But xiaomi Edl mode flash requires an "AUTHORIZED MI ACCOUNT" . Xiaomi people pay to get authorized account license that normal users don't have. So the guy contacted with them on a telegram page called "Mod Edit: Name Removed" . They told him that they will repair his phone via teamviewer. All he had to do is pay some $ & connect phone in edl mode. Rest of the things were done by them. And his phone repaired successfully! (Watch the video from 4:00)
So In his video, he is telling to go to that page & contact with "Mod Edit: Name Removed" there. They take 20-25$ (depends on device). If you tell them you're from Mod Edit: Name Removed's video, they will give some discount
Click to expand...
Click to collapse
Thanks for research!
Meanwhile, i stopped using Windows due to all the caveats and switched to reliable Debian Linux on a different machine.
Again it takes 10 attempts to get into EDL Mode.
I used qdl (Qualcomm downloader for Linux) with all the firehose, raw and patch .xmls
Code:
sudo ./qdl --debug --storage ufs --include . prog_ufs_firehose_8996_ddr.elf partition.xml rawprogram0.xml rawprogram1.xml rawprogram2.xml rawprogram3.xml rawprogram4.xml rawprogram5.xml patch0.xml patch1.xml patch2.xml patch3.xml patch4.xml patch5.xml
Output looked like some stuff was written, at the end i receive:
Code:
qdl: failed to write: Connection timed out
However, the phone is now dead as can be without fastboot working any more.
Maybe i'll give it another try, or get a used Mainboard...
Best regards, Jan
jever2k said:
Thanks for research!
Meanwhile, i stopped using Windows due to all the caveats and switched to reliable Debian Linux on a different machine.
Again it takes 10 attempts to get into EDL Mode.
I used qdl (Qualcomm downloader for Linux) with all the firehose, raw and patch .xmls
Code:
sudo ./qdl --debug --storage ufs --include . prog_ufs_firehose_8996_ddr.elf partition.xml rawprogram0.xml rawprogram1.xml rawprogram2.xml rawprogram3.xml rawprogram4.xml rawprogram5.xml patch0.xml patch1.xml patch2.xml patch3.xml patch4.xml patch5.xml
Output looked like some stuff was written, at the end i receive:
Code:
qdl: failed to write: Connection timed out
However, the phone is now dead as can be without fastboot working any more.
Maybe i'll give it another try, or get a used Mainboard...
Best regards, Jan
Click to expand...
Click to collapse
jever2k said:
Thanks for research!
Meanwhile, i stopped using Windows due to all the caveats and switched to reliable Debian Linux on a different machine.
Again it takes 10 attempts to get into EDL Mode.
I used qdl (Qualcomm downloader for Linux) with all the firehose, raw and patch .xmls
Code:
sudo ./qdl --debug --storage ufs --include . prog_ufs_firehose_8996_ddr.elf partition.xml rawprogram0.xml rawprogram1.xml rawprogram2.xml rawprogram3.xml rawprogram4.xml rawprogram5.xml patch0.xml patch1.xml patch2.xml patch3.xml patch4.xml patch5.xml
Output looked like some stuff was written, at the end i receive:
Code:
qdl: failed to write: Connection timed out
However, the phone is now dead as can be without fastboot working any more.
Maybe i'll give it another try, or get a used Mainboard...
Best regards, Jan
Click to expand...
Click to collapse
That's expensive. Anyway, it will be better if you don’t waste time on this. Just go for 3rd party help(From that official telegram channel or service centre). That will cost less
Tawsif999 said:
That's expensive. Anyway, it will be better if you don’t waste time on this. Just go for 3rd party help(From that official telegram channel or service centre). That will cost less
Click to expand...
Click to collapse
Thanks Tawsif for the good hints and links.
I don't really depend on the phone, so i will keep trying.
It's not wasted time, it's mainly learning new stuff and improving skills.
I believe, i'm not too far away and if it works, it's the best satisfaction.
If not, i bricked an old Mi 5.
All the best,
Jan
Hey guys a long time ago i tried to relock my bootloader and i did it but when i tried to boot the phone on again it gave me an error saying "No OS system could be found your device will not boot" I have tried flashing everything but the phone says "flashing_locked" and i cant unlock the bootloader again because the OEM option turned off on its own, Is there a way to force flash or force the OEM option on?
Imparel said:
Hey guys a long time ago i tried to relock my bootloader and i did it but when i tried to boot the phone on again it gave me an error saying "No OS system could be found your device will not boot" I have tried flashing everything but the phone says "flashing_locked" and i cant unlock the bootloader again because the OEM option turned off on its own, Is there a way to force flash or force the OEM option on?
Click to expand...
Click to collapse
Unfortunately there's no way to save the device in this situation, hopefully you can RMA or have it replaced.
If support asks tell them it won't boot after the device updated itself. Many carriers fail to check if the device was bootloader unlocked and just wait for your admission of guilt.
__
Some extra information:
I wouldn't recommend ever relocking bootloader due to this happening quite frequently.
If you feel like you really have to try:
The only method with the least amount of risk is using LSMA tool from Motorola site(rescue and recovery assistant) to install stock before hand.
That method has highest success rate.
try Rescue and Smart Assistant Tool below
Rescue and Smart Assistant Tool - Motorola
<h6><span style="color:#FFFFFF"><strong>Our Rescue and Smart Assistant tool</strong><br />can help diagnose and resolve issues on your<br />Motorola phone or Lenovo phone/tablet.</span></h6>
www.motorola.com
Issue with relocking bootloader is..
oem_locked accepts signed Motorola firmware
Once you relock bootloader it becomes
Flashing_locked which accepts no flash commands.
Afaik there is no way to restore oem_locked
If the device can't be returned or exchanged I did see that this device is on supported list for moto-key it's a rather expensive service (60usd) but cheaper than buying a new device.
Imparel said:
Hey guys a long time ago i tried to relock my bootloader and i did it but when i tried to boot the phone on again it gave me an error saying "No OS system could be found your device will not boot" I have tried flashing everything but the phone says "flashing_locked" and i cant unlock the bootloader again because the OEM option turned off on its own, Is there a way to force flash or force the OEM option on?
Click to expand...
Click to collapse
Telegram: @flashing_locked
Jhon ti said:
Telegram: @flashing_locked
Click to expand...
Click to collapse
Omg he saved my life for a small amount best money I ever spent
SyberHexen said:
Issue with relocking bootloader is..
oem_locked accepts signed Motorola firmware
Once you relock bootloader it becomes
Flashing_locked which accepts no flash commands.
Afaik there is no way to restore oem_locked
If the device can't be returned or exchanged I did see that this device is on supported list for moto-key it's a rather expensive service (60usd) but cheaper than buying a new device.
Click to expand...
Click to collapse
Could you explain to me in more detail how that moto key thing works? From what I know I re locked my boot loader and the /system is corrupted so it’s stuck in fastboot but the Motorola recovery service doesn’t work