Database Develop

Real Rom Install Issue Re. Trickdroid

I was talking about this problem over in the trickdroid thread, simply because it was trickdroid I was flashing but in fairness to that thread I don't want to clutter it with an endless amount of questions, repeating myself over and over, when people are simply there to review the rom/tweaks. I will give my issues in the correct order as best as I can remember, bottom line is I'm caught in a TWRP bootloop.
1) Picked up phone and unlocked bootloader and rooted via all-in-one toolkit. Confirmed root by downloading Titanium, so at this point I am stock rooted with zero issues.
2) Having installed latest TWRP at time of root I immiedietly backed up the stock rom, which I then copied to computer, so I do have this backed up and it's also visible (though unflashable) in TWRP under internal storage.
3) Flashed Trickdroid, which hung on 'install,' and I've since found out there is an issue with aroma installer. Tried 100 times (no exageration)since then to flash that rom and it gets to 30% installed and then reboots into TWRP. TWRP won't then let me do anything of substance. TWRP is also telling me I am now unrooted when I attempt to reboot into recovery from within twrp.The exact order is, flash rom - gets to 30% - reboots into a white screen (not recovery) that says HTC One, quietly brilliant, and then within 10 seconds it automatically reboots into TWRP.
4) On recomendation from rom developer, attempted to flash CWM via fastboot and it flashed fine, fastboot states the flash is sucessful but then when I reboot into recovery it's still TWRP. So CWM appears to have flashed but hasn't for some reason.
And that's where I am. Tried to flash CWM, tried to push rom to sd card, no luck.
Any ideas?

Try to flash without aroma... Replace the meta inf folder with the one linked in the op so it doesn't utilize aroma
Sent from my HTC One using Tapatalk 2

thesparky007 said:
Try to flash without aroma... Replace the meta inf folder with the one linked in the op so it doesn't utilize aroma
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Tried to do that yesterday and it wouldn't push. Trying again right now so I can give an exact error message.

What do u mean it wouldn't push?
Sent from my HTC One using Tapatalk 2

OK, I've followed the instructions and now have a zip ready to be pushed/flashed.
My question is, would you reccomend flashing it directly to device in fastboot or push to sd card and flash from there?

thesparky007 said:
What do u mean it wouldn't push?
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Kept getting errors whenever I tried to flash or push to sd card

When u extract the meta inf folder what all do u see in the root of that folder
Sent from my HTC One using Tapatalk 2

losangeles100 said:
I was talking about this problem over in the trickdroid thread, simply because it was trickdroid I was flashing but in fairness to that thread I don't want to clutter it with an endless amount of questions, repeating myself over and over, when people are simply there to review the rom/tweaks. I will give my issues in the correct order as best as I can remember, bottom line is I'm caught in a TWRP bootloop.
1) Picked up phone and unlocked bootloader and rooted via all-in-one toolkit. Confirmed root by downloading Titanium, so at this point I am stock rooted with zero issues.
2) Having installed latest TWRP at time of root I immiedietly backed up the stock rom, which I then copied to computer, so I do have this backed up and it's also visible (though unflashable) in TWRP under internal storage.
3) Flashed Trickdroid, which hung on 'install,' and I've since found out there is an issue with aroma installer. Tried 100 times (no exageration)since then to flash that rom and it gets to 30% installed and then reboots into TWRP. TWRP won't then let me do anything of substance. TWRP is also telling me I am now unrooted when I attempt to reboot into recovery from within twrp.The exact order is, flash rom - gets to 30% - reboots into a white screen (not recovery) that says HTC One, quietly brilliant, and then within 10 seconds it automatically reboots into TWRP.
4) On recomendation from rom developer, attempted to flash CWM via fastboot and it flashed fine, fastboot states the flash is sucessful but then when I reboot into recovery it's still TWRP. So CWM appears to have flashed but hasn't for some reason.
And that's where I am. Tried to flash CWM, tried to push rom to sd card, no luck.
Any ideas?
Click to expand...
Click to collapse
Okay LA. One quick and very basic question? You said you rooted the phone and you know because you downloaded and installed Titanium. Titanium does NOT need root for simple backups so that is no way to make sure you have root. To verify root, when you boot into bootloader/recovery, make sure it says "unlocked" and "tampered" at the top. I know it is basic but nothing will work without it. If it shows that, we can work from there. You should be able to just copy the file over to your SD card on the phone if your computer sees it.

frodoboy said:
Okay LA. One quick and very basic question? You said you rooted the phone and you know because you downloaded and installed Titanium. Titanium does NOT need root for simple backups so that is no way to make sure you have root. To verify root, when you boot into bootloader/recovery, make sure it says "unlocked" and "tampered" at the top. I know it is basic but nothing will work without it. If it shows that, we can work from there. You should be able to just copy the file over to your SD card on the phone if your computer sees it.
Click to expand...
Click to collapse
Good points, and yes, i'm unlocked and tampered. What I actually meant was TB stated 'rooted.'

thesparky007 said:
When u extract the meta inf folder what all do u see in the root of that folder
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
The new meta.inf now contains: com folder, CERT.RSA, CERT.SF, MANIFEST.MF

losangeles100 said:
The new meta.inf now contains: com folder, CERT.RSA, CERT.SF, MANIFEST.MF
Click to expand...
Click to collapse
Make sure it zips up properly and try again. If that doesn't flash try flashing the original zip
Sent from my HTC One using Tapatalk 2

Hey, Mike
We can take this here from PMs
Not sure on the zip you are trying to do, but would still try to get off twrp 2.5.0.0.
and fastboot the 2.3.3.0 twrp image i sent you. then try flashing rom after all wipes in recovery, not aroma. and make sure you fastboot the boot image from command window right after you flash rom. then erase cache then reboot to bootloader then reboot system. usually after first boot I reboot again wipe caches then reboot system--

losangeles100 said:
Good points, and yes, i'm unlocked and tampered. What I actually meant was TB stated 'rooted.'
Click to expand...
Click to collapse
I take it that letting the battery drain didn't help? Does ADB find the phone now? by the way, without S-OFF, it is almost impossible to brick your phone so we'll get there eventually!

