From last 2 weeks I have been struggling with getting my mi4 to work again. Earlier, I was running AOSP Extended Custom Rom based on ANDROID 10 without root but bootloader unlocked since last 3+ years and It was running well. Following complication happened suddenly without installing any new app on my phone:
My payment app shown that my phone is rooted and did not let me do any payments
Unable to connect to WIFI showing password cannot be saved
After that, I tried cleaning apps cache while system was on and through TWRP recovery cleaned Dalvik cache and cache but that did not change any behavior.
Instead of factory resetting and reinstalling same rom, I was looking for new rom and found Xtended XR Vanilla ANDROID 11 rom unofficially released in following thread:
Xtended XR Vanilla ANDROID 11 For Mi4 (Cancro)
I downloaded this rom and Gapps from BitGapps as somehow LiteGapps was not installing playstore even it stated in the information. I tried installing Xtended XR and Gapps but TWRP stated Storage is insufficient. So, I decided to see if only Xtended XR rom works or not? It worked after reinstalling. Everything was working fine but battery was draining fast that was unusual because earlier it was giving me around 1.5-2 hours of Screen on Time and now it was down to around 40-50 mins! In order to get Google Playstore, I had to resize system partition.
After reading few articles, threads and watching YouTube videos, I deleted cache, system, data and vender partitions and resized and recreated them. But after doing that still twrp was showing the same message of storage but I found that it is a problem with many custom roms but can be solved by unmounting system, resize system and mounting system again from twrp after flashing rom. It worked and I was able to install BitGapps and except battery draining everything worked. Therefore I was thinking of flashing some custom kernel for battery draining as I was using CraneWing kernel with AOSP Extended it was working fine. Before that I started setting up my phone settings and installed apps from playstore.
Everything was fine till now but on next day after finishing all basic settings and installing apps, I encountered new problem. It happened twice whenever I try to change brightness manually phone restarts automatically. From second time onward phone stopped booting to system.
I tried following things that did not work:
Re-flashing Xtended XR Rom and BitGapps (installed successfully every time but didn't boot)
Wiping and Formatting cache, data, and system partitions
Changing TWRP version
Installing Stock Fastboot MIUI Global Rom for Mi4 Cancro (installed 4-5 times successfully via PC on fastboot, MI recovery opened twice but system did not boot)
Re-flashing TWRP again (Because battery was not charging, so whenever I keep phone as it is for like 1-2 days for draining battery I can open TWRP with 1-3% battery and can charge till 16-20% then it goes to boot loop with Mi Logo)
By this time I was only able to access Fastboot, so tried installing stock rom but it did not boot. Recovery is also not accessible. I found that I can flash stock rom in EDL mode. My phone does not support EDL from fastboot. Then I found following thread for reboot to edl via fastboot:
Reboot to EDL Via Modified Fastboot For Redmi Note 3
I used that but because it was for Redmi Note 3 and I think I made a mistake by using that. I tried button combinations of Power and Volume buttons and also tried battery draining but that did not work. Now at this moment I am stuck with following problems in given order to make my phone work again:
Battery not charging
Stuck in EDL Mode. Restarting frequently (in 2-3 seconds) in EDL continuously without system recognizing it as Qualcomm Device
Able to turn on Fastboot when Connect with Wall Charger but cannot with USB connected with PC. Though I can turn on Fastboot with wall charger connected and then connect to PC to perform any fastboot commands.
Custom Recovery not accessible (Can flash recovery but not opening)
I am not sure it is entirely battery problem or something wrong with custom rom, gapps or fastboot miui stock rom. I am not sure how can I solve this problem now. Battery replacement seems one thing that I can do but the company stopped manufacturing batteries but I found someone who has 3 years old battery stock and says it works very well for this and many other devices batteries that he sells even if manufactured batteries kept unused for long.
What should I do? I would appreciate if someone help me on this.
Thanks.
I think your brightness problem reason was that you flash cuatom kernel. I think that kernel not supported android 11. You should just tried other custom roms like havoc lineage for android 11 or etc.
Does it have blink red LED When you plug your device to charger?
It should turn to fastboot when you plug via USB to PC and hold vol up + power... Anyway, use another cable (original is better) to do that.
If u can't do that :
So about battery, for your problem i think you have 2 ways:
1. Buy and Change battery and flash fastboot rom and...
2. Charge your battery and flash fastboot and...
Just plug your device for 6-8 hours to the charger and after that, flash fastboot...
Be careful that you should use original cable.
moj.enjoy said:
I think your brightness problem reason was that you flash cuatom kernel. I think that kernel not supported android 11. You should just tried other custom roms like havoc lineage for android 11 or etc.
Does it have blink red LED When you plug your device to charger?
It should turn to fastboot when you plug via USB to PC and hold vol up + power... Anyway, use another cable (original is better) to do that.
If u can't do that :
So about battery, for your problem i think you have 2 ways:
1. Buy and Change battery and flash fastboot rom and...
2. Charge your battery and flash fastboot and...
Just plug your device for 6-8 hours to the charger and after that, flash fastboot...
Be careful that you should use original cable.
Click to expand...
Click to collapse
Actually, I did not flash any custom kernel with Xtended XR rom I was just thinking about finding compatible kernel later and then flash it.
Yes, I do get red LED but phone is continuously in EDL bootloop either I put on charge or connect with PC. With charger I can turn on fastboot but with PC it remain stuck in EDL. So I can perform some fastboot commands via getting fastboot by connecting charger -> turn on fastboot -> plug into PC. But after restart it remain in EDL bootloop. So exiting EDL is first major problem that I need to solve.
Your other two suggestions would not work if I cannot get out of EDL bootloop. Though I do think changing battery after resolving EDL bootloop can work but as of now I have no luck. I hope you get my point.
is there a way to manually stopping EDL via opening phone and do something with the motherboard or battery?
btw you have made a great rom @moj.enjoy thank you. I only got to use it for sometime but I liked it. I am planning to install the same rom if my phone starts.
Click to expand...
Click to collapse
maxrajgor said:
Actually, I did not flash any custom kernel with Xtended XR rom I was just thinking about finding compatible kernel later and then flash it.
Yes, I do get red LED but phone is continuously in EDL bootloop either I put on charge or connect with PC. With charger I can turn on fastboot but with PC it remain stuck in EDL. So I can perform some fastboot commands via getting fastboot by connecting charger -> turn on fastboot -> plug into PC. But after restart it remain in EDL bootloop. So exiting EDL is first major problem that I need to solve.
Your other two suggestions would not work if I cannot get out of EDL bootloop. Though I do think changing battery after resolving EDL bootloop can work but as of now I have no luck. I hope you get my point.
is there a way to manually stopping EDL via opening phone and do something with the motherboard or battery?
Click to expand...
Click to collapse
I know what you are say. But are u sure that you are in EDL mode?
I think when you charge battery, it can automatically bypass EDL! In my opinion charge your battery 8 hours and don't touch that. After that
moj.enjoy said:
I know what you are say. But are u sure that you are in EDL mode?
I think when you charge battery, it can automatically bypass EDL! In my opinion charge your battery 8 hours and don't touch that. After that
Click to expand...
Click to collapse
Alright, let me charge battery for 8 hours and then I will post here whatever happens.
maxrajgor said:
Alright, let me charge battery for 8 hours and then I will post here whatever happens.
Click to expand...
Click to collapse
I tried charging battery for 8 hours, but phone remain uncharged. Sadly, nothing changed.
While charging with charger, the red LED blinks variably between 3-12 times before showing MI logo in bootloop.
Blinking of red LED is the same when connected with PC, but in PC it remains in blinking and neither show MI logo nor allow me to fastboot. Also I hear connect and disconnect Windows OS sounds for devices frequently.
Its
maxrajgor said:
I tried charging battery for 8 hours, but phone remain uncharged. Sadly, nothing changed.
While charging with charger, the red LED blinks variably between 3-12 times before showing MI logo in bootloop.
Blinking of red LED is the same when connected with PC, but in PC it remains in blinking and neither show MI logo nor allow me to fastboot. Also I hear connect and disconnect Windows OS sounds for devices frequently.
Click to expand...
Click to collapse
I think It's battery issue...
CONCLUSIONI changed battery then able to flash custom rom, gapps and installed apps. It was working fine.
But again after few hours it suddenly went to bootloop and never booted again. Technician said there is some problem with PCB and phone is considered dead now.
Thank you @moj.enjoy for giving your time here.
Related
Hi everybody,everything is in the title : my phone doesnt boot up anymore since the battery went to 0% I tried with different cable and adaptators. The problem appeared since i flashed boeffla kernel 4.0 u600 the phone detected the cable but the phone wasn't charging now i've made the error to not flash another kernel before the phone stopped.
Is there a solution different from changing the battery to boot up the phone and flash the phone with a stock kernel .When i plug the phone to the computer it's detected as unknow device but nothing more
What device?
Samsung or something else?
Oneplus one
PS : No recovery mode or any other available
mohamed13014 said:
Hi everybody,everything is in the title : my phone doesnt boot up anymore since the battery went to 0% I tried with different cable and adaptators. The problem appeared since i flashed boeffla kernel 4.0 u600 the phone detected the cable but the phone wasn't charging now i've made the error to not flash another kernel before the phone stopped.
Is there a solution different from changing the battery to boot up the phone and flash the phone with a stock kernel .When i plug the phone to the computer it's detected as unknow device but nothing more
Click to expand...
Click to collapse
Maybe use fastboot? The kernel shouldn't affect charging, only rate, as the phone on "off", just like the radio, operates on a different firmware, so it should still charge. The computer is seeing it, so fastboot into an oem unlock should be good. Install adb and what not.
Had similar experience with my old samsung note 2. Falshed a kernel with bug and then couldn't boot up. Then battery went down and phone refused to charge. But with note 2 you can always change battery.
Anyway maybe you need to tear down your phone and charge your battery, since it's hard to say if your phone is hard bricked because the battery ran out. Maybe you can try this thread which tells you how to fix a hard bricked oneplus one. https://forums.oneplus.net/threads/solution-recover-from-hard-bricked-oneplus-one.104943/
After a while without touching it, it finally charged, vert slowely, but it charged. I'll try to figure out what's the problem...
mohamed13014 said:
After a while without touching it, it finally charged, vert slowely, but it charged. I'll try to figure out what's the problem...
Click to expand...
Click to collapse
Mostly the Battery itself
If a battery is completely emtpy for a while it can just break. Its that simple.
Okay guys here 's the backstory .My OPO fell into water and as always advised by the numerous forums online, I put my OPO in a bowl of rice / silica gel for almost 4 days. :good:
When I tried to turn on the phone on the 5th day unfortunately it didn't. Tried to charge it but the LED woudn't light up and the device was stuck in the bootloop at the 1+ logo and powered by android screen. and when connected to PC i did get it to recognize as the QHSUSB_BULK :victory: installed the drivers and used the MSMTool to flash it again. though the flash was successful the device still continues to be stuck in the boot loop. :crying:
I think probably the battery it at fault. When the device fell into water the charge was around 8 %, it's probably dead ( also I get the Low battery charge for sometime to continue message and some text in Chinese , but device still doesn't charge) .
So I wanted someone to try to boot the device directly via the USB power while the battery is disconnected to see if the device boots into system or if it's show the low battery Warning.I'll will be really grateful to you if you could do this task for me. Also if you guys have any other suggestion to bring my OPO back to life or ways to charge my battery it'll be helpful. :silly:
THINGS I AM ABLE TO DO:
1 ) use the MSMTool and flash the firmware
2 ) enter fastboot and flash fastboot images
THINGS I AM NOT ABLE TO DO :
1 ) charge the battery. LED doesn't light up. ( I have tried leaving it for charging using the official charger for upto 48 hrs. Have also tried using other chargers and USB cables)
2 ) enter recovery either directly using the vol down button nor by using the fastboot boot recover.img cmd ( most of the time I get the LOW battery Screen http://i.imgur.com/ih8oKSA.jpg , still doesn't charge )
THINGS I HAVE TRIED:
1 ) MSMFlashtool and the OneplusoneRecovery tool(The modified MSMtool to flash the CM11S firmware)
2 ) One-Click Back to Stock [64GB & 16GB] (by Martin hotmann)
3 ) boot recovery via fastboot command
4 ) Contact the customer service ( not helpful at all.They didn't even look in to my devices because of the water damage ).
Hello guys,
so two days ago just when I was heading into work my phone randomly started restarting itself again and again. I had it in my pocket, mobile data and wifi off and nothing really going on when this happened. I was on stock Cyanogen OS with 6.0.1, rooted and with Xposed, but nothing too crazy or experimental.
The phone would boot with a small vibration to the Oneplus logo with the "Powered by Android" writing, stay on that for about 17-18 seconds, then reboot again. No way of going to the recovery with the hardware keys, it would just reboot the same again and again. Since I couldn't really do much, not turn it off and no way of disconnecting the battery, I just had to watch it reboot helplessly until the battery was dead. At home with some hassle I could get it charged again, which basically consisted of charging it while it kept rebooting and cooling it while doing that since it would get really, really hot.
The only option that really works is is getting it into fastboot via the volume up + power button. But in fastboot nothing I did so far changed even the smalles thing about it's behaviour. I tried flashing a new recovery image, letting it boot into the recovery via fastboot (both stock recovery and TWRP), reflashing the complete OS via fastboot again (CM 13 ZNH2KAS3P0), completely wiping it via fastboot and flashing an older ROM (CM11S XNPH44S) but so far nothing has even changed a thing. It keeps booting to the Oneplus logo for about 17-18 seconds before rebooting. The only thing that has changed is with the CM11S ROM the fastboot logo of the android head is now bigger.
I checked the bootloader via fastboot, but it's still unlocked.
So yeah, I'm at my wits end and desperate for any help. At this point I fear it might be a hardware issue and I can trash it, but I'm ready to grasp for straws as I don't really have the money for a new device yet.
Any help is appreciated! Thanks guys!
Atomschlumpf said:
Hello guys,
so two days ago just when I was heading into work my phone randomly started restarting itself again and again. I had it in my pocket, mobile data and wifi off and nothing really going on when this happened. I was on stock Cyanogen OS with 6.0.1, rooted and with Xposed, but nothing too crazy or experimental.
The phone would boot with a small vibration to the Oneplus logo with the "Powered by Android" writing, stay on that for about 17-18 seconds, then reboot again. No way of going to the recovery with the hardware keys, it would just reboot the same again and again. Since I couldn't really do much, not turn it off and no way of disconnecting the battery, I just had to watch it reboot helplessly until the battery was dead. At home with some hassle I could get it charged again, which basically consisted of charging it while it kept rebooting and cooling it while doing that since it would get really, really hot.
The only option that really works is is getting it into fastboot via the volume up + power button. But in fastboot nothing I did so far changed even the smalles thing about it's behaviour. I tried flashing a new recovery image, letting it boot into the recovery via fastboot (both stock recovery and TWRP), reflashing the complete OS via fastboot again (CM 13 ZNH2KAS3P0), completely wiping it via fastboot and flashing an older ROM (CM11S XNPH44S) but so far nothing has even changed a thing. It keeps booting to the Oneplus logo for about 17-18 seconds before rebooting. The only thing that has changed is with the CM11S ROM the fastboot logo of the android head is now bigger.
I checked the bootloader via fastboot, but it's still unlocked.
So yeah, I'm at my wits end and desperate for any help. At this point I fear it might be a hardware issue and I can trash it, but I'm ready to grasp for straws as I don't really have the money for a new device yet.
Any help is appreciated! Thanks guys!
Click to expand...
Click to collapse
how old is the device?
As far as I know my sister bought it around summer 2014 when it was released, I got it in late 2015
Atomschlumpf said:
As far as I know my sister bought it around summer 2014 when it was released, I got it in late 2015
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
AFAIK,If this toolkit can't fix your device then it's definitely hw issue.
Mr.Ak said:
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
AFAIK,If this toolkit can't fix your device then it's definitely hw issue.
Click to expand...
Click to collapse
Well, the tool won't even recognize my phone, so I guess I'm **** out of luck ¯\_(ツ)_/¯
****ing great....
Atomschlumpf said:
Well, the tool won't even recognize my phone, so I guess I'm **** out of luck ¯\_(ツ)_/¯
****ing great....
Click to expand...
Click to collapse
Lol,gave up that early?
It needs around 10 tries to get it correctly recognised.
Use XP system with the proper drivers given in the above thread.This tool doesn't work on adb/fastboot,it works on Usb Debugging Port,hence requires different drivers.
Mr.Ak said:
Lol,gave up that early?
It needs around 10 tries to get it correctly recognised.
Use XP system with the proper drivers given in the above thread.This tool doesn't work on adb/fastboot,it works on Usb Debugging Port,hence requires different drivers.
Click to expand...
Click to collapse
No, I didn't. I tried the USB Drivers I had already installed, the drivers that came in the package and the QPST Tool suggested in the thread on both my and my girlfriends laptop. But if it doesn't work on ADB/fastboot I probably can't use it anyway since my only two options are having the phone on the fastboot screen or having it constantly reboot....
At this point I'm just really, really frustrated and have sorta accepted it's very likely a hardware issue
I'm with the same problem. In my case, the tool does recognize and shows green after the end but when i try to boot, it only shows the boot logo.
I can enter in fastboot and trying the command "fastboot continue" the brightness goes up, but nothing else
already tried various tools, back to stock, qualcomm , and none worked, so can i throw it out of the window?
Edit: can't enter in recovery, and unlike the op, my phone doesn't reboot (at least i didn't notice it)
After 8 years of tinkering with Android phones I have no clue how this happened.
PIXEL 2 (Walleye, non-xl)
Tried getting TWRP and ElementalX working but either one or both weren't doing there thing, though I could at least boot and use my phone normally. Finally ended in a situation where I couldn't boot passed fastboot with an error at the bottom "ERROR: LoadImageAndAuth Failed: Load Error". Found a fix that said to change the active partition. Set it to b and that worked and surprise it loads TWRP...so somehow TWRP was installed, but I can't actually load Android.
Grabbed the latest factory image and manually flashed all the files in the zip-within-the-zip. Everything flashed with no hiccups so I rebooted to bootloader with the intention to then reboot the system, and now this is happening:
TLDR Phone won't turn on. Holding PWR+VolDown SEEMS to do nothing, but it actually flashes a line on the screen like it's trying to load something for a milisecond, then does nothing. Holding PWR+VolUp does nothing. Holding PWR+VolUp+VolDown does the same screen flash followed by the notification LED blinking red 2 or 3 times. Please help!
EDIT: if it matters, the phone is about 50% battery and currently still on judging purely by the fact that it's been warm for about an hour.
sorry for your troubles, i have yet to see this with our phones. Just to get some more information, what happens when you try and charge it? If you plug your phone in to a computer via USB, does it show up in devices? If it shows in devices, can you run platform-tools and see if it shows up via fastboot devices with an ID? If you can connect to fastboot, you could attempt to flash images that way.
djer34 said:
sorry for your troubles, i have yet to see this with our phones. Just to get some more information, what happens when you try and charge it? If you plug your phone in to a computer via USB, does it show up in devices?
Click to expand...
Click to collapse
Nothing happens if I plug into the computer, no sound and not listed in devices. Plugging it in to the charger does nothing except possibly charges it, but I wouldn't know because the screen doesn't seem to be able to turn on for more than a milisecond of a flash.
I had this same problem when I flashed Elemental X kernel over top of the flash kernel and all I did was use the flash-all script that is included with the system image from google. This got me back to my OS where I flashed elemental and magisk. Do you have insurance through your provider?
Help here:
OP6 + unlocked+TWRP+Magisk+ Pie9.0.9 xXx Rom.
Yesterday i replace the battery, and it was after one year, wish was without energy. Before assemble rear, i charge a little and test everything.
However i have a strange problem:
When charging OFF, the phone boots and appears the information of telephone unlocked, and stays there.
It should appear the symbol of a central battery + percentage and then go black.
Apart that, everything seems ok with the phone, i can turn OFF, reboot normally, enter TWRP and then system...
Is this normal? Or maybe is something wrong with battery?
Someone?
Can your phone charge in unlock interface? Maybe your phone's boot partition is broken, and it can't show charging interface. Try to use mem tools to flash a full package.
Hi.
It charges normally. On or OFF. Last time i erase and flash ROM 9.0.9, i did have some problems in fact....
And i did flash 9.0.9 Autoinstall from Maurofrio, full package. Everthing seems normal and ok....TWRP, Magisk, etc,etc....
Edit:
Turn off, conect cable, vibrate, and get unlock message.
Press power button + 6 seconds, gets black.......vibrate and again message.....something is weird....
Does not show red light of charging, but i think its hardware here, not software.
Mord0rr said:
Hi.
It charges normally. On or OFF. Last time i erase and flash ROM 9.0.9, i did have some problems in fact....
And i did flash 9.0.9 Autoinstall from Maurofrio, full package. Everthing seems normal and ok....TWRP, Magisk, etc,etc....
Click to expand...
Click to collapse
Try to use MSM Download Tool to restore phone, it will fix everything except the hardware problem.