Database Develop

Software or hardware problem?

HTC TyTN II
1. Wirlles DOES NOT WORK
2. Sometimes the signal does not work
3. The camera DOES NOT WORK
4. disc does not work
5. World to the keyboard does not work
Is this a software problem?
Sorry on my bad english.

konzul said:
HTC TyTN II
1. Wirlles DOES NOT WORK
2. Sometimes the signal does not work
3. The camera DOES NOT WORK
4. disc does not work
5. World to the keyboard does not work
Is this a software problem?
Sorry on my bad english.
Click to expand...
Click to collapse
Back up you data and do a hard reset. If the problems persist, you can pretty mouch assume it is a hardware problem.

Hello
I have some problems with the storge.. i have it find with MTTY
when I start my phone it won't show the radio version ect. only the boot display will work for few seconds
and it's crashs! What can i do!? I have flash some roms.
it flashes and it go but it didn't start it.
HardSPL 1.0 from oli
Rom before crash: NoThrills_WM61_GER_V3

meylan said:
Hello
I have some problems with the storge.. i have it find with MTTY
when I start my phone it won't show the radio version ect. only the boot display will work for few seconds
and it's crashs! What can i do!? I have flash some roms.
it flashes and it go but it didn't start it.
HardSPL 1.0 from oli
Rom before crash: NoThrills_WM61_GER_V3
Click to expand...
Click to collapse
Try upgrading your hardspl to 33.4 or 3.29 ,1.0 is a WM 6.0 hardspl.

I have try to upgrade Hardspl many times. And it doesn't do it
so I have try to fix my storege yesterday and then it's broke
then i want start only the lcd goes green.
no screen anymore
task 28 55aa
Format start
Fill RSVD information for block 288 to 309
Storage start sector=0x8DC0, total sector=0x12500
Storage start block=588, total block=1172
Total Bad Block in CE: 0
Erase physical block from 876 to 2048
formatstorage Bad block found: 1603
Format end
Cmd>task 2a
Format ALL start
backup SPL OK
backup MISC configuration OK
SPL start start block=288, total block of CE=1760
ERASE block 1315 FAIL !!!
Write 0xFF start page=0x4800, total page=0x1B800
SPL version and MFG TAG are same, skip it.
restore SPL OK
restore MISC configuratoin OK
restore MFG configuratoin OK
Format ALL end
Cmd>task 32
Cmd>task 37
Invalid debug log data. Please check debug log raw data in addr 0xAE100000
Cmd>task 28
Format start
Fill RSVD information for block 288 to 309
TAG NOT FOUND !!! NOT CLEAR STORAGE !!!
Format end
Cmd>erase
HTCST ÚÈÒHTCE
Cmd>erase a0040000
HTCST ÚÈÒHTCE
Cmd>checksum
Cmd>checkimage
SPL CRC checksum = 0x5507A35A
CE is None.
ExtROM is None.
Cmd>info 8
--- 2K bytes sector version ---
DEVICE NAME=samsung_k9k2g08
DEVICE ID=0xAA
DEVICE MAKER ID=0xEC
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x800
BLOCK PAGE=0x40
Checking block information
BLOCK 8 (0x8) is reversed block
BLOCK 1315 (0x523) is bad block
OS NOT FOUND !!!
Cmd>info 7
CPLD ID=0x8
Cmd>wdatah
Command error !!!
Cmd>rtask 0
Cmd>rtask 4
Cmd>checkimage
SPL CRC checksum = 0x5507A35A
CE is None.
ExtROM is None.
Cmd>password BsaD5SeoA
Pass.
HTCST ÚÈÒHTCE
Cmd>ruurun 0
Command error !!!
Cmd>ResetDevice
what i can do ? since last command it didn't start it

try a new radio and maybe it'l work

meylan said:
what i can do ? since last command it didn't start it
Click to expand...
Click to collapse
The reason it won't start anymore is because you ran Task 2a, which, unlike previous devices, formats EVERYTHING away, including the SPL and Windows Mobile. It essentially bricks the device, as it will not boot past OEMSBL (The radio bootloader, it comes first in boot order and loads the SPL, AFAIK). As soon as the device is reset after running the Task 2a command, the device will not boot as there is no OS bootloader, nor is there anything to boot. However, Jockyw2001 has created tools which may help to recover from a task 2a. A thread concerning Task 2a bricks can be found here. Best of luck with recovering your device.

