Related
twrp does not show up in recovery mode. need help with this . Thanks to all.
Follow the instructions from the same place you got the download link?
Thanks, I could not find what page I was on for that. If someone knows how I can do this let me know. Thanks.
and what about the dual partitions on the pixel. am I booting in to the wrong one for this to happen?.
You "fastboot boot" a twrp image for a one-time use. If you want it to stick as you describe, then you flash the twrp zip from within the temp twrp session which flashes it to both slots and will remain after reboots.
OK can you help me to do this?.
I try that, not working.
need step by step for the pixel2. thanks.
Is all here my friend but you have to be willing to look and learn. It sounds like you need to do some reading. This post has some detailed walk through info:
https://forum.xda-developers.com/pixel-2/how-to/guide-unlock-flash-root-pixel-2-walleye-t3702417
It sounds like you might benefit from some research/practice with fastboot as well.
Thanks, you may be right.
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
I have not one, but two bricks. I bought one to unbrick the other, but the reverse happened. Using the EDL tool from this forum, I made a full and then an all backup and tried to use it to unbrick the other. No success. Now I cannot enter fastboot on either device, but both will enter EDL. I think at least one will fastboot if I can switch the active a/b slot.
Can the active a/b slot be switched via a command in the edl mode? Or is there another way to switch the active slot on a brick without fastboot access? Thank you
I already had that you have to put in the edl tool Then unlock bootloader and then you can go back to fastboot mode, it is because the files abl.elf have to be flashed to have fastboot
but to avoid the brick you have to flash all then boot the mobile phone and best an official Rom flash then back ...in edl Tool .... if you have an A2020G the 1.6 edl firmware helps you continue flashing and then you can lineage OS and then everything else flash what you want
Here ist the Link of 1.6 A2020Gpro Firmware: yadi.sk/d/0d8uKQ1nEd8ZVA
noobstyle1337 said:
I already had that you have to put in the edl tool Then unlock bootloader and then you can go back to fastboot mode, it is because the files abl.elf have to be flashed to have fastboot
but to avoid the brick you have to flash all then boot the mobile phone and best an official Rom flash then back ...in edl Tool .... if you have an A2020G the 1.6 edl firmware helps you continue flashing and then you can lineage OS and then everything else flash what you want
Here ist the Link of 1.6 A2020Gpro Firmware: yadi.sk/d/0d8uKQ1nEd8ZVA
Click to expand...
Click to collapse
Thank you for your answer.
I have tried flashing both phones with the following:
1) Full edl from newly purshased phone with v1.1
2) All edl from newly purchased phone with v1.1
3) A2020G v1.6 pro firmware
4) Several other firmwares which the edl would not accept as valid.
None of these worked. Actually, they made things worse. I cannot not even get to fastboot anymore. They both used to give a splash screen that quickly looped. Even that is now gone. Pressing any combination of buttons results in absolutely nothing or edl mode.
The only conclusion that I can make is one of two things:
1) Bricked both all hope
2) edl flashes that I am using are set up for A slot, when the phone is trying to use B slot. I thought when one slot was unbootable it would automatically switch to the other but that doesn't seem to be happening.
Does anyone know of a way to force the phone to boot to the other slot from edl mode? OR some flag that I can edit to switch the slots? OR some command that I can issue to switch slots using fh_loader.exe or emmcdl.exe or another edl tool?
There's no command to switch active slots that I know of and I've gone into the source on fh_loader.
What phone version do you have? Is there some reason you didn't download the EDL tools I uploaded recently instead? The original EDL tool has a few bugs. Read the newer EDL tool thread for some helpful information related to unbricking.
The fact that you aren't getting a ZTE logo at all indicates that you do not have a mixed up slot a/b situation anyway. It probably means you need to fix your AOP files. Of course the original EDL tool doesn't really let you do that. If you have the US version you can use the tools I uploaded to target just the AOP files and try restoring them from your original backup... either the a or b slot one should work.
Make sure you keep your original ALL/FULL backups (both) from the EDL tool, they're probably 99% good and you'll be doing yourself a favor not to delete or modify them.
groundslug said:
Thank you for your answer.
I have tried flashing both phones with the following:
1) Full edl from newly purshased phone with v1.1
2) All edl from newly purchased phone with v1.1
3) A2020G v1.6 pro firmware
4) Several other firmwares which the edl would not accept as valid.
None of these worked. Actually, they made things worse. I cannot not even get to fastboot anymore. They both used to give a splash screen that quickly looped. Even that is now gone. Pressing any combination of buttons results in absolutely nothing or edl mode.
The only conclusion that I can make is one of two things:
1) Bricked both all hope
2) edl flashes that I am using are set up for A slot, when the phone is trying to use B slot. I thought when one slot was unbootable it would automatically switch to the other but that doesn't seem to be happening.
Does anyone know of a way to force the phone to boot to the other slot from edl mode? OR some flag that I can edit to switch the slots? OR some command that I can issue to switch slots using fh_loader.exe or emmcdl.exe or another edl tool?
Click to expand...
Click to collapse
You can only change the slots if you are in Fastboot. You have doing it wrong ... if you have an A2020G you can flash the firmware ... if you have the A2020u version then you should ... flash the correct one
so in itself quite simple .... flash edl firmware and then unlock .. then you boot into the fastboot mode and then you have to use these lines
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Then
fastboot --set-active=a
in any case you have to unlock to access the fastboot menu
then you should be able to boot
---------- Post added at 04:39 PM ---------- Previous post was at 04:36 PM ----------
remember to flash Android 9 edl firmware because otherwise the unlock won't work
---------- Post added at 04:47 PM ---------- Previous post was at 04:39 PM ----------
also remember that some firmwares have to be in the flash folder or in the backup folder if it doesn't work
bobthenormal said:
What phone version do you have? Is there some reason you didn't download the EDL tools I uploaded recently instead? The original EDL tool has a few bugs. Read the newer EDL tool thread for some helpful information related to unbricking.
Click to expand...
Click to collapse
A2020U on both.
Many thanks for your edl tools! The problem was at least very close to what I thought. Active slot a. Fix bootable partition on your edl tools brought both back to their previous state. (This a/b slot scheme is intentionally over complicated and for modders makes bricks instead of preventing them.) The newly purchased phone is now unlocked and bootable into v1.1. I will proceed with lineage next. The old phone is still a brick with a locked bootloader, but it has fastboot now. I keep you posted. Other life duties call at the moment. Thanks!
groundslug said:
A2020U on both.
Many thanks for your edl tools! The problem was at least very close to what I thought. Active slot a. Fix bootable partition on your edl tools brought both back to their previous state. (This a/b slot scheme is intentionally over complicated and for modders makes bricks instead of preventing them.) The newly purchased phone is now unlocked and bootable into v1.1. I will proceed with lineage next. The old phone is still a brick with a locked bootloader, but it has fastboot now. I keep you posted. Other life duties call at the moment. Thanks!
Click to expand...
Click to collapse
It's great to hear I was able to help save from that terrible bricked feeling!
For the 2nd phone - you can try this to unlock it manually without getting it to boot... First do a full backup using my EDL tool. Then use the "FRP" tool I included to write an "unlocked" version of the FRP partition. Then go into fastboot and do the unlock manually - I think it's "fastboot flashing unlock".. but just search to make sure that's right.
Otherwise.. I'm slow but I'll eventually upload the locked stock ROMs.
bobthenormal said:
It's great to hear I was able to help save from that terrible bricked feeling!
For the 2nd phone - you can try this to unlock it manually without getting it to boot... First do a full backup using my EDL tool. Then use the "FRP" tool I included to write an "unlocked" version of the FRP partition. Then go into fastboot and do the unlock manually - I think it's "fastboot flashing unlock".. but just search to make sure that's right.
Otherwise.. I'm slow but I'll eventually upload the locked stock ROMs.
Click to expand...
Click to collapse
Both are unlocked now, thank you!
I am still having trouble getting lineage OS to go though. Here's the steps I follow:
1) Fashboot flash twrp from here. https://www.mediafire.com/folder/ha8j5crsdmbmx/ZTE_Axon_10_pro_stuff
2) Fastboot flash vbmeta from here. https://www.mediafire.com/folder/ha8j5crsdmbmx/ZTE_Axon_10_pro_stuff
3) Boot to twrp.
4) Twrp flash lineage 16 OS. Tried both from here. http://samson.nwwn.net/~unjust/Axon 10 Pro/LineageOS/
5) Twrp flash lineage 16 OS root addon arm64 from here. https://download.lineageos.org/extras
6) Wipe data and cache.
This results in the previous state in which only edl, no fastboot is available. So I flash my all backup using the edl tools and I am back to the beginning. I must be missing a step???
EDIT: I also tried restoring aop and uefisecapp files via edl after above steps as suggested in your readme. Same with vbmeta. Again, edl only, no fastboot.
groundslug said:
Both are unlocked now, thank you!
I am still having trouble getting lineage OS to go though. Here's the steps I follow:
1) Fashboot flash twrp from here. https://www.mediafire.com/folder/ha8j5crsdmbmx/ZTE_Axon_10_pro_stuff
2) Fastboot flash vbmeta from here. https://www.mediafire.com/folder/ha8j5crsdmbmx/ZTE_Axon_10_pro_stuff
3) Boot to twrp.
4) Twrp flash lineage 16 OS. Tried both from here. http://samson.nwwn.net/~unjust/Axon 10 Pro/LineageOS/
5) Twrp flash lineage 16 OS root addon arm64 from here. https://download.lineageos.org/extras
6) Wipe data and cache.
This results in the previous state in which only edl, no fastboot is available. So I flash my all backup using the edl tools and I am back to the beginning. I must be missing a step???
EDIT: I also tried restoring aop and uefisecapp files via edl after above steps as suggested in your readme. Same with vbmeta. Again, edl only, no fastboot.
Click to expand...
Click to collapse
Just replying real quick since I have a min and I saw a few things you can try... 1. make sure you're installing twrp itself with the zip after you boot into it with fastboot, 2. use the two flags when you write vbmeta just in case (I forget them but one is dm verify and the other is no verity, should be in the original LOS16 thread) and 3. try the fix bootable partition tool from my tools after you install. the LOS16 image has a similar problem as all other images that it has a specific slot it works on (B I think) so if you end up installing and trying to boot it from the other slot it locks into a fast bootloop. Don't bother installing the addons until LOS is booting, so just do a reboot to system after you flash it, fix bootable. If it doesn't boot then it has to be something I'm not thinking of. Goodluck!
It's been a while, but I wanted to follow up.
I did finally get lineage working. The two things that I was missing:
1) Fastboot to flash boot partition with los-twrp-magisked-boot.img
There is another file named twrp-magisked-los-boot.img that did NOT work for.
A third file named Magisk20.3-twrp.img would appear to be yet a third option for flashing boot. I did not try it because I had a working boot.
All three files can be found at link already given: https://www.mediafire.com/folder/ha8j5crsdmbmx/ZTE_Axon_10_pro_stuff
2) Fastboot to flash system partition with system.img
I used python and a python module called payload dumper (use google to find tutorial) to extract the .img files from the lineage 16 zip file.
This gave me 5 files.
boot.img - Did not use. See #1
dtbo.img - Flashing it led to a brick, if I remember right. Do not use.
system.img - Yes!
vendor.img - I flashed it too, but I do not think it is necessary.
vbmeta.img - Did not use. Use vbmeta disabled as noted above.
I use the lineage 16 dated 20191029 that used to be available at the following link. It appears to be dead as of today. Maybe will return.
http://samson.nwwn.net/~unjust/Axon%2010%20Pro/
Other versions of lineage will probably work with this method, but I can not say for sure.
In summary, use fashboot to flash los-twrp-magisked-boot.img and system.img. Obtain boot from link above. Obtain system from python module payload dumper from lineage 16 zip file. See other threads on this forum for details regarding unlocking bootloader with EDL tools and how to make vbmeta disabled. Hope this helps someone avoid the headaches I had!
groundslug said:
It's been a while, but I wanted to follow up.
I did finally get lineage working. The two things that I was missing:
1) Fastboot to flash boot partition with los-twrp-magisked-boot.img
There is another file named twrp-magisked-los-boot.img that did NOT work for.
A third file named Magisk20.3-twrp.img would appear to be yet a third option for flashing boot. I did not try it because I had a working boot.
All three files can be found at link already given: https://www.mediafire.com/folder/ha8j5crsdmbmx/ZTE_Axon_10_pro_stuff
2) Fastboot to flash system partition with system.img
I used python and a python module called payload dumper (use google to find tutorial) to extract the .img files from the lineage 16 zip file.
This gave me 5 files.
boot.img - Did not use. See #1
dtbo.img - Flashing it led to a brick, if I remember right. Do not use.
system.img - Yes!
vendor.img - I flashed it too, but I do not think it is necessary.
vbmeta.img - Did not use. Use vbmeta disabled as noted above.
I use the lineage 16 dated 20191029 that used to be available at the following link. It appears to be dead as of today. Maybe will return.
http://samson.nwwn.net/~unjust/Axon%2010%20Pro/
Other versions of lineage will probably work with this method, but I can not say for sure.
In summary, use fashboot to flash los-twrp-magisked-boot.img and system.img. Obtain boot from link above. Obtain system from python module payload dumper from lineage 16 zip file. See other threads on this forum for details regarding unlocking bootloader with EDL tools and how to make vbmeta disabled. Hope this helps someone avoid the headaches I had!
Click to expand...
Click to collapse
Thanks a lot! I'm stuck in the same spot, I have the solutions but I can't connect fully with sahara or qpst? Is this why you went with the payload dumper? Sorry I'm unfamiliar but I'm up to use it.
Rise55Chrom said:
Thanks a lot! I'm stuck in the same spot, I have the solutions but I can't connect fully with sahara or qpst? Is this why you went with the payload dumper? Sorry I'm unfamiliar but I'm up to use it.
Click to expand...
Click to collapse
By sahara, you mean the EDL protocol, yes? (I am not familar with qpst.) Are you using the EDL tools published by unjustified and bobthenormal on this forum? I had problems with the sahara protocol too when adding the firehose. I initially fixed it by opening the back case and disconnecting and reconnecting the battery connector. That's a big headache, especially if you don't already have the back case open. (I had it open because I had previously replaced the screen.) I found that to be unnecessary. If you press all three buttons to enter EDL mode, just press them again and again until the sahara works and the firehose goes in.
Regarding payload dumper, I used it simply because nothing else gave me a bootable phone. I did use the EDL tools to unlock the bootloader and to set the active slot (only bobthenormal's EDL tools will set the active slot).
Here's the payload dumper tutorial that worked for me.
Extract Android OTA Payload.bin File using Payload Dumper Tool
Learn how to dump and extract Android OTA Payload.bin file to get the boot.img (for rooting with Magisk), vendor.img, and other other partition images.
www.thecustomdroid.com
Don't forget to flash los-twrp-magisked-boot.img and vbmeta disabled as noted above. Also, if you use this method, let me know if it was necessary for you to flash vendor.img. Above all, do a complete backup via the EDL tools before making any other changes!
groundslug said:
By sahara, you mean the EDL protocol, yes? (I am not familar with qpst.) Are you using the EDL tools published by unjustified and bobthenormal on this forum? I had problems with the sahara protocol too when adding the firehose. I initially fixed it by opening the back case and disconnecting and reconnecting the battery connector. That's a big headache, especially if you don't already have the back case open. (I had it open because I had previously replaced the screen.) I found that to be unnecessary. If you press all three buttons to enter EDL mode, just press them again and again until the sahara works and the firehose goes in.
Regarding payload dumper, I used it simply because nothing else gave me a bootable phone. I did use the EDL tools to unlock the bootloader and to set the active slot (only bobthenormal's EDL tools will set the active slot).
Here's the payload dumper tutorial that worked for me.
Extract Android OTA Payload.bin File using Payload Dumper Tool
Learn how to dump and extract Android OTA Payload.bin file to get the boot.img (for rooting with Magisk), vendor.img, and other other partition images.
www.thecustomdroid.com
Don't forget to flash los-twrp-magisked-boot.img and vbmeta disabled as noted above. Also, if you use this method, let me know if it was necessary for you to flash vendor.img. Above all, do a complete backup via the EDL tools before making any other changes!
Click to expand...
Click to collapse
Phenomenal! Best advice, I have received... Thank you so very much. You hit it right on the head. I'll be sure to fill ya in asap when I have the time to get after it. Appreciate you.
bobthenormal said:
EDL tool
Click to expand...
Click to collapse
Hello, where can I find this program? EDL tool
In this Guide i will explain you how you can flash GSI rom in infinix hot 11s
Warning - this can brick your device if not done properly use this guide only if you know how to recover to stock rom using spflash tool
NOTE- I am assuming you have unlocked the bootloader and enabled usb debugging if you haven't done that you can learn to do that from the other guide i made
First you need to download a working gsi for this device you can download the ones we have tested below
Now download and install platform tools using this Tutorial you can skip this if you have already done this
You need to get the vbmeta.img and vbmeta_system.img from stock firmware which you can download and extract using 7zip and then take the both the files from it or ask in our Telegram group
After downloading gsi image make sure to extract it to .img format using 7-zip as
I advice you to move all required files for flashing into platform tool folders in root directory to make it easier or atleast move it to same folder
Product.gsi has been attached (it's same for both NFC and non NFC version)
adb reboot bootloader
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
If you are stuck at "waiting for devices" output at this step you will have to follow this video
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
fastboot reboot fastboot (you should enter fastbootd after this command make sure before continuing)
fastboot flash product product_gsi.img
fastboot flash system <gsiname>.img
IF YOU ARE GETTING UNABLE TO RESIZE PARTITION ERROR MAKE SURE TO FLASH YOU FLASHED Product_gsi.img
Now select recovery from volume down button and power button >> go to wipe data and factory reset now reboot to system
~~End of guide!~~
Tested roms -
Ancient os Android 12 vndklite ( best rom if you want to play games on this phone codm runs buttery smooth on 90fps! has a lots of customisation )
Pixel experience Android 12 vndklite (is more stable and bug free than ancient os better memory management and a lot better battery life than stock and even ancient os best rom if you want to use it for daily driving)
For future development and questions join our telegram group https://t.me/infinixhot11s_dev
Edit - I was able to fix all the audio and performance issues by making a magisk module for it download Here (if you don't know how to root this device I have made a guide on that too)
Low call volume problem is also fixed by the module
Edit 2 - stock camera has been ported to gsi and the 50mp camera works now join telegram for more information
Edit 3 - newer versions of gcam bsg supports 50 mp camera
Edit 4 - Android 13 GSI works good and the Bluetooth issues are fixed in latest patches (you can daily drive it)
Quick fixes for GSI you will need after flashing :-
Enable the settings highlighted in the screenshot below by going to settings/phh settings/misc features
For VoLTE to work go to settings/phh settings/IMS Features and enable all 4 options (make sure you are connected to internet so that you can download ims apk)
Reboot
Non nfc stock rom - Link
nfc stock rom -
Ansh, Zypher here. I'll DM you on XDA regarding to Ancient OS. I cannot use my main phone and no telegram so I'll DM you here. Please accept me, thank you.
Zypher Kim said:
Ansh, Zypher here. I'll DM you on XDA regarding to Ancient OS. I cannot use my main phone and no telegram so I'll DM you here. Please accept me, thank you.
Click to expand...
Click to collapse
Sure
Thx for the awesome step by step guide bro
The volume increases but cannot reduce it and is only on loud speaker
kelvinchinedu said:
The volume increases but cannot reduce it and is only on loud speaker
Click to expand...
Click to collapse
Working to fix it
Better
i tried to do "fastboot reboot fastboot" command, But "fastboot: usage: unknown reboot target fastboot". How to enter fastbootd?
aryornug said:
i tried to do "fastboot reboot fastboot" command, But "fastboot: usage: unknown reboot target fastboot". How to enter fastbootd?
Click to expand...
Click to collapse
Try to download a newer platform tool verson
also works on standard infinix hot 11! except for the gcam patch which i didnt try
Fggevhy said:
also works on standard infinix hot 11! except for the gcam patch which i didnt try
Click to expand...
Click to collapse
That's good to know
Fggevhy said:
also works on standard infinix hot 11! except for the gcam patch which i didnt try
Click to expand...
Click to collapse
Can you tell me what did you do to get it running on the standard hot 11 x662
I tried but ended up bricking my device
(Restored later with sp flash tool)
Yahiaxe said:
Can you tell me what did you do to get it running on the standard hot 11 x662
I tried but ended up bricking my device
(Restored later with sp flash tool)
Click to expand...
Click to collapse
Try following same tutorial but take vbmeta.img and vbmetasystem fr your firmware...also see if hot11 also has same architecture (for gsi)
Uniqueshiva said:
Try following same tutorial but take vbmeta.img and vbmetasystem fr your firmware...also see if hot11 also has same architecture (for gsi)
Click to expand...
Click to collapse
Is the product.gsi the same for the standard hot 11?
Yahiaxe said:
Is the product.gsi the same for the standard hot 11?
Click to expand...
Click to collapse
It should work fine for all android including yours
ansh_/ said:
It should work fine for all android including yours
Click to expand...
Click to collapse
I tried again but I got an error "dm-verify is corrupt your device will boot in 5 seconds" and it just bootloops
Yahiaxe said:
I tried again but I got an error "dm-verify is corrupt your device will boot in 5 seconds" and it just bootloops
Click to expand...
Click to collapse
I got it to finally work thanks to everyone for your help and thanks ansh_/ for the wonderful guide
ps: Switching to a non-vndklite gsi did the trick
the gsi flashing is easier then i thought
I tested pixel experience plus (june update), it was laggy, crashing and slow
currently on ancient os 6.4 and its a-m-a-z-i-n-g smooth, fast, no crashes, good game performance and extremely customizable, I highly recommend it
update; ancient started getting a little laggy for some reason and randomly rebooted a few times
so, i switched to crdroid 8.8, it's great nice clean customizable and stable android, with great battery management and performance
hello need help. after following your tutorial ang flashing crdroid 8.8 i got a device corrupted then proceeds to bootloop.
after that i tried flashing stock firmware using sp flash tool with this tutorial
[Guide] Flashing stock rom for Mediatek devices using spflash tool
In this guide i will explain you how to flash stock ROM using spflash for your Mediatek devices in the simplest way possible Requirements - a phone with Mediatek SoC Stock rom which you may or may not find on your vendor official website ( a...
forum.xda-developers.com
but no luck bypass tool give me some kind of error and wont bypassed the protection. now the phone is stuck on charging light. power button does nothing.
i hope anyone have ideas to fix this
thanks
SlothYano said:
hello need help. after following your tutorial ang flashing crdroid 8.8 i got a device corrupted then proceeds to bootloop.
after that i tried flashing stock firmware using sp flash tool with this tutorial
[Guide] Flashing stock rom for Mediatek devices using spflash tool
In this guide i will explain you how to flash stock ROM using spflash for your Mediatek devices in the simplest way possible Requirements - a phone with Mediatek SoC Stock rom which you may or may not find on your vendor official website ( a...
forum.xda-developers.com
but no luck bypass tool give me some kind of error and wont bypassed the protection. now the phone is stuck on charging light. power button does nothing.
i hope anyone have ideas to fix this
thanks
Click to expand...
Click to collapse
Well, your actually might have just hard bricked this device I am afraid.
But I can tell you the steps to flash the stock firmware
1- Download the firmware for your device make sure its the correct one (If it's incorrect then you will hard brick the device)
2- Make sure you have mtk vcom drivers
3- use spflashtool and load the firmware (no need for the bypass tool)
4- make sure you set it to Firmware Upgrade (This is important)
5- make sure your phone is off
6- click on "Download" in the flashtool
7- Hold both volume buttons and plug in the device
8- If your device is still alive it should start the flashing process
Note: You did something that was incorrect when you started to follow this guide and you most likely hard bricked your device. Your phone is gone I think
Please note that I am not an expert on the subject tho
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/