Database Info

[Q] recovery.img and recovery-from-boot.p

Hi all,
I am trying to make sense of how the android system is made up w.r.t to boot/kernel.
I have been looking at the .img files in the build (I built for the "passion" device), and have been googling around to find some more information about the various .img files.
I ran into a nice HOWTO in android-dls.com 's WIKI, titled HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images (I'm sorry, I'm a new user so XDA won't allow me to post links. I will try to modify my post a soon as I'm granted permission for that)
but I am afraid it is a little outdated:
I have several questions, but I will try to be brief, so I'll focus on
one of them, and if that works I'll proceed to the next questions, all related to "Android bringup for dummy embedded linux kernel experts".
I am fairly aware of differences between different linux
configurations, and I am very familiar with linux bringup concepts, so I will just use common examples from the linux world as my terminology. Hope it will be clear enough.
I understood that boot.img a combination of a kernel (e.g. bzImage in linux) and an initial ramdisk (e.g. initrd.gz), wrapped by some header, as in common linux kernel loading practice (piggy.o etc.).
Now, the aforementioned HOWTO says that the "recovery" image is built on
the same way, and that it is stored on the target's /system/
recovery.img .
I would assume that this would be compound of the ramdisk-
recovery.img, and some other kernel.
Now, the problem is that:
1. This /system/recovery.img does not exist from what I saw (on my
Motorola XOOM tablet)
2. What does exist is /system/boot-from-recovery.p , which is
created during the boot process in obj/PACKAGING/
recovery_patch_intermediates/recovery_from_boot.p .
I saw tons of posts referring to the files, all said that "in order to
replace the rescue disk image, this file needs to be renamed" - but I
am looking for a way to figure out what it is, and how to extract its
contents.
I assume /system/recovery.img is deprecated, is that correct?
3. I did not see any flash devices in /proc/mtd (which is strange).
I searched for hours before sending this post, so I would appreciate
your help. I also posted a similar message at the google android-building group, but it has not been answered yet, and I got the impression that these forums are more active and can help me get where I need.
If it is not the right place to ask the question please let me know -
I just assume this is a general android concept and not device
specific.
Thanks,
Ron

I meant of course /system/recovery-from-boot.p , and not recovery-from.boot.p
-R

Hi,
I don't know if you managed to find out what "recovery-from-boot.p" is, since this is quite an old post, but I think I'll try to help anyway.
recovery.img is not deprecated at all. From my own experience, it looks like "recovery-from-boot.p" is a protection measure introduced in Gingerbread, but not the recovery itself. What it does is replacing any recovery currently installed on the phone with the default one on every boot.
I discovered it after flashing a custom recovery on my Android 2.3.4 phone. It worked, but just during the first boot. The next time I rebooted the phone, the default recovery image was there again. After browsing several sites, I found that "recovery-from-boot.p" is responsible for that.
So, if you flash a custom recovery image on a Gingerbread phone and want to keep it forever, you must delete this "recovery-from-boot.p" from /system, or at least rename it. That way, your new custom recovery will never get overwritten buy the default one, unless you do it yourself.
I hope this helps you and clarifies this question.

Well, it helped me. I'm new to rooting and just came across mention of this file. I am trying to learn 'why' as well as 'how'', so your post was informative.

Was going to ask a dumb question but I figured it out

i need to delet those files
bigrammy said:
Was going to ask a dumb question but I figured it out
Click to expand...
Click to collapse
Hello
can't delete those files >> i am rooted but every time i delete or rename it take permission then nothing happen >> how i can delete them plsssssssssssssssssssssssssssssssssssssss

recovery from boot p
ahmed morsy said:
Hello
can't delete those files >> i am rooted but every time i delete or rename it take permission then nothing happen >> how i can delete them plsssssssssssssssssssssssssssssssssssssss
Click to expand...
Click to collapse
Hey good day. Did you get your problem fixed...? I have an xt912 it has the same file. For days I've been trying to wipe the phone. Tryed rooting it. I tryed reprogramming it. And I got through with all of that. But everytime the phone boots up it goes back to the same state. Then I used a root browser and while exploring I saw this recovery from boot file. I need help. And I don't think I can downgrade the Motorola phones. Thanks in advance.

jman0 said:
Hi,
I don't know if you managed to find out what "recovery-from-boot.p" is, since this is quite an old post, but I think I'll try to help anyway.
recovery.img is not deprecated at all. From my own experience, it looks like "recovery-from-boot.p" is a protection measure introduced in Gingerbread, but not the recovery itself. What it does is replacing any recovery currently installed on the phone with the default one on every boot.
I discovered it after flashing a custom recovery on my Android 2.3.4 phone. It worked, but just during the first boot. The next time I rebooted the phone, the default recovery image was there again. After browsing several sites, I found that "recovery-from-boot.p" is responsible for that.
So, if you flash a custom recovery image on a Gingerbread phone and want to keep it forever, you must delete this "recovery-from-boot.p" from /system, or at least rename it. That way, your new custom recovery will never get overwritten buy the default one, unless you do it yourself.
I hope this helps you and clarifies this question.
Click to expand...
Click to collapse
i have deleted it . then flash recovery ,, but it failed .. it wont even now go to stock recovery itself.. any help..

Does recovery from boot has to do anything with ota update applying ? or it will cause issues in system update ?

I have recovery-from-boot.p in my system and i cant root my phone i cant change the recovery img ... Help?

