I'm completely hopeless, and all I can count on are good people from XDA to help me.
I bought a new Samsung Galaxy S6, T-Mobile version [G920F], running Android 5.1.
I used this tutorial:
http://www.droidviews.com/root-samsu...ry-all-models/
I enabled USB Debugging, downloaded latest Samsung USB drivers.
First I successfully installed TWRP 2.8.7.1, and meanwhile copied the SuperSU.zip to my device.
I had successfully entered TWRP, went to Install, and selected teh SuperSU file. It said it was done, so I went ahead and restarted my device.
Immediately, I noticed that the device was stuck on the boot logo (Galaxy S6 + Powered by Android screen).
And for some reason, when I connect the device with USB to mc PC, Windows says it's "damaged or undetected", something of that sort.
Luckily, I can still detect it in ODIN.
I might mention that I can still enter TWRP & Download Mode from the Bootloop.
I'll give any more information I can, just tell me if there is any hope for me.
Thank you so much.
I bought a new Samsung Galaxy S6, T-Mobile version [G920F], running Android 5.1.
I used this tutorial:
http://www.droidviews.com/root-samsu...ry-all-models/
I enabled USB Debugging, downloaded latest Samsung USB drivers.
First I successfully installed TWRP 2.8.7.1, and meanwhile copied the SuperSU.zip to my device.
I had successfully entered TWRP, went to Install, and selected teh SuperSU file. It said it was done, so I went ahead and restarted my device.
Immediately, I noticed that the device was stuck on the boot logo (Galaxy S6 + Powered by Android screen).
And for some reason, when I connect the device with USB to mc PC, Windows says it's "damaged or undetected", something of that sort.
Luckily, I can still detect it in ODIN.
I might mention that I can still enter TWRP & Download Mode from the Bootloop.
I'll give any more information I can, just tell me if there is any hope for me.
Thank you so much.
No comments:
Post a Comment