Database Develop

[Q] WW 10.26.1.7 firmware zip

Hi there,
I've been searching around to find a specific firmware zip for my new tablet, the SKU: WW, Version: 10.26.1.7.
It appears that asus has pulled this file and was wondering if anyone still has this file available somehow.
I soft-bricked my tablet and am not capable of flashing any other (earlier) firmware zip.
Any help would be greatly appreciated.
Yours sincerely,
Rens "Ikkerens" Rikkerink

Ikkerens said:
Hi there,
I've been searching around to find a specific firmware zip for my new tablet, the SKU: WW, Version: 10.26.1.7.
It appears that asus has pulled this file and was wondering if anyone still has this file available somehow.
I soft-bricked my tablet and am not capable of flashing any other (earlier) firmware zip.
Any help would be greatly appreciated.
Yours sincerely,
Rens "Ikkerens" Rikkerink
Click to expand...
Click to collapse
Why can't you download an earlier firmware?

schmeggy929 said:
Why can't you download an earlier firmware?
Click to expand...
Click to collapse
I can, but it always ends up with some kind of error.
I basically tried following the steps you did:
schmeggy929 said:
i downloaded the asus firmware for 10.14.1.47. extract zip and you get a user.zip. extracted the boot.img. I fastboot erase boot, system, format system, data and cache(as you did)
fastboot -i 0x0B05 flash boot boot.img then
fastboot -i 0x0B05 flash system blob then
fastboot -i 0x0B05 flash system UL-K00C-US-10.14.1.47-user.zip
rebooted back into fastboot and bootloader showed 10.14.1.47 version.
Click to expand...
Click to collapse
But on when trying to flash the ***-user.zip, I get this error message:
Code:
$ fastboot -i 0x0B05 flash system UL-K00C-WW-10.14.1.47-user.zip
target reported max download size of 643825664 bytes
Invalid sparse file format at header magi
Edit: My bootloader version shows: WW_epad-10.26.1.7-20131108

Ikkerens said:
I can, but it always ends up with some kind of error.
I basically tried following the steps you did:
But on when trying to flash the ***-user.zip, I get this error message:
Code:
$ fastboot -i 0x0B05 flash system UL-K00C-WW-10.14.1.47-user.zip
target reported max download size of 643825664 bytes
Invalid sparse file format at header magi
Edit: My bootloader version shows: WW_epad-10.26.1.7-20131108
Click to expand...
Click to collapse
you are going to get that along with a few more errors. Wait until it is done. It will take like 10 mins and finish.
when it is done reboot in bootloader and you should see the version change.

schmeggy929 said:
you are going to get that along with a few more errors. Wait until it is done. I will take like 10 mins and finish.
Click to expand...
Click to collapse
You're getting this wrong, it does not do anything. The process immediately quits.

Ikkerens said:
You're getting this wrong, it does not do anything. The process immediately quits.
Click to expand...
Click to collapse
Ok when you get that message do you get a blinking curser?

Ikkerens said:
Hi there,
I've been searching around to find a specific firmware zip for my new tablet, the SKU: WW, Version: 10.26.1.7.
It appears that asus has pulled this file and was wondering if anyone still has this file available somehow.
I soft-bricked my tablet and am not capable of flashing any other (earlier) firmware zip.
Any help would be greatly appreciated.
Yours sincerely,
Rens "Ikkerens" Rikkerink
Click to expand...
Click to collapse
did you make any backup with cwm recovery?
try this:
unpack blob from 47 update
Code:
fastboot flash staging blob
fastboot flash recovery recovery.img
fastboot reboot-bootloader
load recovery, restore your backup
if you have not made any backup with cwm recovery, tell me.
btw fastboot flash system... is not needed here

lpdunwell said:
did you make any backup with cwm recovery?
try this:
unpack blob from 47 update
Code:
fastboot flash staging blob
fastboot flash recovery recovery.img
fastboot reboot-bootloader
load recovery, restore your backup
if you have not made any backup with cwm recovery, tell me.
btw fastboot flash system... is not needed here
Click to expand...
Click to collapse
I have not made a backup using cwm because there was no CWM available for my version.
My tablet was already updated to 4.3 and I (apparently) could not boot the cwm in the development section.
If I would be able to flash a usable recovery, I wouldn't be in this situation anyway as the asus update (.47) is flashable (found an updater-script in the zip).

Ikkerens said:
I have not made a backup using cwm because there was no CWM available for my version.
My tablet was already updated to 4.3 and I (apparently) could not boot the cwm in the development section.
If I would be able to flash a usable recovery, I wouldn't be in this situation anyway as the asus update (.47) is flashable (found an updater-script in the zip).
Click to expand...
Click to collapse
forget what I wrote here. I opened a thread with unbricking instructions. Good luck

lpdunwell said:
forget what I wrote here. I opened a thread with unbricking instructions. Good luck
Click to expand...
Click to collapse
Won't do me any good at the moment, I already managed to brick it even further (couldn't even get into fastboot mode anymore), so I RMA'd it.