Rug, firstly, thanks for going above and beyond, you're a credit to XDA and I for one really appreciate your help.
Now the weirdness: flashed the TWRP image you gave me and erased cache and rebooted into recovery and it's the original twrp. It definetly flashed correctly, said 'flashed' 'ok' so that is really weird. It simply isn't sticking. And just to clarify, fastboot sees the phone and everything went as it always has, except the end result.

frodoboy said:
I take it that letting the battery drain didn't help? Does ADB find the phone now? by the way, without S-OFF, it is almost impossible to brick your phone so we'll get there eventually!
Click to expand...
Click to collapse
Letting the battery drain is easier said than done on this bad boy
I'm down to 45% and not charging at all so as soon as I get to zero I will let you know. I'm actually starting to pin too much god damned hope on that! lol

Ok when you flashed CWM in the bootloader you complained that it still booted into TWRP, did you try flashing it again and then erasing cache while still in fastboot then booting into the recovery?

losangeles100 said:
Letting the battery drain is easier said than done on this bad boy
I'm down to 45% and not charging at all so as soon as I get to zero I will let you know. I'm actually starting to pin too much god damned hope on that! lol
Click to expand...
Click to collapse
boy this is a stumper! Can you reflash the original stock ROM and relock the bootloader and see if you go back to at least a working phone? Then you can unlock the bootloader again choosing CWM this time and then try to reflash TrickDroid? Also, do you have Superuser installed? I think you said you did. Just see if you can start over to at least recover your phone. Something went wrong with the initial steps to cause it to freeze up like that.

When flashng zip without aroma I get this error in cmd:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

bobruels44 said:
Ok when you flashed CWM in the bootloader you complained that it still booted into TWRP, did you try flashing it again and then erasing cache while still in fastboot then booting into the recovery?
Click to expand...
Click to collapse
I believe I did but you make a valid point.

frodoboy said:
boy this is a stumper! Can you reflash the original stock ROM and relock the bootloader and see if you go back to at least a working phone? Then you can unlock the bootloader again choosing CWM this time and then try to reflash TrickDroid? Also, do you have Superuser installed? I think you said you did. Just see if you can start over to at least recover your phone. Something went wrong with the initial steps to cause it to freeze up like that.
Click to expand...
Click to collapse
Superuser was installed but when I reboot into recovery I get a message from twrp saying 'you're not rooted, would you like to flash SU now.' When I swipe to flash it does nothing, although SU is on internal storage.
Just to add, the backup I made is visible in the TWRP folder in storage but cannot be accessed, and when I hit the restore button nothing is listed.
Regarding reflashing stock original, I'd pay 100 bucks to anyone in this thread who could get me back to stock.

[Q] Sideload 5.1 on nexus 6

I am currently on 5.0.1 and as you all probably all know, the OTA links for 5.1 are available. I am trying to sideload this OTA to my nexus 6. To do this I am using wugfresh's NRT and I have gotten as far as the stock recovery menu. My adb drivers are configured properly which is why I made it this far. Now that I am in stock recovery, NRT says that ADB Sideload device not found. I am not sure what to do from here becuase my phone is not recognized by the computer which means I cannot update any drivers if necessary. Can anyone please guide me from here?

I had the same problem and NRT walked me through the fix. You have to open the device menu on your PC and choose your N6, it will have a yellow triangle on it. Right click and choose update driver from a file on your PC. Then choose the ADB driver to update. Mine connected and sideload was successful after that.

Even after that it may still not recognize (at least for me it did) and a simple unplug and plug in worked fined
Sent from my Nexus 6 using XDA Free mobile app

A2CKilla said:
Even after that it may still not recognize (at least for me it did) and a simple unplug and plug in worked fined
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Ok, so I got it to flash, but then it aborts. It says
e: Footer is wrong
e: signature validation failed
Installation aborted

flamingtiger said:
Ok, so I got it to flash, but then it aborts. It says
e: Footer is wrong
e: signature validation failed
Installation aborted
Click to expand...
Click to collapse
I had the same issue, was able to get it to work using method #2 on this post.
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008

shadow321337 said:
I had the same issue, was able to get it to work using method #2 on this post.
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Click to expand...
Click to collapse
But wont that method completely wipe all data? I guess that is what I am going to have to do

flamingtiger said:
But wont that method completely wipe all data? I guess that is what I am going to have to do
Click to expand...
Click to collapse
Yeah, it will. That's what I had to do, too. Just keep in mind it will also wipe your /sdcard. So if you have any nandroid backups, etc back them up to your computer first. I was able to do that, then restore just the data portion of a 5.0.1 nandroid backup to the 5.1 ROM with no issues. An extra step but it kept my info.

flamingtiger said:
But wont that method completely wipe all data? I guess that is what I am going to have to do
Click to expand...
Click to collapse
You can manually flash the recovery, boot, and system through fastboot without wiping data. Then the adb sideload should work.

All I did was
1. flash stock recovery image from 5.0.1 (may be able to just use 5.1 now that the factory image is out)
2. flash stock system image (same as step 1)
3. sideload ota zip
4. profited!!!
Doing all this, my data was still in tact and this acted just like a regular ota
sub steps
5. add build.prop changes back for tethering
6.change dpi back to 480

ajjames01 said:
You can manually flash the recovery, boot, and system through fastboot without wiping data. Then the adb sideload should work.
Click to expand...
Click to collapse
so in NRT, I should just flash those specific ones and then press sideload update and go through the process again?

flamingtiger said:
so in NRT, I should just flash those specific ones and then press sideload update and go through the process again?
Click to expand...
Click to collapse
basically, unless you're doing it by hand with adb commands, under the advanced option in nrt, you'll see the manual flash buttons towards the middle I believe, your main focus is recovery and system if you want to keep your data

A2CKilla said:
All I did was
1. flash stock recovery image from 5.0.1 (may be able to just use 5.1 now that the factory image is out)
2. flash stock system image (same as step 1)
3. sideload ota zip
4. profited!!!
Doing all this, my data was still in tact and this acted just like a regular ota
sub steps
5. add build.prop changes back for tethering
6.change dpi back to 480
Click to expand...
Click to collapse
Just to make sure, I am supposed to exptract the zip that is found in the original zip that i downloaded from google right? Because NRT wont let me sideload the entire zip from google, so i extracted the one inside that zip and it let me go through. But i ended up with that error. What am i doing wrong?

