[FIX] Phone Bootlooping?

Search This thread
By:
Advanced…
K

krazykrivda

Senior Member
Sep 2, 2009
199
20
Philidelphia
CONFIRMED WORKING ON LINUX.. waiting to hear for windows, mac...

NOTE: Please keep track of what your doing, because if you DON'T know what you broke, your going to have a hard time fixing it.

I'd recommend NOT wiping DATA/factory restore unless you literally have NO other choice (see post 11)

That being said...

Assuming you know what change(s) you made before your bootloop, you are saying to yourself "If i could only boot up so i can UNDO it" ... this IS for you! :)

Directions:

  1. Battery Pull
  2. Put Battery Back
  3. Hold M button on keyboard then power
  4. Use vol - button to go to BP TOOLS (don't select yet)
  5. Connect via USB to computer with ADB
  6. In terminal on computer...
    Code: 
    adb wait-for-device shell
  7. On phone use vol + button to select BP Tools.. then wait for your terminal to get you into shell (this will happen while the phone is continuously bootlooping)
  8. according to djrbliss root method...
Code: 
mv /data/local/12m /data/local/12m.bak 
ln -s /data /data/local/12m
exit
9.
Code: 
adb reboot
10. wait for the power off then repeat steps 1-7
11. again thanks to djrbliss...

Code: 
rm /data/local/12m 
mv /data/local/12m.bak /data/local/12m 
mv /data/local.prop /data/local.prop.bak 
echo "ro.sys.atvc_allow_netmon_usb=0" > /data/local.prop 
echo "ro.sys.atvc_allow_netmon_ih=0" >> /data/local.prop 
echo "ro.sys.atvc_allow_res_core=0" >> /data/local.prop 
echo "ro.sys.atvc_allow_res_panic=0" >> /data/local.prop 
echo "ro.sys.atvc_allow_all_adb=1" >> /data/local.prop 
echo "ro.sys.atvc_allow_all_core=0" >> /data/local.prop 
echo "ro.sys.atvc_allow_efem=0" >> /data/local.prop 
echo "ro.sys.atvc_allow_bp_log=0" >> /data/local.prop 
echo "ro.sys.atvc_allow_ap_mot_log=0" >> /data/local.prop 
echo "ro.sys.atvc_allow_gki_log=0" >> /data/local.prop
exit
12. then again, repeat steps 1-7
13. You should have root, now go ahead and fix whatever needs fixing and reboot 1 final time


ENJOY :)

-KrazyKrivda
 
Last edited:
  • Like
Reactions: orangegator, cellzealot, jrobin and 2 others
J

Jonny9797

Member
May 22, 2009
6
1
I followed this exactly but could never get an adb connection. My drivers are good and my adb setup works just fine (I was using it earlier). And idea what I could be doing wrong?

Thank you so much for posting this btw!
 
D

Darksurf

Senior Member
Mar 15, 2010
213
11
you need to be in the android group and have adb properly installed and preferrably the current version. I use a gentoo based linux system so this stuff isn't an issue for me.

Ubuntu and debian based systems are a little different. I really dislike the package management system and Ubuntu separates users from the actual "linux" part of linux. its like linux for n00bs. Not saying its a bad distro, its just not my distro of choice.

But, if you are booting up your device correctly, you should be able to do adb start-server and then do a adb remount (if rooted) then push the files to /system/app/

if you have just ran updates, reboot your computer. If you aren't picking up the device, try using other ports (usb ports can go into a suspend mode to save power and sometimes don't like to wake up, it also happens in windows)
 
H

highcee

Member
Nov 9, 2008
28
4
Hemet Ca
please help me!

i am having the same problem. i can get into recovery, fastboot, AP, and BP modes, and my device manager sees the ADB interface, but i cannot execute commands. I get this error "C:\Program Files\Android\android-sdk\platform-tools>adb remount error: device not found". i have the latest SDK and moto drivers installed... is there anyway i can install an update.zip from recovery to get me out of the bootloop?
 
K

krazykrivda

Senior Member
Sep 2, 2009
199
20
Philidelphia
I've updated the OP.. there is no longer a "remount" part... so I'm not sure what you are doing.. again if you can join IRC ( webchat.freenode.com ... #krazyk is the chan ) i'd be more than happy to assist
 
R

royolpunk

Senior Member
Oct 31, 2010
317
6
San Jose, CA
guys, i need urgent help...
i did some **** by replacing the SystemUI.apk in RootExplorer and it started force closing. i rebooted and i started bootlooping i backed up the apk in a file on my sdcard called 'import'. now i tried BP tools but it wont recognize my device..i had adb working perfectly fine before. what should i do?
 
H

highcee

Member
Nov 9, 2008
28
4
Hemet Ca
Krivda, even in VM ubuntu it still doesn't see my phone... i have jdk, sdk installed... windows and ubuntu both see my xoom but the D3 is not being seen...
 
K

krazykrivda

Senior Member
Sep 2, 2009
199
20
Philidelphia
if the bootloop is caused due to an issue created in /data then then a factory reset will be fine (if you don't mind losing data).

HOWEVER, if the change it made is in /system.. the factory reset may reset your adb debugging option... which in turn will mean.. you will be stuck in a bootloop without the ability to access adb at all, in which case you are SOL until sbf or a way to run update.zip from recovery.
 
  • Like
Reactions: Rotkaeqpchen
onethreeteeh

onethreeteeh

Senior Member
Aug 21, 2010
73
12
yeah, I'm the same as royol and highcee... i guess it just gives us a double incentive to find an sbf
 
S

suzook

Senior Member
Jan 25, 2010
4,475
1,177
I know its tempting to foolnaround with files. But no one should be messing with anything till we get an sbf.
 
R

Rotkaeqpchen

Senior Member
Apr 30, 2008
485
86
I wanted to say THANK YOU to krazykrivda.

Because of your how-to I have successfully unbricked my Droid3 :))) THANKS
 
