Database Users

The Simple Guide To Rooting The Alcatel Idol 4

Credit goes to dbgr for finding this:
https://forum.xda-developers.com/idol-4s/how-to/6055u-root-method-t3598947
Link to download .rar:
https://mega.nz/#!U24zwYbQ!MwbIX_D01OyHHldd8c_9iCmht6wzcw1duNpGO-PRyWI
This is just a simpler, more detailed guide on how to root this phone.
Forgive me for the lack of pictures, its pretty straightforward anyways. I have included a .rar with this post that has all the essential files you will need.
(I only compressed the .rar, everything else credit goes to the creators)
1. Download the rootpackage.rar i have included, and decompress to somewhere safe.
2. Install SugarQct and install the drivers that came with it. (In the SugarQct installer, not the usb driver folder)
3. After that has finished, open the usb driver folder and run the setup.vbs script there. It should only take a second or two to run.
4. Plug phone into pc.
5. Place supersu.zip onto phone. You can put this anywhere, doesn't really matter.
6. Turn phone off and place into download mode. (Phone must be plugged in to allow download mode)
4. Open sugar with phone plugged in. Be sure to upgrade sugar if you can't see the 6055u in the list.
Set to 6055u, go to options, select save user data. Now press upgrade.
5. While sugar is downloading overwrite the r*****.mbn in bin/6055-*****. This folder appears once you start to download to the phone. You must rename the twrp_recovery_idol4_6055.img to the name of the r*****.mbn.
6. Overwrite again while files are being written. Do this as many times as you please. I only overwrote it more than once as a safety precaution.
7. Before sugar has completed fully, but after files are written, this should be around the time when it starts to download more files. As long as the writing completes you are good to go.
8. Turn phone on and enter recovery mode (power + volume up).
9. In the custom recover menu tap install and install the supersu.zip from the directory you placed it in.
10. Give it a couple of seconds (mine took 30 or so)
11. Allow phone to be rebooted and its now rooted!
Now I've had some interest in using magisk instead of supersu, but i haven't been able to install it after supersu. Choose your rom to flash wisely, as its a pain in the ass to go back from.
Please enjoy your newly rooted Alcatel Idol 4!
Thanks all!
P.S. If someone can dump their standard rom before they flash supersu.zip onto their phone, i'd like to try and find a way to get a custom rom goin and that would help.

I'm not seeing the download for the .RAR file. Am I missing something?

SeanMcCarte said:
I'm not seeing the download for the .RAR file. Am I missing something?
Click to expand...
Click to collapse
I thought i attached it to the thread, give me a second and i'll try again.
Edit:
It seems my rar is too large, i'm headed to work now, but i'll try and get something uploaded in a bit.

Thank you. Much appreciated. Also,can I unplug the phone before rebooting to recovery,or does it have to be plugged in!

SeanMcCarte said:
Thank you. Much appreciated. Also,can I unplug the phone before rebooting to recovery,or does it have to be plugged in!
Click to expand...
Click to collapse
As far as i know it doesn't have to be, but when i was successful i believe i had the phone plugged in. I did try to do somethings earlier today and unplugged the phone, and it was not successful. I do not know if it was because i unplugged the phone or if it was because i had failed to rewrite the recovery flash.

Thank you. I actually didn't want to wait for .rar so I just pieced the files from the forum here. Thank you anyway,at least somebody else will get the RAR. Also,my phone was plugged in when it worked.

I got magisk working for me I unistalled super super went into twrp and installed magisk ( I needed magisk to play fire emblem heroes lol) I'm not sure if I did something else but that's what I remember doing

Is this guide working for all the idol 4 variants or just for the cricket one? I've got the 6055k and I'm wondering if this guide works for my phone too.

scofield119 said:
Is this guide working for all the idol 4 variants or just for the cricket one? I've got the 6055k and I'm wondering if this guide works for my phone too.
Click to expand...
Click to collapse
Theres another guide for the 6055k, i'm not sure if this will work for that one. I know it works for the cricket version and i see no reason why it wouldn't work for the 6055k, but it is a better idea to follow the guide made for the 6055k.

link22534 said:
I got magisk working for me I unistalled super super went into twrp and installed magisk ( I needed magisk to play fire emblem heroes lol) I'm not sure if I did something else but that's what I remember doing
Click to expand...
Click to collapse
Would you mind checking if snapchat works on magisk? I know it doesn't work on supersu, and i've unrooted my phone because i was having troubles getting it installed after supersu.

