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
Hi everybody. I wanted to flash this ROM - Kisja_SUN_Y_1_1_WM_6_1_TF3D_2_5_WWE. After some wrong passes , I had in my hands a phone in boot mode(stripescreened) and also with hardSPL 1.4 from OliNex..But with this hSPL, my flashing always stopped on 0%. Then I chaged some hSPL's, but after I put this one (RUU_Signed_SPL193stock.zip from post http://forum.xda-developers.com/showpost.php?p=2324837&postcount=20) I can't neither change hSPL nor flash the ROM(both stops at 0%, and I tried very much of rom's and SPL's).
Olny when I try to flash the official one, it stops at 1%, terminates and tells that ERROR [294] - INVALID VENDOR ID (and then restarts and white screen appears).I tried a lot of originals, but the same result. Neither ActiveSync nor Explorer doesn't observe my phone(only MTTS or ROMUpdateUtility.exe)
DIAM100 64M
SPL-1.93.0000
MicroP-Diam (LED) v11
MTTY 1.42 :
Cmd>task 2a
Format ALL start
backup SPL OK
backup MISC configuration OK
SPL start start block=288, total block of CE=1760
Write 0xFF start page=0x4800, total page=0x1B800
restore SPL OK
restore MISC configuratoin OK
restore MFG configuratoin OK
Format ALL end
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
OS NOT FOUND !!!
Cmd>task 28
Format start
Fill RSVD information for block 288 to 321
TAG NOT FOUND !!! NOT CLEAR STORAGE !!!
Format end
Cmd>info 2
HTCSH3G__402’1plHTCE
P.S. - Sorry for my bad English.
Hi,
Read this thread here: HERE
it is my thread on MTTY, in the thread you can find solution for everything.
Post your problem in that thread and i will ask a mod to close this as i willl fix it in the proper thread!!
@MODS: Please Close this thread, I will fix in the MTTY thread posted above. Thanks
MG
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
Device : Nexus 5X
I am registered with Google beta program and have installed Andriod 7.0 OTA update this morning. After a few hours of usage, the phone by itself booted and stuck at google dots animation logo. I don't know why it happened and trying to figure out a solution since a few hours.
Here is what I have and What I did so far..
1. Bootloader is LOCKED and both usb debugging and oem unlock check box in developer options are NOT enabled. I can't boot the phone, so there is no way to enable them now.
2. I have tried using fastboot the following commands 'fastboot oem unlock' ; 'flashboot flashing unlock' ; fastboot format cache' with the following results.
fastboot oem unlock and fastboot flashing unlock : FAILED <remote: oem unlock is not allowed>
fastboot format cache :
Creating filesystem with parameters:
Size: 100663296
Block size: 4096
Blocks per group: 32768
Inodes per group: 6144
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 24576
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/6144 inodes and 1422/24576 blocks
target reported max download size of 536870912 bytes
erasing 'cache'...
FAILED (remote: device is locked. Cannot erase)
finished. total time: 0.016s
3. With no good solution, I started looking for adb sideload options.
So I downloaded the recovery rom to adb sideload of this version 6.0.1 (MTC20F) from the website which is the latest release. ANY OTHER older versions are giving error saying Device requires bootloader-bullhead-bhz11e version and rom has a different version bootloader. So it failed to load any other previous rom releases.
Result : It did not work. It successfully installed, both in cmd promt and adb's Apply update from ADB' mode, I get no errors and installs successfully. On booting the phone, It is stuck on same google dots animation logo and phone heats up like insane. I left it there few hours since it takes more time for first booting with much patience and hope but its no good.
4. As some of the forum's advised, I have installed Nexus Toolkit ( which I although hate using). In the toolkit, Unlock bootloader would for some reason reboot my phone as soon as I click it and shows this message "Waiting for devices".
I have explained what I done now. I have pretty much run out my ideas and need you guys help.
The core problem that would solve this is to unlock the device which requires access to Developer's options which the phone won't boot. I only have access to TWRP for now.