flamingtiger said:
Just to make sure, I am supposed to exptract the zip that is found in the original zip that i downloaded from google right? Because NRT wont let me sideload the entire zip from google, so i extracted the one inside that zip and it let me go through. But i ended up with that error. What am i doing wrong?
Click to expand...
Click to collapse
you can see the directories, but yes, the factory image straight from google is where you get the .img files you need
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

A2CKilla said:
you can see the directories, but yes, the factory image straight from google is where you get the .img files you need
Click to expand...
Click to collapse
Thanks bruh, I finally got it to work and lost no data at all. I really appreciate all help and advice that yall gave.

flamingtiger said:
Just to make sure, I am supposed to exptract the zip that is found in the original zip that i downloaded from google right? Because NRT wont let me sideload the entire zip from google, so i extracted the one inside that zip and it let me go through. But i ended up with that error. What am i doing wrong?
Click to expand...
Click to collapse
flamingtiger said:
Thanks bruh, I finally got it to work and lost no data at all. I really appreciate all help and advice that yall gave.
Click to expand...
Click to collapse
A2CKilla said:
All I did was
1. flash stock recovery image from 5.0.1 (may be able to just use 5.1 now that the factory image is out)
2. flash stock system image (same as step 1)
3. sideload ota zip
4. profited!!!
Doing all this, my data was still in tact and this acted just like a regular ota
sub steps
5. add build.prop changes back for tethering
6.change dpi back to 480
Click to expand...
Click to collapse
I'm a noob and want to make sure I do this right, are these following steps correct? i am currently unencrypted, rooted on franco kernel on 5.0.1!
1) flash stock recovery image first
2) flash stock system image second
3) what's the OTA zip? is that within the .tgz file that i downloaded from google?
4) what's build.prop.. ?
5) what's dpi?
Sorry for the noob questions... just don't want to brick my nexus

I got you
wilson289 said:
I'm a noob and want to make sure I do this right, are these following steps correct? i am currently unencrypted, rooted on franco kernel on 5.0.1!
1) flash stock recovery image first
2) flash stock system image second
3) what's the OTA zip? is that within the .tgz file that i downloaded from google?
4) what's build.prop.. ?
5) what's dpi?
Sorry for the noob questions... just don't want to brick my nexus
Click to expand...
Click to collapse
Alright... This is what I did and it should probably work for you:
Because u are on Franco kernel, I recomend that you flash the stock boot.img for 5.01 before begenning
1. Download wugfresh's NRT: this tool is very helpful for all things rooting
2. Make sure fastboot and adb are configured properly
2. I originally downloaded the zip directly from google (900≈ mb)...and it did not work
So I searched on google "nexus 6 5.1 ota zip"... On any website... The Downoad should be around 410 mb - this zip worked for me and give me no errors at all. Do not extract or mess with that zip.
3. Go on the toolkit and launch the advanced options
4. Around the middle of the page, you will see sideload update
5. Go through the prompts and select the 410 mb zip that u downloaded.
This should flash and reboot you to android 5.1
This method will install stock recovery and remove root so afterword go ahead and reroot using the toolkit.
Don't flash anything before besides the original 5.01 stock boot.img. dont worry about DPI or anything: at least that's not what I did, and I got it to work perfectly
If any steps did not make sense or you are not sure what to do.. Don't be afraid to ask me or anyone

?
Although I am not sure about the stock boot.img, it might work with Franco kernel. Anyone else know? Sideload could work with Franco kernel.

Does XperiFIX work with 47.1.A.12.145 aka the April patch?

I want to unlock my bootloader and try a custom ROM, but I don't want to get stuck without a camera. I remember reading somewhere that XperiFIX would need to be updated for the most recent patch to be compatible.
Anyone tried it?

Pickx said:
I want to unlock my bootloader and try a custom ROM, but I don't want to get stuck without a camera. I remember reading somewhere that XperiFIX would need to be updated for the most recent patch to be compatible.
Anyone tried it?
Click to expand...
Click to collapse
Have you thought of asking in the Xperiafix thread ?

Didgesteve said:
Have you thought of asking in the Xperiafix thread ?
Click to expand...
Click to collapse
No, because nobody in that thread has answered that question for the March update either.

Pickx said:
No, because nobody in that thread has answered that question for the March update either.
Click to expand...
Click to collapse
Well if no one has answered then it's probably a no then

I patched XperiFix myself to use it with the .119 FW and it works.
Currently i'm running FW .119 with XperiFix DRM-patch and TWRP from 05.03.18.
I haven't installed the .145 FW atm, because I couldn't boot into Android with TWRP from 05.03.18.
But I read that TWRP came out for the april patch, so I will try to update at the weekend and check again with XperiFix.
Proof FW .119:
Phone Settings:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Phone Security Settings:
XperiFix:
Edit - After Upgrade .145:
I used the April TWRP and I could boot into Android and TWRP.
Phone Settings:
XperiFix:

Thank you very much! So what is the process like to do this with an "unsupported" firmware? How do I patch this for .145, or do I even need to do anything special other than using a newer version of TWRP?

Raz0Rfail said:
I patched XperiFix myself to use it with the .119 FW and it works.
Currently i'm running FW .119 with XperiFix DRM-patch and TWRP from 05.03.18.
[...]
Click to expand...
Click to collapse
Thank you very much! So what is the process like to do this with an "unsupported" firmware? How do I patch this for .145, or do I even need to do anything special other than using a newer version of TWRP?

Raz0Rfail said:
Edit - After Upgrade .145:
I used the April TWRP and I could boot into Android and TWRP.
Click to expand...
Click to collapse
Is upgrading the XperiFix just as simple as replacing the TWRP in the XperiFix folder with the most recent one? If not, what else is required? If so, what do I do with the xz1c-twrptemp.img file? I'm assuming I rename the downloaded TWRP file to xz1c-twrp.img.
It's mentioned at https://www.xperifix.com/2018/03/06/update-2-2-xz1-and-xz1-compact-update/#comment-40 that a guide for this will be released but I haven't found it yet, and given that it looks above like you've already done this I'd be most appreciative if you'd share the process. Thanks!

