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
Related
I have Alcatel OT-910, but i cant find anything about root & rom for this model here on xda-developers forum. I found threads for other Alcatel models (OT-908, OT-980, OT-990) and i was wondering is anyone working on this particular model? Is it possibile to have root access? stock ROM for OT-910? Thanks.
Alcatel OT-910
CPU 600 MHz
OS Android OS, v2.2 (Froyo)
Keyboard QWERTY
root
i have tried to root my OT-910 with SuperOneClick 2.3.3, but it doesn't work.
Keeps stuck at Step #7 Waiting for Device.
also tried to unplug and replug it at this part, but no chance.
any other ideas how to get root? Some of the installed apps are useless for me and eat up my memory, want to get rid of them
rooting problem
I've got OT910 too, tried several ways to root with steps, provided for other Alcatel android phones - no luck.
Try with different versions os superoneclick. Aso you should install Pdanet on your phone and your computer to and try again with superoneclick.
Sent from my ALCATEL one touch 990
No luck still
I tried all SuperOneClick releases, z4root, GingerBreak - nothing really works. The phone is hardly operable without root - too much garbage preinstalled.
Hey, i have an Alcatel OT-909a (which is the same as Alcatel OT-910 but with a lower px camera) and i also am unable to get root access, i already know that there is a stock busybox, and have seen some files of the internal memory but still not having luck, i also flashed some CWM and RA recoveries but i just got stuck while trying to access recovery, so i have to get back to stock recovery, i think there must be a way to do at least a nandroid backup and try to root the backup and flash again, but i dont know, the CWM recovery just boot the android logo, after there is nothing in the screen, but the QWERTY keys are on like if the phone was in recovery, i had tried Super One Click 1.9.2 and 2.3.3 and got stuck in step #7 too, zergRush and GingerBreak doesnt work also, something extrange for me is that the last time i try CWM, it didnt boot into recovery but into fastboot, as far as i know internal memory is read-only except for the installation of apps and some folders (or somehow i push GingerBreak and zergRush to the internal memory isn't?), i can't push su to the xbin or bin folders, but i already saw what is inside xbin an bin (as i said memory is read-only and there are some folders that requires permissions to access), there must be a way to push su to xbin folder (or at least maybe access su in another location?) but i still seeing how?
PD: sorry for my possible bad english speaking
PD2: yes i'm a noob and i hate myself but please some of you that know of this, help us?
Edit: just curious i just push su to "/data/local/tmp" then i just tipe ./su and it appeared on the phone "shell has been granted superuser permissions"
Alcatel_OT_909a /909s /910
OS: Android Gingerbread 2.3.4 / 6180
Kernel: 2.6.35.7-perf [email protected] #3
Here an idea: Custom Rom
hey guys, if some of you (someone, anyone who might wanna help?) are still maybe reading this thread, i wonder, i have played with the phone a little (unluckly i really messed up breaking the cellphone and luckily for me, the motherboard was replaced at service center), and i have been able to pull out most of the system partition, custpack and others, (except for the recovery partition) and i was wondering if maybe there is a way to create a custom rom with those files?, maybe we could create our custom rom and flash it, after seeing around the files, i got that 909a it's using what it's looks like at least the same kernel than ot910, (actually some information is from the ot910, in the manual it refers to ot909a-s ot910 as same cellphone but with different px in camera), so maybe we could create a custom GB rom based on the files from the stock system partition, and as alcatel has relased the kernel sourcecode maybe we could even do a custom kernel?, i was just wondering if someone can try to do a custom rom with those files, as i have tried flashing some GB roms replacing files and the phone doesn't boot up to android, but in recovery you get su access and pull the other files, but when replacing files, there is a moment when the system lose adb shell access, so maybe someone with more knowleadge (as i'm new to both android and linux) can help?
Rooting -- any news?
Has anyone succeeded in rooting the device in the meantime? I had no luck with either psneuter, zergrush, or gingerbreak ...
OT-910 successfully rooted!
Hi,
thank's to the great work of giantpune over at Phandroid, the Alcatel OT-910 has been successfully rooted (see the attached screenshot)!
For instructions, cf. the thread "Optimus Elite root with an apk" at Phandroid's LG Optimus Elite forum. Put in a nutshell, you have to install the following two APK's:
1. the Poot-debug.apk tailor-made for this phone, and
2. Ministro II.apk.
Both files are linked at the end of giantpune's original post at the LG Optimus Elite forum.
Note that Superuser, but not SuperSU, will grant root access on the OT-910.
Have fun!
Any Rom for OT 910
nolda said:
Hi,
thank's to the great work of giantpune over at Phandroid, the Alcatel OT-910 has been successfully rooted (see the attached screenshot)!
For instructions, cf. the thread "Optimus Elite root with an apk" at Phandroid's LG Optimus Elite forum. Put in a nutshell, you have to install the following two APK's:
1. the Poot-debug.apk tailor-made for this phone, and
2. Ministro II.apk.
Both files are linked at the end of giantpune's original post at the LG Optimus Elite forum.
Note that Superuser, but not SuperSU, will grant root access on the OT-910.
Have fun!
Click to expand...
Click to collapse
Can you please suggest any ROM for OT 910.
Help need...
Hi guys,
I need your help man, I had just rooted successfully and I don't know what have I done now it is just stuck at TCL logo and restarting.
please please please help...
May be flashing it solve the problem I have sent email to alcatel but they didn't have the rom so some one help me and also I had flash recovery but didn't back up original one so also give me that or any working CWM recovery.
plzzzzzzzzzzzzzzzz
my last hope is xda...
smkamranqadri said:
Hi guys,
I need your help man, I had just rooted successfully and I don't know what have I done now it is just stuck at TCL logo and restarting.
please please please help...
May be flashing it solve the problem I have sent email to alcatel but they didn't have the rom so some one help me and also I had flash recovery but didn't back up original one so also give me that or any working CWM recovery.
plzzzzzzzzzzzzzzzz
my last hope is xda...
Click to expand...
Click to collapse
If your last hope is xda... then maybe you will not have that much luck, if you're stuck at TCL logo, maybe you could try using the "OTU Upgrade Tool" (by means "OTU = Alcatel/TCL Flasher") and maybe that will do the trick and then you get your phone back to stock, if not (or if you already did that), then you're a little out of luck, as far as I know, there is no stock recovery around, and also as far as I know, there is no CWM recovery, now, in case you did use OTU Tool, and failed flashing the phone, then is almost sure that your nand is bricked, if you used OTU Tool and that didn't get your phone back, then you should see if you can still flash Android Images (more accurately 2.3.3 (since 2.3.4 did brick my phone twice)), at least with a non-functional 2.3.3 image, maybe you could flash from there with OTU again, or try to modify 2.3.3 system to work with your phone, if nothing of that did result for you, then you're out of luck, because I'm almost sure that would mean that you are in a nand brick, and the only way to solve it, is sending it to Service Repair (at least for now)
now, for using OTU Upgrade Tool, you can download it from TCL/Alcatel website ( www2.alcatelonetouch.com/global-en/support/download.html ) in the download section, select your phone model, and from there download the OTU Upgrade Tool, after downloading, install it and follow the instructions for getting the phone in "Download Mode" (in OT910 = (pressing "Q" key with the phone totally off, and after pressing the "Q" key for 30sec. or a minute, then (still pressing the "Q" key) connect it to the pc and follow the onscreen steps (that means, choosing your mobile and getting in to look for the firmware and download it)
I have a kind of "backup" of the system (I mean, every file that is in /system) but sadly, it doesn't have the properly permissions set, and so, it gives also a boot loop (also I bricked my phone once again and for worse, when it was out of warranty), so if you still in warranty maybe you should send it to service :/
that's the sad of life when your mobile is not the one that is being developed by expert developers (not even a beginner one )
Hope you can fix your phone
thanks for help
thanks man you are my captain...
I recheck the upgrade tool it just say that you have latest software.
So if you have 2.3.3 then please give me that i will update it via adb shell as i can still access it as su.
smkamranqadri said:
thanks man you are my captain...
I recheck the upgrade tool it just say that you have latest software.
So if you have 2.3.3 then please give me that i will update it via adb shell as i can still access it as su.
Click to expand...
Click to collapse
I will, but before, what version of upgrade tool are you using? (mine has a kind of strange bug that the rom is never ever able to get the last update (as always download saying there is a new update (it's a fake but anyway)), that would be kind of a problem since maybe after you flash 2.3.3 the upgrade tool will state that you're still in latest firmware (even through upgrade tool is supposed to be a service tool, funny isn't?), anyway, since you have nothing to lose (since apparently you flashed a custom recovery that didn't work for you), but, there are this two things you should try before, first (and pretty much the must obvious one) if you have warranty (as long as you're in warranty and never tried to see what's inside the phone), and two, there is a little possibility that maybe you can access adb via the recovery you flashed, even, when the tcl logo appears, try to do "adb shell" or "adb devices", so maybe you can recover your phone without the need of flashing android 2.3.3.
now, if nothing of that worked, then there is nothing to loose, if you have the android sdk, from there you can download a 2.3.3 image, that will boot, but display nothing in the screen (still you can do adb shell with su, and try to properly install libraries maybe?), if not, then i'll check if I can do one system image for you, and see what it does
by the way, if somehow you can access adb , try to do "adb pull" and pull the " /system" partition
it's really sad that we can't (at least not me) figure out, how to use the files that the upgrade tool uses ( 570mb of 10 - 520kb files)
Help me... alcatel 909
Azuruw said:
I will, but before, what version of upgrade tool are you using? (mine has a kind of strange bug that the rom is never ever able to get the last update (as always download saying there is a new update (it's a fake but anyway)), that would be kind of a problem since maybe after you flash 2.3.3 the upgrade tool will state that you're still in latest firmware (even through upgrade tool is supposed to be a service tool, funny isn't?), anyway, since you have nothing to lose (since apparently you flashed a custom recovery that didn't work for you), but, there are this two things you should try before, first (and pretty much the must obvious one) if you have warranty (as long as you're in warranty and never tried to see what's inside the phone), and two, there is a little possibility that maybe you can access adb via the recovery you flashed, even, when the tcl logo appears, try to do "adb shell" or "adb devices", so maybe you can recover your phone without the need of flashing android 2.3.3.
now, if nothing of that worked, then there is nothing to loose, if you have the android sdk, from there you can download a 2.3.3 image, that will boot, but display nothing in the screen (still you can do adb shell with su, and try to properly install libraries maybe?), if not, then i'll check if I can do one system image for you, and see what it does
by the way, if somehow you can access adb , try to do "adb pull" and pull the " /system" partition
it's really sad that we can't (at least not me) figure out, how to use the files that the upgrade tool uses ( 570mb of 10 - 520kb files)
Click to expand...
Click to collapse
First of all my update tool version is 1.2.0.10.
Second i got second hand set from local market at karachi, pakistan so no warranty where i exchange some email from alcatel support for rom but said that they didn't have.
third i can access adb shell with couple of reentering su i got super user so what to do to recover.
i will pull system partition and give you the link soon also downloading sdk for image.
thanks alot...
may we could chat live for better working. find me smkamranqadri at any platform except google kami.genius.
Got ROM/ RECOVERY
smkamranqadri said:
First of all my update tool version is 1.2.0.10.
Second i got second hand set from local market at karachi, pakistan so no warranty where i exchange some email from alcatel support for rom but said that they didn't have.
third i can access adb shell with couple of reentering su i got super user so what to do to recover.
i will pull system partition and give you the link soon also downloading sdk for image.
thanks alot...
may we could chat live for better working. find me smkamranqadri at any platform except google kami.genius.
Click to expand...
Click to collapse
I had got rom & recovery and every partions so any one need have do chat with me at fb - Muhammad Kamran qadri
Had the phone for 2 weeks. without being rooted it is so boring! Please any devs come up with a custom recovery soon
htcmusic said:
Had the phone for 2 weeks. without being rooted it is so boring! Please any devs come up with a custom recovery soon
Click to expand...
Click to collapse
that's why i gave mine to my wife, she doesn't like root. not positive this device will really get alot of development.
fix-this! said:
that's why i gave mine to my wife, she doesn't like root. not positive this device will really get alot of development.
Click to expand...
Click to collapse
Guys the device was just launched. Right now I'm working on teaming up with Brinly Taylor so we can develop for this.
Moto e 3g Variant boot.img and recovery.img
give me the following and i will try to compile a custom recovery
- boot.img(from 3g variant)
-recovery.img(from 3g variant)
Saumitra Yadav said:
give me the following and i will try to compile a custom recovery
- boot.img(from 3g variant)
-recovery.img(from 3g variant)
Click to expand...
Click to collapse
I have this model. But when i try to extract boot.img from adb shell. it says access denied, and when i type su the it says not found . any idea how this can be resolved.
We seem to have a chicken and egg problem here. We need a custom recovery to get root, but we need root to get the bits to make a custom recovery. I'll try to make something when I have time, but I don't have a device to test with, so I'll need the community's help to test.
squid2 said:
We seem to have a chicken and egg problem here. We need a custom recovery to get root, but we need root to get the bits to make a custom recovery. I'll try to make something when I have time, but I don't have a device to test with, so I'll need the community's help to test.
Click to expand...
Click to collapse
Well i have this 3g variant of moto e 2015. I am ready to help but i am new to all this stuff. Yesterday i pulled system.img but can't pull boot image.
Ravx said:
Well i have this 3g variant of moto e 2015. I am ready to help but i am new to all this stuff. Yesterday i pulled system.img but can't pull boot image.
Click to expand...
Click to collapse
I made something. I have no clue if it will work. Things usually don't work on the first try, but we have to start somewhere. Try this at your own risk. I'm not responsible for bricking your phone. I don't have a Moto E 3G to test with.
As a good first test with this recovery, try flashing SuperSU: http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1
TWRP for 3G Model only! Flash at your own risk! Completely untested first attempt!
Download link for my test recovery: http://www.mediafire.com/download/uple1nxzzpg1cb5/otus_twrp-2.8.6-untested.img
To install:
Code:
fastboot flash recovery otus_twrp-2.8.6-untested.img
EDIT: Don't use this image, it's too big and I've identified other issues.
Ravx said:
I have this model. But when i try to extract boot.img from adb shell. it says access denied, and when i type su the it says not found . any idea how this can be resolved.
Click to expand...
Click to collapse
This will be possible only when moto release sources,
squid2 said:
I made something. I have no clue if it will work. Things usually don't work on the first try, but we have to start somewhere. Try this at your own risk. I'm not responsible for bricking your phone. I don't have a Moto E 3G to test with.
As a good first test with this recovery, try flashing SuperSU: http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1
TWRP for 3G Model only! Flash at your own risk! Completely untested first attempt!
Download link for my test recovery: http://www.mediafire.com/download/uple1nxzzpg1cb5/otus_twrp-2.8.6-untested.img
To install:
Code:
fastboot flash recovery otus_twrp-2.8.6-untested.img
Click to expand...
Click to collapse
I had someone try it and found out that the image is too big. I will post a smaller one that should fit when I find time. I'll need to create a stripped down kernel and device tree for otus. To do that, I'd probably need my own device to test on. The 3G model is unavailable in Canada, but for the sake of the community, I've ordered a 3G model from abroad, at a cost much greater than what it is worth, so that I have a unit to test on. My test unit won't arrive for another week I'd expect.
squid2 said:
I had someone try it and found out that the image is too big. I will post a smaller one that should fit when I find time. I'll need to create a stripped down kernel and device tree for otus. To do that, I'd probably need my own device to test on. The 3G model is unavailable in Canada, but for the sake of the community, I've ordered a 3G model from abroad, at a cost much greater than what it is worth, so that I have a unit to test on. My test unit won't arrive for another week I'd expect.
Click to expand...
Click to collapse
Thankyou so much squid bro, you are great . Please make a new thread for moto e 3g 2015 version in which all the development and testing work will be carried out. I thought that i have made wrong descision by buying Moto E 3g version because of no dev support. You are a life saver bro.....
As far as testing goes , I am in.....:good:
Ravx said:
Thankyou so much squid bro, you are great . Please make a new thread for moto e 3g 2015 version in which all the development and testing work will be carried out. I thought that i have made wrong descision by buying Moto E 3g version because of no dev support. You are a life saver bro.....
As far as testing goes , I am in.....:good:
Click to expand...
Click to collapse
Here goes my second attempt. I've tried to backport my Linux 3.10.74 based "Squid Kernel" to the 3G Moto E. This is a rather crazy idea, and I don't think anyone has ever done this for the MSM8x10 family. I've managed to create a kernel binary that is half the size of the stock kernel. I don't expect this recovery to boot at all. If it does boot, I would be quite pleased.
Download link for the adventurous: https://www.mediafire.com/?j5wgj035ml7nng9
I'd suggest first trying fastboot boot twrp-otus-2.8.6-test2.img before you flash it, since it is experimental and probably won't work. If it does boot, check the file manager to see if it is able to view all your data. If it boots and is able to see your data, then we have a miracle, so go ahead and flash it if you'd like.
If this recovery doesn't boot, don't worry, I will make a recovery that works, just be patient. I'm waiting for my test unit to arrive. It's been crawling along through the USPS. Hopefully, I'll have it by this time next week.
REMINDER: This is totally untested, and probably won't work. Try at your own risk. Make sure to try booting it with "fastboot boot" before flashing it. This might brick your device. Be careful. Even if it appears to work, I don't recommend flashing anything with this recovery until I receive my test device and properly verify it.
P.S. I'll make a new thread once I have something that works.
squid2 said:
Here goes my second attempt. I've tried to backport my Linux 3.10.74 based "Squid Kernel" to the 3G Moto E. This is a rather crazy idea, and I don't think anyone has ever done this for the MSM8x10 family. I've managed to create a kernel binary that is half the size of the stock kernel. I don't expect this recovery to boot at all. If it does boot, I would be quite pleased.
Download link for the adventurous: https://www.mediafire.com/?j5wgj035ml7nng9
I'd suggest first trying fastboot boot twrp-otus-2.8.6-test2.img before you flash it, since it is experimental and probably won't work. If it does boot, check the file manager to see if it is able to view all your data. If it boots and is able to see your data, then we have a miracle, so go ahead and flash it if you'd like.
If this recovery doesn't boot, don't worry, I will make a recovery that works, just be patient. I'm waiting for my test unit to arrive. It's been crawling along through the USPS. Hopefully, I'll have it by this time next week.
REMINDER: This is totally untested, and probably won't work. Try at your own risk. Make sure to try booting it with "fastboot boot" before flashing it. This might brick your device. Be careful. Even if it appears to work, I don't recommend flashing anything with this recovery until I receive my test device and properly verify it.
P.S. I'll make a new thread once I have something that works.
Click to expand...
Click to collapse
Ok probably a noob qiestion. But does booting recovery from adb makes any changes to my device. Is there a probabilty of soft bricking the device by this method.
And should the boot loader be unlocked before trying this.
Ravx said:
Ok probably a noob qiestion. But does booting recovery from adb makes any changes to my device. Is there a probabilty of soft bricking the device by this method.
And should the boot loader be unlocked before trying this.
Click to expand...
Click to collapse
You need an unlocked bootloader. First boot your device into bootloader mode (turn phone off, press and hold PWR and VOL- together for 3 seconds, then let go). You will see a bootloader menu. Then use fastboot on your computer to boot the recovery.
Running "fastboot boot xyz.img" will not make any changes to your device. As long as you don't flash anything with the recovery, it's fairly safe to try. Booting it up and browsing with the file manager shouldn't hurt anything. Note that when you try to leave recovery, TWRP will ask you if you want to root your device with SuperSU. If you want to be safe, read the screen carefully and make sure you say no for now.
The risky operation would be to flash the recovery (fastboot flash xyz.img) and then use the recovery to flash other ROMs or customizations. I would not recommend doing this if you don't have enough experience or are worried about messing up your phone.
squid2 said:
You need an unlocked bootloader. First boot your device into bootloader mode (turn phone off, press and hold PWR and VOL- together for 3 seconds, then let go). You will see a bootloader menu. Then use fastboot on your computer to boot the recovery.
Running "fastboot boot xyz.img" will not make any changes to your device. As long as you don't flash anything with the recovery, it's fairly safe to try. Booting it up and browsing with the file manager shouldn't hurt anything. Note that when you try to leave recovery, TWRP will ask you if you want to root your device with SuperSU. If you want to be safe, read the screen carefully and make sure you say no for now.
The risky operation would be to flash the recovery (fastboot flash xyz.img) and then use the recovery to flash other ROMs or customizations. I would not recommend doing this if you don't have enough experience or are worried about messing up your phone.
Click to expand...
Click to collapse
Sorry bro but it is not booting. The steps i followed
1.) unlocked bootloader ( Success ...getting unlock msg when booting
2.) got to bootloader.
3.)booted the recovery ( i changed the name of recovery to "recovery" for convinience)
4.) cmd showed msg booting but the phone shows android logo and does not act from there.
5. I had to reboot the phone by pressing power button for 10 secs.
Have i done anything wrong????
Ravx said:
Sorry bro but it is not booting. The steps i followed
1.) unlocked bootloader ( Success ...getting unlock msg when booting
2.) got to bootloader.
3.)booted the recovery ( i changed the name of recovery to "recovery" for convinience)
4.) cmd showed msg booting but the phone shows android logo and does not act from there.
5. I had to reboot the phone by pressing power button for 10 secs.
Have i done anything wrong????
Click to expand...
Click to collapse
It might just be that it doesn't work, but your comment about it showing the Android logo doesn't sound right. Does it show a "dead" android logo laying on its back with a door open on its body? If you see that, you booted up the stock recovery. The stock recovery will show that logo forever until you use a certain button combo to bring up a menu.
How did you boot the recovery? I assume you downloaded my file, renamed it to "recovery.img", and then ran this command from the folder that contains my recovery image:
Code:
fastboot boot recovery.img
squid2 said:
It might just be that it doesn't work, but your comment about it showing the Android logo doesn't sound right. Does it show a "dead" android logo laying on its back with a door open on its body? If you see that, you booted up the stock recovery. The stock recovery will show that logo forever until you use a certain button combo to bring up a menu.
How did you boot the recovery? I assume you downloaded my file, renamed it to "recovery.img", and then ran this command from the folder that contains my recovery image:
Code:
fastboot boot recovery.img
Click to expand...
Click to collapse
No it showed the logo of moto powered by android and yes i renamed the file and entered the same command you typed.
As soon as i typed it. It showed that logo and got hanged. And then i rebooted. And it booted normally.
Ravx said:
No it showed the logo of moto powered by android and yes i renamed the file and entered the same command you typed.
As soon as i typed it. It showed that logo and got hanged. And then i rebooted. And it booted normally.
Click to expand...
Click to collapse
I had someone else try it too, with the same result as you. No big surprise to me, didn't expect it to work. I'll make one with a more conventional 3.4.x kernel when I get time.
Otus TWRP Attempt 3
@Ravx
Alright everyone, I've made a third attempt at creating a recovery for the Moto E 3G. I still don't have the device, so you have to test yourself. I made this one with a more conventional 3.4.x kernel. I would guess that this recovery is more likely to work than the the previous one. As before, try fastboot boot xyz.img before flashing. I suspect that this recovery might boot sometimes and fail other times. If it fails to be boot the first time, try a couple more times before giving up.
Download Link: http://www.mediafire.com/download/1he2ys1832441s7/twrp-otus-2.8.6-test3.img
If it boots, try using the file manager. Check that it is able to see all your files. I don't recommended using this recovery to flash things until I'm able to verify it myself.
Try at your own risk. I'm not responsible for messing up your device. This recovery has not been tested.
squid2 said:
@Ravx
Alright everyone, I've made a third attempt at creating a recovery for the Moto E 3G. I still don't have the device, so you have to test yourself. I made this one with a more conventional 3.4.x kernel. I would guess that this recovery is more likely to work than the the previous one. As before, try fastboot boot xyz.img before flashing. I suspect that this recovery might boot sometimes and fail other times. If it fails to be boot the first time, try a couple more times before giving up.
Download Link: http://www.mediafire.com/download/1he2ys1832441s7/twrp-otus-2.8.6-test3.img
If it boots, try using the file manager. Check that it is able to see all your files. I don't recommended using this recovery to flash things until I'm able to verify it myself.
Try at your own risk. I'm not responsible for messing up your device. This recovery has not been tested.
Click to expand...
Click to collapse
Bro you have done it. the recovery booted and i moved a file from one folder to another by using file manager. :good::good::laugh:
EDIT: For now i the recovery's file manager isnt showing "build.prop" and other folders in /system
only the "bin" folder is visible. Is it ok beacaause we havent flashed the recovery or its the other way around.
Hello guys,
I have a problem with my OnePlus X, and it would be lovely if I could get some help or advice from you guys.
> To provide some slight background, I purchased this off of eBay to complete my OnePlus collection. Most listings were above what OnePlus originally sold the phone for, but I found one for $125 in good condition by a seller with a good rating. It was advertised as soft-bricked, with Fastboot in working order. I thought "no problem, I'll just reflash it and be on my merry way."
Now onto the issue. I received it, charged it up, and attempted flashing the official recovery provided by OnePlus, but something is not working. I've been tinkering with Android for a number of years now, so I troubleshooted as much as I could, but to no avail.
1. Starting with device unplugged and powered off, boot into fastboot
2. Plugged into the computer, and ran `fastboot devices` to ensure it's recognized. After that, I flashed the recovery.img that was on my desktop with `fastboot flash recovery recovery.img` (yes I was in the correct directory). It looked successful. Picture of cmd response text at the following imgur album: /a/25DEQ (sorry I cannot post full links yet, had to create a new xda profile, forgot my old one :/
3. Unplugged the phone, powered off, Volume Down + Power to attempt boot into recovery. Failure. It just turns on with the 1+ logo, and quickly flashes the 'android' logo at the bottom. It stays like this until I manually power off.
I'm a bit stumped I have to admit. I would greatly appreciate any input you folks have. Thank you.
AndriyEtch said:
Hello guys,
I have a problem with my OnePlus X, and it would be lovely if I could get some help or advice from you guys.
> To provide some slight background, I purchased this off of eBay to complete my OnePlus collection. Most listings were above what OnePlus originally sold the phone for, but I found one for $125 in good condition by a seller with a good rating. It was advertised as soft-bricked, with Fastboot in working order. I thought "no problem, I'll just reflash it and be on my merry way."
Now onto the issue. I received it, charged it up, and attempted flashing the official recovery provided by OnePlus, but something is not working. I've been tinkering with Android for a number of years now, so I troubleshooted as much as I could, but to no avail.
1. Starting with device unplugged and powered off, boot into fastboot
2. Plugged into the computer, and ran `fastboot devices` to ensure it's recognized. After that, I flashed the recovery.img that was on my desktop with `fastboot flash recovery recovery.img` (yes I was in the correct directory). It looked successful. Picture of cmd response text at the following imgur album: /a/25DEQ (sorry I cannot post full links yet, had to create a new xda profile, forgot my old one :/
3. Unplugged the phone, powered off, Volume Down + Power to attempt boot into recovery. Failure. It just turns on with the 1+ logo, and quickly flashes the 'android' logo at the bottom. It stays like this until I manually power off.
I'm a bit stumped I have to admit. I would greatly appreciate any input you folks have. Thank you.
Click to expand...
Click to collapse
Which recovery u tried? Did u knOw the previous os version details?
And try this after flashing recovery in fastboot, boot into it directly by giving a cmd "fastboot boot recovery.img"
cva_kabil said:
Which recovery u tried? Did u knOw the previous os version details?
And try this after flashing recovery in fastboot, boot into it directly by giving a cmd "fastboot boot recovery.img"
Click to expand...
Click to collapse
Hi! Thank you for your reply
I posted this same question on the /r/oneplus subreddit, and received a quick and helpful walkthrough. Turns out part of the problem was that the micro-usb port on the phone itself is a bit unreliable. I haven't investigated too deeply, but it took a while to find a position for the wire to maintain a stable connection. I suspect this may be why the device was bricked in the first place (disconnect when flashing rom/kernel/etc.)
Anyways, for some reason flashing the stock recovery to the phone was just not working. The guy on reddit recommended trying TWRP, and that worked immediately. However, at that point, I had no idea what the history of the phone was or what OS was on it before, what firmware it had. I tried installing the official CM13 and then Sultan's CM13 with no luck. What *did* work was Oxygen OS 2.2.6.
At this point I'm stuck yet again though... The Marshmallow OTA (3.1.3) in the OS shows as available for download, but when I try to install the download only gets to 22% and then stops. Flashing the 3.1.3 OTA.zip available on OnePlus' support site doesn't work in TWRP, and when I try to flash stock recovery, it doesn't work.. don't know what else to try.
AndriyEtch said:
Hi! Thank you for your reply
I posted this same question on the /r/oneplus subreddit, and received a quick and helpful walkthrough. Turns out part of the problem was that the micro-usb port on the phone itself is a bit unreliable. I haven't investigated too deeply, but it took a while to find a position for the wire to maintain a stable connection. I suspect this may be why the device was bricked in the first place (disconnect when flashing rom/kernel/etc.)
Anyways, for some reason flashing the stock recovery to the phone was just not working. The guy on reddit recommended trying TWRP, and that worked immediately. However, at that point, I had no idea what the history of the phone was or what OS was on it before, what firmware it had. I tried installing the official CM13 and then Sultan's CM13 with no luck. What *did* work was Oxygen OS 2.2.6.
At this point I'm stuck yet again though... The Marshmallow OTA (3.1.3) in the OS shows as available for download, but when I try to install the download only gets to 22% and then stops. Flashing the 3.1.3 OTA.zip available on OnePlus' support site doesn't work in TWRP, and when I try to flash stock recovery, it doesn't work.. don't know what else to try.
Click to expand...
Click to collapse
Root your device using twrp or kingoroot method then install flashify and try to flash stock recovery using flashify. .. Tht may work.
Flashing 3.1.3 via official twrp ll not work... Cos ur bootloader version, U can do it only with stock recovery or u need to edit meta data file. Or u can flash stock recovery img file by twrp
cva_kabil said:
Root your device using twrp or kingoroot method then install flashify and try to flash stock recovery using flashify. .. Tht may work.
Flashing 3.1.3 via official twrp ll not work... Cos ur bootloader version, U can do it only with stock recovery or u need to edit meta data file. Or u can flash stock recovery img file by twrp
Click to expand...
Click to collapse
Thanks I'll give those a shot once I'm home from work! Quick question about editing the META INF. I've heard that doing so risks hard-bricking the device. Is that true?
AndriyEtch said:
Thanks I'll give those a shot once I'm home from work! Quick question about editing the META INF. I've heard that doing so risks hard-bricking the device. Is that true?
Click to expand...
Click to collapse
I dont think so... I hv not tried... But as of i know if u edit it wrongly, u will not be able to flash that file. . Try others methods first... Hope it works
AndriyEtch said:
Thanks I'll give those a shot once I'm home from work! Quick question about editing the META INF. I've heard that doing so risks hard-bricking the device. Is that true?
Click to expand...
Click to collapse
Hi OP, sorry for joining late to the party
So the thing is the OnePlus X is at opposites now since the official MM release on 29th September. The thing is if you are running the old bootloader (OxygenOS 2.x.x) or any ROM based on it, then the New TWRP will not boot, neither will the Stock Recovery that is hosted on the OnePlus download section for the X, which is where i assume you download the stock recovery from, right ? Also note that the official recovery hosted on the TWRP website is also yet to be updated, we're working on that.
So you are on the old Bootloader. Simple stuff. I have posted my guide a lot of time around the forums, its gained a lot of merit. You could follow it for your update process. I'll leave a link below. In case you wanna verify that the old bootloader is causing the issue my Index Thread pinned in the general section has a link for the Stock recovery for Old bootloader, try flashing that via fastboot, if it successfully boots then you're set.
Comprehensive guide to Update to Marshmallow Bootloader
The above guide is centered to the thread i have posted it on but the process is 99% the same. In the end, you could just stay with Oxygen OS 3.1.3, or flash any custom ROM based on the new Bootloader.
Now regarding your query about editing the META of the ROM, well Yes to an extent it IS risky if you ain't careful because my guide guides you to delete the one single line that removes the device check, so as long as you use the modified zip on OnePlus X only, there will be no issues.
Let me know for any further clarifications, also you're welcome to join our support group on Telegram, all of our developers are active there. Ping me (@ mellogang_unite) for an invite
I'm trying to root a friend's Metro LG Aristo MS210 7.0, what method works for rooting this phone?
Msjoannalynn said:
I'm trying to root a friend's Metro LG Aristo MS210 7.0, what method works for rooting this phone?
Click to expand...
Click to collapse
https://androidforums.com/threads/recovery-twrp-v3-for-lg-aristo-metropc-t-mobile.1117942/
Messi got you covered.
Personally I would recommend against rooting right now. There isn't much to be done with the Aristo at this point in time except to make backups of your system. Most you'll end up doing is learning a few things about why mixing system based and systemless mods can lead to pretty unpredictable results.
ninjasinabag said:
There isn't much to be done with the Aristo at this point in time except to make backups of your system.
Click to expand...
Click to collapse
This is exactly what I've wanted to do - preferably by having direct rw access to the flash, like I did on my old phone. Unfortunately the only viable custom recovery procedure right now (messi2050's) involves wiping the userdata partition (unless you somehow happen to have an unlocked bootloader). To make matters worse the userdata partition is encrypted AFAIK. Surely the keys are stored on the phone somewhere but there wouldn't be a way to get them without some exploit, and I don't know if this phone is popular enough for someone to bother researching and publishing an exploit.
There was some progress here (github.com/Lekensteyn/lglaf) on reversing and exploiting LG's LAF protocol in their recovery OS, but it hasn't been updated for more than a year now. If anyone wants to play around with that code, be sure to read this issue (github.com/Lekensteyn/lglaf/issues/7) which has ongoing attempts at reversing LAF's current auth methods. I don't have the time right now to dive into this unfortunately.
messi2050 said:
https://androidforums.com/threads/recovery-twrp-v3-for-lg-aristo-metropc-t-mobile.1117942/
Click to expand...
Click to collapse
reboot into fastboot [ adb reboot bootloader ]
- fastboot oem unlock [ this is going to wipe your data ]
how do i do this any one got any video tutorial for all of this ?
@Messi help
1118niranjan said:
reboot into fastboot [ adb reboot bootloader ]
- fastboot oem unlock [ this is going to wipe your data ]
how do i do this any one got any video tutorial for all of this ?
@Messi help
Click to expand...
Click to collapse
You need to do some search yourself
messi2050 said:
You need to do some search yourself
Click to expand...
Click to collapse
i saw your post in android form they've said u are the best guy to help any link if u can ?
1118niranjan said:
i saw your post in android form they've said u are the best guy to help any link if u can ?
Click to expand...
Click to collapse
Power your phone off.
Hold VOL DOWN WHILE PLUGGING DEVICE INTO COMPUTER WITH USB - this will bring it to the fastboot screen. If you have all drivers installed then you can simply open a cmd window and type "fastboot oem unlock" - which should unlock the bootloader - if all drivers are installed. Then continue with the tutorial as usual.
Is root worth it
So, I have an LG ms210 (Lg Aristo) that I've own for a little over 3 months now, but i have been experiencing this issue since about 1 week into ownership. The phone seams to have a RAM leak or something similar as about every hour it slows down substantially, usually to the point of freezing, or crashing all together and restarting on its own, even if not being touched since I power it on. Ive been thinking about rooting it to debloat, but im not sure if it will help, or if i should just invest in a new handset. I have since factory reset it, deleting more high-resource apps, and leaving it bare-bones system apps and nothing else, but the problem still persists. The carrier i MetroPCS if thats a factor, but i dont see why it would be. Any thoughts?
Rooted mine! Thanks to the modified twrp. I couldn't get into it for alost a week, then had a system update that rebooted me right to it, still had the super su zip in sd card so i flashed it and the no verity zip THANKS OP!!??
captnbluebeard said:
Rooted mine! Thanks to the modified twrp. I couldn't get into it for alost a week, then had a system update that rebooted me right to it, still had the super su zip in sd card so i flashed it and the no verity zip THANKS OP!!
Click to expand...
Click to collapse
If you still have trouble reaching recovery after this, either download an advanced shutdown prompt from the market. (There's one literally called advanced reboot) or you can download a terminal emulator app and use the reboot recovery command with root.
su
reboot recovery
ninjasinabag said:
If you still have trouble reaching recovery after this, either download an advanced shutdown prompt from the market. (There's one literally called advanced reboot) or you can download a terminal emulator app and use the reboot recovery command with root.
su
reboot recovery
Click to expand...
Click to collapse
I did that already, im trying to get xposed up and running but my model #lvl3 doesnt match what is in the terminal in twrp. I still get a weird error ph4u
Most likely shows as the lg stylo 2 plus as I guess your using the lineage backup. So just use the model of the lg stylo 2 in terminal? Guessing as I don't use xposed. What do you use xposed for?
To get it running on the aristo is to either edit build prop values to match the ms210 model, or remove the device requirements from xposed's update binary.
failed remote cannot flash this partition in unlocked state.
Anyone?
can some walk me thru this idk what im doing wrong but i go into adb i reboot bootloader and when i try to fastboot oem unlock it says device not found what am i doing wrong?
question
does this root works for lg ms210 security patch level jan 1 2018?
I believe the root is just twrp so it should work fine. Just update first then follow the steps for flashing twrp and the most recent magisk and probably dm verity thing. If something fails it can be eaily reflashed with the original firmware with correct software and the firmware image/kdz.
Edit: try to reinstall the lg drivers? Also a try a tool called minimal adb and fastboot here
Help. It just staus on "" waiting for device " with oem unlock step
Before rooting your phone , it is necessary to backup data for your phone .
Hi all,
tl;dr: Tried to hard unbrick my Oneplus X, which was partly succesful (no OS is installed in the process, while there should be). I am now stuck with no OS and only the Oneplus recovery. I want to install an OS, but it says my bootloader is locked. To unlock it, I need an OS ==> vicious circle.
Full story below:
Recently I've decided to reinstall LineageOS on my Oneplus X because I had quite some problems with it (battery drain, apps crashing, wifi slow to connect, ...). I've done it like 5 times before on this device for various reasons, so I didn't expect any problems. I had LineageOS 14.1 and TWRP 3.0.3 installed. When I wiped everything, I wanted to flash the ROM I had ready using TWRP. However, gave an error number 7, saying that the ROM is not compatible for the device, which I am sure was. Remembering I had a similar issue a while back, I installed flashed an updated version of TWRP (3.2.2) using TWRP itself. That was successfull, but here's where the trouble began.
I noticed that TWRP didn't recognise any storage (Internal storage, SD card and USB-OTG all showed up as 0 MB) any longer. Neither could I mount any of the storages. I've tried a lot of things to solve this. After a while, I decided that the only hope left was the 'mega unbrick guide' (https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-x.417648/) which claims to be able to recover any device, unless it has a hardware problem. I got good hope as I got near the end of the guide. The last step says 'Disconnect phone from PC and boot into system', but here I got stuck on the Oneplus boot logo, making me think that there is no OS installed on the device.
I can still access the recovery using power button and volume down, but the recovery that the mega unbrick guide installs, is the limited Oneplus recovery. It allows to install a ROM from the local storage, or from USB using adb sideload. When I try option 1, nothing happens, no new screen opens or anything. When I try option 2, I enter the adb sideload mode which would normally allow me to sideload a ROM using my pc. My pc confirms I'm in adb sideload mode, and I try to sideload a ROM. It starts fine, but after a few seconds, it says 'Installation failed'. I've tried stock OOS, latest OOS as well as LineageOS 14.1 that was installed before.
Another thing that I can do in the Oneplus recovery is rebooting into fastboot mode, where I should be able to flash the recovery of my choice. Again, my phone confirms I'm in fastboot mode and I try to flash or boot TWRP recovery, but I get the message: 'FAILED (remote: Device not unlocked cannot flash or erase)'. Okay, seems like the bootloader is still locked, so I should just go and unlock it using 'fastboot oem unlock'. This gives the message: 'FAILED (remote: oem unlock is disabled)'. I've been searching around a lot on the internet, and it seems like the only way to enable oem unlock, is in the OS itself in the developer settings. But the problem is, I have no OS and cannot install one because the bootloader is not unlocked... So I'm stuck in this vicious circle.
I've been searching on the internet for hours and starting to lose hope. At this point, I would be happy if I can just have any OS (OxygenOS or LineageOS or something else) running. If I have that, I should be able to take it from there.
Any help is much appreciated. Thank you very much.
Kind regards,
Jeroen
Bump
Update:
Oneplus support could solve the problem for me! Or at least, partly. It appears that Oneplus has an updated version of the tool used in the mega unbrick guide: MSMDownloadTool V2.1 instead of V2.0. This tool did it's job perfectly, OOS was also installed, in contrast to V2.0 of the tool. I ****ed it up again after that (oops), but found the tool V2.1 online here (https://github.com/finlayacourt/Oneplus-X-Recovery). Some files are missing here like the system.img, but I just copied them from the folder of tool V2.0 found in the mega unbrick guide. It didn't work as perfectly as Oneplus's tool, but at least I was able to install OOS from the Oneplus bootloader, which I wasn't able to before. So knowing that, in the end, the result is the same as for their tool. A working OS again, perfect! So now I can unlock the bootloader again and continue the adventure.
Now, what I've found is that the mainboard I have on my OPX is a newer version (if you search on Google for 'oneplus E1003_15', you'll find some things about it, not much though). I'm 99% positive that this caused all the problems I've encountered. It is why TWRP couldn't see any storage, why the stock Oneplus recovery couldn't see any storage, why the tool V2.0 didn't work and why V2.1 did work. If I wanted a working TWRP, I had to install a modified version of TWRP which is compatible with the newer version, from here: https://www.android-hilfe.de/forum/...-1-oreo-rom-unofficial-onyx-8-1-x.867374.html (yes, once you're relying on German sites, you know you went very deep). After that, I could install LineageOS 14.1 again. I was unable to install the unofficial LineageOS 15.1 however, but knowing where I came from, what I've gone through and how much time I've lost on all of this, I think I'll just stick with LineageOS 14.1 until this baby can retire...
Got to say I only have very positive experiences with Oneplus and it's customer support, and this only adds to it!
I hope I can also help other people with the same problem.
Japeroen said:
Update:
Oneplus support could solve the problem for me! Or at least, partly. It appears that Oneplus has an updated version of the tool used in the mega unbrick guide: MSMDownloadTool V2.1 instead of V2.0. This tool did it's job perfectly, OOS was also installed, in contrast to V2.0 of the tool. I ****ed it up again after that (oops), but found the tool V2.1 online here (https://github.com/finlayacourt/Oneplus-X-Recovery). Some files are missing here like the system.img, but I just copied them from the folder of tool V2.0 found in the mega unbrick guide. It didn't work as perfectly as Oneplus's tool, but at least I was able to install OOS from the Oneplus bootloader, which I wasn't able to before. So knowing that, in the end, the result is the same as for their tool. A working OS again, perfect! So now I can unlock the bootloader again and continue the adventure.
Now, what I've found is that the mainboard I have on my OPX is a newer version (if you search on Google for 'oneplus E1003_15', you'll find some things about it, not much though). I'm 99% positive that this caused all the problems I've encountered. It is why TWRP couldn't see any storage, why the stock Oneplus recovery couldn't see any storage, why the tool V2.0 didn't work and why V2.1 did work. If I wanted a working TWRP, I had to install a modified version of TWRP which is compatible with the newer version, from here: https://www.android-hilfe.de/forum/...-1-oreo-rom-unofficial-onyx-8-1-x.867374.html (yes, once you're relying on German sites, you know you went very deep). After that, I could install LineageOS 14.1 again. I was unable to install the unofficial LineageOS 15.1 however, but knowing where I came from, what I've gone through and how much time I've lost on all of this, I think I'll just stick with LineageOS 14.1 until this baby can retire...
Got to say I only have very positive experiences with Oneplus and it's customer support, and this only adds to it!
I hope I can also help other people with the same problem.
Click to expand...
Click to collapse
Greatly appreciate your feedback here. I think that I am in the same situation you were. Used what you suggested - using MSM v2.1 that you provided with the system.img, non-hlos and userdata.img from MSM v2.0. The process ends with "Download Complete" written in green but when I check "Verify" it fails exactly @system.img, userdata and non-hlos. I can't boot recovery either after these.
Do you have any clue as to why it is so?
gabytzu338 said:
Greatly appreciate your feedback here. I think that I am in the same situation you were. Used what you suggested - using MSM v2.1 that you provided with the system.img, non-hlos and userdata.img from MSM v2.0. The process ends with "Download Complete" written in green but when I check "Verify" it fails exactly @system.img, userdata and non-hlos. I can't boot recovery either after these.
Do you have any clue as to why it is so?
Click to expand...
Click to collapse
As far as I know, I haven't used the "Verify" button. Right after the green "Download Complete" line, I booted into the OOS stock recovery by pressing volume down and power button (I think? Not sure anymore, I always forget it). From there, I could install OOS with a official ROM image.
Are you sure you moved the correct files from V2.0 to V2.1? The way I knew which files to move, is by first starting the V2.1-program without any added files. Then it told me 'system.img missing' (or something like that), so I knew I had to add that. After adding that, I ran the program again and added the next file it said it was missing etc etc.
Sucks to hear your recovery process doesn't go as "smooth" (it's all relative of course) as mine.
Japeroen said:
As far as I know, I haven't used the "Verify" button. Right after the green "Download Complete" line, I booted into the OOS stock recovery by pressing volume down and power button (I think? Not sure anymore, I always forget it). From there, I could install OOS with a official ROM image.
Are you sure you moved the correct files from V2.0 to V2.1? The way I knew which files to move, is by first starting the V2.1-program without any added files. Then it told me 'system.img missing' (or something like that), so I knew I had to add that. After adding that, I ran the program again and added the next file it said it was missing etc etc.
Sucks to hear your recovery process doesn't go as "smooth" (it's all relative of course) as mine.
Click to expand...
Click to collapse
Hah, did not expect an answer, I've seen your thread on oneplus forums as well, glad you were so quick to answer here. I've found the MSM2.1 uploaded in a google drive with all the files afterwards, after some long hours of searching too. Anyway, I still can't adb sideload anything, the storage seems 'corrupted' to say the least, but there are imporvements from MSM v2.0 and v3.0 flahses. The recovery menu works flawlessly now, no artifacts or freezes, also the phone 'almost' booted. It went to the "Updating android apps" thing.
I don't really know what to do next. Recovery does not help me at all. I can't sideload anything, it renders a "protocol fault" error. Internal storage has 2 empty folders within and that's about it. Also the bootloader is locked now and I can't make any use of fastboot mode.
gabytzu338 said:
Hah, did not expect an answer, I've seen your thread on oneplus forums as well, glad you were so quick to answer here. I've found the MSM2.1 uploaded in a google drive with all the files afterwards, after some long hours of searching too. Anyway, I still can't adb sideload anything, the storage seems 'corrupted' to say the least, but there are imporvements from 2.0 and 3.1 flahses. The recovery menu works flawlessly now, no artifacts or freezes, also the phone 'almost' booted. It went to the "Updating android apps" thing.
I don't really know what to do next. Recovery does not help me at all. I can't sideload anything, it renders a "protocol fault" error. Internal storage has 2 empty folders within and that's about it. Also the bootloader is locked now and I can't make any use of fastboot mode.
Click to expand...
Click to collapse
Haha I know the feeling! But thanks to e-mail notifications.
I also thought that my storage was corrupted at first, given the symptoms I described in my first post, so I didn't expect my OPX to be revived, but hey it's still alive now.
I also had the locked bootloader-thing. The way I could unlock it, is by first installing OOS using the stock recovery (which was installed using the tool), then unlocking it in OOS, so I could install another recovery and eventually another OS.
I'm afraid I already explained the problems I encountered and the procedure I followed pretty detailed. If you have anything that deviates from this, I'm sorry to say that I can't really help you with that, even if I wanted to. Did you perform the exact steps I mentioned (including the V2.1-tool that I linked to)? What exactly do you mean with the "3.1 flash"?
It's also already 2 months ago, so I don't even know exactly what I've done apart from what I've described...
Japeroen said:
Haha I know the feeling! But thanks to e-mail notifications.
I also thought that my storage was corrupted at first, given the symptoms I described in my first post, so I didn't expect my OPX to be revived, but hey it's still alive now.
I also had the locked bootloader-thing. The way I could unlock it, is by first installing OOS using the stock recovery (which was installed using the tool), then unlocking it in OOS, so I could install another recovery and eventually another OS.
I'm afraid I already explained the problems I encountered and the procedure I followed pretty detailed. If you have anything that deviates from this, I'm sorry to say that I can't really help you with that, even if I wanted to. Did you perform the exact steps I mentioned (including the V2.1-tool that I linked to)? What exactly do you mean with the "3.1 flash"?
It's also already 2 months ago, so I don't even know exactly what I've done apart from what I've described...
Click to expand...
Click to collapse
It was a typo, I meant v2.0 and v3.0(for oneplus 3). The op3 unbrick guide suggested that the v3.0 might work for oneplus x as well, so I tried that out too.
Anyway, I've done the process a couple more times and the phone booted untill you set the device up, when you are finished it just reboots. I can see the lock screen, I can't bring down the upper bar or enter the settings, if unlocked it prompts me to the first time set up and upon it's completion the phone reboots. I wiped cache,data did a factory reset. Now it's back with the recovery menu artifacts and not booting anymore either. I will use that tool a couple more times then I am done until further suggestions from this forum. After all, my life does not depends on reviving it, I was gonna give it to my brother, who shattered his phones' touchscreen, until he repairs his. Thank you again for replying, no need to reply to this, unless it can help my case.