Database Develop

help installing apk using terminal

ok i just updated to CM 5. and well none of my apps are there, now im trying
this following :
sh /sdcard/installapk.sh /sdcard/theapp.apk
and no luck i think i can b doing it wrong.
cant DL the app cause i dont have the market app ether

Download DroidExplorer and you can do a bulk install of all your apps straight to the sdcard. Works everytime!!!
Link is in my sig

yea but i have no market on the phone and i dont have adb set up on my pc is it possible trew terminal to install astro so i can go on from there?

If your market is not there then you failed to flash the gapps.
You need to flash those AFTER CM5 or BEFORE. I've heard it works different for some people. First time I flashed it, it was before. Now it's after. Before and after won't hurt.

i figured that but the link on CM page for gapps is not working for me

I'm not really sure what having the market working has to do with anything. Clearly you didn't even take the time to click the link in my sig and go to the DroidExplorer thread.

it seems like that is for computers 64bit and up i have 32

brios86 said:
it seems like that is for computers 64bit and up i have 32
Click to expand...
Click to collapse
Are you talking about DroidExplorer? I have it installed on my 10 year old Dell and it is definitely a 32 bit machine. I'm assuming you are talking about something else.

You can use busybox if you have the latest CM ROM installed which you do. Busybox is included in the ROM so you can run busybox commands from terminal.
Put the apps you want to install on the root of your sdcard just to make them easy to find. Once in terminal, su so you have a # symbol
Then
Code:
busybox install /sdcard/yourapp.apk /sd-ext/app

great now i am F*** i tried installing the debug phone ota file that was required for CM 4.x and now i have no recovery it comes out the phone with exclamation mark

trying the droid explorer now

no luck droidexplorer seems to view the device but nothing else

brios86 said:
no luck droidexplorer seems to view the device but nothing else
Click to expand...
Click to collapse
Well that makes sense considering Droid Explorer requires root...According to your post on the first page, you are seeing an exclamation point when booting into recovery which means you lost root access by flashing whatever it is you flashed. Time to start all over again.
There is an updated rooting post for the Dream over at theunlockr.com

ok now my thing is i cant have the phone on cause it will keep getting FC and after a few it reboots

im trying to set up ADB on my pc now will that help me fix this? the phone boots up and the it reboots on its owne

It seems pretty clear that you don't really know what you are doing when it comes to modding your G1, and it is also pretty clear that you aren't willing to listen to directions.
I told you that you could batch install applications through Droid Explorer and you blatantly ignored my directions then said that it wouldn't work because you have a 32 bit computer.
I then gave you directions on how to use busybox to install the application that you wanted and never got a response regarding whether you even tried it or not.
You responded further into the thread saying that now you are getting an exclamation point when booting into recovery which MEANS THAT YOU DON"T HAVE ROOT ANYMORE!!!!!!!!!!!!!!!!!!
Installing adb and getting it working isn't going to do anything for you as far as installing applications because you lost root access which means you don't have the correct permissions to do anything anymore.
I gave you the link to an updated post on rooting so either do that or update this thread with where you stand exactly. Can you get into recovery? Is it an exclamation point? Can you launch the terminal app? When you type "su" do you get a # or an $? Does it say permission denied? ETC ETC ETC

DirectMatrix said:
It seems pretty clear that you don't really know what you are doing when it comes to modding your G1, and it is also pretty clear that you aren't willing to listen to directions.
I told you that you could batch install applications through Droid Explorer and you blatantly ignored my directions then said that it wouldn't work because you have a 32 bit computer.
I then gave you directions on how to use busybox to install the application that you wanted and never got a response regarding whether you even tried it or not.
You responded further into the thread saying that now you are getting an exclamation point when booting into recovery which MEANS THAT YOU DON"T HAVE ROOT ANYMORE!!!!!!!!!!!!!!!!!!
Installing adb and getting it working isn't going to do anything for you as far as installing applications because you lost root access which means you don't have the correct permissions to do anything anymore.
I gave you the link to an updated post on rooting so either do that or update this thread with where you stand exactly. Can you get into recovery? Is it an exclamation point? Can you launch the terminal app? When you type "su" do you get a # or an $? Does it say permission denied? ETC ETC ETC
Click to expand...
Click to collapse
My whole point with the no market is if he would have flashed the gapps or found another way to get them he could have installed a file manager then installed the app off his sdcard.
This was a 1 - 2 minute procedure that he has not made an hour/s procedure.
I agree with droidexplorer, I use it quite constantly. However, if he would have correctly installed CM5 this issue would have never arisen.
As for OP, I strongly advise that you unroot and stick to stock. If you cannot successfully do this, there is a high chance you are going to brick and it's just not worth it.

