Unknown Baseband / Lost IMEI, classic problem but frustating - LeEco Le 1S Questions & Answers

Hi,
I have the X500 16GB model. I cannot use mobile network at all after wrongly flashed 15s firmware directly from a non-stock multilanguage ROM. Here's my take
1. IMEI unknown, Baseband unknown, and I have no backup at all. From what I read, I might lose original NVRAM file/configuration/whatever. There are at times that my SIM card is recognized. However, due to NVRAM problem..my device cannot connect to mobile network at all (no service, manual/automatic network dicovery loops forever)
2. I cannot use ADB on my PC no matter what. There's a very strange problem that my ADB is overridden by Windows USB generic driver. Specifically, this is what happened:
- I have already installed ADB driver.
- Everytime I plugged in my device (USB debugging enabled, charging only) my PC (Windows 7) will recognize it no problem. When I view driver connection with USB deview, there are a pair of value that intrigued me the most. One of the value is ADB driver (pink indicator), with empty serial. The other value is LetvX500 (or other variant, depending on ROM, with green indicator) with available serial number. That made every time I list the device using "adb devices", it will come up empty, blocing any ADB flashing method available (MTK Droid Tools, ADB push, ADB sideload, Fastboot, anything)
- I did almost everything that I could think of to disable the generic USB driver to bring up ADB driver as the only driver recognizing my device (uninstalling driver using USB deview, deleting usbcgpp.sys, blocking USB access, etc), but I could never solved the problem. It's because these two driver apparently go up and down together. Disabling/uninstalling the USB Generic driver always kills ADB driver as well.
3. Locked out of ADB method, the only possible method is to flash fresh ROM to the device. The thing is, it is very hard to find stock rom with scatter file flashable using SP Flash Tool and stock NVRAM. Most of the posted ROM are either flashable using ADB/TWRP method or have no fresh NVRAM data to fix baseband problem (its logical though, because most people most likely want their IMEI intact after SP flashing).
So, I would like know
1. Is there any way to solved the frustrating Windows driver problem and bring up single ADB driver recognition?
2. If no 1 is not possible, does anyone has stock ROM, with scatter file flashable using SP Flash Tool, and containing stock NVRAM?
3. Last question. X 500 has two SIM, and two IMEI. However there's only 1 IMEI information on box/warranty sticker. If I ever get network discovery working, is it possible to use same IMEI in both SIM? would it work?
Thank you very much...

Follow up
I am dealing with same problem and have spent some time trying to resolve it but no approach showed any success.
Can we get a focus group and try to remedy this problem?

One : i faced same ADB driver issue, it occured when i installed PDA apps to sync Phone with PC. I couldnt find any other workaround then installing a fresh version of OS, or a different PC.
Two : http://www.letv.re/topic/725-stock-firmware-8s-14s-of-letv-le1s-x507-sp-flashable-indian-version/
Follow This link for installing stock rom using SP flashtool
Three: Once you have any version of ROM installed. Root & then Install "Tool Hero" App (Google for apk file coz its not available in Play store and many countries). Change your IMEI as per the box and reboot. Secondary slot would Work with any random IMEI number if phone has the primary IMEI properly configured.

Related

[Q]Problem with MTP (and help with a workaround)

