Database Info

Possible to change the Nexus Splash Screen?

Ok, so I am bored with the plain colored X that we get when we turn on the phone. So I am wondering if we can change this image to anything? And if we can do this, how do I go about it.

McFroger3 said:
Ok, so I am bored with the plain colored X that we get when we turn on the phone. So I am wondering if we can change this image to anything? And if we can do this, how do I go about it.
Click to expand...
Click to collapse
I have already tried converting an image to .rgb565 format (which was needed on the G1) and it didn't work, and there was another thread a while back about trying to unyaffs the splash.img or whatever from a dump and it wouldn't work, so for now, I don't think there is a way to do it.

david1171 said:
I have already tried converting an image to .rgb565 format (which was needed on the G1) and it didn't work, and there was another thread a while back about trying to unyaffs the splash.img or whatever from a dump and it wouldn't work, so for now, I don't think there is a way to do it.
Click to expand...
Click to collapse
Damn! I wanted to put up a pic of a hot babe or something haha.

I believe they made this one non changable so people couldn't unlock their bootloader and then flash the original image back on showing it was still locked.
That's a guess though.

Know-Fear said:
I believe they made this one non changable so people couldn't unlock their bootloader and then flash the original image back on showing it was still locked.
That's a guess though.
Click to expand...
Click to collapse
I was thinking it may have been something like that. Don't want anyone making their phone unable to reach the bootloader screen and only show a locked splash image lol.

I think since the bootloader is S-ON, we cant use as many fastboot commands as S-OFF. I forgot how to check what partitions are available within a particular bootloader, but for sure splash1 and splash2 aren't present.

McFroger3 said:
Damn! I wanted to put up a pic of a hot babe or something haha.
Click to expand...
Click to collapse
Is this what you are after?
http://forum.xda-developers.com/showthread.php?t=634915

sd00 said:
Is this what you are after?
http://forum.xda-developers.com/showthread.php?t=634915
Click to expand...
Click to collapse
No i already made a cool boot animation, im talking about the static X you see before the boot animation.

possible yet?
is this still impossible or has someone figured out a way to do this yet?

Still impossible.

Bootloader splash screen not appearing

I'm having a strange issue with the T-Mobile/myTouch 4G slash screen not always appearing when the phone is booting. It's not ROM-related since it's happened with several different ROMs installed. What happens is I'll press the power button, the phone will vibrate, but rather than the white MT4G screen appearing, a completely black screen will. After that, the ROM's splash screen pops up and the boot continues normally. This happens during roughly 1 out of 10 boots, otherwise the MT4G screen appears normally. My concern is that something is corrupt with my bootloader. Does anyone have any idea what's going on here?

More probably something is corrupt with splash1 partition. But yes, something isn't well.
You could try reflashing the splash1, given that you have engineering bootloader, and see if it helps any.

What do you mean when you say "isn't well"? Do I have a potential brick on my hands?
I'm not sure how something could have become corrupted as I haven't messed with the bootloader at all. About a year ago, I rooted via the Visionary/root.sh method and have not flashed many different ROMs.
What exactly is "splash1" and how would I flash it?

That's just weird but I would have to agree with the splash partition thing. One thing you could try is drew blues splash screen editor and relash the stock img. That might fix the issue. Its some where in the apps section.

mark manning said:
That's just weird but I would have to agree with the splash partition thing. One thing you could try is drew blues splash screen editor and relash the stock img. That might fix the issue. Its some where in the apps section.
Click to expand...
Click to collapse
Thanks for the tip. I'll look into it. Do you have any idea what the consequence of a problem with the splash partition is? It still appears normally in 9 out of 10 boots.

Or also open up the pd15img and delete everything except the splash Img. (May not be called splash but you should be able to figure out which of the files it is) Then flash the pd15img accordingly
Edit: splash file and the updater script!!!!!

