so i have tried updating my phone os by using local ota because i have root, i downloaded the zip with oxygen updater and tried flashing it with twrp but it said its wrong device twrp was reporting denniz and the update was for OP515BL1 but when i checked the phone model it said its OP515BL1 so i just removed the abort function when it checked the model since i thought twrp was just reporting incorrect model and after flashing i tried rebooting and now its just stuck on bootloop, i cant get into any recovery/fastboot mode, when its rebooting for a flash of a second it says recovery mode and left bottom corner, i have tried mtk but when i try connecting the device on boot and holding both volume buttons on console it reports this Preloader Preloader - [LIB]: ←[31mStatus: Handshake failed, retrying...←[0m Preloader Preloader - [LIB]: ←[31mStatus: Handshake failed, retrying...←[0m Preloader Preloader - [LIB]: ←[31mStatus: Handshake failed, retrying...←[0m Preloader Preloader - [LIB]: ←[31mStatus: Handshake failed, retrying...←[0m Preloader Preloader - [LIB]: ←[31mStatus: Handshake failed, retrying...←[0m so i kinda dont know what to do anymore, it the device just hardbricked or is there still way to make it boot again, i did backup the data i needed so full wipe is no problem but since i cant even boot to recovery i cant even wipe it any suggestions and help would be welcome
Hi, I made the exact same thing and have the same issue as you.
I have been reading and trying so many different things to get it connected to mtk client but no success,
tools in linux and windows..
I have read that to get access to the mtk client first we have to use the mtk bypass https://github.com/MTK-bypass/bypass_utility but it doesnt even recognize the usb in both windows and linux for me.
And the payloads does not yet include our chip mt6893 anyway..
MT6893 Can't dump bootrom · Issue #27 · MTK-bypass/exploits_collection
MT6893 Can't dump bootrom
github.com
I had some hope in this:
https://www.martview-forum.com/threads/mtk-auth-bypass-tool-v6-exclusive-version.51284/ and it does recognize the chip and starts the bypass but then times out.
Can you try and see if you can bypass with the tool above?
I have given up and will go buy a new phone today i think.
Can confirm, times out after 30 sec or so. I read in another thread that they killed brom mode in android 12 and it does seem that way.
Hey, can I join your club? I did the exact same thing as well ^^
I just got my phone back from a free warranty claim on this boot loop, and they have somehow reflashed it at OnePlus so now I have OOS 12 C.11 trying to downgrade now to get fastboot and brom and thing back to normal: https://community.oneplus.com/thread/1596759
So i took the phone to service on november 8 and it seems like they are almost done with fixing it, by the status changes on the website it seems like they changed the motherboard itself which is a bit strange since i thought they had special manufacturer flashing tools but ah well, for now it seems its gona be on the warranty which i thought just not gonna happen cuz like the orange status which says its not trusted device since its been unlocked shows up when you try booting the device so thats really cool from the service or oneplus warranty policy, but i still havent got the device back since they are still testing it after repairs but i do expect it this week.
So i dont really know if i should buy oneplus ever again if they just disable fastboot and mtk because if they didnt i could have just fixed this myself, but cant really put all the blame on oneplus since i did root and flash twrp on the device so maybe that was the cause of the bootloop, and i would like to know anyone that had the exact, same issue was your device rooted, did you unlock bootloader, custom recovery, how did you flash the ota update.
And sorry everyone that i didnt reply to you if you wanted to test something since i didnt bother checking the forum since i was just so upset that i ****ed up my device by updating and damn oneplus, idont know why they disabled fastboot and mtk, is there maybe vulnerability in it or something so they just disabled it because they could not fix it?
If you have any questions feel free to ask il awnser when them whenever i can.
UPDATE: after i wrote this i rechecked the website and it says its fixed so yeah i should get the phone this week still waiting on them to message me about shipping it to me
totaltmega said:
I have given up and will go buy a new phone today i think.
Click to expand...
Click to collapse
try sending it to service center under warranty since it seems like they did fix mine under warranty when it did show orange alert on boot which did say it is untrusted if you have unlocked your bootloader
totaltmega said:
I just got my phone back from a free warranty claim on this boot loop, and they have somehow reflashed it at OnePlus so now I have OOS 12 C.11 trying to downgrade now to get fastboot and brom and thing back to normal: https://community.oneplus.com/thread/1596759
Click to expand...
Click to collapse
why downgrade? is android 12 really that bad on oxygenos?
So i got my phone back but after like a 2 minutes in the setup screen i noticed that the fingerprint was not working, i did try updating to the latest update since strangely they gave me back one that was year old and it was strange because on the service center website they state that they update the phones to latest version, on the documents i got back with the phone it does say that they changed the motherboard and new imei which was odd seeing how totalmega on this thread got his because they just reflashed it, i might try maybe doing a full reflash of OS if thats possible but if the problem still persists i might need to send it back but still it was still cool that they repaired it under warranty since it had unlocked bootloader.
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?
Hello everyone!
So i've been recently playing with custom roms and I messed up my device shutting it down during a TWRP install (I know how dumb it is and I swore I wouldn't do it again).
My device got bootlooped on the pocophone logo and I could only press the volume down and power button to access a weird black screen (no fastboot, no recovery and not detected by the computer). My last chance was to open it and test points to enter EDL mode (it was almost impossible for me to access it with tweezers). My computer now detects it and I was so happy, MiFlash Tool said my account was bound to my PC so I thought it would work, but I got the message:
Sorry, couldn't flash the device before turning off "Find my Device", and I couldn't find a lot of documentation about that error on the internet.
But how am I supposed to do this considering that I can't even boot my phone ? Or is it just that my account is not authorized, and I need to pay some weird ukrainian guy to posess my computer and work his magic to fix my phone? and how can I contact this kind of guy then?
I have tried doing the same method with Qualcomm Flashing tool QFIL but got the Sahara error. maybe I didn't use the software correctly, I don't really know.
Any help would be very much appreciated, I've been through every website google told me about to fix it, but did not manage to do so.
Thank y'all!
Sorry I didn't read your whole post but I saw you have issues with miflash
Miflash tool has a lot of issues on windows 10
I recommend using vmware with windows 7
Or a computer with windows 7(don't forget to have vcredist 86 and 64 installed)
Superpaupaul said:
Hello everyone!
So i've been recently playing with custom roms and I messed up my device shutting it down during a TWRP install (I know how dumb it is and I swore I wouldn't do it again).
My device got bootlooped on the pocophone logo and I could only press the volume down and power button to access a weird black screen (no fastboot, no recovery and not detected by the computer). My last chance was to open it and test points to enter EDL mode (it was almost impossible for me to access it with tweezers). My computer now detects it and I was so happy, MiFlash Tool said my account was bound to my PC so I thought it would work, but I got the message:
Sorry, couldn't flash the device before turning off "Find my Device", and I couldn't find a lot of documentation about that error on the internet.
But how am I supposed to do this considering that I can't even boot my phone ? Or is it just that my account is not authorized, and I need to pay some weird ukrainian guy to posess my computer and work his magic to fix my phone? and how can I contact this kind of guy then?
I have tried doing the same method with Qualcomm Flashing tool QFIL but got the Sahara error. maybe I didn't use the software correctly, I don't really know.
Any help would be very much appreciated, I've been through every website google told me about to fix it, but did not manage to do so.
Thank y'all!
Click to expand...
Click to collapse
Flashing through EDL mode requires Authorized Xiaomi account. So if you know a person who can perform flashing in your physical presence, approach him or take the phone to the service center.
I´m pretty sure I hardbricked my smartphone. I tried to downgrade from A11 since it messed up my touchscreen, but the process of flashing the older ROM (V11.0.10.0.QFQEUXM) stopped and my phone wont start since then. I know its not completly dead since its recognized on Windows as QDLoader 9008, but I cant flash the ROM I mentioned through MiFlash (using 2020-03-14, also tried 2018-05-28 and 2018-11-15 without success) since it always gives the error "cannot recieve hello packet" (sometimes "cannot read from COM" before that).
It´s worth to mention that I have the EU version, not global, I haven´t opened the back of the phone and I´d rather not to do it, the notification LED is always off and I have ADB, fastboot and the Qualcomm drivers installed. Any idea of what can I do next?
Exactly problem I faced to the T. Same error and everything. The only solution is to go to the device centre and lie android 11 update did it. That's what I did.
Me too, broken touchscreen after update to A11, try to downgrade and my a3 was bricked. I believe that process triggered Android verified boot (anti rollback) and make our a3 bricked. You should bring your phone to service center because you cannot flash through EDL mode without xiaomi authorized account. I'm in Vietnam, service center fixed my A3 for free, even bootloader unlocked
sorry but you can flash stock a11 by qfile and your phone will back to life again
elprfesor said:
sorry but you can flash stock a11 by qfile and your phone will back to life again
Click to expand...
Click to collapse
where can we download stock a11? I'm having the same problem
Hi guys, I did something very stupid, flashed the wrong boot.img and ended up completely bricking my device. I tried changing the active partition to see if it would boot, that didn't help.
I was on the latest august update of official android 11 . Then I found a boot.img I found online, but apparently it wasn't from the exact same rom. The phone booted but no WIFI.
It wouldn't allow me to flash any update through settings - system update hence I decided to try to use a fastboot rom....tried that, but the process when I hit flash_all.bat gives a lot of FAILED (remote: Flashing is not allowed for critical particions) or FAILED (Error reading sparse file)....what am I doing wrong?
I can't do anything except get in fastboot.
Is there any way I can get the phone to work agan? Needless to say that as the idiot I am the whole phone is wiped so this doesn't matter anymore. As long as I can get it to work.
Please advise and thanks (The phone is OP7T Pro ME european).
You can use this tool: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4002909/
leginhee said:
You can use this tool: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4002909/
Click to expand...
Click to collapse
Thanks the problem is i can't get it to start qualcomm edl. I power off, press both vol buttons and conmect to usb but nothing happens. What am i doing wrong?
Qualcomm edl Mode is just a blackscreen
"I can't do anything except get in fastboot."
Your Bootloader was unlocked ?
You can try fastboot reboot edl.
Or you can find a ROM that works, extract all images and flash all of them.
I have a similar problem.. kind of. I just flashed a rooted boot to my phone but there is no wifi at all, and since i dont have a SIM card im not getting any updates. the Boot.img came from the oneplus software update and i did the payload dumper. Since I have rooted it ive lost the wifi capabilites. (its the 7T pro me international.)
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