[ROM][9.0][UN-OFFICIAL][ravel][16.01.2020] crDroid v5.11 - Honor Note 10 ROMs, Kernels, Recoveries, & Other D

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/10.0/README.mkdn
Flashing Instructions:
Pre-installation:
TWRP (Download from here)
gapps (Download from here)
Magisk for Treble for root (after first boot) - (Download from here)
First time installation:
Instructions :
* First of all you need to flash this twrp (I recommend) if not this you can also use other available twrp's.
* Boot into twrp and Format data and wipe system/data/cache/dalvik.
* Flash the rom zip
* After installing the rom , flash the gapps i am going to add into the downloads section.
* If you want to root, flash Magisk
* Reboot to System.
What working?
* camera
* Bluetooth
* wifi
* hotspot
* fingerprint
* livedisplay
* ambient display
* most everything work!
Sources:
ROM: https://github.com/crdroidandroid
Kernel: -foe.kernel
Device-Tree: -kirin970
Download:
ROM AFH
Known issues:
*none
Visit official website @ crDroid.net
crDroid ravel Telegram
crDroid Community Telegram
Donate to help our team pay server costs

Changelog...
*09-01-2020
Initial release
*10-01-2020
Fix major bug
Fix camera / flashlight
Fix ambient display
Fix deep.sleep
Fix wakelock
Fix battery 5000mah
Fix superquick charge ratio
*16-01-2020
Fix deep sleep
Fix aod brightness scale =3
Fix aptouch-deamon

Downloading....

i have tons of apps on my honor note 10 but i would like to try this if anybody can tell how's the sound quality compared to stock rom.
also does the stereo works correctly when the phone is in landscape to the right? tried some open kirin roms and it was awful. stereo channels were inverted if you rotate phone to the right, and you couldn't hear footsteps in pubg.

Do you need to have EMUI 9 to flash? Really looking forward to testing this...

ForgottenSolstace said:
Do you need to have EMUI 9 to flash? Really looking forward to testing this...
Click to expand...
Click to collapse
it needs emui 8

Error installing zip file. This package is for device: ravel; this device is kirin970
---------- Post added at 06:53 PM ---------- Previous post was at 06:51 PM ----------
Probably should edit
Code:
META-INF\com\google\android\updater-script
---------- Post added at 07:02 PM ---------- Previous post was at 06:53 PM ----------
Got this now that I fixed the updater-script:
assert failed: run_program("/sbin/sh", "/system/bin/releasetools.kirin970.sh") == 0
Updater process ended with ERROR: 7
Error installing zip file "/external_sd/...
Click to expand...
Click to collapse
---------- Post added at 07:14 PM ---------- Previous post was at 07:02 PM ----------
Update: it doesn't install correctly, even when I change the device names in updater-script. The device doesn't boot, and skips straight to e-recovery. I also think recovery (TWRP) got overwritten with the flash via the boot img rewrite, so I have to revert to stock to try again.

are you on emui 8 or 9?

dvijetrecine said:
are you on emui 8 or 9?
Click to expand...
Click to collapse
EMUI 8

which twrp you used?

