I haven't touched my LG G7 in a while, so I decided to flash original boot_a/b to be able to OTA update. But when I boot into bootloader, fastboot can't do anything, command simply hangs until I interrupt it.
It is not just that the:
Code:
fastboot flash boot_a boot_v10p.img
fails, but not even:
Code:
fastboot flashing get_unlock_ability
works.
Fastboot recognize the device properly:
Code:
# fastboot devices
LMG710EMabd8a3d8 fastboot
Any thoughts?
Related
Hi, I am trying to Re-Lock my Galaxy Nexus GSM version, I've downloaded the SDK files (adb-mac and fastboot-mac) and all the image files and I am trying to execute the following commands:
adb reboot bootloader
fastboot flash bootloader bootloader-toro-primekk15.img
fastboot reboot-bootloader
fastboot flash radio radio-toro-i515.ek02.img
fastboot reboot-bootloader
fastboot flash radio-cdma radio-cdma-toro-i515.ek05.img
fastboot reboot-bootloader
fastboot -w update image-mysid-icl53f.zip
fastboot reboot-bootloader
fastboot oem lock
With the phone in normal mode I connect the USB cable to the computer, start Terminal windows and run the first command, "./adb-mac reboot bootloader" and the phone will boot into the "Fastboot Mode", then I try to execute "./fastboot-mac devices" to make sure the phone is connected and properly detected and I get nothing.
If I try to execute "./fastboot-mac flash bootloader bootloader-toro-primekk15.img" I get the message <waiting for device> and it will stay there forever.
Do you know what might be the problem ?, is there other method to do this ?, go back to Stock ROM and Re-Lock the device ?, thanks
You must also install the Samsung usb drivers. I have no idea how to do this in mac. A simple search will help you tho.
I walked through the following steps to put the stock OS back on my device...
adb reboot bootloader
fastboot flash bootloader bootloader-toro-primekk15.img
fastboot reboot-bootloader
fastboot flash radio radio-toro-i515.ek02.img
fastboot reboot-bootloader
fastboot flash radio-cdma radio-cdma-toro-i515.ek05.img (Note: This one takes a couple minutes. Be patient)
fastboot reboot-bootloader
fastboot -w update image-mysid-icl53f.zip
I now have the stock OS loaded and can boot alright, unlocked. When I get back into the OS I turn debugging on and then head back to adb. I can browse to my device through the USB but get the following error when attaching to my device.
c:\android\android-sdk\platform-tools\adb shell
[email protected]:/ $ adb reboot bootloader
adb reboot bootloader
error: device not found
1|[email protected]:/ $
Further, if I run "fastboot devices" from my command prompt I get no devices returned.
What am I missing?? I need to get this device relocked to send back in for warranty quickly. I'm trying to get the device locked back up. Any help you can provide is appreciated!
Edit: Resolved now
nevermind... whew... figured it out.
Mark threads as solved and update first post with whats happening, so one doesnt waste time like i did.
No need to double post for that.
I lost my biometric sensor after leaving the test soak and go to a custom rom, how can I recover before leaving the final oreo stock?
eduh9 said:
I lost my biometric sensor after leaving the test soak and go to a custom rom, how can I recover before leaving the final oreo stock?
Click to expand...
Click to collapse
Hi, this happened to me, back to the stock rom (Android 7.0) of the device and do the whole procedure. And your sensor will work
Be careful to do not downgrade your bootloader though.
This tutorial helped me to recover biometrics in my phone (XT1676, reteu, 3/16, DualSIM).
I am not responsible for any damage! If you proceed to follow this, you're doing it at your own risk.
1. Make sure, your adb and fastboot is working.
I recommend using this one https://forum.xda-developers.com/showthread.php?t=2588979 . For me, it's fully working on Win8.1 x64. If you install it (press "Y" for all of 3 questions), but after connecting phone you see "Fastboot cedric S" with yellow exclamation mark in device manager, there's problem with driver: right click on it --> "Update driver software" --> "Browse my computer for driver software" --> "Let me pick from a list of device drivers on my computer" --> "Android devices" --> "Android Bootloader Interface" --> "Next" --> "OK" --> "Close"
(Open cmd and use "cd" command to get to directory, where's adb installed (in this case "cd C:\adb"). Then, press Enter and type "Fastboot devices". If fastboot is properly installed with corresponding drivers, you will see your device listed.)
2. Download this firmware https://drive.google.com/file/d/1hlNzlFhLCEj6xigfKrYcvnwH9jy3f5j3/view and extract it to the same directory as adb is installed.
3. Boot your phone into fastboot mode by pressing and holding power and vol- buttons for few seconds.
4. NOW, THE MOST IMPORTANT PART! Check your bootloader version.
4a. If your bootloader version is B8.25, use these commands to flash:
Code:
fastboot oem fb_mode_set
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
4b. If your bootloader is B8.24 and lower, use these commands:
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
5. Your phone should reboot and sucessfully boot into OS in few minutes with fingerprint working.
DON'T EVEN TRY TO TAKE OTA UPDATES.
6. (optional) However, if you want to update your phone, update it manually with correct files from this site https://forum.xda-developers.com/g5/how-to/cedric-ota-archive-t3795275
Moto g5, has a biometric sensor?
666km666 said:
Moto g5, has a biometric sensor?
Click to expand...
Click to collapse
Of course, it has (fingerprint sensor at the front, under the display).
johnnywilly16 said:
Hi, this happened to me, back to the stock rom (Android 7.0) of the device and do the whole procedure. And your sensor will work
Click to expand...
Click to collapse
Sorry I'm just confirming that I need to go to stock 7.0 first? Will the debloated stock 7.0 be good enough?
eduh9 said:
I lost my biometric sensor after leaving the test soak and go to a custom rom, how can I recover before leaving the final oreo stock?
Click to expand...
Click to collapse
For anyone who finds this there is a flastable Nougat zip for Cedric which fixes finger print scanner, it is in the same thread as the soak 8.1 zip. I hope this saves others trouble as it did me. Find direct answers in telegram:
@cedricNOOBchat
So I am trying to reflash oxygen os because through a series of wacky circumstance I bricked the 9 pro. It seems like the b slot got messed up and there is nothing I can do. I am trying to reflash using MSM however, I now get stuck on "Waiting for Device". I don't think I am properly in edl mode. I tried installing the qualcom driver however it seems like it stil doesn't work. What can I do to unbrick this? Sorry if this is a newbie question, I am newer to Oneplus.
Alright second update: Got fastboot to work with windows, it was an error with my windows in particular. The issue now is I can't get the phone in edl mode. It just goes to fastboot when I try to boot into it.
Update 3: So I think what happened is one of the slots got locked. This is from flashing with fastboot. I'm guessing this is causing it to not boot into edl as well.
I had the same problem.
In fastboot "fastboot -w" this deleted everything. Then via fastboot:
After that, begin typing in the following commands in the CMD window, one at a time:
fastboot flash boot boot.img
fastboot flash cpucp cpucp.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash oplus_sec oplus_sec.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash splash splash.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
That was the first part.
Then "fastboot reboot bootloader".
Here, switch off the device without USB cable. Wait one minute, then hold Volume - & Volume + for approx. 40 seconds and then plug in the USB cable with the keys pressed. The MSM Tools should have started.
This is how it worked for me.
my phone had a black screen and it wouldnt turn on nor do anything other than turn on and off every 10 seconds when plugged in (pc would make the hardware connected and disconnected sounds and qualcom device would show on DM) . THIS IS THE ONLY thing that worked
Follow the first post and it should be good 2 go.
Keep stock recovery and extract the boot image.
You'll need.
Unlocked bootloader as guided here
adb/fastboot and proper drivers on PC.
TWRP from here. Any recent build will do, just grab the latest one.
Steps:
Reboot to fastboot
Code:
adb reboot bootloader
In fastboot, verify it's working properly and get the current slot. The result is either a or b
Code:
fastboot devices
Code:
fastboot getvar current-slot
Now boot into TWRP temporarily. The touchscreen will NOT work(a known issue). Just leave the phone connected
Code:
fastboot boot Twrp_3.5.2-10_EduardoA3677-billie_OxygenOs11_Android11.img
adb should work now. Extract boot image(s).
Code:
adb devices
Code:
adb pull /dev/block/bootdevice/by-name/boot_a boot_a.img
Code:
adb pull /dev/block/bootdevice/by-name/boot_b boot_b.img
Now we have boot_a.img and boot_b.img in current folder. Both should be 96MB or 100,663,296 bytes.
Depends on the result from step 2,
if it's "current-slot: a" then use boot_a.img. if it's "b" use "boot_b.img".
Once done, reboot the phone.
Code:
adb reboot
Now with this boot image, follow the guide to root.