Database Info

stuck on a black HTC screen with 4 warning triangles in each corner

I flashed HPSGill's rom on Friday which is Sense 5 themed, It didn't boot up. So I went back to recovery, wiped everything down, and proceeded to flash the stock ROM. The RUU installation failed, giving me a 150 Error. I have used the same RUU for a year now. I then tried running some fastboot commands but most of them give me "REMOTE: NOT ALLOWED".
The phone goes into fastboot mode as when I execute "fastboot devices" i see my phone serial number on the command line. I can't however access adb. On removing the cable it takes me to the bootloader white screen, only now, the options for reboot, reset factory settings, recovery, etc, are not visible.
It just shows me my phone information, bootloader as relocked, and RUU highlighted. I have tried flashing the RUU multiple times, after each flash attempt, all partitions, except the userdata partition shows userdata FAIL-PU, which as I understand is the partition update failing, bootloader shows - BYPASSED. I have also tried downloading the same RUU just in case somehow the one I had was corrupted. But same result.
HTC service center says since I have rooted my phone, I will have to pay 6000 rs. for a 7000rs. phone to get it repaired. Is there any way back from this ? I have sent it to the service center and will get it back tomorrow, So I can only post screenshots if needed tomorrow. I have scoured the internet for the solution and I have read some odd success stories, but none of them for the explorer, mostly for desires. Any help appreciated.
I will be trying bortak's guide in the meanwhile which is again for htc desire.

Well from what I get so far you're stuck in the middle of a bad RUU flash, idea is you need to complete an RUU flash before you can do anything else, from this I get only try flashing several times this RUU or try with some another RUU else, if there is no fastboot this is hard to be fixed, try sending pm to @legen_dary , he experimented for a while to find some s-off way, so he should know a little bit more about this stuff. I'll continue the search, if find something will share, you also, do share what have you discovered, and if something works what is it.

shortyoko said:
Well from what I get so far you're stuck in the middle of a bad RUU flash, idea is you need to complete an RUU flash before you can do anything else, from this I get only try flashing several times this RUU or try with some another RUU else, if there is no fastboot this is hard to be fixed, try sending pm to @legen_dary , he experimented for a while to find some s-off way, so he should know a little bit more about this stuff. I'll continue the search, if find something will share, you also, do share what have you discovered, and if something works what is it.
Click to expand...
Click to collapse
Thanks for the reply. As I mentioned, the moment i connect the phone via the USB cable, it automatically goes into fastboot mode as when i run "fastboot devices", my device shows up. So I'm considering, not all hope is lost. I have to get to work, will be getting my phone back today, will experiment some and get back here at night.
forgot to mention a couple of things.
1. the bootloader shows relocked. On running the fastboot flash unlocktoken Unlock_code.bin, the command completes successfully but the bootloader still shows relocked. And because it constantly shows relocked, I'm not able to install a custom recovery as well.
2. tried putting the rom in the RUU on sdcard and renaming it as PBsomething.zip. but it wont read the sd card. So flashed it manually via fastboot flash zip zipname.zip runs upto a certain point then gives me something like this
RUU: "FAILED (remote: 90 hboot pre-update! please flush image again immediately)" So I tried reflashing it, but keeps giving the same error.
So since the sd card is not being read at all, I guess bortak's method of creating a goldcard goes out the window.

Hmmm.. This is the second such case i've seen..
Have you tried getting the unlock token again from htcdev??
Also, try updating your hboot version...
Or, get any hboot from an ruu, and do a
Code:
fastboot boot hboot.img
If it wrks, you'll atleast be able to unlock the bootloader, and put a recovery on it..
If, however, your original bootloader remains locked, then you wont be able to access the recovery as well..
In fact, it wouldnt go past the hboot...
ғг๏๓ ҭђє ғเรђ™
---------- Post added at 08:19 AM ---------- Previous post was at 08:15 AM ----------
legen_dary said:
hmmm.. This is the second such case i've seen..
Have you tried getting the unlock token again from htcdev??
Also, try updating your hboot version...
Or, get any hboot from an ruu, and do a
Code:
fastboot boot hboot.img
if it wrks, you'll atleast be able to unlock the bootloader, and put a recovery on it..
If, however, your original bootloader remains locked, then you wont be able to access the recovery as well..
In fact, it wouldnt go past the hboot...
Edit : The correct filename is pj03img.zip(or something)..
When the phone first starts in the hboot, you should see a series of filenames, along with "not found" errors.. If you do, then it does scan the sdcard...
ғг๏๓ ҭђє ғเรђ™
Click to expand...
Click to collapse
ғг๏๓ ҭђє ғเรђ™

