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
Related
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.
Hi everyone !
Here I am in a really bad situation...
I bought a second hand phone with a rom issu and the guy who had it told me he ahd no time to waste trying to make it work again, I decided to buy it thinking that nothing could resist a factory reset via ADB.
But, and if I'm here today, it's because I'm in a such a situation, I need some help, and hope you guys can find a solution or at least some leads.
when I got it:
- model 16 GB D821
- The battery was not correctly attached in the phone (i did open it and put it back how it should be and seems to work)
- it is root, bootloader unlock, with Teamwin recovery version 2.6.3.2
- bootloader version HHZ11D
I can launch the teamwin recovery, it's asking for a password when it's starts, i don't know whay BUT I did a data format seeing that some people had some problem with it and did that to fix it
In Teamwin I got 0mb of storage and no OS installed, again it could be fixable via ADB
Now the best !
I can't flash anything on the phone. I can connect to it, it's well detected, I can control it (via ADB or Fastboot) and I can even had a temporary recovery with the nexus toolkit. but:
-Impossible to flash the bootloader, I do everything right, there is not "error" but at the end nothing changes, I'm back with the HHZ11D version and not the latest on I'm trying to get the HHZ11Z.
-Impossible to flash the recovery, same as the bootloader, version teamwin 2.6.3.2.
-impossible to flash a rom, and I don't have one anyway....
Here we are, I think I tried everything, but any clue would be appreciated. I hope I can fix this...
Thanks for your help.
And finally a picture of my fastboot -w when I do one, does it seem normal to you ?
{
"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"
}
Try in fastboot, fastboot oem lock. Then reboot and see if the bootloader is locked. I'm guessing it isn't and your emmc is bad.
Sent from my Nexus 5
nothing will stick, emmc fried.
samersh72 said:
nothing will stick, emmc fried.
Click to expand...
Click to collapse
Is there anything I can do ? Seems not...
Can I change it ?
RealMyop said:
Is there anything I can do ? Seems not...
Can I change it ?
Click to expand...
Click to collapse
No, you're hosed. Rma would be the option but not in your case. You're not going to be able to flash anything.
Sent from my Nexus 5
RealMyop said:
Is there anything I can do ? Seems not...
Can I change it ?
Click to expand...
Click to collapse
Did bootloader get locked?
GUGUITOMTG4 said:
Did bootloader get locked?
Click to expand...
Click to collapse
Yes I can lock back the bootloader.
RealMyop said:
Yes I can lock back the bootloader.
Click to expand...
Click to collapse
If you can lock it, unlock it again then fastboot flash the cache.img from the factory image
Sent from my Nexus 5
You may be lucky. here you will find the cache.img on method 2. If it doesn't work, do the method 1
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
GUGUITOMTG4 said:
You may be lucky. here you will find the cache.img on method 2. If it doesn't work, do the method 1
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Click to expand...
Click to collapse
I did try and it's not working either... Is there a part in the phone I can change to fix this ?
RealMyop said:
I did try and it's not working either... Is there a part in the phone I can change to fix this ?
Click to expand...
Click to collapse
The mother board
Sent from my SAMSUNG-SGH-I727
My wife has a Samsung Galaxy S6 from Vodafone UK, and it keeps telling her she has an update (see attached photo), however, everytime she tries to run it, it reboots into (what I assume is) recovery, tries to install the update then it comes up with an exclamation mark in a yellow triangle with an Android with X's for eyes. It then reboots without installing the update?
The phone is 100% stock, never had any root or any modifications.
Any ideas why this update is failing?
Cheers
Stewart
{
"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 LG-H815 using Tapatalk
Go to recovery and do wipe cache then update. If it does not work go again to recovery and do full reset then update. If it does not work flash this latest UK Vodafone 5.1.1 ROM via odin.
http://www.sammobile.com/firmwares/download/52427/G920FXXU2POGJ_G920FVFG2BOG2_VOD/
roydok said:
Go to recovery and do wipe cache then update. If it does not work go again to recovery and do full reset then update. If it does not work flash this latest UK Vodafone 5.1.1 ROM via odin.
http://www.sammobile.com/firmwares/download/52427/G920FXXU2POGJ_G920FVFG2BOG2_VOD/
Click to expand...
Click to collapse
Thanks for the reply, the cache wipe didn't work. Don't really want to do a full wipe if I can help it. Will flashing that update via Odin do a full wipe?
May just take it to Vodafone and get them to sort it out.
Have you connected it up to a PC with smart switch and tried updating it that way? Failing that I'd take it into a samsung shop, they can flash / update it for you in about 20 minutes.
FSOP said:
Have you connected it up to a PC with smart switch and tried updating it that way? Failing that I'd take it into a samsung shop, they can flash / update it for you in about 20 minutes.
Click to expand...
Click to collapse
No, I looked at Smart Switch, and it didn't say anything about updating software, only about moving from another phone to Samsung?
We have no Samsung shops around here, would VodaFone shop do?
StuMcBill said:
No, I looked at Smart Switch, and it didn't say anything about updating software, only about moving from another phone to Samsung?
We have no Samsung shops around here, would VodaFone shop do?
Click to expand...
Click to collapse
Yeah it should have said there was an update..... no Vodafone wont have the ability to flash it for you, if there are no Samsung shops near you could try flashing yourself via odin, it's a pretty straight forward process but if it goes wrong it *can* brick your phone and it'll have to go to Samsung anyway
FSOP said:
Yeah it should have said there was an update..... no Vodafone wont have the ability to flash it for you, if there are no Samsung shops near you could try flashing yourself via odin, it's a pretty straight forward process but if it goes wrong it *can* brick your phone and it'll have to go to Samsung anyway
Click to expand...
Click to collapse
Does the odin method wipe the phone?
It shouldn't but I'd make a backup anyway, to be on the safe side.
FSOP said:
It shouldn't but I'd make a backup anyway, to be on the safe side.
Click to expand...
Click to collapse
How? (Sorry, Im currently an LG G4 user, not sure about all the Samsung stuff)
Smart switch will backup your stuff! If you need help flashing with odin there's a stock firmware sticky that guides you through everything you need to know. Or ask here I'll help.
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
Good time of the day, for some reason my phone began to get into Ramdump mode quite often, Is it because of the reusable firmware? And what can be done to fix it? Also a note, I can't flash it through the Archive, it writes an error with the Super file, but if I start flashing it through Android Flash Tool, then everything is fine
{
"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"
}
What rom are you using?
And when is this happening?
Ghostcain said:
What rom are you using?
And when is this happening?
Click to expand...
Click to collapse
This happens on any firmware when I start unlocking the screen with my fingerprint
It may happend due to bad memory from the device
Ghostcain said:
It may happend due to bad memory from the device
Click to expand...
Click to collapse
90gb free
I mean bad RAM maybe it crashes and dump the errors
Ghostcain said:
I mean bad RAM maybe it crashes and dump the errors
Click to expand...
Click to collapse
maybe) idk how fix it
Ghostcain said:
I mean bad RAM maybe it crashes and dump the errors
Click to expand...
Click to collapse
Now I will try to install a custom kernel, maybe something will change
Is this happend on stock rom to?
Try to reflash Kernel only...
It clearly says Kernel Panic which mean kernel is the problem..
Try installing Stock ROM
Max0nchik said:
View attachment 5873071
Click to expand...
Click to collapse
I have the same problem I also lost the finger print unlock . I've flashed back to stock numerous times. Trying to fix it. Every time I go to set up the fingerprint unlock I'm told that it time's out. I tried it on the new update and I've tried it on the February firmware.
nathanxbox911 said:
I have the same problem I also lost the finger print unlock . I've flashed back to stock numerous times. Trying to fix it. Every time I go to set up the fingerprint unlock I'm told that it time's out. I tried it on the new update and I've tried it on the February firmware.
Click to expand...
Click to collapse
I have an assumption that this is due to problems in slots A B, most likely some module broke them. In my case, this especially often pops up if you put a root
nathanxbox911 said:
I have the same problem I also lost the finger print unlock . I've flashed back to stock numerous times. Trying to fix it. Every time I go to set up the fingerprint unlock I'm told that it time's out. I tried it on the new update and I've tried it on the February firmware.
Click to expand...
Click to collapse
Once FPS stops working its broken for good. In almost all cases its a result of flashing something that corrupts/trips the Titan security chip. Mine hasnt worked in months.
ctfrommn said:
Once FPS stops working its broken for good. In almost all cases its a result of flashing something that corrupts/trips the Titan security chip. Mine hasnt worked in months.
Click to expand...
Click to collapse
Bro, were you able to fix this?
Max0nchik said:
Bro, were you able to fix this?
Click to expand...
Click to collapse
No, there is no fix apart from sending it back to Google (or wherever you got it)
ctfrommn said:
No, there is no fix apart from sending it back to Google (or wherever you got it)
Click to expand...
Click to collapse
Thanks for the information, but it sucks to know...
Once Titan is tripped its not really fixable as far as I can tell.