Database Users

Stock Nexus 6P bootloop after setup screen.

Hi guys, my 6P entered a bootloop a few days ago while changing the wallpaper (live earth from the Pixel).
I used the stock recovery for a full wipe, flashed the sock image but the issue remains, now I'm stuck on a bootloop as i enter the initial setup screen.
Any thoughts?

cyberon said:
Hi guys, my 6P entered a bootloop a few days ago while changing the wallpaper (live earth from the Pixel).
I used the stock recovery for a full wipe, flashed the sock image but the issue remains, now I'm stuck on a bootloop as i enter the initial setup screen.
Any thoughts?
Click to expand...
Click to collapse
Welcome to the club
Can you get into recovery mode at all?

Mysticodex said:
Welcome to the club
Can you get into recovery mode at all?
Click to expand...
Click to collapse
Yes, already did a factory reset through stock recovery.

As you can get into recovery, you're in a much better situation than I wise. Please try some of the fix methods listed in the first post here (the ones that include getting into recovery and/or TWRP recovery):
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921

https://www.androidfilehost.com/?fid=24728673521238129
Use the nexus toolkit but first boot to bootloader

Go into bootloader and use the following commands to fix the issue
adb shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384
adb shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384

fapste said:
Go into bootloader and use the following commands to fix the issue
adb shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384
adb shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
Click to expand...
Click to collapse
Thanks but it didn't fix my issue, i am still stuck on the setup screen and it is still rebooting

cyberon said:
Thanks but it didn't fix my issue, i am still stuck on the setup screen and it is still rebooting
Click to expand...
Click to collapse
Did you have Magisk or xposed or suhide when your phone bootlooped?

Nope, it was rooted with SuperSu though.

cyberon said:
Nope, it was rooted with SuperSu though.
Click to expand...
Click to collapse
I see that you had modified your phone with Pixel mod and you probably had tinkered with boot.img as well for removing the Corrupt message or something, Correct?
Try wiping EVERYTHING. Including data as well. Then flash the factory images for 7.1.1 from bootloader.
What's your manufacturing date, emmc date, ram name, how long have you been using your phone?

fapste said:
I see that you had modified your phone with Pixel mod and you probably had tinkered with boot.img as well for removing the Corrupt message or something, Correct?
Try wiping EVERYTHING. Including data as well. Then flash the factory images for 7.1.1 from bootloader.
What's your manufacturing date, emmc date, ram name, how long have you been using your phone?
Click to expand...
Click to collapse
Correct on both, already tried wipe and flashing image through adb and NRT.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

cyberon said:
Correct on both, already tried wipe and flashing image through adb and NRT.
Click to expand...
Click to collapse
Try flashing MIUI rom or some other skinned rom instead of AOSP compiled roms. That might help

fapste said:
Try flashing MIUI rom or some other skinned rom instead of AOSP compiled roms. That might help
Click to expand...
Click to collapse
CM13 didn't fix the issue either, will try MIUI.

boxguy1 said:
https://www.androidfilehost.com/?fid=24728673521238129
Use the nexus toolkit but first boot to bootloader
Click to expand...
Click to collapse
Already did, didn't fix the issue.

cyberon said:
CM13 didn't fix the issue either, will try MIUI.
Click to expand...
Click to collapse
CM 13 is AOSP based rom. MIUI or Firefox OS or other similar OS are not heavily based on AOSP so try your luck with them
---------- Post added at 09:10 AM ---------- Previous post was at 09:03 AM ----------
This is probably because of the corrupt boot.img or corrupt efs partition. I am not really sure myself. So first WIPE EVERYTHING. Including data partition. Then go to your bootloader and run these commands:
adb shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384
adb shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
Then flash MIUI or anyother non AOSP based rom.

fapste said:
CM 13 is AOSP based rom. MIUI or Firefox OS or other similar OS are not heavily based on AOSP so try your luck with them
---------- Post added at 09:10 AM ---------- Previous post was at 09:03 AM ----------
This is probably because of the corrupt boot.img or corrupt efs partition. I am not really sure myself. So first WIPE EVERYTHING. Including data partition. Then go to your bootloader and run these commands:
adb shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384
adb shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
Then flash MIUI or anyother non AOSP based rom.
Click to expand...
Click to collapse
I was able to run those commands on twrp but nothing changed.

I think my 6P might have something wrong with the /system partition, when i tried to resize the partition this error happened a few times, then it finally worked.

cyberon said:
Already did, didn't fix the issue.
Click to expand...
Click to collapse
Oh dam your in a bad situation have to tried a RMA or reflashing manually

