DroidForums.net is the original Verizon Android Forum! Registered Users do not see these ads. Please Register - It's Free!
Results 1 to 7 of 7

Thread: Think I bricked my phone doing manual root exploit

  1. Junior Droid
    toy4x4's Avatar
    Member #
    249986
    Join Date
    Feb 2012
    Location
    VA
    Posts
    29
    Phone
    Driod Bionic
    #1

    Think I bricked my phone doing manual root exploit

    Ok So I rooted my phone manually a while back but noticed that after a reboot I would get the shell $ prompt in ADB... So I would have to Re-exploit the /data/local.prop file and set the line ro.sys.atvc_allow_all_adb=0 to =1 then reboot and then ADB would have # root access again. Long story short I got tired of using echo command to rewrite the /data/local.prop file so pulled it and edited with wordpad then pushed it back down to the phone overwriting the original. After I powered the phone off and back on it just keeps looping at the Droid Animation.
    I think that I may have overwrote the file permissions for /data/local.prop file by pushing it with ADB shell as root # . Any ideas on how to access this file to fix the permissions?

    Here is a log of what I did:

    C:\Users\Jason\android-sdk-windows\platform-tools>adb shell
    root@cdma_targa:/# cat /data/local.prop
    cat /data/local.prop
    ro.sys.atvc_allow_netmon_usb=0
    ro.sys.atvc_allow_netmon_ih=0
    ro.sys.atvc_allow_res_core=0
    ro.sys.atvc_allow_res_panic=0
    ro.sys.atvc_allow_all_adb=0
    ro.sys.atvc_allow_all_core=0
    ro.sys.atvc_allow_efem=0
    ro.sys.atvc_allow_bp_log=0
    ro.sys.atvc_allow_ap_mot_log=0
    ro.sys.atvc_allow_gki_log=0
    root@cdma_targa:/#


    C:\Users\Jason\android-sdk-windows\platform-tools>adb pull /data/local.prop
    140 KB/s (288 bytes in 0.002s)

    C:\Users\Jason\android-sdk-windows\platform-tools>"%ProgramFiles%\Windows NT\Accessories\wordpad.exe" local.prop

    C:\Users\Jason\android-sdk-windows\platform-tools>adb push local.prop /data/local.prop
    72 KB/s (298 bytes in 0.004s)

    C:\Users\Jason\android-sdk-windows\platform-tools>adb shell
    root@cdma_targa:/# cat /data/local.prop
    cat /data/local.prop
    ro.sys.atvc_allow_netmon_usb=0
    ro.sys.atvc_allow_netmon_ih=0
    ro.sys.atvc_allow_res_core=0
    ro.sys.atvc_allow_res_panic=0
    ro.sys.atvc_allow_all_adb=1
    ro.sys.atvc_allow_all_core=0
    ro.sys.atvc_allow_efem=0
    ro.sys.atvc_allow_bp_log=0
    ro.sys.atvc_allow_ap_mot_log=0
    ro.sys.atvc_allow_gki_log=0
    root@cdma_targa:/#exit
    Last edited by toy4x4; 02-03-2012 at 01:23 PM.
  2.  
     
     
     
  3. Master Droid
    Vepaot's Avatar
    Member #
    246005
    Join Date
    Jan 2012
    Location
    KCMO
    Posts
    297
    Liked
    51 times
    Phone
    Droid Bionic
    #2
    I wouldn't say it's bricked just yet, but you are probably going to have wipe it and start over.

    The Aphotic Chaotic
    LG G2 VS980 (Verizon) [JB 4.3] PAC-man ROM
    Nexus 7 [JB 4.2.2] XenonHD
  4. Junior Droid
    toy4x4's Avatar
    Member #
    249986
    Join Date
    Feb 2012
    Location
    VA
    Posts
    29
    Phone
    Driod Bionic
    #3
    What are my options for fixing? Is there a way to load clockworks or something and manually edit the filesystem rather than cloneing over it with a new image?
  5. Droid Sensei
    LtKen's Avatar
    Member #
    31927
    Join Date
    Jan 2010
    Posts
    2,637
    Liked
    3 times
    Phone
    Rezound
    #4
    Your best bet is to pull down the SBF and restore it to stock. There should be a link and instructions in the development subforum.
  6. Junior Droid
    toy4x4's Avatar
    Member #
    249986
    Join Date
    Feb 2012
    Location
    VA
    Posts
    29
    Phone
    Driod Bionic
    #5
    Wierd but doing the a hard reset / factory data wipe and cache wipe didn't fix... It says formating /data... but guess that wasn't were the problem was???
    Guess I will try the RSD lite and find a FXZ file.
  7. Junior Droid
    toy4x4's Avatar
    Member #
    249986
    Join Date
    Feb 2012
    Location
    VA
    Posts
    29
    Phone
    Driod Bionic
    #6
    Okay so there is a lot more I wish I new about the layout of the file system on these phones but I got my phone working again by doing the Minimal FXZ here:
    [GUIDE] Return to stock or recover a brick using the new file format: FXZ

    Now off to recovering all my data and stuff... Then when that's done I will be moving on to do a nandroid backup so next time this won't be such a drag.
  8. Junior Droid
    toy4x4's Avatar
    Member #
    249986
    Join Date
    Feb 2012
    Location
    VA
    Posts
    29
    Phone
    Driod Bionic
    #7
    Just wanted to update this.... I've picked up quite a bit of knowledge since this post. It turns out the permissions were not the issue here. using adb to push it was not a problem... The file gets created with rw permissions for all users so the system should have no problem reading and overwriting this file at boot.
    -rw-rw-rw- root root 288 2012-04-06 14:58 local.prop

    Using wordpad from Microsoft to edit the file was the problem. (I also edited the /system/bin/mount_ext3.sh file to do the forever root at the same time I edited the local.prop file. So really the mount_ext3.sh file probably boot looped the phone before local.prop - who knows.) but here is the low down...

    Using MS products to edit files will write two end of the line / non printing characters to each line in the file. You can see this in notepad++ by going under view, show symbol, show all characters. MS products like to use both CR and LF characters equal to Hex 0d and 0a. Linux on the other hand only uses the LF (line feed) charater equal to hex 0a. Linux does not play well with files that have both CR and LF characters...
    Keep in mind that these end of the line characters are non printing and can't be seen in normal text editors with out using a hex dump tool or a programing utility like notepad++. So for those of you who use a windows pc to edit files on your phone beware!

Links

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

Similar Threads

  1. Upcoming OTA updates & Root exploit
    By rwking in forum Droid Bionic Hacks
    Replies: 4
    Last Post: 10-16-2011, 10:08 PM
  2. MotoGB Root exploit found!
    By Asphyx in forum Motorola Droid 2 Global
    Replies: 1
    Last Post: 08-25-2011, 01:19 PM
  3. Donation for development of a possible root exploit
    By rweb in forum Motorola Droid 3
    Replies: 5
    Last Post: 08-25-2011, 10:11 AM
  4. Root D2G permanently then uninstall the root exploit app?
    By sb56637 in forum Motorola Droid 2 Global Development
    Replies: 4
    Last Post: 06-02-2011, 07:24 PM
  5. Manual root plans y/n?
    By dgerej in forum Android Hacks and Help
    Replies: 8
    Last Post: 12-22-2010, 05:46 PM

Search tags for this page

adb bricked phone
,

android root brick

,

droid bionic root bricks phone

,
how to access the file system on a hard brick phone
,

manually rooting android

,

ro.sys.atvc allow all adb

,
ro.sys.atvc allow all adb=1
,
root android brick
,
root brick
,
root exploit for droid bionic
Click on a term to search our site for related topics.
Find us on Google+