Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,770,105 Members 52,315 Now Online
XDA Developers Android and Mobile Development Forum

[Q] black screen no boot animation yet fastboot still works?

Tip us?
 
micemicerabies
Old
#1  
micemicerabies's Avatar
Junior Member - OP
Thanks Meter 2
Posts: 11
Join Date: Feb 2011
Location: peekskill
Unhappy [Q] black screen no boot animation yet fastboot still works?

I have a Nexus 7 LTE tablet, I recently did a Paranoid android update and everything went smooth. I performed my nandroid backup as I normally would. At some point during the day, my screen went black. I tried rebooting the tablet, but the screen was still black. The device appears to boot fine. I have no boot screen, I cannot enter TWRP or any other boot loader. The notification indicator light blinks and I was able to access the device via adb.

I decided to flash the default nexus 7 firmware using the official google files - 4.4.2 (KOT49H) assuming this would work as per the directions I read in similar threads.

My issue continunes. I still have a black screen. I can no longer access ADB. Fastboot on the other hand works just fine.

Here is the output of my last flash attempt.
Code:
./flash-all.sh 
sending 'bootloader' (3911 KB)...
OKAY [  0.129s]
writing 'bootloader'...
OKAY [  1.355s]
finished. total time: 1.484s
rebooting into bootloader...
OKAY [  0.007s]
finished. total time: 0.007s
sending 'radio' (76038 KB)...
OKAY [  2.388s]
writing 'radio'...
OKAY [  2.995s]
finished. total time: 5.383s
rebooting into bootloader...
OKAY [  0.007s]
finished. total time: 0.007s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-04.02
Baseband Version.....: DEB-Z00_2.42.0_1204
Serial Number........: 0*******
--------------------------------------------
checking product...
OKAY [  0.003s]
checking version-bootloader...
OKAY [  0.004s]
checking version-baseband...
OKAY [  0.004s]
sending 'boot' (7018 KB)...
OKAY [  0.268s]
writing 'boot'...
OKAY [  0.348s]
sending 'recovery' (7566 KB)...
OKAY [  0.283s]
writing 'recovery'...
OKAY [  0.290s]
erasing 'system'...
OKAY [  1.296s]
sending 'system' (730592 KB)...
OKAY [ 24.929s]
writing 'system'...
OKAY [ 32.060s]
erasing 'userdata'...
OKAY [ 25.211s]
formatting 'userdata' partition...
Creating filesystem with parameters:
    Size: 28856791040
    Block size: 4096
    Blocks per group: 32768
    Inodes per group: 8192
    Inode size: 256
    Journal blocks: 32768
    Label: 
    Blocks: 7045115
    Block groups: 215
    Reserved block group size: 1024
Created filesystem with 11/1761280 inodes and 154578/7045115 blocks
sending 'userdata' (139085 KB)...
writing 'userdata'...
OKAY [ 12.329s]
erasing 'cache'...
OKAY [  0.445s]
formatting 'cache' partition...
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)...
writing 'cache'...
OKAY [  0.874s]
rebooting...

finished. total time: 98.361s

Even after a clean flash I still get a black screen and only fastboot is accessible.

What can I do to get rid of this black screen and get my tablet back in working condition?

Any help is appreciated.
 
0wangj4
Old
#2  
Junior Member
Thanks Meter 0
Posts: 23
Join Date: Jul 2009
I have the same issue, but I am stuck on google boot loop. I have tried going back to old factory roms, but still no good.

Have you tried using old factory roms? And were you able to go to recovery from bootloader? I can't even flashing stock recovery.
 
micemicerabies
Old
#3  
micemicerabies's Avatar
Junior Member - OP
Thanks Meter 2
Posts: 11
Join Date: Feb 2011
Location: peekskill
Quote:
Originally Posted by 0wangj4 View Post
Have you tried using old factory roms? And were you able to go to recovery from bootloader? I can't even flashing stock recovery.
I have no bootloader available as the screen is black. I can only access fastboot. I tried flashing the original google supplied firmware as well with no luck.
 
