Hello!
I've got a gt-i9100 (glalaxy SII) with android 4.0.4( No CWM, no Root)
I want to make a recovery image, that when it start running a simple HelloWorld application (printf("Hello World\n") on the screen for example).
1) Samsung Stock recovery image running init(which initializes fs, mount partitions. etc.), then running recovery binary file, which doesn't contains exec (so, I can't add "exec /sbin/HelloWorld" in recovery.rc file).
Is there a way to run the application, modifying rc files in initrd? (I can compile stock kernel from sources, pack/unpack an initrd)
2) I make my own initrd, which contains busybox+udev+some initial scripts. But after flash, phone is going into reboot loop
Maybe someone managed to create "own little" initrd?
3) I think than I can use update.zip file for my goal. So, I downloaded an example of update.zip and make my own update.zip file with HelloWorld application. I've install ZipSigner and "sign" my update.zip with all keys. But for every key stock recovery says that update.zip is not verified.
I don't know how to work with zipsigner and update.zip or ZipSigner doesn't support 4.0.4 android?
Maybe someone was trying to do the same work?
any ideas?
Thanks!
Hey Guys,
i want to build AOSP from sources. Specifically on the Nexus 10.
I downloaded the proprietary binaries from the Nexus Binary Download page. https://developers.google.com/android/nexus/drivers#manta
I followed instructions how to set up the source code and build it but i am not too sure how to correctly extract the proprietary binaries.
(tutorial used: http://forum.xda-developers.com/showthread.php?t=1762641)
I used the self-extracting shell scripts to extract the binaries in the root of the directory i executed "repo sync" in. (in my case: WORKING_DIRECTORY)
The binaries were put to "WORKING_DIRECTORY/vendor"
My question is whether i did it correctly and whether the binaries will be included in the build when i hit "make".
I just flashed my compiled OTA zip and everything worked perfectly with the proprietary binaries!
Hi! I badly need to know if ADT would work if the whole extracted ADT folder from my laptop will be copied to another PC. Will it include the the downloaded and installed packages (SDK package, ARM EABI v7a System Image)?
I own an MTK6735 phone with locked bootloader running Android Lollipop 5.1 64-bit.
I have access to the original rom and I am able to edit system files by mounting system.img in linux, make changes, rebuild and finally flash the new system with mtk flash tool. I was able to add opengapps to my phone by extracting it and putting everything in the correct folders manually. I have however had no such luck with superSU. I tried putting the "su" and "supolicy" binary in both bin and xbin and adding libsupol.so to lib and lib64 folders.
I would greatly appreciate it if anyone can point me in the right direction.
Hello guys!
I have Lenovo Tab 3 [TB3-850M], unfortuantely I am trying to deodex the ROM but both methods in SuperR Kitchen failed.
1st Method using oat2dex: It fails and not fully deodex the ROM and gives a list of failed files [look at pictures]
2nd Method using baksmali/smali: It says it "succeeded" but it doesn't as when flashing the ROM it is unbootable as I got (While deodexing) Java Exception error that it couldn't find classes.dex in all the ROM files!
Please I tried all Marshmallow deodexers available on XDA but nothing seems to work, the most about-successful attempt was with SuperR oat2dex and Fulmics Deodexer but I got com.android.phone has stopped working message error loop and other apps such as Maps and Keyboard.
Thanks in advance!
P.S: If you want the system.img.ext4 and boot.img I will upload them on request as my internet is not that fast and you most probably need one from me because the one online doesn't seem to extract [I made mine by flashing the unextractable system.img using SP Flash Tool and make System Image Backup using TWRP and copied it to my PC]
Regards!
Troubleshooting
What Kitchen version?
1.1.5.9
What environment are you running the kitchen in (OS, 32/64-bit, cygwin, Bash on Windows, etc.)?
Bash on Windows x64
What device are you working on (make/model)?
Lenovo Tab 3 LTE TB3-850M arm64
What was the source you started from (system.img, system.ext4.tar, rom.zip, etc.)
system.img.ext4 from TWRP Backup
What Android version?
Marshmallow 6.0
What perm method (set_perm, set_metadata, sparse_dat, raw_img)?
set_metadata
What did you do after extracting and before building?
Didn't mess with the files before and after building/extracting, just used the commands on SuperR and flashed the finished zip file to the tablet.
Were there errors on the screen if you scroll up in the terminal?
Mentioned the errors on the first post
Send a recovery.log after flashing if you have problems flashing the ROM.
No need because TWRP flash successfully
Send a link that does not require registration to the files you started with (nandroid, system.img, boot.img, etc)
http://www.mediafire.com/file/r2p6hos5k73f161/TB3-850M-System.7z
Use the support option in the Misc Tools menu and attach the support.zip to your post.
I am not sure but looks like SuperR isn't making the support.zip, I will upload the project files instead (I think both are the same)
addas4 said:
What Kitchen version?
1.1.5.9
What environment are you running the kitchen in (OS, 32/64-bit, cygwin, Bash on Windows, etc.)?
Bash on Windows x64
What device are you working on (make/model)?
Lenovo Tab 3 LTE TB3-850M arm64
What was the source you started from (system.img, system.ext4.tar, rom.zip, etc.)
system.img.ext4 from TWRP Backup
What Android version?
Marshmallow 6.0
What perm method (set_perm, set_metadata, sparse_dat, raw_img)?
set_metadata
What did you do after extracting and before building?
Didn't mess with the files before and after building/extracting, just used the commands on SuperR and flashed the finished zip file to the tablet.
Were there errors on the screen if you scroll up in the terminal?
Mentioned the errors on the first post
Send a recovery.log after flashing if you have problems flashing the ROM.
No need because TWRP flash successfully
Send a link that does not require registration to the files you started with (nandroid, system.img, boot.img, etc)
http://www.mediafire.com/file/r2p6hos5k73f161/TB3-850M-System.7z
Use the support option in the Misc Tools menu and attach the support.zip to your post.
I am not sure but looks like SuperR isn't making the support.zip, I will upload the project files instead (I think both are the same)
Click to expand...
Click to collapse
I can't do anything about this. You would need to create an issue on the smali/baksmali github repo. Once it is fixed there, I can compile new jar files and update them in the kitchen. Check your deodex log for the smali/baksmali errors you will need to post when you create the issue/s