LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1 (Oreo), which is designed to increase performance and reliability over stock Android for your device.
Code:
/*
* Your warranty is now void. Knox 0x1.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
WARNING:
This is not a stable version of LineageOS. If you run into problems (and you will), bring us a logcat so we can fix this quickly.
We provide no support for custom kernels, Xposed, or any other modifications made to the system.
Prerequisites:
Your Galaxy Tab A (2015) 8.0".
Odin (you will have to flash TWRP this way if you don't already have it, otherwise extract the img from the tar file and flash it in TWRP).
Downloads:
TWRP 3.2.0 (thanks Deadman for building, Austcool for uploading): [url]https://androidfilehost.com/?fid=962339331458992706[/URL]
Current builds: [url]https://www.androidfilehost.com/?w=files&flid=270958[/URL]
Source code:
Device trees: msm8916-common, gte-common, gt58wifi
Kernel tree: [url]https://github.com/Galaxy-MSM8916/android_kernel_samsung_msm8916[/URL]
LineageOS: GitHub
Support:
You can reach out to me via the official XDA Discord server.
XDA:DevDB Information
LineageOS, ROM for the Samsung Galaxy Tab A series
Contributors
andr01dfr3ak, deadman96385, Paradoxify, Austcool, Spaceminer
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
Version Information
Status: Testing
Created 2018-05-17
Last Updated 2018-05-16
Reserved
Instructions:
From custom ROMs (assuming you already have TWRP):
Download the latest build and TWRP from the links above.
Ensure these downloads are in your tablet.
Extract the img file from the TWRP tar file.
Reboot into TWRP.
Flash the img file you previously extracted into the recovery partition. (Yes, you can update TWRP this way, it is not dangerous).
Reboot recovery. Then flash the ROM.
Reboot into system. You should be good to go.
If you want any of Google's applications, you'll have to download that before rebooting into TWRP, and flash it after the ROM, but before rebooting.
For Google's applications, go to OpenGApps and select "ARM" and "8.1".
Changelog:
5-16-2018:
This was released.
Issues:
Bluetooth is not working
Device can't play audio through speakers (but can through headphones)
Media process not doing its job for some reason
Can't access the camera
Major issue:
This ROM is a hit-and-miss, meaning on some devices, the ROM successfully flashes, and other times, it either doesn't boot or TWRP is unable to flash the ROM.
For Gapps, Install the arm version of Gapps.
Test the rom, very smooth, hope the audio can fix soon.
Doesnt work on sm-t350! You flash the recovery with odin, black screen. Flash recovery with twrp black screen. Flash rom with working twrp black screen!
Hello there. After that I restored the old backup from twrp again, but the device gave the error "efs invalid argument". I have tried many methods and now the device does not boot. Can you help me? I am sorry for my English. Thanks in advance.
maydemir said:
Hello there. After that I restored the old backup from twrp again, but the device gave the error "efs invalid argument". I have tried many methods and now the device does not boot. Can you help me? I am sorry for my English. Thanks in advance.
Click to expand...
Click to collapse
I got you boss I did the same thing and fixed it.
Boot into twrp go to advanced, click terminal and type
mke2fs /dev/block/mmcblk0p13 hit enter.
Then type
mount -w -t ext4 /dev/block/mmcblk0p13 hit enter.
Reboot
It will saying writing indon or something like that after hitting enter on the first command. Are efs is mmcblk0p13 It fixes the problem on reboot your device should boot again flashing stock with Odin doesn't work. I'm guessing you corrupted the data restoring efs and modem with twrp 3.2.1 right? That's how I did it you can't use 3.2.1 for efs or modem it's from lte source code and messes are efs up.hit thanks if it boots it will you just need to type it right. You can also boot into twrp and mount system and use adb to type same command only my adb wasn't working so twrp terminal worked.
Techguy777 said:
I got you boss I did the same thing and fixed it.
Boot into twrp go to advanced, click terminal and type
mke2fs /dev/block/mmcblk0p13 hit enter.
Then type
mount -w -t ext4 /dev/block/mmcblk0p13 hit enter.
Reboot
It will saying writing indon or something like that after hitting enter on the first command. Are efs is mmcblk0p13 It fixes the problem on reboot your device should boot again flashing stock with Odin doesn't work. I'm guessing you corrupted the data restoring efs and modem with twrp 3.2.1 right? That's how I did it you can't use 3.2.1 for efs or modem it's from lte source code and messes are efs up.hit thanks if it boots it will you just need to type it right. You can also boot into twrp and mount system and use adb to type same command only my adb wasn't working so twrp terminal worked.
Click to expand...
Click to collapse
Thank you so much. It really worked. There were errors in the codes I used before. The code at the end of the 13 solved everything
maydemir said:
Thank you so much. It really worked. There were errors in the codes I used before. The code at the end of the 13 solved everything
Click to expand...
Click to collapse
Your welcome I made this account just to help you. I had that happen last week and thought my tablet was never going to work again except with nougat. So I dug for days and figured out how to do it.
Ls -l /dev/block/bootdevice/by-name/ hit enter command in terminal.
It will show the partition table or setup for are tablet and that's how I figured out we need to use 13. I'm glad I could help. Now everything will work again you can flash lineage 15.1 and it'll work freeze Bluetooth with titanium backup to stop error. YouTube pic in picture works just no sound through speaker but headphones work. Remember guys system ,data , and boot leave efs and modem alone with twrp 3.2.1 it screws it up also do a wipe first clean flash only.
---------- Post added at 05:16 PM ---------- Previous post was at 04:47 PM ----------
[/COLOR]
Techguy777 said:
Your welcome I made this account just to help you. I had that happen last week and thought my tablet was never going to work again except with nougat. So I dug for days and figured out how to do it.
Ls -l /dev/block/bootdevice/by-name/ hit enter command in terminal.
It will show the partition table or setup for are tablet and that's how I figured out we need to use 13. I'm glad I could help. Now everything will work again you can flash lineage 15.1 and it'll work freeze Bluetooth with titanium backup to stop error. YouTube pic in picture works just no sound through speaker but headphones work. Remember guys system ,data , and boot leave efs and modem alone with twrp 3.2.1 it screws it up also do a wipe first clean flash only.
Click to expand...
Click to collapse
There is another problem! I have reset my backup but this time the wifi is not turned on. When I try to open it, the key closes itself.
maydemir said:
---------- Post added at 05:16 PM ---------- Previous post was at 04:47 PM ----------
[/COLOR]
There is another problem! I have reset my backup but this time the wifi is not turned on. When I try to open it, the key closes itself.
Click to expand...
Click to collapse
Well you'd have to tell me what firmware you restored. Also when you did that command did you try other numbers first before 13? Because it might have to do with that. Explain in detail everything. But for wifi now you should be able to flash your stock firmware and get it back on. Try that let us Know Odin for that.
I did the same thing knocked my wifi and I don't believe restoring with twrp worked I did get it back with stock and Odin.
I used version 3.1.1 of twrp. I have restored the 6.0.1 stock rooted software from the backup. but everything just works and wi-fi keeps shutting itself down.
---------- Post added at 07:01 PM ---------- Previous post was at 07:00 PM ----------
Techguy777 said:
Well you'd have to tell me what firmware you restored. Also when you did that command did you try other numbers first before 13? Because it might have to do with that. Explain in detail everything. But for wifi now you should be able to flash your stock firmware and get it back on. Try that let us Know Odin for that.
I did the same thing knocked my wifi and I don't believe restoring with twrp worked I did get it back with stock and Odin.
Click to expand...
Click to collapse
I used version 3.1.1 of twrp. I have restored the 6.0.1 stock rooted software from the backup. but everything just works and wi-fi keeps shutting itself down.
maydemir said:
I used version 3.1.1 of twrp. I have restored the 6.0.1 stock rooted software from the backup. but everything just works and wi-fi keeps shutting itself down.
---------- Post added at 07:01 PM ---------- Previous post was at 07:00 PM ----------
I used version 3.1.1 of twrp. I have restored the 6.0.1 stock rooted software from the backup. but everything just works and wi-fi keeps shutting itself down.
Click to expand...
Click to collapse
Yes I don't have time to explain it but efs partition is wifi Bluetooth and other things you have to flash stock now to get wifi back you mounted so now stock firmware will fix it. Before it wasn't mounted so you wouldn't be able to write over it with rom. Flash stock with Odin your wifi won't come back if you don't.
maydemir said:
I used version 3.1.1 of twrp. I have restored the 6.0.1 stock rooted software from the backup. but everything just works and wi-fi keeps shutting itself down.
---------- Post added at 07:01 PM ---------- Previous post was at 07:00 PM ----------
I used version 3.1.1 of twrp. I have restored the 6.0.1 stock rooted software from the backup. but everything just works and wi-fi keeps shutting itself down.
Click to expand...
Click to collapse
Once you flash stock and fix your wifi then you can go back to marshmallow with twrp and wifi working
This is awesome, a bit early for me, but I look forward to running it when it's a bit more mature! Thank you!
I tried to copy Bluetooth.apk and libbluetooth_jni.so from a stock rom. It didn't work but hey at least i don't get hundreds of popups saying bluetooth has stopped. What I love about this rom is how stable and fast it is. Boot up time is only like 20 seconds.
What should I use to root? Magisk or Super and which version?
Dumb question can i use this on a sm t357t
T mobile tab a.. 8.0
Xdevillived666 said:
What should I use to root? Magisk or Super and which version?
Click to expand...
Click to collapse
You can use either on the latest version, but Magisk seems to work better
Related
No longer supported
Unofficial TWRP 3.1.1 w/F2FS
> For the Nexus 6 Shamu
This work is inspired by @The Flash's F2FS TWRP builds. I based this build off of the TWRP Minimal Repo.Features:
TWRP 3.1.1
F2FS Mounting and Formatting supported (En/Decryption not supported, however)
Built atop my kernel
Works
Changelog:
3.1.1-3
Updated sources to 7.1.2_r33, which includes updated f2fs-tools (1.8.0)
Minor GUI tweaks (splash screen, odd gap under "Advanced")
Bump to subversion 3
Installation:
You should know the drill of installing custom recoveries if you found this thread, but anyways:
Have an UNLOCKED Bootloader
Boot to fastboot/bootloader mode (Power + Vol Down from power off)
In adb (replace X with appropriate subversion):
Code:
fastboot flash recovery twrp-3.1.1_X-f2fs-unofficial-shamu.img
You can now reboot to your shiny, new TWRP!
How Do I convert to F2FS?
Backup important data to an EXTERNAL source; if formatting /data, entire internal sd will be wiped.
Ensure your kernel/kernel you will flash supports F2FS. You can use my kernel if you desire.
Reboot to this (or any other) F2FS supported TWRP
Go to -> Wipe -> Advanced Wipe
Tick the desired partition you want to format (ONLY do /data and/or /cache)
Select "Repair or Change Filesystem"
Select "Change File System"
Select "F2FS"
Swipe to Change
Done. Flash all your stuff!
Disclaimer:
I am not responsible for broken devices etc... Flash at your own risk. I am also not affiliated with the official TWRP crew nor Omni ROMs, so please don't complain to them about bugs unique to my own builds.
Sources:
Manifest
TWRP Recovery
Device Tree
Kernel
XDA:DevDB Information
Unofficial TWRP for Shamu w/F2FS, Tool/Utility for the Nexus 6
Contributors
Black_Hat01, Omni Rom, and the great devs of TWRP itself
Source Code: https://github.com/BlackHat01/
Version Information
Status: No Longer Updated
Current Stable Version: 3.1.1-3
Stable Release Date: 2017-09-26
Created 2017-06-27
Last Updated 2018-02-10
Downloads
Download Latest 09/26 Build - 3.1.1-3
How do i make it keep my settings. Every time i boot into twrp i have to swipe to allow modifications and need to set settings again. Also it does not see my backups i made with previous twrp 3.1.1-0
Thanks a lot for this. Does it properly decrypt F2FS data?
Neejay said:
Thanks a lot for this. Does it properly decrypt F2FS data?
Click to expand...
Click to collapse
I don't use encryption so I cannot say. If you can test it for me that would be appreciated
UPDATE:
TWRP Official 3.1.0 changelog states TWRP will try to mount both ext4 and f2fs on decrypt, so It should work.
TMG1961 said:
How do i make it keep my settings. Every time i boot into twrp i have to swipe to allow modifications and need to set settings again. Also it does not see my backups i made with previous twrp 3.1.1-0
Click to expand...
Click to collapse
It should not reset your settings every time you boot into recovery, unless there is something wrong with your /sdcard/TWRP folder. Can you send a recovery log (Advanced > Copy Log)?
Will do that after finishing the install of the rom i am doing now.
TMG1961 said:
Will do that after finishing the install of the rom i am doing now.
Click to expand...
Click to collapse
Thank you. I ask because I am not having that issue at all. Maybe also try re-flashing recovery via fastboot before everything too.
what i did was this. Booted into bootloader. erased recovery, flashd your recovery and booted into it. wiped to allow changes and made changges to settings. Then booted back into rom. The rom i tried it with was stock 7.1.1.
I just finished installing velocity rom and flashed your twrp, same result. I did copy the log. said in twrp that it was copied to /data/media/recovery.log but the log is no were to be found on the phone. Did search the whole phone with root explorer
---------- Post added at 20:00 ---------- Previous post was at 19:59 ----------
when i try to do a backup i get error unable to mount storage
---------- Post added at 20:10 ---------- Previous post was at 20:00 ----------
I think the problem is something else. Not sure but twrp does not see my storage
Black_Hat01 said:
I don't use encryption so I cannot say. If you can test it for me that would be appreciated
UPDATE:
TWRP Official 3.1.0 changelog states TWRP will try to mount both ext4 and f2fs on decrypt, so It should work.
Click to expand...
Click to collapse
Unfortunately, it doesn't work. It doesn't recognize my unlock pattern and won't decrypt. I had to go back to xanaxdroid's 3.0.2.0 twrp for it to work
I did flash the previous twrp and copied the log file. Not sure if that contains what you need ut adding it so you can have a look
Neejay said:
Unfortunately, it doesn't work. It doesn't recognize my unlock pattern and won't decrypt. I had to go back to xanaxdroid's 3.0.2.0 twrp for it to work
Click to expand...
Click to collapse
Thanks for the update. Will look into it.
Black_Hat01 said:
Thanks for the update. Will look into it.
Click to expand...
Click to collapse
No problem. I tried to look for his source, but couldn't find one for shamu directly. Here's where I downloaded his img (if it helps at all): https://forum.xda-developers.com/showpost.php?p=70452221&postcount=29
TMG1961 said:
I did flash the previous twrp and copied the log file. Not sure if that contains what you need ut adding it so you can have a look
Click to expand...
Click to collapse
Can you flash my twrp and send log please? It is the correct log. I just need to see what's going on with mine. Thanks.
i can but after flashing your twrp then flash the old one again and copy the log to the sdcard ? Cause yours says it copies the log but there is no log on the sdcard.
TMG1961 said:
i can but after flashing your twrp then flash the old one again and copy the log to the sdcard ? Cause yours says it copies the log but there is no log on the sdcard.
Click to expand...
Click to collapse
That's odd. I was on Flash's 3.1.0-4 F2FS build and flashed mine right over that build and everything works fine for me (log copying works, settings stick fine, etc..), so maybe try flashing his build, then mine. Without a log, I can't really do much, since I, and nobody else yet has experienced the same issues. I'm going to do some work on it today, and I'll try to get a new build out tonight.
Thanks for your time and help. I downloaded 3.1.0-4 F2FS and 3.1.1-6 F2FS but on both the same. All version dont show anything on the sdcard when i go to advanced/file manager in twrp. So no idea what is causing it but almost sure the problem is on my side.
TMG1961 said:
Thanks for your time and help. I downloaded 3.1.0-4 F2FS and 3.1.1-6 F2FS but on both the same. All version dont show anything on the sdcard when i go to advanced/file manager in twrp. So no idea what is causing it but almost sure the problem is on my side.
Click to expand...
Click to collapse
Perhaps it is just your device. Anyways, I uploaded a new build, maybe try this one out. If it does not, try reflashing stock twrp 3.1.1 and then coming back to an F2FS modified one. Hope the best.
Is there any difference between this and the TWRP F2FS builds found at http://nchancellor.net/Downloads/TWRP/shamu/ ?
TMG1961 said:
...I just finished installing velocity rom
Click to expand...
Click to collapse
I thought that ROM ceased development a long time ago? Happen to have any links with more info on it? https://www.android-port.de/themen/rom-n-7-1-1-velocity-shamu.9596/
espionage724 said:
Is there any difference between this and the TWRP F2FS builds found at http://nchancellor.net/Downloads/TWRP/shamu/ ?
Click to expand...
Click to collapse
Thing is, by the time I posted, I hadn't realized he updated his. But the things that are different are basically the kernel the recovery image is built with (we use our own kernels), and the support. I will be actively building and supporting while The Flash has pretty much moved on from shamu to angler. Any bugs that arise I will try to fix and I will always be trying to keep everything updated. Over time our builds will start to become more and more different.
*** OUTDATED, WORK HAS NOW PROGRESSED TO POISON ROM, https://forum.xda-developers.com/an...mputers/amlogic/t95z-plus-poison-rom-t3751720 ***
Features
Removed Bloatware apps such as Twitter, Team Viewer etc.
Removed Dummy Play Store App
Removed Outdated versions of apps and replaced them with latest versions as of time of writing, like Playstore, Firefox, Kodi etc.
Used a Custom Launcher (Created by Ricky Divjakovski) to give device a fresh look.
Enter Key now works on External Keyboards
Known Bugs:
Play Store shortcut on Launcher does not work, Can open Playstore through Setting/Apps. ***Fixed***
Enter key on External Keyboard doesn't work. ***Fixed***
Navigation Bar does not come back if minimised without a reboot.
When you go to Settings/About/Status sometimes has an error and doesn't open, opens on second attempt though.
Any other bugs feel free to report.
***IMPORTANT ***
You need to be on Stock 7.1.2 Firmware before flashing the Custom Rom. So I recommend you make a backup of your existing Firmware if for any reason you want to go back to your Existing Firmware and setup. To make a backup, you need to get Custom Recovery (TWRP) installed, you need to install the right version of TWRP depending on your existing firmware. Download your existing Firmware Custom Recovery files from below.
TWRP FILES
If on Firmware 6.0.1 from here
If on Firmware 7.1.1 from here
If on Firmware 7.1.2 from here
INSTALLING CUSTOM RECOVERY
METHOD 1:
Download Ricky's Amlogic Flash Tool from AmlogicFlashTool.zip and follow the instructions from his thread over at https://forum.xda-developers.com/an...c/amlogic-devices-amlogic-flash-tool-t3745640.
METHOD 2:
1. Download ADB from here and install it on your pc, then open a command prompt (Windows 10 hold Shift and press Right Mouse button, will take you to Power Shell) in the directory of the custom recovery
2. Enable USB debugging, go to settings>about and click build number about 10 times, then go back to the main settings menu and you will see developer options, enter it and check allow USB debugging.
3. Connect to your device via IP address. go to settings>about>status and get your IP address. it should be something like 192.168.25.19
4. In CMD type the following commands, replace YOURIPADDRESS with the address we got from step 3
Code:
adb connect YOURIPADDRESS
adb push custom-recovery.img /sdcard/
adb shell su -c dd if=/sdcard/custom-recovery.img of=/dev/block/recovery
adb reboot recovery
TWRP BACKUP
Now go ahead and make a backup of your existing setup before proceeding any further. I recommend putting the backup onto a usb drive.
Step:
1. Go to Backup
2.If desired name your backup on name setting up top left hand corner, not necessary but can do if you like.
3. Select Storage: USB or SDCard depending on which one you are going to use. Click OK.
3. Swipe to Backup
4. Let it do it's thing, When finished remove usb/sd card and reboot to system.
5. Recommend putting a copy of your backup from your usb or sd card to your PC as well.
FLASHING 7.1.2 STOCK FIRMWARE
You need to download the Stock 7.1.2 firmware from here
Use the provided USB Burning tool to flash the firmware if you have a USB Male to Male cable. Video of how to here
Now 7.1.2 Stock is installed, you now have to flash the Custom Recovery (TWRP) for 7.1.2, follow the instructions earlier to install Custom Recovery with the 7.1.2 file.
CUSTOM ROM
NOTE: Remember to make sure you have a backup of your old existing firmware before flashing this custom rom
Instructions:
1. Download the 3/32GB T95Z Custom Rom 7.1.2.zip from here
and put it on a usb stick.
2. Reboot into recovery
3. Wipe Cache, System and Data
4. Go back to the main menu and select install, then choose the 3/32GB T95Z Custom Rom 7.1.2.zip and swipe to install!
Reboot and enjoy!
Please give 5 to 10 minutes on first reboot after flash.
Contributors
Ricky Divjakovski, whiteak
ROM OS Version: 7.x Nougat
Credits:
Magendanz (TWRP)
Snoop05 (Adb)
Version Information
Status: Testing
Great job! A whole range of ROMS for Amlogic devices is about to unveil once i release the rom skeletop package!
Hi on my device when i reboot to recovery after put TWRP by adb it's stuck on T95z plus logo... Any idea ?
after unplug the power cable and plug it again the box start, but i can't start in recovery by the adb... can u give me some help ?
Thanks by advance.
---------- Post added at 11:36 AM ---------- Previous post was at 11:31 AM ----------
I do that and i don't see any error..
C:\Users\papla\Downloads\platform-tools-latest-windows\platform-tools>adb connect 192.168.1.100
connected to 192.168.1.100:5555
C:\Users\papla\Downloads\platform-tools-latest-windows\platform-tools>adb push custom-recovery.img /sdcard/
custom-recovery.img: 1 file pushed. 6.6 MB/s (13793280 bytes in 1.986s)
C:\Users\papla\Downloads\platform-tools-latest-windows\platform-tools>adb shell su -c dd if=/sdcard/custom-recovery.img of=/dev/block/recovery
26940+0 records in
26940+0 records out
13793280 bytes transferred in 2.774 secs (4972343 bytes/sec)
C:\Users\papla\Downloads\platform-tools-latest-windows\platform-tools>adb reboot recovery
C:\Users\papla\Downloads\platform-tools-latest-windows\platform-tools>
Is your box 2/16gb or 3/32gb, you may be flashing the wrong TWRP.
whiteak said:
Is your box 2/16gb or 3/32gb, you may be flashing the wrong TWRP.
Click to expand...
Click to collapse
32Gb box and i take the twrp from your thread.
papla83 said:
32Gb box and i take the twrp from your thread.
Click to expand...
Click to collapse
Try this TWRP here
It's a earlier version, but I ported this one myself. It's the one I used until I found a newer version.
whiteak said:
Try this TWRP here
It's a earlier version, but I ported this one myself. It's the one I used until I found a newer version.
Click to expand...
Click to collapse
Same result, hang on t95Zplus logo and doesn't move....
papla83 said:
Same result, hang on t95Zplus logo and doesn't move....
Click to expand...
Click to collapse
And you definitely have a 3/32gb box, I don't know what could be the problem. I had the exact same problem, but it was because I was using the 2/16 version on my 3/32 box. You don't have any usb sticks plugged into the box either? if you do try pulling them out when flashing.
whiteak said:
And you definitely have a 3/32gb box, I don't know what could be the problem. I had the exact same problem, but it was because I was using the 2/16 version on my 3/32 box. You don't have any usb sticks plugged into the box either? if you do try pulling them out when flashing.
Click to expand...
Click to collapse
yes i have, i will try whitout sd card and usb stick and make a feedback
---------- Post added at 02:02 PM ---------- Previous post was at 01:56 PM ----------
same result
can i brick my box if i flash it with the 16Gb model ? because maybe i can try with no risk ( the recovery doesn't start anyway )
Worst case is it should only do the same thing, I was pushing the 16gb model on my box a fair few times and all it did hang at the T95Z Plus logo.
whiteak said:
Worst case is it should only do the same thing, I was pushing the 16gb model on my box a fair few times and all it did hang at the T95Z Plus logo.
Click to expand...
Click to collapse
When i try to send twrp 16gb version to my box i have an error message failed to send file ( i use the amlogic adb tool by Ricky Divjakovski )...
papla83 said:
yes i have, i will try whitout sd card and usb stick and make a feedback
---------- Post added at 02:02 PM ---------- Previous post was at 01:56 PM ----------
same result
can i brick my box if i flash it with the 16Gb model ? because maybe i can try with no risk ( the recovery doesn't start anyway )
Click to expand...
Click to collapse
By personal experience your best bet is to re flash the original rom with the usb flashing tool.
Once it is done you can try flashing different TWRP until you find one that work. Installing TWRP from the store just does not work on those device.
Installing SU also soft brick your device and normal recovery do not work.
Also to flash using to USB burning tool make sure you use the OTG USB port on your device (usually port no, 1).
whiteak said:
Known Bugs:
Play Store shortcut on Launcher does not work, Can open Playstore through Setting/Apps.
Navigation Bar does not come back if minimised without a reboot.
When you go to Settings/About/Status sometimes has an error and doesn't open, opens on second attempt though.
Any other bugs feel free to report.
Click to expand...
Click to collapse
I got play store to work on my original rom from the launcher after disabling it in the app settings, and replacing system/app/GoogleStore folder by the one from SuperCeleron 3/32g custom rom ans installing it from the apk. Might be worth a look to get it working on your rom.
Funny thing is that I tried to install SuperCeleron Rom on my machine but it brick it every time.
Also on initial setup after you have an option to give root acces or not and also to enables init.d support, I just can't remember where it was in the Droid settings on the launcher or the most advance settings in the apps folder. I will have to go thru all the settings to find them.
I tried your ROM but it disabled my Play Store in the launcher and in the apps and did not let me reinstall it for some reason. I had to go thru TotalCommander to be able to launch it. Since I did not want to fool around to restore it. I just flashed back my Rom.
I can live with the way my device perform right now has the most important part for me was Kodi.
Stuck at logo as well
I got everything to go just fine: ADB went smooth, TWRP running just fine, successful flash from microSD card, wiped cache, rebooted and waited 15 minutes and I'm just stuck at the logo
I even pulled AC and ejected the card and then plugged it in let it sit for 20 minutes and nothing but the logo still.
I'm 101% sure I'm have a 3G+32Gb T95z Plus (AP6225 WLAN)
LeMaestro said:
I got play store to work on my original rom from the launcher after disabling it in the app settings, and replacing system/app/GoogleStore folder by the one from SuperCeleron 3/32g custom rom ans installing it from the apk. Might be worth a look to get it working on your rom.
Funny thing is that I tried to install SuperCeleron Rom on my machine but it brick it every time.
Also on initial setup after you have an option to give root acces or not and also to enables init.d support, I just can't remember where it was in the Droid settings on the launcher or the most advance settings in the apps folder. I will have to go thru all the settings to find them.
I tried your ROM but it disabled my Play Store in the launcher and in the apps and did not let me reinstall it for some reason. I had to go thru TotalCommander to be able to launch it. Since I did not want to fool around to restore it. I just flashed back my Rom.
I can live with the way my device perform right now has the most important part for me was Kodi.
Click to expand...
Click to collapse
I want just have the best experience with this box, the box ,at this time and with this rom works, but i feel the works doesn't finish and i think we have a huge possibility with a finalised and optimised rom.
---------- Post added at 10:02 PM ---------- Previous post was at 10:01 PM ----------
Semper 5 said:
I got everything to go just fine: ADB went smooth, TWRP running just fine, successful flash from microSD card, wiped cache, rebooted and waited 15 minutes and I'm just stuck at the logo
I even pulled AC and ejected the card and then plugged it in let it sit for 20 minutes and nothing but the logo still.
I'm 101% sure I'm have a 3G+32Gb T95z Plus (AP6225 WLAN)
Click to expand...
Click to collapse
Hi. sorry for the dumb question but do you wipe to the factory data too or only wipe cache ?
papla83 said:
Hi. sorry for the dumb question but do you wipe to the factory data too or only wipe cache ?
Click to expand...
Click to collapse
I tried just the cache at first, but I tried both. and now, since I updated 7.1.1 > 7.1.2 I can't get TWRP to boot. I think the 7.1.2 doesn't like the TWRP I was using.
PS, the link for TWRP in this thread is nonexistent.
It would be AMAZING if we could get this custom ROM in an IMG file to use in the Amlogic burner application.
Semper 5 said:
I tried just the cache at first, but I tried both. and now, since I updated 7.1.1 > 7.1.2 I can't get TWRP to boot. I think the 7.1.2 doesn't like the TWRP I was using.
PS, the link for TWRP in this thread is nonexistent.
It would be AMAZING if we could get this custom ROM in an IMG file to use in the Amlogic burner application.
Click to expand...
Click to collapse
Take a look here maybe you will find what you need.
https://forum.xda-developers.com/an...95z-plus-one-thread-files-recoveries-t3737040
I used the custom recovery for the 3/32Gb variant and it worked perfect, now I have a working TWRP.
papla83 said:
I want just have the best experience with this box, the box ,at this time and with this rom works, but i feel the works doesn't finish and i think we have a huge possibility with a finalised and optimised rom.
Click to expand...
Click to collapse
Me to I would like to have a few thing added or fixed in the launcher, but those guys just started to work on this a few days ago, so let give them time to make it better. I screw up my box enough in the last week so let be patient.
Semper 5 said:
I tried just the cache at first, but I tried both. and now, since I updated 7.1.1 > 7.1.2 I can't get TWRP to boot. I think the 7.1.2 doesn't like the TWRP I was using.
PS, the link for TWRP in this thread is nonexistent.
It would be AMAZING if we could get this custom ROM in an IMG file to use in the Amlogic burner application.
Click to expand...
Click to collapse
TWRP link updated, not sure why it unlinked but anyway should be good to download again.
LeMaestro said:
Take a look here maybe you will find what you need.
https://forum.xda-developers.com/an...95z-plus-one-thread-files-recoveries-t3737040
I used the custom recovery for the 3/32Gb variant and it worked perfect, now I have a working TWRP.
Me to I would like to have a few thing added or fixed in the launcher, but those guys just started to work on this a few days ago, so let give them time to make it better. I screw up my box enough in the last week so let be patient.
Click to expand...
Click to collapse
That link in the other thread links to my mega folder, can I ask which custom recovery you used the 3.1.1-0 or the 3.0.2, both should work, but just curious. Also so you did manage to flash my custom zip successfully and it did boot up? Not sure why people are having problems.
Code:
*** Disclamer * Your warranty is now void. * *
We are not responsible for bricked devices, dead SD cards, * thermonuclear war,
or you getting fired because the alarm app failed. Please * do some research if you
have any concerns about features included in this ROM * before flashing it! YOU are
choosing to make these modifications, and if * you point the finger at us for messing
up your device, we will laugh at you.
DISCONTINUED, MOVED TO BUILDING CRDROID AND AICP ANDROID PIE
Known Issues
No audio through speaker, currently trying to find a fix.
ROM ResurrectionRemix-O-v6.2.1-20181202
TWRP DOWNLOAD
INSTALLATION
I am assuming that most of you already know how to flash custom ROMS.
Boot into TWRP Recovery Flash TWRP 3.2.3-0 image
Wipe the System, Cache and Data.
Flash ROM Zipfile
Flash the GApps (optional, needed for Google Playstore to work).
(Optional) Flash root zipfile Majisk/SuperSU.
Wipe ART/Dalvik cache.
Reboot
Flashing the ROM itself the boot time is around 5 mins, if you flash Gapps + Majisk or SuperSU expect the first boot time to increase to about 7-8 mins
XDA:DevDB Information
SM-T350 ResurrectionRemix Oreo, ROM for the Samsung Galaxy Tab A series
Contributors
nubianprince
Source Code: https://github.com/Nubianprince/gt58wifi_rr
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Stock Nougat
Version Information
Status: Beta
Beta Release Date: 2018-12-02
Created 2018-12-02
Last Updated 2019-03-23
Reserved
reserved
Did you guys just use the open source code of lineage 15.1 that didn't have working speaker. So is basically the same rom with different name. I'm still going to flash it for kicks but doesn't seem kinda pointless? Twrp should be better I'll let you know I'm assuming you forgot to mention gapps.
Funny cause the guy that built that took the source codes from someone else and that's why the speaker never got fixed because you don't know how to build or compile your just copying.
I got the rom up and running i was on marshmallow firmware and it worked fine. It takes awhile to boot up give it 10 minutes then when you start up it's really slow and lagging but after a couple reboots it works fine. I do say it's resremix tons of customization I haven't used any yet. I still think it's based off the lineage codes but it's different very different setup so it's worth installing if the damn speaker could get fixed it would be great. Bluetooth speaker or headphones work camera works I think the camera on this tablet is **** but works lol. Thanks for the rom guys. Twrp also seems to be working fine which is great because that's been a pain before.
Good job
Enviado desde mi SM-T320 mediante Tapatalk
So i am geting error 7. I have twrp 3.1.1-1_ashyx installed. I flash the new twrp recovery using install > install image > click the recovery file > click recovery partition and swipe to flash. then i follow all the other instructions and it still error 7 "this device is ." i found it odd that it doesnt list any name for the device. any help?
joejunior253 said:
So i am geting error 7. I have twrp 3.1.1-1_ashyx installed. I flash the new twrp recovery using install > install image > click the recovery file > click recovery partition and swipe to flash. then i follow all the other instructions and it still error 7 "this device is ." i found it odd that it doesnt list any name for the device. any help?
Click to expand...
Click to collapse
After you flashed the new twrp 3.2.3 did you reboot back into recovery? You can't just flash it then flash the rom you have to reboot in to recovery again to have it take effect. Also then follow all other instructions what instructions did you follow just a little more detail. Also what room or system were you on before?
I am coming from stock. When I flash from twrp and then click reboot recovery I get a boot loop. I've even tried doing the hold volume down + home + power and then moving to volume up, still doesn't work. I can't get twrp 3.1.0 to work, I always have to use 3.1.1. and I can't get the system to downgrade to marshmallow to test out anything else. It always fails with media failed to launch or something similar. I can only get the stock firmware ending in q1 and q5 to work (the latest ones running nougat). But I did notice on the twrp link that the nougat is for the t355 but appears to work on my t350.
joejunior253 said:
I am coming from stock. When I flash from twrp and then click reboot recovery I get a boot loop. I've even tried doing the hold volume down + home + power and then moving to volume up, still doesn't work. I can't get twrp 3.1.0 to work, I always have to use 3.1.1. and I can't get the system to downgrade to marshmallow to test out anything else. It always fails with media failed to launch or something similar. I can only get the stock firmware ending in q1 and q5 to work (the latest ones running nougat). But I did notice on the twrp link that the nougat is for the t355 but appears to work on my t350.
Click to expand...
Click to collapse
I'm not 100 percent what your saying. I believe your problems is with twrp you need to update twrp to version 3.2.3 which is on the first page of this thread. You need twrp 3.2.3 because the device tree is different for Oreo roms so much that you can't flash them with twrp 3.1.1. Downgrading system was not really the way to do it. I was just saying it worked from marshmallow not that you should be on marshmallow. When I downgraded from nougat firmware q1 and q5 bot to marshmallow I was able to downgrade but I got a drk error upon reboot. I just forced reboot and marshmallow stock worked but Downgrading is not usually good. Let's me also ask did you wipe efs partition with twrp 3.2.1 from the other thread at anytime? Try 3.2.3 either flash tar with Odin or extract img and flash in twrp recovery.
P.s. also yes twrp 355 3.1.1 does work on smt350 very well but still twrp3.2.3 should be the one to use.
If you wiped efs with twrp 3.2.1 and got an error you need to get back on to nougat firmware and then you into twrp terminal in advanced. Type in the first line hit enter then type in second command enter. You will no be able to boot marshmallow but you still might get drk error I got. It's because twrp 3.2.1 came from lte source codes and people think there the same there not the efs partition controls you Bluetooth and wifi on lte I'm sure it controls data. So it's not the same and it damages it and can't fix it because the partitions aren't setup right. I hope this helps. Guys take notes xda is for helping to not just getting root then leaving try to help out.
mke2fs /dev/block/mmcblk0p13
mount -w -t ext4 /dev/block/mmcblk0p13
joejunior253 said:
I am coming from stock. When I flash from twrp and then click reboot recovery I get a boot loop. I've even tried doing the hold volume down + home + power and then moving to volume up, still doesn't work. I can't get twrp 3.1.0 to work, I always have to use 3.1.1. and I can't get the system to downgrade to marshmallow to test out anything else. It always fails with media failed to launch or something similar. I can only get the stock firmware ending in q1 and q5 to work (the latest ones running nougat). But I did notice on the twrp link that the nougat is for the t355 but appears to work on my t350.
Click to expand...
Click to collapse
Device?
Firmware?
TWRP version?
Thanks tech guy. I will try this when I get home. I am back on stock firmware q5. I will just flash with Odin since I don't have twrp at all anymore. I will flash twrp 3.2.3. then I will try these commands. Fingers crossed it will work. Then I will boot into twrp if it works and flash the rom and gapps. I am not trying to root, just a better rom. I will post back soon
joejunior253 said:
Thanks tech guy. I will try this when I get home. I am back on stock firmware q5. I will just flash with Odin since I don't have twrp at all anymore. I will flash twrp 3.2.3. then I will try these commands. Fingers crossed it will work. Then I will boot into twrp if it works and flash the rom and gapps. I am not trying to root, just a better rom. I will post back soon
Click to expand...
Click to collapse
Ok you need root in twrp you'll need to see # on the command line that's super user sign and you can't reset you efs without out it but recovery might have root with flashing it but I don't think so. Main point flash magisk.
Techguy777 said:
I'm not 100 percent what your saying. I believe your problems is with twrp you need to update twrp to version 3.2.3 which is on the first page of this thread. You need twrp 3.2.3 because the device tree is different for Oreo roms so much that you can't flash them with twrp 3.1.1. Downgrading system was not really the way to do it. I was just saying it worked from marshmallow not that you should be on marshmallow. When I downgraded from nougat firmware q1 and q5 bot to marshmallow I was able to downgrade but I got a drk error upon reboot. I just forced reboot and marshmallow stock worked but Downgrading is not usually good. Let's me also ask did you wipe efs partition with twrp 3.2.1 from the other thread at anytime? Try 3.2.3 either flash tar with Odin or extract img and flash in twrp recovery.
P.s. also yes twrp 355 3.1.1 does work on smt350 very well but still twrp3.2.3 should be the one to use.
If you wiped efs with twrp 3.2.1 and got an error you need to get back on to nougat firmware and then you into twrp terminal in advanced. Type in the first line hit enter then type in second command enter. You will no be able to boot marshmallow but you still might get drk error I got. It's because twrp 3.2.1 came from lte source codes and people think there the same there not the efs partition controls you Bluetooth and wifi on lte I'm sure it controls data. So it's not the same and it damages it and can't fix it because the partitions aren't setup right. I hope this helps. Guys take notes xda is for helping to not just getting root then leaving try to help out.
mke2fs /dev/block/mmcblk0p13
mount -w -t ext4 /dev/block/mmcblk0p13
Click to expand...
Click to collapse
So...I am on stock nougat, nothing installed. I flash twrp 3.1.1, I go into twrp, click install, image, click recovery, root and install, then reboot and hold volume up and home, it says in yellow boot recovery, then goes to black screen. Then cannot power on, cannot boot into recovery, can only boot into download mode and reflash and try again.
---------- Post added at 06:40 PM ---------- Previous post was at 06:34 PM ----------
nubianprince said:
Device?
Firmware?
TWRP version?
Click to expand...
Click to collapse
SM-t350
Q5
TWRP 3.1.1
---------- Post added at 06:42 PM ---------- Previous post was at 06:40 PM ----------
Techguy777 said:
Ok you need root in twrp you'll need to see # on the command line that's super user sign and you can't reset you efs without out it but recovery might have root with flashing it but I don't think so. Main point flash magisk.
Click to expand...
Click to collapse
yes there is a # on my terminal when i open twrp 3.1.1.
i think the problem lies in rebooting after flashing the new recovery twrp, it just doesnt work. i am going to redownload and transfer to my sd card again and see if maybe the download was bad.
---------- Post added at 07:00 PM ---------- Previous post was at 06:42 PM ----------
Techguy777 said:
I'm not 100 percent what your saying. I believe your problems is with twrp you need to update twrp to version 3.2.3 which is on the first page of this thread. You need twrp 3.2.3 because the device tree is different for Oreo roms so much that you can't flash them with twrp 3.1.1. Downgrading system was not really the way to do it. I was just saying it worked from marshmallow not that you should be on marshmallow. When I downgraded from nougat firmware q1 and q5 bot to marshmallow I was able to downgrade but I got a drk error upon reboot. I just forced reboot and marshmallow stock worked but Downgrading is not usually good. Let's me also ask did you wipe efs partition with twrp 3.2.1 from the other thread at anytime? Try 3.2.3 either flash tar with Odin or extract img and flash in twrp recovery.
P.s. also yes twrp 355 3.1.1 does work on smt350 very well but still twrp3.2.3 should be the one to use.
If you wiped efs with twrp 3.2.1 and got an error you need to get back on to nougat firmware and then you into twrp terminal in advanced. Type in the first line hit enter then type in second command enter. You will no be able to boot marshmallow but you still might get drk error I got. It's because twrp 3.2.1 came from lte source codes and people think there the same there not the efs partition controls you Bluetooth and wifi on lte I'm sure it controls data. So it's not the same and it damages it and can't fix it because the partitions aren't setup right. I hope this helps. Guys take notes xda is for helping to not just getting root then leaving try to help out.
mke2fs /dev/block/mmcblk0p13
mount -w -t ext4 /dev/block/mmcblk0p13
Click to expand...
Click to collapse
Also in doing this wihtout having the twrp 3.2.3 and just trying from 3.1.1 results in mount: can't find /dev/block/mmcblk0p13 in /etc/fstab
I tried going into mount and clicking system too, still no dice. Really wanted to try this rom though, but all brick walls.
---------- Post added at 07:02 PM ---------- Previous post was at 07:00 PM ----------
Techguy777 said:
Ok you need root in twrp you'll need to see # on the command line that's super user sign and you can't reset you efs without out it but recovery might have root with flashing it but I don't think so. Main point flash magisk.
Click to expand...
Click to collapse
Soi you want me to flash magisk before I flash the new recovery, because i cant get the new recovery to work at all
And I think it is officially bricked now. I have tried to flash stock rom just to go back to having something that is working and I get the Error android and it gets to about 25 percent and resets to do the same thing. I have tried flashing twice, the official from sammobile, BSOD now.
joejunior253 said:
And I think it is officially bricked now. I have tried to flash stock rom just to go back to having something that is working and I get the Error android and it gets to about 25 percent and resets to do the same thing. I have tried flashing twice, the official from sammobile, BSOD now.
Click to expand...
Click to collapse
alright i think i am done being a whiney beezy. i was able ot do a ton of research, found that i might have had an esf failure or something. i flashed stock firmware, then reset odin without letting it reboot, flashed twrp, booted into it, rebooted the tablet and it works. i think i will wait for a from stock explanation on how to get this to work, i cannot get the recovery file to boot from twrp 3.1.1, it just black screens.
joejunior253 said:
alright i think i am done being a whiney beezy. i was able ot do a ton of research, found that i might have had an esf failure or something. i flashed stock firmware, then reset odin without letting it reboot, flashed twrp, booted into it, rebooted the tablet and it works. i think i will wait for a from stock explanation on how to get this to work, i cannot get the recovery file to boot from twrp 3.1.1, it just black screens.
Click to expand...
Click to collapse
Are you not English speaking? I said you had a efs error that's what I thought. You should have flashed the last version of nougat you had working when the error happened boot into stock and turned on USB debugging. Then you flash twrp either t355 3.1.1 or 3.2.3 are the best. I guess flash 3.1.1 for 355 at first then when you flash twrp on stock nougat boot into twrp and flash magisk 17.1 I'm having trouble with magisk 18 on some devices so use 17.1. Those terminal codes are tricky type them perfect or they don't work I recommend a couple times until it works. They should reset your efs partition then you reboot and flash your firmware again I'd say flash nougat again. Cause I flash marshmallow and got drk error. The firmware doesn't touch efs partition so once you screw it up your ass is grass unless you have a efs backup that works not the one from 3.2.1 twrp that screws everyone up. This is why people should not put stuff out until they have tested it. After you fix efs and can reboot then use twrp to flash twrp 3.2.3 by install image find the twrp 3.2.3 image select recovery. Flash because you can't flash Oreo with twrp 3.1.1. Then you can flash this rom.
You need root so you have to flash magisk in twrp after you flash twrp.
Try this code that will list partition blocks. Your efs should be 13. If it's not you don't have smt350 lol. Those codes work it Should say writing inode or something
ls -l /dev/block/bootdevice/by-name enter
mke2fs /dev/block/mmcblk0p13 enter
mount -w -t ext4 /dev/block/mmcblk0p13
Edit try SuperSU 2..82 sr5 beta or 2.79 sr3 because SuperSU is better for Samsung it's made to disable dm verity I think. Only up to nougat SuperSU will not work on Oreo you'll have to use magisk. The most important thing is after you flash the working stock firmware one of them will work I had this problem to only nougat q1 would work the rest didn't boot. So after I got my tablet running I flashed twrp 355 3.1.1 and went into terminal inside advance in twrp. I typed this commands and it worked it reset my efs partition my Bluetooth worked again my tablet would flash custom roms again and even downgrade back to marshmallow but I'm not recommending that. You type the first one hit enter type the second one hit enter then reboot. The firmware needs to be the same one you had when it errors if it's q5 then q5. I'm trying to help man I don't think your tablet is done I think it'll work again but it'll take some time and effort. You got this man . I always flash root first I don't think you have to because twrp already has root but I would say flash SuperSU first .
joejunior253 said:
So...I am on stock nougat, nothing installed. I flash twrp 3.1.1, I go into twrp, click install, image, click recovery, root and install, then reboot and hold volume up and home, it says in yellow boot recovery, then goes to black screen. Then cannot power on, cannot boot into recovery, can only boot into download mode and reflash and try again.
---------- Post added at 06:40 PM ---------- Previous post was at 06:34 PM ----------
SM-t350
Q5
TWRP 3.1.1
---------- Post added at 06:42 PM ---------- Previous post was at 06:40 PM ----------
yes there is a # on my terminal when i open twrp 3.1.1.
i think the problem lies in rebooting after flashing the new recovery twrp, it just doesnt work. i am going to redownload and transfer to my sd card again and see if maybe the download was bad.
---------- Post added at 07:00 PM ---------- Previous post was at 06:42 PM ----------
Also in doing this wihtout having the twrp 3.2.3 and just trying from 3.1.1 results in mount: can't find /dev/block/mmcblk0p13 in /etc/fstab
I tried going into mount and clicking system too, still no dice. Really wanted to try this rom though, but all brick walls.
---------- Post added at 07:02 PM ---------- Previous post was at 07:00 PM ----------
Soi you want me to flash magisk before I flash the new recovery, because i cant get the new recovery to work at all
Click to expand...
Click to collapse
Read everything i ve posted I said it was efs
Dude your all over the map man
1. Flash nougat firmware the last one you had boot up in the rom
2. Flash twrp 3.1.1
3. Flash SuperSU 2.7.9 or magisk 17.1 probably should go with SuperSU 2.82 SR5 beta.
4. Mack a back up
5. Reboot into rom
6. Reboot back into twrp and type that code it fixes your efs partition and resets it. Into terminal emulator inside twrp try it to it says writing inode or something like that. Both lines.
Reboot .
7. Go back into twrp flash image in install menu find twrp 3.2.3 I'm file make sure it's a image file.
Here's a section of my first post
Let's me also ask did you wipe efs partition with twrp 3.2.1 from the other thread at anytime? Try 3.2.3 either flash tar with Odin or extract img and flash in twrp recovery.
P.s. also yes twrp 355 3.1.1 does work on smt350 very well but still twrp3.2.3 should be the one to use.
If you wiped efs with twrp 3.2.1 and got an error you need to get back on to nougat firmware and then you into twrp terminal in advanced. Type in the first line hit enter then type in second command enter. You will no be able to boot marshmallow but you still might get drk error I got. It's because twrp 3.2.1 came from lte source codes and people think there the same there not the efs partition controls you Bluetooth and wifi on lte I'm sure it controls data. So it's not the same and it damages it and can't fix it because the partitions aren't setup right. I hope this helps. Guys take notes xda is for helping to not just getting root then leaving try to help out.
mke2fs /dev/block/mmcblk0p13
mount -w -t ext4 /dev/block/mmcblk0p13
If you can't boot into nougat go into twrp and type that code into the terminal emulator then when you get it to say writing idone or something it's working if you can't see the screen is black you have to search xda on tab a forms there's a fix a don't remember anyone please if you had twrp black screen what did you do? I've never had it.
---------- Post added at 02:36 PM ---------- Previous post was at 02:24 PM ----------
joejunior253 said:
So...I am on stock nougat, nothing installed. I flash twrp 3.1.1, I go into twrp, click install, image, click recovery, root and install, then reboot and hold volume up and home, it says in yellow boot recovery, then goes to black screen. Then cannot power on, cannot boot into recovery, can only boot into download mode and reflash and try again.
---------- Post added at 06:40 PM ---------- Previous post was at 06:34 PM ----------
SM-t350
Q5
TWRP 3.1.1
---------- Post added at 06:42 PM ---------- Previous post was at 06:40 PM ----------
yes there is a # on my terminal when i open twrp 3.1.1.
i think the problem lies in rebooting after flashing the new recovery twrp, it just doesnt work. i am going to redownload and transfer to my sd card again and see if maybe the download was bad.
---------- Post added at 07:00 PM ---------- Previous post was at 06:42 PM ----------
Also in doing this wihtout having the twrp 3.2.3 and just trying from 3.1.1 results in mount: can't find /dev/block/mmcblk0p13 in /etc/fstab
I tried going into mount and clicking system too, still no dice. Really wanted to try this rom though, but all brick walls.
---------- Post added at 07:02 PM ---------- Previous post was at 07:00 PM ----------
Soi you want me to flash magisk before I flash the new recovery, because i cant get the new recovery to work at all
Click to expand...
Click to collapse
No you can't flash magisk before twrp that makes no sense.
Please let me know what firmware update your trying to flash it Should be a the last one you had when you got the efs error and was able to boot into rom. That firmware only that one. No others will work I had this problem and fixed it. Also what twrp were you using when you got the efs error? Please answer it will help others to not touch it. I noticed that twrp 3.2.1 was taking down so I'm wondering did twrp 3.2.3 cause the error?
---------- Post added at 03:34 PM ---------- Previous post was at 02:36 PM ----------
Everyone did I not explain the fix right? I'm trying to learn how to help people on xda and if you guys think I didn't explain things right please let me know. I am fine with criticism so I can learn how to better help people.
liking it so far (been using for a day), i like the customization options for the UI. it took a bit in the setup thingy... it took a couple tries to get passed the "checking for update" spot. but it runs nicely now
Hi Bro., Can I flash this Rom on t355y ?
Unofficial TWRP Recovery for Moto G7 Power
(XT1955-5/ocean/supra)
I didn't want to wait any longer for an official build of TWRP for the Moto G7 Power (ocean) so I ported it over myself following these directions . So far it appears to work with little to no issue with the exception of decryption of userdata on later rom buids...
I was even able to install fastboot(ed) image to ramdisk & flash Magisk-19.3 via TWRP. Hopefully this can hold some of you off until an official build comes out.
If you guys wish to try it out I have uploaded it to my Android file host here.
Latest attempt HERE
Installation Instructions:
1. You will need to boot image via fastboot initially
Code:
fastboot boot twrp-3.3.1-0-ocean-20190904-0715.img
2. Once TWRP boots push Magisk v19.3 to /tmp/ & flash if not installed or you will bootloop
a.
Code:
adb push Magisk-v19.3.zip /tmp/
b.
Code:
adb shell
c.
Code:
twrp install /tmp/Magisk-v19.3.zip
3. Push twrp-3.3.1-0-ocean-20190904-0715.img to /tmp/
Code:
adb push twrp-3.3.1-0-ocean-20190904-0715.img /tmp/
4. Install recovery to ramdisk via fastboot(ed) TWRP
Code:
Tap Advanced > Install Recovery Ramdisk > Navigate to /tmp/twrp-3.3.1-0-ocean-20190904-0715.img
5. If Magisk is installed prior you may bootloop back to recovery
Code:
Advanced > Fix Recovery Bootloop & Reinstall Magisk
NOTE:
When providing feedback please include the build date of port, carrier, security patch, and rom build number of your G7 Power. The last two items can be found in Settings > System > About phone > tap Android version .
E.g.
20190904-0715
Metro
March 1, 2019
PCO29.114-54-2
good, step 1 is in fastboot mode, the 2,3,4 is the pc? or how can I flash
Yes 1 - 2 PC. 3-4 in TWRP. Pretty simple.
Geofferey said:
Yes 1 - 2 PC. 3-4 in TWRP. Pretty simple.
Click to expand...
Click to collapse
install very well start but not let me do anything on the mobile screen does not respond
Alexhdavila said:
install very well start but not let me do anything on the mobile screen does not respond
Click to expand...
Click to collapse
yes, but when it is installed to the device Ramboot, the screen responds then. Use this image to boot TWRP, then use it to install G's build
---------- Post added at 08:10 PM ---------- Previous post was at 07:49 PM ----------
https://drive.google.com/open?id=1n2YwMJ0CcZU5rze6ibaOM68Ox6bxPL9M
One problem i see here, is that TWRP doesn't decrypt storage when formatting.. GSI systems say it's encrypted still.. isn't it supposed to decrypt when formatting?
Scholeggo said:
One problem i see here, is that TWRP doesn't decrypt storage when formatting.. GSI systems say it's encrypted still.. isn't it supposed to decrypt when formatting?
Click to expand...
Click to collapse
The touch screen works for me when I fastboot it & it works when installed to ramdisk.
I think it worked for me when I used the format data option that requires typing yes. What GSI's are you using? I attempted to install one last night no data/wifi.
@Alexhdavila @Scholeggo
I will need more info. Does touchscreen work when booting via fastboot? Do you have a non US variant? What is output of command lsmod through adb shell in Android?
I can most likely make the screen work for you if you provide that info.
Try the latest one with date appended... Touchscreen should work.
https://drive.google.com/file/d/1Clvwof18aLCF8NQqqjvSCkNEpQAkp6tO/view?usp=sharing
Edit: ^ Touch screen works on initial boot and after for my device. Added driver /vendor/lib/modules/aw8624.ko to /sbin/load_drivers.sh. Though I'm not sure if that is a touch related device and a google of aw8624.ko returns nadda.
Geofferey said:
The touch screen works for me when I fastboot it & it works when installed to ramdisk.
I think it worked for me when I used the format data option that requires typing yes. What GSI's are you using? I attempted to install one last night no data/wifi.
@Alexhdavila @Scholeggo
I will need more info. Does touchscreen work when booting via fastboot? Do you have a non US variant? What is output of command lsmod through adb shell in Android?
I can most likely make the screen work for you if you provide that info.
Try the latest one with date appended... Touchscreen should work.
https://drive.google.com/file/d/14JN1e8OlK_sj-AgpD5i97T-vrB5STOSJ/view?usp=sharing
Click to expand...
Click to collapse
Ok, I did send logs that should indicate that decrypting does not work.. I am using Phhusson's AOSP GSI for this test. My G7 Power is 1955-5 on Metro
If you're on a gsi, go into settings and look into lock screen/security and head down to encryption and credentials, and you will see my point.
This screenshot is in fact taken from my decrypted Moto E5 plus
Scholeggo said:
If you're on a gsi, go into settings and look into lock screen/security and head down to encryption and credentials, and you will see my point.
This screenshot is in fact taken from my decrypted Moto E5 plus
Click to expand...
Click to collapse
Did you update the device to the latest release? I forget where I read but after a certain security update TWRP is no longer able to decrypt user data on some devices. I am still on the OG software that came with device (security patch March 1, 2019), no updates. When I installed magisk on this device and disabled force ecrypt/dm-verity it would no longer boot either. I have yet to try disabling force-encrypt while leaving dm-verity. For me TWRP decrypts my data perfectly when installed to ramdisk but not fastbooting. If you flash a GSI rom in my experience you will have to wipe the data and phone will pretty much force this on you with stock recovery.
Also you didn't answer my question about touch screen. In your post you said to fastboot the test-v1.img then flash mine to ramdisk. Did the touchscreen on my build not work for you when fastbooting?
Edit: Actually I didn't ask lol.
Geofferey said:
Did you update the device to the latest release? I forget where I read but after a certain security update TWRP is no longer able to decrypt user data on some devices. I am still on the OG software that came with device (security patch March 1, 2019), no updates. When I installed magisk on this device and disabled force ecrypt/dm-verity it would no longer boot either. I have yet to try disabling force-encrypt while leaving dm-verity. For me TWRP decrypts my data perfectly when installed to ramdisk but not fastbooting. If you flash a GSI rom in my experience you will have to wipe the data and phone will pretty much force this on you with stock recovery.
Also you didn't answer my question about touch screen. In your post you said to fastboot the test-v1.img then flash mine to ramdisk. Did the touchscreen on my build not work for you when fastbooting?
Edit: Actually I didn't ask lol.
Click to expand...
Click to collapse
huh.. before flashing, i was last on the August build.. and yes, i flashed it to ramdisk and did not have an effect with decrypting the device.
no, touch screen does not work when fastbooting your build.
update: with your newer build (with datestamp), touch still doesn't work on fastboot
@Scholeggo
You tried 20190902-1422? Anything after Jun/July I am
pretty sure can not be decrypted via TWRP currently... that is normal operation. I have this same problem on my Pixel with an official TWRP. Right now my main concern is getting touch working for everyone. If you tried 20190902-1422 and touch doesn't work on fastboot I have some ideas to make it work all around. Do you have Hangouts or something so we can work faster to bring fully functional TWRP together? Since you have a device with the problem. Development via threads is slow.
Geofferey said:
@Scholeggo
You tried 20190902-1422? Anything after Jun/July I am
pretty sure can not be decrypted via TWRP currently... that is normal operation. I have this same problem on my Pixel with an official TWRP. Right now my main concern is getting touch working for everyone. If you tried 20190902-1422 and touch doesn't work on fastboot I have some ideas to make it work all around. Do you have Hangouts or something so we can work faster to bring fully functional TWRP together? Since you have a device with the problem. Development via threads is slow.
Click to expand...
Click to collapse
No Hangouts, but what about Telegram? +561-800-8299
---------- Post added at 12:22 AM ---------- Previous post was at 12:16 AM ----------
Geofferey said:
@Scholeggo
You tried 20190902-1422? Anything after Jun/July I am
pretty sure can not be decrypted via TWRP currently... that is normal operation. I have this same problem on my Pixel with an official TWRP.
Click to expand...
Click to collapse
ok, maybe not decrypt like that, but at least have TWRP not mess up internal storage when wiping system?
On the test-v1 I sent, it does that when wiping system alone, rebooted or not. With yours, it does that only when rebooting recovery; as long as you flash another system right after wiping, internal storage seems to be unaffected with your build.
If not decrypting the storage, it shouldn't mess up internal storage at all when wiping system
I think it's a mechanism of the device. When I flash any GSI on top of any userdata that was created by stock rom it messes up that data, most likely intentionally. That happens with 'fastboot flash system system.img' as well. Can you help me with the touch issues?
Try Me!
LATEST ATTMEPT !
Edit:
My last attempt before I say I don't know what I am doing. I've attempted to include all the kernel modules this recovery should need inside the image. There should be no need for it to load modules from /vendor/lib/modules. Hopefully this fixes the touch screen for most users when fastbooting and installing to ramdisk.
your newest build works touch functions properly
Thank you for the confirmation @OGandroid. Hopefully I can put touch to rest now and find other issues.
Geofferey said:
Thank you for the confirmation @OGandroid. Hopefully I can put touch to rest now and find other issues.
Click to expand...
Click to collapse
In my experience touch works fine booting into TWRP but once installed it's gone
I've tried flashing multiple times. Am I doing something wrong here?
Metro by T-Mobile Variant
Hey man thank you so much for your work! Just wanna triple verify tho! This will work on the metro variant? Also is it possible do you know to flash rims from the other g7 series phones?
yes I have the metropcs variant and it works fine on my device both ways booting or flashing it
---------- Post added at 10:26 PM ---------- Previous post was at 10:21 PM ----------
uHeash said:
In my experience touch works fine booting into TWRP but once installed it's gone
I've tried flashing multiple times. Am I doing something wrong here?
Metro by T-Mobile Variant
Click to expand...
Click to collapse
try the newest build touch works perfectly whether booting into twrp or flashing the ramdisk
OGandroid said:
yes I have the metropcs variant and it works fine on my device both ways booting or flashing it
---------- Post added at 10:26 PM ---------- Previous post was at 10:21 PM ----------
try the newest build touch works perfectly whether booting into twrp or flashing the ramdisk
Click to expand...
Click to collapse
Sick man this is awesome I've been waiting for this! Now for some rims and it'll be smooth sailing!
ArrowOS
ABOUTArrowOS is an AOSP/CAF based project started with the aim of keeping things simple, clean and neat.
Website: https://arrowos.net
Github: https://github.com/ArrowOS
Code Review: review.arrowos.net
E-mail: arrowos.contact
PayPal: paypal
changelog and future updates
join moto x4 telegram channel
WHAT WORKS?
Almost everything
WHAT DOESN'T WORK?
You tell me
Be sure to include a log
screenshot thanks to domenik (MotoX4Custom) for this website
INSTALLATION
click here
DOWNLOADS
ROM: Arrow-OS for payton
download
Gapps included
Source Code: https://github.com/ArrowOS
Device Source: https://github.com/mhdaslam790/device-motorola-payton
ROM OS Version: Android 10
ROM Kernel: Linux 3.x.x
Based On: AOSP 10.0
mhdaslam790 said:
ArrowOS
ABOUTArrowOS is an AOSP/CAF based project started with the aim of keeping things simple, clean and neat.
Website: https://arrowos.net
Github: https://github.com/ArrowOS
Code Review: review.arrowos.net
E-mail: arrowos.contact
PayPal: paypal
WHAT WORKS?
Almost everything
WHAT DOESN'T WORK?
You tell me
Be sure to include a log : check how to
DOWNLOADS
ROM: Arrow-OS for payton
download
Gapps included
Source Code: https://github.com/ArrowOS
Device Source: https://github.com/mhdaslam790/device-motorola-payton
ROM OS Version: Android 10
ROM Kernel: Linux 3.x.x
Based On: AOSP 10.0
Click to expand...
Click to collapse
ScreenShots??
srishab55 said:
ScreenShots??
Click to expand...
Click to collapse
Screenshots are here
https://motox4custom.jimdofree.com/android-10/arrow-os/
Can anyone confirm whether Voice Match (OK Google) is working in this ROM? It appears that it might be causing mic issues in other Android 10 ROMs. Thanks!
jhedfors said:
Can anyone confirm whether Voice Match (OK Google) is working in this ROM? It appears that it might be causing mic issues in other Android 10 ROMs. Thanks!
Click to expand...
Click to collapse
Working fine
Thank you for not only this rom but also the custom website!
---------- Post added at 04:32 AM ---------- Previous post was at 03:58 AM ----------
What does ' Error applying update:15 ( ErrorCode:kNewRootfsVerificationError )' mean? I don't know how to solve it.
EthonBanks said:
Thank you for not only this rom but also the custom website!
---------- Post added at 04:32 AM ---------- Previous post was at 03:58 AM ----------
What does ' Error applying update:15 ( ErrorCode:kNewRootfsVerificationError )' mean? I don't know how to solve it.
Click to expand...
Click to collapse
Website is made by Dominick (motox4custom)
Huge shout out to him
Are MOTO actions included in this ROM and working?
Lakynko said:
Are MOTO actions included in this ROM and working?
Click to expand...
Click to collapse
Of course!
Already tried thank you
And must write, that very good ROM! Big thanks.
No bugs so far. Everything goes smoothly.
Stayed on a daily use!
PS: Came from Superior OS
I would appreciate some help. I took a FI X4 and installed Arrow with no issues. Then I tried to re-install with gapps and things went south. Maybe I'm being bitten by the A/B thing.
My current state:
SCENARIO 1
* Clean install Stock FI for X4 works
* Then "copy partitions" and reboot to System fails and reboots to Recovery. <-- Not sure why this happens
SCENARIO 2
* Clean install Stock FI again -- boots and works fine
* fastboot boot twrp, wipe, install Arrow -- install gives no errors
* Reboot to system results in endless Arrow boot animation. I've waited for a couple of hours, so it's not a matter of time.
Suggestions on what I can try? Is "copy partitions" really necessary? (I've put Lineage on two other X4's without using 'copy partitions' -- I didn't even know about it at the time.)
Randy Power said:
I would appreciate some help. I took a FI X4 and installed Arrow with no issues. Then I tried to re-install with gapps and things went south. Maybe I'm being bitten by the A/B thing.
My current state:
SCENARIO 1
* Clean install Stock FI for X4 works
* Then "copy partitions" and reboot to System fails and reboots to Recovery. <-- Not sure why this happens
SCENARIO 2
* Clean install Stock FI again -- boots and works fine
* fastboot boot twrp, wipe, install Arrow -- install gives no errors
* Reboot to system results in endless Arrow boot animation. I've waited for a couple of hours, so it's not a matter of time.
Suggestions on what I can try? Is "copy partitions" really necessary? (I've put Lineage on two other X4's without using 'copy partitions' -- I didn't even know about it at the time.)
Click to expand...
Click to collapse
Clean flash stock firmware
Then flash twrp format in f2fs and reboot
Boot to twrp and Flash copy partition and take persist efs backup
Then wipe data system dalvik
Flash rom+ twrp zip
Reboot recovery and flash magisk if you want...(you dont need to flash gapps BECAUSE it is included in rom)
Just reboot to system
Have look on this website for issue https://motox4custom.jimdofree.com/instructions/install-a-custom-rom/
Trouble installing
EDIT: Got it working!
I gave up waiting for the animation. Switched /data's file system to e2fs, formatted, re-installed Arrow+TWRP and badaboom! Arrow started up successfully. I think I was missing the "format /data" step after switching its fs.
Thank you
------------ END UPDATE -----------
mhdaslam790 said:
Clean flash stock firmware
Then flash twrp format in f2fs and reboot
Boot to twrp and Flash copy partition and take persist efs backup
Then wipe data system dalvik
Flash rom+ twrp zip
Reboot recovery and flash magisk if you want...(you dont need to flash gapps BECAUSE it is included in rom)
Just reboot to system
Have look on this website for issue https://motox4custom.jimdofree.com/instructions/install-a-custom-rom/
Click to expand...
Click to collapse
Thanks for the quick help and reference. I'm not sure if it worked yet or not... It's been running the Arrow boot animation for 20 minutes so far. I'll report back.
Questions:
Is TWRP's warning of "No OS Installed" something I can ignore? (see attached photo)
Why do you recommend a backup of efs and persist? I don't see it used later.
I did not switch /data to f2fs this time because it completely failed (Stock wouldn't boot up). Is f2fs required?
How long should I wait while the boot animation runs before giving up?
Can I capture a log that would be helpful troubleshooting what's going on with the boot?
Here's what I did:
Clean flash stock firmware (XT1900-1_PAYTON_FI_9.0_PPWS29.69-39-6-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip)
Reboot to "Get Started" screen - SUCCESS
Boot to twrp
Flash copy partition
Reboot to "Get Started" screen (confirm all is still working) - SUCCESS
Make backup of persist and efs
Wipe data, system, dalvik
Flash Arrow (did not flash magisk or gapps) File: Arrow-v10.0-payton-UNOFFICIAL-20200119-VANILLA.zip
Flash twrp installer (zip)
Reboot to system --
- twrp warned of "no os installed"
- arrow boot animation
The latest update wiped out fingerprint gestures. It is turned on, but does not work.
What does ' Error applying update:15 ( ErrorCode:kNewRootfsVerificationError )' mean?
I tried both TWRP-payton-3.3.1-Syber-v2.2_11-02 and official twrp
step 1/2...
step 2/2...
Error applying update:15 ( ErrorCode:kNewRootfsVerificationError )
Fingerprint gestures don't work. And hope we can disable the battery charging LED.
johnjingle said:
The latest update wiped out fingerprint gestures. It is turned on, but does not work.
Click to expand...
Click to collapse
Wait for next update
Update -- I went back to stock and now can't get any mobile signal. No voice, no 2G; it's dead. The SIM works fine in my other (Lineage) X4. Looks like bad hardware.
----- end of update -----
Hi all. I'm taking my Arrow-powered new-to-me X4 out today for the first time and just realized it's not getting 4G. In fact, it's all the way back to Edge. My network is set to Global and I'm on T-Mobile USA.
Is LTE working for others here?
I can switch to stock later to check the hardware on this device but that will take some time.
Randy Power said:
Update -- I went back to stock and now can't get any mobile signal. No voice, no 2G; it's dead. The SIM works fine in my other (Lineage) X4. Looks like bad hardware.
----- end of update -----
Hi all. I'm taking my Arrow-powered new-to-me X4 out today for the first time and just realized it's not getting 4G. In fact, it's all the way back to Edge. My network is set to Global and I'm on T-Mobile USA.
Is LTE working for others here?
I can switch to stock later to check the hardware on this device but that will take some time.
Click to expand...
Click to collapse
Doesn't work for me, I do even get 3G, only phone calls.
johnjingle said:
Doesn't work for me, I do even get 3G, only phone calls.
Click to expand...
Click to collapse
Sorry to hear.
I acquired a different X4 and installed Arrow without incident and I'm getting 4G on T-Mobile USA fine now. Maybe you also have bad hardware? Does LTE work on your phone with different firmware?
---------- Post added at 01:47 AM ---------- Previous post was at 01:35 AM ----------
How does the Updater work?
In Settings, I can search for "update" and see "System updates" in the search results. Tapping on that brings up the System menu but there is no "System updates" listed.
I flashed 20200119 a couple of days ago and I thought it's been updated since then.