I flashed HSPL3 on my HD2..and flashed a radio on there also..then i did all of the necessary steps (ie. downloading Android rom, copy to root of SD, click CLRCAD, then HARET.exe..after that it goes to a black screen with about 5 lines of VERY SMALL text..and then it goes to HTC logo screen & gets stuck there forever until i do a battery pull..i've installed various radios on my HD2 for experimentation, still does the same thing..help please??
FYI, Please post questions in the Q&A Forum as per mskip's Sticky http://forum.xda-developers.com/showthread.php?t=713942
Most Android builds do take 15-20mins to boot up the first time (they have to create the data.img file). Your best bet is to check there isn't a data.img file in the Android folder or on the root of your SD card, if there is, delete it. Then try booting again. Once it gets to the HTC logo screen, leave it and go get a a good book or something . My HD2 took about 20mins to boot up the first time, after that, it takes about 20-30 seconds.
Alternativly you can download precreated "data.img"s but you need to make sure they're OK to use with your chosen Android build.
If that doesn't work, check here for more info.
Dave
P.S. Mods, please can someone move this to the appropriate forum. Ta.
verify your android path in startup.txt you'll find the mistake
I'm sorry, i realized that after i posted the thread up, i apologize. I did everything stated in the thread, and still having the same problem. I switched SD cards, formatted them, same problem. I've tried over 5 android builds, no change.
First boot can take a wail, and did you placed also the img file (the 512mb or the 1Gb) on your SD?
When you boot up WinMo, don't enter the PinCode.
Then you should be able to start Android.
The first startup it is hard to stay tuned
Try to start, put your Phone on the desk and get back after 30 Minutes, then everything should be fine...
maybe try a different radio?
caseyman4285 said:
maybe try a different radio?
Click to expand...
Click to collapse
He is has troubles with android first boot up. Radio has nothing to do with it.
P.S Try this rom , it's goddamn amazing in terms of stability and preformance:
http://miuiandroid.com/community/threads/archived-miui-versions-hd2-gb.16553/
I have yet to find an answer to this while searching for the past day, so I'm going to ask about it here.
My LG Optimus V's (just got it a few days ago as a birthday present) screen seems to be permanently blank... In case someone asks... yes, it is activated.
What Happened:
I rooted the phone using Gingerbreak 1.2, installed rom manager/clockwork recovery mod, then attempted to backup my phone in case something went wrong. However, when I started the backup, I noticed that the screen was completely blank. I was kinda freaking out, so I just took a shower while it did it's thing. When I came back, it was done creating the backup and it showed up in Rom Manager. After toying with some of the things I can do with it rooted (I only rooted it to see how much of a difference it would make without changing the kernel), I decided to recover that backup. When my phone restarted to recover the backup, the screen was blank once again. After waiting for over an hour, I concluded that it must have finished (since my HTC Hero would finish restoring and never reboot until I tell it to) and took out the battery. Afterwards, it would show the LG splash screen... then the blank screen.
What I Did:
I was thinking about the android screencast java application a few hours after my problem first developed. I plugged my phone into my computer, got adb working, and android screencast showed me that my phone was actually getting stuck at the clockwork recovery mod screen. I tried many things... I installed a CM7 rom, flashed 3 different recoveries, flashed an overclocked stock rom, etc. Eventually, I flashed the stock rom (no changes whatsoever) and stock recovery. Now I can hear my phone, but cannot see it. However, I should note that while using CM7 the same thing happened. The only difference being that I could use android screencast to see the screen (the phone was actually working) with CM7. Now with the stock rom, adb is disabled and I cannot see the screen or do... anything.
What I Think I Should Do:
I'm thinking about calling Virgin Mobile and telling them that my screen is defected. If they see the issue they'll probably think that it's a hardware issue (for all I know, it could be) and they'll probably give me a replacement. However, if anyone as had the same problem and fixed it, I would love to know.
I would love you hear your opinion on this and, if possible, a fix. Thanks in advance!
(JIC, if I posed in the wrong section, I'm sorry...)
you poor souls reporting the symptoms of getting the newer screen hardware from the optimus s in your v's don't number in the double digits yet, but it's getting closer.
I posted a fix on AndroidCentral, see it:
here
good luck! the fix has worked for everyone I pointed to it so far.
btw, the screencast idea is excellent!
crud. stock recovery, you may be SOL.
you'll probably have to boot into custom recovery to use screencast or adb now.
use the unplug phone -> pull&replace battery -> hold home+volume down -> keep holding, press and hold power until lg screen goes blank to enter recovery. maybe adb will work in stock recovery, I dunno.
Thank you very much for the reply!
Yeah, you're right, I'm probably SOL... I still have one option though! Theoretically, I should be able to turn on ADB without being able to see my screen. I know how to access the settings without seeing it, but navigating myself to the "Applications", "Development", "USB Debugging" may be a little hard. I will attempt to do so. I will report my progress in a bit.
However, if you (or somebody else) could provide screenshots of a step-by-step process to turn on USB Debugging in the stock rom (since it's kinda hard to do remember where everything is and screenshots of different phones is kinda different) then I would appreciate it VERY much!
I shall update this in an hour or so.
UPDATE (9/2/11 - 9 PM):
I'm going to take a break for now. Good thing I give everyone my Google Voice number, I doubt anyone will notice a change. I'm going to flash a stock rom onto my HTC Hero so I can figure out where things are on the LG Optimus V (Same screen size) in an hour or so. I'll update my progress in like 2 hours.
UPDATE (9/3/11 - 8:10 AM):
I have been unable to turn on USB Debugging and it seems to be because I don't know where the confirmation after turning it on is located. However, I should note that when I boot into (I think) recovery, "adb devices" states that the device is attached but offline. If there is a way to make it "online" from stock recovery then I would love to know. For now, I will try everything I can.
UPDATE (9/3/11 - 8:22 AM):
Ok. I plugged my phone into the back of my computer and now when I do "adb devices" it detects the device in recovery mode. However, when I try "adb shell" it says "- exec '/system/bin/sh' failed: No such file or directory <2> -". I'll try some more stuff, but does anyone have any idea of what I can do? Android Screencast doesn't work either, so that's not an option.
UPDATE (9/3/11 - 9:42 AM):
Crap... now it's indefinatly booting into recovery... I had something like this happen before, I'll report my status in an hour or so...
UPDATE (9/3/11 - 12:36 PM):
My friend finally got my phone booting out of recovery again! Now all I have to do is get "USB Debugging" on and it SHOULD work!
I <think> there's a key combination to power up into the bootloader. if you can find it with searching here and android central.
I haven't been able to track that down today. If you can get into the bootloader, you can fix it. Search for asadullah's fastboot root instructions here if you find a way to get into the blue screen (the bootloader, which fastboot talks to.)
otherwise, I'll be done taking the kids to the (ugh) pool in a few hours and I'll search more.
try pulling your battery for a few minutes and see if the reboot cyle stops that way, at least it might get into recovery or the rom.
glad you got back into recovery again, not too sure how to help at this stage though, since I can't find a way to get into the bootloader with a power-on key combo. just emergency mode (useless to the V since the firmware from LG is missing a file) and safe mode. boo.
there is a youtube video for enabling usb debugging on the v, maybe it'll help you find the right spots to press.
http://www.youtube.com/watch?v=nHal0hPNS6s
edit: you can also try to reboot into the bootloader with adb, even though it's missing the shell... it's worth a try, and if it works you can flash xionia recovery with fastboot and things would be a lot easier from that point.
Code:
adb reboot bootloader
if that works but you need more help, a battery pull is the only way to power off with the bootloader except "fastboot reboot" will try to boot your rom.
Awesome, thanks for the replies! I'm going to try your suggestions now. I'll let you know how things work out in a few hours. I would have replied earlier, but to my satisfaction there was a surprise party planned for me, lol. I will defiantly try these out now.
Once again, thank you very much. I honestly did not expect a reply for something that happens to such few people.
bigsupersquid said:
I <think> there's a key combination to power up into the bootloader. if you can find it with searching here and android central.
I haven't been able to track that down today. If you can get into the bootloader, you can fix it. Search for asadullah's fastboot root instructions here if you find a way to get into the blue screen (the bootloader, which fastboot talks to.)
otherwise, I'll be done taking the kids to the (ugh) pool in a few hours and I'll search more.
try pulling your battery for a few minutes and see if the reboot cyle stops that way, at least it might get into recovery or the rom.
Click to expand...
Click to collapse
I'm honestly not sure what my friend did, lol. She was just messing with it while it was, apparently, in recovery and it ended up rebooting and loading the rom. I, honestly, don't want to risk getting stuck in recovery anymore since taking out the battery for an hour didn't do anything... If I'm unable to get adb on using what I know from that video then I'll try booting into the bootloader. Like I said before, I'll report my status in a few hours. I really appreciate your help up to now!
EXTREMELY HAPPY UPDATE!!! (9/4/11 - 1:22 AM)
I was able to turn on ADB! I used what I learned from that video and how turning on ADB works on my HTC Hero to get it working and it's FINALLY ON! Now I can attempt to flash the recovery, kernel, and everything else in order to get it working! Thank you VERY much! I will let you know how everything turn out
Another Wonderful Update! (9/4/11 - 2:03 AM)
I have flashed the recovery.img (the Xionia CWMA one) and can see my screen in recovery! I haven't seen anything on my screen besides the LG splash screen so I'm overwhelmed with joy! I'm flashing a new ROM and the other stuff now!
Final Update! (9/4/11 - 2:09 AM)
2:05 AM - I see the rom's boot screen!
2:06 AM - I see the CM7 Mod boot screen!
2:08 AM - I see the UI on my screen and everything seems to be working! Thank you VERY much!
Quick question though... If I want to install a new ROM, do I need to flash the xionia anykernel one directly afterwards?
ah, excellent! glad it's working now.
you're the most persistent (and maybe technically apt) person I've helped with this so far.
I still think that using screencast was the best new idea I've seen yet.
yes, you'll need to flash the xionia kernel after flashing any rom or rom update.
roms come with their own kernel in the boot.img, and none of them currently out for the v have the video drivers from the newer sprint kernels.
right now, xionia kernel is the only thing that works.
and, you'll need to flash the key swap after changing roms, as well, but at least forgetting to do that won't take out your display.
now that you've got xionia recovery on your phone, it should be a lot easier next time.
Thank you for both the help and the compliment!
I don't like giving up when it's something I know I can do. I figured that if I was able to mount my SD card without being able to see the screen, I should be able to turn on USB Debugging as well. About the Android Screencast... I didn't actually think about it until it until I plugged in my phone while the screen was blank, ran "adb devices", and saw that my device was detected within recovery. I figured that I might as well give it a shot... and it worked.
Alright, that's what I figured. Hopefully someone realizes what's happening with refurbished Optimus V smartphones and ports the newer sprint kernels to the Optimus V. I feel like I got ripped-off though... I bought my phone "new" and got a refurbished one. I can't really do anything though, we're not technically supposed to be rooting our Virgin Mobile phones anyways, lol. I'll be sure to do that everytime now though. For now, I think I'm good with the Bumblebee rom.
Once again, thank you VERY much for your help! I know I would not have been able to fix my phone without your help.
EDIT:
Oh yeah, btw, if the Optimus V ever gets stuck in stock recovery, press the "back" button then "home" button to boot into the rom. Not sure why it works (I was never able to see the screen), but it worked.
There is a key combo!
First time caller long time listener... I bricked my own Optmus V with a bogus ROM. To boot into recovery without adb press (Home)+(Volume Down)+(Power) Now rocking CM7!
Hi,
I'm a little nooby at all this, trying to learn better.
I started with a fully working, Galaxy S2, which I rooted ages ago. I did a factory reset on it, then the phone would not boot - it goot stuck at the Samsung Logo. (Probably due to the battery running out during the new user set up).
So I installed slimbean ROM 4.3 build 1 (put it on the SD card, installed by holding volume up+ power+ menu button).
After that, it still won't boot. This time, it got stuck on the SlimBean logo, instead a Samsung Logo.
So I installed Siyah-v3.3.2-CWM kernel. Now, after the first boot screen, it goes blank (no ROM boot screen).
Umm. Maybe I'm making more of a mess. But the most important thing is that I understand how this all works. Please don't send me to a guide, I've already read lots (they make a lot of assumtions about knowledge level, and are often really wordy which muddles things up in my mind.
I probably installed the wrong kernel for the version of slimrom I have....
Help ! ?
Please someone reply
Absolutely do not bump threads after an hour. This isn't your personal tech support hotline.
Good job keeping the forum in order, boss. Must be lonely at the top.
Of anybody could help me that would be absolutely fantastic. I was half asleep in a thread on trying to get a custom recovery for my Verizon Ellipsis 7 (quanta qmv7a) and I found a recovery.img and it was noted that it was a test. I'm just curious of anyone knows how to fix my brick because the recovery won't load and I'm now stuck in a boot loop, the "welcome" screen comes up and goes away and comes up again repeatedly. Is there a way I can adb flash this tablets stock recovery? I still have the original recovery.img I just need to figure out how to flash it when its boot looped due to a wrong recovery.img flash. Help is greatest appriciated! Thank you!
bump
-The complete lack of responses could mean that we're screwed... (or we've asked a dumb question).Today, I too was a little too eager with the Enter button without triple-checking if the version of the recovery would be compatible with my current ROM -- it obviously wasn't -- Ellipsis_boot_patched_140902-025705.img over the top of 4.4.2 -- should have done more homework
Google's bots have hit this thread -- I hope we can help others who find this thread in our predicament and give solutions -- not just be a dead-end as it is now.
It's only been 4 hours since I've been working on it... it had an unlocked bootloader so there is hope.
I can tell what _doesn't_ work straight away:
1. Pulling the battery cable -- the back cover comes off easy -- insert a credit card starting at the SIM/SD slots and work your way around the cover and then gently pull the battery harness from the battery terminal assembly -- At least I don't have to see WELCOME taunting me by flashing every few minutes.
2. Combinations of button pressing -- I tried all the dead-Andi tricks...
3. Adb and RSD-lite aren't being acknowledged.
For just a few seconds before re-cycling -- Windows DOES recognize the phone (via USB) -- enough time to (indirectly) put a batch file in the bootloader?
-- or the answer could come from a combination of all the above.
After months of tweaking, I had just gotten the 16G SD card to be stable and (fairly) transparent as the main-APP drive -- Thanks mostly in part to Vicky's recent overhauling of her app: Apps2D -- I don't want to abandon all those hours without giving it one last concerted effort.
I am also willing to give playing with the physical ROM a try (-- I pray it's not embedded in the Soc). I remembered all the fun I had with JTAGs all those years ago when I was messing with DSS systems.
The tablet was a grateful gift to me but would not be one I would have ever purchased... The Ellipsis 7 was one of the first "cheap" tablets on the market... it shows. I would never use it professionally -- but wouldn't hesitate to use it as a backup or taken out camping...
I'm giving this a 30% chance of success.... well, i'm in the market for a new tablet... maybe one of those new Win8/Marshmallow dual-booters made-in-China?
You say you have the original recovery.img could you send me that please?
ThatGuyWhoLovesRoot said:
Of anybody could help me that would be absolutely fantastic. I was half asleep in a thread on trying to get a custom recovery for my Verizon Ellipsis 7 (quanta qmv7a) and I found a recovery.img and it was noted that it was a test. I'm just curious of anyone knows how to fix my brick because the recovery won't load and I'm now stuck in a boot loop, the "welcome" screen comes up and goes away and comes up again repeatedly. Is there a way I can adb flash this tablets stock recovery? I still have the original recovery.img I just need to figure out how to flash it when its boot looped due to a wrong recovery.img flash. Help is greatest appriciated! Thank you!
Click to expand...
Click to collapse
I am still trying to work on one, could you send me the original recovery.img if you still have it? Thanks
Bondaddict said:
I am still trying to work on one, could you send me the original recovery.img if you still have it? Thanks
Click to expand...
Click to collapse
i actually threw it away, but i have another that isnt bricked ill pull the recovery from that one if you would like. it wont be for a couple weeks as my daughter was just born and i havent had time to do anything on my pc. just let me know ill get back when i can
That would be awesome
ThatGuyWhoLovesRoot said:
i actually threw it away, but i have another that isnt bricked ill pull the recovery from that one if you would like. it wont be for a couple weeks as my daughter was just born and i havent had time to do anything on my pc. just let me know ill get back when i can
Click to expand...
Click to collapse
Ya if you could do that that would be amazing! Could you also include how you suspended the pre boot?
Bondaddict said:
Ya if you could do that that would be amazing! Could you also include how you suspended the pre boot?
Click to expand...
Click to collapse
Is there a chance that you have the entire ROM? I tried to root and ended up bricking the device
Okay, so I apologize in advance if this cannot be posted here. My reason for doing so, is because I need some help with a Zenwatch 2 by Asus and the thread pertaining to this device seems to be a ghosttown. So if you need, please move this where it should go, but not without offering a word of advice or two first
So obviously I have a zenwatch 2, and I was tinkering with it earlier, and somehow got it stuck in CVC fastboot or something like that. I was able to get TWRP on it (Thank god, im much more optomistic now) but I am still having trouble getting an OS back on it. At first I wasnt even able to read the internal storage from my computer, or even begin to sideload anything, but I went into the TWRP settings and repaired the partitions to EXT4 or something of that sort. Now I am able to sideload, as well as access the storage from my PC, but I have had no success in flashing a working OS.
Im usually pretty familiar with android, rooting and unlocking, but these watches seem to be a bit different.
If anyone has anything that would help, please feel free!
The exact model of watch I have is WREN W1502Q .... I think.
Thanks in advance!
UPDATE:
I got it to boot!! Now I am stuck with a hang on that screen with all the swirly dots (the four separate animations that is right before boot)
So we're making progress, but I dont know if it is just gonna take a long time to boot, or if it is hanging! Hopefully we can get over this last hump. Thanks!
UPDATE 2:
Back up and running!
Praise the Lord!