I have a UK-bought SGT10.1, which I rooted shortly after purchase and installed CWM Recovery using Odin. I've been running In Paris for a while, and was about to update to v5. Last time I downloaded pershoot's kernel from droidbasement, I saw an updated version of CWM Recovery here: http://droidbasement.com/db-blog/?p=2370.
Being a security-type, running the latest versions is always the best option to me - and seeing I know my way around the console I figured I'll install adb/fastboot and use that this time instead of Odin. So I downloaded the SDK, installed the Tab 10.1 drivers (I've reinstalled Windows since I rooted), and grabbed the fastboot .exe from the previous revision and placed it inside android-sdk\platform-tools next to adb.
Now I'm trying to follow the instructions to install the extracted .img - but having some issues getting into fastboot mode in order to execute the commands. Running adb devices results in expected output, as does adb reboot recovery. However running adb reboot bootloader causes the device to reboot all the way back through to the lockscreen. I see some advice stating that to manually enter fastboot you reboot the device holding power+vol down, then pressing down to switch to the second option that isn't download mode. However that to me is the option to manually enter CWM Recovery, so now I'm confused. Running fastbooot reboot-bootloader cause
I don't want to brick my device, so I figured I'd ask for some advice here for getting into fastboot mode, and ask whether I can just flash the .zip inside CWM Recovery or if that is a very risky move?
Thanks in advance
Related
Problem: Was trying to install AOKP 4.0 onto my fully updated TF201.
Wiped data/cache/davlik
installed ROM
installed Google Apps
Device stuck on splash screen.
Figured out the problem was an older version on CWM. I believe it was 5.5.0.4.
Tried to go install latest version of CWM: 5.8.3.4 by using the Fastboot method.
Accidentally selected Wipe Data Option instead of USB.
Lost CWM, all data on internal memory and my entire OS.
Device cannot boot (stays on splash screen). I also try to get back into CWM and it fails. I get bounced back to the Fastboot screen.
What can I do to get this thing back up and running? I will even take stock at this moment just to get the ball rolling again.
Thanks!
kevinb77 said:
Problem: Was trying to install AOKP 4.0 onto my fully updated TF201.
Wiped data/cache/davlik
installed ROM
installed Google Apps
Device stuck on splash screen.
Figured out the problem was an older version on CWM. I believe it was 5.5.0.4.
Tried to go install latest version of CWM: 5.8.3.4 by using the Fastboot method.
Accidentally selected Wipe Data Option instead of USB.
Lost CWM, all data on internal memory and my entire OS.
Device cannot boot (stays on splash screen). I also try to get back into CWM and it fails. I get bounced back to the Fastboot screen.
What can I do to get this thing back up and running? I will even take stock at this moment just to get the ball rolling again.
Thanks!
Click to expand...
Click to collapse
Go here, http://forum.xda-developers.com/showthread.php?t=1615990 read the OP, then go here to download http://teamw.in/project/twrp2/93
Follow the instructions under
Download - Recovery Image / Fastboot Method:
You will back up and running in no time, unfortunately you will need to reinstall the rom....
PS you will need to adb push the rom after you reboot to recovery....
Gage_Hero said:
Go here, http://forum.xda-developers.com/showthread.php?t=1615990 read the OP, then go here to download http://teamw.in/project/twrp2/93
Follow the instructions under
Download - Recovery Image / Fastboot Method:
You will back up and running in no time, unfortunately you will need to reinstall the rom....
PS you will need to adb push the rom after you reboot to recovery....
Click to expand...
Click to collapse
Thanks for the quick response!
OK, I was able to get the stock TF201 drivers onto my Windows 7 PC (since an alternate method had me change them) I am following every step explained in the directions from TeamW.in and am getting this error: "The program can't start because AdbWinAPI.dll is missing from your computer. Try reinstalling the program to fix this problem"
(UPDATE) I was able to find a ADBWinAPI.dll file and I dropped it into the same folder as the twrp.blob and fastboot.exe files. I am not able to access the cmd line, but it does not start the flash, it only lists a bunch of optional cmds to pick from. None of which look useful.
kevinb77 said:
Thanks for the quick response!
OK, I was able to get the stock TF201 drivers onto my Windows 7 PC (since an alternate method had me change them) I am following every step explained in the directions from TeamW.in and am getting this error: "The program can't start because AdbWinAPI.dll is missing from your computer. Try reinstalling the program to fix this problem"
(UPDATE) I was able to find a ADBWinAPI.dll file and I dropped it into the same folder as the twrp.blob and fastboot.exe files. I am not able to access the cmd line, but it does not start the flash, it only lists a bunch of optional cmds to pick from. None of which look useful.
Click to expand...
Click to collapse
Did you ever have any luck with this? I had a JB ROM soft brick my 201 about a year ago. I lost TWRP recovery, OS, pretty much everything. It stays on the splash screen and allows me to get to the fastboot option. I can't get my computer(windows 8) to recognize it at all. Just states it can not recognize USB device. I installed the universal naked driver package along with trying the stock ASUS driver package with no luck.
I put the tablet down and purchased a 701 but now would like to fix the 201 and sell it. If you have any advice I would be very thankful
Hey everyone,
This is my first time posting to the forums. I have been trying to get everything done without having to ask questions since there are so many all over the place and I can see how it can get tiring trying to help everyone when their may be an answer out there already if you look. However, I have ran into an issue that I can't seem to find much information on. I have the HTC Rezound that is S-On (apparently you need a Linux machine to get S-Off which I don't have. Using Windows 7.) and have been using fastboot to get things done. I have unlocked the bootloader and have installed the 'Amon Ra' recovery and setup Superuser and SU. As far as I know, I have to use ROM's that are S-On friendly (right?) and I chose to try out 'EclipticRez' and later 'Talon'.
As I tried to flash the ROM's through fastboot it fails with the following errors every time and I cannot continue:
archive does not contain android-info.txt
archive does not contain android-product.txt
From what I found is that it may be a bad download of the ROM. Maybe.... But it happened consecutively with two different ROM downloads.
I also read that maybe the recovery wasn't setup, which as far as I know it is. Should I use a different recovery? Everyone usually references to using CWM, which I wouldn't mind using but I couldn't figure out how to get SU access.
Can I just create the files myself? They are only txt files after all.
If anyone can help me with this I will be so grateful! I'm pretty new to this and it has definitely been a fun learning experience for me
Much thanks in advance!
Strikerz87 said:
Hey everyone,
This is my first time posting to the forums. I have been trying to get everything done without having to ask questions since there are so many all over the place and I can see how it can get tiring trying to help everyone when their may be an answer out there already if you look. However, I have ran into an issue that I can't seem to find much information on. I have the HTC Rezound that is S-On (apparently you need a Linux machine to get S-Off which I don't have. Using Windows 7.) and have been using fastboot to get things done. I have unlocked the bootloader and have installed the 'Amon Ra' recovery and setup Superuser and SU. As far as I know, I have to use ROM's that are S-On friendly (right?) and I chose to try out 'EclipticRez' and later 'Talon'.
As I tried to flash the ROM's through fastboot it fails with the following errors every time and I cannot continue:
archive does not contain android-info.txt
archive does not contain android-product.txt
From what I found is that it may be a bad download of the ROM. Maybe.... But it happened consecutively with two different ROM downloads.
I also read that maybe the recovery wasn't setup, which as far as I know it is. Should I use a different recovery? Everyone usually references to using CWM, which I wouldn't mind using but I couldn't figure out how to get SU access.
Can I just create the files myself? They are only txt files after all.
If anyone can help me with this I will be so grateful! I'm pretty new to this and it has definitely been a fun learning experience for me
Much thanks in advance!
Click to expand...
Click to collapse
1) Switch to TWRP or CWM for your recovery.
2) You install the rom zip via recovery.
3) You then need to fastboot flash the kernel from the rom zip you downloaded. You don't install the whole rom via fastboot.
To borrow from the CM11 thread.
- Place the boot.img into the platform-tools folder of the Android SDK's install directory.
- Boot to the bootloader.
- Ensure your device is connected to your computer and that your device is now in fastboot mode. This is a white screen and it says fastboot on it.
- Open a Terminal (OSX or Linux) or CMD window (Windows) and cd to the platform-tools directory of the Android SDK's install directory.
- Issue this command to flash the boot.img we placed in the platform-tools folder earlier:
Code:
fastboot flash boot boot.img
- Watch the output of the terminal, it should say something like "sent successfully".
- Finally send this command:
Code:
fastboot reboot
Since you're s-on, you'll need to do this whenever you install a new rom. Using these steps, you can install any rom you want.
Strikerz87 said:
Hey everyone,
This is my first time posting to the forums. I have been trying to get everything done without having to ask questions since there are so many all over the place and I can see how it can get tiring trying to help everyone when their may be an answer out there already if you look. However, I have ran into an issue that I can't seem to find much information on. I have the HTC Rezound that is S-On (apparently you need a Linux machine to get S-Off which I don't have. Using Windows 7.) and have been using fastboot to get things done. I have unlocked the bootloader and have installed the 'Amon Ra' recovery and setup Superuser and SU. As far as I know, I have to use ROM's that are S-On friendly (right?) and I chose to try out 'EclipticRez' and later 'Talon'.
As I tried to flash the ROM's through fastboot it fails with the following errors every time and I cannot continue:
archive does not contain android-info.txt
archive does not contain android-product.txt
From what I found is that it may be a bad download of the ROM. Maybe.... But it happened consecutively with two different ROM downloads.
I also read that maybe the recovery wasn't setup, which as far as I know it is. Should I use a different recovery? Everyone usually references to using CWM, which I wouldn't mind using but I couldn't figure out how to get SU access.
Can I just create the files myself? They are only txt files after all.
If anyone can help me with this I will be so grateful! I'm pretty new to this and it has definitely been a fun learning experience for me
Much thanks in advance!
Click to expand...
Click to collapse
also to note....you dont have to install linux to get s-off....if you follow my guide you can do it straight from a live disk rather than installing it....so it wont erase or mess up your windows partition at all
Solved!
Thank you, Mjones, I finally got it! I knew it was much easier than I was making it out to be. I was missing the kernel! Yeah, a crucial part in the process, I know
I first ran CWM and flashed the ROM over and ran the .zip through recovery (which I couldn't understand at first as I could never find it in the directory) but the installer would only go 50% and would fail... makes sense why now lol
I later flashed TWRP and backed up again after recovering from the fail. I flashed over the kernel and voila! So simple... Had to slap myself.
Thanks again! Case solved.
REV3NT3CH, that is sweet!! I have been hoping there is a way to gain s-off with Windows. I have 7 at work and 8.1 (which I can't get anything to work on) at home. I actually have to focus on work today haha so I'll look into the method and try it out tomorrow if I can. Thanks for all of the help.
mjones73 said:
1) Switch to TWRP or CWM for your recovery.
2) You install the rom zip via recovery.
3) You then need to fastboot flash the kernel from the rom zip you downloaded. You don't install the whole rom via fastboot.
To borrow from the CM11 thread.
- Place the boot.img into the platform-tools folder of the Android SDK's install directory.
- Boot to the bootloader.
- Ensure your device is connected to your computer and that your device is now in fastboot mode. This is a white screen and it says fastboot on it.
- Open a Terminal (OSX or Linux) or CMD window (Windows) and cd to the platform-tools directory of the Android SDK's install directory.
- Issue this command to flash the boot.img we placed in the platform-tools folder earlier:
Code:
fastboot flash boot boot.img
- Watch the output of the terminal, it should say something like "sent successfully".
- Finally send this command:
Code:
fastboot reboot
Since you're s-on, you'll need to do this whenever you install a new rom. Using these steps, you can install any rom you want.
Click to expand...
Click to collapse
Thank You So much, Mine case also Resolved. I was too frustated sice last 3 days cause my phone was in dead mode. At the end, fastboot flash boot boot.img Worked. ThankYOu
mjones73 said:
1) Switch to TWRP or CWM for your recovery.
2) You install the rom zip via recovery.
3) You then need to fastboot flash the kernel from the rom zip you downloaded. You don't install the whole rom via fastboot.
To borrow from the CM11 thread.
- Place the boot.img into the platform-tools folder of the Android SDK's install directory.
- Boot to the bootloader.
- Ensure your device is connected to your computer and that your device is now in fastboot mode. This is a white screen and it says fastboot on it.
- Open a Terminal (OSX or Linux) or CMD window (Windows) and cd to the platform-tools directory of the Android SDK's install directory.
- Issue this command to flash the boot.img we placed in the platform-tools folder earlier:
Code:
fastboot flash boot boot.img
- Watch the output of the terminal, it should say something like "sent successfully".
- Finally send this command:
Code:
fastboot reboot
Since you're s-on, you'll need to do this whenever you install a new rom. Using these steps, you can install any rom you want.
Click to expand...
Click to collapse
I need to be able to do it via fastboot, as my Motorola Electrify M is stuck in a bootloop and there's no way I could find to boot into recovery. I'm using ./fastboot update name_of_update.zip and it is an official OTA .zip but I still get this error. Any suggestions?
ecols33 said:
I need to be able to do it via fastboot, as my Motorola Electrify M is stuck in a bootloop and there's no way I could find to boot into recovery. I'm using ./fastboot update name_of_update.zip and it is an official OTA .zip but I still get this error. Any suggestions?
Click to expand...
Click to collapse
Sorry, don't know anything about that phone.
ecols33 said:
I need to be able to do it via fastboot, as my Motorola Electrify M is stuck in a bootloop and there's no way I could find to boot into recovery. I'm using ./fastboot update name_of_update.zip and it is an official OTA .zip but I still get this error. Any suggestions?
Click to expand...
Click to collapse
Did you try this first? (Right from Moto's site)
Perform a factory reset using external keys
1. Power off the phone, press and hold volume down button, press power button
2. Screen will come up with "Fastboot", press Vol down key to cycle through choices until you get "Android Recovery", then press Vol up key
3. Wait for the "triangle ! / Android" screen then go on to step 4
4. Press both Vol up and Vol down key simultaneously. A menu will come up
5. Tap on Vol down key until "wipe data/factory reset" is highlighted, and tap Power key. Another Confirmation screen will come. Tap on Vol down key until coming to Yes and tap Power key
6. After userdata is cleared, the "reboot system now" option will be highlighted by Default. Tap Power key
7. Phone will reboot to initial setup screen.
PLEASE HELP! I have a Huawei P8 and I tried to update to android 6.0 (GRA-L09xxxxxxxxxxxB317 or something) Went to install it and now im stuck in bootloop (a very annoying one, I can rarely get into eRecovery and eRecovery is not able to fix my problem: "Getting package info failed") so I went into fastboot&rescue mode and I did the flash thing via my PC (that Fastboot flash boot boot.img etc.) but I get this error saying: "FAILED (remote: Command not allowed)" for any image im trying to flash. My fastboot/bootloader or whatever it's called is locked my android is unrooted and stock android. I don't know how to unlock it I can't find anything anywhere.. HELP ME
not working
hariom.gupta11 said:
Thank You So much, Mine case also Resolved. I was too frustated sice last 3 days cause my phone was in dead mode. At the end, fastboot flash boot boot.img Worked. ThankYOu
Click to expand...
Click to collapse
not working on my 4c. write successful but when reboot is completed it goes to previous state.
"the user data partition can no longer be used"
zb602kl_x00tdb
L0RDZ3RO said:
PLEASE HELP! I have a Huawei P8 and I tried to update to android 6.0 (GRA-L09xxxxxxxxxxxB317 or something) Went to install it and now im stuck in bootloop (a very annoying one, I can rarely get into eRecovery and eRecovery is not able to fix my problem: "Getting package info failed") so I went into fastboot&rescue mode and I did the flash thing via my PC (that Fastboot flash boot boot.img etc.) but I get this error saying: "FAILED (remote: Command not allowed)" for any image im trying to flash. My fastboot/bootloader or whatever it's called is locked my android is unrooted and stock android. I don't know how to unlock it I can't find anything anywhere.. HELP ME
Click to expand...
Click to collapse
I have same problem on asus zenfone max pro m1 I bought it online said used and now working
can't boot into recovery.
can't boot into system.
Only EDL Mode and Fastboot Mode, but fastboot is Locked whic I cant unlock because I cannot boot into system to toggle USB Debugging and allow OEM unlocking
Qualcomm is harder to flash than MTK that can use SP FlashTool.
on this I use QFIL but keeps "sahara error". I tried searching and try moving firmware file to bin but no Luck. I'm currently trying different version of QFIL Tool.
If it FAILS my only HOPE is to use MUT-QCfire which will Require a "SmartCardReader" Which is a bit pricey and I don't even know if it will work on my device.
So I need to appeal to the android gurus of the world. I have an issue that I am having a difficult time sussing out and I am hoping someone else can help me figure it out.
My device is an HTC One M7, rooted, running Insert Coin 3.0.2 (Android 4.4.2), S-On., Hboot 1.44, TWRP Recovery
My problem is I can not access my Recovery and Fastboot isn't seeing my device, so I can not flash a new one. I can get to my phone in adb, just fine, but using flash_image to flash a recovery threw up a -1 error, so flashing recovery through adb appears to be out, as well. If I go to my Bootloader, selecting Recovery simply dumps me back to Fastboot.
I haven't booted into recovery since I installed this Rom, months ago, so I don't know exactly when my Recovery broke. I do know that today, I tried updating TWRP through Flashify and I suspect that may be part of the issue, since Flashify insisted on pulling down the TWRP for the M8 instead of the M7. I didn't catch that little nugget till after I flashed it.
I am pretty well open to anything that might work, but I am not sure what my options are when I can't even get into recovery. A pre-emptive thank you to anyone attempting to help. It should be said that apart from this, the phone works fine. I simply can't get into recovery to update my ROM, anymore.
Ok, I am an idgit. Could a mod move this to the Q&A forum? Apologies.
EqualOpportunityDork said:
So I need to appeal to the android gurus of the world. I have an issue that I am having a difficult time sussing out and I am hoping someone else can help me figure it out.
My device is an HTC One M7, rooted, running Insert Coin 3.0.2 (Android 4.4.2), S-On., Hboot 1.44, TWRP Recovery
My problem is I can not access my Recovery and Fastboot isn't seeing my device, so I can not flash a new one. I can get to my phone in adb, just fine, but using flash_image to flash a recovery threw up a -1 error, so flashing recovery through adb appears to be out, as well. If I go to my Bootloader, selecting Recovery simply dumps me back to Fastboot.
I haven't booted into recovery since I installed this Rom, months ago, so I don't know exactly when my Recovery broke. I do know that today, I tried updating TWRP through Flashify and I suspect that may be part of the issue, since Flashify insisted on pulling down the TWRP for the M8 instead of the M7. I didn't catch that little nugget till after I flashed it.
I am pretty well open to anything that might work, but I am not sure what my options are when I can't even get into recovery. A pre-emptive thank you to anyone attempting to help. It should be said that apart from this, the phone works fine. I simply can't get into recovery to update my ROM, anymore.
Click to expand...
Click to collapse
ADB works in an OS or in custom recovery and fastboot works in the bootloader. ADB doesn't work if the phone is in bootloader. I think you will have to run a RUU then go into stock recovery and do a factory reset. Let the phone boot normally then you can start the custom routine. You might also check to see if your ADB & fastboot are up to date. To run the RUU you will have to relock your bootloader since you are S-ON.
Thanks. Yea, I've managed to figure out the difference between adb and fastboot through all this. so plus for learning! However, the only method I have found for relocking my bootloader is through fastboot, which I can't seem to be able to use.
I will see if there's a newer version of fastboot out there, though. hadn't thought of that.
EqualOpportunityDork said:
Thanks. Yea, I've managed to figure out the difference between adb and fastboot through all this. so plus for learning! However, the only method I have found for relocking my bootloader is through fastboot, which I can't seem to be able to use.
I will see if there's a newer version of fastboot out there, though. hadn't thought of that.
Click to expand...
Click to collapse
Another quick thought, you wouldn't happen to be using Win 8 are you? If so, Win 8 doesn't see hboot 1.44 you are going to have to use a Win 7, Mac or Linux machine. Sorry, I didn't catch it earlier. Here is a how to for Linux and you don't have to install it permanently on your computer:
HOW TO USE LINUX FOR FASTBOOT & ADB VIA USB
This guide originally posted by @Danny201281
http://forum.xda-developers.com/showpost.php?p=54272479&postcount=219Linux is your friend; if your drivers are not working the chances of getting them working again without the phone booting are slim. But Linux doesn't need drivers to talk to your device.
Go here: http://www.pendrivelinux.com/ and download Universal USB Installer – Easy as 1 2 3
Then go here: http://releases.ubuntu.com/12.04/ and download Ubuntu from the first link at the top that says PC (Intel x86) desktop CD
Then use these files to create a bootable Linux USB drive with at least a 2 GB persistent file for storing files. You'll also probably need to change your boot settings in the computers bios to boot from USB.
MOVING YOUR FILES TO UBUNTU
Once booted you should be at a screen with options to "Try Ubuntu” or "Install Ubuntu". We don’t need to Install anything so just choose "Try Ubuntu" and the computer will boot to the Ubuntu Desktop (If you get a popup saying "system has encountered an error" or something similar just cancel and ignore it, it should have no effect on what we need to do as it is due to missing Linux OS updates we don’t need). On the left of the screen you'll see the Dock. Open the orange folder icon near the top this is the Home folder. It’s where we need to put any files we need to work with such as a rom.zip you want to push to the device or recovery.img files for flashing.
To get your files here is a simple drag and drop process. In the top left of the Home folder you'll see the drive structure of you pc under devices. Choose your PCs hard drive and Right-Click then" Open in a new window". Locate your .zip or .img files and drag them into the home folder. Now wait for the copy process to complete and rename them for easier typing later, e.g., rom.zip, firmware.zip or recovery.img etc.
USING ADB AND FASTBOOT
First you need to install adb fastboot; this is easy just 3 commands in the terminal. Thanks to Webupd8 team.
Code:
sudo add-apt-repository ppa:nilarimogard/webupd8
Code:
sudo apt-get update
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
Make sure your connected to the internet and press Ctrl+Alt+T to open the terminal then type or copy and paste the above commands one at a time waiting for each to complete their output. It may seem to have stopped at times but be patient when the prompt returns to normal enter the next command and when there all done you’re ready to use adb and fastboot.
Once you've moved all the files you need to the home folder that’s it you’re ready to go. Close everything down on the desktop (optional) and press Ctrl+Alt+T this will open the terminal now connect your phone with the USB cable. All fastboot commands need to have the "sudo" prefix added at the start, e.g.
fastboot flash recovery recovery.img becomes sudo fastboot flash recovery recovery.img
fastboot devices becomes sudo fastboot devices
However, adb should work basically the same as on windows. If you do have problems with normal adb commands adding “sudo” can help here as well.
Click to expand...
Click to collapse
Dude, you are my hero. I couldn't get fastboot to work, because I had missed the part where I needed to preface it with sudo. I had adb and fastboot running a couple of days ago on my Mint install, but I didn't realize I was missing 4 freaking letters to get it right. Just flashed latest twrp and booted into recovery, no problem.
Thanks again, for the help, even if I should have found that on my own, sooner. I thought I had really hosed something on my phone. Now I can move on to hopefully not screwing something else up.
You could have used flashify to flash a recovery.IMG. free app from app store
I mentioned trying Flashify in the OP.
Just installed the new nightly which I found out after the fact was to version 12.1 (Android 5.1) from version 12.0. This of course means installing a new version of gapps for this version. I found and downloaded the new gapps, then went to reboot into recovery (it had been working prior to this). This time when I hit the volume down button on reboot, it just continued to boot normally. I even tried booting with the up button: same result. I can't access the play store because the gapps has to be updated first. Is there another way to get into recovery mode to install gapps? or alternatively another way to install it without recovery mode?
Found part of the answer
OK, found out how to reboot recovery with ADB. For anybody else who wants to know:
Install ADB on your computer if you haven't already
Run command shell (cmd)
Go to the platform-tools directory under where you installed ADB
If you're using ADB over network, type: adb connect {ip address of tablet}
type : adb reboot recovery
And that should get you into recovery mode
Now I just gotta get the correct version of gapps, the first one I got isn't working.
Hi all,
I appear to have done something wrong when flashing my device with boombox and flashing twrp. I seem not to be able to access recovery so I can update my boombox rom. I have tried button combinations, I have tried fastboot boot twrp.img in bootloader which just reboots my system, I have tried booting directly from home screen using adb which registers an error and I have tried re-flashing but unfortunately I cannot access recovery.
Any way I can get into recovery without erasing my data?
Jonnibravo said:
Hi all,
I appear to have done something wrong when flashing my device with boombox and flashing twrp. I seem not to be able to access recovery so I can update my boombox rom. I have tried button combinations, I have tried fastboot boot twrp.img in bootloader which just reboots my system, I have tried booting directly from home screen using adb which registers an error and I have tried re-flashing but unfortunately I cannot access recovery.
Any way I can get into recovery without erasing my data?
Click to expand...
Click to collapse
If you're rooted, give the reboot recovery app you installed after bootloader unlock root privileges.
If not then use the exact same PC ADB commands to boot to TWRP like during bootloader unlock.
I'm confused why you mention flashing TWRP after Boombox. Surely you didn't do that. You already had TWRP.
I am rooted, Recovery reboot just reboots the phone, I have tried to get into twrp by reinstalling but again does the same things just reboots the system after the corruption warning screen. I've also tried to install from the bootloader with the fastboot boot twrp.img command but it simply says waiting for device.
Sorry turns out I was flashing the wrong file from another tutorial, I was flashing 3.1.1 instead of 3.2.1
Jonnibravo said:
Sorry turns out I was flashing the wrong file from another tutorial, I was flashing 3.1.1 instead of 3.2.1
Click to expand...
Click to collapse
Then you didn't follow my bootloader unlock and root guide. I never mention that other TWRP, much less link to it.
You're going to have to load into Download mode and use fastboot commands, but you say you couldn't get past flashing TWRP.
Uninstall the LG Mobile Driver if you have them, then reinstall.
1st, reboot into OS, then open up Device Manager and change view to Show hidden devices. You should see a new category named 'ADB Interface' and underneath that 'Fastboot Interface (Google USB ID)'.
If not, you will also see 'ADB Device' for Other Devices category:
right click that to update driver software ---> Browse my computer for driver software ---> Let me pick from a list... ---> Show all Devices ---> Have Disk ---> Browse ---> C:\Program Files (x86)\LG Electronics\LG Mobile Driver ---> 'lgandbus' ---> 'LGE ADB Mobile Interface'
Download adb/fastboot software, download Joan TWRP 3.2.1 img file and place it in adb/fastboot folder, then send your phone into Download mode:
Open up cmd and type the following after changing directory to Adb/fastboot folder: fastboot devices (see if your device is there), fastboot flash recovery TWRP.img or (whatever file is named).img, then fastboot boot TWRP.img or (whatever file is named).img