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

Search This thread

jbarcus81

Senior Member
Jul 30, 2010
3,010
614
Marietta, OH
Samsung Galaxy Watch 5
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..
 
Last edited:

regalstreak

Senior Member
Jun 26, 2013
1,263
4,504
Mumbai
Attached the rar file here. Maybe would be helpful if mega goes down or something :') Nice post tho.
 

Attachments

  • MAC.rar
    128 bytes · Views: 84

aureliomilitao

Senior Member
Mar 12, 2013
1,061
56
Belo Horizonte
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

Senior Member
Sep 23, 2013
293
89
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

Senior Member
Mar 4, 2017
163
38
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

Senior Member
Oct 27, 2016
135
53
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

Senior Member
Mar 4, 2017
163
38
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

New member
Jan 26, 2019
3
0
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

Code:
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

Member
Dec 3, 2016
10
1
Trois-Rivières
github.com
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

Member
Mar 14, 2013
22
3
New York
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:

Code:
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:

Code:
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":

Code:
~ # ←[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?
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 55
    What is the persist partition?

    Persist is partition mounted at /persist. It has ext4 file system. DRM releated files, sensor reg file (sns.reg), wifi and bluetooth mac addresses are stored there.

    If you experience the following issues:
    • Can't access to internal storage.
    • No signal even after formating cache and fastboot flash cache.img
    • IMEI number is lost even after formating cache and fastboot flash cache.img
    • Boot loop on Lollipop 5.0 and above
    • You get "e: cannot mount /persist" in recovery
    then your persist partition have to be fixed.


    Requirements to proceed:

    • Ability to use adb command.
    • TWRP or Philz touch recovery.
    • Universal Naked Driver for recovery. (Windows users)
    • Root.

    Setting up adb, rooting and installing drivers are not part of this guide. If you have to do that then please use @rootSU's great thread to find the guides you need.

    Let's start!

    • Reboot your phone to recovery.
    • Connect USB cable.
    • Open CMD or Terminal application.
    • Enter following commands in CMD or Terminal application:

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

    You should be prompted to repair or fix errors. Keep pressing enter until the process finishes.
    If you are not prompted for repair or you still have problems then follow my instructions.


    • Get to that point again when you entered the adb shell command then type the following command:

    • make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/persist

    • Reboot your phone.

    Now all your problems should be gone now, but your wifi and bluetooth addresses should be fixed to prevent further problems or bugs.

    • Download this rar file.
    • Extract it.
    • (Linux users should enable show hidden files)
    • Open .bdaddr with a hexeditor.
    • You should see following:
    • Change the last three 00 to something else.
    • You can use 0-9 numerals and A-F letters.
    • Save the modified .bdaddr.
    • Open .macaddr with a hexeditor.
    • You should see the following:

    • Change the last three 00 to something else.
    • You can use 0-9 numerals and A-F letters.
    • Save the modified .macaddr.
    • Copy both files to your sdcard.
    • Enable USB debugging on the phone.
    • Open CMD or Terminal application. (If you closed it)
    • Enter following commands in CMD or Terminal application:

    • Grant access on the phone.
    • cd /persist
    • mkdir bluetooth wifi
    • chown bluetooth:system ./bluetooth
    • chmod 770 ./bluetooth
    • cp /sdcard/.bdaddr /persist/bluetooth
    • chown bluetooth:system ./bluetooth/.bdaddr
    • chmod 660 ./bluetooth/.bdaddr
    • chown wifi:system ./wifi
    • chmod 770 ./wifi
    • cp /sdcard/.macaddr /persist/wifi
    • chown wifi:system ./wifi/.macaddr
    • chmod 660 ./wifi/.macaddr

    Reboot your phone. All your problems should have gone now. You can delete .bdaddr and .macaddr from your sdcard.

    About the other files:

    SNS.reg will be regenrated, but the DRM releated files will not. Nobody ever complained about the missing DRM files, but I still want to make it possible to restore them. If anyone could make an md5 checksum about the files on the persist partition that would be great.
    3
    Great thread @bitdomo. Thanks for adding this to the forum. I added it to the root guides section of sticky roll-up

    Sent from my Nexus 5 using Tapatalk
    2
    nexus 5 *no baseband*no imei*no signal* solved

    yes, just press enter
    HOW I FIXED IT ::good:
    1- DOWNLOAD ANDROID -SDK
    2-ADB COMMAND ( I USED WINDOWS 7 )
    3-FLASHED PHILZ TOUCH RECOVERY ,,, TWRP RECOVERY IT WASN'T HELP ME
    4- ROOTED DEVICE
    5-I OPENED CMD
    6-HIT : adb shell / PRESS ENTER/
    7-e2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata /PRESS ENTER/
    8- KEEP PRESS ENTER UNTIL ITS FINISHED DONE
    I FIXED MY NEXUS 5 LIKE THAT
    ******* VERY BIG THANKS TO THE GENIUS *** bitdomo *** WHO'S MADE THIS THREAD
    ******* VERY BIG THANKS TO THE AWESOME **** *** rootSU *******
    ******* VERY BIG THANKS TO THE ******** ROLF2 *********
    THANK YOU GUYS BECAUSE OF YOU MY NEXUS 5 BACK TO LIFE I REALLY APPRECIATED
    1
    This should be very helpful, well done!
    1
    When I download the .rar file and extracted it, the file was empty. Im using a mac, does anybody still have that file or am I doing something wrong?
    You're doing it right. You need to show hidden files, though. The two files have a . as the first character. Mac (and UNIX and Linux) see . as a hidden file.

    Sent from my TARDIS