Related
I just obtained the Galaxy S2 LTE from Rogers, which is a an upgrade from the one I obtained from Bell.
As a result I found myself looking for an easy way to root the device, which led to multiple posts but no clear solution as to how to achieve this on my newly obtained device.
This post is merely a recollection of the posts and threads that have helped me achieve root on the SGH-I727R sold by Rogers in Canada.
Warning: I take no responsibility if you brick your phone. Do at your own risk.
Phone specs:
Samsung Galaxy S2 LTE by Rogers
Model: SGH-I727R
Baseband: I727RUXKJ7
Android version: 2.3.5
Kernel version: 2.6.35.11
Build number: GINGERBREAD.RUXKJ7
References:
Superuser.apk and su binary: http://androidsu.com/superuser/
ZergRush binary: https://github.com/downloads/revolutionary/zergRush/zergRush.zip
http://forum.xda-developers.com/showpost.php?p=18373159&postcount=30
http://forum.xda-developers.com/showpost.php?p=18544480&postcount=46
The process
My research took me to the posts above which focus on the use of the root exploit ZergRush.
1 - Download all the necessary files
ZergRush binary
Superuser.apk
su binary
2 - Run ZergRush as follows:
This requires the Android sdk with and the use of adb, which can be found in platform-tools on the sdk directory.
open a command line (cmd.exe) and type the following commands
type in "adb push C:\[location of zergRush]\zergRush /data/local"
type in "adb shell"
type in chmod 755 /data/local/zergRush
type in "/data/local/zergRush"
This is the output to be expected (this may be different for your device. Let the binary do it's job):
Code:
$ /data/local/zergRush
/data/local/zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x0002e118
[+] Found a Samsung, running Samsung mode
[*] Scooting ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 149 zerglings ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[+] Zerglings found a way to enter ! 0x18
[+] Overseer found a path ! 0x00030730
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[+] Overseer found a path ! 0x000307f8
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[+] Zerglings caused crash (good news): 0x40322cd4 0x0074
[*] Researching Metabolic Boost ...
[+] Speedlings on the go ! 0xafd25d9d 0xafd3975f
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 181 zerglings ...
[+] Rush did it ! It's a GG, man !
[+] Killing ADB and restarting as root... enjoy!
This will temporarily root your device (until the next reboot).
3 - Push Superuser.apk and su binary
Type the following commands in your command line shell:
adb remount
adb push c:\[path_to_Superuser.apk]\Superuser.apk /system/app
adb push c:\[path_to_su_binary]\su /system/bin
adb shell
chmod 644 /system/app/Superuser.apk
chmod 4755 /system/bin/su
reboot
This is the expected result:
Code:
C:\[path_to_SDK]\platform-tools>adb remount
remount succeeded
C:\[path_to_SDK]\platform-tools>adb push c:\[path_to_Superuser.apk]\Superuser.apk /system/app
4461 KB/s (785801 bytes in 0.172s)
C:\[path_to_SDK]\platform-tools>adb push c:\[path_to_su_binary]\su /system/bin
2713 KB/s (22228 bytes in 0.008s)
C:\[path_to_SDK]\platform-tools>adb shell
# chmod 644 /system/app/Superuser.apk
chmod 644 /system/app/Superuser.apk
# chmod 4755 /system/bin/su
chmod 4755 /system/bin/su
# reboot
reboot
Once the device has rebooted, you will have the application Superuser with root privileges which will allow other apps to benefit from it.
it is far from a one click app, and doesn't include any goodies that may be found in CMW4, but it's better than no root at all.
All credit goes to the creator of ZergRush and the people who contributed to the conversation on the original ZergRush thread.
Awesome.... I was wondering whether we were getting our own section or staying on the i9100 forum, glad you posted here.
Sent from my SGH-I727R using XDA App
To be honest, I didn't really know where else to put it.
Since it still somehow falls in the SGS2 category, I opted to put it here.
Hope this helps as we wait for the good stuff.
we might have to wait until it comes out on AT&T... unless we got more CDN devs that can bring on the good stuff sooner.
Have you tried installing CWM?
certainly a step in the right direction....
cue_32 said:
we might have to wait until it comes out on AT&T... unless we got more CDN devs that can bring on the good stuff sooner.
Have you tried installing CWM?
Click to expand...
Click to collapse
I haven't had a chance to play around with the roms yet. I'll probably have time this week to try and see what happens.
only way we gonna get our own section is if people start voting on that page.
How can we vote on a page? we need one!! I really want to root but im afraid to follow these experimental directions.. I cant risk bricking my phone
Could any of you fine folks clarify whether the Rogers GS2 is running Exynos or Snapdragon? I am 95% sure it's Snapdragon, but ALL info I find states "1.5ghz dual-core" and leaves it at that
Thank you, and I hope you are enjoying your phones
euphoria47 said:
Could any of you fine folks clarify whether the Rogers GS2 is running Exynos or Snapdragon? I am 95% sure it's Snapdragon, but ALL info I find states "1.5ghz dual-core" and leaves it at that
Thank you, and I hope you are enjoying your phones
Click to expand...
Click to collapse
Crapdragon, just like the AT&T Skyrocket.
You should put this in either Skyrocket dev section, or nowhere. (The I777 community is getting annoyed with all the ****rocket clutter in general/Q&A.)
What the hell were the XDA mods thinking putting the ****rocket dev section under the I777? If it were lumped with anything it should've been the T-Mobile T989 which is 98% identical.
We need our own forum someone setup the voting
Sent from my SGH-I727R using XDA App
Thanks. It worked. Took lots of tries to get everything working.
Cheers
Do we have to unlock the boot loader for this?
Hey,
The only device I have rooted before was Nexus one, where you had to unlock the bootloader first as far I remember when I did it. Do we need to unlock the boot loader to do this on the Galaxy S2 LTE. As well is there away we can revert back to original rom to avoid invalidating the warrenty? I just got the device and would hate to scrap it!!
Thanks.
digg1980 said:
Hey,
The only device I have rooted before was Nexus one, where you had to unlock the bootloader first as far I remember when I did it. Do we need to unlock the boot loader to do this on the Galaxy S2 LTE. As well is there away we can revert back to original rom to avoid invalidating the warrenty? I just got the device and would hate to scrap it!!
Thanks.
Click to expand...
Click to collapse
This is not a ROM.
The only thing you are doing is using the ZergRush exploit to gain access as root to the device and adding 2 files to your filesystem, namely Superuser.apk and su.
As far as performing the procedure, you just have to put your phone in debug mode when plugged to usb and use adb shell from the android SDK.
To go back to the original state of the device, all you have to do is remove those 2 files from their respective locations.
Entropy512 said:
Crapdragon, just like the AT&T Skyrocket.
You should put this in either Skyrocket dev section, or nowhere. (The I777 community is getting annoyed with all the ****rocket clutter in general/Q&A.)
What the hell were the XDA mods thinking putting the ****rocket dev section under the I777? If it were lumped with anything it should've been the T-Mobile T989 which is 98% identical.
Click to expand...
Click to collapse
I don't see why people keep calling it Skyrocket... There is no such denomination in Canada.
As far as the device itself, it is understandable that you don't own the device. This makes your criticism of it purely based on second hand experience - I assume that by "I777 community" that you mean you.
Some people other than you does own it, and might be interested in reading this. If you're not, why bother wasting a post in stating how much you hate the I727R and how the post is located in the wrong section (isn't that the role of the mods?).
Technically, they all fall into the Galaxy S2 category, the XDA mods should actually create one big SGS2 forum and put sub-forums for the I9100, the I777, I727R and the T989 instead of having 14 different forums for each device that is the SGS2 and they should most definitely call them by their code names instead of the carrier selected names, which throws everyone into confusion when looking for answers.
Agreed, Thanks. I understand the skyrocket is the other closest north american variant and so we should be following its development closely.
I've been trying to get other i727r owners to post requests as well.
I hope those asking for voting to be set up have actually also gone to the thread request post and added "+1 Galaxy S2 I727R".
That's what I did, however the post mod stated that it already had a forum and to stop requesting:
http://forum.xda-developers.com/showpost.php?p=19195950&postcount=1788
It's not even in the request list even though people are requesting it.
I don't see the forum anywhere?? Am I blind? I put a request in.
The mod assumed we were talking about the sky rocket so everyone go request in there "+1 SGH-I727R"
Sent from my SGH-I727R using XDA App
ninja0n3 said:
Technically, they all fall into the Galaxy S2 category, the XDA mods should actually create one big SGS2 forum and put sub-forums for the I9100, the I777, I727R and the T989 instead of having 14 different forums for each device that is the SGS2 and they should most definitely call them by their code names instead of the carrier selected names, which throws everyone into confusion when looking for answers.
Click to expand...
Click to collapse
Very good idea...
For 6.3 see http://forum.xda-developers.com/showthread.php?p=24129239
Please do not reupload/redistribute BurritoRoot2/BurritoRoot3, instead link directly to my hosting. I own the server, it will no go away any time soon. This allows me to update it if a bug is found.
BurritoRoot3 is not opensource, it is free, but it is not free to distribute. Please do not redistribute it.
Tested on 6.2, 6.2.1 and 6.2.2
Disclaimer:
BurritoRoot3 may void your warranty. While it was tested, over and over, a chance of data loss or hardware damage always exists. If something bad happens due to your use of BurritoRoot3, well it is your fault not our's, don't blame any of us.
Wine/Coffee/Device Funding:
To donate to jcase of TeamAndIRC for BurritoRoot go here:
http://forum.xda-developers.com/donatetome.php?u=2376614
To donate to pokey900 for the FireFireFire Bootloader go here:
http://forum.xda-developers.com/donatetome.php?u=466725
Download:
http://download.cunninglogic.com/BurritoRoot3.apk
BurritoRoot3 is an all in one package, to root and install the custom bootlaoder, FireFireFire, onto the KindleFire.
Instructions are pretty plain and simple, however you will have to get adb working on your own (if you have written, or know of adb guides for the Kindle Fire please PM me to list them here).
ADB GUIDES
MAC GUIDE: http://forum.xda-developers.com/showthread.php?t=1443071
WINDOWS GUIDE: http://www.jayceooi.com/2011/12/13/how-to-install-kindle-fire-adb-usb-driver/
LINUX GUIDE: http://forum.xda-developers.com/showthread.php?p=22067293
What it does:
Gains root, installs superuser, installs su and installs the FireFireFire bootloader.
At this time, we do not have permission to distribute any recovery, once one is available for our use, we will add auto flashing of recovery.
How to use:
adb shell chmod 777 /data/local/tmp
Run app, follow directions given by the app.
Usage example :
[email protected]:~$ adb shell chmod 777 /data/local/tmp <---- This one is important, it may not create BurritoRoot3.bin if this is not done
[email protected]:~$ adb install BurritoRoot3.apk
4897 KB/s (1151520 bytes in 0.229s)
pkg: /data/local/tmp/BurritoRoot3.apk
Success
<go open the app now>
[email protected]:~$ adb shell /data/local/tmp/BurritoRoot3.bin --root
BurritoRoot3 Installer 0.1 by TeamAndIRC
#########################################################################
Usage: BurritoRoot3.bin <parameter>
--root - Restart adbD as root, and install Superuser app
--install - Install su
#########################################################################
Gaining root...
Installing Superuser APP, if it erros as already exists, please ignore the error.
pkg: /data/data/net.andirc.burritoroot3/bin/Superuser.apk
Success
Restarting adbD as root...
Please run adb shell /data/local/tmp/BurritoRoot3.bin --install
[email protected]:~$ adb shell /data/local/tmp/BurritoRoot3.bin --install
BurritoRoot3 Installer 0.1 by TeamAndIRC
#########################################################################
Usage: BurritoRoot3.bin <parameter>
--root - Restart adbD as root, and install Superuser app
--install - Install su
#########################################################################
BurritoRoot3 kroot 0.1 - TeamAndIRC
Remounting /system...
Cleaning up, ignore any errors
rm failed for /system/xbin/su, No such file or directory
rm failed for /system/bin/su, No such file or directory
Installing su...
Remounting /system..
Root installed
Starting: Intent { act=android.intent.action.MAIN cmp=net.andirc.burritoroot3/.FireFireFire }
Please check your Kindle's screen
[email protected]:~$
If you already have root, and want to safely install the FireFireFire bootloader, you can use the app, just install, open/close the app then
adb shell am start -a android.intent.action.MAIN -n net.andirc.burritoroot3/net.andirc.burritoroot3.FireFireFire
To install the CWR recovery by DoomLord after gaining root:
Download it, and push it to your Kindle
adb push <filename> /data/local/recovery.img
adb shell dd if=/data/local/recovery.img of=/dev/block/platform/mmci-omap-hs.1/by-name/recovery
Would you support the archos G9 devices
jutley said:
Would you support the archos G9 devices
Click to expand...
Click to collapse
Doesn't archos sign or lock system?
I love you Devs so much. I just got a Kindle today, but as I watched the video your Kindle shows up under Other Devices as if it didn't install the device driver. Mine is installed under portable devices. Can I just update that one or is there a debug mode for the Kindle that I'm missing?
Thanks for all you do!
---------- Post added at 10:06 AM ---------- Previous post was at 09:55 AM ----------
CharlieBoy808 said:
I love you Devs so much. I just got a Kindle today, but as I watched the video your Kindle shows up under Other Devices as if it didn't install the device driver. Mine is installed under portable devices. Can I just update that one or is there a debug mode for the Kindle that I'm missing?
Thanks for all you do!
Click to expand...
Click to collapse
LoL Nevermind I think I know why mine isn't there... I've already installed ADB from before. I shall continue on and see what happens :-D
I'm currently running Ubuntu 11.10(Without access to a windows computer to do so.) And after following the steps within the BurritoRoot I get error: insufficient permissions for device when entering adb root. I've rebooted my kindle and laptop as well as changed usb ports.
I've set it up so that it's acknowledged within /.android. Am I perhaps missing something sdk wise? The usb configuration install for extras within it says Linux isn't compatible. But any insight into this would be appreciated I'm not new to Android or adb for that matter. Things seem to be done differently for the Kindle is all.
Thanks guys.
AproSamurai said:
I'm currently running Ubuntu 11.10(Without access to a windows computer to do so.) And after following the steps within the BurritoRoot I get error: insufficient permissions for device when entering adb root. I've rebooted my kindle and laptop as well as changed usb ports.
I've set it up so that it's acknowledged within /.android. Am I perhaps missing something sdk wise? The usb configuration install for extras within it says Linux isn't compatible. But any insight into this would be appreciated I'm not new to Android or adb for that matter. Things seem to be done differently for the Kindle is all.
Thanks guys.
Click to expand...
Click to collapse
adb kill-server
sudo -s
adb devices
should see it now
Quit following me around jcase
Unheard said:
Quit following me around jcase
Click to expand...
Click to collapse
Hah Where you been?
I can not get ADB to recognize the device for the life of me.
I know I have the drivers installed the Fire is recognized as "android composite adb interface" under the Android Phone category in Device manager. But I can not get adb to see it.
"Adb kill-server"
"adb devices"
and it shows no devices attached. Ive done a factory reset on the tablet just to see (knowing it wouldn't make a difference)
Im running Windows XP
if someone could help me out.
notsointeresting said:
I can not get ADB to recognize the device for the life of me.
I know I have the drivers installed the Fire is recognized as "android composite adb interface" under the Android Phone category in Device manager. But I can not get adb to see it.
"Adb kill-server"
"adb devices"
and it shows no devices attached. Ive done a factory reset on the tablet just to see (knowing it wouldn't make a difference)
Im running Windows XP
if someone could help me out.
Click to expand...
Click to collapse
I'm sure its related to windows' drivers but I have no clue. Sorry
jcase said:
adb kill-server
sudo -s
adb devices
should see it now
Click to expand...
Click to collapse
Thanks man, I knew I must have failed to do something. It's much appreciated.
Dis this last night and it worked fine. Thanks!
I did have a few minor stumbles though. It seems the newest version of the software changed the name of the superuser app but the guide still uses the old name in the install command. Once I realized this I just changed the name in the command and it went right in.
Also for some reason I couldn't select the text in the adb box on the web page so I had to enter the commands by hand. No big deal but I would have felt more secure if the commands were in simple text so I could have copy/paste them in.
Like I said though everything worked and I have the market installed now. Thanks for the hard work!
I'm having some trouble with mine...I am trying to follow the video instructions to the link but it shows downloading a .android folder and extracting it to my user name on desktop but there is no such link. I have downloaded SDK and installed google usb drivers as well. I have 6.2.1 firmware and downloaded kindleroot_androidpolice.apk and placed on my kindle and I also downloaded superuser-2. I am not able to install the driver to the fire either. I go to my computer, manage, device manager, kindle, update driver software, browse my computer, etc. I have no INF file to choose under my .android folder.
Any help would be appreciated
My sd card is showing up as unmounted and not sure how to remount it. I sent adb remount and it didn't work. Any help would be appreciated.
Fee454 said:
I'm having some trouble with mine...I am trying to follow the video instructions to the link but it shows downloading a .android folder and extracting it to my user name on desktop but there is no such link. I have downloaded SDK and installed google usb drivers as well. I have 6.2.1 firmware and downloaded kindleroot_androidpolice.apk and placed on my kindle and I also downloaded superuser-2. I am not able to install the driver to the fire either. I go to my computer, manage, device manager, kindle, update driver software, browse my computer, etc. I have no INF file to choose under my .android folder.
Any help would be appreciated
Click to expand...
Click to collapse
would suggest to use this:
http://forum.xda-developers.com/showthread.php?t=1399889
[/COLOR]
b63 said:
would suggest to use this:
http://forum.xda-developers.com/showthread.php?t=1399889
Click to expand...
Click to collapse
This tool will attempt to install the correct Drivers for the Kindle Fire.
It will also perform the setup required for adb_usb.ini in .android for you.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
Press any key to continue . . .
I tried to install the drivers for the kindle but i receive the above message
---------- Post added at 09:56 PM ---------- Previous post was at 09:07 PM ----------
My issue is it cannot find my device...where can I find the kindleADB.zip I keep hearing about?
did you do install_drivers.bat first ?
take a look:
http://forum.xda-developers.com/showpost.php?p=20698002&postcount=283
that should correct the path issue
You should get the same files from the android Sdi. Good luck.
Jcase, I know that you said the unroot button did not work, but is there a method of unrooting?
b63 said:
did you do install_drivers.bat first ?
take a look:
http://forum.xda-developers.com/showpost.php?p=20698002&postcount=283
that should correct the path issue
Click to expand...
Click to collapse
Yes thank you. Moving it to the same as the run.bat seemed to have worked as it shows online now when running the Kindle Fire Utility. I switched it to fast boot but now seems to have been frozen at the kindle fire logo for quite some time now. I heard you have to switch to fastbook to install TWRP first before rooting?
I am not sure if I should attempt to somehow reboot this as it seems to be stuck at the boot up screen
wrong - switch back to normal boot and use the utility
As you see in this post : http://forum.xda-developers.com/showthread.php?t=1162971 , a method to downgrade (or update) when having the error ... so the thing is Gingerbreak was patched in 2.3.5 , or other older versions so the only simple thing is to use another exploit , lets cut through into it , and please post your feedback :
For whoever wants temproot for the use of superuser , Option 1 is the only option for Locked BL+S-ON , but after finishing option 1 , your sdcard will be unmounted (mount it from settings) , and bluetooth won't work unless the phone is rebooted , which means when the root is gone , Option 1 can't allow you to flash CWM , or generally edit /system by any way , but stuff more like SetCPU , Titanium Backup , and similar root apps work ...
OPTION 1
IF you aren't seeing the # in the command prompt that is because you aren't rooted , so you have to use zergRush or Tacoroot , but zergrush is easier :
1. download the temproot.zip and extract it somewhere
2. enable USB debugging on your Wildfire S
3. go to market and download superuser ( doesn't root your phone but it may help )
4. plug your phone and run temproot
5. just watch it , if you see between the lines overseer found a path ,then it worked
6. now to make sure you gained root , try turning on bluetooth , if it did then you are not rooted , also when you open the command prompt , if you type in "adb shell" and seen # , then it worked , if you saw $ , type in the cmd "su" , it should change to # , if it didn't check your phone (superuser will ask to allow or not , just allow it)
This is what i got , please tell if it worked , because it worked for me so it should for you !
I am new to xda in posting and replying stuff , but i know how forums work , so if i asked a question of how this forum works , plz answer .
OPTION 2
I've Got feedback earlier that zergRush didn't work , then this method will state the second root option which is kinda harder and picky-er , so let's cut through into it ...
This exploit is called Tacoroot , and it is mostly used for adb shell root purposes , not for superuser purposes
1. Extract the Tacoroot simple.zip somewhere and enable USB Debugging at settings >applications>development
2. Enable USB debugging from Settings> Applications > Development
3. Now run Step1
4. After the phone reboots to recovery , press both vol + and power button in the same time until a menu of four shows up , then make sure you got reboot system is highlighted (it may not be called reboot system , but something similar) and press the power button
5. when the phone boots , run Step2
6. Redo step 4
7. Now after it boots run step3
8. That's It ! you got root ! now open up a cmd , cd to the adb directory , and type in adb shell , then su , and it should show # , which confirms the root
!
WARNING : you will have a bootloop now while you have the adb root , and if you have finished what you need with the root , to get unrooted and boot normally just run Undo .
does not work for me: (
i have problem, look:
***************************************
*** HTC Wildfire S Temporary root ****
******** by wiseminosse 2011 **********
running step 1...
adb server is out of date. killing...
* daemon started successfully *
rm failed for /data/local/tmp/boomsh, No such file or directory
running step 2...
rm failed for /data/local/tmp/sh, No such file or directory
running step 3...
397 KB/s (23056 bytes in 0.056s)
running step 4...
running step 5...
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00016118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
running step 6...
rm failed for -f, Read-only file system
mount: Operation not permitted
running step 7...
Unable to chmod /sbin: Read-only file system
running step 8...
Click to expand...
Click to collapse
PeMo19946 said:
does not work for me: (
i have problem, look:
Click to expand...
Click to collapse
did you enable usb debugging ??
yes.. maybe i have problems with computer..
for me it worked like a charm , give me your software specifications please (s-on/s-off , unlocked/locked bootloader ... )
s-off
bootloader locked ;/
i can't unlock bootloader but i have bad software
I must try tomorrow in Windows XP
well done ,so useful
Permanent root for S-off and unlocked bootloader WFS
PeMo19946 said:
s-off
bootloader locked ;/
i can't unlock bootloader but i have bad software
I must try tomorrow in Windows XP
Click to expand...
Click to collapse
hey , try removing the usb debugging and then re-enable it , it might help , also don't run temproot in cmd , just go to the folder and run it !
more over , you are s-off , meaning you can get permananet root ! go to shortfuse.org and download superoneclick ,extract it somewhere , and run superoneclick , all you have to do just click root ! and answer anything it asks you , then reboot the phone , you'll have perm root !!
EDIT : it is downloaded from http://depositfiles.com/files/n0dcxce3t
Make More internal storage !!
Check out my new tutorial , thanks to Jikantaru ! Make a lots of storage on your picky Wildfire S !
http://forum.xda-developers.com/showthread.php?p=22520350#post22520350
This is an expanded version of Jikantaru's tutorial and more precise !
PeMo19946 said:
s-off
bootloader locked ;/
i can't unlock bootloader but i have bad software
I must try tomorrow in Windows XP
Click to expand...
Click to collapse
maybe i got your problem , look , when first choosing HTC sync , it might open HTC sync on the PC , so open up task manager(on PC) , and go to the processes tab , end every process that carries htc on it , then try redoing the thing !
Sorry, i have S-ON, sorry. I must try all steep in XP, maybe help
I give know ..
well please post your feedback here please
Does not work on XP, still the same error with the lack of access to files.
are you following the instructions correctly
cuz it is a temproot that should work on any wildfire s , give your software info please , go to settings about and there find and tell me your software specifications
Android version 2.3.5
HTC Sense version 2.1
Software number 2.17.531.1
More:
Kernel version
2.6.35.10-g8409c43
[email protected] #1
Wed Nov 16 17:52:43 CST 2011
Baseband version
47.23b.35_3035H_7.53.39.11M
Build number
2.17.531.1 CL214145 release-keys
Tacoroot , option 2
What on earth ?! 2.17 ?! Then you only have tacoroot to work , I will be updating my main post for the use of tacoroot then , it may take time ...
Oh, this is a way to give me all this work?
PeMo19946 said:
Oh, this is a way to give me all this work?
Click to expand...
Click to collapse
Tacoroot Gives you temproot access to any HTC phone , although you might not access the phone directly from the touchscreen , but you will only see a bootloop , while this loop is looooopppiinggg , you have root access through the adb shell , which will give you what is required "ROOT ACCESS" !
PeMo19946 said:
Oh, this is a way to give me all this work?
Click to expand...
Click to collapse
Post Updated , check it for the tacoroot ...
still error, driving me crazy! want to smash the phone right now
how to remove a wrong post?
Just got a "factory refurbished" Kindle Fire 8.9 HD for a STEAL (Amazon gave $50 back on the refurb).
Anyway, now that I have it and have been playing with it for a few weeks, I've realized that the current root methods (including Root Many Android) say they have rooted it, but I don't quite have all the SU access. Digging deeper, I've found that I have System Version 8.4.9.
I can get a partial root, but cannot mount the system to RW
Anyone out there working on the Root of Kindle Fire 8.4.9?
I would just downgrade it and flash a custom rom.
Sent from my Amazon Tate using Tapatalk
stunts513 said:
I would just downgrade it and flash a custom rom.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
Stunts,
I'd love to do that, but one of the issues with the current root is I can't use KFFirstAide to do much of anything. I would like to keep the KF as close to stock as I can, as I have kids and the FreeTime app is nice. I'm mostly looking to get the Google Play store up and working.
I've done a search but don't see anything on how to downgrade the KF from 8.4.9 without having root.
What am I missing?
You don't need root. When you initially power the device on it should briefly be detected as a jem device. Download then drivers in my signature and extract them somewhere. Now open the device manager and plug the kindle in while off, when you see the jem device, right click it and hit update drivers, and tell it to look where you extracted mine. If this is windows 8 you will have to disable driver signature enforcement first. If you can manage to get this step completed the rest is simple, it basically involves this: grab a utility like kindle fire first aid and shift + right click it and hit new command window here. With the kindle off and unplugged type
Code:
fastboot -I 0x1949 getvar product
once it says waiting for device plug the kindle in while it is off, it should enter fastboot, from there you can use kffa to downgrade it.
Sent from my Amazon Tate using Tapatalk
stunts513 said:
You don't need root. When you initially power the device on it should briefly be detected as a jem device. Download then drivers in my signature and extract them somewhere. Now open the device manager and plug the kindle in while off, when you see the jem device, right click it and hit update drivers, and tell it to look where you extracted mine. If this is windows 8 you will have to disable driver signature enforcement first. If you can manage to get this step completed the rest is simple, it basically involves this: grab a utility like kindle fire first aid and shift + right click it and hit new command window here. With the kindle off and unplugged type
Code:
fastboot -I 0x1949 getvar product
once it says waiting for device plug the kindle in while it is off, it should enter fastboot, from there you can use kffa to downgrade it.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
Tried to downgrade. I can get to fastboot without any issues, but it looks like there are issues with KFFA (I'm using 4.1.87-beta). I get the following when trying to "Completely Restore the KFHD 8.9 8.1.4" (Option 7)
(snipped to the last one for space, all have the final "Unable to establish SSL Certificate)
**********************************************************************
*I Have Fetched The recovery.img - 1 More To Download................*
**********************************************************************
--2014-06-14 13:04:18-- y
<snip> (don't have 10 posts so can't post all the links)
HTTP request sent, awaiting response... 302 FOUND
Cookie coming from address attempted to set domain to dropbox.com
Cookie coming from address attempted to set domain to dropbox.com
Location: (removed as I don't have 10 posts)] [following]
--2014-06-14 13:04:18-- (removed as I don't have 10 posts)
Connecting to address... connected.
ERROR: cannot verify address's certificate, issued by `address High Assurance Server CA':
Unable to locally verify the issuer's authority.
To connect to address insecurely, use `--no-check-certificate'.
Unable to establish SSL connection.
****************************************************************************************
*I Have Fetched The system.img - I Am Ready To Flash The 3 Images......................*
****************************************************************************************
Press any key to continue . . .
target reported max download size of 1006632960 bytes
error: cannot load 'boot.img': No error
target reported max download size of 1006632960 bytes
error: cannot load 'recovery.img': No error
target reported max download size of 1006632960 bytes
error: cannot load 'system.img': No error
Would You Like To Wipe Data And Cache (y/n) ?
After this, I wipe data and cache and then didn't finish the registration (so I didn't get "pushed" an update, just in case)
Come back up and I'm still in 8.4.9
I've gone in to dropbox and pulled all the images to my computer. Is there a way to move these and get them properly mounted in adb? I'm a relative n00b but getting a bit more comfy in the adb environment and may be able to do it from there, with a bit of help?
Thanks!
Do not actually use KFFA use this method --> http://forum.xda-developers.com/showthread.php?t=2468988
You only need kffa for adb.exe and fastboot.exe ect.
PS. Be sure NOT to to connect to the Internet after until you have OTA blocked, and if you Like you can manually upgrade to what ever firmware you would like, I went back to v848
jmpiv4 said:
Do not actually use KFFA use this method --> http://forum.xda-developers.com/showthread.php?t=2468988
You only need kffa for adb.exe and fastboot.exe ect.
PS. Be sure NOT to to connect to the Internet after until you have OTA blocked, and if you Like you can manually upgrade to what ever firmware you would like, I went back to v848
Click to expand...
Click to collapse
Now I'm stuck in the Kindle Fire boot screen - orange. I got through all the flashes without an issue and unplugged on the final reboot per your instructions. I try to adb to it and there are no devices found.
Edit: Whoops. Was using my old shortcut command keys (arrows) and just changed what flashed to system - forgot to flash to the right places. Trying again!
Illinifan97 said:
Now I'm stuck in the Kindle Fire boot screen - orange. I got through all the flashes without an issue and unplugged on the final reboot per your instructions. I try to adb to it and there are no devices found.
Edit: Whoops. Was using my old shortcut command keys (arrows) and just changed what flashed to system - forgot to flash to the right places. Trying again!
Click to expand...
Click to collapse
Hi guys, thx for all tutorials in this site, but i can't root my Kindle Fire HD 8.9...this is the error
"/system/bin/sh su cannot execute permission denied "
KatanAlive said:
Hi guys, thx for all tutorials in this site, but i can't root my Kindle Fire HD 8.9...this is the error
"/system/bin/sh su cannot execute permission denied "
Click to expand...
Click to collapse
Is your Kindle up and running? I also have a Kindle Fire HD 8.9 and yesterday I downloaded latest update.bin file (8.4.9) from Amazon and updated my Kindle and later rooted it using the manual method described in http://forum.xda-developers.com/showthread.php?t=2069117 thread. It was total success. Just don't miss a single step from that method.
Actually I had my Kindle (ver 8.4.8) rooted before and Google Play installed with the same method but I was having some issues (not because of rooting but because I had been tinkering with the system apps) so decided to update to overcome those glitches. I installed RootKeeper from Google Play and told it to protect my root access during update process but this crap could not. After update I lost my root and now Google Play Store and related services stopped working, as I didn't have root access so couldn't manage to delete their apks from System apps. So I decided to root it again with the same method and I did it, after rooting it again I went to system apps and deleted old apks of Google Play and other related apks. Then I agin installed Google Play using the automatic method mentioned in above thread.
Sorry if this story is irrelevant but I just wanted to share my experience so any one searching for something could find a clue from it. One thing is confirmed here, KFFirstAid can easily install Google Play after 8.4.9 update and the above mentioned manual method can root it successfully. I am not sure about automatic method though.
you have been very usefull! Thx...but, i still can't root with any method
Can i ask you for some help (i've actually the 8.4.9 version) in private?
KatanAlive said:
Hi guys, thx for all tutorials in this site, but i can't root my Kindle Fire HD 8.9...this is the error
"/system/bin/sh su cannot execute permission denied "
Click to expand...
Click to collapse
KatanAlive said:
you have been very usefull! Thx...but, i still can't root with any method
Can i ask you for some help (i've actually the 8.4.9 version) in private?
Click to expand...
Click to collapse
Of course. I am not very knowledgable but I would try my best to share my experience.
akb1ajay said:
Of course. I am not very knowledgable but I would try my best to share my experience.
Click to expand...
Click to collapse
I write you a pm
I just tried the fastboot stuff and it will not enter fastboot. Do i need a fastboot cable?
Also i would like to remove all things kindle aka custom roms. So thats a non issue meaning if the only way to root a hd 8.9 with 8.4.9 rom version that was some how pushed on to my kindle via ota that i had turned off but got turned back on some how. Then thats fine and infact i want to remove amazons crap rom any how.
Nanaki-seto said:
I just tried the fastboot stuff and it will not enter fastboot. Do i need a fastboot cable?
Also i would like to remove all things kindle aka custom roms. So thats a non issue meaning if the only way to root a hd 8.9 with 8.4.9 rom version that was some how pushed on to my kindle via ota that i had turned off but got turned back on some how. Then thats fine and infact i want to remove amazons crap rom any how.
Click to expand...
Click to collapse
Read post 9 on previous page.
akb1ajay said:
Read post 9 on previous page.
Click to expand...
Click to collapse
Already tried this. It works partially only once it is fully done rebooting the kindle fire is running so slowly as to be unworkable for any thing. Also the lock swipe etc looks torn inhalf. At this point i have to use recorvery to get it to respond properly. I need to root or change rom out right (preferably) But the fast boot commands do nothing. Tried getting it to show up as gem device and use the other drivers that are suppose to let me enter fast boot by a fastboot command. It does not seem to work.
So after trying the method in post 9 again i need to recover to factory again. As it is running extremely slow
stunts513 said:
I would just downgrade it and flash a custom rom.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
Stunts what is the best surefire way to downgrade? My previously rooted kindlefire hd 8.9 just got ota updated to 8.4.9. I had disabled ota i thought but it would seem it wasnt. Now i can not reroot it properly. I want to just go with a custom rom and be done with this mess. I do not have a fastboot cable. But it would seem there are ways around that such as the fastboot -i etc etc how ever i tried that and it did not work (including getting the drivers to the jem. I think i may be missing the chance to get the update drivers bit done intime (not sure here). At any rate help!!! heh
Again what i want to do
Downgrade to easiest rom ver to flash from to a custom rom using what ever meathod is the most effective minus fastboot cable. also recommendations on rom to use are very welcome.
akb1ajay said:
Is your Kindle up and running? I also have a Kindle Fire HD 8.9 and yesterday I downloaded latest update.bin file (8.4.9) from Amazon and updated my Kindle and later rooted it using the manual method described in http://forum.xda-developers.com/showthread.php?t=2069117 thread. It was total success. Just don't miss a single step from that method.
Actually I had my Kindle (ver 8.4.8) rooted before and Google Play installed with the same method but I was having some issues (not because of rooting but because I had been tinkering with the system apps) so decided to update to overcome those glitches. I installed RootKeeper from Google Play and told it to protect my root access during update process but this crap could not. After update I lost my root and now Google Play Store and related services stopped working, as I didn't have root access so couldn't manage to delete their apks from System apps. So I decided to root it again with the same method and I did it, after rooting it again I went to system apps and deleted old apks of Google Play and other related apks. Then I agin installed Google Play using the automatic method mentioned in above thread.
Sorry if this story is irrelevant but I just wanted to share my experience so any one searching for something could find a clue from it. One thing is confirmed here, KFFirstAid can easily install Google Play after 8.4.9 update and the above mentioned manual method can root it successfully. I am not sure about automatic method though.
Click to expand...
Click to collapse
This worked for getting root back, but didn't initially work for the Google apps. It looks like Amazon filled the file system /system leaving no room for the apps. Since I don't use Text To Speech, I removed /system/tts/ivona/vox_en_us_salli22i which is 100+MB, freeing plenty of space for Google apps. I saved a copy to /sdcard just in case. I recommend saving a copy of system.img first, since my first attempts at removing files deleted the apk, but didn't free the space and I had to do a restore once.
Full Manual Root - Kindle Fire HD 8.9 System Version 8.4.9 on Ubuntu Linux 14.04
Hi Guys,
If none of the usual methods work, here is a method for rooting Kindle Fire HD 8.9 with the new 8.4.9 system version. It was written for and tested on Linux, but should work on Windows as well.
Requires Linux and "DOS" scripting knowledge - particularly if anything goes wrong. If you are not familiar with linux shell, please do not try!
USE AT YOUR OWN RISK!!!
I was struggling a whole day with rooting my Kindle Fire HD 8.9 with the 8.4.9 stock rom. I use Linux (Ubuntu 14.04) and don't really have access to Windows. I've tried several methods, including several versions of the Bin4ry method, but the result was:
a) nothing happened at the end,
b) the system was hell slow, but did not get the root prompt/access.
Finally I've managed to root with a full manual - no script running - method. It was based on Bin4ry v18.5.1 root: the tools were uploaded to the kindle from the package, and the rooting steps were based on the RunMe.bat (manually entering step-by-step). It requires an installed adb on the linux machine (I have it from an Android SDK install)!
Sources:
http://forum.xda-developers.com/showthread.php?t=2277105 : I've started from here. I recommend to read this before starting the process.
http://forum.xda-developers.com/showthread.php?t=2069117 : "C-2) The next steps are used to Root the Kindle - Alternative Method (Manual Version)"
http://pocketnow.com/2012/10/10/root-without-unlocking : for understanding the exploit
Requirements:
1. Install adb on the linux machine.
2. Download Root MANY ANDROID 32-bit!(Dropbox): https://dl.dropbox.com/u/54456659/Win32.zip and extract.
Rooting:
The steps are based on manually entering the commands of the "1)Normal" method of the RunMe.bat:
1) In a terminal change to the directory where Win32.zip was extracted and enter:
Code:
adb push stuff/busybox /data/local/tmp/.
adb push stuff/su /data/local/tmp/.
adb push stuff/Superuser.apk /data/local/tmp/.
adb shell chmod 755 /data/local/tmp/busybox
2) Restore the fake “backup”. Note: _do not click restore on your Kindle device_! Just enter the command into the command prompt on your PC and press the enter key:
Code:
adb restore fakebackup.ab
3) Run the “exploit”:
Code:
adb shell “while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done”
(It will display a lot of "link failed File exists" lines)
4) Now that the “exploit” is running, click restore on your device.
5) Once it finishes, reboot your device. Note: Don’t use your kindle yet, this exploit reboots into emulator mode which will be laggy with a flickering screen (or no display at all). This is normal.
Code:
adb reboot
6) Once rebooted, open a shell:
Code:
adb shell
Check: Once you do step 6, your should have a root shell (your prompt should be #, not $). If it’s not #, start again from step 2.
7) Continue with the steps of the RunMe.bat - now entering the commands in the root shell:
Code:
/data/local/tmp/busybox mount -o remount,rw /system
/data/local/tmp/busybox mv /data/local/tmp/su /system/xbin/su
/data/local/tmp/busybox mv /data/local/tmp/Superuser.apk /system/app/Superuser.apk
/data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin/busybox
chown 0.0 /system/xbin/su
chmod 06755 /system/xbin/su
chmod 655 /system/app/Superuser.apk
chmod 755 /system/xbin/busybox
rm /data/local.prop
reboot
Done .
The Method described above didn't work for me.
Tried to do it step by step but the exploit part is not working, gives me a syntax error.
Then i used runme.bat and the exploit seems to work (slow reboot, scrambled kindle logo) but root isn't working properly afterwards.
It's kinda half-rooted now, with SuperSU working and displaying "granted root access..."-messages but if i try to install the play store i'm stuck.
ESexplorer is in root mode, mounted system R/W but when i try to move vending.apk to system/app it fails. No root access it seems
Opening SuperSU results in a failed update process....
Any kind of help is deeply appreciated...
Fixing that syntax error
Toastytwo said:
The Method described above didn't work for me.
Tried to do it step by step but the exploit part is not working, gives me a syntax error.
Then i used runme.bat and the exploit seems to work (slow reboot, scrambled kindle logo) but root isn't working properly afterwards.
It's kinda half-rooted now, with SuperSU working and displaying "granted root access..."-messages but if i try to install the play store i'm stuck.
ESexplorer is in root mode, mounted system R/W but when i try to move vending.apk to system/app it fails. No root access it seems
Opening SuperSU results in a failed update process....
Any kind of help is deeply appreciated...
Click to expand...
Click to collapse
This method worked for me! I also got a syntax error the first time arround but I fixed it by splitting this command (adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done") into 2 separate command 1) adb shell, 2) while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done
After taking away the quotes it worked exactly as described!
AFTV 1.
I just rooted using kingroot. Then tried to swipe kingsuer by supersu. Something happened.
Therefore, I have no CWM or others. I do not have boot menu.
I have a USB cable. I've tried fastboot devices but no devices found.
I've tried adb reboot recovery and I was into Amazon system recovery <3>, but there was on recovery menu at all.
Please help. It looks I could use shell and su, but not fastboot.
I am not an expert so please forgave my languages.
Thanks.
C:\adb>cmd.exe C:\adb
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\adb>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ $ su
1|[email protected]:/ $ reboot recovery
C:\adb>
vincentjones said:
AFTV 1.
I just rooted using kingroot. Then tried to swipe kingsuer by supersu. Something happened.
Therefore, I have no CWM or others. I do not have boot menu.
I have a USB cable. I've tried fastboot devices but no devices found.
I've tried adb reboot recovery and I was into Amazon system recovery <3>, but there was on recovery menu at all.
Please help. It looks I could use shell and su, but not fastboot.
I am not an expert so please forgave my languages.
Thanks.
C:\adb>cmd.exe C:\adb
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\adb>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ $ su
1|[email protected]:/ $ reboot recovery
C:\adb>
Click to expand...
Click to collapse
Don't know if this will work but here's a link you may wanna try -
http://forum.xda-developers.com/showthread.php?t=2799779
If you don't get any joy sit tight cause I'm sure rbox may make a in bricking image at sum point like he did with our AFTV2 so don't panic just play the waiting game ok.
If this helps press that thanks button
supersume is causing issues with devices. lots of threads open regarding this.
why did you need root for if you are not good at understanding?
vincentjones said:
AFTV 1.
I just rooted using kingroot. Then tried to swipe kingsuer by supersu. Something happened.
Therefore, I have no CWM or others. I do not have boot menu.
I have a USB cable. I've tried fastboot devices but no devices found.
I've tried adb reboot recovery and I was into Amazon system recovery <3>, but there was on recovery menu at all.
Please help. It looks I could use shell and su, but not fastboot.
I am not an expert so please forgave my languages.
Thanks.
C:\adb>cmd.exe C:\adb
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\adb>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ $ su
1|[email protected]:/ $ reboot recovery
C:\adb>
Click to expand...
Click to collapse
You should had visit this forum and read first before you removed kingroot with superuser, box is bricked for now and your only hope is ....rbox. Removing kingroot with superuser will brick your box!
Wait for him to release OS5 recovery for fireTV 1 and he may be releasing an unbrick image as he did for fireTV 2. This is your only hope for now anyway.
I knew there was a risk but I did it anyway. Now I regret it.
Actually I saw the firetv2 unbrick image and I was almost started to try it for my fireTV 1 before I posted this help post. Now I know I should wait.
Thanks a lot.
I really appreciated.
bula1ca said:
You should had visit this forum and read first before you removed kingroot with superuser, box is bricked for now and your only hope is ....rbox. Removing kingroot with superuser will brick your box!
Wait for him to release OS5 recovery for fireTV 1 and he may be releasing an unbrick image as he did for fireTV 2. This is your only hope for now anyway.
Click to expand...
Click to collapse
Supersume was what I used.
I do not know why I did it. I just can not help doing it even I know it was stupid. Maybe it was the new feature or the desire of getting rid of kinguser.
Thanks a lot.
El_Nino9 said:
supersume is causing issues with devices. lots of threads open regarding this.
why did you need root for if you are not good at understanding?
Click to expand...
Click to collapse
deanr1977 said:
Don't know if this will work but here's a link you may wanna try -
http://forum.xda-developers.com/showthread.php?t=2799779
If you don't get any joy sit tight cause I'm sure rbox may make a in bricking image at sum point like he did with our AFTV2 so don't panic just play the waiting game ok.
If this helps press that thanks button
Click to expand...
Click to collapse
I've tried the keyboard method and no luck.
I better just wait.
Thanks.
There is no way to create an unbricking image for the FireTV1 if your bootloader is locked.
rbox said:
There is no way to create an unbricking image for the FireTV1 if your bootloader is locked.
Click to expand...
Click to collapse
Cheers for clearing that up rbox
vincentjones said:
I've tried the keyboard method and no luck.
I better just wait.
Thanks.
Click to expand...
Click to collapse
Oh well sorry mate but unless someone else has any ideas you have your answer above
Sent from my SM-G900F using Tapatalk
Thanks a lot. rbox.
rbox said:
There is no way to create an unbricking image for the FireTV1 if your bootloader is locked.
Click to expand...
Click to collapse
rbox said:
There is no way to create an unbricking image for the FireTV1 if your bootloader is locked.
Click to expand...
Click to collapse
that sucks big time glad i got an FTV 2 with the whole preloader method which can take 2 hours or so but at least revive.
i was thinking if he has adb, can he not push an official update to it and revive it?
the keyboard trick usually works but i understand it hasn't for this user. can official recovery not do adb side load?
a shame to see the device go like that.
i've had to unplug my stick. i disabled OTA using adb yet it still updated and it causes issues with watching stuff it just leaves the video and i have to load it again. got annoying. i'll just wait
El_Nino9 said:
that sucks big time glad i got an FTV 2 with the whole preloader method which can take 2 hours or so but at least revive.
i was thinking if he has adb, can he not push an official update to it and revive it?
the keyboard trick usually works but i understand it hasn't for this user. can official recovery not do adb side load?
a shame to see the device go like that.
i've had to unplug my stick. i disabled OTA using adb yet it still updated and it causes issues with watching stuff it just leaves the video and i have to load it again. got annoying. i'll just wait
Click to expand...
Click to collapse
su would need to be working to put an official update on it.
rbox said:
su would need to be working to put an official update on it.
Click to expand...
Click to collapse
i guess the only way is hardware mod and write the files directly.
Freakin SuperSU me. I wish I wouldn't have been so stupid to try it.
mrchrister said:
Freakin SuperSU me. I wish I wouldn't have been so stupid to try it.
Click to expand...
Click to collapse
I was lucky I tried it about 10times but it wouldn't work.... after the reports of bricks come I was so happy it didnt work. I feel sad for you unlucky people who bricked with that app! It's a shame
Sent from my SM-G900F using Tapatalk
same happened here .. 'supersu me' didnt work. after a reboot root was lost and supersu didnt work ... so i tried supersu me pro which messed it up.
i wish i never tried super sume either .. my fire tv is bricked also!!
yep. supersu me cost me $100. now i got the new firetv 2 already rooted. i still want to revive the bricked firetv through mmc hardware access.
Sent from my iPhone using Tapatalk
mrchrister said:
yep. supersu me cost me $100. now i got the new firetv 2 already rooted. i still want to revive the bricked firetv through mmc hardware access.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
somebody mentioned in reddit about "EMMC chip".
I am waiting for his progress report.
It is possible to unbrick the firetv through soldering 4 cables on the logic board. Google for 'exploitee emmc firetv' and you will find an online shop selling the adapter to communicate with the firetv's emmc (its internal hard drive) for $17. I just got the adapter but I don't have a fine enough soldering iron tip yet. The contacts on the logic board of the firetv are tiny, so you really need to know what are you doing. Should you succeed with soldering it on you can then reflash the system partition through the dd command to unbrick.
Sent from my X98 Air III(M5C5) using Tapatalk