Database Info

HOX Stuck at boot "One" screen, Haven't Flashed Lately

I was on the phone earlier for a fair bit, when I hung up I noticed the battery at 4%. Got home little bit later and when I checked my phone again it was off, I hit the power button so it began to power on, and I them plugged it into AC charger right away while booting up. A couple of minutes later and I noticed it was still on the "One" boot screen (on a sense ROM at the moment, ViperXL 2.1.1). Tried holding power to reboot and it did the same thing.
Figured I leave it plugged in for a little bit, maybe battery was just really low. After about 30 minutes or so it was plugged in, still on the same screen (couldn't power it off it would just reboot). Tried to reboot again, and got stuck on the same screen. This time however I noticed the phone was quite hot, though it seems to be cooling down slightly since I've unplugged it, but not 100% sure.
What could be the issue/any ideas? I haven't flashed anything in over a week, last being ViperXL 2.1.1 and BeastMode Kernel 3.0. First time dealing with potential boot issues as I am always very careful when flashing. Any help is appreciated!

Try reading threads before you post. You may have read a thread that said don't post questions in General. There is a Q&A forum for this.
Anyways, try erasing the caches and rebooting.

Myrder said:
Try reading threads before you post. You may have read a thread that said don't post questions in General. There is a Q&A forum for this.
Anyways, try erasing the caches and rebooting.
Click to expand...
Click to collapse
Yeah I was thinking this might not be the right place but wasn't totally sure, I apologize.
I was having trouble getting it to boot into the bootloader as well, forgot to mention that originally, holding volume down and power wasn't working. However after not sure how many attempts I did get it somehow. Perhaps I was holding the buttons down incorrectly, I think I let go of power early the time it worked? Not sure. After a straight system reboot from recovery did not work, I tried wiping cache's as you said and it booted fine! Much thanks.
Again apologies from rushing to make a thread, just got kind of frustrated with not being able to boot into even the bootloader or just power it down for awhile, for seemingly no reason. Someone can delete this thread if they'd like. Thank you though!

maybe your phone doesnt like the overclock. not all phones can handle high overclocks and some cant work with ANY overclock. i would try letting the phone charge and flashing the stock boot.img

Songlambr37 said:
Who else in the world still use the manly Dell Venue?
who can help us upgrade it to 4.0?
Click to expand...
Click to collapse
I think you're lost

Songlambr37 said:
Who else in the world still use the manly Dell Venue?
who can help us upgrade it to 4.0?
Click to expand...
Click to collapse
Wtf,.. This is second thread I've seen that in,..
WR
Sent by WR's One XL

Chrysis said:
I was having trouble getting it to boot into the bootloader as well, forgot to mention that originally, holding volume down and power wasn't working. However after not sure how many attempts I did get it somehow. Perhaps I was holding the buttons down incorrectly, I think I let go of power early the time it worked? Not sure.
Click to expand...
Click to collapse
Almost always a matter of pilot error (as long as you have a charge light coming on, it should go to hboot no problem). Correct way is to hold vol down rocker, don't let it go, then press the power button for 3 seconds or so. Release the power button (but keep holding vol down). Don't let go of vol down until the hboot screen comes up.
If the screen is on, you can do the same as above, with the only change being: holding the power button down for 5 seconds or so until the capacitive buttons flash, then release the power button.

WarRaven said:
Wtf,.. This is second thread I've seen that in,..
WR
Sent by WR's One XL
Click to expand...
Click to collapse
I'm on it.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"If you choose not to decide, you still have made a choice"
Sent from my Galaxy Note (i717), using XDA Premium.

Chrysis said:
Yeah I was thinking this might not be the right place but wasn't totally sure, I apologize.
I was having trouble getting it to boot into the bootloader as well, forgot to mention that originally, holding volume down and power wasn't working. However after not sure how many attempts I did get it somehow. Perhaps I was holding the buttons down incorrectly, I think I let go of power early the time it worked? Not sure.
Click to expand...
Click to collapse
Future reference to boot into.downloader...
-lock screen like you would be putting phone in pocket
-hold power + vol down unroll screen goes off
-let go of POWER BUTTON ONLY right after screen goes off and continue holding vol down.
You'll boot into downloader just fine.
Sent from my HTC One XL cellular device over clocked to 1.9Ghz

Sorry to resurrect a slightly old thread, but was there any solution to this? My phone just died last night and won't start back up. It just stays stuck on the loading screen. I went into recovery and deleted the caches just in case, but it hasn't fixed anything. I have a nandroid backup from a weeks ago that I can just if I have to, but I'd prefer not to since I'd lose the app data.
Any ideas?

Valohtar said:
Sorry to resurrect a slightly old thread, but was there any solution to this? My phone just died last night and won't start back up. It just stays stuck on the loading screen. I went into recovery and deleted the caches just in case, but it hasn't fixed anything. I have a nandroid backup from a weeks ago that I can just if I have to, but I'd prefer not to since I'd lose the app data.
Any ideas?
Click to expand...
Click to collapse
Reading the thread says wiping caches worked for the OP.
Sent from my One X using xda app-developers app

Ah right missed that. Didn't work for me unfortunately. Would re-flashing the ROM without wiping work?

Valohtar said:
Ah right missed that. Didn't work for me unfortunately. Would re-flashing the ROM without wiping work?
Click to expand...
Click to collapse
That was going to be my next suggestion. Its your best bet if you don't want to lose all of your app data.
Sent from my One X using xda app-developers app

[Q] G2X Stuck at Boot Screen - Brick?

Hello all,
I have an LG G2X P999. I got this phone two days ago, and tried to root it. After watching some videos, I realized the phone was already rooted- Because it had the superuser icon in the menu, as I saw in videos.
Moving along, I downloaded ROM Manager. I flashed CWM and then tried to install the latest stable version of Cyanogen Mod.
After restarting the phone from CWM, it gets stuck at the Second LG Bootscreen.
When I hold the power button + Vol Dwn button, I see the android and the arrow. I realize now, that means CWM isnt really installed.
However, that doesnt help with the issue at hand- I cannot bypass the Second boot screen.
No matter how long I leave it, or any of the methods I try.
I have downloaded the NvFlash package, which contains the program + the apx drivers. However, I am unable to install the drivers, as my laptop wont detect the phone.
I have removed the battery, held both volume buttons and plugged in the USB. Nothing happens.
The computer does not detect the device. Different ports, Different cables, even tried a different laptop. Nothing.
I have done as much research as I can, and all the tutorials have me confident that I know what to do AFTER the device is detected.
But I cannot find any resource, that advises me what to do if the device doesn't even get detected :crying::crying::crying:
Ive read link after link, that has led me back to links that I have already checked.
The only thing I have not done, is ask for help. This is why I am now here.
Please, may I have some assistance. I am at my wits end.

:crying:
:crying::crying::crying:
:crying:

So the only way the phone detects the device, is by putting the battery in - Then holding the power + volume down buttons till it reaches the second LG logo.
Which is where the device freezes. It doesnt pass this boot screen.
It detects it as Unknown Device. Not APX
Also, the phone can charge with the USB. The laptop doesnt detect it while charging.

So I got the phone to go into APX mode.
I did this by having the battery IN the phone.
Plugging the phone IN the laptop.
Holding the power + VOL down buttons. It reset the phone, then went to the second LG boot screen.
I then held the VOL buttons + Power button. Then the laptop detected the device, and APX showed up in Device Manager.
__________
After doing that, I opened NVFlash, and clicked "Flash CWM 5.0.2.0 Internal and Exernal ....."
The process ws successful and then the phone went to "S/W Upgrade Please wait."

I do not know WHO said the battery NEEDS to be out or WHY they said that, but those instructions are NOT ACCURATE.
The battery does not NEED to be taken out to do this process, I have now gotten my G2x into CWM using NVFLASH, WITH the battery IN the phone.
This little detail has caused heartache to many G2X owners, including myself.
I have the remedy, my friends!! Leave the battery IN the phone!! It WILL WORK!!
Someone please make this a sticky, OR add these instructions to the original NVFlash Method.
The public needs to know.
I hope my journey will help many others, peace and love to you all.

You are incorrect. But whatever...
Sent from my glorified LG pet rock™

justjackyl said:
You are incorrect. But whatever...
Sent from my glorified LG pet rock™
Click to expand...
Click to collapse
My friend, what I have posted are the steps I took to get my g2x working; That is what worked for me, fact.
I am now running weapon g2x 3.0_R1; flawlessly, might I add. Praise to the developers.
I'm sorry you felt your disapproving opinion was necessary.

itskingruss said:
I do not know WHO said the battery NEEDS to be out or WHY they said that, but those instructions are NOT ACCURATE.
Click to expand...
Click to collapse
This is what you said and is incorrect.
This has worked for me and countless others and a statement like this can throw off a new user. Occasionally, directions will need to be altered and most often when they do it is due to operator error resulting in straying away from said original directions.
You should not state that these directions are "not accurate" , but rather should state something along the lines of "I ran into problems and got it to work trying this way, just an idea if someone else gets stuck."
But the original directions work correctly.
But it's cool man, I've only been modding this phone for a year now. Your solid 3 days of ownership have far surpassed that.
Sent from my glorified LG pet rock™

I got stuck in that same boot loop following some video on YouTube just this past weekend! ha-ha...
Glad I'm not the only one
Nvflash worked flawless with for me with battery out
Sent from my LG-P999 using xda app-developers app

JA1983 said:
I got stuck in that same boot loop following some video on YouTube just this past weekend! ha-ha...
Glad I'm not the only one
Nvflash worked flawless with for me with battery out
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
Sent from my glorified LG pet rock™

justjackyl said:
This is what you said and is incorrect.
This has worked for me and countless others and a statement like this can throw off a new user. Occasionally, directions will need to be altered and most often when they do it is due to operator error resulting in straying away from said original directions.
You should not state that these directions are "not accurate" , but rather should state something along the lines of "I ran into problems and got it to work trying this way, just an idea if someone else gets stuck."
But the original directions work correctly.
But it's cool man, I've only been modding this phone for a year now. Your solid 3 days of ownership have far surpassed that.
Sent from my glorified LG pet rock™
Click to expand...
Click to collapse
Lmao when I read this I died, I tried the OP's way to make sure I had something to back me up incase I ever felt like hating on him and strangely for me both the OP's and the original way works for my G2X

Lol who cares, happy you got your phone working op
Sent from my LG-P999 using xda app-developers app

[Q] Can't get into recover, phone won't boot, CM9

Hi there,
I have a Rogers Galaxy SGH-i727R. About three weeks ago, the phone started re-starting on it's own. I though maybe it was a sticky power key and had that replaced. The problem persisted. I then noticed that it was primarily upon receiving text messages that the phone would reboot. So it seemed it was a software issue. I am running the stable build of CM9.
Yesterday the phone rebooted and never got off the angry alien screen. I pulled the battery, charged it etc and still could not get it to fully boot up. I left it for over an hour. I finally decided to call it quits and re-flash the phone. Problem is, it will not boot into recovery at all. When I hold down Vol + - and Power, it jsut goes into a loop of vibrating every three seconds until I let go and then it tries a normal boot again. Once, I briefly got a screen saying I was trying to install custom software and to press volume up to do so, but before I could hit volume up, the phone cycled off.
I should also mention that the four buttons on the bottom of the screen do not work. I accidentally sliced the wires on the side of the phone when opening it up. I use a software button saver widget to access their functions. I wonder if that issue is related....
Thanks for any advice. I would like to get into recovery so I can load a new ROM or a stock ROM.

You're going to get blasted for posting this here....
That being said, your power button is borked, common on these phones. Happened to mine, but I was still under warranty so it was replaced.

eagercrow said:
You're going to get blasted for posting this here....
That being said, your power button is borked, common on these phones. Happened to mine, but I was still under warranty so it was replaced.
Click to expand...
Click to collapse
He said his was replaced and the issue continued..
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

Blast away
Sorry. Where should I be posting this? I am happily corrected. I find the titles of the forums confusing, sorry.

btm fdr said:
He said his was replaced and the issue continued..
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Your point? I can't tell you how many times I've been sent "new" or "tested good" parts and they are DOA when installed. Or people who claim to have replaced or fixed a part but really didn't.
tonyrage.stc said:
Sorry. Where should I be posting this? I am happily corrected. I find the titles of the forums confusing, sorry.
Click to expand...
Click to collapse
In the Q/A section is the proper place. I had the exact same issues you are having, fortunately I had the option to trade it in for a new one. Good luck!

[Q] Keyboard dock problems

Hey guys
I pulled my TF300 out of the box, let it run through updating everything it wanted to update then after rebooting the keyboard dock refuses to work. The power is still there, showing up on the battery monitor and charging the tablet, and it's showing up as being connected, plus the USB port is fine, but there's no response from pressing any keyboard buttons or poking the mouse pad. Before the tablet updated to 4.2 (from whatever it came in the box with) it worked fine since I put in my gmail stuff with it, but now nothing.
I've tried reboots and reconnects and everything basic I can think of. Nothing wants to do anything.
There's so many threads about these problems, but no-one seems to actually have an answer for it, other than just poke and hope something works.
Anyone have an idea what I should do?

Hypothisising
Quote:
LostAlone said:
Hey guys
I pulled my TF300 out of the box, let it run through updating everything it wanted to update then after rebooting the keyboard dock refuses to work,,,
I've tried reboots and reconnects and everything basic I can think of. Nothing wants to do anything.
There's so many threads about these problems, but no-one seems to actually have an answer for it, other than just poke and hope something works.
Anyone have an idea what I should do?
Click to expand...
Click to collapse
This is just a hypothesis, but it's worth the shot.
When you updated the tablet, was the dock connected?
If not, the dock firmware might out dated for your tablets firmware version. I presume that's why on the update notice it advises you to connect your dock; to keep the dock compatible to prevent other users may end up in a situation like yours. Have you tried flashing the latest official rom via fastboot with the Tablet connected? You never know, it might be the solution.
Hope this helped.:laugh:
Live long and prosper.
If I have helped you in any way, shape or form, hit the thanks button. If I have given you a link to someone on XDA that helped you, give them thanks first.

Weird I never had my dock connected when updating, never had any issues!
Sent from my TF300T using xda app-developers app

Quote:
noahvt said:
Weird I never had my dock connected when updating, never had any issues!
Sent from my TF300T using xda app-developers app
Click to expand...
Click to collapse
So did you have any success? The problem might of been caused by the upgrade of the 4.1 bootloader to the 4.2 one whilst not having your dock attached.
Live long and prosper.
If I have helped you in any way, shape or form, hit the thanks button. If I have given you a link to someone on XDA that helped you, give them thanks first.

Stuck at boot screen and can't access recovery

It's the holidays which means helping to fix others' devices.
I've got a family member's TF300T that gets to the ASUS boot screen but just spins forever. The bootloader hasn't been unlocked and I think it's on JB but I don't have any way to tell which version of the stock ROM it is. I've spent the last hour reading through posts on multiple forums but haven't found anything that works.
I've tried accessing recovery by holding vol down but no luck. It just hits that boot screen and spins. I've installed the standalone drivers as well as the ASUS Sync utility but I can't get adb to see the device. I know the keyboard dock has some problems and doesn't work 100%, but I think the USB port is okay because the owner uses a mouse on it. There's an amber light next to the charging port that is blinking. I'm not really familiar with this device so I tried connecting my Win 10 machine (a T100 coincidentally) with a regular microUSB to that and with the charging cable but neither worked.
Is there something I might be missing or anything else I should be trying with this device?

rileysmith said:
It's the holidays which means helping to fix others' devices.
I've got a family member's TF300T that gets to the ASUS boot screen but just spins forever. The bootloader hasn't been unlocked and I think it's on JB but I don't have any way to tell which version of the stock ROM it is. I've spent the last hour reading through posts on multiple forums but haven't found anything that works.
I've tried accessing recovery by holding vol down but no luck. It just hits that boot screen and spins. I've installed the standalone drivers as well as the ASUS Sync utility but I can't get adb to see the device. I know the keyboard dock has some problems and doesn't work 100%, but I think the USB port is okay because the owner uses a mouse on it. There's an amber light next to the charging port that is blinking. I'm not really familiar with this device so I tried connecting my Win 10 machine (a T100 coincidentally) with a regular microUSB to that and with the charging cable but neither worked.
Is there something I might be missing or anything else I should be trying with this device?
Click to expand...
Click to collapse
You said you held vol down. Hold vol down and power button together from off state. Maybe that's what your doing though. That should take you to boot loader.
Sent from my HTC One M8 using XDA Free mobile app

purple patch said:
You said you held vol down. Hold vol down and power button together from off state. Maybe that's what your doing though. That should take you to boot loader.
Sent from my HTC One M8 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah, sorry, that is what I meant. No luck getting into the bootloader.

rileysmith said:
Yeah, sorry, that is what I meant. No luck getting into the bootloader.
Click to expand...
Click to collapse
There's a thread about 3 down from yours, see if that helps. Appears the issue is more common than I thought. It's by mgs333
Sent from my HTC One M8 using XDA Free mobile app

purple patch said:
There's a thread about 3 down from yours, see if that helps. Appears the issue is more common than I thought. It's by mgs333
Sent from my HTC One M8 using XDA Free mobile app
Click to expand...
Click to collapse
I've read that one and a dozen others. Unfortunately unlike just about everyone else who has had it get stuck, I can't get access to anything that'll let me wipe, flash, or really do anything so I'm sort of dead in the water until I can.
I'm familiar enough with Android that I'm pretty confident in getting it working when I do, but until then I'm a bit lost.

rileysmith said:
I've read that one and a dozen others. Unfortunately unlike just about everyone else who has had it get stuck, I can't get access to anything that'll let me wipe, flash, or really do anything so I'm sort of dead in the water until I can.
I'm familiar enough with Android that I'm pretty confident in getting it working when I do, but until then I'm a bit lost.
Click to expand...
Click to collapse
I've never tried, but look up nvflash. It may help as your stock. Sorry but I'm no more help, someone else may answer, but bit slow around here these days lol.
Sent from my HTC One M8 using XDA Free mobile app

Thanks. I'll look into it some more.
I glanced over it briefly in my earlier research but it seemed like it might not work in my situation.

I got it. This thing has been used in a pretty dusty work environment and I cleaned it up. I think the volume down button was being prevented from working. After cleaning I got right into the bootloader and wiped it. After that it started right up.

rileysmith how you do it?