LinearEquation
Old
(Last edited by LinearEquation; 30th May 2014 at 08:17 PM.)
#4  
LinearEquation's Avatar
Senior Member
Thanks Meter 403
Posts: 1,687
Join Date: Aug 2013
Location: Midwest

 
DONATE TO ME
Quote:
Originally Posted by micemicerabies View Post
I have no bootloader available as the screen is black. I can only access fastboot. I tried flashing the original google supplied firmware as well with no luck.
As I look at the script it looks like that was a very fast flash. Did you check the MD5 to make sure the file was not corrupted? Because it does not even look like anything flashed.

Edit: At best, maybe, the system flashed but boot and recovery were done in a couple seconds. I'd check the MD5 or reflash the images.

Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
[ROOT] 2013 KFHD7 Soho firmware 11.x.x.x (no camera)
http://forum.xda-developers.com/show...44736&page=101 If needed contact @GranPC for an updated Firerooter.
[Root] 2012 KFHD7 Tate http://forum.xda-developers.com/show....php?t=1886460
2nd [Bootloader]/[TWRP] KFHD7 Tate
http://forum.xda-developers.com/show....php?t=2128848
http://forum.xda-developers.com/show....php?t=2271909
KFHD7 Tate System Restore Tool http://forum.xda-developers.com/show....php?t=1951254
 
micemicerabies
Old
(Last edited by micemicerabies; 3rd June 2014 at 02:40 AM.)
#5  
micemicerabies's Avatar
Junior Member - OP
Thanks Meter 2
Posts: 11
Join Date: Feb 2011
Location: peekskill
Quote:
Originally Posted by LinearEquation View Post
As I look at the script it looks like that was a very fast flash. Did you check the MD5 to make sure the file was not corrupted? Because it does not even look like anything flashed.

Edit: At best, maybe, the system flashed but boot and recovery were done in a couple seconds. I'd check the MD5 or reflash the images
Code:
root@box:/root/# md5sum razorg-kot49h-factory-49789b24.tgz && sha1sum razorg-kot49h-factory-49789b24.tgz 
8e42ffe324a9109031dd4f9dd53fdc9a  razorg-kot49h-factory-49789b24.tgz
49789b240cab9a8e91c1f5a3eb0b6be0b07b5732  razorg-kot49h-factory-49789b24.tgz
Correctly hashes against
MD5SUM = 8e42ffe324a9109031dd4f9dd53fdc9a
SHA1SUM = 49789b240cab9a8e91c1f5a3eb0b6be0b07b5732
For the 4.4.2 (KOT49H) Image (NOTE: The original flash that I showed the output for was for the later image 4.4.2_r2 (Verizon) (KVT49L)) In the past I have had more success with the KOT49H image and will continue testing using this image.

Here is the latest attempt at flashing using the flash-all.sh script
Code:
root@box:/root/razorg-kot49h-factory-49789b24/razorg-kot49h# ./flash-all.sh 
sending 'bootloader' (3911 KB)...
OKAY [  0.244s]
writing 'bootloader'...
OKAY [  1.383s]
finished. total time: 1.627s
rebooting into bootloader...
OKAY [  0.006s]
finished. total time: 0.006s
sending 'radio' (43830 KB)...
OKAY [  2.666s]
writing 'radio'...
OKAY [  1.748s]
finished. total time: 4.415s
rebooting into bootloader...
OKAY [  0.005s]
finished. total time: 0.006s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-04.02
Baseband Version.....: DEB-G00_2.37.0_1024
Serial Number........: 0*******
--------------------------------------------
checking product...
OKAY [  0.003s]
checking version-bootloader...
OKAY [  0.004s]
checking version-baseband...
OKAY [  0.004s]
sending 'boot' (7018 KB)...
OKAY [  0.424s]
writing 'boot'...
OKAY [  0.369s]
sending 'recovery' (7566 KB)...
OKAY [  0.456s]
writing 'recovery'...
OKAY [  0.281s]
erasing 'system'...
OKAY [  1.304s]
sending 'system' (721408 KB)...
OKAY [ 43.544s]
writing 'system'...
OKAY [ 30.515s]
erasing 'userdata'...
OKAY [ 22.401s]
formatting 'userdata' partition...
Creating filesystem with parameters:
    Size: 28856791040
    Block size: 4096
    Blocks per group: 32768
    Inodes per group: 8192
    Inode size: 256
    Journal blocks: 32768
    Label: 
    Blocks: 7045115
    Block groups: 215
    Reserved block group size: 1024
