Database Develop

[DUMP] Motorola Atrix 4G U4_1.5.2

Hi!
This is a dump of [FLASH_SBF] Motorola Atrix 4G U4_1.5.2
Kernel config, initramfs + recovery Code Group 56 / Partition 10 / Recovery --- Code Group 55 / Partition 11 / Kernel
Modem (new ver: oly17706 stock: oly17705) (Code Group 5)
/system - mirror (Code Group 57)
/osh (Code Group 58)
I'll post the other partitions shortly.
Stock ----------------
ro.build.id=OLYFR_U4_1.2.6
ro.build.display.id=OLYFR_U4_1.2.6
ro.build.version.incremental=1296900353
ro.build.date=Sat Feb 5 03:11:10 CST 2011
ro.build.date.utc=1296897070
ro.build.user=w19091
ro.build.host=il93lnxdroid46
ro.build.description=olympus-user 2.2.1 OLYFR_U4_1.2.6 1296900353 ota-rel-keys,release-keys
ro.build.fingerprint=MOTO/olyatt/olympus/olympus:2.2.1/OLYFR_U4_1.2.6/1296900353:user/ota-rel-keys,release-keys
ro.build.version.full=Blur_Version.4.1.26.MB860.ATT.en.US
Update ----------------
ro.build.id=OLYFR_U4_1.5.2
ro.build.display.id=OLYFR_U4_1.5.2
ro.build.version.incremental=1298398352
ro.build.date=Tue Feb 22 09:28:35 PST 2011
ro.build.date.utc=1298395715
ro.build.user=fpgh48
ro.build.host=ca25rhe85
ro.build.description=olympus-user 2.2.1 OLYFR_U4_1.5.2 1298398352 ota-rel-keys,release-keys
ro.build.fingerprint=MOTO/olyatt/olympus/olympus:2.2.1/OLYFR_U4_1.5.2/1298398352:user/ota-rel-keys,release-keys
ro.build.version.full=Blur_Version.4.1.52.MB860.ATT.en.US

Da_G said:
Hi!
This is a dump of [FLASH_SBF] Motorola Atrix 4G U4_1.5.2
System - [font size=-2]mirror[/font]
I'll post the other partitions shortly.
Click to expand...
Click to collapse
If I may ask, how did you pull the Dump?

hes da_g, thats how he did it.

There are a couple sbf tools available that will separate out the CGs (Code Groups) from the .sbf (which is a container for the CGs and a few other things)
I used RSD Lite which splits them out, each is an image of the partition (like one made with dd) so you can do:
Code:
mount -o loop ~/olyfr_u4_1.5.2_signed_olpsattspe_p012_hwolympus_1g_1ffCG57.smg /mnt/atrix
which mounts the filesystem to /mnt/atrix letting you read everything out

Ok so pretty much the currently available version of RSD (4.9) can read the SBF just not flash it to the Atrix. Thanks!
Da_G said:
There are a couple sbf tools available that will separate out the CGs (Code Groups) from the .sbf (which is a container for the CGs and a few other things)
I used RSD Lite which splits them out, each is an image of the partition (like one made with dd) so you can do:
Code:
mount -o loop ~/olyfr_u4_1.5.2_signed_olpsattspe_p012_hwolympus_1g_1ffCG57.smg /mnt/atrix
which mounts the filesystem to /mnt/atrix letting you read everything out
Click to expand...
Click to collapse

Si Senor. Yes Sir!

Sorry I am trying to learn all the limbo.. what the significance of a dump? is that a copy of the sbf?

It's a file archive (specifically .tar.gz, which is comparable to a .zip or a .rar) with all the files in the filesystem. So it's not a copy of the .sbf, but another way of presenting the same data. And with root you can shuffle these files in by remounting /system rw and copying them in, to try out new stuffs
edit: updated first post with /osh dump

Da_G said:
It's a file archive (specifically .tar.gz, which is comparable to a .zip or a .rar) with all the files in the filesystem. So it's not a copy of the .sbf, but another way of presenting the same data. And with root you can shuffle these files in by remounting /system rw and copying them in, to try out new stuffs
edit: updated first post with /osh dump
Click to expand...
Click to collapse
Hey G, exactly whats new in this? How do I remount the new stuff? You make everything sound so simple!

Well, for example, if you wanted to pull out an app you could grab the .apk from the dump, deodex it, and introduce it into your current rom..
I think it's likely possible to directly flash the .smgs to NAND too, bypassing the bootloader. I did some testing with Fenrir on IRC that resulted in a brick (all hail!) but before the brick happened we were successful in flashing a (signed) part of the NAND without issue.
(uploaded kernel config, initramfs, modem)

Da_G said:
Well, for example, if you wanted to pull out an app you could grab the .apk from the dump, deodex it, and introduce it into your current rom..
I think it's likely possible to directly flash the .smgs to NAND too, bypassing the bootloader. I did some testing with Fenrir on IRC that resulted in a brick (all hail!) but before the brick happened we were successful in flashing a (signed) part of the NAND without issue.
(uploaded kernel config, initramfs, modem)
Click to expand...
Click to collapse
Any exciting things inside? That are worth checking? Is the modem different?

