Related
Hi
I am having some issues with my Xperia Z2 D6502. I am new to rooting, so please bear with me.
I rooted my device following these instructions. All things went smoothly. However next day I started having problems to boot into recovery mode. I have explained my problem here. I tried reinstalling Z2-lockeddualrecovery2.7.154-BETA.installer which I got from the above instructions. It installed successfully but still I couldnt boot into recovery mode. The phone even stopped detecting my SD card, I had to reinsert it each time I would reboot to make it work.
So I followed all the instructions from the scratch again except for the last one which involved flashing pre rooted 5.1.1 stock ROM(flashable_D6502_23.4.A.0.546.zip). I wanted to keep rooted kitkat 4.4.2(I initially,i ..e., before rooting, had 5.1.1 but according to the instructions I had to downgrade it to kitkat) which I obtained as a result of downgrading my Xperia Z2 from 5.1.1.
Now I am facing wifi problems with kitkat. I can connect to the network but internet works extremely slow while it works absolutely fine on other devices. I dont have access to the router as its a common router in my dorm. I tried several solutions which I found on internet involving changing DNS to 8.8.8.8 and changing IP settings to static. None of them had any effect. Is there anything else I could do to resolve this issue?
The main reason I want to keep kikat is that I want to install Xposed on my device for imei changer and android id changer, and I read somewhere that for installing Xposed on kitkat you dont need to flash any zips and just install it like any other app. I didnt flash it on lollipop because of the warnings about getting stuck in bootloop in sony devices and I wasnt sure of how to flash it as the instructions were not very detailed and I am new to it. So do we flash it the same way I flashed 5.1.1 rom, i.e., booting into recovery mode and then selecting install and then selecting the zip I want to install?
I got this link to working modules on sony devices but I cant find imei changer in the list. So even if I installed Xposed, with your help of course, will I be unable to use imei and android id changer?
I read in several places that I should backup my device so that I can restore to the previous state in case I soft brick it or enter a bootloop. What kind of backup is this and how do I take it?(I googled and found Backup TA to take backup but I am not sure if that is the type of backup I am looking for and the instructions in the page are not detailed enough for me as I cant risk my device.)
I have one request, please provide me with detailed steps as I am doing all of it for the first time and am extremely nervous of screwing up my device as it is my only phone and quite expensive too.
Well, my device is rooted, on 5.1.1, and Xposed Works very well, without bootloops, and all Modules that I tried worked very well, by your description I can't figure out what is causing your problems...
stayawake said:
Well, my device is rooted, on 5.1.1, and Xposed Works very well, without bootloops, and all Modules that I tried worked very well, by your description I can't figure out what is causing your problems...
Click to expand...
Click to collapse
I havent tried Xposed on my device yet. Have you tried imei changer and android id changer? If not can you confirm if it works?
Can you please provide me with detailed step on how to install Xposed?
If my device goes into bootloop, will I be able to flash it using stock ROM?
And can you please provide answers regarding taking backup?
berbatov93 said:
I havent tried Xposed on my device yet. Have you tried imei changer and android id changer? If not can you confirm if it works?
Click to expand...
Click to collapse
I didn't tried these two modules.
berbatov93 said:
Can you please provide me with detailed step on how to install Xposed?
Click to expand...
Click to collapse
following the official topic of the module, you will have all the steps to install it, and the version that most fits with your system version
berbatov93 said:
If my device goes into bootloop, will I be able to flash it using stock ROM?
Click to expand...
Click to collapse
If you got a boot loop, you can:
1: Force power off the device by holding volume+ and power button simultaneously, then, you will able to flash via flashtool a new ROM
2: if you have a custom recovery, you can follow the same method to power off, then, power on and access the recovery, where you will be able to flash a zip containing a new system, etc.
berbatov93 said:
And can you please provide answers regarding taking backup?
Click to expand...
Click to collapse
Well, again, using a custom recovery you can make a Backup, the interface is very intuitive and easy to understand.
stayawake said:
I didn't tried these two modules.
Click to expand...
Click to collapse
Can you please try them?
If you got a boot loop, you can:
1: Force power off the device by holding volume+ and power button simultaneously, then, you will able to flash via flashtool a new ROM
2: if you have a custom recovery, you can follow the same method to power off, then, power on and access the recovery, where you will be able to flash a zip containing a new system, etc.
Well, again, using a custom recovery you can make a Backup, the interface is very intuitive and easy to understand.
Click to expand...
Click to collapse
Do we make custom recovery using the backup option we get when we boot into recovery menu?
And how to enter recovery menu without booting into the system? I access it using NDR utils app.
And do I need to flash any recovery zip from the recovery menu if I want to keep it?
berbatov93 said:
Can you please try them?
Do we make custom recovery using the backup option we get when we boot into recovery menu?
And how to enter recovery menu without booting into the system? I access it using NDR utils app.
And do I need to flash any recovery zip from the recovery menu if I want to keep it?
Click to expand...
Click to collapse
If you have Dual recovery, you are already running a custom recovery.
to enter the recovery menu whitout boot the system, you should:
Power On the device, and at the FIRST SONY screen, when the LED flashes, press volume up to enter TWRP
stayawake said:
If you have Dual recovery, you are already running a custom recovery.
to enter the recovery menu whitout boot the system, you should:
Power On the device, and at the FIRST SONY screen, when the LED flashes, press volume up to enter TWRP
Click to expand...
Click to collapse
Volume down for TWRP, volume up goes to the other one, CWM I think? I've never looked!
@berbatov93 you need a bit more patience and to read more things. Forums are awesome because you can get help from people all over the world but it rarely happens in real time.
stayawake said:
If you have Dual recovery, you are already running a custom recovery.
to enter the recovery menu whitout boot the system, you should:
Power On the device, and at the FIRST SONY screen, when the LED flashes, press volume up to enter TWRP
Click to expand...
Click to collapse
Its doesnt enogh to tap once volume up to enter to recovery ,when Sony logo shows he must tap few times volume up until notification led get purple color and phone goes in to recovery.This is procedure for Philzz Touch Recovery.
may i ask you something..did you unmount your memory card before you take it out?
if you want to have lastest version lolipop with root..
downgrade your phone to android lolipop 5.0.1..then follow this step http://forum.xda-developers.com/xperia-z1/general/root-xperia-running-lollipop-lb-ubl-t3123893..
then..
1. install busybox
2. turn on usb debugging and unknown source
3. find lolipop lastest version preroot...copy to your memory card (make sure to unmount it before you put it out) or just put the usb cable
4. install recovery (make sure to get lastest recovery.. can get it on nut.xperia-files.com/)
5. enter recovery then flash lastest pre root lolipop..
6. turn on your phone...
7.Good Luck
TA Partition Backup is for who want to unlock bootloader.. it backup DRM key which important for waranty.
Thank You, i hope this will help you
NamiDragneel said:
may i ask you something..did you unmount your memory card before you take it out?
if you want to have lastest version lolipop with root..
downgrade your phone to android lolipop 5.0.1..then follow this step http://forum.xda-developers.com/xperia-z1/general/root-xperia-running-lollipop-lb-ubl-t3123893..
then..
1. install busybox
2. turn on usb debugging and unknown source
3. find lolipop lastest version preroot...copy to your memory card (make sure to unmount it before you put it out) or just put the usb cable
4. install recovery (make sure to get lastest recovery.. can get it on nut.xperia-files.com/)
5. enter recovery then flash lastest pre root lolipop..
6. turn on your phone...
7.Good Luck
TA Partition Backup is for who want to unlock bootloader.. it backup DRM key which important for waranty.
Thank You, i hope this will help you
Click to expand...
Click to collapse
The DRM keys are unlikely to affect your warranty claim but they do other things including allowing your device to get OTA upgrades.
To unlock your bootloader you have to get an unlock code from Sony, to do that you give them your device details. So if you send it back for warranty and they look it up, I have no idea if they do, they'll see that you have unlocked your bootloader. Or at least got the code to do so, I doubt anyone gets the code without planing on using it.
Those DRM keys play a role in the Sony image processing for both the camera and the Bravia Engine. That is what you lose by unlocking the bootloader, warranty is not the major factor.
Hey
I had the same problem.
So what I did to solve this?
I did a factory reset > flash again flashable_D6502_23.4.A.0.546.zip > wipe dalvik >
And the problem was fixed.
Good luck
Updated for more serious reference. Hope this info helps you!
Procedure:
Once you have updated to Nougat, you would have to unlock your bootloader
The APK that unlock the bootloader works (Even though is marked as M version). (Remember that this will wipe your device!) For ULBL -> Version UnlockTool_2017_0803(android M) (FROM ASUS) https://www.asus.com/us/Phone/ZenFone-3-Zoom-ZE553KL/HelpDesk_Download/
Zenfone will reboot and you will able to see a new splash screen that informs you that your device is unlocked giving you boot options Don't press anything. (You will see this everytime you reboot). The next screen will show an erase process. Phone will reboot.
Once booted enable developer options and adb via usb.
You can find TWRP builds right here: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w (Special thanks to: @shakalaca) Use the latest one.
Go to fastboot mode and install TWRP. (fastboot flash recovery (nameoffile).img)
Let fastboot do it's magic, once you finish press volume buttons till you find reboot recovery press power button to select. It will boot again to the first splash. Do not press anything, let it work. It will boot TWRP in a whistle.
Once in TWRP make a backup. You know it's necessary, and will save your ass in case of a softbrick.
Flash latest magisk (Current Ver: 13.3) Magisk thread: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Reboot, check drawer for magisk manager, magisk and root should be enabled.
Voila. Safetynet test passed :good:
what version was twrp are you using and what steps did you take to get magisk to work.
smariob said:
So today finally I got my Asus Zenfone 3 Zoom. I couldn't contain myself to start playing with it.
My very first surprise was that the phone requested for an update. I've done it. I ended with a stock 7.1.1 AZ3Z.
This is my experience:
The APK that let you unlock bootloader works. (Remember that this will wipe your device)
After auto reboot I cheched safetynet. At this point test failed (Little bit obvious)
I was able to go to fastboot mode and install TWRP (The same you can find right here at the forum)
Let fastboot do it's magic, press volume buttons till you find reboot recovery. It will boot TWRP in a whistle.
Once in TWRP I made a backup. You know if necessary.
The next step was a crossfinger procedure. Just flashed latest magisk Beta (13)
Reboted checked for magisk manager on drawer.
It was there and root also. Enabled magiskhide, and voila. Safetynet test passed :good:
Hope this Info help you.
Click to expand...
Click to collapse
Do you know if this works with Android Pay?
magicmanfk said:
Do you know if this works with Android Pay?
Click to expand...
Click to collapse
It should work with it, im able to login intoy bank account with no problem with this method, I will give it a try for you though.
mr573162 said:
what version was twrp are you using and what steps did you take to get magisk to work.
Click to expand...
Click to collapse
magicmanfk said:
Do you know if this works with Android Pay?
Click to expand...
Click to collapse
It's twrp 3.1.0
It should work as it passes CTS profile and Basic Integrity I can't test it myself because I live in Mexico and Android Pay is not avialable here yet.
Will edit OP
Just a question as I'm having difficulty booting into TWRP.
My device is unlocked and when flashing TWRP using the command "fastboot flash recovery twrp.img" and trying to boot into it nothing happens other than my device going into the bootloader. I have tried flashing both the most recent TWRP 3.1.1 and 3.1.0 yet I keep on coming to the same problem. Can anyone provide help? thanks in advance.
GarGarStinks said:
Just a question as I'm having difficulty booting into TWRP.
My device is unlocked and when flashing TWRP using the command "fastboot flash recovery twrp.img" and trying to boot into it nothing happens other than my device going into the bootloader. I have tried flashing both the most recent TWRP 3.1.1 and 3.1.0 yet I keep on coming to the same problem. Can anyone provide help? thanks in advance.
Click to expand...
Click to collapse
Everytime you reboot the pone starts into boot loader. It has a countdown to boot into whatever is commanded.
Once you flashed succesfully the recovery img you just have to select option to boot recovery with vol keys and power.
Phone will reboot into bootloader agin let it boot on contdown (don't press any key)
Then it will boot into twrp.
Hello, on nougat i am trying to install the twrp, I downloaded the official bootloader release program (after installing the message "unlocked device") but trying to install the twrp via fastboot me by an error message. ... but I think the problem is the unlocking of the bootloader (if I turn the ze553kl in fastboot mode I see my device is "locked") ... there is another version of the bootloader release software? The one available on asus site would look for android M ... maybe there is one for Nougat? Thanxs
Wop. I used the M version apk on Nougat. It worked with no issues, the unlock of boot loader is successful when all the content of your smartphone is wiped.
For reference: https://www.youtube.com/watch?v=hg77b8o8Jk4 Min 1:29
Thank you! But running the software, does not run any wipe, it only displays an "unlocked" message without having to restart anything else. I also tried to make a "factory reset" and repeat lab process but the result does not change ...
TWRP tip!!
smariob said:
Go to fastboot mode and install TWRP. You can find TWRP and how to install it right here: https://forum.xda-developers.com/zenfone-3-zoom/how-to/twrp-zenfone-3-zoom-t3624551
:
Click to expand...
Click to collapse
If you follow that link and flash the recommended version, TWRP might load upside down and mirrored, impossible to use. I flashed the latest version from the MEGA link (3.1.1) and it was back to normal. Just a head's up for future reference, you might want to update your post.
---------- Post added at 09:39 PM ---------- Previous post was at 09:32 PM ----------
smariob said:
Go to fastboot mode and install TWRP. You can find TWRP and how to install it right here: https://forum.xda-developers.com/zenfone-3-zoom/how-to/twrp-zenfone-3-zoom-t3624551
:
Click to expand...
Click to collapse
If you follow that link and flash the recommended version, TWRP might load upside down and mirrored, impossible to use. I flashed the latest version from the MEGA link (3.1.1) and it was back to normal. Just a head's up for future reference, you might want to update your post.
Updated, never had mirror issues but is always better to have latest recovery.
Edit. Jimbo, I got an anwer from the source it notes: "please use 'fastboot flash recovery' instead of 'fastboot boot' to avoid up side down screen"
I've also tried installing from scratch with Asus flash tool, but I still can not unlock bootloader ... Anyone know if there is also an unofficial method for unlocking the bootloader?
@bizzino what model of Z3Z are you using?
Maybe Unlock bootloader app is intended for specific models... Let me do a little bit of research
Double posted... (Don't know for what reason this is happenning)
smariob said:
@bizzino what model of Z3Z are you using?
Maybe Unlock bootloader app is intended for specific models... Let me do a little bit of research
Click to expand...
Click to collapse
Ze553kl. WW_Z01H
bizzino said:
Ze553kl. WW_Z01H
Click to expand...
Click to collapse
Couldn't find another unlock tool than 2017_0803 ...
What info gives you fastboot mode?
smariob said:
Couldn't find another unlock tool than 2017_0803 ...
What info gives you fastboot mode?
Click to expand...
Click to collapse
Locked
Works just fine, thank you
But how would I go about setting the phone back to stock if needed in the future? (Removing Magisk, and replacing TWRP with the original recovery software).
@bizzino No news for you i wasn't able to find more info I'm sorry. Maybe change it for warranty? @subsector you should flash original recovery via fastboot and then sideload the stock rom
Back to Stock with @raystef66's Files
This guide used a method stemmed from paranoia. Now that we have decent flashable files everything is much simpler!
We'll be using raystef66's flashable TWRP files to go completely back to stock. At the end there's instructions if you want to lock your bootloader.
Be sure that you are on the latest TWRP version!
1) Files to Download:
- TWRP Flashable Bootstack/Stocksystem Image from here: Download Center. Download the latest BOOTSTACK and STOCKSYSTEM from there.
- If you want to lock the bootloader, also download the STOCK RECOVERY zip from the same stocksystem version that you downloaded. The flashable stock recovery zips are on the Factory Images Division, right above the TWRP flashable files.
- Magisk 15.2 (or latest), or SuperSU 2.79 (Latest not recommended ). If you will relock the bootloader, skip this part.
2) Installation
- Put all the files on the internal storage or SD card. Backup your important stuff from the internal storage, because you might need to format it!
- Go to TWRP. Wipe data, system and cache (don't format data though).
- Install the bootstack that you downloaded. Then install the stock system.
- If you will NOT relock the bootloader, install Magisk or SuperSU
- Reboot
If the phone asks for a password when it gets to the system, go to TWRP. It will ask for a password, just select Cancel. After you're on the main TWRP screen, select Wipe, then Format data, then type yes. After that, reboot.
3) 5 second screen removal / restore Fastboot
This is useful whether you're relocking the bootloader or not. Just go to raystef66's guide and follow it completely. After doing it your phone will have Fastboot (very good for softbricks and relocking), no 5 seconds screen (your phone will boot up faster) and it will be even closer to full stock.
4) ONLY FOR RELOCKING - Replace TWRP with Stock Recovery
Simply go to TWRP and flash the stock recovery file you downloaded. After that, enable OEM unlocking and USB debugging from the dev options, and then go to Fastboot and issue "fastboot oem lock".
@Choose an username... thanks for the credits.
you can return to stock in that way. you can reflash twrp with tool, allways checking bootloader still unlocked.
I allway update in this way, reboot to twrp, flash the recovery image, not a zip, its the same, but I make sure that the recovery correspond to the base version in my phone. after that, I reboot to system directly, update in the ota way, or the zip way, but from running android, rooted or not, and I dont have to wipe.
After update is done, the most important thing is leave the phone till it is completly booted, then you can reflash twrp with axon7tool again.
You dont need to root, you dont need anything to keep twrp. You only need to flash supersu or magisk if you use darkenfx zips. And if you do it, you have to backup wipe and restore cause you lose encryptation.
But thats all. I think stock rom its still the best, not in battery life, but in camera and bundled apps, It works perfectly, except, I have 2 bugs since allways, wake up with proximity sensor covered, and whatsapp online with app in background, I can live with that
I can re-lock bootloader after this process?
thanks for the guide.
Help Needed ! A2017g Bricked while trying to returning to stock
Hi, Please help me to get my Axon 7 in a working state. I was using Xenon HD Rom for A2017g Oreo. With twrp version as suggested in the guide.
I followed the procedure, installed the bootstack and then stock system B09
But when I tried to reboot, it said no OS Installed. Then I rebooted, and it was stuck at bootloader with no twrp and just the message as follows :
Android Recovery : ZTE/P996A04_N/ailsa_ii
7.1.1/NMF26V/20171120.101942
user/release-keys
Use volume up/down and power
and then certain other options in blue
Please help !
I also have a Problem.
I tried going back to stock from LOS 14.1. Now I am stuck on the 5 seconds screen, it won't continue.
The files I used were the Nougat B10 Files :-/
HansWursT619 said:
I also have a Problem.
I tried going back to stock from LOS 14.1. Now I am stuck on the 5 seconds screen, it won't continue.
The files I used were the Nougat B10 Files :-/
Click to expand...
Click to collapse
Enter the recovery, it should be the stock one (turn the phone off, then hold vol+ and power). Then download a stock B10 file (not the twrp flashable one) and install it from an SD card
No its not the stock one, its still TWRP.
I only flashed Bootstack and stock system (step 2). The reboot afterwards doesnt work
What do you mean by "a stock B10 file"? There are so many files types :-/
I am not quite sure what I should do now, do I have to do the EDL route? That one sounds confusing as well.
EDIT: I tried using B08 Files and now the reboot prompt in TWRP tells me there is no os installed.
Will I, like naveen09y, end up without TWRP if I reboot now?
HansWursT619 said:
No its not the stock one, its still TWRP.
I only flashed Bootstack and stock system (step 2). The reboot afterwards doesnt work
What do you mean by "a stock B10 file"? There are so many files types :-/
I am not quite sure what I should do now, do I have to do the EDL route? That one sounds confusing as well.
EDIT: I tried using B08 Files and now the reboot prompt in TWRP tells me there is no os installed.
Will I, like naveen09y, end up without TWRP if I reboot now?
Click to expand...
Click to collapse
Probably, so just don't. You should just wipe system and data, flash the bootstack, then the system. Also follow raystef's guide to "remove bootloader unlocked inscription"
I now managed to get the phone working with EDL flash of MM B10.
But I cant relock the bootloader :-/
Bascially my bootloader is gone so I cant reboot to it and do "fastboot oem lock".
Why is this such a hassle
HansWursT619 said:
I now managed to get the phone working with EDL flash of MM B10.
But I cant relock the bootloader :-/
Bascially my bootloader is gone so I cant reboot to it and do "fastboot oem lock".
Why is this such a hassle
Click to expand...
Click to collapse
You didn't follow my instructions. Follow raystef's removed unlocked bootloader inscription and you'll get fastboot back. You can do that with the phone on.
Don't relock it unless it's really necessary (i.e. warranty). If you're gonna sell it just follow that guide and don't relock, the 5 seconds screen will disappear and it'll look like it's locked
I cant follow the guide because I can't access the bootloader...
Also the TWRP files in https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379 this guide (step 6) are no longer accessible.
HansWursT619 said:
I cant follow the guide because I can't access the bootloader...
Also the TWRP files in https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379 this guide (step 6) are no longer accessible.
Click to expand...
Click to collapse
What? Lol
First of all - you are basically installing the bootloader with raystef's guide, so I have no idea why you want to enter it...
You have to enter TWRP and follow the guide from there.
The guide from Controllerboy is basically the same guide but it also has instructions on other things (i.e. unlock etc.). I don't know what you are trying to accomplish with it. Use EDL Tool by djkuz if you want to install TWRP (it is explained there how to do that).
Phone was rooted with Magisk 16, I was on AEX Android 8.1 ROM. I'm trying to return to stock and relock bootloader.
I wiped everything, I flashed A2017G-N-B10-bootstack and A2017G-N-B10-stocksystem from "TWRP flashable Bootstack/Stocksystem Images" section. Booted to system and now phone is stuck on the ZTE POWERED BY android boot screen. 5 minutes there. Is it normal?
Edit: Got tired of waiting and kept pressing the power button. After doing so, the phone reboots but same thing. And I can't access TWRP with VOL INCREASE + POWER BUTTON.... VOL DECREASE + POWER BUTTON takes me to Factory Test Mode.
aLexzkter said:
Phone was rooted with Magisk 16, I was on AEX Android 8.1 ROM. I'm trying to return to stock and relock bootloader.
I wiped everything, I flashed A2017G-N-B10-bootstack and A2017G-N-B10-stocksystem from "TWRP flashable Bootstack/Stocksystem Images" section. Booted to system and now phone is stuck on the ZTE POWERED BY android boot screen. 5 minutes there. Is it normal?
Edit: Got tired of waiting and kept pressing the power button. After doing so, the phone reboots but same thing. And I can't access TWRP with VOL INCREASE + POWER BUTTON.... VOL DECREASE + POWER BUTTON takes me to Factory Test Mode.
Click to expand...
Click to collapse
Try this.
Oki said:
Try this.
Click to expand...
Click to collapse
Yes, thanks. I already had seen it some minutes ago. It's so convenient that you posted this guide today lol
I want to flash stock rom from RR Nougat. I have installed latest twrp, flash bootstack and then stock system. After that I flash supersu 2.79. But when I press reboot system it say no OS installed
Willchi said:
I want to flash stock rom from RR Nougat. I have installed latest twrp, flash bootstack and then stock system. After that I flash supersu 2.79. But when I press reboot system it say no OS installed
Click to expand...
Click to collapse
The best way to return to stock is via EDL, for example MiFlash or EDL tool. If you have an U, then DrakenFX's zips can do that, it happened to me already. Usually G zips like raystef's work just fine.
Try using Magisk instead of SuperSU, just in case. Use 16.7
@Choose an username...
Thanks for posting this.
Credits to all concerned a big thumbs up.
I do however feel that there are to many versions of the Axon 7 packages and I can see why people are ending up with boot issues etc.
Syberclone said:
@Choose an username...
Thanks for posting this.
Credits to all concerned a big thumbs up.
I do however feel that there are to many versions of the Axon 7 packages and I can see why people are ending up with boot issues etc.
Click to expand...
Click to collapse
what
you do realize this guide is older than a year right?
Yeah, its all good
I have this device rooted with magisk BUT cant find way to properly port a qualcomm twrp from similar devices i just need help to get started with custom recovery if i can get one to boot i might be able to fiqure out the rest if any "Bugs" are found thru out the custom recovery. any help would be appericated.
below is a stock image of recovery and boot if needed
both images were from a " .Tar " file. I then extracted the file and got the recovery and boot in " .img.lz4 " format and then i converted them to " .img " only for easy access to edit ETC.
Android Version : 10
Current Firmware Version : A115MUBU1ATC2
Chipset : msm8953
Encryption State : encrypted
#System as Root
Uses an A/B operating System
https://drive.google.com/drive/folders/1mYYqvNgAXAxmiBH8ZDmbnoKMma4CUR12?usp=sharing
Why not compile a matching TWRP by yourself?
Look inside here.
@ jwoegerbauer i can give a try but have no experiences when it comes to makin a custom recovery.
ᐯerified Developer said:
I have this device rooted with magisk BUT cant find way to properly port a qualcomm twrp from similar devices i just need help to get started with custom recovery if i can get one to boot i might be able to fiqure out the rest if any "Bugs" are found thru out the custom recovery. any help would be appericated.
below is a stock image of recovery and boot if needed
both images were from a " .Tar " file. I then extracted the file and got the recovery and boot in " .img.lz4 " format and then i converted them to " .img " only for easy access to edit ETC.
Android Version : 10
Current Firmware Version : A115MUBU1ATC2
Chipset : msm8953
Encryption State : encrypted
#System as Root
Uses an A/B operating System
https://drive.google.com/drive/folders/1mYYqvNgAXAxmiBH8ZDmbnoKMma4CUR12?usp=sharing
Click to expand...
Click to collapse
Yea, im also looking for a way to get some sort of custom recovery on the exact same device. My advice is (if you cant build your own version of twrp) to just wait for some devs to release something for it. The galaxy a11 is a very new device so we'll just have to wait it out.
Edit: So I followed a tutorial here (https://www.youtube.com/watch?time_continue=40&v=MyxGZbCuxDQ&feature=emb_logo) and i created this (https://filebin.net/u3yww2cyajktm043). IT MAY OR MAY NOT WORK!!! USE IT AT YOUR OWN RISK!!!!
what model number is yours? i have the one from boost its the sm-a115u and it seems the toggle for oem unlock is not in my dev settings on my phone
ninjakira said:
what model number is yours? i have the one from boost its the sm-a115u and it seems the toggle for oem unlock is not in my dev settings on my phone
Click to expand...
Click to collapse
You can put the device into download mode and unlock the bootloader from there...
I'm currently stuck on this device trying to get it to unlock the boot loader. I've ticked OEM unlock but when I get into download mode (adb reboot download) I'm not getting any option to unlock the boot loader there. I'm also not able to get into download mode with any key commands. Any ideas here?
I've heard you power off, then hold volume up and down when you plug in a data cable. Haven't tried it yet, I'm on the a115u t-mobile variant. I can get to what it calls download mode, which looks to be fastboot and NOT the standard samsung blue screen download mode. Just boot to recovery and select reboot to bootloader. I do not have oem unlock in my dev settings, but I'll see if I can fastboot oem unlock when I get back to my laptop.
flash sm-a115u1 version firmware first. gives you oem unlock option. obviously toggle on and adb debugging. power off the phone. hold both volume buttons and insert usb cable. it will look like the normal blue download warning screen but read it carefully. it says long press volume up to unlock bootloader. it works. it will go black. release volume up and next it will ask you to confirm. choose yes. it will reboot and erase. after skipping thru set up enable dev options again and you will see oem toggle greyed out with a caption "bootloader already unlocked". thats as far as ive gotten. because now im like "what now?" i need a custom recovery file to flash to the device. any help with that out there? so now that the bootloader is unlocked can i install magisk to root and if so after that how can i network unlock? any help would be greatly appreciated. also looking for any custom roms that are available for this a11(2020). seems like a decent phone.thanks.
Situation:
You can build your TWRP it's very easy. Or get compiled version from A10 and patch your system.
As result you'll get a bootloop.
Why?
Samsung had f****d you up and give you a SECURE BOOT that's not possible to remove by bootloader unlock. If you're install wrong signed recovery loader will said to you:
1st something is going wrong and signatures are mismatched, lete wipe your phone!
Ok. You jad solved that and not wiped your phone.
2nd hmm, signatures still mismatched I'll not boot and go in ***!
Result:
Untill someone will not break this Qualcomm Secure Boot you'll not able to install custom OS or TWRP or any other good stuff.
Is there any updates that can be flashed with stock recovery
griha41 said:
Situation:
You can build your TWRP it's very easy. Or get compiled version from A10 and patch your system.
As result you'll get a bootloop.
Why?
Samsung had f****d you up and give you a SECURE BOOT that's not possible to remove by bootloader unlock. If you're install wrong signed recovery loader will said to you:
1st something is going wrong and signatures are mismatched, lete wipe your phone!
Ok. You jad solved that and not wiped your phone.
2nd hmm, signatures still mismatched I'll not boot and go in ***!
Result:
Untill someone will not break this Qualcomm Secure Boot you'll not able to install custom OS or TWRP or any other good stuff.
Click to expand...
Click to collapse
my a115u is stuck on load screen ,,after flash root trying to get bit un stuck ?????
ugg frustrating
sdell said:
my a115u is stuck on load screen ,,after flash root trying to get bit un stuck ?????
ugg frustrating
Click to expand...
Click to collapse
What's a point? Unpack firmware's AP_ file, extract boot.img, patch it through magisk, and flash through odin. But where in that thread header did you found the install root?
I want to remind you that recovery is bot a root part. That's why root thread and TWRP threads are separated.
griha41 said:
What's a point? Unpack firmware's AP_ file, extract boot.img, patch it through magisk, and flash through odin. But where in that thread header did you found the install root?
I want to remind you that recovery is bot a root part. That's why root thread and TWRP threads are separated.
Click to expand...
Click to collapse
cause i was new ..lol didnt know ..and still trying to understand it all but thqnk you for reply
sdell said:
cause i was new ..lol didnt know ..and still trying to understand it all but thqnk you for reply
Click to expand...
Click to collapse
Ahh I see. Sorry then.
You shall do that way. Find current fiware for your device, download it through fine software.
A result you will get 5 files with .zip extension.
You need to unpack file with AP_ prefix, i suggest you to use 7zip for that stuff. From file you need took off the boot.img.
Then boot.img you shall pack into archive.tar,
When you've done, down load the Magisk apk from github and install on your phone. Move your jew archive to phone memory/diwnload folder and start the Magisk, make patching of kenel, as result you'll receive the magisk_patched.tar, copy that file to your pc and start the Odin, place that archive in AP slot and flash it.
PROFIT!
But I want to warn you in android 10 and up there root and kernel system are different, now system is booting from super.img, and partition /,/system and etc are RO, so through the root you'll not able to change anything in system it would be wiped on next system restart.
it started with calyxOS then i tried Paranoid Andriod and now i am trying RiceDriod.
Specifically it happens trying to go into recovery mode to install updates via adb sideloading but it just takes me to the google screen then the "your devices bootloader is unlocked" warning.
I just flashed stock using andriod flash tools and it worked fine. not sure why it wont work for the others.
catcatjpg said:
it started with calyxOS then i tried Paranoid Andriod and now i am trying RiceDriod.
Specifically it happens trying to go into recovery mode to install updates via adb sideloading but it just takes me to the google screen then the "your devices bootloader is unlocked" warning.
I just flashed stock using andriod flash tools and it worked fine. not sure why it wont work for the others.
Click to expand...
Click to collapse
You have to flash a custom recovery so that you can flash custom ROMs.
Lineage OS has a up to date collection for device specific recoveries. However, you have to check the compatibility of them with the ROM you are intended to flash.
You should read the OP of that ROM more carefully regarding the compatibility issue.
aimsjahan said:
You have to flash a custom recovery so that you can flash custom ROMs.
Lineage OS has a up to date collection for device specific recoveries. However, you have to check the compatibility of them with the ROM you are intended to flash.
You should read the OP of that ROM more carefully regarding the compatibility issue.
Click to expand...
Click to collapse
I do flash the custom recovery so I can flash the ROM. I never had an issue before but now I do even though I have done everything correctly.
How do I clear cashe partition and dalvik cashe? The rest of the steps I have done but have not worked unfortunately. even with the different roms.
Do you have a visual of this? Pixel 6 does not have a physical home button when powered off haha. It would also help just for better understanding what to do
nothings working so far guess ill stick with graphene until i get a new phone or a solution pops up
catcatjpg said:
Do you have a visual of this? Pixel 6 does not have a physical home button when powered off haha. It would also help just for better understanding what to do
Click to expand...
Click to collapse
To manually boot recovery on a custom rom just hold power button down , keep holding it down and once your screen goes black hold volume down till you are in bootloader/fastboot mode, then use volume to select recovery and hit power. That should get you in recovery on custom roms. Or you can plug in to a PC with adb and enable USB debugging and dev options on device, disable screen lock and type: sudo adb devices (for Linux ) and when the box pops up on your phone check mark it really quick. Now your device can have commands sent to it. If on a custom rom from cli type: sudo adb reboot recovery or sudo adb reboot bootloader then use volume keys to go to recovery and power to select it.
The best way to get out of a bootloop is hold power and volume down until you are in bootloader/aka fastboot mode then execute the ./flash-all.sh script that's in factory image and let it flash and wipe your device. You can always sideload a rom again but the factory image script will get everything to normal. There are tons of videos on YouTube about flashing device's. Everything changed a few years ago when Google started making android A/B partition devices but if you check out YouTube just do a quick search for whatever it is and more than likely you'll find what you're looking for there. Lots of pixel 6 videos!!!
Please explain your "exact " installation technique step by step. The more details the better the answers you'll get. What rom are you installing and exact steps you are doing to get in a boot loop.. While there are some highly intelligent people here nobody can read minds. Every detail helps to get a solution that works. Must be specific.. For me I rarely have issues but i don't flash nearly as often as I used to but when I have had a loop I hold power and volume down then from bootloader screen plug up to PC and I flash factory image using the flash-all.sh script that comes in factory image. Check out YouTube for visuals. Lots of good videos there.
This will hopefully provide more information on my situation
Currently I am trying to install RiceDroid for the pixel 6.
How I am in stalling it is I extract the images from the payload bin using a guide. Get the vendor boot image. Flash it with 'fastboot flash vendor_boot 'path/to/vendor_boot.img' then I try to boot into recovery which doesn't work it loads into the the warning screen then to the Google boot up screen but I never get to the Andriod 'no command' screen I only get taken back to the warning screen then back to the boot screen again untill I manually boot into bootloader again (power button and volume down) and flash my stock firmware.
Other Roms are not working for me either and it started happening after I tried to flash calyxOS and that failed. Now I can't even flash lineageOS or Evolution X rom only web flashing with GrapheneOS and Android Flash Tool can successfully flash my device.
im not sure what i did but things are working again