You can boot to bootloader, as I can see the image posted above showing you in bootloader/download mode.
Download the Nexus factory image: https://developers.google.com/android/images#angler
Extract it until you see system.img, boot.img, etc.
Format each partition (or use erase if it complains it can't format), then flash the img file.
Code:
fastboot format system
fastboot flash system system.img
fastboot format cache
fastboot reboot-bootloader
Repeat the above code box steps for each image file. You can skip flashing recovery, userdata and cache images all together, however I'd still format/erase userdata/cache. Do not format/erase recovery unless you're confident you know what you're doing. I personally format recovery and flash the latest versioned image again, just to be sure.
I also do the same for radio and bootloader, but many people have yelled at me that that's super unsafe. I leave that in your hands.
Make sure you have a backup of your EFS partition!

starting into TWRP recovery after official Lineage os update.

I was trying to update nightly build ( 21st March released) of lineage os for ZUK Z1. But now it is only starting in TWRP recovery mode. What to do now? Please help me.
I have attached a screenshot of the error which I am getting while installing any build of lineage os.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

imcoder said:
I was trying to update nightly build ( 21st March released) of lineage os for ZUK Z1. But now it is only starting in TWRP recovery mode. What to do now? Please help me.
Click to expand...
Click to collapse
https://androidforums.com/threads/twrp-bootloop-fix-after-update-ota.922585/
Just go on this link and follow the steps given. There are two commands there, just type those commands in terminal of TWRP.. When your phone will boot properly first flash the latest TWRP 3.1.0, you will find it in original Android development section. Then only install the OTA. With TWRP 3.1.0 the OTA is installed automatically and there is no bootloop. All works fine....
---------- Post added at 01:38 PM ---------- Previous post was at 01:34 PM ----------
Incase if you are getting error 7 while installing official lineage OS then follow this
1. Download unofficial los 14.1 by orderkrieger
2. Clean install it...
3. Download official los 14.1
4. Clean install it...
There should be no error 7 while installing official los if you follow this.

I also faced the same issue and followed the above steps and it worked for me... Thanks for your help...!!!!

Hi
Hi what about the latest nightly 28march one how is it shall i download and install it oy

Here's the solution: https://www.youtube.com/watch?v=vSWC5MAB5cE

I found a similar issue by ZUK2 : https://forum.xda-developers.com/showpost.php?p=72298526&postcount=14
I used it on my ZUK1, but update the path according my filesystem...
This worked for me:
1. Boot to TRWP Recovery (power off, power on with volume up +volume down)
2. "Mount" -> mount "System" then back to main screen
3. "Advanced' -> "Terminal"
Type the following command:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
Then run it...
4. go back to main menu, then "Reboot" -> "Power off"
5. Switch on, and then should work normally...

Mammuth1 said:
I found a similar issue by ZUK2 : https://forum.xda-developers.com/showpost.php?p=72298526&postcount=14
I used it on my ZUK1, but update the path according my filesystem...
This worked for me:
1. Boot to TRWP Recovery (power off, power on with volume up +volume down)
2. "Mount" -> mount "System" then back to main screen
3. "Advanced' -> "Terminal"
Type the following command:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
Then run it...
4. go back to main menu, then "Reboot" -> "Power off"
5. Switch on, and then should work normally...
Click to expand...
Click to collapse
Worked like a charm. You saved my life with this one. I have no admin rights on my work PC so troubleshooting is difficult and I would be a dead man with no phone today. Many thanks!

tanmeshn said:
https://androidforums.com/threads/twrp-bootloop-fix-after-update-ota.922585/
Just go on this link and follow the steps given. There are two commands there, just type those commands in terminal of TWRP.. When your phone will boot properly first flash the latest TWRP 3.1.0, you will find it in original Android development section. Then only install the OTA. With TWRP 3.1.0 the OTA is installed automatically and there is no bootloop.
Click to expand...
Click to collapse
I cannot find a version 3.1 I used twrp-3.0.2-0-Z1, which is the latest from https://twrp.me/devices/zukz1.html and with this version the bug exists.

lg-optimus said:
I cannot find a version 3.1 I used twrp-3.0.2-0-Z1, which is the latest from https://twrp.me/devices/zukz1.html and with this version the bug exists.
Click to expand...
Click to collapse
https://forum.xda-developers.com/devdb/project/dl/?id=23595&task=get

Can I flash the new version 3.1 with the old version 3.0? Thanks!

lg-optimus said:
Can I flash the new version 3.1 with the old version 3.0? Thanks!
Click to expand...
Click to collapse
Yes,. You can flash twrp 3.1 over 3.0.2

Thanks, for unknown reasons I do not have any problems with 3 installations, so I am waiting to flash the newer verison.

tanmeshn said:
Yes,. You can flash twrp 3.1 over 3.0.2
Click to expand...
Click to collapse
I was unsure, what to use then, recovery or boot, what should I have used.
I decided to use fastboot
Code:
# /install/androidins/platform-tools/fastboot flash recovery /install/androidins/zuk_install/twrp-3.1.0-0-ham.img
target reported max download size of 1610612736 bytes
sending 'recovery' (10866 KB)...
OKAY [ 0.376s]
writing 'recovery'...
OKAY [ 0.150s]
finished. total time: 0.525s
# /install/androidins/platform-tools/fastboot reboot
rebooting...

Not working
Mammuth1 said:
I found a similar issue by ZUK2 : https://forum.xda-developers.com/showpost.php?p=72298526&postcount=14
I used it on my ZUK1, but update the path according my filesystem...
This worked for me:
1. Boot to TRWP Recovery (power off, power on with volume up +volume down)
2. "Mount" -> mount "System" then back to main screen
3. "Advanced' -> "Terminal"
Type the following command:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
Then run it...
4. go back to main menu, then "Reboot" -> "Power off"
5. Switch on, and then should work normally...
Click to expand...
Click to collapse
It says
Code:
dd: can't open '/dev/block/platform/msm_sdcc.1/by-name/misc' : No such file or directory
Once take a look at my files in dev/block/platform/ folder in this video

its saying there is no directory named dd
its saying there is no directory named dd

Mammuth1 said:
I found a similar issue by ZUK2 : https://forum.xda-developers.com/showpost.php?p=72298526&postcount=14
I used it on my ZUK1, but update the path according my filesystem...
This worked for me:
1. Boot to TRWP Recovery (power off, power on with volume up +volume down)
2. "Mount" -> mount "System" then back to main screen
3. "Advanced' -> "Terminal"
Type the following command:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
Then run it...
4. go back to main menu, then "Reboot" -> "Power off"
5. Switch on, and then should work normally...
Click to expand...
Click to collapse
Hi, thanks for your help, Why this happend?
I installed last lineageos nightly, gapps, all ok, but when I perform a factory reset from the options menu (of android) this happen, and only works performing this solution.

help anyone, stuck rebooting into recovery all the time, my phone is lenovo k3 note it happened after i tried factory reset on new installed rom.
getting error dd: can't open '/dev/block/platform/msm_sdcc.1/by-name/misc' : No such file or directory ... how can i fix that?

Moto G4 Plus
I have same issue in my Moto g4 plus......Does it reset every data present in the Phone ?
QUOTE=Mammuth1;74320886]I found a similar issue by ZUK2 : https://forum.xda-developers.com/showpost.php?p=72298526&postcount=14
I used it on my ZUK1, but update the path according my filesystem...
This worked for me:
1. Boot to TRWP Recovery (power off, power on with volume up +volume down)
2. "Mount" -> mount "System" then back to main screen
3. "Advanced' -> "Terminal"
Type the following command:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
Then run it...
4. go back to main menu, then "Reboot" -> "Power off"
5. Switch on, and then should work normally... [/QUOTE]
---------- Post added at 02:49 AM ---------- Previous post was at 02:38 AM ----------
Does it reset my phone data ??
Mammuth1 said:
I found a similar issue by ZUK2 : https://forum.xda-developers.com/showpost.php?p=72298526&postcount=14
I used it on my ZUK1, but update the path according my filesystem...
This worked for me:
1. Boot to TRWP Recovery (power off, power on with volume up +volume down)
2. "Mount" -> mount "System" then back to main screen
3. "Advanced' -> "Terminal"
Type the following command:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
Then run it...
4. go back to main menu, then "Reboot" -> "Power off"
5. Switch on, and then should work normally...
Click to expand...
Click to collapse

