Need Help Recompiling Kernel - HTC Vivid, Raider, Velocity

Howdy Folks,
I've been working on porting some ROMS to our device from the Sensation forum and I'm getting closer. I am currently using cygwin in Windows 7 64-bit so that I am able to use dxdia's kitchen. I have been able to successfully decompile both boot.img from the Base (U.S. Stock Vivid) and Port (Elegancia Pegasus) but when I need to recompile, I get the error "Compiling mkbootfs ... Error: mkbootfs not successfully compiled!"
I don't know how to proceed at this point in time. After I get the boot.img working, I'll need to start working on the AROMA script so you might not hear from me for a few weeks (due to work and school). I've been following the guide from http://forum.xda-developers.com/showthread.php?t=2245786. If anyone has experience with using dxdia's kitchen or has a different tool that I can use in Windows, that would be great. I want to keep the development for this phone going until a pick up the Nexus 5 (whenever that may be).
-Apatche

Related

[DEV] Ubuntu on Nexus S (natively)

Ok, so following on from the MeeGo thread, I have Ubuntu booting on the Nexus S using the same method and same kernel.
The Ubuntu image used is the HD2 Ubuntu image (v 0.3), loaded from a file on the internal memory (again, no flashing required - you can thank me later).
The touchscreen isn't yet working, but that's my kernel at fault. Will fix that with the MeeGo stuff.
If you want to try this yourself, first grab yourself a copy of Ubuntu for HD2, and take just the rootfs.ext2 file and drag it to your Nexus S (put it in a folder called 'ubuntu' - lowercase is important!).
Then use fastboot to boot the following image (or flash it to recovery partition if you're daring and know how dangerous that can be):
http://dl.dropbox.com/u/8657343/bootUbuntu.img
You will need to do one minor edit once the device is booted; you will see the screen output is very weird; ADB push the following file to /etc/X11/xorg.conf, and then reboot Ubuntu:
http://dl.dropbox.com/u/8657343/xorg.conf
If you're in any way interested, please click the thanks button! Otherwise, enjoy!
nice!
the next thing we'll need after getting the touch screen working
is to have a calling app daemon, and make sure internet works on both 3G and WiFi
nice, look same at Ubuntu Netbook Edition
What about Galaxy S?
Njcki said:
What about Galaxy S?
Click to expand...
Click to collapse
In theory the same stuff should work; I don't have a Galaxy S to test on or I'd try it. I don't know anything about the Galaxy S' bootloader, or how much the kernel would differ (I'm guessing not at all, since this is a stock Samsung kernel from the Android kernel source)
I did an article on my site http://www.android-ita.com/dev-port-di-ubuntu-sul-nexus-s/
Maybe some italian devs, will help you
Thanks for this, gonna have a play now
Why is it dangerous to flash the boot image to recovery? Isn't fastboot lower level than recovery, or have I got that wrong?
nice, thanks. trying this as soon as my wife gets off my phone.
Oh my god.. You are awesome good sir. Will give it a run when touch is up and running!
I'd love it to be run from Android....i dont want it natively, just to test it...booting for example from an android app
I would love to know if this will work on Epic 4G. I'm going to give it a shot to see what happens.
Great job
Could you give us the sources of your kernel ? Is it patched ?
Tyruiop said:
Great job
Could you give us the sources of your kernel ? Is it patched ?
Click to expand...
Click to collapse
There are no changes to the kernel at all so far. I changed the config file to enable VTs, that's it.
Ok, thank you, I'll try to build one myself
can this method be used to install android 2.3 on a phone running android 2.1,
especilly in the case when upgrading is difficult because of kernel and locked bootloader (like motorola devices) ? excuse me if it is a silly question, i'm not a coder.
would it be possible to make an app that re-boots into fastboot and runs the fastboot command. since we dont always have a comp available to run fasboot which makes this useless if your not at home, or have a laptop (in which case you dont need ubuntu on a phone)
works on Nexus One right now ?
--> ok I'm trying
It blocks on X screen of my nexus one.. before the classic bootanimation.zip
Someone have any idea about that ?
Ok, so I've got wifi working . Here is my solution. A little bit crappy but... hey... it's a start ! Also, I tried compiling the kernel with the module built in and it wont boot, and I don't know why ?
Howto get wifi :
1) Boot Ubuntu following stroughtonsmith indications
2) Download http://tyruiop.org/~tyruiop/wifi_nexuss_ubuntu.tar.bz2
3) push the vendor directory at the root. The path must remain (/vendor/firmware etc...) and the bcm4329.ko file wherever you want.
4) reboot under ubuntu
5) *optional, only if ifconfig -a doesn't show eth0* type insmod /path/to/bcm4329.ko
6) Type "ifconfig -a". An eth0 interface should appear. It's wireless. You can configure it with wpa_supplicant without a problem .
Uhm.. with Nexus One, Ubuntu blocks on X SCREEN (before the classic bootanimation).. Maybe something that I do is wrong ?
- Download HD2 Ubuntu
- mkdir ubuntu/
- put in ubuntu/ the fs on the archive I downloader
- put ubuntu/ in the SDCARD
- adb reboot bootloader
- fastboot boot bootUbuntu.img
Is it correct ?

