Stuck on Bootloop with Locked Bootloader - Xiaomi Redmi Note 4 Questions & Answers

Hi,
I've been tricking around with the Note 4 64gb since it entered into a Bootloop about 2 weeks ago and at one stage I got into a Chinese Rom but then it all fell apart. I cannot even get back to that point.
Phone will not switch on, will not enter into the phones ROM so I cannot change any of the settings within. Therefore the bootloader remains locked because I cannot access the phone however I know I can flash to the phone but why it will not restart is beyond me. Remains on Miui Screen on constant reboot after 30 seconds or so.
When I did get the CN Dev Rom(whatever it was as I got excited when it loaded and cannot remember how I did it) to load it was the phone disconnected from USB and below the powered by android came up. It would only go passed this when I connected the USB to power/pc as apparently the battery is bad. I know this couldn't be the case because the phone will happily sit for hours in Fastboot Mode(Rabbit) so maybe that Rom affected the hardware badly.
Using Smart Phone Flash Tool I can get
6.12 Global, 8.03 Global, 7.12 CN and 8.1.18 Roms to flash to the phone without any success of booting up normally or even showing the powered by android thing. These will all only work with the Cust.img file because otherwise it says File Too big.
It only flashes with everything ticked except preload. It will not work just by having system and boot selected. Error Codes are then 0Xc00500003
Using Mi Flash I can see the device connected in Fastboot mode and it says Flash Complete but the fact it only takes 1 second leads me to believe it does not actually flash anything because it won't reboot.
Using ADB and entering command with admin rights and typing adb devices(whilst in fastboot) doesn't show the device connected at all but refreshing Mi Flash does show the device. Very odd.
When I did get the Chinese Dev Rom to work on the phone I did notice that the IMEI had been wiped from the phone which was less than helpul also.
Can anybody help me get the phone back to a working state?
Thanks in advance

---

I think the fact you are not getting no reply from 'adb devices' is not a good start, are you sure you have all the correct drivers? Secondly do you have another computer to try it on?
Here is the minimal ADB:
http://xiaomitips.com/download/adb-setup-v1-4-3/
Here is the Unbrick Guide & install the drivers that are in it:
http://forum.xda-developers.com/red...redmi-note-4-unlock-bootloader-t3517806/page5

---

Wilderone said:
I think the fact you are not getting no reply from 'adb devices' is not a good start, are you sure you have all the correct drivers? Secondly do you have another computer to try it on?
Here is the minimal ADB:
http://xiaomitips.com/download/adb-setup-v1-4-3/
Here is the Unbrick Guide & install the drivers that are in it:
http://forum.xda-developers.com/red...redmi-note-4-unlock-bootloader-t3517806/page5
Sent from my Redmi Note 4 using Tapatalk
Click to expand...
Click to collapse
Thank you for your reply. At the time of your reply I am still fighting with the phone.
I have managed to get CN Dev back working again and I'm back to having No IMEI. It seems I may have wiped it during the earlier flash attempts.
Problem now is the people who gave me the phone to fix(family) threw out the box so I don't have the IMEI to reapply to the unit. Damn
Cannot then get Miui Account to load in because the phone won't confirm IMEI information.
Also battery running on CN is totally dead when running the OS. As soon as you pull the USB it powers down yet, like I said before, when not in ROM could happily reboot all day long or sit on the Fastboot screen.

---

Sounds like it may have wiped all your Engineering settings? just a guess, I'm assuming it's brand new so its strange that it has a battery problem?
As for the IMEI I just happen to have saved some links from the en.miui forums just in case I ever came across this problem but....you will need a valid IMEI.
http://en.miui.com/thread-411112-1-1.html
http://en.miui.com/thread-474409-1-1.html
Sent from my Redmi Note 4 using Tapatalk

---

The Device is basically brand new. Turned on Christmas Day by Nephew. I turned it on a few weeks before it and downloaded everything etc and did the updates. I don't think he would have been tinkering with ROM(all of them are not technically adept) and it wasn't damaged by all accounts .
Anyway. I've managed to Harvest an IMEI from an Old Phone, Installed this through a programme, connected my Mi Account, unlocked the bootloader and then flashed the correct Global Rom. Excellent.
No. The Battery is now the issue. It will not charge.
This is what I now need advice on. Anything I can do to get around this? Battery Hardware Tests say it's fine but It's not charging and only working on USB power.

---

What does your battery log look like?
Dial *#*#3646633#*#*
Sent from my Redmi Note 4 using Tapatalk

---

Aha, I see one major difference. I'm not showing a Battery Voltage
Battery Status: Charging (USB)
Battery Level: 0
Battery Scale: 100
Battery Health: Good
Battery Voltage: 0 mV
Battery Temperature: 37.0c
Battery Technology: Li-poly
Time since Boot: 31:00(not that it matters)
Interval of Info Record[1-100] 10 is in the changeable box
Battery Info Record: Start
--------------------------------------------
I'm going to surmise that the Voltage is the Problem here.