legen_dary said:
Hmmm.. This is the second such case i've seen..
Have you tried getting the unlock token again from htcdev??
Also, try updating your hboot version...
Or, get any hboot from an ruu, and do a
Code:
fastboot boot hboot.img
If it wrks, you'll atleast be able to unlock the bootloader, and put a recovery on it..
If, however, your original bootloader remains locked, then you wont be able to access the recovery as well..
In fact, it wouldnt go past the hboot...
ғг๏๓ ҭђє ғเรђ™
---------- Post added at 08:19 AM ---------- Previous post was at 08:15 AM ----------
ғг๏๓ ҭђє ғเรђ™
Click to expand...
Click to collapse
Thanks. will try it out and get back to you but after about 12 hours, I am yet to get back my phone and gotta get to work.

burnt nand
your nand is burnt.you should use cute_prince's method.
Steps of solution
1.flash twrp via fastboot -------fastboot flash recovery twrp.img
2.boot recovery via fastboot------fastboot boot twrp.img
3.apply cute prince method -------http://forum.xda-developers.com/showpost.php?p=36868966&postcount=2367
4.re lock bootloader via fastboot ------fastboot oem lock
5.run compatible ruu
6[optional ] unlock bootloader and Flash favourite rom

juristokrat said:
your nand is burnt.you should use cute_prince's method.
Steps of solution
1.flash twrp via fastboot -------fastboot flash recovery twrp.img
2.boot recovery via fastboot------fastboot boot twrp.img
3.apply cute prince method -------http://forum.xda-developers.com/showpost.php?p=36868966&postcount=2367
4.re lock bootloader via fastboot ------fastboot oem lock
5.run compatible ruu
6[optional ] unlock bootloader and Flash favourite rom
Click to expand...
Click to collapse
He's unable to unlock the bootloader so it's impossible to flash a custom recovery
You can't use fastboot boot or fastboot flash with a locked bootloader. Can you get into HBOOT mode by holding volume down and power while switching on the device? Or does it go straight into FASTBOOT mode?

i tried
1) unlocking bootloader, and now its unlocked.
2) fastboot getvar all gives me
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.03.0000
(bootloader) version-baseband: 1.11.82.17
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.31.720.3
(bootloader) serialno: ********
(bootloader) imei: *******
(bootloader) product: pico
(bootloader) platform: HBOOT-7225A
(bootloader) modelid: PJ0310000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 3673mV
(bootloader) partition-layout: HTC
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 30d3dcb5
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.032s
3) fastboot oem boot boots up the phone and is now stuck in a bootloop. gives me the htc jingle and restarts. tried pulling the battery and volume down + power combination to get to the hboot menu, but brings me back to the black htc screen with 4 triangles. At least there is some progress. Now I somehow just need to get that menu back that comes up after the volume down + power combination.
4) tried fastboot oem resetRUUflag and it gave me this -
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.009s
5) tried fastboot boot hboot.img with the boot.img from the RUU
it gave me -
creating boot image...
creating boot image - 788480 bytes
downloading 'boot.img'...
OKAY [ 0.263s]
booting...
FAILED (remote: reproduce boot image with on-flash ramdisk error)
finished. total time: 0.300s

Can you get into recovery?

The boot.img file is the kernel bro.. Not the hboot..
The file you're looking for is hboot -something-something.img
ғг๏๓ ҭђє ғเรђ™

@sachin thomas - No I can't get into recovery
@legen_dary - hboot_1.03.0000_30d3dcb5_1129_signed this one right ? i just renamed it to hboot.img to avoid typing or copying the whole name
EDIT : i find this flag out of place . (bootloader) boot-mode: RUU. should it be RUU ? i think this is the one causing all the problem, though of course i may be wrong.

salil_1337 said:
@sachin thomas - No I can't get into recovery
@legen_dary - hboot_1.03.0000_30d3dcb5_1129_signed this one right ? i just renamed it to hboot.img to avoid typing or copying the whole name
EDIT : i find this flag out of place . (bootloader) boot-mode: RUU. should it be RUU ? i think this is the one causing all the problem, though of course i may be wrong.
Click to expand...
Click to collapse
You can't boot from a signed HBOOT image because it's a plain binary file and not an android boot image. As you have unlocked the bootloader try fastboot boot with any recovery.img file (CWM or TWRP)

Sachin Thomas said:
You can't boot from a signed HBOOT image because it's a plain binary file and not an android boot image. As you have unlocked the bootloader try fastboot boot with any recovery.img file (CWM or TWRP)
Click to expand...
Click to collapse
EXCELLENT !
did this -
I:\Android Rooting\Flash>fastboot boot recovery-clockwork-5.0.2.8-pico.img
downloading 'boot.img'...
OKAY [ 0.810s]
booting...
OKAY [ 0.014s]
finished. total time: 0.834s
and now I am in CWM recovery screen.
EDIT 1: wiped all partitions.
EDIT 2 : rebooted the phone to check if it let me into the hboot menu, but it comes back to the black htc screen with 4 exclamation marks