TeeJay3800 said:
Thanks for the tip. I'll look into it. Do you have any idea what the consequence of a problem with the splash partition is? It still appears normally in 9 out of 10 boots.
Click to expand...
Click to collapse
No I don't but I wouldn't think it could or would completely fail without loosing the entire eMMc chip.
Sent from my Google Nexus 12... yep I'm from the future where Apple is no more!

Btw tj I have to say this. Wrong section buddy lol. ;-)
Jk jk

mark manning said:
Btw tj I have to say this. Wrong section buddy lol. ;-)
Jk jk
Click to expand...
Click to collapse
Haha, I knew someone would give me s**t. I debated if it really belonged in Q&A. Still not sure. Maybe you're right.

I am thinking about flashing a new bootloader flash screen via fastboot by following the instructions in this thread: http://forum.xda-developers.com/showthread.php?t=866474. If anyone has any input I'm all ears.

mark manning said:
That's just weird but I would have to agree with the splash partition thing. One thing you could try is drew blues splash screen editor and relash the stock img. That might fix the issue. Its some where in the apps section.
Click to expand...
Click to collapse
you mean this one?
http://forum.xda-developers.com/showthread.php?t=956434
if not, this one works very well, just used it yesterday, worked amazingly.

TeeJay3800 said:
I am thinking about flashing a new bootloader flash screen via fastboot by following the instructions in this thread: http://forum.xda-developers.com/showthread.php?t=866474. If anyone has any input I'm all ears.
Click to expand...
Click to collapse
I'd say - go for it. In the worst case, you'll get a customized splash screen, in the best case - your problem will disappear.
If it doesn't help - you could try (re)flashing Engineering HBOOT.
And if both didn't help - then you should hope that this would be the only semi-bad sector your eMMC has (most probably the problem appears because eMMC isn't read correctly, but since it's on splash1 partition - the only harm is not seeing the image).

Jack_R1 said:
I'd say - go for it. In the worst case, you'll get a customized splash screen, in the best case - your problem will disappear.
If it doesn't help - you could try (re)flashing Engineering HBOOT.
And if both didn't help - then you should hope that this would be the only semi-bad sector your eMMC has (most probably the problem appears because eMMC isn't read correctly, but since it's on splash1 partition - the only harm is not seeing the image).
Click to expand...
Click to collapse
Thanks for the info. I do have the "good" eMMC, so hopefully this fixes the issue and I have no further problems.

[FIX] Flashed Wrong Recovery image

Alright, so we all know it's confusing to differentiate the One XL from the One X, especially since Rogers and AT&T insist on calling it the One X.
IF YOU HAVE A "ONE X" FROM ROGERS/AT&T, YOU HAVE THE ONE XL. DON'T EVEN BOTHER VISITING THE ONE X FORUMS.
Now, you've gone and downloaded CWM from the One X forums and flashed it to your One XL, and you're semi-bricked. Let's get you out of that pickle. Please note that I have not done any of this to my own One XL, as there's no ROMs or custom recovery images or kernels for our phone yet. However, just this morning I performed a similar operation on my Jetstream, and the steps will be identical. I take no responsibility for any problems you experience.
First, you'll need to download the leaked RUU that can be found here: http://forum.xda-developers.com/showthread.php?t=1550930
EDIT: designgears has offered a newer recovery image. I'm not sure what advantages it would bring, but at least there's a second option: http://www.gigashare.in/53885
Please note that this is marked as the AT&T RUU, so there's no guarantee this will work for Rogers. However, your recovery mode is screwed anyway, so in my opinion, it couldn't hurt to try.
Once you've downloaded the RUU, run it. You don't need to install the RUU itself, we just have to have the application running. Once running, it'll create a "rom.zip" file in a temp folder somewhere in your user profile. While the RUU is open, just search for "rom.zip" and you should find it. Open this file and extract "recovery_signed.img" to your computer, into the same folder as your "fastboot" application. Once you've done this, close the zip file and exit the RUU.
Now, boot your device into fastboot mode
Code:
adb reboot bootloader
Once in bootloader mode, you may need to select "fastboot" from the menu.
Now that you're in fastboot mode, you can flash the recovery we extracted from the RUU:
Code:
fastboot flash recovery recovery_signed.img
Your screen will go through a couple brief steps, something like "sending recovery_signed.img" then "writing recovery_signed.img" and then "OK."
Try to boot into recovery now, and you should see the standard HTC recovery mode!
I really hope this helps everyone out. I'll iterate again that I have no tried this with my One XL, so I have no actual proof that this will work. But, if you've already flashed the wrong recovery image, you should be somewhat familiar with these steps already.
EDIT: Please post your success with this method. As I haven't tested, I'd like to know if everything's kosher, and I can change the instructions accordingly if something's wrong.