Da_G said:
Well, for example, if you wanted to pull out an app you could grab the .apk from the dump, deodex it, and introduce it into your current rom..
I think it's likely possible to directly flash the .smgs to NAND too, bypassing the bootloader. I did some testing with Fenrir on IRC that resulted in a brick (all hail!) but before the brick happened we were successful in flashing a (signed) part of the NAND without issue.
(uploaded kernel config, initramfs, modem)
Click to expand...
Click to collapse
can you write to /sys folder with mounting ? if so i will stop what im doing as i have something to try

dumb question, but is there any rsd lite version that will flash this onto the atrix? not that i plan to do it, just want to learn.

t0dbld said:
im confused are you guys all not running this version already? I have 2 atrix in my hands this is same build i have ran sense day 1 are some of you running different versions? also what are than your build dates ?
Click to expand...
Click to collapse
I'm on Build # U4.1.2.6 so....

franciscojavierleon said:
dumb question, but is there any rsd lite version that will flash this onto the atrix? not that i plan to do it, just want to learn.
Click to expand...
Click to collapse
Not right now. Tomorrow maybe.

@Fixter:
The modem is 1 version higher (info in first post) changes are negligable.
@t0dbld:
Yes, you are free to read/write the whole /system partition. (with root) (edit: after talking on irc i realize you meant /sys which is a kernel interface rather than a partition, you can't write to it like a partition, but you can change some config settings there)
And should any (very) brave souls want to try flashing through a completely manual, arcane, scary, possibly deadly to your device method, I might have a way to bypass the bootloader for writing the sensitive areas of NAND that would normally be signature checked. With some testing were able to write a few 1KB chunks without issue, when tried a whole image it bricked, failing security check on next boot. Have some ideas how to get around that though, maybe better to try when a working RSD/SBF combo is available for easy recovery

Da_G said:
@Fixter:
The modem is 1 version higher (info in first post) changes are negligable.
@t0dbld:
Yes, you are free to read/write the whole /system partition. (with root)
And should any (very) brave souls want to try flashing through a completely manual, arcane, scary, possibly deadly to your device method, I might have a way to bypass the bootloader for writing the sensitive areas of NAND that would normally be signature checked. With some testing were able to write a few 1KB chunks without issue, when tried a whole image it bricked, failing security check on next boot. Have some ideas how to get around that though, maybe better to try when a working RSD/SBF combo is available for easy recovery
Click to expand...
Click to collapse
Hi, will this resolve my Atrix 4G's problem of unable to detece network carriers after using *#*#4636#*#* code to check the radio band?
My 4G now can only dial emergency calls. Can I share with u the attached docment and hopefully you can give me some advice if I can resolve my problem.
Thanks so much...

Da_G said:
There are a couple sbf tools available that will separate out the CGs (Code Groups) from the .sbf (which is a container for the CGs and a few other things)
I used RSD Lite which splits them out, each is an image of the partition (like one made with dd) so you can do:
Code:
mount -o loop ~/olyfr_u4_1.5.2_signed_olpsattspe_p012_hwolympus_1g_1ffCG57.smg /mnt/atrix
which mounts the filesystem to /mnt/atrix letting you read everything out
Click to expand...
Click to collapse
nice, just like the rfs files from the captivate
Da_G said:
@Fixter:
The modem is 1 version higher (info in first post) changes are negligable.
@t0dbld:
Yes, you are free to read/write the whole /system partition. (with root) (edit: after talking on irc i realize you meant /sys which is a kernel interface rather than a partition, you can't write to it like a partition, but you can change some config settings there)
And should any (very) brave souls want to try flashing through a completely manual, arcane, scary, possibly deadly to your device method, I might have a way to bypass the bootloader for writing the sensitive areas of NAND that would normally be signature checked. With some testing were able to write a few 1KB chunks without issue, when tried a whole image it bricked, failing security check on next boot. Have some ideas how to get around that though, maybe better to try when a working RSD/SBF combo is available for easy recovery
Click to expand...
Click to collapse
RSD 5 is in the release thread now, seems to be working here so far

t0dbld said:
can you write to /sys folder with mounting ? if so i will stop what im doing as i have something to try
Click to expand...
Click to collapse
Are you trying to write to /sys or /system? Also, what are you trying to do?

ok serious question that might sound dumb.
how far are from unlocked bootloader ?
i mean i see everyone is so excited. but i dont know what does that mean .
can someone explain to me in simple way so i can thank him ? lol

[RECOVERY][Experimental][OS2SD/Internal][f2fs]TWRP2.8.0.0-multi

TWRP 2.7.1.0 multi-mode recovery. 2.7.1.0 v3 was the first release for p500, (thanks to @HardLight for advising, testing, and posting it. And for making a p500 OS2SD ROM to justify it.)
v1 and up are for thunderc (Optimus V/S), there's a separate thread over there in the appropriate forum.
Now with f2fs! Thanks @HardLight
OS2SD/Internal All-In-One. Switch modes under Advanced. It tells you on the title bar which mode it's in.
It'll flash gapps or PurePerformances or what have you to either the p2/p4 sdcard partitions for OS2SD or the internal partitions.
This has a special partitioner to set up your card for OS2SD. In OS2SD mode, go to Advanced then Partition. Set your sizes, it isn't aware yet of the whole card size (yet) so it'll just tell you if you go over and refuse to format it.
Whatever is left after your system/swap/data is your /sdcard size.
If it's in Internal mode the partitioner does sd-ext and swap instead. same deal, the leftover space is your /sdcard size.
Under the Wipe -> advanced menu, you can now select either system or data and press the 'repair or change filesystem' bar at the bottom, select change filesystem, select f2fs.
TLS enabled, system/data MTD swap on internal mode to match post-7/12/2014 androidarmv6 builds. Won't flash older ROMS or ones without the MTD swap correctly.
I am working on making it compatible with older builds too... but not yet. You may have to use a new update-binary to flash older zips. Or grab the older one from this zip file.
download, shared folder here:
Experimental, may be glitchy! Enjoy!
source on github

reserved
reserved against whatever need

reserved
I suspect I'll need more than one extra post to cover important stuff that won't fit in the OP.

On the portal today was announced a recovery-switcher app. One could have the mtd swapped and not-mtd swapped recoveries, or a cwm and a twrp recovery on the sdcard and use the app to switch between them. Do not know if this baby would work on a P500, though.
Would rather have a decent all-in-one, but that 5meg limitation may make this impractical (for example, the cwm has lost its sdcard partitioning functions).

bigsupersquid said:
TWRP 2.7.1.0 multi-mode recovery. v4. ...
OS2SD/Internal All-In-One. Switch modes under Advanced. It tells you on the title bar which mode it's in.
It'll flash gapps or PurePerformances or what have you to either the p2/p4 sdcard partitions for OS2SD or the internal partitions.
Experimental, may be glitchy! Enjoy!
source on github
Click to expand...
Click to collapse
So if understand correctly i'll flash the mod "buttons search<->power" & other zip files normally and not have to put the files into the rom manually or edit the updater script etc.:victory: thanks a lot
testing...

Dovidhalevi said:
On the portal today was announced a recovery-switcher app. One could have the mtd swapped and not-mtd swapped recoveries, or a cwm and a twrp recovery on the sdcard and use the app to switch between them. Do not know if this baby would work on a P500, though.
Would rather have a decent all-in-one, but that 5meg limitation may make this impractical (for example, the cwm has lost its sdcard partitioning functions).
Click to expand...
Click to collapse
that thing on portal reflashes the recovery every time to change it.
you could just as easily use flashable zip recoveries...
xdema said:
So if understand correctly i'll flash the mod "buttons search<->power" & other zip files normally and not have to put the files into the rom manually or edit the updater script etc.:victory: thanks a lot
testing...
Click to expand...
Click to collapse
that specific mod, you'd have to fix the updater-script to use it for os2sd, because it specifies MTD mounts.
mount("yaffs2", "MTD", "system", "/system");
pa_gapps and CrossBreeder and other more generic zips use
busybox mount /system
//edit: proper syntax:
run_program("/sbin/busybox","mount","/system");
instead of trying to call out the filesystem type.

bigsupersquid said:
that thing on portal reflashes the recovery every time to change it.
you could just as easily use flashable zip recoveries...
that specific mod, you'd have to fix the updater-script to use it for os2sd, because it specifies MTD mounts.
mount("yaffs2", "MTD", "system", "/system");
pa_gapps and CrossBreeder and other more generic zips use
busybox mount /system
instead of trying to call out the filesystem type.
Click to expand...
Click to collapse
i'll check the updater script, thanks for the pureperformance thinks, i discover a another method to speed up the p500 :fingers-crossed:

bump
f2fs enabled for OS2SD.
uses updater script like so:
mount("f2fs", "EMMC", "/dev/block/mmcblk0p4", "/data");
to use f2fs /data go into Wipe menu, advanced, select data checkbox, press 'repair or change filesystem' bar, change filesystem, f2fs. accept.
you only have to do that once to change from the default ext4 partition type.
it handles /system f2fs as well.
mount("f2fs", "EMMC", "/dev/block/mmcblk0p2", "/system");
change the filesystem the same way as data.
new 3.0.101 kernel but I noticed no differences in recovery except the working f2fs. Thanks @HardLight.
for now, attached .img for you who really have to experiment. I haven't tested this one very much on thunderg, just thunderc. basics tested on thunderg.
flashable zip added to shared folder linked in OP.
there's a little something extra in the shared folder...
I'm also uploading ROMs for the adventurous.
f2fs-system and f2fs-data os2sd builds if you're brave enough to try them. change both system and data to f2fs in recovery before flashing the rom unless you've already done that with an earlier version.
I don't have cell service to test but it's basically an androidarmv6 build plus 3.0.101 kernel and f2fs os2sd. everything else looks like it works to me.
I added Email, Apollo, Speech Recorder (which tunes up voice search I think), emojii in messaging and aosp keyboard, and extra wallpapers. Including Grass live wallpaper (which does actually work on armv6, it just looks for some network function and errors out ... I patched it,) and it reverts to building libcamera. Plus hackers keyboard because I like arrow and tab in terminal. No voice search in hackers keyboard though.
...

bump for twrp 2.8.0.0
no other fixes or anything, just a rev up for twrp.
I'll upload in an hour or so. //edit: well, maybe not so soon. I can't test at the moment since my o1 went into a no-boot loop. perfectly good running rom on it too. bah.
take me the evening to fix it.

bigsupersquid said:
bump for twrp 2.8.0.0
no other fixes or anything, just a rev up for twrp.
I'll upload in an hour or so. //edit: well, maybe not so soon. I can't test at the moment since my o1 went into a no-boot loop. perfectly good running rom on it too. bah.
take me the evening to fix it.
Click to expand...
Click to collapse
i'm testing your's 0509
in this you made the on boot fix?
##fix "add_tid_to_cgroup failed to write" errors
chmod 0660 /dev/cpuctl
# allow reading kernel command line
chmod 0644 /proc/cmdline
Click to expand...
Click to collapse
thanks
could you say to me if it's normal this:
i make the wipe of the /system in twrp, then if i go to "repair or change fs" it show size 390mb, used 110mb
but if i make a wipe or a "change fs", used space shouldn't be 0mb?
is the same for /data.
i un/mounted the partitions before, but have always some mb used in both.
hum minitool show me that the two f2fs partitions are fully used, maybe it can't read the f2fs, however i've formatted the partitions again in ext4 and now retry the f2fs format via twrp
edit: however, after 2nd format in the end /data have 144 mb used, /system 110mb. so i suspect it's normal

xdema said:
i'm testing your's 0509
in this you made the on boot fix?
thanks
could you say to me if it's normal this:
i make the wipe of the /system in twrp, then if i go to "repair or change fs" it show size 390mb, used 110mb
but if i make a wipe or a "change fs", used space shouldn't be 0mb?
is the same for /data.
i un/mounted the partitions before, but have always some mb used in both.
hum minitool show me that the two f2fs partitions are fully used, maybe it can't read the f2fs, however i've formatted the partitions again in ext4 and now retry the f2fs format via twrp
edit: however, after 2nd format in the end /data have 144 mb used, /system 110mb. so i suspect it's normal
Click to expand...
Click to collapse
looks normal to me, ext4 uses "only" about 16MB after format but f2fs uses a lot more.
minitool will only work right if your kernel supports f2fs and I doubt m$ware does right now.
and the fix din't get migrated from the overrides in thunderc to p500 yet, sorry, was a 'for fun' build to share after a recent repo sync.
this one probably has a built libcamera instead of the froyo as well. (reversion)

reverted to twrp 2.7.1.0
2.8 kept bootlooping my o1.
one too many passes with kdz, it's total blackout no power, and I'll have to jtag it now.
be a while before I release another update unless I find an o1 with fastboot.

bigsupersquid said:
reverted to twrp 2.7.1.0
2.8 kept bootlooping my o1.
one too many passes with kdz, it's total blackout no power, and I'll have to jtag it now.
be a while before I release another update unless I find an o1 with fastboot.
Click to expand...
Click to collapse
My 01 does have fastboot e.e

andrea210701 said:
My 01 does have fastboot e.e
Click to expand...
Click to collapse
I meant that I can use. HardLight pointed me to the method to enable it... if I hadn't completely fried my firmware. no backlight even, much less lg logo or emergency mode.
eventually I'll find another p500 for development (I can't use gsm phone on my service) but the going rate on ebay is $50 and I can't justify that for a hobby.
unfortunately it's too tweaky and time consuming for me to remotely develop by having someone else debug, so any more p500 stuff will be untested and slightly sketchy because of that.

Project [F2FS] [OS2SD]
[F2FS] [OS2SD] it can work with any other rom? Thanks.

cwm6.0.5.3oldMTDmounts_p500.zip
I do not know what it is? Sorry for the little understood...

Any PlayStore said:
cwm6.0.5.3oldMTDmounts_p500.zip
I do not know what it is? Sorry for the little understood...
Click to expand...
Click to collapse
clockwork mod v 6.0.5.3 for pre-tls roms (before androidarmv6 swapped the system and data Mount points in the kernel) used for kitkat roms around July 2014 or earlier or other 4.4 roms without the MTD partition swap

[RECOVERY]Safestrap 3.75 for unused partitions (/preinstall & /webtop)

This version of SafeStrap is based on SafeStrap 3.75 but has a lot of differences with it:
- there is not more the splashscreen during the boot, to enter in Safestrap you have to select BP Tools in the Boot Mode Selection Menu(VolUp&&VolDown+PowerOn)
- has been added a Safe Rom slot that uses the unused partitions:
/preinstall (~ 600mb) for /system
/webtop (~ 1,4gb) for /data
/cache is shared with the Stock Rom slot
- in this version you have 6 slots: the Stock Rom slot, the Safe Rom slot and the four virtual slots
- the Safe Rom slot is faster than any virtual slot and safer than the Stock Rom slot
If you are using the original Safestrap you can simply install this new version over it and you will still have your roms in the virtual slots.
This version of Safestrap works like any other version of Safestrap and you can use the Stock Rom slot and the four virtual slots as you are usually do, the only thing that is a bit complicated is to install an aosp rom in the new Safe Rom slot that i provided in it.
DOWNLOAD AND GUIDE TO USE THE SAFE ROM SLOT
HOW TO POST REQUEST FOR HELP:
You have to entirely read this thread, I do NOT answer redundant question.
I do not answer to requests for help in private, I have neither the time nor the interest in doing so.
Any doubts, questions or requests must be posted in this thread in order to answer a single time and help everyone.
XDA:DevDB Information
Safestrap 3.75 for unused partitions (/preinstall & /webtop) , Tool/Utility for the Motorola Droid 4
Contributors
Mentor.37
Version Information
Status: Stable
Created 2015-02-21
Last Updated 2016-01-05

This thread is not about the ramdisks so do not ask about them.
In case of problems you can build the ramdisk as i explained in the main thread.

Super, i wait for some time for someone to make this. I'v tested this with cm12 to safe slot but blank screen. Some progress in this kexec problem ? Also SS revovery splash screen is not so but as turning of device and keys combo pressing.

I rechecked everything more and more times but seem to me that everything is ok, for now I do really have not idea on where could be the problem.

Solved
Good news, I understood where is the problem with the roms that use a kexec kernel and the problem was not in my modded recovery but in the rom's ramdisk. I'm now running the cm11 in my safe slot.
I will correctly describe how to run a kexec rom in my safestrap version in the next days, for now i'm a bit busy.

Mentor.37 said:
Good news, I understood where is the problem with the roms that use a kexec kernel and the problem was not in my modded recovery but in the rom's ramdisk. I'm now running the cm11 in my safe slot.
I will correctly describe how to run a kexec rom in my safestrap version in the next days, for now i'm a bit busy.
Click to expand...
Click to collapse
could the partitions be formated fs2fs ?
Regards

For now they can be formatted only as you can format the stock rom or any slot in the standard safestrap but should not be difficult add this option in safestrap but i can't ensure you that they will work, as far as i know the aosp roms require an ext3 or ext4 fs for /system and /data.
#Postedit
I have never used safestrap before this my project and for this i did not know it well, now i saw that the f2fs is the fs used for the virtual stlots and yes i can format these partitions as f2fs the first time that the safe slot is selected but for now i'm using the cm11 in this slot with the partitions formatted as ext3 and the rom is really really fast.

Final version
I just uploaded the final version in which i also restored the capability to use the virtual slots.
If you are using my previous debug version or if you are using the original safestrap 3.75 you can simply install this new version over them and you will still have your rom in the safe slot or in the virtual slot.

Yes, i know that i told that the previous was the final version but i just uploaded a little update that fixes a problem in the layout of the new safe slot menu.

Mentor.37 said:
For now they can be formatted only as you can format the stock rom or any slot in the standard safestrap but should not be difficult add this option in safestrap but i can't ensure you that they will work, as far as i know the aosp roms require an ext3 or ext4 fs for /system and /data.
#Postedit
I have never use safestrap before this my project and for this i did not know it well, now i saw that the f2fs is the fs used for the virtual stlots and yes i can format these partitions as f2fs the first time that the safe slot is selected but for now i'm using the cm11 in this slot with the partitions formatted as ext3 and the rom is really really fast.
Click to expand...
Click to collapse
I was thinking to add fs2fs support to the kernel and see how it works, like otterx project.
thanks for your work !
regards

Thank you for great work. I'm now trying CM11 in safe slot. Everything looks great, it run very fast compared to cm12. I have one question: How can I edit cm12 ramdisk.img? I've tried "Android Image Kitchen 2.0" with no luck. Thanks for help.

In the cm12's ramdisk.img there is the file safestrapped.cpio before the real ramdisk so you have to split them with an hex editor (1F 8B 08) then you can extract the ramdisk, edit it, repack it and finally recreate the ramdisk.img reconcatenating with the hex editor the file safestrapped.cpio with the edited ramdisk.
Anyway yesterday night i attached at the main thread two flashable zips that install an edited ramdisk.img with an addon.d script that makes it persistent for the cm11 m12 and for the cm12 nightly. In this way anyone can try these roms in the Safe Slot.
I'm trying the cm12 in the safe slot from yesterday and it works flawless, it is faster than the cm11 used in the same slot, i suppose thank to the ART.

Mentor.37 said:
In the cm12's ramdisk.img there is the file safestrapped.cpio before the real ramdisk so you have to split them with an hex editor (1F 8B 08) then you can extract the ramdisk, edit it, repack it and finally recreate the ramdisk.img reconcatenating with the hex editor the file safestrapped.cpio with the edited ramdisk.
Anyway yesterday night i attached at the main thread two flashable zips that install an edited ramdisk.img with an addon.d script that makes it persistent for the cm11 m12 and for the cm12 nightly. In this way anyone can try these roms in the Safe Slot.
I'm trying the cm12 in the safe slot from yesterday and it works flawless, it is fastest than the cm11 used in the same slot, i suppose thank to the ART.
Click to expand...
Click to collapse
Excellent! It works like a charm! Now i can swap SD-card and internal storage etc... Thank you Mentor!

Thanks, Mentor.
This is a brilliant idea, and it works perfectly.
It seems crazy not to use this, if you don't need /preinstall or /webtop.

Mentor.37 said:
In the cm12's ramdisk.img there is the file safestrapped.cpio before the real ramdisk so you have to split them with an hex editor (1F 8B 08) then you can extract the ramdisk, edit it, repack it and finally recreate the ramdisk.img reconcatenating with the hex editor the file safestrapped.cpio with the edited ramdisk.
Anyway yesterday night i attached at the main thread two flashable zips that install an edited ramdisk.img with an addon.d script that makes it persistent for the cm11 m12 and for the cm12 nightly. In this way anyone can try these roms in the Safe Slot.
I'm trying the cm12 in the safe slot from yesterday and it works flawless, it is fastest than the cm11 used in the same slot, i suppose thank to the ART.
Click to expand...
Click to collapse
Can you also add patch for cm 10.2.1 ?

Anyone can build by itself a ramdisk to use a rom in the Safe Rom slot with these passages:
1) unpacking the ramdisk.img with this command:
Code:
gunzip -c ../ramdisk.img | cpio -i
N.B.: for the roms based on LP the procedure is a bit more complex and i explained it some post above
2) editing the file fixboot.sh as explained in the main thread
3) repacking the new ramdisk.img with this command:
Code:
find . | cpio -o -H newc | gzip > ../ramdisk.img