STUCK in TWRP

I was running ressurection remix rom and then i went to settings and did a factory reset.
then my phone rebooted and took me to twrp. it now boots into twrp every single time. tried installing a new fresh rom but didnt work. tried this thing too -
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
but didnt work ... please help, this is the only phone i have and will have for the next 3 years

Ob6801 said:
I was running ressurection remix rom and then i went to settings and did a factory reset.
then my phone rebooted and took me to twrp. it now boots into twrp every single time. tried installing a new fresh rom but didnt work. tried this thing too -
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
but didnt work ... please help, this is the only phone i have and will have for the next 3 years
Click to expand...
Click to collapse
Please have a look at here if it you as it seems same problem http://forum.xda-developers.com/zuk-z1/help/twrp-bootloop-installing-lineageos-t3570896/post72030892

Thanks!
my problem is solved

Ob6801 said:
Thanks!
my problem is solved
Click to expand...
Click to collapse
Please tell how you solved your problem. Remember to help each other that read that thread to find a solution. Thanks!

In TWRP, Go to advance, then go to Terminal and write down these codes one-by-one.
1. Code (Text): dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota Now press enter, and write down another code.
2. Code (Text): dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
Press enter again! Then go to main menu, go to Reboot and hit System. You're done, enjoy!

Ob6801 said:
I was running ressurection remix rom and then i went to settings and did a factory reset.
then my phone rebooted and took me to twrp. it now boots into twrp every single time. tried installing a new fresh rom but didnt work. tried this thing too -
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
but didnt work ... please help, this is the only phone i have and will have for the next 3 years
Click to expand...
Click to collapse
Try this this solved my problem may be it'll help you also
Search on you tube "phone reboots in twrp recovery"

