I've spent the past 4 hours flashing roms to my phone just to see what works and what doesn't. I could easily say that 30% of that time could be added to productivity if I could ODIN into a semi-stock rom that has a custom recovery file already in /./system/bin. How do I do this?
You would get your phone to the state that you want, and then pull system images using DD, and package them using tar.
http://androidforums.com/behold-2-all-things-root/54424-creating-custom-roms-backups-odin.html
I would suggest that you just use the custom system instructions on that page, and then use the rest of the parts from Ayoteddy's original KG2 odin post, just to be sure that nothing goes wrong with the bootloader. the system part is factoryfs.rfs
sduvick said:
You would get your phone to the state that you want, and then pull system images using DD, and package them using tar.
http://androidforums.com/behold-2-all-things-root/54424-creating-custom-roms-backups-odin.html
I would suggest that you just use the custom system instructions on that page, and then use the rest of the parts from Ayoteddy's original KG2 odin post, just to be sure that nothing goes wrong with the bootloader. the system part is factoryfs.rfs
Click to expand...
Click to collapse
Legit dude. Thanks for the heads up. Might make my own rom pretty soon.
No prob, hope to see it up here.
The only file I am modifying resides in /./system/bin, thus the only partition I have to dump is bml9. Is this correct?
{
"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"
}
The sizes. Did he do an
Code:
$ ls -l
then take the size in bits and just add a plus sign for the tail command? If this is something I should do for myself do not respond.
Yes, only worry about bml9. Don't worry about the kernel piece in there, that's irrelevant. If you just root it and add the modded recovery, make sure that it works, then pull the bml9 (or stl9, can't remember which is in that thread), that will add root and CWM
Related
Hello,
I need help to recover my phone - Star s9500 after booting into factory mode and going to "Clear eMMC" (I know this was stupid of me but that is another story...). From MTKDroidTools, the phone hardware reads mt6582 and was running 4.2.2.
When the phone powers on, I only get the Android bootup animation and everything stops there.
I managed to install CWM using MTKDroidTools and even tried to flash the ROM using CWM after placing the zipped image on an sdcard. CWM simply aborts after attempting to read the zipped package.
For some reason MTKDroidTools does not show the IMEIs, but I can see the records when I power the phone into factory mode.
I tried to flash the rom using SP Flash tools as indicated in this thread:http://forum.xda-developers.com/showthread.php?t=2458369, but I simply keep waiting with the indicator "EMMC searching" from the tool or the phone itself even after 10 minutes (see attached files).
I am attempting to flash with this rom - http://www.needrom.com/mobile/star-s9500-mt6582-fwvga/ .
I did read somewhere that I have to setup partition information stored in the eMMC for the flashing to be successful. The post on this is here: http://checkrom.com/threads/formatting-emmc-no-no-no.647/ , but I believe I can get this phone up and running again.
Various sources say that I only need to flash the rom. Can someone please point me in the right direction? Why am I unable to flash with SP Flashtools? What alternative flash tools can I try? For pictures please see attached.
I am also now getting a BROM Error from SP Flashtools saying Failed to open COM 8.(see attached)
Thank you in advance!
{
"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"
}
S
Hi,
I see many people flashing whole firmware through ODIN just for changing their baseband (specially CM users). A simple way exist just for changing baseband.
What you'll need?
Rooted device
busybox installed
Terminal emulator
Baseband to flash
Click to expand...
Click to collapse
So what you need to do?
Extract firmware tar file & put modem.bin.md5 on your device as /sdcard/modem.bin.md5 (internal sdcard)
Fire up terminal emulator, get su rights by typing in terminal su
Now type
Code:
dd if=/sdcard/modem.bin.md5 of=/dev/block/mmcblk0p13
and hit enter.
Click to expand...
Click to collapse
Thats all...:good:
You can do this directly from CM based ROMs also...
As usual i'm not responsible for bricked devices...!
Newbie question. What is the help of flashing a new baseband ?
I have LQE (ROMANIA) baseband. Can I flash LQL (ITALY) baseband ?
Confirmation
Tested -> Working!
After flashing this, restarted my phone and a BIGGGG log file apeared in /data.
Look:
{
"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"
}
P.S. Sorry for new post! I had to edit the previous one....
BOOTMGR said:
Hi,
I see many people flashing whole firmware through ODIN just for changing their baseband (specially CM users). A simple way exist just for changing baseband.
Click to expand...
Click to collapse
There is also a flashable zip by t4n017.
So you can't make typos and brick your phone
Hi
I've downloaded and copied the update firmware files for my D2302, however when I try to create the FTF file it freezes while processing the first file. The decrypted file it creates has no data in it. Any ideas?
My end goal is to be able to have it rooted and if I'm really lucky, have a recovery. However, it doesn't look like
{
"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"
}
[D230X.properties, in Flashtool data] it even has a recovery (which sounds odd, but I can't get it to go into recovery by power+voldn - it just goes through to system. - I'm now trying to do root with locked bootloader methods.) EDIT: Turns out you have to mash voldn to get into recovery.
Thanks
Biscuit. said:
Hi
I've downloaded and copied the update firmware files for my D2302, however when I try to create the FTF file it freezes while processing the first file. The decrypted file it creates has no data in it. Any ideas?
My end goal is to be able to have it rooted and if I'm really lucky, have a recovery. However, it doesn't look like
[D230X.properties, in Flashtool data] it even has a recovery (which sounds odd, but I can't get it to go into recovery by power+voldn - it just goes through to system. - I'm now trying to do root with locked bootloader methods.) EDIT: Turns out you have to mash voldn to get into recovery.
Thanks
Click to expand...
Click to collapse
If you have an locked bootloader, install philz-twrp multirecovery and take a nandroid backup. I believe it's best to have a nandroid and and ftf (clean) because if you have some mod or problem with your current ROM and an FTF is your only choice it could end badly.
Sent from my D2303 using XDA Free mobile app
Been scratching my head on this one for a day or two, as while Kinguser/Kingroot works on my phone, it just doesn't cut it in my case and I wouldn't want to put my trust on something that's of dubious repute. Not that I am laying smack on the Kinguser team though, it's that I'm more confident with something the Android community is vouching on for years.
Things needed:
MTK Droid Tools
A working 5038A stock ROM. This image taken off a Smart-locked phone may work.
The latest SuperSU flashable image
Your phone
ADB drivers, and some patience
So what I did was this: Fire up MTK Droid Tools, and click on the Root/Backup/Recovery tab. Click on the Recovery and Boot button, and it'll ask you for a boot image from the stock ROM. Click Yes on the message box that shows up, and if done correctly you'll end up with a fresh recovery image on the recovery folder. Open SP Flash Tool, load up the scatter file from the ROM you just downloaded (or backed up), then load the recovery image you made earlier. You can either flash the whole ROM along with the CWM you did, or just the latter:
{
"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"
}
Once all that's done, boot to recovery by holding Volume+ and Power. Select the SuperSU package from your SD card, then let it do its thing. If done correctly, SuperSU should work properly on your device. Make sure to untick Mount namespace separation on the SuperSU settings menu for Titanium Backup to work correctly (c.f. djranoia).
You can try this image I made just in case; I can't guarantee that it works on any Alcatel OT-5038A out there though.
Code:
http://d-h.st/Ja0x
I don't take credit for all of this, but I'd just like to share this tip in case you feel like doing things the hard way.
Hi Guy,
I tried to remove the bootloader warning on SM-T290 https://forum.xda-developers.com/t/...age-on-samsung-a30-after-root-device.3954589/
But when I unzip the BL md5 file, there is no PARAM.bin inside. Actually, all files that were exacted from BLxx.md5 are not decodable.
{
"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"
}
And I also try to follow this: https://forum.xda-developers.com/t/get-param-bin-file-samsung.3782066/ to try to get the PARAM.bin file from the device, but all the param files I pulled are also can not be unzipped (using 7.zip)
I was stuck there for a long time and do not know should I continue to work on it and if someone are more familiar with FW and system files.
Any advice or help would be appercaietd.
Chochowneinei said:
Hi Guy,
I tried to remove the bootloader warning on SM-T290 https://forum.xda-developers.com/t/...age-on-samsung-a30-after-root-device.3954589/
But when I unzip the BL md5 file, there is no PARAM.bin inside. Actually, all files that were exacted from BLxx.md5 are not decodable.
View attachment 5266335
And I also try to follow this: https://forum.xda-developers.com/t/get-param-bin-file-samsung.3782066/ to try to get the PARAM.bin file from the device, but all the param files I pulled are also can not be unzipped (using 7.zip)
View attachment 5266337
I was stuck there for a long time and do not know should I continue to work on it and if someone are more familiar with FW and system files.
Any advice or help would be appercaietd.
Click to expand...
Click to collapse
The boot logo is in the bootloader, which is signed by Samsung. It cannot be changed. Also, the bootloader unlock message is in the bootloader. It cannot be removed.
Hi all, I'm here in Feb23 also looking to kill off the annoying unlock warning on an SM-T295 ( LTE version of T290 ). Is this option stone cold dead or was a solution found? I can just see other posts in different Samsung groups where the PARAM file has been located and shared for users to drop in. My SM-T295 is being re-purposed for a car install, so I just want rid of the annoying visuals/time loss as the car ignition feed triggers the launch of the device.