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.
Related
Hello, yesterday I just unlocked my moto g's(from koodo) bootloader. And right after I unlocked it, it was stuck in a bootloop, but I managed to install the recovery. Then I tried to install the stock rom multiple times, then I decided to install a custom rom then revert to stock. So I did install a custom rom, but now it's worse. I shows up the android error sign everytime I boot the phone. And the recovery is gone, it would just boot up to the android error sign. And the only thing available is the fastboot menu. Please Help!
Ali7000 said:
Hello, yesterday I just unlocked my moto g's(from koodo) bootloader. And right after I unlocked it, it was stuck in a bootloop, but I managed to install the recovery. Then I tried to install the stock rom multiple times, then I decided to install a custom rom then revert to stock. So I did install a custom rom, but now it's worse. I shows up the android error sign everytime I boot the phone. And the recovery is gone, it would just boot up to the android error sign. And the only thing available is the fastboot menu. Please Help!
Click to expand...
Click to collapse
please help!
What do you mean by "I managed to install the recovery"?
When you're talking about installing the stock ROM, is that through mfastboot (motorola-fastboot) or a custom recovery?
Did you run any unsafe commands like mfastboot erase (anything other than modemst1 and modemst2)?
Side note: it is bad forum etiquette to needlessly quote posts, and very bad forum etiquette to "bump" a post after three mere hours. I understand you're probably stressed from your phone acting up, but the decision to type "fastboot oem unlock" is ultimately yours. I advocate having a backup device if you're going to be serious about flashing ROMs and such.
Sorry if this is a double post but I need help badly
I cannot get any recoveries to work on my OnePlus 3. Not even stock. Ill flash twrp to it and it will say successful but I cannot boot into it and using fastboot boot twrp.img says it works but my phone just hangs at the fastboot window and then crashes so I have to hard restart it.
Any suggestions on how to fix it?
Hello
As you said, youve already asked here so this thread will be closed
http://forum.xda-developers.com/general/xda-assist/oneplus-3-recovery-t3483564
Wait for one of our Assist team to point you to the right place to get help.
Thanks.
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 a new Pixel 4a, Android 12. I want to use lineage 19.1. I try already several days to flash TWRP, sunfish_twrp3.6.1-11 or sunfish_twrp11-test3. No success. Finally I write fastboot flash boot_a_twrp.img instead of fastboot boot twrp.img. It ended up with the screen of teamwin, hanging there. Now the pixel is not booting to android any more but each time to the incomplete teamwin screen. So I tried to flash the newest factory image. No success : "writing 'boot' failed (remote: Failed to write to partition Not Found)
I need help urgently. Thanks!
Henneranek said:
I have a new Pixel 4a, Android 12. I want to use lineage 19.1. I try already several days to flash TWRP, sunfish_twrp3.6.1-11 or sunfish_twrp11-test3. No success. Finally I write fastboot flash boot_a_twrp.img instead of fastboot boot twrp.img. It ended up with the screen of teamwin, hanging there. Now the pixel is not booting to android any more but each time to the incomplete teamwin screen. So I tried to flash the newest factory image. No success : "writing 'boot' failed (remote: Failed to write to partition Not Found)
I need help urgently. Thanks!
Click to expand...
Click to collapse
I don't think you're providing enough info. "I tried to flash the newest factory image" doesn't tell useful people what you did. I'm not useful, anyway.
I wouldn't use TWRP on the 4a. I'm using LOS recovery. You can follow the instructions (read the whole thing first) here: https://wiki.lineageos.org/devices/sunfish/install
That should allow you to do a clean install of LOS19.
Thank you for giving advice. I followed exactly your recommended web-site (Install LineageOS on sunfish, Temporarily booting a custom recovery using fastboot). From what I understand the first step is to install a recovery which in my case was sunfish_twrp3.6.1-11.img . I did not work. I also tried an older twrp.img. "fastboot flash boot twrp.img" did not work. I read and read, learned about 2 slots, without a deep understanding. Then I tried " fastboot flash boot_a_twrp.img". It seemed to work. But when I reboot into recovery it is stuck at the screen of teamwin (see attachment).
I thought to give up and do a factory reset. But there I got this: Failed to write to partition Not Found. What can I do now? Is there a way to do a factory reset to slot_b ?
If you try to help me please remember that I don't have enough knowledge to understand abbreviations.
Henneranek said:
Thank you for giving advice. I followed exactly your recommended web-site (Install LineageOS on sunfish, Temporarily booting a custom recovery using fastboot). From what I understand the first step is to install a recovery which in my case was sunfish_twrp3.6.1-11.img . I did not work. I also tried an older twrp.img. "fastboot flash boot twrp.img" did not work. I read and read, learned about 2 slots, without a deep understanding. Then I tried " fastboot flash boot_a_twrp.img". It seemed to work. But when I reboot into recovery it is stuck at the screen of teamwin (see attachment).
I thought to give up and do a factory reset. But there I got this: Failed to write to partition Not Found. What can I do now? Is there a way to do a factory reset to slot_b ?
If you try to help me please remember that I don't have enough knowledge to understand abbreviations.
Click to expand...
Click to collapse
if it goes into bootloader head over to the android flash tool and give that a try,,https://source.android.com/setup/contribute/flash
To hammered58 Thank you for this suggestion reg. android flash tool. This seems very complicated and I don' t understand some terms. I am a NOOB.
In my Pixel 4a the slot a is somehow obstructed. Can't I use slot b to do a factory reset?
Henneranek said:
To hammered58 Thank you for this suggestion reg. android flash tool. This seems very complicated and I don' t understand some terms. I am a NOOB.
In my Pixel 4a the slot a is somehow obstructed. Can't I use slot b to do a factory reset?
Click to expand...
Click to collapse
Its not complicated at all,, just put you phone in fastboot, which I know you have done before , go here (https://flash.android.com) and follow the on screen prompts, select any factory image and start.
Dear hammered58, I am so thankful to you! Thank you for encouraging me to use the Android Flash Tool. I was skeptical. To undo the pop-up blocker in Chrome was complicated for me. After some failures because I was not patient enough I finally succeeded.
Henneranek said:
Dear hammered58, I am so thankful to you! Thank you for encouraging me to use the Android Flash Tool. I was skeptical. To undo the pop-up blocker in Chrome was complicated for me. After some failures because I was not patient enough I finally succeeded.
Click to expand...
Click to collapse
Good to know it worked for you
Good morning all I need some help unbricking my pixel 5. I have exhausted all possible avenues that I'm aware of to restore my phone out of bootloop. At the time I messed it up I was attempting to use twrp. In an attempt to fix the phone I tried flashing the system,and boot to no avail repeatedly getting the error "boot.img missing command-line or os version" as well as using the flash all from the stock firmware file. The current active slot is b and the a/b partition thing is new to me so I'm sure somewhere along the way I missed something. Any help is greatly appreciated .
Could you try this fastboot command and see if it works?
fastboot --set-active=a
I did try that however I'm not sure i was doing it correctly is it typed the way you typed it out?
Reboot the phone into the bootloader, look up how to do that if you don't know how, and then manually flash a rom or use the Android Flash Tool. The latter option is recommended if you are a novice.
I wouldn't say I'm novice lol but more out of the game too long either way thank you for your assistance I will try that as soon as I get a chance and report back
UPDATE your advice worked and I was able to reboot properly thank you in a side note is it impossible at this time to install twrp on a pixel 5?
musiv2 said:
UPDATE your advice worked and I was able to reboot properly thank you in a side note is it impossible at this time to install twrp on a pixel 5?
Click to expand...
Click to collapse
Yes. The Pixel series, as with most A/B devices, do not have a bespoke recovery partition. The recovery kernel is compressed into the boot image. TWRP does not support compression in this way so it cannot be used as a replacement for the stock recovery. The only effective way to use TWRP is to live boot the image, use TWRP to do whatever you need to do, without installing it to /boot.
BTW the next time you need to restore your phone you can use the Android Flash Tool.
Ok thank you for the explanation as I stated before I am new to the a/b partitioning way of android life so I have alot to learn
I used twrp in the past( on no A/B devices) but would recommend learning fastboot/adb. First step: always make sure USB debugging is enabled after every flash. This will make it so you can fix a lot of mistakes and recover your device. It's the first thing I do after every boot on a new install.
Here's the commands to flash stock to both slots. NOTE: this is for android 13. 12 and before will be a little different. Bootloader, radio and rom names should be exact to file, this is just for example.
fastboot --slot=all flash bootloader bootloader.img
fastboot reboot bootlaoder
fastboot --slot=all flash radio radio.img
fastboot reboot bootlaoder
fastboot --slot=a --skip-reboot update stock-image.zip
fastboot reboot bootlaoder
fastboot --slot=b --skip-reboot update stock-image.zip
fastboot -w
fastboot reboot
One final note: I put slot a first but I always start with the active slot(it's in the bootloader screen). If you want the android 12 instructions, let me know but it's not much different, you just use the stock recovery.