Database Info

Help me please (noob @ flashing ROMS)

I loaded my Rogers HTC one X with the CyanogenMod 10 - Endeavor Unleashed | 027 | UNIFIED HBOOT. It worked for a bit but is now stuck in the loading screen. I connected it to my PC and put it in fastboot and attempt to reflash the boot img and nothing changes. I have attempted to find an original RUU as mine is corrupted.
I have read the forums and see alot of fixes if you can access the phone to move the files to the SD however I cant get to that point. I am sure this has been answered somewhere but i haven't been able to find it as yet.
This is my first attempt to use a ROM.. The phone was unlocked via HTC dev. I have since read I should have also turned the S-off but I missed that before I flashed the ROM.
Any ideas would be appreciated.
Here is the info from the device.
c:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.11.0000
(bootloader) version-baseband: 0.18as.32.09.28L
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.94.631.3
(bootloader) serialno: HT249W305429
(bootloader) imei: 359691042187149
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4200mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 8d23f0c0
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.076s
c:\Android>
I originally posted this in the wrong forum. I was told not to use the international ROMS. I did try flashing cm-10-20121126-NIGHTLY-evita using the One X One Click v 1.9. When I reboot it it just gives me the CM loading screen.

First, we don't have S-Off yet. Whoever told you that doesn't know what they're talking about.
Flashing international/Tegra3 roms on this phone, as you've learned, won't work. There are certain Tegra3 roms that will hard-brick you, but I've seen people recover from flashing the wrong CM10. If you can still get to the bootloader, you're okay.
It's possible you corrupted your sd card. Try reformatting it.

Drag0nus said:
I loaded my Rogers HTC one X with the CyanogenMod 10 - Endeavor Unleashed | 027 | UNIFIED HBOOT. It worked for a bit but is now stuck in the loading screen. I connected it to my PC and put it in fastboot and attempt to reflash the boot img and nothing changes. I have attempted to find an original RUU as mine is corrupted.
I have read the forums and see alot of fixes if you can access the phone to move the files to the SD however I cant get to that point. I am sure this has been answered somewhere but i haven't been able to find it as yet.
This is my first attempt to use a ROM.. The phone was unlocked via HTC dev. I have since read I should have also turned the S-off but I missed that before I flashed the ROM.
Any ideas would be appreciated.
Here is the info from the device.
c:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.11.0000
(bootloader) version-baseband: 0.18as.32.09.28L
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.94.631.3
(bootloader) serialno: HT249W305429
(bootloader) imei: 359691042187149
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4200mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 8d23f0c0
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.076s
c:\Android>
I originally posted this in the wrong forum. I was told not to use the international ROMS. I did try flashing cm-10-20121126-NIGHTLY-evita using the One X One Click v 1.9. When I reboot it it just gives me the CM loading screen.
Click to expand...
Click to collapse
Also, try to format system and do factory reset using TWRP
While in a directory with ADB, fastboot and TWRP (custom recovery), Do the following command
fastboot boot TWRP.img
Then, in TWRP, go to wipe
Then go toilet pap--- oops
Jk but go to Factory Reset
When it's done, do wipe system
Then, finally install a rom and flash the kernel
Hope I helped!

Tanmaynarang said:
Also, try to format system and do factory reset using TWRP
While in a directory with ADB, fastboot and TWRP (custom recovery), Do the following command
fastboot boot TWRP.img
Then, in TWRP, go to wipe
Then go toilet pap--- oops
Jk but go to Factory Reset
When it's done, do wipe system
Then, finally install a rom and flash the kernel
Hope I helped!
Click to expand...
Click to collapse
Thank you for the idea.
I tried this but it goes to the HTC screen and stops.
Also I am now noticing that my SD is not accessible. I think I did something way wrong when I originally flashed the rom.

Drag0nus said:
Thank you for the idea.
I tried this but it goes to the HTC screen and stops.
Also I am now noticing that my SD is not accessible. I think I did something way wrong when I originally flashed the rom.
Click to expand...
Click to collapse
Did you wipe/factory reset in bootloader? That will completely wipe your sd card so that you have to reformat it.