Excellent work!

Mentor.37 said:
Anyone can build by itself a ramdisk to use a rom in the Safe Rom slot with these passages:
1) unpacking the ramdisk.img with this command:
Code:
gunzip -c ../ramdisk.img | cpio -i
N.B.: for the roms based on LP the procedure is a bit more complex and i explained it some post above
2) editing the file fixboot.sh as explained in the main thread
3) repacking the new ramdisk.img with this command:
Code:
find . | cpio -o -H newc | gzip > ../ramdisk.img
Click to expand...
Click to collapse
For some strange reason I cannot repack new ramdisk.img for cm 10.2.1

I have a problem - the safe slot is there but, it shows that it has 0 MB (0 MB Free) in Data. I still did try to install CM11 (M12) there. It did installed successfully, but after rebooting it stuck (at least I think it did) on the CM boot animation. It stayed there for good half a hour so I thought there is a problem. So i restarted and went back to stock (have CM12 there, I wanted to test a CM11 a bit if it would be snappier as it probably is more developed and than switch those two as CM12 has nightly updates and there is risk of bricking the phone with daily flashes)
Anyway is showing 0 MB in Data normal and /preinstall and /webtop are used anyway or is it wrong?
Thanks!

dutohlav said:
I have a problem - the safe slot is there but, it shows that it has 0 MB (0 MB Free) in Data. I still did try to install CM11 (M12) there. It did installed successfully, but after rebooting it stuck (at least I think it did) on the CM boot animation. It stayed there for good half a hour so I thought there is a problem. So i restarted and went back to stock (have CM12 there, I wanted to test a CM11 a bit if it would be snappier as it probably is more developed and than switch those two as CM12 has nightly updates and there is risk of bricking the phone with daily flashes)
Anyway is showing 0 MB in Data normal and /preinstall and /webtop are used anyway or is it wrong?
Thanks!
Click to expand...
Click to collapse
Both preinstalled and Webtop should have data in them, before you wipe them, what are total sizes?
Sent from my XT907 using Tapatalk

