Database Info

[Root] Alcatel OT Idol 6030X - Sloved

Hi everyone,
Can please some one help me Rooting this phone.. i have tryed almost all tutorials of manual an auto rooting android Devices and nothing works..
here the specifications:
Chipset MTK 6577+
CPU Dual-core 1 GHz
1 Gb Ram
Android 4.1.1
Kernel - 3.4.0
Root:
ok ok guys i've made it....
tnks God... so ive followed 4 tutorials and the combinations of them got me to this...
i will share just take a look:
{
"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 think this will work on Idol X the 6030X version only
all the files needed are here
The Sp version is on txt on the file..
User the scatter on the 7zip file
load it Sp deselect everything... but the recovery
Select the recovery on the Zip file
Power off the mobile
disconect from pc
On Sp click Download and yes and plug hte phone into the pc
Wait to complete and unplug the phone from pc..
enter on Cwm by pressing Power and Vol+ as sun u see the logo stop pressing the power and press vol+ till cwm pops.
the Zip file Root_Superuser_3.1.3_Busybox_1.20.2-Update1-signed must be on your sdcard
now follow the normal procidure to instal zip from Sdcard..
reboot phone after and open supersu, it will ask from Busybox update, choose normal, and done... install RootChecker just to verify..
My big tnks to all of you that help me to get here... and mostly to Rua1(tnks man) for this tutorial - http://forum.xda-developers.com/showpost.php?p=38337401&postcount=5
Enjoe....

I would like to know how to root this phone also...
Thanks

Anyone?

@Pyntux
Poz sugradjanine
I haven't bought the phone yet but I did some research and found 2 methods but none on english :S
Hungarian - http://data.hu/get/6493358/Alcetel_OT_6030D_Root_HowTo.pdf
German - http://www.android-hilfe.de/5684068-post10.html
I tryed to translate the German text via Google, here it goes...
-Download first the files
CWM Recovery 6030D
Cwm Recovery 6.0.2.8 Neu!! Optional
MTK Droid & Tools 2.44 (without warez)
TWRP Recovery 2.4.4.0
VCOM Drivers
SpFlashtool
************************************************** ************************************************** *
MobileUncle Tools
Mobile Uncle Tools 2.8.0
-So you can very easy to flash the patched recovery
Here we go:
-Idol connected on the PC (USB debug mode must be active) and install drivers if needed
-(Must be quick startup disabled) SPFlash run tools, Scatter file and then load cwm recovery to download press idol off
-Idol on the Pc connected (the drivers are installed automatically)
-The SPflashTools will now flash the Cwm recovery. If a green circle appears everything went well.
-Unplug the cable, run MTKDroidTools.
-Switch on with Power & Volume + and simultaneously connect the smartphone to the PC
-Once this is recognized (as comic characters will appear, but everything is ok), go to "root, backup, recovery and super user click on it that can be installed.
-The display during the root process remains dark all the time with me. So do not panic
-Unplug the cable, wait a minute and long press on the power button until the logo appears idol
-I had to update suspersu (after first boot) ... but is normal.
-You can also make a backup, although that will not be complete. Important is the boot.img and recovery.img are here.
-caution: After a reboot the CWM recovery is overwritten by the stock recovery. Personally, I would leave it there so far is no 100% functional recovery
The idol is now rooted
The CWM and TWRP recovery is not 100% functional. The Custpack partitions get no support.
edit
With Mtk Droid Root Tools & backup works fine)
Hope I helped Cant wait to get the phone, just 20 days to go...
What are your impressions about the phone?
Edit: Forgot to say, this is for 6030D but it will maybe work on the other two models... Hopefully
Have you tryed this: http://forum.xda-developers.com/showthread.php?t=2160490

Pozz sugradjanine!
Thanks a lot, but I could not root that way, perhaps I'm making a mistake somewhere, gonna try again...

