Related
My phone doesnot go past google logo.
Need the stock recovery and system image
I am thinking once i get them i should be able to run using FAstboot commands
without even unlocking(as fast boot oem unlock also not working for me) boot loader..somebody please confirm...
I tried fastboot update update.zip with Official 2.3.3 ROM but i get following error
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
My phone is not rooted neither the boot loader is unlocked( I have failed to unlock it with Fastboot OEM unlock)
First thing first... connect your phone and type "adb devices". Does your serial nr show up? Turn off your phone and boot into bootloader (hold vol up + power). Type "fastboot devices", does your serial nr show up? If not, adb and/or fastboot isn't recognizing your connection and device. If it does, you SHOULD be able to type "fastboot oem unlock" to unlock your bootloader.
Tip: you can view your bootlooader state on the device display when inside the loader. It says "State: LOCKED" or "State: UNLOCKED" respectively.
[ROM] Samsung stock D720 for Nexus S 4G
All else fails, this should get your phone back to factory.
http://forum.xda-developers.com/showthread.php?t=1072698
http://www.holylivingfuck.com/Crap/SamsungSimpleDL_D720(1.0.002).zip
MIRROR
http://www.fileserve.com/file/JnCgZkm
I have nexus s GSM(tmobile version) , anybody knows similar link like above for it.
jottosson said:
First thing first... connect your phone and type "adb devices". Does your serial nr show up? Turn off your phone and boot into bootloader (hold vol up + power). Type "fastboot devices", does your serial nr show up? If not, adb and/or fastboot isn't recognizing your connection and device. If it does, you SHOULD be able to type "fastboot oem unlock" to unlock your bootloader.
Tip: you can view your bootlooader state on the device display when inside the loader. It says "State: LOCKED" or "State: UNLOCKED" respectively.
Click to expand...
Click to collapse
when i run adb devices it doesnt display any device seems it needs usb debugging enabled which I cant do as mentioned above.
when i run fastboot devices , it does display my phone's serial number but when i run the command fastboot oem unlock my phone displays a confirmation to select "Yes or no" , i chose "yes" and hit the power button but then it doesnt do any thing it just stays there , i tried multiple times waited several mins to hours but no luck yet.
I am running all this on windows 7 64 bit computer .
http://forum.xda-developers.com/showthread.php?t=884416&highlight=STOCK
justsahid said:
when i run adb devices it doesnt display any device seems it needs usb debugging enabled which I cant do as mentioned above.
when i run fastboot devices , it does display my phone's serial number but when i run the command fastboot oem unlock my phone displays a confirmation to select "Yes or no" , i chose "yes" and hit the power button but then it doesnt do any thing it just stays there , i tried multiple times waited several mins to hours but no luck yet.
I am running all this on windows 7 64 bit computer .
Click to expand...
Click to collapse
cadams14 said:
http://forum.xda-developers.com/showthread.php?t=884416&highlight=STOCK
Click to expand...
Click to collapse
this doesnt work as it also asks to unlock botloader sing Fastboot oem unlock
i am also stuck in the same situation but i dont have a sprint 4g. is there any other links available?
Another one here. Same situation. Any resolutions yet?
jboxer said:
Another one here. Same situation. Any resolutions yet?
Click to expand...
Click to collapse
Here you go, set your phone to download mode and use ODIN to flash your phone (i9020) back to stock.
http://www.samfirmware.com/WEBPROTECT-i9020.htm
justsahid said:
My phone doesnot go past google logo.
Need the stock recovery and system image
I am thinking once i get them i should be able to run using FAstboot commands
without even unlocking(as fast boot oem unlock also not working for me) boot loader..somebody please confirm...
Click to expand...
Click to collapse
Check out that u hv installed driver properly for fastboot. Bootloader need to b unlocked for getting into Download mode.
Sent from my Nexus S using XDA App
zirra said:
Here you go, set your phone to download mode and use ODIN to flash your phone (i9020) back to stock.
http://www.samfirmware.com/WEBPROTECT-i9020.htm
Click to expand...
Click to collapse
This will work for the t? I was under the impression we didnt have any images for the 9020t version.
Edit: I just signed up for the site and everything, and it says nothing about being for the T version.
Yes that Odin package from Samfirmwares is for the I9020T. However it is not version 2.3.3, but rather 2.3.1 GRH78.
I have had my US996 almost a month. Infant mortality period should be past so I tried to unlock bootloader today. I had all the necessary settings enabled and got into Fastboot mode. I entered "fastboot oem device-id' and " waiting for device" stayed on PC screen for 5 minutes until I aborted. I'm sure this isn't normal. I really want to unlock this beauty because I paid $117 more than Verizon charges just so I could. Any suggestions?
If it says waiting for device you phone is not being recognized in fastboot. Verify the fastboot DRIVERS are installed in device manager.
I am obviously missing something here I have verified that the phone has the latest usb driver. I open an administrative command prompt and go to the directory where the 3 downloaded files are. I use the oem cable to connect the phone to my PC. I select either photo or file transfer (tried both several times) and enter "adb bootloader reboot" which reboots the phone into adb mode. I then enter "fastboot oem device-id" and the dos screen says "waiting for any device". IMy previous phone was the LG G3 which was rooted, bootloader unlocked, and running SkyDragon ROM and with heavy modding via Xposed. I'm no developer but I'm not exactly a noobie either. I'm about ready to throw in the towel. Very frustrating! Thanks for your help anyway me2131
The reboot command is "adb reboot bootloader" not "adb bootloader reboot". You can confirm you're in fastboot mode as your phone screen will show the following,
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you're sure you're in fastboot, you can check if your computer I registering it by running "fastboot devices"
Code:
C:\Users\XXX\AppData\Local\Android\sdk\platform-tools>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
LGUS996XXX device
C:\Users\XXX\AppData\Local\Android\sdk\platform-tools>adb reboot bootloader
C:\Users\XXX\AppData\Local\Android\sdk\platform-tools>fastboot devices
LGUS996XXX fastboot
If it does not register in "fastboot devices" you're either not in fastboot mode or the drivers aren't installed.
redshorty4 said:
The reboot command is "adb reboot bootloader" not "adb bootloader reboot". You can confirm you're in fastboot mode as your phone screen will show the following,
If you're sure you're in fastboot, you can check if your computer I registering it by running "fastboot devices"
Code:
C:\Users\XXX\AppData\Local\Android\sdk\platform-tools>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
LGUS996XXX device
C:\Users\XXX\AppData\Local\Android\sdk\platform-tools>adb reboot bootloader
C:\Users\XXX\AppData\Local\Android\sdk\platform-tools>fastboot devices
LGUS996XXX fastboot
If it does not register in "fastboot devices" you're either not in fastboot mode or the drivers aren't installed.
Click to expand...
Click to collapse
No devices were seen. when I run "fastboot devices". Also, the PC device manager displays this information in "Events":: Device USB\VID_1004&PID_633E&MI_00\6&7f41b3b&6&0000 requires further installation.
What further installation? I have never run across this cryptic message before. No idea what to do now.
Go over the process again and do a search on XDA for the latest fastboot drivers and install those. I was having problems with the old fastboot and it worked for me after I updated it.
LBJM said:
Go over the process again and do a search on XDA for the latest fastboot drivers and install those. I was having problems with the old fastboot and it worked for me after I updated it.
Click to expand...
Click to collapse
There has been progress but I still cannot get fastboot to work. I am using fastboot.exe dated 11-12-2016 and is the latest I could find. The progress is that, after loading and installing the file "Universal USB Driver" on the PC can now see the device when I enter "adb devices" at the C:\Tools> prompt. It shows LGUS996b******* device. I then enter "adb reboot bootloader" and the phone shows the "Welcome to Fastboot mode for bootloader unlock". But when I enter "fastboot oem device-id" I still get the "Waiting for any device" message and nothing further happens. Sorry, I'm STILL missing something. Thanks for the help so fay to the three responders.
PhoneBull said:
There has been progress but I still cannot get fastboot to work. I am using fastboot.exe dated 11-12-2016 and is the latest I could find. The progress is that, after loading and installing the file "Universal USB Driver" on the PC can now see the device when I enter "adb devices" at the C:\Tools> prompt. It shows LGUS996b******* device. I then enter "adb reboot bootloader" and the phone shows the "Welcome to Fastboot mode for bootloader unlock". But when I enter "fastboot oem device-id" I still get the "Waiting for any device" message and nothing further happens. Sorry, I'm STILL missing something. Thanks for the help so fay to the three responders.
Click to expand...
Click to collapse
I used "fastboot oem unlock" as I only had the V20 attached to the PC and not any android devices.
Has anyone successfully unlocked the US996 using a Windows 10 Pro 64 bit PC?
PhoneBill said:
Has anyone successfully unlocked the US996 using a Windows 10 Pro 64 bit PC?
Click to expand...
Click to collapse
I did it with windows 8.1 x64, just make sure you have adb that supports win 10 and find fastboot drivers for win 10.
I hate to admit it but I am ready to give up. I have tried all the suggestions made here plus many others and cannot get past the "Waiting for any device" message when I try to fastboot. I have used both 3.0 and 2.0 USB ports, have disabled driver signature enforcement in windows, disabled Automatic Download of Drivers from Windows Update and virtually everything else I could find about this problem. I am SO SICK of "Waiting for any device" that I am considering selling the US996 and getting another G3 because last night US99610f was installed on my phone and apparently root has been lost with this ROM version. I thought I had auto updates disabled but all the playing around with settings I have had to do in the past week must have turned it back on. I thank all in this thread who have tried to help me.
PhoneBill said:
I have had my US996 almost a month. Infant mortality period should be past so I tried to unlock bootloader today. I had all the necessary settings enabled and got into Fastboot mode. I entered "fastboot oem device-id' and " waiting for device" stayed on PC screen for 5 minutes until I aborted. I'm sure this isn't normal. I really want to unlock this beauty because I paid $117 more than Verizon charges just so I could. Any suggestions?
Click to expand...
Click to collapse
I'm the OP and am finally unlocked and rooted! It took a lot of searching, deleting stuff from Windows 10 and loading new stuff, and time but I finally succeeded and am happy to report have experienced no problems. The OTA was pushed to my phone 2 days before I succeeded in unlocking so I was on US99610f. So maybe those of you holding off on the OTA for fear of losing root are going to be OK. TWRP and Titanium Backup both fully functional although I don't understand why the SuperSu version I have is 2.79 when I downloaded 3.0.2-1. I am anxiously awaiting Xposed for Nougat and hopefully success someday with mods for enabling the FM radio and Verizon Advanced Calling. Even if none of that happens it's still a beast of a phone.
Edit: OOPS! I DO have TWRP ver. 3.0.2-1 and SuperSu ver. 2.79. I wasn't thinking when I typed the above!
That's good to know. I took the update last week. I'm waiting to root. I'm not confident about being able to go back to stock. Still pretty confused by the methods... and waiting for Xposed.
EDIT
Oh, I wasn't aware Advanced calling is lost once phone is rooted...
advanced calling was lost for me when I upgraded to the F firmware. I had to clear cache and reboot a million times but I also had my friend at Verizon toggle advanced calling on and off to trigger something...and something worked and it wasn't grayed out anymore and was on again. so I don't think it's rooting that does it, but it was the new OTA.
Sent from my LG-US996 using Tapatalk
I had the same problem with fastboot saying "waiting for any device" even though adb was able to list the devices. I finally got "fastboot oem device-id" working with my LG V20 model US966 on Windows 10.
Go into Windows Device manager and find the phone. Right click the phone and choose "Update Driver".
Then "Browse my computer for drivers".
Then "Let me pick from a list of available drivers on my computer"
You may see a single item "Android Device". If so, select that and you will get the option to choose which device driver to load.
Choose "LGE Mobile ADB Interface" and click Next.
You will get a warning that the driver is not recommended. Click "Yes" to use it anyway.
Note that if you do not get an option to install the driver then make sure you have installed the Android Driver (via Google's Android SDK) and the LG Driver.
Hello,
I am going through the official way of unlocking the bootloader through developer.lge.com
I am trying to see my device's ID but can't get into boot loader mode
When ever I run "adb reboot bootloader" in CMD I get the message "no device/emulator found"
- OEM unlock is enabled
- USB debugging is enabeled
- I am using LG usb drivers
Did a ton of googling and not sure what else to try.
I wanna root this phone so bad!
Well I was able to get past the ID issue by using a different PC, however once I was able to input my device ID and everything into the LG site, the message I got was this:
Your device (LGUS996Z) does not support unlocking the bootloader. Please check your model. Your account will be locked if you enter the wrong information more than 8 times.
I don't even understand how it's possible if this us a US996.. gonna be pretty upset if I can't unlock the bootloader
What the heck is a LGUS996Z anyway!?
Gonna be really upset if I can't unlock the bootloader
Here's a picture of the model number sticker:
https://www.dropbox.com/s/y64rgsee2rol37a/20180120_024800.jpg?dl=0
pretty sure it isn't the us cellular version
I just follow the official "fastboot oem unlock" ,After restart device don't green light ,The computer unkonw device
adb drivies "List of devices attached",Consult online customer service "since the warranty is expired we will not be able to replace and there is no repair option too."
Discard this device I was confused?
Hello! I don't know if there might a be a solution for this problem, we've tried many stuff that's been posted here on the forums but ended up in the same results, so no luck. My friend's Moto G5 Plus "bricked" itself while updating to Oreo some time ago, wasn't rooted or anything, bootloader wasn't unlocked either. We can access the recovery menu with "power + vol+", but any option we try to use ends up with the message "Failed to pass validation, backup to fastboot". Some of the solutions I've tried require the bootloader to be unlocked, but I haven't been able to unlock it since my friend never checked the "Allow OEM unlock" option. He took the phone to the official service but they said they couldn't do anything and wanted to sell him a new phone. Any help is appreciated. Thanks in advance!
ZSparda said:
Hello! I don't know if there might a be a solution for this problem, we've tried many stuff that's been posted here on the forums but ended up in the same results, so no luck. My friend's Moto G5 Plus "bricked" itself while updating to Oreo some time ago, wasn't rooted or anything, bootloader wasn't unlocked either. We can access the recovery menu with "power + vol+", but any option we try to use ends up with the message "Failed to pass validation, backup to fastboot". Some of the solutions I've tried require the bootloader to be unlocked, but I haven't been able to unlock it since my friend never checked the "Allow OEM unlock" option. He took the phone to the official service but they said they couldn't do anything and wanted to sell him a new phone. Any help is appreciated. Thanks in advance!
Click to expand...
Click to collapse
Would be helpful to know what exactly you've done to rescue that device.
For example, did you try to wipe the complete device and fastboot flash the latest signed Oreo firmware?
Is the device recognised by a PC?
What about using Lenovo Motorola Smart Assistant?
Wolfcity said:
Would be helpful to know what exactly you've done to rescue that device.
For example, did you try to wipe the complete device and fastboot flash the latest signed Oreo firmware?
Is the device recognised by a PC?
What about using Lenovo Motorola Smart Assistant?
Click to expand...
Click to collapse
Hey! From what he told me, at first he was able to access the recovery menu, when then little Android with the red mark shows up, then he used the Smart Assistant and after that he gets the validation error message that I mentioned. I suppose the Smart Assistant made things worse? The device was initially recognised by the PC, but now it isn't. We tried to flash the stock firmware and unlock the bootloader but we didn't have any luck either. Since the PC didn't recognized it anymore we tried a few things to make it work but ended up giving up.
ZSparda said:
Hey! From what he told me, at first he was able to access the recovery menu, when then little Android with the red mark shows up, then he used the Smart Assistant and after that he gets the validation error message that I mentioned. I suppose the Smart Assistant made things worse? The device was initially recognised by the PC, but now it isn't. We tried to flash the stock firmware and unlock the bootloader but we didn't have any luck either. Since the PC didn't recognized it anymore we tried a few things to make it work but ended up giving up.
Click to expand...
Click to collapse
So you can't get to the screen with the dead android (fastboot mode) or recovery with the key combination (power and vol down/power and vol up)? You should be able to get there and check the connection by typing
fastboot devices
or
adb devices
Is the battery full enough to start?
Do you see the device in Windows devices manager?
PC should recognise it at very worst, as qhsusb_bulk. Your PC must be in test mode, and then when you connect look in device manager, under usb devices, and a hard bricked phone will show as qhsusb_bulk. Anything else, you should be able to communicate with ADB/fastboot, as Wolfcity stated. If it does show as qhsusb_bulk, you will need to use vaches' blankflash to recover the unit.
Wolfcity said:
So you can't get to the screen with the dead android (fastboot mode) or recovery with the key combination (power and vol down/power and vol up)? You should be able to get there and check the connection by typing
fastboot devices
or
adb devices
Is the battery full enough to start?
Do you see the device in Windows devices manager?
Click to expand...
Click to collapse
I tried to attach a couple of screenshots but I get the "bad request" message here. Anyways, when we do a normal boot we get the validation error message and we are sent directly to fastboot menu, but there we cannot choose any options because all of them lead to the error message again.
It's been a couple of weeks now but the last time we tried doing something, the device wasn't showing up in device administrator nor being recognized by adb.
As regards to the battery, we've left it charge up for some hours, so I guess that's not a problem, although we cannot see the percentage.
[email protected] said:
PC should recognise it at very worst, as qhsusb_bulk. Your PC must be in test mode, and then when you connect look in device manager, under usb devices, and a hard bricked phone will show as qhsusb_bulk. Anything else, you should be able to communicate with ADB/fastboot, as Wolfcity stated. If it does show as qhsusb_bulk, you will need to use vaches' blankflash to recover the unit.
Click to expand...
Click to collapse
I'll tell him to check if it shows up as qhsusb_bulk and update here. Could you explain a bit more or link to a thread about vache's blankflash? What is it exactly?
ZSparda said:
I'll tell him to check if it shows up as qhsusb_bulk and update here. Could you explain a bit more or link to a thread about vache's blankflash? What is it exactly?
Click to expand...
Click to collapse
This thread is long, but alot of good info on hard bricked Moto G5 plus devices.
Code:
https://forum.xda-developers.com/g5-plus/help/moto-g5-plus-hard-bricked-recognized-t3636457
To get PC in test mode
Code:
Here is how to turn on or off the Test Mode feature in Windows 10.
IMPORTANT: Please remember that turning off the Test Mode feature may force the program/driver which is not digitally signed stop working.
Step 1: Open Command Prompt as administrator. To do so, type CMD in Start menu search to see Command Prompt in the search result. Right-click on Command Prompt entry and then click Run as administrator option. Click Yes button when you see the User Account Control screen.
Step 2: At the Command Prompt window, execute the following commands:
To enable the Test Mode:
Bcdedit.exe -set TESTSIGNING ON
To disable the Test Mode:
Bcdedit.exe -set TESTSIGNING OFF
If the above command didn’t work, this one must work:
Bcdedit.exe -set loadoptions ENABLE_INTEGRITY_CHECKS
Bcdedit.exe -set TESTSIGNING OFF
You may exit the Command Prompt now.
[email protected] said:
This thread is long, but alot of good info on hard bricked Moto G5 plus devices. To get PC in test mode
Click to expand...
Click to collapse
Thanks! I'll send him all these so he can try. I'll update as soon as possible.
[email protected] said:
This thread is long, but alot of good info on hard bricked Moto G5 plus devices. To get PC in test mode
Click to expand...
Click to collapse
Update: The PC detects the phone as Android Device > Mot Composite ADB Interface.
But once in adb, adb devices isn't working. It doesn't recognize the device.
ZSparda said:
Update: The PC detects the phone as Android Device > Mot Composite ADB Interface.
But once in adb, adb devices isn't working. It doesn't recognize the device.
Click to expand...
Click to collapse
It is recognizing the device, " Mot Composite ADB Interface" is correct.How about
Code:
fastboot devices
? It should show the device #. ADB doesn't always show devices.
[email protected] said:
It is recognizing the device, " Mot Composite ADB Interface" is correct.How about ? It should show the device #. ADB doesn't always show devices.
Click to expand...
Click to collapse
Yes! Fastboot devices shows the device! So now we have to procede with the flashblank.zip and all that from the other post right? Also sorry for the late reply, I've been pretty busy these past days so I left him with all the work.