salil_1337 said:
EXCELLENT !
did this -
I:\Android Rooting\Flash>fastboot boot recovery-clockwork-5.0.2.8-pico.img
downloading 'boot.img'...
OKAY [ 0.810s]
booting...
OKAY [ 0.014s]
finished. total time: 0.834s
and now I am in CWM recovery screen.
EDIT : wiped all partitions.
Click to expand...
Click to collapse
To be on the safer side do cute_prince's nand recovery procedure as juristokrat suggested

Sachin Thomas said:
To be on the safer side do cute_prince's nand recovery procedure as juristokrat suggested
Click to expand...
Click to collapse
i did that when i got my nand burned after installing cm10 beta 6. But AFAIK and as far as I understand, i need to place the flash_erase file into system/xbin. I am right now stuck in recovery. How am I supposed to do it from there ? is there a flashable zip for it which will run the commands via recovery ?
EDIT : this is FAR better than i expected. since I'm in recovery, adb devices spits this out -
adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
SH1BJVN07184 recovery

salil_1337 said:
i did that when i got my nand burned after installing cm10 beta 6. But AFAIK and as far as I understand, i need to place the flash_erase file into system/xbin. I am right now stuck in recovery. How am I supposed to do it from there ? is there a flashable zip for it which will run the commands via recovery ?
Click to expand...
Click to collapse
Mount your SD card in recovery and place the file in the root of the SD card. Now, if you have TWRP you can use its file manager to move it into system/xbin and set permissions to 755
If you have CWM you can type the following in adb shell:
cd /
mv /sdcard/flash_erase /system/xbin
cd system/xbin
chmod 755 flash_erase
Click to expand...
Click to collapse
Then find a newer RUU and run it

Sachin Thomas said:
Mount your SD card in recovery and place the file in the root of the SD card. Now, if you have TWRP you can use its file manager to move it into system/xbin and set permissions to 755
If you have CWM you can type the following in adb shell:
Click to expand...
Click to collapse
OK. booted via twrp, copied file from sd card, but there seems to be no xbin folder in system
EDIT : ran it directly from the sd card via the terminal in twrp, it ran without errors. rebooted the phone, still comes up to the black htc screen

salil_1337 said:
OK. booted via twrp, copied file from sd card, but there seems to be no xbin folder in system
Click to expand...
Click to collapse
Mount system

Sachin Thomas said:
Mount system
Click to expand...
Click to collapse
after mounting system, its still showing only one folder in system . lost+found. nothing else.
ran it directly from the sd card via the terminal in twrp, it ran without errors. rebooted the phone, still comes up to the black htc screen

salil_1337 said:
after mounting system, its still showing only one folder in system . lost+found. nothing else.
ran it directly from the sd card via the terminal in twrp, it ran without errors. rebooted the phone, still comes up to the black htc screen
Click to expand...
Click to collapse
Oh, the xbin folder should have got deleted when you formatted system. I don't think you can't get rid of the HTC screen without successfully flashing an RUU. Our aim is to get rid of bad blocks which prevents the RUU from getting flashed
Are you sure that it ran without errors? Move it into /system and change permission to 755 and re-run it before attempting to flash another RUU

[Q] one xl stuck

Okay, I tried putting a new rom on my at&t one xl, and it did something horribly wrong. I was able to get to recovery and it told me I had no operating system, the I tried flashing a new rom again. At this point it restarted the phone got stuck at the splash screen and now I cant even get to recovery just the fast boot and boot loader. Any help would greatly appreciated.

You haven't given any of the vital information required to help you. Please provide the following:
hboot/firmware version
S-on or s-off
Recovery version
What ROM(s) you were trying to flash
What you have done to try to recover
Sent from my Evita

timmaaa said:
You haven't given any of the vital information required to help you. Please provide the following:
hboot/firmware version
S-on or s-off
Recovery version
What ROM(s) you were trying to flash
What you have done to try to recover
Sent from my Evita
Click to expand...
Click to collapse
hboot 1.14.002
s is off
cant remember recovery version since I can't access it
I had viper rom and I was going to cyanogen mod 10.1
and I thought I had a titanium backup but my whole sd card go deleted, so I mounted my sd card and got the rom again and flashed it and at that point I couldn't go back to recovery

Did you read the OP for cm10.1? It states in the requirements that you must RUU up to the latest (3.18) to run that ROM. In terms of your recovery, just flash it again from fastboot.
Sent from my Evita