Ikkerens said:
Won't do me any good at the moment, I already managed to brick it even further (couldn't even get into fastboot mode anymore), so I RMA'd it.
Click to expand...
Click to collapse
oh crap. sorry about that. I know there's the nvflash, too, but I have no idea how to use that so far...
would you mind telling what exactly happened?

lpdunwell said:
oh crap. sorry about that. I know there's the nvflash, too, but I have no idea how to use that so far...
would you mind telling what exactly happened?
Click to expand...
Click to collapse
Nvflash is inaccessible at the moment, it requires some preparation (you have to prepare it BEFORE you brick it)
Anyway, basically, I bought the tablet a few hours earlier.
Wanted to root it to remove some bloatware and restore some titanium backup thingies.
So I unlocked, rooted, basic stuff.
Went into TB, removed bloatware such as Amazon Kindle and some other irrelevant titles.
That action however, somehow caused it to be unbootable.
So I went into some basic repair stuff, as usual.
Tried to flash a recovery, only to find out, there is no working recovery. Only CWM, which required an earlier version of my bootloader.
So, what next. Restore stock? Downloaded the firmware, found out it was the earlier version of my device, because Asus removed the 4.3-EU version from their website.
So, I downloaded the .47-EU version, opened it. Saw there were no images, merely plain files meant for /system and an updater-script.
I ended up attempting to package my own system.img after that. Created an ext4 image on my computer, moved the files there. Followed the instructions in updater-script, which were mostly symlinks and stuff.
In the end of the updater-script they flashed blob to /staging and boot.img to /boot.
So, I flashed my custom system.img to /system.
Flashed boot
Flashed the blob
And beyond that point, I ended up in a bootloop of my bootloader. I could not hold down volume to enter fastboot or anything. All I could do was watch the asus logo as it constantly rebooted. (And ofcourse, no way to turn it off other than waiting for the battery to die)

Ikkerens said:
Nvflash is inaccessible at the moment, it requires some preparation (you have to prepare it BEFORE you brick it)
Anyway, basically, I bought the tablet a few hours earlier.
Wanted to root it to remove some bloatware and restore some titanium backup thingies.
So I unlocked, rooted, basic stuff.
Went into TB, removed bloatware such as Amazon Kindle and some other irrelevant titles.
That action however, somehow caused it to be unbootable.
So I went into some basic repair stuff, as usual.
Tried to flash a recovery, only to find out, there is no working recovery. Only CWM, which required an earlier version of my bootloader.
So, what next. Restore stock? Downloaded the firmware, found out it was the earlier version of my device, because Asus removed the 4.3-EU version from their website.
So, I downloaded the .47-EU version, opened it. Saw there were no images, merely plain files meant for /system and an updater-script.
I ended up attempting to package my own system.img after that. Created an ext4 image on my computer, moved the files there. Followed the instructions in updater-script, which were mostly symlinks and stuff.
In the end of the updater-script they flashed blob to /staging and boot.img to /boot.
So, I flashed my custom system.img to /system.
Flashed boot
Flashed the blob
And beyond that point, I ended up in a bootloop of my bootloader. I could not hold down volume to enter fastboot or anything. All I could do was watch the asus logo as it constantly rebooted. (And ofcourse, no way to turn it off other than waiting for the battery to die)
Click to expand...
Click to collapse
Since you are unlocked, you can try to flash the recovery (extract it first) of the US version 1.7, should be the same as wwe. Or just even try to flash the whole us update manually. And later change back to the wwe version when it comes available. The 47 update was only a minor ota for 4.2 so no image of recovery or bootloader there.

Sad story. What would have been the safe thing to do, if others wish to root their devices?

Snah001 said:
Since you are unlocked, you can try to flash the recovery (extract it first) of the US version 1.7, should be the same as wwe. Or just even try to flash the whole us update manually. And later change back to the wwe version when it comes available. The 47 update was only a minor ota for 4.2 so no image of recovery or bootloader there.
Click to expand...
Click to collapse
I still had the original recovery flashed, I never overwrote it actually. I needed a custom recovery (such as CWM, TWRP).
Flashing an US update is not possible alltogether, there are some minor differences with hardware compitability and such.
Problem is, I could've downloaded the .47 update, but I had already updated to 4.3 (BL 10.26.1.7)

Ikkerens said:
I still had the original recovery flashed, I never overwrote it actually. I needed a custom recovery (such as CWM, TWRP).
Flashing an US update is not possible alltogether, there are some minor differences with hardware compitability and such.
Problem is, I could've downloaded the .47 update, but I had already updated to 4.3 (BL 10.26.1.7)
Click to expand...
Click to collapse
I don't know if it isn't possible. On the TF700 it was only a line in the build.prop file that made the difference.
I would try it because now you have nothing and when it works you have the us version yes, but at least it works.

pelago said:
Sad story. What would have been the safe thing to do, if others wish to root their devices?
Click to expand...
Click to collapse
This guide worked fine for me; http://forum.xda-developers.com/showthread.php?t=2516215
It's only about what you do with the root ^^
Snah001 said:
I don't know if it isn't possible. On the TF700 it was only a line in the build.prop file that made the difference.
I would try it because now you have nothing and when it works you have the us version yes, but at least it works.
Click to expand...
Click to collapse
Already too late, it has been RMA'd, and then, I had nothing to flash it with.