Hey, sorry I didn't get back to you sooner, went to bed.
Here is just the recovery image for a newer, unreleased leak.
http://www.gigashare.in/53885
1.61.502.1 CL49502

designgears said:
Hey, sorry I didn't get back to you sooner, went to bed.
Here is just the recovery image for a newer, unreleased leak.
http://www.gigashare.in/53885
Click to expand...
Click to collapse
Heh, don't apologize to me, my phone's locked and running fine. (I've had the phone since Friday... I think this is the longest I've ever gone without rooting an Android phone.)
I'll put that link up in the first post, thanks!
EDIT: Oh! And is that AT&T or Rogers?

craig0r said:
Heh, don't apologize to me, my phone's locked and running fine. (I've had the phone since Friday... I think this is the longest I've ever gone without rooting an Android phone.)
I'll put that link up in the first post, thanks!
EDIT: Oh! And is that AT&T or Rogers?
Click to expand...
Click to collapse
It's AT&T recovery.

Flashed but still having trouble. Got into recovery but can't boot.
Going to see if re-locking the bootloader may help. Only thing different I've done is that I ran that flash_boot.zip thing that Leedroid had on his page. It just seems to push a boot.img file and clear the fastboot cache.
Does anyone have that particular boot.img file? Pretty please?

For myself I will leave it for now and wait until an official rogers RUU or custom recovery to make sure I don't break it again
Sent from my HTC One X

bongd said:
Flashed but still having trouble. Got into recovery but can't boot.
Going to see if re-locking the bootloader may help. Only thing different I've done is that I ran that flash_boot.zip thing that Leedroid had on his page. It just seems to push a boot.img file and clear the fastboot cache.
Does anyone have that particular boot.img file? Pretty please?
Click to expand...
Click to collapse
The rom.zip file from the AT&T ruu should have the boot.img file in it. you can flash it with
Code:
fastboot flash boot boot.img
However, the boot partition is a WEE bit more critical to the phone's function than the recovery partition. Dunno if I'd be flashing it myself, at least not to a Rogers phone.
Sent from my HTC One X using xda premium

craig0r said:
The rom.zip file from the AT&T ruu should have the boot.img file in it. you can flash it with
Code:
fastboot flash boot boot.img
However, the boot partition is a WEE bit more critical to the phone's function than the recovery partition. Dunno if I'd be flashing it myself, at least not to a Rogers phone.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Thanks, man. Someone said they flashed the entire RUU to their Rogers phone so I don't think it could be too harmful.
I only have my Ubuntu machine and Wine is being fussy and not extracting the rom.zip archive properly. I'll see if something gets released soon. I rarely see Rogers RUU so hopefully I'm not waiting too long. Reactivated my SIM for my Galaxy Nexus but still sad lol

