[Q] Wugfresh failed, Softbricked? - Nexus 7 (2013) Q&A

Hi guys, I was wondering if someone with experience would be able to help me (a noob) out.
Last night I wanted to upgrade from 4.4.2 with Franco Kernel on my nexus 7 2013 to 5.0.2 Lollipop. I suspected that the franco kernel would prevent me from upgradeing OTA and I determined I must flash it myself. I downloaded Wugfresh Nexus toolkit and followed the videos but my computer said something like "wugfresh.exe stopped working. windows will try to find a solution." The window closed and now my nexus 7 wont load past the google screen. I am able to reach fastboot mode but if I try to access recovery, there is simply an android figure with a red exclamation point over it. Wugfresh doesn't seem to be working for me as I keep getting "failed: command write failed no such device or address"
I'm really stuck. It doesnt look like I can use Wugfresh (soft-bricked/bootloop option) as I keep getting failed reports. I have attached a screenshot to help describe what I am talking about.
Lemme know if you have any suggestions on how to proceed or need any additional information from me. I'm really bummed out and I have all day today to try and fix it.
Best,
ljia4

Will this menu help?
I see from the first sceenshot I attached that cache, recovery and system failed. Should I just use the menu in the second screenshot to flash those?
Im scared I will break it irreparably if i do so.

Flash the system image from fastboot and stop using toolkits.
Edit: When I say flash from fastboot, I mean actually use fastboot from the Android SDK and NOT the "fastboot flash" option in the toolkit. If you don't know how to use fastboot, and I suspect you don't, just read one of the many adb/fastboot guides available on XDA. You shouldn't be rooting/ROMing/modding your Android devices if you don't know how to use fastboot.
http://forum.xda-developers.com/showthread.php?t=2277112

@ljia4- Well? Any luck?

_MetalHead_ said:
@ljia4- Well? Any luck?
Click to expand...
Click to collapse
Thanks for following up. I was able to experiment with the advanced menu on wugfresh and eventually flash recovery and system. Then I used ota updates to get lollipop.
Thanks for checking back, I appreciate your time and efforts. I'll !take sure to steer clear from modding/flashing from here on out!

ljia4 said:
Thanks for following up. I was able to experiment with the advanced menu on wugfresh and eventually flash recovery and system. Then I used ota updates to get lollipop.
Thanks for checking back, I appreciate your time and efforts. I'll !take sure to steer clear from modding/flashing from here on out!
Click to expand...
Click to collapse
Don't steer clear of it, just learn how to do it the right way! I think you'll find that understanding how to use fastboot is much easier than it seems, and knowing how to do this stuff is invaluable. Aside from the fact that you'll be able to do pretty much anything, you'll also know how to get yourself out of a bind should you find yourself in one. Seriously, give that guide I posted a read, and if you have any questions don't hesitate to ask.
Anyways, I'm glad you got your situation figured out (even if you still used a toolkit ).

^++

_MetalHead_ said:
Don't steer clear of it, just learn how to do it the right way! I think you'll find that understanding how to use fastboot is much easier than it seems, and knowing how to do this stuff is invaluable. Aside from the fact that you'll be able to do pretty much anything, you'll also know how to get yourself out of a bind should you find yourself in one. Seriously, give that guide I posted a read, and if you have any questions don't hesitate to ask.
Anyways, I'm glad you got your situation figured out (even if you still used a toolkit ).
Click to expand...
Click to collapse
When I got my Nexus 5 and used Wug's toolkit to root and install TWRP, I'd already read about fastboot commands. Watching the Live Log, and seeing it was doing exactly what the posts said you do with fastboot (just automating it), was a nice way to see that it really is as easy as "fastboot flash system system.img", etc.

Related

Dealing with Sprint / HTC Preinstalled Junk - Startup Auditor or Just wait for Root?