this is not the first time i try this i have a understanding of what i am doing, for some reason i decided to try another sdcard and it magically booted fine, now the gapps link doesn't work for me, so i am trying to install astro threw terminal emulator (astro is on the root of the sdcard) so i can just install the rest of my apps

thank you busybox worked thank you so much

funny after all the stuff i tried i decided to try a diff sdcard and it booted fine and then changed back to the old sdcard and it works fine

Lenovo Ideapad K1 One-Click Root (Mostly)

First, please forgive me if this is posted in the wrong section. It seemed most appropriate.
Second, I take no credit for anything here except for writing the .bat file here used to do the work, as well as assembling the files as per the original post.
All credit goes to djmwj and his article found here:
http://rootzwiki.com/topic/8722-lenovo-ideapad-k1-rooting-guide-messy/
As the title states, it was very messy. The OP figured out how to make it go, but it was a bit fuzzy to follow. So, I thought I'd help folks out a bit and clean things up.
So, I took the instructions presented in the OP, and condensed them into one download with one .bat that does everything from start to finish, minus installing the respective drivers for ADB and NVFlash. However, the drivers are included in the download.
Instructions:
1. Extract K1Root.rar to the directory of your choosing.
2. Connect your tablet to your PC with the USB cable.
3. With your tablet off, press POWER+VOL_UP+VOL_DOWN until the screen turns on, but displays only black.
4. Windows should detect the device, but not install drivers.
5. Go into device manager, select the APX device, choose update drivers, and install the drivers from the aptly named NVFlash_Drivers folder.
6. Open up the NVFLASH_HOME folder and run the file K1Flash.bat
7. Make your desired choices when prompted, and enjoy.
Notes (PLEASE READ BEFORE USING):
THERE MAY BE BUGS! I used it on my own stuff before releasing, and all of the essential components work as they should, however, there may possibly be a minor hiccup somewhere in the script. This should not damage anything. If you have doubts, you're welcome to examine the .bat and check it for yourself.
Please be gentle. I am not a full-time developer. I just wrote this to help make the process simpler for people.
The OP suggests you download and read the partition table, and then name the backup files based on that. This script names the backup files based on the flash.cfg script referenced in the OP, which is what controls the flashes used anyway. So, there shouldn't be any irregularities, however, I can't speak for every device on the planet.
This does NOT use the latest OTA updates. The rooted files being flashed are the default ones from the original download. You can easily adapt this to any files generated from the latest OTA files by simply dropping them in the NVFLASH_HOME file.
To install the SU properly, you have to install ADB drivers midway through the script. There's probably a way around this, but I didn't find it to be too inconvenient.
The ADB drivers are also located in the NVFLASH_HOME folder. Just do like you did when installing drivers in step #5, but instead point to NVFLASH_HOME.
Um...um...
That should be it. Obviously, use at your own risk. Let me know if there are problems with the script, and I will fix them.
Oh, and party on, Wayne.
http://www.megaupload.com/?d=AG10XE25
EDIT:
Attached is an updated .bat file which fixes a few errors in the original script, plus adds more userability. Just extract to the NVFLASH_HOME folder and run.

digitalhigh said:
First, please forgive me if this is posted in the wrong section. It seemed most appropriate.
Click to expand...
Click to collapse
You may want to change the title to Ideapad K1, I don't know if this will work for the Thinkpad tablet.
Thanks for this, I just picked up this tablet ($250 at staples) and was worrying about having to tackle linux and "compiling" just to be able to get hulu.com working. You're a lifesaver.

