Hi all,
I have been through douzens of threads and forums looking for a solution to this.
I followed some instructions to modify the build.prop file on my Huawei G535-L11 to disable Huawei theme manager in order to get Xsposed working fully (changed ro.config.hwtheme: 0). I did a backup of my original build.prop before hand, and my phone was rooted and unlocked but running the stock rom.
Unfortunately, it rebooted but won't go past the first 'EE' splash screen (just turns off again).
I can inconsistently get in to both fastboot and Android recovery, so I have been trying to use adb to push the original build.prop to /system/ on the phone.
However, this fails as /system/ is apparently RO. I have now discovered that I can't get SU permissions despite my phone being rooted.
If I try:
adb shell
$ su
nothing happens and it goes back to a $ prompt.
If I try:
adb root
I get the message (paraphrased):
adb cannot run as root in production builds.
So I can't push or do any adb method of restoring the build.prop file?! I don't understand why it is acting as if it is not rooted. I had Link2sd, Gravity Box, No Frills Cpu Controller all set up and working before, so I'm fairly sure I did truly have root.
I have also tried flashing a TWRP recovery, which apparently is successful, but when I go in to recovery it is still the Android Recovery.
Does anyone have any ideas what I could do to get my phone working again please?! This is my last gasp before the phone gets filed under 'B' in the cylindrical cabinet in the corner of the room!
Any assistance greatly appreciated!
Some systems are very finicky with modded build.props, or you didn't set the file's permissions correctly. I'm afraid without being able to boot or a working custom recovery, then adb won't work, much less root enabled adb functions. adb works in some stock recoveries, but only for sideloading files directly signed by the manufacturer. In regards to TWRP, is the bootloader unlocked? If not, that would explain why it didn't work. Other than that, I don't believe you'll have any other options besides reloading the stock firmware.
Hi,
Thanks for the reply. Yes, the bootloader was / is unlocked.
Unfortunately, there isn't any stock firmware available anywhere. Unless someone out there has a backed up rom image from the EE Kestrel?
This is supposed to be a working TWRP for your device http://forum.xda-developers.com/showpost.php?p=58522448&postcount=117 - if you get it loaded, there might be a chance to push the working build.prop back to the phone. I would read that thread too and see if there isn't more useful info there or another member with your phone that could make a backup for you. Good luck.
Thanks.
Unfortunately, I'm pretty sure that is the TWRP I've tried. I'll double check when I'm on my PC.
I might try requesting a rom image on that thread, but the community for this phone seems to be pretty dead :/
I've just gone and ordered a new phone anyway, but it seems like a waste of a good phone just for the sake of one line of bad code!
Thanks for your help. I'll post again if I have any success.
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
Hey there! I am new to this forum, if this thread breaks a rule, I'm completely sorry
I use a Acer B1-730(not HD), it has a completely locked bootloader, but I rooted it using the Intel FBRL method (the one that involves adb/fastboot to flash a temporary custom recovery)
I rooted it so I could use App2SD and similars (KitKat user here ), but it didn't worked.......Edited build.prop.....Didn't worked, but didn't stop working after one restart...So I got tempted to edit the vold.fstab....But I didn't find any resource with a file similiar to mine...So I just picked a generic one and pushed into my device Apparently, that just made me stuck in bootloop....I am trying to fix it for hours, discovering that it somehow responds to adb commands and that I am able to use the Intel FBRL to go to custom recovery and revert my changes (no backup or stock rom for me And I prefer to continue with my files)
But It denies the permission to push files into it(I think that it is because it is only partially turned on), refuses to accept the licenses for my custom zips and is only responding to adb sometimes,most of the time, my PC don't find it, what can I do? I have the changed files, original files, and licensed zip,how do I send them with this post? Can someone help me?
I don't have Custom Recovery BTW
@demkantor
@milkyway3
@Woody Herald
@bilgerryan
@engloa
Hello there xda members, I am somewhat familiar with rooting android phones, however the last time I had done so was with was older HTC and I believe maybe it was a Sony about 2-3 years ago. I now have an Alcatel 3v and I've come to learn that rooting seems to be different on newer phones and the newer Android Oreo. I have managed to unlock the bootloader on my phone, and I have also downloaded the android sdk on my windows computer and am somewhat familiar with adb and Fastboot Commands, although I have only barely begun to understand Linux terminal commands. There is no version of twrp for my phone and I have not been able to find a stock firmware anywhere to go with the magisk method, as well none of the one click solutions have worked for my phone, including the ones requiring use of a pc and developer mode enabled. Im wondering if I can access the system folders and write to them through adb or fastboot using push / pull commands or if there is a way to make a stock boot. Img straight from my phone so I can patch it? If not is there any other possible way to root this phone? Any help would be appreciated.
Laney613 said:
Hello there xda members, I am somewhat familiar with rooting android phones, however the last time I had done so was with was older HTC and I believe maybe it was a Sony about 2-3 years ago. I now have an Alcatel 3v and I've come to learn that rooting seems to be different on newer phones and the newer Android Oreo. I have managed to unlock the bootloader on my phone, and I have also downloaded the android sdk on my windows computer and am somewhat familiar with adb and Fastboot Commands, although I have only barely begun to understand Linux terminal commands. There is no version of twrp for my phone and I have not been able to find a stock firmware anywhere to go with the magisk method, as well none of the one click solutions have worked for my phone, including the ones requiring use of a pc and developer mode enabled. Im wondering if I can access the system folders and write to them through adb or fastboot using push / pull commands or if there is a way to make a stock boot. Img straight from my phone so I can patch it? If not is there any other possible way to root this phone? Any help would be appreciated.
Click to expand...
Click to collapse
The phone is project treble compatible so you could try flashing a GSI just make sure the GSI is A-only not A/B as the phone dosen't support seamless updates. There are tons of GSIs out there with root and gapps just choose which one you like but I would highly recommend taking a backup of your stock ROM as they haven't really got firmware downloads for this phone. Also after you have rooted I would recommend locking the bootloader again so any repair shops wont find out that the phone has been rooted. There is another way which is you could dump the boot image from the phone and install the magisk manager apk. Then patch your boot image through it and flash it with fastboot and now your stock rom is rooted.
I've been having difficulty finding a way to backup my stock rom without a rooted phone... I have looked into miracle box and sp flash tool and other programs but they so far seem either dated, contain viruses or don't do what they advertise / incompatible with my phone, or need root access to show partitions etc. also, with flashing a generic system image, are they device specific or is that the whole point of project treble, how they are universally supported? I want to keep my phone as close to stock as possible but with root access. If I could find a way to backup my boot image I could go the magisk method...
Laney613 said:
I've been having difficulty finding a way to backup my stock rom without a rooted phone... I have looked into miracle box and sp flash tool and other programs but they so far seem either dated, contain viruses or don't do what they advertise / incompatible with my phone, or need root access to show partitions etc. also, with flashing a generic system image, are they device specific or is that the whole point of project treble, how they are universally supported? I want to keep my phone as close to stock as possible but with root access. If I could find a way to backup my boot image I could go the magisk method...
Click to expand...
Click to collapse
The Generic system images are universal because basically project treble separates the files that make the phone work such as the camera and fingerprint into a vendor partition which means manufacturers don't have to make new drivers to work with the new os update. The only issue on my phone which is the 3v 5099y (single sim with nfc) is that pie is very slow and laggy but everything works however oreo is very fast. I tried looking for a way to dump the boot.img but all i could find was tutorials for phones which either were rooted or had twrp. But i did find this tutorial which dumps the entire firmware although its very complicated https://android.stackexchange.com/q...nd-full-rom-without-root-for-mediatek-devices
For the cpu part though I would select mt6735 as the mt8735 is basically a rebrand
im so tired to root my alcatel 3v phone many try all method to rooting but almost field please help me
Hello, and thanks for reading my post...HOPING someone can help...so, Here's the specs. If you need more just ask...
Mediatek MT6739 salable: ZTE Z3351S (Qlink Wireless govt. phone)
Android 9 running SP 2019-07-05 (API 28)
Build: Z3351SV1.0.0B4
BL: Locked, no root (even through Magisk...so far.)
As this is my primary phone I'd really rather avoid the off chance of bootloop, soft/hard bricking....but I am very interested in the security features on this device...I've not done a LOAD of rooting and playing, this system has managed to make my poor old brain swim like I had a green beer!!!
I've so far managed to get a temp root solution, and got backups of the entire device excepting the /user partition...not an easy task, and I PROBABLY coulda got it but that's one big-a^& file!
Since I don't wanna have to actually pay full price for a replacement in the case of me screwing up, I've hesitated on trying the Magisk solution for a /system-less root. I unpacked the boot.img and ramdisk (which wound up empty,) and the recovery.img and ramdisk (which did have files,) and I dont really have the experience in repacking the image (with oem signature,)
or (and this is a big one,)
how to enable the full fastboot on it...and I'm not sure where that is, I think it's moved to the user area...and I want the BL unlocked before I even try to Magisk this puppy...
Fastboot works okay, maybe. Command adb reboot bootloader gets me a fastboot mode on the device, but no fastboot devices. When I lsusb (Linux Mint 18) the Mediatek device shows up, but not as bootloader.
I would like to take these unpacked files, mod the existing kernel to allow full fastboot, repack it (with oem sig so the stock recovery doesn't reject it,) the flash it as an update....
....HEEELLLPPP...
What do I do from here?!?
Thanks a LOT guys...and you gals too!:laugh: