Related
Hello,
I was recently trying to load a stock rom on my LG540 and the process was interrupted because of a power failure. But the phone luckily booted into "download mode". I want to reflash using the procedures discussed in various posts on bricked phones, but my computer can no longer recognize the phone. The KDZ updater reports "Phone not Found". The correct drivers are installed and I am running windows 7 home edition.
Any thoughts as to how to get the computer recognize the phone?
Thanks, MN
maybe using "Run as administrator"
Try installing these drivers, they helped me when I first used KDZ. The links are from a hungarian site.
http://www.4shared.com/file/Zx52g1kl/Optimus_GT540_pc_sync.html
I think the bootloader is corrupted, it's basically "bricked", but not fully
Drivers must be the issue. Try uninstalling LG driver, reinstall it or use Windows Update to install drivers.
Bricked GT540
Maybe you can use LGDP2 ??
Okay so i did something i shouldn't of.
After buying a T-mobile dell streak 7 online, i found out it had been rooted with clockwork recovery mod by dj steve v4.0.1.4. When i tried working with it i found out i couldn't use the phone functions of the tablet so i decided to do a factory reset in the settings. To my dismay the problem only got worse and now when the tablet boots up normally it asks me for a password that wasn't on there before. I read on a thread somewhere that this is because the device is trying to decrypt something but that it's because there's no OS on it. I can still boot up in recovery mode and perform all the options in there.
So i bought a usb cable for it hoping that i would be able to flash it back to factory settings, but now i am unable to get it to work with usb.
I have a win 7 64 bit and i have tried downloading divers from all kinds of places which seem to be the right ones but windows will not allow me to install them and insists that the best ones are installed.
I've downloaded android sdk tools and installed all the components that are pertinent to this version and make (at least i think)
I've tried downloading PDAnet, the pc sync tool that is available on the dell site and that didn't work either. Under fastboot mode on the tablet the driver is installed correctly but still appears as a unknow device and i don't see the fastboot window show up when i plug it in so...
I've literally read hundreds of threads to see if maybe i could do it by placing update.zip files on the sd card and then installing them under CWM, some have worked, some haven't but when i reboot it's still the same.
Please help!!!
timaloud said:
Okay so i did something i shouldn't of.
After buying a T-mobile dell streak 7 online, i found out it had been rooted with clockwork recovery mod by dj steve v4.0.1.4. When i tried working with it i found out i couldn't use the phone functions of the tablet so i decided to do a factory reset in the settings. To my dismay the problem only got worse and now when the tablet boots up normally it asks me for a password that wasn't on there before. I read on a thread somewhere that this is because the device is trying to decrypt something but that it's because there's no OS on it. I can still boot up in recovery mode and perform all the options in there.
So i bought a usb cable for it hoping that i would be able to flash it back to factory settings, but now i am unable to get it to work with usb.
I have a win 7 64 bit and i have tried downloading divers from all kinds of places which seem to be the right ones but windows will not allow me to install them and insists that the best ones are installed.
I've downloaded android sdk tools and installed all the components that are pertinent to this version and make (at least i think)
I've tried downloading PDAnet, the pc sync tool that is available on the dell site and that didn't work either. Under fastboot mode on the tablet the driver is installed correctly but still appears as a unknow device and i don't see the fastboot window show up when i plug it in so...
I've literally read hundreds of threads to see if maybe i could do it by placing update.zip files on the sd card and then installing them under CWM, some have worked, some haven't but when i reboot it's still the same.
Please help!!!
Click to expand...
Click to collapse
You need to grab a NVFLash pack, put device in APX mode, install the APX drivers, and install a complete full restore.
reply
giveen said:
You need to grab a NVFLash pack, put device in APX mode, install the APX drivers, and install a complete full restore.
Click to expand...
Click to collapse
Thank you so much for taking your time to help.
Ok so i downloaded NVFlash, that i have found to be able to put my device in APX mode i need to hold down the power button and the volume - button at the same time when booting up but that sends me to fastboot. Is this the same as APX ? Sorry i don't know much about this.
Also when you say install the APX drivers, i have not been able to find these, could you send me a link ?
I don't mean to be rude or mean, but this is a question that has been answered a hundred times here, please look around and read a bit, we are getting tired of holding baby hands.
Thanks for your imput
giveen said:
I don't mean to be rude or mean, but this is a question that has been answered a hundred times here, please look around and read a bit, we are getting tired of holding baby hands.
Click to expand...
Click to collapse
Hey! Thank you for answering. Please don't be too quick to pass judgement, I have read hundreds of threads and i have downloaded all kinds of different drivers, roms, and recovery images. I've followed all the instructions of the related posts but the Tablet's OS wont boot up. I cannot install any .pkg updates because any option i select when i boot it up holding down power and volume + buttons sends me to CWM recovery mod and all the update.zip roms that i have installed this way have made no difference.
I have come to the conclusion that i need to flash a recovery image from the computer but i cannot because all the drivers i have found for it have not worked. My device does not appear as a drive therefore i can't see it in nvflash or even windows for that matter. yesterday i called dell support to see if they had any drivers available that weren't already posted on their site but with no luck.
The reason i'm writing this is because i was hoping someone had a similar problem and could help me, i know you deal with people that don't even take the trouble to look into the other threads every day, but believe me i have.
If you can help i would greatly appreciate it, or point me to what i'm doing wrong Tks.
In NVflash or APX mode the S7 doesn't appear as a drive. With your S7 on plugged into your PC, you don't see it as a drive? This should work right out of the box. Although some have reported the manual mentioned Driver. Zip folder is missing.
If hold the Volume + and - button in a plug into your PC, do your hear a beep? If so, you would then go into the device manager, select the APX device and install the drivars from the NVflash download package.
These videos posted by "giveen" may help as well: http://www.youtube.com/playlist?list=PLB99FAE280F618B12
awesome
wptski said:
In NVflash or APX mode the S7 doesn't appear as a drive. With your S7 on plugged into your PC, you don't see it as a drive? This should work right out of the box. Although some have reported the manual mentioned Driver. Zip folder is missing.
If hold the Volume + and - button in a plug into your PC, do your hear a beep? If so, you would then go into the device manager, select the APX device and install the drivars from the NVflash download package.
These videos posted by "giveen" may help as well:
Thank you so much, i was finally able to install the drivers in APX mode. Flashing it from here shouldn't be too much of a hassle. Very grateful for your help. Cheers
Click to expand...
Click to collapse
Hello ned help..
rm-1030 flashing rom 2.1.0.12 complete Done
i have two version
RM1013_059V788_2.1.0.12 and
RM1013_059V786_2.1.0.12 but still dead..
Usb detect as emerency connectivity
when im flash using rom rm1013_2.1.0.13_059V78 always stuck at rm1013_2.1.0.13_user_NON-HLOS.bin
and shown error dialog "failed using firehouse protocol"
need help..
ive try to redownload ROM.. but keep error
im sorry i cant upload picture coz need 10 posts but im using txt file
maybe the firmware you downloaded is corrupted.. where did you downloaded your firmware files? I use navifirm+ but yesterday I'm trying to redownload a rom but navifirm+ seems to be not working any more..
thaks for replay,
iv downloaded from Package Majnager .. and from this seidea.com/tag/rm-1013-2-1-0-13/
its still blank screen and just detect "emerency connecivity
first download nokia-x2-tools.v.1.2.en.exe, from the tool install drivers.. then go to your "C:\ProgramData\Nokia\Packages\Products\RM-XXX" and delete all files or move it somewhere if you don't want to delete.. and replace everything with the files that you downloaded.. and run "Lunch Nokia Care Suite" as administrator.. and flash your firmware..
thaks...
I thinks its hardware problem.. coz i have 5 different firmware and already used maximal method
change folder.. remove.. redownload.. and anythink
and my phone cant detect fastboot or recovery
btw thaks
aw.. that's too bad.. I fixed my completely dead x2 with that method though.. it has no fastboot and undetected adb but I recover it somehow, I think it's just a luck..
I have exactly same problem havent found solution yet.
I have same problem too
arisjb said:
hello ned help..
Rm-1030 flashing rom 2.1.0.12 complete done
i have two version
rm1013_059v788_2.1.0.12 and
rm1013_059v786_2.1.0.12 but still dead..
Usb detect as emerency connectivity
when im flash using rom rm1013_2.1.0.13_059v78 always stuck at rm1013_2.1.0.13_user_non-hlos.bin
and shown error dialog "failed using firehouse protocol"
need help..
Ive try to redownload rom.. But keep error
im sorry i cant upload picture coz need 10 posts but im using txt file
Click to expand...
Click to collapse
Remove battery from device atleast 1min
Insert battery
Start device in bootloop and if not start only connect to PC
Start Nokia care suite >product software > open product> select device and flash
jepr0x1011 said:
aw.. that's too bad.. I fixed my completely dead x2 with that method though.. it has no fastboot and undetected adb but I recover it somehow, I think it's just a luck..
Click to expand...
Click to collapse
My Nokia X2 had also give completely dead. I tried to Flash stock ROM in it via Nokia care suite and which I've even done previously however this time my phone had gone completely blank and does not even go to recovery mode. It has gone completely unresponsive. Please help me on this.
Hello everyone,
I have a Lumia 1320, which, until yesterday, was running fine on Windows Phone 8.1, which is the last OS update for it. On seeing the recent release of WP Internals 2.3, I decided to tinker with the phone to see if I could get Windows 10 Mobile on it.
Following the standard procedure (downloading FFU, HEX and MBN files and proceeding in Flash mode), I successfully unlocked the bootloader of the phone. However, things went south when I proceeded with enabling Mass-Storage mode for the phone.
When the phone was connected to PC and I chose the option to enable Mass Storage mode from WP Internals, the USB cable somehow got a little loose and the process was interrupted. And just like that, the phone was gone!
The 1320 is bricked now. It's not recognized by the PC, WDRT or WP Internals. No vibration, no Nokia logo, nothing. What's worse is that the phone's power button is broken (in a way that can't be fixed) so I can't even hard reset it.
Is there any way to recover the phone and get Windows 10 Mobile (or at least, Windows Phone 8.1) on it? Any help would be immensely appreciated.
Thanks in advance!
Did you try Lumia Software Recovery Tool? Some years ago i had problem nearly the same. Probaby that program helped me, i am not sure but you can try.
A side note: Mass storage cannot be enabled on x2x devices without the proper SBL3 img file. Were you using one (SBL3) at that time?
For your phone will it be seen as QDLoader 9008? If so use the emergency download instructions for that mode found in the forums to try to recover it.
I had my 1320 (RM-995) bricked for the longest time after flashing an RM-994 ffu until gus33000 shared a full zip of all the lumia payloads. I found a hex file in there that finally worked on my device.
nate0 said:
A side note: Mass storage cannot be enabled on x2x devices without the proper SBL3 img file. Were you using one (SBL3) at that time?
For your phone will it be seen as QDLoader 9008? If so use the emergency download instructions for that mode found in the forums to try to recover it.
I had my 1320 (RM-995) bricked for the longest time after flashing an RM-994 ffu until gus33000 shared a full zip of all the lumia payloads. I found a hex file in there that finally worked on my device.
Click to expand...
Click to collapse
Hello, do you still have the SBL3 image file of Lumia1320? I need it very much, thanks.
Missoula19 said:
Hello, do you still have the SBL3 image file of Lumia1320? I need it very much, thanks.
Click to expand...
Click to collapse
I never had an sbl3 img for the 1320 only the sbl3 files for
-Lumia-1020
-Lumia-520.
-Lumia-620.
-Lumia-625.
-Lumia-810.
-Lumia-820.
-Lumia-822.
-Lumia-920.
-Lumia-925.
nate0 said:
I never had an sbl3 img for the 1320 only the sbl3 files for
-Lumia-1020
-Lumia-520.
-Lumia-620.
-Lumia-625.
-Lumia-810.
-Lumia-820.
-Lumia-822.
-Lumia-920.
-Lumia-925.
Click to expand...
Click to collapse
So, can the Lumia 1320 use the 1020's sbl3 file? I see both of them are the same soc.
Hello,
I have a somewhat aged Idol 4 lying here.
This no longer boots or it hangs in the boot loop.
So I tried to install an update via a stock rom from the network via the recovery menu and ADB sideload and always got the error status 7. (Alcatel_Idol_4_6055K_01001_01002_OTA)
Resetting the system didn't help here either.
Then I tried to install TWRP on the device.
But unfortunately both methods that I tried failed.
Once via Sahara & firehose-test and the second was Suger QCT via the download mode.
But both of them got the error message NPRG Error 5002.
I have installed suitable USB drivers.
So my question, does anyone have a tip for me on how I could get the device revived?
And Sorry for my bad english
Hm.. said:
Hello,
I have a somewhat aged Idol 4 lying here.
This no longer boots or it hangs in the boot loop.
So I tried to install an update via a stock rom from the network via the recovery menu and ADB sideload and always got the error status 7. (Alcatel_Idol_4_6055K_01001_01002_OTA)
Resetting the system didn't help here either.
Then I tried to install TWRP on the device.
But unfortunately both methods that I tried failed.
Once via Sahara & firehose-test and the second was Suger QCT via the download mode.
But both of them got the error message NPRG Error 5002.
I have installed suitable USB drivers.
So my question, does anyone have a tip for me on how I could get the device revived?
And Sorry for my bad english
Click to expand...
Click to collapse
Hello, I deleted my system from twr without realizing what I was doing, the result is that I stay on the Alcatel logo. My steps were, the installation of sugar, when it starts not to update the application. Choose the 6055 model, since the 6055P model that is mine does not appear in the drop-down. Before starting sugar, turn off the mobile completely and connect it off to the usb of the pc, check if when connecting it the pc does not detect it, use another cable (there are many cables that only serve to charge and not to read on the pc) Now start sugar, choose the model and click on the Udgrade tab. You will surely get several messages saying that the mobile has been modified and that you lose the guarantee, go ahead accepting the message, in a few minutes you will have it ready. Greetings.
Perdigon55 said:
Hello, I deleted my system from twr without realizing what I was doing, the result is that I stay on the Alcatel logo. My steps were, the installation of sugar, when it starts not to update the application. Choose the 6055 model, since the 6055P model that is mine does not appear in the drop-down. Before starting sugar, turn off the mobile completely and connect it off to the usb of the pc, check if when connecting it the pc does not detect it, use another cable (there are many cables that only serve to charge and not to read on the pc) Now start sugar, choose the model and click on the Udgrade tab. You will surely get several messages saying that the mobile has been modified and that you lose the guarantee, go ahead accepting the message, in a few minutes you will have it ready. Greetings.
Click to expand...
Click to collapse
Hello, thanks for the answer and the download.
I've tried the same way. I still downloaded your file and tried as you described.
Unfortunately I got the same error NPRG Error 5002 again.
Unfortunately I have no idea where the problem could be.
I found out that it could be a memory error.
As if a flash process had failed and there is no longer a correct series of partitions.
So I would need a complete original rom and would have to flash it via fastboot.
I could also try it via twrp, but I don't get this flashed.
And I don't have a complete original rom either.
Hello,
So I have now been able to flash the phone with another PC with Sugar QCT after it suddenly started up after the battery was completely empty and I charged it again.
But unfortunately the boot problem persists after turning off the phone again.
Even after replacing the battery with a new one.
Then I tried to flash TWRP via the Alcatel Flasher.
The flash process was successful but there was no TWRP on it after the reboot.
So the problem could still be somewhere else than just the firmware.
Hm.. said:
Hello,
So I have now been able to flash the phone with another PC with Sugar QCT after it suddenly started up after the battery was completely empty and I charged it again.
But unfortunately the boot problem persists after turning off the phone again.
Even after replacing the battery with a new one.
Then I tried to flash TWRP via the Alcatel Flasher.
The flash process was successful but there was no TWRP on it after the reboot.
So the problem could still be somewhere else than just the firmware.
Click to expand...
Click to collapse
Hello, it may be that you are making the same mistake that I made when installing recoveri. When selecting the recovery, note that the twr is the one that weighs about 14 mb and the original one about 24 mb. I think that when you make a copy with the recovery program and then install the twr you select it wrong. In the program, do not make the copy of the recovery, skip that step and go directly to install and select the 14 mb file. You will see that this is the problem. Cheers