I feel your pain!
bongd said:
Thanks, man. Someone said they flashed the entire RUU to their Rogers phone so I don't think it could be too harmful.
I only have my Ubuntu machine and Wine is being fussy and not extracting the rom.zip archive properly. I'll see if something gets released soon. I rarely see Rogers RUU so hopefully I'm not waiting too long. Reactivated my SIM for my Galaxy Nexus but still sad lol
Click to expand...
Click to collapse
I've been in the same boat brother, minus flashing the boot.img file. Did you end up resolving/unbricking your XL? If not, I can extract the boot.img from my Rogers phone if that would help.
Btw, I haven't been on the forums in a couple of days, but I caught wind of your predicament and I'm surprised at the trouble you've had recently asking for help in this matter. Some people are ridiculous!
Truth is, we have this pretty new device that we want to take advantage of! We got excited, and f'd up. Anyhow, let me know if I can help.

krepler said:
I've been in the same boat brother, minus flashing the boot.img file. Did you end up resolving/unbricking your XL? If not, I can extract the boot.img from my Rogers phone if that would help.
Btw, I haven't been on the forums in a couple of days, but I caught wind of your predicament and I'm surprised at the trouble you've had recently asking for help in this matter. Some people are ridiculous!
Truth is, we have this pretty new device that we want to take advantage of! We got excited, and f'd up. Anyhow, let me know if I can help.
Click to expand...
Click to collapse
That would be freakin' wicked, man. Recovery works but that darn boot.img probably needs replacing. If you could pull stock recovery too that might help as well.
Been a bad day lol... broke my hand on cement earlier too so this is appreciated. Ouch, knuckle is all over the place. Hopefully I get this phone workjing soon to take my mind off things LOL

bongd said:
That would be freakin' wicked, man. Recovery works but that darn boot.img probably needs replacing. If you could pull stock recovery too that might help as well.
Been a bad day lol... broke my hand on cement earlier too so this is appreciated. Ouch, knuckle is all over the place. Hopefully I get this phone workjing soon to take my mind off things LOL
Click to expand...
Click to collapse
Ok, I'm in the middle of downloading the evita leaked files. I can't extract it from my phone since I need root... unless you know a way other than adb shell? Either way, I don't think you can access it without root. I've tried a few ways with no luck.
I see you can't access the evita files so the best I can do for you is extract it from there for you. Download is slow as hell, so bear with me!

krepler said:
Ok, I'm in the middle of downloading the evita leaked files. I can't extract it from my phone since I need root... unless you know a way other than adb shell? Either way, I don't think you can access it without root. I've tried a few ways with no luck.
I see you can't access the evita files so the best I can do for you is extract it from there for you. Download is slow as hell, so bear with me!
Click to expand...
Click to collapse
No need to ask for my patience, bro. It's hugely appreciated! Thanks a ton!

bongd said:
No need to ask for my patience, bro. It's hugely appreciated! Thanks a ton!
Click to expand...
Click to collapse
My new issue is I'll have to make a couple more posts before I can add urls to them, since I never post on the forums. Gotta start somewhere...
Scratch that, you the good 'ol copy and paste.
http://www.gigashare.in/d4129 = HTC One XL AT&T 1.44.502.1 Radio 0.15.3201.09 recovery_signed.img
http://www.gigashare.in/8adee = HTC One XL AT&T 1.44.502.1 Radio 0.15.3201.09 boot_signed.img

krepler said:
My new issue is I'll have to make a couple more posts before I can add urls to them, since I never post on the forums. Gotta start somewhere...
Scratch that, you the good 'ol copy and paste.
http://www.gigashare.in/d4129 = HTC One XL AT&T 1.44.502.1 Radio 0.15.3201.09 recovery_signed.img
http://www.gigashare.in/8adee = HTC One XL AT&T 1.44.502.1 Radio 0.15.3201.09 boot_signed.img
Click to expand...
Click to collapse
and the latest:
http://www.gigashare.in/0029e = Cingular 1.68.502.1 Radio 0.16.32.09.01 boot_signed.img
http://www.gigashare.in/03695 = Cingular 1.68.502.1 Radio 0.16.32.09.01 recovery_signed.img
Should've just waited and posted these ones... buuuuuuut, I have no patience.
Hopefully the boot.img works for you! Let me know how she goes.