gallahad2000 said:
You may want to change the title to Ideapad K1, I don't know if this will work for the Thinkpad tablet.
Thanks for this, I just picked up this tablet ($250 at staples) and was worrying about having to tackle linux and "compiling" just to be able to get hulu.com working. You're a lifesaver.
Click to expand...
Click to collapse
Wow. Yeah, I'm pretty sure the key used is just for the Ideapad. Thanks for pointing that out. My dumb a$$ must've blanked out and just used the group name when posting.
And just to be fair, the original poster does include everything needed to do stuff in windows as well - it's just very hard to discern from the post.

question
Is anyone working on a custom ROM for this tablet? I am hopeing that there will be at least a few custom roms available at some point in the near future.

jfkerekes said:
Is anyone working on a custom ROM for this tablet? I am hopeing that there will be at least a few custom roms available at some point in the near future.
Click to expand...
Click to collapse
We need to be able to root and unlock the bootloader first.

Does the root method work on the 121211 update?
Or is there a way to flash back to the older firmware?

the OTA update 12 12 11.... seems to be update.zip style with no .img files inside. just loose files like normal rom updates. doesnt seeem like you can drop the files in as suggested. or i have the wrong OTA....
oh and is this for LINUX as the OP or work in windows too??

Hi, I was wondering, is this procedure works for the Lenovo ThinkPad 1838-25U? I'm thinking to buy it to give a test ride, i sold my Transformer 101 to buy the Prime but it seems like Asus is taking vacations on the delivery shipments. Is this a good tablet? or is better to wait for another version?

READ THE POST
IDEApad not THINKpad. no it wont work.

First of all- thank you so much for creating this script! I have been putting off rooting this device due to the "messy" nature of the original post.
I was hoping you could help me troubleshoot, I have tried both the new K1 root application and the original .bat file. I know the drivers are working because the script makes it as far as creating and formatting partitions and successfully pushes the bootlooder.bin but then:
bootloader.bin sent successfully
file not found: recovery.img
failed executing command 2147483647 NvError 0x4
command failure: create failed
I've tried everything I can think of... any ideas?
Thanks again.

I found problem.
after root done follow step. I cannot factory reset and update any ota.
anyone can help me ?

taiz said:
I found problem.
after root done follow step. I cannot factory reset and update any ota.
anyone can help me ?
Click to expand...
Click to collapse
Yes you have to roll-back to 04 stock and then apply the OTA's

Backup of the stock lenovo .apks!
File 1:http://www.mediafire.com/?r7iskr3wrfx4u01
File 2:http://www.mediafire.com/?fymdv9e9kmj332s
File 3:http://www.mediafire.com/?w33k205ej4fpbcl
A big thanks to Khanning who was nice enough to walk me through the adb commands and bear with me when I couldn't get adb over usb to work.

This may fix your issues http://forum.xda-developers.com/showpost.php?p=21309379&postcount=50

Can someone help I used this and I installed drivers from the drivers folder fine ....I ran option 1 fine and it said completed but said something about nvflash error make sure drivers are installed ....but on my tablet it said phone update success ....when I try option three to flash image it just stays at nvflash started and goes no further and when I try to install Su it won't connect adb , probably cause adb drivers wouldnt install ....any advice ....device is booting and seems stock ....it did not wipe my files either
Sent from my HTC EVO 3D X515a using XDA App

maek_it_happen said:
Can someone help I used this and I installed drivers from the drivers folder fine ....I ran option 1 fine and it said completed but said something about nvflash error make sure drivers are installed ....but on my tablet it said phone update success ....when I try option three to flash image it just stays at nvflash started and goes no further and when I try to install Su it won't connect adb , probably cause adb drivers wouldnt install ....any advice ....device is booting and seems stock ....it did not wipe my files either
Sent from my HTC EVO 3D X515a using XDA App
Click to expand...
Click to collapse
It means you are not in APX mode. Read the PDF and follow the instructions for installing the APX drivers. This should fix your issues.http://forum.xda-developers.com/show...9&postcount=50

I just completed step 3 flashing the image went fine up to bootloader .bin sent successfully ...then it says
File not found recovery.img
Failed executing command 2147473647 Nverror 0x4
Command failure : create failed
Edit the link u posted is not working and the drivers are installed
Edit 2 I just downloaded ur v2 root tool in ur other thread ....for some reason ur flash me Command actualy went past the recovery img error I was having with this tool .... But yours is flawless
Sent from my HTC EVO 3D X515a using XDA App