DaveTheTytnIIGuy said:
The reason it won't start anymore is because you ran Task 2a, which, unlike previous devices, formats EVERYTHING away, including the SPL and Windows Mobile. It essentially bricks the device, as it will not boot past OEMSBL (The radio bootloader, it comes first in boot order and loads the SPL, AFAIK). As soon as the device is reset after running the Task 2a command, the device will not boot as there is no OS bootloader, nor is there anything to boot. However, Jockyw2001 has created tools which may help to recover from a task 2a. A thread concerning Task 2a bricks can be found here. Best of luck with recovering your device.
Click to expand...
Click to collapse
agh f*** thanks i didn't know that...
It's normal that the device isn't detected as qualm anymore?
it display me by connecting with Pc: "DATA LINK" or so

meylan said:
agh f*** thanks i didn't know that...
It's normal that the device isn't detected as qualm anymore?
it display me by connecting with Pc: "DATA LINK" or so
Click to expand...
Click to collapse
When I manually put my phone in OEMSBL, which is what yours should be in when you turn it on right now (the light is green but the screen stays black), windows detects it in Device Manager as: ZTE NMEA Device CDMA 1X, ZTE Diagnostics Interface 6000 CDMA 1X, ZTE USB Modem 6000 CDMA 1X. It should also detect the GPS and some other stuff, but I can't find those in Device manager.

mhh i used MTTY but i can't get in download mode
what commands should I write?

meylan said:
mhh i used MTTY but i can't get in download mode
what commands should I write?
Click to expand...
Click to collapse
This kind of stuff is too complicated for me, so I can't answer that myself. However, there are many threads that talk about task 2a resets and how to recover from them. Here, here, and here are all good places to start. But keep in mind that you should NOT try anything in these threads unless you have read everything, and are absolutely sure that the tool is for your specific situation. For example, DO NOT use the FrankenKaiser version in the third link if you don't have the Radio from Hell installed.
Alternatively, you could try the XDA IRC channel, or PM jockeyw2001.
Once again, best of luck repairing your brick.

Unmodded restore problems!!!Write protected? Also some Valuable Information

I recently aquired a Streak 7 and am having trouble resetting it since it has all the original owners info on it.
1. I encountered a force close error upon first boot.
- android.process.acore stopped unexpectedly
2. After this error continued to appear I said F*** this and rebooted into the Stock Dell recovery(Volume + and Power)
I chose option 3 for a factory reset and erase internal tablet storage.
Rebooted and Bam same bull**** errors. I did this 3 more times powering off with the pin hole off button after the streak kept booting with this error.
I read this entire forum development and general questions to see what problems others are having, I came across a few threads all very informative on how to attempt to restore your Streak 7.
Before attempting the various methods of either NVFlash, the fastboot method and even flashing clockwork recovery through fastboot I figured I would see what I could get the Streak to do in it's current state.
*Note* I am very familiar with ADB and Fastboot but if I over looked something I will not be offended if anyone can provide some useful information.
OK, Here is my story
I put the streak on my HDMI dock and was able to succefully install the ADB drivers on Windows 7 x64. From there I launched the ADB Shell
c:/androidsdk/tools> adb shell
$
once in the shell i found I could launch the android setting using this command
$ am start -a android.intent.action.MAIN -n com.android.settings/.Settings
Once in the settings and periodically hitting forceclose and quit to the .acore error I was able to retrieve this information
Android Version
2.2
Baseband Version
11.809.05.02.00
Kernel version
2.6.32.9
OEM Version
GLUNB1A132433
Build Number
14394
I also realized that I can install apps through adb so I went and installed the latest standalone ADW Launcher which installs fine and allows me to actually use the device a little.
c:\androidsdk\tools>adb install launcher.apk
1307 KB/s (2533717 bytes in 1.892s)
pkg: /data/local/tmp/launcher.apk
Success
You will notice that apps install to this location
/data/local/TMP
it turns out that even installing the new launcher won't allow me to do much because the previose owner changed his google password so I have no market acces or anything like that.
I then tried doing the factory reset within the Android settings>privacy>factory data reset.
The device reboots and I again encounter the same error and the device has also not reset the user data.
So i rooted the device and found that even root was only temporary, the ADB shell returns the # sign indicating that it has root, great but when the device is rebooted it returns to the condition I got it in.
If I run ADB remount with root I get this
c:\androidsdk\tools>adb remount
remount failed: Operation not permitted
c:\androidsdk\tools>
this tells me that even though the phone has root it will not mount any file system with read/write permissions
I then installed the latest free Clockwork Rom Manger via ADB
it prompts me for root permissions I select allow and then the app closes after it downloads and tries to write the clockwork recovery image. I said fine this won't work.
I moved on to the Flashing Clockwork Recovery via Fastboot
In Fastboot I get this
c:\androidsdk\tools>fastboot devices
? fastboot
c:\androidsdk\tools>fastboot -i 0x413C flash recovery clockwork.img
sending 'recovery' (4416 KB)...
OKAY [ 0.560s]
writing 'recovery'...
OKAY [ 0.110s]
finished. total time: 0.670s
c:\androidsdk\tools>
WOW I didn't know that 4MB could be sent and flashed over usb in under a second!!!! WTF!!!!!
So obviously there is something going on here where I cannot write to the internal memory...
I decided to just use NVFlash because people seem to be having luck with it
http://forum.xda-developers.com/showthread.php?t=1018809
I Didn't.......
I spent a hell of a lot of time downloading and redownloading the different images and finally got them all downloaded successfully. I run the restore.bat file and it says everything went fine but it didn't, I tried NVFlash with and without P14.img and it just doesn't seem to do anything it always restores it to how it was when i got it errors and all.
Now for the best method I tried, the fastboot method by flashing boot_orig.img, recovery_orig.img and system_orig.img
http://forum.xda-developers.com/showthread.php?t=1011654
Flash_image is not and ADB Shell command
and I also don't beleive the images are writing to the disc that fast.
I'm tired of typing now so please if anyone has any info on how I can write information to the internal ROM memory not the internal sd card I would greatly appreciate it.
Tom