iElvis said:
Did you wipe/factory reset in bootloader? That will completely wipe your sd card so that you have to reformat it.
Click to expand...
Click to collapse
Yes I did. The thing is I can't access the SD card to format it. when I try to mount the SD from the phone it does nothing either. I am very lost now.

Drag0nus said:
Yes I did. The thing is I can't access the SD card to format it. when I try to mount the SD from the phone it does nothing either. I am very lost now.
Click to expand...
Click to collapse
You need to mount it from your computer.

iElvis said:
You need to mount it from your computer.
Click to expand...
Click to collapse
Ok thanks. Can you point me in the right direction to be able to do so?

Drag0nus said:
Ok thanks. Can you point me in the right direction to be able to do so?
Click to expand...
Click to collapse
Just plug it in and navigate to your phone in Explorer. You should then get a prompt to format it.

iElvis said:
Just plug it in and navigate to your phone in Explorer. You should then get a prompt to format it.
Click to expand...
Click to collapse
That's the thing. I hook it to the PC, it will open sence but it doesnt show in explorer now.

Drag0nus said:
That's the thing. I hook it to the PC, it will open sence but it doesnt show in explorer now.
Click to expand...
Click to collapse
Are you in bootloader? Try a different cable, or different USB port.
Try plugging it in, shutting down, and rebooting to bootloader. Sometimes it takes some effort to get it to show up.

Go to my computer. Right click where it says removable storage .... format.. it WILL erase everything. But hey, at least you Still have a phone right
Sent from my One X using Tapatalk 2

Just run rogers 1.94 ruu

The problem is that the computer does not see it as a storage device because the SD card doesn't show up I have tried multiple computers and multiple cables any suggestions
Sent from my SGH-I747M using xda app-developers app

try this
http://forums.team-nocturnal.com/showthread.php/1050

You are going into TWRP and clicking mount usb storage to get windows to recognize it right?

codeprimate said:
try this
http://forums.team-nocturnal.com/showthread.php/1050
Click to expand...
Click to collapse
Thanks. this worked and I just finished flashing the new ROM and am waiting for it to complete and then I should be golden.

[Q] How to unlock bootloader with no boot on original everything???

Hi all,
So I have my firends TF300 or TF300T that does not boot. It hangs on the Asus splash screen but I can go into the recovery mode.
This tablet went ahead and messed up on its own, no flashing or unrooting attempted :/
So, now I cant get the boot unlock from Asus, so I cant flash a new recovery or rom... is there anyway to get around this??
I can connect to USB mode from the recovery, but the android and RCK both stop at "signature match".
When wiping data I get the following error:
Code:
Booting failed
unrecoverable bootloader error (0x00000000)
The reason I dont know the exact model number is because I cant boot and find any information about the tablet
Any help greatly appreciated.

Can you copy stock Asus rom to sd and install it from recovery?

stenc55 said:
Can you copy stock Asus rom to sd and install it from recovery?
Click to expand...
Click to collapse
No problem to copy stock to SD, but how would I install from recovery with no CWM and locked bootloader?

Snarlster said:
No problem to copy stock to SD, but how would I install from recovery with no CWM and locked bootloader?
Click to expand...
Click to collapse
You wrote that you can get into recovery. If it is stock Asus rom then original recovery is OK, because stock rom is signed.
Or you can try with ADB or Fastboot.

stenc55 said:
You wrote that you can get into recovery. If it is stock Asus rom then original recovery is OK, because stock rom is signed.
Or you can try with ADB or Fastboot.
Click to expand...
Click to collapse
Thanks for that, I was under the assumption that I couldn't install the stock also!
But Im far from there yet, I just spent many hours trying to install the stock that I downloaded from asus website in various way's. The file I downloaded was:
HTML:
US_epaduser_10_4_2_20_UpdateLauncher
This computer is bought in the US, and this is the exact version nr that they describe in the recovery.
Fastboot lists the device and now I've tried 2 different computers and different usb ports with:
Code:
fastboot -i 0x0B05 flash system blob
And it erases the system and say's that its going to write the system... but thats it. After a long time of waiting (many times), I eventually unplug and get an error:
FAILED (data transfer failure (Too many links))
I also tried copying the file to the SD card (two of them) both with and without renaming it "epad_update.zip" but that gives me a dead (lying) android with a triangle above the belly...
Then sometimes when trying to flash with fastboot I start getting the error:
HTML:
load_file: could not allocate 818942949 bytes
error: cannot load 'blob': Not enough space
But I found a way to get rid of that by: "flashboot update US_epad-user-10.4.2.20_2.zip" which gives an error but allows me to flash again.
I was thinking the cord might be the problem but then why wouldn't the SD card method work?
So, I'm confused
You mention ADB? I thought that was only possible if I would boot into android?

