Related
So me and Phhusson spent a good part of yesterday and today trying to get the Treble GSI to boot on the OnePlus 6 but no luck.
Only got the device recognised as Qualcomm HS-USB Diagnostics 900E (COM3), no ADB so no logcat
Which means no /system boot at all, black screen after the bootloader unlocked warning.
there are some dm-verity/fec errors, but using a modified vbmeta image did not change anything
If any other dev out here has any ideas you are welcome, me and phh are out of ideas.
PS, find here stock vendor, system and boot images, plus the dump of /sys/fs/pstore
https://drive.google.com/open?id=1J_sROd5AYVmvVTOGfMBuazoVWx4bSkTe
Update 1:
The black screen and no boot issue seems to be much more widespread and it's not specific to the Treble GSI, I have seen a lot of users experiencing the same exact behaviour when flashing other images too, even some stock images from OnePlus.
No clue yet about the exact cause, waiting for more devs to join in on this.
I assume you guys have contacted 1+?
Fingers crossed they could help
Same problem here.. No idea why OP6 boots into EDL mode when You try to boot Phh GSI. I noticed that sometimes when I boot into TWRP, it freezes and boots into EDL too.
Edit: And just like Exelios said, even with stock OP6 system.img it refuses to boot and boots into EDL instead.
ProtoDeVNan0 said:
Same problem here.. No idea why OP6 boots into EDL mode when You try to boot Phh GSI. I noticed that sometimes when I boot into TWRP, it freezes and boots into EDL too.
Edit: And just like Exelios said, even with stock OP6 system.img it refuses to boot and boots into EDL instead.
Click to expand...
Click to collapse
Yeah, you might have to re-flash the entire device with fastboot -w flashall, only way I got back to stock.
https://forum.xda-developers.com/showpost.php?p=76620386&postcount=60
Interesting...who knows what kind of weird stuff OnePlus did when implementing Treble. Did you try Updating to OnePlus Android P beta and going from there?
Exelios said:
Yeah, you might have to re-flash the entire device with fastboot -w flashall, only way I got back to stock.
https://forum.xda-developers.com/showpost.php?p=76620386&postcount=60
Click to expand...
Click to collapse
Managed to get it to boot after I used those commands (Thanks for telling me though )
fastboot flash boot_a
fastboot flash boot_b
fastboot flash system_a
fastboot flash system_b
fastboot flash vendor
fastboot -w flash vbmeta
And I used latest OOS zip from OP website. Just had to extract payload etc.
My guess is that we either need a different vbmeta or ramdisk is not compatible with our OP6. I never worked on A/B so it's all new to me. But I will do some "reverse engineering" soon. I'm surprised to see OP mess up Treble though, they are very developer friendly so why did they mess it up?
ProtoDeVNan0 said:
Managed to get it to boot after I used those commands (Thanks for telling me though )
fastboot flash boot_a
fastboot flash boot_b
fastboot flash system_a
fastboot flash system_b
fastboot flash vendor
fastboot -w flash vbmeta
And I used latest OOS zip from OP website. Just had to extract payload etc.
My guess is that we either need a different vbmeta or ramdisk is not compatible with our OP6. I never worked on A/B so it's all new to me. But I will do some "reverse engineering" soon. I'm surprised to see OP mess up Treble though, they are very developer friendly so why did they mess it up?
Click to expand...
Click to collapse
What I suspect is that the software is just unfinished, not messed up.
Here is the VBMETA.img that made it possible to boot on the pixel 2 xl, but causes the OP6 not to boot at all, not even stock system.
https://drive.google.com/open?id=1ifnXCIdkqKnk_a1HII9RqQd5CVFWz1xR
Bought and shipped a OP6 to Phhusson, hopefully he manages to figure out something with the device in his hands.
Are there really no other devs interested in getting this working? Just me and Phhusson?
Little update
Different OP6 devices are failing to boot differently, some go to EDL and some in PDL, when flashed the same files in the same way.
(Emergency Download Mode
Primary Download Mode)
Sent from my OnePlus 6 using XDA Labs
Hey buddy,
Not sure if you have seen this thread:
https://forum.xda-developers.com/oneplus-6/how-to/guide-how-to-flash-treble-roms-oneplus-6-t3797858
Is this what you're talking about?
Regards,
Ravi
Sent from my OnePlus6 using XDA Labs
See, I really wish I knew how to get started learning about Android Development like this, I would love to help lol.
I've tried dabbling in Custom ROMs but I don't know enough Java to add useful features lol, and even understanding the build system is kind of hard lol.
Like where would one go to learn how to make Treble ROMs boot and fix errors like this, and just dev stuff like this in general haha.
i was able to boot flashing boot_a, boot_b, system_a, system_b, vbmeta and vendor. i didn't used any dm-verify commands....
ps: it feels really smoother and snappier.... dont know why yet..... lol.....
TURBO
TURBO2012 said:
i was able to boot flashing boot_a, boot_b, system_a, system_b, vbmeta and vendor. i didn't used any dm-verify commands....
ps: it feels really smoother and snappier.... dont know why yet..... lol.....
TURBO
Click to expand...
Click to collapse
What are you talking about? Your screenshot shows stock ROM, not any of the GSI
Exelios said:
What are you talking about? Your screenshot shows stock ROM, not any of the GSI
Click to expand...
Click to collapse
My bad.... I flashed the files in OP. Thinking those were a gsi rom. Lol... My apologies.....
this is the correct one:
TURBO
This thread is almost 3 years old but leaving this here since it is the top google search for OnePlus 6 HS-USB Diagnostics 900E hopefully my solution in the link below helps someone else in the future.
[GUIDE] Mega Unbrick Guide for A Hard Bricked OnePlus 6
Similar to the previous threads for OnePlus 5 or OnePlus 5T, here are the necessary packages to unbrick/revive a hard bricked OnePlus 6. Download: https://www.androidfilehost.com/?w=files&flid=271466 OnePlus 6_180513_氢OS线刷包.rar After using it...
forum.xda-developers.com
Hi folks,
I'm in an odd situation, as my device is the EU 5G variant that before this mess, I believe was on the 10.0.3 OTA. From what I gather, this means fastboot images and MSM tools are scarce, and generally not available for my device. Like an idiot, I pressed on with trying to install the LineageOS 16 build from:
https://wiki.lineageos.org/devices/guacamole/install
For some reason, the LineageOS rom wouldn't flash through their recovery, so I tried some other ROMS I thought might be compatible to no avail.
After a series of mishaps, I managed to get TWRP to boot and formatted everything, including system. From then, I'm stuck in a bootloader loop without any kind of recovery or OS on either partition.
I can't fastboot boot any boot or recovery images, or fastboot flash boot. Everything just throws up the fastboot screen again, though I feel like this may just be a case of me not understanding the partitions.
I'm at a complete loss. I don't know how MSM tools work or if they exist for my variant.
How can I save my phone?
Thanks in advance
PM sent
Probably need to flash an entire fast boot rom and then wipe data.
Hey guys, I'm using Vsmart Joy2+ from Vsmart.
I want to install a custom gsi rom but it doesn't work. It said that " Image flashed completed" but it didn't boot up but suck in a boot loop.
I have tried to flash vbmeta, magisk, fastboot -w but it didn't work.
Can you guys help me?
1st thing of all things you should do is to add "Vsmart Joy2" to front of this thread's title what will prevent visitors to unnecessarily open this thread for reading.
Hi, I'd like to install Magisk and the various modules, but from what I've read there is not a twrp dedicated, I believe that my device might support the same work done via adb on the M40, the bootloader can be unlock easily from settings developer, therefore, I will understand come enter to fastboot without being too technical, maybe with the shell "Minimal ADB and Fastboot", I accept suggestions, thanks.
I don't know if there's TWRP (or others like it) for the Teclast M40 Pro, in wich case I'd instruct you to get the firmware (specifically system.img and/or boot.img) and either patch boot.img with the magisk app and flash it using fastboot or unpacking system.img and inserting a static su binary under sbin (this is very insecure and feature lacking) or manually installing magisk binaries and configs as it would if it ware done by TWRP, repacking and flashing.
now the former is nice and easy, infact, it's what topjohnwu himself reomends!
the latter... you'll be asking yourself why you even tried
Qwerty_in_me said:
I don't know if there's TWRP (or others like it) for the Teclast M40 Pro, in wich case I'd instruct you to get the firmware (specifically system.img and/or boot.img) and either patch boot.img with the magisk app and flash it using fastboot or unpacking system.img and inserting a static su binary under sbin (this is very insecure and feature lacking) or manually installing magisk binaries and configs as it would if it ware done by TWRP, repacking and flashing.
now the former is nice and easy, infact, it's what topjohnwu himself reomends!
the latter... you'll be asking yourself why you even tried
Click to expand...
Click to collapse
Hi, thanks, I could also try with the tool "Minimal Adb and Fastboot" that I used to flash the recovery. img on Xiaomi Mi 11 Ultra, I could also look for the stock firmware, for now I've only found the one with Android 10 on the HardReset site, the problem is that I can't boot into fastboot mode, even following the instructions by pressing power and volume down and releasing power as soon as the teclast logo appears, but continuing to press volume down, until the recovery mode appears, it doesn't appear and the tablet reboots in safe mode or aeroplane mode...
Oof, sounds like you're S out of L.
with MTK and Quallcomm devices this isn't a problem, they boot into BROM with an EDL USB connection and flash tools just work even with a corrupt bootloader.
never mind unisoc has it too: https://spdflashtool.com/ - it says it's for spreadtrum, but it's the same thing AFAIK
also try holding Vol+Up/Down/both and power for extended periods of time (if it boots android - reboot)
I really appreciate it, yes of course, UNISOC, formerly Spreadtrum, very interesting tool, so now (I have not done anything yet I'm just reading) I can download the drivers spd and with the tool possibly install boot.img modified by Magisk, although I do not know, exactly how to do it, I will learn! Thanks
Qwerty_in_me said:
Oof, sounds like you're S out of L.
with MTK and Quallcomm devices this isn't a problem, they boot into BROM with an EDL USB connection and flash tools just work even with a corrupt bootloader.
never mind unisoc has it too: https://spdflashtool.com/ - it says it's for spreadtrum, but it's the same thing AFAIK
also try holding Vol+Up/Down/both and power for extended periods of time (if it boots android - reboot)
Click to expand...
Click to collapse
Good morning, I've tried almost all the Hovatek methods within my reach, but with android 11 it's impossible to patch recovery.img because it doesn't exist in the stock rom, patching the boot.img is useless, editing the vbmeta-sign.img I haven't figured out how to do yet, so I'm back to square one. The only thing could be to downgrade with the Teclast M40 rom that is android 10, but I do not know if Spd Upgrade would allow me to flash with that rom, what do you think?
Hi,
Do you find a solution to root the M40 pro ?
Thanks
you could take a cue from these threads; extract the keys one by one from your vbmeta.sign and "assemble" your custom signed vbmeta.img
How to create a custom signed vbmeta.img for Unisoc using AVBtool
If you're into rooting and flashing custom recoveries then Android Verified Boot (AVB) or dmverity is something you should be aware of. We'd dropped a blog post on why dmverity could be causing your p
forum.hovatek.com
How to root the Teclast M40
The Teclast M40 runs on Android 10 Q and Unisoc T618 Processor. Rooting this model is pretty much like rooting the Teclast P80X except there are some important differences. Things to note when trying
forum.hovatek.com
S1ncr3six said:
you could take a cue from these threads; extract the keys one by one from your vbmeta.sign and "assemble" your custom signed vbmeta.img
How to create a custom signed vbmeta.img for Unisoc using AVBtool
If you're into rooting and flashing custom recoveries then Android Verified Boot (AVB) or dmverity is something you should be aware of. We'd dropped a blog post on why dmverity could be causing your p
forum.hovatek.com
How to root the Teclast M40
The Teclast M40 runs on Android 10 Q and Unisoc T618 Processor. Rooting this model is pretty much like rooting the Teclast P80X except there are some important differences. Things to note when trying
forum.hovatek.com
Click to expand...
Click to collapse
Did you get the M40 Pro rooting?
Enrique Ruiz said:
Hai ottenuto il rooting dell'M40 Pro?
Click to expand...
Click to collapse
i have unlocked bootloader but if i try to flash boot.img with magisk tablet go to loop
GigilinE said:
i have unlocked bootloader but if i try to flash boot.img with magisk tablet go to loop
Click to expand...
Click to collapse
Thank you very much for your answer friend
GigilinE said:
i have unlocked bootloader but if i try to flash boot.img with magisk tablet go to loop
Click to expand...
Click to collapse
Enrique Ruiz said:
Thank you very much for your answer friend
Click to expand...
Click to collapse
Hi guys.
No news from a possible root ? I had unlock the bootloader too only...
Thanks
I have bricked this device (One Plus Nord CE 2 Lite) by flashing the unofficial twrp image for this device. Device bootloops in TWRP.
Previously, I had succesfully unlocked the bootloader and rooted this device by flashing the patched magisk boot.img by following the method mentioned in this post (https://forum.xda-developers.com/t/rooting-oneplus-nord-2-ce-lite.4500297/)
How to restore the factory image and recover from this?
Any help is appreciated.
Thanks
...reboot to fastboot, flash the original boot and vbmeta and you're done ...maybe you have to change back the slot, but it's almost impossible to brick the device
...don't mess around with "Recovery" ...this device has already the newest partitioning system and there is no recovery partition
best regards
I messed up by flashing the wrong twrp image made. (Device was stuck on 1+ logo screen)
Thanks to your post i was able to rescue this device.
I used Oxygen Updater App, payload-dumper-gui and minimal adb fastboot.
Flashed boot and vbmeta with stock img files.
Restarting the device now will boot into fastboot mode.
Changing slots helped a lot.
(fastboot set-active=a/b)
After that, Device booted normally into OS.
... you're very welcome, Sir ...but really, don't mess around with "old school" recovery systems ...they are not needed anymore and furthermore they can't handle the "dynamic super partitioning" ...and again: nobody needs them after the year 2015 anymore
...best regards
NickR01 said:
I messed up by flashing the wrong twrp image made. (Device was stuck on 1+ logo screen)
Thanks to your post i was able to rescue this device.
I used Oxygen Updater App, payload-dumper-gui and minimal adb fastboot.
Flashed boot and vbmeta with stock img files.
Restarting the device now will boot into fastboot mode.
Changing slots helped a lot.
(fastboot set-active=a/b)
After that, Device booted normally into OS.
Click to expand...
Click to collapse
Hey can you help me pls, I am in the exact same situation as you but I can't get the stock img files, whenever I use payload-dumper it just gives me system.img and nothing else, could you maybe share your img files ?
Edit: I manged to get some files but still not the boot.img, I don't undestand why it just refuses to give them to me, I redownloaded everything at least 3 times...
Use Payload-Dumper-GUI instead of Payload-Dumper-Go
Hey @NickR01 if possible can you send me an boot.img and vbmeta
I don’t have windows pc so can’t use Payload-Dumper
It will also help future users to unbrick device.
NickR01 said:
Use Payload-Dumper-GUI instead of Payload-Dumper-Go
Click to expand...
Click to collapse
@vikas_anakin What's your device version?
cph2381 cph2409
NickR01 said:
@vikas_anakin What's your device version?
cph2381 cph2409
Click to expand...
Click to collapse
cph2381
@vikas_anakin I have files for eu variant, can't help you there bud. If flashed it can mess up your device.
If you are stuck with payload.bin extraction... try it with an android device.
Here's the tool for Android.
Payload-Dumper-Android
Here's the guide for it.
XDA Guide
Newb Guide
Follow the guide and download this app to extract the .bin file
Termux App: Termux Github
After the extraction, type fastboot (pc required) commands to flash and change current active slots from A to B if it's stuck in bootloop after flashing.
I hope this helps you recover your device.
NickR01 said:
@vikas_anakin I have files for eu variant, can't help you there bud. If flashed it can mess up your device.
If you are stuck with payload.bin extraction... try it with an android device.
Here's the tool for Android.
Payload-Dumper-Android
Here's the guide for it.
XDA Guide
Newb Guide
Follow the guide and download this app to extract the .bin file
Termux App: Termux Github
After the extraction, type fastboot (pc required) commands to flash and change current active slots from A to B if it's stuck in bootloop after flashing.
I hope this helps you recover your device.
Click to expand...
Click to collapse
Extracting the payload.bin is not an issue, The issue is I don't have stock firmware.
I used https://www.getdroidtips.com/oneplus-nord-ce-2-lite-5g-firmware-flash-file/ but my wifi and Bluetooth are not working after installing it.
Do you have any suggestions on how can i resolve these issues?
@vikas_anakin Download authentic firmware from this app. Files are pulled from OnePlus servers.
Google Playstore: Oxygen Updater
Oxygen Updater Settings -> Enable Advanced Mode
Select device region.
Latest update for holi is CPH2381_11_A.13 as of now.
I extracted the images from the payload.bin found in the Oxygen Updater file (that I had actually successfully used to update my device) and flashed 2 partitions:
fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
I then rebooted and now it's stuck in a boot loop & I can't even access fastboot anymore. Can someone please help?
Thanks
EDIT:
I managed to access fastboot & flash the rest of the partitions to fix it.
Hi everyone, just to piggy back on this thread, I also have the same device, and I have unofficial twrp and boot loader unlocked, however I have no back up rom and just want to get the phone back to normal really. Ive been following guides all over the place, but could someone point me in the right direction ? can I just download a rom for the OP nord ce 2 lite 5g, put it on my phone and have twrp install it? could someone guide me please. many thanks!
lemonmuffs said:
Hi everyone, just to piggy back on this thread, I also have the same device, and I have unofficial twrp and boot loader unlocked, however I have no back up rom and just want to get the phone back to normal really. Ive been following guides all over the place, but could someone point me in the right direction ? can I just download a rom for the OP nord ce 2 lite 5g, put it on my phone and have twrp install it? could someone guide me please. many thanks!
Click to expand...
Click to collapse
Yes, that will work.
vikas_anakin said:
Yes, that will work.
Click to expand...
Click to collapse
Or else you can extract img files from the oneplus rom file.
and flash them using fastboot.
Okay thank you for the reply, would you be able to point me to a official img file ? Or maybe someone has one extracted I could use please? I have looked online, but the ones I have gotten don't seem to work. I have also looked on the oneplus website for an official img but I could not find one.
So after a little more research, I can use another android device with the app Oxygen updater, download the full img.... So I am currently doing that and then ill try use fastboot or twrp to flash. Just wanted to spread info incase anyone else is having issues getting latest official roms for this device.
Hey guys, i have bricked my Oneplus Nord ce 2 lite 5g (Cph2381)
I tried using the fastboot enhance tool to flash a payload.bin file i thought was the right one for the device ..the device went to blackscreen..ive tried switching it on but its not working..ive done alittle research and found out that i should use an msm tool to force flash the initial stock firmware so that it can boot up ...problem is i cant seem to find the right msm tool for Oneplus nord ce 2 lite 5g , which msm tool can i use ? help please
Jazzyjuis said:
Hey guys, i have bricked my Oneplus Nord ce 2 lite 5g (Cph2381)
I tried using the fastboot enhance tool to flash a payload.bin file i thought was the right one for the device ..the device went to blackscreen..ive tried switching it on but its not working..ive done alittle research and found out that i should use an msm tool to force flash the initial stock firmware so that it can boot up ...problem is i cant seem to find the right msm tool for Oneplus nord ce 2 lite 5g , which msm tool can i use ? help please
Click to expand...
Click to collapse
Hey man, I would suggest not going with msm tool or anything.
Just download the latest update file of your device using oneplus updater app, or you can ask for the file if some of your friends has the same device.
use this tool to extract payload files https://github.com/vm03/payload_dumper
Now you can follow the same procedure as here https://forum.xda-developers.com/t/...ock-oxygenos-firmware-on-oneplus-10r.4465077/