Related
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!
I've managed to flash (using the guide here: https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814) the incorrect firmware to my phone. I used the 8.0.0.140 firmware for the BKL-L09 to my BLA-L09. Now, it reports as having no IMEI number and I have no SIM car recognised.
I've tried using the guide above, but it reports as BKL not supported.
How screwed am I? Would something like FunkyHuawei Unbrick Flash Tool work (although the download keeps being reported as having a virus). Has anyone got any ideas?
Thanks.
nea102 said:
I've managed to flash (using the guide here: https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814) the incorrect firmware to my phone. I used the 8.0.0.140 firmware for the BKL-L09 to my BLA-L09. Now, it reports as having no IMEI number and I have no SIM car recognised.
I've tried using the guide above, but it reports as BKL not supported.
How screwed am I? Would something like FunkyHuawei Unbrick Flash Tool work (although the download keeps being reported as having a virus). Has anyone got any ideas?
Thanks.
Click to expand...
Click to collapse
See if you can flash TWRP: https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-twrp-3-2-1-0-t3769904
If it works, you can re-flash BLA using: https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
If you don't get FBE working you should be able to just Wipe -> Format Data -> 'yes' and use Reboot -> Recovery. This will remove encryption.
After this transfer the HuRUpdater script and firmware zips to internal sdcard.
Be sure to backup internal sdcard before Format Data as this will wipe it.
I'm amazed your phone even boots
ante0 said:
See if you can flash TWRP: https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-twrp-3-2-1-0-t3769904
If it works, you can re-flash BLA using: https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
If you don't get FBE working you should be able to just Wipe -> Format Data -> 'yes' and use Reboot -> Recovery. This will remove encryption.
After this transfer the HuRUpdater script and firmware zips to internal sdcard.
Be sure to backup internal sdcard before Format Data as this will wipe it.
I'm amazed your phone even boots
Click to expand...
Click to collapse
You and me both!
I've got TWRP on, but so far it's just showing me the TWRP splash screen and not actually loading into it.
nea102 said:
You and me both!
I've got TWRP on, but so far it's just showing me the TWRP splash screen and not actually loading into it.
Click to expand...
Click to collapse
Boot looping with TWRP. Only shows the splash page for a bit then reboots to the eRecovery.
Evening my brother,
Please relax and don't panic, as you are not alone and by the look of things you won't be the last one. I also did the same thing by rebranding my mate 10 pro to porsche design and flashed the porsche firmware to my 10 pro. After all that my device booted and it was rebranded to porsche design, but without imei, not detecting sim and all I had to do was to rebrand it back to BLA-L29 and flashed the BLA-L29 firmware. All is back to normal working order. I just hope your bootloader is still unlocked.
The bootloader is unlocked, I just can't get into TWRP at the moment.
You don't need TWRP and all you need is to follow the guide in this forum about rebranding. You also don't need FH paying method. Just follow that guide and it is straightforward.
---------- Post added at 06:08 AM ---------- Previous post was at 06:03 AM ----------
https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
Hayeni said:
You don't need TWRP and all you need is to follow the guide in this forum about rebranding. You also don't need FH paying method. Just follow that guide and it is straightforward.
---------- Post added at 06:08 AM ---------- Previous post was at 06:03 AM ----------
https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
Click to expand...
Click to collapse
I've tried following that method but I get an error message saying "No support BKL".
Ok I see. Please download the firmware package of the exact original model of your mate 10 and try and flash it using the same guide, but of course without rebranding and see if it will take it.
Hayeni said:
Ok I see. Please download the firmware package of the exact original model of your mate 10 and try and flash it using the same guide, but of course without rebranding and see if it will take it.
Click to expand...
Click to collapse
Tried that as well. Still says "No support device BKL"
Ok, I'm in to TWRP. However, it will not let me mount the phone as storage. Nor does it have an SD Card slot that I can put the files on to. Ideas?
nea102 said:
Ok, I'm in to TWRP. However, it will not let me mount the phone as storage. Nor does it have an SD Card slot that I can put the files on to. Ideas?
Click to expand...
Click to collapse
Can your browse to /data using Advanced - File Manager?
And does ADB work?
ADB working - I am currently pushing the files to the phone.
ante0 said:
Can your browse to /data using Advanced - File Manager?
And does ADB work?
Click to expand...
Click to collapse
Ok, so I got all the files on there and tried flashing using HuRUpdater but it errors out. Log here: https://pastebin.com/gXh0sesh
nea102 said:
Ok, so I got all the files on there and tried flashing using HuRUpdater but it errors out. Log here: https://pastebin.com/gXh0sesh
Click to expand...
Click to collapse
Open TWRP terminal OR adb shell:
mount -r /vendor
mount -o rw,remount /vendor
See if it want to flash now.
Which TWRP are you using BTW? (post link to thread)
I've tried a few versions - one starts the install but reboots randomly and then others that bomb out straight away.
ante0 said:
Open TWRP terminal OR adb shell:
mount -r /vendor
mount -o rw,remount /vendor
See if it want to flash now.
Which TWRP are you using BTW? (post link to thread)
Click to expand...
Click to collapse
Still bombs out using this one: https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-twrp-3-2-1-0-t3769904
I've tried 0.4 (reboots), 0.5 and 0.6.
I've also tried this one (random reboots) https://forum.xda-developers.com/mate-10/development/recovery-twrp-3-2-1-0-touch-recovery-t3752399
And I've tried this one: https://forum.xda-developers.com/honor-9/development/oreo-t3754483 (same - bombs out)
Is there a way to recover this installing the Huawei zips through ADB or something?
ante0 said:
See if you can flash TWRP: https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-twrp-3-2-1-0-t3769904
If it works, you can re-flash BLA using: https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
If you don't get FBE working you should be able to just Wipe -> Format Data -> 'yes' and use Reboot -> Recovery. This will remove encryption.
After this transfer the HuRUpdater script and firmware zips to internal sdcard.
Be sure to backup internal sdcard before Format Data as this will wipe it.
I'm amazed your phone even boots
Click to expand...
Click to collapse
thanks alot for the link of the tool.
i successfully rebranded my mate 10 pro back to BLA from RNE.
nea102 said:
Is there a way to recover this installing the Huawei zips through ADB or something?
Click to expand...
Click to collapse
Actually, have you tried TWRP for V10?
https://forum.xda-developers.com/honor-view-10/development/recovery-twrp-3-2-1-0-t3769917
Else you can try NoCheck, it will let you flash firmware using stock recovery (patched to not do verification).
https://forum.xda-developers.com/ho.../recovery-bkl-nocheck-recovery-flash-t3778085
(It has only been tested on L04, but I guess it's worth a shot)
You'd just need to get Magisk, which should be easy as you'd only need to patch ramdisk or if you already have it installed.
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.
I have a samsung a30 with an unlocked bootloader and twrp installed, but no OS/ROM at the moment. I'm not able to install any rom either cus the phone used to have android 10 when i unlocked the bootloader and now the system partition is mounted as read-only and i'm not able to uncheck that box in twrp. so b asically, I have a phone without any OS, unrooted, with twrp and an unlocked bootloader. i just want to mount system partition as read/write. Or I'd like to restore my phone to factory condition but i'm not able to flash any roms at all. any help please??
@idli_ninja
If no OS/ROM is present, then logically enough also no /system partition is present
jwoegerbauer said:
@idli_ninja
If no OS/ROM is present, then logically enough also no /system partition is present
Click to expand...
Click to collapse
yeah, i guess so. the logs show "Unable to find partition for path '/system' in red, in twrp. any idea how i can fix this?
idli_ninja said:
yeah, i guess so. the logs show "Unable to find partition for path '/system' in red, in twrp. any idea how i can fix this?
Click to expand...
Click to collapse
Flash a ROM via TWRP.
jwoegerbauer said:
Flash a ROM via TWRP.
Click to expand...
Click to collapse
Flashing is useless. in the mount tab in twrp, system is set to be read only. flashing any rom and rebooting makes my phone get stuck in a bootloop. and for flashing stock rom with odin, it fails and the phone showssw rev check fail (bootloader) device:5 binary:2. so basically i'm stuck without an OS
idli_ninja said:
Flashing is useless. in the mount tab in twrp system is set to be read only. flashing any rom and rebooting makes my phone get stuck in a bootloop. and for flashing stock rom with odin, it fails and the phone showssw rev check fail (bootloader) device:5 binary:2. so basically i'm stuck without an OS
Click to expand...
Click to collapse
Your Samsung has a microSD slot, hence you should be able to flash a Custom ROM.
jwoegerbauer said:
Your Samsung has a microSD slot, hence you should be able to flash a Custom ROM.
Click to expand...
Click to collapse
I've tried, flashing another rom doesn't change anything cus the system partition is set to be read-only. apparently, it's s feature of android 10 to set the system partition to read only when the bootloader is unlocked and i've heard the problem can be solved using magisk and adb and stuff but i'm not sure how.
0
Try using Odin to flash the stock firmware while in download mode