Related
I made my phone image with ClockModRecovery.
And I got:
boot.img
cache.yaffs2.img
cache.yaffs2.img
recovery.img
system.yaffs2.img
.android_secure.vfat.tar
sd-ext.ext3.tar
Where I can find Camera.apk?
I tried to find without success...
It should be inside system. Yaffs or sd-ext depending on if you use an a2sd script. You'll have to unpack it somehow.
Btw, why do you need it. It should be delivered with your rom.
Gesendet von meinem Desire mit Tapatalk
I extracted all img and tar
except boot.img and recovery.img because cannot open
and searched in all extracted files and cannot find camera.apk
I found:
s.system.app.HTCCamera.apk
(this is looks like original camera but this is cache
\data\com.estrongs.android.pop\cache\.apps)
s.sdcard.HDR_Camera_v2.0[szoheb].apk
s.sdcard.backups.apps.Paper Camera-17.apk
I am not sure what you mean by that first apk. But if it is from system/apps it should be the original one.
Could you explain more detailed what you mean by it looks like but isn't?
Gesendet von meinem Desire mit Tapatalk
I cannot open this file, and file size is 4,6KB
I downloaded factory image from code.google.com,and I extracted a file who name is system.img,but I don't know how can I unpack it.
I don't know unpack it with what software,Is not always able to unpack the file when I
tried some softwares.(yaffs2img,winimage,winRAR and something else)
what is a right way to extract and edit it?
Thank you!
you don't extract .img files.... you flash the img file through fastboot.
google on how to use fastboot for more details.
You can extract them just fine. I used dsixda's kitchen to extract system.img so that I could pull the gapps.
zephiK said:
you don't extract .img files.... you flash the img file through fastboot.
google on how to use fastboot for more details.
Click to expand...
Click to collapse
I just want make it into zip file and flash it with recovery,facilitate I edit a rom.
zephiK said:
you don't extract .img files.... you flash the img file through fastboot.
google on how to use fastboot for more details.
Click to expand...
Click to collapse
mwalt2 said:
You can extract them just fine. I used dsixda's kitchen to extract system.img so that I could pull the gapps.
Click to expand...
Click to collapse
Dsixda's kitchen? Can it unpack the system.img? Actually,I want delete some gapps and edit this rom.
8723045587230455 said:
Dsixda's kitchen? Can it unpack the system.img? Actually,I want delete some gapps and edit this rom.
Click to expand...
Click to collapse
Yes, it works ok. Just put the system.img in the original update and choose to make a rom from that file. It will guide you through extracting the system.img. You might be able to get it to build the entire rom if you just zip all of the .img's together and choose that for the input file.
Thank you so much and I'll try. ^^
You can use http://forum.xda-developers.com/showpost.php?p=15333542& postcount=135 to convert the image to an .ext4.img and then use http://www.diskinternals.com/linux-reader/ to mount (if you are using Windows).
Sent from my Galaxy Nexus using Tapatalk
efrant said:
You can use http://forum.xda-developers.com/showpost.php?p=15333542& postcount=135 to convert the image to an .ext4.img and then use http://www.diskinternals.com/linux-reader/ to mount (if you are using Windows).
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I'm glad i found your post on here. Greatly appreciate it! :victory:
I want to use odin to install the original 4.0.4 version but it still fails because the file that downloads images from Google is factory extension .Tgz can tell me how to do it by odin? I downloaded a. Tar site that supposedly works and my I get the following error. Thanks in advance and sorry for the translation made by google.
Why don't you just flash it through fastboot? Or use a program like 7-Zip and extract it to it's TAR extension.
sebora said:
I want to use odin to install the original 4.0.4 version but it still fails because the file that downloads images from Google is factory extension .Tgz can tell me how to do it by odin? I downloaded a. Tar site that supposedly works and my I get the following error. Thanks in advance and sorry for the translation made by google.
Click to expand...
Click to collapse
You need to load the tar file through PDA not phone...
Sent from my Galaxy Nexus using XDA App
miketoasty said:
Why don't you just flash it through fastboot? Or use a program like 7-Zip and extract it to it's TAR extension.
Click to expand...
Click to collapse
As I make it? of. tgz to. tar as to decompress the. tgz 1 zip and decompress multiple files.
Como lo convierto? de .tgz a .tar ya que al descomprimir el .tgz se descomprimen 1 zip y varios archivos.
bigwillis said:
You need to load the tar file through PDA not phone...
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
What do you mean? If I can explain. Thank you.
sebora said:
As I make it? of. tgz to. tar as to decompress the. tgz 1 zip and decompress multiple files.
Como lo convierto? de .tgz a .tar ya que al descomprimir el .tgz se descomprimen 1 zip y varios archivos.
Click to expand...
Click to collapse
Install 7-zip. Right click on the .tgz file, and from the menu select 7-zip>Extract files. You'll end up with a single .tar file which goes in PDA.
I recommend Fastboot however as it's the best way to flash the Nexus with factory images, etc...
CMNein said:
Install 7-zip. Right click on the .tgz file, and from the menu select 7-zip>Extract files. You'll end up with a single .tar file which goes in PDA.
I recommend Fastboot however as it's the best way to flash the Nexus with factory images, etc...
Click to expand...
Click to collapse
tomorrow i try. And say its ok or not. Thanx
The only thing flashed through phone is modems ....ie basebands ....kernels and roms etc go into the pda slot ....
Sent from my SPH-D710 using Tapatalk 2
CMNein said:
Install 7-zip. Right click on the .tgz file, and from the menu select 7-zip>Extract files. You'll end up with a single .tar file which goes in PDA.
I recommend Fastboot however as it's the best way to flash the Nexus with factory images, etc...
Click to expand...
Click to collapse
The solution was perfect, it turns out to unzip a file using Winrar. Zip and. Tar and 7zip is solved, thank you very much to all and sorry for the inconvenience of a novice.
Greetings and THX TO ALL for reply
I think ODIN is ****, and even more so for the Galaxy Nexus. Fastboot is the best way to flash files to the Gnex.
Hi, other problem, files .sig not found?
Odin is still in operation although the extension is. Tar gives me the same error I posted above to see if someone gives me a solution...
Hi,
after my Ouya had been soft-bricked because i didnt accept the new TOS i am trying to get it alive again. After tinkering with "/system/build.prob" and installing 2 new launchers the Fouya comes up with black screen and takes very long until i can access it with "adb". Luckily this still does work.
I did just change the update url in /system/build.prob, nothing more.
Anyone has tips on what to check and how to get the package manager working again?
The exact "adb" error is "Error: Could not access the Package Manager. Is the system running?"
thx,
Tycho
What about recovery? Are you able to enter and Flash stock/custom rom?
But first you might want to Check your build.prop for errors:
Did you mache enter a spaces in last line/ at the end of one line?
Did you push build.prop via adb and forgot to give it the right permissions?
Gesendet von meinem One X+ mit Tapatalk-4
Hi and thx for answering,
nchantmnt said:
What about recovery? Are you able to enter and Flash stock/custom rom?
Click to expand...
Click to collapse
i can boot cwmrecovery via fastboot but it wont boot from the recovery partition. Also i did use "dd" to write the recovery image. I also get sometimes the pink cwm screen and its only using the left half of my monitor.
But first you might want to Check your build.prop for errors:
Did you mache enter a spaces in last line/ at the end of one line?
Click to expand...
Click to collapse
thx, i will check this. As i cant use my old Ubuntu 11.10 i am using windows atm. and edit with notepad++.
There must be no spaces at the end of line then i guess? I think i restore the backup props file and then go from there.
Did you push build.prop via adb and forgot to give it the right permissions?
Click to expand...
Click to collapse
i forgot to memorize the access rights and then set it to 777.
cheers,
Tycho
Should be 644 and dont forget to mount r/w System
Gesendet von meinem One X+ mit Tapatalk-4
So you are able to restore stock or custom rom and even push stock build.prop via adb? What exactly do you need us to tell you then?
If cwm is corrupted try ob another monitor/TV. If recovery doesn't show up hit the windows button on your keyboard a couple of times, this should bring up cwm screen again.
Gesendet von meinem One X+ mit Tapatalk-4
nchantmnt said:
So you are able to restore stock or custom rom and even push stock build.prop via adb?
Click to expand...
Click to collapse
I can access my Ouyas via adb and i can write the recovery flash, which i did several times, but i cant boot to whatever reasons from the recovery partition. Maybe its an issue with the USB keyboard.
What exactly do you need us to tell you then?
Click to expand...
Click to collapse
I needed to know to get the boot process unstuck. Thanx to you its working again. It hab been the wrong access permissions of the build.prop file which did prevent the box from booting into a launcher. After setting "chmod 644" again, like you suggested, everything works again and now my Ouya is alive and kickin with a Nova Launcher and the exposed. I am working on getting cifs/nfs working atm.
Again, thx for the help.
// Tycho
Hello,
Does this ROM support helium devices? Does anyone use it? On the hardware side, the helium hardware is also shown. (Snapdragon 652) I wanted to communicate with the maintainer, but i do not speak Chinese Can you help me with this?
https://download.mokeedev.com/?device=hydrogen
Yes u can install it in helium and I am replying from this ROM only.
svvv said:
Yes u can install it in helium and I am replying from this ROM only.
Click to expand...
Click to collapse
What about CPU one of them 650 and the other 652, my device may become unusable!
Just 2 extra cores in 652...apart from that both are same. So if u flash hydrogen rom in helium 2 cores will be always offline that's it...no other difference.
To enable 2 cores in hydrogen... just need to do small change in the boot.img
svvv said:
Just 2 extra cores in 652...apart from that both are same. So if u flash hydrogen rom in helium 2 cores will be always offline that's it...no other difference.
To enable 2 cores in hydrogen... just need to do small change in the boot.img
Click to expand...
Click to collapse
hi , do you know how enable the 2 cores? how change the boot.img?
ikaros80 said:
hi , do you know how enable the 2 cores? how change the boot.img?
Click to expand...
Click to collapse
You have to copy this file from helium boot.img "init.qcom.power.rc" . Use any boot image unpack/pack tool. Get the file from helium boot.img.
Unpack hydrogen boot.img and replace it and pack it. u can replace the kernel with the new one and flash it which will enable all the cores.
svvv said:
Just 2 extra cores in 652...apart from that both are same. So if u flash hydrogen rom in helium 2 cores will be always offline that's it...no other difference.
To enable 2 cores in hydrogen... just need to do small change in the boot.img
Click to expand...
Click to collapse
svvv said:
You have to copy this file from helium boot.img "init.qcom.power.rc" . Use any boot image unpack/pack tool. Get the file from helium boot.img.
Unpack hydrogen boot.img and replace it and pack it. u can replace the kernel with the new one and flash it which will enable all the cores.
Click to expand...
Click to collapse
do you know any link for kernel?
ikaros80 said:
do you know any link for kernel?
Click to expand...
Click to collapse
Use the same boot.img from mokee rom. I have attached init.qcom.power.rc here use it.
Also attached the modified boot.img file which I am using in helium for mokee. If u want u can directly flash the file from twrp image flash.View attachment init.qcom.power.rc.zip
View attachment image-new.img.zip
svvv said:
Use the same boot.img from mokee rom. I have attached init.qcom.power.rc here use it.
Also attached the modified boot.img file which I am using in helium for mokee. If u want u can directly flash the file from twrp image flash.View attachment 4132124
View attachment 4132126
Click to expand...
Click to collapse
must flash the 2 filies?
ikaros80 said:
must flash the 2 filies?
Click to expand...
Click to collapse
I have given this file init.qcom.power.rc so that if u want to flash any hydrogen rom in helium u can replace this file in boot.img to enable all cores.
The boot.img is already been modified with the above file u can just flash this file alone for mokee rom.
svvv said:
I have given this file init.qcom.power.rc so that if u want to flash any hydrogen rom in helium u can replace this file in boot.img to enable all cores.
The boot.img is already been modified with the above file u can just flash this file alone for mokee rom.
Click to expand...
Click to collapse
i just try to flash this MK71.2-hydrogen-201704290936-NIGHTLY.zip , but say is not for your model helium
ikaros80 said:
i just try to flash this MK71.2-hydrogen-201704290936-NIGHTLY.zip , but say is not for your model helium
Click to expand...
Click to collapse
Unzip the file...modify these lines in updater-script
Ro.product.device="helium"
Ro.build.product="helium"
Save and zip the files again and flash it
svvv said:
Unzip the file...modify these lines in updater-script
Ro.product.device="helium"
Ro.build.product="helium"
Save and zip the files again and flash it
Click to expand...
Click to collapse
i unzip the file, change the lines in this file, then zip again but the problem is the first zip before unzip is 425mb and the sexond after zip again 375mb
ikaros80 said:
i unzip the file, change the lines in this file, then zip again but the problem is the first zip before unzip is 425mb and the sexond after zip again 375mb
Click to expand...
Click to collapse
That's fine...you can flash it
You don´t need unzip the rom, just open zip with 7zip, extract updater-script file, delete original from zip, make a copy of original (just in case), edit the above mentioned lines with Notepadd++ and then put your edited file in the zip, just close your zip again
the same nightly work out of the box for my helium. Though it slowly removed the content of my memory card, all of my backups/music/photos is gone bit by bit and it had to reboot like 3 or 4 times at the first initial boot.