I got the notification to install and I tried. Shield restarted and the little green android guy showed up and it started installing the update. Half way through it showed a red explanation mark with the words "error". I had to hold down the shield+home keys to restart. The shield restarted just fine. I deleted the data in google frameworks (read to do that here) and tried the update again, same outcome.
I'm new to android (came from iphone) and now have a galaxy S4. So I apologize about the noobiness.
My shield is rooted and bootloader unlocked. As far as I know I did not install any custom recovery. I thought that users should be able to install OTA if they are running the stock OS and no custom recoveries. Am I wrong about that? Anyways, I have SuperSU installed along with a few rooted apps. My guess is that I will need to install a custom recovery so I can flash this update, is this correct? I would be very grateful if someone would explain whats going on here =P
You should not need a custom recovery for this.
Due to the download size of this update it appears to be an incremental update.
the download size i see is 22.3 MB
You would need to see the exact error to try an figure out more.
UPDATE
Installed fine for me
Custom recovery is definitely not needed. Root by itself also does not interfere. I updated without trouble.
Maybe try reflashing the boot and system partitions to stock and try the update again?
Gnurou said:
Custom recovery is definitely not needed. Root by itself also does not interfere. I updated without trouble.
Maybe try reflashing the boot and system partitions to stock and try the update again?
Click to expand...
Click to collapse
a quick how to on reflashing the boot and system would be awesome!!
--edit:nevermind... im trying out Kwonggers program--
ok somehow i softbricked my shield. I've tried Kwonggers program and I've manually flashed recovery,boot, and system and afterwards all I get is the flashing green controller during boot. I know I did it right because all messages were positive.
I also downloaded the most up to date shield files from nvidia (update64) which is extract-nv-recovery-image-shield-01.00.13216_261.5912.sh however I dont know how to use a *sh file.
Rhokk said:
a quick how to on reflashing the boot and system would be awesome!!
--edit:nevermind... im trying out Kwonggers program--
ok somehow i softbricked my shield. I've tried Kwonggers program and I've manually flashed recovery,boot, and system and afterwards all I get is the flashing green controller during boot. I know I did it right because all messages were positive.
I also downloaded the most up to date shield files from nvidia (update64) which is extract-nv-recovery-image-shield-01.00.13216_261.5912.sh however I dont know how to use a *sh file.
Click to expand...
Click to collapse
it needs a factory rest.
my suggestion is to re-flash system (again) using the command fastboot -w flash system system.img
the .sh file is for use on Linux, cygwin can probably do that if you have the correct things installed with it.
chevyowner said:
it needs a factory rest.
my suggestion is to re-flash system (again) using the command fastboot -w flash system system.img
the .sh file is for use on Linux, cygwin can probably do that if you have the correct things installed with it.
Click to expand...
Click to collapse
Chevyowner you are the best! After reading your suggestion, I tried just the system.img this time and presto! This time it took. Not sure why it didn't take the 2 times I tried it last night.
Thanks for helping newer guys like me. Really appreciate it!
Rhokk said:
Chevyowner you are the best! After reading your suggestion, I tried just the system.img this time and presto! This time it took. Not sure why it didn't take the 2 times I tried it last night.
Thanks for helping newer guys like me. Really appreciate it!
Click to expand...
Click to collapse
glad you got it working
chevyowner said:
glad you got it working
Click to expand...
Click to collapse
hi.
i am a new guy from far far away China, language is the biggist problem.
the same issue, i can't fix it, error in updating ota 65.
re-flash system (again) using the command fastboot -w flash system system.img
Click to expand...
Click to collapse
how to do? where i can get /system.img/? and how to push the img to my Shield?
except a PC and a cable, i don't have any tools, no software. and i can't get that what you guys talking about. but the same issue.
if you guys can help, i will be very appreciated
if u do know Chinese.....=P
Hi, I have the same issue, OTA 64 installed with bootloader unlocked and rooted. Will my data be preserved if I flash only the system image?
Nikojiro said:
Hi, I have the same issue, OTA 64 installed with bootloader unlocked and rooted. Will my data be preserved if I flash only the system image?
Click to expand...
Click to collapse
how can you get the /system image/? thanks
starfriend.y said:
how can you get the /system image/? thanks
Click to expand...
Click to collapse
Here's how I fixed my system:
Downloaded OTA 65 image from https://developer.nvidia.com/develop4shield
As per instructions (see https://developer.nvidia.com/sites/default/files/akamai/mobile/shield/HowTo-Flash-Recovery-Image_1.txt), flashed only boot, recovery and system images (so it wouldn't wipe your user partition, e.g. apps and data)
Rebooted the unit, waited for the upgrade to complete. Root will be lost if you had it.
Rerooted the unit (see https://github.com/linux-shield/shield-root)
It works perfectly now.
Nikojiro said:
Here's how I fixed my system:
Downloaded OTA 65 image from https://developer.nvidia.com/develop4shield
As per instructions (see https://developer.nvidia.com/sites/default/files/akamai/mobile/shield/HowTo-Flash-Recovery-Image_1.txt), flashed only boot, recovery and system images (so it wouldn't wipe your user partition, e.g. apps and data)
Rebooted the unit, waited for the upgrade to complete. Root will be lost if you had it.
Rerooted the unit (see https://github.com/linux-shield/shield-root)
It works perfectly now.
Click to expand...
Click to collapse
thanks for your help.
is that /ota 65 image/ a 1.0GB .sh file? i can't unzip it.
i think that i have to unzip the .sh file with a linux pc.
starfriend.y said:
thanks for your help.
is that /ota 65 image/ a 1.0GB .sh file? i can't unzip it.
i think that i have to unzip the .sh file with a linux pc.
Click to expand...
Click to collapse
Yes the .sh file is a linux shell script. I can repack it in a standard zip and upload it later today on a share if you want.
Sent from my GT-I9100 using Tapatalk
Ok I uploaded a repacked zip of the OTA 65 images for linux-less people
https://mega.co.nz/#!ccRCQTAS!FylQx29ZE7RUvi-kzbwb53woZGRZUu9_RAQNk9_FkMI
Please note that you'll need to have the Android SDK installed, as well as the proper USB driver.
Nikojiro said:
Ok I uploaded a repacked zip of the OTA 65 images for linux-less people
https://mega.co.nz/#!ccRCQTAS!FylQx29ZE7RUvi-kzbwb53woZGRZUu9_RAQNk9_FkMI
Please note that you'll need to have the Android SDK installed, as well as the proper USB driver.
Click to expand...
Click to collapse
thanks a lot! you are so kind!
Nikojiro said:
Ok I uploaded a repacked zip of the OTA 65 images for linux-less people
https://mega.co.nz/#!ccRCQTAS!FylQx29ZE7RUvi-kzbwb53woZGRZUu9_RAQNk9_FkMI
Please note that you'll need to have the Android SDK installed, as well as the proper USB driver.
Click to expand...
Click to collapse
here i come again...
as your guide, i've flash my Shield /recovery.img/ and /boot.img/, they all done. but failed when i flash /system.img/, "FAILED (remote: insufficient memory)"
why?
starfriend.y said:
here i come again...
as your guide, i've flash my Shield /recovery.img/ and /boot.img/, they all done. but failed when i flash /system.img/, "FAILED (remote: insufficient memory)"
why?
Click to expand...
Click to collapse
Hi, sorry with so little background information I'm afraid I can't help. I'd recommend a full reflash of your unit.
Sent from my GT-I9100 using Tapatalk
Nikojiro said:
Hi, sorry with so little background information I'm afraid I can't help. I'd recommend a full reflash of your unit.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
thank you first.
I do as you said, download the file, unzip it, and i got /system.img/, /boot.img/ and /recovery.img/.
i opened cmd and type /fastboot flash system system.img/ and i got failed information: /FAILED (remote: insufficient memory)/
im sure i wipe my shield first, and i flash recovery, boot very well.
can't update
hello,
I would very much appreciate some real help.
I want to be able to update to 65 WITHOUT loosing my userdata. I very much care for all my settings, software and setup.
I am bootloader unlocked from the very beginning and rooted. I was able to update OTA just fine until this update, and the root back very easily each time afterwards.
I knew that this ($#@@ing) delta update will give me trouble so I made some research first. With no use... I still couldn't update..
What I did:
-> downloaded custom CMW for shield and booted. made a nandroid (again: I very much care for my data and I won't update until and can do it without wiping) - all fine
-> downloaded the extracted image of OTA 65 from this thread, booted into boot loader and did:
fastboot flash recovery recovery.img
- OK
fastboot flash boot boot.img
- OK
fastboot flash system system.img
- insufficient memory crap.. (hoped I won't get it but... (( )
-> booted back into JB.. booted fine but my SD card storage partition wasn't where file managers read it anymore (it was mounted and OK on /system/storage but just lost some symlink of some sort... no big deal.. I guess it was the new bootloader at fault but since the 65 system image wasn't flashed I guessed it will work again afterwards..)
-> opened supersu, full unrooted, took a leap of fate and tried the delta update OTA... gave me the killed andoid at about 50% (
-> tried fastboot flash system system.img on another computer.. insufficient memory crap again....
-> so I booted again into CMW and restored my nandroid. Luckily everything worked fine...
So if someone knows how can I go 65 without userdata wipe, please help me!
thank you very much
Same problem here
Surprise, surprise! .... =(
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
//cc @Nikojiro
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You are looking for a special modded Clockworkmod recovery?
Clockworkmod Recovery v4.0.0.5
removed downloadlinks cause of issues with the new unity kernel.
please use this very special recovery
Just have a look on this site: 4EXTRecovery v1.1.1 | STAY @EXT4 | Convert EXT4 without losing data | Advanced Backup
Clockworkmod Recovery v3.2.0.0
downloadlink:
PG88IMG-RECOVERYIMG-3.2.0.0.zip
Clockworkmod Recovery v3.1.0.1
downloadlink:
PG88IMG-RECOVERYIMG-3.1.0.1.zip
or visit my blog dev page: lbc mod android development - custom recovery
Install Instructions:
download the zip package
rename it to PG88IMG.zip
put that file on the root of your sd card
start you phone in bootloader (hboot not fastboot)
the bootloader will ask you if you want to install recovery.img
confrim
reboot
rename the file again into something else (cause bootloader will always try to flash if a PG88IMG.zip file is on your sd card
loveboatcaptain said:
Hey Guys,
just have the first booting version of ClockworkMod Recovery v.3.0.2.4 on my phone.
View attachment 575564
a full working beta will come in the next days.
Install instructions will follow, too.
CREDITS: this is basicly the work of HCDR.Jacob how helped my to build this, cause my macbook sucked at building from source. so give him a big tanks too ;-)
see you later with a download for everyone with s-off
regards
Click to expand...
Click to collapse
woohoo
you are great
Ah mr mac user succeeded gratz
Sent from my HTC Incredible S using XDA Premium App
Hawkysoft said:
Ah mr mac user succeeded gratz
Click to expand...
Click to collapse
Yeah, with a little help from my friends ;-)
Jacob is fixing the last bugs and than i think were done and can do some tests before release.
regards
Maybe ours work for you to, koush made ours public today. Ill give u the info tomorrow, should be all the same
Sent from my HTC Incredible S using XDA Premium App
the beta tests have finished...
we talked to koush and he put it into ROM MANAGER just in this minute...
so happy flashing for all with s-off and root.
regards
p.s. don´t forget to thank HCDR.Jacob. He build it together and fixed the bugs and of course koush for pushing it so quick to ROM MANAGER.
thx to this great community
loveboatcaptain said:
Hey Guys,
[ROMmanager]
regards
Click to expand...
Click to collapse
Cool - working, thanks!
running backup now - so let the de-sense begin - I always brake some things when playing around to strip sense, so great to have full backup...
dont know said:
Cool - working, thanks!
running backup now - so let the de-sense begin - I always brake some things when playing around to strip sense, so great to have full backup...
Click to expand...
Click to collapse
feel free to test my first rom ;-)
this would be easier to "de-sense" cause it´s allready deodexed. so you needn´t delete so much stuff ;-)
a light version will follow the nexts days, which will be "de-sensed" and have a custom launcher like ADW or LP
regards
loveboatcaptain said:
feel free to test my first rom ;-)
this would be easier to "de-sense" cause it´s allready deodexed. so you needn´t delete so much stuff ;-)
a light version will follow the nexts days, which will be "de-sensed" and have a custom launcher like ADW or LP
regards
Click to expand...
Click to collapse
It's a very light desense I want (only get rid of the ad-ware inkluded and some others like twitter..)
I'm on ADW because of the cool themes available.
THANKS for the possibility of real rooting (unsecure and clockwork) again..
Hi, how can I root my desire s save
Sent from my Desire S using XDA Premium App
M0ng0 said:
Hi, how can I root my desire s save
Sent from my Desire S using XDA Premium App
Click to expand...
Click to collapse
Hey, today i unlocked mine with an xtc clip.
Then I flashed the unsecured Boot Image. I hope it is called so .
After that worked successful, i rooted it with SuperOneKlick.
Maybe this works for you too.
Any chance you can get in touch with the developer of this as there seems to be a very annoying bug.
Everytime i include:
format CACHE or
format("ext4", "EMMC", "/dev/block/mmcblk0p27", "/cache");
the recovery will not flash the ZIP. It will always give a STATUS 1 error.
So i have to manually format cache and run my ZIPS.
Thanks.
anybody successfully tried to revert on stock recovery?
fastboot says "FAILED (remote: not allowed)", and with cwm recovery it's impossible to try new OTA...
MarylandCookie said:
Any chance you can get in touch with the developer of this as there seems to be a very annoying bug.
Everytime i include:
format CACHE or
format("ext4", "EMMC", "/dev/block/mmcblk0p27", "/cache");
the recovery will not flash the ZIP. It will always give a STATUS 1 error.
So i have to manually format cache and run my ZIPS.
Thanks.
Click to expand...
Click to collapse
hey dude,
i ported the recovery together with a friend. so i´m your man ;-)
i never noticed that there is a problem with formating cache partition, cause i don´t touch it with my updater-script.
so first question:
why you will add that to your updater-script? me for myself prefere the way of wiping my phone manually. and that works very well with CMR. i also tested it in the mount/partition menu.
i would not like it, when a script wipes stuff and i did not know about.
i only use format for system in my full update.zip´s. in updates for my rom i did not wipe anything.
second question: did you know that cache partition is always mounted when recovery starts? perhaps thats the problem.
regards
mih_ said:
anybody successfully tried to revert on stock recovery?
fastboot says "FAILED (remote: not allowed)", and with cwm recovery it's impossible to try new OTA...
Click to expand...
Click to collapse
those fastboot commands only works with an ENG S-Off bootloader. which we dont have. we have SHIP S-Off... there are differences between those both.
our bootloader can everything the ENG can with fastboot commands. we have to use a zip file to flash things like recovery or splash.
you have to add your recovery backup img into my PG88IMG-unsecured_bootimg.zip file from this post [BOOT] Root for S-Off with unsecured Boot Image rename it to PG88IMG.zip and add your recovery.img into that zip file and remove the boot.img file.
than put the file on the root of your sdcard and reboot into bootloader.
the file will be flashed automaticly.
after reboot your phone, rename the file again to something else, cause every time you are in bootloader and this file is named PG88IMG.zip on your sdcard thhe bootloader will try to flash it.
just a little tipp at the end: you can add every img file into this zip. system and data img files from nandroid backups are working too ;-)
regards
Thank you!
I'll try it next time, i'll need it
But i've managed to flash it through flash_image from this link:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#HBOOT_partition_map
with recover.img from OTA downloaded.
After OTA i've lost the root, but gingerbreak still works...
mih_ said:
Thank you!
I'll try it next time, i'll need it
But i've managed to flash it through flash_image from this link:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#HBOOT_partition_map
with recover.img from OTA downloaded.
After OTA i've lost the root, but gingerbreak still works...
Click to expand...
Click to collapse
Could you PLEASE give me a short (or long ) description how to install the ota?
No idea what to do with the linked code...
EDIT Extracted the boot.img from ota and copoed it to PG88IMG.zip - restart - run ota-update -> fail
EDIT2 I'm an idiot: instead of boot.img it is a great idea to try it with recovery.img *LOL*
You just have to replace clockworkmod ecovery with stock one.
I've taken it from OTA downloaded.
It contains file firmware.zip inside, which contains recovery.img as well.
You can flash it with tool flash_image (http://www.thinkthinkdo.com/trac/project1/raw-attachment/wiki/vision_utilities/flash_image.zip)
Just put it somewhere to device, where you can run it (for instance/data/local/bin/, /system/bin/ if remounted to rw, /sdcard if remounted to exec)
and run from device or adb shell like%
su
flash_image recovery /sdcard/recovery.img
after that, you can reboot to hboot, check out that you do not have cwm recovery anymore, boot to android and install OTA as usual from menu...
does the recovery also do a backup of the radio?
(my wifi is broken sinve ota update - and I'm an stock recovery now, so can't test at the moment)
Cache being mounted or unmounted isnt the issue.
I can wipe cache manually but automatting it in the script seems the break the whole process.
Its good for testing and having a fresh install.
Lets android re-build everything.
Take from Clockworks How to:
wipe cache partition
Wipes the cache partition of the device to clear all the data accumulated there over use. This is often used before installing a new ROM, app, kernel or any similar mod via recovery
Click to expand...
Click to collapse
http://www.addictivetips.com/mobile...-and-how-to-use-it-on-android-complete-guide/
This is a flashable ZIP, containing the latest kernel and build of Android 4.3 by Google. It is made for the Google Nexus 7 3G, and is flashable through TWRP. I did not test it since I don't have a 3G model of the Nexus 7.
Download link: https://mega.co.nz/#!xskHxaRb!ZP3kYCk66VinJc70TswVBSAv8yZ3QoKKgUCtzVe66lY
Odexed, and no superuser management tool. Chainfire released an experimental version supporting Android 4.3 on his Google+. so I'll add that to the OP later.
Enjoy!
Anybody tested?
Also, will there be radio and bootlosder in flashable form?
Fatal1ty_18_RUS said:
Anybody tested?
Also, will there be radio and bootlosder in flashable form?
Click to expand...
Click to collapse
From what i can see, there is no bootloader and radio in it, so anyone has to flash it by himself.
EDIT: The ZIP works fine, i just flashed bootloader and radio through fastboot prior to installing it over TWRP. Haven't tested any root zips, yet.
i got 4.3
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Root does work, flashing this zip. Although Titanium Backup didn't work at first, i installed busybox, changed the backups location from /storage/emulated/0 -> /storage/emulated/legacy and i had to uncheck the first backup to make the restore work (no idea which of those three things actually did the work).
biggoldring said:
Click to expand...
Click to collapse
That's great, but can someone explain why baseband is still old (i've flashed 0.18 and on fastboot i see the correct version, but on System->About i get still 0.17)?
stadicon said:
Root does work, flashing this zip. Although Titanium Backup didn't work at first, i installed busybox, changed the backups location from /storage/emulated/0 -> /storage/emulated/legacy and i had to uncheck the first backup to make the restore work (no idea which of those three things actually did the work).
That's great, but can someone explain why baseband is still old (i've flashed 0.18 and on fastboot i see the correct version, but on System->About i get still 0.17)?
Click to expand...
Click to collapse
you mean you flash the zip in stock recovery??
Gabrieltan said:
you mean you flash the zip in stock recovery??
Click to expand...
Click to collapse
I don't have stock recovery, TWRP remained untouched through this process. I just installed this zip to gain root access through TWRP, then changed setting in Titanium Backup to make it work..
stadicon said:
I don't have stock recovery, TWRP remained untouched through this process. I just installed this zip to gain root access through TWRP, then changed setting in Titanium Backup to make it work..
Click to expand...
Click to collapse
so your point is flash the rom then direct flash the zip?? because if boot then flash the zip definitely TWRP will lose. Am i right?
Gabrieltan said:
so your point is flash the rom then direct flash the zip?? because if boot then flash the zip definitely TWRP will lose. Am i right?
Click to expand...
Click to collapse
No, why it should get lost?
The process i did was:
1) Boot at bootloader ([POWER]+[VOL-])
2) fastboot flash bootloader <bootloader.img>
3) fastboot flash radio <radio.img>
4) Start recovery (TWRP)
5) Flash stock-4.3 zip
6) Flash SuperSU zip
That's all. Neither recovery, nor userdata were touched through this process. The only affected partitions are bootloader, radio, system, boot and data.
stadicon said:
No, why it should get lost?
The process i did was:
1) Boot at bootloader ([POWER]+[VOL-])
2) fastboot flash bootloader <bootloader.img>
3) fastboot flash radio <radio.img>
4) Start recovery (TWRP)
5) Flash stock-4.3 zip
6) Flash SuperSU zip
That's all. Neither recovery, nor userdata were touched through this process. The only affected partitions are bootloader, radio, system, boot and data.
Click to expand...
Click to collapse
i just full wipe my tilapia.. lolx.. anyway, i have backup all of my apps in zip file.. hahaha
one thing can confirm is no need flash bootloader.. i didnt flash it still ok.. but radio i not sure yet..because dont have simcard right now..lolx
Gabrieltan said:
i just full wipe my tilapia.. lolx.. anyway, i have backup all of my apps in zip file.. hahaha
one thing can confirm is no need flash bootloader.. i didnt flash it still ok.. but radio i not sure yet..because dont have simcard right now..lolx
Click to expand...
Click to collapse
You mean you download zip file from OP, then flash it in TWRP?
Sent from my GT-N7105 using Tapatalk 4 Beta
zard said:
You mean you download zip file from OP, then flash it in TWRP?
Sent from my GT-N7105 using Tapatalk 4 Beta
Click to expand...
Click to collapse
yup.. without flash bootloader.. now trying for titanium.. where can change the storage thing?
Gabrieltan said:
yup.. without flash bootloader.. now trying for titanium.. where can change the storage thing?
Click to expand...
Click to collapse
This is Chainfire's information: You can fix this by going into preferences and selecting a folder under /storage/emulated/legacy as backup/restore path, not under /storage/emulated/0
I think it means that you copy your files from /storage/emulated/0 to /storage/emulated/legacy, then rescan backup directory and set to /storage/emulated/legacy.
Sent from my GT-N7105 using Tapatalk 4 Beta
zard said:
This is Chainfire's information: You can fix this by going into preferences and selecting a folder under /storage/emulated/legacy as backup/restore path, not under /storage/emulated/0
I think it means that you copy your files from /storage/emulated/0 to /storage/emulated/legacy, then rescan backup directory and set to /storage/emulated/legacy.
Sent from my GT-N7105 using Tapatalk 4 Beta
Click to expand...
Click to collapse
that is what i did just now... and it cause i lost my root for tb.. now trying clear data, forget root and rerun the application
Gabrieltan said:
i just full wipe my tilapia.. lolx.. anyway, i have backup all of my apps in zip file.. hahaha
one thing can confirm is no need flash bootloader.. i didnt flash it still ok.. but radio i not sure yet..because dont have simcard right now..lolx
Click to expand...
Click to collapse
Yeah, i forgot to say that i full wiped first, of course (not sure if it's mandatory, though). Bootloader and radio may not be so important, as after i flashed them 4.2.2 booted successfully (before installing 4.3) which might be a sign that not much of a difference was made.
Gabrieltan said:
yup.. without flash bootloader.. now trying for titanium.. where can change the storage thing?
Click to expand...
Click to collapse
Just go on to Menu->Preferences... . There is an option about the location of the backups (the first option under Backup Settings). If you press on it you get on /storage/emulated/0/TitaniumBackup but you change that to /storage/emulated/legacy/TitaniumBackup. Practically, it's the same folder (nothing needs to be copied or anything) but it's just on a different mount point and for some reason (i am guessing permissions) it does work. If it asks you to copy any other backups just don't do it, everything is already there.
stadicon said:
Just go on to Menu->Preferences... . There is an option about the location of the backups (the first option under Backup Settings). If you press on it you get on /storage/emulated/0/TitaniumBackup but you change that to /storage/emulated/legacy/TitaniumBackup. Practically, it's the same folder (nothing needs to be copied or anything) but it's just on a different mount point and for some reason (i am guessing permissions) it does work. If it asks you to copy any other backups just don't do it, everything is already there.
Click to expand...
Click to collapse
LOLx... i did that and now my backup all lose.. urs still at there?? one more thing, you able use tb to delete apps??
There should be no way to lose your backups unless you have chosen purposely to do so. Check that your Titanium Backups folder is still there in SDCARD.
If I weren't on vacation using only Chromebook I'd have upped this this morning with root; I managed via ARM Chromebook dev mode with adb and fastboot to backup data from my N4 and N7 3G and then install stock, flash recovery and make root, followed by restoring my titanium data. Both devices were as they were in 4.2.2 but in 4.3 within the hour.
Furthermore I had the ability to flash Franco r170 on the N4
Gabrieltan said:
LOLx... i did that and now my backup all lose.. urs still at there?? one more thing, you able use tb to delete apps??
Click to expand...
Click to collapse
Just use a file manager to make sure everything is fine. Technically, /storage/emulated/0/TitaniumBackup and /storage/emulated/legacy/TitaniumBackup is the same folder, i don't know why TB does't list your backups.
BTW, i think the battery drain issue is now fixed.
stadicon said:
Just use a file manager to make sure everything is fine. Technically, /storage/emulated/0/TitaniumBackup and /storage/emulated/legacy/TitaniumBackup is the same folder, i don't know why TB does't list your backups.
Click to expand...
Click to collapse
i also dont know why.. but i can backup... ya, only can use root explorer to delete, i tried few apps, all cant delete..
gapps hosted here works: http://forum.xda-developers.com/showthread.php?t=2248654
this Recovery is now depreciated go https://forum.xda-developers.com/showthread.php?p=71244945 instead
What's new
MTP auto mount on boot fixed!
Data unmount after few seconds fixed.
Bugs
Battery Info doesn't work (due to M based sources)
Data decryption
Mount Loop devices (Kernel issue) can't be fixed atm
Credits: TWRP (Team win Recovery Project)
Huawei
@BadWolfYe for giving info on how he got MTP working.
Me
Current status: Stable
Created: 2016-11-20
Removed
LastStandingDroid said:
This was shared here for reasons that some P9 users came to our H8 thread so i decided to post it here as well.
Click to expand...
Click to collapse
Thank you so much for your hard work. When you say data works but requires reflash could you explain which part requires reflash?
Regards
Lee
Just to clarify, does this allow mounting and editting of /system partition, manually via TWRP terminal?
Atarii said:
Just to clarify, does this allow mounting and editting of /system partition, manually via TWRP terminal?
Click to expand...
Click to collapse
Yes you can mount cust, data, system, product, vendor
thel2dab said:
Thank you so much for your hard work. When you say data works but requires reflash could you explain which part requires reflash?
Regards
Lee
Click to expand...
Click to collapse
The properdata fix will flash a empty image to the phone which you'll have to resize after flash or I'll get 2.Gb of internal storage only.you might need repair data first or reboot recovery for it to be repairable.
Sent from my FRD-L09 using Tapatalk
U are best.
Does flashing ROM's work?
I whant to flash newest N emui 5.0 wihout roolback
I don't know why but my phone fails to boot after flashing the properdatafix.zip and resizing.
It resizes correctly but after it won't boot. I have to flash old firmware and upgrade to to 7.0 again.
Any help would be great.
Regards
Lee
richish said:
U are best.
Does flashing ROM's work?
I whant to flash newest N emui 5.0 wihout roolback
Click to expand...
Click to collapse
It flashes firmwares yes I've reflashed N and the hw_EU full package
thel2dab said:
I don't know why but my phone fails to boot after flashing the properdatafix.zip and resizing.
It resizes correctly but after it won't boot. I have to flash old firmware and upgrade to to 7.0 again.
Any help would be great.
Regards
Lee
Click to expand...
Click to collapse
Exactly what did you flash? AFAIK if it is a zip that mounts a image it will either bill the flash process with a reboot or make your device stuck on splash screen. What zip did u use?
If.u flashed N pack from M twrp u can install it again with this twrp. If it doesn't boot then it's probably due to a Img (ext4) that is being mounted and that's most likely is due to modified boot.img which will kill the boot procedure supersu package can make a modified boot but it won't boot due to su.img being mounted so it'll reboot to recovery
Sent from my FRD-L09 using Tapatalk
LastStandingDroid said:
Exactly what did you flash? AFAIK if it is a zip that mounts a image it will either bill the flash process with a reboot or make your device stuck on splash screen. What zip did u use?
Click to expand...
Click to collapse
I flashed the properdatafix.zip from the 1st post. Then rebooted in to twrp went to wipe - advanced wipe - data - resize partion - reboot - stuck on black screen.
fastboot flash, recovery, boot, system, from stock to get device booting again.
I must be doing something wrong. I know this is really cheeky to ask but could you make a video or something of the correct flashing procedure? The way I have tried is like this:
1 Fastboot flash your recovery.img
2. Boot into TWRP recovery.
3. Install properdatafix.zip
4. Reboot recovery.
5. Resize data partition.
6. Reboot and phone wont boot anymore.
Regards
Lee
thel2dab said:
I flashed the properdatafix.zip from the 1st post. Then rebooted in to twrp went to wipe - advanced wipe - data - resize partion - reboot - stuck on black screen.
fastboot flash, recovery, boot, system, from stock to get device booting again.
I must be doing something wrong. I know this is really cheeky to ask but could you make a video or something of the correct flashing procedure? The way I have tried is like this:
1 Fastboot flash your recovery.img
2. Boot into TWRP recovery.
3. Install properdatafix.zip
4. Reboot recovery.
5. Resize data partition.
6. Reboot and phone wont boot anymore.
Regards
Lee
Click to expand...
Click to collapse
You can install the firmware again after you resized the data partition if something goes wrong and report back if it helps. Maybe it is a block issue in fstab but it shouldn't be
Sent from my FRD-L09 using Tapatalk
@LastStandingDroid
I also will not boot in the system...
What file system (data) should be displayed in TWRP, ext4?
LastStandingDroid said:
You can install the firmware again after you resized the data partition if something goes wrong and report back if it helps. Maybe it is a block issue in fstab but it shouldn't be
Sent from my FRD-L09 using Tapatalk
Click to expand...
Click to collapse
How should I install the firmware again? Through flashable zip or through dload folder and hold vol up and down when restarting phone? Thank you for your patience, I know I am taking a lot of your time with this.
Regards
Lee
kep2008 said:
@LastStandingDroid
I also will not boot in the system...
What file system (data) should be displayed in TWRP, ext4?
Click to expand...
Click to collapse
The data should be ext4 format. Could u mount system and check if there's any file in system folder also u might need to resize system as well since u only have 19mb as well.
thel2dab said:
How should I install the firmware again? Through flashable zip or through dload folder and hold vol up and down when restarting phone? Thank you for your patience, I know I am taking a lot of your time with this.
Regards
Lee
Click to expand...
Click to collapse
Sent from my FRD-L09 using Tapatalk
thel2dab said:
How should I install the firmware again? Through flashable zip or through dload folder and hold vol up and down when restarting phone? Thank you for your patience, I know I am taking a lot of your time with this.
Regards
Lee
Click to expand...
Click to collapse
I'd use twrp to flash it.since u won't have to roll back again
Sent from my FRD-L09 using Tapatalk
LastStandingDroid said:
I'd use twrp to flash it.since u won't have to roll back again
Sent from my FRD-L09 using Tapatalk
Click to expand...
Click to collapse
Thanks. It seems to reflash ok in TWRP but after the flash completes. I need to factory reset but I am back to to stock recovery. It seems that flashing the update.zip overwrites the recovery. (I assume this is expected?)
Thanks again for your help. Is there is anything else I can try to get this to work?
Regards
laststandingdroid said:
the data should be ext4 format. Could u mount system and check if there's any file in system folder also u might need to resize system as well since u only have 19mb as well.
Sent from my frd-l09 using tapatalk
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Again install update.zip 7.0, but the system will not boot...
thel2dab said:
Thanks. It seems to reflash ok in TWRP but after the flash completes. I need to factory reset but I am back to to stock recovery. It seems that flashing the update.zip overwrites the recovery. (I assume this is expected?)
Thanks again for your help. Is there is anything else I can try to get this to work?
Regards
Click to expand...
Click to collapse
Yes the recovery is replaced after flash back stock. Did it boot after reflashed?
Strange are you having Vendor And product option available in Mount restore and backup? To see if they are properly flashed?
kep2008 said:
View attachment 3948500View attachment 3948501
Again install update.zip 7.0, but the system will not boot...
Click to expand...
Click to collapse
Did you get the data to work in TWRP? I think the boot.img is the issue here tbh. Since I neither can't boot unless I use a supersu fixed image.
Sent from my FRD-L09 using Tapatalk
Ok w8 I'll fix a twrp that will make the installation of su system less mode possible but u will be forced to remove su.img from /data/ else it won't boot
fastboot flash this: http://www21.zippyshare.com/v/7YNPp3AI/file.html
Before You Flash SuperSU-Systemmode you need to mount system & /vendor first since the Sepolicy is located in the "Vendor" Partition for reasons i won't bother to explain.
Once Flashed Mount Data again (if it gets unmounted, mount system) and navigate to /data and remove su.img
This will make N booting
Sent from my FRD-L09 using Tapatalk
LastStandingDroid said:
Yes the recovery is replaced after flash back stock. Did it boot after reflashed?
Strange are you having Vendor And product option available in Mount restore and backup? To see if they are properly flashed?
Did you get the data to work in TWRP? I think the boot.img is the issue here tbh. Since I neither can't boot unless I use a supersu fixed image.
Sent from my FRD-L09 using Tapatalk
Click to expand...
Click to collapse
/data is mounted only with /system, but the installation files still contain errors /data/media
mount -o bind /data/media /sdcard process ended with ERROR 255
kep2008 said:
/data is mounted only with /system, but the installation files still contain errors /data/media
mount -o bind /data/media /sdcard process ended with ERROR 255
Click to expand...
Click to collapse
Did u use the new recovery? If so that is for now common since it uses a different mount file rather than busbox version) that's why this message comes
In fact I copied over the "original" mount file from stock recovery but it isn't copying the compete file as it's only 6b so it'll stay until I try fix it.
Sent from my FRD-L09 using Tapatalk
I rooted my HTC U11+ using Magisk without having TWRP installed. I can't find the link anymore, but I think it was through fastboot and if I remember correctly, I had to format /data after installing Magisk due to the device encryption. Everything is working fine.
Today I got a notification that a new firmware with the version number 1.24.401.2 is available (current version is 1.10.401.23). I'm pretty sure if I install it, i I will loose root and I would have to install Magisk again to gain root back which would require to format /data. I would like to prevent that since I've spend ages to configure and adjusting everything to my needs and I'm not keen to do that again.
Is there a way of installing the OTA update without loosing root and having to wipe /data?
midiwidi said:
I rooted my HTC U11+ using Magisk without having TWRP installed. I can't find the link anymore, but I think it was through fastboot and if I remember correctly, I had to format /data after installing Magisk due to the device encryption. Everything is working fine.
Today I got a notification that a new firmware with the version number 1.24.401.2 is available (current version is 1.10.401.23). I'm pretty sure if I install it, i I will loose root and I would have to install Magisk again to gain root back which would require to format /data. I would like to prevent that since I've spend ages to configure and adjusting everything to my needs and I'm not keen to do that again.
Is there a way of installing the OTA update without loosing root and having to wipe /data?
Click to expand...
Click to collapse
Would the following be helpful?
Haven't tried myself yet.
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
Thank you for the link DanteGR. It looks promising.
I'll have to find out if my HTC U11+ is supported by FlashFire. It most likely doesn't have two partitions (A/B).
So if somebody knows if the U11+ is working with FlashFire, please let me know!
Is there a way of backing everything up in case something goes wrong with with the OTA update using FlashFire? I'm not keen on loosing all the adjustments and settings I made in the last couple of weeks (I even modified files in /data/data to fix App issues). As far as i know Nandroid backups are not possible because the currently available TWRP recovery for the U11+ doesn't support data decryption. I have backups to Google Drive enabled (with all options including App data), but I don't know if that is enough to bring the system back into the current state afterwards.
midiwidi said:
Thank you for the link DanteGR. It looks promising.
I'll have to find out if my HTC U11+ is supported by FlashFire. It most likely doesn't have two partitions (A/B).
So if somebody knows if the U11+ is working with FlashFire, please let me know!
Is there a way of backing everything up in case something goes wrong with with the OTA update using FlashFire? I'm not keen on loosing all the adjustments and settings I made in the last couple of weeks (I even modified files in /data/data to fix App issues). As far as i know Nandroid backups are not possible because the currently available TWRP recovery for the U11+ doesn't support data decryption. I have backups to Google Drive enabled (with all options including App data), but I don't know if that is enough to bring the system back into the current state afterwards.
Click to expand...
Click to collapse
No problem.
AFAIK unfortunately there isn't a way for a full backup without a completely functioning TWRP.
If rooted, Titanium would be your best bet but not for everything obviously.
midiwidi said:
I rooted my HTC U11+ using Magisk without having TWRP installed. I can't find the link anymore, but I think it was through fastboot and if I remember correctly, I had to format /data after installing Magisk due to the device encryption. Everything is working fine.
Today I got a notification that a new firmware with the version number 1.24.401.2 is available (current version is 1.10.401.23). I'm pretty sure if I install it, i I will loose root and I would have to install Magisk again to gain root back which would require to format /data. I would like to prevent that since I've spend ages to configure and adjusting everything to my needs and I'm not keen to do that again.
Is there a way of installing the OTA update without loosing root and having to wipe /data?
Click to expand...
Click to collapse
As you, I have root but no TWRP installed. I did the OTA update and I didn't lost my data. I lost root during the process but it was very easy to install it back without loosing or wipe data.
If you have installed Magisk via patched boot.img, here is what I have done :
-Go in Magisk, choose uninstall and then "restore image"
-Then, go check for update on your phone and start it.
-At the same time, download stock RUU rom (the same as the OTA, here for European version : https://forum.xda-developers.com/htc-u11/development/htc-u11-stock-rom-ruu-t3741849) and extract boot.img from it with RUUdecrypttool (https://forum.xda-developers.com/chef-central/android/tool-universal-htc-ruu-rom-decryption-t3382928). It can be long.
-When update is complete and you have extracted boot.img, put it in your phone and patch it with magisk : install, patch boot image. Then you will have a "patched_boot.img" in your magiskmanager folder. Copy this file on your PC.
-Go to download mode on your phone and flash patched_boot.img via Flashtool.
Root is back, no data lost :good:
Kidy973 said:
As you, I have root but no TWRP installed. I did the OTA update and I didn't lost my data. I lost root during the process but it was very easy to install it back without loosing or wipe data.
If you have installed Magisk via patched boot.img, here is what I have done :
-Go in Magisk, choose uninstall and then "restore image"
-Then, go check for update on your phone and start it.
-At the same time, download stock RUU rom (the same as the OTA, here for European version : https://forum.xda-developers.com/htc-u11/development/htc-u11-stock-rom-ruu-t3741849) and extract boot.img from it with RUUdecrypttool (https://forum.xda-developers.com/chef-central/android/tool-universal-htc-ruu-rom-decryption-t3382928). It can be long.
-When update is complete and you have extracted boot.img, put it in your phone and patch it with magisk : install, patch boot image. Then you will have a "patched_boot.img" in your magiskmanager folder. Copy this file on your PC.
-Go to download mode on your phone and flash patched_boot.img via Flashtool.
Root is back, no data lost :good:
Click to expand...
Click to collapse
Just a heads up.
I think for OTAs only (NOT RUUs) you don't even have to use the decrypt tool.
The zip is already decrypted so just extract the boot.img.
EDIT: Not 100% sure though will try it out this evening.
DanteGR said:
Just a heads up.
I think for OTAs only (NOT RUUs) you don't even have to use the decrypt tool.
The zip is already decrypted so just extract the boot.img.
EDIT: Not 100% sure though will try it out this evening.
Click to expand...
Click to collapse
That is correct.
I have done it many times.
m3johan said:
That is correct.
I have done it many times.
Click to expand...
Click to collapse
Oh well.
Last night I downloaded a random OTA for the HK version and the firmware.zip inside it could not be opened I guess due to encryption.
Are you sure about that?
DanteGR said:
Oh well.
Last night I downloaded a random OTA for the HK version and the firmware.zip inside it could not be opened I guess due to encryption.
Are you sure about that?
Click to expand...
Click to collapse
I can not be 100% sure, but all I have unpacked including this 1.24.401.2 ota were no problem.
Can you give me the link to the HK-ota?
m3johan said:
I can not be 100% sure, but all I have unpacked including this 1.24.401.2 ota were no problem.
Can you give me the link to the HK-ota?
Click to expand...
Click to collapse
This is the one I tried to extract without success.
Just to make it clear. I had no problem extracting the actual OTA. The problem was trying to extract the firmware.zip inside it.
Thank you for your input.
https://www.androidfilehost.com/?fid=962187416754455026
DanteGR said:
This is the one I tried to extract without success.
Just to make it clear. I had no problem extracting the actual OTA. The problem was trying to extract the firmware.zip inside it.
Thank you for your input.
https://www.androidfilehost.com/?fid=962187416754455026
Click to expand...
Click to collapse
You are right. I could not unpack firmware from that one either.
Deleted
m3johan said:
You are right. I could not unpack firmware from that one either.
Click to expand...
Click to collapse
The decrypt tool doesn't seem too bad after all though.
I'll have to try it shortly.
For those who are using Taiwan model, what is your software number?
Mine is 1.23.709.9
RUU decrypt tool
DanteGR said:
The decrypt tool doesn't seem too bad after all though.
I'll have to try it shortly.
Click to expand...
Click to collapse
RUU_decrypt_tool works like a charm
the command on the command line is (in windows) RUU_decrypt_tool -f RUU file name (use TAB for name completion or rename to RUU.zip) (for firmware files) which gets you (see thumbnail)
The tool automatically has a output as "OUT" in the folder where it resides; I've put my RUU file in the ADB folder together wit the RUU_decrypt_tool
You'll find the RUU_decrypt_tool here
btw: I am 70 years young, so if I can do it most people can as well.....
If none of the required arguments are supplied a simple Yes/No interface will be presented.
Required arguments (and/or):
-s, --system extract the system.img and boot.img (for ROM)
-f, --firmware extract the firmware files
-z, --sdruuzip copy and rename rom.zip for SD-Card flashing
Note: this will create a duplicate if the input is already a rom.zip
Keyfile Updater arguments:
-o, --offline disable down/upload of keyfiles
--no-upload do not upload if a new keyfile is generated
--sync-keyfiles sync entire keyfile folder (download & upload)
when used without a RUU the tool will only synchronize the
keyfiles, otherwise it will download new keyfiles before decrypting
and upload only if a new keyfile is generated
Click to expand...
Click to collapse
When I used to have htc 10 s-on I could update the fw using a zip file(perhaps firmware. Zip) inside the OTA file for my cid and flash it in RUU mode, of course I had to use a custom rom based on the same fw to complete it
Finally, after a couple of month and being annoyed of the update message popping up all the time, I got some time to proceed with the update.
I found that what I've said in my first post isn't true. I had a non-official TWRP (without decryption support) installed and now remember that I have installed Magisk through that.
I've started the update procedure with clicking "uninstall" and "restore image" in the Magisk app. After downloading the OTA, I clicked on install now. My phone rebooted into recovery (TWRP) and prompted to enter my unlocking pattern. I entered it, but TWRP said something like can't mount, wrong password.
I thought it's because TWRP doesn't support decryption yet and I need to go back to the stock recovery to be able to apply the OTA. I extracted the recovery_signed.img from here (from the same software version I'm currently running 1.10.401.23) and flashed it using fastboot. If I boot into recovery now, I see it's the stock one, but it shows a red exclamation mark in a red triangle. I can press power button + volume up and get into the normal recovery menu. I've tried to wipe the cache there, but it didn't made a difference. I still get that red exclamation mark. If I download the OTA and click on install now, my phone restarts and shows the normal picture of applying the update until about 24% of progress and then it shows the red exclamation mark again. If I press power + volume up now, nothing happens.
If I manually boot into recovery and use power + volume up to get into the recovery menu, there are two options to apply an update. One using the sdcard and one using ADB. I have the hope that the red exclamation mark is gone once I installed the update manually.
The sdcard option doesn't work. The recovery shows the message can't mount /sdcard. The ADB sideload option causes problems too.
If I use a older version of ADB I get the error "cannot read OTA.zip" in my command window on the PC. I've tried it with a small text file and that worked. I read that it has something to do with the address space which is too small and that I should use the newest version from googles platform tools. I installed version 27.0.1 and used the contained ADB to do the sideload. This time I got an error message like "adb server version (31) doesn't match this client (36)", but it didn't say that it can't read the file.
I'm kind of stuck now. Has somebody a suggestion how to proceed, to get rid of the red exclamation mark so that I can normally apply the OTA update and gain root again afterwards by flashing a Magisk patched boot.img through fastboot?
midiwidi said:
...shows the normal picture of applying the update until about 24% of progress and then it shows the red exclamation mark again....
Click to expand...
Click to collapse
You have a modified /system partition. You will need to restore stock system partition of the version you are running to get past this.
You have a modified /system partition. You will need to restore stock system partition of the version you are running to get past this.
Click to expand...
Click to collapse
Thank you very much for this hint. I will do a
fastboot flash system system.img
tonight and let you know how it went.
I did flash the original system.img. Here the output of the command window
C:\Users\midiwidi\Downloads\HTC_U11+\Original_HTC_Firmware_Europe\OUT_2Q4D_1.10.401.23\system>fastboot.exe flash system system.img
sending 'system' (16384 KB)...
OKAY [ 1.651s]
writing 'system'...
(bootloader) HOSD CL#991677
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 3.461s]
finished. total time: 5.111s
Unfortunately that didn't change anything. I still get the red exclamation mark if I boot into recovery
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
.
Is there a log file or something similar to find out what the recovery is complaining about? This is the output after bypassing the red exclamation mark with power + volume up
.
Any other ideas how to proceed?
POST - v14
(This number will increase every time the post is updated.)What's new in v14?
Corrected some simple mistakes in procedure.Modified overall post for better UX.
Spoiler: Version Changelog
What's new in v13?
Modified Gapps part in requirements to make it more clear.Added useful information section. for Pro Noobs and Ultra Noobs like me.What's new in v12?
Added User Contributions and feedback section.Added Miscellaneous recommendations section.Modified some steps in installation procedure to make it even more noob friendly.Linked @lmaohelp's thread.Decreased size of text in procedure.
This ROM is based on Android 10 GSI builds of @phhusson (Thanks a ton to him).
Thanks to @Hami_Do for his hi6250 patches.
Thanks to Huawei for making their phones nearly unbrickable .
Thanks to @Djiban for his ideas on improving the thread.
Follow this thread only if you know what you're doing. I'm not responsibe for any damage or thermonuclear wars .
Read the post completely and understand it before doing anything ATLEAST FOR THE SAKE OF MANKIND .
This thread is best viewed in PC and is Noob Friendly.
Note that I was using flux substratum theme in the screenshots. Hence, icons and colors may vary on your device.
Spoiler: Requirements
Requirements:
Huawei Honor 6X (Unlocked Bootloader. If not, follow this post (using PotatoNV) or YouTube video.
EMUI 8 (If not, you could follow this guide, direct file : link).
GSI from link (download system-quack-arm64-aonly-vanilla.img.xz, you could try others but arm64, a-only is must).
TWRP from attchments or link or any other TWRP recovery compatible with Honor 6X EMUI 8.
Gapps(Optional, I used nano OpenGapps, NikGapps gave an error during installing, You can also try others. You can directly try the img with gapps instead of vanilla but i prefer nano gapps over vanilla).
stock recovery.
Time.
PC.
ADB and Fastboot.
Patience.
Human Brain.
ALL IN ONE GUIDE : Check it out here. It contains every thing in detail all the way from bricked device -> EMUI 2 -> EMUI 5 -> EMUI 8 -> AOSP 10 (mentioned in this post). Thanks to @lmaohelp for his effort and describing everything in detail.
Useful Information :
What on the Earth is meant by Vanilla android? -> it is the stock / pure version of android without Google apps and services.
What is OpenGapps? Check it out at OpenGapps.org!
What is Nano (not the mathematical 10^-9) Gapps? It is a version of Gapps with Minimal installation which means only the core part of gapps is installed with very little major apps. They can be installed later.
What is ARM64? it is a 64 bit operating system/platform.
What on the moon is AOSP? It stands for android open source project which is the purest form of android.
NOTE : My device bootlooped whenever I tried installing Magisk. So, better stick with the PHH-SuperUser that you get out-of-the-box with the system image.
NOTE : Skip every step with gapps if you are already using img with gapps.
What isn't working :
VoLTE (can't be fixed as per my knowledge), Camera (FIXED NOW | trying to find a fix, replacing libcamxxx could help), Flashlight (FIXED NOW | also trying to find a fix, fixing camera may fix this too).
CAMERA AND TORCH HAVE BEEN FIXED. Thanks to @Hami_Do (flash the attched patch file whenever you are bored, LOL)
What's Working :
Everything except the ones mentioned above VoLTE.
*Tell me if something else isn't working.
***If you have a bricked device/messed up somewhere during the process and unable to figure out what to do, follow this guide by @lmaohelp .***Procedure :
Make sure your device is running EMUI 8.
Extract downloaded image using some xz extractor(7zip can also do this), copy it to pc.
Reboot your device to TWRP recovery.
Format the data partition {Wipe > Format data > type "yes"}
(Optional) In TWRP, choose wipe > advanced wipe > select system, data, cache and DALVIK and format them.
Check if your device is detected by adb using
Code:
adb devices
.
Move the img file using adb to device
Code:
adb push -p *img-name*.img /sdcard/
(the img file must be in adb directory).
(Optional, only if you want nano gapps over vanilla) Move Gapps in the same manner
Code:
adb push -p *gapps-name*.zip /sdcard/
(the zip file must be in adb directory).
Install img as system image {Install > Install Image > Select > Choose system image > Swipe➡}.
(Optional, only if you want nano gapps over vanilla) Unmount and Remount system partition. Go to wipe > advanced wipe > Choose system > resize. Flash gapps.
Flash stock recovery(also available in attachments) with twrp in the same way. push it with adb using
Code:
adb push -p STOCK_RECOVERY_RAMDISK.img /sdcard/
and flash it with twrp as "Recovery" after choosing install image.
Disconnect your device from PC and reboot to recovery(stock one).
Clear cache partition and perform a factory reset(You'll get an error during factory reset but you have to do it) (your device will bootloop if wiped with twrp itself).
Reboot, Cross your fingers and wait.
>If you flashed gapps over vanilla, the first boot would take about 5 mins. else, it would be very fast. Subsequent boots on both are quite fast.
>Sometimes, I observed that flashing gapps from internal storage caused bootloop(this is because of corrupt zip), in such case get back to EMUI 8, repeat the process by flashing gapps from micro sd.
*you'll get a warning that something wrong with your device every time you boot it. IGNORE IT.
Spoiler: Additionals
Additionals:
> If you messed up somewhere during installation, you can always recover your device by following this guide.
> If you have the update.zip file from the above mentioned EMUI 8 folder directly, you could just directly flash it after wiping data, system and cache(use adb push or microsd to transfer update.zip to device).
>Its better to charge your device to atleast 70% before doing anything as you'll have ample of time to recover it if you messed up something. If not, you can still charge your device in eRecovery mode and twrp but i found some issues like heating up and slow charging.
>Don't forget to set ringtone, notification and other sounds from settings after booting.
Spoiler: Updates
Updates :
I was able to install magisk by flashing unSU zip from @Hami_Do 's thread on hi6250 manual fixes and then flashing phh's magisk after deleting phh-su from /system/bin/ but sadly, I wasn't able to use quickswitch for other launchers as it needs magisk version of 20.4 (min.) but phh's magisk is 19.3 and substratum theme engine is not working (due to some error). So, I'm sticking with the root that comes out of the box and I recommend you to do the same. EXTRAS : The Phone and Messaging apps that came out of the box with the GSI stopped working after installing magisk. So, you are installing magisk, just replace these system apps from LineageOS ones or delete them and install the google phone and messaging from play store.
During multiple tests (installing, modifying and testing the GSI for its stability in multiple ways), I found that you need not always go back to stock EMUI 8 if you messed up something. This works without error but if you have some time, getting back to stock EMUI 8 is still recommended before installing some other ROM/GSI.
Try not to touch the finger print sensor when you are at the setup after first boot. This is making the finger print sensor not recognisable until next reboot.
User Feedback and Contributions :
Thanks to @OrionThyHunter for his feedback and some fixes :
Using the Greenify app will stop the finger print sensor from working. FIX : Disable "Alternative Screen Off Mode".
Thanks to @[email protected] for finding out he following issues :
Adaptive Brightness Doesn't work. Flash the attachment in this post to fix it.
To pass SafetyNet, follow this post.
Miscellaneous Recommendations :
Use Google Camera Go app for photos. Its much better than the GSI's stock one.
Happy Flashing !
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
thank you it worked, now waiting for volte and camera fix on next update.... please update soon.... waiting waiting waiting........
[email protected] said:
thank you it worked, now waiting for volte and camera fix on next update.... please update soon.... waiting waiting waiting........
Click to expand...
Click to collapse
I think VoLTE can't be fixed.
For camera, you have to replace each file in /system/lib/ starting with libcam(libcamxyz...) from stock emui 8 and check each possible combination with subsequent reboots. I'm a little bit busy right now as I'm working on AOSP 11(as I believe it'll run without much problems because it has been tested on other hi6250 devices) with @Djiban. You could just do this on your own. If you find any working combination, please post it in this thread.
[email protected] said:
thank you it worked, now waiting for volte and camera fix on next update.... please update soon.... waiting waiting waiting........
Click to expand...
Click to collapse
Finally, Fixed it dude(camera and torch) by replacing libraries! Found a patch that does the same thing. Updated the Original post.
Tried a lot to fix VoLTE but didn't work... will try again later.
CHECK IT OUT!
#endyourwait LOL!
Hi again, I got this installed using TWRP, and I still have TWRP installed because I don't have the stock recovery. The system boots but it is giving me an error saying encryption unsuccessful, with a button saying "erase all data" which does nothing, and I am unable to do anything.
I was having this error when I first installed EMUI 8 from EMUI 5 as well, but at least the button took me to eRecovery, where the factory reset would fail at 5-6%. Currently if I go into eRecovery and click factory reset, it just reboots and takes me to TWRP again. Also, when I go into eRecovery it asks me to reformat the partition because it is "corrupted", which somehow changes the file system for /data to f2fs, and causes the phone to be stuck on the android boot animation. When I change /data back to ext4 I am able to boot back to the screen of encryption unsuccessful.
How do I fix this issue and be able to use the phone? Attached is a screenshot of the error message the OS is giving me.
lmaohelp said:
Hi again, I got this installed using TWRP, and I still have TWRP installed because I don't have the stock recovery. The system boots but it is giving me an error saying encryption unsuccessful, with a button saying "erase all data" which does nothing, and I am unable to do anything.
I was having this error when I first installed EMUI 8 from EMUI 5 as well, but at least the button took me to eRecovery, where the factory reset would fail at 5-6%. Currently if I go into eRecovery and click factory reset, it just reboots and takes me to TWRP again. Also, when I go into eRecovery it asks me to reformat the partition because it is "corrupted", which somehow changes the file system for /data to f2fs, and causes the phone to be stuck on the android boot animation. When I change /data back to ext4 I am able to boot back to the screen of encryption unsuccessful.
How do I fix this issue and be able to use the phone? Attached is a screenshot of the error message the OS is giving me.
Click to expand...
Click to collapse
Did you flash stock recovery after flashing system image?
Get back to emui 8(if you have update.zip, you could directly flash it with twrp). Repeat the process. Flash stock recovery. Perform a factory reset. And boot it to the system for the first time. You could then flash twrp with fastboot.
***Do not do a factory reset with twrp! Its causing errors.***
Apparently it could be a faulty EMMC chip according to this website, which makes sense since TWRP is not able to mount the internal storage partition or the Dalvik / ART cache, and eRecovery is not able to reset the phone, which is a characteristic of EMMC failure, according to this website. I had to unplug the battery countless times when I was tinkering with the phone, because my power button is broken, and it definitely would've contributed to this failure according to what I have read. Well, guess I'm done with this phone lol
EDIT: Well I'm starting from scratch again but everything is installing fine so I guess nothing is wrong currently? Huawei factory reset even worked
Venkata Lochan Nune said:
Did you flash stock recovery after flashing system image?
Get back to emui 8(if you have update.zip, you could directly flash it with twrp). Repeat the process. Flash stock recovery. Perform a factory reset. And boot it to the system for the first time. You could then flash twrp with fastboot.
***Do not do a factory reset with twrp! Its causing errors.***
Click to expand...
Click to collapse
No, I don't know where to find the stock recovery file, where can I find it?
I managed to boot into EMUI 8 just fine since I did not have a password on the EMUI 5 OS before installing lol. Now I just need the stock recovery you are talking about so I can follow your steps.
do you mean, you testing ASOP 11 on honor 6x ? if yes wow......
[email protected] said:
do you mean, you testing ASOP 11 on honor 6x ? if yes wow......
Click to expand...
Click to collapse
Nope, not now. @Djiban is quite busy and for me to work, I'm not having a spare device. He'll do it when he's got free time.
I didn't find much noticeable differences between AOSP 10 and 11 execpt some ui improvements and under-the-hood improvements. So, I'll skip AOSP 11 and directly will work with AOSP 12 on future. I liked the new things introduced in android 12. So, I'll definitely work on it.
lmaohelp said:
No, I don't know where to find the stock recovery file, where can I find it?
I managed to boot into EMUI 8 just fine since I did not have a password on the EMUI 5 OS before installing lol. Now I just need the stock recovery you are talking about so I can follow your steps.
Click to expand...
Click to collapse
Do you have the update.zip file?
Or wait I'll attach one in few hours...
lmaohelp said:
Apparently it could be a faulty EMMC chip according to this website, which makes sense since TWRP is not able to mount the internal storage partition or the Dalvik / ART cache, and eRecovery is not able to reset the phone, which is a characteristic of EMMC failure, according to this website. I had to unplug the battery countless times when I was tinkering with the phone, because my power button is broken, and it definitely would've contributed to this failure according to what I have read. Well, guess I'm done with this phone lol
EDIT: Well I'm starting from scratch again but everything is installing fine so I guess nothing is wrong currently? Huawei factory reset even worked
Click to expand...
Click to collapse
This is because twrp on our phone doesn't support encryption-decryption things. So, they can only mount internal storage when you perform a complete data format by typing "yes".
Venkata Lochan Nune said:
Do you have the update.zip file?
Or wait I'll attach one in few hours...
Click to expand...
Click to collapse
I do, but I'm unfamiliar with how to get the recovery.img from the zip file. If you can tell me how to extract it or attach one that would be great!
lmaohelp said:
I do, but I'm unfamiliar with how to get the recovery.img from the zip file. If you can tell me how to extract it or attach one that would be great!
Click to expand...
Click to collapse
Actually, flashing it should replace twrp with stock one didn't it?
You can extract it with 7zip. It worked for me.
Venkata Lochan Nune said:
Actuall, flashing it should replace twrp with stock one didn't it?
You can extract it with 7zip. It worked for me
Click to expand...
Click to collapse
What do you mean by flashing it, the update file? I updated from EMUI 5 to EMUI 8 using a update.zip file and HWOTA method so I am not sure if that is the same thing as just flashing the update.zip file. Also, just extracting the files doesn't produce anything useful. I used a firmware extractor from this thread, which comes up with the files shown in the screenshot. Now I'm not sure which file is the stock recovery image. I also tried flashing Magisk for root access and using Flashify to backup the stock recovery image, but the app would just freeze, I'm not sure why.
lmaohelp said:
What do you mean by flashing it, the update file? I updated from EMUI 5 to EMUI 8 using a update.zip file and HWOTA method so I am not sure if that is the same thing as just flashing the update.zip file. Also, just extracting the files doesn't produce anything useful. I used a firmware extractor from this thread, which comes up with the files shown in the screenshot. Now I'm not sure which file is the stock recovery image. I also tried flashing Magisk for root access and using Flashify to backup the stock recovery image, but the app would just freeze, I'm not sure why.
Click to expand...
Click to collapse
Well you could directly flash update.zip with twrp.
Wail I'll attach it in a while. Just turned on my PC to search for it and this bloody "working on updates" came up.
lmaohelp said:
What do you mean by flashing it, the update file? I updated from EMUI 5 to EMUI 8 using a update.zip file and HWOTA method so I am not sure if that is the same thing as just flashing the update.zip file. Also, just extracting the files doesn't produce anything useful. I used a firmware extractor from this thread, which comes up with the files shown in the screenshot. Now I'm not sure which file is the stock recovery image. I also tried flashing Magisk for root access and using Flashify to backup the stock recovery image, but the app would just freeze, I'm not sure why.
Click to expand...
Click to collapse
Yeah I've faced the same problem with flashify and ofcourse other similar apps. The problem I usually get is that system partition isn't writable. After changing it to r/w, I get an error that boot image not found. (This doesn't happen in flashify, it just freezes). Not sure what the problem is maybe, huawei's anti modding measures...
This might be the stock recovery(its in between some 10 other recoveries so, not sure). Try it and inform me
EDIT : THIS IS NOT THE RIGHT ONE. STOCK RECOVERY WAS ATTACHED IN POST #1.
Venkata Lochan Nune said:
This might be the stock recovery(its in between some 10 other recoveries so, not sure). Try it and inform me.
Click to expand...
Click to collapse
I don't think that is the correct file, as I flashed it and "adb reboot recovery" just causes it to be stuck on the "your phone is unlocked" screen, and so does clicking the factory reset option in eRecovery. I tried extracting the RECOVERY_RAMDIS(K).img file and flashing it, which worked, and successfully failed (lol) to reset the phone.
EDIT: I got into the OS successfully. It is unexpectedly smooth, good job!
lmaohelp said:
I don't think that is the correct file, as I flashed it and "adb reboot recovery" just causes it to be stuck on the "your phone is unlocked" screen, and so does clicking the factory reset option in eRecovery. I tried extracting the RECOVERY_RAMDIS(K).img file and flashing it, which worked, and successfully failed (lol) to reset the phone.
EDIT: I got into the OS successfully. It is unexpectedly smooth, good job!
Click to expand...
Click to collapse
So you liked it?
And hey, attach the stock recovery for future reference if someone needs it.
Use the camera patch to fix cam and flashlight issues. It just replaces the libraries. Flash any emui 8 compatible twrp with fastboot. Take a migrate backup in case.
Google Camera GO app works like a charm and is better than the stock one so I recommended using it.
Enjoy your phone!