Ikkerens said:
This guide worked fine for me; http://forum.xda-developers.com/showthread.php?t=2516215
It's only about what you do with the root ^^
Click to expand...
Click to collapse
Well I meant, what should a root user do to try and protect themselves against bricking their device like you did? Is it a matter of making sure that CWM or TWRP is on the device as a recovery partition? And are those available on TF701T yet?

Oh dear. That's a lot gone wrong.
Cwm is available and that works.
It's made by drgravy. I use it in my unbrick tut.
All i can say is, root --> cwm --> backup.
Sent from my GT-I9505 using xda app-developers app

That CWM wouldn't boot for me :/

[bounty] Requesting root + twrp for US version moto z3 play

$50 available via the crypto currency of YOUR choice.
Request: root. Tethered root is ok. Magisk systemless safteynet passing persistent root via zip flashing using persistent twrp is preferred, naturally.
This phone is AMAZING. Also the one sold from motorola.com is bootloader unlockable. The Amazon one is not.
To verify: if you got your z3 play from carrier or Amazon it is not bootloader unlockable.
If you bought from Motorola.com it is bootloader unlockable.
Battery without Moto mod is the best I have ever seen. Screen is amazing. Microsd slot, this is a really good feature. This is what my s9 plus should have been. No bloatware. I only want root for systemwide adblocking. (Adguard systemstore certificate)
With the Moto battery mod you can't run out of battery in a day. It's the best. Hopefully we will get unofficial custom rom someday so I can use Xposed and microg. You would be surprised how much telemetry even "stock like" roms have.

tomkleeeb said:
$50 available via the crypto currency of YOUR choice.
Request: root. Tethered root is ok. Magisk systemless safteynet passing persistent root via zip flashing using persistent twrp is preferred, naturally.
Click to expand...
Click to collapse
An attempt was already made. Using the firmware image someone linked here, I attempted to build and flash a TWRP for the Z3 Play I bought from Best Buy.
The result was a hard brick. Device would no longer power on. (Never seen this before, so it was definitely worth documenting for the TWRP chat)
Got a replacement Z3 Play, rebuilt TWRP but booted the firmware. Hard hang. Tried booting just the boot.img from the firmware image... also a hard hang.
So the software that we have now is not compatible with the Z3 Play.
Root and TWRP will come easily once we have an official image for the phone. It's unlocked, that's usually the hard part. Just gotta wait for Motorola to release the files or source first.

twelfth said:
An attempt was already made. Using the firmware image someone linked here, I attempted to build and flash a TWRP for the Z3 Play I bought from Best Buy.
The result was a hard brick. Device would no longer power on. (Never seen this before, so it was definitely worth documenting for the TWRP chat)
Got a replacement Z3 Play, rebuilt TWRP but booted the firmware. Hard hang. Tried booting just the boot.img from the firmware image... also a hard hang.
So the software that we have now is not compatible with the Z3 Play.
Root and TWRP will come easily once we have an official image for the phone. It's unlocked, that's usually the hard part. Just gotta wait for Motorola to release the files or source first.
Click to expand...
Click to collapse
Can you dump boot.img from the same devise, then fastboot boot boot.img?
If that works...
Could you then use magisk to add systemlessly root to the boot image
Then fastboot boot patched boot.img for tethered root?
This thread shows dumping partitions
https://forum.xda-developers.com/showthread.php?t=2450045

tomkleeeb said:
Can you dump boot.img from the same devise, then fastboot boot boot.img?
Click to expand...
Click to collapse
Not without root.
tomkleeeb said:
This thread shows dumping partitions
https://forum.xda-developers.com/showthread.php?t=2450045
Click to expand...
Click to collapse
Also from that thread:
TheThread said:
Pr-requirement:
- Rooted device.
Click to expand...
Click to collapse
You need root to get boot.img from a device to build TWRP.
or.
You need firmware images to be released by Motorola to build TWRP with the boot.img they release.
or.
You need source.
No way around it.

twelfth said:
You need source.
No way around it.
Click to expand...
Click to collapse
I made a thread on their official forums. https://forums.lenovo.com/t5/Moto-Z...this-phone-D/m-p/4176309/highlight/false#M200
This may seed things along.

if you boot into bootloader and run fastboot getvar all you'll see that our firmware is based on LA.UM.6.2.r1-07200-sdm660.0
so this should be our (incomplete) kernel source
https://source.codeaurora.org/quic/la/kernel/msm-4.4/tag/?h=LA.UM.6.2.r1-07200-sdm660.0
search for LA.UM.6.2.r1 on https://wiki.codeaurora.org/xwiki/bin/QAEP/release and you'll see all the updates we're missing since march

