Related
Hi all I am putting together an android app that will making the rooting process much easier. This thread is discuss issues and suggestions with this app.
I have the app near done, the biggest problem is that I cannot format the sdcard as fat32. Is formatting to fat32 required. Why do we do this? What is the real need to do this?
I have not tested the app out yet, but so far this is how it has been put together. There is a main activity with textboxes that have the urls of the files needed to root (dreaimg.nbh, recovery.img, hardsplupdate.zip, JF_RC33update.zip) and there are buttons for each step in the process to download these necessary files and extract them if needed and put them on the sdcard and renaming them properly. You can change the urls to something else if needed.
so you click the first button it downloads the .nbh and puts it on the sdcard and then prompts the user to turn off, power+camera on, flash. when phone is on then reinstall this app and go to step 2 (because it would of been lost when flashed)
you click the second button it downloads recovery.img and hardsplupdate.zip. renames the files appropriately and puts them on the sd. it runs a script to do the recovery.img flash. It then prompts you to restart into recovery mode and gives the instructions on flashing the hardspl. and tells you to reopen this app when done
you click the third button it downloads the latest JF firmware (lets just say the RC33 flavor) puts it on the sdcard and renames it as update.zip. it prompts you to restart into recovery mode and do the flash.
Anybody see any possible problems with this logic? Also what do people think about maybe packing some of these files in the app instead of having them be downloaded?
Update: app is working http://allshadow.com/forum/viewtopic.php?f=9&t=5229
I am still looking for help to make it better.
I need devs to help make it nicer.
I am also looking for someone who's familiar with the update.zip package, to pack the radio, hardspl, and jf_rc33 all in one update file.
If anybody is interested in helping, PM me
I dont think its that big of a deal to format the card yourself, but why not make an app on the desktop that does some of the work for you, like formatting the card, then downloading and renaming the files needed to get started?
Packing the files into the app is going to make the app big. I like this whole idea though.
when you flash the .nbh it does a wipe on its own so one would need to re-download the app after that unless you can get it to stick somehow, i like the idea, is each button of the app just running a script? like to get the dreaimg.nbh have a script that runs:
"$wget [url to the .nbh file]
$echo 'please reboot your phone into SPL by holding the camera and power button'"
or did you have some other idea?
i like the idea but i am just not sure how easy this would be to code as i am just used to writing scripts that do everything for me.
or you could follow Kllian's advice and make a desktop program that does all this. i could easily write a script for linux that would do it, and a .bat file wouldn't be too hard either. you would just need to have adb and you could have the scipt/batch reboot the phone into recovery to do the flashing of each update.zip
pm me if you have an questions or would like me to write a script to do all this
tubaking182 said:
when you flash the .nbh it does a wipe on its own so one would need to re-download the app after that unless you can get it to stick somehow, i like the idea, is each button of the app just running a script?
Click to expand...
Click to collapse
tubaking brings up a good point.
I have an idea that possibly could resolve the "wiping" issue. What you do is, the initial app would be placed on the desktop (assume RC30). From here you'd downgrade the firmware to RC29.
The problem is though, the app you are scripting will be wiped. SO...
How about saving it on the SD temporarily.
THEN modifying the .nbh file to restore the <rooting app> to desktop (from SD)
Just throwing some stuff out there.
IF you need some help, hit me up.
if anyone knows how to convert a .sh bash script from linux to a .bat batch file for windows then i already have the script written, send me a PM to get it. or we could port it into java, but i don't know how to do that stuff. tomorrow i will upload my script onto 4shared and provide a link here as long as it works. keep in mind that i am on a linux machine and my script will not work in M$ windows. i don't know a damn thing about mac, so i have no idea if this will work or not for them.
my script is nearly completely automated, the only thing you need to do is hit ENTER a few dozen times, i will also write a completely automated one that sleeps rather than waits for you to hit enter, but it will take longer to run most likely since i will have to oversetimate the sleep time.
hopefully i can find a windows machine and learn what commands in the cmd are equal to the commands in my terminal
akapoor said:
tubaking brings up a good point.
I have an idea that possibly could resolve the "wiping" issue. What you do is, the initial app would be placed on the desktop (assume RC30). From here you'd downgrade the firmware to RC29.
The problem is though, the app you are scripting will be wiped. SO...
How about saving it on the SD temporarily.
THEN modifying the .nbh file to restore the <rooting app> to desktop (from SD)
Just throwing some stuff out there.
IF you need some help, hit me up.
Click to expand...
Click to collapse
modifying ,nbh files is no easy task, i tried it once and fortunately for many people GSLeon3 was able to help me fix my tilt. i think the .bat or .sh would be the easiest way to root your phone
Tubaking,
Send over the file you have. Ill work on converting it to a .bat, useable from windows.
Email : akapoor92_at_gmail.com
I should have it soon, but since its like 3:30am here, I'm off to bed. Haha
tubaking182 said:
modifying ,nbh files is no easy task, i tried it once and fortunately for many people GSLeon3 was able to help me fix my tilt. i think the .bat or .sh would be the easiest way to root your phone
Click to expand...
Click to collapse
Uh, you'd not only need to modify the nbh file, but you'd also need to sign it with the Google OTA keys - otherwise the phone will refuse to flash it.
If it were possible to create Google-signed nbh files we'd dispense with all this downgrading nonsense and just create an nbh of the latest JF firmware with root and directly flash that.
The issue is that until you've patched the recovery loader the phone won't flash anything that isn't signed by Google. The reason we can get around this is that there is a leaked signed file with the old firmware version, and that version happens to contain a vulnerability that you can use to get root access. Once you have root access you can reflash the recovery loader with a new one which accepts the test keys. At that point you can dispense with the hacks and begin directly flashing whatever you want.
In any case, rooting a phone is serious enough of a matter that we probably shouldn't be encouraging anybody who can download an app to do it. They should at least have some confidence in reading and following obscure instructions online, because of anything goes wrong later that is what they'll be doing...
Thanks for all your input. I have been trying to hold hand people through the root process and it is a real pain. Biggest issues are people not being able to unzip files correctly, rename files correctly, and the biggest thing is the recovery.img step and typing in the commands.
- .nbh cannot be patched because it is signed.
- yes my app will get wiped because of the .nbh flash. It does tell the user to reinstall this app once done with the .nbh step and then continue
- i prefer an android app, so people can do it without a computer and without having to install the sdk
- the app does not run a script to get the files. it uses some android sdk functions to download files. it does use the unzip linux command to unzip, not sure if this will work because of permissions, i may have to figure out how to do it from the sdk. the app does run a script to do the recovery.img step, during this step we should already have root so no issue there with permissions.
Biggest problem I see is Fat32 format I heard it is not absolutely necessary. Does anyone have any more information about why this needs to be done?
it IS necessary, you need the card formatted in order to do the NBH flash, after that you should be ok. most card come formatted in the box they came in so anyone that said they didn't need to format their card is lying because is was already formatted to fat 32
in the RC29 firmware is there a su command in /system/bin/ or are all commands run as root without having to call /system/bin/su ??
moussam said:
in the RC29 firmware is there a su command in /system/bin/ or are all commands run as root without having to call /system/bin/su ??
Click to expand...
Click to collapse
from what i've read, in the RC29 version andything you type on the home screen gets put through a root shell as well all on it's own
I have a feeling whoever makes this app is going to sell iot for a ridiculous price on the market
My script is written but requires the user to do certain things, later I hope to have it be completely automated after a certain point and it will be free. After I get it written in linux shell I will be converting it to use in windows. Expect my automated root to be available for download by the weekend.
I got the app pretty close to done. I hope to put something up tonight or tomorrow that you guys can test. I am not going to charge for this app, I want to give it for free so everybody can have root and a more rich experience.
The place were I am stuck right now is the unzipping of the DREAIMG.NBH file from its zip file after it is downloaded. I am using java.util.zip I am not sure if the problem is because the file is so big or if I am doing it wrong. does anyone have an android java unzip code snippet?
The app now downloads files for you and unzips them if needed. THere is an issue with the unzipping though, after around 25 MB of unzipping DREAIMG.NBH i get this error...
java.io.IOException at java.util.zip.InflaterInputStream.read(InflaterInputStream.java)
anybody have any suggestions? Is their not enough memory to unzip the files or something?
For now I am not going to let the .nbh file be zipped up. THe app instead will have to download the full uncompressed .nbh file.
So it is ready to be tested, if you want to try it out PM me, I do not want to just post it and have everybody use it until it has been tested more.
Good news the app works on downloading the .nbh file and then flashing you to RC29. It then successfully downloads the recovery.img and hardspl update.zip
I had someone testing it and when they ran the recovery script the mount command gave them mount: operation not permitted. Is this correct? I know without root it is supposed to give you mount: permission denied.
If this is correct the app is working, and I just need someone else to confirm.
Mike
Does anybody else want to help with the coding of this project? If so create an open-source repository and I will add the current source in there.
This has been resolved by using the flash lite exploit to gain root access allowing the misc partition to be flashed with a downgraded main version number which allows the old leaked Eng RUU we have to be flashed!
GUI for how to root
http://forum.xda-developers.com/showthread.php?t=720565
Old and Outdated information from the Original Post listed below for historical purposes ONLY
Who is Affected: If you've flashed the official OTA update on top of a non rooted ROM or your new EVO comes loaded with it, right now it appears there is no way to obtain root...yet!
What is Patched by the OTA: Through the radio.img which the OTA flashes, it updates the Main Version in the bootloader preventing Toast's root methods from working. It also flashes back the stock recovery, removing our root access in recovery mode and ability to apply .zip files. And last of all, the OTA patches the exploit hole in /system/bin/hstools used for unrevoked1 root.
Successfully eliminating all released methods of obtaining root access.
Conclusion:
after going through all these methods with a great helpful member of the unrevoked team, joshua_, this was the final answer:
[22:34] <joeykrim> cant see to find a method to RUU the phone back down ... ive tried all the methods ive seen. any methods i missed?
[22:34] <joshua_> ok, looks like we are hosed then
[22:34] <joshua_> we have a few more tricks up our sleeve sooner or later
Future:
If you have any suggestions/ideas, please post. I might have missed a method.
We will work towards obtaining root for those with new EVOs that have the official OTA applied and those who applied the official OTA.
Details of the tested known root methods:
user debug PC36IMG.zip (toast part 1) - bootloader error - Main Version is older! Update Fail! Do you want to reboot device?
eng build PC36IMG.zip (toast part 2) - bootloader error - Main Version is older! Update Fail! Do you want to reboot device?
RUU_Supersonic_1.32.651.6 extracted rom.zip renamed to PC36IMG.zip - bootloader error - main version is older
RUU_Supersonic_1.32.651.6_Radio_1.39.00.05.31_release_171253_signed.exe - Error [140]: Bootloader version error The ROM Update Utility cannot update your Android. Please get the correct ROM Update Utility and try again.
RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_release_171253.exe - Error [140]: Bootloader version error The ROM Update Utility cannot update your Android. Please get the correct ROM Update Utility and try again.
Stock Recovery - Apply update.zip - clockwork recovery update.zip - E:failed to verify whole-file signature E:signature verification failed
flash_image (flash boot or mtd-eng.img) - copied to /sdcard, but sdcard is mounted with noexec. partition with write access for non-root user and allows executing is /data/local . flash_image can't write to the partitions w/o being run with root permissions. chownto and chown of flash_image to user root - permission denied.
##786# - Reset - doesn't seem to effect much in the way of bootloader version ...
Modifying PC36IMG.zip - using a hex editor to attempt at changing the MainVer stored in the android-info.txt, if any bit changes, it seems to fail the validation by the bootloader.
I tried almost all of these after the OTA hit my wifes phone. No dice. Subscribed to further updates on this thread.
I created a PC36IMG.zip file which contained the .6 releases wimax image and the android-info.txt file from the new update. I was then able to successfully flash it with hboot by placing it in the root of the sdcard and doing a down volume power on boot. It found the pc36img.zip file, verified it, asked me if I wanted to flash it. When I selected yes, proceeded to do so. It then reported the flash as having been successful.
I can't tell if the flash actually worked because I don't know where to check the wimax version info...
I don't know if this worked because the phone doesn't care to check the MainVer when flashing just the wimax image or if it did it because I pulled a fast one with the android-info.txt file swap.
I extracted the wimax image from the RUU_Supersonic_1.32.651.6_Radio_1.39.00.05.31_release_171253_signed.exe file.
I wonder if it would be possible to pull the same trick with the larger subset of images from the rooting pc36img.zip files. i.e. swap out the android-info.txt files...
frankenstein\ said:
I created a PC36IMG.zip file which contained the .6 releases wimax image and the android-info.txt file from the new update. I was then able to successfully flash it with hboot by placing it in the root of the sdcard and doing a down volume power on boot. It found the pc36img.zip file, verified it, asked me if I wanted to flash it. When I selected yes, proceeded to do so. It then reported the flash as having been successful.
I can't tell if the flash actually worked because I don't know where to check the wimax version info...
I don't know if this worked because the phone doesn't care to check the MainVer when flashing just the wimax image or if it did it because I pulled a fast one with the android-info.txt file swap.
I extracted the wimax image from the RUU_Supersonic_1.32.651.6_Radio_1.39.00.05.31_release_171253_signed.exe file.
I wonder if it would be possible to pull the same trick with the larger subset of images from the rooting pc36img.zip files. i.e. swap out the android-info.txt files...
Click to expand...
Click to collapse
im guessing the only reason it allowed you to flash a PC36IMG.zip which wasn't HTC signed is because you're using the hboot from the eng build of the PC36IMG.zip which doesn't check for HTC signatures on the PC36IMG.zip file. Not sure if it looks at the MainVer or not ...
once you're on a stock hboot, the PC36IMG.zip file has to be signed by HTC in order to flash!
I think in order for this to be patched, the bootloader code needs to be disassembled between the two versions to find out what bytes were patched and then either remove the code that checks for HTC signing or find a way to circumvent it.
We had to do things like this when working with mach_kernel when we got ahold of the first developer build of OS X for Intel. It was a pain in the ass and took weeks before we cracked the kernel.
There is even more risk with this though since tampering with the bootloader can definitely permanently brick devices.
joeykrim said:
If you've flashed the official OTA update or your new EVO comes loaded with it, right now it appears there is no way to obtain root...yet!
after going through all these methods with a great helpful member of the unrevoked team, joshua_, this was the final answer:
[22:34] <joeykrim> cant see to find a method to RUU the phone back down ... ive tried all the methods ive seen. any methods i missed?
[22:34] <joshua_> ok, looks like we are hosed then
[22:34] <joshua_> we have a few more tricks up our sleeve sooner or later
If you have any suggestions/ideas, please post. I might have missed a method.
We will work towards obtaining root for those with new EVOs that have the official OTA applied and those who applied the official OTA.
Here are details of the tested methods:
user debug PC36IMG.zip (toast part 1) - bootloader error - Main Version is older! Update Fail! Do you want to reboot device?
eng build PC36IMG.zip (toast part 2) - bootloader error - Main Version is older! Update Fail! Do you want to reboot device?
RUU_Supersonic_1.32.651.6 extracted rom.zip renamed to PC36IMG.zip - bootlaoder error - main version is older
RUU_Supersonic_1.32.651.6_Radio_1.39.00.05.31_release_171253_signed.exe - Error [140]: Bootloader version error The ROM Update Utility cannot update your Android. Please get the correct ROM Update Utility and try again.
RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_release_171253.exe- Error [140]: Bootloader version error The ROM Update Utility cannot update your Android. Please get the correct ROM Update Utility and try again.
Stock Recovery - Apply update.zip - clockwork recovery update.zip - E:failed to verify whole-file signature E:signature verification failed
flash_image (flash boot or mtd-eng.img) - copied to /sdcard, but sdcard is mounted with noexec. only partition with write access for non-root user and allows executing is /sqlite_stmt_journals . flash_image can't write to the partitions w/o being run with root permissions. another words, need root access to use flash_image
##786# - Reset - doesn't seem to effect much in the way of bootloader version ...
Click to expand...
Click to collapse
since my frien did the OTA update yesterday and "bricked" his phone i have been trying to fix the phone (i have access to bootloader so it seems to me that maybe, just maybe i can save the phone) anyways, i have been getting a lot of the same error messages anytime i try to update/load any stock rom via bootloader.
what my question is, is there a way to take a 1.47.651.1 rom/image and put it into an ruu? i have looked all over htc's website, but they don't even acknowlege the existence of the evo, at least not that i can find.
joeykrim said:
flash_image (flash boot or mtd-eng.img) - copied to /sdcard, but sdcard is mounted with noexec. only partition with write access for non-root user and allows executing is /sqlite_stmt_journals . flash_image can't write to the partitions w/o being run with root permissions. another words, need root access to use flash_image
...
Click to expand...
Click to collapse
Just curious here, regarding the above step, if you had access to a phone that was already rooted, could you use your sdcard in that phone to copy the files into /data and then transfer the sdcard back to the unrooted phone to flash it then?
Sorry for the long multi quote, there are quite a few good ideas and I wanted to make sure I explored each of them as far as the original poster intended.
EtherealRemnant said:
I think in order for this to be patched, the bootloader code needs to be disassembled between the two versions to find out what bytes were patched and then either remove the code that checks for HTC signing or find a way to circumvent it.
Click to expand...
Click to collapse
interesting ... circumventing the HTC signature check would be perfect and essentially give us an eng build bootloader.
in the RUU.exe rom.zip files, the android-info.txt indicate the MainVer along with a separate hboot.img file. the official OTA didn't have an hboot.img file. It only had a radio.img file which must have updated the MainVer value.
Not sure where on the phone this MainVer value is stored? in the radio?
you're suggesting, compare the bootloader, which is obviously stored somewhere in radio.img as thats the only file being flashed thru the OTA which increments the bootloader version number, against an older radio.img to attempt and find which bytes were changed for the version number?
The radio.img files are all around 22mbs ... ugh
if we're able to find the change in version number on the radio.img, not sure how it would help in flashing over it?
i was kind of thinking down these lines...since the bootloader checks the version number of any file it attempts to flash, the version number is going to be the key.
if we're able to increment (or temp change) the main version number in the file being flashed w/o messing up the htc signature, that could work.
2002wrex said:
what my question is, is there a way to take a 1.47.651.1 rom/image and put it into an ruu?
Click to expand...
Click to collapse
i've heard this was often done back in the WinMo days but i haven't seen anything on this board regarding this approach. if you have any detailed information, we could def look into it!
unknown_owner said:
Just curious here, regarding the above step, if you had access to a phone that was already rooted, could you use your sdcard in that phone to copy the files into /data and then transfer the sdcard back to the unrooted phone to flash it then?
Click to expand...
Click to collapse
very clever concept!
i'm not 100% sure on all the different approaches in the suggestion, but here are the ones it prompted me to explore.
unfortunately, every time the /sdcard is mounted on the phone, its mounted as noexec, meaning no files located on the /sdcard can be executed like programs.
also the /sdcard is mounted with uid=1000 and gid=1015 meaning all files mounted on the /sdcard have their uid/gid overwrote so none of them are allowed root ownership.
without being able to "su" to root access, we aren't able to run any programs with root access.
trying to chownto flash_image to any reference file as root results in:
chownto flash_image /system/bin/chown
Can't change user/group to root!
chown root flash_image
Unable to chmod flash_image: Operation not permitted
if i missed the suggested approach, could you elaborate?
Oh boy...... I thought I was alone in this. I try everything I can and now gave up. Any one can rooted this new OTA please let me know. I really need to downgrade from this.
Made me think of a problem that happened with the Directivo a few years back...
ht t p://dealdatabase.com/forum/showthread.php?t=22154
I was looking around, trying to figure out some way to hack the hdvr2 w/o modifying the prom. I recalled something from the xbox-linux team's presentation for CCC, which was something close to "once you break the chain of trust, the box is forever compromised." I thought to myself: "self, if we can load one kernel via BASH_ENV, why can't we load a second kernel?"
Click to expand...
Click to collapse
So, is there a way we could compromise the kernel? If so, then...
Subscribed...
Not really interested in rooting until froyo is working, and I could really use the wifi fixes this OTA is supposed to offer, but I'll hold off installing it until we know it can eventually be rooted.
Mikesus said:
http://dealdatabase.com/forum/showthread.php?t=22154
So, is there a way we could compromise the kernel? If so, then...
Click to expand...
Click to collapse
i read thru the thread. im not clear on how they used BASH_ENV or any other method to load a 2nd kernel.
unfortunately, i think we have an extra layer of security that they dont. thanks HTC!
without nand unlocked on the kernel partition no data can be stored there including a 2nd kernel.
appreciate the link and info. perhaps the ideas or concepts will spur some innovation!
joeykrim said:
i've heard this was often done back in the WinMo days but i haven't seen anything on this board regarding this approach. if you have any detailed information, we could def look into it!
Click to expand...
Click to collapse
the thing about winmo ruu's (here's a topic i DO know well) is that they are always in a zip. you decompress the zip and have access to all the files. one of them will be the ruu, the rest are all the supporting files/images/rom. all of the android ruu's seem to come as on large exe that doesn't allow access to the files, it merely runs itself. in the winmo days if you got a rom with no ruu, and didn't want to flash from SD, you just took someone elses ruu and dumped the rom image in to the decompressed folder containing the ruu.
i appreciate the help joey, obviously you are busy with your own problems and a lot of people around here just throw you the old "SEARCH BUTTON" response. any help is greatly appreciated!
2002wrex said:
the thing about winmo ruu's (here's a topic i DO know well) is that they are always in a zip. you decompress the zip and have access to all the files. one of them will be the ruu, the rest are all the supporting files/images/rom. all of the android ruu's seem to come as on large exe that doesn't allow access to the files, it merely runs itself. in the winmo days if you got a rom with no ruu, and didn't want to flash from SD, you just took someone elses ruu and dumped the rom image in to the decompressed folder containing the ruu.
Click to expand...
Click to collapse
interesting again .. so the RUU .exe files for android, do have a payload stored in a rom.zip file which is dumped to a temp directory after the RUU .exe starts and before it finishes.
now, the rom.zip files have been pulled and posted in each of the two RUU .exe threads we currently have. these rom.zip files do contain all .img files which are flashed to the phone. the catch is though, just as the PC36IMG.zip files used in root, these rom.zip files seem to have a special HTC signature (checksum?) in their header.
if you open these rom.zip files from the RUU in winzip, it will error out, but using 7zip, they open just fine.
im new to HTC, this is my first HTC android phone and its almost been 4 weeks so this is as much as i know. it seems, if we're able to alter these rom.zip files either used in the RUU .exe or naming them PC36IMG.zip flashed thru the bootloader and the phone excepts them, we would be golden!
to help save you some searching and let you see what im talking about, here is the latest RUU rom.zip file
http://www.joeyconway.me/evo/stock/RUU_Supersonic_1.32.651.6_Radio_1.39.00.05.31_rom.zip
Subscribed, I was able to Order my EVO today so I will be watching for development. I pledge my donations to whoever is able to figure it out. I really appreciate the efforts of this community.
I second that pledge for donations! I, like many others here, updated while knowing that I probably shouldn't have. I knew better...
Subscribed.
Thanks for all the effort and work. I hope ya'll get it figured out.
dang, I just got my evo yesterday and got the update message so I thought it'd be ok to update it as I thought it might have been old.
Came home and was excited to do all my customization and tweaks, but w/ no prevail
So my local best buy will not give the phone to the customer without pushing the new OTA to it :/
Apparently all of the stores will be doing this per Sprint and HTC's request.
EtherealRemnant said:
So my local best buy will not give the phone to the customer without pushing the new OTA to it :/
Apparently all of the stores will be doing this per Sprint and HTC's request.
Click to expand...
Click to collapse
Try calling them ahead of time before picking it up and asking if you can just swing by and pick it up yourself and call Sprint to activate yourself. Tell them you are in a rush, make up a story, and see if they just let you pay for it and run.
I am happy with what I have since the new update from Viewsonic.
If I only want to add Google Experience, marketplace, do I still need to go through the process of rooting, installing clockwork and a new UI?
Is there just a simple way to add GE to the Classic UI?
Gapps install
http://forum.xda-developers.com/showthread.php?t=842590
Everyone,
I have had zip luck with this method of installing zapps. Not a dev, but I've been doing this long enough.....
I moved the Recovery file to to /sdcard. Checked for command and command line inside that file All ok to my eye.
Downloaded the gapps file which my WinRAR pronounces a WinRAR/Zip file. So I tried renamein the original update.zip and didn't get any install. So I extracted using winRAR. Still no install.
I tried the permutations as well. Extracted using G-Tablet extract. Still no results.
There must be something I am missing here -- too much holiday cheer or too many crowds or whatever.
Suggestions?!
Rev
butchconner said:
Everyone,
I have had zip luck with this method of installing zapps. Not a dev, but I've been doing this long enough.....
I moved the Recovery file to to /sdcard. Checked for command and command line inside that file All ok to my eye.
Downloaded the gapps file which my WinRAR pronounces a WinRAR/Zip file. So I tried renamein the original update.zip and didn't get any install. So I extracted using winRAR. Still no install.
I tried the permutations as well. Extracted using G-Tablet extract. Still no results.
There must be something I am missing here -- too much holiday cheer or too many crowds or whatever.
Suggestions?!
Rev
Click to expand...
Click to collapse
I HAD to resort to putting on Clockwork Mod 0.8 to get GApps on my G Tablet.
Putting the update.zip on the internal and sd card storage did not work for me either with the newest update installed.
Clockwork Mod is a super easy install - just follow the instructions on how to install G Apps...basically: put CWM on your SD card in it's root (meaning NOT in any directories) and rename it update.zip, put the corresponding recovery directory on the SD as well. I use Winrar as well, I drag the recovery directory right from the file itself and to the SD Card.
Will look like:
Drive: update.zip
Drive: /recovery/command
basically.
Flash it the normal stock way (power and volume +). I press Power and Volume + without even powering off the device, because if the device is powered down and then you start it and miss that first start up, the device WILL delete the recovery/command file and the update won't flash.
GL
I don't officially get to play with my GTab until after package opening tomorrow so I can't do anything today, but I'm trying to line up my to do list. I have never rooted, flashed, or modded anything but am not afraid to play around as long as I don't brick the tablet.
What do you mean when you say "put the corresponding recovery directory on the SD as well. I use Winrar as well"? What is the corresponding recovery directory? What do you use Winrar for? I Googled "winrar" and found " WinRAR is a shareware file archiver and data compression utility developed by Eugene Roshal, and first released in the fall of 1993.[1] It is one of the few applications that is able to create RAR archives natively, because the encoding method is held to be proprietary. " I cannot figure out why it would be needed to load the standard Android market.
MSU_Sparty,
When you do updates (or installs) that have to be flashed onto the internal sdcard, they usually com in pairs of files. You will have an update.zip file that has the update in it (DUH!) -- and accompanying it will be a "Recovery" directory that has a command file in it (The command file has only one line that "calls" the update.zip file.
WinRAR "Zip" utility enters the picture because most of the devs here use WinRAR to package updates. The when they tell you to decompress it, you use WiinRAR and are left with a .zip file to install.
That's the question I had about this update. The Gapp file show to be a RAR package, but when I un-RAR it I come up with no .zip file -- only regular files.
Hope this helps you understand.
Rev
P. S. -- If you are new to this business, take it slow and easy and read ahead on this site and make sure you understand what you are doing. I try to do that, but even with years of IT experience I still mess things up once in a while.
Neoprimal,
Thanks for the tip about CWM. I have two tablets and the other has CWM on it and is fairly modded.
But this tablet I am trying to keep basically stock so I can get updates, etc. and see what the "state of product" is.
As mentioned in my previous answer, I am stumped because I am not getting what looks to be an update.zip file from the Gapp download. When I use WinRAR to decompress the Gapp file, I don't get a .zip file -- only a couple of directories. On the other hand, when I rename the Gapp file update.zip and try to flash it it doesn't work.
Again, thanks for the reply.
Anyone else with suggestions!!!????
Rev
Thanks. What you've written really does clarify the previous post. I appreciate it.
But let me ask another naive question. Why don't the developers create their update programs so they can be installed by just downloading them OTA like most applications? That would sure make it easier for neophytes. I'm guessing that the reason is because we aren't really adding an application but replacing the OS.
I greatly appreciate your guidance and that of all of the folks who use this forum.
Happy Holidays!
Hello Daoist, not sure if u got my messages, so here goes. Im on a rooted stock US transformer os version 8.6.5.9 i tried using your method to update to 8.6.5.13 and i used the check if all apks are there .zip you included in that tutorial. The test zip showed me that for some reason im missing kindle-oem.odex kindle-oem.apk maps.odex and maps.apk. So now im at a loss on what can be done, i would love to get my transformer up to speed, 8.6.5.19 I believe is your latest tutorial update. Any help will be greatly appreciated.
Vitto
If you want to update, you have a few choices:
1) find the source and restore the missing/modded files. You can download the manaul updates from the ASUS website (but you need to know how to unblob the files), or there might be a full rom floating around somewhere on xda or the internet.
2) modify the ota so that it skips the kindle and maps files. This would involve editing the updater-script and removing 8 lines- 2 lines for each file. Then rezip everything, (sign it), and flash it.
You could also roll your own custom rom...
Thank you gee one I would have to go with option 1 as i have no idea about either coding or editing a script. So far no luck with the source I might end up d/ling the update from asus website, just need to learn how to unblob it.
Vitto
Ok so i dug through couple of .zips even found the files and got them back in system/app but update is still not recognizing them. Any way anyone could post kindle-OEM.odex maps.apk and maps.odex from v8.6.5.9 US? If sharing apks and files like that is not allowed then i am truly sorry i even mentioned it.
Vitto
I was playing with System/app/...
after checking some useless apps and removing them, this happened to me .
I am wonder what did i choose by mistake, and what was that?
check attachments for screen shots please.
I am not sure about Fusion.apk
If yes that's the problem, may some one provide a copy for me.
Thanks.
Actually they are there, and i can use them, but not visible.
Desire S
ICS 4.0.4
Sense 3.6
fusion.apk is part of htc sense framework, just open rom zip and copy that file to /system/app and reboot
441Excelsior said:
fusion.apk is part of htc sense framework, just open rom zip and copy that file to /system/app and reboot
Click to expand...
Click to collapse
Hi
Dude i ca'not , thats official RUU rom (exe) cant be extract.
then ask someone who use stock rom if he can upload that file for you
441Excelsior said:
then ask someone who use stock rom if he can upload that file for you
Click to expand...
Click to collapse
LooL Thank BTW.
Haven't played with RUU for a very long time. but if I remember correctly, when you run exe it extracts rom zip file to a temp folder somewhere on your c drive, keep it open and do a search you should be able to find the zip.
A good example of why it's a good idea to make a nandroid backup before playing with the system...
ContactFront said:
Haven't played with RUU for a very long time. but if I remember correctly, when you run exe it extracts rom zip file to a temp folder somewhere on your c drive, keep it open and do a search you should be able to find the zip.
Click to expand...
Click to collapse
Yep, OP just needs to search and read. This is exactly the method we used to get the .zip originally when the ICS RUU was released by HTC.
SimonTS said:
Yep, OP just needs to search and read. This is exactly the method we used to get the .zip originally when the ICS RUU was released by HTC.
Click to expand...
Click to collapse
IDC i always relock - install RUU - unlock - root.
THATS ALWAYS BETTER TO HAVE A CLEAR INSTALLATION OF SOME THING RATHER THAN PACK INSTALLATION.
ContactFront said:
Haven't played with RUU for a very long time. but if I remember correctly, when you run exe it extracts rom zip file to a temp folder somewhere on your c drive, keep it open and do a search you should be able to find the zip.
Click to expand...
Click to collapse
That's really nice if it does some thing like that. i did search in %temp% and %user%/app/data
but no trace .
and i am not sure that you are able to use UniExtractor to extract this new type of protected EXE file.
by using CMD, n does command you would get a pack from that EXE file, included a CAB file which is included all data in,
Is there to open a protected CAB?
usualy windows Cabinet files may extract via Winrar, Cabex, Cabextractor, etc ...
SimonTS said:
Yep, OP just needs to search and read. This is exactly the method we used to get the .zip originally when the ICS RUU was released by HTC.
Click to expand...
Click to collapse
2- And there is no big deal with Root n non-rooted device.
3- whats your problem with me?
why you always search for some thing in my topics to say some thing against me?
4-I see that you have lots of thanks
i am wounder that you have ever gained a thanks to solve a problem?????(or just talking off topics, make some one mad, blah blah blah...)
azithro said:
2- And there is no big deal with Root n non-rooted device.
3- whats your problem with me?
why you always search for some thing in my topics to say some thing against me?
4-I see that you have lots of thanks
i am wounder that you have ever gained a thanks to solve a problem?????(or just talking off topics, make some one mad, blah blah blah...)
Click to expand...
Click to collapse
No, there is no problem whether you are rooted or not as you said you need the Fusion.apk - which you just need to pull from the extracted .zip file after the first stage of running the RUU on your PC.
I don't have a problem with you - other than the fact that you seem to want to argue with anyone who gives you advice. You asked for a .apk file - you were suggested to extract it yourself from the RUU and then you decide to argue and find reasons why you can't do it. If you want help then read the answers from knowledgeable people and try what they suggest - otherwise what is the point in asking?
As for my 'Thanks' - who cares? I know less than many of the people on here, and you don't get 'Thanks' in Off-Topic, and I am almost never in OT, and it's none of your damn business why people have thanked me in the past.
You seem to have a real attitude of assuming you have a right to be supported. XDA is not, and never has been, a helpdesk for noobs - you need to get that into your head and deal with it.
Edit on this as I wanted to be sure of what I was saying. If you run the RUU then it will extract various info, including ROM.zip, into a temp folder, but this .zip is only useful as an image to flash from recovery, not to extract individual files from. On that basis, look for one of the ROMs that were based on the official RUU - there was a de-odexed, pre-rooted one released fairly shortly after the RUU - and pull fusion.apk from there.
And don't take your rookie mistake and frustration at yourself out on other members of XDA.
azithro said:
That's really nice if it does some thing like that. i did search in %temp% and %user%/app/data
but no trace .
and i am not sure that you are able to use UniExtractor to extract this new type of protected EXE file.
by using CMD, n does command you would get a pack from that EXE file, included a CAB file which is included all data in,
Is there to open a protected CAB?
usualy windows Cabinet files may extract via Winrar, Cabex, Cabextractor, etc ...
Click to expand...
Click to collapse
It indeed does somthing like this
Look into your C:\Users\YOURUSERNAME\AppData\Local\Temp
SimonTS said:
No, there is no problem whether you are rooted or not as you said you need the Fusion.apk - which you just need to pull from the extracted .zip file after the first stage of running the RUU on your PC.
I don't have a problem with you - other than the fact that you seem to want to argue with anyone who gives you advice. You asked for a .apk file - you were suggested to extract it yourself from the RUU and then you decide to argue and find reasons why you can't do it. If you want help then read the answers from knowledgeable people and try what they suggest - otherwise what is the point in asking?
As for my 'Thanks' - who cares? I know less than many of the people on here, and you don't get 'Thanks' in Off-Topic, and I am almost never in OT, and it's none of your damn business why people have thanked me in the past.
You seem to have a real attitude of assuming you have a right to be supported. XDA is not, and never has been, a helpdesk for noobs - you need to get that into your head and deal with it.
Edit on this as I wanted to be sure of what I was saying. If you run the RUU then it will extract various info, including ROM.zip, into a temp folder, but this .zip is only useful as an image to flash from recovery, not to extract individual files from. On that basis, look for one of the ROMs that were based on the official RUU - there was a de-odexed, pre-rooted one released fairly shortly after the RUU - and pull fusion.apk from there.
And don't take your rookie mistake and frustration at yourself out on other members of XDA.
Click to expand...
Click to collapse
Thanks Bro, Cheers man :highfive:
ContactFront said:
It indeed does somthing like this
Look into your C:\Users\YOURUSERNAME\AppData\Local\Temp
Click to expand...
Click to collapse
Thank you 2 bro. GJ
ContactFront said:
Haven't played with RUU for a very long time. but if I remember correctly, when you run exe it extracts rom zip file to a temp folder somewhere on your c drive, keep it open and do a search you should be able to find the zip.
Click to expand...
Click to collapse
My Desire s is running MIUI v5 android 4.1.2 rom about 4 months and it runs Perfect , the best ROM I have ever used, BTW I bought Lumia 920, and I Love it, do not want to go back to android again.