bongd said:
That would be freakin' wicked, man. Recovery works but that darn boot.img probably needs replacing. If you could pull stock recovery too that might help as well.
Been a bad day lol... broke my hand on cement earlier too so this is appreciated. Ouch, knuckle is all over the place. Hopefully I get this phone workjing soon to take my mind off things LOL
Click to expand...
Click to collapse
Bongd, The recovery works for you? My situtation is in the same boat with Krepler minus the boot.img. I am little bit worry if I load the AT&T recovery and that will conflict the boot.img in Rogers phone.
---------- Post added at 07:25 AM ---------- Previous post was at 07:22 AM ----------
krepler said:
I've been in the same boat brother, minus flashing the boot.img file. Did you end up resolving/unbricking your XL? If not, I can extract the boot.img from my Rogers phone if that would help.
Btw, I haven't been on the forums in a couple of days, but I caught wind of your predicament and I'm surprised at the trouble you've had recently asking for help in this matter. Some people are ridiculous!
Truth is, we have this pretty new device that we want to take advantage of! We got excited, and f'd up. Anyhow, let me know if I can help.
Click to expand...
Click to collapse
Krepler, Can you tell me how did you solve your recovery? I am in your sisutation as well, flash the wrong recovery and once I boot to recovery and it will occur the boot loop, however I am still able to use the One X (Semi-bricked). Did you flash the stock recovery from Rogers or the one that you just posted from AT&T?

Elin28 said:
Bongd, The recovery works for you? My situtation is in the same boat with Krepler minus the boot.img. I am little bit worry if I load the AT&T recovery and that will conflict the boot.img in Rogers phone.
Click to expand...
Click to collapse
One does not interfere with the other. Recovery is pretty much its own operating system, completely segregated from the rest of the phone. It can neither hinder nor enhance the booting of your phone in normal mode. You could theoretically flash a random sequence of ones and zeros to the recovery partition, and the phone would continue to boot just fine. Until you try and go into recovery mode that is. Flashing the recovery_signed.img as per my instructions is safe in regards to the phone's normal operation. I can't promise that it's a working recovery, however, as I've not tried it myself.

Awesome! Just booted up, my man. A thousand fellatios to you!! Please message me your Paypal address so I can buy you a beer or two.
Haven't tried the Cingular ones but the AT&T ones worked just fine. I'm betting it'll be damn near identical, save probably a few radio adjustments or very minor adjustments.
Booted to the main screen so I should be able to set things up. But I'll chime in and report if there are any major issues. Thanks again!!

Hey I am happy your phone boot up man!!
I am still having trouble with the recovery. I try flash the att& the cingular recovery. good thing is no bootloop I see an image showing black phone and a green circle. then I end up with image of a phone with red triangle with a "!" inside. and then the phone reboots.
am I doing something wrong?
Thanks
bongd said:
Awesome! Just booted up, my man. A thousand fellatios to you!! Please message me your Paypal address so I can buy you a beer or two.
Haven't tried the Cingular ones but the AT&T ones worked just fine. I'm betting it'll be damn near identical, save probably a few radio adjustments or very minor adjustments.
Booted to the main screen so I should be able to set things up. But I'll chime in and report if there are any major issues. Thanks again!!
Click to expand...
Click to collapse

@bongd
Awesome bro!!!! Glad you got your hox up and running.
Sent from wherever I am!

