Database Users

[Q] Stock ROM without HBOOT etc. (FM Radio)

Sorry for the newb-ish question. I'm in a mad rush to build my FM app and would prefer not to have to research this issue for hours.
I have my FM app running on Blayo ROM, using btipsd_cli, and I think it should then work on the stock ROMs. AFAICT they also include btipsd_cli.
So I want to test on a stock ROM. Which one should I use ? I'm avoiding the RUU's because I don't want to have to mess with Windows etc.
So I'm looking at: OTA_Legend_Froyo_S_Vodafone_UK_3.14.161.1-2.05.161.1_R_P_release_135177_156984k4i146wit81sj23a.zip
But the embeded firmware.zip includes an HBoot and radio and recovery.
I don't want to lose my S-Off, or my CM recovery.
Can I do this ? What's the easiest/safest way ? Or any other stock ROM I should use ? Perhaps I should test with the oldest ROM and the newest ROM.
Thanks much !

Sure m8. Just extract whichever img you want and flash it via fastboot. I'm not sure about system.img. Some guys reported that flashing system.img doesn't actually work. In that case put it on /sdcard, fire up CWM, format system partition, mount it and then inside adb shell unyaffs the image into /system dir.
EDIT: Ahh one more thing. You can't just install any OTA you want. What OTA does is binary patching of existing files. That said it means you have to have binaries that actually match to their patches but I guess you knew that before
Sent from my HTC Legend

BlaY0 said:
Sure m8. Just extract whichever img you want and flash it via fastboot. I'm not sure about system.img. Some guys reported that flashing system.img doesn't actually work. In that case put it on /sdcard, fire up CWM, format system partition, mount it and then inside adb shell unyaffs the image into /system dir.
EDIT: Ahh one more thing. You can't just install any OTA you want. What OTA does is binary patching of existing files. That said it means you have to have binaries that actually match to their patches but I guess you knew that before
Click to expand...
Click to collapse
Thanks BlaY0 !
No I didn't know about the patching of files. So that's what the *.p files are for... Yuck, that's messy IMO.
I WOULD have known if I spent much time in this area but I haven't. A few months back I finally had my phone in a nice state and haven't looked back. It was VERY painful doing all that, and at least twice I messed up badly and had to restart. So I don't want to repeat that.
I haven't figured out how all the partitions/image files interact, so I won't go down that road at this time. I'm guessing it may not be possible to go back to stock temporarily and then revert to the other ROMs easily.
So for now I think I'll continue to use your ROM as a proxy for a stock ROM and hopefully my app will work as well on stock ROMs. BTW, I'm now running your new 8.4 and it's working very nicely thank you...

Those .p files are standard bsdiff patches. At least they should be, but HTC once again made some internal changing to that so I was unable to manually apply those patches on my PC.
If you are S-OFF which I believe you are, all you have to care about are boot.img and system.img. 1st is image made of kernel + initrd and 2nd is basically yaffs2 image. 1st can be flashed with flash_image and 2nd can be unpacked with unyaffs (after you format system partition and mount it on /system via CWM). All needed tools are available in CWM recovery and they are also part of AOSP and are compiled separately each as its own bin. Flashing can also be done via fastboot, but I'm not sure about HTC's system.img as I'm not S-OFF. You should try that.
Sent from my HTC Legend

[REQ] Stock Kernel 2.3.4

can anybody deliver the stock 2.3.4 kernel as an image to reflash via recovery if one wants to go back from a custom kernel?
would be easier, than using an old backup or reflash the whole ROM due to lost data, apps, sms, etc.

Second to that....maybe someone can help us.
Best Regards

Third to that! Want to try custom kernel, but don't want reflash whole image, if I'll not like it.

evlevl said:
Third to that! Want to try custom kernel, but don't want reflash whole image, if I'll not like it.
Click to expand...
Click to collapse
do a nandroid backup. it saves kernels