Created filesystem with 11/1761280 inodes and 154578/7045115 blocks
sending 'userdata' (139085 KB)...
writing 'userdata'...
OKAY [ 14.458s]
erasing 'cache'...
OKAY [  0.484s]
formatting 'cache' partition...
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)...
writing 'cache'...
OKAY [  1.179s]
rebooting...

finished. total time: 115.443s
I agree that these write speeds seem a little too quick

Sidenote: Before I tried this last flash I was able to confirm that the digitizer is functional. The devices appeared to boot into the factory image (screen was still black) I was some how able to get the accessibility options enabled so that the devices would speak out my actions. I did not complete this tutorial. This leads me to believe there is some more bizarre underlying screen issue. Possibly a loose cable?
 
micemicerabies
Old
#6  
micemicerabies's Avatar
Junior Member - OP
Thanks Meter 2
Posts: 11
Join Date: Feb 2011
Location: peekskill
Hopefully something here can help.

Code:
fastboot getvar all
(bootloader)  version-bootloader: FLO-04.02
(bootloader)  version-baseband: DEB-G00_2.25.1_0802
(bootloader)  version-hardware: rev_e
(bootloader)  version-cdma: N/A
(bootloader)  variant: deb 32G
(bootloader)  serialno: 0*******
(bootloader)  product: deb
(bootloader)  secure_boot: enabled
(bootloader)  lock_state: unlocked
(bootloader)  project: deb
(bootloader)  off-mode-charge: yes
(bootloader)  uart-on: no
(bootloader)  partition-type:bootloader: emmc
(bootloader)  partition-size:bootloader: 0x0000000000aee000
(bootloader)  partition-type:recovery: emmc
(bootloader)  partition-size:recovery: 0x0000000000a00000
(bootloader)  partition-type:boot: emmc
(bootloader)  partition-size:boot: 0x0000000001000000
(bootloader)  partition-type:system: ext4
(bootloader)  partition-size:system: 0x0000000034800000
(bootloader)  partition-type:cache: ext4
(bootloader)  partition-size:cache: 0x0000000023000000
(bootloader)  partition-type:userdata: ext4
(bootloader)  partition-size:userdata: 0x00000006b7ffbe00
all: 
finished. total time: 0.026s
 
micemicerabies
Old
#7  
micemicerabies's Avatar
Junior Member - OP
Thanks Meter 2
Posts: 11
Join Date: Feb 2011
Location: peekskill
Thumbs up Asus RMA was not horrible

I want to close out this thread with some answers about my experience.

I requested an RMA from Asus and sent my device to get checked out or repaired by them. I was fearful that they would notice that I had tampered with the device. I removed the backing to check the battery, unlocking the bootloader and flashing 3rd party ROMs etc.

I ended up re-locking the bootloader since I had fastboot access and tested my luck. I bubble wrapped the devices as Asus said they do not supply padding or any packing material for return of the product.

I was able to check the RMA status page and saw that my tablet arrived in TX at the repair site. They did not update the status page for 3 days with no indication of what caused the issue. Finally the status was changed from < Received > to < Repair Complete >. I had to contact support as they did not supply me with a tracking number. They gave me the tracking details and I got my tablet back yesterday. Asus did not use any of my bubble wrap and the tablet was free floating in a barely reinforced cardboard box.

No explanation was given as to the cause of the failure, I got back the exact same back cover as well as the screen. So either they changed some internal part or flashed some part of the device that I am unaware of.

