Related
New possible root method on Thinkpad tablet forums, by OPDECIRKEL. He needs help testing it out.
look here and lets cross our fingers =D
http://www.thinkpadtabletforums.com...nt/yareftpt-yet-another-root-exploit-for-tpt/
opdecirkel released the exploit -> http://opdecirkel.wordpress.com/2012/03/18/yareftpt/
unfortunately, it doesn't work. =( can't execute "adb remount" when the script calls for it, but hopefully things will get ironed out soon.
***EDIT***
updated script worked!
-=HOLLYW00D=- said:
unfortunately, it doesn't work. =( can't execute "adb remount" when the script calls for it, but hopefully things will get ironed out soon.
Click to expand...
Click to collapse
Not sure if it can help you, but try checking the TPT forum thread again, there has been some advances and troubleshooting going on
Moved To General
As the first post is just a link and contains no development, this has no place in this section
updated -> http://opdecirkel.wordpress.com/2012/03/18/yareftpt/
Someone thinkpadtabletforum reported that it worked for him.
updated script worked for me! cwm installed fine as well!
I achieved root with the new method on OTA 2.5. Also installed CWM with no issues. Works great.
Sent from my PC36100 using Tapatalk
I can confirm it worked!
I had to update first because the "Disable Battery Discharge" option was not there. (I guess my Tablet stopped getting OTA updates since I was on ThinkPadTablet_A310_02_0024_0065_US... Also, you have to update one at a time, you can't go from 24_65 straight to 37_75. Also, I stopped at 39_86 since I was impatient.)
I like this once since we can see how it worked rather than blindly running some guys program (I never tried the first root.)
I can also confirm the new method to be working. Just rooted my 0089_WE TPT. Works like a charm
I am quoting the following post (i don't have privilege to post there): forum.xda-developers.com/showpost.php?p=23902281&postcount=64
daswahnsinn said:
I unrooted and then updated, now I can't root. I updated the SDK and made sure I have the proper drivers needed. So I take back my easy comment. I'll keep trying I might just manually push the files back.
Click to expand...
Click to collapse
How did it fail? At which stage and what error did you get?
Okay, I'll try and flash the oldest update zip, and it fails as it should, then I wipe the cache part, reboot, and I hit enter when I gets to the unlock screen then the CMD window closes.
EDIT: I spent a good hour or so combing through my PC and these forums and tried both methods a lot, and this one finally worked. It wouldn't let me get to the /cache/recovery/pwn/su part of the script. Thank you all for your support.
I have problems...
Hi all,
Apologizes for my english, too bad to discuss this kind of issues. Sorry in advance.
I had the "fantastic" idea to update the firmware some weeks ago, when I was SU. After this, I've lost most of capabilities!
I tried to follow the procedure, but I cannot reach 'root' in any case. I have version WE089. Downloaded US060, but there's only 065 for Western Europe. I got both, just in case..
Unfortunately, in the first step it failed I'm not able to update anything. The process crashes when is loading old firmware, either US060 or WE065.
I've realised that during the process I loose the USB link connection (when I reboot), and the system tries to install again and again the driver. If the TPT is running in recovery mode, it seems that is not connected via USB... If I have the tablet in "normal use", I see it through the Windows Desktop.
Other question: should I disconnect the Internet connection?
I guess other requirements are right (ADBD, debugging mode,...). It's really annoying, it took me a lot of hours and I haven't found any solution.
Can anybody help me? What I'm doing wrong?
Cheers!
jm
W7 64bits - TPT WE089
@jm
goto device manager. right click on Android device. reinstall device driver.
This worked for me in recovery when the device was not recognized.
Edit: look here: http://forum.xda-developers.com/showthread.php?t=1471106&page=2
What do you mean with loosing the connection? Is the adb driver installed correctly? Where did you get it from? Is it an genuine lenovo driver? If so, than you shouldn't worry!
Perhabs it's the MTP driver, that is missing when you boot into recovery? If it's the adb driver, than you should try jlove's method.
In addition I wanted to inform you, that the new method worked for me, too! Even with some complications... by this way, thanks again to opdecirkel!
Because the run.bat script did't worked correctly, I had to do it manually. So I put the "yareftpt" on C:\\, started cmd.exe, booted the TPT into recovery and changed the directory in cmd.exe with "cd.." to "cd yareftpt" ...followed the instructions with the update...
echo 4. Reboot in RECOVERY: (shutdown the tablet, then start it and press volume + few times until it starts in recovery)
echo 5. Go to apply update, select the update from the sdcard and try to apply it. It will fail, but that is OK.
echo 5. Then, go to 'WIPE CACHE PARTITION' and select it (navigate with volume buttons and select it with power button),
echo 6. When wipe cache complete, press (here) ^<ENTER^>.
and after that I copied the first line of the script into cmd and executed. I did it line after line, just to the next step. (dark green= copy line after line, paste and execute)
adb shell "/system/bin/mkdir /data/local/pwn"
adb shell "/system/bin/mkdir /data/local/pwn-bak"
adb shell "/system/bin/cat /system/etc/install-recovery.sh > /data/local/pwn-bak/install-recovery.sh.orig"
adb shell "/system/bin/mkdir /cache/recovery/pwn"
adb push su /cache/recovery/pwn
adb shell "/system/bin/rm /cache/recovery/log"
adb shell "/system/bin/ln -s /system/etc/install-recovery.sh /cache/recovery/log"
adb shell "echo \"/system/bin/chmod 777 /cache\" >> /tmp/recovery.log"
adb shell "echo \"/system/bin/mount -t ext4 /dev/block/mmcblk0p4 /cache\" >> /tmp/recovery.log"
adb shell "echo \"/system/bin/chmod 777 /cache\" >> /tmp/recovery.log"
adb shell "echo \"/system/bin/mount -oremount,rw -t ext4 /dev/block/mmcblk0p4 /cache\" >> /tmp/recovery.log"
adb shell "echo \"/system/bin/chmod 777 /cache\" >> /tmp/recovery.log"
adb shell "echo \"/system/bin/chmod 777 /cache/recovery\" >> /tmp/recovery.log"
adb shell "echo \"/system/bin/chown root /cache/recovery/pwn/su\" >> /tmp/recovery.log"
adb shell "echo \"/system/bin/chmod 4777 /cache/recovery/pwn/su\" >> /tmp/recovery.log"
echo 7. On the device, go to 'DISABLE BATTERY DISCHARGE' and select it. When complete press (here) ^<ENTER^>
pause
some of commands might cause failures, but don't worry and just go on
adb shell "/system/bin/rm /cache/recovery/log"
echo 8. On the device, select REBOOT. When startup COMPLETE press (here) ^<ENTER^>
pause
adb push Superuser.apk /data/local/pwn/Superuser.apk
adb push busybox /data/local/pwn/busybox
adb push su /data/local/pwn/su
adb push pwn-in.sh /data/local/pwn/pwn-in.sh
adb shell "/system/bin/chmod 777 /data/local/pwn/pwn-in.sh"
echo Your PC command prompt appears next. Do the following things:
echo 1. adb shell
echo when '$' (adb shell) appear, do:
echo 2. /cache/recovery/pwn/su
echo when '#' appears. You are root. run the following:
echo 3. /data/local/pwn/pwn-in.sh
now you should try if you have su, even if you don't see in your app list..
download root checker, install, open and try it!
You should have root right now.
In my case, i had root, but no CWM!
So I had to install in manually, but with root it should't be a problem. you only have to download the correct cwm version:
http://forum.xda-developers.com/showpost.php?p=21916505&postcount=71
then I installed it with the Android Terminal Emulator app, because the cmd.exe method did't worked for me. You should just follow the instructions:
or you can copy img file on /data/local/ folder of your tablet (with a file manager with root permissions)
launch "Android Terminal Emulator" application
and tape the instructions
su
mount -o rw,remount /system
echo "#!/system/bin/sh" > /system/etc/install-recovery.sh
dd if=/data/local/NameOfCWMFile.img of=/dev/block/mmcblk0p1
http://www.thinkpadtabletforums.com...nd-development/clockworkmod-recovery-for-tpt/
After a shutdown and reboot into recovery I had cwm! So I am able to do nandroid backups...
In this way, I would particularly like to thank to all devs that made the TPT root possible! Now i like my TPT 1000% more than before...e.g. no status-bar in lecture notes -> sooo great!!
I do get the following error maybe someone can help me out
[*]
[*]
[*]
/system/bin/mkdir: not found
/system/bin/mkdir: not found
cannot create /data/local/pwn-bak/install-recovery.sh.orig: directory nonexisten
t
/system/bin/mkdir: not found
699 KB/s (22364 bytes in 0.031s)
/system/bin/rm: not found
/system/bin/ln: not found
7. On the device, go to 'DISABLE BATTERY DISCHARGE' and select it. When complete
press (here) <ENTER>
Drücken Sie eine beliebige Taste . . .
it cant find the mkdir command very strange
I'm a little rusty, but are the / and \ facing the correct way? And are you in the correct directory? Not found usually means path is incorrect.
@rangercaptain
thats the commands from the root script. I didnt change them.
the commands are send over from adb shell and the tablet is in root directory i think.
When i go into shell and type in ls i get access denied error.
and you load the update zip and wiped cache before typing the commands, right? You have to do this every time you try to root...
Try to do it with another method. Don't do it directly trough adb shell...just type the shell commands in the cmd.exe
You just have to chance the directory in cmd, before executing the commands.
Then try not to input 'adb shell' before the shortened command, but the whole command as one line like:
adb shell "/system/bin/mkdir /data/local/pwn"
Perhabs it will work..?!?
@neos
yes i do the same procedure.
I also tried over cmd with adb shell "command" and also in shell.
Always the same error.
I looked into the system/bin directory and mkdir does have filesize of 0kb...
Apparently I am running OTA 2 or 2.5. I am not really sure which one. I did get some kind of system update from lenovo the other day.
I would like to install ADW Launcher EX, but I guess I need root for that as the market says it is incompatible with my device.
Funnily enough Go Launcher EX showed up as free in the Amazon App Store. I have that now ( not installed, but added to my account in case they make it not free). It will install if I want it to on my non-rooted setup.
So I guess my question how do I root this sucker?
Buil Info:
ThinkPad_Tablet_A310_02_0039_0089_02_US
Kernel: 2.6.36.3
Machine Type: 1838-22U.
Thanks in advance.
Sent from my ThinkPad Tablet using xda premium
This information is available in another thread.
http://forum.xda-developers.com/showthread.php?p=23754510
Possible new way to ROOT
Moved To General
Please do not post questions in the development section
Anyone have an idea why the stock accuweather widget will work with stock home but not adw launcher?
Sent from my ThinkPad Tablet using xda premium
Ok I am not rooted thanks to that script.
However it would *NOT* run on my Windows 7 64-bit machine. Kept crapping out during the adb shell commands :
Code:
adb shell "/system/bin/mkdir /data/local/pwn"
adb shell "/system/bin/mkdir /data/local/pwn-bak"
adb shell "/system/bin/cat /system/etc/install-recovery.sh > /data/local/pwn-bak/install-recovery.sh.orig"
adb shell "/system/bin/mkdir /cache/recovery/pwn"
adb push su /cache/recovery/pwn
adb shell "/system/bin/rm /cache/recovery/log"
adb shell "/system/bin/ln -s /system/etc/install-recovery.sh /cache/recovery/log"
adb shell "echo \"/system/bin/chmod 777 /cache\" >> /tmp/recovery.log"
adb shell "echo \"/system/bin/mount -t ext4 /dev/block/mmcblk0p4 /cache\" >> /tmp/recovery.log"
adb shell "echo \"/system/bin/chmod 777 /cache\" >> /tmp/recovery.log"
adb shell "echo \"/system/bin/mount -oremount,rw -t ext4 /dev/block/mmcblk0p4 /cache\" >> /tmp/recovery.log"
adb shell "echo \"/system/bin/chmod 777 /cache\" >> /tmp/recovery.log"
adb shell "echo \"/system/bin/chmod 777 /cache/recovery\" >> /tmp/recovery.log"
adb shell "echo \"/system/bin/chown root /cache/recovery/pwn/su\" >> /tmp/recovery.log"
adb shell "echo \"/system/bin/chmod 4777 /cache/recovery/pwn/su\" >> /tmp/recovery.log"
So I busted out and dusted off my old Thinkpad T43 with Win7 Pro 32-Bit, installed the ADB driver and BAM! Root.
So a few Q's.
I had to manually install busybox. No big deal, but weird.
I installed Clockwork Mod Recovery to the internal flash but it detects my tablet as a transformer prime. Is this ok?
Finally, I am still unable to uninstall the damned social touch app. I've managed to remove almost all the other bloat crap but this app defies me. Suggestions anyone?
Thanks to the great community!
Weirder and weirder.
Clockwork recovery crashes 50% of the time. I am not doing anything special except trying to make a ROM backup.
I would like to flash a clean, rooted, de-bloated image from here:
http://forum.xda-developers.com/showthread.php?t=1536693
Any help would be greatly appreciated.
Temetka said:
I installed Clockwork Mod Recovery to the internal flash but it detects my tablet as a transformer prime. Is this ok?
Click to expand...
Click to collapse
Have you installed the version from here?
http://forum.xda-developers.com/showpost.php?p=21916505&postcount=71
Finally, I am still unable to uninstall the damned social touch app. I've managed to remove almost all the other bloat crap but this app defies me. Suggestions anyone?
Click to expand...
Click to collapse
I removed it using Titanium Backup. Had no problems with it.
No, I didn't use that one. I used the one from the market. How do I install the .img file? I didnt see an option when I boot into Lenovo's recovery.
Sent from my ThinkPad Tablet using xda premium
Temetka said:
No, I didn't use that one. I used the one from the market. How do I install the .img file? I didnt see an option when I boot into Lenovo's recovery.
Sent from my ThinkPad Tablet using xda premium
Click to expand...
Click to collapse
Download the right recovery for your TPT 16GB, 32GB or 64GB
You can find the instructions to install it here:
http://forum.xda-developers.com/showthread.php?t=1458212
Code:
adb push ventana_recovery.img /data/local/
adb shell
su
mount -o rw,remount /system
echo "#!/system/bin/sh" > /system/etc/install-recovery.sh
dd if=/data/local/cwr_recovery_2.img of=/dev/block/mmcblk0p1
OK, Temetka,
First- the CWM 'app' you got from the market does nothing (that anyone here is doing). Uninstall and move on.
Second- CWM replaces your stock Lenovo Recovery 'BIOS', so when you boot to recovery mode, you'll see a top hat icon and lots of new options. You won't use Lenovo's anymore.
Third- Get your TPT's appropriate CWM image here(to be installed using ADB commands from your computer) downloaded to your PC
Fourth- follow these instructions (copied from here) to use ADB to install CWM Recovery into the recovery partition, replacing Lenovo's.
open command line and go to folder where the file is saved
Code:
> adb push NameOfCWMFile.img /data/local/
> adb shell
> su
> mount -o rw,remount /system
> echo "#!/system/bin/sh" > /system/etc/install-recovery.sh
> dd if=/data/local/NameOfCWMFile.img of=/dev/block/mmcblk0p1
Shut down your tablet. Boot into Recovery (vol+, vol+, etc.). Using CWM options, choose reboot (this should clear a possible reboot issue while inside CWM).
Done - now you can...
'Backup' - create a Nandroid on your external SD-Card-- DO THIS FIRST!
'Restore' - install any other TPT nandroids (no-bloat_0089_US for example)
'Install image from SD-Card' - install CM9 (Ice Cream Sandwich)
...and much more
Thank you both. I have rooted and hacked the crap out of my Nook Tablets and Captivate. That being said it has all been done using Odin, SD card booting with CWM on the SD card and so on. I haven't really fiddled around with adb.
Later on this evening I will go ahead and give those instructions a shot. I'll probably just pull the trigger and install CM9 as well just to try it out and maybe help out with posting any bug reports and so on.
Sent from my ThinkPad Tablet using xda premium
Also the CWM I installed from the market is actually Clockwork Rom Manager.
I also installed Rom Toolbox which has helped me out with removing some of the bloat applications.
I followed that up with Titanium Backup and made a full backup on my spare 16GB card. Once I have CWM installed, I will make a full Nandroid backup of this system as it stands now. I am pretty happy with its performance now that I have been able to debloat it and run sd speed increase.
Since I am asking some questions, got 1 more for ya guys. I have used the V6 supercharger script on my Nooks and they have really given a nice noticeable increase in system performance and UI resposniveness. Has anyone here used it on a TPT, and if so what was the experience like?
Sent from my ThinkPad Tablet using xda premium
Ota 2.5 and root
Temetka said:
Apparently I am running OTA 2 or 2.5. I am not really sure which one. I did get some kind of system update from lenovo the other day.
I would like to install ADW Launcher EX, but I guess I need root for that as the market says it is incompatible with my device.
Funnily enough Go Launcher EX showed up as free in the Amazon App Store. I have that now ( not installed, but added to my account in case they make it not free). It will install if I want it to on my non-rooted setup.
So I guess my question how do I root this sucker?
Buil Info:
ThinkPad_Tablet_A310_02_0039_0089_02_US
Kernel: 2.6.36.3
Machine Type: 1838-22U.
Thanks in advance.
Sent from my ThinkPad Tablet using xda premium
Click to expand...
Click to collapse
Solved ... follow this link.
So thecubed made a great tool to root, but the .bat file is intended for PC use. I'm on a Mac.
Could anyone extrapolate the adb commands used in that file? I'm familiar with adb and would have no issues with following the commands, I just can't seem to see exactly what the .bat file does.
tldr: what are the adb commands needed to root using his files? I can take it from there.
I'd love to know as well.
Sent from my VS980 4G using Tapatalk 4
mjdupuis said:
So thecubed made a great tool to root, but the .bat file is intended for PC use. I'm on a Mac.
Could anyone extrapolate the adb commands used in that file? I'm familiar with adb and would have no issues with following the commands, I just can't seem to see exactly what the .bat file does.
tldr: what are the adb commands needed to root using his files? I can take it from there.
Click to expand...
Click to collapse
Here, I put the whole .bat file text, you should be able to figure it out.
@echo off
echo.
echo **************************************
echo Easy root for LG G2
echo Supports ATT, TMO, VZW, and KT Variants
echo Repackaged by IOMonster
echo See http://tinyw.in/mXhw for details
echo **************************************
echo.
echo.
echo Credit to http://optimusforums.com/threads/how-to-root-the-lg-g2-f320.8846/
echo.
echo.
pause
echo Looking for device...
.\adb.exe wait-for-device
echo Determining carrier...
for /f %%i in ('.\adb.exe shell getprop ro.build.target_operator') do set RESULT=%%i
if %RESULT%==ATT GOTO ATTTMORoot
if %RESULT%==TMO GOTO ATTTMORoot
if %RESULT%==VZW GOTO VZWRoot
if %RESULT%==KT GOTO KTRoot
echo.
echo.
echo No matching phone found. Got %RESULT% from ADB.
pause
:ATTTMORoot
echo Found ATT or TMO phone!
echo Pushing g2_security...
echo.
.\adb.exe push g2_security /sdcard/g2_security
GOTO RootStep2
:VZWRoot
echo Found VZW phone!
echo Pushing VZW g2_security...
.\adb.exe push g2_security_vzw /sdcard/g2_security
GOTO RootStep2
:KTRoot
echo Found KT F320k phone!
echo Pushing ytiruces_1a ...
.\adb.exe push ytiruces_1a /sdcard/ytiruces_1a
GOTO RootStep2
:RootStep2
echo.
echo.
echo *******************************************************
echo Now, please unplug usb, go to developer options and
echo disable USB debugging and re-enable it.
echo Once you've done that, re-plug your usb...
echo *******************************************************
pause
echo Waiting for device...
.\adb.exe wait-for-device
echo Now it's time to install su and superuser.
echo.
echo Please note! This will trip LG's rootchecker!
echo.
echo This means your phone will show ROOTED in the settings menu,
echo and in the LG Download mode.
echo.
echo If you do not want to possibly invalidate your warranty
echo press CTRL-C to stop this script.
echo You will have a rooted ADB, but no apps on the phone will be able
echo to access root functions.
echo.
pause
echo.
echo.
echo Mounting system RW and pushing SU, then remounting system RO again
.\adb.exe shell "mount -o remount,rw /system"
.\adb.exe push su /system/xbin/su
.\adb.exe shell "chown 0.0 /system/xbin/su;chmod 06755 /system/xbin/su;sync;mount -o remount,ro /system"
echo Installing superuser
.\adb.exe install superuser.apk
echo.
echo.
echo ***************************************************
echo Done.
echo ***************************************************
echo.
echo Please check the above for any errors and let me know if you run into any issues.
echo Enjoy your phone!
pause
Click to expand...
Click to collapse
wargreymon89 said:
Here, I put the whole .bat file text, you should be able to figure it out.
Click to expand...
Click to collapse
If anyone can't, they don't need to root.
If you know your carrier, skip all the carrier detect crap and go straight to pushing the correct root.
Then wait and push Su and the rest.
It's a pretty simple root via adb manually.
I just want tethering to work before I run out and get one.
Thank you very much!
I'm having trouble getting debug mode on my mac. Any suggestions? SDK Tools are updated and USB Debugging is checked...
Did you select internet and then Ethernet when you connect your USB?
mjdupuis said:
Did you select internet and then Ethernet when you connect your USB?
Click to expand...
Click to collapse
Your a boss!
wargreymon89 said:
Here, I put the whole .bat file text, you should be able to figure it out.
Click to expand...
Click to collapse
By the way, this worked out just fine. I couldn't get it to work the first time around because the original method by thecubed didn't work with the ota. His update worked. Thank you, again.
A Mac root method (not automated)
I posted this in another Q&A thread, just wanted the answer to be available if someone may be following this. The two thread might need to be combined.
WARNING! This is just what worked for me, and it's just the adb commands from thecubed's program. All credit goes to him, I didn't do any of this, just took the info from it.
Here's the thread: http://forum.xda-developers.com/showthread.php?t=2448887
Download it, unzip it, and then take a moment to go back and thank him if you didn't do that.
You are not actually using his program, just the files and commands. Everything is done using Terminal and the Finder. You must have ADB working, look elsewhere for instructions on setting that up.
The files used here are the Verizon versions of the files, which I used for my phone. They are also specific to the OTA'd Verizon software, "11A" so there are different files if you haven't installed the OTA. These commands are correct, but the files being pushed aren't all the same between different carrier models and do not work with any other carrier. All the right stuff for other carriers is contained in thecubed's program.
The bold sections are files you need to send over adb, you can manually enter the file pathway or drag the files from finder into terminal after the adb commands (and before you type the destinations).
One more warning; if this is your first time using adb or terminal, I don't recommend this as your first try. It's super easy to screw something up in terminal.
Your phone must have developer options enabled and usb debugging on. Plug in your phone via usb and select "Internet" and then "Ethernet."
adb push ytiruces_1a_vzw /sdcard/ytiruces_1a
Unplug usb, disable USB debugging and then re-enable it. Plug USB back in.
adb shell "mount -o remount,rw /system"
adb push su /system/xbin/su
adb shell "chown 0.0 /system/xbin/su;chmod 06755 /system/xbin/su;sync;mount -o remount,ro /system"
adb install superuser.apk
exit
I see there are step by step videos for windows but none for Mac yet. I've rooted my last two phones but I followed videos which showed the exact process. I'm hoping someone eventually posts a Mac walk through video for the less confident users such as me.
I'm trying to follow the steps. When I run ./adb devices it lists my phone but says offline next to it. any ideas?
If you're on a Mac there's no "./" just "adb devices". You can't follow the commands in the .bat file without making those adjustments. Did you try following the commands in my post?
black05x5 said:
I'm trying to follow the steps. When I run ./adb devices it lists my phone but says offline next to it. any ideas?
Click to expand...
Click to collapse
You need to be sure USB debugging is on, that you selected Internet>Ethernet when connected to USB, and my phone asked me if I wanted to allow connections from my computer. If all these are set up correctly it should work.
I have usb debugging on. My phone did ask me to confirm connection which I did. Then when I type ./adb devices it lists my phone but still says offline next to it. Being a noob at this I'm really stumped.
mjdupis can you please clarify what you mean when you say I don't need to type ./ before the command? My understanding was I always had to do this on a Mac?
black05x5 said:
mjdupis can you please clarify what you mean when you say I don't need to type ./ before the command? My understanding was I always had to do this on a Mac?
Click to expand...
Click to collapse
The "/" is what you would use to point to a filepath. Like /Home/Library/Root or a file on the phone /System. If you look at the commands I listed there are no ./ before any adb commands, that's a windows thing.
Terminal tells me there's no such directory when I put ./ before adb commands, because it thinks I'm trying to direct it to an adb folder.
I reinstalled everything and now its finally recognizing my phone. Now I just have to figure out how to do this. Sorry to keep asking, but can someone confirm if this is right...
Now that it recognizes my phone
I type adb push then drag the file ytiruces_1a_vzw into terminal and then type /sdcard/ytiruces_1a and hit enter.
Then unplug the cord from phone, turn of debugging and back on then plug the cord back in. then select internet ethernet to activate debugging.
Then type adb shell and hit enter.
Then type mount -o remount,rw /system and hit enter.
Is this correct so far??
thanks for your help!!
---------- Post added at 10:54 PM ---------- Previous post was at 10:15 PM ----------
Actually, looks like I figured it out. Got phone rooted... Thanks again for the help!
Could use your help again! Got my phone rooted and installed TWRP. Everything was working great. Running stock rom. Only mod I had done was the black notification bar. I installed an app from the market called LCD Density. Tried changing my phone from 320 to 300. It then reboots the phone for it to take affect. My phone is now stuck in a bootloop on the LG logo screen with the LED flashing. I can get into TWRP but the problem is I never made a back up or downloaded a rom onto the phone as I hadn't planned to flash any roms. Is there any way I can get a rom onto my phone so I can then flash it in TWRP? I have a Mac.. Thanks for any help...
Got it fixed! Was finally able to connect to my Mac. Then put a rom on the phone using ADB and flashed the rom.
Hello guys and gals,
my wife managed to break her screen on the SM-G900F Model from germany and she got her a new phone. The problem is now that she has some data on the phone she needs (like the google e-mail what she has forgotten the name of) and some other stuff. I want to enable usb debugging over recovery and mirror the screen on my pc (i did that once on my old Galaxy S3 Neo).
I was searching on this forums for a sollution to enable usb debugging over recovery https://forum.xda-developers.com/showthread.php?t=2697523.
I managed to flash the recovery, but adb still does not recognise the phone while in recovery mode. I am running out of options and i really need help of some dev to decompile the kernel, edit the init-rc, and to recompile the kernel, so i could flash it on the phone. I was looking at some guides, but i just don't get it how to do that
Click to expand...
Click to collapse
It would help if someone has some user friendly guide to do that, so i would try that on my own.
I hope there is someone who can help me.
Stock Rom version: G900FXXS1CPLV_G900FDBT1CPJ1_G900FXXU1CPJ1_HOME.tar.md5
Click to expand...
Click to collapse
Hi,
Why not using latest TWRP custom recovery instead of trying old/outdated and not officially supported CWM?
I have no problem with accessing to ADB from latest TWRP.
TomyVk said:
Hello guys and gals,
my wife managed to break her screen on the SM-G900F Model from germany and she got her a new phone. The problem is now that she has some data on the phone she needs (like the google e-mail what she has forgotten the name of) and some other stuff. I want to enable usb debugging over recovery and mirror the screen on my pc (i did that once on my old Galaxy S3 Neo).
I was searching on this forums for a sollution to enable usb debugging over recovery https://forum.xda-developers.com/showthread.php?t=2697523.
It would help if someone has some user friendly guide to do that, so i would try that on my own.
I hope there is someone who can help me.
Click to expand...
Click to collapse
Boot to TWRP recovery
Then enter these commands in a terminal/cmd window on pc
If you're not rooted leave out the su from below - think it should still work
Assuming you have Samsung USB drivers & adb setup on pc
Code:
adb shell
su
mount -o remount,rw /system
cd /
echo "persist.service.adb.enable=1" >> default.prop
echo "persist.service.debuggable=1" >> default.prop
echo "persist.sys.usb.config=mtp,adb" >> default.prop
echo "persist.service.adb.enable=1" >> /system/build.prop
echo "persist.service.debuggable=1" >> /system/build.prop
echo "persist.sys.usb.config=mtp,adb" >> /system/build.prop
This will enable adb but you still may face unauthorized as you get a prompt on phone screen to allow adb & to accept connection - you maybe able to manually send the rsa key but you will have to Google that if you face that problem - it will depend on Android version
ADB should be enabled in latest twrp recovery so pull the build.prop edit it then push it back setting correct permissions
However if you are simply copying files just enter twrp & you will be able to see all your phone files via USB connection on your pc
Obviously with Google email you would need to boot the phone so try the above to enable adb debugging in normal boot
TheFixItMan said:
Boot to TWRP recovery
Then enter these commands in a terminal/cmd window on pc
If you're not rooted leave out the su from below - think it should still work
Assuming you have Samsung USB drivers & adb setup on pc
Code:
adb shell
su
mount -o remount,rw /system
cd /
echo "persist.service.adb.enable=1" >> default.prop
echo "persist.service.debuggable=1" >> default.prop
echo "persist.sys.usb.config=mtp,adb" >> default.prop
echo "persist.service.adb.enable=1" >> /system/build.prop
echo "persist.service.debuggable=1" >> /system/build.prop
echo "persist.sys.usb.config=mtp,adb" >> /system/build.prop
This will enable adb but you still may face unauthorized as you get a prompt on phone screen to allow adb & to accept connection - you maybe able to manually send the rsa key but you will have to Google that if you face that problem - it will depend on Android version
ADB should be enabled in latest twrp recovery so pull the build.prop edit it then push it back setting correct permissions
However if you are simply copying files just enter twrp & you will be able to see all your phone files via USB connection on your pc
Obviously with Google email you would need to boot the phone so try the above to enable adb debugging in normal boot
Click to expand...
Click to collapse
Well, i have flashed the latest twrp recovery twrp-3.2.3-0-klte.img.tar over odin. It flashed without problems.
But the same problem persists, when i boot in to recovery mode adb does not recognise th phone in recovery mode.
When i type adb shell i just get a "error: device not found" from adb
I have installed the newest samsung drivers over Kies3.
TomyVk said:
Well, i have flashed the latest twrp recovery twrp-3.2.3-0-klte.img.tar over odin. It flashed without problems.
But the same problem persists, when i boot in to recovery mode adb does not recognise th phone in recovery mode.
When i type adb shell i just get a "error: device not found" from adb
I have installed the newest samsung drivers over Kies3.
Click to expand...
Click to collapse
How do you know twrp booted if you can't see the screen?
TWRP will have adb support so as long as twrp booted it will work
Once you have flashed twrp in odin you must boot into twrp as soon as the phone restarts for twrp to stick - if you switched the device off or the phone booted normally you will have to reflash twrp - if you can't see the screen that maybe an issue
TheFixItMan said:
How do you know twrp booted if you can't see the screen?
TWRP will have adb support so as long as twrp booted it will work
Once you have flashed twrp in odin you must boot into twrp as soon as the phone restarts for twrp to stick - if you switched the device off or the phone booted normally you will have to reflash twrp - if you can't see the screen that maybe an issue
Click to expand...
Click to collapse
Oh, that might be the problem. What do i have to do after the flashing to boot in to twrp?
The same key combination as for the recovery mode or something else, or do i just disable automatic reboot in odin?
TheFixItMan said:
How do you know twrp booted if you can't see the screen?
TWRP will have adb support so as long as twrp booted it will work
Once you have flashed twrp in odin you must boot into twrp as soon as the phone restarts for twrp to stick - if you switched the device off or the phone booted normally you will have to reflash twrp - if you can't see the screen that maybe an issue
Click to expand...
Click to collapse
TomyVk said:
Oh, that might be the problem. What do i have to do after the flashing to boot in to twrp?
The same key combination as for the recovery mode or something else, or do i just disable automatic reboot in odin?
Click to expand...
Click to collapse
As soon as the device restarts & the Samsung logo appears (that you can't see) hold Vol up home button & power button
Can try disabling auto restart then pull the battery after flash & then hold the button combo to start
TheFixItMan said:
As soon as the device restarts & the Samsung logo appears (that you can't see) hold Vol up home button & power button
Can try disabling auto restart then pull the battery after flash & then hold the button combo to start
Click to expand...
Click to collapse
Thank you, it worked. I will now try to enable the usb debugging
TheFixItMan said:
Boot to TWRP recovery
Then enter these commands in a terminal/cmd window on pc
If you're not rooted leave out the su from below - think it should still work
Assuming you have Samsung USB drivers & adb setup on pc
Code:
adb shell
su
mount -o remount,rw /system
cd /
echo "persist.service.adb.enable=1" >> default.prop
echo "persist.service.debuggable=1" >> default.prop
echo "persist.sys.usb.config=mtp,adb" >> default.prop
echo "persist.service.adb.enable=1" >> /system/build.prop
echo "persist.service.debuggable=1" >> /system/build.prop
echo "persist.sys.usb.config=mtp,adb" >> /system/build.prop
This will enable adb but you still may face unauthorized as you get a prompt on phone screen to allow adb & to accept connection - you maybe able to manually send the rsa key but you will have to Google that if you face that problem - it will depend on Android version
ADB should be enabled in latest twrp recovery so pull the build.prop edit it then push it back setting correct permissions
However if you are simply copying files just enter twrp & you will be able to see all your phone files via USB connection on your pc
Obviously with Google email you would need to boot the phone so try the above to enable adb debugging in normal boot
Click to expand...
Click to collapse
When i try to mount the system partition i just get this:
mount -o remount,rw /system
mount: can't find /system in /proc/mounts
TomyVk said:
When i try to mount the system partition i just get this:
mount -o remount,rw /system
mount: can't find /system in /proc/mounts
Click to expand...
Click to collapse
You might have a problem of when twrp starts it asks you to swipe to allow system modifications but you can't see that
See if are able to do an adb screen cast that allows you to control the screen via adb then you can fully get into twrp
Or see if you can simply pull the build.prop & default.prop to pc & edit it & push it back
TheFixItMan said:
You might have a problem of when twrp starts it asks you to swipe to allow system modifications but you can't see that
See if are able to do an adb screen cast that allows you to control the screen via adb then you can fully get into twrp
Or see if you can simply pull the build.prop & default.prop to pc & edit it & push it back
Click to expand...
Click to collapse
When i type ls in the shell i get this
Code:
ls
boot init.rc sdcard
cache init.recovery.hlthchrg.rc seapp_contexts
charger init.recovery.qcom.rc selinux_version
data init.recovery.service.rc sepolicy
default.prop init.recovery.usb.rc service_contexts
dev license sideload
efs modem sys
etc oem system
external_sd proc tmp
file_contexts property_contexts twres
file_contexts.bak recovery ueventd.qcom.rc
firmware res ueventd.rc
fstab.qcom root usbstorage
init sbin vendor
The system folder is empty tho. I have pulled the default.prop to my pc and pushed it back, created the build.prop and pushed it in to the system folder.
After i did that i typed exit and then adb reboot. Still no usb debugging. I checked the files again and the default.prop was back to the original, and the build.prop from the system folder was gone after the reboot. I don't know what i am doing wrong. I even have root access....
TomyVk said:
When i type ls in the shell i get this
Code:
ls
boot init.rc sdcard
cache init.recovery.hlthchrg.rc seapp_contexts
charger init.recovery.qcom.rc selinux_version
data init.recovery.service.rc sepolicy
default.prop init.recovery.usb.rc service_contexts
dev license sideload
efs modem sys
etc oem system
external_sd proc tmp
file_contexts property_contexts twres
file_contexts.bak recovery ueventd.qcom.rc
firmware res ueventd.rc
fstab.qcom root usbstorage
init sbin vendor
The system folder is empty tho. I have pulled the default.prop to my pc and pushed it back, created the build.prop and pushed it in to the system folder.
After i did that i typed exit and then adb reboot. Still no usb debugging. I checked the files again and the default.prop was back to the original, and the build.prop from the system folder was gone after the reboot. I don't know what i am doing wrong. I even have root access....
Click to expand...
Click to collapse
System isn't mounted which is why you can't access it - you need to swipe to enable system modification when you first start twrp which you can't see hence I said see if are able to control screen from pc
Make sure you set the correct permissions for the file - 644 or rw-r-r
TheFixItMan said:
System isn't mounted which is why you can't access it - you need to swipe to enable system modification when you first start twrp which you can't see hence I said see if are able to control screen from pc
Make sure you set the correct permissions for the file - 644 or rw-r-r
Click to expand...
Click to collapse
File permissions are correct, i have checked them as soon i saw that it wont work.
i have tried to mirror the screen over adb with
https://www.xda-developers.com/scrcpy-control-android-on-pc/
http://marian.schedenig.name/2014/07/03/remote-control-your-android-phone-through-adb/
and i was checking on google arround, nothing works. It also seems like that the touch screen is broken...
Anyone knows maybe annother option to mount the system?
TomyVk said:
File permissions are correct, i have checked them as soon i saw that it wont work.
i have tried to mirror the screen over adb with
https://www.xda-developers.com/scrcpy-control-android-on-pc/
http://marian.schedenig.name/2014/07/03/remote-control-your-android-phone-through-adb/
and i was checking on google arround, nothing works. It also seems like that the touch screen is broken...
Anyone knows maybe annother option to mount the system?
Click to expand...
Click to collapse
No other than the commands I've given you
TheFixItMan said:
No other than the commands I've given you
Click to expand...
Click to collapse
Means the only chance would be to pull a rom and edit it so that adb is enabled and flash it on the device....
Well, i think i got a new hobby xD
Hello
I have a Samsung Galaxy Tab A 10.1 (2016) and i have rooted it. now i am getting that annoying Knox notification about security. I have tried to get rid of it/deactivate but without luck.
I have tried:
- through adb shell command
- A few months ago i have tried to disable a knox service through a bat fille which contains this:
@Echo off
echo ---------------------------------
echo Security Notification Removing
echo By BoxWares
echo ---------------------------------
echo.
echo Please make sure that Sideload mode is enabled from Custom Recovery, and SAMSUNG drivers are installed.
echo.
echo Starting adb server..
echo ADB Starting ..
adb kill-server
echo Waiting for device ..
adb wait-for-device
adb shell su '-C' mount -o rw,remount /system
adb shell su '-C' rm -r /system/app/SecurityLogAgent
echo Security Notification Removed Successfully ..
pause
- through smali patcher
- paid the titanium backup and froze associated apps (what i have found through google search are a bit different associated apps, in the attachment you can see what did titanium backup find under "knox"- i have freeze which you can see in blue + secure folder later).
That goddamn security notification still keeps popping out.
Is there any way to get rid of it? it is really annoying me.
Thank you for helping me