yoohoohoo said:
Hey I am happy your phone boot up man!!
I am still having trouble with the recovery. I try flash the att& the cingular recovery. good thing is no bootloop I see an image showing black phone and a green circle. then I end up with image of a phone with red triangle with a "!" inside. and then the phone reboots.
am I doing something wrong?
Thanks
Click to expand...
Click to collapse
Have you tried running "fastboot erase cache"?
What other steps have you done as well? The killer for me was the boot.img file that Leedroid created as part of his ROM installation. The AT&T recovery is what I had used. For a moment I thought I might need to try flashing the system.img file like redwreck had to, but I didn't need to.
Perhaps someone could upload that as well, please? If you need to flash that, it's "fastboot flash system system.img" and it'll flash that too. I always do "fastboot reboot" after as well.
I trust that these should work. Hopefully there'll be a full Rogers RUU so we can flash that just to be on the safe side. Best of luck! I'll keep an eye on this thread as well.
Since I posted earlier I've been setting things up and it's working like a damn charm. Tried exhausting every weird and quirky feature I thought might screw up, but I can't find anything that's not working.

[Q] Stock Sensation stuck on white HTC screen and bootloop

Thanks

spturner said:
I have also tried the HTC bootloader unlock on the HTC website, but after following the instructions exactly, it failed. I tried twice.
Click to expand...
Click to collapse
when you are saying it failed what do you mean exactly?
i would suggest you to use ganeshp's guide from general section to S-OFF your device but unfortunately your device is not in working condition

I would say its time to retire your sensation... If you cannot unlock the bootloader and a factory reset does not help then I dont think there is much more that can be done.

I would say... Find the cid then based on it... Find the proper ruu and run it...
Sent from my HTC Sensation using xda premium

The failure I get when trying the HTC unlocking tool is the same as a lot of people have reported

spturner said:
The failure I get when trying the HTC unlocking tool is the same as a lot of people have reported -
c:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.160s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.170s
I've triple checked the process and am sure I'm doing it right.
I bought the phone on ebay a few months ago and it's been working fine up until now.
A few things about the phone however -
1. It was sent to me with a box, but the IMEI number on the phone didn't match the number on the box. I've since found that maybe this could be due to an HTC motherboard repair when it was under warranty (I understand there was a high dust under the screen failure rate on these models ?) This could also explain why the HTC unlock doesn't work ?
2. When I got the phone, I did a factory reset and the only language packs available as part of the factory reset were Asian ones, (Thai etc), but after a full reset, it operated fine in English.
3. The phone is sim-free
Unless anyone can come up with any solutions it sounds like it's time to take a sledgehammer to the thing, and also a mental note to NEVER buy HTC again. Time for the Nexus 4 I think.
Thanks
Click to expand...
Click to collapse
i think that causes the failure because of different imei after motherboard's replacement
if i remember well there is somewhere a thread of what to do when htcdev fails after motherboard is being replacing
and it comes with different imei
but i don't remember where
give it a try and search it

I have none of these, as the phone is completely stock and of course I can't get into the phone to install things or change settings.

spturner said:
Thanks, yes I had already searched and found various ways to do this, but it seems most do not work, or you at least need to have other things installed and working, or USB debugging enabled.
I have none of these, as the phone is completely stock and of course I can't get into the phone to install things or change settings.
Here comes that sledgehammer ! Actually, maybe I'll just fry it in a microwave and post the video on youtube.
Goodbye HTC...you pile of junk phone manufacturer.
Click to expand...
Click to collapse
Nooooooooooo... :silly:
as i said find the proper RUU ...from here and flash it
TIP: RUU can be flashed from bootloader and no adb is required ..thus usb debugging enabling is not required

For the moment, the sledgehammer is put away as it seems you guys might just get me sorted...maybe ?
Thanks

Any further assistance will be much appreciated
Thanks

ask FootBall for the non xe RUU ...

Help needed desperately!