How do you unpack and repack boot.img?

NOTE: Unfortunately I've had to remove links from this post because I'm a new user. I'll add them back in once I have enough posts.
I've been trying to edit a file in boot.img from the CyanogenMod 12.1 (huashan) nightlies but I'm experiencing some issues finding the right tools/methods for the job.
Most scripts I've found expect an Android Magic number at the beginning of the file but this simply isn't there. It seems there is no header at all that matches the specification from bootimg.h (missing link) though I did discover the cmdline argument at the end of the file with a hex editor.
After searching and experimenting for hours I found a script here (missing link) which enabled me to extract the kernel and ramdisk images despite the missing header but now I don't know how to repack the files into a boot.img of the same structure.
I've tried the following but it results in a boot.img that is about 40% larger than the orginal (despite me only adding one line of code) and has an entirely different structure (with an Android Magic number, etc.).
Code:
mkbootimg --base 0x00200000 --pagesize 2048 --kernel boot.img-kernel.gz --ramdisk newramdisk.cpio.gz -o newboot.img
I found this resource (TWRP, missing link) which mentions that Xperia devices have special boot images (or something like that, I didn't understand all of it) - this might explain why the boot.img structure is so different - but I can't find any further documentation on this or instructions on how to deal with the format.
The Xperia devices have a recovery-in-boot arrangement. This means that the recovery is booted using the regular kernel / boot image in the device. Team Win has worked with the FreeXperia device maintainers to come up with a way to extract the ramdisk from the FOTAKernel partition and use the ramdisk from that partition instead of the recovery that is included in the boot image of your device. This means that if you install current CM nightlies and flash TWRP to the FOTAKernel partition, you will be able to use TWRP instead of the CWM or CM recovery that normally comes in a CM boot image. Other boot images including stock kernels can be repacked to include this extraction utility to allow you to use TWRP from the FOTAKernel partition. This setup allows you to choose what recovery you want to have installed and allows you to update your recovery more easily. Unfortunately this setup requires that the boot image that you have installed include the ramdisk extraction utility.
Click to expand...
Click to collapse
So now I'm at a loss at how to continue. I would much appreciate any pointers, ideas or help in general.

@infernalpostcard , hopefully this tool made by @Adrian DC will help you out.
https://github.com/AdrianDC/android_huashan_bootimg_editor

Raienryu said:
@infernalpostcard , hopefully this tool made by @Adrian DC will help you out.
https://github.com/AdrianDC/android_huashan_bootimg_editor
Click to expand...
Click to collapse
Thanks. This looks really promising. I'm trying it out now...
EDIT: It worked! This is exactly what I needed. Unfortunately what I was actually trying to achieve (apply a fix to break a boot-loop my phone gets in, due to an encrypted filesystem) didn't work so I'll have to come up with new ideas.

[RECOVERY][EXPERIMENT/TEST] TWRP 3.2.1.x for TF701T

Hi, I don't post much on here but I wanted to share something with everyone since this is one of my fav tablets (before one of my drives crash and the data is lost, lol).
Disclaimer: I'm providing this AS-IS, I've been using this for about a few weeks now and while there may be bugs, it's been working for me and figure I'd share a newer version of TWRP for the TF701T. This will need some testing, I haven't tried flashing a newer rom - just using a "dirty port" of Remix OS I'm using (SK1WG base).
Hopefully this helps someone who loves this lil tegra transformer as much as I do!
I'll post links to source later on but to build this but if anyone wants to try;
-I used a slightly modded version of the zombi-x device tree
-tweaked the rm-wrapper (from the timduru katkiss device tree) so it references the correct includes (I was building under zombi-x 5.1 using omni twrp 8.x)
-Since the device tree was already using a prebuilt kerenel, I plugged the one from the TWRP 2.8.x kang/area51 by sdbags release
-The "rom base" folder I was building under was "zombi-x" 5.1/LP
-and the TWRP sources were from omnirom's oreo/8.x source
Here's a link to my dropbox tf701t folder, I keep a backup in the recovery folder.
I also built a 3.0.0.0 "area51" version, think I found that in the zombi-x repositories also. Both booted, roms I had installed, backups were made and restored under both however I've used the 3.2.1.x version more exetensively.
DROPBOX TF701T LINK!
Anyways, happy holidays everybody! I'll try and keep up with this post and update things when I get a chance, but for now rock on!
PS. Should be able to
Code:
fastboot boot <recoveryimagefile.img>
to test it before flashing permanently with
Code:
fastboot flash recovery <recoveryimagename.img>
PS2. Added images to post for 3.2.1.0 and the "Area51" 3.0.0.0 builds, Enjoy!
PS3. UPLOADED SOURCES! (finally, lol)
DEVICE TREE
-The device tree is still setup to use the prebuilt kernel (I compiled from source posted below this, with gcc 8.x toolchain). If using the kernel source below, use recovery_tf701t_defconfig - otherwise just make sure whatever config you run is setup to use LZMA for ramdisks here.
-Also this device tree is setup to use F2FS, I left the original ext4 fstab files included with a ext4_* prefix if anyone's curious. I'll fix that eventually and split them into 2 branches (ext4-only and f2fs).
KERNEL SOURCE
-This experimental kernel has some tweaks, F2FS support (no encryption), O/C @ ~2.5Ghz, bunch of extra governors (lionheart works nicely), but in it's base form works great for booting recovery.
Hopefully this stuff helps others bulding for this awesome lil tablet! Back to some more compilations while I got time.
UPDATE: F2FS Test (12/30/17)
-Added a recovery build that I have been running for a bit with F2FS support
-Use this with a ROM that supports F2FS, or repack a boot.img with a F2FS kernel and mod the ramdisk (edit fstab to mount /data /system and /cache with F2FS.).
-It supports the usual ext4 and other filesystems, but defaults to f2fs when using the format data and wipe commands (modded fstab on /system /cache /data).
-Also haven't had any issues formatting /cache, or touch not working with this kernel. I'll get around to a normal ext4 version and upload that as it seems to fix the /cache issues.

Just here to say it all works as before and there aren't any new/strange problems. The issues with not being to format /cache and so on without going back and forth to ext4 still persist, though.

hitmancho said:
Just here to say it all works as before and there aren't any new/strange problems. The issues with not being to format /cache and so on without going back and forth to ext4 still persist, though.
Click to expand...
Click to collapse
Glad it works for you too, I noticed the /cache issue also on the other TWRP 2.8.x version posted for this tablet too. One thing that I do (even on the other TWRP) is wipe the partition I want (or change its fs type) first, and if I need to touch another partition then I reboot the recovery and it works.
It's annoying, I'm currently testing building the kernel inline instead of using the 2.8.x kernel (from that other posted recovery) in the device tree. I'm using sources that I know boot, just playing with the configs to see how it plays with TWRP. I ported over the f2fs stuff from the katkiss kernel to mess around with, boots in the rom fine - so if I can get it to boot recovery then the f2fs formatting stuff should work and mount correctly.
Sidenote - one thing I notice with the 3.2.1-0 version is the screen seems to work better, I haven't had the touchscreen not responsive issue I had with the previous TWRP 2.8.x version.
Going for a coffee, I'll play around with it tonight (and remember to upload stuff to my github eventually to share). Long day of work, time to unwind

Small Update (Progress is good!)
So, took some time to dig around why it wasn't booting the recovery when I built from the same (working) kernel source I'm booting the normal android os with. Turns out, most likely due to space savings, the recovery is set to boot LZMA - turned that on in the config and that kernel now booted up recovery perfectly!
I'm rebuilding the kernel, since in my infinite wisdom, I compiled with my selinux disabled kernel - which also worked, but bombed out on any rom zips that ran anything to do with contexts/perms. Good news was F2FS worked mounting, formatting, etc.. Hopefully tomorrow I'll have a selinux friendly f2fs supporting kernel for recovery that'll work.
Random sidenote: I was eyeing the newer kernel drivers (from 4.x), If everything works as it's currently configured, I'll give try backporting the newer stuff and see how she runs. Just wanted to post a small update with some notes just in case anyone in wants to try building it themselves.

Thanks for your work! If you could manage to fix the format issues with current TWRP, that would be excellent. I've never been able to dirty flash due to this pesky recovery problem, I always have to go back and forth to ext3 -> ext4 and then flash clean and restore my apps .. quite a bit of time waster.

silverchairbg said:
Thanks for your work! If you could manage to fix the format issues with current TWRP, that would be excellent. I've never been able to dirty flash due to this pesky recovery problem, I always have to go back and forth to ext3 -> ext4 and then flash clean and restore my apps .. quite a bit of time waster.
Click to expand...
Click to collapse
I need to reformat /system and /cache only - most times. No need to reinstall apps.

You're lucky then, I always end up with errors on dirty flash and format /data also fails, so I resort to changing FS. Sometimes even this gives errors and I need to do it several times until errors are gone.

I just restart recovery and try formatting again.

AmauryRR great work! Please use the memory card of the docking station

Sorry for offtop, but... I saw on your dropbox remixOS. Where I can find info about how to install it? Main theme on tf701t about remix os is not having this. (or i am blind).

I haven't tried flashing a newer rom - just using a "dirty port" of Remix OS I'm using (SK1WG base)
Click to expand...
Click to collapse
Can you, please, describe how it is working?
---------- Post added at 11:22 AM ---------- Previous post was at 11:20 AM ----------
Sasisco said:
Sorry for offtop, but... I saw on your dropbox remixOS. Where I can find info about how to install it? Main theme on tf701t about remix os is not having this. (or i am blind).
Click to expand...
Click to collapse
Yes, please, more info on that!

Tf701t update
Hi AmauryRR,
Any chance you could break the process down step by step for none-IT people like me? i have tried everything but think i have to accept that this is above my pay grade .
i am especially having a difficult time with the boot loader. Indicates the following: "An unknown error occurs, which may be a network......try again later"
i can email you the screenshots as i can't seem to upload them here.
regards
rob

Can someone get me recovery work in android 4.2.2 ,
10.14.1.47 bootloader please?
"" I searched in google all recovery file can't be downloaded''

Any chance of a flashable version of this?