I just did the "fastboot getvar all" and figured it could possibly help someone to help me, so I'll toss it in here.
HTML:
(bootloader) version-bootloader: 1.0
(bootloader) version-baseband: 2.0
(bootloader) version: 0.4
(bootloader) serialno: some.long.number, possibly private? :)
(bootloader) mid: 001
(bootloader) product: Cardhu
(bootloader) secure: yes
(bootloader) unlocked: no
(bootloader) partition-size:bootloader: 0x0000000000800000
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:recovery: 0x0000000000800000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:boot: 0x0000000000800000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:system: 0x0000000030000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x000000001ac00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x00000006e5680000
(bootloader) partition-type:userdata: ext4
all:
finished. total time: 0.083s
Any help greatly appreciated!

Snarlster said:
I just did the "fastboot getvar all" and figured it could possibly help someone to help me, so I'll toss it in here.
HTML:
(bootloader) version-bootloader: 1.0
(bootloader) version-baseband: 2.0
(bootloader) version: 0.4
(bootloader) serialno: some.long.number, possibly private? :)
(bootloader) mid: 001
(bootloader) product: Cardhu
(bootloader) secure: yes
(bootloader) unlocked: no
(bootloader) partition-size:bootloader: 0x0000000000800000
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:recovery: 0x0000000000800000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:boot: 0x0000000000800000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:system: 0x0000000030000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x000000001ac00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x00000006e5680000
(bootloader) partition-type:userdata: ext4
all:
finished. total time: 0.083s
Any help greatly appreciated!
Click to expand...
Click to collapse
I also tried copying the file to the SD card (two of them) both with and without renaming it "epad_update.zip" but that gives me a dead (lying) android with a triangle above the belly...
The above line is bothersome. You don't rename the zip file you unzip once and find another zip which you place on your sdcard and boot into stock recovery, as when you got the red triangle.
Good Luck!

tobdaryl said:
I also tried copying the file to the SD card (two of them) both with and without renaming it "epad_update.zip" but that gives me a dead (lying) android with a triangle above the belly...
The above line is bothersome. You don't rename the zip file you unzip once and find another zip which you place on your sdcard and boot into stock recovery, as when you got the red triangle.
Good Luck!
Click to expand...
Click to collapse
I knew I didn't need to rename it, and I didn't for the first 20 times As that failed, I found this on some forum and gave it a try.
Booting into stock recovery gives you the red triangle? do you mean with a dead android underneath? After a while of the dead android with triangle, it just turns off... I dont get the huge triangle sign like I do on my galaxy... this one has a broken android included. any hints on that?

Snarlster said:
I knew I didn't need to rename it, and I didn't for the first 20 times As that failed, I found this on some forum and gave it a try.
Booting into stock recovery gives you the red triangle? do you mean with a dead android underneath? After a while of the dead android with triangle, it just turns off... I dont get the huge triangle sign like I do on my galaxy... this one has a broken android included. any hints on that?
Click to expand...
Click to collapse
I just used the red triangle since you were familiar with how to get there. I was hoping your recovery would take over and install the proper zip.
Rename the once unzipped file EP201_768_SDUPDATE.zip and try the exact same procedure as before.
Sorry I didn't put these together on the other post. Long week!

tobdaryl said:
I just used the red triangle since you were familiar with how to get there. I was hoping your recovery would take over and install the proper zip.
Rename the once unzipped file EP201_768_SDUPDATE.zip and try the exact same procedure as before.
Sorry I didn't put these together on the other post. Long week!
Click to expand...
Click to collapse
Aww, that was promising! I saw the android working for about 3 seconds... then it died again with open belly container and red triangle exclamation mark
Why would renaming it like this make a difference?

