OK, so I flashed TWRP and now I have sort of a halfway bricked x829- I can load TWRP and Fastboot, that's it. I can't adb sideload anything because I get a "cannot read" error. I also can't Fastboot flash anything because all the ROMs I can find are zip files, and not .img files. What am I doing wrong?
Wagmans said:
OK, so I flashed TWRP and now I have sort of a halfway bricked x829- I can load TWRP and Fastboot, that's it. I can't adb sideload anything because I get a "cannot read" error. I also can't Fastboot flash anything because all the ROMs I can find are zip files, and not .img files. What am I doing wrong?
Click to expand...
Click to collapse
ok why do you even want to flash the rom with adb/fastboot?
even if you forgot to cp the rom onto the sdcard - just flash with twrp from a stick - OTG works fine
Horsebeatsbishop said:
ok why do you even want to flash the rom with adb/fastboot?
even if you forgot to cp the rom onto the sdcard - just flash with twrp from a stick - OTG works fine
Click to expand...
Click to collapse
OTG not working for me either. I have a USB C to standard USB adapter and it doesn't see any flash drives (I can see the drive being accessed- the light flashes, but doesn't mount). Do I need a USB OTG C Y adapter? I'm a bit lost why I can't just adb sideload.
Someone explain it to me like I'm a child. Obviously I'm doing something wrong and I'm missing something.
Wagmans said:
OTG not working for me either. I have a USB C to standard USB adapter and it doesn't see any flash drives. Do I need a USB OTG C Y adapter? I'm a bit lost why I can't just adb sideload.
Someone explain it to me like I'm a child. Obviously I'm doing something wrong and I'm missing something.
Click to expand...
Click to collapse
ok sounds like a toughie - never had a problem with OTG (neither with fat32 nor ntfs both works (twpr 3.0.2.1 myself) )
since i'm just a beginner myself i can only give you ideas where i would look:
-do you even see your device in adb service?
-enabled usb-debug?
-current usb driver?
-current adb version?
-correct adb version (32/64b)?
Horsebeatsbishop said:
ok sounds like a toughie - never had a problem with OTG (neither with fat32 nor ntfs both works (twpr 3.0.2.1 myself) )
since i'm just a beginner myself i can only give you ideas where i would look:
-do you even see your device in adb service?
-enabled usb-debug?
-current usb driver?
-current adb version?
-correct adb version (32/64b)?
Click to expand...
Click to collapse
I flashed TWRP properly- but when I put it into recovery I get half a corrupted screen- after the screen goes off if I press the power button I can access TWRP.
I tried flashing multiple flash drives in different formats- yes, I can see the drive LEDs flash after I insert it, but when I try to mount it says "0" space for all drives.
So, I assume everything is working properly because adb can see the device in sideload mode (Win 10 device mgr shows it as a USB device, when in TWRP (no sideload mode) it sees it as ADB device- but when I try to run ADB it doesn't show any devices):
List of devices attached
17963e29 sideload
No devices listed when sideload in TWRP is off.
I should be able to sideload something, but I get:
loading: 'le_x2_x820-5.9.020S.zip'
* cannot read 'le_x2_x820-5.9.020S.zip' *
Every time- every file.
Bricked?
are you using the official twrp ?
you should... https://twrp.me/devices/leecolemax2.html
or use multirom.
you can also transfer the rom first using mtp (in twrp).and flash afterwards.
Gesendet von meinem LEX820 mit Tapatalk
A.N.Droid said:
are you using the official twrp ?
you should... https://twrp.me/devices/leecolemax2.html
or use multirom.
you can also transfer the rom first using mtp (in twrp).and flash afterwards.
Gesendet von meinem LEX820 mit Tapatalk
Click to expand...
Click to collapse
FlashTools64_20161125.zip
I figured it out. I had to download FlashTools64 from Asus in order to sideload the file without the "cannot read" error. Well, that took me all morning.
This should be posted in the TWRP sticky.
I'm sideloading a rom right now. Let's see what happens...
Wagmans said:
FlashTools64_20161125.zip
I figured it out. I had to download FlashTools64 from Asus in order to sideload the file without the "cannot read" error. Well, that took me all morning.
This should be posted in the TWRP sticky.
I'm sideloading a rom right now. Let's see what happens...
Click to expand...
Click to collapse
looks like the standard 15 sec adb installer to me... seems u had the wrong version
Horsebeatsbishop said:
looks like the standard 15 sec adb installer to me... seems u had the wrong version
Click to expand...
Click to collapse
I don't know- I dowloaded it right from the link in the TWRP thread.
Anyways. now when I'm sideloading a ROM it times out at 46% every time (TWRP stops sideload mode). Any ideas?
Wagmans said:
I don't know- I dowloaded it right from the link in the TWRP thread.
Anyways. now when I'm sideloading a ROM it times out at 46% every time (TWRP stops sideload mode). Any ideas?
Click to expand...
Click to collapse
I had sort of the same problem, your not encrypted are you?
Supertacomonkeyexplosion said:
I had sort of the same problem, your not encrypted are you?
Click to expand...
Click to collapse
Nope. Unless I can sideload a ROM I'm stuck because TWRP won't mount a flash drive for me.
why dont you transfer the zip first with mtp?
Gesendet von meinem LEX820 mit Tapatalk
Wagmans said:
Nope. Unless I can sideload a ROM I'm stuck because TWRP won't mount a flash drive for me.
Click to expand...
Click to collapse
You can't boot the OS at all ?
I flashed twrp, couldn't backup,side load or read any OTG. I ended up booting back into my stock OS, loosing twrp, putting teamspain cm13 on, reflashing twrp from fastboot then immediately booting into twrp and flashing CM zip.
Mine was encryption problem though, cm let me decrypt and twrp started working right
Supertacomonkeyexplosion said:
You can't boot the OS at all ?
I flashed twrp, couldn't backup,side load or read any OTG. I ended up booting back into my stock OS, loosing twrp, putting teamspain cm13 on, reflashing twrp from fastboot then immediately booting into twrp and flashing CM zip.
Mine was encryption problem though, cm let me decrypt and twrp started working right
Click to expand...
Click to collapse
Nope. Just TWRP, that's it. As for MTP it doesn't even show up- just as a Android ADB Device in the drivers when in TWRP, and as a USB Device in TWRP Sideload mode. Remember, I'm stuck in either TWRP or Fastboot mode.
Wagmans said:
Nope. Just TWRP, that's it. As for MTP it doesn't even show up- just as a Android ADB Device in the drivers when in TWRP, and as a USB Device in TWRP Sideload mode. Remember, I'm stuck in either TWRP or Fastboot mode.
Click to expand...
Click to collapse
you have strange issues. are you sure you installed the right twrp version for your device? a link would help.
about adb:
i'm using universal ADB drivers and it just works.
http://adbdriver.com
Gesendet von meinem LEX820 mit Tapatalk
Wagmans said:
Nope. Just TWRP, that's it. As for MTP it doesn't even show up- just as a Android ADB Device in the drivers when in TWRP, and as a USB Device in TWRP Sideload mode. Remember, I'm stuck in either TWRP or Fastboot mode.
Click to expand...
Click to collapse
Strange that you lost your OS just flashing a recovery image, I've never seen that before. My last suggestion would be to fastboot flash a earlier version of TWRP.
Not sure of you seen this..... Last resort if you can't figure it out
https://forum.xda-developers.com/le-max-2/how-to/guide-hard-brick-fix-qualcomm-hs-usb-t3492949
Getting closer- I gave up on sideloading and I was finally able to push a ROM to the phone.
Thanks for all the help guys. Now running Chinese .20s ROM. Took long enough.lol
Wagmans said:
Getting closer- I gave up on sideloading and I was finally able to push a ROM to the phone.
Thanks for all the help guys. Now running Chinese .20s ROM. Took long enough.lol
Click to expand...
Click to collapse
Glad you figured it out.
Your running Chinese 20s on x829?
Lots of people will be interested to know how it runs..... Fingerprint? Language? Band 20? VoLTE?
Supertacomonkeyexplosion said:
Glad you figured it out.
Your running Chinese 20s on x829?
Lots of people will be interested to know how it runs..... Fingerprint? Language? Band 20? VoLTE?
Click to expand...
Click to collapse
Been playing with it a bit:
Shows as X820 with 64GB
Fingerprint still doesn't work for me
Google Voice doesn't work- at least I haven't figured it out (Doesn't recognize "OK Google"- I have to go into the app by hand).
Same problem- no VoLTE on AT&T here in US (didn't think it would work- unsupported phone). On Band 2 with LTE (cycled it- was on band 17 before). Haven't checked the other bands yet.
Lots of bloatware. That I can deal with. If I can't get Google voice recognition working properly I'll probably go to a custom ROM.
Wagmans said:
Getting closer- I gave up on sideloading and I was finally able to push a ROM to the phone.
Thanks for all the help guys. Now running Chinese .20s ROM. Took long enough.lol
Click to expand...
Click to collapse
You should share how did u fix it for helping other people in the future
Enviado desde mi ASUS_Z00TD mediante Tapatalk
Related
I tried to flash the team spain 5.8 recovery but it does not work , flash seem to go well but still only boots into stock recovery.
Rom is 15s
zsajak said:
I tried to flash the team spain 5.8 recovery but it does not work , flash seem to go well but still only boots into stock recovery.
Rom is 15s
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=68462069&postcount=2
sanke1 said:
http://forum.xda-developers.com/showpost.php?p=68462069&postcount=2
Click to expand...
Click to collapse
How can I follow your guide If I cannot flash the recovery?
zsajak said:
How can I follow your guide If I cannot flash the recovery?
Click to expand...
Click to collapse
Are you having correct adb drivers installed? On my PC Windows 10 X64, they get installed from Windows Update and show up as "London Marshal adb interface."
It wouldn't hurt to try a different USB port.
Also try fully resetting your phone to factory default from the settings.
I am using X821 and only the TWRP recovery posted in my guide works. Other recoveries do not work for our device.
BTW I have updated my guide. Check it out again.
sanke1 said:
Are you having correct adb drivers installed? On my PC Windows 10 X64, they get installed from Windows Update and show up as "London Marshal adb interface."
It wouldn't hurt to try a different USB port.
Also try fully resetting your phone to factory default from the settings.
I am using X821 and only the TWRP recovery posted in my guide works. Other recoveries do not work for our device.
BTW I have updated my guide. Check it out again.
Click to expand...
Click to collapse
For some reason it was not working, it is now.
I still get a bootloop when I try to flash the resurrection remix rom.
cm13 by teamspain worked fine though
sanke1 said:
Are you having correct adb drivers installed? On my PC Windows 10 X64, they get installed from Windows Update and show up as "London Marshal adb interface."
It wouldn't hurt to try a different USB port.
Also try fully resetting your phone to factory default from the settings.
I am using X821 and only the TWRP recovery posted in my guide works. Other recoveries do not work for our device.
BTW I have updated my guide. Check it out again.
Click to expand...
Click to collapse
I followed your guide and installed twrp correctly and it worked.
I cannot install any rom besides cm13 unofficial though, i always get a bootloop if I install resurrection remix for example.
Its really very annoying, I wiped everything including data and system, only the official 16s roms works and cm13 unofficial, all other roms result in a bootloop.
something is not right here.
twrp not mounting storage data
sanke1 said:
Are you having correct adb drivers installed? On my PC Windows 10 X64, they get installed from Windows Update and show up as "London Marshal adb interface."
It wouldn't hurt to try a different USB port.
Also try fully resetting your phone to factory default from the settings.
I am using X821 and only the TWRP recovery posted in my guide works. Other recoveries do not work for our device.
BTW I have updated my guide. Check it out again.
Click to expand...
Click to collapse
twrp flased but its not mounting storage data, also sideload command to install supersu.zip didnt worked tried several times
its just stopping exactly at 73% everytime
Flash at your own risk!
Not responsible for any damage you may do by attempting to modify stock software!
Recovery will work on all Shield 16GB 2015, Shield Pro 2015 & Shield 2017 16GB. All models...
You need ADB and FASTBOOT to get this installed.
You can follow this guide HERE or HERE
See attachments below for download.
Update 02/01/17
Added proper device info for 2017 Shield 16GB to allow OTA updates. Should work but not 100% sure if it will.
Extract img file from within zip folder
Reboot to bootloader
Use one of the two following commands
To flash recovery
fastboot flash recovery recovery.img
To boot into recovery without flashing
fastboot boot recovery.img
---
Thanks to TWRP for making the sources available and to @Steel01 for his work on TWRP for original shield which this was ported from.
Might be a stupid question but will this be OK to use on the 1st gen 16gb version aswel?
Slayerkodi said:
Might be a stupid question but will this be OK to use on the 1st gen 16gb version aswel?
Click to expand...
Click to collapse
I doubt it since 2015 TWRP did not work on 2017.
Slayerkodi said:
Might be a stupid question but will this be OK to use on the 1st gen 16gb version aswel?
Click to expand...
Click to collapse
The files system files between 2017 and 2015 are different you can try it, you wont hurt anything, but i doubt it will work. if you do try it do fastboot boot and not fastboot flash
My laptops broke so won't be doing this anytime soon, will see if there is a way to flash twrp to recovery without a PC because as far I know android to android adb or fastboot does not work
I'll definitely test it in a few hours when I get home.
not booting for me
jonasgrosch said:
not booting for me
Click to expand...
Click to collapse
4K TV?
If yes, hook it up to 1080 TV or monitor.
AndroidUser00110001 said:
4K TV?
If yes, hook it up to 1080 TV or monitor.
Click to expand...
Click to collapse
no it'S 1080p. tried by flashing and direct booting. both will kinda flash the screen after booting, turn off the shield and reboot it after.
the short flashing screen is the only difference to my tests with the unhacked image of twrp.
jonasgrosch said:
no it'S 1080p. tried by flashing and direct booting. both will kinda flash the screen after booting, turn off the shield and reboot it after.
the short flashing screen is the only difference to my tests with the unhacked image of twrp.
Click to expand...
Click to collapse
your bootloader unlocked?
brandonb21 said:
your bootloader unlocked?
Click to expand...
Click to collapse
yes of course
jonasgrosch said:
yes of course
Click to expand...
Click to collapse
other people in the Q&A thread are saying it works fine. try another 1080p tv/monitor and make sure your using 5.0.1 non developer image on your 2017 shield
brandonb21 said:
other people in the Q&A thread are saying it works fine. try another 1080p tv/monitor and make sure your using 5.0.1 non developer image on your 2017 shield
Click to expand...
Click to collapse
tried with another screen. nothing changed. still not working
---------- Post added at 10:25 PM ---------- Previous post was at 10:18 PM ----------
jonasgrosch said:
tried with another screen. nothing changed. still not working
Click to expand...
Click to collapse
nevermind. got it working by disconnecting usb connection to my pc right after executing the boot command.
Are all the partitions showing up in TWRP that should be? I never put TWRP on my 2015 Shield Pro so not sure what should be showing up.
On my 2017 I can only write to the TWRP folder using the USB cable connected to my PC. I tried to put in a USB stick but TWRP did not recognize it nor does it recognize External Storage.
I have USB hard drive formatted for internal storage so not sure if that is why I don't see any partitions in TWRP and can only write to the TWRP folder.
I am about to build TWRP from source and was just wondering what partitions shows up from more experienced users so I can adjust the TWRP settings so more partitions show up if that is the cause....
AndroidUser00110001 said:
Are all the partitions showing up in TWRP that should be? I never put TWRP on my 2015 Shield Pro so not sure what should be showing up.
On my 2017 I can only write to the TWRP folder using the USB cable connected to my PC. I tried to put in a USB stick but TWRP did not recognize it nor does it recognize External Storage.
I have USB hard drive formatted for internal storage so not sure if that is why I don't see any partitions in TWRP and can only write to the TWRP folder.
I am about to build TWRP from source and was just wondering what partitions shows up from more experienced users so I can adjust the TWRP settings so more partitions show up if that is the cause....
Click to expand...
Click to collapse
I just got an email from nvidia and they processed my rma and now waiting for a tracking number i doubt il see mine till next week or i would help you out.
gunner007dc said:
I was able to unlock the bootloader, enable USB debugging.
I tried flashing the TWRP image, however attempting to boot into recovery gives the sad little android man with the red exclamation (NO COMMAND)
If I attempt to just boot the image I see the TWRP splash screen, then a few seconds later the system reboots.
Click to expand...
Click to collapse
try disconnecting the usb cable going from your pc to your android box right after hitting enter after typing "fastboot boot twrp.img"
seems to be a bug. make sure it downloads the image all the way before disconnecting.
gunner007dc said:
Yep that seemed to do it. I flashed TWRP already, just when I typed adb reboot recovery, you just have to disconnect the USB. Then it booted into TWRP just fine.
Stupid question, but is it best practice to just install the dev image + SuperSU at this point. It's what I'm currently running, but didn't know if it was just better to run stock image + SuperSU. (or maybe dev is needed for root)
Click to expand...
Click to collapse
use the retail one, the dev image can run beta drivers such as graphic drivers that may or may not cause issues at some point. and the developer image dosent get ota updates.
Was able to root mine as well by pulling out the usb cable while booting into twrp. Thanks Guys!
how do u install supersu with the usb cable disconnected?
brand0n9 said:
how do u install supersu with the usb cable disconnected?
Click to expand...
Click to collapse
Enable MTP in TWRP, plug USB cable in and then transfer SU to the internal drive?
So after a while of tinkering with my Honor 9 trying to flash Supersu via TWRP everything got messed up.
Tried doing a clean install, and that made everything worse.
So now i am stuck with no TWRP Recovery and cannot load the Fastboot. Only option available now is Huawei eRecovery through wifi that obviously doesnt work, and forced recovery (vol+ and vol- and powerbutton) which is also not working trying to flash with stockrom.
So what can i do now? am i missing something?
Inisio said:
So after a while of tinkering with my Honor 9 trying to flash Supersu via TWRP everything got messed up.
Tried doing a clean install, and that made everything worse.
So now i am stuck with no TWRP Recovery and cannot load the Fastboot. Only option available now is Huawei eRecovery through wifi that obviously doesnt work, and forced recovery (vol+ and vol- and powerbutton) which is also not working trying to flash with stockrom.
So what can i do now? am i missing something?
Click to expand...
Click to collapse
Do you have your PC connected via USB to your phone when trying to boot to fastboot?
completely power off phone, then hold vol-down and plug in USB cable... this should boot you into fastboot, try and flash TWRP from there, although, if you dont have the required files on your device (or any way to get them onto it) you are not in a good situation.
something similar happened to me the other day, and this got me into fastboot where i could flash a system.img (or use HWOTA or whatever it is), though i had TWRP installed, but no OS.
fregor said:
Do you have your PC connected via USB to your phone when trying to boot to fastboot?
Click to expand...
Click to collapse
Yeah, did that now and it worked. Although my previous attempts doing this nothing happened. But i am in the fastboot now atleast, bad news is that my device doesnt come up when using the apb devices command.
Any tips on what to do now? i suppose my device isnt showing because i cant use debug mode?
Inisio said:
Yeah, did that now and it worked. Although my previous attempts doing this nothing happened. But i am in the fastboot now atleast, bad news is that my device doesnt come up when using the apb devices command.
Any tips on what to do now? i suppose my device isnt showing because i cant use debug mode?
Click to expand...
Click to collapse
There's a lot of options on this forum if you have fastboot access and TWRP. So you should be able to get back to where you were before tinkering.
I recommend an external SD card reader to get necessary files on a SD card.
fregor said:
There's a lot of options on this forum if you have fastboot access and TWRP. So you should be able to get back to where you were before tinkering.
I recommend an external SD card reader to get necessary files on a SD card.
Click to expand...
Click to collapse
Yeah, i have been looking around on the forum alot, but almost every thread with a similiar problem they still have access to TWRP, which i dont sadly :/.
Inisio said:
Yeah, i have been looking around on the forum alot, but almost every thread with a similiar problem they still have access to TWRP, which i dont sadly :/.
Click to expand...
Click to collapse
You should be able to flash it in fastboot though. If your fastboot is locked and frp is locked, you have a problem.
Not sure if recovery in Hisuite might be an option.
Sent from my STF-L09 using Tapatalk
fregor said:
You should be able to flash it in fastboot though. If your fastboot is locked and frp is locked, you have a problem.
Sent from my STF-L09 using Tapatalk
Click to expand...
Click to collapse
yeah, i'm gonna see if i can come up with a way to flash it. Even though i cant find it using ADB anymore, there might some other way.
do you think it's possible doing this using the eRecovery Forced update?
Try this with a sdcard:
https://forum.xda-developers.com/showthread.php?t=3696892
oslo83 said:
Try this with a sdcard:
https://forum.xda-developers.com/showthread.php?t=3696892
Click to expand...
Click to collapse
So another problem, cant move bigger files than 4gb to the SD card. And cant format in NTFS because it seems like the phone wont take it.
but using a tempfile from a failed transfer the install at least starts, and ofcourse fails after a while since its incomplete. But how can i transfer the UPDATE.APP file to the card?
Inisio said:
So another problem, cant move bigger files than 4gb to the SD card. And cant format in NTFS because it seems like the phone wont take it.
but using a tempfile from a failed transfer the install at least starts, and ofcourse fails after a while since its incomplete. But how can i transfer the UPDATE.APP file to the card?
Click to expand...
Click to collapse
Format to exfat
Sent from my STF-L09 using Tapatalk
fregor said:
Format to exfat
Sent from my STF-L09 using Tapatalk
Click to expand...
Click to collapse
That did it, never thought of exfat! New firmware installed, thanks alot for the help!
Thank TWRPBuilder Team. Great dudes doing great things:good:
TWRP 3.2.3-0
Model# SM-T530/NU
https://drive.google.com/open?id=1UvSszpSLYTFgpieTLYQt5_z-0DZv3Dg9
Thank fo the head up but for the most part this version of TWRP work fine but when TWRP is not in use it go into deep sleep mode where device wont wake up at all unless i reboot it kind of suck i think about going back to version 3.1.1/3.0.1 witch is old but in my opinion work perfect with no bugs what so ever, Id use it if there was no bugs at all and every thing worked as expected. AKA still buggy as hell fo the most part
DJABHipHop said:
Thank fo the head up but for the most part this version of TWRP work fine but when TWRP is not in use it go into deep sleep mode where device wont wake up at all unless i reboot it kind of suck i think about going back to version 3.1.1/3.0.1 witch is old but in my opinion work perfect with no bugs what so ever, Id use it if there was no bugs at all and every thing worked as expected. AKA still buggy as hell fo the most part
Click to expand...
Click to collapse
I always disable screen timeout in the settings of TWRP so I haven't run into that issue. Im not sure why you would say its buggy as hell. I dont think a screen timeout bug qualifies it for all that. Just disable screen timeout in twrp settings and move on. Certainly not a reason to downgrade, but to each their own I guess.
some one please port it to t330nu ...
MTP
I've tried to port lineage os 14.1 from kminilte (Samsung S5mini) to degaslte (Samsung Tab4 T235Y) cause they have same chipset and gpu. But I have failed because I don't know much about porting roms. I just replaced
these following files from degaslte cm13 to kminilte cm14.1.
1.boot image
ramdisk - charger, default.prop, fastab.universal3470, init.universal3470.rc, init.universal3470.usb.rc, ueventd.rc, ueventd.universal3470.rc
split-img - boot.img-zImage
2.system.new.dat
System/Etc - Bluetooth and WiFi folder, apns-conf.xml, recovery-resource.dat
System/Lib - egl & hw & soundfx folder
System/vendor - firmware folder, lib/ hw folder
Now I facing issue with USB mtp not showing on my tab. Even in cm12.1, cm13, stock rom. Everything works except USB mtp. Twrp mtp also don't work. Please help me to solve this . Which files should I replace to work mtp USB?
Reshan Kariyawasam said:
I've tried to port lineage os 14.1 from kminilte (Samsung S5mini) to degaslte (Samsung Tab4 T235Y) cause they have same chipset and gpu. But I have failed because I don't know much about porting roms. I just replaced
these following files from degaslte cm13 to kminilte cm14.1.
1.boot image
ramdisk - charger, default.prop, fastab.universal3470, init.universal3470.rc, init.universal3470.usb.rc, ueventd.rc, ueventd.universal3470.rc
split-img - boot.img-zImage
2.system.new.dat
System/Etc - Bluetooth and WiFi folder, apns-conf.xml, recovery-resource.dat
System/Lib - egl & hw & soundfx folder
System/vendor - firmware folder, lib/ hw folder
Now I facing issue with USB mtp not showing on my tab. Even in cm12.1, cm13, stock rom. Everything works except USB mtp. Twrp mtp also don't work. Please help me to solve this . Which files should I replace to work mtp USB?
Click to expand...
Click to collapse
Let me know if the camera and mic work
i flashed this twrp and it keeps rebooting back to twrp any fix for this?
mrdreamers said:
i flashed this twrp and it keeps rebooting back to twrp any fix for this?
Click to expand...
Click to collapse
Thats really odd!
As of right now I've seccessfuly fixed the microphone but its still really quite witch requird more digging all soulutions are welcome at this time freas build comming today for t530&t530nu user new thread started by to posted all device fixes and rom tweaks to The Samsung Galaxy Tab 4 in general.
https://drive.google.com/drive/folders/1F3qVR2Gy-SCqFwg5El7-aeGn6UhX-_-_?usp=sharing
DJABHipHop said:
Thats really odd!
Click to expand...
Click to collapse
ya i just odin firmware and started over no root no recovery, its a x-mas gift to my sister and law anyway she don't need all that, she's not nerdy like us lol!!!!
How it look?
How's the recovery doing? Is it working fully?
How do you use this file? This is an .img file. Normally, you use a .tar file for twrp. I am running 3.0.1.0 on my SM-T530, but I would like to run 3.2.3 on here like I do for my SM-T900.
PizzaG said:
Thank TWRPBuilder Team. Great dudes doing great things:good:
TWRP 3.2.3-0
Model# SM-T530/NU
https://drive.google.com/open?id=1UvSszpSLYTFgpieTLYQt5_z-0DZv3Dg9
Click to expand...
Click to collapse
ive tried flahsing this and then my tablet says "recovery is not seandroid einforcement" whats should i do now? its not recognized by odin now when entering DM...
srialmaster said:
How do you use this file? This is an .img file. Normally, you use a .tar file for twrp. I am running 3.0.1.0 on my SM-T530, but I would like to run 3.2.3 on here like I do for my SM-T900.
Click to expand...
Click to collapse
I think our definitions of "normal" are different. Tar is for Odin, img is for when you already have TWRP installed. In TWRP, select install tab, install image tab, select your twrp.img file and flash it. Enjoy newer TWRP =)
If you are really worried about it, you can easily take the older TWRP tar file, open with winrar, and replace the old twrp with the new one. Then you will have an Odin flashable tar file with the newer TWRP. You can then send it to me and I'll post it on the Main page for others who want to flash it with Odin.
nico3dd said:
ive tried flahsing this and then my tablet says "recovery is not seandroid einforcement" whats should i do now? its not recognized by odin now when entering DM...
Click to expand...
Click to collapse
recovery is not seandroid einforcement isn't anything you need to worry about and affects nothing. It's nothing more than a nag from Samsung. What you should do now is enjoy updated TWRP. The recovery has 0 to do with Odin. If Odin isn't working, then it's your device or PC drivers. I'm able to use Odin with no issues. The only thing "wrong" with this TWRP is that there is no ADB/MTP usb in TWRP, which is a nice feature but not required for the average user. The other "issue" with this TWRP is that when in TWRP, the screen doesn't timeout correctly. Again, not a big deal at all. Just go into your TWRP settings and disable screen timeout. Who needs to be in TWRP and worrying about their screen timing out anyways? Certainly not me. I disable screen timeout, do my business in TWRP and boot. If you would like to fix the issue in TWRP, feel free. Let me know and I'll post the source for it and you can work on it.
PizzaG said:
I think our definitions of "normal" are different. Tar is for Odin, img is for when you already have TWRP installed. In TWRP, select install tab, install image tab, select your twrp.img file and flash it. Enjoy newer TWRP =)
If you are really worried about it, you can easily take the older TWRP tar file, open with winrar, and replace the old twrp with the new one. Then you will have an Odin flashable tar file with the newer TWRP. You can then send it to me and I'll post it on the Main page for others who want to flash it with Odin.
recovery is not seandroid einforcement isn't anything you need to worry about and affects nothing. It's nothing more than a nag from Samsung. What you should do now is enjoy updated TWRP. The recovery has 0 to do with Odin. If Odin isn't working, then it's your device or PC drivers. I'm able to use Odin with no issues. The only thing "wrong" with this TWRP is that there is no ADB/MTP usb in TWRP, which is a nice feature but not required for the average user. The other "issue" with this TWRP is that when in TWRP, the screen doesn't timeout correctly. Again, not a big deal at all. Just go into your TWRP settings and disable screen timeout. Who needs to be in TWRP and worrying about their screen timing out anyways? Certainly not me. I disable screen timeout, do my business in TWRP and boot. If you would like to fix the issue in TWRP, feel free. Let me know and I'll post the source for it and you can work on it.
Click to expand...
Click to collapse
thank you for fast replying!
problem is, tablet is useless now, i was trying to install lineageOS and along the way i encountered many issues, one of them being outdated twrp 3.0.3.0 wont let me start lineage (it showed a cannot load os message ) so i tried upgrading twrp and tablet is now busted, caput. cannot even get into recoveyr mode. it shows that reinforced thing message for 5 sesc and then it goes black and do nothing. how can i revert this wihtout flashing another recovery through odin?
nico3dd said:
thank you for fast replying!
problem is, tablet is useless now, i was trying to install lineageOS and along the way i encountered many issues, one of them being outdated twrp 3.0.3.0 wont let me start lineage (it showed a cannot load os message ) so i tried upgrading twrp and tablet is now busted, caput. cannot even get into recoveyr mode. it shows that reinforced thing message for 5 sesc and then it goes black and do nothing. how can i revert this wihtout flashing another recovery through odin?
Click to expand...
Click to collapse
At this point I would probably start over from scratch and flash stock with Odin. How did you try installing updated TWRP?
If you want me to update the tar file with newer TWRP so it can be flashed with Odin, send me the tar file of old twrp and the newer twrp img file and i'll get that done for you.
can you please port the twrp to the t330nu?
zuhero said:
can you please port the twrp to the t330nu?
Click to expand...
Click to collapse
If you send me a base that's close in hardware yes, i'll port it for you. I don't have time to hunt.
PizzaG said:
If you send me a base that's close in hardware yes, i'll port it for you. I don't have time to hunt.
Click to expand...
Click to collapse
this are the last twrps for t330nu that i've seen and worked well:
https://androidfilehost.com/?fid=24421527759888610
https://androidfilehost.com/?fid=24499762635999726
their respective threads are:
https://forum.xda-developers.com/tab...m-v32-t3109777
https://forum.xda-developers.com/tab...alaxy-t2922795
all credits go to user sub77
Delete
---------- Post added at 06:12 AM ---------- Previous post was at 06:08 AM ----------
zuhero said:
this are the last twrps for t330nu that i've seen and worked well:
https://androidfilehost.com/?fid=24421527759888610
https://androidfilehost.com/?fid=24499762635999726
their respective threads are:
https://forum.xda-developers.com/tab...m-v32-t3109777
https://forum.xda-developers.com/tab...alaxy-t2922795
all credits go to user sub77
Click to expand...
Click to collapse
If you know how to get skype working on the tab 4 for matisse & milet device hit me up on tellgrem @DJABHipHop I can sure use the help with fixing all the little but anoying bugs.
Thenk in advance.
I'm in a desperate state here....unlocked bootloader andtried to flash Pixel ROM....followed all the steps on https://forum.xda-developers.com/poco-f1/how-to/how-to-transform-pocophone-f1-to-pixel-t3910187 except I used the latest version of bellyllium - v10 ( not thinking it would be the wrong one.)
Consequently I am stuck in a bootloop because I have no OS on the phone and can't use MiFlash to flash stock as it keeps telling me to download and install the drivers (which I have).
My phone can do fastboot but I can't adb to it (it isn't listed as a device) so can't push the firmware - any help much appeciated. (btw I'm not new.)
ashboe said:
I'm in a desperate state here....unlocked bootloader andtried to flash Pixel ROM....followed all the steps on https://forum.xda-developers.com/poco-f1/how-to/how-to-transform-pocophone-f1-to-pixel-t3910187 except I used the latest version of bellyllium - v10 ( not thinking it would be the wrong one.)
Consequently I am stuck in a bootloop because I have no OS on the phone and can't use MiFlash to flash stock as it keeps telling me to download and install the drivers (which I have).
My phone can do fastboot but I can't adb to it (it isn't listed as a device) so can't push the firmware - any help much appeciated. (btw I'm not new.)
Click to expand...
Click to collapse
Just put any flashable Rom on a sdcard and install it from twrp, or boot to twrp, Mount storage and connect to computer, transfer ROM and flash.
Skickat från min POCOPHONE F1 via Tapatalk
Zeggi said:
Just put any flashable Rom on a sdcard and install it from twrp, or boot to twrp, Mount storage and connect to computer, transfer ROM and flash.
Skickat från min POCOPHONE F1 via Tapatalk
Click to expand...
Click to collapse
I think my age is catching up to me!!! I knew how to do this easily just 5 or 6 years ago! God it's terrible getting old!!
ashboe said:
I think my age is catching up to me!!! I knew how to do this easily just 5 or 6 years ago! God it's terrible getting old!!
Click to expand...
Click to collapse
Yes the old day only TWRP-ROM-GAPPSS right now TWRP-VENDOR&FIRMWARE-DFE-ROM&GAPPSS Happy flashing
armuttaqin said:
Yes the old day only TWRP-ROM-GAPPSS right now TWRP-VENDOR&FIRMWARE-DFE-ROM&GAPPSS Happy flashing
Click to expand...
Click to collapse
You have forgotten different versions of TWRP apart from official and dm_verity
tnsmani said:
You have forgotten different versions of TWRP apart from official and dm_verity
Click to expand...
Click to collapse
:fingers-crossed: yes my mistake
Are you ok?
i don't know why you can't use adb to flash again twrp?
hoxuanson91 said:
Are you ok?
i don't know why you can't use adb to flash again twrp?
Click to expand...
Click to collapse
Yes, I had a senior moment when I couldn't for the life of me remember what to do. I simply went into TWRP and mounted sd card, transfered new rom and flashed.
Sanatogen tonic for me, please....
ashboe said:
Sanatogen tonic for me, please....
Click to expand...
Click to collapse
xD
ashboe said:
Yes, I had a senior moment when I couldn't for the life of me remember what to do. I simply went into TWRP and mounted sd card, transfered new rom and flashed.
Sanatogen tonic for me, please....
Click to expand...
Click to collapse
Hi Bro, You should put your phone into Fastboot Mode and install twrp through ADB again.
=> Copy Vendor/Rom/gapps/magisk/DFE into your storage.
Wipe advance -> stick: wipe data, cache, davik, systerm (only 4wipe, no more)
Choose Install -> Flash Vendor -> Flash Rom (if you wanna use Pixel rom, don't flash gapps) -> Flash magisk 18.1 -> Flash DFE 18.1 -> Reboot
Sorry if i use english not well.