nataelj said:
Is upgrading the XperiFix just as simple as replacing the TWRP in the XperiFix folder with the most recent one? If not, what else is required? If so, what do I do with the xz1c-twrptemp.img file? I'm assuming I rename the downloaded TWRP file to xz1c-twrp.img.
It's mentioned at https://www.xperifix.com/2018/03/06/update-2-2-xz1-and-xz1-compact-update/#comment-40 that a guide for this will be released but I haven't found it yet, and given that it looks above like you've already done this I'd be most appreciative if you'd share the process. Thanks!
Click to expand...
Click to collapse
I wrote you a pm to modify xperifix.
You need only the current kernel for the fw installed. It comes with flashing firmware.
The temp TWRP inside the data folder is only get booted from the XperiFix tool.
The XperiFix tool boot this temp TWRP to change the libs, install magisk and so on.
If you change the TWRP temp through another TWRP image, all commands to flash magisk etc. Won't work, so for the work is the temp TWRP required.
Important is that you use the correct kernel before you use xperifix, because this kernel get flashed and TWRP temp got booted as recovery, so nothing changes what you have currently installed as boot or recovery image.
So the second TWRP I let It as it be. After flashing the XperiFix files and the phone restart correctly, I boot into bootloader and flash the new TWRP recovery and then I reboot into TWRP to check if all files shown in /sdcard are correctly named. If the names are correct, you use the right TWRP to the installed security patch from Google. If you have only cryptic names inside /sdcard you have the wrong TWRP to the installed security patch. If it's so that the wrong TWRP is installed download the correct one and flash the recovery again.
Edit: sorry I forget I wrote am pm to pickxx.
I send it to you too.
I can't post it here, because it's not save and if the owner find out, he would fix it, that patching is not possible.

