Hello and first of all thank you for reading. I've a strange problem with my redmi note 3 pro.
i was chatting with it but suddenly it starts to have bootloops (mi logo flashes). I tried to restore it with recovery (it was still not unlocked) but nothing to do. So i flashed rom with the miflash and in edl mode (i tried latest stable, latest developer and first developer fastboot roms) but the bootloop was still here. So i tried to unlock bootloader with unoficial method (official says that my phone is linked to another account, absolutely false but i will come to this point later). Tried to flash zip with TWRP but still bootloops. I was tired and i tried cm13. It worked, phone boots and i was absolutely happy but dialer crashes when i receive calls. So i understand that my phone wants the boot.img of android 6.0 to not go into bootloop. I flashed (via TWRP) latest 6.0 based miui rom and it worked but still with dialer problem. I tried to unlock it but still no go. So i decided to try to sign out of my miaccount (yeah it was still there after flash with miflash in EDL mode, don't know why!) becasue it asked me to enter my password to use the phone when i boot miui 6.0 for the first time.
SO i Have absolutely no idea on what i should do. Phone bootloops when i use a 5.1 based rom, and with 6.0 dialer crashes. That's the strangest thing ever.
I tried many fastboot roms in edl and in fastboot, i tried custom recoveries and stock one, tried to unlock and relock bootloader. I tried basically everything (wipes, system-data-cache-internal) EVERYTHING!
please if you hava any idea i will be glad to try!
I've tried to restore a backup from another RN3P but still bootloop. Maybe is somethig related to the boot.img? changing it makes the phone boot.
Go to a Mi service center. They might be able to help you.
Which gapps you installed after you flashed cm13...
When i used stock package, my dialer was also crashing but when i used micro package, the problem was solved....
claudios91 said:
Hello and first of all thank you for reading. I've a strange problem with my redmi note 3 pro.
i was chatting with it but suddenly it starts to have bootloops (mi logo flashes). I tried to restore it with recovery (it was still not unlocked) but nothing to do. So i flashed rom with the miflash and in edl mode (i tried latest stable, latest developer and first developer fastboot roms) but the bootloop was still here. So i tried to unlock bootloader with unoficial method (official says that my phone is linked to another account, absolutely false but i will come to this point later). Tried to flash zip with TWRP but still bootloops. I was tired and i tried cm13. It worked, phone boots and i was absolutely happy but dialer crashes when i receive calls. So i understand that my phone wants the boot.img of android 6.0 to not go into bootloop. I flashed (via TWRP) latest 6.0 based miui rom and it worked but still with dialer problem. I tried to unlock it but still no go. So i decided to try to sign out of my miaccount (yeah it was still there after flash with miflash in EDL mode, don't know why!) becasue it asked me to enter my password to use the phone when i boot miui 6.0 for the first time.
SO i Have absolutely no idea on what i should do. Phone bootloops when i use a 5.1 based rom, and with 6.0 dialer crashes. That's the strangest thing ever.
I tried many fastboot roms in edl and in fastboot, i tried custom recoveries and stock one, tried to unlock and relock bootloader. I tried basically everything (wipes, system-data-cache-internal) EVERYTHING!
please if you hava any idea i will be glad to try!
Click to expand...
Click to collapse
I had a similar issue a while ago with a friend's Samsung. The service center people said that it was a RAM issue..
. If you can return the phone to wherever you bought it from, Do it ASAP and get another model...
Otherwise you might have to go to a service center and tell them exactly what you are facing. Before that i must suggest
Try installing a custom Kernel perhaps and see if it still bootloops
For every worst case software/firmware failure, full rom flash would be the one to solve it. Based on your story, it must be the hardware problem. So if possible, bring it to your nearest service center..
i really thank you for the reply but this phone comes from china and i'm in Italy so I have no warranty at all (including the fact i changed the screen) I think i will use it as an ipod. I've posted a log of the kernel bootloop so maybe someone with skills could help me!
that's the log! http://pastebin.com/b3CVcBAT
Related
I have a Z5C(E5803) that was originally able to unlock the bootloader and let me flash ROMs, specifically the Cyanogen ROM that CTXz has been working on. I ran out of power and got stuck in some kind of nasty bootloop yesterday that prompted me to re-flash boot.img and TWRP.
After I did these things I left it charging for a few hours and it was able to boot into TWRP where I then restored it to a backup of the basic Xperia pre-loaded ROM.
This all worked fine, thought I could boot into TWRP and just flash the Cyanogen zip again. I can get into TWRP just fine but I attempt to flash Cyanogen I get an "ERROR 7"
I have since done several wipes, gotten into the bootloader settings by entering that code in the dialer and have seen that bootloader unlock = no. I distinctly remember bootloder unlocking being allowed the first time I installed CM on my device, what could have caused this?
I was able to use it with fastboot anyway and install CM13 again, maybe this was a bug?
When I tried using oem unlock command with fastboot it said my device was already rooted even though I had just restored from a backup, and then I just proceeded normally from there.
use CM13 official Recovery to FLASH CM13.
also i don't think so twrp3.0.2 is out there for z5c. are you using any other variants Twrp? (YUGA ? )
Lets start off with telling you i am a newbie and was just following tutorials without really knowing what i was doing.
That said, i tried to install a custom ROM but got an error (7) in TWRP. Decided to reflash my old rom and update TWRP using the official TWRP app.
So i did that but when i wanted to boot into recovery it was stuck on the oneplus screen. I went into fastboot and typed fastboot oem unlock because i thought i could flash TWRP that way if the bootloader was unlocked.
When i tried to restart it gave me nothing but the oneplus screen, even the bootloader wont start. I shut it off completely and now it doesn't give me anything at all - just black.
Can someone help me out?
EDIT:
Issue resolved using THIS. Tyvm
Firstly, I try to unlock the bootloader and flash cm14 rom with the unofficial method (without applying from the mi.com). Unfortunately, it becomes soft brick. then I make the deep flash cable to enter the 9008 mode and use mi flash tool to flash the miui rom in it. However, after successful flashing, the mobile either cannot open or just showing mi logo for forever. I have tried at least 10+ miui rom (global, chinese and develop with different versions). Even I exchange the recovery .img to try to enter the twrp, it still cannot enter, I duno what is the problem, finally, i download a Rom and flash it, I can enter the recovery (twrp) but still cannot enter the miui. Now I can flash cm14.1 in it. But I just wanna know why? i have searched many posts saying taht just enter 9008 mode and flash the miui rom and everything is ok, but what i get is bootloop or dead.
turn off driver signature while flashing miui official rom
Simoom Sadik said:
turn off driver signature while flashing miui official rom
Click to expand...
Click to collapse
I did turn off on several trial of flashing, and the result is the same.
i am wondering if there is any lock by xiaomi to prevent flashing with the latest rom. That means after flashing the latest rom, your phone will be locked and no more other official rom can be flashed using 9008 method.
After my phone randomly bootlooped after almost 2 years i wanted to install a new custom rom. I have a redmi Note 3 SE (kate). So far only nitrogen os with oreo has worked. Every other custom rom is producing bootloop. On nitrogen my fingerprint does not work and some buttons don't do what I expect them to (left one is not go back, middle one is recent apps for some reason). So I really want to instll a different rom.
What I usually do to install the roms:
Factory reset -> Install Rom -> Install Gaps -> Reboot -> Bootloop (Except nitrogen oreo)
What am I doing wrong here? I am really getting desperate here.
ll9X said:
After my phone randomly bootlooped after almost 2 years i wanted to install a new custom rom. I have a redmi Note 3 SE (kate). So far only nitrogen os with oreo has worked. Every other custom rom is producing bootloop. On nitrogen my fingerprint does not work and some buttons don't do what I expect them to (left one is not go back, middle one is recent apps for some reason). So I really want to instll a different rom.
What I usually do to install the roms:
Factory reset -> Install Rom -> Install Gaps -> Reboot -> Bootloop (Except nitrogen oreo)
What am I doing wrong here? I am really getting desperate here.
Click to expand...
Click to collapse
First Update to latest twrp 3.2.1 .
and flash latest global beta firmware. If u officially unlock then flash firmware with emmc file.
If u unofficially unlocked then flash without emmc file.
https://forum.xda-developers.com/redmi-note-3/development/firmware-hmnote3proglobal-t3574361
ll9X said:
After my phone randomly bootlooped after almost 2 years i wanted to install a new custom rom. I have a redmi Note 3 SE (kate). So far only nitrogen os with oreo has worked. Every other custom rom is producing bootloop. On nitrogen my fingerprint does not work and some buttons don't do what I expect them to (left one is not go back, middle one is recent apps for some reason). So I really want to instll a different rom.
What I usually do to install the roms:
Factory reset -> Install Rom -> Install Gaps -> Reboot -> Bootloop (Except nitrogen oreo)
What am I doing wrong here? I am really getting desperate here.
Click to expand...
Click to collapse
Plz factory reset in rec not in system mode.
tonyyang- said:
Plz factory reset in rec not in system mode.
Click to expand...
Click to collapse
Yeah that's what I did.
naik2902 said:
First Update to latest twrp 3.2.1 .
and flash latest global beta firmware. If u officially unlock then flash firmware with emmc file.
If u unofficially unlocked then flash without emmc file.
https://forum.xda-developers.com/redmi-note-3/development/firmware-hmnote3proglobal-t3574361
Click to expand...
Click to collapse
I already tried twrp 3.2.1. Yesterday I also tried flashing global beta firmware. I unlocked mine unfoficially so I flashed without emmc. Unfortunately that didn't change anything. After that I just flashed with emmc (wasn't completely sure if I unlocked it unofically). As a result I couldn't start my os and twrp anymore. Bootloader was locked again. I unlocked it in edl mode again and flashed RR. After that it finally worked. I was so surprised. I have no idea why flashing without emmc didn't change anything but after a lot of struggle it worked at least.
Thanks for your reply that seems to be the correct solution. It would be kind of nice if more custom rom threads would mention that you need a new firmware because some people like may not know that.
ll9X said:
I already tried twrp 3.2.1. Yesterday I also tried flashing global beta firmware. I unlocked mine unfoficially so I flashed without emmc. Unfortunately that didn't change anything. After that I just flashed with emmc (wasn't completely sure if I unlocked it unofically). As a result I couldn't start my os and twrp anymore. Bootloader was locked again. I unlocked it in edl mode again and flashed RR. After that it finally worked. I was so surprised. I have no idea why flashing without emmc didn't change anything but after a lot of struggle it worked at least.
Thanks for your reply that seems to be the correct solution. It would be kind of nice if more custom rom threads would mention that you need a new firmware because some people like may not know that.
Click to expand...
Click to collapse
Lol..you are cute.
You should know that officially unlocking and unofficial unlocking is not same thing.
Emmc file is bootloader update. Flashing firmware with emmc file will update both firmware and bootloader partition
Only officially unlocked devices can flash emmc file without bricking thier phones and relocking. So better officially unlock ur device to update emmc in future.
Which unofficial method did you try that worked?
I dont think Xiaomi will fix my unlock issue any soon so maybe will try other methods
Possibly i got issues with my account since been using the same with old device as well and messed up a lot
Selling my F1 phone. No matter what I do, on first boot, LineagOS asks for the pattern I used.
Tried wiping everything with TWRP 3.3.0 official. System, data, everything really - installing LOS from SD.
Basically, installing vendor, LOS, gapps - boots fine, then asks for the pattern.
Adding DFE to the flashing sequence didn't do much.
What to do to make the phone "brand new" and forget my pattern?
I also got this.. Im in siberia rom sometimes when i reboot my phone it asks the pattern i used so i just use the pattern lock i put. It then proceeds booting up but i never flashed dfe my twrp is unofficial twrp with decryption support
Yeah, it never bothered, but it might bother the new owner.
It's hard to believe that it's actually impossible to remove. I don't care about wiping clean, just need to make sure there's no lock.
Did you try flashing miui official rom via miflash ? I once done this method on redmi 3 on my friends phone since he got locked out of his phone . he did not remember his xioami id or password but miflash method worked for him
jithutty said:
Did you try flashing miui official rom via miflash ? I once done this method on redmi 3 on my friends phone since he got locked out of his phone . he did not remember his xioami id or password but miflash method worked for him
Click to expand...
Click to collapse
Thought if that, for some reason no version of miflash worked for me.
Mmm google or youtube search..or just go to mi service if its the only way
some amd procesor not working with miflash,
guys any solution for this
after flashing lineage i got this encryption pattern . I tried flashing Disable-Force-Encryption-Treble.zip
and still get this !!
http://www.mediafire.com/file/8o07v77cntpywpn/ResetScreenLock.zip/file
flash it via TWRP