timmaaa said:
Did you read the OP for cm10.1? It states in the requirements that you must RUU up to the latest (3.18) to run that ROM. In terms of your recovery, just flash it again from fastboot.
Sent from my Evita
Click to expand...
Click to collapse
I must of completely overseen that. and sir the only option I have on my boot is fast boot, recovery, factory reset, clear storage, simlock, image crc, and power down. I don't know how to even flash things at this point.

and only options I fast boot are bootloader, reboot, reboot boot loader and powerdown

That's all you need to RUU, it's an exe file that you just run while your phone is connected in fastboot mode. You'll need top flash your recovery again, then you can flash a ROM.
Download the RUU
Run the RUU
Download recovery
Flash recovery
Flash ROM
The fastboot command to flash the recovery is:
fastboot flash recovery "recovery.img"
(The exact recovery filename, without the talking marks)
fastboot erase cache
fastboot reboot-bootloader
Now you can enter recovery on your phone, mount usb storage, copy ROM to phone, flash ROM.
Sent from my Evita

Thanks guys. My kids an idiot and did this today to his phone (my old phone). He got the information from you guys and left it to me to fix when I got home.

timmaaa said:
That's all you need to RUU, it's an exe file that you just run while your phone is connected in fastboot mode. You'll need top flash your recovery again, then you can flash a ROM.
Download the RUU
Run the RUU
Download recovery
Flash recovery
Flash ROM
The fastboot command to flash the recovery is:
fastboot flash recovery "recovery.img"
(The exact recovery filename, without the talking marks)
fastboot erase cache
fastboot reboot-bootloader
Now you can enter recovery on your phone, mount usb storage, copy ROM to phone, flash ROM.
Sent from my Evita
Click to expand...
Click to collapse
Cool glad ur all set
Sent from my HTC One XL using xda premium

[SOLVED] I can't enter into recovery mode. Please help

I broke the digitizer, so I replaced it (I think successfully). I was able to boot it once and everything worked fine. Now all I get is a bootloop with the htc logo on white background.
I wanted to install a newer rom, but I'm unable to enter recovery
If I try to enter recovery pressing vol down and power, and then select recovery and press power, I get the htc logo bootloop again
I was in rom CM 10.2 by Sultan. With S-off. I can't remember which recovery I had installed (4ext or twrp?)
What could I do?
Are there any pc tools like flashtool for Sony devices or Odin/Heimdall for Samsung ones? (preferably for ubuntu)

First eject your battery than reinsert and try again volume and power button
Sent from my HTCSensation using xda app-developers app