Pyntux said:
Pozz sugradjanine!
Thanks a lot, but I could not root that way, perhaps I'm making a mistake somewhere, gonna try again...
Click to expand...
Click to collapse
Here an Italian guide.
http://www.androidiani.com/forum/modding-alcatel/287723-root-alcatel-one-touch-star-6010d-e-idol-6030d-unaltra-anteprima-mondiale.html

Could someone translate this to English? And has anyone managed to finally root the phone?
Sent from my ALCATEL_one_touch_995 using xda premium

I do not have enough knowledge to do a this, + none of the tutorial is on in English ...
I successfully rooted all my other android devices, gt i5500, Galaxy Ace, Galaxy Tab 2, Huawei G300, but this Alcatel giving me a headache ...

Take it easy... Im working on it...
But it is not easy...
Tapatalking From The 3° Galaxy GT-9300

Look at this:
http://forum.xda-developers.com/showthread.php?t=1923764
In Idol in default.prop is "ro.secure=1" , so we need to dump boot.img and set "ro.secure=0"

Hey Guys,
I have created the Hungarian document so will guide you through but will definitely need some time.
BRB

Here you go:
http://data.hu/get/6560704/Alcatel_6030D_Rooting.pdf
Let me know if you need help!

Gets terror uploading the custom recovery To the idol...
error 1011 no enough space....
Tapatalking From The 3° Galaxy GT-9300

Please check the scatter file maybe it's incorrect. Try re-creating it once again. The Cusotm Recovery has to be smaller or equal than the recovery partition size in the scatter file.

Finallx got the phone! It's so cool! Love the slim box and it's sooo fast! Anyway, i read something about the phone losing the DRM licence after root. Now, what does this DRM licence do and can we use this phone normally without it? As much as i got it, this has something to do with the licences for the apps...
Sent from my ALCATEL ONE TOUCH 6030X using xda premium

After losing DRM, you can lose GSM signal all the way, I do not want to play with it...
@H377
Are we losing DRM after rooting?
Is that tutorial for 6030X also?
Does stock recovery owerwrite custom cwm (which we need to install) after rooting/rebooting?

Hi,
I still can use all the features on the phone after root, so I'm not quite sure if we loose anything. Still can play videos, MP3s, so all the apps work. Haven't noticed anything yet.
I think you can root the 6030X also with this procedure just be sure that you use your own scatter file extracted from your own phone. Then you cannot really mess anything up.
If you flash the stock recovery to the phone after rooting it will definitely overwrite the custom one. So normally it doesn't overwrite it automatically only if you manually flash it.

H377 said:
Hi,
I still can use all the features on the phone after root, so I'm not quite sure if we loose anything. Still can play videos, MP3s, so all the apps work. Haven't noticed anything yet.
I think you can root the 6030X also with this procedure just be sure that you use your own scatter file extracted from your own phone. Then you cannot really mess anything up.
If you flash the stock recovery to the phone after rooting it will definitely overwrite the custom one. So normally it doesn't overwrite it automatically only if you manually flash it.
Click to expand...
Click to collapse
So I need to download stock recovery with flash tool, to flash after rooting?
Also, cwm recovery in tutorial is good, no need to mod any other recovery, just to use scatter which I made with MTK?

Pyntux said:
So I need to download stock recovery with flash tool, to flash after rooting?
Also, cwm recovery in tutorial is good, no need to mod any other recovery, just to use scatter which I made with MTK?
Click to expand...
Click to collapse
It depends on:
If you have rooted the phone you can leave the custom CWM on it no need to reflash the stock recovery. But if you want to you can flash the stock back. It's all up to you.

I'm asking because I do not need cwm for now, just need root and everything else to be stock... Thanks, I will try this method...

[C2304] Installing TWRP or CWM recovery in the Xperia C