Okay so I haven't rooted or rommed for quite some time and i decided to finally come back to it after stopping over a year ago. I just recently got this m8 for verizon and i wanted to turn it into a developer edition. Well I used sunshine to s-off my device, and i changed my mid and cid to the developer ones. (yes i know they're the right ones. I've triple checked them. All was going well. I then used the jrummy rom installer to install my twrp. When I did that, it rebooted and then all of my stuff was gone except for my hboot, recovery, and fastboot. the recovery said it couldn't mount anything. not even the system! so i couldn't flash anything. i tried sideloading liquid smooth through adb in twrp and all it does is boot loop. so i thought that I should probably run the appropriate RUU. I tried. I keep getting error 155. even after i relocked the bootloader. But before i locked the bootloader i flashed a stock recovery img. i tried manually installing a RUU zip. wrong mid (tried using verizon one when i had already changed the mid to developer one. I can't find the right zip for the developer edition and none of the .exe ones work. i keep getting error 155. So now the only thing i can access is a bootlooping liquid smooth rom and hboot/fastboot/ruu mode. no recovery. and as far as i still know, a recovery cannot recognize the system partition and any .exe ruu gives me the 155 error. I am in desperaste need of help. at this point i don't even care about lollipop and anything. just help get me back to stock please!! :crying: :crying: :crying: :crying:
Edit: I was on Stock Verizon 4.4.4 when I started all of this, and I was following this thread http://forum.xda-developers.com/htc-one-m8/general/guide-update-to-official-developer-t3002003

Ryuk666 said:
Okay so I haven't rooted or rommed for quite some time and i decided to finally come back to it after stopping over a year ago. I just recently got this m8 for verizon and i wanted to turn it into a developer edition. Well I used sunshine to s-off my device, and i changed my mid and cid to the developer ones. (yes i know they're the right ones. I've triple checked them. All was going well. I then used the jrummy rom installer to install my twrp. When I did that, it rebooted and then all of my stuff was gone except for my hboot, recovery, and fastboot. the recovery said it couldn't mount anything. not even the system! so i couldn't flash anything. i tried sideloading liquid smooth through adb in twrp and all it does is boot loop. so i thought that I should probably run the appropriate RUU. I tried. I keep getting error 155. even after i relocked the bootloader. But before i locked the bootloader i flashed a stock recovery img. i tried manually installing a RUU zip. wrong mid (tried using verizon one when i had already changed the mid to developer one. I can't find the right zip for the developer edition and none of the .exe ones work. i keep getting error 155. So now the only thing i can access is a bootlooping liquid smooth rom and hboot/fastboot/ruu mode. no recovery. and as far as i still know, a recovery cannot recognize the system partition and any .exe ruu gives me the 155 error. I am in desperaste need of help. at this point i don't even care about lollipop and anything. just help get me back to stock please!! :crying: :crying: :crying: :crying:
Edit: I was on Stock Verizon 4.4.4 when I started all of this, and I was following this thread http://forum.xda-developers.com/htc-one-m8/general/guide-update-to-official-developer-t3002003
Click to expand...
Click to collapse
Can you go into bootloader an try to flash twrp via fast boot? Then if you can try going into recovery by picking recovery in boot loader..

