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.
Related
Ok so a couple days ago in preperation of selling my evo 3d , i flashed a new rom of which i cant remember , i also beleive i flashed silverneedle kernel through the gpl tool app. Ever since no matter what i do , i cant get past the white HTC screen , it just reboots from there . Ive tried the superwipe tool and it seemed like it was going to work , but nothing . Ive also looked over several threads on here and no one seemed to have had an answer, thus im making my own thread. Im currently trying to flash warm 2.3 rom. I even thought maybe it was a bad transfer to the sd card because the sd card was acting funky when the rom was being transfered to it in my galaxy s2 so then i just downloaded it dirtectly from dolphin browers to the root of the sd card right from the galaxy to see if that was the problem. Still nothing , just the htc screen. Anybody have any idea how to fix this? I just want the phone back to stock so i can sell it , ugh. O and im on HBOOT 1.5 with the official HTC unlock and S-on.
I'm in the same boat. Fairly new evo 3d with hboot 1.5 rooted through htc. I've been flashing several roms over the last few days all with success, found I like Xplod XE from team nocturnal the best, nice and fast. What i found was that the kernel never changed, as I had read would happen with s-on. After doing some reseach and trying a few things I ran into your problem. Now no matter what or how i flash i'm stuck in a boot loop at the white HTC screen. The last kernels I've attempted to push were Tiamat_E3D-v1.1.0-Sense and silverneedle-test5. I've tried various combinations of wiping both caches with and without factory reset/system wipe as well as flashing several roms with success, still stuck with the boot loop. Flashed all roms through TeamWin Recovery and pushed kernels through clockwork recovery via fastboot/cmd promt.
Darthdaddy said:
.... and pushed kernels through clockwork recovery via fastboot/cmd promt.
Click to expand...
Click to collapse
Not sure about this.
But when flashing kernels, it happens through fastboot. You shouldnt see clockwork anything.
I dont quite understand adb or how to push things through command prompt so im not even going there but i have tried the RUU method and i keep getting an unknown error at the end of things and then nothing happens. Through all of this i still have recovery , which is good , but its becoming useless because nothing is sticking. Previously the gpl app let me flash kernels flawelessly. I had a cracked screen and a replacment put on. I take it home , power up the evo and notice that its acting really buggy and funny , so i flash a new rom and kernel and am now in the never ending bootloop mode. Its getting really frusuturating. Im about to try re locking it and see if that works. I dont even care if i lose root , just want to go back to a fresh phone.
carnivalrejectq said:
I dont quite understand adb or how to push things through command prompt so im not even going there but i have tried the RUU method and i keep getting an unknown error at the end of things and then nothing happens. Through all of this i still have recovery , which is good , but its becoming useless because nothing is sticking. Previously the gpl app let me flash kernels flawelessly. I had a cracked screen and a replacment put on. I take it home , power up the evo and notice that its acting really buggy and funny , so i flash a new rom and kernel and am now in the never ending bootloop mode. Its getting really frusuturating. Im about to try re locking it and see if that works. I dont even care if i lose root , just want to go back to a fresh phone.
Click to expand...
Click to collapse
The info here should fix you up. Lock the phone before you run the RUU.
Edit: Also, I never found the need to push files from adb. I just put them in my c:\android-sdk-windows\tools folder. If they need to be on the sdcard, I just drag and drop.
Followed directions from another site to work through command prompt and get into recovery, pm me for the link. Made sure i had my rom file on my sd card, did a factory reset then manual install of rom via clockwork then rebooted. Went through fine.
tailsthecat3 said:
The info here should fix you up. Lock the phone before you run the RUU.
Edit: Also, I never found the need to push files from adb. I just put them in my c:\android-sdk-windows\tools folder. If they need to be on the sdcard, I just drag and drop.
Click to expand...
Click to collapse
Do i have to have adb setup to relock? i typed the fastboot oem lock into command prompt and nothing happened. i am on a different new computer than i was when i unlocked the phone in the first place.
carnivalrejectq said:
Do i have to have adb setup to relock? i typed the fastboot oem lock into command prompt and nothing happened. i am on a different new computer than i was when i unlocked the phone in the first place.
Click to expand...
Click to collapse
Youll need to have all the necessary files/programs which I imagine are fastboot, adb, device/android drivers...
Ok ive relocked the phone but RUU is not working , i still keep getting an error, and then when it gos back to the bootloader it says "Hboot version is Older!" and "Update Failed!" This time though RUU makes it a little further about a quarter of the way in where it says "sending" , before it does this , though. I never end up actually getting a progress bar on the phone or the little exclamation points. Im totally lost lol.
carnivalrejectq said:
Ok ive relocked the phone but RUU is not working , i still keep getting an error, and then when it gos back to the bootloader it says "Hboot version is Older!" and "Update Failed!" This time though RUU makes it a little further about a quarter of the way in where it says "sending" , before it does this , though. I never end up actually getting a progress bar on the phone or the little exclamation points. Im totally lost lol.
Click to expand...
Click to collapse
Try this. Watch the vid, download the files.
Frankly, you should be able to run the RUU, so long as youre 'relocked'. Thats how Ive done it, multiple times. Hopefully we can get you back to stock.(Which we can)
Whew , i finally got it! The last part there was my erorr for using an older RUU , i didnt look close enough and i thought i was using 2.08. So i dled the 2.08 one and now its all good to go. Haha literally been doing this since 930 am. Thanks for the help guys , btw.
I used Hansoons all in 1 toolkit to root my rezound, I unlocked the bootloader, loaded the twrp recovery and flashed supersu. Now when my phone boots all I get is the bar across the top with the signal strength, battery level, and time. What can I do to get my phone to function again??
I had previously unlocked with the toolkit and ran a few root apps and removed some blotware. I then relocked and everything was working fine until I tried to root it again.
Are you s-on then?
Did you RUU first? Might want to do that since you had made changes before. That will bring you back to nice and fresh stock.
The latest one is here:
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
IF YOU ARE S-ON... you can relock, RUU and then flash the recovery again and get root and see if that helps.
If you are s-off then await someone else's answer, but I think you run the RUU without relocking.
Ya, s-on. That looks like what I need to do, just wasn't sure what to call the process and search for... Unfortunately with my 4g internet via my phone gone, I gotta sit here and wait on the download to complete on my slower internet. Greatly appreciate the fast response!!!!
disdard said:
Ya, s-on. That looks like what I need to do, just wasn't sure what to call the process and search for... Unfortunately with my 4g internet via my phone gone, I gotta sit here and wait on the download to complete on my slower internet. Greatly appreciate the fast response!!!!
Click to expand...
Click to collapse
The answer isn't always RUU. Running an RUU will reverse everything that you just did. You will lose root. You're phone will be wiped. And you'll have to relock. What I recommend trying first is rebooting into recovery. Twrp in this case for you. You can do this by getting into bootloader (power and volume down on boot up) and hitting recovery. Once in recovery try wiping cache and dalvik. Reboot. If that fixes it... Cool. If not.. reboot into recovery again and wipe data. This time it should almost certainly work. You won't have root. But you will be stock.
Flashing a custom ROM will fix your problem as well.
There is almost nothing that you can screw up to the point of HAVING to RUU. Most people only use an RUU to update firmware and radios when new versions are released
Sent from my ADR6425LVW using Tapatalk 2
GetRipped said:
The answer isn't always RUU. Running an RUU will reverse everything that you just did. You will lose root. You're phone will be wiped. And you'll have to relock. What I recommend trying first is rebooting into recovery. Twrp in this case for you. You can do this by getting into bootloader (power and volume down on boot up) and hitting recovery. Once in recovery try wiping cache and dalvik. Reboot. If that fixes it... Cool. If not.. reboot into recovery again and wipe data. This time it should almost certainly work. You won't have root. But you will be stock.
Flashing a custom ROM will fix your problem as well.
There is almost nothing that you can screw up to the point of HAVING to RUU. Most people only use an RUU to update firmware and radios when new versions are released
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Well it's not like one should avoid RUU like the plague, geez.
As to wiping your phone, flashing a custom ROM can/will do that as well. Relocking and unlocking again are really no big deal, just a couple commands. Rerooting is simple. It's really not as bad as you make it out to be, imo. And in fact, there's a ton of threads suggesting running an RUU to solve issues and get a fresh start.
I like to run an RUU since it brings you back to a nice fresh stock install, and yes, it will update if the phone is not up to date. In this case to global, which is a bonus.
feralicious said:
Well it's not like one should avoid RUU like the plague, geez.
As to wiping your phone, flashing a custom ROM can/will do that as well. Relocking and unlocking again are really no big deal, just a couple commands. Rerooting is simple. It's really not as bad as you make it out to be, imo. And in fact, there's a ton of threads suggesting running an RUU to solve issues and get a fresh start.
I like to run an RUU since it brings you back to a nice fresh stock install, and yes, it will update if the phone is not up to date. In this case to global, which is a bonus.
Click to expand...
Click to collapse
Oh hai there.:angel:
disdard said:
I used Hansoons all in 1 toolkit to root my rezound, I unlocked the bootloader, loaded the twrp recovery and flashed supersu. Now when my phone boots all I get is the bar across the top with the signal strength, battery level, and time. What can I do to get my phone to function again??
I had previously unlocked with the toolkit and ran a few root apps and removed some blotware. I then relocked and everything was working fine until I tried to root it again.
Click to expand...
Click to collapse
It sounds like you just need a new launcher. If you're getting to that point are you able to pull it down and see the notification area?
If yes then you could use Droid Explorer to push another launcher to the phone.
If not, yeah you maybe looking at starting over. Have you tried using a different recovery? I know personally I've had issues with every launcher except for Amon Ra.
I ran RUU, and once reset to stock breezed through the process of rerooting. Unfortunately had that done before any of the other replies, because it would have been easier to just do the resetting. But I got into the mess while trying to straighten out the issue of my dialer and people app disappearing so just fully going back to stock ensured I got the entire mission accomplished. And at the point it would boot to, you couldn't pull up the notification window so a new launcher wouldn't have fixed it.
Atleast I learned a bunch through the process!!! Just getting into rooting and customization, took the first step and rooted and kinda figured out how things work. Once I figure out a little more and decide which ROM I want to try, I'd like to try a custom ROM. All stuff I'm familiar doing with computers just gotta figure out exactly how it all works on phones....
Glad you are back up and running! Sorry if my method was more involved/time consuming.
I would suggest that before you flash a custom ROM you make a nandroid of your stock set up. Then you can always flash back to that if you don't like the ROM or run into issues and avoid troubleshooting or RUUing just to fix something.
It's a good safety net and a good habit to always have a nandroid to go back to in case of issues. I usually keep one handy of stock and of any ROMs I like, and always make one before flashing a new ROM or even a theme for a ROM.
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
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
I thought you guys might find this amusing, and hopefully it will help some people that get into a similar situation as myself. First, a little background - I rooted and installed Alliance Rom years ago back before the bootloader was unlocked. This worked amazing for me for a long time but I've recently had some weird issues with my phone so I decided to do a factory reset.
I went into settings, clicked factory reset, and then my phone got into a boot loop on recovery. I remember from before I had to do a regular boot then click recovery at the prompt instead of doing the factory recovery so I did that.
Instead of doing a normal wipe, I wanted to wipe everything on my phone and start from scratch so I did the full wipe (in what I think was TWRP or safestrap or whatever). When I went to reboot my phone it had a message like "are you sure? there's no OS installed" and I clicked ok. Well now I couldn't get the phone to boot into anything except download mode so at least I can use Odin.
I'm frantically searching google to try and find ways to install some sort of recovery so I could load AllianceRom again since I still had the zip file for it. Eureka, I found TWRP for my phone! I tried to flash TWRP through Odin but that doesn't work because my bootloader wasn't unlocked.... I remember this from last time ... all of the places I found online to install any sort of recovery required the phone to be booted into android.
So I'm clicking around and someone has a recovery randomly posted in a thread so I install it thinking, what the hell, what's the worst that could go wrong. So I install it through Odin and boot into normal recovery and I get this message saying my phone has been tampered with and to go to a verizon store immediately! Oops... upon further investigation (looking at the download screen), I tripped the knox flag... oh well, it's not like my phone is in warranty anymore (I got it on release day).
I search around looking for what I should do next and I found a thread that talked about being on complete stock, rooting, then unlocking the bootloader. I download all the files I need (newest firmware here - https://www.sammobile.com/firmwares/galaxy-note3/SM-N900V/ and thread here - https://forum.xda-developers.com/ve...guide-ob6-of1-root-bootloader-unlock-t3439010) to go back to stock and flash in Odin. Actually I didn't download from sammobile.com because it was downloading too slow so I just googled the file name and found it somewhere else faster, go figure.
Everything seems to be going ok then all of a sudden FAIL in Odin... Ahhh what the heck do I do now? Try again obviously! Second try works woo hoo! Phone start booting up, things are looking good!!! hooray!! But wait... it's taking forever to start and it's stuck on the Verizon logo... uh oh... taking way too long to boot up so I pull the battery and try again. Boots right in saying that android is upgrading so I think I'm finally in the home stretch here.
I try to run the ArabicToolApp for Root but I installed the latest firmware which isn't supported DAMN IT! Downloaded the correct firmware (OB6!), flashed in Odin, same problem before where it was stuck on the red verizon screen, pulled battery, rebooted, finally time to get root!
Phone finally boots into OS and I get a popup "unfortunatley com.google.process.gapps has stopped" great... and it keeps coming up over and over again after I hit ok... just my luck! Reboot again to see if that fixes the issue. Seems weird that I didn't have to go through all the initial setup stuff I did on the other version I installed... hmm... or maybe it was because I pulled the battery on the red verizon screen? Whatever. I somehow manage to get to options to do a factory reset and I let the verizon screen stay on a while this time. I'll go take my contacts out and give my wife some love while I wait
Come back and the phone is at the setup wizard, this is good news. Enabled USB debugging, installed root, done! Thank god!
Next I want to unlock the bootloader. I follow the steps here which aren't very clear (I'm guessing on purpose for novice computer users) - https://forum.xda-developers.com/ve...l/official-note-3-verizon-bootloader-t3359370
1. I installed eMMC from the play store to make sure my CID started with a 15, it does so I know I'm good to use the hack.
2. I installed both files in the unlock kit (adb and driver setup)
3. Fired up adb, navigated to where I had unlock_n3, and ran through the first part of the code once, reboot my phone, checked that the CID was the developer CID, and then ran the second part of the code three times before it worked
I verified the bootloader was installed correctly by trying to install TWRP through Odin, which worked!
I'm going to try out Jasmine Rom since it's a popular one that is on 5.0. My SD card only showed 30 megs free or something like that, so I formatted it from within android and copied the zip file over and installed the Rom through TWRP. Rom installed just fine, so I did one last factory reset which worked great and I think I'm finally good to go!
If you have any questions or run into any issues feel free to reply here and I'll try to help as much as I can.
Glad it worked out for you in the end.
From making a few mistakes I know that sinking feeling "oh no, what have I done?"
FWIW, the bootloader unlock method (in principle) works from nearly ANY ROM which is rooted - so, you would have saved yourself a bunch of time if you had started with that before you wiped the Alliance ROM. So long as you have root and a CID value that starts with 0x15, you just need root privileges - no need to return to stock and re-root.
(The "in principle" part is that there were several bugs in the "safety checks" portion of the unlocker binary that were sensitive to the OS revision, so you might have to search through the unlock thread to find a version of the unlock binary that is compatible with whatever rooted ROM is on the phone when the unlocking is attempted.)
good luck
PS The AryaMod ROM (w/ phantomOne kernel) is pretty solid - Marshmallow w/ S-Pen apps, too! As with any other dev ROM, there are a few sharp edges, but mostly everything works (except NFC).
.