Related
I must admit I do it often. With so many ROMs out there is like being a kid in a candy store. my 8gb sd card is maxing out with nandroid backups! arghh!!!
You have ORD then
Deffo ORD. A hopeless case sadly, beyond saving.
You could try going into recovery to see if that helps*
*That was a test. If you reached for your phone and booted into CWM then there is NO helping you. If you took 'Recovery' to mean a support group then there may be some hope yet!
It's called ORD.
Welcome to, the dark side.
MUHAHAHAHAHAHAHAHAHA
nah this is absolutely normal ... the reason i change roms every week is the fact every single one has one or two bugs in it that make my normal lifestyle and well being completely impossible ...
Can anyone mention, which rom has the best battery life and speed ??
demetriusdev said:
Can anyone mention, which rom has the best battery life and speed ??
Click to expand...
Click to collapse
Just as a word of advice...avoid asking that. You'll most likely either get chewed out or get the same answer every time....you'll know what that answer is right away. Not trying to get on your case, just a fair warning.
-If ignorance is bliss why aren't you smiling?-
Yeah I find myself doing that. I've already done it four times today. What I don't like is all the times I have to reinstall all my apps. :/
It annoys me too the way I lose unread texts while I'm flashing a new ROM.
I also have some weird strange thing, where when I change ROM's it'll resend all the texts I've sent that day. I quite like annoying people when I do that tbh.
Skellyyy said:
What I don't like is all the times I have to reinstall all my apps. :/
Click to expand...
Click to collapse
Have you tried using titanium backup?
-If ignorance is bliss why aren't you smiling?-
twitch153 said:
Have you tried using titanium backup?
-If ignorance is bliss why aren't you smiling?-
Click to expand...
Click to collapse
I've used it before... Don't like the way you had to keep clicking install and open with every app. I use MyBackup Pro and it uses the market links to install them. Doesn't always work though.
Yes (Response to questionnaire)
my ord days are long gone =)
and I haven't looked back
It's 2am here and playing with android 2.3 sigh....
Sent from my LG-P500 using XDA Premium App
Skellyyy said:
I've used it before... Don't like the way you had to keep clicking install and open with every app. I use MyBackup Pro and it uses the market links to install them. Doesn't always work though.
Click to expand...
Click to collapse
If you get the paid version of titanium backup up you can run batch operations.
And I flash so many times a day I lose count, all ways feel like I need to be running the latest and greatest.
Sent from my awesome DZ
No cant say i do but certainly for the first 6 months or so when i joined this forum i used to be a bit of a ROM flashing addict, been using Sergio Coredroid now since January and that's the longest ive gone without flashing anything else.
i am a flashoholic...everyday i log in just to check if a new rom is out...the longest i've gone without a flash is 4 days...today is the 4th day
Only if I see improvement, I don't care about homes and colors, ill do that on my own
Sent from my X10i using XDA App
I went 2 weeks without flashing my DZ. It was on 1.72 so I had no root and no ROMs.
Now - (If there are any bloody ROM updates) I flash as they upload.
NANDroid > Flash > Play > Flash > Break > Flash > Play > Flash >Hate > NANDroid Restore.
Yes. If I won't try all of them roms, how should I know I use the best one?!
Yes def get the paid version of titanium. I used to switch like Once a week but I am loving trigger right now. Don't think im going to be switching anytime soon. Still switch kernels left and right tho lol
Trigger + Tigerblood = Winning
buh bye xda.
-deck
:O First!
Lets try this out!
Looking forward to giving pre-alpha3 a go. Played around with with version 2 for a bit and really enjoyed it. Appreciate all you work on this ROM!!
Sent from my ADR6300 using xda premium
Exciting stuff.
I'll give it a go! Thanks!
Cool
Sent from my PC36100 using xda premium
Can't wait to get my hands on this, as soon as camera is working I'll give it a shot! Great work!
Yes! I've been waiting to see if you would get am ics build up, since you have those nice pure gingerbread builds
Sent from my ADR6300 using XDA App
is this any different than R2's latest build in terms of smoothness, speed, or improvements?
when you say Cam doesnt work, does that mean at all or just some features of the Cam? This is the only thing stopping me from trying this Rom. Been dying to get my hands on an ICS port for our Inc's. Thank you so much for this, great job!
Hmmm, I flashed it, erased data and dalvik cache, nothing at the incredible screen, did it again, same thing?
Not to be rude or anything, but I haven't even been able to get passed the welcome screen due to reboots. I've had six in a row after the language screen. This has been the case with my phone on any of the current ICS roms. It will eventually get passed it, but still randomly reboot all over the place.
Agenda Calendar Widget
After installing this ROM, GAPPS, and a couple of apps I got a few soft reboots, but it now seems stable. So don't give up on this right away. Reboot and few times and it should get better. GPS, wifi, sound all seem to be working well.
It did start with language as Afrikaans, but I managed to find my way through the menus and switch to English.
I don't think any camera app will function. Something to do with the lib files needing updating. I don't think anyone has that figured out yet for ics-dinc.
Does anyone have an agenda style calendar widget that works with this or any ics-dinc ROM? Seems that smooth calendar is not ready for ics yet.
People stuck at the welcome screen probably didnt do a full wipe, including system wipe and boot. Exciting, can't wait to try.
Sent from my ADR6300 using XDA App
romsRfun said:
People stuck at the welcome screen probably didnt do a full wipe, including system wipe and boot. Exciting, can't wait to try.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Why would I or anyone not do a full wipe? I understand there are some people that are that noob, but really? I've tried ICS over ten times now and have had the same results with each iteration. I've had many reboots from just typing in my email address. This is not an issue of wiping.
Sent from my ADR6300 using XDA App
rvrugg90 said:
is this any different than R2's latest build in terms of smoothness, speed, or improvements?
Click to expand...
Click to collapse
Anyone flashed both and have any thoughts on this?
R2's ROM at least has a much more detailed changelog and list of what works/doesnt work. With nothing else to go on, I have to assume that the better-documented one is the better ROM.
I'd like to hear what people think though.
Try vrsuperwipe after wiping and before flashing
Sent from my ADR6300 using XDA App
Ics for Droid incredible is coming fast ! Huh ?
Sent from my Incredible 2 using xda premium
demarcmj said:
Anyone flashed both and have any thoughts on this?
R2's ROM at least has a much more detailed changelog and list of what works/doesnt work. With nothing else to go on, I have to assume that the better-documented one is the better ROM.
I'd like to hear what people think though.
Click to expand...
Click to collapse
I can't get the ringer or alarms to work on R2's version. They all work on Deck's.
demarcmj said:
Anyone flashed both and have any thoughts on this?
R2's ROM at least has a much more detailed changelog and list of what works/doesnt work. With nothing else to go on, I have to assume that the better-documented one is the better ROM.
I'd like to hear what people think though.
Click to expand...
Click to collapse
Both work about the same. Though I had fewer fc's using Inc decks, but that doesn't really mean anything as they are both pre-alpha.
Make sure you guys understand what you're doing with this build, as in, if it won't boot or you boot loop or get stuck, the problem is what YOU are doing, and not the rom.
First of all, if you haven't checked the Md5 sum then you're really wasting your time and shooting blind. It HAS to match EXACTLY.
Second, follow the dev's instructions exactly as they wrote them. That means wipe and format the areas listed, and install the proper files in the proper order. So if he says to install the rom first, don't reboot yet, then install gapps, then reboot, then do it in that order.
Third, pay attention to what your phone is doing during the installation, ensuring you get all the messages you're expecting.
Fourth, be PATIENT. Consider what it is your phone is doing the very first time you boot up after installation: building and loading, compiling and accessing files and db's for the FIRST time. Let your phone do it's job and give it some time before you go munching on the sammich.
And finally, be cool. Don't come in here on an Alpha pre release thread and stink up the joint. (say "*****, be cool") If you can't seem to get it to take, then try a different method. Download the rom on a computer and transfer it to your phone, see if you get a different md5. Flash the rom zip, then flash it again right away before anything else. You make it through the setup screen, reboot the mofo and let it gain some proficiency.
One more thing, all the time and effort these guys put in to get these out is free of charge. Keep that vibe going however you can.
Much love my friends
Sent from SkyNet's Matrix in a galaxy far, far away, where no one has gone before...
Downloaded decrappified 1.1. Computer has a bad usb port and i think it disconnected before it was finished downloading. At this point the phone became stuck in cwm, so I erased user data and reset settings. The phone then said i had a bad sim card, but two replacements didnt fix it. I bypassed the sim card with up, down, search, home and the decrappified seemed to have flashed, but the phone now resets itself every 30 seconds or so.
I'd like to at least get this phone back to stock so i can take it in. been using my wifes old purple curve for the last 2 months. Any help would be appreciated. Thanks.
nesta111 said:
Downloaded decrappified 1.1. Computer has a bad usb port and i think it disconnected before it was finished downloading. At this point the phone became stuck in cwm, so I erased user data and reset settings. The phone then said i had a bad sim card, but two replacements didnt fix it. I bypassed the sim card with up, down, search, home and the decrappified seemed to have flashed, but the phone now resets itself every 30 seconds or so.
I'd like to at least get this phone back to stock so i can take it in. been using my wifes old purple curve for the last 2 months. Any help would be appreciated. Thanks.
Click to expand...
Click to collapse
My wife told me if I bricked my phone, I would have to go back to using the Cricket Wireless phone we had. YUCK. "Again" she says as she is reading over my shoulder. Anyhow.... stay calm, all is fine. In the forums there is a way to fix it. The phone is unbrickable. LG thought of everything. So diagnose the issue, and look in the forums. You will probably need ADB and stock programming, you can search our forums for ADB and you should track it all down. If you run into issues you can go to IRC the channel we have there is #lgrevolution and someone might be there to help you. It took Cubed 5 minutes to fix my phone, but it took 5 hours for him to come on IRC. I will try to dig up somethings. But you will need ADB so go get that.
Yeah, that blackberry is one hell of a leap backwards, nevermind the comments i get for carrying a purple phone. Even the wife likes to poke fun.
Ive been looking through the archives some and not sure what route to go, not farmiliar with ADB but i'll start looking into that.
nesta111 said:
Yeah, that blackberry is one hell of a leap backwards, nevermind the comments i get for carrying a purple phone. Even the wife likes to poke fun.
Ive been looking through the archives some and not sure what route to go, not farmiliar with ADB but i'll start looking into that.
Click to expand...
Click to collapse
Decrappified is a Froyo Rom, the Revo is now on Gingerbread. Either restore your back up, or download and install GingerVolt Rom.
mtmichaelson said:
Decrappified is a Froyo Rom, the Revo is now on Gingerbread. Either restore your back up, or download and install GingerVolt Rom.
Click to expand...
Click to collapse
If you didn't make a back up, there is a nandroid in the the development section. When did you get your phone? How long ago did you root it? Do you have Froyo or Gingerbread? If you had Ginger, of course Mt is right, you would do the Gingervolt. But you gotta take it back to your stock to get rid of decrap. Most of your answers will be in the Development section of our forums.
I didn't make a back up, so that isn't an option. I rooted and then broke the phone 2 to 3 months ago, i am not sure if that was before gingerbread or not. I guess i'll search the development section for answers on getting back to stock.
markapowell said:
My wife told me if I bricked my phone, I would have to go back to using the Cricket Wireless phone we had. YUCK. "Again" she says as she is reading over my shoulder. Anyhow.... stay calm, all is fine. In the forums there is a way to fix it. The phone is unbrickable. LG thought of everything. So diagnose the issue, and look in the forums. You will probably need ADB and stock programming, you can search our forums for ADB and you should track it all down. If you run into issues you can go to IRC the channel we have there is #lgrevolution and someone might be there to help you. It took Cubed 5 minutes to fix my phone, but it took 5 hours for him to come on IRC. I will try to dig up somethings. But you will need ADB so go get that.
Click to expand...
Click to collapse
I disagree. I Hard Bricked my Revo. Won't get into details as it's not important and I managed to find a local seller via Craigslist for same day replacement.
What happened is a flash occurred that should've failed, but didn't. The power button would no longer function and the 'failsafe' usb, no battery recovery method would not even work either. I would get a quick response when pulling the battery with USB plugged in, but then it would fail beyond that. Have since then destroyed the board due to some very private files located on internal board that were 'in transition' and couldn't chance being recovered by other parties for security purposes. I do, however, have a nice parts phone, such as screen, body, and battery cover.
Anyhow, moral to the story.. YES, the Revo CAN BE BRICKED!
-Cybie
Cybie257 said:
Anyhow, moral to the story.. YES, the Revo CAN BE BRICKED!
-Cybie
Click to expand...
Click to collapse
Nicely done! Now help this poor guy fix his. ; )
Also, if it was closer to 3 months ago then it was going to be froyo, right? Find the v4 stock and flash that. I'd link the thread but I'm on my Revo. : /
I found a rooted stock rom posted by thecubed, currently downloading that to my sd card. Anyone see a problem using that? Also found some tot files for stock. I think i had ver 6, but my phone wont let me check. Does it make a difference which one I use if i go that route?
nesta111 said:
I found a rooted stock rom posted by thecubed, currently downloading that to my sd card. Anyone see a problem using that? Also found some tot files for stock. I think i had ver 6, but my phone wont let me check. Does it make a difference which one I use if i go that route?
Click to expand...
Click to collapse
You are nit making this easy, lol. You should have the v6 version. I would go to the tot file. Also you would have had froyo, but after a month it should have updated to ginger bread. So go get the v6, then I would check phone status and see if there is an update. majority of us got the gingerbread update, if you don't there isinfo on how to do it. If you do, there is the one click tool kit that will get your phone rocked out.
Sent from my VS910 4G using xda premium
Cybie257 said:
I disagree. I Hard Bricked my Revo. Won't get into details as it's not important and I managed to find a local seller via Craigslist for same day replacement.
What happened is a flash occurred that should've failed, but didn't. The power button would no longer function and the 'failsafe' usb, no battery recovery method would not even work either. I would get a quick response when pulling the battery with USB plugged in, but then it would fail beyond that. Have since then destroyed the board due to some very private files located on internal board that were 'in transition' and couldn't chance being recovered by other parties for security purposes. I do, however, have a nice parts phone, such as screen, body, and battery cover.
Anyhow, moral to the story.. YES, the Revo CAN BE BRICKED!
-Cybie
Click to expand...
Click to collapse
Bull****!!! I tried absolutely everything to try and brick this phone in order to get a replacement and I was able to recover every single time... what did you do.. I got to know in case this phone sucks also???
drt054 said:
Bull****!!! I tried absolutely everything to try and brick this phone in order to get a replacement and I was able to recover every single time... what did you do.. I got to know in case this phone sucks also???
Click to expand...
Click to collapse
Jeez, I know, I just took him at his word, no need to fight over it. Lol. When cubed told me it was unbrickable he said he did everything possible too, and the secret to fixing it was dependent on how the phone acted, what lights were on, what the screen did, because each one had its own fix. I had a mismatch md5 and it said in the instructions don't turn off your phone. I did and caused it to brick. But there was a section in our forum to fix that brick. And with cubes help and mt laughing at me,we got it fixed.
Sent from my VS910 4G using xda premium
This whole situation was answered by mt. Just flash a gingerbread ROM either the stock v7 or gingervolt And you're good to go.
Sent from my VS910 4G using xda premium
Beamer9408 said:
This whole situation was answered by mt. Just flash a gingerbread ROM either the stock v7 or gingervolt And you're good to go.
Sent from my VS910 4G using xda premium
Click to expand...
Click to collapse
Got it unrooted and back to stock! The phone still resets itself every minute or so. Not sure if that is because I manually forced it past the sim card setup screen. Anyway, at least I can now take it into verizon. Thanks all for the help.
Glad to hear you're making progress. You may still want to go the ADB route and put zv6 on. I understand getting the Over The Air push upgrade to zv7 will then get you the upgraded radio. I haven't heard any other method for getting the radio.
I found my own noob way to brick a Revo, not in a good way.
Sent from my VS910 4G using Tapatalk
Bait-Fish said:
Glad to hear you're making progress. You may still want to go the ADB route and put zv6 on. I understand getting the Over The Air push upgrade to zv7 will then get you the upgraded radio. I haven't heard any other method for getting the radio.
I found my own noob way to brick a Revo, not in a good way.
Sent from my VS910 4G using Tapatalk
Click to expand...
Click to collapse
That kind of makes no sense flash the v7 tot it will get you to gingerbread get rid of your reboot issue. Also I wouldn't take the phone to Verizon unless you don't have cwm recovery in your phone cause more than likely they are going to try And factory reset your phone which will then boot into cwm recovery. Either way you're going the long way about fixing that phone.
Sent from my VS910 4G using xda premium
Old posts like these (below) lead me to believe the radio is only OTA. Of course it's old info and things may have changed. I didn't follow the TOT thread/s as closely since my phone behaved and did the OTAs fine. Realized I forgot there was a radio update on zv6. That's partly why I was paying attention to mentions of radio upgrades and it was taking a while to get root for zv6.
http://forum.xda-developers.com/showpost.php?p=18947155&postcount=1111
mtmichaelson said:
The radio is not inside the boot.img. It is stored in a different partition, and lg has done a fine job of covering it up, so it is difficult to tell.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=18843721&postcount=91
mtmichaelson said:
My roms already had the update except for the updated radio and boot.img (kernel & ramdisk). I will update the boot.img in the roms, but lg has covered up the radio mount point, so the radio may have to be updated through the actual update.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=18907274&postcount=25
drt054 said:
Only other option will be to downgrade or ugrade using LGNPST. Or wait, one of the other Members is attempting to get the v7. Tot file then can just use LGNPST to upgrade.. or MTMichaelson will be posting Gingervolt some time today which will have everything except new radio.. that you need to flash through LGNPST or the OTA update.. the radio that is along with the firmware.
Click to expand...
Click to collapse
Edit: Realize re-reading I need to clarify. My POV was just regarding his method and maintaining all features, not the reboot issue per se.
Right the tot is everything...sorry wasn't trying to be a **** might be how it came out though.
Sent from my VS910 4G using xda premium
No problem
Sent from my VS910 4G using Tapatalk
mtmichaelson said:
Decrappified is a Froyo Rom, the Revo is now on Gingerbread. Either restore your back up, or download and install GingerVolt Rom.
Click to expand...
Click to collapse
yep, that was all it took. I downloaded gingervolt and the reboot problem went away. Hopefully a new sim card will get it back up and running. Thanks again for everyones help.
hey guys i searched and havent really found anything that matched quite what i had going on so here we go... I was 95 percent through flashing the ICS rom it got through the hboot section and rebooted.. on the screen i saw two arrows in circular form above a phone .. and something was definitely being downloaded.. then the phone went black, doesnt go into hboot, doesnt a charging light when plugged in , but is picked up by the computer, ie. connection noise. Im in no way a noob at flashing roms , but something is definitely wrong with my phone.. Any ideas? It was charged full battery by the way.. it does glow in a dull light when i push volume down and power, or power alone...
Your phone indeed seems to be bricked. The identification noise from the computer may just mean that your USB is receiving power from the battery.
When my friend had a similar problem with his Amaze, he went to the HTC service center and they replaced his phone after keeping it for 4 days
So taking it to bestbuy to get it serviced is probably the only alternative, since its insured through them... lol just my luck
I brick mines as well. If you love your device stay away ics for now .
Sent from my Galaxy Nexus using xda premium
Dxtra said:
I brick mines as well. If you love your device stay away ics for now .
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
That's not fair to say. There's plenty of users that flashed without bricking their devices.
I followed the alternate directions here and had no issues.
Dxtra...I was able to do it no problems...saying to stay away is not at all accurate unless u cannot fully comprehend the instructions...never tell ppl to shy away from improvements because u urself did not succeed just offer warning...it is the linux way
Sent from my HTC PH39100 using XDA
meatwad0222 said:
Dxtra...I was able to do it no problems...saying to stay away is not at all accurate unless u cannot fully comprehend the instructions...never tell ppl to shy away from improvements because u urself did not succeed just offer warning...it is the linux way
Sent from my HTC PH39100 using XDA
Click to expand...
Click to collapse
I'm not the only one with a brick device, there's plenty more on here. Our phone is a pretty expensive device if you got the money and you want to take the risk go ahead. Why would I tell anyone to flash when is not safe to.
Sent from my Galaxy Nexus using xda premium
Dxtra said:
I'm not the only one with a brick device, there's plenty more on here. Our phone is a pretty expensive device if you got the money and you want to take the risk go ahead. Why would I tell anyone to flash when is not safe to.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Not sure why you keep posting it's not safe. I think I've seen like 3 people who've screwed it up out of probably 100+ installs. PirateGhost has released an ICS RUU which is completely noob proof so even unrooted users can get some ICS love before the OTA update.
As far as im concerned each one of us is responsible for what happens to our phones, warnings are put for a reason.. ive jailbroken, rooted the hardest of phones .. it was just my time for the inevitable to happen. I get my phone back in three days and you can be sure ill be back here again doing crazy rooty stuff to my phone no rom or dev should be held responsible for what ive done ..
Sent from my MB860 using Tapatalk
dusty2422 said:
Not sure why you keep posting it's not safe. I think I've seen like 3 people who've screwed it up out of probably 100+ installs. PirateGhost has released an ICS RUU which is completely noob proof so even unrooted users can get some ICS love before the OTA update.
Click to expand...
Click to collapse
Saying something is noob proof will inevitably prove that some where some noob will sow its not noob proof. I'll admit there were a few moments of panic when I flashed the zip method pg released. When that happened I just breathed deep and took my time and everything worked great in the end. I personally feel that what the devs have put out there is fairly safe as long as the directions are followed exactly.
Sent from my HTC PH39100 using xda premium
Dxtra said:
I'm not the only one with a brick device, there's plenty more on here. Our phone is a pretty expensive device if you got the money and you want to take the risk go ahead. Why would I tell anyone to flash when is not safe to.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I don't have the money to buy tons of new devices....its about knowing ur own limitations...do not criticise a devs hard work when it is proven to work...no its defenitly not idiot proof but it is very easy...I've done it to 3 phones already with no problems...the devs are not responsible for bricked phones
Sent from my HTC PH39100 using XDA
yea i must say it was a hundreed percent my fault in bricking my device so im not mad at anyone..and as far as the money goes its not a super big deal..i always make more o and btw im gonna be getting my replacement today and im gonna try this all again aft6er reading everything again and again and agian o and again lol
So, the phone is bricked. I have the same problem as the OP. I Lost access to Hboot while flashing ICS. I accidently sent it to recovery after Hboot update...and it never recovered LOL. Anyone know a good de-bricking service or know how much it will cost if I send it back to HTC or AT&t to fix it? I bought mine at the AT&T store, so no protection plan. I'm gonna get another device anyway (from Best Buy this time), but it would be great to have the Vivid back as a backup.
I bricked my phone Sunday night, still not 100% sure what I did wrong but it did what yours is doing now. I simply called the AT&T exchange by mail and used the factory warranty. Granted I guess there is a slight chance they could find out it was rooted (if they can somehow get it to recover or even turn on) but it got me a replacement... Food for thought.
Btw I got the new one and used the RUU and it worked seamlessly.
Sent from my HTC PH39100 using xda premium
bsSkunkApe said:
So, the phone is bricked. I have the same problem as the OP. I Lost access to Hboot while flashing ICS. I accidently sent it to recovery after Hboot update...and it never recovered LOL. Anyone know a good de-bricking service or know how much it will cost if I send it back to HTC or AT&t to fix it? I bought mine at the AT&T store, so no protection plan. I'm gonna get another device anyway (from Best Buy this time), but it would be great to have the Vivid back as a backup.
Click to expand...
Click to collapse
I did the same thing, selected recovery right after successful HBoot update. Then afterwards, each and every restart shows searching sd card with a black background. After several attempts of pulling battery, reinsert and power button + vol down, I was able to get back into HBoot. From there I immediately flash recovery through fastboot and now am happily on ICS.
If you did the same and phone boots up with the searching sd screen, there is a shot of bring it back.
dizzyraider said:
I did the same thing, selected recovery right after successful HBoot update. Then afterwards, each and every restart shows searching sd card with a black background. After several attempts of pulling battery, reinsert and power button + vol down, I was able to get back into HBoot. From there I immediately flash recovery through fastboot and now am happily on ICS.
If you did the same and phone boots up with the searching sd screen, there is a shot of bring it back.
Click to expand...
Click to collapse
Fraid it doesn't search for anything. I posted in the threads and tried everything I could think of and everything that was suggested. Though there isn't much you can do besides keep removing the battery and trying vol dn + pwr. Just a black screen.
Just a few things I tried (removed battery each time)- vol down + power (no sd card in) = blank black screen
vol down + power (with sd card and PH39IMG file) = blank black screen
vol down + power > boots to blank black screen, wait few seconds > press power button (like I'm going to fastboot) > plug into computer > type fastboot command into command prompt = command prompt says waiting for device
I always read the directions and threads a bunch of times before doing anything. Did lots of reading, google-ing, and searching. Fraid it bit the dust. I appreciate the help though. This is the first device snafu I've had. I've never had to send a phone in for any kind of warrantee work before. Hence my question above about getting it fixed.
Just in case, if it were to boot to that screen, what would I want to do? Just the PH39IMG? Or is there some other procedure?
Dxtra said:
Why would I tell anyone to flash when is not safe to.
Click to expand...
Click to collapse
Who TOLD you to flash the phone??? When I got my first android phone, a Samsung Fascinate, I LOVED the phone but nervous AS HELL that I would brick the phone. And I read, and read, and REREAD, trying to make sure I understood everything so that when I went looking for help, I at least could say, "Yes, I already tried this, this, and this".
I think the key thing to all of this is in two-fold - one, as someone stated before, this is a developer's forum. If you work on your car, and forgot to put oil in it, are you going to blame your mechanic? If you change your brakes and did not do something correctly, causing an accident, are you going to blame the car manufacturer??? Two, it states in MANY places, before you post, READ, READ, READ. It was actually ADVISED to NOT FLASH this ROM...
From this point forward, it almost seems as if there needs to be a waiver release to download roms, stating you will not ridicule nor torment the developers. And though I had heard about it but never seen it before, as I am on my 4th Android phone, there definitely are a few VERY NOTICEABLE disrespectful and ungrateful individuals in this forum. If you were my kid, and acted like that to me for something I GAVE YOU, I would do the same as PG - TAKE IT WAY and forget you.
well, i read all the time how nexus devices are unbrickable and maybe (hopefully) im wrong! so i been running stock rom rooted for a few days actually since yesterday i flashed back to stock and rooted only and flashed cwm recovery thats it. today (actually just a little while ago) i was messing around and was running antutu benchmark with stock then i flashed franco r53 kernel using his auto flash method in his app. no sooner that i started the test in antutu phone went completely black. will not respond to anything. so i said well maybe i can connect usb and get it to go into fastboot so i got lucky (or so i thought) soon as i plugged it in i saw red light at the bottom and battery charging icon. so i press power and volume down and was able to get into fastboot, i was kinda happy about this. i flashed back to stock wiped everything first wipe boot wipe cache wipe recovery wipe system flash bootloader reboot bootloader and flashed the system img and boot img and all that went thru succesfully. but it still will not boot it goes in and out red light battery icon google image. so i tried again flash stock images locked bootloader and fastboot reboot nothing i unplug usb goes straight black screen and wont respond. plug back in get red light and battery icon in and out back and forth between icon and black screen with red light. so i know allot of people get complacent in thinking that because you have a nexus you cannot brick but it is possible to brick this phone. or maybe someone can tell me im wrong. lol anyways just posting this here for people to think twice and not get so comfortable thinking you cannot brick a nexus. tommorow ill take the phone to t-mobile and get another one. and no i wont tell them it was my fault! (< for that one guy) lol good night!
I read lot about "antutu benchmark" as it's bad for Nexus 4 and cause this problem!.
hope somebody can help you out.
maddoggin said:
well, i read all the time how nexus devices are unbrickable and maybe (hopefully) im wrong! so i been running stock rom rooted for a few days actually since yesterday i flashed back to stock and rooted only and flashed cwm recovery thats it. today (actually just a little while ago) i was messing around and was running antutu benchmark with stock then i flashed franco r53 kernel using his auto flash method in his app. no sooner that i started the test in antutu phone went completely black. will not respond to anything. so i said well maybe i can connect usb and get it to go into fastboot so i got lucky (or so i thought) soon as i plugged it in i saw red light at the bottom and battery charging icon. so i press power and volume down and was able to get into fastboot, i was kinda happy about this. i flashed back to stock wiped everything first wipe boot wipe cache wipe recovery wipe system flash bootloader reboot bootloader and flashed the system img and boot img and all that went thru succesfully. but it still will not boot it goes in and out red light battery icon google image. so i tried again flash stock images locked bootloader and fastboot reboot nothing i unplug usb goes straight black screen and wont respond. plug back in get red light and battery icon in and out back and forth between icon and black screen with red light. so i know allot of people get complacent in thinking that because you have a nexus you cannot brick but it is possible to brick this phone. or maybe someone can tell me im wrong. lol anyways just posting this here for people to think twice and not get so comfortable thinking you cannot brick a nexus. tommorow ill take the phone to t-mobile and get another one. and no i wont tell them it was my fault! (< for that one guy) lol good night!
Click to expand...
Click to collapse
If it's easy to take back do it. However couple of folks have got it fixed by opening the backplate and disconnecting/reconnecting battery terminals.
Almost 90%+ people having this issue were running Antutu.
Why would you think its a good idea to flash a custom kernel on to stock?
There are tons of threads about this, do some searching your phone is not bricked, also to the poster above me there is nothing wrong with flashing a custom kernel over stock.
Sent from my Nexus 4
http://forum.xda-developers.com/showthread.php?t=2128392
XxSilent22xX said:
There are tons of threads about this, do some searching your phone is not bricked, also to the poster above me there is nothing wrong with flashing a custom kernel over stock.
Sent from my Nexus 4
Click to expand...
Click to collapse
Actually that is incorrect, it is not okay. Most Devs will post comparable kernels, or flash your own kernel on to this rom at your own risk on every rom thread op. Stock only supports its own kernel, so while some kernels might work as a stock replacement kernel, it is never a good idea to flash a custom kernel on to a stock rom unless the Dev says otherwise.
This for the help. I'll try this tomorrow morning. Of course I tab a search bit could not find the threads. I hit red light and it took me to legacy phone. I type brick in search fort n4 and nothing. So I never saw those threads about this issue. So thanks. And ive never had a problem with running custom kernels on stock ROM. Never! Lol
Any ways thanks for help! Can moderator close this thread please! Thanks!
Sent from my Galaxy Nexus using xda premium
And then u guys say that a removable back cover is not a deal breaker
There are a lot of times when u need to reset the phone by taking the battery out
Sent from my GT-N7000 using xda app-developers app
Franco R53 is fine on stock - running it here with minimal other changes (I.e. root + email security policy hack)
I've updated every Franco kernel and all seen OK. Perhaps the benchmark related hardware failure is worth looking closely at.
FWIW, if you're back to stock, lock the bootloader and send it back as it sounds hardware to me.
Daern
Sent from my Nexus 4 using Tapatalk 2
synergeticink said:
Actually that is incorrect, it is not okay. Most Devs will post comparable kernels, or flash your own kernel on to this rom at your own risk on every rom thread op. Stock only supports its own kernel, so while some kernels might work as a stock replacement kernel, it is never a good idea to flash a custom kernel on to a stock rom unless the Dev says otherwise.
Click to expand...
Click to collapse
:sigh: No. Franco says his kernel supports the stock ROM. In fact, stock is the standard to test a kernel on. Unless a ROM is created with very specific additions that rely on a custom ramdisk to function, there is nothing wrong with it. Even then, it's not really wrong, you'll just have some missing features.
Charge your phone?
Im pretty sure you get the red light if your device has not enough power to display the screen.. Put your phone on charge through the main plug
qazibasit said:
And then u guys say that a removable back cover is not a deal breaker
There are a lot of times when u need to reset the phone by taking the battery out
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
So true man so true!
Sent from my Galaxy Nexus using xda premium
This happened to me, except I was bone stock. You need to hold down all 3 buttons at the same time; several times, and then try to get into the bootloader. That's what worked for me. Once you're in the bootloader you can flash the stock image(s) via fastboot.
qazibasit said:
And then u guys say that a removable back cover is not a deal breaker
There are a lot of times when u need to reset the phone by taking the battery out
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Holding down the power button for five seconds is the equivalent to pulling the battery, is it not? That is how it has been on other devices with non-removable batteries.
Sent from my Nexus 4
OniV2 said:
Holding down the power button for five seconds is the equivalent to pulling the battery, is it not? That is how it has been on other devices with non-removable batteries.
Sent from my Nexus 4
Click to expand...
Click to collapse
if this is true then why do i need to pull the phone apart and disconnect the battery and reconnect? apparently this is a known issue and has happened to others and taking phone apart and disconnecting battery and rconnecting it fixes the issue. unfortunately i dont have the right tools to do this so i will be taking my phone to t-mobile this morning. thanks for all the help guys. really appreaciate all the responses i got.
At times the power button wont work. In some cases of soft bricks. I have this issue since i had HD2.
Sent from my GT-N7000 using xda app-developers app
estallings15 said:
:sigh: No. Franco says his kernel supports the stock ROM. In fact, stock is the standard to test a kernel on. Unless a ROM is created with very specific additions that rely on a custom ramdisk to function, there is nothing wrong with it. Even then, it's not really wrong, you'll just have some missing features.
Click to expand...
Click to collapse
That's exactly what I said in my last post. Next time the op needs to clarify if the custom kernel supports stock. But regardless I was correct.
OniV2 said:
Holding down the power button for five seconds is the equivalent to pulling the battery, is it not? That is how it has been on other devices with non-removable batteries.
Sent from my Nexus 4
Click to expand...
Click to collapse
The service manual says ten seconds but yes it fully cuts power from the battery.
So sitting in my car waiting for t mobile store to open I decide to plug phone in to car charger since I know this will be first thing t mobile does and lo and behold phone booted up and start working. Battery drained to 0 and charging now. Go figure
Sent from my Nexus 4 using xda premium