When flashing a new ROM, is it necessary to rename the custom ROM file to RUU_Signed.nbh?
Many Thanks,
BK1650
as I know it is not necessary
Related
i am following all steps thru SAFE WM5 upgrade guide. I make it thru the Flashing HardSPL and Upgrading to Radio version 1.41.00.10 with no problems. But on Rebuilding the ROM file I cannot get passed this step....
____________________________________________
When you have downloaded the ROM file you must extract the contents of it using winrar into a folder, to make the process simple i suggest extracting to "original". Now delete ALL the files EXCEPT THE .NBH FILE. We are only interested in this file as it contains the nbh data which is flashed to the device.
The next step is to extract the contents of the file and split it into the seperate components.
Download duttys nbh tool and run it,
_____________________________________________
When I run that tool and try to Decompile NBH File the only thing it show me is radio.nb
It does not show me files like Windows.nb or Herm_ExtendedRom.nb and so on. Just radio.nb
So i am stuck I would really like your help on this.
Here is the link to the step i get stuck on.
http://www.mrvanx.org/cms/index.php...ask=view&id=27&Itemid=26&limit=1&limitstart=4
I can download all the files and programs but as you read above i am having problems. Thanks for any help
Next time wait for me to read this thread rather than PM-ing me the same EXACT thing!
Like I said in the PM it sounds like you are decompiling a radio upgrade rather than a ROM upgrade. Verify you are extracting the nbh from the correct file.
Is there a unified manner in which this is done?
I've been looking for a way to precook this kernel here: http://forum.xda-developers.com/showthread.php?t=756774 into my ROM's zip before flashing, to save myself the extra step.
Is there anything special to it? I assumed it might just be as straightforward as copying the entire folder structure into the ROM's zip, but the kernel inquestion actually has a third folder called "kernel".
Any help would be much appreciated, this combined with my LauncherPro cooking question earlier will make this ROM perfect for me
LiquidSolstice said:
Is there a unified manner in which this is done?
I've been looking for a way to precook this kernel here: http://forum.xda-developers.com/showthread.php?t=756774 into my ROM's zip before flashing, to save myself the extra step.
Is there anything special to it? I assumed it might just be as straightforward as copying the entire folder structure into the ROM's zip, but the kernel inquestion actually has a third folder called "kernel".
Any help would be much appreciated, this combined with my LauncherPro cooking question earlier will make this ROM perfect for me
Click to expand...
Click to collapse
unpack the existing rom zip's boot image, copy in the kernel you wants zImage, repack it and plop the boot image back into the sip. then remove all the modules in /system/lib/modules in the rom zip and copy all the modules from the kernel zip into the modules folder in your rom zip.
then you ware ready to go.
Yes man, but where to put the zImage? i have 2 GZ files and 1 folder. i tried to put it in the folder and repack that, and the rom stuck at the splash screen. where to put it and how?
thanks
Hey Guys,
I'm in need of some really n00b friendly advice.
When you flash a new ROM (i.e. CM9) in CWM the tutorials tell you to flash the file named Update.zip. My problem is that I can't seem to find one in the zip file I downloaded for my xperia mini.
I downloaded FXP131, and found the zip file to contain a boot.img, which will be the kernel. And 2 other folders named META-INF and System.
I know how to flash the kernel and expect it was just left in there for easy transportation.
But where in the world is 'update.zip'?
Am I meant to unpackage the kernel then re-zip the META-INF and System folder and then call that 'Update.zip'?
I've flashed roms for some of my other devices before, but they've always used flashtool or samsungs flashtool.
Please help me guys, I don't like sounding this inexperienced
update.zip
I'm wondering if the ROM I am trying to flash needs to be renamed as update.zip in order to work. It is krook's v.6 of JB for the Lenovo K1 tablet. Since the download site has to distinguish between wifi and 3G versions, as well as nvflash versions there are a number of different filenames, however does it need to be renamed after putting it on my SD card?
Generally speaking "update.zip" is used as a generic name. For example the update.zip I just flashed is actually named "rascarlo_maguro_ota_2012-11-01.zip". When you flash a custom ROM in a custom recovery you should be able to browse & flash whichever file you need.
The FXP131.zip file that contains the boot.img and 2 other folders named META-INF and System is the "update.zip"
solved
My problem was an incomplete download. I compared file sizes, and checked md5sums and determined the correct ROM and it is now in the middle of finishing the upgrade/optimization process.
Thx
Trying to create a flashable ZIP for a ThunderBolt. I have 2 questions:
My first question being, how do I determine the command on my device to install the APK I've included in the zip file?
Second question is, the update-binary is in all the ZIP archives and I would like to know what it does exactly. Is it required?
Thank you in advance!
Hey everyone
I'd like to know what I need to do to replace a custom kernel that comes with a custom rom zip to a stock kernel?
Is it as simple as just replacing the boot.img file & /META-INF folder from a stock kernel zip with the boot.img file & /META-INF folder in the custom rom zip?
Reason why I want to do this, is to be able to flash a custom rom with a stock kernel through flashfire so I don't trip knox, since a custom kernel would trip knox.
At the moment I've got a custom rom with stock kernel on my phone with knox 0x0 but I'd like to try out some of the other great roms that are available and unfortunately they all come with custom kernels :/
I've been googling for the past hour but I'm only finding outdated information and I don't really want to rely on that lol.
Thanks in advance
no no..you only have to extract the Rom using winrar and copy the boot img over..now go to system /Lib/modules and delete the those files.. copy (if there any) the new in..and zip it again using winrar
BTW..you don't have Knox tripped..? if you are about to flash this with a custom recovery..you will trip Knox for sure
Alex-V said:
no no..you only have to extract the Rom using winrar and copy the boot img over..now go to system /Lib/modules and delete the those files.. copy (if there any) the new in..and zip it again using winrar
BTW..you don't have Knox tripped..? if you are about to flash this with a custom recovery..you will trip Knox for sure
Click to expand...
Click to collapse
Alright thanks for explaining! Ill be flashing with flashfire