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
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!
as soon i flashed cyanogenmod 12.1 official from website , my phone rebooted ,i saw the logo and then it automatically turned off . it is happening every time i try to open my phone and i am only able to open fastboot mode by holding power+volume up key
What's your phone's model?
What model and brand is your phone? Did you follow instructions on how to install CM - like, wipe data, dalvik cache, and so on? Have you tried reinstalling stock ROM?
He has yu yunique, the bootloader is also not unlocked and recovery also not opening. He can only use fastboot
How did he install CM 12, if the bootloader is locked?
---------- Post added at 04:09 PM ---------- Previous post was at 04:02 PM ----------
Try this - thetechnotriad com/393/how-to-unbrick-yu-yureka/
(Put dots in spaces - I don't have 10 posts, can't post link's)
There's a guide, on how to unbrick your phone, using fastboot.
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 ?
Hello. I decided to switch to CarbonROM on my Poco f1 thinking that it was based on Android 10 (I really like gesture navigation). After reformatting my device I flashed the firmware, carbonrom and then my microG package. After a little hitch with the wrong firmware it worked. Then, after realising that it didn't have android 10 gesture navigation I thought I'd switch to another ROM. I booted to my recovery (SkyHawk recovery, based on twrp) and went to re format my device. The recovery asked me for a password to decrypt my device (which I found odd as I had never set up a password on CarbonROM) which I cancelled the request and went to reformat my device. I typed in yes and it told me the "Unable to mount storage". Wiping, mounting or any other action yields the same response. I tried rebooting to system and after the CarbonROM boot animation it told me "Encryption unsuccesful" and some text saying I need to reset my phone. I pushed the reset phone button and after a pop up claims to reset it, it boots back to recovery. The main console in the recovery says "cryptkeeper.showFactoryReset() corrupt=false". I have repeated multiple times. All I can access is the recovery (from which I can do nothing) and fastboot.
Is my phone stuffed or can I restore it somehow?
Flash twrp recovery.
Adidas108 said:
Flash twrp recovery.
Click to expand...
Click to collapse
How though? Despite failing earlier, I have now been able to boot up into CarbonROM (so my phone is not bricked ) but I am unable to wipe / reformat my phone from SkyHawk. I know that you can flash a recovery if you have Magisk root, but even flashing Magisk doesn't work from SkyHawk. Can I get TWRP to replace SkyHawk through Fastboot / ADB or anything like that?
Just flash twrp img file using shrp then boot to recovery
---------- Post added at 07:08 AM ---------- Previous post was at 07:05 AM ----------
Use this one
MOD EDIT: Link Removed
---------- Post added at 07:10 AM ---------- Previous post was at 07:08 AM ----------
You can use fastboot
Adidas108 said:
Just flash twrp img file using shrp then boot to recovery
---------- Post added at 07:08 AM ---------- Previous post was at 07:05 AM ----------
Use this one
---------- Post added at 07:10 AM ---------- Previous post was at 07:08 AM ----------
[/COLOR]You can use fastboot
Click to expand...
Click to collapse
Would mind linking me to instructions on how to do with fastboot?
Thank you
hslav said:
Would mind linking me to instructions on how to do with fastboot?
Thank you
Click to expand...
Click to collapse
Nevermind I got it working. Thank you!
hslav said:
Nevermind I got it working. Thank you!
Click to expand...
Click to collapse
Good to hear.
For others check link bellow about adb/fastboot
https://www.youtube.com/redirect?ev...-adb-fastboot-installer-tool-windows-t3999445