I hadn't had to deal with this for some time, perhaps because I've updated my devices (Nexus 4, Nexus 5, Nexus 7 '13) with the factory images, with "-w" removed from flash-all, then flashing CWM's recovery, ensure SuperSU was installed, then continuing. Today, I used the new OTA image on my Hammerhead/N5, and recovery-from-boot.p seems to be up to its old tricks again.
Solution is simple.
Flash your alternate Recovery in fastboot, fastboot flash recovery [recovery image file] . Boot into Recovery. Apply/install root app (typically via sideload). Mount /system. adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.bak. Reboot. Done. (If you're unfamiliar with fastboot, adb, and flashing new recovery partitions, you have some reading to do. Commence RTFM.)
I also used to have to move /system/etc/install-recovery.sh but that seems to be gone in Marshmallow. :} Or moved...?

well, after following a guide I have extracted the system.img from a pure-nexus ROM(The ROM I'm currently using), now I can see that "recovery-from-boot.p" file is responsible for recovery lock in my phone. I'll keep it short and straight to the question
"Can I remove this file and rebuild the .dat file and flash it?, so that I won't have any other problems at all"
I want to know if recovery-from-boot.p file is linked to anything other than just locking the recovery or re-flashing it innumerable times.

[A510/A511] [WIP] Stock ROM dumps - Get back to factory state

As we now have functional recovery options on our tablets, and people will inevitably mess things up with their device, we need to get a way to get your tablets back to factory condition. But I need your help with this!
What do you want?
Here's my idea: We have all seen various ZIPs floating around, most of them leaked from somewhere. The problem with these is that you can't use OTA updates, and I'm not sure what Acer Service Center thinks of custom ROM installs. What I want is to build a list of software that is officially distributed by Acer, is OTA-updateable, etc. For this reason, I want people that have not yet modified their tablets (except root) to provide image dumps of their /system, /boot, /flexrom, and /recovery partition. It's really easy to do, and you'll help yourself and others when they get into trouble.
Can I help?
Answer all of the following questions. If at one point the answer is "Sorry, you can't help", well... You can't help
Is your device unlocked and rooted? Yes - You can help! / No - You can still help, but you need to unlock and root your device.
Do you have the original Acer ROM installed on your device? Yes - You can help! / No - Sorry, you can't help
Have you received the latest OTA updates for your device? Yes - You can help! / No - You can help as well!
Have you removed any apps or files from the /system or /flexrom partition? Yes - Sorry, you can't help / No - You can help!
Have you installed a custom recovery image? Yes - You can still help, as long as everything else is still original / No - You can help!
Okay, so I can help, now what?
If you can and are willing to help (remember, it could save your own ass one day), follow the instructions below. If you get stuck or simply don't know where to start but are willing to help, let us know in this thread and I'm sure we can all help eachother out.
This will not gather any personal data from you. Personal data is stored on the /data partition, which we don't need, so: No worries!
Root your device, if you haven't already.
Connect your tablet to your computer via ADB
Type the following command: adb shell. You are now logged into your tablet. You can exit at any time by typing exit and hitting ENTER.
Type the following command: dd if=/dev/block/mmcblk0p2 of=/sdcard/boot.img. This will copy your /boot partition to a file called boot.img on your internal storage. This one will be fast, it only has about 8MB to copy.
This step can be skipped if you have a custom recovery! Type the following command: dd if=/dev/block/mmcblk0p1 of=/sdcard/recovery.img. This will copy your /recovery partition to a file called recovery.img on your internal storage. This one will be fast as well, it only has about 6MB to copy.
Type the following command: dd if=/dev/block/mmcblk0p3 of=/sdcard/system.img. This will copy your /system partition to a file called system.img on your internal storage. This one will take a bit longer, it has about 360MB to copy.
Type the following command: dd if=/dev/block/mmcblk0p6 of=/sdcard/flexrom.img. This will copy your /flexrom partition to a file called flexrom.img on your internal storage. This one will take a bit longer as well, it has about 360MB to copy.
Type exit to exit the ADB shell. Copy the four .img files from your tablet (internal storage) to your computer. You might have to reboot your tablet if the files don't show up.
ZIP or RAR these files, and upload them somewhere. If you can't find a place to store them: send me a private message or reply in this thread and we'll arrange something else. If you have uploaded the files somewhere: again, send me a private message or reply in this thread.
So now what?
When I receive your files, I will package them into an update.zip that can be flashed from custom recoveries. This will then restore everything (including the custom recovery) to factory state, which can help you in getting your device back to stock.
What versions do you have already?
Acer_AV041_A510_1.044.00_WW_GEN1 (download links will follow shortly)
Acer_AV041_A510_1.098.00_EMEA_CUS1 (download links will follow shortly)
Acer_AV041_A510_1.099.00_EMEA_DE (download links will follow shortly)

The idea sounds great so far. But I have a small problem to make a complete backup for my a511.
Your linked root tutorial for the procedure is only for a100/a510 and doesn't work for a511, as I understand.
The tutorial for rooting the a511 needs first to flash a CWM.
http://forum.xda-developers.com/showthread.php?t=1729432
So it isn't possible for us to backup the recovery partition, right ?
I have the stock Acer_AV041_511_1.028.00_EMEA_DE on my device.
Is it even possible to backup and recover the baseband ?
I'm very interested in your CWM recovery for a511 too, but since many guys f++++d up their device now, I want to make sure that my device will not goes the same way.

i can help, n my tab is rooted.
but i don understand the first step: Connect your tablet to your computer via ADB

What about if we have removed system apps (such as the antivirus that comes with the tablet). It wouldn't be a complete dump if it didn't include those.
I have root and am happy to provide a dump, but I did uninstall several of the crappier pre-installed apps that came with my tablet.

scorpio16v said:
The idea sounds great so far. But I have a small problem to make a complete backup for my a511.
Your linked root tutorial for the procedure is only for a100/a510 and doesn't work for a511, as I understand.
The tutorial for rooting the a511 needs first to flash a CWM.
http://forum.xda-developers.com/showthread.php?t=1729432
So it isn't possible for us to backup the recovery partition, right ?
I have the stock Acer_AV041_511_1.028.00_EMEA_DE on my device.
Is it even possible to backup and recover the baseband ?
I'm very interested in your CWM recovery for a511 too, but since many guys f++++d up their device now, I want to make sure that my device will not goes the same way.
Click to expand...
Click to collapse
Hi, your device will not brick, I can send you a test A511 recovery if you want. Worst that can happen is that recovery won't boot, but in that case you can simply put back recovery. Send me a private message and we can work something out.

scae said:
What about if we have removed system apps (such as the antivirus that comes with the tablet). It wouldn't be a complete dump if it didn't include those.
I have root and am happy to provide a dump, but I did uninstall several of the crappier pre-installed apps that came with my tablet.
Click to expand...
Click to collapse
Then it's of no use, unless you have a backup of your pre-installed apps. Removing apps from the /system or /flexrom partition is not recommended, and you gain nothing by it: You only gain space on read-only filesystems which you won't use in 99% of situations, and you've now broken OTA's for yourself as well, as OTA's will only install when apps are present unless you start modifying OTA files.
The 'correct' way to get rid of pre-installed apps is simply freezing them, either from the settings menu or with an app like Titanium Backup. This will make it seem like they're not there (so they don't use resources at all), but the APKs don't get removed.
So unfortunately, we can't use your dumps to restore devices to factory state. Unless, ofcourse, you've made a backup of the apps somewhere.

skymario said:
i can help, n my tab is rooted.
but i don understand the first step: Connect your tablet to your computer via ADB
Click to expand...
Click to collapse
Do you have ADB or the Android SDK installed?

NoThrills said:
Do you have ADB or the Android SDK installed?
Click to expand...
Click to collapse
I just learned ADB, n successful install ur CWM, later will try to dump my stock Rom to u.
My stock Rom version 1.073 ww gen1

does it matter if the system apps have been frozen or do they need to be unfrozen first?

I have flashed that remove stock recovery mod so the stock rom doesn't keep overwriting cwm on reboot. Does that disqualify me? If not I'll dump my rom for you when I get home.
I'm on this rom version:
ro.build.pandora.id=Acer_AV041_A510_RV28RC04_PA_CUS1
ro.build.flexrom.id=Acer_AV041_A510_1.076.00_PA_CUS1

I unlocked bootloader,rooted,installed cwm then backed up my stock rom.Could i restore my stock rom then be able to send you those fills
and return to total stock.

NoThrills said:
Hi, your device will not brick, I can send you a test A511 recovery if you want. Worst that can happen is that recovery won't boot, but in that case you can simply put back recovery. Send me a private message and we can work something out.
Click to expand...
Click to collapse
i think he mean that the a511 recovery doesn't work properly....you can flash a zip, but nearly all other options brick the device
i have a a511 too with Acer_AV041_A511_1.028.00.EMEA_DE and can help with testing or something else

I have Acer AV041_A510_1.079.00_PA_CA. (Canada)
I have not done a thing to it because it is a replacement for the Galaxy Note I bricked trying to upgrade from GB to ICS, too early.
I might try again if I was sure I could get back to where I am, using your process.
I assume that your Root link is comprehensive but I also need reassurance on how to ADB.
[email protected]
Sent from my A510

blgblade said:
i think he mean that the a511 recovery doesn't work properly....you can flash a zip, but nearly all other options brick the device
Click to expand...
Click to collapse
No, as I understand, the only working methode to root the a511 is to bootloader unlock, flash the custom recovery and then the root.zip.
Maybe I'm wrong and there is another working way to root the device ?
The problem is simply, that we lost the stock recovery before we have a backup from it.
If we have another root way for a511, the backup of stock firmware is done in a few minutes and from this point we can test the a511 custom recovery from NoThrills.

To the A511 owners: Technically, if you have a install-recovery.sh file on your device, the device will always flash recovery back from the boot.img.
In theory: To test, one could simply overwrite the stock recovery with my Recovery (not the other ones, they will brick your device) and then when you reboot, your device will overwrite the recovery with the stock one again. So you really don't need a backup of the recovery partition.
As long as you don't let your device fully boot (so, stay in recovery) there's plenty of time to test if the recovery works or not. If it doesn't, simply reset your device and it will flash back the original recovery (again: provided there is a install-recovery.sh in your /system partition).
So again, if anyone is willing to test, let me know

NoThrills said:
To the A511 owners: Technically, if you have a install-recovery.sh file on your device, the device will always flash recovery back from the boot.img.
Click to expand...
Click to collapse
I can't find a install-recovery.sh in /system partition on my a511. Search on root-explorer can't find one on the device.
Even NOT on /system/etc like on other devices.

NoThrills said:
So unfortunately, we can't use your dumps to restore devices to factory state. Unless, ofcourse, you've made a backup of the apps somewhere.
Click to expand...
Click to collapse
Ah damn, I did back them up via titanium but it doesn't seem to want to restore them - it just sits there say restoring app.

scorpio16v said:
I can't find a install-recovery.sh in /system partition on my a511. Search on root-explorer can't find one on the device.
Even NOT on /system/etc like on other devices.
Click to expand...
Click to collapse
Yeah, I meant /system/etc... That's weird, I'd figure Acer would use the same system on the A511... Let me check one of the leaked ROMs...

Hello,
I have an stock Acer_AV041_A510_1.098.00_EMEA_CUS1, there we go for the files
Host file is not the stock version, it was edited by AdAway.
Can you make a version without recovery overwritting ?
I thinks a lot of people want to try some roms... just for testing...
Acer_AV041_A510_1.098.00_EMEA_CUS1 boot && system && flexroom:
http :// dl.free.fr/jDEmTNSD4
Have Fun

Hello,
I have the same rom without root or unlocked bootloader or moded recovery so if the above on does not make it I'll upload mine.
Sent from my A510 using xda app-developers app

[Q] Samsung Stellar Verizon SCH-I200 Stock Firmware

So I accidentally bricked the new Samsung Stellar and my backups got wiped during the process.
Can anyone find the stock firmware/kernel for the Samsung Stellar?
Much appreciated.

sovereign73811 said:
So I accidentally bricked the new Samsung Stellar and my backups got wiped during the process.
Can anyone find the stock firmware/kernel for the Samsung Stellar?
Much appreciated.
Click to expand...
Click to collapse
mines isnt bricked but im looking for the same thing. Deleted some stuff I shouldnt have and no getting system ui force close. Let me know if you have an luck. Ill do the same

Do you still have the stock recovery? I may be able to get into my old OS if you can get the stock recovery pulled off.
Unfortunately I'm not sure how you will extract the recovery ROM off of your phone...I'll keep looking around.

mcarrion78 said:
mines isnt bricked but im looking for the same thing. Deleted some stuff I shouldnt have and no getting system ui force close. Let me know if you have an luck. Ill do the same
Click to expand...
Click to collapse
I'm curious, have you reinstalled the pesky stock apps to see if the OS crashes would stop? There may be something to that.
Also I possibly can help you get an image but I need a recovery image. If you're still rooted, download this:
http://android.podtwo.com/romdump/
Download Terminal Emulator from the Google Play Store and then follow these instructions:
http://forum.xda-developers.com/showthread.php?t=1771347
If I can get back into my phone by restoring the stock recovery, I may be able to get you an image that works.

Uh...OK...feel free to; it keeps the topic up fresh on the first page! lol.
Anyways I managed to theorize that a recovery is all I need....dang, looks like that's both of us now eh?

Im still rooted. im trying to figure out how to pull the recovery myself to possibly help in building CWM for the phone. I know removing some stock apps is what caysed my force close i just dont know all of the ones i deleted. I didn't think to back any of them up

I've got something up there that should help you pull out the stock recovery as well.
Romdump should work and should not brick anything so please give it a try.
sovereign73811 said:
Also I possibly can help you get an image but I need a recovery image. If you're still rooted, download this:
http://android.podtwo.com/romdump/
Download Terminal Emulator from the Google Play Store and then follow these instructions:
http://forum.xda-developers.com/showthread.php?t=1771347
If I can get back into my phone by restoring the stock recovery, I may be able to get you an image that works.
Click to expand...
Click to collapse

used romdump and this is what i get. it leaves me a text file thats 2.46 know that cant be it
c:\SDK\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # /data/local/romdump
/data/local/romdump
Android ROM dumper v0.82b
(c)2011 Sebastian404
Device : IMM76D.I200VRALG4
Creating required files... cat: can't open '/proc/mtd': No such file or directory
Opening mtd table... Segmentation fault
139|[email protected]:/ #

mcarrion78 said:
used romdump and this is what i get. it leaves me a text file thats 2.46 know that cant be it
c:\SDK\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # /data/local/romdump
/data/local/romdump
Android ROM dumper v0.82b
(c)2011 Sebastian404
Device : IMM76D.I200VRALG4
Creating required files... cat: can't open '/proc/mtd': No such file or directory
Opening mtd table... Segmentation fault
139|[email protected]:/ #
Click to expand...
Click to collapse
That's complicated. It looks like you use ADB from your PC. I'm curious, is your phone stable enough to run the Romdump from the phone itself? You will need terminal emulator to do this.
There is also a method that just works for recovery and boot partitions (the ones I and a few others need). Take a look here and scroll down to the heading that says "Alternative Method If The Above Does Not Work:".
http://www.addictivetips.com/mobile...es-boot-recovery-and-system-partition-images/

i get the same thing using terminal on my phone

http://www.addictivetips.com/mobile...es-boot-recovery-and-system-partition-images/
Have you looked at this link? It even has an alternate way to use romdump.

I don't know if this has anything to do with what we need for a stock ROM but here's something interesting:
http://androidforums.com/elite-all-things-root/551775-well-lets-get-ball-rolling-11.html
Again to any of you who have a rooted Samsung Stellar, please help us with a Stock ROM image!

heres the verizon stuff you were looking for
https://www.dropbox.com/sh/chkru9gi16k9ar8/G-DHp6SgnD

Thanks, although we already have that and we got a phone fixed for it...too bad not mine.
Hey did you get the message? Here I'll post it again:
OK people: here's a tip I've received from an XDA developer expert:
Quote:
a quick and dirty explanation (need root)
Code:
dd if=/dev/block/mmcblk0p1 of=/sdcard/output.img
this will save the partition mmcblk0p1 to output.img
now, to determine what partitions are
on my device its:
Code:
ls -l /dev/block/platform/msm_sdcc.1/by-name/
but you're scheme and directory structure there might be a little different, so adjust accordingly
Longer Version:
http://www.darkyrom.com/index.php?th...with-adb.8059/

yeah i got that message and i got the output.img just havent uploaded it

What were you able to extract by chance?
If you could find a recovery partition, that would be great.

even in recovery its actually loaded to RAM and not mounted (this allows you to flash to it while in recovery)
do:
Code:
ls -l /dev/block/platform/msm_sdcc.1/by-name
(its msm_sdcc.1 on my device, yours may be different but it should be similar)
Click to expand...
Click to collapse
Another tip to extract and backup the stock recovery.

stock rom
hey so im reading the threads and i wanted to know some kind of update. Did people test out the stock rom yet? Any good news?

Yes, thankfully we've got them working (thanks invisiblek!) and I'll make a further update in a few hours.

Where is the thread for this at?
Has this been dropped all together? I was looking for some stock and/or stock-rooted roms for this thing. Any hope out there?

Possible Method to Flash ROMs without Custom Recovery on MK2 (Confirmed for MF3)

Credit goes to developer, zroice, at the International Note 3 section for his work towards this.
DISCLAIMER: I AM NOT HELD RESPONSIBLE IF YOU BRICK/BOOTLOOP/ OTHERWISE INCAPACITATE YOUR DEVICE IN ANY WAY. YOU'VE BEEN WARNED!
This has been confirmed working for the AT&T Note 3 (Thanks to drakeymcmb and Bri315317) WITH SOME PROBLEMS. Therefore, probably with some changes, this *might* work for our device. I wanted to share the information here to simply see if anyone is able to confirm or deny this for the SGH-I337.
Original Thread: http://forum.xda-developers.com/showthread.php?t=2550120
AT&T Note 3 Thread: http://forum.xda-developers.com/showthread.php?t=2554411
OP from zroice:
zroice said:
Ladies and Gentlemen I present to you the
kn0x0ut Toolbox v1.03!
(notice the 0x0 reference! hehe)
This script allows you to install custom roms, and mods that you would normally have to flash with custom recovery.
,
But as we all know, if you want to keep knox warranty void at 0x0 you cannot use a custom recovery or kernel.
If your knox warranty is already void aka 0x1 then you can still use this tool but it wont bring back the warranty...
---
This kn0x0ut toolbox itself requires root! You will have to use "Root de la vega" or some other method to get rooted while keeping your warranty intact.
---
How to use:
Extract the download from below to your internal or external sd card.
Then browse into that directory with terminal or adb shell and type:
Code:
sh kn0x0ut.sh
or
Code:
sh kn0x0ut.sh help
and you will get all the commands supported currently.
---
Check post 2 for full command list!
To install a rom or other zip you will have to extract its contents to the "extract_files_here" subfolder of kn0x0ut and then run the install command.
Code:
sh kn0x0ut.sh install
or
Code:
sh kn0x0ut.sh new_rom
(this is the command to install a new rom basically, meaning: backup and clean base, clean dalvik, install rom, reboot)
or if you want to install a rom with all the mods currently available:
Code:
sh kn0x0ut.sh new_rom all_addons
NOTE: The install script looks inside the extract_files_here folder for data and/or system folders to be copied over to the system or data folder on your device respectively.
All other folders it finds will get "ignored" (they will be copied to a folder "not_installed" which is created if the script finds incompatible folders or files). After the seperation
of the data and system folder from the unsupported ones, some dangerous libs which cannot be copied while the system runs will get removed from the temporary installation
folder so to ensure that there is no crash during the copy process. Once these files are removed the safe files get copied to your system and the permissions get fixed with
my permission fixing script.
The files that have been installed will get moved into a subfolder called "installed" and into another subfolder with the date and time of the installation.
The files that could not be installed by the script in the first run get moved to "not_installed".
These files could still become installed if you copy or move them over to the extract_files_here folder again for a second run. But remember that a data and/or a system folder is expected by the script inside the extract_files_here folder - so you have to make sure the structure is alright if you do things like this.
---
Example:
X-Note has the following folders when extracted:
META-INF, data, system, xnote.
The data and system folder will get installed, while the metainf and xnote folder wont. Inside the xnote folder you will find stuff that would normally be installed by aroma through user choice.
If you look inside there at the acid mod folder for example, there will be a system folder. To install this mod with kn0x0ut in a second run, you would have to move that system folder back
to the extract_files_here folder and then run the install command again. Only things inside data or system folder will ever be installed. And even then you gotta make sure the folder structure is
as on the system or data partition itself. (so apks need to be inside ..../kn0x0ut/extract_files_here/data/app or ..../kn0x0ut/extract_files_here/system/app to be moved to the right folder, etc...
you get it. (if not you should not use it for stuff like that)
---
This is only version 1.03 - I got more ideas to integrate but I dont wanted to hold things back any longer...
A word of warning though:
This is made for lazy people (like myself) and not for dumb people! (aka: its made to save time and ease up things and should be used with caution to not mess up things)
(for example: dont clean_base or use new_rom without actually installing a new rom or you will most likely end up without system apps and device not booting correctly - like you wouldnt wipe system in a custom recovery without installing a rom...).
It can be used over adb or terminal, but if you install a rom (clean_base) the system ui gets stopped, so better do it over adb!
It basically does the steps I described in my guide to install custom roms on knox firmware in a script, plus some other nice little timesavers.
Dont worry about error messages that say files dont exist or that they already exist! (thats normal)
Feel free to check out the source code and suggest improvements or enhancements like new mods to integrate.
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I337 using Tapatalk

Interesting...but since it doesn't flash kernels we'd still only be able to use whichever ROMs are compatible with stock kernels? I wonder how different the libs used are between the s4 and note 3

prisonnet said:
Interesting...but since it doesn't flash kernels we'd still only be able to use whichever ROMs are compatible with stock kernels? I wonder how different the libs used are between the s4 and note 3
Click to expand...
Click to collapse
You're probably right. It would be preferable for someone on mf3 to test because they would have a way to odin back to stock.

This basically sounds like framework modification. It sounds as if it might be use-able with TW based type ROMs but I doubt CM, AOSP, AOKP, or MIUI ROMs will work. If it works, it should simplify modifying the framework because it allows Devs to create certain Pseudo-Roms with many modifications to be flashed all at one time via ADB instead of needing to do several individual changes.
Take a look at the P-ROM or Pseudo-ROM thread in Android development by Nottach. It seems to be the same concept just for MDL firmwares.

phobia09 said:
You're probably right. It would be preferable for someone on mf3 to test because they would have a way to odin back to stock.
Click to expand...
Click to collapse
I'd be interested to see if this works on MJ9 / MK2 since SafeStrap isn't available for those versions yet, but I don't think there's odin available for MK2. Might be a one-way trip to bricksville.

prisonnet said:
I'd be interested to see if this works on MJ9 / MK2 since SafeStrap isn't available for those versions yet, but I don't think there's odin available for MK2. Might be a one-way trip to bricksville.
Click to expand...
Click to collapse
That's the main reason I posted this. I wouldn't want to test since I'm on mk2. I was more hoping someone on mf3 could test it and then maybe see if we could somehow tweak it for mj9/mk2 users if necessary.

phobia09 said:
That's the main reason I posted this. I wouldn't want to test since I'm on mk2. I was more hoping someone on mf3 could test it and then maybe see if we could somehow tweak it for mj9/mk2 users if necessary.
Click to expand...
Click to collapse
Going to try this after work tonight. I'm still on MF3. Read through the kn0x0ut script and no changes need to be made for this to work on our device - the partitions listed are all the same. I'll try a 4.2.2 TW Rom, then 4.2.2 GPE, then upgrade to MK2 and try a 4.3 TW and 4.3 GPE rom.
I'd be more confident trying this on MK2 if it worked on MF3 without any problems.

prisonnet said:
Going to try this after work tonight. I'm still on MF3. Read through the kn0x0ut script and no changes need to be made for this to work on our device - the partitions listed are all the same. I'll try a 4.2.2 TW Rom, then 4.2.2 GPE, then upgrade to MK2 and try a 4.3 TW and 4.3 GPE rom.
I'd be more confident trying this on MK2 if it worked on MF3 without any problems.
Click to expand...
Click to collapse
I would definitely appreciate it. If we can somehow get in touch with the same individual who uploaded the mf3 tars we may be able to get a method to flash back to stock mk2. Then we would be all set up with a way to flash without waiting on bootloader unlock or custom recovery. Looking forward to what you find out.

phobia09 said:
I would definitely appreciate it. If we can somehow get in touch with the same individual who uploaded the mf3 tars we may be able to get a method to flash back to stock mk2. Then we would be all set up with a way to flash without waiting on bootloader unlock or custom recovery. Looking forward to what you find out.
Click to expand...
Click to collapse
We also might be able to restore MK2 if someone can back up their MK2 installation using this method: http://forum.xda-developers.com/showpost.php?p=44917036&postcount=1

Would it be possible to use this to downgrade from MF3 back to MDL?? This could be very awesome...

hexagonsunja said:
Would it be possible to use this to downgrade from MF3 back to MDL?? This could be very awesome...
Click to expand...
Click to collapse
Unfortunately not. That requires a whole different level of access which, to my knowledge, no one has been able to achieve yet. Think of this as a command-line version of safestrap, without the rom slot functionality.

Interesting. I've given up hope on unlocking the bootloader for the s4. Minds much better than mine have tried and failed. If there's a way to circumvent the bootloader problem completely, this could be the holy grail for ATT S4 users! I agree that we'd probably have to stick with stock kernel ROMs, much like SS does, but it does open up an avenue of options for users.
I would volunteer, but as far as I know, there's no way to flash back to stock MK2 just yet. I can root easily enough, but I'm not going to risk a brick until there's a known flash to stock method. >_>

prisonnet said:
Unfortunately not. That requires a whole different level of access which, to my knowledge, no one has been able to achieve yet. Think of this as a command-line version of safestrap, without the rom slot functionality.
Click to expand...
Click to collapse
Ah I see, I wonder if this is the first step though... I am currently on MF3 and rooted, so I would likely be willing to try this out once others report success. I am hesitant to brick my daily driver though...

Zephcemi said:
Interesting. I've given up hope on unlocking the bootloader for the s4. Minds much better than mine have tried and failed. If there's a way to circumvent the bootloader problem completely, this could be the holy grail for ATT S4 users! I agree that we'd probably have to stick with stock kernel ROMs, much like SS does, but it does open up an avenue of options for users.
I would volunteer, but as far as I know, there's no way to flash back to stock MK2 just yet. I can root easily enough, but I'm not going to risk a brick until there's a known flash to stock method. >_>
Click to expand...
Click to collapse
I can verify that the script works on MF3. Just used it to remove then re-install the 4.2.2 GPE rom I was using with safestrap. I'm now going to upgrade to MK2 and try a 4.3 GPE rom...wish me luck

prisonnet said:
I can verify that the script works on MF3. Just used it to remove then re-install the 4.2.2 GPE rom I was using with safestrap. I'm now going to upgrade to MK2 and try a 4.3 GPE rom...wish me luck
Click to expand...
Click to collapse
Good luck! If you can verify, I'll be getting a 4.3 GPE rom myself. Godspeed!

prisonnet said:
We also might be able to restore MK2 if someone can back up their MK2 installation using this method: http://forum.xda-developers.com/showpost.php?p=44917036&postcount=1
Click to expand...
Click to collapse
I think this would be awesome, I am much too ignorant to understand; Where/how is this script to be run? Terminal Emulator? ADB? Odin itself? If it's something relatively low risk (and assuming I'm capable of doing it) I'll attempt it because I'm on MK2.
prisonnet said:
I can verify that the script works on MF3. Just used it to remove then re-install the 4.2.2 GPE rom I was using with safestrap. I'm now going to upgrade to MK2 and try a 4.3 GPE rom...wish me luck
Click to expand...
Click to collapse
GOOD LUCK! Thanks again for your contribution! :fingers-crossed:

phobia09 said:
I think this would be awesome, I am much too ignorant to understand; Where/how is this script to be run? Terminal Emulator? ADB? Odin itself? If it's something relatively low risk (and assuming I'm capable of doing it) I'll attempt it because I'm on MK2.
GOOD LUCK! Thanks again for your contribution! :fingers-crossed:
Click to expand...
Click to collapse
Just in case, I'd make an odin backup using this script http://forum.xda-developers.com/showpost.php?p=44917036&postcount=1
That way you can return to the state your phone is in now if something goes wrong - it will probably take at least an hour, and is harder to restore than a backup would be in TWRP or similar, but at least it's possible.
If you do want to give it a shot (make a backup first!), all you need to do (which I'll be doing myself after my phone finishes updating to MK2) is extract this rom http://forum.xda-developers.com/showthread.php?p=47718525#post47718525 into the "put_files_here" folder of the kn0x0ut zip, then send the whole kn0x0ut folder somewhere to your phone, like /mnt/extSdCard or just /mnt/sdcard.
Then through adb (not terminal emulator because the GUI will crash - as expected - when you delete the rom you are currently running), do sh kn0x0ut.sh install and it should automatically install the rom in the "put_files_here" folder. I think there's a new update of the kn0x0ut script coming soon that allows flashing of straight zip files, but not sure when that will be released.

prisonnet said:
Just in case, I'd make an odin backup using this script http://forum.xda-developers.com/showpost.php?p=44917036&postcount=1
That way you can return to the state your phone is in now if something goes wrong - it will probably take at least an hour, and is harder to restore than a backup would be in TWRP or similar, but at least it's possible.
If you do want to give it a shot (make a backup first!), all you need to do (which I'll be doing myself after my phone finishes updating to MK2) is extract this rom http://forum.xda-developers.com/showthread.php?p=47718525#post47718525 into the "put_files_here" folder of the kn0x0ut zip, then send the whole kn0x0ut folder somewhere to your phone, like /mnt/extSdCard or just /mnt/sdcard.
Then through adb (not terminal emulator because the GUI will crash - as expected - when you delete the rom you are currently running), do sh kn0x0ut.sh install and it should automatically install the rom in the "put_files_here" folder. I think there's a new update of the kn0x0ut script coming soon that allows flashing of straight zip files, but not sure when that will be released.
Click to expand...
Click to collapse
@prisonnet Have you utilized this script on any previous versions? Actually used the tar ball to restore anything? I haven't tried and I'm a bit skeptical.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

brobinson2102 said:
@prisonnet Have you utilized this script on any previous versions? Actually used the tar ball to restore anything? I haven't tried and I'm a bit skeptical.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I'm making one right now to see if it can work, though i had to build the commands into my own batch file as running the script through ADB or Terminal Emulator didn't work. Currently compressing the files and then hopefully when i test them it will work, but i am highly doubtful that it will because i believe they need to be signed and i remember Aou creating something like this for MF3 in his neutered update thread and I believe it didn't flash.

DeadlySin9 said:
I'm making one right now to see if it can work, though i had to build the commands into my own batch file as running the script through ADB or Terminal Emulator didn't work. Currently compressing the files and then hopefully when i test them it will work, but i am highly doubtful that it will because i believe they need to be signed and i remember Aou creating something like this for MF3 in his neutered update thread and I believe it didn't flash.
Click to expand...
Click to collapse
I'm working on the same thing now. If the tar file doesn't work, my next step is to try manually flashing the backed-up system.img.ext4 with busybox dd. Someone correct me if I'm wrong, but ROMs contain boot.img and system files, since we can't flash boot.img without bricking that leaves system.img? I know safestrap doesn't flash boot.img; I assumed it just flashed the system - so I'm just trying to do that manually.

[h910] rooted Oreo stock-based - get fingerprints AND radio working (if one isnt)

Hello everyone, I'm a total noob but I solved a problem which I couldn't find the answer to, so I thought I'd share. Please take care following my noob advice, I'm not responsible for anything which goes wrong with your phone (and if it gets complex, I probably don't have the skills to help)!!
What was my problem?
When I went from Nougat to Oreo, my radio broke (no cell reception). However I had the files from LGUP, so I could flash "fsg" "modem" "modemst1" and "modemst2" in fastboot (as explained here) which did indeed fix my modem problem, giving me back radio and data. However, this also made the fingerprint scanner disappear from my phone's settings menu. As far as I could tell, this wasn't a problem related to encryption (as discussed in AO ROM thread a lot, which is what I'm now running), rather 'twas a problem with the firmware! So I was loving Alpha Omega, but left without fingerprint scanner since radio isn't really optional on a phone.
Solution?
Please remember, I'm a noob and have only done this for my own phone, a h910, I don't know if i will work for you or on other models!!
Basically, I mish-mashed the two modem files from Oreo and Nougat, to get both things working!
Steps I took:
1) Use Linux - I couldn't get the files to open properly in windows, and didn't find a way to write to the image files.
2) Find a stock "modem.img" file from Oreo (i searched on google "stock oreo h910 modem and it came straight up) - I think I am too new on this forum to post outside links so you'll have to search for it.
3) Find a stock modem file from nougat (I used my original LGUP dump file from nougat, renamed to .img) I'm not sure if it is important that this came from your phone or not, if you followed all the instructions on the dirtysanta root guide, you'll have this as part of your LGUP backup.
NOTE: both of these files were 86 Mb (helped me feel confident I'd found the right thing on google)
4) Create backup copies of both, and append ".img" to your LGUP "modem" file. Call the backup of your OREO modem (the one you got off of google) "MyModem.img", just to keep it clear for later.
5) Mount the NOUGAT img first in a terminal (might have to make a mount point first), for me this was like this:
Code:
sudo mkdir /mnt/modemfiles
mount -o loop /path/to/your/nougat-modem-file.img /mnt/modemfiles
You obviously have to put the file path to where you saved your NOUGAT modem image - the one from LGUP!
6) You should now be able to see the nougat modem .img mounted as a disk in "places" on your file explorer. Go there, and copy the contents into a new folder somewhere easy to find (make a folder on your desktop called NougatModem.) There are two folders iniside, one called "image" and one called "verinfo".
7) Now you can un-mount, as we have what we need from it, easiest to do by just right-clicking it in file explorer and select unmount.
8) Next we will mount the image which will become your new (hopefully working!) modem, but it has to be writeable, so using the same mount point we would do
Code:
sudo mount -o loop,rw /path/to/MyModem.img /mnt/modemfiles
Remember that "MyModem.img" should be your backup OREO image - where all the firmware works but you don't get radio.
9) Now basically comes replacing a few files in the OREO modem (which we have mounted) with ones from your original NOUGAT backup (which are in that folder on your desktop). I couldn't remember if cp command replaced things with the same name, so I used rm to remove files, and then cp to replace them once they were gone.
a) first it is the folder called modem_pr, inside image
Code:
sudo rm -R /mnt/modemfiles/image/modem_pr/
b)next were all the files in the image directory which were modem.SOMETHING
Code:
sudo rm /mnt/modemfiles/image/modem.*
10) Finally we have to replace those files and the folder with the same things from our NOUGAT folder which is on our desktop, using the copy command. I will put the commands as if you did name that folder NougatModem
a) so first the folder which we removed
Code:
sudo cp -r ~/Desktop/NougatModem/image/modem_pr/ /mnt/modemfiles/image/
b) now all the files again, using the wildcard for the different extensions
Code:
sudo cp ~/Desktop/NougatModem/image/modem.* /mnt/modemfiles/image/
So if all went to plan, you now have an image (which you can unmount), called MyModem.img, which you can flash in fastboot to the modem parition (fastboot flash modem /path/to/MyModem.img) and if it works for you like it did for me, you have cell reception, data (after putting in APN if it's needed) and fingerprint scanner all working on OREO. Again, I'm on Alpha Omega, loving the rom and now going to go play a bit.
I've not been on the forum long, but have just gained a HUGE insight into how much time people put into making guides and helping others learn (this has taken me ages haha). Thanks to everyone for your hard work and community spirit, please let me know if this works for you or if it provides any interesting insight as I really did it blind (I had no idea if it would work, and was just making some slightly educated guesses - I got lucky!). Also, if the instructions are hard to follow and you have a hint, I'm happy to edit them to make them clearer.
ENJOY!!
PS - I know the linux commands could be better haha, using more than one mount point too might have been easier, but I figured that I'd just keep it exactly the same as how I did it since I'm a noob and would be more likely to screw something up in the instructions, if I changed it without trying at the same time!
EDIT: I could also upload my "patched" modem image, but not sure if it will work for other people's phones, or if it has "personal" or unique info in it (basically if it would be safe to do so) - If someone who knows tells me it'd be good to go, I'm happy to share it if it would save people from having to go through the whole process. I guess I hope posting all this will be a learning thing for others too Gotta have some justification haha!!

You are to be commended on your well presented write up. But I'm sure there is an easier way to get data and fingerprint working without going through all of that.
I don't have an original H910 device but I did flash H910 oreo kdz on my device and data did not work at all. Didn't test fingerprint. All I did was flash modem using lgup patched from another variant and that solved it.

ezzony said:
You are to be commended on your well presented write up. But I'm sure there is an easier way to get data and fingerprint working without going through all of that.
I don't have an original H910 device but I did flash H910 oreo kdz on my device and data did not work at all. Didn't test fingerprint. All I did was flash modem using lgup patched from another variant and that solved it.
Click to expand...
Click to collapse
Thank you for the commendation haha! What a mission!
So I'm guessing you flashed a different version's KDZ?? As far as I'm aware from lots of reading here on xda, there are no KDZ files for the h910. For me the kdz from h915 worked perfectly for example, apart from data. And that was the story with a few things I flashed, KDZ or ZIPs, they would break data, I'd flash the modem, and that would break the fingerprint scanner. Hence this long-winded solution lol.
If you have an original h910 kdz that people don't know about that'd be interesting in itself!!

No, I flashed a H910 ZIP that someone kindly uploaded here somewhere. Then I flashed back the modem from a Verizon kdz.

You are the best, I have been trying to solve this for a long time, I tried flashing many things it thanks to you I now have a working fingerprint and data. Although I am a complete noob for using linux I just used it for the first time using live boot. This is a challenge for noobs but worth it at the end and big thanks.

Why not just cross flash to us996 and walk away? 0_o You get a newer modem this way. I think you have to enable bands on some devices but on h910 I don't think even this matters. You are just downgrading the modem and keeping the new bootstrap. Still from what I read this is encryption issue. There was a supposedly a rsa key change during the update... without them matching the bootstrap will not will not load fingerprint software as it's not trusted unless it matches.

Vortell said:
Why not just cross flash to us996 and walk away? 0_o You get a newer modem this way. I think you have to enable bands on some devices but on h910 I don't think even this matters. You are just downgrading the modem and keeping the new bootstrap. Still from what I read this is encryption issue. There was a supposedly a rsa key change during the update... without them matching the bootstrap will not will not load fingerprint software as it's not trusted unless it matches.
Click to expand...
Click to collapse
So should I flash the whole ROM or just the modem of us996 to have both working?

DesrtSailor said:
You are the best, I have been trying to solve this for a long time, I tried flashing many things it thanks to you I now have a working fingerprint and data. Although I am a complete noob for using linux I just used it for the first time using live boot. This is a challenge for noobs but worth it at the end and big thanks.
Click to expand...
Click to collapse
Just wanted to say that made my day when I read that the original post had helped you out Cheers for letting me know

Awesome!! Thanks for this. Where did you get the idea of what files to change? Just curious.
I am still tinkering. I have an LGUP dump from:
ATT Stock
A-O Nougat install
A-O Oreo install
I was mix and matching the modem files with various modemst1 and modemst2 files. I did this because it seemed that I got better signal strength with the A-O Nougat install... but I got the kernel panic/modem crash whenever I lost signal on the phone. But with this hand made modem file - no crash. But now I am going to continue mix/match and see what crashes and what gives the best signal strength.
Anyway thanks a bunch!!

Please give me the patched modem file, please send it to [email protected]

I would root then try activity launcher or some sort if hidden menu launcher to get band menu. Alternatively get Network signal guru and lock bands. That how i did it in los 17.1 not sure if it would work on stock. I went from hspa to lte doing it in h915(it's a Canadian h910). I even crossflashed to us996 and left it that way. Says it even says band 66 was unlocked in the app but it has not been tested yet. Either way I got band 4 and 12 once I did this.