Originally Posted by txxa
1. Boot into recovery.
2. Enable adb ( in twrp you need to start adb sideload, than cancel it ). Nexus recovery starts adb automaticaly
3. adb shell mount /dev/block/mmcblk0p24 /system
4. adb push ./su /system/xbin
5. adb shell ls -la /system/xbin ( i have not only su binary there, but tcpdump, and nc. for me it's some kind of check point. i mounted correctdevice )
6. adb shell chmod 06755 /system/xbin/su
7. adb shell ln -s /system/xbin/su /system/bin/su
8. adb shell sync
9 adb shell umount /system
10. adb reboot
After reboot install supersu from market. It will say about obsolete ( old binary ), but will work.
In windows steps 5 nad 8 can be skiped and in step 4 use: adb push su /system/xbin
Thanks to txxa for his work :good:
I thought i just need to flash supersu.zip ...
Sent from my HTC Desire X using xda premium
Works perfect. Screenshot attached.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello,
is this root method need unlocked bootloader ?
ralfred said:
Hello,
is this root method need unlocked bootloader ?
Click to expand...
Click to collapse
Ofcourse. Every root method does. Coz to have a custom recovery, u need to unlock.
Regards
neXus PRIME said:
Ofcourse. Every root method does. Coz to have a custom recovery, u need to unlock.
Regards
Click to expand...
Click to collapse
Thanks for your reply
I'll wait the update for me
You can add this one to OP
1) Download attached binaries from rootbin.zip to your adb folder
2) Reload to recovery (tested with Nexus Recovery)
3) Run in cmd
Code:
adb shell mount /dev/block/mmcblk0p24 /system
adb push su /system/xbin
adb push busybox /system/xbin
adb shell chmod 06755 /system/xbin/su
adb shell chmod 06755 /system/xbin/busybox
adb shell ln -s /system/xbin/su /system/bin/su
adb shell sync
adb shell umount /system
adb reboot
4a) Download and install supersu from market. It will say about obsolete ( old binary ), but will work.
4b) Instal via recovery attached UPDATE-SuperSU-v1.25.zip
You can choose between 4a or 4b.
Also attached archives with exe files.
Those who didn't root their phone download rootboxJB.zip (it roots phone and installing busybox)
Those who have rooted their phone download bboxJB.zip (it only installs busybox)
boot.img with init.d support can be found here.
Thanks to Softor from 4pda forums for all files and guides.
Another simple way......
....to own your phone even with new OTA JB!!
Gave it a trie and it worked like a charm - well, at least for me!
Just Flash the attached files trough recovery (used NexusRecovery 1.1 Beta - thx btw ) in following order:
1. Su_Bbox_1.20.2_gazhead_signed
2. Superuser-3.1.3-arm-signed
Would like to hear if it also worked for you!
cant root my device, htc desire x, first i rooted it, update came out, i got back to stock recovery, installed update, got latest twrp recovery and now rooting doesnt work even with this method. anyone have any ideas?
strawdr said:
cant root my device, htc desire x, first i rooted it, update came out, i got back to stock recovery, installed update, got latest twrp recovery and now rooting doesnt work even with this method. anyone have any ideas?
Click to expand...
Click to collapse
Checked preferences in Superuser?
Or which error do you have?
Will this method work for the 2.22 version of JB update?
Droid.Anoop said:
Will this method work for the 2.22 version of JB update?
Click to expand...
Click to collapse
I installed "superuser" on 2.22.707.6 (asia wwe) and i got strange bug. SU is working (tested with terminal emulator), but sometime when some app do "su" my phone goes to reboot. I was tryed to use myONEdx rom, but same trouble. Whats wrong with my device? =((
Related
Hey guys, I'm just wondering where to get that java box for the hero phone ( like in the modaco Rom)
Thanks in advance!
i would also like this, I extracted the apk but i need more then that because it wont run on my friends stock hero.
im an mgmaps user so java is required!
huh, any replies to this? i'm not rooted, stock upgraded rom, can i get java and where can i find a suitable app?
http://lmgtfy.com/?q=jbed+android+apk
first link ... took me 5 secs
alright dudes, here is the tutorial for that.. thought everyone had found it for himself, but okay ;-)
http://home.leakdroid.com/2009/08/31/java-app-for-android/comment-page-1/
keyra74 said:
http://lmgtfy.com/?q=jbed+android+apk
first link ... took me 5 secs
Click to expand...
Click to collapse
yeah, aren't you cute, found that myself, thank you oh-so-very-much....now, this:
adb remount
adb install Jbed.apk or adb push Jbed.apk /system/app
adb push libjbedvm.so /system/lib
adb shell reboot
is French to me....je ne parle pas francais!!!!
so, illiterate as i am, i turned to a forum of experts for a bloody answer....so, once again, thank you oh-so-very-much for providing it
i hope i've embedded enough sarcasm to make you realize you haven't helped a bit!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
1. Download this
2. Start a shell (i prefer adb shell), and type the following (each line confirmed with the return key)
Code:
adb remount
adb install Jbed.apk or adb push Jbed.apk /system/app
adb push libjbedvm.so /system/lib
adb shell reboot
Ready to take off with Java!
suisen said:
yeah, aren't you cute, found that myself, thank you oh-so-very-much....now, this:
adb remount
adb install Jbed.apk or adb push Jbed.apk /system/app
adb push libjbedvm.so /system/lib
adb shell reboot
is French to me....je ne parle pas francais!!!!
so, illiterate as i am, i turned to a forum of experts for a bloody answer....so, once again, thank you oh-so-very-much for providing it
i hope i've embedded enough sarcasm to make you realize you haven't helped a bit!
Click to expand...
Click to collapse
They helped you out to much if you ask me...
Don't forget that this is a development sub-forum! If you don't understand the things mentioned here you should post your question in the general forum where they could help you out step by step.
does not work with the new rom release(rooting was no problem with flashrec and does work)
ginchiller said:
does not work with the new rom release(rooting was no problem with flashrec and does work)
Click to expand...
Click to collapse
in modaco it is already included, with normal rom it works (tested and using it)
that is just a proof that it is working in the new release, but how could it be installed without flashing to modaco?
maybe by reading this thread?
http://forum.xda-developers.com/showpost.php?p=4545215&postcount=7
yeah,...thanks... but as i said this method is not working with the new rom...
i figured out how to install it on the new rom!!!
as i said i have allready rooted it with this tutorial
Flashrec
so i had the cm-hero-recovery.img on my phone again
i restarted the phone holding POWER+HOME (not power+back)
then i typed in the following commands into the cmd (be sure that you have the Jbed.apk & libjbedvm.so in your android sdk tools folder)
Code:
adb shell mount /system
adb push Jbed.apk /system/app
adb push libjbedvm.so /system/lib
adb shell reboot
and after the reboot there it should be, i hope i could help someone with the same problem
Worked perfectly ginchiller ty
Is there a way to fullscreen mode?
I have installed the new opera mini but it has bugs with landscape.
Without landscape its ok but I want it in fullscreen...
for those j2me apps i tried yet, fullscreen works perfectly
How to install applications? When i run jbed i see sdcard folder. What i have to do?
close jbed, open a file browser, goto the folder where you stored the java-program (*.jar) and open/execute it with jbed (just open it, normally after a successful installation of jbed, jbed will pop up)
ohh, i will try another file manager because when i tap on .jar file in SUBFS its try to extract files not execute)))
This enables you to reboot the phone from the power menu
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Reboot Options
Reboot - Reboot phone normally
Fastboot - Reboot into FASTBOOT mode (requires conected to pc with installed fastboot drives)
Download Links (please do not mirror)
[Latest - 4.0.2.A.0.42]
RebootOptions_4.0.2.A.0.42
[Old - 4.0.1.A.0.283]
RebootOptions_4.0.1.A.0.283
Istallation:
Copy .zip to sdcard
Flash .zip in recovery
Note: By replacing framework-res.apk you will remove any previously installed themes. And if you install another mod (framework-res.apk) you will need to copy back your stock android.policy.jar and framework.jar.
what did happen when u do reboot .. do you mean close all application or restarting the phone ??
Could you update these files to the 145 firmware
thanks
Great Thanks Adam.. Will try it tomorrow
I tried for 181 and got into a boot loop..
007Arc said:
I tried for 181 and got into a boot loop..
Click to expand...
Click to collapse
Then you probably set the wrong permisions, I have tested both versions and it works for me
Eighty89Teen said:
Could you update these files to the 145 firmware
thanks
Click to expand...
Click to collapse
Upload your framework.res.apk, framework.jar and android.policy.jar.
And i will fix it
AdamTt said:
Then you probably set the wrong permisions, I have tested both versions and it works for me
Click to expand...
Click to collapse
Whats the correct permission?
I used xxo
xoo
xoo
Sent from my LT15i using Tapatalk
Yes..but you need to put it into system folder first.. Change perms then move to correct folder..also ensure you're using correct version for your rom.
Sent from The Arc!
im_iceman said:
Yes..but you need to put it into system folder first.. Change perms then move to correct folder..also ensure you're using correct version for your rom.
Sent from The Arc!
Click to expand...
Click to collapse
I did exactly what u say. I had also the correct verion. But I only tried the the root explorer method.
Sent from my LT15i using Tapatalk
Another way to do it is using the terminal ( i don't like to press power button)
Start terminal then type su then type reboot
You should update your list of commands. framework-res.apk should be last because once it changes, your phone automatically reboots and you can't run the other commands.
However, I still can't get it to work on my Rogers-branded, rooted arc.
2.3.2, 3.0.A.2.181
Using the following commands:
Code:
adb push android.policy.jar /sdcard/android.policy.jar
adb push framework.jar /sdcard/framework.jar
adb push framework-res.apk /sdcard/framework-res.apk
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock0 /system
dd if="/sdcard/framework.jar" of="/system/framework/framework.jar"
dd if="/sdcard/android.policy.jar" of="/system/framework/android.policy.jar"
dd if="/sdcard/framework-res.apk" of="/system/framework-res.apk"
chmod 644 "/system/framework-res.apk"
mv "/system/framework-res.apk" "/system/framework/framework-res.apk"
Just boot loops.
BluechipJ said:
You should update your list of commands. framework-res.apk should be last because once it changes, your phone automatically reboots and you can't run the other commands.
However, I still can't get it to work on my Rogers-branded, rooted arc.
2.3.2, 3.0.A.2.181
Using the following commands:
Code:
adb shell
su
adb push android.policy.jar /sdcard/android.policy.jar
adb push framework.jar /sdcard/framework.jar
adb push framework-res.apk /sdcard/framework-res.apk
mount -o remount,rw -t yaffs2 /dev/block/mtdblock0 /system
dd if="/sdcard/framework.jar" of="/system/framework/framework.jar"
dd if="/sdcard/android.policy.jar" of="/system/framework/android.policy.jar"
dd if="/sdcard/framework-res.apk" of="/system/framework-res.apk"
chmod 644 "/system/framework-res.apk"
mv "/system/framework-res.apk" "/system/framework/framework-res.apk"
Just boot loops.
Click to expand...
Click to collapse
oh sorry, missed that.. Fixed now.
Thats strange, it worked last time i checked.. But i will flash back to .181 tomorrow, and test it again
First post updated with .145 version
does this show battery percentage, because I want to keep that feature from another mod
confirmed .145 version working on me, thanks adam, really appreciate it
kagemand123 said:
does this show battery percentage, because I want to keep that feature from another mod
Click to expand...
Click to collapse
Unfortunately not.
AdamTt said:
oh sorry, missed that.. Fixed now.
Thats strange, it worked last time i checked.. But i will flash back to .181 tomorrow, and test it again
Click to expand...
Click to collapse
Confirmed that .184 works on my Rogers-branded arc:
2.3.3, 3.0.A.2.181
(.181 framework-res.apk kept boot-looping.)
BluechipJ said:
Confirmed that .184 works on my Rogers-branded arc:
2.3.3, 3.0.A.2.181
(.181 framework-res.apk kept boot-looping.)
Click to expand...
Click to collapse
Good
Then i probably messed something up with the .181 (will take a look at it later)
As far as i know, the files from 181 and 184 are the same.
If you like, I can add battery percentage
Hey dude! Thanks alot!! It worked great. Found a possible bug though.. Could just be my unit but when using the widget for toggling backlight on and off the screen locks. Could be something or not. Just my 2 cents Keep up the great work man!!!
(I'm on .181)
Wildfire Bootanimations collection
CLICK ON THE NAME TO DOWNLOAD
Earth
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Cyanogen Mod 7
Pc
Google
Fuego
Aurora streak
N1 style
N1 CyanogenMod
Honeycomb Boot
Latido
AndroidGlow1
AndroidGlow2
AndroidParticles2
AndroidMinimal1 Green
Dancing Android
Htc Quietly Brilliant
Jockerdroid
Eye red
c64
Gingeryoshi
AndroidParticles1 Green
Cyanogenmod rotate
Matrix
r2d2
See you guys!!!
Thank you for this
I've been looking for some new ones.
So, I'm not sure here, do I flash or replace original?
nejc121 said:
Thank you for this
I've been looking for some new ones.
So, I'm not sure here, do I flash or replace original?
Click to expand...
Click to collapse
First option :
Rename the downloaded file into update.zip and put into sdcard
Recovery --> apply SDcard: update.zip
Or without renaming the file --> "install zip from SDcard"/"choose zip from SDcard"
Second option:
Some roms have bootanimation at system/media...( Cyanogen,ruymanca,passion.....),so you have to install as i'm explaining:
Extract *.zip file you downloaded
At customice/resource you'll found bootanimation.zip
*Copy bootanimation.zip (without unzipping) with root explorer in data/local of our wildfire
*Reboot and that's all
Hmmm, I tried chosing it, but it said it was aborted....
Ah, I got it, I needed to use Recovery 2.5 that I got from the ROM manager
Hmm...I flashed it as update.zip, but I still have my old custom bootani
Lemme try via ADB
nejc121 said:
Hmmm, I tried chosing it, but it said it was aborted....
Ah, I got it, I needed to use Recovery 2.5 that I got from the ROM manager
Hmm...I flashed it as update.zip, but I still have my old custom bootani
Lemme try via ADB
Click to expand...
Click to collapse
have you tried first and second option?
I haven't tried the manual zip select, because I'm lazy
I'll do that after ;D
First adb!
Okay it worked
First I just had to get R/W acces, then I just pushed the file
nejc121 said:
I haven't tried the manual zip select, because I'm lazy
I'll do that after ;D
First adb!
Okay it worked
First I just had to get R/W acces, then I just pushed the file
Click to expand...
Click to collapse
Glad to help you
Thanks again for your guide over there
I had to do a recovery because density changers ****ed up games
I'm using CM7 and I have tried both method. Don't work
i tried putting it in /system/media (cm7) and ended up with a blank screen. seemed to boot up alot quicker though...
Try pushing it to data/local
yep all done
i have wildfire S-OFF and root, using CM7 stable,i installed super manager, gave it superuser permissions,set busybox path to system/xbin,gave R/W acces to system, and tried to copy bootanimation.zip to both data/local and system/media... but when i paste super manager always says not enough free space... but i doubt thats the issue cause the animation is just a few kbs...after it says not enough free space it the sign goes away and the bootanimation.zip appears in the directory as it was copied there but when i reboot i dont have the animation just blank screen.. i tried everything and i dont really have a clue whats wrong
can anyone help me please?
mtnhan1996 said:
I'm using CM7 and I have tried both method. Don't work
Click to expand...
Click to collapse
i use super manager
just dload it from the market (free) , go into file explorer, give it root permission by tapping the menu and setup
copy and paste to your hearts content
edit
I did have your problem after i de-branded my phone , s-off with alfarev fixed it .
conclusion after thinking on this part of the day
Update your Hboot maybe?
I use Clockwork 3.0 and when i try to update it it says
"Amend scripting (update-script) is no longer supported." Help me
Get ROM Manager
Click Flash Recovery
Click Rebbot into Recovery
Flash there.
So it only works on Clockwork 2.5
Now i finally not failed installing, but it didn't worked, it shows the CyanogenMod bootanimation
Do you have ADB?
If not, install Android SDK
Extract Bootanimation.zip from the flashable zip and place it in the same folder ADB is (By default: C:\Program Files\Android\android-sdk\platform-tools)
Then go to the Command prompt (Startmenu-CMD)
And type in cd C:\Program Files\Android\android-sdk\platform-tools
Then: adb shell
Then copy and paste this: # mount -o rw,remount -t yaffs2 /dev/block/mtdblock3
Also copy paste this: # chmod 777 /system
Type Exit
Type: adb push bootanimation.zip data/local
And you're done.
nejc121 said:
Do you have ADB?
If not, install Android SDK
Extract Bootanimation.zip from the flashable zip and place it in the same folder ADB is (By default: C:\Program Files\Android\android-sdk\platform-tools)
Then go to the Command prompt (Startmenu-CMD)
And type in cd C:\Program Files\Android\android-sdk\platform-tools
Then: adb shell
Then copy and paste this: # mount -o rw,remount -t yaffs2 /dev/block/mtdblock3
Also copy paste this: # chmod 777 /system
Type Exit
Type: adb push bootanimation.zip data/local
And you're done.
Click to expand...
Click to collapse
so i have to extract the bootanimation.zip and copy it from
\bootanimation\system\customize\resource to the same folder as the adb.exe
Worked for me, thanks
i like this boots file and download one i nedd but i can't install it in my wildfire cyanogen mod 7
thanks
Future of this rom and me - https://plus.google.com/u/0/100983447046094793882/posts/7YtTFWWgT1C
it works beautiful!!! your the man!!! its more snappy too!! this is turning out quite well... Samsung galaxy s 2, kiss my amazes shiny metal ass!!!
Is this from what we worked on last night?
da9b16 said:
Is this from what we worked on last night?
Click to expand...
Click to collapse
no this was a diffrent project i worked on man
deleted...
no just double click bat. and it opens up cmd
try putting in on the c:\
see if it works that way
hmmm tried that and it completed successfully but no dice....gonna try again..
mkearney83 said:
hmmm tried that and it completed successfully but no dice....gonna try again..
Click to expand...
Click to collapse
what you mean man
I ran the tool and it gave me root until I had to reboot.
After the reboot, no root.
I do not have the bootloader unlocked.
Also I found an error in your script.
:cd %:h
adb wait-for-device
adb push zergRush /data/local/
adb shell chmod 777 /data/local/zergRush
adb shell /data/local/zergRush
adb wait-for-device
adb shell sleep 1
adb remount
adb shell mount -o rw,remount rootfs /
adb shell mount -o remount,suid /dev/block/mmcblk0p29 /system
adb shell chmod 4755 /system/bin/sh
adb push ./su /system/bin
adb push ./su /system/bin
adb push ./busybox /system/bin
adb shell chmod 4755 /system/bin
adb shell chmod 4755 /system/bin/su
adb shell chmod 4755 /system/bin/su
adb push ./Superuser.apk /system/app
adb install ./androidterm.apk
adb wait-for-device
adb shell sync
pause
Click to expand...
Click to collapse
I'm assuming that one of them is supposed to be busybox?
Binary100100 said:
I ran the tool and it gave me root until I had to reboot.
After the reboot, no root.
I do not have the bootloader unlocked.
Click to expand...
Click to collapse
ya if you want root to stay you will have to unlock boot loader
no thats for superuser to work
jpeiv did it work for you?
Is this safe to use on 1.36.531.6?
xboarder56 said:
ya if you want root to stay you will have to unlock boot loader
no thats for superuser to work
Click to expand...
Click to collapse
You have to chmod su twice for it to work???
Binary100100 said:
You have to chmod su twice for it to work???
Click to expand...
Click to collapse
i guess it's working that way
and yes its safe to use on 1.36.351.6 confirmed
and to unlock bootloader we use the HTCdev method?
morganpants said:
and to unlock bootloader we use the HTCdev method?
Click to expand...
Click to collapse
to unlocked bootloader use htc dev meothed
brokenwatch said:
Is this safe to use on 1.36.531.6?
Click to expand...
Click to collapse
ive been running it for 4 hours, ive rebooted manually multiple times, and its perfect so far with no bugs... even stuck after a factory reset, with no fc's..... its perfect
morganpants said:
and to unlock bootloader we use the HTCdev method?
Click to expand...
Click to collapse
yes, use the htc method
do you recommend or do u think i should wait until s-off is achieved incase we cant flash after the htcdev unlock?
morganpants said:
do you recommend or do u think i should wait until s-off is achieved incase we cant flash after the htcdev unlock?
Click to expand...
Click to collapse
you can flash recoverys with htc dev method and system.imgs.
but with true s-off you can flash boot.img and radio's
you can do both methods if you want to make sure everything is fully unlocked
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my HTC Ruby using xda premium
how to enable adb shell in recovery mode?
when i try "adb shell" in recovery mode,it says sh not find somthing
does this means can't use adb in recovery mode?
i want trace recovery bin by ida pro,sames i have 2 chose:
1,enable adb shell and gdb server in recovery mode
2,or run recovery bin in normal mode.
the 1st,cant open adb shell
the 2nd got segment error in sh
please help!
<robin> said:
how to enable adb shell in recovery mode?
when i try "adb shell" in recovery mode,it says sh not find somthing
does this means can't use adb in recovery mode?
i want trace recovery bin by ida pro,sames i have 2 chose:
1,enable adb shell and gdb server in recovery mode
2,or run recovery bin in normal mode.
the 1st,cant open adb shell
the 2nd got segment error in sh
please help!
Click to expand...
Click to collapse
Release 5a recovery?? I get error: closed
Drivers are good aye?
Stifilz
no,i'm at 3.2.1
how to open adb shell?
<robin> said:
no,i'm at 3.2.1
how to open adb shell?
Click to expand...
Click to collapse
Wtf. Normally just adb shell. Does adb pull or adb push work etc?
<robin> said:
how to enable adb shell in recovery mode?
when i try "adb shell" in recovery mode,it says sh not find somthing
does this means can't use adb in recovery mode?
i want trace recovery bin by ida pro,sames i have 2 chose:
1,enable adb shell and gdb server in recovery mode
2,or run recovery bin in normal mode.
the 1st,cant open adb shell
the 2nd got segment error in sh
please help!
Click to expand...
Click to collapse
hi robin,
1. change region to US,
2. download this hacked_recov,
3. run recovery, update with this file, should finish with error 7,
4. wait one minute, and adb should be available - make sure that you have installed adb drivers for recovery device.
5. when in adb shell type this:
Code:
/system/bin/tempsu
PATH=$PATH:/system/bin:/system/xbin
and you will get root, and normally working with all the commands shell.
br
condi
wow,thanks candi!
your tool is real cooooool
i can trace recovery now!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
getting prohibit update as a result of checking version or base
condi said:
hi robin,
1. change region to US,
2. download this hacked_recov,
3. run recovery, update with this file, should finish with error 7,
4. wait one minute, and adb should be available - make sure that you have installed adb drivers for recovery device.
5. when in adb shell type this:
Code:
/system/bin/tempsu
PATH=$PATH:/system/bin:/system/xbin
and you will get root, and normally working with all the commands shell.
br
condi
Click to expand...
Click to collapse
So I've been at this for days now. From what I can read here and on the web it looks like my region file is screwed up. Tried a million different region zips.
I can get device to show in adb as recovery.
Any thoughts?