Related
This is official ROM (bin) from acer. Is for Liquid E. For Liquid - visit modaco forum.
http://tranz.it/load.php?id=pywW4rpuHxQ1lsGx685901
Since yesterday also available on the acer site (support section)!
nietnicks said:
Since yesterday also available on the acer site (support section)!
Click to expand...
Click to collapse
Yep- it is from there, but only BIN file.
Hmmm seems that with the official acer update the upgraded S100 is going to be a problem.
I've got a message that the froyo update can only be done on liquid e devices because of the RAM space. s100 has 256Mb and the liquid e 512Mb. Because of that the official acer update tool stops.
Is this the reason the froyo alpha version i've installed now is a bit laggy???
[update] Gonna try the modaco version now! (4.002.14.EMEA.GEN1 bin for 256M)
hmmm, stopped at fastboot succesfull, now rebooting. and then it stopped. powerbutton does nothing, repluggung usb does nothing. Bricked?
Not bricked as it seemes. Used the following tips by malez and got out of the bricked mode (where it did nothing):
1. Pull battery in and usb cable to phone and pc
Press in order and without releasing
1. < (back button)
2. Camera
3. (power) not always necessary
Bootloader should appear. If that doesn't work unplug usb and unplugg battery and retry.
If this still does not work you can also try this
1. turn off your phone (and unplug usb if plugged)
2. press camera + volume up and then without releasing this two buttons hit power and the phone will vibrate two times. Release all buttons.
3. take the battery out and put it back (don't touch any button on the phone)
4. connect the usb to your computer and you will the acer logo and then bootloader will pop up.
Second list of tips got me up and running again with the new bin!
Is there any way to install this upgrade from SD card, I use Linux and therefor do not have windows.
Thanks.
nimnull said:
Is there any way to install this upgrade from SD card, I use Linux and therefor do not have windows.
Thanks.
Click to expand...
Click to collapse
Yes, you can... amm... somewhere in modaco i saw this kind of update... see there: http://android.modaco.com/category/418/acer-liquid-liquid-modaco-com/
I hope you find it!
nietnicks said:
[update] Gonna try the modaco version now! (4.002.14.EMEA.GEN1 bin for 256M)
hmmm, stopped at fastboot succesfull, now rebooting. and then it stopped.
Click to expand...
Click to collapse
Same here.
After "fastboot" successful it show a warning like "restoration is needed".
Taking the battery out (to turn off the phone) and putting it back and after turning on the phone worked for me
Still in the process of flashing, but here is my fun experience of trying to un-root and having tried about 6 different methods I had an idiot savant moment and figured this out.
As the subject explains I had official 3.29.651.5 hboot 0.97.0000 that I used unrevoked 3.21 to root with clockworkmod 2.5 as the custom recovery.
I was trying to follow these instructions:
http://www.evo4gforum.net/htc-evo-4...emoval-of-root-restoring-stock-rom/?topicseen
and
http://forum.xda-developers.com/showthread.php?t=780141
and
countless others of flashing a pc36img.zip to restore a ruu version.
The problem with the first set of instructions is that I would get an Error 170 USB connection when the phone would reboot to the HTC bootloader.
The problem with the second set of instructions was that I kept getting an error of main version is older when trying to update from the recover power+vol down.
So what I got to finally work is:
download HTC Sync 2.40
Download from http://shipped-roms.com/shipped/Supersonic RUU_SuperSonic_S_Sprint_WWE_3.29.651.5_Radio_2.15.00.09.01_NV_1.77_CNV_release_150224_signed.exe
Windows 7 x64 Pro
1. Turn off the phone and power up using vol down + power
2. Start the RUU_SuperSonic installer and complete the first 2 check boxes and next. Once the box displays that its checking your phone for android version hit the first option which is fastboot
3. If it kick over to it fastboot usb since its still connected to the computer
4. If it gets to the USB Error connect on the PC, start over at 2 and try a different option under fastboot. I am not for certain if I hit boot loader under fastboot or not It took a few tries to get it to start the push from the PC.
5. Let it do its thing and it should complete the flash process like normal.
Downloading and updating to 3.70.651.1 right now.
Thanks, these steps worked for me. Very well written!
I tried to flash my MS2, but now I have no boot and no access to the phone.
Story:
- root via paxChristos' Linux Port of DooMLoRD's Easy Rooting Toolkit
- backup via Titanium Backup
- backup via Bootstrap
- installed CyanogenMod and the nightly build cm_droid2_full-139.zip
- realized ... it is the wrong Mod, because for Druid2 and I have a Milestone2 = not the same
- sudo ./sbf_flash MILS2_U6_2.2.16_SIGNED_UCAMILESTONE2B1B80E100A.0R_USXMILE20RTDACH_P016_A005_HWp2a_Service1FF.sbf
And now, I have a dead phone ... even could not start it. It is just a black screen and nothing more!
The only thing that show "life" is the LED on the side of the USB-Cable plug!
I also tried Vol-Up/Dwon + Camera, Arrow-Up + Power On, x + Power On ... with and without USB-Cable!
Is there a way to flash the phone anyway?
Would be nice to have a little help!
A little more info:
Plug in USB cable and lsusb:
Bus 002 Device 013: ID 22b8:4280 Motorola PCS
Long press on the power button and lsusb:
no Motorola
Keep USB cabel in the phone, unplug the batterie and plug in back ... lsusb:
Bus 002 Device 015: ID 22b8:4280 Motorola PCS
And more info:
udev-rule1 (worked to flash the phone)
SUBSYSTEMS=="usb", ATTRS{idVendor}=="22b8", ATTRS{idProduct}=="41db", MODE="0666", OWNER="sasch" #Normal, Debug & Recovery droid
udev-rule2 (tried after reboot of phone showed lsusb shown before)
SUBSYSTEMS=="usb", ATTRS{idVendor}=="22b8", ATTRS{idProduct}=="4280", MODE="0666", OWNER="sasch" #Normal, Debug & Recovery droid
Also ... not worked:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="22b8", MODE="0666", OWNER="sasch" #Normal, Debug & Recovery droid
$ ./adb kill-server
$ ./adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
$ ./adb shell
error: device not found
Your only chance is SBF right now. Hold camera, vol down and power together, which can brings up bootloader mode and then flash it via RSDLite, because sbf_flash did not worked for me.
I made the same mistake myself back in the day .
I could get into bootloader no worries though... are you sure you didn't drain the battery or something?
Just seems pretty odd that you could remove an impossible to unlock, locked bootloader
First of all ... thanks for helping me!
Anonymous_ said:
Your only chance is SBF right now. Hold camera, vol down and power together, which can brings up bootloader mode and then flash it via RSDLite, because sbf_flash did not worked for me.
Click to expand...
Click to collapse
Nothing happend ... screen is black, LEDs are off!
DreadPirateDan said:
I made the same mistake myself back in the day .
I could get into bootloader no worries though... are you sure you didn't drain the battery or something?
Just seems pretty odd that you could remove an impossible to unlock, locked bootloader
Click to expand...
Click to collapse
Battery should be ok, it also don't work with Charger on!
If it is impossible to remove the locked bootloader, why can I still not boot?!
If the device bricked only a black screen shows up. This is bootloader mode. RSDLite will recognise your phone and flash an SBF.
Sent from my MotoA953 using XDA App
Damn ... just bought a used one on eBay and now I have my old one fixed! *lol*
Thanks to you all ..
I used my laptop with Windows7 and RDS light from Chip Online
Then I used the SBF Version 2.3.4!
reboot ...DONE ... Milestone2 worked again!
But ...
root via zergRush_automated_Linux_root
Installed bootstrap-1.0.0.5-droid2.apk from SD-Card because:
$ sudo ./adb push bootstrap-1.0.0.5-droid2.apk /system/app/
failed to copy 'bootstrap-1.0.0.5-droid2.apk' to '/system/app//bootstrap-1.0.0.5-droid2.apk': Read-only file system
reboot
wipe data/factory reset
wipe cache partition
installzip from sdcard (cm7-111129-2153-NIGHTLY-Milestone2.zip)
reboot ... black screen again!
Maybe the bootstrap installation is the problem?!
I think the message is very clear. The bootstrapper never installed to begin with. Second of all, why are installing the bootstrapper like that? Instead of copying it to your SD-Card and execute it from the file browser on your phone. It will be installed, after which you should execute it. It will ask for root access when you press the bootstrap button. You give it and then you press the button Reboot Recovery. Then you'll be in CWM. You can't install CM7 from Motorola's recovery, which is what you've been doing all the time.
Further: Endless7 has written a guide here: http://forum.xda-developers.com/showthread.php?t=1310641
I'd suggest you follow it, and if you don't understand something ask it.
HAPPY NEW YEAR!!!
Okay, actual I have my MS2 with the original sbf and I wait until my second MS2 is here.
Then I try to install CM!
Never the less I have questions, just to be sure.
When I install the droid2bootstrap, I just copy the file to the sdcard and then install it at the phone?! Is this correct?
Then the HowTo says: 3.open droid2bootstrap and select install recovery
But there is nothing like "install recovery" to select. There is just a screen with two buttons (Bootstrap Recovery and Reboot Recovery) ... I think "Bootstrap Recovery" first, then reboot?
If I do the steps above, I have an bootloader installed on my phone?! Which I can start with the volume buttons at bootup?
Wow, I have to learn a lot about Android phones! I read the wiki, but asking questions will help me more!
Thanks to you all!
What you described is correct except the startup with volume buttons.
You have to use the Reboot Recovery button to get in CWM, where you can flash CM7.
And just for the record: every phone has a bootloader installed, otherwise it wouldn't be able to boot an OS. Fact is that you can't replace it on the Milestone 2.
Don't mix up Recovery and Bootloader. They're different things.
sasch42 said:
$ sudo ./adb push bootstrap-1.0.0.5-droid2.apk /system/app/
failed to copy 'bootstrap-1.0.0.5-droid2.apk' to '/system/app//bootstrap-1.0.0.5-droid2.apk': Read-only file system
reboot
wipe data/factory reset
wipe cache partition
installzip from sdcard (cm7-111129-2153-NIGHTLY-Milestone2.zip)
reboot ... black screen again!
Maybe the bootstrap installation is the problem?!
Click to expand...
Click to collapse
bootstrap is not copied to /system/app , adb said "failed to copy...".
maybe copy it do /data/app ?
You wiped data and cache.. how about dalvik?
Because the copy failed, I installed the app from the sdcard (/data/app was also read only).
But as described here (http://forum.xda-developers.com/showthread.php?t=1310641) I used the wrong app!
IMHO it is the same to copy the app via adb or install it from sdcard?!
What the shizzle, you are making it so hard for yourself.
If you simply place the .apk file onto the root of you SD card, then using your phone, open the .apk, install it, then open the installed app, you will have no problems at all. I'm not sure of your motivation to try other methods when it allready works fine
Also, i would say that since it has apparently failed for you, no it isn't the same
EDIT: on a side note, it would seem you flashed the official gingerbread sbf, so now you will only be able to use the gingerbread kernel roms. Which is pretty much the cm9 alpha version, endless 7's cm7 defy port. Not really sure about the other gb rom (argen2stone, blurless etc). So make sure you read up on what you need and what will work
DreadPirateDan said:
...
If you simply place the .apk file onto the root of you SD card, then using your phone, open the .apk, install it, then open the installed app, you will have no problems at all. I'm not sure of your motivation to try other methods when it allready works fine
Also, i would say that since it has apparently failed for you, no it isn't the same
...
Click to expand...
Click to collapse
Have you read all the posts?
My mistake was ti follow this guide.
And my way to install the app was, to copy it tio the sdcard because the method in the guid didn't work!
Milestone 2 Bricked
Hello friend, i am having the same problem then you...
It only show black screen and the led on the side of the usb cable and i also tried Vol-Up/Dwon + Camera, Arrow-Up + Power On, x + Power On ... with and without USB-Cable, as you and nothing...
Can you help me? please!
Do you have RSDLite? If yes, then RSDLite should detect your phone as it is already in bootloader mode (the black screen). You can flash an SBF at this point.
Download an appropriate one, if you were on Froyo then Froyo and in case you had upgraded to Gingerbread then download a GB SBF.
Flash the SBF. You would probably end up in a bootloop. Go to moto recovery, wipe data and boot. You should be good to go.
Edit: I believe that only GB sbf is gonna work for you as I suspect that you were somehow on GB and then tried to flash Froyo which led you to the black screen.
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
Hi all,
First message in this wonderful community.
Anywas, having owned a Galaxy Note 3 for a few years now I thought I'd give it a shot at installing a new ROM to get it in better shape and try to stay with it a bit longer. Nothing really wrong with the phone other than getting a bit sloooow, specially the camera.
Anyways, not being a very geeky person, I soon realized the learning curve is steep.
This is what I've done so far:
1) Identified the model (SM-N9005)
2) Downloaded and unzip the SDK platform tools
3) Downloaded the TWRP custom recovery
4) Unlocked developer tools, allow unknown source (not sure if that is needed) and allowed USB debugging. In this phone I think there is no option for OEM unlocking.
5) Installed latest Samsung USB driver
5) Tried to proceed with unlocking the bootloader. This is where I ran into issues:
- I installed ADB Installer saying YES to everything
- Connected phone to pc with a usb cable
- From the command prompt (in my user) I executed adb reboot bootloader. I initially got an error (something about daemon and a port?....) but was able to move ahead
- The green android logo appeared along with this message "Downloading ...Do not turn off target!!"
At this point, pressing the volume down, power and select at the same time I tried to get out but kept on coming back to the same android menu stuck in "Downloading ...Do not turn off target!!". After the third try, a new warning message came up asking me if I want to proceed or reboot phone (pressing volume down) and I rebooted the phone to "escape" this predicament. I thought I was going to brick the thing!
Anyways, any recommendations on how to proceed? Is there an easier method to root the phone? Or to circumvent the issue I encountered?
As you might have guessed by my message, I can (sometimes) follow instructions but the underlying knowledge of what I am doing is .... well ...missing? :silly:
Hope you guys can help me. Thank you all in advance for your assistance.
PierreBCN said:
Hi all,
First message in this wonderful community.
Anywas, having owned a Galaxy Note 3 for a few years now I thought I'd give it a shot at installing a new ROM to get it in better shape and try to stay with it a bit longer. Nothing really wrong with the phone other than getting a bit sloooow, specially the camera.
Anyways, not being a very geeky person, I soon realized the learning curve is steep.
This is what I've done so far:
1) Identified the model (SM-N9005)
2) Downloaded and unzip the SDK platform tools
3) Downloaded the TWRP custom recovery
4) Unlocked developer tools, allow unknown source (not sure if that is needed) and allowed USB debugging. In this phone I think there is no option for OEM unlocking.
5) Installed latest Samsung USB driver
5) Tried to proceed with unlocking the bootloader. This is where I ran into issues:
- I installed ADB Installer saying YES to everything
- Connected phone to pc with a usb cable
- From the command prompt (in my user) I executed adb reboot bootloader. I initially got an error (something about daemon and a port?....) but was able to move ahead
- The green android logo appeared along with this message "Downloading ...Do not turn off target!!"
At this point, pressing the volume down, power and select at the same time I tried to get out but kept on coming back to the same android menu stuck in "Downloading ...Do not turn off target!!". After the third try, a new warning message came up asking me if I want to proceed or reboot phone (pressing volume down) and I rebooted the phone to "escape" this predicament. I thought I was going to brick the thing!
Anyways, any recommendations on how to proceed? Is there an easier method to root the phone? Or to circumvent the issue I encountered?
As you might have guessed by my message, I can (sometimes) follow instructions but the underlying knowledge of what I am doing is .... well ...missing? :silly:
Hope you guys can help me. Thank you all in advance for your assistance.
Click to expand...
Click to collapse
flash custom recovery.download supersuzip latest version is 2.82.push it to your phone.reboot to recovery mode.flash supershu zip.reboot to system.your phone is rooted.that's it.
Sent from my SM-N930F using Tapatalk
Normal method .
Flash TWRP via Odin.Put custom rom on SD card .
Boot to TWRP recovery and flash .
N9005 does not have a locked bootloader .