I am chasing the Z2 Force 1789-04 OREO ROM as released by AT&T in the OTA update.
I am using one in Australia (works great on Telstra) and I believe the reason I can't get the OTA update because I am not on the AT&T network. (Although I have had OTA updates on Taiwan model ASUS phones before).
Searched the web and XDA high & lo and there is never any mention of this one.
The software version of mine is also stuck.
And when I go and check if there is any update,it will say that my system is up to date.
dijia1124 said:
The software version of mine is also stuck.
And when I go and check if there is any update,it will say that my system is up to date.
Click to expand...
Click to collapse
Same as yours
Install Lenovo Moto Software Assistant on a Windows PC, enable USB debugging on the phone, and connect via USB to PC (assuming drivers are installed). The software will allow you to download the update and install via fastboot. This will wipe your device, so be sure to back up your data.
209pcs said:
Install Lenovo Moto Software Assistant on a Windows PC, enable USB debugging on the phone, and connect via USB to PC (assuming drivers are installed). The software will allow you to download the update and install via fastboot. This will wipe your device, so be sure to back up your data.
Click to expand...
Click to collapse
Stuck on 7.1.1, system update saying up to date. This method I used to get oreo but with July 1 security patch which broke fingerprint option?
Lenovo Assistance is still saying OCXS27.109-47-11(July patch) is the lastest
Oreo Update
For all who could not receive the Android 8 Oreo update and need it:
I was finally able to install the update through the Lenovo Moto Smart Assistant (poorly designed tool but at least it's a work around):
https://support.lenovo.com/il/en/downloads/ds101291
Before starting, you have to tap your build number 7 times ( Apps > Settings > System > About phone then tap Build number 7 times. Tap the Back icon to navigate back to System then select Developer options.)
Tap USB debugging to turn on. BTW when you connect it to the smart assistant, there will be a couple of popups on the phone screen that you have to give permission to.
The first dozen times I tried it, it would stall at 51% no matter what settings i picked. I finally got it to work by doing the following:
Once it recognized the phone (has to be powered on), I went to the update tab and let it see my phone and get ready to start the update.
Next I turned off the phone, then held the down volume, and powered back on (into fastboot.) Then I started the upgrade. It took a while but actually completed when I came back from breakfast.
Then, I had a new problem which appears all over the net: my finger print reader didn't work anymore. I tried a full wipe/restore from the settings, but it didn't help. There's directions all over the net to sideload files, etc, but I didn't do any of that.
I went back into the smart assistant and instead of doing the upgrade, I did the rescue (pick Moto Phone, then select your device from the drop downs (moto z 2nd gen). With this process, it actually tells you to turn off your phone, then power-on with the volume down depressed.
After the Rescue, my finger print reader was reconfigured and is now working great.
I hope someone else finds this helpful. I was very eager to get the update and make sure my phone didn't brick or something while I could still return it. Good luck and comment with your results if you give it a try.
westec2 -
Once it recognized the phone (has to be powered on), I went to the update tab and let it see my phone and get ready to start the update.
Next I turned off the phone, then held the down volume, and powered back on (into fastboot.) Then I started the upgrade.
Click to expand...
Click to collapse
Unfortunately, I am unable to replicate this. When I turn off my device, LMSA reverts to not seeing the device.
I've tried to use the RESTART BOOTLOADER option which seems to do something, but even though LMSA advances to 100%, the update didn't actually do anything.
So, I'm still stuck.
Related
So I just got an LG G pad 10.1 VK700 from Verizon the other day. I rooted the device on the first day but never really added any additional apps or software.
Another member in the household was using the tablet and it asked if they wanted to accept the VZW Update for KitKat 5.0. They downloaded the update, and now the tablet is stuck in a bootloop at the Fastboot screen.
There are only 3 options I can select from this screen in the top left using the volume keys: RESTART, RESTART BOOTLOADER & POWER OFF. Any time I select either of the restart options, the screen just goes blank and hangs. I have to manually power off, and upon turning back on I am right back to this limited Fastboot menu.
Bottom left reads:
FASTBOOT MODE
PRODUCT_NAME - E9LTE_VZW
VARIANT - e9lte_vzw Toshiba 16GB
HW VERSION - rev_10
BOOTLOADER VERSION - N/A
BASEBAND VERSION - N/A
CARRIER INFO - N/A
SERIAL NUMBER - VZ7005xxxxxxx
SECURE BOOT - disabled
LOCK STATE - locked
I booted into Recovery mode, but any of the options I select from the System recovery menu send me right back to the Fastboot screen.
Is there anything to be done at this point?
UPDATE: Problem solved. Research into the other variants of the LG G Pad lead me to the the LG Mobile Support Tool, which you can find by googling B2CAppSetup.exe.
Now, if you are stuck in a Fastboot loop as I was, I ended up having to restart the device while holding down the Power + Volume UP & DOWN. This brought up a screen displaying a bar code and the device MSN and IMEI number. Using this number return to the LG Mobile Support tool and select Options>Upgrade Recovery. Even if your device is already plugged in via USB, the software will not recognize the device -- you may want to double check to make sure your device drivers were installed prior to this step. Input your IMEI number into the box and restart the device in to download mode. It took a few attempts due to the quick action of Fastboot, but I was finally able to access the menu while USB was plugged in to the device and restarting while holding the Volume + key. Now you can continue with the installation and you will be back into your tablet in no time.
I have access to the device via usb / fastboot, adb is not registering. If anyone has any suggestions on what I can try, please let me know. I do not have a backup or a version of the OEM ROM. Every effort so far just sends me right back to the Fastboot screen with 3 options. Anything I can run from command prompt using fastboot alone that would help in this situation? Any way to do a factory restore without having an actual OEM image?
Well im stuck at the verizon screen too but for a different reason
JRSwole said:
So I just got an LG G pad 10.1 VK700 from Verizon the other day. I rooted the device on the first day but never really added any additional apps or software.
Another member in the household was using the tablet and it asked if they wanted to accept the VZW Update for KitKat 5.0. They downloaded the update, and now the tablet is stuck in a bootloop at the Fastboot screen.
There are only 3 options I can select from this screen in the top left using the volume keys: RESTART, RESTART BOOTLOADER & POWER OFF. Any time I select either of the restart options, the screen just goes blank and hangs. I have to manually power off, and upon turning back on I am right back to this limited Fastboot menu.
Bottom left reads:
FASTBOOT MODE
PRODUCT_NAME - E9LTE_VZW
VARIANT - e9lte_vzw Toshiba 16GB
HW VERSION - rev_10
BOOTLOADER VERSION - N/A
BASEBAND VERSION - N/A
CARRIER INFO - N/A
SERIAL NUMBER - VZ7005xxxxxxx
SECURE BOOT - disabled
LOCK STATE - locked
I booted into Recovery mode, but any of the options I select from the System recovery menu send me right back to the Fastboot screen.
Is there anything to be done at this point?
UPDATE: Problem solved. Research into the other variants of the LG G Pad lead me to the the LG Mobile Support Tool, which you can find by googling B2CAppSetup.exe.
Now, if you are stuck in a Fastboot loop as I was, I ended up having to restart the device while holding down the Power + Volume UP & DOWN. This brought up a screen displaying a bar code and the device MSN and IMEI number. Using this number return to the LG Mobile Support tool and select Options>Upgrade Recovery. Even if your device is already plugged in via USB, the software will not recognize the device -- you may want to double check to make sure your device drivers were installed prior to this step. Input your IMEI number into the box and restart the device in to download mode. It took a few attempts due to the quick action of Fastboot, but I was finally able to access the menu while USB was plugged in to the device and restarting while holding the Volume + key. Now you can continue with the installation and you will be back into your tablet in no time.
Click to expand...
Click to collapse
Hello I have the exact same model I got 28th my g4 and successfully rooted with kingroot and used supersume to change it to supersu. Everything was perfect and running fine and I tried an entropy engine I use on my other rooted phone and it was not help so I disabled it and rebooted like I have with my other one before and it stuck at that horrible red screen lol. I haven't done anything else major to alter anything to do with the OS like installing an OTA and I can only get to the same screens as you. My problem is I don't have a PC and haven't in a very long time and if I get to one I wouldn't know where to start out, last computer I owned has a floppy disk lol but I don't see how I would need to re flash the entire OS because of an entropy engine hickup. If you or anyone know of a way to slap this thing back to reality I would highly appreciate it. I got very familiar with the android os and how it works but never had a PC to go beyond a basic root so technically I'm still a noob in a way. I only care to expand dual window to other apps if I get it fixed cuz I'm not gonna risk screwing with it any more now than I have to, my luck is too bad lol thanks in advance
dadrumgod said:
Hello I have the exact same model I got 28th my g4 and successfully rooted with kingroot and used supersume to change it to supersu. Everything was perfect and running fine and I tried an entropy engine I use on my other rooted phone and it was not help so I disabled it and rebooted like I have with my other one before and it stuck at that horrible red screen lol. I haven't done anything else major to alter anything to do with the OS like installing an OTA and I can only get to the same screens as you. My problem is I don't have a PC and haven't in a very long time and if I get to one I wouldn't know where to start out, last computer I owned has a floppy disk lol but I don't see how I would need to re flash the entire OS because of an entropy engine hickup. If you or anyone know of a way to slap this thing back to reality I would highly appreciate it. I got very familiar with the android os and how it works but never had a PC to go beyond a basic root so technically I'm still a noob in a way. I only care to expand dual window to other apps if I get it fixed cuz I'm not gonna risk screwing with it any more now than I have to, my luck is too bad lol thanks in advance
Click to expand...
Click to collapse
If you are stuck in this particular Fastboot loop without a computer I am afraid your options are going to be very limited. The only thing I can imagine that you would be able to try is restarting the tablet while holding down the Power + Volume Down keys to access the stock System recovery menu. You can try to use Factory data reset and Wipe cache to see if that can resolve the issue, but for me every attempt to perform actions from this menu brought me right back to the Fastboot screen. The only other way I could communicate to the device in this scenario was using command line, and even then I could only access fastboot and not abd.
I would highly advise getting at least a cheap older laptop with Windows if you plan on rooting any device, otherwise the dangers will far outweigh the benefits. I'm just hoping some development comes along for the VK700 G Pad 10.1, at least a TWRP or CWM release.
JRSwole said:
If you are stuck in this particular Fastboot loop without a computer I am afraid your options are going to be very limited. The only thing I can imagine that you would be able to try is restarting the tablet while holding down the Power + Volume Down keys to access the stock System recovery menu. You can try to use Factory data reset and Wipe cache to see if that can resolve the issue, but for me every attempt to perform actions from this menu brought me right back to the Fastboot screen. The only other way I could communicate to the device in this scenario was using command line, and even then I could only access fastboot and not abd.
I would highly advise getting at least a cheap older laptop with Windows if you plan on rooting any device, otherwise the dangers will far outweigh the benefits. I'm just hoping some development comes along for the VK700 G Pad 10.1, at least a TWRP or CWM release.
Click to expand...
Click to collapse
Thanks for your response, I have unfortunately tried that too and wipe cache, reset , all back to fastboot. I figured it would be impossible without a pc. Oh yea my stock recovery says modified in the top left corner, but anyway I can get access to a PC But honestly it's been awhile since I even needed to use one and don't know exactly where to start, like navigating around, and how to install what software on the pc. I can't find anyone that will walk me through it locally or online and every tutorial I find is missing some lil step I need. I know Android in detail but after basic root my experience hits a brick wall. I'm capable of more jus got to get broke in on a pc again. Now I only care to root for stuff like freezing apps, gesture control, and really want to use any app in dual window. Ain't screwing with any system tweaks again it was pointless lol I guess I need all the right files and hit up the pc...can't really do worse no??
Sent from my VS986 using Tapatalk
JRSwole said:
If you are stuck in this particular Fastboot loop without a computer I am afraid your options are going to be very limited. The only thing I can imagine that you would be able to try is restarting the tablet while holding down the Power + Volume Down keys to access the stock System recovery menu. You can try to use Factory data reset and Wipe cache to see if that can resolve the issue, but for me every attempt to perform actions from this menu brought me right back to the Fastboot screen. The only other way I could communicate to the device in this scenario was using command line, and even then I could only access fastboot and not abd.
I would highly advise getting at least a cheap older laptop with Windows if you plan on rooting any device, otherwise the dangers will far outweigh the benefits. I'm just hoping some development comes along for the VK700 G Pad 10.1, at least a TWRP or CWM release.
Click to expand...
Click to collapse
Oh yea I almost forgot I got side tracked earlier. I know there is already a twrp, I have 2 versions (2.8...something and the next version strait off twrp site. I was the one guy it wouldn't flash through flashify for but others claimed it did. God knows really, but I'm gonna wait till I have a PC of my own before I touch my g4 but man the ability to open any app in dual window is just too damn sweet...if I could only change that one word on build prop to false without all the other hassle
Sent from my VS986 using Tapatalk
JRSwole said:
Now, if you are stuck in a Fastboot loop as I was, I ended up having to restart the device while holding down the Power + Volume UP & DOWN. This brought up a screen displaying a bar code and the device MSN and IMEI number. Using this number return to the LG Mobile Support tool and select Options>Upgrade Recovery. Even if your device is already plugged in via USB, the software will not recognize the device -- you may want to double check to make sure your device drivers were installed prior to this step. Input your IMEI number into the box and restart the device in to download mode. It took a few attempts due to the quick action of Fastboot, but I was finally able to access the menu while USB was plugged in to the device and restarting while holding the Volume + key. Now you can continue with the installation and you will be back into your tablet in no time.
Click to expand...
Click to collapse
I tried following your recommendation, but the LGMobile Support Tool said the device wasn't plugged in no matter which combination of buttons I pushed while running the Upgrade Recovery option, and I wasn't able to figure out how to get to download mode either.
gnomesinrome said:
I tried following your recommendation, but the LGMobile Support Tool said the device wasn't plugged in no matter which combination of buttons I pushed while running the Upgrade Recovery option, and I wasn't able to figure out how to get to download mode either.
Click to expand...
Click to collapse
If your problem is from an OTA failing due to taking it while modded and you can get to fastboot the following command might fix it:
Code:
fastboot erase cache
That will delete the OTA zip and break the bootloop.
Hi everyone, today my Elephone p8000 with stock rom (no root nor recovery installed) proposed me an OTA update, and I did it.
After installing the update the phone is stuck at the boot animation logo. If I boot in factory mode (volume down + power button) I am presented with a bunch of options in Chinese, which I don't understand. If I go in recovery mode (volume down + power button) it says "no command".
What can I do? What are my options? Is it bricked?
Yup mine too. Mine has root, with no custom recovery. Get the same boot loop and the sad open Android 'no command'.
Haven't had a chance to dig around for a solution but I suspect it is a case of using the flash tool to wipe and load a standard ROM? Hopefully an easier way.
kevvyboy said:
Yup mine too. Mine has root, with no custom recovery. Get the same boot loop and the sad open Android 'no command'.
Haven't had a chance to dig around for a solution but I suspect it is a case of using the flash tool to wipe and load a standard ROM? Hopefully an easier way.
Click to expand...
Click to collapse
Damn. I had huge problems with the flash tool in the past (I don't have a Windows PC) and the idea of spending the weekend trying to get the damn thing work is not a fun one.
Got this issue too this morning on way to work, I guess my phones useless today until I get home to try and flash it.
seem to be able to get to the boot select screen but nothing is different anyway, also managed to get into a "PCBA" mode that did a load of tests to the phone but thats it.
it now just died, not powering on, think its bricked :crying:
skea said:
it now just died, not powering on, think its bricked :crying:
Click to expand...
Click to collapse
Probably just out of power. Try charging it for a while and/or download and flash entire rom using sp flash except for data-partition so as you don't lose your data.
pitrus- said:
Probably just out of power. Try charging it for a while and/or download and flash entire rom using sp flash except for data-partition so as you don't lose your data.
Click to expand...
Click to collapse
thanks it was out of power lol
I just had the same problem. Did you solved it?
Like, exactly the same... Crazy
Another one
My p8000 also in bootloop after ota update. Only have an old vista PC w8ll dust it off tonight and see what happens
mines doing the same i thought it was too good to be true and it was lol
Cannot get pc (win 10) to install all the drivers, PC cannot see the phone so unable to run flash tool.
Suggestions? I presume the ROM cannot be flashed through the recovery (standard)?
EDIT: Driver package installed by disabling 'driver verification' setting in Windows. Phone only recognised as a MTP USB Device in devide manager, and flash tool does not seem to want to do anything. Might try this on a Win 7 laptop tomorrow. HJow you guys getting on with this?
Success - I Have a Working Phone
(or, How Chest Pains and Rage Focused the Mind)
So. This is what worked for me. Win 10. P8000 bootloop.
1) put p8000 into recovery, chose 'power off'. (I couldn't seem to stop it rebooting using the power button)
2) installed driver pack by disabling the Windows install signed drivers only setting. Rebooted. This turns the setting back on, but the drivers have alrwady been installed, no issue with that.
3) installed the flash tool. Brief panic at Chinese chars, located English. Calmed down.
4) loaded flash tool, with ROM ready to go.
5) this is the biggie, this is what brought it all together.........connected the powered down p8000 via USB and IMMEDIATELY hit the download button in the flash tool - ie BEFORE a new instance of USB bing-bong-device-connected sound.
6) once all downloaded, disconnect phone, reboot. Took an extended time (few mins) to boot, enough time to almost start swearing under my breath, but it just needed some patience.
Now, what I spent some time unsuccessfully trying to fix - needlessly as it turns out - was what my phone appeared under 'Device Manager'. It still lists it as an MTP USB Device under the 'Portable Devices' submenu. It did not seem to matter, as long as all the driver were installed.
I wish you all the best of luck in solving your issues, hopefully some of what I wrote can be helpful.
pitrus- said:
download and flash entire rom using sp flash except for data-partition so as you don't lose your data.
Click to expand...
Click to collapse
I have the same boot loop after ota. I did no backup before, so data partition contains my apps right ?
I never used the flash tool , where should I start , any good link for beginners ?
I read some things about the flash options months ago, must I disable/uncheck some options ?
Thanks for help.
same issue
Hi everyone!
I've got the same issue: I allowed the OTA update to 20151105 firmware release from previous version (20150725), after the upgrade, the phone keeps in a bootloop with a new colored Elephone logo.
I can't find a valid set of drivers, I tried a lot over the night, but windows don't recognize the phone.
PLEASE some kind soul could link a valid driver package to use SP tool ?
thanks a lot in advance!
mr..speed said:
I have the same boot loop after ota. I did no backup before, so data partition contains my apps right ?
I never used the flash tool , where should I start , any good link for beginners ?
I read some things about the flash options months ago, must I disable/uncheck some options ?
Thanks for help.
Click to expand...
Click to collapse
kevvyboy said:
Success - I Have a Working Phone
(or, How Chest Pains and Rage Focused the Mind)
So. This is what worked for me. Win 10. P8000 bootloop.
1) put p8000 into recovery, chose 'power off'. (I couldn't seem to stop it rebooting using the power button)
2) installed driver pack by disabling the Windows install signed drivers only setting. Rebooted. This turns the setting back on, but the drivers have alrwady been installed, no issue with that.
3) installed the flash tool. Brief panic at Chinese chars, located English. Calmed down.
4) loaded flash tool, with ROM ready to go.
5) this is the biggie, this is what brought it all together.........connected the powered down p8000 via USB and IMMEDIATELY hit the download button in the flash tool - ie BEFORE a new instance of USB bing-bong-device-connected sound.
6) once all downloaded, disconnect phone, reboot. Took an extended time (few mins) to boot, enough time to almost start swearing under my breath, but it just needed some patience.
Now, what I spent some time unsuccessfully trying to fix - needlessly as it turns out - was what my phone appeared under 'Device Manager'. It still lists it as an MTP USB Device under the 'Portable Devices' submenu. It did not seem to matter, as long as all the driver were installed.
I wish you all the best of luck in solving your issues, hopefully some of what I wrote can be helpful.
Click to expand...
Click to collapse
kevvyboy said:
Success - I Have a Working Phone
(or, How Chest Pains and Rage Focused the Mind)
So. This is what worked for me. Win 10. P8000 bootloop.
1) put p8000 into recovery, chose 'power off'. (I couldn't seem to stop it rebooting using the power button)
2) installed driver pack by disabling the Windows install signed drivers only setting. Rebooted. This turns the setting back on, but the drivers have alrwady been installed, no issue with that.
3) installed the flash tool. Brief panic at Chinese chars, located English. Calmed down.
4) loaded flash tool, with ROM ready to go.
5) this is the biggie, this is what brought it all together.........connected the powered down p8000 via USB and IMMEDIATELY hit the download button in the flash tool - ie BEFORE a new instance of USB bing-bong-device-connected sound.
6) once all downloaded, disconnect phone, reboot. Took an extended time (few mins) to boot, enough time to almost start swearing under my breath, but it just needed some patience.
Now, what I spent some time unsuccessfully trying to fix - needlessly as it turns out - was what my phone appeared under 'Device Manager'. It still lists it as an MTP USB Device under the 'Portable Devices' submenu. It did not seem to matter, as long as all the driver were installed.
I wish you all the best of luck in solving your issues, hopefully some of what I wrote can be helpful.
Click to expand...
Click to collapse
pretty much did the same thing and it worked!! Cheers!! (also had the rage and it took ages to find english on the tool lol :laugh: )
when you get the android with the "no command" message, let go of the volume and power buttons. Then hold the POWER BUTTON for 1-2 seconds and TAP VOLUME UP while still holding the power button. this will open the recovery options
omg!!
disabling the Windows install signed drivers only setting!!
i thought we wouldnt have to do things like this since Windows 95
Lol
Worked for me
Had I only found this tutorial before yesterday... it took me hours to figure this out.
I can, however, now confirm this works.
Regarding point 5):
(i) Power down phone (ii) start flash tool/go to download tab (iii) select scatter file (iv) hit "download" with no phone attached (v) attach the powered down phone
...and things will be fine. Doing anything fast is not required.
The point is to install SP_Drivers_v2.0 first, as described here. After this, everything goes smooth.
kevvyboy said:
Success - I Have a Working Phone
(or, How Chest Pains and Rage Focused the Mind)
So. This is what worked for me. Win 10. P8000 bootloop.
1) put p8000 into recovery, chose 'power off'. (I couldn't seem to stop it rebooting using the power button)
2) installed driver pack by disabling the Windows install signed drivers only setting. Rebooted. This turns the setting back on, but the drivers have alrwady been installed, no issue with that.
3) installed the flash tool. Brief panic at Chinese chars, located English. Calmed down.
4) loaded flash tool, with ROM ready to go.
5) this is the biggie, this is what brought it all together.........connected the powered down p8000 via USB and IMMEDIATELY hit the download button in the flash tool - ie BEFORE a new instance of USB bing-bong-device-connected sound.
6) once all downloaded, disconnect phone, reboot. Took an extended time (few mins) to boot, enough time to almost start swearing under my breath, but it just needed some patience.
Now, what I spent some time unsuccessfully trying to fix - needlessly as it turns out - was what my phone appeared under 'Device Manager'. It still lists it as an MTP USB Device under the 'Portable Devices' submenu. It did not seem to matter, as long as all the driver were installed.
I wish you all the best of luck in solving your issues, hopefully some of what I wrote can be helpful.
Click to expand...
Click to collapse
What if no Windows?
Edit: Never mind, I got myself a windows computer and succeeded. Thanks for all the orientation!
Hi all,
Thanks a lot for posting a solution to this problem so quickly. I am affected by the same issue. Looking to buy some LSD to better enjoy the psychtrip my phone seems to be stuck in. Also looking to fix the phone.
Unfortunately, I'm running Ubuntu 14.04 LTS. I did find a guide to use the flash tool on Ubuntu, but my phone does not seem to connect. I'm guessing this has something to do with that pack of drivers 2.0, for which I have no equivalent. I would really appreciate any ideas!
I might end up returning my phone to Amazon, though. It's only been a few days since I've had it, and you can imagine that although I was really liking it, I'm beginning to change my mind.
Your advice?
EDIT: I am getting the following error message:
BROM ERROR: S_COM_PORT_OPEN_FAIL (1013)
[COM]: Failed to open COM port.
[HINT]:
I did some googling, but didn't find anything worth mentioning.
yslsl said:
Had I only found this tutorial before yesterday... it took me hours to figure this out.
I can, however, now confirm this works.
Regarding point 5):
(i) Power down phone (ii) start flash tool/go to download tab (iii) select scatter file (iv) hit "download" with no phone attached (v) attach the powered down phone
...and things will be fine. Doing anything fast is not required.
The point is to install SP_Drivers_v2.0 first, as described here. After this, everything goes smooth.
Click to expand...
Click to collapse
Ahh good stuff. Connect phone last after hitting download - thanks for the heads up. Got my wife's p8000 today so will be doing some flashing later.
Cheers!
Hello Everyone!
I recently tried to root my wileyfox swift but failed miserably. I did the following when fastbooting the recovery image -> fastboot flash system ****.img.
However, i realized my mistake too late, and now my phone is all messed up!
The phone doesnt show anything when i try to start it and i cant access fastboot again, to undo my mistake. My device manager recognizes my phone when its plugged in to my computer but i cant access any files.
Am i screwed or is there any solution to this?
Thanks in advance!!
Try to access the bootloader with the hardware button combo first (volume down + power / volume up + power). If you get into recovery, you will be able to get to the bootloader with adb or a menu entry. Depends on what recovery you have installed for the latter.
In case you have no access to the bootloader (proper soft brick), go for the QFIL method. Avoid using it unless there is no other option.
Here is the thread:
http://forum.xda-developers.com/wileyfox-swift/general/how-to-set-device-tampered-to-false-t3276317
Cant access bootloader.
However, tried your second option and it went well until i got "SaharaDownload fail" at the last step, and now my computer doesnt recognize the phone in device manager. It does not show anywhere that my phone is connected.
narmista said:
Cant access bootloader.
However, tried your second option and it went well until i got "SaharaDownload fail" at the last step, and now my computer doesnt recognize the phone in device manager. It does not show anywhere that my phone is connected.
Click to expand...
Click to collapse
Does the phone give any indication of being connected? Notification light, starting the display, etc?
If yes, make sure the phone is in the correct mode and check the drivers - some of the other forum members mentioned this and the gymnastics around the battery. This would be on my to-do list. The device might come up on the device manager as different one, so monitor the manager for any changes once you connect the device.
If you happen to have Windows 7 device laying at you house, you can try with it (if only not to worry about compatibility and sporadic Win10 behaviour).
It will be a good idea to check the turkish website for General Mobile 4G (one of the Android one derivatives of the hardware) where some people have faced similar problems using the same tool.
narmista said:
Cant access bootloader.
However, tried your second option and it went well until i got "SaharaDownload fail" at the last step, and now my computer doesnt recognize the phone in device manager. It does not show anywhere that my phone is connected.
Click to expand...
Click to collapse
If you need my help via TeamViewer then WhatsApp me at +27799261595 or pm me
Finally got my phone back on the device manager! However, I still get sahara error when trying the back to false method.
imgur.com/a/FsSX0
*It says no port available since i removed the phone*
Hello Gurus,
Well i am trying to boot my phone into download mode but i am continuously getting
secure booting error 1014 and my phone then boots lollipop 5.1 which is stock rom.
my lg g4 model is h81510h build number lmy47d, it is not rooting or flashed anyway.
I want to flash flash marshmallow kdz with lg flash tool but my phone is not booting into download mode, please help or suggest any other method
HALP PLS
I'm having more or less the same problem. I bought a used H815 and it came with Android 5.1 (software version h81510h)rooted and stock recovery. I tried upgrading to MM over OTA but tapping Update Center leads me directly to the App Update screen instead of giving me a choice between software update and app update.
That is when I decided to go the KDZ route but when i tried switching the phone to download mode it went there and in the top left corner there was this 'Secure Booting Error 1014' message and then it restarted in about 5 seconds. I have tried this multiple times with the same exact result.
ADB detects my phone but when I send the 'reboot bootloader' command it just does a plain reboot so I can't use any of the fastboot commands. I also have no idea whether this phone has an unlocked bootloader or not.
Also for some weird reason my phone is not using the MTP mode when I connect it to my PC. It either uses PTP or charge-only depending on what I select but if I select MTP it automatically reverts to the previously selected mode. LG Bridge doesn't detect it and neither does the Mobile Support Tool but I can transfer images just fine. MTP was working last night but it suddenly stopped working and I have no clue why.
I can get into the recovery without any problems.
Please help me get it working again
you-mair said:
I'm having more or less the same problem. I bought a used H815 and it came with Android 5.1 (software version h81510h)rooted and stock recovery. I tried upgrading to MM over OTA but tapping Update Center leads me directly to the App Update screen instead of giving me a choice between software update and app update.
That is when I decided to go the KDZ route but when i tried switching the phone to download mode it went there and in the top left corner there was this 'Secure Booting Error 1014' message and then it restarted in about 5 seconds. I have tried this multiple times with the same exact result.
ADB detects my phone but when I send the 'reboot bootloader' command it just does a plain reboot so I can't use any of the fastboot commands. I also have no idea whether this phone has an unlocked bootloader or not.
Also for some weird reason my phone is not using the MTP mode when I connect it to my PC. It either uses PTP or charge-only depending on what I select but if I select MTP it automatically reverts to the previously selected mode. LG Bridge doesn't detect it and neither does the Mobile Support Tool but I can transfer images just fine. MTP was working last night but it suddenly stopped working and I have no clue why.
I can get into the recovery without any problems.
Please help me get it working again
Click to expand...
Click to collapse
Any update ? I am also facing same issue. One wierd thing I noticed that adb devices displays phone as "LGLS991" can you tell me your result of adb devices ?
Im having the same problem.
Lg bridge, lgup and flashtool not detecting my phone. How to flash my phone with any os? Kindly help me
Same problem with my H811. Any solutions?
I cant get my g4 into download mode. I was able to earlier but it died on me. My buddy has the same phone so I am using his fully charged battery now (mine was around 40$) but I'm still getting nothing. Should I reformat the SD card and try again? I can't think of anything else.
Hello everyone! I hope you're doing well. I'm new here and I'm facing a problem that I can't seem to solve, so I'm here to ask for your help.
CONTEXT: My girlfriend had a phone whose screen broke. She couldn't afford to buy a new one, and neither could I help financially. But I had two old devices: a Motorola G1 (which I used to store some things and do simple tasks) and a Lenovo Vibe K5 Plus, which was the one I was using. Since I had just graduated from college and she hadn't, she had a greater need than me for a slightly better phone. So I gave her my Lenovo and I'm using the Motorola. When the Lenovo was still with me, I had put a custom ROM on it from Lineage (I think it was Android Nougat, if I'm not mistaken) and it also had TWRP. Before giving it to her, I only did a quick format of the phone.
A few days ago, there was a problem with the Lenovo and Android no longer worked. The phone turned on, entered the Lineage boot screen, but when it tried to turn on Android, a message appeared saying that Google's text-to-speech had continuously failed, and the phone turned off. She brought it to me yesterday and I thought about installing the original stock ROM on the device. With difficulty, I managed to get the laptop (Windows 10) to recognize the phone when it turned on. The difficulty was because when I tried to turn it on, the screen kept flashing on the Lenovo. I opened the device, took out the battery, waited for a while, and miraculously managed to turn it on. When it turned on, the laptop installed the device before it turned off. Through ADB, I managed to get the device to reboot directly to recovery, since I couldn't access recovery through the physical buttons on the device.
So, I managed to make a backup of the files that were important to my girlfriend and that were on the phone's internal memory. After that, I formatted the device through TWRP using the "format data" button. Still, I used the wipe to erase everything except for "USB-OTG" and the memory card option (which I had removed along with the SIM card before trying the procedure). After that, I restarted the phone to enter TWRP directly.
PROBLEM: After doing this, I tried to install the stock ROM using ADB sideload, but it said there was something wrong with the image I was using. The sideload gave an error message and said that the phone needed to be restarted. I restarted it from this screen by sliding my finger to the right, and... the phone no longer turned on and wasn't recognized by the laptop! I can't access TWRP through the physical buttons (at least not through the traditional method I know, which is the volume up button and the power button), ADB doesn't recognize the phone, and I don't know what else to try.
QUESTION(S): How can I force the laptop to recognize the device so that I can make it reboot directly to TWRP, since the device doesn't turn on for long enough for Windows to try to check the drivers? Or has TWRP been corrupted? If so, how can I install TWRP again? Is there any other way to access recovery? Is there any other way I can use to install the stock ROM? We can't afford to take it for repair at this time (the situation here in Brazil is very bad), much less afford to buy a new device. Does anyone have any other ideas on how I can access recovery or how I can install a ROM without necessarily turning on the device? Or any other ideas?
I really appreciate anyone who read this far and, in advance, I thank anyone who can help me. Gratitude!