NeonWhitey said:
Would you mind checking if snapchat works on magisk? I know it doesn't work on supersu, and i've unrooted my phone because i was having troubles getting it installed after supersu.
Click to expand...
Click to collapse
Yep it works I had to change a setting to get magisk hied working it was magisk core only mode and I pass the netsaftey check

link22534 said:
Yep it works I had to change a setting to get magisk hied working it was magisk core only mode and I pass the netsaftey check
Click to expand...
Click to collapse
Thanks for the info, but funnily enough i'm having difficulties getting the damn thing rooted again.

Thanks for the write up, I've flashed and reflashed many times... you have to be carefully about when you interrupt the process. Also know that a newer version is out. Cheers mate.

I'm not sure if it's the latest version of Sugar, but I've been trying so many times, but to no avail. Has anyone had any luck on the new version?
SUGAR QCT_SP V11.3.0
I've gotten to the point that when I start the upgrade with Sugar, it says my phone is already rooted. However, when I try to access Recovery, there is no option to install TWRP. It looks like it just loaded the same old recovery...no matter how fast and how many times I replace the Rxxxxxx.mbn file.
Cheers,
Wickster

6055p
is there any guide to root 6055p model

no luck getting this to work guys, could really use some help

Having the same problems as PizzaG - tried all the timing tips no TWRP
Having the same situation as PizzaG - same Cricket version, using the newer version of Sugar QCT 11.1.3. I've tried starting right after it reaches the last written file (4095M), Ive even tried waiting until you get the vibrate and Alcatel logo (which happens at the very end of the download, but was someone's tip), same story, boots into Android recovery. Any other tips?

Possible Solution to Rooting Troubles
I was having the same troubles as the above posters. What seemed to be the problem was that I had set a pin code to unlock my device, which made it encrypted. Unfortunately, the only way to remove a pin is to do a factory reset. Anyway, I did a factory reset and ran sugar immediately after - making sure to start the phone before sugar finished - and it worked! Perhaps there is something simpler to do and I didn't have to do a factory reset, but I don't know what that is, and this worked.

Someone have try with the 6055A?

hmm, im noticing mine says encrypted as well but i never set anything for security. just the swipe. @ ThisEndsInTears did you do a factory reset from stock recovery or from withing the phone settings? Thanks much, hopefully one step closer to getting this rooted. Y has nobody developed cm for 6.0.1 for this? cm13 im pretty sure it is

Moto E4 sperry XT1766 not booting up after a restore via TWRP

Long story short, my phone only displays the n/a screen and won't boot up.
I got the phone from Sprint, and it is the Qualcomm version. (The box says that anyway.) I wanted to root the device, so I unlocked the bootloader and attempted to flash SuperSU. This didn't work, as the app didn't show after the flash. I then tried to use Magisk, but I received Error 1 (boot image patched by other programs). To fix this issue, I downloaded a similar stock ROM and tried to install that. I ended up just wiping all the data on the phone, including the OS. Luckily I did make a nandroid backup.
The phone currently has no OS, due to me wiping all my data on it. I made a backup of when it did work (said earlier), with all partitions excluding Data. I have restored it, but it doesn't boot up. TWRP says nothing about there being no OS on the phone. I can't find a stock ROM of this particular phone, but there are some close ones. (sperry XT1768 I believe.) If anyone could help me restore my phone or possibly provide me the stock ROM I would be beyond grateful. I would also be also be okay with posting any logs or things you need.
Thanks much!

Go here:
https://firmware.center/firmware/Motorola/Moto E4/Stock/
This is the Boost XT1766 firmware :
https://firmware.center/firmware/Mo...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

I did a dumb and was rewarded
So, I ended up flashing the sperry XT1768 ROM that I had downloaded. Keep in mind I already lacked an OS, so I had nothing to lose.
PLEASE NEVER FLASH A ROM THAT DOESN'T BELONG TO YOUR DEVICE. THIS COULD CAUSE YOUR PHONE TO BE BRICKED.
Against the above statement, I literally had nothing to lose. I got my phone to boot up, and it has all of its functionality. Thank you for posting the correct software amarc78, I'll have to flash the correct ROM at a later time.
Moral of the story, please know what you are doing before you do something dumb. Use proper forums (such as the one you are on...) to do such tasks as rooting your phone.

