Database Users

Have to admit I need some help with rooting

Ok so this is whats been happening. I have an eris im trying to load a custom rom on after I did the 2.1OTA
When I came out to XDA to use the root I was at first confused since it was all going from 1.5 to 2.1. After reading further I read reports that 2.1OTA is rootable just like 1.5 as long as I follow the proper steps.
I: Gaining root
An unlocked hboot will allows us to flash in a modified IMG ROM signed with test keys as supposed to requiring an official ROM from HTC. This will open us to be able to flash a modified recovery.
1. Download this file: PB00IMG.zip (md5: 63eacc5ede3b179f95dc22d8ef585f94)
2. Place PB00IMG.zip onto the root directory of your sdcard.
3. Power down your phone.
4. Hold Volume Down while you Power On. This should bring you to a screen saying "HBOOT" and some other stuff. Wait for it to load the image, and it will say Push Activate. Push the trackball button to continue. The process will take around 5-10 minutes. The first time your phone boots up it will take a lot longer than normal.
Click to expand...
Click to collapse
I think this is where things go wrong. When this was attempted it I saw that my bootloader was now reading 1.49 (phone never been rooted before) instead of the one people report you need to root which is 1.47
It loaded up under 2.1 still and I believe its still the 2.1OTA so I head on to next step for recovery img. something seems to have gone wrong with it too (possibly me messing up the sdk) as now when I try to load any recovery images via fastboot "FAILED <remote: not allow>
Now the more trouble part is now that its ready I follow the instructions on how to actually load the rom through the recovery and SD card method. I believe my recovery is not what its supposed to be either as when it loads I see an android next to a caution symbol with a yellow ! and when the recovery screen is brought up I only have 4 options. Ill type abit what I see
"
Android system recovery <2e>
Use volume key to highlight:
click power key to select.
Reboot system now
Apply sdcard:update.zip
Wipe data/factory reset
Wipe cache partition
E:Can't open /cache/recovery/command"
Now I have tried the instruction of wiping first with a data and cache wipe but it does not give me any options after that on to flash from sdcard
IV: Flashing a custom ROM
1. Download the Rooted 2.1 v0.8T2 zip file.
2. Copy the WHOLE zip file to the root directory of your SD card. (You can enable USB-MS enable from your shiny new recovery to mount your phone as a USB Mass Storage device.)
3. Choose Wipe. Choose data/factory Reset (In the stock ROM, the dalvik is stored in the data and you don't have an EXT partition... yet.)
4. Choose Flash zip from sdcard. Find the eris_0_3.zip file.
5. Wait until it shows as complete and choose reboot system now.
Click to expand...
Click to collapse
I have tried putting different ROM's on my sdcard. I attempted to downgrade using the tutorial provided and using the official RUU from PCD's website. (which both didnt work as downgrade would stop at recovery or RUU states wrong bootloader version towards the middle of the load) and I tried even renaming the ROM's to update.zip the message I get everytime is the same with 2 results one for the rom without the update.zip and one with it.
(with update.zip)
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted
(without update.zip)
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted
Also for those wondering I followed the method of installing drivers and using debugging mode ....all drivers seem to be working fine.
Also just for further info when I run the RUU to try and downgrade my bootloader goes back to showing 1.47 but the radio is still 2.40 if this gives and help
If some could first tell me where I went wrong and then where to go from here I will be most appreciative and im even willing on putting out a reward if someone can do this for me quickly (I am poor some it wont be a big reward but it will be something)
Thanks for any help.

This means you are on the leaked version now and there is nothing that can be done as of right now.

K well thanks for the short and sweet answer. Can anyone tell me how I went from stock 2.1OTA to getting the leaked verision? was it step number one that did it? something didnt load correctly after that?

ca2l3vin said:
K well thanks for the short and sweet answer. Can anyone tell me how I went from stock 2.1OTA to getting the leaked verision? was it step number one that did it? something didnt load correctly after that?
Click to expand...
Click to collapse
So you saying you had 1.5, then got the OTA update from Verizon?
If that is true, are you sure you downloaded the correct root image? Cuz if I remember correctly, the non root one is named the samething. But I could be wrong as I never tried leak.

sounds like you got a bad pb001.img file.

ca2l3vin, it sounds like you may have downloaded and flashed the wrong PB00IMG.zip file. Where did you get it from?

nevermind addressed my issue

As far as I understood I got it from the tutorial was the first place I got it. After I started to have issues I downloaded it from another site thinking I could just update with correct one. Same name same file size and unfortunately same results.
also I did forget to put in my build number like the above post so ill drop that in now.
Firmware Version
2.1
Baseband Version
2.40.00.01.22
Kernel Version
2.6.29-5898f66b
[email protected] #1
Build Number
2.19.605.1 CL123435 test-keys
Software Number
2.19.605.1
Browser version
webKit 3.1
PRI Version
2.11_002
PRL Version
51866 (I know this is just area based)
ERI Version
5

ca2l3vin said:
As far as I understood I got it from the tutorial was the first place I got it. After I started to have issues I downloaded it from another site thinking I could just update with correct one. Same name same file size and unfortunately same results.
also I did forget to put in my build number like the above post so ill drop that in now.
Firmware Version
2.1
Baseband Version
2.40.00.01.22
Kernel Version
2.6.29-5898f66b
[email protected] #1
Build Number
2.19.605.1 CL123435 test-keys
Software Number
2.19.605.1
Browser version
webKit 3.1
PRI Version
2.11_002
PRL Version
51866 (I know this is just area based)
ERI Version
5
Click to expand...
Click to collapse
I hate linking back to another forum, but I used this guide and it worked flawlessly for me.
http://androidforums.com/all-things-root-eris/53963-guide-stock-1-5-latest-root-2-1-a.html
Did not check your link to see if its teh same but I can vouch that this one is 100% working.

af man...seriously!

out of curiously i reboot my phone via power + volume up and saw my hboot version 1.49.... it's werid because I had my phone rooted long ago when I was running on 1.50. Anyway, I'm still able to boot into Amon_RA's recovery and using Tainted Vanilla ROM as of now. I'm thinking it might be because of *228 actually reprogrammed SPL somehow, because i saw glimpse of message during programming phase, it said "SPL unlocked" and "OTA update completed"

HAAZAAAA!!!! Thanks to droidkevlar
So what happened was the wording on the original tutorial confused me quite abit. basically on the recovery step I skipped over it completely due to the fact that it was worded as an optional step for just creating your own recovery point. Once I read the guide linked by droidkevlar I see that THAT is the actually Amon's Recovery image needed to load the custom ROMS in the first place.
ITS A NEEDED STEP not really an optional one (unless your a dev I guess)
I just did my first flash to the EvilEris Rom and now will be trying others out.
I think the tut should be possibly re-worded as I have seen others that seem to be in the same boat I was in. or atleast put in that all steps are needed.
Anyways all the steps and files are the same on both so just follow them both out all the way and it works with 2.1OTA

ca2l3vin said:
HAAZAAAA!!!! Thanks to droidkevlar
So what happened was the wording on the original tutorial confused me quite abit. basically on the recovery step I skipped over it completely due to the fact that it was worded as an optional step for just creating your own recovery point. Once I read the guide linked by droidkevlar I see that THAT is the actually Amon's Recovery image needed to load the custom ROMS in the first place.
ITS A NEEDED STEP not really an optional one (unless your a dev I guess)
I just did my first flash to the EvilEris Rom and now will be trying others out.
I think the tut should be possibly re-worded as I have seen others that seem to be in the same boat I was in. or atleast put in that all steps are needed.
Anyways all the steps and files are the same on both so just follow them both out all the way and it works with 2.1OTA
Click to expand...
Click to collapse
Glad I could help. Aloysius is also a very good one to check out. Heard there are issues with v12 but v11 maps is solid!

[ROM][03/06/2011]FlashBack21 v2 -Return to Factory Stock - March 2011 OTA

[SIZE=+3]FlashBack21 v2 - Return to Factory 2.1 Stock - March 2011 OTA[/SIZE]
Note1: This ROM supersedes the (former) "FlashBack15" ROM as of 2010/10/20. This step was taken because it appears that VZW/Google are no longer providing Cupcake->Eclair OTA downloads for the Eris.
Note2: The V2 FlashBack21 ROM installs the stock HTC software corresponding to the March 2011 OTA version V2.41.605.6. The V1 FlashBack21 ROM installs the stock HTC software corresponding to the July 2010 OTA - version V2.37.605.4
[SIZE=+2]Last Updated: March 06 2011[/SIZE]
This ROM is intended for reverting a rooted Eris with a custom recovery to the HTC stock software: March 2011 2.1 OTA ROM - v 2.41.605.6. There are many other ways to do this; but this way uses Amon_RA for the installation as a convenience for less experienced rooters. (And only Amon_RA v1.6.2 - the installer will refuse to work with any other recovery.)
Two versions are provided: one which flashes the radio firmware version 2.42.01.04.27, and one which does not flash the radio; other than this difference, they are identical. (The same radio firmware - v2.42.01.04.27 - was used in both the July 2010 & March 2011 OTA releases.) Choose the ROM which best fits your needs. If you already have the most recent radio installed (2.42.01.04.27), there is no need to reflash the radio.
File name: "FlashBack21_v2.zip" (download link and md5 sigs below).
File name: "FlashBack21_v2_noRadioFlash.zip" (download link and md5 sigs below).
Derived from the Eris "March 2011 OTA" (2.41.605.6) release, this ROM repackages the last official 2.1 ("Eclair") release for the Eris from HTC/VZW so that it can be installed with Amon_RA recovery - you flash it just like any other dev ROM. There are essentially no customizations, and no built-in root or extra tools; it is 99.99% stock, with the following difference:
- This ROM also performs jcase's "Flash Any RUU" patch to the misc partition during the flashing process.
This step is performed so that the Eris responds well to flashing operations involving the use of any PB00IMG.zip file (via HBOOT), or application of any RUU utility for the Eris. So, even though this is an "unrooting" ROM, pains are taken to make sure that it is easy as possible to re-root or manipulate with existing methods.
This ROM does not touch the bootloader (or "Hboot" or "IPL/SPL"). If you want to install a different bootloader, do it first before applying this ROM.
[SIZE=+1]Please Note: THE RECOVERY BOOT PARTITION IS REPLACED BY THE MATCHING VERSION OF THE STOCK RECOVERY PARTITION (V2: March 2011 OTA; V1: July 2010 OTA) in this ROM. This means that you will need to re-root your phone if you use this ROM, should you later decide that you want to restore a different ROM.[/SIZE]
[SIZE=+1]Please Note 2: ONE OF THESE ROMs FLASHES A RADIO. This is different than nearly 99% of all Eris dev ROMs. You will see some activity at the conclusion of your Amon_RA recovery session as a result of this - if you choose to use the ROM version that flashes the radio firmware.[/SIZE]
[SIZE=+2]Instructions[/SIZE]
- Read this whole post all the way through before you begin
- Charge your phone completely
- Download the .zip file you need to the top-most folder of your SD card
- Verify the length and/or MD5 checksums (of the copy of the ROM file on the SD card)
- Boot into the Amon_RA recovery, Wipe, and then flash the FlashBack21 ROM (of your choosing)
IF YOU ARE FLASHING THE RADIO:
- When flashing is complete, you will see the message at the bottom of the screen:
"Reboot via vol-up+vol-down or menu to complete installation"
- Make sure to exit Amon_RA after the ROM has finished flashing by selecting the "Reboot now" top-level menu item. Don't do something stupid like pulling the battery.
- You will see two successive splash screens that you do not normally see when using Amon_RA - these indicate that the factory recovery boot is performing the radio flashing operation. Do not interrupt - the phone will reboot on it is own when this step completes.
[SIZE=+2]Acknowledgments[/SIZE]
- Amon_RA for his recovery boot
- jcase for his disclosure to the Eris community of the misc partition "main version number" patch
- hundreds of others on XDA and AF too numerous to mention
- doogald for re-hosting the ROMs (2/15/2012)
[SIZE=+2]Downloads - V2 - March 2011 OTA - v 2.41.605.6[/SIZE]
(Thanks to XDA user doogald for hosting these downloads!)
[SIZE=+1]Flashes Radio !!!![/SIZE]
FlashBack21_v2.zip ( 109,245,758 Bytes; MD5: 3c770473e18e539afe5d090b4a5462ca )
[SIZE=+1]Same ROM, but does NOT flash Radio[/SIZE]
FlashBack21_v2_noRadioFlash.zip ( 102,181,672 Bytes; MD5: d0137efb10dd714cf3770e5ff7b842f5 )
[SIZE=+2]Downloads - V1 - July 2010 OTA - v 2.37.605.4[/SIZE]
(Thanks to XDA user doogald for hosting these downloads!)
[SIZE=+1]Flashes Radio !!!![/SIZE]
FlashBack21_v1.zip ( 108,784,952 Bytes; MD5: 416a92afe52d87beccbef29380a2009f )
[SIZE=+1]Same ROM, but does NOT flash Radio[/SIZE]
FlashBack21_v1_noRadioFlash.zip ( 108,784,967 Bytes; MD5: 44bff966290bb02c0b70ae06ef95d719 )
(Note that both V1 ROM files include the radio image, even though the latter does not flash this firmware - that is why the file sizes are nearly identical.)
OBSOLETE & DEPRECATED - Flashback15_v1
Thanks to XDA user doogald for hosting this download!
- This is here for historical purposes only.
- Note this now ONLY provides a Cupcake (Android 1.5) Factory roll-back for the Eris, as VZW/Google are no longer providing OTAs for the Eris.
- Do not use unless you specifically want a stock "Cupcake" (Android 1.5) Eris
- Note this ROM also UNROOTS YOUR PHONE by replacing the custom recovery with the stock recovery
FlashBack15_v1.zip ( 94,011,341 Bytes; MD5: e5e7ab9f3bc3314f28543fd88ae296fd )
bftb0

Thanks, sounds like this could come in handy!

Yep thanks .... will make it easy when I send this phone back for my 5th eris

This should be stickied up to...Good work!

Nice. Agree this should be sticky

Very nice thank you!
Sent from my Eris using XDA App

Awesome work

Awesome. I agree - lets make this a sticky.
Sent from my nonsensikal froyo using XDA App

Just used this... Worked like a charm. Excellent work and thanks.

This is gonna help out alot of people.

ill be using this in the next few days, got to return my eris cuz trackball is going out :/

TopazAaron said:
ill be using this in the next few days, got to return my eris cuz trackball is going out :/
Click to expand...
Click to collapse
Note that this ROM does not replace the bootloader - so, if you have the engineering bootloader on your phone, you might just want to flash the MR2 RUU (or the corresponding PB00IMG.zip) immediately after booting this (no point in doing the OTA twice). Or, for folks that know their way around fastboot, if they have the S-OFF bootloader, there is always the option to put an S-ON bootloader back onto the phone thusly[SIZE=+1]**[/SIZE]:
Code:
fastboot flash hboot hboot_7501a_1.47.0000_091023.nb0
I did things this way (no replacement of the bootloader) because most of the folks that did their Eris rooting the "old school" way - and have the Engineering bootloader on their phone (1.49.2000 S-OFF) are comfortable using adb or fastboot, et cetera - and probably have enough knowledge to manually replace their bootloader; whereas the late-comers to the rooting party (leakers and others) that are not familiar with these methods probably used "one click" or similar, so they probably don't have the S-OFF bootloader on their phone anyway.
If I was going to return a phone to VZW, and was concerned that a computer forensics expert was going to examine my phone (I'm 99.999% confident that this does NOT happen), I would apply the MR2 and then take the OTA after that.
Here are the reasons why (these are really only motivations for the ultra-paranoid):
- None of the dev ROMs have ever touched the "NVRAM" area of the phone, whereas the "leak" PB00IMG.zip ROMs did manipulate that. So, phones that went through a leak-flash install still have evidence (in NVRAM) that they have been flashed with unofficial software releases (from HTC), even if the so-called "ROM" has been replaced. The only way to over-write that is to re-write the NVRAM using a VZW-sponsored RUU (or corresponding PB00IMG.zip file). In my mind, that is the MR2, not the "Official" ( == Leak-V3) RUU.
- The same thing is true of the "misc" partition - evidence of fooling around with HBOOT+PB00IMG.zip files persists in the misc partition if you do not take steps to overwrite it. (I flashed and rooted my phone an absurd number of times yesterday (for testing), and right now my misc partition reports "2.19.605.1" because the last thing that I did was install the S-OFF bootloader using HBOOT and the battery-pull trick).
- Forensic evidence in the form of directory or file timestamps probably can determine if a phone has a non-factory, or non-RUU software on it. The same thing is probably true of very low-level (yaffs2) filesystem storage order - there is no reason to believe that the file storage order (relative to the linear page layout of flash memory) will be preserved with a non-stock installer.
But, as I said, the above considerations are for the truly paranoid. VZW doesn't look at phones that carefully, and probably can not for economic reasons - and all the things I mentioned above can not be determined easily (for instance by a retail clerk looking at the booted phone)
But in a way, it doesn't matter anyway - because of the "checkin" process that happens every time the phone boots up, and the pattern of phone activations or market history, Google and VZW have enough information available (between them) in the form of user activity that they could identify every rooted Android user on the VZW network - if they cared enough to do so.
As I said, if I were going to return a phone, I would do the "misc" partition hack, install the MR2 RUU (or matching PB00IMG.zip file), and then take the OTA - and then finally perform a factory reset. But even that is probably far more effort than is necessary.
bftb0
[SIZE=+1]**[/SIZE] Flashing the bootloader is the single most dangerous operation you can perform. Make damn sure the file you are planning on flashing has the correct MD5 signature, as "fastboot" does not check a single thing - it will allow you to flash total garbage to the phone.

I'm shipping back an Eris which I used this method on to remove root, but don't have time to do the 2. 1 update, do you think VZW cares that its running 1. 5?
Sent from my FroyoEris using Tapatalk

eriscentro said:
I'm shipping back an Eris which I used this method on to remove root, but don't have time to do the 2. 1 update, do you think VZW cares that its running 1. 5?
Click to expand...
Click to collapse
Doubt it matters. It takes about 20 minutes for the full OTA 2.1 update, but once you kick it off, the entire process requires no interaction - go do something else for 20 minutes.
You might also want to do a factory reset using the the phone's menu - that will clear the activation status of the phone.

ok... I read bftb0's post... but not sure I'm following
I did the universal one click root method to root my phone and I'm not sure if I need to go to the trouble of flashing something to fix the bootloader or w/e...(not sure if I even messed with the bootloader, maybe I did but this is the noob coming out in me)
If I wanted to send my eris back today to verizon, wouldn't flashing this new zip fix everything I need it to fix and make it comepletely back to its original stock settings??

NPH- said:
ok... I read bftb0's post... but not sure I'm following
I did the universal one click root method to root my phone and I'm not sure if I need to go to the trouble of flashing something to fix the bootloader or w/e...(not sure if I even messed with the bootloader, maybe I did but this is the noob coming out in me)
If I wanted to send my eris back today to verizon, wouldn't flashing this new zip fix everything I need it to fix and make it comepletely back to its original stock settings??
Click to expand...
Click to collapse
Except the bootloader and radio.
Sent from my xtrSENSE Eris using XDA App

NPH- said:
ok... I read bftb0's post... but not sure I'm following
I did the universal one click root method to root my phone and I'm not sure if I need to go to the trouble of flashing something to fix the bootloader or w/e...(not sure if I even messed with the bootloader, maybe I did but this is the noob coming out in me)
If I wanted to send my eris back today to verizon, wouldn't flashing this new zip fix everything I need it to fix and make it comepletely back to its original stock settings??
Click to expand...
Click to collapse
You will be fine. The radio gets flashed by the 2.1 OTA, and you never replaced your bootloader with the one-click method, so that is already stock.
If it happens that you were one of the "leakers", then you have the 1.49.0000 S-ON bootloader, and VZW has shipped phones with that, too.
Be happy.
bftb0

I found that I couldnt re-root the phone with this flashback. I ended up using the PB00IMG.zip file on the SD card and let the phone do itself over. No luck on this one.

Used this today, walked into Verizon store. They looked at it. Sending me a new one as we speak. THANK YOU!!!

on my 5th
rvpartsguy said:
Yep thanks .... will make it easy when I send this phone back for my 5th eris
Click to expand...
Click to collapse
This will make it easier when i get my 6th..
Just received my 5th...lol
Heard as stock runs low for replacements, in certain areas, they are receiving a Droid 2... Can anyone confirm????

[Q] Unable to upgrade from... (solved, but questions) **UPDated**

Hi fellow streak users. Hopefully I'm asking questions in the right place.
Background:
I have read a fair amount of threads on upgrading the streak. I had 1.6, GUASBA111100 (build 6267? from memory), and received the dell 2.2 update notification. Downloaded the update and selected it when it downloaded. The phone re-booted, then sat at a black screen. There it sat for many hours. I tried re-downloading the update many times, but it does the same thing.
I got sick of this and started digging on the web. A simple method seemed to be to rename the file Update.pkg and put it on the root of the sdcard. It then sits at the dell logo. Forever. I have downloaded more images, roms, recoveries than I want to admit. I have attempted following fastboot instructions. They all fail on the reboot.
Currently the phone will not start up at all. Is it really possible to brick the phone?
What I'm trying to do.
Given all the bad publicity I have read about the current 2.2 from dell, I am hoping to install steve's latest version. I am hoping someone has some time and patience to explain how to do this. (commands and which files to use) (as the phone does not seem to respond to all the methods flooding multiple forums).
If you need further information, please ask.

Try flashing the stock recovery for the 1.6 build you have then it should boot as normal. Make sure all the other versions you have are not in the "fastboot" c:/ folder.

OK, here's the update. It's a bit jumbled and random, but I have been up for at least 18 hours fiddling...
I was unable to find the stock recovery for the 1.6 build I had. Probably lots of mismatched files were flashed unnecessarily. Nothing would touch the 'carrier unlocked US version' I had. That is until I tried QDL tool upgrade M 2.7.4.8 Now I suspect it is a beta version of 2.2 that it puts on the phone. It's slow and featureless. But it was the only thing that worked. From there I managed to make clockwork recovery work, and worked my way from steve's 1.4.6 to 1.5.1 to 1.5.2 Somewhere here the phone chucked a spaz and I discovered my phone had been booted off the network (showed no signal coverage). I began to suspect something to do with the imei being blocked (Another streak I was playing with is locked to O2, but came with a rebelsim installed - apparently illegal in australia). I checked the IMEI and it had mysteriously changed. (I suspect it had somehow been put to all zeroes, and something somewhere had given it a 'different' one.) Anyway, I used the QDL tool again, and the original one came back.
Finally what worked for me: QDL tool to flash 2.2, flashthe new amss.mbn, flash clockwork recovery, put steves 1.4.6 on SDcard and flash, then flash 1.5.3
(I couldn't tell you where I downloaded the files that worked. Your results (people who are still seeking action to try and upgrade their software) may vary. All I can say is that now I have downloaded half the internet and installed all the computer drivers, I have hit on a combination that works for me on this computer).
Steve, Thankyou! It's fast, snappy. It has those settings I love to twiddle.
Thank you to everyone else that has either directly or indirectly helped me with your description of how you got yours working.
Thank you for the hosting of the ROMS. I like that you don't have to wait 45 seconds and/or join to download.
A few comments:
I downloaded so many roms and files that it wasn't funny. The problem is that they are all named Update.zip, amss.mbn etc. When they are all in the download folder... Some people just provided the files, others packaged them with a batch file to automate the process. If I was to download them all again, I would download them into folders labelling them...
There seems to be a wide variety of situations/variables that dictate 'what you need to do and how you need to do it' to change roms in the phone. There are half a dozen comprehensive guides on the net, yet all different. I was quite confused. It almost needs some sort of chart where you can pick where you are at the moment, where you want to be, then follow those instructions.
I was also bamboozled with the different tools. QDL, flashboot, ADB etc. I have a bit of an idea, but I'm sure others are equally confused. I know the information is 'out there' but to have it all in one place. What do some of the files do. Why might you need to flash them. Which files are erased by the stock ROM if you don't do anything with them. What does it do when you flash a recovery? How long does it stay on the phone?
There are several parts of the phone that get upgraded. Not sure I have it right, but QDLtool upgrades the modem software (amongst other things) Other things you change is the baseband, SDcard contents etc. (Trying to connect what software files go to what places to what hardware in the phone.)
I do have several questions that have arisen.
1. Am I right in thinking you must flash steves 1.4.6 before you can flash the latest 1.5.3?
2. QDLtools: In theory is it possible to replace the files somehow so it puts steve's latest ROM straight on?
3. Rebelsim: (The small amount of information I have suggests it is illegal in australia) Does it block or change the imei? Can the carrier tell if you are using one?? (not that I use one, apparently they don't work on 2.2)
(that's all for the moment.)

i have been having problems with doing my streak aswell and still am but
ato answer one of your questions that i found out while downloading the whole internet is that the QDL tool can be used to put steves on
here is the instructions i just copied off the qdl page i would of posted a link but i am a new member so i cant post inks yet
Beyond QDLTool
Using QDLTool will get you to a pre-release of v2.2. From here, you’ll want to upgrade to a newer release. The two options that people tend to choose from are to either go up to the official v2.2 ROM from Dell, or install DJ_Steve’s latest ROM.
Official ROM
If you want to go to the latest official ROM from Dell, simply set up your wifi connection, then go to Settings -> About Phone -> System updates. The latest update can then be downloaded and installed, updating your Streak.
Latest Streakdroid ROM
If you want to upgrade to the latest Streakdroid ROM (1.5.3), either from the QDLTool install or from the latest official build, you can follow these steps:
1.Go to the downloads section and grab StreakMod Recovery, the latest 1.5.3 Update and the AMSS for 1.5.1+ (the update and amss are under Roms, StreakMod Recovery is under Recovery)
2.Copy the update-1.5.3.zip file onto the root of your SD card.
3.Extract recovery.img from the StreakMod recovery and place it, along with amss.mbn, into the same directory as QDLTool (QDLTool has a copy of fastboot)
4.Shut down your Streak, then hold down the camera button (all the way) as you turn it back on.
5.The screen should turn white; press ‘Fastboot’ in the top right hand of the screen.
6.Plug in the USB cable – the Streak should now display ‘FASTBOOT_MODE’ at the bottom of the screen.
7.Open a command window and use ‘cd’ to change to the same directory as qdltool.
8.Run: fastboot -i 0x413c flash recovery recovery.img
9.Run: fastboot -i 0x413c flash amss amss.mbn
10.Run: fastboot -i 0x413c reboot
11.As the Streak starts to reboot, hold down both volume buttons.
12.The recovery menu should come up; select option 2 (Upgrade)
13.A Dell logo and an exclamation mark should appear; press power or menu to open StreakMod’s main menu
14.Select ‘apply sdcard:update.zip’ then ‘chose zip on sd card’
15.Find the update-1.5.3.zip file, select it and apply the zip.
16.When the update finishes, press back a couple of times then select the option to reboot your Streak.
17.The Streak will restart. It will take about 5 minutes to complete, but you are now on the latest v1.5.3

at moment i am following the qdl guide to getting the steve rom on my phone so will let you know how it has gone but with that guide the installation at moment seemed seemless now got to see if it goes off the dell logo after a while if not got to recovery but lets hope

no luck so far
stuck on the logo screen but asked for help now its a waiting game

Cheers for that!
Sent from my Dell Streak using XDA App

Is it necessary to use QDLTool to get to the pre-release 2.2 if I am on 1.6 or can I just follow steps 1-17?
The reason I ask is that QDLTool for me just stops at "Check version ... " so I have not been able to complete running it.

i dont know if it is necessary
are all the drivers installed?
i used to have a prob where it kept failing me but all i had to do was change usb port
and got it working but i was running 2.1 stock at the time but that was buggy and crap UI
have you tried just puting 2.1 or 2.2 on your SD card and updating that way

i finally got my streak sorted
i started from scratch
first i installed clockwork mod using fastboot
then installed very version of steves roms in order starting with 1.1.1
and worked my way down and when i installed 1.5.0 i then ran flashed the amss that is required if you want to get the newer versions then installed the rest of the updates and when i got to 1.5.3 i also installed the camera fix
i found it best to put all steves rom zip files onto your SD card at once then it saves having to keep putting one of after another
also after every update leave the phone for a few mins because it does take a lil time to sort the updates out
THE ROM UPDATES (at top also has the AMSS that need flashing)
http://streakdroid.com/?page_id=15&category=1
Camera fix and the comandlines for the AMSS update
http://forum.xda-developers.com/showthread.php?t=802405
clockwork
http://streakdroid.com/?page_id=15&did=9

I don't know if all the drivers are installed. Is there a way to check? I cannot even get into FASTBOOT (POWER + CAMERA) mode and the Streak is just in an infinite reset loop.
Just a note, the older StreakFlash QDLTool completes completely but the newer one in Repairtool just sits infinitely at "Check Version ... "

what operating system you using on your computer

rahbone said:
what operating system you using on your computer
Click to expand...
Click to collapse
Nice of you to ask, as indirectly that was the issue. I outlined it over at the forum mydellmini dot com. Sorry, cannot post hyperlinks as yet. Issue has been resolved. Looking now to load 1.5.3

why not spam a few more posts on here then u can do links when u want 2 in future
you just need 3 more posts i believe the you can do links

[WARNING] Flashing the chineese update.zip will block all further updates FIXED!

Edit: Solution found look below!!!

As I posted in a different thread:
I managed to do it, but it was hackish
How I did it:
Used a terminal directly on the tablet, no adb.
I installed the acer chinese update. I 'dd'ed my old system and flexrom and rebooted. After that I checked for updates, and as luck had it, there was one. I tried it, but it failed half way through the procedure.
I rebooted again, then I 'dd'ed a boot.img on mmcblk0p2 from a 1.016 that matched my original system.img and flexrom.img. WITHOUT REBOOTING (I tried that before, it gives a bad kernel checksum and stops, but I assumed on update it would just patch if the file corresponds and re-sign), I then proceeded to do the update. It rebooted, entered recovery, and lo and behold, IT WORKED! So I'm 100% back to stock.
I would imagine that the same procedure would work when manually updating through recovery (using an extracted update.zip).
I used the kernel from here:
http://forum.xda-developers.com/showpost.php?p=14033507&postcount=27
EDIT: The kernel is stock for ACER_A500_1.016.05_COM_GEN1
Take a look at the thread linked below, get the 1.016.05_COM_GEN1 files (system, flexrom, and boot). If you are not offered an online update (System>About>Check for updates), you need the official update.zip from Acer. Extract the update.zip from the official Acer update THAT MATCHES YOUR FLEX VERSION using the XOR 12 method (see here - http://forum.xda-developers.com/showthread.php?t=1065360&page=20 - note in that post the link is for 03_COM_GEN1, NOT 05_COM_GEN1. For 04_COM_GEN1 and 05_COM_GEN1 see here - http://forum.xda-developers.com/showpost.php?p=14052165&postcount=184. For 03 and 04 you will need to find system.img, flexrom.img and boot.img, for 05 they are linked in the thread below).
EDIT: The thread with the images for ACER_A500_1.016.05_COM_GEN1 is here:
http://forum.xda-developers.com/showthread.php?t=1086785
EDIT: You might pull this off for other flex versions as well, but you would need all the files (system.img, flexrom.img, boot.img AND update.zip) from those versions.
PLEASE NOTE THAT THIS ONLY WORKS IF YOU HAVE THE OFFICIAL UPDATE.ZIP FOR YOUR SPECIFIC FLEX VERSION

Wow, I was about to try that!!!
I'll do that now and see how it goes.
Thanks mate!
EDIT: Worked!

I would expect that the reason an update fails on the Chinese one is that it tries to patch the kernel (which is different from the one expected). The update is a bunch of diffs and patches, and almost no full files, so it cannot be applied over anything but the right files.

Yes that is true. The old kermel checksum check was failing.

huxflux2003 said:
EDIT: Worked!
Click to expand...
Click to collapse
Glad to hear it Take that, you sneaky Acer bastards!

adancau said:
As I posted in a different thread:
I managed to do it though, but it was hackish
How I did it:
Used a terminal directly on the tablet, no adb.
I installed the acer chinese update. I 'dd'ed my old system and flexrom and rebooted. After that I checked for updates, and as luck had it, there was one. I tried it, but it failed half way through the procedure.
I rebooted again, then I 'dd'ed a boot.img on mmcblk0p2 from a 1.016 that matched my original system.img and flexrom.img. WITHOUT REBOOTING (I tried that before, it gives a bad kernel checksum and stops, but I assumed on update it would just patch if the file corresponds and re-sign), I then proceeded to do the update. It rebooted, entered recovery, and lo and behold, IT WORKED! So I'm 100% back to stock.
I would imagine that the same procedure would work when manually updating through recovery (using an extracted update.zip).
I used the kernel from here:
http://forum.xda-developers.com/showpost.php?p=14033507&postcount=27
Take a look at the thread, get the 1.016 files, system, flexrom, and boot, and try it.
Click to expand...
Click to collapse
Ahhhh a true milestone, well done.........

Nice work! Two questions:
Does the update work in the US?
I assume gingerbreak still works after the OTA update?
Thx

gingerbreak works

_motley said:
Does the update work in the US?
I assume gingerbreak still works after the OTA update?
Click to expand...
Click to collapse
A warning first: You DO NOT need to do this if you haven't installed the chinese update.zip (update.acer.zip) before, as that is the only one that changes kernels. Also, if you have anything other than ACER_A500_1.016.05_COM_GEN1, it's debatable if you want to do this (if you do read below), it might be better to wait for an official update.
The kernel above is stock for ACER_A500_1.016.05_COM_GEN1
So it works if you have ACER_A500_1.016.05_COM_GEN1 images, or are ok with changing your flex to that (in which case you would need to flash a system.img and a flexrom.img for ACER_A500_1.016.05_COM_GEN1, reboot, and then flash the kernel from the post above before heading off to recovery and updating - HOWEVER as far as I know no one has tried this, though IN THEORY it should work).
Gingerbreak still works, you can get root back after updating.

Just so I'm clear...
I'm at version 1.139.05 but I got here via the Chinese update.zip.
What do I need to do to get back to stock? Do I need to go back to my old system image and flexrom plus a new kernel?
Could someone post clearer instructions?
Thanks

adancau said:
A warning first: You DO NOT need to do this if you haven't installed the chinese update.zip (update.acer.zip) before, as that is the only one that changes kernels. Also, if you have anything other than ACER_A500_1.016.05_COM_GEN1, it's debatable if you want to do this (if you do read below), it might be better to wait for an official update.
The kernel above is stock for ACER_A500_1.016.05_COM_GEN1
So it works if you have ACER_A500_1.016.05_COM_GEN1 images, or are ok with changing your flex to that (in which case you would need to flash a system.img and a flexrom.img for ACER_A500_1.016.05_COM_GEN1, reboot, and then flash the kernel from the post above before heading off to recovery and updating - HOWEVER as far as I know no one has tried this, though IN THEORY it should work).
Gingerbreak still works, you can get root back after updating.
Click to expand...
Click to collapse
Thanks guys, I did restore using the Chinese update.zip last week and I am currently sitting at kernel 2.6.36.3 with flashed system img=Acer_A500_1.104.05_COM_GEN1, but with recovered Chinese kernel modules for wifi etc. I also flashed a flexrom.img from this build as well. I didn't flash the boot.img from this build, but was thinking about it until huxflux2003 reported the check-sum failure.
So, I am trying to decide what I am going to do. It sounds easy enough to get back to stock now, but I may wait for the official update next month that has 3.1. At this point, I suppose we are assuming that it will be a full update.zip that will work on any tablet (god I hope so). It's about time they gave us a full recovery image...I will be beyond disappointed if they don't. Let's also just hope we can still gain root easily after this.
One more question, if I use all the images from ACER_A500_1.016.05_COM_GEN1 that were posted, does this have to match what I had originally had in any shape or form? It sounds like since all the pieces are from the same build, everything will be fine regardless of what you had to begin with. Is this right?
Thx

To your last question - Theoretically yes, it should work, and I guess you don't need to match what you originally had. I can only speculate, logically though it would makes sense. You definitely need all the images to be from the same build (system+flexrom+boot.img). You also need the official update for that build.

heyoh said:
Just so I'm clear...
I'm at version 1.139.05 but I got here via the Chinese update.zip.
What do I need to do to get back to stock? Do I need to go back to my old system image and flexrom plus a new kernel?
Could someone post clearer instructions?
Thanks
Click to expand...
Click to collapse
To get back to stock you need the three images for your build - system, flexrom, and boot. If there is no online update available, you also need the update.zip for that build (extracted from an official acer update using the XOR 12 method - do a search).
Alternatively, I suppose you could switch to a new build for which you could find all the necessary files (but it hasn't been tried).
Flash system.img using dd. You might need to re-root. Reboot, flash flexrom.img. Reboot once more. Make sure your wifi works (you might need different kernel modules).
Look to see if there is an online update (Settings > About > Check for updates). If there is, cancel it. Flash boot.img on mmcblk0p2. DO NOT REBOOT.
If there was an online update available, now it's the time to perform it. After it's done you will get you back to stock 1.139.05.
If there isn't any update, make sure you have the update.zip on the root of your microSD. Turn off the tablet, then turn it back on holding the volume key closest to the power button. Do not let go of that button until you see some text in the corner. At that moment the update would begin. Once rebooted you will be back to stock.
Hope I've explained it better this time, and it works ok for you. If not, you need to go through the chinese update again. Good luck.

adancau said:
To your last question - Theoretically yes, it should work, and I guess you don't need to match what you originally had. I can only speculate, logically though it would makes sense. You definitely need all the images to be from the same build (system+flexrom+boot.img). You also need the official update for that build.
Click to expand...
Click to collapse
It worked for me too! Thanks again for the tip. I am now at the latest build and ahead of the US update schedule from what I can gather
It asked me to update after I flashed the ACER_A500_1.016.05_COM_GEN1 build system.img and flexrom.img. Even from the US it prompted just fine since I was on ACER_A500_1.016.05_COM_GEN1 build and not ACER_A500_1.104.05_COM_GEN1 as the former is what the differential patch targets.
I cancelled the update once I saw it presented and then blew on the boot.img from the ACER_A500_1.016.05_COM_GEN1 build. Then, without rebooting, I downloaded and applied the update (but with a little hiccup, see below). Now I am at Acer_A500_1.139.05_COM_GEN1 and didn't lose any user apps or settings etc.
Had a scary point though that I will share as it may help others. The first time I tried, the zip wouldn't downloadload and I was getting an HTTP 403 error. I cleared the systemupdater app and FWUpdateService data. I also killed the services and then I was stuck. Instead of conceding to reflashing the Chinese update.zip and starting over, I unzipped the Chinese update.zip and grabbed the boot.img from it. I then dd'ed that image back to the boot partition and rebooted again. It came back up and I this time I was able to do the system update successfully. Whew!

Followed instructions by OP and it worked perfectly! Back to stock and updated.
I think I'll be keeping these system images for next time I brick and have to flash the Chinese update.

Any chance of someone uploading the extracted update.zip for the new Acer_A500_1.139.05_COM_GEN1 so I can update manually using this method.
Thanks in advance

I used the above method to update to 1.139.04 from 1.016.04.
However my kernel is still 2.6.36.3-00001-gf991e5d instead of the 2.6.36.3 everyone else is reporting?

tianqi said:
I used the above method to update to 1.139.04 from 1.016.04.
However my kernel is still 2.6.36.3-00001-gf991e5d instead of the 2.6.36.3 everyone else is reporting?
Click to expand...
Click to collapse
If you directly flashed a 1.139.04 image your kernel has not been updated. You had to flash a 1.016.04 image, flexrom and boot, and then run the update.
You MIGHT have some luck regardless by running the update.zip now (I used it on mine one time when I updated like you did, and it seemed to work, but I have not noticed the kernel number). Be prepared to have to reflash if something goes wrong though.

I did reflash system, flexrom, and boot from 1.016.04...
Second time is still the same...
Kernel is still 2.6.36.3-00001-gf991e5d...

Patched 11.0.12.12.KB05AA ROM for rooted users - install from Fastbootd!!!

[UPDATE]:
**********
I got sick of my phone telling me I needed to update but I couldn't because I'm rooted. So finally got around to patching the last full ROM today w/ the incremental.
This is the fastbootd w/ flash_all.bat script to update to 11.0.12.12.KB05AA. The package for KB05AA (Global/US) is not yet available, hence I'm still making it available here. Be sure to alter the flash script (remove the "rem" before boot.img and recovery.img if you DO NOT want to keep your custom kernel + TWRP) ****************
3.14 GB file on MEGA
mega.nz
THIS IS ONLY FOR 11.0.9.9.KB05AA, BUT READ IT ANYWAY!!!!: ***************
I think this is the first time anyone has actually made a working incremental update for a rooted OOS device, or any with a payload.bin update method that I know of. This method doesn't require any wiping and TWRP / rooted boot.img / custom OOS kernel can be installed right after the script finishes (or left on the device), and you don't even change your active slot (usually, incremental updates will flash to the inactive slot).
I won't get into that many specifics except it was EXTREMELY DIFFICULT, but it works now. Read here if you want to do it yourself in the future, or on another phone. Should work on just about any phone that uses payload.bin files https://forum.xda-developers.com/t/...11-0-9-9-kb05aa-posted.4314677/#post-85425949
You may have to edit the .bat file to pick your RAM type (the lp5 ones are for devices with LPDDR5; it is preset for most of the phones using the LPDDR4 RAM). On the Op8T at least you can do this from adb shell:
adb shell getprop ro.boot.ddr_type; where a 0 is LPDDR4 and 1 is LPDDR5 ram. If it's 1 returned, you need to flash the lp5 files instead of the same named otherwise files in the .bat file (so edit it).
That weird -cow stuff is temp files that prevented the update from working. Not documented anywhere I could find (well, minimally explained by Google), took hours to figure out they were filling the super partition up. I had to re-engineer a Linux project (linked above) to get this working, and have officially updated from 11.0.8.13 to 11.0.9.9 COMPLETELY now. While rooted, without switching slots, and TWRP installed.
You just have to ensure you're on the latest ADB and Fastboot tools and an adb reboot bootloader, followed by a fastboot reboot fastboot should get you there. You can check with: fastboot getvar is-userspace
If it says yes, you're in fastbootd. It actually will work with TWRP installed, I found out later, as long as you reboot in TWRP to fastboot and confirm with the command above you're in fastbootd.
https://github.com/fawazahmed0/Latest-adb-fastboot-installer-for-windows/releases/tag/v1.7 has a script that will get you the Latest ADB and Fastboot and put it in a folder for you.
I uploaded it to Mega. Just use some common sense and look at the flash_all.bat file before flashing. I'd write more but I'm tired as hell from getting this working. Now we'll never have to wait for an incremental update while rooted again, at least in the foreseeable future.

I'm just going to leave this here
https://forum.xda-developers.com/t/...1-kb2003-kb2005.4178675/page-25#post-85386145

g96818 said:
I'm just going to leave this here
https://forum.xda-developers.com/t/...1-kb2003-kb2005.4178675/page-25#post-85386145
Click to expand...
Click to collapse
That never worked for me and others, Always resulted in either bootloop or booting back to previous build

nujackk said:
That never worked for me and others, Always resulted in either bootloop or booting back to previous build
Click to expand...
Click to collapse
I've mentioned it multiple times for people having issues. They need to use the unbrick tool cause there is something wrong with the original rom install from OnePlus.

g96818 said:
I've mentioned it multiple times for people having issues. They need to use the unbrick tool cause there is something wrong with the original rom install from OnePlus.
Click to expand...
Click to collapse
This Devs solution works and i appreciate his work. And appreciate your attempts but didn't work for me So ....

nujackk said:
This Devs solution works and i appreciate his work. And appreciate your attempts but didn't work for me So ....
Click to expand...
Click to collapse
It's good that you found a band-aid fix.

nujackk said:
That never worked for me and others, Always resulted in either bootloop or booting back to previous build
Click to expand...
Click to collapse
Of course I tried that solution first, it didn't work on my device.
I'm glad it did on others' devices, kudos to you for posting it (and I DO appreciate your work), but this is the only one that worked on mine. Why? Who knows. I also followed another guide that didn't work. Or else I wouldn't have wasted all my time making this (it took many, many hours to assemble). I'm not saying it's the best solution (I really hope someone just uses what I put in the other thread and assembles it into an easier format for others to use), but I have a full time job (2 actually) so I can't work on it anymore. But it works, no data loss, and TWRP can be installed. Until the next incremental update comes out, then I'll post another version using the tools I used for this, if your build doesn't work on my device. But only when I have the time...

g96818 said:
It's good that you found a band-aid fix.
Click to expand...
Click to collapse
LoL band-aid fix... Call it whatever you want, it works.
It's actually a patched 11.0.8.3.KB05AA with the incremental update applied to it for 11.0.9.9.KB05AA. So it flashes to the active slot and TWRP / rooted custom kernel can all be installed at the same time, even while you are still rooted with Magisk, and even if TWRP is installed. No data loss. I never claimed perfection on this project, just that it works for me.
Keep doing what you're doing, I'll keep doing what I'm doing. We both just aim to help others anyway. I just couldn't get any other method to work so I came up with this one, extending on the incomplete / abandoned work of others. I didn't come up with Payload extraction. Never claimed to. I didn't come up with fastbootd flashing either.
All the forked and modified code is at my GitHub repo. The fork goes back to several other devs' forks (mine is the 3rd modified fork).

Someone want to point me to the right download for the incremental update to 11.0.9.9.KB05AA? I got a download link but if it's not for this exact ROM, it would be dangerous (I don't know what would break) if I applied it and patched the incremental 11.0.9.9 (which is like a full ROM in the way I distribute it here). I believe the update is 11.0.10.10.KB05AA. I tried downloading as illustrated in the linked thread and it halfway installed (Op8T's don't seem to like the "remove Magisk images" and then install the update method, it totally jacked up my system (like long boot time, alarms didn't work, numbers wouldn't always appear to login to the phone after reboot, etc.), luckily I had backed up Super in TWRP and that fixed it (upon a restore). The one someone told me was the official link to the incremental update did not work with the Linux program I hacked, so it's either incapable of patching an incremental 2x, or I got the wrong file downloaded. My life is so crazy at the moment I don't have time to screw up my phone just to get the incremental update downloaded on my phone and extract it, so if anyone has already done that, please let me know.

mslezak said:
Someone want to point me to the right download for the incremental update to 11.0.9.9.KB05AA? I got a download link but if it's not for this exact ROM, it would be dangerous (I don't know what would break) if I applied it and patched the incremental 11.0.9.9 (which is like a full ROM in the way I distribute it here). I believe the update is 11.0.10.10.KB05AA. I tried downloading as illustrated in the linked thread and it halfway installed (Op8T's don't seem to like the "remove Magisk images" and then install the update method, it totally jacked up my system (like long boot time, alarms didn't work, numbers wouldn't always appear to login to the phone after reboot, etc.), luckily I had backed up Super in TWRP and that fixed it (upon a restore). The one someone told me was the official link to the incremental update did not work with the Linux program I hacked, so it's either incapable of patching an incremental 2x, or I got the wrong file downloaded. My life is so crazy at the moment I don't have time to screw up my phone just to get the incremental update downloaded on my phone and extract it, so if anyone has already done that, please let me know.
Click to expand...
Click to collapse
Better to install the full ROM
Download Oxygen Updater in app store and select your device AA for global and Ba for European device.
Go to settings, system update wait til 100% and Don't reboot yet if you want to keep Root
Go to Magisk and install ota in inactive slot

5star02707 said:
Better to install the full ROM
Download Oxygen Updater in app store and select your device AA for global and Ba for European device.
Go to settings, system update wait til 100% and Don't reboot yet if you want to keep Root
Go to Magisk and install ota in inactive slot
Click to expand...
Click to collapse
I think maybe you misunderstood what I did in this thread. I patched a full ROM with the incremental update of 11.0.9.9.KB05AA. So while OnePlus does not have a full ROM available for download (yet), it is available for download here.
Yeah the method you propose is the "normal" rooted way, but if you're rooted already it forces you to full ROMs not OTAs. You'll be on 11.0.8.3.KB05AA. The goal here is to get on 11.0.10.10.KB05AA (someone NOT ROOTED could download the OTA update using Oxygen Updater and upload it here so I could make a patched version for those that want to keep their root / custom kernel / TWRP / etc and avoid the hassle of unrooting first, which wipes your data partition). At least my Oxygen Updater won't let me download incremental updates even with Magisk Images removed (don't try this unless you're on Op8 / Op8 Pro; some people are having big system update issues on Op8T incremental hence why this thread exists.) It jacked up my system pretty bad (Magisk images removed, Settings / System / System Updates method) until after a boot.img and super restore from TWRP. Not all devices were setup the same (mine is a US carrier converted to US KB05AA). To my knowledge, no direct download has been posted for KB05AA incremental update. Here or on TG. If you have found one, please post a link here. The only one out I've seen works on European ROMs. OnePlus always does KB05AA last for whatever reason.

11.0.10.10.KB05AA posted with caveats - please back up your data as suggested in case the Phone Services APK doesn't fix your SIM after a flash, and you end up formatting the data partition. You may want to try some other methods or just plan on restoring (not with TWRP Alpha in my experience).

mslezak said:
Guys, bad news. So 11.0.10.10.KB05AA incremental does something to the data partition and kills your SIM access.
...
Click to expand...
Click to collapse
I successfully update from 9.9 to 10.10 including keeping root. I have no issues with my Sim card. So, for me, the update is fine.
However, I believe that the 10.10 update includes a key change. This results in the data partition being unreadable if you swap back to the previous slot after the update. I found this out by doing just that using TWRP.
But syncing the 10.10 firmware to the inactive slot fixes this. It might be possible (I haven't tried it) to just sync the keymaster partition to the inactive slot and then restore 9.9 (excluding keymaster).

BillGoss said:
I successfully update from 9.9 to 10.10 including keeping root. I have no issues with my Sim card. So, for me, the update is fine.
However, I believe that the 10.10 update includes a key change. This results in the data partition being unreadable if you swap back to the previous slot after the update. I found this out by doing just that using TWRP.
But syncing the 10.10 firmware to the inactive slot fixes this. It might be possible (I haven't tried it) to just sync the keymaster partition to the inactive slot and then restore 9.9 (excluding keymaster).
Click to expand...
Click to collapse
Can you explain how you managed to update it? I'm screwed at this point anyhow, would like to hear how you did it. Are you just saying when you update flash to both slots and the data is still readable? Instead of flashing to active only? I still have the extracted / patched ROM, not going to try it out now (or for a while) unless I know someone has figured out a way to make it not break the system data. (Note: I'm on a very hacked phone; it's a carrier T-mobile originally fastbootd converted to Global, then updated on Global since then). I realize most people probably don't have a phone that's been altered this much. Then the easier methods are more likely to work. I'm also running a custom fork (mine) of RadioActive kernel (just tweaked how I like it, wakelocks blocked to save idle battery, some GPU frequencies added, etc). I tried running just the patched boot.img with Magisk but still Phone Services was busted.

@mslezak, When I get an update I:
- use a terminal session (you could also use ADB) to restore the stock boot and recovery (this way I don't lose root yet)
- install the update but don't reboot
- copy the new boot image and patch it
- turn on airplane mode (to avoid SafetyNet and certification issues in the next step)
- reboot the phone and the updated system comes up
- flash the patched boot image and TWRP in fastboot/bootloader
- reboot and disable airplane mode
This is basically @osm0sis' process from https://forum.xda-developers.com/t/...ices-platforms.2239421/page-149#post-84764713
No, I'm not saying flash to both slots, because that will make it impossible to fall back to the current system if the update fails (though this is meaningless if you're manually flashing partitions).
I've got into the habit of syncing active to inactive (after I'm happy with the update) simply because it's required when going from OOS to a custom ROM (I use a shell script based on the LineageOS sync zip). And, after the sync, I can now access the data partition from the inactive slot (which wasn't the case just after the update due to the different keys).

mslezak said:
Can you explain how you managed to update it? I'm screwed at this point anyhow, would like to hear how you did it. Are you just saying when you update flash to both slots and the data is still readable? Instead of flashing to active only? I still have the extracted / patched ROM, not going to try it out now (or for a while) unless I know someone has figured out a way to make it not break the system data. (Note: I'm on a very hacked phone; it's a carrier T-mobile originally fastbootd converted to Global, then updated on Global since then). I realize most people probably don't have a phone that's been altered this much. Then the easier methods are more likely to work. I'm also running a custom fork (mine) of RadioActive kernel (just tweaked how I like it, wakelocks blocked to save idle battery, some GPU frequencies added, etc). I tried running just the patched boot.img with Magisk but still Phone Services was busted.
Click to expand...
Click to collapse
Thats not very hacked/hacked at all, and quite a few use that setup

xstefen said:
Thats not very hacked/hacked at all, and quite a few use that setup
Click to expand...
Click to collapse
LoL I gave up fastbootd flashed to 11.0.10.10.KB05AA and formatted data, let Google download everything it backed up, and am back in business. Just have a lot of apps to login to / Magisk modules to add / etc.
So yeah my patched 11.0.10.10.KB05AA works but the data must be formatted or the SIM doesn't work (at least for me; I don't know if anyone else has tried it since I just posted it a few hours ago; it could be that it works for some without causing issues, I don't have any idea). The goal was to not have to mess up the data partition.... but I can't control what OnePlus does in their updates... Try what worked for others posted here first I'd suggest, or just make solid backups of everything knowing you're going to likely need to reinstall / re-login to everything and format the data partition. New pin, new fingerprint, etc. Re-login to your wifi blah blah.
It's still a full unreleased ROM so I posted it for those that don't mind taking backups (outside of TWRP) if they want to keep root & TWRP on the new release... Yeah a pain to setup if you aren't warned to use another backup method (maybe there is a better backup method, maybe Migrate (app store early access) is developed enough for easy transfer now, I know many people said it worked well in the past but haven't been following the updates. Still free).

It dawned on me later that since the only thing that didn't work using this method going from 11.0.9.9.KB05AA to 11.0.10.10.KB05AA was phone services, that I should just include the working version in this post. Since I already did it the hard way and restored everything back to normal. AS I SAID ABOVE, IF PHONE SERVICES ISN'T ENOUGH TO FIX THE ISSUE, PM ME AND I CAN EXTRACT MORE RELATED FILES UNTIL IT WORKS AGAIN. Unfortunately, I can't just downgrade to 11.0.9.9.KB05AA and keep trying fastbootd over and over again as I don't have the time.

g96818 said:
I've mentioned it multiple times for people having issues. They need to use the unbrick tool cause there is something wrong with the original rom install from OnePlus.
Click to expand...
Click to collapse
The whole point of this is to AVOID the unbrick tool, reinstalling an outdated version, updating each new ROM build since the brick tool was made, and starting over clean. I think... Have a hunch at least we're almost there on 11.0.10.10.KB05AA with an APK install... Although just backing up everything first will always work (if you don't mind formatting your data partition) just as it's posted here already. Always an issue for us rooted users (especially on Global) since we're always last in line to get a full ROM. This IS a full ROM, payload extracted and patched with incremental updates. Still not available from OnePlus Global (KB05AA) as I checked today, so still relevant.

Ladies and Gents,
I have removed some off topic posts from this thread because I believe we could express the same meaning in more civil words. Please try to do that from now on.
Thanks.
Jerry
FSM