maek_it_happen said:
Edit 2 I just downloaded ur v2 root tool in ur other thread ....for some reason ur flash me Command actualy went past the recovery img error I was having with this tool .... But yours is flawless
Click to expand...
Click to collapse
Glad to hear it worked for you.
TD

I recently got this device and looking for a way to root this device without having to roll back to the factory default rom and then having to update again using OTA.
Question, am I in luck, is that at all possible or do I have to really rollback and reinstall everything again?
Thanks!
Sent from my K1 using Tapatalk

Anyone have the root? Megaupload is down forever.

Installing Xposed on the Android Emulator

I've done a fair amount of research and am still having trouble getting this installed on an emulated device. I have tried the base adt-sdk images for 4.1.2, 4.3 and 4.4.2 none of which I was able to attain the same "rooted" functionality as a phyical device. Most of the threads I read were a lot like this: http://forum.xda-developers.com/showthread.php?t=1731095
Xposed always gives me the following error: "Failed to get root access. Make sure your device is root properly and you have not blocked shell commands."
When I
Code:
adb shell
into the device I have [email protected], so I have access to root. The su binary is in both /system/bin and /system/xbin. I have also tried remounting the /system partition as rw, but nothing seems to help.
I'm not sold on any particualr version of android as long as it is >=4.1.2. I know some SELinux stuff came in at 4.3.
Any help you could offer would be great,
Thanks!

It worked flawlessly for me using Genymotion. I'm guessing you're using the normal Android emulator - apps won't get root on that directly and I'm not familiar with it.
You could, however, manually replace the necessary files. I'd recommend changing the installation mode to "Recovery" then checking the flashable ZIP's updater-script and basically replicate it from the shell (the updater-script is a shell script).

GermainZ said:
It worked flawlessly for me using Genymotion. I'm guessing you're using the normal Android emulator - apps won't get root on that directly and I'm not familiar with it.
You could, however, manually replace the necessary files. I'd recommend changing the installation mode to "Recovery" then checking the flashable ZIP's updater-script and basically replicate it from the shell (the updater-script is a shell script).
Click to expand...
Click to collapse
Where does it drop the script?

Blackdragon1400 said:
Where does it drop the script?
Click to expand...
Click to collapse
The script is inside the ZIP, which I think I saved to /sdcard/Android/data/de.robv.android.xposed.installer/ - check the output on your screen after pressing install, it should be noted there.

GermainZ said:
The script is inside the ZIP, which I think I saved to /sdcard/Android/data/de.robv.android.xposed.installer/ - check the output on your screen after pressing install, it should be noted there.
Click to expand...
Click to collapse
Alright, I will give it a try tomorrow, and post an update on the results. Thanks for the help!

Note that there are still a few minor things that are done via root, even when using the manual recovery installation mode. So the app needs to get root access.

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

How to root me572c Lollipop

First of all, many thanks for 4pda members.
It's time to post new thread for Lollipop.
This is for Kitkat me572c users.
(I can't make link so just copy the url)
● Lollipop firmware (UL-K007-WW-12.14.1.12) with root
Code:
mega.nz/#!LwJ3VBxK!4V4Ay-RzLS8x609zvyWL8IlcgI3xxfLcSqZ3gZkc52Q
● Install-Recovery.rar
Code:
mega.nz/#!C5ghzL6R!GR0WgLCumy6a429kB0ZjQOMxjPSylz07fVnHtKVm8ng
● ADB Driver
Code:
mega.nz/#!YAlxVbYS!7xfADRLuvcyO1GxRHtre3_e1TaVPmtIykqGbKCzUkkk
1) Can only be set on 4.4.2 (Kitkat). If you have already installed Lolipop, you must first revert to Kitkat. The computer should be installed ADB driver for the tablet and the tablet is turned on for the USB debugging. (no need to backup Internal memory. every data remain. but just in case, back up your data.)
2) Connect powered tablet to the computer. Download the firmware and rename it MOFD_SDUPDATE.zip, copy to the root of the memory card(MicroSd card) of the tablet. Download the archive Install-Recovery.rar and unpack it on your computer.
3) Run Install-Recovery.cmd, after the black command window turns up, volume buttons to select SD Download and power button for confirm. This will start the process of firmware.