Flashing back stock kernel will not allways help , because some other alterations (e.g. in intit.d) will still remain .. But if you want the stock 2.3.4 kernel .. you can download the full rom posted by me or given in an other thread .. set a side the boot.img and flash it with fastboot ( fastboot flash boot boot.img)
If you do not want to download load an entire rom I attached the stcok 2.3.4 kernel .

Bandis710 said:
Flashing back stock kernel will not allways help , because some other alterations (e.g. in intit.d) will still remain .. But if you want the stock 2.3.4 kernel .. you can download the full rom posted by me or given in an other thread .. set a side the boot.img and flash it with fastboot ( fastboot flash boot boot.img)
If you do not want to download load an entire rom I attached the stcok 2.3.4 kernel .
Click to expand...
Click to collapse
excellent, thanx mate! i don't want to flash a whole rom just to get back on stock kernel, because all the backing up and restoring if not necessary is boring...
and does that really set back all changes, a custom kernel does on my phone? aren't there also always some folders in the zip-files of customs?

Well, now I see a reason why there is no "default kernel".
It's because all these custom kernels consist not only from "boot.img", but also from a number of "init.d scripts", "*.so modules", etc, which are obviously different from kernel to kernel. So because of that you cannot have an universal "stock" kernel, but rather a whole stock ROM.
Thanks a lot for all of you who comment that request, now the situation with kernels is more clear.

While all the above is sensible, it should be possible with a modicum of planning to go back and forth between a custom kernel and the stock one. I feel the question is more: is it worth the trouble versus flashing again? Probably not.
1 - Nandroid backup.
2 - Examine the scripts and files included in the custom kernel's zip.
3 - Back up what is replaced, patched or deleted outright from stock.
4 - Note what is added by the custom kernel.
When you want to revert to stock, reflash boot.img from stock, and either adb push the stock backup files back, or create your own update zip with a proper script to finish the job.

Noobie Question about ICS

I can't post in the development forums so I figured I would ask here:
I understand how to use adb and fastboot, etc.. What I am missing is with the new ICS ROM it states that I must "fastboot flash system system.img"; however none of the ICS zip file I have seen come with a system.img file (just the boot.img).
Am I missing something? Any help would be greatly appreciated..

I used the version available on Rootzwiki... not sure if thats the answer you wanted. I'm running 4.0.3 ICS on my wifi XOOM OC to 1.54. No FC's, reboots or anything of the sort. You'll need to be sure that you have su-install.zip, and other img files needed. As I said, you'll find them all on the rootzwiki website under xoom hope this helps, if not good luck.

You are talking about two different things here. I don't know where to start here you're all mixed up. There are several ways to flash a ROM, you can fastboot flash the .img files such as what you are referencing to. Or you can flash an update .zip file from recovery. The way you flash the ROM depends on the source, if its a bunch of *.img files you use fastboot, if it's a *.zip file you use recovery. Just follow the directions given for installation that are provided with the ROM you are downloading.

sboehler said:
I can't post in the development forums so I figured I would ask here:
I understand how to use adb and fastboot, etc.. What I am missing is with the new ICS ROM it states that I must "fastboot flash system system.img"; however none of the ICS zip file I have seen come with a system.img file (just the boot.img).
Am I missing something? Any help would be greatly appreciated..
Click to expand...
Click to collapse
Hello, and welcome to XDA! =] Anyways on with your question. There are two ways to flash a ROM to your xoom. One being fastboot/adb, where you use the command line on your computer to send commands to your device and make it do stuff. This is where you use system.img, boot.img, recovery.img.
The second, is CWM (ClockWorkMod recovery) This, as far as im aware, is the most common way. This is where the .zip's come in. Because you take the .zip you put it on your external SD card. boot into recovery (after flashing CWM of course) and flash the rom. CWM is nice because you can also make a 100% snapshot of your internal memory state via making a nanodroid back up. That way if anything messes up you have a 100% backup you can restore at anytime if you need it.
In a nutshell, You use *.img files with fastboot and .zip files with CWM.
Anyways. If you're new to rooting. Please check out these two threads, They'll help you get started. =]
Xoom Heaven: Root+Non Root Users Are Welcome!
[Guide] Setting up and using adb/fastboot-unlock, flash custom recovery & root
The second guide I did use to flash my own zoom so I can assure you it does work.

