I currently have this problem that when I flash a version of TWRP(have tried both 3.0.2 and 3.1.0) I cannot reboot my current OS(have tried both stock 376 and 378). Simply pressing the power button will result in recovery mode. Stranger still, when i flashed a ROM as a zip out of twrp, it actually booted up, but then I could no longer return to recovery mode, despite fiddling around mith multiple button combinations.
Seems as though i am missing something obvious, as i have not found a thread regarding a similar issue. Anybody have a clue as to what it might be?
macjagger said:
I currently have this problem that when I flash a version of TWRP(have tried both 3.0.2 and 3.1.0) I cannot reboot my current OS(have tried both stock 376 and 378). Simply pressing the power button will result in recovery mode. Stranger still, when i flashed a ROM as a zip out of twrp, it actually booted up, but then I could no longer return to recovery mode, despite fiddling around mith multiple button combinations.
Seems as though i am missing something obvious, as i have not found a thread regarding a similar issue. Anybody have a clue as to what it might be?
Click to expand...
Click to collapse
it seems like u dint have an proper boot.img
try flashing ftf
I've been flashing the stock firmware(s) as ftf using flashtool (newest version) and xperifirm, that's why I think it's so odd. Before flashing TWRP, the stock ROM boots up and everything works as it should. After flashing TWRP, it only boots up into recovery.
macjagger said:
I've been flashing the stock firmware(s) as ftf using flashtool (newest version) and xperifirm, that's why I think it's so odd. Before flashing TWRP, the stock ROM boots up and everything works as it should. After flashing TWRP, it only boots up into recovery.
Click to expand...
Click to collapse
hmmm do u flash an kernel that has dm variety fix
---------- Post added at 08:32 AM ---------- Previous post was at 08:32 AM ----------
also what firmware ur are on
altvolt74 said:
hmmm do u flash an kernel that has dm variety fix
---------- Post added at 08:32 AM ---------- Previous post was at 08:32 AM ----------
also what firmware ur are on
Click to expand...
Click to collapse
Yes, I've been flashing kernels with that fix.
I managed to get stock 378 DE running using only flashtool with jutphaas' boot.img of this thread: https://forum.xda-developers.com/z5-compact/general/32-3-0-378-pushed-xperifirm-t3559906/page4
I've also had 376 DE and 376 AU firmware working with this ROM: https://forum.xda-developers.com/z5-compact/development/rom-stock-z5c32-3-0-376r2dau-t3570248
In this case I was able to flash the ROM .zip out of TWRP and boot into the ROM. Afterwards I could no longer enter TWRP though.
In both cases, after (re)flashing TWRP, I'd get stuck in recovery.
macjagger said:
Yes, I've been flashing kernels with that fix.
I managed to get stock 378 DE running using only flashtool with jutphaas' boot.img of this thread: https://forum.xda-developers.com/z5-compact/general/32-3-0-378-pushed-xperifirm-t3559906/page4
I've also had 376 DE and 376 AU firmware working with this ROM: https://forum.xda-developers.com/z5-compact/development/rom-stock-z5c32-3-0-376r2dau-t3570248
In this case I was able to flash the ROM .zip out of TWRP and boot into the ROM. Afterwards I could no longer enter TWRP though.
In both cases, after (re)flashing TWRP, I'd get stuck in recovery.
Click to expand...
Click to collapse
try flash e5823 lates nougat e5823_32.3.A.0.376_R2R_AU instead of (e5803) firmware
also to enter flash the rom using kernel partition
off phone . ...hold vol down and power release power when see sony keep holding volume down all the way till recovery
format system
flash zip
i will update intrustions since theres people having issues while flashing an rom using e5823 on e5803 or probably ur flashing it wrong using the recovery that is integrated to the boot.img
---------- Post added at 05:01 AM ---------- Previous post was at 05:00 AM ----------
also sorry for late reply been cooking xperia xz rom to our z5 compact also finish is uploading it now
I'll give it a try in a couple of days. Need my phone as a daily driver currently. Appreciate your help
macjagger said:
In both cases, after (re)flashing TWRP, I'd get stuck in recovery.
Click to expand...
Click to collapse
To me it seems like you are just flashing twrp to the wrong partition.
How do you flash it?
You have to flash it with command:
Fastboot flash recovery "twrp.img"
macjagger said:
I currently have this problem that when I flash a version of TWRP(have tried both 3.0.2 and 3.1.0) I cannot reboot my current OS(have tried both stock 376 and 378). Simply pressing the power button will result in recovery mode. Stranger still, when i flashed a ROM as a zip out of twrp, it actually booted up, but then I could no longer return to recovery mode, despite fiddling around mith multiple button combinations.
Seems as though i am missing something obvious, as i have not found a thread regarding a similar issue. Anybody have a clue as to what it might be?
Click to expand...
Click to collapse
oh hai
just wanted to link you in on this:
https://forum.xda-developers.com/z5...m-fix-twrp-t3560135/post71433741#post71433741
Hey fellas, I'm back. Excuse my absence, currently busy with exams.
It seems as though @Gewiz was correct. I was trying to flash twrp over "Flashtool>fastboot mode>select kernel to flash", which probably targets the wrong partition. Instead I now used "Flashtool>fastboot mode>reboot into fastboot mode via fastboot" and flashed it using the standard cmd window line ("fastboot flash recovery twrp.img") and it seems to have worked.
Thanks to everyone on this thread!
macjagger said:
Hey fellas, I'm back. Excuse my absence, currently busy with exams.
It seems as though @Gewiz was correct. I was trying to flash twrp over "Flashtool>fastboot mode>select kernel to flash", which probably targets the wrong partition. Instead I now used "Flashtool>fastboot mode>reboot into fastboot mode via fastboot" and flashed it using the standard cmd window line ("fastboot flash recovery twrp.img") and it seems to have worked.
Thanks to everyone on this thread!
Click to expand...
Click to collapse
Have you tried to do a restore yet?
Just wanted to ask so I can isolate twrp with rootkernel
Related
hi
im flash cynagen mod 12 by twrp recovery but when the phone up recovery is changed to cyanogen and dont work very good for ex dont work for install any things... i flash zombie kernel by flash tool but dont change my recovery !.... what to do change my custom recovery to philiz or twrp or.... ?
If youre trying toflash another rom or restore a backup You can hotboot doom kernel by placing the boot img in your adb area open command prompt and place phone in fastbootmode (hold vol up and connect usb to pc) type fastboot devices then enter in command prompt then type fastboot boot boot.img...as the phone boots remember to hold vol down when you see purple led otherwise you might have to repeat the process!!!
....
zubeedubs said:
If youre trying toflash another rom or restore a backup You can hotboot doom kernel by placing the boot img in your adb area open command prompt and place phone in fastbootmode (hold vol up and connect usb to pc) type fastboot devices then enter in command prompt then type fastboot boot boot.img...as the phone boots remember to hold vol down when you see purple led otherwise you might have to repeat the process!!!
Click to expand...
Click to collapse
i have win8 and dont work fastboot
Try number 4 on this list and place the shortcut and boot img in your adb folder...
http://www.7tutorials.com/7-ways-launch-command-prompt-windows-7-windows-8
After hotbooting doom kernael ,how to get TWRP recovery in 5.0 ROMs
recovery Problem
I have the same Problem( but my phone is xperia z) but it only appears automaticly in lollipop . and i can't change in lollipo ,on KitKat Roms it works fine. I really don't get it how this works .i flashed to stock then i flashed a aosbam Rom (KitKat) ,after that I flashed the lightning kernel. On kit kat i habe twrp but as soon flash a lollipop Rom it becomes a useless
Cyanogen recovery.All this started after I installed a APP in lollipop to getrecovery because it disapeared in validus rom ( lollipop).
Sorry that i ask for help in this thread but it's the only one i could find which is active.
You can use Rashr to replace recovery in current kernel image on the go. I use it all the time to get TWRP - works perfectly. Can backup kernel image before modifying.
You can flash Philz, TWRP (any version, incl. 2.8.5.0) or any other recovery image from sdcard with it on top of AOSP kernel.
https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools
B.Maximenko said:
You can use Rashr to replace recovery in current kernel image on the go. I use it all the time to get TWRP - works perfectly. Can backup kernel image before modifying.
You can flash Philz, TWRP (any version, incl. 2.8.5.0) or any other recovery image from sdcard with it on top of AOSP kernel.
https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools
Click to expand...
Click to collapse
I have a recent CM12 nightly installed on my Z Ultra and would like to get rid of the built in CM Recovery and flash TWRP. Will the app Rashr flash the TWRP img successfully, without any further modifications - change of kernel etc?
Thank you.
pretty pixel said:
I have a recent CM12 nightly installed on my Z Ultra and would like to get rid of the built in CM Recovery and flash TWRP. Will the app Rashr flash the TWRP img successfully, without any further modifications - change of kernel etc?
Thank you.
Click to expand...
Click to collapse
Yes, this is how I do. Just run Rashr on fresh CM12 installation with stock kernel and CM recovery--and get TWRP with stock kernel.
BTW, I don't know if TWRP will be overwritten after flashing a new CM nightly, didn't try yet. So maybe you'll have to run Rashr after every CM update.
B.Maximenko said:
Yes, this is how I do. Just run Rashr on fresh CM12 installation with stock kernel and CM recovery--and get TWRP with stock kernel.
BTW, I don't know if TWRP will be overwritten after flashing a new CM nightly, didn't try yet. So maybe you'll have to run Rashr after every CM update.
Click to expand...
Click to collapse
That's great. Thank you. I don't mind if I need to re-flash TWRP after each CM update
---------- Post added at 11:51 PM ---------- Previous post was at 10:53 PM ----------
B.Maximenko said:
Yes, this is how I do. Just run Rashr on fresh CM12 installation with stock kernel and CM recovery--and get TWRP with stock kernel.
BTW, I don't know if TWRP will be overwritten after flashing a new CM nightly, didn't try yet. So maybe you'll have to run Rashr after every CM update.
Click to expand...
Click to collapse
Thank you. On boot, how do you enter TWRP? Volume up, or volume down?
pretty pixel said:
That's great. Thank you. I don't mind if I need to re-flash TWRP after each CM update
---------- Post added at 11:51 PM ---------- Previous post was at 10:53 PM ----------
Thank you. On boot, how do you enter TWRP? Volume up, or volume down?
Click to expand...
Click to collapse
During boot, wait until device vibrates and hold vol down until you see TWRP logo.
B.Maximenko said:
During boot, wait until device vibrates and hold vol down until you see TWRP logo.
Click to expand...
Click to collapse
I can confirm this worked for me. Thank you again..
My Moto E Hangs when I try to boot a TWRP image
Attempted procedure:
(After booting into stock fastboot)
Code:
fastboot boot twrp-2.7.1.0-condor.img
A reboot to that TWRP was expected instead. But it freezes on bootloader.
TWRP used on the attempt:
dl.twrp.me/condor/twrp-2.7.1.0-condor.img.html
I don't want to flash a different recovery or anything else, just a clean root.
Moto E XT1025 DTV Dual BR
4.4.4
21.12.40.condor_retbr_tv_ds.retvr.en.BR.retbr
LucasBS1 said:
My Moto E Hangs when I try to boot a TWRP image
Attempted procedure:
(After booting into stock fastboot)
Code:
fastboot boot twrp-2.7.1.0-condor.img
A reboot to that TWRP was expected instead. But it freezes on bootloader.
TWRP used on the attempt:
dl.twrp.me/condor/twrp-2.7.1.0-condor.img.html
I don't want to flash a different recovery or anything else, just a clean root.
Moto E XT1025 DTV Dual BR
4.4.4
21.12.40.condor_retbr_tv_ds.retvr.en.BR.retbr
Click to expand...
Click to collapse
Sometimes booting recovery doesn't work...You will have to flash it. Perhaps you can flash the stock recovery after successful root? though i am not sure that will work
Also try booting into CWM
Tried the same method with CWM.img
Same result: fastboot frozen (volume buttons not responsive, and PC no longer sends commands)
To flash the stock recovery I would need to back it up first
But guess what's needed to backup ?
Yes, a temporary flashed bootloader with ZIP support
Would you know someone, who knows someone, who knows an master from MTI or Hogwarts or Narnia that knows an alternative ?
I would flash a mod right away if I could backup the original first...
(Unless, as I don't know exactly how this works, the ROM might come with the bootloader (?) Because the stock ROM I can download easily anywhere (already did))
LucasBS1 said:
Tried the same method with CWM.img
Same result: fastboot frozen (volume buttons not responsive, and PC no longer sends commands)
To flash the stock recovery I would need to back it up first
But guess what's needed to backup ?
Yes, a temporary flashed bootloader with ZIP support
Would you know someone, who knows someone, who knows an master from MTI or Hogwarts or Narnia that knows an alternative ?
I would flash a mod right away if I could backup the original first...
(Unless, as I don't know exactly how this works, the ROM might come with the bootloader (?) Because the stock ROM I can download easily anywhere (already did))
Click to expand...
Click to collapse
Hi,
Did you managed it to work? I have exactly the same problem. If I even flash twrp or cwm I still can't boot into it, there is only "no command" message.
I can't get any help anywhere, it makes me crazy. Do you have any custom recovery that worked for you after flashing?? I'm even starting to think that my device is broken somehow.
giaur said:
Hi,
Did you managed it to work? I have exactly the same problem. If I even flash twrp or cwm I still can't boot into it, there is only "no command" message.
I can't get any help anywhere, it makes me crazy. Do you have any custom recovery that worked for you after flashing?? I'm even starting to think that my device is broken somehow.
Click to expand...
Click to collapse
I did NOT flash the recovery yet
I'm trying to run the recovery without flashing it, to avoid problems like yours
You said you flashed both CWM and TWRP ?
And Neither one of them worked ?
I'm screwed too, then...
:crying:
See if you can find the stock recovery somewhere
And NOT here
This forum is not good for it
It's too much phone specific... too narrow... and we get no attention; specially with our "not-mainstream" phone
Generic instruction could work
If you take any action, or find any forum you find helpful, let me know
@giaur @LucasBS1
I too have tried booting the recovery ,but it doesn't work. You will have to flash it
if you are seeing 'no command' message it means that you still have stock recovery and the custom recovery wasn't flashed successfully.
try this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-2-0-touch-recovery-t2971601
or this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-6-0-touch-recovery-t3100879
LucasBS1 said:
I did NOT flash the recovery yet
I'm trying to run the recovery without flashing it, to avoid problems like yours
You said you flashed both CWM and TWRP ?
And Neither one of them worked ?
I'm screwed too, then...
:crying:
See if you can find the stock recovery somewhere
And NOT here
This forum is not good for it
It's too much phone specific... too narrow... and we get no attention; specially with our "not-mainstream" phone
Generic instruction could work
If you take any action, or find any forum you find helpful, let me know
Click to expand...
Click to collapse
None of them worked. I'm going to resign, because there is nothing I can do. Seems you have exactly the same problem as me. What I tried:
- fastboot boot recovery.img. Phone hangs on bootlogo
- flash recovery, then use go to recovery option in fastboot menu. In this case, 2 possibilities: with usb cable connected, it boots normally to system, not to recovery. With usb cable disconnected, screen goes black and phone looks like powered off. You will need to power it on and it will boot to system.
- On running system with usb debugging enabled. If you type "adb reboot recovery", you will end with dead robot and "no command" error. You can however press VolUP +Power on this screen and you will see Android 3e recovery.
If you have the same problem as me, you are completly lost and it's impossible to intall recovery on your device. I'm close to resign and say "**** this ****ty phone" because (as you already mentioned), there is no any attention on my questions, twrp support was dropped long time ago etc.
Flashing recovery should not wipe your data, so once you try to flash twrp or cwm, please let me know about your results. I'm sure I will never able to solve this problem, but I will feel better knowing that I'm not alone whit it
---------- Post added at 06:05 PM ---------- Previous post was at 06:00 PM ----------
mepsilon2 said:
@giaur @LucasBS1
I too have tried booting the recovery ,but it doesn't work. You will have to flash it
if you are seeing 'no command' message it means that you still have stock recovery and the custom recovery wasn't flashed successfully.
try this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-2-0-touch-recovery-t2971601
or this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-6-0-touch-recovery-t3100879
Click to expand...
Click to collapse
Still the same, I'm on stock recovery. In console, no errors:
Code:
[email protected]:~/android/DO_MOTOROLI/twrp/2.8.5$ fastboot flash recovery twrp2.8.5.0-recovery.img
target reported max download size of 299892736 bytes
sending 'recovery' (9046 KB)...
OKAY [ 0.312s]
writing 'recovery'...
OKAY [ 0.860s]
finished. total time: 1.172s
But "adb reboot recovery" - "No command". Damn it...
---------- Post added at 06:26 PM ---------- Previous post was at 06:05 PM ----------
Ok, I'm finished. It's not possible. F U C K Motorola and good night. My advice: don't waste your time if you have the same problem. You will get nothing, except wasted time. It's good that it's not my phone (I own OnePlus One). But I was asked to install CM12.1 on my friend's phone. It's impossible, so I will need to tell him I was failed with that.
mepsilon2 said:
@giaur @LucasBS1
I too have tried booting the recovery ,but it doesn't work. You will have to flash it
if you are seeing 'no command' message it means that you still have stock recovery and the custom recovery wasn't flashed successfully.
try this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-2-0-touch-recovery-t2971601
or this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-6-0-touch-recovery-t3100879
Click to expand...
Click to collapse
I see people complaining about bugs or not-working features on the first link
Are you sure it's safe ?
It's not the official TWRP (apparently)
When I google for this bootloader the official page shows version 2.7.1.0
Whereas on your second link they are on the 2.8.2.0
Which one should I trust ?
And to anyone who might answer:
Trough PC is the only/safest way to flash these recoveries ?
Seeing giaur on that situation puts me stepping back...
LucasBS1 said:
I see people complaining about bugs or not-working features on the first link
Are you sure it's safe ?
It's not the official TWRP (apparently)
When I google for this bootloader the official page shows version 2.7.1.0
Whereas on your second link they are on the 2.8.2.0
Which one should I trust ?
And to anyone who might answer:
Trough PC is the only/safest way to flash these recoveries ?
Click to expand...
Click to collapse
I tested both: latest official 2.7 and linked 2.8. So they are safe. Official support for Moto E was dropped long time ago.
giaur said:
I tested both: latest official 2.7 and linked 2.8. So they are safe. Official support for Moto E was dropped long time ago.
Click to expand...
Click to collapse
Cool
Regarding to safety
Should I flash CWM or TWRP ? Why ?
Regarding the method
Flash through usb->Fastboot or through Apk (like CWM)
Or a third method ?
And why
Between TWRP 2.7 and 2.8, which one is safer ?
And of course...why ?
And a last question, before I leave you guys alone:
Did you manage to root the phone, despite the poblems occurring to you, giaur ?
Once you succesfuly flash twrp, you need to flash supersu then and you are rooted. If you don't have your current system rooted, the only way to flash custom recovery is to flash via fastboot. TWRP is recommended, because it's way better
I can't say anything more, because my moto e is not flashable, so I can't replace stock recovery.
Yo !
Flashed TWRP
But wiped things I shouldnt
How to put the ROM back via USB ?
EDIT:
NEVERMIND
Found how to use SD to do that
giaur said:
Once you succesfuly flash twrp, you need to flash supersu then and you are rooted. If you don't have your current system rooted, the only way to flash custom recovery is to flash via fastboot. TWRP is recommended, because it's way better
I can't say anything more, because my moto e is not flashable, so I can't replace stock recovery.
Click to expand...
Click to collapse
I was also struggling a lot many days into getting twrp and cw loaded on to a Moto E. The problem was that I was pressing the Power button to activate the recovery menu and that will not activate the recovery option. You got to press the UP button instead of power after executing
Code:
fastboot.exe flash recovery twrp-2.8.1.0-condor.img
. This is quite counter intuitive but described well in most posts, but as experts we assume up button is to go up the menu.
Sunish Issac
I wanted the new update so that I could move my apps to my SD card. I also wanted TWRP.
I followed this guide to install TWRP.
TWRP was successfully flashed. So I try to boot into it using 'fastboot boot recovery.img' to boot into it.
I get the 'ERROR: Remote DTB not found' message. So booting into recovery using fastboot doesn't work.
I try booting into recovery manually (volume down + power). That doesn't work either. It freezes up at the OnePlus logo.
So, since TWRP isn't working, I flash stock recovery. That worked fine, and booted into it successfully (manually).
I boot into stock recovery and followed this guide to try updating manually using stock recovery. Of course, the update fails.
I then try flashing the full dump here. I factory reset, then flashed the full dump.
"Update successful."
Now, it refuses to boot into system AND recovery.
Okay, I'll just reflash stock recovery?
ERROR: Remote DTB not found
Booting into recovery manually freezes up too, just like TWRP did earlier.
Is there something I'm doing wrong to get this error? Google tells me dtb errors are caused by corrupt IMGs, but I downloaded all the IMGs twice and from all available mirrors to try them out. I see that some other users in the OnePlus forums and in XDA are having the same problems when flashing TWRP.
I really just need to be able to boot into at least one recovery so I can flash a system dump again.
I am not sure if this is the cause of the problem, but I've noticed most OnePlus X users have the E1003 model, while I am using a E1005.
Any help is appreciated.
mechanity said:
I wanted the new update so that I could move my apps to my SD card. I also wanted TWRP.
I followed this guide to install TWRP. Like a few others in the thread, I had the problem that when I try to boot manually into recovery, the screen shows the OnePlus logo with the android logo. Then the android logo disappears, and no matter how long I hold the down button while booting, the screen freezes at the OnePlus logo.
Fine, I'll just use fastboot boot recovery.img .
Nope, I get the 'ERROR: Remote DTB not found' message. Still stuck on the fastboot screen.
Great, I'll just flash stock recovery. Cool, it worked.
I booted into stock recovery and followed this guide to try updating manually using stock recovery. Of course the update fails.
Maybe I can just flash the full dump here. I factory reset, then flashed the full dump. Now it refuses to boot into system AND recovery.
Okay, I'll just reflash stock recovery?
ERROR: Remote DTB not found
Booting into recovery manually gives me the same results as flashing TWRP did earlier. So now, I can neither flash stock recovery nor TWRP to install any OxygenOS.
Is there something I'm doing wrong to get this error? Google tells me dtb errors are caused by corrupt IMGs, but I downloaded all the IMGs twice and from all available mirrors to try them out. I really just need to be able to boot into at least one recovery so I can flash a system dump again.
I am not sure if this is the cause of the problem, but I've noticed most OnePlus X users have the E1003 model, while I am using a E1005.
Any help is appreciated.
Click to expand...
Click to collapse
When you try do go in recovery manually(volume up+power) what does it show
mohammedtabish said:
When you try do go in recovery manually(volume up+power) what does it show
Click to expand...
Click to collapse
Well, pressing volume up + power actually takes me to bootloader mode.
Volume down + power, on the other hand, shows the OnePlus logo and the Android logo for a split second. Then the android logo disappears, the OnePlus logo stays, and it freezes there.
In case my post wasn't very clear, the same thing happens even if I don't attempt to boot into recovery (as in, it does the same thing if I just press the power button to boot into the system).
In bootloader try to go in fastboot mode then flash the recovery using fastboot
Sent from my ONE E1003 using Tapatalk
mohammedtabish said:
In bootloader try to go in fastboot mode then flash the recovery using fastboot
Sent from my ONE E1003 using Tapatalk
Click to expand...
Click to collapse
That is exactly what I said I did in the OP. I have tried this multiple times.
Yes its softbrick and to solve this prob the only thing that i can think is install usb drivers again and tell me you that you have checked the debugging before getting softbricked and try f2fs recovery from eng_stk kernel thread
Sent from my ONE E1003 using Tapatalk
mohammedtabish said:
Yes its softbrick and to solve this prob the only thing that i can think is install usb drivers again and tell me you that you have checked the debugging before getting softbricked and try f2fs recovery from eng_stk kernel thread
Sent from my ONE E1003 using Tapatalk
Click to expand...
Click to collapse
I tried the f2fs recovery from blu_spark eng.stk thread just now. I am still getting the remote: dtb not found error.
Still freezing when I boot manually into the recovery.
I think change the pc you are using and start every thing from new in other thats the last hope
Sent from my ONE E1003 using Tapatalk
mohammedtabish said:
I think change the pc you are using and start every thing from new in other thats the last hope
Sent from my ONE E1003 using Tapatalk
Click to expand...
Click to collapse
Tried all of these steps on two other PCs already, on both Windows 8 and Windows 7. It's not a driver issue or OS issue.
Guess I'll have to wait until the system IMGs are out, unless anyone else has any other suggestions.
System image ??? If you mean stock then its available bro
Sent from my ONE E1003 using Tapatalk
mohammedtabish said:
System image ??? If you mean stock then its available bro
Sent from my ONE E1003 using Tapatalk
Click to expand...
Click to collapse
It's available as a .zip, which means you need a working recovery to install it.
There is image also if you cant find it i can upload that i have backed up that or i will try to find that link
Sent from my ONE E1003 using Tapatalk
mohammedtabish said:
There is image also if you cant find it i can upload that i have backed up that or i will try to find that link
Sent from my ONE E1003 using Tapatalk
Click to expand...
Click to collapse
Please do find that link or upload it, I cannot find it at all.
Thank you very much.
[/COLOR]
mechanity said:
Please do find that link or upload it, I cannot find it at all.
Thank you very much.
Click to expand...
Click to collapse
There you go bro
https://drive.google.com/file/d/0B3AIip-hiOnNaTVSQXk5bUgzVnM/view?usp=sharing
Sent from my ONE E1003 using Tapatalk
Hit thanks if helped
mohammedtabish said:
[/COLOR]
There you go bro
https://drive.google.com/file/d/0B3AIip-hiOnNaTVSQXk5bUgzVnM/view?usp=sharing
Sent from my ONE E1003 using Tapatalk
Hit thanks if helped
Click to expand...
Click to collapse
Sorry, I think you misunderstood me. I stated in the original post that I already have the stock recovery img, and have already tried flashing it.
I am talking about a full system image that can be flashed via fastboot or odin.
Ooooooo i think thats not available sorry for waisting you time though
Sent from my ONE E1003 using Tapatalk
mohammedtabish said:
Ooooooo i think thats not available sorry for waisting you time though
Sent from my ONE E1003 using Tapatalk
Click to expand...
Click to collapse
It's okay, thanks for your help.
mechanity said:
Tried all of these steps on two other PCs already, on both Windows 8 and Windows 7. It's not a driver issue or OS issue.
Guess I'll have to wait until the system IMGs are out, unless anyone else has any other suggestions.
Click to expand...
Click to collapse
been having the exact issue...now people wont think im crazy.
---------- Post added at 05:27 PM ---------- Previous post was at 05:26 PM ----------
mechanity said:
Sorry, I think you misunderstood me. I stated in the original post that I already have the stock recovery img, and have already tried flashing it.
I am talking about a full system image that can be flashed via fastboot or odin.
Click to expand...
Click to collapse
You can boot to stock.img?
I have the same dtb error when I try any twrp image I have attempted to flash...exactly like your issue, but stock works fine.
If you can get into stock you can flash the full rom zip of 2.1.2 and then flash the ota to 2.1.3 after.
You have to flash the full zip first.
joho5 said:
been having the exact issue...now people wont think im crazy.
---------- Post added at 05:27 PM ---------- Previous post was at 05:26 PM ----------
You can boot to stock.img?
I have the same dtb error when I try any twrp image I have attempted to flash...exactly like your issue, but stock works fine.
If you can get into stock you can flash the full rom zip of 2.1.2 and then flash the ota to 2.1.3 after.
You have to flash the full zip first.
Click to expand...
Click to collapse
Originally, I could boot to the stock recovery. However after flashing that full 2.1.3 dump that I linked to, I can't boot to system or recovery. Flashing stock recovery now gives me the same remote:dtb not found error.
i have the same problem
i can't get into adb but can get into fastboot
Hi dudes. I have question. Is possible to have root on nougat on togari ( z ultra ) ? If IT is, van someone explain me, how to do IT ? Or give some link for tutorial.
I have the same situation with recovery.
Have Nougat AOiSP 7.1.1
Thanks for respond
FranekOz said:
Hi dudes. I have question. Is possible to have root on nougat on togari ( z ultra ) ? If IT is, van someone explain me, how to do IT ? Or give some link for tutorial.
I have the same situation with recovery.
Have Nougat AOiSP 7.1.1
Thanks for respond
Click to expand...
Click to collapse
If you have AOSiP 5.6 Nougat I think you should already have root access with SuperSU, look for it in settings, if not, having a custom rom you should have a recovery, reboot to recovery and flash SuperSU.zip from the following link
https://download.chainfire.eu/696/supersu/
Good luck mate!
Sent from my Xperia+Z+Ultra using Tapatalk
Oh dude, thanks for answering
But there is problem. I havent any option with "root" in name. And after install rom i losted my recovery. After this i installed cm recovery img by flashtool ( twrp image in flashtool bricking my bootloader). So when i flashed.... I have purple led. And okay... But when i going to recovery LED is correctly Orange. And after this phone screen is turning off and after few seconds going to normal system booting. For sure i have C6833. What i can do ? Im doing something wrong ?
Ok, I think you should flash TWRP 3.0.x directly to the new /recovery partition via fastboot:
fastboot erase recovery
fastboot flash recovery recovery.img
Here's a link to the full thread with detailed instructions and links to download the .img file you'll need, this way you'll never loose recovery again
https://forum.xda-developers.com/showthread.php?t=3307043
Then if successful you should be able to boot to your new recovery and flash SuperSU.
If you were to fail to get recovery with that method you might have a different problem, try the above, if it doesn't work I'll help. There's a chance your recovery partition wasn't created correctly....
Sent from my Xperia+Z+Ultra using Tapatalk
Okay ill gry tomorrow. There is starting to be late. And i will informate You. Thanks You realny much
Hi!
After flashing that twrp 3 you linked, I still can not enter to recovery.
Power button, wait for purple, push vol down purple changes to weird lightbrown, than nothing.
before cm was working, than I was put a dual rom there, which wasn't able if I remember correctly to flash that nougat, so i flashed it from fastboot. From there I'm not able to enter recovery.
Also that link says "To use, make sure you have installed the new bootloader by flashing the latest stock Sony ROM at least once."
So it could be a problem? I don't know which one was the last stock Sony ROM it, I was bought it used, and w/o thinking I was put cm on it.
pictogram said:
Hi!
After flashing that twrp 3 you linked, I still can not enter to recovery.
Power button, wait for purple, push vol down purple changes to weird lightbrown, than nothing.
before cm was working, than I was put a dual rom there, which wasn't able if I remember correctly to flash that nougat, so i flashed it from fastboot. From there I'm not able to enter recovery.
Also that link says "To use, make sure you have installed the new bootloader by flashing the latest stock Sony ROM at least once."
So it could be a problem? I don't know which one was the last stock Sony ROM it, I was bought it used, and w/o thinking I was put cm on it.
Click to expand...
Click to collapse
You seeing the led going purple and all colors shows you are on an old stock rom.
Flash the latest firmware with Flashtool: http://www.flashtool.net/downloads.php
And try again.
I need stock 5.1 lp for flash recovery ? Damn....
Ok I did it. No purple light now.
But now I don't know how to enter recovery.
Stock sony 5.1.1 is on. Tried to get in recovery, but just boots.
Flashed twrp 3.0 still don't know how to get in.
I thought to install XZDualRecovery https://forum.xda-developers.com/showthread.php?t=2647492 because it says how to enter into it, but im not sure i can flash it via fastboot.
heeeelp!
edit:
adb reboot recovery just simply restarts back to android... ? O.O
eddit:
never mind, it works now
To enter recovery:
* Switch off the phone
* Hold Vol-Down & Power button simultaneously until the phone vibrates
* Release the power button and keep holding Vol-Down until the Sony logo appears
Sent from my Xperia+Z+Ultra using Tapatalk
---------- Post added at 06:26 PM ---------- Previous post was at 06:10 PM ----------
FranekOz said:
I need stock 5.1 lp for flash recovery ? Damn....
Click to expand...
Click to collapse
You don't actually need it, if you had latest Sony stock at least once then the new bootloader would have been installed, and new /recovery partition created.
If you read and followed AOSiP installation instructions correctly, you should have been aware that having had lollipop installed in your phone was also needed for any Marshmallow or Nougat Rom to work, since your AOSiP worked that should've been the case.
Did you try flashing TWRP 3.0.x via fastboot?
Sent from my Xperia+Z+Ultra using Tapatalk
9crack said:
To enter recovery:
* Switch off the phone
* Hold Vol-Down & Power button simultaneously until the phone vibrates
* Release the power button and keep holding Vol-Down until the Sony logo appears
Sent from my Xperia+Z+Ultra using Tapatalk
---------- Post added at 06:26 PM ---------- Previous post was at 06:10 PM ----------
You don't actually need it, if you had latest Sony stock at least once then the new bootloader would have been installed, and new /recovery partition created.
If you read and followed AOSiP installation instructions correctly, you should have been aware that having had lollipop installed in your phone was also needed for any Marshmallow or Nougat Rom to work, since your AOSiP worked that should've been the case.
Did you try flashing TWRP 3.0.x via fastboot?
Sent from my Xperia+Z+Ultra using Tapatalk
Click to expand...
Click to collapse
Yeah, now recovery working. But i installed supersu next to get in recovery, witthout checking than my rom working correctly. And now i have issue with AOSiP logo... Its stuck ( i had that before in diffrent roms).or recovery. So i will try to take my system wipe....
You're almost there man, you now have a decent recovery, now as you said just do a full wipe, flash rom, gapps and SuperSU, reboot and see if it's working the way you like, write any findings or whatever at your rom's thread, good luck bro.
Sent from my Xperia+Z+Ultra using Tapatalk
9crack said:
To enter recovery:
* Switch off the phone
* Hold Vol-Down & Power button simultaneously until the phone vibrates
* Release the power button and keep holding Vol-Down until the Sony logo appears
Click to expand...
Click to collapse
If I do that nothing happens.
The purple light come back to me, so i'm waiting for that, and when it appears, i press the vol-up and twrp comes in. Though it freezes out, if i press vol-down when the purple light is comeing, or when i press restart in twrp. Black nothingness in both cases.
I think the purple light at boot come back when I flashed nougat boot, system and userdata. I don't really understand. Firmware is a different thing right? It is not on the partitions.
I probably will put another nougat on it, this: https://forum.xda-developers.com/xp...elopment-cm14-android-7-0-freexperia-t3457377
instead of this one: https://forum.xda-developers.com/xperia-z-ultra/development/android-n-t3452954
I will hope it doesn't freeze inside the os.
edit: ohh its freezeng out there too: https://forum.xda-developers.com/showpost.php?p=68603461&postcount=17
eddit: your method also works i tried it again now. when i was powering off the phone it was freezed out. (but i thought it is off) so had to push that reset button.
Whenever your phone needs a restart, (i.e. something happened and it seems frozen...) you don't have to use the little red reset button, you can get the same result by holding Power button + Vol-up until it vibrates, that'll switch it off just like the reset button, then you can just turn it back on normally to boot to your rom or boot to recovery.
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 ?