Related
Original post:
Hello,
I am new to android but not to linux. I used to tweak my winmo phone rom.
I have backed up my device with nandroid. I just need some explanations:
- why isn't the radio extracted?
- how can I "extract" does .img files to modify and then rebuild them?
I found some informations of what the .img files contain here: ROM Partitions it should be the same for Hero
I have found some informations on how to push updates to the rom by looking at modaco updates. It seems quite simple to delete/copy files on the hero rom using an update-sript file. I am however curious about the RSA cert and if some files need to be signed.
Any information welcomed.
Regards
Click to expand...
Click to collapse
How to
Extract NAND image files
To extract .img files, I have found unyaffs from http://code.google.com/p/unyaffs/ I have compiled it under ubuntu 64 (attached). Unyaffs works on system.img but on no other .img file
To extract boot.img use attached extract-kernel.pl and extract-ramdisk.pl
# extract-kernel.pl boot.img
# extract-ramdisk.pl boot.img
Should work for recovery.img but haven't tried as custom recovery images on the forum are great.
Rebuild system.img
Seems you just need "to loopback mount an image on your linux box and format it with YAFFS".
But it is useless as because Hero's SPL does not allow flashing system.img directly. You should use an update.zip package for that. (read below)
Rebuild boot.img
After extracting your boot.img using attached extract-*.pl and tweaking it, in same folder run:
# mkbootfs boot.img-ramdisk | gzip > ramdisk-boot
# mkbootimg --kernel boot.img-kernel --ramdisk ramdisk-boot --cmdline "no_console_suspend=1 console=null" -o newBoot.img --base 0x19200000
Creating an update.zip package
Creating an update.zip package is quite easy in fact. For example, to add a (valid) test.apk package to your rom:
- create an empty folder <workdir>
- create folder structure for test.apk (<workdir>/system/app) and copy the test.apk
- create folder structure for update-script (<workdir>/META-INF/com/google/android)
- edit <workdir>/META-INF/com/google/android/update-script
- put in it:
Code:
show_progress 0.1 0
copy_dir PACKAGE:system SYSTEM:
set_perm_recursive 0 0 0755 0644 SYSTEM:app
show_progress 0.1 10
- compress the <workdir> content to zip (not the <workdir> folder itself)
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.
To find more command to use in update-script, look at other's.
Modify .apk package
Seems it is easy to uncompress an .apk package (zip) an to modify files in it and then compress it. But after all: you must sign it like update.zip packages.
ODEX files
- What are those Odex files? Answer.
- How to get rid of them?
Odex files depend on framework they are made for. To deodex an odex file use that how to
Then you may create a classes.dex file by executing the smali program on the "out" folder. You then rename it to classes.dex and add it to the .apk.
- How to create them?
Use dexopt-wrapper on device.
Porting an other device's rom
Well, that part is easy
- extract the system.img
- extract boot.img
- replace boot.img-kernel with the one from your stock Hero rom one.
- rebuild boot.img
- build update.zip package (look someone's hero custom rom to see how to do it)
- sign and flash
It should run place and make calls but probably won't have Wifi, BT, trackball support. If you make those work: tell me, but I think we should wait to be able to compile a 2.6.29 kernel to have those.
Tools
Androsign script (linux)
I wrote that androsign script to quick sign zip files. Just put it in your <SDK>/tools folder, then chmod +x. If you have put the tools folder in your PATH, you can call it directly like this:
androsign /dev/folder1/folder2/update.zip (or any zip/apk file)
It will output an update-signed.zip (or app-signed.apk etc) in the same folder than original file was in.
Notes
Note1: thanks
Thanks to every guy that helped me found all that.
Note1: sharing
I searched for hours, so I am more than happy to share it to save someone's time. I am just disappointed than some people here do not have that spirit: I could have use those hours for development instead of research...
Note3: corrections
So, if you found anything incorrect, would like to supply more informations or want to correct my bad english: just PM me.
To find
- how to dump radio from device
- how to build a custom hero kernel (waiting for HTC sources)
To come
How to prepare your own kitchen and useful scripts (linux)
gecka said:
I am new to android but not to linux.
Click to expand...
Click to collapse
Same here. I do lots of tweeking on my linux machine, so i know quite a lot of linux. If there would be anyone to answer those questions by gecka, I might start tweeking the rom (maybe someday cook one up)
Best regards
Hello,
First post edited, but still some ignorances... Please share if you know anything.
Best regards
unpack and pack boot.img and recovery.img
First you need utilities such as mkbootfs and mkbootimg. maybe you can find them online (i can upload them later compiled for linux x86-64) but i suggest you download android source (http://source.android.com) and do a generic make. In this way you have these and other utilities(tools to pack system.img too, but if you haven't an engineering bootloader you can't flash it directly) in /out/host/... (it's better if you add this in your PATH)
To unpack and pack boot and recovery, read here:
http://forum.xda-developers.com/showthread.php?t=443994
or here:
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
...or...
(I have attached extract-kernel and extract-ramdisk scripts from JF build environment) :
to unpack (boot.img or recovery.img, i'm writing the commands with boot.img):
Code:
extract-kernel boot.img
extract-ramdisk boot.img
at this point you have
boot.img-kernel
boot.img-ramdisk
to repack (boot.img or recovery.img):
For hero you need to specify the base address because it's different (0x19200000). For more information: http://forum.xda-developers.com/showthread.php?t=541522.
Code:
mkbootfs boot.img-ramdisk | gzip > ramdisk-boot
mkbootimg --kernel boot.img-kernel --ramdisk ramdisk-boot --cmdline "no_console_suspend=1 console=null" -o newBoot.img --base 0x19200000
Useful resources for android modding are the dream forums (most of the concepts/hacks works for hero too):
http://forum.xda-developers.com/forumdisplay.php?f=448
(informative thread here: http://forum.xda-developers.com/showthread.php?t=519523)
note: mkbootimg with --base support is in donut and master (or find the patch on gerrit and apply it to cupcake)
First of all, the reason you cant unyaffs anything other than system.img is because they aren't YAFFS images. boot/recovery is kernel+initrd like in any normal linux bootimage scenario (see more below).
Tofind
- how to dump radio from device
Click to expand...
Click to collapse
Haven't gotten into that myself yet, but I know modaco posted an update.zip with radio image included on this very forum. Look for it.
- how to extract NAND images other than system.img
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=443994
- rebuild NAND images such as system.img
Click to expand...
Click to collapse
This isn't hard, just loopback mount an image on your linux box and format it with YAFFS.
Building a custom kernel and recovery binary
HTC hasn't yet released the changes they have made to the hero/dream/magic kernels, 32A board, so you can't just compile a kernel from the AOSP. I haven't tried it yet but this patch might work on hero too:
http://forum.xda-developers.com/showthread.php?t=548061
EDIT: HTC Sources for dream and magic at http://developer.htc.com
For building a custom recovery, it's better if you use cyanogen's recovery code, found in his git : github.com/cyanogen, because it already has menus for nandroid and other tools, but you can use the recovery code from AOSP too (cyanogen's one is a patched version with a lot more features, http://forum.xda-developers.com/showthread.php?t=523558). To make a custom recovery you need to change the recovery binary (because the press event of the hero trackball has a different keycode, 191), the kernel and the init scripts. Actually i don't remember what else I've changed to make cm's recovery working with hero (the recovery that we are actually using here), I'm at work now, but i'll check later and post more details, or you can just unpack the recovery and see the changes .
First post updated.
Nandroid only backs up the partitions in the main storage nand, but radio and spl are flashed to the radio's own nand flash. Whether it's possible to dump it or not I don't know, but honestly, I don't see why you'd want to. Radio images are available through RUU's and I don't think editing would be an easy task
jubeh said:
Nandroid only backs up the partitions in the main storage nand, but radio and spl are flashed to the radio's own nand flash. Whether it's possible to dump it or not I don't know, but honestly, I don't see why you'd want to. Radio images are available through RUU's and I don't think editing would be an easy task
Click to expand...
Click to collapse
Sometimes, new radio images appear on new phones. That is why I am looking on a way to extract it.
very useful thread.
Very nice tutorial, thank you!
could you please specify a bit more on how to clone from android's git and then build the mkbootimg and mkbootfs (just make, right)? I tried and I keep getting a "fatal:server dumped connection" error
Are we able to modify an official ROM (also for hero). Which shows up in RUU as INFOsignature checking... failed. Am I able to change the kernel and make it work?
jubeh said:
could you please specify a bit more on how to clone from android's git and then build the mkbootimg and mkbootfs (just make, right)? I tried and I keep getting a "fatal:server dumped connection" error
Click to expand...
Click to collapse
What command do you use?
In fact i won't be able to explain you better than that page: http://source.android.com/download
Following that how to, you'll be able to sync an android branch You can learn more about git, branches and more here (Repo and Git resources)
The sync is long (2.9Go). Then, to build mkbootimg and mkbootfs, you should do a generic build of android going to source folder and issuing the 'make' command.
All that will be part of my upcoming "How to prepare your own kitchen and useful scripts".
awsy44 said:
Are we able to modify an official ROM (also for hero). Which shows up in RUU as INFOsignature checking... failed. Am I able to change the kernel and make it work?
Click to expand...
Click to collapse
Well, to grep the system from a windows RUU exe file you should launch it and then look in your user temporary folder for a rom.zip file in a {uid} subfolder. It contains the system and boot img files.
You then need to make an update.zip package from them. Have a look to someone's hero custom rom and to it's update-script to see how it is achieved. My 'How to' gives you all you need to understand update.zip packages and to extract system.img.
If you are porting a Hero rom, no need to change the kernel.
Regards
Well, to grep the system from a windows RUU exe file you should launch it and then look in your user temporary folder for a rom.zip file in a {uid} subfolder. It contains the system and boot img files.
You then need to make an update.zip package from them. Have a look to someone's hero custom rom and to it's update-script to see how it is achieved. My 'How to' gives you all you need to understand update.zip packages and to extract system.img.
If you are porting a Hero rom, no need to change the kernel.
Regards
Click to expand...
Click to collapse
Thanks so much for this amazing information, however how do i stop getting hit with the infosignature failed error? is that the kernel or the hboot? it says 12 signature verify error.
Oh, I do have the source and I am running my own donut build on my dream with some of my spice, but the problem I was having was cloning that exact project (mkbootimg) from android.git.kernel.org using git, but when I read what you said, I remembered that when you make the build, it also compiles several tools and i overlooked checking the out folder for it, kind of dumb on my part since I had already pulled the fastboot tool from that build and added it to my own bin, i guess mkbootimg and mkbootfs should be there too, right?
i tried running androsign and got this error
Code:
[email protected]:~/android/dev/sdk/tools$ ./androsign META-INF.zip
Exception in thread "main" java.lang.NoClassDefFoundError: testsign
Failed!
[email protected]:~/android/dev/sdk/tools$
if i use a ROM of one device on an other different device, I think I must build a kernel on my own, is that correct?
but what config should I use? a config from my current running ROM? then I think I must make it suitable for new ROM, what options should I care about?
for example, if I want to run a AOSP 2.01 ROM ( system.img) on a Magic 32A device with SPL 1.76, and now I am running a SenseUI ROM which kernel is 2.6.27, I think I should build a 2.6.29 kernel from the git tree, and ensure it will work with camera/bt/wifi/trackball of my device properly first .
how can I make this step successful?
other hand, the dynamic lib files(.so) with the system.img can be incorrect. so, I may need to build them too for pairing with the kernel I built in previous step. I think applications will work properly because they only care about if the interfaces of kernel and lib is correct. for that, also there some config job (like build.prop, etc) to do, is there a list of all of these jobs? and what values can I refer to? the original ROM (Magic 32A SPL 1.76 working ROM here) ?
am I right? what should i do and what are in those steps? are there some doucments I can read from?
Thanks for the good summary. Just one question, where did testsign.jar come from? I'd like to get the source. Thanks!
JackZero said:
Thanks for the good summary. Just one question, where did testsign.jar come from? I'd like to get the source. Thanks!
Click to expand...
Click to collapse
Read this !
http://www.androiddevelopment.org/tag/apk/
;-)
Hi there, as many of you may know dzo or simple god makes a flashable version of android for our KAISERs.
But vefore here are some rules:
THIS THREAD IS MADE TO KEEP THE FLASHING ANDROID ON KAISER DEV THREAD CLEAN FROM USERQUESTIONS!!!
DON'T ASK USER QUESTIONS IN THE DEV THREAD!!!
This Thread is for experienced Kaiser users who aren't in development but wan't to see android running native from NAND.
THIS IS AT THE CURRENT STATE VERY VERY VERY BETA, THERE MAY BE A HIGH RISC TO BRICK YOUR DEVICE. THIS WILL COMPLETLY WIPE WINDOWS MOBILE. JUST USE IT IF YOU CAN ANSWER YOURSELF THE FOLLOWING QUESTIONS: (without search function)
-What is an .nbh file
-how to flash a kaiser
-What is HardSPL /Security unlock
-How to recover a bad rom flash?
-What to do if your device won't start anymore?
-Do you have basic android skills?
Ok Guys, little cleanup and updates:
INDEX:
-Post one:
Different flashing methods
Things to take care off
-Post two:
How to creat your own nbh files
How to make custom splash screens
-Post three:
Working Systems/rootfs
Bugs
Usefull Links
Thanks
HOW TO START ANDROID FROM NAND
Method one:
1-Download one of the nbh's here http://www.megaupload.com/?f=SA71F1MT, you'll have to look for the right panel type, Key layout and resolution needed for the rom you're flashing, just like your default.txt from sd boot.
2-Download http://www.mediafire.com/?zldjhfnkzk2
3-Copy the androidinstall.tar from the androidinstall.zip file to the root of your sdcard
4-delete/rename any old android files on your sdcard
5-Unzip the androidinstall.zip and replace the ruu_signed.nbh in it with the one you downloaded in the first link. (must be named ruu_signed.nbh)
-6Run the custom ruu.exe - thats all after reboot you'll have a flashed Cupcake android.
Method two:
1-delete/rename any old android files on your sdcard
2-Download one of the nbh's here http://www.megaupload.com/?f=SA71F1MT, you'll have to look for the right panel type, Key layout and resolution needed for the rom you're flashing, just like your default.txt from sd boot.
3-Create three empty files on your sdcard wihout any extension:
-datafstonand
-systemfstonand
-rootfstonand
4-Copy your prefered rootfs.img, system(img,ext2,sqsh) and an empty data.img to sdcard root
5-Copy the nbh file you downloaded to the root of your sdcard and rename to kaisimg.nbh
6-Reboot your device using restart button and cam button, then when it tells you, press power key to flash the new nbh.
-Reboot by pulling the battery - Thats it ( First start may take a while and may reboot randomly, just give it some time)
Different Tricks and hints (collected in the forums):
-Change Panel Type:
Run: "echo 1 > /sys/module/board_htckaiser/parameters/panel_type" through adb or init
-Experimental GPS:
For working, gps you need to replace libgps.so with the one from the vogue gps thread.
Experimental openGL Drivers ( Eclair Only)
-Download this one and flash your prefered nbh: http://rapidshare.com/files/345432577/kasiandroid_nbh_with_opengl.zip
-Install the included script sheduler, and replace the afterboot.txt with the one included in the zip file
This will install an app that will run the afterboot.txt after every boot and fix file permissions.
-Or you can open the afterboot.txt and run it in terminal after every boot.
To see if it works install the included gallery3d.apk, iff you see thumbnails, it worked
Not tested by me, yet through no time.. (Thanks to quitlahok and rzk333 for this manual)
THIS IS JUST FOR THOOSE WHO ARE MORE IN DEVELOPMENT AND LINUX
HOW TO CREATE YOUR OWN NBH FILES:
1- Set up your prefered Linux Setup, i use Debian.
2-Build kaiser kernel with wiki manual
3-git clone git://androidhtc.git.sourceforge.net/gitroot/androidhtc/tinboot
4-git clone git://androidhtc.git.sourceforge.net/gitroot/androidhtc/bootenv
5-cd bootenv
6-cp buildInitrd buildInitrd-mini
7-nano (or whatever your favorite editor is) buildInitrd-mini
8-change all instances (2 of them) of initrd to initrd-mini
9-sh buildInitrd-mini
10-cd tinboot
11-nano tinboot.S
12-the paths to fix are at the bottom of the file, it's pretty self-explanatory. higher up in the file you'll see the kernel cmdline under an .ifdef kaiser line
13-after that you'll need to download and extract any windows kitchen, and install wine however your linux distro requires and make a note of the path you extract nbhmerge.exe to as you'll need it in your tinboot.S file, along with the path to your kernel zImage and initrd-mini.gz
after that if you've got everything else in place, go ahead and run the compilekaiser script in the tinboot dir and you should have an nbh
if the nbh won't flash (i had this issue) copy the output.nb file, boot into windows, and use nbhutil.exe to convert it to an nbh and flash that one. for some reason yang doesn't work right for me personally
HOW TO CREATE CUSTOM SPLASH SCREENS: (this is a manual by POV)
1. Install HardSPL.
2. Create a BMP file in paint, size must be 240x320, save it as BMP 24bit.
3. Download SplashTool
4. Load your BMP on nb_image_converter (included in SplashTool's zip) and save it as splash.nb
5. Open SplashTool.exe and convert splash.nb to new format.
6. Pack the resulting splash.nb into a NBH file using htc rom tool.
7. Flash your cusotm NBH using CustomRUU.
This will not harm your installed android
WORKING SYSTEMS / ROOTFS'S: ( Collected in the forums)
- http://forum.xda-developers.com/showthread.php?t=587116 ION Donut, reuploaded by 160bpm
- http://forum.xda-developers.com/showthread.php?t=619980 MYNs warm Donut
- http://forum.xda-developers.com/showthread.php?t=619718 Jamezelles Sense Tattoo
- http://forum.xda-developers.com/showthread.php?t=591104 Plemens Donut AOSP
- http://forum.xda-developers.com/showthread.php?t=603028 Jamezelles Sense Hero
- http://forum.xda-developers.com/showthread.php?t=619285 Shidells Android 2.1
rootfs 2010-01-06 works best for me get it here: http://sourceforge.net/projects/androidhtc/files/
Bugs:
NOT WORKING: WiFi, GPS, Voice Call, Bluetooth
(GPS experimental with the files from first post)
Usefull Links:
Android on Sourceforge:
http://sourceforge.net/projects/androidhtc/files/
Android on htc Website:
http://www.androidonhtc.com
dzo's page:
http://it029000.massey.ac.nz/vogue/
Android SDK:
http://developer.android.com/sdk/
Tinboot dev thread:
http://forum.xda-developers.com/showthread.php?t=614275
Thanks:
dzo, plemen, jamezelle, zenulator, enatefox, mssmision, vilord, rzk333, diagdave
SORRY IF I'LL FORGET ANYONE
Here's a couple boot screens I made.
Thanks i'll add this to the first post
Thanks JeckyllHavok, good idea I keep posting over here am not into kernel things anyway
Ok after a few attempts I finally got Android flashed, and running, using my backup kaiser, which has no network connection, so the lack of wifi is a bit of a problem, but seems to be working fine so far, and fast
Just wondering if it would be possible to flash other versions, like eclair or even flan, since polyrhythmic's eclair version seems to be nice and stable, or is this going to fast to soon?
Just tested this with sshidels nexus rom, but itjust ends in bootscreen loops. Maybe other roms work
Looks like in need to learn to read. I found these instructions in the Vouge forum:
Method 2:
------------------------------------------------------------------
Check here for NBH files containing a linux kernel and initrd to allow you to flash android to your vogue and wipe windows completely.
The ROMs are dated and there are three versions.
They are identical except the resolution; 240x320, 320x428 and 320x480.
This rom will copy your rootfs, system and data to nand (the internal storage of the phone) so you will only be running from nand. To do this, make sure you have a working setup (using system.sqsh and data.img without partitions) and install the new rootfs. Make sure it still works.
Make sure you have a carrier rom to go back to. Android currently doesn't let you change any of the radio parameters so you would have to flash back to a carrier rom to re-provision your phone.
Now create 3 empty files in the root of your sd card called:
rootfstonand
systemfstonand
datafstonand
These must be all lower case with no extensions and they will be deleted once each fs has been copied.
Now flash the rom corresponding to your resolution and wait.
Click to expand...
Click to collapse
Buried for stupidity. Works great so far.
Flashing now.
1st edit: We have Android .
2nd edit:26 min it just turned itself off ... creepy ... soft reset ....I'll post back results.
3rd:39 min later Actual Phone screen came up No SIM ..Opps rebooted waiting agian.
What is working/not working with this flash.
From what I've read everything except.
Blutooth
wifi
GPS
Still waiting back at ANDROID screen
I have successfully flashed THIS BUILD using the following method:
dzo said:
...create 3 empty files in the root of your sd card called:
rootfstonand
systemfstonand
datafstonand
These must be all lower case with no extensions and they will be deleted once each fs has been copied.
Click to expand...
Click to collapse
It's a little small and awkward due to the set resolution, but it's possible to flash different builds!
Another note: When flashing builds it takes a very long time, but when it gets to the setup android screen it has a system FC and the screen doesnt respond. This has happened everytime. I had to pull the battery and when I boot it up a second time it boots just fine.
loserskater said:
I have successfully flashed THIS BUILD using the following method:
It's a little small and awkward due to the set resolution, but it's possible to flash different builds!
Another note: When flashing builds it takes a very long time, but when it gets to the setup android screen it has a system FC and the screen doesnt respond. This has happened everytime. I had to pull the battery and when I boot it up a second time it boots just fine.
Click to expand...
Click to collapse
Hi
Can you please send me the files on the sdcard. I am having an issue with every build.
Thanks
Did wifi work with any builds?
I think no, not now
Tilt
Hey all,
Working great on my tilt except the ringer just rings in the earpiece at like phone call volume. You can't really hear it unless you have your ear against it. Any thoughts?
I used DZO's build of 1.5 and one of the NBH filwa from Ra333 as the DZO one did not work.
Jaguarius said:
Hey all,
Working great on my tilt except the ringer just rings in the earpiece at like phone call volume. You can't really hear it unless you have your ear against it. Any thoughts?
I used DZO's build of 1.5 and one of the NBH filwa from Ra333 as the DZO one did not work.
Click to expand...
Click to collapse
Are the keys on the slide keyboard working correctly
OK now got two nand flashed kasiers, (both kais130), first using the 'original' flash method, ( dzo nbh, androidinstall.tar), and the other method from the vogue threads, with polyrhythmics Eclair build, which is much slower, ( uses SD card rather than Nand?).
Both seem to be working as well as can be expected at this early stage of Nand flashing.
What I would like to know is how to 'upgrade' our zImage, since some builds have a different zImage version than the one we are currently flashing with, ( I am assuming our zImage is in the NBH flash), since this may help enable wifi/gps which we are presently lacking.
I am looking for a dev that can help me try and enable JIT on the SGS i have, a dalvikvm + libdvm.so and libnativehelper.so that should enable JIT. Could a dev with please create an update zip with these original files from our SGS (as a backup) and then sign these files as an update.zip and then do the same with the files i have attached - then try and flash them and see if you can get it to boot.
Please PM me if you have any questions or if you can successfully boot the phone.
(i am away from home for a few days and will not be able to try myself.. using hotel computer...)
Thanks
Sorry forgot to upload the files was watching the match. Will upload them in the next few minutes.
I already done compiled with JIT enable
copy files to my device, succesfully boot up but when I test with Linpack
MFLOPS was decrease, 6.65
before apply those files MFLOPS was 8.92
Hmm I might done somethings wrong?
FYI,
Maybe
Yes you may have made a mistake, could you please try with the files above.
can't boot for my i9000
Hang on boot loop
...
W/BootAnimationSEC( 2179): ms4631 - Repeat Loop Animation
...
Not working and NoooooO !! I can't remove those libs T_T
execute "su" got "Segmentation fault" -__-"
@bratfink May I? where did you got those files.
You can use my Custom Rom for this ;-) http://forum.xda-developers.com/showthread.php?t=724450
I just want to put those (essential) JIT enabled file. Or It will not work? if there're only those 3 files.
Just don't want to use custom ROM right now, it's base on European rom but I'm living in Asia. There're many tasks to do after use others region rom, for me.
@seraphimserapis Could you suggest the information that made me, to build my own custom rom, base on my region's rom. I googling, googling couple weeks ago but still can complete the jigsaw.
-_-" finally, I can recover my devices ...
@bratfink I think those files were dangerous, got stucked at the (big S boot screen), broke the "su" command so I can not restore the original one.
I must flash the Kernel back to LeShak kernel then restore those files. flash current again then device back to normal.
Hello,
I recently uninstalled some (system / T-Mobile) apps with Titanium Backup. And I did not make a backup first. The phone still runs fine but the OTA fails.
I tried so far:
- RUU 1.28 -> does not work, because system is already 1.29
- find rom.zip and unpack -> Ok, but cannot unpack system.img, unyafs fails.
The file which the OTA misses, according to logfile is named: 4661_TMODE_Music_One.odex
If someone could sent me this file or upload it somewhere I would be thankful.
There is a good chance that there are more files missing, but the log stops after the first fail.
I see in the system.img that there are at least 4 files with similar names:
4661_TMODE_Music_One.odex
4661_TMODE_Music_One.apk
4662_TMDE_Games_One.odex
4662_TMDE_Games_One.apk
If anyone knows how to unpack these, this would also helpful.
deleted
I think the best way to get all your bloatware back is to lock the bootloader and then flash the 129 RUU. Here is the link for the RUU if its T-mobile uk.
http://www.filefactory.com/file/6y1...Radio_1.1204.105.14_release_260731_signed.exe
Once your back to stock you can unlock again with your unlock token, flash cwm and make a stock nandroid backup.
If you need a file factory password pm me.
No, it's T-Mobile Germany, so I guess this will not help.
At the moment I'm trying to unpack the files from the system.img, but none of the methods described in the forums are working.
It is almost crazy, I can see the filenames and contents (lots of "PK" headers for instance) within the system.img but I've no idea how to extract them.
Get in touch with football. He might be able to get the RUU for you.
ghori1989 said:
Get in touch with football. He might be able to get the RUU for you.
Click to expand...
Click to collapse
Ok, tried that, waiting for the reply.
Meanwhile I'm able to mount the system image with some modifications as ext4 image and copy the contents. If there is an interest for this, I propably could write some tool to make this automatic.
Anyway, it did not help me, because the versions of the files in the image do not match the ones expected from the OTA.
Hi all
I'm trying to flash and old kernel (boot.img) and system (super.img) to a S20 z1s exynos - SM-G980F/DS with a SW REV. higher than I would like...
I flashed TWRP sucessfully, this tripped knox, so I don't care at all about unsigned code running.
So I tried to:
1. disable AVB using a prebuilt vbmeta.img from here: https://forum.xda-developers.com/t/...root-s20-series-and-upgrade-firmware.4079353/
2. unpacking and then re-packing the stock firmware using "superr"s kitchen, but this produced a zip with which twrp was not happy with, even fixing a lot of updater-script errors... then again I think it does not help that my TWRP thinks the device is a z3s (no other twrp build available)...
3. flashing via ODIN obviously failed due to the device vs binary SW REV. difference.
4. flashing boot and super "by hand" in twrp -> error about SW REV. mismatch (DEVICE: X BINARY: X-1)
I have so many Questions to which I am unable to find answers, just suspicions/opinions....
Qs:
1. Can I simply disable all boot verification somehow?
2. how are vbmeta images created? do I need to fakesign my images? (vbmeta.img and vbmeta_samsung.img)
Thanks a lot for some clarifications
Defekkt said:
Hi all
I'm trying to flash and old kernel (boot.img) and system (super.img) to a S20 z1s exynos - SM-G980F/DS with a SW REV. higher than I would like...
I flashed TWRP sucessfully, this tripped knox, so I don't care at all about unsigned code running.
So I tried to:
1. disable AVB using a prebuilt vbmeta.img from here: https://forum.xda-developers.com/t/...root-s20-series-and-upgrade-firmware.4079353/
2. unpacking and then re-packing the stock firmware using "superr"s kitchen, but this produced a zip with which twrp was not happy with, even fixing a lot of updater-script errors... then again I think it does not help that my TWRP thinks the device is a z3s (no other twrp build available)...
3. flashing via ODIN obviously failed due to the device vs binary SW REV. difference.
4. flashing boot and super "by hand" in twrp -> error about SW REV. mismatch (DEVICE: X BINARY: X-1)
I have so many Questions to which I am unable to find answers, just suspicions/opinions....
Qs:
1. Can I simply disable all boot verification somehow?
2. how are vbmeta images created? do I need to fakesign my images? (vbmeta.img and vbmeta_samsung.img)
Thanks a lot for some clarifications
Click to expand...
Click to collapse
For these and other reasons, I quickly grew frustrated with SuperR's Kitchen and ultimately ended up rolling my own purpose-built solution that peels the layers of the onion of the Samsung package, gets to the point of mountable filesystem images, performs the desired transforms, and then packs everything back up into Odin-flashable .tar.md5 files. It's rough and minimalistic, but it works.
I'm not familiar with the error you mention, but usually those sorts of errors come from flashing a bootloader in Odin that is below the level of the one residing on the device. I haven't done much flashing via TWRP since I'm producing Odin-flashable output and I don't know why you'd have issues on boot.img or super.img. For my own sanity I don't regularly flash bootloader images. boot.img doesn't contain the booatloader though: it's the kernel and initramfs.
vbmeta.img files are generated with avbtool. I created one with a null signature which is identical to the ones floating around on the forum. I also cleaned up my fstab and manifests using the techniques of ianmacd's multidisabler.
sjevtic said:
For these and other reasons, I quickly grew frustrated with SuperR's Kitchen and ultimately ended up rolling my own purpose-built solution that peels the layers of the onion of the Samsung package, gets to the point of mountable filesystem images, performs the desired transforms, and then packs everything back up into Odin-flashable .tar.md5 files. It's rough and minimalistic, but it works.
I'm not familiar with the error you mention, but usually those sorts of errors come from flashing a bootloader in Odin that is below the level of the one residing on the device. I haven't done much flashing via TWRP since I'm producing Odin-flashable output and I don't know why you'd have issues on boot.img or super.img. For my own sanity I don't regularly flash bootloader images. boot.img doesn't contain the booatloader though: it's the kernel and initramfs.
vbmeta.img files are generated with avbtool. I created one with a null signature which is identical to the ones floating around on the forum. I also cleaned up my fstab and manifests using the techniques of ianmacd's multidisabler.
Click to expand...
Click to collapse
Thank you for your reply!
1. any chance you could list the steps you used to re-package a samsung rom?
2. is there a guide on how to create null-sigged vbmetas? can you use avbtool or do I need to manually edit the vbmeta file(s) ?
I did not try to downgrade the bootloader, just boot.img (kernel) and super (system, etc.).
Thanks in advance and best regards!
Sorry for the delay. I am on vacation and have not been regularly checking the forum.
To give you a conceptual overview of the workflow, here is the debug output my script generates for each step when trivially unpacking/repacking a Samsung firmware archive:
Extracting source zip.
Extracting .tar.md5 files.
Unlz4ing, unsparsing, and copying images.
Unpacking super.img.
Unpacking boot.img and up_param.bin.
Mounting filesystem images.
Applying main transforms.
Unmounting and checking filesystem images.
Repacking up_param.bin and boot.img.
Repacking super.img.
Sparsing, lz4ing, and copying images.
Archiving .tar.md5 files.
The real magic, of course, is in the transforms that are performed along the way, of which there are many. Most (notably those that are operations against the filesystem images) are performed during step 7, though some are performed before or after other steps by necessity. At some point I'll probably document this process a bit more and release the scripts since it is nontrivial.
Here is how I created my null vbmeta image:
Code:
avbtool make_vbmeta_image --flags 2 --padding_size 256 --output "${STEP_03_DIR}/BL/vbmeta.img"