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.
Related
Just received a replacement Vibrant and can not boot into recovery through the power/volume up/down method, has something changed?
To get into recovery mode you need to hold Volume Down and Power Button.
I have booted into recovery many times with my original Vibrant, my replacement will not boot.
Um, the OP explicitly said that they can't get into recovery with volup+voldn+power, on a replacement phone. Replacement=more likely they know how to do it that I do, but I just received a new Vibrant from T-Mo-USA today and I cannot get it into recovery either.
VolUp+VolDn held, power until 'vibrant samsung' then release power is supposed to be recovery, but not working for me. Just VolDn or just VolUp and power only boots the phone as well. Waiting with power held until screen goes black again then 'vibrant samsung' returns is also ineffective. I can get to download mode with vol buts while plugging USB, and I've double-checked that both vol buts are working. It /is/ possible that a change took place and recovery is no longer accessible through that key combo...
Shiny new handset, never yet had a SIM inserted. (Trying to get clockwork recovery running to do nandroid backup before setting up first time) (adb gives me a permission error, going to research that now)
j
Quick Boot in the market.
I am NOT a fan of the new q&a section. I liked going to one place.
s15274n said:
I am NOT a fan of the new q&a section. I liked going to one place.
Click to expand...
Click to collapse
Agreed. Wait, is this s15274n. I love Q&A.
haha guess you saw you were in the sticky now
newkirk said:
Um, the OP explicitly said that they can't get into recovery with volup+voldn+power, on a replacement phone. Replacement=more likely they know how to do it that I do, but I just received a new Vibrant from T-Mo-USA today and I cannot get it into recovery either.
VolUp+VolDn held, power until 'vibrant samsung' then release power is supposed to be recovery, but not working for me. Just VolDn or just VolUp and power only boots the phone as well. Waiting with power held until screen goes black again then 'vibrant samsung' returns is also ineffective. I can get to download mode with vol buts while plugging USB, and I've double-checked that both vol buts are working. It /is/ possible that a change took place and recovery is no longer accessible through that key combo...
Shiny new handset, never yet had a SIM inserted. (Trying to get clockwork recovery running to do nandroid backup before setting up first time) (adb gives me a permission error, going to research that now)
j
Click to expand...
Click to collapse
Let us know if you find a resolution, thanks!
s15274n said:
Quick Boot in the market.
I am NOT a fan of the new q&a section. I liked going to one place.
Click to expand...
Click to collapse
Quick Boot specifically states that you must ALREADY have root status for it to work.
So we need Root for Quick Boot to get into Recovery Mode, but we need to first get into Recovery Mode to get Root...
Ring around the rosy...
Anybody else have any ideas?
^ he didn't say he didn't have root already. I also posted an alternate method to root above without stock recovery.
Have either of you found a way to recovery with key combos yet. I too can not get recovery with vol buttons. Only thru terminal, adb, rom manager, etc. i'd really like to know if anyones found a solution to this??? I'd like to be able to boot recovery manually in case I cant boot into home screen for some reason.
Someone mentioned getting it to work while having it plugged into the charger.
Frankly, the only way I was able to get into Recovery Mode was through the ADB method.
Sent from my SGH-T959 using XDA App
I called T-Mobile regarding this and they agree it should work with hardware buttons and are sending me a replacement.
Same issue. Got the phone on Aug 23 and the only way I can go to recovery is via ADB and ClockWorkMod
Hmmm, I have the same issue. The funny thing is that I can get into recovery on my girl's phone just fine. And I can't on mine. They only way I could get into recovery was by using the 1-click root. Now, I can use ROM Manager to get into recovery while "on-the-go". At first, I was honestly afraid that maybe my phone came without the recovery installed!
I know it gets frustrating listening to the stupid T-Mobile jingle taunting you every time it fails.
I guess it's not a big enough deal to me to send it back now that I have a couple of options, but it seems like it's a more common issue than I thought. Only way to get Samsung to do something is to keep sending them back . . .
Its important to be able to get recovery with the buttons tho. What if your flashing roms or anythimg for that matter and the phone wont boot regularly. Then you cant get into recovery to restore. Called tmobile and Im sending mine back tomorrow for replacement, unless somebody knows another way to get into recovery if you end up in a boot loop???
My friend just got his Vibrant, I went to root it for him and wont go into recovery. Mine works fine,I can get into recovery fine on mine everytime. I told him to return it and swap it out. Getting into recovery is very important if you flash a rom and you run into booting issues.
roguespy0 said:
My friend just got his Vibrant, I went to root it for him and wont go into recovery. Mine works fine,I can get into recovery fine on mine everytime. I told him to return it and swap it out. Getting into recovery is very important if you flash a rom and you run into booting issues.
Click to expand...
Click to collapse
I really suspect what we're seeing isn't a defect per se, but the result of a suit at t-mo being told that people are using recovery mode for rooting their phones and restoring things like wifi tethering, who responded "then disable recovery mode dammit"...
If you return a Vibrant that won't go into recovery from buttons and actually get a new-in-the-box vibrant in its place, I suspect there's a very high probability that the replacement is the same, and if you get a replacement that WILL enter recovery from buttons I suspect it's likely to be an open box or what-have-you. For the latter, as more Vibrants are returned for not entering recovery, you're more and more likely to end up with a 'like-new' replacement that won't enter recovery either.
Long-term I suspect the solution is going to have to come from us, not t-mobile.
j
I can not boot into recovery this is also a replacement phone. I installed vibrant7 didn't care for it so did a rom manager recovery back to stock and my phone is stuck on the vibrant start screen. Can anyone help me fix my brick?
it doesn't work on my Vibrant,tried Volume Up/Power,Volume Down/Power, no luck....
Hello,
about 2 hours ago I decided that I would unlock my device (before that I read maximum informations that I could). Unlocking went fine and I also installed TWRP 2.1.3 (through ViperMod). So far so good.
Then I made backup in TWRP in case something goes wrong. I was going to try AOKP v40 so I downloaded it via goo manager and then I flashed it in TWRP Install option (and also installed gapps) and wiped cache. Device rebooted and I was stuck at AOKP boot animation for about 15 minutes when I decided to recover back. So I rebooted, restored and rebooted.
Now I'm stuck at first boot logo (eee pad). When I try to do VolDown+Power to get into recovery it doesn't ask for VolUp, but goes straight to selection of Wipe or USB. When I select fastboot or wait 10 secs device frozes. (I haven't tried wipe, just in case it would be needed to unbrick).
I read thread about unbricking (http://forum.xda-developers.com/showthread.php?t=1514088) and to me it seems like option 3, but I don't see recovery option.
In device manager I have 'ASUS Fastboot Interface'.
Here's video how it looks like: http://www.youtube.com/watch?v=7BGd1PIVbn8
Please please could anyone help me?
Btw: Is there any chance to shut down? Holding power button just resets, so does pinhole... :/
qery said:
Hello,
about 2 hours ago I decided that I would unlock my device (before that I read maximum informations that I could). Unlocking went fine and I also installed TWRP 2.1.3 (through ViperMod). So far so good.
Then I made backup in TWRP in case something goes wrong. I was going to try AOKP v40 so I downloaded it via goo manager and then I flashed it in TWRP Install option (and also installed gapps) and wiped cache. Device rebooted and I was stuck at AOKP boot animation for about 15 minutes when I decided to recover back. So I rebooted, restored and rebooted.
Now I'm stuck at first boot logo (eee pad). When I try to do VolUp+Power to get into recovery it doesn't ask for VolUp, but goes straight to selection of Wipe or USB. When I select fastboot or wait 10 secs device frozes. (I haven't tried wipe, just in case it would be needed to unbrick).
I read thread about unbricking (http://forum.xda-developers.com/showthread.php?t=1514088) and to me it seems like option 3, but I don't see recovery option.
In device manager I have 'ASUS Fastboot Interface'.
Here's video how it looks like: http://www.youtube.com/watch?v=7BGd1PIVbn8
Please please could anyone help me?
Btw: Is there any chance to shut down? Holding power button just resets, so does pinhole... :/
Click to expand...
Click to collapse
Shouldn't it be volume and power down to get to the option to press volume up for recovery?
Are you familiar with fastboot flashing recoveries? Either way that will be helpful info for us to have.
Most important thing, this is no big deal at all, it's really a minor issue. Don't let yourself get stressed out over it, the community will make sure you're good to go.
CharliesTheMan said:
Shouldn't it be volume and power down to get to the option to press volume up for recovery?
Click to expand...
Click to collapse
Yes sure my bad, it was typo (I was kinda sleepy and tired when I was writing)
CharliesTheMan said:
Are you familiar with fastboot flashing recoveries? Either way that will be helpful info for us to have.
Click to expand...
Click to collapse
Nope, this is my first time flashing.
You say you dont see the VOL_UP message. From the video it looks like it is there. You just did not press it within 5 seconds.
Once it comes up, let go of the buttons ;p
leppie said:
You say you dont see the VOL_UP message. From the video it looks like it is there. You just did not press it within 5 seconds.
Once it comes up, let go of the buttons ;p
Click to expand...
Click to collapse
nope it's not there. I was holding voldown from the start and as soon as it should say 'press volup for recovery' (time 0:04) it jumps (skips 5 seconds of waiting) directly to wipe/fastboot options (wipe is one that is selected on video)
Ok so I managed to fix my problem thanks to hanzo001's thread (http://forum.xda-developers.com/showthread.php?t=1662158). Someone should add this instructions to the [HOW-TO] Unbrick your Transformer Prime (or not) thread.
qery said:
Ok so I managed to fix my problem thanks to hanzo001's thread (http://forum.xda-developers.com/showthread.php?t=1662158). Someone should add this instructions to the [HOW-TO] Unbrick your Transformer Prime (or not) thread.
Click to expand...
Click to collapse
glad it's fixed, im sure hanzo001 will appriciate a simple thanks on his thread too..and let others know it worked for you
Hi guys, thanks for taking the time to read this. My brother's tablet is 'softbricked'. It hasn't been modified in any way, no unlocking, no custom ROMs etc. All he did was try to install the Jellybean update from Asus' site. I'm not quite sure what went wrong but the tablet won't get past the the Asus splash screen.
I've been googling around for solutions, of which I have found http://forum.xda-developers.com/showthread.php?t=1916952, going to the bootloader and factory resetting, or wiping the SD card and replacing the update. The problem is every attempt to get to the bootloader just leaves me at the Asus splash screen. Even holding volume down + hitting the reset slot button doesn't work. All of these fixes require access to the bootloader.
It was the correct SKU, nothing has been done to the tablet, so this shouldn't be TOO difficult to reverse right? I also assume that this isn't the only person this has happened to, but my google searches haven't proved fruitful.
extraneousleopards said:
Hi guys, thanks for taking the time to read this. My brother's tablet is 'softbricked'. It hasn't been modified in any way, no unlocking, no custom ROMs etc. All he did was try to install the Jellybean update from Asus' site. I'm not quite sure what went wrong but the tablet won't get past the the Asus splash screen.
I've been googling around for solutions, of which I have found http://forum.xda-developers.com/showthread.php?t=1916952, going to the bootloader and factory resetting, or wiping the SD card and replacing the update. The problem is every attempt to get to the bootloader just leaves me at the Asus splash screen. Even holding volume down + hitting the reset slot button doesn't work. All of these fixes require access to the bootloader.
It was the correct SKU, nothing has been done to the tablet, so this shouldn't be TOO difficult to reverse right? I also assume that this isn't the only person this has happened to, but my google searches haven't proved fruitful.
Click to expand...
Click to collapse
Try powering off the device by holding down the power button for 10 seconds. Now hold volume down and the power button both together and keep holding them for about 5 - 10 seconds. Do you get icons appear on the screen ?
flumpster said:
Try powering off the device by holding down the power button for 10 seconds. Now hold volume down and the power button both together and keep holding them for about 5 - 10 seconds. Do you get icons appear on the screen ?
Click to expand...
Click to collapse
Nope still goes straight to the Asus splash screen. Samsung phones have ODIN that basically is a godmode tool. Does Asus have anything?
He's accepted that all data will be lost. We just want it to work
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Hi everyone,
While trying to return to stock using the LG Flash Tool .tot method, my phone got disconnected from my PC during the firmware update. Now, I just get the LG screen in a boot loop without the ability to get into download mode or recovery. I've looked around for a good half hour and couldn't find a thread describing a similar problem, so if it's a noob question, my bad. I have insurance for physical damage, so it might accidentally get run over at some point today. Any last ditch efforts available before it happens?
Appreciate any and all input!
jhajj33 said:
Hi everyone,
While trying to return to stock using the LG Flash Tool .tot method, my phone got disconnected from my PC during the firmware update. Now, I just get the LG screen in a boot loop without the ability to get into download mode or recovery. I've looked around for a good half hour and couldn't find a thread describing a similar problem, so if it's a noob question, my bad. I have insurance for physical damage, so it might accidentally get run over at some point today. Any last ditch efforts available before it happens?
Appreciate any and all input!
Click to expand...
Click to collapse
If you pull the battery, then put it back in, it should be off.
Then press and hold vol dn while plugging it in it should go into DL mode. Flashtool should work then.
It might be vol up. I can't remember off hand.
It's Vol Up (and hold it) + plug into the computer to get to Download Mode, but if the OP was already in a flash process that got interrupted it's entirely possible the phone won't go back into Download Mode again. It should be able to get back into that mode given how it works but, it's all relative given how far along the process was the first time when it was interrupted.
Pull the battery for 30 seconds, re-insert it, then hold Vol Up + plug it into the computer and see what happens. If it will absolutely not jump back into Download Mode then yep, it's pretty much hosed and would need LG to do something to resolve it.
Good luck...
jhajj33 said:
I have insurance for physical damage, so it might accidentally get run over at some point today.
Click to expand...
Click to collapse
Thanks for that good laugh, almost spit out my coffee with that one.
engine95 said:
If you pull the battery, then put it back in, it should be off.
Then press and hold vol dn while plugging it in it should go into DL mode. Flashtool should work then.
It might be vol up. I can't remember off hand.
Click to expand...
Click to collapse
That was the first thing I tried doing, it completely ignores my button presses no matter what I do. Held uo/down while plugging it in, , tried power+up, power+down to get into recovery mode, nothing. Just keeps showing the splash screen over and over again. This isn't my first, or even 10th rodeo as far as restoring phones back to stock, but I've never seen something like this before. Starting to think it's a lost cause.
When it is at the LG screen try running:
fastboot reboot-bootloader hopfuly that will boot you into download mode. The next thing you can try is to download the twrp image and then run this command: fastboot flash boot <namehere>. I know its not the same device but I did the same thing ony kindle fire and that boot command worked. It just booted me into twrp and I flashed a new rom.
Noticed quite a few threads re this, have had the prob myself.
Found a simple fix, while trying different things...
Hold ALL buttons down at once (vol dn + vol up + pwr button). Keep them held down for about a min or two. Phone will respond and you'll be able to shut it off. It takes a while to respond.
Cheers
Thank you!
I've added this to the US998 Pie KDZ thread. That KDZ is very wonky. It's the only Pie people have problems flashing. Probably because LG has not yet released Open Market US998 and the one we are using is technically for U.S. Cellular US998.
I had no trouble flashing it myself -- on my backup V30+(former LS998) going straight from Nougat (never updated, it was my backup phone) to Pie through Dev Patched LGUP Refurbish mode. But lots of other people seem to have problems.
On my daily phone, I'm still on rooted stock Oreo with Magisk and Xposed mods.
AsItLies said:
Noticed quite a few threads re this, have had the prob myself.
Found a simple fix, while trying different things...
Hold ALL buttons down at once (vol dn + vol up + pwr button). Keep them held down for about a min or two. Phone will respond and you'll be able to shut it off. It takes a while to respond.
Cheers
Click to expand...
Click to collapse
Hi, @AsItLies, I have tried but my phone still keeps bootloop, so could you please describe it more detailed? Can you enter fastboot or rec then? If possible, please come to see this: Help! bootloop per 5 sec, cannot enter rec, download or fastboot
zacox123 said:
Hi, @AsItLies, I have tried but my phone still keeps bootloop, so could you please describe it more detailed? Can you enter fastboot or rec then? If possible, please come to see this: Help! bootloop per 5 sec, cannot enter rec, download or fastboot
Click to expand...
Click to collapse
I think it's pretty clear, what I did and it worked in my situation(s):
There are 3 buttons right? Vol up, Vol dwn, and pwr.
Press all 3, at the same time, keep them pressed until the phone responds. It can take quite a while.
The last time I used this was after flashing LOS17, but then flashed a 19.x version of Magisk... (that's the wrong version of Magisk for Q Roms btw), resulting in phone stuck on boot logo, wouldn't budge.
I honestly have never tested exactly 'how long' it takes to respond, just that it does eventually respond and are then able to get to recovery etc. I can say time wise, if you hold them down and no response after a few minutes, then it's probably not going to work in your situation.
good luck
AsItLies said:
I think it's pretty clear, what I did and it worked in my situation(s):
There are 3 buttons right? Vol up, Vol dwn, and pwr.
Press all 3, at the same time, keep them pressed until the phone responds. It can take quite a while.
The last time I used this was after flashing LOS17, but then flashed a 19.x version of Magisk... (that's the wrong version of Magisk for Q Roms btw), resulting in phone stuck on boot logo, wouldn't budge.
I honestly have never tested exactly 'how long' it takes to respond, just that it does eventually respond and are then able to get to recovery etc. I can say time wise, if you hold them down and no response after a few minutes, then it's probably not going to work in your situation.
good luck
Click to expand...
Click to collapse
Oh, I'm just a little confused if you are talking about powering off/shutting down the phone entirely or instead changing the status of logo sticking and then shutting off with extra operation. My phone was suffering automatic reboot per 5 second, so I cannot recognize any other response than that. Thanks for your patience, but I just want to know something more to see if this method works when the phone is almost bricked. It seems you could enter rec or at least download mode, so maybe you had performed force reboot.
Hope further confirmation.
zacox123 said:
Oh, I'm just a little confused if you are talking about powering off/shutting down the phone entirely or instead changing the status of logo sticking and then shutting off with extra operation. My phone was suffering automatic reboot per 5 second, so I cannot recognize any other response than that. Thanks for your patience, but I just want to know something more to see if this method works when the phone is almost bricked. It seems you could enter rec or at least download mode, so maybe you had performed force reboot.
Hope further confirmation.
Click to expand...
Click to collapse
Hmmm I think you may be over thinking this a bit. All that happens (for me) is the phone responds (it gets out of the loop). Then, do whatever you want (shut down, recovery, etc etc).
I wouldn't suggest trying to reboot system again, as you already know that won't work...
All I can say is, if you tried the above and held the buttons, and nothing happened, then I don't know what else you can do. Sorry. Hopefully you can find a way.
Just in case someone is having problems entering download mode while in this bootloop, I'll explain how I applied AsltLies method:
First I held all buttons at the same time, no matter how many times the phone restarted, I still held them
After a while, a white screen with the MEID or IMEI info showed up, this is when the phone stopped bootlooping and I released the buttons.
Then, I CONNECTED the phone to the pc, after that I held VOL UP+POWER BUTTON, this would make the screen go black eventually, and when that happened, I inmediately released the power button but not the VOL UP button, and the phone entered into fully working download mode.
I hope this helps someone.
Dr_Roo said:
Just in case someone is having problems entering download mode while in this bootloop, I'll explain how I applied AsltLies method:
First I held all buttons at the same time, no matter how many times the phone restarted, I still held them
After a while, a white screen with the MEID or IMEI info showed up, this is when the phone stopped bootlooping and I released the buttons.
Then, I CONNECTED the phone to the pc, after that I held VOL UP+POWER BUTTON, this would make the screen go black eventually, and when that happened, I inmediately released the power button but not the VOL UP button, and the phone entered into fully working download mode.
I hope this helps someone.
Click to expand...
Click to collapse
Thanks. Added your notes to the Recovery Post in US998 Pie KDZ thread.
https://forum.xda-developers.com/showpost.php?p=81728547&postcount=641
dr_roo said:
just in case someone is having problems entering download mode while in this bootloop, i'll explain how i applied asltlies method:
First i held all buttons at the same time, no matter how many times the phone restarted, i still held them
after a while, a white screen with the meid or imei info showed up, this is when the phone stopped bootlooping and i released the buttons.
Then, i connected the phone to the pc, after that i held vol up+power button, this would make the screen go black eventually, and when that happened, i inmediately released the power button but not the vol up button, and the phone entered into fully working download mode.
I hope this helps someone.
Click to expand...
Click to collapse
thank you so much omg lifesafer