Related
Hi guys,
This is all about developing the Focus S, since we are on our own on this one I thought id start the ball moving but it would be great if others can help, my first target is to try and download as much of the device as possible
Can I promise anything at all? nope
Have I achieved anything yet? well id say 1 step above doing nothing at all, if you can call that progress then yes, there is progress
Is it even possible to do anything? i dunno
Could i brick my device? possibly, i honestly don't know
in short, this is me blindly wondering in the dark with absolutely no direction what so ever!
So what have i done, well, i managed to get the Focus S talking to Qualcomms diagnostic utility, QPST and RevSkills CDMA Workshop
I cant get QXDM to install on Win 8 x64 and im not sure we need that one anyway
it is possible to edit stuff on the phone at a very low level, NOT OS level, it should be possible to download the various images on the phone, but ive yet to have any luck with that, it keeps coming up with "Arm9 fatal error"
ive been able to download and backup various phone settings but this is still outside of the OS#
I can play about with the EFS but there are several folders that i cant get in to yet
So far,both the samsung download mode and the ARM9 (?) download mode IS visible and installes as a com port, but there is no response on that port, i can only get a response within windows when i enable USB diag mode....
i decided not to link to the various tools ive mentioned here, i dont know the legalities of it all so use google, they are all easy to find.
Samsung studio 3 drivers
http://downloadcenter.samsung.com/c...813082717640_Samsung_USB_Driver_Installer.exe
Install it with compability for windows vista.
Samsung Focus info (note that most of this doesn't work, its for the older focus but some does)
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Focus
Handy Diagnostic codes
*#7284# - USB Path control (select to change how your phone communicates with your computer)
*#197328640# - The Root Menu (seriously, don't get too cocky, you could bugger up your device)
Samsung USB Download mode
Turn off Device
hold the camera button and the Volume UP
Whilst holding those two push and hold the power button until it vibrates
Samsung Device Hard reset
Turn off Device
hold the camera button and the Volume Down
Whilst holding those two push and hold the power button until it vibrates
Follow on screen instructions
Enable Diagnostic mode and Connect to QPST or other GSM/CDMA software
Download and install the Samsung drivers above
open the diagnostic app and dial code *#7284#
Select Modem,USB Diag
Reboot
When you plug the phone in you should see a COM port install and appear in device manager
load QPST configuration
Click on the Ports Tab then Click add new port
Select your Phone com port
Click OK then select the phone from the list, hit enable
Click on start clients then you can play with a bunch of options
Please note that this is a serious piece of kit, its designed for low level editing, what I mean by that is that it couldn't care less about if it works or not after you finish playing, a couple of other software options to play with are CDMA tools and RevTools both have the potential to paperweight your phone!
NOTE: Zune will not connect and whilst connected to PC you may lose all GSM connectivity whilst connected as well.
Enable FTM (Factory Test Mode)
open Diagnostic app and dial code*#197328640#
select 6 (common)
Select 1 (FTM)
Select 1 (on)
Click return save (it doesn't always persist unless you do)
Hit Back until you back to the main menu then win key to Windows
REBOOT to enable
NOTE: You will lose ability to connect to GSM with this enabled, a reboot is required to enable it after its set and to deactivate it, ive not found a noticeable difference with this on
If im not wrong, WP uses arm v7.
Good luck with this, it would be nice to see a 7.8 ROM on this device before I go buy the ATIV.
tayfelix said:
If im not wrong, WP uses arm v7.
Click to expand...
Click to collapse
yes your right, but that's what it says, it reboots in to some sort of QC download mode, QPST is the waiting for it to talk to it which it doesn't do, it just sits there with this error message.
I have been able to backup the Important bits that make the phone work, and I have access to the EFS, I can change all sorts at a very low level but any time I try and download some of the various "partitions" it reboots to this special download mode. because we don't have any form of ROM I thought the first priority should be to see if we can make a backup of it, outside of MS encrypted zune backup I mean
the software is old so perhaps it doenst work with newer hardware, but then it does with android soooo.....
LudoGris said:
Good luck with this, it would be nice to see a 7.8 ROM on this device before I go buy the ATIV.
Click to expand...
Click to collapse
don't hold your breath, I still don't really know what im doing, consider this playing.....in a mine field
Hmmm. If this does work. Will it ever work on focus flash/ omnia w? Cuz it got the same spec except different screen sizes
tayfelix said:
Hmmm. If this does work. Will it ever work on focus flash/ omnia w? Cuz it got the same spec except different screen sizes
Click to expand...
Click to collapse
That depends what you mean by work, will the focus flash connect to various diagnostic tools? yes probably, will it be possible to download the ROM? maybe, beyond that I haven't got a clue
starting to run out of ideas, I think either the download mode via QPST is disabled or, and more likely, the driver isn't correct, when it enters the arm9 fatal error screen it is still using same driver, the same driver samsungs download mode uses, but both won't talk to QPST unless I enable diagnostic mode within windows phone OS, the prob with that is that it won't then allow access to the file systemSent from my fake Lumia 900 using XDA Windows Phone 7 App
It also have diagnostic tools .
tayfelix said:
It also have diagnostic tools .
Click to expand...
Click to collapse
be careful, you can bugger up your device!i will write a more detailed guide later
First things first, you will need to make sure you have the samsung diagnostic tool install
bring up the phone dialer and dial
##634#
you will now see a diagnostic app on your app list, run it and type in
*#7284#that will enable you to change the USB connection mode,select
Modem USB diag
OPTIONAL - Typing in the following code will bring up the diagnostic root menu
#197328640#you can find a full list Here Many of the codes on that list just run functions found in the root menu
Bare in mind that pissing around with some of the things in there will bring about a swift crappy end to your day!
plugging in your your phone at this point will install a Samsung COM driver
next download and install QPST on your computer, run the config part of that, it will ask you to select your phone, you will need to add a com port, it should then list your phone to connect to it
you can then edit the EFS, service/phone settings, download settings
you will need to know your SPC number, mine was already 0000000, there are ways of working out your number if leaving it all at zeros doesnt work.
use the service editor to read the phone settings, it will ask for your SPC, once loaded,you can save those settings to a file, very important ifyou screw something up
Cool, I will try it when I'm free. Hmm what's UR focus s BOOTLOADER, firmware version and diagnostic version ?
tayfelix said:
Cool, I will try it when I'm free. Hmm what's UR focus s BOOTLOADER, firmware version and diagnostic version ?
Click to expand...
Click to collapse
as reported in windows phone about screen, note that the Focus S and Omnia 7, has a firmware update that will stop any interop unlocking, i had it installed but it killed my battery life and my phone reception so i took it off, id suspect the bootldt vs will be different between devices, even though they were released at the same time
bootldr 6.5.16.0
firmware 2103.11.10.1 (not the Samsung update that breaks interop)
diagnostic 0923 (not the Samsung update that breaks interop)
Er it's focus, focus s , focus flash/omnia w and omnia 7 that are affected by the freakin update. This is my version from the about info
Firmware: 2424.12.04.1
Bootloader: 6.4.4.0
Diagnostic : 1109
Note : I cant interlop unlock my omnia as Samsung fixed the exploit in the new firmware version
How did u remove the firmware ?
tayfelix said:
Er it's focus, focus s , focus flash/omnia w and omnia 7 that are affected by the freakin update. This is my version from the about info
Firmware: 2424.12.04.1
Bootloader: 6.4.4.0
Diagnostic : 1109
Note : I cant interlop unlock my omnia as Samsung fixed the exploit in the new firmware version
How did u remove the firmware ?
Click to expand...
Click to collapse
I made a backup before I installed it
I think we can get an xap of my version of the diagnostic tools, but the firmware update also changes drivers an a few other things, those cant be changed, if we could send custom cabs to the device we are laughing, but we cant, to cab send requires the cab to be signed, and the device would need to have that certificate, which cant be put on whilst its all in use
:S don't think so as diagnostic tool is based on firmware I think.
tayfelix said:
:S don't think so as diagnostic tool is based on firmware I think.
Click to expand...
Click to collapse
try this, remove your existing diagnostic app and install this xap
How can u install a xap..
Is your device still unlocked? The Samsung update will stop you applying the unlock but if you had it already installed it will still work, if it is unlocked then use an cap deployed, my link to the wee guide details how to do it, if it's interop unlocked but you can't install an xap deplorer the use the xap deplorer included with the WP SDK
Sent from my Lumia 900 using XDA Windows Phone 7 App
it's ok. I will just wait for someone to be able to unlock the device as I already got the exploit for interlop unlock patched
tayfelix said:
it's ok. I will just wait for someone to be able to unlock the device as I already got the exploit for interlop unlock patched
Click to expand...
Click to collapse
well there isn't anyone working on unlocking it as far as I know, so if its going to happen then we need to do it ourselves.
Ive exhausted just about every avenue I can think of getting access to the device, ive been able to dump parts of the RAM but still not the ROM,
EFS is writable but I cant get in to the secure folders. The only way I can think of for getting the ROM is to get it working in one of the two download modes, both will not talk to anything tho, perhaps if I had the commands to copy the ROM I could just send them in the hope it will reply but it sure as hell isn't saying anything to the commands I have sent.
Hmmm. Must there be a exploit? Zzz there's are very little/no hackers having a focus s or a focus flash/omnia w. they all have 1st gen devices I think.
My phone was bricked and I restored it following this tut ( http://forum.xda-developers.com/showpost.php?p=62405939&postcount=138 ). Now the phone is turned on normally, but I have this strange thing:
My phone number
Unknown
IMEI
0
IMEI SV
00
I have also this warning: Current version is not available for user. Can't find matched cust for NT-code mcc/mnc, subset.
How to fix?
BlackStorm94 said:
My phone was bricked and I restored it following this tut ( http://forum.xda-developers.com/showpost.php?p=62405939&postcount=138 ). Now the phone is turned on normally, but I have this strange thing:
My phone number
Unknown
IMEI
0
IMEI SV
00
I have also this warning: Current version is not available for user. Can't find matched cust for NT-code mcc/mnc, subset.
How to fix?
Click to expand...
Click to collapse
Same thing happened to me after I unbricked my device using the exact same tutorial. However, even with IMEI 0 I can still make and receive calls and text messages. But I'm not sure if I should leave my device like this. If someone has any solution to provide I would be very grateful! I hope it doesn't involve flashing any ROM again cause I'm really afraid that I may brick my phone again ...
Hey guys, I had exactly the same problem. I tried different things including flashing various Roms and Bootstack, but nothing seemed to work. Since I’ve been searching for a solution quite a while, I now have the honor to help you out and everyone with an L90, who stumbles upon the same issue.
First of all, I made a backup of my EFS, so that I could restore the state my phone was in (IMEI=0, but working baseband). You can do that easily with TWRP (thx to shoxxy . By the way, this is something which we all should have done beforehand. It would have been much easier to restore our IMEIs.
But don’t worry, if you follow the instructions in this video (https://www.youtube.com/watch?v=nwzgs1Cmr9k) you should be able to get your IMEI working again. For those, who feel more comfortable following written instructions I copied the following procedure using this thread (http://forum.xda-developers.com/showthread.php?t=1960918) as a model and edited them a little to the way it just worked for me.
Do this on your own responsibility! And better double-check with the video our other threads.
Before you start:
Download this package (http://www.mediafire.com/download/figdbxb75j5kyry/package.rar), it belongs to the user who made the video on youtube (PremiumRepair).
Make sure your phone is rooted and USB-Debugging is enabled (http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951)
Procedure :
Install Drivers. Either you use LG Support Tool or download them directly. For me the LGUnitedMobileDriver+3.14.1_ML_WHQL.exe worked just fine. Don’t forget to uninstall old drivers or you could run into problems.
Install QPST v2.7.378. Microsoft Visual C++ 2005 Redistributable is a prerequisite, just confirm it.
Plug your device into your PC (USB port)
Run QPST Configuration from your Windows Start menu. Switch to the second tab ("Ports") and choose "Add new port" (bottom left button). You should see a COM port associated with "USB/QD Diagnostic". Select it, then press Ok. You can close the QPST Configuration window now.
Open Windows Explorer and browse to "C:\Program Files\Qualcomm\QPST\bin" (or wherever you installed QPST) and launch RF_NV_Manager.exe. In RF NV Manager, Go to "Settings / Comport". You should see your COM port in the dropdown box. Select it, then press OK.
Go to "File" and choose "Read from phone". RF NV Manager will read all NV items from the phone. Now if you see item #550, you will be able to alter it (see below). If you can’t find it, go to “File” and choose “Read supported RF NV Items”. If you still can't find it, there is a way to create it. Take a look at the thread I linked to.
Now comes the critical step of altering the IMEI. Select item #550 and you'll see 9 boxes on the right, a "Write NV" button and an "Hex" checkbox. Check the "Hex" checkbox.
Now, you'll have to enter the IMEI in the 9 boxes in a very specific way. The easiest way is to use the IMEI converter (for other method see linked thread). Put your IMEI in, convert it and put the digits in the boxes (two number per box).
Now you can then press "Write NV" to write the IMEI value to your phone.
Once done, unplug the device, and reboot it. Now you IMEI should be changed. If it’s not your number, take a look at the step seven again and check the video.
Please give a feedback, if it worked for you (incl. Details about your device, ROM, etc.) so that other users can profit from it. Thanks
Edit: @ BlackStorm94 - Don't worry about the warning. It will vanish if you install a different ROM.
I'm stuck at step 6. When I click Read From Phone, I get an error which says that my phone is not present. Also, on QPST Configuration, even tho I have set the Port to the one my phone appears, under Phone it says No Phone ... I guess my phone isn't recognized for some reason. Do I need to root it before I do this? I hope not because I don't really want to mess with it after the hard brick
Lazgeor said:
I'm stuck at step 6. When I click Read From Phone, I get an error which says that my phone is not present. Also, on QPST Configuration, even tho I have set the Port to the one my phone appears, under Phone it says No Phone ... I guess my phone isn't recognized for some reason. Do I need to root it before I do this? I hope not because I don't really want to mess with it after the hard brick
Click to expand...
Click to collapse
Yes, your phone needs to be rooted. This solution for rooting works great for me: http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
mhikel said:
Yes, your phone needs to be rooted. This solution for rooting works great for me: http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
Click to expand...
Click to collapse
So, I rooted the phone successfully, but the phone is still not recognized by QPST Configuration or RF NV Manager. My pc recognizes the phone and I can do everything properly, but these programs say that there is No Phone ... I don't know what to do ...
mhh, that sounds like a problem with the drivers. Did you uninstall all the drivers (incl. Qualcomm drivers) from your PC? And have you installed the official LG drivers for our devices (for example from the link in this post: http://forum.xda-developers.com/showpost.php?p=62405939&postcount=138) Try another PC if it still doesn't work
mhikel said:
mhh, that sounds like a problem with the drivers. Did you uninstall all the drivers (incl. Qualcomm drivers) from your PC? And have you installed the official LG drivers for our devices (for example from the link in this post: http://forum.xda-developers.com/showpost.php?p=62405939&postcount=138) Try another PC if it still doesn't work
Click to expand...
Click to collapse
I'm going to try on a new computer tomorrow afternoon and I'll let you know how it went. I uninstalled all drivers associated with my phone on my computer and after reinstalling them I still got no results. I guess I may have confused it So that's why I'll try on a new one. Thanks for your help
Hello, sorry for the late reply. I just wanted you to know that even though I tried with another computer, my phone was still not recognizable. It doesn't really matter tho, cause even with the IMEI 0 I still have service and it works normaly for about a month now. If you have any solution then I would like to try it, but if not then it's okay. Thanks for your time
No worries! You do have USB-Debugging enabled, have you!? I mean you probably needed to do this for rooting. But if you haven't done it yet, that's probably the problem. Enable USB-Debugging like this (Go to Settings > General > About phone > Software information, tap Build number seven times and then go to Settings > Developer options and turn on Usb debugging) (copied from http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951)
[/COLOR]
mhikel said:
No worries! You do have USB-Debugging enabled, have you!? I mean you probably needed to do this for rooting. But if you haven't done it yet, that's probably the problem. Enable USB-Debugging like this (Go to Settings > General > About phone > Software information, tap Build number seven times and then go to Settings > Developer options and turn on Usb debugging) (copied from http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951)
Click to expand...
Click to collapse
Yeah yeah, I had USB Debugging enabled every time I plugged my phone into both of my PCs. But I don't think that's the reason this tutorial isn't working on my phone. When I unbricked the device, I had to use the L90 D405 loader.img in order to reflash the bootloader and recovery. But my phone is the d405n model, and that's the ROM I installed to it. So the phone now thinks that it is the D405 but the ROM I have installed is the one for d405n. I hope you understood this cause I know it's a bit weird I see options to activate NFC but I never use it so I can't tell you if it works. However I can activate it properly. Anyway, about the IMEI, as I told you, it basically works without problems even with 0 because I think that my service provider doesn't block anybody except someone reports the device as stolen. If you have any further solutions then let me know but if not the don't worry, I'm okay!
Lazgeor said:
But my phone is the d405n model, and that's the ROM I installed to it. So the phone now thinks that it is the D405 but the ROM I have installed is the one for d405n.
Click to expand...
Click to collapse
Ah, that makes sense. Flashing the right bootstack as described here (http://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632) could maybe help you (I haven't tried the one for D405n myself but it's supposed to stable). On the other hand: You probably installed a .kdz (ROM) with the correct Bootstack for your D405n included. ...So I don't think it'll bring back the IMEI or change anything. I'm running out of ideas, sry!
mhikel said:
Ah, that makes sense. Flashing the right bootstack as described here (http://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632) could maybe help you (I haven't tried the one for D405n myself but it's supposed to stable). On the other hand: You probably installed a .kdz (ROM) with the correct Bootstack for your D405n included. ...So I don't think it'll bring back the IMEI or change anything. I'm running out of ideas, sry!
Click to expand...
Click to collapse
It's okay I don't want to bother you any further. I'll buy a new phone soon anyways and since I'll give this one to my small brother, I don't think he'll really worry if his IMEI is 0 If at some point this device gets blocked by a service provider then I'll start searching for ways to fix it again. That bootstack page you mentioned seems useful. I'll try that if I do have any problems. Thank you very much for your help
That sounds reasonable! You are really welcome If you still need help just post here again. Although I have no other ideas at the moment someone else might. If you felt supported here I'd really appreciate the thanks! button. Yeah, you are right, the bootstacks supplied by Xemidra are of great value for our LG L90.
mhikel said:
That sounds reasonable! You are really welcome If you still need help just post here again. Although I have no other ideas at the moment someone else might. If you felt supported here I'd really appreciate the thanks! button. Yeah, you are right, the bootstacks supplied by Xemidra are of great value for our LG L90.
Click to expand...
Click to collapse
Update: I actually fixed it I know I told you that I would leave it as it is for now, but today I had nothing to do, so I decided to try my best and fix it. What I did was, as the post you told me said, I had to install the Kit Kat bootstack and the easiest way to do that is by flashing the Kit Kat rom. So I downgraded to android 4.4.2 using the stock rom I found on another post, and then I used your tutorial on the Kit Kat version. This time I was able to pass step 6 because my phone was getting recognized properly. I also didn't needed root access after all, since the new rom was just installed and it worked. After finishing the tutorial and restarting the phone, my IMEI was back! Then I upgrated my phone to the lollipop version, and when the upgrade finished, my IMEI was still there. So now I'm in lollipop with a working IMEI. I'm so thankful to you now, thank you very much for helping me and providing me these useful tutorials. I really appreciate it
Wow, that's just great!=) congratulations, you can be proud! Happy for you, that was quite an issue. You are welcome=) Well, someone from this forum helped me out, when I seeked for help and I am happy to give something back. Thank you for sharing your solution! That should be helpful for the next one stumbling over this problem. Enjoy your completely restored phone!=)
As the title says.... tried to uninstall all the drivers and install them again..some restarts my pc...some uninstalls and then again installs...but the problem continues. Any suggestions? my lg l90 405 is rooted...does the boot loader have to be unlocked too or smth?
IN Device manager phone is like LGE Mobile USB serial port (com5)
QSTP CONFIGURATION: COM 5 ENABLED NO PHONE
RF NV MANAGER: Phone is not present when i m going to read.
any ideas? thanks a lot
UPDATE: Phone decides to work just fine without IMEI. receiving and make calls sms and stuff fine. just saying..
Same thing happens to me too. With all the correct drivers installed I still get No Phone in QPST Configuration ... But yeah, my phone works perfectly too with IMEI 0, so even if there isn't a solution about this problem, it doesn't really matter.
Hi guys .. can you share the backup NVRAM.bin of your phone 'cuz i have a problem of my unit my phone detects a sim name of our carrier but it says NO SERVICE, both sims, in Wifi also it can detect wifi networks but can't connect, also in bluetooth, i always refresh it to scan but cannot found nearby devices, and also when i used the wifi-hotspot to activate the Shareit apk but it says restart hotspot, it keeps restarting .. i think the NVRAM has been damaged
last time i've remembered, this phone was deadboot and i flashed the firmware through SP Flash Tool .. i've used FORMAT ALL + DOWNLOAD option, it's working now but i cannot use the wireless connections .. when i checked the scatter firmware, there is no nvram.bin on the folder
someone else here who has a good heart to share his NVRAM or full backup rom ?? much better if its already flashable
i hope you would help me out of this problem
Doctor_Titi said:
Hello
I'm not an expert about Asus Phones (I've got my own ZenFone Go just since 2 days), but i'm not sure then NVRAM.bin cause networks problems. This could be something like Baseband or Firmware. Have you searched if Asus released full firmware for your phone? (and also try to flash it from recovery, or your PC) This could generally solve some problems.
Click to expand...
Click to collapse
Hey friend could you send me, firmware or backup, flash sp flash tool, thanks! Asus zc500tg:dedos cruzados::dedos cruzados:
Doctor_Titi said:
Sorry, I dont have this phone :/ but I'll try to search ROM for ur phone if it's available. What have you tired to make it working? (And also how you bricked ur phone)
Click to expand...
Click to collapse
I have an asus zc500tg v 12.1.0.5, the brickeo brickeo to the moemento of flashing a rom in twrp recovery and it does not turn on but the pc detects it !, I need your help to solve the problem, I am from colombia. : Eek::
Doctor_Titi said:
If ur phone is recognized, try fastboot and ADB command. Also, have you tried to unlock your bootloader? Because an locked boot loader brick your phone if he's not. (But you can recover this, by processing unlocking operation in fastboot/recovery)
Click to expand...
Click to collapse
Hello friend, I can not recover the mobile with adb and recovery, I need a firmware backup for sp flash tool
Help Me
Help me zenfone go zc500tg zoovd my phone is wrong root then total dead can not live
if your phone can not live, what can we do?
tambok_15 said:
Hi guys .. can you share the backup NVRAM.bin of your phone 'cuz i have a problem of my unit my phone detects a sim name of our carrier but it says NO SERVICE, both sims, in Wifi also it can detect wifi networks but can't connect, also in bluetooth, i always refresh it to scan but cannot found nearby devices, and also when i used the wifi-hotspot to activate the Shareit apk but it says restart hotspot, it keeps restarting .. i think the NVRAM has been damaged
last time i've remembered, this phone was deadboot and i flashed the firmware through SP Flash Tool .. i've used FORMAT ALL + DOWNLOAD option, it's working now but i cannot use the wireless connections .. when i checked the scatter firmware, there is no nvram.bin on the folder
someone else here who has a good heart to share his NVRAM or full backup rom ?? much better if its already flashable
i hope you would help me out of this problem
Click to expand...
Click to collapse
Hello tambok,
Unfortunately AFAIK, NVRAM partition holds the data for all the radios(like the uniqu IMEI number for telephony radios, other stuff for Wifi and Bluetooth etc.), and it's unique for every device, so if you didn't back it up, sorry - your device has turned into a very expensive brick.
Should you manage to get it through repairs, warranty(who am I kidding, your warranty is void because of flashing it) or non-warranty, back up the NVRAM next time you format your device.
@tambok_15 bro you should be able to find your wifi, bluetooth, imei, etc code for you device on the box of that phone the day you purchased it. It should be written on one of the sides. (Screenshot below)(i erased mine)
After you find the device-specific code on the box, you can then flash it into your nvram via SN Write tool (just google it) just make sure to have the correct drivers as well. You can also find a tutorial on how to use sn write tool on the forum hovatek.
I am not 100% sure this will fix the phone entirely but it's worth a shot. Good luck.
Edit: If your problem is related to baseband i don't know about it maybe you can find a solution on google . . .
I need help too. So, I own a Moto G5s plus sanders. I unlocked its bootloader the day I got it. Didn't keep any backup and rooted it. I Also installed dot os based on android 11. But my 4G Volte connection was finicky. So, I decided to use a Volte zip patch. But, anyways I flashed the zip via TWRP and tried to reboot. But the phone didn't turn on after that. After a few minutes to my shock I understood that I hardbricked my mobile. No button combos, nothing worked. Anyways in my desperation I found a YouTube video showing the use of blankflash to revive a phone and lo and behold I used the procedure to again restore my device. It booted to the fastboot interface. But my happiness was short lived. My baseband was unknown at this point and the bootloader was I dunno downgraded to 0.5 inplace of 2.12. But, more importantly the unlock status was lost. I unlocked it again and all went well. I could even flashed TWRP. but then I realised I couldn't upgrade my bootloader. I couldn’t do anything. It's always gives a "security downgrade", "preflash validation failed" and "permission denied" error. I even tried RSA official rescue tool from Lenovo but even it was unsuccessful. It was never unsuccessful before that. Not even with a unlocked bootloader. I researched for days and tried custom ROMs. I flashed stock images. Nothing brought back my baseband and IMEI. When I type "fastboot oem unlock critical" it gives me permission denied error with a message. "Need OEM signed bootloader." I think the blankflash bootloader is the root of all evil. I need to change it and therefore I need to enter the edl mode. I have tried all adb commands and fastboot commands. The phone reboots okay after those commands but never goes into edl mode whatsoever. I am also ready to do a controlled hardbrick of my device to go into the edl mode so that I can use my device again with a proper bootloader and a properly working fastboot. Please help
i think this vid will help
Greetings everyone. Sorry if I posted this in the wrong forum. Please move this in appropriate forum if I made a mistake. Believe me, for the last 7 days I have searched all of xda and internet, followed innumerable guides, FAQs and workarounds and none worked. So, as a last resort I am starting this thread
Device: Motorola Moto G5s Plus XT1804 ......4GB _64GB variant
Problem: 1) Baseband not found (unknown) Original Baseband: M8953_52.61.07.98R SANDERS_INDIADSDS_CUST
2) IMEI 0 (Sim cards are not detected).
I bought this refurbished phone about an week ago after my last LG went kaput. I was happy by the build quality of the phone. But it only ran Android 8.1 Oreo. So, I decided to put a custom ROM in it. I am not exactly a newbie to the world of CyanogenMods, Lineage OSes and Pixel Experiences. Or, so I thought. Anyways, after a lot of searching I finally decided on Dot OS 5.2 Official Android 11 version. The ROM looked very pleasing and the reviews looked positive. So, I got the unlock key from Motorola website, unlocked the bootloader, put in official TWRP recovery in it. Everything went like a breeze and in all that excitement I forgot to take a backup of the persist, efs and other partitions. A very costly mistake it seems. DotOS booted fine and looked really fresh till I found that there is a small cross near the SIM card network signal triangle up righthand side corner and the signal is only LTE and not VOLTE. I was using a Vodafone Sim card at the time. Although VOLTE option was enabled in SIM settings. To confirm my doubts regarding VOLTE I switched to a JIO Simcard and alas I was not able to make a call without redirecting through the horrid JIO calling app. VOLTE was indeed not working. So, I looked up for a fix and I found a Volte ZIP file from here https://www.google.com/url?sa=t&sou...0QFnoECBAQAQ&usg=AOvVaw0YgJvCjQWXXV8WQSJkxBOK . This was the starting of my troubles. I flashed the universal VOLTE fix zip from TWRP and it flashed fine. On rebooting, I found to my shock that my phone was not turning on. I pressed and held the power key and there was no sign of life. I couldn’t go to the fastboot bootloader or recovery. Only the white led blinked at the top when connected to the charger. My phone was apparently hard bricked. I searched frantically for a solution in this forum and YouTube wherein I found that one can bring it back to life by doing a blankflash. Found the blankflash file here https://www.google.com/url?sa=t&sou...wQFnoECAsQAQ&usg=AOvVaw1eVdBWGVFr8aiqLdP-ZkeT followed the instructions and it flashed my bricked device back to fastboot. I was relieved for a moment but the next I found that the Bootloader version has downgraded from BL C2 07 to BL C0 05. I knew something was wrong as bootloader downgrade shouldn't be possible. Also the unlock and rooted status were also lost and the baseband was unknown at this point. Anyways the device was recognised as a fastboot device and I tried to flash the stock ROM latest version using the fastboot. But, only then I realised there was something wrong with the bootloader. It gave errors like security downgrade, permission denied, preflash validation failed, remote command failed. At this point I was truly confused and worried. Why would it think the latest bootloader to be a security downgrade to a supposedly old bootloader and prevent me from flashing it. However it did flash the other files like gpt.bin for partition, oem.img, boot.img, system.img sparsechunks and everything else. I booted back to Android 8.1 Oreo and everything seemed working except my IMEI now read zero and my Simcard was not recognised by the device. After that I again unlocked my bootloader. Somehow the original unlock key worked and the bootloader screen said flashing unlocked but the bootloader didn't behave like an unlocked bootloader. The TWRP installed fine but couldn’t install the latest Pixel Experience. The flash screen said PE 11 was for Sanders and my device is (blank no name). I tried both the normal and plus and both behaved similarly. Lineage OS unofficial builds behaved similarly. I again tried Dot OS and Arrow OS and both installed fine except there was no signal. For a moment I tried to forget about the bootloader but concentrated on recovering my IMEI and Baseband but I couldn’t. For nearly 5 days I tried different guides including a detailed guide using Validus Sanders ROM but none worked. My EFS folder has files around 12 megabytes but my Persist seems deleted at zero bytes. The IMEI keeps changing between null, zero and unknown depending on the 20 something ROMs I tasted on this device. At this point, I am at a loss. This was to be my main phone and I am financially crunched. I can't buy another phone right now. I think that blankflash bootloader is corrupted and it is giving me permission denied errors. Even Magisk won't work properly. I even tried using the official rescue and smart assistant tool by Lenovo and it failed at 47 percent. I tried in different computers and Win7 to Win 11 OSes but it was of no use. I also tried getting a QCN file but I couldn’t get one for the device to recover the IMEI. Please suggest something if anyone of you can save this poor device of mine. Thanks in advance
Raghaov said:
i think this vid will help
Click to expand...
Click to collapse
Thanks for the quick reply but my phone is soft bricked now. It was hardbricked and I uses a faulty blankflash bootloader to bring it back to life. My device is softbricked now. I have lost my baseband and I have no IMEI. I cannot take calls and no mobile data. Can you show me a way to go to edl mode in my device. Thanks again.
can your phone turn on if yes can you root it with magisk
if yes then pls tell me i will tell you
I can do everything except calling and mobile data. Yes, I have rooted with Magisk and have root access. But my baseband is unknown and my IMEI is showing zero. I can't call or access mobile data. Although I can use wifi
I have tried what is shown in this video already. Didn't work
I think the blank flash bootloader was corrupt or of a different region.
so go to magisk manager and on top-right corner you will see setting click the button right next to it and click on reboot to edl
I didn't even knew that. Trying asap. Will update
Doesn’t work. Reboots back to system.
Updated Magisk to latest and tried both edl and download mode like you said brother. Everytime boots back to system. Am I missing something. The phone was not connected to the PC at the time
I am on stock Oreo now. Rooted and twrp installed
An interesting observation while installing Xposed, it gave an error that the device is not rooted properly
I have an untouched dump file for my model. The whole thing. Could you please guide me how I can restore my smartphone from that.
can you flash it through adb sideload fastboot twrp etc
I don't know but I sold the device. I bought a new one. Thanks @Raggaov for the help.
you're welcome