Related
Apparently sometimes it's not the best idea to use the flashing software that the manufacturer of your phone released.
I have a Wiko Lenny(technically a MediaTek MT6572) that has(or had - now it's dead) the habit of simply rebooting into a bootloop every few months. Fixing that was simple; just start SP Flash Tool, format everything then flash the stock ROM back. Last time I did that was around 4 months ago, and since then I have upgraded to Windows 10, and as such, lost the tools I had installed.
Yesterday it went into a bootloop again. I didn't remember exactly what tools I used, so I assumed they were the tools that Wiko supplied a while back with the V10 ROM. Well, they weren't. I still thought I'd give them a try. I mean, it's from the manufacturer's site, so they must work even better that the ones I was using.
I was wrong. The tool flashed the ROM "successfully", but the only thing it actually succeeded to do is corrupt the preloader. For those who don't know, corrupting the preloader basically means the phone won't even power on(not boot, actually power on), won't charge, and the PC won't detect anything if you connect the phone. Practically, it's the hardest brick a phone can get.
The fastest way to fix that is by either using a JTAG connection to flash everything manually, or by entering something called the Mediatek META mode(don't quote me on this one, though - I never heard of it before). JTAG - well I don't have the tools or expertise necessary to do that(although I'd love to learn how to do it - if anyone can point me to a well-written guide or two about that, please do!), and I simply can't get the phone to enter the META mode.
Is JTAG the only way to do it? Is META mode just a myth? Is there a way to save my phone, or should I just say "RIP" and buy a new one(I have the money for a Samsung Galaxy A3, the new one, but I was planning to buy a new computer with that money - is it worth it?)?
TL;DR (It's not that long but anyway...):
I have a Wiko Lenny(Mediatek MT6572) with a corrupted preloader after I flashed it with Wiko's tool. Can I repair it or should I just buy a new phone?
Link to the culprit that killed my phone(AKA Wiko V10 ROM): https://docs.google.com/uc?id=0BzeAvoIC2yhHMTZESUU1Y3hUM0E
Come on people, let's fix this little guy.
EDIT: Please, just tell me what your ideas are... A tip, a crazy idea, some details about MTK devices that could help, anything is appreciated.
Please...
Looks like I'm getting the 10 posts just by begging people to say something... :crying:
I have an MTK phone and its always going wrong and not booting/turning on because I mess with it and break it
I'm sure I flash the backup I made in mtktools with spflash, and plug the phone in with no battery attached, I also have to use windows 7 on a dual boot as windows 10 never played ball properly. You also need the mtk VCOM driver installed, not just adb and normal drivers. If you have all these, and have tried them, then that is the end of my knowledge sadly. Only other thing is going to needrom and seeing if they have a full rom/backup with partition tables/preloader etc.
Also, had to try a few versions of sptools as certain versions didnt work, forget which one I have and which didnt work. And also had to use a samsung USB lead as the stock one didnt work, or the other way round. I just remember it was a ball-ache but did eventually work. Am not on that pc so cant be more helpful, sorry....
robneymcplum said:
I have an MTK phone and its always going wrong and not booting/turning on because I mess with it and break it
I'm sure I flash the backup I made in mtktools with spflash, and plug the phone in with no battery attached, I also have to use windows 7 on a dual boot as windows 10 never played ball properly. You also need the mtk VCOM driver installed, not just adb and normal drivers. If you have all these, and have tried them, then that is the end of my knowledge sadly. Only other thing is going to needrom and seeing if they have a full rom/backup with partition tables/preloader etc.
Also, had to try a few versions of sptools as certain versions didnt work, forget which one I have and which didnt work. And also had to use a samsung USB lead as the stock one didnt work, or the other way round. I just remember it was a ball-ache but did eventually work. Am not on that pc so cant be more helpful, sorry....
Click to expand...
Click to collapse
Thanks for replying. I'm not sure if I have the VCOM drivers, but I'll check. Luckily I also have a Win7 PC besides this one, so I'll try it there too.
You need to repair preloader. Contact me !
gsm-decode said:
You need to repair preloader. Contact me !
Click to expand...
Click to collapse
Please do a nice thing, and tell me how to repair it here. Maybe there will be people in the exact same situation...
Can't fix MIne too !
DragonSky87 said:
Please do a nice thing, and tell me how to repair it here. Maybe there will be people in the exact same situation...
Click to expand...
Click to collapse
I also got an android phone that is INTEX AQUA I5 hd , i was flashing my phone and unfortunatly my pc got off while flashing . And my preloader got currepted .
When i tries to flash my phone it connects to pc as Mediatek Viacom port , but after 3-4 sec it connects as a usb port .
I continuously gots connceted and dissconnected .
and my Sp flash tool shoes error " S_DA_SDMMC_READ_FAILED(3153) "
Can anybody help me with it ? please help me as soon as possible.
You need to flash preloader by Testpoint,after that flash rom.
Dont remember exactly the testpoint but you can try
DragonSky87 said:
Apparently sometimes it's not the best idea to use the flashing software that the manufacturer of your phone released.
I have a Wiko Lenny(technically a MediaTek MT6572) that has(or had - now it's dead) the habit of simply rebooting into a bootloop every few months. Fixing that was simple; just start SP Flash Tool, format everything then flash the stock ROM back. Last time I did that was around 4 months ago, and since then I have upgraded to Windows 10, and as such, lost the tools I had installed.
Yesterday it went into a bootloop again. I didn't remember exactly what tools I used, so I assumed they were the tools that Wiko supplied a while back with the V10 ROM. Well, they weren't. I still thought I'd give them a try. I mean, it's from the manufacturer's site, so they must work even better that the ones I was using.
I was wrong. The tool flashed the ROM "successfully", but the only thing it actually succeeded to do is corrupt the preloader. For those who don't know, corrupting the preloader basically means the phone won't even power on(not boot, actually power on), won't charge, and the PC won't detect anything if you connect the phone. Practically, it's the hardest brick a phone can get.
The fastest way to fix that is by either using a JTAG connection to flash everything manually, or by entering something called the Mediatek META mode(don't quote me on this one, though - I never heard of it before). JTAG - well I don't have the tools or expertise necessary to do that(although I'd love to learn how to do it - if anyone can point me to a well-written guide or two about that, please do!), and I simply can't get the phone to enter the META mode.
Is JTAG the only way to do it? Is META mode just a myth? Is there a way to save my phone, or should I just say "RIP" and buy a new one(I have the money for a Samsung Galaxy A3, the new one, but I was planning to buy a new computer with that money - is it worth it?)?
TL;DR (It's not that long but anyway...):
I have a Wiko Lenny(Mediatek MT6572) with a corrupted preloader after I flashed it with Wiko's tool. Can I repair it or should I just buy a new phone?
Link to the culprit that killed my phone(AKA Wiko V10 ROM): https://docs.google.com/uc?id=0BzeAvoIC2yhHMTZESUU1Y3hUM0E
Click to expand...
Click to collapse
Repair your own device
Soft Brick: Soft brick is the state of android device which occur due to some software problems like boot loops or phone freezing at some point during boot. This only occurs if some software problem occurred in the device mainly during OS upgrade or ROM flashing. If your device is in such state then you are luck there are 99% chances that you can recover your beloved device without needing any professional help or spending hundred of dollars.
Hard Brick Hard brick is the state of android device that occurs when your device won’t boot at all i.e. no boot loop,no recovery and also not charging. This occurs due to trying to flashed firmwere not made for your device or flashed incorrectly. This is more difficult to resolve and often require professional help
in MTK Android there is many Partitions in your phone. like Preloader, Recovery, Bootimg etc….. if somehow Preloader get Corrupted then you phone will not able to DETECT WITH PC !!! in other words you will have phone with BOOT DEAD.
How Preloader get corrupted ?
There could be few reasons but main reason could be that someone or you Flash your complete phone (include Preloader) with wrong files or with wrong ver. Also there could be reason someone Delete Preloader or you Deleted.
How could i know my phone have preloader dead ?
Preloader can be dead if some one Flash it wrong and after flash your mobile will not detect with pc any more. for confirm
1.sp flash tools does not detect your phone anymore and also the computer does not as there is a pop sound when usb is connected to device
2.open device manager
take battery out from phone
insert usb
insert battery
and check is computer detecting any device
If it’s not detect then you have phone which Preloader is dead AKA Boot Dead
How can i repair it ?
requirement
1.screwdriver (by which you can open the screw from handset)
2.bricked device
3.a usb cable
4.a copper wire( for sold test points)
5.a pc with sp flash tool,mtk drivers and stock firmwere for your mobile
now you have to disassemble your phone and take pcb out. check there should be some Golden points. check these points there should be written on them Rx,Tx,GND,Vcc,Vcharge etc… check there should be written “COLO” or “KOLO” or“KCOLO” you have to Sold that point with GND After Sold Attach usb now your phone will detect with USB !! and now ready to Flash.
In some phones “COLO” or “KOLO” or “KCOLO” not written for those type of phones you have to test all points one by one Short Golden point with GND and attach usb cable which point short with gnd can able to detect your phone by pc isForce Preloader Mode Test Point !! Keep in mind Don’t Short Vcc,Vcharge or any other pin which have 4.x Volts also i had tested “Colo” or “Kolo” or “KCOLO” don’t have any kind of volts.
need help
gsm-decode said:
You need to repair preloader. Contact me ![/QUOTE
i have samsung clone A9 MT6580 After reflash phon,e is dead by sptool..i thinkl preloader is damaged..i dont have back up..but ditecting VCOM BUT Always "Sft Enable Dram_Fail (4032)" in format or fullfash in all tools
Click to expand...
Click to collapse
help me i corrupted my pre loader
gsm-decode said:
You need to repair preloader. Contact me !
Click to expand...
Click to collapse
hi sir I try to flash a stock rom downloaded from internet
its a vivo v5 android mobile phone
I tried to flash but I got a few alerts
the selected model does not support model verification
and
if I tried it gives me a brom error
now my phone condition is hard bricked and responding to flash tool
gsm-decode said:
You need to repair preloader. Contact me !
Click to expand...
Click to collapse
HI sir how can I contact you
Hi I also have the same problem - when I flashed the stock rom of my LG K7 X-210 (MT6580__lge__LG-X210__m13g__5.1__ALPS.L1.MP6.V2.19_ARIMA6580.WE.L_P42) with the SP Flash tool when I was in a bootloop, I accidentally forgot to uncheck the preloader option. I flashed it to my phone and from that point onwards it didn't want to start up any more, nor would it react if I tried charging it. So conclusion: the preloader is corrupt...
However, I read online that MTK devices (mine is MT6580) have a 'meta' mode which allows your device to still connect to SP Flash tool even if it is hardbricked (in my case by pressing the volume up button, and then simultaneously plugging it in the computer). It is then recognized as MTK Com port something in device manager.
Luckily I have the same phone (but it's not mine) and I was wondering if it was possible to make a full rom dump from that device and restore it on mine? (a method that is safe for the other device as well)
i have a proble on my new phone since i flash preloader my touch is not working anymore, any solutions ?
gsm-decode said:
You need to repair preloader. Contact me !
Click to expand...
Click to collapse
I need to repair preloader of My Nokia G20.
hello this is very simple.
i solved this problem.
i wrte english very small.
flash atarken yanlış attığın preloader dosyası ile başlat.cihazı bilgisayara bağla.format bittikten hemen sonra doğru preloader dosyasını klasörün içine yapıştır.ama çok hızlı olmalısın.yani uyumsuz preloader dosyası ile cihaza yükleme yaparken tam format esnasında uyumlu olan preloader dosyasını hızlıca yapıştır.
gsm-decode said:
You need to repair preloader. Contact me !
Click to expand...
Click to collapse
Hello, is it too late to write?
Hi, i'm starting this thread by excusing myself for this approximativly english, i'm not really an english man :angel:
I don't really like calling help on forum, but at 00:30, with studies tomorrow, i'm really bored.
So, today at 17:30, i have reboot my OPX, simply reboot, and i'm now on a bootloop... I read a looooooot of thing on internet and i deduce that : My bootloader has relocked himself.
Before this reboot, i was on OxygenOS 3.* with TWRPblu****** and an unlocked bootloader. I can't access to recovery, only to a bootloop or fastboot mode.
I've tried :
- Use fastboot commands to flash recoveries, but nothing happen because i can't unlock the bootloader
- Use the MSMdowloadtool like all guide said, but the problem is there i think. My device aren't recognize as a "Qualcomm ***********" is recognize as "Android" or "One plus bootloader device" (i haven't exact name here). I thinked Windows 10 have the faculty to identify android devices, so i've installed on dual boot windows 7, no more results. (Signed Drivers are disabled)
I have no idea, i need u :crying:
If anyone have ever see the same issue, give me ur solution please
I certainly will contact the OnePlusSupport too but i know it's not really a good idea.
I will go to sleep now, i need to go to school tomor... today.
Have a good night !
Nekkoelb said:
Hi, i'm starting this thread by excusing myself for this approximativly english, i'm not really an english man :angel:
I don't really like calling help on forum, but at 00:30, with studies tomorrow, i'm really bored.
So, today at 17:30, i have reboot my OPX, simply reboot, and i'm now on a bootloop... I read a looooooot of thing on internet and i deduce that : My bootloader has relocked himself.
Before this reboot, i was on OxygenOS 3.* with TWRPblu****** and an unlocked bootloader. I can't access to recovery, only to a bootloop or fastboot mode.
I've tried :
- Use fastboot commands to flash recoveries, but nothing happen because i can't unlock the bootloader
- Use the MSMdowloadtool like all guide said, but the problem is there i think. My device aren't recognize as a "Qualcomm ***********" is recognize as "Android" or "One plus bootloader device" (i haven't exact name here). I thinked Windows 10 have the faculty to identify android devices, so i've installed on dual boot windows 7, no more results. (Signed Drivers are disabled)
I have no idea, i need u :crying:
If anyone have ever see the same issue, give me ur solution please
I certainly will contact the OnePlusSupport too but i know it's not really a good idea.
I will go to sleep now, i need to go to school tomor... today.
Have a good night !
Click to expand...
Click to collapse
Fastboot commands : is the phone recognised?
"fastboot oem device-info" output?
Did you tried the Mega unbricked guide?
Which step precisely is a problem?
Kéno40 said:
Fastboot commands : is the phone recognised?
"fastboot oem device-info" output?
Did you tried the Mega unbricked guide?
Which step precisely is a problem?
Click to expand...
Click to collapse
Yes he used..read full op.
Nekkoelb said:
Hi, i'm starting this thread by excusing myself for this approximativly english, i'm not really an english man :angel:
I don't really like calling help on forum, but at 00:30, with studies tomorrow, i'm really bored.
So, today at 17:30, i have reboot my OPX, simply reboot, and i'm now on a bootloop... I read a looooooot of thing on internet and i deduce that : My bootloader has relocked himself.
Before this reboot, i was on OxygenOS 3.* with TWRPblu****** and an unlocked bootloader. I can't access to recovery, only to a bootloop or fastboot mode.
I've tried :
- Use fastboot commands to flash recoveries, but nothing happen because i can't unlock the bootloader
- Use the MSMdowloadtool like all guide said, but the problem is there i think. My device aren't recognize as a "Qualcomm ***********" is recognize as "Android" or "One plus bootloader device" (i haven't exact name here). I thinked Windows 10 have the faculty to identify android devices, so i've installed on dual boot windows 7, no more results. (Signed Drivers are disabled)
I have no idea, i need u :crying:
If anyone have ever see the same issue, give me ur solution please
I certainly will contact the OnePlusSupport too but i know it's not really a good idea.
I will go to sleep now, i need to go to school tomor... today.
Have a good night !
Click to expand...
Click to collapse
Power off your phone, connect to PC with power off holding volume up button. It should detect phone as Qualcomm.
Nekkoelb said:
Hi, i'm starting this thread by excusing myself for this approximativly english, i'm not really an english man :angel:
I don't really like calling help on forum, but at 00:30, with studies tomorrow, i'm really bored.
So, today at 17:30, i have reboot my OPX, simply reboot, and i'm now on a bootloop... I read a looooooot of thing on internet and i deduce that : My bootloader has relocked himself.
Before this reboot, i was on OxygenOS 3.* with TWRPblu****** and an unlocked bootloader. I can't access to recovery, only to a bootloop or fastboot mode.
I've tried :
- Use fastboot commands to flash recoveries, but nothing happen because i can't unlock the bootloader
- Use the MSMdowloadtool like all guide said, but the problem is there i think. My device aren't recognize as a "Qualcomm ***********" is recognize as "Android" or "One plus bootloader device" (i haven't exact name here). I thinked Windows 10 have the faculty to identify android devices, so i've installed on dual boot windows 7, no more results. (Signed Drivers are disabled)
I have no idea, i need u :crying:
If anyone have ever see the same issue, give me ur solution please
I certainly will contact the OnePlusSupport too but i know it's not really a good idea.
I will go to sleep now, i need to go to school tomor... today.
Have a good night !
Click to expand...
Click to collapse
You have noting to do but to flash stock oos 2.1.4 using Qualcomm flasher and driver.I faced the same issue.but I managed to flash using Qualcomm in windows 10.and got my onyx back.
My suggesting is remove the adv or oneplus drivers.just install the Qualcomm driver and connect the device.follow the device manager if the deivce detected or not.it will detect and flash using Qualcomm flasher.
Hi,
I bricked my phone, a SHARP Aquos C10.
After unlocking the bootloader I was able to install several rom. The last one was LineageOS 18.
I bricked the phone when I tried to replace LineageOS Recovery with TWRP by dint of trying.
The phone is not completely blocked. It gets stuck for a long time on the "battery" logo which replaced the "Sharp" logo when the unlocked it. After several minutes, it vibrates and restarts.
I can restart it by long pressing the OFF button, I can't turn it off, I can't put it in recovery mode.
I can just put it in download mode but unfortunately it is no longer recognized by the PC.
So, bricked or not bricked.
Thank you for your help.
Nobody can help me ?
Hallo,
if you still can go to the download mode, maybe not all hope is lost. Your phone might not have
a hard brick, but only a soft brick. Everything should be fine as long the download mode isn't bricked too.
I had a similar problem once with a tablet after flashing it.
You need to install the USB-Drivers for your device on your PC and then reconnect it.
This might sound ridicolous if you already have installed them, but sometimes
a deinstallation of the USB-drivers and reinstallation of the drivers might help.
I found the following site for the drivers:
"https://gsmusbdriver.com/sharp-aquos-c10".
If you prefer an official source, you can use: "http://www.sharpusa.com/Home/CustomerSupport/SharpCareCenter/MobileSupport/ADBDriver.aspx"
However both sources seem to look reliable for me, even if I can't test it, without having a SHARP device.
If you are not sure, you might compare it with other tutorials and look for reviews.
Installing the drivers can't lead to harm to your device until you don't connect it.
Things can't really get worse if you install the drivers. The only thing that could happen is, that either the PC will say that it recognizes the device or that no device can be recognized, so it's worth a try. Please report me, if it worked for you and you are able to flash again. I hope this will help.
With kind regards
dontdropme
Hello,
Thank you very much for your help.
Yes, I installed the USB drivers. I unlocked the phone for you I installed another rom.
I reinstalled the drivers following your links. Unfortunately that does not change anything. The phone is not recognized. No sound comes out of the computer when I connect the USB cable.
I tried on 2 computers, 1 on Windows 10 and in Windows 10 / Xubuntu dualboot.
When the battery is empty and I try to turn it on, a red battery will light up and flash. As I charge it, the battery changes color to green.
I don't have download mode if the cable is not plugged into the computer or the charger.
:/
Hallo,
the download mode is supposed to be only able to get started if you connect the device to the computer or another device, this is not strange. You need to go to the download mode and try to flash the stock firmware for you device. Try it at first without a device recognition of your PC and find out, if you need to do a hard reset before, to regain factory settings. I have listed, in color, a short number of things you could do now. If this still doesn't work only the SHARP team or a specialized company might help.
What you could do, is to ask the SHARP support for a source for the USB drivers and how to do a hard reset to regain the factory settings. I don't know which flashing tool you use for you device.
Normally if your device is not recognized by plugging it in to the PC-USB-Port the flashing tool shouldn't recognize it either, but it might be just an error of Windows, and the flashing tool is not allways depentent to the USB-drivers, but relies only on the question if you can go to the download mode, so you could give it a try to flash even in this case. Start the flashing software and look what will happen.
You said, that you have successfully flashed until now, which means that the flashing tool supports you device. If you can't flash now anymore, you might also not make a backup, which would be important, because the only things you could try now, is to find the stock firmware and flashing it.
If you haven't installed any important data on your system after flashing LineageOS or if you already made backups of your applications in a cloud or another drive you need not to care. It is possible that you will need to do a hard reset before. You can find on hardreset.info, in the section "All devices", how to do it or ask the SHARP support. If you fear you have still important data on your phone a backup is normally recommended.
Because flashing a ROM not only wipes your data, but removes the guarantee, the result is: Restoring the phone to a usable device by any helping team of SHARP's customer care service in you city, even if you have any service buildings, might be expensive in this case. To go around high prices you would need too look around also for other data restoring companies or specialists, if nothing works.
But at first, if you are able to do it; I would recommend to do a hard reset of your device, which should restore it to factory setting, which should make the drivers work.
Even if they don't work, ask SHARP for actualized USB-drivers. Try flashing also with and without working USB drivers, and find SHARP's stock firmware for you device first, which is a "must do", if you want to have access to the original recovery mode again. Flash this stock firmware after you have done a hard reset. After flashing the stock firmware you should be able to go to the custom recovery mode again, if not, only a specialized company or a help team of SHARP's customer service might help.
Hello,
The adb and fastboot commands wait for the device to connect.
SHARP support is not responding.
Hello, did you try "https://getsupport.sharpusa.com/Contact-Us/Product-Support"?
Because of the actual situation with the Virus, they might need longer to answer, so you need to be patient. As I see you already tried to connect your device after the use of CMD.exe. Installing the drivers with CMD and checking the Windows Hardware Manager if the Installation worked correctly is one way to do a driver install. I am sorry if this didn't work for you. If it does not, only a specailized soft- and hardware team can help, which could get expansive, but maybe not as much as buying a new device, so I hope for you Sharp will answer and give a correct Installation guide and that it will fit to solve your problem. I wish you good luck and that you don't need any other company than Sharp to help. I know that nobody is amused if all help and waiting does not help, after bricking bis device, but unfortunately I can't do more for you. I wish you success and keep your device in a safe place just for the case.
The Issue:
The phone is constantly booting looping (flashes the Oneplus logo).I am unable to go to fastboot through either adb or through the on-phone buttons.
When plugged into a charger, it immediately begins to bootloop once enough power is supplied.
The only way to turn it off is by letting it get to 0%.
What caused the issue:
My phone got soft bricked all of a sudden, so I followed some tutorials that I found online showing me how to flash firmware using adb in fastboot and by unlocking my bootloader. This temporarily fixed the issue, but it told me that after doing everything I should relock it through ADB. Foolishly, I did so and am now stuck in this situation.
What I've tried:
I am able to get into EDL mode by holding both volume buttons, even while in the boot loop state.
I have downloaded the latest version of QPST and this firmware file (https://firmwarefile.com/oneplus-10t-5g-cph2415).
Quick note: I'm not sure if that's how it's meant to be, but QPST always detects my phone as "Download" (ESN: Download, Phone Number: Download, Banner: Download).
I am not quite sure how to use QPST and have tried following the guide, which told me to select some.hex files from the firmware I downloaded, but I was unable to find any.hex files at all and therefore could not proceed.
I also tried QFIL by selecting prog_firehose_ddr.elf from the IMAGES folder and tried multiple times in both UFS and emmc mode, selecting all of the rawprogram 1-5.xml files with their corresponding patch1-5.xml files from the IMAGES folder, but I always got the same error:
ERROR: function: sahara_rx_data:276 Unable to read packet header. Only read 0 bytes
ERROR: function: sahara_main:982 Sahara protocol error
ERROR: function: main:320 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Fail process fail
Finish Download
I have tried the leaked EDL flasher from here: https://forum.xda-developers.com/t/edl-flash-tool-leak.4494211/. However, I have been unsuccessful in doing so, though I may have been doing it wrong, and it would be greatly appreciated if someone could explain or tell me how to do it. As you can see in the attached image, I tried to flash it by using the images folder located in the firmware that I have downloaded. But it just gets stuck at 3%
indefinitely as the time goes up forever.
Thanks for reading looking forward to any replies/info
uh do not flash it by qfil it will just not work because oneplus actually blocked qfil and qpst so the only way is their edl tool and you cannot flash it on the edl tool unless you have an (actual) account and (not) bypassed
oneplus is really starting to nerve me really their merge with oppo is like a mistake
oneplushypergaming said:
oneplus is really starting to nerve me really their merge with oppo is like a mistake
Click to expand...
Click to collapse
the Merge was a mistake, its laughable that OnePlus went from being with the opensource community to being completely against it.. What annoys me the most is, instead of just locking their bootloader, they post the source code for their phone, probably as they have to, yet they give no way to utilize that code without developers running the risk of bricking their device.. Developers are willing to dedicate their time and money, to build for a device, all they ask, is for the ability to be able to unbrick, that is humble, Devs ask for donations, they do not force it.. Oppo do not even allow their bootloader to be unlocked, which prevents users from bricking their device.. OnePlus allow users to unlock their bootloader, knowing full well that Developers will understandably not be willing to develop for a device without a potential 60-80% brick chance.. The code could very well build for said rom, but once flashed it has the potential to turn the dev's device into a paper weight, meaning something they do to provide, turns into something that ultimately takes..
hosthere247 said:
the Merge was a mistake, its laughable that OnePlus went from being with the opensource community to being completely against it.. What annoys me the most is, instead of just locking their bootloader, they post the source code for their phone, probably as they have to, yet they give no way to utilize that code without developers running the risk of bricking their device.. Developers are willing to dedicate their time and money, to build for a device, all they ask, is for the ability to be able to unbrick, that is humble, Devs ask for donations, they do not force it.. Oppo do not even allow their bootloader to be unlocked, which prevents users from bricking their device.. OnePlus allow users to unlock their bootloader, knowing full well that Developers will understandably not be willing to develop for a device without a potential 60-80% brick chance.. The code could very well build for said rom, but once flashed it has the potential to turn the dev's device into a paper weight, meaning something they do to provide, turns into something that ultimately takes..
Click to expand...
Click to collapse
Well said to be honest that clears my suspicion about oppo they are greedy and dirty and maybe it is oppo who is making oneplus act like this in the first place oneplus should really consider all of this and give the people what they want instead of being a monopoly like oppo i never even liked oppo from the beginning actually i trusted oneplus with my 7t because i knew if i were to brick it the msm tool will always be there it has been months since the release of the 10t and ace pro and yet still no msm tool for it or a way to even get it back yet but there are many msm tools for the rest of the oneplus devices so maybe i am wrong they can tell us but i still think it is wrong that th 10 pro has to have an actual account.
I'm stuck with a Hard Brick and my device screen is black, only entering EDL for a few seconds.
Qmiclient it's the new MSM
AkayamiShurui said:
Qmiclient it's the new MSM
Click to expand...
Click to collapse
Hello , I found this topic because i'm facing the same problem as OP after relocking bootloader .... As anyone found solution to flash on edl mode ? Thanks
mybrickplus said:
Hello , I found this topic because i'm facing the same problem as OP after relocking bootloader .... As anyone found solution to flash on edl mode ? Thanks
Click to expand...
Click to collapse
the only thing i can think of is a slot switch
Yes Probably what happened but now i'm totally stuck on the bootloop until no baterry left.
Cant access fastboot because the phone boot and 2 seconds later reboot ... I can only access edl mode with Oneplus Flasher (bypassed by Hexa change) but after that, like op described the time keep increasing ,and circle progress stays at 3%, nothing seems change on phone
You have no option but to use the official flashing revovery via Oneplus / oppo whoever does it which means paying them to reflash the phone correctly
Ok thank you, so ive to send back the phone or i can do it on my own ?
mybrickplus said:
Ok thank you, so ive to send back the phone or i can do it on my own ?
Click to expand...
Click to collapse
no need to send the phone to oneplus just contact them directly and arrange for one of their techs to reflash your phone over the internet
leezaal said:
no need to send the phone to oneplus just contact them directly and arrange for one of their techs to reflash your phone over the internet
Click to expand...
Click to collapse
He could try but I'm not that sure that they are continuing to offer this service.
Thank you for your help and answers
So anyone who still watching this thread I made progress on this whole problem I took the 11r firmware file and it has script.sh commands in there and I ran them and it extracted all of the firmware files and made a bin folder that has only two folders inside of it and it took all the files to make it it puts it in your recovery section of your computer but it compiled all the empty files so they actually have things on them if you want to know how I did it and what I used just private message me cuz I will not be posting public because Oppo
Hello,
recently I started to play with my Honor 8X JSN-L21 Europe version and I wanted to install a custom ROM from MOS. The instructions said to downgrade my phone to EMUI9.0. I had EMUI10 installed, used HiSuite to downgrade, but it could only go down to EMUI9.1. So, after a little googling, I tried to flash official ROM using the update.app method. After many attempts which ended at 0% the phone finally started to "verify the image," only to stop at 3% and fail. After this i restarted my phone and it is totally bricked. No LED flashing, nothing on the screen, no fastboot/update mode.
The only thing that works now (my computer can see) is putting the phone in COM mode using test point.
I found on the internet some HiSilicon flashing tool that could help, but it doesn't detect my phone when I plug it in (Device Manager says Huawei COM1 - clearly it's connected). The only other option is to buy DX Phoenix and try it out.
Before buying the software, do you guys think it could help? I don't want to spend some $$$ on a software that might (not) work.
Thanks everyone!