[boot.img] obsolete please lock

Status
Not open for further replies.
Search This thread
By:
Advanced…
HQRaja

HQRaja

Retired News Writer
Jan 27, 2008
491
433
Islamabad
hqraja.com
A colleague wrote a post at our blog a few hours back based on the guide here. I just got done with heavily editing it based on the response here and publishing it. I also added a manual method involving booting with the insecure boot image and copying the required files to the appropriate paths directly. I don't have a Nexus 4 at the moment but in my personal experience with Nexus devices including Galaxy Nexus on Jelly Bean 4.2, this method *should* work as long as you can boot using the insecure boot image, even if the recovery method fails to work. The full step-by-step instructions should be easy to follow for anyone. Hope it helps. Here is the link:
http://www.addictivetips.com/android/root-google-nexus-4-install-clockworkmod-recovery/

PS: If it works for you, please do confirm here, thanks.
 
Last edited:
  • Like
Reactions: Ameri-CAIN
S

Stryder5

Senior Member
Mar 2, 2009
3,352
1,144
Texas
HQRaja said:
A colleague wrote a post at our blog a few hours back based on the guide here. I just got done with heavily editing it based on the response here and publishing it. I also added a manual method involving booting with the insecure boot image and copying the required files to the appropriate paths directly. I don't have a Nexus 4 at the moment but in my personal experience with Nexus devices including Galaxy Nexus on Jelly Bean 4.2, this method *should* work as long as you can boot using the insecure boot image, even if the recovery method fails to work. The full step-by-step instructions should be easy to follow for anyone. Hope it helps. Here is the link:
http://www.addictivetips.com/android/root-google-nexus-4-install-clockworkmod-recovery/

PS: If it works for you, please do confirm here, thanks.
Click to expand...
Click to collapse

I tested the recovery posted on your site and it has the same error I posted earlier about it not mounting the /sdcard path.
 
S

Stryder5

Senior Member
Mar 2, 2009
3,352
1,144
Texas
HQRaja said:
A colleague wrote a post at our blog a few hours back based on the guide here. I just got done with heavily editing it based on the response here and publishing it. I also added a manual method involving booting with the insecure boot image and copying the required files to the appropriate paths directly. I don't have a Nexus 4 at the moment but in my personal experience with Nexus devices including Galaxy Nexus on Jelly Bean 4.2, this method *should* work as long as you can boot using the insecure boot image, even if the recovery method fails to work. The full step-by-step instructions should be easy to follow for anyone. Hope it helps. Here is the link:
http://www.addictivetips.com/android/root-google-nexus-4-install-clockworkmod-recovery/

PS: If it works for you, please do confirm here, thanks.
Click to expand...
Click to collapse

IT WORKED! Well, the manual method worked that involves ADB.

Used these files:
http://www.mediafire.com/?az44dwrww0808j3

With these commands:
Code: 
adb shell mount -o remount,rw /system
adb push su /system/bin/
adb push Superuser.apk /system/app/
adb push busybox /system/xbin/
adb shell
su
chmod 06755 /system/bin/su
chmod 0644 /system/app/Superuser.apk
chmod 04755 /system/xbin/busybox
cd /system/xbin
busybox --install /system/xbin/
exit
exit

I can now confirm I have root!
 
  • Like
Reactions: HQRaja and Ameri-CAIN
S

Stryder5

Senior Member
Mar 2, 2009
3,352
1,144
Texas
HQRaja said:
YES! Gonna post my own thread with this method and my Root_Files.zip download so that those looking for root can easily gain it.
Click to expand...
Click to collapse

I was hoping you would so I wouldn't have to haha :D

I think I'm the first person to confirm root on here ^__^ I must say, rooting the phone within 12 hours of buying it is a new record for me haha.

I would thank you, but I'm out of thanks for the day. I'll add it to you in the morning haha.
 
Harry GT-S5830

Harry GT-S5830

Senior Member
Apr 9, 2012
886
232
The recovery I posted is an early blind build. Maybe the other one posted on the forum

Sent from my HTC Explorer A310e using xda app-developers app
 
Napstar

Napstar

Inactive Recognized Developer
Aug 20, 2011
398
1,097
Pune
You forgot to add the sticky bit in your instructions...

Here is what you wrote,
Code: 
adb shell chmod 0655 /system/bin/su
adb shell chmod 0655 /system/app/Superuser.apk

