It's finally here! TWRP recovery for the Fire TV 1. Most likely, I will not be updating this thread with new releases, as the prerooted ROMs will always contain the latest version. This thread is just here so people on Fire OS 3 can install TWRP and people on rooted but locked bootloader Fire TV 1's can get recovery initially installed.
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.
Installing this requires root. If you are not rooted, figure that out first.
Installation for Unlocked Bootloader
Make sure you are on a FULLY unlocked bootloader. From within FireOS and after running su run this:
Code:
cat /proc/cmdline
And MAKE SURE unlocked_kernel=true is present! If it is not, you are NOT fully unlocked and you must Fully Unlock first!
Make sure you are on at least 51.1.4.0 ROM and the latest CWM installed.
Copy the bueller-twrp_3.0.0-6.img file to /sdcard
From within adb shell, use su to become root, and run this command (are you sure you did step 1?)
Code:
dd if=/data/media/0/bueller-twrp_3.0.0-6.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
From outside adb shell, reboot to recovery
Code:
adb reboot recovery
TWRP should load, you can install a FireOS5 prerooted ROM now.
Installation for Locked Bootloader
This requires that you are on at least version 5.0.5 and rooted.
Copy the bueller_recovery_vX.zip file to /sdcard
From within adb shell, use su to become root, and run this command (replace vX with the actual version you downloaded)
Code:
sh /data/media/0/bueller_recovery_vX.zip
Reboot
Notes
This includes bootmenu. For everyone that loved the old bootmenu with Comic Sans, I'm sorry to disappoint you, but the Comic Sans is gone. When the FireTV boots, it will present you with the bootmenu where you can leave it alone and it will boot normally or you can select recovery and it will boot in to recovery. You do need a USB keyboard to interact with the bootmenu. To force it to boot in to Recovery, you can create a file /cache/bootmenu_recovery.
DHCP for Ethernet is enabled, and if there is enough demand I may add in wifi at some point. The IP address should show up in the top left corner.
USB storage and USB keyboard/mice should all work. Hotplugging works, so you should be able to plug and unplug devices as needed.
You can use a USB keyboard, mouse, or the mouse emulator to interact with it. To use a keyboard, you can use the arrow keys to move the cursor and the enter key to select buttons. Sliders don't require sliding, so you can just hit enter/click on them. To use the mouse emulator, use adb shell and then run the program mouse and follow the instructions.
ROMs
Recovery must be included in all ROMs. If you want to develop a ROM, please contact me about including recovery in it.
Installing zips
You can push zips to /sdcard, put it on a USB storage, or use adb sideload. Do note you need adb version 1.0.32 to use adb sideload.
Stuck in a loop?
If you cannot boot normally and keep going back to the bootmenu, wipe Cache from Wipe -> Advanced Wipe.
Source Code
You can find the source code here:
https://github.com/androidrbox/firetv-2ndinit
https://github.com/androidrbox/android_bootable_recovery
WARNINGS
It is extremely important you never reboot after a failure. This will most likely lead to a brick. If recovery is hung, you can use adb shell to run
Code:
killall recovery
to restart it
It is also extremely important to never reboot after wiping /system.
Finally, thanks to everyone who has donated to me.
Changelog and Downloads:
July 7, 2016 - v2 (md5sum: 8f65187cb0cbc190a7d64f512ae3ede2)
This is the updated version with TWRP 3.0.0-7.
July 4, 2016 - TWRP Image 3.0.0-7 (md5sum: cda1a1c1cdd3e25a1caa86f5a5de1eee)
May 20, 2016 - v1 (md5sum: 9208d81fd07cff9952de5be33c62f730)
This is for use by people who have FireOS5 and are rooted.
This includes 2ndinit version a7a48c and TWRP version 3.0.0-6.
May 20, 2016 - TWRP Image (md5sum: 5dc83370046e5b50755ddb55fe8424ad)
This is for use by people who have FireOS3 and CWM and is TWRP version 3.0.0-6.
thanks so much rbox! just tested it and i can confirm that my firetv 1 with fireos3 and fully unlocked bootloader just installed twrp successfully - woot!
i still have the old boot menu though with comic sans..?
mrchrister said:
thanks so much rbox! just tested it and i can confirm that my firetv 1 with fireos3 and fully unlocked bootloader just installed twrp successfully - woot!
i still have the old boot menu though with comic sans..?
Click to expand...
Click to collapse
For unlocked bootloaders, this step JUST installs recovery. You need to install the prerooted rom to get the new bootmenu.
got you, downloading now
Sent from my iPhone using Tapatalk
I successfully dd'ed the recovery image onto my ftv with unlocked bootloader but attempting to boot it causes the TWRP logo to show for a few seconds, then the screen goes black and the cycle repeats. Any idea how to fix this?
ssgelm said:
I successfully dd'ed the recovery image onto my ftv with unlocked bootloader but attempting to boot it causes the TWRP logo to show for a few seconds, then the screen goes black and the cycle repeats. Any idea how to fix this?
Click to expand...
Click to collapse
If you unplug the power and replug it, it should boot normally, then you can see if the recovery log got saved, /cache/recovery/last_log and pastebin it.
The log at /cache/recovery/last_log is from CWM from the last time I flashed a new rom.
ssgelm said:
The log at /cache/recovery/last_log is from CWM from the last time I flashed a new rom.
Click to expand...
Click to collapse
Can't really explain why it would be doing that. Can you connect via adb?
I am not on ethernet right now. When I get a chance I'll do that and see if I can connect. Thanks so much for your work on this!
ssgelm said:
I successfully dd'ed the recovery image onto my ftv with unlocked bootloader but attempting to boot it causes the TWRP logo to show for a few seconds, then the screen goes black and the cycle repeats. Any idea how to fix this?
Click to expand...
Click to collapse
I'm also getting this, what can I do?
here's last_log
gehx said:
I'm also getting this, what can I do?
Click to expand...
Click to collapse
Can you connect via adb?
rbox said:
Can you connect via adb?
Click to expand...
Click to collapse
yep, that's how I pulled last_log
gehx said:
yep, that's how I pulled last_log
Click to expand...
Click to collapse
I meant while recovery is running.
rbox said:
I meant while recovery is running.
Click to expand...
Click to collapse
recovery never fully loads, i just get the twrp splash screen over and over and over again...it's in a loop
gehx said:
recovery never fully loads, i just get the twrp splash screen over and over and over again...it's in a loop
Click to expand...
Click to collapse
Yes. But have you tried using adb...
rbox said:
Yes. But have you tried using adb...
Click to expand...
Click to collapse
I'm not sure what IP to use?
gehx said:
I'm not sure what IP to use?
Click to expand...
Click to collapse
The same one the firetv would be using when it's booted... via ethernet of course.
rbox said:
The same one the firetv would be using when it's booted... via ethernet of course.
Click to expand...
Click to collapse
the connection times out:
adb connect 192.168.1.6
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
unable to connect to 192.168.1.6:5555: Operation timed out
Click to expand...
Click to collapse
gehx said:
the connection times out:
Click to expand...
Click to collapse
Can you pull the log again? It should say the ip in it actually.
rbox said:
Can you pull the log again? It should say the ip in it actually.
Click to expand...
Click to collapse
new last_log
it shows 192.168.1.8; I'm unable to adb connect to that IP too
Related
Warning:
I will not be responsible for damage to your device(s) by using this exploit. Antivirus software and Play services will likely detect this as potentially malicious. It is an exploit, deal with it or don't use it. Do not mirror these applications without my permission!
PwnMyMoto is a replacement for my previously released MotoRoot. PwnMyMoto exploits three vulnerabilities, to gain root access, then to gain write to system. This is a traditional root, and doesn't use any 'hackery' to maintain su access unlike MotoRoot.
First we use bug 9695860 (aka second masterkey) to gain system user, then it uses a symlink attack to gain root access. After gaining root we exploit a flaw in the bootloader, allowing us to bypass the write protection applied to system. In the process we remove stock recovery, so OTAs will not be a worry.
Install PwnMyMoto by running:
adb install -r PwnMyMoto-<version and model go here>.apk
Click to expand...
Click to collapse
Then run PwnMyMoto, depending on the current root status of your phone it will reboot 2 or 3 times, after the last reboot it will uninstall it self and su will be installed on the actual system partition. Please install SuperSu from the market after this step is done.
We have two (ok more but were not going into that) boot modes. First is normal, which boots regular Android, and in this case boots with system write protected. Second is recovery mode, normally it boots recovery without write protection. Our exploit will hijack recovery bootmode and boot Android without write protection.
After running this exploit, if you boot normally /system will be write protected. If you boot to "recovery", Android will boot without write protection. If you wish to edit system, you must boot into "recovery" to do so, any changes made will stick and will work in either bootmode. My suggestion is to make your changes in "recovery" and run the device day to day in normal mode, until we are certain "recovery" mode will be 100% stable for day to day use.
The exploit will uninstall itself after successful exploitation.
To see if write protection is applied, you can run:
adb shell getprop ro.boot.write_protect
Click to expand...
Click to collapse
If it returns '1' then write protection is applied to /system, if it returns '0' then no write protection has been applied.
In the future we will have a replacement recovery, but at this time it is still in development. Enjoy.
Change Log:
1.4.3 allows detection of failed su installation (0 size su) and reinstallation)
1.4.1 adds reliability, and fixes issues for users when improper permissions are applied to su (Preventing updates).
1.2 - Bug fix for devices which had recieved OTAs.
If you used 1.1 and have a problem with recovery coming back, run the following command:
adb shell su -c "dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/dev/block/platform/msm_sdcc.1/by-name/recovery"
Click to expand...
Click to collapse
1.1 - initial release
Thanks!
Figure I should add that this does not allow usage of custom kernels at this time because everything is still signature checked.
Is there an unroot process?
alee said:
Is there an unroot process?
Click to expand...
Click to collapse
I'd assume you could boot into the recovery mode and just delete superuser, su, and busybox, but someone more knowledgeable should confirm.
Sent from my Nexus 7
Just an FYI, since I panicked a little, when the little Andy is shown lying on his back and it says "No command", just wait it out
Dr. Carpenter said:
Just an FYI, since I panicked a little, when the little Andy is shown lying on his back and it says "No command", just wait it out
Click to expand...
Click to collapse
It probably didn't work for you then. I was having the same problem earlier and again now.
I still have root. It did the same thing when booting to recovery. Guess I'll reinstall and give it another go.
Sent from my XT1080 using Tapatalk 4
Dr. Carpenter said:
I still have root. It did the same thing when booting to recovery. Guess I'll reinstall and give it another go.
Sent from my XT1080 using Tapatalk 4
Click to expand...
Click to collapse
It shouldn't boot to recovery since it is being replaced.
Sorry, meant when booting to "recovery". It went to the no command screen for a minute then rebooted to Android.
Sent from my XT1080 using Tapatalk 4
If you are running into an issue where it is booting into normal recovery, come find me on IRC. I think 1.1 fixed the bug but if it didn't i need to release 1.2/
OK, not sure what's going on now... The first time I ran it, the button said something like Click to root, now this time it said Boot into WP bypass. Hit it and same thing, back to the no command screen for a while and then a reboot. I was previously rooted, but based on the OP, that shouldn't make a difference. Back up now, and the app is still installed (it uninstalled the first time), still says the same thing.
Worked for me... Rooted w.o wp when booting to recovery
jcase said:
If you are running into an issue where it is booting into normal recovery, come find me on IRC. I think 1.1 fixed the bug but if it didn't i need to release 1.2/
Click to expand...
Click to collapse
first of all, thanks so much, and i apologize for the noob questions below, but i'd like some clarification if possible (perhaps a video would be helpful like on your previous releases).
1) does it matter which version of your moto root app and SU we are currently using?
2) what do you mean in the OP by normal mode and recovery mode? I mean i've used custom recovery and normal (adb) mode, but when you say "recovery mode" will have write access, does that mean you will have write access only while you are in recovery? I think it means that you get into regular android operating system (that is adb), but through some extra boot/recovery step. This is confusing.
3) which custom recovery is the stock recovery being replaced with?
4) how do we tell it to boot in "recovery mode" or "normal mode"?
5) which version of supersu should we use? is the regular one OK?
6) which IRC are you referring to in the above quote?
Version 1.2 should work on devices that had taken the OTA, 1.1 didn't reflash the recovery partition with boot for them.
a manual fix for those that used 1.1 is a single command
adb shell su -c "dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/dev/block/platform/msm_sdcc.1/by-name/recovery"
Click to expand...
Click to collapse
So am I to understand that in order to install this apk you have to use adb. Because it doesn't install like a normal apk it says that a signed version is already installed. Which is the other apk 1.1 if so this sucks I nuked my computer last night no adb. Will the 1.2 version allow me to install the apk normally over the 1.1
Never mind I see that its 1.2 now and it did install no problem and deleted itself and I have root. However like mistermojo I am confused as to how to get r/w I know how to get into recovery but once there do you just reboot and then you have r/w a little clarification would be appreciated. Thank you for the exploit and especially it being an apk since my computer took a **** last night.
bigv5150 said:
So am I to understand that in order to install this apk you have to use adb. Because it doesn't install like a normal apk it says that a signed version is already installed. Which is the other apk 1.1 if so this sucks I nuked my computer last night no adb. Will the 1.2 version allow me to install the apk normally over the 1.1
Never mind I see that its 1.2 now and it did install no problem and deleted itself and I have root. However like mistermojo I am confused as to how to get r/w I know how to get into recovery but once there do you just reboot and then you have r/w a little clarification would be appreciated. Thank you for the exploit and especially it being an apk since my computer took a **** last night.
Ok I can't get into stock recovery when I get into fastboot and choose recovery it goes to a black screen and like it is off I can get back into fast boot or just boot the phone normal but no recovery.
Click to expand...
Click to collapse
recovery is over written with this method. simply use an app that reboots to recovery and the phone will boot normally only write protection will be disabled.
Bigv
power off your phone
Press vol - and power key at the same time for 3 secs and release
You should be in the fastboot. Press vol - until you highlight recovery.
Press vol + to select and boot to android with write protect turned off
asuhoops8628 said:
Bigv
power off your phone
Press vol - and power key at the same time for 3 secs and release
You should be in the fastboot. Press vol - until you highlight recovery.
Press vol + to select and boot to android with write protect turned off
Click to expand...
Click to collapse
Got it my dumbas was pushing power not + and I was just turning the screen off not rebooting into recovery or normal power up thanks for the help. It sucks not being to run adb to check for write permission. But I was able to modify the media file in the ui and change the effect tick so I know it works.
mistermojorizin said:
first of all, thanks so much, and i apologize for the noob questions below, but i'd like some clarification if possible (perhaps a video would be helpful like on your previous releases).
1) does it matter which version of your moto root app and SU we are currently using?
2) what do you mean in the OP by normal mode and recovery mode? I mean i've used custom recovery and normal (adb) mode, but when you say "recovery mode" will have write access, does that mean you will have write access only while you are in recovery? I think it means that you get into regular android operating system (that is adb), but through some extra boot/recovery step. This is confusing.
3) which custom recovery is the stock recovery being replaced with?
4) how do we tell it to boot in "recovery mode" or "normal mode"?
5) which version of supersu should we use? is the regular one OK?
6) which IRC are you referring to in the above quote?
Click to expand...
Click to collapse
Basically what is going on is if you go to fastboot mode vol - and power at the same time you have the option to boot into recovery, however it isn't actually booting into a normal or custom recovery where you can flash it boots normally but has no write protection so that you can write to the system. Then once you write you can reboot normally. Is that correct jcase?
Hi, i was using CM12.1, however I accepted an update and didn't figured out it was a CM13 Release, so when i dirty flashed the CM13 ROM over the CM 12.1 one, i got suspicious about something was wrong (due to the loading apps getting forever to configure)...the problem is that i tried then to patch gapps 6.0 and the recommended firmware to avoid problems but got many errors, then i tried to downgrade, however my TRWP just get stuck on the initial blue screen and just doesn't load, so i read what to do and did a downgrade using ToT back to Stock Verizone Firmware, and then tried to reinstall TWRP, i used ioroot to root my G3, then tried to reinstall TWRP but it always get an error, when the phone reboots to enter download mode it gets stuck in the LG Screen, and just stays there...i tried to enter TWRP like usual but the problem with the initial screen getting frozen is still there. I wanna get back to CM 12.1 but i have no idea how to make my TWRP work again
Hope you can help me out guys. Thanks
ezugaru said:
Hi, i was using CM12.1, however I accepted an update and didn't figured out it was a CM13 Release, so when i dirty flashed the CM13 ROM over the CM 12.1 one, i got suspicious about something was wrong (due to the loading apps getting forever to configure)...the problem is that i tried then to patch gapps 6.0 and the recommended firmware to avoid problems but got many errors, then i tried to downgrade, however my TRWP just get stuck on the initial blue screen and just doesn't load, so i read what to do and did a downgrade using ToT back to Stock Verizone Firmware, and then tried to reinstall TWRP, i used ioroot to root my G3, then tried to reinstall TWRP but it always get an error, when the phone reboots to enter download mode it gets stuck in the LG Screen, and just stays there...i tried to enter TWRP like usual but the problem with the initial screen getting frozen is still there. I wanna get back to CM 12.1 but i have no idea how to make my TWRP work again
Hope you can help me out guys. Thanks
Click to expand...
Click to collapse
I have the exact same problem, except I cannot downgrade at all. I get to the Download mode and nothing happens. The TWRP only gets to the initial TeamWin screen so I can't do anything through that route. I have no GAPPS and it really sucks. Any help would be appreciated
gypsydanger said:
I have the exact same problem, except I cannot downgrade at all. I get to the Download mode and nothing happens. The TWRP only gets to the initial TeamWin screen so I can't do anything through that route. I have no GAPPS and it really sucks. Any help would be appreciated
Click to expand...
Click to collapse
Hi, this is what i used to downgrade : http://forum.xda-developers.com/verizon-lg-g3/general/guide-flash-to-stock-10b-kdz-method-t2928140
Hope it helps, i'm at the office now, so when i get home I'll check where i got the resources to downgrade since i used my personal computer to do it.
Hey, i got it working now, i accessed the root files froma explorer in my G3, thn looked for the old recovery.img that were there and deleted them, then tried to reinstall it using adb, it shows 0+0 packages send to the phone, but it actually unblock the TWRP.
ezugaru said:
Hey, i got it working now, i accessed the root files froma explorer in my G3, thn looked for the old recovery.img that were there and deleted them, then tried to reinstall it using adb, it shows 0+0 packages send to the phone, but it actually unblock the TWRP.
Click to expand...
Click to collapse
what file explorer did you use and where was it located...I used es file explorer but cannot find that file
gypsydanger said:
what file explorer did you use and where was it located...I used es file explorer but cannot find that file
Click to expand...
Click to collapse
Try with Root Browser, then look for the Root / sdcard path and delete the recovery.img files, in my case there were 3 of them.
ezugaru said:
Try with Root Browser, then look for the Root / sdcard path and delete the recovery.img files, in my case there were 3 of them.
Click to expand...
Click to collapse
I don't have any of those .img files I tried following that guide as well and nothing happened it got to like 4% then said update failed due to an error. any ideas? I just need to get TWRP working again so I can do a clean flash, is there anyway I can reinstall TWRP it was originally installed through goomanager. tried updating there and it just reboots recovery to get stuck on the teamwin splash screen.
gypsydanger said:
I don't have any of those .img files I tried following that guide as well and nothing happened it got to like 4% then said update failed due to an error. any ideas? I just need to get TWRP working again so I can do a clean flash, is there anyway I can reinstall TWRP it was originally installed through goomanager. tried updating there and it just reboots recovery to get stuck on the teamwin splash screen.
Click to expand...
Click to collapse
I did it using the adb minimal tool, just placed the trwp 2.8.6.0 file into the root of sdcard folder, then using adb (phone must be connected to the laptop/pc in ethernet mode to be recognized) i ran
Code:
adb shell
command, after successfull initialize i used
Code:
su
(phone must be rooted to get a working su), and then i just ran the
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
command and the
Code:
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
command, during install it says 0+0 files sent, so i think it detects the trwp is already installed but still do something that fix the brick. Hope you can get it working.
ezugaru said:
I did it using the adb minimal tool, just placed the trwp 2.8.6.0 file into the root of sdcard folder, then using adb (phone must be connected to the laptop/pc in ethernet mode to be recognized) i ran
Code:
adb shell
command, after successfull initialize i used
Code:
su
(phone must be rooted to get a working su), and then i just ran the
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
command and the
Code:
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
command, during install it says 0+0 files sent, so i think it detects the trwp is already installed but still do something that fix the brick. Hope you can get it working.
Click to expand...
Click to collapse
when I run
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
I get permission denied
any thoughts on that? I still cannot figure this out ugh so much has changed since I have rooted my last phone
gypsydanger said:
when I run
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
I get permission denied
any thoughts on that? I still cannot figure this out ugh so much has changed since I have rooted my last phone
Click to expand...
Click to collapse
Did you give terminal root permissions by issuing the SU command and then granting the permissions on the phone?
[VK810.4G] [altev] [ViKtory810ROM] official LG G Pad 8.3 Lollipop 36B_00 5.0.2
[VK810.4G] [altev] official LG G Pad 8.3 Lollipop 36B_00 5.0.2 DEBLOAT SCRIPTS and copies of all the files they remove
[VK810.4G] [altev] OTAs, .IMGs and KDZs, oh my
I don't recall it asking me after entering the su command...it has asked me on the phone at some point tho, anyway to reset that? Ill be trying again on my lunch break. Thanks for the help so far ill keep updating my status.
gypsydanger said:
I don't recall it asking me after entering the su command...it has asked me on the phone at some point tho, anyway to reset that? Ill be trying again on my lunch break. Thanks for the help so far ill keep updating my status.
Click to expand...
Click to collapse
If you're using SuperSU, launch the app and look at the list of apps with both permanantly granted or denied superuser permissions. You can click on an app there to change it. Are you using a local Terminal emulator app? If so, that's what would request SU access when you enter the command, but if you've done SU in Terminal on this ROM installation before and you granted permanent SU permissions for it, it would give it again automatically when you enter the SU command.
If you're using ADB via USB from a PC, and you authorized USB Debugging on the phone prompt when you connected from the PC, and you then enter the SU command through the PC, I'm not sure what app shows up in the SuperSU app.
You're welcome, good luck!
---------- Post added at 08:39 AM ---------- Previous post was at 08:36 AM ----------
gypsydanger said:
I have the exact same problem, except I cannot downgrade at all. I get to the Download mode and nothing happens. The TWRP only gets to the initial TeamWin screen so I can't do anything through that route. I have no GAPPS and it really sucks. Any help would be appreciated
Click to expand...
Click to collapse
By the way, when using Download mode, what tool are you using with it? LG Flash Tool 2014? Did you previously install the Verizon specific LG drivers, reboot the PC, then connect the phone to the PC in Download mode to a USB 2.0 port with the original cable? Check in Device Manager to see if your phone is listed under Modems when your phone is in Download mode? It can take up to 5-10 minutes for the PC to load the driver you previously installed, each time you connect the phone to a different USB 2.0 port.
Sorry if any of this is repeating anything that's already been asked or suggested.
If you can get it to, I'd suggest flashing the 10B KDZ for the easiest to root with the Stump app in brute force mode, and put TWRP on with TWRP Manager.
roirraW "edor" ehT said:
If you're using SuperSU, launch the app and look at the list of apps with both permanantly granted or denied superuser permissions. You can click on an app there to change it. Are you using a local Terminal emulator app? If so, that's what would request SU access when you enter the command, but if you've done SU in Terminal on this ROM installation before and you granted permanent SU permissions for it, it would give it again automatically when you enter the SU command.
If you're using ADB via USB from a PC, and you authorized USB Debugging on the phone prompt when you connected from the PC, and you then enter the SU command through the PC, I'm not sure what app shows up in the SuperSU app.
You're welcome, good luck!
---------- Post added at 08:39 AM ---------- Previous post was at 08:36 AM ----------
By the way, when using Download mode, what tool are you using with it? LG Flash Tool 2014? Did you previously install the Verizon specific LG drivers, reboot the PC, then connect the phone to the PC in Download mode to a USB 2.0 port with the original cable? Check in Device Manager to see if your phone is listed under Modems when your phone is in Download mode? It can take up to 5-10 minutes for the PC to load the driver you previously installed, each time you connect the phone to a different USB 2.0 port.
Sorry if any of this is repeating anything that's already been asked or suggested.
If you can get it to, I'd suggest flashing the 10B KDZ for the easiest to root with the Stump app in brute force mode, and put TWRP on with TWRP Manager.
Click to expand...
Click to collapse
ok so I figured out the permission denied...somehow my root access in dev options got to off I changed it to adb and got this one to work
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
but this one says /sdcard not found...I created the folder and it still says not found.
Code:
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
where exactly does the recovery.img need to be located.
I am using LG Flash Tool 2014 and I have installed the specific drivers from lg and I can see my phone correctly in Device Manager. I just keep getting it stopped due to an error, but if I can get recovery working then I should be able to flash a stable CM for now.
gypsydanger said:
ok so I figured out the permission denied...somehow my root access in dev options got to off I changed it to adb and got this one to work
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
but this one says /sdcard not found...I created the folder and it still says not found.
Code:
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
where exactly does the recovery.img need to be located.
I am using LG Flash Tool 2014 and I have installed the specific drivers from lg and I can see my phone correctly in Device Manager. I just keep getting it stopped due to an error, but if I can get recovery working then I should be able to flash a stable CM for now.
Click to expand...
Click to collapse
the file goes in the root of storage, not in a folder, as shown in th pic.
if it says sdcard not found, you either entered the command wrong, or there is something wrong with your file system.
fyi, because the first command worked, you literally have no recovery now. thats what it does, empty the partition.
bweN diorD said:
the file goes in the root of storage, not in a folder, as shown in th pic.
if it says sdcard not found, you either entered the command wrong, or there is something wrong with your file system.
fyi, because the first command worked, you literally have no recovery now. thats what it does, empty the partition.
Click to expand...
Click to collapse
ok yes I have no recovery, that is correct...I put the recovery.img in /root and run the 2nd command again and it still says dd: /sdcard/recovery.img: No such file or directory
when I open up ES File Explorer it opens by default to /sdcard and immediately says /sdcard/ not found...if my file directory is messed up how do I go about getting it corrected?
edit: I used flashify and got TWRP back on successfully but it still won't go past teamwin splash screen....am I missing something I'm on cm 13.020151124-nightly-vs985.
is there a specific version of twrp I need for that nightly?
gypsydanger said:
ok yes I have no recovery, that is correct...I put the recovery.img in /root and run the 2nd command again and it still says dd: /sdcard/recovery.img: No such file or directory
when I open up ES File Explorer it opens by default to /sdcard and immediately says /sdcard/ not found...if my file directory is messed up how do I go about getting it corrected?
edit: I used flashify and got TWRP back on successfully but it still won't go past teamwin splash screen....am I missing something I'm on cm 13.020151124-nightly-vs985.
I'm attempting to wipe recovery again and try CWM to see if that will work.
Click to expand...
Click to collapse
unfortunately, i dont know how to fix it.
im betting stock wont flash because of whatever is damaged on your internal card.
i just looked back and noticed this all started with cm13. i have to wonder, how many phones are they going to break before they pull this update until a fix is found.
your is the first that i have come across that broke the internal card, but i have seen quite a few that broke the external.
im not suggesting you try this, as i really dont know what will happen.
as a last resort, you could try to zero out the data partition with dd code.
given the unknown damage to your card, i cant stress enough, this is a last resort, and may brick your phone.
normally, it should react like a factory reset, but if its still unable to use the internal properly afterwards, it very possibly may not boot fully or at all any more.
edit, as far as i know, the newest version is what they are using, but i dont know what that is specifically.
bweN diorD said:
unfortunately, i dont know how to fix it.
im betting stock wont flash because of whatever is damaged on your internal card.
i just looked back and noticed this all started with cm13. i have to wonder, how many phones are they going to break before they pull this update until a fix is found.
your is the first that i have come across that broke the internal card, but i have seen quite a few that broke the external.
im not suggesting you try this, as i really dont know what will happen.
as a last resort, you could try to zero out the data partition with dd code.
given the unknown damage to your card, i cant stress enough, this is a last resort, and may brick your phone.
normally, it should react like a factory reset, but if its still unable to use the internal properly afterwards, it very possibly may not boot fully or at all any more.
edit, as far as i know, the newest version is what they are using, but i dont know what that is specifically.
Click to expand...
Click to collapse
yea that scares me...now that I have made a little progress I'll try reverting to stock again the two ways I have found. I'll keep updating my progress.
gypsydanger said:
yea that scares me...now that I have made a little progress I'll try reverting to stock again the two ways I have found. I'll keep updating my progress.
Click to expand...
Click to collapse
so I have recovery back on my phone but it won't go past splash screen, I can remove recovery to where I have no recovery at all, everytime I put recovery back on from an app like Flashify it is successful but I can't get past the Splash screen of twrp...if i can get twrp or any other recovery on my phone i should be fine that is what is hanging me up...is there another recovery I can use with CM13 other than TWRP so I can try that and if so how do I get it onto my phone, I can't seem to get fastboot to work so help on that might be useful.
when I try the kdz method to revert to stock it fails due to an error...when I try the dll version to revert to stock it sits on waiting for connection, if I unplug the phone it errors out
gypsydanger said:
so I have recovery back on my phone but it won't go past splash screen, I can remove recovery to where I have no recovery at all, everytime I put recovery back on from an app like Flashify it is successful but I can't get past the Splash screen of twrp...if i can get twrp or any other recovery on my phone i should be fine that is what is hanging me up...is there another recovery I can use with CM13 other than TWRP so I can try that and if so how do I get it onto my phone, I can't seem to get fastboot to work so help on that might be useful.
when I try the kdz method to revert to stock it fails due to an error...when I try the dll version to revert to stock it sits on waiting for connection, if I unplug the phone it errors out
Click to expand...
Click to collapse
What error when flashing the KDZ? Most errors in LG Flash Tool 2014 should be totally ignored, just drag the dialog out of your way and don't press any buttons.
roirraW "edor" ehT said:
What error when flashing the KDZ? Most errors in LG Flash Tool 2014 should be totally ignored, just drag the dialog out of your way and don't press any buttons.
Click to expand...
Click to collapse
it says update failed due to an error and you have to hit retry or it does nothing...unless I need to just do nothing.
edit: IT WORKS YAY...all I did was retry and retry (definition of insanity) and the /sdcard just appeared then the dd command worked and I'm in recovery now yayayayayay
edit: edit: I did take out my eternal SD card so I am going to guess and say that that was the problem from the get go...anybody have any thoughts on that??
Go here for a updated TWRP thread!
Hey guys I have twrp here however I need help from the community.
The Twrp i have compiled, i have not tested everything yet, so please do not try any function yet, If you want to test out functionality, I found that reflashing stock system.img, boot.img, and recovery.img will probably reverse some damages, however I dont want anyone to mess their watch up (unless you are really brave) also guys flashing this twrp renders android wear useless so please do not flash it, this is going to be a tethered recovery for now. Only fastboot boot this thing anyways, with this itll help advance custom roms.
I have compiled the latest kernel, and I want to see if there is differences in the boot.img's that i have, and the ones that everyone else is running.
The kernel was giving me loads of build errors, but recently i had it built but I cant get it to boot android wear. My theory is that the boot.img i have, has .67, and i compiled .87, and there is something weird there. Unless my fixes broke the kernel, I have no idea but this will hopefully shine light on my issue. I did try .67 multiple times but untar'ing it gives errors and building it doesnt boot it, .87 doesnt have tar issues so IDK
Thanks /u/hamagc! Hopefully ill have something happen within a week or so!
Make sure you have adb & fastboot: This installer is for windows, and it installed adb, fastboot, and drivers with a few key presses
Download twrp here: and place it in a folder of your choice.
force the watch to power down by holding the button or power down in settings, when the screen goes black, repress and hold the button and swipe the screen from the upper left down to the lower right and that should bring up the ASUS logo with CSC Fastboot Mode! on the screen
Plug your watch in your computer and wait a few seconds then type in the CMD fastboot boot recovery.img and you should have a recovery to make backups or to flash supersu if needed
links:
System.img:
https://www.dropbox.com/s/pq03vrapclz3684/system.img?dl=0
Boot.img:
https://www.dropbox.com/s/p16n60s0s7wdbhh/boot.img?dl=0
good luck!!
hamagc said:
so attempting this for you, i get to twrp and push the fastboot dd if=/dev/block/mmcblk0p28 of=/sdcard/system.img command and i am left with a <waiting for device>.
scratch that, put commands into adb instead of fastboot and it's working. will have something for you shortly!
Click to expand...
Click to collapse
I forgot one step, with twrp on the watch, type in
adb shell
and then try the dd commands
T10NAZ said:
I forgot one step, with twrp on the watch, type in
adb shell
and then try the dd commands
Click to expand...
Click to collapse
yep, exactly what i had to do lol.
many thanks to you two
T10NAZ said:
I forgot one step, with twrp on the watch, type in
adb shell
and then try the dd commands
Click to expand...
Click to collapse
Fastboot booted the recovery and it boots into twrp just fine nice work!
EDIT: just took a full system and data backup and rooted the device with supersu and all is working fine
noahvt said:
Fastboot booted the recovery and it boots into twrp just fine nice work!
EDIT: just took a full system and data backup and rooted the device with supersu and all is working fine
Click to expand...
Click to collapse
Im really excited to hear that this is all working a-ok!!
noahvt said:
Fastboot booted the recovery and it boots into twrp just fine nice work!
EDIT: just took a full system and data backup and rooted the device with supersu and all is working fine
Click to expand...
Click to collapse
I thought if you rooted you get screwed for any and all future OTA updates? I swear I've heard that for multiple Android Wear watches.
parkerlreed said:
I thought if you rooted you get screwed for any and all future OTA updates? I swear I've heard that for multiple Android Wear watches.
Click to expand...
Click to collapse
I took a full twrp backup before root so I doubt that I won't get any available updates when I restore that backup
parkerlreed said:
I thought if you rooted you get screwed for any and all future OTA updates? I swear I've heard that for multiple Android Wear watches.
Click to expand...
Click to collapse
yes, that is my understanding, but if you make backups of everything before you root, and reflash it when an ota drops, you should be alright. However if I can get everything in working order, we can keep up with ota's in flashable rom form.
we now have access to clean system and boot images too if twrp decides not to restore your backups for some reason
Sweet!
Holy crap guys, I have a source built kernel booted!
Im adding some more features and seeing how stable it runs, so far i hit 1 random reboot, but it looks like its holding strong
This is a step by step guide for those who want root privileges on their watches. First of all, thanks to @rbox for the modified recovery image, and thanks to @Chainfire for the rooting files. Great developers.
I´ve used the latest superSU beta (systemless rooting), only deleting from the script the superuser.apk.
I´m not responsible for any damage. Do it knowing what you´re doing and at your own risk.
1- You must be in android wear 6.0.1 version. Download and unpack the rooting_files.rar (3 parts, xda format restrictions) and press shift button while right mouse click on a blank space on the folder. In the menu, select open command window here.
2- Reboot your watch in fastboot mode (power off the watch and power on sliding your finger from left top corner to right down corner) (or use adb command "adb reboot bootloader"). Connect it in the charging craddle to pc. If yout bootloader is locked, run "fastboot oem unlock" (It will factory reset your watch). If not, continue.
3- [optional] Flash through adb the twrp287 base image with the command "fastboot flash recovery twrp287.img"
4- Flash the modified twrp with "fastboot flash recovery twrp300modif.img"
5- Select recovery mode from fastboot menu and enter in twrp.
6- Push the wearSU267.zip into the internal memory with command "adb push wearSU267.zip /sdcard"
7- In TWRP select Install option and flash the wearSU267.zip. You may see some errors, ignore them.
8- Reboot your watch
You should have root now! Try it with a su command in terminal or any app.
I´ve included the original TWRP 3.0.0 image if anyone want to flash it after all.
Due to the new /system partition format, we cannot mount it in writable mode, so we cannot make changes inside at the moment, maybe someone can find a solution...
EXTRA: If you want change DPI, run this command: "adb shell wm density 180" (180 or whatever you want). The original value is 240 dpi.
Reserved
Nice tutorial! Currently flashing, I'll see if it works in a few minutes
Update: NICE! Worked like a charm!
Seeing as Busybox is used by almost all android wear apps would you not add it to the files? Also why are you flashing an old recovery and then the proper working one? Just flash the working one
Funciona de lujo, grax!
Xmaster24 said:
Seeing as Busybox is used by almost all android wear apps would you not add it to the files? Also why are you flashing an old recovery and then the proper working one? Just flash the working one
Click to expand...
Click to collapse
In the TWRP page it says the 3.0.0 image is an update, and must be flashed over an old version:
"TWRP Install (Requires TWRP 2.8.4 or higher already installed)"
https://twrp.me/devices/lggwatch.html
Anyway, it does not have effect, it is a precaution.
I´ve installed busybox after all through apk, but it´s not necessary for get root commands working
prototovsky said:
In the TWRP page it says the 3.0.0 image is an update, and must be flashed over an old version:
"TWRP Install (Requires TWRP 2.8.4 or higher already installed)"
https://twrp.me/devices/lggwatch.html
Click to expand...
Click to collapse
Em that's if your updating via recovery through fastboot your completely overwriting the recovery partition if you know how flashing works therefore the old version just disappears after flashing new version
Xmaster24 said:
Em that's if your updating via recovery through fastboot your completely overwriting the recovery partition if you know how flashing works therefore the old version just disappears after flashing new version
Click to expand...
Click to collapse
Then I´ll mark it as optional.
Knowledge is always collaborative
prototovsky said:
Then I�?�´ll mark it as optional.
Knowledge is always collaborative
Click to expand...
Click to collapse
Here's a link to my root method: Only 4 Steps you can take what you like from it http://forum.xda-developers.com/apps/supersu/android-wear-6-0-1-root-squashfs-t3319097/
Also thanks for info on dpi hate having 240 dpi even though it's the watches true dpi lol
Ok, so my watch is rooted now. Thanks! Now what?
jwinstonsf said:
Ok, so my watch is rooted now. Thanks! Now what?
Click to expand...
Click to collapse
Well I use kernel audiotor 4 wear, advanced settings(playstore) commandr, es file explorer (installed onto watch via adb) and minium wear
Xmaster24 said:
Well I use kernel audiotor 4 wear, advanced settings(playstore) commandr, es file explorer (installed onto watch via adb) and minium wear
Click to expand...
Click to collapse
my watch starts now only in twrp - the whole time - what can i do???
finrod2007 said:
my watch starts now only in twrp - the whole time - what can i do???
Click to expand...
Click to collapse
Try a factory reset in TWRP, if this does not work, reflash the rom
prototovsky said:
Try a factory reset in TWRP, if this does not work, reflash the rom
Click to expand...
Click to collapse
unable to mount ....system, data ....
finrod2007 said:
unable to mount ....system, data ....
Click to expand...
Click to collapse
Then reflash all (stock) through adb using this: http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863
prototovsky said:
Then reflash all (stock) through adb using this: http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863
Click to expand...
Click to collapse
thx, i think this will work out, i dont know what it is with twrp flashing supersu...
finrod2007 said:
thx, i think this will work out, i dont know what it is with twrp flashing supersu...
Click to expand...
Click to collapse
after point 5 of the tool - i stuck on bootlogo...made point 6 to restore the watch from stock but now it starts, starting the apps and do the same again and again, its going worser than better^^
finrod2007 said:
after point 5 of the tool - i stuck on bootlogo...made point 6 to restore the watch from stock but now it starts, starting the apps and do the same again and again, its going worser than better^^
Click to expand...
Click to collapse
Just use my method only 4 Steps and have debugged it completely so there should be no problems http://forum.xda-developers.com/g-watch/development/guide-how-to-root-lg-g-watch-6-0-1-t3320512
Xmaster24 said:
Just use my method only 4 Steps and have debugged it completely so there should be no problems http://forum.xda-developers.com/g-watch/development/guide-how-to-root-lg-g-watch-6-0-1-t3320512
Click to expand...
Click to collapse
yes of course I had known it before i had not done it, because everything was good, because then after point 6 i have android 5.1.1 on my watch, not android 6 any more, and its equal what i do nothing is changing when i start the watch, android is starting is finishing, watch starting again, doing this as again and again. i have done step 4 again, it does not change anything...
---------- Post added at 04:08 PM ---------- Previous post was at 04:07 PM ----------
finrod2007 said:
yes of course I had known it before i had not done it, because everything was good, because then after point 6 i have android 5.1.1 on my watch, not android 6 any more, and its equal what i do nothing is changing when i start the watch, android is starting is finishing, watch starting again, doing this as again and again. i have done step 4 again, it does not change anything...
Click to expand...
Click to collapse
but i will do your method now, maybe need a fresh stock rom which i can flash with a .bat file or something like that. are there any links???
finrod2007 said:
yes of course I had known it before i had not done it, because everything was good, because then after point 6 i have android 5.1.1 on my watch, not android 6 any more, and its equal what i do nothing is changing when i start the watch, android is starting is finishing, watch starting again, doing this as again and again. i have done step 4 again, it does not change anything...
---------- Post added at 04:08 PM ---------- Previous post was at 04:07 PM ----------
but i will do your method now, maybe need a fresh stock rom which i can flash with a .bat file or something like that. are there any links???
Click to expand...
Click to collapse
Will send you stock system.img, and you can use invisiblek's kernel or stock boot.img cause they are both working fine just format the others (/data and /cache)
Hello,
Recently I achieved root on my Fire via KingRoot on Fire OS 5.0.1. I disabled the Fire Launcher, and then I stupidly decided to remove KingUser and replace it with SuperSU with SuperSU-Me. Long story short, I rebooted the device when SuperSU finished updating the binaries, and I was greeted with a bricked Fire that would stay on the Fire screen but would not dim and do much else. I can get ADB access, but my Windows PC says that the device is unauthorized and my Linux box says that the device is offline. Any help? I am kind of lost as to what I can do. Thank you in advance
HyperNyan said:
Hello,
Recently I achieved root on my Fire via KingRoot on Fire OS 5.0.1. I disabled the Fire Launcher, and then I stupidly decided to remove KingUser and replace it with SuperSU with SuperSU-Me. Long story short, I rebooted the device when SuperSU finished updating the binaries, and I was greeted with a bricked Fire that would stay on the Fire screen but would not dim and do much else. I can get ADB access, but my Windows PC says that the device is unauthorized and my Linux box says that the device is offline. Any help? I am kind of lost as to what I can do. Thank you in advance
Click to expand...
Click to collapse
Can you get into recovery by holding Power and Volume-Up?
DoLooper said:
Can you get into recovery by holding Power and Volume-Up?
Click to expand...
Click to collapse
Yes, I indeed can get into recovery mode! There might be some hope for my tablet
HyperNyan said:
Yes, I indeed can get into recovery mode! There might be some hope for my tablet
Click to expand...
Click to collapse
Yes, indeed! You can sideload the latest Amazon update. It's 5.1.1. (AFAIK, the November 5.0.1 is not available.) Get the update here: http://kindle-fire-updates.s3.amazo...aZE/update-kindle-20.5.4.1_user_541113320.bin
In recovery, highlight the adb sideload option and press power to get into sideload mode. I don't know linux, but if using Windows install adb drivers. Now, from CMD window, type:
adb sideload <name of the update file>
The update will install and you should be able to boot. You can root with kingroot. After rooting, read/use @bibikalka's guide to reinstall 5.1.1 with SuperSU (to kill Kingroot) and to install Gapps.
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
DoLooper said:
Yes, indeed! You can sideload the latest Amazon update. It's 5.1.1. (AFAIK, the November 5.0.1 is not available.) Get the update here: http://kindle-fire-updates.s3.amazo...aZE/update-kindle-20.5.4.1_user_541113320.bin
In recovery, highlight the adb sideload option and press power to get into sideload mode. I don't know linux, but if using Windows install adb drivers. Now, from CMD window, type:
adb sideload <name of the update file>
The update will install and you should be able to boot. You can root with kingroot. After rooting, read/use @bibikalka's guide to reinstall 5.1.1 with SuperSU (to kill Kingroot) and to install Gapps.
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
Click to expand...
Click to collapse
Thank you! My Fire tablet is now able to boot and can run normally, but with root access this time Thank you for helping me through this issue
Update:
I tried to install TWRP without reading that it would not work on the newer Fire OS bootloader, and now I am stuck with no recovery. Attempting to boot into TWRP results in a black screen after the Amazon logo and then it reboots into the OS. I do have access to Android, but I cannot flash the stock recovery as I am currently without a recovery. Any pointers as to how I can possibly get the stock recovery again so then I can redo the whole process of attempting to install CM11?
You may be able to dd the recovery partition. Someone else will have to help with that.
HyperNyan said:
Update:
I tried to install TWRP without reading that it would not work on the newer Fire OS bootloader, and now I am stuck with no recovery. Attempting to boot into TWRP results in a black screen after the Amazon logo and then it reboots into the OS. I do have access to Android, but I cannot flash the stock recovery as I am currently without a recovery. Any pointers as to how I can possibly get the stock recovery again so then I can redo the whole process of attempting to install CM11?
Click to expand...
Click to collapse
Just do this, run the script provided :
http://forum.xda-developers.com/showpost.php?p=62011272&postcount=2
I'll get you TWRP and 4.5.3 bootloaders. Then flash 5.4.1 stuff from TWRP.
DoLooper said:
Yes, indeed! You can sideload the latest Amazon update. It's 5.1.1. (AFAIK, the November 5.0.1 is not available.) Get the update here: http://kindle-fire-updates.s3.amazo...aZE/update-kindle-20.5.4.1_user_541113320.bin
In recovery, highlight the adb sideload option and press power to get into sideload mode. I don't know linux, but if using Windows install adb drivers. Now, from CMD window, type:
adb sideload <name of the update file>
The update will install and you should be able to boot. You can root with kingroot. After rooting, read/use @bibikalka's guide to reinstall 5.1.1 with SuperSU (to kill Kingroot) and to install Gapps.
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
Click to expand...
Click to collapse
THANK YOU SO EFFING MUCH! I thought my HD6 was done. I was beginning to panic. I went through a LOT of guides to fix it and nothing worked except what you posted.
I know this thread is pretty old, but I haven't fixed the recovery issue yet due to being scared of bricking my tablet. So, just asking, which script do I run? Thanks!
HyperNyan said:
I know this thread is pretty old, but I haven't fixed the recovery issue yet due to being scared of bricking my tablet. So, just asking, which script do I run? Thanks!
Click to expand...
Click to collapse
The recommendations have not changed since the last time you asked Either install stock recovery via Flashify (dig out the recovery image from this zip : 5.2.0_stock_recovery_only.zip , here : http://forum.xda-developers.com/showpost.php?p=62011272 ), or run the script in post #2, and from TWRP, re-install 5.4.1 bootloaders :
http://forum.xda-developers.com/showpost.php?p=62011272&postcount=2
Thank you! My tablet is now working great, TWRP successfully installed. Just about a few minutes ago I had a panic attack when it started boot-looping, but then I shut it off for a while, and booted it into TWRP, and it was fine. Go figure I will now attempt to install cm11! Thank you for all of your help!