Hello. If anyone has the opportunity and desire, help, please, solve the problem.
About 3 years ago, a friend bought this phone in a Vodaphone salon.
Once at work, he was discharged to zero and turned off. After trying to charge, I went into the bootloop. The logo appeared and the phone turned off and so on endlessly. He ditched it and bought a new one.
The phone lay until he decided to revive it in order to give it to the child.
They took it to the service, they just looked at the model and said that they would not even take it.
On some Indonesian resource, I found a global firmware and instructions. Everything was done, the phone started up, it was updated by air to 10 android. But with the firmware, the nvram file went away and imei.
If it is possible to make a full backup of the firmware for a flash drive with nvram or just a backup of nvram.bin, then I would be grateful.
Nowhere on 6750 mt I can not find a file database for recovering nvram and imei
Tried it using MAUI meta - it does not load the file, the modem does not detect it correctly, asks for a local db file. Have a change to relatives from the box. The main thing is that at least some program should determine it correctly.
Hello - it's not my upload, but I found the ROM here.
Related
If anyone else has encountered something similar to this issue See the URL link below ! solved this issue
Evening XDA, *update**I think this is what the problem might be , will confirm later this evening after i get a chance to try it ** http://forum.xda-developers.com/showthread.php?t=2332913
Ive been flashing my androids ever since my GS2 - never had a problem..Well maybe a few but nothing a few hours of google and xda forums hasnt solved.
However as of a couple of days ago I was on Alliance Rom v3.0 for The N7100 , I decided it was time for a change ( note at this point nothing was out of the ordinary )
I downloaded the Stock Firmware ( just to test out Al-lplay with my new blu-ray player , and to see how bad stock looks these days )
I downloaded the firmware from Sammy Mobile, latest one ect all correct model..blah blah.
Rooted the stock firmware using odin 3.07, followed by applying TWRP recovery.
I had the Alliance V3.1 rom ready on my EXT SD card - So as i would normally go about doing it i'd started to flash this new rom.
After flashing i'd noticed it didnt apply - the stock rom had prevailed !...so repeated the flash procedure again...it applied this time..... however I now had no signal ?! strange !?
Ive Never had any issue with flashing and losing serial numbers or IMEI numbers, so at this point it wasnt backed up ( stupid i know !, but over the past 3 years ! ive not had any problems what so ever ! )
I thought the best option would be to wipe clean, and do a fresh install of stock rom and root/recovery and flash again !!
Same problem...
This time I decided maybe there was a problem with this file, so tried another ROM
Applied fine, however same issue...signal but its not registering on network !?
Went back to stock...to my horror...not registering on network...immediatly thinking..how ironic that i didnt back my efs folder up..and this had happned, checked my IMEI it had gone to the temp IMEI that loads of people have reported that flashing had given them.
Immediatly backed up my EFS folder ( knowing myself that its too late )
Tried flashing , Wannam Rom, Alliance Rom v3, Project AOSP, all with the same results...no signal or not registering on network ! all these showed my IMEI being the default one not my actual IMEI on the phone and box itself !
starting to have a little panic as my phones my only means of communication ( par from my Mi-fi ) I wasnt even able to call a local phone shop to enquire if they repair IMEI ect.
As a last effort I wiped the phone, flashed stock with odin, rooted/stock ect and deleted the old efs folder and pasted the same folder I had backed up earlier ( even when it wasnt working then ! )...and to such relief....it seemed to re-apply the correct IMEI ! happy days !
however...im still unable to flash any other Rom as it seems to clear my IMEI
thanks for reading this long dribble post, im at work and having to come back and add to this, when i get a spare moment ( appologies for the spelling and gram)
but any help or checks would be much app'd !!
Ry2mkk
I had a problem once that made my phone not ask for a pin, and not have coverage.
It turned out the recovery I used was wiping a little bit to much, and took out the modem too.
I didn't look at the imei, but in "Settings - About Phone - Baseband" it said something like it's unavailable.
To get it to work again I flashed TWRP (Team Win Recovery Project) http://teamw.in/project/twrp2/115, download a Stock rom from samfirmware.com, extract both the zip and the .tar.md5, open odin and put the modem file in the phone field.
Then flash just that, onlu modem, nothing else. That made it work for me. And after I switched to TWRP I have not had the problem.
well, i flashed only the modem, but it still didn't solve the problem
i am the problem as his...
beyarfaj2004 said:
well, i flashed only the modem, but it still didn't solve the problem
i am the problem as his...
Click to expand...
Click to collapse
It was the same for me.
Some one now?
Try to flash stock rom again maybe it will help you
Sent from my GT-N7100 using xda app-developers app
Hi guys
So my battery had decided to swell a few days ago in my Note 2 GT-N7100, and suddenly my phone lost network and couple of days later, didn't go beyond the logo screen. I got the new battery (needed to tell my mother that it was NOT my fault that the phone died on me, and she insisted I use the old battery till the day phone dies so couldn't get the new battery before since I had no money and they are pricey stuff) but the problem persisted so I turned to recovery mode, which claimed that my /efs file was missing and could not be loaded. I did not have the slightest clue such a thing existed before this. Needless to say, /efs was NOT backed up. This was my first smartphone too, so I had no clue.
I did manage to get my phone running after installing the firmware by Odin and using CWRM to get to root and disabling factory mode, but it seems the IMEI and Serial number are still not right. The IMEI number starts with generic 0049XXXXXXXXXX and the Serial number is 4df7e1b53a26cfcd, which is not same to the S/N given behind the back of my battery. I really need help salvaging this; I want to avoid going to Samsung Customer Care since, well as I mentioned before, my mother has allergy on spending on anything which has 'Tech' written over it, and this will lead to me getting stuck with this phone without being able to really use it. Is there any way out? Please help!
Edit: I tried to flash a modem into it, and right now /efs is an empty folder and the IMEI and Serial number situation is unchanged. My mind is on a merry go round. Seriously need help here!!!!!
Hello everyone! I need some help because i'm out of ideas how to resolve the softbrick on my old phone. First i'll explain how i got it in this state:
So i have 2 meizu note 8 i don't use anymore (one with broken touch and lcd, and the other was perfectly fine), and because of boredom and covid restrictions i had the "brilliant ideea" to mess with them and update to android 10 with GSI treble roms. The original android was flyme os 7.1.6.1 EU. First i unlock the bootloader on both and installed twrp recovery. No problems so far , everything worked fine with flyme os. Then i tried to install gsi android 10 with twrp on one of the phone (the one that does not have the screen broken). I had an error with system partition not mounting , so i did a full format in twrp (cache, data, system,internal storage, boot,vendor) and then i managed to flash it. Android 10 GSI (Havoc Os) booted up but with problems : First i got a message right after boot "There's an internal problem with your device. Contact your manufacturer for details" then the config wizard crashed constantly, but i managed to finish the process and android is working (sort of ).The problem wich i called it soft brick is the fact that wifi, data sim,bluetooth, gps, sound are not working (not detected, nada....).Both IMEI are correctly recognized, but the basic functions of the phone don't work.
Having another identical phone with original firmware, i made a full twrp backup (21 partitions..with system,data,cache, modem,kernel,vendor ....everything) and restored it on the culprit. Flyme os booted up but with the exact same symtoms as with GSI 10. It seems i messed up somewhere so i reverted back to stock flyme os recovery and flashed the original software (update zip form their website). Still the same symtoms. So I went further and got the flyme os files for QPST / QFIL flash tool. Flashed it successfully with QFIL but no improvements. I suspected the modem firmware being corrupt and flashed it separately, but i just can't get it to work.
So any ideas? I have the msm partion table and trying to pull everything with adb root and adb shell from the other phone, and restore it back to the other, but got stuck somewhere....(i'm doing more research).
A short update. Apparently the persist and persistbak partitions got corrupted or formated by me (tho twrp does not have option to format persist). This partition is responsible for calibration data for all sensors and baseband. So that's why i had all these problems.
Right now i'm trying to pull those partition images form the other phone and flash them on the bricked one.
Got it resolved. Flashing persist.img partition resolved all my problems but the IMEI and baseband got deleted .So it was necessary to pull *.qcn backup file from the working phone with QFIL program, manually edit both IMEI within qcn file with HEX editor , adding the right ones, and then restore it in the bricked phone.
Now it's working as it should.
I'm writing this in case someone gets their phone soft-bricked like mine. Hope it helps. It got me 2 full days, researching and testing things out!
Hi, I got the same exact problem after doing the flashing using orangefox, all sensors and camera not working even after flashing the original global rom via Qfil. I have been looking for that persist.img file to help me fix the issue. could you please share the Persist.img file here? you will really help a brother
hi there! i have also the same problem... accidentally formatted all partitions in orangefox recovery, been going through all night in recovering my Meizu note 8 here.. i bricked it and been looking for a firmware everywhere, and now i found a flashable firmware through qspt, im getting the same problem here, i've been looking everywhere to where i can get persist image and qcn, im not sure if my emei is messed up though.. i really need ur help also... i need this phone for my game development progress
Hi! I need the flashable firmware of the Meizu Note 8 7.1.6.1G please. I can't find it anywhere.
X-NeRo-X said:
Got it resolved. Flashing persist.img partition resolved all my problems but the IMEI and baseband got deleted .So it was necessary to pull *.qcn backup file from the working phone with QFIL program, manually edit both IMEI within qcn file with HEX editor , adding the right ones, and then restore it in the bricked phone.
Now it's working as it should.
I'm writing this in case someone gets their phone soft-bricked like mine. Hope it helps. It got me 2 full days, researching and testing things out!
Click to expand...
Click to collapse
can you share file with us?
Hello there,
I'll start from the very beginning...
My old Samsung Galaxy S9+ have a crack on its screen but my phone is insured so I got a new one, I backed up all of the files on the old one using TWRP backup (EFS, DATA, VENDOR, SYTEM, CARRIER, BASEBAND, RECOVERY, ODM). I tried restoring my old data to my new phone, it did the trick but there was a problem, the IMEI is UNKNOWN (00000), I tried scouring EVERY solution I could find to fix the problem but to no avail. Here's the list of every solution I could think of (although I'm sure I did a lot more than that) :
1. ODIN FLASH TO STOCK ROM (G965FXXSBETH2) I USED THE CARRIER ROM (Optus)
2. REPLACE THE DEVICE ID ON THE EFS BACKUP AND RESTORE (USING HEX EDITOR)
3. USE A COMBINATION FIRMWARE
4. REPLACE THE SIM CARD
5. IMEI MAKER/REPAIR
Okay now to explain why all of those didn't work :
1. I flashed it to stock ROM but it still didn't work for some reason, I figured it's probably because the ROM isn't really for refreshing IMEI
EDIT: I tried re-partitioning, pit and Nand erase but it didn't do anything.
2. I tried hex editing the efs backup for TWRP to restore but it still detects it as 00000
3. I can't use a combination firmware because the bootloader is updated (apparently I cannot downgrade) and every time I try flashing it, it just comes up with SW REV check fail (Bootloader) error
4. Well I tried, I though by replacing the SIM card I'll MAGICALLY get my IMEI back.
5. IMEI MAKER/REPAIR didn't do anything, I followed the specific instructions and got my IMEI number into it but when I flashed it via TWRP, my IMEI still remained the same.
Conclusion:
Yes, I learned my lesson and I should ALWAYS backup BEFORE I restore. I need HELP and I'm just in a desperate situation, I've been at this for 3 days now (maybe longer). My foolish self didn't untick EFS, Baseband, Carrier configuration or anything related to cellular phone internet before restoring. Somewhere around me buggering with the settings, my phone thinks it has 2 SIM slots (which it doesn't) but I'm sure that's not the problem. Please help me.
For reference with the IMEI MAKER/REPAIR here's the link to what I used
https://forum.xda-developers.com/cr...lashable-zip-imei-repair-android-one-t2992846
EDIT: Silly me, of course it won't work because it's for Android One devices ONLY.
Holy ****, never mind that. Thanks for fixing my phone @hainguyenthao you're a legend!
Holy ****, never mind that. Thanks for fixing my phone @hainguyenthao you're a legend!
Holy ****, never mind that. Thanks for fixing my phone @hainguyenthao you're a legend!
Good evening you absolute legends!
After quietly reading along since 2013 and flashing a few phones over the years thanks to you, I'm now at a point where I can't think of anything to do with my problem.
So I bought my dad a used G960F for his birthday and wanted to install Lineage OS just as I did with mine a couple months ago. To make things short, in the meantime all ROMs I used where deleted, so I did the same procedure but with other ROMs, and well ... bricked the phone. After a week or so I finally got it working (didnt know about Samsungs bootloader hierarchy and couldn't flash a ROM with a lower BL), just to find out now that in the process the IMEI got deleted completely.
After seeing too many shady websites this is what I tried so far:
Flashing with a Pit-File + NAND Erase and Re-Partiton
Flashing stock rom (tried both Android 9 and Android 10)
Erasing everything or only parts of the efs/ folder, even though I only found that applied to other Samsung phones than mine
One ROM I tried back when the phone was bricked was from _alexndr, and I found one post where a user also lost IMEI after using it but got it back when he installed the ROM again. This one I will try out now.
So I have one G960F working but with empty IMEI. Not a bunch of zeros, its simply empty. I know one correct IMEI, since its printed on the OEM box three times. (Don't know why they dont print both numbers on the box....). I've seen a bunch of semi-(il)legal Apps that let you change the IMEI, but I dont feel like getting into that and it wouldn't help me with the second IMEI.
(Additionally, I have my own G960F completely working, if it helpes in any way.)
Does any of you have any ideas left or has experience with such a problem?
Either way, thanks for taking your time with me and everybody else!
Cheers Anthony
Hi guys!
I solved my problem and maybe my way can help some of you.
As I understood from _alexndr's thread [1] is that you can not only not go down a BL-Version when flashing, but you can't also go down in the CSC version. But while doing the first thing resolves in an error while flashing, the second one simply works but therefore can't detect the IMEI etc sometimes.
My solution in the end was to flash _alendr's kerlel, force my CSC module (maybe this parts isn't necessary) while flashing and and then installing the BL he provided [2].
Even though this thread stayed empty, I still wanna thank all of you for keeping up so much work!
[1] https://forum.xda-developers.com/t/...vbase-v7-4-encryption-support-may-09.3764822/
[2] https://forum.xda-developers.com/t/...support-may-09.3764822/page-151#post-84984391