Anyone else who has a similar issue and needs to get an RMA I would recommend the following.
1. If you still have access to fastboot relock the bootloader. You can check using
Code:
fastboot getvar all
1. Take photos of the device and all physical imperfections so you have some recourse if someone breaks the screen

2. Bubble wrap the device tightly to ensure no damage occurs on the way to the repair site.

3. Tracking & Insurance is a must. If you can prove the screen broke due to USPS or whoever then at least you can get a new tablet with the insurance money. Don't cheap out, get the $250 or $350 worth. The whole cost of shipping should be less than $10 and is worth the piece of mind.

Finally I just updated my tablet to 4.4.3 as it was returned with 4.4.2. Here is what a successful flash looks like, as well as how long each part takes to flash. Compared to the previous flash times one can see the difference.

Code:
root@box:/Android/razorg-ktu84l-factory-9f9b9ef2/razorg-ktu84l# ./flash-all.sh 
sending 'bootloader' (3911 KB)...
OKAY [  0.227s]
writing 'bootloader'...
OKAY [  1.285s]
finished. total time: 1.512s
rebooting into bootloader...
OKAY [  0.006s]
finished. total time: 0.006s
sending 'radio' (76038 KB)...
OKAY [  4.231s]
writing 'radio'...
OKAY [  2.986s]
finished. total time: 7.217s
rebooting into bootloader...
OKAY [  0.006s]
finished. total time: 0.006s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-04.02
Baseband Version.....: DEB-Z00_2.42.0_1204
Serial Number........: 0*******
--------------------------------------------
checking product...
OKAY [  0.003s]
checking version-bootloader...
OKAY [  0.004s]
checking version-baseband...
OKAY [  0.004s]
sending 'boot' (7050 KB)...
OKAY [  0.408s]
writing 'boot'...
OKAY [  0.335s]
sending 'recovery' (7600 KB)...
OKAY [  0.432s]
writing 'recovery'...
OKAY [  0.290s]
erasing 'system'...
OKAY [  1.297s]
sending 'system' (740284 KB)...
OKAY [ 42.003s]
writing 'system'...
OKAY [ 32.278s]
erasing 'userdata'...
OKAY [ 21.615s]
formatting 'userdata' partition...
Creating filesystem with parameters:
    Size: 28856791040
    Block size: 4096
    Blocks per group: 32768
    Inodes per group: 8192
    Inode size: 256
    Journal blocks: 32768
    Label: 
    Blocks: 7045115
    Block groups: 215
    Reserved block group size: 1024
Created filesystem with 11/1761280 inodes and 154578/7045115 blocks
sending 'userdata' (139085 KB)...
writing 'userdata'...
OKAY [ 13.308s]
erasing 'cache'...
OKAY [  0.368s]
formatting 'cache' partition...
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)...
writing 'cache'...
OKAY [  1.145s]
rebooting...

finished. total time: 113.509s
My overall experience with the RMA process was great I did not have any of the nightmare problems that I read about on other forums.

Good luck to anyone going through this headache.
The Following User Says Thank You to micemicerabies For This Useful Post: [ Click to Expand ]
 
mdamaged
Old
#8  
mdamaged's Avatar
Senior Member
Thanks Meter 905
Posts: 1,447
Join Date: Oct 2013
Location: South of Heaven

 
DONATE TO ME
 
Quote:
Originally Posted by micemicerabies View Post
I want to close out this thread with some answers about my experience.

I requested an RMA from Asus and sent my device to get checked out or repaired by them. I was fearful that they would notice that I had tampered with the device. I removed the backing to check the battery, unlocking the bootloader and flashing 3rd party ROMs etc.

I ended up re-locking the bootloader since I had fastboot access and tested my luck. I bubble wrapped the devices as Asus said they do not supply padding or any packing material for return of the product.

I was able to check the RMA status page and saw that my tablet arrived in TX at the repair site. They did not update the status page for 3 days with no indication of what caused the issue. Finally the status was changed from < Received > to < Repair Complete >. I had to contact support as they did not supply me with a tracking number. They gave me the tracking details and I got my tablet back yesterday. Asus did not use any of my bubble wrap and the tablet was free floating in a barely reinforced cardboard box.

