Related
Okay, here's the deal... I have an OPO (not mine) that is completely stock running, I would presume 5.0.2. I'm not exactly sure which build. But I was told that she turned the phone off at night and charged it. Turned it on in the morning and it got stuck on the cyanogen logo. No boot loops, no getting past that. Just sitting there. The device is stock, bootloader locked, no root. I also highly doubt that ADB debugging was turned on while it was working...
I'm trying to wipe it bring it back to stock, but I'm not having any success. I've gone in to Cyanogen recovery and wipe/factory reset, wipe cache, wipe media. Reboot, still stuck. When I click apply update in recovery, it gives me a bunch of errors saying so and so directory isn't found. So that leaves to me to believe that something went bad.
I just tried to fastboot oem unlock, said it finished in a few seconds. Then I tried to fastboot the factory image files and after the first one (modem), it gave me an error saying the bootloader is locked.
I'm out of ideas and the unbrick a hard bricked OPO thread said it wouldn't work, so I haven't tried it. Any advice on where to look would be much appreciated.
Anybody?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I get this when I hit Apply Update and then use storage as option.
moobieboobie said:
Anybody?
I get this when I hit Apply Update and then use storage as option.
Click to expand...
Click to collapse
Flash The whole Rom with fastboot to fix The Problem ....make a backup of your internal sdcard....
jamal2367 said:
Flash The whole Rom with fastboot to fix The Problem ....make a backup of your internal sdcard....
Click to expand...
Click to collapse
That's the problem. I can't because the bootloader is locked. When I try to unlock it, it runs the command. Then when I try to fastboot flash, it tells me the bootloader is locked. I have my own OPO that I have unlocked and rooted, so knowing how to unlock isn't an issue either.
moobieboobie said:
That's the problem. I can't because the bootloader is locked. When I try to unlock it, it runs the command. Then when I try to fastboot flash, it tells me the bootloader is locked. I have my own OPO that I have unlocked and rooted, so knowing how to unlock isn't an issue either.
Click to expand...
Click to collapse
Run CMD as Admin ...have you install the right driver for your phone and install the ADB drivers correctly? ...
jamal2367 said:
Run CMD as Admin ...have you install the right driver for your phone and install the ADB drivers correctly? ...
Click to expand...
Click to collapse
Yes, all updated drivers. Drivers are not the issue since I can execute commands while in fastboot. The issue is not having an unlocked bootloader, so I can't flash anything and it won't unlock bootloader.
moobieboobie said:
Yes, all updated drivers. Drivers are not the issue since I can execute commands while in fastboot. The issue is not having an unlocked bootloader, so I can't flash anything and it won't unlock bootloader.
Click to expand...
Click to collapse
Ps did phone was encrypt?
geowolf1000 said:
Ps did phone was encrypt?
Click to expand...
Click to collapse
No, phone was not encrypted and ColorOS unbrick didn't work. It recognizes the phone, I hit start and it does it's thing. After first green bar, it boot loops instead of flashing all the files. Ran as admin and all the drivers are good.
moobieboobie said:
No, phone was not encrypted and ColorOS unbrick didn't work. It recognizes the phone, I hit start and it does it's thing. After first green bar, it boot loops instead of flashing all the files. Ran as admin and all the drivers are good.
Click to expand...
Click to collapse
hit install from recovery
Choose file to update
Search files
Do you see your partition?
System exist?
What system do you have color or cyanogen?
Data?
Sd?
geowolf1000 said:
hit install from recovery
Choose file to update
Search files
Do you see your partition?
System exist?
What system do you have color or cyanogen?
Data?
Sd?
Click to expand...
Click to collapse
See post above with picture. It was running stock Cyanogen OS 12, not modded or anything. When I hit Apply Update and Choose from internal storage, I get the error in above picture.
moobieboobie said:
See post above with picture. It was running stock Cyanogen OS 12, not modded or anything. When I hit Apply Update and Choose from internal storage, I get the error in above picture.
Click to expand...
Click to collapse
But you have adb
Sideload full rom included recovery
From adb
geowolf1000 said:
But you have adb
Sideload full rom included recovery
From adb
Click to expand...
Click to collapse
If by sideload, you mean copy the rom to device and then load..I can not access device storage. ADB sideload rom through command line gives me the same errors you see in the above picture.
moobieboobie said:
If by sideload, you mean copy the rom to device and then load..I can not access device storage. ADB sideload rom through command line gives me the same errors you see in the above picture.
Click to expand...
Click to collapse
F**ing recovery
With adb you can navigate to system and change built.prompt and enable debugg mode
All the other method i know need root so dd (replace)recovery from adb
geowolf1000 said:
F**ing recovery
With adb you can navigate to system and change built.prompt and enable debugg mode
All the other method i know need root so dd (replace)recovery from adb
Click to expand...
Click to collapse
Can you give instructions on how to? I'm not too familiar with adb, but can follow steps.
moobieboobie said:
Can you give instructions on how to? I'm not too familiar with adb, but can follow steps.
Click to expand...
Click to collapse
Even this suggest need root.
All need root.... To system...
moobieboobie said:
Can you give instructions on how to? I'm not too familiar with adb, but can follow steps.
Click to expand...
Click to collapse
Another trick for installation is
Code:
fastboot boot <path/name of the recovery twrp img>
It will boot your phone into recovery once from the recovery image
stored in your PC temporarily
then you can flash the zip either by sideload or
Check this
geowolf1000 said:
Another trick for installation is
Code:
fastboot boot <path/name of the recovery twrp img>
It will boot your phone into recovery once from the recovery image
stored in your PC temporarily
then you can flash the zip either by sideload or
Check this
Click to expand...
Click to collapse
cannot fastboot boot recovery, tells me bootloader is locked and fails. the link requires unlocking bootloader, which is not working for me.
moobieboobie said:
cannot fastboot boot recovery, tells me bootloader is locked and fails. the link requires unlocking bootloader, which is not working for me.
Click to expand...
Click to collapse
Haz a parametre here
There is a way to flash an unlocked bootloader if you can't fastboot oem unlock.
As you already tried the color.zip method you should already have most of the needed files.
Download the attachment and unzip it into color folder replacing the files emmc_appsboot.mbn and rawprogram0_64.xml (backup the originals first).
-power off the OPO
-hold VolUp and plug into PC
-on PC open device manager, OPO should be in QDloader 9008
-keep an eye on device manager and start msm8974downloadtool from color.zip
-when in device manager the QDloader 9008 disconnects press stop in msm8974downloadtool
-OPO should now be Qualcomm Diagnostics 9006 in device manager
-download MiFlash from here http://www.androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable/ and set it up like on the pictures on that website
-click refresh. now it should show you OPO on the respective COM port. click flash
-when successfull finished unplug and press and hold power for 30 seconds
-now start into fastboot with power + VolUp and there is your unlocked bootloader
-now you can flash cos with fastboot
The rawprogram0_64xml is edited so that it only writes partition table and flashes sbl1, dbi, rpm, tz, recovery and emmc_appsboot.
This worked for me when i couldn't flash with msm8974downloadtool, it always flashed modem, started with flashing system and then began from the start again.
tropenfrucht said:
There is a way to flash an unlocked bootloader if you can't fastboot oem unlock.
As you already tried the color.zip method you should already have most of the needed files.
Download the attachment and unzip it into color folder replacing the files emmc_appsboot.mbn and rawprogram0_64.xml (backup the originals first).
-power off the OPO
-hold VolUp and plug into PC
-on PC open device manager, OPO should be in QDloader 9008
-keep an eye on device manager and start msm8974downloadtool from color.zip
-when in device manager the QDloader 9008 disconnects press stop in msm8974downloadtool
-OPO should now be Qualcomm Diagnostics 9006 in device manager
-download MiFlash from here http://www.androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable/ and set it up like on the pictures on that website
-click refresh. now it should show you OPO on the respective COM port. click flash
-when successfull finished unplug and press and hold power for 30 seconds
-now start into fastboot with power + VolUp and there is your unlocked bootloader
-now you can flash cos with fastboot
The rawprogram0_64xml is edited so that it only writes partition table and flashes sbl1, dbi, rpm, tz, recovery and emmc_appsboot.
This worked for me when i couldn't flash with msm8974downloadtool, it always flashed modem, started with flashing system and then began from the start again.
Click to expand...
Click to collapse
gave it a shot a few minutes ago.. As soon as 9008 dc fom device manager, i hit stop. the phone turns off or reboots (the screen goes blank)... I hear the connection, but no 9006.
Update: Thread outdated. A new and working version of TWRP was posted in another Forum. Thanks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I get this
PS: On instructions for second method you may want to mention you have to rename twrp image to recovery.img
My device is now stuck in the fastboot menu. It says I can navigate the menu using volume up and down but pressing either of those doesn't do anything and I can't seem to power off the device by holding the power button. Any suggestions on how to fix this?
laod said:
My device is now stuck in the fastboot menu. It says I can navigate the menu using volume up and down but pressing either of those doesn't do anything and I can't seem to power off the device by holding the power button. Any suggestions on how to fix this?
Click to expand...
Click to collapse
Some people have reported that touch isn't working and partitions aren't mounting properly. I tried to fix most issues and uploaded a new version. I do not own this device personally - so i can not test the fixes. Please give me feedback for the updated version.
I just got my GPD XD+ today, thanks for the TWRP build but on mine, even with the current build (2018/04/01), I can't perform any actions. Touch still seems not to work for me. I can't get past TWRP asking me "Keep System Read-only?" Let alone see if partitions are loading correctly.
Everything is in portrait mode which is awkward for this device. What about landscape? Shouldn't it be 1280x720 rather than 720x1280?
**Update**
It would appear that my touch controls are inverted... so the fix for others, seems to have inverted my own.
**Update 2***
Well... after realizing the touchscreen was reversed for me, I was able to slide the "Swipe to allow modifications" slider but after that, I chose to reboot out of recovery since the likelyhood of me hitting something by mistake with the controls reversed was high. Being very careful, I was able to tell it to reboot to system and now the system hangs at the GPD logo.. which no longer animates... I can no longer boot into anything but recovery and fastboot.
Any theories as to what has happened? Does anyone have a Clean Stock ROM of the plus model so I can start over using adb?
**Update 3**
PsyOps pointed me towards some stock images at "forum.gpd.hk/t3-the-latest-firmware-of-gpd-game-console" and I'm back in business. Had to flash more than just recovery and boot.. had to flash system as well for some reason.
Goayandi said:
Some people have reported that touch isn't working and partitions aren't mounting properly. I tried to fix most issues and uploaded a new version. I do not own this device personally - so i can not test the fixes. Please give me feedback for the updated version.
Click to expand...
Click to collapse
I have the same situation here.
It happened after unlocked the bootloader, so it's nothing to do with the recovery.
The adb commend return the error: device '(null)' not found.
I can't check the "recovery" box. It doesn't do anything. And the first methode doesn"t work
EDIT : nevermind, I did it but same problem as Busted77
laod said:
My device is now stuck in the fastboot menu. It says I can navigate the menu using volume up and down but pressing either of those doesn't do anything and I can't seem to power off the device by holding the power button. Any suggestions on how to fix this?
Click to expand...
Click to collapse
Same thing here. Now waiting for the battery to empty. What happens after that? Will it work fine and the bootloader be unlocked?
vanzan said:
Same thing here. Now waiting for the battery to empty. What happens after that? Will it work fine and the bootloader be unlocked?
Click to expand...
Click to collapse
I was being dinner and used adb commands instead of fast boot. If you have your device plugged into a computer with fastboot setup you can run "fastboot reboot" and everything should work.
vanzan said:
Same thing here. Now waiting for the battery to empty. What happens after that? Will it work fine and the bootloader be unlocked?
Click to expand...
Click to collapse
Wait for the battery runs out, then recharge, it works fine and the bootloader is unlocked, the first boot will take longer and a few reboot.
And I find that any time you issue fastboot command from you pc, the xd plus will stuck and you have to wait the battery runs out.
I installed the Magisk use fastboot method, stuck again, and need to wait for the battery runs out, recharged, and evertyhing ok then.
There's another root method on Chinese forum (flash supersu pack by recovery), since I rooted by installin Magisk, I didn't try that.
---------- Post added at 11:46 ---------- Previous post was at 11:45 ----------
laod said:
I was being dinner and used adb commands instead of fast boot. If you have your device plugged into a computer with fastboot setup you can run "fastboot reboot" and everything should work.
Click to expand...
Click to collapse
No, when I stuck in the fastboot menu, the adb command return error that no device can find, I have to unplug battery or wait for the battery runs out.
"fastboot reboot" worked perfectly for me!
Fastboot stuck
Same problem here.
I installed the drivers but got the error.
Now my device is in fastboot mode but fastboot reboot etc. don't work.. And I just can't turn it off..
Im really sad.
Windows 10 x64
So.. At least I could fix the problem, I installed the Drivers (had do disable driver signature) and installed your TWRP Mod successfully but the Screen is mirrored! U can use it but its very tricky.. I could open "Install" But if I open it, twrp could not load any data it called "0MB Space" and yeah after reboot, my GPD XD Plus DON'T start..
LeraxGER said:
So.. At least I could fix the problem, I installed the Drivers (had do disable driver signature) and installed your TWRP Mod successfully but the Screen is mirrored! U can use it but its very tricky.. I could open "Install" But if I open it, twrp could not load any data it called "0MB Space" and yeah after reboot, my GPD XD Plus DON'T start..
Click to expand...
Click to collapse
I had the same issue, could use it inverted and mirrored but after running it and not doing anything with it, I could no longer boot into system... Only into recovery. If I tried to boot into system, the boot animation would never animate and the system would hang.
See PsyOps' reply to my question of where to find a stock rom. You can either use the provided tool or you can use adb commands to reflash your system partition... At least for me I had to flash system... Flashing boot and recovery (removing TWRP) didn't work alone...
reddit.com/r/gpdxd/comments/8a50vq/gpd_xd_plus_stock_rom_available/
Busted77 said:
I had the same issue, could use it inverted and mirrored but after running it and not doing anything with it, I could no longer boot into system... Only into recovery. If I tried to boot into system, the boot animation would never animate and the system would hang.
See PsyOps' reply to my question of where to find a stock rom. You can either use the provided tool or you can use adb commands to reflash your system partition... At least for me I had to flash system... Flashing boot and recovery (removing TWRP) didn't work alone...
reddit.com/r/gpdxd/comments/8a50vq/gpd_xd_plus_stock_rom_available/
Click to expand...
Click to collapse
Thanks for the advice, I spoke with him too and he already gave me the guide how to boot into Recovery Mode and then fastboot (Hold VOL+ & On Off Untill Menu apperas, then boot into recovery, then if the android guy appears press On/Off and THEN VOL+, so you're in the normal recovery mode for all the other poor user's )
And I flashed system.img, boot and stock recovery and then it booted up..
The only thing is, that I think that the SD card won't mount correctly anytime and if I plug it to the PC, I dont see the SD card and big files (like the StockROM Update 1.10 abort before its finished).
Greetings
Contact me in discord.
Could you please close the thread and delte the download link? Not even once your TWRP worked, please don't share the file anymore. Other user's will brick their device too.
Hello how to fix a black screen caused by overheating device?i dont know how to use the stock recovery i have thr gpd boot logo but after a black screen and blue led thanks
Hello !
Just acquired an HTC U12+ in replacement for my brave Oneplus One, that i kept updated to Android Pie. Compare to my old One, HTC didn't make it easy to make mod...
As I hate all these stupid UI, i want AOSP without the google app as much as i can, so i wanted to try the Android Pie GSI "FLOSS", hoping it works great.
Anyway since yesterday i spend a lot of time trying to install TWRP on my U12, and fastboot and adb make me crazy. First i unlock the bootloader with the describe procedure, it works fine, i use fastboot from offical repo of ubuntu 18.10. I red all the thread and understand that i must boot first twrp and then flash it with the installer. The problem is fastboot and adb are not working after unlocking the bootloader. I am using the USB type C to type A cable from HTC.
My phone was with firmware 1.25 with june patch when i bought it. So i download the right version of TWRP. Fastboot is not working anymore and i get an error of "protocol". Then i see in the FAQ that you need to use the last version from google. This fastboot didn't worked much more, "too many links" error or similar. I tried different usb port of my pc, it seems the usb 3.0 and 3.1 do this, with usb 2.0 error is different, it said "downloading boot.img" and nothing happens. Then i tried to update to 1.30, but fastboot is not working more. I tried in windows, i install the htc driver and use the latest fastboot, same errors. Also tried another pc running ubuntu 18.04 without success.
Right now "fastboot devices" find the U12 properly but all command show error, and "adb devices" shows nothing in download mode.
I guess the problem come from the usb cable ? I live in a small town in the middle of nowhere and have no type c cable, so i ordered two new cable among other accessories, i hope they works but i won't have them before two week probably more (revolution in coming in France ).
But what i don't understand, if it's a problem with the cable, why fastboot was working when i do the "fastboot flash unlocktoken Unlock_code.bin" to unlock the bootloader, and then it refuse to work ?
Regards !
When you do fastboot devices and U12 shows up then you should be alright.
To boot TWRP you must be in boot loader, NOT download mode.
fastboot boot twp.img
It has worked for me just fine on windows, macOS, and Ubuntu
---------- Post added at 10:10 PM ---------- Previous post was at 10:08 PM ----------
Use
fastboot --version
To see what fastboot version you have. Latest should be 28.0.1
Hello,
Thank you for your answer. I know the difference between the fastboot and download mode, i try everything but the problem is always the same. My fastboot is the latest from the xda topic :
./fastboot --version
fastboot version 28.0.1-4986621
For example i just try again, it's connected to the usb 2.0 port of my pc, i'm in fastboot (recovery) and not download mode :
./fastboot devices
FA8731F01429 fastboot
./fastboot boot twrp-3.2.3-2-ime.img
Downloading 'boot.img' ... and nothing happens
If it's connected to usb 3.0 or 3.1, get the "too many links" error.
Edit : another exemple, if i use the fastboot from kubuntu 18.10 repo :
[email protected]:~$ fastboot devices
FA8731F01429 fastboot
[email protected]:~$ fastboot boot twrp-3.2.3-2-ime.img
< waiting for any device >
@ghstmm
I've read your posts and I can't stop feeling that there's something off, obviously. Don't be mad at me cuz I'm not an expert, but you might be in the wrong mode. You should be in "Bootloader" mode which is different than "Recovery" mode.
That is a strange issue.
Several users on the Pixel 2 forum had the same issue and a different cable worked. I don't know how a cable only works with certain commands.
Looks like you're doing it right however. Unfortunately it might simply be a cable.
Maybe try flashing a boot.img that already has twrp in it so you can just use the bootloader recovery option?
---------- Post added at 08:35 AM ---------- Previous post was at 08:27 AM ----------
k_l_o said:
@ghstmm
I've read your posts and I can't stop feeling that there's something off, obviously. Don't be mad at me cuz I'm not an expert, but you might be in the wrong mode. You should be in "Bootloader" mode which is different than "Recovery" mode.
Click to expand...
Click to collapse
You should be on this screen.
BOOTLOADER
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yes i am to this screen when i use fastboot. Not have the same info in the screen though. I cannot make a photo now so i will just write what i see :
press volume key etc...
Fastboot Mode (in red)
PRODUCT_NAME - HTC_Phone
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - FA8731F01429
SECURE BOOT - PRODUCTION
SECURE STATE - S-ON
DEVICE STATE - UNLOCKED (U) (in red)
KEY STATE - NONE
*** Software status: Modified *** (in red)
Guess i will try again when i'll get the other cable, but it's very strange indeed.
@ghstmm
Have you installed the latest HTC drivers?
Edit:
Forgot to mention I had the "too mank link" error because my HTC Drivers were out of date when I replaced my HTC 10 with the HTC U12+
k_l_o said:
@ghstmm
Have you installed the latest HTC drivers?
Edit:
Forgot to mention I had the "too mank link" error because my HTC Drivers were out of date when I replaced my HTC 10 with the HTC U12+
Click to expand...
Click to collapse
I mostly use linux so their is no driver, but in windows i install the HTC SYNC MANAGER. It finds the phone when firmware was in 1.25, but after update to 1.30 i got a message saying this software is deprecated and the manager didn't find the phone. What driver should i use ?
Regards
ghstmm said:
I mostly use linux so their is no driver, but in windows i install the HTC SYNC MANAGER. It finds the phone when firmware was in 1.25, but after update to 1.30 i got a message saying this software is deprecated and the manager didn't find the phone. What driver should i use ?
Regards
Click to expand...
Click to collapse
I brought up the HTC Sync Manager only for the purpose of installing the drivers. I uninstall the Sync Manager portion of the package afterwards. Anyway, try this link for the latest HTC Driver:
http://www.mediafire.com/file/g4r62oz2v9b1x0q/HTC-Mobile-Driver-v4.17.0.001.zip
I was already in v4.17.0.001. Guess i have to wait now for the new cable, hope it solve the problem...
Hello,
Normally no problem with the cable provided in the box of HTC! It is true that the U12 is pretty capricious! sometimes it takes several times with ADB!
It is not a problem of ADB version even the version 'htc_fastboot' of 2016 works at home!
PS: The most painful is the touch button to go into bootload Pffffffffff
Alan-B said:
Hello,
Normally no problem with the cable provided in the box of HTC! It is true that the U12 is pretty capricious! sometimes it takes several times with ADB!
It is not a problem of ADB version even the version 'htc_fastboot' of 2016 works at home!
PS: The most painful is the touch button to go into bootload Pffffffffff
Click to expand...
Click to collapse
I don't have any problem with adb, it works always without issues. Yeah sometimes it's difficult to boot into bootloader, but I use adb for that also
Sent from my HTC U12+ using XDA Labs
Just to know, when you run fastboot boot image are in you in the correct directory where the image file is?
master66 said:
Just to know, when you run fastboot boot image are in you in the correct directory where the image file is?
Click to expand...
Click to collapse
I try pretty much everything, inside or outside the platform-tools directory, also renamed twrp several time but no success.
Good news, i make it works I receive the cables todays, and even if the fastboot boot twrp.img still didn't work for any reason, adb works with the two cable i ordered. So i root the phone and use magisk to install twrp.
Strange thing, adb didn't work in download mode, only in android.
ghstmm said:
I try pretty much everything, inside or outside the platform-tools directory, also renamed twrp several time but no success.
Good news, i make it works I receive the cables todays, and even if the fastboot boot twrp.img still didn't work for any reason, adb works with the two cable i ordered. So i root the phone and use magisk to install twrp.
Strange thing, adb didn't work in download mode, only in android.
Click to expand...
Click to collapse
If fastboot wasn't working, then it's a driver issue. If you're in bootloader/download, you have to install them completely new again. Also TWRP has to be booted from bootloader, not download....
Sent from my HTC U12+ using XDA Labs
DeeZZ_NuuZZ said:
If fastboot wasn't working, then it's a driver issue. If you're in bootloader/download, you have to install them completely new again. Also TWRP has to be booted from bootloader, not download....
Sent from my HTC U12+ using XDA Labs
Click to expand...
Click to collapse
Hello,
Again i was using the fastboot to fastboot, and download to adb
However i get a more serious problem. Now that twrp is working i tried to flash the gsi img. It works but when i start android ask me a password, so i look for the problem and it seems i just didn't wip data. I go back to twrp and perform data and wipe again, i wanted to flash again the gsi image. Problem is their wasn't anything in the sdcard directory (i didn't wip internal storage, so why ?). I try to adb to push to send again the gsi img, but when i go to twrp and go to the adb option, i get "adb devices sideload" and every command :
[email protected]:~/Téléchargements/HTC U12+/platform-tools$ ./adb push /home/satan/system-arm64-ab-floss-su.img /sdcard
adb: error: connect failed: closed
[email protected]:~/Téléchargements/HTC U12+/platform-tools$ ./adb usb
error: closed
[email protected]:~/Téléchargements/HTC U12+/platform-tools$ ./adb devices
List of devices attached
FA8731F01429 sideload
I guess i got a very bad idea to reboot my phone as their was no os. So now the phone is rebooting constently. How i can i go again to twrp ?
Edit : i didn't understand everything from this A/B partition system... i guess my phone is brick now ?
ghstmm said:
Hello,
Again i was using the fastboot to fastboot, and download to adb
However i get a more serious problem. Now that twrp is working i tried to flash the gsi img. It works but when i start android ask me a password, so i look for the problem and it seems i just didn't wip data. I go back to twrp and perform data and wipe again, i wanted to flash again the gsi image. Problem is their wasn't anything in the sdcard directory (i didn't wip internal storage, so why ?). I try to adb to push to send again the gsi img, but when i go to twrp and go to the adb option, i get "adb devices sideload" and every command :
[email protected]:~/Téléchargements/HTC U12+/platform-tools$ ./adb push /home/satan/system-arm64-ab-floss-su.img /sdcard
adb: error: connect failed: closed
[email protected]:~/Téléchargements/HTC U12+/platform-tools$ ./adb usb
error: closed
[email protected]:~/Téléchargements/HTC U12+/platform-tools$ ./adb devices
List of devices attached
FA8731F01429 sideload
I guess i got a very bad idea to reboot my phone as their was no os. So now the phone is rebooting constently. How i can i go again to twrp ?
Edit : i didn't understand everything from this A/B partition system... i guess my phone is brick now ?
Click to expand...
Click to collapse
No not bricked, but you can't sideload an img. Just get it back to sdcard and flash it from there, also for GSI it is better to wipe from stock recovery
Sent from my HTC U12+ using XDA Labs
Ok but how do i go back to the recovery ? The phone is just constently rebooting. From now to go to recovery i waited to be in android, press power button and down right after black screen, now i can't do that.
ghstmm said:
Ok but how do i go back to the recovery ? The phone is just constently rebooting. From now to go to recovery i waited to be in android, press power button and down right after black screen, now i can't do that.
Click to expand...
Click to collapse
This is a quote from the root thread:
"Long press (sometimes really long!) the Power button until you feel the vibration motor (not the feedback) kick in. When it kicks in let go of power button quickly and push volume down to boot into bootloader."
If I remember correctly this is how I was able to get my phone into bootloader when my phone was also in a boot loop. The timing must be precise or you will not get it into bootloader mode. Good luck.
Sent from my HTC U12+ using Tapatalk
mauiblue said:
This is a quote from the root thread:
"Long press (sometimes really long!) the Power button until you feel the vibration motor (not the feedback) kick in. When it kicks in let go of power button quickly and push volume down to boot into bootloader."
If I remember correctly this is how I was able to get my phone into bootloader when my phone was also in a boot loop. The timing must be precise or you will not get it into bootloader mode. Good luck.
Sent from my HTC U12+ using Tapatalk
Click to expand...
Click to collapse
Ok i get it Short timing indeed.
Edit : I finally install the latest android 9 pie gsi. It's working great and i love the floss version, but their is a few bugs : no brightness adjustment, localisation not working and few screen bugs (icon mostly).
Anyway thanks you all for your help
Hello,
My OnePlus is stuck in a bootloop. I can turn it off but if I turn it on, it displays the first screen with the logo "+1" then the second screen with the circles that turn and there they freeze. The circles do not move any more then it restarts and it starts again until the battery runs out.
I tried this awesome tuto called "How to unroot OnePlus 6 in bootloop / hard-brick" but i'm stuck in thé step 5. The phone restarts, I first screen "1+" then the screen with the H2OS logo and then it remains frozen on the logo and the phone restarts and so on. I have tried to retake everything from step 1 but I am still stuck in step 5.
Do you have any idea ?
Thanks,
Don't know that tutorial, but i think it's only a softbrick, have you tried to format data from recovery? Stock one or TWRP doesn't matter, and what you was doing before the phone goes bricked?
Hi !
Sorry I can't post URL of this tuto because i'm new here and there is a restriction. It's this one :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Before this bug I was just playing with a stupid filter in Snapchat then white screen and bootloop.
I've already tried the followings things (without success) :
Wipe data and cache
- reset system setting
- wipe cache => aucun effet
- erase everything (music, pics, etc)
Advanced
- Reboot to fastboot
- Reboot to recovery
I'm lost...
Oli78 said:
Hi !
Sorry I can't post URL of this tuto because i'm new here and there is a restriction. It's this one :
Before this bug I was just playing with a stupid filter in Snapchat then white screen and bootloop.
I've already tried the followings things (without success) :
Wipe data and cache
- reset system setting
- wipe cache => aucun effet
- erase everything (music, pics, etc)
Advanced
- Reboot to fastboot
- Reboot to recovery
I'm lost...
Click to expand...
Click to collapse
Are you encrypted/decrypted twrp/root unlocked bootloader? One or all of them? Tell me more
Sent from my OnePlus7T using XDA Labs
have u try to flash the stock oxygenos firmware zip ? u can use both stock and twrp recovery. what's ur bootloader state ? locked or unlocked ?
Hitman478™ said:
Are you encrypted/decrypted twrp/root unlocked bootloader? One or all of them? Tell me more
Sent from my OnePlus7T using XDA Labs
Click to expand...
Click to collapse
I'm sorry I don't know what is "TWRP". But i saw there is wrote : "bootlocker : device state locked". Is it helpful for you ?
Azhar_Fahry said:
have u try to flash the stock oxygenos firmware zip ? u can use both stock and twrp recovery. what's ur bootloader state ? locked or unlocked ?
Click to expand...
Click to collapse
I just follow this tutorial https://www.youtube.com/watch?v=yKfT7UsWQAk and i'm stuck in the step 5 like you can see here https://www.youtube.com/watch?v=4gMUUZ2CVDM
My bootloader state is locked.
You need to try a format from stock recovery but you'll lose your data
Hitman478™ said:
You need to try a format from stock recovery but you'll lose your data
Click to expand...
Click to collapse
Luckily I made a backup a week before so it's not a problem to lose my data. How can I format from stock recovery ?
Is there a tutorial?
I tried to unlock my bootloader.
Download & Update OnePlus 6 Drivers => ok
Download & Update Fastboot and ADB Binaries/Drivers => ok
Open a command prompt window
fastboot devices => ok
fastboot oem unlock => flashing unlock is not allowed
Try the MSM unbrick tool, i don't think you can unlock the bootloader in this state since you didn't enable it in the dev options
Oli78 said:
Hello,
My OnePlus is stuck in a bootloop. I can turn it off but if I turn it on, it displays the first screen with the logo "+1" then the second screen with the circles that turn and there they freeze. The circles do not move any more then it restarts and it starts again until the battery runs out.
Thanks,
Click to expand...
Click to collapse
With the phone turned off. Hold the volume down button and then push the power button for 10-15 seconds and see if phone reboots to recovery or fastboot. If you can get the phone boot to fastboot, follow the simple guide at the link below. Be patient and follow the steps. This process will erase all the data but you said you already have a copy of the back up data. Download on your PC/laptop the correct version, most current stable OS is 9.0.9. Download will be in the zip format. Unzip the file. While phone in the fastboot mode, connect to your PC. In the unzipped folder, click on FlashAll.bat file and wait. You may get some failure messages, just igore them. Eventually the phone will reboot as a brand new phone. Here is the link:
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Goodluck.
Chinaroad said:
Try the MSM unbrick tool, i don't think you can unlock the bootloader in this state since you didn't enable it in the dev options
Click to expand...
Click to collapse
I already try this solution but i'm still in bootloop.
Gr8man001 said:
With the phone turned off. Hold the volume down button and then push the power button for 10-15 seconds and see if phone reboots to recovery or fastboot. If you can get the phone boot to fastboot, follow the simple guide at the link below. Be patient and follow the steps. This process will erase all the data but you said you already have a copy of the back up data. Download on your PC/laptop the correct version, most current stable OS is 9.0.9. Download will be in the zip format. Unzip the file. While phone in the fastboot mode, connect to your PC. In the unzipped folder, click on FlashAll.bat file and wait. You may get some failure messages, just igore them. Eventually the phone will reboot as a brand new phone. Here is the link:
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Goodluck.
Click to expand...
Click to collapse
Thanks, I try that but there is a failure message "FAILED (remote: Flashing is not allowed in Lock State)" and the phone dit not reboot.
Turn off the phone.. Den press both volume up and power button for few sec.. It will boot into Fastboot.. Now connect to pc and then use Fastboot command to unlock your bootloader. Then use msmtool to install fresh stock rom.
HatRiGt said:
Turn off the phone.. Den press both volume up and power button for few sec.. It will boot into Fastboot.. Now connect to pc and then use Fastboot command to unlock your bootloader. Then use msmtool to install fresh stock rom.
Click to expand...
Click to collapse
I already did that and with this command (fastboot oem unlock) I get this error : flashing unlock is not allowed.
I guess I've to unlock my bootloader first but I don't know how to do that in hardbrick...
I am assuming that you have appropriate ONEplus driver installed?
---------- Post added at 05:40 PM ---------- Previous post was at 05:37 PM ----------
Also are you using the command mentioned in my previous email from the downloaded zipped file. don't try to unlock. Simply try flashall.bat file in the fastboot mode.
Oli78 said:
Luckily I made a backup a week before so it's not a problem to lose my data. How can I format from stock recovery ?
Is there a tutorial?
Click to expand...
Click to collapse
boot into ur recovery, wipe data and flash this firmware. https://forum.xda-developers.com/oneplus-6/how-to/official-oxygenos-5-1-5-ota-oneplus-6-t3794232 . i hope it works.
try this
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
Gr8man001 said:
I am assuming that you have appropriate ONEplus driver installed?
---------- Post added at 05:40 PM ---------- Previous post was at 05:37 PM ----------
Also are you using the command mentioned in my previous email from the downloaded zipped file. don't try to unlock. Simply try flashall.bat file in the fastboot mode.
Click to expand...
Click to collapse
Yes, i dit that :
reboot the phone in fastboot mode
download the OS 9.0.9
connect the phone to the PC (in USB)
in the previous zip folder, click on flash-all.bat
and see the capture below...
Hello.
I've followed instructions as in this thread https://forum.xda-developers.com/t/root-psyche-root-xiaomi-12x-with-magisk.4455293/
only 1 thing I did wrong is downloading 13.02 boot.img file instead of 13.04 boot.img which wasn't available at that time.
After I flashed phone was stuck in Recovery mode bootloop, then for some reason it just got stuck in normal bootloop.
after that I downloaded 13.04 boot.img which was for my version, patched it on another phone in magisk, repeated instructions and now it's stuck in fastboot bootloop.
I also want to mention that I don't have external SD card so I was using boot.img directly from my pc.
Please help me.
There was solution to use Mi Phone Assistant but program doesn't detect my phone.
Edit: I'm green in these kind of termins so want to mention that it doesn't constant rebooting, just everytime I try to boot it goes into fastboot.
If phone is ADB enabled try this
1. Connect Windows desktop computer with phone via USB cable what came with phone
2. In Windows Command prompt run command sequence
Code:
adb devices
adb reboot
to exit phone into NORMAL boot ( i.e. system mode -> ANDROID OS)
xXx yYy said:
If phone is ADB enabled try this
1. Connect Windows desktop computer with phone via USB cable what came with phone
2. In Windows Command prompt run command sequence
Code:
adb devices
adb reboot
to exit phone into NORMAL boot ( i.e. system mode -> ANDROID OS)
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When in fastboot adb devices didn't find any devices
this screenshot is after I entered in recovery mode but you see it yourself...
Looks like USB Debugging isn't got successfully enabled on phone.
xXx yYy said:
Looks like USB Debugging isn't got successfully enabled on phone.
Click to expand...
Click to collapse
Does it mean that phone is forever bricked? Can you throw me some words of hope please.
it is not forever bricked. you just messed up with the boot image. try the troubleshooting steps from the link you ve posted with a different cable. or a different usb. or a different pc. the app should detect the phone at some point.
Fytdyh said:
it is not forever bricked. you just messed up with the boot image. try the troubleshooting steps from the link you ve posted with a different cable. or a different usb. or a different pc. the app should detect the phone at some point.
Click to expand...
Click to collapse
Thank you for advice, I will try.
Fytdyh said:
it is not forever bricked. you just messed up with the boot image. try the troubleshooting steps from the link you ve posted with a different cable. or a different usb. or a different pc. the app should detect the phone at some point.
Click to expand...
Click to collapse
Tried on different PC, didn't work. I doubt it's USB cable because it's original and I unlocked bootloader with it before. I'm desperate...
Edit: I think it's because of software that my phone doesn't get detected, https://prnt.sc/G232WPcRRqC1 mi unlock tool does detect it although only in fastboot mode, not recovery.
edit2: mi pc suite detects my phone in Fastboot mode but writes this... https://prnt.sc/4dB06CtvIfhz
can you enter in recovery mode ? when you enter in recovery mode, what options do you have ?
kiknalex said:
Tried on different PC, didn't work. I doubt it's USB cable because it's original and I unlocked bootloader with it before. I'm desperate...
Edit: I think it's because of software that my phone doesn't get detected, https://prnt.sc/uwS8qnna60rX mi unlock tool does detect it...
Click to expand...
Click to collapse
Hey, just download the Fastboot ROM for your device, extract the boot.img from there and place it in the platform-tools folder.
Then open CMD inside the platform-tools folder and execute the below command to flash the stock boot.img file [assuming you are in the Fastboot Mode]:
Code:
fastboot flash boot boot.img
You may then boot to the OS via the below command
Code:
fastboot reboot
Sidenote: To avoid such scenarios in the near future, please refrain from directly flashing the boot.img. Rather first temporary boot via
Code:
fastboot boot magisk_patched_boot.img
And then use the Direct Install feature of Magisk for permanent root
Fytdyh said:
can you enter in recovery mode ? when you enter in recovery mode, what options do you have ?
Click to expand...
Click to collapse
https://prnt.sc/Oyjs9lxGVFX8 It's same as in this picture, not my phone tho. I didn't try erase data because I think it will disable USB debugging and I chose to wait for answers on forums.
binary**# said:
Sidenote: To avoid such scenarios in the near future, please refrain from directly flashing the boot.img. Rather first temporary boot via
Code:
fastboot boot magisk_patched_boot.img
And then use the Direct Install feature of Magisk for permanent root
Click to expand...
Click to collapse
Hey, thanks for help, I want to clarify 2 things:
1.
Hey, just download the Fastboot ROM for your device, extract the boot.img from there and place it in the platform-tools folder.
Then open CMD inside the platform-tools folder and execute the below command to flash the stock boot.img file [assuming you are in the Fastboot Mode]:
Do I do it with stock boot.img or I should patch it?
2. Isn't that the same as instructions I linked in thread post?
kiknalex said:
Hey, thanks for help, I want to clarify 2 things:
1.
Hey, just download the Fastboot ROM for your device, extract the boot.img from there and place it in the platform-tools folder.
Then open CMD inside the platform-tools folder and execute the below command to flash the stock boot.img file [assuming you are in the Fastboot Mode]:
Do I do it with stock boot.img or I should patch it?
2. Isn't that the same as instructions I linked in thread post?
Click to expand...
Click to collapse
flash the stock image first. after you get a fully fuctional phone attempt the rooting guide. as in, booting the phone as normal, be relieved that you did not hard brick it. then try again, and follow every step of the way.
Fytdyh said:
flash the stock image first. after you get a fully fuctional phone attempt the rooting guide. as in, booting the phone as normal, be relieved that you did not hard brick it. then try again, and follow every step of the way.
Click to expand...
Click to collapse
I just did it and situation is same, it enters bootloops in fastboot... I just remembered one thing and don't know how important it is but maybe makes a difference.
If I recall correctly, when I first flashed patched.img, the installation process wrote sending boot_b but after that it always said sending boot_a
like in this screenshot https://prnt.sc/t931it_cCodT .
Maybe it is root of problems?
I also want to mention a little detail that I rememeber.
When I was checking MIUI updates on site, the release was Stable BETA but only recovery was available, although now fastboot is available too, it's just Stable - without Beta, Perhaps my ROM was Stable Beta and not stable? It's 13.04 GLOBAL.
well, it does have importance. newer devices have 2 partition for booting. while older have only 1.
try this
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
kiknalex said:
Hey, thanks for help, I want to clarify 2 things:
1.
Hey, just download the Fastboot ROM for your device, extract the boot.img from there and place it in the platform-tools folder.
Then open CMD inside the platform-tools folder and execute the below command to flash the stock boot.img file [assuming you are in the Fastboot Mode]:
Do I do it with stock boot.img or I should patch it?
2. Isn't that the same as instructions I linked in thread post?
Click to expand...
Click to collapse
Oh, I forgot to mention that you should only download the same version of Fastboot ROM that was installed on your device. And then flash the stock boot.img from that ROM to both slots using the commands given by @Fytdyh
Fytdyh said:
well, it does have importance. newer devices have 2 partition for booting. while older have only 1.
try this
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
Click to expand...
Click to collapse
Tried still same... maybe it's something with vbmeta.img?
or if your inactive partition is still non-corrupted [fingers crossed] then you could try booting it via that slot. For that, change the active partition via
Code:
fastboot set_active other
and then
Code:
fastboot reboot
binary**# said:
Oh, I forgot to mention that you should only download the same version of Fastboot ROM that was installed on your device. And then flash the stock boot.img from that ROM to both slots using the commands given by @Fytdyh
Click to expand...
Click to collapse
I downloaded same. :|.
I don't mind using another ROM if it will fix my issues, is it even possible to install from situation like this?