[GUIDE][FIX] Boot loop on Lollipop 5.0 and above (fix persist partition)

[jbarcus81]

Excuse my ignorance if this won't work, but would this fix my issue of not being able to obtain LTE when I get off Wifi? I've been having an issue since the Hydrogen fix (modem) that when on Wifi and I switch to cell data I instantly get H+ or H (On AT&T) and have to either cycle Airplane mode or reboot the phone and then instantly get LTE .. I used to not have to worry about it.. Was ALWAYS on LTE even with Wifi on unless I was in an area without LTE.. Now it's a battle.. Does this on any rom, stock or CM based..

 

[deisonribeiro14]

This work in android 7.0?
I have a Xiaomi Mi5 and the wifi don't turning on.
Thanks for now.

 

[regalstreak]

Attached the rar file here. Maybe would be helpful if mega goes down or something :') Nice post tho.

 

[aureliomilitao]

How fix this error in image

http://imgur.com/a/uIcfq

 

[aureliomilitao]

adb shell
e2fsck /dev/block/platform/msm_sdcc.1/by-name/persist

no appear nothing comand , no responsive in CMD

i try all metods for fix boot lopping

my nexus5 no install recovery, no wipes , only enter fastboot and logo google

 

[mrfrantastic]

hy guys
im not really a noob to this , but this method those not work for me ..
everytime i typed the commend line it said that the journal still still has errors and does nothing after ..
please help .. thank you

its shows this
/dev/block/platform/msm_sdcc.1/by-name/userdata: ********** WARNING: Filesystem
still has errors **********

@bitdomo

Having the same issue. Does this seems to be a hardware error then?

 

[xsacter]

My Nexus 5 wifi died a couple months ago, and it hasn't worked since. I think it's a hardware issue but could someone help me out? I've let it die but when I charge it back up about 2 weeks later still doesn't work

 

[Locura18]

My Nexus 5 wifi died a couple months ago, and it hasn't worked since. I think it's a hardware issue but could someone help me out? I've let it die but when I charge it back up about 2 weeks later still doesn't work

Don't sweat it. Sounds like your Wi-Fi chip is out. You might also get hi battery drain. Some other random issues. Only solution I know is to change the Wi-Fi chip if you can get it. If not replace the mother board altogether.

 

[xsacter]

Don't sweat it. Sounds like your Wi-Fi chip is out. You might also get hi battery drain. Some other random issues. Only solution I know is to change the Wi-Fi chip if you can get it. If not replace the mother board altogether.

Most likely I'll have to change the Mobo all together. Thanks anyways

 

[phoenixDBP]

I tired the steps but wifi still having issues.
When I look into the root browser, the wifi folder I created is not present.
And one thing, when I entered su, it said not found. Is that the reason?
If so, how can I fix it?
I rooted my Nexus 5 with custom rom Paranoid androind 7.3.1(Nougat 7.1.2) using Magisk v18.0
I looked in Magisk Manager -> SuperUser, to check if shell needs toggle to enable root, but didnt find the entry for shell.
Superuser Access is set to "Apps and ADB" in Magisk Manager

C:\windows\system32>adb shell
~ # ←[6ne2fsck /dev/block/platform/msm_sdcc.1/by-name/persist
e2fsck /dev/block/platform/msm_sdcc.1/by-name/persist
e2fsck 1.42.9 (28-Dec-2013)
/dev/block/platform/msm_sdcc.1/by-name/persist: clean, 17/1024 files, 1111/4096
blocks
~ # ←[6n
~ # ←[6nmake_ext4fs /dev/block/platform/msm_sdcc.1/by-name/persist
make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/persist
Creating filesystem with parameters:
    Size: 16777216
    Block size: 4096
    Blocks per group: 32768
    Inodes per group: 1024
    Inode size: 256
    Journal blocks: 1024
    Label:
    Blocks: 4096
    Block groups: 1
    Reserved block group size: 7
Created filesystem with 11/1024 inodes and 1102/4096 blocks
~ # ←[6n
C:\windows\system32>adb shell
~ # ←[6nsu
su
/sbin/sh: su: not found
~ # ←[6ncd /persist
cd /persist
/persist # ←[6nmkdir wifi
mkdir wifi
/persist # ←[6nls
ls
wifi
/persist # ←[6nchown wifi:system ./wifi
chown wifi:system ./wifi
/persist # ←[6nchmod 770 ./wifi
chmod 770 ./wifi
/persist # ←[6ncp /sdcard/.macaddr /persist/wifi
cp /sdcard/.macaddr /persist/wifi
/persist # ←[6nchown wifi:system ./wifi/.macaddr
chown wifi:system ./wifi/.macaddr
/persist # ←[6nchmod 660 ./wifi/.macaddr
chmod 660 ./wifi/.macaddr
/persist # ←[6nls
ls
wifi
/persist # ←[6n
C:\windows\system32>

​

 

[NatoBoram]

I was not able to restore a Mac address with the .macaddr file. I used Jeex to edit the file, the permissions seems fine, the file is in the right place, yet every reboot I have a different Mac address.

 

[Ayni]

I'm in need of an spare phone and I only have this Nexus 5 stuck on "Google logo" eternal BootLoop. So I've been trying to fix it with no avail.

I've tried flashing the factory img and LineageOS using TWRP latest version and also a couple of older ones. But it continues to BootLoop..

I've found this thread and felt hopeful as it seemed to have helped so many out there. So I prepared everything just like the OP said, including installing NakedDriver(uninstalling/deleting previous one + restarting pc). But it seems I just can't get root access, as when I run adb shell su, it returns:

adb shell su
/sbin/sh: su: not found

I've tried rooting with "CF-Auto-Root-hammerhead-hammerhead-nexus5" and also downloading latest Chainfire SuperSu Zip (v2.82) and flashing (install) through recovery. Both ways when it reboots it goes back to the deadly bootloop.

However I went ahead and tried the adb shell commands:

adb shell
~ # ←[6ne2fsck /dev/block/platform/msm_sdcc.1/by-name/persist
e2fsck 1.42.9 (28-Dec-2013)
/dev/block/platform/msm_sdcc.1/by-name/persist: clean, 12/1024 files, 1103/4096
blocks
~ # ←[6n

That's all, no prompts to repair anything.. so I go ahead and try the next command "make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/persist":

~ # ←[6nmake_ext4fs /dev/block/platform/msm_sdcc.1/by-name/persist
Creating filesystem with parameters:
    Size: 16777216
    Block size: 4096
    Blocks per group: 32768
    Inodes per group: 1024
    Inode size: 256
    Journal blocks: 1024
    Label:
    Blocks: 4096
    Block groups: 1
    Reserved block group size: 7
Created filesystem with 11/1024 inodes and 1102/4096 blocks
~ # ←[6n

When I reboot it goes again into bootloop!

What am I missing? Do you guys think it's that I effectively have no Root? How to Root it while it's stuck on bootloop?
Is this something that's still fixable or should I stop wasting my time?