wikedbubble said:
I recently aquired a Streak 7 and am having trouble resetting it since it has all the original owners info on it.
1. I encountered a force close error upon first boot.
- android.process.acore stopped unexpectedly
2. After this error continued to appear I said F*** this and rebooted into the Stock Dell recovery(Volume + and Power)
I chose option 3 for a factory reset and erase internal tablet storage.
Rebooted and Bam same bull**** errors. I did this 3 more times powering off with the pin hole off button after the streak kept booting with this error.
I read this entire forum development and general questions to see what problems others are having, I came across a few threads all very informative on how to attempt to restore your Streak 7.
Before attempting the various methods of either NVFlash, the fastboot method and even flashing clockwork recovery through fastboot I figured I would see what I could get the Streak to do in it's current state.
*Note* I am very familiar with ADB and Fastboot but if I over looked something I will not be offended if anyone can provide some useful information.
OK, Here is my story
I put the streak on my HDMI dock and was able to succefully install the ADB drivers on Windows 7 x64. From there I launched the ADB Shell
c:/androidsdk/tools> adb shell
$
once in the shell i found I could launch the android setting using this command
$ am start -a android.intent.action.MAIN -n com.android.settings/.Settings
Once in the settings and periodically hitting forceclose and quit to the .acore error I was able to retrieve this information
Android Version
2.2
Baseband Version
11.809.05.02.00
Kernel version
2.6.32.9
OEM Version
GLUNB1A132433
Build Number
14394
I also realized that I can install apps through adb so I went and installed the latest standalone ADW Launcher which installs fine and allows me to actually use the device a little.
c:\androidsdk\tools>adb install launcher.apk
1307 KB/s (2533717 bytes in 1.892s)
pkg: /data/local/tmp/launcher.apk
Success
You will notice that apps install to this location
/data/local/TMP
it turns out that even installing the new launcher won't allow me to do much because the previose owner changed his google password so I have no market acces or anything like that.
I then tried doing the factory reset within the Android settings>privacy>factory data reset.
The device reboots and I again encounter the same error and the device has also not reset the user data.
So i rooted the device and found that even root was only temporary, the ADB shell returns the # sign indicating that it has root, great but when the device is rebooted it returns to the condition I got it in.
If I run ADB remount with root I get this
c:\androidsdk\tools>adb remount
remount failed: Operation not permitted
c:\androidsdk\tools>
this tells me that even though the phone has root it will not mount any file system with read/write permissions
I then installed the latest free Clockwork Rom Manger via ADB
it prompts me for root permissions I select allow and then the app closes after it downloads and tries to write the clockwork recovery image. I said fine this won't work.
I moved on to the Flashing Clockwork Recovery via Fastboot
In Fastboot I get this
c:\androidsdk\tools>fastboot devices
? fastboot
c:\androidsdk\tools>fastboot -i 0x413C flash recovery clockwork.img
sending 'recovery' (4416 KB)...
OKAY [ 0.560s]
writing 'recovery'...
OKAY [ 0.110s]
finished. total time: 0.670s
c:\androidsdk\tools>
WOW I didn't know that 4MB could be sent and flashed over usb in under a second!!!! WTF!!!!!
So obviously there is something going on here where I cannot write to the internal memory...
I decided to just use NVFlash because people seem to be having luck with it
http://forum.xda-developers.com/showthread.php?t=1018809
I Didn't.......
I spent a hell of a lot of time downloading and redownloading the different images and finally got them all downloaded successfully. I run the restore.bat file and it says everything went fine but it didn't, I tried NVFlash with and without P14.img and it just doesn't seem to do anything it always restores it to how it was when i got it errors and all.
Now for the best method I tried, the fastboot method by flashing boot_orig.img, recovery_orig.img and system_orig.img
http://forum.xda-developers.com/showthread.php?t=1011654
Flash_image is not and ADB Shell command
and I also don't beleive the images are writing to the disc that fast.
I'm tired of typing now so please if anyone has any info on how I can write information to the internal ROM memory not the internal sd card I would greatly appreciate it.
Tom
Click to expand...
Click to collapse
Bump for a resolution. A lot of folks seem to be encountering this issue; I think it has something to do with a Linux failsafe measure (from another thread), but I'm not savvy enough in Linux to know for sure. Good luck to you!

