I've bought my Redmi Note 2 one month ago: everything worked fine for the first 3 weekes, but in the last few days one bug came out. Every time I power off the phone it keeps rebooting showing the boot logo (mi.com) for few seconds: I have to pull of the battery to normally power off the phone.
When the phone is one there are no problems: everuthing works fine, no reboot.
I've installed all the lates xiaomi.eu weekly rom (now I'm on 5.10.22) but the problem persists... I've also tried the official stable rom (miui 6 6.7.11) but nothing changed...
What can I do? Is it a software problem or maybe hardware?
Hi, it seems that during shutdown something goes wrong and the phone reboot (like bsod restart in Windows)
So this must be a software problem. Please flash TWRP recovery from Fastboot and reinstall latest ZIP from Xiaomi.eu
(Remember to wipe data - dalvik and also system first)
Good luck
jack_21 said:
Hi, it seems that during shutdown something goes wrong and the phone reboot (like bsod restart in Windows)
So this must be a software problem. Please flash TWRP recovery from Fastboot and reinstall latest ZIP from Xiaomi.eu
(Remember to wipe data - dalvik and also system first)
Good luck
Click to expand...
Click to collapse
thanks jack 21!
I've already installed twrp from fastboot and installed several zip from xiaomi.eu and en.miui.com but the shutdown-reboot bug persists...
do I have to install a rom from fastboot... or do I have to wipe something (boot.img..?) from fastboot?
You have to wipe system, dalvik, cache
Then reinstall the zip file
Please for now don't touch boot because we don't know what may happen
jack_21 said:
You have to wipe system, dalvik, cache
Then reinstall the zip file
Please for now don't touch boot because we don't know what may happen
Click to expand...
Click to collapse
So.... installed twrp via fastboot; wiped everythin, installed latest xiaomi.eu zip; rebooted phone --> shutdown bug again..
p.s. even power off from recovery has the loop reboot bug..
Mmm don't know what to do in this case [emoji24]
I'll try installing other roms like smiui or AOSP... and if I don't find a solution maybe I'll send back my phone for assistance..
Related
Hey,
just flashed my Xperia Z2.
First unlocked, then flashed boot.img, then installed cyanogenmod and gapps.
Now the phone restarts but stays an boot screen. Since about 10 minutes.
I'm afraid of having an empty accu in the end.
What to do?
greez
Muffin
Muff(in) said:
Hey,
just flashed my Xperia Z2.
First unlocked, then flashed boot.img, then installed cyanogenmod and gapps.
Now the phone restarts but stays an boot screen. Since about 10 minutes.
I'm afraid of having an empty accu in the end.
What to do?
greez
Muffin
Click to expand...
Click to collapse
You probably forgot to wipe your data and cache before you installed Cyanogenmod.
I went through this same thing and even though I remembered to wipe data and cache before I installed Cyanogenmod, I didn't notice that during the wipe, CWM gave me an error mounting /data
What I had to end up doing to fix it all was:
1. FTF flash the original D6503 ROM to my device again.
2. Flash the boot.img for CWM.
3. Boot into CWM.
4. Wipe data and cache. (This time it worked no problem.)
5. Install Cyanogenmod
6. Install Gapps
7. Reboot
8. Enjoy the device.
sodaboy581 said:
You probably forgot to wipe your data and cache before you installed Cyanogenmod.
I went through this same thing and even though I remembered to wipe data and cache before I installed Cyanogenmod, I didn't notice that during the wipe, CWM gave me an error mounting /data
What I had to end up doing to fix it all was:
1. FTF flash the original D6502 ROM to my device again.
2. Flash the boot.img for CWM.
3. Boot into CWM.
4. Wipe data and cache. (This time it worked no problem.)
5. Install Cyanogenmod
6. Install Gapps
7. Reboot
8. Enjoy the device.
Click to expand...
Click to collapse
Hey thanks for your answer.
I didn't forgot to wipe.
I don't know my firmware version. Could the version be a problem?
I don't habe the D650(3) ROM...
Hm...:crying:
What is that FTF-Flash?
greez
See here: http://forum.xda-developers.com/showthread.php?t=2759934
You have to do this to recover from when you turn your phone into a brick.
EDIT: Oops, I just noticed I made a mistake up there. I actually flashed the D6503. NOT THE D6502. I have a D6503 device.
sodaboy581 said:
See here: http://forum.xda-developers.com/showthread.php?t=2759934
You have to do this to recover from when you turn your phone into a brick.
EDIT: Oops, I just noticed I made a mistake up there. I actually flashed the D6503. NOT THE D6502. I have a D6503 device.
Click to expand...
Click to collapse
Thank you very much.
I already got it.
Had to download ftf and flashtool.
Now everything works.
Have a nice day.
greez
Hi.
I have a slight problem with my device. Yesterday, after installing new update via updater my device cant boot the system. It stays on black screen with "MI" then "Powered by android" appears and nothing happens (waited couple of hours, but still nothing). I've tried to wipe cache, dalvik cache and factory reset via recovery - still nothing.
My device was flashed to have TWRP and then supersu - haven't used any other modifications.
Can anyone please help?
Cheers
Same here, TWRP backup also seems gone and cant manually install the update ROM nor the previous stable one.
My problem is solved.
I've flashed miui v.6.7.5 via miFlash and then installed new release through recovery and it works just fine.
Hi there
I'm totally happy with this device but had an issue today for no apparent reason.
I was using it normally, I put it in my pocket (80% battery) and when I took it out, it was stuck on MI logo screen. Maybe screen wasn't properly blocked or something. But I find all the situation quite shocking since I normally set manual updates for system, and apps, playstore, etc.
I haven't done any flashing opperation recently since I'm not much into this kind of things nor installed any new app recenlty. However the phone was rooted (previos bootloader unlocking) quite a while ago by using "magisk method keeping stock recovery for OTA".
The phone is permanently on with MI logo on screen. I tried using power off button for a long time to see if I could turn it off but it didn't work.
I have access to Fast Boot and to Stock Recovery (3.0).
Is there any way to enter the system again without losing all data? If not, can I recover data before "flashing" anything or before using "wipe all data" option in recovery mode?
Thank you for any possible answer.
Reinstall twrp and boot into twrp from Command Window and Flash Lazy flasher you'll be booted into Your phone
notoriouslion said:
Reinstall twrp and boot into twrp from Command Window and Flash Lazy flasher you'll be booted into Your phone
Click to expand...
Click to collapse
Thanks a lot mate, with this small guidance and not much idea about this things I flashed lazyflasher, wiped cache and dalvik (couldn't with stock recovery) and reboot into system.
Just out of curiosity, by flashing this lazyflasher have I done permanent changes on the system, or just through the first immediate boot they disappear?
What do you think could cause a bootlop if not an update? May an app installed a while ago causing something like this?
xdaforo said:
Thanks a lot mate, with this small guidance and not much idea about this things I flashed lazyflasher, wiped cache and dalvik (couldn't with stock recovery) and reboot into system.
Just out of curiosity, by flashing this lazyflasher have I done permanent changes on the system, or just through the first immediate boot they disappear?
What do you think could cause a bootlop if not an update? May an app installed a while ago causing something like this?
Click to expand...
Click to collapse
It happens sometimes for Unknown reasons and Lazyflasher will not harm your device and I would suggest you to flash Another Rom
xdaforo said:
Thanks a lot mate, with this small guidance and not much idea about this things I flashed lazyflasher, wiped cache and dalvik (couldn't with stock recovery) and reboot into system.
Just out of curiosity, by flashing this lazyflasher have I done permanent changes on the system, or just through the first immediate boot they disappear?
What do you think could cause a bootlop if not an update? May an app installed a while ago causing something like this?
Click to expand...
Click to collapse
Did you run any root apps ? If /system changes you need Lazyflasher I think. You could alternatively reflash the ROM (without wiping data)
Hello, I now have 8 days note 10 lite today I unlocked bootloader, installed TWRP via adb after that I installed lineage os and wiping data etc. After that I faced a bootloop and lineageos bootscreen doesnt go away after 15 minutes.
So I tried to reflash the rom again, but twrp isnt able to reinstall the rom. I then used miflash to get original rom again.
Started all over installed twrp, flashed lineage os after this install after reboot I get everytime back into TWRP and looked on my pc and all files suddenly are encrypted on my phone and cant get lineage os rom again on my phone..
So I used miflash again and decided to ask here first. Does anybody know if I maybe use a wrong TWRP or missed a step?
I really dont understand it, I tried it for a 3th time. Here is exactly what I did.
- installed TWRP through ADB (TWRP-3.4.0-0_Android11_Roms_AndroidHQ254)
- In TWRP put rom on my internal storage
- Wipe Dalvik, data and cache
- Install rom (TWRP-3.4.0-0_Android11_Roms_AndroidHQ254)
- data wipe (where I had to type yes to confirm)
- Reboot to system and then it doesnt do anything and goes back into TWRP where I cant do anything, and I have to flash original rom back through MiFlash.
I run now MIUI 12.0.2
Android 10
Try using orangefox recovery. And i think you have to wipe data before installing rom, not after it.
ApexPrime said:
Try using orangefox recovery. And i think you have to wipe data before installing rom, not after it.
Click to expand...
Click to collapse
Thank you, I was able to do it with Orangefox.
Hi, I've recently repaired my mido with a new screen after a fall. After this I tried some custom roms. Initially I managed to install lineage 18.1. After I switched to dotOS. From this point on, the phone restarts a few seconds after the launcher appears. To fix this I used MiFlah to install latest MIUI, formatted data, wiped everything, tried TWRP and Orangefox, tried other custom roms with no changes. Now only stock MIUI11 works. Other custom roms (included lineage) gets the phone continuously rebooting. Could be an hardware problem? What am I doing wrong? It is the first time in ages I have problems flashing ROMS .-.
Thanks.
gabritb01 said:
Hi, I've recently repaired my mido with a new screen after a fall. After this I tried some custom roms. Initially I managed to install lineage 18.1. After I switched to dotOS. From this point on, the phone restarts a few seconds after the launcher appears. To fix this I used MiFlah to install latest MIUI, formatted data, wiped everything, tried TWRP and Orangefox, tried other custom roms with no changes. Now only stock MIUI11 works. Other custom roms (included lineage) gets the phone continuously rebooting. Could be an hardware problem? What am I doing wrong? It is the first time in ages I have problems flashing ROMS .-.
Thanks.
Click to expand...
Click to collapse
The vendor partition could have some code/ file that persists stock ui or system
and make sure your phone was rooted before flashing custom rom
and also via twrp flashing. from what Ive seen flash in twrp before flash custom rom( https://www.google.com/search?client=firefox-b-d&q=disable+encryption+treble ) then flash the "verity and encryption disabler ,theres another one to re enable encyption only " then flash custom rom
after flashing custom rom reboot poweroff(switch phone off via twrp)
reboot into twrp and flash whatever else you need
now reboot to system and your phone should work fine
Thanks, it worked!
I did:
Flash last miui with miflash
Flash recovery
Flash you suggested zip
Format data
Flash lineage 17.1 (android10)
WIpe system, data, cache, art cache
Flash any android 11 ROM
gabritb01 said:
Thanks, it worked!
I did:
Flash last miui with miflash
Flash recovery
Flash you suggested zip
Format data
Flash lineage 17.1 (android10)
WIpe system, data, cache, art cache
Flash any android 11 ROM
Click to expand...
Click to collapse
Holy **** how did you come up with this.
Either the zip with Magisk somehow fixed it or installing the android 10 rom somehow. Either way doesn't make sense
flairepathos.info said:
The vendor partition could have some code/ file that persists stock ui or system
and make sure your phone was rooted before flashing custom rom
and also via twrp flashing. from what Ive seen flash in twrp before flash custom rom( https://www.google.com/search?client=firefox-b-d&q=disable+encryption+treble ) then flash the "verity and encryption disabler ,theres another one to re enable encyption only " then flash custom rom
after flashing custom rom reboot poweroff(switch phone off via twrp)
reboot into twrp and flash whatever else you need
now reboot to system and your phone should work fine
Click to expand...
Click to collapse
Didn't work for me,
- did all the steps , exactly - flashed stock fastboot , then flashed Android 10 based rom crDroid + pico gapps. worked fine for 2 hours or so .
but interesting enough , phone freezes then shutdown without restarting , then i would go and trun it back on , but fingerprint not working now
heroboy107 said:
Didn't work for me,
- did all the steps , exactly - flashed stock fastboot , then flashed Android 10 based rom crDroid + pico gapps. worked fine for 2 hours or so .
but interesting enough , phone freezes then shutdown without restarting , then i would go and trun it back on , but fingerprint not working now
Click to expand...
Click to collapse
i think somewhere in the process the persist partition gets damaged .
heroboy107 said:
i think somewhere in the process the persist partition gets damaged .
Click to expand...
Click to collapse
so if you have magisk you can use a zip file to chmod 744 or 644 (it may be "chmod root 744" )the /persist partiton and thatll mean only true root has access
so 7 is read write execute 6 is read and write 4 is read only 5 is read execute i forgot which number was execute only 1 maybe?
so play with the permissions or look in the root folder for boot.p or permissions.sh then you can modify in there the permissions, it can cause bootloop , so always keep an original copy or youll hae to reflash(DISCLAIMER)
so you can pull the file using adb+root / or a root explorer
Copy it to phone then edit then copy to SDCARD
reboot to twrp then use shell/terminal "chmod 777" the partition where the file is / or read write everything
then copy the file and overwrite the original