frantisheq said:
if you boot into bootloader and run fastboot getvar all you'll see that our firmware is based on LA.UM.6.2.r1-07200-sdm660.0
so this should be our (incomplete) kernel source
https://source.codeaurora.org/quic/la/kernel/msm-4.4/tag/?h=LA.UM.6.2.r1-07200-sdm660.0
search for LA.UM.6.2.r1 on https://wiki.codeaurora.org/xwiki/bin/QAEP/release and you'll see all the updates we're missing since march
Click to expand...
Click to collapse
I posted on GitHub asking for source.
Anyone wanna bump it?
https://github.com/MotorolaMobilityLLC/kernel-msm/issues/165

i have patched boot.img for 1929-8 using magisk manager apk from magisk 16.7.
not tested, i have locked bootloader.
if you have unlocked bootloader you can try "fastboot boot patched_boot.img" first without flash to see if it even boots. if it does you can try to flash it, extract magisk 16.7 zip and install apk from common folder.
https://drive.google.com/open?id=1n7Wf8ekChsDIUFmya0yFIRFQ581EIQxZ
if you brick your device you're on your own.
also i have sent boot.img to TWRP Builder, hopefully guys there can make a port from it.

frantisheq said:
i have patched boot.img for 1929-8 using magisk manager apk from magisk 16.7.
not tested, i have locked bootloader.
if you have unlocked bootloader you can try "fastboot boot patched_boot.img" first without flash to see if it even boots. if it does you can try to flash it, extract magisk 16.7 zip and install apk from common folder.
https://drive.google.com/open?id=1n7Wf8ekChsDIUFmya0yFIRFQ581EIQxZ
if you brick your device you're on your own.
also i have sent boot.img to TWRP Builder, hopefully guys there can make a port from it.
Click to expand...
Click to collapse
I have 1929-4 and unlocked the bootloader, tried it all, it's useless. (I used the boot of course from my version) Also I tried to port twrp but beyond the splash screen with the inscription twrp it did not work, and my knowledge in programming is almost equal to 0.

thought so. stock boot.img should boot with locked bootloader and it didn't.
ok i'll try to capture OTA url when it's available.

And yet I managed to get the root of the right through the magic and actually boot it. It was necessary in the magic to choose options for patch boot as far as I remember with encryption related, and it worked out))

frantisheq said:
thought so. stock boot.img should boot with locked bootloader and it didn't.
ok i'll try to capture OTA url when it's available.
Click to expand...
Click to collapse
Moto asked what version I need.... What version do we need to build root? https://github.com/MotorolaMobilityLLC/kernel-msm/issues/165

this looks looks like a bad joke. we don't even need to ask them, there's GPL

frantisheq said:
this looks looks like a bad joke. we don't even need to ask them, there's GPL
Click to expand...
Click to collapse
I don't know. I just want root.
I think they can get away with it because source is available upon request, but no one requests it. I am surprised their GitHub doesn't have 1000s of people clamoring for source code for root. This thing is on my short list of phones. Op6/6T would be my next choice but I like microsd more than I like root friendly warrenty.

tomkleeeb said:
I don't know. I just want root.
I think they can get away with it because source is available upon request, but no one requests it. I am surprised their GitHub doesn't have 1000s of people clamoring for source code for root. This thing is on my short list of phones. Op6/6T would be my next choice but I like microsd more than I like root friendly warrenty.
Click to expand...
Click to collapse
Try to boot from my boot (fastboot boot root.boot.img) and if the system boots,you will see in the manager of magics that you already have the root rights, then you can safely flash this boot to yourself (fastboot flash boot root.boot.img) and it will be your root. But twrp recovery I can not yet port unfortunately.(And of course you need to have a bootloader unlocked)
https://drive.google.com/file/d/1wwD4J3DN4sYqfD1hOe0uApHC9tgqKIfu/view?usp=drivesdk

Willy33 said:
Try to boot from my boot (fastboot boot root.boot.img) and if the system boots,you will see in the manager of magics that you already have the root rights, then you can safely flash this boot to yourself (fastboot flash boot root.boot.img) and it will be your root. But twrp recovery I can not yet port unfortunately.(And of course you need to have a bootloader unlocked)
https://drive.google.com/file/d/1wwD4J3DN4sYqfD1hOe0uApHC9tgqKIfu/view?usp=drivesdk
Click to expand...
Click to collapse
Have to buy the phone first lol.
No root = no buy
I just like the idea of the ga!epad controller mod $79.99
Android has no good game controller

kernel source should be released by tuesday
https://github.com/MotorolaMobilityLLC/kernel-msm/issues/165#issuecomment-415027775

