Related
Update 17 May 2012:
- added "return to stock" section at the end.
Update 17 Apr 2012:
- kernel has been successfully tested on a P-7320. 4 days, 0 problems!! =). thanks for testing and reporting go to androidpetruska! removed the warnings. =)
post can be found here.
Update 16 Apr 2012:
- re-uploaded all files... somehow the links were broken...
Update 15 Apr 2012:
- [kernel] [usb charging] fixed the charging status reported to the system => now v0.3. please find more detailed information here: http://forum.xda-developers.com/showpost.php?p=24889247&postcount=19
Update 11 Apr 2012:
- [kernel] [usb charging] fixed unplug/reconnect "bug" => now v0.2
- [kernel] sources added.
Click to expand...
Click to collapse
Hi everyone,
Here you will find CWM Recovery 5.5.0.4 for the P7320 / P7320T along with rooting instructions - and a usb-charging-enabled kernel. Recovery and kernel have been tested on the P7320 and the P7320T.
I hope this thread helps to let the 7320 development gain some momentum!
Install CWM Recovery
1. Download Odin and the Samsung Drivers. Both are included in the GTab89Files.zip from nirogu325's guide here: http://forum.xda-developers.com/showpost.php?p=20586389&postcount=1 (You'll find it under "Download Pack".)
If you are new to this whole rooting thing, I strongly recommend to read his FAQ section before proceeding!
DO NOT USE the recoveries included. Just extract the "Odin" and the "Driver" folders.
2. Download the cwm recovery for the 7320 here: View attachment P7320T_cwm_recovery_alpha.zip and unzip it.
3. You can check if you have correct drivers installed by trying step 4 and 5 first. If Odin does not recognize your device, install the driver (SAMSUNG_USB_Driver_for_Mobile_Phones.exe).
4. Put your device in "Download-Mode": switch it off, hold volume down (the left volume key) and power until you're asked if you want to continue what you confirm by pressing volume up (the right volume key). Alternatively you can put it in download mode with a simple "adb reboot download" if you have usb-debugging enabled and adb installed...
5. Connect your device DIRECTLY to your PC and open Odin as administrator. You should see a yellow field (ID:COM/ some values). If not your tablet is not recognized correctly and you probably need to reinstall the drivers.
6. click on "PDA" and select "P7320T_cwm_recovery_alpha.tar.md5". LEAVE EVERYTHING ELSE AS IT IS. (only "Auto Reboot" and "F.Reset Time" should be checked) and then...click on "Start".
Flashing should be finished within a second or so.
You can enter recovery mode by switching off the tablet, then holding the right volume key and pressing power until it vibrates or use "adb reboot recovery".
How to root your device
After cwm installation, rooting your device is pretty straight forward:
1. Download Superuser.zip: View attachment Superuser-3.0.7-efghi-signed.zip
2. Put it on your sdcard.
3. Start cwm recovery as described above.
4. Select "install zip from sdcard" -> "select zip from sdcard"->"Superuser-3.0.7-efghi-signed.zip" and confirm selection by choosing "Yes - Install ....."
Step 4 may abort with some error, but if you repeat it for maybe 2,3 or even 4 times, it will finish successfully.
Your phone is now rooted.
Enable usb charging
Here is the usb-charging-enabled kernel I promised yesterday. It's based on the Samsung GT-P7320T Kernel for HC. USB charging is based on pershoot's kernel for the galaxy tab 10.1. thanks for providing the sources. Everything is working (wlan, bluetooth, camera,etc).
usb charging is enabled by default.
Installing the kernel
1. although I have also made a cwm flashable zip containing the stock kernel for the 7320T please do a full system backup before messing around with your tab.
2. download the modified kernel: View attachment signed_GTP7320T_glitschis_kernel_v_0_3.zip
3. optional: download the stock kernel from here: View attachment signed_GTP7320T_stock_kernel_dvlb2.zip
4. put the file(s) on your sdcard.
5. start into CWM recovery (again: as described above)
6. Select "install zip from sdcard" -> "select zip from sdcard"->"signed_GTP7320T_glitschis_kernel_v_0_3.zip" and confirm selection by choosing "Yes - Install ....." to install the kernel. (reverting to stock also works this way, just choose the stock kernel zip (see 3.))
6. restart the tab.
Disable usb charging (Why??!!?)
If you have adb installed, it can be turned off with following command:
Code:
adb shell
su
echo 0 > /sys/class/power_supply/battery/force_usb_charging
and turn it on again:
Code:
adb shell
su
echo 1 > /sys/class/power_supply/battery/force_usb_charging
Both commands will take effect after unplugging and reconnecting your device. And the setting will be lost after reboot.
Does anybody know a widget that does exactly that? - including showing the current status???
return to stock
There are two possible ways:
- Find a stock rom and install it with odin, that will reset you whole device...
- Or follow the steps described below, to remove superuser, the kernel and the cwm recovery. Everything else will stay as it is.
1. Download View attachment signed_superuser_uninstall.zip and put it on your sdcard.
1b. If you also installed the kernel, please find the stock kernel download link above and put the file on your sdcard.
2. Start into CWM recovery (again: as described above)
3. Select "install zip from sdcard" -> "select zip from sdcard"->"signed_superuser_uninstall.zip" and confirm selection by choosing "Yes - Install ....."
3b. now is the time to flash the stock kernel, in case you have flashed the custom kernel.
4. Reboot your device and put it into download mode.
5. Download View attachment stock_recovery_7320.zip. Unzip and install with Odin - exactly the same way you installed the cwm recovery before.
If you encounter any problems or have feature requests, please report them. Any feedback is highly appreciated!
as requested, I've created a github account and uploaded the sources: https://github.com/glitschi/kernel_P7320
credits:
go to koush for cwm sources,to utkanos for his i957 port, to kershoot for his usb charging patch, to chainfire for Superuser.zip, to suwandiapr for providing the factory image, to nirogu325,to EndoSurf, to orlandoxpolice, and to everybody else testing! and xda for hosting so much useful information!
cheers,
glitschi
Finally you post it.. Thank you!!
If i want to enable usb charging do i need to root my device?
Is there a zip file i can flash to enable usb charging?
@suwandiapr: was kind of busy, and it's my first tutorial, it took some time to do it..... sorry for the delay....
@ay33ta: I've searched a bit, and it seems we need a little kernel mod for usb charging - if I understand it correctly..... I'll try to do that within the next days... In case it's going to be available, you need to root your device in order to flash the new kernel.
edit: you need cwm recovery for flashing the kernel and root to enable usb charging.....
very nice.
do you 7320 guys have any leads on development for ROMS?
Putting recovery and root on my device worked fine. Thank you.
Now i would like to know how to enable usb charging if anyone knows. Thanks
You need to flash a kernel which has this feature build in, since the stock kernel does not allow charging on USB.
I have a USB charging enabled kernel here for almost 2 days now, but the camera was not working - until an hour ago.
It was kind of hard and kept me working long hours figuring out what was going on there, and I almost gave up, thinking samsung released non working source.... (what they actually did, but it took 4 lines of code to get it working finally....)
I still have to do some testing. But if everything looks good, I'm going to release a cwm flashable zip containing the new kernel within the next hours. Along with a guide how to install it and enable USB charging.
cheers,
glitschi
update: lots of other stuff to do..... will post tomorrow.....
update2: updated! see post #1
orlandoxpolice said:
very nice.
do you 7320 guys have any leads on development for ROMS?
Click to expand...
Click to collapse
not yet, as far as I know... anything we can do about?
glitschi667 said:
not yet, as far as I know... anything we can do about?
Click to expand...
Click to collapse
some ICS leaks are out for snapdragon devices, i would suggest starting there
Thanks for the new kernel, working great so far. I am bouncing the USB settings using gscript with tasker and displaying the setting by a variable in a minimalist text widget.
I would like to get a copy out the kernel source code.
Sent from my GT-P7320T using Tapatalk
super user link
The superuser download link is broken
uploaded all files to xda and updated the links, should be working now.
will post new kernel version (no unplug needed for usb charging) and the sources later today.
sorry for the delay.... was away for the holidays......
cheers,
glitschi
glitschi667 said:
will post new kernel version (no unplug needed for usb charging) and the sources later today.
Click to expand...
Click to collapse
Bought my lte-pad 10 days ago, already loving it more than my GalaxyS2. The usb-charging is the only thing to dissapoint. Thank you for fixing it, and providing a working CWM.
-Doc
nice to hear that! =). you are welcome!
so you can confirm the kernel is working with the GT-P7320 without the "T" at the end?
new kernel version and sources available! updated post #1.
enjoy,
glitschi
glitschi667 i have put cwm and superuser on my 8.9 tab i know that i have root. Now when i flash 0.2 usb charging kernel through cwm and reboot usb charging still doesnt work.
Am i doing something wrong? The file flashes fine.
Have you got the charging symbol with an X? If so it is charging, but slowly (this is what mine does).
i have a red x when using a apple usb charger but when you use official charger came with it i get a white x.
When i had my 10.1v i had the same problem. I rooted it and put on one of preshoot kernel/roms and it would charge fine with a apple charger, this is what im hoping to do with my 8.9.
Thanks for the work so far.
i wouldnt use an apple charger
I did some research regarding the charging and reporting to the system:
- the tab consumes around 500mA with minimum brightness set and 900mA - 1000mA with brightness set to max. even more if you play a game or something....
- the stock kernel only provides 500mA when charging over usb and (theoretically) 2000mA when connected to the samsung charger (I had just about 1700mA reported by the kernel...)
- with the modified kernel and usb charging enabled, the device can take up to 2000mA over usb or any other charger.
- v0.2 has still the same reporting as the stock kernel. If the device is connected over usb, it just reports that it is "Discharging". But with usb_charging enabled it is just the reporting that is wrong.
Now I've done some changes to the kernel:
If the tab is connected over usb, the kernel checks if more power is available than consumed. In this case, it reports "Charging" to the system. If the battery is full, it also reports that. But if the consumption is higher than what is provided, it reports "Discharging" and the red X will appear. This is checked every 30seconds. You can check the reported values by going to Settings->About device->Status.
Now you can see, if you consume more power than provided, but (as on stock kernel) you cannot see, how fast the tablet is charging.
You may notice, that after reboot or a newly inserted usb cable, it might display "Discharging" since the power consumption values need some time to adjust, but the correct value will be shown after ~30seconds.
If you want to check the power consumption values, you can find them in the kernel log.
Code:
adb shell dmesg | grep read_current
will provide you with the values you are interested in:
Code:
<6>[ 2820.576049] fg_read_current : CURRENT(352mA), AVG_CURRENT(329mA)
<6>[ 2821.449310] fg_read_current : CURRENT(-653mA), AVG_CURRENT(298mA)
negative means "discharging", positive values "charging". So if you disconnect it, the -653 should be the power consumption of the tablet. if you reconnect it and a value of 352 is reported, the output of your usb-port should be around 1000mA.
if somebody is interested, I wrote a little app to keep track of these kernel messages, but it is still a bit buggy, so I won't release it right now - but you can write me a pm...
cheers,
glitschi
ps. going to update post #1
What happened to the attachments?
The attachments seemed to have disappeared...
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
CHANGELOG 2.8.1.0
- MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
- TrueType Font support - optional as it takes up a decent amount of space so may not be available on all devices - thanks to Tassadar
- Temperature support - thanks to bigbiff
- Various other bugfixes and tweaks
CHANGELOG 2.8.0.1
- Fix a bug that caused weird graphics and touch issues
CHANGELOG 2.8.0.0
- Fix a bug that caused weird graphics and touch issues
- Add MTP support to recovery thanks mostly to bigbiff with a little help from Dees_Troy
- Add command line capabilities - you can now execute various TWRP features via adb instead of the touchscreen
- Add support for color in the console and give error, warning, and highlight lines different colors
- Track backup and restore progress based on file sizes to provide a much more accurate indication of progress
- Improve handling of /misc thanks to mdmower
- Improve setting of time on Qualcomm devices thanks to [NUT]
- Allow using images on slidervalue GUI objects thanks to Tassadar
- Allow using variables and addition and subtraction in variables for easier theming
- Add support for 1440x2560, 280x280, and 320x320 resolutions and update 240x240
- Allow ui.xml file to include additional xml files to help break up the theme and make TWRP easier to maintain
- Other minor fixes and improvements
BUGS:
- Off mode charging.
INFORMATION:
2014-11-04
- Fixed capacitive buttons
- Fixed MTP
2014-10-26
- TWRP version 2.8.1.0
2014-10-15
Today (2014-10-15) I announce a build with F2FS support, today's and upcoming build's will have support for F2FS file system. Read more about F2FS from post #10
DOWNLOAD:
TWRP_2.8.1.0-20141104-u8800.zip - Link removed because of problems with wiping /data and /cache.
TWRP_2.8-20141029-testbuild2-u8800.zip
Looking for the u8800pro or u8860 version?
They can be found here: [RECOVERY] TWRP 2.8.1.0 recovery for u8800pro/u8860
Last Updated: 2014-11-04
hi, i am with blefish´s rom and this recovery seems to work at least when i done a backup/recovery rom thanks mate
pl4t!n said:
hi, i am with blefish´s rom and this recovery seems to work at least when i done a backup/recovery rom thanks mate
Click to expand...
Click to collapse
Great could you test off mode charging too? Is there charging animation?
I don't think off mode charging works. This version behaves as previous TWRP versions. When the device is connected power off just reboots it to recovery again.
Also mtp doesn't seem to work. No prompt to install any driver on pc and no folders for internal external sd as happens in normal mode.
dancer_69 said:
I don't think off mode charging works. This version behaves as previous TWRP versions. When the device is connected power off just reboots it to recovery again.
Also mtp doesn't seem to work. No prompt to install any driver on pc and no folders for internal external sd as happens in normal mode.
Click to expand...
Click to collapse
Did you tested it? I made some changes so can you test this: http://www.mediafire.com/download/0xdf40ebilob6zz/TWRP_2.8.0.0-2014108-test-u8800.zip and report?
Yes I did. The link you provide is newer?
EDIT:
I tested the version you provided and there is no difference. Device still reboots to recovery when press power off button, and MTP doesn' t work. Also either if I enable or disable MTP from the button I hear the disconnect/don't recognized sound from windows. I can run adb and adb shell command though.
Also in both versions the device's touch buttons are always lighten, and don't work. I can use only recovery's home and back buttons but the device's buttons don't work. In fact none of the device' s buttons work. Only the "power" button activates the lock screen.
dancer_69 said:
Yes I did. The link you provide is newer?
EDIT:
I tested the version you provided and there is no difference. Device still reboots to recovery when press power off button, and MTP doesn' t work. Also either if I enable or disable MTP from the button I hear the disconnect/don't recognized sound from windows. I can run adb and adb shell command though.
Also in both versions the device's touch buttons are always lighten, and don't work. I can use only recovery's home and back buttons but the device's buttons don't work. In fact none of the device' s buttons work. Only the "power" button activates the lock screen.
Click to expand...
Click to collapse
Hi
Guess we need to wait until the bugs are fixed as I too am on blefish CM11 rom
Thanks Dancer_69 for taking the risk and the update on the recovery bugs.
cheers
dancer_69 said:
Yes I did. The link you provide is newer?
EDIT:
I tested the version you provided and there is no difference. Device still reboots to recovery when press power off button, and MTP doesn' t work. Also either if I enable or disable MTP from the button I hear the disconnect/don't recognized sound from windows. I can run adb and adb shell command though.
Also in both versions the device's touch buttons are always lighten, and don't work. I can use only recovery's home and back buttons but the device's buttons don't work. In fact none of the device' s buttons work. Only the "power" button activates the lock screen.
Click to expand...
Click to collapse
Thanks man. Have there ever been a recovery where the off mode charging have been ok? Do you see only "Unknown device" in the Window's Device manager? Yes, the buttons are always lighten. Would you like a non-lighted buttons better? "Back" button should be only functioning one of the device buttons. I'll check these issues..
Lihis said:
Thanks man. Have there ever been a recovery where the off mode charging have been ok? Do you see only "Unknown device" in the Window's Device manager? Yes, the buttons are always lighten. Would you like a non-lighted buttons better? "Back" button should be only functioning one of the device buttons. I'll check these issues..
Click to expand...
Click to collapse
Off mode charging is not working because bootloader don't allow it. We have to wait for blefish release it's modified bootloader.
Support for F2FS file system
Added support for F2FS file system.
What is F2FS file system?
F2FS (Flash-Friendly File System) file system is a flash file system initially developed by Samsung Electronics for the Linux operating system kernel (source). Here is some benchmark made with Xperia Z1 [Benchmarks] File System Performance: F2FS vs EXT4.
For now there is no ROM which uses F2FS file system but in future there may be.
can´t install it, "recovery partition could not be foud". What's the problem?
Anyway, can you make a flashable zip file?
vitorugo-8 said:
can´t install it, "recovery partition could not be foud". What's the problem?
Anyway, can you make a flashable zip file?
Click to expand...
Click to collapse
How you are trying to install the recovery? I consider about that.
Lihis said:
How you are trying to install the recovery? I consider about that.
Click to expand...
Click to collapse
Flashify and twrp app, both gave me that partition error... also when trying to install the cm11 unoficial rom and others i get the status 7 error on the cwm recovery. That's why i'm trying to install twrp recovery
vitorugo-8 said:
Flashify and twrp app, both gave me that partition error... also when trying to install the cm11 unoficial rom and others i get the status 7 error on the cwm recovery. That's why i'm trying to install twrp recovery
Click to expand...
Click to collapse
TWRP is not officially supported for our device and I have not never used TWRP app so.. I own a u8800pro so I can't say 100% sure how you can replace your recovery, but I'm sure you can find it by searching this forum. By the way, pink screen is a common way to change recovery at least on u8800pro, maybe in u8800 too?
vitorugo-8 said:
Flashify and twrp app, both gave me that partition error... also when trying to install the cm11 unoficial rom and others i get the status 7 error on the cwm recovery. That's why i'm trying to install twrp recovery
Click to expand...
Click to collapse
its seems to me that your error is because you need to increase you system with [PARTITION] BlePart [v2.x] http://forum.xda-developers.com/showthread.php?t=2615712 and after that you already can install blefish´s cm 11 rom http://forum.xda-developers.com/showthread.php?t=2616956
before you do anything, please read carefully see if you have the all the necessary requirements to do this
Hey Guys,
Is this recovery STABLE now. I'm on TWRP 2.7 so want to make sure before I change
thnx for the help
mohammad.nomaan said:
Hey Guys,
Is this recovery STABLE now. I'm on TWRP 2.7 so want to make sure before I change
thnx for the help
Click to expand...
Click to collapse
Could you test it? I got report that flashing and backup/restore is OK but MTP is broken?
Lihis said:
Could you test it? I got report that flashing and backup/restore is OK but MTP is broken?
Click to expand...
Click to collapse
Hi
I can try but not before Saturday as my phone is with my brother who is away until then.
Will install, check and revert by Sunday.
thnx
TWRP version 2.8.1.0 now available. OP updated.
Lihis said:
TWRP version 2.8.1.0 now available. OP updated.
Click to expand...
Click to collapse
what is the changelog for this update?
Hello everybody !
I 've spend a long time on this forum and i've found a lot of interesting and useful tips.
I'm in a bad situation today and I can not find a solution so i thank you for the time spent reading this.
Yesterday i've seen an icon on my desktop and i couldn't remember what application it is. I clicked and it was the beginning of an endless nightmare... A huge lag began by making the phone unusable and apps was installing one after one...
When it has calmed down a bit, i tried to install cleaning softwares but i couldn't do anything so I tried to do a factory reset. After that... the malware was still here... So i've decided to clean all by installing a new ROM.
This is a Jiayu S3 4G 5.5 Inch MT6752 Octa Core RAM 3GB 1080P Screen Dual SIM 4G LTE Mobile Phone (invoice description) so i wanted to try the CM12.1 for Jiayu S3 (found on needrom).
My phone was Rooted and TWRP was installed so i've copied the ROM files on a SD card, rebooted in recovery mode, wiped cache, data, dalvic and system and tried to install the new ROM. it was abnormally rapid and now the phone bootloops.
The only thing i can do is activate Fastboot (if i choose normal boot or recovery it continues to bootloop).
I've tried to flash recovery with :
fastboot flash recovery recovery.img
but i get an error message : FAILED (remote : partition 'recovery' not support flash).
Does anyone has ever been in this situation and solved it ?
Thanks for your help !
Hello,
I got exactly the same problem. Did you find a solution?
My phone is in a bootloop, I can only access to the fastboot mode. (fastboot devices show my device).
In this mode, I can't flash my recovery.img:
fastboot flash recovery recovery.img --> partition 'recovery' not support flash.
I can't see my device with the command adb devices (adb devices doesn't show my device, I think because USB debugging is off, but i can't switch it on)
Did someone find a solution ?
Any help would be appreciated, thanks !
That's the behavior of a wrong preloader that was flashed / malware that affected preloader.
Grab a full spftools ROM set, and flash the entire ROM using " upgrade mode"
Cheers
PS: on s3 you need to have both volume buttons pressed, then you can press download on the spft.
PPS: this will destroy all of your data, so back it up first ..
Thanks for your answer.
So, I downloaded latest version of Flash_Tools, but i can't find any complete set for flashing... only recovery.img (I'm searching on needrom.com). Do you have a place to find these?
>PS: on s3 you need to have both volume buttons pressed, then you can press download on the spft.
I think i got another problem: with Flash_Tools, I'm unable to flash anything to my device... There is a special mode to launch, as you explained, but it seems I can't access it... By pressing both up and down volume button, the phone should boot on a special mode ? How can I know if the phone is booted in this mode ? The USB cable must be plugged before/after booting the phone in this mode ?
mick605 said:
Thanks for your answer.
So, I downloaded latest version of Flash_Tools, but i can't find any complete set for flashing... only recovery.img (I'm searching on needrom.com). Do you have a place to find these?
>PS: on s3 you need to have both volume buttons pressed, then you can press download on the spft.
I think i got another problem: with Flash_Tools, I'm unable to flash anything to my device... There is a special mode to launch, as you explained, but it seems I can't access it... By pressing both up and down volume button, the phone should boot on a special mode ? How can I know if the phone is booted in this mode ? The USB cable must be plugged before/after booting the phone in this mode ?
Click to expand...
Click to collapse
There is no special mode, please serach the forum on how to use sptools, i am sure you will find plenty of them.
Sorry for late answer !
Thanks for this advice, i will try as soon as possible and post if it's ok or not.
Hello everybody !
Ok, I got it !
My problem came from the drivers... But not the ADB drivers, the preloader drivers.
In the Windows device manager, when I plugged my phone (previously swithced off), I got a "MT65xx Preloader" device with a warning. Be careful, this item stay 2 or 3 seconds before disappearing ! This driver wasn't installed correctly, that's why Flash Tools didn't worked for me (it didn't see my phone) !
So, I got the driver on the web, by typing "MT65xx Preloader driver", I got the drivers that I installed. This guide gave me the files and a method to install them:
http: //laurentiumihet.ro/sp-flash-tool-mediatek-mt65xx-drivers-download-and-installation-guide-including-bricked-devices/ (can't post links, delete space after http: )
To install the driver, you can set up manually by right clicking on the "MT65xx Preloader" > "Update drivers". Then, browse to the drivers you previously downloaded (a folder containing .inf and .sys files). Windows should detect the driver and install it.
To check if the preloader driver is correctly installed, power off your phone and unplug it, them plug it. Instead of the previous "MT65xx Preloader" entry, you should now see a "MediaTek PreLoader USB VCOM Port" under "Ports (COM & LPT)" (same as before, this item is displayed only 2-3 seconds...).
Now that the preloader driver is correctly installed, Flash Tools works for me. I successfully flashed a new rom I got from needrom.com (a full set, as suggested by superdragonpt), and my phone boots now =)
Thanks all for your answers ! Xehon, hope it will works for you !
Thanks mick605 !
I travel for work so i can't try all the advices on this forum atm.
I'll check this when i get back home and i'll tell you if it's ok
Thanks again !
mick605 said:
Hello everybody !
Ok, I got it !
My problem came from the drivers... But not the ADB drivers, the preloader drivers.
In the Windows device manager, when I plugged my phone (previously swithced off), I got a "MT65xx Preloader" device with a warning. Be careful, this item stay 2 or 3 seconds before disappearing ! This driver wasn't installed correctly, that's why Flash Tools didn't worked for me (it didn't see my phone) !
So, I got the driver on the web, by typing "MT65xx Preloader driver", I got the drivers that I installed. This guide gave me the files and a method to install them:
http: //laurentiumihet.ro/sp-flash-tool-mediatek-mt65xx-drivers-download-and-installation-guide-including-bricked-devices/ (can't post links, delete space after http: )
To install the driver, you can set up manually by right clicking on the "MT65xx Preloader" > "Update drivers". Then, browse to the drivers you previously downloaded (a folder containing .inf and .sys files). Windows should detect the driver and install it.
To check if the preloader driver is correctly installed, power off your phone and unplug it, them plug it. Instead of the previous "MT65xx Preloader" entry, you should now see a "MediaTek PreLoader USB VCOM Port" under "Ports (COM & LPT)" (same as before, this item is displayed only 2-3 seconds...).
Now that the preloader driver is correctly installed, Flash Tools works for me. I successfully flashed a new rom I got from needrom.com (a full set, as suggested by superdragonpt), and my phone boots now =)
Thanks all for your answers ! Xehon, hope it will works for you !
Click to expand...
Click to collapse
First of all hi I'm new in this thread,
I have installed everything correctly but I still have only 3 seconds before my phone showes the the charging icon and disconnects.
Can anybody please help me? I actually have been stuck with this problem for months now and all these months I have been using the samsung galaxy s advance (launched in 2011) on marshmallow.
Anyone using Heimdall with this device I do not have Windows so Linux it is and cannot get Heimdall to extract .pit file from sm-t350 thanks
joeeboogz said:
Anyone using Heimdall with this device I do not have Windows so Linux it is and cannot get Heimdall to extract .pit file from sm-t350 thanks
Click to expand...
Click to collapse
I used Heimdall to root my sm-t580 using Ubuntu. Under the utilities tab, click on Detect, and you should see the Device Detected radio button selected, as well as Device Detected in the output box. Then under Download PIT, click on save as. A dialog box opens so that you can select a destination and name the file. Navigate to the folder of your choice, name the file and click on save. Once the dialog box closes, click on the Download button. You can monitor the progress in the output box. Hope this helps and let me know if need any help. I'll do my best.
Sent from my SM-T580 using Tapatalk
db1911 said:
I used Heimdall to root my sm-t580 using Ubuntu. Under the utilities tab, click on Detect, and you should see the Device Detected radio button selected, as well as Device Detected in the output box. Then under Download PIT, click on save as. A dialog box opens so that you can select a destination and name the file. Navigate to the folder of your choice, name the file and click on save. Once the dialog box closes, click on the Download button. You can monitor the progress in the output box. Hope this helps and let me know if need any help. I'll do my best.
Sent from my SM-T580 using Tapatalk
Click to expand...
Click to collapse
Hello
I use gentoo linux and I have SM-T580 tablet also.
Can you please be more specific on which heimdall version you used? Where you got the package in ubuntu? is this in the standard repos?
Is this safe to root my tablet. I need twrp most likely I suppose
__roman__ said:
Hello
I use gentoo linux and I have SM-T580 tablet also.
Can you please be more specific on which heimdall version you used? Where you got the package in ubuntu? is this in the standard repos?
Is this safe to root my tablet. I need twrp most likely I suppose
Click to expand...
Click to collapse
For flashing TRWP, I started here.
This post motivated me to build the packages myself rather than use the repo versions.
There are instructions for building your own packages along with the source files here
Once you launch Heimdall, the process is pretty much the same as in Odin. This page is also good for reference.
Make sure you follow the steps in the XDA guide. My first time through, I made some mistakes and was stuck in a bootloop after flashing SuperSU. It wasn't too difficult to fix everything and start over. Second time around, I followed all of the steps and everything worked perfectly. TWRP goes into the recovery partition using Heimdall.
Are you looking to flash a ROM after you install TWRP?
Thank you for your fast response.
About myself: So far I have a nexus 7 with broken charging port. while fixing i cracked the digitizer. I classified it as not fixable. I have two nexus 4 phones where I need to replace soon the digitizer. I'm used to fastboot and adb. the nexus 4 was my first smartphone. I went through all the android 4 and upwards custom rom things on my nexus 4.
I have no idea how odin works. As I use for a long time only linux. this is my first samsung android based device
Yes I am looking for a custom ROM later. Any suggestion? I also need some solution for the annoying ads in youtube and google chrome!
Any recommendation, as you have the same device?
-- building from source should not be an issue. gentoo is a source based distro. the compiler toolchain is working
thank you
__roman__ said:
Thank you for your fast response.
About myself: So far I have a nexus 7 with broken charging port. while fixing i cracked the digitizer. I classified it as not fixable. I have two nexus 4 phones where I need to replace soon the digitizer. I'm used to fastboot and adb. the nexus 4 was my first smartphone. I went through all the android 4 and upwards custom rom things on my nexus 4.
I have no idea how odin works. As I use for a long time only linux. this is my first samsung android based device
Yes I am looking for a custom ROM later. Any suggestion? I also need some solution for the annoying ads in youtube and google chrome!
Any recommendation, as you have the same device?
-- building from source should not be an issue. gentoo is a source based distro. the compiler toolchain is working
thank you
Click to expand...
Click to collapse
You're welcome. Let me know if you run into any issues. I only mentioned Odin because many of the instructions refer to it rather than Heimdall. Though they serve much the same function, they are not identical. I've been using Linux only myself now for several years.
Sounds like we've talked similar Tech paths. I had a Nexus 7 that eventually died because of a cracked digitizer after I had repaired the charging twice. I also had bought Nexus 4 for my family members and ended up changing a few cracked screens. You get the hang of it after a while.
I haven't yet had time to load a custom ROM on my Samsung tablet. I hope to have the time in the next few days. I want to get a copy of the stock ROM in case I'm not happy with whatever I flash. I'll let you know d what I end up with. Maybe you can share what you end up using too.
Sent from my SM-T580 using Tapatalk
can you post the errors you get while using heimdall? are you using the GUI frontend or just the CLI command line heimdall?
I use the command line since the GUI makes my head spin
$ heimdall print-pit
^ will print PIT to shell screen
gian20 said:
can you post the errors you get while using heimdall? are you using the GUI frontend or just the CLI command line heimdall?
I use the command line since the GUI makes my head spin
$ heimdall print-pit
^ will print PIT to shell screen
Click to expand...
Click to collapse
I used the GUI. The verbose mode (standard selection I believe) displayed the progress nicely. I'll try to grab some screenshots for you.
Sent from my SM-T580 using Tapatalk
What I hate the most, TWRP guys are unable to add SM-T580 to their pages.
MY amazon purchase says: Samsung Galaxy Tab A (2016) T580 25,54 cm (10,1 Zoll) Wi-Fi Tablet-PC (Octa-Core, 2GB RAM, 16GB eMMC, Android 6.0, neue Version) weiß
the url in your guide is dead: https://teamw.in/devices/samsunggalaxytaba101wifi2016.html
says: "404 Not Found; nginx/1.10.3 (Ubuntu)"
new url: https://twrp.me/samsung/samsunggalaxytaba101wifi2016.html
I assume Code Name: gtaxlwifi = SM-T580
on bottom there is noted
Changelog:
James Christopher Adduono
2016-08-11T19:02:43Z
Import SM-T580 TWRP kernel Image and dtb.img (1.0) Change-Id: Ib3aec1f34a684e087200f0de78b260def007a334
Click to expand...
Click to collapse
--
Device => Settings => Lock screen and security => changed screen lock type to NONE
Device => Settings => Cloud and accounts => I removed everything (The reason was the warning that I may brick my device when It is linked to my existing google account)
–
Wrong: https://forum.xda-developers.com/ga...overy-official-twrp-gtaxlwifi-galaxy-t3437666
Quote: Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Home] buttons while your device reboots.
right: https://www.android-hilfe.de/forum/...sm-t585-samsung-galaxy-tab-a-2016.788225.html
quote: Drücke [Power], wähle Neustart und drücke dann sofort folgende Knöpfe:
[power + vol down + home]
Translates to reboot your device. than press [power + vol down + home]. the xda link misses to also press power
3) Issue "heimdall flash --RECOVERY <recovery.img>" to flash in the same manner as with ODIN on Windows.*
Click to expand...
Click to collapse
–
[email protected] ~/Heimdall/build/bin $ ./heimdall flash --RECOVERY twrp-3.2.1-0-gtaxlwifi.img
Heimdall v1.4.2
Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
100%
RECOVERY upload successful
Ending session...
Rebooting device...
Releasing device interface…
–
Click to expand...
Click to collapse
It seems heimdall works as ordinary user ROMAN. Not superuser on my gentoo box.
The "heimdall print-pit " prints the memory areas and htan reboots my box
How do I enter TWRP?
I assume TWRP is not installed I can not enter it
The stock rom is still in use. The tablet still boots
During bootup
POWER + volume down + Home button => same "odin flash screen" as it was
assume: Power + volume up + home button => seems stock samsung recovery?
When I do as User ROMAN in gentoo linux
[email protected] ~ $ adb reboot recovery
I get the same "Samsung RECOVERY". I assume it is the SAMSUNG recovery.
twrp file checksum was verified of course before using it.
heimdall was build from source. the instructions were clear. gentoo has a working compiler chain, no issues
i just did not copy it to the bin folder the exectute ables, as i dislike putting not package manager maintained files into /bin folder. very bad practise
--
I waited a bit before I tried doing it. I assume TWRP was not written to the device so far.
__roman__ said:
What I hate the most, TWRP guys are unable to add SM-T580 to their pages.
MY amazon purchase says: Samsung Galaxy Tab A (2016) T580 25,54 cm (10,1 Zoll) Wi-Fi Tablet-PC (Octa-Core, 2GB RAM, 16GB eMMC, Android 6.0, neue Version) weiß
the url in your guide is dead: https://teamw.in/devices/samsunggalaxytaba101wifi2016.html
says: "404 Not Found; nginx/1.10.3 (Ubuntu)"
new url: https://twrp.me/samsung/samsunggalaxytaba101wifi2016.html
I assume Code Name: gtaxlwifi = SM-T580
on bottom there is noted
--
Device => Settings => Lock screen and security => changed screen lock type to NONE
Device => Settings => Cloud and accounts => I removed everything (The reason was the warning that I may brick my device when It is linked to my existing google account)
–
Wrong: https://forum.xda-developers.com/ga...overy-official-twrp-gtaxlwifi-galaxy-t3437666
Quote: Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Home] buttons while your device reboots.
right: https://www.android-hilfe.de/forum/...sm-t585-samsung-galaxy-tab-a-2016.788225.html
quote: Drücke [Power], wähle Neustart und drücke dann sofort folgende Knöpfe:
[power + vol down + home]
Translates to reboot your device. than press [power + vol down + home]. the xda link misses to also press power
–
It seems heimdall works as ordinary user ROMAN. Not superuser on my gentoo box.
The "heimdall print-pit " prints the memory areas and htan reboots my box
How do I enter TWRP?
I assume TWRP is not installed I can not enter it
The stock rom is still in use. The tablet still boots
During bootup
POWER + volume down + Home button => same "odin flash screen" as it was
assume: Power + volume up + home button => seems stock samsung recovery?
When I do as User ROMAN in gentoo linux
[email protected] ~ $ adb reboot recovery
I get the same "Samsung RECOVERY". I assume it is the SAMSUNG recovery.
twrp file checksum was verified of course before using it.
heimdall was build from source. the instructions were clear. gentoo has a working compiler chain, no issues
i just did not copy it to the bin folder the exectute ables, as i dislike putting not package manager maintained files into /bin folder. very bad practise
--
I waited a bit before I tried doing it. I assume TWRP was not written to the device so far.
Click to expand...
Click to collapse
In order to boot into TWRP, you need to restart the device then hold power, volume up and home.
Sent from my SM-T580 using Tapatalk
db1911 said:
In order to boot into TWRP, you need to restart the device then hold power, volume up and home.
Sent from my SM-T580 using Tapatalk
Click to expand...
Click to collapse
When I hold Power + volume up + home the device starts and instantly turns it off. For some reason holding power turns the device off now during the cold boot phase, which was never the case before.
When I use a soft reboot with Power + volume up + home I get a blue screen with a white android man symbol. Which is definitely not TWRP.
As said i know how twrp looks alike. i used twrp with nexus 4 and nexus 7.
i am quite certain that heimdall did not wrote twrp. or for some reason the stock recovery is written back.
Which also indicates my comment => adb reboot recovery gave me also teh blue background with the white man. Which seems to be the stock samsung recovery.
And
https://www.android-hilfe.de/forum/root-custom-roms-modding-fuer-samsung-galaxy-tab-a-2016-10-1.3054/root-sm-t580-sm-t585-samsung-galaxy-tab-a-2016.788225.html
Clearly states in german which button is which button. There is no mixup possible in my case!
the heimdall gui only accepts gz files. means these are some compressed files. in the pull down menu.
so i used the cli software.
--
I updated before a few days ago the tablet operating system. after 4 -5 months without an update. I got outdated android security patchsetof 1 december 2017 with outdated antique android 7.0
Build number NRD90M. T580XXU2BQL1 = official samsung update.
502 history|grep heimdall
503 ls -alh
504 ./heimdall detect
505 ./heimdall flash --RECOVERY twrp-3.2.1-0-gtaxlwifi.img
506 adb reboot recovery
507 ./heimdall flash --RECOVERY twrp-3.2.1-0-gtaxlwifi.img
508 heimdall
509 ./heimdall --help
510 ./heimdall flash --RECOVERY twrp-3.2.1-0-gtaxlwifi.img --no-reboot --usb-log-level debug
511 ./heimdall flash --RECOVERY twrp-3.2.1-0-gtaxlwifi.img --no-reboot
512 ./heimdall flash --RECOVERY twrp-3.2.1-0-gtaxlwifi.img
513 ls
514 ./heimdall flash --RECOVERY /home/roman/Heimdall/build/bin/twrp-3.2.1-0-gtaxlwifi.img
515 ./heimdall
516 ./heimdall print-pit
Click to expand...
Click to collapse
I am not sure where the issue is.
I had issues with kernel 4.14.10, latest stable on kernel.org. My usb printer did also not work. Same config worked since over ~9 years. Same gentoo, different notebooks.
I reverted now to 4.9.73
I suppose also the "--no-reboot " is essential.
Than because the device will refuse to power off. Press Power + (volume up or down (not sure honeslty) + home button,
which rebooted the device, and instantly press the key combo for TWRP.
TWRP shoes up the first time with the following:
TWRP screen.
bla bla ... TWRP will be unable to prevent the stock ROM from replacing TWRP and will not offer to root your device
=> this was exactly the issue I had. stock rom seems to replace TWRP
I assume, which is not that clear. => Swipe to allow modifications.
--
[email protected] ~ $ adb reboot recovery
Click to expand...
Click to collapse
does as expected now reboots into TWRP with some delay. I ssume it is not the cpu, it is the firmware which does some checks now.
---
As said this is my first SAMSUNG android based device
now it says
warranty void: 1 (0x030c)
current binary: custom (changed from something else)
---------- Post added at 07:53 PM ---------- Previous post was at 07:16 PM ----------
I ruled out the kernel 4.14. as beeing faulty. No surprise
An indicator is that before the knox coutner was never triggered before, it seems TWRP was not written correctly with kernel 4.14.x.
Small chance of doubt of course as i also used the --no-reboot option.
If i had second such expensive tablet, I could rule it out. But i do not have a second virgin tablet to rule the errors out a 100 percent.
--
One question.
How comes TWRP on SAMSUNG SM-T580 does not power off when I use the power off button in software. It does reboot instead of powering off the device.
I know samsung sucks. The device can barely be powered off except when the device is unlocked in android, and stupidly press power button and than twice a big software power off button.
it is obvious some idiotic customers complained the device is broken, it is always turned off, so they removed the power off feature and replaced it with a reboot or doing nothing.
Nexus 4 / nexus 7 2012 does not have such nonsense. Any acpi computer can be instantly turned off and does not reboot endless times.
Sorry to derail this topic.
The firmware of SM-T580 is a bit ****** up.
The device could not bootup today. Which looked like a softbrick.
The device only randomly enters the custom recovery. When you press it too long it turns off or does something else. Very unreliyable. This was definitely much better on nexus 4 and nexus 7.
I'm kinda certain the firmware is rubbish in any aspect. I assume the firmware tries to removes accidentally turn on of the device or going into the recovery. I have not yet figured out the timings and when to press it. It is kinda obvious they have some sort of timer running in the background which acts differently on the keyprssses.
the solution of keeping the buttons pressed forever does not really work for this device.
@ guy who asked me what I want to flash, which custom rom => https://forum.xda-developers.com/ga...-lineageos-14-1-android-7-1-2-nougat-t3706002
It has a bit of bloat. Much better as the SAMSUNG stock fake android. and 3 GIB more now.
which version of Heimdall could I use?
db1911 said:
I used Heimdall to root my sm-t580 using Ubuntu. Under the utilities tab, click on Detect, and you should see the Device Detected radio button selected, as well as Device Detected in the output box. Then under Download PIT, click on save as. A dialog box opens so that you can select a destination and name the file. Navigate to the folder of your choice, name the file and click on save. Once the dialog box closes, click on the Download button. You can monitor the progress in the output box. Hope this helps and let me know if need any help. I'll do my best.
Sent from my SM-T580 using Tapatalk
Click to expand...
Click to collapse
Hello! I have samsung galaxy tab A, sm-t580.
I use Heimdall (c) 2010-2013 Benjamin Dobell, Glass Echidna, but it doesn't work well, especially when initialize the protocol
Hello,
I've got a Galaxy Tab S5e which I want to boot when I insert a usb cable for charging.
I've tried using the fastboot oem off-mode-charge 0 command but whatever I try fastboot keeps waiting for devices.
Tried updating the USB driver already.
When I have my tablet connected and it's normally booted adb devices shows the device. When I then reboot into bootloader using adb reboot bootloader, it's no longer showing devices when I try fastboot devices.
What am I missing here?
Is there another solution to this problem?
Hope someone can help me out.
Thnx!
Hi
Firstly I do not know if fastboot commands work with samsung, that is why we have to use Odin to flash roms
I am on stock ROM and have the exact opposite problem.
I rooted using magisk following the excellent guide in xda
I then installed a magisk patched version of twrp using the official twrp installer. (detailed in post 232 of the S5e root thread)
This left me with three issues.
1 The tablet would be rooted weather I booted into system or recovery.
2 The adb would not connect or said device was offline
3 The tablet would boot up when plugged in to the charger.
Wiping the cache in twrp corrected the first 2 but has left me with a tablet that boots when charging cable is plugged in
So if you want a rooted tablet that boots on charging this may be the way to go only I don't yet know how to reverse it!
And of course it may not work that way with older or newer firmware
Extall
Hi, thanks for the answer.
I followed this brilliant guide to root indeed.
After that I've changed this file : /system/bin/playlpm. The source for this is here.
I've changed it to:
#!/system/bin/sh
sleep 20
/system/bin/reboot
Works like a charm. Device is rooted but I don't care. I hope future firmware will still support this but I think I'm going to make a clone using the backup feature of TWRP. This way I can always go back to this point.
In my case, the device is only used with one app. It boots on power and starts the app with Surelock. It's used in a museum.
Thanks for the answer, I had the same solution
Kind regards,
Marcel