R7 PlusM doesn't boot properly anymore - Oppo R7 Plus

Hi there, I have tried to find a solution today for this issue but I can't find anything useful anywhere .
Last night I received another update via OTA 151115 and proceed to install it as the earlier ones didn't work. Surprisingly this one worked and after restart my phone didn't had any trace of google apps on it, try to install google play, framework and so but the phone says it's not compatible with google (Big time). Then I went to the bootloader to perform a wipe/erase everything and here's when the problem began, it was stuck in the screen that says optimising applications (the one before starting the setup) and after half an hour unattended the phone restart itself one after another, like in a loop.... From this point on, I haven't been able to power on the device anymore.
It was bought through a third party seller from China, already contacted them and waiting for an answer...
Any clue about what can I do to use my phone again?
Update: I can see the oppo logo after pressing volume up plus power buttons for around 15 seconds but it shows for less than a second the screen it appears when it's updating the software and then it switches itself off... Is this a sign of possible recovery in some way?
just downloaded the last 151115 official update from the oppo community forum but I've got a problem. I can not enter the fasboot or recovery mode because the phone is like trying to install something and it constantly switches itself off... The day this happened, I had two files in my root directory, one was the few update and the other was a full Google thing in the same format than the fw file, I'm afraid I selected the wrong one and that's why the phone went crazy. I guess if there's some way to cancel that attempt to update the wrong file or reset that thing in some way, I'd be able to start over but I can't find anything grgrgr
By the way, the last ota update allowed google maps to work flawlessly and also Instagram, two of my biggest concerns with the phone
I'm even trying to contact oppo service to send the thing and sort it out that way xx
Cheers
Pedro

I've just contacted Oppo Customer Service in Europe to see if they have any solution for my problem as I can't make this thing to start and the battery also doesn't seems to be charging though... No response for the moment, just an automated one confirming the reception of my enquiry
Should I start thinking about my lovely new phone as my new paper weight?

peterpanda1970 said:
I've just contacted Oppo Customer Service in Europe to see if they have any solution for my problem as I can't make this thing to start and the battery also doesn't seems to be charging though... No response for the moment, just an automated one confirming the reception of my enquiry
Should I start thinking about my lovely new phone as my new paper weight?
Click to expand...
Click to collapse
No, no you have a chance to save your phone. If you have to R7 plus M Oppo Chinese version, I can help you. I also had this problem, but he was able to solve it. My Skype: ed_mobstyle.

Hi mate, thanks for the answers. Yes it is the China mobile version "M" I don't have Skype I'm afraid grgrgr
Cheers
Pedro

I was able to fix this problem fairly easily.
First I entered recovery (press Power + Volume Down when the phone is booting up)
Then from the device menu I installed a ROM, you want to download the version you last used. (MAKE SURE IT IS FOR THE OPPO R7 PLUS M)
After installing the stock rom, it will go into installation and have you set up your phone.
After you installed the ROM, download OPPO tools v 1.6.5
Open Oppo Tools and root your phone this will take a few minutes.
After you have rooted your device open Oppo Tools again and select Unlock Google Mobile Services (this too me two weeks to figure out).
Let the phone restart, after it is finished, you should have basic google functionalities (Playstore and Frameworks).
Now since you are rooted, it means that your phone will not download any further OTAs and you will have to install them as ROMs, you can do so by repeating the above process, but I'm not sure of the functionality of Oppo Tools past the most current version.
I cant post links to provide you to where the ROM files and Oppo Tools are at this moment
The roms will be located on the "[ROM][STOCK] Official R7 Plus Roms | R7Plus, R7PlusF, R7PlusM [15 Sep 2015]" of Oppo Fourms
The Oppo Tools will be located when you google "OPPO Tools apk" on your computer and it will take you to the thai version of Oppo Fourms follow the link there to download the apk

Hi mate, thanks for your answer but my problems is that I can't enter the recovery mode cause the phone try to install something and then it switches itself off
I've tried to connect the phone to my laptops and sometimes they recognised it as Qhsub something and I can't find anywhere this driver. Then all the softwares I've got ask me for a scatter file which I don't have....
Also trying to contact support from the brand. For now just send them my data and the phone's imei and now waiting for the magic response... They are excessively slow in their answers!
Thanks so much anyway
Cheers
Pedro