Snarlster said:
Aww, that was promising! I saw the android working for about 3 seconds... then it died again with open belly container and red triangle exclamation mark
Why would renaming it like this make a difference?
Click to expand...
Click to collapse
I can't say but for me when one doesn't work the other may. Asus has several methods of delivery these are the two which have been used with success in your situation.
Asus also uses dlpkgfile with the zip extension removed for ota updates but they are much smaller files and the updater-script is handled differently. I admit I have not tried to get stock recovery to process them from the bootloader. You can try as you can't get much worse.
Keep an eye on this thread and I'll try to do some searching, going through notes, and thinking and report back if anything else comes up.
I won't be able to do this until 3-10-2013 unless I get a break. Sorry.
I don't have any other methods that can be done with stock recovery and locked bootloader!
I'm sorry.

tobdaryl said:
I can't say but for me when one doesn't work the other may. Asus has several methods of delivery these are the two which have been used with success in your situation.
Asus also uses dlpkgfile with the zip extension removed for ota updates but they are much smaller files and the updater-script is handled differently. I admit I have not tried to get stock recovery to process them from the bootloader. You can try as you can't get much worse.
Keep an eye on this thread and I'll try to do some searching, going through notes, and thinking and report back if anything else comes up.
I won't be able to do this until 3-10-2013 unless I get a break. Sorry.
I don't have any other methods that can be done with stock recovery and locked bootloader!
I'm sorry.
Click to expand...
Click to collapse
I'll keep an eye out for sure, actually have been refreshing the page but didn't notice that it went over to second page
Thanks for the reply, I'll also post if I find something, but at this point it seems pretty hopeless... perhaps I'll start another thread since the topic on this one is incorrect now that I know I can flash stock recovery instead of trying to unlock the bootloader, I'll also post the link to the new thread when that happens
Thanks again for your help, if you get any ideas im all ears

I just broke the whole phone..

Hello! Before you guys flame me with messages of how much dumb I am or anything similar - don't bother, i already know it and i regret it...
So... I have AT&T HTC One X, with Hboot 2.14, CID CWS__01 which i just destroyed as much as i could >.> Let me reproduce things i've tried..
First of i changed my CID to 11111111 and unlocked the bootloader - took me an hour, but i did it and it was working...
I've installed recovery, even rooted the ROM... But that wasn't enough - i wanted to install ParanoidAndroid ( and i didn't read that it needs S-OFF, realized that just after i installed it and rebooted the phone )..
So after a reboot, the white HTC logo it just went black screen and nothing else... So i've began to look up on forums if someone else had this kind of a problem...
Then i tried another 2 ROM's, which worked as well as PA - just black screen...
So i thought - maybe i'll do everything from scratch ? Why not, I changed CID back to stock, wiped everything etc. and locked the bootloader....
But now I've got a weird problem - i can't change CID with "fastboot oem writecid" - it returned me error
(bootloader) elite_init_sd, SD card already power on
(bootloader) sdhw_7xxx_open: id=0
(bootloader) [SD_HW_ERR] SD: No device attached
(bootloader) 902910 902E20
FAILED (status read failed (No such file or directory))
finished. total time: 1.282s
Click to expand...
Click to collapse
So now i have no access to recovery, so i can't even do anything to the storage, the phone doesn't boot up, tried RUU for ATT version ( RUU_Evita_UL_ATT_US_1.44.502.1_Radio_0.15.3201.09_release_249105 - i guess its for HBoot 1.44, not 2.14 >.> ) it just showed me an error that it couldn't send data to the phone and i should check my connection to the phone ( drivers are installed and working fine )
I've also tried fastbooting the OTA zip to the phone - well, the phone is on S-ON and it just declines any zip that i try to flash
Also i lost connection to ADB - its impossible to connect to it while phone is in bootloader, right? : /
So i'm left with empty phone without any rom, recovery - anything...
Is there any way of fixing it ? Its 5th hour where i just sit and try to look up for any information, but I just can't find anything...
I guess i just hard bricked the phone and i can try to play some volleyball with it >.>

Your mistake was thinking that you needed s-off to flash the ROM(s), you don't, all you needed to do was flash the boot.img via fastboot after flashing the ROM with your recovery. There's an Evita FAQ thread which contains this information stickied at the top of the q&a section you've posted this thread in . This is in no way intended to flame you, just show you the catalyst point for this mayhem.
Anyway, what is your current CID? Check it with this command:
Code:
fastboot oem readcid
You must be connected in fastboot mode (bootloader) in order for fastboot commands to work (and in answer to your question, no, adb does not work in fastboot mode, only in Android and in recovery).
Transmitted via Bacon

thanks for Your reply : )
My current CID is CWS__001. Im posting the whole information from fastboot
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 0.24p.32.09.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT28GW304238
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: low
(bootloader) battery-voltage: 3403mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97c9a06e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.094s
Click to expand...
Click to collapse
I should mention that the battery was at ~95% at the time i was trying to flash/do anything.
So, is there any way to make at least recovery working? As for now i flash recovery using fastboot flash, but that does nothing - it says that its done, but when i get into bootloader and check recovery then enter it, it goes to white htc logo and goes back to bootloader >.>
EDIT!!!!!
I managed to get it working! I downloaded RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial which worked flawlessly and stock ROM just booted up! Jesus christ, thank You internet for providing exact links to the RUU's etc >.> I guess i'll try to not brick the phone again ^^ Thanks for the reply again : )
Topic can be closed now : )

