I just flashed PureKat V4 on this HTC G2 and I'm having trouble getting GApps on here. I got the rom working with S-On by flashing it in TWRP, then extracting it on my PC and doing fastboot flash boot boot.img. The problem is I cannot flash GApps. I've been trying to do it via sideload in TWRP. There is over 1 GB of space, so far more than enough. I've been using the pico and nano 4.4.x packages plus both the regular and "small" Cyanogenmod GApps packages for CM11.
For nano and CM11 regular GApps, it says:
Code:
Insufficient storage space available in
System partition. You may want to use a
smaller GApps (i.e. Mini Modular GApps)
or remove some apps using gapps-config.
For pico and CM11 "small" GApps it says:
Code:
E: Could not create file for updater extract in '
I'm not sure what it says after the apostrophe because that is the edge of the screen.
The only thing I could think of is S-On, so I tried to S-Off using the "new gfree" method, ie.
Code:
[email protected]:/data/local/tmp # ./gfree -f -b hboot-eng.img
--secu_flag off set
--cid set. CID will be changed to: 11111111
--sim_unlock. SIMLOCK will be removed
--hboot set. hboot image hboot-eng.img will be installed in partition 18
Section header entry size: 40
Number of section headers: 44
Total section header table size: 1760
Section header file offset: 0x000138b4 (80052)
Section index for section name string table: 41
String table offset: 0x000136fb (79611)
Searching for .modinfo section...
- Section[16]: .modinfo
-- offset: 0x00000a14 (2580)
-- size: 0x000000cc (204)
Kernel release: 3.0.101-cyanogenmod-g9eb87bf
New .modinfo section size: 212
Attempting to power cycle eMMC... OK.
Write protect was successfully disabled.
Searching for mmc_blk_issue_rq symbol...
- Address: 00000000, type: t, name: mmc_blk_issue_rq, module: N/A
Kernel map base: 0x00000000
Failed to open /dev/kmem: No such file or directory trying /dev/gkmem
Failed to open /dev/gkmem: No such file or directory
I'm assuming it failed because I'm already running a custom ROM. This is the only step I tried in the gfree method because it looked like all the other steps are for root and recovery, which I have already.
I tried installing the Play Store apk, but as expected, the Play Store icon is unresponsive after installation. What should I do to get the Play Store? It's really the only Google application that needs to be on this device.
It's always right when I give up hope that I figure out the answer...
Solution: Use these GApps: http://dz.ace-com.cz/index.php/downloads
Related
whats up guys, so i decided to unroot my g2 and i used this method to root it (http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD) i guess i used the gfree method? and i tried doing the Returning to stock method on the same link. so i got to the part where i had to restore the partition 7 i did both methods of trying to restore the partition 7..but it resulted with error opening copied file..but i synced it anyway, still s-off....i need the s-on....but the phone does seem like its back to its original stock rom...i jsut need to have it s-on...any idea on how to turn it back on???? if i do the ota update would it make it turn back on, or would that just brick my phone?
C:\Users\Blah\Desktop\p>adb shell
# /data/local/tmp/gfree -s on -c T-MOB010
/data/local/tmp/gfree -s on -c T-MOB010
--secu_flag on set
--cid set. CID will be changed to: T-MOB010
Section header entry size: 40
Number of section headers: 44
Total section header table size: 1760
Section header file offset: 0x00015398 (86936)
Section index for section name string table: 41
String table offset: 0x000151df (86495)
Searching for .modinfo section...
- Section[16]: .modinfo
-- offset: 0x000011cc (4556)
-- size: 0x000000c4 (196)
Kernel release: 2.6.32.17-g814e0a1
New .modinfo section size: 204
Attempting to power cycle eMMC... OK.
Write protect was successfully disabled.
Searching for mmc_blk_issue_rq symbol...
- Address: c02a8d44, type: t, name: mmc_blk_issue_rq, module: N/A
Kernel map base: 0xc02a8000
Kernel memory mapped to 0x40002000
Searching for brq filter...
- Address: 0xc02a8d44 + 0x34c
- 0x2a000012 -> 0xea000012
Backing up current partition 7 and patching it...
Error opening copy file.
#
^---this is what happens when i try to put s-on with gfree way under the Returning to Stock on the wiki page. ( i tried both ways and the i have the same result of it saying "Error opening copy file." if anyone has encountered the same problem or have a solution for this, please it would be great, i need to get my g2 exchanged because the orientation/tilt sensor is busted...
*NVM I GOT IT*
Nvm i got it
Whatever you do, make sure you don't explain how you fixed it. That way, if someone else has the same problem in the future, you don't inadvertently help them.
futuremonkey said:
Whatever you do, make sure you don't explain how you fixed it. That way, if someone else has the same problem in the future, you don't inadvertently help them.
Click to expand...
Click to collapse
Tell it monkey! So sick of people doing that and wanting everyone to help, but then don't say what fixed it so the next person doesn't have to go through hell and back. Very selfish. This is a give and take community guys not just take take take.
Sent from my HTC Vision using XDA Premium App
uhhh, should i explain how i fixed it or what..no one even bothered trying to help me out anyway
YES PLEASE! I'm stuck with the exact same problem and I just can't figure it out.
Hi Guys,
Need help! I have a Desire Z that can boot into CWM however cannot apply ROMS. I keep getting an Error MEssage that reads "E:Error in /sdcard/"name of ROM.zip" (status 1)" but have had different status numbers.
It was a unity rom- but tried modaco and cm to get it working with no luck. HAve tried rooting process from scratch but keep getting errors.
Formating and clearing caches does not help.
I can ADB and shell to the phone so able to transfer files etc.
HEre is an example of some of the errors I get though the various processes...
/data/local/tmp # ./gfree -f -b hboot-eng.img -y recovery.img
./gfree -f -b hboot-eng.img -y recovery.img
--secu_flag off set
--cid set. CID will be changed to: 11111111
--sim_unlock. SIMLOCK will be removed
--hboot set. hboot image hboot-eng.img will be installed in partition 18
--recovery set. recovery image recovery.img will be installed in partition 21
Section header entry size: 40
Number of section headers: 44
Total section header table size: 1760
Section header file offset: 0x000138b4 (80052)
Section index for section name string table: 41
String table offset: 0x000136fb (79611)
Searching for .modinfo section...
- Section[16]: .modinfo
-- offset: 0x00000a14 (2580)
-- size: 0x000000cc (204)
Kernel release: 2.6.32.28-cyanogenmod-g4f4ee2e
New .modinfo section size: 216
Attempting to power cycle eMMC... Failed.
Module returned an unknown code (No such file or directory).
When switching between CWM screens I get the followign error messages...
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Factory Reset from the Boot Screen just results in the screen being locked at three android men on skateboards.
Any help is much appreciated....
sounds like fried emmc
Hey everyone, I'm new here and I finally decided to root my g2. I'm using the cyanogenmod wiki entry. I am at the point where it says to write "./gfree -f -b hboot-eng.img -y recovery.img" though every time I do this it says:
# ./gfree -f -b hboot-eng.img -y recovery.img
./gfree -f -b hboot-eng.img -y recovery.img
--secu_flag off set
--cid set. CID will be changed to: 11111111
--sim_unlock. SIMLOCK will be removed
--hboot set. hboot image hboot-eng.img will be installed in partition 18
--recovery set. recovery image recovery.img will be installed in partition 21
Section header entry size: 40
Number of section headers: 44
Total section header table size: 1760
Section header file offset: 0x000138b4 (80052)
Section index for section name string table: 41
String table offset: 0x000136fb (79611)
Searching for .modinfo section...
- Section[16]: .modinfo
-- offset: 0x00000a14 (2580)
-- size: 0x000000cc (204)
Kernel release: 2.6.32.17-g814e0a1
New .modinfo section size: 204
Attempting to power cycle eMMC... OK.
Write protect was successfully disabled.
Searching for mmc_blk_issue_rq symbol...
- Address: c02a8d44, type: t, name: mmc_blk_issue_rq, module: N/A
Kernel map base: 0xc02a8000
Kernel memory mapped to 0x40002000
Searching for brq filter...
- Address: 0xc02a8d44 + 0x34c
- ***WARNING***: Found fuzzy match for brq filter, but conditional branch isn't
. (0xea000012)
Backing up current partition 18 and installing specified hboot image...
Backing up partition /dev/block/mmcblk0p18 to /sdcard/part18backup-1313372731.bi
n ...
Writing image hboot-eng.img to partition /dev/block/mmcblk0p18 ...
Error opening input image.
is this normal? if it helps, I continue on to write
./root_psn
sync
and nothing happens. Thanks ahead of time for any help.
Nevermind. I just went through every step again and it worked.
Hi, I'm trying to root my HTC Desire Z in order to put custom ROM on it later, and having some (prolly noob) issue:
Followed the 'ADB for noobs' thread and all ok: http://forum.xda-developers.com/showthread.php?t=865685
Now I'm trying to follow the rooting on this thread: http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
Stuck on step #4:
# cd /data/local/tmp
# ./gfree -f -b hboot-eng.img -y recovery.img
# ./root_psn
# sync
Getting the following:
$ ./gfree -f -b hboot-eng.img -y recovery.img
./gfree -f -b hboot-eng.img -y recovery.img
--secu_flag off set
--cid set. CID will be changed to: 11111111
--sim_unlock. SIMLOCK will be removed
--hboot set. hboot image hboot-eng.img will be installed in partition 18
--recovery set. recovery image recovery.img will be installed in partition 21
Section header entry size: 40
Number of section headers: 44
Total section header table size: 1760
Section header file offset: 0x000138b4 (80052)
Section index for section name string table: 41
String table offset: 0x000136fb (79611)
Searching for .modinfo section...
- Section[16]: .modinfo
-- offset: 0x00000a14 (2580)
-- size: 0x000000cc (204)
Kernel release: 2.6.35.10-g53a84f9
New .modinfo section size: 204
Attempting to power cycle eMMC... Failed.
Module returned an unknown code (Operation not permitted).
Any idea? (highlighted the part which I think is the issue, but don't know how to resolve it )
I get the same thing too
Sent from my T-Mobile G2 using xda app-developers app
so did you successfully downgrade first?
Downgrade and then ROOT
or if easier after downgrade follow The cyanogen Wiki
or many seem to find it easiest to follow STRAWMETALs PDF GUIDE
I said it was a noob issue, Didn't downgrade it :$ , will do that and update. Thanks demkantor
I want to load a custom ROM on my Desire Z. (finally!)
And I eventually got adb to work.
Now following the guide: Rooting the Vision (G2/DZ) and DHD; I got as far as this step:
4 S-OFF, root and its friends Super-CID, SIM-unlock, engineering hboot, clockwork recovery and root
In the following section we are trying to gain write access to the emmc by power cycling it.
We recommend to install the engineering hboot as part of the gfree procedure.
In the root shell (indicated by the #) that you got in the Temporary root section execute the following commands:
Code:
# cd /data/local/tmp
# ./gfree -f -b hboot-eng.img -y recovery.img
# ./root_psn
# sync
Wait a few seconds for the changes to "take".
Click to expand...
Click to collapse
Before receiving this error:
Code:
# ./gfree -f -b hboot-eng.img -y recovery.img
./gfree -f -b hboot-eng.img -y recovery.img
--secu_flag off set
--cid set. CID will be changed to: 11111111
--sim_unlock. SIMLOCK will be removed
--hboot set. hboot image hboot-eng.img will be installed in partition 18
--recovery set. recovery image recovery.img will be installed in partition 21
Section header entry size: 40
Number of section headers: 44
Total section header table size: 1760
Section header file offset: 0x000138b4 (80052)
Section index for section name string table: 41
String table offset: 0x000136fb (79611)
Searching for .modinfo section...
- Section[16]: .modinfo
-- offset: 0x00000a14 (2580)
-- size: 0x000000cc (204)
Kernel release: 2.6.32.21-g132894e
New .modinfo section size: 204
Attempting to power cycle eMMC... OK.
Write protect was successfully disabled.
Searching for mmc_blk_issue_rq symbol...
- Address: c02adc44, type: t, name: mmc_blk_issue_rq, module: N/A
Kernel map base: 0xc02ad000
Kernel memory mapped to 0x40002000
Searching for brq filter...
- Address: 0xc02adc44 + 0x34c
- 0x2a000012 -> 0xea000012
Backing up current partition 18 and installing specified hboot image...
md5sum #1 = 62c0aac0a85f3a0a0cbe364b64c552e6
md5sum #2 = 2ce1bdd5e4c1119ccfcecb938710d742
Backing up partition /dev/block/mmcblk0p18 to /sdcard/part18backup-1363017105.bin ...
Writing image hboot-eng.img to partition /dev/block/mmcblk0p18 ...
md5sum #3 = 62c0aac0a85f3a0a0cbe364b64c552e6
md5sum #3 == md5sum #1 - the hboot image was not installed!
Probably the power cycle of the eMMC failed. Check the messages above.
You might join the IRC channel #G2Root on Freenode for further help!
What should be my next course of action?
Thanks for all suggestions,
Alec Taylor
Double check you have the right hboot downloaded and that the md5sum matches, then run the command again. If you still have issues copy and paste your input/output from cmd here
Sent from my Nexus 7 using xda premium
I have included the input/output from my CMD in the initial post.
Sorry I thought you were just copying and pasting from the guide you were folowing. I guess I was reffuring to the entire root procedure but its no big deal
Its telling you exactly what is happening, phone didn't take the flash of the new engineeging bootloader, probably the emmc didn't cycle, try running command again, if its the same outcome double check your radio version as that can cause this or can you post all info from your hboot screen here
Sent from my SGH-T839 using Tapatalk 2
Also I couldn't get it to work with Gingerbreak or DooMLoRD's Easy Rooting Toolkit either.
*bump*
Right down all info on boot loader, you seem to know what to do but you're missing something, possibly need to change radio as gfree will not work with newer ones
Sent from my Nexus 7 using xda premium
FYI: Was able to root it finally by upgrading my stock to gingerbread from froyo; then back down to non-stock froyo followed by upgrade to modded Jelly Bean.