Related
Ok, just bricked my Nextbook 7
Here is how I flashed a firmware without access to recovery:
If you are in a bootloop, Connect USB and Power.
Press and hold pin on back until you hear windows try to detect a device but the screen is off.
Download this: http://arctablet.com/assets/tools/Firmware/Rockchip_CPU_based/Rockchip_Batch_Tool_v1.4.zip
Install the driver from the drivers folder.
3. Installing the drivers on the computer
Following the tablet entering in recovery mode, the computer should now show it has found a new USB device and prompt for a device driver. Select the appropriate driver in the driver directory from the Rockchip Flash Tool 1.4 package.
It will then install the driver for RK29 Device
4. Sending the firmware to the tablet
The flashing tool should display a green square around the number 1 in the lower left area of the Windows application.
Select the firmware file to flash using the button in the top right area of the application. Select the update.img file from here:
http://www.multiupload.com/NQHSNZJSO2
Then push the Upgrade button to transfer the selected firmware to the tablet.
The firmware will be copied to the tablet, a progression counter will go from 0% to 100% on this step, followed by a verification.
You are done, let the tablet reboot and update itself. It should take a few minutes for the flash process to finish.
This procedure has been successfully tested on Windows XP 32 bits for flashing a bricked NextBook 7 Premium YF1011 (but should work on others)
Hi, the multiupload link seems down, would it be possible to re-up? thanks!
And how exactly are you supposed to install the drivers from the driver folder? Because those are not Runable files, theyre drivers, with no install command. So, my daughters nextbook is bricked, wont install drivers(says not successfully installed after i plug it in) and there is no way to install the drivers from the batch file. Anything you left out??? Id like to unbrick this thing. Thanks..
SOLVED
I found out how to install the drivers on windows 7!
Follow this:
click the start button > type in the search box right above the start button "device manager"
(make sure the tablet is plugged in and in USB MODE)
right click the tablet or unknown device
select install/update driver manually
browse for the driver in the download folder then it should be updated
worked for me.
Nextbook 8 stuck in bootloop
I am a noob. My Nextbook 8 is stuck in bootloop, the last app i downloaded was firefox. Ive read that this can be fixed by starting safe mode and doing a factory reset, how do i do this?!? Im desperate, and would greatly appreciate any help that works, thanks.
I recently downloaded an ICS-based, Cynagen 9 ROM. It was making my Infuse very hot, so I decided to restore back to my previous ROM (Ethereal). I've tried Odin (can't get COM## to appear on it) and Heimdall (installed drivers, new version of Java, still doesn't recognize device). I don't want to pay to have it fixed again, so does anyone have any suggestions as to how I can fix myself? I have a blue CWM. Thanks.
GAPY427 said:
I recently downloaded an ICS-based, Cynagen 9 ROM. It was making my Infuse very hot, so I decided to restore back to my previous ROM (Ethereal). I've tried Odin (can't get COM## to appear on it) and Heimdall (installed drivers, new version of Java, still doesn't recognize device). I don't want to pay to have it fixed again, so does anyone have any suggestions as to how I can fix myself? I have a blue CWM. Thanks.
Click to expand...
Click to collapse
I flash a gb rom in blue cwm to get....red cwm, then flash a gb ROM again...
Have you tried diff usb port & cable....pc?
bigjoe2675 said:
I flash a gb rom in blue cwm to get....red cwm, then flash a gb ROM again...
Have you tried diff usb port & cable....pc?
Click to expand...
Click to collapse
I tried to reflash Ethereal ROM but it doesn't work. Oh, hell, I may just get GSIII on Verizon and call it a day.
GAPY427 said:
I tried to reflash Ethereal ROM but it doesn't work. Oh, hell, I may just get GSIII on Verizon and call it a day.
Click to expand...
Click to collapse
way to throw in the towel...some don't have that option...but XDA is learning experience, not for the towel tossers...
but if you require and want it we can provide it for you any and some assistance.
if you no longer require the thread you can click that triangle to the right of your op...and tell mods to close this thread..
thx
Sounds like if you would do a battery pull and get to download mode you could odin or heimdall back but if ya wanna toss money away to upgrade that's cool too
Sent from my SGH-I997 using xda premium
dawsndev said:
Sounds like if you would do a battery pull and get to download mode you could odin or heimdall back but if ya wanna toss money away to upgrade that's cool too
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
That's it -- I tried Odin and Heimdall but they didn't work. I downloaded the drivers several times, but both programs couldn't recognize my device. I couldn't see the COM## in Odin when I plugged in my Infuse.
bigjoe2675 said:
way to throw in the towel...some don't have that option...but XDA is learning experience, not for the towel tossers...
but if you require and want it we can provide it for you any and some assistance.
if you no longer require the thread you can click that triangle to the right of your op...and tell mods to close this thread..
thx
Click to expand...
Click to collapse
I want to fix my Infuse, but it becomes frustrating when you try these programs (Odin, etc.) and it isn't successful. I can't reboot my phone into anything right now (a new ROM, a restore, etc). It's stuck in the blue recovery.
to get COM## Try using a different usb plug. That has always been my fix for that issue
TheDSMjuggalo said:
to get COM## Try using a different usb plug. That has always been my fix for that issue
Click to expand...
Click to collapse
can I get in bluerecovery?
Sent from my SGH-I997 using xda premium
bradman117 said:
can I get in bluerecovery?
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
using a different usb port is for odin. download and flash the modded 3e rom found here: http://forum.xda-developers.com/showthread.php?t=1092021
Then flash over the rom you wanted thru the recovery
GAPY427 said:
I want to fix my Infuse, but it becomes frustrating when you try these programs (Odin, etc.) and it isn't successful. I can't reboot my phone into anything right now (a new ROM, a restore, etc). It's stuck in the blue recovery.
Click to expand...
Click to collapse
Since you're stuck in recovery and can't get Heimdall or Odin to work, you'll need to use adb to do what I'm about to explain. So, let me know if you need a tutorial on using adb. You can use adb to push items to /sdcard/ while in CWM recovery. Using adb, put the rom that you want on the internal sdcard and put Zen Arcade's Infusion-Z kernel zip there as well. Get the kernel here:
http://forum.xda-developers.com/showthread.php?p=25724526
Then, use the install from zip feature in CWM recovery to flash Zen's kernel to the phone. After the kernel flash, unplug the USB cable and shut the phone off by holding down the power button (it won't boot into anything yet). Then hold the power button and two volume buttons. When the Samsung logo appears, release the power button and keep holding the volume buttons until you are in red recovery. Go to mounts and storage and format system, data, and cache. Then, go back to flash your rom and then reboot. If you're still wanting to throw in the towel, mail it to me and I'll do it for you.
Sent from my SGH-I997 using Tapatalk 2
TheDSMjuggalo said:
to get COM## Try using a different usb plug. That has always been my fix for that issue
Click to expand...
Click to collapse
I've tried that several times. My device is not recognized by Odin.
jscott30 said:
Since you're stuck in recovery and can't get Heimdall or Odin to work, you'll need to use adb to do what I'm about to explain. So, let me know if you need a tutorial on using adb. You can use adb to push items to /sdcard/ while in CWM recovery. Using adb, put the rom that you want on the internal sdcard and put Zen Arcade's Infusion-Z kernel zip there as well. Get the kernel here:
http://forum.xda-developers.com/showthread.php?p=25724526
Then, use the install from zip feature in CWM recovery to flash Zen's kernel to the phone. After the kernel flash, unplug the USB cable and shut the phone off by holding down the power button (it won't boot into anything yet). Then hold the power button and two volume buttons. When the Samsung logo appears, release the power button and keep holding the volume buttons until you are in red recovery. Go to mounts and storage and format system, data, and cache. Then, go back to flash your rom and then reboot. If you're still wanting to throw in the towel, mail it to me and I'll do it for you.
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
Yes, I'll need a tutorial on adb.
GAPY427 said:
Yes, I'll need a tutorial on adb.
Click to expand...
Click to collapse
I've put together a package with all that you'll need for adb. Use these instructions to move the files that I mentioned in my earlier post.
First, let's make sure that we are on the same page with drivers, since you have had trouble with both Heimdall and Odin.
1.) Unplug USB cable.
2.) In the Windows Control Panel, go to "Programs and Features" or "Add/Remove Programs" and uninstall any instances of Samsung Kies and SAMSUNG USB Driver for Mobile Phones.
3.) Download and install THIS version of SAMSUNG USB Driver for Mobile Phones.
4.) After installing the driver, plug in USB cable, and give Windows a moment to setup the driver. When your connection is ready, a USB cable with a check beside it should appear in the Windows system tray.
You can give Odin another try, and it should work for you now with the new driver, or you can move forward with using adb to do what you need.
1.) Download and unzip THIS adb package.
2.) Browse to the folder containing adb.exe. Hold down shift and right click with the mouse; then choose "Open command window here".
3.) Make sure that you are in CWM recovery, and in the Windows command prompt, type
Code:
adb devices
If all is working correctly, your device should appear in the list.
4.) Place any files that you want to move to the device in the same folder as adb.exe.
5.) Then do this for each file: Type the command below, but replace fullfilename with the full name of the file.
Code:
adb push [I]fullfilename[/I] /sdcard/
When the transfer finishes, you should be able to access the items on your internal sd card. From here you can follow the instructions that I gave in the earlier post.
jscott30 said:
I've put together a package with all that you'll need for adb. Use these instructions to move the files that I mentioned in my earlier post.
First, let's make sure that we are on the same page with drivers, since you have had trouble with both Heimdall and Odin.
1.) Unplug USB cable.
2.) In the Windows Control Panel, go to "Programs and Features" or "Add/Remove Programs" and uninstall any instances of Samsung Kies and SAMSUNG USB Driver for Mobile Phones.
3.) Download and install THIS version of SAMSUNG USB Driver for Mobile Phones.
4.) After installing the driver, plug in USB cable, and give Windows a moment to setup the driver. When your connection is ready, a USB cable with a check beside it should appear in the Windows system tray.
You can give Odin another try, and it should work for you now with the new driver, or you can move forward with using adb to do what you need.
1.) Download and unzip THIS adb package.
2.) Browse to the folder containing adb.exe. Hold down shift and right click with the mouse; then choose "Open command window here".
3.) Make sure that you are in CWM recovery, and in the Windows command prompt, type
Code:
adb devices
If all is working correctly, your device should appear in the list.
4.) Place any files that you want to move to the device in the same folder as adb.exe.
5.) Then do this for each file: Type the command below, but replace fullfilename with the full name of the file.
Code:
adb push [I]fullfilename[/I] /sdcard/
When the transfer finishes, you should be able to access the items on your internal sd card. From here you can follow the instructions that I gave in the earlier post.
Click to expand...
Click to collapse
Followed your instructions. Removed SAMSUNG drivers. Installed drivers in your instructions. Odin did not work. Tried the other method and I receive this message in the Cmd window: 'adb' is not recognized as an internal or external command, operable program or batch file.
GAPY427 said:
Followed your instructions. Removed SAMSUNG drivers. Installed drivers in your instructions. Odin did not work. Tried the other method and I receive this message in the Cmd window: 'adb' is not recognized as an internal or external command, operable program or batch file.
Click to expand...
Click to collapse
You have to be in the exact directory as adb.exe or you'll continue to get that error. Go to the exact folder, hold shift and right click the mouse in that folder window. Choose "Open command window here".
Good luck, and enjoy the holiday.
Sent from my SGH-I997 using Tapatalk 2
jscott30 said:
You have to be in the exact directory as adb.exe or you'll continue to get that error. Go to the exact folder, hold shift and right click the mouse in that folder window. Choose "Open command window here".
Good luck, and enjoy the holiday.
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
Not working. I'm stuck either in blue recovery or a Galaxy S cyanogen(mod) screen.
GAPY427 said:
Not working. I'm stuck either in blue recovery or a Galaxy S cyanogen(mod) screen.
Click to expand...
Click to collapse
Anyone taking time to help you is going to need more to go on than "Not working." I already know that you're in blue recovery. What's the latest on using adb to push a kernel with red recovery to your device so we can get you back to Gingerbread?
Sent from my SGH-I997 using Tapatalk 2
jscott30 said:
Anyone taking time to help you is going to need more to go on than "Not working." I already know that you're in blue recovery. What's the latest on using adb to push a kernel with red recovery to your device so we can get you back to Gingerbread?
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
I tried pushing a kernel through adb but I didn't see it on my sd card. There were also 4 different choices of kernels (Core A, Core B, etc.). I tried to push A & B but saw neither of them on recovery.
GAPY427 said:
I tried pushing a kernel through adb but I didn't see it on my sd card. There were also 4 different choices of kernels (Core A, Core B, etc.). I tried to push A & B but saw neither of them on recovery.
Click to expand...
Click to collapse
Did you see the transfer in progress in the command line? If so, and if the transfer finished, it's on there. I wonder if you're looking on your external sd card instead of the internal.
Sent from my SGH-I997 using Tapatalk 2
---------- Post added at 08:59 PM ---------- Previous post was at 08:54 PM ----------
Alright, in blue recovery, go to "install zip from sdcard".
Then, go to "choose zip from sdcard". Do you see the items that you pushed with adb listed there? Don't choose "choose zip from internal sdcard". Despite what that sounds like, it's your external sdcard.
Hello everyone, Im making a new rooting tutorial for the Samsung Galaxy S Relay 4G as the last tutorial [root]\{cm9} samsung galaxy relay 4g (updated 11/19) wasn't working for me. This tutorial will also have more details so will be easier to follow for the less technical.
BEFORE I START I AM IN NO WAY RESPONSIBLE IF YOU BRICK YOUR DEVICE. ROOTING YOUR PHONE WILL VOID YOUR WARRANTY..
1. Follow this guide for setting up the SDK. If you already have SDK, great move on to step 2
2. Download Drivers and install them. If you already have your drives installed move on to stop 3
3. Download Odin v3.04
4. Unzip the Odin archive. Put it somewhere you can find it, on the root of your C:\ drive is a good place.
5. Download ClockworkMod-based Recovery
6. Unzip cwm.tar.zip into Odin3-v3.04 folder that you unzipped in step 4
7. Download Super User
8. Place UPDATE-SuperSU-v1.25.zip on your phones sdcard.
9. Run the Odin executable "Odin3 v3.04.exe" in the Odin3-v3 folder
9.5 Go into your phone settings and click on Develop Option then make sure USB Debugging is checked.
10. Power off your Samsung Galaxy S Relay 4G and connect the USB adapter to the computer and to your Samsung Galaxy S Relay 4G
11. Boot the Samsung Galaxy S Relay 4G into download mode by holding down Home, Volume Down and Power
NOTE: To confirm the device is connected and working, look for the blue COM box with the word Added!! inside
12. Uncheck the box labeled Auto Reboot
13. Press the dialog box labeled PDA and select the ClockworkMod-based Recovery named "cwm.tar.md5"
14. Press start and a blue transfer bar will appear on the device showing the recovery being transferred
15. Once the recovery has been transferred you should see a Green PASSED. At his point disconnect the Samsung Galaxy S Relay 4G and remove the battery
14. Put your battery back in your Samsung Galaxy S Relay 4G and Immediately boot into recovery by holding down Home, Volume Up and Power
15. Once in recovery use volume down to select install zip from sdcard and hit power
16. Use volume down key to select UPDATE-SuperSU-v1.25.zip and hit power.
17. Now you are rooted but we are not done yet, Reboot your phone and make sure super user is showing up in the app drawer.
18. Now open up a cmd window by going to the start menu of windows and typing in cmd in the search or by clicking on run on the right hand side.
19. In the cmd window navigate to adb which is part of the SDK kit you installed in step one.
20. Once you are in the same directory as adb.exe type adb shell.
21. Now type su and a pop up will show up on your phone
22. Click grant permission yes
23. Now type mount -o remount rw /system
24. Type cd system
25. Type rm recovery-from-boot.p
26. Type cd etc
27. Type rm install-recovery.sh
28. Repeat steps 9 to 14 BUT SKIP STEP 12
9. Run the Odin executable "Odin3 v3.04.exe" in the Odin3-v3 folder
10. Power off your Samsung Galaxy S Relay 4G and connect the USB adapter to the computer and to your Samsung Galaxy S Relay 4G
11. Boot the Samsung Galaxy S Relay 4G into download mode by holding down Home, Volume Down and Power
NOTE: To confirm the device is connected and working, look for the blue COM box with the word Added!! inside
13. Press the dialog box labeled PDA and select the ClockworkMod-based Recovery named "cwm.tar.md5"
14. Press start and a blue transfer bar will appear on the device showing the recovery being transferred.
Phone will restart and you now have a custom recovery and are rooted.
Thanks Jay
Jay Dogg said:
Hello everyone, Im making a new rooting tutorial for the Samsung Galaxy S Relay 4G as the last tutorial [root]\{cm9} samsung galaxy relay 4g (updated 11/19) wasn't working for me. This tutorial will also have more details so will be easier to follow for the less technical.
BEFORE I START I AM IN NO WAY RESPONSIBLE IF YOU BRICK YOUR DEVICE. ROOTING YOUR PHONE WILL VOID YOUR WARRANTY..
1. Follow this guide for setting up the SDK. If you already have SDK, great move on to step 2
2. Download Drivers and install them. If you already have your drives installed move on to stop 3
3. Download Odin v3.04
4. Unzip the Odin archive. Put it somewhere you can find it, on the root of your C:\ drive is a good place.
5. Download ClockworkMod-based Recovery
6. Unzip cwm.tar.zip into Odin3-v3.04 folder that you unzipped in step 4
7. Download Super User
8. Place UPDATE-SuperSU-v1.25.zip on your phones sdcard.
9. Run the Odin executable "Odin3 v3.04.exe" in the Odin3-v3 folder
9.5 Go into your phone settings and click on Develop Option then make sure USB Debugging is checked.
10. Power off your Samsung Galaxy S Relay 4G and connect the USB adapter to the computer and to your Samsung Galaxy S Relay 4G
11. Boot the Samsung Galaxy S Relay 4G into download mode by holding down Home, Volume Down and Power
NOTE: To confirm the device is connected and working, look for the blue COM box with the word Added!! inside
12. Uncheck the box labeled Auto Reboot
13. Press the dialog box labeled PDA and select the ClockworkMod-based Recovery named "cwm.tar.md5"
14. Press start and a blue transfer bar will appear on the device showing the recovery being transferred
15. Once the recovery has been transferred you should see a Green PASSED. At his point disconnect the Samsung Galaxy S Relay 4G and remove the battery
14. Put your battery back in your Samsung Galaxy S Relay 4G and Immediately boot into recovery by holding down Home, Volume Up and Power
15. Once in recovery use volume down to select install zip from sdcard and hit power
16. Use volume down key to select UPDATE-SuperSU-v1.25.zip and hit power.
17. Now you are rooted but we are not done yet, Reboot your phone and make sure super user is showing up in the app drawer.
18. Now open up a cmd window by going to the start menu of windows and typing in cmd in the search or by clicking on run on the right hand side.
19. In the cmd window navigate to adb which is part of the SDK kit you installed in step one.
20. Once you are in the same directory as adb.exe type adb shell.
21. Now type su and a pop up will show up on your phone
22. Click grant permission yes
23. Now type mount -o remount rw /system
24. Type cd system
25. Type rm recovery-from-boot.p
26. Type cd etc
27. Type rm install-recovery.sh
28. Repeat steps 9 to 14 BUT SKIP STEP 12
9. Run the Odin executable "Odin3 v3.04.exe" in the Odin3-v3 folder
10. Power off your Samsung Galaxy S Relay 4G and connect the USB adapter to the computer and to your Samsung Galaxy S Relay 4G
11. Boot the Samsung Galaxy S Relay 4G into download mode by holding down Home, Volume Down and Power
NOTE: To confirm the device is connected and working, look for the blue COM box with the word Added!! inside
13. Press the dialog box labeled PDA and select the ClockworkMod-based Recovery named "cwm.tar.md5"
14. Press start and a blue transfer bar will appear on the device showing the recovery being transferred.
Phone will restart and you now have a custom recovery and are rooted.
Click to expand...
Click to collapse
Does this root method work for Jelly Bean 4.1.2 running Relay devices?
Sent from my SGH-T699 using xda app-developers app
Chrizuki said:
Does this root method work for Jelly Bean 4.1.2 running Relay devices?
Sent from my SGH-T699 using xda app-developers app
Click to expand...
Click to collapse
yes this should would with any firmware
Jay Dogg said:
Hello everyone, Im making a new rooting tutorial for the Samsung Galaxy S Relay 4G as the last tutorial [root]\{cm9} samsung galaxy relay 4g (updated 11/19) wasn't working for me. This tutorial will also have more details so will be easier to follow for the less technical.
BEFORE I START I AM IN NO WAY RESPONSIBLE IF YOU BRICK YOUR DEVICE. ROOTING YOUR PHONE WILL VOID YOUR WARRANTY..
1. Follow this guide for setting up the SDK. If you already have SDK, great move on to step 2
2. Download Drivers and install them. If you already have your drives installed move on to stop 3
3. Download Odin v3.04
4. Unzip the Odin archive. Put it somewhere you can find it, on the root of your C:\ drive is a good place.
5. Download ClockworkMod-based Recovery
6. Unzip cwm.tar.zip into Odin3-v3.04 folder that you unzipped in step 4
7. Download Super User
8. Place UPDATE-SuperSU-v1.25.zip on your phones sdcard.
9. Run the Odin executable "Odin3 v3.04.exe" in the Odin3-v3 folder
9.5 Go into your phone settings and click on Develop Option then make sure USB Debugging is checked.
10. Power off your Samsung Galaxy S Relay 4G and connect the USB adapter to the computer and to your Samsung Galaxy S Relay 4G
11. Boot the Samsung Galaxy S Relay 4G into download mode by holding down Home, Volume Down and Power
NOTE: To confirm the device is connected and working, look for the blue COM box with the word Added!! inside
12. Uncheck the box labeled Auto Reboot
13. Press the dialog box labeled PDA and select the ClockworkMod-based Recovery named "cwm.tar.md5"
14. Press start and a blue transfer bar will appear on the device showing the recovery being transferred
15. Once the recovery has been transferred you should see a Green PASSED. At his point disconnect the Samsung Galaxy S Relay 4G and remove the battery
14. Put your battery back in your Samsung Galaxy S Relay 4G and Immediately boot into recovery by holding down Home, Volume Up and Power
15. Once in recovery use volume down to select install zip from sdcard and hit power
16. Use volume down key to select UPDATE-SuperSU-v1.25.zip and hit power.
17. Now you are rooted but we are not done yet, Reboot your phone and make sure super user is showing up in the app drawer.
18. Now open up a cmd window by going to the start menu of windows and typing in cmd in the search or by clicking on run on the right hand side.
19. In the cmd window navigate to adb which is part of the SDK kit you installed in step one.
20. Once you are in the same directory as adb.exe type adb shell.
21. Now type su and a pop up will show up on your phone
22. Click grant permission yes
23. Now type mount -o remount rw /system
24. Type cd system
25. Type rm recovery-from-boot.p
26. Type cd etc
27. Type rm install-recovery.sh
28. Repeat steps 9 to 14 BUT SKIP STEP 12
9. Run the Odin executable "Odin3 v3.04.exe" in the Odin3-v3 folder
10. Power off your Samsung Galaxy S Relay 4G and connect the USB adapter to the computer and to your Samsung Galaxy S Relay 4G
11. Boot the Samsung Galaxy S Relay 4G into download mode by holding down Home, Volume Down and Power
NOTE: To confirm the device is connected and working, look for the blue COM box with the word Added!! inside
13. Press the dialog box labeled PDA and select the ClockworkMod-based Recovery named "cwm.tar.md5"
14. Press start and a blue transfer bar will appear on the device showing the recovery being transferred.
Phone will restart and you now have a custom recovery and are rooted.
Thanks Jay
Click to expand...
Click to collapse
I've done most of the instructions said and everything seems fine with my phone. I have SU and it is rooted, but I'm stuck on "25. Type rm recovery-from-boot.p" because when I type it in, it says that the rm failed because there was no such file or directory. Is it really important/necessary to have a custom recovery?
Chrizuki said:
I've done most of the instructions said and everything seems fine with my phone. I have SU and it is rooted, but I'm stuck on "25. Type rm recovery-from-boot.p" because when I type it in, it says that the rm failed because there was no such file or directory. Is it really important/necessary to have a custom recovery?
Click to expand...
Click to collapse
Quick answer is no you do not need the custom recovery but it is a good idea to have it. As far as step 25 goes make sure you are in the correct directory. Once you have gotten into your phone using adb shell type cd system. Then type pwd and make sure you are in /system. If you are in system type "ls" and see if the file "recovery-from-boot.p" is there. Repeat these steps for the "install-recovery.sh" file. Now if both file are gone off your phone you can Repeat steps 9 to 14 BUT SKIP STEP 12 or even better if the files didn't exist at all then your should be rooted and already have the custom recovery. You can check to see if you have the custom recovery by booting into recovery by holding down Home, Volume Up and Power or by typing adb reboot recovery but make sure you are not in adb shell.
I wrote this tutorial because the Samsung Galaxy Relay 4g I was rooting had these files "recovery-from-boot.p" and "install-recovery.sh" which was more or less a fail safe for the phones recovery. Every time the phone booted it was checking the recovery and replacing it with the stock recovery by using those two files. So my work around was to get the phone rooted and delete those two files then reflash the custom recovery.
This procedure worked perfectly for me, thanks. I just bought this phone for my Wife. It auto-upgraded to Jelly Bean OTA, and I was ready to root and load recovery. I'm now rooted, and took my first nandroid backup.
The only thing I had to figure out, was how to boot to download mode and recovery. I've done this procedure on many phones and tablets, including a Samsung Galaxy S2, but this phone was a little different. After pressing the volume key, home, and power, you have to release all buttons as soon as you see any text on the screen. For download mode, I had to immediately press volume up within 2 seconds, or it would continue to something else.
I'm curious about this clockwork recovery too. Was it originally written for another device? It works good. I just don't see it offered for this phone in Rom Manager.
Again thanks for taking time to type up this procedure, and for the extra steps at the end for the override.
CWM isn't in ROM Manager probably because we haven't submitted it to them
cannot cannot for the life of me get this phone to go in recovery. Basically stuck right at step 11. Nothing doing. I hold V down, power, home then I get a msg that tells me V down to power off and V up to start download. Anything I do, phone will just reboot. What am I missing?
devis said:
cannot cannot for the life of me get this phone to go in recovery. Basically stuck right at step 11. Nothing doing. I hold V down, power, home then I get a msg that tells me V down to power off and V up to start download. Anything I do, phone will just reboot. What am I missing?
Click to expand...
Click to collapse
Step 11 is to boot into download mode not recovery but in post 6 Jorakal said "The only thing I had to figure out, was how to boot to download mode and recovery. I've done this procedure on many phones and tablets, including a Samsung Galaxy S2, but this phone was a little different. After pressing the volume key, home, and power, you have to release all buttons as soon as you see any text on the screen. For download mode, I had to immediately press volume up within 2 seconds, or it would continue to something else." I didn't have to do it that way but if it worked for Jorakal it may work for you.
If that doesn't work for you, you can always try using adb to reboot into download mode the command is "adb reboot download", this will work for you but you may run into problems on step 14 if you can't boot into recovery using "Home, Volume Up and Power" because by the time you can use adb to boot into recovery the phone has already replaced your custom recovery with the stock one.
I'll try... thanks!
14. Press start and a blue transfer bar will appear on the device showing the recovery being transferred
15. Once the recovery has been transferred you should see a Green PASSED.
Click to expand...
Click to collapse
I conclude it is in Odin program.
But on the phone even when its finished in Odin, still white Downloading... And green : Do not turn off target.
Is it right, as I have some problems after reboot.
It is like crashing 3 or 4 times, you can see that on my video.
http://youtu.be/3V24FbY0jH8
I used Odin 3.07 and Super User 1.34
In phone I can see :
Qualcomm secureboot : enable - is that OK?
UPDATE:
All is working fine now.
I follow all steps again.
We don't need to do it with adb, all related commands to adb could be done in shell apk.
Regards and thanks for tutorial.
Jay Dogg said:
Hello everyone, Im making a new rooting tutorial for the Samsung Galaxy S Relay 4G as the last tutorial [root]\{cm9} samsung galaxy relay 4g (updated 11/19) wasn't working for me. This tutorial will also have more details so will be easier to follow for the less technical.
BEFORE I START I AM IN NO WAY RESPONSIBLE IF YOU BRICK YOUR DEVICE. ROOTING YOUR PHONE WILL VOID YOUR WARRANTY..
1. Follow this guide for setting up the SDK. If you already have SDK, great move on to step 2
2. Download Drivers and install them. If you already have your drives installed move on to stop 3
3. Download Odin v3.04
4. Unzip the Odin archive. Put it somewhere you can find it, on the root of your C:\ drive is a good place.
5. Download ClockworkMod-based Recovery
6. Unzip cwm.tar.zip into Odin3-v3.04 folder that you unzipped in step 4
7. Download Super User
8. Place UPDATE-SuperSU-v1.25.zip on your phones sdcard.
9. Run the Odin executable "Odin3 v3.04.exe" in the Odin3-v3 folder
9.5 Go into your phone settings and click on Develop Option then make sure USB Debugging is checked.
10. Power off your Samsung Galaxy S Relay 4G and connect the USB adapter to the computer and to your Samsung Galaxy S Relay 4G
11. Boot the Samsung Galaxy S Relay 4G into download mode by holding down Home, Volume Down and Power
NOTE: To confirm the device is connected and working, look for the blue COM box with the word Added!! inside
12. Uncheck the box labeled Auto Reboot
13. Press the dialog box labeled PDA and select the ClockworkMod-based Recovery named "cwm.tar.md5"
14. Press start and a blue transfer bar will appear on the device showing the recovery being transferred
15. Once the recovery has been transferred you should see a Green PASSED. At his point disconnect the Samsung Galaxy S Relay 4G and remove the battery
14. Put your battery back in your Samsung Galaxy S Relay 4G and Immediately boot into recovery by holding down Home, Volume Up and Power
15. Once in recovery use volume down to select install zip from sdcard and hit power
16. Use volume down key to select UPDATE-SuperSU-v1.25.zip and hit power.
17. Now you are rooted but we are not done yet, Reboot your phone and make sure super user is showing up in the app drawer.
18. Now open up a cmd window by going to the start menu of windows and typing in cmd in the search or by clicking on run on the right hand side.
19. In the cmd window navigate to adb which is part of the SDK kit you installed in step one.
20. Once you are in the same directory as adb.exe type adb shell.
21. Now type su and a pop up will show up on your phone
22. Click grant permission yes
23. Now type mount -o remount rw /system
24. Type cd system
25. Type rm recovery-from-boot.p
26. Type cd etc
27. Type rm install-recovery.sh
28. Repeat steps 9 to 14 BUT SKIP STEP 12
9. Run the Odin executable "Odin3 v3.04.exe" in the Odin3-v3 folder
10. Power off your Samsung Galaxy S Relay 4G and connect the USB adapter to the computer and to your Samsung Galaxy S Relay 4G
11. Boot the Samsung Galaxy S Relay 4G into download mode by holding down Home, Volume Down and Power
NOTE: To confirm the device is connected and working, look for the blue COM box with the word Added!! inside
13. Press the dialog box labeled PDA and select the ClockworkMod-based Recovery named "cwm.tar.md5"
14. Press start and a blue transfer bar will appear on the device showing the recovery being transferred.
Phone will restart and you now have a custom recovery and are rooted.
Thanks Jay
Click to expand...
Click to collapse
I had to struggle with two points. But got them afterwards. Hence it would be great if you update the instructions:
11. Boot the Samsung Galaxy S Relay 4G into download mode by holding down Home, Volume Down and Power
For me, I also had to need to hold down these buttons, but then after message text is coming up, I also then had to release all the buttons and then press Volume up within one second, 2 seconds are too late. Please for that reason just give a note mentioning this in case if its not enough.
please also complete the notice:
NOTE: To confirm the device is connected and working, look for the blue COM box with the word Added!! inside the message box
otherwise I was really confused because in the COM box there is no such text coming in it, and didnt know if I can go ahead or not.
Please check and rewrite the numbers in correct order after 14 - 15 - 14
also because of this:
16. Use volume down key to select UPDATE-SuperSU-v1.25.zip and hit power.
That was the most difficult part for me as I was getting the message: "E: failed to verify whole-file signature" and the installation failed. I found the solution after many google tries. which is in our case to restart the instruction from 15. and go ahead without failing each steps till 16.
Hence, note: In case of failure, repeat the steps from 15 again.
Jay Dogg said:
28. Repeat steps 9 to 14 BUT SKIP STEP 12
...
Phone will restart and you now have a custom recovery and are rooted.
Click to expand...
Click to collapse
Can I ask what the significance of running step 28 (the repeat step) is?
Is it necessary for recovery to work properly? I only ask because i installed the recovery following these steps up to but not including step 16, and then tried installing the new bootloader, modem, and latest CM nightly, but it's not getting past the CM splash screen
well I got CM to boot by just rewiping and reflashing, but I'm still curious about step 28. I find every phone can have their quirks and it's important to learn them if your'e going to be flashing
Do I need to root te device to flash other roms ? I've red somewhere that I don't have to do this on this device.
My device has the latest official jelly been, so it has the latest radio & bootloader.
edit: It this the correct order ? (I always wipe all partitions before flashing a rom, expect recovery):
http://forum.xda-developers.com/showpost.php?p=46578334&postcount=8
Ziida said:
Can I ask what the significance of running step 28 (the repeat step) is?
Is it necessary for recovery to work properly? I only ask because i installed the recovery following these steps up to but not including step 16, and then tried installing the new bootloader, modem, and latest CM nightly, but it's not getting past the CM splash screen
well I got CM to boot by just rewiping and reflashing, but I'm still curious about step 28. I find every phone can have their quirks and it's important to learn them if your'e going to be flashing
Click to expand...
Click to collapse
Because of these files "recovery-from-boot.p" and "install-recovery.sh" which was more or less a fail safe for the phones recovery. Every time the phone booted it was checking the recovery and replacing it with the stock recovery by using those two files. So my work around was to get the phone rooted and delete those two files then reflash the custom recovery. Because at this point when you reboot the phone to delete those to files they have already ran and you don't have a custom recovery, all you have is root which is what you need to delete those two files =). It appears some people didn't have these files because they had already rooted there phone be for or where not on the most current OTA. If they didn't have the files then they were done at step 17 and if they had tried to go further would of gotten a errors at steps 25 and 27. But if they had the files and stopped at 17 they would no longer have a custom recovery after they had rebooted the phone. So over all steps repeat steps are just to make sure you have a custom recovery installed.
Thanks Jay
Jay Dogg said:
Because of these files "recovery-from-boot.p" and "install-recovery.sh" which was more or less a fail safe for the phones recovery. Every time the phone booted it was checking the recovery and replacing it with the stock recovery by using those two files. So my work around was to get the phone rooted and delete those two files then reflash the custom recovery. Because at this point when you reboot the phone to delete those to files they have already ran and you don't have a custom recovery, all you have is root which is what you need to delete those two files =). It appears some people didn't have these files because they had already rooted there phone be for or where not on the most current OTA. If they didn't have the files then they were done at step 17 and if they had tried to go further would of gotten a errors at steps 25 and 27. But if they had the files and stopped at 17 they would no longer have a custom recovery after they had rebooted the phone. So over all steps repeat steps are just to make sure you have a custom recovery installed.
Thanks Jay
Click to expand...
Click to collapse
That's very informative. Thank you so much for the response! I guess I just didn't have to continue past step 17!
I get pit error: on heimdall and odin, what's the problem ?
Get PIT for mapping:
Complete(Write) operation failed!
Added!
edit: using another pc and it worked fine with heimdall (very easy to use).
Worked like a champ for me this morning, followed the steps closely. 4th phone rooted...still going strong...
Hello root experts!
I just downloaded all files needed for root and I've got one last question...after these 28 steps procedure whats about my personal data? It will be deleted? Like call log,sms, emails, settings etc... Or it will be untouched?
If no...please can You give me advice for any useful backup app
Many thanks in advance!
EDIT: Already rooted and everything seems to be fine
Having trouble getting superuser zip to intall
I keep getting signature verification failed. tried several places to get superuser zip; same error no matter where. Anyone had this issue?
Thx!
Ok, I have scoured google, xda, galaxytabhacks... you name it. I have pretty much tried it all. Yes I have tried heimdall, odin in virtualbox, updated ia32-libs, tried adb, tried fastboot... You name it.
I have a Galaxy Tab 2 10.1 (Wifi) and I thought it would be a fairly simple thing to root it and put a cyanogenmod Rom on it using a ubuntu 12.04 based OS PC I have. I guess I am wrong. I have figured out the Power On/Down Vol button puts the device in some recovery mode and the Power On/Up Vol puts it in the Download mode, but pretty much once I do either the usb connection to the device appears to be a brick - no matter what method I use.
When I do power up the device normally I do mtp-tools to try to recognize the device but they do fail to connect to it. So it is not a problem with USB at a low level - and honestly this PC has been used for a lot of technical things and it has worked flawlessly in the past. I have found several posts about linux/ubuntu and doing a root, but they seem to not have full answers.
Any help?
Tek Tengu said:
Ok, I have scoured google, xda, galaxytabhacks... you name it. I have pretty much tried it all. Yes I have tried heimdall, odin in virtualbox, updated ia32-libs, tried adb, tried fastboot... You name it.
I have a Galaxy Tab 2 10.1 (Wifi) and I thought it would be a fairly simple thing to root it and put a cyanogenmod Rom on it using a ubuntu 12.04 based OS PC I have. I guess I am wrong. I have figured out the Power On/Down Vol button puts the device in some recovery mode and the Power On/Up Vol puts it in the Download mode, but pretty much once I do either the usb connection to the device appears to be a brick - no matter what method I use.
When I do power up the device normally I do mtp-tools to try to recognize the device but they do fail to connect to it. So it is not a problem with USB at a low level - and honestly this PC has been used for a lot of technical things and it has worked flawlessly in the past. I have found several posts about linux/ubuntu and doing a root, but they seem to not have full answers.
Any help?
Click to expand...
Click to collapse
Is the cable disconnected when you try it? Also I assume you have a 10.1. You have to be clear on that.
Sent from my GT-P3113 using Tapatalk HD
Luigi2012SM64DS said:
Is the cable disconnected when you try it? Also I assume you have a 10.1. You have to be clear on that.
Sent from my GT-P3113 using Tapatalk HD
Click to expand...
Click to collapse
I have tried it cable disconnected, cable connected, cable complete off both pc and device, cable across the room, cable in a coil, cable in a straight line, cable in the left usb port, cable in the right usb port... You name it. So yes I have tried all of the variations. Trust me I have worked on this for 4 nights solid and have read every variations of tab 10.1 and tab 2 10.1 rooting guide and tried it (which many of them lie).
I think my original post said the device is a Samsung Galaxy Tab 2 10.1, but if it didn't that is the type. Again, I am trying to do this with/on a 64 bit Ubuntu 12.04 laptop. Its actually a Samsung Chronos 7 15.6". I has 3 USB ports and I have tried two of them (my wireless mouse is on one).
1. Put your Tab in download mode, conect it to your PC, run heimdall as root:
Code:
$ sudo heimdall detect
If your device not detected, downgrade heimdall to 1.3.1 .
2. Extract cf-auto-root for your device, flash it:
Code:
$ sudo heimdall flash --recovery recovery.img --cache cache.img
ketut.kumajaya said:
1. Put your Tab in download mode, conect it to your PC, run heimdall as root:
Code:
$ sudo heimdall detect
If your device not detected, downgrade heimdall to 1.3.1 .
2. Extract cf-auto-root for your device, flash it:
Code:
$ sudo heimdall flash --recovery recovery.img --cache cache.img
Click to expand...
Click to collapse
Normaly should
Code:
sudo heimdall flash --recovery recovery.img
be the thing, flash the supersu.zip in Recovery and you have been root.
Have you all udev rules? Fastboot and ADB is installed?
---------- Post added at 10:48 PM ---------- Previous post was at 10:46 PM ----------
Oh and use only heimdall 1.3.1 all higher versions will brick your tab!
ketut.kumajaya said:
1. Put your Tab in download mode, conect it to your PC, run heimdall as root:
Code:
$ sudo heimdall detect
If your device not detected, downgrade heimdall to 1.3.1 .
2. Extract cf-auto-root for your device, flash it:
Code:
$ sudo heimdall flash --recovery recovery.img --cache cache.img
Click to expand...
Click to collapse
heimdall does not detect any device and it was already downgraded to 1.3.1. I have tried to build the 1.4 RC1 but I can't get beyond the lsub1.0.0 32 lib issues. I have also read all the tips on that and none of them seem to work either.
So I assume if I can't detect I can't do (2).
Any??
Any further ideas or help?
Dexxmor said:
Normaly should
Code:
sudo heimdall flash --recovery recovery.img
be the thing, flash the supersu.zip in Recovery and you have been root.
Have you all udev rules? Fastboot and ADB is installed?
---------- Post added at 10:48 PM ---------- Previous post was at 10:46 PM ----------
Oh and use only heimdall 1.3.1 all higher versions will brick your tab!
Click to expand...
Click to collapse
I am only using Heimdall 1.3.1
I develop mobile apps and have adb installed and fastboot is installed. I played around with both of them trying to connect and neither would. Did not try as su.
What did you mean by udev rules?
The device is detectable but not connectable when it is operating normally by this laptop using mtp-tools. So I know the USB ports are working. It seems like once I put the device in either recovery or download modes the ports act "dead" like there is nothing on the other end. Do I need to manually mount something?
Tek Tengu said:
What did you mean by udev rules?
Click to expand...
Click to collapse
You need the 51-android rules to connect successfully a android device
Dexxmor said:
You need the 51-android rules to connect successfully a android device
Click to expand...
Click to collapse
Never heard of these in all the googling... Where can I find them?
http://developer.android.com/tools/device.html
https://code.google.com/p/51-android/
https://help.ubuntu.com/community/AndroidSDK
Put the attached file (the file in the zip) to /etc/udev/rules.d
Dexxmor said:
http://developer.android.com/tools/device.html
https://code.google.com/p/51-android/
https://help.ubuntu.com/community/AndroidSDK
Put the attached file (the file in the zip) to /etc/udev/rules.d
Click to expand...
Click to collapse
So does Heimdall use adb to accomplish its tasks under the hood? Is that the rub?
Sure, and fastboot this both are very important. But without the udev rules they are usseles.
Dexxmor said:
http://developer.android.com/tools/device.html
https://code.google.com/p/51-android/
https://help.ubuntu.com/community/AndroidSDK
Put the attached file (the file in the zip) to /etc/udev/rules.d
Click to expand...
Click to collapse
Still not connecting. Here are screenshots. I have the udev rules set up, and have rebooted adb does not detect any devices when I have the device in Download mode, nor does Heimdall.
Any more ideas??
Tek Tengu said:
Still not connecting. Here are screenshots. I have the udev rules set up, and have rebooted adb does not detect any devices when I have the device in Download mode, nor does Heimdall.
Click to expand...
Click to collapse
Any other ideas?? I am running out of options and I need to root/mod this tablet.
Resolved - but not with Ubuntu
Tek Tengu said:
Any other ideas?? I am running out of options and I need to root/mod this tablet.
Click to expand...
Click to collapse
I think there must just be some issue with Samsung/Ubuntu 12.04 with the USB devices with this Samsung device. I have done a lot of mobile development on this box, and have not run into issues before, but this one I poked and poked, and never made any traction any way.
Finally I brought up a Windows 8 machine (actually a slightly newer version of the same Samsung model, but a 17" laptop vs 15") and ran Odin and accomplished this rooting/ROM'ing with no issues whatsoever. Amazing. I am a big linux fan, have run into fringe issues like this before, normally after some poking resolved them - this one blows me away.
Thanks for the help!
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