[Q] ICS on a similar phone

Please forgive me for posting on your forum but I gave googled my problem with no success and the developers for ICS on the Hero have made progress with compiling ICS so I thought I'd ask my question here.
I have successfully compiled ICS 4.0.3 for the ARMv6 using the TeamICS patches here:
hxxps://github.com/TeamICS/ICS_Fixes
(sorry....can't post outside links yet!)
And other relevant pataches like:
hxxp://r.cyanogenmod.com/#change,10532
My phone is the Samsung Intercept with the S3C6410 processor similar to the processor in the Hero. The Intercept ROMs don't use .img files to flash the /system partition so I compiled ICS with: make -j4 otapackage to get a zip.
My dev box is Ubuntu 10.04 LTS and everything is installed EXACTLY like the AOSP website says it should be here:
hxxp://source.android.com/source/initializing.html
I flash the zip using CM recovery and boot and this error is killing me:
Warning PackageParser Exception reading AndroidManifest.xml in /system/framework/framework-res.apk
Warning PackageParser java.lang.SecurityException: /system/framework/framework-res.apk failed verification of META-INF/CERT.SF
Warning PackageParser Exception reading AndroidManifest.xml in /system/app/PicoTts.apk
Warning PackageParser java.lang.SecurityException: /system/app/PicoTts.apk failed verification of META-INF/CERT.SF
No apk will load because they fail verification. The list of failed APK's is long in logcat. I even went into the Java source code to hack out the verification code with no success. If any Devs have seen this or know why this is happening I would be grateful for a hint. Thanks.
UPDATE: I flashed the Hero ICS zip to my phone(with a few modifications to prevent a phone brick!) to see if the problem was with my compile or something else and I got the same errors. This must mean that there is something about the way Android checks APK signatures that I don't understand.
More information:
If I run jarsigner -verify -certs framework-res.apk I get "jar verified".
I have a theory about certs being bad at runtime:
In logcat there are entries saying that bouncycastle classes can't be preloaded and I'm guessing that bouncycastle has something to do with cryptographic keys so maybe PackageParser can't use the crypto classes and bombs.
jaybob413 would definitely be the guy to ask, or even mattcrystal. see if they have time to pm back and forth, and even post this in a dev/wip/rom thread in the intercept forums. exciting what these old phones can do, and i hope you go far with your port.
whoshotjr2006 said:
jaybob413 would definitely be the guy to ask, or even mattcrystal. see if they have time to pm back and forth, and even post this in a dev/wip/rom thread in the intercept forums. exciting what these old phones can do, and i hope you go far with your port.
Click to expand...
Click to collapse
Thanks for the tip...I have sent a message on github to mattcrystal so maybe he will respond if he has time.
bads3ctor said:
Please forgive me for posting on your forum but I gave googled my problem with no success and the developers for ICS on the Hero have made progress with compiling ICS so I thought I'd ask my question here.
I have successfully compiled ICS 4.0.3 for the ARMv6 using the TeamICS patches here:
hxxps://github.com/TeamICS/ICS_Fixes
(sorry....can't post outside links yet!)
And other relevant pataches like:
hxxp://r.cyanogenmod.com/#change,10532
My phone is the Samsung Intercept with the S3C6410 processor similar to the processor in the Hero. The Intercept ROMs don't use .img files to flash the /system partition so I compiled ICS with: make -j4 otapackage to get a zip.
My dev box is Ubuntu 10.04 LTS and everything is installed EXACTLY like the AOSP website says it should be here:
hxxp://source.android.com/source/initializing.html
I flash the zip using CM recovery and boot and this error is killing me:
Warning PackageParser Exception reading AndroidManifest.xml in /system/framework/framework-res.apk
Warning PackageParser java.lang.SecurityException: /system/framework/framework-res.apk failed verification of META-INF/CERT.SF
Warning PackageParser Exception reading AndroidManifest.xml in /system/app/PicoTts.apk
Warning PackageParser java.lang.SecurityException: /system/app/PicoTts.apk failed verification of META-INF/CERT.SF
No apk will load because they fail verification. The list of failed APK's is long in logcat. I even went into the Java source code to hack out the verification code with no success. If any Devs have seen this or know why this is happening I would be grateful for a hint. Thanks.
UPDATE: I flashed the Hero ICS zip to my phone(with a few modifications to prevent a phone brick!) to see if the problem was with my compile or something else and I got the same errors. This must mean that there is something about the way Android checks APK signatures that I don't understand.
More information:
If I run jarsigner -verify -certs framework-res.apk I get "jar verified".
I have a theory about certs being bad at runtime:
In logcat there are entries saying that bouncycastle classes can't be preloaded and I'm guessing that bouncycastle has something to do with cryptographic keys so maybe PackageParser can't use the crypto classes and bombs.
Click to expand...
Click to collapse
Sorry sir. I personally do not have enough time to look at your problem. I'm pretty busy with Zero Hero at the moment and ICS development is always on going.
When compiling from source the very last thing the complier does is run Google's signapk before finishing the zip. One reason I never got it to work was I was running 32 bit Ubuntu. Jaybob noticed I needed to be running 64 bit to properly compile and after that I'm able to flash my own builds from source. My guess is this is where you might be failing. ICS is a much bigger than gingerbread and tons of changes that are hard to overcome.
Sent from my HTC Zero Hero Sense 3.5
MattCrystal said:
Sorry sir. I personally do not have enough time to look at your problem. I'm pretty busy with Zero Hero at the moment and ICS development is always on going.
When compiling from source the very last thing the complier does is run Google's signapk before finishing the zip. One reason I never got it to work was I was running 32 bit Ubuntu. Jaybob noticed I needed to be running 64 bit to properly compile and after that I'm able to flash my own builds from source. My guess is this is where you might be failing. ICS is a much bigger than gingerbread and tons of changes that are hard to overcome.
Sent from my HTC Zero Hero Sense 3.5
Click to expand...
Click to collapse
Thanks for posting. ICS on the Samsung Intercept is up and running.
Do me a favor and click thanks perhaps and your welcome
Sent from my HTX Zero Hero Sense 3.5
no wip/dev thread on the intercept forums yet? that would be awesome, i a know a few with intercepts that would love to see ics on their phones. op you should think about making it happen, at least posting a guide/howto.

jelly bean root way over my head

just wanted to let all you developers know you kick ass..... i had a jb rooted ahd running batakang rom and loved it until it had an unfortunate meeting with the tire of my fullsize truck this morning....replacement from att store come with stock jb on it ....ive never used linux before and really dont think i can handle the root process for jb (especially after reading the posts from ppl alot smarter than me that were having problems.....looking forward to a simpler method like motofail....thanks again for all of your help and looking forward to making my ahd scream again
jaydheat said:
just wanted to let all you developers know you kick ass..... i had a jb rooted ahd running batakang rom and loved it until it had an unfortunate meeting with the tire of my fullsize truck this morning....replacement from att store come with stock jb on it ....ive never used linux before and really dont think i can handle the root process for jb (especially after reading the posts from ppl alot smarter than me that were having problems.....looking forward to a simpler method like motofail....thanks again for all of your help and looking forward to making my ahd scream again
Click to expand...
Click to collapse
It is a piece of cake trust me. Before I rooted my AHD I had never used Ubuntu or any form of Linux. I download Unbuntu and made the liveCD, and literally copied and pasted every command from the thread into the terminal in Ubuntu, then just followed the instructions on how to connect the phone. Worked first time, no issues. Just grab a cup of coffee, take your time, copy and paste and you will have root in no time,
brett_day said:
It is a piece of cake trust me. Before I rooted my AHD I had never used Ubuntu or any form of Linux. I download Unbuntu and made the liveCD, and literally copied and pasted every command from the thread into the terminal in Ubuntu, then just followed the instructions on how to connect the phone. Worked first time, no issues. Just grab a cup of coffee, take your time, copy and paste and you will have root in no time,
Click to expand...
Click to collapse
The hardest part is probably making the liveCD :laugh:
this is a one-click tool for the "hardest" part..
enjoy!
http://www.linuxliveusb.com/
jaydheat said:
just wanted to let all you developers know you kick ass..... i had a jb rooted ahd running batakang rom and loved it until it had an unfortunate meeting with the tire of my fullsize truck this morning....replacement from att store come with stock jb on it ....ive never used linux before and really dont think i can handle the root process for jb (especially after reading the posts from ppl alot smarter than me that were having problems.....looking forward to a simpler method like motofail....thanks again for all of your help and looking forward to making my ahd scream again
Click to expand...
Click to collapse
I rooted my AHD tonight and it was my first experience ever using Ubuntu. It took me a while to figure it out, but once I got started it was a cake walk. Like someone else said, the hardest part is probably making the LiveCd/usb. I'm not sure why, but I couldn't ever get Ubuntu to work properly in VirtualBox so I ended up just booting my LiveUSB and opening the instructions on my tablet and doing it. It's super easy. Just do exactly what it says.
Oh, and it took me a little while to figure out just how to open a terminal in Ubuntu (ctrl+alt+T). If you're as much of a noob with this as I am knowing how to open a terminal will save you some time right from the get-go.
Good luck!
Google is your friend
any help?
ok so I ran Ubuntu and i cannot get my AHD to connect to the remote server i have entered everything as the instructions said all i get is an error that says that i need to repair my network is there a way to fix this?I really want my root back guys any help ?
EDIT:I have fix this by restarting my router excuse my my questions
very sorry
jelly bean root issues
hey guys just a few questions trying to root my ahd....im using ubuntu 12.04lts live cd
just a few issues
first
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
samba : Depends: samba-common (= 2:3.6.3-2ubuntu2) but 2:3.6.3-2ubuntu2.3 is to be installed
Depends: libwbclient0 (= 2:3.6.3-2ubuntu2) but 2:3.6.3-2ubuntu2.3 is to be installed
Recommends: tdb-tools but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
[email protected]:~$ sudo gedit /etc/samba/smb.conf
this is what i get when i install samba
also when i try to restart it says
[email protected]:~$ sudo restart smbd
restart: Unknown job: smbd
also prolly a stupid question but when i try to do the file manager it says cannot connect to remote host,
ive tried resetting my router and restarting both my phone and computer and nothing works...help
:
So yeah...
I was wondering, if any "recent" version of Ubuntu would work for the root...
Main reason for asking this was because I had a Live USB With 10.04
That and the PC i'm stuck with ATM just can't seem to handle 12.04...
[EDIT]
Never mind, I'm getting Lubuntu...
[EDIT]
I keep getting this error when trying to install samba in my lubuntu (persistent) usb...
Personally, I find these errors to be very annoying, as all I want to do is root my phone...
So, at the moment, I can't install Samba, can't "sudo gedit..."
[email protected]:~$ sudo apt-get install samba
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
samba : Depends: samba-common (= 2:3.6.6-3ubuntu1) but 2:3.6.6-3ubuntu5 is to be installed
Depends: libwbclient0 (= 2:3.6.6-3ubuntu1) but 2:3.6.6-3ubuntu5 is to be installed
E: Unable to correct problems, you have held broken packages.
[email protected]:~$
i got it...
thanks for all your help, you guys roick finally rooted on stock jelly bean btw used ubuntu 12.10 on usb worked great first time no problems
Lubuntu Variant
I noticed for Lubuntu, its a slight variant as opposed to the basic Ubuntu instructions...
Instead of gedit, you can substitute leafpad instead...
"sudo leafpad /etc/samba/smb.conf"
Oh and I think I solved my earlier problem after installing the "sessioninstaller" from the Synaptic Package Manager... (Use the search function.)
My only issue ATM is when I'm in the terminal and I try and use "sudo restart smbd" and it doesn't seem to work.
It merely tells me smbd isn't a process...

BootTools Native Compile

I have been trying to get these BootTools from github cross compiled for android for around 2 weeks without success, they build but when I unpack and repack my boot.img and then cat it to the block, it hangs at the boot screen and then reboots into recovery, when I repeat the same process on my desktop with the perl scripts it works perfect so I come here to ask for help on getting these tools cross compiled to run natively on android in a manner that works, thanks Mark.
Sent from my GT-I9305 using xda premium

[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.

Categories

Resources