Develop Bugs

[GUIDE] Restoring Your KF to stock from ROMs

Here's how to restore your KF to stock from a custom ROM
make sure you have the stock recovery installed (if you are in CM7 you are)
First, download the latest official update from here -> http://www.amazon.com/gp/help/customer/display.html?nodeId=200790620
then download this file -> http://www.mediafire.com/?31sljwzyu0i1nev
and place it on your sdcard
it should be /sdcard/command
rename the amazon update to update.zip (even if it's a .bin file, make sure it is update.zip, NOT update.zip.bin
then, place that file on the sdcard under /sdcard/kindleupdates/
it should be /sdcard/kindleupdates/update.zip
turn off usb mass storage mode
go into the adb shell and type
cd cache
mkdir recovery
cp /sdcard/command /cache/recovery/
idme bootmode 0x5001
reboot
i just went from cm7 to stock and it worked fine

<3 thanks man

This makes me much more inclined to try to CM7; however, I think I will wait for a final version of the ROM. Seems like a lot of good progress is being made. Thanks for posting!

lol stick to stock until the wrinkles are ironed out. i feel like everybody wants in on the alpha builds for all devices until they actually test it out and wanna go back

JackpotClavin said:
lol stick to stock until the wrinkles are ironed out. i feel like everybody wants in on the alpha builds for all devices until they actually test it out and wanna go back
Click to expand...
Click to collapse
That's the truth. When I get payed Friday you got your self some beer money coming.
Sent from my Kindle Fire using xda premium

All in favor of from now spelling paid as payed say I
I always make that mistake, we should have the option to spell it both ways
Sent from my DROID Pro using XDA App

I think the current CM7 build is pretty soild.
Is it possible to mess around with ROMs in Eclipse or do you need to be running linux?

Never tried using another OS. I believe the easiest OS to set up a build environment is linux (ubuntu primarily)
Sent from my DROID Pro using XDA App

So has anybody actually done this?
Sent from my DROID Pro using XDA App

JackpotClavin said:
So has anybody actually done this?
Sent from my DROID Pro using XDA App
Click to expand...
Click to collapse
I tested it. It worked for me. I went back to cm7 tho.
Sent from my Kindle Fire using xda premium

Sweet, I feared I might've skipped a small step or made a typo thanks!
Sent from my DROID Pro using XDA App

Ahh see now I can take a dip into the CM waters.

Tnis is impossible if adb shell don't work and device have bootloop?

animefun135 said:
Tnis is impossible if adb shell don't work and device have bootloop?
Click to expand...
Click to collapse
Maybe try to explain in better English
Sent from my Kindle Fire using xda premium

This is impossible as long as my device is infinitely restarts after logo Kindl Fire ...
Just does not work command adb shell.
This method is useless if the command adb shell is broken.

I don't think it was meant to provide a way out in case something gets messed up, just a way to get back to stock should you want to under normal circumstances.

animefun135 said:
This is impossible as long as my device is infinitely restarts after logo Kindl Fire ...
Just does not work command adb shell.
This method is useless if the command adb shell is broken.
Click to expand...
Click to collapse
Sure, it doesn't work, since you jumped the gun and tried to do this on your own without waiting for someone knowledgeable to put out clear instructions.
Any other posts people put up probably won't apply to you because you jacked up your Fire.
Why not seal deal the go for the coup de grace and make a factory cable, that forces it into fastboot etc so you can try and get back into adb.

Thelgow said:
Sure, it doesn't work, since you jumped the gun and tried to do this on your own without waiting for someone knowledgeable to put out clear instructions.
Any other posts people put up probably won't apply to you because you jacked up your Fire.
Why not seal deal the go for the coup de grace and make a factory cable, that forces it into fastboot etc so you can try and get back into adb.
Click to expand...
Click to collapse
This is the best post of all time since I broke my Kindlе. I'll try it if it is not repaired at a service center.

Not sure if that's sarcasm. Note: the bulletproof vest goes on before you get shot, not after.

Thelgow said:
Not sure if that's sarcasm.
Click to expand...
Click to collapse
Well, that was the first real piece of advice he got... So I suspect that he might actually be trying to say 'thank you'

HOW TO: Install FXP113 Custom ROM on Xperia Play R800x

When installing FXP113 to my phone, I found that on bootup I would get an error on the phone process and I had no service. After trying a few different things, I finally found the solution: Install FXP112 first, then install FXP113 over it without wiping data. Here is a step by step tutorial on installing FXP113 on the R800x. It probably would work the same for all Xperia Plays.
Required: Rooted Xperia Play and unlocked bootloader.
Needed Files: FXP112 as modified by Chevyowner
FXP113 as modified by Chevyowner
Replacement build.prop file for R800x
Fastboot - Fastboot+ADB+Fastboot_Drivers.zip
Sony Drivers
Recommended: Boot into recovery and make a Nandroid backup before continuing.
1. Copy the files for FXP112 and FXP113 to your sdcard. You will need to access these from recovery.
2. Install Fastboot. Unzip the file into C:\fastboot.
5. 2. Extract the boot.img of your choice to the fastboot directory. You may use the one in FXP113, or DarkForest3.img or DarkForest4.img (available here.)
5. Enter into Fastboot Mode. - Turn off phone. Hold search button down. Plug in USB cable. The power light should be blue The first time you do this, you will be prompted for the fastboot drivers. They will be in C:\fastboot\fastboot drivers.
6. To flash the new boot image, go to a command prompt and change to the c:\fastboot directory. Then use the following command:
fastboot -i 0x0fce flash boot boot.img <----- the name of your boot image.
7. When finished, remove the usb cable. Power on the phone and enter into Recovery. On some kernels, you will press repeatedly the volume down button; on others, you will press repeatedly on the back button or possibly the search button.
8. You MUST clear Data, Cache and Dalvik Cache. It is also recommended by some people to clear the battery stats.
9. Install zipfile from sdcard. Select the FXP112 file first. Allow it to install and then reboot the phone. (I usually clear data, cache and dalvik again just to be sure.)
10. Activate your phone on the Verizon network.
11. Now shut down and reboot into Recovery again.
12. This time, clear ONLY cache and dalvik cache. Do NOT clear data.
13. Install zipfile from sdcard. Select the FXP113 file this time. Allow it to install and then reboot the phone.
14. Copy the build.prop file into /system. You may want to rename the current one first.
15. Reboot and enjoy! You should be up and running with full data, wifi access now.

re
So for step #10 do u get charged from verizon to activate ur new roms data?
And for #14 do u just copy it via root explorer to /system?
Thanks for taking time to write this

FPlusPS3 said:
So for step #10 do u get charged from verizon to activate ur new roms data?
And for #14 do u just copy it via root explorer to /system?
Thanks for taking time to write this
Click to expand...
Click to collapse
#10 There is no charge to activate the phone if you already have service. It's like dialing *228 and choosing option 1, only the system does it for you.
#14 Yes, you can just copy it to \system, but don't forget to change access to RW before pasting. You may also want to rename the old file first as a backup, although I never have.
Sent from my R800x using XDA

my phone gets stuck at the android screen after i flash fxp112

johnboyjr said:
my phone gets stuck at the android screen after i flash fxp112
Click to expand...
Click to collapse
What kernel did you use?
Did you clear data, cache and dalvik cache before you installed FXP112?
If yes, just for kicks, go clear it again.
Also, remember, the first boot after a clean install takes longer than normal.
Sent from my R800x using XDA

yes i cleared them and and i tried DarkForest4 and fxp112
i waited over 15 min still nothing

johnboyjr said:
yes i cleared them and and i tried DarkForest4 and fxp112
i waited over 15 min still nothing
Click to expand...
Click to collapse
OK. Well, if it were me, the next thing I would do is to flash back to totally stock and get that working. Then try it again.
Sent from my R800x using XDA

What changes are in your build.prop? I've been running fine (except for one or two small problems) with the standard build.prop from FXP112.

crono141 said:
What changes are in your build.prop? I've been running fine (except for one or two small problems) with the standard build.prop from FXP112.
Click to expand...
Click to collapse
I think it was just edited to identify the phone properly as an R800x. PaxChristos told me to use it when he helped me install FXP111 and I have used it ever since. I haven't had any issues at all with it, so you might give it a try if you're on Verizon.
Sent from my R800x using XDA

That was only needed the first time Chevy made FXP111 work, he missed some things in the build.prop that created graphical artifacts in menus and such. All of his builds after that have the correct build.prop now.
Sent from my R800x using XDA

*22899 is the shortcut for activating service in case anyone wanted to just store it for future reference
-and you can also use flashtool to flash back to stock or flash a new kernel

*228 worked fine for me. semcsuite.apk won't show up in my app drawer. I moved it to /system/app and fixed permissions. Still not there.
Sent from my R800x using XDA

Wallrunner said:
That was only needed the first time Chevy made FXP111 work, he missed some things in the build.prop that created graphical artifacts in menus and such. All of his builds after that have the correct build.prop now.
Sent from my R800x using XDA
Click to expand...
Click to collapse
Thanks! Good to know, and one less thing to screw with in the future!
Sent from my R800x using XDA

re
Does Psxperia or XPERIA GAMEPAD games even work on cm9

For some reason, trying use videocall in gtalk worked fine at first, but changing to rear camera made gtalk fc. After that no camera works at all.
GPS only works on maps (no on gps status, or any other app), since my wifi neighbours are all on the google database i'm not sure if the true gps is really working.
And have another annoying things.
I'm hacking all my phones since android 2.1, and I cant consider this release as an true release candidate. Its more beta.
I have a r800i.

FPlusPS3 said:
Does Psxperia or XPERIA GAMEPAD games even work on cm9
Click to expand...
Click to collapse
From what I have read... no. That is why I have not jumped ship to CM. Otherwise I would be there right now. So until they get the touchpads working I will wait, although I have also read they are working on creating from scrathc their own drivers for the touchpads as the current drivers now require SE framework...... so cross your fingers.

Nighty0 said:
For some reason, trying use videocall in gtalk worked fine at first, but changing to rear camera made gtalk fc. After that no camera works at all.
GPS only works on maps (no on gps status, or any other app), since my wifi neighbours are all on the google database i'm not sure if the true gps is really working.
And have another annoying things.
I'm hacking all my phones since android 2.1, and I cant consider this release as an true release candidate. Its more beta.
I have a r800i.
Click to expand...
Click to collapse
Not to be rude or by any disrespect but how isn't it a "true" release? A release is a release..being that it's in beta status doesn't mean it's any less, cm is always changing and improving so there is no hey this is the final version kind of thing..CDMA isn't even supported by cm at all so the fact we have cm9 before verizon gives it to us is amazing. Just to point out, this isn't hacking by any means, android is open source..it's like going into an open store and saying you're breaking in

agraceful said:
Not to be rude or by any disrespect but how isn't it a "true" release? A release is a release..being that it's in beta status doesn't mean it's any less, cm is always changing and improving so there is no hey this is the final version kind of thing..CDMA isn't even supported by cm at all so the fact we have cm9 before verizon gives it to us is amazing. Just to point out, this isn't hacking by any means, android is open source..it's like going into an open store and saying you're breaking in
Click to expand...
Click to collapse
Yes, giving their release to us is amazing, but saying that camera works on changelog, and not even the basic apps like gtalk and camera works, this barely can be considered as working.
As a software engineer I label as a beta, not RC anything. beta is to fix stopper bug like this, RC is for the little annoyances lonely.
For example, my work friend installed another rom on their htc sensation, labeled as beta and all features works, with jagged areas here and there.
And yep, I know the Team FreeXperia is a one guy team
I'm happy with all this releases, only frustrated because the thing is being labeled as working, when not. So I made a report here to make sure another person doesn't make the same mistake as me.

netizenmt said:
Thanks! Good to know, and one less thing to screw with in the future!
Sent from my R800x using XDA
Click to expand...
Click to collapse
actually this build.prop works better it lets Plants Vs Zombies and Asphalt 6 RUN and work

How do install install the custom rom and set up fastboot?

[Guide] Modding build.prop in Cm7 and Cm9

Hello all,
I was looking through, the development section when I realized there was no thread about how to edit the build.prop file.
The build.prop file helps Google Play and other apps identify what device you have.
This guide will show how to edit the file to get maximum app availability. You can also edit the file in order to change the pixel density and there are quite a few other changes as well.
(Note: This does not work on the stock kindle fire rom)
The first thing you should do is backup the build.prop file to your enternal storage.
(The build.prop file is located in the folder)
Once you have made a backup, you are free to edit it.
Change the following lines to:
ro.product.model=GT-I9100
ro.product.brand=samsung
ro.product.name=GT-I9100
ro.product.device=GT-I9100
ro.product.board=GT-I9100
(a few more rows down)
ro.product.manufacturer:samsung
Save your changes, reboot your device and you will have access to the complete android market. Gameloft games that say, "Your device is not compatible with this, game please request a refund" will work. Please note that it could take up to an hour before Google starts to think that you have a GT-I9100.
Enjoy the full market experience right from Cm7-9,
Greg

Thanks. This is a great guide!

Just a warning though: Some games/apps really are incompatible even though they may show up.

veeman said:
Just a warning though: Some games/apps really are incompatible even though they may show up.
Click to expand...
Click to collapse
This is true, but a majority of the games at least will work. It is more the Gameloft games that can start having problems.

Lemme throw this out there...
Many ROMs already have a device ID set. Currently on my gedeROM, I'm listed as a Galaxy Tab. Is the build.prop easy enough to change to any device? And could we take time to post in this thread, settings for other compatible devices? I do like my KF to be registered as a Kindle. And I would guess some device IDs offer benefits over others?

TinkerToyTommy said:
Lemme throw this out there...
Many ROMs already have a device ID set. Currently on my gedeROM, I'm listed as a Galaxy Tab. Is the build.prop easy enough to change to any device? And could we take time to post in this thread, settings for other compatible devices? I do like my KF to be registered as a Kindle. And I would guess some device IDs offer benefits over others?
Click to expand...
Click to collapse
The steps that I just posted above will work on almost any device running a stock rom or a custom rom. For some reason, it just does not work on Kindle Fire stock rom. There are benefits to each device, some device's have similar hardware as others. But if you are looking for more apps, the Nexus devices have the best app availability. just as a random example, the GT-I9100 might have a more similar processor to the Kindle then a Galaxy Nexus.
Sent from my Galaxy Nexus.

Could someone please post the original build.prop settings before making these changes.I didn't save a copy of it before I changed them and my KF has been stuck in portrait mode for some reason ever since I did this several days ago. Unfourtunately it didn't yield any better results for me in the Google Play store anyway even though my KF is rooted with KFU and I use GoLauncher.Thanks guys :laugh:

Does this work for Jellybean ROMs? I followed this guide but my Kindle Fire wouldn't boot afterwards... I'm using twa_priv's CM10 rom

technut said:
Could someone please post the original build.prop settings before making these changes.I didn't save a copy of it before I changed them and my KF has been stuck in portrait mode for some reason ever since I did this several days ago. Unfourtunately it didn't yield any better results for me in the Google Play store anyway even though my KF is rooted with KFU and I use GoLauncher.Thanks guys :laugh:
Click to expand...
Click to collapse
If you use root explorer it will save a backup for you
Sent from my LG-P999 using xda premium

eoy4 said:
Does this work for Jellybean ROMs? I followed this guide but my Kindle Fire wouldn't boot afterwards... I'm using twa_priv's CM10 rom
Click to expand...
Click to collapse
I am using the same ROM and am wondering the same thing. I will try it to see if the same thing happens to me.
Sent from my Kingle Fire running CM10 Jellybean

eoy4 said:
Does this work for Jellybean ROMs? I followed this guide but my Kindle Fire wouldn't boot afterwards... I'm using twa_priv's CM10 rom
Click to expand...
Click to collapse
It should be fine as long as you don't change anything important.

veeman said:
It should be fine as long as you don't change anything important.
Click to expand...
Click to collapse
What's an example of an app that doesn't show up using the default build.prop on my ROM?

I did this and after reboot everything seems fine except my brightness is stuck on high and nothing I've found will adjust it.
Any ideas?
Sent from Epic Touch ICS

eoy4 said:
Does this work for Jellybean ROMs? I followed this guide but my Kindle Fire wouldn't boot afterwards... I'm using twa_priv's CM10 rom
Click to expand...
Click to collapse
Had the same problem, so i booted in to recovery and wiped dalvik and cache then rebooted system.

I follow all the steps and the result is that phone is booting but the screen is tatally in black. Already did Dalvik and chache wiping proces with no lucky results...
Any idea what else I could do...
I did it on a LG Hub...
Regards

Thank you for this.........thank you very much

Wouldnt it be better if the build.prop was of a Nexus 7
All u really need to change in the build.prop is two lines
ro.product.model=Kindle Fire(or whatever it is)
ro.product.brand=Amazon(whatever it may be)
To
ro.product.model=Nexus 7
ro.product.brand=google
BTW this will work on any ROM
Sent from my Nexus 7 using XDA Premium HD app

[ROM] Ubuntu Touch [Mar-6-2014]

Better explaination of Ubuntu OS and how it relates to us.
Ubuntu OS currently run on top of an Android "shell". The android layer contains the boot.img(kernel/ramdisk), initd, vendor specific drivers etc.. This is what first boots then the ubuntu file system is loaded within this Android "shell". This is why we need flash two zips to have it working(Android and Ubuntu). Ubuntu uses CM10.1 repos for the Android shell portion of the OS. This still works for us as we had official cm 10.1, though development wasn't long lived before moving to 10.2.
There is an AOSP 4.4.2 branch Ubuntu is working on to maybe replace the CM based Android component, but it is currently less stable than the CM based. Hopefully the AOSP branch becomes more stable in the near future as the development for our device is active there.
Built from source using modified mako tree/kernel
Working:
Most things..
Power key works to turn screen on and off after a reboot
Phone/SMS
3G/Wifi
Camera
Click to expand...
Click to collapse
Bugs/Not Working:
1. Cannot seem to add account with numbers in the email. The back button is active under the keyboard and is activated when trying to switch to numerical keypad
To Import Google Contacts from computer terminal:
adb shell
sudo -u phablet -i
syncevolution --configure --sync-property "[email protected]" --sync-property "password=secret" Google_Contacts
syncevolution --sync refresh-from-server Google_Contacts addressbook
2. Vol. Keys/Caps not working... doubt cap keys will be supported as the ui is made for not having them.
3. Wifi not remembered after reboot
4. Alarms don't work
Click to expand...
Click to collapse
Install from recovery:
1. Make your Nandroid to return to
2. Full Wipe
3. Install geeb zip
4. Install ubuntu zip - This is SLOW
5. Reboot and try - There is no boot animation so just be patient.. it boots
Click to expand...
Click to collapse
Downloads:
Geeb Zip
Ubuntu Zip
Ubuntu Touch change log
Don't Forget to hit the Thanks!

Please build for geehrc too

Haze028 said:
Just for something new to try.......Ubuntu Touch(Trusty) for the Geeb. Though not a daily driver by any means.....barely useable in most respects currently.
Built from source using modified mako tree/kernel
Working:
Phone/SMS
3G/Wifi
Camera
Bugs/Not Working:
Keyboard crashes
Unable to add account
Unable to install programs which is due to 2...which is do to 1....barely functional until fixed
Vol. Keys/Caps not working... doubt cap keys will be supported.
There are really alot more bugs...alot...but those are the two key
Install from recovery:
1. Make your Nandroid to return to
2. Full Wipe
3. Install geeb zip
4. Install ubuntu zip - This is SLOW
5. Reboot and try - There is no boot animation so just be patient.. it boots
Downloads:
Geeb Zip
Ubuntu Zip
Don't Forget to hit the Thanks!
Click to expand...
Click to collapse
I don't know if this thread is helpful for you, or maybe you've alreay seen it:
http://forum.xda-developers.com/showthread.php?t=2587823
i tried it and it booted successful on my geehrc. Wifi worked, also keyboard and i could add an account too. Phone/SMS didn't work due no signal. The keyboard had also one severe bug: In the terminal the enter key didn't work.
It's worth a try, you can easily remove it, you just have to reflash your recovery ( in my case TWRP ).

New update. Running ALOT smoother.
The ubuntu zip is a nightly offered through ubuntu so you can always re download that at any point and flash overtop current installation to get the latest. It's a large file so I usually get it weekly...

Will this work on the American geeb (e970)? :-?

topdawg7793 said:
Will this work on the American geeb (e970)? :-?
Click to expand...
Click to collapse
It should.... Let me know if not.

Seriously impressed by this, good job.

Haze028 said:
It should.... Let me know if not.
Click to expand...
Click to collapse
It works! Everything seems to be working; just a few bugs here and there with the keyboard and occasional glitches in performance but very impressive for something that's unoptimized..Thanks!

Can i flash this on geehrc?why do we need to flash geeb.zip?thanks.
Sent from my Optimus G using XDA Premium 4 mobile app

sunnytse1 said:
Can i flash this on geehrc?why do we need to flash geeb.zip?thanks.
Sent from my Optimus G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Its not for sprint yet.....I'll work on that this weekend hopefully.
The geeb.zip is needed because of how Ubuntu touch works. Its currently using a mako device tree that has been converted to flash on my e973, the at&t is pretty much the exact same which is why it works for them.
First you flash a cm10.1 based Ubuntu tweaked android sysyem-- geeb.zip
Second is the Ubuntu rootfs that goes atop the android base-- Ubuntu zip

I'm totally jacked to try this. I've downloaded each file twice and tried to get this running. Thing is that the md5s are different for each file. I tried all 4 combinations and let them try to boot for 30 mins each. I must be getting bad downloads lol
Long story short: I would be super grateful for some md5s, if you get a chance
Sent by my Nexus 6 through tears in rain.

=JKT= said:
I'm totally jacked to try this. I've downloaded each file twice and tried to get this running. Thing is that the md5s are different for each file. I tried all 4 combinations and let them try to boot for 30 mins each. I must be getting bad downloads lol
Long story short: I would be super grateful for some md5s, if you get a chance
Sent by my Nexus 6 through tears in rain.
Click to expand...
Click to collapse
Seems like this is starting to happen to more people..... wondering if ubuntu zip got changed causing it not to boot. I'll try to get a booting copy up today
EDIT:
I downloaded everything myself to try and con confirm it is currently not booting. Ubuntu has changed something that has broke our display. If you reboot the phone you can turn the screen on an off with the power button. I'll hopefully fix this this weekend.. though it's a busy one for me already. See what I can do

Haze028 said:
Seems like this is starting to happen to more people..... wondering if ubuntu zip got changed causing it not to boot. I'll try to get a booting copy up today
EDIT:
I downloaded everything myself to try and con confirm it is currently not booting. Ubuntu has changed something that has broke our display. If you reboot the phone you can turn the screen on an off with the power button. I'll hopefully fix this this weekend.. though it's a busy one for me already. See what I can do
Click to expand...
Click to collapse
Thanks! But yeah, nobody here assumes this should take priority over anything in your personal life we'll get it when we get it.
Sent by my Nexus 6 through tears in rain.

This weekend ended up being a write off for me so I'll have to see when I can get to making a new working zip, or maybe its an issue from ubuntu end they'll resolve.
Did anyone that tried this and had it boot happen to still have the trusty-preinstalled zip they used? If someone has one from 8th or earlier it should boot... i unfortunatly don't have an earlier build then the 13th... you can still download the 12th and up from the ubuntu phablet site... not sure if that pre-dates the issue or not.
Edit: I havn't tried the 13th build to say if it works or not. Here is the link to the phablet site if someone wants to try an earlier build. look for the preinstalled zip at the bottom of the page after selecting the date

I'll guinea pig a couple older builds and post which one works.
Sent by my Nexus 6 through tears in rain.

Ok, again I feel a little stupid(again).... I don't empty my Trash very often at all(on my computer or in real life), just neglected to think of it til now. I have an Ubuntu zip from the 4th still there, uploading it now(upload speed is slow... won't be done for an hour or so). Going to check that it boots as it should then i'll post the link.
Again, this is just to hold over untill I can try to see what I need to change to get us booting with the nightlies again.
EDIT: Can verify now that it boots. Here is the Ubuntu zip from the 4th. Remember, not that it really matters, this is an older version than the current.