prechcik said:
thanks for Your reply : )
My current CID is CWS__001. Im posting the whole information from fastboot
I should mention that the battery was at ~95% at the time i was trying to flash/do anything.
So, is there any way to make at least recovery working? As for now i flash recovery using fastboot flash, but that does nothing - it says that its done, but when i get into bootloader and check recovery then enter it, it goes to white htc logo and goes back to bootloader >.>
EDIT!!!!!
I managed to get it working! I downloaded RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial which worked flawlessly and stock ROM just booted up! Jesus christ, thank You internet for providing exact links to the RUU's etc >.> I guess i'll try to not brick the phone again ^^ Thanks for the reply again : )
Topic can be closed now : )
Click to expand...
Click to collapse
Glad to see you're all working now. But you need to edit your IMEI out of your post asap, never post your IMEI publicly.
Transmitted via Bacon

Software Information Screen

My power button quit working, I'm within the 1 year warranty period, and I need to go back to stock after I get my replacement.
Before I call VZW, since I'm rooted and using nV ROM, and I know they ask about the Software, does anyone have a screen shot of the Stock Software screen, Kit Kat unless LP has been pushed?
Thanks!
Sent from my HTC6525LVW using XDA Premium 4 mobile app

EvoNotion said:
My power button quit working, I'm within the 1 year warranty period, and I need to go back to stock after I get my replacement.
Before I call VZW, since I'm rooted and using nV ROM, and I know they ask about the Software, does anyone have a screen shot of the Stock Software screen, Kit Kat unless LP has been pushed?
Thanks!
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
They can see more information than you can tell them. Best bet is to be stock during that call.

Thanks for that input.
So, since the new phone arrived, I've been trying to restore my old phone to stock, S-OF, Unroot and Locked boot loader, etc.
I'm able to ADB into fastboot, however for whatever reason I cannot load the 06BIMG.zip(not at my computer)
Fastboot simply reboots immediately when I adb reboot boatloader.
Is there another way to get a stock image on the phone, remove the red text at boot up, s-off, lock boot loader with stock recovery and unroot?
Everything I've tried seems to be hinged on that fastboot rebooting issue.
Thanks
Sent from my HTC6525LVW using XDA Premium 4 mobile app

EvoNotion said:
Thanks for that input.
So, since the new phone arrived, I've been trying to restore my old phone to stock, S-OF, Unroot and Locked boot loader, etc.
I'm able to ADB into fastboot, however for whatever reason I cannot load the 06BIMG.zip(not at my computer)
Fastboot simply reboots immediately when I adb reboot boatloader.
Is there another way to get a stock image on the phone, remove the red text at boot up, s-off, lock boot loader with stock recovery and unroot?
Everything I've tried seems to be hinged on that fastboot rebooting issue.
Thanks
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
0P6BIMG.zip ?