hi mate I guess un the malysia oppo community you can fin the drivers and every things about oppo r7pkusM

sollitair said:
hi mate I guess un the malysia oppo community you can fin the drivers and every things about oppo r7pkusM
Click to expand...
Click to collapse
Just checked in and didn't find anything but the bloody oppotools lol.
Cheers mate!

so please if you still with the same problem let me know I'll try to write an email directly to you with all
links you need for it.
[email protected]
best of luck

Still at the same point mate! The thing keeps on trying to install something and switches itself off. My windows laptop runs on win10, the other is a Mac so I guess useless for this matters... The battery runs out faster than ever even being off. Disaster! Lol
I would really appreciate your help
Cheers
Pedro

This is a video I made to explain how this thing try to boot and it never makes it further...
https://www.youtube.com/watch?v=2LNiWODlUd0

Hi matr
believe me I have just coming back from oppo office and I show them your video and what they said '' you have to change it with the guarantee you have''.
it clear now for me and I state that I had the same problem all what I did is installing the oppo drivers on my PC boot on fastboot mode give some commands to unlock it and tjen I flash the original recovery from oppo then tje coloros was installed and updated as well before flashi'g again TRWP recovery and right now I''m writing to you from my r7plusm it's work smothly rooted with the same original oppo rom coloros.
I hope that your just missing something and let me know to to follow you step by step on this.
cheers P

sollitair said:
Hi matr
believe me I have just coming back from oppo office and I show them your video and what they said '' you have to change it with the guarantee you have''.
it clear now for me and I state that I had the same problem all what I did is installing the oppo drivers on my PC boot on fastboot mode give some commands to unlock it and tjen I flash the original recovery from oppo then tje coloros was installed and updated as well before flashi'g again TRWP recovery and right now I''m writing to you from my r7plusm it's work smothly rooted with the same original oppo rom coloros.
I hope that your just missing something and let me know to to follow you step by step on this.
cheers P
Click to expand...
Click to collapse
Hi mate, my problem is that my computer detects the phone as qhsusb_bulk and I've tried every single file I found with that name and nothing changes, well, the device name from unknown to com1, com2... up to com13 I have seen.... Other thing is that I can't enter the fastboot mode or recovery mode neither. I wish I had an oppo service near home but I live in Uk, now I'm trying to get service from oppostyle and waiting for an answer. To be honest with you, I'm really annoyed with all this, never had a problem with bricked androids or iphones until I met this "guy" lol
Cheers
Pedro

I'm really sorry dude I hope I can help you as I did for mine it was quit simple with the same driver problems,so try to uninstall all drivers you have for oppo and install the one I shared with you taken from my ohone directly that the only way you can give any commands to your phone to switch to fastboot mode even if the problem still present

when I try to install the driver on my win10 laptop it says this...

Using an old win7 laptop I managed to install the bloody Qhsub driver and now the phone appears in the com ports under the name Qualcomm HS-USB QDLoader 9008 (COM4) does this means the phone really doesn't exist?

Update to this thread, I can't do anything until I find a proper driver for the phone which actually is recognised by my laptop as Qhsub_bulk and I can't bloody find this anywhere at least for making 6795 processors or specifically for this model...
Any clue?

peterpanda1970 said:
Update to this thread, I can't do anything until I find a proper driver for the phone which actually is recognised by my laptop as Qhsub_bulk and I can't bloody find this anywhere at least for making 6795 processors or specifically for this model...
Any clue?
Click to expand...
Click to collapse
No need panic ))) I've sent you a set for recovery your device )))) Good luck

ed_mobstyle said:
No need panic ))) I've sent you a set for recovery your device )))) Good luck
Click to expand...
Click to collapse
Hi mate, thanks for your help. Tried to open the link you sent me but it says it's not available anymore grgrgr
Cheers
Pedro

peterpanda1970 said:
Hi mate, thanks for your help. Tried to open the link you sent me but it says it's not available anymore grgrgr
Cheers
Pedro
Click to expand...
Click to collapse
Hi, please check now

Related

[Completed] [Q] Black Screen of Death

