[Q] NV Partition - Oppo Find 7 and 7a

Hello guys. A while ago, I received a update/upgrade from Color OS to the latest version(don't ask me which one,cause I don't remeber :/ ).
So, I did the update/upgrade, and once I rebooted the phone,my NV partition was gone,as well as my IMEI..
But before all this, I was having unified storage made available by COldbird,and everything went fine,and I also managed to get the backup that was made when I unified the partitions.. And that backup is stored on my laptop.. I was wondering if there's any chance that I can use that backup to restore my NV partition and consequently recover my IMEI,although it's written on the back of the phone,and also in the invoice,sent by the crappy sellers( that aren't able of helping me in this situation,because the warranty and their store only fixes hardware issues: the seller is Mobicity UK btw )
I've already been in touch with Oppo, but so far haven't heard from them..
Right now,the phone is running on Nameless rom,but I can always get it back to the factory state,although it won't create the NV partition...
Any suggestion on how to solve this situation??
Thank's a lot for all the attention

Related

[Q] Probably defective EFS - how to restore?

Hey,
My phone somehow got messed up (Unable to mount /efs) and what I had to do is create a new partition and link it. It solved most of my problems (EFS was usable again and I could install roms etc).
What happened though is I can't register to a mobile network. After doing my share research I came to a conclusion that probably my EFS is messed up and it could be the reason why.
Now, I don't have EFS backup from before this problem started, as I was using stock rom and not rooted.
Is it gonna do me any good if I take an EFS backup from someone ELSE and try to restore it on my phone??
If yes, anyone mind doing me the favor of sending me their EFS Backup?
If not, what else can I do?
I have tried the following:
1) Install various modems
2) Install various roms
3) Downgrade to 4.3, install modem and kernel and upgrading again
4) I even took my phone to a shop and they used some equipment to burn my imei
I am currently using:
DN3 rom v5.2
CWM Recovery
Thanks
Edit: Solved by doing efs repair with the equipment thingy

(EFS corrupted) No IMEI and no Backup

Hey, my esf partitions seems to be broken after i flashed unofficial Ressurection Remix and later did a restore of my Oxygen OS 3.2.6 backup, now i do not have an IMEI number anymore. I tried clean flashing stock Oxygen OS in many versions but it never worked. I now switched back to Ressurection Remix and my Mac adress is restored, but still no IMEI. I only found solutions for the Oneplus One but i am not sure wich one would work for the OP3..
I really hope someone can help me, otherwise i learned an expensive lesson.
Looked around and not seen anyone who has managed to get their IMEI back on their OP3, maybe worth contacting OP support to see what they can do for you.
Have you tried the Chamelephon app to restore the IMEI?
podge3 said:
Have you tried the Chamelephon app to restore the IMEI?
Click to expand...
Click to collapse
this is why i said search the forums @Huthi
Not sure why you just made another thread when the problem hasn't changed
I did this remote desktop session with an OP support member but he didnt get it to work and told me i should send in my device.
The Chamelephone app throws out an error "processor type is not MediaTek" and when i proceed it doesnt seem to work, any suggestions?
I searched all forums for over 8 hours now and i am very desperate, i dont find a solution working for me.. I made a second thread because i think the first one wasnt specific enough and it can be deleted
I really hope someone knows a brilliant solution, because i am not able to find one anymore, nothing left to google about in my opinion
Btw when i flash Ressurection Remix i have an mac adress, with OOS not, so may this means my efs partition isnt messed up completely?
Huthi said:
I did this remote desktop session with an OP support member but he didnt get it to work and told me i should send in my device.
The Chamelephone app throws out an error "processor type is not MediaTek" and when i proceed it doesnt seem to work, any suggestions?
I searched all forums for over 8 hours now and i am very desperate, i dont find a solution working for me.. I made a second thread because i think the first one wasnt specific enough and it can be deleted
I really hope someone knows a brilliant solution, because i am not able to find one anymore, nothing left to google about in my opinion
Btw when i flash Ressurection Remix i have an mac adress, with OOS not, so may this means my efs partition isnt messed up completely?
Click to expand...
Click to collapse
you said you wiped all partitions except internal storage, so you also wiped the EFS partition, so i doubt there's a way to recover it without restoring a backup.
really can't think of a way to restore it without sending it into OP
You have learned a potentially expensive lesson BEFORE doing anything always backup EFS without fail.
Yea i guess i did
i thought nandroid backsup everything needed to restore a device 100 %
in twrp wipe the esf partition is not shown under advanced wipe so i thought it wont be wiped
the support said the only way may be a hardware exchange, lets bet on how much it will cost, 200€? naw man
Huthi said:
Yea i guess i did
i thought nandroid backsup everything needed to restore a device 100 %
in twrp wipe the esf partition is not shown under advanced wipe so i thought it wont be wiped
the support said the only way may be a hardware exchange, lets bet on how much it will cost, 200€? naw man
Click to expand...
Click to collapse
if you really did wipe your EFS and really don't have a backup, then there's literally no solution but paying up for a HW exchange, man
i dont think i did wipe it because twrp does not seem to have this option right?
yea i hope it does not cost too much
Huthi said:
i dont think i did wipe it because twrp does not seem to have this option right?
yea i hope it does not cost too much
Click to expand...
Click to collapse
someone correct me if i'm wrong, but im pretty sure that the fact that TWRP lets you backup your EFS partition to begin with means it also lets you wipe and restore it.
2x4 said:
someone correct me if i'm wrong, but im pretty sure that the fact that TWRP lets you backup your EFS partition to begin with means it also lets you wipe and restore it.
Click to expand...
Click to collapse
okay, but why doesnt it work after i restored a backup with working esf.. doesnt make sense to me, maybe my recovery is outdated but i dont think so.. no matter what i pay the bill and learned my lesson, if ever one guy reads this thread in a few weeks with the same issue: pay the bill and learn your lesson, backups are important and check twice if your esf is backed up, you will need it sooner than you think
EFS backup!! I need to do it now!! Sorry for the loss OP. Hope you get it fixed.
Sent from my ONEPLUS A3003 using Tapatalk
I don't own this phone yet(have nexus 6p) but I am buying this soon....usually when this happens to me....I reboot to recovery, wipe cache and reboot and all fixed....or flash back to stock and all fixed
Have you tried reflashing the radio/modem?.. That works on Samsungs so might be the go for you.
Huthi said:
okay, but why doesnt it work after i restored a backup with working esf.. doesnt make sense to me, maybe my recovery is outdated but i dont think so.. no matter what i pay the bill and learned my lesson, if ever one guy reads this thread in a few weeks with the same issue: pay the bill and learn your lesson, backups are important and check twice if your esf is backed up, you will need it sooner than you think
Click to expand...
Click to collapse
Getting confused here, did you actually backup the efs partition or not?
What partitions did you tick when you did the TWRP backup?
If you did do a EFS backup are the file sizes for both efs1 and efs2 around 2mb in size?
daleski75 said:
Getting confused here, did you actually backup the efs partition or not?
What partitions did you tick when you did the TWRP backup?
If you did do a EFS backup are the file sizes for both efs1 and efs2 around 2mb in size?
Click to expand...
Click to collapse
No i did not back them up the android sdk way, i only backed up my phone with twrp and i backed up all partitions shown to me except cache (efs was never listed in twrp) and so i restored my whole backup, wich seems like not including efs
No i did not try reflashing modem/radio but i surely do it before sending it in today
Huthi said:
No i did not back them up the android sdk way, i only backed up my phone with twrp and i backed up all partitions shown to me except cache (efs was never listed in twrp) and so i restored my whole backup, wich seems like not including efs
Click to expand...
Click to collapse
What version of twrp did you use? In the latest official version there is an option to back up efs
slonn said:
What version of twrp did you use? In the latest official version there is an option to back up efs
Click to expand...
Click to collapse
That's what's thrown me it definitely shows efs on TWRP 3.0.2-1
daleski75 said:
That's what's thrown me it definitely shows efs on TWRP 3.0.2-1
Click to expand...
Click to collapse
I recall that TWRP 3.0.2-1 had some problems with restoring efs and there was a warning posted on portal some weeks back. You should be regular on portal bro.
http://forum.xda-developers.com/nexus-6p/help/announcement-twrp-3-0-2-1-fatal-bug-t3453119
Edit: I see you're not the op, but still it is potentially dangerous for you too, to use that recovery's efs backing/restoring if you go ahead to help this guy.

