Guys
Sorry for a new thread, but have trawled through all posts and not found one post relating to the problem I have with my XT910 Razr
I upgraded to T-Mobile leak successfully. Then the new OTA generic Europe appeared. I followed other guidelines that other users had tried and succeeded with - that is flash the boot_new.img and the system_signed from the correct SBF according to posts (which if I hadn't had the correct SBF system, would've given me a message that others have had - so I know, well - think, I have the correct one as . . .
However, and this has been doing my head in now for 2 days, I get this message
Verifying current system
assert failed: apply_patch_check
("MTD:boot:8388608:5fff8425560eb1002b467062de2b355b45090ad7:838
8608:2997ddb421e1d44b026410339e343f60b3bb65bd")
E:Error in /tmp/sideload/package.zip
(Status 7)
. . . etc
Now I have data wiped, cache wiped over and over again. I have a feeling it's to do with the boot_new.img posted - oh damn, don't tell me it's a CDMA patch that I've applied to GSM (maybe too much sun in England at the moment)
Anyway, first post on here after being a member for around 6 years and I am at my wits end.
If anyone could help it would be extremely appeciated
Cheers, in advance
Gazblade said:
Guys
Sorry for a new thread, but have trawled through all posts and not found one post relating to the problem I have with my XT910 Razr
I upgraded to T-Mobile leak successfully. Then the new OTA generic Europe appeared. I followed other guidelines that other users had tried and succeeded with - that is flash the boot_new.img and the system_signed from the correct SBF according to posts (which if I hadn't had the correct SBF system, would've given me a message that others have had - so I know, well - think, I have the correct one as . . .
However, and this has been doing my head in now for 2 days, I get this message
Verifying current system
assert failed: apply_patch_check
("MTD:boot:8388608:5fff8425560eb1002b467062de2b355b45090ad7:838
8608:2997ddb421e1d44b026410339e343f60b3bb65bd")
E:Error in /tmp/sideload/package.zip
(Status 7)
. . . etc
Now I have data wiped, cache wiped over and over again. I have a feeling it's to do with the boot_new.img posted - oh damn, don't tell me it's a CDMA patch that I've applied to GSM (maybe too much sun in England at the moment)
Anyway, first post on here after being a member for around 6 years and I am at my wits end.
If anyone could help it would be extremely appeciated
Cheers, in advance
Click to expand...
Click to collapse
Looks like you're trying to flash an ICS update from wrong GB.
What's the GB version you are updating from? And whats the version you're trying to flash?
Cheers
Just to be sure you got the right System_signed I'll post it again
http://sbf.droid-developers.org/umt...USASPDRRTGB_HWp2b_Service1FF_fastboot.xml.zip
No other would work!
And this is the boot.img I've used to upgrade
http://www.mediafire.com/?rh4flyvuo5lej9w
Gesendet von meinem XT910 mit Tapatalk 2
Thanks for quick reply HSD.
Unfortunately I have also used the boot.img and also system_signed from the links you've posted.
When I've done that (applied that boot and system) and then applied the OTA (xt910_ics_4.0.4_for 2_3_6_en_eu_retail_ota_b731.zip) it doesn't even get as far as the post above - fails on update package check
Then I read another post that used
SPDREM_U_01.6.5.1-167_SPU-15-M2_SIGNEuropeAustraliaEMEA_USASPDRRTGB_HWp2b_Service1FF_fastboot.xml.zip
and flashed boot_new.img and system_signed (from the extract) and have got further.
And the previous error is now what I get.
The error using the M2-3 (link you've posted) is different. Says something along the lines of wrong build.prop
I would post the error but, unfortunately as my phone is currently bricked, I am charging on BP Tools.
Is there any way of flashing the boot_signed and overwrite the current one using ADB or motofastboot/eprj. I've tried and just get a Preflash error
I think i know what kind of error you mean. We got an couple of bricked phones in Germany allready. Saved some of them, but 2 Guys would stay bricked until there's a working Fastboot for ICS.
---------- Post added at 01:30 AM ---------- Previous post was at 01:28 AM ----------
Gazblade said:
Is there any way of flashing the boot_signed and overwrite the current one using ADB or motofastboot/eprj. I've tried and just get a Preflash error
Click to expand...
Click to collapse
How do you flash the files?
---------- Post added at 01:35 AM ---------- Previous post was at 01:30 AM ----------
Put the Files of the eprj-mfastboot (3 Files), the system signed and the boot_new.img on your desktop.
Then hit the Startbutton on windows and search for > cmd <
open it an write this commands (every line confirm with ENTER)
cd desktop
eprj-mfastboot flash boot boot_new.img
eprj-mfastboot flash system system_signed
(I use Windows 7 for this)
I've tried various ways. Standard adb fastboot, moto-fastboot, eprj-mfastboot
Same with each
. . . . flash boot boot_new.img
. . . . flash system system_signed
Then wipe data/factory reset and then recovery mode the OTA
I've even even edited the xml file in the extracted SBF so the _signed files that don't work are deleted and then ran RSD Lite with the edited SBF again - and I've also done that with Eternity's alternative flash method.
No joy with any!
Been trying for 2 and a half days now and I wouldn't be so frantic if I didn't work for myself and this is my contact number for customers!!
Hurry up and release the SBFs Moto! Although I am concerned that the boot_new.img that I've applied has screwed things up!
And your last post is the last thing I've tried.
As you've said
Put the Files of the eprj-mfastboot (3 Files), the system signed and the boot_new.img on your desktop.
Then hit the Startbutton on windows and search for > cmd <
open it an write this commands (every line confirm with ENTER)
cd desktop
eprj-mfastboot flash boot boot_new.img
eprj-mfastboot flash system system_signed
Done that and no joy. I'm wondering if I've got the correct OTA downloaded?
I think you've maybe tried to much, like the Guys here in Germany.
Unfortunately we can't do an clean flash at the moment and in Germany ICS would not released untill the Maxx is in Store (end of June). That're the latest news i've read.
I have to ask this now (experience from the last days ):
You unpacked the two Parts of the new Leak to got the right Update.zip and you're sure, that you got it on your SD and doesn't try to flash the T-Mobile Leak again?
---------- Post added at 01:57 AM ---------- Previous post was at 01:54 AM ----------
Blur_Version.651.167.26.XT910.Retail.en.EU.part1.rar
Blur_Version.651.167.26.XT910.Retail.en.EU.part2.rar
That's the new Leak!
Two parts? I thought there was three from mediafire? Unrared all three. Is there another version I've not actually seen in the posts?
And the t-mobile is not on the SD card, so yes am flashing, well what I at least consider, the correct one (ends in b6371.zip?)
und vielen Dank soweit Freund
Downloading now thanks. Will let you know in oh, about 7 minutes apparently!
HSD-Pilot said:
I think you've maybe tried to much, like the Guys here in Germany.
Unfortunately we can't do an clean flash at the moment and in Germany ICS would not released untill the Maxx is in Store (end of June). That're the latest news i've read.
I have to ask this now (experience from the last days ):
You unpacked the two Parts of the new Leak to got the right Update.zip and you're sure, that you got it on your SD and doesn't try to flash the T-Mobile Leak again?
---------- Post added at 01:57 AM ---------- Previous post was at 01:54 AM ----------
LOL
That's the new Leak!
---------- Post added at 01:59 AM ---------- Previous post was at 01:57 AM ----------
Told me, when you got it. I'll delete the links after that
Click to expand...
Click to collapse
arent those my links?
And this should be done with the SBF you posted earlier?
Got them thanks
Now to give it a go
leisures said:
arent those my links?
Click to expand...
Click to collapse
NOOOOOO
---------- Post added at 02:17 AM ---------- Previous post was at 02:15 AM ----------
Gazblade said:
And this should be done with the SBF you posted earlier?
Click to expand...
Click to collapse
Yes!
---------- Post added at 02:20 AM ---------- Previous post was at 02:17 AM ----------
Should i let them in or delete them...That's the big question.
Have seen to many bricked Devices in the last days (I can't delete the Quote anyway so happy flashing )
HSD-Pilot said:
NOOOOOO
---------- Post added at 02:17 AM ---------- Previous post was at 02:15 AM ----------
Yes!
---------- Post added at 02:20 AM ---------- Previous post was at 02:17 AM ----------
Should i let them in or delete them...That's the big question.
Have seen to many bricked Devices in the last days (I can't delete the Quote anyway so happy flashing )
Click to expand...
Click to collapse
ok ok i can block the files from my mediafire acc anyway, want me to do it?
Let them in. I think the people now know about the risks by flashing this Leak.
And your Links are posted all over the world, so don't make people unhappy
I'm out now.
02:30am and to much Diablo III today.
See Ya
So far so good. Looks like my fault in downloading wrong OTA.
You are a God Send (if I wasn't an atheist!). I owe you a big, big favour HSD.
Thank you very, very much my friend
HSD-Pilot said:
Let them in. I think the people now know about the risks by flashing this Leak.
And your Links are posted all over the world, so don't make people unhappy
I'm out now.
02:30am and to much Diablo III today.
See Ya
Click to expand...
Click to collapse
what i found funny is that the link for the part1 has been downloaded 351 times and part2 1806.....who download only part2???
Related
When I tryed to flash MeanICS on my evo all appeared to go well until I rebooted. After rebooting I only got a black screen. I can still boot into bootloader which gives me hope. I tryed reflashing Mean and a couple of other ROMs but the problem persists. I was hoping someone may have had a simular problem and had a fix or workaround that I could try.
Thx
Check my guide I listed this exact issue in troubleshooting, if you have any questions after feel free to ask
Thank you for your help. I now understand the problem (bootloop, caused probably by the kernel) but even a full wipe using twrp I can't get any ROMs to load, and I was not thinking and didn't make a back up.
Download a ROM and verify the check sum then unzip and place the boot.img in your adb tools (or SDK depending on what you use) boot to boot loader and select fastboot (from PC terminal, sorry) type fastboot flash boot boot.img and then in recovery try to flash the ROM zip. Be sure to wipe dalvik, cache, factory reset and system first to avoid issues
---------- Post added at 05:35 PM ---------- Previous post was at 05:22 PM ----------
I just noticed you said black screen, that most definitely is a kernel issue but its a ROM base mismatch, you just needed to fast boot the mean kernel most likely
I had this problem literally yesterday. All you need to do is flash the boot.img located in the unzipped folder of meanrom and then flash via fast boots via pc or mac. Wipe everything first and then flash the BOOT.IMG. THEN FLASH MEAN ROM and wipe cache etc.
Sent from my EVO on CM10
Yeah I read too quickly and missed the part about the black screen. I decided it was better to outline the whole process
ok i downloaded a new rom, verified md5sum, and unzipped the rom. i also downloaded eclipse and am linking eclipse and android sdk to try and make this a little easier, i hope. i feel like such a total noob, well for the most part i am.... i guess what i am saying is that i don;t know if i am removing boot.img from zip or if i'm just checking something on the boot.img using adb
You just need adb tools, you are making this a little harder then it needs to be
---------- Post added at 06:08 PM ---------- Previous post was at 06:02 PM ----------
Sorry, couldn't remember the exact name, do a search for evo4glteroot2 its basically adb tools
http://downloadandroidrom.com/file/HTCEvo4GLTE/rooting/Evo4GLTERoot2.zip
It took me a bit to realize what you guys were telling me to do.. I can be dence at times. But thank you very much my phone is now fixed.
No prob. Sorry if I at any time seemed hostile, I have been having issues with loud neighbors who have legal permission to make noise all damn night and have done so all week, I'm very agitated
---------- Post added at 08:01 PM ---------- Previous post was at 08:00 PM ----------
Oh god now I'm confusing threads again
Hey there folks. I should probably preface this whole thing by letting everyone know that I have successfully SBF'd my DX2 in the past a few times, but most recently I keep getting an error in the middle of the process. Sine I've disconnected the phone after that error message, it's basically just been a brick. I've repeated the process a few times and I continue to get error messages at the same point in the process.
I also looked on the web and downloaded a new version of RSD Lite (5.4.4) and tried it with that version with still the same results. Originally I had decided to SBF in the first place because I had flashed the CM10A3 mod to my phone and there were all kinds of bugs making the phone unusable for that OS. I attempted to reflash something else (like the CM7.2 that I had running on it flawlessly) but the verbiage for that ROM said I needed to start from GB2.3.4, so I was afraid to go straight to CM10 from CM7. Admittedly, I am a little confused as to whether all new mods can only be flashed from GB2.3.4 or if it's okay to go directly from one mod to another, so a little advice there would be appreciated too......
So....is this thing savable???
Thanks in advance,
Scott
DX2 ezSBF
link in my list
sd_shadow's [Collection] of Links for Droid X2
Sent from my XT862 using xda premium
sd_shadow said:
DX2 ezSBF
link in my list
sd_shadow's [Collection] of Links for Droid X2[/URL]
Sent from my XT862 using xda premium
Click to expand...
Click to collapse
Hey Shadow....thanks for the advice as well as the great work on putting together the Linux-based SBF tool. I tried it and everything was going smoothly until it started to flash and very early on I got an error message:
"Uploading RDL03 failed 00080000/00300000
!! failed"
Any ideas??
sounds like hardware failure.
may not be fixable.
you can keep trying to flash the sbf with rsd lite or ezSBF
or you could try flashing the boot.img with moto-fastboot.exe
I'll post some links
Sent from my XT862 using xda premium
---------- Post added at 12:31 PM ---------- Previous post was at 11:36 AM ----------
read SBF "ACTUALLY" Fails... Need help with ADB fastboot
seems like same error
download moto-fastboot.exe and DX2 boot.img
move to a folder like c/root
and unzip both
boot DX2 to fastboot
a. Pull the battery.
b. Plug the battery back in.
c. Power up your phone by pressing and holding the VOLUME DOWN BUTTON and then pressing the POWER BUTTON until you see the words FASTBOOT (in white) at the top of the DX2’s screen. This should only take about 3-5 seconds
d. e. Press the VOLUME UP BUTTON and the screen will say Starting Fastboot protocol support, when you see that phone is ready
Open the CMD, (Start/all programs/accessories/command prompt and enter the these commands.
cd/
cd c:root
moto-fastboot.exe flash boot boot.img
So I flashed the boot.img via your instructions and everything seemed to go fine so I tried the ezSBF method but it failed again. I also tried to SBF via RSD Lite to see if that would work but it failed also. Clearly there was some king of progress though because this time I got 29% of the way thru the flashing process as opposed to only 4% like before flashing the boot.img.
Frustrated!!
try a different version of rsd lite
5.5.4 isn't that new
---------- Post added at 05:39 PM ---------- Previous post was at 05:36 PM ----------
don't know when 5.5.4 came out, but 5.6 has been out since November 2011,
sd_shadow said:
try a different version of rsd lite
5.5.4 isn't that new
---------- Post added at 05:39 PM ---------- Previous post was at 05:36 PM ----------
don't know when 5.5.4 came out, but 5.6 has been out since November 2011,
Click to expand...
Click to collapse
Gotchya....will do!! I understand that the SBF process can be a bit finicky with USB cables too....I'll try a different one of those too. Thank you for your input!
As I bricked my SGH_S959G by flashing empty pit file now phone is dead (no jtag here).
If some one has experience who can flash one of the attatched zips in cwm and give me the Debrick dumb file generated in sdcard.
thanks in advance.
Any one.
What exactly do these do?
---------- Post added at 09:40 PM ---------- Previous post was at 09:39 PM ----------
I have this phone but I'm not entirely sure i want to flash these
---------- Post added at 09:51 PM ---------- Previous post was at 09:40 PM ----------
mohammad.afaneh said:
As I bricked my SGH_S959G by flashing empty pit file now phone is dead (no jtag here).
If some one has experience who can flash one of the attatched zips in cwm and give me the Debrick dumb file generated in sdcard.
thanks in advance.
Click to expand...
Click to collapse
Have you checked here?
http://forum.xda-developers.com/showthread.php?t=1982571
Straight Talk SGS2- SGH-S959G
If you extract the zip file and take a look to updater-script you will see that its make a copy of first 80 megabite of emmc (boot loader and some other files) that files make phone boot turn on and boot to recovery nor download mod.
Look here
http://forum.xda-developers.com/showthread.php?t=2581166
Yesterday i brickid my s3 and fixed it by steps in that thread.
and my 959G is dead 2 months ago so i will try it.
dont flash it if you dont know what inside it.
mohammad.afaneh said:
If you extract the zip file and take a look to updater-script you will see that its make a copy of first 80 megabite of emmc (boot loader and some other files) that files make phone boot turn on and boot to recovery nor download mod.
Look here
http://forum.xda-developers.com/showthread.php?t=2581166
Yesterday i brickid my s3 and fixed it by steps in that thread.
and my 959G is dead 2 months ago so i will try it.
dont flash it if you dont know what inside it.
Click to expand...
Click to collapse
Yeah, I'm not
Hello, I am new as a poster on these forums, but not new as a visitor, but I thought I would have the best luck asking around here. So basically I was being stupid and on my HTC One M8, which has been rooted for some time, I wanted to put the 5.0.1 GPE Skydragon on. I had been trying to get S-off in the past, but it had failed. Today I tried again, but still wouldn't get past first bottle. Either way I was impatient and misinterpreted a tutorial someone had created, implying you already had S-Off. I though that would be a later step and this was a different method, so I tried to flash the ROM with S-On, and things went downhill from there. I could make my phone vibrate by using the volume buttons, but a dark screen that displayed nothing. I was able to access my boot loader and TWRP, so I know the screen isn't kill. When inside of TWRP, I clicked on system cache along with Davlik and other ones, so it screwed my system no also. Also, if I plug it into my computer the internal sd and external sd do appear, so that's good. But in recap I am stuck where I can only access TWRP and boot menu, and because my S is on, I cant seem to flash anything nor get past it. Please help, my phone is vital especially in Finals Week.
The best way to recover is to flash a RUU...I do not have links for you, but I have been here for a few months. I've heard when problems exist, the best thing to do is flash a RUU...I might be completely wrong, but give wonder_never_cease a pm. He's a very knowledgeable person.
jxcorex28 said:
The best way to recover is to flash a RUU...I do not have links for you, but I have been here for a few months. I've heard when problems exist, the best thing to do is flash a RUU...I might be completely wrong, but give wonder_never_cease a pm. He's a very knowledgeable person.
Click to expand...
Click to collapse
couldn't find that user... he is on the forum, correct?
Its wonders_never_cease
But in all seriousness this information is posted time and time again here. I'm sure wonders has better things to do than to do your searches for you. Not trying to be rude but its all right here.
- Sent from a payphone ...
tommy_riley said:
Its wonders_never_cease
But in all seriousness this information is posted time and time again here. I'm sure wonders has better things to do than to do your searches for you. Not trying to be rude but its all right here.
- Sent from a payphone ...
Click to expand...
Click to collapse
Well, I have looked around, nothing in the same predicament that I am in currently... So I will send him a message anyway, maybe I'll get lucky.
Update: I messaged him and no reply yet, this is urgent, so if anyone can directly help me I would appreciate it greatly.
As instructed above if unable to boot into bootloader to flash a custom recovery and pushing a custom rom to phone,flash the ruu thats for your software build you had prior to this fiasco,patience is a virtue eh...lol...
tommy_riley said:
Its wonders_never_cease
But in all seriousness this information is posted time and time again here. I'm sure wonders has better things to do than to do your searches for you. Not trying to be rude but its all right here.
- Sent from a payphone ...
Click to expand...
Click to collapse
"sent from a payphone". i love it!
"all I can really do, is stay out of my own way and let the will of heaven be done"
ryankrogh said:
When inside of TWRP, I clicked on system cache along with Davlik and other ones, so it screwed my system no also.
Click to expand...
Click to collapse
You mean you wiped something, like system? What were you trying to accomplish by doing this, exactly?
---------- Post added at 01:43 PM ---------- Previous post was at 01:41 PM ----------
ryankrogh said:
Well, I have looked around, nothing in the same predicament that I am in currently...
Click to expand...
Click to collapse
This same situation gets asked several times a day.
Just restore the nandroid you made. If you didn't make one, than that is a mistake I suggest you never repeat ever again.
If no nandroid, you just need to flash a ROM (either by adb sideloader, adb push, mount memory in recovery, or put on removable SD). A ROM that matches you current firmware will avoid the long boot times and broken WiFi that are symptomatic of a firmware mismatch. You haven't posted enough info for us to know what firmware you are on (hboot and radio number).
---------- Post added at 01:45 PM ---------- Previous post was at 01:43 PM ----------
jxcorex28 said:
The best way to recover is to flash a RUU...I do not have links for you
Click to expand...
Click to collapse
http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Relock the bootloader to RUU (with s-on).
---------- Post added at 01:52 PM ---------- Previous post was at 01:45 PM ----------
BTW, what is with all the bad thread titles today? At least 4 threads in this forum titled "HELP", "[Q]" or something similar. This this is a Q&A and help forum, so of course you are asking for help and have a question. But please try to give your thread a specific title describing your issue, to help keep the forum organized.
redpoint73 said:
You mean you wiped something, like system? What were you trying to accomplish by doing this, exactly?
---------- Post added at 01:43 PM ---------- Previous post was at 01:41 PM ----------
This same situation gets asked several times a day.
Just restore the nandroid you made. If you didn't make one, than that is a mistake I suggest you never repeat ever again.
If no nandroid, you just need to flash a ROM (either by adb sideloader, adb push, mount memory in recovery, or put on removable SD). A ROM that matches you current firmware will avoid the long boot times and broken WiFi that are symptomatic of a firmware mismatch. You haven't posted enough info for us to know what firmware you are on (hboot and radio number).
---------- Post added at 01:45 PM ---------- Previous post was at 01:43 PM ----------
http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Relock the bootloader to RUU (with s-on).
---------- Post added at 01:52 PM ---------- Previous post was at 01:45 PM ----------
BTW, what is with all the bad thread titles today? At least 4 threads in this forum titled "HELP", "[Q]" or something similar. This this is a Q&A and help forum, so of course you are asking for help and have a question. But please try to give your thread a specific title describing your issue, to help keep the forum organized.
Click to expand...
Click to collapse
The issue has been resolved after a stressful weekend, there was a droid news article that worked for me, so the RUU method worked in the end. Thanks anyway!
We need captures of the OTA payload, URL, metadata, etc. Anything we can get. We also need to study how our partitions change and which have changed. We also need a sound method to accept OTA when rooted (Temp Magisk revert, accept OTA, reinstall Magisk to other slot, reboot?) or revert to stock (restore both sets of boot and dtbo slots?).
Only lead I have is from our NSG friends. Action happens in /data/ota_package. Not sure if anything ends up in /cache.
This OTA includes fixes for GPS, December security level, and "general bugs fixed". n41 5G does not appear to be included, but recent FCC filings suggest that it's at least being tested.
https://fccid.io/2ABZ2-EE143/Test-Report/I19Z62071-WMD01-Part27-NR-Rev0-4569370
https://fccid.io/2ABZ2-EE143/Letter/FCC-cover-letter-C2PC-letter-template-rev1-4569357
It would be a really good time to bring back a Telegram or Discord channel.
Edit: OTA package snagged! https://android.googleapis.com/pack.../aa21536ec572b3c15ab76c49160441f041cf6a27.zip
Credit to xian from the NSG Telegram
<Mod edit>
Can I take this update if I was once rooted but have now flashed back to original boot.img? Obviously once updated I'll run the partition script to pull new partitions so I have virgin partitions on the new build.
OTA Direct Link
Not sure if it will take for me because of my haxing about.
---------- Post added at 12:13 ---------- Previous post was at 12:06 ----------
ntzrmtthihu777 said:
OTA Direct Link
Not sure if it will take for me because of my haxing about.
Click to expand...
Click to collapse
Didn't take. Investigating.
---------- Post added at 13:05 ---------- Previous post was at 12:13 ----------
Bad vbmeta_a hash.
---------- Post added at 13:07 ---------- Previous post was at 13:05 ----------
kirschdog1 said:
Can I take this update if I was once rooted but have now flashed back to original boot.img? Obviously once updated I'll run the partition script to pull new partitions so I have virgin partitions on the new build.
Click to expand...
Click to collapse
apparently you need all stock partition. I need a good vbmeta_a apparently
ntzrmtthihu777 said:
OTA Direct Link
Not sure if it will take for me because of my haxing about.
---------- Post added at 12:13 ---------- Previous post was at 12:06 ----------
Didn't take. Investigating.
---------- Post added at 13:05 ---------- Previous post was at 12:13 ----------
Bad vbmeta_a hash.
---------- Post added at 13:07 ---------- Previous post was at 13:05 ----------
apparently you need all stock partition. I need a good vbmeta_a apparently
Click to expand...
Click to collapse
U want mine from the read back so i can upload
omariscal1019 said:
U want mine from the read back so i can upload
Click to expand...
Click to collapse
Vbmeta_a? Sure. At class so I can't do anything with it yet.
Good news guys, Looks like we will be getting our MSM Tool in about a week
By creating our own ops or the kindness of OnePlus and leakers?
I'm not sure how that would change our situation with the new protections OnePlus is using on MSM tools. We'd have a good rescue method at the very least, but likely not a conversion method.
The only undisclosed exploit I know of is for the Sprint OnePlus 7 Pro 5G and that's purely for a bootloader and/or SIM unlock.
Edit: Saw your post in the other thread. I really hope the tech isn't full of crap like the others promising remote sessions that they never follow up on or provide the wrong files.
ntzrmtthihu777 said:
Vbmeta_a? Sure. At class so I can't do anything with it yet.
Click to expand...
Click to collapse
In a bit ill upload
So i shouldn't accept this update if rooted then?
omariscal1019 said:
In a bit ill upload
Click to expand...
Click to collapse
Cool. Looks like both sides have to be how TMobile
expects them to be in order for the update to work.
ntzrmtthihu777 said:
Cool. Looks like both sides have to be how TMobile
expects them to be in order for the update to work.
Click to expand...
Click to collapse
Yeah that **** happ n on the moto z2f back like two years ago couldnt update if u werent stock on both slots
Bildo41383 said:
So i shouldn't accept this update if rooted then?
Click to expand...
Click to collapse
Think it won't work anyway. It checks hashes of the
other side before applying, and if they don't match
it can't apply the update (brotli diff format, not a
full update.zip style update which just replaces
everything).
But what's the end state of the slots after an update?
A on 16, B on 19? Is 13/14 gone?
LLStarks said:
But what's the end state of the slots after an update?
A on 16, B on 19? Is 13/14 gone?
Click to expand...
Click to collapse
Yeah. My understanding is that 19 installs over 13. I'm
not one hindered percent sure though.
Partition hashes are going to be important. I think we still have our backups and whatever was documented in TEK's thread.
LLStarks said:
Partition hashes are going to be important. I think we still have our backups and whatever was documented in TEK's thread.
Click to expand...
Click to collapse
Note that these hashes may be deep dm-verity
hashes not plain sha256 and so on.
i know i can't get the update to actually update it fails i have tried going back to stock from my backed-up images locked the bootloader seems i cant get it to update
Yeah I'm having the same problem. All I did was root by flashing Magisk. I have since uninstalled the root/Magisk etc and I still get install problem at the very end of the OTA install . Thoughts?
I haven't updated to the new OTA yet, because I now have to restore from a backup so that it doesn't error again. I was curious how many partitions changed since January 2nd, 2020, and since rooting and using the phone for two weeks from the time of that 02 JAN backup the SHA-1 checksum of 43 different partitions have changed. I'll have to look at logs to where the error is from (i.e., because it happened even after I flashed back original unmodified boot_b), or I could just restore everything back.
adb sideload says it flashed it but phone stays the same...