I would like to get everyone's opinion, I'm looking at a couple options of how to get rid of Sprint / HTC Junk that runs at startup and continues to startup - Sprint Nav, Sprint Zone, Nascar, all those things. I'd love to hear alternate suggestions as well.
1. Startup Auditor - Seems to do a decent job of keeping things from starting, definitely reduced boot time, but I'm unsure of how it actually operates - is it just another task killer? Or does it actually take things out of a startup list without running in the background? I've been playing with it for close to a day and am still undecided, at times it seems to help, but other times I don't think it really did anything. It seems like having root would make it completely pointless, since you could edit things yourself.
2. Wait for Root - I already did the OTA update so root is not possible, from what I understand. With root access, I'm sure it would be much easier to remove the actual applications, and furthermore install custom roms without the bloat.
3. ?? You tell me please
Thanks guys!
If you're comfortable using adb, you can root here: http://forum.xda-developers.com/showthread.php?t=718889
I rooted my yesterday after the OTA and flashed Fresh 0.5.3. It doesn't have most of the crapware.
gx1400 said:
If you're comfortable using adb, you can root here: http://forum.xda-developers.com/showthread.php?t=718889
I rooted my yesterday after the OTA and flashed Fresh 0.5.3. It doesn't have most of the crapware.
Click to expand...
Click to collapse
Funny I was just reading that. I have zero experience with ADB, but perhaps that is the best route. Can't be too hard to learn, right?
Thanks for posting that. If you have root, it mostly eliminates the need for a program like startup auditor, right?
berardi said:
Funny I was just reading that. I have zero experience with ADB, but perhaps that is the best route. Can't be too hard to learn, right?
Thanks for posting that. If you have root, it mostly eliminates the need for a program like startup auditor, right?
Click to expand...
Click to collapse
Correct. Most ROMs already have the crapware removed, however, once rooted you'll also have the ability to remove and do anything else you want.
If you are uncomfortable with adb, don't be. There are enough tutorials and videos around to walk you through the process. Not only was I a complete noob when I moved to Andriod from the iPhone but I am also using a Mac which means the commands are slightly different. However, with a little trial and error I was able to root via adb the very weekend the phone was released when only adb instructions existed.
And, going forward you'll never have to wait for "Idiot Guides" again. Whenever something new and great comes along you'll have the skills to implement it right away.
okolowicz said:
Correct. Most ROMs already have the crapware removed, however, once rooted you'll also have the ability to remove and do anything else you want.
If you are uncomfortable with adb, don't be. There are enough tutorials and videos around to walk you through the process. Not only was I a complete noob when I moved to Andriod from the iPhone but I am also using a Mac which means the commands are slightly different. However, with a little trial and error I was able to root via adb the very weekend the phone was released when only adb instructions existed.
And, going forward you'll never have to wait for "Idiot Guides" again. Whenever something new and great comes along you'll have the skills to implement it right away.
Click to expand...
Click to collapse
I'm trying to setup ADB right now but I'm stuck here:
http://forum.xda-developers.com/showthread.php?t=694250
3. Enabling ADB support on EVO
If using completely stock EVO, adb will be disabled in recovery and can't be enabled.
Click to expand...
Click to collapse
So if you can't enable ADB on stock EVO, but you need ADB to root - what to do?
EDIT : Nm I think I got it
I want to say that if you plug your phone into your computer and select sync option, that it will install the necessary drivers. Just make sure to turn on usb debugging in your settings menu: menu,settings, applications, development, usb debugging- check the box.
elegantai said:
I want to say that if you plug your phone into your computer and select sync option, that it will install the necessary drivers. Just make sure to turn on usb debugging in your settings menu: menu,settings, applications, development, usb debugging- check the box.
Click to expand...
Click to collapse
Thanks got it..
I'm following these instructions, they seem the most complete. I followed every step successfully and refreshed the pages, and it told me to reboot and run part2. However when I hit
adb reboot
it returns
adb: permission denied
What did I do wrong here?
EDIT: Missed hitting exit. That step wasn't there in original, it is in the recompiled though.
go read up on that thread, do a search for 'permission denied' or the like and I am sure something will come.I saw it a few times while reading that thread
err... Are you sure it didnt just mean reboot your phone?
elegantai said:
go read up on that thread, do a search for 'permission denied' or the like and I am sure something will come.I saw it a few times while reading that thread
err... Are you sure it didnt just mean reboot your phone?
Click to expand...
Click to collapse
haha thanks I was messed up because the original instructions didn't say to exit the adb shell (I probably should have known though) but now I'm past that, now to reboot and hit adb shell /data/local/part2 in time lol this is fun :-D
All done!!! :-D now to flash rom... good times!
Thanks all

