Hello Everyone
I have a Xa1 Ultra phone (G3223)
After 3 full days of searching how can i root my phone i have come to the conclusión that is not posible because of these failed attemps :
1.- My firmware stock versión (working property) its 48.1.A.2.109 i couldnt find any custom kernel nor recovery that Works with this firmware and because of that i cant flash it, so i cant root it.
2.- I could not find and older versión of firmware that had a custom boot.img or recovery.img so i could not downgrade my phone to root it.
3.-There's only 1 post i found on this forum that had a working custom kernel and recovery to be able to root a xa1 ultra Xperia, but his stock firmware versión was 48.1.A.2.50 so as it does not matched mine any attemp to flash it got me a bootloop
So in resume is there anyway i could rot my xa1 ultra phone or all of my assumptions on my researchs are correct?
my stock firmware is G3223_48.1.A.2.109 is there any way i can root it?
Thanks in advance for any information about the subject
The furthest I got is to the conclusion that we need to downgrade to firmware G3223_48.1.A.2.101, there's a working magisk install for that.
I can't get the firmware anywhere and this forum is basically a cemetery.
Mighty_Rearranger said:
The furthest I got is to the conclusion that we need to downgrade to firmware G3223_48.1.A.2.101, there's a working magisk install for that.
I can't get the firmware anywhere and this forum is basically a cemetery.
Click to expand...
Click to collapse
Haven't tested but I found this >> G3223_48.1.A.2.101 https://drive.google.com/file/d/1-oCN7am9nL5TiDQs5uUdLGtW2zEoSVpq/view
It was listed midway through this website >>> https://www.martview-forum.com/thre...-version-firmware-ftf-lock-remove-file.23366/
The .101 downgrade went fine with flashtool, but the TWRP package I found on the janjan thread just boot loops. In fact, anything that I try ends in bootlooping, even fastboot booting an extracted kernel without modification (extracted with either AIK or flashtool).
I think this phone will be impossible to root unless we find the original 48.1.A.2.50 software.
Mighty_Rearranger said:
The .101 downgrade went fine with flashtool, but the TWRP package I found on the janjan thread just boot loops. In fact, anything that I try ends in bootlooping, even fastboot booting an extracted kernel without modification (extracted with either AIK or flashtool).
I think this phone will be impossible to root unless we find the original 48.1.A.2.50 software.
Click to expand...
Click to collapse
After flashing TWRP did you immediately factory reset? [Flash TWRP, reboot into TWRP, Wipe]. With other devices I've had issues occur if I did not remember to.
Related
Hi,
I am just writing these steps to help those who want to downgrade from KK to JB due to any reason. Please use these steps at your own risk.
Some Background:
Recently I updated my Razr M to KK, it was Locked and Unrooted, but with the help of Twelroot and Motopocalypse I rooted and unlocked the BL.
Now somehow I didn't like the KK and wanted to go back to JB 4.1.2 because I was now having unlocked BL and rooted phone so it was easy but need to follow some steps to successfully downgrade to JB. So an unlocked BL and rooted with KK is must.
Prerequisite:
USB drivers for Razr M must be installed before proceeding.
Steps:
1. download the firmware file [Android 4.1.2
Blur_Version.98.30.1.XT907.Verizon.en.US] from http://sbf.droid-developers.org/phone.php?device=8
2. extract the above archive and replace the XML file with the one in attachment.
3. put the phone into fastboot mode and flash the firmware with RSD Lite (attached)
4. reboot and now you have JB 4.1.2
If you want to install root application again and also want to flash custom recovery then please follow the Post#5 [ATTACK] (thanks ATTACK)
Note : for custom recovery you will need the fastboot.exe if you don't have it then install minimal_adb_fastboot_v1.1.3_setup.exe(attached).
Put the phone in fastboot mode, copy the recovery to c:\ and execute the below command :
fastboot flash recovery [Path to recovery image]
If it help you then don't forget to press Thanks button !
Forgive my ignorance but this won't downgrade the kernel will it? I'm hoping it's possible to go from the newest OTA to the stable CM11 but I'm guessing this is new kernel JB. Either way thanks if I can't go to stable CM11 I'll stick with rooted 4.1.2.
Once you have a unlocked bootloader, you do not need to use "root programs". All you need to do is flash a custom recovery via Mfastboot / fastboot then flash SuperSU / Superuser.
In dhacker29's folder there are 2 different recoveries.
"msm8960" is for 4.1.2
"KITKAT" is for 4.4.2
ATTACK said:
Once you have a unlocked bootloader, you do not need to use "root programs". All you need to do is flash a custom recovery via Mfastboot / fastboot then flash SuperSU / Superuser.
In dhacker29's folder there are 2 different recoveries.
"msm8960" is for 4.1.2
"KITKAT" is for 4.4.2
Click to expand...
Click to collapse
thanks ATTACK, can you please point out that which recovery is specially for 4.1.2 because there are a lot of recoveries with msm8960 in Dhacker29's folder.
One more thing if you have flashable Su and busybox zip then please attach it , i will update the OP.
thanks alot.
DHACKER29's FOLDER
- LINK
JELLYBEAN 4.1.2 RECOVERIES
- CWM-6.0.4.6-swipe-moto_msm8960
- TWRP-2.7.0.0-moto_msm8960-hdpi
KITKAT 4.4.2 RECOVERIES
- CWM6049-RAZR-HD_M-KITKAT
- TWRP2710-RAZR_M-KITKAT
SUPERUSER - I'm just going to link to Chainfire's thread, Direct people to download from there.
http://forum.xda-developers.com/showthread.php?t=1538053
BUSYBOX
https://play.google.com/store/apps/details?id=me.timos.busyboxonrails
Could you go back to KK when you've downgraded to JB? Just asking this question early before the CM11 M8 release and the transition occurs.
TheForceUnleashed said:
Could you go back to KK when you've downgraded to JB? Just asking this question early before the CM11 M8 release and the transition occurs.
Click to expand...
Click to collapse
Yes.
ATTACK said:
Yes.
Click to expand...
Click to collapse
So just by flashing the KK firmware in RSD without any changes to the xml? Sorry for the noob questions, I realize how easy this phone can be bricked and I want to avoid it.
TheForceUnleashed said:
So just by flashing the KK firmware in RSD without any changes to the xml? Sorry for the noob questions, I realize how easy this phone can be bricked and I want to avoid it.
Click to expand...
Click to collapse
I see don't why you would need to. It would be just like restoring stock firmware via RSD Lite.
When I try to flash this, I get Failure on 2/20, sbl1
jrk190 said:
When I try to flash this, I get Failure on 2/20, sbl1
Click to expand...
Click to collapse
Did you replace the XML file included in attachment?
Sent from my ME173X using Tapatalk
Sure did. I can't even restore to 4.4.2, I'm stuck on a broken system with no wifi or signal. This sucks...
reply
is this sure it works? i read the feedback so,me user try it failed?
jrk190 said:
Sure did. I can't even restore to 4.4.2, I'm stuck on a broken system with no wifi or signal. This sucks...
Click to expand...
Click to collapse
Can you please post the error that is displayed in RSD Lite ?
The steps are tested by my 2 times, and there shouldn't be any problem. Make sure you have installed the correct drivers.
Please ensure that your bootloader is unlocked and shows BL unlocked status code 3 on BL screen.
I was also able to successfully flash back to JB with House of Moto via fast boot and full data wipe. It would not work with Universal or Keep Data, had to do full data wipe. Just another alternative :good:
xKroniK13x said:
I was also able to successfully flash back to JB with House of Moto via fast boot and full data wipe. It would not work with Universal or Keep Data, had to do full data wipe. Just another alternative :good:
Click to expand...
Click to collapse
I have used my method two time successfully, just follow the steps described in OP.
reply
Thanks You Its a Success Downgrade From 4.4 stock > CM11 > Stock rom 4.1 Thank you so much !!!
For those undergoing the downgrade process in RSD Lite and it takes forever for it to finish and the system ends up without data/signal, you need to RSD Lite flash again in order to regain signal. I believe the flashing was sluggish due to the jump from 4.4.2 to 4.1.2 and the many changes that were reflashed.
Sent from my DROID RAZR M using XDA Free mobile app
We have a wiener!
Thank you so much for the guide. After a lot of trial and error (mostly error), I thought that I had bricked my lovely XT907. I finally restored KitKat by flashing the 4.4.2 firmware with the edited XML file (deleting lines with "Getvar", "var" and "oem" in them), then followed your guide to the letter and found myself with a perfectly functional phone once again. No more sticky fastboot loops or audio-related crashes for me!
Lovely guide - thanks again! :laugh:
---------- Post added at 11:05 PM ---------- Previous post was at 10:59 PM ----------
What functionality does Busybox add? The description on the Play page is woefully sparse.
Thanks!
ATTACK said:
I *DON'T see why you would need to. It would be just like restoring stock firmware via RSD Lite.
Click to expand...
Click to collapse
*EDIT
I don't know why this posted as a new reply
Hi,
I have the flickering screen problem with my phone and it is out of warranty so i can't send it back to repair.
I tried upgrading to the latest firmware, tried factory reset, wipe cache, installing google launcher, enabling the HW thing in developer mode and nothing worked.
I read that WW_2.12.40.11 version doesn't have the screen problem and i want to try it, but i wanna be sure i'm doing it the right way.
1) I read that i can't just put the wanted firmware in my phone and install the update but i must also flash the matching recovery to flash the wanted version - is it true?
2) Can i downgrade straight from my version to the lower one because i think the other way around, i need to have higher version for upgrading to the higher version i now have.
3) Where can i find the adb driver for this?
Thanks
You can downgrade via ext sd card using the downgrade version from asus > 52.20.40.196 LP which when installed , reboots to 2.20.40.196LP
When putting WW-UL- 52.20.40.196.zip.zip ,make sure to put an extra .zip on the end in file manager or in sd from pc first and reboot.
If you then put WW-UL-2.12.40.11-user.zip.zip (extra .zip) on sd or in file manager . You might get that to give you notification after a reboot too. Although i have not tested to downgrade that far .
You must use the first 52.20 blah blah fw to initially downgrade first though. Ignore this and you are liable to brick. Here >
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-52.20.40.196-user.zip
See my downgrade via ext sd video and thread , familiarise yourself with the process first !
https://forum.xda-developers.com/zenfone2/help/success-downgrade-mm-to-lp-via-sd-card-t3520642
Any questions , just ask
timbernot said:
You can downgrade via ext sd card using the downgrade version from asus > 52.20.40.196 LP which when installed , reboots to 2.20.40.196LP
When putting WW-UL- 52.20.40.196.zip.zip ,make sure to put an extra .zip on the end in file manager or in sd from pc first and reboot.
If you then put WW-UL-2.12.40.11-user.zip.zip (extra .zip) on sd or in file manager . You might get that to give you notification after a reboot too. Although i have not tested to downgrade that far .
You must use the first 52.20 blah blah fw to initially downgrade first though. Ignore this and you are liable to brick. Here >
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-52.20.40.196-user.zip
See my downgrade via ext sd video and thread , familiarise yourself with the process first !
https://forum.xda-developers.com/zenfone2/help/success-downgrade-mm-to-lp-via-sd-card-t3520642
Any questions , just ask
Click to expand...
Click to collapse
Thanks alot
Just a question before i try your method: I already installed 2.12.40.11 recovery.img into the phone. can i still use your method or should i first flash 4.21.40.223 recovery.img back to the phone?
gifnooky said:
Thanks alot
Just a question before i try your method: I already installed 2.12.40.11 recovery.img into the phone. can i still use your method or should i first flash 4.21.40.223 recovery.img back to the phone?
Click to expand...
Click to collapse
OK, it's weird, i did flash the 2.12.40.11 recovery.img to the phone using adb and it was said in the console that the process completed, but now when i enter recovery mode it still shows me 4.21.40.223 version.
OK, I did downgrade with your method and it works great, but when i try to downgrade fro that version to the version i want to try i get error that i cant install the package over the existing newer version.
Just to inform.
gifnooky said:
OK, I did downgrade with your method and it works great, but when i try to downgrade fro that version to the version i want to try i get error that i cant install the package over the existing newer version.
Just to inform.
Click to expand...
Click to collapse
If you want to downgrade to such an old version, find the .raw file of that version (search here on XDA) and flash it via Asus Flash Tool.
JBolho said:
If you want to downgrade to such an old version, find the .raw file of that version (search here on XDA) and flash it via Asus Flash Tool.
Click to expand...
Click to collapse
Thanks for the advice.
I searched and found raw firmware versions but no the one i'm looking for.
Is there any way i can install the official firmware i have? i also found recovery.img, boot.img, droidboot.img of the version i want.
gifnooky said:
Thanks for the advice.
I searched and found raw firmware versions but no the one i'm looking for.
Is there any way i can install the official firmware i have? i also found recovery.img, boot.img, droidboot.img of the version i want.
Click to expand...
Click to collapse
If you have all the img partitions you can always try installing via fastboot commands but i really recommend using a raw with Asus Flash Tool...
Hai friend try flash 3 file of boot.img recovery.img and droidboot.img version 40.11.. and then flash rom with adb sideload.. its work for me... and solve my prob flicker display..
Sent from my ASUS_Z00AD using Tapatalk
savve said:
Hai friend try flash 3 file of boot.img recovery.img and droidboot.img version 40.11.. and then flash rom with adb sideload.. its work for me... and solve my prob flicker display..
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
Hi, thanks i'l try that.
does it matter in what order i flash this 3 files?
Edit: If i already flashed the ROM can i just flash the boot.img and droidboot.img or do i need to do the whole process including flashing the ROM again?
Is your screen flickering problem like this: https://www.youtube.com/watch?v=kRuxTefNcKw
If its like that I was told its a LCD hardware problem which gets fixed by replacing LCD.
Update:
Well, I installed firmware 2.12.40.11 and it worked fine for several days but then the screen started to flicker again.
i started to update the devices with OTA updates and then i saw that in firmware WW_2.20.40.174 the screen didn't flicker.
i had further updates and then the screen started to flicker again.
i tried to flash recovery.img, boot.img and droidboot.img but not the device only enters fastboot mode but when i try to enter normal boot or recovery mode, it only comes back to fast boot mode.
any suggestion what should i do to unbrick the phone?
Thanks
Hi Everyone
I have a Z2 Plus 64GB India released model running Android 7.0 and March 2017 security patch. I have unlocked bootloader, installed twrp and also rooted using su zip file.
I have made the necessary tweaks that I wanted to do with the device and want 1) unroot (I know how to do it. Not an issue), 2) Replace twrp with stock recovery. But even after searching around in different forums, I am not able to find the stock recovery image anywhere. Can anyone help me with where to find the recovery file?
Also is it enough to only replace the stock recovery or boot image also requires any re-flashing? I am not sure about this.
Appreciate your help.
Recovery
Follow this link and download
I've extracted the recovery img and uploaded it to the drive drive.google. com/file/d/0ByBSgAwMMburNS12VEx5VVZ0b3c/view?usp=sharing
If any download prblm inbox me
Peace
ok so this is a totally noob type question:
(The goal is to root and install a custom rom on my Z1c)
I have just successfully unlocked the bootloader of my Z1 compact. What is the next step?
I read that with a UBL, I can flash a pre-rooted image. Well, first, I do not know which image should I install, but I came across this one:
https://forum.xda-developers.com/so...503-14-6-0-368customizedinpre-rooted-t3204433
Downloaded it, however, it is a zip file. Tried Flashtool but looks like it does not take zip files...only ftf. So what gives?
Is there a step I am missing?
Can someone PLEASE help me? I would really appreciate it.
Hosed!
Uh Oh....while waiting for someone to reply here...I did this and looks like I have managed to hose my phone:
As described here:
https://forum.xda-developers.com/so...503-14-6-0-368customizedinpre-rooted-t3204433
I followed the very first step ...
If You are on Lollipop
Flash any 14.4.A.0.108 FTF. You can find one here.
Click to expand...
Click to collapse
The flash to 14.4.A.0.108 FTF finished successfully......no errors...but when I boot my phone, it goes to the blue screen and then it again reboots.
Is this a boot loop people talk about?
How do I recover from it?
a little progress, but...
ok so in another thread a nice guy told me to follow this process:
https://forum.xda-developers.com/crossdevice-dev/sony/root-root-stock-firmware-modern-sony-t3558904
I did and that has given me a little more progress. However, now I am unable to boot the phone. It just says SONY...and goes black again........this keeps on looping. :crying:
rajdude said:
ok so in another thread a nice guy told me to follow this process:
https://forum.xda-developers.com/crossdevice-dev/sony/root-root-stock-firmware-modern-sony-t3558904
I did and that has given me a little more progress. However, now I am unable to boot the phone. It just says SONY...and goes black again........this keeps on looping. :crying:
Click to expand...
Click to collapse
Maybe I am wrong, but I think that you should flash stock rom with flashtool, this is for xperia z but same steps https://forum.xda-developers.com/xperia-z/general/tutorial-how-to-flash-stock-roms-t2240614 ( or you can google for more stuff )
Get stock ftf with xperifirm, will be the .236 ( last version ) you can go look for older ones here on forum https://forum.xda-developers.com/showthread.php?t=2687324
Then, I dont know if bootloader will be locked again, but anyways check that, if locked unlock and install twrp ( you need custom recovery to flash custom roms that are zip files ) https://forum.xda-developers.com/showpost.php?p=73586527&postcount=169 at bottom is twrp file
you can also follow this https://forum.xda-developers.com/showpost.php?p=73575131&postcount=130
Finally with twrp installed get a backup https://www.xda-developers.com/how-to-backup-android/ you can save to pc https://forum.xda-developers.com/android/software-hacking/tool-twrp-backup-restore-tool-pc-t3572241
Now you can flash whatever you want
As I said, I am not an expert but I think this is how it works, good luck :fingers-crossed:
So i have a samsung s9 SM-G960F/DS version. i had have run TWRP on it and magisk + exposed and it worked fine. i had to uninstall exposed to log into some apps and then i would reinstall it agian. but when i ran the exposed unintaller the phone would not boot. i tryed diffrent things and it would not boot unless it had the exposed intalled on it. i did a complete wipe of the phone with TWRP and now i can´t install stock rom. i downloaded the latest stock ROM for my model and the latest odin that can handle the lz4 compression. bur when i but in BL AP CP CSC it just get stuck on system.img all the time. i there is simply nothing i have not tryed. and nothing works for me. The only think working is if i flash the TWRP then i can boot into recovery TWRP. thats it. i am at a point where i will pay anyone who can help me figure this out cause i almost lost all hope for this to work agian. So i really really hope someone here have an ide to what could work for me. every tip and trick i will test and if someone offer help via discord or somthing i would also be glad to hear from you.
Hi
Extract and flash bootload.img or hidden.img file from the main stock rom.
I'll check the actual file name for you when I get home later. Did experience that problem sometime back on my s6 edge.
Usually there is a small error message on the screen of the s9 if odin fails or stalls. It's small blue text, I have a feeling it's either 'magic string error' or 'SYSTEM not [Sec]' or close to it. I find this happens when flashing the wrong firmware for that model. Example, flashing G960N firmware for a G960F.
I just did a reflash and here are my exact steps for my G960F.
1. Download Odin 3.13.1
2. Make sure Samsung Drivers are installed
3. Grab the latest firmware for your device, my device is a G960F so I just picked the latest BRJ3 firmware with November patch from Updato. Just get the firmware for your exact model.
4. Extract the files from the ZIP file
5. Add all the correct BL, AP, CP and CSC files to odin.
6. Select nand erase
7. Boot S9 into download mode
8. Flash to phone.
Don't try to flash TWRP before installing the full firmwares and until the phone is setup.
If all fails, and because you seem to be able to install TWRP, then you can download TGP Kernel ROM and flash that. It is based on stock G960F firmware, has a nice aroma installer for selecting various things and tweaks. It also provides a clean install of Magisk if that's something you like.
Also be sure to flash no-DM Verify.
Make sure you're not trying to downgrade the bootloader, I'm sick of writing out the same guide each time and I just did it earlier today so shouldn't be hard to find
*Detection* said:
Make sure you're not trying to downgrade the bootloader, I'm sick of writing out the same guide each time and I just did it earlier today so shouldn't be hard to find
Click to expand...
Click to collapse
thanks for the replies. the issue is fixed and the problem was the i last my "magic string" but a friendly person on the forum sent me the things needed to restore it and then restore to prerelease rom so i could upgrade to latest rom agian.
zalik20 said:
thanks for the replies. the issue is fixed and the problem was the i last my "magic string" but a friendly person on the forum sent me the things needed to restore it and then restore to prerelease rom so i could upgrade to latest rom agian.
Click to expand...
Click to collapse
Why not ot share those items to help others in the forum.
nsnobel2 said:
Why not ot share those items to help others in the forum.
Click to expand...
Click to collapse
You should look for samfirm or frija tool . Those would help you get latest firmware for your phone. Download it , flash it with odin and everything should be fine. Just remember that its possible that as you would be on latest firmware, you might not be able to downgrade in future.