[S-OFF] Revone Assistance - One (M7) Q&A, Help & Troubleshooting

For those having issues with Revone S-OFF for their One (as I did)
A little googling and I managed to resolve the issue but cant post it in that specific forum until I make 10 posts (rules are rules eh?)
Applies to Windows Machines as that's what I'm running and haven't tried my Linux box yet
Update your ADB Drivers and files using this link: "dl.google.com/android/repository/platform-tools_r16.0.1-windows.zip" - direct copy of the platform-tools from the SDK but sometimes you don't need all the additional stuff that comes with the SDK
As an 'Old Skool Droider' I simply unpacked to 'C:Andriod' and ran my Command Prompt in there: 'adb devices' comes up clear as does pushing files to and fro etc etc etc.
Probably the simplest thing in the world tbh but I noticed that some folks were still running into issues, since its been a while since I last did some faffing with Android my drivers were older then the Ark
-H
p.s Cant post direct Links either

Related

ADB HELP

I have tried every process I can find in the forum regarding rooting and ADB but I cannot seem to figure this out. I would like to think that I am computer literate and that I know my way around pretty well but somehow this escapes me. I am running Windows 7 64 bit and can't seem to get anything right as far as this process goes.
Is there a rooting/adb for dummies section that someone can point me to?
the sticky wiki for guides at the top of the front page....
try to look around a little before starting new threads.
beyondinferno said:
the sticky wiki for guides at the top of the front page....
try to look around a little before starting new threads.
Click to expand...
Click to collapse
Thanks for your help...I did look around but I still can't get it to work. I've been through quite a few threads. I don't know if I'm missing something somewhere or what.
is your problem your computer not seeing the phone?
i RUU'd my phone earlier today to test out something i did, but then i found out that adb couldn't connect anymore. i'm still trying to figure it out.
Exactly what are ya having problems with?
http://forum.xda-developers.com/showthread.php?t=502010
1. HTC Sync installed?
2. Android SDK downloaded?
3. Debugging enabled on the phone?
4. is ADB showing up in the Device manager?
5. Check this thread out dealing with x64 drivers
http://forum.xda-developers.com/showthread.php?t=560962
Hmmm..
I have Win7 64bit too
I think I just downloaded the newest Android SDK and HtcSync for the Eris. It
works fine for me. What exactly is the issue? You have the phone in debug mode or whatever mode right?
some folks have used PdaNet
http://www.junefabrics.com/android/download.php
first off, I can't get Sync to work at all no matter which version I've tried. Then the drivers won't load for sdk. it just seems like nothing is working together at all.
alright, i figured it out.
uninstall HTC Sync and the HTC Drivers.
reinstall.
done.
justinisyoung said:
alright, i figured it out.
uninstall HTC Sync and the HTC Drivers.
reinstall.
done.
Click to expand...
Click to collapse
yeah just make sure you use the newest HTC Sync for the Eris!
just out of curiosity why the eris? am i going to have issues later down the road?
DanWalker said:
I have tried every process I can find in the forum regarding rooting and ADB but I cannot seem to figure this out. I would like to think that I am computer literate and that I know my way around pretty well but somehow this escapes me. I am running Windows 7 64 bit and can't seem to get anything right as far as this process goes.
Is there a rooting/adb for dummies section that someone can point me to?
Click to expand...
Click to collapse
Alright... what's your main problem? Are you not able to get the ADB driver to work with your phone in Windows 7 64 bit -- if so, do know that it is possible, because I have it working fine on my computer (Win 7 64B).
If ADB driver situation is your problem, do as follows:
1. Download the file below (to desktop for easy access - This is the Vista 64 bit Drivers)
2. Unzip
3. Go to Device Manager
4. Find ADB (It should come up as ADB with a Yellow Exclamation mark next to it)
5. Right click on it, choose update driver
6. When it asks you to auto find the driver or browse for the driver -- choose BROWSE.
7. Set the path to where you downloaded the file, and then click next.
8. If done correctly, you should see a window pop up that says "Successfully installed My HTC driver".
ADB will work after that is complete. To test, open CMD - go to androidsdk\tools folder, and then run adb devices (If serial # appears, there you have it).
Also with the method above, this will allow the HTC Sync application to work as well.
Source: ME, tested extensively and more than once.
DanWalker said:
just out of curiosity why the eris? am i going to have issues later down the road?
Click to expand...
Click to collapse
HTC Sync for the Hero was released before Win7, so the Vista drivers will work but you have to jump through some hoops.
Now the Eris version is the same HTC Sync but it has drivers for Windows 7, it is the same software but is bundled with newer drivers.
Roger that guys, thanks for the help. I will attempt tonight when I get back to my computer.
Ok just got home and am doing the suggested things, after installing the SDK it wants me to install packages and when I choose cancel, windows says the program was not installed correctly. what do i need to install?!
Also no ADB in device manager!
yeah they took out the packages of the SDK, so you have to add them in as needed.
I have a 2nd Win7 box that's an Android virgin, I will try and run through the install tonight(off at 5pm PST)when I get home and I'll document the install.
hang in there.
rlaxton said:
yeah they took out the packages of the SDK, so you have to add them in as needed.
I have a 2nd Win7 box that's an Android virgin, I will try and run through the install tonight(off at 5pm PST)when I get home and I'll document the install.
hang in there.
Click to expand...
Click to collapse
That would be awesome, I'm at the point where I am just about to give up. I have never been so frustrated with a computer. This is the first Windows 7 system I have done anything with and I already don't like it.
DanWalker said:
Ok just got home and am doing the suggested things, after installing the SDK it wants me to install packages and when I choose cancel, windows says the program was not installed correctly. what do i need to install?!
Also no ADB in device manager!
Click to expand...
Click to collapse
Install packages? What? Weird, the Android SDK is natively 32 bit, but will work in Windows 7 64 BIT (That's what I'm running now).
Alright, steps to take:
1. Uninstall/remove everything you did before.
2. Grab the Windows Android SDK -- download it (to the desktop is fine)
3. UNZIP/Extract the SDK
4. Drag the Android SDK to the root of your drive (Local Disk C: )
5. For easy access purposes, RENAME the Android SDK from what you see to something like: androidsdk
6. Open Command Prompt
7. Verify that you can get to the "androidsdk" directory by running the command: cd androidsdk\tools
8. If you can get there -- then good, so far.
9. Now to test "adb" -- Have your phone connected to the PC.
10. While still in command prompt and STILL in the c:\androidsdk\tools: dir... run command: adb devices
11. This should return your Serial #
12. If your serial # shows up, then make sure you can run the command adb shell and see if you get the # sign, which indicates that you are rooted -- If not, then you need to begin the process of rooting your phone.
Also, if ADB doesn't work after this point, do what I told you earlier, I can guarantee that it does work, because I actually did it this morning on my work computer (Which is Windows 7 64 Bit).
Good luck, report back.
Holy crap it looks like it worked!! Thanks Pseudo! Now if I could only get my damn phone to find Sync I'd be all set.
Still can't get sync to register with phone but that's no biggie. But have a small issue that I dunno where to look to find an answer. I'm trying to update my recovery from 1.5.2 to 1.6.2 and can't seem to follow the directions appropriately.
via adb -> Requires a custom recovery (with test-keys)
Code:
Copy recovery-RA-heroc-v1.6.2.img to the root of your sdcard
Boot into your current custom recovery (boot while holding HOME)
Connect your Hero via usb to your pc/mac/...
adb shell
$su (not required if you have root already)
#mount -a
#flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2.img
None of that seems to work lol.
So since we're on the subject does anyone know how to set up the drivers for linux mint kde? I'm brand new to linux and I've managed to do some things but that is just one thing that i cant do so far and after almost a day pf searching this forum and others i just cant seem to get it
DanWalker said:
Holy crap it looks like it worked!! Thanks Pseudo! Now if I could only get my damn phone to find Sync I'd be all set.
Still can't get sync to register with phone but that's no biggie. But have a small issue that I dunno where to look to find an answer.
Click to expand...
Click to collapse
First off, no problem for the help -- glad it worked. What ROM are you currently running, that would be helpful in solving your sync issue.
DanWalker said:
I'm trying to update my recovery from 1.5.2 to 1.6.2 and can't seem to follow the directions appropriately.
Click to expand...
Click to collapse
Alright, lets begin - To upgrade to RA 1.6.2, (You have to be in recovery mode (Home + Power) -- and also have your phone connected to the PC). Then do as follows:
1. Download the 1.6.2 file
2. Copy or move it to your androidsdk\tools folder
3. Run commands below:
Code:
adb push recovery-RA-heroc-v1.6.2.img /sdcard
Code:
C:\AndroidSDK\tools>adb shell
Code:
mount -a
You'll probably get the next line below -- that's okay.
Code:
mount: mounting /dev/block/mmcblk0p2 on /system/sd failed: No such file or directory
Keep going...
Code:
flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2.img
After you do this, the shell should return #, if it does, then run:
Code:
reboot recovery
Now verify that your recovery says 1.6.2.
Good luck.
thatguythatdid said:
So since we're on the subject does anyone know how to set up the drivers for linux mint kde? I'm brand new to linux and I've managed to do some things but that is just one thing that i cant do so far and after almost a day pf searching this forum and others i just cant seem to get it
Click to expand...
Click to collapse
Well, since you've asked a good question, I shall direct you in the right direction. Linux Mint is a derivative of Ubuntu, so this guide should work for you., however do note that I have not tested this in Linux Mint, as I currently run Ubuntu 9.10, but you should be okay.
Go HERE and bookmark this page for reference, it has some good stuff -- Now this guide is not directly for our phones (CDMA HERO), however the directions, if followed correctly... DO WORK and have been tested by me (did this last night) with successful results.
When you get to the web page, start at "Generic Linux Instructions". Also, when you get to the heading "Set up ubuntu to recognize your phone, and the adb/fastboot commands in the terminal" -- step 4 will ask you to create an empty file, use the Ubuntu 9.10 format and NOT the older versions, again this format should work in the latest version of Linux Mint.
Hope that helps. Also, if have problems or want a step by step tutorial (pending how "new" to Linux you are), just ask me or PM me, I'll write one up.

[Q] N1 ADB & Fastboot for Ubuntu 10.04

I didn't really know where to put this question, but since it involves my Nexus One I put it here. I put Ubuntu 10.04 on a old Compaq V2000 laptop that I resurrected from the dead, and it's running beautifully. I spend more time on my Ubuntu machine then my new Toshiba/w/ W7. Anyway I need things working like I have on my Toshiba. I set up ADB after getting bits and pieces of information here and there, I just could never get fastboot to work for my N1, except when I'm in fastboot and I plug in my usb it changes from fastboot to fastboot usb, so it's recognized in fastboot, well sorta. But, when I run fastboot devices the terminal just hangs on >>waiting for device<<. Now I have another problem, adb works just fine, but yesterday I used it and where the number of your devices appears is blank now, no number shows up, but I can still run commands. I've done just about everything and I'm at a loss here. Some real help here, no snide remarks, and no [email protected], I need dev help or someone familiar with Ubuntu 10.04, or if you've had this problem lend some help. Once again I already have adb setup, but my number isn't showing anymore, and I need fastboot working, and yes I gave it executable permissions, I exported my path, I created my android rules, I edited my .bashrc file. Thanks much in advance. Long Live Linux!!!!!!
I'm good, found a executable script that solved my problem.
I think you just had to sudo adb. It's always polite to post what you did to fix a problem that way someone can search and find the answer, not just a question that says fixed.
Read Read Read!!!!!!!!!!
evilkorn said:
I think you just had to sudo adb. It's always polite to post what you did to fix a problem that way someone can search and find the answer, not just a question that says fixed.
Click to expand...
Click to collapse
I said in my post that I used a executable script, I mean thats all you should need to know. I read about it somewhere, that's all I needed to know, and I found it on my own. They have nuff post on how to setup your adb, but none are 100%, so you have to take bits and pieces from them, and kinda wing it from there. I don't sudo adb on my system, sudo adb =can't be found. It would be senseles to have to type sudo every time you wanted to run adb, I have my to autostart as root as soon as I run adb. If someone needed help all they have to do is ask. Since this post I've had to re-install ubuntu 3 times and I've gotten my adb & fastboot working with the same method I used the first time. I have my adb setup where I can push and pull from any directory, so I don't fill up my tools directory with too many files, and so I don't have to move files, I can just push & pull to & from anywhere.
Perhaps you can share the script you found?
Dude, chill out. The guides are fine and 100%. I don't need to know ****, I know how to setup adb. How the hell is someone going to find that script when you didn't link it.
First, you have to tell sudo where to look for adb, you obviously didn't link it init.d or some other way to tell the software what to do with adb. You have to do 'sudo /home/name/sdk/tools'.
google query: somewhere executable script ubuntu adb
rm -r -f /
Hope this helps
prettyboy85712 said:
Perhaps you can share the script you found?
Click to expand...
Click to collapse
Here's the links, the script isn't mine to give, and I think that would be against the rules. Go to the first link to get the installer, and the next one to get the fastboot exe. I would follow the instructions in the second link. Once you finish that, run the adb script, If nothing pops out of the script when it starts to run , run it again, or try running (in terminal) command. If you need detailed instructions PM me, it's a little process, you have to edit some files.
http://www.droidforums.net/forum/hacking-help/38186-linux-sdk-adb-autoinstaller-script.html
http://forum.xda-developers.com/showthread.php?t=537508
Good for you.

[Q] Dazed and Confused

So I'm trying to get a better understanding of the things I am reading here and on other Android websites. I keep reading about ADB - which I've gathered stands for Android Development Bridge. I did a search on this site and found the "easy ABD tutorial" that actually confused me even more. So my question is, could someone please explain to me in laymans terms what exactly is ABD? I've successfully rooted my D3 and created a nandroid and would l iike to try the Steel Droid Rom however, it talks about using ADB to push the BlurEmail.apk to system/app/.
I think I've successfully installed the Android SDK but I have no clue as to how to install the ABD "drivers" that are referenced in the the following post: http://www.xda-developers.com/android/adb-easy-tutorial/
Is there a difference between the SDK application and ADB or are they part of the same thing?
Is there a way to verify if I have the ADB drivers/application/whatever that I need so that I can push the BlurEmail.apk to the system/app/ file location?
As always, thanks to those that provide a response to this thread.

[TOOLS] Create unlock.img, fix boot.img, repack update.bin (for aboot

The attached archive includes 3 tools for those of you with .3.2.3.2 (or earlier) bootloaders.
Since other tools (and earlier version of these very tools) are available and working well,
this is mostly meant as an entry to an imaginary beauty contest. (JOKING!!!)
cuber.py
a generic gmpy2-free reimplementation of @vortox's signature.py
use this to generate your unlock.img
cuboot.py (uses cuber.py)
a Python-only reimplementation of @vortox's cuber
includes fixes to the kernel command-line and the device-tree
use this to convert a standard Amazon boot.img (>=.4.x.x)
upHDX (uses cuboot.py)
bash script to repack Amazon updates for TWRP
could be DANGEROUS, use with care
tested on Apollo for both 14.4.5.2 and 14.4.5.3
my unit is fully 14.4.5.3 now, except for aboot (which is 3.2.3.2)
should work on Thor as well
Those with bootloader .3.2.6 and lower can downgrade to .3.1.0
and upgrade the bootloader to the latest vulnerable version .3.2.3.2.
Those with .3.2.7 and higher appear to be out of luck with forged signatures, but I hear there's progress on rooting .4.5.2.
The python scripts have been tested on the following OS / Python combinations:
Windows: 2.7.9 and 3.4.3
Linux: 2.7.9 and 3.3.4
OSX: 2.6.? (cannot quite remember)
In addition to the tools themselves, I also included "educational" examples
(examples.sh for Linux/OSX, examples.bat for Windows).
These make use of the split.py script, which is otherwise unnecessary.
(The Windows example also shows that simply echoing your manfid/serial
combo to cuber.py -the way one does in Linux/OSX- won't work due to
the carriage-return character introduced by the echo command.
You'll need to handcraft a file matching the '0x%02x%08xn' format...)
Another batch file py..bat is meant as an extra aid for Windows users
to avoid trouble with setting paths and such. You should be able to simply
download and install your preferred Python version.
Open a command shell (cmd.exe), navigate to wherever you extracted the
archives, and type 'py PYTHON-SCRIPT ARGS' to run the Python scripts.
(This handholding intentionally does NOT work for the upHDX script.)
Hopefully, someone will find these simple tools useful.
EDIT: To unlock your bootloader (<=.3.2.3.2), you'll need adb and fastboot.
On Linux, most distributions package these separately. Look for android-tools-{adb,fastboot} or some such.
For Windows, you can get these from the official Android SDK (which is a **large** download,
with a lot more tools you won't need, if you don't already use them, but it's safe).
Alternatively, there's a very legit-looking project here an XDA, with a much smaller
download, fast install, and exactly the tools you need. I haven't used either... (-;
The actual unlock procedure is described here and here.
EDIT#2: I added another script 'cublock.py' to make unlock.img generation super easy both on Windows and Linux.
MD5( tools.zip) = c17fc91344bd3b4b040129a79a39741f
EDIT#3: Fixed issues with older versions of certain tools on Debian 7.
MD5( tools.zip) = 4f93ab667fd61db26c83675ce0bd6d9f
EDIT#4: Fixed a bug when 'cuber.py' is used directly from the command line.
MD5(tools.zip) = 67b4a6d65aa2b0aa3500b122c8a25290View attachment 3210856
XDA:DevDB Information
HDXtools, Tool/Utility for the Amazon Kindle Fire HDX 7" & 8.9"
Contributors
draxie
Version Information
Status: Alpha
Created 2015-03-13
Last Updated 2015-03-13
Thank for your works.
Can I use upHDX to remove bootloader, recovery from 4.5.3 and flash via TWRP?
Thanks
tuanda82 said:
Thank for your works.
Can I use upHDX to remove bootloader, recovery from 4.5.3 and flash via TWRP?
Thanks
Click to expand...
Click to collapse
Let's hope so. That's what I did, in any case.
I'm an adventurer; so, I ran './upHDX fw update-kindle-14.4.5.3_user_453011120.bin',
pushed the resulting update-kindle-14.4.5.3_user_453011120-upHDXfw.zip to my HDX 8.9
and installed it with TWRP.
Worked for me, but I cannot provide any guarantees, unfortunately.
It may be wise to omit 'fw', and doublecheck that you're happy with the contents of the
updater-script in the newly generated archive.
AND, -of course- make sure your bootloader version is at most .3.2.3.2!!!
draxie said:
Let's hope so. That's what I did, in any case.
I'm an adventurer; so, I ran './upHDX fw update-kindle-14.4.5.3_user_453011120.bin',
pushed the resulting update-kindle-14.4.5.3_user_453011120-upHDXfw.zip to my HDX 8.9
and installed it with TWRP.
Worked for me, but I cannot provide any guarantees, unfortunately.
It may be wise to omit 'fw', and doublecheck that you're happy with the contents of the
updater-script in the newly generated archive.
AND, -of course- make sure your bootloader version is at most .3.2.3.2!!!
Click to expand...
Click to collapse
Thanks. But your upHDX scripts is for linux user only. I am on Windows .
If you have time could you upload your xxxx_14.4.5.3_xxxx.zip? Thanks
draxie said:
The attached archive includes 3 tools for those of you with .3.2.3.2 (or earlier) bootloaders.
Since other tools (and earlier version of these very tools) are available and working well,
this is mostly meant as an entry to an imaginary beauty contest. (JOKING!!!)
cuber.py
a generic gmpy2-free reimplementation of @vortox's signature.py
use this to generate your unlock.img
cuboot.py (uses cuber.py)
a Python-only reimplementation of @vortox's cuber
includes fixes to the kernel command-line and the device-tree
use this to convert a standard Amazon boot.img (>=.4.x.x)
upHDX (uses cuboot.py)
bash script to repack Amazon updates for TWRP
could be DANGEROUS, use with care
tested on Apollo for both 14.4.5.2 and 14.4.5.3
my unit is fully 14.4.5.3 now, except for aboot (which is 3.2.3.2)
should work on Thor as well
Those with bootloader .3.2.6 and lower can downgrade to .3.1.0
and upgrade the bootloader to the latest vulnerable version .3.2.3.2.
Those with .3.2.7 and higher appear to be out of luck with forged signatures, but I hear there's progress on rooting .4.5.2.
The python scripts have been tested on the following OS / Python combinations:
Windows: 2.7.9 and 3.4.3
Linux: 2.7.9 and 3.3.4
OSX: 2.6.? (cannot quite remember)
In addition to the tools themselves, I also included "educational" examples
(examples.sh for Linux/OSX, examples.bat for Windows).
These make use of the split.py script, which is otherwise unnecessary.
(The Windows example also shows that simply echoing your manfid/serial
combo to cuber.py -the way one does in Linux/OSX- won't work due to
the carriage-return character introduced by the echo command.
You'll need to handcraft a file matching the '0x%02x%08x\n' format...)
Another batch file py..bat is meant as an extra aid for Windows users
to avoid trouble with setting paths and such. You should be able to simply
download and install your preferred Python version.
Open a command shell (cmd.exe), navigate to wherever you extracted the
archives, and type 'py PYTHON-SCRIPT ARGS' to run the Python scripts.
(This handholding intentionally does NOT work for the upHDX script.)
Hopefully, someone will find these simple tools useful.
EDIT: To unlock your bootloader (<=.3.2.3.2), you'll need adb and fastboot.
On Linux, most distributions package these separately. Look for android-tools-{adb,fastboot} or some such.
For Windows, you can get these from the official Android SDK (which is a **large** download,
with a lot more tools you won't need, if you don't already use them, but it's safe).
Alternatively, there's a very legit-looking project here an XDA, with a much smaller
download, fast install, and exactly the tools you need. I haven't used either... (-;
The actual unlock procedure is described here and here.
EDIT#2: I added another script 'cublock.py' to make unlock.img generation super easy both on Windows and Linux.
MD5( tools.zip) = c17fc91344bd3b4b040129a79a39741f
Click to expand...
Click to collapse
Thanks a lot for the good work but id like to let tell you that it will be great if you can explain all the entire work in layman's terms because there would be many people having hundreds of questions and concerns.
Just an advice if you feel worthy... No disrespect intended...
I would like it in layman terms...
And how to do it on Windows. This seems like confusion for me. I have no idea where to start.
I did it all in windows 8.1 64 bit edition.
With help from this post:
http://forum.xda-developers.com/showpost.php?p=58897784&postcount=67
get Python 2.7 for windows and install it >>https://www.python.org/download/releases/2.7/
btw I installed the 64 bit edition for both
get GMPY2 for Python 2.7 https://code.google.com/p/gmpy/downloads/list
Follow the post for step by step. I encountered some trouble with fast boot driver, I had to remove the driver and install a generic one I selected from windows then I manually installed it. Ran the fast boot command to unlock and I was unlocked. a lot easier than it looks.
Reckerr said:
I would like it in layman terms...
And how to do it on Windows. This seems like confusion for me. I have no idea where to start.
Click to expand...
Click to collapse
Appreciate it. Will attempt Saturday after a read through.
Works on Windows...
tuanda82 said:
Thanks. But your upHDX scripts is for linux user only. I am on Windows .
If you have time could you upload your xxxx_14.4.5.3_xxxx.zip? Thanks
Click to expand...
Click to collapse
Actually, I tested upHDX in Windows using Cygwin.
I had to select zip and unzip in the Archive group and python in the Python group
in the installer to get all the dependencies in place, and the only issue I faced was a few filename collisions
in the /system/media/audio/ringtones folder (case-sensitivity problem).
Code:
[COLOR="Lime"]>[/COLOR] diff -ru cygwin/ linux/
Only in linux/system/media/audio/ringtones: ANDROMEDA.ogg
Only in linux/system/media/audio/ringtones: CANISMAJOR.ogg
Only in linux/system/media/audio/ringtones: Hydra.ogg
Only in linux/system/media/audio/ringtones: PERSEUS.ogg
Only in linux/system/media/audio/ringtones: URSAMINOR.ogg
These could just be copied from the original update-*.bin after installation.
Reckerr said:
I would like it in layman terms...
And how to do it on Windows. This seems like confusion for me. I have no idea where to start.
Click to expand...
Click to collapse
If you could spell out what you mean by 'it', I might be able to help.
yujikaido79 said:
I did it all in windows 8.1 64 bit edition.
With help from this post:
http://forum.xda-developers.com/showpost.php?p=58897784&postcount=67
get Python 2.7 for windows and install it >>https://www.python.org/download/releases/2.7/
btw I installed the 64 bit edition for both
get GMPY2 for Python 2.7 https://code.google.com/p/gmpy/downloads/list
Follow the post for step by step. I encountered some trouble with fast boot driver, I had to remove the driver and install a generic one I selected from windows then I manually installed it. Ran the fast boot command to unlock and I was unlocked. a lot easier than it looks.
Click to expand...
Click to collapse
Of course, if you want to make it more difficult for yourself,
you can use the older version of my tool as well.
The new one is not limited to Python 2.7, but works on both current Python versions;
and does NOT require GMPY2.
Also, if you are looking to unlock your bootloader, the 'cublock.py' script is your friend.
You just pass in the manfid and serial (separately; no need to fuse them).
Whether you choose to install Python standalone or as part of Cygwin is up to you.
The latter also includes 'bash' and lets you convert the Amazon update to a TWRP-friendly ZIP.
draxie said:
Of course, if you want to make it more difficult for yourself, you can use the older version of ny tool as well.
The new one is not limited to Python 2.7, but works on both current Python versions; and does NOT require GMPY2.
Also, if you are looking to unlock your bootloader, the 'unlock.py' script is your friend.
You just pass in the manfid and serial (separately; no need to fuse them).
Whether you choose to install Python standalone or as part of Cygwin is up to you.
The latter also includes 'bash' and lets you convert the Amazon update to a TWRP-friendly ZIP.
Click to expand...
Click to collapse
I have Windows 7 and Nexus 2.0.5 with bootloader from http://forum.xda-developers.com/kin...p-flashable-3-2-3-bootloader-upgrade-t3025504 installed Python 2.7 and the adb and fastboot and driver package from post 1
Using
adb shell
cat /sys/block/mmcblk0/device/manfid
cat /sys/block/mmcblk0/device/serial
And unlock.py and then
adb reboot-bootloader
And
Fastboot -i 0x1949 devices
fastboot -i 0x1949 flash unlock <unlock file>
fastboot -i 0x1949 reboot
IT was very easy, I only had some driver problems in fastboot mode
Uphdx don't work on debian 7
Bruder Torgen said:
I have Windows 7 and Nexus 2.0.5 with bootloader from http://forum.xda-developers.com/kin...p-flashable-3-2-3-bootloader-upgrade-t3025504 installed Python 2.7 and the adb and fastboot and driver package from post 1
Using
adb shell
cat /sys/block/mmcblk0/device/manfid
cat /sys/block/mmcblk0/device/serial
And unlock.py and then
adb reboot-bootloader
And
Fastboot -i 0x1949 devices
fastboot -i 0x1949 flash unlock <unlock file>
fastboot -i 0x1949 reboot
IT was very easy, I only had some driver problems in fastboot mode
Click to expand...
Click to collapse
FYI - followed this process on an identical environment with identical results. Struggled a bit more with Windows drivers; if you're having trouble this might help (posts 8-10).
im running this version 13.3.0.2 and im a newbe with kindle what should I do
benyo8990 said:
im running this version 13.3.0.2 and im a newbe with kindle what should I do
Click to expand...
Click to collapse
Welcome to the HDX forums. How to proceed depends on what you want to accomplish. Read through the various threads to see what is available and the effort required. If your goal is to root and/or install custom roms you MUST disconnect from WiFi as Amazon will attempt to upgrade your tablet to the lastest Fire OS. Should that happen your options will be severely limited.
Two words of caution:
1) Kindles are not like other devices. Tough to tame and easy to brick. If you approach modding with a casual attitude you'll probably end up with a non-recoverable brick. READ, READ, READ before doing anything. Ask questions when you are ready.
2) There are no tidy fail-safe tutorials for the HDX. There is work and risk involved. You have to do your homework first. No one is going to hold your hand (sorry for the lecture - just trying to set expectations early).
More info please!
dpeddi said:
Uphdx don't work on debian 7
Click to expand...
Click to collapse
Given that it worked for me even in Cygwin on Windows 7, this sounds odd.
Nevertheless, I'd appreciate more info on how it fails (and which flavor of Debian 7
you are using; so, that I have a chance to reproduce your issue).
UPDATE: Nevermind. I fired up a VM with Debian 7.8.0-amd64-standard,
and found out for myself. Apparently, 'df' in 'coreutils 8.13' used here
doesn't support the '--output' option; AND, python 2.7.3 is more strict
about the input types to 'unpack'. I fixed these and the script worked.
I'll post the new version in a second.
DF --optional not supported, $m seems to not be set
Thank you for posting this awesome tool. I am running 13.4.5.2 with a twrp recovery and the most recent available (without breaking twrp) kernel.
My question is, if worst case scenario happens and I try to use cygwin to upHDX, it does not work, but I think it did, and I install a partially working update, am I bricked? Or, will it just write over my kernel and recovery with no hope of going back. As I type this, I am thinking the answer is, both are possible, but thought I would ask before breaking things.
Sent from my KFTHWI using Tapatalk
[Edit] If you know what you are doing, this script is very helpful. I especially enjoy how it explains everything it does as it does it. So, you can see the files it changes. I used cygwin and it worked perfectly. If you understand the Unix command tools, it is a piece of cake. I do not mean to belittle the risk involved, it is significant, however, if you read what is happening, and know this worked, and can be assured there is no issue with your recovery, you can still roll back if something goes wrong. Do not take this comment as minimal risk, the risk is substantial, and you need to wipe to go back. One of my devices did not take the update well (My fault), and, I had to go back. These devices do not handle wipes well. So, the moral of the story.
-This is an excellent and versatile tool,
-There is significant risk
-If you do your research, follow directions, and meet the requirements, you can get success. Have your cake and eat it too on your terms!!
-With this tool, I have the most recent update, root, and twrp (Amazon apps work too).
Thanks again for the tools.
[/Edit]
lekofraggle said:
My question is, if worst case scenario happens and I try to use cygwin to upHDX, it does not work, but I think it did, and I install a partially working update, am I bricked? Or, will it just write over my kernel and recovery with no hope of going back. As I type this, I am thinking the answer is, both are possible, but thought I would ask before breaking things.
Click to expand...
Click to collapse
I saw you managed fine, but just in case anybody else wonders,
the script will bail at the first sign of error and you'll know it.
Of course, this won't guarantee that things cannot go wrong,
but minimizes the chances that they go unnoticed.
NOTE, HOWEVER that:
This has only been tested on 4.5.2 and 4.5.3; and, I would strongly recommend against blindly running it on newer releases (as the pattern matching that's being relied upon for what to throw away --including the anti-rollback fuse stuff-- might easily get broken with relatively minor changes.
A good sanity check is to unzip both the original update and the newly created "sanitized" version, and compare them (e.g. via a recursive diff) to doublecheck if the changes are sensible.

Simple explanation to fix ADB unauthorized device in 'M'

QUESTION: Can someone please explain in simple form how to fix the ADB unauthorized issue that has been present since the update to M? The option for removing any current rsa keys is gone from the developer settings. And when you plug your phone in to a new computer it used to pop up a notification that would let you accept the rsa key. None of this is working any more. I cant believe that it is not a bigger issue and I have spent a few hours over a few days looking for a solution so if I have missed it, I am sorry. I have read a few things that say that google has just removed the ability to use adb and one post even explaining that, what looked to me to be a prop file variable, needed to be changed from 0 to 1, or vise versa, but didnt explain where the variable was. I dont see anything that I am confident with in the build.prop. Thanks. Please explain so that anyone will be able to overcome this issue, or point to a link.
Are you talking about the option to "Revoke USB debugging authorisations" under Developer options? It's there, at least on my N6 running stock 6.0.1 MMB29V... And I just tried to ADB to my device and the popup for the authorisation came up on the phone, just as it should.
I think you have some other problem going on.
Are you running the latest adb/fastboot tools on your PC?
Article showing removal of ADB
stevemw said:
Are you running the latest adb/fastboot tools on your PC?
Click to expand...
Click to collapse
Yes I am, I always use the one directly from the 'platform-tools' directory in the SDK. Another thing is I have read multiple articles that actually state that Google has removed the adb functionality in marshmallow... I don't get it. I even went from stock G.E. to CM an its exact same problem. Not to mention now I am dealing bwith the fact that the nethunter kernel isn't compatible with the CM build for Nexus... What!? Anyone can enlighten me on that subject I would love to know that as well... LoL. Here is link to one of the ADB articles though.
Tekto-kodi.com/kodi-news/marshmallow-android-6-removes-adb/
I looked at your link and the links provided in that article. The only thing I can read from those is that the ability to run ADB from your phone, i.e. from the terminal emulator (not your PC) has been removed. Are you trying to run ADB from your phone or your PC (I was under the impression that you're using your PC, but I have to ask)?
As I stated before, ADB from my PC to my N6 works just fine with Marshmallow (6.0.1 MMB29V).
You say that you use ADB directly from "platform-tools", but you don't say if you've updated the tools from the SDK-manager.

Categories

Resources