Haze028 said:
Ok, again I feel a little stupid(again).... I don't empty my Trash very often at all(on my computer or in real life), just neglected to think of it til now. I have an Ubuntu zip from the 4th still there, uploading it now(upload speed is slow... won't be done for an hour or so). Going to check that it boots as it should then i'll post the link.
Again, this is just to hold over untill I can try to see what I need to change to get us booting with the nightlies again.
EDIT: Can verify now that it boots. Here is the Ubuntu zip from the 4th. Remember, not that it really matters, this is an older version than the current.
Click to expand...
Click to collapse
Confirmed, definitely boots. And I've successfully added all my accounts, but you've gotta either tap the top-right corner of the bottom-left 'swap' key to get the @ or the numbers, or the bottom-left corner of the swap-key (depends on which account you're trying to add - some of them have the Back button in the way which you can avoid by tapping the top-right corner of the swap key, and some have the Cancel button in the way, which you can avoid by tapping the bottom-left corner of the swap key). It's a pain the arse but it works.
I want to do the Google Contacts fix, but I want to do it from the handset's terminal app (i.e. not through ADB) - how do you do a return (Enter) in the Terminal app?
EDIT: found the fix for Enter and Backspace not working in terminal app. Flash this in recovery.

adzidek said:
Confirmed, definitely boots. And I've successfully added all my accounts, but you've gotta either tap the top-right corner of the bottom-left 'swap' key to get the @ or the numbers, or the bottom-left corner of the swap-key (depends on which account you're trying to add - some of them have the Back button in the way which you can avoid by tapping the top-right corner of the swap key, and some have the Cancel button in the way, which you can avoid by tapping the bottom-left corner of the swap key). It's a pain the arse but it works.
I want to do the Google Contacts fix, but I want to do it from the handset's terminal app (i.e. not through ADB) - how do you do a return (Enter) in the Terminal app?
EDIT: found the fix for Enter and Backspace not working in terminal app. Flash this in recovery.
Click to expand...
Click to collapse
Going to add this zip yo the OP, where did you find it so I can credit them when I link it

Would I be able to flash this on e975?
Sent from my LG-E975 using XDA Premium 4 mobile app

Haze028 said:
Going to add this zip yo the OP, where did you find it so I can credit them when I link it
Click to expand...
Click to collapse
oh, man i have no clue. i was googling like mad and stumbled across it. on the plus side, im typing this on my e971 running ubuntu touch !

[Q] Probably broke it...[Resolved]

So I was working on putting on a new ROM and when I went to install the PA G Apps zip it said in my recovery that I didn't have enough space in the system storage. Which was a little confusing since I had just wiped it like usual through the recovery before I do a ROM. However I was navigating the recovery since it had been a while and just check out some of the things I didn't notice that changed. Went to the Mounts and Storage area, then I guess I touched "Format /system" and when I realized that it moved to asking me if I wanted to format /system I tried to push NO but apparently I have fat fingers and still pushed yes...So now after having rebooted the phone it is stuck at the screen "Google *small unlocked Lock at the bottom*". And now I'm not sure what to do.
Any advice?

Well this is nothing serious. Just reflash your ROM or flash the new one you werd gonna flash..
P.s. formatting system is a good idea anyway before flashing a new ROM..
Sent from my Galaxy Nexus using XDA Premium HD app

mrgnex said:
Well this is nothing serious. Just reflash your ROM or flash the new one you werd gonna flash..
P.s. formatting system is a good idea anyway before flashing a new ROM..
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Well the issue is it is stuck...I let it sit for at least 5min or so and it just sat there at that same spot. Is that because I need to reflash it? I have the Galaxy Nexus Toolkit, but I haven't used it as of late since I haven't needed it. If you don't mind going into detail I would appreciate it .
Should also mention if I go into the bootloader, it hangs at "Downloading..." so effectively I can't do anything to reflash my ROM or anything. And I probably should be clear that this all happened AFTER I flashed the new ROM and then remembered I needed the PA G Apps. Should have refreshed my memory with doing this sort of thing since I'm not as experienced as I use to be long ways back.

Ysosrslawl said:
Should also mention if I go into the bootloader, it hangs at "Downloading..."
Click to expand...
Click to collapse
Did you actually use the right combination to go to bootloader? Because from what I understand, you simply wiped your /system clean, which is a simple matter to fix - just flash any ROM or restore any valid backup to make it work again.
Sent from Google Nexus 4 @ CM11

AndyYan said:
Did you actually use the right combination to go to bootloader? Because from what I understand, you simply wiped your /system clean, which is a simple matter to fix - just flash any ROM or restore any valid backup to make it work again.
Sent from Google Nexus 4 @ CM11
Click to expand...
Click to collapse
Volume button then Power button until it vibrates then keep holding down the volume button? Only way I know how to do it, seeing as I've never heard of another way to do it.

Ysosrslawl said:
Volume button then Power button until it vibrates then keep holding down the volume button? Only way I know how to do it, seeing as I've never heard of another way to do it.
Click to expand...
Click to collapse
Yeah, make sure you hold BOTH volume keys for bootloader. Hold only VOLUME- for Download mode as you've seen before. If you indeed held both keys but still got to Download mode, chances are you have a broken volume key.
Sent from Google Nexus 4 @ CM11

Yep I'm dumb apparently and misjudged how the buttons were being pressed down...now on to step 2! Hmmm....

Seems like the zip for the ROM isnt in the storage anymore. How do I copy it back on from just being in fastboot mode or recovery? I'm not familiar with ADB at all. I may have figured out the problem so hold on...I think I derped and forgot that I removed the device drivers off my desktop because I wanted to fresh install them way back.
Edit2: Doing this the hard way.

OK SO I feel like a total noob, which I really am. I've never used ADB, never tried pushing files, or anything of the sort. I tried for a very long time to get the Galaxy Nexus toolkit to help me out but it REALLY didn't do ANYTHING for me. None of the options worked like I had hoped, the ONLY thing it did for me was to install the missing drivers I needed. Other than that it was utterly useless. You guys may find this funny, but I really had no idea on how to fix this even in the slightest. Even with the responses put here by some of the community.
However, with a little searching I was able to find the answers to my questions, not found here on XDA unfortunately. What I ended up doing was updating my SDK tools and learning how to open up ADB (had no idea why the adb.exe wasn't just opening for me like I assumed it would). From there I used the sideload option in my recovery to help me get my ROM flashed back on my phone. So now all is well and I can go back to being a noob who just likes to find good looking ROMS and play with them every couple months.
Thanks, my issue is now resolved.