Help flashing recovery... - T-Mobile LG G2x

Hi guys, I've had my G2x for a while and I am just running stock GB that I got via the OTA update. My phone is rooted with the UnlockRoot program, but other than that, I have no recovery or anything flashed and I've never used nvflash.
I've tried searching through the stickies and I can't seem to find any simple guide to flash the recovery with NVflash. Can someone tell me how to do this or point me in the right direction? Thank you!

http://forum.xda-developers.com/showthread.php?t=1056847
Sent from my LG-P999 using XDA App

Thank you!! Any reason to use CWM 4 over 5? Or should I just go with 5?

All right I must be a total idiot here but I got CWM 5 flashed and it seems to work except for one thing. The volume buttons move the selected menu item up and down, but what do I press to select an option?? All the soft keys seem to either make a black screen with a hat appear or they move the selected item.
For the life of me I can't seem to make it actually pick an option and I feel like an idiot, lol...

userno69 said:
All right I must be a total idiot here but I got CWM 5 flashed and it seems to work except for one thing. The volume buttons move the selected menu item up and down, but what do I press to select an option?? All the soft keys seem to either make a black screen with a hat appear or they move the selected item.
For the life of me I can't seem to make it actually pick an option and I feel like an idiot, lol...
Click to expand...
Click to collapse
Lol the soft buttons do actually do stuff but just use hardware keys. Power to select.

Related

Ran Flash-SPL and Unlock Radio - Pixelated Boot?

Hey guy,
Did I just brick my new Tilt? I downloaded the KaiserUnlock took with the nifty 3 steps button and ran the first two; after restarting from step 2 - after the AT&T bootscreen it's all just pixelated crap. It's obviously alive and active-sync's but I can't use it.
Can I recover from this?
Thanks!
Jeremy
Did you read the textbox that popped up on your screen before clicking the ok button? Because I think that will have your answer.
Ummm
The one that said are you sure? I can't do a hard reset because I can't read my screen to touch anything (and I think I need to for the hard reset?)
Ah Ha
OK, Apparently my fat fingers just had a hard time with the soft keys. Leave it to the fairer sex
Jeremy
Well..
ok the hard reset worked - it reloaded all the settings and then after it was done customizing everything it booted back up into pixel land?
Well
anyone? I'm frantic here
triksterut said:
The one that said are you sure? I can't do a hard reset because I can't read my screen to touch anything (and I think I need to for the hard reset?)
Click to expand...
Click to collapse
No. The one that said you may need to upgrade to Windows Mobile 6.1 before continuing....
I'm assuming that you're using Olipro's kit. You really might want to read through that thread.
Thought about that
But I can't upgrade anything; it won't even active synch after the radio upgrade?
put your device in bootloader and flash from there
How do I force it into boot loader mode? Is there a keyboard combination?
Jeremy
why do you even jump straight into doing this without doing any research first??
http://wiki.xda-developers.com/index.php?pagename=HTC_Kaiser
look for kaiser resets, and whatever questions you have next, just read the upgrading section.
the straight answer
the straight answer is hold down power key and camera press reset button on bottom with stylus and hold to side keys till 3 graidents. plug in and upgrade to a windows mobile 6.1 rom. i did the same thing because i was rushing... sometimes you have to learn the hard way to read before you leap.
Heck I know that before I did anything that would have royally mucked up my $400 phone I wanted to make sure that I read everything I was going to do to it .... twice.
Bootloader
* Press and hold the Camera button
* Using a stylus, press and hold the soft reset button at the bottom of the phone
* Release both buttons once the bootloader screen appears
From wiki
PS Sorry, I did not read until the end of the tread.
Press and hold the camera button, then push the stylus into the reset hole near the USB connecter, while still holding the camera button.
*edit* Oops, missed the fact there was a page two, bit late on the details there..

Strange incident with CWM