---

So its detecting the battery & health is good but at 0% & has no voltage lol.
What about under Hardware Testing/ Power/Charge Battery
Anyone can chime in here please as I'm not an electrician.
FYI, This was taken when I was plugged in.
Sent from my Redmi Note 4 using Tapatalk

---

Battery on USB and Battery with Original Charger plugged into wall outlet returns the same 0v Voltage.
When I plugged the device into the Wall and powered up it said 50% battery and within a second said 0% Battery and back to square One.

---

Im not sure what that means sorry, If it were me, in the predicament with your warranty I would be inclined to open it up & remove the battery for a while.
Depends if you are technically minded although it doesn't look too difficult.
https://youtu.be/6RBHqqF2Cg4
Failing that I would look on AliExpress for a new battery & see if it is worth the time & effort.
Also you may post some of this elsewhere in other forums to see if you can get an expert opinion.
Sent from my Redmi Note 4 using Tapatalk

---

Replaced battery. No luck. So it wasn't the battery.

---

BertieBaron said:
Replaced battery. No luck. So it wasn't the battery.
Click to expand...
Click to collapse
Sounds strange for a new device but it is possible it's developed a hardware problem.
I'm assuming you have tried different chargers, cables & had a physical look at the micro USB port for any signs of damage.
Have you had a good research on Google?
I found the following:
https://www.androidpit.com/how-to-fix-a-phone-that-won-t-charge
https://www.google.com.au/search?hl...rki9AO&gws_rd=ssl#gfe_rd=cr&gws_rd=ssl&xxri=1
See how you go & let me know.
Sent from my Redmi Note 4 using Tapatalk

---

Have I researched Google? Yes, many times every single day.
I did check and rub over the USB port to ensure that the connections should be fine and straight etc.
When I run a test on "Charger Plug In" using *#*#36443#*#* I can see Charger Current: Fluctuating between - numbers and 250mA so there's power coming from the USB Port into the Phone.
Using *#*#3646633#*#* I can see the Battery but without Voltage going into it.
Is the problem somewhere between power coming into the phone and getting to the battery?
When I removed the battery the phone will not power up by itself connected to AC Power

---

BertieBaron said:
Hi,
I've been tricking around with the Note 4 64gb since it entered into a Bootloop about 2 weeks ago and at one stage I got into a Chinese Rom but then it all fell apart. I cannot even get back to that point.
Phone will not switch on, will not enter into the phones ROM so I cannot change any of the settings within. Therefore the bootloader remains locked because I cannot access the phone however I know I can flash to the phone but why it will not restart is beyond me. Remains on Miui Screen on constant reboot after 30 seconds or so.
When I did get the CN Dev Rom(whatever it was as I got excited when it loaded and cannot remember how I did it) to load it was the phone disconnected from USB and below the powered by android came up. It would only go passed this when I connected the USB to power/pc as apparently the battery is bad. I know this couldn't be the case because the phone will happily sit for hours in Fastboot Mode(Rabbit) so maybe that Rom affected the hardware badly.
Using Smart Phone Flash Tool I can get
6.12 Global, 8.03 Global, 7.12 CN and 8.1.18 Roms to flash to the phone without any success of booting up normally or even showing the powered by android thing. These will all only work with the Cust.img file because otherwise it says File Too big.
It only flashes with everything ticked except preload. It will not work just by having system and boot selected. Error Codes are then 0Xc00500003
Using Mi Flash I can see the device connected in Fastboot mode and it says Flash Complete but the fact it only takes 1 second leads me to believe it does not actually flash anything because it won't reboot.
Using ADB and entering command with admin rights and typing adb devices(whilst in fastboot) doesn't show the device connected at all but refreshing Mi Flash does show the device. Very odd.
When I did get the Chinese Dev Rom to work on the phone I did notice that the IMEI had been wiped from the phone which was less than helpul also.
Can anybody help me get the phone back to a working state?
Thanks in advance
Click to expand...
Click to collapse
HI there. i have mi note 4 which is currently stuck on bootloop.can u tell me please how to boot up this device.i have done almost everything.my phone's condition is just like yours.

---

tahir786 said:
HI there. i have mi note 4 which is currently stuck on bootloop.can u tell me please how to boot up this device.i have done almost everything.my phone's condition is just like yours.
Click to expand...
Click to collapse
Your model is Redmi Note 4, right?
Which variant? The one with MediaTek chipset or the one with Qualcomm chipset?

---

BubuXP said:
Your model is Redmi Note 4, right?
Which variant? The one with MediaTek chipset or the one with Qualcomm chipset?
Click to expand...
Click to collapse
its a Qualcomm.