Hi everyone ! I am new to forum, so please forgive me if I post into the wrong category .
I have a very big problem with my phone (LG L3 Optimus E400) . I have installed a lot of custom roms on it and yesterday I realized that the current rom I was using doesn't receive text messages so I decided to try antoher one and I had the "great" idea to Flash v20 Baseband for flashing SlimBeane610 rom. That was very silly. After I flashed the rom, I rebooted my phone and nothing happened, screen is black all the time. When I press the power button the phone vibrates and the back and menu buttons lights up for 1 second like normal log on, then boom, all goes black again and if I don't remove the battery and I press the power button or any combination (like Reset, Emergency mode) doesn't work. I googled everything, I found something on this forum but not very useful. I tried wit adb but my phone isn't on so it can't be recognized. I tried wit KDZ Updater (until the phone was recognized) but I get a error like WParam: 100 and LParam: 500. When I connect it with USB sounds are playing like normal and Mobogenie wants to connect with it but I can't enable USB Debugging so it's pissing me off . If I can enable USB Debuggins from PC somehow, maybe I can connect phone with Mobogenie and make a restore , a backup or flash another rom, it would be easy If I can go into recovery or emergency mode but I can't . If it would exist a software that can erase everything on the phone when the it's turned off ... .I tried with LG TOOLS, LG PC SUITE IV, LG FLASH TOOLS, Android MULTI TOOLS and nothing(i have the latest drivers installed). Can I make something to it using the external_sd (like put a flash into it, connect it through PC via USB cable and try to flash a rom from command prompt but I don't know the paths). This is a very hard problem, I have a bricked L3 and I don't know hot to unbrick, I think isn't only a soft problem, maybe I should do something with its hardware ? If anyone could help I would really appreciate .
Thanks in advance !
PS : I won't be able to follow this conversation until the next week because I am going to "Primitive Age" right now...oh God, I'm only good to smash things . :crying:
PodGom said:
The most important thing is, can you see the LG logo that shows up in normal boot? If you don't, it'd be either a screen problem or a hard brick. Nobody except LG can fix these problems, and you would have to pay LG some money to fix the phone. But if you DO see the LG logo and your phone stops, you can try the below options.
It just may be bricked, and you could try getting into recovery and flash an alternative ROM. But if that doesn't work, tryLG mobile support tools to get it back to its stock firmware. Good Luck!
Click to expand...
Click to collapse
No, I can't see the LG logo . If I could saw the LG screen was very easy to fix it. I think the phone it's really dead and I also think that even an authorized service can't fix it . Do you know an approximately price for fixing this issue ? Thanks .
Hi,
You should definitely ask the experts who own your device for help, Here...
http://forum.xda-developers.com/optimus-l3-l5-l7/help
Good luck!
Thank you. Thread closed.

Lenovo S856 China Unbricking tutorial

