Hey guys so I've been killing myself just trying to find ways to get my newly rooted xperia z2 phone to boot into recovery mode.
Essentially I followed this guide to the bone and successfully rooted my phone --> http://forum.xda-developers.com/xperia-z2/development/stock-d6502-23-1-0-726-complete-guide-t3085893
The big problem is whatever I do, no matter the selection of recovery apps(quickboot, twrp manager, etc.) I install I can never get back into recovery mode, my phone turns off and goes into normal bootup, even when I try to do manual recovery mode the light indicator on top doesn't show up and the phone ends up starting normally.
I have factory resetted my phone a couple of times to have a fresh start each time I try something new but nothing seems to work.
On top of that SDFix and it's other variants does not work on my phone, so I can't install any apps on my micro sdcard. I'm really at a loss for what to do here(been at it for 3 days now) so I'm seeking help.
I'm not sure what information to give but I'll try to give as much details as I can about my situation, I'm really desperate to have recovery and my sd card working normally as I am currently very limited with the stuff I want to do on my phone. :crying::crying:
Info:
Model Number: D6503
Android Version: 5.0.2
Kernel Version: 3.4.0-perf-g72984dd [email protected] #1
Build Number: 23.1.A.0.726
SuperSU Installed
Phone is factory reset and rooted.
No other mods & apps installed aside from pre-installed apps and SuperSU
I would very much appreciate it if someone can help me with this problem, thank you!! :cyclops::laugh:
I can't access recovery mode either. Led light doesn't come on when I turn on the phone as well.
I was thinking abt rooting my phone but nvm now.
saedted said:
I can't access recovery mode either. Led light doesn't come on when I turn on the phone as well.
I was thinking abt rooting my phone but nvm now.
Click to expand...
Click to collapse
I think it doesn't matter whether your phone is rooted or not for you to be able to access recovery mode(not sure about this to be honest). I know rooting(and all this headache) is worth it for any android phone especially the xperia z2 which is why I'm hellbent on getting this fixed.
I wanna install cyanogen mod but those two things I've mentioned in my first post is really limiting what I can do with this phone sadly.
disenx34 said:
I think it doesn't matter whether your phone is rooted or not for you to be able to access recovery mode(not sure about this to be honest). I know rooting(and all this headache) is worth it for any android phone especially the xperia z2 which is why I'm hellbent on getting this fixed.
I wanna install cyanogen mod but those two things I've mentioned in my first post is really limiting what I can do with this phone sadly.
Click to expand...
Click to collapse
Sony devices don't have recovery partition, either unlock your BL (and lose DRM keys) and flash a kernel with a built-in recovery , or keep your BL locked and install nut's dual recovery (you need a rooted system before installing).
All the info needed for both options is here on xda but i think you guys need to read a lot more before you start messing with your devices....
ptmaniac said:
Sony devices don't have recovery partition, either unlock your BL (and lose DRM keys) and flash a kernel with a built-in recovery , or keep your BL locked and install nut's dual recovery (you need a rooted system before installing).
All the info needed for both options is here on xda but i think you guys need to read a lot more before you start messing with your devices....
Click to expand...
Click to collapse
I already did everything I possibly could think of (i.e. unlocked bootloader through sony website, rooted, etc.) like I mentioned in the OP, I actually just recently discovered(like 15 minutes ago) that apparently there's this thing called Sony RIC and that's what's disabling me from installing anything on the system and limiting what I can do with my phone because everything(sd card + system folders) are read only and not write-able.
I found out from this thread (http://forum.xda-developers.com/xperia-z2/general/4-4-4-sony-ric-killer-t2953141/page3) that there's no updated version of 'Sony RIC KILLER' for lollipop version 5.0.2. so I guess I'm stuck. I tried installing TWRP recovery through TWRP manager on my phone and it wouldn't even get to the recovery mode.
I'm gonna keep trying other variants of dual recoveries till one successfully works, I'll also try your suggestion of flashing a kernel with a built-in recovery that's one area I haven't dabbled in yet, this is my first android device so I'm still figuring out where the red line is on everything. :laugh::good:
disenx34 said:
I already did everything I possibly could think of (i.e. unlocked bootloader through sony website, rooted, etc.) like I mentioned in the OP, I actually just recently discovered(like 15 minutes ago) that apparently there's this thing called Sony RIC and that's what's disabling me from installing anything on the system and limiting what I can do with my phone because everything(sd card + system folders) are read only and not write-able.
I found out from this thread (http://forum.xda-developers.com/xperia-z2/general/4-4-4-sony-ric-killer-t2953141/page3) that there's no updated version of 'Sony RIC KILLER' for lollipop version 5.0.2. so I guess I'm stuck. I tried installing TWRP recovery through TWRP manager on my phone and it wouldn't even get to the recovery mode.
I'm gonna keep trying other variants of dual recoveries till one successfully works, I'll also try your suggestion of flashing a kernel with a built-in recovery that's one area I haven't dabbled in yet, this is my first android device so I'm still figuring out where the red line is on everything. :laugh::good:
Click to expand...
Click to collapse
On stock rom / kernel only nut's dual recovery will work. IT will also disable sony ric for you in the process. check here: http://forum.xda-developers.com/showthread.php?t=2261606
On custom kernel you have to choose a kernel with the recovery you want and flash that (don't forget to unlock BL before or you'll end up with softbrick). Recovery managers won't work as there is no recovery partition on your device...
install latest version of nuts recovery for z2 and install it after finish phone well reboot into recovery
Then dont update busybox it well break recovery
Related
Hi!
I'm starting this thread because I can't find anything in the whole atrix subforum that matches my situation.
I've purchased an Atrix last month (even when sweared that wouldn't buy an motorola again since the milestone lack of support fiasco) and I'm very happy with the stock rom so far (in fact, back when I bought the milestone, I made the first battery charge and then fashed the hell out of it ).
Now I've sucessfully rooted my atrix and wish to install a custom recovery that allow me to backup my current flash and start testing things out, it's possible with a locked bootloader? In many post there are indications that ROM Manager can flash a custom recovery with only root access, but doesn't clarify wether a unlocked bootloader is necesary...
The whole point is being able to recover the original state of the phone when things get really mess up, (for the moment) I don't pretend to flash custom firmware.
Other question: When I rooted, I installed busybox, why? dunno (and this is my first mistake) but since then I noticed a longer boot time (about 30-40 seconds more). when tried to unninstall it , the app (busybox free) claims that unninstalling it will bootloop my device...
so far, thes are my concerns
this are my specs:
Atrix MB860 (made in Tierra del Fuego, Argentina: often reffered as the "Atrix Fuego" don'tknow if there is any difference with the "standard" atrix appart of this being 3g and not 4g ) Stock 2.3.6 Claro AR rom, rooted, 8gb ext-sd
Thanks for reading and sorry for my bad english!!
here is some info: http://forum.xda-developers.com/showthread.php?t=1262266
But in short, the locked bootloader insures that the boot partition (kernel), partition table and recovery are all signed by Motorola. Note that this doe NOT include the system partition which is all some ROMs need to flash.
So some ROMs can, and some can not be flashed and used while the bootloader is locked.
Alas, CWM recovery (or any other custom recovery) can NOT be used without an unlocked bootloader.
[Note, a rooted phone can INSTALL CWM recovery, but the bootloader will not allow it to run]
There is a decent thread on installing an unlocked bootloader and then a real recovery over in the ATRIX/general section. I would recomend either doing that or just leaving things alone
Hey, I did the same thing. Just install Titanium Backup. With this app you can force uninstall busybox. Then you are back to normal. Good luck.
exwannabe said:
here is some info: http://forum.xda-developers.com/showthread.php?t=1262266
But in short, the locked bootloader insures that the boot partition (kernel), partition table and recovery are all signed by Motorola. Note that this doe NOT include the system partition which is all some ROMs need to flash.
So some ROMs can, and some can not be flashed and used while the bootloader is locked.
Alas, CWM recovery (or any other custom recovery) can NOT be used without an unlocked bootloader.
[Note, a rooted phone can INSTALL CWM recovery, but the bootloader will not allow it to run]
There is a decent thread on installing an unlocked bootloader and then a real recovery over in the ATRIX/general section. I would recomend either doing that or just leaving things alone
Click to expand...
Click to collapse
That's what I thought.... So at least for a while, let's leave things just like they are right now
Very Interesting thread, just got answered a couple extra questions D
chrism.brunner said:
Hey, I did the same thing. Just install Titanium Backup. With this app you can force uninstall busybox. Then you are back to normal. Good luck.
Click to expand...
Click to collapse
It sounds logical, since busybox wasn't installed in the first place... But the bootloop message is scary as hell (I think it is meant to be) Will give TiBo a try...
Hey guys! Unfortunately I bricked my new HTC Desire 626s while fiddling around with xposed for lollipop after successfully rooting the phone and installing cyanogen recovery. I think if I flash the stock rom on the phone through either adb or cyanogen recovery I can unbrick it, but I have been unsuccessful in finding this file on the internet. Would anyone care to give me a link or upload the stock firmware/rom of this phone? It would really help me out, thank you!
You have to make sure the firmware is the same version or newer than the one currently on the phone as well as which carrier or region the phone is from. Without that, can't provide the correct file to download.
es0tericcha0s said:
You have to make sure the firmware is the same version or newer than the one currently on the phone as well as which carrier or region the phone is from. Without that, can't provide the correct file to download.
Click to expand...
Click to collapse
Umm.. Okay so I guess I'll give you my phone's info? WAIT DOES THIS MEAN YOU CAN PROVIDE A DOWNLOAD!? IM SO EXCITED, UH OK HERE
- HTC Desire 626s
- Metro PCS USA
- Current firmware version : 1.06.1550.7
ANYTHING ELSE?? IF YOU CAN GIVE ME THAT DOWNLOAD LINK, MY MOM WONT KILL ME:crying::crying::crying: (she's really pissed :laugh Thank you btw!
Was just thinking about this...if you soft bricked after attempting to install Xposed, and nothing else, you should be able to get out of it by flashing the xposed uninstaller zip. If that does not work, stay tuned to this thread http://forum.xda-developers.com/desire-626/help/htc-desire-626s-root-recovery-t3169169 as there are some others at the end of the thread in a similar predicament. It does not appear that there is an official RUU yet for the Metro version, only the T-Mobile version, and they are not compatible. Just try the uninstaller zip first because that would be the easiest thing to try and should only take a couple of minutes.
es0tericcha0s said:
Was just thinking about this...if you soft bricked after attempting to install Xposed, and nothing else, you should be able to get out of it by flashing the xposed uninstaller zip. If that does not work, stay tuned to this thread http://forum.xda-developers.com/desire-626/help/htc-desire-626s-root-recovery-t3169169 as there are some others at the end of the thread in a similar predicament. It does not appear that there is an official RUU yet for the Metro version, only the T-Mobile version, and they are not compatible. Just try the uninstaller zip first because that would be the easiest thing to try and should only take a couple of minutes.
Click to expand...
Click to collapse
I tried this before my phone got ****ed and it worked:good:! If you can help me dude that'd be great. After uninstalling or changing some stuff in priv-app on my HTC Desire 626s, when I rebooted, it would just stay in a boot loop with the optimizing app message. Any ideas?
What did you uninstall? I would ask for those apps in that thread and use a flashable zip and install via TWRP. You might also try clearing caches and/or resetting the phone again. It DOES take a long time to optimize the apps after wiping stuff as well, so sometimes it is a matter of being patient.
This is why I ALWAYS recommend to freeze apps vs uninstalling. Uninstalling them does not get you any usable space back, so there is no benefit, but it can cause issues if you do need the apps, as you can see...
es0tericcha0s said:
What did you uninstall? I would ask for those apps in that thread and use a flashable zip and install via TWRP. You might also try clearing caches and/or resetting the phone again. It DOES take a long time to optimize the apps after wiping stuff as well, so sometimes it is a matter of being patient.
This is why I ALWAYS recommend to freeze apps vs uninstalling. Uninstalling them does not get you any usable space back, so there is no benefit, but it can cause issues if you do need the apps, as you can see...
Click to expand...
Click to collapse
I believe I uninstalled the dialer and its service in an attempt to replace them with the stock lollipop ones. How do you install TWRP on this phone? My mom has the same phone and its also rooted but hers actually works so I was thinking since TWRP has a nandroid backup setting, I could simply do a nandroid backup on hers and flash it on to mine to see if it will boot up. What do you think? And for the optimizing apps thing, it would finish optimizing, say starting apps, reboot and then optimize again and repeat. Thanks for the help btw, I really hope we can fix this.
You have to unlock the bootloader @ htcdev.com and use fastboot to install TWRP. And yes, that would work, as long as they are on the same software update. Know that when you unlock the bootloader, it will automatically wipe the phone, so make sure she has everything backed up to Google, the PC, etc.
es0tericcha0s said:
You have to unlock the bootloader @ htcdev.com and use fastboot to install TWRP. And yes, that would work, as long as they are on the same software update. Know that when you unlock the bootloader, it will automatically wipe the phone, so make sure she has everything backed up to Google, the PC, etc.
Click to expand...
Click to collapse
Do you have the TWRP recovery file for me to download?
I'm afraid I'm a bit confused... How did you install Xposed and the Uninstaller without a custom recovery? Upon further searching, there doesn't appear to be a version of TWRP for your phone that I could find. Just figured you already had one. You must be on Kit Kat and not Lollipop?
es0tericcha0s said:
I'm afraid I'm a bit confused... How did you install Xposed and the Uninstaller without a custom recovery? Upon further searching, there doesn't appear to be a version of TWRP for your phone that I could find. Just figured you already had one. You must be on Kit Kat and not Lollipop?
Click to expand...
Click to collapse
I installed Cyanogen recovery before flashing Xposed and the uninstaller. I thought you had the TWRP recovery img for my phone which is why I asked. I believe some developers are working on a Clockworkmod recovery for this phone which is basically the same thing as TWRP recovery, right? Anyways I guess I just have to wait until that comes out, but I was wondering if anyone who somehow got a hold of the stock rom could upload it for us to use. It would be really helpful
ClockWorkMod is the recovery that Cyanogen uses. That is able to perform nandroid backups as well.
You have to unlock the bootloader, then if you messed up your stock rom and you've updated it to something newer than what Samsung gives for a stock recoverable rom, you must first use the tmobile vers, let it fail, and then use metropcs vers.
If you messed up recovery or anything it will all go back to stock after flash.
Next just copy superuser zip file to phone, go to download mode and adb flash cyanogen recovery img. Then reboot to recovery, choose to flash update, and find the superuser. zip and flash it, voila.
https://www.mediafire.com/?8o6qtn7hlsec0zj,yqbbzb7divlcvvc
Kitkat, anyone?
Does anybody have a stock KitKat ROM for this device? I'd like to try to bypass the FRP, but am stuck on what must be either a marshmallow or lollipop ROM.
What carrier do you have?
I can send you a backup of the FRP.img for Marshmallow or for lollipop.
You can dd if= flash it to your device and you should be all good.
I am looking for any older roms for these devices too.
Seems like not too many people save the RUU and then HTC only releases the newest.
I got lollipop and marshmallow that's it.
But like i said we can fix the frp partition.
Issue is fixed
BigCountry907 said:
What carrier do you have?
I can send you a backup of the FRP.img for Marshmallow or for lollipop.
You can dd if= flash it to your device and you should be all good.
I am looking for any older roms for these devices too.
Seems like not too many people save the RUU and then HTC only releases the newest.
I got lollipop and marshmallow that's it.
But like i said we can fix the frp partition.
Click to expand...
Click to collapse
I ended up fixing it using some ADB commands as noted in the "Well, I may have found..." thread. It'll be nice to have this phone out of my life. The day I had to spend with it was two days too many.
I have an Xperia Z5 Compact with German T-Mobile factory ROM, which is not too much use to me coz I don't live in Germany or use T-Mobile. I wanted to flash a stock ROM with no bloatware. Root probably later, I'd like to use the phone a bit first. It isn't simlocked btw, and was OTA updated to Marshmallow before I tried anything.
So I unlocked the bootloader, then flashed the recovery and boot images from the first post here without noticing they are old versions and further down the thread they are updated. Now I can get into TWRP recovery, but when I try to start the phone normally it freezes on the pink T-Mobile splash screen. Recovering from my Nandroid backup doesn't help... coz I only created it from within TWRP after I did this flash.
I can't use Flashtool, it says USB debugging is turned off. I guess what I flashed before has reset that to off. I tried following the Lollipop instructions here to turn it back on using adb, but I can't pull the file mentioned there. Anyone got instructions for doing the same on Marshmallow please?
Not exactly panicking here, but I really wish I practiced on my old HTC Hero before jumping in blind....
moyabrit said:
I have an Xperia Z5 Compact with German T-Mobile factory ROM, which is not too much use to me coz I don't live in Germany or use T-Mobile. I wanted to flash a stock ROM with no bloatware. Root probably later, I'd like to use the phone a bit first. It isn't simlocked btw, and was OTA updated to Marshmallow before I tried anything.
So I unlocked the bootloader, then flashed the recovery and boot images from the first post here without noticing they are old versions and further down the thread they are updated. Now I can get into TWRP recovery, but when I try to start the phone normally it freezes on the pink T-Mobile splash screen. Recovering from my Nandroid backup doesn't help... coz I only created it from within TWRP after I did this flash.
I can't use Flashtool, it says USB debugging is turned off. I guess what I flashed before has reset that to off. I tried following the Lollipop instructions here to turn it back on using adb, but I can't pull the file mentioned there. Anyone got instructions for doing the same on Marshmallow please?
Not exactly panicking here, but I really wish I practiced on my old HTC Hero before jumping in blind....
Click to expand...
Click to collapse
use adb and flash androkernel to fix the incorrect kernel that you installed. you can do that by renaming it boot.img and sending the command fastboot flash boot boot.img
i haven't messed with androplus in a while but if you were on marshmallow i believe v34 will work and if you were on the absolute newest marshmallow i think its v35 off the top of my head.
fyi you dont need usb debugging on to use flashtool, you can get into fastboot mode with no rom at all installed.
Kogan agora 6 plus.
android 6.0
i tried, kingoroot, towelroot and kingroot.
All failed, i am now asking around the community on a way to root it for various reasons.
will provide more info about it when it charges.
edit:
Model number: Kogan Agora 6Plus
android version: 6.9
baseband version: MOLY.LR11.W1539.MD.MP.V10.P6, 2016/07/29 14:46
kernal version: 3.18.22
Build number: M1_PLUS_N_AU_KG_M_MT6755_65U_V1.8
custom build version: alps-mp-m0-mp7-v1.5_mlt6755.65u.m_p11
In the developer options, there is a toggle called OEM unlocking. Try toggling it and try rooting again.
I got my device rooted... it's an algerian clone of your device and you can check by yourself (google "iris next e"
At first, I thought that this device is unrootable as I tried every rooting sofrware out there and no one sorked, then I tried some adb methods and neither worked also, but then I tried the last bullet in my gun and that worked
I repacked a TWRP recovery to be compatible with the device and rooted systemlessly with supersu... now I even have exposed and magisk working
If you can make the recovery yourself then do it, if you don't I can share my repacked TWRP with you and show you step by step what to do
On the technical side, what I discovered was that there is no adbd neither adb bridge in stock recovery mode (I even looked for it in the ramdisk and found out it's not loaded) so the repacked TWRP recovery (I got the source TWRP from a Xiaomi m3 forum, the M3 has the same SoC -mt6755- which made it easy to port), I booted the recovery from fastboot and it worked like a charm
p.s: if you dont know what all I said means, don't try it, you might brick your phone!! and please don't try the m3 recovery without porting it cause it will brick your phone for sure!!
I can confirm they device looks identical, I am not very familiar with repacking TWRP, but would be appreciative if you were happy to share.
Jimmy Mossiba Floyd said:
I got my device rooted... it's an algerian clone of your device and you can check by yourself (google "iris next e"
At first, I thought that this device is unrootable as I tried every rooting sofrware out there and no one sorked, then I tried some adb methods and neither worked also, but then I tried the last bullet in my gun and that worked
I repacked a TWRP recovery to be compatible with the device and rooted systemlessly with supersu... now I even have exposed and magisk working
If you can make the recovery yourself then do it, if you don't I can share my repacked TWRP with you and show you step by step what to do
On the technical side, what I discovered was that there is no adbd neither adb bridge in stock recovery mode (I even looked for it in the ramdisk and found out it's not loaded) so the repacked TWRP recovery (I got the source TWRP from a Xiaomi m3 forum, the M3 has the same SoC -mt6755- which made it easy to port), I booted the recovery from fastboot and it worked like a charm
p.s: if you dont know what all I said means, don't try it, you might brick your phone!! and please don't try the m3 recovery without porting it cause it will brick your phone for sure!!
Click to expand...
Click to collapse
ok then: what you'll need to download is:
1. adb minimal drivers (you can find it here on xda)
2. supersu latest systemless zip (2.79 I think it's the latest version) after you've downloaded it, put it in the device's internal memory (yeah just right-click the zip file, chose "send-to" then chose your device)
3. the recovery file which is compressed in zip (unzip it and put the img file in the folder where you've installed adb - c:\adb\ )
after that, when you've got everything set, restart your device in fastboot mode: shut down the phone then put it on by hitting the power button and volume up button.. you're gonna have a three-choices menu that you're gonna scroll with the volume up button, when you've got the cursor on "fastboot" press the volume down button... the device will be put on fastboot mode.
Now back to your pc, open a command prompt, then brows to c:\adb. When you have your command prompt on adb, write this (including the quotes):
fastboot boot "TWRP 3.0.2 by Jemmini.img"
Hit enter... wait a little (while the recovery boots) and then... voila!! all you've got to do is to flash the supersu zip through the recovery and reboot: congratulations your device is now rooted
p.s: I suggest you make a full backup for all the partitions from TWRP before you do anything... you'll thank me for that
Thanks for the elaborate explanation,but I am stuck on:
Jimmy Mossiba Floyd said:
fastboot boot "TWRP 3.0.2 by Jemmini.img"
Click to expand...
Click to collapse
Cmd says that it successfully pushed and booted the image
Code:
downloading 'boot.img'...
OKAY [ 0.717s]
booting...
OKAY [ 0.070s]
finished. total time: 0.799s
...but after a couple of seconds, it reboots to system.
Any Ideas what is happening?
Long time no see hhhhh
ummm really have no idea since it works flawlessly for me but ummmm tell me: do you care if you lose the stock recovery?
I would like to try to flash it but there is a chance that it would not work , therefore having no recovery. I have unlocked my bootloader though.
Ok so instead of:
fastboot boot "TWRP 3.0.2 by Jemmini.img"
Try:
fastboot flash boot "TWRP 3.0.2 by Jemmini.img"
This is only if you're gonna take the risk... If not, just give me time maybe I'm gonna find something for you
Sorry, but I don't want to take the risk. I think the problem is that I am running Android 7.0 which differs from other versions. I have contacted Kogan to see if I can access the source code, but judging by previous threads on Kogan, it is not going to be easy.
Ah ok then I must be wrong! Because my device runs on Marshmallow 6.0 and ther must be a difference between the two (software-side)
I don't know if you can do it but, can I have a system dump so that I can bring you a fix for rooting the device?
P.S: I can assist you to make one if you want!
I am not quite sure how to dump the system (Is it "adb pull /system <whatever path>"). I have run the command, and it seems that adb can't access the /system/bin folder. Is it required for recovery porting? If not I will upload the system.
Sorry for being late, I have no DSL where I live and my data plan came to an end!! I will look for a method to dump the whole system for you. Stay tuned
Kogan has replied back and the kernel is released to the public.
https://assets.kogan.com/files/support_files/KAPHN4G6PA_Kernel/kernel-3.18.tar.gz
I am not very experienced with compiling from the kernel so some help would be nice.
I'm not really into compiling kernels... I wish I could... Gonna see with some developers in the samsung forums may be they'll be willing to help
P.S: I'm really really sorry for being late to help you with rooting the phone.. my only pc is bricked and I need it to send you the files I used to pull and push recovery to the phone
In case it's not much asking, is there a possibility to have the link for the stock firmware from kogan?
Unfortunately, Kogan did not release the stock firmware, just the kernel. I'll too go to the other forums and see if they can help.
Thank you very much for your help, and I hope that you can un-brick your pc.
Installed TWRP but it can't read internal storage.
Also wanting to root my agora 6 plus BUMP
looking for help to root
Goals:
Installing a custom recovery like trwp
Rooting
Flashing Xposed.
its on Nougat (7.0)
I can access the bootloader, fastboot and the default installed "recovery" which when loaded say something macros the lines of no commands give by booting the phone and holding both vol up and the lock/power buttons.
I'm available to talk on discord to speed things up.
I've got a bit of experience rooting the z2 and an old htc pico back in the day but i'm consider me a noob as i haven't done this kinda thing in years and don't even know where to begin.
Cryptic Bore said:
looking for help to root
Goals:
Installing a custom recovery like trwp
Rooting
Flashing Xposed.
its on Nougat (7.0)
I can access the bootloader, fastboot and the default installed "recovery" which when loaded say something macros the lines of no commands give by booting the phone and holding both vol up and the lock/power buttons.
I'm available to talk on discord to speed things up.
I've got a bit of experience rooting the z2 and an old htc pico back in the day but i'm consider me a noob as i haven't done this kinda thing in years and don't even know where to begin.
Click to expand...
Click to collapse
The thing is that I have a similar (identic) phone but Algerian brand that makes the phone is still on marshmallow!
I've still got the phone, but I don't know if my TWRP would work for you!
Quick questions:
0. Is it your daily driver phone? do you have a backup for your photos/data/important files on internal storage? just to put you in the image: I lost all my internal storage as I was playing with ramdisk modifications, hopefully my photos were cloud backed up. So be warned
1. Is your phone's bootloader unlocked?
2. Are you familiar with flashing or booting recoveries or kernels from fastboot?
after you answer I'll guide you through it
Hey thanks for the reply im thinking of teaching myself to build my own port of trwp.
0. It is my daily driver but i only just got it the other day ie. nothing important on there besides two factor authentication which even that i can reset up fairly easily. or just take the sim card out and use sms for that.
I also like to live on the edge a bit place austinpowers.jpg here(my first smart phone i got for my birthday from my rents: i got into a boot loop through flashing with in a week of receiving it and fixed on the fly at uni using the libary computers without my rents knowing my phone was broken xD)
1. Is the boot loader unlocked not sure how to check it on this phone, I do however have dev options unlocked with usb debuging etc turned on aswell as tickbox for "OEM Unlocking" with the description: allow the bootloader to be unlocked which i just have turned on .
2. Yes i do but im a bit out of practice its been years since ive messed around with root on android. Ive got logcat dumps through adb and have got fast boot working (as far as i can tell with the "fastboot" devices query) Got some help from a FB friend who is also going to try helping me make this happen. My previous experience was a HTC pico (the first smart phone i referenced earlier) and a Sony z2 which recently died dropping it which had a duel boot setup with carbon rom being the daily driver/rom.
Jimmy Mossiba Floyd said:
The thing is that I have a similar (identic) phone but Algerian brand that makes the phone is still on marshmallow!
I've still got the phone, but I don't know if my TWRP would work for you!
Quick questions:
0. Is it your daily driver phone? do you have a backup for your photos/data/important files on internal storage? just to put you in the image: I lost all my internal storage as I was playing with ramdisk modifications, hopefully my photos were cloud backed up. So be warned
1. Is your phone's bootloader unlocked?
2. Are you familiar with flashing or booting recoveries or kernels from fastboot?
after you answer I'll guide you through it
Click to expand...
Click to collapse
I'm using a Sony Xperia Z2 tablet - SGP511 (castor_windy). It's been rooted before, bootloader unlocked and had a couple of custom ROMs at various times. I've had issues because apps like root checker say it's not rooted properly and I am not getting the full benefit of a rooted tablet.
I have recently reset it to factory and the original OS seems to have come back. I'm now trying to start again with a new ROM but can't get into recovery mode.
I've flashed TWRP recovery BUT - I can't get into recovery mode to ensure root has happened properly. I've tried getting to recovery via adb and via the hard buttons on the tablet, but the tablet either resets and loads up again or I get a triple vibrate and the LED flashes different colours.
So - i'd love to know any thoughts anyone might have? I think there's something glitchy way down underneath what I can see. I'm not amazing at this stuff - really just read a lot of forums.
I'm hoping to have TWRP working and then to root using SuperSU to ensure that the tablet is rooted properly, THEN to flash Paranoid Android.
I really really hope someone can give me a hand!