I typed it from my phone whilst I was enjoying the evening outside. Just the only numbers in my head.
I'm downloading your RUU exe right now Dottat. Didn't realize you're local by an hour to me.
thanks!

dottat said:
0P6BIMG.zip ?
Click to expand...
Click to collapse
So I downloaded your EXE, and I get a failure in regard that it reboots to the HTC logo and the phone reboots immediately, causing the program to fail.
Error 155: unknown error
This is the same problem i was having when trying to do the fastboot push of the RUU I had downloaded previously.
Image version is 1.54.401.10
What ever can i do?

EvoNotion said:
So I downloaded your EXE, and I get a failure in regard that it reboots to the HTC logo and the phone reboots immediately, causing the program to fail.
This is the same problem i was having when trying to do the fastboot push of the RUU I had downloaded previously.
Image version is 1.54.401.10
What ever can i do?
Click to expand...
Click to collapse
Try flashing official stock vzw firmware via SD card. Are your mid and cid stock?
401 isn't vzw firmware BTW

dottat said:
0P6BIMG.zip ?
Click to expand...
Click to collapse
dottat said:
Try flashing official stock vzw firmware via SD card. Are your mid and cid stock?
401 isn't vzw firmware BTW
Click to expand...
Click to collapse
I just remember last year downloading and installing the nV Rom which was 4.4.2. and updating the radios.
I've tried the 0p6bimg.zip method in fastboot, but it fails as well. Maybe I'm doing it wrong, but it's in the root of the SD card.

EvoNotion said:
I just remember last year downloading and installing the nV Rom which was 4.4.2. and updating the radios.
I've tried the 0p6bimg.zip method in fastboot, but it fails as well. Maybe I'm doing it wrong, but it's in the root of the SD card.
Click to expand...
Click to collapse
I can do a team viewer session with you this weekend to take a look with you if you want

dottat said:
I can do a team viewer session with you this weekend to take a look with you if you want
Click to expand...
Click to collapse
That would be tits man. I'll be in Dover tomorrow night if you want to check it out live....LMK

EvoNotion said:
That would be tits man. I'll be in Dover tomorrow night if you want to check it out live....LMK
Click to expand...
Click to collapse
Depends on what time...lol. I work in Lancaster during the week a lot.

dottat said:
Depends on what time...lol. I work in Lancaster during the week a lot.
Click to expand...
Click to collapse
You tell me, I'll probably get out of work around 3pm and head down to York. I have to pick up tools from a friend that's borrowing them for work around 5/530, so whenever.
Since the PWR buttons not working, I'm not able to select HBOOT at the bootloader screen, and the commands I was using to get the HTC black screen fail to push. However, I just renamed your ZIP file and will try again and report back

EvoNotion said:
You tell me, I'll probably get out of work around 3pm and head down to York. I have to pick up tools from a friend that's borrowing them for work around 5/530, so whenever.
Since the PWR buttons not working, I'm not able to select HBOOT at the bootloader screen, and the commands I was using to get the HTC black screen fail to push. However, I just renamed your ZIP file and will try again and report back
Click to expand...
Click to collapse
BTW...from a booted ROM the command adb reboot oem-78
Will land you in ruu mode.

dottat said:
BTW...from a booted ROM the command adb reboot oem-78
Will land you in ruu mode.
Click to expand...
Click to collapse
well now, learn something new everyday. Got me to the HTC screen, and then it rebooted though.

EvoNotion said:
well now, learn something new everyday. Got me to the HTC screen, and then it rebooted though.
Click to expand...
Click to collapse
Can you adb reboot-bootloader and get a fastboot getvar all.
X out your imei and sn