Flash any kernel or modem on CWM

- I made some ZIPs with scripts for you to flash any kernel or modem on CWM.
- It's simple, just drag and drop your file to the correct ZIP.
#Put zImage on the "Flash Kernel [zImage]"
#Put boot.img on the "Flash Kernel [boot.img]"
#Put modem.bin on the "Flash Modem [modem.bin]"
1. Extract the ZIPs from the 7z file first.
2. Just open your ROM file [Cyanogenmod {Also other AOSP, AOKP, etc...}, Samsung Stock, Samsung-based], extract the file, and drag and drop to the ZIP, then you install on CWM Recovery, very simple,
Download

in the meta-in folder, there are some cert files and stuff, do i need to move them in as well?

Good work Marcello
Enviado do GalaxyS2 usando Tapatalk 2.1.3

LogeshMenon said:
in the meta-in folder, there are some cert files and stuff, do i need to move them in as well?
Click to expand...
Click to collapse
There are just binary and script, no need for certs. Just drag and drop or extract and compress the file you want to flash,

Re: boot.img -- have you never had problems with wifi using just the boot.img? Especially across firmwares such as AOSP <-> Samsung?
I always thought you also had to flash dhd.ko, among other modules. The advice here is what I have been following: http://forum.xda-developers.com/showthread.php?t=1059412

stone_ship said:
Re: boot.img -- have you never had problems with wifi using just the boot.img? Especially across firmwares such as AOSP <-> Samsung?
I always thought you also had to flash dhd.ko, among other modules. The advice here is what I have been following: http://forum.xda-developers.com/showthread.php?t=1059412
Click to expand...
Click to collapse
No. Never had any problems. And maybe those libs are already inclued in the ROM, don't know. And all I know is that boot.img = zImage. I've seen a thread saying that you can rename boot.img to zImage.

Unfortunately this didn't work for me - the first time.
I ended up stuck on the boot screen - ie samsung galaxy siii logo appears, no boot animation to imply it's starting up
I tried restore from a CWM backup but there was a checksum mismatch (scrath that idea)
I thought i'd give it one last try.
I flashed your flash modem.zip first, then reflashed my ROM (Ripper ROM v7) with no data wipe, and it WORKED!
I'm pretty happy now because for a while there I thought I had bricked my device!
Now i just have to install a few more zips as addons to my ROM and i'm back in business. (just installed those, restarting now)
*edit* restarted, mods working ok, 4G/LTE connected, everything is good again
Just realized this thread was for the SGS2 whereas I have a i9305 SGS3 4G/LTE. Whoops. Well it worked, but in my case i had to reflash the ROM.
I think I have done it right, but my baseband version in About Phone still shows I9305ZHALI2 (it should read I9305TDVLI5)? The ROM i reflashed does not come with a radio, it uses the one already on your device.

jjcoolaus said:
Unfortunately this didn't work for me - the first time.
I ended up stuck on the boot screen - ie samsung galaxy siii logo appears, no boot animation to imply it's starting up
I tried restore from a CWM backup but there was a checksum mismatch (scrath that idea)
I thought i'd give it one last try.
I flashed your flash modem.zip first, then reflashed my ROM (Ripper ROM v7) with no data wipe, and it WORKED!
I'm pretty happy now because for a while there I thought I had bricked my device!
Now i just have to install a few more zips as addons to my ROM and i'm back in business. (just installed those, restarting now)
*edit* restarted, mods working ok, 4G/LTE connected, everything is good again
Just realized this thread was for the SGS2 whereas I have a i9305 SGS3 4G/LTE. Whoops. Well it worked, but in my case i had to reflash the ROM.
I think I have done it right, but my baseband version in About Phone still shows I9305ZHALI2 (it should read I9305TDVLI5)? The ROM i reflashed does not come with a radio, it uses the one already on your device.
Click to expand...
Click to collapse
This is very old. If you tried on your S3 lte, of course it won't work. Be more careful next time,
Sent from my GT-I9300 using xda premium