Raz0Rfail said:
I wrote you a pm to modify xperifix.
I can't post it here, because it's not save and if the owner find out, he would fix it, that patching is not possible.
Click to expand...
Click to collapse
I still haven't gotten a PM.
Also, the link I posted above was one to the creator of Xperifix (@sToRm// (Heiko Frenzel) on this forum) mentioning that he was going to publish a guide on how to do this update on the XperiFIX website, so I think you'd probably be fine to publish that yourself. Far from causing him to fix it, I think you'd just save him some work. If anyone knows otherwise please feel free to correct me.
Finally, the above discussion is helpful in clarifying what to do (or not to do) with the temp, but I'm still not sure what I need to replace or update in the XperiFIX to enable it to work on the most recent firmware.

nataelj said:
I still haven't gotten a PM.
Also, the link I posted above was one to the creator of Xperifix (@sToRm// (Heiko Frenzel) on this forum) mentioning that he was going to publish a guide on how to do this update on the XperiFIX website, so I think you'd probably be fine to publish that yourself. Far from causing him to fix it, I think you'd just save him some work. If anyone knows otherwise please feel free to correct me.
Finally, the above discussion is helpful in clarifying what to do (or not to do) with the temp, but I'm still not sure what I need to replace or update in the XperiFIX to enable it to work on the most recent firmware.
Click to expand...
Click to collapse
I couldn't share the PM, because my PM settings wasn't configured to save it in send mails.
I will write a Tutorial after my work 19:00 (UTC +1), how to patch XperiFix.exe to use it with the new firmwares. I won't share my patched .exe files. If you want it, you have to follow the tut.
You should leave the files in XperiFix folder as it currently is.
You only need TWRP for current Security Patch if you want to change files inside /sdcard, flash files from /sdcard, or create a working Nandroid Backup.

Raz0Rfail said:
I couldn't share the PM, because my PM settings wasn't configured to save it in send mails.
I will write a Tutorial after my work 19:00 (UTC +1), how to patch XperiFix.exe to use it with the new firmwares. I won't share my patched .exe files. If you want it, you have to follow the tut.
You should leave the files in XperiFix folder as it currently is.
You only need TWRP for current Security Patch if you want to change files inside /sdcard, flash files from /sdcard, or create a working Nandroid Backup.
Click to expand...
Click to collapse
Cool; will look forward to the details!
To be clear though, I have an unpatched, unrooted device that's on the most recent firmware. I'm not just updating to access the sdcard and create backups, I'm updating to crack the phone in the first place (without having to do a downgrade, which I haven't worked out the full process for yet). Not sure if that changes anything or not but figured I'd mention in case.

I had .34 firmware, used Xperifix, than upgraded to .119 and indeed it stopped working.

This is a Tutorial about patching XperiFix from Storm// to use it with new Firmwares.
It's not officially provided or allowed by him!
At first I have to be clear at the following points:
The Patch has the same requirements as XperiFix itself (without the old firmwares)
Your Device must have a unlocked bootloader.
With unlocking your bootloader, you will loose your DRM Keys for this phone forever!
The XperiFix is only simulating DRM-Keys, so the camera and other things can be used again.
You should have installed the correct drivers for bootloader and USB-Debugging
Get Software
Download and install XperiFix first on your PC:
https://www.xperifix.com/download/xperifix-latest/ Version2.2
For patching XperiFix download DnSpy on Github(https://github.com/0xd4d/dnSpy/releases/tag/v4.5.3)
Get TWRP for your FW: https://androidfilehost.com/?w=files&flid=232371 (current for .145 FW is twrp-3.2.1-0-lilac-10-patchlevel-2018-04-05.img)
Get and install Firmware
At first you need the Current firmware on your Device.
I use FlashTool to download and flash the Firmware: http://www.flashtool.net/downloads.php
Download new XZ1c-Firmware trough XperiFirm inside FlashTool.
After the download close XperiFirm to create the new FTF-file from FlashTool automaticly.
In FlashTool click Flash --> Flashmode --> Select new Firmware (don't change anything at wiping or excluding), execute the flash.
After flash reboot phone into system, it needs time just wait!
If reboot is from Android needed to finish upgrade, let the phone do it.
Patch XperiFix
Extract DnSpy from zip-file.
open DnSpy.exe, Open XperiFix.exe under File --> Open (C:\XperiFix\XperiFix.exe).
In "Assembly Explorer" switch to XperiFix (2.2.0.0) --> XperiFix.exe--> (XperiFix (Yellow Color) --> Form1 in tree structure.
Right Click on public Form1(), "edit Method".
In the new Window, you are able to change the source code.
replace the following variable
this.validfw = new List<string>
{
"47.1.A.8.49",
"47.1.A.12.34",
"47.1.A.12.75"
};
with
this.validfw = new List<string>
{
"47.1.A.8.49",
"47.1.A.12.34",
"47.1.A.12.75",
"47.1.A.12.119",
"47.1.A.12.145"
};
Click on the Button compile. You will see the changes in the main Window from DnSpy.
Click on File -> Save Module --> enter name, save the .exe-file.
Start the patched XperiFix.exe
reboot phone into Bootloader and connect it to your pc, because there XperiFIX can detect it without crashing.
If everything was correct patched with DnSpy you should be allowed to use it.
Set the hook and click on "FIX my Device!" then let XperiFIX do it's work.
if you see magisk and XperiFIX get flashed inside twrp everything is fine.
if the phone restarts into system, reboot phone into bootloader to flash your twrp recovery.
Flash Recovery
reboot phone into Bootloader and connect it to your pc.
"Path to fastboot\fastboot.exe" flash recovery "Path-to-Twrp\twrp-3.2.1-0-lilac-10-patchlevel-2018-04-05.img"
"Path to fastboot\fastboot.exe" reboot
Phone should start into android, first time needs time because it has wiped dalvic and cache.
In Android take a photo and check album if there is a green picture or not (shouldn't be).
You can start telephone APP call *#*#SERVICE#*#* or *#*#7378423#*#* and inside the Service Menu switch to "service tests" and there to Security.
Should be near identically to mine, some Thread entries before.
You have now the new Firmware and XperiFIX installed.
Afterwards I'm using root Explorer and Titanium Backup to clean the Bloatware which come from installing the new Firmware.
If something is not clear or detailed, please write it to me.

Raz0Rfail said:
This is a Tutorial about patching XperiFix from Storm//
Click to expand...
Click to collapse
Thank you so much; that's amazing!!!
One note; you mention manually flashing the new firmware with flashtool. Is there any difference between this approach and using a device that has been updated to that firmware via OTA update from Sony?
Related to that, where does the new TWRP connect in? I see that you download it, and later you mention that it gets loaded; presumably it needs to get saved somewhere specific in XperiFIX or linked to via the dnSpy changes?
I'm concerned because it sounds like everyone else here is upgrading an already flashed system and can re-flash the new twrp from the old one. I've got a fresh OTA rom I'm patching and rooting so it doesn't yet have twrp. As XperiFIX installs TWRP I assumed I'd have to link it to the correct twrp file somehow (perhaps replace the one in the XperiFIX file structure?), but I don't see that here. Something additional required in this case?

nataelj said:
Thank you so much; that's amazing!!!
One note; you mention manually flashing the new firmware with flashtool. Is there any difference between this approach and using a device that has been updated to that firmware via OTA update from Sony?
You only need the Firmware, how you get to the Firmware is secondary. But if you unlocked your bootloader you can't install the new OTAs.
Related to that, where does the new TWRP connect in? I see that you download it, and later you mention that it gets loaded; presumably it needs to get saved somewhere specific in XperiFIX or linked to via the dnSpy changes?
The TWRP recovery is only in your phone. XperiFix pushes it's own twrp trough the process.
The XperiFix TWRP is located at C:\XperiFIX\DATA\TWRP\xz1c-twrp.img.
But if you flash your own recovery as in step 5 described, the xperiFix twrp is obselete.
I'm concerned because it sounds like everyone else here is upgrading an already flashed system and can re-flash the new twrp from the old one. I've got a fresh OTA rom I'm patching and rooting so it doesn't yet have twrp. As XperiFIX installs TWRP I assumed I'd have to link it to the correct twrp file somehow (perhaps replace the one in the XperiFIX file structure?), but I don't see that here. Something additional required in this case?
I understand your concern. You will be able to forget about the OTA updates as soon as you unlock the bootloader.
My recommendation is to wait as soon as a new firmware is out until TWRP has been adapted.
Because I had to redo my mobile 3 times because I didn't wait and couldn't flash XperiFix.
This means you need to download 2.5 GB+- for each update, patch XperiFix, and start the process from the beginning.
This is the price to use the phone with root and Magisk.
Translated with www.DeepL.com/Translator
Click to expand...
Click to collapse
Do you understand better now?

@Raz0Rfail everything worked. I had to wipe and install janjan's ROM because magisk wasn't working after XperiFIX, but other that your guide worked perfectly. Thanks again.

Raz0Rfail said:
Do you understand better now?
Click to expand...
Click to collapse
Seems to have failed for me. I now get green camera images and have no root; something went wrong somewhere... :-/

Try using xperifix again. Boot into bootloader, plug phone into pc, start modified xperifix, execute it again. And check if in TWRP is flashing magisk and xperifix kernel.
Did you flash recovery with fastboot flash recovery or fastboot flash boot?
If you use the second variant, it is clear that this was your mistake, because magisk and xperifix kernel is patched into the installed kernel.

Raz0Rfail said:
Try using xperifix again. Boot into bootloader, plug phone into pc, start modified xperifix, execute it again. And check if in TWRP is flashing magisk and xperifix kernel.
Did you flash recovery with fastboot flash recovery or fastboot flash boot?
If you use the second variant, it is clear that this was your mistake, because magisk and xperifix kernel is patched into the installed kernel.
Click to expand...
Click to collapse
Hmm, maybe I could use more clarification on that step then. I actually just went into TWRP and then hit install and pointed it to install the new file (copied to the phone) as a new recovery. Would that not work? If not, is the above meant to say I should use flashtool and flash that new TRWP with it?
EDIT: Hey!!! Something worked! I checked the logs and saw some failed file copies and permission errors so I played around with it some and reran as you suggested and it seems to have worked now! I'm up and running and my photos are no longer green!!
I am not seeing Magisk as an app though, and when I try and open Titanium Backup it just cycles while looking for SU and Busybox. If I get the Root Checker app it says not rooted too even though it finds an Su; does that actually mean not rooted or does Magisk work in some other way to give permission?

Lenovo Z5s Update to ZUI 11.5 (Android 10)

Disclaimer: No guarantees. Follow at your own risk. I am not responsible for bricked phones.
Credits to 4PDA
Prerequisites:
Knowledge of OEM unlocking from Developer options, adb, and fastboot
Knowledge of QPST in case you encounter bootloop, so you can revert to a reliable stock ROM
Unlocked bootloader (from here)
1) Get your bootloader unlocked, if you haven't already.
- Visit https://www.zui.com/iunlock
- Enter the IMEI1 (Second number when you call *#06# with the phone)
- Enter the Device ID from the Bootloader/Fastboot (Hold VOL- and Power, while device is off)
- Enter your email and captcha and set the checkmark to acknowledge voiding your warranty.
- If you get an error saying that your IMEI1 is wrong, put in a sim card and wait a few hours. If it still doesn't work, write an email to [email protected]
- In the developer settings in android, enable usb debugging and oem unlock.
- Flash the sn.img file you receive with fastboot (again, hold vol- and power while the device is off). Command is 'fastboot flash unlock sn.img'. You need compatible usb drivers, qualcom drivers and adb/fastboot to do that. Use google or write me a PM if you have trouble with that.
- execute 'fastboot oem unlock-go'
- This allows you to use fastboot to flash custom system/boot/vendor/vbmeta images
Click to expand...
Click to collapse
@wzsx150's recovery-TWRP-3.3.1-1015-LENOVO_Z5S-CN-wzsx150.img MEGA Google Drive
@wzsx150's TWRP for Android 10 TWRP-3.3.2B-0508-LENOVO_Z5S-10.0-CN-wzsx150-fastboot.7z (extract the IMG file and flash using fastboot)
3) Now you can flash TWRP.
- Download ...
- Flash it from the Bootloader with 'fastboot flash recovery recovery-TWRP-3.3.1-1015-LENOVO_Z5S-CN-wzsx150.img'
- Press VOL UP / VOL DOWN to navigate to recovery.
Click to expand...
Click to collapse
11.3.169: L78071_11.3.169_DEV_FullOTA.zip
11.5.096 Update: ZUI_11.3.169_DEV_TO_ZUI_11.5.096_ST.zip
11.5.111 Update: ZUI_11.5.096_TO_ZUI_11.5.111_ST.zip
Other files, use at your own risk
Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
Official TWRP for jd2019
In recovery, Format data, then wipe Dalvik/ART Cache, Cache, Data
Reboot to recovery
Install in order, without rebooting, 11.3.169 -> 11.5.096 Update -> 11.5.111 Update.
Install Magisk 20.4
Install TWRP for Android 10 (above) using fastboot if the update replaces stock recovery after rebooting
Edited out from original
Wipe Data and flash Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
In order not to encrypt Data in the future, install Official TWRP immediately after installing updates. Install > Install Image > twrp-3.3.1-0-jd2019.img
Install GApps
Note: I do not know if the 11.5 update relocks the bootloader. It doesn't lock the bootloader.
I had bootloop from OpenGApps. 4PDA post advises to use BiTGApps. You can install Google Play Store from the built-in Lenovo App Center and that's what I did.
Haven't tried disabling dm-verity and forceencrypt.

Good job, my man, I'll check it out tonight and prepare ourselves an updateable package for people coming from any rom to avoid the hassle of going through all of that. As soon as I get it working will release a new TWRP for Android 10.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

carlshark said:
View attachment 5036881
Click to expand...
Click to collapse
Nice job man, so the update works as it should? I'm patching the images and will upload a full ota update to make it easier to move between Pie and 10. Regarding recoverys, did you test any twrp? Any decryption working? What about this official twrp, does it actually work? Thanks for the files man, this will make everything much easier

jacoghi said:
Nice job man, so the update works as it should? I'm patching the images and will upload a full ota update to make it easier to move between Pie and 10. Regarding recoverys, did you test any twrp? Any decryption working? What about this official twrp, does it actually work? Thanks for the files man, this will make everything much easier
Click to expand...
Click to collapse
I've been using the phone on 11.5.111 for a couple of days now.
I flashed both the 3.3.2 TWRP of @wzsx150 and the official TWRP and they seem to be working. I didn't turn off encryption so it seems to work well.
Happy to have helped in a small way. Thank you for your hard work!

links not works

vesdan said:
links not works
Click to expand...
Click to collapse
Thanks for the heads up, apparently the original poster removed the links. Will be uploading the ones I used.
Reuploading done.

Thank you very much

Thanks for the rom my friend.
Can you please upload the latest update cause i am rooted and it cannot be installed via the system.
Also guys ,does anyone knows if i can put the latest android 10 with multilanguage rom ?Thank you for everything ,i appreciate.

thx for the post, i am wondering if the ota will be avaliable, because the bootloader unlock site does not approve my imei number

sorry guys, i rushed and flashed the gapps and now facing a bootloop, i prepared qpst and a stock rom but i verz rom i am missing a content.xml file, can anyone please help me?

galardo_2 said:
sorry guys, i rushed and flashed the gapps and now facing a bootloop, i prepared qpst and a stock rom but i verz rom i am missing a content.xml file, can anyone please help me?
Click to expand...
Click to collapse
https://mega.nz/folder/PegDDQ7I#bmCCIt1lAWAe7ui_gkmwSQ/folder/fOAQ1QCa
here is many ROMS
Do not install gapps on ZUI !!!!

vesdan said:
https://mega.nz/folder/PegDDQ7I#bmCCIt1lAWAe7ui_gkmwSQ/folder/fOAQ1QCa
here is many ROMS
Do not install gapps on ZUI !!!!
Click to expand...
Click to collapse
but the qpst app need an aditional content.xml file, where can i get one

Install global via fastboot, all is included or in qfil ROM is all in zip file

vesdan said:
Install global via fastboot, all is included or in qfil ROM is all in zip file
Click to expand...
Click to collapse
I tried and failed again

i tired and failed again

galardo_2 said:
thx for the post, i am wondering if the ota will be avaliable, because the bootloader unlock site does not approve my imei number
Click to expand...
Click to collapse
I tried unlocking 2 Lenovo phones. The first attempt had sent me an email, but the second attempt did not. The unlock procedure went through though. So I tried changing the link provided in the first email http://cdn.zui.lenovomm.com/developer/lenovoboot/xxxxxxxx/sn.img (xxxxxxxx - serial number of phone) and it worked. This might not work for you though.
As for the OTA, I really am not sure... Probably

carlshark said:
I tried unlocking 2 Lenovo phones. The first attempt had sent me an email, but the second attempt did not. The unlock procedure went through though. So I tried changing the link provided in the first email http://cdn.zui.lenovomm.com/developer/lenovoboot/xxxxxxxx/sn.img (xxxxxxxx - serial number of phone) and it worked. This might not work for you though.
As for the OTA, I really am not sure... Probably
Click to expand...
Click to collapse
after a few atempts (3-4 days) the imei number got accepted, but now i have another problem as you can see, i flashed the gapps and now i have the bootloop and i dont have a clue how to undone it

hello friends I have all the updates installed, but it tells me that there is a new one, where can I download it?
On the other hand, what difference is there between installing by twrp and qfill?

galardo_2 said:
i tired and failed again
Click to expand...
Click to collapse
This is problem with program, drivers sahara. Try fastboot

Root any BL UNLOCKED T-Mobile/Metro OnePlus Nord with Magisk and temp root

Disclaimer: NOT RESPONSIBLE FOR ANY BRICKED DEVICES
YOUR DEVICE MUST HAVE AN UNLOCKED BOOTLOADER FOR THIS TO WORK
My first tutorial, gonna keep this short and sweet
1. Go to settings > About Phone > check your version number (eg 10.5.9 for mine)
2. Go to this thread and download the global zip with the corresponding number https://forum.xda-developers.com/t/...ota-oxygenos-repo-of-oxygenos-builds.4253501/
3. Use payload dumper to extract the payload.bin file in the zip (you don't have to extract the whole thing, I killed mine when I got my boot.img file)
4. Install Magisk on your device and patch the just extracted boot.img
5. Copy patched boot.img to your computer
6. Reboot into bootloader, run this command and NOTHING ELSE
fastboot boot <location of patched boot.img>
7. Now your device should be booted into a rooted state and if your wifi or cellular doesn't work, have no fear. This is only temporary and we need root for the next few steps
8. Install Partitions Backup https://www.apkmirror.com/apk/wanam/partitions-backup/partitions-backup-2-3-0-release/
9. Use that to dump boot.img from both slots to your device
10. Use Magisk to patch both boot.img files just dumped from Partitions Backup
11. Copy all dumped and patched boot.img files to your computer
12. Reboot into bootloader and fastboot boot into your newly patched boot.img files
13. If everything works, reboot back into the bootloader and flash the working patched boot.img files to both slots
14. Profit and enjoy! Tested and working on 10.5.9 for my N100, not yet tested on Android 11, do so at your own risk!
Leave a thanks if this helped you, this is for folks like me who couldn't find a backup of their OS build on the internet and needed a temp way to root their carrier devices

I'm going to try this now. Thank you for the idea!

I've tested this method on BE2012 / 11.0.1.BE82CB and unfortunately the global rom's boot.img bricks the device - it won't get past the T-Mobile loading screen.
I'm going to try to restore via MSM and try it with 10.5.8.BE82CB now.

bouyakasha said:
I've tested this method on BE2012 / 11.0.1.BE82CB and unfortunately the global rom's boot.img bricks the device - it won't get past the T-Mobile loading screen.
I'm going to try to restore via MSM and try it with 10.5.8.BE82CB now.
Click to expand...
Click to collapse
Unfortunately, I can't even get into EDL mode. So this brick might be permanent. I'm asking for help from the community here: https://forum.xda-developers.com/t/nord-n100-edl-mode-dead-gone.4341305/

bouyakasha said:
I've tested this method on BE2012 / 11.0.1.BE82CB and unfortunately the global rom's boot.img bricks the device - it won't get past the T-Mobile loading screen.
I'm going to try to restore via MSM and try it with 10.5.8.BE82CB now.
Click to expand...
Click to collapse
youre not supposed to flash the global rom boot.img but boot from it, thats why it relies on a temp root. and the versions have to be exactly the same or you'll brick the device
what version was your old device on? good luck unbricking it though, hope you get another shot at it

luridphantom said:
youre not supposed to flash the global rom boot.img but boot from it, thats why it relies on a temp root. and the versions have to be exactly the same or you'll brick the device
what version was your old device on? good luck unbricking it though, hope you get another shot at it
Click to expand...
Click to collapse
You're right about the flash, my mistake. Sigh.
Versions need to be exactly the same anytime you're rooting with a boot image.
This is version I was attempting to root: 11.0.1.BE82CB

bouyakasha said:
You're right about the flash, my mistake. Sigh.
Versions need to be exactly the same anytime you're rooting with a boot image.
This is version I was attempting to root: 11.0.1.BE82CB
Click to expand...
Click to collapse
yea if you had booted from a magisk rooted 11.0.1 global boot.img and followed the rest of the steps you wouldve been ok because as soon as you reboot you lose root and boot from your original boot partition again
the number 1 rule of rooting with fastboot is always boot from it and test it before flashing it. other users were warning about wifi/cell failures so i played it safe and am still fine

I just tried this method with N200. 11.0.2.0 is the latest good rooted boot.img I have, but 11.0.3.0 is latest update and there's no MSM.
Anyway booting to 11.0.3.0 using the 11.0.2.0 rooted boot.img works great! Still, I tried this method and when I extract the BootA and BootB partitions and try to flash them with Magisk, Magisk tells me it's an unsupported file. This is true when I try it as tar.gz (that's how it comes from Partitions Backup) and if I rename it to *.img - either way I can't get Magisk to want to flash it. Any ideas?
In the meantime, using the 11.0.2.0 rooted boot image seems to work fine with 11.0.3.0. So, maybe I can just go with it?
Anyway this is an awesome guide and I learned a lot from it. HUGE THANK YOU.

bouyakasha said:
I just tried this method with N200. 11.0.2.0 is the latest good rooted boot.img I have, but 11.0.3.0 is latest update and there's no MSM.
Anyway booting to 11.0.3.0 using the 11.0.2.0 rooted boot.img works great! Still, I tried this method and when I extract the BootA and BootB partitions and try to flash them with Magisk, Magisk tells me it's an unsupported file. This is true when I try it as tar.gz (that's how it comes from Partitions Backup) and if I rename it to *.img - either way I can't get Magisk to want to flash it. Any ideas?
In the meantime, using the 11.0.2.0 rooted boot image seems to work fine with 11.0.3.0. So, maybe I can just go with it?
Anyway this is an awesome guide and I learned a lot from it. HUGE THANK YOU.
Click to expand...
Click to collapse
partitions backup compresses the dump so you cant just simply rename it. think theres an option to dump it uncompressed so you can pass it on to magisk. the other way is to untar it then pass it to magisk
i'd just experiment a bit more as long as you remember to use fastboot boot until you get the config you want then you can flash it

luridphantom said:
partitions backup compresses the dump so you cant just simply rename it. think theres an option to dump it uncompressed so you can pass it on to magisk. the other way is to untar it then pass it to magisk
i'd just experiment a bit more as long as you remember to use fastboot boot until you get the config you want then you can flash it
Click to expand...
Click to collapse
Oh, thank you! That makes sense. I will try to UN-Tar it

I used Zarchiver to unarchive the TAR into boot.img for both, and this all worked! Thanks so much. Awesome guide.

@onlycash You should try this!

luridphantom said:
yea if you had booted from a magisk rooted 11.0.1 global boot.img and followed the rest of the steps you wouldve been ok because as soon as you reboot you lose root and boot from your original boot partition again
the number 1 rule of rooting with fastboot is always boot from it and test it before flashing it. other users were warning about wifi/cell failures so i played it safe and am still fine
Click to expand...
Click to collapse
I tried several times and it's not working for me.
Everything appears to be fine till I try to "fastboot boot patched.img".
I'm trying to do this on an Metro N100 which is on 11.0.1BE82CF
I downloaded the global: 11.0.1: OnePlusN100Oxygen_14.O.21_GLO_0210_2107241056 MD5: a895312987628f21d0232d44575d0742
I extracted the payload and dumped the boot.img
I patched it in Magisk
I successfully "fastboot boot" that patched file but then it just hangs at the at the Metro boot screen.
I waited a minute or two but it didn't move past that screen, should I have waited longer?
In any event, I could hold down the power key and reboot into the unrooted stock 11.01 without issue.
Does anyone have an idea what I'm doing wrong?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
.

onlycash said:
I tried several times and it's not working for me.
Click to expand...
Click to collapse
Dude your phone is an anomaly Another dude in the TWRP post has had some success on his BE2015
I'm baffled.

thomaskmaagaard said:
Dude your phone is an anomaly Another dude in the TWRP post has had some success on his BE2015
I'm baffled.
Click to expand...
Click to collapse
Interesting...
I went and read tabuRebel post and I'm not sure what he did. What I'm unsure about is if he flashed TWRP or just fastbooted it and I think he rooted 10.5, not 11.01 but that's not totally clear either. Did he ever get TWRP to flash a zip or did he use a prepatched boot.img? Lots of what he did and how it ended up are very unclear to me.
Even the posts in this thread are not always clear to me. Did they fastboot a global patched img that matched or didn't match their installed ROM?
For example did bouyakasha above used an 11.02 img to temp root his 11.03? Maybe I'm just misunderstanding what he posted.
The ambiguity in the posts can make being sure what others had success with a bit difficult to discern.
I really don't think my phone is different than any other. I think how others were successful is not as cut and dry as it may seem.
Maybe I need to update to 11.03 first.
.

onlycash said:
Interesting...
I went and read tabuRebel post and I'm not sure what he did. What I'm unsure about is if he flashed TWRP or just fastbooted it and I think he rooted 10.5, not 11.01 but that's not totally clear either. Did he ever get TWRP to flash a zip or did he use a prepatched boot.img? Lots of what he did and how it ended up are very unclear to me.
Even the posts in this thread are not always clear to me. Did they fastboot a global patched img that matched or didn't match their installed ROM?
For example did bouyakasha above used an 11.02 img to temp root his 11.03? Maybe I'm just misunderstanding what he posted.
The ambiguity in the posts can make being sure what others had success with a bit difficult to discern.
I really don't think my phone is different than any other. I think how others were successful is not as cut and dry as it may seem.
Maybe I need to update to 11.03 first.
.
Click to expand...
Click to collapse
you might also want to disable dm-verity by flashing an empty vbmeta image which you can find in other threads on xda
if you can get twrp for android 11, it's better to boot that and patch your boot image than to flash it

My experience was this method word great for:
N100 / BE2012 / 10.5.8.BE85CB
N200 / DE2118 / 11.0.3.DE18CB (allowing me to create a boot image for an update that has no binary posted yet by OP)
My experience was this method didn't work great, and bricked because I didn't read the instructions and flashed the boot image instead of booting to the boot image to test it first for:
N100 / BE2012 / 11 (can't remember rest, but I tried with current 11 version)
Hope that helps.

luridphantom said:
you might also want to disable dm-verity by flashing an empty vbmeta image which you can find in other threads on xda
if you can get twrp for android 11, it's better to boot that and patch your boot image than to flash it
Click to expand...
Click to collapse
I posted a good deal on the TWRP thread. I can fastboot the TWRP on my phone but I can't see any files only folder tree, even with my SD card I don't see any files either with TWRP.
I should add I'm running TWRP on a Metro N100 which is both SIM and bootloader unlocked. Also I didn't flash the TWRP I only fastbooted it, could that be the problem?
I really would rather flash the zip and root that way if I could get the TWRP to work.
I'm unsure what "disable dm-verity by flashing an empty vbmeta image" means in my case. What does this do?
Again I'm truly grateful for any help, thank you.

bouyakasha said:
My experience was this method word great for:
N100 / BE2012 / 10.5.8.BE85CB
N200 / DE2118 / 11.0.3.DE18CB (allowing me to create a boot image for an update that has no binary posted yet by OP)
My experience was this method didn't work great, and bricked because I didn't read the instructions and flashed the boot image instead of booting to the boot image to test it first for:
N100 / BE2012 / 11 (can't remember rest, but I tried with current 11 version)
Hope that helps.
Click to expand...
Click to collapse
Just to be clear I have a Metro N100 BE2015 running 11.0.1BE82CF.
With that being said, did you only get root when you went back to 10.5.8?
Are you rooted now on 11 and if so how did you get there?
Did you brick and go back to 10 then root 10 and update to 11 and keep root? How did you patch the img file after going to 11?
Any help and info would be much appreciated.
.

@onlycash I have constructed a small/random theory with no real basis. Could your problems be related to OOS 11? It sounds as dumb to me as it probably does to you, but I'm getting a nagging sensation that folks with success on your model aren't running the new update.
Just a weird hunch with no proper research, but I find it weird that you have these "unique" problems so I'm just spitting random junk at this point.