Related
Hi,
I tried flashing a ROM with Odin to my I9000 today, and in the middle of flashing I received an error message. Once I tried to start it I got a weird logo on my screen with a yellow exclamation mark. Managed to enter Download mode again though.
Once I disconnected the device and tried to connect it again in Download mode, my PC stopped recognizing it - I got "USB Device not recognized" and can't use Odin to flash anymore.
I tried Heimdall on OSX as well but it didn't work either.
Is this fixable ?
Thanks,
George
At which phase did the flashing stopped? Uninstall and reinstall the drivers again.
Since your phone boots to download mode, it's absolutely fixable, so chill!
I've been through this before, and this method worked.
1. Reboot PC.
2. Clear /temp folder on PC.
3. Boot phone into download mode.
4. Connect to PC, so that ur PC recognizes your device.
5. Switch off phone.
6. Set up Odin with all the files assigned like PDA, modem and csc.
*I suggest re-partitioning using 512.pit file
7. Boot phone to download, connect to PC, hit start on Odin.
Done
#if device is still unrecognized, reinstall drivers.
Let me know if it helped.
Sent from my GT-I9000 using Tapatalk 2
Hi,
I followed your instructions & I tried a different set of drivers but I still get Windows cannot recognize your device error.
The error occurred in Odin while flashing the main image (the big file).
Are you sure that as long as I can get to Download Mode I can still recover from this ?
Thanks,
George
Try removing the SIM and/or SDcard before reflashing again with ODIN.
It's a solution I found on the forums that saved my I9000 before.
The problem is that I can't even get to the stage where I'm able to flash anything. No PC/Mac will recognize my device.
georgehdd said:
The problem is that I can't even get to the stage where I'm able to flash anything. No PC/Mac will recognize my device.
Click to expand...
Click to collapse
I have the exact same problem, this seems like a lot more ppl are having it too, I still cant fix mine yet, tried all kinds if methods , my 3 different pc with different. cables still won't reconize my i9000
Sent from my Dell Streak using XDA
Well, I know this may sound weird..
1. Reinstall drivers
2. Detach battery and keep phone that way for 5-6 hour. (I dunno why, but this worked with me!)
3. IMPORTANT DON'T SKIP: clear all temporary files on your PC.
4. MOST IMPORTANT: reboot download and simply "connect" to PC with no other applications running. This time, your PC should recognize your device.
5. Turn off your phone, reboot your PC, again clear temporary files.
6. Start Odin, assign files to respective fields, check repartition. NOW CONNECT THE PHONE TO PC IN DOWNLOAD MODE.
7. After Odin recognizes (that block goes yellow), wait for a minute, start.
##Please follow all the steps do not skip any.
It should 99% fix your phone, if it doesn't, service centers will be happy to help.
Sent from my GT-I9000 using Tapatalk 2
jay_ingale said:
Well, I know this may sound weird..
1. Reinstall drivers
2. Detach battery and keep phone that way for 5-6 hour. (I dunno why, but this worked with me!)
3. IMPORTANT DON'T SKIP: clear all temporary files on your PC.
4. MOST IMPORTANT: reboot download and simply "connect" to PC with no other applications running. This time, your PC should recognize your device.
5. Turn off your phone, reboot your PC, again clear temporary files.
6. Start Odin, assign files to respective fields, check repartition. NOW CONNECT THE PHONE TO PC IN DOWNLOAD MODE.
7. After Odin recognizes (that block goes yellow), wait for a minute, start.
##Please follow all the steps do not skip any.
It should 99% fix your phone, if it doesn't, service centers will be happy to help.
Sent from my GT-I9000 using Tapatalk 2
Click to expand...
Click to collapse
Following these steps, try also to remove SIM and SD card before connecting to the PC
I followed all the steps but windows still see the phone as unknown device and that odin of course does not detect the phone either...also have used the samsung usb driver dated june 2012 from xda here..anyother suggestions ?
Sent from my Dell Streak using XDA
I got a Galaxy Nexus and it happened the same. Any solution for that?
thangbithit said:
I got a Galaxy Nexus and it happened the same. Any solution for that?
Click to expand...
Click to collapse
If you can get in download mode, you can be helped..
Just seek help in galaxy nexus forum, as that will be more helpful..
Sent from somewhere...
Hi guys, got a slight problem with entering fastboot mode. I hold the volume-up key and connect me USB cable but rather than getting the noise verifying it's been connected ok, I get that dull sound it makes when it hasn't worked. It won't even let me install the drivers and in device manager it comes up as "S1boot Fastboot" for a few seconds before then going into battery charging mode. I downloaded the Android SDK latest and replaced the USB driver INF file with the one sony give you but it didn't work so reversed back to the other driver the SDK manager installs and that didn't work either.
I've been through the tutorials and even tried to update the driver in device manager in the few seconds it stays there but that didn't work either! USB debugging is enabled too!
Please help, I'm not a noob and have done fastboot booting before and yes for those who may ask have already checked to make sure the bootloader can be unlocked and yes it can also the phone is NOT branded and is unlocked to all networks.
Any help will be appreciated, thanks!
Dave.
Are you on Windows 8? Using USB 3.0?
"As your flesh bears the sigil....your name is that....of a recusant."
First be sure you're using a 2.0 usb port, if this is ok maybe it's a windows 8 driver problem, so you should try this http://forum.xda-developers.com/showthread.php?t=2170114. It works for me
For also fastboot and flashmode come for 5 Sec. So Make sure you prepare the file and attach the device to fastboot or flashmode when it is asked.
Still problems
I'm still working on a 2012 laptop with Windows 7 Premium installed. It's fully up to date and all the drivers are installed properly I just don't get it, I've tried everything and it's still making the noise as if it won't connect. I don't know what to do to be honest. Also yes it is USB 2.0.
darkdemon32 said:
I'm still working on a 2012 laptop with Windows 7 Premium installed. It's fully up to date and all the drivers are installed properly I just don't get it, I've tried everything and it's still making the noise as if it won't connect. I don't know what to do to be honest. Also yes it is USB 2.0.
Click to expand...
Click to collapse
Hmm...how many USB ports are being used when you're flashing the phone?
"你看到了没? 爱让我流胆怯的泪..."
"Have you seen it? Love has made me cry cowardly tears..."
Fastboot with Xperia XP
I have the same problem, can't get it to fastboot mode.
Tried the Windows 8 zith USB 2, and also on XP machine where I was succesfully used it for a Xperia U.
Dump Windows..
Opensource rules!!! I switch on a VM with Windows only when I need Photohshop. Otw, Ubuntu and openSUSE FTW!!
sarkar1990 said:
Dump Windows..
Opensource rules!!! I switch on a VM with Windows only when I need Photohshop. Otw, Ubuntu and openSUSE FTW!!
Click to expand...
Click to collapse
Opensource forever)))
Sent from my ME371MG using xda app-developers app
same problem...
m having same kind of problem i was trying to flash boot img from cm 11 but fast boot isnt recognizing my device any more.my sp is rooted bootloader unlocked.fast boot was recognizing it yesterday.please tell me what to do
What I did was use a Windows XP machine.
Couldn't get it to work on my Windows 7/8, because of the restrictions in driver signatures.
Sent from my C5303 using Tapatalk
fastboot
darkdemon32 said:
Hi guys, got a slight problem with entering fastboot mode. I hold the volume-up key and connect me USB cable but rather than getting the noise verifying it's been connected ok, I get that dull sound it makes when it hasn't worked. It won't even let me install the drivers and in device manager it comes up as "S1boot Fastboot" for a few seconds before then going into battery charging mode. .
Click to expand...
Click to collapse
I have a similar problem. the power light lights up blue then passes into the phone starts loading mode
Sorry for bad English
The updated version (09.14) don't work properly. It doesn't enable me to go to Flashmode. Uninstalled and used the previous version and it worked as it should, no issues entering Flashmode.
i might have actually found the solution. im on the 4.3fw build version 12.1.a.1.201... in my case, my pc will automatically install the drivers for mass storage giving me no chance to update the driver to the one from sony.
you need to do step 9. and 10. if you havent done so from http://unlockbootloader.sonymobile.com/instructions
what i did was allow developer settings and allow debugging via usb.
plug in and attempt to go in to fastboot and obviously it'll fail.
go to device manager. (control panel->hardware and sound->device manager) quickly scroll down go to other devices. you will see s1fastboot (or something like that) if you're quick enough, if not, in my case, the phone will go in to charging mode.
what i did was to disable xperia sp mass storage from disk drives category too.
right click on it and select update driver software and you will select the file you've unzipped (following step 9 and 10 sony's instructions).
after it has finished updating, unplug your usb and attempt to enter fastboot, it should work.
PS: im no expert, this solution might be out there somewhere already or it could just be a great coincidence. some of these steps might not be useful even.
Had this problem and found a funny solution: I switched my cable and the port I was using. Both Ubuntu and Windoze 7 failed on both fastboot and flash mode, even though in both the phone would charge. I grabbed a spare micro USB cable and plugged it into the front of the PC; voila. Now the phone is rooted and running the latest CM.
Need a final solution for this problem
I don't know what to do!!! The problem is this, very similar to the others mentioned above,: When i conect my xperia sp to fastboot mode, pressing volume up while plugging in usb cable, the phone led turns to blue for few seconds and than it just turns to red showing on the screen the battery image( normal charging mode)...... I' m using windows xp and a rooted xperia sp whit cm11 (for locked bootloader obviously). Just two last things:
the phone can be unlocked( I checked it) and fastboot worked the same as now with stock xperia sp firmware.
Please i need a final and a certain solution for this problem!!!
i'll be very thankful to anyone who give me a hand!!!!
TheTras said:
I don't know what to do!!! The problem is this, very similar to the others mentioned above,: When i conect my xperia sp to fastboot mode, pressing volume up while plugging in usb cable, the phone led turns to blue for few seconds and than it just turns to red showing on the screen the battery image( normal charging mode)...... I' m using windows xp and a rooted xperia sp whit cm11 (for locked bootloader obviously). Just two last things:
the phone can be unlocked( I checked it) and fastboot worked the same as now with stock xperia sp firmware.
Please i need a final and a certain solution for this problem!!!
i'll be very thankful to anyone who give me a hand!!!!
Click to expand...
Click to collapse
Are you trying to unlock your phone?
Have you installed device specific/fastboot/flashmode drivers via FlashTool? If you are on Windows 8/8.1, you need to disable driver verification to get it done.
Alternatively if you just wanna unlock your bootloader, you can use the BLU option in FlashTool. Again all drivers will need to be properly installed for your phone to be detected correctly.
You say you had the same problem with stock firmware which means you probably haven't setup adb/fastboot properly on your PC. Does your phone get detected correctly in Device Manager? Have you tried installing drivers via Device Manager?
....
So the solution is installing flashtool and installato drivers via Emma?? Thanks forma the attention!!
TheTras said:
So the solution is installing flashtool and installato drivers via Emma?? Thanks forma the attention!!
Click to expand...
Click to collapse
I meant install drivers via FlashTool. Go to C:\Flashtool\drivers or wherever you have installed Flashtool and run the Flashtool-drivers.exe.
Select flashmode drivers, fastboot drivers and common drivers viskan board (SP drivers) and install them. Like I said if you are on Win 8/8.1, you will have to disable driver signature enforcement. Just look it up in YouTube and follow a tutorial.
Please excuse me if I'm repeating a prior question but it seems far too specific to trawl through pages of related threads to make sure.
I decided I was going to sit down and root my Xperia Z1....
Steps:
1. I installed ADB and Fastboot via the latest windows Android SDK (r23-.0.2), in fact I had to source a sony version of the fastboot driver in order to get it working but once I'd done that all went ahead as planned.
2. Generally followed this guide (wont let me post a link but google "honami cyanogenmod" and it's the 2nd result)
3. All was going swimmingly, I entered fastboot mode absolutely fine, flashed CWM using fastboot which all loaded up absolutely fine.
3. At this stage ADB was not picking up my device at all, tried different cables, ports, all of the usual. What I didn't do was make a backup, and then I wiped all of the things that it's possible to wipe thinking to myself that I was going to get Cyanogenmod on there so all would be fine...
4. Finally I (quite stupidly) restored from memory card (which had already been wiped) from inside CWM, the device restarted and now I am getting no response AT ALL.
5. Sometimes it will load the Sony 'splash' logo that first appears but sometimes not, when plugged in the device is recognised and ADB actually sees the device but lists it as offline... Interestingly at this stage windows device installer actually installs Sony ADB driver for me automatically.
6. All I'm getting at the moment is a red flashing LED although when I plug in via USB the device is again recognised when I type adb devices but again is offline...
If any more information is needed please, I will be more than happy to give a quick reply.
Thank you in advance
JJrmc said:
I decided I was going to sit down and root my Xperia Z1....
Steps:
1. I installed ADB and Fastboot via the latest windows Android SDK (r23-.0.2), in fact I had to source a sony version of the fastboot driver in order to get it working but once I'd done that all went ahead as planned.
2. Generally followed this guide (wont let me post a link but google "honami cyanogenmod" and it's the 2nd result)
Click to expand...
Click to collapse
Were you trying to root your phone or install cyanogenmod? You followed a guide to install cyanogenmod on xperia Z1.
AkiraProject said:
Were you trying to root your phone or install cyanogenmod? You followed a guide to install cyanogenmod on xperia Z1.
Click to expand...
Click to collapse
I was trying to end up with a rooted device running Cyanogenmod, I've been putting it off and off looking into the whole rooting scene and mistakenly dived in a little too quick without knowing what I was doing.
after that you move cm-11-20141112-SNAPSHOT-M12-honami.zip to your sd card. Now you have flashed boot.img you can't move zip to your sd card using z1 you had to do that before using fastboot. use some sd card adapter and do it. then put the sd card back in your phone. turn it on then enter the cwm recovery pressing Vol+ for a few seconds when the sony logo shows up. select full wipe data. then install from zip. choose cm-11-20141112-SNAPSHOT-M12-honami.zip. reboot. ADB won't work until you have installed cyanogenmod zip. You have only installed cyanogenmod kernel and custom recovery when you flashed the boot.img.
AkiraProject said:
after that you move cm-11-20141112-SNAPSHOT-M12-honami.zip to your sd card. Now you have flashed boot.img you can't move zip to your sd card using z1 you had to do that before using fastboot. use some sd card adapter and do it. then put the sd card back in your phone. turn it on then enter the cwm recovery pressing Vol+ for a few seconds when the sony logo shows up. select full wipe data. then install from zip. choose cm-11-20141112-SNAPSHOT-M12-honami.zip. reboot. ADB won't work until you have installed cyanogenmod zip. You have only installed cyanogenmod kernel and custom recovery when you flashed the boot.img.
Click to expand...
Click to collapse
Firstly AkiraProject thank you for your time on this.
I do realise that in my stupidity I could have loaded the cm-11-20141112-SNAPSHOT-M12-honami.zip to my SD card (if I'd had one or waited and gotten one).
What I did however was wipe everything I possibly could, and then hit restore from sdcard/0/ I believe - it may have been a different directory.
I believe what I have done is restored to a blank image......
WHen not plugged into usb I get a red blinking LED when just pressing the power button once.
When holding volume-up + Power the phone vibrates as if it is trying to boot but is unable to
If I leave it plugged into USB AND then press , the device shows the sony Logo and then proceeds to display a backlit but plain black screen, Sony PC Companion recognises the device as connected but is unable to interact with it. The output of "adb devices" shows my device but says "unauthorized" and windows is attempting to install MTB driver....
The behaviour doesnt seem to be quite the same every time.
I believe the device is soft bricked.... is this likely to be a case of a wiped partition table? Or at least loss of the boot partition?
If I leave the device plugged in via USB it periodically reboots itself, shows the Sony logo, remains on a bank screen then shuts itself down.
Shows in device manager as "USB Input Device" on win 7 x64 pro
Thanks in advance
Pretty certain it's not hard bricked, there will be instructions here you can follow:
http://forum.xda-developers.com/showthread.php?t=2574764
Sent from my C6903 using XDA mobile app
D33KK said:
Pretty certain it's not hard bricked, there will be instructions here you can follow:
http://forum.xda-developers.com/showthread.php?t=2574764
Sent from my C6903 using XDA mobile app
Click to expand...
Click to collapse
I have done quite a lot of reading etc on the subject....
according to This thread, Sony Xperias have the bootloader in non-writable mask ROM... so you should always be able to access Fastboot or Flash Mode?
The problem I am having is that I don't seem to be able to activate EITHER Fastboot OR Flash mode in order to flash some new firmware onto my device....
My device is recognized as a "USB Input Device" on Device Manager and windows tries to install MTP driver. I'm going to have a go at the process with a fresh install of windows 7 x64 and 'windows auto-install drivers' turned off.
What is the maximum damage I could have done here?
Thanks
Update
Hard reset (red button inside of the sim-card slot) resets the phone with three vibrates and it restarts.
The phone powers on and displays Sony splash screen and then displays a back-lit black screen.
The phone gets much hotter than normal and powers on to the blank back-lit screen when on charge.
I have NO ACCESS to flash mode or fast boot. Any combination of buttons leads to the same outcome: single vibrate, red LED and the phone shows the Sony splash screen then blank screen, as if the button combinations are just ignored...
Flashtool DOES NOT recognize the device, although it is recognized as C6903 in device manager (I have Sony adb driver installed and have disabled the MTP driver that windows recommends).
Flashtool gives me the red error text about making sure drivers are installed and making sure the device isn't in MTP mode.
I'm at an absolute loss as to what to try next, can somebody shed any light on this? There are plenty of guides but they all seem to rely on EITHER fastboot or flash mode and I can access neither although the phone powers on!
Thanks in advance!
Maybe the partition was corrupted when you flash "blank" image..........
So....JTAG....or send to Sony service....
Shutdown with power+vol up (will vibrate thrice) and see if it doesn't turn on automatically.
If it didn't turn on now check your task manager on windows, go to process tab, kill adb.exe (every adb.exe)
Back on phone connect usb holding down the vol down button (phone have to be off before you connect usb), if green led turns on and doesn't turn off you are on flashmode.
Check on flashtool or flashtool64 (for 64bits) and see if flashtool detects your device. If it detects and recognizes your phone flash the FTF for your device and let it do its job.
As you messed the phone Sony will charge for repairs.
Hi,
Am a novice when it comes to rooting, unlocking android devices. So please excuse my ignorance and my long-winded style of writing. I want the expert users to educate me on this issue and so I don't want to miss any trivial (or not so trivial) information.
1) So, I got Samsung gear live from ebay. It came with a sprat-userdebug 5.0.1. After googling I found out that it's a user/refurb build and can't be updated to 5.1.1
2) Thanks to rootjunky! I used Gear live restore tool V3 and unlocked the bootloader (option 2). Faced few issues in getting the driver. However, fixed everything and unlocked it. Flast TWRPd it (option 8). Flashed recovery (option 4) and bootimage (option 5). Then I sideloaded stock image from 4.4W.2 (using boot.img and system.img). That was the version I found after googling.
3) Then I tried to update it via OTA download. Download completed and it went back to recovery mode and did't apply the download. There was an error message that said something like "Unable to verify the download"
4) Tried multiple times and no luck with that
5) Then tried to sideload new version 5.1.1 LCA43 from xda wiki page. However, when my device went to recovery mode, my pc lost the connection and i wasn't able to sideload (received - device "null" not found" - error from adb command)
6) Until this point I was able to pair my device with my samsung S5 phone and only problem was not able to install the update
7) Then I reset my watch to factory setting, restarted multiple times, went to recovery mode to boot as a new device etc. No luck
8) Then I did something I shouldn't have done (or I think I shouldn't have done). Used option 7 root gear live. When the system went to SH mode, I panicked and closed the cmd prompt and hard reset the device by holding power button
9) After this step, I was not able to pair my device with my phone. Now the version says 4.4W.1 - KGW42N
10) Tried resetting my device, restarted it, used recovery mode to restart it, revoked all debug access, deleted adbkey from my PC, uninstalled android SDK, all drivers, etc. Reinstalled it again with no help.
11)Suddenly android wear in my phone sees my wifirouter as a device (strange)
11) When I plug in the device to my Pc, I could see it in my device manager. When I use recovery tool it says unregistered device and asking me to register it via my phone. Where as am not able to pair it with my phone. Tried to pair it with a new phone (moto e) and no help either
12)Somewhere read that disabling wifi in the phone before pairing works. Tried that and no luck
So here am with a bricked device that stays in the screen where it says "install android wear in your phone" and detects nothing else. Am able to go to bootloader mode, recovery mode from the device. However when it's in recovery mode, my PC doesn't detect it. Even the recovery tool says unregistered device.
Please help in unbricking this device and thank you for reading thru the whole problem. Any help would be much appreciated!
Use Gear live restore tool v2. Lots of known issues with v3
Thanks for the reply. I will try this. However, how will I make my device discoverable? Now, none of my phones detect my device.
So I guess I will get "Unauthorized Device" error when I use recovery tool. Could you please let me know if there's other way around? Or am i missing something?
I've never used it
Pretty sure all the info you need is in the thread
http://forum.xda-developers.com/gear-live/development/utility-gear-live-watch-tool-t2846696
No luck. Tried V2. Tool doesn't recognize my watch. It says 'Device Unauthorized. Please check the confirmation dialog on your device'. My device is stuck in 'Install Android wear on your phone' screen.
unbricked using v2 of the tool. Now trying to update the os version. Will see if I can get lucky this time. Thanks for the help!
All is good now. Now my gear live is running on 5.1.1 with latest updates.
Good work
Please can you tell what exactly you done, as I'm on the same root.. and I'm using win 10... but without any luck so far..
darwchprish said:
Please can you tell what exactly you done, as I'm on the same root.. and I'm using win 10... but without any luck so far..
Click to expand...
Click to collapse
Simple procedure.
Just download v2 of this tool
Make sure to install USB drivers
Unlock bootloader - option 2
Then use option 6 to flash it. Then you'll get new OTA updates.
Refer rootjunky video - https://www.youtube.com/watch?v=x7oRjESQh_o
I'm not able to pair my device with my phone. Now the version says 4.4W.1 - KGW42N,
and ... I tried V2 and V3. Tool but doesn't recognize my watch. It says 'Device Unauthorized. My device is stuck in 'Install Android wear on your phone' screen.
darwchprish said:
I'm not able to pair my device with my phone. Now the version says 4.4W.1 - KGW42N,
and ... I tried V2 and V3. Tool but doesn't recognize my watch. It says 'Device Unauthorized. My device is stuck in 'Install Android wear on your phone' screen.
Click to expand...
Click to collapse
Follow this procedure.
1)Make sure all drivers are installed properly in your PC
2) Make sure when you connect your device to your PC, it's discovered as unauthorized device. It's ok
3) Long press power button in the device and swipe from top left to botom right corner when you see samsung gear live logo
4)This will get the device to bootloader mode
5)Now connect the device to your PC and run V2 of the tool. Your device will be discovered in fastboot mode
6)Now select option 6 to flash the device to stock. It'll flash it
7) Now swipe down to highlight start and swipe from right to left to start. If it goes to Raw dump code = 6. do a hard restart by long pressing power button. You'll get back your device in original setting.
Check rootjunky youtube video to get the live demo of this procedure.
noviceinandroid said:
No luck. Tried V2. Tool doesn't recognize my watch. It says 'Device Unauthorized. Please check the confirmation dialog on your device'. My device is stuck in 'Install Android wear on your phone' screen.
Click to expand...
Click to collapse
How did you get past this? I'm stuck here now too.
-- update after trying that procedure again, it worked to get to fastboot mode. Now I'm doing that 'option 6' to flash it.
mike061215 said:
How did you get past this? I'm stuck here now too.
-- update after trying that procedure again, it worked to get to fastboot mode. Now I'm doing that 'option 6' to flash it.
Click to expand...
Click to collapse
Good luck.
It worked -- and I finally got the OS to update an all that and now I finally have a functional Gear Live. Phew!
My Gear Live was bricked a lot... Computer detect device as RELINK HS-USB QDLoader 9008. Has anyone any idea how fix it?
lamik91 said:
My Gear Live was bricked a lot... Computer detect device as RELINK HS-USB QDLoader 9008. Has anyone any idea how fix it?
Click to expand...
Click to collapse
sounds like USB driver issue. Please install correct drivers and follow the steps mentioned above. It should be unbricked.
Where can i find correct drivers? Additionally my Gear Live doesn't turn on and has only black screen.
I am confused on how to use the tool. My watch is stuck at the Install Android Wear App and won't do anything short of turning it off. How do I enable developer mode \ debugging without being able to get to the watch settings. Please help! Thanks
pedalquickly said:
I am confused on how to use the tool. My watch is stuck at the Install Android Wear App and won't do anything short of turning it off. How do I enable developer mode \ debugging without being able to get to the watch settings. Please help! Thanks
Click to expand...
Click to collapse
You need to factory reset first of all. After that let connect to your wifi, the updates will download on their own. They put a new one out today. I can't go into how but if you look at the forum and search the answers are there. There's even a tool to use.
Sent from my SM-N910T3 using XDA-Developers mobile app
If anyone has been paying attention to any of my threads you'd know i've been having a horrible time trying to get my LG G4 to work. After much trouble of not being able to connect my phone to the computer via download mode ( driver wont start , code 10) my cyanogenmod recovery magically allowed me to install the supersu zip to root the system, and finally the global root access option in cm13 worked which enabled me to install an app and flash twrp. From here I was able to download prometheus rom, and install it from twrp because the cm recovery kept giving me errors., ran smoothly.. was able to get all of my downloaded apps retrieved via google. I reboot the phone this morning after deleting some un wanted apps I had now i'm getting ' secure boot error 1003" and will not boot past the Lg screen. I am really at a lost here and would appreciate it if someone would take the time out to help me. Now I am totally screwed because I cant get windows to install the download mode driver correctly as there is a yellow exclamation mark next "LGE Android MTP device" with a code 10. That is important because adb/fastboot wont recognize the device unless this driver is running and working. I mean sheesh ive tried this on three computers and cant get this da*n driver to install, really? am i seriously missing something? lg software wont even recognize my phone unless its in download mode and even then, will fail to run because * the device can not start* so the software shuts down
Please, help. and if any suggestions, please provide tutorials to back it up.
Sunaj1 said:
If anyone has been paying attention to any of my threads you'd know i've been having a horrible time trying to get my LG G4 to work. After much trouble of not being able to connect my phone to the computer via download mode ( driver wont start , code 10) my cyanogenmod recovery magically allowed me to install the supersu zip to root the system, and finally the global root access option in cm13 worked which enabled me to install an app and flash twrp. From here I was able to download prometheus rom, and install it from twrp because the cm recovery kept giving me errors., ran smoothly.. was able to get all of my downloaded apps retrieved via google. I reboot the phone this morning after deleting some un wanted apps I had now i'm getting ' secure boot error 1003" and will not boot past the Lg screen. I am really at a lost here and would appreciate it if someone would take the time out to help me. Now I am totally screwed because I cant get windows to install the download mode driver correctly as there is a yellow exclamation mark next "LGE Android MTP device" with a code 10. That is important because adb/fastboot wont recognize the device unless this driver is running and working. I mean sheesh ive tried this on three computers and cant get this da*n driver to install, really? am i seriously missing something? lg software wont even recognize my phone unless its in download mode and even then, will fail to run because * the device can not start* so the software shuts down
Please, help. and if any suggestions, please provide tutorials to back it up.
Click to expand...
Click to collapse
This happened to me last night. I tried to "relock" the bootloader. I had to put the phone in download mode, and recover using LG bridge. I found several different ways to accomplish the download mode listed but only one worked., i believe it was here. http://www.androidexplained.com/lg-g4-how-to-boot-into-download-mode/
I used these directions mostly but did one thing a little differently
Download LGUP and install it. I used the DropBox link in this thread:
http://forum.xda-developers.com/g4/h...mm-lp-t3249803
Remember to install the LGUP_8994_DLL file BEFORE LGUP_Install
Download and install LG Bridge (for the USB drivers) here:
http://www.lg.com/uk/support/pc-suite
Select the LG 815 model, the drivers will work. I only used the LG Bridge to install the USB drivers. Nothing else.
OK, now here's where your phone comes in.
Step 1: Turn off your phone (pull the battery if you must, but put it back in).
Step 2: Hold the VOLUME UP button and plug the USB cable into your PC. This puts your phone into DOWNLOAD MODE.
Step 3: On your PC, open up LGUP. The program shoud recognize the phone as H811 in COM3 or COM4. Highlight it and click the SELECT button.
Step 4: Under the "Process" row, select UPGRADE
Step 5: Click the blank space under File Path, it will pop up a [...] [X] at the end. Click the [...].
Step 6: Select the H81120i_00_0201.kdz and click on Start. The program will push the STOCK H811 MM ROM to your phone. This will bring your phone out of Brick mode, but you will have to go through the entire rooting process again.
Instead of using the KDZ files, I used lg bridge. Once i was actually in download mode, and lg bridge recognized my phone, i went the the software update tab and clicked on the error recovery, the tool downloaded the proper rom, installed in and I was back to stock, no root.
Take the cover off of your battery, have a good usb cable handy. I had to remove the battery, hold the buttons and start over several times before I got it to work, but I did.
Good luck.
happimeal said:
This happened to me last night. I tried to "relock" the bootloader. I had to put the phone in download mode, and recover using LG bridge. I found several different ways to accomplish the download mode listed but only one worked., i believe it was here. http://www.androidexplained.com/lg-g4-how-to-boot-into-download-mode/
I used these directions mostly but did one thing a little differently
Download LGUP and install it. I used the DropBox link in this thread:
http://forum.xda-developers.com/g4/h...mm-lp-t3249803
Remember to install the LGUP_8994_DLL file BEFORE LGUP_Install
Download and install LG Bridge (for the USB drivers) here:
http://www.lg.com/uk/support/pc-suite
Select the LG 815 model, the drivers will work. I only used the LG Bridge to install the USB drivers. Nothing else.
OK, now here's where your phone comes in.
Step 1: Turn off your phone (pull the battery if you must, but put it back in).
Step 2: Hold the VOLUME UP button and plug the USB cable into your PC. This puts your phone into DOWNLOAD MODE.
Step 3: On your PC, open up LGUP. The program shoud recognize the phone as H811 in COM3 or COM4. Highlight it and click the SELECT button.
Step 4: Under the "Process" row, select UPGRADE
Step 5: Click the blank space under File Path, it will pop up a [...] [X] at the end. Click the [...].
Step 6: Select the H81120i_00_0201.kdz and click on Start. The program will push the STOCK H811 MM ROM to your phone. This will bring your phone out of Brick mode, but you will have to go through the entire rooting process again.
Instead of using the KDZ files, I used lg bridge. Once i was actually in download mode, and lg bridge recognized my phone, i went the the software update tab and clicked on the error recovery, the tool downloaded the proper rom, installed in and I was back to stock, no root.
Take the cover off of your battery, have a good usb cable handy. I had to remove the battery, hold the buttons and start over several times before I got it to work, but I did.
Good luck.
Click to expand...
Click to collapse
Thanks so much. Hopefully I can get this to work, if I can get the PC to see the LGE MTP download mode driver then the rest is golden. Will keep things updated. Will try when I get home.
happimeal said:
This happened to me last night. I tried to "relock" the bootloader. I had to put the phone in download mode, and recover using LG bridge. I found several different ways to accomplish the download mode listed but only one worked., i believe it was here. http://www.androidexplained.com/lg-g4-how-to-boot-into-download-mode/
I used these directions mostly but did one thing a little differently
Download LGUP and install it. I used the DropBox link in this thread:
http://forum.xda-developers.com/g4/h...mm-lp-t3249803
Remember to install the LGUP_8994_DLL file BEFORE LGUP_Install
Download and install LG Bridge (for the USB drivers) here:
http://www.lg.com/uk/support/pc-suite
Select the LG 815 model, the drivers will work. I only used the LG Bridge to install the USB drivers. Nothing else.
OK, now here's where your phone comes in.
Step 1: Turn off your phone (pull the battery if you must, but put it back in).
Step 2: Hold the VOLUME UP button and plug the USB cable into your PC. This puts your phone into DOWNLOAD MODE.
Step 3: On your PC, open up LGUP. The program shoud recognize the phone as H811 in COM3 or COM4. Highlight it and click the SELECT button.
Step 4: Under the "Process" row, select UPGRADE
Step 5: Click the blank space under File Path, it will pop up a [...] [X] at the end. Click the [...].
Step 6: Select the H81120i_00_0201.kdz and click on Start. The program will push the STOCK H811 MM ROM to your phone. This will bring your phone out of Brick mode, but you will have to go through the entire rooting process again.
Instead of using the KDZ files, I used lg bridge. Once i was actually in download mode, and lg bridge recognized my phone, i went the the software update tab and clicked on the error recovery, the tool downloaded the proper rom, installed in and I was back to stock, no root.
Take the cover off of your battery, have a good usb cable handy. I had to remove the battery, hold the buttons and start over several times before I got it to work, but I did.
Good luck.
Click to expand...
Click to collapse
bro, thanks for taking the time to write this out. Not sure what I was doin wrong before, but i was able to flash back to stock