Google Experience only - G Tablet General

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!

Related

Android app that roots your phone

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.

[help]anybody can tell me how to convert official ROM to update.zip

anybody can tell me how to convert official ROM to update.zip
I want to know how to make an official from the ROM can customize the ROM, instead of only at others do the update.zip in thickening delete...
First, you need to run the RUU.
Check in your system TEMP folder, and you should have an update.zip there.
Unzip that, and you'll have amongst others, system.img
Extract the files via unyaffs or other means, customize your build, zip and sign.
Voila.
My guess is that a simple search via the search tool would've resolved that, then again, I guess you were too lazy to do that.
adwinp said:
First, you need to run the RUU.
Check in your system TEMP folder, and you should have an update.zip there.
Unzip that, and you'll have amongst others, system.img
Extract the files via unyaffs or other means, customize your build, zip and sign.
Voila.
My guess is that a simple search via the search tool would've resolved that, then again, I guess you were too lazy to do that.
Click to expand...
Click to collapse
I have get the system.img, but I don't know what tools and methods reduction system.img to update.zip file format,can replace programs self.
Can you explain it step by step?
He actually told you in the post above to use unyaffs, all you need to know is already in this forum if you search for it. Here's a thread to get you started:
http://forum.xda-developers.com/showthread.php?t=566235
thanks , i went to see

might be a stupid question, but my g tab doest not recognizes the .rar Rom file

i'm trying to update my gtab to tnt lite 3.1. currently, i'm running the tnt lite 2.2 and installed that with out any problems following directions. that was a zip format. however, the tnt lite 3.1 file that i got from the following thread
http://forum.xda-developers.com/showthread.php?t=842004
is a .rar. When i go to install the zip from sd card, go to roms folder, it doesn't come up and i can't see it. however, the tnt lite 2.2 is there. i tried just re-doing the folder into zip, and got it to recognize, but it still did not boot up. i selected it and it just went back to the previous menu. how or where can i get the zip file for tnt lite 3.1?
You need to extract the rar file first. Once extracted you will find a update.zip file you can use to install.
You can extract the rar on the gtab with androzip from market or unrar it from your PC with winrar or 7zip.
wasya152 said:
i'm trying to update my gtab to tnt lite 3.1. currently, i'm running the tnt lite 2.2 and installed that with out any problems following directions. that was a zip format. however, the tnt lite 3.1 file that i got from the following thread
http://forum.xda-developers.com/showthread.php?t=842004
is a .rar. When i go to install the zip from sd card, go to roms folder, it doesn't come up and i can't see it. however, the tnt lite 2.2 is there. i tried just re-doing the folder into zip, and got it to recognize, but it still did not boot up. i selected it and it just went back to the previous menu. how or where can i get the zip file for tnt lite 3.1?
Click to expand...
Click to collapse
This is directly taken from the link you provided. The rar file once extracted will have the update.zip file, and a recovery folder with a command file in it. It is a rar so people with clockwork know not to try and flash the file directly without pulling the zip file out of it.
Instructions for those with standard recovery:
- Extract the RAR to the root of your internal memory. So, for example, if your device is mounted on your Windows F drive, you need to extract the RAR so that you have an F:\update.zip file and an F:\recovery folder. Then, unmount the drive cleanly.
- Power off the device, then begin the flash process by holding the power switch and volume up switch for several seconds. You should see a recovery screen and it will take 1-2 minutes to complete.
- After the update is complete, the system will reboot.
- You will see the standard Google registration screen, on first boot. You can skip the Google registration process and try later, when you have WiFi running.
Note: these instructions are for the internal memory. If you have no access to that (ie stuck in a boot loop), you can add the files to a microSD card and that will work. However, you need to make one edit to the \recovery\command file, which is a text file. Edit it in notepad and change "SDCARD" to "SDCARD2" and resave it. But, make sure that Windows doesn't add a .TXT extension - it HAS to be called "command".
Instructions for those with clockworkmod .8:
- Extract the RAR and place the update.zip file anywhere in /sdcard (do NOT just copy the original RAR, that won't work! You have to open up the RAR and copy the update.zip inside. You don't need the /recovery folder for cwm). I would recommend putting the file on the root of /sdcard, since it will be easier to upgrade that way.
- Reboot into recovery. Do a backup first, as that's always a good idea.
- Then, choose "apply sdcard:update.zip", assuming you added the update.zip to the root of /sdcard, and run it.
- Reboot.
Note: I have heard reports that this might "Status 7" and I have no fix for that, yet. It seems to be intermittent.
thanks guys. that was very helpful. got it to work.
Good to hear. I actually specifically used a rar format for these because it needs to be extracted. I used to use a zip format and there was a lot of confusion, as well - I need to support standard recovery users as long as we have them (and we will probably always have a few of them).