Problem: You have purchased a China Lenovo S856 smartphone and tried to flash ROW ('Rest of World') firmware to it for whatever reason. You now have a softbricked phone that won't boot past the Lenovo screen.
Solution: Download the following files, which are a little tutorial with pictures, as well as the correct China firmware for your s856 and the Flashing tool to use....https://drive.google.com/open?id=0B6knvSQRiKPzQTMtaXFXZEFNbHc https://drive.google.com/open?id=0B6knvSQRiKPzRTk4ZTB3c1VDdzA https://drive.google.com/open?id=0B6knvSQRiKPzWVA2UENuY1NYTkk
All the solutions I have seen so far were sketchy at best and very difficult to comprehend, let alone use to unbrick your phone. This is what worked for me, and my attempt to help anyone else with the above problem.
That is all, and good day to you.
Thanks for your help, but my problem looks very difficult now, because the system cannot recognize the phone and the phone refuse to boot on. What do you advice?
way2aware said:
Problem: You have purchased a China Lenovo S856 smartphone and tried to flash ROW ('Rest of World') firmware to it for whatever reason. You now have a softbricked phone that won't boot past the Lenovo screen.
Solution: Download the following files, which are a little tutorial with pictures, as well as the correct China firmware for your s856 and the Flashing tool to use....https://drive.google.com/open?id=0B6knvSQRiKPzQTMtaXFXZEFNbHc https://drive.google.com/open?id=0B6knvSQRiKPzRTk4ZTB3c1VDdzA https://drive.google.com/open?id=0B6knvSQRiKPzWVA2UENuY1NYTkk
All the solutions I have seen so far were sketchy at best and very difficult to comprehend, let alone use to unbrick your phone. This is what worked for me, and my attempt to help anyone else with the above problem.
That is all, and good day to you.
Click to expand...
Click to collapse
Prajiro said:
Thanks for your help, but my problem looks very difficult now, because the system cannot recognize the phone and the phone refuse to boot on. What do you advice?
Click to expand...
Click to collapse
Hello...
My system did not recognize my phone, either. Nor would it boot up... it was bricked. This tutorial is for people who are exactly in your situation. I would suggest downloading the files I have uploaded, and reading the tutorial.
way2aware said:
Hello...
My system did not recognize my phone, either. Nor would it boot up... it was bricked. This tutorial is for people who are exactly in your situation. I would suggest downloading the files I have uploaded, and reading the tutorial.
Click to expand...
Click to collapse
Finally got the process started,...but after 7s I got and error message Reached the end of the file.(0x80070026: Receiving hello packet)
Could it be my PC (win 10 32 bit) problem or what do you think?
This happened to me as well, the first and second time I tried the flash. There is a trick which worked for me... I pulled the battery out and put it back in and while holding the volume 'up' button, I plugged my phone into my computer usb port and let windows install the driver. It took a few seconds and then I clicked 'refresh' on the Miflash window, which I had left on. At this point the 'flash' button became available and I clicked on it. This time the flash was successful. Try it.

[OPPO R7S] Hard-Bricked - Kindly Help Needed

Hi guys, i'm desperately writing this thread after asking for help in the Oppo Community forum without no luck.
I know that this is for R7 Plus but i hope that someone could help me with my beloved R7s.
Months ago i've succefully installed the Project Spectrum ROM and it worked fine until few weeks ago when i noticed a random system slow down, maybe after an automatic app update.
I tryed to uninstall few apps and reboot the phone several times but with no luck.
So i decided to wipe it and reinstall the Color OS following the walkthrough but something went wrong and now my OPPO R7s is in a strange bootloop without recovery and fastboot.
The strange things are these:
- if I press the power button all I can see is the OPPO Logo and the loading dots in slow-mo
- if i connect it directly to a Windows PC it is recognized as a generic "Android" terminal.
- if i connect it to a Windows PC pressing and holding POWER + VOLUME DOWN + VOLUME UP it's recognized as a QHSUSB_BULK
I'm not a noob, neither an engineer, but i've a bit of familiarity with computers and similar things so i've tried to follow this guide:
http://community.oppo.com/en/forum.php?mod=viewthread&tid=48654
Downloading this service repair rom : https://drive.google.com/file/d/0BybDE_sPI3b5cmgtU05fbXNobVU/view (from this related discussion : http://forum.xda-developers.com/r7-plus/help/r7s-service-romqpst-unbrick-t3493377)
Following the guide, when i try to execute MSM8x39Downloadtool.exe selecting the phone model (i've three choices xx080_32G, xx081_32G, xx082_32G - and i don't know which one is the correct one) the phone is not recognized as COM CONNECTED in none of the ports. If I also do the verification, clicking on the top right button, it shows FAILED on system.img file.
Can that be the problem?
I'm stuck guys and i don't know what to do.
Any help will be better then a christmas present
Thanks in advance!!
A.
Download this rom and place it in the internal sd and flash to downgrade from spectrum
https://s3.amazonaws.com/public.opp...d_ColorOS/Specified_ColorOS_R7sf_full_009.zip
kishd said:
Download this rom and place it in the internal sd and flash to downgrade from spectrum
https://s3.amazonaws.com/public.opp...d_ColorOS/Specified_ColorOS_R7sf_full_009.zip
Click to expand...
Click to collapse
Thanks kishd i'll give this a try!
The only thing i'm bit worried about is how to flash from the internal sd without recovery mode and fastboot...
I'll keep you updated!:good:
any news?did you manage to fix?
hello guys
i have a problem with my oppo RS7
it has a hard bricked and stucked on booting and booting..... I only have a MacBook Pro and not windows
is anyone over there that knows exactly how to unbrick it using a Mac ?!