Mile_zdr said:
First eject your battery than reinsert and try again volume and power button
Sent from my HTCSensation using xda app-developers app
Click to expand...
Click to collapse
I've done so many times, that's the first thing I've tried.
I was thinking about using adb and fastboot commands to see if I can get to the recovery that way or at least they prompt some errors that tell me what's wrong.
But I don't know what should I do, I've always used some gui (like flashtool or heimdall or odin for other devices, no idea if there's anything like that for htc devices)

devrruti said:
I've done so many times, that's the first thing I've tried.
I was thinking about using adb and fastboot commands to see if I can get to the recovery that way or at least they prompt some errors that tell me what's wrong.
But I don't know what should I do, I've always used some gui (like flashtool or heimdall or odin for other devices, no idea if there's anything like that for htc devices)
Click to expand...
Click to collapse
from fastboot try the command
fastboot reboot recovery
otherwise reflash the recovery again
see only step 2 from here
http://forum.xda-developers.com/showthread.php?t=1631861
for tool see here
http://forum.xda-developers.com/showthread.php?t=1668276

k
rzr86 said:
from fastboot try the command
fastboot reboot recovery
otherwise reflash the recovery again
see only step 2 from here
http://forum.xda-developers.com/showthread.php?t=1631861
for tool see here
http://forum.xda-developers.com/showthread.php?t=1668276
Click to expand...
Click to collapse
ok I've tried everything i could on ubuntu, windows 7 and windows 8.1. Please more ideas?
on Ubuntu
I've installed adb and fastboot and added the file 51-android. rules. I enter fastboot mode on phone and it is recognised by pc.
sudo fastboot reboot recovery does nothing
I've downloaded 4ext recovery and uncompressed
sudo fastboot flash recovery recovery.img
sending 'recovery'
okay
writing 'recovery'
FAILED (remote: not allowed)
I've also placed the 4ext recovery zip file on the sd renamed as PG58IMG.zip, no luck either. it just says parsing, but doesn't do anything else
on windows 7 and 8 I've tried with kgs utility with the option 3 to install a recovery. however this tool didn't work. Sometimes it just closed. other times it complained about md5. I think this tool tries to download Juopunutbear windows version and fails because it is no longer available a link for the windows version
phone was rooted, bootloader unlocked, supercid... using Juopunutbear
it had a recovery installed (i think it was 4ext, but i don't remember)
it had CM 10.2 by sultanxda
i replaced the digitizer. first boot everything was working.
I rebooted to enter the recovery to install a new rom but i can't
i can't boot to rom or recovery. i just get the htc logo bootloop
fastboot tells me remote not allowed
image attached
the bootloader was unlocked, but the "Locked" word was always there if i remember well, i read this was because of unlocking with Juopunutbear instead of htc dev, but that this didn't matter

{
"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"
}
image boot

Try to flash 3.33 universal firmware (check md5 sum before flashing important ) that will give you patched hboot (unlocked) after that try to flash recovery
Edit: here is link for firmware , read the steps carefull Firmware
Sent from my HTCSensation using xda app-developers app

yes do as Mile_zdr suggested
with locked bootloader you can't do almost nothing
before flashing 3.33 universal firmware check md5 sums(important)
by the way i thought you still had unlocked bootloader
edit: because of locked bootloader you don't have access to the rom and recovery

I had unlocked the bootloader with unlimited.io juopunutbear, this is very strange. As I said, I read somewhere that the locked word is there if you use the juopunutbear method, but it was supposedly unlocked. the only thing I did was change the digitizer.
but yeah it looks like it is locked if i can't use fastboot nor recovery. thank you very much, I'll try that firmware and tell you

devrruti said:
I had unlocked the bootloader with unlimited.io juopunutbear, this is very strange. As I said, I read somewhere that the locked word is there if you use the juopunutbear method, but it was supposedly unlocked. the only thing I did was change the digitizer.
but yeah it looks like it is locked if i can't use fastboot nor recovery. thank you very much, I'll try that firmware and tell you
Click to expand...
Click to collapse
also in order to have access in all fastboot commands you need unlocked bootloader or the patched hboot

rzr86 said:
also in order to have access in all fastboot commands you need unlocked bootloader or the patched hboot
Click to expand...
Click to collapse
I am not able to flash the universal firmware 3.33 either
How should I do it?
I put it in the sd card root directory, but it doesn't do anything special either, what should I expect?
I tried this method also with the 4ext recovery zip
I wasn't able to flash 4ext recovery img with fastboot
sudo fastboot flash recovery recovery.img
gives me the remote not allowed error
~$ sudo fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.32.401.3
(bootloader) serialno: xxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxx
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4091mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 617f0a98
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.485s
Am I unlocked or not? I'm lost
How should I unlock bootloader if that is the case (I had already done so with unlimited.io juopunutbear)
All instructions are for when you are on stock locked firmware
Thanks for your patience. I bought this phone recently and everything was good until I crashed the screen. I don't want to give up but I really don't know what else I can do to fix it.

devrruti said:
I am not able to flash the universal firmware 3.33 either
Click to expand...
Click to collapse
why you are not able to flash 3.33 firmware?

Mile_zdr said:
why you are not able to flash 3.33 firmware?
Click to expand...
Click to collapse
How should i flash it?
what are the options to do it?
should i do it with fastboot? what would be the command?
So far, if i select recovery, all i get is the htc logo bootloop
Whatever I've tried with fastboot gives me remote not allowed
If i place it as a zip on the microsd with the proper name, nothing happens either
I don't know what else to do.
I know it's confusing to help this way.
I could show you a video or maybe with videocall somehow to show everything?

devrruti said:
How should i flash it?
what are the options to do it?
should i do it with fastboot? what would be the command?
So far, if i select recovery, all i get is the htc logo bootloop
Whatever I've tried with fastboot gives me remote not allowed
If i place it as a zip on the microsd with the proper name, nothing happens either
I don't know what else to do.
I know it's confusing to help this way.
I could show you a video or maybe with videocall somehow to show everything?
Click to expand...
Click to collapse
put the firmware.zip in the root of your sdcard as you did(name it as pg58img.zip if it doesn't already)
then boot into bootloader and it will scan and detect it automatically
it will ask you to update
edit: for the command i think is fastboot flash zip pg58img.zip but i am not so sure

rzr86 said:
put the firmware.zip in the root of your sdcard as you did(name it as pg58img.zip if it doesn't already)
then boot into bootloader and it will scan and detect it automatically
it will ask you to update
edit: for the command i think is fastboot flash zip pg58img.zip but i am not so sure
Click to expand...
Click to collapse
yeah I did something! Now I have 3.33, but still bootloop when turning it on and when selecting recovery.
I already had tried like you said puting the recovery or the 3.33 firmware on the sd as zip with that name but it didn't fix anything.
I was able to flash universal firmware 3.33 this way, not sure if that would be fine but i risked:
now boot looks like this compared to the image i attached on the first page
then I was able to flash 4ext recovery this way
sudo fastboot flash recovery recovery.img
it said sending ok, writing ok, finished
it didn't give me the remote not allowed error
however i still have the green htc on white bootloop. I also have this bootloop when i try to select recovery
this happens when i put the recovery zip renamed on the sd root, but nothing else
Excuse the potato camera

devrruti said:
yeah I did something!
I already had tried like you said but it didn't do anything.
I was able to flash universal firmware 3.33 this way, not sure if that would be fine but i risked:
View attachment 2670274
now boot looks like this compared to the image i attached on the first page
View attachment 2670281
then I was able to flash 4ext recovery this way
sudo fastboot flash recovery recovery.img
it said sending ok, writing ok, finished
it didn't give me the remote not allowed error
however i still have the green htc on white bootloop. I also have this bootloop when i try to select recovery
this happens when i put the recovery zip renamed on the sd root, but nothing else
View attachment 2670289
View attachment 2670290
Click to expand...
Click to collapse
now after you flashed 3.33 firmware flash recovery via fastboot step 2 from the link http://forum.xda-developers.com/showthread.php?t=1631861

Mile_zdr said:
now after you flashed 3.33 firmware flash recovery via fastboot step 2 from the link http://forum.xda-developers.com/showthread.php?t=1631861
Click to expand...
Click to collapse
I already tried that way, it says that I flashed it and went ok, however I still get the green htc on white bootloop when I select recovery or just boot.
Your phone will (re)boot, wait until you see a white screen which says "FASTBOOT USB"
Type in: fastboot flash recovery recovery.img
Wait until the flashing is finished
Type in: fastboot reboot
I had problems uploading the images on the post before, they should appear now if reloaded
I'm out of ideas, any suggestion?

devrruti said:
I already tried that way, it says that I flashed it and went ok, however I still get the green htc on white bootloop when I select recovery or just boot.
Your phone will (re)boot, wait until you see a white screen which says "FASTBOOT USB"
Type in: fastboot flash recovery recovery.img
Wait until the flashing is finished
Type in: fastboot reboot
I had problems uploading the images on the post before, they should appear now if reloaded
I'm out of ideas, any suggestion?
Click to expand...
Click to collapse
Did you delete the PG58IMG file? you got to delete. it eject your sd card and if you have sd card reader delete the file or try to go to recovery without sd card

Mile_zdr said:
Did you delete the PG58IMG file? you got to delete. it eject your sd card and if you have sd card reader delete the file or try to go to recovery without sd card
Click to expand...
Click to collapse
yeah I've tried putting different recoveries on the sd, no luck.
then I've deleted them and tried to flash them via fastboot
it all says ok, transfered and installed succesfully (no remote not allowed errors now), but i still get the htc bootloop then if i select recovery or boot normally
i also tried to fastboot flash the recovery without sd card, but still the same

devrruti said:
yeah I've tried putting different recoveries on the sd, no luck.
then I've deleted them and tried to flash them via fastboot
it all says ok, transfered and installed succesfully (no remote not allowed errors now), but i still get the htc bootloop then if i select recovery or boot normally
i also tried to fastboot flash the recovery without sd card, but still the same
Click to expand...
Click to collapse
did you try to go to recovery without sd card or use another sd card (not to flash just go to recovery with other sd card)
otherwise i don't have any other thoughts mate... :/

[Q] How to erase all data with ADB command?

Hello,
I have an issue with my sensation. The screen stays black. I can boot on my ROM, the bootloader (fastboot), and the recovery, but I can't see nothing.
Someone wants to buy my phone. But I can't sell the phone with my personal data.
I need to know how to erase all data in my phone with ADB command line under fastboot.
Please, help me.

bobatomix said:
Hello,
I have an issue with my sensation. The screen stays black. I can boot on my ROM, the bootloader (fastboot), and the recovery, but I can't see nothing.
Someone wants to buy my phone. But I can't sell the phone with my personal data.
I need to know how to erase all data in my phone with ADB command line under fastboot.
Please, help me.
Click to expand...
Click to collapse
there is an option from bootloader to factory reset the device but i don't know what exactly is doing
did you try to flash an official rom(RUU.exe)?

rzr86 said:
there is an option from bootloader to factory reset the device but i don't know what exactly is doing
did you try to flash an official rom(RUU.exe)?
Click to expand...
Click to collapse
For factory reset : I try but I'm not sure it worked, because I see nothing on the screen.
For official rom(RUU.exe) : I try but it didn't work.
For information my phone is S-OFF.
For me, the solution is to do that with adb's commands. I want to do a full wipe .

bobatomix said:
For factory reset : I try but I'm not sure it worked, because I see nothing on the screen.
For official rom(RUU.exe) : I try but it didn't work.
For information my phone is S-OFF.
For me, the solution is to do that with adb's commands. I want to do a full wipe .
Click to expand...
Click to collapse
since you are on S-OFF change your cid to supercid and flash whatever ruu you want
by the way what problem did you have with ruu?

rzr86 said:
since you are on S-OFF change your cid to supercid and flash whatever ruu you want
by the way what problem did you have with ruu?
Click to expand...
Click to collapse
The phone is S-OFF and supercid.
The message with RUU is ERROR [120] : battery less than 30% - but the battery is full.
I tried this http://forums.androidcentral.com/ge...oyo-get-error-120-battery-less-than-30-a.html , and it didn't work.
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27
(bootloader) version-baseband: 11.24A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.33.401.1
(bootloader) serialno: xxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxx
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG58*****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4172mV
(bootloader) partition-layout: Generi
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 617
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse

bobatomix said:
The phone is S-OFF and supercid.
The message with RUU is ERROR [120] : battery less than 30% - but the battery is full.
I tried this http://forums.androidcentral.com/ge...oyo-get-error-120-battery-less-than-30-a.html , and it didn't work.
Click to expand...
Click to collapse
did you try what it says in post #15 of that link?
try with a different battery if you have
also wipe battery stats from recovery but i don't think it will do anything

rzr86 said:
did you try what it says in post #15 of that link?
try with a different battery if you have
also wipe battery stats from recovery but i don't think it will do anything
Click to expand...
Click to collapse
I tried with my anker. It doesn't work neither.

bobatomix said:
I tried with my anker. It doesn't work neither.
Click to expand...
Click to collapse
if i remember well it has been reported that issue before here in sensation forum
maybe you can find something here
i don't know what else to suggest

rzr86 said:
if i remember well it has been reported that issue before here in sensation forum
maybe you can find something here
i don't know what else to suggest
Click to expand...
Click to collapse
Okk, thanks for your time and your suggestions.

If you format the data partition it will clear or your personal data on your device.Just boot into recovery and wipe data partition.
You could also use the command fastboot erase data.It would be nice to delete cache too (fastboot erase cache).
If you erase data partition it could cause rom instabilities or a not working rom.In my opinion the most safe way to clear all your personal data is to make a full wipe (using 4ext recovery) and to reflash your (custom) rom.
If you have the original rom with original recovery you could use the "factory reset" option from your bootloader to reset the phone.If you have a cwm or other recovery it probably won't work.In any case an RUU would be a very good solution.Have you try to flash your phone using a rom.zip from an original RUU?You have to rename it to PG58IMG.zip and you put it to your sdcard in order to flash it from your bootloader.

Gatosbil said:
If you format the data partition it will clear or your personal data on your device.Just boot into recovery and wipe data partition.
You could also use the command fastboot erase data.It would be nice to delete cache too (fastboot erase cache).
If you erase data partition it could cause rom instabilities or a not working rom.In my opinion the most safe way to clear all your personal data is to make a full wipe (using 4ext recovery) and to reflash your (custom) rom.
If you have the original rom with original recovery you could use the "factory reset" option from your bootloader to reset the phone.If you have a cwm or other recovery it probably won't work.In any case an RUU would be a very good solution.Have you try to flash your phone using a rom.zip from an original RUU?You have to rename it to PG58IMG.zip and you put it to your sdcard in order to flash it from your bootloader.
Click to expand...
Click to collapse
It's very difficult to do something with no screen. I will try the PG58IMG.zip's method. But this method, I think, keeps all data.
I need to do a full wipe without screen, just with adb on the fastboot.

bobatomix said:
It's very difficult to do something with no screen. I will try the PG58IMG.zip's method. But this method, I think, keeps all data.
I need to do a full wipe without screen, just with adb on the fastboot.
Click to expand...
Click to collapse
fastboot oem rebootruu
fastboot erase userdata
and maybe
fastboot erase system
should remove everything

Cant fastboot boot twrp.img - OnePlus 6

I dont understand why It wont boot into the twrp img.
I have tried a few times now after i have deleted the content of the phone twice, and it still wont work..
I do have an unlocked bootloader, and I have followed different guides tried to read up on it myself, but ive tried all day, i dont know what is wrong.
Everytime i try to do "fastboot boot twrp.img" it wont work, it says okay, booting..., okay, finished. then my phone starts going into fastbootmode, but is then just stuck on the black screen with the 1+ logo with the text under it saying fastboot mode.
Im running android 10
The files i use is :
twrp-3.3.1-2-enchilada.img
twrp-installer-3.3.0-0-enchilada.zip (never gotten to this stage)
Magisk-v20.3.zip
I hope some1 is able to help me out thanks for reading

use newest twrp file image

mcboums said:
use newest twrp file image
Click to expand...
Click to collapse
I also did that, same result

Same issue here, had to settle for a magisk patched boot image

0x0null said:
Same issue here, had to settle for a magisk patched boot image
Click to expand...
Click to collapse
Same issue here....twrp-3.3.1-2-enchilada.img is last image

use this twrp
hello i just stuck at that problem too my phone stuck at fastboot mode similar to boot loop i find the solution by following this post https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213

Trevasta said:
hello i just stuck at that problem too my phone stuck at fastboot mode similar to boot loop i find the solution by following this post https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213
Click to expand...
Click to collapse
Tried all that too, same issue

Ive used 'fastboot flash boot twrp.img' in the past to get into twrp then flash stock boot.img in twrp to restore boot, then flashing twrp.zip in twrp.

gffmac said:
Ive used 'fastboot flash boot twrp.img' in the past to get into twrp then flash stock boot.img in twrp to restore boot, then flashing twrp.zip in twrp.
Click to expand...
Click to collapse
I'm not the OP but that also does not work.

Stuck in fastboot upgrading to OOS 10
Awkwardguy9000 said:
I dont understand why It wont boot into the twrp img.
Same problem here, after trying to upgrade from OOS 9 to OOS10 (clean flash like described in https://forum.xda-developers.com/oneplus-6/how-to/official-oxygenos-5-1-5-ota-oneplus-6-t3794232). After Flashing OOS10.03, latest TWRP bluespark 9.109, and Magisk 20.4, the phone got stuck in the "bootloader unlocked" startup screen.
Maybe the problem was I came from 9.08 (seems one first has to go to 9.09 ?), maybe the problem was Magisk 20.4 not working well with TWRP ?
In any case I decided to restore my nandroid backup. However, after this I lost the recovery, and now cant flash it back with fastboot (same symptoms as described elsewhere in this post). None of the belopw work:
fastboot flash recovery TWRPxxx (tells me recovery_a not found)
fastboot flash boot TWRPxxx (works, but can't boot into recovery anyway)
fastboot boot TWRPxxx (works, but doen't boot into recovery )
I noticed that at startup I see for a moment the Android 10 logo (the little green man), but the OOS I restored with the nandroid backup is 9.08 ! Presumably the phone is now stuck in the Nirwana between Pie and Q.
My question is now the following:
How can I use fastboot to flash a new TWRP, OOS amd Magisk without loosing my internal disk data ? Which version of TWRP, OOS, and Magisk should I use ? Is it best to first go back to OOS 9 or should I go rightaway to OOS 10 ?
Thanks
PS: Could I try to swich the active partition ? fastboot getvar all tells me I am in slot a
bootloader) has-slot:modem:yes
(bootloader) has-slot:system:yes
(bootloader) current-slot:a
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:6
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:yes
(bootloader) slot-retry-count:a:7
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:no
(bootloader) slot-count:2
(bootloader) secure:yes
Edit: Managed to go back to TWRP recovery by switching the active partition (fastboot --set-active=b). But what next? Dont want to loose that slot as well..
EDIT: I now actually managed to boot back to recovery (fastboot boot twrp-3.3.1-18-enchilada-Q-mauronofrio.img). I could save important files back to the PC (via simple drag and drop), including the Nandroid Backup (OOS9.08), music, photos etc..
In principle I could now try to flash a new ROM.zip, but which one ? Should I go back to the old OOS (9.08), or to 9.09 so I can upgrade to 10 later ? But the TWRP version is Android Q, so maybe I should try 10.0 or 10.3 ?
Would anybody know which (if any) of these possibilities has the best chance to succeed without wiping the internal data ?
If a total wipe is unavoidable, what is the best way to proceed ? Is via TWRP recovery possible (clean install, but leave internal data intakt),or do I need fastboot flash which wipes all user data es well (as described https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665) ?
Click to expand...
Click to collapse

Problem Solved
I followed this post https://forum.xda-developers.com/showpost.php?p=78915106&postcount=2
(reflash same ROM and Magisk versions as those originally installed, then restore nandroid backup).
3 things to note which were not obvious to me:
- Unzipp ALL files into one single folder (same ROMs have zips within zips)
- use the "flash-all-partitions-fastboot.bat" file,
- answer NO to the first question "Wipe all data (recommended)". If not, the internal data (data/media) will be wiped as well, including your nandroid backup and other info (music, photo..). If you have to wipe, make sure the backup is on the PC