i have paid to download firmware for XT1929-8 and unlocked the bootloader.
the bad news, boot.img patched with Magisk won't boot, it just reboots.
the good news, stock boot.img worked so my phone works.
the best news, treble ResurrectionRemix system img for ARM64 a/b with gapps and su just booted up
https://forum.xda-developers.com/pr...pment/gsi-resurrection-remix-o-6-1-0-t3811299
i'm going to try pixel experience later
EDIT: sound works, dual sim works, wifi works, fingerprint works, navigation bar needs to be enabled in settings, battery moto mod seems to be not charging, unable to change display brightness
pixel experience won't boot (maybe it will, it's because i have downloaded a version instead of a/b). i'm back to stock ROM
EDIT2: got root working.
not sure if it's needed but i have used Magisk Manager from https://raw.githubusercontent.com/ianmacd/MagiskBuilds/master/updates/ianmacd.json
installed the apk
set up that URL as custom Update Channel in Magisk manager settings
patched boot.img with "Preserve force encryption" and "Preserve AVB2.0/dm-verity" checked
patched boot.img for xt1929-8 can be downloaded here https://drive.google.com/open?id=11CJ65ojDZmCQVZGSHXicfFSMaenFHiiv
now where is that $50? my donation button still works
EDIT3: got boot.img with working TWRP, but it won't boot Android just TWRP.
if you'd like to try fastboot flash boot_a recovery.img and choose recovery in bootloader menu.
be sure to have boot.img backup before flashing because it won't boot Android and TWRP is unusable as it is, it can't even mount data.
https://drive.google.com/open?id=1C3lcyK3y4RL1Ep56wqWpfw0VWIHuhiO0

Absolutely all the same thing I did with my 1929-4 three days ago ... with twrp the same situation unfortunately ...

i was able to flash magisk and boot.img so it works. still don't know why it won't boot android.
device/motorola/beckham - https://drive.google.com/open?id=1KQ8KFthPJzr1VXt41F9N7O7fY8IRzcb6

[UNOFFICIAL] [RECOVERY] [OnePlus 6T] OrangeFox Recovery Project [R10.1]

[Deleted]

Is this confirmed working for the 6T? Just asking since I only see a IMG file and no installer. Also Orange Fox Recovery is commonly only used by Xiaomeme devices and has some MIUI Specific Features. Won't that interfere with out Devices?

How to install the recovery I followed the directions it won't boot into the recovery

Nice work! Looks cool

Just to clarify (thanks to Mauro for making us lazy with his installers ) I haven't ever installed an img on an A/B device so it seems obvious that we should choose "Install Recovery Ramdisk" as the target partition, However I'm unsure because I know there is not a dedicated recovery partition on our A/B device and I know this is not TWRP. So could "Boot" be the target partition? Isn't the recovery image integrated into the boot partition on these phones?

tswb said:
How to install the recovery I followed the directions it won't boot into the recovery
Click to expand...
Click to collapse
Updated instructions

Causical said:
Just to clarify (thanks to Mauro for making us lazy with his installers ) I haven't ever installed an img on an A/B device so it seems obvious that we should choose "Install Recovery Ramdisk" as the target partition, However I'm unsure because I know there is not a dedicated recovery partition on our A/B device and I know this is not TWRP. So could "Boot" be the target partition? Isn't the recovery image integrated into the boot partition on these phones?
Click to expand...
Click to collapse
You want to install recovery ramdisk.

Nice work there. Will try now

Spookybear said:
You want to install recovery ramdisk.
Click to expand...
Click to collapse
Your present instructions will lead to many post reporting bricked or non functional devices.
There is no recovery partition on our phone, only a boot one
If you fastboot flash the. img file it will overwrite the regular boot partition. You must perform a temporary boot by using fastboot boot twrp.img then install twrp, By either specifying clearly to 'install ramdisk recovery' either providing a regular zip installer file.
The other complication is that on some versions of OOS fastboot boot command is broken. So you must specify to have OOS 10.3.0 or eventually a custom ROM ?

Install via the "Recovery Ramdisk" Option doesn't work AT ALL! I just soft-bricked my phone twice now.

The opening post makes me think that Dev doesn't own a OP6T
I think this thread should be paused until actually working instructions are defined.....

Striatum_bdr said:
The opening post makes me think that Dev doesn't own a OP6T
I think this thread should be paused until actually working instructions are defined.....
Click to expand...
Click to collapse
don't know, kinda weird. I've never had issues flashing anything on my 6T up to now. Recovery Ramdisk in recovery for sure doesn't work. I'm about to try and just boot it, but those fastboot commands in the OP don't make sense at all.
---------- Post added at 09:46 AM ---------- Previous post was at 09:40 AM ----------
Causical said:
don't know, kinda weird. I've never had issues flashing anything on my 6T up to now. Recovery Ramdisk in recovery for sure doesn't work. I'm about to try and just boot it, but those fastboot commands in the OP don't make sense at all.
Click to expand...
Click to collapse
Okay I've just undoubtedly confirmed that this recovery.img does not even 'fastboot boot'...at least as far as OOS 10.3.1 is concerned. So I advise against use unless you're prepared to hook up to your PC and use fastboot to restore your boot partition.

Hi there, i'm not a developer or anything. But I can't figure this recovery out, i tried it on 10.3.0 and 9.0.17 and it wouldn't work. I tried everything: fastboot boot, fastboot flash boot and install on recovery ram disk. I also tried booting it with from a full wiped op6t, i'm pretty sure this .img doesn't work. I due hope that this recovery is coming to op6t. it's bin a long time since there's bin a new good working recovery. I'm looking forward to it dev!

This does not work for OP6T as of right now. I use Orange Fox recovery on my Redmi Note 7 so I'm familiar with installing it but instructions and/or the way this img is built is incorrect.