ROOT FAIL HELP PLEASE probably wrong spot but i'm new to android and i am panicking

i have a new nexus 7 2013 and i messed up big time im no good with all this adb stuff i unlocked it rooted. wouldnt boot. went in team win recovery project and somehow ended up deleting the os i cant get the computer to recognize the device to install the os if thats even possible or if i even could find out how. the computer just calls it flo and says i need to update the driver which it is or i culdnt of rooted(failed)... thanks any help is much appreciated. some on recommended to mount but cant get it to connect to computer.
UTubeMeBeach said:
i have a new nexus 7 2013 and i messed up big time im no good with all this adb stuff i unlocked it rooted. wouldnt boot. went in team win recovery project and somehow ended up deleting the os i cant get the computer to recognize the device to install the os if thats even possible or if i even could find out how. the computer just calls it flo and says i need to update the driver which it is or i culdnt of rooted(failed)... thanks any help is much appreciated. some on recommended to mount but cant get it to connect to computer.
Click to expand...
Click to collapse
Try this
http://forum.xda-developers.com/showthread.php?t=2381582
http://goo.gl/lF0HEC
This is the driver you need to install to use ADB while in recovery which is different to the one for Fastboot and ADB while booted.
Perhaps this is what you are facing?: http://forum.xda-developers.com/showthread.php?t=2380913 The fact that you lost the OS leads me to believe so. Match the thread to your problem, however. If the information in the thread I linked to doesn't match your issue, then your best bet would be the one-click factory recovery mentioned earlier in the thread. Best of luck, from one novice, shaky rooter to another!
thetechaddict10 said:
Perhaps this is what you are facing?: http://forum.xda-developers.com/showthread.php?t=2380913 The fact that you lost the OS leads me to believe so. Match the thread to your problem, however. If the information in the thread I linked to doesn't match your issue, then your best bet would be the one-click factory recovery mentioned earlier in the thread. Best of luck, from one novice, shaky rooter to another!
Click to expand...
Click to collapse
OMG if this works ill pm you and tell you
thetechaddict10 said:
Perhaps this is what you are facing?: http://forum.xda-developers.com/showthread.php?t=2380913 The fact that you lost the OS leads me to believe so. Match the thread to your problem, however. If the information in the thread I linked to doesn't match your issue, then your best bet would be the one-click factory recovery mentioned earlier in the thread. Best of luck, from one novice, shaky rooter to another!
Click to expand...
Click to collapse
omg gimme your paypal email?? you saved my ass dude that worked perfect id be glad to pay you a couple dollars and thanks for everyone else who helped
UTubeMeBeach said:
omg gimme your paypal email?? you saved my ass dude that worked perfect id be glad to pay you a couple dollars and thanks for everyone else who helped
Click to expand...
Click to collapse
If you insist, there should be a "Donate to Me" box next to my information on the left.
I had the same problem. Got stuck with no OS installed, USB debugging disabled, and no ROM I could flash. I was scared ****less but I ended up fixing it with a restore program.
Glad you got it fixed.
I learned how to unlock, root, flash custom kernels with my old nexus 7 before I attempted on my new nexus 7. Didn't want to make an expensive mistake. I looked at things here last year when I got my first n7, got confused and didn't attempt it. Now, I definitely won't go back to just stock. Hope you get it all sorted out! It was definitely scary for me the first time.
Sent from my Nexus 7 using Tapatalk 4
I don't think I've ever heard of a case where someone permanently soft-bricked their device.
This irrational fear of "bricking" your device if you do something wrong needs to stop.
If your device gets soft-bricked, just flash the stock images - fixes it every time.
Geodude074 said:
I don't think I've ever heard of a case where someone permanently soft-bricked their device.
This irrational fear of "bricking" your device if you do something wrong needs to stop.
If your device gets soft-bricked, just flash the stock images - fixes it every time.
Click to expand...
Click to collapse
It's mainly the word "brick" that gets on my nerves.
Most of these are really just bootloops or boot hangs. My last one was the latter (and a little unsettling, I'll admit). Turns out that trying to flash a root zip before you've signed into the tablet at least somewhere to create the sdcard directories just leads to a headache for me.

[Q] What should I do to restore my Nexus 7 (2013) to work on which I tried to root?

Hello,
I tried to root my new Nexus 7 (2013). I am not able to post the link of the tutorial which I followed (from androidrootz). I tried contacting the author of that tutorial - he did try his best but was not able to change the state.
When about to complete the entire process, close to the finish - I am not able to get inside the "Recovery Mode" to install Super User SU. i.e. When I press recovery mode in the bootloader I get the Google logo and it stays there till battery runs out.
Now when I start the tablet normally, I get the Google logo and the nexus logo. Then nexus logo stays there till the battery runs out.
I am a developer and I kinda need the tablet to run. My main purpose of rooting the tablet is to use certain admin feature and install a custom ROM.
If I could straighten up my tablet to work the way it does - that would really great. I am not bothered about the loss of data at all.
I could use both Windows and Mac to get things in order. At this moment I am not sure what the problem is nor do I know what to do.
If someone could guide me thro' to get the tablet up and running the normal, I highly appreciate it.
Thank you and regards,
Karsnen.
karsnen said:
Hello,
I tried to root my new Nexus 7 (2013). I am not able to post the link of the tutorial which I followed (from androidrootz). I tried contacting the author of that tutorial - he did try his best but was not able to change the state.
When about to complete the entire process, close to the finish - I am not able to get inside the "Recovery Mode" to install Super User SU. i.e. When I press recovery mode in the bootloader I get the Google logo and it stays there till battery runs out.
Now when I start the tablet normally, I get the Google logo and the nexus logo. Then nexus logo stays there till the battery runs out.
I am a developer and I kinda need the tablet to run. My main purpose of rooting the tablet is to use certain admin feature and install a custom ROM.
If I could straighten up my tablet to work the way it does - that would really great. I am not bothered about the loss of data at all.
I could use both Windows and Mac to get things in order. At this moment I am not sure what the problem is nor do I know what to do.
If someone could guide me thro' to get the tablet up and running the normal, I highly appreciate it.
Thank you and regards,
Karsnen.
Click to expand...
Click to collapse
If you can get into bootloader, you should be able to recovery. I suggest you follow the guide here:
http://forum.xda-developers.com/showthread.php?p=44888268#post44888268
and choose the flash-all option which will wipe user data and start fresh.
sfhub said:
If you can get into bootloader, you should be able to recovery. I suggest you follow the guide here:
http://forum.xda-developers.com/showthread.php?p=44888268#post44888268
and choose the flash-all option which will wipe user data and start fresh.
Click to expand...
Click to collapse
It worked. Thank you so much.
I just want to know, if you could recommend a guide for rooting the new nexus 7 on windows machine, what would that be?
Thank you once again.
Check in the stickies for detailed instructions. If you just want a simple summary:
http://forum.xda-developers.com/showthread.php?p=44597339#post44597339
sfhub said:
If you can get into bootloader, you should be able to recovery. I suggest you follow the guide here:
http://forum.xda-developers.com/showthread.php?p=44888268#post44888268
and choose the flash-all option which will wipe user data and start fresh.
Click to expand...
Click to collapse
So I'm using a Mac OSX 10.8.4, and the new Nexus 7 (2013) version. I unlocked my bootloader, but I cannot get it into recovery mode, and I'm a little nervous. This is my first android device, but I've been an avid iOS jailbreaker since the OG iPhone. Can any of you point me to an extremely thorough guide on how to both fix my current issues, and then properly Unlock, Recovery, Root, and Flash Custom ROMs to this tablet?
Thank you so much.
tr00gle said:
So I'm using a Mac OSX 10.8.4, and the new Nexus 7 (2013) version. I unlocked my bootloader, but I cannot get it into recovery mode, and I'm a little nervous. This is my first android device, but I've been an avid iOS jailbreaker since the OG iPhone. Can any of you point me to an extremely thorough guide on how to both fix my current issues, and then properly Unlock, Recovery, Root, and Flash Custom ROMs to this tablet?
Thank you so much.
Click to expand...
Click to collapse
Buddy,
I was in the exact similar position as you are. Do not fear. Just follow the response I got above. It will help you.
Just follow it.
regards,
Karsnen.
karsnen said:
Buddy,
I was in the exact similar position as you are. Do not fear. Just follow the response I got above. It will help you.
Just follow it.
regards,
Karsnen.
Click to expand...
Click to collapse
Are the commands the same in terminal, or should I run windows in a VM to use the command line?
The only cmd in that post is flash-all
It is the same. Get into the directory and enter flash-all when you have to, in the terminal.
When I'm in the VM in windows, I go to the directory, but then it says "flash-all" is not a valid command. What am I doing wrong? It won't work in Terminal either. Can you please walk me through it. I feel so stupid as is, but I can't figure out what I'm doing wrong.
tr00gle said:
When I'm in the VM in windows, I go to the directory, but then it says "flash-all" is not a valid command. What am I doing wrong? It won't work in Terminal either. Can you please walk me through it. I feel so stupid as is, but I can't figure out what I'm doing wrong.
Click to expand...
Click to collapse
Did you unpack the google image download twice? (per the instructions) Once to get the tar from the tgz and a second to get the files from the tar.
sfhub said:
Did you unpack the google image download twice? (per the instructions) Once to get the tar from the tgz and a second to get the files from the tar.
Click to expand...
Click to collapse
Ok, I MUST be using the wrong guide or something, because I don't have any files with a .tar extension. I promise I'm not this dumb, but I can feel my frustration making me dumber. Halp
course ndighdl
tr00gle said:
Ok, I MUST be using the wrong guide or something, because I don't have any files with a .tar extension. I promise I'm not this dumb, but I can feel my frustration making me dumber. Halp
Click to expand...
Click to collapse
OK, i forgot to download the image files from google. Now I'm doing it, and it says fastboot is not a valid command, and nothing is happening.
tr00gle said:
OK, i forgot to download the image files from google. Now I'm doing it, and it says fastboot is not a valid command, and nothing is happening.
Click to expand...
Click to collapse
Did you do step #3 in the guide?
http://forum.xda-developers.com/showthread.php?t=2428194
sfhub said:
Did you do step #3 in the guide?
http://forum.xda-developers.com/showthread.php?t=2428194
Click to expand...
Click to collapse
Is that link to the guide? there wasn't one on that link. I appreciate you replying this many times already, but I just need one set of steps to follow, that are clear and detailed. That's all. Do I need to use windows, mac or linux? I have a macbook pro, but I can run windows or linux in parallels if necessary. I just need to KNOW. Please.

[Q] Galaxy Nexus help

Hi,
I require advice as to how i should proceed with my recent purchase blunder.
Background: I required a cell since my current one started acting up with frequent call drops and shut downs. I scoured my local craiglist and got a used Galaxy Nexus for ~$ 100. The guy said it wasn't rooted, and so i proceeded to purchase, but only realised now that the cell is infact rooted, with ClockworkMod (not well versed with droid) and some functions / options do not work as intended. I want to unroot it and i tried to follow this guide, but it gets stuck at
Code:
fastboot reboot-bootloader
saying waiting for device.
Not sure what to do as i'm fine even if i have to stay rooted, but i want the damn thing to work properly.
Also, if anyone can recommend how i go about installing ROM's
Regards,
Probably drivers. Just manually boot into bootloader.. And then flash the factory image.
Sent from my Galaxy Nexus using xda app-developers app
Fastboot reboot-bootloader command will only work if you are already in the bootloader mode anyways...
As @mrgnex said, just do it manually, or use adb commands to boot into bootloader where THEN you use fastboot command.
To manually get into bootloader/fastboot mode; power down, then hold power button and volume up AND down all at same time for few seconds, it'll vibrate and you'll be in the bootloader mode where u can issue the fastboot commands.
Ok. I tried to put the .tgz file onto the cell and tried to install the file from there which is ~250mb. But when i try to select installing from s/d card, it does not show up the file there. I am most cretain i'm doing something wrong, and so would like to know what it is ? Any other guide that could be a little easy to follow ??
You don't actually move the factory images onto your phone.
One of the sticky threads here is called "return to stock". That should guide you in the right direction.
Sent from my Galaxy Nexus using xda app-developers app
huzzug said:
Ok. I tried to put the .tgz file onto the cell and tried to install the file from there which is ~250mb. But when i try to select installing from s/d card, it does not show up the file there. I am most cretain i'm doing something wrong, and so would like to know what it is ? Any other guide that could be a little easy to follow ??
Click to expand...
Click to collapse
it's great that you're learning to do this Droid life has a good howto, just google "droidlife how to root galaxy nexus"
if worse comes to worse you can use this toolkit that does it for you, it's called wugfresh google "wugfresh nexus toolkit"
If you want to install ROMs you download the zip right on your device (make sure you get a ROM zip file AND a gapps zip file. They are linked in pretty much every OP for ROMs)
Downloading a ROM zip directly from/on device is easiest because then you do not have to transfer the file(s) over to your device in order to "flash"(aka install). Then all you do is go into recovery mode. Then go to install, then choose your ROM zip file. After that installs, then install gapps file the same way, always install gapps zip AFTER the rom zip.
If you use TWRP as your custom recovery you can "queue" your zip installs(choose rom zip and then you can choose to add another zip file and it will flash them both for ya)
And usually it is recommend to do a factory reset from recovery before you reboot into system. (Make sure to not wipe ALL /data...choose factory reset...wiping ALL /data will wipe /sdcard contents as well)
This all might seem foreign and difficult at first, but once you've done it once or twice(or more... you might become what we call a "crack flasher"-one who is constant changing ROM and kernel and setups lol, that's when it gets REALLY fun) so do not get discouraged. Especially if you don't understand the terminology we all use, you will become familiar with it quickly. And remember, Google is your best friend, almost any questions you might have will yield MANY helpful results when you put in a Google search, highly recommend that if using Google for trying to get useful info to put things like "how to install custom recovery "Galaxy Nexus" xda" to get the best info possible )
And do not be afraid to ask us either if you feel lost. It's easier to prevent an issue than to fix it(though fixing a borled Gnex is fairly easy with all the tools available here and elsewhere)
As for going back completely to stock, as mentioned above, to do that you aren't putting any files onto your device itself. You download them to PC(I use my laptop) and install from there using fastboot. When you download the factory img that is for your specific device and unzip it (I believe they still come compressed... If not ignore that part sorry!) You will see inside there is a script called "flash-all.sh" OR if using windows use the "flash-all.exe" that will automate the fastboot commands needed for a full factory stock restore of the device.
I could link you to posts containing useful how-tos and info and such, but right now I'm viewing forum via Tapatalk app on my device and really gonna be lazy and just say look at the "Sticky posts" in General, Q&A, and Development sections, those are most likely what I would link to you here.
After reading through some of those, if you need clarification of steps taken or something, come on back and let us know.
huzzug said:
Hi,
I require advice as to how i should proceed with my recent purchase blunder.
Background: I required a cell since my current one started acting up with frequent call drops and shut downs. I scoured my local craiglist and got a used Galaxy Nexus for ~$ 100. The guy said it wasn't rooted, and so i proceeded to purchase, but only realised now that the cell is infact rooted, with ClockworkMod (not well versed with droid) and some functions / options do not work as intended. I want to unroot it and i tried to follow this guide, but it gets stuck at
Code:
fastboot reboot-bootloader
saying waiting for device.
Not sure what to do as i'm fine even if i have to stay rooted, but i want the damn thing to work properly.
Also, if anyone can recommend how i go about installing ROM's
Regards,
Click to expand...
Click to collapse
Not sure getting the GN was a good idea even for $100, surely there must have been better options.
SolGoodGuy said:
Not sure getting the GN was a good idea even for $100, surely there must have been better options.
Click to expand...
Click to collapse
Maybe on contract for that price yes.
But for $100 no contract, that's not bad for a Gnex.. considering I paid ~400 just over 1.5yrs ago lol. And a highly developed device at that.
MAYBE could have found another device for a little bit more in the 150-200 range that was newer. But 100aint bad for a gnex
ashclepdia said:
Maybe on contract for that price yes.
But for $100 no contract, that's not bad for a Gnex.. considering I paid ~400 just over 1.5yrs ago lol. And a highly developed device at that.
MAYBE could have found another device for a little bit more in the 150-200 range that was newer. But 100aint bad for a gnex
Click to expand...
Click to collapse
I see an optimus G on swappa for $115. Much better phone.
Actually, I ain't in US guys. And whatever I found was a personal preference as I wanted this model and not any other.
Bumpity bump
huzzug said:
Bumpity bump
Click to expand...
Click to collapse
Bump?
Did you ever try what I said?
You need to download the factory img needed and run the flash all script...
Edit::
HERE go to this thread.
http://forum.xda-developers.com/showthread.php?t=2726518
Follow my advice there, except make sure to grab maguro img for your device. Be sure to grab the correct package for your device (takju yakju, etc...it will tell u in bootloader mode which one u have)