Missing partitions

To cut to the chase…
My G5 (XT1671 32GB) has no IMEI. The one smart(?) thing I did before starting to screw around was make a backup with TWRP - 2 backups actually, one stock, the other AtomicOS. When I try to restore the backup I get an "unable to locate partition by backup name" message for these partitions: efs1, efs2, logo, oem. I gather the efs partitons are the ones that correspond to IMEI and other modem related things.
Is there any way to bring these partitions back? I've reinstalled the stock ROM (a few times now) and that doesn't seem to restore them (however when I try restoring I always get an error message on this line "fastboot flash partition gpt.bin"
Is restoring even going to fix the IMEI? From what I've read those backups are supposed to be an exact clone of the device - sort of like using Macrium to make an image of your PC (btw the backups include everything, whether it was needed or not ~6-7GB in size)
Cheers
Once you've flashed an oreo rom, imei will always be 0 when reverting to stock.
You could try this though: https://www.youtube.com/watch?v=XmKg84IXEbo
Going back to stock isn't the issue with the IMEI, it's whether you can turn off auto-update fast enough no to let an OTA update through (at least that's what screwed me)
I did run through the video you linked before hand. Kinda worked. Got 3G back, but when I tried the steps to restore 4G I just lost my IMEI again.
Still doesn't answer why I kept getting the missing partition message in TWRP. I do have full backups so you'd think restoring my efs would be the answer.
Turns out that was the answer… I have no idea what exactly happened but after trying the steps in that video again I decided to restore my AtomicOS backup (prefer it to Pixel Experience) for WIFI usage if nothing else. I got the same missing partitions message and this time somewhere during the restore process TWRP crashed/rebooted (could only boot as far as the bootloader menu). When I booted back into recovery to try and restore again I finally had all the options to restore my efs/logo/etc.. So I restored everything available (minus "system image") and am back to a fully functional AtomicOS.
I'm thinking I could also restore my stock backup now without problem now since I made it way before I ever tried any 64bit/Oreo roms. But ATM I don't want to tempt fate. Besides probably better to wait until Moto/Lenovo officially launches their Oreo update before considering stock again

[Help]Meizu Note 8 Softbrick after GSI Treble flash

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?

[help] imei unkown/00000 after restoring backup

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!

Categories

Resources