The following errors occurred with your submission:
leather.face has chosen not to receive private messages or may not be allowed to receive private messages. Therefore you may not send your message to him/her.
If you are trying to send this message to multiple recipients, remove leather.face from the recipient list and send the message again.
Click to expand...
Click to collapse
Nice to see you again :highfive:, do you have new device? did you sell desire c?
I tried extracting boot.img through kitchen,winrar,ext2explore but none of them work.
Sorry.
einstein.frat said:
Nice to see you again :highfive:, do you have new device? did you sell desire c?
I tried extracting boot.img through kitchen,winrar,ext2explore but none of them work.
Sorry.
Click to expand...
Click to collapse
Sounds like he is just having a paddy... xd ^__^ cant you just use adb to pull the boot image... unless the boot.img is in a zip file not on the phone?
He pm asking to modify a 11mb boot.img from razr to add init.d support, problem is it's unreadable by tools unlike htc 3.5 mb can be decompiled by kitchen boot tools
Related
Since we have rooted it now SPL seems to be useless.
----
Well, this is the original SPL image on Tattoo, nothing related to update.zip.
----
I was trying to reverse it, and just found why it refuses to erase, but I could not find why it refuses to download data from the host.
----
By now, to flash SPL or the first splash, you need a custom kernel with additional partition information and then use flash_image is OK.
tewilove said:
Since we have rooted it now SPL seems to be useless.
Click to expand...
Click to collapse
useless !! nope defo not, thanks for the input..
are you new here or regular user with new I.D. ??
..
definitely tewilove ; i loved this since long time.... is it correct that i rename it as update.zip & boot into recovery, then apply update.zip ???
one more question : will it change my baseband version from G to H ?, which is non 3G to 3G firmware...
i am dying here someone would come up with this innovative upload. thanks tewilove for this wonderful upload....
@tewilove, ur zip file is not signed.... when i tried updating it in recovery mode, it says verification failed, no signature....
what to do buddy ?
manuvaidya said:
@tewilove, ur zip file is not signed.... when i tried updating it in recovery mode, it says verification failed, no signature....
what to do buddy ?
Click to expand...
Click to collapse
sign it urself using testsign.jar
svprm said:
sign it urself using testsign.jar
Click to expand...
Click to collapse
how do i do it ??? little brief explanation would have been much better rather than telling me do it myself right ???
I have a dead Tattoo.. stucked in tattoo logo at the boot... it's possible to use this spl for heal?
Lox_Dev said:
Original post:
Now you are going to sign the zip file. Download attached testsign.zip and copy it in your <SDK>/tools folder. Extract it here. It should create a sign subfolder with a testsign.jar file in it.
Then, from <workdir> folder, do:
java -classpath <SDK>/tools/sign/testsign.jar" testsign file.zip file-signed.zip
Ok, now your zip file is ready to be deployed using cyanogen recovery image.
Click to expand...
Click to collapse
Test Jar:http://forum.xda-developers.com/attachment.php?attachmentid=220533&d=1251207154
after i signed the file and try to flash i get the following message:
E:Can't find update script
Any ideas?
svprm said:
Test Jar:http://forum.xda-developers.com/attachment.php?attachmentid=220533&d=1251207154
Click to expand...
Click to collapse
i am sorry. i couldnt succeed in signing it with testsign.jar file u uploaded....
could u please do it for me... just a favour. i think i am missing out some important step whicch i couldnt figure it out.... please test sign it & upload it here.....
moved to here
First, i nice ask somebody, if can give decription code for http://fus.samsungmobile.com/Phone_Binary/9/GT-I9000_I9000XFJM3_I9000OXFJM1_I9000XXJM1_I9000XFJM3_XF_VIP.zip.enc
It is for product code GT-I9000HKDVIP (croatian VIPnet).It is URGENT for me.
Second:
Have anywhere some Windows apps (not checkFus.apk on our device, give not right decription codes) wich can search decription code, and unpack it on to normal zip or tar files for flashing with Odin.
Thanks
Regards
The code: 18392010 provided by CheckFus.apk did actually work, and here is a dl-link. I will remove it tomorrow though.
LuffarJoh said:
The code: 18392010 provided by CheckFus.apk did actually work, and here is a dl-link. I will remove it tomorrow though.
Click to expand...
Click to collapse
Your dl link is not valid.... And with wich application i can .zip.enc unpacked in usually .zip format ??? With rar, zip, 7-zip dont go...
Regards and forwarding thanks on answer.
Hi, sorry about the bad link, it have been fixed now.
Take a look here on how to decrypt to get a valid zip-file.
Hi,
I need to change default contact pictures. Its for our customer who finds the green droid infinitely iritating . Anyway, I rooted the Desire HD and did s-off, Clockwork recovery is in place. Bud I didnt find any themes or even adress where those pictures are in the phone.
I will be happy for any advice what image to create, how big, format etc...
And ofcouse where to flash it.
Update:
Actually, no one solved it, i found numerous questions about this and no definitive answer. So any pro here who wants to get extra thanks ?
This is my exact wish!
Fullscreencaller works as windows... unusable
I know where the Dancing Android lives
You need 7zip installed and your chosen ROM saved on your PC.
Right click on ROM and choose
7zip>Open Archive (don't just double click to open it)
Now browse to:
\system\app\
Right click on Phone.apk and choose:
Open
Now browse to:
\res\drawable-hdpi\
Extract the folder so you can view them all as thumbnails. Then you will see 4 files called:
phone_default_270.PNG
phone_default_300.PNG
phone_default_incall_270.PNG
phone_default_incall_300.PNG
There are other contact pictures in there too, as it's the dialler so just have a look and see what you want to change.
Now, for the contact picture that appears in your contact list in HTC People, follow the same as above but go to:
\system\app\HtcContacts.apk\res\drawable-hdpi\
Then look for:
people_home_defaultphoto.PNG
It might also be worth a look in:
\system\framework\framework-res.apk\res\drawable-hdpi\
Now for the disclaimer:
This is all at your own risk. I'm not sure what limitations / consequences there are for modifying these files as I have only used this method to swap icons from other ROMs into my own. You might need some kind of special editor for the PNGs, but at least you now know where to look
@sviftcz: If you need help with creating a flashable zip, you could upload your Phone.apk and the pictures you want and I'll make one for you.
sigurd_LU said:
@sviftcz: If you need help with creating a flashable zip, you could upload your Phone.apk and the pictures you want and I'll make one for you.
Click to expand...
Click to collapse
What are the missing steps from my post above? I'm keen to do this myself now we're speaking about it!
Do the pngs have to be saved a specific way or is it simply a case of creating a file with the same dimensions and swapping them over? As I said, I've only ever swapped over files that were from one ROM into another rather than adding in files I've created myself.
Thanks
Your guide is awesome! But it misses the steps how you get it on your phone
You'll have to take your original phone.apk, open it with winrar or 7zip (don't extract, just open it), and drag and drop your edited images from the previously extracted apk in the right folders.
When you're done, exit winrar/7zip and put the phone.apk into system/app of this flashable update zip: http://www.multiupload.com/THCTLMRDBU
And that's it. If you want more details or if I didn't explain it well, just tell me.
Haha, yeah... I forgot to say that I do it before I flash the ROM!
Using your flashable zip is way easier though.
The only other thing is, do you have to save the PNGs with specific settings, other than them being the same size obviously?
Cheers
CitizenLee said:
Haha, yeah... I forgot to say that I do it before I flash the ROM!
Click to expand...
Click to collapse
Okay
The color depth (expressed in bits) doesn't matter as long as the png has the right dimensions, as you said.
btw, I didn't make this zip, it's from he_stheone64.
IS there any temporary rooting available for the new version of Desire HD?
I dont want to update any FW, nor root image. Thanks the help!
Okay. So I found out where all the problems are. I also did fix the two things in the boot.img ramdisk. But I am not being able to decompile the framework-res.apk in which the storage_list.xml needs to be edited. Maybe since it's API 22.
Booting the modified boot.img without editing the framework-res.apk gives a bootloop. Rather it completes boot and gets stuck after the word android disappears. Rebooting makes it enter a bootloop.
Please see if you can decompile the framework-res.apk from the lollipop backup and reply. Thank you.
I am also attaching the new boot.img if anybody needs it. But do NOT flash.
CosmoDroid said:
Okay. So I found out where all the problems are. I also did fix the two things in the boot.img ramdisk. But I am not being able to decompile the framework-res.apk in which the storage_list.xml needs to be edited. Maybe since it's API 22.
Booting the modified boot.img without editing the framework-res.apk gives a bootloop. Rather it completes boot and gets stuck after the word android disappears. Rebooting makes it enter a bootloop.
Please see if you can decompile the framework-res.apk from the lollipop backup and reply. Thank you.
I am also attaching the new boot.img if anybody needs it. But do NOT flash.
Click to expand...
Click to collapse
Which process or tool did u use for decompiling sir??
kumar akarsh said:
Which process or tool did u use for decompiling sir??
Click to expand...
Click to collapse
Apktool and its derivatives.
CosmoDroid said:
Apktool and its derivatives.
Click to expand...
Click to collapse
OK sir, I'll try n let u know..
CosmoDroid said:
Okay. So I found out where all the problems are. I also did fix the two things in the boot.img ramdisk. But I am not being able to decompile the framework-res.apk in which the storage_list.xml needs to be edited. Maybe since it's API 22.
Booting the modified boot.img without editing the framework-res.apk gives a bootloop. Rather it completes boot and gets stuck after the word android disappears. Rebooting makes it enter a bootloop.
Please see if you can decompile the framework-res.apk from the lollipop backup and reply. Thank you.
I am also attaching the new boot.img if anybody needs it. But do NOT flash.
Click to expand...
Click to collapse
hey is it possible if we can anyhow, partition our 4gb rom to work as a internal storage?
Androidoo said:
hey is it possible if we can anyhow, partition our 4gb rom to work as a internal storage?
Click to expand...
Click to collapse
It is mounted like that only in the 5.1 backup rom. But you'd only get about 2.33GB of internal storage as the rest is used by the other system partitions. Also you won't be able to move apps to the external sd card. IMO 2.33GB is too little as most apps store their data on the primary storage partition.
CosmoDroid said:
It is mounted like that only in the 5.1 backup rom. But you'd only get about 2.33GB of internal storage as the rest is used by the other system partitions. Also you won't be able to move apps to the external sd card. IMO 2.33GB is too little as most apps store their data on the primary storage partition.
Click to expand...
Click to collapse
ok but as in the 8 gb rom, some part of the rom goes for the primary internal storage, to store app data. and coz of that same thing is happening to our devices in 4gb rom, so i was thinking if there could be way, by which we can make our sd card, to be read as the primary internal storage. I owned an ace plus, and we have done such things there so if its possible here too otherwise we could better wait for ota and the new sources
SD Card issue.
Guys I flashed it but when I opened file manager I couldn't access my SD card. It just showed the name SD Card but actually it was the internal storage. But when I connected to PC I could see both storages displayed. Usually it doesn't show internal storage on PC. Also another issue is I couldn't sideload any apps at all. It just kept giving the "Package installer has stopped" message.
Androidoo said:
ok but as in the 8 gb rom, some part of the rom goes for the primary internal storage, to store app data. and coz of that same thing is happening to our devices in 4gb rom, so i was thinking if there could be way, by which we can make our sd card, to be read as the primary internal storage. I owned an ace plus, and we have done such things there so if its possible here too otherwise we could better wait for ota and the new sources
Click to expand...
Click to collapse
Swapping the external sd as internal storage would only be possible after someone can decompile the framework-res.apk because vold.fstab isn't used anymore from 4.3 I guess.
whiplash1 said:
Guys I flashed it but when I opened file manager I couldn't access my SD card. It just showed the name SD Card but actually it was the internal storage. But when I connected to PC I could see both storages displayed. Usually it doesn't show internal storage on PC. Also another issue is I couldn't sideload any apps at all. It just kept giving the "Package installer has stopped" message.
Click to expand...
Click to collapse
Can't you read the OP? I did clearly mention not to flash the attached boot.img.
CosmoDroid said:
Swapping the external sd as internal storage would only be possible after someone can decompile the framework-res.apk because vold.fstab isn't used anymore from 4.3 I guess.
Can't you read the OP? I did clearly mention not to flash the attached boot.img.
Click to expand...
Click to collapse
I mean I flashed the actual ROM files. Not this decompiled one. But since you seem to have understood the problem, I posted in this thread.
CosmoDroid said:
Okay. So I found out where all the problems are. I also did fix the two things in the boot.img ramdisk. But I am not being able to decompile the framework-res.apk in which the storage_list.xml needs to be edited. Maybe since it's API 22.
Booting the modified boot.img without editing the framework-res.apk gives a bootloop. Rather it completes boot and gets stuck after the word android disappears. Rebooting makes it enter a bootloop.
Please see if you can decompile the framework-res.apk from the lollipop backup and reply. Thank you.
I am also attaching the new boot.img if anybody needs it. But do NOT flash.
Click to expand...
Click to collapse
What exactly do you mean by decompile?? Do you need the storage_list.xml file??
Is this what you want?
CosmoDroid said:
Okay. So I found out where all the problems are. I also did fix the two things in the boot.img ramdisk. But I am not being able to decompile the framework-res.apk in which the storage_list.xml needs to be edited. Maybe since it's API 22.
Booting the modified boot.img without editing the framework-res.apk gives a bootloop. Rather it completes boot and gets stuck after the word android disappears. Rebooting makes it enter a bootloop.
Please see if you can decompile the framework-res.apk from the lollipop backup and reply. Thank you.
I am also attaching the new boot.img if anybody needs it. But do NOT flash.
Click to expand...
Click to collapse
Will this help??
xdaaritra said:
Will this help??
Click to expand...
Click to collapse
Nope. You just used an archive manager and extracted the file. I need this file from the decompiled apk so that it is editable.
Oh now I get it.
CosmoDroid said:
Nope. You just used an archive manager and extracted the file. I need this file from the decompiled apk so that it is editable.
Click to expand...
Click to collapse
You need apktool to decompile it. But the current version doesn't support api 22. So I guess we'll just have to wait. Sorry I didn't knew that.
Already tried that still didn't fixed
Actually I did all that stuff since the indonesian backup came out. Actually people should together feedback them regarding adding the feature of apps to be moved to sd card so that they soon release OTA to fix that or wait for MyPhone UNO's backup to come then we will surely get that issue fixed.
Rohan Taneja said:
Actually I did all that stuff since the indonesian backup came out. Actually people should together feedback them regarding adding the feature of apps to be moved to sd card so that they soon release OTA to fix that or wait for MyPhone UNO's backup to come then we will surely get that issue fixed.
Click to expand...
Click to collapse
Did you fix the framework-res.apk? If yes how did you decompile it?
CosmoDroid said:
Did you fix the framework-res.apk? If yes how did you decompile it?
Click to expand...
Click to collapse
I used RC4. Which decompiled without any error but compilation was a problem.
You should try that on any linux, it simply works on that.
Rohan Taneja said:
I used RC4. Which decompiled without any error but compilation was a problem.
You should try that on any linux, it simply works on that.
Click to expand...
Click to collapse
I also used RC4 but it gave errors. I'll try later on a fresh linux installation.
porting rom from android one to other media tek
CosmoDroid said:
Okay. So I found out where all the problems are. I also did fix the two things in the boot.img ramdisk. But I am not being able to decompile the framework-res.apk in which the storage_list.xml needs to be edited. Maybe since it's API 22.
Booting the modified boot.img without editing the framework-res.apk gives a bootloop. Rather it completes boot and gets stuck after the word android disappears. Rebooting makes it enter a bootloop.
Please see if you can decompile the framework-res.apk from the lollipop backup and reply. Thank you.
I am also attaching the new boot.img if anybody needs it. But do NOT flash.
Click to expand...
Click to collapse
can you tell me how can i port boot.img from android one to other media tek devices ? i heard boot.img in android one is different from other media tek devices.
Need it for a Cricket 626s. It was never officially released by Cricket, so if anyone has a T-Mo or Metro ZIP, that would be wonderful.
The T-Mo/Metro RUU's didn't take.
I flashed the T-Mobile Debloated MM ROM from XDA on my Cricket 626s. I haven't encountered any big issues yet, but make sure you back up Lollipop in the event that you do.
IMPORTANT: Before you first boot up into MM, remove your SIM card. Do not insert it until the setup process is completely over. When you get to Self-Service, wait a while to bypass it.
jakesnot-hereman said:
I flashed the T-Mobile Debloated MM ROM from XDA on my Cricket 626s. I haven't encountered any big issues yet, but make sure you back up Lollipop in the event that you do.
IMPORTANT: Before you first boot up into MM, remove your SIM card. Do not insert it until the setup process is completely over. When you get to Self-Service, wait a while to bypass it.
Click to expand...
Click to collapse
Where can you download this?
technohunter123 said:
Where can you download this?
Click to expand...
Click to collapse
I misspoke; it's actually the Sprint ROM: https://forum.xda-developers.com/de...m-flashable-stock-htc-626s-debloated-t3293602
I forgot one step, though. There's a couple of lines in a single file that prevent this file from flashing.
To fix it:
Open the .zip file from Windows (Without extracting)
Navigate to /META-INF/com/google/android/
Open 'updater-script' with a good text editor
Delete the lines from 'assert' to the next semi-colon
Save, and let Windows recompile the .zip
This new file should flash without problem. If you have trouble doing this, say something, and I'll upload mine when I get home.
jakesnot-hereman said:
I misspoke; it's actually the Sprint ROM: https://forum.xda-developers.com/de...m-flashable-stock-htc-626s-debloated-t3293602
I forgot one step, though. There's a couple of lines in a single file that prevent this file from flashing.
To fix it:
Open the .zip file from Windows (Without extracting)
Navigate to /META-INF/com/google/android/
Open 'updater-script' with a good text editor
Delete the lines from 'assert' to the next semi-colon
Save, and let Windows recompile the .zip
This new file should flash without problem. If you have trouble doing this, say something, and I'll upload mine when I get home.
Click to expand...
Click to collapse
Thanks for helping out here. I just tried your suggestion, and when I flash from TWRP, I get the error:
"Updater process ended with ERROR: 6
Error installing zip file '/sdcard/TWRP/Sprint_Stock_MMDB_2.27.651.6.zip'"
embhorn said:
Thanks for helping out here. I just tried your suggestion, and when I flash from TWRP, I get the error:
"Updater process ended with ERROR: 6
Error installing zip file '/sdcard/TWRP/Sprint_Stock_MMDB_2.27.651.6.zip'"
Click to expand...
Click to collapse
Huh. Try this zip; I just flashed it successfully: https://drive.google.com/file/d/0B9O8izj2yw8iTWFnXzRWS20xaUk/view?usp=sharing
jakesnot-hereman said:
Huh. Try this zip; I just flashed it successfully: https://drive.google.com/file/d/0B9O8izj2yw8iTWFnXzRWS20xaUk/view?usp=sharing
Click to expand...
Click to collapse
That did it! Thanks for your help getting the right ROM.
:good:
After installing the ROM, I followed these instructions for activating / setting up (since I got the error "Cannot contact Google servers" trying activate G account):
https://forum.xda-developers.com/showpost.php?p=69853901&postcount=281
Help
Help please my little brother attempted to root his metro pcs htc desire 626s and some how he accidently wiped the os on it will the file on the thread be a rom i could install to his phone using twrp?
gruiz487 said:
Help please my little brother attempted to root his metro pcs htc desire 626s and some how he accidently wiped the os on it will the file on the thread be a rom i could install to his phone using twrp?
Click to expand...
Click to collapse
You can use the zip that jakesnot-hereman posted in TWRP