[Guide]Installing Custom Splash Screens (Revised 10/1/11)(Works for all hboots)

*updated 2/2/2011*
First, props to silentstryder for putting up the process. I'm just giving it it's own thread for the newbies, users with the new hboots (2.02 and 2.10) and for people who just plain don't like command prompt. Also, HUGE thanks to Stoney 666 for giving me the software to convert images to .rgb565 and to CYBERxNUKE for creating it.
*Note*
all filenames in this process are case sensitive. Don't capitalize it if it's not capitalized and don't lower case it if it's not lowercase. Also, do not add extensions unless you're instructed to. Doing any of these can mess up the process.
**UPDATE 10/1/11**
Updated a working PC36IMG.zip (in the attachments in the bottom). The last one was corrupt and the Unrevoked website goes down sometimes.
**UPDATE 10/24/11**
Added up a pro tip for people who want to make their own Splash screens and not just make their own Splash PC36IMG.zip.
Okay, rewriting this process from scratch because, well it's easier that way.
PART 1 (if you downloaded a splash screen image from the Themes and Apps Section of the Evo forums in XDA, the proceed directly to PART 2).
1. Download the EVOSplash Zip from the attachments.
2. Open the howto.txt file inside for instructions on how to use it. With this program, you can convert a file into the required .rgb565 file.
3. Rename the converted .rgb565 file splash1.img
PART 2 (if you have your file all ready to go)
*note* if you have not done so, rename the splash picture to splash1.img
1. Go to this website: http://unrevoked.com/rootwiki/doku.php/public/forever
2. Download the original PC36IMG.zip file (it's close to the bottom)
3. Use a .zip editor (winzip, 7zip, etc) to open it.
*ehem* DO NOT EXTRACT, JUST OPEN
4. Replace the splash1.img in the zip with the one you have/just made. Save it.
5. Plug your phone in, connect to PC via disk drive.
6. Put the PC36IMG onto the root of your SD card (for newbies, that's the very first page of the SD card).
7. Reboot phone into bootloader (turn off, volume down + power)
8. The phone should recognize the zip and ask if you want to update. Select yes (I believe it's volume up for yes).
The zip will install and you're new splash screen should be there next time the phone reboots.
I hope this helps a lot and thanks to everyone who's read it and been patient. It took me a month to thread jumping before I found a process that worked with hboot 2.02 and 2.10 (I have 2.10). This is also the easiest way for people who are uncomfortable with adb and the command prompt.
Give me a thanks if it helped, I do this for free so I don't accept donations
**PRO TIP**
If you want it to fit the whole screen (or to make your own from scratch), use a photo or paint like program (Photoshop, etc). Make a new file that is 480 pixels wide and 800 pixels for height. Then re-size the picture you want to use in it (another tip: use a picture that is bigger than 480x800. If it's smaller, it'll get fuzzy and become lower quality) to fit the borders of the new file. Alternatively, you can make your own. Save as JPEG when you're done, then follow the instructions above.
Followed the process, it's not working for me. I don't get a prompt to update in hboot. PC36IMG.zip is on the root of my SD card. =/
EDIT: When I boot back into CM6 and look at the root of my SD card the .zip is gone...
EDIT2: Diagnosed and fixed, had to make the PC36IMG.zip rwx-rwx-rwx. Flashed just fine!
what about users with hboot 0.93.0000?
AbsolutZeroGI said:
First, props to silentstryder for putting up the process. I'm just giving it it's own thread for the newbies, users with the new hboots (2.02 and 2.10) and for people who just plain don't like command prompt.
Okay here we go. This process is to install custom splash screens without having to use the command prompt or fastboot. Users who have hboot 2.02 and 2.10 CANNOT use the command prompt anyway so this is the workaround for those people.
1. Download the PC36IMG.zip from the attachments.
2. Find the splash screen you want and rename it splash1.img (don't worry about any warnings about it not being usable, Android is smarter than Windows).
3. Open the .zip and delete the splash1.img that's already there and replace it with the one you downloaded.
4. Plug your phone in, select "disk drive".
5. Move the .zip file into the first page (or root page) of your sd card.
6. Remount sd card (not necessarily important, but recommended).
7. Power Down
8. Load into Hboot (volume down + power)
9. Hboot will recognize the .zip as an update and will ask if you want to install it, hit volume up to install.
10. Reboot and enjoy your new splash screen.
If this gets a sticky, so be it, if not, I am going to PM the OP of the sticky'd thread with all the splash screens and ask him if he'd put this guide in there.
I hope this helps some people, it sure helped me.
Click to expand...
Click to collapse
you forgot to mention that the image used for the splash needs to be in .rgb565 format before renaming it to splash1.img, and has to be saved as a 24bit rgb bmp or png file before converting to .rgb565.... use this to convert the images to .rgb565 View attachment EVOSplash.zip there is also a "how to" in the zip.
or to make your life easier, go here... http://forum.xda-developers.com/showthread.php?t=812572 and i'll make one for you...
Stoney 666 said:
you forgot to mention that the image used for the splash needs to be in .rgb565 format before renaming it to splash1.img, and has to be saved as a 24bit rgb bmp or png file before converting to .rgb565.... use this to convert the images to .rgb565 View attachment 481035 there is also a "how to" in the zip.
or to make your life easier, go here... http://forum.xda-developers.com/showthread.php?t=812572 and i'll make one for you...
Click to expand...
Click to collapse
Thanks, all the splash files i've downloaded so far have been in .rgb565 so far but this is definitely useful information, especially if people want to make their own.
meansixx said:
what about users with hboot 0.93.0000?
Click to expand...
Click to collapse
This is compatible with all hboots. It's just that people with the two newest ones can't use any other method (to my knowledge) except this one so I thought it was guide worthy. Most of the threads that have splash screens have alternate instructions.
*bump*
people still need this, I wish I could get it sticky'd
problem installing splash screen
I am having the same problem as above, I have read alot on this fourm and still cannot get a different splash screen up. Im looking to install the stock flash for the evo. I'm getting an error no image found please help.
Thanks...
I found
a flashable zip of the stock splash screen, and it worked, but I would still like to know how to do this. I wanted to put on the red evo skelton giving the finger.
pgagolfer said:
a flashable zip of the stock splash screen, and it worked, but I would still like to know how to do this. I wanted to put on the red evo skelton giving the finger.
Click to expand...
Click to collapse
When you add the image to the Evo, make sure it's in it's native resolution (my instructions only cover splash screens from this forum, which is 800x480).
For further info, read Stoney 666's post, that's how you do it if your image doesn't start in the right file type.
Thanks.
Got it to work, not sure how, i think i used a different PC36IMG file, or I took zip off the ending.
pgagolfer said:
Got it to work, not sure how, i think i used a different PC36IMG file, or I took zip off the ending.
Click to expand...
Click to collapse
Even if you take off the .zip it's still a zip so one way or the other it works I just uploaded the PC36IMG file I found on the Unrevoked website.
Glad you got it to work!
Ok, I'm not doing something right. I downloaded the PC36IMG.zip, opened it, replaced the file with the splash screen I wanted, and re-zipped the file. Put it on the root of my sd card, and started it in bootloader. First, it didn't prompt me to update, although when it checked the sd card for updates, I did note that it said "parsing PC36IMG.zip", but then returned to the menu. I tried flashing it from recovery as well and it didn't work.
From all the stuff I've read this seems to be the method that makes the most sense and is easiest. I've tried flashing it via ABD and a whole bunch of other stuff to no avail; my computer must not like my phone.
What am I doing wrong, I followed your steps...
EDIT: I rooted phone with unrevoked...don't know if that is why. I know that has been a roadblock with some of the other methods of changing the splash screen.
Any possible way to get this turned into a flashable zip file? Im not good with adb!
wizholt7 said:
Ok, I'm not doing something right. I downloaded the PC36IMG.zip, opened it, replaced the file with the splash screen I wanted, and re-zipped the file. Put it on the root of my sd card, and started it in bootloader. First, it didn't prompt me to update, although when it checked the sd card for updates, I did note that it said "parsing PC36IMG.zip", but then returned to the menu. I tried flashing it from recovery as well and it didn't work.
From all the stuff I've read this seems to be the method that makes the most sense and is easiest. I've tried flashing it via ABD and a whole bunch of other stuff to no avail; my computer must not like my phone.
What am I doing wrong, I followed your steps...
EDIT: I rooted phone with unrevoked...don't know if that is why. I know that has been a roadblock with some of the other methods of changing the splash screen.
Click to expand...
Click to collapse
For 1 you don't have to unzip and re-zip. Just replace the image that's already in the zip. I think a couple of people have had this problem before. I'd try again without re-zipping the package.
Also, if you didn't get the splash screen from this section of the forums (i.e. you're using your own or from a different phone in xda), go to post #4 (on the first page) and read stoney 666's post about converting the file to .rgb565 and then renaming it (not convert, rename) it to splash1.img (yes, with the file extension).
Basically, from where you are, here's what I'd do:
attempt to just replace the splash1.img file in the zip without unzipping and try again. Or, try downloading the original, untainted one here: http://unrevoked.com/rootwiki/doku.php/public/forever
and follow the steps over again.
if that doesn't work:
follow stoney 666's instructions and convert the image to .rgb565 format and then rename it to splash1.img.
That should do it.
I will also post that link in the OP and tell people to get the original instead of using mine as people have been having trouble with it.
luist4498 said:
Any possible way to get this turned into a flashable zip file? Im not good with adb!
Click to expand...
Click to collapse
I revised the instructions on the original post, it should work for you. It's not flashable in recovery, but it's flashable in bootloader which is just as good (don't need clockwork or ra recovery to do it).
I tried it again adding the file to the zip instead of unzipping, rezipping, and no dice. I'll download the PC36IMG file from unrevoke's website and see if that works.
EDIT: I just downloaded the one from unrevoked's website, and I noticed the image file it has in there by default is "splash1.img". The name of the file I am inserting is "evosplash1.rgb565". That is the correct file name, right?
Also, I just tried it with the file from unrevoked's website, still no luck. It just says "parsing PC36IMG" but doesn't do anything and returns to the bootloader options...
Ok, so I finally got it figured out, thanks to moseso. Apparently, it was because the name of the file was wrong. As I understood it, the file was to be named evosplash1.rgb565 . But I had to rename it to splash1.img . I guess it was a misunderstanding on my part, idk. But I got it now. Here is the link to the thread if anyone wants or needs it: http://forum.xda-developers.com/showthread.php?p=11113102#post11113102
wizholt7 said:
Ok, so I finally got it figured out, thanks to moseso. Apparently, it was because the name of the file was wrong. As I understood it, the file was to be named evosplash1.rgb565 . But I had to rename it to splash1.img . I guess it was a misunderstanding on my part, idk. But I got it now. Here is the link to the thread if anyone wants or needs it: http://forum.xda-developers.com/showthread.php?p=11113102#post11113102
Click to expand...
Click to collapse
It says in the OP to rename the file and always has.
Glad you got it figured out.
AbsolutZeroGI said:
*updated 2/2/2011*
First, props to silentstryder for putting up the process. I'm just giving it it's own thread for the newbies, users with the new hboots (2.02 and 2.10) and for people who just plain don't like command prompt. Also, HUGE thanks to Stoney 666 for providing the software to convert images to .rgb565.
*Note*
all filenames in this process are case sensitive. Don't capitalize it if it's not capitalized and don't lower case it if it's not lowercase. Also, do not add extensions unless you're instructed to. Doing any of these can mess up the process.
Okay, rewriting this process from scratch because, well it's easier that way.
PART 1 (if you downloaded a splash screen image from the Themes and Apps Section of the Evo forums in XDA, the proceed directly to PART 2).
1. Download the EVOSplash Zip from the attachments.
2. Open the howto.txt file inside for instructions on how to use it. With this program, you can convert a file into the required .rgb565 file.
3. Rename the converted .rgb565 file splash1.img
PART 2 (if you have your file all ready to go)
*note* if you have not done so, rename the splash picture to splash1.img
1. Go to this website: http://unrevoked.com/rootwiki/doku.php/public/forever
2. Download the original PC36IMG.zip file (it's close to the bottom)
3. Use a .zip editor (winzip, 7zip, etc) to open it.
*ehem* DO NOT EXTRACT, JUST OPEN
4. Replace the splash1.img in the zip with the one you have/just made. Save it.
5. Plug your phone in, connect to PC via disk drive.
6. Put the PC36IMG onto the root of your SD card (for newbies, that's the very first page of the SD card).
7. Reboot phone into bootloader (turn off, volume down + power)
8. The phone should recognize the zip and ask if you want to update. Select yes (I believe it's volume up for yes).
The zip will install and you're new splash screen should be there next time the phone reboots.
I hope this helps a lot and thanks to everyone who's read it and been patient. It took me a month to thread jumping before I found a process that worked with hboot 2.02 and 2.10 (I have 2.10). This is also the easiest way for people who are uncomfortable with adb and the command prompt.
Give me a thanks if it helped, I do this for free so I don't accept donations
Click to expand...
Click to collapse
maybe a really stupid question, as i can be known for those but i can be a worry wart. im using miui 1.8.5 on tiamat-evo 4.0.6 w/ sbc, and im just curious, is reflashing the stock pc36img.zip (after my file replacement, ofc) going to change ANYTHING else on my phone? been having a hell of a time keeping it running lately and i WANT to do this, but now im leery of EVERYTHING...

[Q] task rpcrouter:15 blocked (CDMA)

Same as posted here "I have an HTC [differing: Touch Pro (Alltel CDMA)]. I followed the instruction on forum.xda-developers.com for [FRX*] but it [enters an endless loop] at "task rpcrouter:15 blocked for more than 120 sec". The solution that worked in that link does not solve the same problem with a CDMA RAPH800.
The solution given there (paraphrased from that thread):
Link to the fix. The issue is caused by not having a data plan; the install gets stuck in a loop looking for a signal.
The solution that worked for a GSM phone
download RIL file from http://forum.xda-developers.com/atta...9&d=1302817139 and place in the root of microsd.
download rootfs file from http://www.megaupload.com/?d=1NGCVCTT and place in the root of microso.
add to the end of /conf/froyo.user.conf file "/sdcard/libhtcgeneric-ril.so /lib/froyo/libhtcgeneric-ril.so" before the last "}"
Please help me find a solution for a CDMA phone - next month I'd like to take a dozen of these phones and use them as learning aids in a construction course for laborers, but I cannot start testing construction applications since I cannot get the OS to work.
I'm curious as to what happens when you format your microSD and run FRX7.1MR without anything additional. Could I get you to try this method without the additional stuff?
To be explicit, I'd like you to format your microSD with something other than the Windows method and I'd like you to download THIS (if you haven't already) and THIS. Extract the contents of both files to the root of your microSD. You should see a folder called "FRX07.1" and under that folder, you should see 3 folders and 7 files. Move the contents of that folder up to the root of the microSD. Look under the folder called "STARTUPS" and locate your device type (ie RAPH800) and copy over to the root of your microSD. Once done, run Haret on your phone and let me know what happens.
do you have an application you suggest for "format your microSD with something other than the Windows method"; sourceforge did not turn up anything.
forest.peterson said:
do you have an application you suggest for "format your microSD with something other than the Windows method"; sourceforge did not turn up anything.
Click to expand...
Click to collapse
use SDFormatter
wow that SDformatter link has a lot of popups - this link feels less like I just found a date at the bus-stop sdcard.org/downloads/formatter_3 ; but it will not install on either Server2008R2 x64 or Server2003 R2 SP2 x32.
I reformatted the microSd with the format tool in Server2008R2 as FAT format. Installed the files, and boom - I see little green guys swirling around the screen. After awhile a dialog appeared "Sorry! The process com.android.phone has stopped unexpectedly. Please try again"; the dialog closed and it seems like it works! Thank you. I will try again with the HPtool and as FAT32.
Now I just need to learn how to use Android - and the screen calibration seems off? Deleting ts-calibration and rebooting to calibrate.
Glad to hear using the latest bundle works for you! Yeah, that might be a slight issue with an outdated kernel. The main thing I wanted to do is get you booted up first!
Before we continue, make sure you make a backup of your current configuration by copying the contents of the microSD and either moving it to your computer or some other storage device. This way you know you have a "working" bundle.
Next we update the kernel package from HERE; might I suggest using THIS kernel package. Be sure to delete the old files (should be located under root of the microSD and called modules-xxx and zImage) first! Extract till you see two files then rename zImage-xxx to just zImage and feel free to delete the files you extracted from. I've always created my own ts-calibration file but just wanted you to have it, "just in case".
Additionally, you may also need to update the rootfs by deleting the file called rootfs and downloading THIS file. Extract the file and rename to just rootfs and be sure to place it where the file called Haret is (default location is root of the microSD).
files are downloaded and installed - everything seems to work

Categories

Resources