Database Info

[FIRMWARE] <I535VRUCML1> (MODEM/RPM/TZ/SBL) Verizon SGS3 (SCH-I535)

No, I do not have a full I535VRUCML1 firmware package for you.
Yes, I somewhat lied in the title of this thread. But I did it for a good reason: to get your attention.
Mods - I'm sure you'll understand.
You should NOT flash the I535VRUCML1 firmware (or any subsequent releases for that matter). You will brick. This is what vzw/samsung did on the first OTA for the Galaxy S4. They changed the keys they sign the firmware with. This prevents us from 'mis-matching' our firmware like we've been doing all along. We've been leaving aboot (VRUAME6, the african-canadian sock-monkey leaked bootloader) alone and updating everything else. Since they're signing with different keys now, doing this will brick your device. If you update the ENTIRE bootchain (including aboot) you shouldn't brick, but will be stuck with a locked bootloader and any attempt to downgrade (via dd, etc) will brick you as well. Even if you manage to flash an ENTIRE old bootchain over VRUCML1, you'll brick because they trip a qfuse that prevents it from working. More info about qfuse by djrbliss here: http://t.co/myb0LIrN6e
Just stick with VRUBMF1, trust me.
These firmware updates have, up until now, consisted of several partitions that we update:
- tz (trustzone)
- rpm (resource/power management)
- sbl[1,2,3] (secure bootloaders)
- NON-HLOS (modem/baseband)
Due to the way Samsung and Verizon have chosen to proceed with future updates (following what they do for the Galaxy S4) we cannot flash all these partitions anymore (see above) and retain our unlocked bootloader. We CAN, however, update the baseband as it's not signed.
Latest firmware: NE1 modem with MF1 firmware: http://www.invisiblek.org/firmware/d2/d2vzw_MF1_firmware_NE1_modem.zip (md5sum: 7a49bb13c1160f4d4a89488127684b5b)
This will be the final zip I make. MF1 was the last firmware that allowed us to use the old bootloader, and NE1 is likely to be the last modem we'll ever receive.

How would we measure objectively, coverage/speed differences between what we have the old and new radios?
I guess bandwidth speed test app? Anything else?

Sweet. Maybe I'll get better signal. My voice/1x reception has been worse than my old dx. I'm dropping calls left and right. I also live in the middle of BFE.
how is baseband/radio affected when we flash something else with cwm or with Odin? I mean, I have stock rooted w. b00stedv.002, but if I flash aokp or cm, will it replace this new radio with whatever one is included with them?
Slightly OT, I remember on the dx, if you wanted to sbf without the radio you did it with Linux, otherwise with moto's rsdlite.

Will this wipe data/swap us back to a stockish rom?

invisiblek said:
I've always liked having a thread dedicated to keeping links for the most updated modems for a device. Just easier to find that way.
These are packaged for flashing with Odin. Flash in the PDA section.
I will not promise anything as far as faster speeds or better coverage.
IMPORTANT:
Do not unplug while this is happening, unless you are in dire need of a paperweight.
Odin tends to seem like it hangs for a short bit toward the end of the flash. Be patient, it will finish and automatically reboot.
Latest one on top.
VRLG1 - http://goo.im/devs/invisiblek/i535/VRLG1.modem.tar.md5
This is the first OTA
VRLF2 - http://goo.im/devs/invisiblek/i535/VRLF2.modem.tar.md5
This is the original shipped modem
Click to expand...
Click to collapse
very good idea these are amaazing.. any idea if the new radio plays nicer with installs etc.. as the old one has more or less everyone with no service here and there.. or globally roaming :/

beanstown106 said:
very good idea these are amaazing.. any idea if the new radio plays nicer with installs etc.. as the old one has more or less everyone with no service here and there.. or globally roaming :/
Click to expand...
Click to collapse
no idea, i'm still rocking a stock rom
would be nice though if this fixed some of the aosp problems
MOD: please sticky this thread

invisiblek said:
no idea, i'm still rocking a stock rom
would be nice though if this fixed some of the aosp problems
MOD: please sticky this thread
Click to expand...
Click to collapse
im on cm10 after all the audio commits etc it seems like the most stable rom other than stock, beats aokp or cm9 right now imho, no data drops etc

So...This is just the new baseband right?
So should be able to flash with custom recovery/rom etc?
this is my first samsung device so not looking for a brick.

