Related
Well, after spending almost 11 hours trying to boot into recovery or download, I know for sure that there is something going on with my phone re: hardware locked. The date on my box is 7-16. It is an early Vibrant. But no matter what I do, I cannot get into download or recovery which means my ****ing phone is literally worthless.
I have tried all possible thousands of combination's of buttons, batteries, and cords while booting and nothing happens.
The Vibrant logo shows, then it shows the pink, annoying as hell T-mobile logo, than goes to the Galaxy S logo which loads for a little bit and then just leads me to a black screen. Eventually the 4 buttons on the front of the phone turn on and then nothing else happens. It will just sit like this forever.
I know all I need to do is get a working ROM loaded but it is literally impossible to do so.
Can anyone offer any suggestions? Or are anyone else having the same problem?
I guess the only way I can get a working phone is to get in touch with T-mobile and do a Warranty exchange. That's a damn shame too, because I will be without a working phone for a week.
What about using adb?
adb reboot recovery -or- adb reboot download ?
I had a hw locked vibrant, never tried the adb reboot download, recovery did work.. I added another line on my account last night for somone, who got a vibrant, theirs wasn't hw locked, so I traded 'em ;P
Agree with the above poster I have been stuck on the vibrant screen or dark screen and adb still worked to save me
when i try to use adb, it just tells me that it cant find the device. i'm not able to boot into android OS at all.... screen just hangs. so my computer is never getting a chance to see my phone hence why i cant use adb to reboot it into recovery or download.
I believe your device has to go into recovery mode then check with and devices and if you see a device I THINK it is and reboot download, I am 90% certain
Sent from my SGH-T959 using Tapatalk
have you installed the drivers? phone DOES NOT have to boot into android for adb to read it.
98classic said:
have you installed the drivers? phone DOES NOT have to boot into android for adb to read it.
Click to expand...
Click to collapse
i do believe i have the correct drivers installed. i was able to use adb to run lagfixes before i was having this problem. when i boot my phone, i get a sound from my computer saying that it recognizes a usb device. the two drives in the vibrant show up in My Computer but i cannot access them as windows says they are not accessable at the moment.
at what point will adb be able to recognize my phone when booting? no matter what i do when i try adb shell i get error: device not found
It could be the phone not bring in debugging mode, either because it's been turned off or the os isn't getting far enough to turn it on. I think I've been able to get adb to recognize my phone even while it was booting up (at the white vibrant screen). Maybe you can try adb then?
Same problem here. I probably just have to sell it fast on ebay or something. Hopefully some kind of fix starts by the end of the week. First phone in my smartphone life to brick from a simple Voodoo lag fix. Please XDA gods find a solution.
crazycaveman said:
It could be the phone not bring in debugging mode, either because it's been turned off or the os isn't getting far enough to turn it on. I think I've been able to get adb to recognize my phone even while it was booting up (at the white vibrant screen). Maybe you can try adb then?
Click to expand...
Click to collapse
nope, no go. adb will not recognize my device no matter what. and the device isnt loading the OS so i cannot turn debugging on. i guess this is a real "brick" then.
This sounds like a rant rather than a question. Just sayin'.
DKYang said:
This sounds like a rant rather than a question. Just sayin'.
Click to expand...
Click to collapse
fixed that. my bad.
Check my thread in the dev section... I can get ADB working when you are stuck at the vibrant screen... MIGHT... just might work in your situation...
My thread is probably fallen back a few pages now... its a [Guide] [Think Tank]
renocivik said:
Check my thread in the dev section... I can get ADB working when you are stuck at the vibrant screen... MIGHT... just might work in your situation...
My thread is probably fallen back a few pages now... its a [Guide] [Think Tank]
Click to expand...
Click to collapse
thanks for the suggestion. i found your thread and went through the steps in the OP... still no luck. no matter what i do, i cannot get passed the black screen the loads after the galaxy s logo. i also cannot get into download mode or recovery no matter what combination of button presses i use.
just do the following , i used to have the problem of going into the download mode and this is what realy worked to me :
1- turn off the phone.
2- plug in the USB cable.
3- wait until the battery green charging start.
4- press the vol + , vol - , the power botton together.
5- when the screen gose black release the power botton only.
you should now be in the downloading mode
core99 said:
just do the following , i used to have the problem of going into the download mode and this is what realy worked to me :
1- turn off the phone.
2- plug in the USB cable.
3- wait until the battery green charging start.
4- press the vol + , vol - , the power botton together.
5- when the screen gose black release the power botton only.
you should now be in the downloading mode
Click to expand...
Click to collapse
this isnt working either. :-(
I just fixed this on my phone. Your phone will go into download mode. Plug the phone in and wait for the battery symbol to fully load. Hold Vol + and _ and PWR until it goes black, then release the PWR button only. It will go into DL mode. Fire up Odin, and flash the "Froyo that does not brick" ROM. It will boot into the i9000 recovery mode and give you an error. Hold the Vol + and - and PWR again and release PWR when the phone goes black. It will go into DL mode again. Now with Odin, flash the factory firmware, making sure to click re-partition this time. After the phone reboots, it will fire right up into the factory ROM.
atoz350 said:
I just fixed this on my phone. Your phone will go into download mode. Plug the phone in and wait for the battery symbol to fully load. Hold Vol + and _ and PWR until it goes black, then release the PWR button only. It will go into DL mode. Fire up Odin, and flash the "Froyo that does not brick" ROM. It will boot into the i9000 recovery mode and give you an error. Hold the Vol + and - and PWR again and release PWR when the phone goes black. It will go into DL mode again. Now with Odin, flash the factory firmware, making sure to click re-partition this time. After the phone reboots, it will fire right up into the factory ROM.
Click to expand...
Click to collapse
this is exactly the method i want to try. but unfortunately i cannot get the phone into recovery or download mode. i have tried at least 100 times now with many different combination's of plugging the usb cord in and pressing the volume and power buttons.
two ideas: one, is it possible that i wiped recovery and download mode from my phone on accident? the reason why i ask is that i was super tired and flashing roms and kernels to my phone. i flashed back to my original stock rom and then i flashed the kernel. for some reason, i selected wipe date/cache in Rom Manager before flashing the kernel. i have no idea why i did this. seriously. totally noob move. so im assuming i have a kernel flashed but now there is no ROM installed for the phone to boot into.
two, if above is not the issue, than im going to assume that the phone is not recognizing any button presses while its off, so when i turn it on it just recognizes that the power was pressed and ignores the volume presses, thus not booting the phone into recovery or download.
edit: i should mention again that at no time does adb recognize my device. so i cannot use adb to reboot the phone into the mode i need.
just a comment for the OP - the vibrant isnt worthless, it is something that YOU did to get the phone into its current state. So dont blame the phone for something that it didnt do on its own.
/end rant
byt3b0mb said:
just a comment for the OP - the vibrant isnt worthless, it is something that YOU did to get the phone into its current state. So dont blame the phone for something that it didnt do on its own.
/end rant
Click to expand...
Click to collapse
I understand what you mean. I appreciate your criticism of my original post. Let me say that I wrote it while frustrated. But I know that isn't an excuse.
The device is fantastic. I know that I did this to it myself. It's unfortunate.
Anyways, I received a replacement phone. I will be more careful this time.
Hey Guys, could sure use your help... i updated my 10.1 le yesterday and that went thru fine. Later on i was playing and watching youtube and it sent my tablet into a boot loop and i cant seem to fix it. any help would be appreciated thanks in advance.
Mine did the same thing when i was streaming music. Not even Odin brought it back. I used adb to reboot into stock 3e recovery and wipe data/factory reset it, then used Odin to grt back to 3.0.1. Then i just redownloaded the 3.1 update. Hope that helps
LovellKid said:
Mine did the same thing when i was streaming music. Not even Odin brought it back. I used adb to reboot into stock 3e recovery and wipe data/factory reset it, then used Odin to grt back to 3.0.1. Then i just redownloaded the 3.1 update. Hope that helps
Click to expand...
Click to collapse
right now im having problems with adb listing the devices. adb is installed. it keeps saying that i need some APX drivers???
Drivers are here:
http://www.samsung.com/us/support/owners/product/GT-P7510UWYXAR
I had the same problem. This is what i did. Since I had already rooted my tablet, I already had in my laptop ADB and the driver for the tablet. If you don't have these 2 things, I suggest you go to the development section of this forum, look for the insrltructions on how to root, and download what you need.
I connected my tablet then went into cmd mode (DOS MODE), then typed adb reboot recovery. From there the tablet rebooted into recovery. I then wiped data and cache. Then I rebooted and it went fine, no more bootloop. In settings I noticed that it had reverted back to 3.0.1 so I just did update again. Since then my tablet has been smooth as butter.
Sent from my GT-P7510 using XDA Premium App
For those not too comfortable with ADB, I just installed PDAnet (for the fastboot drivers) and after booting to fastboot (holding power and the volume down button and selecting the USB symbol) I used the "fastboot -w" command in CMD.exe to wipe the device.
Its rather strange that a lot of people are having problems. Mine started after getting an error turning on the WIFI chip. Thank god for Titanium Backup's option to sync with Dropbox. Hope this helps.
kdietze3 said:
For those not too comfortable with ADB, I just installed PDAnet (for the fastboot drivers) and after booting to fastboot (holding power and the volume down button and selecting the USB symbol) I used the "fastboot -w" command in CMD.exe to wipe the device.
Its rather strange that a lot of people are having problems. Mine started after getting an error turning on the WIFI chip. Thank god for Titanium Backup's option to sync with Dropbox. Hope this helps.
Click to expand...
Click to collapse
THANK YOU!! Your suggestion of installing PDAnet saved me! I was having a hell of a time trying to get the right drivers so my computer would recognize the tablet has an adb device. After installing PDAnet, it was a cinch. Then I reflashed everything, wiped userdata and cache, and rebooted (I followed the instructions found here: http://forum.xda-developers.com/showpost.php?p=14600617&postcount=111) Now my tab is working again and I was getting ready to ship it off to Samsung so they could re-flash it for me.
Follow this steps
The steps are this:
http://forum.xda-developers.com/showpost.php?p=15084897&postcount=123
Obviously I have installed adroid-sdk and download fastboot from HTC page.
I'm one of the lucky ones who has had their I/O tab stuck in a boot loop on 3.1, and after trying the steps below, I am not getting it to work. I know I must be making a stupid mistake somewhere along the line, but essentially,
I downloaded the new image, boot, and recovery files into a directory on my hard drive;
I installed PDAnet;
I entered into fastboot on my GTab and plugged it into my PC;
I can tell that fastboot is now listed as a device (I suspect this means that the drivers are installed correctly and that it is recognizing a fastboot device);
Now when I try to run the fastboot commands suggested, I get 'fastboot' is not recognized as an internal or external command...
Stupid question, but I am supposed to run this command from cmd.exe, right? Any ideas what I am doing wrong so that the fastboot commands are not recognizable? I may need a dumbed down instruction set if there are steps I am missing somewhere...
engljeff said:
I'm one of the lucky ones who has had their I/O tab stuck in a boot loop on 3.1, and after trying the steps below, I am not getting it to work. I know I must be making a stupid mistake somewhere along the line, but essentially,
I downloaded the new image, boot, and recovery files into a directory on my hard drive;
I installed PDAnet;
I entered into fastboot on my GTab and plugged it into my PC;
I can tell that fastboot is now listed as a device (I suspect this means that the drivers are installed correctly and that it is recognizing a fastboot device);
Now when I try to run the fastboot commands suggested, I get 'fastboot' is not recognized as an internal or external command...
Stupid question, but I am supposed to run this command from cmd.exe, right? Any ideas what I am doing wrong so that the fastboot commands are not recognizable? I may need a dumbed down instruction set if there are steps I am missing somewhere...
Click to expand...
Click to collapse
Edit:
After trying just about everything, I have concluded there are two hurdles I still cannot pass. First, if I fastboot my device, and select the USB icon, my device is appearing in my windows device list. However, I cannot run any fastboot commands in cmd.exe window. Not sure why or what else is needed. Second, I successfully installed SDK and tried to enter recovery mode through ADB, but I cannot find the magic trick to have my device appear in ADB. ODINing back to stock did not make a difference. If I can get past either of these hurdles I am confident I can progress, so any suggestions are appreciated.
fastboot commands never seem to work for me. Always says waiting for device.
ericc191 said:
fastboot commands never seem to work for me. Always says waiting for device.
Click to expand...
Click to collapse
Which makes me wonder if I am doing something wrong. I can't even get fastbook command to be recognized. It's as if there is some fastboot software needed so that my pc knows what to do when I type fastboot. I hoped SDK was enough, took a stab with a fastboot.exe from htc I found on another forum, neither worked. How did you get your pc to look for your device from fastboot in the first place?
Sent from my SGH-T959 using XDA App
Hi .. I have the same problems before
I found out that the new ADB has moved the directory to "platform-tools"
This renders the fastboot useless "winapiadb.dll"(or something) file not found pop up window
I got that ridiculous bootloop issue right in the middle of the flight! thought I bought a $$$ junk lol
use the fastboot -w option to recover .. but it resets the whole tablet back to OE (original everything)
Hey guys,
So I have one of the Limited Edition Google IO Galaxy Tab 10.1's and I can't find a more updated thread than this. It seems this problem is isolated or mostly isolated to the Limited Edition tabs?
Anyways, I've read through the thread (as well as many other resources) and I just don't understand what I'm supposed to do to defeat the boot loop problem.
For me, pressing the Power and Volume up button (or Power and Volume down button) doesn't do a thing. The tablet does not respond at all. The only thing other than the boot loop is that I can get it into "upload mode" whatever that is.
This thread doesn't mention upload mode, so I don't know how to proceed. I can't seem to find anything in the manual about this sort of hard reset, nor can I find any information anywhere else.
Also, I've read this thread, and I do not have any familiarity with what the following software projects are: Odin, PDAnet, and APX Drivers. I also have not used the android SDK.
Also, in the third post chris eckman posted a link to some sort of Galaxy Tab drivers on samsung's site, which is now a broken link.
Anyways, while I'm a noob to the XDA community, I am a computer engineer, and I'm confident I won't have any trouble recovering this device. There's just so much conflicting information and alternatives methods that I'm not sure how to proceed.
It seems like a tutorial might exist out there that I have not yet found?
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Clyde_Frog said:
Hey guys,
So I have one of the Limited Edition Google IO Galaxy Tab 10.1's and I can't find a more updated thread than this. It seems this problem is isolated or mostly isolated to the Limited Edition tabs?
Anyways, I've read through the thread (as well as many other resources) and I just don't understand what I'm supposed to do to defeat the boot loop problem.
For me, pressing the Power and Volume up button (or Power and Volume down button) doesn't do a thing. The tablet does not respond at all. The only thing other than the boot loop is that I can get it into "upload mode" whatever that is.
This thread doesn't mention upload mode, so I don't know how to proceed. I can't seem to find anything in the manual about this sort of hard reset, nor can I find any information anywhere else.
Also, I've read this thread, and I do not have any familiarity with what the following software projects are: Odin, PDAnet, and APX Drivers. I also have not used the android SDK.
Also, in the third post chris eckman posted a link to some sort of Galaxy Tab drivers on samsung's site, which is now a broken link.
Anyways, while I'm a noob to the XDA community, I am a computer engineer, and I'm confident I won't have any trouble recovering this device. There's just so much conflicting information and alternatives methods that I'm not sure how to proceed.
It seems like a tutorial might exist out there that I have not yet found?
Click to expand...
Click to collapse
Ok, well if you are running a "stock" IO bootloader, then you should have fastboot and download modes accessible to you by using the volume down and power button combo.
Have you ever gotten to this menu before? If not, then you just aren't doing it right. Let go of the power button part of this combo once the samsung logo appears, and then you should see two icons appear. If you have an IO bootloader, then you are going to go into fastboot mode, and then use fastboot to get your recovery booted. Once you get CWM booted, you can flash a stock ROM, load up stock recovery and wipe this sucker back to factory, and then fastboot your CWM recovery and install Task650's latest rom and be bootloop free. Let me know if you need further help.
Alright, first things first. Yes, this tablet is 100% stock, and I've done one major Android update, but it was not the one that broke everyone's wireless.
----------
So going step by step:
you should have fastboot and download modes accessible to you by using the volume down and power button combo. Have you ever gotten to this menu before?
So, I did once get to what I believe was the "fastboot" menu. I had four options available to me, the first one was something like "repair boot process" which I selected, because I was having a boot problem. It did nothing, and now I cannot get back to that menu.
I did get to the USB upload screen once by accident, when I was trying to get back to the boot menu, but not knowing what to do at that point. I had to shut it off.
Let go of the power button part of this combo once the samsung logo appears, and then you should see two icons appear.
Which Samsung logo? If I press both the power button and volume up or down, I get nothing. Nothing happens. If I press the power button first and then two seconds later start holding down the volume button, then eventually I get the blue swirly samsung screen. At the end of that, the samsung logo is clear. But waiting a bit longer, after about 30 seconds of blank screen, a pulsing white Samsung logo comes up, and I've never known which samsung logo to stop holding the power button. I believe I've tried every combination imaginable, and none of them work.
If you have an IO bootloader Do you mean Google I/O Stock bootloader? If not, I have no idea what this is in reference to.
Once you get CWM booted No idea what that is.
you can flash a stock ROM Where do I get that?
-------------
My bootloop might be different from everyone else's. Everyone else says "shut off the device, and then turn it on with the volume down/up held down. The problem with mine is that it NEVER shuts off! So, I can only do about 2 tests per day, because the only way I can shut it off is to let the battery run dead.
Mine switches from boot loop, and if I force that off, by holding down the power button for 10-15 seconds, then it immediately boots back up into "going into upload mode, cause unknown" If I force that screen off, it boots into the boot loop, so I can never boot from a "powered off" mode, again, unless I let the battery run dead.
I've tried every button pressing boot sequence I can think of with no luck. Can't I just upload something to the device in "upload mode" ? I don't need any data off this device, I just want it to be reset back to day 1, so that I can turn it on and use it.
Thanks so much for your help. As you might imagine, this is a very frustrating problem.
bootloop
can someone please help me ,i have a samsung galaxy tab 2 10.1 ,and its on boot loop ,always showing smsung galaxy tab 2 logo,i've tried restoring factory settings ,,didn't work ,i tried to install receovery from internal sd card says not found ,some one pleeaaase send me the steps of what to do
I tried to not start a new thread but ... I'm at a loss so here's the sitch..
I rooted, unlocked, and installed CWM using ViperMOD tool here
I got successful on upon running the program. Confirmed root, proceeded to unlock and install CWM. Like I said, the messages informed me of no errors and got successful. HOWEVER, when I power off the prime and attempt to button combo into recovery, the phone just boots up. I don't see text to even press the volume up button.. the only text I see is the asus kernel splash and boot ani..
I then went to RM and tried to flash CWM that way.. again i got successful but button combo's aren't working or I'm just not getting it right.. (thought, you should know I tried bout every damn combo I could think of, AFTER reading an trying what is suggested.) So then I tried rebooting into recovery via RM.. phone just reboots. I then tried installing touch recovery via RM.. got successful but again, no way to boot into recovery.
According to RM my current recovery is 5.8.x.x
I read another way to install CWM via BLOB, but I've also read installing anything BLOB after installing CWM will lead to a brick. Obviously I'm trying to avoid that. For the love Android, if anyone can point me in the right direction I'd be really happy. Thank you!
*EDIT****UPDATE**
This is a little confusing as i just watched yet another how-to vid.. and this one showed booting into recovery from power on .. and I don't believe it but it worked. Finally saw the 3 text lines at the top when Asus spash showed up. I powered off the Prime and tried again.. no problems whatsoever.
I'm sorry for starting a new thread.. believe me, I started searching yesterday and gave up at 11:30 last night.. started my quest again this morning and no dice so I started a new thread. Again.. Jerdog, I'm sorry man. Ugh.. feeling pretty bad about this thread now. If it can be deleted, please do. Otherwise close.. :-\
[/YOUTUBE]
Coreym said:
I tried to not start a new thread but ... I'm at a loss so here's the sitch..
I rooted, unlocked, and installed CWM using ViperMOD tool here
I got successful on upon running the program. Confirmed root, proceeded to unlock and install CWM. Like I said, the messages informed me of no errors and got successful. HOWEVER, when I power off the prime and attempt to button combo into recovery, the phone just boots up. I don't see text to even press the volume up button.. the only text I see is the asus kernel splash and boot ani..
I then went to RM and tried to flash CWM that way.. again i got successful but button combo's aren't working or I'm just not getting it right.. (thought, you should know I tried bout every damn combo I could think of, AFTER reading an trying what is suggested.) So then I tried rebooting into recovery via RM.. phone just reboots. I then tried installing touch recovery via RM.. got successful but again, no way to boot into recovery.
According to RM my current recovery is 5.8.x.x
I read another way to install CWM via BLOB, but I've also read installing anything BLOB after installing CWM will lead to a brick. Obviously I'm trying to avoid that. For the love Android, if anyone can point me in the right direction I'd be really happy. Thank you!
Click to expand...
Click to collapse
I had the same issue with the TF101, TF201 is the same...POWER OFF completly, now POWER ON HOLDING POWER AND VOLUME DOWN until white writting comes up on TOP LEFT OF SCREEN, then let go of power and volume down and press VOLUME UP you should see "ENTERING RECOVERY IMG"
i did a quick vid and put on YOUTUBE for you check it out,
hope it helps
LNKNPRKFN said:
I had the same issue with the TF101, TF201 is the same...POWER OFF completly, now POWER ON HOLDING POWER AND VOLUME DOWN until white writting comes up on TOP LEFT OF SCREEN, then let go of power and volume down and press VOLUME UP you should see "ENTERING RECOVERY IMG"
i did a quick vid and put on YOUTUBE for you check it out,
http://www.youtube.com/watch?v=1VOiCogOQJ0&list=UUdwXLQixIUNxzkX0zHVsYpQ&index=1&feature=plcp
hope it helps
Click to expand...
Click to collapse
Thanks dude.. Yeah, this was a stumper for me. As I did the button combo right, and maybe just maybe I let go too soon when seeing the asus screen, but I can tell you I tried endlessly last night and never saw the little text in the top left corner. Just watched zedo's vid and he started from power on.. so I tried, and it worked. Now i see the little text everytime I button combo..
Oh well.. really glad I got it figured out.. and thank you so much for the reply and help. Really!
Coreym said:
Thanks dude.. Yeah, this was a stumper for me. As I did the button combo right, and maybe just maybe I let go too soon when seeing the asus screen, but I can tell you I tried endlessly last night and never saw the little text in the top left corner. Just watched zedo's vid and he started from power on.. so I tried, and it worked. Now i see the little text everytime I button combo..
Oh well.. really glad I got it figured out.. and thank you so much for the reply and help. Really!
Click to expand...
Click to collapse
I must have NVFlashed my TF101 100x cause i thought CWM didnt do on because i use quickboot and it didnt go to recovery and i didnt know how to get it there but then i figured it out, so since my prime is the same its GRAVY, at least you got it now!!!
food for thought: i have flashed my sgs and my maguro countless times both combined, and i never ever encountered such an error. Either adb reboot recovery, native rom option or if neither are available, button combo.
/offtopic: i'm eager to see what nvflash can do. definately more powerful than fastboot
Hi there,
I juste got a cheapo Azpen A729 tablet. I succesfully rooted it with Kingo Root and it was also recognized by ADB. I then tried to boot into bootloader through ADB, but it never when past the Azpen logo screen and since then the tablet is stuck at the that screen whenever I try to restart it. So I'm afraid that I bricked it... On the Azpen website there are firmwares for several of their devices, but not for the A729. Does anyone have experience with this device and maybe some advice? Thanks!
maksmtl said:
Hi there,
I juste got a cheapo Azpen A729 tablet. I succesfully rooted it with Kingo Root and it was also recognized by ADB. I then tried to boot into bootloader through ADB, but it never when past the Azpen logo screen and since then the tablet is stuck at the that screen whenever I try to restart it. So I'm afraid that I bricked it... On the Azpen website there are firmwares for several of their devices, but not for the A729. Does anyone have experience with this device and maybe some advice? Thanks!
Click to expand...
Click to collapse
yes you bricked your device.
you rooted that device, but not unlock dootloader.
Hi,
I just tried to boot into bootloader, not to unlock it or anything else. I simply rooted the device, I didn't try to install any custom recovery (not that there would be one anyway, AFAIK) or anything like that. If I'm missing something here, would you mind to explain? Thanks.
Paget96 said:
yes you bricked your device.
you rooted that device, but not unlock dootloader.
Click to expand...
Click to collapse
maksmtl said:
Hi,
I just tried to boot into bootloader, not to unlock it or anything else. I simply rooted the device, I didn't try to install any custom recovery (not that there would be one anyway, AFAIK) or anything like that. If I'm missing something here, would you mind to explain? Thanks.
Click to expand...
Click to collapse
Ok, I understand
This device have stock recovery???
Yes, everything is stock, the only thing I did was rooting it with Kingo Root, like so: http://forum.xda-developers.com/android/help/root-azpen-a729-t3003908
Unfortunately there isn't much information out there yet for the A729, it seems to be fairly recent. Treecheetahdolo here managed to unbrick his A727, but unfortunately there is no firmware (yet?) available for the A729 on azpens site to try this...
Paget96 said:
Ok, I understand
This device have stock recovery???
Click to expand...
Click to collapse
maksmtl said:
Yes, everything is stock, the only thing I did was rooting it with Kingo Root, like so: http://forum.xda-developers.com/android/help/root-azpen-a729-t3003908
Unfortunately there isn't much information out there yet for the A729, it seems to be fairly recent. Treecheetahdolo here managed to unbrick his A727, but unfortunately there is no firmware (yet?) available for the A729 on azpens site to try this...
Click to expand...
Click to collapse
Go to recovery and wipe data and cache.
I'd like to, but I'm not able to go into recovery unfortunately... It's supposed to be vol-down + power button (http://www.azpenpc.com/service/detail.php/id-9.html), at least for the earlier devices, but this doesn't seem to work here, it always gets to the Azpen logo screen and gets stuck there... I tried every other key combination I could think of, but to no avail. Either the device is seriously bricked, or there's a secret key combination here to go into recovery that azpen didn't communicate...
Paget96 said:
Go to recovery and wipe data and cache.
Click to expand...
Click to collapse
maksmtl said:
I'd like to, but I'm not able to go into recovery unfortunately... It's supposed to be vol-down + power button (http://www.azpenpc.com/service/detail.php/id-9.html), at least for the earlier devices, but this doesn't seem to work here, it always gets to the Azpen logo screen and gets stuck there... I tried every other key combination I could think of, but to no avail. Either the device is seriously bricked, or there's a secret key combination here to go into recovery that azpen didn't communicate...
Click to expand...
Click to collapse
The [Vol- ] [POWER] combo works, but you have to hold them until the unit powers on, (like forever). If it won't go past the Azpen LOGO, I would recommend contacting your local supplier.
Ok, so if, when you boot into recovery, it still passes through the Azpen logo, then there might definitely be a problem... :-/ Mrdownboy, you have a A729, right? Did you already boot into the bootloader at some point? This thing does have a bootloader, right? I contacted Azpen to see if they have a firmware image that I could try to flash, before trying to going through a RMA procedure with my rooted tablet... We'll see. Anyway, thanks!
mrdownboy said:
The [Vol- ] [POWER] combo works, but you have to hold them until the unit powers on, (like forever). If it won't go past the Azpen LOGO, I would recommend contacting your local supplier.
Click to expand...
Click to collapse
maksmtl said:
Ok, so if, when you boot into recovery, it still passes through the Azpen logo, then there might definitely be a problem... :-/ Mrdownboy, you have a A729, right? Did you already boot into the bootloader at some point? This thing does have a bootloader, right? I contacted Azpen to see if they have a firmware image that I could try to flash, before trying to going through a RMA procedure with my rooted tablet... We'll see. Anyway, thanks!
Click to expand...
Click to collapse
Hey maksmtl,
I haven't tried accesing the bootloader yet, I'm still on the process of acquiring another brand new A729 for dumping the ROM and then start from there. I'll call Azpen tomorrow and ask them about a stock fw, but I wouldn't hold my breath. Once I have a stock ROM, I'll start looking into a custom recovery. Baby steps...
---------- Post added at 01:27 PM ---------- Previous post was at 01:22 PM ----------
maksmtl said:
Ok, so if, when you boot into recovery, it still passes through the Azpen logo, then there might definitely be a problem... :-/
Click to expand...
Click to collapse
I don't quite understand what you are saying here... You have to hold [Vol-] [POWER] until the unit powers on, (forever...). Then just sit back and relax. If after 15 mins you're not on recovery, and it's boot-looping, it might need a STOCK ROM re-flash.
Hi mrdownboy,
what I meant is that, I thought that, as with e.g. a Nexus device, when you boot into recovery it directly goes there, without going through the google logo screen first as it would in a normal boot. So I thought/was hoping, that on the Azpen it would do the same thing, not going through the logo screen when booting into recovery. That's why I thought that I didn't have the right key combination, because it would always boot into the azpen logo screen, where it then gets stuck. From what you said, I understood that the azpen still goes through the logo screen first, before going into the recovery menu, or did I misunderstand you here? When I press and hold [Vol-] + [POWER], the device boots directly into the azpen logo screen after 8 seconds or so, after that nothing happens anymore. I also tried to keep holding the buttons after the logo appears, but that doesn't seem to change anything neither, unless you really have to do that for an insanely long time...?
mrdownboy said:
I don't quite understand what you are saying here... You have to hold [Vol-] [POWER] until the unit powers on, (forever...). Then just sit back and relax. If after 15 mins you're not on recovery, and it's boot-looping, it might need a STOCK ROM re-flash.
Click to expand...
Click to collapse
Did you get into recovery?
mrdownboy said:
Did you get into recovery?
Click to expand...
Click to collapse
Nope... But again, just to be sure, since I'm still a bit confused here: when you go into recovery it DOES go through the Azpen logo screen first, right?
I wrote to Azpen as well about a firmware for the A729, since they have firmwares for other models, but I didn't get a response yet. But then again, if if I had a firmware, I'm not even sure if I could flash it with PhoenixUSBPro tool, if the device can't go into recovery, I doubt it can go into download mode... Btw, be careful in your development if you don't want the same thing happening to you when booting into the bootloader... It would be definitely cool to have a custom recovery and eventually cutom ROMS however!
If I can't recover my device I don't even know if I'll try going through a RMA though, since it might be too expensive sending the tablet in, considering its initial cost...
maksmtl said:
Nope... But again, just to be sure, since I'm still a bit confused here: when you go into recovery it DOES go through the Azpen logo screen first, right?
I wrote to Azpen as well about a firmware for the A729, since they have firmwares for other models, but I didn't get a response yet. But then again, if if I had a firmware, I'm not even sure if I could flash it with PhoenixUSBPro tool, if the device can't go into recovery, I doubt it can go into download mode... Btw, be careful in your development if you don't want the same thing happening to you when booting into the bootloader... It would be definitely cool to have a custom recovery and eventually cutom ROMS however!
If I can't recover my device I don't even know if I'll try going through a RMA though, since it might be too expensive sending the tablet in, considering its initial cost...
Click to expand...
Click to collapse
If you call them right now, you'll be surprised how good they are at personal customer service. They WILL offer options, but they don't have the firmware available for public release yet. Is your model the A729BT or the A729 Non-BT? I really want to do a ROM dump, but it's proven way more difficult than I initially thought. If there is a way to dump a ROM w/o rooting it would be excellent.
Also, I don't think they have a bootloader installed.
mrdownboy said:
The [Vol- ] [POWER] combo works, but you have to hold them until the unit powers on, (like forever). If it won't go past the Azpen LOGO, I would recommend contacting your local supplier.
Click to expand...
Click to collapse
That's what they show on their website, but it has not worked for me at all. I've tried repeatedly with vol+ & power, vol- & power, vol+ & vol- & power... nothing has worked, it always boots fully up.
Is yours the A729 with bluetooth from TigerDirect? (their website lists that only the TigerDirect version has Bluetooth)
Were you actually able to get into the stock recovery menu?
---------- Post added at 09:26 PM ---------- Previous post was at 08:42 PM ----------
mrdownboy said:
If you call them right now, you'll be surprised how good they are at personal customer service. They WILL offer options, but they don't have the firmware available for public release yet. Is your model the A729BT or the A729 Non-BT? I really want to do a ROM dump, but it's proven way more difficult than I initially thought. If there is a way to dump a ROM w/o rooting it would be excellent.
Also, I don't think they have a bootloader installed.
Click to expand...
Click to collapse
I called them and I definitely did not find them customer-friendly.
I politely pointed out that the Users menu was missing and as I understand it, it's only an entry in a config file to enable it and asked if it would be possible to get a patch as I bought this for my son and didn't want to have to root it and the guy on the phone cut me off mid-sentence and scolded me for even mentioning rooting the device and told me it'd void my warranty. I asked about the firmware image and he was very dismissive about it. I asked if I could submit a bug report about the fact that a valuable feature of JB 4.2+ was missing (and the fact that this was a tablet that appeared to have a phone build of Android, more below). I'm not even sure how to describe his response "you want to submit a BUG REPORT?!"... yes, I do. He gruffly agreed to take down my request and proceeded to ask me for full contact info (full name, address, email, phone number, etc.). When I asked for the case number, he was confused... they apparently have no bug or complaint tracking system whatsoever. He explained to me that there was no way the developers were going to provide a patch, that Android is open source and it's up to the developers to decide how to configure the builds, etc. After some back and forth, I finally asked him how big the company was. He was obviously taken aback, so I explained that he seemed to know an awful lot about what the developers would be willing to do... he took this as a compliment and explained that I had "called corporate" (I called the support number on their website).
This screams "tiny operation" to me... either this guy was one of the developers (answering the customer support line), one of the main people in the company, or they're simply an importer and order the devices in bulk and resell them with nothing more than a custom logo.
Alibaba lists this unit for "US $1 - 45"... minimum qty 100 units.
More on the build: This device appears to have a default config for a phone, as not only is the Users menu missing, but it has a "Mobile network settings" menu which is entirely non-applicable to a device like this (menu items include "Data roaming", "Preferred network type" (2G/3G), "Network operators", etc.).
I sure hope I caught him on a bad day, and others have better luck.
Oh - and the reason I was reluctant to root it right away was I'm a bit gunshy and wanted to make sure I could return it if I needed to. I recently had a horrid experience with a d2 tablet that bricked itself (black-screen before splash-screen) after a few hours of use on Christmas morning (nearly every review on newegg for the device, all posted after I bought it, had the exact same problem). I'm lucky I was able to send that one back for a refund. Thankfully, this one appears to be a *lot* more reliable a unit (my son has played many, many hours of games on it for the past month).
I talked to the Azpen support, and they told me to push the volume button in the middle (I guess that comes down to the same as pressing vol- and vol+) and the power button. In my case that didn't work, but my tablet seems to be definitely bricked... I have the BT model from TigerDirect.
glabifrons said:
That's what they show on their website, but it has not worked for me at all. I've tried repeatedly with vol+ & power, vol- & power, vol+ & vol- & power... nothing has worked, it always boots fully up.
Is yours the A729 with bluetooth from TigerDirect? (their website lists that only the TigerDirect version has Bluetooth)
Were you actually able to get into the stock recovery menu?
Click to expand...
Click to collapse
maksmtl said:
I talked to the Azpen support, and they told me to push the volume button in the middle (I guess that comes down to the same as pressing vol- and vol+) and the power button. In my case that didn't work, but my tablet seems to be definitely bricked... I have the BT model from TigerDirect.
Click to expand...
Click to collapse
I just tried it again by pressing in the middle (in case there was a 3rd switch) and could feel both the up and down button click, and it booted all the way up (the logo came and went 3 times as it was booting up). I held all three (incl power) buttons down until it had the full Android display up (with the lock slider).
So... sounds like the guy was wrong - even on a fully functional unit, that won't bring up the menu.
It does have a recessed reset button (you can only hit it with a paper-clip or similar). I've seen some devices where you have to hold that down for ridiculous periods of time. I'm surprised the guy didn't mention that.
maksmtl said:
Hi mrdownboy,
what I meant is that, I thought that, as with e.g. a Nexus device, when you boot into recovery it directly goes there, without going through the google logo screen first as it would in a normal boot. So I thought/was hoping, that on the Azpen it would do the same thing, not going through the logo screen when booting into recovery. That's why I thought that I didn't have the right key combination, because it would always boot into the azpen logo screen, where it then gets stuck. From what you said, I understood that the azpen still goes through the logo screen first, before going into the recovery menu, or did I misunderstand you here? When I press and hold [Vol-] + [POWER], the device boots directly into the azpen logo screen after 8 seconds or so, after that nothing happens anymore. I also tried to keep holding the buttons after the logo appears, but that doesn't seem to change anything neither, unless you really have to do that for an insanely long time...?
Click to expand...
Click to collapse
Please don't panic. I've found myself in the same situation with my A729 where key press sequences and back panel reset were to no avail. As a matter of fact, just last night I found myself where you are now. After booting into the bootloader through ADB, my Azpen had that same zomie stare that your's is experiencing.
Here's what I did. I turned it over screen down and walked away. Simply let the battery deplete over night. When you attempt to turn it on tomorrow it will complain of insufficient power. Plug it into your charger for about a half-hour, press and hold down the Volume "UP" button and then press the power button (You've heard this drill before, but THIS time you've given the instrument time to "forget" the last instruction given to it.) Let me know if this time (finally) your Azpen A729 boots into the recovery screen.
Most importantly, don't panic. Let the battery deplete firstly and then attempt the recovery mode.
- PoFolk
Hi PoFolk,
that sounds very promising! My Azpen is draining its battery right now. I actually had a suspicion that the tablet wasn't completely shut off, since every time I plugged in the charger, it would boot into the Azpen screen right away... But I didn't think about letting the battery die to give it a fresh start. Crossing fingers right now...
Oh, and I'm not panicking actually, I was almost expecting some problems with such a cheap tablet. I would probably be panicking more if this was my Nexus 7, which I just gave a new youth through F2FS.
Anyway, I'll let you know how it went tomorrow, thanks! Btw, are you sure about Volume "UP"? That would be new.
PoFolk said:
Please don't panic. I've found myself in the same situation with my A729 where key press sequences and back panel reset were to no avail. As a matter of fact, just last night I found myself where you are now. After booting into the bootloader through ADB, my Azpen had that same zomie stare that your's is experiencing.
Here's what I did. I turned it over screen down and walked away. Simply let the battery deplete over night. When you attempt to turn it on tomorrow it will complain of insufficient power. Plug it into your charger for about a half-hour, press and hold down the Volume "UP" button and then press the power button (You've heard this drill before, but THIS time you've given the instrument time to "forget" the last instruction given to it.) Let me know if this time (finally) your Azpen A729 boots into the recovery screen.
Most importantly, don't panic. Let the battery deplete firstly and then attempt the recovery mode.
- PoFolk
Click to expand...
Click to collapse
Works for me:
1) Depress "UP" volume button throughout this procedure.
2) Depress power button and release when Azpen bootloader logo appears.
3) Sing or hum a tune whilst the Azpen logo stares at you, all whilst you're depressing the volume "UP" button. (yes, it seems like an eternity)
4) Android system recovery screen pops up.
5) Don't try anything fancy just yet. Select "reboot system now".
6) Light up a cigar or draw a beer. Your Azpen should be restored.
alright guys, so here's the story. just yesterday i bought a brand new lg v10, got it home and the first thing i did was root the device and used ADB to load TWRP following the instructions here on SDA to a T for the ROOT/RECOVERY setup. and it worked. all was fine and dandy, the first time i booted into TWRP via ADB after root i got in, flashed a debloated ROM + xposed and again, everything went fine.. loaded into the OS of the new ROM, went through setup, turned on USB debugging, clicked always allow this computer, installed xposed app yadayadayada. I then, using ADB again, loaded into TWRP. i created a backup there just in case something went wrong with the changes i was about to make and once the backup was complete i loaded back in to the OS. at this point i thought i had done everything right and was confident that if i made system changes that didn't work out i could just flash the phone with TWRP from the backup i made. right? WRONG! ...apparently... so anyways, i made my first change, which was to use a NONROOT app called texdroider or whatever to change my DPI (as i have done with a couple phones previously without much issue) but i didn't take into account that stupid second screen... making the DPI changes system wide, as i'm sure those of you that know this phone are aware, causes the systemUI to crash with an error.. making the OS unusable.. so i tried to load into TWRP by holding the volume down and power button.. but instead it just booted me to the factory recovery.. not TWRP... the phone is unusable within the OS, i can't get the phone to connect to adb to boot into twrp as i had previously, i can't seem to get the phone into download mode, and i can't boot to TWRP and the OS is junk at this point.. but it DOES say on the "LG" screen that the bootloader is unlocked so i'm really hoping i'm not completely out of luck.. but i am not sure what to do at this point. does anyone here know of anything i can try to get into a custom recovery at this point? if i could get into TWRP my SD card in the phone has a backup, the original image, not to mention i could pull the SD card and add anything i need via my pc and then boot back to twrp etc etc and i would have no issue fixing the phone... i really don't understand what i did wrong or why i can't boot to my custom recovery but i'm at a loss.. i'm just looking for a way to force the phone into a custom recovery... or restore the original factory image.. if you have any advice at all i would really appreciate it.
Thanks for reading
**UPDATE** this may or may not make things much easier... but I got download mode working!! so at least there's that, still no custom recovery and i'm currently looking for a KDZ or TOT file to flash via lg flash tool... hopefully that makes things easier..
When you say you got to the factory recovery, what was that, an Android on its side or something asking you to factory reset your device? If it was the factory reset screen, if you select yes and then yes, it will take you to TWRP if you have it installed. If you don't it will factory reset your device.
ngoblirsch said:
**UPDATE** this may or may not make things much easier... but I got download mode working!! so at least there's that, still no custom recovery and i'm currently looking for a KDZ or TOT file to flash via lg flash tool... hopefully that makes things easier..
Click to expand...
Click to collapse
To boot into recovery from power off, you hold volume down & power. When you see the LG logo release and press power while continuing to hold volume down. Then as said above, it come up as a factory reset, select yes each time, and it should boot into twrp, providing you installed it correctly.
Sent from my LG-H901 using Tapatalk
YrrchSebor said:
When you say you got to the factory recovery, what was that, an Android on its side or something asking you to factory reset your device? If it was the factory reset screen, if you select yes and then yes, it will take you to TWRP if you have it installed. If you don't it will factory reset your device.
Click to expand...
Click to collapse
it was a screen asking me to do a factory reset, i click yes, it asks to confirm, i click yes again and then it "successfully" factory resets my phone... it shows the android factory reset symbol that its resetting, then says that its "optimizing apps" and goes through that whole process.. but when it finally loads the "welcome" screen (so i know for a fact that some sort reset has taken place) i get the same "systemui has crashed" error and the OS is unusable and won't connect to my computer.. idk why i can't access TWRP.. i booted to it 3 times before this happened, though never by the hardware buttons on the phone.. everytime i booted to TWRP i had used ADB to boot to TWRP.. what makes me the most sad is that i have a nandroid backup on my SD card... but i can't flash it without recovery.. which i can't install on the phone without getting into the OS..
is there any way to install TWRP or even boot to a temporary TWRP so that i can do so? if i can flash my nandroid i'm saved.. if i can get into a custom recovery i'm saved.. if i can find a .kdz file to flash, i'm saved... if i can get my phone to be recognized by my computer/adb i'm saved.... there simply has to be a way to unbrick this phone...
ZDeuce2 said:
To boot into recovery from power off, you hold volume down & power. When you see the LG logo release and press power while continuing to hold volume down. Then as said above, it come up as a factory reset, select yes each time, and it should boot into twrp, providing you installed it correctly.
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
well i seem to have somehow NOT installed TWRP correctly because it just proceeds to factory reset my phone.. which for some odd reason doesn't reset the DPI... leaving me stranded... is there any way to get ADB to see my device in its present state? my computer makes the device recognition noise when i enter download mode and i can see it in device manager but not my computer or ADB
I've had this phone just over 2 months but I'm not positive, is download mode the same as the bootloader on this device? If so, fastboot commands should work, and you can flash TWRP again, or do 'fastboot boot TWRP_filename' and it will boot TWRP temporarily.
Oh, and the factory reset just wipes your data, but otherwise doesn't restore your system to factory state. That's why your dpi change remained.
YrrchSebor said:
I've had this phone just over 2 months but I'm not positive, is download mode the same as the bootloader on this device? If so, fastboot commands should work, and you can flash TWRP again, or do 'fastboot boot TWRP_filename' and it will boot TWRP temporarily.
Oh, and the factory reset just wipes your data, but otherwise doesn't restore your system to factory state. That's why your dpi change remained.
Click to expand...
Click to collapse
dude.. then what good is a factory reset?!? like seriously... and yeah, i tried that but i can't get adb to connect in download mode.. the device doesn't show up when I type "adb devices" like it did when i first rooted it. ... and i thought i followed the instructions exactly as it was laid out from this link.
http://forum.xda-developers.com/tmobile-lg-v10/general/guide-how-to-root-lg-v10-easy-t3274699
i think somewhere in there i must have missed something and ended up only booting into twrp temporarily.. which is certainly possible since i never boot to twrp during that initial process from the hardware keys or soft keys.. always through adb.. the phone was already plugged in.. typing the command was a couple keys away..
is there anyway to get TWRP on to the phone now? or am i screwed :'(
Well, it is a factory restore for the average user, because the average person isn't modifying their system. But no, I'm sure you're not screwed. If you're in the bootloader you can't use adb, you're already past that step, so you can skip to the fastboot part. What happens when you type fastboot devices? If the phone shows up then you can either fastboot flash or boot TWRP..
YrrchSebor said:
Well, it is a factory restore for the average user, because the average person isn't modifying their system. But no, I'm sure you're not screwed. If you're in the bootloader you can't use adb, you're already past that step, so you can skip to the fastboot part. What happens when you type fastboot devices? If the phone shows up then you can either fastboot flash or boot TWRP..
Click to expand...
Click to collapse
from what screen should i be attempting this? hold volume up with phone off and plug in to computer to enter download mode? should i try it at the factory reset screen (volume down plus power)? those are the only two screens i seem to have access to.. in download mode my pc/adb just doesn't recognize the phone.. it doesn't show up as a proper device like it did before this whole thing and in that factory reset mode i get nothing.. the download mode seems like its built for LG and runs from different drivers because in device manager it shows up with an error code that it couldn't start the device (this was not the case when i was using adb to unlock the bootloader and then using the bootloader to boot to TWRP..) what am i missing?
and hey, thank you so very much for taking time out of your day to help me. I really do appreciate it.
ngoblirsch said:
from what screen should i be attempting this? hold volume up with phone off and plug in to computer to enter download mode? should i try it at the factory reset screen (volume down plus power)? those are the only two screens i seem to have access to.. in download mode my pc/adb just doesn't recognize the phone.. it doesn't show up as a proper device like it did before this whole thing and in that factory reset mode i get nothing.. the download mode seems like its built for LG and runs from different drivers because in device manager it shows up with an error code that it couldn't start the device (this was not the case when i was using adb to unlock the bootloader and then using the bootloader to boot to TWRP..) what am i missing?
and hey, thank you so very much for taking time out of your day to help me. I really do appreciate it.
Click to expand...
Click to collapse
No problem buddy, and sorry for the confusion. You want to be on the bootloader screen, so here is what you can do: turn the phone off(or remove the battery if you have to, and put it back in), plug the usb cable into the computer only(not phone), hold volume down on phone, plug the usb cable into the phone. That should get you into the bootloader, and then you should be able to fastboot flash or fastboot boot TWRP.
Waiting for a resolution to this thread!
I'm pulling for you from the cheering section. (otherwise known as afraid to do it myself section!)
I'm pretty sure others have come through this exact situation unharmed (I've pretty much read every thread here.) so it's only a matter of time before you get this figured out.
Here's hoping it's sooner than later.
Sorry I can't offer more besides encouragement!
Sent from my pretty nifty brand new LG V10
ngoblirsch said:
from what screen should i be attempting this? hold volume up with phone off and plug in to computer to enter download mode? should i try it at the factory reset screen (volume down plus power)? those are the only two screens i seem to have access to.. in download mode my pc/adb just doesn't recognize the phone.. it doesn't show up as a proper device like it did before this whole thing and in that factory reset mode i get nothing.. the download mode seems like its built for LG and runs from different drivers because in device manager it shows up with an error code that it couldn't start the device (this was not the case when i was using adb to unlock the bootloader and then using the bootloader to boot to TWRP..) what am i missing?
and hey, thank you so very much for taking time out of your day to help me. I really do appreciate it.
Click to expand...
Click to collapse
Hold volume down and plug the cable in, already have completed in terminal.....
Sent from my LG-H901 using Tapatalk
YrrchSebor said:
No problem buddy, and sorry for the confusion. You want to be on the bootloader screen, so here is what you can do: turn the phone off(or remove the battery if you have to, and put it back in), plug the usb cable into the computer only(not phone), hold volume down on phone, plug the usb cable into the phone. That should get you into the bootloader, and then you should be able to fastboot flash or fastboot boot TWRP.
Click to expand...
Click to collapse
planetbeen said:
Waiting for a resolution to this thread!
I'm pulling for you from the cheering section. (otherwise known as afraid to do it myself section!)
I'm pretty sure others have come through this exact situation unharmed (I've pretty much read every thread here.) so it's only a matter of time before you get this figured out.
Here's hoping it's sooner than later.
Sorry I can't offer more besides encouragement!
Sent from my pretty nifty brand new LG V10
Click to expand...
Click to collapse
ZDeuce2 said:
Hold volume down and plug the cable in, already have completed in terminal.....
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
@ngoblirsch Along with the information provided in these suggestions and what you have said, you need to reinstall your LG/fastboot drivers on your PC while in fastboot mode
YrrchSebor said:
No problem buddy, and sorry for the confusion. You want to be on the bootloader screen, so here is what you can do: turn the phone off(or remove the battery if you have to, and put it back in), plug the usb cable into the computer only(not phone), hold volume down on phone, plug the usb cable into the phone. That should get you into the bootloader, and then you should be able to fastboot flash or fastboot boot TWRP.
Click to expand...
Click to collapse
OH DEAR GOD THANK YOU!!!!
I spent all damn day yesterday trying to figure out how to get to the bootloader on this phone.. everything i read online said to hold volume down PLUS power while plugging it in and it was NOT working lmao. dude, thank you so much. after i read that comment here it took me about 30 seconds to connect to adb and boot to TWRP. This thread can be listed as RESOLVED!
Thanks again!! can't wait to start tweaking this awesome phone!
planetbeen said:
Waiting for a resolution to this thread!
I'm pulling for you from the cheering section. (otherwise known as afraid to do it myself section!)
I'm pretty sure others have come through this exact situation unharmed (I've pretty much read every thread here.) so it's only a matter of time before you get this figured out.
Here's hoping it's sooner than later.
Sorry I can't offer more besides encouragement!
Sent from my pretty nifty brand new LG V10
Click to expand...
Click to collapse
Well I appreciate the encouragement, it sure seems to have helped! Issue has been resolved. ended up that i just didn't know the hardware key combination to get to the bootloader/fastboot mode without being already connected to adb. nothing that i could find online said to hold volume down while plugging it in to a computer. as soon as i was able to do so i connected to adb and it was a breeze from there; I am now back with an OS AND a customer recovery properly installed on the device!! I will be hanging around these forums for as long as i have this phone so i'm sure i'll bump into you guys! absolutely love the community here on XDA, you guys are freaking awesome!!
ngoblirsch said:
OH DEAR GOD THANK YOU!!!!
I spent all damn day yesterday trying to figure out how to get to the bootloader on this phone.. everything i read online said to hold volume down PLUS power while plugging it in and it was NOT working lmao. dude, thank you so much. after i read that comment here it took me about 30 seconds to connect to adb and boot to TWRP. This thread can be listed as RESOLVED!
Thanks again!! can't wait to start tweaking this awesome phone!
Click to expand...
Click to collapse
Glad you got it fixed, and welcome to the V10 device and forums!