Zachery Calahan said:
So, I ended up flashing the sperry XT1768 ROM that I had downloaded. Keep in mind I already lacked an OS, so I had nothing to lose.
PLEASE NEVER FLASH A ROM THAT DOESN'T BELONG TO YOUR DEVICE. THIS COULD CAUSE YOUR PHONE TO BE BRICKED.
Against the above statement, I literally had nothing to lose. I got my phone to boot up, and it has all of its functionality. Thank you for posting the correct software amarc78, I'll have to flash the correct ROM at a later time.
Moral of the story, please know what you are doing before you do something dumb. Use proper forums (such as the one you are on...) to do such tasks as rooting your phone.
Click to expand...
Click to collapse
Hmmmm, sounds intriguing. I soft bricked my xt1766 a few days ago and have found multiple fixes, but nothing that sticks. That above firmware? Took me two days to realize I needed RSD Lite to flash it. What was that RSD Lite? You play funny with Windows 10, no worries, I'll create my own batch file to manually flash this firmware.........WHAT!!!!!!! Why is there a multi colored ring saying "erasing" at the bottom and rebooting every 30 seconds?????? So after further research and "multiple error 7s" as well as "cant mount cache/data" errors, I came to another fix, lo and behold, im in a TWRP bootloop. Long story short, FML!!!!! Im glad you found a fix. Happy flashing.

TeamAndro08 said:
Hmmmm, sounds intriguing. I soft bricked my xt1766 a few days ago and have found multiple fixes, but nothing that sticks. That above firmware? Took me two days to realize I needed RSD Lite to flash it. What was that RSD Lite? You play funny with Windows 10, no worries, I'll create my own batch file to manually flash this firmware.........WHAT!!!!!!! Why is there a multi colored ring saying "erasing" at the bottom and rebooting every 30 seconds?????? So after further research and "multiple error 7s" as well as "cant mount cache/data" errors, I came to another fix, lo and behold, im in a TWRP bootloop. Long story short, FML!!!!! Im glad you found a fix. Happy flashing.
Click to expand...
Click to collapse
I used this rsdlite, and it works on my PC with Windows 10. Just make sure you have Motorola drivers installed.

madbat99 said:
I used this rsdlite, and it works on my PC with Windows 10. Just make sure you have Motorola drivers installed.
Click to expand...
Click to collapse
Im at work now, but when I get home, I'll definitely give that pony a whirl! Thanks man.

TeamAndro08 said:
Im at work now, but when I get home, I'll definitely give that pony a whirl! Thanks man.
Click to expand...
Click to collapse
For the Twrp loop, try selecting reboot bootloader, then in bootloader, select start. That should get you into system.
There is a fix for that, I'll find the link. Some twrp build aren't wiping something properly and causes a recovery loop after formatting data.

madbat99 said:
For the Twrp loop, try selecting reboot bootloader, then in bootloader, select start. That should get you into system.
There is a fix for that, I'll find the link. Some twrp build aren't wiping something properly and causes a recovery loop after formatting data.
Click to expand...
Click to collapse
Definitely appreciate the info brother, I havent been able to get to it cuz of work. But tonight, I will try all things youve mentioned.

TeamAndro08 said:
Hmmmm, sounds intriguing. I soft bricked my xt1766 a few days ago and have found multiple fixes, but nothing that sticks. That above firmware? Took me two days to realize I needed RSD Lite to flash it. What was that RSD Lite? You play funny with Windows 10, no worries, I'll create my own batch file to manually flash this firmware.........WHAT!!!!!!! Why is there a multi colored ring saying "erasing" at the bottom and rebooting every 30 seconds?????? So after further research and "multiple error 7s" as well as "cant mount cache/data" errors, I came to another fix, lo and behold, im in a TWRP bootloop. Long story short, FML!!!!! Im glad you found a fix. Happy flashing.
Click to expand...
Click to collapse
THIS! Have you ever found a solution? I have the EXACT SAME PROBLEM

steevo398 said:
THIS! Have you ever found a solution? I have the EXACT SAME PROBLEM
Click to expand...
Click to collapse
So you're in a TWRP loop now?

madbat99 said:
So you're in a TWRP loop now?
Click to expand...
Click to collapse
You're just all over the place, kudos to your dedication.
Basically in trying to fix the bad key/erasing boot loop I flashed twrp and tried to format data/unencrpyt which in turn throws errors which require manually reformatting /data until errors are gone and then formatting/unencrypting again which upon rebooting turns into twrp loop. Then tried to flash no-verity, the twrp loop persists.