which should be modified as
Code: 
adb shell chmod 06[COLOR="red"][B]7[/B][/COLOR]55 /system/bin/su
adb shell chmod 06[COLOR="Red"][B]7[/B][/COLOR]55 /system/app/Superuser.apk

Here I have added 7 as permission for rwx to user of binary which you mistaken as 6...
Also, 6 should be the sticky bit which helps our device to execute the su binary with root as executing person and not the device user as executing one.

Have a look at here for more details,
http://www.techcuriosity.com/resources/linux/advanced_file_permissions_in_linux.php

in SUID - [ Set User ID ] section


USSENTERNCC1701E said:
Okay, so couple things first, ChainsDD is fantastic, he maintains SuperUser for us! Now, as far as I know, these binaries have NOT been tested on a Nexus 4 yet, so it is possible though unlikely that they may not work. If so, no biggie, you just won't have root.

  1. Extract su and Superuser.apk and copy them to your adb platform-tools folder.
  2. Boot the unsecured boot image from the OP.
  3. Make sure debugging mode is active on the device.
  4. Open a command prompt in the adb platform-tools folder.
  5. Mount /system as rw.
    Code: 
    adb shell mount -o,rw /system
  6. Push su and Superuser.apk to /system.
    Code: 
    adb push su /system/bin/
adb push Superuser.apk /system/app/
  7. Change permissions on su and Superuser.apk.
    Code: 
    adb shell chmod 0655 /system/bin/su
adb shell chmod 0655 /system/app/Superuser.apk
  8. Reboot.
Click to expand...
Click to collapse
 
USSENTERNCC1701E

USSENTERNCC1701E

Senior Member
Sep 21, 2010
1,262
290
Logan
Napstar said:
You forgot to add the sticky bit in your instructions...

Here is what you wrote,
Code: 
adb shell chmod 0655 /system/bin/su
adb shell chmod 0655 /system/app/Superuser.apk

which should be modified as
Code: 
adb shell chmod 06[COLOR="red"][B]7[/B][/COLOR]55 /system/bin/su
adb shell chmod 06[COLOR="Red"][B]7[/B][/COLOR]55 /system/app/Superuser.apk

Here I have added 7 as permission for rwx to user of binary which you mistaken as 6...
Also, 6 should be the sticky bit which helps our device to execute the su binary with root as executing person and not the device user as executing one.

Have a look at here for more details,
http://www.techcuriosity.com/resources/linux/advanced_file_permissions_in_linux.php

in SUID - [ Set User ID ] section
Click to expand...
Click to collapse

Ah, facepalm. Thanks. Haven't done manual root in like a year :( knew something didn't feel right about that, couldn't remember if it was 0655 or 0755, almost had it lol. Edited my previous post. Credited you.
 
Last edited:
  • Like
Reactions: Harry GT-S5830
Harry GT-S5830

Harry GT-S5830

Senior Member
Apr 9, 2012
886
232
Napstar said:
You forgot to add the sticky bit in your instructions...

Here is what you wrote,
Code: 
adb shell chmod 0655 /system/bin/su
adb shell chmod 0655 /system/app/Superuser.apk

which should be modified as
Code: 
adb shell chmod 06[COLOR="red"][B]7[/B][/COLOR]55 /system/bin/su
adb shell chmod 06[COLOR="Red"][B]7[/B][/COLOR]55 /system/app/Superuser.apk

Here I have added 7 as permission for rwx to user of binary which you mistaken as 6...
Also, 6 should be the sticky bit which helps our device to execute the su binary with root as executing person and not the device user as executing one.

Have a look at here for more details,
http://www.techcuriosity.com/resources/linux/advanced_file_permissions_in_linux.php

in SUID - [ Set User ID ] section
Click to expand...
Click to collapse

Is this on the website? I didn't write them

Sent from my HTC Explorer A310e using xda app-developers app
 
Status
Not open for further replies.

Similar threads

atl4ntis
  • Locked
