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.
Related
Hey all,
I installed CWM and loaded CM9 on my TF201.
I decided I wanted to try Androwook 2.1 as I really need usb disk support.
I followed the instructions on the page and flashed TWRP recovery (successfully).
I went into TWRP and backed up all my data.
I wiped EVERYTHING & then I tried to install Androwook (5 times) with the stable motley kernel.
After finishing in Aroma it's failing with the following:
-checking model id
assert failed: getprop("ro.product.device") == "tf201"
Any idea how to get past this point? - Thanks in advance!
could be a corrupt download, redownload the rom push it with adb and try it again see if maybe that works
also make sure your on the latest twrp or the one before it think it was 2.1.3?, its either the rom or the recovery bugging out i think
msfguard said:
could be a corrupt download, redownload the rom push it with adb and try it again see if maybe that works
Click to expand...
Click to collapse
That's what I thought too so I downloaded again from the direct server link (on attempt 3). I didn't try to push it with ADB though...
Brb - testing :fingers-crossed:
Amadei said:
That's what I thought too so I downloaded again from the direct server link (on attempt 3). I didn't try to push it with ADB though...
Brb - testing :fingers-crossed:
Click to expand...
Click to collapse
yep normaly a
adb push romname.zip /sdcard
will do the trick with twrp, think CWM needs something else but i been twrp since it came out
msfguard said:
yep normaly a
adb push romname.zip /sdcard
will do the trick with twrp, think CWM needs something else but i been twrp since it came out
Click to expand...
Click to collapse
Well i went into the build.prop and the ro.product.device is pointing to eeepad and not tf201
Couldn't i just change that to tf201 so it'll install?
Amadei said:
Well i went into the build.prop and the ro.product.device is pointing to eeepad and not tf201
Couldn't i just change that to tf201 so it'll install?
Click to expand...
Click to collapse
Not to sure, i think its your recovery though, what version are you running and from where?
just flash this in recovery
twrp 2.2
http://flumpster.lolcakes.com/android/twrp2.2.0.zip
thanks fumpster for the linky
msfguard said:
Not to sure, i think its your recovery though, what version are you running and from where?
just flash this in recovery
twrp 2.2
http://flumpster.lolcakes.com/android/twrp2.2.0.zip
thanks fumpster for the linky
Click to expand...
Click to collapse
And it's installing after getting 2.2... Thanks for your time and help! much appreciated!
Amadei said:
And it's installing after getting 2.2... Thanks for your time and help! much appreciated!
Click to expand...
Click to collapse
So can I flash that if I have CWM? I can't get anything to work. ADB not working cuz drivers aren't working. universal naked drivers won't work.
And of course in CWM it doesn't see the sdcard...so am I screwed or missing something?
I started by the directions and using goo manager cuz I didn't want to mess w adb while I was at work, and now I'm stuck in CWM and can't get a damn thing to work.
willowave said:
So can I flash that if I have CWM? I can't get anything to work. ADB not working cuz drivers aren't working. universal naked drivers won't work.
And of course in CWM it doesn't see the sdcard...so am I screwed or missing something?
I started by the directions and using goo manager cuz I didn't want to mess w adb while I was at work, and now I'm stuck in CWM and can't get a damn thing to work.
Click to expand...
Click to collapse
You have to get ADB working, then you can start in fastboot and flash TWRP . power + vol down and use vol. to choose the one in the mittle of the screen, usb icon.
You can also push a rom to the sdcard when you are in recovery mode. = power + vol down and vol up
I used this cmd : adb push "romname" /data/media/ to push the rom.
Then Cwm could se the rom.
Cmd: Adb push "romname" /sdcard didn't work for me. Cwm couldn't se the internal sdcard.
If it continues to boot loop, then startup in fastboot menu and wipe it from there. It's the one to the left.
Wipe from recovery menu didn't work for me. Fastboot menu wipe did.
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)
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
Hello everyone. I started this thread because I don't think I've seen anything with this issue on my specific phone on this forum. Apologies if this has been discussed before.
Anyway, I'm having issues installing a ROM with adb sideload on TWRP recovery.
I got the ROM and the recovery image from blox2.com (I would post the links but apparently the forum doesn't allow me to...)
Everything works fine, I'm able to boot into TWRP recovery and inititiate the adb sideload, but the process gets stuck when it reaches 28% and throws the error message:
serving: 'BLOX2core-v1.1.1-31217.zip' (~28%) * failed to read command: Success
Click to expand...
Click to collapse
In case this has anything to do with ADB version, I'm using Debian and my adb version is 1:7.0.0+r1-4
If you need any more info, please ask.
Thanks in advance.
Ok, an update.
I now tried installing the ROM through TWRP's own installing option, but TWRP crashes and reboots a couple of seconds after the install is initiated.
max_157 said:
Ok, an update.
I now tried installing the ROM through TWRP's own installing option, but TWRP crashes and reboots a couple of seconds after the install is initiated.
Click to expand...
Click to collapse
Make sure you have MTP turned off. Also DM verity and force encryption needs to be disabled
ieatgravity said:
Make sure you have MTP turned off. Also DM verity and force encryption needs to be disabled
Click to expand...
Click to collapse
How do I disable MTP? I can't get android to boot. Can you disable it from TWRP or is it done from a fastboot/adb command?
I figured it out. I disabled MTP from the mount menu and disabled DM-Verify and encryption from the Advanced menu... same results
max_157 said:
How do I disable MTP? I can't get android to boot. Can you disable it from TWRP or is it done from a fastboot/adb command?
Click to expand...
Click to collapse
Flash supersu then flash the ROM
ieatgravity said:
Flash supersu then flash the ROM
Click to expand...
Click to collapse
OK. I tried
1. Booting into TWRP
2. Selected Install
3. Selected UPDATE-SuperSU-v2.65-20151226141550.zip
It crashed after a couple of seconds.
Tried with MTP disabled and DM-verity and encryption disabled.
max_157 said:
OK. I tried
1. Booting into TWRP
2. Selected Install
3. Selected UPDATE-SuperSU-v2.65-20151226141550.zip
It crashed after a couple of seconds.
Tried with MTP disabled and DM-verity and encryption disabled.
Click to expand...
Click to collapse
I'm would assume the bootloader was unlocked? Are you able to make a nandroid backup? And have you tried flashing twrp to the phone ?
Where do you have the files located at? Is it on the SDcard or on the flash drive?
does this work?
fastboot oem unlock
or
fastboot flashing unlock
Should also erase/wipe everything except system/recovery/boot...
Also hope you made a nandroid backup first with the fastboot boot recovery.img, then booting into TWRP and backup. to flash drive. Need MTP disabled for some to not reboot.
Also try with the new TWRP where the reboot has been fixed.. and which version 16/2 or 64/4 BLU X2 or mini?
ieatgravity said:
I'm would assume the bootloader was unlocked? Are you able to make a nandroid backup? And have you tried flashing twrp to the phone ?
Click to expand...
Click to collapse
The bootloader was indeed unlocked.
I haven't tried flashing TWRP to the phone. Would this make it work? I'm kind of scared of having a recovery image that crashes whenever I try stuff. Can I restore the stock recovery in case anything happens?
AlienTeck said:
Where do you have the files located at? Is it on the SDcard or on the flash
drive?
Click to expand...
Click to collapse
Internal flash drive.
AlienTeck said:
does this work?
fastboot oem unlock
or
fastboot flashing unlock
Click to expand...
Click to collapse
Yup! It works. It says it's already unlocked.
AlienTeck said:
Should also erase/wipe everything except system/recovery/boot...
Also hope you made a nandroid backup first with the fastboot boot recovery.img, then booting into TWRP and backup. to flash drive. Need MTP disabled for some to not reboot.
Click to expand...
Click to collapse
I did wipe cache and everything else, and had MTP disabled.
AlienTeck said:
Also try with the new TWRP where the reboot has been fixed.. and which version 16/2 or 64/4 BLU X2 or mini?
Click to expand...
Click to collapse
64/4 BLU X2 version.
I can't find BLU Life One X2 on the official TWRP website, the only version I tried was on blox2.com, which I think is a modified version of 3.0.2-0.
Problem fixed!
I flashed the stock firmware using QFIL 1.0.2. Thanks so much to everyone who helped!
QFIL
I got the QFIL rom from blox2.com
When you say fixed, do you mean TWRP is now working? Or that you were able to flash the stock back? Did you already take the BLOX2 OTA update?
Trying to figure out if the update had anything to do with this default rebooting on /system being made writable.. Also did you make a nandroid backup?
QFIL is now on 1.0.0.3
AlienTeck said:
When you say fixed, do you mean TWRP is now working? Or that you were able to flash the stock back? Did you already take the BLOX2 OTA update?
Trying to figure out if the update had anything to do with this default rebooting on /system being made writable.. Also did you make a nandroid backup?
QFIL is now on 1.0.0.3
Click to expand...
Click to collapse
I was able to flash the stock back, but via QFIL, not TWRP. The rebooting issue still persists.
I didn't make a nandroip backup, will get to it now.
Oh, I'm actually now trying to fix the rebooting issue. I think it might be a write protection, like the one HTC has. Example: https://www.youtube.com/watch?v=KV3YaMBnEYI
I really really need to be able to modify the system partition because the phone comes with a lot of crawpare and even some malware (https://www.cyberscoop.com/android-malware-china-huawei-zte-kryptowire-blu-products/)
FotaProvider installs some apps without your consent like Uber and some games and supposedly sends some info, too.
When I try to remove it with root uninstallers, the phone reboots. I though I had gotten rid of this issue by reflashing the ROM but apparently not...
I only flashed TWRP to cache and booted to it and flashed super SU, then used root essentials to remove some of the bloatware. But noticed supersu was gone now. It was able to remove or disable some of the stuff without rebooting and then later manually rebooting it. I disabled the apps and then removed it, so I think even the update now has the stuff but still disabled. The update also supposedly removes one of the apps that sent data back.
It rebooted at first until I saw that I had to disable MTP in TWRP options. I have not tried the recent TWRP, I was still using the one under development in the beginning.
AlienTeck said:
I only flashed TWRP to cache and booted to it and flashed super SU, then used root essentials to remove some of the bloatware. But noticed supersu was gone now. It was able to remove or disable some of the stuff without rebooting and then later manually rebooting it. I disabled the apps and then removed it, so I think even the update now has the stuff but still disabled. The update also supposedly removes one of the apps that sent data back.
It rebooted at first until I saw that I had to disable MTP in TWRP options. I have not tried the recent TWRP, I was still using the one under development in the beginning.
Click to expand...
Click to collapse
How do I install this update?
Also, I tried removing some system apps with Root Essentials but it still rebooted.
max_157 said:
How do I install this update?
Also, I tried removing some system apps with Root Essentials but it still rebooted.
Click to expand...
Click to collapse
For the time being you need to boot into TWRP and manually remove apps using ADB. We are currently working on patching the kernel to allow /system to be mounted RW sAo that you can use apps to remove system apps. In the mean time use Blox2core as it has been fully debloated.
ieatgravity said:
For the time being you need to boot into TWRP and manually remove apps using ADB. We are currently working on patching the kernel to allow /system to be mounted RW sAo that you can use apps to remove system apps. In the mean time use Blox2core as it has been fully debloated.
Click to expand...
Click to collapse
Sounds great! Looking forward to it.
I can't install Blox2core since TWRP reboots when I try to install it or even wipe the /system partition though. Some people mentioned TWRP 3.0.3 fixed this issue.
max_157 said:
Sounds great! Looking forward to it.
I can't install Blox2core since TWRP reboots when I try to install it or even wipe the /system partition though. Some people mentioned TWRP 3.0.3 fixed this issue.
Click to expand...
Click to collapse
We have a new tool that you can use to flash TWRP and root. All auto matic. Give it a try and let me know if it works for you.
[TOOL]Draco’s Blox2Autoroot - http://wp.me/p8gYUZ-5x
Afterwards you'll be able to flash Blox2core
Also I was unaware of this TWRP 3.0.3 for the blox2. The only one that has been ported has been 3.0.2 last I checked.
I would say disable MTP in TWRP options and developer options as well. dirst disabled it in developer options before I found out that did not stop the kernel rebooting the phone when /system became writable. I had not installed the oct update BLU sent out and maybe that makes a difference? Although the QFIL should also have the original boot/kernal image? so not sure what is going on..
If that dont stop it we need a new kernal.. I think I have the original kernal/boot saved. If anyone wants to see if that fixed the reboot.
twrp gave a MD5 of it..
152479bd51790d374885cc1a847e4c31 boot.emmc.win
Seems I need a faster course in android.. A few months ago I thought an android was some guy in dr who.
---------- Post added at 12:08 PM ---------- Previous post was at 11:46 AM ----------
The OTA update showed up one day and it installed it.. For the longest time I ignored it but I suppose someone hit ok on it.. But SuperSU seemed to have vanished before that I think. Spending time on 2 other problem phones so this one is not a priority since it works very well comparatively. I love it though it is heavy as a brick. Even my N5x case fits with a little coaxing. Although the DPI setting is set much higher like for a HD screen and not FHD. Maybe we can change it in build.prop to fix it. The N5x has much smaller icons and letters and actually fit 5 icons to a row although they both have the same density screen.. BLU has much better touch though and is far brighter and richer.
---------- Post added at 12:30 PM ---------- Previous post was at 12:08 PM ----------
The 2 boot images ARE different.. But you should first try to write a backup back to itself and see if there are problems and guess I dont have the previlage of attaching files just yet on here.
max_157 said:
Problem fixed!
I flashed the stock firmware using QFIL 1.0.2. Thanks so much to everyone who helped!
I got the QFIL rom from blox2.com
Click to expand...
Click to collapse
Could you share the link to the stock ROM you used with QFIL?
Thanks!
As you know, TWRP still doesn't support FBE, so in-case if you wanna flash another system.img the Wipe data/factory reset in TWRP wouldn't work (at least didn't work for me).
That would force you to get back to stock recovery, which allows a successful factory reset.
Steps are pretty straight forward, if you already have a backup of your stock recovery just do the below steps, if else you could download one from the below link.
Put the device into fastboot mode. There are two ways to do that.
1)By long pressing the power button and volume down button whilst the USB is connected.
2)Just do a adb reboot bootloader command if you could boot into the system.
Then just do
Code:
fastboot flash recovery_ramdisk recovery_ramdisk.img
Then disconnect the USB and long press the power and volume up button until you see the "The device is booting now" message.
Downloads
- Stock recovery for BKL-L09
Thanks, you saved me.
Thanks
Just created a md5sum of your recovery and my backed up recovery. It's exactly the same size but the md5sum is different.
A quick look with a hex editor also shows some big differences. Is that expected?
Copperhead100 said:
Just created a md5sum of your recovery and my backed up recovery. It's exactly the same size but the md5sum is different.
A quick look with a hex editor also shows some big differences. Is that expected?
Click to expand...
Click to collapse
MD5 hash wouldn't possibly match, because the backup was taken using dd and there might be some config files modified or added when I used the stock recovery once. But, hey the thing would work if you have BKL-L09 device
Thanks. This works!
shihabsoft said:
As you know, TWRP still doesn't support FBE, so in-case if you wanna flash another system.img the Wipe data/factory reset in TWRP wouldn't work (at least didn't work for me).
That would force you to get back to stock recovery, which allows a successful factory reset.
Click to expand...
Click to collapse
Mate, will this stock recovery work in Indian model(BKL-L09-C675)?
atf2m4 said:
Mate, will this stock recovery work in Indian model(BKL-L09-C675)?
Click to expand...
Click to collapse
Ofc it does
shihabsoft said:
Ofc it does
Click to expand...
Click to collapse
Mate, after restoring this recovery, will I be able to receive system update for the device. I have rooted with Magisk and twrp is installed. what to do to receive system update automatically?. please give detailed steps. Thank you.
atf2m4 said:
Mate, after restoring this recovery, will I be able to receive system update for the device. I have rooted with Magisk and twrp is installed. what to do to receive system update automatically?. please give detailed steps. Thank you.
Click to expand...
Click to collapse
Not sure, as it might check integrity before giving updates. Just download Firmware Finder app and check for updates constantly.
atf2m4 said:
Mate, after restoring this recovery, will I be able to receive system update for the device. I have rooted with Magisk and twrp is installed. what to do to receive system update automatically?. please give detailed steps. Thank you.
Click to expand...
Click to collapse
You will receive the updates but you won't be able to install them with TWRP. Simply flash the stock recovery and the updates will self install when they come. You'll have to root again with Magisk after the updates, but that's a simple process.
Sent from my Honor View 10 using XDA Labs
Hie,
How can I get back from lineage OS to stock using this? I guess I'm on the same boat as a lot of people out there and could really use some help here. I'm on Cosmos OS and can't go back to stock. I tried flashing this recovery.img but can't figure out a way back.
Reboot to bootloader, flash system recovery_ramdisk and ramdisk. Reboot to recovery wipe cache, reboot system enjoy.
Works every time fine for me
Powered by View 10
2WildFirE said:
Reboot to bootloader, flash system recovery_ramdisk and ramdisk. Reboot to recovery wipe cache, reboot system enjoy.
Works every time fine for me
Powered by View 10
Click to expand...
Click to collapse
Can you help me with the commands please?
---------- Post added at 09:20 PM ---------- Previous post was at 09:12 PM ----------
2WildFirE said:
Reboot to bootloader, flash system recovery_ramdisk and ramdisk. Reboot to recovery wipe cache, reboot system enjoy.
Works every time fine for me
Powered by View 10
Click to expand...
Click to collapse
Wildfire, can you please help me with the commands? I believe there's an inclusion of ramdisk in the commands now.
---------- Post added at 09:52 PM ---------- Previous post was at 09:20 PM ----------
2WildFirE said:
Reboot to bootloader, flash system recovery_ramdisk and ramdisk. Reboot to recovery wipe cache, reboot system enjoys.
Works every time fine for me
Powered by View 10
Click to expand...
Click to collapse
Apparently, there isn't any system.img file in the Indian firmware I downloaded. The rest are there but not the system.img.
Someone please help me out
I can't flash system.img as I was told in an earlier reply, it returns me an error that says 'Error: Cannot load System.':crying: I tried using -P and 256M commands to see the space divided and none of these worked either. CAN SOME PLEASE HELP ME OUT WITH THIS?
I cannot find system.img in the Indian firmware either, that is making things tough for me.
ankan1993 said:
I can't flash system.img as I was told in an earlier reply, it returns me an error that says 'Error: Cannot load System.':crying: I tried using -P and 256M commands to see the space divided and none of these worked either. CAN SOME PLEASE HELP ME OUT WITH THIS?
I cannot find system.img in the Indian firmware either, that is making things tough for me.
Click to expand...
Click to collapse
You should have made a backup before you started "tinkering" with your device. Lesson learned, hopefully.
Sent from my Honor View 10 using XDA Labs
Einwod said:
You should have made a backup before you started "tinkering" with your device. Lesson learned, hopefully.
Sent from my Honor View 10 using XDA Labs
Click to expand...
Click to collapse
Indeed! Can you please help me this one time?
ankan1993 said:
Indeed! Can you please help me this one time?
Click to expand...
Click to collapse
I cannot help you as I do not have your firmware or know anything about the Indian version. Where did you get this firmware from?
Einwod said:
I cannot help you as I do not have your firmware or know anything about the Indian version. Where did you get this firmware from?
Click to expand...
Click to collapse
I downloaded this from https://www.getdroidtips.com/huawei-honor-view-10-b160-oreo-firmware/#Downloads.
ankan1993 said:
I downloaded this from https://www.getdroidtips.com/huawei-honor-view-10-b160-oreo-firmware/#Downloads.
Click to expand...
Click to collapse
What device do you have exactly?