steevo398 said:
You're just all over the place, kudos to your dedication.
Basically in trying to fix the bad key/erasing boot loop I flashed twrp and tried to format data/unencrpyt which in turn throws errors which require manually reformatting /data until errors are gone and then formatting/unencrypting again which upon rebooting turns into twrp loop. Then tried to flash no-verity, the twrp loop persists.
Click to expand...
Click to collapse
Used to have a couple of these phones .
If you're stuck in a TWRP loop
The quick workaround is to reboot to bootloader, then proceed from there to Start. However, you'll need to do this *every* time until the BCB is cleared.
To clear the BCB manually, issue this command in TWRP terminal:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=1M
have you tried formatting data, then flashing.magisk?

[Bricked]Like a Boss(err... complete imbecile)

So here's the story..
Everything was running beautifully, I got bootloader unlocked, TWRP installed and rooted with Magisk, even a few modules and of course my favorite Viper4android... All without having to ask any questions. Super silky smooth thanks to all the amazing devs here that made it so easy ?
... The problem, I'm not incredibly familiar with Magisk hide and everything was going phenomenally but low and behold the play store had to show up with an warning notification that Viper could be harmful... It wouldn't allow me to dismiss it, so like the amazing genius I am I remember that Magisk hide is used to hide things from the store...Rrrright?
Not sure if this matters but Viper was a system app at the time and yeah I TRIED to hide it ??
... thought everything was cool for about 30 seconds
... phone shut down, booted to recovery
.... So I thought, ehhh no big deal I'll just do A WIPE and restore my back up
restored the back up.... Seemed to anyhow, went through the complete process.
I went to reboot system and NADA just boots back to TWRP for a moment anyhow...
So then I'm thinking oh well I'll just go back in to restore my backup AGAIN... NOTHING'S THERE!
I go to SDcard and it's nothing but a bunch of folders with jumbled alphanumerics
Fuhhh...
At some point it stopped letting me reboot TWRP, not sure how to differentiate when, but it just loops straight back to Fastboot now Everytime and I can see my device in the computer but I try fastboot boot twrp.img and it says something like failed can't recognize boot.
Edit: (I guess this has to be in the form of a question)... What do I do?

Causical said:
So here's the story..
Everything was running beautifully, I got bootloader unlocked, TWRP installed and rooted with Magisk, even a few modules and of course my favorite Viper4android... All without having to ask any questions. Super silky smooth thanks to all the amazing devs here that made it so easy
... The problem, I'm not incredibly familiar with Magisk hide and everything was going phenomenally but low and behold the play store had to show up with an warning notification that Viper could be harmful... It wouldn't allow me to dismiss it, so like the amazing genius I am I remember that Magisk hide is used to hide things from the store...Rrrright?
Not sure if this matters but Viper was a system app at the time and yeah I TRIED to hide it
... thought everything was cool for about 30 seconds
... phone shut down, booted to recovery
.... So I thought, ehhh no big deal I'll just do A WIPE and restore my back up
restored the back up.... Seemed to anyhow, went through the complete process.
I went to reboot system and NADA just boots back to TWRP for a moment anyhow...
So then I'm thinking oh well I'll just go back in to restore my backup AGAIN... NOTHING'S THERE!
I go to SDcard and it's nothing but a bunch of folders with jumbled alphanumerics
Fuhhh...
At some point it stopped letting me reboot TWRP, not sure how to differentiate when, but it just loops straight back to Fastboot now Everytime and I can see my device in the computer but I try fastboot boot twrp.img and it says something like failed can't recognize boot.
Edit: (I guess this has to be in the form of a question)... What do I do?
Click to expand...
Click to collapse
Hi there. So the warning from the play store was actually from "play protect" which you can disable IN the play store in the left pull out menu. Not something you need Magisk hide for. Now the folders with jumbled characters are because of encryption. When you restored your backup, the device's encryption went wack on you, which happens with this device if you install or restore anything with a previous security patch than you currently have. It's annoying, but you either have to format your data entirely, or (what I recommend) use the MSM Download tool that can be found here in the guide section of this forum. Use the T-Mobile version of the tool if you have a T-Mobile variant of the device, and the global version if you have the global version of the device. What you could try to back up your important stuff, boot TWRP with fastboot using "fastboot boot [TWRPfilename]" and you might be able to plug in your device to a PC to save stuff first. But yeah, MSM tool is your best bet, that has happened to me before, and the play protect option in the play store is what you should have disabled instead of using Magisk for it.

