Redmi Note 4 in bootloop after changing battery - Xiaomi Redmi Note 4 Questions & Answers

Dear community, my Redmi Note 4 had its battery dying, so I ordered a new BN41 battery on ebay. After receiving it, I followed a video tutorial on youtube in order to replace the old battery with the new one. After that, I started the phone and since then it's in bootloop mode. The only thing I get is the Mi splashscreen without the android message at the bottom, and it keeps looping like that if I dont hold the power button in order to shut down the device. If I press volume down and power button I can enter fastboot mode. I also managed to unlock my phone with the official xiaomi unlock tool. I tried to use SP Tools with the fastboot rom "Redmi Note 4 MTK Latest Global Stable Version Fastboot File Download" ( nikel_global_images_V10.1.1.0.MBFMIFI_20181206.0000.00_6.0_global_b73ca18a6f.tgz) from en.miui.com a-234.html
I use SP Tools version 5.1648 with replacing the cust.img with a cust global I found on different forums.
In SP Tools I leave all checked and "Download only" mode, when I plug the phone all the process runs successfully until the end, but then when I unplug the phone and start it it's still in bootloop (no android message at the bottom of the screen, only the "Mi" logo in the middle of the screen ).
I haven't tried anything else, and not sure what else should I try, any suggestions would be appreciated.
Thanks in advance for your help. Let me know if you need any additional information that could help to resolve the issue. Before changing the battery everything was working fine, official rom, just the battery was not holding anymore.
Best regards,

