Database Info

FRF91 OTA?

FRF91 OTA just turned up on my un-rooted nexus one - not sure whats included, I already had the FRF85B OTA update earlier this week to take me from my manually (but officially google sourced) beta builds of FROYO iAnybody else seen this?
Cheers
James

I too just got this update this afternoon on my non-rooted Nexus One. I'm on T-Mobile.

Just got mine OTA as well a few minutes ago.. unrooted AWS N1 on T-Mobile.
{
"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 just got it too. Should be safe eh?
ed: Scraps. It doesn't want to apply itself if using AmonRA... :/

Come on guys, grab the url from logcat please.

just did a google search but I only find this and this and another site but no one seems to know what's been fixed
Edit // -> http://forum.xda-developers.com/showthread.php?p=7030780

This is (I hope!!) relevant info I found in logcat --
W/RecoverySystem( 555): !!! REBOOTING TO INSTALL CACHE:signed-passion-FRF91-from-FRF85B.db99fdf1.zip !!!
Does it help?
EDIT: HERE YOU GO http://android.clients.google.com/packages/passion/signed-passion-FRF91-from-FRF85B.db99fdf1.zip

Yea I just got it, straight from FRF83

Any idea what changes this build contains?

Everytime i receiv an update OTA when i reboot i get an error in the downloaded file, can it be bec i have the bootloader unlocked?
it says ts not signed or smntg

And sorry to crosspost, but does recovery-root still work on FRF91?

Unlocking bootloader will not cause update to fail. If you have custom recovery and/or custom ROM, it will.

My guess would be that it's probably a fix to the exploit which allows people to root without unlocking the bootloader.

venec said:
Everytime i receiv an update OTA when i reboot i get an error in the downloaded file, can it be bec i have the bootloader unlocked?
it says ts not signed or smntg
Click to expand...
Click to collapse
If you have changed your recovery from stock, then the OTA won't install.

AT&T
Safe to apply to AT&T phones?

rohandhruva said:
Unlocking bootloader will not cause update to fail. If you have custom recovery and/or custom ROM, it will.
Click to expand...
Click to collapse
Aha! im using Amon_RA recovery
how do i update with this?
Im trying from sd card but it wont do it either ><

ArcanaXVIII said:
My guess would be that it's probably a fix to the exploit which allows people to root without unlocking the bootloader.
Click to expand...
Click to collapse
thats exactly what i was thinking

blix247 said:
Safe to apply to AT&T phones?
Click to expand...
Click to collapse
All updates from EPE54B and up are safe as far as I know. If not, it wouldn't flash. The updates are the same for both now days.

venec said:
Aha! im using Amon_RA recovery
how do i update with this?
Im trying from sd card but it wont do it either ><
Click to expand...
Click to collapse
nvm i just went back to stock recovery, im not installing any custom ROM anyways
Yet....
Thank you

You could always just fastboot boot the stock recovery and flash it so that you don't have to reflash the recovery again.

S6 Bootloader and Modem Odin Flash Failed Red

Greetings, this might be a better place to post this. Up till now my roots have been ok and bootloader and modems are ok. But recently (yesterday) i wanted to use Xtresolite Rom again and wanted to update to newest recommend BL and Modem, however im getting a fail. I already tried a new computer so its not that. I never had this issue before and its a bit concerning.
The phone works ok, but i can no longer update the BL and Modem on it.... any ideas on how to get around this ? Reset it or something like that ? I have read that a possible complete FORMAT might fix it, but does that mean it removes everything on the phone including SDcard storage files or just the mainphone files ? Here is a screenshot of what i get in Odin, would really appreciate some 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"
}

agentdangermouse said:
Greetings, this might be a better place to post this. Up till now my roots have been ok and bootloader and modems are ok. But recently (yesterday) i wanted to use Xtresolite Rom again and wanted to update to newest recommend BL and Modem, however im getting a fail. I already tried a new computer so its not that. I never had this issue before and its a bit concerning.
The phone works ok, but i can no longer update the BL and Modem on it.... any ideas on how to get around this ? Reset it or something like that ? I have read that a possible complete FORMAT might fix it, but does that mean it removes everything on the phone including SDcard storage files or just the mainphone files ? Here is a screenshot of what i get in Odin, would really appreciate some help.
Click to expand...
Click to collapse
you phone g920i?

agentdangermouse said:
Greetings, this might be a better place to post this. Up till now my roots have been ok and bootloader and modems are ok. But recently (yesterday) i wanted to use Xtresolite Rom again and wanted to update to newest recommend BL and Modem, however im getting a fail. I already tried a new computer so its not that. I never had this issue before and its a bit concerning.
The phone works ok, but i can no longer update the BL and Modem on it.... any ideas on how to get around this ? Reset it or something like that ? I have read that a possible complete FORMAT might fix it, but does that mean it removes everything on the phone including SDcard storage files or just the mainphone files ? Here is a screenshot of what i get in Odin, would really appreciate some help.
Click to expand...
Click to collapse
If you previously firmware (OI9 and new) had it, you can return to the boot loader only to release OI9.
Older bootloader cause an error.

