Hello,
I have a Nexus 4 running Kitkat 4.4.2 and everything was good until a few days ago. I have a few accounts on the phone but the one I'm trying to fix is the corporate email - I had a stuck message (not in my Outlook inbox but in my phone inbox) and tried deleting & filing in a different folder but nothing worked. With iphones and newer Blackberry devices, you can simply remove the offending account and then add it again which usually fixes glitches like this. After removing the corporate email account from the accounts list and having it hang when trying to recreate it, I ended up doing some reading which led me to the Security section to remove the corporate email from there. Now I am able to create a corporate email account but my only options are POP or IMAP which won't work.
Any ideas...?
Peter
You probably deleted exchange services. Flash the system img file from the factory image in fastboot.
Sent from my Nexus 5
I am an Android beginner - will that wipe my N4 and does it involve rooting it?
jd1639 said:
You probably deleted exchange services. Flash the system img file from the factory image in fastboot.
Sent from my Nexus 5
Click to expand...
Click to collapse
PeterRooter said:
I am an Android beginner - will that wipe my N4 and does it involve rooting it?
Click to expand...
Click to collapse
It will not wipe your device or involve rooting, except if you haven't already unlocked the bootloader. That'll wipe your device.
Sent from my Nexus 5
PeterRooter said:
Hello,
I have a Nexus 4 running Kitkat 4.4.2 and everything was good until a few days ago. I have a few accounts on the phone but the one I'm trying to fix is the corporate email - I had a stuck message (not in my Outlook inbox but in my phone inbox) and tried deleting & filing in a different folder but nothing worked. With iphones and newer Blackberry devices, you can simply remove the offending account and then add it again which usually fixes glitches like this. After removing the corporate email account from the accounts list and having it hang when trying to recreate it, I ended up doing some reading which led me to the Security section to remove the corporate email from there. Now I am able to create a corporate email account but my only options are POP or IMAP which won't work.
Any ideas...?
Peter
Click to expand...
Click to collapse
Under add account in setting the options should look like this. (Pic attached)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 4 using XDA Premium HD app
xxISYMFSxx said:
Under add account in setting the options should look like this. (Pic attached)
View attachment 2663599
Sent from my Nexus 4 using XDA Premium HD app
Click to expand...
Click to collapse
I realize that, but it doesn't - the corporate selection isn't listed. Only POP and IMAP...
jd1639 said:
It will not wipe your device or involve rooting, except if you haven't already unlocked the bootloader. That'll wipe your device.
Sent from my Nexus 5
Click to expand...
Click to collapse
So to sum up - download fastboot, unlock bootloader and then load the system.img
I'll give it a shot this afternoon, thanks for your help.
Finally worked up the courage to try this today and ended up with a fresh phone (not what I wanted).
Here's what I did;
put phone in fastboot mode (by pressing vol up, vol down and power)
fastboot devices (to make sure it could see it)
fastboot oem unlock
fastboot flash system system.img (from Kitkat 4.4.2, same OS I was running before this crap started)
fastboot oem lock
fastboot reboot
Then I got to pick a language and start the setup, just like when it came out of the box (minus all my apps, data and pics)...
PeterRooter said:
Finally worked up the courage to try this today and ended up with a fresh phone (not what I wanted).
Here's what I did;
put phone in fastboot mode (by pressing vol up, vol down and power)
fastboot devices (to make sure it could see it)
fastboot oem unlock
fastboot flash system system.img (from Kitkat 4.4.2, same OS I was running before this crap started)
fastboot oem lock
fastboot reboot
Then I got to pick a language and start the setup, just like when it came out of the box (minus all my apps, data and pics)...
Click to expand...
Click to collapse
If you weren't unlocked before, unlocking is what wiped your device. Just flashing the system.img will not wipe the device
Sent from my Nexus 5
Related
Today I turned on my new Nexus 10 first time and then came this sh.t!!!
Could someone please tell me what's gone wrong? Developer edition? No final ROM?
Is this useful in some way or should I send it back to google???
Please help!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Kroenen66 said:
Today I turned on my new Nexus 10 first time and then came this sh.t!!!
Could someone please tell me what's gone wrong? Developer edition? No final ROM?
Is this useful in some way or should I send it back to google???
Please help!!!
Click to expand...
Click to collapse
Yes it would appear you have a developer Rom and I doubt it would be useful to anyone. Basically you have two options:
1) Send it back to Google for a replacement. (Could end up waiting a number of weeks)
2) Flash the Factory Image for the Nexus 10 which can be found at:
https://developers.google.com/android/nexus/images#mantaray
This will load the final release of JB which should be already on your device and you could be up and running in 15 mins.
dr9722 said:
Yes it would appear you have a developer Rom and I doubt it would be useful to anyone. Basically you have two options:
1) Send it back to Google for a replacement. (Could end up waiting a number of weeks)
2) Flash the Factory Image for the Nexus 10 which can be found at:
https://developers.google.com/android/nexus/images#mantaray
This will load the final release of JB which should be already on your device and you could be up and running in 15 mins.
Click to expand...
Click to collapse
If I flash the factory image .... I have restrictions? in comparison .....to take it back to Google for a replacement???
What is the better option?
When the flash is just as good .... how / with what do I flash it?
Kroenen66 said:
Today I turned on my new Nexus 10 first time and then came this sh.t!!!
Could someone please tell me what's gone wrong? Developer edition? No final ROM?
Is this useful in some way or should I send it back to google???
Please help!!!
Click to expand...
Click to collapse
Kroenen66 said:
If I flash the factory image .... I have restrictions? in comparison .....to take it back to Google for a replacement???
What is the better option?
When the flash is just as good .... how / with what do I flash it?
Click to expand...
Click to collapse
if you flash the factory image you will then be the same as everyone else, no restrictions whatsoever.
Follow this guide:
http://androidtobe.blogspot.co.uk/2011/12/galaxy-nexus-installing-ics-402-from.html
That is for the Galaxy Nexus however the same commands still apply. Just ensure you download the correct Factory Image and change the file name where appropriate.
dr9722 said:
if you flash the factory image you will then be the same as everyone else, no restrictions whatsoever.
Follow this guide:
http://androidtobe.blogspot.co.uk/2011/12/galaxy-nexus-installing-ics-402-from.html
That is for the Galaxy Nexus however the same commands still apply. Just ensure you download the correct Factory Image and change the file name where appropriate.
Click to expand...
Click to collapse
The Factory Image is no Problem:
https://developers.google.com/android/nexus/images
If I make an error in an entry, I can restart the process again or is my Nexus 10 dead/Bricked/paperweight?
Isn't there any solution to "reset" to normal state without going to unlock process and flashing all partitions manually ?
what is the normal way to get back to org. Image when "normal Nexus 10" devices are out of order ?
We urgently need root and CWM on this tablet ...8)
fogbav said:
Isn't there any solution to "reset" to normal state without going to unlock process and flashing all partitions manually ?
what is the normal way to get back to org. Image when "normal Nexus 10" devices are out of order ?
We urgently need root and CWM on this tablet ...8)
Click to expand...
Click to collapse
The normal way is to restore the device using the correct nexus factory image for your device then executing the flash all script included with the factory image. This script will flash all the necessary partitions for you and reset your device to factory stock. This method doesn't require unlocking the bootloader and doesn't require root.
Sent from my SCH-I535 using xda premium
shimp208 said:
The normal way is to restore the device using the correct nexus factory image for your device then executing the flash all script included with the factory image. This script will flash all the necessary partitions for you and reset your device to factory stock. This method doesn't require unlocking the bootloader and doesn't require root.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
So - can you give us the link to the "right" image - and write 2-3 lines how to flash ? Volume up/down Power to stock recovery etc. Copy image to where ... etc ... this would be wonderful ... thank you so much ...
Nexus 10 Factory Image:
https://developers.google.com/android/nexus/images#mantarayjop40c
You also need to set up the Android SDK, especially adb and fastboot.
Reboot to bootloader:
adb reboot-bootloader
When in fastboot mode, you can start flashing the factory images.
flash-all.bat does all the work for you.
But make sure, adb AND fastboot is working inside CMD!
Thank you very much ... we will give it a try ... even if i don't know how many user get a developer version of the Nexus 10 ... this order was normaly done ... and we were some kind of surprised when the tab was started ...8)
Oh Google .. something went realy wrong this time ... 8)
Interesting that you're the second person to have this debug ROM installed and both of you are in Germany.
Me too, same here, living in Germany.
hi, i updated my phone with the last cyanogenmod nightly as always, but when it restarted i cannot use 3g or wifi, i can't browse internal folder connected by usb and adb doesn't recognise it
i can't even try to install any drivers because it doesn't even recognise them...
help me please...
i don't know what to do
Flash the last working ROM you used. wipe cache.
Sent from my Nexus 4
bricked means the phone doesnt turn on or do anything, its essentially a "brick"
before you became a rom flasher, with a rooted phone, you should of learned your way around first, at least learn the basics when it comes to servicing your device. i bet you used a root toolkit because it was easy and you didnt have to learn anything http://forum.xda-developers.com/showthread.php?t=2367406
a. if you made a nandroid backup(you should always before flashing something new) restore it.
b. flash the latest rom that worked for you(if its still in your storage), via your recovery.
c. youll have to figure out how to get adb working on your computer and push a rom to your phone via the adb push option in your recovery.
d. if all else fails, fastboot flash the factory img and reroot.
i'm not a total newbie...
i rooted my phone (and the prevoius one, a htc tattoo) without any toolkit
if i could flash something i clearly never opened this thread -.-
-adb does not list my device
-i can't install any driver, even the one included in the official sdk
the message i get is this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
-i wiped everything
i can turn on the phone, but:
- i can't use internet neither with wifi neither with 3g -> i can't login into my google account or download another rom
- signal is absent -> i can't make phone calls or send sms
so, for me, it's a total brick
i didn't know about the fastboot option, i tried and it worked.
thank you all
il_doc said:
i'm not a total newbie...
i rooted my phone (and the prevoius one, a htc tattoo) without any toolkit
if i could flash something i clearly never opened this thread -.-
-adb does not list my device
-i can't install any driver, even the one included in the official sdk
the message i get is this:
-i wiped everything
i can turn on the phone, but:
- i can't use internet neither with wifi neither with 3g -> i can't login into my google account or download another rom
- signal is absent -> i can't make phone calls or send sms
so, for me, it's a total brick
i didn't know about the fastboot option, i tried and it worked.
thank you all
Click to expand...
Click to collapse
if fastboot worked for you, then adb should have worked. i bet it might be something as simple as updating adb/getting a new version of adb. anyways, im glad fastboot worked
Issue fixed thread closed
A guy wants to change his Nexus 4 for my actual phone, but here is the problem:
Seems like in the middle of an update to 4.4 the phone turned off suddenly
*The phone don´t charge but the battery icon shows up
*If you connect it to the charger you can enter to the recovery
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
*If you connects it to the PC you can see that it connects to "google nexus 4 bootloader image"
So, is the problem reversible? I dont want to change my phone for another with no possible repair, the guy thinks the battery is the problem
What do you think guy? Do I accept the change or is too risky?
Thanks and sorry for my english.
If the phone gets recognized on your computer while in the boot loader (the menu you see on your picture posted) you can just flash the official Google factory image. This should make the phone running again.
It seems during the 4.4 update something went wrong seeing the phones still on the .27 baseband and old version of the boot loader.
Please search the forums to on how to flash factory images using fastboot mode. There are plenty of easy manuals here.
PS: do not post the phones serial number (like on your picture). Bad people can do bad stuff
Sent from my Nexus 4 using XDA Free mobile app
Oxious119 said:
If the phone gets recognized on your computer while in the boot loader (the menu you see on your picture posted) you can just flash the official Google factory image. This should make the phone running again.
It seems during the 4.4 update something went wrong seeing the phones still on the .27 baseband and old version of the boot loader.
Please search the forums to on how to flash factory images using fastboot mode. There are plenty of easy manuals here.
PS: do not post the phones serial number (like on your picture). Bad people can do bad stuff
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
I didnt know about the serial number, I will delete the pic, but I dont know what people can do with it (if you explain to me)
So, if is safe to restore the phone I should make the change righ? what do you think? Thanks for your help!
Well, if the phone doesn't work at the moment why don't you try to make it work before you decide to trade?
I'm not entirely sure but I think the serial number is important for warranty claims and such. But generally you shouldn't let anyone know your phones serial or imei number, there's no legal/harmless reason anyone needs to know.
Sent from my Nexus 4 using XDA Free mobile app
Oxious119 said:
Well, if the phone doesn't work at the moment why don't you try to make it work before you decide to trade?
I'm not entirely sure but I think the serial number is important for warranty claims and such. But generally you shouldn't let anyone know your phones serial or imei number, there's no legal/harmless reason anyone needs to know.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
The problem is that he just want to change, he is not going to give it to me for try, for that reason I was thinking if I should do the change or not, seems like if you plug the phone to the power you can enter to the recovery like you see in the pic, but im not still sure, if Im sure about fix the phone I will do the change, but I have no way to know it :/
Can I do something just from the recovery for know if the phone have a solution? (without a pc)
Well, why wouldn't he let you try to fix it first. No way to tell if it can definetly be fixed if you can't even try.
Sent from my Nexus 4 using XDA Free mobile app
Well, I'll try to do something, hope I can fix it, I have a few hours to decide if I do the change.
Thanks buddy, I'll tell you later about my decision!.
Finally I saw the phone in person; if you plug it to the power it just blink the red led, you can access to the boot loader, and if you try to start the system the phone just show the google splash and then just turn off, I wasn't really sure about the change so I finally said no at least for now.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have a Nexus 4 in front of me with a diagonal crack from top left to bottom right corners of the screen.
The touch screen only responds on the upper half of the phone.
I have been tasked with getting the images, videos, music etc. from this phone, however as I am unable to unlock the phone I am finding it pretty difficult!
Is there any way to get the data from the phone using either software or hardware hacks?
I know there are a lot of very knowledgeable people on this forum, any information is appreciated, even if I have to open up the phone and start cutting wires!
Thank you,
- Pano
Yes there is quite a single way to do it using ADB on your computer. Do you have that set up?
Sent from my Nexus 4 using XDA Free mobile app
fredcorp6 said:
using ADB
Click to expand...
Click to collapse
I've not got that set up no, are you talking about This?
OK I installed ADB and Fastboot.
I downloaded the custom Nexus 4 recovery from Clockwork Mod.
Booted the phone into Fastboot mode
Found the phone with ADB, tried to run the recover image... the phones LOCK STATE is LOCKED
How do I get past this!?
- Pano
EDIT:
It seems your bootloader is locked. NRT will unlock it but it will wipe your data. And a locked bootloader won't allow ADB (correct me if i'm wrong)
Try doing a factory reset through Recovery, it should get rid of the lock screen and allow you to transfer stuff through USB. I never tried to so i'm not sure will it work
Mashed_Potatoes said:
Try doing a factory reset through Recovery
Click to expand...
Click to collapse
Sure this won't wipe any data :fingers-crossed:
I'll have a look into it, thanks
- Pano
Panomosh said:
Sure this won't wipe any data :fingers-crossed:
I'll have a look into it, thanks
- Pano
Click to expand...
Click to collapse
##
Hi.
Is the device still under guarantee?
If not, you maybe can open the device and get the storage out of it, if there's no other way. First try it with this program, if you give up and there's no other way, (sorry to say this) you must do that.
Or try this:
Connect your phone to the charger
Reboot it
And start in safe mode (somehow, if you're able to do.)
...or replace the screen!
I'm so sorry for you, that something like that happened.
I hope you to manage to rescue your data somehow.
I also know the bitter feeling of data loss ;(
I hope this helped.
OK just to keep all updated and in case anyone ever uses this post in the future to help them...
I have tried everything, nothing worked as it either involved use of the touch screen at some point, or required me to have previously turned USB DEBUGGING on... I have come up with a new solution :
Using the ADB I will unlock the phone using the command
Code:
fastboot oem unlock
This will WIPE all the data from the phone, however it will allow me to finally install a custom recovery mod.
I am then going to find a way to connect the phone to the computer, clone the internal memory to a virtual hard drive and then use some recovery software to get back all the data that was "erased" when I unlocked the oem
Hopefully :fingers-crossed:....
I'll keep the thread updated
- Pano
▲Important Information before Continueing!
Panomosh said:
OK just to keep all updated and in case anyone ever uses this post in the future to help them...
I have tried everything, nothing worked as it either involved use of the touch screen at some point, or required me to have previously turned USB DEBUGGING on... I have come up with a new solution :
Using the ADB I will unlock the phone using the command
Code:
fastboot oem unlock
This will WIPE all the data from the phone, however it will allow me to finally install a custom recovery mod.
I am then going to find a way to connect the phone to the computer, clone the internal memory to a virtual hard drive and then use some recovery software to get back all the data that was "erased" when I unlocked the oem
Hopefully :fingers-crossed:....
I'll keep the thread updated
- Pano
Click to expand...
Click to collapse
This will only work, if the Computer has FULL ACCESS to the file system.
The best Data-Recovery Program is IsoBuster by Peter van Hoove.
...and also, it's not just normal deleting but WIPING, so recovery chance is very low.
...Nexus 4 ALWAYS makes god-damn' problems: RedLight of Death, No MicroSD, Data Loss because of Google's Locked Bootloader.
My Advice The Next time you buy a Device with Android - Unlock the bootloader to avoid further problems.
I hope you to fix all problems. All the best / Have a nice day
Followed these instructions to unlock the bootloader and flash the latest DU to my wife's XT1575: https://forum.xda-developers.com/moto-x-style/general/guides-how-to-guides-beginners-t3200808
DU was buggy so I decided to flash stock nougat using these instructions (left bootloader unlocked): https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142
Everything seemed to go fine until we attempted to sign into her existing account and got this error: Unable to sign in to device due to an unknown error. Please try another account or try to sign in again after 24 hours.
Had no idea what that was about, so I Googled it and found out about Factory Reset Protection (FRP). I didn't find much information and the only advice I found was to wait at least 24 hours before trying again. Turned off the phone and waited a full 26 hours before turning it on again--attempted to sign in again and still getting the same error.
Any advice for what to do next?
This was the first link that popped up. Just asking, have you tried this?
antariksh said:
This was the first link that popped up. Just asking, have you tried this?
Click to expand...
Click to collapse
Thanks for the reply. I hadn't tried that yet, but I just did and it didn't seem to work. Everything happened exactly the same even after "removing" the device as per the instructions.
Screenshot from Google account: https://image.ibb.co/dbnjz6/screenshot.jpg
thejukes said:
Thanks for the reply. I hadn't tried that yet, but I just did and it didn't seem to work. Everything happened exactly the same even after "removing" the device as per the instructions.
Screenshot from Google account: https://image.ibb.co/dbnjz6/screenshot.jpg
Click to expand...
Click to collapse
Are you seeing 'Access Removed' in Google Settings?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Have you tried logging in any other GMail accounts?
antariksh said:
Are you seeing 'Access Removed' in Google Settings?[/IMG]
Click to expand...
Click to collapse
No. I saw the big red "REMOVE" button, clicked it, and got the confirmation just like the article said, but as you can see from my screenshot, it does not say "Access Removed." next to the device. There is also no more "REMOVE" button. But the interface seems slightly different from the time that article was written so perhaps that's why.
antariksh said:
Have you tried logging in any other GMail accounts?
Click to expand...
Click to collapse
Yes, tried but it won't allow it. It says that a factory reset was done on it and that I need to log in from the account that was on it. But, when I try doing that, of course I get the same error as before: Unable to sign in to device due to an unknown error. Please try another account or try to sign in again after 24 hours.
thejukes said:
No. I saw the big red "REMOVE" button, clicked it, and got the confirmation just like the article said, but as you can see from my screenshot, it does not say "Access Removed." next to the device. There is also no more "REMOVE" button. But the interface seems slightly different from the time that article was written so perhaps that's why.
Yes, tried but it won't allow it. It says that a factory reset was done on it and that I need to log in from the account that was on it. But, when I try doing that, of course I get the same error as before: Unable to sign in to device due to an unknown error. Please try another account or try to sign in again after 24 hours.
Click to expand...
Click to collapse
Not sure what causing it, but try Factory resetting the current Stock ROM or try any other custom ROM with Nano GApps.
P.S: If you currently are on Stock Nougat then flash any Custom ROM based on stock nougat.
I thought FRP didn't work with an unlocked bootloader?
antariksh said:
Not sure what causing it, but try Factory resetting the current Stock ROM or try any other custom ROM with Nano GApps.
P.S: If you currently are on Stock Nougat then flash any Custom ROM based on stock nougat.
Click to expand...
Click to collapse
The phone originally had Marshmallow. The issue with custom ROMs is reliability. Even with DU, which is known for being one of the more stable ROMs, there were a lot of glitches. For example, sometimes the camera app would open, sometimes it wouldn't, which isn't good when you've got a toddler and want to capture moments.
Maybe I'm misinterpreting what you're saying... Are you suggesting that maybe I can somehow circumvent FRP by going from a custom ROM and back to a stock ROM?
Try commenting out this line in build.prop with a # tag
Code:
ro.frp.pst=/dev/block/platform/soc.0/f9824900.sdhci/by-name/frp
antariksh said:
Try commenting out this line in build.prop with a # tag
Code:
ro.frp.pst=/dev/block/platform/soc.0/f9824900.sdhci/by-name/frp
Click to expand...
Click to collapse
Thanks. Unfortunately, I don't know how to do this. I did some Googling and found instructions that won't work for me since I can't get into the phone. Also, looking at the firmware files, I don't see any the files in question.
I called Google and they blamed Motorola and patched me through to their support line. Motorola had no clue what to do. They blamed the legally required "kill switch" but said that it should let me in if I know the right account and password, which I do, but it still doesn't work.