Do not try this recovery, for now, it doesn't work, period.
Wait for dev's update, he has been asked by xda to look into this

the recovery img doesnt work and the directions suck i dont understand

tswb said:
the recovery img doesnt work and the directions suck i dont understand
Click to expand...
Click to collapse
Spookybear got the links for dumpling and fajita mixed. The correct files for OnePlus 6T are in the OnePlus 5T thread.
https://forum.xda-developers.com/on...nofficial-orangefox-recovery-project-t4041781

Do not flash these. he put dumpling under fajita and fajita under dumpling. Wait for him to fix this.
Edit: the zip will protect you, the .img will not. Meaning the zip will error

So now this is very confusing... The original img file was labeled Fajita and it was not the correct one and now the OP's been updated to show Dumpling files and the Fajita labeled files are in another thread.
So which is it? Are the Dumpling named files misnamed Fajita files? Or are the Dumpling files actually Dumpling files?

apophis9283 said:
Do not flash these. he put dumpling under fajita and fajita under dumpling. Wait for him to fix this.
Edit: the zip will protect you, the .img will not. Meaning the zip will error
Click to expand...
Click to collapse
So you mean that the correct files we need to flash are the Dumpling ones. But we can only flash the image because the ZIP won't work as it's checking for Dumpling?

Nokia 4.2 Bricked, but can still enter FastBoot

Hello everyone :laugh:!
Tried rooting the Nokia 4.2, did not know which img to use exactly so I tried one from some other shady site and messed up. Luckily, the recovery partition was still working. After trying to boot lots of images, I got tired and accidentally even flashed a Nokia 6.2 TWRP image to my recovery partition. Then I completely messed up. The phone only gets into fastboot now. May I please ask some help of you? I've been trying for days to fix things. I just wanted to root the original firmware. Now when I try to flash TWRP, it even says that the 'recovery' partition has no partition table! I can still write to boot_a and boot_b though. The phone originally had the October patch level, but before bricking it I upgraded it to the December level.
Kind regards,
Alexander47u

Search on google and try do download and flash the stock firmware (unrooted)

Phone does not get detected by QFIL
thegamingcat13 said:
Search on google and try do download and flash the stock firmware (unrooted)
Click to expand...
Click to collapse
I have tried this using QFIL, however the phone is not detected. The phone also goes into fastboot as soon as the cable is plugged in, even when the phone is off.
Have also installed appropiate drivers for QFIL, but no luck.

Extract the system, boot, dtbo, vbmeta and vendor img's from the downloaded archieve and flash those using fastboot

Works, Thank you!
thegamingcat13 said:
Extract the system, boot, dtbo, vbmeta and vendor img's from the downloaded archieve and flash those using fastboot
Click to expand...
Click to collapse
Thank you! This worked flawlessly.

#metoo
Haha, I have done the EXACT same thing as you. Now I can only enter fastboot mode and when I try to flash anything I have downloaded I get an error about missing partitions. I have looked everywhere for details on the partition sizes, mount points and so on but nobody has uploaded the information. In the end I went and purchased a second device in order to dump the entire stock ROM in order to fix the first phone. I've got the second phone running in ADB-mode but I can only backup to an .ab file so now I am back at square one. All of the guides I can find on how to dump the ROM involves flashing TWRP recovery but THERE IS NONE FOR THE 4.2 :crying: And after researching Android forensics I have found a guide to dumping the ROM but it needs root access in the phone shell. All I wanted was root (and LineageOS). Does anyone feel like patching the stock ROM and making a zip-file containing the img-files from all of the partitions?

Hi. You need to check which slot is in use, A or B. You can also choose slot A or B with fastboot. Then you flash the images to the partitions by appending _a or _b to the partition name.
E.g.
fastboot --set-active=a
fastboot flash boot_a boot.img
Etc.
You also need to make sure you have a recent version of fastboot, as the fastboot in some Linux package managers or blog posts for Windows give you the older one, which does not support changing active slots.
Inside the stock rom that can be found online, there is another archive containing the needed images.

alexander47u said:
Hi. You need to check which slot is in use, A or B. You can also choose slot A or B with fastboot. Then you flash the images to the partitions by appending _a or _b to the partition name.
E.g.
fastboot --set-active=a
fastboot flash boot_a boot.img
Etc.
You also need to make sure you have a recent version of fastboot, as the fastboot in some Linux package managers or blog posts for Windows give you the older one, which does not support changing active slots.
Inside the stock rom that can be found online, there is another archive containing the needed images.
Click to expand...
Click to collapse
Thanks for the tip! Looks like I solved it earlier, I found a "user_update" zip in one of the downloaded ROMs and used fastboot update user_update.zip. Wuhu! I did not specify the slot but the system boots up. On the first boot I got an error message asking me to restore factory settings which seemed to work. Now all I need to do is get root access... Alexander, did you manage to flash a rooted recovery now? Thanks in advance!

You need to put the stock boot.img unaltered on a sdcard or the internal storage and then run the Magisk android app. It will offer an option to patch the boot.img. Then you can place the patched boot.img back on your computer and flash it using fastboot.