furkanndk said:
you phone g920i?
Click to expand...
Click to collapse
Yeah sorry i mentioned its Samsung SM-G920i

bininga59 said:
If you previously firmware (OI9 and new) had it, you can return to the boot loader only to release OI9.
Older bootloader cause an error.
Click to expand...
Click to collapse
I never had I09, pretty sure previous to this i had one B0F or something like that. What is the latest for Samsung 920i that i can try ?

agentdangermouse said:
I never had I09, pretty sure previous to this i had one B0F or something like that. What is the latest for Samsung 920i that i can try ?
Click to expand...
Click to collapse
Actually issue is resolved, i installed Samsung Phone Info from app store and i double checked my bootloader and modem installed i am already running latest bootloader from here http://forum.xda-developers.com/galaxy-s6/development/g920i-bootloader-modem-updated-10-10-t3221796
So i guess the fact is i cannot downgrade maybe thats why this is the issue. So i think all is ok
Thanks for the assistance

Bricked? + FRP Moto G 3

Hello,
I have ran out of things to try with this phone - hoping someone out there knows if there is something that can be done.
Was given the device to remove the FRP (Factory reset protection). I set up fastboot, adb drivers and started messing around with it.
First of all, I tried upgrading to the newest MM version for it using the official images from the Motorola website - turns out it does not remove the google account lock, and the version was different than the ones they use in the 'FRP bypass' videos.
Then, I tried downgrading it to 5.1.1 (the same way I did to MM, using fastboot), and some of the commands failed - resulting in the phone not booting up, unless I go straight for the Vol down + power button to get to the bootloader.
Lastly, I tried flashing an older version of MM, only to get 'failed to validate system image' on boot (picture below). Is there something that could fix this/remove the damn FRP? The warranty does not matter, the thing is unusable - any kind of ROM etc. would do. Debugging is disabled.
{
"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"
}
The loader, currently:

was the phone stolen? because why would anyone hard reset their device, just asking.
dont know any solution for you
and btw.. NEVER try to downgrade your device it can cause problems, as you see

Not sure, it was given as a collateral for a job or something, and the guy disappeared. Basically, it is either try and make it usable or just throw it away. Trying to figure out what are the options at the moment.
HelpMeruth said:
was the phone stolen? because why would anyone hard reset their device, just asking.
dont know any solution for you
and btw.. NEVER try to downgrade your device it can cause problems, as you see
Click to expand...
Click to collapse

You need to re-flash the latest firmware you flashed to your device boot again. To downgrade you have to unlock the bootloader first, but the OEM unlock setting in developer settings must be turned on, what I think you can't do with the FRP lock.

coolizard said:
You need to re-flash the latest firmware you flashed to your device boot again. To downgrade you have to unlock the bootloader first, but the OEM unlock setting in developer settings must be turned on, what I think you can't do with the FRP lock.
Click to expand...
Click to collapse
Ok, I flashed it again, it's 6.0.0. I even managed to get into the settings by doing the usual FRP bypass, however, this version does not have the developer options enabled by clicking the build number, and the 'users' setting is not there, therefore I cannot enable USB debugging like everyone does.

Your first error was upgrading to the latest version, because the newest version they have fixed.
I don't know if this will help, but in fastboot mode try to format system, and reflash the stock!

ExaHamza said:
Your first error was upgrading to the latest version, because the newest version they have fixed.
I don't know if this will help, but in fastboot mode try to format system, and reflash the stock!
Click to expand...
Click to collapse
I realize my mistake now :/ Tried formatting, reflashing.. I guess it's called Factory Reset Protection for a reason eh

Enirox said:
I realize my mistake now :/ Tried formatting, reflashing.. I guess it's called Factory Reset Protection for a reason eh
Click to expand...
Click to collapse
have you unlocked?
Sent from my MotoG3 using Tapatalk

ExaHamza said:
have you unlocked?
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
No, I have not. Had a real laugh though - I was able to access the settings - disable setup wizard - open chrome using google now, download apk's (like nova launcher) and have a home screen, browse apps all while FRP'ed. No go on the debugging/reset though :crying:

If can install apps try to root it with kingroot, and replace the stock recovery with TWRP, then format everything, and put another ROM into, after that reflash your stock. I don't know if you can do this without unlocking the bootloader.
I have seen some devices allowing do root + TWRP, without unlocking the bootloader. But you can try it!
Sent from my MotoG3 using Tapatalk

Fastboot stuck, recover images

I had the unfortunate accident of my 4a going through a full laundry cycle. I didn't expect it to even turn on, but it did.
No I am stuck at pic related.
Perhaps the memory is gone for good or something else? I am not expecting the phone to work normally, but I would like to get some pictures in their original quality, including some videos that exist only there.
Any ideas what I can do on my own? How realistic would it be for a recovery shop to be able to do it?
{
"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"
}

