I've never tried flashing a radio through fastboot flash radio radio.img only by putting pd98img.zip into my SD and going into bootloader.
I'm currently on 26.13, can I take radio.img out of Radio_12.65.60.29_26.14.04.28_M_2.rar and zip it up myself into a file
called pd98img.zip and flash it in my bootloader instead?
thank you.....
Yes, but don't forget to include the txt file in the pd98img.
marsdta said:
Yes, but don't forget to include the txt file in the pd98img.
Click to expand...
Click to collapse
Thanks, do I have to or else it doesn't work? or Can I just do it without the txt, because when I look into pd98img.zip files the only file is the radio.img without any txts.
unless both the radio.img from rar and the pd98img.zip?
Every pd98img I have ever downloaded has that android-info.txt file. Not sure exactly how it works, but its needed for your phone to flash the radio image inside the zip
Here is a pic of the files inside of a pd98 I just Downloaded.
{
"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"
}
What you can do is take a different pd98 your have and replace the radio image with the one you want
Yeah you will need the android-info.txt
I had posted the android-info.txt for another member who said it worked for him. Here's the link to the thread. (Post 8)
Related
Hi
I would be very happy if someone could tell me how to re-sign the ROM after I add and delete stuff to /system/app? what do I need?
thanks
edit: I read this but the link is dead, can't download.
http://forum.xda-developers.com/showthread.php?t=473580
Don't bother. If your recovery is set to check signatures, your rom will fail unless it is signed by the device manufacturer.
It would sort of defeat the whole purpose of signatures if you could just change something and re-sign it with the original signature.
Dont ask me to ever explain the math behind the crypto, but I can link a wikipedia page
{
"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://en.wikipedia.org/wiki/Digital_signature#Integrity
There are a few ways to resign your changes to a custom ROM but you may not need to resign if your custom recovery doesn't check or if you use something like 7zip to open the zip but not actually extract it while making your changes. If you do need/want to resign, there are a few possibilities. A couple android apps can sign files on your phone itself: Signapktic or ZipSigner. There are also tools for your computer floating around xda to sign zip and apk files. I have a droplet called Android-sign(mac-only) to use every now and then. Also, there's always the testsign.jar method from the command line.
Code:
java -classpath /PATH/TO/testsign.jar testsign update.zip update-signed.zip
So i tried to make a progress but nothing i stuck -.-
i followed this guide http://forum.xda-developers.com/showthread.php?t=2195858
but the program wants the system file of stock rom...
however stock rom doesnt have any .img etc folder..only
this if i extract ''G900HXXU1ANCI_G900HUUB1ANCI_G900HXXU1ANCI_HOME.tar.md5''
so my question is there a way to take folder system to progress my trying of make custom rom?
Airboner said:
So i tried to make a progress but nothing i stuck -.-
i followed this guide http://forum.xda-developers.com/showthread.php?t=2195858
but the program wants the system file of stock rom...
however stock rom doesnt have any .img etc folder..only
this if i extract ''G900HXXU1ANCI_G900HUUB1ANCI_G900HXXU1ANCI_HOME.tar.md5''
so my question is there a way to take folder system to progress my trying of make custom rom?
Click to expand...
Click to collapse
Open the md5 using 7zip and extract the files to a folder.
drakester09 said:
Open the md5 using 7zip and extract the files to a folder.
Click to expand...
Click to collapse
tnx its says that incorrenct etc but extracted..
we will see after..
so i took system.img and i place it on ...../original_update
and when i extract the stock rom its show this message..
i extracted wrong system? :/
should i place system somewhere else?
tnx btw guyz
{
"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"
}
Just as the headline says, are the TWRP .img files flashable with the Android application called Flashify?
Or should it be done via Odin?
Enddo said:
Just as the headline says, are the TWRP .img files flashable with the Android application called Flashify?
Or should it be done via Odin?
Click to expand...
Click to collapse
I only use flashify it's the better way never a problem, open the archive file , extract recovery.img and flash it with flashify
Enddo said:
Just as the headline says, are the TWRP .img files flashable with the Android application called Flashify?
Or should it be done via Odin?
Click to expand...
Click to collapse
I don't see why not, their description lists flashing recovery.img files as an option
{
"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"
}
I have flashed the .img file of the TWRP Recovery several times via the Flashify app. And TWRP have worked perfect everytime after that. So i haven't come across any issues or problems by going that way so far.
http://forum.xda-developers.com/note-4/development/twrp-2-8-1-2-recovery-note-4-sm-n910c-t2977933
Thanks a ton, guys
hey,
I'm trying to flash a KK Stock ROM on my SG4 -L720T , unsuccesfully, I get an error when flashing it thru the recovery
this is the file-
{
"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"
}
Lidor167 said:
hey,
I'm trying to flash a KK Stock ROM on my SG4 -L720T , unsuccesfully, I get an error when flashing it thru the recovery
this is the file-
Click to expand...
Click to collapse
That looks like an Odin file in a zip. Are you sure it's a ROM? Look inside the zip and if you don't see a folder titled Meta-INF, then it's not a ROM.
bilgerryan said:
That looks like an Odin file in a zip. Are you sure it's a ROM? Look inside the zip and if you don't see a folder titled Meta-INF, then it's not a ROM.
Click to expand...
Click to collapse
It's a ROM, there's a Meta-INF in it.
That is an Odin File. I have the exact same file saved on my laptop. It definitely will not flash through recovery.
Sent from my Nexus 6 using XDA-Developers mobile app
Lidor167 said:
It's a ROM, there's a Meta-INF in it.
Click to expand...
Click to collapse
Try these - http://forum.xda-developers.com/showthread.php?t=3049810
What was the error message that the recovery have you when you tried to flash it?
If someone is having problems with NVRAM error in wifi section after installing custom rom and then reverting to original one then this thread is for you.
Disclaimer: I am not responsible for any damage done to your device.
With this out of the we can start. First of all you will need Sp flash tool an a copy of original firmware and working brain. First you will ned to extract your firmware zip that you can download HERE. After extracting firmware files you will need to edit Android_scatter.txt file under NVRAM section.
{
"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"
}
In file_name you have to change NONE to nvram.bin and is_download to true. After that it should be looking something like that.
Now save and exit notepad text editor. After that you need to copy nvram.bin file that you can download here: NVRAM.bin and move it to extracted firmware folder. If you have any problems with error checksum mismatch you have to delate Checksum.ini in your firmware folder. If everything was done correctly you should be able to see nvram option in download tab.
Deselect everything expect for nvram and then click download button. After completion reboot to system. Now this error should be no more. This method should work for all mtk devices but you will need to extract nvram.bin file from normally working device you can follow this Youtube Tutorial.