alexander47u said:
You need to put the stock boot.img unaltered on a sdcard or the internal storage and then run the Magisk android app. It will offer an option to patch the boot.img. Then you can place the patched boot.img back on your computer and flash it using fastboot.
Click to expand...
Click to collapse
I was able to succesfully patch boot.img with magisk, then I copied the patched boot image to my computer with linux. Fastboot flash boot boot.img worked but upon reboot I got an error message saying "corrupt data" and offered to do a factory reset. Any chance you can upload your patched boot image so I can use yours?

Magisk boot.img patched.
http://s000.tinyupload.com/index.php?file_id=49342816027254664129

Posted

alexander47u said:
Magisk boot.img patched.
http://s000.tinyupload.com/index.php?file_id=49342816027254664129
Click to expand...
Click to collapse
You legend! Thank you. Now to see if I can get it to work... what security patch is this up to?

Oslokalle said:
You legend! Thank you. Now to see if I can get it to work... what security patch is this up to?
Click to expand...
Click to collapse
Up to March. I used the stock rom that is floating around on the internet. Not sure if I am allowed to post stock roms.
I was able to update to April using Magisk but not any further than that.

thegamingcat13 said:
Extract the system, boot, dtbo, vbmeta and vendor img's from the downloaded archieve and flash those using fastboot
Click to expand...
Click to collapse
Tried this using a user_update.zip file from www[.]getdroidtips[.]com/stock-rom-nokia-4-2-firmware/. My phone boots again, but Wi-Fi doesn't work. My model # is TA-1133. What should I do?
Edit: tried to install the latest security OTA from t[.]me/nokiarepoen/379, V2.29C, but I get
Code:
E:Package is for source build 00WW_2_29B but expected 00WW_1_17I
. Is there a base user_update for build 00WW_2_29B floating around?

Oslokalle said:
Thanks for the tip! Looks like I solved it earlier, I found a "user_update" zip in one of the downloaded ROMs and used fastboot update user_update.zip. Wuhu! I did not specify the slot but the system boots up. On the first boot I got an error message asking me to restore factory settings which seemed to work. Now all I need to do is get root access... Alexander, did you manage to flash a rooted recovery now? Thanks in advance!
Click to expand...
Click to collapse
Kindly provide me that zip too.

Question root failed and bootloop

I got a china version OnePlus 10 Pro
i was flashed in oxygen OS A12 EU
I extract the boot.img (52M) from payload.bin today and use magisk cancy to patch
and then i try to fastboot flash boot boot_patched.img
and now start bootloop on one plus splash screen
I can still go to fastboot and fastbootD , I can still flash the payload again but still bootloop
anyone have idea what can i fo to fix ? thanks

leofung_wai said:
I got a china version OnePlus 10 Pro
i was flashed in oxygen OS A12 EU
I extract the boot.img (52M) from payload.bin today and use magisk cancy to patch
and then i try to fastboot flash boot boot_patched.img
and now start bootloop on one plus splash screen
I can still go to fastboot and fastbootD , I can still flash the payload again but still bootloop
anyone have idea what can i fo to fix ? thanks
Click to expand...
Click to collapse
Hey,
If you've only booted the image, then you only need to reboot and the image is lost, the only way that it would be permanent is if it was flashed: fastboot flash not: fastboot boot.
Usually what happens is when you obtain a firmware to install or in your case change region, and you wish to root this firmware you would extract payload.bin then use fastboot enhance to extract the boot.img
Then copy to your phone and patch it with the latest stable Magisk (in this case 24.3)
So again, if you've only booted the image then just reboot your phone and it'll turn on using the actual flashed boot.img from the firmware, not the one you booted.
If that doesn't work then you must have flashed it. In which case you can either re-flash your original boot.img or boot then direct install a correctly patched image for the correct firmware (after a success boot) via Magisk.

leofung_wai said:
I got a china version OnePlus 10 Pro
i was flashed in oxygen OS A12 EU
I extract the boot.img (52M) from payload.bin today and use magisk cancy to patch
and then i try to fastboot flash boot boot_patched.img
and now start bootloop on one plus splash screen
I can still go to fastboot and fastbootD , I can still flash the payload again but still bootloop
anyone have idea what can i fo to fix ? thanks
Click to expand...
Click to collapse
Here's a good "how to" to follow.
https://www.droidwin.com/how-to-root-oneplus-10-pro-via-magisk-patched-boot-img/

Canuck Knarf said:
Here's a good how to to follow.
https://www.droidwin.com/how-to-root-oneplus-10-pro-via-magisk-patched-boot-img/
Click to expand...
Click to collapse
No he has changed region. This is for color OS...he's already done all this.
If you read the OP, he's already on EU 11_A.12
This would just make matters much worse

dladz said:
No he has changed region. This is for color OS...he's already done all this.
If you read the OP, he's already on EU 11_A.12
This would just make matters much worse
Click to expand...
Click to collapse
what you talking about ...it applies to all ...if hes on colors os....oxgyen os..he stills needs ...boot img...vender_boot...and vbmeta. img and magisk