Hey Thanks for the Bump, I am tearing my hair out over thins thing.
On another note I found this post for the LG GX2 for flashing clockwork recovery through APX with NVFLASH
http://www.techofweb.com/technology/flashing-cwm-recovery-g2x.html
I hope there might be a way to do this on the Streak, but I don't know that much about NVFlash. My hope in getting the clockwork recovery is that the restore and recovery tools used in clockwork recovery will in theory allow me to format and write roms to the internal memory...... I hope
Anyway I hope someone is reading and understanding my trouble other than Z4nd4r
Tom

I've been having similar problems with my streak7. It was working fine on stock 2.2.2 then got stuck in boot loop at the "stick together" screen.
I tried to factory reset in recovery. No change.
I tried to restore with nvflash. It completed fine, but no change.
http://forum.xda-developers.com/showthread.php?t=1018809
I tried with fastboot (boot.img, restore.img and system.img). It completed fine, no change.
I tried the 2.2.2 update.pkg in recovery, but it stops at "install modem error", no change.
I tried to flash DJ_Steve's honeycomb, and it stops at:
Formatting partition 2 BCT please wait... FAILED!
command failure: create failed (bad data)
bootloader status: partition table is required for this command (code: 8) message: nverror:0x2 (0x2) flags: 0
I tried formatting all partitions with:
nvflash --bl bootloader.bin --format_all
then restore with nvflash
It completes with no errors, but still no change.
I also tried to get clockwork on the streak 7 with fastboot. Even though I didn't get any errors, clockwork recovery did not get installed. So I'm thinking it's some sort of write protect error, since nothing I write to the device seems to be sticking.
If I format all partitions, would the streak 7 even get to the t-mobile "stick together" logo? I would think it would get stuck at the dell logo. I'm stuck at this point and have no idea what to try next. Any suggestions?

Could the problem be due to previous owner(s) trying to root the DS7 and Dell had implemented some kind of security measure to prevent rooting of the DS7?

Bump for a real solution.
I found a solution and my solution was to sell it before I threw it against a wall.

What's the common denominator, here? Were these all purchased used/3rd party?

Mine was bought new and ran great till mothers day and my sis asked to use it to post pics to facebook so I unmounted my sd and gave it to her she poped in her 32 gig sd card and got tired of waiting for the the gallery to populate and ejected the card without unmounting it and handed it back to me and said it was junk an and slow .......ever since its been stuck in read only
Ive dissasymbled it formated it flashed it factory reset it and reguardless of what I do still comes back the same as though I hadnt touched it.......even tried to short the nand chip out to clear it..........its like a cockroarch thats wounded .....it just wont finish dieing