Tigerstown said:
Can you go into bootloader an try to flash twrp via fast boot? Then if you can try going into recovery by picking recovery in boot loader..
Click to expand...
Click to collapse
I tried already. it gives me this error in my command prompt:
target reported max download size of 1826414592 bytes
sending 'recovery' (14814 KB)...
OKAY [ 1.373s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.388s
And then that's all I get. twrp was not flashed.

Ryuk666 said:
I tried already. it gives me this error in my command prompt:
target reported max download size of 1826414592 bytes
sending 'recovery' (14814 KB)...
OKAY [ 1.373s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.388s
And then that's all I get. twrp was not flashed.
Click to expand...
Click to collapse
So have you tried to change your Cid back to vzw an run the ruu?

I had the dev cid, but then i changed it to super cid. i'll try the vzw one right now and get back to you in a moment

Ryuk666 said:
I had the dev cid, but then i changed it to super cid. i'll try the vzw one right now and get back to you in a moment
Click to expand...
Click to collapse
An use the VZW ruu too

Tigerstown said:
An use the VZW ruu too
Click to expand...
Click to collapse
I'm using the VZW RUU zip through the external sd card and i changed the cid to the verizon one. It was loading the RUU zip and it gave me this:
Model ID incorrect!
Update Fail!
Press <POWER> to reboot.
When i press power it just throws me back into the bootlooping liquid smooth rom to i have to put it back into fastboot so I'm still at a standstill.

Ryuk666 said:
I'm using the VZW RUU zip through the external sd card and i changed the cid to the verizon one. It was loading the RUU zip and it gave me this:
Model ID incorrect!
Update Fail!
Press <POWER> to reboot.
When i press power it just throws me back into the bootlooping liquid smooth rom to i have to put it back into fastboot so I'm still at a standstill.
Click to expand...
Click to collapse
You change your mid as well? If so can you change it back to VZW one.

How do i go about doing that through fastboot? I did it through adb last time.

Ryuk666 said:
How do i go about doing that through fastboot? I did it through adb last time.
Click to expand...
Click to collapse
Hold tight for a few mins. Don't do anything else. I'm talking to someone now. He is going to join in an finish getting you booted...

Ryuk666 said:
How do i go about doing that through fastboot? I did it through adb last time.
Click to expand...
Click to collapse
any chance you can install teamviewer so i can get you fixed up and booted?

Okay thank you so much. I will sit here and leave it alone and wait patiently lol.

dottat said:
any chance you can install teamviewer so i can get you fixed up and booted?
Click to expand...
Click to collapse
One moment and i'll go do that now.

Ryuk666 said:
One moment and i'll go do that now.
Click to expand...
Click to collapse
PM me the login info...

Dottat you are seriously the man! You are so awesome! I would have never gotten that done myself. You are seriously amazing!

Glad your all set. That's why I hit him up

I am having the exact same issue except i found a couple problems in my recovery log that stumped me some how in the mix my serial number became =£Ðcçy™yüRv–²‹ and my mid shows
ro.boot.mid=
in my boot log what can i do to solve these problems????
---------- Post added at 07:02 AM ---------- Previous post was at 06:45 AM ----------
I am having the exact same issue except i found a couple problems in my recovery log that stumped me some how in the mix my serial number became =£Ðcçy™yüRv–²‹ and my mid shows
ro.boot.mid=smiley and an arrow (woulent paste)
in my boot log what can i do to solve these problems????

People I think it would be best to give up the dev conversion idea on a verizon m8. A bunch of us tried and tried and take this from experience you will be opening up a can of worms. Wouldnt it be nice to be able to oh heck yeah I would like to also but unless your really really really experienced with this stuff your going to be regretting trying it.
It would be nice but I think it wont work because of the cdma side of the verizon m8. It works great on at&t & tmobile verizons which are all gsm. Our verizon phones are world phones and both cdma and gsm so somewhere lies the incompatibility.
Believe me I tried and tried and tried and I spent a lot of time getting my phone back working right again. My recommendation is if your thinking about trying to convert your verizon m8 to a dev edition save yourself a big headache and dont waste your time. Either that or get an at&t or tmobile m8 and convert it, but then use it on either at&t or tmobile where it will work right and the LTE will work.
It was really nice of these guys to help get his phone fixed so anyone else thinking about it learn from his mistake and forget about it lol.

Ryuk666 said:
Dottat you are seriously the man! You are so awesome! I would have never gotten that done myself. You are seriously amazing!
Click to expand...
Click to collapse
Did you get your fixed? because i have similar problem. i got my verizon m8 messed up MiD To 0P6B10000 instead of 0P6B20000. And now i cant flash any official firmware. can you help me out?

Mine did indeed get fixed. But I'm not exactly sure how. Dottat was a huge help. He definitely knows what he's doing lol. He was going through command prompt fastboot commands so fast I couldn't follow him haha.