You must log in or register to reply here.

Similar threads

Hashcode
[WIP][KERNEL][KEXEC] JB ROMS For Droid 3 [03/06: BT/SPEAKERPHONE FIX]
Replies
2K
Views
491K
sd_shadow
sd_shadow
Hashcode
[SELFKANG ICS AOSP ROM] CM9/ICS for Droid 3 -- [BETA 2012-03-11]
Replies
2K
Views
378K
Endoroid
Endoroid
tspx23
Guide - Unlock XT862 for T-mobile/ATT
Replies
539
Views
212K
sd_shadow
sd_shadow
chevycam94
[ROM] Steel Droid: 5.0 Gingerbread - 5.7.894 - DEODEXED - 1-11-2013
Replies
423
Views
140K
T
tim-ranger
Deodexed
  • Locked
Can this Root Droid 3?
Replies
808
Views
140K
NeoS
NeoS

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 5
    K
    krazykrivda
    CONFIRMED WORKING ON LINUX.. waiting to hear for windows, mac...

    NOTE: Please keep track of what your doing, because if you DON'T know what you broke, your going to have a hard time fixing it.

    I'd recommend NOT wiping DATA/factory restore unless you literally have NO other choice (see post 11)

    That being said...

    Assuming you know what change(s) you made before your bootloop, you are saying to yourself "If i could only boot up so i can UNDO it" ... this IS for you! :)

    Directions:

    1. Battery Pull
    2. Put Battery Back
    3. Hold M button on keyboard then power
    4. Use vol - button to go to BP TOOLS (don't select yet)
    5. Connect via USB to computer with ADB
    6. In terminal on computer...
      Code: 
      adb wait-for-device shell
    7. On phone use vol + button to select BP Tools.. then wait for your terminal to get you into shell (this will happen while the phone is continuously bootlooping)
    8. according to djrbliss root method...
    Code: 
    mv /data/local/12m /data/local/12m.bak 
ln -s /data /data/local/12m
exit
    9.
    Code: 
    adb reboot
    10. wait for the power off then repeat steps 1-7
    11. again thanks to djrbliss...

    Code: 
    rm /data/local/12m 
mv /data/local/12m.bak /data/local/12m 
mv /data/local.prop /data/local.prop.bak 
echo "ro.sys.atvc_allow_netmon_usb=0" > /data/local.prop 
echo "ro.sys.atvc_allow_netmon_ih=0" >> /data/local.prop 
echo "ro.sys.atvc_allow_res_core=0" >> /data/local.prop 
echo "ro.sys.atvc_allow_res_panic=0" >> /data/local.prop 
echo "ro.sys.atvc_allow_all_adb=1" >> /data/local.prop 
echo "ro.sys.atvc_allow_all_core=0" >> /data/local.prop 
echo "ro.sys.atvc_allow_efem=0" >> /data/local.prop 
echo "ro.sys.atvc_allow_bp_log=0" >> /data/local.prop 
echo "ro.sys.atvc_allow_ap_mot_log=0" >> /data/local.prop 
echo "ro.sys.atvc_allow_gki_log=0" >> /data/local.prop
exit
    12. then again, repeat steps 1-7
    13. You should have root, now go ahead and fix whatever needs fixing and reboot 1 final time


    ENJOY :)

    -KrazyKrivda
    View
    4
    psouza4
    psouza4
    Anyone who has a bricked DROID 3 phone (Verizon only), I may have a solution for you.

    Requirements:
    • Windows platform
    • 7-zip installed (and know how to extract files)
    • ability to follow all instructions exactly
    • willingness to factory reset/lose data on their phone

    This unbrick method is NOT guaranteed to work, but it's very hopeful for most situations where other methods aren't working. If you are in desperate need of a fix, send me a PM and I'll link you some files to try.

    Lastly: I will not be walking through anyone step by step on how to run this procedure -- the included instructions should be more than enough for most people. If you read the instructions and are thoroughly confused, then this fix isn't for you.
    View
    1
    K
    krazykrivda
    if the bootloop is caused due to an issue created in /data then then a factory reset will be fine (if you don't mind losing data).

    HOWEVER, if the change it made is in /system.. the factory reset may reset your adb debugging option... which in turn will mean.. you will be stuck in a bootloop without the ability to access adb at all, in which case you are SOL until sbf or a way to run update.zip from recovery.
    View
    1
    psouza4
    psouza4
    ctheory83 said:
    Lay it on me man, I want my D3 back.
    Click to expand...
    Click to collapse
    Check your PM.


    sparkyman216 said:
    Worked perfectly. Like psouza4 will tell you read the instructions then do what they say. Brought me back from the dead.
    Click to expand...
    Click to collapse
    Thanks :D
    View

New posts