Ok, so I've now been through SBFing my phone for the second time, and I'm starting to learn a little, but I'd like to get some clarification on how the different functions and components involved relate to each other. I'm trying to put together a mental picture of a smartphone's software components to understand all of this better.
Basically I'm trying to identify the differences and connections between the bootloader (specifically locked bootloaders, as found on my Droid X, et al.), the recovery partition, the kernel, SBF files, nandroid backups, and the customizable portions of a ROM. I've drawn a diagram that illustrates to the best of my ability the connections I've been able to put together, which I will explain here.
As I understand it the bootloader tells the phone what to load when it boots up. Apparently, locked bootloaders have some restrictions as to what can be loaded, which prevent custom kernels from being loaded. I'm not sure how this works exactly, but effectively it seems as though the bootloader ensures that the kernel being used is appropriate for the phone.
However I'm pretty certain that the OS image you put on a phone contains the kernel, but the entire OS is not locked down, so that makes it seem like the bootloader only ensures that the kernel portion of the image you use is kosher, and doesn't care about the customizable parts (e.g. all of the changes in a Cyanogenmod ROM versus a stock ROM).
As I understand it, a phone comes with a stock recovery... thing. I don't know if this is a separate partition that can be loaded or if it's somehow part of the OS itself. But clearly, on rooted phones this can be customized as well (i.e. clockwork recovery et al.). The diagram below puts the recovery thing inside the OS "bubble" but perhaps it should be outside.
Nandroid backups are clearly some form of image, but do they contain the entire OS, or just the custom ROM part, as in the diagram below? Does the success of a restored backup depend on the kernel that's loaded?
As for SBFs, how does an SBF file compare to a ROM ZIP file? And how do these compare to nandroid backups? Are they all just images? What makes them different? If the kernel can't be changed, then is a cyanogenmod release (for example) a full OS including a copy of the kernel it was built on (e.g. Froyo, GB), or is it only one part of the whole?
I hope I've explained what I'm looking for well enough. I know enough to be dangerous, as the saying goes, but I'm sure anyone who knows what they are talking about will read this (and the diagram) and go "wow is this guy confused". So help a brother out. Can anyone correct me where I'm wrong and help me build a more accurate mental image of how this all works? I'm a very visual learner, so a corrected diagram would be a big plus as well. Thanks for any insights.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Related
My Prophet has stopped reading SIM cards, and will need a warranty repair.
I can't take it in as it is, what with Jesters spash screen and all. I just assumed I could re-run a previous rom to have it install, but apparently you can't "downgrade".
I've tried looking for downgrade guides, but I haven't managed to find one. Ultimately, as long as I can get the splash screens to have it boot up to "Invalid or Missing Sim" I should be home free, but how do I get them out of the previous rom? Or, how do I edit the rom so it'll install on my device?
I've tried using TyphoonNBFtool to edit the image version, when I go to resave the rom, it only saves 2kb, so I'm obviously missing something here. I'm currently looking into ways to strip files from the rom itself.
Any ideas or suggestions here?
I have had (and still have) problems with my S200. I have installed the LVSW AKU2.3 ROM and I did not have any problems with the warranty.
They just check the image, OS, SW release and radio version and they all passed the warranty check.
So there is no need downgrading.
HappyFace said:
I have had (and still have) problems with my S200. I have installed the LVSW AKU2.3 ROM and I did not have any problems with the warranty.
They just check the image, OS, SW release and radio version and they all passed the warranty check.
So there is no need downgrading.
Click to expand...
Click to collapse
Well, half the reason I wanted to was to learn how to do it.
Which was successful!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://forum.xda-developers.com/showthread.php?t=271043
This thread had all the tools I was after, and a PDF with tutorial. Obviously I just substituted what I required, and whammo. I initially attempted to use the prophet RomUpdateUtility-No Vendor ID, but that didn't work. So I tried the Wizard one that was included in the tools, and it worked no hassles.
So yeah, I'll take it back tomorrow.
Summary: You can't downgrade roms because if the IPL or SPL version (primary and secondary boot sections, or something) is lower than the one you have installed on your phone, it won't let you install anything. "This NBF file cannot be used for your PDA phone. Please get newer NBF file." So you have to use the tools in the above thread to split the nbf up into it's appropriate sections (OS, Extended Rom, IPL, SPL, Phone splash, HTC splash and GSM), then re-combine them without the IPL and SPL using a Cooking Guide and then use a working Rom Update Utility (as I mentioned above, I had to use the Wizard one that came with the tools because the Prophet one kept saying it couldn't open the "required file") to install it onto your phone.
You can use this thread if you're only interested in changing your boot splashes.
Welcome!
Soo, it's time for some more custom blingbling..! - Pictures of each will be below.
I will continue on from my easy and sexy Umbrella Corp splash! (Link in sig) - If you want some links and info on how to do these, please read in the comments of that thread, I also gave thanks to the people who needed it, in there.
I'll do a quick install guide plus some info on when these splashscreens will not work for you. There's happened a lot since the GB days, sadly.. So this will take some time for you to do. Involving some ROM flashing and so on. :/ Sorry. - If you're on a stock ICS rom, you may get away without flashing any roms around, since it's.. Stock Samsung..
Install and explanation + short troubleshoot, yeah..
Okay.. You're on some awesome rom like AOKP or Asylum or CM10, when you realize you could do with a new, fun splashscreen. This is where you need to stop and think about it.. Is it worth downloading and flashing an old firmware just for this? If it is, keep on reading. The idea of this CWM flash is to rewrite the param.lfs file inside /system/mnt/.lfs, in order to do so, we sadly need an older stock GB firmware. You will get back to your daily driver afterwards, but this step is needed. So.. Yeah.. Make sure you don't get the triangle on the flash. There are numerous ways to avoid this.. Mobile Odin being a really sexy one. If the param.lfs file isn't rewritten, it won't take your custom splash .jpg into consideration and you will be stuck with a "draw_fail_logo01 as your splashscreen. This won't in any way damage the device, it just really sucks and will require you to reflash an old GB rom anyways in order to even get the old GT-N7000 splash back. So yeah.. If you wanna do this, do it right from the beginning to save yourself some time.
But hell, we're all flashing pro's, amirite?
So.. Proper root and yellow triangle is all that will stop you from flashing these.
Basically what this file does: Replaces one jpg with another jpg + a path to said jpg. Once you reboot the device, it will no longer show GT-N7000 before it goes to the bootanimation, it will show something cool.
Installation steppy-steps
1. Download an old GB rom, since these are the ones you can rewrite the param.lfs file on.. The ICS and Jelly ones, doesn't allow for this. :/ - Make a nandroid backup before, ofc. if you wanna keep your stuff.
2. If it isn't rooted, root it. I recommend CF-root since you also get CWM that way. Most important thing is that you don't get the triangle.
3. Download one of my .rar's and unrar it.
4. Copy the contained .zip onto your device.
5. Flash it in CWM.
6. Reboot into your super awesome NEW GB rom and check out all the features and uhh, don't forget to check if the splashscreen worked.
7. Wipe data, system and cache and do a CWM restore to your ICS/Jelly rom.
Splash Screens
Android Splashy Splashy
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download: https://www.box.com/s/p5956o677fd21aienxaa
GT-N7000 Gold
Download: https://www.box.com/s/ve097ivsioeefa5uiul0
Hello World
Download: https://www.box.com/s/pcn0qrj4cxb376e70jik
League of Legends - Show your support to the Fields of Justice with this tacky splash screen.
Download: https://www.box.com/s/93plngte4cdwuv38mwak
Remember that at any point, you can unrar my archives and replace my image with something else, just keep the .jpg name. I've heard rumors that it will max fit 3 4ths of the screen. So full screen isn't possible. I keep them in this ratio simply because they are made from the original screen, back in the day when I made the first one. It is centered and it makes for a fine fit.
Thanks for reading, enjoy them.
My buddy tested this out on his Butterfly and it turned out to work good. Full ROOT with S-OFF.
I am not the creator of this one click, but I was told it could be shared freely, as it also describes in the .ZIP contents.
I did not personally try this out myself (My One X is already rooted + S-OFF) so be sure to check it out and read all the documents before trying out this new root exploit.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It did finally pick up my One X after about 10 mins (more like 2), but like I said I'm already rooted. It looks like it supplies a good amount of phones, and with the 3 different methods for rooting, especially the third, hopefully we will see some good results!
I'm not responsible for harm that comes from this file, I have ran and tested it out to SOME EXTENT. Please be aware of this, and like I said, READ THE DOCUMENTATION.
It states it can:
Root Android 2.x
Root Android 3.x
Root Android 4.x
Rooting Phones and Tablets
Supplies S-OFF as well (80% Chance)
So, like I said, try it out and let me know if it works!
Nice one !
Sent from my HTC Butterfly using xda premium
somebody please explain to us noob, what is the advantage of s-off? mine is rooted but s-on. is this worth the risk? Thank you!
royskeyz said:
somebody please explain to us noob, what is the advantage of s-off? mine is rooted but s-on. is this worth the risk? Thank you!
Click to expand...
Click to collapse
What Is S-OFF?
In their devices, HTC have installed a sort of security check whose level is determined by S-OFF/S-ON. Essentially, this security level is a flag stored on the device’s radio that checks signature images for any firmware before it is allowed to be written to system memory. This hinders using any custom ROMs, splash images, recovery etc., and also restricts access to the NAND flash memory. However, when security level is set to S-OFF, the signature check is bypassed, allowing a user to upload custom firmware images, unsigned boot, recovery, splash and HBOOT images, as well as official firmware that has been modified, this enabling maximum customization of your HTC Android device.
Furthermore, S-OFF also reduces restrictions on accessing the NAND flash memory on the device, allowing all partitions (including /system) to be mounted in write mode while the operating system is booted.
Is this for the X920D/X920E/Both? Really happy to know it works
Doesn't work.. I tried on the x920d (UB1).. while on, while in bootloader, while in fastboot.. doesn't work.. just sits there with message "looking for HTC Butterfly" for almost 20 mins, before I closed it.
Since I have tested it myself, I am going to close this thread, just incase someone tries something else and has a brick.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
For a little while there I had an Orbic of my own, but that caused mass-hysteria on Verizon's part because you aren't supposed to try and put a post paid SIM in a pre paid phone or it won't work. However it doesn't just "not work", it totally messes up your account big time to the point where no one knows how to fix it. It turns your postpaid SIM into a prepaid one and locks you out, among some other things too that generally turn your smile into a frown. Long story short I was without service for 5 days straight and ended up having to return my Orbic and get an X4 from Best Buy (so I guess there's a happy ending to it). Lesson learned, won't be trying that again. Hopefully this message can prevent someone else from making the same mistake as well
Anyway, during that very short time I had the Orbic I managed to make a dirty port of something called RedWolf Recovery. I had this sitting around on my computer and almost forgot about it entirely. Think TWRP but it has different branding and much more features, like more partitions it can back up and a theme engine that's supposedly much better and more flexible than TWRP's
WHAT WORKS:
Everything except what's listed below
WHAT DOESN'T WORK:
Basically the same stuff as my dirty port of normal TWRP, the vendor partition won't mount and data won't mount until you flash the disable-encryption zip and factory reset
If you find anything else let us know. I might not be able to fix it entirely since I don't have proper source code to work from (all these images are pre-compiled dirty ports) but at least everyone else can be aware to stay away from certain things if they break something
DOWNLOAD:
LINK TO THE IMAGE ITSELF
To install it just flash it in fastboot like you would the normal TWRP image
I can't exactly provide any "source code" either since all of my stuff are dirty ports so far. However all of the images I use I will link to right here so you can still have access to everything I did to work with in your own endeavors
THANKS TO:
Team RedWolf for that bangin' recovery I could pull from
XDA user @Devil7DK for making the Redmi 3S port of RedWolf, that has the same chipset as the Orbic so that's what I used to dirty port. Check out his original thread HERE
Team Orbic for the usual help they provide
Carliv Image Kitchen for letting me do all those dirty ports and mods of images that I did
how do i flash the dm verity? I can't seem to save it on the phone on a partition thats mounted, and thus can find it in twrp.
Can i flash it with adb/fastboot?
bubbyj said:
how do i flash the dm verity? I can't seem to save it on the phone on a partition thats mounted, and thus can find it in twrp.
Can i flash it with adb/fastboot?
Click to expand...
Click to collapse
You can't flash "dm verity"
Hi Everyone Thans for having me Im stuck
My s7 froze and wouldnt do anything I managed to turn it off ,then it wouldnt boot ,after clearing the cashe and rebooting system it almost started but kept going to the android falling over ,
I read the options to sort this and tried to flash twrp recovery I seemed to go ok but when the phone rebooted it went to the An error has occured while updating the device software screen ,
I have tried smart switch but it does not see /connect the phone ,I can with a bit of messing with the buttons get from the An error /use the emergency recovery function screen to the ODIN Mode screen and the phone connects to odin But when i try to re flash the boot loader it flashes to the end then fails .
Am I right thinking Its the boot loader I need to get on 1st to get any further ?
Can anyone point me in the right direction ?
If ive posted in the wrong place please can you move
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sounds to me, like part of the storage may have suddenly failed or been damaged, causing your device to lock up and after a reboot, triggering this unusual state. Part of the bootloader is likely not getting read or written to properly, so installing fails only after partially writing to the device, and it refuses to boot. You could try a repartition and complete installation - that might also make it worse though. I've seen the blue screen of mild annoyance many times - not sure about the falling android, was there any text? If so, what did it say? The firmware does contain screens for various diffrent panic states, resembling the one you mentioned. I would encourage you to do some more research on those and look for patterns in the way it fails - or doesn't - when flashing other parts of the firmware package. Don't even bother with SmartSwitch - in my experience, it fails at anything the errors tell you to use it for. Also, simple issues like a faulty cable or the wrong firmware can often be overlooked - so make sure those are fine before starting to experiment.