Related
please help my oneplus 3 can't boot to system or recovery after unbricking with mega unbrick method 1 and 2
the phone boot to black screen and led notification shining white
i try unbricking method again and flash recovery from fastboot dosn't work
sorry my english
Did you solved? I have the same issue ... No ideea what to do... How did you solved?
bibiii79 said:
Did you solved? I have the same issue ... No ideea what to do... How did you solved?
Click to expand...
Click to collapse
If you follow the instructions for method 2, and repeatedly do it a few times, you can succeed. The important thing is to follow the instructions strictly, however silly they may look like.
I did several times, double checking all steps, still boot loop. After apply the method 2 , is doing a boot loop. Than I tried to apply again method 2 I have the successful download with green ...than I go in recovery and flash over adb sideload oos 3.2.8 ...than I start , no more boot loop, but after Oneplus logo goes into black screen with a withe stable notification led turned on ....I left over night ... But it keep staying like that until I force to power off by pressing and holding power button( after I want to turn off i cannot only going into bootloader and from there I choose power of, because is automatically turning on if I press and hold only the power button in order to turn off the device).
Pfiu difficult... I am thinking, some files are missing, this , and where I go in bootloader in missing the values on. Bootloader version- , and baseband version- ....
bibiii79 said:
I did several times, double checking all steps, still boot loop. After apply the method 2 , is doing a boot loop. Than I tried to apply again method 2 I have the successful download with green ...than I go in recovery and flash over adb sideload oos 3.2.8 ...than I start , no more boot loop, but after Oneplus logo goes into black screen with a withe stable notification led turned on ....I left over night ... But it keep staying like that until I force to power off by pressing and holding power button( after I want to turn off i cannot only going into bootloader and from there I choose power of, because is automatically turning on if I press and hold only the power button in order to turn off the device).
Pfiu difficult... I am thinking, some files are missing, this , and where I go in bootloader in missing the values on. Bootloader version- , and baseband version- ....
Click to expand...
Click to collapse
The bootloader and baseband versions were missing when i bought the phone new and are still blank today after flashing a few ROMs and Recoveries/Firmware and modems. So that is not an issue.
Are you downloading the correct files?
tnsmani said:
The bootloader and baseband versions were missing when i bought the phone new and are still blank today after flashing a few ROMs and Recoveries/Firmware and modems. So that is not an issue.
Are you downloading the correct files?
Click to expand...
Click to collapse
Yes, I am using the unbrick method with msm download tool, using the Method 2, after apply, installing all's the Qualcomm drivers 9008 , drivers signature off in windows.... The unbrick tool is passed with the green message .... Reversing back to oos 3.1.2 Android 6.0.1 ..stock, I have recovery working and bootloader also working, bootloader is locked ....so I cannot do too mutch. I start the device right away after unbrick tool and still boot to op logo that is going to vibrate as restart .... And stays in boot loop. Next step I go into recovery , and do over sideload an update with a full ROM, oos 4.0.1 , also tried with full ROM 3.2.8 ...I can sideload the whole ROM , than i start the device and after op logo goes in black screen and white motivation led lighted .... I leave it for 30 min, and still in the same, now I force turn off by going into bootloader and power off. Notice that after this sideload flash I cannot access the recovery. So I need to apply back the unbrick msm download tool for op3.
I tried also to flash over sideload a signed script from Ahmed , unified toolkit , to activate the USB debugging, but gives an error.
I run out of ideas .....any help is welcome ....
Thanks
bibiii79 said:
Yes, I am using the unbrick method with msm download tool, using the Method 2, after apply, installing all's the Qualcomm drivers 9008 , drivers signature off in windows.... The unbrick tool is passed with the green message .... Reversing back to oos 3.1.2 Android 6.0.1 ..stock, I have recovery working and bootloader also working, bootloader is locked ....so I cannot do too mutch. I start the device right away after unbrick tool and still boot to op logo that is going to vibrate as restart .... And stays in boot loop. Next step I go into recovery , and do over sideload an update with a full ROM, oos 4.0.1 , also tried with full ROM 3.2.8 ...I can sideload the whole ROM , than i start the device and after op logo goes in black screen and white motivation led lighted .... I leave it for 30 min, and still in the same, now I force turn off by going into bootloader and power off. Notice that after this sideload flash I cannot access the recovery. So I need to apply back the unbrick msm download tool for op3.
I tried also to flash over sideload a signed script from Ahmed , unified toolkit , to activate the USB debugging, but gives an error.
I run out of ideas .....any help is welcome ....
Thanks
Click to expand...
Click to collapse
Hi bro, did you solved it? Im facing the same problem here
bluuquthug said:
Hi bro, did you solved it? Im facing the same problem here
Click to expand...
Click to collapse
Unfortunately not yet ... Yes I solve it, I bought a Moto Z with dual SIM and snapdragon 820 and 64 GB and SD card with 280 euro .... I am disappointed at the moment about Oneplus 3 , I was a Nexus fan and switched to oneplus ... I thought will be opensource ... But way to expensive repair this done in service , Easter to buy another one ... You save time .. you cannot save money on it ..
bibiii79 said:
Unfortunately not yet ... Yes I solve it, I bought a Moto Z with dual SIM and snapdragon 820 and 64 GB and SD card with 280 euro .... I am disappointed at the moment about Oneplus 3 , I was a Nexus fan and switched to oneplus ... I thought will be opensource ... But way to expensive repair this done in service , Easter to buy another one ... You save time .. you cannot save money on it ..
Click to expand...
Click to collapse
Had the same problem with my oneplus x.
P
oneszero said:
Had the same problem with my oneplus x.
Click to expand...
Click to collapse
And what was the end of your story with Oneplus x?
bibiii79 said:
P
And what was the end of your story with Oneplus x?
Click to expand...
Click to collapse
RMA'd it to a service center for repair, after two tech support calls. They actually told me that they couldn't repair it due to "water damage." Funny thing is, that phone was never dropped in or on anything, let alone in WATER. Then to add insult to injury they refused to send it back to me stating that I had to pay for return shipping. My wife got on the phone with them and by the end of the phone call they said that they would send it back for free. HAHA. So I bought a Oneplus 3 after that whole ordeal. All the while the Oneplus X sat in the box on my desk for about 5 months. Last week I decided to pick it up and tinker with it some more. I scoured the net trying to find any other programs or solutions that I hadn't tried prior to sending it off. I came across somethings that I hadn't seen before. https://forum.xda-developers.com/oneplus-x/help/fastboot-mode-available-stuck-kindly-t3387918. http://rootmygalaxy.net/oneplus-x-s...w.pickmod.com/rom/4187/coloros-for-oneplus-x/. Ended up flashing Color OS via msm tool. Wouldn't load OS, but i didn't end up with a black screen and white LED, it just sat there. So right after I flashed Color OS, i Flashed the mini unbrick tool by Naman, and BOOM it booted into OS. Hope this helps.
Yo Guys.
I tried to install an EMUI 8 ROM on my EMUI 5.1 Honor 7x and now the screen wont turn back on.
The Phone is constantly in Fastboot mode when connected to PC and only the EMUI 5.1 Parts are flashable.
Through the MUltiTool i found out that the Battery-Voltage is at 0 constantly, which is probably the Reason for the screen.
I have the BND-L21 and tried to flash the System,Boot,Cust,Recovery.img from the FirmwareFinder and nothing changed.
Then i tried to flash the EMUI 8 parts, but i says Command not allowed, which probably means the PArtition isnt there.
The bootloader is unlocked and PC can find the device in Fastboot.
What can i do now?
Thanks
ackhack said:
Yo Guys.
I tried to install an EMUI 8 ROM on my EMUI 5.1 Honor 7x and now the screen wont turn back on.
The Phone is constantly in Fastboot mode when connected to PC and only the EMUI 5.1 Parts are flashable.
Through the MUltiTool i found out that the Battery-Voltage is at 0 constantly, which is probably the Reason for the screen.
I have the BND-L21 and tried to flash the System,Boot,Cust,Recovery.img from the FirmwareFinder and nothing changed.
Then i tried to flash the EMUI 8 parts, but i says Command not allowed, which probably means the PArtition isnt there.
The bootloader is unlocked and PC can find the device in Fastboot.
What can i do now?
Thanks
Click to expand...
Click to collapse
I think as long as battery is at zero flashing will allways fail.
Maybe if you had a second working phone , you could try to swap the batteries, at least long enough to try and flash the firmware
mrmazak said:
I think as long as battery is at zero flashing will allways fail.
Maybe if you had a second working phone , you could try to swap the batteries, at least long enough to try and flash the firmware
Click to expand...
Click to collapse
Maybe it's a software issue, and something is really messed up in the phone so that it can't even connect to the battery properly, resulting in the 0 voltage... if this is the case, then a battery replacement wouldn't do anything, instead, other parts have to be replaced, including the motherboard and whatnot iirc.
mrmazak said:
I think as long as battery is at zero flashing will allways fail.
Maybe if you had a second working phone , you could try to swap the batteries, at least long enough to try and flash the firmware
Click to expand...
Click to collapse
steven360 said:
Maybe it's a software issue, and something is really messed up in the phone so that it can't even connect to the battery properly, resulting in the 0 voltage... if this is the case, then a battery replacement wouldn't do anything, instead, other parts have to be replaced, including the motherboard and whatnot iirc.
Click to expand...
Click to collapse
Yeah i just bought the screwdriver to open the smartphone and they will probably deliever on 15th.
But i think the batteryswap wont work, because i never had issues with the battery and never changed it, so it would be very random that it breaks at the same time as i flash the ROM.
The Software probably thinks it has emui 8 to work with but there is emui 5.1 on the phone, which i would accept that i doesnt work, but disconnecting the battery seems very odd.
One way it may work is to either somehow flash a 5.1 rom or emui 8 with fastboot, but i dont know how to do these things. (when the flashing works)
ackhack said:
Yeah i just bought the screwdriver to open the smartphone and they will probably deliever on 15th.
But i think the batteryswap wont work, because i never had issues with the battery and never changed it, so it would be very random that it breaks at the same time as i flash the ROM.
The Software probably thinks it has emui 8 to work with but there is emui 5.1 on the phone, which i would accept that i doesnt work, but disconnecting the battery seems very odd.
One way it may work is to either somehow flash a 5.1 rom or emui 8 with fastboot, but i dont know how to do these things. (when the flashing works)
Click to expand...
Click to collapse
Well you cant create partitions with fastboot, so you cannot flash emui 8 rom with fastboot, if phone is / was running on emui 5
and "offline charging" is function from kernel. And as a side effect of your bad flashed rom, perhaps battery has drained and cannot charge. That is why the suggestion of swapping battery. Not because battery went bad, just that at this time is cannot charge.
mrmazak said:
I think as long as battery is at zero flashing will allways fail.
Maybe if you had a second working phone , you could try to swap the batteries, at least long enough to try and flash the firmware
Click to expand...
Click to collapse
steven360 said:
Maybe it's a software issue, and something is really messed up in the phone so that it can't even connect to the battery properly, resulting in the 0 voltage... if this is the case, then a battery replacement wouldn't do anything, instead, other parts have to be replaced, including the motherboard and whatnot iirc.
Click to expand...
Click to collapse
mrmazak said:
Well you cant create partitions with fastboot, so you cannot flash emui 8 rom with fastboot, if phone is / was running on emui 5
and "offline charging" is function from kernel. And as a side effect of your bad flashed rom, perhaps battery has drained and cannot charge. That is why the suggestion of swapping battery. Not because battery went bad, just that at this time is cannot charge.
Click to expand...
Click to collapse
Yeah i`ll look if the battery is giving out power when the screwdriver arrive, lets see what happens then
Hello everyone, This post is about how to unbrick your Redmi Note 8 Pro.
Sorry for my bad English
A couple of months ago, at the start of sales, I bought myself a Redmi Note 8 Pro, deciding to flash it on a global version, I bricked it, at that time no one knew how to fix it, I decided that it couldn’t be fixed anymore, I bought another phone and left Redmi Note 8 Pro on the shelf, and now a couple of weeks ago I decided to turn it on and see if I could fix it and it turned on! first the vibration starts and then highlighted a white Redmi logo, after that the phone showed that it is charging and I decided to go into a fastboot mode and he booted up! I flashed a boot.img and recovery from my Miui version that i was using before bricking phone (in my case it was from miui 10.4.5)and the phone turned on! none of my data was deleted.
So what you need to do:
1. After bricking your phone, do not try to charge it!
Leave somewhere for a 3-5 days to discharge your phone
2. Put your phone in charge after leaving your phone for a 3-5 days, if your phone boot up as usually (No logo and no image, only black screen) then leave it for a couple more days and put it on charge after couple days
3. If your phone discharged to 0% (battery is fully discharged), then redmi logo comes and then phone shows that it is charging like usually.
4. Do not waste your time, after battery icon shows up *photo* Press Volume Down and Power OFF together, then phone will be booted in fastboot mode.
5. Then you need to flash boot.img and recovery, I was using from version Miui 10.4.5, i will put everything below so you can download it
6. After Flashing boot and recovery, your phone will boot up and that's it!
Download links:boot.img V10.4.5
boot.img V11.0.1.0
recovery V10.4.5
Following this guide might help you to unbrick your phone, no need to use any programs like Miflash or SP FlashTool!
I hope my guide will help you, have a good day
It only works if boot image is not damaged. You can try eg: fastboot flash boot twrp.img and reboot to see.
This will replace your boot image with recovery image, it will completely brick the phone because boot image is no longer working, then prepare to go back to Mi store or $29 for authorised service account.
idog8818 said:
It only works if boot image is not damaged. You can try eg: fastboot flash boot twrp.img and reboot to see.
Click to expand...
Click to collapse
Dude, how could you suggest to try something which will hard brick your device? That's careless and reckless! So guys, don't do that!
That's just example, not suggest someone to do it. Trying to use this example to support my point.
---------- Post added at 11:49 AM ---------- Previous post was at 11:47 AM ----------
Olei said:
Dude, how could you suggest to try something which will hard brick your device? That's careless and reckless! So guys, don't do that!
Click to expand...
Click to collapse
You are using parts of sentence to kill my point.... This is ridiculous.
idog8818 said:
It only works if boot image is not damaged. You can try eg: fastboot flash boot twrp.img and reboot to see.
This will replace your boot image with recovery image, it will completely brick the phone because boot image is no longer working, then prepare to go back to Mi store or $29 for authorised service account.
Click to expand...
Click to collapse
Exactly. If you had flashed custom recovery.img and boot.img and after booting in TWRP the phone became hard brick (only led light works) then the stock boot.img is lost. The method proposed (drain the battery) could be done by opening the phone and disconnecting - connecting the battery.
There is only one solution if boot.img and recovery.img are flashed and afterwards the phone became brick. Either buy an authorized account to use it while in 'sp flash tool' or wait and see if developers create a 'MTK__DA.bin' file or an 'auth_sv.file' in order to use it in 'sp flash tool' and flash the phone. The 'mi flash' program can't work if the pc can't recognize the device. The bricked phone is visible in devices only if you hold vol button.
tornado71 said:
There is only one solution if boot.img and recovery.img are flashed and afterwards the phone became brick. Either buy an authorized account to use it while in 'sp flash tool' or wait and see if developers create a 'MTK__DA.bin' file or an 'auth_sv.file' in order to use it in 'sp flash tool' and flash the phone. The 'mi flash' program can't work if the pc can't recognize the device. The bricked phone is visible in devices only if you hold vol button.
Click to expand...
Click to collapse
https://forum.hovatek.com/thread-23776.html is collecting those above mentioned files. As of now, there's nothing available for the RN8Pro, however, it has already been requested. So there's at least the chance to fetch it from there in the future. I don't know whether the available generic Xiaomi files will work.
Olei said:
https://forum.hovatek.com/thread-23776.html is collecting those above mentioned files. As of now, there's nothing available for the RN8Pro, however, it has already been requested. So there's at least the chance to fetch it from there in the future. I don't know whether the available generic Xiaomi files will work.
Click to expand...
Click to collapse
I tried the generic files. They do not work
Olei said:
I tried the generic files. They do not work
Click to expand...
Click to collapse
They work with authorised service account, I've tried. lol.
idog8818 said:
They work with authorised service account, I've tried. lol.
Click to expand...
Click to collapse
Hello my brother, i finished by bricking my RN8PRO while flashing TWRP, no normal boot no fastboot no recovery, just LED lighting when connecting him to PC, PLZ do you know where i can find an Authorized Mi Account, i will donate. Thanks bro :good:
Thread cleaned
XDA-Developers is a platform to discuss and share, but please do not spam your mail or phone numbers to exchange paid unlock services as we do not encourage others to post with the intention to sell something, see our FORUM RULES :good:
Thank you all for your understanding :good:
strongst
Forum Moderator
Phone not booting
my phone is charging but not booting only the notifikation light glows (not blinking)
what does that mean?
documentation android xiaomi
fi4tch said:
Hello everyone, This post is about how to unbrick your Redmi Note 8 Pro.
Sorry for my bad English
A couple of months ago, at the start of sales, I bought myself a Redmi Note 8 Pro, deciding to flash it on a global version, I bricked it, at that time no one knew how to fix it, I decided that it couldn’t be fixed anymore, I bought another phone and left Redmi Note 8 Pro on the shelf, and now a couple of weeks ago I decided to turn it on and see if I could fix it and it turned on! first the vibration starts and then highlighted a white Redmi logo, after that the phone showed that it is charging and I decided to go into a fastboot mode and he booted up! I flashed a boot.img and recovery from my Miui version that i was using before bricking phone (in my case it was from miui 10.4.5)and the phone turned on! none of my data was deleted.
So what you need to do:
1. After bricking your phone, do not try to charge it!
Leave somewhere for a 3-5 days to discharge your phone
2. Put your phone in charge after leaving your phone for a 3-5 days, if your phone boot up as usually (No logo and no image, only black screen) then leave it for a couple more days and put it on charge after couple days
3. If your phone discharged to 0% (battery is fully discharged), then redmi logo comes and then phone shows that it is charging like usually.
4. Do not waste your time, after battery icon shows up *photo* Press Volume Down and Power OFF together, then phone will be booted in fastboot mode.
5. Then you need to flash boot.img and recovery, I was using from version Miui 10.4.5, i will put everything below so you can download it
6. After Flashing boot and recovery, your phone will boot up and that's it!
Download links:boot.img V10.4.5
boot.img V11.0.1.0
recovery V10.4.5
Following this guide might help you to unbrick your phone, no need to use any programs like Miflash or SP FlashTool!
I hope my guide will help you, have a good day
Click to expand...
Click to collapse
bonjour,
je debute et je cherche une doc systeme android. Peux tu m'aider?
hi,
i'm looking for a system's documentation for Android. Can you help me please?
regards
I only flashed the recovery.img, not the boot. img. Should I try to drain the battery? Also, would disconnecting/reconnecting the battery work instead of waiting for the battery to drain?
lakhdar0104 said:
Hello my brother, i finished by bricking my RN8PRO while flashing TWRP, no normal boot no fastboot no recovery, just LED lighting when connecting him to PC, PLZ do you know where i can find an Authorized Mi Account, i will donate. Thanks bro :good:
Click to expand...
Click to collapse
you must to let the battery drained to 0% or disconecte the battery after this connecte the charger and the phone boot again
How long to wait battery drain? 1 week? 2 week?
As a beginner I was looking for ways to get away from the Google dialer and the phone recording restrictions. Read that the Indonesian ROM had the miui dialer and tried to flash an official Indonesian rom on my new Redmi Note 8. The result was not good. After flashing, using the XiaoMiFlash tool and a tweak to bypass the mismatched-image-error (https://forum.xda-developers.com ... r-fastboot-t3638653, the phone remained in Fastboot mode. I have probably tried to boot a Gingko image on a Willow phone.
When trying to restart it just blinks briefly and turns of. The same in fastboot mode: just briefly buzzes and shows the the fastboot screen and then turns off. Guess it is bricked.
Is there any way to restore it to original global rom?
the same problem with you
NoviceDK said:
As a beginner I was looking for ways to get away from the Google dialer and the phone recording restrictions. Read that the Indonesian ROM had the miui dialer and tried to flash an official Indonesian rom on my new Redmi Note 8. The result was not good. After flashing, using the XiaoMiFlash tool and a tweak to bypass the mismatched-image-error (https://forum.xda-developers.com ... r-fastboot-t3638653, the phone remained in Fastboot mode. I have probably tried to boot a Gingko image on a Willow phone.
When trying to restart it just blinks briefly and turns of. The same in fastboot mode: just briefly buzzes and shows the the fastboot screen and then turns off. Guess it is bricked.
Is there any way to restore it to original global rom?
Click to expand...
Click to collapse
the service center have no idea, they said the phone must change motherboard:crying:
dugu1248 said:
the service center have no idea, they said the phone must change motherboard:crying:
Click to expand...
Click to collapse
Hi, I had a similar issue and I sent it to the service center. Was the fix too expensive for you?
SonXiaomi89 said:
Hello !
I ran into the same problem, and I solved it!
inbox me. I can help you to solve this problem.
Click to expand...
Click to collapse
why not post it here so everyone can get it ???
repair it on service center
SonXiaomi89 said:
Hello !
I ran into the same problem, and I solved it!
inbox me. I can help you to solve this problem.
Click to expand...
Click to collapse
Why not post it here, so everyone can get it ???
That's what the forum is for.
NoviceDK said:
As a beginner I was looking for ways to get away from the Google dialer and the phone recording restrictions. Read that the Indonesian ROM had the miui dialer and tried to flash an official Indonesian rom on my new Redmi Note 8. The result was not good. After flashing, using the XiaoMiFlash tool and a tweak to bypass the mismatched-image-error (https://forum.xda-developers.com ... r-fastboot-t3638653, the phone remained in Fastboot mode. I have probably tried to boot a Gingko image on a Willow phone.
When trying to restart it just blinks briefly and turns of. The same in fastboot mode: just briefly buzzes and shows the the fastboot screen and then turns off. Guess it is bricked.
Is there any way to restore it to original global rom?
Click to expand...
Click to collapse
I got the same here. Did you fix it?
Sorry, I am a idiot and My phone was in perfect condition until I run
fastboot erase recovery
Click to expand...
Click to collapse
fastboot reboot recovery
Click to expand...
Click to collapse
and now my phone doesnt have charging logo on, doesnt boot to bootloader
It is basically black and no response
however, the noti LED is on when charging. and I saw COM6 in device manager once then disappeared
AND in some combination of phone key the LED blink 'while charging condition'
In addition, I tried unplug internal battery but it doesnt work
Any idea how to fix it?
P.S. I have seen the repairing MB need 102 pounds (it's nearly 70% of the price I bought it
This phone have NFC, IR control, 64MP camera which is perfect in this price range
If this phone cant repair, any suggest of non-xiaomi (chinese) phone recommend?
(samsung A52s is top of the hill too but it is a bit old in late 2022)
hheylau said:
P.S. I have seen the repairing MB need 102 pounds (it's nearly 70% of the price I bought it
This phone have NFC, IR control, 64MP camera which is perfect in this price range
If this phone cant repair, any suggest of non-xiaomi (chinese) phone recommend?
(samsung A52s is top of the hill too but it is a bit old in late 2022)
Click to expand...
Click to collapse
Kirasu2080 said:
Click to expand...
Click to collapse
Thank you sooooo much. This tutorial works and save me lots of money and worries.
Btw, is it only available/ apply for note 8 pro cuz it is mediatek cpu?
How do they extract/ do I find the auth file that used in SPflash.exe ?
hheylau said:
Thank you sooooo much. This tutorial works and save me lots of money and worries.
Btw, is it only available/ apply for note 8 pro cuz it is mediatek cpu?
How do they extract/ do I find the auth file that used in SPflash.exe ?
Click to expand...
Click to collapse
Yep. It just works for some old mtk devices. It's based on MTK-bypass github, but it didn't get update for long time. For auth file, I got no idea, didn't search that deep.
Same Situation. Got My Device Bricked (Begonia). Hard Brick, I Tried The Method Mentioned Above.
But When Using Bypass Tool it give the following error...
Please Help....
ahadjutt7 said:
Same Situation. Got My Device Bricked (Begonia). Hard Brick, I Tried The Method Mentioned Above.
But When Using Bypass Tool it give the following error...
Please Help....
Click to expand...
Click to collapse
There's some tricks:
- Use only port that you added Libusb. If you change port, you need to add again.
- Close and open new bypass, hold Power until notification light turn off and on then hold Power + Volume up until it show "Protection disable"
- If bypass error, redo all steps again.
- If sp flash tool not flash after 20s, press Stop. Bypass success again. Then press Download. Usually it will work in 2nd time