Related
Hi guys, I hate to make a new post but I feel like I've exhausted all options. I'm getting a bootloop when flashing Viper 3.5.0 and ARHD 12.0. I have a T-Mobile GSM M9 with S-OFF . My bootloader currently locked. Here are my steps:
1. I've got Super CID
2. Flashed TWRP 2.8.7.0
3. Rooted
Then I wanted to put on a new rom:
4. Flashed different firmware from here: http://forum.xda-developers.com/one-m9/development/firmware-t3068243
I've tried 2.10.401.1 (International) / 2.7.531.6 (T-Mobile US) / 1.32.531.33 (T-Mobile US)
5. Flashed Viper 3.5.0 and AHD 12.0 with the wipe option after each firmware upgrade/downgrade. Each time I boot the phone up (no matter what firmware is used), Android will optimize all the apps, and it will sit at the Android setup screen for a second or two, and then just reboot. Android will optimize all apps again, I'll see the setup screen, and then the loop again.
Anybody have any suggestions? I'm sure I'm missing something simple. I don't need the bootloader unlocked since I have S-OFF, correct? Thanks in advance for any and all help!
Are you able to enter into twrp custom recovery? You can install the ROM zip from there. Other option would be the sideload method.
- Put in the rom you want to install into the same directory where the adb tool is. In your case custom rom isnt it? Rename it to something simple like rom.zip
- Shift+right click in the emtpy area where the ADB tool and your is and open the command prompt.
- Navigate through custom recovery > Advanced > ADB Sideload. Your phone should now be waiting for the rom you are about to send.
-Go back to your command prompt and type the following; adb sideload rom.zip
Note that the rom you are sending needs to be complete and have all the files needed in it.
Hi Nikolay82, thanks for the reply. I'm not having an issue flashing the ROM. The issue i'm experiencing is that my phone goes into an endless bootloop after the ROM is flashed.
sstrunks84 said:
Hi Nikolay82, thanks for the reply. I'm not having an issue flashing the ROM. The issue i'm experiencing is that my phone goes into an endless bootloop after the ROM is flashed.
Click to expand...
Click to collapse
Unlock your bootloader and try again. As far as I know the M9 prevents the system from booting correctly if the bootloader is locked and TWRP is installed.
The rom should flash the boot and fix the problem. As for unlocking your bootloader please check the following;
1. Register here; https://www.htcdev.com/
2. Once registered login and select the "Unlock Bootloader" > Get Started > Select your device.
3. If you do not see HTC One M9 listed, select Last option which is "All other supported Devices"
4. Click on "begin unlock bootloader"
5. Follow the instructions and open the command prompt where your ADB is and prepare phone for fastboot mode / download mode.
6. type in; fastboot oem get_identifier_token
7. You will now get a block of text, mark and copy only the area starting from <<< Identifier token start[block of code here] Identifier token end >>>> (mark also those <<<< and >>>>) c
8. Go back to the htc.dev where you logged in and paste in the code under "My device Identifier token" field and submit the query. Navigate to your e-email where they sent you the token and download file; Unlock_code.bin
9. In that mail you will also have a link to continue unlocking the bootloader process, click it,
10. Place the Unlock_code.bin file into the folder where your ADB tools are.
11. Open up the command prompt again and type in; fastboot flash unlocktoken Unlock_code.bin
12. New dialogue should appear asking you if you want to unlock. Please note that if you proceed everything on your phone will be wiped out, so make sure you backed up things you need.
13. Go back to bootloader mode and it should say "UNLOCKED". Same with download mode.
Thanks @Flippy498! Unlocking the bootloader did the trick!
So I think I've gone and bricked my LG G3.
After the ROM I was using, cm-13.0-20160322-NIGHTLY-d855 (CM13 March 22nd) from here, kept freezing 20 seconds after startup, I went to update to cm-13.0-20160325-NIGHTLY-d855 (CM13 March 25th). I booted into recovery (TWRP 2.8.7.0) as usual and went to flash both the ROM's .zip file and an Opengapps .zip file using TWRP's queue feature. However, it appeared to get stuck at a line (unfortunately I don't remember what it said exactly. Something involving patching system, I think), so I pulled the battery. I get the feeling this was a super not good thing to do, as my G3 now sits at the "LG - Life's Good" screen indefinitely. Holding Power+Vol.Down does not boot into Recovery, and neither does holding Vol.Up and plugging into my computer activate Download mode.
I tried to be as thorough as I could with exactly the steps I took, so I'm just hoping someone can give me a few pointers on what I can do.
As I type this I had the phone connected to my computer next to me, and I've suddenly heard the Windows "Device connected" sound and the phone is now showing this in the top right corner, in tiny font:
Code:
[784670] Fastboot mode started
[784820] -- reset --
[784820] -- portchange --
Edit: When this occurred, a device named "Android" appeared under the "Other devices" tab in Windows Device Manager. It's got a yellow warning sign next to the icon, and Properties says that the drivers for the device aren't installed.
Perhaps this is relevant to getting it working again.
First you need the adb drivers for lg g3
Then you need proper partitions, depends what your starting system was, before cm..
then simply reflash them
fastboot flash aboot aboot.img
fastboot flash recovery twrp.img (because you don´t have one)
fastboot flash laf laf.img (this should fix the download mode)
Depending on what the system in original was and what the cm package installed...
bender_007 said:
First you need the adb drivers for lg g3
Then you need proper partitions, depends what your starting system was, before cm..
then simply reflash them
fastboot flash aboot aboot.img
fastboot flash recovery twrp.img (because you don´t have one)
fastboot flash laf laf.img (this should fix the download mode)
Depending on what the system in original was and what the cm package installed...
Click to expand...
Click to collapse
Many thanks for the reply.
By ADB drivers for the LG G3, do you mean the Lg United Mobile Driver? I have version 3.13.2 of them, if that's what they are.
When I input the commands
Code:
adb devices
or
Code:
fastboot devices
nothing appears, so are there different drivers I should look for?
I'm not too sure how to "fix" partitions, either, but I'm guessing it requires ADB/fastboot.
The file aboot.img and laf.img, will I need to find somewhere to download them from?
Again, I appreciate the response.
In case you have the drivers not installed (the "android" device without drivers in device manager), try with "google adb driver" ->
or pdanet
however the lg one should be fine (if not -> try one of the ones I mentioned)
bender_007 said:
In case you have the drivers not installed (the "android" device without drivers in device manager), try with "google adb driver" ->
or pdanet
however the lg one should be fine (if not -> try one of the ones I mentioned)
Click to expand...
Click to collapse
I used PdaNet to install the LG drivers, and inputting the command "fastboot devices" now shows
Code:
? fastboot
Inputting "adb devices" does not show anything, however.
I then attempted to flash a recovery, TWRP version 2.8.7.0 with the command "fastboot flash recovery "recovery.img"". However, the phone's screen showed the following:
Code:
[998960] Error: Command never completed
[998960] Error: Auto CMD12 Error
[998960] Error: Command never completed with errors
[998960] Failed Writing block @ 1
How do I fix the partitions and find the files "aboot.img" and "laf.img"?
Thanks for your help so far, I'm glad that there is progress now.
it has to be fastboot flash recovery recovery.img (where recovery.img is twrp.img, twrp.bin, recovery.img or similiar, without any quotations)
What happens when you try to enter TWRP? Are you doing it right? Hold volume down and power ---- wait for lg logo an release for less than a second and keep holding again.
aboot and laf are downloadable or extractable (from KDZ/TOT) -> use bullghosts kdz/tot extractor
bender_007 said:
it has to be fastboot flash recovery recovery.img (where recovery.img is twrp.img, twrp.bin, recovery.img or similiar, without any quotations)
What happens when you try to enter TWRP? Are you doing it right? Hold volume down and power ---- wait for lg logo an release for less than a second and keep holding again.
aboot and laf are downloadable or extractable (from KDZ/TOT) -> use bullghosts kdz/tot extractor
Click to expand...
Click to collapse
I retried the command fastboot flash recovery recovery.img but it resulted in the same output as before.
I followed the exact instructions to enter TWRP but it just stays at the LG logo screen. I've held Power+Vol.Down for about a minute after quickly releasing it+pressing it again at the LG logo, but it just doesn't do anything.
I've found myself a Lollipop KDZ file. The CyanogenMod I was running, however, ran on Android 6.0 Marshmallow. Will I need a Marshmallow KDZ file instead?
check PM - Private Messages
+check out this drivers(I packaged few of them, there is also lg adb, try the ones)
bender_007 said:
check PM - Private Messages
+check out this drivers(I packaged few of them, there is also lg adb, try the ones)
Click to expand...
Click to collapse
I appreciate the offer to use Teamviewer to help me, but I think it would be best if you typed out some instructions in a reply to this thread so that others with the same issue can refer to here.
Solution
I've found a solution to my issue, at least.
Downloading "recovery.img" from here, putting it in the same folder as fastboot, and then using the command
Code:
fastboot boot recovery.img
booted my phone properly, into cm-13.0-20160322-NIGHTLY-d855 (CM13 March 22nd).
However this resulted in all data being erased, including internal storage.
After using Flashify to re-flash TWRP (just in case), everything works as it should.
HexManiacSpeck said:
I've found a solution to my issue, at least.
Downloading "recovery.img" from here, putting it in the same folder as fastboot, and then using the command
Code:
fastboot boot recovery.img
booted my phone properly, into cm-13.0-20160322-NIGHTLY-d855 (CM13 March 22nd).
However this resulted in all data being erased, including internal storage.
After using Flashify to re-flash TWRP (just in case), everything works as it should.
Click to expand...
Click to collapse
Glad you got it working
Regarding teamviewer - it was an exploration mission so I would see how your device behaves, maybe wrong drivers, maybe..100reasons (I certainly would write it in here if there was a better idea on my side)
bender_007 said:
Glad you got it working
Regarding teamviewer - it was an exploration mission so I would see how your device behaves, maybe wrong drivers, maybe..100reasons (I certainly would write it in here if there was a better idea on my side)
Click to expand...
Click to collapse
That's alright, many thanks for your help. I've just heard bad stories regarding Teamviewer and didn't want to risk anything.
HexManiacSpeck said:
That's alright, many thanks for your help. I've just heard bad stories regarding Teamviewer and didn't want to risk anything.
Click to expand...
Click to collapse
No problem, sometimes you have to trust people
There were people who asked for help, installed teamviewer and didn´t gave any control permissions (which is fine). But they were expecting someone is having soo much free time to explain things (which I would if I had time)
cheers, flad you fixed it
Fixed my G3 I was about to send to trash!
HexManiacSpeck said:
I've found a solution to my issue, at least.
Downloading "recovery.img" fromhere, putting it in the same folder as fastboot, and then using the command
Code:
fastboot boot recovery.img
booted my phone properly, into cm-13.0-20160322-NIGHTLY-d855 (CM13 March 22nd).
However this resulted in all data being erased, including internal storage.
After using Flashify to re-flash TWRP (just in case), everything works as it should.
Click to expand...
Click to collapse
Thanks a million for pointing to this recovery file!
I was also in a situation where all my attempts to flash a recovery were failing due to:
Failed Writing block @ 1
Click to expand...
Click to collapse
The rest of my phone was unusable (no working recovery, no download mode, just the LG logo or this fastboot mode)
I tried several TWRP recovery versions & flavors, but so far, I only successfully reboot in recovery using CyanogenMod recovery file (download.cyanogenmod.org/?device=d855). Though I was not able to do much afterwards apart some adb commands that were not working either.
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p20
dd: /dev/block/mmcblk0p20: write error: I/O error
This recovery img did the trick and I'm now back with a CyanogenMod ROM and a wiped phone.
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)
Good day mate. My brick phone is F460S variant. I got this error when I tried to go back to Lollipop using Lg flash tool 2014, it got stuck on 5% and remove usb cable and start again, after that I got this error Secure Booting Error! Cause: boot certification verify.
No download mode
No recovery
anyone can help me please?:crying:
anyone?
You have triggered the downgrade QFUSE. There is nothing you can do apart from trying to unbrick it like it was dead, but that's not guaranteed to work. You should have researched more before attempting this. My prototype doesn't have a QFUSE, so i am free to downgrade via TOT to kitkat or lollipop.
西村大一 said:
You have triggered the downgrade QFUSE. There is nothing you can do apart from trying to unbrick it like it was dead, but that's not guaranteed to work. You should have researched more before attempting this. My prototype doesn't have a QFUSE, so i am free to downgrade via TOT to kitkat or lollipop.
Click to expand...
Click to collapse
What does QFUSE mean?
anmino said:
What does QFUSE mean?
Click to expand...
Click to collapse
I second you on this. I just uninstalled MultiROM and got the secure booting error. Depending on the ROM you have, find a bumped kernel and flash it. Most of the kernels on XDA are pre-bumped unless the developer states so. Boot into recovery, tutorials on the internet, then flash the kernel and voila.
if you can use twrp or you're able to flash, use mr_bump.zip: https://mega.nz/#!DNwhRBrK!Ki6zIzXca0KjPShi6L2oaCYIr0CkmH8sEymEt-0Q3ys
oh sorry, I didn't see "no recovery".
HardStyl3r said:
if you can use twrp or you're able to flash, use mr_bump.zip: https://mega.nz/#!DNwhRBrK!Ki6zIzXca0KjPShi6L2oaCYIr0CkmH8sEymEt-0Q3ys
oh sorry, I didn't see "no recovery".
Click to expand...
Click to collapse
Yes, no DOWNLOAD mode and RECOVERY mode.. Anyone have an idea how to fix this?
anyone?
Hello, i got the same probleme and i've trying a lot of things but not resolved..
My phone is a LG G3 Beat F470s..
Please help us..
Dowblnload adb and fastboot drivers
Download laf.img for your device
Download LG Drivers
Get you G3 to fastboot mode. Hold volume up and connect it to PC
Open fastboot and adb folder in PC, ctrl+shift+right click and open cmd. Type fastboot devices...if ur device is listen then proceed, if not u did not do something cotrectly...if yes just flash laf img to your G3 and voila
I remember me that I was in the same situation:
No TWRP, no download mode, so i have use in pat this thread:
https://forum.xda-developers.com/showthread.php?t=1752270
And an other that i haven't found again (xda thread), in some lines:
=> download the last img file from: https://eu.dl.twrp.me/d855/
=> no download mode available so no possibility to flash manually twrp file from an LG Flash Tool
==> so setup an adb connexion to the phone, cp command to copy the img file on the sdcard or where you want
=> command: "flash recovery twrp-2.8.x.x-xxx.img" (https://www.xda-developers.com/how-to-install-twrp/
=> if it's as worked, you could reboot manually in twrp, make again the partitions if needed and flash any ROM.
Hi Guy!
It's been a while since I've posted on here, last time was the HTC HD2 days, Remember that?!
Anyways I've started unlocking my LG G4 H815 after 2 years, 2nd motherboard and new screen. I've used the official route through LG and got to the TWRP installation and hit an issue.
I'm running the command prompt in adb installation path, using the latest version of TWRP which was renamed like the guide said. Using Windows 10 which gives all the drivers needed to allow the phone to be recognised when I type in "reboot bootloader".
Issue is when trying to install TWRP through command prompt "fastboot flash recovery twrp-3.1.0.0-h815.img"
I get "invalid destination or file cannot be found" I've tried different files, checked I'm booting from the right place, IMG file is in ADB/fastboot folder also. Debugging and what not all enabled.
So I'm out of idea? Help
Dingo
You need a microsd card installed on the phone and a copy of twrp image on the microsd card - you can also add a copy of supersu zipfile if you want to install root
fastboot boot twrp-2.8.7.1-h811.img (phone itself boots TWRP)
from phone itself:
In TWRP hit Install > Images... (bottom right corner) > select TWRP.img on ext sdcard > select "recovery" > swipe for permanent install of twrp
for root: Hit the Home button > Install > select SuperSU zip on external sdcard > swipe
Reboot into Android. (if TWRP asks if you want to install SU, HIT NO!!!)
if you do not have an external sdcard to save SuperSU and the TWRP.img onto.. you will need to skip saving the files to sdcard until AFTER you fastboot OEM unlock and boot into TWRP. After fastboot booting TWRP you can use adb push to put SuperSU and TWRP.img onto the internal sdcard to install with TWRP. Or you can use the MTP mount option in TWRP and drag n' drop the files from the computer to the phone. You cannot store the files on the internal sdcard before the OEM unlock because OEM unlock wipes all your data.
These are for h811 g4 but should work fine for you, instructions can be found here:
https://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
Dingo88 said:
Hi Guy!
It's been a while since I've posted on here, last time was the HTC HD2 days, Remember that?!
Anyways I've started unlocking my LG G4 H815 after 2 years, 2nd motherboard and new screen. I've used the official route through LG and got to the TWRP installation and hit an issue.
I'm running the command prompt in adb installation path, using the latest version of TWRP which was renamed like the guide said. Using Windows 10 which gives all the drivers needed to allow the phone to be recognised when I type in "reboot bootloader".
Issue is when trying to install TWRP through command prompt "fastboot flash recovery twrp-3.1.0.0-h815.img"
I get "invalid destination or file cannot be found" I've tried different files, checked I'm booting from the right place, IMG file is in ADB/fastboot folder also. Debugging and what not all enabled.
So I'm out of idea? Help
Dingo
Click to expand...
Click to collapse
You are using an abandoned version please use the latest beta in the official TWRP thread
.
Sent from my LG-H815 using XDA Labs
Dingo88 said:
Hi Guy!
It's been a while since I've posted on here, last time was the HTC HD2 days, Remember that?!
Anyways I've started unlocking my LG G4 H815 after 2 years, 2nd motherboard and new screen. I've used the official route through LG and got to the TWRP installation and hit an issue.
I'm running the command prompt in adb installation path, using the latest version of TWRP which was renamed like the guide said. Using Windows 10 which gives all the drivers needed to allow the phone to be recognised when I type in "reboot bootloader".
Issue is when trying to install TWRP through command prompt "fastboot flash recovery twrp-3.1.0.0-h815.img"
I get "invalid destination or file cannot be found" I've tried different files, checked I'm booting from the right place, IMG file is in ADB/fastboot folder also. Debugging and what not all enabled.
So I'm out of idea? Help
Dingo
Click to expand...
Click to collapse
i beleive win 10 gives problems and must use USB 2.0
Hi Cheers for replys,
Had an issue on Win7 where I couldn't make "android" drivers work, both LG usb and Google driver update failed miserably.
On the TWRP I've used the latest version and a previous version. Placed it within the ADB folder and on the SD card both came out saying , "invalid file destination or something like that" am I missing a command prompt for the phone to access the SD card?
Thanks Dingo88
Dingo88 said:
Hi Cheers for replys,
Had an issue on Win7 where I couldn't make "android" drivers work, both LG usb and Google driver update failed miserably.
On the TWRP I've used the latest version and a previous version. Placed it within the ADB folder and on the SD card both came out saying , "invalid file destination or something like that" am I missing a command prompt for the phone to access the SD card?
Thanks Dingo88
Click to expand...
Click to collapse
It seems you really miss something. Read carefully. Fastboot flash will not work!
You just need to reboot into bootloader then using
fastboot boot twrp.img
Then you should see TWRP. Then you would flash TWRP from within TWRP. That's all described in the official install guide.
Btw: Exactly because of your problems with drivers etc I created FWUL ( https://tinyurl.com/FWULatXDA )..
The latest TWRP beta is 3.1.1 btw.
.
Sent from my LG-H815 using XDA Labs
Hi Steadfaster, cheers for the reply.
Im definitely doing something wrong, im still at a loss.
I've unlocked the boot loader, followed by "adb reboot bootloader" which takes me into the bootloader.
Then with the lgg4-twrp.img placed in both the SD and ADB location I type "fastboot boot lgg4-twrp.img. I get no luck!
Pic attached! Apologies if your screaming at your screen!
Dingo88 said:
Hi Steadfaster, cheers for the reply.
Im definitely doing something wrong, im still at a loss.
I've unlocked the boot loader, followed by "adb reboot bootloader" which takes me into the bootloader.
Then with the lgg4-twrp.img placed in both the SD and ADB location I type "fastboot boot lgg4-twrp.img. I get no luck!
Pic attached! Apologies if your screaming at your screen!
Click to expand...
Click to collapse
Rename the downloaded twrp to twrp.img no dashes. and it has to be in the same folder where your adb exe is.
.
Sent from my LG-H815 using XDA Labs
Dingo88 said:
Hi Steadfaster, cheers for the reply.
Im definitely doing something wrong, im still at a loss.
I've unlocked the boot loader, followed by "adb reboot bootloader" which takes me into the bootloader.
Then with the lgg4-twrp.img placed in both the SD and ADB location I type "fastboot boot lgg4-twrp.img. I get no luck!
Pic attached! Apologies if your screaming at your screen!
Click to expand...
Click to collapse
could be corrupted download verify md5 with latest 3.1.1 as named and downloaded using 61ed0c81afb750535bdb71dfb0298149 md5 key
then simplify things, rename file to twrp.img to avoid typing errors