hello all ive got myself into a problem with my phone where its only booting into apx mode which at the moment isnt much use, ive found one way that may fix it but i would need someone to extract there APP and LNX and SOS from there phone, if someone is willing to help id be very grateful and can give instructions if needed
thankyou in advance
bish
nvm ive tried this way and not succeeded., if anyone has any ideas please let me know.thanks
does anyone know if nv flash even works with our phones, ive tried a few commands but always the same thing about write failed
Please give some details ,, what did you tried ?? ,, what happend ?? ,, tried reflash the *.KDZ or not ?? ,, Tried to *.DZ by LG flash tool or not ?? .
Of course I'm willing to help , but what do need ??
I'm ready to help any one needs help as well as I can .
Sent From My LG-P880 (O4X) .
By Pressing "THANKS" You Will Help Me .
hi thankyou for replying. basically all im able to do is get into apx mode (nvflash), stupidly i decided to test the thing that i found where the phones with the unlockable bootloaders(23400) could use the chinese kdz v20a and id stumbled across that we could apparently unlock the bootloader. although we had the it saying it was unlocked we had the problem of the system acting otherwise, so i dumbingly thought right if its not actually unlocked i shouldnt be able to remove the bootloader and done the command fastboot erase bootloader and now am stuck in this position
i have backups of of the main partitions( APP and SOS LNX) ect but not sure if useful) and the problem is currently im getting usb write failed with nvflash
i cannot boot into s/w mode or recovery although sometimes i can connect to my pc and it says that a usb composite device cannot start
thankyou for replying i deeply appreciate it
There are at least two ways to get into SW, with or without battery. Did you tried both? Pressing vol+ instead of vol- gives you another mode, you tried? Try them all after re-install the drivers and with LGFlash Tool. Select all ports and see if you have communication.
Sent from my LG-P880 using xda app-developers app
hmm... as I know you full-bricked your device ...
you need to enter download mode by an external action (from PC) using ''usbboot.exe'' to load two files that will turn on your phone into download mode by the command :-
Code:
usbboot <2ndstage> <image>
for example (for LG-P920 (LG Optimus 3D)) :-
Code:
usbboot p920-aboot.2nd p920-u-boot_fastboot.bin
then flash the bootloaders :-
Code:
fastboot flash x-loader x-loader.img
fastboot flash u-boot u-boot.img
this will force the phone into download mode or fastboot . by fastboot flash bootloader and by download mode flash *.DZ system .
but the problem is ...
we don't have these two files (*.2nd & *.bim or *.img) those are nessesery for this process .
I don't have the skill to port/make/compile them ..
Try contact a good Tegra 3 Developer so every CPU family has its own files to boot .
If your device was from OMAP44xx family I could help you because the files are exist , but Tegra 3 ... it's a little new .
Good Luck
there is some u-boot.img and x-loader.img for the p880 here in the forums.i have my normal boot.img ect and even the contents of sys and the dev folder alll backed up also back nandroid backups if any of them would be useful.
thankyou OS_HACKING you have at least give me something that i can look into and a glimmer of hope. if i manage to fix it i need to learn to not meddle with the phone and leave any hacking to the pro's. really gutted as my phone is like my right arm,its with me 24/7 and im usually always on it.. ive had to use my old acer a500 of my daughter for now and its such a big change
@RuedasLocas
yeah mate ive tried both methods, the only thing apart from apx mode is occassionally it says there is a device that cannot start when connected to pc,.thankyou also mate i appreciate help from you both
friartuckme said:
there is some u-boot.img and x-loader.img for the p880 here in the forums.i have my normal boot.img ect and even the contents of sys and the dev folder alll backed up also back nandroid backups if any of them would be useful.
thankyou OS_HACKING you have at least give me something that i can look into and a glimmer of hope. if i manage to fix it i need to learn to not meddle with the phone and leave any hacking to the pro's. really gutted as my phone is like my right arm,its with me 24/7 and im usually always on it.. ive had to use my old acer a500 of my daughter for now and its such a big change
@RuedasLocas
yeah mate ive tried both methods, the only thing apart from apx mode is occassionally it says there is a device that cannot start when connected to pc,.thankyou also mate i appreciate help from you both
Click to expand...
Click to collapse
In mine (V20A), APX doesn't work.
It was already hard to do something in V10x, in V20A the device is not even recognized...
Probably the best change will be using (or try it) LGFlash Tool or Official B2CApp to flash a V10x version, and probably the best
will be a V10A.
Don't forget to check if you're using the correct .dll.
Check if you have the latest drivers:
http://www.4shared.com/file/rPpP2btT/LGUnitedMobileDriver_S4981MAN3.html
http://www.4shared.com/file/ZSMf2x6n/LGUSBModemDriver_Eng_WHQL_Ver_.html7
Goog luck on that. :fingers-crossed:
my pc finds it in apx and installs the drivers , also i can get it too recognise there is a device there for nvflash, i think that i would have to use Wheelie along with nvflash. when ive tried one way to revive my phone with nvflash it stated that the partition couldnt be found. which i guess is because im using the flash.bct and flash.cfg from ICS Bootloader which was extracted a while ago, il need to get them from the jb bootloader
ive got the u-boot.img and x-loader from our phones if they are needed
if not i guess il just have to save money to buy another 4x hd.i cannot see myself loving a phone as much as i like the 4x
thankyou
ive done some more looking around and trying different things, and it seems to even have the chance to get anywhere il need the following extracted from jb, the flash.cfg and the BCT and bootloader.bin. i found an nvflash that didnt give me the unknown device error but it stopped at it couldnt find the partitions mentioned the current partition table i was using(it was from ICS which i think some partitions was named different
friartuckme said:
ive done some more looking around and trying different things, and it seems to even have the chance to get anywhere il need the following extracted from jb, the flash.cfg and the BCT and bootloader.bin. i found an nvflash that didnt give me the unknown device error but it stopped at it couldnt find the partitions mentioned the current partition table i was using(it was from ICS which i think some partitions was named different
Click to expand...
Click to collapse
And how can I extract that?
You tried ADB? Maybe (if it works of course) pushing those unsecure img to unlock the EUR-XXX can bring it to life somehow...
I'm really out of ideas.
I tried APX with several drivers but the only thing I got was a bluescreen and a computer crash... device remains unknown
I think that nvflash for our phone needs some encryption keys (SBK keys) and AFAIK nobody has founded what they are so far. They may be Imei or sn dependant. So I think you can't use nvflash and maybe its better to send device to LG service if you can.
thats what wheelie is for, also id have thought that if the bootloader could be erased from within fastboot wihtout an sbk and, which isnt as low level as nvflash wouldnt it be different,
remember i dont have a bootloader thats signed with an sbk or communicates to the fuse, i know that on the transformer (tegra 3) they had the work around of something to do with wheelie
RuedasLocas said:
And how can I extract that?
You tried ADB? Maybe (if it works of course) pushing those unsecure img to unlock the EUR-XXX can bring it to life somehow...
I'm really out of ideas.
I tried APX with several drivers but the only thing I got was a bluescreen and a computer crash... device remains unknown
Click to expand...
Click to collapse
from what ive read when you fully unlock your bootloader like yours its possible that theyve blocked nvflash, mine was done with the chinese kdz and i had it saying unlocked in fastboot getvar all but it wasnt saying unlock in S/W or within android its self
i think skydev managed to extract the bct ect from the bootloader so il ask him if he still has them or if not then how to extract them
ive managed to get the bootloader.bin. i think i should able to progress when i have the others, adb doesnt also work mate, as the bootloader is at the very beguinning of all processes except nvflash
could you look and see what your odm files say, they are in sys/firmware/fuse/ i think, thankyou
another thing that il look into is someone mentioned about enabling jtag or write access by bridging two points inside the phone, this would obviously be the last thing when all else fails i just need to look in the lg service pdf for the schematics
friartuckme said:
could you look and see what your odm files say, they are in sys/firmware/fuse/ i think, thankyou
another thing that il look into is someone mentioned about enabling jtag or write access by bridging two points inside the phone, this would obviously be the last thing when all else fails i just need to look in the lg service pdf for the schematics
Click to expand...
Click to collapse
I made a copy of my "fuse" folder, forget about "secure_boot_key" cause is always "empty"...
http://www.4shared.com/rar/Y5AU8ZGl/fuse.html
I think that Nvidia have some specific android toolkits but to download them, you need to register, etc... I gave up in the midle of all that but, you can try it.
RuedasLocas said:
I made a copy of my "fuse" folder, forget about "secure_boot_key" cause is always "empty"...
http://www.4shared.com/rar/Y5AU8ZGl/fuse.html
I think that Nvidia have some specific android toolkits but to download them, you need to register, etc... I gave up in the midle of all that but, you can try it.
Click to expand...
Click to collapse
thankyou mate, as i said from when i first come to the lg 4x part of xda forums, your a good bloke, always helping people as much possible
after some more thinking,im struggling to understand why if the bootloader was unlocked could we not use unsecured boot and dexters cwm on the chinese kdz, and why was it saying unlocked in fastboot getvar all but saying locking in android and no unlocked text in S/W mode
what else apart from the bootloader can give the error of boot image signature error, and if the bootloader wasnt unlocked would it be possible to physically delete it, or could it have told whatever was saying it was unlocked that its erased while its actually not been but all link to it erased
i mananged to find my sys folder which i copied to my pc and noticed a difference in our odm_reserved files, which i think is to do with bootloaders
yours is
0x00000000000000000000000000000000000000000000000000000040000000c0
while my odm_reserved was
0x0000000000000000000000000000000000000000000000000000008000000000
not sure exactly what that means but strange
------------ does anyone known of what the load address and entry address is about,
bct file: flash.bct
booloader file: bootloader.bin
load addr 0x300d8106
entry addr 0x300d8106
device id: 0x7130
uid: 0x015d25648c57f00e
RCM version: 0.4
downloading miniloader to target...
Error downloading miniloader
ive just guessed a number for both addresses and obvously wrong
RuedasLocas said:
I made a copy of my "fuse" folder, forget about "secure_boot_key" cause is always "empty"...
http://www.4shared.com/rar/Y5AU8ZGl/fuse.html
I think that Nvidia have some specific android toolkits but to download them, you need to register, etc... I gave up in the midle of all that but, you can try it.
Click to expand...
Click to collapse
yeah mate im a member of the tegra development and have the tool kit. too be honest i havent found much of any use but that could be because ive an untrained eye
friartuckme said:
yeah mate im a member of the tegra development and have the tool kit. too be honest i havent found much of any use but that could be because ive an untrained eye
Click to expand...
Click to collapse
Probably will be enough the correct driver for APX mode on v20a, than with nvflash try to rollback whatever you made.
Sent from my LG-P880 using xda app-developers app
Related
Hi guys, I am having an issue i cant seem to resolve on my razr i. apologies if this has already been covered in another thread (or 10, which is usually the way with these things because nobody reads the other threads) I have been through a load of other threads but cannot seem to resolve my issue so i started my own.
Right, I have switched from iphone to razr and am not stupid when it comes to jailbreaking etc so thought rooting the razr wouldnt be a problem. when trying to root it it failed and i am stuck at the fastboot menu, however, everything on the menu is disabled so i cant use it. i get the usual message:
fastboot reason: flash failure
fastboot max download size: 100mb
usb connected
if i try to use anything on the menu i get the following message:
fastboot menu disabled.
my phone is not unlocked and not rooted. i have barely done anything to it other than install a couple of free apps. i am unable to progress past this screen. the phone is GB and is on 4.0.4
any help you guys can give would be greatly appreciated. again, apologies if this has already been covered, none of the solutions i found were able to resolve my issue. as i said, i had no problems jailbreaking my old iphone, i am a bit of a n00b when it comes to droids...
AW: [Q] razr i problems - fastboot menu
Are you able to run fastboot commands ? Cause in that case you might be able To unlock bootloader and reflash the software .
Sent from my XT890 using xda premium
xX_Alex_Xx said:
Are you able to run fastboot commands ? Cause in that case you might be able To unlock bootloader and reflash the software .
Sent from my XT890 using xda premium
Click to expand...
Click to collapse
I am not able to do anything. if i scroll to any of the options on the menu as soon as i hit the volume up key it just returns a message advising the fastboot menu is disabled.
**edit
ah commands not menu options. not sure how i go about doing that. i am 100% new to droid...
ged flanders said:
Hi guys, I am having an issue i cant seem to resolve on my razr i. apologies if this has already been covered in another thread (or 10, which is usually the way with these things because nobody reads the other threads) I have been through a load of other threads but cannot seem to resolve my issue so i started my own.
Right, I have switched from iphone to razr and am not stupid when it comes to jailbreaking etc so thought rooting the razr wouldnt be a problem. when trying to root it it failed and i am stuck at the fastboot menu, however, everything on the menu is disabled so i cant use it. i get the usual message:
fastboot reason: flash failure
fastboot max download size: 100mb
usb connected
if i try to use anything on the menu i get the following message:
fastboot menu disabled.
my phone is not unlocked and not rooted. i have barely done anything to it other than install a couple of free apps. i am unable to progress past this screen. the phone is GB and is on 4.0.4
any help you guys can give would be greatly appreciated. again, apologies if this has already been covered, none of the solutions i found were able to resolve my issue. as i said, i had no problems jailbreaking my old iphone, i am a bit of a n00b when it comes to droids...
Click to expand...
Click to collapse
Had the same problem, I used the recommendation in this thread, 5th post and it worked, but afterwards need to re-download apps from PlayStore:
http://forum.xda-developers.com/showthread.php?p=36612151
Follow the instructions exactly - you need the drivers and RSD lite on Windows PC, then connect the phone via usb cable that came with it; and you'll need a full unzip program (cost) so you can move the unzipped files into RSD lite. Get the right flash file though - there's a list in the linked post if you don't want GB retail which I used. Important: this only works for ICS 4.0.4 and don't try to downgrade to an earlier version than what's currently on your phone e.g. v.39 to v.31, for example.
Good luck.
AW: [Q] razr i problems - fastboot menu
If the solution from mervluk does not work (It didn't work for me either) , you should try if you are able to use the fast boot commands .
To do that simply connect your phone to the PC. Then download fast boot , if you do not already have that. It is in the .zip from the RAZR I root thread.
The go to the downloaded folder. There hold shift and perform a right mouse click. Then choose" start a command prompt here "or something similar (don't know how the option is called in English).
Then type in
fastboot reboot
When the phone reboots you might be able to unlock your phone and flash the software.
BUT BE AWARE! YOU WILL LOSE YOUR WARRANTY!!
So you better try the other solution first. This should be your last option.
If you don't know how to unlock the bootloader look in the RAZR I forum or pn me .
Alex
Sent from my XT890 using xda premium
mervluk said:
Had the same problem, I used the recommendation in this thread, 5th post and it worked, but afterwards need to re-download apps from PlayStore:
http://forum.xda-developers.com/showthread.php?p=36612151
Follow the instructions exactly - you need the drivers and RSD lite on Windows PC, then connect the phone via usb cable that came with it; and you'll need a full unzip program (cost) so you can move the unzipped files into RSD lite. Get the right flash file though - there's a list in the linked post if you don't want GB retail which I used. Important: this only works for ICS 4.0.4 and don't try to downgrade to an earlier version than what's currently on your phone e.g. v.39 to v.31, for example.
Good luck.
Click to expand...
Click to collapse
thanks buddy. i will give this a whirl and let you know how i get on. fingers crossed!
mervluk - your advice worked a treat. i got it working again. thanks !
now i am working again, what cool tricks do people advise. is it worth rooting it ? what can i do once it is rooted? am i able to network unlock it myself ?
ged flanders said:
mervluk - your advice worked a treat. i got it working again. thanks !
now i am working again, what cool tricks do people advise. is it worth rooting it ? what can i do once it is rooted? am i able to network unlock it myself ?
Click to expand...
Click to collapse
Glad about that. This phone can be a bit of a so-and-so. ics is being updated ota to Jelly Bean 4.1.2, which I've avoided so far to keep fm (although not activated on the supplied software). I did succeed with unlocking the bootloader (loose warranty - important) following the whole complicated procedure on Moto's website - but couldn't myself use the shortcuts on here. (Then had to set up again and re-download everything from the PlayStore). It required the Moto-supplied key. I then rooted, though I think the JB ota download unroots again? You can't use RSD lite with JB.
With JB the procedures are different, and a modified JB European (not for use with GB) firmware is now available on another thread which is impressing some posters. But I think just be a bit cautious as there does not appear to be any fix for the "service code corrupt" bootloader error yet. Looks like the options are very restricted whilst no-one understand the interaction between Google Android and the intel atom chipset.
I have a network unlock key from one of the commercial suppliers (cellunlocker.net), but haven't needed to try and use it yet!
My phone has no network and it says no sim card. After further investigation it appears that this is because the IMEI number has just gone, it doesnt exist on the phone. It is standard I have never changed software so have no idea how this could happen. Tried factory reset but nothing works. Any ideas greatly appreciated.
Re flash stock firmware and it should come back
Sent from my Nexus 5 using Tapatalk
Flash it to stock.
Root it
Install es explorer or any root explorer
Install hex editor
In es explorer go to efs folder in root
Open nv_data.bin in hex editor
Goto position 00188020 and check. .
Sent from my GT-I9500 using XDA Premium HD app
amit.talukdar said:
Flash it to stock.
Root it
Install es explorer or any root explorer
Install hex editor
In es explorer go to efs folder in root
Open nv_data.bin in hex editor
Goto position 00188020 and check. .
Sent from my GT-I9500 using XDA Premium HD app
Click to expand...
Click to collapse
This is still not a Samsung forum.
Sent from my OmniROM-powered LG Optimus 4X HD
Try to pull dev/block/platform/sdhci-tegra.3/by-name/NVA
Open with text editor.
Check if imei is stored.
This partition is recreated on flashing dz/kdz. I am not sure if IMEI is read from here. If you give email i will send you my NVA partition to compare. Don't post it or people will see your IMEI
Sent from my LG-P880 using xda app-developers app
Hi...I have similar problem ...my LG-P880 dont show the IMEI and factory reset is also not working...as per above I have checked in NVA folder it cotains proper IMEI number...so any idea how to fix the situation...? Thanks in advnace...
jigneshandroid said:
Hi...I have similar problem ...my LG-P880 dont show the IMEI and factory reset is also not working...as per above I have checked in NVA folder it cotains proper IMEI number...so any idea how to fix the situation...? Thanks in advnace...
Click to expand...
Click to collapse
Try Flashing using either by KDZ or LG Flash tool it might help you,
Try below link for procedure of LG Flash Tool
http://forum.xda-developers.com/showthread.php?t=2179126
KDZ Method
http://forum.xda-developers.com/showthread.php?t=2069723
Read the steps and understand it properly,
Hit thanks button below,if this help you out
Good Luck:good:
Salman Al-Badgail said:
Try Flashing using either by KDZ or LG Flash tool it might help you,
Try below link for procedure of LG Flash Tool
http://forum.xda-developers.com/showthread.php?t=2179126
KDZ Method
http://forum.xda-developers.com/showthread.php?t=2069723
Read the steps and understand it properly,
Hit thanks button below,if this help you out
Good Luck:good:
Click to expand...
Click to collapse
Thanks for your guidance...I have tried both option but it get stuck in middle somewhere and not able to flash the kdz file.
So at this moment LG Mobile support tools not able to cross 10% in firmware update process and stops due to some error.
With KDZ update tools, same situation....and device can connect to adb terminal no other recovery mode options.
So using adb terminal is there any chances to do some fix ?
I think I have currupted my boot loader during installation of third party recovery software without doing boot loader unlock option.
Please guide or suggest any other try.....
Thanks
jigneshandroid said:
Thanks for your guidance...I have tried both option but it get stuck in middle somewhere and not able to flash the kdz file.
So at this moment LG Mobile support tools not able to cross 10% in firmware update process and stops due to some error.
With KDZ update tools, same situation....and device can connect to adb terminal no other recovery mode options.
So using adb terminal is there any chances to do some fix ?
I think I have currupted my boot loader during installation of third party recovery software without doing boot loader unlock option.
Please guide or suggest any other try.....
Thanks
Click to expand...
Click to collapse
How you get into this problem?
Give me your BL - status, Secondly try changing PC. Also let me know what ROM you were using before getting into this problem (Stock/Custom)
Thirdy Party softwares (recovery) like....?
If you just give us info, someone might help you properly. I am just a Junior Member here, helping you out the info i had.
[Edited : Sorry for my English, I am Arabic]
Salman Al-Badgail said:
How you get into this problem?
Give me your BL - status, Secondly try changing PC. Also let me know what ROM you were using before getting into this problem (Stock/Custom)
Thirdy Party softwares (recovery) like....?
If you just give us info, someone might help you properly. I am just a Junior Member here, helping you out the info i had.
[Edited : Sorry for my English, I am Arabic]
Click to expand...
Click to collapse
It was happened like......the phone was working ok with latest official updates V20A and suddenly lost the IMEI number so Mobile network also. After some try finally I have done factory reset..but it was not working as expected...some time it has shown IMEI but lost also...tried many time factory reset but not worked...so tried with LG Mobile repair under upgrade and recovery option but it was failing at 10 % everytime. So thought lets intall new ROM so decided to install cyanogonmod so for preparation rooted phone and installed CWM recovery ....as doing all this first time so may be forgot to unlock the bootloader so after installation of CWM recovery phone has not booted and also not going to recovery menu. After that under upgrade mode tried to burn KDZ file using LG mobile support tool but that also not working.
So now the situation is, the can only go in to firmware update mode and some time getting connected to adb terminal.
So now is there any change of BL repair through adb terminal or the only option remain is visit LG support....?
Please guide....
Thanks,
jigneshandroid said:
It was happened like......the phone was working ok with latest official updates V20A and suddenly lost the IMEI number so Mobile network also. After some try finally I have done factory reset..but it was not working as expected...some time it has shown IMEI but lost also...tried many time factory reset but not worked...so tried with LG Mobile repair under upgrade and recovery option but it was failing at 10 % everytime. So thought lets intall new ROM so decided to install cyanogonmod so for preparation rooted phone and installed CWM recovery ....as doing all this first time so may be forgot to unlock the bootloader so after installation of CWM recovery phone has not booted and also not going to recovery menu. After that under upgrade mode tried to burn KDZ file using LG mobile support tool but that also not working.
So now the situation is, the can only go in to firmware update mode and some time getting connected to adb terminal.
So now is there any change of BL repair through adb terminal or the only option remain is visit LG support....?
Please guide....
Thanks,
Click to expand...
Click to collapse
Did you check your BL status for now?
3845#*880#
Salman Al-Badgail said:
Did you check your BL status for now?
3845#*880#
Click to expand...
Click to collapse
At present phone is not booting so not able run any short cut commands....but before crash it was showing status locked...
I will try as per your message ...will update the results...
Thanks
jigneshandroid said:
At present phone is not booting so not able run any short cut commands....but before crash it was showing status locked...
I will try as per your message ...will update the results...
Thanks
Click to expand...
Click to collapse
Great, will be waiting for your answer
Salman Al-Badgail said:
Great, will be waiting for your answer
Click to expand...
Click to collapse
I am trying with the links you have provided to flash the ROM, but before I start it...getting problem to keep the device connected to USB port...in device manager on connection it shows connected under Ports but in few seconds it gets disconnected (like timeout)..so exploring how can I keep it connected so that can try the tools once more.
jigneshandroid said:
I am trying with the links you have provided to flash the ROM, but before I start it...getting problem to keep the device connected to USB port...in device manager on connection it shows connected under Ports but in few seconds it gets disconnected (like timeout)..so exploring how can I keep it connected so that can try the tools once more.
Click to expand...
Click to collapse
Did you downloaded the files??
Install Drivers and follow the steps properly,
this should work for you to keep connected,
One more thing run drivers and flashtool as administrator, I already PM you.
Still having problems, please let me know.
If your phone is still not booting, I am afraid that you bricked it.
Good Luck
Salman Al-Badgail said:
Did you downloaded the files??
Install Drivers and follow the steps properly,
this should work for you to keep connected,
One more thing run drivers and flashtool as administrator, I already PM you.
Still having problems, please let me know.
If your phone is still not booting, I am afraid that you bricked it.
Good Luck
Click to expand...
Click to collapse
I am able connect my device to LGFlashTool on com Port1 but download fails with below log on port1
StartDownload()
Saved result to XML file.
Failure : 207
FAIL
and same thing repeating as software retries the same.
Can somebody guide what is this situation ?
Thanks and best regards,
Jignesh
jigneshandroid said:
I am able connect my device to LGFlashTool on com Port1 but download fails with below log on port1
StartDownload()
Saved result to XML file.
Failure : 207
FAIL
and same thing repeating as software retries the same.
Can somebody guide what is this situation ?
Thanks and best regards,
Jignesh
Click to expand...
Click to collapse
Post a screenshot so that anyone could help you.
jigneshandroid said:
I am able connect my device to LGFlashTool on com Port1 but download fails with below log on port1
StartDownload()
Saved result to XML file.
Failure : 207
FAIL
and same thing repeating as software retries the same.
Can somebody guide what is this situation ?
Thanks and best regards,
Jignesh
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2179126
Try using post #7 by RuedasLocas
and read it untill you get it.
:good:
Salman Al-Badgail said:
http://forum.xda-developers.com/showthread.php?t=2179126
Try using post #7 by RuedasLocas
and read it untill you get it.
:good:
Click to expand...
Click to collapse
OK..thanks I will check this post whether somebody has reported similar problem...do you mean page 7 is it ?
:good:
jigneshandroid said:
OK..thanks I will check this post whether somebody has reported similar problem...do you mean page 7 is it ?
:good:
Click to expand...
Click to collapse
Page 1 -> post #7 by RuedasLocas
My phone connects fine with adb. I tooted with towelroot, i have the D415 (see screenshot) i have run the commands on a pc several time with no errors. I tried it with my terminal emulator severaIm times and it says "decixe not found) HAHHA its just funny to me. I want to unlock this bootloader i even tried a factory cable (for kindle and only once) no dice. I get download mode and thats it. I know I must be doing somethimg wrong but damned if i can figure what. Pc is windows 764 bit. I like to have a custom rexovery and i have heard i can put onw like this (locked) but i did that to another device and to make it short it sits in a drawer being brand new and broken. Apparently those instructioms are correct because there are many success stories. I followed the directions like this is my last phone for a whi
PHP:
le. Can someone help me out please? Thank you
Holy....... 64bit! Im not futureman!!!!
Do you need to unlock the bootloader on d415? I taught you could flash a custom recovery without unlocking... (I don't own one!)
I ave twrp on it. So far i havent been able to do anything but a nandroid and restore with it. I am now at a pc so i can dl from devhost. We shall see, (i doubt it,)
whodisname said:
I ave twrp on it. So far i havent been able to do anything but a nandroid and restore with it. I am now at a pc so i can dl from devhost. We shall see, (i doubt it,)
Click to expand...
Click to collapse
The bootloader on the LG-D415 is unlocked out of the box.
Wow, and all these instructions!! I figured after i put twrp on it it was cool but it didnt flash the rom, omly had one cuz dev host doesnt dl on cell phones so well,
whodisname said:
My phone connects fine with adb. I tooted with towelroot, i have the D415 (see screenshot) i have run the commands on a pc several time with no errors. I tried it with my terminal emulator severaIm times and it says "decixe not found) HAHHA its just funny to me. I want to unlock this bootloader i even tried a factory cable (for kindle and only once) no dice. I get download mode and thats it. I know I must be doing somethimg wrong but damned if i can figure what. Pc is windows 764 bit. I like to have a custom rexovery and i have heard i can put onw like this (locked) but i did that to another device and to make it short it sits in a drawer being brand new and broken. Apparently those instructioms are correct because there are many success stories. I followed the directions like this is my last phone for a while. Can someone help me out please? Thank you
Click to expand...
Click to collapse
For starters, you need the fastboot executable for Windows to unlock the device, not ADB. The minimal ADB version, also applies to fastboot, is 1.0.31. Secondly, you must enable fastboot mode on the device beforehand. Thirdly, unless LG has changed things in the last month or so, the bootloader on the LG-D415 is unlocked.
To enable fastboot mode, see http://forum.xda-developers.com/lg-l90/general/guide-fastboot-l90-d415-t2827825
To unlock the bootloader, see http://forum.xda-developers.com/lg-l90/general/guide-unlock-bootloader-t-mobile-l90-t2836457. Shouldn't be necessary tho . Won't hurt anything to go thru the process however.
Thank you, i have fastboot and adb (fixed a bricked kindle last week!!) I wasnt sure about the bootloader and iwasnt gunna be without a recovery like i was with my lg lucud!!!
And excuse my unintelligible post above. New size screen?
Or as bricked as these Qualcomm devices CAN be?
Hey all,
The TL;DR is basically where the list starts
I was running Blu's TWRP v45, the latest PureFusion, Blu's latest Custom kernel, had OB15 firmware underneath. I had been SO USED to simply downloading the newest firmware from kamilmirza's AFH page and just flashing it + it being totally fine that I did it without thinking for OB16. I wasn't too worried because about a week ago I had flashed the unofficial Oreo Lineage and it worked just fine! Plus, I just assumed if it died I could just restore a backup or re-flash the older OB. But as soon as I flashed the new firmware/modem by itself this time on an otherwise perfectly running device, I only saw the OnePlus splash screen. No booting, no access to recovery, no NOTHIN.
I tried flashing the beta TWRP version afterward via fastboot but no dice. Also tried temporary booting via fastboot to it, flashing Blu's again, booting to that. Everything the same result. Splash screen & nothing more. I then went to the extent of trying to format all the partitions and flash a boot.img or do a "-w update" or "flashall" command via fastboot. Because everything out in the universe is a recovery-flashable-zip, it seems like there's no way I can flash the necessary OTA stuff to bring it back to life!
My only remaining idea is getting this damn unbrick tool to work (duhh). I can see the Qualcomm HS-USB QDLoader 9008 in device manager after doing the Vol Up (only) and plugging the cable in. BUT the MSMDownloadTool just cannot see the device. Not in bootloader, not in the weird Vol-Up/cable state. [This is with Qualcomm drivers QUD.WIN.1.1 Installer-10037.3 Setup.exe, the official OnePlus drivers, ADB & Fastboot installed.]
Sorry for long explanation. In the end, what I'm left with is:
Blank formatted partitions (I hope... I'm not even positive they wound up formatted from the fastboot commands)
Fastboot is detected, but no ADB devices are found
Can get to bootloader, but nothing else
No recovery access - Flashing beta akhilnarang Oreo recovery does nothing. Flashing stock recovery does nothing. Flashing Blu_Spark recovery does nothing. (The fastboot commands succeed though each time somehow)
So far the only suggestion I've received is trying the MSMDownloadTool/unbrick process on another computer.
Does anyone have ANY ideas? From my experience, it seems like what might help me would be if a folder with the specific partition images existed for the OTAs, like how Google offers. (boot.img, recovery.img, user-data.img, system and so on). Am I wrong in thinking that? OnePlus has told me this simply does not exist and cannot give me anything like that (don't know why, when they already offer all the OTA flashables...)
PS - OnePlus support just absolutely refuses to even let me communicate to a "level 2" representative to ask a couple of the more technical questions about it. I can't understand why. They are insisting I start an RMA and send it for repair. They even initially scheduled a time for me to talk to higher level rep and then thought up a reason to cancel it via email an hour or so later...
Edit: Just in case the thread gets large and people don't read further posts, this is using:
Windows 10 Pro 64-bit
Test mode for the driver signing is enabled. Have the watermark bottom right of desktop
It's with the stock DASH cable
Tried multiple ports
Unfortunately it just doesn't show up in MSM at all, even with hitting 'enumerate' button multiple times
Tried starting the tool BEFORE the device is plugged in, as well as after
This is what Device Manager shows (attached) but just nothing in MSM all the way up & down
HOW IT GOT SOLVED:
At the end of the day, I had to fight and convince OnePlus support to grant me a remote session with Level 2 Support.
(Attached final image) These two password protected RAR files had almost identical tools as the Unbrick tutorial on XDA.
The major difference was that MSMDownloadTool was version 3.0.8 ***does anyone have this version??*** I can't get into these RARs. The 3.0 tool circulating did not work for me. We might need the newer version as time goes on?? Otherwise, the process was identical.
Unfortunately, the image they used was for 7.1.1. I had to unlock the bootloader and after doing that and getting OB15 & the RR build I wanted, etc, I then realized my phone was force-encrypted as well.
The only toolkit that worked for force decrypting once everything else worked was:
OnePlus_3_3T_5_64bit_TOOLKIT_by_Neisor
Finally, something like 3 clean flashes later, we Gucci.
Thanks for the attempted help to those that did! Hopefully this can help someone else.
Which Windows do you have? Have you tried MSMtool in safe mode? Or disabling Driver Signature Verification (any Windows after XP). I have got my phone so messed up that it was showing many lines with red "failed" text nearly on everything. No OS, no recovery, no boot, I think even modem was failed. This screen but I had way more fails https://forums.oneplus.net/attachments/win_20160928_21_31_49_pro-jpg.459494/
As long as you can turn your phone off and on, it's doable. But you need to do that USB plugging + volume up thing while phone is totally off (you can hear Windows making bling when you connect it while pressing volume up, but phone itself stays screen off). And there shouldn't be anything on the screen before/while MSMtool do its job.
You can try different USB ports too.
Eremitus said:
Which Windows do you have? Have you tried MSMtool in safe mode? Or disabling Driver Signature Verification (any Windows after XP). I have got my phone so messed up that it was showing many lines with red "failed" text nearly on everything. No OS, no recovery, no boot, I think even modem was failed. This screen but I had way more fails https://forums.oneplus.net/attachments/win_20160928_21_31_49_pro-jpg.459494/
Click to expand...
Click to collapse
Hahaha yes...... That's why I made this post though! It SEEMS like it should be possible to recover from this since fastboot commands + bootloader work! It SEEMED like it would be easy to recover from if anything went wrong... But, here I am.
Oh yeah forgot to mention ~
Windows 10 Pro 64-bit
Test mode for the driver signing is enabled. That part of the process went totally fine with BIOS and installing stuff, etc.
Also, shot in the dark but might @Funk Wizard have any ideas? Sorry to call out for this
Hopefully someone knows better how to solve this. For me the MSMtool part is always the hardest part too, usually it finds the phone, but throws some strange "Sahara communication failed" error. I noticed that even different USB cable can be a problem, but since your Windows finds "Qualcomm HS-USB QDLoader 9008" I guess that's not the case. Does it say something after that "Qualcomm 9008" -thing? For me it shows (COM3 or COM4 depending on which port it's in).
btw, I messed up my phone in nearly similar case, flashing wrong firmware when using leaked H2OS ROM.
Eremitus said:
Hopefully someone knows better how to solve this. For me the MSMtool part is always the hardest part too, usually it finds the phone, but throws some strange "Sahara communication failed" error. I noticed that even different USB cable can be a problem, but since your Windows finds "Qualcomm HS-USB QDLoader 9008" I guess that's not the case. Does it say something after that "Qualcomm 9008" -thing? For me it shows (COM3 or COM4 depending on which port it's in).
Click to expand...
Click to collapse
Yeah sorry again for not being more clear lol
It's with the stock DASH cable
Tried multiple ports (but no USB 2 ports hmm)
Unfortunately it just doesn't show up in MSM at all, even with hitting 'enumerate' button multiple times.
Also tried starting the tool BEFORE device plugged in as well as after
This is what Device Manager shows (attached) but just nothing in MSM all the way up & down
If I find a solution I'll definitely put it in OP for others
purplepenguin said:
Yeah sorry again for not being more clear lol
It's with the stock DASH cable
Tried multiple ports (but no USB 2 ports hmm)
Unfortunately it just doesn't show up in MSM at all, even with hitting 'enumerate' button multiple times.
Also tried starting the tool BEFORE device plugged in as well as after
This is what Device Manager shows (attached) but just nothing in MSM all the way up & down
If I find a solution I'll definitely put it in OP for others
Click to expand...
Click to collapse
Hmm, ok.
Stock dash cable works, so that part is ok. Also usb3.0 ports should work too, atleast for me. So everything else seems to be ok except the MSMtool itself
Try different cable, bin there done that!!
purplepenguin said:
Yeah sorry again for not being more clear lol
It's with the stock DASH cable
Tried multiple ports (but no USB 2 ports hmm)
Unfortunately it just doesn't show up in MSM at all, even with hitting 'enumerate' button multiple times.
Also tried starting the tool BEFORE device plugged in as well as after
This is what Device Manager shows (attached) but just nothing in MSM all the way up & down
If I find a solution I'll definitely put it in OP for others
Click to expand...
Click to collapse
I hope you find a solution, since my experience sounds similar to yours Ill share it and maybe you can find something to help out.
I was exactly where you are for about 3 hours last night.
Boot would always get stuck at the splash screen. Could boot into Fastboot, tried using the Skipsoft tool to fastboot flash a stock image but it kept failing.
As far as the Unbrick Tutorial goes, I know the first thing I kept messing up was thinking I needed to press the power button while holding the volume up and connecting to the PC
Also when I tried to manually update the driver on "Qualcomm 9088" it said it was already up to date.
Then I just ran the MSMTool it flashed 6.0.1 back on my phone and I was back in business.
Im sure this is the guide you followed: Here
I found another on the oneplus forums that is essentially the same but goes into a little more detail in the steps: Here
Since I was back completely Stock including Recovery I went ahead and sideloaded OB16 to get the firmware and modem then went about rooting, unencrypting etc...
Lost a few days worth of files but I'm back running LunuxOS Oreo right now.
Good luck I know how you feel. :good:
I've got it revived! I'll update OP. Sadly, it required OnePlus's intervention.
Hi. Trying to do brute force to get the passowrd here, don't you know how many characters that was? It will take days in my machine to search from 3 to 9 characters...
I think it is impossible to you to know, but if you know if they used only letters or something like that, it would be very useful
guilhermeferrari said:
Hi. Trying to do brute force to get the passowrd here, don't you know how many characters that was? It will take days in my machine to search from 3 to 9 characters...
I think it is impossible to you to know, but if you know if they used only letters or something like that, it would be very useful
Click to expand...
Click to collapse
Sorry man. The OnePlus guy was ready an hour early before our appointment time. So I didn't have time to set up screen recording or anything
if I had to narrow it down more itd only be like 4-9 chars lol I know that's not much help... Definitely let me know if you get it open though please! It would probably help a lot of us!
purplepenguin said:
Sorry man. The OnePlus guy was ready an hour early before our appointment time. So I didn't have time to set up screen recording or anything
if I had to narrow it down more itd only be like 4-9 chars lol I know that's not much help... Definitely let me know if you get it open though please! It would probably help a lot of us!
Click to expand...
Click to collapse
Well, I know the password. It's 10 character long. 7+3(7english small latter with 3 Numbers).
L2 Driver password is very very very very very loooooooong. can't even count accurately.
namefaisal said:
Well, I know the password. It's 10 character long. 7+3(7english small latter with 3 Numbers).
L2 Driver password is very very very very very loooooooong. can't even count accurately.
Click to expand...
Click to collapse
Jeez so wait you got it open or not?? Confused lol
Got the newer download tool ??
Yeah, I got it open
purplepenguin said:
Jeez so wait you got it open or not?? Confused lol
Got the newer download tool ??
Click to expand...
Click to collapse
Yeah it's the new 3.08 msmdownloadtool. OnePlus3T_28_A.57_171012.zip
I know the password and I won't share that but I will upload an UNLOCKED zip on google drive tonight. L2 Drivers too.
New Files without Password
namefaisal said:
Yeah it's the new 3.08 msmdownloadtool. OnePlus3T_28_A.57_171012.zip
I know the password and I won't share that but I will upload an UNLOCKED zip on google drive tonight. L2 Drivers too.
Click to expand...
Click to collapse
Latest 3.08 msmdownloadtool re-archived without password from OnePlus3T_28_A.57_171012.zip
https://drive.google.com/file/d/1kp2SBmhAByydol97o0yVlurVue9Ow8Aq/view?usp=sharing
And the L2+ driver.zip re-archived without password
https://drive.google.com/file/d/1JL_sRg86CczUeZ2cfw8GY6rxc43myif8/view?usp=sharing
@Sam Nakamura
namefaisal said:
Latest 3.08 msmdownloadtool re-archived without password from OnePlus3T_28_A.57_171012.zip
https://drive.google.com/file/d/1kp2SBmhAByydol97o0yVlurVue9Ow8Aq/view?usp=sharing
And the L2+ driver.zip re-archived without password
https://drive.google.com/file/d/1JL_sRg86CczUeZ2cfw8GY6rxc43myif8/view?usp=sharing
Click to expand...
Click to collapse
This totally worked for me. Yes it put me back on 7.1.1 but I have been having issues trying to flash Oxygen ROMS and getting them to take. Phone is back to bone stock which I wanted for now and is working great. Thank you for sharing,
cdorrell12000 said:
This totally worked for me. Yes it put me back on 7.1.1 but I have been having issues trying to flash Oxygen ROMS and getting them to take. Phone is back to bone stock which I wanted for now and is working great. Thank you for sharing,
Click to expand...
Click to collapse
You are most welcome.
Sadly everyone gets unbricked with these files but My device didn't. I have to send the device to the service center now. It seems my case is a hardware issue. Tough luck
namefaisal said:
Latest 3.08 msmdownloadtool re-archived without password from OnePlus3T_28_A.57_171012.zip
https://drive.google.com/file/d/1kp2SBmhAByydol97o0yVlurVue9Ow8Aq/view?usp=sharing
And the L2+ driver.zip re-archived without password
https://drive.google.com/file/d/1JL_sRg86CczUeZ2cfw8GY6rxc43myif8/view?usp=sharing
Click to expand...
Click to collapse
thanks a lot saved my day !!
purplepenguin said:
@Sam Nakamura
Click to expand...
Click to collapse
Sorry, I just saw your mentioning somehow I missed it, happy you got your phone back already, unfortunately not independent for big OP, did you guys already share this new 3.08 MSM-download-tool to the well established threads or did you I missed this too? This information and according files should be shared with the community and easy to find for those poor souls who unintentionally killed their beloved device...
---------
Edit: further sharing isn't necessarily needed, you did already a pretty good job by naming the thread and describing the situation thoroughly, only suggestion could be to link the updated MSM-download-tool download to the first post with some hint, just an idea though...
Cheers
Sent from my OnePlus 3T using XDA Labs
How do I write IMEI along with baseband version back to my phone? I really don't want to risk bricking it again, that's enough stress for me in the past two days
I heard that I can only flash IMEI 2 back to it, and if I want flashing IMEI 1 as well I'd need to install a custom rom on the phone. So if that's a solution I'd love if someone could help me with it. MIUI 13 is slow and laggy af (which is the reason I bricked the phone in the first place, to install a better ROM).
But here's something, when I flash the phone's firmware through fastboot, issues start to rise (as per my experience with it so far), but through SP Flash Tool, it's alright. So I'd love to know if installing custom ROMs using the tool would be alright, if not then if recovery is required or if fastboot is fit for the job. If that's an issue I'd love if someone could give me advice when it comes to it.
Old post 1: (not my current situation)
"Long story short, I bricked the phone and after months, I've finally been able to repair it (downgraded from MIUI 13 to MIUI 11), but I lost my IMEI. I have the phone's two IMEI numbers, but I could not find any tool to help me write it to the phone. Either that, or I don't know whether the phone should be turned on or off, or if there's any special mode that's required for that matter.
Help would really be appreciated."
Old post 2:
"It happened after manually installing engineering ROM on it, now I can only doubt it's BROM mode that's working and nothing else, but I'm not sure. SP Flash Tool doesn't want to work with the phone since I want to flash the stock rom back. I really need help please."
YLTN said:
Long story short, I bricked the phone and after months, I've finally been able to repair it (downgraded from MIUI 13 to MIUI 11), but I lost my IMEI. I have the phone's two IMEI numbers, but I could not find any tool to help me write it to the phone. Either that, or I don't know whether the phone should be turned on or off, or if there's any special mode that's required for that matter.
Help would really be appreciated.
Click to expand...
Click to collapse
Install Engineering ROM and then write imei using available tools.
mvikrant97 said:
Install Engineering ROM and then write imei using available tools.
Click to expand...
Click to collapse
I fear that if I install the ROM, the phone might brick again
YLTN said:
I fear that if I install the ROM, the phone might brick again
Click to expand...
Click to collapse
Why?
mvikrant97 said:
Why?
Click to expand...
Click to collapse
The reason why my phone broke in the first place was due to flashing a misc.bin file after following a YouTube tutorial. It was part of a process to download twrp on the phone unofficially. Since then I started looking for ways to fix it until I finally found a post that had to do with fixing nvdata corruption (which was the error I had prior to fixing the phone) which helped.
So yeah, I don't think I can trust flashing ROMs on my phone as much as before, but I'll still try the engineering ROM thing.
mvikrant97 said:
Why?
Click to expand...
Click to collapse
So um...it bricked. This time worse than before. It doesn't turn on at all no matter how long I press the power button. It was after I manually flashed eng rom.
YLTN said:
So um...it bricked. This time worse than before. It doesn't turn on at all no matter how long I press the power button. It was after I manually flashed eng rom.
Click to expand...
Click to collapse
Does it shows up in device manager?
mvikrant97 said:
Does it shows up in device manager?
Click to expand...
Click to collapse
Yep, it doesn't show up as it's name or "Android", it shows up as MediaTek USB Port (COM3), that's why I doubted it to be in BROM mode.
YLTN said:
Yep, it doesn't show up as it's name or "Android", it shows up as MediaTek USB Port (COM3), that's why I doubted it to be in BROM mode.
Click to expand...
Click to collapse
By the way, after trying to connect to it using mtkclient, I got this error:
DeviceClass - [LIB]: ←[31mCouldn't get device configuration.←[0m
YLTN said:
By the way, after trying to connect to it using mtkclient, I got this error:
DeviceClass - [LIB]: ←[31mCouldn't get device configuration.←[0m
Click to expand...
Click to collapse
Hold on, it worked now for some reason when I disconnected the battery, but it keeps connecting and disconnecting so that's an issue.
I'll try to reconnect the battery and see.
YLTN said:
Hold on, it worked now for some reason when I disconnected the battery, but it keeps connecting and disconnecting so that's an issue.
I'll try to reconnect the battery and see.
Click to expand...
Click to collapse
Please install LIB USB drivers.
Visit this tutorial here on xda
mvikrant97 said:
Please install LIB USB drivers.
Visit this tutorial here on xda
Click to expand...
Click to collapse
Bro, thank you so much, the phone's unbricked now. I couldn't believe my eyes
But for now, is there any solution for the IMEI problem?
YLTN said:
Bro, thank you so much, the phone's unbricked now. I couldn't believe my eyes
But for now, is there any solution for the IMEI problem?
Click to expand...
Click to collapse
I always recommend a NV Backup before messing up with your own device, that's all I know.
Download the file attached here but remember you can fix only second IMEI using this method. Please don't try to fix both IMEI or NV Data will be corrupted again.
Video Tutorial to Follow Video Tutorial
mvikrant97 said:
I always recommend a NV Backup before messing up with your own device, that's all I know.
Download the file attached here but remember you can fix only second IMEI using this method. Please don't try to fix both IMEI or NV Data will be corrupted again.
Video Tutorial to Follow Video Tutorial
Click to expand...
Click to collapse
The guy in the video is using MIUI 12, I have MIUI 13. I don't know if that's an issue but someone in the comments said something about MIUI or so. I'm not a professional but many times when I see tutorials they're very specific with the MIUI version.
Also, I'm not sure how to back up nv data, do I use mtkclient or is it somewhere in the attachment you sent me?
And one more thing, my phone's baseband version is unknown, could that affect the process?
YLTN said:
The guy in the video is using MIUI 12, I have MIUI 13. I don't know if that's an issue but someone in the comments said something about MIUI or so. I'm not a professional but many times when I see tutorials they're very specific with the MIUI version.
Also, I'm not sure how to back up nv data, do I use mtkclient or is it somewhere in the attachment you sent me?
And one more thing, my phone's baseband version is unknown, could that affect the process?
Click to expand...
Click to collapse
You don't need the backup anymore and you can follow the tutorial in the video irrespective of the MIUI version you have.
I have also attached the files that are used in the video.
mvikrant97 said:
You don't need the backup anymore and you can follow the tutorial in the video irrespective of the MIUI version you have.
I have also attached the files that are used in the video.
Click to expand...
Click to collapse
Alright then, I'll follow the steps and tell you the results once I'm done.
mvikrant97 said:
You don't need the backup anymore and you can follow the tutorial in the video irrespective of the MIUI version you have.
I have also attached the files that are used in the video.
Click to expand...
Click to collapse
The phone keeps rebooting when connecting it to Maui META. Like it shows META MODE at the bottom of the screen but then it turns off. Now it's bootlooping. I guess I'll have to flash MIUI on it again. At least I still have access to fastboot and recovery.
Update: NV Data corrupted after flashing MIUI, but I got a solution that hopefully works.
Update 2: After flashing MIUI 11 (along with some other nvdata and nvram files, i think they're just empty), it works now and the error is gone. But as I said IMEI issue's still there. Maybe I would need engineering ROM for this one? Although it bricked my phone before.
Also, the phone started bootlooping before attempting the Maui META thing, so maybe it's either the manual formatting of partitions or the files I flashed on it.
YLTN said:
The phone keeps rebooting when connecting it to Maui META. Like it shows META MODE at the bottom of the screen but then it turns off. Now it's bootlooping. I guess I'll have to flash MIUI on it again. At least I still have access to fastboot and recovery.
Update: NV Data corrupted after flashing MIUI, but I got a solution that hopefully works.
Update 2: After flashing MIUI 11 (along with some other nvdata and nvram files, i think they're just empty), it works now and the error is gone. But as I said IMEI issue's still there. Maybe I would need engineering ROM for this one? Although it bricked my phone before.
Also, the phone started bootlooping before attempting the Maui META thing, so maybe it's either the manual formatting of partitions or the files I flashed on it.
Click to expand...
Click to collapse
Try flashing the ENG rom and try fixing your IMEI
mvikrant97 said:
Try flashing the ENG rom and try fixing your IMEI
Click to expand...
Click to collapse
So I ran into another issue. it tells me I need "exaid-verified.img" and that verified boot is enabled, which is not present in the ENG ROM folder.
mvikrant97 said:
Try flashing the ENG rom and try fixing your IMEI
Click to expand...
Click to collapse
Btw one more thing, I can update my phone right? Like, it won't break my phone? I'm good with MIUI 11 but I wonder if updating it would fix baseband version.