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
Related
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
Hello,
Today I've been trying to root my HTC One S (S3) and install CM11 (cm-11-20140210-SNAPSHOT-M3-ville)
1. I made successfull S-OFF
{
"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"
}
2. Installed wrong recovery (r2-modaco-recovery-clockwork-touch-ville.img)
3. Then installed correct (working) recovery for s3
4. Flashed my boot - fastboot flash boot boot.img
5. Made backup
6. Factory reset (everything)
7. Tried to install cm *.zip but here it is (tried also another CM's):
What is more phone freezes during start, display non-stop the same:
Help me please, what can I do ?
marcinostry said:
Hello,
, what can I do ?
Click to expand...
Click to collapse
did you downloaded the rom fir your device ?
cause, as i look at your pictures, that rom isn't for your device, see picture number 2,
or there's something wrong at updater script, contact your rom developer about the updater script
edit : you can aslo try to replace your recovery with the others, maybe it's the problem too
http://download.cyanogenmod.org/?device=ville
Here is source of my roms. However there is no info if they are for s3 or s4 ..
Problem SOLVED
ROMS located on the cyanogenmod site are for ville (but not ville c2).
I used "Stable: cm-11-20140110-UNOFFICIAL" from http://forum.xda-developers.com/showthread.php?t=2527962 because it's especially for C2
Before flash I had to flash the kernel file from THIS NEW version
Then made factory reset in TWRP 2 Recovery (versions for c2 - http://techerrata.com/browse/twrp2/villec)
Finally, installed the rom from xda and everything works fine !
{
"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"
}
Prerequisite:
- Must have Root
- Twrp should be installed
To get Android N Emojis:
1. Copy "AndroidNEmoji - for S7 Edge.zip" and "Backup - Emoji.zip" to a folder where it is easily accessible.
2. Reboot into TWRP.
3. Flash zip file - "AndroidNEmoji - for S7 Edge.zip".
4. Reboot.
Original link: http://www.androidauthority.com/android-n-emoji-686594/
Google did add some new emoticons, so those might show as [].
To Revert back to original:
1. Reboot into TWRP.
2. Flash zip file - "Backup - Emoji.zip"
3. Reboot
Credits:
Thanks to GadgetHacks and Shooting Star Max (providing the font + script)
Please flash at your own risk. I am not responsible for any damages you may receive from flashing this, although it is very unlikely.
Regards.
thanks for these...do you know if these work on swiftkey or not?
bilal91 said:
thanks for these...do you know if these work on swiftkey or not?
Click to expand...
Click to collapse
I don't see why not, but I haven't tried, so I won't know for sure.
Zer0_ said:
I don't see why not, but I haven't tried, so I won't know for sure.
Click to expand...
Click to collapse
i can confirm it does work with swiftkey but i prefer the original samsung ones tbh
to have TWRP, do you need to unlock bootloader? This will break Knox?
gd6noob said:
to have TWRP, do you need to unlock bootloader? This will break Knox?
Click to expand...
Click to collapse
if you got the international version you don't need to unlock bootloader, just click oem unlock in settings and put TWRP on the phone but yes it will trip knox
Hi I successfully rooted my device (Magisk) following the steps from the below link :-
after rooting my device I cross verified via root checker.......then reinstalled Magisk application and everything worked fine.
after that stupid me didnt know what i was doing and was playing with the Magisk application and clicked on the option install on the first option.
then the device asked to reboot and i rebooted.......after that my device is stuck in an endless reboot.
when trying to access TWRP am only getting android stock recovery.
conclusions :-
DEVICE STUCK IN ENDLESS BOOTLOOP !
UNABLE TO ACESS TWRP
NEED HELP IN :-
HOW TO INSTALL NEW FIRMWARE !
HOW TO REMOVE CURRENT OS FIRMWARE
{
"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"
}
Re-flash phone's Stock ROM to get rid off of all modificatins you applied so far.
jwoegerbauer said:
Re-flash phone's Stock ROM to get rid off of all modificatins you applied so far.
Click to expand...
Click to collapse
jwoegerbauer said:
Re-flash phone's Stock ROM to get rid off of all modificatins you applied so far.
Click to expand...
Click to collapse
HELLO THANK YOU FOR THE REVERT BUT I GET A BIG FAIL POP UP WHEN TRYING FLASH STOCK ROM VIA ODIN attached screenshots plsssss help me ! Am I doing anything wrong while flashing let me know .
Hey Guys !
It's been a long time since I left Android mods and a lot has changed since 2015
I managed to lost both the IMEI from my cousin Samsung A12(dual SIM) after tried this guide https://forum.xda-developers.com/t/installing-twrp-and-linageos.4334465/ .
The fault it's on me and not on the guide, I lost the backup file.
I managed to get until the last step before flash the Lineage OS from ADB Sideload.
I format everything and then i couldn't make a connection with the ADB sideload and tried to get back to stock firmware with ODIN.
After flash the firmware i lost both IMEI.
Things I tried :
~ Clean install with ODIN (from the guide)
~Tried to change the IMEI with different apps with root
~Right now I'm trying to install every possible ROM from this site https://samfw.com/firmware/SM-A125F/COS
{
"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"
}
All replies are welcome !
Best regards,
Leon
I thought MediaTek will change but its still the same pain in the ...
EDIT
I managed to get back both IMEI with this version, A125FXXU1AUC3 .
Just to help any other with the same problem.
Best regards,
Leon
Deleted but another alternatives is the downgrade or flash android 10 CP with the last update (This only works with binary 1 firmwares)
In my opinion is so stupid this bug/error and I tink the Knox 0x1 affects this problem (All firmwares with no imei problem has the secured by Knox splash) but is my opinion