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.
Related
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.
A lot of people like to have flashy, colorful, crazy boot animations. I like to keep it simple, very simple.
Overwrite the bootanimation.zip or VZW_bootanimation.zip wherever it's located on your ROM (usually /data/local or /system/customize/resource). I prefer to do this with Root Explorer.
I don't know if small-sized boot animations have any impact on start-up speed, but this one's pretty lightweight.
(Update: matching splash screen added in post below)
This looks really good and I have installed it.
Can you make a splash screen that appears just prior to this animation?
luvit said:
This looks really good and I have installed it.
Can you make a splash screen that appears just prior to this animation?
Click to expand...
Click to collapse
Here you go!
Place PB31IMG.zip on the root of your SD card. Reboot to Hboot.
You should be prompted to install your custom splash1.
(I actually made this splash screen a couple months ago, but I since removed the 'TM' from the logo --- original thread: http://forum.xda-developers.com/showthread.php?t=753938)
I got em both working!
Thanks, again!
theotherrogue said:
A lot of people like to have flashy, colorful, crazy boot animations. I like to keep it simple, very simple.
Overwrite the bootanimation.zip or VZW_bootanimation.zip wherever it's located on your ROM (usually /data/local or /system/customize/resource). I prefer to do this with Root Explorer.
I don't know if small-sized boot animations have any impact on start-up speed, but this one's pretty lightweight.
(Update: matching splash screen added in post below)
Click to expand...
Click to collapse
I love the simplicity of this. I took a similar approach in uncommon sense. well done.
Before I try this, I just want to make sure that my phone can take it. Im running CMod and I just want to replace the splash screen that first pops up when it turns on, not the boot animation. If I install the Pbimg.zip file will that just replace my splash screen? also before I do this, can a nandroid backup restore my splash screen If I want to revert back to the origional? Thanks. I really like this splash screen and it looks totally awesome. Please PM me for your Answers!
mikeacela said:
Before I try this, I just want to make sure that my phone can take it. Im running CMod and I just want to replace the splash screen that first pops up when it turns on, not the boot animation. If I install the Pbimg.zip file will that just replace my splash screen? also before I do this, can a nandroid backup restore my splash screen If I want to revert back to the origional? Thanks. I really like this splash screen and it looks totally awesome. Please PM me for your Answers!
Click to expand...
Click to collapse
The splash screen wont replace your boot animation. And nandroid doesnt save splash screens.
Sent from my ADR6300 using XDA App
For some reason every time I try to install the PB31Img.zip it doesent install in HBoot. I have no idea what could be the problem. i also tried to install it from CWmod and that didnt work Either? Any ideas as to what might be the cause? I really like this splash screen but for some reason it just wont flash in hboot. I have S-Off but for some reason it still doesent work.
mikeacela said:
For some reason every time I try to install the PB31Img.zip it doesent install in HBoot. I have no idea what could be the problem. i also tried to install it from CWmod and that didnt work Either? Any ideas as to what might be the cause? I really like this splash screen but for some reason it just wont flash in hboot. I have S-Off but for some reason it still doesent work.
Click to expand...
Click to collapse
I'm not sure what the issue might be. Make sure you are in the Bootloader screen that says "HBOOT", not "FASTBOOT". When you load HBOOT, it should prompt you after a few seconds to install the update. (ClockworkMod/Recovery shouldn't be used at all for updating splash screens)
I just double checked the attachment posted here. Works fine. Make sure you place it on the root of your SD card.
Thanks for the boot animation. It's lightweight and speedy, just what I needed.
Sent from my Incredible using Tapatalk.
theotherrogue said:
I'm not sure what the issue might be. Make sure you are in the Bootloader screen that says "HBOOT", not "FASTBOOT". When you load HBOOT, it should prompt you after a few seconds to install the update. (ClockworkMod/Recovery shouldn't be used at all for updating splash screens)
I just double checked the attachment posted here. Works fine. Make sure you place it on the root of your SD card.
Click to expand...
Click to collapse
try to format your sdcard to fat32 then try again..
theotherrogue said:
A lot of people like to have flashy, colorful, crazy boot animations. I like to keep it simple, very simple.
Click to expand...
Click to collapse
This splash screen/boot animation set is beautiful.
I owe you a beer.
/me looks at OP's location...
****, you're awfully close to home. Doesn't matter. Should I get a chance to cross paths, I owe you a beer.
mikeacela said:
For some reason every time I try to install the PB31Img.zip it doesent install in HBoot. I have no idea what could be the problem. i also tried to install it from CWmod and that didnt work Either? Any ideas as to what might be the cause? I really like this splash screen but for some reason it just wont flash in hboot. I have S-Off but for some reason it still doesent work.
Click to expand...
Click to collapse
Is your SD Card formatted to FAT32? That's where I slipped up, once I did that I could mod my splash to my heart's content
EDIT: Agh, sorry, didn't see page 2 of this thread and thus remy2501's already suggested this. What else could be wrong.. is it on the root of your SD Card? Is the volume up rocker the first button you press when going in to hboot?
mikeacela said:
For some reason every time I try to install the PB31Img.zip it doesent install in HBoot. I have no idea what could be the problem. i also tried to install it from CWmod and that didnt work Either? Any ideas as to what might be the cause? I really like this splash screen but for some reason it just wont flash in hboot. I have S-Off but for some reason it still doesent work.
Click to expand...
Click to collapse
Remember to be very specific as to the name, the only thing you should be installing in the root must be named: PB31IMG
Not PB31IMG.zip or PB31img and so on.....if that doesn't work there might be a problem with that particular splash screen. Once you get it installed, remember to remove that zip file from the root otherwise next time you go into HBoot it will ask you to reinstall......Good luck !
Oddly enough, I lost 3G after installing this. After rolling back to a previous backup, 3G is back.
I installed it around 3pm yesterday and somehow was oblivious to not having 3G. My phone had even restarted a few times after that, yet no 3G. All day I have been wondering why my 3G hasn't been working, never tied it back to this load screen. I rolled back to a previous backup and 3G came on instantly and a full day's worth of emails and gtalk messages streamed in.
Curious to know if anyone else encountered the same?
I'm running Miui btw.
wow nice combo looks smoothe and simple and just what i was looking for.
Aeckert said:
Oddly enough, I lost 3G after installing this. After rolling back to a previous backup, 3G is back.
I installed it around 3pm yesterday and somehow was oblivious to not having 3G. My phone had even restarted a few times after that, yet no 3G. All day I have been wondering why my 3G hasn't been working, never tied it back to this load screen. I rolled back to a previous backup and 3G came on instantly and a full day's worth of emails and gtalk messages streamed in.
Curious to know if anyone else encountered the same?
I'm running Miui btw.
Click to expand...
Click to collapse
i had this problem too but not with the boot animation. i had to install king kernel to get 3g working on virtuious rom in order to fix it.
any chance of making a shutdown.zip?
causing 3g to not work.
Not sure if it was the splash or boot animation, but 3g would not work after installing these on Virtuous 3.01 with the Adrynalyne Custom Kernel v2.
Flashed this and have no problems with 3g on virtuous. Thanks for it!
Sent from my HTC Incredible
I TRIED THE HBOOT 2.2 ROOT GOT BRICKED AND USED THE FIX FROM "Monarky"
THANKS DUDE AND IT WORKED SO IVE PUT TOGETHER
A SHORTER FIX I ACTUALLY DID THE WORK MYSELF SO ALL YOU HAVE TO DO IS REPLACE THE ATTACHED FILE WITH THE ONE ON YOUR SD CARD
AND RELOAD BOOTLOADER AND IT SHOULD UNBRICK BUT ITS GOING TO SWITCH YOUR "PRI VERSION" BUT IT WORKS
ALL I ASK FOR IS A SIMPLE THANKS
FIX - http://www.megaupload.com/?d=2KA69REH
How are you defining "bricked?" What was your phone doing? What did the screen look like?
Tapa tapa tapa
mlin said:
How are you defining "bricked?" What was your phone doing? What did the screen look like?
Tapa tapa tapa
Click to expand...
Click to collapse
he was probably referring to being stuck at the RUU update screen
mlin said:
How are you defining "bricked?" What was your phone doing? What did the screen look like?
Tapa tapa tapa
Click to expand...
Click to collapse
s0xpan said:
he was probably referring to being stuck at the RUU update screen
Click to expand...
Click to collapse
well yea the red triangle
I haven't downloaded what you cooked up there, but if included radios or the wimax partition, you really need to warn people that they could lose 4G.
If you "brick" your phone, you should only use the RUU from Sprint to fix it. If the phone isn't recognized by the RUU, then extract the PC36IMG.zip from it and use the fastboot command line to flash.
-- Brian
That's not a brick. A brick is when your device will not do anything. Won't power on, won't even light up when you plug it in. There's nothing you can do with a true brick, that's why it's named that way.
If you can get into bootloader, you can recover your device.
clamknuckle said:
That's not a brick. A brick is when your device will not do anything. Won't power on, won't even light up when you plug it in. There's nothing you can do with a true brick, that's why it's named that way.
If you can get into bootloader, you can recover your device.
Click to expand...
Click to collapse
Not true. Here is a scenario for you...actually happened to my evo:
Your entire os gets erased, except bootloader. Your screen won't even come on, but the charge light comes on, and the computer sees the device. Fun part is, it does not even see it as android...it pops up as qualcomm. Ruu doesn't work. Pc36Img doesn't work. Trying to flash through fastboot doesn't work. Why? Because there are so many bad blocks in the memory that nothing will write (htc doesn't allow their handsets to skip bad blocks). So, you were mostly right, but there are exceptions to everything.
tejasrichard said:
Not true. Here is a scenario for you...actually happened to my evo:
Your entire os gets erased, except bootloader. Your screen won't even come on, but the charge light comes on, and the computer sees the device. Fun part is, it does not even see it as android...it pops up as qualcomm. Ruu doesn't work. Pc36Img doesn't work. Trying to flash through fastboot doesn't work. Why? Because there are so many bad blocks in the memory that nothing will write (htc doesn't allow their handsets to skip bad blocks). So, you were mostly right, but there are exceptions to everything.
Click to expand...
Click to collapse
So... as the man said, if you got it working then it wasn't really "bricked."
Tapa tapa tapa
tejasrichard said:
Not true. Here is a scenario for you...actually happened to my evo:
Your entire os gets erased, except bootloader. Your screen won't even come on, but the charge light comes on, and the computer sees the device. Fun part is, it does not even see it as android...it pops up as qualcomm. Ruu doesn't work. Pc36Img doesn't work. Trying to flash through fastboot doesn't work. Why? Because there are so many bad blocks in the memory that nothing will write (htc doesn't allow their handsets to skip bad blocks). So, you were mostly right, but there are exceptions to everything.
Click to expand...
Click to collapse
Nope, your wrong. Back when I used to mod PSPs, if you flashed a firmware incorrectly, you'd either get a semi-brick or a brick. A semi-brick is when you can't get into the OS, but you can access some sort of recovery menu/method. A brick is when it won't turn on at all or it will turn on but won't do anything (or freeze at splash screen).
mlin said:
So... as the man said, if you got it working then it wasn't really "bricked."
Tapa tapa tapa
Click to expand...
Click to collapse
Who said it was working?
I very clearly said that it wouldn't work, no matter what method was used. Please reread my original post. I don't think you understood what I said. Though you could get the phone into bootloader, the screen was not on. The only reason you would even know the phone was on was if you had it hooked up to your comp when you powered up. There was no method you could use that would allow anything to be written to the internal memory. There was a hardware problem with some of the evos, where in they have a TON off bad blocks. This prevented the os from being rewritten. I have meet a few other guys on xda who have the problem with bad blocks. So, how would you define this, if not as a brick? It wasn't hung up somewhere. It was totally unusable. After spending 2 hours on IRC, we decided it was totally unfixable. Took it to a sprint repair center the next day and, funny enough, they agreed. They couldn't even access it enough to tell that I had an unlocked bootloader. Yes, they replaced it.
tejasrichard said:
Who said it was working?
I very clearly said that it wouldn't work, no matter what method was used. Please reread my original post.
Click to expand...
Click to collapse
Ok, fair enough and my bad for misreading your post and I realize that I misread Clamknuckle's original post which is why I misinterpreted yours. SOmetimes I just gotta slow down a bit I guess.
mlin said:
Ok, fair enough and my bad for misreading your post and I realize that I misread Clamknuckle's original post which is why I misinterpreted yours. SOmetimes I just gotta slow down a bit I guess.
Click to expand...
Click to collapse
No big deal, man
The whole thing is pretty silly, anyway. My only point was you could be bricked and still have your charge light comer on. No hard feelings here.
Tejasrichard is right. I got one of the bad blocks phone, brand new too. I guess ill use it for a spare touchscreen
Bootup Problem
So I have an evo that when powered up only displays the startup white HTC EVO 4G screen for 5 sec....turns off for 3 or 4 sec then back on and same in a continuous loop. I can access regular android recovery with the white screen and androids on the bottom. When I choose recovery from the options on that page it does nothing but the white HTC EVO 4G screen boot looping over and over.
Things I have tried:
New SD Card
PC36IMG - tons of them from many methods
Flash a new recovery
The computer does recognize the phone but I can't find it anywhere?
Any help ?
PM me please.
clamknuckle said:
That's not a brick. A brick is when your device will not do anything. Won't power on, won't even light up when you plug it in. There's nothing you can do with a true brick, that's why it's named that way.
If you can get into bootloader, you can recover your device.
Click to expand...
Click to collapse
X2!.................
After trying this method my phone stills only boots to the white screen
I know we're going to get at least one person who says their phone is bricked. Here's how to unbrick it (links to stock rom/kernel, etc) for Virgin and Sprint versions:
http://www.howardforums.com/showthread.php/1691827-Intercept-free-stock-ROMs-and-apps!
You'll need to know how to install and patch SWUpdate for the Moment so it works for the Intercept. Not hard at all.
Did I miss something? How did we go from the EVO to the Moment/Intercept? Anyhow I'm having the same problem as whoisjlk in post #14. Please if anyone has a solution I would greatly appreciate it and even donate. PLEASE PLEASE PLEASE...thanks in advance.
Wow I guess I posted in the wrong section LOL.
Ok, I have an Evo that I would like to recover from the dark side.
I rooted my HTC EVO 4g using Unrevoked, it worked fine, then I decided to flash a new rom, followed all the steps and I backed up my stock and wipe data/factory reset and Davik, now my phone doesn't read the sd card.
Took the sd card out and did a FAT32 format (4 times already), downloaded the new zip to it and still not reading.'
Bought a couple different SD cards.
Can't do a restore because the sd card and is not recognized.
As soon as I check install zip from card it reads
ClockworkMod Recovery v2.5.0.1
E:Can't mount /dev/block/mmcblk0 (or /dev/block/mmcblk0p1)
(No such file or directory)
E:Can't mount /sdcard
Now I know Amon RA Recovery is way better.
I had S-OFF, after wipe all data have S-ON and don't know why.
This is what I tried:
All kinds of PC36IMG (Recoveries, ROMS, Unrevoked S on and S off)
ADB doesn't work.
Phone is not found, when try to update drivers using Windows 7 it says that Qualcomm-CDMA-Technologies-MSM driver is not found, but my other EVO and the ones that I rooted have no problems.
Phone boots into HBOOT and Recovery.
After opening HBOOT PC36IMG gets recognized but not updated.
In recovery when try to flash from SD has the message E: Can't blah blah
If I try to reboot the phone, it just goes to a black screen with a flashing LED or gets stock on white screen forever.
Any ideas?
I would like to fix it, already have a working phone, and I don't need this one, is just to put all the help together and maybe some one that has a similar problem can avoid all the troubles and follow a single post and not spend hours searching just to find the wrong answers.
Otherwise is going to be just for spare parts and that doesn't help many.
Thanks in advance.
If you have an idea, lets try it, PM or reply here.
Tried this but I have this error after Fastboot :
HBOOT > FASTBOOT > no image or wrong image
also, tried factory reset but it just freeze or nothing happens after I chose FACTORY RESET.
Please help.
MarlX said:
Tried this but I have this error after Fastboot :
HBOOT > FASTBOOT > no image or wrong image
also, tried factory reset but it just freeze or nothing happens after I chose FACTORY RESET.
Please help.
Click to expand...
Click to collapse
Some questions, is your phone a standard DESIRE S, S-ON, with standard HBOOT etc?
I'd wait for someone with more Android experience than myself to confirm this, but, I believe that you should attempt to re-flash your original ROM (RUU). Which you should hopefully find somewhere in this post http://forum.xda-developers.com/showthread.php?t=1002506
ben_pyett said:
Some questions, is your phone a standard DESIRE S, S-ON, with standard HBOOT etc?
I'd wait for someone with more Android experience than myself to confirm this, but, I believe that you should attempt to re-flash your original ROM (RUU). Which you should hopefully find somewhere in this post http://forum.xda-developers.com/showthread.php?t=1002506
Click to expand...
Click to collapse
Thanks for the reply.
It's S-ON, this is untouched so I guess standard HBOOT?
Is flash(ing) ROM can be done even phone is not rooted?
Also, been searching around and found this (almost) same problem encountered, regarding "No image...", but I'm hesitant coz now I have to start from scratch again after that(?). :/
http://forum.xda-developers.com/showthread.php?t=648864
MarlX said:
Thanks for the reply.
It's S-ON, this is untouched so I guess standard HBOOT?
Is flash(ing) ROM can be done even phone is not rooted?
Also, been searching around and found this (almost) same problem encountered, regarding "No image...", but I'm hesitant coz now I have to start from scratch again after that(?). :/
http://forum.xda-developers.com/showthread.php?t=648864
Click to expand...
Click to collapse
You should be able to flash an official HTC ROM, without ROOT. Although if you are operator locked ie T-Mobile/Vodafone etc you may have to install one of their ROMS. Although I'm a little out of my depth/comfort zone with all this...
I may be well off the mark here, but, have you tried it, without your SD card inserted? give it a go?
What you found is related to something different. and related to image files stored on your SD card used for updating....which is what made me make the above suggestion.
After a factory reset you will have to start a fresh anyway.
Ohh. So it's not related.
My phone looks like this :
SAGA PVT SHIP S-ON RL
HBOOT-0. 98. 0000
RADIO-38. 03. 02. 15_M
e-MMC-boot
Mar 10 2011, 14:58: 38
HBOOT
vol <up>......
vol <down>......
POWER
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
Click to expand...
Click to collapse
FASTBOOT goes to BOOTLOADER menu which shows me the "No image..."
RECOVERY works but then after the process it turns off, and vibrate several times.
FACTORY RESET if selected, nothing happens, like it froze or something.
Did you try it without an SD as suggested?
The IMAGE errors I think (but could be wrong) are as a result of FASTBOOT auto checking for the existence of update files on your SD and simply not finding any!
Does it say Checking.....
If you select FASTBOOT then REBOOT what happens? Phone hangs? with what screen?
Hopefully someone else will add some advice soon?
ben_pyett said:
Did you try it without an SD as suggested?
The IMAGE errors I think (but could be wrong) are as a result of FASTBOOT auto checking for the existence of update files on your SD and simply not finding any!
Does it say Checking.....
If you select FASTBOOT then REBOOT what happens? Phone hangs? with what screen?
Hopefully someone else will add some advice soon?
Click to expand...
Click to collapse
Yes, I did. It's same.
If I put the SD in it, when chosing FASTBOOT the errors looks like the attachment in this topic : http://forum.xda-developers.com/showthread.php?t=703761
Yes it say Checking...
Doing FASTBOOT then REBOOT shuts down the phone then restarts it and hangs at the green HTC logo.
I really wish someone can help me.
BTW, regarding the ROM's you provided above, what do you suggest is the one for me? I really don;t have any idea. I'm from Asia (Philippines) and phone is not locked by a mobile carrier.
MarlX said:
Regarding the ROM's you provided above, what do you suggest is the one for me? I really don;t have any idea. I'm from Asia (Philippines) and phone is not locked by a mobile carrier.
Click to expand...
Click to collapse
I've found a very similar sounding problem experienced by another user in this thread
I'm afraid that I don't know which of those ROMS would be best for you, I imagine one of the HTC ones, sorry....
Ensure that you continue to keep charging your device. Now, I'm grasping at straws now, but have you tried the above without a SIM inserted?
Same problem
I had the same problem much times!
I had to Factory Reset my phone every time it freezes!
When i did a factory reset, it was all ok until it appeared again
The only solution i found was to factory reset the phone..
ben_pyett said:
I've found a very similar sounding problem experienced by another user in this thread
I'm afraid that I don't know which of those ROMS would be best for you, I imagine one of the HTC ones, sorry....
Ensure that you continue to keep charging your device. Now, I'm grasping at straws now, but have you tried the above without a SIM inserted?
Click to expand...
Click to collapse
Yes, I also did that. Unfortunate, nothing happens, if it does not froze it boots to that green HTC logo and stops there.
I guess the only solution is to bring this to the store where I purchased it.
ben_pyett said:
I've found a very similar sounding problem experienced by another user in this thread
I'm afraid that I don't know which of those ROMS would be best for you, I imagine one of the HTC ones, sorry....
Ensure that you continue to keep charging your device. Now, I'm grasping at straws now, but have you tried the above without a SIM inserted?
Click to expand...
Click to collapse
Yes, I also did that. Unfortunate, nothing happens, if it does not froze it boots to that green HTC logo and stops there.
I guess the only solution is to bring this to the store where I purchased it.
MarlX said:
I guess the only solution is to bring this to the store where I purchased it.
Click to expand...
Click to collapse
Did you read the very similar sounding thread that I found http://forum.xda-developers.com/showthread.php?t=1107016&highlight=boot? unfortunately this is what that person ended up doing
If someone can advise which ROM would be the best for you to select then I'd possibly try that before returning it?
Good luck...
I've seen another user @Skanob also from the Phillipines, if you look at the details within his signature in the following post http://forum.xda-developers.com/showpost.php?p=14748687&postcount=4 you should see details of the RUU ROM that you can/should try to flash.
I am actually downloading it now.
Hope this will fix it.
This will not void the warranty, right? Coz I'm gonna bring the phone to the service center later (it's 12.30AM here atm).
MarlX said:
I am actually downloading it now.
Hope this will fix it.
This will not void the warranty, right? Coz I'm gonna bring the phone to the service center later (it's 12.30AM here atm).
Click to expand...
Click to collapse
I'll be perfectly honest, I don't know if this voids warranty....sorry..
Ultimately, you're only putting back the same ROM as the phone has on it originally, but, bear in mind that in the other thread I posted above, re-flashing the original ROM didn't resolve the issue, so if there's any doubt that this might void the warranty - don't do it!
MarlX said:
I am actually downloading it now.
Hope this will fix it.
This will not void the warranty, right? Coz I'm gonna bring the phone to the service center later (it's 12.30AM here atm).
Click to expand...
Click to collapse
Flashing RUU won't void the warranty. How long are you waiting on the htc logo screen? It can take a while after factory reset...
It might be that some files were corrupted so flashing RUU should help. If not, connect your device to computer and see what logcat is showing
Sent from my HTC Desire S using XDA App
The longest was 25 minutes, then had it reboot again coz nothing happened. Also, when doing the Factory Reset it just hangs/do nothing, can't choose any option from the menu, have to remove the battery to turn the device off.
I'm gonna bring the phone to the service center in a while.
OK.. here we go.. I bought my VERIZON M8 the day it was released. I came to this site, after having successfully put the viper Timon my DNA. Not exactly.new to this but I'm in a bit of a mess. I have tampered above unlocked on my bootloader screen and when I boot into the ROM I am using... A message flashes at the bottom saying for development use only and other legal stuff from HTC. What steps can I take to remove those? I have permanent s-off and weaksauce still installed. Is there a toolkit like for the m7 or am I missing something? Help is appreciated.
Joeymaz73 said:
OK.. here we go.. I bought my VERIZON M8 the day it was released. I came to this site, after having successfully put the viper Timon my DNA. Not exactly.new to this but I'm in a bit of a mess. I have tampered above unlocked on my bootloader screen and when I boot into the ROM I am using... A message flashes at the bottom saying for development use only and other legal stuff from HTC. What steps can I take to remove those? I have permanent s-off and weaksauce still installed. Is there a toolkit like for the m7 or am I missing something? Help is appreciated.
Click to expand...
Click to collapse
I see a message about "Development use only for HTC" or whatever when booting into the bootloader (or recovery...or both...I can't remember), but it doesn't affect anything. Is that what you're referring to? Also, remove Weaksauce like the S-Off instructions told you to do.
And what exactly is this "mess" you're in? If a message flashes across your screen and then your phone finishes booting into the ROM, that doesn't exactly sound like a mess to me...
sfreemanoh said:
I see a message about "Development use only for HTC" or whatever when booting into the bootloader (or recovery...or both...I can't remember), but it doesn't affect anything. Is that what you're referring to? Also, remove Weaksauce like the S-Off instructions told you to do.
And what exactly is this "mess" you're in? If a message flashes across your screen and then your phone finishes booting into the ROM, that doesn't exactly sound like a mess to me...
Click to expand...
Click to collapse
I guess I'm just ocd. I dont like seeing those messages if i dont have to.I had originally. Removed weaksauce.. but put it back on when the permanent. Root didn't take effect properly. Is everyone seeing tampered? If not I'd prefer to be able to get rid of it as well.
Joeymaz73 said:
I guess I'm just ocd. I dont like seeing those messages if i dont have to.I had originally. Removed weaksauce.. but put it back on when the permanent. Root didn't take effect properly. Is everyone seeing tampered? If not I'd prefer to be able to get rid of it as well.
Click to expand...
Click to collapse
If flashing the superuser zip didn't work correctly for you, that's an issue you should probably look into...
Like I said, I don't see it say "tampered", I just see the "This build is for development purposes only" message when I boot into recovery. You're sure you see it when booting normally into the ROM itself?
sfreemanoh said:
If flashing the superuser zip didn't work correctly for you, that's an issue you should probably look into...
Like I said, I don't see it say "tampered", I just see the "This build is for development purposes only" message when I boot into recovery. You're sure you see it when booting normally into the ROM itself?
Click to expand...
Click to collapse
go here: http://forum.xda-developers.com/showthread.php?t=2709976
kwkw480 said:
go here: http://forum.xda-developers.com/showthread.php?t=2709976
Click to expand...
Click to collapse
Yeah, but unless if he also flashed a custom boot.img (or a ROM that has a custom boot.img included), or is actually booting into recovery when he sees it, he shouldn't be seeing it when he boots into the ROM itself.
Edit: I just misread the OP, apparently he may be using a custom ROM, I didn't notice that before.
sfreemanoh said:
Yeah, but unless if he also flashed a custom boot.img (or a ROM that has a custom boot.img included), or is actually booting into recovery when he sees it, he shouldn't be seeing it when he boots into the ROM itself.
Edit: I just misread the OP, apparently he may be using a custom ROM, I didn't notice that before.
Click to expand...
Click to collapse
Sorry Guys, I should have told you which ROM I had flashed to.. SKYFALL★| |►1.12.605.11◄|4.4.2|VZW||ODEX/DEODEX||►1.2◄|April.10. I'll follow the directions pointed to in the thread above when I get home.. Still leaves me with "tampered" when I boot into recovery or bootloader.
kwkw480 said:
go here: http://forum.xda-developers.com/showthread.php?t=2709976
Click to expand...
Click to collapse
Ok.. That zip file, for the red letters worked great. thank you..
after a bunch of searching.. I found this..http://forum.xda-developers.com/showthread.php?t=2708565
thanks for everyone's help. I appreciate everything you do.
Or you can go here where there are a variety of options including making your phone look like it is still s-on
http://forum.xda-developers.com/showthread.php?t=2710503
Thanks for that tool page. I love learning new things about these phones. 20 years I've just been a PC guy.. learning how to do some of this can be tricky. Thank goodness for this forum and the people on it.