Canuck Knarf said:
what you talking about ...it applies to all ...if hes on colors os....oxgyen os..he stills needs ...boot img...vender_boot...and vbmeta. img and magisk
Click to expand...
Click to collapse
Are you suggesting that the boot.img in color OS is the same as it is in OOS?
You're mistaken if you do think that
They're completely different operating systems, have different system.img's boot.img's, in fact most if not all images are different, to suggest he should obtain a firmware that he's just changed FROM is a bad suggestion..
That's what I'm talking about.
As per the OP, he has changed region, he is no longer using color OS ( the site you suggested is referring to this firmware)
He is now on oxygen OS using the firmware EU 11_A.12
If he was to attempt to use a color OS boot image his phone would continue to be in a boot loop but for a different reason.
Again, this would make things much much worse.
If what he's advised is true then he's successfully changed OS/region and now wants to root, the only thing he's done thus far is to boot a boot image. I think he's flashed it as booting is not permanent, to suggest to go ahead and attempt to obtain a color OS boot image or vendor image is absolutely ridiculous.
He's on an EU firmware. So he requires an EU boot image.

He's in boot loop cause he is booting to A slot...

Thanks for everyone's reply i did change the boot to A and reflash everyone again it can boot now but when i try to root again , it stuck into fastboot mode

dladz said:
Are you suggesting that the boot.img in color OS is the same as it is in OOS?
You're mistaken if you do think that
They're completely different operating systems, have different system.img's boot.img's, in fact most if not all images are different, to suggest he should obtain a firmware that he's just changed FROM is a bad suggestion..
That's what I'm talking about.
As per the OP, he has changed region, he is no longer using color OS ( the site you suggested is referring to this firmware)
He is now on oxygen OS using the firmware EU 11_A.12
If he was to attempt to use a color OS boot image his phone would continue to be in a boot loop but for a different reason.
Again, this would make things much much worse.
Click to expand...
Click to collapse
oxygen OS using the firmware EU 11_A.12.... He still needs boot img ...vender_boot form the firmware EU 11_A.12 . to root

leofung_wai said:
Thanks for everyone's reply i did change the boot to A and reflash everyone again it can boot now but when i try to root again , it stuck into fastboot mode
Click to expand...
Click to collapse
you need to load the firmware EU 11_A.12 to b slot using fastboot enhance

He already had boot?? What are you talking about???
He had a functional OS, in order to root you only need ONE image.
The boot image which comes from OOS. The link you sent is for Color OS?? Make sense now ??
He just needs to patch it correctly and boot it then direct install.
Im going over this again with someone who's incapable of understanding the basics.

Canuck Knarf said:
you need to load the firmware EU 11_A.12 to b slot using fastboot enhance
Click to expand...
Click to collapse
You do realise that booting an image does not need to be directed don't you?
Only by flashing should you direct the image to a particular slot.
By flashing you are permanently flashing an image.
I don't think you understand this so I'll make it simple for you.
You want to root your phone. You have an image you've just patched, from boot.img to magisk_patched.img
Firstly you would want to send this via fastboot, you do not need fastboot enhance for this.
The preferred way to do this is to fastboot boot magisk_patched.img
Why is this preferred??
Because if it fails as it may. Then you are not stuck in a boot loop, you just reboot and you're back in the OS.
The 2nd method is flashing.
fastboot flash boot_a magisk_patched
Press enter.
fastboot flash boot_b magisk_patched
Press enter
fastboot reboot
Press enter.
Now although this can work it is not the preferred method because you aren't just booting the image you are flashing it, this means that if it fails you cannot just reboot and get back to the OS you have to either obtain a new boot image and patch it although you cannot do this yourself as your phone no longer boots or you obtain an already patched boot image, again the last one I wouldn't recommend..

Thanks again but i had a question , i tried to flash or boot a patched boot img , now i can boot and get into system...but still not root

leofung_wai said:
Thanks again but i had a question , i tried to flash or boot a patched boot img , now i can boot and get into system...but still not root
Click to expand...
Click to collapse
Ok so if you've got into the system..
You need to follow the instructions I have in my guide in order to get root...
You can use the boot image I have there.

leofung_wai said:
Thanks again but i had a question , i tried to flash or boot a patched boot img , now i can boot and get into system...but still not root
Click to expand...
Click to collapse
It is always better to patch boot.img of your own version (you can dump it from payload dumper etc.) and then only fastboot boot patched_image.img and then directly install it via Magisk.

Boot this image.
192 MB folder on MEGA
mega.nz

Yes i did dump from my own and patched by magisk cancy , but it still ...get in normally

Do not flash it.
If your phone boots to the OS, then open Magisk and click install. Direct install and you're done

leofung_wai said:
Yes i did dump from my own and patched by magisk cancy , but it still ...get in normally
Click to expand...
Click to collapse
If you've patched your own image and booted it then click Magisk then install. Then direct install and you're done..

dladz said:
Do not flash it.
If your phone boots to the OS, then open Magisk and click install. Direct install and you're done
Click to expand...
Click to collapse
thanks i success root by your image now
but i had a question, i messed up the slot B and now can only boot through slot A Will it affect anything