Related
Hey guys
I was wondering why there are no custom roms which can be flashed with odin which retain knox warranty status?
Apparently you can alter the system image / partition and as long as you stay away from recovery and kernel partition the knox warranty will stay 0x0?
What else does RDLV do than use a modified system image? Thats why u get custom status, but knox stays 0x0 because you dont flash kernel or recovery.
So with odin tars just containing system.img we should be able to install custom roms without even needing CWM or any other recovery - we just lose the convinient method for backup/restore by staying stock recovery right? (and no adb in recovery, which actually sucks more imo).
---
We should actually also be able to install cwm zip files without a recovery right? Couldnt you just extract the zip and run the binary or the script from there? Or transform the update-script to a real sh file instead. Or are there "limits" as to what you can do on the running device vs recovery mode? Recovery mode is just a minimal os anyway isnt it?
Or is there maybe already some app or tool out there which can flash zips while device is fully booted?
And last but not least: Anyone tried side-booting a recovery image? Afaik you can boot images without actually flashing them onto the device right? Couldnt we just temporarily boot the recoveries without actually flashing?
---
I really want to beat this knox **** =)... (without tripping warranty hehe)
ohh i just found an app which can flash zips without recovery:
"Flash Gordon"
Pretty sure Knox checks the entire rom as a whole rather than just the recovery and kernel.
URDLV is done through hex editing a small bit of the rom/image. Not replacing an entire part of the rom.
It would be interesting though as we can flash roms without installing the new bootloaders, I wonder if there's a way to dummy up a rom to look like an official rom while being custom...
well I'm pretty sure custom (modified) system.img is alright. It doesnt matter what you change - the system is custom or its not (verified by signature scan or smth).
So if we pack up roms or mods into a modified system.img they should be flashable with odin without tripping knox.
I will try it out - I extracted a stock system.img.ext4 from MJ7 and will try to merge it up with x-note installer zip. The aroma installer is what giving me trouble - else I could just copy over all the files from the zip to the system.img and fix the permissions.
But creating a system.img from a "normal" rom zip without aroma or special choices during install process should be pretty easy:
1.) You need linux so that you can work with the permissions and mount the system.img as a directory etc.
2.) extract the system.img.ext4 from the tar.
3.) get simg2img and use it to "decrypt" the system.img.ext4 to a system.raw which then can be mounted with "mount -t ext4 -o rw,loop system.raw mount_point".
4.) Edit what you like and make sure the permissions are alright.
5.) repack to img.ext4. (forgot the tools name for that.. smth like "makeext4fs" or so)
6.) repack to tar
7.) add md5 and create tar.md5
8.) Flash through odin
---
I will try it as soon as I created my system.img.ext4 with x-note, but this gonna take some while - rom brewers could do this alot easier after rom creation though. (maybe we could even find a way to still use aroma installer or something else mimicking its actions)
---
ADD: Also wanted to add that that my experience so far is that the knox flag is pretty forgiving about what you do on your phone as long as you stay away from the kernel and recovery.
I deleted like everything related to knox (even the containers folder in system root with the extra apks and jars, also deleted tima_measurement_info which gets recreated every boot though, deleted or renamed some binaries related to knox like containersetup in /system/bin) and even modded my efs folder (tried to use my random mac script - but apparently the stock kernel ignores mac settings) and other pretty deep things, without tripping knox yet - so to me that seems like we can just do what we want with our system partition (and some others) as long as the kernel and recovery remain signed by samsung. (we really need to get our hands on this signing key somehow!!!!!!!)
If you flash a modified system.img it will trip Knox. Rdv only modifies bites of the IMG ..
Sent from my SM-N900W8 using XDA Premium 4 mobile app
DAGr8 said:
If you flash a modified system.img it will trip Knox. Rdv only modifies bites of the IMG ..
Sent from my SM-N900W8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Does that mean that it's not a check-sum lock? Even a bit would change the check-sum. What else could it be checking? Size?
It checks for signature. That's for sure not sure why modifying the zip doesn't trip it Maybe it's only matching part of it ..
Sent from my SM-N900W8 using XDA Premium 4 mobile app
So flashing a self-brewed system.img.ext4 (within an odin tar and including cache.img with CSC data - like the one URDLV spits out) does trip knox? Is this confirmed?
If it is confirmed, this means that while flashing the knox must be tripped - because you can just alter the system partition on a running system and it does not trip knox flag as far as I can tell. So how does this signature thing work anyway? You get the checksum of the whole rom and encrypt it afterwards and check against this? Because if so, then modifying anything on system would just trip knox. And if the signature is just some appended file or something then it is not really safe - because you could just leave that signature file intact.
I did not try it yet, but I'm really strongly believing that there is a way to get a custom system.img onto the device without tripping knox - maybe those who tried just messed up somewhere. But RDLV does modify the image - may it be "just" hex-editing or be it some other modification - modification = checksum wont match = detected as "custom" by syscope. And RDLV actually adds a line (or edits an existing one, not 100% sure) to /system/bin/ss-presetup.sh - that would definitely change the checksum etc.
---
What RDLV actually does on top of flashing the system.img.ext4 is also flashing the cache.img which contains CSC data afaik - so maybe the secret lies there - that you need the right cache.img for the corresponding system.img.ext4?
I will most likely just end up tripping knox by will just to have a custom recovery and kernel, but before that maybe I or we can learn a lil more about how the flag works?
Digital signature of system.img is not modified by RDLV but will be by building a system.img because it will be a new one
can you maybe explain how this digital signature works if you happen to know? If it checksums the whole image for example, it would be broken by the modifications RDLV does - and I doubt he's doin a signature "collusion" so that the checksum stays the same right?
How about this then:
You edit stuff ON DEVICE and dump the system.img.ext4 from the running note3 and flash that onto another or reflash it on your own device - this should also retain the signature shouldnt it?
Skipping the step of unpack/repacking of the img this way..
(just need to find a way to modify EVERYTHING on a running device - maybe have some files be changed on boot through scripts if no change is possible while the system is fully booted - I read you cannot change some lib files in system while system runs or it will crash / break the operation)
Hello guys i've installed merruk kernel 2.0 pre-final and my imei is blank. It don't recognize my sim card. I've made a full backup in CWM but it not worked. I want to revert ext4.zip process and install my stock kernel that i have a backup, is't possible? Will it restore my IMEI?
most likely the ril is not compatible with your baseband
I keep saying you cant use an old kernel with a new firmware baseband or you will loose imei
you can solve this by replacing the ril lib with an old baseband version
see
http://forum.xda-developers.com/showpost.php?p=52449987&postcount=232
try the hyp 8 ril - you can try others if you wish
if you want to return to stock you will have to flash stock rom via odin to convert your system from ext back to rfs
see
http://forum.xda-developers.com/showthread.php?t=2568853
you can then restore your stock nandroid backup as long as you restore it using the kernel and cwm from which it was made on
marcussmith2626 said:
most likely the ril is not compatible with your baseband
I keep saying you cant use an old kernel with a new firmware baseband or you will loose imei
you can solve this by replacing the ril lib with an old baseband version
see
http://forum.xda-developers.com/showpost.php?p=52449987&postcount=232
try the hyp 8 ril - you can try others if you wish
if you want to return to stock you will have to flash stock rom via odin to convert your system from ext back to rfs
see
http://forum.xda-developers.com/showthread.php?t=2568853
you can then restore your stock nandroid backup as long as you restore it using the kernel and cwm from which it was made on
Click to expand...
Click to collapse
My current ROM is the stock rom of S5360B, how do i do it without brick my phone in this case? what other methods should i try to restore my IMEI if this method not work?
Current ROM info:
Model: GT-S5360B
Version: Android 2.3.6
Product Code: ZTO
PDA: S5360BUTME2
CSC: S5360BZTOMJ1
MODEM: S5360BUTNA1
The GT-S5360B is exactly the same phone as a normal GT-S5360. It will work without much problems (if any), and it most probably won't brick your phone. Flash the zip for your baseband as per nornal (remember to mount /system)
Any other methods? I'm not too sure, apart from using Galaxy Toolbox to check your efs partition is damaged and backing up your efs partition.
Kaen22 said:
My current ROM is the stock rom of S5360B, how do i do it without brick my phone in this case? what other methods should i try to restore my IMEI if this method not work?
Current ROM info:
Model: GT-S5360B
Version: Android 2.3.6
Product Code: ZTO
PDA: S5360BUTME2
CSC: S5360BZTOMJ1
MODEM: S5360BUTNA1
Click to expand...
Click to collapse
no difference - you can flash 5360 on a 5360b if you want to
the only difference is the B version is branded varient of the 5360
you can use any file you like from the 5360 without any problems plus if you really want the 5360b firmware to flash stock rom via odin at a later date its also on my firmware thread
Ok, I'll try to install the stock rom via odin, hope it works . I have a doubt, I ran the ext4 converter. have i to follow this tutorial http://forum.xda-developers.com/showthread.php?t=2007720 or can i install without re-partition?
If it not working, what ril fix file can i use for my phone?
I'll update the result here.
Kaen22 said:
Ok, I'll try to install the stock rom via odin, hope it works . I have a doubt, I ran the ext4 converter. have i to follow this tutorial http://forum.xda-developers.com/showthread.php?t=2007720 or can i install without re-partition?
If it not working, what ril fix file can i use for my phone?
I'll update the result here.
Click to expand...
Click to collapse
Never tick repartition in odin
all you have to do is flash pda modem and csc - DO NOT tick anything extra
your phone will convert back to rfs from ext if you flash stock rom via odiin
I posted a load of rils from different basebands in post #2 of this thread - you can use what ever one you want - ril is dependant on rom firmware and kernel being used
marcussmith2626 said:
Never tick repartition in odin
all you have to do is flash pda modem and csc - DO NOT tick anything extra
your phone will convert back to rfs from ext if you flash stock rom via odiin
I posted a load of rils from different basebands in post #2 of this thread - you can use what ever one you want - ril is dependant on rom firmware and kernel being used
Click to expand...
Click to collapse
The phone doesn't recognized in download mode. It says "unknown device". I've installed Saumsung drivers and it's usb work fine but in download mode it not working.
Kaen22 said:
The phone doesn't recognized in download mode. It says "unknown device". I've installed Saumsung drivers and it's usb work fine but in download mode it not working.
Click to expand...
Click to collapse
then click unknown device
update driver
select folder
select the install location of the samsung divers (normally C:\Program Files\SAMSUNG)
if its not there then you havent installed the drivers
note - you do not need drivers for mass storage mode - you only need them for adb (download mode)
It worked! I've installed the stock rom and my IMEI is showing and the sim card is ok. Thank you all. But i have one more question:
I don't intend to continue with stock rom and stock kernel. What should i do to prevent this error occur by installing any custom rom or custom kernel? I've heard that i have to backup the efs, but the efs folder is always blank on galaxy y.
Kaen22 said:
It worked! I've installed the stock rom and my IMEI is showing and the sim card is ok. Thank you all. But i have one more question:
I don't intend to continue with stock rom and stock kernel. What should i do to prevent this error occur by installing any custom rom or custom kernel? I've heard that i have to backup the efs, but the efs folder is always blank on galaxy y.
Click to expand...
Click to collapse
the efs partition is empty on galaxy y because that partition is not mounted
you can backup your efs partition with galaxy toolbox but that wont help you with the problem you had
I keep saying its to do with the ril - you cant use an old kernel with a new firmware and vise versa
to solve this if you use an old kernel with a new firmware replace the ril lib of the new firmware with one from an old firmware
Iv even posted them
Hi All,
I'm not sure if this is the right place to post this as I'm relatively new to posting on XDA. My girlfriend has a Galaxy S4 (I337) that I quickly and easily installed Cyanogenmod on. It's awesome and significantly better than TouchWiz. So, I bought an S4 off Ebay assuming it would be similar enough. It turns out this new S4 is an I9500 and before shipping it was updated to 4.3, which appears to lock the bootloader and prevent downgrading. I've tried Odin, Heimdall, ADB, Philz, Chainfire, Cofface, stock ROMs, etc with no luck. Today I did manage to root the phone and confirm root with TowelRoot. I'm wondering/hoping someone might have some resources to get CM on this thing. While I'd prefer not to brick it I am willing to take risks as I have a Razr (soft-bricked and unbricked) running CM and am relatively comfortable with computers/Linux.
I've been Googling and trying things for a month now and can't even find that much information on the locked bootloader. Any help would be greatly appreciated, thanks.
--
SL
The I9500 doesn't have a locked bootloader. You just can't downgrade from 4.3 to 4.2.2 with official roms. Same applies when you are running 4.4, then you also can't downgrade officially.
Just flash a custom recovery true Odin and flash away.
Why would you even want to downgrade? Are you sure you are picking the right files? You cant flash the files for the I337 on the I9500. So just go to the section for the I9500 roms and flash away.
Hi Lennyz1988,
Thanks for the quick reply. I don't specifically want to downgrade but that's the last option I've tried. Ultimately the goal is to put Cyanogenmod on the phone. When I attempt to upload any file via Odin I get "secure magiccode check fail : boot" (or fail : recovery) depending on what I'm flashing. All the reading I've done says that when these phones are updated to 4.3 a fix has been applied that stops Odin from working. Thus, I my last resort is/was to try and downgrade. As I said, I've been Googling for the last month and while few people have posted about this I have not found any solutions.
Hoping someone might have a solution or anything new to try that I haven't tried already, thanks again,
--
SL
Download the latest TWRP recovery:
http://techerrata.com/browse/twrp2/i9500
Fire it up in Odin under PDA. You need the .tar (DON'T EXTRACT IT).
If it fails:
- Different usb port
- Different cable
- Different pc
- Reinstall drivers
- Make sure Kies is not running the background.
Or you can use heimdall to flash it. Use the command line though:
heimdall flash --recovery nameoftherecovery.img (you need the .img instead of the .tar)
No luck there, Odin still fails with the same message. I have tried Heimdall on 2 different computers (4 different usb cables) and always get the libusb 12 error.
Since I have root access I figured I might be able to wipe the recovery partition from a terminal emulator. I copied recovery.img from the I9500 CWM to the internal sd card. I then went to /dev/block/msm_sdcc.1/by-name to figure out what partition is recovery, turns out its 21. I then did “dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p21”. I then booted into recovery and it just hung up. I had previously found a stock recovery partition so I flashed that via Odin (the only file I have found that works flashing via Odin). I could then boot back into the normal recovery. I then tried flashing both recovery and cache with the CF Auto files (cache is partition 18). Same result, it just hangs when trying to boot into recovery. At one point I did manage to flash a recovery that then came up with a warning about “software installed that is not supported by AT&T” and I couldn’t get past that so had to flash the stock recovery again.
On a side note, I accidentally wiped the EFS partition in this process (if found a tutorial that shows the S3 had recovery in partition 10, which is EFS on the S4). As a result 1.) the menu didn’t pop up when I hit the power button and 2.) wifi didn’t work. So, I made an .img of the EFS partition on my GT-I337 and moved it to the I9500 and that worked restoring both. In case anyone makes the same mistake.
I have now also used CWM ROM Manager and GooManger and tried installing recovery that way with no luck.
Just check if the internal memory partitioning is correct ( number, size and format) (use fdisk or parsed).
ODIN will install according to the PIT file and if drivers and cables are OK it is no other explanation than that.
PS: do not trust heimdall data because it just read the PIT file and do not give the true info from the memory part.!
Uhm on the TWRP website they say that the I9500 has it on partition 10.....
This would be the proper partition based on their website:
mmcblk0p10
Are you absolutely sure you have an i9500? Because my guess is that you don't.....
Boot into download mode. What does it say your model is?
Because on the AT&T it's partition 21.... So my guess is that you are messing up....
Thanks everyone for the input/feedback,
Something I think I had forgotten to mention previously, when the initial root/recovery attempts didn't work I downloaded an app to verify it is a genuine Samsung as I have heard of very good knock-offs. It is genuine according to the app.
Good point/catch regarding the location of the recovery partition. Under About Phone it shows as an I9500 and always has. When in download mode it currently shows as I337 but I wasn't sure if that was simply a result of all my attempts so I figured best to go with the one I am certain has been the same since I bought the phone. I had been hesitant to try wiping the recovery with for the I337 as that is how I soft-bricked my RazrHD (ultimately un-bricked it).
Tonight I will try the I337 files and see if Odin is successful. Thanks again.
Damn! Turns out my phone is an I337. The hardward (under the battery) says I9500 and when I plug it into a computer it shows up as I9500. On the weekend I thought I read that there is now the ability to flash recovery and install CyanogenMod on I337 if its updated to 4.4.2. So, I donwloaded the firmware and flashed with Odin. It flashed successfully but now I realize I am mistaken and 1.) cannot flash recovery, and 2.) cannot downgrade. For the time being I have installed Nova Launcher and removed as much of TouchWiz as possible. It's not perfect but at least usable. I'd like to start researching what it would take to flash recovery on this phone but I suspect I'm too busy at this moment.
Thanks everyone for the help,
First of all Ive been reading for yours looking for a solution.
My case: I was using Sixerperience V3 from Geiti94, I flashed wrong build prop and lost signal after that. I have a previous EFS folder backup.
What I did:
1) try to flash modem using Odin (more sthan 3times)
2) Flash firmware using Odin
3) Flash firmware using odin
4)install again Sixexperience
5) TRY SOME CODES I FOUND
THE MOST EXTRANGE THING. AFTER THE BUILD.PROP FLASH AND TILL NOW PHONE REFUSE TO REBOOT OR TURN OFF. IT ALWAYS GET STUCKED IN THE PROCESS WHEN I SELECT IT. IF I DONT TOUCH NOTHING IT REBOOTES ITSELD
PLEASE WHAT MORE CAN I DO. CAN I DAMAGE HARDWARE BECOUSE OF BUILPROP
THANKS
Hello Fellas, am posting here as I haven't found help elsewhere. Kindly Respond to my woes. I have a rooted Galaxy Note 3 N900 running official Lollipop with IMEI Null/Null and No Baseband version. The IMEI just disappeared totally out of the blue as no custom ROM has been flashed on the device!! This has happened 2 months after updating from 4.3 Jelly bean. With no prior EFS Backup here's what I have tried:
1. EFS Professional (backup&restore complete but no luck)
2. EFS Restore express ( backup.bat>Odin restore)
3. GSII Repair tool
After hitting no luck with the above tools and without any "/EFS mount errors" in recovery either and WIFI working fine, I came to a conclusion that most probably the EFS folder partition on my Note 3 is still intact and most probably this could be a case of a bad modem which would explain the loss of Baseband Version and thus the Null IMEI. So I tried flashing back to KitKat with N900XXUENG1 firmware and separately flashed a few modems compatible with Samsung's new EFS System: N900XXUENG1_MODEM, N900_XXUENF2_MODEM_CWM and also gave a shot at recommended N900_XXUENE1_MODEM_CWM.ZIP which seems to restore baseband for many users with this issue but this failed as well. After much searching I found a 4file_N900XXUGBNL8 Lollipop Firmware with PIT from Dev-Host, flashed all files in Odin&even repartitioned the device but still no baseband!!! WIFI&everything else runs smooth except the damn baseband/Null IMEI! Almost Exhausted my options...
Now I trust we have some informed members and developers here, NEED YOUR VALUABLE IDEAS HERE mates! Someone, anyone.....Thanks!
Have got any guarantee of the device?If so,send it to service ıf your guarantee continiues.
If you bought the device from another country,This may occur ıf you didn't register it.(In my country this is how it works.Turkey)
Or someone cloned your imei,check your imei ıf it is valid.
This is not because you upgraded your device to android 5.
If ıt was the case,you would have already faced the problem after just the flash.
I would say flash another modem
But,You say you tried flashing other modems.So no luck with that.
I had seen s3 with the same problem.I had flashed a modded modem.
It worked.I dont know if there is one for your device.
Briefly this is an imei/modem problem.
I don't know ıf the suggestions above help you.
I hope so.
Good luck.
try flashing stock rom from sammobile via odin. you need to backup efs folder everytime you flash a new rom, that's my opinion. may be wrong.
I think I used to had this problem with my Note 2 as well. If you come from 4.3 you should flash stock ROM Jelly bean 4.3 from Sammobile or Samsung-updates website. Then flash lollipop 5.0 over 4.3 when you can see your IMIE. Maybe it will work.
So. If u in L bootloader. U must! Flash the L modem that sometimes didnt get flashed by the odin while flashing stock rom. So just extract the modem.img and things for modem. Then just flash it using dd command or make flashable zip. Then it works fine. I have it on s4 exynos. That if i in L bootloader then even i install kitkat rom with L bootloader. U must still flash the L modem. K. Hope it works
1. İf you couldnt recover with efs professional , probably you've been lost your original imei files like nv_data.bin etc. and there is no backup...
2. So try to remake this kind of files with-again- with efs professional. But there is not so much info about this "creation" process.
3. I had the same situation. . . . And i'm still sorry. . . ( . . . The other solution is JTAG, more easy, cheaper in total and psychologicaly healty !!!)
GOOD LUCK....
m6112 said:
1. İf you couldnt recover with efs professional , probably you've been lost your original imei files like nv_data.bin etc. and there is no backup...
2. So try to remake this kind of files with-again- with efs professional. But there is not so much info about this "creation" process.
3. I had the same situation. . . . And i'm still sorry. . . ( . . . The other solution is JTAG, more easy, cheaper in total and psychologicaly healty !!!)
GOOD LUCK....
Click to expand...
Click to collapse
All EFS folder files are present including nv_data.bak&.bin Am a bit reserved to go the JTAG way just yet.
white7561 said:
So. If u in L bootloader. U must! Flash the L modem that sometimes didnt get flashed by the odin while flashing stock rom. So just extract the modem.img and things for modem. Then just flash it using dd command or make flashable zip. Then it works fine. I have it on s4 exynos. That if i in L bootloader then even i install kitkat rom with L bootloader. U must still flash the L modem. K. Hope it works
Click to expand...
Click to collapse
Thanks for that but as I already said I was lucky to find a 4file partitioned Lollipop ROM with separate modem. Flashed that through Odin and even repartitioned the device but that hit a rock as well!
longcoming said:
Have got any guarantee of the device?If so,send it to service ıf your guarantee continiues.
If you bought the device from another country,This may occur ıf you didn't register it.(In my country this is how it works.Turkey)
Or someone cloned your imei,check your imei ıf it is valid.
This is not because you upgraded your device to android 5.
If ıt was the case,you would have already faced the problem after just the flash.
I would say flash another modem
But,You say you tried flashing other modems.So no luck with that.
I had seen s3 with the same problem.I had flashed a modded modem.
It worked.I dont know if there is one for your device.
Briefly this is an imei/modem problem.
I don't know ıf the suggestions above help you.
I hope so.
Good luck.
Click to expand...
Click to collapse
It's an old device, no warrants. Am indeed looking at the possibility of someone else allocating the IMEI to their device, though i doubt. But if that was the case shouldn't the Baseband at least be present?
Did you try downgrading to 4.3 with official stock files?
If not,give it a shot.
Droidsan said:
It's an old device, no warrants. Am indeed looking at the possibility of someone else allocating the IMEI to their device, though i doubt. But if that was the case shouldn't the Baseband at least be present?
Click to expand...
Click to collapse
I have explained it earlier, Actually it is kernel. Newer kernel makes some changes on EFS partition and that changes can not be read by old kernel but in this case once you flash newer modem it will be solved. If your issue doesn't solved by flashing latest stock ROM then only possibility is messed up EFS partition and for that you must have a backup which was created when your device was normal. If your EFS partition is corrupted and you don't have backup then i think only option you have is to go to service station they can repair it easily. Though your device is not under warranty but you have official bill then still they can do it with paid service. Now a days samsung have changed policy and restoring IMEI they needs to do it online with samsung server (this information I got from service center owner in my city who is my friend and he did same for one of my friend)
UPDATE:
dr.ketan said:
I have explained it earlier, Actually it is kernel. Newer kernel makes some changes on EFS partition and that changes can not be read by old kernel but in this case once you flash newer modem it will be solved. If your issue doesn't solved by flashing latest stock ROM then only possibility is messed up EFS partition and for that you must have a backup which was created when your device was normal. If your EFS partition is corrupted and you don't have backup then i think only option you have is to go to service station they can repair it easily. Though your device is not under warranty but you have official bill then still they can do it with paid service. Now a days samsung have changed policy and restoring IMEI they needs to do it online with samsung server (this information I got from service center owner in my city who is my friend and he did same for one of my friend)
Click to expand...
Click to collapse
Thank you Dr.Ketan for that information. You have been a great help to many. I have followed your posts about this issue and I feel there is still hope.
UPDATE:
I WAS ABLE TO RESTORE THE BASEBAND AND NOW THE IMEI IS GENERIC, READS 004999010640000. [/B] I was able to restore nv_data backup from /Efs folder and deleting bad nv_data. Here's what I did:
Using root Explorer in /EFS:
Deleted corrupt files;
nv_data.bin ( 18 April 2015)
nv_data.bin.md5 (18 April 2015)
Renamed backup files (dated 31 Jan 2015) to apply;
.nv_data.bak > nv_data.bin
.nv_data.bak.md5 > nv_data.bin.md5
Using ADB shell:
Code:
adb shell
su
umount /efs
mke2fs /dev/block/mmcblk0p3
mount -w -t ext4 /dev/block/mmcblk0p3 /efs
Reboot
However, the baseband and generic IMEI come&go across reboots and seems not to stick permanently. Any possible steps from here???
NOTE: Previously I have been able to restore Unknown Baseband and Null IMEI in Galaxy S2 i9100 using the above adb method (Code Only) http://www.selftechgenius.com/?p=284
NOTE: Previously I have been able to restore Unknown Baseband and Null IMEI in Galaxy S2 i9100 using the above adb method (Code Only) http://www.selftechgenius.com/?p=284
Try this out
I always have that problem when I downgrade to jellybean but solving it is easy. Just flash THIS modem file under the AP option Odin. Tell me if it works.
Muthumbi said:
I always have that problem when I downgrade to jellybean but solving it is easy. Just flash THIS modem file under the AP option in odin mode. Tell me if it works.
Click to expand...
Click to collapse
If flashing modem via Odin you MUST turn off the phone then start it in DL mode. Simply doing a 'reboot' into DL mode will not let the modem be flashed.