THIS IS ONLY FOR FIRETV1 RUNNING FIREOS3 WITH UNLOCKED BOOTLOADER!
It's finally here! Recovery for the Fire TV. This is based off of CWM and the way versions will work is I will append an extra digit to the end of the CWM version. So 6.0.5.0.0 is my first release based off of 6.0.5.0. I will also be releasing a recovery based off of TWRP, at some point.
As usual, this WILL void your warranty and I am NOT responsible for anything you do with this. Installing it properly won't brick your Fire TV, but doing stupid things with it might. Of course, this requires that you are rooted to begin with.
Installation
Unlock the bootloader: You must first unlock your bootloader. Failing to do this will result in recovery not working.
Copy: Copy the recovery.img to Fire TV via adb, or whatever else you like.
Flash: From an adb shell, run
Code:
su
to get to root and then
Code:
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Replacing /sdcard/recovery.img with the directory and name of file that you copied.
Reboot:
Code:
adb reboot recovery
Profit
Upgrade
The same as installation, just skip step 1.
Notes
Note that it does take a few seconds for it to start. The screen will be black, don't be alarmed. As long as the Amazon logo disappears, it is loading.
This comes with DHCP enabled ethernet, please don't ask about wifi. Maybe at some point I'll get that working, but for now it's not going to happen. When recovery starts, it will print out it's IP address. Note that this might be different from the one it gets while booted into the OS. This works with USB storage and USB input devices. Right now, it does not support input hotplug so unless you have a keyboard plugged in when it boots, it won't work. This will be fixed. Unpowered USB hubs are hit or miss. Powered should always work.
There are protections against flashing an unmodified stock image. Under no circumstances should you ever attempt to flash such an image. You can download modified stock images here.
[size=+2]If something fails to flash DO NOT reboot. Try again and/or retransfer the file over adb.[/size]
AOSP, custom kernels, etc
When using custom kernels be extra careful. If you are developing a kernel, it is best to flash recovery to the boot partition and the new kernel to test to the recovery partition. There is no known way of booting into recovery if your kernel can't boot. In the future, I plan on releasing a "boot menu" program to help with this situation.
USB Storage
USB storage should be working. When you go to the backup/restore menu, /storage/usbdisk should be one of the options. When you go to the install screen /storage/usbdisk should be one of the updates. FAT32 and ext4 should work. NTFS formatted partitions will not show up as an option.
Overscan
To accommodate people who need to apply overscan for their TV, I have enabled configurable overscan. By default it is disabled. You can control the amount of overscan either with FastForward and Rewind buttons or the 1 and 2 buttons. It will save it so the next time it reboots it will remember your choice.
adb sideload
Installing zips with sideload is the easiest method. Select sideload as the option to install, then from your computer run adb connect followed by adb sideload.
Controlling from the commandline
If you have no keyboard or cannot connect a keyboard, I wrote a little program called recovery-input that allows you to control recovery from an adb shell. @AFTVnews.com wrote a guide at http://www.aftvnews.com/how-to-remotely-control-clockworkmod-on-the-amazon-fire-tv-using-adb/
[size=+2]Finally, thanks to everyone who has donated![/size]
Changelog and Downloads:
Nov 02, 2014 - 6.0.5.1.4a (md5sum: 67b1a13b7bec645cb9291e80478d4635)
Added the missing recovery-input program
Nov 01, 2014 - 6.0.5.1.4 (md5sum: 9ba1ee7a914fad9e9c5509db4677e3e9)
Fix ext4 external usb support.
Removed kernel patching. This recovery now REQUIRES the bootloader to be unlocked.
Oct 19, 2014 - 6.0.5.1.3 (md5sum: 4984a2ae6489422298557d32cd2386b7)
Enable vi in busybox
Enable adjustable overscan
Allow flashing custom kernels
Oct 05, 2014 - 6.0.5.1.2 (md5sum: ae21891b4fd1e58c513ae5cdd09f4d93)
Print the current IP address on start
Disable automatic flashing
Disable install-recovery warning
Don't show unmountable NTFS partitions
Sep 27, 2014 - 6.0.5.1.1 (md5sum: bd490fd43f287b7ea01a6cc9d00b2232)
Fixed USB storage behind a hub
Sep 26, 2014 - 6.0.5.1.0 (md5sum: f82eccfd3638909f02eea1ca59e1b2a2)
Fixed USB storage
Enabled overscan
adb sideload over network
Larger font
Sep 19, 2014 - 6.0.5.0.0 (md5sum: 5c126edda9ea12696bebee7e368841e5)
First release
Awesome! Thanks so much for your hard work Rbox :good: :highfive:
Edit:
Installed without issues. Remote not working as expected so I switched to the K400 and works 100% Great work, donated $10 for your efforts!
Here are some guides with step by step instructions:
How to install ClockworkMod Custom Recovery on the Amazon Fire TV
http://www.aftvnews.com/how-to-install-clockworkmod-custom-recovery-on-the-amazon-fire-tv/
How to update ClockworkMod Custom Recovery on the Amazon Fire TV
http://www.aftvnews.com/how-to-update-clockworkmod-custom-recovery-on-the-amazon-fire-tv/
How to remotely control ClockworkMod on the Amazon Fire TV using ADB
http://www.aftvnews.com/how-to-remotely-control-clockworkmod-on-the-amazon-fire-tv-using-adb/
How to install a Custom ROM Image on the Amazon Fire TV
http://www.aftvnews.com/how-to-install-a-custom-rom-image-on-the-amazon-fire-tv/
How to update a Rooted Amazon Fire TV to the Latest Version Without Losing Root
http://www.aftvnews.com/how-to-upda...tv-to-the-latest-version-without-losing-root/
How to Revert back to Stock Recovery and Stock Software
http://www.aftvnews.com/how-to-revert-an-amazon-fire-tv-back-to-stock-recovery-and-stock-software/
..
Should adb sideload work over tcpip rather than just usb?
If so it doesn't work for me; soon as it's toggled in recovery the firetv isn't accessable over adb tcpip anymore.
Luxferro said:
Should adb sideload work over tcpip rather than just usb?
If so it doesn't work for me; soon as it's toggled in recovery the firetv isn't accessable over adb tcpip anymore.
Click to expand...
Click to collapse
I never tested it. The problem with sideload is I believe it restarts the adb daemon. I'll see if I can figure out what's wrong with it.
Update: So I just tested it and looked in to the code. It looks like when recovery starts, it uses the full adbd. But when you go to do a sideload, it switches to the internal version called minadbd. minadbd only supports USB. So for the next version I will add in network support.
Any way to use CWM to make a backup when there isn't enough free internal memory for the backup files? Like backing up to a mounted USB drive or network location.
AFTVnews.com said:
Any way to use CWM to make a backup when there isn't enough free internal memory for the backup files? Like backing up to a mounted USB drive or network location.
Click to expand...
Click to collapse
If you have a USB drive plugged in before it starts, it *should* see it. I haven't tested it in a while but it was working at one point. But like I said, I was having problems getting it to work with a hub with a flash drive and a keyboard. I suppose if you created a commands file that told it to backup to the external storage and reboot afterwards, it wouldn't need a keyboard plugged in. If you can't get your USB drive to work, I'll figure out the commands file.
nice job i thought before summer ended we would have a recovery. i cant wait for a ROM for the FTV . fingers crossed. also can i use firmware version 51.1.0.1 instead of 51.1.0.2? id rather not "update" if it isn't necessary and im guessing the difference between the two makes no difference.
edit: dosent matter i upgraded and installed. recovery working just fine. thank u rbox.
I don't have the fire TV yet and I don't know anything about the software of this thing, but wouldn't it be easier if we can boot into fastboot? With that every firmware version could be flashed. There was a fastboot cable for the fire tablet. Can't we build something like this for the fire tv?
alex1301 said:
I don't have the fire TV yet and I don't know anything about the software of this thing, but wouldn't it be easier if we can boot into fastboot? With that every firmware version could be flashed. There was a fastboot cable for the fire tablet. Can't we build something like this for the fire tv?
Click to expand...
Click to collapse
Yes, it would be easier. And a fastboot cable for the Fire TV is just a plain USB A to A cable. But the bootloader is locked and prevents one from using fastboot boot and fastboot flash.
rbox said:
Yes, it would be easier. And a fastboot cable for the Fire TV is just a plain USB A to A cable. But the bootloader is locked and prevents one from using fastboot boot and fastboot flash.
Click to expand...
Click to collapse
Alright, I hate it when they lock the bootloader so deep that we can't unlock it
rbox said:
(you made a backup before attempting to flash something, right?)
Click to expand...
Click to collapse
No
Can you upload "stock_recovery.img"? I didn't downgrade to 51.1.0.2 :silly:
Kramar111 said:
No
Can you upload "stock_recovery.img"? I didn't downgrade to 51.1.0.2 :silly:
Click to expand...
Click to collapse
I ask one simple thing. That people follow the directions. Is that so hard to do?
http://www.mediafire.com/download/6q1c96y5tcc4xgc/recovery-stock-51.1.0.img
CLran619 said:
also can i use firmware version 51.1.0.1 instead of 51.1.0.2? id rather not "update" if it isn't necessary and im guessing the difference between the two makes no difference.
Click to expand...
Click to collapse
I am wondering the same thing as I am still on 51.1.0.1 as well.
Sent from my SCH-I545 using Tapatalk
collindv said:
I am wondering the same thing as I am still on 51.1.0.1 as well.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I just updated the post to reflect that you only need to downgrade if you are on 51.1.1.0.
Luxferro said:
Should adb sideload work over tcpip rather than just usb?
If so it doesn't work for me; soon as it's toggled in recovery the firetv isn't accessable over adb tcpip anymore.
Click to expand...
Click to collapse
I was able to get sideload over network working, so that will be included in my next update. Thanks!
Anyone know a way of determining firmware revision from the command line?
jocala said:
Anyone know a way of determining firmware revision from the command line?
Click to expand...
Click to collapse
Code:
grep fingerprint /system/build.prop
Is there anyway to boot into ClockworkMod recovery other than via the "adb reboot recovery" command? I'm guessing the Alt+PrintScreen trick would take you there, yes? Any other ways?
Related
I just went through the unlock and root it is fresh in the mind. These directions ASSUME AN SD CARD IS INSTALLED to the tablet and a WINDOWS OS!
Downloads, get them and put them in a folder on your computer:
Asus Unlock Tool download link from ASUS:
http://support.asus.com/Download.as...ck_Device_App_V6.apk#UnLock_Device_App_V6.apk
Fastboot EXE:
I got fastboot.exe when I downloaded Ultimate Backup Tool from here:
http://goo.gl/iOUwe
Unzip it so you have fastboot.exe
TWRP:
Get TWRP for TF201Jellybean, here is their page I have posted the download link below:
TWRP Page
On that page are instructions including a download link.THIS LINK IS FOR TF201 RUNNING JB BOOTLOADER ONLY! DO NOT USE IT IF YOU ARE NOT SURE WHAT YOU ARE RUNNING STOP NOW!
TWRP Download for TF201 running STOCK JellyBean OS:
http://techerrata.com/file/twrp2/tf201/openrecovery-twrp-2.3.1.0-tf201-jb.blob
MD5 Checker:
When TWRP is downloaded you can compare the MD5 hash of what you downloaded to confirm it is the a good download. If you don' do this and flash a bad copy of TWRP your tablet is now garbage. You can find something like winMD 5 generator:
http://www.winmd5.com/download/winmd5free.zip
Unzip the above download and run WinMD5.exe to generate an MD5 hash of the TWRP file you downloaded. Compare it to what it says the files MD5 hash is on the download web page. If I remember correctly I had to manually type in the MD5 hash from the page because it was an image I couldnt just copy. Or you can just visually verify with the one generated by winmd5.
Once the MD5 is verified rename the TWRP you downloaded to TWRP.blob just to shorten the name for scripts later and copy it to where you have fastboot unzipped.
ADB command:
I got ADB from several sources but this "root method" http://forum.xda-developers.com/showthread.php?t=1886460 from bin4ry is what I have been using: (And no, it doesnt work for the prime because the exploit he uses to run the device in emulator mode doesnt work for us)
Download bin4ry's root tool to get the ADB file
SuperSU:
Finally download SuperSU zip file from:
http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip
How To Use The Downloads:
Unlock Device:
First we need to unlock the device. Copy the unlocker APK to the root of your SD card for your tablet via the USB cable or putting the SDCARD in to your computer directly or with the ADB PUSH command if you know how to do that. Run the built in file explorer on our tablet and browse to the SD card (/Removable/MicroSD). Tap the Unlock APK to install. Once installed run the Icon for the unlocker and follow directions. There are several warnings etc.. You will need wifi connected and it will unlock your device and VOID YOUR WARRANTY!.
The unlock will take a few minutes and reboot one or more times. When it is successfull you will see a notice on device boot up that says the device is unlocked.
Flash TWRP:
Once unlocked, power it off. Once off power it on by holding BOTH volume down and power buttons. When you see the menu appear the first option is RCK. press Volume Down to change the cursor to be over the USB logo (two presses of the button) and press volume up. This puts your device in fastboot mode
Back on your computer you should hopefully see a successfull driver install for fastboot. I got all my drivers from downloading and installing the Android SDK so you may or may not need to do that. Android SDK
If all is prepared and you are in fastboot with drivers loaded:
On your computer hold shift and right click on the folder where fastboot and the twrp.blob file are and you will see a context menu. Click on "Open Command Window Here" (Vista + only or if you installed powertools on 2000/XP)
If you don't get the command window here option then you will have to open a command prompt. Open the run dialog and type CMD and hit enter. This will get a dos command windows. Use the change directory (CD) command to change the current folder in the DOS window to where your fastboot file and TWRP.blob are.
In the command window copy and paste the following line:
fastboot -i 0x0b05 flash recovery twrp.blob
and hit enter
Let it runs its course. When done I had a black screen with ASUS in the middle and a blue-ish bar across the bottom that was filled. I had to hold power until it rebooted. ( I waited about 5 minutes with that blue bar filled before looking up onilne to power off. I would recommend waiting a couple of minutes to be sure/safe)
Install SuperSU:
Once I confirmed my Stock OS loaded I copied the Super SU zip file we downloaded above over to the device via the USB cable to the root of my SD card, or by inserting SDCARD in to my computer and copy it over to ROOT of card or with ADB PUSH. Once the copy completes shutdown the device again.
Once off, power it on and press and hold both the power buttons and volume down again. When the menu appears you should already have RCK (recovery) highlighted so press volume up to load TWRP recovery.
OPTIONAL - BACKUP IF YOU WANT TO:
In TWRP there is a backup option. I chose to backup to my SD CARD and made sure to backup everything and generate an MD5. It takes a While but you can flash this back ANYTIME to put your device back to the STOCK JB OS without root. You can use the backup anytime you like to preserve your devices COMPLETE STATE. Just use the restore option in TWRP to put it back.
To flash root, once TWRP loads, the top left option is "Install" tap that.
You will see a few choices, select the radio button to install from SD card (external source it may say). Tap the super su zip file: Superuser-3.1.3-arm-signed.zip to choose it.
Slide the slider at the bottom to the right.
This will flash superSU to your device. When successfully done, reboot (flash should only take a few seconds).
When you boot up SuperSU is installed.
To test root with ADB:
Your tablet must be plugged in to the USB port of the computer of course.
If you installed the SDK tools ADB is there or use the one from bin4ry's root tool as follows:
Unzip the downloaded root tool from bin4ry mentioned above. Use the shift and right click method in explorer on the "STUFF" folder for the unzipped files or use the command windows to change directory of the unzipped folder and further in to the "STUFF" folder.
In the command windows type:
adb shell
<hit enter>
after a few seconds you should see a $ prompt and your are in to the console of your tablet.
Type:
su root
<hit enter>
Superuser will prompt you to grant root permissions and I set the setting so it doesnt prompt me every time.
Your prompt will change to # and thats it, you are root.
I don't seem to have the command sudo on my tab so every time I want root in a terminal I type that su root to get the # prompt.
Any apps that need root can now ask for it, you will get that same "Grant" prompt and do so if that is what you want.
ADB will now yield Root when you type: SU root and hit enter (grant root privs in the popup)etc...
Final thoughts:
There are other ways to copy content to the device such as using ADB PUSH etc... and I am sure this could be mostly if not all scripted but now that my tablet is rooted I am not going to write one and flash SuperSU over and over and possibly screw up my device. Follow the directions above and you will be successfull. If someone wants to write a script based on the above knock yourself out.
I HIGHLY recommend checking ALL MD5 hashes of downloads to confirm you got what you were supposed to. This will help prevent bricks.
Nice to see another guide on unlocking and flashing TWRP
McJesus15 said:
Nice to see another guide on unlocking and flashing TWRP
Click to expand...
Click to collapse
I was thinking a "how to root without unlock" one should be next....
hx4700 Killer said:
I was thinking a "how to root without unlock" one should be next....
Click to expand...
Click to collapse
Haha we have to wait for the amazingly smart people here to find an exploit for Jelly Bean. Although unlocking and flashing a custom rom is the way to go
Sent from my Zio using xda app-developers app
McJesus15 said:
Haha we have to wait for the amazingly smart people here to find an exploit for Jelly Bean. Although unlocking and flashing a custom rom is the way to go
Sent from my Zio using xda app-developers app
Click to expand...
Click to collapse
Yeah, the How to was going to be:
Step1) You can't.
So you finally did it... Did your warranty run out or did the frustration finally get to you?
I'm still holding off for now. In a way its a good thing an exploit hasn't been found, it means google have made the system fairly secure.
Next weekend I'm going to give finding an exploit one last red hot go. Failing that (and I'm sure i will) I'll be joining you.
abazz said:
So you finally did it... Did your warranty run out or did the frustration finally get to you?
I'm still holding off for now. In a way its a good thing an exploit hasn't been found, it means google have made the system fairly secure.
Next weekend I'm going to give finding an exploit one last red hot go. Failing that (and I'm sure i will) I'll be joining you.
Click to expand...
Click to collapse
I wanted to flash the Energy rom because of the near double quadrant scores people were posting. Little did I (or the chef) know that the Kernel was set to 1.8GHZ and constantly running 1.6. CPU throttling did little to inhibit that and even if you set it back to 1.4 it still ran 1.6 when max CPU was needed The back cover temp went from 90 deg while playing an interactive game for 20 minutes to 108.5 deg when playing the same game for 20 minutes. I had to think that was compromising stability and longevity as well as battery life so I flashed back my stock backup I made via TWRP and rooted as above.
I wouldnt mind going back when the kernel is more controllable. I'm actually playing with backtrack 5 now that I am rooted and EDS with mounts to truecrypt volumes so glad I am rooted, would have rather not voided the warranty
I think the policy should be that if you unlock things like the screen and wireless etc.. should still be covered but since they can't control overclocking etc... those kinds of issues are not.
Between 3 kids events, Holiday stuff I barely have the time to do the things I want to do let alone invest time in hacking this device =/
Thanks for the guide. Picked up a second hand Prime + Dock online with a locked boot loader. Following your guide I had it unlocked, rooted, and with CM10 in about half an hour or less.
Thanks!
Sent from my One X using xda premium
jetpackjeff said:
Thanks for the guide. Picked up a second hand Prime + Dock online with a locked boot loader. Following your guide I had it unlocked, rooted, and with CM10 in about half an hour or less.
Thanks!
Sent from my One X using xda premium
Click to expand...
Click to collapse
Glad it was helpful.
I guess I need to go look in to CM10, I see plenty of people using it and talking about it.
hx4700 Killer said:
Glad it was helpful.
I guess I need to go look in to CM10, I see plenty of people using it and talking about it.
Click to expand...
Click to collapse
As far as I know the kernel issue is fixed. Androwook never had the issue. It'll still get hot but not enough to cause concern
Sent from my Zio using xda app-developers app
worked for me :thumbup:
Sent from my Transformer Prime TF201 using xda app-developers app
And for me, didn't get much easier - or idiot proof
Thanks worked perfectly, I'm on CM10 now
Btw, you should change this line (because it's kinda wrong):
Let it runs its course. When done I had a black screen with ASUS in the middle and a blue-ish bar across the bottom that was filled. I had to hold power until it rebooted. ( I waited about 5 minutes with that blue bar filled before looking up onilne to power off. I would recommend waiting a couple of minutes to be sure/safe)
For this part the blue bar across the bottom did show up but not the ASUS logo, for me the tablet stayed on the same page with the USB logo and the other stuff and the blue bar across the bottom (not the Asus logo).
wrong thread
I have always been locked, and RMAed previously. I was able to successfully do this last night, thanks for the links.
Yay! After reading the forums and triple checking every thing I finaly got ROOT!
Thanks! Now I'm off to install the Energy Rom and hopefully enjoy GTA on a 42" TV with a USB controller
Fail
Doesn't work for me. I'm trying to switch to TWRP from an ever flakier CWM that won't do a backup. I'm already unlocked and rooted but still with stock ROM (which won't update any more because I'm rooted.)
The fastboot flash finishes ok but when I try to boot into recovery I get the message that it is loading the recovery kernel and then it just boots into Android. I have no recovery at all now which is kind of scary.
(God I hate this device for noodling with. Whenever you miss a beat you're looking at a 5 minute uninteruptable boot/shutdown cycle to try again. Everything outside of the Andorid zone itself is so baroque, archaic and intricate that feels like Windows 1.0. More than once mine has come within a nat's ass of being introduced to the wall at high velocity.)
---------- Post added at 11:59 PM ---------- Previous post was at 11:28 PM ----------
DonGateley said:
Doesn't work for me.
Click to expand...
Click to collapse
Oh, how utterly silly of me. Because I rooted long ago I didn't get the JB upgrade OTA so I'm still with ICS. The blob I needed was
http://techerrata.com/file/twrp2/tf201/openrecovery-twrp-2.3.3.0-tf201-ICS.blob
(At least I determined that flashing the JB blob onto ICS is not catastrophic.)
Maybe I'm not the only one in this state. It might be a good idea in the text to tell others of the ICS option.
The reason I'm here is that I want to install CM10 so I wanted to back up first. When I do that upgrade I assume this ICS TWRP will cease working and I will then need to fastboot flash the JB blob, right? Or might I have a "Can't get there from here" kind of problem?
Thanks for the links and write up.
2 questions.
Do I need an SD card or is the internal storage ok to use.
And, what part of this process roots the device?
Thanks!
**EDIT**
Never mind, I am a bonehead. I had my prime replaced due to a camera defect, so they shipped me a new one running JB.
So I have been away from teh forum a couple of months...didn't realize a way to get around locked, un-rooted, JB had been found.
Thanks again!
Sent from my Transformer Prime TF201 using xda app-developers app
Thanks for writing this up, I can't thank you enough. About a month ago I hard bricked my prime and had to send it in to Asus to have it repaired (thankfully I didn'y get charged). I tried installing twrp but didn't check the md5; this was well written. Wish I could give you a hug.
I know maybe some people will think I'm dumb now or something... But I want to ask before I begin and maybe brick it
So this really WORKS with the LATEST OTA update from Asus? I searched everywhere for days/weeks/months already and found this today so I'm a little bit sceptic, hope you understand me.
as the title asks, should I run the update I just got from AT&T? I read several differing opinions for different phones. some say don't, as it may relock the bootloader, others say it won't even let you complete the process if any /systems files are altered, some of mine are. Any input would be greatly appreciated.
ps it would suck if I lost root, as I can't establish a usb connection with my pc and wouldn't be able to reroot.
NoobDude said:
as the title asks, should I run the update I just got from AT&T? I read several differing opinions for different phones. some say don't, as it may relock the bootloader, others say it won't even let you complete the process if any /systems files are altered, some of mine are. Any input would be greatly appreciated.
ps it would suck if I lost root, as I can't establish a usb connection with my pc and wouldn't be able to reroot.
Click to expand...
Click to collapse
you will lose root. Just did it. I had to replace TWRP with stock recovery. However, i noticed speed improvements here and there. i have not really tested new radio yet... not enough time yet
thanks for the super speedy response, it's really appreciated! :good:
NoobDude said:
thanks for the super speedy response, it's really appreciated! :good:
Click to expand...
Click to collapse
i noticed my bootloader was still unlocked and i installed the cwm recovery,then booted into recovery. And when i went to leave recovery, it told me that my root may be lost and ask if i wanted to fix it. said yes and root appears to be back. then i installed latest TWRP(2.5) and all is ok! :good:
Edit:
after installing TWRP i did a backup (just in case). and after the back up it asked to fix permissions. said ok(as i thought maybe i lost root again) and it booted in android and root appears to be rooted. I tested with android terminal
a recovery can't be flashed in recovery with s-on** though, can it? To flash a new recovery you need to use adb no?
pardon my brain fart above..... so when you updated it erased your recovery? and the only way to install a recovery is via a usb connection? in other words, if I install the update while in my predicament, I'd loose recovery and root...
NoobDude said:
a recovery can't be flashed in recovery with s-on** though, can it? To flash a new recovery you need to use adb no?
pardon my brain fart above..... so when you updated it erased your recovery? and the only way to install a recovery is via a usb connection? in other words, if I install the update while in my predicament, I'd loose recovery and root...
Click to expand...
Click to collapse
you would boot into bootloader(fastboot) and flash the recovery:
$ sudo fastboot flash recovery <nameofrecovery>.img
edit: changed (hboot) to (fastboot) sorry if there was confusion, but it was late.
Orrrrr go and flash the AT&T update in it's Rom format. It's in Android Development.
can I flash the kernel in recovery though? I though with s on I had to do it from a computer using adb?
edit: ya there's no way I can flash the boot.img, that I know of at least, until I can get my usb connection working.
Are your drivers installed
yes and no. I installed HTC sync, the driver installer from Lucky 13s how to root post, and the ones from Hasoons tool. I tried installing then all separately, together, every which way. Currently all those programs are installed, yet in my device manager, nothing from HTC appears. It's like thy're installed but not. I backed up my phone right after I rooted it, nothing modified, its like it just came out the box only with root. I restored that "rom" and STILL it will not connect! I plug my phone in and NOTHING happens, it only charges. Tried different USB chords and plugged them into every USB port on the computer front and back, nothing , nadda, zip. I'm currently running vista, and am on the verge of dropping 100$ on Windows 7 and praying it fixes the problem. I've googled the CRAP out of this issue, and all i found are people who had FAILED installations. I've yet to get a failed message though. I swear i'm the only person with this issue. And its making me MAD... :crying:
NoobDude said:
yes and no. I installed HTC sync, the driver installer from Lucky 13s how to root post, and the ones from Hasoons tool. I tried installing then all separately, together, every which way. Currently all those programs are installed, yet in my device manager, nothing from HTC appears. It's like thy're installed but not. I backed up my phone right after I rooted it, nothing modified, its like it just came out the box only with root. I restored that "rom" and STILL it will not connect! I plug my phone in and NOTHING happens, it only charges. Tried different USB chords and plugged them into every USB port on the computer front and back, nothing , nadda, zip. I'm currently running vista, and am on the verge of dropping 100$ on Windows 7 and praying it fixes the problem. I've googled the CRAP out of this issue, and all i found are people who had FAILED installations. I've yet to get a failed message though. I swear i'm the only person with this issue. And its making me MAD... :crying:
Click to expand...
Click to collapse
do yourself a favor and get yourself a Live CD of Ubuntu. Ubuntu is free and the perferred OS for android. i swear by it. You can dual boot your vista and Ubuntu if you partition your hard drive. then after install and you boot into Ubuntu, hit ctrl-alt-t to open a terminal and type
Code:
sudo apt-get install android-tools-adb
when you type sudo you will have to enter your password, and it will not show it as you type
then
Code:
sudo apt-get install android-tools-fastboot
then restart the computer into Ubuntu
download the boot.img
press ctrl-alt-t
cd to the file directory (usually cd Downloads)
and type:
sudo fastboot flash boot <name of boot>.img
TheJokah said:
do yourself a favor and get yourself a Live CD of Ubuntu. Ubuntu is free and the perferred OS for android. i swear by it. You can dual boot your vista and Ubuntu if you partition your hard drive. then after install and you boot into Ubuntu, hit ctrl-alt-t to open a terminal and type
Code:
sudo apt-get install android-tools-adb
when you type sudo you will have to enter your password, and it will not show it as you type
then
Code:
sudo apt-get install android-tools-fastboot
then restart the computer into Ubuntu
download the boot.img
press ctrl-alt-t
cd to the file directory (usually cd Downloads)
and type:
sudo fastboot flash boot <name of boot>.img
Click to expand...
Click to collapse
Im very familiar with Ubuntu i have 12.04 dual booted on my acer chromebook and ran plenty of programs with terminal. Im going to take your advice right now and get cracking! Thanks a lot man!
Hi guys, over the past few weeks, I have noticed that many people are having problems rooting their Jetstreams. So because of this, I thought I would put together an all in one guide to help alleviate everyone's problems.
So what this will show you how to do:
Unlock the bootloader
Flash a custom recovery
Grant root access
Prepare the device for S-OFF
Included files:
HTC Drivers
ADB
Fastboot
TWRP 2.4.1.0
SuperSU 1.51
Note: This guide is for windows only
Ok, so lets begin:
Download attached zip
http://www.mediafire.com/download/ao1ykdpx5jn2uni/Root_HTC_Jetstream.zip
Extract the zip to an appropriate place on your computer
Install the HTC drivers
Do so by double clicking the HTCDriver_4.2.0.001.exe from the zip
Run the RUU if needed
I am assuming you are on a completely stock HTC Jetstream with no modifications what so ever. I am also assuming you are on the latest software 1.30.502.1 for AT&T users or 1.26.631.4 for Rodgers users. If you are not, please download and run the latest RUU from the following website:
http://forum.xda-developers.com/showthread.php?t=2094375
Please note that running the RUU will completely WIPE your device of all personal data, so backup accordingly
To run the RUU, make sure the Jetstream is turned on and is fully booted into Android
Make sure "USB Debugging" is enabled under development settings
Make sure "Fastboot" is disabled under power settings
Simply attach the Jetstream to your computer with the appropriate USB cord
Double click on the downloaded RUU .exe file to run the program
If for some reason you cannot boot into Android, you can do the following:
With the device turned off, hold the volume down button and simple press the power button for a second or two
The device will boot into the bootloader, from there use the volume buttons to navigate to fastboot and the power button to select
Once in fastboot, connect the device to the computer with the USB cord and then double click the downloaded RUU .exe
Now lets unlock the bootloader
Please note that unlocking the bootloader will also WIPE your device
Go to http://www.htcdev.com/
Create an account if you do not already have one
Click on "Unlock Bootloader" and then "Get Started"
In the drop down box, select "HTC Jetstream"
Agree to all the legal terms
Follow all the instructions to obtain your unlock token
To easily do this:
Make sure "USB Debugging" is enabled under development settings
Make sure "Fastboot" is disabled under power settings
Connect the device to the computer with the USB cable
Navigate to the extracted folder of the attached zip
Hold the shift key and right click in the folder, then select "Open Command Window Here"
Type the following in the command window
Code:
adb reboot bootloader
Once the device has booted into fastboot, type the following in the command window
Code:
fastboot oem get_identifier_token
Copy the appropriate text according to the website and submit it
You will then be emailed an "Unlock_code.bin" and a link to continue the unlock process
Download the "Unlock_code.bin" and place it in the extracted folder from earlier
Now type the following in the command window
Code:
fastboot flash unlocktoken Unlock_code.bin
On the device you will be prompted to unlock the device, use the volume keys to navigate to "Yes" and use power to select
The device will reboot back into Android
Now lets flash a custom recovery
Connect the device to the computer with the USB cable
In the extracted folder open a command window by holding the shift key, right clicking, and selecting "Open Command Window Here"
Type the following in the command window
Code:
adb reboot bootloader
Once the device has booted into fastboot, type the following into the command window
Code:
fastboot flash recovery htc_jetstream_twrp_recovery_2.4.1.0.img
Once the custom recovery has been successfully flashed, type the following into the command window
Code:
fastboot reboot
The device will then boot back into android
Now lets get root
Connect the device to the computer with the USB cable
Copy the "SuperSU-v1.51.zip' to the root of you SD card
Go to the extracted folder, hold the shift key, right click, and select "Open Command Window Here"
Now type the following into the command window
Code:
adb reboot recovery
While at the recovery main menu, select the wipe option and wipe cache and dalvik cache
Next go back to the main menu and select install
Navigate to the SuperSU zip we placed on the SD card and flash the zip
Once it flashes, go back to the main menu and reboot back into system
The device will boot back into Android and the device will now be rooted!
So what now?
After completing the step above, you device should have an unlocked bootloader, and custom recovery installed, and also have root access. After having all of this you may now go on to install any custom ROMs you may want, however, I would recommend obtaining S-OFF to give yourself full control over your device.
This following link should help to explain what S-OFF is exactly:
http://forum.xda-developers.com/showpost.php?p=42455824&postcount=1
This next link is to the JuopunutBear S-OFF method:
http://forum.xda-developers.com/showthread.php?t=1906353
People I would like to thank:
DoomLoRD - for his initial work with rooting the HTC Jetstream
jmz - for giving us a custom recovery and hosting all the RUUs for us
TeamWin - for TWRP
Chainfire - for his amazing work with Android and SuperSU
Fuses and the rest of Team Unlimited - for giving us an S-OFF method
Disclaimer:
Just to be clear, unlocking and rooting your HTC Jetstream voids your warranty, so anything you do to it is your decision and I am in no way responsible for anything that happens to your device
great work!
@DNarsingh
Windows 8 64 finally can ADB to Jetstream and Sensation XL.
Thanks for driver file HTCDriver_4.2.0.001.exe containing within the zip you attached. The driver within htc_sync_setup_3.3.10.exe couldn't seem to get through.
Did a factory reset on my jetstream, and lost root. When I used CWM for recovery, I tried re-rooting using the guide in this thread. After another factory reset, root was still there, so I handed the jetstream to its new owner. However, the new owner has told me that the pen icon doesn't show up when using the pen. He did another factory reset (which took longer than usual), but still nothing. Anyone know what went wrong?
Notontherugman said:
Did a factory reset on my jetstream, and lost root.
Click to expand...
Click to collapse
I've never heard of a factory reset breaking root. The components that enable root usually exist on the /system partition and it is untouched by a factory reset.
The other root method (that I am unfamiliar) with is an insecure kernel. I don't know how this works, but I am pretty sure that a factory reset should not break it.
finniest said:
I've never heard of a factory reset breaking root. The components that enable root usually exist on the /system partition and it is untouched by a factory reset.
The other root method (that I am unfamiliar) with is an insecure kernel. I don't know how this works, but I am pretty sure that a factory reset should not break it.
Click to expand...
Click to collapse
I'm not a dev, and have just been following how-tos on XDA up to now (from back in the days of HTC HD2); therefore, I can't give details since I am inexperienced.
After the factory reset, Titanium Backup was denied SU, I could not browse the root directories/folders and all the software that needed root to work would not.
My question still stands: the pen icon won't show up. Anyone know what went wrong or what he may be doing wrong? In desperate need for help.
Notontherugman said:
After the factory reset, Titanium Backup was denied SU, I could not browse the root directories/folders and all the software that needed root to work would not.
Click to expand...
Click to collapse
Did you try to install the superuser app that you were formerly using from the market? My guess is that you lost the /data/app/su.apk that manages superuser, but that the binary is still in your /system/xbin/su directory somewhere. You probably removed the seemingly redundant /system/app/su.apk while using Titanium Backup, but are now left without a copy of it.
Notontherugman said:
My question still stands: the pen icon won't show up. Anyone know what went wrong or what he may be doing wrong? In desperate need for help.
Click to expand...
Click to collapse
If you are using Hive ROM then the pen icon will not appear, but the pen will still work with most apps. If you are using a different ROM then I really have no idea why the pen icon is not working. Are you certain that the pen battery still has a charge?
finniest said:
If you are using Hive ROM then the pen icon will not appear, but the pen will still work with most apps. If you are using a different ROM then I really have no idea why the pen icon is not working. Are you certain that the pen battery still has a charge?
Click to expand...
Click to collapse
Not using any ROMs.
I had removed most of the bloatware when I was using it, but the pen icon was there and I could use it just fine (before the factory reset).
Now, after the factory reset and the root method above, he tried his Flyer's pen on the Jetstream as well, so the battery is not a problem.
Notontherugman said:
I had removed most of the bloatware when I was using it, but the pen icon was there and I could use it just fine (before the factory reset).
Click to expand...
Click to collapse
Try using logcat to diagnose the problem. I suspect something will show up during boot or when you press where the pen icon should be.
http://www.xda-developers.com/android/help-your-developers-pull-a-logcat-when-issues-arise
I got the Jetstream back today.
I had managed to make a backup before using Clockwork Mod.
After the above rooting method, CWM is gone, and I can't use the backup files to restore using TWRP.
The link for CWM is gone. This is becoming extremely frustrating.
Notontherugman said:
I got the Jetstream back today.
I had managed to make a backup before using Clockwork Mod.
After the above rooting method, CWM is gone, and I can't use the backup files to restore using TWRP.
The link for CWM is gone. This is becoming extremely frustrating.
Click to expand...
Click to collapse
I have a copy of the CWM recovery.img. When I get home tonight, I will upload it for you.
I would recommend redoing your backup in TWRP afterward. In my experience, this recovery is a bit more up to date..
DNarsingh said:
I have a copy of the CWM recovery.img. When I get home tonight, I will upload it for you.
I would recommend redoing your backup in TWRP afterward. In my experience, this recovery is a bit more up to date..
Click to expand...
Click to collapse
Definitely.
And thank you!
EDIT: found CWM on an old hard disk. Managed to get ADB working. Restoring should fix most of the problems.
Thanks very much for the post
Sent from my SGH- I317M (Note II) running CM 11 using XDA Mobile App
every thing is ok
my device is fully rooted with twrp recovery and unlocked bootloader
but I have a problem.
I have sim card signal Icon but my device can not confirm simcard
what can I do?
Thanks!
Since I have rooted my device I can no longer access downloads from the google play store. I constantly get RPC:S-7:AEC-0 or -7 errors. I have tried all the tricks on various
forums but have had no luck. Do you have any fixes related to the jetstream?
Thanks, Mike
GROTEU said:
Since I have rooted my device I can no longer access downloads from the google play store. I constantly get RPC:S-7:AEC-0 or -7 errors. I have tried all the tricks on various
forums but have had no luck. Do you have any fixes related to the jetstream?
Thanks, Mike
Click to expand...
Click to collapse
It doesn't sound related to rooting. I would suggest a backup (there are many means of accomplishing this) and then a factory restore. If that doesn't work then install a custom ROM.
rooting issues
i have been trying to root my jetstream so i can get some lift out of it but when i get to the fast boot the system just hangs there any suggestions please if you know a complete way to root a htc from rogers i would love the support thanks
EDIT: Rooting the device is now possible! Download the image here! (Thanks to Justin Case!!)
Alright, you've unlocked your bootloader and you're ready to tear it up with custom roms and other assorted mods. But wait, this is probably a good time to stop. No, I'm not messing with you. Justin Case and I only just acquired root on the G Watch on July 4th, and there's very little that can be done with it at this point. Additionally, there are no superuser managers (eg. Chainfire's SuperSU or Koush's Superuser) available to prevent an app from abusing root for malicious purposes. This situation will surely change over a matter of days, or even hours, but that's where we're at for the moment. I'm not suggesting that people avoid rooting, only that they wait until it can be done a little more safely.
If you're one of the people that wants to get started on building some root apps, or you just need to be on the bleeding edge, you're in the right place. So far, we only have the process worked out for the LG G Watch, but the Samsung Gear Live should be ready fairly soon.
Now, reboot into the bootloader:
adb reboot bootloader
And boot the G Watch using the modified boot image. Warning: Do not flash the boot image, just boot from it!
fastboot boot LGGW-rootboot.img
The watch will play the boot animation for about 2 seconds, then automatically reboot. This time it will boot normally. There will be no outwardly obvious signs it has been rooted, but you can check it by opening a shell over adb and running su.
adb shell
su
If your prompt turns from [email protected] to [email protected], then you've got root on your G Watch. Congratulations!
Click to expand...
Click to collapse
From http://www.androidpolice.com/2014/0...nlock-the-bootloader-and-root-the-lg-g-watch/
Smith7018 said:
So I've started looking into rooting the G Watch and it's not going to be simple. Here are some of my findings:
1. There's a firewall running that blocks any outside communications that aren't sent out by Google-sanctioned apps.
2. The build time is Jun 23, 2014. That means towel root won't work...
3. The device codename is Dory.
4. Many apps will sidled but a lot of them will crash. Once we get root, this could be as simple as moving over libs.
5. Installing the Android keyboard apk allows the user to have a keyboard when necessary! I know this never worked on Glass.
So yeah, we have our work cut out for us. Anyone else looking at this?
(I've attached the build.prop)
Click to expand...
Click to collapse
Hi Smith,
I've ordered a watch but hasn't come yet.
What about accessing a shell via adb? Is this possible?
I certainly assume it is, so I'd bet root would come this way.
Doing some more research...
In theory...
We can unlock the bootloader (fastboot oem unlock)
Flash a recovery (TWRP?)
Flash either a kernel to root the device
OR
Flash a zip which just places an appropriate su binary in place.
Right now we will have to wait for a super user application to be ported to Android Wear....I imagine ChainFire or another will have that before too long.
Stericson said:
Doing some more research...
In theory...
We can unlock the bootloader (fastboot oem unlock)
Flash a recovery (TWRP?)
Flash either a kernel to root the device
OR
Flash a zip which just places an appropriate su binary in place.
Right now we will have to wait for a super user application to be ported to Android Wear....I imagine ChainFire or another will have that before too long.
Click to expand...
Click to collapse
I can confirm that fastboot oem unlock successfully unlocks the boot loader! Also, I can confirm that side loading the Gear Live's stop watch runs on the G Watch. The clock faces install (and are visible in the selection menu) but crash when selected. Interestingly enough, logcat says the app is unable to bind to the Wear home screen... I wonder what could be stopping the legit Android app from running... OEM checks?
If you can in fact unlock the bootloader, rooting is just a matter of waiting for a custom recovery to be ported over to it.
(and being updated to both support such small displays and no buttons at all)
TheManii said:
If you can in fact unlock the bootloader, rooting is just a matter of waiting for a custom recovery to be ported over to it.
(and being updated to both support such small displays and no buttons at all)
Click to expand...
Click to collapse
How would we get into recovery... Seems like a recovery would be best done from a computer.
It hasn't been mentioned on how to do it while it was booting,
but currentl you can enter it by doing
Code:
adb reboot bootloader
The issue is that doing it that way requires an already working rom that also has debugging turned on.
Updated the first post with instructions on how to root the G Watch!
Smith7018 said:
Updated the first post with instructions on how to root the G Watch!
Click to expand...
Click to collapse
But why would you without SuperSU or SuperUser?
I'd wait until it's properly supported unless you're REALLY comfortable with your security.
Sent from Nexus 5 or 7.
After doing a decent amount of research I have not been able to find information concerning my situation.
About six months ago I rooted and installed the Kindle hdx Nexus rom with no problems. Then suddenly while playing Minecraft pe the device shuts off. I restart and it goes to the nexus boot with the four dots exchanging genetic material(lol) It got stuck at this point whenever I tried to restart. I hadn't changed and settings or software it just crashed
I am able to boot into safestrap recovery so I tried to reinstall stall the Thor rom since I still had the file on the Kindle. Theni got the boot loop from the colored dots stage and sometimes the boot would go to "initializing apps 1 of 50) or somthing like that and then it would loop.
I tried to restore to whatever previous back up and version I had and one of them must have been from the stock rom bc the loading "kindle logo" was the stock yellow and white... all I got was a loop so I reinstalled the Thor rom...
I probably should not have but at this point I tried to remove some apps via the safe strap file manager bc i know in my experience with phones certain apps can cause problems and my device was too full to preform backup via recovery
And in my last desperate attempt to not loose some of the things not backed up on the Kindle I connected to my computer to find out my computer can't recognize the device at this point...
I checked the plugins I checked the versions for compatability
I tried to use safestrap side load and came up with command not recognized for internal or external device (somthing like that)
Are there any other options for me? Does this mean it's a hard brick and what could have went wrong?
I think my mistake originally was I didn't create a separate rom slot before flashing(I don't think that bit of information was in the write up I followed)
Side note: for the record I did try to connect to my computer earlier than I stated with the device not being recognized while off or from ss recovery to try save some files
Zavxda said:
After doing a decent amount of research I have not been able to find information concerning my situation.
About six months ago I rooted and installed the Kindle hdx Nexus rom with no problems. Then suddenly while playing Minecraft pe the device shuts off. I restart and it goes to the nexus boot with the four dots exchanging genetic material(lol) It got stuck at this point whenever I tried to restart. I hadn't changed and settings or software it just crashed
I am able to boot into safestrap recovery so I tried to reinstall stall the Thor rom since I still had the file on the Kindle. Theni got the boot loop from the colored dots stage and sometimes the boot would go to "initializing apps 1 of 50) or somthing like that and then it would loop.
I tried to restore to whatever previous back up and version I had and one of them must have been from the stock rom bc the loading "kindle logo" was the stock yellow and white... all I got was a loop so I reinstalled the Thor rom...
I probably should not have but at this point I tried to remove some apps via the safe strap file manager bc i know in my experience with phones certain apps can cause problems and my device was too full to preform backup via recovery
And in my last desperate attempt to not loose some of the things not backed up on the Kindle I connected to my computer to find out my computer can't recognize the device at this point...
I checked the plugins I checked the versions for compatability
I tried to use safestrap side load and came up with command not recognized for internal or external device (somthing like that)
Are there any other options for me? Does this mean it's a hard brick and what could have went wrong?
I think my mistake originally was I didn't create a separate rom slot before flashing(I don't think that bit of information was in the write up I followed)
Side note: for the record I did try to connect to my computer earlier than I stated with the device not being recognized while off or from ss recovery to try save some files
Click to expand...
Click to collapse
No, creating a separate rom slot is not problem/solution (explicitly not recommended). What symptoms is your device exhibiting now? Which version of Safestrap?
Davey126 said:
No, creating a separate rom slot is not problem/solution (explicitly not recommended). What symptoms is your device exhibiting now? Which version of Safestrap?
Click to expand...
Click to collapse
Ok thanks good to know.:highfive: I thought I read somewhere some people do that.
Ss 4.01 (TWRP v2.7.1.0)
Basically the same as before, bootloop at the four loading dots not recognized by the computer
Zavxda said:
Ok thanks good to know.:highfive: I thought I read somewhere some people do that.
Ss 4.01 (TWRP v2.7.1.0)
Basically the same as before, bootloop at the four loading dots not recognized by the computer
Click to expand...
Click to collapse
Safestrap v4 has no native ability to communicate with the outside world. Not recognized via tether is expected with a non functioning rom. Suggest the following:
- perform a 'factory reset' from the Wipe menu (slider at bottom)
- reinstall Nexus rom using zip resident on the device
If symptoms persist it suggests corruption in the system partition which can not be wiped in Safestrap (option exists but is ignored behind then scenes as it would also destroy Safestrap recovery). Not much you can do about that short of replacing boards.
Note: There is an untested option that *may* work with a secondary slot. Try the above first and report back results.
Where would the nexus rom be located?
Davey126 said:
Safestrap v4 has no native ability to communicate with the outside world. Not recognized via tether is expected with a non functioning rom. Suggest the following:
- perform a 'factory reset' from the Wipe menu (slider at bottom)
- reinstall Nexus rom using zip resident on the device
If symptoms persist it suggests corruption in the system partition which can not be wiped in Safestrap (option exists but is ignored behind then scenes as it would also destroy Safestrap recovery). Not much you can do about that short of replacing boards.
Note: There is an untested option that *may* work with a secondary slot. Try the above first and report back results.
Click to expand...
Click to collapse
Well anyway doing factory reset and reinstalling the rom zip was not working... now when I go to restore or install option no rom file comes up
Zavxda said:
Well anyway doing factory reset and reinstalling the rom zip was not working... now when I go to restore or install option no rom file comes up
Click to expand...
Click to collapse
A zip file doesn't just disappear unless the file system is damaged. Look around with the Safestrap file manager. Without a rom zip on board your options are very limited.
Davey126 said:
A zip file doesn't just disappear unless the file system is damaged. Look around with the Safestrap file manager. Without a rom zip on board your options are very limited.
Click to expand...
Click to collapse
Yeah seems like it's missing... i think it went away after one of the factory resets I did...
I have this exact same issue - I can boot into Recovery, but I have no way of getting a ZIP onto the device to flash a ROM? Is there a way?
skoop99 said:
I have this exact same issue - I can boot into Recovery, but I have no way of getting a ZIP onto the device to flash a ROM? Is there a way?
Click to expand...
Click to collapse
Nope - no file transfer capability without a functioning ROM or custom recovery (requires an unlocked bootloader)
Zavxda said:
Yeah seems like it's missing... i think it went away after one of the factory resets I did...
Click to expand...
Click to collapse
Davey126 said:
Nope - no file transfer capability without a functioning ROM or custom recovery (requires an unlocked bootloader)
Click to expand...
Click to collapse
I actually managed to use ADB PUSH to transfer a ROM zip to the device - but after flashing it, the device still fails to boot. I'll try again with a different ROM...
skoop99 said:
I actually managed to use ADB PUSH to transfer a ROM zip to the device - but after flashing it, the device still fails to boot. I'll try again with a different ROM...
Click to expand...
Click to collapse
Update - I have now successfully pushed another ROM to the device, using:
ADB push <path to rom zip> /sdcard
Flashed said ROM, booted OK. Then re-installed the device in Windows as a "normal" Kindle portable device again, to enable drag & drop file transfers. Dropped Gapps zip on it, rebooted into Recovery, flashed Gapps. All good again!
So, Safestrap 4.xx DOES allow ADB connectivity to a device. As long as you can still boot into Recovery.
skoop99 said:
Update - I have now successfully pushed another ROM to the device, using:
ADB push <path to rom zip> /sdcard
Flashed said ROM, booted OK. Then re-installed the device in Windows as a "normal" Kindle portable device again, to enable drag & drop file transfers. Dropped Gapps zip on it, rebooted into Recovery, flashed Gapps. All good again!
So, Safestrap 4.xx DOES allow ADB connectivity to a device. As long as you can still boot into Recovery.
Click to expand...
Click to collapse
Whoa!! This is new and potentially great news for those with 'bricked' devices with a bootable Safestrap v4 recovery installed. I believe this was attempted in the past w/o success. Something changed or earlier tests were flawed.
Although it may not matter can you answer a few questions:
- Apollo or Thor?
- which rom was installed in the STOCK slot when the inadvertent wipe took place?
- what was the base version of FireOS (4.5.2 or 4.5.5.1) when Safestrap v4 recovery was first installed?
- ROM currently installed (the one that booted after adb push)?
- anything else unusual about the device or its history?
Again, this is a nice find a casts a shadow over previous statements, many made by me, that there was no resolution to this dilemma.
skoop99 said:
I actually managed to use ADB PUSH to transfer a ROM zip to the device - but after flashing it, the device still fails to boot. I'll try again with a different ROM...
Click to expand...
Click to collapse
Davey126 said:
Whoa!! This is new and potentially great news for those with 'bricked' devices with a bootable Safestrap v4 recovery installed. I believe this was attempted in the past w/o success. Something changed or earlier tests were flawed.
Although it may not matter can you answer a few questions:
- Apollo or Thor?
- which rom was installed in the STOCK slot when the inadvertent wipe took place?
- what was the base version of FireOS (4.5.2 or 4.5.5.1) when Safestrap v4 recovery was first installed?
- ROM currently installed (the one that booted after adb push)?
- anything else unusual about the device or its history?
Again, this is a nice find a casts a shadow over previous statements, many made by me, that there was no resolution to this dilemma.
Click to expand...
Click to collapse
- Thor
- Nexus: http://forum.xda-developers.com/kindle-fire-hdx/development/rom-hdx-nexus-v4-0-1-t3125808
- 4.5.2
- CM11: http://forum.xda-developers.com/kin...-cm-11-safestrap-20150628-unofficial-t3145547
- Nope.
Bootloader is also still locked.
I only figured this out when I noticed that device manager DID detect the device, but couldn't find a driver. So I installed the ADB driver, and hey presto: ADB DEVICES sees it.
C:\Users\KoopS\Dropbox\Downloads\android-sdk-windows\platform-tools>adb devices
List of devices attached
D070A0A0348300GD recovery
Hope it helps someone else. Again, though - you need to be able to boot into Recovery...
skoop99 said:
- Thor
- Nexus: http://forum.xda-developers.com/kindle-fire-hdx/development/rom-hdx-nexus-v4-0-1-t3125808
- 4.5.2
- CM11: http://forum.xda-developers.com/kin...-cm-11-safestrap-20150628-unofficial-t3145547
- Nope.
Bootloader is also still locked.
I only figured this out when I noticed that device manager DID detect the device, but couldn't find a driver. So I installed the ADB driver, and hey presto: ADB DEVICES sees it.
C:\Users\KoopS\Dropbox\Downloads\android-sdk-windows\platform-tools>adb devices
List of devices attached
D070A0A0348300GD recovery
Hope it helps someone else. Again, though - you need to be able to boot into Recovery...
Click to expand...
Click to collapse
Freaking amazing! Such an obvious and simple solution that has gone undetected for years. There are some tentative caveats (device type, older ROMs) but not sure any of it matters for basic adb access. Time will tell as others stumble into this situation.
For clarity, which recovery are you referencing? Stock or Safestrap? If the former adb access may offer a small measure of hope for those with other types of soft 'bricks'.
I unlocked the bootloader and flashed TWRP on all my HDX devices long ago and haven't loaded Safestrap for testing in months. Just continued to reference previous (mis)understandings around recovery capabilities which was generally bad news. I will likely create a new thread referencing you findings for those who may have shelved their romless but still functioning devices.
Thanks again for sharing. @skoop99 is the man of the day!
See pic. This is my KFHDX...
Wow this is fantastic news! has anyone else here had a chance to try this? I can't remember if the PC responded at all when I plugged in the Kindle
What was the first ROM you tried that didn't work?
Is there a reason you didn't flash the Nexus ROM again?
Zavxda said:
Wow this is fantastic news! has anyone else here had a chance to try this? I can't remember if the PC responded at all when I plugged in the Kindle
Click to expand...
Click to collapse
I'll try this soon. I have a Kindle HDX 7 (that I retrieved from the bin after reading this) that will boot to safe strap, but has no rom, and no zip file of a rom to install.
I'm guessing I need to download and use ADB devices?
Does this work with windows 10?
HDX is too nice to throw away, I hope this works....
Nagoyablue73 said:
I'll try this soon. I have a Kindle HDX 7 (that I retrieved from the bin after reading this) that will boot to safe strap, but has no rom, and no zip file of a rom to install.
I'm guessing I need to download and use ADB devices?
Does this work with windows 10?
HDX is too nice to throw away, I hope this works....
Click to expand...
Click to collapse
- works with Win 10
- you may need to install drivers (although Win 10 often gets it right)
- also consider Minimal ADB and Fastboot (here)
So, I pushed the zip of CM11 unofficial to my HDX. And installed it. I'm pushing the GAPPS now....
---------- Post added at 07:06 PM ---------- Previous post was at 07:05 PM ----------
And cyanogenmod is booting up! It works! My Kindle fire HDX 7 is saved! Amazing.