There's any hope for hard bricked Moto G3? (no fastboot, Qdloader 9008)

Hi guys its the 3rd time that i post here in the forum hopping to restore my "dead" Moto G3 XT1543 1GB RAM Snapdragon 410 (MSM8916).
Some days ago I've unlock my phone bootloader in order to install CM14.1 and i did it with success! but my sim card wasn't working, so, I tried to look for a solution. And I found a video on youtube that showed the supost fix for this issue, but i was wrong. I've flashed the file which broke my phone immediately and now my phone doesn't do ANYTHING!! Well, at least it shows on my computer as QDLoader 9008 but for now on I dont know what I have to do! I know that the easiest way to fix it is buying another motherboard, but I think that still hope for someone to find the way to fix it! Well, if the pc recognizes the processor so there's something to be done right?
I had searched all over the internet during this week, and I found some interesting possible ways to fix it, but im not a developer so I need help and opinions from other people.
1)The first way was to change the mode to 9006 aka diag mode though some files wich in theory allows you to acces eMMC partition and restore all the 29 inside partition and recover your phone. The problem is: I don't know how to change it to diag mode, but yea i have the needed files, and i don't have the tool to acces the eMMC of the phone and i dont have a backup of the partitions to write over the corrupted ones.
2)The second way was to use this tutorial *http://www.droidsavvy.com/unbrick-qualcomm-mobiles/* that i still havent tried since my phone isn't with me right now. So, in this supose way we can contact the phone through a tool called QFIL and try to "Inject" the bootloader or whatever, in the phone to foce him into a bootloop and so enabling the fastboot mode which allows you to install a rom later on. well the problem for this one is, i dont know if it works on your moto g3 but i gonna try. (if you try this option tell me and i gonna upload the needed files because the folder avaliable in the link contais files for the processor Snapdragon 610 and Moto G3 processor is a 410)
3) The third way is a Jtag repair in a authorized store, but i dont think Moto G3 have a jtag fix (im posting this possibility because i could be wrong)
4) In this way could be a updated Blank Flash actually used to hard unbrick the Moto G1 and I Guess the G2? But im not a developer and I dont know too much about programing, but i'm sure someone out there is a pro
5) Use the QPST which is kinda the same thing as use a eMMC tool? ( again im not a dev ) and from what i got, is used to config all your phone from scratch. would be good if there's a tuto out there
6) Sit and wait till Motorola release the MBM-CI 5.0 which from what i got is used like the Blank Flash or used to make a Blank Flash idk
AGAIN!!! IM NOT A DEV, THIS IS JUST SOME WAYS THAT I FOUND OUT THERE ON THE INTERNET WHICH COULD BE USED TO FIX YOUR BELOVED MOTO G3!! SO, I'M SHARING ALL MY RESEACH WITH YOU GUYS BECAUSE IS A SHAME HAVE TO DUMP MY DEVICE LIKE THAT OR HAVE TO EXPEND LIKE R$ 500 IN A NEW MOTHER BOARD WHICH IN DOLLAR ITS LIKE 1600 U$D (this is Brazil guys yea it's a horrible country T_T ) SO I HOPE THAT THIS POST HELPS SOMEBODY AND IF YOU GOT SOME INFO SHARE TO HELP US TRY TO FIX THE PHONE!
hey you got successful??? in unbricking your phone?
[email protected] said:
hey you got successful??? in unbricking your phone?
Click to expand...
Click to collapse
not yet, i send my phone to an authorized i hope they can fix it via programming box
IkkyShad said:
not yet, i send my phone to an authorized i hope they can fix it via programming box
Click to expand...
Click to collapse
Ohhkay
You'll need blankflash for this device, that's the only thing which will take it back to bootloader mode so you can flash a firmware. Blankflash is usually found in stock firmwares, however the chances are kinda low
siredux said:
You'll need blankflash for this device, that's the only thing which will take it back to bootloader mode so you can flash a firmware. Blankflash is usually found in stock firmwares, however the chances are kinda low
Click to expand...
Click to collapse
yeah i know, i tried everything in 3 weeks but with no success, unfortunately the moto g3 firmwares are kinda different from other firmwares
IkkyShad said:
yeah i know, i tried everything in 3 weeks but with no success, unfortunately the moto g3 firmwares are kinda different from other firmwares
Click to expand...
Click to collapse
Can we even try a firmware of Moto g 2 Nd gen ,to get into fastboot anyhow ? Bcoz Moto g 2nd gen is hardbirck recoverable
[email protected] said:
Can we even try a firmware of Moto g 2 Nd gen ,to get into fastboot anyhow ? Bcoz Moto g 2nd gen is hardbirck recoverable
Click to expand...
Click to collapse
yeah, you can try but the models are different and also the partitions inside the phone... try it out and if it works you can post here
No u can't try the Moto g2 firmware..... As Moto g2 is also waiting for MBM CI 5 file for lollipop and Motorola is not releasing those file needed for blankflash
Sorry to bump needlessly but has there been any progress in this regard?
Has anyone found a solution or blankflash files?
I managed to hardbrick my device while trying to resize the system and userdata partitions (stupid, I know)
Jaysin365 said:
Sorry to bump needlessly but has there been any progress in this regard?
Has anyone found a solution or blankflash files?
I managed to hardbrick my device while trying to resize the system and userdata partitions (stupid, I know)
Click to expand...
Click to collapse
No... And just like previous Moto devices, it is unlikely we will ever get the necessary files.
Same situation, any updates?
I'm currently facing the same situation with XT1543, it ran Marshmallow 6.0 stock (came with Lollipop) and suddenly it hard bricked (last time i checked there were no software updates and even if there were, the phone would not restart itself to update). I ran blankflash but the results were these:
greeting device for command mode
opening device: \\.\COM3
OKAY [ 0.001s]
greeting device for command mode
FAILED (blank-flash:greet-device:error reading packet)
Click to expand...
Click to collapse
I appreciate any help!
gibarsin said:
I'm currently facing the same situation with XT1543, it ran Marshmallow 6.0 stock (came with Lollipop) and suddenly it hard bricked (last time i checked there were no software updates and even if there were, the phone would not restart itself to update). I ran blankflash but the results were these:
I appreciate any help!
Click to expand...
Click to collapse
If you can't get to the bootloader, it's toast... we do not have the proper files to do a Qload reflash, and the chances of getting them are near zero.
Try the usual... drain the battery and hold Power+Vol Dn (normal method to access bootloader) or press and hold Power+Vol Dn for 15-30 seconds, if you can't get to the bootloader there is NO recovery method available. Sorry.
acejavelin said:
If you can't get to the bootloader, it's toast... we do not have the proper files to do a Qload reflash, and the chances of getting them are near zero.
Try the usual... drain the battery and hold Power+Vol Dn (normal method to access bootloader) or press and hold Power+Vol Dn for 15-30 seconds, if you can't get to the bootloader there is NO recovery method available. Sorry.
Click to expand...
Click to collapse
Thanks for the quick reply, I will post my results here whether it's successful or not.
acejavelin said:
If you can't get to the bootloader, it's toast... we do not have the proper files to do a Qload reflash, and the chances of getting them are near zero.
Try the usual... drain the battery and hold Power+Vol Dn (normal method to access bootloader) or press and hold Power+Vol Dn for 15-30 seconds, if you can't get to the bootloader there is NO recovery method available. Sorry.
Click to expand...
Click to collapse
+1 on this.
The only other thing I would do is take it apart and detach one wire from battery and short that lose wire to the other wire (short the phone, NOT the battery!) for 15 sec or so and reconnect wire to battery and put phone back together and try boot to bootloader (power plus vol-dn). If no go, at that point if it were worth it I would give it to ATT to fix, or toss it in the drawer for parts.
I too hard bricked my g3.
My PC detected it as Qualcomm 9008 mode
Plz help how to solve this
Durga teja said:
I too hard bricked my g3.
My PC detected it as Qualcomm 9008 mode
Plz help how to solve this
Click to expand...
Click to collapse
Tell us how you bricked it?
KrisM22 said:
Tell us how you bricked it?
Click to expand...
Click to collapse
Rooted and installed twrp nd framework on 5.0
Bro accidentally updated to 6.0 on WiFi
Blank screen. No bootloader.
LED blinkinh
Durga teja said:
Rooted and installed twrp nd framework on 5.0
Bro accidentally updated to 6.0 on WiFi
Blank screen. No bootloader.
LED blinkinh
Click to expand...
Click to collapse
beyond my knowledge. Hopefully someone will jump in.
Durga teja said:
Rooted and installed twrp nd framework on 5.0
Bro accidentally updated to 6.0 on WiFi
Blank screen. No bootloader.
LED blinkinh
Click to expand...
Click to collapse
If there is no bootloader and the only thing that can be seen on the computer is QdLoader mode, it's done... Send it to Moto for repair or send it to the recycler, there is no fix we can do.