dvijetrecine said:
which twrp you used?
Click to expand...
Click to collapse
This one: https://androidfilehost.com/?fid=11410932744536987360
---------- Post added at 03:38 AM ---------- Previous post was at 03:27 AM ----------
Currently, my phone hangs on the TWRP logo (your TWRP, even when I install your version . I had gotten the old version of TWRP to run upon reverting to stock (stock still wouldn't boot, though, even after reverting via EMUI recovery), but /system would only get mounted read-only. So kind of stuck here. I also tried fastboot flash system on a number of images with no success in booting. I recall I had to flash a zip to disable encryption of /system. Is that still the case, and if so where do I find that zip?

ForgottenSolstace said:
This one: https://androidfilehost.com/?fid=11410932744536987360
---------- Post added at 03:38 AM ---------- Previous post was at 03:27 AM ----------
Currently, my phone hangs on the TWRP logo (your TWRP, even when I install your version . I had gotten the old version of TWRP to run upon reverting to stock (stock still wouldn't boot, though, even after reverting via EMUI recovery), but /system would only get mounted read-only. So kind of stuck here. I also tried fastboot flash system on a number of images with no success in booting. I recall I had to flash a zip to disable encryption of /system. Is that still the case, and if so where do I find that zip?
Click to expand...
Click to collapse
it's not mine. i just have some experience with flashing roms on this phone

okay, so i managed to install the rom successfully.
it was a bit of a trial and error but i made it.
so, you need to be on emui 8. if you're on emui 9, here is the link on how to downgrade: https://huaweiadvices.com/downgrade-huawei-android-pie-emui-9-0-to-oreo-emui-8/
after you downgraded your phone successfully, you can proceed to the next step.
next step is installing the right recovery. first, you install this one: https://androidfilehost.com/?fid=11410932744536987360
then you flash rom and gapps. boot into OS. if you did everything right, it should boot.
now, with the recovery we installed, there will be error with read only system and you won't be able to use your phone right.
so, next step is to install this recovery: https://androidfilehost.com/?fid=4349826312261697516
now the order of installing stuff is very important. don't install second recovery before doing all the steps above.
after successfull installation of second recovery, you will need to wipe data. not just factory reset but full wipe.
when the wiping is done, you can now install rom again, gapps and magisk. then you install this zip: https://zackptg5.com/downloads/Disable_Dm-Verity_ForceEncrypt_01.15.2020.zip
by the name of the zip you could figure out that it is about disabling force encryption and all that good stuff.
and you are done. now everything should work properly.
problems so far: when you rotate phone to the right, stereo doesn't follow orientation so it's reversed and you can't play fps games. also, overall sound quality is bad

dvijetrecine said:
okay, so i managed to install the rom successfully.
it was a bit of a trial and error but i made it.
so, you need to be on emui 8. if you're on emui 9, here is the link on how to downgrade: https://huaweiadvices.com/downgrade-huawei-android-pie-emui-9-0-to-oreo-emui-8/
after you downgraded your phone successfully, you can proceed to the next step.
next step is installing the right recovery. first, you install this one: https://androidfilehost.com/?fid=11410932744536987360
then you flash rom and gapps. boot into OS. if you did everything right, it should boot.
now, with the recovery we installed, there will be error with read only system and you won't be able to use your phone right.
so, next step is to install this recovery: https://androidfilehost.com/?fid=4349826312261697516
now the order of installing stuff is very important. don't install second recovery before doing all the steps above.
after successfull installation of second recovery, you will need to wipe data. not just factory reset but full wipe.
when the wiping is done, you can now install rom again, gapps and magisk. then you install this zip: https://zackptg5.com/downloads/Disable_Dm-Verity_ForceEncrypt_01.15.2020.zip
by the name of the zip you could figure out that it is about disabling force encryption and all that good stuff.
and you are done. now everything should work properly.
problems so far: when you rotate phone to the right, stereo doesn't follow orientation so it's reversed and you can't play fps games. also, overall sound quality is bad
Click to expand...
Click to collapse
Thanks for posting this. So in my situation, with a read-only /system on EMUI 8, and a TWRP that hangs on the logo, do I need to revert to stock via Hi-suite? I'm in the process of trying dload method to get to EMUI 9 and try some other ROMs at the moment

you just need to flash stock recovery and do a factory reset or full wipe. that should do it

dvijetrecine said:
you just need to flash stock recovery and do a factory reset or full wipe. that should do it
Click to expand...
Click to collapse
I tried exactly this, but TWRP still hangs on the TWRP logo (both versions). I had locked, stock EMUI 9 running from the dload method, so I did fastboot oem unlock with my bootloader code, which worked. Then a forced factory reset, and without first booting, I flashed twrp. No luck.
Any suggestions? I may also need stock recovery for EMUI 9 if you know where to find that...

you should let it boot. install emui with dload, let it boot and then try flashing twrp. it might hang a bit, but it will work. sometimes a reboot is needed

I got this ROM to install manually via fastboot flash system once I upgraded to EMUI 9. The problem is, now I can't even get to TWRP when I fastboot flash recovery_ramdisk and then press the volume keys (it just goes to EMUI now). I'll continue experimenting
---------- Post added at 05:33 PM ---------- Previous post was at 05:17 PM ----------
Update: the phone was in a transitory state, where running the dload method had failed, hence /system was unencrypted and booting to recovery_ramdisk would fail. I did volume+up on boot to load EMUI recovery, tried a factory reset, and now hanging again at TWRP. Will try a factory reset with legacy EMUI recovery and repeat...

when on emui 9, it's pretty hard to get into twrp. you have to hold on vol up and power when booting to get into twrp. and also, those open kirin roms are no better than this one. this one even feels like the best
---------- Post added at 01:41 AM ---------- Previous post was at 01:36 AM ----------
ForgottenSolstace said:
I got this ROM to install manually via fastboot flash system once I upgraded to EMUI 9. The problem is, now I can't even get to TWRP when I fastboot flash recovery_ramdisk and then press the volume keys (it just goes to EMUI now). I'll continue experimenting
---------- Post added at 05:33 PM ---------- Previous post was at 05:17 PM ----------
Update: the phone was in a transitory state, where running the dload method had failed, hence /system was unencrypted and booting to recovery_ramdisk would fail. I did volume+up on boot to load EMUI recovery, tried a factory reset, and now hanging again at TWRP. Will try a factory reset with legacy EMUI recovery and repeat...
Click to expand...
Click to collapse
just be careful. huawei phones are pretty finicky and love to brick when you interrupt them in upgrading, downgrading or installing anything. it's all good when you go to custom roms, but those often lack features. i had high hopes for this rom but i just can't get over the fact how bad the sound quality is compared to the stock rom. i'm returnig back to emui 8 and probably will sell this phone in some time. thinking about buying rog phone 2, but i love the big screen of the honor note 10

dvijetrecine said:
when on emui 9, it's pretty hard to get into twrp. you have to hold on vol up and power when booting to get into twrp. and also, those open kirin roms are no better than this one. this one even feels like the best
---------- Post added at 01:41 AM ---------- Previous post was at 01:36 AM ----------
just be careful. huawei phones are pretty finicky and love to brick when you interrupt them in upgrading, downgrading or installing anything. it's all good when you go to custom roms, but those often lack features. i had high hopes for this rom but i just can't get over the fact how bad the sound quality is compared to the stock rom. i'm returnig back to emui 8 and probably will sell this phone in some time. thinking about buying rog phone 2, but i love the big screen of the honor note 10
Click to expand...
Click to collapse
Yes, indeed: you need to press and HOLD the volume up rocker AND hold the power button for a real delay. You might expect the phone to turn off again, but it doesn't. You boot to TWRP.
Now, I have the first TWRP installed, but it still hangs on the TWRP logo (EMUI 9). Not sure if I missed a step, but here's what I did:
dload method to EMUI 9 latest
boot to download mode; fastboot oem unlock
wait for factory reset
let the phone reboot. Turn it off to download mode again
flast twrp to recovery_ramdisk
boot to recovery with aforementioned method
Hopefully, I missed something down the line, because I really need root at the very least. Unless someone can point me to the stock boot.img file, I don't see how I'll get root on this device if TWRP won't boot.

Related

Last night's OTA update bricked XT1521

My XT1521 is stuck at Fastboot, after trying to install last night's OTA update. The Bootloader Logs screen says "failed to validate system image" followed by "Boot up failed".
All of my important data is backed up. I don't care about preserving any data on the phone; I just want to get it working again.
The attached photo shows what I can see.
After connecting the USB cable, "fastboot devices" returns TA38502SB6 fastboot
Is this something I can fix myself, with appropriate software? Will I need to approach Motorola? Is it beyond help?
Flash the twrp recovery using fastboot, install a rom and the squid kernel. The Rom is pretty stable now..
---------- Post added at 09:05 PM ---------- Previous post was at 08:33 PM ----------
Or else you can download the stock Rom
http://motofirmware.center/files/fi...2_lxi2250-531_cid7_subsidy-default_cfcxmlzip/
And the guide is : http://forum.xda-developers.com/mot...e-restore-moto-e-2015-stock-firmware-t3044936
rushabshah32 said:
Flash the twrp recovery using fastboot, install a rom and the squid kernel. The Rom is pretty stable now..
---------- Post added at 09:05 PM ---------- Previous post was at 08:33 PM ----------
Or else you can download the stock Rom
http://motofirmware.center/files/fi...2_lxi2250-531_cid7_subsidy-default_cfcxmlzip/
And the guide is : http://forum.xda-developers.com/mot...e-restore-moto-e-2015-stock-firmware-t3044936
Click to expand...
Click to collapse
Those look very useful, thank you. Gives me something to do this evening!
Loganberry said:
My XT1521 is stuck at Fastboot, after trying to install last night's OTA update.
Click to expand...
Click to collapse
Was it the stock 5.1 update???
Software status: modified
How did you get the OTA update and what did you do previously ?
Recovery log says you had a modified software. So there was no hope to apply patch properly. And it bricked your system
rushabshah32 said:
Was it the stock 5.1 update???
Click to expand...
Click to collapse
Not sure. It was only around 20-30MB or so; can't remember the exact size.
PsyClip-R said:
How did you get the OTA update and what did you do previously ?
Recovery log says you had a modified software. So there was no hope to apply patch properly. And it bricked your system
Click to expand...
Click to collapse
OTA update was advertised through the normal Motorola OTA feature. All I did was to tap on "Yes, I'm in" to accept it when it was offered.
If my phone's ruined, then it's ruined. Irritating, but not the end of the world; a new Moto E2 isn't expensive. I'd just prefer not to have to buy a new one if there's any hope of resurrecting this one. As I indicated in my first post, the important data is safe; I just want a working phone again.
Edit: just re-read your question; realised I might have misunderstood part of it.
My phone had previously been rooted; before accepting the OTA update I went through the steps to unroot the phone before taking the OTA update; looks like something went wrong somewhere along the way.
Loganberry said:
My XT1521 is stuck at Fastboot, after trying to install last night's OTA update. The Bootloader Logs screen says "failed to validate system image" followed by "Boot up failed".
All of my important data is backed up. I don't care about preserving any data on the phone; I just want to get it working again.
The attached photo shows what I can see.
After connecting the USB cable, "fastboot devices" returns TA38502SB6 fastboot
Is this something I can fix myself, with appropriate software? Will I need to approach Motorola? Is it beyond help?
Click to expand...
Click to collapse
i got the update yesterday too on my X1521 but it was working fine.after immediate reboot it was lagging like hell but rebooting solved it
Guys don't panic. What I would do is unlock the bootloader and flash TWRP, after that just download any custom ROM and TWRP lets you get on MTP so you can transfer the ROM to the internal storage.
---------- Post added at 06:58 PM ---------- Previous post was at 06:57 PM ----------
Also there's plenty of stock ROMS out there like SuperR's Stock Roms
I have a similar issue, I just accepted the OTA update from Motorola on my XT1511(otus), It was stock/rooted. The phone went into boot loop. Tried these things to remedy
1) tried booting to TWRP from fastboot. I'd get the TWRP splash screen, but no functionality
2)flashed TWRP - now have functioning recovery, but during rom flash get "error, cant mount /data
3)fastboot -w successfully wiped data, but couldn't format partition, still raw
4)From twrp "mount" screen couldn't check the box for mounting data
5)from twrp wipe>format data was able to format the partition
6) I've flashed a couple of twrp recovery images, and a couple of different roms, I don't get error messages, but now when the phone is powered on it always boots into recovery, even when reboot>system or reboot power off is selected. I can still access fast boot.
Any suggestions? I'm going to try returning to stock at this point'
Update: Downloaded stock recovery here:
http://forum.xda-developers.com/devdb/project/dl/?id=11977
Installed with fastboot, phone boots properly now!

