Related
Intro: I hate to update my bootloader, so I created this rom and used this method to install the official AT&T kitkat and get root.
This rom is simply a flashable zip made from the official ATT KitKat 4.4 SBF which will install version 140.44.5. It is intended for the ATT moto x with locked bootloaders. The flashable zip does not modify the bootloader or anything besides /system, but the full instructions will wipe your userdata and sdcard.
WARNING: I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE.
Prerequisite:
Moto x with either the .51 (original), .54 (1st OTA) stock rom.
Have fastboot (motorola version for this phone) and PC drivers installed and working
BACKUP ANYTHING YOU DON'T WANT TO LOSE. THESE INSTRUCTIONS WILL WIPE YOUR USERDATA AND SDCARD.
Instructions for ATT moto x with locked bootloader:
root with PwnMyMoto or RockMyMoto (for .51 or .54 respectively, thanks jcase)
install safestrap (thanks Hashcode and Team Win)
download rom to sdcard (motox-kk-140.44.5.ghost_att-full.zip, link below)
download supersu flashable to sdcard (link below, thanks Chainfire)
extract boot.img, NON-HLOS.bin and fsg.mbn from the .zip to the fastboot directory of your PC
enter safestrap recovery (TWRP) and activate the stock-slot
flash rom (motox-kk-140.44.5.ghost_att-full.zip) to the stock-slot using TWRP recovery
immediately flash supersu using TWRP recovery
within TWRP reboot to bootloader
execute fastboot commands (below). Note: The "fastboot erase userdata" command will wipe you data and sdcard.
boot to recovery (which will boot up normally and allow the next step without rebooting)
reinstall safestrap
Fastboot commands:
Code:
fastboot flash boot boot.img
fastboot flash recovery boot.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
Notes:
You should always be able to flash back to stock, as this procedure does not modify your bootloader. (I still use the original bootloader from the original att .51 version.)
There is a new version of SuperSU, but I used version 1.65 (Let me know if the newest version still works.)
I wiped userdata. It may not be necessary, but my observation was that people had "soft reboots when uninstalling apps" and ultimately wiped anyway.
Safestrap works as before, and I have used it to backup and restore to the stock slot.
140.44.5 rom download : http://www.androidfilehost.com/?fid=23212708291682137
supersu: http://forum.xda-developers.com/showthread.php?t=1538053 (download "CWM / TWRP / MobileODIN installable ZIP")
Original source files: http://sbf.droid-developers.org/ghost/list.php (Thanks Skrilax_CZ, Pzyduck and the Firmware Team)
thanks ctrl-freak!
Thanks for posting this. If I have a Moto X with an unlocked bootloader, can I skip any of these steps?
I'm currently running rooted 4.2.2 with 139.12.54.ghost_att.ATT.en.us
RichAP said:
Thanks for posting this. If I have a Moto X with an unlocked bootloader, can I skip any of these steps?
I'm currently running rooted 4.2.2 with 139.12.54.ghost_att.ATT.en.us
Click to expand...
Click to collapse
Having not tried it, the following would be my guess:
I assume you have TWRP or CWM recovery installed in the recovery partition (not safestrap:TWRP). If so, then you can skip steps 1, 2, 11 and 12 and use your regular TWRP or CWM on step 6.
Ideally a rom would be created to do all the flashing in 1 step, but this rom is intended for safestrap's TWRP which is limited and/or some things have not been tested to my knowledge.
Reverting back to 4.2.2
never mind. Found the instructions
I am trying this now following your instructions and I'm going to NOT fastboot flash recovery boot.img or erase userdata and see what happens. (I have TWRP & unlocked bootloader)
I will report back if successful...so far I'm at "Android is upgrading..."
---------- Post added at 07:10 PM ---------- Previous post was at 07:07 PM ----------
I have no wifi or cell signal...guessing the modem is screwed up. Guess i will try flashing it again.
---------- Post added at 07:25 PM ---------- Previous post was at 07:10 PM ----------
Tried flashing the modem again but no go, no wifi, no cell radio, no bluetooth and camera doesn't work either.
Since the camera doesn't work I'm guessing its something else besides the modem?
RichAP said:
I am trying this now following your instructions and I'm going to NOT fastboot flash recovery boot.img or erase userdata and see what happens. (I have TWRP & unlocked bootloader)
I will report back if successful...so far I'm at "Android is upgrading..."
---------- Post added at 07:10 PM ---------- Previous post was at 07:07 PM ----------
I have no wifi or cell signal...guessing the modem is screwed up. Guess i will try flashing it again.
---------- Post added at 07:25 PM ---------- Previous post was at 07:10 PM ----------
Tried flashing the modem again but no go, no wifi, no cell radio, no bluetooth and camera doesn't work either.
Since the camera doesn't work I'm guessing its something else besides the modem?
Click to expand...
Click to collapse
You need to manually put your apns in under mobile networks and after that WiFi should turn on, had the same issue with the sbf file flash
Sent on my Moto X
It won't save an APN and I get see how that would stop WIFI from working. Bluetooth does work and Camera "fails to initialize".
I tried wiping everything out and starting from scratch but get the same results, even downloaded the main 4.4 zip file again (in case I had a bad download)
Do i need a windows machine to use RSD Lite or an i fastboot flash from the stock rbf?
It's my understanding that safestrap isn't working with 4.4, does it work through this method because this does not update the bootloader?
RichAP said:
I am trying this now following your instructions and I'm going to NOT fastboot flash recovery boot.img or erase userdata and see what happens. (I have TWRP & unlocked bootloader)
I will report back if successful...so far I'm at "Android is upgrading..."
---------- Post added at 07:10 PM ---------- Previous post was at 07:07 PM ----------
I have no wifi or cell signal...guessing the modem is screwed up. Guess i will try flashing it again.
---------- Post added at 07:25 PM ---------- Previous post was at 07:10 PM ----------
Tried flashing the modem again but no go, no wifi, no cell radio, no bluetooth and camera doesn't work either.
Since the camera doesn't work I'm guessing its something else besides the modem?
Click to expand...
Click to collapse
You will most likely need to do the kernel (boot.img). It wouldn't surprise me if it fixed the camera.
RichAP said:
It won't save an APN and I get see how that would stop WIFI from working. Bluetooth does work and Camera "fails to initialize".
I tried wiping everything out and starting from scratch but get the same results, even downloaded the main 4.4 zip file again (in case I had a bad download)
Do i need a windows machine to use RSD Lite or an i fastboot flash from the stock rbf?
Click to expand...
Click to collapse
This sounds eerily like the problem I was having. I tried several things, but neither data nor wifi worked, and when I went to settings->status the baseband reported "unavailable".
I made three changes to my procedure and the problem went away:
1) I used the older (known working) SuperSU version 1.65
2) I stopped running wipe (data, cache, dalvik) within safestrap:TWRP
3) I ran "erase userdata"
I am not sure which of these changes fixed the problem, but the procedure finally worked. Let us know if you figure it out.
Thanks, I've been flashing boot boot.img and even tried it from a different download.
---------- Post added at 10:04 PM ---------- Previous post was at 10:00 PM ----------
Ctrl-Freak said:
This sounds eerily like the problem I was having. I tried several things, but neither data nor wifi worked, and when I went to settings->status the baseband reported "unavailable".
I made three changes to my procedure and the problem went away:
1) I used the older (known working) SuperSU version 1.65
2) I stopped running wipe (data, cache, dalvik) within safestrap:TWRP
3) I ran "erase userdata"
I am not sure which of these changes fixed the problem, but the procedure finally worked. Let us know if you figure it out.
Click to expand...
Click to collapse
I do have the baseband version: Unknown
I will try the 3 things you did.
Thx.
Thanks for the help guys, after trying to work it out after a few hours I finally used RSDLite and was able to get ATT 4.4 functional.
Will try to root it in the morning.
Would anyone please make a torrent for the 4.4 firmware? My internet keeps disconnecting :crying:
TIA
Really good directions CTRL-Freak.
Brand new Moto X owner, as of this morning. After being a little confused on what SafeStrap was (at first) and finding the thread for PwnMyMoto (which is titled root/write protection bypass) I am now up and running with no issues. Activated my SIM just a few minutes ago with AT&T and I am happy!
SafeStrap - http://rootzwiki.com/topic/104161-recovery-locked-safestrap-recovery-v365-2013-11-13/
PwnMyMoto - http://forum.xda-developers.com/showthread.php?t=2444957
Is it possible to upgrade from you att .43 leak without a full wipe?
So I suppose if I am on the AT&T version and took the 4.4 OTA, then I am SOL? Would live to get root.
Sent from my XT1058 using Tapatalk
Cubfan99 said:
So I suppose if I am on the AT&T version and took the 4.4 OTA, then I am SOL? Would live to get root.
Sent from my XT1058 using Tapatalk
Click to expand...
Click to collapse
You can RSD back to 4.2
Sent from my N7 Razor
I'm currently using this fastboot-ghost_retbr-user-4.2.2-13.9.0Q2.X-116-LCX-35-36-release-keys-cid12-Brazil-BR.tar.gz I install this?
Infekxion said:
You can RSD back to 4.2
Click to expand...
Click to collapse
Are there instructions for that somewhere?
-- Sent from my Moto X on Tapatalk Pro
I currently have this problem that when I flash a version of TWRP(have tried both 3.0.2 and 3.1.0) I cannot reboot my current OS(have tried both stock 376 and 378). Simply pressing the power button will result in recovery mode. Stranger still, when i flashed a ROM as a zip out of twrp, it actually booted up, but then I could no longer return to recovery mode, despite fiddling around mith multiple button combinations.
Seems as though i am missing something obvious, as i have not found a thread regarding a similar issue. Anybody have a clue as to what it might be?
macjagger said:
I currently have this problem that when I flash a version of TWRP(have tried both 3.0.2 and 3.1.0) I cannot reboot my current OS(have tried both stock 376 and 378). Simply pressing the power button will result in recovery mode. Stranger still, when i flashed a ROM as a zip out of twrp, it actually booted up, but then I could no longer return to recovery mode, despite fiddling around mith multiple button combinations.
Seems as though i am missing something obvious, as i have not found a thread regarding a similar issue. Anybody have a clue as to what it might be?
Click to expand...
Click to collapse
it seems like u dint have an proper boot.img
try flashing ftf
I've been flashing the stock firmware(s) as ftf using flashtool (newest version) and xperifirm, that's why I think it's so odd. Before flashing TWRP, the stock ROM boots up and everything works as it should. After flashing TWRP, it only boots up into recovery.
macjagger said:
I've been flashing the stock firmware(s) as ftf using flashtool (newest version) and xperifirm, that's why I think it's so odd. Before flashing TWRP, the stock ROM boots up and everything works as it should. After flashing TWRP, it only boots up into recovery.
Click to expand...
Click to collapse
hmmm do u flash an kernel that has dm variety fix
---------- Post added at 08:32 AM ---------- Previous post was at 08:32 AM ----------
also what firmware ur are on
altvolt74 said:
hmmm do u flash an kernel that has dm variety fix
---------- Post added at 08:32 AM ---------- Previous post was at 08:32 AM ----------
also what firmware ur are on
Click to expand...
Click to collapse
Yes, I've been flashing kernels with that fix.
I managed to get stock 378 DE running using only flashtool with jutphaas' boot.img of this thread: https://forum.xda-developers.com/z5-compact/general/32-3-0-378-pushed-xperifirm-t3559906/page4
I've also had 376 DE and 376 AU firmware working with this ROM: https://forum.xda-developers.com/z5-compact/development/rom-stock-z5c32-3-0-376r2dau-t3570248
In this case I was able to flash the ROM .zip out of TWRP and boot into the ROM. Afterwards I could no longer enter TWRP though.
In both cases, after (re)flashing TWRP, I'd get stuck in recovery.
macjagger said:
Yes, I've been flashing kernels with that fix.
I managed to get stock 378 DE running using only flashtool with jutphaas' boot.img of this thread: https://forum.xda-developers.com/z5-compact/general/32-3-0-378-pushed-xperifirm-t3559906/page4
I've also had 376 DE and 376 AU firmware working with this ROM: https://forum.xda-developers.com/z5-compact/development/rom-stock-z5c32-3-0-376r2dau-t3570248
In this case I was able to flash the ROM .zip out of TWRP and boot into the ROM. Afterwards I could no longer enter TWRP though.
In both cases, after (re)flashing TWRP, I'd get stuck in recovery.
Click to expand...
Click to collapse
try flash e5823 lates nougat e5823_32.3.A.0.376_R2R_AU instead of (e5803) firmware
also to enter flash the rom using kernel partition
off phone . ...hold vol down and power release power when see sony keep holding volume down all the way till recovery
format system
flash zip
i will update intrustions since theres people having issues while flashing an rom using e5823 on e5803 or probably ur flashing it wrong using the recovery that is integrated to the boot.img
---------- Post added at 05:01 AM ---------- Previous post was at 05:00 AM ----------
also sorry for late reply been cooking xperia xz rom to our z5 compact also finish is uploading it now
I'll give it a try in a couple of days. Need my phone as a daily driver currently. Appreciate your help
macjagger said:
In both cases, after (re)flashing TWRP, I'd get stuck in recovery.
Click to expand...
Click to collapse
To me it seems like you are just flashing twrp to the wrong partition.
How do you flash it?
You have to flash it with command:
Fastboot flash recovery "twrp.img"
macjagger said:
I currently have this problem that when I flash a version of TWRP(have tried both 3.0.2 and 3.1.0) I cannot reboot my current OS(have tried both stock 376 and 378). Simply pressing the power button will result in recovery mode. Stranger still, when i flashed a ROM as a zip out of twrp, it actually booted up, but then I could no longer return to recovery mode, despite fiddling around mith multiple button combinations.
Seems as though i am missing something obvious, as i have not found a thread regarding a similar issue. Anybody have a clue as to what it might be?
Click to expand...
Click to collapse
oh hai
just wanted to link you in on this:
https://forum.xda-developers.com/z5...m-fix-twrp-t3560135/post71433741#post71433741
Hey fellas, I'm back. Excuse my absence, currently busy with exams.
It seems as though @Gewiz was correct. I was trying to flash twrp over "Flashtool>fastboot mode>select kernel to flash", which probably targets the wrong partition. Instead I now used "Flashtool>fastboot mode>reboot into fastboot mode via fastboot" and flashed it using the standard cmd window line ("fastboot flash recovery twrp.img") and it seems to have worked.
Thanks to everyone on this thread!
macjagger said:
Hey fellas, I'm back. Excuse my absence, currently busy with exams.
It seems as though @Gewiz was correct. I was trying to flash twrp over "Flashtool>fastboot mode>select kernel to flash", which probably targets the wrong partition. Instead I now used "Flashtool>fastboot mode>reboot into fastboot mode via fastboot" and flashed it using the standard cmd window line ("fastboot flash recovery twrp.img") and it seems to have worked.
Thanks to everyone on this thread!
Click to expand...
Click to collapse
Have you tried to do a restore yet?
Just wanted to ask so I can isolate twrp with rootkernel
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 ?
i have tried to install twrp. I have do the all what the intructions says. I get into twrp but when i boot my device again and tried to go twrp it goes to xiaomi recovery. My twrp gets overwritten by stock recovery on redmi 5. What i can do?
Which command line are you using?
Aleksiton said:
i have tried to install twrp. I have do the all what the intructions says. I get into twrp but when i boot my device again and tried to go twrp it goes to xiaomi recovery. My twrp gets overwritten by stock recovery on redmi 5. What i can do?
Click to expand...
Click to collapse
Code:
fastboot flash recovery *twrp image name*
should allow you to write twrp to your flash partition.
If you're using
Code:
fastboot boot *twrp image name*
it just loads twrp for that instance.
On a sidenote, what are your plans with TWRP? MIUI has an issue that twrp asks for password when starting. If you want to root, you're better off loading it for single instance, installing magisk.
himodyuti said:
Code:
fastboot flash recovery *twrp image name*
should allow you to write twrp to your flash partition.
If you're using
Code:
fastboot boot *twrp image name*
it just loads twrp for that instance.
On a sidenote, what are your plans with TWRP? MIUI has an issue that twrp asks for password when starting. If you want to root, you're better off loading it for single instance, installing magisk.
Click to expand...
Click to collapse
I use "fastboot flash recovery twrp image name". I planning to instal pixel experience rom on my phone. I have read that your phone doesn't need to root. am i righ?
himodyuti said:
Code:
fastboot flash recovery *twrp image name*
should allow you to write twrp to your flash partition.
If you're using
Code:
fastboot boot *twrp image name*
it just loads twrp for that instance.
On a sidenote, what are your plans with TWRP? MIUI has an issue that twrp asks for password when starting. If you want to root, you're better off loading it for single instance, installing magisk.
Click to expand...
Click to collapse
I am using xiaomi beta developer rom. Is that a problem?
anti rollback security ?..
if You're using MIUI 10
YOU Won't be able to flash any custom recovery..you'll have to fastboot boot recovery.img everytime you want to flash something ?
risunygma said:
anti rollback security ..
if You're using MIUI 10
YOU Won't be able to flash any custom recovery..you'll have to fastboot boot recovery.img everytime you want to flash something ?
Click to expand...
Click to collapse
I have watch some videos and they said that its possible to install custom recovery permanently even if the phone has anti rollback. But if i cant install recovery can i still install custom rom and root the phone?
PE Installation
Aleksiton said:
I am using xiaomi beta developer rom. Is that a problem?
Click to expand...
Click to collapse
I don't think developer rom should be a problem.
Try this:
1. Copy PE Rom on your SD Card.
2. Fire up the stock recovery->wipe data.
3. Then when rebooting, keep the Vol Down key pressed. This will take you directly to Bootloader without invoking MIUI to encrypt the internal storage.
4. Connect to your pc, boot to TWRP with
Code:
fastboot boot *twrp image name*
You will see that it no longer asks for password.
5. In TWRP, go to Wipe Data->Advanced Wipe->Wipe everything except SD Card. (I am assuming you want a clean flash)
6. Back to main twrp screen->Install->Select Storage->SD Card->ROM File. It will take a while to install.
7. Reboot and you're good to go.
Please note that you still have the stock recovery installed in your phone. You can try to replace it with TWRP now as there won't be MIUI to roll it back to stock recovery. Hope it helps.
himodyuti said:
I don't think developer rom should be a problem.
Try this:
1. Copy PE Rom on your SD Card.
2. Fire up the stock recovery->wipe data.
3. Then when rebooting, keep the Vol Down key pressed. This will take you directly to Bootloader without invoking MIUI to encrypt the internal storage.
4. Connect to your pc, boot to TWRP with
You will see that it no longer asks for password.
5. In TWRP, go to Wipe Data->Advanced Wipe->Wipe everything except SD Card. (I am assuming you want a clean flash)
6. Back to main twrp screen->Install->Select Storage->SD Card->ROM File. It will take a while to install.
7. Reboot and you're good to go.
Please note that you still have the stock recovery installed in your phone. You can try to replace it with TWRP now as there won't be MIUI to roll it back to stock recovery. Hope it helps.
Click to expand...
Click to collapse
I did something and now i have twrp my main recovery but every time i wan't wipe it says unable to mount data and some others errors. I tried to flash magisk it worked and my phone is now rooted. I can format data and boot back into miui. But how i can fix the problem? Is my twrp broken? I don't think that miui stock recovery is deleted i think its only overwritten by twrp. I flashed lazyflasher and then it was my main recovery.
If you want to use miui then miui eu roms are recommended. They work flawless with custom twrp's.
Aleksiton said:
I did something and now i have twrp my main recovery but every time i wan't wipe it says unable to mount data and some others errors. I tried to flash magisk it worked and my phone is now rooted. I can format data and boot back into miui. But how i can fix the problem? Is my twrp broken? I don't think that miui stock recovery is deleted i think its only overwritten by twrp. I flashed lazyflasher and then it was my main recovery.
Click to expand...
Click to collapse
No twrp isn't broken. The recovery is responsible for wiping data. Since stock recovery isn't there, the phone boots into twrp. Try factory reset inside twrp->Wipe or advanced wipe->select everything except sd card and format. If that fails, I have uploaded a copy of my recovery to the below link. Flash that and follow the process I have given above. If the phone starts booting into miui, it will encrypt the internal storage again and you have to start over.
https://drive.google.com/file/d/1u3v8n6YMbXFrU0Zn6t8IMK18KiuQBUhz/view?usp=drivesdk
---------- Post added at 06:03 PM ---------- Previous post was at 06:01 PM ----------
xDoge said:
If you want to use miui then miui eu roms are recommended. They work flawless with custom twrp's.
Click to expand...
Click to collapse
Can you unlock the internal storage from twrp there? I am seeing all those tutorials saying that you should enter you lock screen password in twrp to unlock your internal storage but it doesn't seem to work.
---------- Post added at 06:06 PM ---------- Previous post was at 06:03 PM ----------
Aleksiton said:
I did something and now i have twrp my main recovery but every time i wan't wipe it says unable to mount data and some others errors. I tried to flash magisk it worked and my phone is now rooted. I can format data and boot back into miui. But how i can fix the problem? Is my twrp broken? I don't think that miui stock recovery is deleted i think its only overwritten by twrp. I flashed lazyflasher and then it was my main recovery.
Click to expand...
Click to collapse
Another thing, before you wipe your internal storage log out of your google and mi accounts. Else, PE Rom might throw an error saying there's something wrong with your phone. As far as I know it doesn't affect the functionality, but why take the risk.
himodyuti said:
No twrp isn't broken. The recovery is responsible for wiping data. Since stock recovery isn't there, the phone boots into twrp. Try factory reset inside twrp->Wipe or advanced wipe->select everything except sd card and format. If that fails, I have uploaded a copy of my recovery to the below link. Flash that and follow the process I have given above. If the phone starts booting into miui, it will encrypt the internal storage again and you have to start over.
https://drive.google.com/file/d/1u3v8n6YMbXFrU0Zn6t8IMK18KiuQBUhz/view?usp=drivesdk
---------- Post added at 06:03 PM ---------- Previous post was at 06:01 PM ----------
Can you unlock the internal storage from twrp there? I am seeing all those tutorials saying that you should enter you lock screen password in twrp to unlock your internal storage but it doesn't seem to work.
---------- Post added at 06:06 PM ---------- Previous post was at 06:03 PM ----------
Another thing, before you wipe your internal storage log out of your google and mi accounts. Else, PE Rom might throw an error saying there's something wrong with your phone. As far as I know it doesn't affect the functionality, but why take the risk.
Click to expand...
Click to collapse
Is possible to get hard brick if i flash your recovery wrong or my twrp cant wipe data or my twrp can't flash the rocevery right? My phone is working good right now so i dont want take big risk.
himodyuti said:
Can you unlock the internal storage from twrp there? I am seeing all those tutorials saying that you should enter you lock screen password in twrp to unlock your internal storage but it doesn't seem to work.
Click to expand...
Click to collapse
OK which twrp are you guys using/talking about?
Aleksiton said:
Is possible to get hard brick if i flash your recovery wrong or my twrp cant wipe data or my twrp can't flash the rocevery right? My phone is working good right now so i dont want take big risk.
Click to expand...
Click to collapse
AFAIK, you can't flash another ROMs twrp if it was built with proper assert.
And I haven't heard of twrp hard bricking the phone. You can always flash stock ROM via fast boot but say goodbye to data & internal storage.
So always keep backup.
xDoge said:
OK which twrp are you guys using/talking about?
Click to expand...
Click to collapse
What do you mean? Tif you mean the version its twrp 3.3.0-rosy.
xDoge said:
OK which twrp are you guys using/talking about?
AFAIK, you can't flash another ROMs twrp if it was built with proper assert.
And I haven't heard of twrp hard bricking the phone. You can always flash stock ROM via fast boot but say goodbye to data & internal storage.
So always keep backup.
Click to expand...
Click to collapse
What do you mean "AFAIK, you can't flash another ROMs twrp if it was built with proper assert"?
himodyuti said:
No twrp isn't broken. The recovery is responsible for wiping data. Since stock recovery isn't there, the phone boots into twrp. Try factory reset inside twrp->Wipe or advanced wipe->select everything except sd card and format. If that fails, I have uploaded a copy of my recovery to the below link. Flash that and follow the process I have given above. If the phone starts booting into miui, it will encrypt the internal storage again and you have to start over.
https://drive.google.com/file/d/1u3v8n6YMbXFrU0Zn6t8IMK18KiuQBUhz/view?usp=drivesdk
---------- Post added at 06:03 PM ---------- Previous post was at 06:01 PM ----------
Can you unlock the internal storage from twrp there? I am seeing all those tutorials saying that you should enter you lock screen password in twrp to unlock your internal storage but it doesn't seem to work.
---------- Post added at 06:06 PM ---------- Previous post was at 06:03 PM ----------
Another thing, before you wipe your internal storage log out of your google and mi accounts. Else, PE Rom might throw an error saying there's something wrong with your phone. As far as I know it doesn't affect the functionality, but why take the risk.
Click to expand...
Click to collapse
I have tried to unlock the internal storage but i can't
himodyuti said:
No twrp isn't broken. The recovery is responsible for wiping data. Since stock recovery isn't there, the phone boots into twrp. Try factory reset inside twrp->Wipe or advanced wipe->select everything except sd card and format. If that fails, I have uploaded a copy of my recovery to the below link. Flash that and follow the process I have given above. If the phone starts booting into miui, it will encrypt the internal storage again and you have to start over.
https://drive.google.com/file/d/1u3v8n6YMbXFrU0Zn6t8IMK18KiuQBUhz/view?usp=drivesdk
---------- Post added at 06:03 PM ---------- Previous post was at 06:01 PM ----------
Can you unlock the internal storage from twrp there? I am seeing all those tutorials saying that you should enter you lock screen password in twrp to unlock your internal storage but it doesn't seem to work.
---------- Post added at 06:06 PM ---------- Previous post was at 06:03 PM ----------
Another thing, before you wipe your internal storage log out of your google and mi accounts. Else, PE Rom might throw an error saying there's something wrong with your phone. As far as I know it doesn't affect the functionality, but why take the risk.
Click to expand...
Click to collapse
Can you give me full instructions how to fix my 0mb and unable to mount data (invalid argument) problem and how do i install custom rom (PE rom)
himodyuti said:
No twrp isn't broken. The recovery is responsible for wiping data. Since stock recovery isn't there, the phone boots into twrp. Try factory reset inside twrp->Wipe or advanced wipe->select everything except sd card and format. If that fails, I have uploaded a copy of my recovery to the below link. Flash that and follow the process I have given above. If the phone starts booting into miui, it will encrypt the internal storage again and you have to start over.
https://drive.google.com/file/d/1u3v8n6YMbXFrU0Zn6t8IMK18KiuQBUhz/view?usp=drivesdk
---------- Post added at 06:03 PM ---------- Previous post was at 06:01 PM ----------
Can you unlock the internal storage from twrp there? I am seeing all those tutorials saying that you should enter you lock screen password in twrp to unlock your internal storage but it doesn't seem to work.
---------- Post added at 06:06 PM ---------- Previous post was at 06:03 PM ----------
Another thing, before you wipe your internal storage log out of your google and mi accounts. Else, PE Rom might throw an error saying there's something wrong with your phone. As far as I know it doesn't affect the functionality, but why take the risk.
Click to expand...
Click to collapse
Do i flash your recovery as my new recovery? And is it safe to flash your recovery?
Aleksiton said:
Do i flash your recovery as my new recovery? And is it safe to flash your recovery?
Click to expand...
Click to collapse
Yes I use Redmi 5 as well. This is just a backup of my stock recovery. No issues.
---------- Post added at 03:48 PM ---------- Previous post was at 03:46 PM ----------
Aleksiton said:
Can you give me full instructions how to fix my 0mb and unable to mount data (invalid argument) problem and how do i install custom rom (PE rom)
Click to expand...
Click to collapse
Sorry I haven't been able to solve the internal storage
mounting issue either. I just wipe my data using stock recovery, go straight into bootloader before it can boot up, boot twrp from there and install whatever rom i need to install.
himodyuti said:
Yes I use Redmi 5 as well. This is just a backup of my stock recovery. No issues.
---------- Post added at 03:48 PM ---------- Previous post was at 03:46 PM ----------
Sorry I haven't been able to solve the internal storage
mounting issue either. I just wipe my data using stock recovery, go straight into bootloader before it can boot up, boot twrp from there and install whatever rom i need to install.
Click to expand...
Click to collapse
I have heard that people format data and then they restart the phone to recovery and wipe all data. Is that right? And if i flash pe rom do i need to flash anything else?
Aleksiton said:
I have heard that people format data and then they restart the phone to recovery and wipe all data. Is that right? And if i flash pe rom do i need to flash anything else?
Click to expand...
Click to collapse
Formatting data and wiping data from recovery is the same thing. I'd suggest that you wipe data from recovery. That way it won't automatically reboot and accidentally go into android again. You can keep the vol down button pressed immediately after hitting reboot so bootloader starts right away. Remember to remove your mi account and google account before doing any data wipe.
PE comes preloaded with all the gapps. I didn't have to flash anything else with it.
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!