Well, Hi!
A little history before the real problem.
My girlfriend bought a U8800-51 phone by my recommendations, because it's a great phone in this range of prices.
The phone had a problem. It reboot many times in a day (10~20 times) So I decided to upgrade the OS to GB with the gingermovida v1.1 ROM.
The phone stopped in the bootanimation secuence. I tried 5 times with the same result.
I downloaded the official 2.2.2 ROM from the Huawei website and put it in the SD card. I turned on the phone in download mode and started the install secuence. But stopped in the 2/2 step with the "Update Failed" message.
I tried to enter in recovery mode without success, with 5 different "recovery.img" files. In a thread in this forum somebody explained a method to back to stock froyo ROM using a .img file and the Roadkil's Disk Image tool, but with a AT&T img file.
My brother has the same phone so i made a backup of his phone and put it in my girlfriend phone. Everything works great! Boot OS and load all the information, 3G work and USB Mass storage work, so I did a wipe data - factory reset and everyrhing works again.
At this point I discovered that the IMEI is the same of my brother's phone. I tried many different tricks or tutorials (QPST, CDMA Tool, DFS, AT Command in Terminal, etc) and nothing changed. In the last try I upgraded the OS using CM7 movida v2 and 3G works, WiFi works, but I still have the same IMEI and a new problem came out. When I plug the USB cable and activate the Mass Storage Mode, only shows a Read Only CD drive with all SD Card files.
In the stock froyo ROM I went to the "Project Menu" and changed the USB options, but I can't remember in what option I leave it. In this ROM (CM7 movida v2) i can't go to this menu and check if I have the same Stock ROM configuration.
Besides, I didn't backed up my GF'S IMEI. So I don't know if it can be recovered.
She's gonna kill me, so I need a little help ASAP!
That's all. So here's the thing:
- I have the same IMEI of my brother's phone.
- Everything works except for the Read-Only Mass Storage Mode.
P.S: I don't know if the different driver that I installed affect something here.
Try to upgrade your phone, puting dload folder on sdcard, maybe it can fix your IMEI. About the mounting, I dont know what is happening, but maybe if you upgrade your OS, it will work fine..
What ROM can I use? The Official Huawei ROM (Movilnet U8800-51) didn't work (to solve the IMEI problem) If I try to downgrade using that ROM the phone stop in the 2 step and then I will need to do everything again.
What about B565? You can download it here: http://www.huaweidevice.com/cn/downloadCenter.do?method=toDownloadFile&flay=software&softid=NDEyMTU=
And I also found this topic, there is a user who says the solution so check it out http://forum.xda-developers.com/showthread.php?t=1513439
Well, that ROM is for PRO version of the U8800 phone and I have the U8800-51 version. Baseband and other thing are different between versions. I will try the steps of your link when my girlfriend let me try again
Sorry, my mistake :/
I dont own a u8800 51 but the software isnt the same as u8800?
No, unfortunately, like I said: Baseband and other tiny thing are differents :crying:
-.-" Wait a bit, maybe someone will help you
Do you have any sort of backup from where you were when the phone worked correctly?
that's why I don't share backup. The fw on the -51 is tightly locked. I'm surprised they allowed pink screen. Your better off going for warranty. Unless, you can open the background password. I'll look for an alternative fix.
Sent from my U8800-51
eyeconic said:
Do you have any sort of backup from where you were when the phone worked correctly?
Click to expand...
Click to collapse
I don't have any backup.
Somcom3X said:
that's why I don't share backup. The fw on the -51 is tightly locked. I'm surprised they allowed pink screen. Your better off going for warranty. Unless, you can open the background password. I'll look for an alternative fix.
Click to expand...
Click to collapse
But I tried with differents codes for the background password without success
0, 000, 1234, 111, 999... etc nothing work
xolott said:
I don't have any backup.
But I tried with differents codes for the background password without success
0, 000, 1234, 111, 999... etc nothing work
Click to expand...
Click to collapse
Gotta love Att.
Sent from my U8800Pro using Tapatalk 2
Related
Hi there!
I have bricked my phone and it is in "download" mode.
Is there a way to "bring it back" with Odin?
Thanks!
M.
Did they repaired your phone for the second time? If not, what did they said? What did you do in the first place that you bricked it?
Sent from my Ideos X5
Still waitin'
Nobody called me, don't know what's happening with my phone.
Get back here when new info available.
No, Odin is for Samsung
Better try to flash stock rom
http://forum.xda-developers.com/showthread.php?t=1205307
darkfiremark said:
No, Odin is for Samsung
Better try to flash stock rom
http://forum.xda-developers.com/showthread.php?t=1205307
Click to expand...
Click to collapse
People still doesn't read. I said that it is bricked! Cannot install anything on.
Brgds
What do you mean by download mode? if you turn it on with vol up and down and power held, what happens?
Try put stock rom (2.3 or 2.2 depending on what was on phone before) in dload folder on sd card and it might flash firmware off that.
If you're on download mode then you can upload a recovery an boot image. Do it and use that to flash any rom you want.
I appreciate people trying to help. But sometimes it is good to stay quiet. So please, don't reply with funny suggestions.
Thanks.
Hello;
What, exactly, is "download mode"?
For someone how's in need of help, you should take it easy on the atitude and provide more info for those sparing a moment of their lives to try to help you out, no?
bonowax said:
Hello;
What, exactly, is "download mode"?
Click to expand...
Click to collapse
http://androidforums.com/vibrant-tips-tricks/177526-how-enter-download-mode-what-worked-me.html
VuDuCuRSe said:
For someone how's in need of help, you should take it easy on the atitude and provide more info for those sparing a moment of their lives to try to help you out, no?
Click to expand...
Click to collapse
I am just trying to say that sometimes it is better to no reply at all.
If i said that the telephone is bricked and only in download mode you should know what does it mean before you reply. That's all. No hard feelings.
Try using a FAT32 formatted sdcard, with nothing in it but the dload folder with a stock ROM.
Couple days ago, I deleted all files from my U8800's FAT32 and EXT4 partitons - yes, even the 'image' folder, connected to my Linux box.
Because I wanted to revert to stock Froyo, i dumped back partition 5, from a backup I did some months ago - but this part is not relevant.
Formatted the card, dumped the dload folder into it, with a card reader; removed the battery and followed the procedure described in your link.
First try, it displayed some error message - can't remember - second try it showed up the pink screen, followed by the blue screen and initiated the ROM flashing. My phone is now fine and dandy... Oh, it rebooted three times after installing stock Froyo, so don't be alarmed when you get there.
Cheers
Good luck
bonowax said:
Try using a FAT32 formatted sdcard, with nothing in it but the dload folder with a stock ROM.
Couple days ago, I deleted all files from my U8800's FAT32 and EXT4 partitons - yes, even the 'image' folder, connected to my Linux box.
Because I wanted to revert to stock Froyo, i dumped back partition 5, from a backup I did some months ago - but this part is not relevant.
Formatted the card, dumped the dload folder into it, with a card reader; removed the battery and followed the procedure described in your link.
First try, it displayed some error message - can't remember - second try it showed up the pink screen, followed by the blue screen and initiated the ROM flashing. My phone is now fine and dandy... Oh, it rebooted three times after installing stock Froyo, so don't be alarmed when you get there.
Cheers
Good luck
Click to expand...
Click to collapse
I tried all you mentioned 30 X and more then that But no success
Btw: if you dumped back your partition from backup you had access to internal memory ... i don't have that connection neither on Ubuntu or Windows. I got pink screen but it is in "Download mode" only.
Thanks.
Can you explain me how did you get your Huawei u8800 enter in Download mode if it's a feature of some samsung smartphones to work with odin ?
You're being a little rude for those who're tryin' to help you, you should be more polite ma friend...
You didn't even say what rom were you using... so I guess you don't even deserve any help from anybody.
Peace
I've had download mode on my previous Android device - LG GT540. All it needed to enter such mode was to remove the battery, SIM and sdcard , and plug the USB cable. It would enter download mode and allow a stock ROM to be flashed with the standard LG update tool.
Actually, I dumped partition 5 back to the phone prior to erasing every file system in it, and indeed had pink screen mode access in order to do it...
Sorry it didn't work out for you.
Loureiro said:
Can you explain me how did you get your Huawei u8800 enter in Download mode if it's a feature of some samsung smartphones to work with odin ?
You're being a little rude for those who're tryin' to help you, you should be more polite ma friend...
You didn't even say what rom were you using... so I guess you don't even deserve any help from anybody.
Peace
Click to expand...
Click to collapse
I've installed some custom ROM and after reboot it stopped to boot in HUAWEI logo. And that was it. I have tried to install official ROM's all of them with standard methods (dload folder) but every time ends in step 2/2 (installation failed or something like that). I opened up new thread with that few weeks ago:
http://forum.xda-developers.com/showthread.php?t=1466953
This thread was supposed to answer my question at the top. And some guys did. I don't know how can thread be closed by the author. I've try to find it but with no success.
I appreciate people like to help. But if people don't know what i am asking why answering and asking questions that are answered in many threads before.
You see .. this thread should be as small as possible but ends with looong explanations which doesn't help at all
Peace.
Moved To Q&A
We now have a Q&A section. Please post all questions there
My friend has got a Samsung I5800 Apollo (Galaxy 3) which he claims it cannot make or receive calls. He asked me what might be wrong with it. I'm not saying its lost or stolen but why else would it not work? Only other thing could possibly when it was unlocked to networks the phone imei got messed up? I've seen some phones get all zeros.
i'd suggest unlocking it with superoneclick. if that fails, maybe replace the phone.apk?
Honestly, i think the simplest solution when u have serious prblms like that is to backup all ur data and just flash a new ROM. I can wholeheartedly recommend Kyrillos' ROM v9.5. Hasnt let me down once!
Sent from my GTI5800 on Kyrillos' ROM v9.5 using xda
I will probably test that rom out at some point. Thanks
Sent from my GT-I9100 using Tapatalk 2 Beta-4
I had a similiar problem, android process force closed when I tried to call. I am trying to flash my phone right now but the problem is, the phone now bootloops. Damned roms...
digitalni said:
I had a similiar problem, android process force closed when I tried to call. I am trying to flash my phone right now but the problem is, the phone now bootloops. Damned roms...
Click to expand...
Click to collapse
You didn't by any chance restore your system data with TiBa when changing roms?? And not to sound patronising but you can enter recovery mode (if available on your kernel) by pushing Vol Up+Vol Down+Home+Power buttons together and restore factory settings, or download mode to flash from Odin by pushing Vol Down+Home+Power buttons together.
Okay i got the phone today and it was on 2.1. I updated it to AOKP just to test and it installed fine. But the sim card does not get found at all. I tried 2 sim cards that work in my sg2.
If there any place I can check to see if the phone has actually been locked to use?
Sometimes problems like this can be caused by framework-res.apk. Try flashing a custom ROM and see if it works.
PiracyX said:
Okay i got the phone today and it was on 2.1. I updated it to AOKP just to test and it installed fine. But the sim card does not get found at all. I tried 2 sim cards that work in my sg2.
If there any place I can check to see if the phone has actually been locked to use?
Click to expand...
Click to collapse
If I'm not wrong, AOKP is an ICS ROM, and I'd read that ICS has a bug and don't see the sim card untill you remove the pin.
Wont work without disabling Pin on SIM.
i'm gonna quote the solution i had with the exact same problem when my emei got corrupted:
marcel i found out what was teh problem corrupted EMEI - efs....
i was lucky enough to have a nv_data.bin backed up in my sd from ages ago!
i dowloaded an efs.tar flashed it through odin and then copy nv_data.bin from sd -> /efs and then
chown 1001:1001 /efs/nv_data.bin
i inserted my sim and VOILAAA!!! this is a know problem with cm7 and since someone will get this problem these are the links that will solve the problem:
http://forum.xda-developers.com/showthread.php?t=859914
http://forum.samdroid.net/f60/tutori...artition-3600/
http://www.madteam.co/forum/support-7/no-network!!!/
Click to expand...
Click to collapse
I got this message after updating to android 4.4.4.
What could be causing this?
term44 said:
I got this message after updating to android 4.4.4.
What could be causing this?
Click to expand...
Click to collapse
Hi check your IMEI see if it is correct...
Could be the wrong modem or a bad EFS do you have an EFS folder back up
MAX 404 said:
Hi check your IMEI see if it is correct...
Could be the wrong modem or a bad EFS do you have an EFS folder back up
Click to expand...
Click to collapse
Checked the IMEI, it is ok.
term44 said:
Checked the IMEI, it is ok.
Click to expand...
Click to collapse
If is not hardware, chances are that the efs folder is corrupted.
Try a different kernel
Try a different modem
Flash full wipe custom rom again..
Last flash stock rom...
If all fails the problem most like it is in the efs folder, if you have a backup restore it
MAX 404 said:
If is not hardware, chances are that the efs folder is corrupted.
Try a different kernel
Try a different modem
Flash full wipe custom rom again..
Last flash stock rom...
If all fails the problem most like it is in the efs folder, if you have a backup restore it
Click to expand...
Click to collapse
would try that all, but the phone refuses to connect to pc now, so i can not transfer the files... any suggestions?
it says that device driver did not install properly. i have installed kies in order to push drivers to my pc, but still same.
term44 said:
would try that all, but the phone refuses to connect to pc now, so i can not transfer the files... any suggestions?
it says that device driver did not install properly. i have installed kies in order to push drivers to my pc, but still same.
Click to expand...
Click to collapse
De install drivers and install them again , try another usb port , make sure kies is not activated
MAX 404 said:
De install drivers and install them again , try another usb port , make sure kies is not activated
Click to expand...
Click to collapse
just done that and still cant connect. however odin detects the phone, which is good :=) so i will install stock rom.
hopefully that will solve the problem with the sim card..
term44 said:
just done that and still cant connect. however odin detects the phone, which is good :=) so i will install stock rom.
hopefully that will solve the problem with the sim card..
Click to expand...
Click to collapse
restoring to stock rom solved the problem
term44 said:
restoring to stock rom solved the problem
Click to expand...
Click to collapse
Glad is working mate
Back up before you do anything else do not forget to backup the efs folder
Sent from my Nexus 7 using XDA Premium 4 mobile app
same issue.
I have the same issue as described by the op.
I flashed back to official 4.4.2 and the problem persist.
IMEI number is correct.
IMEISV is 01
Ive been trying to fix this for over a week to no avail. Losing my mind. Is there anything else you can suggest to fix this issue?
Phone is an i9500.
Was really hoping for some help by now. This will be the second time ive posted to this site in the 2 years ive been here with zero responses.
As a side note. I wanted to add that at the same time i started having the "not registered on network" error my sd card stopped being read by the phone also. I replaced the sim/sd holder in the phone itself hoping this would fix both issues but it has obviously not. Still not reading the sd. Says its blank or unrecognized file system. When i try to format it it doesn nothing. This is the sd I had in the phone before having issues. It worked fine then.
The phone just suddenly stopped working one morning. I used it to send a couple text and make a call, next time i picked it up "not registered" issue began. No changes to the phone in between those times.
I figured I would add this info in hopes of gaining a response.
Thanks.
The Core Prime will not boot into recovery, or safe mode, or to the home screen. The only way to sometimes get it into download mode is leave it plugged into the wall charger for a couple minutes, then it will SOMETIMES go into download mode to charge. Holding down every combination of keys does not work, please don't suggest holding down keys.
All I ever see is a mmc confirmation fail movinand checksum confirmation fail error no matter what I try. I never see the Samsung intro, boot intro, or tracfone intro anymore, just a black screen that leads to that error message in red letters.
Regardless of which computer or cable I use, Windows never sees the phone. Doesn't try to install the drivers, doesn't make a sound that something was plugged in, nothing shows up in device manager, nothing (even in download mode)
I called 800 Samsung (4 times asking the same thing to different people to make sure I didn't just get helped by a noob over the phone). I went and talked to the Samsung guys inside worst buy (didn't do anything except informing me there is a Samsung store in LA). I called the Samsung store in LA and talked to a technician and the technician supervisor (I could drive there if their answer wasn't factory reset)
But EVERYONE from Samsung is saying all that can be done is factory reset.
I do not need a factory reset. I need my data.
I have posted numerous threads, and even though there was good advice given, none of it worked.
All I did before this error was try to update Google maps. The phone has never been backed up/rooted/nothing its stock.
At this point, I'm willing to negotiate paying someone to get my data back.
Someone please help.
Sorry To Hear that this is really a big problem but every thing has a solution ..
As you say the windows doesn't read the device and so as Odin try http://tinyurl.com/Heimdall-oa on Linux (don't use virtual machine )
OK if Heimdall read the device flash stock firmware (same version) if the device open congratulations
else flash custom recovery (you can find one in cyanogen discussion) and launch aroma file manager pull out your data so you're safe to reset ?? hope to be helped you .
The x man said:
Sorry To Hear that this is really a big problem but every thing has a solution ..
As you say the windows doesn't read the device and so as Odin try http://tinyurl.com/Heimdall-oa on Linux (don't use virtual machine )
OK if Heimdall read the device flash stock firmware (same version) if the device open congratulations
else flash custom recovery (you can find one in cyanogen discussion) and launch aroma file manager pull out your data so you're safe to reset ���� hope to be helped you .
Click to expand...
Click to collapse
Thank you for trying to help me. I do not yet have a Linux box set up. Can you recommend a distro, version, or live cd of Linux to use?
You can use Ubuntu 14.04
The x man said:
You can use Ubuntu 14.04
Click to expand...
Click to collapse
I will post my results here as soon as I try
If your phone is still stuck, flash TWRP (google it if you don't know it) for s820l. After TWRP is installed backup your data to your Internal or External Storage. Once the backup is complete factory reset (I highly suggest bakcking up to an SD card) if it still only boots to this screen try flashing the Stock ROM.
If your phone is messed up after the factory reset, i suggest SD card for files and everything if your computer has an SD adapter and reader you won't need to turn the device on. Hopefully this fixes it for you.
P.S. By no means do I know exactly what I'm doing, I flashed the wrong TWRP for mine and only got a download screen. This is the method i used to fix it. Also i am not allowed to post links or I would. so google sm-s820l custom recovery and to get a Stock ROM. Above the page for it should be a bunch of tabs that look like this " Android Area 51 > Forum > Straight Talk/Net10 > Samsung Phones > Samsung Galaxy Core Prime > Recovery Releases" Click on Samsung GCP and then your all set. Hope this helps.
AJOKER21 said:
If your phone is still stuck, flash TWRP (google it if you don't know it) for s820l. After TWRP is installed backup your data to your Internal or External Storage. Once the backup is complete factory reset (I highly suggest bakcking up to an SD card) if it still only boots to this screen try flashing the Stock ROM.
If your phone is messed up after the factory reset, i suggest SD card for files and everything if your computer has an SD adapter and reader you won't need to turn the device on. Hopefully this fixes it for you.
P.S. By no means do I know exactly what I'm doing, I flashed the wrong TWRP for mine and only got a download screen. This is the method i used to fix it. Also i am not allowed to post links or I would. so google sm-s820l custom recovery and to get a Stock ROM. Above the page for it should be a bunch of tabs that look like this " Android Area 51 > Forum > Straight Talk/Net10 > Samsung Phones > Samsung Galaxy Core Prime > Recovery Releases" Click on Samsung GCP and then your all set. Hope this helps.
Click to expand...
Click to collapse
Core prime model is also G-360* (main number) not just SM-820L .
The x man said:
Core prime model is also G-360* (main number) not just SM-820L .
Click to expand...
Click to collapse
True so if it's not the SM-S820L just input your model number instead of the one I posted that was my bad I assumed TracFone. Also don't think just because the phone is the same they will all work if you do use the wrong TWRP or ROM because the model is different it will brick your device. Again it was my mistake but overall I hope this helps.
AJOKER21 said:
True so if it's not the SM-S820L just input your model number instead of the one I posted that was my bad I assumed TracFone. Also don't think just because the phone is the same they will all work if you do use the wrong TWRP or ROM because the model is different it will brick your device. Again it was my mistake but overall I hope this helps.
Click to expand...
Click to collapse
Never mind i just wanted to share info. + mine reply was before twrp or cwm being ported to core prime ,and at this time no custom roms for 360* Models
Is TWRP ported to other versions of this phone? It seems like it is atleast the VE one has it and my TracFone version does I'm sure most of the others ones do and you also do not need a Custom ROM just a stock one which is probably floating around out there somewhere. For the OPs phone which if the model was posted this would be a billion times easier. So Mr. OP please post your model for us to help if your issue is still happening.
G360 Rom
AJOKER21 said:
True so if it's not the SM-S820L just input your model number instead of the one I posted that was my bad I assumed TracFone. Also don't think just because the phone is the same they will all work if you do use the wrong TWRP or ROM because the model is different it will brick your device. Again it was my mistake but overall I hope this helps.
Click to expand...
Click to collapse
I have a SM-S820L that i flashed with a 360 and now its bricked
Hii @android_n this is also happen with me on My core 2 G355H I also try to flash Offical frimware but it only boot for few second and shut down
I replace battery with new one and it booted
Problem is in battery it only boot when charger is connect or you can charge your phone battery by booster charger hit thanks if I help
I tried that what i need is a new OS. It keeps telling me No OS is installed but Havent been able to get it installed
noxqes said:
I tried that what i need is a new OS. It keeps telling me No OS is installed but Havent been able to get it installed
Click to expand...
Click to collapse
Check out this thread here http://forum.xda-developers.com/gal...stock-rom-deodex-busybox-root-t3378999/page1. Hope this helps
Sent from my SM-G360T1 using XDA Labs
Hi Guys.
This is a Mediatek Helio X25 Redmi Pro and it came to me bricked from its owner who tried to root it the wrong way. I managed to flash an official rom and bring it back to life but as apparently is the case with these phones, the nvram has been corrupted/rewritten and there's no Imei numbers on the phone, which means no calls and stuff. WiFi works fine. I've already had permission to unlock the bootloader but obviously I can't do anything about it since the software won't ID the device. I believe I might be able to flash a backup of nvram.bin, but I don't have one from this phone, which is why I am posting this here, hoping that maybe one of you can help me by sending me a copy of his own Redmi Pro nvram.bin file. Of course I only need it to get the thing back in the system, after which I can unlock it and use the original Imei numbers. Or if someone has another suggestion, I would greatly appreciate it.
Thanks in advance.
Search for SN writer. Then follow the steps from en.miui.com/thread-198017-1-1.html
Of course you have to have the original imei stickers for the numbers. Entering random numbers is illegal AFAIK.
This will fix your IMEI.
Binnylaw said:
Search for SN writer. Then follow the steps from en.miui.com/thread-198017-1-1.html
Of course you have to have the original imei stickers for the numbers. Entering random numbers is illegal AFAIK.
This will fix your IMEI.
Click to expand...
Click to collapse
Thanks for the reply, friend. I have tried that, as well as almost every other solution provided on the internet apart from the deepflash cable, but I keep getting error messages. And yes, I do have the original Imei numbers and it's those that I'm trying to restore. It just seems that something has gone really wrong in the boot partition and it won't let me do anything there. I'm out of ideas. The phone works fine, except for sim service; I am able to flash roms, but not fully. There's always 3 files that won't be downloaded to the phone using SP Flash Tool. I cannot use MiFlash because the phone won't boot on EDL mode. Any other suggestions you might have, I appreciate them.
Cheers
nsterjo said:
Thanks for the reply, friend. I have tried that, as well as almost every other solution provided on the internet apart from the deepflash cable, but I keep getting error messages. And yes, I do have the original Imei numbers and it's those that I'm trying to restore. It just seems that something has gone really wrong in the boot partition and it won't let me do anything there. I'm out of ideas. The phone works fine, except for sim service; I am able to flash roms, but not fully. There's always 3 files that won't be downloaded to the phone using SP Flash Tool. I cannot use MiFlash because the phone won't boot on EDL mode. Any other suggestions you might have, I appreciate them.
Cheers
Click to expand...
Click to collapse
Tried this method?
http://en.miui.com/thread-411112-1-1.html
Sent from my Redmi Note 4 using Tapatalk
If your phone is booting, I am pretty sure your snwriter version is wrong. Please use this exact version and let us know.
snwritetool.com/download/sn-write-tool-v1-1648
Binnylaw said:
If your phone is booting, I am pretty sure your snwriter version is wrong. Please use this exact version and let us know.
snwritetool.com/download/sn-write-tool-v1-1648
Click to expand...
Click to collapse
I have tried maybe 3 different versions of Sp Flashtool, including this one. I usually get a timeout message. But I will try again. Is there any specifics I should observe regarding the mdb files I need to use? I have tried all the ones that come with the roms I've tried, but without luck.
MaYbe I misunderstood.. You said ur phone is booting fine... and u are on an official ROM. If that is so, you should not use SP FLash to fix IMEI.
SN writer is needed to fix IMEI.. MDDB_InfoCustomAppSrcP_MT6797_S00_MOLY_LR11_W1603_MD_MP_V13_18_P69_1_ulwctg_n.EDB is the MDb file for developer ROM 7.3.6 and APDB_MT6797_S01_alps-mp-m0.mp9_W17.09 is the APDB...
Click on Dual IMEI and enter the two IMEIs.. Switch off the phone before connecting to the USb cable... Make sure you use the original Mi black cable. Now connect the phone without pressing ANY button at all.
That should do the job!
Binnylaw said:
MaYbe I misunderstood.. You said ur phone is booting fine... and u are on an official ROM. If that is so, you should not use SP FLash to fix IMEI.
SN writer is needed to fix IMEI.. MDDB_InfoCustomAppSrcP_MT6797_S00_MOLY_LR11_W1603_MD_MP_V13_18_P69_1_ulwctg_n.EDB is the MDb file for developer ROM 7.3.6 and APDB_MT6797_S01_alps-mp-m0.mp9_W17.09 is the APDB...
Click on Dual IMEI and enter the two IMEIs.. Switch off the phone before connecting to the USb cable... Make sure you use the original Mi black cable. Now connect the phone without pressing ANY button at all.
That should do the job!
Click to expand...
Click to collapse
No, you understood fine; it was me who typed SP Flashtool instead of SN Writer, which was what I meant. Everything else is as I wrote. I have tried 3 different versions of SN Writer, I connect fine and it starts the procedure following the same instructions you mentioned, but it stops half way, giving me an error message. I have tried different combinations of MDB and APDB files from several different ROMs I've downloaded, but they all fail. I'm not very familiar with these things but I can follow instructions and am quick to learn. Still, I have no idea why SN Writer or Maui Meta are not working. I tried to download an nvram.bin file I got from the internet with SP Flashtool, but it would not accept it as it was for Helio X20 I believe, which is why I was hoping someone would make available a copy of nvram.bin for this particular phone. I will also try to make a deepflash cable, hoping that might get me into EDL after which I can use MiFlash to reflash a new official Rom, but I don't know if it will work.
help please
Binnylaw said:
MaYbe I misunderstood.. You said ur phone is booting fine... and u are on an official ROM. If that is so, you should not use SP FLash to fix IMEI.
SN writer is needed to fix IMEI.. MDDB_InfoCustomAppSrcP_MT6797_S00_MOLY_LR11_W1603_MD_MP_V13_18_P69_1_ulwctg_n.EDB is the MDb file for developer ROM 7.3.6 and APDB_MT6797_S01_alps-mp-m0.mp9_W17.09 is the APDB...
Click on Dual IMEI and enter the two IMEIs.. Switch off the phone before connecting to the USb cable... Make sure you use the original Mi black cable. Now connect the phone without pressing ANY button at all.
That should do the job!
Click to expand...
Click to collapse
Hi there, please can you tell me where I find the files (mdb and adb)? Are they somewhere on the phone's firmware? Or somewhere in the rom i flashed?
I'm a beginner having a very similar issue having flashed a rom in rescuing a bricked phone and now have invalid IMEI numbers.
Thanks so much