I'm just going to get straight to the problem here: my Atrix won't boot because something went wrong with a ROM I was trying to install. I was using the package from here Project kitchen sink, and selected aokp. I have Clockwork Recovery 5.8.1.8, so it boots into recovery.
The problem is that my volume rocker is broken, I *think* because of pds, so I cannot navigate the menu. I have tried using RSDLite and Fastboot, hoping that I could work through the recovery boot menu, but it's useless. And since my volume keys refuse to work, I can't set the phone to boot into RSD mode. I'm stuck in an endless loop of not-able-to-do-jack-****, and I don't think I'll be able to send it in to Moto for a replacement.
I don't know if the failure is due to a hardware issue (my Atrix was shipped to me from my family, since I live in Puerto Rico), the CM7 ROM I had before, or a recent crash (the battery was also giving me problems, and lately crashed the phone several times, not turning on unless I pulled it.)
Sparr159 said:
I'm just going to get straight to the problem here: my Atrix won't boot because something went wrong with a ROM I was trying to install. I was using the package from here Project kitchen sink, and selected aokp. I have Clockwork Recovery 5.8.1.8, so it boots into recovery.
The problem is that my volume rocker is broken, I *think* because of pds, so I cannot navigate the menu. I have tried using RSDLite and Fastboot, hoping that I could work through the recovery boot menu, but it's useless. And since my volume keys refuse to work, I can't set the phone to boot into RSD mode. I'm stuck in an endless loop of not-able-to-do-jack-****, and I don't think I'll be able to send it in to Moto for a replacement.
I don't know if the failure is due to a hardware issue (my Atrix was shipped to me from my family, since I live in Puerto Rico), the CM7 ROM I had before, or a recent crash (the battery was also giving me problems, and lately crashed the phone several times, not turning on unless I pulled it.)
Click to expand...
Click to collapse
PDS does not affect volume buttons.
And what happens when you boot? Boot loop is not very specific...
I read a post on here that said it did...
And what happens is that it boots once, stays on the Moto logo, then blacks out, boots again and goes into recovery. Since I have no way to do anything, I press the power button and it goes again.
What I need is either
1) A way to work with RSD through the recovery, or
2) A way to work with ADB through recovery, or
3) Someone to just tell it to me straight: I'm f*cked and I need to send it in to Moto (Which I doubt they would take it.)
Sparr159 said:
I read a post on here that said it did...
And what happens is that it boots once, stays on the Moto logo, then blacks out, boots again and goes into recovery. Since I have no way to do anything, I press the power button and it goes again.
What I need is either
1) A way to work with RSD through the recovery, or
2) A way to work with ADB through recovery, or
3) Someone to just tell it to me straight: I'm f*cked and I need to send it in to Moto (Which I doubt they would take it.)
Click to expand...
Click to collapse
I would tell you to flash touch recovery however I don't think you can and how it would help you recover from this situation.
Sent from my MB860 running Jokersax's CM9
The weird thing is that I had flashed touch recovery before I started with kitchen sink, and it fixed the touch problems I was having there, but now the touch doesn't work. I downloaded it from the clockwork website, because I don't want to pay for something that is available for free, and I flashed it in fastboot.
Now I have Clockwork Recovery 1.8, which should be touch, no?
Sparr159 said:
The weird thing is that I had flashed touch recovery before I started with kitchen sink, and it fixed the touch problems I was having there, but now the touch doesn't work. I downloaded it from the clockwork website, because I don't want to pay for something that is available for free, and I flashed it in fastboot.
Now I have Clockwork Recovery 1.8, which should be touch, no?
Click to expand...
Click to collapse
You mean 5.8.1.8? If so then yes. And if touch is not working in touch recovery then it does sorta confirm you need the PDS fix...
We are finally getting somewhere: yes, it is 5.8.1.8, touch doesn't work. I know I need the PDS fix, and I applied it. Twice. I patched in fastboot before I started with kitchen sink, and I thought it had worked, since the Aroma installer was touch-enabled after I patched. But now the recovery menu is not working. I tried pressing the search key, like with the Aroma installer, but I knew it wouldn't have any effect.
Sparr159 said:
We are finally getting somewhere: yes, it is 5.8.1.8, touch doesn't work. I know I need the PDS fix, and I applied it. Twice. I patched in fastboot before I started with kitchen sink, and I thought it had worked, since the Aroma installer was touch-enabled after I patched. But now the recovery menu is not working. I tried pressing the search key, like with the Aroma installer, but I knew it wouldn't have any effect.
Click to expand...
Click to collapse
Can you point me to the thread where it says volumer rocker is linked to pds because i searched and cant find it.
How are you booting...i mean with what key combination? Im assuming your booting normally(only power button) and end up going into recovery. Try booting with power button and volume down.
Sorry I'm not quoting anybody, first off.
Second, I can't find the link. I spent around an hour searching and found it through duckduckgo, but now I can't remember the search term I used. If I find it, I'll post it.
And yes, I'm booting only with power button, because the volume down key isn't working. That is where the pds problem comes in: I can't use the volume down or up key because the keys don't work.
My friend told me that I could use adb to manually boot it into fastboot mode. That works fine, but I don't know how to flash anything other than the recovery/pds partitions. I know fastboot has a "flashall" command, but I don't know how to use that or if it is even going to help. **Essentially** I can boot into fastboot mode, but I want to know if it is even possible to just flash a rom through that. Messy, of course, but if I can just get even a basic ROM working, I can go on from there.
I think you have 2 options:
1. if you can get to fastboot you can reflash everything using uncle cemka's method: http://forum.xda-developers.com/showthread.php?t=1501532
you basically take an .sbf unpack it and flash each part separately.
2. buy a atrix audio jack/camera flex cable from ebay and install it yourself, be especially careful when installing because the very small flex/ribbon that goes to your volume buttons stress fractures very easily if bent very much when installing, hence your volume buttons stop working.
I'm using cemka's method now. I'm waiting for the stock ROM to download, the one from his post. When I finish the whole process, I'll let you guys know how it worked out.
UPDATE: Thank you to whoever referred me to uncle cemka's method, I was able to use it to flash stock ROM. I have functionality back, can boot, and won't waste around $90 on a paperweight.
However, the first problem is still there: The volume keys still don't work. I still need to fix those before everything is %100 percent, so this issue is still open... Sorry guys
Related
Just received a replacement Vibrant and can not boot into recovery through the power/volume up/down method, has something changed?
To get into recovery mode you need to hold Volume Down and Power Button.
I have booted into recovery many times with my original Vibrant, my replacement will not boot.
Um, the OP explicitly said that they can't get into recovery with volup+voldn+power, on a replacement phone. Replacement=more likely they know how to do it that I do, but I just received a new Vibrant from T-Mo-USA today and I cannot get it into recovery either.
VolUp+VolDn held, power until 'vibrant samsung' then release power is supposed to be recovery, but not working for me. Just VolDn or just VolUp and power only boots the phone as well. Waiting with power held until screen goes black again then 'vibrant samsung' returns is also ineffective. I can get to download mode with vol buts while plugging USB, and I've double-checked that both vol buts are working. It /is/ possible that a change took place and recovery is no longer accessible through that key combo...
Shiny new handset, never yet had a SIM inserted. (Trying to get clockwork recovery running to do nandroid backup before setting up first time) (adb gives me a permission error, going to research that now)
j
Quick Boot in the market.
I am NOT a fan of the new q&a section. I liked going to one place.
s15274n said:
I am NOT a fan of the new q&a section. I liked going to one place.
Click to expand...
Click to collapse
Agreed. Wait, is this s15274n. I love Q&A.
haha guess you saw you were in the sticky now
newkirk said:
Um, the OP explicitly said that they can't get into recovery with volup+voldn+power, on a replacement phone. Replacement=more likely they know how to do it that I do, but I just received a new Vibrant from T-Mo-USA today and I cannot get it into recovery either.
VolUp+VolDn held, power until 'vibrant samsung' then release power is supposed to be recovery, but not working for me. Just VolDn or just VolUp and power only boots the phone as well. Waiting with power held until screen goes black again then 'vibrant samsung' returns is also ineffective. I can get to download mode with vol buts while plugging USB, and I've double-checked that both vol buts are working. It /is/ possible that a change took place and recovery is no longer accessible through that key combo...
Shiny new handset, never yet had a SIM inserted. (Trying to get clockwork recovery running to do nandroid backup before setting up first time) (adb gives me a permission error, going to research that now)
j
Click to expand...
Click to collapse
Let us know if you find a resolution, thanks!
s15274n said:
Quick Boot in the market.
I am NOT a fan of the new q&a section. I liked going to one place.
Click to expand...
Click to collapse
Quick Boot specifically states that you must ALREADY have root status for it to work.
So we need Root for Quick Boot to get into Recovery Mode, but we need to first get into Recovery Mode to get Root...
Ring around the rosy...
Anybody else have any ideas?
^ he didn't say he didn't have root already. I also posted an alternate method to root above without stock recovery.
Have either of you found a way to recovery with key combos yet. I too can not get recovery with vol buttons. Only thru terminal, adb, rom manager, etc. i'd really like to know if anyones found a solution to this??? I'd like to be able to boot recovery manually in case I cant boot into home screen for some reason.
Someone mentioned getting it to work while having it plugged into the charger.
Frankly, the only way I was able to get into Recovery Mode was through the ADB method.
Sent from my SGH-T959 using XDA App
I called T-Mobile regarding this and they agree it should work with hardware buttons and are sending me a replacement.
Same issue. Got the phone on Aug 23 and the only way I can go to recovery is via ADB and ClockWorkMod
Hmmm, I have the same issue. The funny thing is that I can get into recovery on my girl's phone just fine. And I can't on mine. They only way I could get into recovery was by using the 1-click root. Now, I can use ROM Manager to get into recovery while "on-the-go". At first, I was honestly afraid that maybe my phone came without the recovery installed!
I know it gets frustrating listening to the stupid T-Mobile jingle taunting you every time it fails.
I guess it's not a big enough deal to me to send it back now that I have a couple of options, but it seems like it's a more common issue than I thought. Only way to get Samsung to do something is to keep sending them back . . .
Its important to be able to get recovery with the buttons tho. What if your flashing roms or anythimg for that matter and the phone wont boot regularly. Then you cant get into recovery to restore. Called tmobile and Im sending mine back tomorrow for replacement, unless somebody knows another way to get into recovery if you end up in a boot loop???
My friend just got his Vibrant, I went to root it for him and wont go into recovery. Mine works fine,I can get into recovery fine on mine everytime. I told him to return it and swap it out. Getting into recovery is very important if you flash a rom and you run into booting issues.
roguespy0 said:
My friend just got his Vibrant, I went to root it for him and wont go into recovery. Mine works fine,I can get into recovery fine on mine everytime. I told him to return it and swap it out. Getting into recovery is very important if you flash a rom and you run into booting issues.
Click to expand...
Click to collapse
I really suspect what we're seeing isn't a defect per se, but the result of a suit at t-mo being told that people are using recovery mode for rooting their phones and restoring things like wifi tethering, who responded "then disable recovery mode dammit"...
If you return a Vibrant that won't go into recovery from buttons and actually get a new-in-the-box vibrant in its place, I suspect there's a very high probability that the replacement is the same, and if you get a replacement that WILL enter recovery from buttons I suspect it's likely to be an open box or what-have-you. For the latter, as more Vibrants are returned for not entering recovery, you're more and more likely to end up with a 'like-new' replacement that won't enter recovery either.
Long-term I suspect the solution is going to have to come from us, not t-mobile.
j
I can not boot into recovery this is also a replacement phone. I installed vibrant7 didn't care for it so did a rom manager recovery back to stock and my phone is stuck on the vibrant start screen. Can anyone help me fix my brick?
it doesn't work on my Vibrant,tried Volume Up/Power,Volume Down/Power, no luck....
Hello
I rooted my Galaxy s2 i777 using 2.3.6 (I think that was it - what ATT pushed out earlier in the summer) and next flashed CWM using ODIN. I noticed that the menus weren't working in CWM. When I use the home or menu buttons it just toggles a logo screen, and power does nothing (volume keys do work). I noticed others had this issue with this phone but didn't encounter any solutions.
Poking around the Rom Manager application I noticed a reboot into recovery mode feature and thought I'd try it. It did as advertised. But now when I reboot by holding down power it immediately reboots into recovery mode. I'm guessing what happens is the "reboot into recovery mode" feature put itself at the head of the boot sequence and instead of removing itself from there on load, which it probably should, it waits until the user exits the program cleanly. Unfortunately, because I can't get the keys to work in the program, the only way I can exit is to hold down power. I can navigate to the "power off" or "reboot" options but I can't execute them (press "enter"). So it stays at the head of the boot sequence (just my theory) and I can't get out. Actually when I power off by holding down the power key the phone just reboots immediately, right back into cwm recovery, so there seems to be something more going on.
I have a backup of the system but I can't figure out how to get out of the sequence. I tried the download mode and recovery mode key sequences but they don't work (not even sure if they're supposed to work in this recovery screen). Any ideas? I have a backup of the system, so I'm happy to attempt scorched earth suggestions. Kies can't recognize the phone anymore. Many thanks.
Jason Farnon said:
Hello
I rooted my Galaxy s2 i777 using 2.3.6 (I think that was it - what ATT pushed out earlier in the summer) and next flashed CWM using ODIN. I noticed that the menus weren't working in CWM. When I use the home or menu buttons it just toggles a logo screen, and power does nothing (volume keys do work). I noticed others had this issue with this phone but didn't encounter any solutions.
Poking around the Rom Manager application I noticed a reboot into recovery mode feature and thought I'd try it. It did as advertised. But now when I reboot by holding down power it immediately reboots into recovery mode. I'm guessing what happens is the "reboot into recovery mode" feature put itself at the head of the boot sequence and instead of removing itself from there on load, which it probably should, it waits until the user exits the program cleanly. Unfortunately, because I can't get the keys to work in the program, the only way I can exit is to hold down power. I can navigate to the "power off" or "reboot" options but I can't execute them (press "enter"). So it stays at the head of the boot sequence (just my theory) and I can't get out. Actually when I power off by holding down the power key the phone just reboots immediately, right back into cwm recovery, so there seems to be something more going on.
I have a backup of the system but I can't figure out how to get out of the sequence. I tried the download mode and recovery mode key sequences but they don't work (not even sure if they're supposed to work in this recovery screen). Any ideas? I have a backup of the system, so I'm happy to attempt scorched earth suggestions. Kies can't recognize the phone anymore. Many thanks.
Click to expand...
Click to collapse
1. you obviously flashed a kernel WITH CWM via Odin.
2. Rom Manager should not be used.
Flash a rooted stock ROM via ODIN.
read around in the stickies of the i777 forum, and get acquainted with things.
Boot into CWM correctly, and go about flashing whatever you want knowing what you just learned by reading the correct stuff.
Welp, first things first.
1. Read, search, Google, only look at results from this forum, i.e. the ATT Galaxy S2 I777 forums on XDA. Any info from any other sites is more likely to get you nowhere or brick your phone further.
2. After having done so, you'll learn never to use Rom Manager. EVER.
3. Also after having done #1, you'll learn to never try to flash CWM separately. As Moto implies, CWM for our phones is built into custom kernels, it is not separate.
4. Follow this guide to start over and get back to stock.
5. Then follow this guide to root and flash custom ROMs and kernels.
You sound like an intelligent guy, so as long as you do more reading around here you'll figure everything out slowly. Make sure to read stuff multiple times until you fully understand everything, and feel free to ask questions about stuff you don't understand, but only after reading said guides multiple times.
EDIT: Gah Moto, why you gotta post ahead of me D:
Actually the problem is most likely the fact that he is probably using an old version of cwm where the home button selects stuff. And rom manager.
Sent from team Pirate! Using Tapatalk 2
karate104 said:
Welp, first things first.
1. Read, search, Google, only look at results from this forum, i.e. the ATT Galaxy S2 I777 forums on XDA. Any info from any other sites is more likely to get you nowhere or brick your phone further.
2. After having done so, you'll learn never to use Rom Manager. EVER.
3. Also after having done #1, you'll learn to never try to flash CWM separately. As Moto implies, CWM for our phones is built into custom kernels, it is not separate.
4. Follow this guide to start over and get back to stock.
5. Then follow this guide to root and flash custom ROMs and kernels.
You sound like an intelligent guy, so as long as you do more reading around here you'll figure everything out slowly. Make sure to read stuff multiple times until you fully understand everything, and feel free to ask questions about stuff you don't understand, but only after reading said guides multiple times.
EDIT: Gah Moto, why you gotta post ahead of me D:
Click to expand...
Click to collapse
Thanks, that did it. I'd actually read the stickies, I just didn't think I could get into download mode because the phone was stuck in that auto-reboot loop.
For anyone else stuck in that loop cwm recovery loop, the download mode entry method (press both volume keys and insert usb) needs to be timed just so, since you usually perform the sequence when the phone is powered down (in stable way) but in this situation you only have a moment before it restarts. After powering down, just as it restarts automatically you can see the capacitative buttons blink for an instant, and that's when I started the sequence. Took me about half a dozen times but I eventually caught it. Am I the only one struggling with how hard these captchas are getting over the years? there's probably a sticky for that too I guess nvm.
If I'm not mistaken you can get into download mode without having a battery plugged in, so no need for trying to time it. Just hold volume buttons and plug in USB. For future reference; glad you got it worked out. Make sure to read the second guide thoroughly so you know how to safely flash stuff, and hit my thanks button if i helped you out.
Sent from my SGH-I777
Hi,
Today I helped a friend flash a custom rom on a galaxy gio and I opened cmw on my phone to help him go to the right menu's in cmw.
I think I changed the ext4 partition to 0mb (don't realy know how :s) and now when I boot android Instead of the bootscreen with the red m I get some white text with some different options (like boot in adb (about 10 options)) it also tells me I can move change option with volume down and accept with volume up, but these don't do anything :s.
After I wait for a while android just starts booting like normal and everything seems fine, but when android has booted it seems like the touchscreen move up for like a centimeter (if I want to press a button I need to touch the screen under the button) and my soft keys don't work anymore (but I think this is because of the moved touchscreen)
What did I do and how can I make it normal again? I'm running the latest GB Mrom.
Edit:this is the screen I get when there normally is a red circle with the white M in:
Uploaded with ImageShack.us
Thnx if anyone can help me!
I've been trying somethings and if I don't have my usb cable plugged in I can choose some options on the menu, it seems now that I somehow removed my clockwordmod recovery and went back to old recovery? Is this even possible?
Should I just reflash cmw with fastboot again?
Plz help me
I would hold of on flashing another recovery until someone more knowledgeable than I comes along. There might be a chance where you can do permanent damage. Seems like it could have simply deleted their boot logo, and now instead of those options being normally hidden, are being shown. (like when you boot while holding volume down). What happens if you try booting with volume button held down?
Edit: If all else work as it should, just leave it. Makes it look like verbose mode. Forget Motorola and their stupid 'm'. =P
Sent from my MB860 using xda app-developers app
thesummoner101 said:
I would hold of on flashing another recovery until someone more knowledgeable than I comes along. There might be a chance where you can do permanent damage. Seems like it could have simply deleted their boot logo, and now instead of those options being normally hidden, are being shown. (like when you boot while holding volume down). What happens if you try booting with volume button held down?
Edit: If all else work as it should, just leave it. Makes it look like verbose mode. Forget Motorola and their stupid 'm'. =P
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
If I hold volume down + power while booting I get the same thing, and everything works normaly, BUT my touchscreen is messed up, the every touch gets detected to high (if I want to hit app drawer I need to push between the home and back soft button) and the soft buttons don't work.
Oh right, you did mention that, my bad. Well, I'd say hold off for someone that might know what happened as I've never read about or experienced something like this. Maybe try posting in the main XDA Q&A section not specific to Atrix as someone might have had a similar issue with another device (maybe even a Moro) Sorry can't be of much help. Good luck.
Sent from my MB860 using xda app-developers app
touchscreen problems are usually related to the pds partition. Did you by any chance make a backup before these problems started?
I don't know if the bootscreen is related to the PDS partition but it might be that this partition is corrupted.
jorno88 said:
touchscreen problems are usually related to the pds partition. Did you by any chance make a backup before these problems started?
I don't know if the bootscreen is related to the PDS partition but it might be that this partition is corrupted.
Click to expand...
Click to collapse
but could that also explain the weird boot message with the options? (or is it also called animantion, because the Mrom annimations works normal (the blue android guy))
I had mistakenly done something that resulted in your exact problems once. What I did to fix. First you'll need to fastboot a recovery again. Next you'll have to do the pds partition fix. Then lastly flash the proper boot logo back to get the m screen. The first step is dependent on you being able to get into fastboot so hopefully you can.
pre4speed said:
I had mistakenly done something that resulted in your exact problems once. What I did to fix. First you'll need to fastboot a recovery again. Next you'll have to do the pds partition fix. Then lastly flash the proper boot logo back to get the m screen. The first step is dependent on you being able to get into fastboot so hopefully you can.
Click to expand...
Click to collapse
thnx for the reply!
you mean the Fix in this thread?
http://forum.xda-developers.com/showthread.php?t=1131649
And I'm guessing i'll need the one for gingerbread?
M_K_ said:
thnx for the reply!
you mean the Fix in this thread?
http://forum.xda-developers.com/showthread.php?t=1131649
And I'm guessing i'll need the one for gingerbread?
Click to expand...
Click to collapse
Yes that is the right file and yes for gb.
Ok, I just reflashed the recovery with fastboot and then I flashed the PDS partition fix and the touchscreen works perfectly again. Only the red M is still gone.
Any Idea how to get it back?
And Thank You so much!
Now I can use my phone again
M_K_ said:
Ok, I just reflashed the recovery with fastboot and then I flashed the PDS partition fix and the touchscreen works perfectly again. Only the red M is still gone.
Any Idea how to get it back?
And Thank You so much!
Now I can use my phone again
Click to expand...
Click to collapse
Somewhere in the forum is the boot logo. I believe its in the apps section. Search for stock boot logo. Glad I was able to help.
Actually here you go. http://forum.xda-developers.com/showthread.php?t=1423763
So i hoping someone could give me a hand i have exhausted all of my ideas
My Soft key buttons on the bottom of the phone (menu, home, back, search) have stopped working entirely phone is completely stock never rooted flashed or changed in anyway my first thought was maybe it was a software problem so i booted into recovery my holding vol +/- and power and tried to clear the cache (worth a shot right?) but in Samsung's infinite wisdom they use the Home soft key as select so i am unable to select wipe cache and naturally am unable to select Reboot system as well. i pull out the battery to restart the phone but to my horror the phone automatically reboots into the recovery screen... wtf! tried every combination of buttons physical and soft but i cant select anything in the recovery screen you name it i tried it short and long press of everything even tried booting holding different keys just for the sake of trying.
also tried to connect via adb while in recovery to send a "adb reboot" command but adb will not detect the device tried using every Samsung driver i could get my hands on maybe i am missing something here?
Next i tried rebooting with odin using an empty tar file as mentioned here http://forum.xda-developers.com/showthread.php?t=1766399 but it only restarts to the... recovery screen.... for the love of god.
I'm out of ideas and any help would be appreciated i have no insurance and i have another year before I'm up for a renewal.
your phone sounds broken. deactivate it with VZW and go buy something else on swappa/ebay. (i personally recommend the S3, Gnex, or, **** you get another fassy if you want)
Hey dude, I have the stock Verizon ROM and boot loaders installing those should fix your problem and if you don't want to lose what's in your phone I'm afraid friend you're **** out of luck. Pm or call 423 400 6484 I'll give you the pass to the Google drive I use to send ROMs and such. Good luck.
Sent from my SCH-I500 using xda app-developers app
Seeing as the buttons don't work in recovery, what do you think will be fixed by clearing a cache? It's called recovery because it doesn't use that stuff.
Best bet? Try flashing a custom rom which had soft key support and enable them right away. With this phone's penchant for phantom key presses you may have just improved your experience with this phone by having them die.
Time to pony up and flash a real rom
Use Odin to flash a custom recovery, As the last poster said, flash a custom ROM with on-screen key options and use that from now on.
I never use my soft keys in recovery as the power button selects all the options I've ever needed. Have you tried using the power button to select on your phone?
Fascinated by unicorn flavored jellybeans
Ok, so I rooted my LGOG E970. I figured I better unlock it as well, so I used FreeGee and unlocked it. I tried to download CWM but it said it couldnt download file. So I thought I would reboot my phone. Now, all I get is the google logo, with the unlocked key underneath, and it then goes to the LG logo and back to Google and shuts off. I tried to hold down power and volume down, nothing, and power volume up nothing.:crying:
any ideas? Thanks in advance! I love this phone!
CJ
You too, huh?
I did this the other night, and when the CWM failed to install I went to download it myself... That's when I saw that CWM for geeb is 6.0.3.8, not 6.0.4.5 like FreeGee shows. (Looks like FreeGee has moved on to targeting G2 or another... Oops.)
I hope you backed up your EFS, because mine was screwed up and I needed to manually restore it from the backup I'd taken. (I've had my phone rooted for 9+ months, finally got fed up with stock and was looking to get onto a 4.4 ROM)
So here's what I did:
Held power button until phone was properly off (failed boot seemed to be a still partially on state)
Held volumn up first, then started holding power.
When phone vibrated slightly, I let go of power and kept holding volume up... You should be in boot loader now.
When your phone is in the bootloader, connect to your PC (Make sure you have the proper drivers if you use Windows; I use Linux which doesn't have the same nonsense setup for drivers like Windows does)
Make sure "fastboot devices" shows your phone and then type: fastboot flash recovery _____recovery file name.img____
Press volume down twice to select "Recovery", and press power once to select it... You should be booted into the recovery that you just installed.
Once you're in a recovery, you can push a ROM zip via ADB, flash, wipe data/dalvik cache and reboot.
thanks, Just a little more help
aedren said:
You too, huh?
I did this the other night, and when the CWM failed to install I went to download it myself... That's when I saw that CWM for geeb is 6.0.3.8, not 6.0.4.5 like FreeGee shows. (Looks like FreeGee has moved on to targeting G2 or another... Oops.)
I hope you backed up your EFS, because mine was screwed up and I needed to manually restore it from the backup I'd taken. (I've had my phone rooted for 9+ months, finally got fed up with stock and was looking to get onto a 4.4 ROM)
So here's what I did:
Held power button until phone was properly off (failed boot seemed to be a still partially on state)
Held volumn up first, then started holding power.
When phone vibrated slightly, I let go of power and kept holding volume up... You should be in boot loader now.
When your phone is in the bootloader, connect to your PC (Make sure you have the proper drivers if you use Windows; I use Linux which doesn't have the same nonsense setup for drivers like Windows does)
Make sure "fastboot devices" shows your phone and then type: fastboot flash recovery _____recovery file name.img____
Press volume down twice to select "Recovery", and press power once to select it... You should be booted into the recovery that you just installed.
Once you're in a recovery, you can push a ROM zip via ADB, flash, wipe data/dalvik cache and reboot.
Click to expand...
Click to collapse
I try to go to recovery and it just goes blank. What program with my crazy windows would be best to get a stock file to the phone? Or any other ideas>
thanks again
ZombieGeek said:
I try to go to recovery and it just goes blank. What program with my crazy windows would be best to get a stock file to the phone? Or any other ideas>
thanks again
Click to expand...
Click to collapse
Yeah, the stock recovery won't boot if you try it either. I forgot to tell you that. If you drop in a custom recovery (TWRP or CWM), it will work fine and you can both create a backup of your data and flash a new ROM...
If you want to try to get back to stock, LGNPST is what you should try. But to be completely honest, I don't know if you can LGNPST from the state that it's in. I haven't tried, and I'm using a custom ROM now (the whole reason I unlocked the bootloader to begin with).
bummer
aedren said:
Yeah, the stock recovery won't boot if you try it either. I forgot to tell you that. If you drop in a custom recovery (TWRP or CWM), it will work fine and you can both create a backup of your data and flash a new ROM...
If you want to try to get back to stock, LGNPST is what you should try. But to be completely honest, I don't know if you can LGNPST from the state that it's in. I haven't tried, and I'm using a custom ROM now (the whole reason I unlocked the bootloader to begin with).
Click to expand...
Click to collapse
again, thanks so much! you are my hero, only problem is, I loaded the kit kat bu houstonn and now I have no cellular? I hate it when your phone isnt a phone lol
ZombieGeek said:
again, thanks so much! you are my hero, only problem is, I loaded the kit kat bu houstonn and now I have no cellular? I hate it when your phone isnt a phone lol
Click to expand...
Click to collapse
Yeah, I got that too. I don't know if I got it fixed due to changing ROM, using the suggested recovery from the ROM, or if it was due to me restoring my EFS backup.
I flashed the TeamWin recovery found in the PSX instructions. Then I flashed PSX + Latest kernel + Banks Gapps + Banks Google Camera + AT&T NFC fix + SuperSU. I manually restored EFS from an ADB shell while in recovery.
When I booted I had: LTE works, Wifi works, NFC works, Camera works, ART works... The only things failing for me are the following:
Cell provider shows up as "Maritime" (display bug; as mentioned, LTE works fine and I'm on AT&T)
Settings > Developer Tools > Geeky Process Stats (does nothing)
Settings > Lockscreen > Slider Shortcuts (crashes as soon as I tap the middle ring)
LogCat is spammed with "QCOM PowerLock: Failed to acquire lock" whenever my finger is on the screen.
/system/xbin/mount --bind doesn't work (neither does mount -o bind). It gets sorta half-way-there, because the target directory can't be removed, but isn't bound properly it seems.
Other than that, it's been fast and smooth.