Related
I was trying to root my phone using unrevoked 3.32 and during the install it, it stop with a back up CID error missing or something like that. i checked to see in hboot if it was rooted with it showing s-off, and it was but recovery still showed the regular triangle red error. So i restarted normally and tried into install terminal emulator on the phone and thats when it first started vibrating 5 times, then go blank with a green led flash. the phone will boot normally usually be able to use it for a min or less then it will repeat with the blank screens. After checking back into hboot it now shows that its unrooted with s-on. Now i also have problems with the usb/sdcard.
Things i have done to get it back to normal:
- hard reset using clear storage.
-Checking in the SD storage menu i could see it wasn't reading the SDCard so i restarted it in bootload and thru fastboot typed: fastboot oem enableqxdm 0.
- flash through bootloader this file : 3.70.651.1_PC36IMG.zip
After flashing it still takes multiple battery resets to finally get it through the first start up menu and then to the regular home screen. Seems to read the SDcard fine but when connecting the usb from wall charger or PC it doesn't recongnize at all.
The phone is 4 days old and seems to be back to stock except it still vibrates and goes blank with green led flash and it wont recognize charging/pc connection. Will i have any problem if i just go back to sprint and say i want a new one its not working right?
Phone info:
Baseband: 2.15.00.11.19
kernel: 2.6.32.17-gee557fd
Software: 3.20.651.1
PRI: 1.90_003
PRL: 60676
Hardware: 0003
HBOOT-2.10.0001
strdrk1 said:
I was trying to root my phone using unrevoked 3.32 and during the install it, it stop with a back up CID error missing or something like that. i checked to see in hboot if it was rooted with it showing s-off, and it was but recovery still showed the regular triangle red error. So i restarted normally and tried into install terminal emulator on the phone and thats when it first started vibrating 5 times, then go blank with a green led flash. the phone will boot normally usually be able to use it for a min or less then it will repeat with the blank screens. After checking back into hboot it now shows that its unrooted with s-on. Now i also have problems with the usb/sdcard.
Things i have done to get it back to normal:
- hard reset using clear storage.
-Checking in the SD storage menu i could see it wasn't reading the SDCard so i restarted it in bootload and thru fastboot typed: fastboot oem enableqxdm 0.
- flash through bootloader this file : 3.70.651.1_PC36IMG.zip
After flashing it still takes multiple battery resets to finally get it through the first start up menu and then to the regular home screen. Seems to read the SDcard fine but when connecting the usb from wall charger or PC it doesn't recongnize at all.
The phone is 4 days old and seems to be back to stock except it still vibrates and goes blank with green led flash and it wont recognize charging/pc connection. Will i have any problem if i just go back to sprint and say i want a new one its not working right?
Phone info:
Baseband: 2.15.00.11.19
kernel: 2.6.32.17-gee557fd
Software: 3.20.651.1
PRI: 1.90_003
PRL: 60676
Hardware: 0003
HBOOT-2.10.0001
Click to expand...
Click to collapse
That's weird. I'm pretty sure the vibrate 5 times and green blinking led indicates that the phone is in diagnostic mode. I'm not sure how to remedy the situation, I would've suggested a PC36IMG back to stock, but you already tried that. I would try taking the battery out for an hour or more (i've read of people being stuck in diagnostic mode, and leaving the battery out for a good length of time fixed it, i think) then try booting up, and seeing if it works. If not, to answer your question, as long as the bootloader shows S-on, you will have no problems taking it back to Sprint. You need to make sure you have no 'evidence of rooting' on your sd card, just to make sure that the sprint tech doesn't see anything on there. Good luck.
I formatted the sdcard, but it seems to be creating these files QXDM_some numbers.dm is this normal or any indication of rooting the phone.
Sorry to be the bearer of bad news but I had the same issue and eventually gave up after 3 solid days of working on it. You name it, I tried it. Had to get it replaced.
Something about unrevoked and my old 002 phone didn't jive together and the root aborted at an unrecoverable stage. No sd card mount, no adb, not even able to connect via usb, so running an ruu or new pc3600img wasn't an option.
As for the 5 buzzes and shut down after a min or so... Your guess is as good as mine. You can put it in diagnistic mode with the arrow up/power button boot, but thats 3 buzzes not 5.
Wish I could offer some actual help :/ Let us know if you find a fix.
Oh, before I took it back in I did a hard reset so it would reboot before they could get past the setup menus and see the superuser permissions app. Not that they'd care, but just in case.
I have just returned my EVO to sprint for this same problem. He told me it was a common problem. I get my new on today. They could have cared less that it was rooted, he told me it did not matter.
derekstory said:
I have just returned my EVO to sprint for this same problem. He told me it was a common problem. I get my new on today. They could have cared less that it was rooted, he told me it did not matter.
Click to expand...
Click to collapse
I ended up exchanging mine also. The lady really could have cared less. i wish i would of known cause i spent some time trying to get it back to normal. My sister also ended up exchanging hers because she got the white one and wanted the black one instead.
thanks for any help and replies.
I too had the same problem. It all happened when I was trying to flash cyanogen 7 RC2, I wiped all data, and all seemed fine. I rebooted and it went right to the bootloader and I noticed I was S-ON. Tried to re-root, and run a RUU. I did actually get it to boot to sense, but it froze and then I got the buzzes, and the green lights. I went to sprint since I have insurance. They checked it out and then an hour later, they gave me another one.
My EVO is currently stuck in the same state. I have spent a huge amount of time working on it, and have some information. I'm just dumping as much as I can remember in to this post, so excuse the lack of organization.
Before I go any further - I have not been able to fix the issue!
My phone was about as stock as possible when I took it to the Sprint store. They ordered me a new one and gave the broken one back. I have taken a few more risks now that my new one is on the way.
The initial problem started after flashing MIUI recently. The phone booted normally, but I noticed that the SD card was inaccessible. I would bet that the phone was refusing to charge over USB at this point as well, as that issue goes hand-in-hand with the sdcard problem.
The sdcard and its contents were fine. I later made a backup of the card and lost nothing.
Symptoms, high level info:
Phone immediately vibrates 5 times and begins flashing a green indicator, screen black at power on
Under unknown circumstances, the phone will display the white EVO boot screen before exhibiting the above behavior
Cannot exit this mode unless phone is unplugged and battery is removed
Bootloader can be accessed by holding volume down and power when starting fresh
SD Card is accessible in bootloader - indicates the problem is not purely hardware related
Fastboot can be used to temporarily (1 boot) gain access to sd card
Phone can be flashed with official PC36IMG
Phone can be set into RUU mode and flashed with official RUU
Official update.zip can be flashed from stock recovery
Qualcomm diagnostic tools can be used
Phone will remain in the installed OS for a very short amount of time
Bootloader shows S-ON, 'fastboot oem boot' shows Super CID and CID=111111111 instead of SPCS_001
Because one of my initial ideas was to flash a stock PC36IMG from the bootloader, I lost access to a custom recovery very early in the process. Other users may have better luck if they do not immediately flash a stock recovery.
Flashing PC36IMG is accomplished as usual. Vol- + Power.
To temporarily enable the sd card, disable Qualcomm Download mode:
Boot into bootloader
Wait for it to scan the SD Card
Select Fastboot (Power to select)
Plug into computer
Open a command prompt and ensure you have the fastboot executable
Command: fastboot oem enableqxdm 0
Exit fastboot
Select Clear Storage and select No to reboot OR
Select Recovery
The phone will boot into the OS. Under unknown circumstances, the phone will reboot. The amount of time can vary quite a bit. Enabling Airplane mode does not help. Using diagnostic tools to put the phone in Offline mode does not help.
If you would like to use Qualcomm diagnostic tools, the phone will have to be in diagnostic mode, rather than Download mode. The above steps will get you most of the way there, with the added annoyance that the phone will not enter proper diagnostic mode if left plugged in the entire time.
To ensure diagnostic mode correctly enables (or rather, that download mode disables):
Perform the fastboot command to disable qxdm
Unplug the phone
Navigate back to the bootloader, select Clear Storage
Select No (Vol-) to reboot
The white EVO boot screen will display
The screen will go black before the Sprint/4G animation plays
Plug the phone as soon as the white screen disappears, before the Sprint/4G animation
The phone will display in QPST Configuration without saying *Download* everywhere. The phone number will be incorrect, but that value is actually stored as a Directory ID in the NAM. In other words, it's okay.
The QPST Service Programming tool looked like a good place to start. If you would like to look at the configuration options for the EVO, you can start an offline connection using the profile "FFA/SURF QSD8650 Rev 2.0".
Note that the phone will always reboot after writing any values to the phone. This means you will have to pull the battery, unplug it, boot into fastboot, disable qxdm, boot into the OS each time.
You will need your MSL code for many of these applications. You can get it by calling Sprint and asking. They will not provide the code through email.
I can confirm that at least some changes in the Service Programming app will stick. I changed the banner, under the Display tab, to "Brick" (from Sprint), and it showed up in the Notification dropdown.
The NV util can read the values from the phone correctly.
QXDM can issue command to the phone.
ADB will not work. This limits the ability of tools like unrEVOked to do whatever they do. Getting ADB to work could be useful. Note that I did re-enable Debugging in the Setting->Applications menu to no avail. I believe this is a general side effect of this problem and perhaps a key symptom.
The bottom line is that I have run out of ideas. I have not found a setting in any of the QPST or QXDM tools that indicate this mode can be turned off. I have a hard time believing that there is some permanent switch in the Qualcomm SOC that says "always boot into this mode forever", but who knows.
Any suggestions would be great.
To summarize, I have installed a stock PC36IMG, update.zip, RUU. I have access to almost any setting in the phone, but cannot write to NV because it's in the S-ON state, which limits certain fastboot wipe options and the ability to push new images to system partitions from fastboot. I can, in theory, use the QPST Download software to move images if I can find one that might work.
When is the last time you tried running a 3.70 PC36IMG RUU?
I ran the 3.70 RUU literally minutes ago.
RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed
Apparently still not taking?
That's the thing - it *is* taking. Whatever is triggering this mode is not being reset by the RUU (or any other full clear/flash technique).
I have a dump of the NV memory, but I want to run through it with a hex editor to make sure it doesn't have anything that would identify my Sprint account or identity before posting it.
SLOSifl said:
That's the thing - it *is* taking. Whatever is triggering this mode is not being reset by the RUU (or any other full clear/flash technique).
I have a dump of the NV memory, but I want to run through it with a hex editor to make sure it doesn't have anything that would identify my Sprint account or identity before posting it.
Click to expand...
Click to collapse
Ah I see, and good precaution.
My ESN is in the qcn file, and I assume my MEID is as well. I will try to zero them out if I can find them all.
If my phone's ESN is 12345678, then it is in the qcn file as 78 56 34 12.
Does anyone else happen to have a known good QCN? Maybe I can compare them side by side to locate the differences. I suspect that there will be a lot of them, but I can eliminate most of them pretty easily.
While I work on the file (and debate whether or not it's safe to post), here is some information from the NV dump:
Code:
File Version: Major 2, Minor 0, Revision 0
File Summary:
Phone Model: 16 [FFA/SURF QSD8650 Rev 2.0], Configuration Name: default, Total NV Item Count: 1650
Phone Model 16 [FFA/SURF QSD8650 Rev 2.0] Configurations:
Configuration Name: default
Mobile Properties:
ESN: 0xMASKED
Phone Model: 16 [FFA/SURF QSD8650 Rev 2.0]
NV Major: 0
NV Minor: 0
SW Version: 8650B-SDCAPLYM-324026
Client Name: QPST Software Download 2.7.0.362
Code:
Feature Mask:
...Removed for brevity....
Total Set Bits: 108 of 432
Without bothering to specify all the set bits (although there are some interesting ones like "Bit 306: F_UI_GOOFY_MENU_BIT"), maybe someone can confirm that 108 or 432 is close to correct.
I loaded up a nv.img from a nandroid backup I took the day this problem happened (before flashing a ROM). I suspected that the nv.img and the qcn I just pulled should both represent the same general memory in the phone.
The image is...definitely an image. Exactly 640kb, tons of empty space and apparent padding. Much different in overall layout than the QCN, and no trace of my ESN. However, I was able to locate the GPS URLs in both files. While not even close to the same offset in the file, that small section of similarity indicates that the same memory was probably accessed.
Unfortunately I know of no way to push the nv.img to the phone in its current state. If I were able to get the nandroid backup's nv.img onto the phone I could at least eliminate the entire NV memory as a variable. If it fixes it, then awesome, and if it doesn't, then I can ignore the file entirely.
Here is the QCN file with my ESN removed. There may be other private information in the file, but at this point, Sprint is ordering me a new phone, and gave me this one back, so I don't know if they can really do anything about this.
http://rapidshare.com/files/455015717/public.qcn
My enthusiasm toward poking around this file is dropping off pretty quickly since I no longer believe this is where the problem lies.
I had the same thing happen to my EVO last week. Pretty much the exact same symptoms as you. I was able to get the RUU to run, and return my phone back to stock thinking this would fix the problem. I can boot into Sense, but the phone will shut off and do the 5 vibrate thing within a couple of minutes.
I took it into the Sprint store, and the rep told me there is nothing they would do and they would not replace my phone. He assumed it had been rooted (which it had, but I returned it 100% to stock before taking it in), but I have also read of this same thing happening on unrooted phones. I plan on calling Sprint and/or HTC directly to try and get the phone replaced.
From what I've read, it kind of sounds like this is a hardware failure. Possibly something in the internal memory or RAM. Of course, this is just mostly a guess I have. It seems this happens to unrooted phones, but is more common on rooted phones, possibly because of all the flashing we do.
Like I said, it's just a guess of mine, but it kind of makes sense. I wish I could be more help, and I'll definitely be following this thread because this seems to be a fairly common problem with EVOs and Incredibles that nobody has seemed to figure out yet.
hello,
the problem is heat.try to use your evo on the AC vent in your car with ac on you will not get reboot or eny shut down than try to use with out ac...
whenever internal temp goes more than 38C the evo goes off 5 vib. and flashig..
i spent long time testing this so i almost 100% sure that heat is the problem with my evo...
i dont know if there is a way to change the seting on shut down due to heat but it mey be...
adasio said:
hello,
the problem is heat.try to use your evo on the AC vent in your car with ac on you will not get reboot or eny shut down than try to use with out ac...
whenever internal temp goes more than 38C the evo goes off 5 vib. and flashig..
i spent long time testing this so i almost 100% sure that heat is the problem with my evo...
i dont know if there is a way to change the seting on shut down due to heat but it mey be...
Click to expand...
Click to collapse
I was never able to fix mine, but before getting it exchanged i let it sit all night with the battery out and would have the same results. So i know mine wasn't overheating.
strdrk1 said:
I was trying to root my phone using unrevoked 3.32 and during the install it, it stop with a back up CID error missing or something like that. i checked to see in hboot if it was rooted with it showing s-off, and it was but recovery still showed the regular triangle red error. So i restarted normally and tried into install terminal emulator on the phone and thats when it first started vibrating 5 times, then go blank with a green led flash. the phone will boot normally usually be able to use it for a min or less then it will repeat with the blank screens. After checking back into hboot it now shows that its unrooted with s-on. Now i also have problems with the usb/sdcard.
Things i have done to get it back to normal:
- hard reset using clear storage.
-Checking in the SD storage menu i could see it wasn't reading the SDCard so i restarted it in bootload and thru fastboot typed: fastboot oem enableqxdm 0.
- flash through bootloader this file : 3.70.651.1_PC36IMG.zip
After flashing it still takes multiple battery resets to finally get it through the first start up menu and then to the regular home screen. Seems to read the SDcard fine but when connecting the usb from wall charger or PC it doesn't recongnize at all.
The phone is 4 days old and seems to be back to stock except it still vibrates and goes blank with green led flash and it wont recognize charging/pc connection. Will i have any problem if i just go back to sprint and say i want a new one its not working right?
Phone info:
Baseband: 2.15.00.11.19
kernel: 2.6.32.17-gee557fd
Software: 3.20.651.1
PRI: 1.90_003
PRL: 60676
Hardware: 0003
HBOOT-2.10.0001
Click to expand...
Click to collapse
It's bricked. Happened to me when I tried to fix a problem with my phone not mounting the microSD card to any computer (got error message back on a Windows computer saying that the device wasn't recognized). You could probably try to flash the PC36IMG.zip file again from the bootloader, this time without all the addenda at the beginning (if you did that already, the nevermind).
My guess: pray that Sprint doesn't see any evidence of root. If you RUUed back already, they may not see it. You're probably in better position than I am, since the brick happened before I could RUU back with a PC36IMG file (and thus Sprint could see the root. At least Asurion doesn't seem to care about root, as long as I say nothing about it).
Hi, I have a problem with my defy and I really short to deal with that. First my defy stopped on red M logo and done proceed to system start. So I go to service menu, set clear cache- cache were cleared for 30mins so I take out batery, then I set - format/factory reset. same problem, it goes without end so after batery goes off, I make McGiver style for bring pnone to life and go to boot loader, run firmware flash over RSD lite and wait......after that RSD give me this message - Phone [0000] Error verifiing code group 33 Checksums. File:0x8BAC,Phone:0x4805 . RSD do nothing, on phone were instaling. after our when I suppose this is and I take out batery from phone and try run it. Every time start boot loader with message :
Code Corrupt
Battery OK
OK to Program
Conect USB
Data Cable
I cant launch android recovery, and If i flashed firmware again a have the same and. Can you please somebody help me with that??
Thanks,
ps. sorry for my english I think is not perfect
new thing, new error mesage from RSD. he pass Checksums errors, than give me message - restarting device ( that is not happend, device were still on), afted while there is new message : Failed flashing proces. Failed plashing proces. phone [0000] Error geting subscriber unit checksum. Device API error: 0xe003003F Command : (RQRCS 0xe403203f); phone conected
result FAIL
I am really desperate.. anyone have experience with this??
Thanks for any advice.
NoDi
As I see probably nobody had this issue like I had. Tomorrow I try bring phone to seller (Vodafone), and than I have to pray for reflashing it from them. Anywhere I will post result from them after I get some, If somebody have the same problem in future like I had.
NoDi
Difrent SFB
try usuing difrent sfb f.
have similar problem at some time...
just try using another sfb and do factory reset each time
yea.. some sbf have higher or lower on img version which might prevent your phone from fully flashed.
I tried various different FW from here. Everytime the same results. Today I was bring phone to Vodafone, I wonder on verdict
you said you tried all firmware versions, can you try diffrent RSD Lite version, may be RSD lite having problem. I am using " RSD Lite 4.9.msi ".
so phone is back. In report from service were Changed bad SWAP module. In used parts were 1pcs of RF board. Anyway I brought phone back to Vodafone because he cant sign in other than 3G network, and many places in our country are sill only 2G.
I have the E988 Taiwan model with stock 10b firmware. I have previously rooted, and used freegee to turn lge security off and install cwm. However, I have since reset back to stock using a kdz file. My problem is that my IMEI isn't showing up. This randomly hapened when my phone was off a few days ago. It means that I can't connect to the network and my phone is rebooting about every 20 minutes.
However, I have made an interesting discovert. My IMEI is still on the phone. I know this because I have twice managed to connect to the network after many reboots and my IMEI was read correctly in the log file when I reset back to stock.
I decided to root my phone (I have since unrooted) and found that the EFS files m9kefs1, m9kefs2 and m9kefs3 are all 0 bytes. So are all the other files in the folder. I even have backups of these files, and the file sizes update when I copy them in, but when I reboot the phone resets the file sizes back to 0 bytes.
Why is this happening?
On a side note, resetting your phone to stock doesn't actually seem to do anything as you are still required to do a factory reset. Surely all of the files should be deleted?
Thanks
jhb019
Please I really need your help.
My IMEI is definitely on the phone but for some reason the phone isn't reading it. Does anyone know why this is? Has anyone experienced this and managed to fix it?
Thanks
jhb019
So I hope this thread isn't too useless. I've been researching how to restore my imei after losing 4g signal when my phone randomly (just sitting there on the desk, not touching it), decided to get stuck in a reboot loop.
Here's my specs:
Network: AT&T
ROM: CyanogenMod 11-20141112-SNAPSHOT-M12-d2lte
Modem: UCUEMJB
Recovery: ClockworkMod 6.0.4.3
Device Model: SAMSUNG-SGH-I747
Product Code: Not Active
PDA Version:
Baseband Version: I747UCUEMJB
CSC Version:
Kernel Release: 3.4.104-cyanogenmod-g9f57632
Kernel Version: #1 SMP PREEMPT Tue Nov 11 22:15:56 PST 2014
ROM Build: d2uc-user 4.3 JSS15J I747UCUEMJB release-keys
Android Version: 4.4.4
BusyBox Version: 1.22.1
SU Binary Version: 2.40:SUPERSU
So here's what I've learned. My IMEI was lost due to a weird Samsung backup procedure that backed up my /efs folder with essentially a blank copy of important information. I have my IMEI, but writing it to the phone is very difficult. From this tutorial I learned to download QPST, and somewhere else I heard about EFS Professional.
So I tried to use EFS Professional first, and have been able to connect my phone (Had to install adb first via the official android sdk). I was able to make a backup of my efs folder. I was also able to change the usb settings to DIAG + MODEM + ADB. Then I launched the Qualcomm NV Tools. From there, by unchecking "Send SPC" and "Read Phone" I was able to connect to the phone, but any other button I pressed didn't accomplish anything except disconnecting the phone again.
This is when I turned to QPST. I knew from EFS Professional which COM port my phone was using each time, and I added the COM ports to the QPST Configuration program for listening. But my phone was never listed as available in the ports tab, nor was it listed in my device manager under COM ports. I tried using the RF NV Item Manager anyway, entering in my IMEI "backwards" with an 8 in the first line and an "a" after the first real number in my IMEI, but my phone was never really connected, so of course nothing happened.
I learned this was probably because I have no IOTHiddenMenu / Qualcomm USB Settings Menu / whatever you want to call it with USSD codes, because I'm using an AOSP ROM (Cyanogenmod). This thread and this thread were useless in enabling DIAG mode, because of broken links and scripts that no longer work on newer versions of CM.
My next plan is to change ROMs to a TouchWiz ROM, but I haven't found a good one yet, especially considering I've upgraded my bootloader and I know that if I flash a ROM with a downgraded bootloader, I'll definitely brick my phone. So is there a ROM I can use with an upgraded bootloader that won't brick my phone and will allow me to enter DIAG mode so that I can connect to QPST via a COM Port, use the RF NV Item Manager, and put in my old IMEI? Or am I just going about this all wrong?
You do have to be on a TW ROM with a stock dialer for ussd codes to work. Based on everything you posted you should be on the mjb boot loader, but confirm that first. Enter this into a terminal or adb shell:
Code:
getprop ro.bootloader
If you are on an mjb bootloader, then this ROM should work for you http://forum.xda-developers.com/showpost.php?p=47816011&postcount=18. It's a rooted deknoxed at&t stock mjb.
Good luck.
---------- Post added at 12:04 PM ---------- Previous post was at 11:57 AM ----------
You probably already discovered this in your research, but just in case. When you get your imei problem solved, before flashing something other than a TW ROM, enter this in a terminal or adb shell:
Code:
su
reboot nvbackup
That will fix Samsung's whoops and give you a working efs backup partition instead of a blank one.
Thanks! I'll try this and get back.
alexalexalex09 said:
Thanks! I'll try this and get back.
Click to expand...
Click to collapse
You were right about the bootloader - when I looked up the ro.bootloader property, it spit back what I thought was my modem identifier, I747UCUEMJB - so yes, MJB. I'll get a chance to flash the new ROM tomorrow or the next day and see how it goes.
So, two steps forward and three steps back. I did install the new ROM. Initially, it appeared to work, because I was able to dial *#7284# to access the service mode menu and change UART to MODEM, and then dial *#0808# to access the USB Settings menu and change that to RMNET+DM+MODEM. After that, the phone showed up under COM5 in the Device Manager. I opened up QPST Configuration and added COM5 (labelled it "COM5") under ports. However, the phone never showed up (Phone column read "No Phone").
I then tried EFS Professional, but it was unable to detect the phone. I opened up the command line and tried an adb shell, but it didn't connect. Of course, the phone was in RMNET+DM+MODEM mode, not and ADB mode. I then went back into USB settings, changed it to DM+MODEM+ADB, and reconnected the phone. The phone wasn't detected by the computer, and hasn't been since.
I've restarted the phone and the computer multiple times (Windows 7 32 bit), uninstalled the phone drivers, reinstalled them in two different versions, uninstalled and reinstalled QPST (removing the relevant registry entries in between installs), and went through a number of combinations of settings on the phone. I tried with UART set to MODEM and PDA, with USB settings set to DM+MODEM+ADB, RMNET+DM+MODEM, MTP, and MTP+ADB. I made sure superuser was installed correctly and that developer mode was enabled. I still have not gotten the phone to charge in that USB port or show up in Device Manager in any way, even though the USB port on the computer still functions (can access flash drives from it). I plan to do some more googling and troubleshooting about this, but I haven't had the time to yet. On Wednesday I'll hopefully have a minute to try using my work laptop to access the phone. I think once I get the phone to be recognized via USB again I'll be able to have QPST Configuration recognize it, then I'll be able to use that RF NV Item Manager to enter in the new IMEI.
Also, in potentially unrelated news, my install of Titanium Backup is unable to recognize any apps I backed up, even ones that have been previously restored. It sees them in the backup folder (backup folder location says this folder contains 52 backups), but no apps wee listed in the backup/restore tab. Maybe this has something to do with the mount namespace separation setting in SuperSU? I'll test that later.
Some newer ROMs will install but not give you cell service without the newest bootloader and modem.
Try flashing the last release of CM11. I would not touch the bootloader, modem, or EFS folder until you try an older ROM.
audit13 said:
Some newer ROMs will install but not give you cell service without the newest bootloader and modem.
Try flashing the last release of CM11. I would not touch the bootloader, modem, or EFS folder until you try an older ROM.
Click to expand...
Click to collapse
Thanks for chiming in, but I don't understand how this applies. I was on CM11 when my IMEI was removed. When you lose your IMEI, the main symptom is that you can't connect to 4g anymore, and you're stuck on EDGE, which is what happened in my case. I can in fact make calls and send texts, and even load web pages without wifi. It's just slow and prone to call dropping.
As for your advice to install an older ROM, I just flashed a stock ROM, the one linked above. It didn't cause my current lack of USB connection, because I had a USB connection for a while until I changed the UART and USB settings.
I definitely will not touch the bootloader - I've been warned about the dangers of downgrading from an MJB bootloader. I'm not sure what you mean by not touching the modem, but I'm going to assume it's as scary/difficult as the bootloader, so I'll be sure to stay away from changing that too.
As far as not touching the EFS folder, as far as I see it, that's my only way out of this hole, because my end goal is to replace the IMEI that I randomly lost last week, and that's part of the EFS folder in some way that hasn't been explained to me (although I know it has to do with NV settings, maybe some file called nvdata.bin that I've never found, or the /EFS/IMEI folder?). So I think I have to ignore that bit of advice, unless you can give me a good reason to change my goal in all this.
alexalexalex09 said:
As far as not touching the EFS folder, as far as I see it, that's my only way out of this hole, because my end goal is to replace the IMEI that I randomly lost last week, and that's part of the EFS folder in some way that hasn't been explained to me (although I know it has to do with NV settings, maybe some file called nvdata.bin that I've never found, or the /EFS/IMEI folder?). So I think I have to ignore that bit of advice, unless you can give me a good reason to change my goal in all this.
Click to expand...
Click to collapse
I should note that I took a look at my EFS folder while writing this last post, and it's completely empty now. So that's fun.
I suggested flashing back to an older ROM because you made some changes since your original post.
I suggested not touching the bootloader, modem, and EFS because flashing an incompatible bootloader/modem combination can hard brick the phone.
Since your bootloader and modem match, I'm out of suggestions other than perhaps visiting a repair shop to have it fixed.
audit13 said:
I suggested flashing back to an older ROM because you made some changes since your original post.
I suggested not touching the bootloader, modem, and EFS because flashing an incompatible bootloader/modem combination can hard brick the phone.
Since your bootloader and modem match, I'm out of suggestions other than perhaps visiting a repair shop to have it fixed.
Click to expand...
Click to collapse
Thanks for the clarifications. I did visit a shop to see if they could fix it, and all I got were blank stares and people who don't want to deal with IMEI repairs. So back to my own attempts! I realized a couple days ago that my problem in connecting to the computer is that I've developed a crack on my phone's USB port. Also, I think my home desktop's messed up. So with a nice, sturdy cable I installed all the necessary program on my work laptop (Samsung Drivers, ADB, ES Professional, and QPST just for fun). I tried ES Professional first and by using the Qualcomm NV tools I was able to restore my IMEI! I rebooted the phone and now by dialing *#06# I see my IMEI followed by "/ 17".
So now onto the next problem: Still no 4g signal. Under Connections > More Networks > Mobile Networks, there are some errors. I only have one APN, named "ATT Phone" with an APN of "phone" and an MMSC of mmsc.mobile.att.net, and under network operator it simply says "Default Setup". Some research later, I realized this is a common problem, and I guess it has to do with my NV Data being messed up. Obviously, item 550 (0x226) is correct, which I was able to verify using a program called NV-items-reader-writer, but something else is screwed up. Peoplearmy has released a tool that can restore a backup up QCN file, which of course I don't have, so I'm in the process of seeking help from a generous soul who has an app that might help me. Apparently I could also use someone else's NV Items backup, replacing their IMEI with my own. But, I don't have one, so I'm stuck waiting on someone to be nice to me
I did try the method posted here: http://forum.xda-developers.com/showthread.php?t=1808408&page=16
But it didn't work. This thread and this thread and this thread were helpful to me for research.
alexalexalex09 said:
Thanks for the clarifications. I did visit a shop to see if they could fix it, and all I got were blank stares and people who don't want to deal with IMEI repairs. So back to my own attempts! I realized a couple days ago that my problem in connecting to the computer is that I've developed a crack on my phone's USB port. Also, I think my home desktop's messed up. So with a nice, sturdy cable I installed all the necessary program on my work laptop (Samsung Drivers, ADB, ES Professional, and QPST just for fun). I tried ES Professional first and by using the Qualcomm NV tools I was able to restore my IMEI! I rebooted the phone and now by dialing *#06# I see my IMEI followed by "/ 17".
So now onto the next problem: Still no 4g signal. Under Connections > More Networks > Mobile Networks, there are some errors. I only have one APN, named "ATT Phone" with an APN of "phone" and an MMSC of mmsc.mobile.att.net, and under network operator it simply says "Default Setup". Some research later, I realized this is a common problem, and I guess it has to do with my NV Data being messed up. Obviously, item 550 (0x226) is correct, which I was able to verify using a program called NV-items-reader-writer, but something else is screwed up. Peoplearmy has released a tool that can restore a backup up QCN file, which of course I don't have, so I'm in the process of seeking help from a generous soul who has an app that might help me. Apparently I could also use someone else's NV Items backup, replacing their IMEI with my own. But, I don't have one, so I'm stuck waiting on someone to be nice to me
I did try the method posted here: http://forum.xda-developers.com/showthread.php?t=1808408&page=16
But it didn't work. This thread and this thread and this thread were helpful to me for research.
Click to expand...
Click to collapse
I got it! Problem solved!!
So what I realized after going back over those research threads quickly was that I was using Peoplearmy's QCN generator incorrectly. Here's how I fixed it.
1. Opened QPST, followed directions here to connect my phone and start up QPST Software Download.
2. Having already injected my IMEI, I used the backup tab to make a backup.
3. I opened Peoplearmy's SG3QCNGenerator and imported the QCN file that QPST just created. I left "inject IMEI" unchecked, since I already had my original IMEI. I clicked Save As to set the directory and name of the new file, and clicked the Verify IMEI button that appeared to verify that it was correct.
This was the step I had missed - because I never had a valid QCN file to import, I never was able to create a new QCN file. My error in thinking was that, since my current QCN file was obviously messed up, I couldn't use it to make a new QCN file, but that's the whole point of this software.
4. Once I had the new QCN file, I went back to QPST's Software Download program and used the Restore tab. The QCN file generated by Peoplearmy's tool didn't match my model number, but I approved it anyway. It restored the QCN file correctly, but it had an error when it tried to reset the phone.
5. I rebooted the phone manually, and I now have 4G signal!
So, to summarize the difficulties I had:
1. I didn't make an nvbackup before I flashed CM a year ago, and it didn't hurt me until now.
2. I lost my IMEI and couldn't restore it because 1) I was on CM, which stopped me from putting my phone in DM + MODEM + ADB mode and 2) The computer/cable I was using to work on my phone, for whatever reason, were being stupid.
3. I didn't understand that in order to fix my phone I needed to restore my IMEI and repair my nv items (.qcn file)
4. I didn't realize that I could use Peoplearmy's tool to take a messed up nv items qcn file, fix it, and restore it to my phone.
All the tools I ended up needing: Samsung Drivers, ADB, ES Professional, QPST, and Peoplearmy's SG3 Data Restorer. Hope this helps someone else out there.
:good: thanks for posting fix.
"all i can really do , is stay out of my own way and let the will of heaven be done"
Great job. Thanks for posting your solution back here so others can find it.
So i got one of these vs985s. and nothing. screen lit up but nothing else.
so i had a unknown or damaged usb device .long story short
got it in 9008 i follow all the guides emmc and ap test past.
but when i to the sd ram test i get a error of
========DDR TEST START
Test level = 0(check data/address line)
sbl1 partition write FAIL.. senctor 0x28000
WRITE FAIL During ddr test..
Aborted..........
Also everytime i click a restore boot image in any version of board diag tool whatever partition im trying to restore write fails....
Now i remeber back on my g2 i got the 9006 mode i was able to zero all the partitions in linux when it mounted 30 somthin drives.
Is there any info any one could give me as i have followed all the guides.. But might be missing something somewhere.
any help is greatly appreiciated
I have the exact same problem here with my father in law's D852. The phone was never rooted. I was trying to unbrick it but it didn't reboot after flashing sbl1. So I decided to try a stock rom form another source and that's when this happened. Trying to go back to the first rom didn't work, even after erasing the entire emmc. My guess is somehow, we activated permanent paper weight mode. I hope someone more qualified than us can help us, or at least confirm our phones are good for recycling...