Ok, so Was using my nexus s today and I kept getting the notification to perform a system update to the newest version of gingerbread (2.3.4). Prior to pressing update my phone was at 2.3.1 default with 2.5.### ClockworkRecovery and it was rooted. Everything worked on it perfect. So I proceeded to download and install the update, and CWR fails to install the update and I would have to take out the battery to restart the phone. I had been doing this multiple times and I wanted to get it updated. So I go into CWR and try installing it manually:
I look around and try to find the file and I couldn't, I reset user data to see if it would fix it and it didn't, then I go back and start formatting the following folders, /system, /cache, /data and one other but I did not format /boot, so Then (noob me) I restart to phone and of course the rom is gone. I get back to recovery and try to restore from update.zip but the console said the file could not be found, I look up my model and look for a full verison rom and the mount my usb storage and place the rom .zip on the storage and try to install from .zip on sd but it did not work so I end up grabbing this and installing it and now I'm stuck, when I do adb shell it doesn't pick up the phone any more, it can fast boot on the phone but it can't go into recovery and I have no idea what I should do to try to fix this problem.
NOTE: before I ened up installing and replacing the recovery, my /system folder would not mount due to "invalid arguments"
Model is i9020T
I don't have firmware version access
and if there is any other information I can provide please let me know
Update:
I got the device to be recognized by fastboot but not by "adb shell", when I type adb shell no device is found, so I guess my question now is do I need to just flash a new recovery and then try to flash a new rom?
Solution:
1. fastboot your phone, (volume up+lock/power button)
2. place the recovery image you want to install in the "Android SDK"/tools/ folder
3. in your cmd/terminal, while in "Android SDK"/tools/ execute:
Code:
fastboot flash recovery "NAME-OF-RECOVERY.img"
4. once that is installed and it should work, then restart your recovery mode
5.clear all your data/factory reset, including davlik cache
6.mount your sd to your computer so you can place the Rom you want on your phone's sd
7. In recovery choose zip from sdcard to install.
8. It should install, if it gives you problems try another rom, I had problems with rAv 1.2.2, keep restarting every minute. I used "NS-2.3.4-GRJ22-Stock-Deodexed-signed.zip" and it worked.
9. Restart the phone and be patient the phone will start up and you should be set.
Hope this helps someone!
Hi Guys,
Just thought I'd provide a warning and a fix to a half day ordeal recovering from a soft-brick after wanting to make the switch from TW to WWE.
What made this all go wrong?
I have a Padfone 2 which had the latest TW_A68-10.4.17.15
I have a accidentally turned off adb USB debugging mode
The process:
I unlocked my bootloader using the ASUS official unlocker.
I had then install 2.7.0.1 twrp which didn’t work
Install 2.5.0.0 twrp which did.
Forgot to do a backup which I usually did, but guess I thought that I have done this so many times, nothing would go wrong.
DON’T GET COCKY BACKUP FIRST.
Opted for the easy way out and write to system VIA twrp using zip, which was reported to work.
This installed and didn’t report any error.
After reboot, app.phone and another OS programs crashed constantly and rebooted.
I removed my sim and this stopped the crashed apps, but not the reboots.
I realised I was in a whole world of trouble and it was only at this moment did I realise that I didn’t have USB Debugging turned on. Frantically tried to enable it in between reboots, but failed and was now presented with only a ASUS spinning circle of death, or even better later, only the which ASUS logo before it reached it.
All I had available was fastboot and twrp.
You’d think this was an easy fix, but I didn’t have a usable/original rom on the /data/media a.k.a /sdcard partition.
Note: have a handful of roms including your original rom saved on the phone before trying anything, as this phone has no access to external storage when all goes pear shaped.
I wiped caches, didn’t work.
I then wiped data, which then deleted the only rom I had access to. So I couldn’t even now retry installing from zip.
ADB didn’t work from any recovery including CWM 6.0.4.4
I was at a loss and didn’t know what to do.
The recovery:
Installed twrp 2.6.3.0 was persistent with ADB sideload, even though I didn’t have USB Debugging enabled.
Note: ADB sideload will still work even if you don’t have USB Debugging enabled. It’ll either take a min or two to register on your computer, but if not reboot and reboot again to get it to register.
Sideloaded the wrong firmware file again.
Note: If you are trying to sideload the original firmware, extract the zip “TW_PadFone2_user_10_4_17_15_UpdateLauncher.zip” and sideload the zip hiding within “ASUS” -> “Update” -> “TW_A68-10.4.17.15-0-ota-user.zip”
After another long time trying to get the ADB device to register, finally got a second chance and got back to the original firmware.
Did this deter me from the switch from TW to WWE. HELL NO!!
Enable ADB USB Debugging
Make sure you push the rom WWE to your /sdcard partition
How to do it right.
Load the original recovery attached recovery.stock.img
Reboot into recovery and select "apply update from external storage" and choose the zip file to flash.
This will fail! It's what it's meant to do
At this point the recovery changes the partition table and then restarts.
On reboot we will have a nice "Installation aborted", this because, being changed the partition table, the recovery can not find the file to flash as it the partition containing the data has been reformed losing its contents. So you will need to copy the file again via adb.
Select "wipe data / factory reset"
You need to do a wipe, because it formats the partition where we will send the file. Having just changed, the partition has not a file system and so it must be formatted to save something on it.
Upon rebooting to ADB stopped working under the stock recovery. It registered with my computer but the command to repush the WWE rom to /data/media kept failing.
Rebooted into fastboot and install twrp 2.6.3.0. At this stage as I knew that the partition table had been updated, I sideloaded the WWE rom, which works more reliably when it's originally enabled
Did a Wiped cache for safe measure
Reboot and welcome to another 2GBs of space and WWE firmware.
NOTE: Always flash the inner zip “TW_A68-10.4.17.15-0-ota-user.zip” not the outer zip “TW_PadFone2_user_10_4_17_15_UpdateLauncher.zip”
freak4916 said:
Load the original recovery attached recovery.stock.img
Click to expand...
Click to collapse
Where can I find this?
Howdy'
So it's a Moto G X1032, rooted and unlocked bootloader using MotoTool. Stayed on stock for a while until today, I downloaded the CM12 nightly "cm-12-20150119-NIGHTLY-falcon.zip" on a laptop, and this is what went through in order
1. Updated CWM recovery to "recovery-clockwork-6.0.4.7-falcon.img" using ADB
2. Rebooted
3. Copied "cm-12-20150119-NIGHTLY-falcon.zip" and "pa_gapps-modular-mini-5.0.1-BETA12-20150116-signed.zip" and "BETA-SuperSU-v2.44.zip" to SD Card (Root Folder)
4. Reboot into CWM Recovery 6.0.4.7 using power and volume key then 'recovery'
5. Wipe data/factory reset
6. wipe cache partition
7. advanced - wipe dalvik cache - then go back to main menu
8. install zip
9. choose zip from /sdcard
10. 0/
11. cm-12-20150119-NIGHTLY-falcon.zip (Success)
12. pa_gapps-modular-mini-5.0.1-BETA12-20150116-signed.zip (Error Status 6 - Installation aborted) (never mind it, I continue by going back to menu)
13. BETA-SuperSU-v2.44.zip
14. Reboot
15. Root access possibly lost. Fix? No / Yes - Fix root (/system/xbin/su)
16. Yes
17. Motorola Logo
18. Cyanogenmod Blue Evil Android thingie with a rotating arrow appears
19. Stuck like that for more than an hour
20. I google a bit, some say it's super su, some say it's false alarm
21. I remember I had an old supersu.zip in the root folder back from when I first rooted using MotoTools
22. Go back in recovery do the whole thing again but this time with the old supersu
23. Reboot - Stuck on the evil blue android
24. Can't access anything of course other than recovery
25. I come here to ask you for help
Update 1: I flashed the newest supersu and rebooted into recovery from the advanced menu, but it gave the Root access possibly lost. I did it again but this time with the old supersu file I had there and rebooted into recovery, no Root access possibly lost message. So I install the cm12 nightly, but sadly the root access lost message appears again. I'm guessing this is the whole problem. Any ideas?
Update 2: Wiped everything, flashed the good old supersu, flashed cm 12 nightly, flashed the old supersu again, rebooted with no error messages. Yay! Right? No! Still stuck on the evil blue android
Note: Back when I was on stock before any of this, I had super user and not supersu, if it makes any difference to diagnosing this whole thing
Thanks for any help!!
Fixed
For anyone facing the same problem, it's all in the root. The root was not 5.0 capable. You have to download CF Auto Root (newest version supports 5.0). Links in this article
and in case you get an error of wrong path, you can edit the cmd command to point to the files by navigating using CMD to /tools
C:\Windows>cd ..
C:\>cd CF-Auto-Root-falconumts-falconreteu-xt1032\tools
C:\CF-Auto-Root-falconumts-falconreteu-xt1032\tools>fastboot-windows.exe oem unlock (it will give error if you're already unlocked, that's ok)
... OKAY
C:\CF-Auto-Root-falconumts-falconreteu-xt1032\tools>fastboot-windows.exe boot ..\image\CF-Auto-Root-falconumts-falconreteu-xt1032.img
downloading 'boot.img'... OKAY
booting... OKAY
CM12 will boot just fine after that. Just do a fresh install "if necessary"
Thanks incrjaysen for that last step of editing the path.
All works now
It's been a rough morning over here.
I've had a lot of issues with the latest update (12.1) so I decided to download the .zip for CM12s and install it from recover - the exact same way I updated it initially (before I got the 12.1 OTA update).
I used the same .zip file from before, builds.cyngn.com/cyanogen-os/bacon/12.0-YNG1TAS0YL-bacon/2263178b74/cm-12.0-YNG1TAS0YL-bacon-signed
After installing from internal storage from the menu, it seems to install fine, and then it takes me back to the menu and I select Restart System.
After 20 minutes looking at the Cyanogen boot logo, I'm assuming it's stuck.
When I plug the phone into the computer, it says it's charging but neither Windows or my Chromebook recognize the device to allow file transfer.
If I press down+power, I can still get to the Cyanogen menu, but without a new .zip file I'm not sure what else to try.
Any advice? I'm pretty worried!
nagem145 said:
It's been a rough morning over here.
I've had a lot of issues with the latest update (12.1) so I decided to download the .zip for CM12s and install it from recover - the exact same way I updated it initially (before I got the 12.1 OTA update).
I used the same .zip file from before, builds.cyngn.com/cyanogen-os/bacon/12.0-YNG1TAS0YL-bacon/2263178b74/cm-12.0-YNG1TAS0YL-bacon-signed
After installing from internal storage from the menu, it seems to install fine, and then it takes me back to the menu and I select Restart System.
After 20 minutes looking at the Cyanogen boot logo, I'm assuming it's stuck.
When I plug the phone into the computer, it says it's charging but neither Windows or my Chromebook recognize the device to allow file transfer.
If I press down+power, I can still get to the Cyanogen menu, but without a new .zip file I'm not sure what else to try.
Any advice? I'm pretty worried!
Click to expand...
Click to collapse
Have you tried using fastboot to flash the stock images?
Are you using twrp?
1.I suggest installing twrp vor any recovery you like.
2. Than redownload rom and gapps (just to be sure)
3. Mount your device as mtp storage in twrp and put Rom and gapps in it
4. Than wipe /system /data /cache
(data wipe will delete all apps, your internal storage will be untouched)
5. flash rom and gapps
6. reboot your phone
If that does not help try Heisenbergs solution.
The following is an outcome of an initial post I put up in Q&A regarding achieving root on the SM-T235 for the 5.1.1 Stock Rom (and subsequent questions and dialog with other forum members on issues) I have tried to clean up the posts here but am retaining most of them as it shows the issues other users went through (and feedback perhaps useful to some) The TWRP version is key here and it is what was seen as enabling correct flashing of the SU zip to achieve root. So hope this helps!
I used the following firmware today as a demonstration (have tried now all available 5.1.1 firmwares (successfully) except the DBT which does not flash fully for some reason)
https://www.androidfilehost.com/?fid=24269982087020611
which is AUT-T235XXU1BOH7-20151217085736.zip
ROMs are available here
http://forum.xda-developers.com/tab-4/general/links-galaxy-tab-4-official-lollipop-5-t3102844
I took out external sd (so NO EXTERNAL SD..no linkstosd nothing of the sort)
(TO NOTE-I simply took out the external SD and worked with just the internal storage for THIS demonstration to weed out the issue as other members posting on my original thread were not able to achieve the root I was able to get-it is not absolutely necessary and you could have your SU zip and any other files on the external SD however it is a good idea to keep it simple initially)
SO...I went to TWRP
TWRP is the one attached here in this post (from the thread below but may be different as the OP got updated-however the one I have attached works!)
http://forum.xda-developers.com/tab-...a1-sm-t3027059
You will see in this post that has a picture of the previous OP, the file name is what I have
http://forum.xda-developers.com/show...1&postcount=52
anyway, not sure if there are any differences but am using what works for me (the attached file)
So i did the following which may contain extra or unnecessary steps-no harm though in doing them-as I was trying to demonstrate the rooting process relative to issues other forum posters were having
(EDIT-VERIFIED-you could simply start at step 4 below where you go into download mode to flash the rom (but have the SU zip on external SD card unless it is already in the internal sdcard) and also uncheck autoreboot in Odin (do NOT check repartition!) so that once the rom has been flashed you do not have to boot up the rom, but then reset odin, again go to download mode, again uncheck autoreboot, flash TWRP, then go to recovery (do not boot rom), and flash SU zip and then only boot up-thanks frenkie9999999)
Otherwise this is what I did
1) complete wipe data, cache, system, dalvik all 2 times just for good measure
2) format internal sd (note NO external sd card) (no SIM either but that is because I need my phone working during this process and my SIM is on the T705)
3) reboot to download (do NOT install SU by twrp)
4) Used odin 1.85
5) flash the rom above (or the country firmware of your choice)
6) once device boots up do not connect to anything NO google, no wireless nothing
7) just go to settings, enable development and usb debugging (just what I do normally and mock locations) and in security allow for unknown sources, in google settings I uncheck ALL options
8) do not set up anything else
9) connect device to the laptop
10) copied over the beta 2.65 latest chainfire and root explorer apk that I have (to internal storage...see pictures...I do not have anything else in the internal card, and do not have any external card)
Chainfire's SU zip is from (credits to him for his awesome work for many many years now)
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
credit goes to K94U for this post that helped me achieve root on the T235 (not my original work as such but just listing the steps here as there were no explicit instructions for the T235)
http://forum.xda-developers.com/showpost.php?p=64182938&postcount=15
11) disconnected device from the laptop
12) went to download mode
13) odin 1.85 again and this time the TWRP recovery I have attached
14) did not let it boot up.,,,forced it to recovery by first pressing power, vol down and home to get to the choice of download or continue to reboot...
15) chose continue to reboot
16) immediately switched to power, vol up and home to get to TWRP
17) flashed the SU zip
18) do not install SU as prompted by TWRP
19) let it reboot
20) found SU in the installed apps in launcher
21) opened up SU and checked the options I want
that was it...opened root explorer and sure enough have root
Google may prompt accept. decline check apps...I always decline and then go to google settings and uncheck those pesky secuirty options as well (if not done already)
the TWRP version is important as the one I have attached works for the purpose of flashing the SU zip to get root correctly
here are the screenshots and the TWRP tar
Got xposed working too wanam arm (32) v78.1 sdk22
Sent from my SM-T235 using XDA Free mobile app
@mac231us
Doesnt work for me. Did everything as your thread guides but i still can't get the SU permissions.
Enabling SuperSU gives me the note "There is no SU binary installed[...]"
Any idea what i did wrong?
1. Flashed to 5.1.1 from CM12.1 and didn't boot
2. Flashed TWRP and booted directly to recovery
3. Flashed BETA-SuperSU-v2.62-20151210170034 and reboot
4. Got SuperSU app installed but it don't let me launch it (not installed binaries)
tyktak said:
@mac231us
Doesnt work for me. Did everything as your thread guides but i still can't get the SU permissions.
Enabling SuperSU gives me the note "There is no SU binary installed[...]"
Any idea what i did wrong?
1. Flashed to 5.1.1 from CM12.1 and didn't boot
2. Flashed TWRP and booted directly to recovery
3. Flashed BETA-SuperSU-v2.62-20151210170034 and reboot
4. Got SuperSU app installed but it don't let me launch it (not installed binaries)
Click to expand...
Click to collapse
that is odd..i just did a fresh install..wiped fully formatted...went to download (do NOT install SU as twrp prompts) odin flashed the 5.1.1 (nordic)...in fact this time even rebooted and set up google account..then went back to download...installed twrp again...again rebooted but this time straight to twrp...then installed the latest su 2.62-3...rebooted (again do not check the SU install prompted by TWRP)...and the su app was there..and so was the binary
noticed chainfire now has BETA-SuperSU-v2.64-20151220185127.zip
curious did you do a 5.1.1 odin flash from cm12.1 or a twrp nandroid recovery...just wondering if it makes a difference
twrp is from here
http://forum.xda-developers.com/tab-4/general/sm-t235-lte-rooted-twrp-2-8-alpha1-sm-t3027059
again...am only speaking of the T235 (or T235Y) not any other variant
the 5.1.1 I used is from here
https://www.androidfilehost.com/?fid=24052804347821380
in order to prevent stock recovery from coming up always first go to download step (not actual download) but using the volume down, power and home to get to the choice of download and reboot..then reboot but quickly go to volume up home and power to get to the twrp recovery
@mac231us
Aww, i cant get it working..
Did exactly what you said:
1. Format everything from TWRP (5.1.1 rom)
2. Flash 5.1.1 (nordic)
3. Configure google account
4. Back to download and flash TWRP
5. Back straight from download to recovery
6. Flash 2.62-3 and reboot (didnt checked the SU install prompted by TWRP)
7. When i open SuperSU app i am getting exactly:
There is no SU binary installed, and SuperSU cannot install it. This is a problem!
If you just upgrade to Android 5.0, you need to manually re-root - consult the revelant forums for your device!
Click to expand...
Click to collapse
Btw. i am getting red and blue text when booting - Kernel is not seandroid enforcing.
Galaxy Tab 4 7.0 LTE (SM-T235)
EDIT...also
tyktak said:
@mac231us
Aww, i cant get it working..
Did exactly what you said:
1. Format everything from TWRP (5.1.1 rom)
2. Flash 5.1.1 (nordic)
3. Configure google account
4. Back to download and flash TWRP
5. Back straight from download to recovery
6. Flash 2.62-3 and reboot (didnt checked the SU install prompted by TWRP)
7. When i open SuperSU app i am getting exactly:
Btw. i am getting red and blue text when booting - Kernel is not seandroid enforcing.
Galaxy Tab 4 7.0 LTE (SM-T235)
Click to expand...
Click to collapse
cannot think of anything else at the moment except that am using older version of odin v 1.85 (i too get the red and blue text..the recovery is not default as simply rebooting to recovery takes one to the stock unless doing the 3button to download to recovery process to get to twrp)
try it again w odin 1.85 and maybe go back to the way I 'instructed' the first time (where I did not set up the rom at all and went back to straight to twrp and flashed supersu...formatting internal storage is important but think you are doing that already)
you may want to ask some of the other folks who also got root
though imo there were no explicit instructions but enough for me to go on with..here....
http://forum.xda-developers.com/tab-4/general/sm-t235-lte-rooted-twrp-2-8-alpha1-sm-t3027059/page15
except for K94U's post here which was very informative
http://forum.xda-developers.com/showpost.php?p=64182938&postcount=15
and
http://forum.xda-developers.com/tab...laxy-tab-4-t3264281/post64216314#post64216314
EDIT another thought i may have done this at some point do not recall (but not today for example on this new installation) is to format the internal card using the stock recovery itself after installation of the odin-rom
then do the other steps of twrp etc from download mode again
@mac231us
Giving up and waiting for CM13.
I've did everything exactly how it should be done and SuperSU is showing information about mising SU binary.
Tried every SuperSU zips from Chainfire but effect was the same every time even with fresh flash of nordic rom and recovery. Ive tried cleaning data through stock recovery but it didnt helped.
Thanks for trying.
tyktak said:
@mac231us
Giving up and waiting for CM13.
I've did everything exactly how it should be done and SuperSU is showing information about mising SU binary.
Tried every SuperSU zips from Chainfire but effect was the same every time even with fresh flash of nordic rom and recovery. Ive tried cleaning data through stock recovery but it didnt helped.
Thanks for trying.
Click to expand...
Click to collapse
Apparently some users need these additional steps to fix supersu:
11. - Reboot Tablet, and from you PC extract the originally downloaded SuperSU 2.6x file on you PC, and navigate to the common directory on the extracted folder, and copy the superuser.apk file to your tablet.
12. - Make sure that you have Unknown Sources checked in the Device administration section of security settings so that you can install superuser.apk.
13. - Install superuser.apk
Also, SuperSU 2.64 fixed my kernel enforcing msg on boot...
@K94U
Still the same. I'll try flash KK then LL and try again whole process instead of CM12.1 -> LL.
I will let you know if it helped.
Btw. Chainfire published version 2.65 today
tyktak said:
@K94U
Still the same. I'll try flash KK then LL and try again whole process instead of CM12.1 -> LL.
I will let you know if it helped.
Btw. Chainfire published version 2.65 today
Click to expand...
Click to collapse
another wild guess is put all your supersu zip and apk files onto the internal storage itself
you will boot into the rom (now seeing that it does not matter if you boot into rom and then go back to download, odin the twrp, flash the supersu zip or that from odin rom directly go to download again, twrp odin and then flash supersu zip as both worked for me-not sure if there really is any technical difference)
you will need to boot to rom anyway especially after formatting and in order to put the supersu apk as K94U mentioned onto the device and then go back to download and do the recovery etc steps
after yesterday's fresh install the way of booting into rom, then going back to download etc (so this process has worked 2 ways, 4 times so no fluke understand some little differences may exist) i was doing backups only to find that when i actually went to the sd card no backup was there although i could transfer files back and forth between storage and the sdcard and computer and sdcard...so finally it was the sdcard that was bad...now all is working fine with backups after switching to different sdcard and using the ridgecrop 32formatter
http://www.ridgecrop.demon.co.uk
32bit version
@mac231us
Is that possible there is something wrong with the downloaded rom and it causes the problems?
When i get "upgrading" notice after flashing, bar goes 1/4 and then show "erasing".
I'll download germany 5.1.1 and try again. Totally no idea what's wrong. Maybe Link2SD has broke mine partitions or something.. after flashing SuperSU it didn't created any folders in /system
I've unmounted my sdcard but recovery still shows it as possible to wipe.
EDIT: After flashing Germany 5.1.1 there is still Erasing in 1/4 way of upgrading software..
EDIT2: Tried again with differrent usb cable and its the same.
EDIT3: After flashing SuperSU and reboot, device is starting and there is a samsung logo for a few secs and then there is a second reboot but with sound at samsung logo.
tyktak said:
@mac231us
Is that possible there is something wrong with the downloaded rom and it causes the problems?
When i get "upgrading" notice after flashing, bar goes 1/4 and then show "erasing".
I'll download germany 5.1.1 and try again. Totally no idea what's wrong. Maybe Link2SD has broke mine partitions or something.. after flashing SuperSU it didn't created any folders in /system
I've unmounted my sdcard but recovery still shows it as possible to wipe.
EDIT: After flashing Germany 5.1.1 there is still Erasing in 1/4 way of upgrading software..
EDIT2: Tried again with differrent usb cable and its the same.
EDIT3: After flashing SuperSU and reboot, device is starting and there is a samsung logo for a few secs and then there is a second reboot but with sound at samsung logo.
Click to expand...
Click to collapse
the DBT 5.1.1 has never worked for me (flash failed always) (am in the USA btw not that it makes a difference)
the ones that have worked are (have tried all of them at one time or the other when I was experimenting getting root type control (removing unwanted system apps, deodexing etc by flashing zips to perform certain mods/functions))
do not have any special apps like link2sd...i recommend removing external sdcard altogether and just working w the internal storage for now
LTE SM-T235 XXU1BOH7 AUT Region (Switzerland)
--LTE SM-T235 XXU1BOH7 NEE Region (Nordic Countries)
--LTE SM-T235 XXU1BOH7 SER Region (Russia)
--LTE SM-T235 XXU1BOH7 SKZ Region (Kazakhstan)
tyktak said:
@mac231us
Is that possible there is something wrong with the downloaded rom and it causes the problems?
When i get "upgrading" notice after flashing, bar goes 1/4 and then show "erasing".
I'll download germany 5.1.1 and try again. Totally no idea what's wrong. Maybe Link2SD has broke mine partitions or something.. after flashing SuperSU it didn't created any folders in /system
I've unmounted my sdcard but recovery still shows it as possible to wipe.
EDIT: After flashing Germany 5.1.1 there is still Erasing in 1/4 way of upgrading software..
EDIT2: Tried again with differrent usb cable and its the same.
EDIT3: After flashing SuperSU and reboot, device is starting and there is a samsung logo for a few secs and then there is a second reboot but with sound at samsung logo.
Click to expand...
Click to collapse
Here the same for me. Like Tyktak I ve tried every every step like him but not work for me too.
I
Will do flash, root etc from scratch once more tomorrow taking pictures along the way and post here...maybe by evening U.S time
Sent from my SM-T705 using XDA Free mobile app
deleted
mostly replicated/cleaned up in the OP now
@mac231us
Thanks mate, it worked!
The reason was probably the newer TWRP which was 2.8.7.0 Add this tutorial as new topic in general section of Galaxy Tab 4.
@frenkie9999999
tyktak said:
@mac231us
Thanks mate, it worked!
The reason was probably the newer TWRP which was 2.8.7.0 Add this tutorial as new topic in general section of Galaxy Tab 4.
@frenkie9999999
Click to expand...
Click to collapse
AWESOME!...yes was thinking about the TWRP yesterday so posted it this morning along with the other steps.
have requested moderator to move the thread to the General section.
@mac231us
Don't forget to edit first post so ppl won't have any problems
YesssSSS! Twrp 2.8.1.0 !!!!
Works great!!!
Thanks Mac231us!
Thanks tyktak!
-Flash TWRP 2.8.1.0 recovery with odin3 1.85 (without re-stocking) -dont forget UNCHECK "autoreboot" on odin.
-WIPE CACHE & DALVIK
- Flash SuperSU 2.65
enjoy!
---------- Post added at 11:38 PM ---------- Previous post was at 11:37 PM ----------
thanks mr. Chainfire!!!!!!
without you Android will never be the same
Thanks a lot !
I followed every step and I was successful . Everything worked .
My tablet is rooted again !