H4X0R46 said:
Hi there. So the warning from the play store was actually from "play protect" which you can disable IN the play store in the left pull out menu. Not something you need Magisk hide for. Now the folders with jumbled characters are because of encryption. When you restored your backup, the device's encryption went wack on you, which happens with this device if you install or restore anything with a previous security patch than you currently have. It's annoying, but you either have to format your data entirely, or (what I recommend) use the MSM Download tool that can be found here in the guide section of this forum. Use the T-Mobile version of the tool if you have a T-Mobile variant of the device, and the global version if you have the global version of the device. What you could try to back up your important stuff, boot TWRP with fastboot using "fastboot boot [TWRPfilename]" and you might be able to plug in your device to a PC to save stuff first. But yeah, MSM tool is your best bet, that has happened to me before, and the play protect option in the play store is what you should have disabled instead of using Magisk for it.
Click to expand...
Click to collapse
Dang I was kind of afraid of that MSM tool thing, I'm going to have to do a little reading on that. That's one thing I've never done on an Android for sure.
Thank you
... On another note conveniently my Laptop keys ZXCVM just stopped working WTF! Not cool timing, I just bought it.

Causical said:
So here's the story..
Everything was running beautifully, I got bootloader unlocked, TWRP installed and rooted with Magisk, even a few modules and of course my favorite Viper4android... All without having to ask any questions. Super silky smooth thanks to all the amazing devs here that made it so easy ?
... The problem, I'm not incredibly familiar with Magisk hide and everything was going phenomenally but low and behold the play store had to show up with an warning notification that Viper could be harmful... It wouldn't allow me to dismiss it, so like the amazing genius I am I remember that Magisk hide is used to hide things from the store...Rrrright?
Not sure if this matters but Viper was a system app at the time and yeah I TRIED to hide it ??
... thought everything was cool for about 30 seconds
... phone shut down, booted to recovery
.... So I thought, ehhh no big deal I'll just do A WIPE and restore my back up
restored the back up.... Seemed to anyhow, went through the complete process.
I went to reboot system and NADA just boots back to TWRP for a moment anyhow...
So then I'm thinking oh well I'll just go back in to restore my backup AGAIN... NOTHING'S THERE!
I go to SDcard and it's nothing but a bunch of folders with jumbled alphanumerics
Fuhhh...
At some point it stopped letting me reboot TWRP, not sure how to differentiate when, but it just loops straight back to Fastboot now Everytime and I can see my device in the computer but I try fastboot boot twrp.img and it says something like failed can't recognize boot.
Edit: (I guess this has to be in the form of a question)... What do I do?
Click to expand...
Click to collapse
have something similar like you and my phone every time go to fastboot so what I have done is installed rom from fastboot and it worked like a charm my phone was up and running. Little notice if you going to install rom via fastboot you will get some error message but just ignore it and wait till phone reboot and it will erase all data on the phone.
Here is the link if you chose to try just read all before on page one
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516

Sipi1302 said:
have something similar like you and my phone every time go to fastboot so what I have done is installed rom from fastboot and it worked like a charm my phone was up and running. Little notice if you going to install rom via fastboot you will get some error message but just ignore it and wait till phone reboot and it will erase all data on the phone.
Here is the link if you chose to try just read all before on page one
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
Click to expand...
Click to collapse
thank you all for your replies, however I'm beginning to get really frustrated. I'm trying to use the MSM tool and how do I frickin run an .exe when the damn thing is a .rar format, the instructions under that thread are not particularly descriptive. Do I extract it? do I have to run something in a window somewhere? if my device is in EDL and the port shows Qualcomm HS-USB QDLoader 9008 (COM6) is that good?

OMG!

Causical said:
OMG!
Click to expand...
Click to collapse
MSM tool isn't too bad really. You're issue there is most likely a corrupted download. Redownload the entire tool and try to extract it again. Let me know what happens!

H4X0R46 said:
MSM tool isn't too bad really. You're issue there is most likely a corrupted download. Redownload the entire tool and try to extract it again. Let me know what happens!
Click to expand...
Click to collapse
I redownloaded that same one at least twice now... Am I doing right by using WinRAR? I just downloaded from official site the trial version.

This has got me wanting to repeatedly dropkick myself in the larynx.
....#slowassWiFi