Need To Obtain Procedure As To How To Get Into Recovery Mode

Hi,
I'm trying to get into the recovery mode on my LG G5 H830 (T-Mobile / Unlocked) phone. Unless I'm doing something wrong, I can't seem to get into the recovery mode so I can perform a wipe data cache function. I seem to remember reading somewhere else that the only way to get into recovery on this phone is to use a computer to do so. On my desktop computer I already have the android studio application installed, but to be honest I'm still trying to learn how to use it. I don't know why lg makes getting into the recovery mode so difficult. I guess I can try to use the buttons on the phone one more time and see if I have any luck. Also I've read possibly using TWRP will possibly let me perform a wipe data cache function. Thank you for any valid suggestions.
David
Davy49 said:
Hi,
I'm trying to get into the recovery mode on my LG G5 H830 (T-Mobile / Unlocked) phone. Unless I'm doing something wrong, I can't seem to get into the recovery mode so I can perform a wipe data cache function. I seem to remember reading somewhere else that the only way to get into recovery on this phone is to use a computer to do so. On my desktop computer I already have the android studio application installed, but to be honest I'm still trying to learn how to use it. I don't know why lg makes getting into the recovery mode so difficult. I guess I can try to use the buttons on the phone one more time and see if I have any luck. Also I've read possibly using TWRP will possibly let me perform a wipe data cache function. Thank you for any valid suggestions.
David
Click to expand...
Click to collapse
Hi David!
Holy cow, you've installed the entire studio? That's way more than you need. Just get the Platform Tools here: https://developer.android.com/studio/releases/platform-tools
At a user level, all you'll ever need are ADB and fastboot. Then enable developer settings, enable USB debugging and use the command 'adb reboot recovery'. You sure power + volume down don't work? Or power + volume up for fastboot (to get custom recovery installed)? Note that I have made zero research on this device so it may deviate (I'm on mobile right now). If any of those steps seem difficult or you're unsure how to proceed, just let me know where exactly you're stuck.
Oh and when you send an adb command to your device for the first time (like 'adb devices') it will likely show a trust notification on your screen, asking you to allow this computer to send adb commands. Make sure the remember checkbox is on.
Good luck!
Wrapped with delicious Fajita [emoji896]
Hi Timmy,
Thanks for being nice and explaining the process to me, that sounds pretty easy. Today my biggest problem is getting vanced to install on my amazon fire 7 tablet (2019 Edition). I've had it running normally on there previously, but a couple of day's ago I started the vanced app and noticed that I wasn't signed into my google account anymore. And when I attempted to sign in I received the now famous notice that said google server's were busy, please try again later. But knowing I had it running before, motivates me to get it running again. In the interim, I'm using the Web Tube app.
David
That's usually a matter of uninstalling both, installing MicroG first, then Vanced.
Wrapped with delicious Fajita [emoji896]
Timmmmaaahh said:
That's usually a matter of uninstalling both, installing MicroG first, then Vanced.
Wrapped with delicious Fajita [emoji896]
Click to expand...
Click to collapse
Hi Timmy,
Unfortunately I've already tried that, now I'm wondering if it's possibly due to me installing google web view on my tablet. All I can do is just keep trying to figure it out.
Thanks, David
Davy49 said:
Hi Timmy,
Unfortunately I've already tried that, now I'm wondering if it's possibly due to me installing google web view on my tablet. All I can do is just keep trying to figure it out.
Thanks, David
Click to expand...
Click to collapse
Proper reboots in between? I don't see how web view would be related but it's always a good exercise to remove recent installations one by one, retrying Vanced in between. Be sure to share your findings if you encounter a potential culprit. It's important for the community to learn from that.
Hi Timmy (I guess it's okay to use this name),
I think before I do anything else, I'll go back and re-read the instructions on how to properly install it. Unless google has done something on their end, I should be able to get it functioning properly. It was installed previously, that's why I don't know what happened.
Thanks,
David

Categories

Resources