hello, yesterday i was changing rooms and i was wiping everything trough cwm 5.0.2.3 carebear.jrodd.
After wiping i went to choose zip and then i was sent back to main menu, i could choose any option from main menu, but behind options was waiting for me, tiny android fella with open box and some sort of a arrow sign.
I tried at least 15 times to get past that android fella and his freaking box with arrow jumping out of it , but i could not.
i could use nexus s soft buttons and at the bottom of screen was message saying "back button disabled".
i had to remove battery{ i didnt know what to do/i didnt actually have any other options, that i knew about}, then i powered back in to CWM and flashed rom.
everything works fine since then.
did any of u knows what happened?
i flashed lots of roms and i always trying to do everything up to code, but something like this happened to me for the first time.
it wasnt the most pleasant expierence
the same thing happened to me once on my ns4g. I had to pull the battery.
try flash recovery img at fastboot and then see if you can get in recovery
greg2826 said:
hello, yesterday i was changing rooms and i was wiping everything trough cwm 5.0.2.3 carebear.jrodd.
After wiping i went to choose zip and then i was sent back to main menu, i could choose any option from main menu, but behind options was waiting for me, tiny android fella with open box and some sort of a arrow sign.
I tried at least 15 times to get past that android fella and his freaking box with arrow jumping out of it , but i could not.
i could use nexus s soft buttons and at the bottom of screen was message saying "back button disabled".
i had to remove battery{ i didnt know what to do/i didnt actually have any other options, that i knew about}, then i powered back in to CWM and flashed rom.
everything works fine since then.
did any of u knows what happened?
i flashed lots of roms and i always trying to do everything up to code, but something like this happened to me for the first time.
it wasnt the most pleasant expierence
Click to expand...
Click to collapse
As long as it is working OK now then all is good.
Happens every now and again.
Ok this has happened to me a couple of times and from what i have found if i press both up and down volume buttons and power button in random combos after about second or third try it sorts it self out. I have tried to create the error and from what i have seen its if you are a lil heavy handed and either press the volume up and down together to start with or the power with one of the others at the same time it does some weird lock on going back or rebooting or anything really. don't think its isolated to the version of CW as i've had it on older builds
bigmem said:
Ok this has happened to me a couple of times and from what i have found if i press both up and down volume buttons and power button in random combos after about second or third try it sorts it self out. I have tried to create the error and from what i have seen its if you are a lil heavy handed and either press the volume up and down together to start with or the power with one of the others at the same time it does some weird lock on going back or rebooting or anything really. don't think its isolated to the version of CW as i've had it on older builds
Click to expand...
Click to collapse
that happened to me before, i got a mini heart attack, and some what i pressed the both volume button by accident and it worked lol
allenxx said:
that happened to me before, i got a mini heart attack, and some what i pressed the both volume button by accident and it worked lol
Click to expand...
Click to collapse
I swear the amount of random errors i have had in CWM and i always leave the battery pull to last thing, battery pulls have led me to partial bricking and having to learn quick that its not a good thing lol
bigmem said:
I swear the amount of random errors i have had in CWM and i always leave the battery pull to last thing, battery pulls have led me to partial bricking and having to learn quick that its not a good thing lol
Click to expand...
Click to collapse
try twrp recovery
greg2826 said:
hello, yesterday i was changing rooms and i was wiping everything trough cwm 5.0.2.3 carebear.jrodd.
After wiping i went to choose zip and then i was sent back to main menu, i could choose any option from main menu, but behind options was waiting for me, tiny android fella with open box and some sort of a arrow sign.
I tried at least 15 times to get past that android fella and his freaking box with arrow jumping out of it , but i could not.
i could use nexus s soft buttons and at the bottom of screen was message saying "back button disabled".
i had to remove battery{ i didnt know what to do/i didnt actually have any other options, that i knew about}, then i powered back in to CWM and flashed rom.
everything works fine since then.
did any of u knows what happened?
i flashed lots of roms and i always trying to do everything up to code, but something like this happened to me for the first time.
it wasnt the most pleasant expierence
Click to expand...
Click to collapse
It's caused by scrolling through the menu options 3 times. It's actually a feature. I forget where I read it but apparently back in the day there was a dude with a broken power button who couldn't select things in CWM so Koush put in that feature just for him. I believe one of the other buttons works to select items when that's enabled. To get out of it just keep scrolling up or down through the menu options 3 more times.
You ended up in the stock recovery. Hold power then press volume down OR volume up (cant remember which) and you'll be in stock recovery.
Also, the physical buttons are disabled when you press vol up and vol down at the same time. Do it again to return to normal.
happened to my yesterday again, after six months of problems free.
anyway nothing to be scared about.
thank u for answers, i kinda forgot about that thread... LOL

