I installed this rom: (https://forum.xda-developers.com/g4/development/h815-nougat-stock-t3659860) the correct way through TWRP and having an unlocked bootloader and then the rom worked well, but then i thought i still had the TWRP as a recovery so i tried to enter the recovery mode by pressing power button+lower volume button. afterwards i clicked twice yes. so the phone rebooted and the rom didn't work anymore. So tried to find a solution by searching XDA forums and the internet. Since my previous version was MM i found LGUP which could restore the phone to its previous ROM. however i am now having issues with LG UP. i tried several methods:
the 1st one was: from https://forum.xda-developers.com/g4/...mm-lp-t3249803 with the H81520D_00_0115.kdz file and the DLL files which came with the software itself. This always led me to 25% after which LG UP would crash and give a "error code = 0x2000 invalid command response at system". then i tried a different DLL from: https://forum.xda-developers.com/g4/...-file-t3586220 #6 which led me to have the error at 11%.
the 2nd one was: from https://forum.xda-developers.com/g4/...-h815-t3673777 #6-#11 so tried this method with these DLL files and by reinstalling LG UP and the driver, also by using the H81520p_00_0314.kdz file. but now i have the issue that LGUP gets stuck at 4% "USB connection established" and will automatically close the program and windows will show me that "LGUP has stopped working".
the 3rd one was: using LG bridge and hoping it will reset the phone. but nothing it just says that the phone has no software issues and that i have the latest software which is H81529a.
Lastly i tried to get flash twrp-3.1.1-1-g4.img through fastboot and was able to flash the recovery by using "fastboot flash recovery twrp-3.1.1-1-g4.img", however i was not able to get into the recovery because when i typed "fastboot boot twrp-3.1.1-1-g4.img" i would get an error (can be seen in the picture). so i tried to enter the recovery manually by pressing power button+lower volume button, and releasing the power button for 1 second and the pressing the powerbutton again, afterwards i clicked twice yes in the white screen, but this got me to download mode and not into TWRP (can be seen here: https://www.youtube.com/watch?v=xai6_8T8BgI)
I am now stuck and don't know what to do, and was hoping you guys could help me? I am using a PC with WIN 10 and i can boot into Fastboot mode and Download mode
Rmegaxx said:
Lastly i tried to get flash twrp-3.1.1-1-g4.img through fastboot and was able to flash the recovery by using "fastboot flash recovery twrp-3.1.1-1-g4.img", however i was not able to get into the recovery because when i typed "fastboot boot twrp-3.1.1-1-g4.img" i would get an error (can be seen in the picture). so i tried to enter the recovery manually by pressing power button+lower volume button, and releasing the power button for 1 second and the pressing the powerbutton again, afterwards i clicked twice yes in the white screen, but this got me to bootloader and not into TWRP (can be seen here: https://www.youtube.com/watch?v=xai6_8T8BgI)
I am now stuck and don't know what to do, and was hoping you guys could help me? I am using a PC with WIN 10 and i can boot into Fastboot mode and Download mode
Click to expand...
Click to collapse
Suggest you post your issue re: TWRP to steadfasterX's thread: [RECOVERY][h815/h811][OFFICIAL][MM][LL] TWRP 3 touch recovery [2017-06-21]
https://forum.xda-developers.com/g4/development/recovery-twrp-3-touch-recovery-t3442424
after reading through the OP thoroughly and seeing if any of the member's posts match your issue.
steadfasterX has proven very helpful to numerous members with issues.
Related
I have been having issues trying to update my rooted zenfone 2 to 40.168. I found out that I am unable to get into recovery since I have been trying to update. I was able to enter recovery mode before during and after I rooted my phone. When I try to enter recovery mode, it does not go to the error android anymore, instead it goes back to fastboot screen. No matter how many times I try to enter recovery mode, the phone just reboots. I have tried unrooting by uninstalling xposed and unrooting through supersu, but this did not change the fact that I can not enter recovery or update ota. The second method I tried was using ADB sideload: once I got to the step to enter the code 'adb sideload file.zip', it did not recognize the command. The third method I tried was clearing the cache with fastboot format cache but it said permission denied. I just recently attempted another method of updating ota while rooted but still no success. In fact I think I made it worse now because my phone has just randomly rebooted three times within about 2 minutes of being on. The last thing I tried before I am getting these random reboots was steps to apply OTA manually.
I followed these steps..
Download the OTA file from here, check under ota update heading [get the latest one ,check the version number]
rename the OTA zip which you download to "MOFD_SDUPDATE" zip[verify with this pic], paste the renamed zip in external memory[not in internal, tried to place in internal but it didnt work]
now power off, Once it is off, hold down the volume up button and hold on to the power button until the phone vibrates. After the vibration stops, release the power button and continue pressing the volume up button until the green Android robot appears. You should see a blue line below saying "Waiting Fastboot command" ,Now here click vol down till you see Recovery mode in top big rectangle box,now click power button,and thats all it will update your phone..
I have nearly lost hope and I am thinking about a full reformat of the device if I can even get to settings and restore to factory without it randomly rebooting again. I did not need the latest update however I wanted it. Hopefully someone here can help me.
UPDATE1:
Somehow the random reboots have stopped while I am typing this. Just fyi.
UPDATE2:
So I tried to flash the prerooted img of 168 to my phone via fastboot but every command I entered, I recieved permission denied. I still continued with every command and after I finished I wanted to reboot normally to see if it changed anything. I ended up getting my phone stuck on asus boot logo screen(or bricked).. I just booted into fastboot again and attempted to enter recovery mode again. Now recovery mode is actually doing 'Installing system update' like I wanted it to before but it didn't till now!.. It is making progress and is about 1/4th complete so I will keep this thread updated.
UPDATE3: SO that did fix it. I guess I had to brick my phone in order to fix my recovery lol. Now I am going to try to root this 168 version. Thanks for no help people I didn't need it anyways
You're welcome, remember we are all at your beck and call 24/7 (we even have a TARDIS to go back in case you need our help and no one is available) Just hold your breath while someone pops back to help you...
Glad you got it up and running again but seriously, you ask for help and fix it yourself in less than 1 1/2 hours... How many people are available to help you in that time, we all have lives too...
I think I bricked my G3 :/
I tried usual methods but couldn't get into recovery or download mode, then a few days ago I realized I could get it into this fastboot mode by holding volume up and plugging into USB as you would normally do to get into download mode but you have to hold up for a minute or so (it shows the download mode icon for a few seconds and then goes to fastboot) when in fastboot it connects to the computer and shows in device manager as "android device" and the phone says "processing commands" So I tried to follow this guide http://forum.xda-developers.com/showthread.php?t=2785089 to return it to stock, but I couldn't get it to show up in the LG software.
I read some forum posts about fastboot mode and found that by using the command "fastboot boot twrp.img" (the recovery image I downloaded) in command prompt it would send it to the phone and the phone would display some info and then reboot into TWRP, from here I tried to install a correct rom but the installation starts and there are some errors and then it hangs. I also tried the command "fastboot flash recovery twrp.img" but it fails. This is as far as I have got with it.
It came to me in this condition but the previous owner said he was running Cyanogen and it was working fine until he tried to update it with a nightly build. I suspect he might've tried to install the wrong rom for the phone or the rom was corrupt.
ou could try to revive the phone doing a testpoint and then use boarddiag tools (look in xda thread).
Here is how to make a testpoint: http://forum.xda-developers.com/showpost.php?p=65002893&postcount=17
So I already had a rooted (and I'm pretty sure unlocked bootlader) version of the stock Asus and wanted to put CM13 nightly on there. Everything was going smooth until I got to the stage where I have to load into TWRP and I got the error screen with the little dead alien and the red symbol.
Now I can't enter normal boot, but entering recovery mode seems to work. I tried the option to side load a package from ADB on that screen but nothing worked (.zip files extracted, but I got an error on the phone).
As you can tell, I'm really new to this so any help would be greatly appreciated. I tried looking around, but it seems the more common issue is people not being able to enter recovery mode or something similar.
Thanks
Looks like your doing it wrong. Being rooted does not necessarily mean that your bootloader is unlocked.
By the looks of it your in recovery mode with the dead robot with the "error" message. That is normal. To reboot back into system you either have to press (I don't remember) power button and volume up or down button. Then you should see some options with reboot to system. Or if that does not work you can hold the power button till it turns off.
Then you get back into Android, download the official bootloader unlock tool from ASUS and install it on your device. NOTE: If you updated to MM then this will not work and this will void your warranty.
Run the tool and press unlock and it should reboot into fastboot where it should begin the unlocking process. I believe it should automatically reboot and you should see that the Asus logo is now black instead of white. If not, repeat the process.
You can now proceed to flash twrp recovery. Boot into fastboot/bootloader mode either with "adb reboot bootloader" or hold a specific set of buttons while off to go directly into fastboot.
On the computer, connect your device and type in "fastboot flash recovery (path to twrp IMG without brackets)"
When done you should be able to reboot into twrp recovery where you can flash the cm13 zip.
Hope this helped.
Hello there,
we have here a Swift that is stuck on a starting screen since an attempt to downgrade from Cyanogenos 13.1 to Cyanogenmod 12.1. Bootloader ist unlocked and to my knowledge only the recovery was flashed via fastboot.
As soon as the USB cable is connected, the screen goes on with "Wileyfox(with logo) powered by android" and remains there.
Luckily fastboot works, but I can't get into recovery. Neither by selecting "reboot into recovery" from fastboot nor by "Vol-" + "Power".
I tried to reflash Cyanogenos 13 via fastboot as it was suggested in several threads (i.e. unzip and flash the different files step by step). Fastboot always stated success, but no luck... Still the same starting screen.
I even tried flashing TWRP recovery, no change either.
Is there something else I can try?
Thank you all
SOLVED: I was persistent: one other threads regarding a lenovo phone suggested to hold down Power and VolDn continuously for several minutes. After about a minute or so and multiple (min. 15x) power off/ons to the "powered by android" screen, I finally got into TWRP! After a format /data I was able to flash the desired CM.
I hope this helps others with similar problems
Erdbeerfrosch said:
Hello there,
we have here a Swift that is stuck on a starting screen since an attempt to downgrade from Cyanogenos 13.1 to Cyanogenmod 12.1. Bootloader ist unlocked and to my knowledge only the recovery was flashed via fastboot.
As soon as the USB cable is connected, the screen goes on with "Wileyfox(with logo) powered by android" and remains there.
Luckily fastboot works, but I can't get into recovery. Neither by selecting "reboot into recovery" from fastboot nor by "Vol-" + "Power".
I tried to reflash Cyanogenos 13 via fastboot as it was suggested in several threads (i.e. unzip and flash the different files step by step). Fastboot always stated success, but no luck... Still the same starting screen.
I even tried flashing TWRP recovery, no change either.
Is there something else I can try?
Thank you all
SOLVED: I was persistent: one other threads regarding a lenovo phone suggested to hold down Power and VolDn continuously for several minutes. After about a minute or so and multiple (min. 15x) power off/ons to the "powered by android" screen, I finally got into TWRP! After a format /data I was able to flash the desired CM.
I hope this helps others with similar problems
Click to expand...
Click to collapse
I've got the same problem. How id you solve yours?
I did hold the VolumeDown+Power buttons for 5 minutes and I did not get into recovery at all (this was with latest TWRP version 3.1.1-0)
Then I thought it could be the TWRP version, and I tried 3.0.3-0 and finally 3.0.0-0.
After flashing 3.0.0-0 I typed "fastboot reboot" and immediately after pressed VolumeDown+Power on the phone and ... finally was in recovery mode, where I could install microG's lineageos version.
cweiske said:
I did hold the VolumeDown+Power buttons for 5 minutes and I did not get into recovery at all (this was with latest TWRP version 3.1.1-0)
Then I thought it could be the TWRP version, and I tried 3.0.3-0 and finally 3.0.0-0.
After flashing 3.0.0-0 I typed "fastboot reboot" and immediately after pressed VolumeDown+Power on the phone and ... finally was in recovery mode, where I could install microG's lineageos version.
Click to expand...
Click to collapse
hi could you post exactly what you did line by line inc code plz i have twrp 3 img just need to get it over i must be typing something wrong.
thanks
im having a problem, my phone wont go out of fast boot mode, tried everything
Any suggestions??
Here is the correct fix, at least it worked for me,
https://forum.xda-developers.com/showpost.php?p=66158015
For those that, like me, could not get driver recognition on the latest Win 10 x64 no matter what you tried. And ,yes, using every tutorial I could find on this and two "other Forums". Odin failed to see my device (still can't) Cydia impactor allows rebooting into fastboot and D/L but doesn't connect in either alt. mode. Yes, drivers all removed and replaced in varying states (usbdeview, etc.).
But ADB/Fastboot works!
Make sure you have your adb/fastboot drivers installed universally (Check this Fabulous Forum)
Download device-specific TWRP - I used this one for the 4gb version - https://www.dropbox.com/s/b7u3k1mgpppxlyx/recovery.img?dl=0
L.Shift-R. click in the folder you downloaded to (Open Command Window Here) - "adb devices" (to make sure device registers) then - "adb reboot bootloader" gets you into fastboot. - "fastoot boot {your-recovery-name}.img"
I got a fully functional TOUCH CAPABLE TWRP. Which I proceeded to load this - https://www.dropbox.com/s/j1owqv7mjkdpo75/UPDATE-SuperSU-v2.46.zip?dl=0 - and, VOILA! ROOT!!
I had similar issues with my laptop and drivers. Used a friend laptop in the end to "see" the phone and install twrp.
Sent from my S7 using Tapatalk
When I try to boot the recovery.img with fastboot it says that my OEM is locked. I check OEM unlock in developer options, then I do: adb reboot bootloader, then fastboot oem unlock. A warning appears saying to press VOLUME UP button to continue, voiding the warranty or VOLUME DOWN to go back. I try to press VOLUME UP and nothing happens... how did you do it?
vaskovass said:
When I try to boot the recovery.img with fastboot it says that my OEM is locked. I check OEM unlock in developer options, then I do: adb reboot bootloader, then fastboot oem unlock. A warning appears saying to press VOLUME UP button to continue, voiding the warranty or VOLUME DOWN to go back. I try to press VOLUME UP and nothing happens... how did you do it?
Click to expand...
Click to collapse
Hi there, I have the same issue. No success
I found a way, instead of volume up, use the home button this worked for me.. however after I unlocked the OEM and flashed TWRP the phone didn't want to boot anymore. It was stuck on Elephone logo with warning: "Orange State: The phone has been unlocked and can't be trusted. Your device will boot in 5s", however it didn't boot and stayed like that for almost an hour. Had to flash back the stock firmware to boot. Tried 1 more time the procedure to root but again the same. Maybe I do something wrong?
stock fw flash back
Hi, please can you help me with how you flashed back the stock firmware?
I get an error message with twrp : invalid zip file format.
Thank you in advance!
dnsgtr said:
Hi, please can you help me with how you flashed back the stock firmware?
I get an error message with twrp : invalid zip file format.
Thank you in advance!
Click to expand...
Click to collapse
I read somewhere the is a zip inside the update.zip & is that one that is flash able with twrp.
Have a look
During the main time I managed to flash the 0218 stock rom.
I still got the orange message but the phone finally boot. Then I just called the twrp recovery img via atb. I did nothing only touch the reboot in the twrp screen and since then "Orange status...." again.
May be the twrp recovery img is not the right one...
Bad command "fastoot boot {your-recovery-name}.img"
after OEM alow (informacion phone/compilacion number touch fast 9 times/access/alow oem)
fastboot oem unlock
"fastboot boot {your-recovery-name}.img" for me is fastboot boot recovery.img and all OK
bat still not working (phone not thrust unlocked bootloader cleaning data in 5..4..3..2..1.. and rebot)