Related
TWRP 2.8.5.0 YotaPhone 2 recovery imageAfter the bare bones modded stock recovery for YotaPhone 2 it's time for something more advanced. The TeamWin Recovery Project 2, or TWRP2 is just that: a fully fledged, graphical, touch enabled, custom recovery.
This recovery image for YotaPhone 2 is still an alpha version, so expect some rough edges. Which leads me to:
Disclaimer
I am not responsible for damaged or bricked devices. If you follow instructions in this post, then YOU are making the choice to tinker with your device. You are likely to void your warranty by doing so, and on a bad day you might even damage or brick your device.
What is it?
It's a recovery image for YotaPhone 2 based on TWRP2 custom recovery, and the stock kernel from Yota Devices. You can boot it ad-hoc, or flash it permanently to the recovery partition. Use it to root, install software, make backups, update ROMs etc.
What can you do with it?
- adb root & shell access
- All TWRP 2.8.5.0 functionality (except MTP)
- install update zips (signed with testkeys (e.g. SuperSU), Yota Devices software, and also unsigned zips like Xposed framework.
- You can sideload packages, but also install them from internal storage (e.g. Download folder)
- make partition backups
- root your device
What can it NOT do?
- In this recovery image the MTP functionality of TWRP is disabled, it doesn't play nice with YD's kernel.
What do you need?
- YotaPhone 2 (YD201) with Lollipop 5.0
- Some technical confidence to cope with quirks that come with an alpha version
- USB cable with a PC or laptop on one end
Steps overview:
NOTE: I used less detail in this post than the previous recovery thread, please look there for more detail.
1) backup (sync stuff, copy photos off, use a backup app etc, use search if unsure how to)
2) Install adb and fastboot if not yet installed. (For Windows look e.g. here, for linux the fastest is probably to install Android SDK with platform tools, see here If this is not enough info to get you started, please use xda search!)
3) Unlock the bootloader if you haven't done so before (read warning below!)
4) Download recovery image: recovery_twrp_yd201_alpha2.img
5) boot or flash the recovery image
Unlocking bootloader:
Warning: It is currently not known how to re-lock the bootloader. This means you cannot completely undo the next step as of yet. This might have consequences for sending the device in for repairs, if they check for this, and deem it a (warranty) problem.
See stock recovery thread for unlock steps
BOOT the recovery image:
a) First: put the device in fastboot/download mode:
Power off with USB cable disconnected, then hold volume down key while inserting USB cable (which should already be in your PC on the other end).
You should see a black screen with a tiny white: downloading...
b) Boot the recovery image:
Code:
fastboot boot path/to/recovery_twrp_yd201_alpha2.img
Alternatively, flash the recovery image (overwriting the stock recovery):
Code:
fastboot flash recovery recovery_twrp_yd201_alpha2.img
Problems & FAQ
Q: It doesn't work!!1!
A: Please provide plenty of detail about error messages, which step, what versions etc. Without providing any detail you'll look silly. TWRP has it's own logfile that you can copy to (virtual) SD card, and access from there.
Kernel sourcecode:
In this recovery image is Yota Device's version of the Linux kernel v3.4.0 for YotaPhone 2. Yota Devices are required by the GPLv2 license to release the source code for this kernel, but so far they haven't taken that step or even shown intention to do so as far as I know. The YotaPhone firmwares and also this recovery image are in effect violating the GPLv2 license if the situation does not change. Attempts to contact Yota Devices on the subject through support, press departement, and an attempt to contact Yota Device's management, have gone pretty much unanswered as of writing. I'm hoping they're just busy making great devices instead of being unwilling.
If you would like to help future custom ROM development for YotaPhone 2 please do the following:
Encourage Yota Devices through their twitter or facebook accounts to publish the Kernel sourcecode for YotaPhone 2, and ask them to support the open source Android community. You can also submit a request through their support page (hint: choose 'sales' as category, otherwise you'll have to enter lots of details. Be polite!).
Info & credits::
TWRP2 is created and maintained by TeamWin. Please donate through their site if you enjoy their work!
Recovery image for YP2: SteadyQuad
Version: alpha2 based on TWRP 2.8.5.0 with Yota Devices kernel (1.39 EU1)
Thanks to: TeamWin for TWRP, @Dees_Troy for hints for getting it up and running, @Jeopardy for testing, @Chainfire for SuperSU and lastly Yota Devices for a great device.
Linking to this recovery image:
Please don't link directly to the download image, link to this post instead. That way users can get the most recent version and any updated info. (It's an alpha version after all)
Created: 2015-06-23
Last Updated: 2015-06-24
SteadyQuad said:
If you would like to help future custom ROM development for YotaPhone 2 please do the following:
Encourage Yota Devices through their twitter or facebook accounts to publish the Kernel sourcecode for YotaPhone 2, and ask them to support the open source Android community. You can also submit a request through their support page (hint: choose 'sales' as category, otherwise you'll have to enter lots of details. Be polite!).
Click to expand...
Click to collapse
I just approached Yota for the Yotaphone 2 kernel's source code, and they gave me a link to Yotaphone's developer page (https://yotaphone.com/developer/). It's not there (yet). Maybe they'll release the source code once they finalize the SDK...? That, or the recipient of my query didn't understand the question.
Regarding the recovery: works flawlessly. :good:
Jeopardy said:
I just approached Yota for the Yotaphone 2 kernel's source code, and they gave me a link to Yotaphone's developer page (https://yotaphone.com/developer/). It's not there (yet). Maybe they'll release the source code once they finalize the SDK...? That, or the recipient of my query didn't understand the question.
Regarding the recovery: works flawlessly. :good:
Click to expand...
Click to collapse
Yeah, I got the same boxed response and replied that it was not relevant, and explained why. Their SDK (for app development) has nothing to do with the kernel sourcecode, and at the moment their developer pages do not mention anything about kernel sources. I think that their support page tickets are handled by an external company (quicksupportlink.com), that is dependent on Yota for definitive answers, and they're probably instructed to send this reply. At least Yota will get reports from them, with hopefully lots of requests for kernel source. On the press page there's email addresses of 2 press ladies, you could try those too (as I did).
So nice to see this! Looking forward to trying, once mine comes.
Jeopardy said:
I just approached Yota for the Yotaphone 2 kernel's source code, and they gave me a link to Yotaphone's developer page (https://yotaphone.com/developer/). It's not there (yet). Maybe they'll release the source code once they finalize the SDK...? That, or the recipient of my query didn't understand the question.
Regarding the recovery: works flawlessly. :good:
Click to expand...
Click to collapse
Hi Jeopardy,
Next great mod by you! Congrats! :good:
BTW: Does it mean that your version of TWRP recovery doesn't work with 1.44 EU firmware?
Or if I flash this recovery it will work, but the kernel is one step back to 1.39 version?
Thanks in advance for the info.
Regards!
zencooler said:
Hi Jeopardy,
Next great mod by you! Congrats! :good:
BTW: Does it mean that your version of TWRP recovery doesn't work with 1.44 EU firmware?
Or if I flash this recovery it will work, but the kernel is one step back to 1.39 version?
Thanks in advance for the info.
Regards!
Click to expand...
Click to collapse
This recovery is done by SteadyQuad, only tested by me.
But I can answer your question: this recovery works just fine with 1.44 EU firmware. I have flashed it myself successfully. I'm quite sure it is not tied to the firmware version in any way.
Jeopardy said:
This recovery is done by SteadyQuad, only tested by me.
But I can answer your question: this recovery works just fine with 1.44 EU firmware. I have flashed it myself successfully. I'm quite sure it is not tied to the firmware version in any way.
Click to expand...
Click to collapse
Hi again,
Soory for the mistake (I just replied not for the first post). Once again sorry SteadyQuad and congrats for you again!
Jaopardy, thanks for the quick info and confirmation it works on 1.44 EU firmware! It's a good news
Regards!
Jeopardy said:
...Yotaphone 2 kernel's source code...
Click to expand...
Click to collapse
https://srv-fs1.yotadevices.com/public/file/5OyPZKU7Vk6HvML_YZpuRQ/yotaphone2_kernel.tar.gz
elatllat said:
https://srv-fs1.yotadevices.com/public/file/5OyPZKU7Vk6HvML_YZpuRQ/yotaphone2_kernel.tar.gz
Click to expand...
Click to collapse
Thanks, this archive was already known, it contains a kernel snapshot of end of june 2015. I put it on github with some small adjustments to make it build initially. (and it actually boots
I've also put up an initial device and vendor tree there, although both are pretty far from complete/correct at this point.
BTW @elatllat where did you get the link from?
SteadyQuad said:
...where did you get the link from?
Click to expand...
Click to collapse
I did a xda forum search and found that link, this thread, and thought I should link them up.
(as it's not widely known)
so anyone tried xposed??
varun.gid said:
so anyone tried xposed??
Click to expand...
Click to collapse
Yeah. It works as expected. No problems for me.
Has any flashed this recovery permanently over 1.60
Sent from my YD201 using Tapatalk
adamo86 said:
Has any flashed this recovery permanently over 1.60
Sent from my YD201 using Tapatalk
Click to expand...
Click to collapse
You can use this TWRP recovery image with 1.60 just fine (the recovery image is pretty much independent of firmware version).
SteadyQuad said:
You can use this TWRP recovery image with 1.60 just fine (the recovery image is pretty much independent of firmware version).
Click to expand...
Click to collapse
I am having this issue with my yotaphone the epd freezen for a long time I'm not sure if it's twrp. At the moment I flashed the stock modified recovery and it stopped freezing for the last 24hrs i will report back in a few days
Sent from my YD201 using Tapatalk
adamo86 said:
I am having this issue with my yotaphone the epd freezen for a long time I'm not sure if it's twrp. At the moment I flashed the stock modified recovery and it stopped freezing for the last 24hrs i will report back in a few days
Sent from my YD201 using Tapatalk
Click to expand...
Click to collapse
TWRP is only doing anything when you boot into recovery. When you're just using your phone normally, Android doesn't even know about TWRP. So your EPD freezing must be something else.
May be my phone is dieing?
Sent from my YD201 using Tapatalk
SteadyQuad said:
TWRP is only doing anything when you boot into recovery. When you're just using your phone normally, Android doesn't even know about TWRP. So your EPD freezing must be something else.
Click to expand...
Click to collapse
Your right my phone is bust does anyone have yota contact details
Sent from my YD201 using Tapatalk
adamo86 said:
Your right my phone is bust does anyone have yota contact details
Have you done a factory reset?
My EPD was freezing and system clock screwing up. Factory reset, wiped caches etc, then cleared out a few apps didn't need and some system crap, seems to be ok now. Battery drain still occurs but I'm resigned to that unfortunately, just hoping 5.1 fixes the issue (and that we get it soon.).
If nothing works you could try emailing [email protected], hopefully you get somewhere. Their customer service was very good initially for me but seems to take a very long time to get anything done nowadays.
Either way good luck and I hope your phone gets some decent function back eventually .
Click to expand...
Click to collapse
zute333 said:
adamo86 said:
Your right my phone is bust does anyone have yota contact details
Have you done a factory reset?
My EPD was freezing and system clock screwing up. Factory reset, wiped caches etc, then cleared out a few apps didn't need and some system crap, seems to be ok now. Battery drain still occurs but I'm resigned to that unfortunately, just hoping 5.1 fixes the issue (and that we get it soon.).
If nothing works you could try emailing [email protected], hopefully you get somewhere. Their customer service was very good initially for me but seems to take a very long time to get anything done nowadays.
Either way good luck and I hope your phone gets some decent function back eventually .
Click to expand...
Click to collapse
I got rid of it I tried everything downgraded wiped data etc clean install then did ota still freezes after a while. I did clean install of Rom twice. I think the screen is dying or something inside it is loose because the epd started off as freezes then moved to very light grey instead of black and would refresh but old pics and widget would be visible and it started to flicker from one side then it would start to work after a while then fade again etc. When these freezes happened I would get a blue screen when phone was rebooted and it would slow device down then reboot it self until the screen got unfrozen. I noticed even after installing rom new the screen would some time be frozen. It's only sometimes the screen would be reseted if I did a new installation.
I will miss my yotaphone. I will be getting a nexus 6p or v10.
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
Disclaimer
**** All flashing is done at your own risk! ****
**** While this recovery should not break your device, don't come back here blaming anyone if it does! ****
This is a TWRP 3.2.3 build based on Android 7.1.2 source kernel for the Galaxy Tab Active 2 (codename: gtactive2lte) - Exynos. The "tar" file should be installed using Odin (tested on Odin 3.12.3).
Special Notes:
1. DON'T FORGET TO ENABLE "OEM UNLOCK" (located in Developers options, if its not there, you may have to wait for a few days to access that option, some users claim that its within 10 days before this option appears).
2. KNOX will be tripped once you flashed custom binaries to your phone.
3. Samsung Firmware OTA (aka System Updates) will no longer work once you flashed custom binaries.
(You can flash custom ROMs if you want to keep the OS up-to-date.)
4. It is HIGHLY UNRECOMMENDED to purchase any access to any kind of private forums, ROMs or Kernels.(DO NOT GET FOOLED.)
Installation process:
1. Flash Stock ROM.
2. Flash recovery using Odin (AP = recovery.tar).
3. Load recovery immediately after flashing.
4. Format data (Will erase /data partition).
5. Reboot to recovery.
6. ADB push SuperSU to internal storage / insert SD-Card with SuperSU.zip.
7. Flash SuperSU using TWRP install option.
8. Reboot to system (May bootloop several times. Wait untill system loads).
Bugs:
1. ADB sometimes doesn't work in MTP mode. Need to manually change to PTP in order to get adb usage.
2. Bad label in ADB shell + bad characters appearing while writing through AD. Works well out of recovery and on recovery's terminal.
Sources:
Device tree - Device tree
Kernel - Kernel
TWRP sources - platform_manifest_twrp_omni
SuperSU - SuperSU-2.82-SR5
Recovery download:
Recovery
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 08/19/2018 (DD/MM/YYYY)
Contributors:
Many thanks to TWRP's developers for the support on building this recovery.
Special thanks to CaptainThrowback, Bigbiff and Dees_Troy on TWRP-freenode and Ashyx on xda-developers.
Please post any bugs you encounter. I will try to fix any issues that come up.
Thanks for the work and sharing. I'm excited to try. Having root would be great, but I'd also like to be able to make voice calls ( using bluetooth as the built-in speaker & microphone aren't adequate ). Do you think this is possible. What changes, if any, are required to have work with T397 Tab Active 2 ( US variant ) ? I'm sure that it's mobile frequencies are different than what the euro-spec'd T395, but otherwise I think identical.
Slomo
slomo2 said:
Thanks for the work and sharing. I'm excited to try. Having root would be great, but I'd also like to be able to make voice calls ( using bluetooth as the built-in speaker & microphone aren't adequate ). Do you think this is possible. What changes, if any, are required to have work with T397 Tab Active 2 ( US variant ) ? I'm sure that it's mobile frequencies are different than what the euro-spec'd T395, but otherwise I think identical.
Slomo
Click to expand...
Click to collapse
Well, Samsung has a nice repo of their source kernels for every phone Samsung sources
I guess we just have to validate some data taken from boot.img from the stock rom and then build the same with the appropriate source kernel.
Shedaim said:
Well, Samsung has a nice repo of their source kernels for every phone Samsung sources
I guess we just have to validate some data taken from boot.img from the stock rom and then build the same with the appropriate source kernel.
Click to expand...
Click to collapse
Had no idea the source was available for these devices, thanks for sharing. T397 source is in the repository. Let me know if there is something that I can do to assist. I've not compiled these sources although I've compiled other things. Possible to use this tablet as a phone with this ROM as stock T397 ( even after installing several different dialers does not dial ) ?
slomo2 said:
Had no idea the source was available for these devices, thanks for sharing. T397 source is in the repository. Let me know if there is something that I can do to assist. I've not compiled these sources although I've compiled other things. Possible to use this tablet as a phone with this ROM as stock T397 ( even after installing several different dialers does not dial ) ?
Click to expand...
Click to collapse
I can't check the dialer thing, as I don't even have cellular network on my Tablet.
I'll try to build the recovery for the T397 later today, but you will have to check it I guess, as I have no access to that one.
Shedaim said:
I can't check the dialer thing, as I don't even have cellular network on my Tablet.
I'll try to build the recovery for the T397 later today, but you will have to check it I guess, as I have no access to that one.
Click to expand...
Click to collapse
This will be great, let me know if I can help, perhaps document.
slomo2 said:
This will be great, let me know if I can help, perhaps document.
Click to expand...
Click to collapse
Ok, so this is a first try, so I believe it's not going to work, but who knows? we may get lucky.
Recovery for SM-T397 - Android 7.1.2
If it doesn't get installed or leads to a bootloop, I'm gonna need you to pull the boot.img from your device, or send me a link of the stock ROM if it's available.
Please follow the intsallation process described on the README file on the github repository
Shedaim said:
Ok, so this is a first try, so I believe it's not going to work, but who knows? we may get lucky.
Recovery for SM-T397 - Android 7.1.2
If it doesn't get installed or leads to a bootloop, I'm gonna need you to pull the boot.img from your device, or send me a link of the stock ROM if it's available.
Please follow the intsallation process described on the README file on the github repository
Click to expand...
Click to collapse
Thank you! Successfully installed. I found this video helpful for this generation of Samsung device and learning how to navigate recovery and download modes. I disabled auto-reboot in ODIN per your instructions, but it wasn't clear to me how to power-off after download so as to be able to go into recovery without booting so after adequate time I just pulled the battery. I'll spend the evening playing with things and report back, but so far everything seems to be working
---------- Post added at 11:27 PM ---------- Previous post was at 11:15 PM ----------
slomo2 said:
Thank you! Successfully installed. I found this video helpful for this generation of Samsung device and learning how to navigate recovery and download modes. I disabled auto-reboot in ODIN per your instructions, but it wasn't clear to me how to power-off after download so as to be able to go into recovery without booting so after adequate time I just pulled the battery. I'll spend the evening playing with things and report back, but so far everything seems to be working
Click to expand...
Click to collapse
One thing I notice, 7.1.1 is what was/is installed on my tablet now. Not sure what version of Android available on Samsung Opensource or how to check it, but I suspect it is the same since nothing has been pushed OTA.
7.1.1 is what The T397U should have already been on before you started. Mine is and I have not installed this recovery as of yet. Just wanted to let you know it's where it should be.
slomo2 said:
Thank you! Successfully installed. I found this video helpful for this generation of Samsung device and learning how to navigate recovery and download modes. I disabled auto-reboot in ODIN per your instructions, but it wasn't clear to me how to power-off after download so as to be able to go into recovery without booting so after adequate time I just pulled the battery. I'll spend the evening playing with things and report back, but so far everything seems to be working
---------- Post added at 11:27 PM ---------- Previous post was at 11:15 PM ----------
One thing I notice, 7.1.1 is what was/is installed on my tablet now. Not sure what version of Android available on Samsung Opensource or how to check it, but I suspect it is the same since nothing has been pushed OTA.
Click to expand...
Click to collapse
Awesome. I really had my doubts being it the first build and all. I guess, there aren't really any major differences.
If it's possible, can you go through the TWRP checklist here
Some of the tests aren't really necessary, but it's a good checklist to go by anyway.
That way, I can officially add it to the OP.
Shedaim said:
Awesome. I really had my doubts being it the first build and all. I guess, there aren't really any major differences.
If it's possible, can you go through the TWRP checklist here
Some of the tests aren't really necessary, but it's a good checklist to go by anyway.
That way, I can officially add it to the OP.
Click to expand...
Click to collapse
Sorry for delay. I've done the following tests all with the expected results. The only thing I noticed compared to previous installations of TWRP that I've performed ( some years ago ) is that the load time of recovery seems long at 1:15. Also a message about "RECOVERY NOT SEANDROID ENFORCING" which I suspect is normal. Tablet has been working without incident. Thanks again.
Blocking checks
- Correct screen/recovery size
- Working Touch, screen
- Backup to internal/microSD
- Restore from internal/microSD
- reboot to system
-ADB ( yes, if this means being able to access from ADB while in recovery )
Medium checks
- Screen goes off (and on )
- F2FS/EXT4 Support, exFAT/NTFS where supported
- all important partitions listed in mount/backup lists
===> define important ? - depends on the device, i guess
= Assume we can still boot a recovery (aboot/lk is still there for fastboot), can restore everything left ?
- backup/restore to/from external (USB-OTG) storage
- Correct date
Minor checks
- MTP export
- reboot to bootloader
- reboot to recovery
- poweroff
- battery level
- USB mass storage export
- set brightness
- vibrate
Security Policy Updates should not be applied to this system ?
Since this is stock Samsung OS that is rooted I'm guessing this system is still SELinux "enforcing" so does this mean that I can/should say yes to Security Enhancements automatic updates from Samsung ? Any explanation or link on this matter appreciated.
Hey @Shedaim, thanks a lot for this recovery, would it be possible to release an update for oreo?
maddada said:
Hey @Shedaim, thanks a lot for this recovery, would it be possible to release an update for oreo?
Click to expand...
Click to collapse
Hey, sorry for the very late answer.
I'm currently not working on Android and I've never tried on OREO, so my politically correct answer would be: "Right now there is no plan to work the same magic on OREO, but whoever wants, can try to use the device tree I created with a new official OREO kernel (didn't know they have one already)".
Anyway, keep checking the forum from time to time, I may have found the time to work on it
Links to the device tree and other tools used are in the main page of this thread.
Thank you,
Shedaim
I Pay 100$ for making my Galaxy Tab Active 2 booting when its charging
Hey guys,
i hope somebody can help me.
Im trying since 2 Weeks to make my Galaxy Tab Active 2 booting when its charging.
I try all the ways i found (fastboot, LPM change and Autoboot App) and nothing was successful.
So i hope to find with this way somebody who would help me to get the feature.
I need it because i installed the Active 2 on my Harley Davidson as my navigation.
And the problem is that i make a Novalauncher thats looking like the original Harley Davidson one and starts without a code.
So when i put the Tablet in the Mask i dont get a method to press to power button and when i make a method (hole trough the mask or something) then everybody can start up my tablet and use it.
So if somebody can help me with that i will pay them 100$ for helping!
you can contact me at [email protected].
thanks alot
Excuse me for a moment, but i have a Galaxy Tab Active 2 WIFI (sm-t390) and im looking for a custom recovery for it. All i can find for this model is the SM-T395 variant of TWRP,root, etc. Absolutelly nothing for the SM-T390? Does any one have any ideas???? Thank you in advance either way.
sCOTTN916 said:
Excuse me for a moment, but i have a Galaxy Tab Active 2 WIFI (sm-t390) and im looking for a custom recovery for it. All i can find for this model is the SM-T395 variant of TWRP,root, etc. Absolutelly nothing for the SM-T390? Does any one have any ideas???? Thank you in advance either way.
Click to expand...
Click to collapse
I used the methods and recovery here for my tablet which is a T397U...works flawlessly. The same should work for the wifi T390 you have aswell.
Flash process
I am new to the rooting process. This will be my first time. What is the actual flash process? How do I flash the rom on my tablet?
All the links are dead can anyone please post this recovery
i can Flash this twrp-3.2.3-0-gtactive2lte-7.1.2.tar, Odin says pass, but there is no TWRP. it boots into System. when i stop and boot to recovery, there is stll custom recovery from T395XXU5CSH2.
Any hints?
Ok my friends, it's true that family moto g6 (specifically g6 play) will receive android 10? if it's possitive... When will we have news about this?
Also ... does anyone know if there is any rom in development with android 10 for this model (lineage, RR, etc.)?
If anyone knows about this, I think several would appreciate this valuable information.
Answer 1, just wait for Moto to announce it, usually they announce when there gonna do a soak test of a new Android version so whenever Moto does that will be some sort of answer however soak test usually go on for a few months basically it's prolly gonna be almost another year before we hear anything I mean we just got official pie about 2 months ago now after they did soak test for months.
Answer 2, there is not even a custom rom like rr or anything for this device for Oreo or pie so doubtable. Best you can do is try out gsi A only builds, custom rom means it's made specifically for this device where as gsi is compatible with any phone that shipped with Android 8. There is a gsi thread you can out
Answer 3: Motorola has already confirmed that the Moto G6 Play will only get one major OS upgrade, and being that we got Pie now that's all it will get unless a DEV figures out how to make a custom rom for Android 10.
PimpMy5Ton said:
Answer 3: Motorola has already confirmed that the Moto G6 Play will only get one major OS upgrade, and being that we got Pie now that's all it will get unless a DEV figures out how to make a custom rom for Android 10.
Click to expand...
Click to collapse
I have no WiFi right now or I'd already be trying to build for us. They finally fixed the sources for our phone. Phh has Android 10 GSIs out. They'll boot if you flash the Oreo vendor, oem, and boot images first but it's very alpha at the moment. You also need to flash phh's modified magisk from his first Android 10 release. LTE is broken (3G works), and it has some graphics glitches. Most everything else is working fine though. It's not a daily driver yet but it's getting there fast. It will break LTE on stock. To fix that just flash your firmware and let it setup until it reactivates, then you can restore a backup like normal.
Spaceminer said:
I have no WiFi right now or I'd already be trying to build for us. They finally fixed the sources for our phone. Phh has Android 10 GSIs out. They'll boot if you flash the Oreo vendor, oem, and boot images first but it's very alpha at the moment. You also need to flash phh's modified magisk from his first Android 10 release. LTE is broken (3G works), and it has some graphics glitches. Most everything else is working fine though. It's not a daily driver yet but it's getting there fast. It will break LTE on stock. To fix that just flash your firmware and let it setup until it reactivates, then you can restore a backup like normal.
Click to expand...
Click to collapse
That's cool, I was just adding to the answer as to the number of os upgrades that Moto phones get, as far as Phh's android 10 you should be fine as long as you include vendor partition with your stock backup.
---------- Post added at 08:59 PM ---------- Previous post was at 08:54 PM ----------
@Spaceminer Could you link to the sources for the Moto G6 Play?? I have the XT1922-7 Boost Mobile variant.
PimpMy5Ton said:
That's cool, I was just adding to the answer as to the number of os upgrades that Moto phones get, as far as Phh's android 10 you should be fine as long as you include vendor partition with your stock backup.
---------- Post added at 08:59 PM ---------- Previous post was at 08:54 PM ----------
@Spaceminer Could you link to the sources for the Moto G6 Play?? I have the XT1922-7 Boost Mobile variant.
Click to expand...
Click to collapse
https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-PCP29.118-41
phh built an AOSP 10 test image for us which fixes the bootloop on Pie vendor. I tried it last night and everything seemed to work except sound. LTE works after adding the APN settings.
https://github.com/phhusson/treble_experimentations/issues/792#issuecomment-546130091
ry755 said:
phh built an AOSP 10 test image for us which fixes the bootloop on Pie vendor. I tried it last night and everything seemed to work except sound. LTE works after adding the APN settings.
https://github.com/phhusson/treble_experimentations/issues/792#issuecomment-546130091
Click to expand...
Click to collapse
Glad to have it running with Pie and more stable, those are great news
ry755 said:
phh built an AOSP 10 test image for us which fixes the bootloop on Pie vendor. I tried it last night and everything seemed to work except sound. LTE works after adding the APN settings.
https://github.com/phhusson/treble_experimentations/issues/792#issuecomment-546130091
Click to expand...
Click to collapse
Can you guide us? I install the test img but cant boot on pie vendor
Grom9A said:
Can you guide us? I install the test img but cant boot on pie vendor
Click to expand...
Click to collapse
First flash the latest stock boot.img to remove any leftover traces of Magisk, which is now incompatible with phh's AOSP 10 builds.
After that you'll need to disable encryption and dm-verity, if you haven't already done that:
- Download the dm-verity + forced encryption disabler zip here
- Boot into TWRP, go to Wipe, and press Format Data. This will wipe everything from the internal storage! Make sure you have backups stored somewhere else.
- Reboot > Reboot Recovery
- Copy the disabler zip to your phone and flash it
Now the test image should be able to boot on Pie vendor.
(There might be other/better ways of doing this, but those are the steps that worked for me)
ry755 said:
First flash the latest stock boot.img to remove any leftover traces of Magisk, which is now incompatible with phh's AOSP 10 builds.
After that you'll need to disable encryption and dm-verity, if you haven't already done that:
- Download the dm-verity + forced encryption disabler zip here
- Boot into TWRP, go to Wipe, and press Format Data. This will wipe everything from the internal storage! Make sure you have backups stored somewhere else.
- Reboot > Reboot Recovery
- Copy the disabler zip to your phone and flash it
Now the test image should be able to boot on Pie vendor.
(There might be other/better ways of doing this, but those are the steps that worked for me)
Click to expand...
Click to collapse
Thanks, it works. We need to find a way to restore the sound. I try a few zips they send on the telegram group but nothing.
Grom9A said:
Thanks, it works. We need to find a way to restore the sound. I try a few zips they send on the telegram group but nothing.
Click to expand...
Click to collapse
Did you format using the "yes" option? I tried those steps but couldn't get it to boot, but formatting with "yes" was the only thing that I didn't do. I didn't think it would be necessary because my encryption was already disabled.
Have you tried flashing Viper4android? It might make the sound work since it uses it's own drivers and has to gain root access. I'd try the one by zackptg5, the same guy who makes the disabler.
Spaceminer said:
Did you format using the "yes" option? I tried those steps but couldn't get it to boot, but formatting with "yes" was the only thing that I didn't do. I didn't think it would be necessary because my encryption was already disabled.
Have you tried flashing Viper4android? It might make the sound work since it uses it's own drivers and has to gain root access. I'd try the one by zackptg5, the same guy who makes the disabler.
Click to expand...
Click to collapse
Did you flash the stock boot.img? That's all I had to do to make it work, I didn't have to format data since I already have it decrypted.
Spaceminer said:
Did you format using the "yes" option? I tried those steps but couldn't get it to boot, but formatting with "yes" was the only thing that I didn't do. I didn't think it would be necessary because my encryption was already disabled.
Have you tried flashing Viper4android? It might make the sound work since it uses it's own drivers and has to gain root access. I'd try the one by zackptg5, the same guy who makes the disabler.
Click to expand...
Click to collapse
I want to try but can't root this rom
Grom9A said:
I want to try but can't root this rom
Click to expand...
Click to collapse
Under phh's v200 build there's a special magisk he made for his Android 10 GSI.
---------- Post added at 08:11 PM ---------- Previous post was at 08:07 PM ----------
ry755 said:
Did you flash the stock boot.img? That's all I had to do to make it work, I didn't have to format data since I already have it decrypted.
Click to expand...
Click to collapse
Maybe I flashed the wrong boot.img... I might've mixed up Oreo and Pie boot images. I have both firmwares sitting right next to each other.
Spaceminer said:
Under phh's v200 build there's a special magisk he made for his Android 10 GSI.
Click to expand...
Click to collapse
I've tried that along with a few other people in the Moto G6 Telegram group, flashing it just causes bootloops.
ry755 said:
I've tried that along with a few other people in the Moto G6 Telegram group, flashing it just causes bootloops.
Click to expand...
Click to collapse
That explains my problem. I definitely flashed his magisk. Have you guys tried magisk v20 yet?
Spaceminer said:
That explains my problem. I definitely flashed his magisk. Have you guys tried magisk v20 yet?
Click to expand...
Click to collapse
Yep, any kind of Magisk makes it bootloop. Someone reported it to phh and his response was "well don't use magisk then" lol
ry755 said:
Yep, any kind of Magisk makes it bootloop. Someone reported it to phh and his response was "well don't use magisk then" lol
Click to expand...
Click to collapse
I'll check it out and see what I can do. That's not surprising though. It's extremely alpha, so he's probably just prioritizing stock functionality over everything else right now.
I can't get it rooted, but v202 just went up, so I'm going to try my luck with it.
I want to install TWRP as my recovery I've tried at least four different versions that are listed here and a few others from other links:
https://forum.xda-developers.com/t/...p-for-oneplus-8-8-pro-unified-stable.4101313/
I'm not having driver issues anymore so I'm working with adb and fastboot fine. All commands are going through fine and I've tried flashing to recovery_a and recovery_b. Factory resetting doesn't resolve the issue. Every walkthrough I find I get to says flash then boot to TWRP but every time I flash it qualcomm dumps and every time I boot to it it qualcomm dumps.
Is there something corrupted in my recovery I need to wipe somehow? If so how do I wipe it because the only command I found online that would run was fastboot -w and that didn't fix the issue either.
Honestly really annoying at this. This is my 4th OnePlus phone and I've never had so many issues flashing it.
Edit:
I have also tried to do whatever steps are needed to go back to base stock and OS and it doesn't seem to work either. Any help would be appreciated.
Edit 2:
I did it. For anyone who finds this thread in the future the MSM tool did finally work. This is the video I used in the end
(I muted it.) and the first few starts it failed. I went into the properties of the MSM exe and under compatibility checked ran as admin. I also did install the qualcomm driver at some point way before this so not sure if that helped. The MSM tool still didn't work until I started it, turned my phone off, held both volume buttons (not the power) while plugging the phone in. All the stuff online I saw had people starting the program at this point but mine had started already and was in a "waiting for device" state when it worked.
What a lifesaver. Won't be messing around with this again until TWRP is available.
Because you are unable to flash phone's Stock ROM take phone to authorized service center and let them fix it.
Flash stock recovery. TWRP is but compatible with OOS11 for 8/Pro.
Edit: not
Lossyx said:
Flash stock recovery. TWRP is but compatible with OOS11 for 8/Pro.
Click to expand...
Click to collapse
I have had so much trouble figuring that out too. Do you have a good link for that? I can't find an easy way to do it. I've seen people recommend the msmdownloadtool but every time I use it it doesn't pick up my phone.
I've settled with Lineage OS and Gapps until I figure out more.
TheFloppyDisk said:
I have had so much trouble figuring that out too. Do you have a good link for that? I can't find an easy way to do it. I've seen people recommend the msmdownloadtool but every time I use it it doesn't pick up my phone.
I've settled with Lineage OS and Gapps until I figure out more.
Click to expand...
Click to collapse
Meant to say it's **not** compatible with Android 11 yet.
Lossyx said:
Meant to say it's **not** compatible with Android 11 yet.
Click to expand...
Click to collapse
Sorry if I wasn't clear either. I was wondering if you have a good resource for flashing the stock again. I haven't been able to myself.
TheFloppyDisk said:
Sorry if I wasn't clear either. I was wondering if you have a good resource for flashing the stock again. I haven't been able to myself.
Click to expand...
Click to collapse
The same way to flashed TWRP.
fastboot flash recovery recovery_a and _b.
In the future, you should not flash both slots, just flash without specifying _a or _b.
Recovery image can be obtained here;
Android Dumps / oneplus / oneplus8pro · GitLab
GitLab Enterprise Edition
dumps.tadiphone.dev
Although i am not sure which OOS version you use, so you might have to change branch
Lossyx said:
The same way to flashed TWRP.
fastboot flash recovery recovery_a and _b.
In the future, you should not flash both slots, just flash without specifying _a or _b.
Recovery image can be obtained here;
Android Dumps / oneplus / oneplus8pro · GitLab
GitLab Enterprise Edition
dumps.tadiphone.dev
Although i am not sure which OOS version you use, so you might have to change branch
Click to expand...
Click to collapse
I hate to be this much of a noob about it but I see a recovery file listed in the link you sent. Is that the recovery I flash? And if so after flashing is this branch also a stock rom? I've been trying for a while now just to get back to the basic oxygen that comes with the phone but it's been a nightmare for me and it feels like no resource I find fully explains it.
TheFloppyDisk said:
I hate to be this much of a noob about it but I see a recovery file listed in the link you sent. Is that the recovery I flash? And if so after flashing is this branch also a stock rom? I've been trying for a while now just to get back to the basic oxygen that comes with the phone but it's been a nightmare for me and it feels like no resource I find fully explains it.
Click to expand...
Click to collapse
If you want OOS back / new start, best way is really to use MSM. Haven't really used it, so can't help you much. There are tutorials online / YouTube though
Lossyx said:
If you want OOS back / new start, best way is really to use MSM. Haven't really used it, so can't help you much. There are tutorials online / YouTube though
Click to expand...
Click to collapse
Gotcha. Unfortunately I haven't been able to get MSM to recognize my phone yet but I guess I will keep working on it and see what I can do. Thanks for your help.
TheFloppyDisk said:
Gotcha. Unfortunately I haven't been able to get MSM to recognize my phone yet but I guess I will keep working on it and see what I can do. Thanks for your help.
Click to expand...
Click to collapse
It is very sensitive to which USB port you use. For some people only USB2.0 works, for me USB3 works fine as long as it's chipset USB3. The second ASMedia controller doesn't work.
Also, use original cable, and switch off the phone completely, get MSM to the point it's waiting for device so start the download before connecting phone, then while holding the volume keys connect the USB cable and it should instantly start flashing.
so i was trying to flash CherishOS so i followed the instruction and found some problem but i was managed to solve the problem. FYI, the rom gave the link to the custom recovery which is the PixelExperience one, since i'm coming from the stock latest rom so i flashed that. until i done everything and boot to system, and it just keeps returned to the bootloader no matter which option i choose (boot to system & recovery), but luckily the device is still detected in my computer
What i've tried :
- flash recovery (PixelExperience & TWRP)
- Followed this instruction
but none of that is working, one thing i found out while doing the 2nd method is that it shows some errors like "flashing is not allowed for critical partition" and "partition not found".
I have no clue what to do, i've tried whatever solution i could find and none are working. please help, thanks
edit:
I also tried the "fastboot flashing unlock_critical" and tried to reboot into fastbootd but failed and the fastboot shows all command list
I guess you are referencing to CherishOS on xda.
[ROM][13.0]CherishOS-4.2[UNOFFICIAL][Oneplus 8 Pro]
CherishOS is an AOSP based rom focusing on Unique and Smooth UI with handy features. CherishOS is a reborn of pie based Dot-ExtendedOS. * Your warranty is now void. * I am not responsible for anything that may happen to your phone by installing...
forum.xda-developers.com
If i click on the link to download the recovery there is nothing about pixelexperience. So i guess you saw something about pixelexperience in the recovery itself. Thats not a problem anyway. You could use lineage recovery too. As long as the recovery is made for a12 thats not a problem as far as i know.
Its not written in the Cherish OS thread but in all other roms you have to be on the latest OOS11 on BOTH slots. Did you do this beforehand?
The easiest thing now is to use MSM Tool and go back to a locked oos phone.
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
If you like to install a custom rom again, make sure to update both slots before.
Install LineageOS on instantnoodlep | LineageOS Wiki
wiki.lineageos.org
I tried many custom roms or all i think. And tbh the best experience i had for now was OOS11 and the Open Beta 1 OOS12.
OxygenOS 12 [OB1] [Oneplus 8 Pro] - First Open Beta of Global OOS12
*Will update thread as rn im at work* The first Open Beta for Global OOS has been release really quietly (no announcemment so far) but here is the link from where i download it...
forum.xda-developers.com
Good luck.
xtcislove said:
I guess you are referencing to CherishOS on xda.
[ROM][13.0]CherishOS-4.2[UNOFFICIAL][Oneplus 8 Pro]
CherishOS is an AOSP based rom focusing on Unique and Smooth UI with handy features. CherishOS is a reborn of pie based Dot-ExtendedOS. * Your warranty is now void. * I am not responsible for anything that may happen to your phone by installing...
forum.xda-developers.com
If i click on the link to download the recovery there is nothing about pixelexperience. So i guess you saw something about pixelexperience in the recovery itself. Thats not a problem anyway. You could use lineage recovery too. As long as the recovery is made for a12 thats not a problem as far as i know.
Its not written in the Cherish OS thread but in all other roms you have to be on the latest OOS11 on BOTH slots. Did you do this beforehand?
The easiest thing now is to use MSM Tool and go back to a locked oos phone.
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
If you like to install a custom rom again, make sure to update both slots before.
Install LineageOS on instantnoodlep | LineageOS Wiki
wiki.lineageos.org
I tried many custom roms or all i think. And tbh the best experience i had for now was OOS11 and the Open Beta 1 OOS12.
OxygenOS 12 [OB1] [Oneplus 8 Pro] - First Open Beta of Global OOS12
*Will update thread as rn im at work* The first Open Beta for Global OOS has been release really quietly (no announcemment so far) but here is the link from where i download it...
forum.xda-developers.com
Good luck.
Click to expand...
Click to collapse
yoo it works, thanks a lot man. hope you know how relieved i am
yeah i know it's not the problem, but it was the first time i know this recovery in like few years of modding my phone
also i finnaly able to flash the the custom rom, thanks!
I totally agree tho, the oos for me is the best stock rom, i tried the beta 1 tho, but it just leans towards to the color os since oppo is the parent company of oneplus. it just feels more heavy and too many change from the stock android. that's why i decided to flash custom rom
again, thank you so much! have a great day!
B1nz said:
yoo it works, thanks a lot man. hope you know how relieved i am
yeah i know it's not the problem, but it was the first time i know this recovery in like few years of modding my phone
also i finnaly able to flash the the custom rom, thanks!
I totally agree tho, the oos for me is the best stock rom, i tried the beta 1 tho, but it just leans towards to the color os since oppo is the parent company of oneplus. it just feels more heavy and too many change from the stock android. that's why i decided to flash custom rom
again, thank you so much! have a great day!
Click to expand...
Click to collapse
hi.... what exactly have you done to bring it back ??? I'm in the same situation, just fastboot.... thanks
flo musti said:
hi.... what exactly have you done to bring it back ??? I'm in the same situation, just fastboot.... thanks
Click to expand...
Click to collapse
i just used the unbrick tool from the link above, and my phone is back to complete normal. hope it also works for you!
B1nz said:
i just used the unbrick tool from the link above, and my phone is back to complete normal. hope it also works for you!
Click to expand...
Click to collapse
already tried but the phone is not going in Qualcomm EDL mode...
flo musti said:
already tried but the phone is not going in Qualcomm EDL mode...
Click to expand...
Click to collapse
in my experience, my phone is just showing nothing it's like the screen is off. i realized that my phone is in EDL mode is it's detected in my computer as qualcomm something.., when it shows like that that means you haven't installed the qualcomm driver. after that the name will change to "more normal" name. and then you can proceed into the tools