{
"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'm stuck at this screen, its been doing it for about 10 min. is it ok to unplug and start over?

burkett375 said:
I'm stuck at this screen, its been doing it for about 10 min. is it ok to unplug and start over?
Click to expand...
Click to collapse
Did you verify the MD5 before flashing?

nosympathy said:
Did you verify the MD5 before flashing?
Click to expand...
Click to collapse
doesn't it get verified in odin?

burkett375 said:
doesn't it get verified in odin?
Click to expand...
Click to collapse
I don't have any idea. I have always had HTC phones which are very different.
I have built the habit to check MD5 always, regardless of what it is, just so as to not have something happen where I can't say I did everything I could to prevent it.

burkett375 said:
I'm stuck at this screen, its been doing it for about 10 min. is it ok to unplug and start over?
Click to expand...
Click to collapse
yes, if its stuck on SetupConnection unplug and replug
this goes for more than just flashing modems

invisiblek said:
yes, if its stuck on SetupConnection unplug and replug
this goes for more than just flashing modems
Click to expand...
Click to collapse
hmmm...no matter what I do, I can't get past that part

burkett375 said:
hmmm...no matter what I do, I can't get past that part
Click to expand...
Click to collapse
you have the drivers installed?

burkett375 said:
hmmm...no matter what I do, I can't get past that part
Click to expand...
Click to collapse
You are in download mode correct? I literally just flashed this first try.

invisiblek said:
you have the drivers installed?
Click to expand...
Click to collapse
yup, i'm running CM10 right now and working good.
---------- Post added at 01:20 AM ---------- Previous post was at 01:19 AM ----------
nosympathy said:
You are in download mode correct? I literally just flashed this first try.
Click to expand...
Click to collapse
Nope, didn't know it was supposed to be in download mode...i'm a dummy
Edit: all set now...Thanks!

burkett375 said:
yup, i'm running CM10 right now and working good.
---------- Post added at 01:20 AM ---------- Previous post was at 01:19 AM ----------
Nope, didn't know it was supposed to be in download mode...i'm a dummy
Edit: all set now...Thanks!
Click to expand...
Click to collapse
haha no biggie. It happens.

nosympathy said:
I don't have any idea. I have always had HTC phones which are very different.
I have built the habit to check MD5 always, regardless of what it is, just so as to not have something happen where I can't say I did everything I could to prevent it.
Click to expand...
Click to collapse
tar.md5 files have the md5 appended to the end, and I think Odin checks before flashing. Not 100% sure on that though. Checking it yourself is never a bad idea of course.

This newer modem might of improved data throughput. Not entirely sure though, seems like I'm getting faster speed on Speedtest.net but that could be entirely subjective. Thank you invisiblek as always, for your awesome work!

[Q] Has my phone been flashed?

I bought a Nexus 5 on ebay, advertised as factory reconditioned. However, I have a suspicion that the device has already been flashed as it is on Android version 4.4.4 and won't update to Lollipop. Here's a screenshot of the device info.
Are my suspicions confirmed?
{
"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"
}

itchyfeet said:
I bought a Nexus 5 on ebay, advertised as factory reconditioned. However, I have a suspicion that the device has already been flashed as it is on Android version 4.4.4 and won't update to Lollipop. Here's a screenshot of the device info.
Are my suspicions confirmed?
http://s7.postimg.org/gjbvvsggr/Screenshot_2014_12_18_20_33_10.png
Click to expand...
Click to collapse
From what I can tell it looks fine. Is there a small pad lock icon on the bottom of the screen when you boot the phone up? If the bootloader is unlocked, I'm pretty sure you won't get OTA updates. I could be wrong though.

I don't see a padlock icon during bootup - should there be one? If the phone wasn't flashed, then surely I should be able to get OTA update to Lollipop?

Rarscaryfrosty said:
From what I can tell it looks fine. Is there a small pad lock icon on the bottom of the screen when you boot the phone up? If the bootloader is unlocked, I'm pretty sure you won't get OTA updates. I could be wrong though.
Click to expand...
Click to collapse
My buddy left his nexus 7 unlocked and still got the 5.0 update. I think if you're rooted you won't get it.
---------- Post added at 10:43 PM ---------- Previous post was at 10:40 PM ----------
itchyfeet said:
I don't see a padlock icon during bootup - should there be one? If the phone wasn't flashed, then surely I should be able to get OTA update to Lollipop?
Click to expand...
Click to collapse
What do you mean by flashed? Every phone is "flashed". That's how they get android on the device. If it is refurbished, I wouldn't worry about it. It's probably stock, and you'll just have to wait for the update or do it yourself.

wolfen69 said:
My buddy left his nexus 7 unlocked and still got the 5.0 update. I think if you're rooted you won't get it.
---------- Post added at 10:43 PM ---------- Previous post was at 10:40 PM ----------
What do you mean by flashed? Every phone is "flashed". That's how they get android on the device. If it is refurbished, I wouldn't worry about it. It's probably stock, and you'll just have to wait for the update or do it yourself.
Click to expand...
Click to collapse
Sorry, what I mean is I think the phone has been rooted, which I really don't want. I presume the OTA updates has gone out to official Nexus 5's already, and the reason mine won't recognise an update is because it's been rooted.

itchyfeet said:
Sorry, what I mean is I think the phone has been rooted, which I really don't want. I presume the OTA updates has gone out to official Nexus 5's already, and the reason mine won't recognise an update is because it's been rooted.
Click to expand...
Click to collapse
Not every nexus 5 has gotten the update yet. Be a little patient. Or do it yourself.

Rarscaryfrosty said:
From what I can tell it looks fine. Is there a small pad lock icon on the bottom of the screen when you boot the phone up? If the bootloader is unlocked, I'm pretty sure you won't get OTA updates. I could be wrong though.
Click to expand...
Click to collapse
wolfen69 said:
My buddy left his nexus 7 unlocked and still got the 5.0 update. I think if you're rooted you won't get it.
Click to expand...
Click to collapse
OTA Updates arrive even if you are rooted and your Bootloader is unlocked. I received my OTA Update two days back though am rooted and my Bootloader is unlocked

keylocker said:
OTA Updates arrive even if you are rooted and your Bootloader is unlocked. I received my OTA Update two days back though am rooted and my Bootloader is unlocked
Click to expand...
Click to collapse
Cool. Shows how much I know. I just want people to chill out. ............

To find out if your bootloader is unlocked, boot into fastboot mode..from power off hold volume down and power button. It will say on the bottom if it is unlocked. There are apps that will check for root. Google them. There may be a chance that it was once rooted and/or unlocked but flashed back to stock and relocked. In this case the OTA should work just fine. As stated, you should receive notification of update regardless. If rooted or unlocked the OTA will fail when you try to install it.

If you are concerned about the state of the device I would learn how to flash factory images gotten straight from Google. This will completely wipe the device (your data and the ROM) and reinstall it from scratch. There are plenty of tutorials on how to do this and it will give you peace of mind that your device is, from a software perspective, in new condition.

Sekn said:
If you are concerned about the state of the device I would learn how to flash factory images gotten straight from Google. This will completely wipe the device (your data and the ROM) and reinstall it from scratch. There are plenty of tutorials on how to do this and it will give you peace of mind that your device is, from a software perspective, in new condition.
Click to expand...
Click to collapse
This was my exact thought as well. I figure if he had just purchased it, then why not just flash the 5.0.1 factory image and completely wipe the device and start fresh? It's the cleanest way to get the latest everything without having to mess with saving data etc.

keylocker said:
OTA Updates arrive even if you are rooted and your Bootloader is unlocked. I received my OTA Update two days back though am rooted and my Bootloader is unlocked
Click to expand...
Click to collapse
Yes you will being rooted has nothing to do with it. As long as you are running your stock Rom and recovery you will get them no problem.
Sent from my super duper HTC m8 custom beast machine
---------- Post added at 09:37 AM ---------- Previous post was at 09:25 AM ----------
itchyfeet said:
I don't see a padlock icon during bootup - should there be one? If the phone wasn't flashed, then surely I should be able to get OTA update to Lollipop?
Click to expand...
Click to collapse
Did it say that the phone was rooted and bootloader unlocked when you bought it? Use this to see.
market://details?id=com.jrummyapps.rootchecker
http://play.google.com/store/apps/details?id=com.jrummyapps.rootchecker
Either way if it's unlocked and rooted bonus but that will have nothing to do with ota updates. Unless you have a custom recovery installed. Try to boot into recovery and you'll know if it's stock is not
Sent from my super duper HTC m8 custom beast machine

wolfen69 said:
My buddy left his nexus 7 unlocked and still got the 5.0 update. I think if you're rooted you won't get it.
---------- Post added at 10:43 PM ---------- Previous post was at 10:40 PM ----------
What do you mean by flashed? Every phone is "flashed". That's how they get android on the device. If it is refurbished, I wouldn't worry about it. It's probably stock, and you'll just have to wait for the update or do it yourself.
Click to expand...
Click to collapse
Stop lying

str8str said:
Yes you will being rooted has nothing to do with it. As long as you are running your stock Rom and recovery you will get them no problem.
Sent from my super duper HTC m8 custom beast machine
---------- Post added at 09:37 AM ---------- Previous post was at 09:25 AM ----------
Did it say that the phone was rooted and bootloader unlocked when you bought it? Use this to see.
market://details?id=com.jrummyapps.rootchecker
http://play.google.com/store/apps/details?id=com.jrummyapps.rootchecker
Either way if it's unlocked and rooted bonus but that will have nothing to do with ota updates. Unless you have a custom recovery installed. Try to boot into recovery and you'll know if it's stock is not
Sent from my super duper HTC m8 custom beast machine
Click to expand...
Click to collapse
OTA`s will be downloaded but NOT installed if you have root privileges, you can flash factory images manualy though.

Go to the play store get root checker if you don't see a super.su app then most likely not
Turn off the phone hold vol down and power until you boot into fast boot use the volume keys as up and down scroll to recovery press the power button as enter if it pulls up twrp or clockwork mod then it has been rooted at one time if it pulls up a little android with its chest open saying waiting on command no custom recovery just hold down the power button for 10 seconds to reboot as normal

[RECOVERY] TWRP 2.8.6.1 for D80130b

Hey guys,
Using a guide for the g3 by @topet2k12001 i was able to get permanent recovery working for our d801's running the new 30b Lollipop. I compiled the necessary files into a flashable zip for you all. The zip contains bump'd lollipop boot.img, kk aboot.img, and twrp 2.8.6.1 recovery.
as always... FLASH AT YOUR OWN RISK
Prerequisites:
- Running Stock D80130b
- Rooted
- Autorec installed
Getting Started:
- Copy TWRP-2.8.6.1_D80130b.zip to your phones storage
- Run Autorec and flash TWRP (2.7)
- Reboot to recovery
- Flash TWRP-2.8.6.1_D80130b.zip
- Enjoy!
You should now have a permanent recovery.
DOWNLOAD:
Twrp for d80130b:
https://mega.co.nz/#!qFUDWC4a!nHj3R-gPAEqvZ-yLcQMZxXvTN8eFJg99vWfopnCjR_w
Stock d80130b bootstack + recovery: (flashes stock recovery in case anything goes wrong)
https://mega.co.nz/#!KI9k1YxT!HDJEDSd0X1MEsdr5oiNdutg0aADuqB3A1XrNQUjsqrQ
Credits to @blastagator for the Recovery and @Cloudyfa for Autorec

Great work man...i had a feeling you would bring us a working fix

Was going to try this and got 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"
}

nalanotae said:
Was going to try this and got thisView attachment 3241785
Click to expand...
Click to collapse
If i remember correctly, that means you are not currently rooted - or Autorec doesnt have root permissions

Done!..you're awesome man. By the way, my lollipop charges so slowly like in 4-5 hours. Any help you can offer me?

Thanks very much!! Works great
Sent from my LG-D801 using XDA Free mobile app

snowlin said:
If i remember correctly, that means you are not currently rooted - or Autorec doesnt have root permissions
Click to expand...
Click to collapse
I am rooted and autorec had been granted root permisions........... I may try a fresh install of everything and start over tonight after work...... Thanks for your response

Messip3 said:
Done!..you're awesome man. By the way, my lollipop charges so slowly like in 4-5 hours. Any help you can offer me?
Click to expand...
Click to collapse
Just let it cycle a few days. It will improve.
Same happened for me with 30a and 30b. Of anything i reccomend using "amplify" xposed module.

nalanotae said:
I am rooted and autorec had been granted root permisions........... I may try a fresh install of everything and start over tonight after work...... Thanks for your response
Click to expand...
Click to collapse
maybe you need busybox?
I had that problem once but it was in the middle of me re-flashing the kdz a bunch of times and it didn't happen again. Start fresh if you can
KDZ > Root > Recovery

Great work man!
I knew when I saw you working on it in the other thread that you'd find something!
May I ask what you did to fix this?

snowlin said:
Just let it cycle a few days. It will improve.
Same happened for me with 30a and 30b. Of anything i reccomend using "amplify" xposed module.
Click to expand...
Click to collapse
Alright man...thank you.

mjoecarroll said:
Great work man!
I knew when I saw you working on it in the other thread that you'd find something!
May I ask what you did to fix this?
Click to expand...
Click to collapse
I pulled the aboot.img and laf.img from 20e , bumped the stock lollipop boot.img using a guide i found in the g3 forums and packaged it with twrp 2.8.6.1.
I'm not super experienced or anything but this kind of stuff interests me so i learn as i go

That's pretty awesome. I was gonna try something similar, but I was afraid I was gonna brick my phone... I didn't think about bumping the boot.img at all, that was smart haha.

mjoecarroll said:
That's pretty awesome. I was gonna try something similar, but I was afraid I was gonna brick my phone... I didn't think about bumping the boot.img at all, that was smart haha.
Click to expand...
Click to collapse
It took me a ton of trial and error haha, luckily i had the stock recovery already zip'd so if anything went wrong i could usually just flash that in order to be able to boot again and start over.

snowlin said:
It took me a ton of trial and error haha, luckily i had the stock recovery already zip'd so if anything went wrong i could usually just flash that in order to be able to boot again and start over.
Click to expand...
Click to collapse
Worked just great, thanks a million.

snowlin said:
maybe you need busybox?
I had that problem once but it was in the middle of me re-flashing the kdz a bunch of times and it didn't happen again. Start fresh if you can
KDZ > Root > Recovery
Click to expand...
Click to collapse
That was my plan....... When i first flashed this rom i had no problem with installing autorec but then i got the security error.. So i just flashed kdz then rooted and set the phone up...... Can't wait to get all this going.... Really untested to see how sins if these custom roms run with new radio

Screen goes crazy when recovery tries to dim screen...looks like back when lgd jdi screen issues used to be a problem

jamesd1085 said:
Screen goes crazy when recovery tries to dim screen...looks like back when lgd jdi screen issues used to be a problem
Click to expand...
Click to collapse
hmmm i'm not experiencing this at all, i included the panelfix script from the twrp package too. perhaps its not running correctly.
anyone else having this problem?

snowlin said:
hmmm i'm not experiencing this at all, i included the panelfix script from the twrp package too. perhaps its not running correctly.
anyone else having this problem?
Click to expand...
Click to collapse
So far it happened twice while i was testing...while attemting to back up it did it but was fine as long as i kept screen active...also on restore same issue...if no one else has issue then idk

jamesd1085 said:
So far it happened twice while i was testing...while attemting to back up it did it but was fine as long as i kept screen active...also on restore same issue...if no one else has issue then idk
Click to expand...
Click to collapse
maybe try flashing blastagators twrp package for the 801 : http://blastagator.ddns.net/twrp/2-8-6-1.php
even though this is what i used in mine anyways, it's worth a shot. You will still be able to boot after flashing this since it is only recovery.

6.0.1 OTA for stock rooted system

Hi, sorry if this is a stupid question, but I just noticed Sprint pushed an OTA for 6.0.1 to my stock rooted device (S-on) and I'm just trying to figure out what the best way to get this OTA is going to be. I'm assuming I shouldn't download and install the OTA as-is due to the TWRP recovery and root.
After looking around a bit, it seems like the only option available is to use a stock 6.0.0 RUU file in the bootloader and basically reset the entire device back to factory settings (losing all apps and data in the process presumably), installing the OTA, then re-flashing TWRP and re-rooting.
I guess what I'm asking is - 1. is this the correct way to go about doing this? and 2. is there any better alternative perhaps that doesn't involve losing my data?
Thanks in advance guys.

Been googling around for the last few days and scouring this board for just as long and still haven't come to a definitive conclusion. From what little I've seen the documentation on this seems kind of spotty and I'm just wondering which direction to head in. Any help on this would be much appreciated.

Safest way.. ruu back to stock everything take ota and re root/download apps etc...

Thanks for the reply, man.. Thats kind of what I had gathered pouring over all these articles and board posts. I went ahead and RUU'd back to 1.10.651.1 for sprint.. Literally just moments ago though I downloaded the OTA and hit install and got presented with an error screen during the update. Phone rebooted back into the system normally, and I went to check the version # only to see it unchanged, along with a prompt to install the OTA for 1.57.651.1 again.
Any idea why this might've happened or how to remedy 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"
}
Wonders_Never_Cease said:
Safest way.. ruu back to stock everything take ota and re root/download apps etc...
Click to expand...
Click to collapse

What was the error? You may have to relock bootloader to accept the ota...unsure of how they are with their device,GSM device I have doesnt need relocked...(S-Off as well so)
---------- Post added at 12:50 AM ---------- Previous post was at 12:47 AM ----------
Also the 1.57.651.1 RUU is available... Why not use it?
http://dl3.htc.com/application/RUU_HIA_AERO_WHL_M60_SENSE7GP_SPCS_MR_Sprint_WWE_1.57.651.1_R2.exe

Thats the weird part, it didnt give an error message, just that icon in the image I added to my last post. forelock the bootloader would be kind of surprising... Might give that a try in the morning after I find out if it can be re-unlocked.
EDIT: Ohhh I just saw your last edit, i didnt see that before, i'll use that then. Thank you!!!
Wonders_Never_Cease said:
What was the error? You may have to relock bootloader to accept the ota...unsure of how they are with their device,GSM device I have doesnt need relocked...(S-Off as well so)
---------- Post added at 12:50 AM ---------- Previous post was at 12:47 AM ----------
Also the 1.57.651.1 RUU is available... Why not use it?
http://dl3.htc.com/application/RUU_HIA_AERO_WHL_M60_SENSE7GP_SPCS_MR_Sprint_WWE_1.57.651.1_R2.exe
Click to expand...
Click to collapse

Download the .651 ruu,reboot phone into download mode and run it... Should be up to date after that for a bit id think
---------- Post added at 12:58 AM ---------- Previous post was at 12:53 AM ----------
How did you unlock it to begin with? HTC Dev site? If so then should be able to use the same unlocktoken.bin from before... Or can resubmit and get another one...
txag2011 said:
Thats the weird part, it didnt give an error message, just that icon in the image I added to my last post. forelock the bootloader would be kind of surprising... Might give that a try in the morning after I find out if it can be re-unlocked.
EDIT: Ohhh I just saw your last edit, i didnt see that before, i'll use that then. Thank you!!!
Click to expand...
Click to collapse

Thats precisely what I did. Unlocked it with the HTC Dev Token. I gotta admit, I was pretty surprised that I had an OTA so soon after getting the phone and unlocking / rooting it. Just when I had everything set up how I liked it
I just finished flashing the 651 RUU and its just optimizing the apps now, but looks like it should do it!
Wonders_Never_Cease said:
Download the .651 ruu,reboot phone into download mode and run it... Should be up to date after that for a bit id think
---------- Post added at 12:58 AM ---------- Previous post was at 12:53 AM ----------
How did you unlock it to begin with? HTC Dev site? If so then should be able to use the same unlocktoken.bin from before... Or can resubmit and get another one...
Click to expand...
Click to collapse

Cool glad got it sorted...
txag2011 said:
Thats precisely what I did. Unlocked it with the HTC Dev Token. I gotta admit, I was pretty surprised that I had an OTA so soon after getting the phone and unlocking / rooting it. Just when I had everything set up how I liked it
I just finished flashing the 651 RUU and its just optimizing the apps now, but looks like it should do it!
Click to expand...
Click to collapse

Actually.. I've hit another wall now tryign to achieve root with this. I've got TWRP back on the device, and I'm using WinDroid Toolkit to flash SuperSU to it. It'll show that it's pushing it, then drop into recovery and naturally ask for me to wipe the /data partition since it's encrypted, before proceeding to install the supersu.zip package.
The only problem is, there doesn't appear to be any supersu.zip anywhere on the device once it gets into recovery, either before or after the data wipe. Any idea where it's going?
Wonders_Never_Cease said:
Cool glad got it sorted...
Click to expand...
Click to collapse

First thing ya need to do is read how to install adb and fastboot and get away from toolkits... Download 2.67 from this thread...copy to device flash through twrp...
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
txag2011 said:
Actually.. I've hit another wall now tryign to achieve root with this. I've got TWRP back on the device, and I'm using WinDroid Toolkit to flash SuperSU to it. It'll show that it's pushing it, then drop into recovery and naturally ask for me to wipe the /data partition since it's encrypted, before proceeding to install the supersu.zip package.
The only problem is, there doesn't appear to be any supersu.zip anywhere on the device once it gets into recovery, either before or after the data wipe. Any idea where it's going?
Click to expand...
Click to collapse

And didnt mean that in a snotty,sarcastic way... Those tools sometimes cause issues that could be avoided is all I was getting at...

I want to join this conversation.
The A9 of my mom got is a Vodaphone UK version (cid: vodap001) and got the update message to version 1.62.161.2
I've rooted the device and installed TWRP.
So now i relocked the bootloader, installed the firmware.zip that was inside the OTA Download which i've copied from Update-App Path.
If i now want to manualy update the OTA-zip with fastboot in download-mode, i got Error 7.
If i want to update with original OTA updater Up, it stops at 25% with the red cross.
So what should i do now?
There is noch previous RUU-file for this firmware-version thats why i've already updated to the recovery from this OTA-update.
I hope someone can help with it.
Thanks,
Bond

txag2011 said:
Actually.. I've hit another wall now tryign to achieve root with this. I've got TWRP back on the device, and I'm using WinDroid Toolkit to flash SuperSU to it. It'll show that it's pushing it, then drop into recovery and naturally ask for me to wipe the /data partition since it's encrypted, before proceeding to install the supersu.zip package.
The only problem is, there doesn't appear to be any supersu.zip anywhere on the device once it gets into recovery, either before or after the data wipe. Any idea where it's going?
Click to expand...
Click to collapse
I have to agree with Wonders_never_cease about the toolkits. I have used many different ones and they are great from a few things but not all things go right using them unlike adb/fastboot. You should have better results from using adb/fastboot here.
That being said.....it would be easier to achieve root by simply going to full stock using RUU or system/boot.img in fastboot, flashing TWRP, format data, reboot into TWRP, flash supersu 2.74 from your SD card either by itself to obtain normal root or follow steps here http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2 for systemless root. it's that simple...or at least was for me. I never could get pushing supersu through adb right or to work really.
---------- Post added at 10:12 AM ---------- Previous post was at 09:59 AM ----------
Bond246 said:
I want to join this conversation.
The A9 of my mom got is a Vodaphone UK version (cid: vodap001) and got the update message to version 1.62.161.2
I've rooted the device and installed TWRP.
So now i relocked the bootloader, installed the firmware.zip that was inside the OTA Download which i've copied from Update-App Path.
If i now want to manualy update the OTA-zip with fastboot in download-mode, i got Error 7.
If i want to update with original OTA updater Up, it stops at 25% with the red cross.
So what should i do now?
There is noch previous RUU-file for this firmware-version thats why i've already updated to the recovery from this OTA-update.
I hope someone can help with it.
Thanks,
Bond
Click to expand...
Click to collapse
You will not be able to apply the OTA update if you are not completely stock including being with stock recovery. Having your bootloader unlocked will not be an issue so no need to relock it like you did. Use a system/boot/recovery.img to restore stock completely, or whatever RUU need. Then accept the OTA or flash it manually, then reroot. Thats really the only way you will be able to get that to work.....

mcbright80 said:
You will not be able to apply the OTA update if you are not completely stock including being with stock recovery. Having your bootloader unlocked will not be an issue so no need to relock it like you did. Use a system/boot/recovery.img to restore stock completely, or whatever RUU need. Then accept the OTA or flash it manually, then reroot. Thats really the only way you will be able to get that to work.....
Click to expand...
Click to collapse
Thanks for your answer.
But how to get complete stock without nandroid or RUU?
The Firmware.zip of the 1.62.161.2 OTA Update was installed without Errors. But as i already mentioned i Need stock System/boot-files of my last Version (1.62.161.1) to get this partitions to stock. And they are not available anywhere.

Bond246 said:
Thanks for your answer.
But how to get complete stock without nandroid or RUU?
The Firmware.zip of the 1.62.161.2 OTA Update was installed without Errors. But as i already mentioned i Need stock System/boot-files of my last Version (1.62.161.1) to get this partitions to stock. And they are not available anywhere.
Click to expand...
Click to collapse
Ah so sorry, it was 4 am when i was replying so i missed that part on it installing correct, or confused it with the other question i was replying to at that same time haha......anyhoo....i looked for you as well and nothing was found on my end as well so I think you may be in the exact situation i was in when i bought the sprint variant of the A9. HTC has faults like all companies but the one that really pisses me off is their lack of proper support on ALL variants especially concerning firmware. The phone was released and i found NO RUU on their site or anywhere online and of course not many people had my specific variant which meant no one on here or anywhere had the means to get me the stock firmware i too needed to restore my phone.
The ONLY reason anyone here, who has SPRINT US VERSION, is able to then and NOW get the RUU on the HTC website is directly due to my incessant badgering and yelling at HTC damn near daily about having a handset on the market for sale but no firmware for it in case of tech service needs. You may have to do the same thing sadly.
I assume you have checked htc UK site for the rom downloads......contact their tech support and see whats up. Till then, like i had to when the sprint version came out....you'll have to just keep checking back on here and anywhere online for someone else who may post what you need or some other kind of solution.

Thanks mcbright80,
as you already said, HTC resists and says RUUs are only available in the US. I'm excited on their reaction that there are still lower RUU-versions of my UK-edition.
It is an annoying mess with all these different versions for tons of carriers, countrys and so on.

Your device is corrupt

I tiried to flash the new oxygen pie beta. For whatever reason something went wrong and now here I am.
First time i flashed the beat I got the "Your device is corrupt" error. It's not the typical unlocked boot loader error. The explanation point is red, there is no mention of unlocked bootloader and I need to press power button in order to proceed. I tried flashing again at this point and I wiped everything in TWRP, but that didn't help.
Afterwards I have decided to go back to oreo and just upgrade to pie by local upgrade, but after flashing oreo I still get the red "your device is corrupt". However, I can still boot to the oxygen os and it seem to be working fine.

think its the encryption so reformat the data partition and start from scratch

RiTCHiE007 said:
think its the encryption so reformat the data partition and start from scratch
Click to expand...
Click to collapse
Formatted data and wiped everything. Flashed the pie beta. I can boot to the os, but I still get the error..

RiTCHiE007 said:
think its the encryption so reformat the data partition and start from scratch
Click to expand...
Click to collapse
I am decrypt and still get the same warning. I'm sure it'll be fixed later.

mikex8593 said:
I am decrypt and still get the same warning. I'm sure it'll be fixed later.
Click to expand...
Click to collapse
Thing is I still got that error when I went back to 8.1, which suggests it's not the android pie issue. Well, phone is working fine so I guess I will live for now.
Edit:
Something is messed up as I can't pass safetynet, CTS profile fails

Yep, the same. Even completely wiped everything in stock recovery. Seems fine once you hit power twice to go past it.
---------- Post added at 02:19 PM ---------- Previous post was at 02:15 PM ----------
I had to flash the OnePlus6Oxygen_OTA_010_O_MR1_20180607.zip to fix the error when going back to 8.1. Grabbed ti from one of the How To threads for reverting.

Can you post the link to the file?
Barsky said:
Yep, the same. Even completely wiped everything in stock recovery. Seems fine once you hit power twice to go past it.
---------- Post added at 02:19 PM ---------- Previous post was at 02:15 PM ----------
I had to flash the OnePlus6Oxygen_OTA_010_O_MR1_20180607.zip to fix the error when going back to 8.1. Grabbed ti from one of the How To threads for reverting.
Click to expand...
Click to collapse

Guess it is actually form Oneplus site:
https://forums.oneplus.com/threads/...ficial-oxygen-os-roms-and-ota-updates.835607/
In rollback builds under Signed flashable zips (Android P Developer Preview)

Your device will work by hitting power twice at the red text/corrupt still but you can fix it so that your on Beta without it.
Anyone thats getting corrupt device/red text during boot after flashing this beta or any other I have figured the only solution I know of possible atm to get around it so you can have beta's without the error. You will need to use the unbrick tool to totally clear your device from anything that is causing the issue and after that update your phone through settings as normal with no issue. Here is the tool and info for anyone who needs it:
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
Every other way possible tried nothing else worked for me but this. Your device will be in the same state basically as it was in the box so *totally* cleaned.
{
"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"
}

Nameless said:
Your device will work by hitting power twice at the red text/corrupt still but you can fix it so that your on Beta without it.
Anyone thats getting corrupt device/red text during boot after flashing this beta or any other I have figured the only solution I know of possible atm to get around it so you can have beta's without the error. You will need to use the unbrick tool to totally clear your device from anything that is causing the issue and after that update your phone through settings as normal with no issue. Here is the tool and info for anyone who needs it:
https://forum.xda-developers.com/one...ional-t3798892
Every other way possible tried nothing else worked for me but this. Your device will be in the same state basically as it was in the box so *totally* cleaned.
View attachment 4587785
Click to expand...
Click to collapse
The URL you shared is giving 404 error
Please share correct URL

https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
This worked for me , back to stock , then try PIE again

:good:

soldier1 said:
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
This worked for me , back to stock , then try PIE again
Click to expand...
Click to collapse
So you are now back to P beta 1 without the error? Hmm. I got my phone back to 8.1 without the area. But once I flashed it again, the same thing came back.
Thanks
Ended up using qualcomm tool, then flashed P beta 1, then unlocked bootloader, installed twrp, installed magisk7. Everything is good now.

Flashing stock didn't help me, I still had the error. I used the qualcom tool and now I'm on pie without the error.

Barsky said:
Yep, the same. Even completely wiped everything in stock recovery. Seems fine once you hit power twice to go past it.
---------- Post added at 02:19 PM ---------- Previous post was at 02:15 PM ----------
I had to flash the OnePlus6Oxygen_OTA_010_O_MR1_20180607.zip to fix the error when going back to 8.1. Grabbed ti from one of the How To threads for reverting.
Click to expand...
Click to collapse
Also had the same and flashing back the roll back package fixed it, definitely keeping this zip!

Spoke too soon got the corrupt message after going back to 5.1.11 then to oos beta 1 so had to use the unbrick tool instead.

my guess is that the bootloader can not tell if phone is bootloader locked or unlocked. Has any1 tried flashing the bootloader files to see if that could fix it without debrick tool?

mati11233 said:
Thing is I still got that error when I went back to 8.1, which suggests it's not the android pie issue. Well, phone is working fine so I guess I will live for now.
Edit:
Something is messed up as I can't pass safetynet, CTS profile fails
Click to expand...
Click to collapse
No its not, safetynet will not pass, says so even in changelog

Yeah i got the same error, only solution for me was to use unbrick tool

Flash OOS Beta over H2OS beta, no need to wipe data between the two. But it works wonders.