Database Info

EVO OTA is here

take a look guys
http://androidforums.com/htc-evo-4g/90893-ota-update-1-32-651-6-a.html

Interesting...
I am running Flips "stock" rom, and no prompt for this...
Did a "firmware" update... none found.
Did a HTC Software Update... found it.

post the zip so flipz and toast can have a look at it

extrafuzzyllama said:
post the zip so flipz and toast can have a look at it
Click to expand...
Click to collapse
{
"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 used the search function in Root Explorer, but found neither "OTA_Supersonic" or "update.zip"
It must be in one of those folders that need root to view (right now I'm stock no root) like /data or something

DO NOT ACCEPT THE UPDATE FOR NOW ...MORE LATER FROM Matt, Ozzeh,Joshua and zule...

https://twitter.com/unrevoked
There's an OTA update we just got on the #EVO that breaks the root. Don't install it if you want to root.
Click to expand...
Click to collapse

Well that sucks...

upload it so the devs can see whazzz up!

Here's a copy of the sprint hero ota that I got at the same time and it supposedly (not gonna test it) breaks root. I'm pretty sure it's really a super cool update to make are phones ten times better

Just got back home. Super glad I saw this thread. I had the guy at radioshack cancel the update when it came up (he had to turn phone on to complete activation, he said).
He mentioned that for the other 6 phones he did that morning, he let the update install

GumboChief said:
Just got back home. Super glad I saw this thread. I had the guy at radioshack cancel the update when it came up (he had to turn phone on to complete activation, he said).
He mentioned that for the other 6 phones he did that morning, he let the update install
Click to expand...
Click to collapse
99% of the population is better off with the update due to the storage fix. Rooters are a tiny group of people, relatively speaking.

The guy at Sprint almost ran the update since they do have to turn the phone on to activate it, however since I didn't need anything else he just told me to make sure to update and told me how and even offered. I told him I'd get right on it as I go outside. But yea the OTA is probably best for most consumers buying this device (especially after the conversations that took place this morning) as just about everyone else there this morning just wanted to get the phone switching from various carriers from T-Mobile and ATT and just wanted it to work. There was like one other guy there who was pretty knowledgeable buying the phone outright like I was, but he claimed again he just wants the phone to work no jumping through hoops and knows about rooting but has no intentions to. The guy in charge was emphasizing to his staff to make sure to push the update. I just happened to luck out.

anyone got pre and post ota version numbers so I can confirm my unit hadn't been updated before handing it over? Thanks

FuManChuu said:
anyone got pre and post ota version numbers so I can confirm my unit hadn't been updated before handing it over? Thanks
Click to expand...
Click to collapse
1.32.651.1 ->Shipping
1.32.651.6 ->OTA

I was running flipz stock got the notification last night at like 3am and updated. Not sure if it closed root access because I could still go into the recovery screen and navigate the menus to flash, wipe etc.

princem131 said:
I was running flipz stock got the notification last night at like 3am and updated. Not sure if it closed root access because I could still go into the recovery screen and navigate the menus to flash, wipe etc.
Click to expand...
Click to collapse
That sounds promising. Look at the rom version in the about section of settings. Does it end with a 1 or a 6?

princem131 said:
I was running flipz stock got the notification last night at like 3am and updated. Not sure if it closed root access because I could still go into the recovery screen and navigate the menus to flash, wipe etc.
Click to expand...
Click to collapse
are you able to type su thru adb shell or connectbot on the localhost after applying the OTA while stil using flipz stock with root ROM?

um i tested... OTA applied... Rooted, recovery, NAND backup... it all worked...USB debugging Enabled on plugin. Installed 64bit ADB drivers and boom!
no problem to fear the root loss
um crap... nvm apparently i didnt update...
i swear I downloaded, installed, restarted the phone to allow install... but it shows software number 1.32.651.1.
maybe because I did a factory reset? then that would mean that this update is rather a patch (ie like a cab fix)??
or did the update not apply?

Tilde88 said:
um i tested... OTA applied... Rooted, recovery, NAND backup... it all worked...USB debugging Enabled on plugin. Installed 64bit ADB drivers and boom!
no problem to fear the root loss
Click to expand...
Click to collapse
But does that retain the update fix for the sdcard?

damn i updated what am i supposed to do now ?

[Q] Problems with LGP999 Wind

A friend and I were trying to update his Wind LGP999 phone from 2.2 to 2.3. So we followed the instructions from this thread http://forum.xda-developers.com/showthread.php?t=1327929 and things were going good until we got to the connection part. The program continues to freeze and close and the phone is stuck on the s/w update please wait while updating screen. Now we've tried hard reset and even tried to reinstall V10G_00 but the program still freezes. I've been doing some research and unless I haven't searched enough I haven't seen any thread or post with someone with the same problem. So any help in this would be greatly appreciated.
Edit: Done some more research and found How To Load a Custom ROM by David Cogen from The Unlockr and follower his steps and things seemed to work out pretty well but I still get this screen
{
"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 anyone please help with this?

You need to use nvflash to install clockwork recovery then you will be able to install whichever rom you want. There are a few threads out there showing how to install the recovery permanently.
Don't worry you aren't bricked
Edit: Here is a thread that will be useful for ya:
http://forum.xda-developers.com/showthread.php?t=1056847
Pin it to Win it.

I.R.Chevy said:
You need to use nvflash to install clockwork recovery then you will be able to install whichever rom you want. There are a few threads out there showing how to install the recovery permanently.
Don't worry you aren't bricked
Edit: Here is a thread that will be useful for ya:
http://forum.xda-developers.com/showthread.php?t=1056847
Pin it to Win it.
Click to expand...
Click to collapse
Thanks for the post but I've already used nvflash to install CWR and have tried multiple roms and all have ended in the same way. I know I've been doing it right because I even followed the video from the unlockr to the T but at the end where he reboots I instead get the same screen in my earlier post. Is it possible I'm doing something wrong or maybe using the wrong roms?

Its most likely you are just missing a step somewhere. Try heading to the Hellfire rom help thread and read through there see if your missing something.... Usually this is a cut and dry process I don't see how its not working for you ...
Edit:
http://forum.xda-developers.com/showthread.php?t=1513387
Pin it to Win it.

I.R.Chevy said:
Its most likely you are just missing a step somewhere. Try heading to the Hellfire rom help thread and read through there see if your missing something.... Usually this is a cut and dry process I don't see how its not working for you ...
Edit:
http://forum.xda-developers.com/showthread.php?t=1513387
Pin it to Win it.
Click to expand...
Click to collapse
Thanks for thee help I really do appreciate it. And I do believe I found the missing step, some where along the line I thought flashing and rooting where the same so when I flashed CWR I didn't root the phone before I started. And since I'm stuck on that screen does that mean I pretty much screwed?

KingsKnight21 said:
Thanks for thee help I really do appreciate it. And I do believe I found the missing step, some where along the line I thought flashing and rooting where the same so when I flashed CWR I didn't root the phone before I started. And since I'm stuck on that screen does that mean I pretty much screwed?
Click to expand...
Click to collapse
Not at all. Just use nvflash rom for recovery. It will put completely stock tmo 2.3.3 . On phone, sorry no links. Search for that and it should give you a bootable phone. Then just nvflash cwm recovery and flash rom of choice. Don't forget to wipe data. No root required.

I dunno if mentioned before but when I used the method from these links http://forum.xda-developers.com/showthread.php?t=1327929 & http://forum.xda-developers.com/showthread.php?t=1473781 once I had gotten to installer update part it had a connection error which brought me to my present situation also now whenever i tried to repeat the process the program freezes and crashes. If it were my phone I'd just forget the whole thing but since it's my friends I'd rather fix this problem if possible.

KingsKnight21 said:
I dunno if mentioned before but when I used the method from these links http://forum.xda-developers.com/showthread.php?t=1327929 & http://forum.xda-developers.com/showthread.php?t=1473781 once I had gotten to installer update part it had a connection error which brought me to my present situation also now whenever i tried to repeat the process the program freezes and crashes. If it were my phone I'd just forget the whole thing but since it's my friends I'd rather fix this problem if possible.
Click to expand...
Click to collapse
This is what I meant: http://forum.xda-developers.com/showthread.php?t=1248644 That should fix it, and then follow this: http://forum.xda-developers.com/showthread.php?t=1056847 and you should have cwm.

tahahawa said:
This is what I meant: http://forum.xda-developers.com/showthread.php?t=1248644 That should fix it, and then follow this: http://forum.xda-developers.com/showthread.php?t=1056847 and you should have cwm.
Click to expand...
Click to collapse
Well i followed the link and the instructions and now the phone wont even turn on. So the question is what now?
Edit: Battery was dead, charging now

KingsKnight21 said:
Well i followed the link and the instructions and now the phone wont even turn on. So the question is what now?
Click to expand...
Click to collapse
No white LG logo? Or nothing at all? Which link were you following? If it was the first one, then you may want to try it again, I was in the same situation. Not even backlight worked, but I used the NVflash script again and it booted to T-Mobile official 2.3.3 unrooted. Did you hold the volume buttons the entire time?

tahahawa said:
No white LG logo? Or nothing at all? Which link were you following? If it was the first one, then you may want to try it again, I was in the same situation. Not even backlight worked, but I used the NVflash script again and it booted to T-Mobile official 2.3.3 unrooted. Did you hold the volume buttons the entire time?
Click to expand...
Click to collapse
Battery was just dead, it workin now and thank you very much for the help

KingsKnight21 said:
Battery was just dead, it workin now and thank you very much for the help
Click to expand...
Click to collapse
Phew. I thought something went REALLY wrong. -.-' No problem. If ever you have a problem, and want support ASAP, PM me now and take down my email, or just PM me in the future and I'll see what I can do .

tahahawa said:
Phew. I thought something went REALLY wrong. -.-' No problem. If ever you have a problem, and want support ASAP, PM me now and take down my email, or just PM me in the future and I'll see what I can do .
Click to expand...
Click to collapse
I'll do just that Thanks again.

[Q] Rooted 3G Xoom - Trying to Update to 3.1

Ok, so here's my dilemma (And btw, I am not new to this, but it seems as though Motorola is a bit trickier than Samsung when it comes to Rooting IMO. Maybe it's just me.
I recently, through the help of a couple Online Video Tutorials created by SleeplessNinja (Whom btw, is bad ass!!! For all the work he has done!!! I have learned more from him and his Video Turtorials about ADB, fastboot, and Command Prompt in these last few weeks, than I have in all of the short time that I have been working with Android.) I reverted my 3G Xoom back to its ORIGINAL state, like it was the day I took it out of the box, fresh from the HoneyComb 3.0.1 Farm. After doing so I then followed this up by installing a version of CWM (made by Solarnz) through fastboot/ADB. The CWM version is "recovery-Tiamat-R4c-100611-1150-cwm". I then Rooted my Xoom as well with the Universal-Xoom-Root.zip file. In this process, I also flashed a new boot.img, system.img, userdata.img that were all required in order to gain the precious Root that I so badly wanted, rather, needed!​So here I am, with my Xoom freshly rebooted, and smiling with it's now huge Rooted Smile! And what do you think happened next? Oh what do we have here? But an OTA update for the wonderful HoneyComb 3.1! Oh what to do? Do I risk losing my recently gained Root? That, which I went through so much to achieve? Or do I bite the bullet and go for it? Well, instead, I immediately turned off my Xoom, before it could even start downloading the update. I then sifted through countless pages upon pages here in the XDA Forums (Which btw, is the absolute greatest place ever!!! I just had to throw that out there) in the Xoom section, all of which describe ways to update your Rooted 3G Xoom running HoneyComb 3.0.1 to HoneyComb 3.1 they just seem to do it different ways, and some enable you to keep Root, and some you have to lose Root, and then ReRoot once finished.​What I can see is that for the most part it looks as though to go from 3.0.1 to 3.1 one would have to do a similar download of the required boot.img, system.img, recovery.img, as well as the required 3G radio files, and push them through by way of either ClockWorkMod Recovery, or by pushing it through ADB/fastboot. Only thing is, all of the files, or links to files, and I DO MEAN ALL OF THEM, seem to be DEAD links. They either take me to a page that says forbidden, or they take me to an iLivid download page?​Finally, just now, just a few minutes ago, I said screw it and bit the bullet. I decided to download the OTA update and try and just ReRoot after this process finished. Well can you guess what happened when my Xoom restarted? It went into recovery mode for some reason. And at the moment, I am not really sure why?​
I received an Error message that says the following:
ClockWorkMod Recovery v3.2.0.0 (solarnz-R4c-100611-1150)
E:Can't open /dev/block/mmcblk1p3
(No such file or directory)
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I am including picture to the Recovery screen so that everyone can see exactly what it looks like.
{
"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 hope that someone can help me out. I just want to be able to update my Xoom to 3.1 as well as have my Root. I know that there are plenty of ways to do so, and I am fairly comfortable with pretty much every method. Whether it be Command Prompt(ADB/fastboot) A SuperOneClick Method, or installing a modified Recovery and modded System and Boot .img's. Please Help!

I don't know if I got what you mean, but let's see...
First you have to reinstall the Stock Version, the problem is that you'll lose your root access and your data will be formated. After you install the Stock Version again don't root and receive the updates, if I am not wrong you have an Everest Xoom, so you can update until Android 4.0.X, after you update check the FAQ to reroot your Xoom
Wish you all the best!
"This Story Ends Where It Began" - Octavarium (Dream Theater)

XxLordxX said:
I don't know if I got what you mean, but let's see...
First you have to reinstall the Stock Version, the problem is that you'll lose your root access and your data will be formated. After you install the Stock Version again don't root and receive the updates, if I am not wrong you have an Everest Xoom, so you can update until Android 4.0.X, after you update check the FAQ to reroot your Xoom
Wish you all the best!
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Click to expand...
Click to collapse
Thank you very much XxLordxX, all input is welcomed, and very much appreciated, but unfortunately that's not quite it. Allow me to try and simplify:
I am not concerned at all about formatting, and losing any data.
1. What I want to know is, what do these Error messages that I'm now receiving every time I boot into my Custom Recovery mean? Does anyone think I should go about re-installing the Custom Recovery again? The one that is currently installed, the one that I originally installed when I Rooted the Honeycomb 3.0.1? Or should I just go ahead and install a more current version of CWM?
2. Also, why do you suppose that after the OTA download of the Honeycomb 3.1 update was completed and the Xoom restarted, it booted into the Recovery and started giving me those Error messages? I personally think that there is an issue with the OTA Honeycomb 3.1 update, and how it syncs up with this Custom Recovery that I have installed that was created by Solarnz. (Whom by the way does bad ass work!!! It was working flawlessly up until I decided to try and update. LOL. So I want to be clear that I am NOT placing blame at ANYONE but MYSELF as to why I am receiving these error messages. LOL. I just had to add that last line in case somebody took anything I have previously stated in any way offensive.
I just am hoping that someone hear can possibly help me out with correcting the issue/issues at hand.
I may end up just re-installing everything back to stock, and then doing like XxLordxX and just updating my 3G Stingray Xoom through OTA, until I get to the desired OS. Decisions decisions....

DannyShane said:
Thank you very much XxLordxX, all input is welcomed, and very much appreciated, but unfortunately that's not quite it. Allow me to try and simplify:
I am not concerned at all about formatting, and losing any data.
1. What I want to know is, what do these Error messages that I'm now receiving every time I boot into my Custom Recovery mean? Does anyone think I should go about re-installing the Custom Recovery again? The one that is currently installed, the one that I originally installed when I Rooted the Honeycomb 3.0.1? Or should I just go ahead and install a more current version of CWM?
2. Also, why do you suppose that after the OTA download of the Honeycomb 3.1 update was completed and the Xoom restarted, it booted into the Recovery and started giving me those Error messages? I personally think that there is an issue with the OTA Honeycomb 3.1 update, and how it syncs up with this Custom Recovery that I have installed that was created by Solarnz. (Whom by the way does bad ass work!!! It was working flawlessly up until I decided to try and update. LOL. So I want to be clear that I am NOT placing blame at ANYONE but MYSELF as to why I am receiving these error messages. LOL. I just had to add that last line in case somebody took anything I have previously stated in any way offensive.
I just am hoping that someone hear can possibly help me out with correcting the issue/issues at hand.
I may end up just re-installing everything back to stock, and then doing like XxLordxX and just updating my 3G Stingray Xoom through OTA, until I get to the desired OS. Decisions decisions....
Click to expand...
Click to collapse
I suppose those errors messages is because you aren't on Stock Recovery, however you can't just install the Stock Recovery, because custom ROMs doesn't support it. I think there's no problem with the OTA Package, although the recovery is a problem, because it's custom. As you told you're not concerned about formatting your tablet, do it and install Stock again, then you update until the version you want, after that you root again
For more info about restoring to Stock and Rooting visit the FAQ
(BTW, are the same DannyShane from U|A? Because I'm the same XxLordxX as the one at U|A lol)
"This Story Ends Where It Began" - Octavarium (Dream Theater)

New Update - QC2

According to the Verizon Galaxy S5 Update Page:
This software update provides the latest Android™ security patches, fixes an email issue and updates the Amazon Shopping app.
Email update:
Fixes an issue that prevented Outlook® 2007 and 2003 users from accessing and downloading email attachments.
Click to expand...
Click to collapse
Please note that if you happen to play Pokemon GO or any game which "GPS Spoofers" take advantage of, the March Security Patch, and this update will prevent GPS Spoofing.
Also, I'm not entirely sure yet as to whether the Samsung Patch for Qualcomm Galaxy S5 bootloaders included in the March Security Patch will affect the ability to have a Developer bootloader anymore:
SVE-2016-7930: Multiple Buffer Overflow in Qualcomm Bootloader
Severity: Critical
Affected versions: Galaxy S5 with Qualcomm AP chipset
Reported on: December 20, 2016
Disclosure status: Privately disclosed.
A buffer overflow vulnerability exist in Qualcomm bootloader.
The patch prevents buffer overflow by removing the problematic source code.
Click to expand...
Click to collapse
I, personally, am not willing to test this, but if anyone does, please post your results. I'll upload an aboot free (Dev Friendly) firmware as soon as possible in case anyone wants to test it.
I'm currently in the process of downloading/uploading the Odin firmwares right now. I'll update this post when they are uploaded.
EDIT:
Stock No-Wipe FW. Will remove Developer Status Bootloader: G900VVRU2DQC2_G900VVZW2DQC2_G900VVRU2DQC2_HOME.tar.md5.zip
Developer Bootloader Friendly:
G900VVRU2DQC2_G900VVZW2DQC2_G900VVRU2DQC2_HOME_No_Aboot.tar.md5.zip

If it breaks something that I warned about, please reply.
If it breaks something that I didn't warn or know about, please share with everyone else.

I'm guessing no replies and no ROMs based on QC2 means noone has tested it yet.
I'm going to flash the aboot free version to one of my CID 15 S5's later tonight so I'll reply with results.

I'm gonna try it out when I get a chance this week. Thanks!

Has anybody tried this?

robbyoconnor said:
Has anybody tried this?
Click to expand...
Click to collapse
Not yet I'm gonna download this once I get to a pc definitely
Sent from my SM-G900V using Tapatalk

Kastro1784 said:
Not yet I'm gonna download this once I get to a pc definitely
Click to expand...
Click to collapse
You can use Flaahfire by the way.

Download /installed last night.Havent had time to dig around. Precursor look has only shown latest Android security updates.

Dudash said:
I'm going to flash the aboot free version to one of my CID 15 S5's later tonight so I'll reply with results.
Click to expand...
Click to collapse
How we looking, captain?

I recently was pushed the QC2 update with the March 2017 security package. I have noticed a significant decline in performance and battery life. Anyone in the same boat?
It seems like they have pushed a security updated every other month or so for the last 6 months. It is very irritating. I want to go back to root but it is too much of a hassle to figure it out at this point. I feel like they are deliberately doing these updates to make the S5 run worse and feel more outdated so you are more inclined to go buy a new one. Really sick of the whole game that is the telecom industry.
I am going to try doing a factory reset (very annoying) and see if that helps. Hopefully I can hold out long enough for the Pixel 2.

@Dudash QD1 is up, can you upload it to AFH. thanks in advance.

Noooooo! I flashed the Dev friendly QC2 modem and it seems to have killed my dev bootloader and wiped my phone!
I'll keep messing around and see if it can't be remedied. I could just punch myself for being so ambitious, though.
Edit 1: It was taking forever on the Verizon logo, so I pulled the battery and rebooted to recovery. It wiped TWRP and put in stock. I booted to Download Mode, and it still reads MODE: Developer (which I hope to God means my Dev bootloader is retained).
Edit 2: TWRP sucessfully re-flashed. The "Custom" with unlocked lock icon has reappeared on the boot screen, along with the yellow text at the top (so clearly, I was wrong about losing Dev status. Whew! I just freaked out when I saw a plain boot screen and the dreaded Verizon logo :silly. My installation of Lineage OS is clearly gone, but, peeking through TWRP's file manager appears to indicate my media data (photos, downloads, etc.) may yet have survived. I'll flash Lineage and GApps and see what happens.
Edit 3: Lineage OS booted successfully (made easier with the help of an SD card-- hooray for those things, amirite?), with QC2 baseband intact! Hooray! And my downloads and pictures and everything survived too.
Lesson: Always make a nandroid backup when doing this sort of thing! It takes a while, and it's morbidly annoying, but had I done it, I probably wouldn't've had to start from scratch. But hey, got the new baseband, and still running Lineage, so I call this a win. Cheers, everyone! And thanks to OP for posting updates!
Follow-up: Since it doesn't seem like we can flash only the new basebands by themselves, I've found a tactic that does the trick for those of us on not-stock ROMs. Boot into TWRP and make a backup of Boot, System, and Data (notice there's a Modem option-- leave it unchecked). I imagine it's best to put the backup image on an SD card. Then Odin the dev-friendly firmware update (I used the no-wipe option). Let the phone restart, then Odin the most recent TWRP back on there. Boot into TWRP, do a Factory Reset Wipe, and restore the backup you made. Takes a little while, but it does leave you with your phone as it was, but with the new baseband. :victory:
{
"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"
}

mohammad.afaneh said:
@Dudash QD1 is up, can you upload it to AFH. thanks in advance.
Click to expand...
Click to collapse
In the process of uploading right now.

Dudash said:
In the process of uploading right now.
Click to expand...
Click to collapse
??? thanks

J-Lindo said:
How we looking, captain?
Click to expand...
Click to collapse
I totally missed this reply. I flashed QC2 onto one of my S5's and it remained a Dev Edition. Then earlier today I flashed QD1 onto my other S5 and it remained a Dev Edition as well. Faking GPS doesnt work on either anymore but they keep Dev status.

Dudash said:
I totally missed this reply. I flashed QC2 onto one of my S5's and it remained a Dev Edition. Then earlier today I flashed QD1 onto my other S5 and it remained a Dev Edition as well. Faking GPS doesnt work on either anymore but they keep Dev status.
Click to expand...
Click to collapse
No problem! I'm sure you've already seen the results of my first (embarrassingly n00bish) independent baseband flash :laugh:
I appreciate the response, though. Fortunately, I'm not into GPS spoofing, so this isn't an issue for me. When you say you flashed QC2 and QD1, do you mean strictly the basebands without the bootloaders, or did you flash the entire updates and still retain Dev status?

J-Lindo said:
No problem! I'm sure you've already seen the results of my first (embarrassingly n00bish) independent baseband flash :laugh:
I appreciate the response, though. Fortunately, I'm not into GPS spoofing, so this isn't an issue for me. When you say you flashed QC2 and QD1, do you mean strictly the basebands without the bootloaders, or did you flash the entire updates and still retain Dev status?
Click to expand...
Click to collapse
I flashed the entire firmware minus the aboot.

[Solved!] [SM-G955F] RMM state still locked after 7 days (RMM State Prenormal)

I've been trying to install TWRP on my phone for about 3 weeks straight now and i keep running into this exact same issue.
Basically, every time I try to flash anything other than a stock ROM the flash fails and i get "Only official released binaries are allowed to be flashed(RECOVERY)" on my phone's Download screen. (Here's an pic of Odin when the flash fails)
I've tried flashing the latest carrier-unlocked stock ROM to it, and using the phone for 2 week without rebooting (was constantly connected to the internet, uptime was around 300 hours before i attempted to flash TWRP again). I've also tried some solutions I've found on the XDA forums (like flashing the nougat bootloader to my phone, and changing back the time by a month) but nothing appears to work.
I also got the phone used if that's any useful info.
The "OEM Unlock" option was also enabled for some reason after enabling Developer Options. And i also made the mistake of resetting the phone via the recovery menu since i didn't know the previous owner's Samsung account password to remove it from the phone (I'm guessing that's the thing that initially triggered it?)
The phone is also from Spain (but i flashed a stock ROM from my country so it should be fine?) and i have a SIM inserted into it if it's relevant.
I also very much don't care if KNOX trips or not. I don't plan on using any Samsung-made apps ever again since I wanna install a FOSS (free and open-source) ROM to my phone and I don't plan to *ever* sell this phone either.
HUGE thank yous to anyone who finds a solution

FlooferLand said:
I've been trying to install TWRP on my phone for about 3 weeks straight now and i keep running into this exact same issue.
Basically, every time I try to flash anything other than a stock ROM the flash fails and i get "Only official released binaries are allowed to be flashed(RECOVERY)" on my phone's Download screen. (Here's an pic of Odin when the flash fails)
I've tried flashing the latest carrier-unlocked stock ROM to it, and using the phone for 2 week without rebooting (was constantly connected to the internet, uptime was around 300 hours before i attempted to flash TWRP again). I've also tried some solutions I've found on the XDA forums (like flashing the nougat bootloader to my phone, and changing back the time by a month) but nothing appears to work.
I also got the phone used if that's any useful info.
The "OEM Unlock" option was also enabled for some reason after enabling Developer Options. And i also made the mistake of resetting the phone via the recovery menu since i didn't know the previous owner's Samsung account password to remove it from the phone (I'm guessing that's the thing that initially triggered it?)
The phone is also from Spain (but i flashed a stock ROM from my country so it should be fine?) and i have a SIM inserted into it if it's relevant.
I also very much don't care if KNOX trips or not. I don't plan on using any Samsung-made apps ever again since I wanna install a FOSS (free and open-source) ROM to my phone and I don't plan to *ever* sell this phone either.
HUGE thank yous to anyone who finds a solution
Click to expand...
Click to collapse
Can you send a screenshot of the bootloader screen?

Kenora_I said:
Can you send a screenshot of the bootloader screen?
Click to expand...
Click to collapse
I'm guessing you mean the Download screen..?
Here's the Download screen if so:
https://imgur.com/pxu0hsS

FlooferLand said:
I've been trying to install TWRP on my phone for about 3 weeks straight now and i keep running into this exact same issue.
Basically, every time I try to flash anything other than a stock ROM the flash fails and i get "Only official released binaries are allowed to be flashed(RECOVERY)" on my phone's Download screen. (Here's an pic of Odin when the flash fails)
I've tried flashing the latest carrier-unlocked stock ROM to it, and using the phone for 2 week without rebooting (was constantly connected to the internet, uptime was around 300 hours before i attempted to flash TWRP again). I've also tried some solutions I've found on the XDA forums (like flashing the nougat bootloader to my phone, and changing back the time by a month) but nothing appears to work.
I also got the phone used if that's any useful info.
The "OEM Unlock" option was also enabled for some reason after enabling Developer Options. And i also made the mistake of resetting the phone via the recovery menu since i didn't know the previous owner's Samsung account password to remove it from the phone (I'm guessing that's the thing that initially triggered it?)
The phone is also from Spain (but i flashed a stock ROM from my country so it should be fine?) and i have a SIM inserted into it if it's relevant.
I also very much don't care if KNOX trips or not. I don't plan on using any Samsung-made apps ever again since I wanna install a FOSS (free and open-source) ROM to my phone and I don't plan to *ever* sell this phone either.
HUGE thank yous to anyone who finds a solution
Click to expand...
Click to collapse
You did run fastboot OEM unlock?
or
fastboot flashing unlock

Kenora_I said:
You did run fastboot OEM unlock?
or
fastboot flashing unlock
Click to expand...
Click to collapse
I don't think my phone even has fastboot
I tried booting it into recovery and selecting to apply an update with ADB, I've also tried it at the "Waiting for update" screen.
Fastboot just gets stuck saying < waiting for any device >
The OEM unlock checkbox is already checked in Developer Options.
I don't think the S8+ needs another way to enable OEM unlock other than the checkbox in Developer Options.
EDIT: Here's the output of adb logcat --regex rmm after booting into Android if that's helpful(?) (I have no idea how to use Logcat):
{
"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"
}

you did install fastboot drivers? Sometimes if you connect with a usb 3.0 port it dosent work properly

Kenora_I said:
you did install fastboot drivers? Sometimes if you connect with a usb 3.0 port it dosent work properly
Click to expand...
Click to collapse
I've seen a lot of people say the S8+ doesn't have fastboot, there's also no "Reboot to fastboot" option in the recovery menu

Apparently Samsung's RMM server (https://rmm.samsung.com/) appears to be dead (SSL certificate expired and the entire server seems to not work)
So i'm wondering if there's a way to actually spoof the data the server sends, basically blocking Samsung's server and making my own DNS that resolves to my own server sending it's own data.
My problem then is, how would i even know what data my server is supposed to send? And would that even be possible?
I'm very much out of ideas XD
I also found this post (and i have a continuation file for my own phone so in theory it should work?) but it requires the use of iRoot and some proprietary sketchy Windows program. And iRoot and all of these one-click root apps have been known for injecting malware system-level into devices.

FIXED IT!!
The time trick actually worked.
All i had to do was turn back the time by like a year, reboot, enter recovery mode, delete cache, re-enable OEM unlock, spam the update phone button, and boot into download mode!

Nice work! tbh I'd never think of that lol,
FlooferLand said:
FIXED IT!!
The time trick actually worked.
All i had to do was turn back the time by like a year, reboot, enter recovery mode, delete cache, re-enable OEM unlock, spam the update phone button, and boot into download mode!
Click to expand...
Click to collapse

FlooferLand said:
FIXED IT!!
The time trick actually worked.
All i had to do was turn back the time by like a year, reboot, enter recovery mode, delete cache, re-enable OEM unlock, spam the update phone button, and boot into download mode!
Click to expand...
Click to collapse
The same problem, i tried everything, chImera, date, nothing works. Please help me @FlooferLand !

JuanMat97 said:
The same problem, i tried everything, chImera, date, nothing works. Please help me @FlooferLand !
Click to expand...
Click to collapse
The same goes. I have tried everything, and it seems that the post here suggests that we now entirely depend on Samsung to get the site certificate sorted out
Link pasted here for those who don't trust shortened links: https://forum.xda-developers.com/t/...d-expired-certificate-whats-next-lol.4403393/

JuanMat97 said:
The same problem, i tried everything, chImera, date, nothing works. Please help me @FlooferLand !
Click to expand...
Click to collapse
I very much have no clue how it worked for me XD
It's very much possible, you just have to continously try.
I've heard rumors that if you have a Snapdragon chip instead of an Exynos, the RMM is doomed to lock until Samsung resolves their issue. But idk anything about that so i can't really confirm it XD.
I would recommend upgrading to Android 9 and doing the thing i said tho, that worked for me.
Also make sure that your ROM is from the country your SIM card is from, very important.
My phone was originally from Spain, and having a ROM that was made in Spain seemed to caused the RMM to continuously trip out since my SIM wasn't from Spain, so it essentially detected my phone as stolen or smth. You can find official ROMs on something like SamFW.
If this still doesn't work, try waiting 7 days again, then doing the thing i said.

FlooferLand said:
I very much have no clue how it worked for me XD
It's very much possible, you just have to continously try.
I've heard rumors that if you have a Snapdragon chip instead of an Exynos, the RMM is doomed to lock until Samsung resolves their issue. But idk anything about that so i can't really confirm it XD.
I would recommend upgrading to Android 9 and doing the thing i said tho, that worked for me.
Also make sure that your ROM is from the country your SIM card is from, very important.
My phone was originally from Spain, and having a ROM that was made in Spain seemed to caused the RMM to continuously trip out since my SIM wasn't from Spain, so it essentially detected my phone as stolen or smth. You can find official ROMs on something like SamFW.
If this still doesn't work, try waiting 7 days again, then doing the thing i said.
Click to expand...
Click to collapse
friend please, could you say, step by step and in an orderly manner what you did? for example when you said "The time trick actually worked.
All i had to do was turn back the time by like a year" 1-¿have you done that after a flash, a hard reset, or just rebooted without deleting anything?, and also when you said "reboot, enter recovery mode" 2-¿what you did was restart directly to recovery, or restart the system and then restart it again to recovery? and lastly in the part where you said "re-enable OEM unlock, spam the update phone button" 3-¿"re-enable", if you said "re" it means that before reactivating it you already had it activated, right? 4-¿"spam button" by that you mean pressing many times, but, did you have the automatic updates box enabled or not, and... how many times did you touch the update button? thanks in advance, I would appreciate if you answer the 4 questions

which ROM were you using when you did theses steps to unlock? I've tried the 168hs+ method almost now and it didn't worked, then I found your post and tried doing this method changing the date and rebooting cleaning the partition but until now I couldn't achieve it, can you help me pleass

which ROM were you using when you did theses steps to unlock? I've tried the 168hs+ method almost now and it didn't worked, then I found your post and tried doing this method changing the date and rebooting cleaning the partition but until now I couldn't achieve it, can you help me pleass