Related
This mod is no longer being developed.
In case you haven't noticed, it's been deprecated for some time now.
Status Bar Mod for the TrueSmartThis mod adds the Status Bar back to your device. It should work on all ROMS (though I can't make any promises for non TS devices.)
Installation
Download the zip and move to your SD card.
Disable Quick Boot!!! and reboot into recovery.
Perform a NANDroid backup (Highly recommended!)
Flash the mod.
[*]Preform a Factory Reset!!
TroubleshootingIf you do end up in a bootloop, ensure you preformed a factory reset
It may sometimes take a few minutes for the device to preform dex operations, be patient.
Ensure you are on the 1/20/2014 firmware
Get a logcat (adb logcat > log.txt) before asking for help, I am not at your device, seriously, help me out here.
The status bar can be hidden using the Xposed module GravityBox.
If all else fails, restore that NANDroid backup you made earlier.
Jarocks said:
This mod will bring back the status bar on all apps as well as a add more vanilla Settings app.
I've move around some settings, Quick Boot is now under Development Settings. Auto Rotate to display settings. A shortcut to engineering mode can be found under Development Settings.
Enjoy the fruits of my 100th post
Flash in TWRP.
Click to expand...
Click to collapse
How I install it?
Is this for the stock ROM only?
lirona said:
How I install it?
Click to expand...
Click to collapse
Download the zip file to your SD Card and flash it in TWRP recovery.
Please see this thread for information and resources to install TWRP:
http://forum.xda-developers.com/showthread.php?t=2574980
gigaguy said:
Is this for the stock ROM only?
Click to expand...
Click to collapse
It should work on any ROM
Jarocks;51157651
It should work on any ROM[/QUOTE said:
FYI, got boot loop flashing it on Loki's Operative ROM.
Click to expand...
Click to collapse
gigaguy said:
FYI, got boot loop flashing it on Loki's Operative ROM.
Click to expand...
Click to collapse
Me too, I had to go back to an earlier backup
did somebody flash it with success on Lokifish's patch ?
cyrilp said:
did somebody flash it with success on Lokifish's patch ?
Click to expand...
Click to collapse
Nope. Mine is stuck at the omate screen and doesn't go past it. Might have to pull the battery.
UPDATE:
I've now flashed back to stock. Re-flashed this over stock, got another boot loop. Wiped again, reflashed, same deal. Wiped again, no flash, got into the OS, but the update didn't change the status bar.
Any time I flash this over a fresh wipe, I get a boot loop.
Anyone else have any other experiences?
mortis2600 said:
Nope. Mine is stuck at the omate screen and doesn't go past it. Might have to pull the battery.
Click to expand...
Click to collapse
I thought i'd have to pull battery too, but if you can connect to a pc with the drivers, and adb installed you can do "adb reboot recovery"
gigaguy said:
I thought i'd have to pull battery too, but if you can connect to a pc with the drivers, and adb installed you can do "adb reboot recovery"
Click to expand...
Click to collapse
Yeah, it wouldn't let me do that. I had to pull the battery.
Though I can adb reboot now when I get stuck on the loading screen now after I've flashed back to stock.
Me thinks this mod is borked.
---------- Post added at 10:58 AM ---------- Previous post was at 10:56 AM ----------
Jarocks said:
Download the zip file to your SD Card and flash it in TWRP recovery.
Please see this thread for information and resources to install TWRP:
http://forum.xda-developers.com/showthread.php?t=2574980
It should work on any ROM
Click to expand...
Click to collapse
Hey Jarocks,
I'm getting the same issue despite being on stock or on lokifish's mod. Any idea what's causing it?
For those of you in a bootloop try running the following adb commands and rebooting. You may also need to wipe the cache as well.
Code:
adb remount
adb shell rm /system/app/Settings.odex
adb shell rm /system/framework/android.policy.odex
adb reboot
If any take a couple mins to boot up.
Edit:
A fix has been posted in the OP, sorry guys.
Tapatalked from my HTC Droid DNA
Jarocks said:
For those of you in a bootloop try running the following adb commands and rebooting. You may also need to wipe the cache as well.
Code:
adb remount
adb shell rm /system/app/Settings.odex
adb shell rm /system/framework/android.policy.odex
adb reboot
If any take a couple mins to boot up.
Edit:
A fix has been posted in the OP, sorry guys.
Tapatalked from my HTC Droid DNA
Click to expand...
Click to collapse
Thanks for the swift response!
mortis2600 said:
Thanks for the swift response!
Click to expand...
Click to collapse
Please let me know if it fixes your bootloop issue.
Jarocks said:
Please let me know if it fixes your bootloop issue.
Click to expand...
Click to collapse
No luck.
Here's what I've done:
Restored back to Stock
Booted into the OS
Unchecked Quickboot
Rebooted into TWRP
Flashed the updated MOD
Cleared Cache
Stuck at the boot screen
ADB Reboot Recovery
run the commands you listed in a previous post
none of the files are found
Reboot back into boot loop
It's still not working quite right.
So the mod also caused a boot loop and while trying to fix it I managed to wipe my OS. Now I can only boot into TWRP and that's it. Anything I could do to flash the OS. SP flash tools won't recognize my device? I feel like a complete noob!
blu05r6strtbike said:
So the mod also caused a boot loop and while trying to fix it I managed to wipe my OS. Now I can only boot into TWRP and that's it. Anything I could do to flash the OS. SP flash tools won't recognize my device? I feel like a complete noob!
Click to expand...
Click to collapse
SP Flash tool doesn't need to have an OS to recover. So all is not lost. It just takes some tinkering to get it working right. Make sure you follow the steps in the unbrick thread exactly. You may have to plug/unplug with the watch OFF a few times to get it to recognize.
mortis2600 said:
SP Flash tool doesn't need to have an OS to recover. So all is not lost. It just takes some tinkering to get it working right. Make sure you follow the steps in the unbrick thread exactly. You may have to plug/unplug with the watch OFF a few times to get it to recognize.
Click to expand...
Click to collapse
I'll try unplugging it a few times. I followed the guide and reinstalled the drivers but now when I plug it in the driver says unable to install. I'm going to keep trying.
What devices do you both have?
Sent from my GT-N5110 using Tapatalk
Jarocks said:
What devices do you both have?
Sent from my GT-N5110 using Tapatalk
Click to expand...
Click to collapse
Omate true smart. 1/8 us
Jarocks said:
What devices do you both have?
Sent from my GT-N5110 using Tapatalk
Click to expand...
Click to collapse
Omate TrueSmart 1/8GB 1900 (USA)
Baseband is updated to the latest via lokifish's post.
I'm sorry if this isn't the right place.
I rooted my LG G2 D802 around 2 months ago, and completely forgot about it.
I got the Kitkat update about 5 hours ago, and stupidly downloaded it.
The phone got stuck in a team win bootloop and again, in a bit of a panic I wiped the phone (not thinking of just restoring my back up from when i rooted the device)
after that didn't solve anything, i reverted to google. I found a guide on here for my exact problem http://forum.xda-developers.com/showthread.php?t=2451696
I read it carefully and proceeded to follow this by the letter. I think I messed up though, with the 'ADB' thing, the last i remembered about it was using it to root the device, so I followed to guide but using the root folder i had used. now I'm no longer in a team win bootloop, I'm not in a LG splash screen boot loop, I can just about manage to get into recovery and get back to team win, but can't get into download mode.
I really wasn't looking to replace this device until the LG G3 got released, and don't really have the money to spare - so i'm really hoping this is fixable.
a note is, to root the device i followed a guide, and the TWRP (I'm not actually sure) I think i just went with it and managed it so i'm not very good when it comes to the terms, and stuff like that, any help would be greatly appreciated!
I can use a Win7 laptop to do whatever is needed, it is an EE LG G2 D802, UK, 16GB black.
I don't have insurance, I kept pushing myself to wait to do anything like this until I had insurance, but at 2 in the morning, nothing to do, ready to root - It's hard to resist.
(I do have the USB drivers on my laptop)
Sounds like you are in this boat now:
http://forum.xda-developers.com/showthread.php?t=2582142
That should do the trick since it's exactly what's happened to you and the same phone. The update might be different though as that is important to know. Just use the files from whichever the last official update you had was from.
es0tericcha0s said:
Sounds like you are in this boat now:
http://forum.xda-developers.com/showthread.php?t=2582142
That should do the trick since it's exactly what's happened to you and the same phone. The update might be different though as that is important to know. Just use the files from whichever the last official update you had was from.
Click to expand...
Click to collapse
I dont think thats the same problem as mine, i have no error, my screen doesnt go off, it just stays on lg splash screen with multicoloured led flashing, cant turn it off only restart it, i dont have linux & i can get into recovery with a few attempts. Is there anythjng that can be done or is my phone ****ed? Thanks
I have just had another read through, mainly the comments and that guide seems to get you to the point where you can get into recovery and enter those commands in the guide on my opening post - i can get into recovery and i did both fixes, the one using adb if using the adb in the root folder on my laptop i used to root the device is okay, and then again using the terminal emulator in recovery, after neither worked (actually, the terminal emulator one got me from a TWRP bootloop into an lg splash screen bootloop, after reading into thr comment to about page 7 there was an additional line to the terminal emulator method changing only the /fota to /misc which did nothing for my device. The fix there simply changed the type of bootloop i am in
yoalphadied said:
I dont think thats the same problem as mine, i have no error, my screen doesnt go off, it just stays on lg splash screen with multicoloured led flashing, cant turn it off only restart it, i dont have linux & i can get into recovery with a few attempts. Is there anythjng that can be done or is my phone ****ed? Thanks
Click to expand...
Click to collapse
Oh ok. Well, if you can still get into recovery, then you should be able to push another rom to the phone's storage via adb. But your phone definitely isn't screwed. It's pretty hard to totally mess these things up to the point of no return.
es0tericcha0s said:
Oh ok. Well, if you can still get into recovery, then you should be able to push another rom to the phone's storage via adb. But your phone definitely isn't screwed. It's pretty hard to totally mess these things up to the point of no return.
Click to expand...
Click to collapse
Im glad to hear it, got to the point of looking at a new ouone even though i wanted to keep this one until the g3 was on the shelves.
I hate to say, but how would i do this? I only know the very basics, and is the adb used to root fine to do it with? I didnt even know i had flashed TWRP correctly, think i used an app, flashify or something? Any help would be massively appreciated
yoalphadied said:
Im glad to hear it, got to the point of looking at a new ouone even though i wanted to keep this one until the g3 was on the shelves.
I hate to say, but how would i do this? I only know the very basics, and is the adb used to root fine to do it with? I didnt even know i had flashed TWRP correctly, think i used an app, flashify or something? Any help would be massively appreciated
Click to expand...
Click to collapse
So, boot to recovery and plug it in. Your PC SHOULD load the right drivers if you have already installed them. You can verify by going to your Device Mananger and making sure there are no warning signs next to your phone in the list.
If you need the drivers: https://mega.co.nz/#!rU0RkSaK!JzUCoZ5emWOsc_Tw6h8a3JZtRNT1-JvGvc8EC_u9rnI
adb and fastboot files: https://mega.co.nz/#!SJ8ijCKY!UKpr4ufVyPq4DVL2i90RI9CD7TX5AETPHrcqMQdpG5w
Download the rom you need and move it to the folder where the adb and fastboot stuff installs to. Should be C / Program Files (86) / adb
Once there and the drivers are loaded correctly, use the CMD shortcut from the adb set up and do this:
adb devices
If you get are response of some random string of letters + numbers, it's all good.
adb push nameofrom.zip /sdcard/
and then wait. It will take some time as these are large files. Not uncommon for it to take many minutes to 10 or more.
es0tericcha0s said:
So, boot to recovery and plug it in. Your PC SHOULD load the right drivers if you have already installed them. You can verify by going to your Device Mananger and making sure there are no warning signs next to your phone in the list.
If you need the drivers: link
adb and fastboot files: link
Download the rom you need and move it to the folder where the adb and fastboot stuff installs to. Should be C / Program Files (86) / adb
Once there and the drivers are loaded correctly, use the CMD shortcut from the adb set up and do this:
adb devices
If you get are response of some random string of letters + numbers, it's all good.
adb push nameofrom.zip /sdcard/
and then wait. It will take some time as these are large files. Not uncommon for it to take many minutes to 10 or more.
Click to expand...
Click to collapse
Just making sure I understand correctly, the 'rom' i need ks the stock rom, right? Im not looking to root again as the whole reason i rooted was because it was everywhere that ee werent releasing the kitkat update for the g2, since they have now i dont need root anymore.
Ill try this fix later on and tell you if it worked! Thanks
es0tericcha0s said:
So, boot to recovery and plug it in. Your PC SHOULD load the right drivers if you have already installed them. You can verify by going to your Device Mananger and making sure there are no warning signs next to your phone in the list.
If you need the drivers: link
adb and fastboot files: link
Download the rom you need and move it to the folder where the adb and fastboot stuff installs to. Should be C / Program Files (86) / adb
Once there and the drivers are loaded correctly, use the CMD shortcut from the adb set up and do this:
adb devices
If you get are response of some random string of letters + numbers, it's all good.
adb push nameofrom.zip /sdcard/
and then wait. It will take some time as these are large files. Not uncommon for it to take many minutes to 10 or more.
Click to expand...
Click to collapse
Okay, I can't seem to find the LG G2's stock rom anywhere, also the adb push nameofrom.zip /sdcard/ is that the exact command?
I found the stock firmware, but nothing for EE, just o2 and so on.
I also can't seem to get the drivers to work, I have an 'unidentified device' connected to the computer, I have tried to download from the link you gave me, and another place but neither work, once it searches for drivers again after download it just says drivers not found
saying that after trying 'adb devices' i got a random string of letters and numbers, roughly 21 characters long followed by recovery on the same line
yoalphadied said:
Okay, I can't seem to find the LG G2's stock rom anywhere, also the adb push nameofrom.zip /sdcard/ is that the exact command?
I found the stock firmware, but nothing for EE, just o2 and so on.
I also can't seem to get the drivers to work, I have an 'unidentified device' connected to the computer, I have tried to download from the link you gave me, and another place but neither work, once it searches for drivers again after download it just says drivers not found
saying that after trying 'adb devices' i got a random string of letters and numbers, roughly 21 characters long followed by recovery on the same line
Click to expand...
Click to collapse
Hmm if adb devices returned that, that means adb is working which means at least part of the drivers loaded correctly. I would grab the files from here:
http://forum.xda-developers.com/showthread.php?t=2736854
And then adb push the files to the /sdcard/. You want the Philz recovery, and the rom. You can grab the root and the kernel if you want to be rooted and the kernel might make a difference in battery life and performance. Whether that is a positive or negative influence, I've no clue. The poster seemed to like it, and he would know better than I. So you just want to download the files needed and put them in the same folder where you have your adb files. Then for each one you want to use:
adb push
then
nameoffile.zip - where you fill in the name of file with whatever (you can rename the files - but not extensions - to be easier, ie recovery.zip, rom.zip)
then /sdcard/
Full command of pushing the rom to the internal storage, assuming you renamed it to rom.zip would be:
adb push rom.zip /sdcard/
This will take awhile. Probably a good 10 minutes.
After you get it transferred over, then install the recovery zip in your current recovery and then reboot to recovery again so you will be in the new Philz. Then do a factory reset and install the rom zip.
es0tericcha0s said:
Hmm if adb devices returned that, that means adb is working which means at least part of the drivers loaded correctly. I would grab the files from here:
And then adb push the files to the /sdcard/. You want the Philz recovery, and the rom. You can grab the root and the kernel if you want to be rooted and the kernel might make a difference in battery life and performance. Whether that is a positive or negative influence, I've no clue. The poster seemed to like it, and he would know better than I. So you just want to download the files needed and put them in the same folder where you have your adb files. Then for each one you want to use:
adb push
then
nameoffile.zip - where you fill in the name of file with whatever (you can rename the files - but not extensions - to be easier, ie recovery.zip, rom.zip)
then /sdcard/
Full command of pushing the rom to the internal storage, assuming you renamed it to rom.zip would be:
adb push rom.zip /sdcard/
This will take awhile. Probably a good 10 minutes.
After you get it transferred over, then install the recovery zip in your current recovery and then reboot to recovery again so you will be in the new Philz. Then do a factory reset and install the rom zip.
Click to expand...
Click to collapse
Which of those files should I download.
as I understand it, once downloaded and in the file with the ADB.
adb devices (to make sure it is connected)
then
adb push recovery.zip /sdcard/ (saying recovery if I rename the file, and pushing the recovery is first?)
then straight after do I push the rom, after rebooting the device, or push them both - reboot the device then install the rom from the recovery?
the first file is Open Euro D80220D.zip - this is the rom, right? and since it is .ZIP do I extract it to the folder where the ADB is or keep it as .zip to push it?
sorry, I'm really new to all this stuff and starting to regret rooting in the first place.
yoalphadied said:
Which of those files should I download.
as I understand it, once downloaded and in the file with the ADB.
adb devices (to make sure it is connected)
then
adb push recovery.zip /sdcard/ (saying recovery if I rename the file, and pushing the recovery is first?)
then straight after do I push the rom, after rebooting the device, or push them both - reboot the device then install the rom from the recovery?
the first file is Open Euro D80220D.zip - this is the rom, right? and since it is .ZIP do I extract it to the folder where the ADB is or keep it as .zip to push it?
sorry, I'm really new to all this stuff and starting to regret rooting in the first place.
Click to expand...
Click to collapse
Download the rom and the recovery. It's up to you about the SU zip and kernel.
Push both.
Install recovery zip then the reboot recovery (adb reboot recovery or via the settings in recovery itself)
Factory reset then install rom (yes, Open Euro.zip is the rom)
Install kernel and SU now if you want - wipe caches if you do then reboot
es0tericcha0s said:
Download the rom and the recovery. It's up to you about the SU zip and kernel.
Push both.
Install recovery zip then the reboot recovery (adb reboot recovery or via the settings in recovery itself)
Factory reset then install rom (yes, Open Euro.zip is the rom)
Install kernel and SU now if you want - wipe caches if you do then reboot
Click to expand...
Click to collapse
Okay, I just tried pushing the rom, the line entered, i got no return so far but it won't allow me to type anything else in the CMD, i'm guessing its because it's pushing the file?
es0tericcha0s said:
Download the rom and the recovery. It's up to you about the SU zip and kernel.
Push both.
Install recovery zip then the reboot recovery (adb reboot recovery or via the settings in recovery itself)
Factory reset then install rom (yes, Open Euro.zip is the rom)
Install kernel and SU now if you want - wipe caches if you do then reboot
Click to expand...
Click to collapse
The recovery is working fine, but after factory resetting, and then trying to install the rom.zip it tries to open it
then e: cant open /data/media/rom.zip
(bad)
installation aborted
es0tericcha0s said:
Download the rom and the recovery. It's up to you about the SU zip and kernel.
Push both.
Install recovery zip then the reboot recovery (adb reboot recovery or via the settings in recovery itself)
Factory reset then install rom (yes, Open Euro.zip is the rom)
Install kernel and SU now if you want - wipe caches if you do then reboot
Click to expand...
Click to collapse
I didn't actually check to see if i got any errors during the push, so i tried pushing again with a different name rommy.zip and got this error
cannot read 'rommy.zip' : input/output error
3583 KB/s <1372848128 bytes in 374.008s>
yoalphadied said:
I didn't actually check to see if i got any errors during the push, so i tried pushing again with a different name rommy.zip and got this error
cannot read 'rommy.zip' : input/output error
3583 KB/s <1372848128 bytes in 374.008s>
Click to expand...
Click to collapse
Are you trying to sideload it? This is different than pushing the file. You don't need to sideload it. Just plug it in and adb push the files you need to the /sdcard/. And are you trying to install it with Philz?
es0tericcha0s said:
Are you trying to sideload it? This is different than pushing the file. You don't need to sideload it. Just plug it in and adb push the files you need to the /sdcard/. And are you trying to install it with Philz?
Click to expand...
Click to collapse
After realising that the push hadnt completed properly, I redownloaded the file, and then pushed it - now it has got past where it had the error and is at 'installing KitKat 4.4.2 ROM
Thanks for your help, greatly appreciated.
What are the benefits of using the Kernal you mentioned earlier?
maybe everything isn't as clear cut as it seemed, after the ROM installed correctly it asked me to reboot now, so I did and now I'm back stuck on the LG splash screen.
Maybe the rom is the wrong one for my phone? It's an LG G2 16gb D802 UK on EE.
yoalphadied said:
After realising that the push hadnt completed properly, I redownloaded the file, and then pushed it - now it has got past where it had the error and is at 'installing KitKat 4.4.2 ROM
Thanks for your help, greatly appreciated.
What are the benefits of using the Kernal you mentioned earlier?
maybe everything isn't as clear cut as it seemed, after the ROM installed correctly it asked me to reboot now, so I did and now I'm back stuck on the LG splash screen.
Maybe the rom is the wrong one for my phone? It's an LG G2 16gb D802 UK on EE.
Click to expand...
Click to collapse
Ohhh I think that one might be for the 32 GB one. Sorry. *edit*
You can try this one: http://forum.xda-developers.com/showthread.php?t=2681205
es0tericcha0s said:
Ohhh I think that one might be for the 32 GB one. Sorry. *edit*
You can try this one: http://forum.xda-developers.com/showthread.php?t=2681205
Click to expand...
Click to collapse
Should i try installing the kernal? See if that works? As it does say in comments that the 1st works for 16 &32
*EDIT*
install Kernal & supersu doesn't resolve the issue, going to try the new rom you posted now
yoalphadied said:
Should i try installing the kernal? See if that works? As it does say in comments that the 1st works for 16 &32
Click to expand...
Click to collapse
That's what I would do. Won't make it worse. Might help. If not, it's only a few more minutes altogether to try. Just make sure to wipe cache and dalvik cache.
es0tericcha0s said:
Ohhh I think that one might be for the 32 GB one. Sorry. *edit*
You can try this one: http://forum.xda-developers.com/showthread.php?t=2681205
Click to expand...
Click to collapse
Okay, I came across another problem.
with the several versions of the same ROM at /sdcard/ my memory was running low, so i formatted it - then it wouldn't let me push anything to it, anyway i sorted that (can't remember how) and then installed the Kernal and superuser, which didn't seem to sort anything, but I did a little digging and mounted all the directories on Philz.
Then after I restarted the phone, whilst trying to get into recovery I heard the 'LG' splash screen animation noise. and then the phone loaded up the country setting - and then I got an error which made the screen unresponsive, I tried reloading to get yet another error, similar but not the same.
I booted into recovery, did a factory reset and again rebooted the phone and now it works, with the Knock Code! thank you so much you have saved my phone..
Is there anything I can do to say thank you properly, you've just saved me over £250
hi guys
I tried to install a custom rom on my HTC One X PLUS. I am new to this and it looks like i kinda screwed up. i used "HTC One X+ AIO Kit By Hasoon2000 v2.3". I have now this "CWM-based Recovery v6.0.2.7" on my phone. i can't boot the normal OS anymore. everytime i reboot, this cwm recovery shows up. when i try to install cyanogenmod (cm-11-20140705-NIGHTLY-enrc2b.zip) by "install zip from sdcard => choose zip from sdcard ==> ..." i just receive:
Code:
set_metadata_recursive: some changes failed
E:Error in /sdcard/0/cm-11-20140705-NIGHTLY-enrc2b.zip
(Status 7)
Installation aborted.
i have no idea what to do. can anyone pls help? is it still possible to reset everything to get my phone working again?
Flash the latest version, older ones can't flash kitkat ROMs
http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.4.8-enrc2b.img
Sent from my One X+ using Tapatalk
Phoenix09 said:
Flash the latest version, older ones can't flash kitkat ROMs
Click to expand...
Click to collapse
How can i do this? i can't put the file on my phone because my phone doesn't have a sd card.
Hutschi93 said:
How can i do this? i can't put the file on my phone because my phone doesn't have a sd card.
Click to expand...
Click to collapse
check this out http://forum.xda-developers.com/showthread.php?t=2066390 read it all, the part you need is adb sideloading, again, read it all at least a few times
leefear said:
check this out http://forum.xda-developers.com/showthread.php?t=2066390 read it all, the part you need is adb sideloading, again, read it all at least a few times
Click to expand...
Click to collapse
i already tried that, but all i get is this error:
Code:
* failed to write data 'protocol fault (no status)' *
my phone is in this "sideload mode" and i changed the filename into one word (that's what i should do if i get an error)
Hutschi93 said:
i already tried that, but all i get is this error:
Code:
* failed to write data 'protocol fault (no status)' *
my phone is in this "sideload mode" and i changed the filename into one word (that's what i should do if i get an error)
Click to expand...
Click to collapse
did you flash the recovery that phoenix suggested?
leefear said:
did you flash the recovery that phoenix suggested?
Click to expand...
Click to collapse
how? i just can open this cwm based recovery mode or this strangely HBOOT mode. but my computer doesn't really recognize it. if i open the device manager i see it under "ADB Interface" as "HTC Bootloader" but if use "adb devices" in command prompt my phone does not get recognized. the toolkit doesn't recongize it either.
OK guys i got my computer to recognize my phone in recovery mode. i can use adb push to transfer files to my phone. do i have to flash a new recovery or can a just put a new rom on my phone and try installing that?
EDIT:
OK GUYS! thanks to that i got my computer to recognize my phone i could flash the recovery phoenix suggested! and i finally could install my rom! thank you sooo much guys! you are my hero and made my day! i would give you a hug if i could but i guess nobody of you lives in switzerland
love you guys! (no homo)
Hutschi93 said:
OK guys i got my computer to recognize my phone in recovery mode. i can use adb push to transfer files to my phone. do i have to flash a new recovery or can a just put a new rom on my phone and try installing that?
EDIT:
OK GUYS! thanks to that i got my computer to recognize my phone i could flash the recovery phoenix suggested! and i finally could install my rom! thank you sooo much guys! you are my hero and made my day! i would give you a hug if i could but i guess nobody of you lives in switzerland
love you guys! (no homo)
Click to expand...
Click to collapse
glad u got it working bud!
Welcome everyone,
Last week I got second hand Asus Tf201. I was disappointed with the stock rom that was installed on it and I decided to do something with that. I have unlocked bootloader, unlocked root, installed twrp recovery and finally installed AndroWook rom. Then I made a full system backup with twrp. After all, I made a decision to install KatKiss. I have read that to do this I need newer recovery than I had before so I installed the newest version of twrp. Then the problem appeared. When I wanted to get into the recovery twrp asked me for password I had never set. I've read loads of many topic on many different forums about it but unfortunately I was unable to connect my Tf201 to PC because of the broken USB cabel. I have opened android terminal and changed the version of twrp to another but the problem didn't dissappear. By mistake I got into recovery and pushed the "wipe data" button, I even didn't know that it will erase all my data with OS from the device. Right now I'm stuck on twrp asking me for password, when I tap on cancel and get into the menu, then into "restore" it says that it's unable to mount external storage, on which I have my backup files. I bought a new USB cabel, PC sees it in adb, but actually I don't have the faintest idea what can I do more with it. I have already tried some different unbrick methods but some of them need nvflash installed, which I don't have. Could anyone please help me with my problem?
Jackobtone said:
Welcome everyone,
Last week I got second hand Asus Tf201. I was disappointed with the stock rom that was installed on it and I decided to do something with that. I have unlocked bootloader, unlocked root, installed twrp recovery and finally installed AndroWook rom. Then I made a full system backup with twrp. After all, I made a decision to install KatKiss. I have read that to do this I need newer recovery than I had before so I installed the newest version of twrp. Then the problem appeared. When I wanted to get into the recovery twrp asked me for password I had never set. I've read loads of many topic on many different forums about it but unfortunately I was unable to connect my Tf201 to PC because of the broken USB cabel. I have opened android terminal and changed the version of twrp to another but the problem didn't dissappear. By mistake I got into recovery and pushed the "wipe data" button, I even didn't know that it will erase all my data with OS from the device. Right now I'm stuck on twrp asking me for password, when I tap on cancel and get into the menu, then into "restore" it says that it's unable to mount external storage, on which I have my backup files. I bought a new USB cabel, PC sees it in adb, but actually I don't have the faintest idea what can I do more with it. I have already tried some different unbrick methods but some of them need nvflash installed, which I don't have. Could anyone please help me with my problem?
Click to expand...
Click to collapse
Give this command a try
Code:
adb reboot-bootloader
Does it boot to the bootloader screen ?
Thx Josh
bootloader tf201
lj50036 said:
Give this command a try
Code:
adb reboot-bootloader
Does it boot to the bootloader screen ?
Thx Josh
Click to expand...
Click to collapse
Yes it did!
okey, OS is installed, and what is more it works properly. Many Thanks to You!
Now I have a little problem. I can`t remove twrp recovery. I have installed rom manager and installed cwm recovery, but when i reboot tablet to recovery menu the twrp starts as it did before.. What now?
Update:
I did everything mentioned in this post http://forum.xda-developers.com/showthread.php?t=2459711&highlight=twrp+mount&page=4 and have restored my backup. All works fine now. Thanks again!
Jackobtone said:
Now I have a little problem. I can`t remove twrp recovery. I have installed rom manager and installed cwm recovery, but when i reboot tablet to recovery menu the twrp starts as it did before.. What now?
Update:
I did everything mentioned in this post http://forum.xda-developers.com/showthread.php?t=2459711&highlight=twrp+mount&page=4 and have restored my backup. All works fine now. Thanks again!
Click to expand...
Click to collapse
Great to see you up and running ...... :good:
Can you add 'SOLVED' to the thread tittle ....
Thx Josh
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