Related
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 !
I installed the OTA update last night and it's just looping through the "alcatel one touch" and "smart move" screens. It's been like that for hours.
I need assistance in getting into recovery mode, and hopefully getting my files off the device.
I have downloaded android-studio and am about to install it to get adb and fastboot, and have downloaded the drivers for the idol 3. At this point when it's plugged in, my computer doesn't recognize the device.
If you did not have usb debugging enabled BEFORE the boot loop installing adb and fastboot now won't do you any good. Are you still able to get into recovery and is it twrp or the factory recovery? Without a direct way to get the phone into bootloader regretfully the only solution is to send it in for warranty repair (or replacement via your credit card if you paid that way under purchase protection)
Are you trying to remove the data to prevent access by others or because you need the data? Did you make any backups to external sd or copied to the pc?
I as well am stuck in bootloop. Was able to get into factory recovery and reset phone several times. Still no luck. I have a TWRP backup, but how to I do a temporary boot into it? Only option available in factory recovery was to sideload via ADB, but no luck using fastboot commands there. Phoned Alcatel and they have referred me back to Amazon. Amazon only wants to refund me, won't exchange! Of course I bought at the pre-order price. Any help would be greatly appreciated.
wrench588 said:
I as well am stuck in bootloop. Was able to get into factory recovery and reset phone several times. Still no luck. I have a TWRP backup, but how to I do a temporary boot into it? Only option available in factory recovery was to sideload via ADB, but no luck using fastboot commands there. Phoned Alcatel and they have referred me back to Amazon. Amazon only wants to refund me, won't exchange! Of course I bought at the pre-order price. Any help would be greatly appreciated.
Click to expand...
Click to collapse
The factory reset killed you....if you had usb debugging enabled prior and had not done a factory reset (which kills /data) you could have possibly gotten to an adb shell long enough to do an adb reboot bootloader. The problem is there's no way now to get you into bootloader....you can't get to it from recovery (factory).
If you purchased it by credit card you might see if their purchase protection (typically 60-90 days) allows a claim submission for a replacement....in this case they would cut you a check for the cost of a replacement after mailing in your old one. That's the only solution I see to remain at the $199 price.
You could also see if amazon will issue a $50 credit to your account in addition to return to allow for repurchase. Unlikely but possible.
Ok thanks for the input and advice. As a last ditch effort, is there a way to create or modify the twrp file as a "signed" zip file so that I could boot into it via stock recovery. This was how I rooted my old Galaxy S2, although it was a CWM recovery.
wrench588 said:
Ok thanks for the input and advice. As a last ditch effort, is there a way to create or modify the twrp file as a "signed" zip file so that I could boot into it via stock recovery. This was how I rooted my old Galaxy S2, although it was a CWM recovery.
Click to expand...
Click to collapse
Nothing so far has worked in that regard...in fact I created a update.zip using "zipme" to replace the build.prop that another user says the factory recovery refused to process.
Without a full factory rom to pull needed info in or the source code to compile one we can't do some of the things which would "save" the device.
wrench588 said:
...Only option available in factory recovery was to sideload via ADB, but no luck using fastboot commands there.
Click to expand...
Click to collapse
Strange ... the stock recovery of 6039y has an option for reboot to the bootloader.
petrov.0 said:
Strange ... the stock recovery of 6039y has an option for reboot to the bootloader.
Click to expand...
Click to collapse
Can you post a screenshot where the option is? I'm not doubting your word but perhaps he's looking in the wrong place? I'm back on TWRP so can't look in the stock recovery myself.
famewolf said:
Can you post a screenshot where the option is? I'm not doubting your word but perhaps he's looking in the wrong place? I'm back on TWRP so can't look in the stock recovery myself.
Click to expand...
Click to collapse
There is no option for screenshot while the phone is in the stock recovery. I need a camera to take a picture of the menu. I can do this later. The menu however looks like this:
Code:
reboot system now
apply update from ADB
apply update from sdcard
apply update from phone storage
wipe data/factory reset
wipe cache partition
reboot to bootloader
power down
view recovery log
petrov.0 said:
There is no option for screenshot while the phone is in the stock recovery. I need a camera to take a picture of the menu. I can do this later. The menu however looks like this:
Code:
reboot system now
apply update from ADB
apply update from sdcard
apply update from phone storage
wipe data/factory reset
wipe cache partition
reboot to bootloader
power down
view recovery log
Click to expand...
Click to collapse
If it's right off the main page like that then I can confirm it's not on the 6045. It's been one of the main issues with folks bricking their devices...if their rom gets messed up and they have factory recovery they have no way to get into bootloader to do anything to repair the device. Seems alcatel needs to add the reboot to bootloader to our recovery. I wonder where we could report that.
Is there a way to "lock" recovery so the updates cannot replace twrp? TWRP allows adb access and reboot to bootloader.
famewolf said:
If it's right off the main page like that then I can confirm it's not on the 6045. It's been one of the main issues with folks bricking their devices...if their rom gets messed up and they have factory recovery they have no way to get into bootloader to do anything to repair the device. Seems alcatel needs to add the reboot to bootloader to our recovery. I wonder where we could report that.
Is there a way to "lock" recovery so the updates cannot replace twrp? TWRP allows adb access and reboot to bootloader.
Click to expand...
Click to collapse
This is a snapshot from the recovery menu of 6039y.
The short answer of your question regarding the "lock" is ... no. If a longer explanation is needed ... this is from the update file, a link to which was provided by you:
Code:
if ! applypatch -c EMMC:/dev/block/bootdevice/by-name/recovery:18393344:f9062580503eb61b315a5d12c5c6b3bb133aa4b2; then
....etc.
what it does is to check the sha1 sum of the recovery partition and if the sha1 sum doesn't match to f9062580503eb61b315a5d12c5c6b3bb133aa4b2 will continue with an overwriting of the recovery partition and then will apply a patch. It can't be changed because the whole update will fail.
yep no bootloader
I've got reboot to boatloader on main page from stock recovery on my 6045k
Sent from hell
famewolf said:
Is there a way to "lock" recovery so the updates cannot replace twrp? TWRP allows adb access and reboot to bootloader.
Click to expand...
Click to collapse
Back to the "lock" question. Probably it is possible the OTA update to be slightly modified and then to be flashed through the TWRP recovery (there is an option in TWRP to skip the signature verification ... the verification will fail if the zip file is modified). But I prefer to wait for the OTA update of the 6039y, as I want to perform some tests with the upgrade.
ractar28 said:
I installed the OTA update last night and it's just looping through the "alcatel one touch" and "smart move" screens. It's been like that for hours.
I need assistance in getting into recovery mode, and hopefully getting my files off the device.
I have downloaded android-studio and am about to install it to get adb and fastboot, and have downloaded the drivers for the idol 3. At this point when it's plugged in, my computer doesn't recognize the device.
Click to expand...
Click to collapse
I am in the same boat as OP re the state my Idol 3 (6045i) is currently in. I also unchecked superuser but did not unroot completely before installing the update. I have not yet done a data wipe through recovery though. Unfortunately, back when I rooted the phone I did NOT check the box telling the phone to remember the computer/RSA key for future use. As a result, now when the phone is stuck at the white/animated Alcatel boot logo I can see the phone under adb devices, but it shows as unauthorized.
One thing that did seem odd, was browsing through stock recovery when trying to browse to apply an update from either phone storage or the SD card, no files are showing up at all. All it is showing is the folder root ( /.. ) in both instances and nothing else. Even after I attempted loading several system update and twrp images (in .zip and .img formats) on the SD card from my computer, once loaded in the phone none of the files show up through stock recovery. Is this SD card not compatible/formatted wrong or is something else going on?
Is there any current method to gaining access to the phone via adb manupulating the adbkey files in the $User$/Home/.android folder? I do currently have the adbkey files on my Mac from connecting the phone previously. I'm assuming these files are uniquely generated hashes?
That is ridiculous if the 6045k has bootloader access from recovery and 6045i does not. What would be the reasoning for this?
Nikola Jovanovic said:
I've got reboot to boatloader on main page from stock recovery on my 6045k
Sent from hell
Click to expand...
Click to collapse
Does the sha1 sum of your recovery happen to match f9062580503eb61b315a5d12c5c6b3bb133aa4b2 ? If so it could solve some issues but why do I suddenly think all 3 models have their own recovery?
---------- Post added at 08:47 AM ---------- Previous post was at 08:43 AM ----------
n3tnut said:
I am in the same boat as OP re the state my Idol 3 (6045i) is currently in. I also unchecked superuser but did not unroot completely before installing the update. I have not yet done a data wipe through recovery though. Unfortunately, back when I rooted the phone I did NOT check the box telling the phone to remember the computer/RSA key for future use. As a result, now when the phone is stuck at the white/animated Alcatel boot logo I can see the phone under adb devices, but it shows as unauthorized.
One thing that did seem odd, was browsing through stock recovery when trying to browse to apply an update from either phone storage or the SD card, no files are showing up at all. All it is showing is the folder root ( /.. ) in both instances and nothing else. Even after I attempted loading several system update and twrp images (in .zip and .img formats) on the SD card from my computer, once loaded in the phone none of the files show up through stock recovery. Is this SD card not compatible/formatted wrong or is something else going on?
Is there any current method to gaining access to the phone via adb manupulating the adbkey files in the $User$/Home/.android folder? I do currently have the adbkey files on my Mac from connecting the phone previously. I'm assuming these files are uniquely generated hashes?
That is ridiculous if the 6045k has bootloader access from recovery and 6045i does not. What would be the reasoning for this?
Click to expand...
Click to collapse
adb reboot bootloader won't work even with it showing unauthorized? If you can get into bootloader you can fix /system without messing up your /data (don't wipe data or you lose adb entirely...you may figure out how to add the correct hash if we can find how it's generated)
Here's some info on the hashes you might find useful taken from: http://nelenkov.blogspot.com/2013/02/secure-usb-debugging-in-android-422.html
Secure ADB implementation
The ADB host authentication functionality is enabled by default when the ro.adb.secure system property is set to 1, and there is no way to disable it via the system settings interface (which is a good thing). The device is initially in the OFFLINE state and only goes into the ONLINE state once the host has authenticated. As you may already know, hosts use RSA keys in order to authenticate to the ADB daemon on the device. Authentication is typically a three step process:
After a host tries to connect, the device sends and AUTH message of type TOKEN that includes a 20 byte random value (read from /dev/urandom).
The host responds with a SIGNATURE packet that includes a SHA1withRSA signature of the random token with one of its private keys.
The device tries to verify the received signature, and if signature verification succeeds, it responds with a CONNECT message and goes into the ONLINE state. If verification fails, either because the signature value doesn't match or because there is no corresponding public key to verify with, the device sends another AUTH TOKEN with a new random value, so that the host can try authenticating again (slowing down if the number of failures goes over a certain threshold).
Signature verification typically fails the first time you connect the device to a new host because it doesn't yet have the host key. In that case the host sends its public key in an AUTH RSAPUBLICKEY message. The device takes the MD5 hash of that key and displays it in the 'Allow USB debugging' confirmation dialog. Since adbd is a native daemon, the key needs to be passed to the main Android OS. This is accomplished by simply writing the key to a local socket (aptly named, 'adbd'). When you enable ADB debugging from the developer settings screen, a thread that listens to the 'adbd' socket is started. When it receives a message starting with "PK" it treats it as a public key, parses it, calculates the MD5 hash and displays the confirmation dialog (an activity actually, part of the SystemUI package). If you tap 'OK', it sends a simple simple "OK" response and adbd uses the key to verify the authentication message (otherwise it just stays offline). In case you check the 'Always allow from this computer' checkbox, the public key is written to disk and automatically used for signature verification the next time you connect to the same host. The allow/deny debugging functionality, along with starting/stopping the adbd daemon, is exposed as public methods of the UsbDeviceManager system service.
We've described the ADB authentication protocol in some detail, but haven't said much about the actual keys used in the process. Those are 2048-bit RSA keys and are generated by the local ADB server. They are typically stored in $HOME/.android as adbkey and adbkey.pub. On Windows that usually translates to %USERPOFILE%\.android, but keys might end up in C:\Windows\System32\config\systemprofile\.android in some cases (see issue 49465). The default key directory can be overridden by setting the ANDROID_SDK_HOME environment variable. If the ADB_VENDOR_KEYS environment variable is set, the directory it points to is also searched for keys. If no keys are found in any of the above locations, a new key pair is generated and saved. On the device, keys are stored in the /data/misc/adb/adb_keys file, and new authorized keys are appended to the same file as you accept them. Read-only 'vendor keys' are stored in the /adb_keys file, but it doesn't seem to exist on current Nexus devices. The private key is in standard OpenSSL PEM format, while the public one consists of the Base 64 encoded key followed by a `[email protected]` user identifier, separated by space. The user identifier doesn't seem to be used at the moment and is only meaningful on Unix-based OS'es, on Windows it is always '[email protected]'.
While the USB debugging confirmation dialog helpfully displays a key fingerprint to let you verify you are connected to the expected host, the adb client doesn't have a handy command to print the fingerprint of the host key. You might think that there is little room for confusion: after all there is only one cable plugged to a single machine, but if you are running a couple of VMs, thing can get a little fuzzy. Here's one of way of displaying the host key's fingerprint in the same format the confirmation dialog uses (run in $HOME/.android or specify the full path to the public key file):
awk '{print $1}' < adbkey.pub|openssl base64 -A -d -a \
|openssl md5 -c|awk '{print $2}'|tr '[:lower:]' '[:upper:]'
We've reviewed how secure ADB debugging is implemented and have shown why it is needed, but just to show that all of this solves a real problem, we'll finish off with a screenshot of what a failed ADB attack against an 4.2.2 device from another Android device looks like:
famewolf said:
adb reboot bootloader won't work even with it showing unauthorized? If you can get into bootloader you can fix /system without messing up your /data (don't wipe data or you lose adb entirely...you may figure out how to add the correct hash if we can find how it's generated)
Click to expand...
Click to collapse
Just tested using adb reboot bootloader again and this is the result: error: device unauthorized. Please check the confirmation dialog on your device.
Something else I tried was running fastboot commands in the narrow window that the phone initially boots (black screen with Android logo) but that didn't seem to work either. I tried:
fastboot reboot-bootloader
fastboot -i 0x1bbb reboot-bootloader
fastboot -i 0x1bbb devices
I noticed if you plug the phone into the computer via USB while the phone is off, it will briefly power on to the Android logo/black screen before flashing the battery status once and turning off. Is this an opportunity to send fastboot or adb commands to the phone?
I'll try messing with the adbkey stuff later when I have time to dig into it.
There is a tool from Alcatel (TCL) which can perform upgrades of the device from a Windows PC. You can try it if nothing else helps. There are two COM ports available under Windows when the device is powered off and the USB cable is connected to the phone. This tool use them to perform some checks on the device and probably will continue with an upgrade (it says that all of your data will be wiped after the upgrade etc. so there is a possibility to overwrite everything with a stock image) ... there are instructions how to work with it. The link is from the French support section of Alcatel. Despite that the program has support for 6039 and 6045 is not clear for which of their versions.
petrov.0 said:
There is a tool from Alcatel (TCL) which can perform upgrades of the device from a Windows PC. You can try it if nothing else helps. There are two COM ports available under Windows when the device is powered off and the USB cable is connected to the phone. This tool use them to perform some checks on the device and probably will continue with an upgrade (it says that all of your data will be wiped after the upgrade etc. so there is a possibility to overwrite everything with a stock image) ... there are instructions how to work with it. The link is from the French support section of Alcatel. Despite that the program has support for 6039 and 6045 is not clear for which of their versions.
Click to expand...
Click to collapse
The problem is we currently have no stock images in the format it requires to flash to restore the device. I would think those have to be available first?
---------- Post added at 02:56 AM ---------- Previous post was at 02:55 AM ----------
n3tnut said:
Just tested using adb reboot bootloader again and this is the result: error: device unauthorized. Please check the confirmation dialog on your device.
Something else I tried was running fastboot commands in the narrow window that the phone initially boots (black screen with Android logo) but that didn't seem to work either. I tried:
fastboot reboot-bootloader
fastboot -i 0x1bbb reboot-bootloader
fastboot -i 0x1bbb devices
I noticed if you plug the phone into the computer via USB while the phone is off, it will briefly power on to the Android logo/black screen before flashing the battery status once and turning off. Is this an opportunity to send fastboot or adb commands to the phone?
I'll try messing with the adbkey stuff later when I have time to dig into it.
Click to expand...
Click to collapse
You can't do fastboot commands until the phone is IN bootloader....so you'd have to do adb reboot bootloader
adb devices
etc....
famewolf said:
The problem is we currently have no stock images in the format it requires to flash to restore the device. I would think those have to be available first?
Click to expand...
Click to collapse
It is possible the program to download these images from a server.
I found another interesting thing. The device has a download mode. It is activated when the phone is powered off and connected to a PC. You must wait the display to turn off after the charging battery symbol and then to press and hold both volume keys, after which to press and hold the power button (without releasing these for the volume). But still don't know what to do in this mode. No device is detected on my Linux box when the phone is in this state. Probably I should try in Windows.
Also when the Alcatel upgrade tool was trying to detect the phone I'm almost sure that one of the COM ports was
Qualcomm HS-USB Diagnostics 9006
there is a lot information for other devices how this can be used to unbrick your phone, so this is a some start. The images which the people flash through it are in raw format.
So, I think I've managed to salvage my bricked Stylo, I somehow also managed to root my Fiance's LG G Stylo that's on the 6.0 update... this is a guide on how to flash a TWRP Recovery I made of a rooted LG G Stylo that is running Android 6.0 This can get you out of a brick or just give your spare phone root access.
Since I can't find any ways to fix this problem on the internet I'll post what I did here so hopefully I can get some other people out of deep water with their phone.
Stylo.zip
I'm going to assume that if you are following these instructions you have already downloaded and extracted the .zip file named Stylo onto your desktop.
All of these files are in the Stylo folder, so you should only have to download Stylo.zip
Minimal ADB & Fastboot installer
LG Phone Drivers
TWRP Backup file
recovery.img
1. Install minimal_adb_fastboot_v1.4.1_setup into the folder you extracted Stylo.zip in
(Install PhoneDrivers if you have not already)
2. Enable USB Debugging on your phone
(If you are boot looping, you should still be able to boot into the bootloader with
minimal adb fastboot just plug it in and let it do it's bootloop while you try
booting into the bootloader really quick, this may take some trial and error)
3. Launch MAF32.exe
(This is Minimal ADB and Fastboot)
4. In the window that pops up type:
adb devices
It should look like this:
PS C:\Users\Hyperion\Desktop\Stylo> adb devices
List of devices attached
LGMS6318bb1ce9a device
5. Next you will need to type:
adb reboot bootloader
Now, the powershell screen should look like this:
PS C:\Users\Hyperion\Desktop\Stylo> adb devices
List of devices attached
LGMS6318bb1ce9a device
PS C:\Users\Hyperion\Desktop\Stylo> adb reboot bootloader
PS C:\Users\Hyperion\Desktop\Stylo>
6. Once you are in the bootloader type:
fastboot boot recovery.img
(If you opened the PowerShell window by holding shift and using the right click menu,
the recovery.img file should load on its own, your PowerShell window should now look something like this)
PS C:\Users\Hyperion\Desktop\Stylo> adb devices
List of devices attached
LGMS6318bb1ce9a device
PS C:\Users\Hyperion\Desktop\Stylo> adb reboot bootloader
PS C:\Users\Hyperion\Desktop\Stylo> fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.367s]
booting...
OKAY [ 0.011s]
finished. total time: 0.380s
finished. total time: 0.379s
PS C:\Users\Hyperion\Desktop\Stylo>
7. Once TWRP boots up on your device you will need to navigate to Backup
Uncheck everything but boot
Start the backup process
(We are making a backup of boot
so we can take the name of the folder
it makes in /sdcard/TWRP/BACKUPS
and copy/paste that to the rooted backup file.
TWRP will create a backup of your
boot animation that contains your PHONE ID #
In my case it created a file named LGMS6318bb1ce9a )
8. Open your sdcard contents on your computer
navigate to /sdcard/TWRP/BACKUPS
Copy the name of the new folder that was created (Mine is LGMS6318bb1ce9a)
Open the Stylo folder on your Desktop \Desktop\Stylo\TWRP\BACKUPS
Paste the new folder name over the folder titled (Paste Here)
Overwrite the folder in /sdcard/TWRP/BACKUPS that contains
the boot animation with the new folder from \Desktop\Stylo\TWRP\BACKUPS
9. If you are not in TWRP on your phone any more, repeat steps 3. - 6.
10. Once in TWRP click WIPE in the top right, and Swype to Factory Reset
(Unless your backup file is being loaded from Internal Storage)
11. Navigate to RESTORE in TWRP, find your Backup file in the /TWRP/BACKUPS directory
LEAVE EVERYTHING CHECKED!
(If you uncheck anything the phone will not be rooted upon restore of the backup)
(Alternatively you can uncheck Data and have a fresh install of 6.0 with no root.)
The rooted backup should be installing 4144mb worth of data.
I left a few apps on the desktop that I figured would help some people out
Hope this worked for you, getting root on these phones is a *****.
-Mike
Screenshots were taken after the first boot of the Recovered device
Hardware Info
Software Info
Root Check
Can't make it past adb reboot bootloader, phone goes into a unlock mode and freezes up
I know a site that has the QFIL files necessary to actually unbrick a hard bricked Stylo H631. I'm not sure if I'm allowed to link them ..but I will tell you they charge 11.99USD. I'm hoping to have the $ to do it Friday...if I can...I'll give it a try and post findings here
Sent from my ROOTED LG-TP260 Thanks to Messi yet again!!!
SoonersChuck said:
I know a site that has the QFIL files necessary to actually unbrick a hard bricked Stylo H631. I'm not sure if I'm allowed to link them ..but I will tell you they charge 11.99USD. I'm hoping to have the $ to do it Friday...if I can...I'll give it a try and post findings here
Sent from my ROOTED LG-TP260 Thanks to Messi yet again!!!
Click to expand...
Click to collapse
I'm still waiting from someone in the comments from that site to confirm it's not a scam.
I need to find out the pin test spots on the h631/ms631... anyone know of a diagram or schematic floating around??? If so, I may have this figured out...don't want to poke around on my only board and make it completely useless
SoonersChuck said:
I need to find out the pin test spots on the h631/ms631... anyone know of a diagram or schematic floating around??? If so, I may have this figured out...don't want to poke around on my only board and make it completely useless
Click to expand...
Click to collapse
You mean a diagram of the emmc?
Anything that shows me where to touch to get the desired reaction
---------- Post added at 08:50 PM ---------- Previous post was at 08:49 PM ----------
Clk Dat0 gnd...those spots
When i type "fastboot boot recovery.img" in command prompt it comes up with a message saying "cannot load 'recovery.img': No such file or directory". Can someone help? The recovery file is on my desktop
---------- Post added at 11:56 PM ---------- Previous post was at 11:07 PM ----------
fixed my earlier issue but now when my device loads TWRP and i select to back up "boot", it fails.
---------- Post added 19th March 2018 at 12:44 AM ---------- Previous post was 18th March 2018 at 11:56 PM ----------
how do i open the sdcard contents on my computer?
trejose said:
When i type "fastboot boot recovery.img" in command prompt it comes up with a message saying "cannot load 'recovery.img': No such file or directory". Can someone help? The recovery file is on my desktop
---------- Post added at 11:56 PM ---------- Previous post was at 11:07 PM ----------
fixed my earlier issue but now when my device loads TWRP and i select to back up "boot", it fails.
---------- Post added 19th March 2018 at 12:44 AM ---------- Previous post was 18th March 2018 at 11:56 PM ----------
how do i open the sdcard contents on my computer?
Click to expand...
Click to collapse
ya gotta check all the boxes possible after going into the MOUNT options when in TWRP. always before doing almost anything in TWRP. sometimes its persistant, sometimes not depending on device.
---------- Post added at 08:15 AM ---------- Previous post was at 08:09 AM ----------
trejose said:
When i type "fastboot boot recovery.img" in command prompt it comes up with a message saying "cannot load 'recovery.img': No such file or directory". Can someone help? The recovery file is on my desktop
---------- Post added at 11:56 PM ---------- Previous post was at 11:07 PM ----------
fixed my earlier issue but now when my device loads TWRP and i select to back up "boot", it fails.
---------- Post added 19th March 2018 at 12:44 AM ---------- Previous post was 18th March 2018 at 11:56 PM ----------
how do i open the sdcard contents on my computer?
Click to expand...
Click to collapse
Enable MTP in the MOUNT options while in TWRP
I can't seem to get my T-Mobile Stylo 5 to go into fastboot mode. Adb reboot bootloader just reboots the phone for me. Maybe a downgrade is required?? Also I just used platform-tools adb and fastboot. Build# PKQ1.190302.001
I have used ADB sideloaded android wear on my HW2 before Oreo update. All drivers have been set up and working previously. After Oreo, I have tried both my Window 10 Laptop and Windows 7 Laptop. I have enabled USB debug from the Watch. However, no device can be recognised by ADB. Can't see any android device in Device Manager. I have to manually install the new OS. What can I do ?
Have you re-enabled ADB Debugging on the watch?
I am able to push files via ADB After update fine.
---------- Post added at 02:22 PM ---------- Previous post was at 02:21 PM ----------
Also try the Windroid Tool. See if it can detect the watch by showing status 'Online"
hasn4179 said:
Have you re-enabled ADB Debugging on the watch?
I am able to push files via ADB After update fine.
---------- Post added at 02:22 PM ---------- Previous post was at 02:21 PM ----------
Also try the Windroid Tool. See if it can detect the watch by showing status 'Online"
Click to expand...
Click to collapse
Thank you very much for your help. Tried a couple of times on Windows 7 but not working. On Windows 10 finally worked. But when I try to sideload the wear OS 2.10, I was told the intall failed as it is a version downgrade. What can I do?
Ok, thats weird.
I haven't personally done any sideloading yet. But when I was comparing all the details with other peoples' posts, I noticed that even though my OS was 2.9, I also had March security patches installed. Maybe there is a check to see if going to 2.10 may result in downgrading of either the security patch or google play services version, and the system may not allow that.