Dear XDA Members,
I´ve currently downloaded the software update which came out yesterday and my phone asked me if i wanted to update. I did so, and afterwards it rebooted straight into TWRP. I´ve tried several things like rebooting, mounting, erase dalvin cache etc. etc.,
In the end I also totally erased all files on my phone (which i believe was the most stupid thing I can do) and that´s why I am here right now:
I´ve got my LG G2 International version which has only TWRP on it.
My Question is now:
How can I get a custom rom on the internal memory? (Don´t really now how to work ADB Sideload)
How can I mount the device because it does not get recognised if I do the mounting within TWRP?
Literally every help is hiiiighly appreciated!
ij78cp said:
Dear XDA Members,
I´ve currently downloaded the software update which came out yesterday and my phone asked me if i wanted to update. I did so, and afterwards it rebooted straight into TWRP. I´ve tried several things like rebooting, mounting, erase dalvin cache etc. etc.,
In the end I also totally erased all files on my phone (which i believe was the most stupid thing I can do) and that´s why I am here right now:
I´ve got my LG G2 International version which has only TWRP on it.
My Question is now:
How can I get a custom rom on the internal memory? (Don´t really now how to work ADB Sideload)
How can I mount the device because it does not get recognised if I do the mounting within TWRP?
Literally every help is hiiiighly appreciated!
Click to expand...
Click to collapse
From the TWRP terminal command (from the Main Menu > Advanced) type:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit Enter
type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit Enter
Then reboot. If it doesn't fully reboot, you should be able to at least get to Download Mode to reinstall the stock firmware.
es0tericcha0s said:
From the TWRP terminal command (from the Main Menu > Advanced) type:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit Enter
type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit Enter
Then reboot. If it doesn't fully reboot, you should be able to at least get to Download Mode to reinstall the stock firmware.
Click to expand...
Click to collapse
Hey thanks for the reply,
I finally was able to send sth. through adb on the device, the problem now was that it said that MD5 file not found (i tried to flash CM11 for the G2)
any ideas?
ij78cp said:
Hey thanks for the reply,
I finally was able to send sth. through adb on the device, the problem now was that it said that MD5 file not found (i tried to flash CM11 for the G2)
any ideas?
Click to expand...
Click to collapse
I flashed the CM11 now since other posts online it doesn´t matter with the missing MD5 file but I´m still always booting into TWRP... someone posted that it could be that I have the recovery in the boot participation??
I´m out of options does anyone have an idea?
ij78cp said:
I flashed the CM11 now since other posts online it doesn´t matter with the missing MD5 file but I´m still always booting into TWRP... someone posted that it could be that I have the recovery in the boot participation??
I´m out of options does anyone have an idea?
Click to expand...
Click to collapse
Did you try what I suggested? It doesn't sound like it...
es0tericcha0s said:
Did you try what I suggested? It doesn't sound like it...
Click to expand...
Click to collapse
Sorry I though I posted another reply yesterday:
I finally fixed it yesterday... I finally was able to move roms with adb sideload on the phone, installed everything... Was still stuck on the bootloop after that but at least a rom was installed... then I used the top line of the code you posted here in the terminal command... after that everything worked smoothly
Thank you so much for ur help
ij78cp said:
Sorry I though I posted another reply yesterday:
I finally fixed it yesterday... I finally was able to move roms with adb sideload on the phone, installed everything... Was still stuck on the bootloop after that but at least a rom was installed... then I used the top line of the code you posted here in the terminal command... after that everything worked smoothly
Thank you so much for ur help
Click to expand...
Click to collapse
:good::highfive::victory:
Hi everyone
I own an Amazon Fire HD 6 and I love it. It's a powerful little machine, but Fire OS 4.5.3 sucks. I've been looking to root it and run a custom ROM on the device since I got it in December 2014, but I never got around to doing it until now. (And there weren't instructions back then.)
I managed to follow instructions posted by @bibikalka that have proven to be very helpful, but I started encountering a problem at step 2).
bibikalka said:
[DONE] 0) get ADB drivers working on your PC, etc:
http://forum.xda-developers.com/fire-hd/general/root-supersu-stable-appstore-custom-t3113311
Tip: A quick way to debug your adb connectivity issues is to use USBDeView : http://www.nirsoft.net/utils/usb_devices_view.html
[DONE] 1) Determine your FireOS version, versions up to 4.5.3 are rootable, 4.5.4 will need to be upgraded to 5.0.2 and then downgraded to 4.5.3 :
http://forum.xda-developers.com/fire-hd/general/how-to-downgrade-to-4-5-3-root-device-t3139351
[DONE, WITH EXCEPTION] 2) Disable OTA updates ( adb shell ; pm block com.amazon.dcp or "Debloater" http://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294 ),
sideload Kingroot ( http://androidxda.com/download-kingroot-application ),
and let it root. Don't bother with SuperSu at this stage, you'll get it done later.
Click to expand...
Click to collapse
My Fire HD 6 shows up without error in
Code:
adb devices
but when I attempted to sideload Kingroot via
Code:
adb reboot recovery
I got the following error:
Code:
Fire System Recovery
Your Fire doesn't seem to be able to boot. Reseting your device to Factory defaults may help you to fix this issue.
I've since attempted to reset it to Factory defaults, but after trying to boot into recovery afterward, I didn't have any success.
I took it a step further by using the following code to install Kingroot:
Code:
adb install Kingroot_V4.5.0.722.apk
This worked and Kingroot rooted the device without error, but I'm curious to know if this is a big deal since I didn't sideloading the app.
The problem I have now is with sideloading the TWRP image. Without access to recovery, this doesn't appear to be possible. But how can I get my recovery back? I've done some research and apparently this is so messed up that I may need to purchase a factory cable, but I'm curious to know if anyone has any other advice or can help me better understand what went wrong.
Thanks in advance.
Is recovery gone?
pantyman said:
I managed to follow instructions posted by @bibikalka that have proven to be very helpful, but I started encountering a problem at step 2).
My Fire HD 6 shows up without error in . . . adb devices . . . but when I attempted to sideload Kingroot via . . . adb reboot recovery . . . I got the following error:
Fire System Recovery
Your Fire doesn't seem to be able to boot. Reseting your device to Factory defaults may help you to fix this issue.
Click to expand...
Click to collapse
Please do nothing more until @bibikalka or someone else can help you deal with the recovery issue. I'll just point out a few things:
(1) You don't sideload an apk in recovery. (I suspect you know this. For an apk, sideload just means copy/move the apk to the device and install it, with a file manager usually, whereas "adb sideload" from recovery is for bin, zip files.)
I've since attempted to reset it to Factory defaults, but after trying to boot into recovery afterward, I didn't have any success.
Click to expand...
Click to collapse
(2) I assume you got above error again. This is where you need someone else's help.
I took it a step further by using the following code to install Kingroot:
Code:
adb install Kingroot_V4.5.0.722.apk
This worked and Kingroot rooted the device without error, but I'm curious to know if this is a big deal since I didn't sideloading the app.
Click to expand...
Click to collapse
(3) Not a big deal. You got it installed.
The problem I have now is with sideloading the TWRP image. Without access to recovery, this doesn't appear to be possible.
Click to expand...
Click to collapse
(4) You don't adb sideload TWRP. Although there are other methods, we've been using TWRP Manager or Flashify. (Guide). As said, I wouldn't do anything until you figure out the status of recovery.
But how can I get my recovery back? I've done some research and apparently this is so messed up that I may need to purchase a factory cable, but I'm curious to know if anyone has any other advice or can help me better understand what went wrong.
Click to expand...
Click to collapse
Factory (fastboot) cable's don't work with this device; you get into fastboot mode with "adb reboot fastboot," but doing that would be a bad idea right now.
DoLooper said:
Please do nothing more until @bibikalka or someone else can help you deal with the recovery issue. I'll just point out a few things:
(1) You don't sideload an apk in recovery. (I suspect you know this. For an apk, sideload just means copy/move the apk to the device and install it, with a file manager usually, whereas "adb sideload" from recovery is for bin, zip files.)
(2) I assume you got above error again. This is where you need someone else's help.
(3) Not a big deal. You got it installed.
(4) You don't adb sideload TWRP. Although there are other methods, we've been using TWRP Manager or Flashify. (Guide). As said, I wouldn't do anything until you figure out the status of recovery.
Factory (fastboot) cable's don't work with this device; you get into fastboot mode with "adb reboot fastboot," but doing that would be a bad idea right now.
Click to expand...
Click to collapse
Thanks a lot for all of your advice, @DoLooper. I've since actually gotten everything to work by following instructions by @r3pwn on his alternate unbricking method for the Kindle Fire HDX 7" & 8.9"
No issues for me any more! The only thing I have to look for now is a good launcher for this thing. I'm not a big fan of the Vire Launcher.
I'm having this same problem but was unable to fix via the thread linked.
Help please?
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
A while back, Amazon automatically pushed an update to my kid's Fire HD 6. Since then, the device will boot up and then it just freezes. The screen stays on the device is unresponsive. I am able to get in to recovery on the device, and that all seems to work fine, but booting in to Android is useless because it just locks and you cannot do anything with it.
I have been trying to go through this forum to see what my options are for sideloading another firmware or TWRP or anything like that.. and the posts here are not entirely helpful (for me at least). I'm used to going in to recovery and flashing some zip files to install TWRP, Cyanogenmod or GAPPS or anything like that... but the instructions I see for installing TWRP and the like do not seem to be the traditional methods. From what I think I am seeing, to install TWRP you need shell access to the tablet and then you can use dd to write TWRP to the correct storage space.
What are my options for doing things through recovery with adb? Or can I load an old firmware and then go from there? Any help is appreciated - would really love to get CM12 on this thing in the end if I could.
ganiman said:
A while back, Amazon automatically pushed an update to my kid's Fire HD 6. Since then, the device will boot up and then it just freezes. The screen stays on the device is unresponsive. I am able to get in to recovery on the device, and that all seems to work fine, but booting in to Android is useless because it just locks and you cannot do anything with it.
I have been trying to go through this forum to see what my options are for sideloading another firmware or TWRP or anything like that.. and the posts here are not entirely helpful (for me at least). I'm used to going in to recovery and flashing some zip files to install TWRP, Cyanogenmod or GAPPS or anything like that... but the instructions I see for installing TWRP and the like do not seem to be the traditional methods. From what I think I am seeing, to install TWRP you need shell access to the tablet and then you can use dd to write TWRP to the correct storage space.
What are my options for doing things through recovery with adb? Or can I load an old firmware and then go from there? Any help is appreciated - would really love to get CM12 on this thing in the end if I could.
Click to expand...
Click to collapse
Your understanding of TWRP is right. Basically, we dd the twrp image with OS 4.5.3 bootloaders (the only bootloaders that will boot unsigned recovery) and then before leaving TWRP flash back (almost) current bootloaders and recovery.
You should be able to adb-sideload the OS 5.1.2 update to fix the freeze. Was device rooted before it updated? Do you know what OS it was on? If you have adb access while device is frozen, run these commands for current OS info:
adb shell getprop ro.build.version.fireos
adb shell getprop ro.build.version.number
No CM12 available. Mostly-working CM11 is here: http://forum.xda-developers.com/fire-hd/orig-development/rom-cm-11-kindle-hd6-t3270138
BTW, I assume you tried wiping cache and/or factory reset in recovery. If not, I'd do that first.