How-to get a GSI running on your HTC U11 life Android One
Bootloader must be Unlocked
Stock Update to 8.1 must be installed
The Kernel must be Stock without any changes (no Magisk)
Make a Backup thats not Stored on Your Device
Remove the Google Account from the Device and Factory Reset the Device using the Recovery How-to
Download the correct GSI (arm64 a/b)
Flash the system.img using fastboot in Download Mode:
Code:
fastboot flash system_<slot> system.img
where <slot> is a or b depending on your active partition
Reboot the Device and Enjoy
Bugs with phh treble GSI (most others are based on this):
Mobile data doesnt work
Notification LED doesnt work
Audio Output only over speaker (known bug in this GSI for several devices)
List of compatible Roms
If you want to go back to Stock, just download the latest Full Firmware File here in post #2 and Restore the Device using SD Card method like written in post #1 of the same thread.
Updated, added the Guide
I try to flash GSI treble on HTC U11 Life but it doesn't work...
fastboot flash system_a /Users/thibautmaringer/Downloads/PixelExperienceP-arm64-ab.img
Sending sparse 'system_a' 1/3 (1048572 KB) OKAY [ 36.946s]
Writing sparse 'system_a' 1/3 (bootloader) HOSD CL#1033709
(bootloader) [email protected]
(bootloader) [email protected]%
FAILED ()
Finished. Total time: 111.730s
I don't understand...
this is the way to go when, i won't say if, HTC goes down and support will end for our phones.
maybe a bit more difficult than to just flash an image as we've always done, but not much more.
if HTC doesn't present a 9.0 before Xmas i will definitely install AOSP instead with no google at all.
titimar16 said:
I try to flash GSI treble on HTC U11 Life but it doesn't work...
fastboot flash system_a /Users/thibautmaringer/Downloads/PixelExperienceP-arm64-ab.img
Sending sparse 'system_a' 1/3 (1048572 KB) OKAY [ 36.946s]
Writing sparse 'system_a' 1/3 (bootloader) HOSD CL#1033709
(bootloader) [email protected]
(bootloader) [email protected]%
FAILED ()
Finished. Total time: 111.730s
I don't understand...
Click to expand...
Click to collapse
You should place the system.img (gsi) in the same folder where your adb and fastboot installation is. And you can see on the display of your device the progress of writing from 0% to 100% maybe you can have a look at it next time you flash something to see if it flashes at all.
saturday_night said:
You should place the system.img (gsi) in the same folder where your adb and fastboot installation is. And you can see on the display of your device the progress of writing from 0% to 100% maybe you can have a look at it next time you flash something to see if it flashes at all.
Click to expand...
Click to collapse
I tried that but it stuck on "system_a O%" then my cmd says "failed()"
./fastboot flash system_a system.img
Sending sparse 'system_a' 1/2 (1048572 KB) OKAY [ 35.131s]
Writing sparse 'system_a' 1/2 (bootloader) HOSD CL#1033709
(bootloader) [email protected]
(bootloader) [email protected]%
FAILED ()
Finished. Total time: 115.146s
I think that we can't flash GSI like that with the HTC U11 Life
titimar16 said:
I tried that but it stuck on "system_a O%" then my cmd says "failed()"
./fastboot flash system_a system.img
Sending sparse 'system_a' 1/2 (1048572 KB) OKAY [ 35.131s]
Writing sparse 'system_a' 1/2 (bootloader) HOSD CL#1033709
(bootloader) [email protected]
(bootloader) [email protected]%
FAILED ()
Finished. Total time: 115.146s
I think that we can't flash GSI like that with the HTC U11 Life
Click to expand...
Click to collapse
It works that way, already did it three times with three different systems. What file are you using? Do you even have the android one version of the u11 life or the Sense version?
saturday_night said:
It works that way, already did it three times with three different systems. What file are you using? Do you even have the android one version of the u11 life or the Sense version?
Click to expand...
Click to collapse
2 GSI: pixelexperience and phh-treble because I want to install Android P on my phone. I have the one version. So I'm on stock Android 8.1.
The files:
https://github.com/phhusson/treble_experimentations/releases/tag/v104 (ab arm64)
https://forum.xda-developers.com/pr...ce-development/9-0-pixelexperience-p-t3833294 (ab arm64 v9.0.0.r1)
titimar16 said:
2 GSI: pixelexperience and phh-treble because I want to install Android P on my phone. I have the one version. So I'm on stock Android 8.1.
The files:
https://github.com/phhusson/treble_experimentations/releases/tag/v104 (ab arm64)
https://forum.xda-developers.com/pr...ce-development/9-0-pixelexperience-p-t3833294 (ab arm64 v9.0.0.r1)
Click to expand...
Click to collapse
Android 9 GSIs are in an very early development stage and if you would read their threads you would know this. I dont even try it until phh treble has its first stable release.
saturday_night said:
Android 9 GSIs are in an very early development stage and if you would read their threads you would know this. I dont even try it until phh treble has its first stable release.
Click to expand...
Click to collapse
Okay, Thank you. And what have you tried ?
titimar16 said:
Okay, Thank you. And what have you tried ?
Click to expand...
Click to collapse
Android 8.1 GSIs
Today i tested for the first time an Android 9 GSI, phh treble got an update yesterday with a lot of bug fixes and it looks pretty good so far. Sadly we have the same bugs as with Android 8.1 GSIs. Its the first time phh treble gsi android 9 has GApps + Root integrated. I think those bugs we have are related to a faulty treble integration by HTC and cant be fixed by a dev of a GSI but its running good so far.
saturday_night said:
Today i tested for the first time an Android 9 GSI, phh treble got an update yesterday with a lot of bug fixes and it looks pretty good so far. Sadly we have the same bugs as with Android 8.1 GSIs and one additional bug. Its not possible to connect to hidden wifi networks, as long as the networks ssid is visible there is no problem to connect to it. Its the first time phh treble gsi android 9 has GApps + Root integrated. I think those bugs we have are related to a faulty treble integration by HTC and cant be fixed by a dev of a GSI but its running good so far.
Click to expand...
Click to collapse
Hi. Sorry but for me it doesn't work again. I did all the steps:
1) unlock bootloader
2) I'm on stock 2.13.401.1
3) I flashed using fastboot flash system_a system.img (from phh-treble 9 GSI with su and gapps)
4) it says again
Code:
fastboot flash system_a /Users/thibautmaringer/Downloads/system.img
Sending sparse 'system_a' 1/2 (1048572 KB) OKAY [ 32.109s]
Writing sparse 'system_a' 1/2 (bootloader) HOSD CL#1033709
(bootloader) [email protected]
(bootloader) [email protected]%
FAILED ()
Finished. Total time: 109.315s
and on my phone it says "flash success 2/2 start flashing" but nothing happened.
So can you explain how you did that well because for me it doesn't work.
titimar16 said:
Hi. Sorry but for me it doesn't work again. I did all the steps:
1) unlock bootloader
2) I'm on stock 2.13.401.1
3) I flashed using fastboot flash system_a system.img (from phh-treble 9 GSI with su and gapps)
4) it says again
Code:
fastboot flash system_a /Users/thibautmaringer/Downloads/system.img
Sending sparse 'system_a' 1/2 (1048572 KB) OKAY [ 32.109s]
Writing sparse 'system_a' 1/2 (bootloader) HOSD CL#1033709
(bootloader) [email protected]
(bootloader) [email protected]%
FAILED ()
Finished. Total time: 109.315s
and on my phone it says "flash success 2/2 start flashing" but nothing happened.
So can you explain how you did that well because for me it doesn't work.
Click to expand...
Click to collapse
Hmm, there are just two things where i could imagin that it causes a problem for you. First if you try to flash stuff from bootloader and not from download mode. Second would be a problematic usb connnection during the flash process. I have no other ideas sorry.
saturday_night said:
Hmm, there are just two things where i could imagin that it causes a problem for you. First if you try to flash stuff from bootloader and not from download mode. Second would be a problematic usb connnection during the flash process. I have no other ideas sorry.
Click to expand...
Click to collapse
Do you have
Code:
secure boot: PRODUCTION
? Because my usb connection is good and I flash files in "htc download mode"
Maybe can you explain precisely how you flash the GSI ?
titimar16 said:
Do you have
Code:
secure boot: PRODUCTION
? Because my usb connection is good and I flash files in "htc download mode"
Maybe can you explain precisely how you flash the GSI ?
Click to expand...
Click to collapse
1. I remove my Google Account from the Stock System
2. Reboot to bootloader - reboot to recovery and factory reset the device
3. reboot to bootloader and identify the active partition
4. reboot to download mode
5. flash Stock boot.img (because i was rooted before)
6. flash GSI system.img
If you need it more in detail just read the first posts in these two threads: https://forum.xda-developers.com/u11-life/how-to/collection-htc-u11-life-android-one-t3768265 https://forum.xda-developers.com/u11-life/how-to/treble-gsi-running-android-one-8-1-t3823015
And yes i have secure boot production and device state unlocked
saturday_night said:
1. I remove my Google Account from the Stock System
2. Reboot to bootloader - reboot to recovery and factory reset the device
3. reboot to bootloader and identify the active partition
4. reboot to download mode
5. flash Stock boot.img (because i was rooted before)
6. flash GSI system.img
If you need it more in detail just read the first posts in these two threads: https://forum.xda-developers.com/u11-life/how-to/collection-htc-u11-life-android-one-t3768265 https://forum.xda-developers.com/u11-life/how-to/treble-gsi-running-android-one-8-1-t3823015
And yes i have secure boot production and device state unlocked
Click to expand...
Click to collapse
What's your GSI file and android version ? (I mean the entire like 2.12.401....)
titimar16 said:
What's your GSI file and android version ? (I mean the entire like 2.12.401....)
Click to expand...
Click to collapse
I used the Stock boot.img from 2.12.401.17 and phh treble GSI arm64 a/b gapps su... exactly this file https://github.com/phhusson/treble_...download/v105/system-arm64-ab-gapps-su.img.xz
saturday_night said:
1. I remove my Google Account from the Stock System
2. Reboot to bootloader - reboot to recovery and factory reset the device
3. reboot to bootloader and identify the active partition
4. reboot to download mode
5. flash Stock boot.img (because i was rooted before)
6. flash GSI system.img
If you need it more in detail just read the first posts in these two threads: https://forum.xda-developers.com/u11-life/how-to/collection-htc-u11-life-android-one-t3768265 https://forum.xda-developers.com/u11-life/how-to/treble-gsi-running-android-one-8-1-t3823015
And yes i have secure boot production and device state unlocked
Click to expand...
Click to collapse
saturday_night said:
I used the Stock boot.img from 2.12.401.17 and phh treble GSI arm64 a/b gapps su... exactly this file https://github.com/phhusson/treble_...download/v105/system-arm64-ab-gapps-su.img.xz
Click to expand...
Click to collapse
And did you change something about CID of MID ?
titimar16 said:
And did you change something about CID of MID ?
Click to expand...
Click to collapse
No, dont change anything, that can cause a lot of problems
Related
Hi,
I followed this article -> phandroid DOT com/2014/11/05/how-to-root-nexus-9/ (Sorry, new account, can't link) to the letter, and everything seemed to go well, until the last step where I ran "fastboot reboot" which returned "error: device not found" I thought nothing of this as there was a reboot option on the devices screen, so I rebooted, I get the google logo, followed by the four orbs, then it says "Optimising app x of 99" once this is done, its back to the orbs again and it just repeats.
I tried restoring to factory defaults from the recovery menu, that did nothing, then sometime after I noticed I actually cant turn the device off any more, if I hold the power button it turns off, but reboots instantly. I tried going through the steps again, but no luck, the only change was that I didn't have the error at the end, and the first Optimising dialogue said 104 apps, not 99, but all the rest afterwards have said 99.
I'm not sure what do do from here, any advice?
Here's my cmd output:
Code:
## First attempt ##
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb
reboot bootloader
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot oem unlock
...
(bootloader) ability is 1
(bootloader) RUU_frame_buffer_enable_flag=0
(bootloader) Start Verify: 0
(bootloader) [hboot query] query 24 is not implemented
(bootloader) [hboot query] query 24 is not implemented
(bootloader) Start Verify: 0
(bootloader) [hboot query] query 24 is not implemented
(bootloader) [hboot query] query 24 is not implemented
(bootloader) Unlock device successfully!
OKAY [ 23.489s]
finished. total time: 23.489s
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot boot inject.img
cannot load 'inject.img': No such file or directory
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot boot nexus9\inject.img
downloading 'boot.img'...
OKAY [ 0.783s]
booting...
OKAY [ 0.156s]
finished. total time: 0.939s
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot flash boot nexus9\patched.img
target reported max download size of 518205818 bytes
sending 'boot' (7830 KB)...
OKAY [ 0.541s]
writing 'boot'...
(bootloader) Device State : Unlocked
OKAY [ 0.798s]
finished. total time: 1.339s
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb
reboot
error: device not found
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb
reboot
error: device not found
## Second attempt ##
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot oem unlock
< waiting for device >
...
(bootloader) ability is 1
(bootloader) Device stete is unlock already
OKAY [ 0.141s]
finished. total time: 0.141s
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot boot inject.img
cannot load 'inject.img': No such file or directory
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot boot inject.img
downloading 'boot.img'...
OKAY [ 0.749s]
booting...
OKAY [ 0.158s]
finished. total time: 0.908s
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot flash boot patched.img
target reported max download size of 518205818 bytes
sending 'boot' (7830 KB)...
OKAY [ 0.539s]
writing 'boot'...
(bootloader) Device State : Unlocked
OKAY [ 0.787s]
finished. total time: 1.326s
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot reboot
rebooting...
finished. total time: 0.066s
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>
Try returning to stock and trying again. See method 2 of this, http://forum.xda-developers.com/showthread.php?p=58956577
Sent from my Nexus 9 using XDA Free mobile app
That root method is for the old 5.0 Android; it doesn't work anymore with 5.1.1. Go back to stock using jd1639's link, then run Chainfire's Auto-root and you should be good to go. Link is here: https://download.chainfire.eu/595/CF-Root/CF-Auto-Root/CF-Auto-Root-flounder-volantis-nexus9.zip. There's supposedly an update coming in the next week or so to fix the stagefright vulnerability, make sure you do NOT take it in case it does weird things that could cause you to lose root.
(I know it says Volantis and not flounder but the Nexus 9 is known by both names, just to keep things confusing)
Thanks guys, root is now all working
Had a strange way of getting there though, I went back to stock, then tried the auto root as mentioned, but I had the same problem again, so I re-flashed just the boot.img file from stock, powered up, and lo and behold, root working fine
TheShryke said:
Thanks guys, root is now all working
Had a strange way of getting there though, I went back to stock, then tried the auto root as mentioned, but I had the same problem again, so I re-flashed just the boot.img file from stock, powered up, and lo and behold, root working fine
Click to expand...
Click to collapse
Your better off doing the bootloader unlock, then flashing TWRP recovery, then flashing supersu. IMO using autoroot methods make no sense. You now have no recovery and if anything goes wrong you have to flash all of the factory images again. And what if you want to use a custom rom? I would highly recommend getting TWRP at http://twrp.me and flashing it. Then you can actually make full backups in case of disaster. Good luck!
bynarie said:
Your better off doing the bootloader unlock, then flashing TWRP recovery, then flashing supersu. IMO using autoroot methods make no sense. You now have no recovery and if anything goes wrong you have to flash all of the factory images again. And what if you want to use a custom rom? I would highly recommend getting TWRP at http://twrp.me and flashing it. Then you can actually make full backups in case of disaster. Good luck!
Click to expand...
Click to collapse
i'll try your TWRP method once i get my LTE version 32gb
link to bootloader unlock method? thx
which version do i use here?
https://dl.twrp.me/flounder/
cobyman7035 said:
i'll try your TWRP method once i get my LTE version 32gb
link to bootloader unlock method? thx
which version do i use here?
https://dl.twrp.me/flounder/
Click to expand...
Click to collapse
Hey, to unlock bootloader you enable developer settings in android, check the "enable oem unlock" switch, boot the device into fastboot mode "adb reboot fastboot" and issue "fastboot oem unlock". This is assuming you have adb and fastboot in your path/working folder. Then, download the lastest twrp - flounder-2.8.7.0.img - and "fastboot flash recovery flounder-2.8.7.0.img". The flounder version of twrp works for both LTE and WIFI variants. If you need any more assistance just let me know.
cobyman7035 said:
i'll try your TWRP method once i get my LTE version 32gb
link to bootloader unlock method? thx
which version do i use here?
https://dl.twrp.me/flounder/
Click to expand...
Click to collapse
bynarie said:
Hey, to unlock bootloader you enable developer settings in android, check the "enable oem unlock" switch, boot the device into fastboot mode "adb reboot fastboot" and issue "fastboot oem unlock". This is assuming you have adb and fastboot in your path/working folder. Then, download the lastest twrp - flounder-2.8.7.0.img - and "fastboot flash recovery flounder-2.8.7.0.img". The flounder version of twrp works for both LTE and WIFI variants. If you need any more assistance just let me know.
Click to expand...
Click to collapse
Just take notice that this will wipe everything on your device, so make a backup first.
dictionary said:
Just take notice that this will wipe everything on your device, so make a backup first.
Click to expand...
Click to collapse
cobyman7035 said:
...
Click to expand...
Click to collapse
Yes, my apologies... I forgot to mention this. You will definitely want to pull any pictures or other files you might want to keep from the /sdcard partition. Or anything else because ALL DATA WILL BE WIPED.
thx. where do i dload the latest SU chainfire? after i flash twrp, then flash SU? do i need to wipe dalvik or cache?
im installing that huge android SDK studio setup into my laptop for prep
cobyman7035 said:
thx. where do i dload the latest SU chainfire? after i flash twrp, then flash SU?
Click to expand...
Click to collapse
Here > https://download.chainfire.eu/740/SuperSU/BETA-SuperSU-v2.49.zip
ok i just unlocked my bootloader....so i rebooted in android again...i have to go back and enable usb debugging and developers again?
---------- Post added at 10:16 AM ---------- Previous post was at 10:01 AM ----------
when i typ adb reboot fastboot. ...my n9 reboots into the android o.s and NOT into fastboot?
---------- Post added at 10:23 AM ---------- Previous post was at 10:16 AM ----------
nm i installed and flash twrp and SU! i didn't do a dalvik cache wipe...is that ok? booting in android o/s again to setup!
my next step is to go unencrypted... don't wanna setup too many apps cuz its just gonna be all deleted again
My phone is stuck at the oneplus logo after trying to install the twrp-3.0.2-2_blu_spark.v41-onyx or stock recovery
I renames the file .twrp-3.0.2-2_blu_spark.v41-onyx into recovery.img.
My device is recognized with fastboot and tried to install twrp-3.0.2-2_blu_spark.v41-onyx
C:\adb>fastboot devices
b0d361e4 fastboot
C:\adb>fastboot oem unlock
...
OKAY [ 0.008s]
finished. total time: 0.008s
C:\adb>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device is_verified: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.070s]
finished. total time: 0.070s
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 1073741824 bytes
sending 'recovery' (15482 KB)...
OKAY [ 0.623s]
writing 'recovery'...
OKAY [ 0.562s]
finished. total time: 1.186s
C:\adb>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.619s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.685s
Then Installed stock Recovey and again the same problem.
No problems with installing twrp-3.0.2.0 or twrp-2.8.7.0.
At this moment I am stuck and don't know what to do next. I need your help guys!
What ROM or OOS are you on? Is your phone rooted?
What ROM or OOS are you on? Is your phone rooted?
Click to expand...
Click to collapse
OxygenOS 2.2.2 SuperSU v.2.78 Kernel blu_spark.OOS5.1.1 v164
Exodusche said:
What ROM or OOS are you on? Is your phone rooted?
Click to expand...
Click to collapse
OxygenOS 2.2.2 SuperSU v.2.78 Kernel blu_spark.OOS5.1.1 v164
liya123 said:
OxygenOS 2.2.2 SuperSU v.2.78 Kernel blu_spark.OOS5.1.1 v164
Click to expand...
Click to collapse
You really need to read my friend. Twrp V41 is for OOS3. It even is written in the file name. And also many posts on Blu spark thread . So what you need to do now is download Rashr from playstore and flash OOS2 recovery. Or probably fastboot but it MUST be Oxygen OS lollipop recovery. Once this is completed you can flash MM update with this stock recovery. Once OOS3 is booted you may flash TWRP V41.
Exodusche said:
You really need to read my friend. Twrp V41 is for OOS3. It even is written in the file name. And also many posts on Blu spark thread . So what you need to do now is download Rashr from playstore and flash OOS2 recovery. Or probably fastboot but it MUST be Oxygen OS lollipop recovery. Once this is completed you can flash MM update with this stock recovery. Once OOS3 is booted you may flash TWRP V41.
Click to expand...
Click to collapse
Thanks happened.
@Exodusche : I think you may have misunderstood something ; the filename of TWRP 3.0.2-2 is "twrp-3.0.2-2_blu_spark.v41-onyx_by-engstk.img", and thus nothing is said (as always) about the ROM installed on the phone. And this is for a good reason : Recovery is INDEPENDANT of the ROM installed (at the contrary of Kernel).
PS : I also encountered the same problem than Iilya123 when I tried installing TWRP 3.0.2-2 from Engstk. I had to reinstall from the TWRP app installed in my Temasek ROM the right proposed version, and from this new installed recovery, I flashed back the twrp-3.0.2-1_blu_spark...
S
suscrofa said:
@Exodusche : I think you may have misunderstood something ; the filename of TWRP 3.0.2-2 is "twrp-3.0.2-2_blu_spark.v41-onyx_by-engstk.img", and thus nothing is said (as always) about the ROM installed on the phone. And this is for a good reason : Recovery is INDEPENDANT of the ROM installed (at the contrary of Kernel).
PS : I also encountered the same problem than Iilya123 when I tried installing TWRP 3.0.2-2 from Engstk. I had to reinstall from the TWRP app installed in my Temasek ROM the right proposed version, and from this new installed recovery, I flashed back the twrp-3.0.2-1_blu_spark...
S
Click to expand...
Click to collapse
This recovery is designed to work with the new bootloader that is updated when you install OOS3. Unless you did that first, the phone doesn't understand how to boot this version of TWRP.
This guy had a good guide for flashing custom Roms when your on 3.0.1 or 3.1.1 community builds.
http://forum.xda-developers.com/showpost.php?p=68745907&postcount=283
Hi,
After upgrading the device to 3.1.3 the device is draining very fast and I didn't like the new changes.
Can anyone please share steps to downgrade the device to 2.2.2 OS?
I think it's easy, but somebody pls CMIIW, just flash the official TWRP via fastboot (prior to v41), reboot to TWRP, wipe cache, data, system, dalvik, and flash the OOS 2.2.2 zip file.
motherninja said:
I think it's easy, but somebody pls CMIIW, just flash the official TWRP via fastboot (prior to v41), reboot to TWRP, wipe cache, data, system, dalvik, and flash the OOS 2.2.2 zip file.
Click to expand...
Click to collapse
Thanks for your reply
I'm not familiar with few acronyms(CMIIW, TWRP). Could you please elaborate with steps?
Any reference link would also help.
No need to twrp.
Just reboot to recovery, wipe all tehn flash full 2.2.3 full rom zip.
you'll loose your settings and apps installed of course
NB : I think you should wait that 3.1.3 stabilize itself. What don't you like in OOS 3? All tastes exist, I know, but I can't see the point here....
Kéno40 said:
No need to twrp.
Just reboot to recovery, wipe all tehn flash full 2.2.3 full rom zip.
you'll loose your settings and apps installed of course
NB : I think you should wait that 3.1.3 stabilize itself. What don't you like in OOS 3? All tastes exist, I know, but I can't see the point here....
Click to expand...
Click to collapse
ok, I will try this step. If I go to recovery and do I need to download the rom or is it already there?
OOS 3 is buggy and draining out the battery of my device. Also, its making the device very slow.
amrinh said:
ok, I will try this step. If I go to recovery and do I need to download the rom or is it already there?
OOS 3 is buggy and draining out the battery of my device. Also, its making the device very slow.
Click to expand...
Click to collapse
No, you have to download it and put it in your device.
With a well parametred OOS 3 , my device never flyed so quickly.
You should start by going to apps, menus then reset apps parameters (there is a menu for that).
You can go to storage, click on internal storage and wipe cache data.
Reboot.
If still the same, instead of going backward, reflash full rom 3.1.3 zip
the best way to do it is flash bluSpark's TWRP, and then flash OOS 2.2.2
meraj99 said:
the best way to do it is flash bluSpark's TWRP, and then flash OOS 2.2.2
Click to expand...
Click to collapse
You should add that an unlocked bootloader is mandatory for that.
Be carefull, a lot of people (mainly the one that rooted via Kingroot) wiped theirs devices, going that way, without knowing it.
Hey there,
OnePlus recently published an Update for my OPX (Android 6.x). That update feels like the mother of all bugs (battery drain within minutes, no install/de-install options, no valid bootloader available,... ) which leads me to flash custom rom.
the device has been rooted successfully:
Code:
C:\adb>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.017s]
finished. total time: 0.017s
each version of TWRP-recovery images (2.8.xxx - 3.0.2) i am uploading is running successfully as well and leads to the output::
Code:
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (14758 KB)...
OKAY [ 0.531s]
writing 'recovery'...
OKAY [ 0.273s]
finished. total time: 0.811s
the problem is the next step. all versions of the above mentioned recovery-images result in:
Code:
C:\adb>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.531s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.580s
may anybody help me or tell me what i am doing wrong ,please?
any help is mostrly appreciated !
OnePlus: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display pan
Click to expand...
Click to collapse
Fastboot flash original stock recovery then 2.2.2. Bootloader downgraded and can continue flashing as normal.
thanks for that fast reply! i am now happy on "twrp-3.0.2-0-onyx.img" (recovery) and "cm-13.0-ZNH5Y-20160925-STABLE-Sultan-onyx.zip" (rom).
for everybody ekse running into the "dtb"-error:
i downgraded my opx by using that howto (google "opx unroot"):
https:[Double-slash]theunlockr[DOT]com/2016/02/17/how-to-unroot-the-oneplus-x/
i downloaded their recovery and rom and followed each step until (and excluding) "relock the bootloader".
after that i re-started flashing custom recovery and rom
Hi all,
Firstly, excuse my english...
I'm in OOS in version 2.1.3 (yea, old) with custom recovery and root. I have followed this guide : http://forum.xda-developers.com/oneplus-x/general/discussion-how-to-root-oneplus-x-t3242830
I have recently decided to upgrade in OOS 3.x and suprised...... Impossible to boot on TWRP.
$ adb reboot bootloader
Click to expand...
Click to collapse
→ fastboot mode OK
$ sudo fastboot devices
[sudo] Mot de passe de torlik :
4c6f1504 fastboot
Click to expand...
Click to collapse
detected, nice !
$ sudo fastboot boot twrp-2.8.7.0-onyx_f2fs_r9.img
downloading 'boot.img'...
OKAY [ 0.605s]
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.606s
Click to expand...
Click to collapse
WOOT ?
$ sudo fastboot flash recovery twrp-2.8.7.0-onyx_f2fs_r9.img
target reported max download size of 1073741824 bytes
sending 'recovery' (12130 KB)...
OKAY [ 0.684s]
writing 'recovery'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.686s
Click to expand...
Click to collapse
WHAT ?
With VOL- (+) POWER, I boot in Oxygen Recovery, nothing else.
$ sudo fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.006s]
finished. total time: 0.006s
Click to expand...
Click to collapse
(bootloader) Device unlocked: false
How my unlock has been lost ? My phone is yet rooted. SuperSu works correctly.
Can you tell me how it is possible to lost twrp ? I have never upgrade since my unlock.
And now, my only solution is to do a 'fastboot oem unlock' and lost my data ?
Thank you
Not sure whats going on there but easy way is to fastboot flash old stock recovery. Then install 3.1.3 with no problems. Rename file and delete .tar .
Your device bootloader is locked.
Why do you want to flash old TWRP.
To install OOS 3.1.3, you should better flash old OOS stock recovery.
But not sure it wil work.
Now, when you try to reboot recovery, on what recovery are you?
Always TWRP? None?
You should flash Oxygen one, so you can try to flash OOS 2.2.3 full rom zip to start.
Kéno40 said:
Your device bootloader is locked.
Why do you want to flash old TWRP.
To install OOS 3.1.3, you should better flash old OOS stock recovery.
But not sure it wil work.
Now, when you try to reboot recovery, on what recovery are you?
Always TWRP? None?
You should flash Oxygen one, so you can try to flash OOS 2.2.3 full rom zip to start.
Click to expand...
Click to collapse
Thanks for answers.
The issue is exactly that:
"Now, when you try to reboot recovery, on what recovery are you?"
I boot on stock recovery... oxygen recovery instead of twrp. Why?? How??
However I had flash my recovery with twrp last months ago and root my phone.
My problem is I do not want to lost my data... Indeed I can unlock again bootloader but all data will be lost.
How could you flash TWRP if your bootloader is locked? :-S
I don't think you ever get re-locked upon any update..
And yes, you probably have to unlock boot and lose all your user data.. Unless you don't have a backup handy of course :I
You can flash oos 3.1.1 through stock recovery no matter if your bootloader locked or unlocked.
Just download the full rom zip of oos 3.1.1 and place this zip in internal storage and flash with stock recovery. After installing oos3.1.1 you can backup your data and after that you have to go to the developer settings and allow the OEM Unlocking and now you can follow same procedure to unlock bootloader.
Every time I wanna flash Rom files with fastboot or adb side load
System partition failed to flash
even I have tried fastboot enhanced tool but it states all .img file is not logical even .img for stock rom.
Before using MSM tool I haven't faced this kinds of problems but once my device stuck in qualcom crush dump mode and I have to use MSM tool to unbrick my device and after that I think my partition type have changed and I can not flash any kind of rom. Every time I got the following error:
Invalid sparse file format at header magic
Sending sparse 'system_b' 1/5 (773795 KB) OKAY [ 17.926s]
Writing 'system_b' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Invalid sparse file format at header magic
My bootloader is unlocked
I have searched a lot and didn't got any solution and there are many users they are also facing the same problem but didn't got any solutions.
Does anyone know how to fix this problem?
Use adb reboot fastboot instead of adb reboot bootloader
御坂19041号 said:
Use adb reboot fastboot instead of adb reboot bootloader
Click to expand...
Click to collapse
Fastboot working fine here no issue with fastboot.
nowshadalve1 said:
Every time I wanna flash Rom files with fastboot or adb side load
System partition failed to flash
even I have tried fastboot enhanced tool but it states all .img file is not logical even .img for stock rom.
Before using MSM tool I haven't faced this kinds of problems but once my device stuck in qualcom crush dump mode and I have to use MSM tool to unbrick my device and after that I think my partition type have changed and I can not flash any kind of rom. Every time I got the following error:
Invalid sparse file format at header magic
Sending sparse 'system_b' 1/5 (773795 KB) OKAY [ 17.926s]
Writing 'system_b' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Invalid sparse file format at header magic
My bootloader is unlocked
I have searched a lot and didn't got any solution and there are many users they are also facing the same problem but didn't got any solutions.
Does anyone know how to fix this problem?
Click to expand...
Click to collapse
maybe on the wrong version or wrong recovery
dfm000 said:
maybe on the wrong version or wrong recovery
Click to expand...
Click to collapse
I have tried to flash fastboot stock rom also.....
Everytime says partition not found or volume full.
Look at the screenshot
nowshadalve1 said:
I have tried to flash fastboot stock rom also.....
Everytime says partition not found or volume full.
Click to expand...
Click to collapse
which oxygen os version you are on
dfm000 said:
which oxygen os version you are on
Click to expand...
Click to collapse
It's oos 11.2.7.7
After using MSM tool this problem appears before I can flash custom rom without any issue.
nowshadalve1 said:
It's oos 11.2.7.7
After using MSM tool this problem appears before I can flash custom rom withoutwh
Click to expand...
Click to collapse
which rom you trying to install
nowshadalve1 said:
It's oos 11.2.7.7
After using MSM tool this problem appears before I can flash custom rom without any issue.
Click to expand...
Click to collapse
use msm tool again to start fresh. update to version 11.2.8.8 from settings after that. use the recovery included with the rom provider. all should work well
dfm000 said:
use msm tool again to start fresh. update to version 11.2.8.8 from settings after that. use the recovery included with the rom provider. all should work well
Click to expand...
Click to collapse
I have tried this process so many times but still not working.
I can't fastboot any system Img any fix?
Every time I wanna flash Rom img files with fastboot System partition failed to flash Invalid sparse file format at header magic Sending sparse 'system_b' 1/5 (773795 KB) OKAY [ 17.926s] Writing 'system_b' FAILED (remote: 'Partition not...
forum.xda-developers.com
Check the link he also facing same problem...
nowshadalve1 said:
I have tried this process so many times but still not working.
I can't fastboot any system Img any fix?
Every time I wanna flash Rom img files with fastboot System partition failed to flash Invalid sparse file format at header magic Sending sparse 'system_b' 1/5 (773795 KB) OKAY [ 17.926s] Writing 'system_b' FAILED (remote: 'Partition not...
forum.xda-developers.com
Check the link he also facing same problem...
Click to expand...
Click to collapse
https://t.me/OnePlus9ROfficial ask here
Finally I got the solution :
1. update the oos to 11.2.8.8 from system updater.
2. Then unlock the bootloader. -> fastboot flashing unlock
3. Then flash custom recovery -> fastboot flash recovery recovery.img
4.Then enable adb sideload.
5. Then flash rom using-> adb sideload rom.zip
( After 47% it will show an error msg but don't worry)
6. Then back to recovery and formate user data.(most important otherwise you will stuck in bootloop and have to use msm tool)
7. Then reboot to system.
Done.
Who will face this problem on future follow the steps.
Thanks to https://t.me/OnePlus9ROfficial
And also thanks you bro @dfm000
im unable to enter fastboot mode after updating to OOS 12... anyone facing this issue?
gohaaron said:
im unable to enter fastboot mode after updating to OOS 12... anyone facing this issue?
Click to expand...
Click to collapse
Yes I was facing this issue also...you have to rollback to oos 11.
nowshadalve1 said:
Yes I was facing this issue also...you have to rollback to oos 11.
Click to expand...
Click to collapse
i have... so r u saying i need to root from OOS 11? my phone got bricked just now i had to use Msmtool to reflash back to OOS 11... but ive updated back to 12
Yes currently you need to root from oos 11. I don't weather you can root your device from oos 12 or not.
Ask here: https://t.me/OnePlus9ROfficial
And using MSM tool there is no big deal with Android 12. You will flash your device in edl mode so everything will be fine.
nowshadalve1 said:
Yes currently you need to root from oos 11. I don't weather you can root your device from oos 12 or not.
Ask here: https://t.me/OnePlus9ROfficial
And using MSM tool there is no big deal with Android 12. You will flash your device in edl mode so everything will be fine.
Click to expand...
Click to collapse
ok ive joined thanks
gohaaron said:
ok ive joined thanks
Click to expand...
Click to collapse
If you wanna rollback from 12 to 11 can follow this article:
Steps to Downgrade or Rollback Oneplus 8, 8 pro, 8T & 9R from Stable OxygenOS 12 to OxygenOS 11
Oneplus user are not happy about changes done on OxygenOS 12 for Oneplus 8, 8 pro, 8T & 9R. Now users want to downgrade to Stable.
techibee.in
nowshadalve1 said:
If you wanna rollback from 12 to 11 can follow this article:
Steps to Downgrade or Rollback Oneplus 8, 8 pro, 8T & 9R from Stable OxygenOS 12 to OxygenOS 11
Oneplus user are not happy about changes done on OxygenOS 12 for Oneplus 8, 8 pro, 8T & 9R. Now users want to downgrade to Stable.
techibee.in
Click to expand...
Click to collapse
yes i follow him too... but i saw him enter fastboot with OOS 12