Causical said:
I redownloaded that same one at least twice now... Am I doing right by using WinRAR? I just downloaded from official site the trial version.
Click to expand...
Click to collapse
Yes, you are doing it right.
I would use 7zip but winRAR is fine. Dont know why someone would be using that in this day and age... but hey, it works...
I have also read other random threads that says that the file is corrupt. If you cant get a good download let me know and I will upload my collection of files. Send me a PM if you need me to upload. It wont be for a couple hours though...

Apparently they're all corrupt. I just downloaded 9.0.11 after doing .12 first and I'm getting the same errors in WinRAR

Yeah good call on 7-zip, I uninstalled winrar... complete garbage, all changing my folder icons without my consent and stuff.

Causical said:
Yeah good call on 7-zip, I uninstalled winrar... complete garbage, all changing my folder icons without my consent and stuff.
Click to expand...
Click to collapse
Was it Ok with 7Zip?

Scott said:
Was it Ok with 7Zip?
Click to expand...
Click to collapse
No lol, but it's a little more clear that the file is corrupt I suppose ?
Edit: Hey I'm going to try the recommendation of the other guy ^^up there with the fastboot ROM, I don't think it will work because I don't think fastboot is recognizing my boot, but guess we'll see... I'm just curious do you recommend doing the flash-all-partitions-fastboot.bat? Or the "Big One" flash-all-partitions.bat...I feel like I'm on the verge of really slipping deeper into the abyss here.

Here I go... Hope you reply within next 30 seconds lol
Edit: Ho-Ly poop I think that was the single most terrifying event of my life... IT WORKED! I used Mauro's fastboot ROM technique....uuggghhh

I think I used flash all bat and that work for me but phone was reset to factory settings after that
---------- Post added at 03:29 AM ---------- Previous post was at 03:23 AM ----------
Causical said:
Here I go... Hope you reply within next 30 seconds lol
Edit: Ho-Ly poop I think that was the single most terrifying event of my life... IT WORKED! I used Mauro's fastboot ROM technique....uuggghhh
Click to expand...
Click to collapse
im glad it worked, have the same filing as you when I brick phone and then make him work again.

Sipi1302 said:
I think I used flash all bat and that work for me but phone was reset to factory settings after that
Click to expand...
Click to collapse
That's alright, I'll reset everything. Thanks A Bunch dude, that was scary.
Remember kids, Magisk hide is bad mmmkay, don't do Magisk hide!
... All this because I didn't want a pesky warning notification gyollee dude, that allowed me to get absolutely nothing else done on my day off work lol.

Causical said:
That's alright, I'll reset everything. Thanks A Bunch dude, that was scary.
Remember kids, Magisk hide is bad mmmkay, don't do Magisk hide!
Click to expand...
Click to collapse
you welcome, Im glad I could help.Now you will know for the next time hehe:laugh:

I think MSM tool would still be valuable to know how it works, but let's hope I don't need it.

At least you are up and running!
But yeah, the MSM tool is pretty easy to use. If you ever used ODIN on a Samsung phone it would be familiar.

Didn't realize I was upgrading to Android 11, magisk_patched.img bootloops, need help

When I downloaded the lasted OTA update for my OnePlus 8 Pro I thought it was just another hotfix and didn't realize it was a Big Deal Android 11 update. I tried using the normal OTA upgrade processed and kinda screwed myself.
After trying to install in the inactive slot the way I normally upgrade OTA, I ended up bootlooping. So I downloaded the recovery image and tried patching Magisk the long adb way. It wasn't until later that I realized I had to be on the beta channel. I didn't know you needed to disable modules when you upgrade to Android 11, so they might still be in play, but I don't know how to check. I've tried a bunch of stuff without much luck. Here's where I'm at now:
1) Bootloader is unlocked
2) I can get into Recovery Mode fine
3) I can flash the default/unpatched boot.img for my build and boot up fine, but there's no root, and wifi doesn't work and cellular data is really flakey (even though I normally have fine reception here).
4) From an unpatched boot.img I switched Magisk Manager to the beta channel and installed v21.1. Then I patched boot.img to make a new magisk_patched.img from the beta channel.
5) When I try to fastboot flash magisk_patched.img to slot A I bootloop.
6) When I try to fastboot boot magisk_patched.img I get stuck on the red dot with 2 white dots orbiting it for seemingly forever.
7) I think something is wrong in my slot B because I mostly just get stuck in fastboot. This might be an unrelated problem from a while back though.
8) When I try to run adb wait-for-device shell magisk --remove-modules, I just get an error message about magisk not being found.
What can I do to get back to a rooted working patched magisk without wiping all my data and starting from scratch?