---

Hello
I received brand new Xiaomi Remi Note 4 (MediaTek) yesterday and I opened the package and wanted to boot the device up and I was shocked that the device is hanging on Mi logo and then restart or it does what known bootloop, the device enters fastboot mode and nothing else, I tasted the device with too many tools and methods so finally I made sure that there is a problem in internal storage or (eMMC) the data stored as RAW data as shown in the following result:
[VKZ5H6QKR4GEC6TC] *** Fastboot mode
(bootloader) max-download-size: 0x8000000
(bootloader) partition-size:flashinfo: 1000000
(bootloader) partition-type:flashinfo: raw data
(bootloader) partition-sizetp: 2b00000
(bootloader) partition-typetp: raw data
(bootloader) partition-size:userdata: 32000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: 1b000000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: c0000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cust: 20600000
(bootloader) partition-type:cust: raw data
(bootloader) partition-size:keystore: 800000
(bootloader) partition-type:keystore: raw data
(bootloader) partition-size:tee2: 500000
(bootloader) partition-type:tee2: raw data
(bootloader) partition-size:tee1: 500000
(bootloader) partition-type:tee1: raw data
(bootloader) partition-size:logo: 800000
(bootloader) partition-type:logo: raw data
(bootloader) partition-size:boot: 1000000
(bootloader) partition-type:boot: raw data
(bootloader) partition-size:lk2: 400000
(bootloader) partition-type:lk2: raw data
(bootloader) partition-size:lk: 400000
(bootloader) partition-type:lk: raw data
(bootloader) partition-size:nvram: 500000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-size:scp2: 100000
(bootloader) partition-type:scp2: raw data
(bootloader) partition-size:scp1: 100000
(bootloader) partition-type:scp1: raw data
(bootloader) partition-size:md3img: 500000
(bootloader) partition-type:md3img: raw data
(bootloader) partition-size:md1arm7: 300000
(bootloader) partition-type:md1arm7: raw data
(bootloader) partition-size:md1dsp: 400000
(bootloader) partition-type:md1dsp: raw data
(bootloader) partition-size:md1img: 1800000
(bootloader) partition-type:md1img: raw data
(bootloader) partition-sizeroinfo: 300000
(bootloader) partition-typeroinfo: raw data
(bootloader) partition-sizeemkeystore: 200000
(bootloader) partition-typeemkeystore: raw data
(bootloader) partition-size:seccfg: 800000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-sizerotect2: d78000
(bootloader) partition-typerotect2: ext4
(bootloader) partition-sizerotect1: 800000
(bootloader) partition-typerotect1: ext4
(bootloader) partition-size:metadata: 2000000
(bootloader) partition-type:metadata: raw data
(bootloader) partition-size:nvdata: 2000000
(bootloader) partition-type:nvdata: ext4
(bootloader) partition-size:nvcfg: 800000
(bootloader) partition-type:nvcfg: ext4
(bootloader) partition-size:expdb: a00000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-sizeara: 80000
(bootloader) partition-typeara: raw data
(bootloader) partition-size:recovery: 1000000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-sizereloader: 40000
(bootloader) partition-typereloader: raw data
(bootloader) off-mode-charge: 1
(bootloader) warranty: yes
(bootloader) unlocked: no
(bootloader) secure: yes
(bootloader) kernel: lk
(bootloader) product: nikel
(bootloader) version-preloader:
(bootloader) version: 0.5
I was able to repair system, userdata and cache partitions but that was useless, I'm not sure that the problem could be fixed by software solution or hardware one or it's initially and technical problem
Any one can post working bootloader log here using the command 'fastboot getvar all'

---

tahir786 said:
its a Qualcomm.
Click to expand...
Click to collapse
The bootloader is locked or unlocked?

---

BubuXP said:
The bootloader is locked or unlocked?
Click to expand...
Click to collapse
sadly,bootloader is locked.....
---------- Post added at 10:01 AM ---------- Previous post was at 09:55 AM ----------
BubuXP said:
The bootloader is locked or unlocked?
Click to expand...
Click to collapse
it is locked ...is there any way to wake that device up...when i connect that phone via edl mode in mi flashtool ,it always flashing such **** like hello packet and nothing happns..,,, and when i connect via fastboot it took about a second and success showing but nothing happens... plzzz tell me what should i do??

---

tahir786 said:
it is locked ...is there any way to wake that device up...when i connect that phone via edl mode in mi flashtool ,it always flashing such **** like hello packet and nothing happns..,,, and when i connect via fastboot it took about a second and success showing but nothing happens... plzzz tell me what should i do??
Click to expand...
Click to collapse
There is a solutions. You must open your phone to remove the battery, then you need to cut a USB cable to modify it.
If you are capable of this I can explain the procedure.