Related
Hello, i just got my new samsung 7 plus with honeycome 3.2 and im loving it
I want to know what is the step by step instruction to rooting my device using adb?
the root.zip i found on here dont work for me. when i save the file to /sdcard and n reboot n go into wher i applie the zip from sdcard it shows no files at all on my card. i bought the 16gb version of this tab so i dont have the externel sdcard. i thought that i read one the forum you can only use the externel card not the interel. i believe they added the folder /sdcard to the internel drive and thats why it not viewing.
The rooting instructions say to put it on an "external" sdcard for a reason as recovery will not recognize the internal storage. Do you have adb installed on your computer and at least know how to use it? If not it is going to be way easier for you to just go and spend the $10 for an 8 GB sdcard and install it that way.
I can at least get you part way, installing the sdk and jdk. Here are the instructions for installing the android sdk (adb) direct from google. You also need the java jdk installed on your commputer and google has a link in their instructions.
http://developer.android.com/sdk/installing.html
You first need the proper usb drivers installed and not exactly sure on how to do that. I already had the android usb drivers installed on my computer for my phone and I just let the compter install whatever else it needed the first time I connected my tab to it.
You will need usb debugging turned in your settings and then power the tab off. You would then plug the usb cable into the tab and computer then boot it into recovery. Once into recovery Mount/System. You then run adb in a command window and change the drive to the platform-tools directory where adb resides. It would look something like this in a command window (c:\android-sdk-windows\ is how I set my computer up yours may be different):
cd c:\android-sdk-windows\platform-tools
To check and see if your device is recognized by adb run the command:
adb devices
If nothing is listed then adb isn't recognizing the device and you would need to troubleshoot your installation or boot method.
As far as installing the root.zip file I'm not sure as I've never had to do that before as I've always had an external sdcard on my devices. Maybe someone else can take you thru the last step. I believe all you would do is push the file inside the zip folder over to the tab. The su file inside the root.zip folder needs to be in the same directory as adb, platform-tools directory.
adb push su /system/bin
I'm not sure if you need to change permissions on this file or not and that is done thru a chmod command in adb shell but not sure of the proper code to use for the GTab to do this. For my phone setting permissions looks like this:
adb shell
cd /system/bin
chmod 0644 Su
exit
Do not use this chmod as I'm not sure it will work on the GTab or what it will do to it, it just an example.
In summary these are the basic steps you are trying to accomplish:
1. Install Java JDK
2. Install Android SDK
3. Install USB drivers
4. Turn USB debugging on in Tabs settings
5. Boot Tab into recovery while connected to PC
6. Mount/System in recovery
7. ADB push su file to system/bin
8. Set permissions of su???
9. Exit adb
10. Reboot phone and install superuser and busy box from market
Thanks im rooted now. I took the sdcard out of my droidx & it works on my galaxy tab & i used the root.zip file.
Sent from my GT-P6210 using Tapatalk
ronlsjr said:
Thanks im rooted now. I took the sdcard out of my droidx & it works on my galaxy tab & i used the root.zip file.
Sent from my GT-P6210 using Tapatalk
Click to expand...
Click to collapse
Yes any sdcard will do and that is the easiest way. Though I think everyone should learn how to use adb anyways as it is useful especially if you get into modding.
Yes i do want to learn how to use adb. My desire is to become a developer.
Sent from my GT-P6210 using Tapatalk
Just follow the link I provided previously to the android developers site and follow the instructions. You will first have to have Java JDK installed and a link to that is provided on the android developers website in the link. Once JDK is installed download and install the SDK. It will only put the basic functions onto your computer and you will have to install the rest through SDK Manager, this can take a while, up to an hour or so depending on what packages you want to install. At the minimum you would want the Android 3.2 API (GTab 7+ uses this) and the Google USB drivers and then any other API's for phones you may have. I myself installed all the API's as my first phone had Donut (Android 1.6).
I know this may be a stupid question but why root? what special features does it give you? I am not sure If I want to or not.
Anyone? I'm just curious if I should flash a ROM on here or not I just don't know why because it works fine now after the SwiftKey x and other little apps
Sent from my SGH-T869 using XDA Premium App
don't get confused by the lingo...
Noah321 said:
Anyone? I'm just curious if I should flash a ROM on here or not I just don't know why because it works fine now after the SwiftKey x and other little apps
Sent from my SGH-T869 using XDA Premium App
Click to expand...
Click to collapse
There's a difference between "flashing a ROM" and "adding root access".
A custom ROM implies someone has taken the stock software infrastructure, altered/tailored/customized it, and packaged it for others to easily use.
"Rooting" a device just simply gives you access to certain folders, permissions, files, etc.
It's like giving yourself Admin Rights to your work computer (assuming you're over 18 and/or working).
It allows you to do things that the manufacture probably didn't want you to do - like delete "bloatware" (unwanted apps).
If helpful, click "Thanks"
I'm not sure if this the right place to post this-
-This is for the people who couldn't
Get the heimdall way to work.. follow these instructions: http://www.redmondpie.com/root-samsung-stratosphere-4g-on-android-2.3.5-gingerbread-how-to-tutorial/ all the way up to step 6.
Run s2 rooter
Root it
You might have to download superuser from the market as I had it installed already
Update the su binary from within the superuser app.. not mandatory but I did it..
And you will have root.
Things you'll need:
Usbdeview: http://download.cnet.com/USBDeview/3000-2094_4-10614190.html
if ADB isn't seeing ur phone unplug ur phone run usbdeview.exe uninstall the drivers that came from the phone plug phone back in and let them install wait for it to install ADB driver for the phone..debug mode enabled of course.
S2 rooter: http://forum.xda-developers.com/attachment.php?attachmentid=750990&d=1318718398
Have usb debugging enabled
Kernel and heimdall: is in the very first link at the top
If in need of help just email me [email protected]
I'm not very good with writing instructions but I could help directly
Here's a idea, can someone let me know if they think it will work. If the zimage is renamed to a .tar, would it be safe to flash the new tar with oden?
Rocky
Please advise that the source was from here if I am not mistaken
http://rootzwiki.com/topic/7840-kernel-guide-root-your-stratosphere/
heimdall flash -–kernel root-zImage
into rooting the Stratosphere, but the link you provided has a (-) missing in the command and it will not flash, if the creator of the blog, site, blah etc; corrects it, I would not use this link if I were to search again,
http://www.redmondpie.com/root-samsung-stratosphere-4g-on-android-2.3.5-gingerbread-how-to-tutorial/
heimdall flash –kernel root-zImage
A knoob will grow a tumor if he does not see it?
screwFACE_DROIDpower said:
I'm not sure if this the right place to post this-
-This is for the people who couldn't
Get the heimdall way to work.. follow these instructions: http://www.redmondpie.com/root-samsung-stratosphere-4g-on-android-2.3.5-gingerbread-how-to-tutorial/ all the way up to step 6.
Run s2 rooter
Root it
You might have to download superuser from the market as I had it installed already
Update the su binary from within the superuser app.. not mandatory but I did it..
And you will have root.
Things you'll need:
Usbdeview: http://download.cnet.com/USBDeview/3000-2094_4-10614190.html
if ADB isn't seeing ur phone unplug ur phone run usbdeview.exe uninstall the drivers that came from the phone plug phone back in and let them install wait for it to install ADB driver for the phone..debug mode enabled of course.
S2 rooter: http://forum.xda-developers.com/attachment.php?attachmentid=750990&d=1318718398
Have usb debugging enabled
Kernel and heimdall: is in the very first link at the top
If in need of help just email me [email protected]
I'm not very good with writing instructions but I could help directly
Click to expand...
Click to collapse
---------- Post added at 02:32 PM ---------- Previous post was at 02:30 PM ----------
rocksteady said:
Here's a idea, can someone let me know if they think it will work. If the zimage is renamed to a .tar, would it be safe to flash the new tar with oden?
Rocky
Click to expand...
Click to collapse
Don't do it.
This is TWRP recovery and Stock rooted roms for the ICS firmware on the tablet.
These will only work if you currently have ICS running on your tablet. If you still have honeycomb then do the upgrade first.
Nothing was added or removed from the stock roms besides root and busybox.
Only bug with TWRP is that you can't mount sdcard in recovery. Just use adb push.
Instructions for installing TWRP Recovery:
1. Ensure you have Android SDK installed with adb and fastboot working
2. Download both the twrprecovery.img and twrprecovery.zip from here
3. Copy twrprecovery.zip to external sdcard
4. Reboot tablet to bootloader by issuing the command "adb reboot bootloader"
5. Then "fastboot boot twrprecovery.img"
6. When in recovery choose install then browse to /sdcard and choose twrprecovery.zip and flash that zip
7. Now TWRP is installed permanently.
Thanks:
attn1 - gave me some help since I am new to pantech devices
Dees_troy - for TWRP code obviously
Tassadar - for his rotation code for twrp. Without this it wouldn't have been possible
Disclaimer: Flash this ROM at your own risk. I am not responsible for what you do on your device. I left this stock to provide a base for anybody that wants to use it. Mod this rom how you want. Just please remember to give credit where credit is due.
This is a pure stock rooted rom. It has items like busybox, init.d support and so forth. No apps were added or removed. Both Odexed and Deodexed versions below.
Downloads
just in case i need another
Once I reboot into fastboot, I am getting 'cannot load twrprecovery.img': no error
Any ideas? I even created a directory named tools in the adb directory on my computer and moved twrprecovery.img into it.
(Thought that might help).
Where is the twrprecovery.img file supposed to reside? (On the computer, or on the phone?)
mavblues said:
Once I reboot into fastboot, I am getting 'cannot load twrprecovery.img': no error
Any ideas? I even created a directory named tools in the adb directory on my computer and moved twrprecovery.img into it.
(Thought that might help).
Where is the twrprecovery.img file supposed to reside? (On the computer, or on the phone?)
Click to expand...
Click to collapse
On the computer. your command prompt should be at wherever you put twrprecovery.img file is. So for example you put twrprecovery.img at the root of c:, your command prompt should read c:/ .....
Sent from my M7 using xda premium
Tada!!!
Thanks, you rock!
---------- Post added at 01:39 PM ---------- Previous post was at 01:10 PM ----------
OK, stupid question:
How do you reboot to TWRP? It loaded the first time, and I did a backup.
After reboot, I can only seem to get into the standard recovery.
What is the button combination to get to TWRP?
Also, will we be able to use goo manager to update TWRP as new versions come out, or is this a custom version?
TIA
mavblues said:
Tada!!!
Thanks, you rock!
---------- Post added at 01:39 PM ---------- Previous post was at 01:10 PM ----------
OK, stupid question:
How do you reboot to TWRP? It loaded the first time, and I did a backup.
After reboot, I can only seem to get into the standard recovery.
What is the button combination to get to TWRP?
Also, will we be able to use goo manager to update TWRP as new versions come out, or is this a custom version?
TIA
Click to expand...
Click to collapse
Read the instructions. You HAVE to flash the zip I provided for recovery to be installed permanently.
This recovery required some special code for screen rotation. Dees_troy is working on getting it added to mainline. So right now you can't get it through goo manager. But I work closely with Dees to make sure all my builds are officially supported. I will post here when it becomes available through there
Sent from my M7 using xda premium
jmztaylor said:
Read the instructions. You HAVE to flash the zip I provided for recovery to be installed permanently.
This recovery required some special code for screen rotation. Dees_troy is working on getting it added to mainline. So right now you can't get it through goo manager. But I work closely with Dees to make sure all my builds are officially supported. I will post here when it becomes available through there
Sent from my M7 using xda premium
Click to expand...
Click to collapse
Got it - working great!
I'm stuck on fastboot mode. <waiting on device>
I tried unplug/replug USB to different connector, and it's still on <waiting for device>
I even tried to install driver manually from each files pantech folder and still no response
TWRP is on same folder and also set on environment variable
I have done adb devices and it detects as PORORO03111xxxxxxxxxxx
Any suggestion guys?
dagadu said:
I'm stuck on fastboot mode. <waiting on device>
I tried unplug/replug USB to different connector, and it's still on <waiting for device>
I even tried to install driver manually from each files pantech folder and still no response
TWRP is on same folder and also set on environment variable
I have done adb devices and it detects as PORORO03111xxxxxxxxxxx
Any suggestion guys?
Click to expand...
Click to collapse
Waiting on device in fastboot means drivers aren't installed or the wrong ones are. Download the software upgrade app from pantech site then install. Browse to the install directory and run the installer for the drivers. But before that uninstall whatever drivers you have installed currently. I'm mobile or else I would link you directly
Sent from my M7 using xda premium
dagadu said:
I'm stuck on fastboot mode. <waiting on device>
I tried unplug/replug USB to different connector, and it's still on <waiting for device>
I even tried to install driver manually from each files pantech folder and still no response
TWRP is on same folder and also set on environment variable
I have done adb devices and it detects as PORORO03111xxxxxxxxxxx
Any suggestion guys?
Click to expand...
Click to collapse
Did you check "USB debugging" on the tablet?
Also, I had to set USB connection on the tablet to the last choice "PC Data Mode".
Hope it helps.
jmztaylor said:
Waiting on device in fastboot means drivers aren't installed or the wrong ones are. Download the software upgrade app from pantech site then install. Browse to the install directory and run the installer for the drivers. But before that uninstall whatever drivers you have installed currently. I'm mobile or else I would link you directly
Sent from my M7 using xda premium
Click to expand...
Click to collapse
Is this what you're referring to? I download it from Pantech website.
htt p://c7240 62.r62 .cf2.rackcdn. com/PantechPCSuite_1.1.1.3437. exe
When do I need to install the driver? During fastboot mode, or normal mode?
I also notice that when I change the usb mode to MTP, it detects missing driver as well.
During normal mode it detects 2 pantech drivers in order to connect to pc suite.
Oya, when you guys do adb devices, does your device detect POROROxxxxxxx as well or only numbers?
I wonder this has anything to do with it, because I was trying to root with honeycomb version earlier and my pantech is ICS 4.0.4
dagadu said:
Is this what you're referring to? I download it from Pantech website.
htt p://c7240 62.r62 .cf2.rackcdn. com/PantechPCSuite_1.1.1.3437. exe
When do I need to install the driver? During fastboot mode, or normal mode?
I also notice that when I change the usb mode to MTP, it detects missing driver as well.
During normal mode it detects 2 pantech drivers in order to connect to pc suite.
Oya, when you guys do adb devices, does your device detect POROROxxxxxxx as well or only numbers?
I wonder this has anything to do with it, because I was trying to root with honeycomb version earlier and my pantech is ICS 4.0.4
Click to expand...
Click to collapse
Anytime when the tablet is not plugged in. This will make the computer automatically install anything needed for the tablet and you won't have issues with fastboot or adb anymore
Sent from my M7 using xda premium
jmztaylor said:
Instructions for installing TWRP Recovery:
1. Ensure you have Android SDK installed with adb and fastboot working
2. Download both the twrprecovery.img and twrprecovery.zip from here
3. Copy twrprecovery.zip to external sdcard
4. Reboot tablet to bootloader by issuing the command "adb reboot bootloader"
5. Then "fastboot boot twrprecovery.img"
6. When in recovery choose install then browse to /sdcard and choose twrprecovery.zip and flash that zip
7. Now TWRP is installed permanently.
Click to expand...
Click to collapse
I did not understand anything of this manual...
I took the CWM file for Pantech A810S and replaced it recovery to ours, flashed(connect working Element to PC and start cwm.but), everything works.
1806 said:
I did not understand anything of this manual...
I took the CWM file for Pantech A810S and replaced it recovery to ours, flashed(connect working Element to PC and start cwm.but), everything works.
Click to expand...
Click to collapse
Actually it's similar steps; however, yours is more like 1-click root
Anyway, I tried everything all above, but it didn't solve my problem, then I found the solution from other website
I just want to share in case others are stuck in fastboot mode like me:
1. When your tablet screen is on fastboot mode (white), go to device manager on your pc
2. Right click on Android > Update driver
3. Click on Browse driver
4. Choose Let me pick manually from my pc list
5. Choose Android phone and pick the first list there. It should be "Android ADB..."
6. Install and fastboot continued
if you can't find Android ADB from your pc list, then you should unplug device then install PC Suite.
here's the old tuts: youtube com/watch?v=UHRonVzBMsI
Hopefully it helps others and thank you very much for all your help!
Delete!
Finally! and a question
Finally a recovery for the element! Rhanks to the OP. Now I am less afraid to tinker with my tablet.
Question: The most important thing right now that I'd like to do is move the folder /data/data from the internal storage, to the internal SD card. This is stopping me from using Google Magazines and Google music, since their data is being stored there, and it shares space with actual applications. 1GB is not that much space for APPS, Dalvik Cache and APPs' data when you add magazines, and when google starts caching Music and Chrome data there. I currently only have 300MB left before I install Music and magazines. And that is AFTER I've used app2sd on all apps that can be moved. How do I do this?
I have tried simply creating a Link using "ln - s /mnt/sdcard/data /data/data" once I copied/moved the contents of the directory, which sort of works initially, but it will not work after a reboot. It actually stops my tablet from booting. (again, thanks to the OP for the recovery).
right now, I am just doing an "ln" on the specific folder inside the /data/data folder, but it acts weird when I use Titanium Backup to restore data
-> Android noob <-
Installing TWRP went smooth as silk. With twrprecovery.zip on you micro sdcard and Element connected with usb cable and USB debuuging checked 1.Just copy twrprecovery.img into your sdk folder/ platform-tools and also have a copy of cmd.exe from windows in the platform-tools folder. 2. Start cmd.exe and type or copy & paste command reboot bootloader 3. Then on white screen(fastboot) type or paste command fastboot boot twrprecovery.img 4. When you boot into TWRP install twrprecovery.zip.....As you rebbot system TWRP should ask if you want Supersu installed and swipe to install. Once rebooted install supersu from the Play store and open Supersu to update SU file all should be good
Thanks for the info and files. I know I'm a little late on this Tablet but picked it up cheap and with ATT 4G it goes along with my devices. The orginial owner hadn't even installed ICS and she wasn't even aware of an update. She now owns an Apple :laugh::laugh:device LOL
I just picked one up for $90 bucks off ebay. It was on slickdeals .net
Figured i'd use it around the pool and save my phone!
No one has deved a JB rom though Could KK even be possible?
marcustaz said:
I just picked one up for $90 bucks off ebay. It was on slickdeals .net
Figured i'd use it around the pool and save my phone!
No one has deved a JB rom though Could KK even be possible?
Click to expand...
Click to collapse
Yes good deal, got mine last month on Craigslist for $70.00 and works really well. The owner hadn't even updated to 4.0 or even knew how. It is a good tablet and have rooted it. I think its development is pretty well dead as not many sold. Only thing bad about it is the Element reads 2nd partition instead of 1st as most android devices do, so harder to use link2sd or folder mount as they both use 2nd partition.
Sent from my PantechP4100 using XDA Premium 4 mobile app
A lot of people have questions about using ADB, so I decided to make a very simple guide to some basic ADB operations. This information is available all over XDA, but many people don't seem to like looking through other device threads.
ADB should function in recovery and when the tablet is normally booted.
Install ADB on your PC.
Download the attached ADB_files.zip
Create a folder to hold the ADB files (I will use C:\ADB) and extract the files to that folder.
Download and install the Samsung USB drivers (available HERE), or, install KIES to get the drivers.
On the tablet, go to Settings, Developer Options and enable USB debugging.
Connect the Tablet to your PC via USB cable.
Open a command prompt in your ADB folder. The text at the prompt should read C:\ADB. (You can just click on the Command_Prompt.bat to do this).
Verify ADB is working by typing "adb devices" (and hit ENTER) in the command window. You should see a device number listed for your tablet.
You are now ready to use ADB functions.
I have included in the zip a few .bat files to perform some of the basic commands for you. These commands will output files to your ADB directory.
Below are some of the common commands you can use with ADB for troubleshooting purposes:
- To boot into Download mode:
adb reboot download
- To boot into recovery:
adb reboot recovery
- To reboot:
adb reboot
- To get the last_kmsg (to troubleshoot kernel issues):
adb shell cat /proc/last_kmsg > last_kmsg.txt
- To get the dmesg:
adb shell su -c dmesg > dmesg.txt
- To get the logcat:
adb logcat -v time -d > logcat.log
The first time you use the "su" command, you may need to acknowledge the Superuser request on your tablet in order for the superuser permissions to be granted.
These are some very basic examples of what can be done with ADB, but they are very helpful when troubleshooting many issues. There are MANY other commands for ADB(that can be Googled).
There are also some apps that can do this for you, but I prefer to do these things manually most of the time.
Feel free to post any useful adb commands you use on a regular basis.
HOW TO GET A RECOVERY.LOG
If you are in your custom recovery:
Make sure you have adb working on your PC (see above).
Connect your device to PC.
Open a command prompt; then CD to your adb directory.
Type the following command:
Code:
adb pull /cache/recovery/*
You will get several files in your adb directory (log, last_log, last_log.1...etc)
Send those files to your developer.
If you are booted into Android:
Make sure you have adb working on your PC (see above).
Connect your device to PC.
Open a command prompt; then CD to your adb directory.
Type the following commands:
Code:
adb shell
su
mkdir /storage/sdcard0
cp /cache/recovery /storage/sdcard0/recovery
exit
exit
adb pull /storage/sdcard0/recovery
You will get several files in your adb directory (log, last_log, last_log.1...etc)
Send those files to your developer.
I have my GT-P5210 (wifi) rooted...
I have not been able to get ADB to work properly once
Wish I I had tried before I rooted this device.
I have tried via WifI & USB = no go.
Anyway no big deal I guess, running 'ES File Explorer' on a rooted device gives me all the power I need.
Just miss the convenience of sending a single APP from PC to Tablet (without cable) to install.
Well ok then..
I finally tried a different version of adb.exe than the one I originally used (was about 400kb), and now it's all working as expected..Yay
Maybe the version I tried was a bit dated ? not even sure where that is now, lol
done too much since, being a new pad owner and all.
Now I am able to make use of "Right Click APK" >> install via Wireless Connection.
No wires, no prompts.
Just wanted to post a follow up in case anyone thought I inferred 'rooting' somehow cost me ADB functionality
Very happy
:good:
(OP get's a +one for making me revisit the issue)
The best and most simple guide
it`s just what you need
Oxyandy said:
I have my GT-P5210 (wifi) rooted...
I have not been able to get ADB to work properly once
Wish I I had tried before I rooted this device.
I have tried via WifI & USB = no go.
Anyway no big deal I guess, running 'ES File Explorer' on a rooted device gives me all the power I need.
Just miss the convenience of sending a single APP from PC to Tablet (without cable) to install.
Click to expand...
Click to collapse
It's extremely easy to get ADB working on a Tab 3 10.1, just make sure USB Debugging is enabled and reboot. Press the bottom button of the Volume key and Power supply key at the same time. Then Samsung Galaxy Tab 3 10.1 will enter hboot mode.
calden74 said:
It's extremely easy to get ADB working on a Tab 3 10.1, just make sure USB Debugging is enabled and reboot. Press the bottom button of the Volume key and Power supply key at the same time. Then Samsung Galaxy Tab 3 10.1 will enter hboot mode.
Click to expand...
Click to collapse
I guess you missed Post #3 just after that one, I have it working no problem, I had to use a different version of ADB.EXE
Cheers and thanks for the kind offer of help
Oxyandy
cant get into recovery
gr8nole said:
A lot of people have questions about using ADB, so I decided to make a very simple guide to some basic ADB operations. This information is available all over XDA, but many people don't seem to like looking through other device threads.
ADB should function in recovery and when the tablet is normally booted.
Install ADB on your PC.
Download the attached ADB_files.zip
Create a folder to hold the ADB files (I will use C:\ADB) and extract the files to that folder.
Download and install the Samsung USB drivers (available HERE), or, install KIES to get the drivers.
On the tablet, go to Settings, Developer Options and enable USB debugging.
Connect the Tablet to your PC via USB cable.
Open a command prompt in your ADB folder. The text at the prompt should read C:\ADB. (You can just click on the Command_Prompt.bat to do this).
Verify ADB is working by typing "adb devices" (and hit ENTER) in the command window. You should see a device number listed for your tablet.
You are now ready to use ADB functions.
I have included in the zip a few .bat files to perform some of the basic commands for you. These commands will output files to your ADB directory.
Below are some of the common commands you can use with ADB for troubleshooting purposes:
- To boot into Download mode:
adb reboot download
- To boot into recovery:
adb reboot recovery
- To reboot:
adb reboot
- To get the last_kmsg (to troubleshoot kernel issues):
adb shell cat /proc/last_kmsg > last_kmsg.txt
- To get the dmesg:
adb shell su -c dmesg > dmesg.txt
- To get the logcat:
adb logcat -v time -d > logcat.log
The first time you use the "su" command, you may need to acknowledge the Superuser request on your tablet in order for the superuser permissions to be granted.
These are some very basic examples of what can be done with ADB, but they are very helpful when troubleshooting many issues. There are MANY other commands for ADB(that can be Googled).
There are also some apps that can do this for you, but I prefer to do these things manually most of the time.
Feel free to post any useful adb commands you use on a regular basis.
HOW TO GET A RECOVERY.LOG
If you are in your custom recovery:
Make sure you have adb working on your PC (see above).
Connect your device to PC.
Open a command prompt; then CD to your adb directory.
Type the following command:
Code:
adb pull /cache/recovery/*
You will get several files in your adb directory (log, last_log, last_log.1...etc)
Send those files to your developer.
If you are booted into Android:
Make sure you have adb working on your PC (see above).
Connect your device to PC.
Open a command prompt; then CD to your adb directory.
Type the following commands:
Code:
adb shell
su
mkdir /storage/sdcard0
cp /cache/recovery /storage/sdcard0/recovery
exit
exit
adb pull /storage/sdcard0/recovery
You will get several files in your adb directory (log, last_log, last_log.1...etc)
Send those files to your developer.
Click to expand...
Click to collapse
Hello,
When I try to boot into recovery or when I use the above method to boot into recovery my Tab just goes to the
Samsung
GALAXY Tab3
screen and just hangs there
I can get into download mode but ever since I used oden to do recovery.tar.md5 file I have not been able to go into recovery
Any help would greatly be appreciated...
Thanks...
Tom
misterwright said:
Hello,
When I try to boot into recovery or when I use the above method to boot into recovery my Tab just goes to the
Samsung
GALAXY Tab3
screen and just hangs there
I can get into download mode but ever since I used oden to do recovery.tar.md5 file I have not been able to go into recovery
Any help would greatly be appreciated...
Thanks...
Tom
Click to expand...
Click to collapse
Flash the recovery all over again
Brought to you by SM-T210R
Note: adb is functioning correctly
The Tab just hanges when it should be going into recovery
---------- Post added at 10:40 AM ---------- Previous post was at 10:38 AM ----------
I have done that a few times but will try again
Note: I also cant do a factory reset from within the OS...
Thanks...
Tom
misterwright said:
Note: adb is functioning correctly
The Tab just hanges when it should be going into recovery
---------- Post added at 10:40 AM ---------- Previous post was at 10:38 AM ----------
I have done that a few times but will try again
Note: I also cant do a factory reset from within the OS...
Thanks...
Tom
Click to expand...
Click to collapse
Try to reflash rom, firmware and else
Brought to you by SM-T210R
darn
Ripshock said:
Flash the recovery all over again
Brought to you by SM-T210R
Click to expand...
Click to collapse
Reflashed using oden with the same results = I hold down power vol-up and home until the Samsung GALAXY Tab3 screen appears then I let off the power button and the Samsung GALAXY Tab3 screen just sits there
I have tried holding the home and vol-up keys for over a minute with the same results = the Samsung GALAXY Tab3 screen just sits there even after I release all buttons = I have to do a hard boot but then it loads the UI
Tom
misterwright said:
Reflashed using oden with the same results = I hold down power vol-up and home until the Samsung GALAXY Tab3 screen appears then I let off the power button and the Samsung GALAXY Tab3 screen just sits there
I have tried holding the home and vol-up keys for over a minute with the same results = the Samsung GALAXY Tab3 screen just sits there even after I release all buttons = I have to do a hard boot but then it loads the UI
Tom
Click to expand...
Click to collapse
Ok there is a way to flash a recovery or to check if it is there or not if you use twrp use its file manager but don't forget to mount /system or if you are using cmw u need aroma file manager google that, however the problem is idk where is the location of recovery mod so ask @gr8nole
Moreover have you checked if it is a bad download of recovery ofcourse and try other recoveries
Brought to you by SM-T210R
Ripshock said:
Ok there is a way to flash a recovery or to check if it is there or not if you use twrp use its file manager but don't forget to mount /system or if you are using cmw u need aroma file manager google that, however the problem is idk where is the location of recovery mod so ask @gr8nole
Moreover have you checked if it is a bad download of recovery ofcourse and try other recoveries
Brought to you by SM-T210R
Click to expand...
Click to collapse
It does say MD% verified while in Oden but I was thinking the same thing...
I could really use a link to "known good" firmware and rom and anything else that I need...
Thanks
Tom
misterwright said:
It does say MD% verified while in Oden but I was thinking the same thing...
I could really use a link to "known good" firmware and rom and anything else that I need...
Thanks
Tom
Click to expand...
Click to collapse
Well navigate through the forum
Brought to you by SM-T210R
I meant MD5 verified
but would love to try a different download of a recovery if you know of any...
Thanks
Tom
misterwright said:
I meant MD5 verified
but would love to try a different download of a recovery if you know of any...
Thanks
Tom
Click to expand...
Click to collapse
I already have said navigate through the forum! Amd good luck
Brought to you by SM-T210R
Ripshock said:
I already have said navigate through the forum! Amd good luck
Brought to you by SM-T210R
Click to expand...
Click to collapse
Thanks...
If I find a md5 file that works I will post a link
Tom
this worked THANK YOU gr8nole http://forum.xda-developers.com/showthread.php?t=2433853
misterwright said:
Thanks...
If I find a md5 file that works I will post a link
Tom
Click to expand...
Click to collapse
What version of the Tab 3 do you have?
Sent from my SCH-I605
gr8nole said:
What version of the Tab 3 do you have?
Sent from my SCH-I605
Click to expand...
Click to collapse
SM-T210R
Tom
---------- Post added at 01:21 PM ---------- Previous post was at 01:15 PM ----------
gr8nole said:
What version of the Tab 3 do you have?
Sent from my SCH-I605
Click to expand...
Click to collapse
gr8nole,
I found your CWM v6.0.4.8 and flashed and now everything is great
Thank You so much!!!!!!
Tom
---------- Post added at 02:03 PM ---------- Previous post was at 01:21 PM ----------
Ripshock said:
I already have said navigate through the forum! Amd good luck
Brought to you by SM-T210R
Click to expand...
Click to collapse
I clicked thanks on 5 of your post but, I still wanted to tell you how much I appreciated your help!!!!
Tom
misterwright said:
SM-T210R
Tom
---------- Post added at 01:21 PM ---------- Previous post was at 01:15 PM ----------
gr8nole,
I found your CWM v6.0.4.8 and flashed and now everything is great
Thank You so much!!!!!!
Tom
---------- Post added at 02:03 PM ---------- Previous post was at 01:21 PM ----------
I clicked thanks on 5 of your post but, I still wanted to tell you how much I appreciated your help!!!!
Tom
Click to expand...
Click to collapse
Glad it worked
Brought to you by SM-T210R
Hello guys,
Sorry if this is redundant but I did search before making this post so feel free to edit or remove moderators.
I had root prior to last update 7.5.1. Lost root and I could not re-root using Qemu/Root Many/KFAide and I spent a lot of time playing with the CMD prompts. So I was curious and tried Root Master 1.3.6. Sure enough it worked for me in 1 MINUTE!!! So I am only posting this in case there are others out there like me. I found this post to be helpful since it had a lot of pics so I will not put up my own pictures:
http://forum.xda-developers.com/showthread.php?t=2783447
Otherwise, the my cliff notes of the install is:
Copy/transfer Root_Master_1-3-6.apk to any folder on Kindle via usb cable (assuming you installed drivers already, if not search forum)
Install/Open
Select Mulai Root
Popup with two choices will appear Root/Batal (cancel): Select Root
Another popup will show strange characters/Batal: Select Batal this time
You're Done!
Last step: Clean up by going to apps and press/hold root master to remove from device (it's no longer needed since you are rooted and I read it may contain some kind of script that sends your device information to someone bored, however the root itself is safe - I hope!)
Also, four common terms you'll see when you open apps that asks for root permission not covered in the thread above:
jangan tanya lagi - do not ask again
Perizinan - Allow
Tolak - reject
di izinkan xxxxxxxxxxxx dapatkan izin - authorized xxxxxxxxxxxx to get "root" permission (xxx is the name of the app you are opening)
I will post up my version of the file I've used but I believe the file in the thread above is also identical.
Thanks to all and this forum,
Nano out
P.S. Another solution working to removing the Special Offers Lockscreen Ads is to freeze it with Titanium Backup ($$) or ROM Toolbox Lite (free) both can be found on the Google Play Store:
For ROM Toolbox Lite: Open after install, select app manager, click on Kindle Special Offers, select Freeze, then Yes. I'm unsure what the advanced freeze is but my ads are gone and still gone after reboot so I'm a happy camper.
i also have 7.5.1 but stock. never been rooted. i downloaded this APK and followed the instructions... but it didn't successfully root it for me. so... now there's like a Perizinan rumah tangga app that i can't get rid in the app store.... so i'm factory resetting everything again hahaha i think it's malware
---------- Post added at 12:29 AM ---------- Previous post was at 12:17 AM ----------
this is great, this malware has survived a factory reset.... thanks a lot
JediFonger said:
i also have 7.5.1 but stock. never been rooted. i downloaded this APK and followed the instructions... but it didn't successfully root it for me. so... now there's like a Perizinan rumah tangga app that i can't get rid in the app store.... so i'm factory resetting everything again hahaha i think it's malware
---------- Post added at 12:29 AM ---------- Previous post was at 12:17 AM ----------
this is great, this malware has survived a factory reset.... thanks a lot
Click to expand...
Click to collapse
follow the unrooting part mentioned in this guide:
http://forum.xda-developers.com/showthread.php?t=2783447
this is the best method of rooting on 7.5.1:
http://akauntu.blogspot.com/2014/12/install-custom-rom-on-amazon-kindle_26.html
so i did follow both, the first link didn't do anything but load an app and hten it loaded an app that wouldn't go away even after factory reset. great.
secondly, i used the 'best method of rooting on 7.5.1' and the only difference i saw was using non-admin to run commandlines so that made some differences. but i'm not i still have root. the major issue is i can't reboot into fastboot... so that defeats the purpose since i can't downgrade to 7.2.3, which is needed to proceed.
any other tips?
according to a few root checker apps. i have root... but i just can't reboot into fastboot
lolwatpear said:
follow the unrooting part mentioned in this guide:
http://forum.xda-developers.com/showthread.php?t=2783447
this is the best method of rooting on 7.5.1:
http://akauntu.blogspot.com/2014/12/install-custom-rom-on-amazon-kindle_26.html
Click to expand...
Click to collapse
JediFonger said:
so i did follow both, the first link didn't do anything but load an app and hten it loaded an app that wouldn't go away even after factory reset. great.
secondly, i used the 'best method of rooting on 7.5.1' and the only difference i saw was using non-admin to run commandlines so that made some differences. but i'm not i still have root. the major issue is i can't reboot into fastboot... so that defeats the purpose since i can't downgrade to 7.2.3, which is needed to proceed.
any other tips?
according to a few root checker apps. i have root... but i just can't reboot into fastboot
Click to expand...
Click to collapse
The first link I posted was to remove that app installed from root master where is says unrooting and "1.Open "Perizinan rumah tangga."
As for the second link, you should follow the youtube videos as well as some of the info isn't mentioned in the text. You need to make sure the kindle fire drivers are installed properly when using adb and fastboot. One time they were fine for me for adb, but when I went into fastboot, they weren't properly installed. So, I uninstalled them in the device manager and replugged in the kindle and they worked properly.
But since root checker apps are saying you have root, adb shell su -c "reboot bootloader" should get you into fastboot mode. Then you run that other tool to downgrade.
when i run that command i get connection io timer error and thats it. it will only reboot into recovery but never fastboot. i'm tryjng to make or acquire a fastboot cable. the original kindle usb cable is a fastboot cable right? i have to find it not sure where i stored it
---------- Post added at 09:04 PM ---------- Previous post was at 09:02 PM ----------
i dont have any other issues adb driverd and cmd run fine i just cannot get into fastboot no matter what i have used
JediFonger said:
when i run that command i get connection io timer error and thats it. it will only reboot into recovery but never fastboot. i'm tryjng to make or acquire a fastboot cable. the original kindle usb cable is a fastboot cable right? i have to find it not sure where i stored it
---------- Post added at 09:04 PM ---------- Previous post was at 09:02 PM ----------
i dont have any other issues adb driverd and cmd run fine i just cannot get into fastboot no matter what i have used
Click to expand...
Click to collapse
you don't need a fastboot cable for that method. I don't have one myself and have no issue.
when you do "adb devices", does a serial come up?
yes i can run adb devices no problem. i know how to adb kill-server and restart the devices as well so it is detected. i have drivers properly installed as a ADB device under device manager. i can adb reboot and even adb reboot recovery but i can't run adb reboot-bootloader or adb reboot bootloader
and adb shell gets me non-su user prompt but i can't su into the root access #. when i run adb shell su -c "whatever" i get:
[-] connect ui: Timer expired
and that's it. when i run bin4ry rooting i get permission denied i'm guessing on places where it needs to get into fastboot screens.
bought fastboot and now i can get fastboot only through poweron process. which is good! i've downgraded to 7.2.3
July 2017
File: Root_Master_1.3.6_Cekas.apk
VirusTotal: 31 / 61
Root if you like to be hack !