Gentoo11 said:
I had the unfortunate accident of my 4a going through a full laundry cycle. I didn't expect it to even turn on, but it did.
No I am stuck at pic related.
Perhaps the memory is gone for good or something else? I am not expecting the phone to work normally, but I would like to get some pictures in their original quality, including some videos that exist only there.
Any ideas what I can do on my own? How realistic would it be for a recovery shop to be able to do it?View attachment 5252011
Click to expand...
Click to collapse
Since you're stuck at fastboot, you could try to flash full factory image...although, I wouldn't keep my hopes up high...
Let it rest for a full day first. Hopefully not all of it's main components were affected....

Typhus_ said:
Since you're stuck at fastboot, you could try to flash full factory image...although, I wouldn't keep my hopes up high...
Let it rest for a full day first. Hopefully not all of it's main components were affected....
Click to expand...
Click to collapse
It has been a few days since the event. Wouldn't flashing a factory image delete all the data I am hoping recover, though?
Or do you just mean the boot image?

Gentoo11 said:
It has been a few days since the event. Wouldn't flashing a factory image delete all the data I am hoping recover, though?
Or do you just mean the boot image?
Click to expand...
Click to collapse
No, I mean full factory image.
To retain your data you just need to remove the "-w" flag you see at the update command on the flash-all script.

This is what I get

Gentoo11 said:
This is what I get
View attachment 5252097
Click to expand...
Click to collapse
Seems to me that your bootloader is locked. You didn't unlock your bootloader, did you? If not, that won't work.
You could try the full OTA instead of factory image. See if it works.

Typhus_ said:
Seems to me that your bootloader is locked. You didn't unlock your bootloader, did you? If not, that won't work.
You could try the full OTA instead of factory image. See if it works.
Click to expand...
Click to collapse
I did unlock it, though. The phone is supposed to be rooted and all too.

Question i screwed up [SOLVED]

i tried to flash 3qtr with pixel flasher now im in a loop and not sure how to fix can anyone 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"
}

Can you get into bootloader? Completely turn off the phone. Then wait a few seconds to make sure it is off. Afterwards, press power and volume down at the same time until you see bootloader menu.
If you can get into bootloader, go to android flash tools website and reflash.

When the screen goes black to reboot, hold down power + volume down. You should boot to bootloader doing that. Then you can flash the factory image and that should fix it... I think. I've never used Pixel Flasher before. I just do everything manually myself.

xdeeranx said:
Can you get into bootloader? Completely turn off the phone. Then wait a few seconds to make sure it is off. Afterwards, press power and volume down at the same time until you see bootloader menu.
If you can get into bootloader, go to android flash tools website and reflash.
Click to expand...
Click to collapse
yes i can

jdog94 said:
yes i can
Click to expand...
Click to collapse
Then you can can either download the factory image to manually patch (making sure to use platform tools r33.0.3 and NOT latest) or you can use android flash tools the website (If you use website, it's just follow instructions, select the image you want to flash, select options, then flash).

jdog94 said:
i tried to flash 3qtr with pixel flasher now im in a loop and not sure how to fix can anyone help?
Click to expand...
Click to collapse
Are you rooted and do you have any Magisk modules installed? Sounds like maybe a Magisk mod may be in need of an update and caused a bootloop. If this is the case, you can choose to disable Magisk mods in Pixel Flasher and flash again.
Kind of hard to tell without much details given...

Worked thanks So much

I was rooted not sure how I screwed up back to factory now

jdog94 said:
I was rooted not sure how I screwed up back to factory now
Click to expand...
Click to collapse
If you reflashed the image you remove root. Just reroot and you'll be okay.

Still not sure how to do 3qtr beta without screwing up

jdog94 said:
Still not sure how to do 3qtr beta without screwing up
Click to expand...
Click to collapse
Like what Lughnasadh said, it is hard to pinpoint the reason why it screwed up without enough information. Could be platform tools depending on what version you used. And it could also be your magisks modules that are causing the loop. Or the options you selected in pixel flasher. Not sure tbh. Or maybe an entire problem we aren't aware of lol.
Personally, what I would do is a clean flash. Cleanest way to do it. Just back up everything. Do a clean install of the image. Reroot and reinstall all apps/modules afterwards.

xdeeranx said:
Like what Lughnasadh said, it is hard to pinpoint the reason why it screwed up without enough information. Could be platform tools depending on what version you used. And it could also be your magisks modules that are causing the loop. Or the options you selected in pixel flasher. Not sure tbh. Or maybe an entire problem we aren't aware of lol.
Personally, what I would do is a clean flash. Cleanest way to do it. Just back up everything. Do a clean install of the image. Reroot and reinstall all apps/modules afterwards.
Click to expand...
Click to collapse
Thanks