Can anyone post instructions (in English hopefully because I'm lingual challenged) on how to revert back to KitKat if you've already upgraded to Lollipop? I didn't think that was possible...
Thanks so much!

I did a rough translation of the steps for downgrading in this thread. I haven't tried it myself, though, so I can't guarantee success.

It worked yes! Thanks! The only problem I have is my navbar icons is still kitkat, so is my wifi icon/battery. I'm just going to get the xposed module I guess and figure out later while it hasn't changed. But woo!
edit: (DOH!) that's what exposed moduel Xstana is for, nevermind the issue about navbar icons and the other icon problems.
You should include this in OP.
The link you posted for xposed lollipop in the other thread
"Xposed Installer for Lollipop
is.gd/jSVa1Q"

does this work on ME176CX??

redhk886 said:
does this work on ME176CX??
Click to expand...
Click to collapse
I wouldn't try it. The process involves loading ROM images made specifically for the ME572C..

A few questions about this.:
* Is there a way to do this in Linux? I don't own a Windows computer, but I have the full Android SDK installed, including ADB and fastboot.
* Is the Recovery.rar necessary if I am still on Kitkat? I assume this changes out the stock recovery with something else. Is that correct?
* Does this actually unlock the bootloader?
* My tablet is currently running 4.4.2. KVT49L.WW_epad-11.8.3.31-20150126 release-keys
044000309_201407240016. Any problems upgrading from this version?
Thanks
EDIT: Here is a very slightly modified script from the original for Linux. You must have adb and fastboot already installed for this work. These are included in the Android SDK for Linux. Copy and past this into a new file called Install-Recovery.sh and make it executable. You will still need the recovery.img file from the original Install-Recovery.rar archive. I don't think you will need anything else.
THIS IS UNTESTED!
Code:
#!/bin/bash
echo "Waiting for device connection..."
adb wait-for-device
adb reboot bootloader
fastboot flash recovery recovery.img

lexridge said:
A few questions about this.:
* Is there a way to do this in Linux? I don't own a Windows computer, but I have the full Android SDK installed, including ADB and fastboot.
* Is the Recovery.rar necessary if I am still on Kitkat? I assume this changes out the stock recovery with something else. Is that correct?
* Does this actually unlock the bootloader?
* My tablet is currently running 4.4.2. KVT49L.WW_epad-11.8.3.31-20150126 release-keys
044000309_201407240016. Any problems upgrading from this version?
Thanks
EDIT: Here is a very slightly modified script from the original for Linux. You must have adb and fastboot already installed for this work. These are included in the Android SDK for Linux. Copy and past this into a new file called Install-Recovery.sh and make it executable. You will still need the recovery.img file from the original Install-Recovery.rar archive. I don't think you will need anything else.
THIS IS UNTESTED!
Code:
#!/bin/bash
echo "Waiting for device connection..."
adb wait-for-device
adb reboot bootloader
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
I'm using linux tools comes with Intel Phone Flash Lite tool instead of google tools.
https://01.org/android-ia/downloads/intel-phone-flash-tool-lite
adb and fastboot are installed into /usr/lib/phoneflashtoollite/ and changed path for the tools are changed and done manually.
Now I've just succeeded to install LoliPop into my tab after almost 2 days efforts(thank all contributors!!) but I can't reproduce accurate steps in linux(ubuntu) environment.... At least I used windows environment for downgrading from non-rooted 5.01 to 4.4.2...
Good luck !

gmaxjp said:
I'm using linux tools comes with Intel Phone Flash Lite tool instead of google tools.
https://01.org/android-ia/downloads/intel-phone-flash-tool-lite
adb and fastboot are installed into /usr/lib/phoneflashtoollite/ and changed path for the tools are changed and done manually.
Now I've just succeeded to install LoliPop into my tab after almost 2 days efforts(thank all contributors!!) but I can't reproduce accurate steps in linux(ubuntu) environment.... At least I used windows environment for downgrading from non-rooted 5.01 to 4.4.2...
Good luck !
Click to expand...
Click to collapse
As I do not need to downgrade, I think my script will work. I just have not had the time to try it. When I do flash this, I will probably just type in the commands manually so I can what is happening easier. I would just really like to know more about this new Recovery before flashing. Is a CWM based recovery or a stock recovery? If stock, what differs in it from the stock recovery currently present on it?
I grabbed the link you sent, but it's a .deb file. I will search for a RPM or just convert this one, as I am using Fedora 21 and CentOS 7 on my two machines.
Thanks

lexridge said:
As I do not need to downgrade, I think my script will work. I just have not had the time to try it. When I do flash this, I will probably just type in the commands manually so I can what is happening easier. I would just really like to know more about this new Recovery before flashing. Is a CWM based recovery or a stock recovery? If stock, what differs in it from the stock recovery currently present on it?
I grabbed the link you sent, but it's a .deb file. I will search for a RPM or just convert this one, as I am using Fedora 21 and CentOS 7 on my two machines.
Thanks
Click to expand...
Click to collapse
Recovery is not CMW/TWRP, perhaps modified from stock.
Yep, What I did were execute series of command lines manually and crossing my fingers for several times
I'm expecting that will work in RPM based distros.

confirm, successful update using links/directions here.
kk stock rooted -> custom rooted 5.0 as above
yay!
significant speed increase in the ui animations, etc.
...google probably did a lot of support work for the moorefield

SacredMyths said:
It worked yes! Thanks! The only problem I have is my navbar icons is still kitkat, so is my wifi icon/battery. I'm just going to get the xposed module I guess and figure out later while it hasn't changed. But woo!
edit: (DOH!) that's what exposed moduel Xstana is for, nevermind the issue about navbar icons and the other icon problems.
You should include this in OP.
The link you posted for xposed lollipop in the other thread
"Xposed Installer for Lollipop
is.gd/jSVa1Q"
Click to expand...
Click to collapse
Thanks for Xposed info. I installed framework and installer from linux to tablet (by trying install command lines manually) and now they are working perfect. Eating pies with lollipop now, yummmm.

gmaxjp said:
Thanks for Xposed info. I installed framework and installer from linux to tablet (by trying install command lines manually) and now they are working perfect. Eating pies with lollipop now, yummmm.
Click to expand...
Click to collapse
Good , no problem.
Now the only issue I'm having is a few emojis are black D:

where can i download the xposed apk for this model...

javcarbe said:
where can i download the xposed apk for this model...
Click to expand...
Click to collapse
Xposed Installer for Lollipop http://is.gd/jSVa1Q Use latest rev.

Since is a zip
How can I install a zip if I don't have a twrp recovery
---------- Post added at 06:17 PM ---------- Previous post was at 05:47 PM ----------
i unzip run the bat but doesnt work i need an instructions to do it manually
C:\Temp\XposedForZenFoneLollipop_20150607>InstallXposedFramework.bat
'
'
' Connecting ZenFone ..
'
'
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
'
'
' Pushing files ..
'
'
error: device not found
error: device not found
'
'
' Installing Xposed Framework,
' please GRANT permission for this script on your phone !
'
'
error: device not found
error: device not found
error: device not found
'
'
' Done, rebooting ..
'
'
error: device not found

Instructions fail with the recovery not being able to mount the SDCard for some reason.
But the zip sideloaded just fine.
Thanks.
Also, any idea what recovery is compatible?

i tried with flash gordon but doesnt work.... also i tried to recovery and run the bat file and nope... no luck .... any ideas how can I do it, i create a zip file with the framework, the apk is easy to install my issue is with the framework.
Thanks,

javcarbe said:
i tried with flash gordon but doesnt work.... also i tried to recovery and run the bat file and nope... no luck .... any ideas how can I do it, i create a zip file with the framework, the apk is easy to install my issue is with the framework.
Thanks,
Click to expand...
Click to collapse
I guess you just have to turn on usb debugging, connect your device to your pc and execute InstallXposedFramework.bat and InstallXposedInstaller.bat

I did and nothing