TWRP bootloop after LineageOS OTA Update

Hi everyone,
I came into a TWRP bootloop and don't know how to get out. Here's how it happened:
I wanted to start the OTA Update of LineageOS and clicked on install after it was downloaded. The device restarted and booted into TWRP. Nothing else happened. So I decided to do a reboot from TWRP (without doing anything else).
Instead of booting LineageOS it booted again into TWRP.
Now I am caught in this bootloop. The phone always boots into TWRP instead of LineageOS.
Any idea how to fix this?

Solution found
Found a solution by myself:
executing
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
in TWRP terminal solved the issue.
Btw: TWRP recovery from an earlier backup and also clean installing LineageOS did not solve the Problem.

gnackwatschn said:
Found a solution by myself:
executing
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
in TWRP terminal solved the issue.
Btw: TWRP recovery from an earlier backup and also clean installing LineageOS did not solve the Problem.
Click to expand...
Click to collapse
I've encountered too the same problem (my phone version is the h870). Do you have any ideas on why this is happening? I managed to successfully install manually the ota package with twrp (/data/org.lineageos.updater/app_updates) but twrp still keeps looping

I have the same problem. I've tried installing lineage os ota update both via system settings and install manually via twrp but ended up with bootloop. Is there's a way to solve this?

dwisatriow said:
I have the same problem. I've tried installing lineage os ota update both via system settings and install manually via twrp but ended up with bootloop. Is there's a way to solve this?
Click to expand...
Click to collapse
Did you enter twrp via power off - key sequence or via the ota menu?