I've honestly never seen anyone do this before so I'm curious as to how you'll recover from this
My thought are MSM but you may be able to boot. Problem is the magisk modules are still in play.
The adb command may not work for removal as you may not get that far.
Did the installation go through ok? It was just booting that failed?
Could maybe try to wipe system via recovery and go from there.
I'm not too sure buddy.
Keep us posted how u get on.
Edit: Try to boot the boot img.
What model are you on? BA ? I have the boot images in my guides in the guides section. Feel free to take what you need.

dladz said:
My thought are MSM but you may be able to boot. Problem is the magisk modules are still in play.
Click to expand...
Click to collapse
What is MSM?
dladz said:
Did the installation go through ok? It was just booting that failed?
Click to expand...
Click to collapse
You mean the result of fastboot flash magisk_patched.img? Yeah, that has finished fine every time. I'm either stuck bootlooping or booting up never finishes.
dladz said:
Could maybe try to wipe system via recovery and go from there.
Click to expand...
Click to collapse
Doesn't that delete all my data? I've only tried wiping the cache so far.
dladz said:
Edit: Try to boot the boot img.
Click to expand...
Click to collapse
Do you mean fastboot boot magisk_patched.img? That just spins forever and never finishes booting.
Flashing back to the unpatched boot.img boots up fine, but my wifi won't turn on and my cellular data is flakey (even though I usually have fine reception here).
dladz said:
What model are you on? BA ? I have the boot images in my guides in the guides section. Feel free to take what you need.
Click to expand...
Click to collapse
I have the US hardware, so I extracted the boot.img from 11.IN21AA, which was the same number that showed up after the OTA was applied.

I dunno, I tried a bunch of different stuff, ended up bricking it. Restored it with MSM to Android 11, then unlocked the bootloader, and tried to flash a fresh magisk_patched.img and it refused to boot in the same way, even though everything was completely fresh.
Are we sure the Magisk beta channel is working right now?

Ecna said:
I dunno, I tried a bunch of different stuff, ended up bricking it. Restored it with MSM to Android 11, then unlocked the bootloader, and tried to flash a fresh magisk_patched.img and it refused to boot in the same way, even though everything was completely fresh.
Are we sure the Magisk beta channel is working right now?
Click to expand...
Click to collapse
There hasn't been anyone stating issues.
Are you using lucky patcher?

dladz said:
There hasn't been anyone stating issues.
Are you using lucky patcher?
Click to expand...
Click to collapse
I don't know what lucky patcher is, so I guess not?
Turns out the wifi problem was happening on stock anyway. And EdXposed doesn't support 11 yet either. So I flashed back to 10.5.13 before bothering to set up all my apps. I'm gonna wait a bit longer for until 11 is more ripe.

Ecna said:
I don't know what lucky patcher is, so I guess not?
Turns out the wifi problem was happening on stock anyway. And EdXposed doesn't support 11 yet either. So I flashed back to 10.5.13 before bothering to set up all my apps. I'm gonna wait a bit longer for until 11 is more ripe.
Click to expand...
Click to collapse
Ah ok, that's fine if you don't know what lucky patcher is then that's a good thing

Yes, that patched boot image failed me. Can't boot. Can't find stock to flash. Bumbed.

dladz said:
Ah ok, that's fine if you don't know what lucky patcher is then that's a good thing
Click to expand...
Click to collapse
Hi dladz, can you please give me more info on lucky patcher and how it could affect things. I'm an avid lucky patcher user, and recently had issues with phone not booting, had to do a factory reset. (I wonder if lucky patcher was some how the culprit)

hbhorat said:
Hi dladz, can you please give me more info on lucky patcher and how it could affect things. I'm an avid lucky patcher user, and recently had issues with phone not booting, had to do a factory reset. (I wonder if lucky patcher was some how the culprit)
Click to expand...
Click to collapse
Don't know if you know this or not but you can't even discuss LP on XDA so I'm afraid I can't..
All I know is that it's dodgier than Donald trump's hair and should be avoided like an old woman's waffle.
If you've had problems and lucky patcher was installed that would be top of my list of culprits.
Bootloops, corruption, force closes to name but a few issues, it probably mines for coin using your phone's processor when it's not in use and god only knows what it does with your data, if that's the price of free apps? Id rather pay for them, my data is with more than any app.
Soz mate, that's all I can offer.
Just avoid it.. :good:

