I finally got one of these 7T's (international) for a great price and fired it up, didn't do a bit of setup, rather slipped out after WIFI connect so as not to waste time, then used these two videos to unlock, root without TWRP, get Magisk to declare the phone rooted passing checks, and installed Viper 2.5.0.5 which works fine too.
Click to expand...
Click to collapse
Thanks to 'iFaiq Nerd' for the videos. Yeah, they're older and for older versions of 7T OOS, but work fine just by changing the OOS you're working with. You make all the files you need from your own.
I did this because I listened to them and decided he hadn't missed anything and also because I've heard video's asked for in here but didn't see a reference to these two. So far, aside from the OP7T being the side of a small house and weighing as much, it works great.
Note: You might not understand the voice in the video that well, so I recommend expanding the image and using closed captions just to be sure you're doing this correctly.
Edit: I realized when I finally rebooted for the first time yesterday that the boot_b partition hadn't been flashed so I'm adding that as the final instruction. When you're done with the above and all appears to be working fine and you're in the phone, reboot into fastboot, then do this from wherever you put your patched-magisk.
Code:
fastboot flash boot_b magisk_patched.img
Then it boots fine each time.
edit: now working on this for 11.0.0.2 global. - Will write a simple install procedure if update works (Viper works, patch-magisk works, etc).
hachamacha said:
I finally got one of these 7T's (international) for a great price and fired it up, didn't do a bit of setup, rather slipped out after WIFI connect so as not to waste time, then used these two videos to unlock, root without TWRP, get Magisk to declare the phone rooted passing checks, and installed Viper 2.5.0.5 which works fine too.
Thanks to 'iFaiq Nerd' for the videos. Yeah, they're older and for older versions of 7T OOS, but work fine just by changing the OOS you're working with. You make all the files you need from your own.
I did this because I listened to them and decided he hadn't missed anything and also because I've heard video's asked for in here but didn't see a reference to these two. So far, aside from the OP7T being the side of a small house and weighing as much, it works great.
Note: You might not understand the voice in the video that well, so I recommend expanding the image and using closed captions just to be sure you're doing this correctly.
Edit: I realized when I finally rebooted for the first time yesterday that the boot_b partition hadn't been flashed so I'm adding that as the final instruction. When you're done with the above and all appears to be working fine and you're in the phone, reboot into fastboot, then do this from wherever you put your patched-magisk.
Code:
fastboot flash boot_b magisk_patched.img
Then it boots fine each time.
edit: now working on this for 11.0.0.2 global. - Will write a simple install procedure if update works (Viper works, patch-magisk works, etc).
Click to expand...
Click to collapse
Updated to 11.0.0.2 using local - made magisk-patched.img from latest magisk and boot.img as extracted from payload of latest zip distribution.
So far, all is working well, no data on charge life but 11.0 stable was very battery friendly. -- oh yeah: The same Viper I'd used before along with the post-shell.sh file works fine.
Note 2: In V11, it takes me about 3-5 days for the playstore certification but it all works anyway until that time. - I do go to the google certification site and register it using device-id android services framework # - Cheers.
And finally. I really never had a use for the Videos - I just do what I said in the line above. I put someone's vids up because they worked the first time and they were requested.
If anyone needs magic-patched for Global OP7T (works on hd1903 & 7 maybe others). I made one from the boot.img for hd1903 global.
Edit: Just did same thing for 11.0.1.1 global and it works fine: Used the latest magisk patched boot.img -
{
"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"
}
Related
I have the Google Version of Pixel 2 XL I get a fail every time I try and update this but I get "Variable not found." I been at this all night I give up. A link would be a big help.
Thanks all
WhiteReign said:
I have the Google Version of Pixel 2 XL I get a fail every time I try and update this but I get "Variable not found." I been at this all night I give up. A link would be a big help.
Thanks all
Click to expand...
Click to collapse
i just use the factory images
https://developers.google.com/android/ota
Here's the OTAs. I've circled the right one. Maybe you were downloading the UK one?
{
"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"
}
Sent from my Pixel 2 XL using Tapatalk
I can only get the DEC 5 To work. When I do it wont let me up grade to the newer version. kinda stuck here.
Did you unlock critical? One of the messages at the very beginning says unable to flash critical. Sounds like that's the reason that it's failing. If you haven't unlocked critical, and you're going to try it, be aware that it's going to wipe your data.
Secondly, did you try just flashing the bootloader from the January update by itself first?
Sent from my Pixel 2 XL using XDA Labs
sharkie405 said:
Did you unlock critical? One of the messages at the very beginning says unable to flash critical. Sounds like that's the reason that it's failing. If you haven't unlocked critical, and you're going to try it, be aware that it's going to wipe your data.
Secondly, did you try just flashing the bootloader from the January update by itself first?
Sent from my Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
I did just this "fastboot flashing unlock_critical" now after I fast boot I get your device is corrupt It cant be trusted. If I goto Decembers OTA its fine. I dont get it. I am on Verizon's network but got my phone from Google.
WhiteReign said:
I did just this "fastboot flashing unlock_critical" now after I fast boot I get your device is corrupt It cant be trusted. If I goto Decembers OTA its fine. I dont get it. I am on Verizon's network but got my phone from Google.
Click to expand...
Click to collapse
There are multiple step-by-step guides here on how to do just this. Suggest you take a step back and read one or two. There are two separate unlock commands to use and from your photo you did not complete that. Secondly, it looks like you may be using an outdated version of the adb/fastboot binaries. Lastly you don't flash an OTA with flash-all. If you are attempting to sideload an OTA, you use the "adb sideload" command with the phone in Recovery, not flash-all in fastboot mode. At this point, you should probably update your adb/fastboot binaries, download the full factory image (not OTA) and flash it instead. Slow down and read more.
Damn Sir! Thank you very much for the help!
WhiteReign said:
Damn Sir! Thank you very much for the help!
Click to expand...
Click to collapse
Not blaming anyone but instead just using your post for calling out there are what seems like dozens of variations for doing the same few tasks on this device. There are a couple really good tutorials that are either 100% or were until something like TWRP of magisk changed something. At the end of the day there are a few givens that will eventually shake out into something like the Heisenberg thread over on the 6P device.
For anyone reading this, unlock critical if you have not, install a custom kernel if you have touch issues in TWRP, really really really read up on the few custom roms that just hit as they add a few variables that most of us have never experienced, make a list of things you install as you do it. All too often people spend countless time and effort helping someone with a boot loop only to find out something not mentioned was in play. Poor steps were attempted from some other thread only to not help or made it worse or different. Examples of this would be xposed, custom kernel, any zip file mods you flashed, viper, Dolby, substratum, you get the idea. We all wanna help and we all need help at some point. Let us try to make the game as easy to play as possible. Flash on brothers and sisters!!
Hello, my 17 year old got the new one plus 5t yesterday,
He rooted the phone but then realised he couldn’t use certain apps with it rooted, so he uninstalled magisk
He rebooted the phone but it only went into custom recovery and wouldn’t load an OS
Because that didn’t work, he tried flashing an OTA update.
Now his phone is stuck on an upside down screen and a fuzzy section on it.
I know ZERO about android phones.
Should I wait for the support to open at one plus? Or is there something I can do to fix this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
brickedmum said:
Hello, my 17 year old got the new one plus 5t yesterday,
He rooted the phone but then realised he couldn’t use certain apps with it rooted, so he uninstalled magisk
He rebooted the phone but it only went into custom recovery and wouldn’t load an OS
Because that didn’t work, he tried flashing an OTA update.
Now his phone is stuck on an upside down screen and a fuzzy section on it.
I know ZERO about android phones.
Should I wait for the support to open at one plus? Or is there something I can do to fix this?
Click to expand...
Click to collapse
tell him to download this (full firmware)
https://otafsg.h2os.com/patch/amazo...xygen_43_OTA_011_all_1804241056_afd261322.zip
Boot to recovery, copy zip to internal storage, swipe to wipe and flash the zip.
p/s if it cannot boot to custom rec then use this guide
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
Thanks so much for your reply,
In the end I spoke to one plus and they couldn’t fix it, they said I could exchange it free of charge, so he got a brand new phone yesterday! Thank god. I’m never letting him root it again tho, he only had it 24hours!!!
nguyenlucky said:
tell him to download this (full firmware)
https://otafsg.h2os.com/patch/amazo...xygen_43_OTA_011_all_1804241056_afd261322.zip
Boot to recovery, copy zip to internal storage, swipe to wipe and flash the zip.
p/s if it cannot boot to custom rec then use this guide
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
Click to expand...
Click to collapse
brickedmum said:
Thanks so much for your reply,
In the end I spoke to one plus and they couldn’t fix it, they said I could exchange it free of charge, so he got a brand new phone yesterday! Thank god. I’m never letting him root it again tho, he only had it 24hours!!!
Click to expand...
Click to collapse
You should let him experiment again, this time with some more reading here on the forum before though. He can learn a great deal about how different systems are built and the working parts of them.
And mostly since it's really fun, these days its really hard, close to impossible to mess up the phone bad.
Yes - He should be allowed to root it again - He needs practice
fkofilee said:
Yes - He should be allowed to root it again - He needs practice
Click to expand...
Click to collapse
I'm also in that opinion. He should be allowed to root again.
I may have an idea why this happened: Instead of an Oneplus 5T Firmware, he may have flashed a Oneplus 5 Firmware..
you mentioned an upside down turned Screen... well, the normal oneplus 5 had their Display assembled upside down and oneplus thought it would Fixing it by turn the Display Output by 180° by Software configuration. Your son should be Aware of that Oneplus 5 and 5T are different devices.
First step is using fastboot adb tool to flash some custom recovery first such as twrp,then download the latest oxygen system from oneplus official website(should be about 1.6gb) flash it inside and reboot. U will get a official system with official recovery set everything up. Then flash the custom recovery again and flash custom kernals such as bluespark or franco. goto the google pay or other root blocked app to set up everything.
Now you can flash the magisk to get root and activate magisk hide immediately right after u reboot. Remenber to tick the apps you need to hide the root for.
Wish u success:good:
Hi there.
I have a moto g6 play ,as described in the title. Well, everything was working fine, but I had to wipe a Lineage 16 image, 'cause the signal was really bad.
After a wipe, I tried to install a ROM that I don't know if was made for my phone or not, but anyway, I didn't get bricked, since I can load my recovery and fastboot, with no problems. However, I also tried to install other ROM's, that, for sure, are compatible (I even tried to install the one I was using before the wipe), but I got a message from TWRP, saying my phone is jeter and the rom was made for aljeter. That's so strange, my phone is aljeter and it's stated by CPU-Z and the bootloader.
Anyway, I could only install a GSI ROM, named "revenge OS", but it's pretty buggy, almost unusable. The ROM in question was in a flashable .zip format. The problem is that i just can't flash ANY OTHER .img system file, since twrp just says: "flashing file" for 10-15 seconds, and, when I reboot, always get a bootloop, because "there's no OS installed".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I suscessfully installed the stock rom, using a recovery software powered by motorola/lenovo, but that was it... Don't wanna use the stock, but it seems my phone doesn't aceept any custom anymore...
Man, I don't know what to do... please, could someone help me?
I feel sorry for the bad english, that's not my native language...
matheusmalagone said:
Hi there.
I have a moto g6 play ,as described in the title. Well, everything was working fine, but I had to wipe a Lineage 16 image, 'cause the signal was really bad.
After a wipe, I tried to install a ROM that I don't know if was made for my phone or not, but anyway, I didn't get bricked, since I can load my recovery and fastboot, with no problems. However, I also tried to install other ROM's, that, for sure, are compatible (I even tried to install the one I was using before the wipe), but I got a message from TWRP, saying my phone is jeter and the rom was made for aljeter. That's so strange, my phone is aljeter and it's stated by CPU-Z and the bootloader.
Anyway, I could only install a GSI ROM, named "revenge OS", but it's pretty buggy, almost unusable. The ROM in question was in a flashable .zip format. The problem is that i just can't flash ANY OTHER .img system file, since twrp just says: "flashing file" for 10-15 seconds, and, when I reboot, always get a bootloop, because "there's no OS installed".
View attachment 5223107 View attachment 5223109
I suscessfully installed the stock rom, using a recovery software powered by motorola/lenovo, but that was it... Don't wanna use the stock, but it seems my phone doesn't aceept any custom anymore...
Man, I don't know what to do... please, could someone help me?
I feel sorry for the bad english, that's not my native language...
Click to expand...
Click to collapse
Try
ROMs that run on the G6 Play [GSI]
Recommended Root Guide (Jeter) by Ninjakara Recommended tweaks Universal Disabler I also recommend: Magisk, for the ability to use other mods; F-Droid, for free and open source apps. Pie GSI ROMs: (Will update w/replies) Descendant AOSP PHH...
forum.xda-developers.com
Dude no ROM takes only 15 seconds to install. Maybe your download is corrupted? try downloading again. If this doesn't work, try reinstalling TWRP and then flashing again, because maybe TWRP is the troublemaker
Hi, something went wrong while trying to install pixelExperience on my redmi note 8 pro. It doesn't reach any screen, no fastboot, no recovery, no boot screen. The notification led light up when connected to the PC, but no charging screen.
I was installing pixelExperience 11 with no error, but it never booted up after rebooting.
I'm currently trying to flash rom downloaded from xiaomifirmwareupdater.com with SP flash tool. I'm using the version from UnbrickRN8ProNoAuth, it says it worked, but the phone won't start.
The booloader was unlocked, I tried both the global and the europe version. I don't know what to try now, any suggestion ?
What could be the problem, I was expecting that flashing the official rom would at least get me to the boot screen.
Thanks !
Hello to me, exactly the same thing happened to me when installing pixel experience, you follow all the steps of UnbrickRN8ProNoAuth
to use python, driver, libusb, bypass and finally spflashtool with the dafiles and the authfiles?
I use the version with this method is this:
https://c.mi.com/thread-3612344-1-0.html
With that I was able to start the mobile and the fastboot mode worked again, apparently it is a bug when entering pixel experience if you have firmware 12.5 that sometimes causes the brick, try that version it worked for me. a greeting
ps: especially remember to use the auth_sv5.auth in the program
and MTK_AllInOne_DA_mt6765_mt6785, if everything is correct you should get a green check, I tell you because first the program checks the rom if it is correct, do you connect it by pressing the 3 buttons at the same time?
Hey, thx, I'll try with this version then !
Yes I have the green check, and I connect the phone with only the vol+ pressed.
I need to do the bypass every time, is that the normal behaviour, and is there another step I should redo ?
robicop2 said:
Hey, thx, I'll try with this version then !
Yes I have the green check, and I connect the phone with only the vol+ pressed.
I need to do the bypass every time, is that the normal behaviour, and is there another step I should redo ?
Click to expand...
Click to collapse
Because of the preloader mode I never use volume + I always use the 3 buttons, so I added the "libusb filter" the bypass I don't know exactly what it is for, but the 2 times that I used the mediatek program and I used it, I just look at it, and according to github it is used for: "Small utility to disable bootrom protection (sla and daa)" and according to google the bootrom: "Bootrom (or Boot ROM) is a small piece of ROM mask or write-protected flash embedded inside of the processor chip. It contains the first code that the processor executes when turning on or resetting. "Enteoria, if it doesn't write you that data from version 12.0.4, it doesn't turn on, follow all the steps correctly with the rom that is shared with you. above and I should start your phone.
It's working again !!
I searched for a similar version but global, and installed it (https://c.mi.com/thread-3565279-1-0.html)
Thanks a lot.
If that can help someone, this time I had an error on the 4th step, it wasn't finding my phone whereas the step 5 could. I had to rerun step 3.
Now I have to choose between settling with this version or trying again ^^ did you manage to install pixelExperience in the end ?
Hi, I'm glad you fix it in the end, the rom that you put is the same, it only changes that mine is the europe version and yours is International, the google patch also changes,
In the end, if I could install pixel from 12.0.4 to pixel 12, from 12.5 the firmware is different and there are many bricks, I bricked myself just like you did not turn on anything, when going from 12.5 to pixel 11, from 12.0 no It opens up risks of going to pixel 11 or 12.
in the end, you can only install pixel 12, wanting to put 11 could not mount the system and the provider
The problem that the cameras do not work well in pixel, even installing gcam they go lag and not all of them work, not even the 64mpx mode, right now I am in miui stock with bootloader closed again. the cameras are important to me, greetings
{
"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"
}
Hi,
I've got a Motorola G60s (XT2133-2, LISBON RETEU). Hope this forum fits, otherwise please advise where to ask.
My phone is on Android 11 (Build RRLS31.Q2X-70-44-3) and rooted with Magisk. So far I did updates within the Android 11 line by patching BOOT.IMG with Magisk and then flashing all components listed in SERVICEFILE.XML with MFASTBOOT while replacing BOOT.IMG with the patched file.
For some days Lolinet is offering RETEU_12_S3RL32.114-25 now which probably is Android 12.
Is the way I described valid for upgrading from A11 to A12?
bornheim2 said:
Hi,
I've got a Motorola G60s (XT2133-2, LISBON RETEU). Hope this forum fits, otherwise please advise where to ask.
My phone is on Android 11 (Build RRLS31.Q2X-70-44-3) and rooted with Magisk. So far I did updates within the Android 11 line by patching BOOT.IMG with Magisk and then flashing all components listed in SERVICEFILE.XML with MFASTBOOT while replacing BOOT.IMG with the patched file.
For some days Lolinet is offering RETEU_12_S3RL32.114-25 now which probably is Android 12.
Is the way I described valid for upgrading from A11 to A12?
Click to expand...
Click to collapse
Hello,
Unfortunately, this is the wrong section for the G60s. And...I couldn't find a dedicated section for this model, so...I have nowhere else to point you to.
However, flashing the ROM this way should be ok. Since you already have an unlocked bootloader and, by the looks of it, you already know your way around rooting and flashing without LMSA, I think you should be fine.
If you can, try to connect your phone to a Windows PC running LMSA and see if the new version pops up this way. This would be probably the safest way to update, in case you don't have the update already on your phone, through the software udpater.
As always, my advice would be having a backup at hand, just in case things go south. But...otherwise, I think it should be fine. And also, pay attention to the servicefile xml and adjust accordingly, in case some things are different (like the number of spareschunk files, since they might be different from one Android version to another). If they're less than expected, the worst thing that could happen is you'll get an error for "whatever file not found". But if they're more (like you're expecting 9, but they're actually 10)...things will not get flashed, and phone might not boot correctly. So, just double check to make sure everything's fine in this regard.
Also, before rooting, I would go for a test drive without root. Just to make sure the phone boots as it is. After that, if you really need root, you could go through the same procedure to root your phone.
Hope this helps.
bornheim2 said:
Hi,
I've got a Motorola G60s (XT2133-2, LISBON RETEU). Hope this forum fits, otherwise please advise where to ask.
My phone is on Android 11 (Build RRLS31.Q2X-70-44-3) and rooted with Magisk. So far I did updates within the Android 11 line by patching BOOT.IMG with Magisk and then flashing all components listed in SERVICEFILE.XML with MFASTBOOT while replacing BOOT.IMG with the patched file.
For some days Lolinet is offering RETEU_12_S3RL32.114-25 now which probably is Android 12.
Is the way I described valid for upgrading from A11 to A12?
Click to expand...
Click to collapse
The safest way to update a rooted device is to use LMSA's rescue
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
sd_shadow said:
The safest way to update a rooted device is to use LMSA's rescue
Click to expand...
Click to collapse
Doesn't that reset the data?
bornheim2 said:
Doesn't that reset the data?
Click to expand...
Click to collapse
It does. That's why a backup would be necessary in this case.
If you wanna do it without resetting data, you can only do it from fastboot, aaand...even then, I would recommend having a backup at hand, in case things don't go as planned.
Usually, what you would want is an OTA you can sideload. But...there's no such thing available, for as far as I know.
I would hold off if I was you.
I have a G60s, I upgraded last week. It broke it. Seems to be causing issues for this model speciifically.
I have a thread over on Reddit. Should explain my situation. Seems the same for a couple of others.
At this point, if a factory reset doesn't work, I will attempt to downgrade to A11.
https://www.reddit.com/r/MotoG/comments/z17y3x
I can report that this process was absolutely painless. I installed S3RL32.114-25 which gave me A12 and then S3RLS32.114-25-3 which raised the security patch level to 11/2022.
{
"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"
}