Hi To All Member of XDA
Don't Think I am NewBie On XDA. But Never Faced That Kind of Issue And Still Not Find Any Solution For It, So Finally Need To Post This.
Lenovo K900 -
My Handset is Fully Dead. - [ Bought From India ]
Already Tried All Methods :
Normal Power Key Start-up [ Failed ]
Volume Up + Power Key - Boot Screen Start-up [ Failed ]
- Result of Above Two Methods : [ Just Blinking White Light of Home Key - Even NO USB Logo ]
Another Ways Found To Solve This Issue
Installed
IntelAndroidDrvSetup1.2.0
iSocUSB-Driver-Setup-1.0.2
ManufacturingFlashTool_Setup_6.0.2
xFSTK-Setup-1.3.6
All Softwares & Drivers are Properly Installed.
Already Tried MFT 6.02 (Manufacturing Flashing Tool) - Follow All Instruction Carefully
- Result
[ Port 0/0/5 #0: IFW flash failed @ 4%
SOC Device is disconnected - state:1 - status - Flashing IFWI
DEBUG : SOC device lost on port 5
] - SOC Device Lost Because Device Not Responding
*Note : There is No Problem in Firmware File [Not Corrupted or Missed]
So Overall, I had applied All Available Methods Written on Interent. Already Tried ADB And FASTBOOT - No Result
Searched alot Site For Solution - Xda-Developers, Official Lenovo Forum [US, Russian] And Many More, Continue Finding Solution From Last 48 Hours, Can't Sleep Properly.
My Phone is TOTALLY UNRESPONSIVE And will not even go to the boot screen.
So, XDA is My Only HOPE
try pluging charger for at least 4 hours without touching the device , then try manufacturing flash tool method
faraj4 said:
try pluging charger for at least 4 hours without touching the device , then try manufacturing flash tool method
Click to expand...
Click to collapse
Thanks.... Already Tried.... No Result.
faraj4 said:
try pluging charger for at least 4 hours without touching the device , then try manufacturing flash tool method
Click to expand...
Click to collapse
Finally Lenovo is Failed To Start Cell, They Give Me Replacement. Wow...
replacement?
mine bricked 2 days ago, how did you get a replacement?
same problem here...............:crying::crying:
Nazgul1379 said:
same problem here...............:crying::crying:
Click to expand...
Click to collapse
I Contacted Customer Care, And Sent Device To Service Center. They Replaced Motherboard With New One.
One More Thing : I Had Previously Loaded Custom ROM, So My Company Warranty Void. But Due To Dead Condition of Device, They Can't Find Details Of ROM. They Considered As "IN WARRANTY"
the same here
Related
I have been looking in different places for a guide to root the device Haipai x720D and i have seen different ways of doing it but a lot of them are in another language or appear not to be really trusty so i am afraid of trying any of them and end up with a brick..
Could someone post a step by step guide to root this device?
Alpuy said:
I have been looking in different places for a guide to root the device Haipai x720D and i have seen different ways of doing it but a lot of them are in another language or appear not to be really trusty so i am afraid of trying any of them and end up with a brick..
Could someone post a step by step guide to root this device?
Click to expand...
Click to collapse
up
Alpuy said:
up
Click to expand...
Click to collapse
up
Alpuy said:
up
Click to expand...
Click to collapse
## (1) and (2) only for recovery if you experience boot failure
1) Download files for x720d here: http://www.4shared.com/rar/YsR3RDi-/..._Recovery.html
Password is Taiwan101
2) Use flashtool 4.0 and recover your x720d
Original link for (1) and (2) is here http://www.mobile01.com/topicdetail....&t=2934258&p=3
##(3) and (4) are the rooting process
3) After flashing the recover images, boot your phone and ensure its not rooted
4) Use TPSparkyRoot to root your x720d. Link is here http://forum.xda-developers.com/show....php?t=1646544
Follow on-screen instructions. Few re-boots to be done before you are rooted.
Walla. Your x720d should be recovered and rooted.
i made a miztake
Hi everyone,
** EDIT **
i have flashed my x720d with the files posted by "haipai" just above
but now my phone wont boot, and i cannot connect it to my computer
i think he's briked but i hope there is a solution...
Thanks for your help
Nitrogin said:
Hi everyone,
** EDIT **
i have flashed my x720d with the files posted by "haipai" just above
but now my phone wont boot, and i cannot connect it to my computer
i think he's briked but i hope there is a solution...
Thanks for your help
Click to expand...
Click to collapse
also happened to me ...: Rolleyes:: Rolleyes:
before the flash must be clear PRELOADER flag!"!!
to repair the damage, you must:
1 - open the phone by removing the screws.
2 - with a piece of wire to ground the point KCOLD connecting to a screw of the case
3 - press download the original firmware
4 - connect the usb cable and insert the battery (keep it IN POSITION TO END)
5 - cross your fingers : D
sorry for my english ... I'm Italian and I translate with google translate
Tanks for the answer but it look not so easy, where do you find the solution, or maybe a tutorial ??
i don't understand the following sentence
with a piece of wire to ground the point KCOLD connecting to a screw of the case
tanks for the help !
ps : i dont wanna brick it again, where do you found a good firmware ?
up
sorry to keep you waiting!
I understand your situation
look at the first image in the bottom of the post
http://forum.xda-developers.com/showthread.php?t=1943442 or http://forum.xda-developers.com/showpost.php?p=32424838&postcount=616
original ROM
H630_77v01.01b02.rar (214.6 MB)
https://mega.co.nz/#!bcMiWbyK!evXGQURvRVkS7mKUSL_royv-cZQd7rsgP4851xNnP8Y
I hope you will be able to solve
hi,
thank you for helping me, but
i must place a cable between the point "kCOL0" and which is the second ?
i dont have a multimeter or any other tool, i hope this is still possible
thanks
the multimeter is "comfortable" but not necessary. just a piece of stiff wire! kcol0 you connect with any part of the metal frame of the phone! for comfort under a screw, so one end of the wire is locked.
edit:
once flashed the rom, change imei codes! I hope you have it written down somewhere ... otherwise seek it from two old phones that do not use more!
Hi: I bricked my Haipai Noble x720d, it's an mt6577, i mange to dissassemble, i found "kcold" point, and now it can be plugged and recognized by usb port. The problem is that i cannot find a factory rom, and i was tryng to flash different roms and always same error with flash tools 4.0, the error is this:
BROM ERROR: S_DL_GET_DRAM_SETTING_FAIL(5054)
[EMI] Obtain DRAM Failed!
[HINT]:
Please check your load matches to your target which is to be downloaded.
i don't know what that means, I dont know how to solve it, please if someone has a factory rom for that model, Help me.
ROM for x720d
http://forum.xda-developers.com/showthread.php?p=42248564#post42248564
igorilla666 said:
also happened to me ...: Rolleyes:: Rolleyes:
before the flash must be clear PRELOADER flag!"!!
to repair the damage, you must:
1 - open the phone by removing the screws.
2 - with a piece of wire to ground the point KCOLD connecting to a screw of the case
3 - press download the original firmware
4 - connect the usb cable and insert the battery (keep it IN POSITION TO END)
5 - cross your fingers : D
sorry for my english ... I'm Italian and I translate with google translate
Click to expand...
Click to collapse
hi
can you explain me where is the point kcold because i have brick my x720d with a wrong rom.
thanks
I don´t understand it.
haipai said:
## (1) and (2) only for recovery if you experience boot failure
1) Download files for x720d here: http://www.4shared.com/rar/YsR3RDi-/..._Recovery.html
Password is Taiwan101
2) Use flashtool 4.0 and recover your x720d
Original link for (1) and (2) is here http://www.mobile01.com/topicdetail....&t=2934258&p=3
##(3) and (4) are the rooting process
3) After flashing the recover images, boot your phone and ensure its not rooted
4) Use TPSparkyRoot to root your x720d. Link is here http://forum.xda-developers.com/show....php?t=1646544
Follow on-screen instructions. Few re-boots to be done before you are rooted.
Walla. Your x720d should be recovered and rooted.
Click to expand...
Click to collapse
I have completed step 1 but I don't understand step 2. Can you put photo's by the steps? Already thanks!
excuse my poor English
i have axtrom axpad 7e01+ it's pretty good tablet 2 days ago i had an issue when i try to open the tablet it hangs on the logo screen of axtrom and don't open ! so i downloaded the official rom again and the rockship Batch tool 1.7 and followed the guide to re-install rom.
First time trying to re-install it worked successfully but when i tried to open the tablet it had the same issue as before ! so i tried to flash the tablet again and this time i always get this error message
Prepare IDB Failed
and i can't open the tablet tho it's readable in maskrom mode to computer]
i don't know what to do and as a continue of stupidity i disassembled it , thought it's bricked and i really don't know if it is ! ( i had a warranty but the customs service center is too far to go for me )
disassembling did nothing more or less still stuck in this error please help me
note i re-downloaded the rom , tried 2 laptops and 2 USB Cables nothing worked
the error message : im46.gulfup.com/p6qUoL.png
135
maxmono said:
excuse my poor English
i have axtrom axpad 7e01+ it's pretty good tablet 2 days ago i had an issue when i try to open the tablet it hangs on the logo screen of axtrom and don't open ! so i downloaded the official rom again and the rockship Batch tool 1.7 and followed the guide to re-install rom.
First time trying to re-install it worked successfully but when i tried to open the tablet it had the same issue as before ! so i tried to flash the tablet again and this time i always get this error message
Prepare IDB Failed
and i can't open the tablet tho it's readable in maskrom mode to computer]
i don't know what to do and as a continue of stupidity i disassembled it , thought it's bricked and i really don't know if it is ! ( i had a warranty but the customs service center is too far to go for me )
disassembling did nothing more or less still stuck in this error please help me
note i re-downloaded the rom , tried 2 laptops and 2 USB Cables nothing worked
the error message : im46.gulfup.com/p6qUoL.png
Click to expand...
Click to collapse
up no one can help ?
115
up
maxmono said:
up
Click to expand...
Click to collapse
up again
maxmono said:
up again
Click to expand...
Click to collapse
still seeking help
no help ?
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?
Hey there!
I somehow managed to red light brick my x96 mini s905 1gb/8gb, p282 board!
Now the reset button does nothing. I can't boot from any Burn Cards I've made.
Using USB Burn Tool, yields an error at 4% (for every ROM I try including stock rom)
I now have to short the pins to get my pc to even recognize the box and when it does, it fails at 4% in usb burn tools. No matter what settings I use (erase bootloader, erase flash ect)
I've been told these amlogic devices are next to impossible to actually KILL! So is there anyone around XDA that can guide me here?
I'm not new to flashing ROMs (been doing it since my samsung s3 lol) and I have flashed plenty of android boxes without error until this one!
I have a feeling I somehow deleted the bootloader! WHAT DO I DO NOW?!?!
Thanks in advance. Hopefully I've given enough information.
no solution ever for this brick?
found a possible solution
Hi, I just openend a thread where I was able to unbrick my x96mini box
https://forum.xda-developers.com/an...lved-bricked-x96mini-red-led-display-t3992403
I think the problem with this is the power cable is not being conncted after USB detection.
The board doesn't have enough power through USB alone to properly work, so connecting the power jack is mandatory. I failed the first flashing attempt for this reason.
Hope this helps, even when it has been months since OP.
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.