[ROM][MAKO][KitKat/Lollipop/Marshmallow]Cataclysm for Nexus 4[Dec 21, 2015]
Replies
5K
Views
924K
Neo
Neo
He][razor
*[ROM][Official BeanStalk] CLOSED. Please Remove
Replies
624
Views
123K
chineel
chineel
Euroskank
[CM12] [Lollerpop] Mako Nightly Kangs
Replies
2K
Views
438K
J
jr67
D
  • Locked
[KitKat-KVT49L][AOSPA4.3-BETA][SaberMod4.8] ParanoidSaberDroid [AOSPAL-remix] [14/05 - V4.1][Lockscreen Notifications][PIE - PEEK]
Replies
2K
Views
303K
TheDarkDefender
TheDarkDefender
He][razor
[ROM] [AOSB Project] CLOSED. Please remove
Replies
241
Views
69K
biron_w
biron_w

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 12
    Harry GT-S5830
    Harry GT-S5830
    Hi all. Quick notice:

    Usual disclaimers apply.

    This is an Unsecure boot.img I made for Android 4.2 on the Nexus 4.

    Okay cool... but what is an insecure boot.img?

    An insecure boot.img allows the device to be booted with permissions to be mounted as root. This is a way of being able to push SuperSU/Superuser.apk to /system/app and the Su Binaries to /bin

    adb shell
    su
    mount -o remount,rw /system
    exit​

    See more here: External Link
    _____________________________________________________________________________________________________________

    To use this you must be unlocked, not familar with unlocking a Nexus device? Easy. In fastboot mode type "fastboot oem unlock" this wipes all data on the device (virtual sd included).

    A nice article regarding this thread was published here: http://www.addictivetips.com/android/root-google-nexus-4-install-clockworkmod-recovery/

    To boot this boot.img:
    must be in the platform-tools folder in the android-sdk
    must be in fastboot mode (power+vol-)

    First use: fastboot boot "boot.img" (no ")
    Why boot? I have not tested this image as I don't have a Nexus 4 as of yet.**

    **Some users report flashing the image makes the phone in need of a fastboot stock flashing session, stick to booting for now.​


    Thank you for helping!
    -fkrone
    -Ranguvar
    -USSENTERNCC1701E

    This is mainly for development purposes to obtain root on this device, it will be an easier process when a recovery is published and you can flash a su.zip. (see attached)

    DOWNLOAD HERE: http://www.androidfilehost.com/?fid=9390169635556426389
    Note, this is in Nexus 7 folder as Nexus 4 does not have its own atm.​
    Click to expand...
    Click to collapse

    Please Lock!
    View
    3
    fkrone
    fkrone
    Got it!
    Thanks for the tutorials. It was just fun to to something short after midnight (Germany). I was a little bit bored ;) Would be nice if you can mention me in the people helped to create this recovery ;)
    http://www.mediafire.com/?mlv72phch1tgd5y Mediafire-Mirror ;)
    View
    2
    S
    Stryder5
    HQRaja said:
    A colleague wrote a post at our blog a few hours back based on the guide here. I just got done with heavily editing it based on the response here and publishing it. I also added a manual method involving booting with the insecure boot image and copying the required files to the appropriate paths directly. I don't have a Nexus 4 at the moment but in my personal experience with Nexus devices including Galaxy Nexus on Jelly Bean 4.2, this method *should* work as long as you can boot using the insecure boot image, even if the recovery method fails to work. The full step-by-step instructions should be easy to follow for anyone. Hope it helps. Here is the link:
    http://www.addictivetips.com/android/root-google-nexus-4-install-clockworkmod-recovery/

    PS: If it works for you, please do confirm here, thanks.
    Click to expand...
    Click to collapse

    IT WORKED! Well, the manual method worked that involves ADB.

    Used these files:
    http://www.mediafire.com/?az44dwrww0808j3

    With these commands:
    Code: 
    adb shell mount -o remount,rw /system
adb push su /system/bin/
adb push Superuser.apk /system/app/
adb push busybox /system/xbin/
adb shell
su
chmod 06755 /system/bin/su
chmod 0644 /system/app/Superuser.apk
chmod 04755 /system/xbin/busybox
cd /system/xbin
busybox --install /system/xbin/
exit
exit

    I can now confirm I have root!
    View
    2
    USSENTERNCC1701E
    USSENTERNCC1701E
    There ya be, gimme a min to write up root instructions.
    View
    2
    R
    Ranguvar
    Dammit, beat me to it!
    Serves me right for making dinner first ;)

    http://ompldr.org/vZ2ExYQ/recovery.fstab
    View

New posts