I think we need a jtag solution. Doesn't seem like anything done with current tools will help.
I've scoured the internet and turned up nothing.
My streak 7 is collecting dust and probably going on eBay soon. To hell with Dell. This is my first Dell android device and probably my last.
Edit: found information
So I found the datasheet for the NAND chip the Streak 7 uses (http://omapworld.com/iNAND_e_MMC_4_41_IF_data_sheet_v1_0[1].pdf). Aparently the NAND has a write protect feature (temporary and permanent). Tech5 from this thread http://forum.xda-developers.com/showthread.php?t=1113264 says there's a failsafe function that locks the NAND in write protect mode. I don't have the hardware expertise to dig down and see if the system is write protecting the system by locking the chip in write protect mode. If we can somehow figure out how to disable the write protect on the chip, we may have a solution. Maybe someone with good hardware knowledge can take a look and give some feedback?

I'm having this same issue over here. I've tried NVFLASH and Fastboot and it acts like it's happening and then you reboot and get back to the same image every time. Maybe time for a call to Dell on this?

Call Dell
It looks like these Streaks are all stock and having the same problem. I tried calling dell but they wouldn't help me because the streak I got doesn't have the flap for the sd card and that is where they say the Service Tag is written. Freaking BullSh!t. Anyway if someone is willing to call dell and see what they have to say that would be awesome.

Dell is the only solution?
I had a same problem too. No matter what I do, the unit reverts back. It became Read-Only Mode. I guess it happens often enough DELL aware of this problem and the tech supports knows what to do. Only way to fix the unit at this point is ship it back.
I shipped back to Dell and Dell repaired it. Turn Around time: 1 Week.
This is my 1st post.
I do have Streak 5 and 7. I love Streak 5 and DJ Steve's ROM Rocks in Streak 5.

wikedbubble said:
It looks like these Streaks are all stock and having the same problem. I tried calling dell but they wouldn't help me because the streak I got doesn't have the flap for the sd card and that is where they say the Service Tag is written. Freaking BullSh!t. Anyway if someone is willing to call dell and see what they have to say that would be awesome.
Click to expand...
Click to collapse
Settings > About > Status > Service Tag at the bottom.
I'm on the phone with Dell right now about this as I can't find another solution and another user had to get theirs repaired. We'll see what they say.

Solution to write protect?
I was trying to copy some music to mine and got the write protect error message. I took out the micro SD card holder and it indeed was locked. Flipped the switch and back in business! Hope this helps someone!

I wonder if it is newer streaks that are doing this, because I think mine was in stock with Tmobile for a while. They had plenty of them there. They must be "Locking the bootloader" so to speak. If anyone wants to send one to a Dev maybe they can do something about it.

any luck with this any 1? =(

I had a similar issue last week, it looks to be the "Read-Only" Bug. I had to send mine back to Dell, and they just sent me a new unit.
Whatever you do, make sure your DS7 does NOT hit 0% battery, it seems to be the cause of this "Ready-Only" bug.

MTTY and Error 262 when trying to instal HSPL till the Doc shows up...

Well, what happened:
i flashed hspl
i flashed Dynamics_GTX_2.4.5_WWE_Kovsky.nbh
i was happy
i realized that i cant sim-unlock here, so:
i flashed orig. spl aka RUU_Signed.nbh
and then i flashed original APP_SW_X1i_MOBCOM_AT_CDF1215-0312_KOV_R1AA019.nbh
then i sim unlocked the phone by code
then i went directly for a 28
it hang itself when i tried to do flash hspl at 17%
since then, i get everytime stuck at 0% and get the msg 262
even messing around with mtty and all different roms and programs and settings didnt lead any further.
task 28 looks like:
Cmd>task 28
Format start
TAG NOT FOUND !!! NOT CLEAR STORAGE !!!
Format end
Cmd>
task 29 looks like:
Cmd>task 29
Format BINFS start
CE start start block=321, total block=3775
Write 0xFF start page=0x5040, total page=0x3AFC0
Format BINFS end
Cmd>
task 8 seem to take forever, the screen shines in bright white.
with power and vol down i see:
3 colors
kovs110
spl-0.72.0000
microP1-707
microP2-707
serial (which, ofc. turns into usb when i am connecting it)
from there on everything went fine, but the flashing.
ofc i try to flash hspl, but every method hangs at 0% with error 262
mtty up and running (as far as i can see ) i definitely need help.
crawled the forums für 18 hours now, i cant find a solution to this on my own.
btw. cant load something on the card, otherwise i would have tried to load from the map...
again, i call for HEEEEEEEEEEEEEEELPPPPPPPPPPPP!!!!!!!!

no one? :O
do i have produced a brick?
playing around to find out whats going on:
Cmd>info 7
HTC Integrated Re-Flash Utility, Common Base Version : 1.51d
Device Name: Kovsky, Bootloader Version : 0.72.0000
Cmd>info 8
--- 2K bytes sector version ---
DEVICE NAME=micron_mt29f4g16abc
DEVICE ID=0xBC
DEVICE MAKER ID=0x2C
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x1000
BLOCK PAGE=0x40
Checking block information
BLOCK 0 (0x0) is reversed block
.
.
.
BLOCK 32 (0x20) is reversed block /////// that seems to be quite long, in the documentation it goes just till 12 and then it shows partitions, which are not showed at my device :/
OS NOT FOUND !!!
Cmd>checkimage
SPL CRC checksum = 0xEC2F928F
CE is None.
ExtROM is None.
Cmd>task 32
gives no output.
is it possible to flash per mtty? (LRS?)
btw it boots into white screen, not three color bootloader screen
with power vol down into bootloader without any problems
but from there on it always stucks at 0%
//edit
set up an old laptop with winXP and tried it there - you never know? - didn't work...
//edit #5
got a micro sd card
formated it with fat32, put the RUU_Signed.nbh on it,
renamed it to KOVSIMG.nbh, put it in the phone and started it with vol down and powerbutton to the bootloader.
hangs at loading...

come on guys, some one have to have something to say!

To be honest it does not sound promising
try this with mtty
Cmd>set 16 0
Cmd>task 14 0
Cmd>reboot
then try and flash a stock rom

when copied on the sd card, it hangs at loading
when flashed over usb, it hangs at 0% at the progressbar

if you try another hspl does it just sit at 0% ?

i just tried this one out: http://forum.xda-developers.com/showthread.php?t=431218
are there other versions of hardspl?

sorry i meant doing another hardspl with the version your using

yep... just sitting at loading or 0% depends on the way i try to flash
i think, somehow the partitions are ****ed up,
is there some one who knows the mtty and bootloader stuff very well?

have you thought of trying one of the Android NAND roms? If you can just get it to install, you could then go back to windows mobile

do i not need hard spl for android?
does android not get flashed like a windows rom?
i ll read into that, thx for the tipp

It's similar to windows roms yes, but there is a version (ICS 4.0.4alpha), that changes the internal partitions so as a long shot you could try this and then try flashing back to a windows rom.
The thread in question is
http://forum.xda-developers.com/showthread.php?t=1614236

locked security warning by doing nothing

okay guys this is weird. til now i have only read the forums and did think about rooting my phone to install a custom rom because the latest htc update made my phone so horrible. but now anything changed cause this just happened:
i got an sms (using the preinstalled sms app) and answered to it. send the phone to "sleep" (?) by pressing power button once, like always. laying the phone back on the table, continuing playing darksiders2. maybe 5 minutes later the display brightens up by itself like if an incoming call but nothing happens. i grab the phone and try to press anything or swipe to see whats going on, but no input gets recognized. plus the button row doesnt get lighten up like normally. confused i tried to press the power button but even that shows no reaction. it just stayed that way, nothing i could do. because i had one freeze under 2.3.5 or so i took the battery out to do a hard reset. booting up again gets me now into the screen i only read here before: where you have to go to install roms from zips etc. but i have booted normally, without pressing the volume keys. the title row says: locked, security warning. rebooting the phone out of this only gets me back here. i dont get it. i mean i know this version is messed up but what is this? my phone is broken and i havent even tried to unlock or anything else it... my god. i dont know what to do. next week is coming up and i dont have multiple phones.
has anyone any idea? please help!
ps: please forgive me any language flaws, english isnt my mother tongue.

Possible solutions
- Wipe the data from recovery if you can, or from bootloader
- Install the ruu when you had before

What country are you/the phone from?

And give us the output of the command
Fastboot getvar all
Sent from my HTC Incredible S using xda app-developers app

hello, thank you for your replies!
i bought the phone over amazon.de and i'm from germany.
where do i have to write "Fastboot getvar all"? do i need to install something and connect the phone to usb or anything like that? i mean i read about some incS roms on the forums but never tried anything myself so i have to look into that first on how to set things up..
edit: so i finally managed to setup android sdk adb and get this command running. yay!
C:\Windows\system32>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.02.0002
(bootloader) version-baseband: 3831.18.00.11_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.10.405.1
(bootloader) serialno: XXXX
(bootloader) imei: XXXX
(bootloader) product: vivo
(bootloader) platform: HBOOT-7630
(bootloader) modelid: PG3213000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4069mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: d41e50e7
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.030s
Click to expand...
Click to collapse

I think your best option is to just run the ruu http://d-h.st/7UC

ok i have a question: im downloading the exe right now. is this an extracting archive and do i have to do anything with it or is it a real exe and a like precompiled autorun thing? btw what am i downloading here? is this the latest unmodified original htc system for my phone?
and yeah: how do i need to apply it?

benutzer001 said:
ok i have a question: im downloading the exe right now. is this an extracting archive and do i have to do anything with it or is it a real exe and a like precompiled autorun thing? btw what am i downloading here? is this the latest unmodified original htc system for my phone?
and yeah: how do i need to apply it?
Click to expand...
Click to collapse
It is an executable program. Just run it on a Windows PC and follow the instructions.

ouch. so everything will be gone? i mean a have the sd and sim out but okay..
btw: i just dont get what this is. have you any clue on what happened here and/or why? this just makes no sense to me. how can it corrupt itself?

benutzer001 said:
ouch. so everything will be gone? i mean a have the sd and sim out but okay..
btw: i just dont get what this is. have you any clue on what happened here and/or why? this just makes no sense to me. how can it corrupt itself?
Click to expand...
Click to collapse
I don't know why this happen but yes everything will be gone.

i doesnt work.. great..
program runs, checks version, newest version and version on phone are the same, i click okay patch anyway, phone reboots and progress bar shows up on pc. phone boots right to the locked-security warning menu and the pc bar gets stuck at waiting for bootloader. stays there 2 minutes and then aborts patching.

benutzer001 said:
i doesnt work.. great..
program runs, checks version, newest version and version on phone are the same, i click okay patch anyway, phone reboots and progress bar shows up on pc. phone boots right to the locked-security warning menu and the pc bar gets stuck at waiting for bootloader. stays there 2 minutes and then aborts patching.
Click to expand...
Click to collapse
Try it again.

error 171 usb connection error
edit: i found that the fastboot var gives an answer if the phone is connected but (as of my understanding) a basic command like adb devices shows up nothing. is says showing list of devices but the space stays blank. but the fastboot command gets an answer so there must be some sort of communication between phone and pc..

benutzer001 said:
error 171 usb connection error
edit: i found that the fastboot var gives an answer if the phone is connected but (as of my understanding) a basic command like adb devices shows up nothing. is says showing list of devices but the space stays blank. but the fastboot command gets an answer so there must be some sort of communication between phone and pc..
Click to expand...
Click to collapse
Do you have the HTC Sync app installed on your PC? If so, make sure it is not running in the System Tray or remove it all together and try again.
If you don't have HTC Sync installed, then install it to get the current drivers and then you can uninstall it and try it again.

which parts do i uninstall after installing the sync package? i have the following:
htc sync
htc driver installer
htc bmp usb driver
do i just need to uninstall htc sync and keep the rest or uninstall everything?
edit: i only uninstalled htc sync keeping the rest. same error.

benutzer001 said:
which parts do i uninstall after installing the sync package? i have the following:
htc sync
htc driver installer
htc bmp usb driver
do i just need to uninstall htc sync and keep the rest or uninstall everything?
edit: i only uninstalled htc sync keeping the rest. same error.
Click to expand...
Click to collapse
You can extract the Rom.zip file that the ruu is using and update manually.
Start the ruu software and stay on the first screen.
In your Start>Search programs and files box type %temp% and press enter. A temp window should appear.
search for rom.zip in that window and copy this file to your fastboot dir.
Now you have 2 options. Flash through fastboot
Code:
fastboot oem rebootRUU
fastboot flash zip rom.zip
or rename rom.zip to PG32IMG.zip, copy to your sdcard root, reboot bootloader(hboot mode) and let the bootloader detect the zip and install.

Nonverbose said:
and copy this file to your fastboot dir.
Click to expand...
Click to collapse
where is my fastboot dir? for the adb commands i've setup an android-sdk-windows folder in C: but nothing else.
just running the "fastboot oem rebootRUU" command from somewhere gets me this:
C:\Users\XXXX>fastboot oem rebootRUU
...
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(730): error 2
OKAY [ 0.052s]
finished. total time: 0.055s
Click to expand...
Click to collapse
i am doing all this with my bare phone, no sd and sim card inserted. is it necessary to backup my sd card and insert it?!
and does everything needs to be done in an elevated cmd?

Looks like hardware failure. Try the PG32IMG.zip method but I don't like your chances. From what I see, you did everything right.

so you think it just died? when i try to send the rom.zip in an not elevated cmd over usb it sends correctly, then tries to apply it but aborts with an error saying smth. like flashing over remote is not allowed.
funny thing is that i dont have any other access to my microsd (32gig btw) other than my phone. and right now i cant access it or is there a cmd way? i dont think so because the phone os would be needed to unmount the sd card so that windows can access it, right?

benutzer001 said:
so you think it just died? when i try to send the rom.zip in an not elevated cmd over usb it sends correctly, then tries to apply it but aborts with an error saying smth. like flashing over remote is not allowed.
funny thing is that i dont have any other access to my microsd (32gig btw) other than my phone. and right now i cant access it or is there a cmd way? i dont think so because the phone os would be needed to unmount the sd card so that windows can access it, right?
Click to expand...
Click to collapse
I think you have fried emmc chip. Some batches of incS are notorious for it. It commonly occurs by powering down by removing the battery, but It's possible that it just died.
If you have another sdcard, I would try that before giving up hope. You should be able to copy the pg32img.zip by entering hboot USB mode.
edit: I had look back at your previous posts and noticed you didn't have sdcard inserted. It should be installed in the phone.

Help in unlocking Locked device state

Dear All,
This question may have been asked zillion times but may be I am not intelligent enough to understand those answers. Today morning, suddenly my OP3T switched off. On restarting it shows Chinese or Japanese characters with WLAN in between.
I don't want to lose data at any cost because it contains my entire 2 years work. I am sorry but I hadn't taken backup of phone. Since morning have been trying various things. It doesn't go into recovery. It goes into Fastboot menu. From there only came to know about Locked status. Tried Minimal ADB and Fastboot.
Ran commands
Fastboot oem unlock: Failed (OEM unlock is not allowed)
Fastboot oem device-info
Device tempered: false
Device unlocked: false
Device critical unlocked: false
Charger screen enabled: false
Display Panel:
Have console: false
Selinux type: <none>
Boot_mode: Normal
Kmemleak_detect: false
force_training: false
Fastboot oem boot_mode normal: Failed
Fastboot oem boot_mode wlan: Failed
Please help me

what version of OS do you have?? what was the last update ....4.X.X or 5.X.X

If you can see you phone's internal storage from you PC, then you can copy it across.
If not, then use ADB to backup your data. You'll have to search how to do this.
Sent from my OnePlus3T using XDA Labs

If you have ADB you could try "adb pull /sdcard0/" or similar typical storage locations for internal storage.
I've read somewhere that file creation time and things like that can be reset when you pull files, but I cannot confirm.
You should look into adb commands, if that's the only thing you have access to!

shahabkhan99 said:
what version of OS do you have?? what was the last update ....4.X.X or 5.X.X
Click to expand...
Click to collapse
I am not sure of that. It was 3 weeks back

Virral said:
I am not sure of that. It was 3 weeks back
Click to expand...
Click to collapse
as @Csöndi say you have to do the backup.... if you have 4.1.2 and below you can run some commands to change the boot
if not ... you canot fix by commands
aw ... go to fastboot > conect your mobile via usb (make sure driver is there)
open cmd from adb folder & run this : fastboot oem disable_dm_verity
then see wat you get... fail or okay??

shahabkhan99 said:
as @Csöndi say you have to do the backup.... if you have 4.1.2 and below you can run some commands to change the boot
if not ... you canot fix by commands
aw ... go to fastboot > conect your mobile via usb (make sure driver is there)
open cmd from adb folder & run this : fastboot oem disable_dm_verity
then see wat you get... fail or okay??
Click to expand...
Click to collapse
It shows failed.
Tried various things. Attached are the photos of the issue.
The phone shows in device manager but internal memory still not detected.

i think you have to go for Mega brick guide.... but keep in mind there is different method to fix.... so go with without wiping data