No explanation was given as to the cause of the failure, I got back the exact same back cover as well as the screen. So either they changed some internal part or flashed some part of the device that I am unaware of.

Anyone else who has a similar issue and needs to get an RMA I would recommend the following.
1. If you still have access to fastboot relock the bootloader. You can check using
Code:
fastboot getvar all
1. Take photos of the device and all physical imperfections so you have some recourse if someone breaks the screen

2. Bubble wrap the device tightly to ensure no damage occurs on the way to the repair site.

3. Tracking & Insurance is a must. If you can prove the screen broke due to USPS or whoever then at least you can get a new tablet with the insurance money. Don't cheap out, get the $250 or $350 worth. The whole cost of shipping should be less than $10 and is worth the piece of mind.

Finally I just updated my tablet to 4.4.3 as it was returned with 4.4.2. Here is what a successful flash looks like, as well as how long each part takes to flash. Compared to the previous flash times one can see the difference.

Code:
root@box:/Android/razorg-ktu84l-factory-9f9b9ef2/razorg-ktu84l# ./flash-all.sh 
sending 'bootloader' (3911 KB)...
OKAY [  0.227s]
writing 'bootloader'...
OKAY [  1.285s]
finished. total time: 1.512s
rebooting into bootloader...
OKAY [  0.006s]
finished. total time: 0.006s
sending 'radio' (76038 KB)...
OKAY [  4.231s]
writing 'radio'...
OKAY [  2.986s]
finished. total time: 7.217s
rebooting into bootloader...
OKAY [  0.006s]
finished. total time: 0.006s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-04.02
Baseband Version.....: DEB-Z00_2.42.0_1204
Serial Number........: 0*******
--------------------------------------------
checking product...
OKAY [  0.003s]
checking version-bootloader...
OKAY [  0.004s]
checking version-baseband...
OKAY [  0.004s]
sending 'boot' (7050 KB)...
OKAY [  0.408s]
writing 'boot'...
OKAY [  0.335s]
sending 'recovery' (7600 KB)...
OKAY [  0.432s]
writing 'recovery'...
OKAY [  0.290s]
erasing 'system'...
OKAY [  1.297s]
sending 'system' (740284 KB)...
OKAY [ 42.003s]
writing 'system'...
OKAY [ 32.278s]
erasing 'userdata'...
OKAY [ 21.615s]
formatting 'userdata' partition...
Creating filesystem with parameters:
    Size: 28856791040
    Block size: 4096
    Blocks per group: 32768
    Inodes per group: 8192
    Inode size: 256
    Journal blocks: 32768
    Label: 
    Blocks: 7045115
    Block groups: 215
    Reserved block group size: 1024
Created filesystem with 11/1761280 inodes and 154578/7045115 blocks
sending 'userdata' (139085 KB)...
writing 'userdata'...
OKAY [ 13.308s]
erasing 'cache'...
OKAY [  0.368s]
formatting 'cache' partition...
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)...
writing 'cache'...
OKAY [  1.145s]
rebooting...

finished. total time: 113.509s
My overall experience with the RMA process was great I did not have any of the nightmare problems that I read about on other forums.

Good luck to anyone going through this headache.


Thanks for taking the time to update!
Kenneth, what is the frequency? Set a fire for a man, and he will stay warm for a night. Set a man on fire, and he will stay warm for the rest of his life.
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Android App Review: Hide Your Files with Androignito – XDA Developer TV

Stop right now, look at your phone, and see how many pictures, … more

BrightNotes Makes Cloud Notes Simple and Easy

There are literally thousands of note taking apps available on Android, with practically every … more

Google Glass XE20.1 Update Brings Improved Contacts, Head Nudge, New Cards and Commands

Ever since Google unveiled Android Wear earlier this … more

Remote Control Your Android Device with Monitordroid

The Android OS showsgreat potential in many areas. One of most interesting things that … more