[Completed] Doogee X5 Pro Bricked

Ok, i have a doogee x5 pro phone and i tried to root it by flashing twrp recovery using sp flash tools. While flashing i got the error "PMT Changed for the rom it must be download". So i did a small research on internet and i found out that i needed to format everything except bootloader. This succeded. So after that i tried to install the firmware with this succeding to. Unfortunately the time i tried to turn phone on it was dead. SP Flash Tools wont detect it anymore. Please help me cause the phone is not mine and its brand new! I can rate my self as moderate android user. :crying:
i think i have a bigger problem... I downloaded a stock rom for doogee max pro(cause i just realised it wasnt just pro it was max pro) and it didnt seem to be recognised again. Any help would be appreciated. I constantly keep trying to raise it from the deads. Thanks!
Ap0s said:
i think i have a bigger problem... I downloaded a stock rom for doogee max pro(cause i just realised it wasnt just pro it was max pro) and it didnt seem to be recognised again. Any help would be appreciated. I constantly keep trying to raise it from the deads. Thanks!
Click to expand...
Click to collapse
On mtk devices a preloader is independently installed, it should be almost impossible to destroy, I owned a x5 pro and had best success to flash it with sp flash by taking out the battery, press flash button and plug it in...
The second huge issue I see is when you used the specific flash tool format option you very, very likely killed the nvram partition which contained the imei, so you'll have to fix this too by generating a new one and using mtk engineer mode which is well described and to find on Google..
But let's go step by step. Check without battery, or if it's a non replaceable you'll need find the reset button..
i have tried before without battery and i tried just now but nothing. Its very weird it was detected before and now no in same and another machine. I am pretty confused and stressed. Hope i didnt do any physical damage.. :crying:. THANKS!
starting to get pretty stressed omg! and is there a difference between MT6737M and MT6737?
i came to the point im starting to lose my mind... tried everything i could, i have 5 days left to repair this phone and i dont wanna pay 85 euros for this. SP Flash Tools wont detect the phone. Tried almost 5 different scatter files,2 different PCs and different mtk drivers. Im losing my mind already
UPDATE: I almost fixed it! I had flashed wrong preloader so phone wasn't recognized by SP Flash Tool. I fixed preloaded with a little trick from here: link. After that i flashed stock rom downloaded from doogee.cc but phone will not boot resulting in a total black screen. When i hot Power + Vol Up it takes me to another screen:
Select Boot Mode:
Recovery
Bootloader
Normal
Doesn't matter which boot mode i choose i just get a total black screen which means i get nothing. Idk what is happening! Any further help would be appreciated! I constantly try to bring it back working with little success and small improvements.
Last UPDATE: FIXED my phone had no juice left inside so couldnt complete boot proccess. Now its all good running Btw someone must pin this META trick link i send on my previous post cause im sure more people out there have preloader issues!!! Thank you everyone!!
Sam Nakamura said:
On mtk devices a preloader is independently installed, it should be almost impossible to destroy, I owned a x5 pro and had best success to flash it with sp flash by taking out the battery, press flash button and plug it in...
The second huge issue I see is when you used the specific flash tool format option you very, very likely killed the nvram partition which contained the imei, so you'll have to fix this too by generating a new one and using mtk engineer mode which is well described and to find on Google..
But let's go step by step. Check without battery, or if it's a non replaceable you'll need find the reset button..
Click to expand...
Click to collapse
And yes i couldnt flash it with battery only with!

Categories

Resources