[Q] Backup Kernel How To question

Hi,
I have a small question. I own a Canadian Samsung 4 SGH-i337m, after reading the main guide for running other carrier rom on this address
http://forum.xda-developers.com/showthread.php?t=2295557
As the guide mention that I didn't need the loki kernel and I could use my carrier kernel.
I used to backup my kernel with SGS kernel flasher to do the job, but it's not working for s4.
I wanted to backup my stock kernel and apply it after the installation of a cursom rom and apply it through TWRP. As I understood it, kernel is the boot.img, and I read somewhere that the way to create this is to copy the boot.img + copy the /sytem/lib/modules files. If I look to the file prepared by iB4STiD in the file MDOB-I337M-VMK6-FIX-4.1 present here, it seems that it's the case.
There is still flashify as a solution but you can't use the file into recovery.
Does someone know how to do it, or point me out where to find a guide where I can do what I want.
thanks in advance,

youpiyo said:
Hi,
I have a small question. I own a Canadian Samsung 4 SGH-i337m, after reading the main guide for running other carrier rom on this address
http://forum.xda-developers.com/showthread.php?t=2295557
As the guide mention that I didn't need the loki kernel and I could use my carrier kernel.
I used to backup my kernel with SGS kernel flasher to do the job, but it's not working for s4.
I wanted to backup my stock kernel and apply it after the installation of a cursom rom and apply it through TWRP. As I understood it, kernel is the boot.img, and I read somewhere that the way to create this is to copy the boot.img + copy the /sytem/lib/modules files. If I look to the file prepared by iB4STiD in the file MDOB-I337M-VMK6-FIX-4.1 present here, it seems that it's the case.
There is still flashify as a solution but you can't use the file into recovery.
Does someone know how to do it, or point me out where to find a guide where I can do what I want.
thanks in advance,
Click to expand...
Click to collapse
What type of ROM are you using? You have to be using a compatible kernel. AOSP ROM's won't work with a stock kernel, and you can't cross Android version between system and kernel. Using any custom kernel developed for your phone with this guide will work okay however.

Thank you for your answer.
in order to answer your question I was trying to flash the hyperdrive to my phone with compatibility pack. But after reboot I go back directly to download mode. So I figured that it was the boot partition that wasn't adapted to my phone.
So yes, I understand that if you flash a rom based on code as cyanogenmod you will need a custom kernel. but for a rom that is based on stock as hyperdrive rom, unless I'm mistaken, I would imagine that the stock kernel should work.:cyclops:
Is there a way to back it up?

youpiyo said:
Thank you for your answer.
in order to answer your question I was trying to flash the hyperdrive to my phone with compatibility pack. But after reboot I go back directly to download mode. So I figured that it was the boot partition that wasn't adapted to my phone.
So yes, I understand that if you flash a rom based on code as cyanogenmod you will need a custom kernel. but for a rom that is based on stock as hyperdrive rom, unless I'm mistaken, I would imagine that the stock kernel should work.:cyclops:
Is there a way to back it up?
Click to expand...
Click to collapse
My best guess is find out which partition it is and use the dd command OR download the ODIN of your firmware version and extract the boot.img. However, it would be easier to just use a custom kernel designed for your phone as if you back it up like that you either have to make it into a flashable zip or use heimdall to restore it every time.
Sent from Black<3's I337 running Foxhound ROM

Thanks for your answer.
That's weird as a nandroid is doing the job,that is hard to find how to backup a kernel.
anyway, I guess my best chance is to download a custom kernel and apply it after installation of the cutom rom. At first boot re apply a backup kernel with an app as flashify.
thanks youpi