Question [FIXED] Rooted phone(1) freezes about 30 seconds after boot after failed update.

Hey, this is my first post on this forums so excuse me if there are some issues with the way I'm posting.
I have a rooted Nothing Phone (1) at version 1.1.4 (EEA). I got notified about the update to 1.1.6 and of course I wanted to update.
I don't have much experience at phone tinkering and after searching I tried these steps to update my phone. Step 1 and 2 were succesfully done. On step 3 the Updater in settings gave an error saying it couldn't update. I was stupid enough to reboot my phone at this point. At first I thought it booted normally but after 30 seconds or so the phone freezed up, resulting in a soft reboot about a minute later. It's stuck in this loop.
[EDIT] Not actually stuck as I can still use the phone until it freezes and it doesn't freeze in bootloader or recovery
What I've already tried:
- sideloading the update manually via Recovery/ADB. threw an error.
- using fastboot to boot with the rooted image. I thought maybe there is something that is expecting root that is freezing up the phone. Phone still freezed up.
- sideloading the 1.1.6 full update package. threw an kinstalldeviceopenerror
I'm a bit out of ideas how to save my new device. Does anyone have any suggestions?

Make sure you have the right update for your device version.
Nothing Phone 1 update tracker: Here are all the official Nothing OS builds to download and install
We tracked down all the Nothing Phone 1 updates so you don't have to.
www.xda-developers.com
You can try to install a magisk patched boot img
b_5.4.147-qgki-g3e5c6bfc5f18
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
How to unbrick Nothing Phone 1 fastboot bootloop
Welcome to this unbrick tutorial NB: I state immediately that i'm not responsible for any damage that occurs on your phone. This process worked for my Nothing Phone on 1.1.3, but maybe not on yours. I do not suggest following this tutorial if...
forum.xda-developers.com
You will loose all data un your phone doing this.

xtcislove said:
Make sure you have the right update for your device version.
Click to expand...
Click to collapse
In recovery I found out that I have the SKQ1.211230.001/1663771117 (1.1.4 global hotfix) version even though I'm on a European device. Is it okay to try to update to 1.1.5 and then 1.1.6 or will ik mess with any settings?
xtcislove said:
You can try to install a magisk patched boot img
b_5.4.147-qgki-g3e5c6bfc5f18
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Click to expand...
Click to collapse
Done. Didn't change anything except bring my root back. Phone still freezes up.
xtcislove said:
You will loose all data un your phone doing this.
Click to expand...
Click to collapse
Isn't available for this version from what I know and I wanna first get the region problem sorted out.
The thing I find weird here is. The problem started after turning off all magisk modules, and removing the patched boot file via magisk. I reset root and turned on all modules again and the phone still freezes up. I don't know where to search.
EDIT: While pulling /sdcard/ with ADB I found that the command still pulls data while the phone freezes which I find very weird

JDeVries said:
In recovery I found out that I have the SKQ1.211230.001/1663771117 (1.1.4 global hotfix) version even though I'm on a European device. Is it okay to try to update to 1.1.5 and then 1.1.6 or will ik mess with any settings?
Done. Didn't change anything except bring my root back. Phone still freezes up.
Isn't available for this version from what I know and I wanna first get the region problem sorted out.
The thing I find weird here is. The problem started after turning off all magisk modules, and removing the patched boot file via magisk. I reset root and turned on all modules again and the phone still freezes up. I don't know where to search.
EDIT: While pulling /sdcard/ with ADB I found that the command still pulls data while the phone freezes which I find very weird
Click to expand...
Click to collapse
I guess there is something mixed up in your phone.
Since you can use adb pull, simply backup everything and do a reset.
I backup my phone daily do Google Drive, which is maybe not the case for you. I would simply follow the unbrick tutorial and go back to 1.1.3 EEA (You need to flash the super.img first). This will give you a clean device again so you can exclude that the freezing is a hardware error.
There is only one thing you can try:
Flash flash boot 1.1.6 and vendor_boot 1.1.6 and adb sideload full 1.1.6 eea via recovery.
I would go back to EEA.

There was something mixed up. I couldn't fix by sideloading 1.1.6 via recovery. I factory reset my phone via recovery which fixed the freezing. Then I pushed the 1.1.6 EEA rom to /sdcard/ota and dialed *#*#682#*#*. Installed the update from there and everything works again!