My spv e650 does't boots. - HTC Vox

Hi.
I haven't found any thread about problem like my phone has. It was last time when it got ran out of battery and shut down. I've connected it to charger and switched it on but it stopped on that red - green - blue screen. Of course there was another flashing screen before, almost impossible to read - "Booting from SD". So i tried it and formated my micro sd to fat32, copied VoxRomWM6.5Clean_v3.1.nbh (from fireburned) and renamed it to Vox0img.nbh, like someone said before. It looks like working - "Checking SD contents", then phone asks me if i want update SD image. I confirm and it's "Formating BINFS", "Reading from SD", "Verifying certificate", "Flashing first phase of OS", "Reading second OS from SD", "Flashing second phase of OS"... Then the phone says "Success. Press any key.", but it gets me to the same old screen of bootloader, and everything is the same, after restart too...
Old OS was WM6.1 by Dr.Gonzo... And if it would be a clue, more than month before my phone was sunken for several seconds, but i disasembled it immediately (With very usefull htc's manual) and dried. Everything was ok, even after that accident. I've mentioned about that because maybe there is a possibility the connections are responsible for that, but i've checked and cleaned main 3 of them but nothing has changed...
Has anyone any soultion for me? Please.

Related

Odd bootloader issues.

I had posted this in the stickied bootloader thread, but I'm pretty sure I posted to the wrong spot. If a mod wants to move this to another thread then by all means...
My kaiser is doing something I haven't heard of yet. Recently its started to act funny after 6 months of no new software, tinkering, flashing - nothing.
3 days ago I had to restart due to the sound cutting out and I got stopped at the bootloader. After fiddling with it, soft resetting multiple times, taking out the battery (just random low level troubleshooting) it booted into windows. This happened sporadically one or two more times.
I have also noticed that in the last 3 days the phone will suddenly drain to no battery without any warning. I will have 25% battery and be on a call for 20 minutes, then have the phone completely power off. normally, windows alerts me to high heaven with multiple warnings, etc. None - just powered off. After 30+ minutes of recharging in the off state, I powered on... bootloader again.
I hooked it into USB and sent the mtty "boot" command. This worked, it booted straight into windows. Due to my frequent sound problems I figured I'd load on a new radio "just in case" - so I loaded on the eMo radio via the sd card method, and soft reset. Again, bootloader. So I gave it the mtty BOOT command and got into windows... so far so good.
I soft reset just to see what would happen - bootloader.
Now I find myself having to soft reset frequently because the sound will just stop working at random. Of course when I soft reset I get bootloader but just today I found something very interesting: If I plug the phone into USB then simply soft reset it will restart and go right into loading windows. This works from inside windows as well as when I'm stuck at bootloader.
Is this common? My rom is Dutty's 6.1 from April 29. My radio is currently 1.71.09.01.emo. Thanks guys
*edit* now every time I hang up a phone call the earpiece starts making a "TV snow" or "power lines" kind of noise. This of course requires a soft reset which may or may not send me into bootloader. it varies.
I'm no flashing or rom expert by any means but if I were you, I would remove SD card, flash a different hardSPL other than what you're using now, flash a another cooked rom, and another radio. Starting from scratch sounds like the way to go. Good luck ...
I flashed a new SPL (3.29 fixed) and switched from dutty's to hyperdragon III Nov 6. I'm pretty sure this has fixed it.

Touch Pro stuck on bootscreen

Hi.
My phone shows strange behavior now 2 times in a row: After some time, i suddenly get an error, that some exe wasnt found and i cannot start any application, the start menu gets empty, etc.
It's like he cannot access the hard-drive ( ) anymore, just like what happens if you turn your hard-disk off while xp is still running (try it, its fun!)
Afterwards, i cannot get past bootscreen if i soft-reset. ONLY a hard-reset or reflashing works.
I remember, that i didn't always did a hard-reset after flashing a new rom, could this MAYBE be the issue? I flashed my phone after the first incident and now did a hard reset after the second one.

My Sda dont power on... but show the tmobile logo?????????

HI, the problem is that phone dont start, what happens is that when attempting to turn it only shows the Tmobile logo for a few seconds, then turns off and comes back the logo, and definitely off, the LED light dont turns on but displays the logo when power on the cellphone!!!!!!!!!!
I appreciate your help
Step 1:
It could be a problem with the battery - reboot while the charger is connected
and/or let the battery charge fully before turning on the device. Use a different battery if you can get for a try-out.
Step 2:
Remove the SD card, sometimes a faulty card prevents the boot.
Step3:
If the boot does not go to the operating system, then also the settings in the OS may prevent a clean boot. This is very unusual, but you could try to reset the device to the "out of the box" settings (hard reset). You will loose all data and installed programs on the device though in that way.
Step 4:
If the OS is corrupt (how could that happen?) you may want to re-flash the operating system. Take the last available official ROM for that - you will not have to deal with any "special" unlocking stuff. Needless to say that you will also loose everything on the device.
Hi
I have this problem too. T-Mobile SDA Music Edition (Tornado) starts to T-Mobile logo and turn off. I read a lot about it and I think its corrupted after flashing to WM6 (it was'nt my phone). When I write to TeraTerm "info 2" it looks like its CID locked...
Is it enough to return to the original WM5 ROM??
If yes, wher can I find it??
Edit:
I found t-mobile SDA ROM in this post:
http://www.howardforums.com/showthread.php/1035146-SDA-ROM-disappeared-from-HTC-site-Why
but it didn't help:/
Edit:
It works After second flashing SDA alive. First time don't work because battery

[Q] Xoom Never Rooted - Stuck at Logo

I bought my Xoom when they first came out and have never rooted or unlocked it. It's been a good tablet all these years, but for no apparent reason, now won't boot up. I haven't loaded any new apps on it in months. I picked it up off the charger one morning and it was frozen. I rebooted it, and it refuses to go past the "M" logo screen. Multiple soft resets had no effect. I tried a factory reset - it says "Wiping data...Performing BP Clear...BP clear failed. Formatting /data...formatting /cache...Data wipe complete." Another reboot takes me back to the "M" screen, and I'm stuck once again.
I loaded up the Motorola drivers into my computer, and plugged the Xoom in. The computer sees it on a hardware level (in Devices, it shows up as MZ602, but it never shows up as a drive letter where I could actually drag files to and from it. (As I recall, it has to be fully booted and on before it shows up as a drive letter, but I may be wrong on that. I haven't plugged it in to the computer very often)
So I'm out of ideas, other than spending $160 to send it back to Motorola repair, which I don't think I'll do for a four year old tablet. Any ideas, anyone? Thanks!
jfran2 said:
I bought my Xoom when they first came out and have never rooted or unlocked it. It's been a good tablet all these years, but for no apparent reason, now won't boot up. I haven't loaded any new apps on it in months. I picked it up off the charger one morning and it was frozen. I rebooted it, and it refuses to go past the "M" logo screen. Multiple soft resets had no effect. I tried a factory reset - it says "Wiping data...Performing BP Clear...BP clear failed. Formatting /data...formatting /cache...Data wipe complete." Another reboot takes me back to the "M" screen, and I'm stuck once again.
I loaded up the Motorola drivers into my computer, and plugged the Xoom in. The computer sees it on a hardware level (in Devices, it shows up as MZ602, but it never shows up as a drive letter where I could actually drag files to and from it. (As I recall, it has to be fully booted and on before it shows up as a drive letter, but I may be wrong on that. I haven't plugged it in to the computer very often)
So I'm out of ideas, other than spending $160 to send it back to Motorola repair, which I don't think I'll do for a four year old tablet. Any ideas, anyone? Thanks!
Click to expand...
Click to collapse
have u tried re-flashing the rom?

P3100 16GB - bricked or emmc bug? what to do next?

Greetings xda-developers,
I own a galaxy tab 2 P3100 16GB model since march 2013 (pretty old yeah, but i like it, its my first tab ) It is running everything stock (recovery plus OS, JB 4.1.2).
It was working all good and serving good for my browsing, whatsapp, mails, youtube, hotstar etc etc. (heavy user of tab) Suddenly on one fine Sunday morning it restarted by itself. I thought this to be normal but it wasn't. After every 10 to 20 seconds I could hear the starting tone. When i looked to the tab, it was pretty warm on the left side where it usually does when used heavily, but it was acting strange.
The tab was restarting by itself! The home screen appears, i could start an app and suddenly it restarts and this continues every 20 seconds until the battery goes low.
I thought two new installed apps would e problem so i removed them and to my surprise(!), they were back again after next 'auto restart'. The 'auto restart' stuff happened back in January this year (after my nephew installed many games on it) but was solved when I did factory reset from settings menu.
But this time nothing successful. Neither factory reset from settings menu nor from recovery. I have tried using twrp and CM11 last year but returned to stock after few months.
I tried flashing twrp, cwm recoveries but after every boot it returns to stock. Even flashing OS didn't helped.
My problem is similar to these:
https://forum.xda-developers.com/showthread.php?t=2641158
and
https://forum.xda-developers.com/showthread.php?t=2627490
and
https://forum.xda-developers.com/galaxy-tab-2/help/unable-to-install-twrp-t3696545
Also the stock recovery screen shows the following at bottom:
# Manual Mode #
-- Appling Multi-CSC...
did not match sized '/system/csc/common/system/csc/default_workspace.xml'(No data available)
(I wanted to attach image to this post but could not find an option.)
From all my readings on this forum, I can conclude (?) that its an emmc issue (end of life?).
Need your help guys.
The tab is in excellent condition except this issue. Can this be solved?
I am from electronics and embedded system (microcontrollers) profession and hobbyist. I know replacing emmc or motherboard (or scrapping the tab, NO! i don't want to though i now own the Lenovo tab 4 8 plus 3GB RAM+16GB version ) is an obvious solution.
A (may be obvious) possibility came in my mind if external memory card could be used for booting and I (and many others) could bring their tab to use (instead of making it a paperweight )
I though this to be possible solution: https://forum.xda-developers.com/galaxy-tab-2/general/discussion-alternative-tab-2-emmc-bug-t3306862
but i am not able to understand the instructions and the links posted by OP are not functional.
Can this be a solution:
https://forum.xda-developers.com/showthread.php?t=1866675
OR
I am thinking of this:
I got schematics and service manual for p3100 from internet. I looked the datasheet for OMAP4430. I am thinking whether the boot sequence can be changed (or may be no need to change the sequence) and we can boot from external micro SD card
or something like
https://forum.xda-developers.com/showthread.php?t=1312391
or can https://forum.xda-developers.com/showthread.php?t=2109044 be used?
But whenever i plugged my tab in windows without battery or with battery, initially i could see new device found 'OMAP....' something but immediately after 2 or so seconds it shows device unplugged.
Any comments guys?
Thanks for reading patiently the long write up...
You can't boot from external SD because you aren't able to flash a high modified boot.img if your emmc got read only.
You'll need to replace the emmc or find someone who can flash an updated emmc firmware via isp (but the issue might come back in short time after firmware update).
Thanks for reply.
Well i have to search someone from my nearby city for such service.
Is it not possible booting from external even if the boot sequence is changed, i mean if hardware is modded to change boot sequence?
Humm but it will require the primary and secondary bootloaders then...
The pandaboard has increased by curiosity of such possibility. I think i need to study more...

Categories

Resources