[Q] Nexus S i9020A Bricked due to failing power button - Odin seems the last hope?

Hi everyone,
INTRO:
So the power button on my Nexus S broke. No big deal, I remapped it to the search button and used the volume rocker to wake the device; an option that was embedded in Cyanogenmod9.
Then I upgraded to CM10... since I did that on top of CM9, my volume rocker option was still enabled, but the option is no longer in CM10's GUI.
I had some annoying issue and thought maybe I should wipe my phone; which I did.
Sadly, I realized that my "wake using volume rocker" option was no longer enabled, and there is no GUI to turn it back on.
I then found a .zip package that was supposed to enable the option but, I guess I went too fast, now my phone is stuck on a bootloop.
THE PROBLEM:
Since my power button is broken, I cannot navigate in the fastboot menu to recovery and fix the ROM.
Worst, since the power button is somehow shorted (i.e.: it powers on automatically when I insert the battery) Fastboot is not working properly and my PC never sees my phone, so you can forget about fastboot boot recovery.img
So: boot loop, power button broke, no recovery, no fastboot. =(
I searched quite a bit and found out you could get the Nexus S in download mode and get it to work with ODIN using a USB JIG.
I made myself such a JIG and successfully put the phone in some kind of download mode where my PC sees it, fastboot devices yields nothing *but* ODIN sees the phone!
So a glimmer of hope except for the fact that finding the .tar files for the Nexus S seems impossible...
Thoughts? Suggestion? TIA!
Francis // XC3N
Oh BTW:
-Yes I saw the other posts, but none of them mention the odin files
-Yes, I know fastboot is better; but it's not working and:
-No, I can't see the device on 3 different PCs using 3 different OSes and 3 Different cables when in fastboot mode
I mean by that last line that *nothing* shows in device manager in Win7 or XP and *nothing* shows in lsusb on ubuntu
So unless someone has an idea it looks like Download mode is the only way my PC sees my phone...
My power button done the same thing, I googled around and found a solution that worked for me.
It's somewhere here on xda but I don't got the link, basically everytime I booted into the bootloader I couldn't move the cursor with the volume button because the phone thought I was holding the power button, so I carefully tapped the casing around the power button and rebooted the bootloader and eventually I had control, it took 5-6 attempts to get it going but it did fix the power button for me.
I think it's something to do with the micro switches giving out after a certain number of uses.
Also it started screwing about recently so I just blew into the casing through the power button and it's behaved ever since.
In short, tap it until it works, once you have control of fastboot plug the usb in and your pc should detect it
Hope this helps, Good Luck
Sent from my U20i using xda app-developers app
Muckyfox said:
My power button done the same thing, I googled around and found a solution that worked for me.
It's somewhere here on xda but I don't got the link, basically everytime I booted into the bootloader I couldn't move the cursor with the volume button because the phone thought I was holding the power button, so I carefully tapped the casing around the power button and rebooted the bootloader and eventually I had control, it took 5-6 attempts to get it going but it did fix the power button for me.
Also it started screwing about recently so I just blew into the casing through the power button and it's behaved ever since.
Click to expand...
Click to collapse
Hey MuckyFox thanks for your reply!
Unfortunately, that would've worked back when the power button was flimsy and still working once in a while... I did try the tapping thing but really nothing works... the button seems entirely dead and shorted. I guess at this point I might've to bring it in for repair... if the power button isn't broken then I'll be able to easily fix everything in recovery or fastboot. Sucks because I feel like I'm so close to getting it to work without spending money XD I just can't find the files for odin even though they really do seem to exist.
Allright so I found some odin files which were said to work with the i9020a
I flashed them... at some point it said "RESET!" and then odin no longer saw the device. The device is now not booting at all. FML
So this thread is going to end up like every other similar thread: I went and bought a Galaxy Nexus ;P
For posterity, these are the files you shouldn't flash on i9020A:
BOOTLOADER : Bootloader_I9020XXJK1.tar
PDA : PDA_SOJU_GRH78_85442_SIGNED.tar
PHONE:
CSC : CSC_I9020_EUR.tar
My power button started failing over the last couple of days. First when I would set the phone to standby it would ask me if I wanted to switch off the device, then later on it wouldnt respond at all.
Really weird solution - boot into recovery, factory restore, clear dalvik cache, voila, works good as new! (aside from losing all my settings)
Note, I barely managed to get into recovery. The power button fully stopped working halfway through and I had to take the battery out and try it a couple of times.
Oddly, even during this uber-broken phase, the power button would always switch on the device when fully switched off (not just standby) indicating to me that it wasnt just a physical broken connection.
I've mentioned this before, but a full casing for the phone with all the buttons is around $10 on eBay
Sent from my Nexus S using xda app-developers app
XC3N said:
So this thread is going to end up like every other similar thread: I went and bought a Galaxy Nexus ;P
For posterity, these are the files you shouldn't flash on i9020A:
BOOTLOADER : Bootloader_I9020XXJK1.tar
PDA : PDA_SOJU_GRH78_85442_SIGNED.tar
PHONE:
CSC : CSC_I9020_EUR.tar
Click to expand...
Click to collapse
You need stuff for SOJUA, and just the fact CSC has EUR meaning Europe in it would scare the crap out of me. Possible you just flashed stuff meant for i9020T and not i9020A.
In case anybody comes back here, I'm just gonna drop this in.

[Q] CWM Touch 6.0.2.7 issue/question

Ok maybe i´m blind but what has happened her: No possibility to make a factory reset on may p3110? Where the hell is the yes? (yes i tried to scroll down Can´t post a pic here but CWM only shows "No" and "No". Kidding me?
try to scroll on different areas of the screen, aside from the list itself, where you would expect. also i think you can still scroll the list with the volume buttons? I can't confirm cause I went back to non touch. hope this helps.

Long press problem with my s8+ only in the center of the screen.

Hello.
Since a long time i have a big issue with my rooted s8+.
When i want to long press (tap and hold) on my screen to select a text, sometime it works sometime it doesn't work (it do like i pressed the screen and releases it immediately when it does not work as short press).
Until a few days ago i thought it was a random problem.
But i discovered a few days ago that this problem happens ALL THE TIME when i need to long press on the center of the screen and NEVER HAPPENS when i long press on the top or bottom of the screen.
Now when i want to select a text in the center of the screen, i just have to scroll the text up or down and then the long press works.
Does anybody have the same issue on his s8+?
Is there an app to definitly check this issue that happens only on long press and never on short press ?
How can i fix it?
Thank you for your help
(sorry my english is very bad i hope you have understood my question)
Open up your phone app as if you're going to call someone and dial *#0*#
(Star pound zero star pound)
This will get you into maintenance mode where you can trouble shoot many things. Tap on "touch" and drag finger all over the boxes on the screen in the shape of a rectangle with an X through it. This will allow u to see how your phone is responding to touch. Hope this gives u an idea as to where or if the issue is occurring. If not at least it's a pointer for phone issue trouble shooting.
Cheers!
Thank you for your answer.
I tried that and everything is ok on the touch test.
But after this test i just tried to select something on this page and i have the same issue. When i want to select in the center of the screen the tap and hold is not working.
I scroll a little the page and it is working.
It seem it just don't detect that i hold my finger. But detect normally when i just press with my finger.
I think i should send my phone to Samsung.
parisien99 said:
Thank you for your answer.
I tried that and everything is ok on the touch test.
But after this test i just tried to select something on this page and i have the same issue. When i want to select in the center of the screen the tap and hold is not working.
I scroll a little the page and it is working.
It seem it just don't detect that i hold my finger. But detect normally when i just press with my finger.
I think i should send my phone to Samsung.
Click to expand...
Click to collapse
I just tried with the page i put a screenshot in attachment to this post.
When i try a tap and hold (i tried several times) on the line "i scroll a little the page..." it does not work ( it just select the word on which i have put my finger but i can not extend the selection and i don't have the icon with copy past etc)
But when i tap and hold on the line starting by "of the screen the tap...." and the line starting with "it seem i just don't detect..." everything is normal.
parisien99 said:
I just tried with the page i put a screenshot in attachment to this post.
When i try a tap and hold (i tried several times) on the line "i scroll a little the page..." it does not work ( it just select the word on which i have put my finger but i can not extend the selection and i don't have the icon with copy past etc)
But when i tap and hold on the line starting by "of the screen the tap...." and the line starting with "it seem i just don't detect..." everything is normal.
Click to expand...
Click to collapse
Here's your troubleshooting steps. Try them each one at a time. If #1 doesn't work, then move on to #2, etc, until it's fixed.
1. Reboot phone
2. Clear cache in recovery
3. Start in Safe Mode
4. Factory Reset
5. Reflash stock, factory firmware with ODIN
If none of those fix the issue, then you will need to reach out to Samsung.
Mr. Orange 645 said:
Here's your troubleshooting steps. Try them each one at a time. If #1 doesn't work, then move on to #2, etc, until it's fixed.
1. Reboot phone
2. Clear cache in recovery
3. Start in Safe Mode
4. Factory Reset
5. Reflash stock, factory firmware with ODIN
If none of those fix the issue, then you will need to reach out to Samsung.
Click to expand...
Click to collapse
Thank you
I think most that it would be a hardware problem
But as my phone is rooted i will do all that before sending to samsung as i must install a stock rom before sending to Samsung.
But most of all i wanted to know if other people had also this issue.
parisien99 said:
Thank you
I think most that it would be a hardware problem
But as my phone is rooted i will do all that before sending to samsung as i must install a stock rom before sending to Samsung.
But most of all i wanted to know if other people had also this issue.
Click to expand...
Click to collapse
The steps I gave you actually eliminate it being a software problem, so it narrows it down to hardware.
Let us know if you're able to fix it, or have to send it to Samsung fie repair.
Mr. Orange 645 said:
The steps I gave you actually eliminate it being a software problem, so it narrows it down to hardware.
Let us know if you're able to fix it, or have to send it to Samsung fie repair.
Click to expand...
Click to collapse
Than you
I will do that in a few days.
But i just thinked about something.
I just updated my samsung firmware on dec 28. And i had this issue before the update.
When updating, for the root, i installed twrp and have done a complete wipe on twrp before installing magisk. (i still didn't find no way to root without wiping, if there is a way please tell me)
I think i have passed all these steps when i have done the update/root process. Am i right?
parisien99 said:
Than you
I will do that in a few days.
But i just thinked about something.
I just updated my samsung firmware on dec 28. And i had this issue before the update.
When updating, for the root, i installed twrp and have done a complete wipe on twrp before installing magisk. (i still didn't find no way to root without wiping, if there is a way please tell me)
I think i have passed all these steps when i have done the update/root process. Am i right?
Click to expand...
Click to collapse
I honestly don't know. I don't root. So I don't know the steps. Try them anyway, and if you end up having to do a factory reset, don't restore anything. Start completely fresh.
And installing STOCK UNROOTED firmware with ODIN will eliminate any issues associated with root.
parisien99 said:
Thank you for your answer.
I tried that and everything is ok on the touch test.
But after this test i just tried to select something on this page and i have the same issue. When i want to select in the center of the screen the tap and hold is not working.
I scroll a little the page and it is working.
It seem it just don't detect that i hold my finger. But detect normally when i just press with my finger.
I think i should send my
Did you try doing a factory reset? You could try that but it sounds as if it is a hardware issue. Get it in to samsung before warranty runs out. Good luck my friend!
Click to expand...
Click to collapse

Categories

Resources