Related
Hello everyone,
Can someone please inform and post a thread link of a battery mod that works on the i9001? By battery mod I mean small zip file that is installed from recovery and changes the stock battery meter
You can make it yourselt.
1. Use Root Explorer to get your framework-res.apk file
2. Go to http://uot.dakra.lt/ to customize it yourselt.
3. Go to http://forum.xda-developers.com/showthread.php?t=1253707 to download the Root-i9001-Signed.zip
4. Put the modified framework-res.apk in the above zip file and delete the unneeded files.
5. Update the updater-script file, resign the zip file.
6. Flash the zip file in recovery.
Do you like this one?
quest221 said:
You can make it yourselt.
1. Use Root Explorer to get your framework-res.apk file
2. Go to http://uot.dakra.lt/ to customize it yourselt.
3. Go to http://forum.xda-developers.com/showthread.php?t=1253707 to download the Root-i9001-Signed.zip
4. Put the modified framework-res.apk in the above zip file and delete the unneeded files.
5. Update the updater-script file, resign the zip file.
6. Flash the zip file in recovery.
Do you like this one?
Click to expand...
Click to collapse
If you use manveru0's kernal and recovery you can now flash the update files as they come from the kitchen
quest221 said:
You can make it yourselt.
1. Use Root Explorer to get your framework-res.apk file
2. Go to http://uot.dakra.lt/ to customize it yourselt.
3. Go to http://forum.xda-developers.com/showthread.php?t=1253707 to download the Root-i9001-Signed.zip
4. Put the modified framework-res.apk in the above zip file and delete the unneeded files.
5. Update the updater-script file, resign the zip file.
6. Flash the zip file in recovery.
Do you like this one?
Click to expand...
Click to collapse
Hmm... yes, nice, but I'm not in to designing things. I was looking for something that has been already created
what's the version of your Rom?
quest221 said:
what's the version of your Rom?
Click to expand...
Click to collapse
Firmware version : 2.3.4
baseband version I9001XXKP4
Kernel Version : [email protected] #7
Build Number : GINGERBREAD.XXKP4
I use Go launcher (from my opinion it's the best), if you think otherwise please post the better launcher, I am opened to experiment others.
Many thanks,
Ciprian
I don't have a I9001XXKP4 Rom in my hard drive. If you can send your your framework-res.apk, I can make one for you.
quest221 said:
I don't have a I9001XXKP4 Rom in my hard drive. If you can send your your framework-res.apk, I can make one for you.
Click to expand...
Click to collapse
I would like something like http://img225.imageshack.us/img225/9943/smoothbatt.png if it is possible.
I have attached framework-res.apk
opps a
hey guys!
just used this. twice great kitchen, really revamped some of the more boring icons on stock roms. thanks for the tip!!
1framework-res_I9001XXKP4_signed.zip is the file that I updated the updater-script so you can flash it in the in-build recovery.
1framework-res_I9001XXKP4_original_signed.zip is your original file. If there are any issues, you can flash it back in the in-build recovery.
How to:
Copy the zip file to the internal SD card, not the external one, go to recovery, flash it.
quest221 said:
1framework-res_I9001XXKP4_signed.zip is the file that I updated the updater-script so you can flash it in the in-build recovery.
1framework-res_I9001XXKP4_original_signed.zip is your original file. If there are any issues, you can flash it back in the in-build recovery.
How to:
Copy the zip file to the internal SD card, not the external one, go to recovery, flash it.
Click to expand...
Click to collapse
Thanks, exactly what I needed. I flashed it and all is ok
quest221 said:
1framework-res_I9001XXKP4_signed.zip is the file that I updated the updater-script so you can flash it in the in-build recovery.
1framework-res_I9001XXKP4_original_signed.zip is your original file. If there are any issues, you can flash it back in the in-build recovery.
How to:
Copy the zip file to the internal SD card, not the external one, go to recovery, flash it.
Click to expand...
Click to collapse
can i use it on 2.3.6 rom?
nope because you will end up in a bootloop by flashing this
its only for XXKP4
urm, Ive tried to do as you told in post number 2(by cooking it according to my own preference)
but my problem starts from step number 5
5. Update the updater-script file, resign the zip file.
Click to expand...
Click to collapse
I already received the cooked file
but I dont know how to change the update script and end up failing to update using the zip file.
can you please help me?
or link me to a place that really can help me to learn better on changing the update script.
try this one, I updated the updater-script, you can compare it with the one from kitchen.
PS: Forgot to update the update-binary file, now try the new one. It should work.
Thanks!!!! But I got an error that states
E:error in /tmp/sideload/package.zip
(status 2)
I wonder whats wrong.
looked in a thread
http://forum.xda-developers.com/showthread.php?t=1194245&page=3
and from what I understand it seems to be a problem with the update binary. But Im just an end user and this is too much for me.
anyway maybe Ill try to flash the cranium ROM and try to cook again a new one and use your update script.
cheers!!
Hi,
Is there any posibility to change framework-res.apk file without CWM? I don't want to instal CWM becouse of it has a problem with front side cam and I need this cam. It's can't be overwritten when the phone works. Maybe some adb and push command is possible.
Could you help me by describing the whole procedure? Sorry for my English.
@quest221
Can you maybe make one for Android 2.3.5 like the screenshot @ page 1?
I have baseband I9001XXKPF, Build XXKPG
I update the zip file with the new update-binary file.
Is there any posibility to change framework-res.apk file without CWM?
Click to expand...
Click to collapse
Yes, I just use the recovery from Samsung, not the third-party.
Check the post #2, that's the steps. Also replace the update-binary file with the one in my zip file.
Can you maybe make one for Android 2.3.5 like the screenshot @ page 1?
Click to expand...
Click to collapse
Upload your framework-res.apk file.
Hi!
Since xda-univeristy arised i thought it would be nice to learn something about green droid
I am going to learn about tweaking and theming:and here comes dozens of my questions:
1. I have downloaded Official ics repack by N00BY0815
2. I extracted it and i have:
2 folders ( META-INF and System)
2 files boot.ing and system.img
How can i extract this system.img ?
I tried to use 7zip but it says that" it cannot open it as archive"
Thanks in advance and please for leniency
it can be opened with Diskinternals Linux Reader. if not. use "sgs2toext4.jar" to convert it to .img.ext4 and then open it
Nihiliu said:
Hi!
Since xda-univeristy arised i thought it would be nice to learn something about green droid
I am going to learn about tweaking and theming:and here comes dozens of my questions:
1. I have downloaded Official ics repack by N00BY0815
2. I extracted it and i have:
2 folders ( META-INF and System)
2 files boot.ing and system.img
How can i extract this system.img ?
I tried to use 7zip but it says that" it cannot open it as archive"
Thanks in advance and please for leniency
Click to expand...
Click to collapse
Everything for theming is in the System folder. All the APK's(Applications) Boot.img is probably the recovery image it installs. But to theme you would need to decompile the apks in the system folder
Everythink was in system folder in gingerbread, in this system folder i have only app folder with su.apk and bin folder with su file.
So files i need are in system.img
@broodplank1337 thanks for help, program works well, now i can begin
But first only one question, now i can extract files, but can i pack them using same tool ?
Nihiliu said:
Everythink was in system folder in gingerbread, in this system folder i have only app folder with su.apk and bin folder with su file.
So files i need are in system.img
@broodplank1337 thanks for help, program works well, now i can begin
But first only one question, now i can extract files, but can i pack them using same tool ?
Click to expand...
Click to collapse
I don't know much about S2 but can't you just use 7zip to make it an archive and flash it through rrecovery?
"Anger and intolerance are the enemies of correct understanding." -Mahatma Gandhi
Nihiliu said:
How can i extract this system.img ?
Click to expand...
Click to collapse
Hi. You can use dsixda's Android Kitchen for that.
Nihiliu said:
Everythink was in system folder in gingerbread, in this system folder i have only app folder with su.apk and bin folder with su file.
So files i need are in system.img
@broodplank1337 thanks for help, program works well, now i can begin
But first only one question, now i can extract files, but can i pack them using same tool ?
Click to expand...
Click to collapse
You can pack them with the android kitchen, install the zip, then you do this in terminal emulator to make the system.img file:
Code:
su
cat proc/mounts
now look up the system partition, in my case it's mmcblk0p14
Code:
dd if=/dev/block/mmcblk0p14 of=/sdcard/system.img BS=4096
This will dump the system partition to system.img (for example when making an odin image)
Been looking around and I cannot get info(or I may have missed it) on how to convert system.sin to system.img.
The reason I want the system.img is I'd like to try deodexing my own JB(HKversion) stock rom.
how can I manage it in dsixda's kitchen, it says I need a system.img or either one of the following:
The format for each ROM must be one of the following:
- system.img + optional boot.img/lib.img (e.g. stock ROM or Nandroid)
- ZIP file for a custom ROM (e.g. update.zip)
- ZIP file containing *.img (e.g. stock rom.zip)
- ZIP file containing shipped ROM in SYSTEM + BOOT folder format
- Working folder made with this kitchen (e.g. WORKING_old_rom)
What I've already done so far was pulled out the system.sin from an FTF and made it system.ext4 in flashtool. And I also have extracted all the system files but I don't know how to go from here LoL.
Thanks in advance for any inputs guys.
Rycon33 said:
Been looking around and I cannot get info(or I may have missed it) on how to convert system.sin to system.img.
The reason I want the system.img is I'd like to try deodexing my own JB(HKversion) stock rom.
how can I manage it in dsixda's kitchen, it says I need a system.img or either one of the following:
The format for each ROM must be one of the following:
- system.img + optional boot.img/lib.img (e.g. stock ROM or Nandroid)
- ZIP file for a custom ROM (e.g. update.zip)
- ZIP file containing *.img (e.g. stock rom.zip)
- ZIP file containing shipped ROM in SYSTEM + BOOT folder format
- Working folder made with this kitchen (e.g. WORKING_old_rom)
What I've already done so far was pulled out the system.sin from an FTF and made it system.ext4 in flashtool. And I also have extracted all the system files but I don't know how to go from here LoL.
Thanks in advance for any inputs guys.
Click to expand...
Click to collapse
Just rename it.
That works if you want to use system.sin in dsixdas kitchen to make your own rom.
The instructions say to rename system.sin to system.img
PS, in fact you can just use system.sin, check in the first post for supported devices, it tlks about what to do for sony phones
gregbradley said:
Just rename it.
That works if you want to use system.sin in dsixdas kitchen to make your own rom.
The instructions say to rename system.sin to system.img
PS, in fact you can just use system.sin, check in the first post for supported devices, it tlks about what to do for sony phones
Click to expand...
Click to collapse
- If using stock FTF for kitchen:
1) Unzip FTF file, extract the system.sin
2) Dump system image from system.sin w/ Flashtool
(Advanced-> SIN Editor)
3) Rename dumped file to system.img
mate, I tried renaming it and put it on "original_update" folder but still the file cannot be detected I still cannot create a working folder and says
CREATE WORKING FOLDER FOR ROM
==============================
Ensure there is at least one ROM under the 'original_update' folder!
Select an option:
s - Show supported formats
x - Abort, don't create working folder
Or press Enter to continue
?
I also tried renaming the flashtool's dumped data(system.ext4) to system.img but still to no avail.
Any other way aside from system.img thing?
Rycon33 said:
- If using stock FTF for kitchen:
1) Unzip FTF file, extract the system.sin
2) Dump system image from system.sin w/ Flashtool
(Advanced-> SIN Editor)
3) Rename dumped file to system.img
mate, I tried renaming it and put it on "original_update" folder but still the file cannot be detected I still cannot create a working folder and says
CREATE WORKING FOLDER FOR ROM
==============================
Ensure there is at least one ROM under the 'original_update' folder!
Select an option:
s - Show supported formats
x - Abort, don't create working folder
Or press Enter to continue
?
I also tried renaming the flashtool's dumped data(system.ext4) to system.img but still to no avail.
Any other way aside from system.img thing?
Click to expand...
Click to collapse
wait, let me boot into linux and I will check
gregbradley said:
wait, let me boot into linux and I will check
Click to expand...
Click to collapse
mate, btw I'm only using cygwin in win7 if that matters on my issue
Rycon33 said:
mate, btw I'm only using cygwin in win7 if that matters on my issue
Click to expand...
Click to collapse
No, it doesnt matter, I did it with that setup, but its much easier with a ubuntu dual boot.
What you did should work.
Extract system.sin
Dump it with flash tool to get system.ext4, rename to system.img and put in original input folder.
then choose create working folder....
try it again,
gregbradley said:
No, it doesnt matter, I did it with that setup, but its much easier with a ubuntu dual boot.
What you did should work.
Extract system.sin
Dump it with flash tool to get system.ext4, rename to system.img and put in original input folder.
then choose create working folder....
try it again,
Click to expand...
Click to collapse
thanks mate, after I re-do the dump-data in flashtool, now system.img(renamed from system.ext4) can be detected
got another question again, just to confirm what's the API level? is it 16 for Android 4.1.2? coz I only see 4.1.1 for level 16
Rycon33 said:
thanks mate, after I re-do the dump-data in flashtool, now system.img(renamed from system.ext4) can be detected
got another question again, just to confirm what's the API level? is it 16 for Android 4.1.2? coz I only see 4.1.1 for level 16
Click to expand...
Click to collapse
if you have the latest version of everything it should be OK.
Just give it a go and see...
I used the same setup I have for my latest release as I did for my original ICS release, so the api level should be OK
EDIT
I do love your sig pic, where did you get it from? Or did you make it yourself?
gregbradley said:
if you have the latest version of everything it should be OK.
Just give it a go and see...
I used the same setup I have for my latest release as I did for my original ICS release, so the api level should be OK
EDIT
I do love your sig pic, where did you get it from? Or did you make it yourself?
Click to expand...
Click to collapse
with regards to my sig banner, i got it from one of the post from G+ last time, here's a copy of the actual file -> https://dl.dropbox.com/u/28587036/Android/Android_Evolution.jpg
ok I used 16, another question , what will I do to the one file that was never deodexed? it is the playstationcertified.odex
Could not deodex the following (you can try to deodex these files again):
playstationcertified.odex
A summary of the deodexing has been logged in deodex_040813_020606.log
71 *.odex files remain in system/app
1 *.odex files remain in system/framework
Rycon33 said:
with regards to my sig banner, i got it from one of the post from G+ last time, here's a copy of the actual file -> https://dl.dropbox.com/u/28587036/Android/Android_Evolution.jpg
ok I used 16, another question , what will I do to the one file that was never deodexed? it is the playstationcertified.odex
Could not deodex the following (you can try to deodex these files again):
playstationcertified.odex
A summary of the deodexing has been logged in deodex_040813_020606.log
71 *.odex files remain in system/app
1 *.odex files remain in system/framework
Click to expand...
Click to collapse
I have always just left it in for my releases, but seeing as I dont use it, i have personally deleted both the file and the odex file.
I think its the same for all stock based roms...there will be some aditional sony security on that file as it enables you to download sony play station games so the kitchen is not set up to integrate the odex file into the original one.
gregbradley said:
I have always just left it in for my releases, but seeing as I dont use it, i have personally deleted both the file and the odex file.
I think its the same for all stock based roms...there will be some aditional sony security on that file as it enables you to download sony play station games so the kitchen is not set up to integrate the odex file into the original one.
Click to expand...
Click to collapse
oh ok.
mate, apologies for many questions, this is my first try so I'm still confuse of many things
so after I de-odexed, what's next?
> ADVANCED OPTIONS
11 - De-odex files in your ROM
12 - Tools for boot image (unpack/re-pack/etc.)
13 - Add /data/app functionality
14 - Add /etc/init.d scripts support (busybox run-parts)
15 - Unpack data.img
16 - Sign APK or ZIP file(s)
17 - Convert update-script or updater-script
18 - Plugin scripts
99 - Build ROM from working folder
0 - BACK TO MAIN MENU
basically I only want a deodexed ROM and the CWM and root retained
Rycon33 said:
oh ok.
mate, apologies for many questions, this is my first try so I'm still confuse of many things
so after I de-odexed, what's next?
> ADVANCED OPTIONS
11 - De-odex files in your ROM
12 - Tools for boot image (unpack/re-pack/etc.)
13 - Add /data/app functionality
14 - Add /etc/init.d scripts support (busybox run-parts)
15 - Unpack data.img
16 - Sign APK or ZIP file(s)
17 - Convert update-script or updater-script
18 - Plugin scripts
99 - Build ROM from working folder
0 - BACK TO MAIN MENU
basically I only want a deodexed ROM and the CWM and root retained
Click to expand...
Click to collapse
What do you want to do?
You cant do (12) use championshipswimmers kernel kitchen for that.
But i do suggest adding 14, and rooting it (thats in the main menu)
also, zipalign apks...but it will ask you to do that when you compile it
Other than that its up to you. Just try some different options out and see what you think...thats the best way to learn, if you see my releases, the first two versions were not released because I was learning and playing around with it
Make sure though that you dont use the updater script it produces, its wrong for our phones.
"Borrow" one from a working ROM in our dev section, just ask permission first.
Rycon33 said:
thanks mate, after I re-do the dump-data in flashtool, now system.img(renamed from system.ext4) can be detected
got another question again, just to confirm what's the API level? is it 16 for Android 4.1.2? coz I only see 4.1.1 for level 16
Click to expand...
Click to collapse
For android 4.1.2 api must be set @16 othervise it wont boot
Sent from my LT29i using xda app-developers app
gregbradley said:
What do you want to do?
You cant do (12) use championshipswimmers kernel kitchen for that.
But i do suggest adding 14, and rooting it (thats in the main menu)
also, zipalign apks...but it will ask you to do that when you compile it
Other than that its up to you. Just try some different options out and see what you think...thats the best way to learn, if you see my releases, the first two versions were not released because I was learning and playing around with it
Make sure though that you dont use the updater script it produces, its wrong for our phones.
"Borrow" one from a working ROM in our dev section, just ask permission first.
Click to expand...
Click to collapse
asterix005 said:
For android 4.1.2 api must be set @16 othervise it wont boot
Sent from my LT29i using xda app-developers app
Click to expand...
Click to collapse
ok mates, thank you very much, I managed to de-odexed my stock ROM:good:
This is what I did. Using flashtool, I dumped my system.sin file to get a ext4 file. Then I open it with ext4 reader and extracted the contents. I then placed it in a folder called 'system' and proceed with the android kitchen.
Humans have evolved to be smarter, but there's one thing we can't get rid off. It's human stupidity.
If you still want to deodex playstationcertified.odex rename it to com.playstation.playstationcertified.odex.
That did the trick for me in earlier firmware versions.
Sent from my phone using XDA Premium
i try many times but it's all show this
CREATE WORKING FOLDER FOR ROM
==============================
Ensure there is at least one ROM under the 'original_update' folder!
Select an option:
s - Show supported formats
x - Abort, don't create working folder
Or press Enter to continue
any idea or should i press enter to continue?
i try with system.img from xperia TX rom 1.67
lucky92 said:
i try many times but it's all show this
CREATE WORKING FOLDER FOR ROM
==============================
Ensure there is at least one ROM under the 'original_update' folder!
Select an option:
s - Show supported formats
x - Abort, don't create working folder
Or press Enter to continue
any idea or should i press enter to continue?
i try with system.img from xperia TX rom 1.67
Click to expand...
Click to collapse
why don't you press it an see?
anyway, have you used flashtool to extract the system.sin into an ext4 extension yet?
gregbradley said:
why don't you press it an see?
anyway, have you used flashtool to extract the system.sin into an ext4 extension yet?
Click to expand...
Click to collapse
i tried extract thee system.sin into ext4 and rename it to sysmtem.img but no luck
update: after re-dump system.sin and press countinue, it's seem ok, maybe my fault.
Thank you anyway :laugh:
Sorry but I have another question, after i make a flashable zip and flash through CWM, it always stuck at Sony logo, any idea ?
Hello,,,
anybody knows how to fully root emui 3.0. i've been trying to use 3.0 since it was released by Oxalis for L10 but i have a problem in rooting. I did root the phone, but i can say it is only 99% rooted, bcoz everytime i tried to delete file or app under /system/app directory files will be reverted after rebooting. i've deleted the files or app under the mentioned directory and i successfully deleted, but again, if i will reboot the phone, the apps deleted will be installed again.
Use custom E3.0 rom,unpack zip on pc,delete unwanted apps and everything you want,pack in zip again and than flash rom.This is only way (in my case) to delete unwanted apps.In any other way deleted apps return back after reboot.
Sent from my HUAWEI P7-L10 using Tapatalk
gregysk said:
Use custom E3.0 rom,unpack zip on pc,delete unwanted apps and everything you want,pack in zip again and than flash rom.This is only way (in my case) to delete unwanted apps.In any other way deleted apps return back after reboot.
Sent from my HUAWEI P7-L10 using Tapatalk
Click to expand...
Click to collapse
i'll better make updater.zip than unpacking system...
Just flash a different kernel, the 3.0 version from this thread: http://forum.xda-developers.com/asc...ds-tweaks-kernels-recoverys-emui-2-3-t2966670
The stock kernel contains a ramdisk which restores files deleted from the system partition. The custom kernel does not.
witteswa said:
Just flash a different kernel, the 3.0 version from this thread: http://forum.xda-developers.com/asc...ds-tweaks-kernels-recoverys-emui-2-3-t2966670
The stock kernel contains a ramdisk which restores files deleted from the system partition. The custom kernel does not.
Click to expand...
Click to collapse
Thanks a lot... I hope this will work. coz i tried everything except this. I will install 3.0 again later. Thank you so much.
witteswa said:
Just flash a different kernel, the 3.0 version from this thread: http://forum.xda-developers.com/asc...ds-tweaks-kernels-recoverys-emui-2-3-t2966670
The stock kernel contains a ramdisk which restores files deleted from the system partition. The custom kernel does not.
Click to expand...
Click to collapse
thanks for this idea. i am 100% rooted now. thanks a lot.
Did you delete file set_immutable.list ?
majcomtech said:
thanks for this idea. i am 100% rooted now. thanks a lot.
Click to expand...
Click to collapse
hi, i am also trying to fully root Emui 3.0. i am currently running Emui 3.0 b602 on L10 and after rooting (CWM+Update SuperSU) same issue (with files being reverted)
now I am relying on updates.zip through CWM for downgrades,etc using sideload update through usb and sometimes feels awkward
I followed the link mentioned above and found a custom E3.0 rom named boot_HRT_emui3.0.img.
@majcomtech, is this the one file that made you 100% root? I did not see references to L05, L07 or L10 nor B602, B604 or B609. Does it mean that this HRT boot.img is valid for all P7 models, say for the whole family of p7s?
will it fully root my 99% P7 L10 B620 EMUI3.0 BETA to 100% P7 L10 B620 EMUI3.0 BETA even though is not specific to a L10 nor b602?
@Kostyan_nsk, can not find set_immutable.list file inside /system folder as I used to have, a config text file with a list of immutable folders and files.
If I flash that hrt boot image I would not need to delete that file? is that the following step, flash new boot.img then delete set_immutable.list?
thanks in advance for your advice, those seam like a lot of questions :silly:
p.d: sorry english not my native language
Printusrzero said:
@Kostyan_nsk, can not find set_immutable.list file inside /system folder as I used to have, a config text file with a list of immutable folders and files.
If I flash that hrt boot image I would not need to delete that file? is that the following step, flash new boot.img then delete set_immutable.list?
Click to expand...
Click to collapse
The principle of locking system files and folders is next: there is set_immutable binary in ramdisk of boot image that executes in boot up. This binary reads list of files and folders in /system/set_immutable.list and locks them.
So there's several ways to avoid it: delete or comment line in init.rc file in ramdisk that executes set_immutable. As I remember, it looks like "exec set_immutable 1". Or change parameter from "1" to "0". Or completely delete set_immutable binary from ramdisk. So if set_immutable won't execute, existense of /system/set_immutable.list won't affect at anything.
Or you can just delete set_immutable.list and set_immutable binary will not lock anything because it will not be able to get list of files and folders to lock.
If you don't have set_immutable.list file already, I think custom boot image with disabled set_immutable binary will not solve your issue. But you have to try anyway. If system won't boot, just revert back your boot.img via fastboot or TWRP and you won't loose anything.
I think problem is in su binary. Something with security context or permissions or something else. But it's just my humble opinion, probably I'm wrong.
Thanks Kostyan_nsk for your last post!
I unpacked ramdisk and set 'exec set_immutable 1' to 0. flashed and recovery still active.
then unpacked again and renamed immutable binary inside initrc/sbin, flashed and recovery still on
I also checked supersu binaries and updated supersu both through CWM and Google... so far all my efforts were to not avail
solved! flashing custom 3.0 kernel fixed it. Kostyan_nsk you directed me to the right direction init.rc, thanks a lot .
Hello
Is there any1 with BOOT.img from firmware B584 that could upload?
You mean the kernel, right? Sorry, no. Have just the UPDATE.APP from B594 on my phone. Maybe you can download the zip-file again and get it out of the UPDATE.APP? For what do you need this? Update because custom kernel?
Literally the kernel i have installed now (ESAL v2.0) lacks "Revoke USB Authorizations" on settings. Thats why i need that specific one. (removing data/misc/adb/adb-keys doesnt help)
metonator said:
Literally the kernel i have installed now (ESAL v2.0) lacks "Revoke USB Authorizations" on settings. Thats why i need that specific one. (removing data/misc/adb/adb-keys doesnt help)
Click to expand...
Click to collapse
I'm too lazy to get boot.img for you, but there is a work around for your problem.
If you are using windows go to C:\Users\<your_windows_user_name is_here>\.android
(If using linux I don't know where to go)
Copy adbkey.pub in your device and rename it "adb_keys" with no filename end.
On your device move it in to data/misc/adb/ and probably not important but permissions are -rw-r----- .
Restart adb.
This has worked for me earlier, I hope I didn't forgot anything important.
Also you can use huaweiupdate extractor to get boot.img from update.app.
keikari said:
I'm too lazy to get boot.img for you, but there is a work around for your problem.
If you are using windows go to C:\Users\<your_windows_user_name is_here>\.android
(If using linux I don't know where to go)
Copy adbkey.pub in your device and rename it "adb_keys" with no filename end.
On your device move it in to data/misc/adb/ and probably not important but permissions are -rw-r----- .
Restart adb.
This has worked for me earlier, I hope I didn't forgot anything important.
Also you can use huaweiupdate extractor to get boot.img from update.app.
Click to expand...
Click to collapse
Will try tonight if this method will work
Just use adbd insecure
Ok, extracted it myself (took a bit, but at least it works). Here's the file in case someone will search for it.
metonator said:
Ok, extracted it myself (took a bit, but at least it works). Here's the file in case someone will search for it.
Click to expand...
Click to collapse
thks im looking for that