Hi
Some background. Like many, I bought a TF700T and like a fool installed the OTA update to JB. I then downgraded, rooted in .30, then upgraded again and flashed SU to keep root in JB. I am now, therefore, running the stock OTA JB ROM, rooted. My bootloader is also unlocked.
Initially after this, plugging the TF700 into USb on Windows 7 (x64) worked fine - the device popped up as a Media Device and I could transfer files on and off it with ease. Now, without changing anything on either end, Windows is refusing to play. It tries to install MTP drivers but fails. If I boot the device in either CWM or Fastboot it connects fine (with adb and fastboot, respectively).
I want to get files on and off the *internal* storage (I don't have an external sdcard)
Things i have tried:
- Using a different USB port
- Using one of the USB ports on the back of the machine, instead of the front ones
- Uninstalling the MTP drivers
- Using the ASUS drivers from the website
- Cleaning out all my old unconnected USB devices (show devmgr_unconnected_devices=1 or whatever) and uninstalling all THOSE drivers
- Cleaning out with USBDeview
- Fresh install of the OTA ROM, after a data wipe/factory reset and wiping cache and dalvik
The only things I haven't tried are a new USB cable (damn you ASUS and your proprietary connector), and a clean install of Windows (major ballache).
Any ideas about what I could do to sort this would be greatly appreciated.
Since I only want to be able to move files on and off the device, I tried a workaround. I tried mounting the sdcard (internal) in windows manually through adb but the command I used to use on my old S2 through adb shell (echo dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file) but it errors with No such path or similar. I'm unsure if the mount points are different (I guess they will be, can anyone help with telling me what the mount point for the internal emmc is on the tf700?)
Really hope someone will be able to help me!
Thanks in advance guys
I'm in a similar situation except I'm not rooted or unlocked. I've tried just about all the steps you've mentioned w/ no luck. I've even tried to three different PCs running XP, Vista, and 7 and get the same result. What makes the situation even worse is my brand new 32GB microSD card won't read on my desktop as well.
m000se said:
Hi
Some background. Like many, I bought a TF700T and like a fool installed the OTA update to JB. I then downgraded, rooted in .30, then upgraded again and flashed SU to keep root in JB. I am now, therefore, running the stock OTA JB ROM, rooted. My bootloader is also unlocked.
Initially after this, plugging the TF700 into USb on Windows 7 (x64) worked fine - the device popped up as a Media Device and I could transfer files on and off it with ease. Now, without changing anything on either end, Windows is refusing to play. It tries to install MTP drivers but fails. If I boot the device in either CWM or Fastboot it connects fine (with adb and fastboot, respectively).
I want to get files on and off the *internal* storage (I don't have an external sdcard)
Things i have tried:
- Using a different USB port
- Using one of the USB ports on the back of the machine, instead of the front ones
- Uninstalling the MTP drivers
- Using the ASUS drivers from the website
- Cleaning out all my old unconnected USB devices (show devmgr_unconnected_devices=1 or whatever) and uninstalling all THOSE drivers
- Cleaning out with USBDeview
- Fresh install of the OTA ROM, after a data wipe/factory reset and wiping cache and dalvik
The only things I haven't tried are a new USB cable (damn you ASUS and your proprietary connector), and a clean install of Windows (major ballache).
Any ideas about what I could do to sort this would be greatly appreciated.
Since I only want to be able to move files on and off the device, I tried a workaround. I tried mounting the sdcard (internal) in windows manually through adb but the command I used to use on my old S2 through adb shell (echo dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file) but it errors with No such path or similar. I'm unsure if the mount points are different (I guess they will be, can anyone help with telling me what the mount point for the internal emmc is on the tf700?)
Really hope someone will be able to help me!
Thanks in advance guys
Click to expand...
Click to collapse
First check make sure you have your "USB debug" and "Unknow software" checked in settings. Then go here and install the pda software for your windows. Once installed, it will installed all the driver for your tab automatically. You don't need to use the software, you can uninstall it later, but the driver will stay.
http://junefabrics.com/android/download.php
I haven't picked up a TF700 yet (out of stock locally), so these are just general suggestions...
From adb, shell into the OS (adb shell) and list the directories to try and determine their structure. If the device is booted, the internal SD should already be mounted.
I would start by looking for the following folders:
/sdcard
/mnt/sdcard
/data/media
m000se said:
Hi
Initially after this, plugging the TF700 into USb on Windows 7 (x64) worked fine - the device popped up as a Media Device and I could transfer files on and off it with ease. Now, without changing anything on either end, Windows is refusing to play. It tries to install MTP drivers but fails. If I boot the device in either CWM or Fastboot it connects fine (with adb and fastboot, respectively).
Click to expand...
Click to collapse
I had the same problem getting MTP to work on old XP machine. The following worked for me...see post #12
http://www.transformerforums.com/fo...ormer-manual-usb-drivers-sync-software-2.html
Thanks for the replies, everyone. I installed PDANet and was initially hopeful once the drivers started installing. Sadly, Windows still doesn't see my device.
adb shell-ing into the device --> mounts
This lists /dev/fuse as the internal storage. I can't echo this to /sys/devices/usb_mass_storage/lun0/file because when I do it returns "No such file or directory"
The solution posted as working on XP machines doesn't work either.
This is seriously annoying. I'm tempted to just give in and get myself a 32GB SDHC and card reader and just use that instead - at least that way I can move the files across with Root Explorer or something...

[Q] ROOT Smartpad ep750

Hi, does anybody have any idea on how to root this? On their website they have an updater tool which says to get it into recovery you must push power and volume button only there is no volume button.. only physical button is a power button and then there is a reset hole in the back of the tablet. http://www.easypix.eu/smartpad750_en.html
I would like to at least root it and then see if there are any developers for this model.
Thanks.
I found a question from someone who has broken their same model tablet which was rooted, so it is possible.
You can get the proper windows drivers and connect to it through ADB. Using this method you can push clockwork mod touch, and the touch interface should work fine. You might have to use ADB terminals for keypresses as it starts though, I'm not sure how you would boot into recovery without a rom. But once in a rom, you can always select the reboot into recovery option.
do you have any guide for this, Im more just interesting in rooting it to start with. I think I figured out how to get it into some sort of recovery mode but windows wont let me install the recovery mode drivers so I cant do anything
bump
I just rooted it with unlockroot.com , It works for any tablet with the rockchip 2906 (Rk29).
Kevinjs said:
do you have any guide for this, Im more just interesting in rooting it to start with. I think I figured out how to get it into some sort of recovery mode but windows wont let me install the recovery mode drivers so I cant do anything
Click to expand...
Click to collapse
Hi there. Do you mind sharing the info how to get it into some sort of recovery mode . And with the tool from that web site. Was it difficult to do?
ADB does not find Easypix Smartpad EP750
Kevinjs said:
I just rooted it with unlockroot.com , It works for any tablet with the rockchip 2906 (Rk29).
Click to expand...
Click to collapse
It seems impossible for me, I installed the driver, now in the Windows device-manager you can find a "Class for rockusb devices" and there a "RK29 Device" but adb seems not fo find it.
While I see the device in my Windows device manager I pushed the Root-button from the unlockroot.com - tool, but after it tried to check via ADB there comes a popup "not detected any device ..."
Checking it with Ubuntu-Linux with the lsusb - command, this tablet has NO NAME, I can find the VendorID and the ModelID but after that, there is NOTHING , all other USB-Devices do have a name after its IDs, and trying to check via Davlik Debugging Monitor (ddms) you have to chose the name of your device,
but it is impossible to me, because I cannot chose NOTHING to use NOTHING with ADB ... has anybody an idea, how it may work, or has anybody a working ROM on his Easypix Smartpad EP750 which has root or at least a name ?
Maybe anybody has a working udev - entry for Linux ... pls post it here !!!
Under Windows I am able to flash the device with its own flashing-tool (RKBatchTool) but since now I did not find any ROM which I can flash instead of the original ROM - the latest I downloaded from Easypix-WebSite = 750_20120621 with Android 4.04 but no root-access,
I tried to flash a CM9, but the RKBatchTool told, that was no possible ROM for that device .....
ProJerem said:
It seems impossible for me, I installed the driver, now in the Windows device-manager you can find a "Class for rockusb devices" and there a "RK29 Device" but adb seems not fo find it.
While I see the device in my Windows device manager I pushed the Root-button from the unlockroot.com - tool, but after it tried to check via ADB there comes a popup "not detected any device ..."
Checking it with Ubuntu-Linux with the lsusb - command, this tablet has NO NAME, I can find the VendorID and the ModelID but after that, there is NOTHING , all other USB-Devices do have a name after its IDs, and trying to check via Davlik Debugging Monitor (ddms) you have to chose the name of your device,
but it is impossible to me, because I cannot chose NOTHING to use NOTHING with ADB ... has anybody an idea, how it may work, or has anybody a working ROM on his Easypix Smartpad EP750 which has root or at least a name ?
Maybe anybody has a working udev - entry for Linux ... pls post it here !!!
Under Windows I am able to flash the device with its own flashing-tool (RKBatchTool) but since now I did not find any ROM which I can flash instead of the original ROM - the latest I downloaded from Easypix-WebSite = 750_20120621 with Android 4.04 but no root-access,
I tried to flash a CM9, but the RKBatchTool told, that was no possible ROM for that device .....
Click to expand...
Click to collapse
How did u manage to flash through windows? i have one of these tablets that was handed out with some ****ty program that has been installed by a medical company to give out to patients , with a load of information about certain medical conditions, a load of ****e basically, i want to flash the original rom in order to wipe this crap program from it to allow me to use it as a normal tab . I managed to install the driver but cannot get it into any form of recovery mode in order for the device to show in the flashing program . Any help appreciated
hi i was wondering if you could let us no if it worked for you as i have 3 of them with pattern key lock and its saying im putting in the wrong email address which is the correct 1 and i can find any information to help me remove them.

[Q] Installing USB Drivers for ADB in Recovery

It's been bugging me for a while that I can't use ADB while in recovery. It's a matter of getting the drivers installed correctly, I think, I just don't know exactly how to do it. When the phone is booted I can use ADB and MTP just fine. Odin sees my phone in download mode as well. The only problem is in recovery. I'm using TWRP 2.3.3.0, but I've had the problem on previous version of TWRP and CWM. I have the Samsung USB drivers installed, and when the phone is booted Device Manager (in Windows 7) says the drivers being used are from Samsung. However, when in recovery Device Manager shows SAMSUNG_Android_SCH-I535 with the yellow '!' and says no drivers are installed. I can try to choose the drivers to install manually, but if I point to the Samsung USB Drivers folder, Windows can't find the right drivers automatically and there are 25 subfolders with somewhat cryptic names, so I don't know which to choose.
Does anyone know how to get ADB working in recovery?
EDIT: Got it working. I don't know anything about how drivers work, but I dug around a little and it turns out the device shows different Hardware IDs when booted versus when in recovery. The drivers .inf has to contain one of the Hardware IDs given by the device so after finding the driver being used by Windows (by searching for the Class GUID given in the driver details when the phone was booted and searching through all the .infs in the Samsung drivers folder for the matching string) I just added a line with one of the Hardware IDs given in recovery so Windows would install the driver. I tested with adb devices, adb shell and adb pull default.prop and each worked fine.
For anyone interested the driver being used is in 25_escape. In the file ssudadb.inf just add the line
Code:
%CompositeAdbInterface% = ssud.Install, <Hardware ID>
under [Google.NTx86] and [Google.NTamd64], where <Hardware ID> is one of the Hardware IDs given by your phone when in recovery. In Windows, go to the Device Manger > right click your phone > Properties > Details tab > Hardware IDs in the drop down. Mine was
Code:
%CompositeAdbInterface% = ssud.Install, USB\VID_18D1&PID_D001
Then update the driver, browse for drivers, pick the 25_escape folder, and you're good to go. The driver will fail a security check because you've modified it, I ignored it.
I imagine this could cause a problem if some other device uses the same Hardware ID (e.g. if it's some sort of generic or default one that's given in recovery) but I'll cross the bridge if I come to it. There may be some safer way to force driver installation.
EDIT: After doing this you'll get a warning when you plug your phone while it's booted. It will say something to the effect of Hardware ID missing or not being able to identify the device plugged in. This isn't a problem though, ADB and MTP still work fine and the device is identified properly in Device Manager.

[Q] Phone not recognized by computer

Alright, here goes my first post. I have lingered in these forums for awhile, and have always found what I needed. This is the first time my searching on here, as well as google, has let me down.
To clarify, if I connect to my computer and have USB Mass Storage on, I can see it, move files to it and everything. My problem is, I am using my old phone (P500) to learn and practice ADB (I own a GNEX), and would like to install CWM via ADB, but I need to move files to the root of my sd.. but my phone won't show up if it's in debugging mode!
I have the drivers installed, and used a toolkit to root (worked fine, no errors). Am I missing something here or is there another issue?
Info:
Windows 7 64bit
Telus Mobility (Canada)
Model: LG-P500h
Android 2.3.3 (stock)
stock kernel
MissBizz said:
Alright, here goes my first post. I have lingered in these forums for awhile, and have always found what I needed. This is the first time my searching on here, as well as google, has let me down.
To clarify, if I connect to my computer and have USB Mass Storage on, I can see it, move files to it and everything. My problem is, I am using my old phone (P500) to learn and practice ADB (I own a GNEX), and would like to install CWM via ADB, but I need to move files to the root of my sd.. but my phone won't show up if it's in debugging mode!
I have the drivers installed, and used a toolkit to root (worked fine, no errors). Am I missing something here or is there another issue?
Info:
Windows 7 64bit
Telus Mobility (Canada)
Model: LG-P500h
Android 2.3.3 (stock)
stock kernel
Click to expand...
Click to collapse
Since the device is not getting detected with USB Debugging enabled it's safe to assume a bad driver installation. To verify tho, enable USB Debugging on the device and connect it to your PC. Go to Device Manager. Somewhere towards the top, assuming the drivers were installed will be a device "ADB Interface" with a subitem "Android Platform Sooner Single ADB Interface" or something similiar. If the "ADB Interface" item isn't there then the drivers weren't installed correctly. Uninstall them. Reboot computer. Rerun driver installation program. When it finished, reboot your PC. Power off the device. Connect it to your PC. Power on the device and let all drivers install. You should be good to go from here.
If you'd like a good known set of LGE USB drivers, download Android Flash Recovery, link is in my signature. Hope this helps.
EDIT:
Oh, and Welcome to XDA

My Moto G is not connecting to PC even after other Moto G connects to the same PC

Well guys, from the title you will think that its a regular windows drivers problem, but its not that straight. My Moto G is not even detecting to my laptop having windows 10 system (no yellow exclamation mark in device manager, not even an error message atleast) But at the same time my friends Moto G and Moto E is connecting in seconds and able to see that in device manager, also able to access files from mobile storage.
First time in my life I am feeling clueless even after trying every option to fix it.
First the basic system information for you:
Laptop: Dell Inspiron 1545 , Windows 10 OS Pro version (not K and KN version )
Drivers installed: Motorola device manager, Google SDK pack is also installed with its ADB driver.
About phone:
Moto G XT1033 16GB model[/COLOR]
OS: non rooted stock Lollipop 5.1 OS, Developer options enabled-USB debugging enabled
Now things I've already tried to fix this:
With Windows 10:
1) Downloaded Motorola device drivers from mototola website for Moto G. Installed, checked for update drivers. Thoroughly gone through Device manager and checked there but no sign of device at all.
2) NO problem with data cable because it can transfer data and not just a charging cable. confirmed and verified.
3) Checked USB ports for loose contacts at both sides of wire. Connected in every port for hope. No such problem.
4) Even after my Windows 10 is a Pro version I still tried to install Media Feature Pack as suggested by Microsoft site in case to overcome this problem but no luck.
5) Whenever I tried to run Motorola device manager, it just checks for new device software and goes off saying no updates.
Now even you can tell that there is no issue with windows system.
With Moto G:
1) Checked USB debugging, stay awake options In developer options.
2) Tried changing MTP option to PTP and reverse in setting - storage menu.
3) Checked every setting menu from android settings and apps to make sure no one is preventing this device from connecting.
4) Tried reseting mobile with to factory.
5) Pen drive is connecting to mobile via USB OTG and data transfer is working to and fro.
Important:
1) I can transfer my mobile files to PC by wireless method using apps, but I want to root my device. For that I have to connect it to PC to unlock the boot loader.
2) Before 2 months with the same system and windows 10, this moto g was connecting to PC and I was able to transfer files. But for now its not connecting at all.
Sorry for the long post but help me guys !!! What can you suggest me here if I am missing something ?
Thanks in advance.:good:
Things you could try:
- Use a Linux OS (live CD/USB) and run lsusb to see if anything shows up
- Put the phone into bootloader mode (fastboot) and see if the PC detects any USB device
If both of the above fail, the USB port in your phone may be defective.
_that said:
Things you could try:
- Use a Linux OS (live CD/USB) and run lsusb to see if anything shows up
- Put the phone into bootloader mode (fastboot) and see if the PC detects any USB device
If both of the above fail, the USB port in your phone may be defective.
Click to expand...
Click to collapse
Thanks for the quick reply. I tried to connect mobile in fastboot mode and now its saying [device descriptor request failed] in device manager. I am trying further and will also check linux os option that you suggested.
Tried both of your workarounds
When connected in fastboot mode it is showing [device descriptor request failed] in device manager.
Searched about it a lot and tried different solutions suggested for it..but its still not connecting properly.
2) checked with live cd and using command lsusb but no luck there ..
Now I'm really thinking that it's a USB port problem/hardware problem of mobile..but how that port is working fine for charging ??
Plzz suggest me any other methods of fix thus problem or is there any other way rather than connecting mobile to pc for unlocking Motorola devices bootloader ???
After a couple of hours trying to fix this problem with my XT1039, I solved it with this windows update: https://www.microsoft.com/en-us/download/confirmation.aspx?id=49919 .
All over the internet ppl say that Media Feature Pack for N and KN versions of Windows 10 should be installed but all the mirrors and 1st results goes to the PREVIOUS version which didn't solve my problem. With this latest version, everything is working now.

Categories

Resources