[HOW TO] remove device encryption and get superSU

The below steps are only part of the solution since there are a couple of prerequisites (with solutions for those already on these forums and MIUI sites). I'm afraid since it's getting late here, I cannot provide detailed steps for everything, I'm assuming you are like me and only got so far, so already know what you're doing
I'm not responsible for hard bricks, however if any steps I've entered are entirely wrong, please do let me know. I'm only trying to help the community out.
What you need:
Unlocked bootloader, sadly you will have to wait for the permission from them (I don't like this process either)
Decent knowledge of TWRP menu system
no care for completely wiping the SD Card contents - please make a backup of pictures or anything else you want
adb and fastboot both working and recognising the phone properly
Gemini (Xiaomi Mi 5) TWRP - https://drive.google.com/file/d/0B95J_je8rRN0V1Y2T2o0Mlh2R1E/view?usp=docslist_api **Thanks to Nesquix for posting the link to this** it is in Chinese and the theme changing solution did not work for me - but this doesn't really matter if you know your way around TWRP
Latest SuperSU - https://download.chainfire.eu/924/SuperSU/BETA-SuperSU-v2.68-20160228150503.zip
Latest DEV Fastboot ROM - I cannot post the link however it can be found by searching for "mi 5 fastboot developer rom" on Google and selecting the link going to en.miui.com
STEPS to take:
Extract the contents of the fastboot ROM to a location of your choice. The only file you need is this one: \...\...\images\system.img (if someone can upload separately, I'll link in OP)
Place both the system.img from the fastboot ROM and twrp img file in the location of your fastboot folder
Enter fastboot mode (bootloader) on the Mi 5 via Power off --> volume down + power on --> let go once you see the MI logo
Check your device can be seen via the command, fastboot devices --> ENTER
Now input the following command, fastboot flash recovery twrp-mi5.img --> ENTER
Now enter in to recovery via volume up + power on - There appears to be a bug with TWRP whereby on some boots, touch isn't responsive, just keep booting back till it works (it will eventually)
Swipe on the first screen to enter the menu, tap the top right icon for wiping data, then the bottom right icon, you will see a text box with a warning - enter yes, then tick to fully wipe the SD card
Power off again, and reboot back to fastboot mode (bootloader)
Once there, input this command, fastboot flash system system.img --> ENTER
Once the system is flashed, input this command, fastboot reboot
Skip past initial steps for speed place the superSU zip on the root of the SD Card and then reboot back to recovery again
Flash SuperSU in recovery (top left option, find your zip, flash it
Reboot system
PROFIT - you now have an unencrypted system with working superSU and apps like Adaway work flawlessly - HAVE FUN and don't forget to say thanks if I did actually help you
Interesting notes.....
I'm not sure about anyone else, but I found web browsing to be alarmingly slow with no good explanation, the above steps completely resolved this
Google is now a search option in the default browser (it wasn't before!!)
Call it placebo all you want, but the phone really does seem a lot faster now.
Last but not least, I'm fairly certain to update to newer versions, you only have to extract same system.img from future fastboot ROM zips, and flash this on it's own to update the system.
To get the multilingual functionality of TWRP working, copy this file in TWRP\theme
You can also change the theme color in the advanced settings .
https://drive.google.com/file/d/0B95J_je8rRN0N19DLXdFYXV4NW8/view?usp=docslist_api
nesquix said:
To get the multilingual functionality of TWRP working, copy this file in TWRP\theme
You can also change the theme color in the advanced settings .
https://drive.google.com/file/d/0B95J_je8rRN0N19DLXdFYXV4NW8/view?usp=docslist_api
Click to expand...
Click to collapse
I think we dont need to copy TWRP theme. You can set language in first welcome screen or in Settings menu, and tap "world icon".
Here is the attachment of TWRP Screenshot :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---------- Post added at 03:38 PM ---------- Previous post was at 03:26 PM ----------
kickassdave said:
The below steps are only part of the solution since there are a couple of prerequisites (with solutions for those already on these forums and MIUI sites). I'm afraid since it's getting late here, I cannot provide detailed steps for everything, I'm assuming you are like me and only got so far, so already know what you're doing
.
Click to expand...
Click to collapse
I think we dont need to flash system.img. check out my post here. After flashing TWRP via fastboot, format data and type yes in TWRP, all you need to do is reboot to system and swipe disable stock recovery flash. Setup your Mi5 and then copy SuperSU 2.65 or 2.68 beta to your Mi5. Next is reboot back to recovery, swipe allow modification, and then flash the SuperSU. Done. I tested out on Dev ROM and Stable ROM too, that there is no need to flash system.img again.
tomhtg90 said:
I think we dont need to copy TWRP theme. You can set language in first welcome screen or in Settings menu, and tap "world icon".
Here is the attachment of TWRP Screenshot :
---------- Post added at 03:38 PM ---------- Previous post was at 03:26 PM ----------
I think we dont need to flash system.img. check out my post here. After flashing TWRP via fastboot, format data and type yes in TWRP, all you need to do is reboot to system and swipe disable stock recovery flash. Setup your Mi5 and then copy SuperSU 2.65 or 2.68 beta to your Mi5. Next is reboot back to recovery, swipe allow modification, and then flash the SuperSU. Done. I tested out on Dev ROM and Stable ROM too, that there is no need to flash system.img again.
Click to expand...
Click to collapse
When I set to English in TWRP without the theme mod, it instantly reverts to Chinese.
With regards to flashing the system.img, I have a slight nagging issue with regards to the amount of files inside the fastboot image which WEREN'T required for full functionality.
I'm also concerned about where my data was going when browsing, as my browsing was slow no matter which browser I used - almost as if it was proxying via China.
Having only flashed system.img I no longer have this issue.
kickassdave said:
When I set to English in TWRP without the theme mod, it instantly reverts to Chinese.
With regards to flashing the system.img, I have a slight nagging issue with regards to the amount of files inside the fastboot image which WEREN'T required for full functionality.
I'm also concerned about where my data was going when browsing, as my browsing was slow no matter which browser I used - almost as if it was proxying via China.
Having only flashed system.img I no longer have this issue.
Click to expand...
Click to collapse
English languages in TWRP will not go back to chinese if you tap on "Never show this screen during boot again", "swipe to allow modification" and "Swipe disable recovery flash". But, if that's the only method that work for you, good then. Cheers
No need to flash again system here too
What exactly do the rest of the contents of the ROM contain then since I literally flashed on a single img from the entire zip!
I have mine Mi5 unlocked, with TWRP, root (SU) open encryption.
I'm on china dev rom 6.3.17 and would like to upgrade to 6.3.24, as I have some issues (camera force close after trying to get picture during video recording and some apps crashes).
Anyway, my question is: HOW should I update system and not lose all my setting, apps, data, etc and of course I can't lose root, open encryption and unlocked bootloader.
Please advise.
1myxomatosis1 said:
I have mine Mi5 unlocked, with TWRP, root (SU) open encryption.
I'm on china dev rom 6.3.17 and would like to upgrade to 6.3.24, as I have some issues (camera force close after trying to get picture during video recording and some apps crashes).
Anyway, my question is: HOW should I update system and not lose all my setting, apps, data, etc and of course I can't lose root, open encryption and unlocked bootloader.
Please advise.
Click to expand...
Click to collapse
this is what i'm trying to do now. but i'm on another base... not the 6.3.17 but the 7.2.7.0, anyway this is the same procedure.
when you have unlocked your bootloader, there is no way to encrypt all data again if you don't select "flash_all_lock.bat" with MiFlash windows app...
so you can play all TWRP partitions...except the SDCARD (called "data/media", don't mingle/mix up/confound with the "data" partition.... )
So since fastboot is still open with your unlocked bootloader are always able to reflash a recovery and do whatever you want again, don't panic !
i tried updating my rom 7.2.7.0 to 6.3.24 by flashing the system.img BUT there are some force close.... security center FC... wifi not working... i think they forgot to say that we need to manually flash the boot.img too (kernel.... who contain a lot of drivers and system links...)
so i just flashed the system.img and boot.img of the 6.3.24 on my 7.2.7.0 rom, i will report my feedback in some hours max. EDIT : WORKING !
but don't wory, since you don't wipe your SDCARD in the recovery (or use the flash_all_lock.bat with MiFlash), you will not loose your decrypted data partition
if my method of "simple updating" is not working by just flashing system.img and boot.img over the rom........ i suggest to reflash all partition with adb (system.img and boot.img), after that you can reboot to the twrp recovery, flash supersu 2.68 (or the last one) to be root, and setup your phone again... (you can do a MiBackup in the settings, and restore it later, this is working fine for your app, settings and so on)
:silly:
---------- Post added at 08:21 PM ---------- Previous post was at 08:13 PM ----------
UPDATE : WORKING.
Procedure to UPDATE since your phone have UNLOCKED BL, data decrypted and TWRP already flashed (or you can flash it before the procedure by adb) :
PROCEDURE
just flash the system.img AND the boot.img with adb in the CMD
(be sure your files are in the same folder of adb.exe and fastboot.exe)
"fastboot flash system system.img"
"fastboot flash boot boot.img"
then reboot to twrp recovery... flash supersu 2.68..
you don't need to wipe something.
just reboot and wait.
your phone is now updated, with root, twrp, decrypted data, and you don't loose your apps, settings and files. :good:
nesquix said:
[...]
PROCEDURE
[...]
Click to expand...
Click to collapse
Sound so easy and so fantastic that I can't just believe I'll try tomorrow as today I don't have power if something went wrong and I would have to start from a zero point:]
1myxomatosis1 said:
Sound so easy and so fantastic that I can't just believe I'll try tomorrow as today I don't have power if something went wrong and I would have to start from a zero point:]
Click to expand...
Click to collapse
I can't flash anything on TWRP, I can't mount the data... and so there's no file in sdcard
so at which point is the phone unencrypted? With installing SuperSU ?!
I also have the provlem, that TWRP changes the language instantly after changing it. And it also prompts me for password of encrypted partitions
Ivyn87 said:
I can't flash anything on TWRP, I can't mount the data... and so there's no file in sdcard
Click to expand...
Click to collapse
Because your phone is still encrypted.
So read all 3stpage and you will understand what you need to do.
http://forum.xda-developers.com/mi-5/help/rooting-mi-4-unlocking-bootloader-t3334677/page3
---------- Post added at 04:12 PM ---------- Previous post was at 04:11 PM ----------
p1nky said:
so at which point is the phone unencrypted? With installing SuperSU ?!
I also have the provlem, that TWRP changes the language instantly after changing it. And it also prompts me for password of encrypted partitions
Click to expand...
Click to collapse
After wiping all the phone 2 times in the twrp recovery.
nesquix said:
Because your phone is still encrypted.
So read all 3stpage and you will understand what you need to do.
http://forum.xda-developers.com/mi-5/help/rooting-mi-4-unlocking-bootloader-t3334677/page3
---------- Post added at 04:12 PM ---------- Previous post was at 04:11 PM ----------
After wiping all the phone 2 times in the twrp recovery.
Click to expand...
Click to collapse
Very thanks... now it work
Why can't TWRP write to encrypted partitions? I thought this is possible with TWRP 3.0. At least I have not heard from new Nexus owners that disabling encryption is necessary.
Hello,
I have Twrp already and a custom rom, i only want to decrypt . Am i right that i only< had to do this:
Swipe on the first screen to enter the menu, tap the top right icon for wiping data, then the bottom right icon, you will see a text box with a warning - enter yes, then tick to fully wipe the SD card.
And later to get root:
Skip past initial steps for speed place the superSU zip on the root of the SD Card and then reboot back to recovery again
Flash SuperSU in recovery (top left option, find your zip, flash it
Reboot system.
Kind regards gandalf
Thank you very much. !!!!:laugh::laugh:
I saved this tutorial, I had left the phone in the login screen.
Hello guys , I need some advice. I have a Mi5s already unlocked with TWRP and custom rom, but would like to get rid of encryption. My doubt is, if I format data and wipe everything, will I be able to move the rom zip in TWRP? And also, will I still have a system installed ? Thanks for your reply
christ-al said:
Hello guys , I need some advice. I have a Mi5s already unlocked with TWRP and custom rom, but would like to get rid of encryption. My doubt is, if I format data and wipe everything, will I be able to move the rom zip in TWRP? And also, will I still have a system installed ? Thanks for your reply
Click to expand...
Click to collapse
Yes ... U keep system...get blank data... Restart the phone... copy the zip/ROM again...or use USB otg

[DISCONTINUED][ROM][SM-T350][UNOFFICIAL]ResurrectionRemix-O-v6.2.1-20181202

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 ?

[TWRP + Root] Galaxy J7 Refine (8.0) (Boost/Sprint)

TWRP has been successfully ported to the Galaxy J7 Refine (SM-J737P) (Oreo 8.0)​ROOT METHOD POSTED BELOW IN POST #2​Giving credit where credit is due:
@Dark98 for compiling the TWRP.img
@☆KØŁØЯΛĐØ☆ providing device files + testing/porting
@topjohnwu for Magisk
DISCLAIMER: This is NOT in Odin flashable .tar format. Due to sporadic updates in security & Oreo, Odin won't be much help here.
This has been tested & confirmed working on device build R16NW.J737PVPU1ARG3. It should work on other versions.
UPDATE: This will work on any Oreo version as well, including the new April 1, 2019 R16NW.J737PVPS3ASC2 update.
The patched_boot.img.tar I've attached will not work if you are on a different version of Oreo. You must provide your own patched_boot.img.tar that coincides with your respective version.
Proof of port is in the screenshot below (I've underlined the device build)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
There is a downside & an upside:
- The downside is that after you flash TWRP & reboot, you will lose root.
- The upside is that TWRP will remain so all you need to do to regain root is flash the Magisk-v18.1.zip in Recovery.
Procedure:
- In order to flash, you need an app that will do so without booting into recovery. View attachment Flashify.apk is the ideal choice for this procedure.
- Flash TWRP in Flashify but do not reboot from the app itself. Power off your device & boot into [TWRP] Recovery manually.
PAY ATTENTION TO THESE NEXT FEW STEPS!!!
- Extract the twrp.img from View attachment J737P_TWRP.zip
- Flash through Flashify, then boot into TWRP for the first time
- Now that you have booted into TWRP the first time, Swipe to allow modifications
- Navigate to Wipe > Format Data > type yes when prompted (this will not delete any files you have in your Internal Storage)
- Once the format is completed, go to TWRP home screen & Reboot > Power Off
DO NOT REBOOT TO SYSTEM
- Once device powers off, reboot back into TWRP (yes you will boot into recovery twice)
If you fail to immediately boot back into TWRP, you will brick & have to start over. The fiirst reboot is to clear out (wipe) the /Data partition to make room for your new recovery. Wiping will not delete any internal storage items. However, it will return a value of 0 for /Data. The second boot is to secure TWRP as your new Recovery, as well as fix the /Data return value.
- Now that you have secured TWRP, go ahead & make a TWRP backup as a safety precaution before you reboot. The backup could be considered "stock" with TWRP as the Recovery. The reason being is that you will lose root after formatting /Data. No worries, you will get it back.
After creating the backup, follow these next steps very carefully!!
You will now flash Magisk-v18.1 to regain root. With the new security measures Samsung put in late 2017, you will need to flash 2 .zip files after to ensure that root sticks.
YOU NEED TO FLASH THESE FILES IN ORDER. DO NOT WIPE CACHE AFTER EACH FLASH. DO NOT REBOOT AFTER EACH FLASH. FLASH EACH PACKAGE ONE AT A TIME. WAIT UNTIL THE 3RD FLASH IS COMPLETE & THEN REBOOT DEVICE. IT WILL TAKE SEVERAL MINUTES SO BE PATIENT.
(Still in TWRP)
- Go to Home & select Instal
- In this order, flash one at a time:
View attachment Magisk-v18.1(18100).zip
View attachment no-verity-opt-encrypt-6.0.zip
View attachment RMM-State_Bypass_Mesa_v2.zip
DO NOT WIPE THE CACHE
Screenshots of proper installation (in order):
- Reboot device normally. If you do not flash the dm-verity & RMM .zip files in order, you will bootloop & have to start over.
- When you get to your home screen, you will receive a notification to update Magisk. Update by either selecting the notification or manually through Magisk Manager.
- Allow Magisk to install the update; do not update through TWRP.
ĐØΠΞ
[ROOT] Galaxy J7 Refine (SM-J737P) (Oreo 8.0)​
FOLLOW THESE DIRECTIONS. I AM NOT RESPONSIBLE IF YOU BRICK YOUR DEVICE.
View attachment 4733553 View attachment 4733552
I have given you a freebie by providing the patched_boot.img.tar, thus saving you a few steps
All files needed are uploaded to my Drive: https://drive.google.com/folderview?id=1-8CGkYef58I-DrkyOshRFniecO_0dBDc
NOTICE: Patched_boot.img.tar is solely for the J737PVPU1ARG3 software version. Any attempt to flash to a different version will result in a bootloop. You must patch + flash your own stock boot.img if you are on a different software version.
YOU MUST PAY ATTENTION TO THE FOLLOWING
- In the Bli5zkrieg.zip you extracted, load up Odin_v13.1 (non-patched)
- Load only the BL/AP/CP files from your stock firmware into Odin
- As soon as the flashing process ends, you must reboot quickly back into Download Mode. You have to be quick. If you allow the device to begin booting up, it makes the rooting process more difficult.
Assuming you followed directions...
- Close Odin_v13.1 & unplug your device while still remaining in Download Mode
- Launch Odin_v13.1 [Patched] & load up the patched_boot.img.tar in the AP slot
- Reconnect device & proceed to flash
- Device will reboot with "Verification Failure" so you must reset (this is part of root) (it does not activate FRP lock)
- When device reboots to Setup Wizard, skip through it. Do not add any accounts (Google or Samsung). Do not consent to giving any device data for whatever purposes (they will ask twice; look carefully)
- On the home screen, unlock Dev Options &allow USB Debugging. OEM should already have been unlocked
- Connect device to your pc & in the ZeeToolz folder you extracted, run CMD.exe
- Input adb devices to ensure proper connection
- Input adb install -r MagiskManager-v7.0.0.apk to install MM to your device
- Open MagiskManager & make sure everything is good to go (see attached screenshot)
- If everything is done properly then you will see a superuser tab in the left side-bar, indicating root access
ĐØΠΞ
Thanks for making / working on this man. Running butter smooth on my SM-j737P (J737PVPU2ARJ2.)
note: I had to use an sdcard to store the proper files to be able to flash in twrp. adb sideload nor mtp would not work while in twrp during the initial install.
I used the files below.
Root Files (patched boot image): https://drive.google.com/file/d/1xan3RfRs4x4As7ONxLtW-WXKh_KvjyXY/view
Unbrick Files (stock J737PVPU2ARJ2) : https://androidfilehost.com/?fid=11410932744536992025
Cheers!
kinehumane said:
Thanks for making / working on this man. Running butter smooth on my SM-j737P (J737PVPU2ARJ2.)
note: I had to use an sdcard to store the proper files to be able to flash in twrp. adb sideload nor mtp would not work while in twrp during the initial install.
I used the files below.
Root Files (patched boot image): https://drive.google.com/file/d/1xan3RfRs4x4As7ONxLtW-WXKh_KvjyXY/view
Unbrick Files (stock J737PVPU2ARJ2) : https://androidfilehost.com/?fid=11410932744536992025
Cheers!
Click to expand...
Click to collapse
No problem man. I didnt think to test sideload or mtp as I always use an SDcard (comes in handy lol). It was a tad bit tedious to get the whole process down due to Oreo. That being said, ensure that you have a backup. Editing any part of the system (ie. Build.prop) will result in failure. I installed the Time Zones update & it failed. As far as MagiskSU goes, I like the Modules but prefer SuperSU root. Will see about incorporating it in the near future
This is likely a silly question, but I downloaded and installed flashify, have put the TWRP.img on the SD Card, but for some reason, flashify won't go further than giving me the option of flashing a recovery... one tap and the app is frozen....
So, is there another app that will flash the image, so as to follow the directions in the OP? Flashify doesn't seem to be happening for me. Can't seem to find one that doesn't do a root-check first, refusing to do the deed if root isn't there yet?
Trying from square 1, to the point that I did a total backup, factory reset, and am starting with a reset phone.
pauljulian said:
This is likely a silly question, but I downloaded and installed flashify, have put the TWRP.img on the SD Card, but for some reason, flashify won't go further than giving me the option of flashing a recovery... one tap and the app is frozen....
So, is there another app that will flash the image, so as to follow the directions in the OP? Flashify doesn't seem to be happening for me.
Click to expand...
Click to collapse
I experienced the sluggish behavior as well. Manually go into Magisk Manager > SuperSU & make sure Flashify has been granted root access. I've noticed Magisk is rather slow when it comes to asking or granting root access on some apps. If you cannot get it to flash with Flashify, I'd suggest going with Root Essentials. Its an all-in-one root toolbox with a flashing mechanism
Root Essentials won't work as a secondary flasher bc it requires a custom recovery to be installed beforehand. Flashify will be your best bet so try all possibilities to get it to work
☆KØŁØЯΛĐØ☆ said:
I experienced the sluggish behavior as well. Manually go into Magisk Manager > SuperSU & make sure Flashify has been granted root access. I've noticed Magisk is rather slow when it comes to asking or granting root access on some apps. If you cannot get it to flash with Flashify, I'd suggest going with Root Essentials. Its an all-in-one root toolbox with a flashing mechanism
Click to expand...
Click to collapse
I'll give it a try... thanks... Just trying to follow the instructions to the letter, and I'm laboring under the assumption that the TWRP image has to be on there before going on to the next steps...
pauljulian said:
I'll give it a try... thanks... Just trying to follow the instructions to the letter, and I'm laboring under the assumption that the TWRP image has to be on there before going on to the next steps...
Click to expand...
Click to collapse
I revised my last comment. TWRP is to be flashed after you have rooted with Magisk. The posts are a little offputting due to the order they are in & I apologize for that lol Root with Magisk first & then you can install TWRP
pauljulian said:
I'll give it a try... thanks... Just trying to follow the instructions to the letter, and I'm laboring under the assumption that the TWRP image has to be on there before going on to the next steps...
Click to expand...
Click to collapse
Hmm... Root Essentials tells me it failed to install the image...
If flashify does work, but is just seriously sluggish, I can live with that if it's just a matter of setting it aside until it loads it up, that's cool... just trying to get the TWRP.img on there per instructions... Selecting the Install Recovery Image craps out... I have a copy of that image on both the emulated and the external SD, just to see if it was that... doesn't seem to work.
My understanding from the instructions is that I can't flash this particular TWRP image with Odin...
Does the patched boot image go on first, or what? I've been around here for a while, and have flashed other phones in the past, but this one is a challenge.
---------- Post added at 07:01 PM ---------- Previous post was at 06:58 PM ----------
☆KØŁØЯΛĐØ☆ said:
I revised my last comment. TWRP is to be flashed after you have rooted with Magisk. The posts are a little offputting due to the order they are in & I apologize for that lol Root with Magisk first & then you can install TWRP
Click to expand...
Click to collapse
OK... that makes more sense... I'll do that first, then go on to the other... Thanks, friend.
pauljulian said:
Hmm... Root Essentials tells me it failed to install the image...
If flashify does work, but is just seriously sluggish, I can live with that if it's just a matter of setting it aside until it loads it up, that's cool... just trying to get the TWRP.img on there per instructions... Selecting the Install Recovery Image craps out... I have a copy of that image on both the emulated and the external SD, just to see if it was that... doesn't seem to work.
My understanding from the instructions is that I can't flash this particular TWRP image with Odin...
Does the patched boot image go on first, or what? I've been around here for a while, and have flashed other phones in the past, but this one is a challenge.
---------- Post added at 07:01 PM ---------- Previous post was at 06:58 PM ----------
OK... that makes more sense... I'll do that first, then go on to the other... Thanks, friend.
Click to expand...
Click to collapse
Flashing with Flashify is under the assumption that you dont have a lot of 3rd party apps installed. If you are logged into your Google or Samsung account(s) & have your data being backed up, it creates a more sluggish environment.
First, follow the rooting guide I posted above. If you do, you should have root access via Magisk with very little apps installed & you arent logged into any Account(s). After you have that, then install Flashify. Manually set root access if need be. Make sure you have all your device security settings disabled, Dev Options, USB Debugging, blah blah blah
We will get you root access & TWRP installed bud
pauljulian said:
My understanding from the instructions is that I can't flash this particular TWRP image with Odin...
Does the patched boot image go on first, or what? I've been around here for a while, and have flashed other phones in the past, but this one is a challenge.
---------- Post added at 07:01 PM ---------- Previous post was at 06:58 PM ----------
OK... that makes more sense... I'll do that first, then go on to the other... Thanks, friend.
Click to expand...
Click to collapse
When you go to get root, you will need your stock firmware (BL/AP/CP files). My directions are pretty straight forward. Unzip the tools, load up Odin (non-patched), flash BL + AP + CP in their respective slots. Make sure that after you flash the stock, you instantly reboot back into Download Mode. Close the current Odin & open the patched Odin. Load the patched_boot.img.tar I provided to the AP slot & flash. It will reboot with a Verification Failure, thus forcing you to format your device. When your device reboots, skip through Setup Wizard, dont link any Google or Samsung accts. On the home screen, use cmd terminal on your pc to install the MagiskManager.apk. Once sideload, you will see root access & more than likely a toast notification asking you to update Magisk.
Rashr (View attachment de.mkrtchyan.recoverytools.apk) works as a good substitute for Flashify. You just need to move the TWRP.img to the root of your sdcard (/emulated/0/sdcard) & flash it through the Recovery from Storage option. Reboot into TWRP &continue following the instructions I've posted
pauljulian said:
Hmm... Root Essentials tells me it failed to install the image...
If flashify does work, but is just seriously sluggish, I can live with that if it's just a matter of setting it aside until it loads it up, that's cool... just trying to get the TWRP.img on there per instructions... Selecting the Install Recovery Image craps out... I have a copy of that image on both the emulated and the external SD, just to see if it was that... doesn't seem to work.
My understanding from the instructions is that I can't flash this particular TWRP image with Odin...
Does the patched boot image go on first, or what? I've been around here for a while, and have flashed other phones in the past, but this one is a challenge.
---------- Post added at 07:01 PM ---------- Previous post was at 06:58 PM ----------
OK... that makes more sense... I'll do that first, then go on to the other... Thanks, friend.
Click to expand...
Click to collapse
OK... one more silly question... the patched.boot file gets loaded into the AP slot in Odin, and not the BL slot? Reason I'm asking is that after flashing that from the AP slot, the device sits at the Boot logo, and sits there...
As I had tried a few other things, and needed to add my account info to grab the Root Essentials, I just said the hell with it, and re-flashed the stock files.. then without anything other than Dev mode enabled, I booted into download mode and flashed the patched.boot tar file in the AP slot, as directed, and here it sits.
I get this happening, you make it to Albuquerque, and I owe you a few beers...
---------- Post added at 08:09 PM ---------- Previous post was at 08:07 PM ----------
pauljulian said:
OK... one more silly question... the patched.boot file gets loaded into the AP slot in Odin, and not the BL slot? Reason I'm asking is that after flashing that from the AP slot, the device sits at the Boot logo, and sits there...
As I had tried a few other things, and needed to add my account info to grab the Root Essentials, I just said the hell with it, and re-flashed the stock files.. then without anything other than Dev mode enabled, I booted into download mode and flashed the patched.boot tar file in the AP slot, as directed, and here it sits.
I get this happening, you make it to Albuquerque, and I owe you a few beers...
Click to expand...
Click to collapse
OK... missed the immediately into download mode... Once more, with feeling.
When all else fails, go back and read the instructions CAREFULLY... <lol>
Reflashing the stock files and starting over...
pauljulian said:
OK... one more silly question... the patched.boot file gets loaded into the AP slot in Odin, and not the BL slot? Reason I'm asking is that after flashing that from the AP slot, the device sits at the Boot logo, and sits there...
As I had tried a few other things, and needed to add my account info to grab the Root Essentials, I just said the hell with it, and re-flashed the stock files.. then without anything other than Dev mode enabled, I booted into download mode and flashed the patched.boot tar file in the AP slot, as directed, and here it sits.
I get this happening, you make it to Albuquerque, and I owe you a few beers...
---------- Post added at 08:09 PM ---------- Previous post was at 08:07 PM ----------
OK... missed the immediately into download mode... Once more, with feeling.
When all else fails, go back and read the instructions CAREFULLY... <lol>
Reflashing the stock files and starting over...
Click to expand...
Click to collapse
Lol The directions are on point. They're solid. You just have to pay attention ?
Here's the old fart with another question....
After flashing the stock files as instructed, I immediately hit the download mode as soon as the screen went black. Flashed the patched boot as instructed, and, as you stated, it would go immediately into recovery due to verification error.
I wiped the cache and hit factory reset, then reboot.
It's now sitting at the boot logo screen, and has been there for more than 1/2 hour.
Honest! I followed your instructions to the letter, and I recall first boot after rooting taking a while to come up into the system on other devices I've had, but I don't recall first boot taking anywhere this long.
I'm stumped.
pauljulian said:
OK... one more silly question... the patched.boot file gets loaded into the AP slot in Odin, and not the BL slot? Reason I'm asking is that after flashing that from the AP slot, the device sits at the Boot logo, and sits there...
As I had tried a few other things, and needed to add my account info to grab the Root Essentials, I just said the hell with it, and re-flashed the stock files.. then without anything other than Dev mode enabled, I booted into download mode and flashed the patched.boot tar file in the AP slot, as directed, and here it sits.
I get this happening, you make it to Albuquerque, and I owe you a few beers...
---------- Post added at 08:09 PM ---------- Previous post was at 08:07 PM ----------
OK... missed the immediately into download mode... Once more, with feeling.
When all else fails, go back and read the instructions CAREFULLY... <lol>
Reflashing the stock files and starting over...
Click to expand...
Click to collapse
pauljulian said:
Here's the old fart with another question....
After following the instructions, yes, the phone went immediately into recovery mode, after flashing the error message you described.
I went ahead and did the factory reset, and told it to reboot... It's been sitting at the boot logo for about 25 minutes.
Should it take this long for first boot, after flashing the patched.boot.img.tar? I loaded the tar into the AP slot, as instructed. After flashing it, and the screen going to black, hit the download mode immediately... I flashed it, as said, at reboot, it went into recovery after a quick error message... I did factory reset, then rebooted normally.
I really have no idea... I'll let it keep sitting, to see if it finally boots, but this seems like a terribly long time that it's' at the bootscreen.
Click to expand...
Click to collapse
You seem to be rebooting into Recovery an awful lot. You shouldn't be booting into recovery mode at all when attempting to root. Recovery mode only needs entered during either process whenever you attempt to flash TWRP. Luckily for you, I dont have sh¡t to do tonight so I can help you until you get it right lol Shoot me an email at [email protected] & we can get started. I dont want to clutter up this feed with a revised how-to guide lol
Other Variants
I tried on my j737p ( rooting worked like a charm ) however your patched boot image had to be substituted in order for my j737 variant to go further than a boot loop.
for twrp the flash of the recovery image went over fine and booted into twrp nicely. however i flashed those 3 files one at a time and all 3 at once both in order each time a few different times to verify. regardless what i do it sends me into a boot loop upon leaving twrp.
do you have any recommendations on what to modify in your procedure for my variant?
my specs are as follows:
Model - SM-J737P
ROM - J737PVPS2ASA1
Android - 8.0
SDK - 26
Kernel - 4.4.13-14521356 [email protected] gcc 4.9.x 20150123
Processsor - armv8l
I have 2 of the same j737p phones so im using one as my test subject before i move each step to my daily j737p.
I am comfortable with beta experimentation within reason.
on a side note - If anyone has my variant and would like the root to work I can send you the patched boot image that I used to get the root to take and let you boot into android successfully.
fsceo said:
I tried on my j737p ( rooting worked like a charm ) however your patched boot image had to be substituted in order for my j737 variant to go further than a boot loop.
for twrp the flash of the recovery image went over fine and booted into twrp nicely. however i flashed those 3 files one at a time and all 3 at once both in order each time a few different times to verify. regardless what i do it sends me into a boot loop upon leaving twrp.
do you have any recommendations on what to modify in your procedure for my variant?
my specs are as follows:
Model - SM-J737P
ROM - J737PVPS2ASA1
Android - 8.0
SDK - 26
Kernel - 4.4.13-14521356 [email protected] gcc 4.9.x 20150123
Processsor - armv8l
I have 2 of the same j737p phones so im using one as my test subject before i move each step to my daily j737p.
I am comfortable with beta experimentation within reason.
on a side note - If anyone has my variant and would like the root to work I can send you the patched boot image that I used to get the root to take and let you boot into android successfully.
Click to expand...
Click to collapse
I have since revised my instructions for root, starting that my guide is very device specific & you will have to tweak instructions in order to accommodate your version.
As far as TWRP goes, did you boot into TWRP twice? Once for the initial install to format the /data partition & the second to secure TWRP along with flashing the files? You need to do it simultaneously & in order otherwise it won't work
It's a happenin' thang!!!!
Many thanks to Killer for all the help! Decent person stayed up with me troubleshooting until 6:30 this morning... It's working!!!!
(now, if I can find the damned SIM card that bounced off my desk into the carpeting, I'll have basically a laptop replacement! (well, for a lot of things, that is... <chuckle>)
pauljulian said:
It's a happenin' thang!!!!
Many thanks to Killer for all the help! Decent person stayed up with me troubleshooting until 6:30 this morning... It's working!!!!
(now, if I can find the damned SIM card that bounced off my desk into the carpeting, I'll have basically a laptop replacement! (well, for a lot of things, that is... <chuckle>)
Click to expand...
Click to collapse
Not a problem buddy. Was fun & if you have any more questions, you have my contact info
fsceo said:
I tried on my j737p ( rooting worked like a charm ) however your patched boot image had to be substituted in order for my j737 variant to go further than a boot loop.
for twrp the flash of the recovery image went over fine and booted into twrp nicely. however i flashed those 3 files one at a time and all 3 at once both in order each time a few different times to verify. regardless what i do it sends me into a boot loop upon leaving twrp.
do you have any recommendations on what to modify in your procedure for my variant?
my specs are as follows:
Model - SM-J737P
ROM - J737PVPS2ASA1
Android - 8.0
SDK - 26
Kernel - 4.4.13-14521356 [email protected] gcc 4.9.x 20150123
Processsor - armv8l
I have 2 of the same j737p phones so im using one as my test subject before i move each step to my daily j737p.
I am comfortable with beta experimentation within reason.
on a side note - If anyone has my variant and would like the root to work I can send you the patched boot image that I used to get the root to take and let you boot into android successfully.
Click to expand...
Click to collapse
Sent you a pm, but having trouble rooting the same variant

[PORT] Unofficial TWRP for G7 Power

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!

Categories

Resources