Well, I just purchased this device and came here after that to look at what we had and I'm disgusted.
And there are several reasons for that, being:
1 - Locked Bootloader...
2 - This forum seems somewhat abandoned, which leads it to be somewhat disorganized.
EdiT:
Thanks to our friend repey6 > http://forum.xda-developers.com/member.php?u=5704037
TWRP 2.8.7.0 is now included, and it works just ok, with all functionality.
I strongly recommend you to use it instead of any other recovery. Just make sure to backup your ROM again after installing it, as CWM or Carliv backups won't work in TWRP.
I replaced the old TWRP included in the attachments with the new one provided by repey6, but the installation process remains the same.
Plus, this was not created by me and it's mad old (2014). But still it works better than the Carliv Recovery we have available here...
So Let's go. The proccess is the same for both, just choose the recovery image you want in the end of the topic.
(almost forgot to say that if your phone bricks it's you responsibility, I tested it in mine and it is working fine)
STEPS:
STEP1- Root your phone (if it's not rooted yet).
To root your phone you'll need to:
a-Download the framaroot APK provided in the attachments
b-Install it then click in the Boromir option and the su binary will be installed.
c-Download SuperSU from google play store.
That's all, simple like that.
STEP2- Check your bootloader's S1 Version
a-Open your dialer and input *#*#7378423#*#* , then go to Service Info>Software Info> S1 Boot Version.
b- Check if yours is 2.14.J.2.6 or 2.14.J.2.13 or 2.14.J.2.16 . If yours is one of these go ahead, it should work just fine and you can proceed.
If yours is 2.14.J.0.68 do not proceed, as it will 100% brick your phone.
c- My phone has S1 Boot Version 2.14.J.1.15 and in spite of the developer having not mentioned anything about it, I risked it all and my phone flashed the recovery normally, so if your version is also 2.14.J.1.15, it should work just fine and you can proceed.
STEP3 - Install the recovery
NOW, BE EXTREMELY CAREFUL HERE, OTHERWISE YOU WILL HARD BRICK YOUR PHONE:
a-Download the mobileuncle.apk file provided in the attachments and install it.
b-Download the twrp_xperia_C.img file provided below and put it in your internal memory (not on the external). Rename it to recovery.img, otherwise mobile uncle won't see it.
Now, here's the part you have to mind, so you won't brick your phone.
Mobile uncle can install a recovery using one of two methods. One is by installing the image from your internal memory (which we'll be doing). Other is installing it from the internet.
Now, YOU DON'T WANT to install a recovery from the internet, as mobile uncle doesn't provide any image for your device. So if you flash any of these recoveries, you'll never be able to make your phone boot again.
See in the image below and you'll get what I mean:
{
"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"
}
c - So, before proceeding TURN OFF YOUR WIFI AND DATA CONNECTIONS so that mobile uncle won't show any recovery from internet
d-Open mobile uncle.
e-Grant Super User
f-Press "Recovery Update"
g- With wifi turned off, you'll see only your recovery in the screen
h- Click it, the file size of the file I'm posting must be around 6MB ( 6210KB for CWM), if it's different cancel and download file again.
i- press ok and restart.
DONE
:good:
EDIT:
I just noticed that after flashing the recovery you might get your phone stuck in the SONY logo after it.
In fact it happened to me, but just once.
If that happens don't panick. Recove the cover of your phone and besides the SIM-2 slot you'll see a tiny role with the word "reset". Insert a needle in there and your phone will restart normally.
CREDITS FOR CWM
Prashanth Jraj
Credits for posting it on the net and for the original tutorial:
informationlord.com
credits for TWRP 2.8.7.0
Miha_xXx
Original Post (for TWRP - in Russian): Click Here
credits for this tutorial:
me
ATTACHMENTS BELOW

Thanks for the guide! Does this also work on the C2305 model, or is it strictly for C2304?

Syd_M said:
Thanks for the guide! Does this also work on the C2305 model, or is it strictly for C2304?
Click to expand...
Click to collapse
It should work in both, I'm using a recovery for C2305 in my C2304.
Just don't try flashing a C2305 ROM on your C2304. It will not hardbrick your phonw, but the SIM cards will not work and you will get a mad functioning phones.
Some custom ROM's based on stock firmware work in both though.

Hey anyone tried for xc 2305???

So my S1 bootloader version is: 2.14.J.0.68. Is it for sure there is nothing that can be done?

SMIT120 said:
Hey anyone tried for xc 2305???
Click to expand...
Click to collapse
sid4913 said:
So my S1 bootloader version is: 2.14.J.0.68. Is it for sure there is nothing that can be done?
Click to expand...
Click to collapse
Sorry for the late reply! Haven't been able to test this until recently due to an issue getting my PC to work properly with my phone. Anyway, I would like to confirm that I was able to flash this on my Xperia C2305 that had S1 Boot Version 2.14.J.0.68. The photo below is proof of CWM running on my Xperia C2305:
Things you will need:
WMShua SuperFlash: http://soft.flushrom.com/WMShuaSetup.exe (after installing, you can change the language to English by renaming Program Files/wmshua/language to Program Files/wmshua/language_x)
Xperia C 16.0.B.2.16 FTF: C2305_16.0.B.2.16_TacoNikky.ftf or C2305_16.0.B.2.16_Congngheviet.ftf (pick one; I used TacoNikky's version)
Procedure:
1. Open WMShua, then click on Flash (not Super Flash). Browse to the FTF file you downloaded. You can choose to backup system before flash (I unchecked it on mine). Follow the screenshot below for guidance:
2. Turn off your phone. Next, hold down the Vol- (volume down) button on your phone. While holding down, plug in the micro USB cable. The LED will flash red. When it changes to green, release the Vol- button. WMShua should automatically try to install the needed drivers. After installing drivers, it will begin the flashing process. If your phone turns on instead, simply unplug it from the USB, turn it off, then try again.
The flash process may take a long time (it took 30+ minutes for me), and sometimes it may look like it hanged, but it's actually working. Just be patient. Once it reaches 100%, your phone will automatically boot up. Check your S1 Boot Version—it should now be 2.14.J.2.16. You may find that you've lost root, so you will need to root it again (I use KingoRoot). After rooting, follow the instructions on the first post to install CWM or TWRP. Good luck!

[ROOT] Samsung galaxy J2 Prime - G532G (G532GDXU1APL1)

Hi
I created root method for the last version of samsung J2 Prime G532G - G532GDXU1APL1.
It based on modified stock recovery with custom keys (mine), which allow to install a special zip that signed with those keys.
This method include's a patched boot.img (sepolicy), in order the root work properly. (this is normal system root - not systemless, and from Android 6.0 or samsung 5.1.1 and above need also pathed boot)
The phone must be with G532GDXU1APL1 version, or it wont work.
It can be downloaded from here
G532GDXU1APL1
Instructions:
Download this file, and extract it to some folder.
G532GDXU1APL1_root_by_avicohh
Open odin and flash the .tar file inside the folder (In AP).
This file contains the custom recovery, a patched boot, and an empty cache.img in order the phone will restart to recovery after flashing.
In recovery choose "Apply update from ADB".
Run the .bat script file from the "SuperSU sideload installer" folder.
Wait until it finish, the phone will restart automatically with SuperSU inside.
Good luck!
Credits:
@Chainfire for SuperSU
@osm0sis for AIK
P.S. (for devs)
This method can be modified to another build / device, by patching the sepolicy inside boot.img (see here), and replacing the res / keys file inside the recovery.img with my keys. (Attached)
You can unpack and repack boot and recovery images with this tool. (It recomanded to this on linux in order to keep the files permissions)
The stock recovery doesn't support the standart SuperSU installer bacause it bash script, so i wrote another one in Edify. (this zip should work on any device with android 5.11 - 6.0.1 and armv7)

I am waiting new method root for G532G (G532GDXU1APL1)
Now..
great work ,,thanks bro .......I 'm so happy .....

Manual instruction recovery_custom_keys.7z ??? thank
---------- Post added at 02:11 PM ---------- Previous post was at 02:07 PM ----------
avicohh said:
Hi
I created root method for the last version of samsung J2 Prime G532G - G532GDXU1APL1.
It based on modified stock recovery with custom keys (mine), which allow to install a special zip that signed with those keys.
This method include's a patched boot.img (sepolicy), in order the root work properly. (this is normal system root - not systemless, and from Android 6.0 or samsung 5.1.1 and above need also pathed boot)
The phone must be with G532GDXU1APL1 version, or it wont work.
It can be downloaded from here
G532GDXU1APL1
Instructions:
Download this file, and extract it to some folder.
G532GDXU1APL1_root_by_avicohh
Open odin and flash the .tar file inside the folder (In AP).
This file contains the custom recovery, a patched boot, and an empty cache.img in order the phone will restart to recovery after flashing.
In recovery choose "Apply update from ADB".
Run the .bat script file from the "SuperSU sideload installer" folder.
Wait until it finish, the phone will restart automatically with SuperSU inside.
Good luck!
Credits:
@Chainfire for SuperSU
@osm0sis for AIK
P.S. (for devs)
This method can be modified to another build / device, by patching the sepolicy inside boot.img (see here), and replacing the res / keys file inside the recovery.img with my keys. (Attached)
You can unpack and repack boot and recovery images with this tool. (It recomanded to this on linux in order to keep the files permissions)
The stock recovery doesn't support the standart SuperSU installer bacause it bash script, so i wrote another one in Edify. (this zip should work on any device with android 5.11 - 6.0.1 and armv7)
Click to expand...
Click to collapse
recovery_custom_keys.7z hướng dẫn tay ??? cảm tạ

I don't understand, what instructions?

ask something
this root files include custom recovery?

Yes, but no TWRP. Modified stock recovery.

not only G532GDXU1APL1
Not only G532GDXU1APL1 is working but also G532GDXU1AQA4 is rooted smoothly i have tested on my device. So thanks a lot.:fingers-crossed:

Brother. Can you explain to me ste by step to root sm-g532g on aq4 firmware? Please
:fingers-crossed:
bolda.mia said:
Not only G532GDXU1APL1 is working but also G532GDXU1AQA4 is rooted smoothly i have tested on my device. So thanks a lot.:fingers-crossed:
Click to expand...
Click to collapse

Just do the instruction in the first post.

Hei avicoh
avicohh said:
just do the instruction in the first post.
Click to expand...
Click to collapse
sometimes i have an error when daemon start in cmd, maybe my pc's problem? I used win7 64 bit

Upload log

Log is here
avicohh said:
Upload log
Click to expand...
Click to collapse
{
"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"
}
HELP ME

I ALSO USE STOCK FIRMWARE THAT U GIVE ABOVE G532GDXU1APL1 ,
sometimes there is a messege in CMD that saying ADB out of date :/

I believe it something in your computer.
Try another one.

avicohh said:
Upload log
Click to expand...
Click to collapse
avicohh said:
I believe it something in your computer.
Try another one.
Click to expand...
Click to collapse
another one??????

alfanjawa8 said:
I ALSO USE STOCK FIRMWARE THAT U GIVE ABOVE G532GDXU1APL1 ,
sometimes there is a messege in CMD that saying ADB out of date :/
Click to expand...
Click to collapse
@avicohh WHY SUPERUSER CANNOT BE READ?

Try with another computer.

I my god it is now ask for password, and i have no z2x box to unlock it :/

So maybe @bolda.mia is wrong.
The reason the device ask for password is because the custom boot is based on G532GDXU1APL1 and you have a newer system version. (I think is something related to storage encryption, I don't know exactly)
That's why I said this method should work only on G532GDXU1APL1.
Anyway​, flash the stock version back. I believe it will fix the problem even without wipe.

before root, I already flash to lower version brother
avicohh said:
so maybe @bolda.mia is wrong.
The reason the device ask for password is because the custom boot is based on g532gdxu1apl1 and you have a newer system version. (i think is something related to storage encryption, i don't know exactly)
that's why i said this method should work only on g532gdxu1apl1.
Anyway​, flash the stock version back. I believe it will fix the problem even without wipe.
Click to expand...
Click to collapse
i know exactly, that i already flashing with the lower rom such as pl1 pk3 etc. And the result is same, ask for password my brother!

OTA update & Magisk : Bootloop. Please help!

Hello, this morning I thought I'd try to apply Oneplus OTA update, but while keeping Magisk and its modules installed.
So I googled it and I was candid enough to follow this tutorial.
Here are the exact steps I followed:
Apply the Oneplus OTA update (download & install) BUT did not reboot
Magisk Manager → Uninstall → Restore Images (Maybe that's where I screwed up as I should have run this before above step?)
installed TWRP A/B Retention Script from Magisk Manager (installed module but did not reboot).
Magisk Manager → Install Magisk → Install to Inactive Slot
Pressed the reboot button in Magisk Manager
Now the phone rebooted, oneplus boot logo, then phone unlock screen and automatically "restarted" as shown on this picture:
{
"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"
}
And then it rebooted into TWRP, asking for my password. After I enter the password, TWRP decrypt my partition and then I don't know what to do.
I flashed magisk again, but with no luck.
Thanks a lot in advance for your help and suggestions!
[EDIT] here is what happen when I flash twrp zip installer
Shoud I flash FULL oneplus firmware from this link?

I solved it by flashing oneplus full update image, then directly flashing twrp (from twrp), then flashing magisk, and finally rebooting.

I spoke too fast.
I was able to boot into oneplus system, but Magisk was not there anymore.
So I booted into recovery (twrp), flashed magisk (it said flashing on slot A this time), rebooted: Bam, same bootloop issue than before!!
Is it related to magisk modules that were not disabled? Or what?
Any feedback would be much appreciated! Thanks

Ok, so finally I did identified the root problem : Magisk module incompatibility! The faulty module is LOS Call Recorder, so I had to do this:
Removing the los call recorder module folder from TWRP file explorer (/data/adb/modules/folder_to_remove) worked!

Yes the guide specifies you disable modules. If you skip that you will boot loop. You could have gone back to the other slot and disabled them or disabled them from TWRP and then booted the new slot.

larsdennert said:
Yes the guide specifies you disable modules. If you skip that you will boot loop. You could have gone back to the other slot and disabled them or disabled them from TWRP and then booted the new slot.
Click to expand...
Click to collapse
I agree, and to elaborate one step further than this, I had the exact same issue and found that you don't just have to disable the modules, but you have to fully remove them (using the little trash icon in Magisk). I've heard the call recording module causes issues, but from now on I remove all of them to avoid the issue.
The way that I solved it post-bootloop was by booting to TWRP (either your phone retained it or use Fastboot boot with the .img file), and then using the function in TWRP 'Advanced > File Explorer' browsing to access 'Data\adb\modules'. For each offending module, browse into the module folder, then hit the blue folder icon on the bottom right to select and delete the entire folder. Be sure to only do this to the specific modules, I don't want you accidentally removing anything core to the OS.
That's the steps that worked for me I hope this helps you!

You actually don't have to trash them but it makes it clearer to most people. The issue is that after the update, Magisk thinks a particular module is installed when it isn't. If you simply disabled it previously, you can boot no problem after the OTA however if you then reenable the module, your next boot will loop because the module isn't there. Confusing so really the best advice is to uninstall modules and reinstall them so that nobody will simply reenable a dead module.

I'm having this exact issue, except I DON'T HAVE ANY MODULESSS
I don't know what to do... I've completely factory reset and it still didn't help

Have you flashed full stock without root?

larsdennert said:
Have you flashed full stock without root?
Click to expand...
Click to collapse
Haha, I actually did and that was the fix... After many Magisk Uninstaller flashes and Magisk installations, I realised the issue was with the OS itself, and flashing the stock image replaced the boot image which was causing the problem (I think... Idk if I'm right about this)

Depending on the phone model you'll need another rooted boot image. If you need a current one for the 1917, I can get you one.

Hi so i'm having this exact problem. Is there any solution that doesn't include a factory reset? Currently I'm stock os android 10 and was running magisk 20.4. had a bootloop uninstalled all modules etc and still bootloop. Only when I uninstall magisk does my phone boot to system. Reflash and we get a bootloop. Does anyone know what could be corrupted etc to stop magisk from rooting my phone? I'm sure a factory wipe will fix this but surely theres a better way.
Again,works perfectly without magisk installed. Then install magisk and we get a bootloop. Please help.

Try removing magisk manager and then flash magisk. How are you doing magisk? With an image or twrp? Could be you are using a bad boot image.

larsdennert said:
Try removing magisk manager and then flash magisk. How are you doing magisk? With an image or twrp? Could be you are using a bad boot image.
Click to expand...
Click to collapse
Magisk has been fully removed by flashing the zip file in twrp. Everything is deleted. When I reflash the zip in twrp I get a bootloop. It's the same steps as I originally used to root the phone without issue.

You understand that magisk is two parts? Boot code and an apk to manage settings. Was the apk also removed?

larsdennert said:
You understand that magisk is two parts? Boot code and an apk to manage settings. Was the apk also removed?
Click to expand...
Click to collapse
Yes when you run the installer it removes the apk also. So when I can boot back to the os there is no trace of the manager apk.

Bxperiaz3 said:
Yes when you run the installer it removes the apk also. So when I can boot back to the os there is no trace of the manager apk.
Click to expand...
Click to collapse
Try checking the /data/adb/modules to see if any modules is present,magisk don't result in bootloop unless it's one of the modules that you installed.
Uninstaller should have removed the modules,just check in twrp
You can also try flashing magisk after flashing stock boot image(use the correct versions one),maybe boot image might be corrupted

Joker123## said:
Try checking the /data/adb/modules to see if any modules is present,magisk don't result in bootloop unless it's one of the modules that you installed.
Uninstaller should have removed the modules,just check in twrp
You can also try flashing magisk after flashing stock boot image(use the correct versions one),maybe boot image might be corrupted
Click to expand...
Click to collapse
All modules have been removed. I might try flashing the stock boot image and see if that helps. my other plan was to dirty flash the stock rom and the magisk again to see if this repairs the problem.
---------- Post added at 10:49 PM ---------- Previous post was at 10:23 PM ----------
SOLVED!
In case anyone runs into this issue in future. I'm guessing something must have happened to the boot image because I fired up TWRP, cleared Dalvik, flashed the stock os, booted straight back to recovery, flashed TWRP again, then magisk 20.2. Then I switched slots and did the same thing and then rebooted. Now I have everything working again, magisk updated to 20.4 and no data or app loss. Very happy

How To Guide Update from Rooted Android 12 to Rooted Android 13 and Keep Data

Introduction
This is a guide for updating from Android 12 (rooted) to Android 13, maintaining root and keeping data. I followed this method with success after having a difficult time finding clear instructions. Hopefully it helps someone.
Disclaimer
I assume no responsibility for the malfunctioning/bricking of your phone.
Notes
Method uses Pixel Flasher
Updates both slots to Android 13 as suggested by V0latyle
One caveat with flashing patched boot.img directly (this method) is that you won't be able to revert back to take OTA updates.
To work around this, you could either follow this tutorial or boot the patched boot.img first and do a direct install in the Magisk app.
These two methods would replace the method that this post covers.
Process
Make sure you have the most up to date version of Pixel Flasher, Platform Tools, and Google USB Driver
Download factory image of Android 13
Flash using Pixel Flasher following these steps and screenshot (see corresponding numbers in screenshot)
Browse to your platform tools folder
Reload adb connected devices
Select your device from dropdown
Browse to Android 13 factory image zip file
Click to process factory image (gets boot file from image)
Select factory boot image
Patch factory boot image
Select patched boot image
Select keep data
Select flash to both spots
Push 'flash pixel phone' button
{
"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"
}
Wait for process to complete. it will take some time since it has to flash both slots. your phone will reboot to Android 13 as normal once it’s complete
Enjoy A13
Troubleshooting
Only issue I ran into was Pixel Flasher couldn't detect my device when in bootloader-fastboot mode. ADB commands were registering fine.
To fix this,
Plugged in my phone
Booted to the bootloader screen
Opened device manager in windows 10
Updated the driver for the android device/pixel 6a/unknown device using the latest google usb driver
Future OTA Updates
To take future OTAs without an original boot.img, you can either follow this tutorial to force the original boot.img into the system and take the OTA directly, or this tutorial to sideload a downloaded OTA and re-apply root with Magisk.
Thanks
topjohnwu for Magisk
badabing2003 for Pixel Flasher
psychedel!k for help with OTA update info

Thank you for the tutorial!
I have a doubt... Currently I'm already on A13 with root but I'm not very clear about the steps to follow when the next update comes out and I want to flash it already with root through pixel flasher...
- Should I follow these same steps except check that I update both slots?
- Should I check both "disable" boxes? (What are these two options for?)
- After selecting the rom and hitting "Patch" I would install the new rom with magisk and I would not lose the modules or anything like that?
Thank you again!

dannyzamora said:
- Should I follow these same steps except check that I update both slots?
Click to expand...
Click to collapse
I don't believe you need to update both slots if you've already done that when moving to Android 13. If you didn't, it would probably be good to update both slots like i show in my screenshot
dannyzamora said:
- Should I check both "disable" boxes? (What are these two options for?)
Click to expand...
Click to collapse
i would recommend reading about these two. i'm not an expert and can't provide much info without doing research myself. I chose to go with the defaults and recommendations i saw while researching the process.
dannyzamora said:
- After selecting the rom and hitting "Patch" I would install the new rom with magisk and I would not lose the modules or anything like that?
Thank you again!
Click to expand...
Click to collapse
after you click the patch button, Pixel Flasher will do the installation. you don't need to install the factory image with magisk afterward. all magisk modules should persist through the update.
happy to help the best i can.

Excellent write-up. One caveat with flashing patched boot.img directly is that you won't be able to revert back to take OTA. To work around you could either follow this tutorial or boot the patched boot.img first and do a direct install in the Magisk app

psychedel!k said:
Excellent write-up. One caveat with flashing patched boot.img directly is that you won't be able to revert back to take OTA. To work around you could either follow this tutorial or boot the patched boot.img first and do a direct install in the Magisk app
Click to expand...
Click to collapse
Ahh, i see. Thank you for sharing this. I will update my post to include this information, but to be sure i fully understand first, the work around you mention would need to be done instead of doing the process i outline, correct?
For myself who followed the process I shared, what are my options for updating once an new OTA becomes available?

R.Suave said:
Ahh, i see. Thank you for sharing this. I will update my post to include this information, but to be sure i fully understand first, the work around you mention would need to be done instead of doing the process i outline, correct?
For myself who followed the process I shared, what are my options for updating once an new OTA becomes available?
Click to expand...
Click to collapse
correct and to take OTAs without an original boot.img you could either follow this tutorial to force the original boot.img into the system and take the OTA directly, or this tutorial to sideload a downloaded OTA and re-apply root

just wanted to say thank you for this guide and detailed instructions. amazing!!

Questions
1. When I try to run APT 34 it says it won't work, so I have to use 33?
2. I have the roms in a folder but it will not find any images.
3. Do I need to reboot to bootloader and use magisk? It's greyed out.