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
Related
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.
Hi Friends...
my phone had an unlocked bootloader with custom recovery sultan's TWRP 3.02
and recently i installed stock oxygenOS flashable zip 3.1.4 version..
everything was fine..
today i tried to install cyanogenmod 14 nightly build..
i downloaded the zip , gapps pico , superSu 2.78
went into twrp -> factory reset -> advanced-> wipe everything...
flashed os -> gapps -> super su and rebooted ..
after that my phone got stuck in oneplus logo for quite a long time ..so i switched it off and tried to switch On again..
.............................................bootloop...........................................
showed oneplus logo blinked again vibrated oneplus logo............it didnt boot up
i cant go into the newly installed OS ..and the recovery didnt boot also..
but fastboot worked though...
i tried to reflash the sultan recovery again ..using fastboot commands ..it got flashed but cant boot ...
then i tried to install original oxygen recovery MM version ..
later it showed the error that my device is not unlocked and cannot flash or erase...
i have told everything i did ..its my favorite phone ..one and only........
please help me guys...!!
prasannazx said:
Hi Friends...
my phone had an unlocked bootloader with custom recovery sultan's TWRP 3.02
and recently i installed stock oxygenOS flashable zip 3.1.4 version..
everything was fine..
today i tried to install cyanogenmod 14 nightly build..
i downloaded the zip , gapps pico , superSu 2.78
went into twrp -> factory reset -> advanced-> wipe everything...
flashed os -> gapps -> super su and rebooted ..
after that my phone got stuck in oneplus logo for quite a long time ..so i switched it off and tried to switch On again..
.............................................bootloop...........................................
showed oneplus logo blinked again vibrated oneplus logo............it didnt boot up
i cant go into the newly installed OS ..and the recovery didnt boot also..
but fastboot worked though...
i tried to reflash the sultan recovery again ..using fastboot commands ..it got flashed but cant boot ...
then i tried to install original oxygen recovery MM version ..
later it showed the error that my device is not unlocked and cannot flash or erase...
i have told everything i did ..its my favorite phone ..one and only........
please help me guys...!!
Click to expand...
Click to collapse
Use mega unbrick guide if you tried all other procedure.
I was caught up in the same situation. Follow the mega unbrick guide and your phone will be back to normal.
link to the mega unbrick please..
Asmmahin said:
link to the mega unbrick please..
Click to expand...
Click to collapse
Here you go
http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
Is mega unbrick or hard unbrick is same ?
amgh said:
Is mega unbrick or hard unbrick is same ?
Click to expand...
Click to collapse
Both are same.some call it hard unbrick or some mega that's it.
1.) Make sure driver signature enforcement is disabled.
2) Download this :- http://www.mediafire.com/download/4aqwyi3g1d6wc67/Qualcomm 1.00.11.rar
Keep phone disconnected from PC.
Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
Run the Qualcomm setup wizard (also located in the qc folder)
When completed, restart your PC again with Driver Signature Disabled. (Optional but preferred)
4) press vol up button for 10s and plug it in pc keeping pressed
The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install.
5) now flash it with msmtool u can downloa th 47mb one in comments
http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
6) the phone now should have the stock recovery
---------- Post added at 10:08 PM ---------- Previous post was at 10:07 PM ----------
sabrinano24 said:
1.) Make sure driver signature enforcement is disabled.
2) Download this :- http://www.mediafire.com/download/4aqwyi3g1d6wc67/Qualcomm 1.00.11.rar
Keep phone disconnected from PC.
Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
Run the Qualcomm setup wizard (also located in the qc folder)
When completed, restart your PC again with Driver Signature Disabled. (Optional but preferred)
4) press vol up button for 10s and plug it in pc keeping pressed
The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install.
5) now flash it with msmtool u can downloa th 47mb one in comments
http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
6) the phone now should have the stock recovery
Click to expand...
Click to collapse
ps= remove the space in the frist link
Ok so i've the same problem but my phone can't boot after fix the brick it's the same:
C:\Android>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.017s]
finished. total time: 0.019s
C:\Android>fastboot flash recovery recovery.img
target reported max download size of 1073741824 bytes
sending 'recovery' (15920 KB)...
OKAY [ 0.507s]
writing 'recovery'...
OKAY [ 0.303s]
finished. total time: 0.817s
C:\Android>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.516s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.556s
Bjr49000 said:
Ok so i've the same problem but my phone can't boot after fix the brick it's the same:
C:\Android>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.017s]
finished. total time: 0.019s
C:\Android>fastboot flash recovery recovery.img
target reported max download size of 1073741824 bytes
sending 'recovery' (15920 KB)...
OKAY [ 0.507s]
writing 'recovery'...
OKAY [ 0.303s]
finished. total time: 0.817s
C:\Android>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.516s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.556s
Click to expand...
Click to collapse
did you install a rom after the fix ?
After fix, it's the official ROM so déveloper > OEM and USB debuging
adb reboot bootloader
Adb oem unlock ans After the command i write
prasannazx said:
Hi Friends...
my phone had an unlocked bootloader with custom recovery sultan's TWRP 3.02
and recently i installed stock oxygenOS flashable zip 3.1.4 version..
everything was fine..
today i tried to install cyanogenmod 14 nightly build..
i downloaded the zip , gapps pico , superSu 2.78
went into twrp -> factory reset -> advanced-> wipe everything...
flashed os -> gapps -> super su and rebooted ..
after that my phone got stuck in oneplus logo for quite a long time ..so i switched it off and tried to switch On again..
.............................................bootloop...........................................
showed oneplus logo blinked again vibrated oneplus logo............it didnt boot up
i cant go into the newly installed OS ..and the recovery didnt boot also..
but fastboot worked though...
i tried to reflash the sultan recovery again ..using fastboot commands ..it got flashed but cant boot ...
then i tried to install original oxygen recovery MM version ..
later it showed the error that my device is not unlocked and cannot flash or erase...
i have told everything i did ..its my favorite phone ..one and only........
please help me guys...!!
Click to expand...
Click to collapse
That is because the kernel and boot loader used for 14.1 is different you need to update the kernel.
Follow Mega unbrick guide carefully to unbrick the phone.
sabrinano24 said:
did you install a rom after the fix ?
Click to expand...
Click to collapse
After the fix, i've OOS, and that all.
Bjr49000 said:
Ok so i've the same problem but my phone can't boot after fix the brick it's the same:
C:\Android>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.017s]
finished. total time: 0.019s
C:\Android>fastboot flash recovery recovery.img
target reported max download size of 1073741824 bytes
sending 'recovery' (15920 KB)...
OKAY [ 0.507s]
writing 'recovery'...
OKAY [ 0.303s]
finished. total time: 0.817s
C:\Android>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.516s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.556s
Click to expand...
Click to collapse
I had same issue you need to flash different TWRP. If your on 2.X.X TWRP 3.0.2 . If you have updated to 3.X.X then 3.0.3. If you have issues with 3.0.3 you can try twrp 3.0.2-0 or bluesparks 3.0.2-1 V41.
just flash the arsenic-kernel everything will be fine.. https://forum.xda-developers.com/oneplus-x/development/kernel-arsenic-kernel-r2-t3422020
The problem is not the kernel but the bootloader so how to change/update recovery?
Bjr49000 said:
The problem is not the kernel but the bootloader so how to change/update recovery?
Click to expand...
Click to collapse
If you did not unlocked bootloader properly then also you might face the problem...
to unlock bootloader: https://forum.xda-developers.com/oneplus-x/general/discussion-how-to-root-oneplus-x-t3242830
make sure you follow all the step. (If you didn't followed these steps then lock bootloader {fastboot oem lock} and unlock using this mathod.)
Falsh this kernal after flashing rom and gapps, https://forum.xda-developers.com/oneplus-x/development/kernel-arsenic-kernel-r2-t3422020
Don't forget to hit :good:
Bjr49000 said:
Ok so i've the same problem but my phone can't boot after fix the brick it's the same:
C:\Android>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.017s]
finished. total time: 0.019s
C:\Android>fastboot flash recovery recovery.img
target reported max download size of 1073741824 bytes
sending 'recovery' (15920 KB)...
OKAY [ 0.507s]
writing 'recovery'...
OKAY [ 0.303s]
finished. total time: 0.817s
C:\Android>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.516s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.556s
Click to expand...
Click to collapse
I used to have this problem. You need to flash the new bootloader, sometimes updates and whatnot doesn't flash it for you. If the zip doesn't work you can try finding the fastboot partition image and flashing to aboot (instead of fastboot flash recovery recovery.img when flashing a twrp build for example, it would be fastboot flash aboot emmc_appsboot.mbn). There was a post on the oneplus forums where the files could be found, just google dtb not found error.
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
I tried to install lineage OS 17.1 on a Moto-Z with Android 6.0.1, and failed.
Here is one error I'd like to solve - this command:
fastboot flash recovery twrp-3.3.1-0-griffin.img
Results in:
(bootloader) has-slot:recovery: not found
(bootloader) is-logical:recovery: not found
Sending 'recovery' (20536 KB) OKAY [ 0.443s]
Writing 'recovery' (bootloader) Image not signed or corrupt
OKAY [ 0.481s]
Finished. Total time: 0.932s
twrp-3.3.1-0-griffin.img is the lastest image, from here.
The same error appears when I try to flash the lineage recovery:
fastboot flash recovery lineage-17.1-20201211-recovery-griffin.img
So what is wrong here?
I've been flashing a Moto e5 Plus today, and the ADB messages were the same, except without the "has slot" line. I think they are standard.
I also had trouble getting TWRP to "stick". What ended up working was booting into the bootloader, flashing TWRP and instead of rebooting I selected "recovery" with the volume buttons.
The TWRP site says this in its instructions:
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Click to expand...
Click to collapse
but holding Power + Volume Up after reboot didn't seem to work for me.
mfs-ness said:
What ended up working was booting into the bootloader, flashing TWRP ...
Click to expand...
Click to collapse
How did you flash TWRP - from the bootloader?
Or from the PC via fastboot - in which case there is always the above error, not just with TWRP images.
This is how I flashed TWRP from a linux desktop:
Code:
./adb -d reboot bootloader
sudo ./fastboot flash recovery ~/Downloads/twrp-3.4.0-0-hannah.img
(bootloader) is-logical:recovery: not found
Sending 'recovery' (19798 KB) OKAY [ 0.795s]
Writing 'recovery' (bootloader) Image not signed or corrupt
OKAY [ 0.552s]
Finished. Total time: 1.352s
The first line results in the screen with the open-chested android. Then I ran the fastboot command. Then I selected "recovery mode" on the phone.
mfs-ness said:
This is how I flashed TWRP from a linux desktop:
...
Click to expand...
Click to collapse
Not different from my technique.
So we seem to have different conditions on the phone, firmware, whatever.