dottat said:
Can you adb reboot-bootloader and get a fastboot getvar all.
X out your imei and sn
Click to expand...
Click to collapse
C:\Users\Abraham\Documents>adb kill-server
C:\Users\Abraham\Documents>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Users\Abraham\Documents>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.027s]
finished. total time: 0.037s
C:\Users\Abraham\Documents>fastboot flash zip 0P6BIMG.zip
target reported max download size of 1826418688 bytes
sending 'zip' (1726320 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 8.723s
C:\Users\Abraham\Documents>adb reboot bootloader
C:\Users\Abraham\Documents>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.0926
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.1700.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXX
(bootloader) imei: XXXXX
(bootloader) imei2: Not Support
(bootloader) meid: 99000429333087
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.141s
C:\Users\Abraham\Documents>

EvoNotion said:
C:\Users\Abraham\Documents>adb kill-server
C:\Users\Abraham\Documents>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Users\Abraham\Documents>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.027s]
finished. total time: 0.037s
C:\Users\Abraham\Documents>fastboot flash zip 0P6BIMG.zip
target reported max download size of 1826418688 bytes
sending 'zip' (1726320 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 8.723s
C:\Users\Abraham\Documents>adb reboot bootloader
C:\Users\Abraham\Documents>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.0926
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.1700.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXX
(bootloader) imei: XXXXX
(bootloader) imei2: Not Support
(bootloader) meid: 99000429333087
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.141s
C:\Users\Abraham\Documents>
Click to expand...
Click to collapse
Try flashing this zip the same exact way...
https://www.androidfilehost.com/?fid=95916177934537898

dottat said:
Try flashing this zip the same exact way...
https://www.androidfilehost.com/?fid=95916177934537898
Click to expand...
Click to collapse
Should I rename it to something?

EvoNotion said:
Should I rename it to something?
Click to expand...
Click to collapse
Should not need to

dottat said:
Try flashing this zip the same exact way...
https://www.androidfilehost.com/?fid=95916177934537898
Click to expand...
Click to collapse
Got half way through and now I'm at the four exclamation marks on the corners

Messed up installing 5.1.11. now only fastboot boots and can't boot twrp image.

i tried to install the newest 5.1.11 in full ( as i am magisk rooted, twrp installed, and bootloader unlocked). i kept getting system ui crashes over and over and eventually, after so many, the phone just powers down by itself. I had tried clearing cache after going back into twrp. Rebooted. Same ui issue. Then i decided to restore a backup in twrp i had made a few weeks ago stored on internal memory. This was a bad idea. It said it restored successfully but upon reboot, i only get fastboot now. i think it is communicating with fastboot but when i try to fastboot boot twrp-3.2.1-0 (or 3.2.2-0) i get, "remote: Failed to load/authenticate boot image: Load Error". I do not know what to do and am hoping you guys can figure out how to fix this. Any attempt to enter recovery via buttons results in fastboot booting. restart is also fastboot.
This is what my phone says:
FastBoot mode
Product_name- sdm845
variant- sdm ufs
basband version-
serial- it's there
secure boot- yes
device state- unlocked
Don't know if this helps fastboot getvar all reports this:
C:\Adb\OnePlus 6 Files>fastboot getvar all
(bootloader) unlocked:yes
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3837
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) variant:SDM UFS
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x1B800B7000
(bootloader) partition-type:system_a:ext4
(bootloader) partition-size:system_a: 0xB2C00000
(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:no
(bootloader) slot-retry-count:a:0
(bootloader) slot-unbootable:a:yes
(bootloader) slot-successful:a:no
(bootloader) slot-count:2
(bootloader) secure:yes
(bootloader) serialno: omitted
(bootloader) product:sdm845
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi
all:
finished. total time: 0.047s
Is there anyone that has had this set of circumstances and got out of it? Any help is appreciated. There are some things i've seen that i can do but don't want to do further damage. Thanks to all for any and all help.

thejase said:
i tried to install the newest 5.1.11 in full ( as i am magisk rooted, twrp installed, and bootloader unlocked). i kept getting system ui crashes over and over and eventually, after so many, the phone just powers down by itself. I had tried clearing cache after going back into twrp. Rebooted. Same ui issue. Then i decided to restore a backup in twrp i had made a few weeks ago stored on internal memory. This was a bad idea. It said it restored successfully but upon reboot, i only get fastboot now. i think it is communicating with fastboot but when i try to fastboot boot twrp-3.2.1-0 (or 3.2.2-0) i get, "remote: Failed to load/authenticate boot image: Load Error". I do not know what to do and am hoping you guys can figure out how to fix this. Any attempt to enter recovery via buttons results in fastboot booting. restart is also fastboot.
This is what my phone says:
FastBoot mode
Product_name- sdm845
variant- sdm ufs
basband version-
serial- it's there
secure boot- yes
device state- unlocked
Don't know if this helps fastboot getvar all reports this:
C:\Adb\OnePlus 6 Files>fastboot getvar all
(bootloader) unlocked:yes
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3837
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) variant:SDM UFS
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x1B800B7000
(bootloader) partition-type:system_a:ext4
(bootloader) partition-size:system_a: 0xB2C00000
(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:no
(bootloader) slot-retry-count:a:0
(bootloader) slot-unbootable:a:yes
(bootloader) slot-successful:a:no
(bootloader) slot-count:2
(bootloader) secure:yes
(bootloader) serialno: omitted
(bootloader) product:sdm845
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi
all:
finished. total time: 0.047s
Is there anyone that has had this set of circumstances and got out of it? Any help is appreciated. There are some things i've seen that i can do but don't want to do further damage. Thanks to all for any and all help.
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 your solution lies here

tabletalker7 said:
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 your solution lies here
Click to expand...
Click to collapse
I saw this. Will i keep my data with this method?

thejase said:
I saw this. Will i keep my data with this method?
Click to expand...
Click to collapse
no, but if you can't even boot to TWRP then you have nothing left to save at this point.

Try booting the latest twrp (3.2.3.0) before giving up and wiping. If you can get to fastboot, you're not bricked.

iElvis said:
Try booting the latest twrp (3.2.3.0) before giving up and wiping. If you can get to fastboot, you're not bricked.
Click to expand...
Click to collapse
thanks for the suggestions but no dice.

According to your first posting, the phone knows that the boot partition on both your slots are a mess and can't load - you need the fastboot rom to make the phone start over and try again. Sorry buddy - I would like to save your data but it doesn't seem feasible at this point.

tabletalker7 said:
According to your first posting, the phone knows that the boot partition on both your slots are a mess and can't load - you need the fastboot rom to make the phone start over and try again. Sorry buddy - I would like to save your data but it doesn't seem feasible at this point.
Click to expand...
Click to collapse
That's alright. I appreciate the point in the right direction. Doing that fastboot method bat file that you suggested now... Thanks for the help.

thejase said:
That's alright. I appreciate the point in the right direction. Doing that fastboot method bat file that you suggested now... Thanks for the help.
Click to expand...
Click to collapse
tabletalker7 said:
According to your first posting, the phone knows that the boot partition on both your slots are a mess and can't load - you need the fastboot ROM to make the phone start over and try again. Sorry buddy - I would like to save your data but it doesn't seem feasible at this point.
Click to expand...
Click to collapse
So as it turns out that method worked using the bat file flash all fastboot. Though, not at first. When it first rebooted after the bat file finished flashing. system UI was still crashing. When you initially run the bat file at the beginning, it asks if you want to delete your data. First time around i said no, just to see what it would do. Well it booted, but kept getting that system ui crash that I had in the beginning of all this mess. I rebooted and this time chose to erase data and then it re-flashed all again (same bat file). Turns out, when it booted, same deal, system UI crash. So this time i was looking things up while the crashes where happening and then it just rebooted on its own (as it does with a number of system UI crashes in succession). When it came up it was that Chinese menu (which i assume to be download mode or something). Anyway, i chose English and it's a menu to clear dalvik and cache, system settings reset, and one other i can't remember. i did system settings then dalvik and finally, when i rebooted, it was like it was booting for the first time with no crashes. Only thing i can figure is that setting in the bat file at first launch actually didn't erase user data since when it booted, all my icons where there in the background. doing it "on device" in download mode seems to have worked. I am only adding this information as an f.y.i.. Thanks again for all your help, guys.

thejase said:
When it came up it was that Chinese menu (which i assume to be download mode or something).
Click to expand...
Click to collapse
That's stock recovery.

maigre said:
That's stock recovery.
Click to expand...
Click to collapse
Oh, ok. Funny thing is, I had never seen what that looked like as I immediately installed twrp from the time I bought it. Makes sense, though I still wonder why it booted to stock recovery after systemui crashing. Unless it senses the crashes and does that by default to clear system settings and data for a successful boot?