Even though bootloops are generally a software issue, I would carefully consider the fact that it occurred after you physically opened your phone and replaced the battery.
I would open the phone again and examine it for the possibility that a connector inside has been disturbed and maybe not re-seated correctly.
It may also be beneficial to temporarily put back in the original battery just to rule out the possibility that the replacement battery is not causing an issue, (though I can't see how it could).
Once you have been able to rule out any physical problems then look into reflashing the rom etc.
Sent from my Redmi Note 4 using Tapatalk

Hi, Thanks for the feedback.
Actually, I have proceeded to physical checks, tried previous battery, connectors, but unfortunately still the same...
I have tried several fastboot images using SP Flash tool, always the process ends successfully from the tool side, but phone remains in bootloop after turning it on.
Could installing TWRP be any sort of help ? I am not an expert so trying to figure out the possibilities. I have not able to install TWRP anyway so far, there is a lot of information out there but I'm having trouble to figure out what is the right information. As I don't have access to android to set the phone in debug mode I am trying to install TWRP with SP Flash tools, but haven't been successful so far.
Any additional thoughts ?
Best,

Hi, after further inspection I noticed that I damaged the main board flex for my redmi note 4 while replacing the battery.
My Redmi Note 4 is MTK processor (not Snapdragon) The flex on my phone says :
CM885_MAIN_FPC_V2.0
FWSZ 42 16
I find on aliexpress , ebay, replacement flex cables but with other references.
Are the cables for SD & MTK different ? From the pictures they look pretty the same, but apparently they are different can someone confirm ?
For MTK version of the phone, I find replacements, but with other references than mine. I did not found any with the FWSZ 42 16 reference ; but they all have the CM885_MAIN_FPC_V2.0 reference
Does anyone knows which reference of cable I can order, knowing that my phone is an MTK version of the redmi note 4.
Thanks.

Quick update, I ordered a new CM885_MAIN_FPC_V2.0 cable flex for my Redmi Note 4.
Now I'm waiting to receive it, replace it and see if my phone boots normally.

Good luck. I hope it works.
Sent from my Redmi Note 4 using Tapatalk

Related

How to recover bricked Elephone P9000Lite

Hello guys,
I am really in need of help. For reason that does not matter any more I have tried to root my phone and now it is unable to start. I followed the steps listed in the below tutorial:
bbs.elephone.hk/thread-9919-1-1.html
However after following some steps, video tutorials and further confusions I ended up trying to "Firmaware Upgrade" my phone with SPFlash Tool, but unfortunately the process was ended prematurely and my phone is not able to start at all (black screen and no reaction from any button). I understand that everyone must take responsibility for the consequences followed by rooting a phone, but I wanted to ask you guys if I am able to recover the phone or I would need to buy a new one.
Here is more detailed information of what I tried and what is the problem I am experiencing:
- Error that I see when I try to "Format & Download" (or any other option / action that SPFlash tool has):
BROOM ERROR : STATUS_PRELOADER_INVALID (-1073545212)
[HINT]:
- What I tried:
1. Reinstalling the drivers because I tought that they are incorrect. Every downloaded dirver results to the same error and I believe that the issue is not related to the dirvers at all (I use Windows 7 Ultimate with the SP_Driver_v2.0).
2. Tried using different versions for SPFlash Tool, but it appears that only the latest ones works with the scatter file that I have (MT6755_Android_scatter.txt). Versions that I tried are - v5.1552; v5.1524; v5.1620; and after trying evrything I believe that the issue is not related to the used tool nor scatter file.
My conclusion is that somewhere along the way I re-formatted my phone, but since the processes ended prematurely this may have disrupted the correct format of the internal storage.
Is is possible to recover from this and if it is what steps / actions should I take to do so. I would really appreciated some help of you guys and will be glad if the phone is working back (promise to stop being a "hacker").
Best Regards,
A fellow that need helps or a new phone
I just wanted to add that I was able to recover my phone. YEY!!!!
For those of your who ran to the same problem here is what I did to restore the phone from the boot loop:
1. Remove the battery - this is quite a tricky part, but if you follow the steps and be careful there should not be any problems:
- Remove the back from the phone - since it is no meant to be easily removed you could use a plastic card and start from the top of the phone (where the ear jack is located).
- After that you would need to remove the top plastic cover - it is placed to protect the main board and all modules. You would need a small "Philips" screwdriver in order to remove all screws. Note that there is one hidden screw that is placed on the middle bottom part of the plastic cover. You could recognize it by the elephone logo placed on top of it.
- Once the plastic cover is removed you will see the connector of the battery. Remove so that the device is actually turned off.
2. Download a STOCK ROM for your device:
- The STOCK ROM for Elephone P9000Lite was downloaded from here:
4pda.ru/forum/index.php?showtopic=697579&st=20#entry47838700
All required images along with the scatter.txt file should present inside the downloaded archive.
3. Flash the ROM by using SPFlash tool:
- What I did here is to follow a tutorial that is specifically for hard bricked devices:
devs-lab.com/how-to-unbrick-mediatek-device.html
In my case I had to use the Format + Download option in SPFlash tool and select all images to be flashed. The important part was that the phone's battery had to be disconnected, all images selected by clicking the "Format + Download" option and finally hit the "Download" button. Once this is done you can connect the battery again and connect the device to your computer.
After the process is completed the device can be powered on and it should start booting.
I hope that I can help someone with these steps and that you do not give up on your phone.
Best Regards,
Happy fellow that resurrected his pone
I've bricked my other devices before and all i had to do to fix it, was remove the battery and format & download the original software. As you meantioned, with P9000 (same as with the Lite version), the problem is non-removable back cover and battery. Thank you for this tutorial, but it'd be better is somebody make a video tutorial or just add any media at all as many people might not want to do it, because of fear to break something under the back cover
Thanks for this, I am currently in the same position you were. I've cracked open the phone and am just trying to work out which connector feeds the power from the battery. I was pretty sure my problem was repairable so wasn't too stressed, but I hadn't thought to attempt to open the phone up like you did. It was surprisingly easy, and I don't think I'll have done any permanent damage. I'm hoping I can get the phone going again without any data loss, I was trying to flash recovery when I bricked it so hopefully I simply flash TWRP and she boots again.
awedxz said:
I just wanted to add that I was able to recover my phone. YEY!!!!
For those of your who ran to the same problem here is what I did to restore the phone from the boot loop:
1. Remove the battery - this is quite a tricky part, but if you follow the steps and be careful there should not be any problems:
- Remove the back from the phone - since it is no meant to be easily removed you could use a plastic card and start from the top of the phone (where the ear jack is located).
- After that you would need to remove the top plastic cover - it is placed to protect the main board and all modules. You would need a small "Philips" screwdriver in order to remove all screws. Note that there is one hidden screw that is placed on the middle bottom part of the plastic cover. You could recognize it by the elephone logo placed on top of it.
- Once the plastic cover is removed you will see the connector of the battery. Remove so that the device is actually turned off.
2. Download a STOCK ROM for your device:
- The STOCK ROM for Elephone P9000Lite was downloaded from here:
4pda.ru/forum/index.php?showtopic=697579&st=20#entry47838700
All required images along with the scatter.txt file should present inside the downloaded archive.
3. Flash the ROM by using SPFlash tool:
- What I did here is to follow a tutorial that is specifically for hard bricked devices:
devs-lab.com/how-to-unbrick-mediatek-device.html
In my case I had to use the Format + Download option in SPFlash tool and select all images to be flashed. The important part was that the phone's battery had to be disconnected, all images selected by clicking the "Format + Download" option and finally hit the "Download" button. Once this is done you can connect the battery again and connect the device to your computer.
After the process is completed the device can be powered on and it should start booting.
I hope that I can help someone with these steps and that you do not give up on your phone.
Best Regards,
Happy fellow that resurrected his pone
Click to expand...
Click to collapse
Hello all. I softbricked my phone while attempting to flash TWRP, and ended up with a phone that wouldn't present anything on screen. So I've located an old XP computer to rule out any driver issues, and using the battery removal mentioned above I was able to flash the factory 20160422 firmware which is what I believe my phone had before I started tinkering. I unticked the userdata box as I flashed it, and left the recovery box ticked which I thought would fix any corrupt recovery that my tinkering caused. The flash took some time, but I got the green tick indicating that it went well. However I still get nothing on screen, the only time I get anything is when I plug it into charge, I get a green battery charge icon for a few seconds before it fades away. If I leave it plugged in for a while, the screens starts to faintly flash sporadically. Does anyone have any advise for me? @awedxz, could you please confirm that the battery connection is on the far left, a shiny copper ribbon with a small silver rectangle plug that clicks into the board?
jiddahidda said:
Hello all. I softbricked my phone while attempting to flash TWRP, and ended up with a phone that wouldn't present anything on screen. So I've located an old XP computer to rule out any driver issues, and using the battery removal mentioned above I was able to flash the factory 20160422 firmware which is what I believe my phone had before I started tinkering. I unticked the userdata box as I flashed it, and left the recovery box ticked which I thought would fix any corrupt recovery that my tinkering caused. The flash took some time, but I got the green tick indicating that it went well. However I still get nothing on screen, the only time I get anything is when I plug it into charge, I get a green battery charge icon for a few seconds before it fades away. If I leave it plugged in for a while, the screens starts to faintly flash sporadically. Does anyone have any advise for me? @awedxz, could you please confirm that the battery connection is on the far left, a shiny copper ribbon with a small silver rectangle plug that clicks into the board?
Click to expand...
Click to collapse
Let it to charge more time
Thanks mate, this advise was spot on. It must have had 0% battery after fixing it! It's now alive and charging up. How neat that Mediatek devices can be unbricked so easily, although I'll have to be a bit more careful in future I think! My previous devices have been Motorola, HTC and Samsung devices, each with different tools and flashing techniques. Haven't bricked any of them in the past, but it's nice knowing this device will be hard to permanently brick.
chtsarts said:
Let it to charge more time
Click to expand...
Click to collapse
Had the same problem, a small cable that goes from the power button was disconnected. Connect the cable and it should run just fine
Just to chime in, I soft bricked my phone as well.
I managed to get it back to life, without taking the phone apart, so that is not a necessity.
Here's what happened: I had CM13 installed on the phone and wanted to go back to stock, so I flashed it according to the guides, also overwriting the preloader.
After that, the phone was dead, as in unable to turn on, no charger detection etc.
As is already known, this phone has an "emergency" line / device, that will turn on once you connect it to the computer and press the VOL+ button (the device will show up for a couple seconds in the Windows device manager).
So what I tried was to flash it again and again, to no avail; sp_flashtool reported the following error after trying to flash the preloader: "BROM ERROR - STATUS_EXT_RAM_EXCEPTION (-1073414139)"
Finally I tried different stock roms, from the Elephone forum.
The one that did the trick for me was the 20160304 - I loaded the scatter file into sp_flash tool and only flashed the preloader. After that, Windows suddenly recognized the phone as the preloader device, the screen turned on showing the charging image and the notification led lit up. I was able to flash the phone without errors again.
After that I flashed the rest of the stock firmware - without the preloader.
I then let the phone charge a little bit and it turned back on.
If that version of the preloader does not do the trick for you, try different ones.
No need to take the phone apart.
Good luck everyone!
For everyone's else information having this problem. I also bricked my P9000 whilst flashing TWRP and getting the RAM error. I tried every options possible but the only one that worked was to disconnect the battery. It is actually a very easy process as described as above. The battery connector is the small connector nearest to the volume buttons with the bronze coloured connector cable. It simply lifts up and your battery is disconnect. I changed the settings in SP FLASH to without battery and my phone flashed without any problems. Before this, it had been dead for over a week and all other methods failed to wake it up. Hope this helps.
---------- Post added at 11:36 AM ---------- Previous post was at 11:07 AM ----------
This video may help also
https://www.youtube.com/watch?v=irDOXh1QoKE
Hi everyone! I had the same problem (bricked phone not recognised by flash tool ecc ecc) and disconnecting the battery did the trick, but I may have messed up with some
The screen connectors and now the screen lits up but stays black. Sounds and touch screen work (I can unlock the screen because I hear the unlock sound), but the screen stays black... If I have damaged the connector (I think it's the one on the upper left, the thinner one that doesn't really click when inserted) there is not much to do, but I just wanted to know If anyone had the same issue and eventually resolved it.

Did I just kill my girlfriend's Redmi 3s?

When she got this Xiaomi 3S I rooted it and put Lollypop xiaomi.eu_multi_HM3_6.9.22_v8-5.1 ROM together with TWRP recovery (don't know what version it was, but it was the latest at that time).
Yesterday we learned that she cannot connect to Gear S2 watch via Samsung Gear Companion app, so I thought that changing the ROM might improve things.
From http://en.miui.com/download-303.html I downloaded miui_HM3SGlobal_V8.2.5.0.MALMIDL_5271576d3b_6.0.zip and after copying it to the local storage I pointed the installer to the zip file. The logs showed that the installer could not mount /firmware and after a half an hour the progress bar reached the end but nothing happened. I left it for at least 10 more minutes, nothing changed. I took a screenshot, which the TWRP log acknowledged, so it wasn't really stuck.
I held the power button and the phone shut down, but now I cannot turn it on. No signs of life whatsoever, no matter what key combination I press now.
What might've happened?
Did I get the wrong ROM? I don't think so.
Was that ROM supposed to be installed over the old one? Xiaomi didn't say no.
Any advice is welcome.
I've created the nandroid backup with TWRP, and backed it off the phone before I started the upgrade, but it's of no use to me now, as I cannot get it back to life.
Guys at Xiaomi boards pointed out to a mistake I've done, apparently one does not flash stock ROM over Xiaomi.eu ROM.
I should've used MiFlash to do it.
You can try to use Xiaomi Deep Flash Cable.
Try to enter EDL mode and use miflash.
Thanks, I've already tried with making my own deep flash cable, but the phone did not react to it as expected. These days I plan to bring it to a repair shop and let them have a go, rather than ordering one of those cables and then wait for a month before I have a chance to play again with it

[HELP] Error Mode Boot loop -No Access to fastboot/adb/recovery

Hi hello
So here’s a head scratcher I hope someone can help me with that won’t involve replacing my main board.
Got myself the p20 lite (ANE-LX1 C432) - Single Sim.
I unlocked the bootloader with Huawei just before they stopped handing out the codes. All was good and happy with the world.
Rooted with Magisk and Was busy messing around With Termux, Linux deploy, Mobile Terminal and some pretty basic stuff. I’ve been out of the android scene for a while so was getting reacquainted with the scene.
Anyway. I was messing around in the terminal in a root shell just fixing basic permissions after messing up my termux environment as root. Phone randomly rebooted (I must’ve messed with the wrong folder -no idea which) came back on and my IMEI and baseband were gone.
No worries, I thought. Happened tonnes of times with my previous Devices (looking at you Samsung) just a quick restore or flash and all will be happy again.
Yeah, not quite.
Note that up until this point I hadn’t touched the system partition (probably besides the mobile terminal mishap -no idea)
So over the last week or so I have tried everything. Restore from Twrp backup. Flashed stock through fastboot, through erecovery. Those flashed ok but didn’t fix it.
Putting numerous different update.app FULL & OTA updates in dload folder on SD and internal all failed. Only used my builds version of course and only ones firmware finder deemed compatible/available
Then I got desperate (read: stupid) Decided to take the unpacked firmware files and flash whichever ones twrp would let me. First tried just the modem files. Didn’t help. Then just went through the list and flashed all I could.
I think the kicker came in when I installed the Trustfirmware.img because once I did that I rebooted and now I was stuck in an endless boot loop. No way to get into recovery. Not with their ton combo nor adb/fastboot.
I still had access to fastboot at this point at least and started doing every single thing suggested all over the net just trying to get back to stock.
Tried the unbrick option on The Huawei Multi-Tool. Flashed ok. Phone still wouldn’t boot. Did it a few times with 3 approved versions. Nothing. Only access to fastboot otherwise I was in a boot loop with error mode error no 15 and the verification failure (Attached below)
Last thing I tried after reading online was to relock my boot loader and flash stock. So I locked it with Huawei Multi-Tool. Reboot......
Now I don’t even have access to fastboot. My PC’s (windows and Linux) don’t even acknowledge it and holding volume down in all the weird and wonderful ways and times does nothing. All I get is startup Huawei Logo, Error Mode as per pic Below and then reboot. That’s it.
I’m assuming it’s trying to do a factory reset after relocking the bootloader (if it even locked properly, can’t check) but it can’t get into recovery/erecovery. I dunno ?
That’s my essay of where I’m at. Warranty is already void so not an option and I don’t want to buy a new mainboard (may as well buy a new phone).
So here I am. Is this my life now or does anyone have any magic tricks to possibly suggest?
Pyrolectic13 said:
Hi hello
So here’s a head scratcher I hope someone can help me with that won’t involve replacing my main board.
Got myself the p20 lite (ANE-LX1 C432) - Single Sim.
I unlocked the bootloader with Huawei just before they stopped handing out the codes. All was good and happy with the world.
Rooted with Magisk and Was busy messing around With Termux, Linux deploy, Mobile Terminal and some pretty basic stuff. I’ve been out of the android scene for a while so was getting reacquainted with the scene.
Anyway. I was messing around in the terminal in a root shell just fixing basic permissions after messing up my termux environment as root. Phone randomly rebooted (I must’ve messed with the wrong folder -no idea which) came back on and my IMEI and baseband were gone.
No worries, I thought. Happened tonnes of times with my previous Devices (looking at you Samsung) just a quick restore or flash and all will be happy again.
Yeah, not quite.
Note that up until this point I hadn’t touched the system partition (probably besides the mobile terminal mishap -no idea)
So over the last week or so I have tried everything. Restore from Twrp backup. Flashed stock through fastboot, through erecovery. Those flashed ok but didn’t fix it.
Putting numerous different update.app FULL & OTA updates in dload folder on SD and internal all failed. Only used my builds version of course and only ones firmware finder deemed compatible/available
Then I got desperate (read: stupid) Decided to take the unpacked firmware files and flash whichever ones twrp would let me. First tried just the modem files. Didn’t help. Then just went through the list and flashed all I could.
I think the kicker came in when I installed the Trustfirmware.img because once I did that I rebooted and now I was stuck in an endless boot loop. No way to get into recovery. Not with their ton combo nor adb/fastboot.
I still had access to fastboot at this point at least and started doing every single thing suggested all over the net just trying to get back to stock.
Tried the unbrick option on The Huawei Multi-Tool. Flashed ok. Phone still wouldn’t boot. Did it a few times with 3 approved versions. Nothing. Only access to fastboot otherwise I was in a boot loop with error mode error no 15 and the verification failure (Attached below)
Last thing I tried after reading online was to relock my boot loader and flash stock. So I locked it with Huawei Multi-Tool. Reboot......
Now I don’t even have access to fastboot. My PC’s (windows and Linux) don’t even acknowledge it and holding volume down in all the weird and wonderful ways and times does nothing. All I get is startup Huawei Logo, Error Mode as per pic Below and then reboot. That’s it.
I’m assuming it’s trying to do a factory reset after relocking the bootloader (if it even locked properly, can’t check) but it can’t get into recovery/erecovery. I dunno ?
That’s my essay of where I’m at. Warranty is already void so not an option and I don’t want to buy a new mainboard (may as well buy a new phone).
So here I am. Is this my life now or does anyone have any magic tricks to possibly suggest?
Click to expand...
Click to collapse
Check the second post in this thread:
https://forum.xda-developers.com/honor-7x/help/help-stuck-error-mode-screen-t3735067
kilroystyx said:
Check the second post in this thread:
https://forum.xda-developers.com/honor-7x/help/help-stuck-error-mode-screen-t3735067
Click to expand...
Click to collapse
Thanks for this.
The battery discharged fully about two days ago.
I haven’t tried plugging it in and out as/if it turns on immediately (though even though it shows dead without charger it still comes on immediately).
I’m gonna get a weaker lower amp charger and see if that maybe helps. Fml ?
***UPDATE***
Been at it for hours. Battery is completely flat. But h second I plug it in the the Black Huawei logo comes up ten a few seconds later it’s on the same error screen for a little longer then boot loops like that constantly.
The error isn’t the same as the post in that link though. And I am FRP unlocked.
Eh.
Pyrolectic13 said:
Thanks for this.
The battery discharged fully about two days ago.
I haven’t tried plugging it in and out as/if it turns on immediately (though even though it shows dead without charger it still comes on immediately).
I’m gonna get a weaker lower amp charger and see if that maybe helps. Fml ?
***UPDATE***
Been at it for hours. Battery is completely flat. But h second I plug it in the the Black Huawei logo comes up ten a few seconds later it’s on the same error screen for a little longer then boot loops like that constantly.
The error isn’t the same as the post in that link though. And I am FRP unlocked.
Eh.
Click to expand...
Click to collapse
I guess your previous error was related to ramdisk...
Now what is your current situation?
-What error is showed in the Error mode?
-Can you reach FASTBOOT&RESCUE MODE menu?
-What is your current recovery?
kilroystyx said:
I guess your previous error was related to ramdisk...
Now what is your current situation?
-What error is showed in the Error mode?
-Can you reach FASTBOOT&RESCUE MODE menu?
-What is your current recovery?
Click to expand...
Click to collapse
As it stands I cannot enter fastboot or recovery mode. Update from SD also doesn’t do anything. Battery is completely discharged. And if I leave it on the charger it doesn’t charge, only boot loops.
So with all that the ONLY thing this phone does now is:
- Starts up Showing Huawei logo
- Error Mode Screen with Func No: 15 (bl31 image) & Error No: 1 (security verify failed)
- Reboots
Ths happens whether it’s plugged into the pc’s usb or the charger. Tried all combinations of buttons too.
It has stock recovery as I flashed that back when trying to revert back to stock.
I lost access to fastboot after I locked the bootlaoder again using the Huawei Multi Tool. It’s like it trying to do the factory wipe that it usually would after locking/unlocking the bootloader but is unable to due to the error mode screen.
Sent from my iPhone using Tapatalk
Pyrolectic13 said:
As it stands I cannot enter fastboot or recovery mode. Update from SD also doesn’t do anything. Battery is completely discharged. And if I leave it on the charger it doesn’t charge, only boot loops.
So with all that the ONLY thing this phone does now is:
- Starts up Showing Huawei logo
- Error Mode Screen with Func No: 15 (bl31 image) & Error No: 1 (security verify failed)
- Reboots
Ths happens whether it’s plugged into the pc’s usb or the charger. Tried all combinations of buttons too.
It has stock recovery as I flashed that back when trying to revert back to stock.
I lost access to fastboot after I locked the bootlaoder again using the Huawei Multi Tool. It’s like it trying to do the factory wipe that it usually would after locking/unlocking the bootloader but is unable to due to the error mode screen.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
I see, it is really bad
My last hope is to be able to do a forced Firmware upgrade. Press power button and VOL + and VOL- simultaneously. Do you see the same as the attached image?
kilroystyx said:
I see, it is really bad
My last hope is to be able to do a forced Firmware upgrade. Press power button and VOL + and VOL- simultaneously. Do you see the same as the attached image?
Click to expand...
Click to collapse
Ah man, I wish it would even do that. It makes no attempt to even pretend to see the sd card update. If I hold all the buttons in it still only comes up with the error mode and reboots.
I popped it open and connected a charger up battery to see if that would help but it doesn’t.
Do you maybe know the pin layout on the inside or know where I could get schematics? Been looking everywhere.
I’m almost done building my own Jtag box and am hoping to bring it back to life by writing straight to the damn thing.
Sent from my iPhone using Tapatalk
Pyrolectic13 said:
Ah man, I wish it would even do that. It makes no attempt to even pretend to see the sd card update. If I hold all the buttons in it still only comes up with the error mode and reboots.
I popped it open and connected a charger up battery to see if that would help but it doesn’t.
Do you maybe know the pin layout on the inside or know where I could get schematics? Been looking everywhere.
I’m almost done building my own Jtag box and am hoping to bring it back to life by writing straight to the damn thing.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
That is sad!!!
With JTAG and schematics stuff I cannot help you.
What I found recently and it was new for me (I didn't tested yet) is a possibility to install firmware via "dload" folder, but to start installation the stock recovery have to be full functional.
If I found something interesting for you I'll post here.
kilroystyx said:
That is sad!!!
With JTAG and schematics stuff I cannot help you.
What I found recently and it was new for me (I didn't tested yet) is a possibility to install firmware via "dload" folder, but to start installation the stock recovery have to be full functional.
If I found something interesting for you I'll post here.
Click to expand...
Click to collapse
To my knowledge the recovery is installed. Well erecovery. It was working up until I locked the bootloader again and it went into a boot loop instead of doing the factory reset.
Is there any other way to force sd update other than with the dload folder?
Thanks for tying to help, I appreciate it.
Pyrolectic13 said:
To my knowledge the recovery is installed. Well erecovery. It was working up until I locked the bootloader again and it went into a boot loop instead of doing the factory reset.
Is there any other way to force sd update other than with the dload folder?
Thanks for tying to help, I appreciate it.
Click to expand...
Click to collapse
You can check the official documentation about that.
Please let us know how you solved this problem.
kumarsid7 said:
Please let us know how you solved this problem.
Click to expand...
Click to collapse
Still unsolved as of yet.
I’ve finished building my own version of the Riff/Octoplus box as well as a makeshift Jtag. I’m still trying to find and piece together some firmware files and other board software I think I need.
Also, if anyone has any idea where the test point is on this board I’d really appreciate you pointing it out. I cannot find the schematics or any solid documentation anywhere.
I will attach the pics I have of both sides of the board as soon as I get home.
Sent from my iPhone using Tapatalk
in first picture youle see many circles golden 2 smallest is testpoint good luck
Pyrolectic13 said:
Still unsolved as of yet.
I’ve finished building my own version of the Riff/Octoplus box as well as a makeshift Jtag. I’m still trying to find and piece together some firmware files and other board software I think I need.
Also, if anyone has any idea where the test point is on this board I’d really appreciate you pointing it out. I cannot find the schematics or any solid documentation anywhere.
I will attach the pics I have of both sides of the board as soon as I get home.
View attachment 4579956
View attachment 4579957
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
in first picture youle see many circles golden 2 smallest is testpoint good luck
well, try to restore your device using dload method. It needs you to copy the UPDATE.APP in dload folder of an external sd card(formated in NTFS format) and then just press both vol up+down along with power button for a few seconds. It will auto launch huawei e-recovery and will try to flash the UPDATE.APP you stored in ext sd card. This should definitely work.
Dload method doesn't need you to unlock your device or bootloader.
Maybe?
I know it’s a long shot but I still have this phone. If anyone maybe knows if there’s been a way to fix this as of yet please let me know. ?
Lol. Still got this damn thing. Been searching around and seen a few people reporting similar errors. Never find out if they ever solve it though.
So. Anyone maybe have any knowledge to share? Anything at all.
I don't know if you still have your device, but I had the exact same issue with a P10 (VTR-L09)
I was able to fix fastboot using https://github.com/mashed-potatoes/PotatoNV
That tool was designed to unlock the bootloader, but I noticed that It actually flashes a slightly modified version of fastboot.
PotatoNV can also unlock P20 lite bootloader, so you should give it a shot.
Good luck!
If it works, you should be able to flash stock recovery image and then restore the system using the dload folder.
you can Repair it with Software Testpoint and Full Bootloader Unlock ,and then flash a Board Software via Software Testpoint, that helps 100%!!!
use this Firmware Download ANE-LX1
use the Software with logins and you have all what you need.
you must start the Software Testpoint so!!
VIDEO : how to start Software Testpoint P20 Lite
than in Software Testpoint you flash the included Board Software with DC-Phoenix and after that use the included dload update via sdcard and eRecovery mode and your Phone is running!!!
I would unlock the bootloader via Software Testpoint with DC-Phoenix, then the FBLock is unlocked and you can flash as you wish!!!! And the great thing about it is that you don't need an UnlockKey either, you can then read this with HCU client software, the only thing that's stupid is that you need a time-based license for the two programs, which you have to buy.
HCU client download
https://hcu-client.com
DC Phoenix download
https://forum.dc-unlocker.com/forum/modems-and-phones/huawei/155916-dc-phoenix
Since I accidentally bought a 3-day license twice and my P20 Lite is now completely rooted on Lineage 19.1, I can give away 2 access data, which are still valid for 2 days.
you can edit your smartphone with it.
username : bl26457
password : kKncnkMj
username : bl26390
password : JDAZqnkN
Then I wish you a lot of fun with it, hope it helps you if someone else is active in this thread.

Dead End (Dead Brick) with asus zenfone 3 pegasus (x008)

Hello everyone,
This is my first post here, so I would like to say how great is to have such an amazing community!So way to go to all!
Now let's get to the point.I recently bought a asus zenfone 3 pegasus (x008), which was pre-owned and came with the chinese version of firmware.For some reason I realized when I recieved it,that it had invalid IMEI,so I tried to get it rooted and then with the appropriate tools I may had a good chance of making it able to make and recieve some calls (for a change). All were going well,I installed the right drivers,downloaded twrp for my version, so far so good,but on the way I needed to go back to the original recovery,and when I used the sp flash tool for some reason,it stuck and the process was interrupted.The status of the phone currently is as described in the title,TOTALLY BRICKED,except from the charging LED light.
I tried again with SP to do the same process with the original stock firmware for my device,but the strange thing here is that,although the pc reacts to connection with sound,SP flash tool does not respond at all.No red or purple bars like nothing was plugged.It surely is not matter of time because I plugged it and left it many times for about 5-10 minutes.I used all the possible combinations of keys while it is shut down (no other way to be so far) and even the no key.No response for SP flashtool.I checked my device manager and when I plug it in I have the phone as Mediatek DA usb vcom (Android). I WOULD TRULY APPRECIATE IT if you could help me resolve my problem.

Question Stuck on fastboot mode with low battery

Hello,
So I tried to flash a global rom into my chinese GT 2 pro which didn't actually work, and in the process of fixing this and having to go to work etc the phone battery died and now that I have all the resources to "unbrick" the phone I can't flash anything because of the low battery and I can't charge the phone because it won't even load the recovery mode. I am trying the .bat file that I found in this forum where it charges rebooting the fastboot mode but it's charging 2mv every 3.5 minutes and if my maths are correct, this would take me 2 months to charge to 30% in order to flash anything which obviously is not viable . And I've seen suggestions about splitting a cable and charging the battery with the wires directly but I can't find any information on how to actually do this. Would this work at all? Or is there anything I can do? Please give me some hope! Thank you all in advance
boot into TWRP from fastboot and let it charge
I have tried this but still not working. It's says OKAY after "sending boot" but nothing happens, just a black screen. Although I'm not completely sure that I'm doing this right or even using the right image. Would you be able to guide me with this a bit further please?
try this to disable start-up on usb
Code:
fastboot oem off-mode-charge 1
fastboot oem enable-charger-screen
Thank you, I will try this tomorrow and update either way in case it helps someone else (because hopefully it does work! )
Hello all, so those codes didn't work. I got a guy to try and unbrick it who in the attempt to do so he actually hard bricked it I had given up at this point but he didn't. He wanted to try a test point which involves opening the back of the phone, which actually worked! (Apparently we tried to flash the wrong ofp) anyway, in the process of opening the back case I damaged the power flex (and the actual back case too, but I wasn't too worried about that as I thought I had no phone anyway).... I would attempt to replace both but I can't find where to buy replacements. If I try to google it everything I find is for realme gt neo. Any ideas where I can find a new power flex and back cover? Thank you!

Categories

Resources