I have my trinity briked and want to bring it to service centre. But ROM version I tried to flash before briking was in different region which may breach the warranty.
Now it boots and stops with a start up logo in different language. I am worried that service centre may refuse my repair request. Can I erase the image file from ROM? or any suggestion to avoid showing this screen? It is possible to use mtty and erase the image file? where is the image files' address? or how to erase the main ROM so that it will not show the image?
I tried most of the recovery method from here http://forum.xda-developers.com/showthread.php?t=286755 but still failed. My case is "Hybrid Bricks: combinations of both type 1 and type 2 bricks"
Model: D810 (trinity)
ROM Before Flash: 1.??
Radio Before Flash: 1.07??
Bootloader Before Flash: 1.07.??
Flash failed at: It seems completed at 100% but cannot boot after finish all
Flashing ROM: 1.23
Flashing Radio: 1.13.00
Bootloader After Failure: 1.07.0000
tried unlock and using SSPL to flash
CID Before Failure Super CID: tried unlock but don't know if success
CID Corrupt: Yes, info 2 shows HTCSF ?? HTCE
Radio Corrupt: Yes
No GSM Error: Yes
Stuck In Bootloader: No
Stuck On Windows Mobile Splash: Yes
Can boot into OS: No
Tried mtty command set 14 0: Yes
Tried wiki problem number 5: Yes
mtty info 2 output: CID: HTCSF ?? HTCE
Current Device Status: hang at welcome screen when power on
Hi Gurus and friends,
I have a problem, my Uni is semi bricked i think, I can only get to bootloader mode after several tries. I tried the MTTY program to format the Uni so that I can install a original WM5 ROM. But my ROM update stops after updating the Radio ROM and doesn't proceed after that.
Below is that command that I used and the reply that I get from MTTY.
Do help.
USB>
USB>task 32
Level = FF
USB>task 28 55aa
Wait..
status=60
DOC_ReadFAT0 fail: Start=3FA0000,Len=200
Read data error in tag
DOC_format failed!
USB>
anyone???
Hi anyone?????chx
Do help ya all.
TQ again,
te
It sounds like there may be some physical corruption to the NAND.
DOCInfoTableinitHW+
Binary0 Size: 0x100000
FAT0 Size: 0x4000000
FAT1 Size: 0xA00000
FAT2 Size: 0x2C70000
All Size: 0x7770000
FAT0_ADDR=0x100000,FAT1_ADDR=0x4100000,FAT2_ADDR=0x4B00000
That's a log from a Universal with nothing physically wrong with the NAND (IIRC, it's been a while).
Can you give a little more info on the problems 'before' you got into this state. Did you loose the radio and get the usual Error 114/144 messages when you tried to just install a radio ROM?
I really don't know too much about this stuff but when I was using mtty to back up my rom using the directions from buzzdev.net I was having problems because my sim and cid or what-not was locked. Apparently this could be seen from the "Level = FF" line. Read the following link and hopefully this helps... http://buzzdev.net/read.php?40,33157,35149#msg-35149
SORRY GUYS...ITS WORKING PROPERLY..WAS OVER LOOKING A SIMPLE STEP..
THANK U GUYS..
Hey guys,
I was trying to install custom ROM on my Diamond and now, all i am seeing the standard Touch Diamond black screen and nothing beyond that.
Here are the steps which i followed:
1. Downloaded HARD SPL from http://forum.xda-developers.com/showthread.php?t=416211 and ran ROMUpdateUtility.exe on the phone. It was successfull
2. Then downloaded custom Radio 1.09.25.23 and installed on the phone jst as the previous step. Even that was successful.
3. Downloaded MTTY from http://forum.xda-developers.com/showthread.php?t=540290 and tried flashing from USB (post #4).
3.1 in the bootloader, selected USB and left every other configuration like original.
3.2 in the cmd :
--------------------------
Cmd>set 14 0
HTCST ÚÈÒHTCE
--------------------------
then,
--------------------------
Cmd>task 29
Format BINFS start
Fill RSVD information for block 288 to 321
CE start sector=0x14, total sector of CE and TFAT=0x14
CE start start block=321, total block=1727
ERASE block 75 FAIL !!!
ERASE block 123 FAIL !!!
ERASE block 138 FAIL !!!
ERASE block 1075 FAIL !!!
ERASE block 1667 FAIL !!!
Write 0xFF start page=0x5040, total page=0x1AFC0
Format BINFS end
------------------------------
then,
---------------------
Cmd>task 8
Cmd>
---------------------
disconencted my device and held the vol down key and was navigated to the bootloader screen with USB connection.
4. dowloaded 'Energy' ROM from http://forum.xda-developers.com/showthread.php?t=517300
and then tried running it.. but then the custom RUU says that cant connect.
Now i am really worried..did i brick my cell? is there any way to come out of this??
Loads of thanks in advance..
Dear all,
This is my first message on this forum, so thank you for letting me join. I hope we can fix my current problem.
Quickly, about the context, I got a Nexus 7 2013 LTE from a colleague who kinda bricked it. Apparently, he has been investigating on it for some time, so I am completely unsure what happened. I'll do my best to provide answers and perform actions but there are some things I do not know, and some other things I might not be able to do.
About the tablet, as aforementioned, it is a Nexus 7 2013 LTE from Asus/Google, and my friend told me it is 2nd generation.
The tablet cannot boot at all, only got the white Google logo, thus I am unsure what is currently installed.
Same with recovery mode unavailable, anyway I can access the fastboot mode (volume down + power) where I could get the following information :
Code:
Product name : deb
Variant : deb 32G
HW version : rev_e
Bootloader version : FLO-04.05
Baseband version : DEB-Z00_2.44.0_0213
Carrier info : None
Serial number : 05ef14bb
Signing : Yes
Secure boot : Enabled
Lock state : Locked
As the OS is not booting, I am figuring out to reinstall the OS from scratch using an Android official image gathered here :
Code:
https://developers.google.com/android/nexus/images#razorg
I downloaded the latest razorg
Question : Can you please confirm that his choice is correct ?
Then I also installed the latest android SDK.
I had a little trouble to get the driver installed, but finally, and when fastbooted, the windows device manager shows :
Code:
Android device
[INDENT]Android Bootloader Interface[/INDENT]
When running fastboot commands, I get the following :
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot devices
05ef14bb fastboot
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) SB=Y
OKAY [ 0.012s]
finished. total time: 0.014s
So my assumption is that so far my setup is correct.
Question : Can you please confirm ?
Now coming back to the procedure to perform the update, we roughly got the following :
- Get the image
- Get the latest android SDK
- Run a fastboot oem unlock to allow the firmware to be updated
- Run the flash-all.bat command which will perform
* Flash of the bootloader
* Flash of the radio
* Update of the OS- Run a fastboot oem lock to prevent any further update.
Right now I am trying to run a fastboot oem unlock.
I get the confirmation screen on the device about removing all personal data.
I can confirm and then the process is starting, or is supposed to start since I get the following output :
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot oem unlock
...
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
Anyway, after several tries, and ultimately around 12 hours letting it work, I need to observe that the device is not yet unlocked.
I also tried a
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
Anyway it stays stuck.
I also tried to format the cache, but due to the fact that the system is still in a locked state, it is not possible.
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot format cache -u
Creating filesystem with parameters:
Size: 587202560
Block size: 4096
Blocks per group: 32768
Inodes per group: 7168
Inode size: 256
Journal blocks: 2240
Label:
Blocks: 143360
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/35840 inodes and 4616/143360 blocks
sending 'cache' (10984 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.011s
So my questions are :
- Was everything done correctly ?
- Have you got any idea on how to make it work ?
I'd like to add that I read numerous posts about those kind of issues, but could not find anything satisfactory.
I read that it might be needed to activate the debug mode, and some unlock within the development menu, anyway and as previously mentioned I do not have access to the OS, so I do not know if those changes are done, and also cannot perform anything.
As mentioned the fastboot is working, about ADB it is not, but I also believe that ADB can only be used while the main OS is started (as opposed with fastboot mode), and development option / debugging option are activated.
Is this assumption correct ?
Thank you for your help in advance.
omaquaire said:
Dear all,
This is my first message on this forum, so thank you for letting me join. I hope we can fix my current problem.
Quickly, about the context, I got a Nexus 7 2013 LTE from a colleague who kinda bricked it. Apparently, he has been investigating on it for some time, so I am completely unsure what happened. I'll do my best to provide answers and perform actions but there are some things I do not know, and some other things I might not be able to do.
About the tablet, as aforementioned, it is a Nexus 7 2013 LTE from Asus/Google, and my friend told me it is 2nd generation.
The tablet cannot boot at all, only got the white Google logo, thus I am unsure what is currently installed.
Same with recovery mode unavailable, anyway I can access the fastboot mode (volume down + power) where I could get the following information :
Code:
Product name : deb
Variant : deb 32G
HW version : rev_e
Bootloader version : FLO-04.05
Baseband version : DEB-Z00_2.44.0_0213
Carrier info : None
Serial number : 05ef14bb
Signing : Yes
Secure boot : Enabled
Lock state : Locked
As the OS is not booting, I am figuring out to reinstall the OS from scratch using an Android official image gathered here :
Code:
https://developers.google.com/android/nexus/images#razorg
I downloaded the latest razorg
Question : Can you please confirm that his choice is correct ?
Then I also installed the latest android SDK.
I had a little trouble to get the driver installed, but finally, and when fastbooted, the windows device manager shows :
Code:
Android device
[INDENT]Android Bootloader Interface[/INDENT]
When running fastboot commands, I get the following :
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot devices
05ef14bb fastboot
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) SB=Y
OKAY [ 0.012s]
finished. total time: 0.014s
So my assumption is that so far my setup is correct.
Question : Can you please confirm ?
Now coming back to the procedure to perform the update, we roughly got the following :
- Get the image
- Get the latest android SDK
- Run a fastboot oem unlock to allow the firmware to be updated
- Run the flash-all.bat command which will perform
* Flash of the bootloader
* Flash of the radio
* Update of the OS- Run a fastboot oem lock to prevent any further update.
Right now I am trying to run a fastboot oem unlock.
I get the confirmation screen on the device about removing all personal data.
I can confirm and then the process is starting, or is supposed to start since I get the following output :
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot oem unlock
...
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
Anyway, after several tries, and ultimately around 12 hours letting it work, I need to observe that the device is not yet unlocked.
I also tried a
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
Anyway it stays stuck.
I also tried to format the cache, but due to the fact that the system is still in a locked state, it is not possible.
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot format cache -u
Creating filesystem with parameters:
Size: 587202560
Block size: 4096
Blocks per group: 32768
Inodes per group: 7168
Inode size: 256
Journal blocks: 2240
Label:
Blocks: 143360
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/35840 inodes and 4616/143360 blocks
sending 'cache' (10984 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.011s
So my questions are :
- Was everything done correctly ?
- Have you got any idea on how to make it work ?
I'd like to add that I read numerous posts about those kind of issues, but could not find anything satisfactory.
I read that it might be needed to activate the debug mode, and some unlock within the development menu, anyway and as previously mentioned I do not have access to the OS, so I do not know if those changes are done, and also cannot perform anything.
As mentioned the fastboot is working, about ADB it is not, but I also believe that ADB can only be used while the main OS is started (as opposed with fastboot mode), and development option / debugging option are activated.
Is this assumption correct ?
Thank you for your help in advance.
Click to expand...
Click to collapse
I believe this issue has been encountered and answered a multitude of times. When it's stuck at erasing and cannot complete, something has gone wrong with the partition (hardware or software-wise) and the only solution I've come across so far is a replacement motherboard.
graphdarnell said:
I believe this issue has been encountered and answered a multitude of times. When it's stuck at erasing and cannot complete, something has gone wrong with the partition (hardware or software-wise) and the only solution I've come across so far is a replacement motherboard.
Click to expand...
Click to collapse
Hello,
I actually roamed a bit through the forums, and though this question has been asked, I could not really find some satisfactory...
So sad that we will have to change the mainboard, anyway I'll advise my friend.
Thank you very much for your reply anyway.
Best regards,
---
Olivier
LK-1.0.0.0000
Radio-01.01_U11440261_56.02.50306G_2_F
OpenDSP-v20.2.6-00452-M8994_0216
OS-1.32.161.15
Software status: Modified
Unlocked
S-ON
Recovery:
TeamWin Recovery Project 3.0.0-0
Good day,
I am German and can not speak much English. I translate everything from Google
So I hope that you with me bischen re consideration have the probably bad translation.
First time as the problem occurred I had "Android_Revolution_HD-One_M9_14.0".
Now the mobile has sat down in the boatloop overnight.
Have it with wipe of "dalvik cache" and "cache" tried. No success, now it does not hang in the bootloop anymore
It boot it dead.
TWRP points to system Patition "Present: yes" "Removable: No" "Size: 0MB" "Used: 0MB" "Free: 0MB" "Backup Size: 0MB"
Property then TWRP "Install" tried Revolution_HD to Install.Da stands then "set_matadata_recursive: some changes faild"
And as always hangs in the boot.
Then I tried the original Rome of Vodafone
(RUU_HIMA_UHL_L50_SENSE70_Vodafone_UK_1.32.161.15_Radio_01.01_U11440261_56.02.50306G_2_F_release_426771_signed_2_4.exe)
To install with Pc.
But the mobile phone makes every boot attempt of the PC a bootloader rebootart. What I gave up after 2 hours.
I then tried with "fastboot oem lock" it to "Relock". That does not work.
The error comes
" C:\adb2>fastboot.exe oem lock
< waiting for any device >
(bootloader) RELOCK device
FAILED (status read failed (Unknown error))
finished. total time: 0.289s "
Hope all the helpful infos have written with pure you can help me.
Best regards Maik