TWRP Loop
Mr-Kappa said:
Did you enter twrp via power off - key sequence or via the ota menu?
Click to expand...
Click to collapse
I am in the same boat, but about to try the fix above.
From what I've read elsewhere, this is a known bug in TWRP, and some useful person berated someone else for not knowing about having the correct bootloader (???), but when you're doing an update, that doesn't seem a logical thing?
In answer to your question Mr Kappa, when the system has downloaded the update, you tap to install, and it just does it's own thing, and hey presto, you're stuck in a twpr boot loop. This happens on all models it seems, from LG, Samsung, Moto, and lord only knows how many others, but the fix (and the only fix unless you leave USB debugging enabled) is this "dd if=" command, which is different for each make and model of phone.
***IF you have USB debugging enabled** - reboot to bootloader from TWRP (it will allow you to do this) then connect to your PC, open a command window (assuming you've got ADB/FASTBOOT installed) and type in "FASTBOOT CONTINUE". Apparently this works, but I've not enabled USB debugging so I can't try it (sensible security feature).

Try this one...
https://forum.xda-developers.com/lg-g6/development/recovery-twrp-3-1-x-t3627595

Mr-Kappa said:
Did you enter twrp via power off - key sequence or via the ota menu?
Click to expand...
Click to collapse
I entered it via "reboot recovery" menu on flashify apps.

thx bro its work!!!

I am sorry to be asking at the wrong forum, but does anyone know the dd command for LeEco Le 1s? I am stuck with the same problem and am not able to find any solution for my model anywhere
I would be grateful if someone was kind enough to help me out here.

I had the same issue and was able to fix as the OP said but I wanted to add a couple steps that might not be obvious to some newbs like me.
Turn on the phone and let TWRP load. Connect your phone to your computer via USB and open a terminal window on your computer. Type adb shell. Then:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
Worked for me on LG G6 US997.

gnackwatschn said:
Found a solution by myself:
executing
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
in TWRP terminal solved the issue.
Btw: TWRP recovery from an earlier backup and also clean installing LineageOS did not solve the Problem.
Click to expand...
Click to collapse
THANK YOU VERY MUCH !!!!!
YOU HELP ME TO FIXING MY PHONE DUDE (anyway, I came from google search and I'm using LineageOS 15 on my zenfone. Got a bootloop to TWRP and I try to do what you say and surprisingly it works ! :highfive

Thanks, I use this every time an OTA update breaks boot.
gnackwatschn said:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
Click to expand...
Click to collapse

Hey there, I'm having same problem.
I couldnt run the command in windows, but I did on Recovery terminal (OrangeFox), even tho the command runs properly, I still cant get out of Recovery.
Any idea?

gnackwatschn said:
Hi everyone,
I came into a TWRP bootloop and don't know how to get out. Here's how it happened:
I wanted to start the OTA Update of LineageOS and clicked on install after it was downloaded. The device restarted and booted into TWRP. Nothing else happened. So I decided to do a reboot from TWRP (without doing anything else).
Instead of booting LineageOS it booted again into TWRP.
Now I am caught in this bootloop. The phone always boots into TWRP instead of LineageOS.
Any idea how to fix this?
Click to expand...
Click to collapse
Yes, its the root that caused it. in twrp backup the data to mmc/otg/internal -> copy the lineage os zip file, gapps.. to a mmc or otg, in twrp -> wipe cahe,dalvik, data.. exept internal stor-> select storage, install lineage then gapps , dont install magisk/root zip, restore data, reboot system, install update -> reboot-> install rootzip.
next time unistall root then update.

gnackwatschn said:
Solution found
Found a solution by myself:
executing
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
in TWRP terminal solved the issue.
Btw: TWRP recovery from an earlier backup and also clean installing LineageOS did not solve the Problem.
Click to expand...
Click to collapse
im sorry i am a newbie here.I have the same problem with a xiaomi redmi 7,i was forced to re-install the whole rom with the newest update because of the bootloop.Where exactly do i execute this command? in my computer? or in fastboot mode?

I have the same problem but my pc does not detect my phone when Im trying to connect it and use ADB, I tried 2 different cables. Is there anything I can do or my phone turned into expensive brick?
EDIT: I ignored what my pc was telling me (that no device is connected) and simply went to adb and typed the code above. It works, thank you

jdrouill said:
Turn on the phone and let TWRP load. Connect your phone to your computer via USB and open a terminal window on your computer. Type adb shell. Then:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
Click to expand...
Click to collapse
Bro! You are my hero <3 Thank You so kindly much!

I just registered and only wanna say to you that "you're doing god's work". Thanks a lot. Keep em coming to this gem. Youre awesome. Thanks a lot!
gnackwatschn said:
Solution found
Found a solution by myself:
executing
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
in TWRP terminal solved the issue.
Btw: TWRP recovery from an earlier backup and also clean installing LineageOS did not solve the Problem.
Click to expand...
Click to collapse

Jonarius said:
im sorry i am a newbie here.I have the same problem with a xiaomi redmi 7,i was forced to re-install the whole rom with the newest update because of the bootloop.Where exactly do i execute this command? in my computer? or in fastboot mode?
Click to expand...
Click to collapse
yes, using your PC, try searching about adb and how it work first.
here: https://www.xda-developers.com/install-adb-windows-macos-linux/
It aint hard, after that you can execute these:
Turn on the phone and let TWRP load (Even though bootlooping and stuck on the TWRP logo). Connect your phone to your computer via USB and open a terminal window on your computer. Type adb shell. Then:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
Worked for me on Xiaomi 6X recently. Good luck!

Bootloop after install stock oreo

Hi guys.
I tried to install the oreo stock rom from this page in my xt1680:
https://forum.xda-developers.com/g5...o-twrp-flashable-stock-builds-coming-t3830482
But I am getting a bootloop.
How I can fix that?

AnasElInmortal said:
Hi guys.
I tried to install the oreo stock rom from this page in my xt1680:
https://forum.xda-developers.com/g5...o-twrp-flashable-stock-builds-coming-t3830482
But I am getting a bootloop.
How I can fix that?
Click to expand...
Click to collapse
This happened to me too. What I have to do is boot into the bootloader first then boot into the system. Hope this helps

You can do as JohnSmith8786 suggests, but you will have to do it every time, or you can boot into twrp recovery, hook up to your pc and using adb type
Code:
adb shell dd if=/dev/zero of=/dev/block/platform/soc/7824900.sdhci/by-name/misc

[email protected] said:
You can do as JohnSmith8786 suggests, but you will have to do it every time, or you can boot into twrp recovery, hook up to your pc and using adb type
Code:
adb shell dd if=/dev/zero of=/dev/block/platform/soc/7824900.sdhci/by-name/misc
Click to expand...
Click to collapse
What does the command do exactly?