Related
After a convoluted process and many mishaps on my part (I bricked it) my phone has a working, rooted and stripped down version of 2.3.6 on it. Which works as intended except the screen is now grainy and the colors are over-saturated. (side note: unfortunately I did not do a backup of the stock firmware-stupid I know)
I'm guessing this is a driver issue with the firmware or gpu because the pictures I took before I tried getting cyanogen on my phone now look very pixelated; almost like one of those cheesy after effects. I tried updating the firmware and it said I was current. Is there a way to update drivers? Do I have to find the original firmware for my phone (I looked on here the forum with the huge list of branded and unbranded and was at a loss)?
Also in my endeavor to attain the cm7 I tried rom manager which never worked even after getting the pre-rooted firmware. It will let me download the new clockwork but it does not appear to flash it and any attempt to install or reboot to clockwork doesn't do anything (gives prompts, I say yes, nothing happens). As a result of following the cyanogen wiki twice it says I have two custom firmwares and I cannot get into clockwork at all. I could the first time through before I bricked it but now I can't. Is there a way to remove the extra kernel?
The only reason I have a working phone is because of Odin. Is there a way to use Odin to install cm7 and would that fix the display issues or am I better off finding the stock firmware and hoping the display will default back to working?
Thank you in advance,
noob
http://forum.xda-developers.com/showthread.php?t=1313659
Branded? Unbranded?
There is only one variant of the I777 - AT&T Branded. Anything in the Development forum for the I777 will work on an I777.
It's not like the I9100 with a bunch of minor subvariants.
drmorbo said:
After a convoluted process and many mishaps on my part (I bricked it) my phone has a working, rooted and stripped down version of 2.3.6 on it. Which works as intended except the screen is now grainy and the colors are over-saturated. (side note: unfortunately I did not do a backup of the stock firmware-stupid I know)
I'm guessing this is a driver issue with the firmware or gpu because the pictures I took before I tried getting cyanogen on my phone now look very pixelated; almost like one of those cheesy after effects. I tried updating the firmware and it said I was current. Is there a way to update drivers? Do I have to find the original firmware for my phone (I looked on here the forum with the huge list of branded and unbranded and was at a loss)?
Also in my endeavor to attain the cm7 I tried rom manager which never worked even after getting the pre-rooted firmware. It will let me download the new clockwork but it does not appear to flash it and any attempt to install or reboot to clockwork doesn't do anything (gives prompts, I say yes, nothing happens). As a result of following the cyanogen wiki twice it says I have two custom firmwares and I cannot get into clockwork at all. I could the first time through before I bricked it but now I can't. Is there a way to remove the extra kernel?
The only reason I have a working phone is because of Odin. Is there a way to use Odin to install cm7 and would that fix the display issues or am I better off finding the stock firmware and hoping the display will default back to working?
Thank you in advance,
noob
Click to expand...
Click to collapse
Are you able to reboot the phone in recovery using ADB?
Its gotten to the point where nothing I try works. I managed to get cm7 installed and it got stuck in a boot loop. Flashed back to the stripped down version again. Everything that could go wrong has. For now I just want to go back to whatever firmware came with my phone out of the box. The startup logo was at&t so I guess I'll go for the branded version (which I can't find on here--its almost 3 am I apologize for my idiocy) and hope the screen issue is resolved.
Thanks again
defeated
drmorbo said:
For now I just want to go back to whatever firmware came with my phone out of the box. The startup logo was at&t so I guess I'll go for the branded version (which I can't find on here--its almost 3 am I apologize for my idiocy) and hope the screen issue is resolved.
Click to expand...
Click to collapse
Which you can't find? Someone posted the link to my return to stock guide in post #2 of this thread.
If you return to complete stock using Entropy512's Return/Unbrick to stock package, you will regain the AT&T boot logo instead of any custom boot logo. The phone will be just like it was when you first took it out of the box.
If you want the stock ROM plus root, Entropy has a package for that also. Just flash one of his packages with Odin, or use the One-Click downloaders for his package that are linked in my guides.
Update: You can also download all of these from my Download Repository.
Okay so I did the return to stock without root one click and that went fine. However the display is still not working properly. Solid colors are fine and I even went into the debug screen and tested all the colors. They were brilliant but any dimming or shading of two colors just looks wrong. The only thing that I can think of is the bootloader is wrong. It says my phone is a I9100 which it isn't. However I'm not sure why a bootloader would affect the display. Does the I777 have a different initialization process for the gpu? Or is the issue somewhere else?
drmorbo said:
Okay so I did the return to stock without root one click and that went fine. However the display is still not working properly. Solid colors are fine and I even went into the debug screen and tested all the colors. They were brilliant but any dimming or shading of two colors just looks wrong. The only thing that I can think of is the bootloader is wrong. It says my phone is a I9100 which it isn't. However I'm not sure why a bootloader would affect the display. Does the I777 have a different initialization process for the gpu? Or is the issue somewhere else?
Click to expand...
Click to collapse
That might affect it but I highly doubt it.
So do you have any idea what could have caused it? I tried searching the forums but I couldn't find somebody with a similar problem.
Where exactly does it say your phone is I9100?
It shows "Samsung galaxy s II I9100" before the at&t load screen.
drmorbo said:
It shows "Samsung galaxy s II I9100" before the at&t load screen.
Click to expand...
Click to collapse
The return to stock did not complete correctly. This screen appears after flashing a non-stock kernel with Odin/Heimdall.
Entropy512 said:
The return to stock did not complete correctly. This screen appears after flashing a non-stock kernel with Odin/Heimdall.
Click to expand...
Click to collapse
Yes. The very first method I tried was the heimdall from the cyanogen wiki. I've used various methods without success. However the last effort was to restore the phone and I used the one click stock without root. Was it supposed to restore the bootloader? Also I updated ota and the display works much better. The remaining discoloration/pixelation could have been there all along as I didn't wait long to put cyanogen on it (1 day) and I have nothing to compare it to.
drmorbo said:
Yes. The very first method I tried was the heimdall from the cyanogen wiki. I've used various methods without success. However the last effort was to restore the phone and I used the one click stock without root. Was it supposed to restore the bootloader? Also I updated ota and the display works much better. The remaining discoloration/pixelation could have been there all along as I didn't wait long to put cyanogen on it (1 day) and I have nothing to compare it to.
Click to expand...
Click to collapse
The return-to-stock-with-root shouldn't touch bootloaders - but it should have restored a stock kernel. IF you're getting the "yellow triangle" I9100 boot screen, the last thing flashed with Odin/Heimdall was NOT a stock kernel.
There is no yellow triangle. I used the exe from the link in the first response in this forum. In any case I'll throw a picture of the phone while turned off but charging tonight. The display issues aren't grave but they are noticeable and annoying. Do you know of an app that allows you adjust graphical/display settings? Maybe it would suffice.
I found information concerning my display issues. Apparently it's an issue with the phone. Its called black crush. My phone has this and oversaturated red. So shading details are pixelated and reddish.
http://forum.xda-developers.com/showthread.php?t=1124669
Also I noticed people repeatedly mentioning screen modes under setting>displays however my phone does not have this option. Also all of the mentions have been under the forum for the regular version of the phone not the AT&T variant. Is the AT&T version missing this option or am I blind?
drmorbo said:
I found information concerning my display issues. Apparently it's an issue with the phone. Its called black crush. My phone has this and oversaturated red. So shading details are pixelated and reddish.
http://forum.xda-developers.com/showthread.php?t=1124669
Also I noticed people repeatedly mentioning screen modes under setting>displays however my phone does not have this option. Also all of the mentions have been under the forum for the regular version of the phone not the AT&T variant. Is the AT&T version missing this option or am I blind?
Click to expand...
Click to collapse
AT&T version is missing screen tuning unless you run a custom ROM that readds it like Serendipity VIII or Unnamed.
Okay cool. So I used the one click with root and the wifi is broken and it won't let me do an OTA. however I had previously used the one click without root and I was able to OTA and that solved the broken wifi. What would be the easiest way to fix the wifi?
Flash cwm>factory restore/wipe (I don't have cwm and I remember the cyanogen wiki way to get cwm messed up my soft buttons--two didn't work anymore)
Or
Flash the 12/21 dd kernel (I did originally try this route. However Odin didn't recognize the kernel. I even repackaged I with just zImage. Still nothing.)
Thank You again Entropy
DrMorbo
Sounds like there is something broken about the oneclick... Try flashing the return-to-stock package with Heimdall. Heimdall also lets you flash kernel zImages without packaging into a tar.
However Heimdall needs its own driver mojo on Windows - I can't really help you with this, I've flashed a device from Windows only once, and that was the Tab 10.1 because Heimdall won't talk to it.
Nevermind. I tried the update a third time. It decided to work (48 hours later). Everything works. Wifi works. The screen is better (I used voodoo screen tuning to greatly diminish the black crush and red saturation. I can finally customize my phone now. Any nifty apps you know of Entropy? (Regular or root needed)
Thank you again Entropy,
DrMorbo
Hello guys, you'll have to excuse me for the wall of text, but it is necessary to fully describe my ordeal.
I bought an used atrix about 4 months ago from ebay (and i'm now deeply regretting it, too many issues). When I first received the phone I was unable to hear callers, even though they could hear me (badly, but could). I resolved that the easiest way possible: I bought a headset. Even with that issue and since it was impractical for me to return the phone because I'm in a different country (customs alone were over $100) I continued to use it. I flashed CM7 and ATT N_.37, flashed TWRP 2.1 and I enjoyed my phone for a couple months (even with the audio issue). Then one day, I went to bed with my phone on a full charge and in the morning I found it turned off. I tried to turn it back on and nothing happened. I thought maybe the battery had been drained by something, because I had left 3G data enabled. I tried to charge it and nothing happened, except the phone started to get really really hot in the lower part so I decided to disconnect it. I tried again a couple hours later and same thing happened. Next day I hit the power button and was able to enter android recovery. I wiped and factory reset, reinstalled cm7, gapps and radio and phone turned on and showed around 60% charge and it seemed fine and then all of a sudden the led started glowing light blue. Then the phone shut down and started to boot loop. I took off the battery, let it rest a while and then when I turned it back on everything worked fine (still, minus audio). That was two weeks ago. Today, it started to do the something similar but worse. Blue led flashing and boot loop are there but if I enter recovery I can't find anything in the sdcard, and if I place a microsd in the slot it isnt recognized. Also, led is flashing blue even while in recovery so I doubt it is a CM7 issue.
tl;dr My phone is dead. Can it be fixed or do I now own a $250 paperweight?
Try to flash your phone with your stock firmware using rsd lite
here a list of firmwares ... http://forum.xda-developers.com/showthread.php?t=1125944
WARNING! : flash it with YOUR stock sbf !!!
isn't that dangerous? from what i understand with this post it seems as if it isn't advisable to use an sbf on an unlocked bootloader.
not.a.troll said:
isn't that dangerous? from what i understand with this post it seems as if it isn't advisable to use an sbf on an unlocked bootloader.
Click to expand...
Click to collapse
Only if you're downgrading. It can work if you do it properly, but it's not recommended. Fruitcakes are the more foolproof way to go.
well i chickened out of the .sbf flash and just tried the moto-fastboot stock restore available elsewhere. while everything seemed to flash correctly i am still bootlooping/shut down. also, light blue led still there and sometimes i get stuck on bootscreen and can't even enter recovery. guess ill have to take it to a shop and see if something can be done. else S>atrix 4g for parts.
D:
hello to all
my atrix 4g originally was in firmware 4.5.141.MB860 ATT, i unlocked the bootloader succesfully and flash CM7... but for reasons of life (silly excuse jejeje) i want to take it back to the original fw... with this files: Blur_Version.4.5.141.MB860.ATT.en.US and 1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf.gz can i go back to stock fw? with this stock files i lose the boot unlock? is this a safe method? and what is the safest?
thanks for your help and greetings from Colombia (and sorry for my bad english)
Flash the latest sbf for your phone. I've done several with no problems. Yes, you do lose the unlocked bootloader though.
This will return you to stock. I used the same files.
not.a.troll said:
well i chickened out of the .sbf flash and just tried the moto-fastboot stock restore available elsewhere. while everything seemed to flash correctly i am still bootlooping/shut down. also, light blue led still there and sometimes i get stuck on bootscreen and can't even enter recovery. guess ill have to take it to a shop and see if something can be done. else S>atrix 4g for parts.
D:
Click to expand...
Click to collapse
I also have been through several phones with this issue. Although you can flash the sbf with no troubles, that is really only good for sending it into warranty. From my experience, this is a hardware issue, and flashing the stock sbf doesn't solve the problem. If you do not have warranty, a repair shop is your best bet.
Good luck.
Repy
x-geo said:
hello to all
my atrix 4g originally was in firmware 4.5.141.MB860 ATT, i unlocked the bootloader succesfully and flash CM7... but for reasons of life (silly excuse jejeje) i want to take it back to the original fw... with this files: Blur_Version.4.5.141.MB860.ATT.en.US and 1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf.gz can i go back to stock fw? with this stock files i lose the boot unlock? is this a safe method? and what is the safest?
thanks for your help and greetings from Colombia (and sorry for my bad english)
Click to expand...
Click to collapse
Hi,
Yes you can go back to your stock rom. Another yes, you will lose all your files and your bl unlock too. You have to start everithing from the begining. this is a safe method if you flash your own rom.
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.
Hey good people, after an entire day of trying to tinker with my phone, I soft bricked it.
It started because I wanted a theme, that required CM. So I've browsed a lot of threads and tried some things, and a couple of restarts and factory resets later, it went downhill.
So, P760 20i, running stock 4.1.2, after the last factory reset, I rooted it using this tutorial. I did that in order to install this CWM, to further install CM 10.1, the one I needed. After I did all that and finally booted up in recovery mode, I wiped user data as per instructions in the last link, and when trying to install the ROM, an error felt the need to interfere with my plans. So that's how I ended up with a phone that, if I don't take 3 more pills now, I'm gonna give to the dog to chew on.
It powers on, passes the LG logo, after the screen goes white and it says Under Coding...and the only option is a button to Reset Phone (it's basically a restart phone). A pop-up immediatly appears, saying that com.android.phone has stopped. After I click OK on that it asks for my SIM PIN, it accepts it, and briefly shows a weird, low-res old-looking Android lock screen and then back to the blank screen with another pop-up, asking me about Mobile Networks. That's about all the interaction there is. Click Home button does nothing, clicking Back button just swipes the screen back on the screen, and Menu does nothing. Rebooting from that button is again useless.
That CWM is still there, I can access boot in recovery mode, but to no avail. I've wiped cache, wiped Dalvik Cache, rebooted and nothing. I've tried hard reset with vol down+home then power for 3 secs, release power but still hold down vol down+home until the friendly robot appears, but the result is the same, nothing happens.
During the day I went through more methods, I had a lot of trouble with fastboot which I couldn't get to work.
My question is, based on what I told you, can you instruct me in the right direction ? Also, now that this happened and if it's possible to fix it, could it be fixed with CM installed automatically, or will it be a stock reset and then again back to the drawing board ?
If you need any more details, I'll try to provide, I didn't do much after the last factory reset except for what you see here.
@nerazull Welcome to the forums.
I guess first things first.... With this device you cannot flash any custom roms without unlocking the bootloader first. You cannot flash any custom roms with this version of CWM recovery either and there is no work around for the bootloader such as loki.
When you installed CWM did you make a nandroid backup? I hope so.... this is always, always the first thing you do before making any changes to the system.
If you did then just boot into CWM and restore your nandroid backup and that should resolve your issue.
If you didn't perform a nandroid backup then you can try and flash one for your specific device (p760 jb) from cmahendra's nandroid thread here - http://forum.xda-developers.com/showthread.php?t=2136204
If the nandroid backup doesn't work then you'll have to follow cmahenda's unbrick guide by either using the offline or online flash here - http://forum.xda-developers.com/showthread.php?t=2085344
@xdrc45 Well, I didn't perform any kind of backup, I usually don't (call me an optimist ...I'm actually sad now )
I woke up earlier and started reading the second topic you posted. I'm thinking about trying that and not the first one, since I see the first one MAY have some personal data, I would prefer a stock option.
The question is, does it matter that it was 20i before, must I find a 20i now, or can I take any other one ? Or any other one respecting country/provider ?
Also, the first one says that device must be rooted. Is it still rooted now, with the method I used and after the incident ?
I also tried a couple of ways to unlock the bootloader yesterday, best result I got was a phone restart but nothing different. I also couldn't find a way to tell if the bootloader was unlocked or not.
PS: Thanks for the welcome
The nandroid backups are clean as in stock, rooted and all personal information is removed.
Personally i would try the nandroid backup firsr as that would be the fastest way to restore your device. Take a total of 5 min to try and yes the device should still be rooted.
My L9 had the same problem after I installed the L9 Recovery, I booted into CWM and made a backup and then when I rebooted to the OS I got the error Encrypting - Reset Phone. Booted back to CWM, restored my backup and everything was fine... turned out to be a problem with BusyBox.
For the kdz you only need one that is for your model# and that is the same version of OS that came installed on the device (ics or jb) for the offline flash.
When you successfully unlock the bootloader you will be taken to a verification screen to actually unlock it. Its a huge pain to achieve. What you can do one you restore the device and make a nandroid backup is
1. Install a launcher lile Apex or Nova
2. Install xposed framework
3. Inatall gravity box xposed module
4. Install xthemes xposed module
All the above allow you to make custom changes from the status bar to kk themes
Ok, I will take your advice and try with the backup first.
And btw, that's the same error I get, I said "Under Coding" because that's the word-by-word translation from my language, didn't think of "Encrypting"
In regards to the theme part, that's what I originally did. I found the same version of the theme I wanted as an XTHEME. I followed the instructions of the developer on the play store. I rooted using the same method I mentioned in OP, got the XPOSED framework, got XTHEMES Engine, got the theme, but it wasn't working as intended. The theme only changed a couple of icons and the battery icon, it was like 20% of what the screenshots on the play store were showing. It also had something resembling 256 colors in the drop-down menu.The comments and rating of the theme made me think that the problem was on my end.
I found the same theme that had another application method, and required one of these: CM10.1, CM10, CM9 ,AOKP and Paranoid Android, so I decided to try this one with CM10.1, maybe it wouldn't glitch.
Sadly, there were no reviews of the theme for my device, so I couldn't tell if it was a problem with this specific device+that theme.
I can't post outside links due to being new on the forums, but the themes I'm talking about can be found in the Play Store, search term "Deus Ex Android Blue", the first two should be Custom ROM one and XTHEME one. Maybe you have some insight.
PS: I see that you also have this device, albeit 769, and it's the only one with stock ROM on it. I'm not a very experienced user, should I still pursue bootload unlock+custom ROM ? Is it too much of a hassle ? I'd like to do it and not just for the theme (it's the main reason though), if I fix the current problem.
I found 2 methods that used adb/fastboot for unlocking, got Android SDK, adb worked fine but I couldn't do anything about fastboot. I also tried that method (I think "Lelus"), where you had to remove battery, plug in phone like that, "catch" the device and manually install it's driver, etc, but I didn't fully understand what to do there. I only did the first part. There was another link to a tutorial about this method, spanning 3-4 methods, and I saw it's pretty random, and my USB cable is also not very reliable, if I move it by just a bit it may interrupt the connection.
LE: I'm sorry I can't quote all the methods I tried yesterday so you can better respond to me, but I can't even remember all...at one time I had 20+ tabs on the subject, bookmarked a few, tried some, ran into scam websites claiming they had a good method, etc.
And one last thing (sorry for this wall of text reply ), you said this CWM I got can't install Custom ROMs, but can it flash the backup I need ?
@nerazull
See the thing is that using something like xposed framework modules, is that it literally makes changes to the framework and the phone just might not like one of those changes. Sometimes it won't apply all the way across the system and you may only end up with only 20% of the theme working because some of the themes were originally cm10+ themes ported to xposed and may have been developed for a specific device and isn't a 100% compatible or a bad download. Usually if it causes any problems you can just uninstall the module and reboot and everythings fine, if not that's where a backup comes in handy.
I haven't tried to unlocked mine yet, just because I really haven't had the time to spend a day flashing kdz and dealing with the inverted touch screen. I plan on it one of these days, I've already downloaded everything for the device to do it and even have fastboot already set up just in case. So yes you could say it is a pain to unlock the bootloader, but I'm pretty sure more people have been more successful at unlocking on the p760 than on other variants.
Fastboot is actually pretty easy to set up. Open device manager and open lelus fastboot script, minimize the fastboot script windows so you can see them both fully open on the screen. Turn off the device and remove the battery and keep it screen down on a flat surface, plug your USB cable into your PC not into the device yet - select #1 for fastboot - push any key to continue - quickly plug in the USB cable into the device and and put the battery back in - on device manager you will see "unknown device" pop up and right click on it quickly and select update driver - select manually install the driver - then navigate to where you have the fastboot diver folder and click on "usb _drv_windows" and install - once that's done repeat the process again to install the drivers again.
Yes that cwm version will flash the nandroid backup and mod zips.
One other thing you can try is apex launcher, that's what I'm using. With this you can change a lot of the launcher settings, change and edit the size and image for icons and folders to adding themes, I'm using kitkat HD multi launcher theme through apex and its really nice and clean.
I haven't tried it yet but you can also try themer beta
@xdrc45 Well, I managed to install a backup from your first suggested method and it worked fine. I also tried Nova Launcher for a bit, bit I just got my mind set up on that theme and it's not going away I've also managed to install the fastboot drivers using the Lelus method (don't know why, but your instructions here made much more sense to me then the other 2 I found )
I decided I still want to pursue unlocking the bootloader and installing CM 10.1, I really want to check it out.
Will this BL unlocking method work for me ? I couldn't find any mention of 20i in the thread. And if yes, can that CWM flash a custom ROM, unlike my current one ?
And of course, thanks for your help so far. Really appreciate it.
@nerazull Hey you're welcome.... glad I could be of help.
I don't think v20i is unlockable, you could try and issue the unlock command but I'm pretty sure you will have to flash to a European open kdz like v20b and then follow the tutorial and yes that CWM will work.
You could also use markolino631 Tool box to try and unlock the bootloader. It issues the unlock command and can flash CWM for you easily ... There's a CWM for cm10 and the new version has one for cm11.
http://forum.xda-developers.com/showthread.php?t=2190326
I'm surprised you're going for cm10.1 instead of cm11
@xdrc45 Well, I did try to unlock 20i with the method I mentioned but it didn't work, I decided to flash v20b europe open. I flashed v20b Europe Open (just got the kdz from there, didn't follow those steps, didn't go back to ICS) using offline method (had to hard reset after because I was stuck in a bootloop, it worked fine after). I've got the fastboot drivers installed like I said before, I've checked and they're installed correctly. I've also installed/uninstalled the LG drivers twice, once offline to make sure Windows doesn't search for updates, and I still can't unlock bootloader. I've tried both unlocking methods aforementioned and the phone just reboots normally.
I've made these screenshots of what my Device Manager looks like, just for the sake of being thorough.
In phone, Software Version now says P76020b. Could the problem be here, shouldn't it say EUR-something ?
And I'm going for CM 10.1 for that theme, if it works and I like it I'll make a backup and get CM11 and see if they're compatible or not and move on from there That is, if I can get this bl unlocked.
LE: In the [2in1GUIDE] there's this post that mentions BusyBox. My device is not rooted after the kdz flash and obviously I don't have BusyBox. But that wouldn't make sense since it's not a pre-requisite in the tutorial and the tutorial is also meant to root.
There's also this...and this confuses me even further + other random occurrences.
Is it safe to assume that I should start experimenting ?
Yeah these L9's can be a pain in the @ss, but the nice thing is you can recover it from almost anything.
Just keep trying and don't give up on it. I've seen where some people have tried multiple times to unlock, like 20 times without success and then they try again and boom, unlock success. Make sure you have and are using the phones service and wifi. Make some calls and watch some videos or a movie on it.... You need to receive the token, this is the whole reason for waiting an hour before issuing the unlock command, but it may take longer than an hour or two to receive it, like some waited 10 hours and then the unlock worked.
Unfortunately there is no one set way to unlock and everyone has had different experiences and tried different techniques to get it to work. All you can do is, as you said "Experiment" and exhaust all options.
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