So my buddy bought a "new" LGOG on Craigslist from someone. We get it, and it's acting really odd. Forceclosing, freezing, shutting off, etc. Even after a factory restore, same issues persisted.
I said just bring it over and we'll LGNPST it back to stock. I plugged it in and LGNPST'd it to the newest official Jellybean and some of his stuff was there like a few apps, wallpaper, etc. VERY odd. Certain things were still force closing as well. I LGNPST'd it back to the ICS ROM, and still teh same thing. Some data was there.
So I tried getting into fastboot to wipe the phone and it for the life of it woudl NOT enter fastboot. Vol Up+Power, tried ADB commands such as adb reboot fastboot, and adb reboot bootloader. The phone would just reboot twice and boot into the OS. It was like the prev. owner screwed up the boot loader somehow, maybe trying to Freegee? But wouldn't LGNPST reflash that?
I finally got fed up and flashed the Nexus 4 .TOT file in LGNPST and flashed CM10.1. The phone functions perfectly now and enters fastboot and is stable.
SO my question is, what could have happened, and why would it only enter fastboot once I LGNPST'd the N4 ROM? I'd like to convert back but I'm afraid once I do I'll be back to square one. Any ideas of what the heck happened?
PS. I know the N4 convert is frowned upon but it seemed like the only thing left to do. My phone is currently N4 converted, though I'm converting back soon to LGOG.
I also tried flashing one of the Tinybin fixes.
We don't have fast boot when stock. We get fast boot after freegee
Sent from my LG-E970 using Tapatalk 2
Also, it seems for quite a few people they need the alt version of the teenybin, I did.
When I used the original one it just hung at the LG logo.
Wipe data after you lgnpst
Sent via LG E970 with houstonn aokp 4.2.2
bleached45 said:
Also, it seems for quite a few people they need the alt version of the teenybin, I did.
When I used the original one it just hung at the LG logo.
Click to expand...
Click to collapse
Same here with the Alt version. Though, I also had to disconnect the battery after using it. The phone wouldn't do anything outside of getting into fastboot, couldn't even load into recovery. Everything was peachy after the disconnect.
Sent from my LG-E970 using xda premium
Related
After countless hours of research, I decided to unlock my bootloader and to root my Motorola Atrix 4G. With success, I was happy to have everything working and installed the Darkside Custom Rom. I let a friend borrow my phone, and they saw the AT&T system update and they decided to install it. They bring back the phone and the system update has finished and was installing. The phone powers off and starts to install the update. 10% into the install, it stops, and I got the little green droid man with the /!\ behind him. I take out my battery, place it back in after 30seconds. It powers on, boots up, powers off and tries to load the update again. I restart it, but this time quickly going into RomManager and starting it up in Recovery Mode. I go to restore the phone using the file I backed up from the TitaniumBackUp app, everything backs up except the system. I plug my phone into my laptop, and everything is in the folder. I performed a system/factory reset, downloaded the last Gingerbread update, but nothing helps. Anything I try to load it says "Installation aborted". No matter if it's the original update or a ROM I download. Looking up other forums, I notice others that have downloaded the Darkside ROM have had the same; if not similar issues. I apologize for the length of this message, but I wanted to put in as much detail as I could so you know exactly what the issue is. I look forward to hearing from someone, and thank you in advance!!!
You probably need to sbf it back to a stock ROM and start over. I had a similar problem when I first got my Atrix and the AT&T update first came out. I had already rooted it and didn't unlock the bootloader yet. It tried to update and bricked the phone. Got AT&T to give me another though as I had just got the thing.
nickdeal said:
You probably need to sbf it back to a stock ROM and start over. I had a similar problem when I first got my Atrix and the AT&T update first came out. I had already rooted it and didn't unlock the bootloader yet. It tried to update and bricked the phone. Got AT&T to give me another though as I had just got the thing.
Click to expand...
Click to collapse
Thanks a ton! How would I go about doing that?
You need to download motorola RSD app to you computer. Search XDA for stock firmwares and download one. You will then need to use the button combo to get in to RSD. Connect the phone to your computer and make sure it recognizes. I had an issue where one of my laptops would not recognize the phone for anything. I had to use a different laptop. Once it's done you should be back to stock. The bootloader should be unlocked still. Just root and flash your ROM of choice.
Sent from my MB860 using XDA App
Okay. So. After some trouble with houstonn's latest rom's lately (getting stuck on boot), I decided I'd give one more try for the 4/30 release. Clean wipe, flashed it, flashed minimal apps. Stuck on boot. WOOP WHO CARES?
This time was different - I couldn't access recovery. So I tried like 30 more times to access recovery. Couldn't do it. LGNPST back to the ICS stock bin (11c). Get my OTA update to 4.1.2, rooted with this method http://forum.xda-developers.com/showthread.php?t=2006946. After that, I tried to access recovery mode again. Couldn't do it. So, I was like "what the hell, maybe FreeGee will help." So I continued on to unlock the bootloader with FreeGee and with CWM. Installed quickboot and chose to restart to recovery. SAME THING. Black Screen after LG logo. Can't get into recovery.
Now I'm LGNPSTing back to stock to repeat process. Any ideas on what's going on?
Edit: Running into quite a few problems with LGNPST. Gets stuck at 85% and won't boot even after power cycle.
Edit 2: TeenyBin AltBin let me format my partitions and then the LGNPST worked. Got the OTA. Rooted again, used FreeGee, except this time with TWRP 2.5.0.0. Wouldn't reboot afterwards, so moved on to TeenyBin AltBin again. The phone booted up and everything runs fine. One thing to note: I had some wifi problems when I just TeenyBinAltBin'd and used a restore point for stock 4.1.2 which is why I was so adamant to LGNPST like normal. Still can't flash any of the newer ROMs of houstonn's, but I can others. On the good side, I still have a phone. Hopefully if anyone else has the issue, they can follow this and resolve it.
Hello everyone, i am currently on a brand new p769 from Tmobile and i have it rooted and very debloated through my own means, like nova launcher, jb camera, viper4android and such and such.
so today my phone gave in and said that it no longer has any space, yet i have a 32 gig SD card and i know that apps2sd is disabled because LG and blah blah.
SO im seeing that our phone has a decent CM10.1 rom and a great PAC rom and i loved those roms when i still used my HTC Incredible 2, but i have a locked bootloader, and i cant simply flash it with the cwm recovery i currently have. so my questions are the following:
Is the 4G impacted in any way? Like speed-wise
Wifi calls arent that important but it'd be great if there was a workaround.
Is it hard to re-lock the bootloader if the phone ever breaks?
i dont care for 1080p recording as the 5MP camera isnt that great either way, but i really hope that there isnt any camera problems
and finally, will my apps be able to be installed in the SD card?
so is it worth unlocking the bootloader or not?
All pros no cons stock sucks
Sent from my SGH-M919 using Tapatalk 2
richardlibeau said:
All pros no cons stock sucks
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
WELP i guess thats good enough for me!
Its hard to unlock the boot loader but its worth it if you're ultimately successful. My bootloader is unlocked. Want more space for apps? Unlock that bootloader and throw AntonX's CM10.1 on there. Stock should've had this setup(apps2sd and no emulated SD storage) period.
Sent from my LG-P769 using Tapatalk 4
Im trying. It's the hardest thing I've done yet, I'm sitting on 10g right now trying to see what's next
Sent from my LG-MS910 using xda app-developers app
MoonMaster345 said:
Im trying. It's the hardest thing I've done yet, I'm sitting on 10g right now trying to see what's next
Sent from my LG-MS910 using xda app-developers app
Click to expand...
Click to collapse
Make sure you follow the instructions word for word. Something small done different could leave you stuck wondering what the problem is. Even if you have to read the instructions more than once or twice then that's good. BTW "4G" speeds don't seem to be impacted. Its faster than my home internet. I'm better off watching hq YouTube videos on my tablet with the built in wifi tether in CM from my phone, rather than my home connection.
Sent from my LG-P769 using Tapatalk 4
MoonMaster345 said:
Hello everyone, i am currently on a brand new p769 from Tmobile and i have it rooted and very debloated through my own means, like nova launcher, jb camera, viper4android and such and such.
so today my phone gave in and said that it no longer has any space, yet i have a 32 gig SD card and i know that apps2sd is disabled because LG and blah blah.
SO im seeing that our phone has a decent CM10.1 rom and a great PAC rom and i loved those roms when i still used my HTC Incredible 2, but i have a locked bootloader, and i cant simply flash it with the cwm recovery i currently have. so my questions are the following:
Is the 4G impacted in any way? Like speed-wise
Wifi calls arent that important but it'd be great if there was a workaround.
Is it hard to re-lock the bootloader if the phone ever breaks?
i dont care for 1080p recording as the 5MP camera isnt that great either way, but i really hope that there isnt any camera problems
and finally, will my apps be able to be installed in the SD card?
so is it worth unlocking the bootloader or not?
Click to expand...
Click to collapse
You can switch int to ext... Since you have a 32gb then it'll be very good for you. Go HERE for more info...
Sent from my LG-P769 using Tapatalk 4
I'm actually stuck right now in the step before getting to fastboot. i flashed v20B euro then installed x and u i think then i wiped then installed v10g then wiped then reinstalled 20B then waited more than 20 minutes and it just reboots instead of going to fastboot when i do adb reboot oem-fastboot..
i'll go back to stock for the day (its 4 am currently) and see if i can try again in the morn
MoonMaster345 said:
I'm actually stuck right now in the step before getting to fastboot. i flashed v20B euro then installed x and u i think then i wiped then installed v10g then wiped then reinstalled 20B then waited more than 20 minutes and it just reboots instead of going to fastboot when i do adb reboot oem-fastboot..
i'll go back to stock for the day (its 4 am currently) and see if i can try again in the morn
Click to expand...
Click to collapse
I did it without fastboot. I used the wonky touch screen to install Artas' recovery installer, then did the touch fix and bingo bango bongo
If your only problem with stock was the App2sd, then there are some 5-minute solutions out there.
https://play.google.com/store/apps/details?id=com.buak.Link2SD
or
http://forum.xda-developers.com/showthread.php?t=1410262
Personally, I use my L9 for most of my camera activities, so the 1080HD is quite a necessary.
MoonMaster345 said:
I'm actually stuck right now in the step before getting to fastboot. i flashed v20B euro then installed x and u i think then i wiped then installed v10g then wiped then reinstalled 20B then waited more than 20 minutes and it just reboots instead of going to fastboot when i do adb reboot oem-fastboot..
i'll go back to stock for the day (its 4 am currently) and see if i can try again in the morn
Click to expand...
Click to collapse
I just got the bootloader unlocked on my P769 a couple days ago. I got lost along the way, so I had to retrace a couple steps and hop around.
I started with the stock V20D (T-Mobile USA), downgraded to V20B (European). You gotta wait at the very minimum 30 minutes. Give yourself 45 minutes to be safe. The V10G is simply to root, but there's a bunch of bins that can be used to do so with the other JB ROMs. If you're doing everything all over again, don't worry about rooting or the recovery until you've finished the bootloader unlock.
Running AntonX's CM10.1 right now, it's smooth and stable. In terms of space, internal is fixed at 1.8GB. I still have about 561MB available, and I'm done loading all the apps I actually need.
Guys i actually just want to finish this...so if someone can quickly respond that'd be great.
Here are all the steps i did.
I was stock 20f, i was rooted, i downgraded to 20B, screen inverted but not the LG logo or anything, restarted, went to 10G, screen is now Inverted, went to recovery, installed radio, rebooted, installed x and u, went to 20B again and waited multiple times, no adb reboot oem-unlock.
so i went back to 20f for the night, screen is fine but touch is messed up, can't access recovery for the life of me, factory reset, flashed 10G again, screen still fine but touch isn't. when i try to install x and u it gives me UNKNOWN ID: DD, so i think its laready installed?
now what do i do?
do i flash 20B without the bin then wait again?
or do i do as in the video and install 10G instead then continue?, or do i wait now that i'm on 10G and try the adb reboot oem-unlock?
i cant use stock because the screen is inverted and even though the phone is rooted, the recovery wont work..
I pretty much did the same thing you did, loading a non-P769 ROM before unlocking the bootloader.
Like I mentioned, ignore rooting and installing a recovery until the bootloader is done.
Now that you've reversed and screwed up (it's supposed to happen, not a real screw up) the touchscreen, you can't fix that until you root. So instead, let's just unlock the bootloader first.
Do the offline flashing method for the V20B (European OPEN) ROM again. Then wait the 30-45 minutes after the device is on. Make sure that the radio is on, with a SIM card in it, though this might not be necessary.
queboy89 said:
I pretty much did the same thing you did, loading a non-P769 ROM before unlocking the bootloader.
Like I mentioned, ignore rooting and installing a recovery until the bootloader is done.
Now that you've reversed and screwed up (it's supposed to happen, not a real screw up) the touchscreen, you can't fix that until you root. So instead, let's just unlock the bootloader first.
Do the offline flashing method for the V20B (European OPEN) ROM again. Then wait the 30-45 minutes after the device is on. Make sure that the radio is on, with a SIM card in it, though this might not be necessary.
Click to expand...
Click to collapse
Or if you can somehow figure out how to connect your WiFi with the wonky touch screen, having an active data connection the entire time is the most important part.
The easiest way to do all of this:
1.) I used Lelus root method for JB as I installed V20B, it'll be rooted once you boot it up, if not then you did something wrong.
2.) At this point I navigated the inverted touchscreen to WiFi settings and enabled my connection (typing in the network key was a b****) this way you always have an active data connection (make sure in Advance setting for WiFi that it doesn't turn off while screen is off) you will need this for the bootloader to unlock properly.
3.) It's extremely important that you enable USB Debugging, you need this to run adb commands. Once that's all done, wait a half hour (I waited a whole hour) run the unlock bootloader command. It should bring you to a prompt screen asking you to press one of the volume keys to confirm you want it unlocked. After that it boots into fastboot.
4.) Congrats! Your bootloader is now unlocked, you might wanna use the toolkit to flash recovery with while you're on the bootloader.
4.) I put the necessary files to reverse the touch screen back to normal on my sdcard, you'll be able to use adb to run a command to install the fix. I believe it was a v6.bin file, it's been so long I sorta forgot some of this but it'll ring a bell if I just tried again from the very start. This fixes the reversed touch, you need to flash a different ROM and the radio for P769 as well (for your signal to work).
5.) At this point I just decided to make a nandroid backup and wipe everything and I installed CM10.1 at that point, never bothered going back to stock afterwards, I am so content with my phone after unlocking it.
After unlocking, I can honestly say this phone will hold me down for a long time, and it gave me the motivation I need to save up for a newer phone without the urge of replacing what I have at any point. (I'm waiting on the new Nexus, can't wait to see how it turns out)
Sorry if my instructions don't make much sense, I quickly jotted these notes down, no access to a PC so I'm writing all of this on Tapatalk 2, this is what I did and I was successful. You'll get it done, just don't lose your patience. It'll be soooooo worth it, I almost gave up but now I'm glad I didn't. This is quite possibly the most difficult device I've ever rooted, but I had prior experience with .kdz offline method on my older device (LG E739) along with learning how to come back from a full hardbrick (my old phone is a zombie) so this whole process was pretty familiar to me, that experience helped me understand everything I needed to know in no time.
We all know your pain, and trust me I'm happy to help because stock ROM just isn't worth keeping when you can have a highly optimized custom ROM instead.
Good luck! Hope you're successful in your attempts
Sent from my Pokédex
You guys are a great community, so much help im getting :laugh:
i feel at home here.
i'll see if your instructions work. i am in the rooted 20B so that means i did lelus' root properly, i see the superSU
i got the wifi working so now i wait right?
adb also works i tested adb devices.
should i leave the screen on all time? also should i install the cmw/bootstrap recovery?
30 minutes later and no go with adb reboot oem-unlock.....
im actually running the commands from a folder with the adb and fastboot files, am i supposed to run the commands form somewhere else?
Im currently sitting on a rooted v20B with wifi and 4g working but for the life of me i can't get it to reboot to fastboot..
MoonMaster345 said:
Im currently sitting on a rooted v20B with wifi and 4g working but for the life of me i can't get it to reboot to fastboot..
Click to expand...
Click to collapse
Patience is the key mang, the amount of time it takes could vary.
Does it reboot at all when you type that command?
Sent from my Pokédex
leolawliet said:
Patience is the key mang, the amount of time it takes could vary.
Does it reboot at all when you type that command?
Sent from my Pokédex
Click to expand...
Click to collapse
It indeed reboots but not to fastboot like it should.
i was actually able to boot into fastboot by the omap4boot mode but i dont think it helps..
I would like instruccions to go back to full stock, fix screen and touch and all. then start from square one..
MoonMaster345 said:
I would like instruccions to go back to full stock, fix screen and touch and all. then start from square one..
Click to expand...
Click to collapse
From the beginning
http://forum.xda-developers.com/showpost.php?p=44325657&postcount=4&nocache=1&z=6862240654882044
Good luck and be patient! It worked for me.
Sent from my LG-P769(20F) using the xda-developers app. If I helped you please hit the "thanks" button.
So today, i went to load up a book in kindle and it crashed a couple times in a row. I figured no biggy, and rebooted the phone (which I can't remember the last time I did, weeks ago).
Upon reboot, for some reason, I'm stuck in a boot loop. I get the white screen with the HTC logo for about 15-30 seconds, it shuts down, repeat. I figured no biggy, everything is stock, I don't care about anything on it, I'll just use the RUU to fix it.
That is where my problem begins. Unforunately, I am updated to 2.95, and the last release RUU is 2.89, so it won't let me install. I can get into hboot, I can use fastboot, so I used fastboot to erase the cache. Anything I select (factory reset, recovery, etc) in hboot just sends me back into the reboot loop. Manually flashing errors out because of the mainver discrepancy. I can't use the low version fix because I'm not rooted, so sure, let's try that... I started the process and unlocked successfully. Now the problem is, any recovery I've installed (4ext from the root thread, CWM5.8 from the boot loop thread) installs fine, but whenever I reboot recovery, again, boot loop. It doesn't matter whether the reboot comes from a fastboot command or selecting recovery reboot from inside hboot.
So, desperate (and somewhat ignorant), I booted up into Linux and tried the unbrick post, and of course, the device never shows up with the battery out, cause it ain't bricked. I was hoping somehow that I could use it to replace hboot, figuring that might be corrupt or something crazy like that (grasping at straws really).
What I really need is a 2.95 RUU, but that hasn't been released, and I figured if that didn't work, something is probably fried hardware wise.
I restored a stock signed recovery, so more or less, right now I'm back exactly where I'm started (other then the fact that my phone is now unlocked) and just not sure where to go from here. Any advice would be helpful. Thanks!
EDIT: I'm a moron, and I forgot to specify, but the phone is sprint. I also don't have any service on it (mainly used as an mp3 player) so I don't have any recourse through them.
I'm almost considering bricking the thing to change the hboot (I haven't done my homework on it yet) any thoughts there? Or is it not something I can do because of my problem?
Sounds like you didn't flash a ROM after getting into recovery.
You need to make sure you're unlocked, and flash a recovery...4ext recovery is highly recommended as it has a setting just to help s on users.
To start and get you up and going, i suggest downloading butterz sense ROM and placing it on your SD card.
Then you need to wipe everything except your SD card
Now flash a new rom, like butterz sense.
Reboot and you should be good
If not you may need to flash boot.IMG in fast boot.
to run an old ruu, you will need to get s off and for that you need a booting ROM.
Good luck!
Sent from my Evo 3D CDMA using xda app-developers app
hossman said:
Sounds like you didn't flash a ROM after getting into recovery.
You need to make sure you're unlocked, and flash a recovery...4ext recovery is highly recommended as it has a setting just to help s on users.
To start and get you up and going, i suggest downloading butterz sense ROM and placing it on your SD card.
Then you need to wipe everything except your SD card
Now flash a new rom, like butterz sense.
Reboot and you should be good
If not you may need to flash boot.IMG in fast boot.
to run an old ruu, you will need to get s off and for that you need a booting ROM.
Good luck!
Sent from my Evo 3D CDMA using xda app-developers app
Click to expand...
Click to collapse
Well, the problem is that I can't get into a recovery after I install it, I'm still caught in the boot loop... but I will try flashing the boot img. Thanks!
If you would like a quicker response/fix check your pm....i can try to help
Sent from my Evo 3D CDMA using xda app-developers app
Well, I did reflash boot.img with no success. I went to relock the phone and was just gonna throw it on the shelf for a couple weeks (as I do have another one), and when I did that using fastboot, it sent the command over and the phone received it, but it gave me a failure message. So now, it doesn't turn on, when I hook it up to the charger, I get the red charging light for about 10 seconds, and very occasionally when I remove the battery and put it back in the HTC logo appears for about 3-5 seconds before the phone cuts off again.
I'm starting to think there was some hardware issue. Since it had a screwy digitizer anyways (and I chose to get another evo for 65 rather then paying 30-35 for the ldc/dig combo), I'm just going to keep it around for parts and maybe play with it another time.
Your offer of help is greatly appreciated however, thank you.
EDIT: It doesn't seem to be truly bricked, or it isn't a recoverable brick... not really seeing the dim red light and the unbrick script doesn't detect it... the phone isn't in emmc mode... but I'm not hugely concerned with it now like I said.
LOL I'm a moron... my battery went dead during the whole recovery thing. Slapped another battery in and I am back to the original problem. Ignore my last post, basically.
At this point, I think that I might be possible that I can't get into recovery because, to the best of my knowledge, the "fast boot" option is ticked in the settings. Unfortunately, I can't get into the phone to change it, so even more chicken/egg stuff. Bleh. I'm still chugging along, any input appreciated. Maybe I can call HTC or Sprint and beg for an RUU?
thatdumbguy said:
LOL I'm a moron... my battery went dead during the whole recovery thing. Slapped another battery in and I am back to the original problem. Ignore my last post, basically.
At this point, I think that I might be possible that I can't get into recovery because, to the best of my knowledge, the "fast boot" option is ticked in the settings. Unfortunately, I can't get into the phone to change it, so even more chicken/egg stuff. Bleh. I'm still chugging along, any input appreciated. Maybe I can call HTC or Sprint and beg for an RUU?
Click to expand...
Click to collapse
Good luck!
So pull the battery, and put it back in.
Hold volume up and then press power.
Does that bring you to boot loader?
Does it say unlocked?
Sent from my Evo 3D CDMA using xda app-developers app
Hello all, and thanks in advance for your help. I don't know if all of this is relevant to what happened, but I'm including it in case there's some small clue.
My phone was an S-OFF running HBOOT 2.09. I have been running Deck's CM builds for a while now with no issues. Last week, I decided to update to the new firmware which included the new partition layout.
HTC's RUU executable did not work, so I used the two zip method in this post. I first renamed rom_01 to PJ75IMG.zip, placed it on the SD card, rebooted and installed, then did the same with rom_02. Loaded everything up, seemed great with the stock image. After verifying everything was working fine, I flashed a new recovery (2.7.0.0b, via PJ75IMG.zip as well), and installed the latest OmniROM (3/31) via recovery. I had some issues with the PA 0-Day GAPPs that were recommended (force close errors with Google Keyboard) so after reflashing Omni switched back to the 12/09 GAPPs in Deck's thread. Everything seemed great.
A few days later, after having the phone in my pocket, my screen turned into a rainbow of pixels. Here is what it looks like: http://imgur.com/9ef6F8z It still seemed to work, just the screen was always that rainbow.
Thinking it was an issue with the firmware, I tried to RUU back to a somewhat earlier stock by using ViperRUU 3.16.651.3. However, after going through the RUU process, it had gone about 30-40 minutes with no updates, so I thought it had crashed. I checked to see if that was normal, and saw that it was not and they recommended restarting the process. I restarted both the ViperRUU (couldn't find phone anymore) and the phone, and now I think my phone might be totally bricked.
When I turn it on, there is nothing on the screen. It vibrates once, like it's trying to start, but nothing happens and the phone is otherwise unresponsive. I can try to boot into the bootloader (volume down + power) and that SEEMS to work, but the screen doesn't turn on then either. Occasionally, it will display the same rainbow pixels after "selecting" an option on the bootloader menu (I'm assuming). I've also pulled the SD card to insure it's not trying to read any PJ75IMG.zip.
I can't seem to get it to go into fastboot mode (single power button click after thinking I'm in the bootloader) and adb only shows the device as OFFLINE when I can get it to detect. It's hard to know what's going on without the screen.
Has anyone heard of this before? I probably ****ed something up but other than ending the ViperRUU early, not sure what. Thanks in advance, I very much appreciate it.
matt135353 said:
Hello all, and thanks in advance for your help. I don't know if all of this is relevant to what happened, but I'm including it in case there's some small clue.
My phone was an S-OFF running HBOOT 2.09. I have been running Deck's CM builds for a while now with no issues. Last week, I decided to update to the new firmware which included the new partition layout.
HTC's RUU executable did not work, so I used the two zip method in this post. I first renamed rom_01 to PJ75IMG.zip, placed it on the SD card, rebooted and installed, then did the same with rom_02. Loaded everything up, seemed great with the stock image. After verifying everything was working fine, I flashed a new recovery (2.7.0.0b, via PJ75IMG.zip as well), and installed the latest OmniROM (3/31) via recovery. I had some issues with the PA 0-Day GAPPs that were recommended (force close errors with Google Keyboard) so after reflashing Omni switched back to the 12/09 GAPPs in Deck's thread. Everything seemed great.
A few days later, after having the phone in my pocket, my screen turned into a rainbow of pixels. Here is what it looks like: http://imgur.com/9ef6F8z It still seemed to work, just the screen was always that rainbow.
Thinking it was an issue with the firmware, I tried to RUU back to a somewhat earlier stock by using ViperRUU 3.16.651.3. However, after going through the RUU process, it had gone about 30-40 minutes with no updates, so I thought it had crashed. I checked to see if that was normal, and saw that it was not and they recommended restarting the process. I restarted both the ViperRUU (couldn't find phone anymore) and the phone, and now I think my phone might be totally bricked.
When I turn it on, there is nothing on the screen. It vibrates once, like it's trying to start, but nothing happens and the phone is otherwise unresponsive. I can try to boot into the bootloader (volume down + power) and that SEEMS to work, but the screen doesn't turn on then either. Occasionally, it will display the same rainbow pixels after "selecting" an option on the bootloader menu (I'm assuming). I've also pulled the SD card to insure it's not trying to read any PJ75IMG.zip.
I can't seem to get it to go into fastboot mode (single power button click after thinking I'm in the bootloader) and adb only shows the device as OFFLINE when I can get it to detect. It's hard to know what's going on without the screen.
Has anyone heard of this before? I probably ****ed something up but other than ending the ViperRUU early, not sure what. Thanks in advance, I very much appreciate it.
Click to expand...
Click to collapse
This is a known hardware issue. Look here:
http://forum.xda-developers.com/showthread.php?t=2470296
It happened to me as well. I called Sprint and they replaced my phone for no charge.
Sent from my EVO using XDA Premium 4 mobile app
Ah, thanks for the link. I don't have TEP and it's out of warranty but I'll give Sprint repair a shot. Thanks!
Evolution_Freak said:
This is a known hardware issue. Look here:
http://forum.xda-developers.com/showthread.php?t=2470296
It happened to me as well. I called Sprint and they replaced my phone for no charge.
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hmm...I bought mine secondhand and am going to be running it on Ting, you think they would do that for me if it happens? :laugh:
matt135353 said:
Ah, thanks for the link. I don't have TEP and it's out of warranty but I'll give Sprint repair a shot. Thanks!
Click to expand...
Click to collapse
I have TEP but that never even came up. I never filed a claim. They originally wanted me to go to a Sprint store to have a tech look at it but I complained that the nearest store is an hour away. So they took my word, after explaining what was happening, and sent me a new (refurbished) EVO and then I sent them the old one in the package they provided with the new one. This was back in November of 2013 and I never heard anything else about it.
Sent from my Nexus 5 using XDA Premium 4 mobile app