Database Users

Can't Boot Up Stock ROM Out of the BOX

Just received my Nexus 7 today. I tried booting it up right of the box when the google logo came out and then the screen went black. I thought it might only need recharging. so I plugged it in to charge and waited for the battery icon to show that its charging. I tried booting up again after three hours of charging, the google logo came out again and then the brightness of the screen lowers and I can still barely see the logo. The screen blacked out again and the X showed up and I thought it was booting when it disappeared quickly and it blacked out again. I waited for a while and nothing is showing up on the screen. I tried rebooting a million times and the same thing happens every time. I plugged the tablet to my PC and I can open the internal memory when nothing is showing on the screen after boot up. I went into fastboot mode and unlocked the bootloader and rooted the nexus and tried rebooting with the same result. I tried flashing the stock rom twice using the toolkit and again using adb with no luck. I'm trying to flash a custom rom to see if it fixes anything but I can't seem to boot into recovery either. Can someone show me how to flash a custom rom at fastboot by adb without using recovery? I tried searching for a solution but couldn't find anything. Did someone have the same problem?
I'm from Abu Dhabi and unfortunately I won't be able to return it without wasting a fortune on shipping.
Thanks in advance

Blue Reaper said:
Just received my Nexus 7 today. I tried booting it up right of the box when the google logo came out and then the screen went black. I thought it might only need recharging. so I plugged it in to charge and waited for the battery icon to show that its charging. I tried booting up again after three hours of charging, the google logo came out again and then the brightness of the screen lowers and I can still barely see the logo. The screen blacked out again and the X showed up and I thought it was booting when it disappeared quickly and it blacked out again. I waited for a while and nothing is showing up on the screen. I tried rebooting a million times and the same thing happens every time. I plugged the tablet to my PC and I can open the internal memory when nothing is showing on the screen after boot up. I went into fastboot mode and unlocked the bootloader and rooted the nexus and tried rebooting with the same result. I tried flashing the stock rom twice using the toolkit and again using adb with no luck. I'm trying to flash a custom rom to see if it fixes anything but I can't seem to boot into recovery either. Can someone show me how to flash a custom rom at fastboot by adb without using recovery? I tried searching for a solution but couldn't find anything. Did someone have the same problem?
I'm from Abu Dhabi and unfortunately I won't be able to return it without wasting a fortune on shipping.
Thanks in advance
Click to expand...
Click to collapse
I Think what you'll have to do is finding a recovery program like Odin. It seems like there might be something wrong at bootup maybe. I think it is the ROM. You have to find out how to flash the ROM again. If that doesn't work flash a custom ROM like CM10 or something.

Ryan35310 said:
I Think what you'll have to do is finding a recovery program like Odin. It seems like there might be something wrong at bootup maybe. I think it is the ROM. You have to find out how to flash the ROM again. If that doesn't work flash a custom ROM like CM10 or something.
Click to expand...
Click to collapse
Odin? isn't that for samsung.
Try booting your nexus 7 into the bootloader. Turn off device hold Volume UP and Volume DOWN and hold onto the power button.
You should now be in the bootloader.
If you are in bootloader you should be able to flash the stock rom again. Use this toolkit
http://forum.xda-developers.com/showthread.php?t=1809195 Option 9
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Install the correct drivers then install the toolkit as far as I am aware it has a option to restore stock image.
Hope this helps!!!

mulkman said:
Odin? isn't that for samsung.
Try booting your nexus 7 into the bootloader. Turn off device hold Volume UP and Volume DOWN and hold onto the power button.
You should now be in the bootloader.
If you are in bootloader you should be able to flash the stock rom again. Use this toolkit
http://forum.xda-developers.com/showthread.php?t=1809195 Option 9
Install the correct drivers then install the toolkit as far as I am aware it has a option to restore stock image.
Hope this helps!!!
Click to expand...
Click to collapse
Oh Sorry. I have A Galaxy Exhibit so I use Odin. I thought it was throughout Android. Oh well, I hope your solution helps him.

I tried flashing the stock ROM with the toolkit twice and I get the same thing. Anyone knows how to flash a custom ROM without using a recovery image? Thanks!

Blue Reaper said:
I tried flashing the stock ROM with the toolkit twice and I get the same thing. Anyone knows how to flash a custom ROM without using a recovery image? Thanks!
Click to expand...
Click to collapse
flash your roms/kernels in your custom recovery. educate yourself before you brick your device.

Blue Reaper said:
I tried flashing the stock ROM with the toolkit twice and I get the same thing. Anyone knows how to flash a custom ROM without using a recovery image? Thanks!
Click to expand...
Click to collapse
Use option 8 that will unlock your bootloader, root your device and flash custom recovery. Once done you will be able to flash any custom rom easily via Clockworkmod recovery
Hope that helps

simms22 said:
flash your roms/kernels in your custom recovery. educate yourself before you brick your device.
Click to expand...
Click to collapse
If you have read my first post or the title for that matter you would have already known that the device wasn't working OUT OF THE BOX. You would also know that I have already tried flashing a custom recovery without any success. Thanks for your input BTW
mulkman said:
Use option 8 that will unlock your bootloader, root your device and flash custom recovery. Once done you will be able to flash any custom rom easily via Clockworkmod recovery
Hope that helps
Click to expand...
Click to collapse
I have already unlocked my bootloader through mskip's toolkit and have rooted my device through wug's root toolkit because mskip's required me to enable debugging which wasn't possible in my situation. I tried flashing a custom recovery or even booting into one but it just loops and nothing happens.
I was wondering if I could use adb command prompt to flash a custom ROM through the bootloader if someone can give me the commands or a link to thread with instructions (I tried searching but couldn't find anything) Thanks!

Blue Reaper said:
If you have read my first post or the title for that matter you would have already known that the device wasn't working OUT OF THE BOX. You would also know that I have already tried flashing a custom recovery without any success. Thanks for your input BTW
I have already unlocked my bootloader through mskip's toolkit and have rooted my device through wug's root toolkit because mskip's required me to enable debugging which wasn't possible in my situation. I tried flashing a custom recovery or even booting into one but it just loops and nothing happens.
I was wondering if I could use adb command prompt to flash a custom ROM through the bootloader if someone can give me the commands or a link to thread with instructions (I tried searching but couldn't find anything) Thanks!
Click to expand...
Click to collapse
you really shouldnt use the root toolkits, they are more trouble and more confusing than doing it the right way. in a nutshell, this is the whole process for any nexus device.
1. fastboot oem unlock
2. fastboot flash a custom recovery
3. flash the su binaries or custom rom in your custom recovery
4. reboot and profit.
if you google fastboot recovery, im sure that youll find an answer. the fastboot process of flashing a recovery is the same for all android devices, just the file name is different.

No seriously, dont flash a Custom Recovery/Custom Rom at first !
I will tell you what to do step by step to get the Original Rom (Stock) working.
First ! Download the Stock rom from google https://dl.google.com/dl/android/aosp/nakasi-jro03d-factory-e102ba72.tgz
2. Get Fastboot, it is in the Android SDK or on the web(would be easier I think)
3. Open CMD/Terminal
4. (Linux/Mac Only otherwise skip this): Type sudo -s (It is going to ask for your password, type it.)
5. Run these command one by one :
fastboot erase boot
fastboot erase system
fastboot erase cache
fastboot erase userdata
fastboot erase recovery
6. Alright so now your device is empty, so any broken file is gone.
7. Extract the firmware you downloaded at first step (Dont extract the archive inside).
8. Type these command :
fastboot flash bootloader bootloader-grouper-3.34.img
fastboot reboot-booloader
fastboot -w update image-nakasi-jro03d.zip
9. Wait until it is done and the device will boot up !

Blue Reaper said:
Just received my Nexus 7 today. I tried booting it up right of the box when the google logo came out and then the screen went black. I thought it might only need recharging. so I plugged it in to charge and waited for the battery icon to show that its charging. I tried booting up again after three hours of charging, the google logo came out again and then the brightness of the screen lowers and I can still barely see the logo. The screen blacked out again and the X showed up and I thought it was booting when it disappeared quickly and it blacked out again. I waited for a while and nothing is showing up on the screen. I tried rebooting a million times and the same thing happens every time. I plugged the tablet to my PC and I can open the internal memory when nothing is showing on the screen after boot up. I went into fastboot mode and unlocked the bootloader and rooted the nexus and tried rebooting with the same result. I tried flashing the stock rom twice using the toolkit and again using adb with no luck. I'm trying to flash a custom rom to see if it fixes anything but I can't seem to boot into recovery either. Can someone show me how to flash a custom rom at fastboot by adb without using recovery? I tried searching for a solution but couldn't find anything. Did someone have the same problem?
I'm from Abu Dhabi and unfortunately I won't be able to return it without wasting a fortune on shipping.
Thanks in advance
Click to expand...
Click to collapse
Sounds to me that your automatic brightness control is off......try this. Power up and after the Nexus X shows up and the screen goes black, give it about two or three minutes to finish booting. Then, with the power still on, take it out in the bright sunlight or shine a flashlight on the screen. If you see the start up options, then it is the brightness control and a simple adjustment in the settings will take care if it.
Good luck!!!

dparrothead1 said:
Sounds to me that your automatic brightness control is off......try this. Power up and after the Nexus X shows up and the screen goes black, give it about two or three minutes to finish booting. Then, with the power still on, take it out in the bright sunlight or shine a flashlight on the screen. If you see the start up options, then it is the brightness control and a simple adjustment in the settings will take care if it.
Good luck!!!
Click to expand...
Click to collapse
You beat me to it! I was going to post this right before I read your reply :silly:
"Thanks for all the help guys! So I found out what's wrong and it is one of the most frustrating defects I have ever encountered. When the screen was blacking out after boot up the device was actually working the whole time only the screen was off (as in ZERO brightness). The way I found out was when I tried rebooting into fastboot I heard a screenshot sound when pressing the power and volume down button. So I hooked up the tablet to my PC to take a look at what I captured. To my surprise, it was the welcome screen. I kept taking screenshots until I reached the settings to enable debugging ( Apparently, the rooting wasn't successful using wug's toolkit). After enabling debugging I was going to reboot but I had an idea. I thought if I used my Galaxy Nexus's LED light on the screen I might be able to see something. Stupid idea right? WRONG! The moment I pointed the light at the screen the screen magically brightened up and was working fine! I turned the screen off and on again and the screen was dim again. And once again turned on when I flashed my LED on it. I figured out it was the light sensor after reading a thread on androidforums...
I guess I'll have to deal with it, I don't use automatic brightness anyway
Thanks again! "

Once you get it going, you should be able to put it on auto and it should work just fine. And if it doesn't, at least you will know how to fix it.
Enjoy your N7, I know I do:laugh:

Blue Reaper said:
You beat me to it! I was going to post this right before I read your reply :silly:
"Thanks for all the help guys! So I found out what's wrong and it is one of the most frustrating defects I have ever encountered. When the screen was blacking out after boot up the device was actually working the whole time only the screen was off (as in ZERO brightness). The way I found out was when I tried rebooting into fastboot I heard a screenshot sound when pressing the power and volume down button. So I hooked up the tablet to my PC to take a look at what I captured. To my surprise, it was the welcome screen. I kept taking screenshots until I reached the settings to enable debugging ( Apparently, the rooting wasn't successful using wug's toolkit). After enabling debugging I was going to reboot but I had an idea. I thought if I used my Galaxy Nexus's LED light on the screen I might be able to see something. Stupid idea right? WRONG! The moment I pointed the light at the screen the screen magically brightened up and was working fine! I turned the screen off and on again and the screen was dim again. And once again turned on when I flashed my LED on it. I figured out it was the light sensor after reading a thread on androidforums...
I guess I'll have to deal with it, I don't use automatic brightness anyway
Thanks again! "
Click to expand...
Click to collapse
Hmm that sucks :/ If I were you, I would not deal with this, I would ask Google/Shop for a replacement. Why keeping something broken when you can get one fully working ? If you deal with google it is cool because you only send your broken device once you got your new one so that way you can keep using it all the time Also, it would be a pain to keep broken, everytime you flash a new rom, you would have the automatic brightness turned on by default :/

jamesst20 said:
Hmm that sucks :/ If I were you, I would not deal with this, I would ask Google/Shop for a replacement. Why keeping something broken when you can get one fully working ? If you deal with google it is cool because you only send your broken device once you got your new one so that way you can keep using it all the time Also, it would be a pain to keep broken, everytime you flash a new rom, you would have the automatic brightness turned on by default :/
Click to expand...
Click to collapse
It's not broken. Just a one time glitch!! :good:

dparrothead1 said:
It's not broken. Just a one time glitch!! :good:
Click to expand...
Click to collapse
Unsure about that, I've tried to reproduce the case and I can't seem to success to get a 0% Backlight.

Get an exchanged aka RMA it. The same thing happened to me. Get an exchange.

Knightsofwar210 said:
Get an exchanged aka RMA it. The same thing happened to me. Get an exchange.
Click to expand...
Click to collapse
Agreed, not working out of the box is Deff asking for an rma
Sent from my Rooted, LazyPanda, White "Destroy Mode" Evo

Why the heck would you try n flash it when it didnt work out the box there could be all sorts wrong with it..
Sent from my Nexus 7 using Tapatalk 2

jamesst20 said:
Unsure about that, I've tried to reproduce the case and I can't seem to success to get a 0% Backlight.
Click to expand...
Click to collapse
You can't reproduce it because it was a one time glitch!!!

[Q] Nexus 4 Download Mode?

Hello, i was trying to charge my nexus 4 couse it wouldn't turn on but after an hour it still didn't turn on.
So after trying a liitle wile to turn it on i held all three buttons (power, volume up & down) and now it says "Download Mode".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Never heard of this mode. Try connecting ur phone to pc and see if it gets detected. That would be nice to know.

gt-kingz said:
Never heard of this mode. Try connecting ur phone to pc and see if it gets detected. That would be nice to know.
Click to expand...
Click to collapse
srry just restarted (it don't appear on the computer, can check with lsusb on ubuntu but not now)

How to do it!
How to get into Download Mode
Boot into bootloader and hold all three buttons

It's LG's version of Samsung's Odin mode. However, there isn't a leak of the utility yet.
There is a long tutorial on how to use it in the Nexus 4 service manual floating around.
Basically it's worthless for us until that utility leaks.

El Daddy said:
It's LG's version of Samsung's Odin mode. However, there isn't a leak of the utility yet.
There is a long tutorial on how to use it in the Nexus 4 service manual floating around.
Basically it's worthless for us until that utility leaks.
Click to expand...
Click to collapse
I'm not entirely sure, but I think that "Download mode" interfaces with LGNPST. From my understanding, it's not publicly available, but...
Anyway, this is an interesting thread.

efrant said:
I'm not entirely sure, but I think that "Download mode" interfaces with LGNPST. From my understanding, it's not publicly available, but...
Anyway, this is an interesting thread.
Click to expand...
Click to collapse
Interesting indeed. So it looks like I'm wrong. Most of that stuff is way over my head though.
Sent from my Nexus 7 using xda premium

When I first rooted I flashed a bad recovery that deleted all my stuff and got into DL mode 3 times, I panicked. Somehow I managed to get back into boot loader and after that flashed stock boot.IMG and re-rooted...
Sent from my Nexus 4 using xda app-developers app

309041291a said:
When I first rooted I flashed a bad recovery that deleted all my stuff and got into DL mode 3 times, I panicked. Somehow I managed to get back into boot loader and after that flashed stock boot.IMG and re-rooted...
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
i'm in the same situation and appropriate anybody's help to get me back into the right track.

So what happened with this? Mine just did the same while doing the rooting of my phone. I've been using MSKIP's tutorial amongst other youtube videos showing his option in depth. No idea what happened but now I'm stuck in this "brick" or "soft brick" mode like you guys were saying earlier. What is the solution? I don't see any other pages in this thread and I'm a total noob with this stuff.
**Edit**
Fixed mine, was waiting for a while like it said but I finally powered it one, did a factory reset, and re-did everything else that comes with the 1 CLICK FOR ALL button on mskip's toolkit. Everything is perfect now and I hacked it, whoo hoo!

easy fix... working..
Jbele said:
Hello, i was trying to charge my nexus 4 couse it wouldn't turn on but after an hour it still didn't turn on.
So after trying a liitle wile to turn it on i held all three buttons (power, volume up & down) and now it says "Download Mode".
Click to expand...
Click to collapse
this same problem happened to me today.. don't worry there is a fix...
1.Get into bootloader ( Press all three buttons at same time)
2.flash google factory image from fastboot. get factory images from here... https://developers.google.com/android/nexus/images ..
3.If you dont know how to flash use mskip's toolkit for nexus 4 and flash it... (best for new users like me) get mskip's toolkit from here... http://forum.xda-developers.com/showthread.php?t=1995688
ALL THANKS TO MSKIP'S TOOLKIT
if you have queries or want detailed information comment below
NICE FEELING WHEN YOU SEE DOWNLOAD MODE... WORTH EXPERIENCING THE MINI HEART ATTACK..
DON'T WORRY ITS NEARLY IMPOSSIBLE TO BRICK NEXUS 4..
:good::good::good: ALL THE BEST:good::good::good:
HOPE THIS WORKS

shengovind said:
this same problem happened to me today.. don't worry there is a fix...
1.Get into bootloader ( Press all three buttons at same time)
2.flash google factory image from fastboot. get factory images from here... https://developers.google.com/android/nexus/images ..
3.If you dont know how to flash use mskip's toolkit for nexus 4 and flash it... (best for new users like me) get mskip's toolkit from here... http://forum.xda-developers.com/showthread.php?t=1995688
ALL THANKS TO MSKIP'S TOOLKIT
if you have queries or want detailed information comment below
NICE FEELING WHEN YOU SEE DOWNLOAD MODE... WORTH EXPERIENCING THE MINI HEART ATTACK..
DON'T WORRY ITS NEARLY IMPOSSIBLE TO BRICK NEXUS 4..
:good::good::good: ALL THE BEST:good::good::good:
HOPE THIS WORKS
Click to expand...
Click to collapse
it happened to me now, when the battery was dead. when i connect the phone to a wall charger i got the download mode massage ,
when i'm pressing all 3 buttons the phone makes a vibe (like a boot vibe) and the the red light is flashing on/off
no bootloader.
what to do?

havlaz said:
it happened to me now, when the battery was dead. when i connect the phone to a wall charger i got the download mode massage ,
when i'm pressing all 3 buttons the phone makes a vibe (like a boot vibe) and the the red light is flashing on/off
no bootloader.
what to do?
Click to expand...
Click to collapse
You should try to get into the fastboot mode first, when the phone is off, Hold Power + Volume Download button. If you can get in the fastboot menu, then use instruction above to reflash your device.
If you can't, you might be able to recover your phone using Download Mode: http://forum.xda-developers.com/showthread.php?t=2347060

havlaz said:
it happened to me now, when the battery was dead. when i connect the phone to a wall charger i got the download mode massage ,
when i'm pressing all 3 buttons the phone makes a vibe (like a boot vibe) and the the red light is flashing on/off
no bootloader.
what to do?
Click to expand...
Click to collapse
Red light due to battery low..
All you have to do is charge the phone for about six hours on the wall charger..
Then try booting your phone ..
If there's only bootloader and phone isn't booting flash factory from fastboot..
Plug it to wall charger over night.. Then try to get to download mode..
Try this to get out of red light only if there is absolutely no other way..: http://forum.xda-developers.com/showthread.php?t=2250454
If there is no boot loader whatsoever even after trying for a hell lot of time, only download mode, then do this..
http://forum.xda-developers.com/showthread.php?t=2347060
sent from my Prevert nexus

psak said:
i'm in the same situation and appropriate anybody's help to get me back into the right track.
Click to expand...
Click to collapse
When you are in download mode, press and hold Vol Down and Power, that should bring up fastboot mode, which you can use to flash another recovery...

[email protected] said:
When you are in download mode, press and hold Vol Down and Power, that should bring up fastboot mode, which you can use to flash another recovery...
Click to expand...
Click to collapse
Try Pressing power button alone for 10 sec or so...
Should do the trick

Having the same problem. I was on purity rom(4.4.3), with default purity kernel. I flashed the Ak poseidon kernel, with Ukm. It booted fine , was on phone for about 4 minutes, and then I ran antutu benchmark. Before that I didn’t change anything via synapse app. Then when I ran test on antutu phone went off. Non of the buttons were responding. I plugged the phone into wall charger and pressed all 3 buttons. Then the download mode appeared. Left it like that on the charger , went to sleep. When I woke up the phone was turned off. Today I was flashing factory img ( 4.4.3. occam). Following the instructions http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312 [/URL]. Everything went ok no problem in the cmd , only the thing was , when I had to fastboot the booth loader, then the phone stuck in power on loop . ( reboots, then it says google, and reboots again) I was able to stop this by holding volume down, then it goes into bootloader. Finished flashing factory img, like it says on the tut. And the same thing happens. The phone won’t boot, And it is not responding when it is unplugged. Please help :/
---------- Post added at 03:28 PM ---------- Previous post was at 03:26 PM ----------
shengovind said:
Red light due to battery low..
All you have to do is charge the phone for about six hours on the wall charger..
Then try booting your phone ..
If there's only bootloader and phone isn't booting flash factory from fastboot..
Plug it to wall charger over night.. Then try to get to download mode..
Try this to get out of red light only if there is absolutely no other way..: http://forum.xda-developers.com/showthread.php?t=2250454
If there is no boot loader whatsoever even after trying for a hell lot of time, only download mode, then do this..
http://forum.xda-developers.com/showthread.php?t=2347060
sent from my Prevert nexus
Click to expand...
Click to collapse
I will try to reconnect the battery now, maby that will help----

Fixed it !
ripped.animal said:
Having the same problem. I was on purity rom(4.4.3), with default purity kernel. I flashed the Ak poseidon kernel, with Ukm. It booted fine , was on phone for about 4 minutes, and then I ran antutu benchmark. Before that I didn’t change anything via synapse app. Then when I ran test on antutu phone went off. Non of the buttons were responding. I plugged the phone into wall charger and pressed all 3 buttons. Then the download mode appeared. Left it like that on the charger , went to sleep. When I woke up the phone was turned off. Today I was flashing factory img ( 4.4.3. occam). Following the instructions http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312 [/URL]. Everything went ok no problem in the cmd , only the thing was , when I had to fastboot the booth loader, then the phone stuck in power on loop . ( reboots, then it says google, and reboots again) I was able to stop this by holding volume down, then it goes into bootloader. Finished flashing factory img, like it says on the tut. And the same thing happens. The phone won’t boot, And it is not responding when it is unplugged. Please help :/
---------- Post added at 03:28 PM ---------- Previous post was at 03:26 PM ----------
I will try to reconnect the battery now, maby that will help----
Click to expand...
Click to collapse
After reconnecting the battery, I managed to boot the device. But i got gazzlion errors, non of the apps were responding. I got the msg to delete the partion or my device will not function properly. Since I have already flashed the factory img I booted to stock recovery. And deleted all user data , (factory reset). Then the device booted normally. I have lost my recovery img but what the hell I don’t care now Flashed the CMW touch, and super user. Now everything works fine

Fix - Volume Up + Power
I had the same problem this morning and found an easier fix on Google product forums.
Push Volume Up + Power button until it works. Worked for me
<not able to paste link as I'm still a n00b user and this is among my first ten posts here. Ok, this is my FIRST post here>

I got the same thing too...

S5 G900F - Infinite Bootloop, can't access bootloader, flashed with stock roms.. HELP

Hi,
**Long Story**
I'm new here - I refrained from posting as I know a repeat post can p*** people off but I can't find my problem or fix it.
My own Sony was stolen a week ago - My brother in law kindly gave me his old S5 as a back up phone.
He has never had any problems with it EVER. I did a factory reset (from the settings menu) to clear his data and straight away I was in a boot loop (Handset vibrates, Samsung logo displays, blue LED, vibrates, handset switches off.. over and over again) the only way to stop this is to remove the battery. I cannot enter recovery mode but I CAN enter download mode. According to the settings the handset was running the latest version of lollipop.
I took the phone home anyway, thinking I could fix it - leaving the battery out in my pocket.
When I got home, I put the battery in and the phone turned on, unfortunately I forgot to put the sim card in - so I removed the battery, put in the sim card and... Boot Loop!
At this point I was really frustrated so I left the battery out and went to sleep. I woke up in the morning, put the battery in and it worked fine, all day, then all of a sudden the phone switched itself off and now I'm back in a boot loop and this time it isn't wanting to work again.
I have:
- Flashed with stock roms using Odin (5.0 & 4.4.2) - Yes, I used the correct firmware for my handset.
- Flashed with Kies to the latest firmware
- In desperation, tried the "Bash your power button against a hard, flat surface" trick
- Shouted at the handset
None of these have worked and every post I have found says to put the phone in recovery mode, I CANT. When I try, the blue "Recovery Booting" text is displayed, but just restarts anyway...
Weirdly and at random times, twice, the phone has powered on while plugged into my laptop, but the screen is blank, I get message sounds and the soft keys below the screen light up, but the screen is blank.
Any body have any idea?!?!! I'm vaguely techy, however not with this kind of thing. Any help would be much appreciated. What confuses me is there was no problem before I did the factory reset.

didscub said:
Hi,
**Long Story**
I'm new here - I refrained from posting as I know a repeat post can p*** people off but I can't find my problem or fix it.
My own Sony was stolen a week ago - My brother in law kindly gave me his old S5 as a back up phone.
He has never had any problems with it EVER. I did a factory reset (from the settings menu) to clear his data and straight away I was in a boot loop (Handset vibrates, Samsung logo displays, blue LED, vibrates, handset switches off.. over and over again) the only way to stop this is to remove the battery. I cannot enter recovery mode but I CAN enter download mode. According to the settings the handset was running the latest version of lollipop.
I took the phone home anyway, thinking I could fix it - leaving the battery out in my pocket.
When I got home, I put the battery in and the phone turned on, unfortunately I forgot to put the sim card in - so I removed the battery, put in the sim card and... Boot Loop!
At this point I was really frustrated so I left the battery out and went to sleep. I woke up in the morning, put the battery in and it worked fine, all day, then all of a sudden the phone switched itself off and now I'm back in a boot loop and this time it isn't wanting to work again.
I have:
- Flashed with stock roms using Odin (5.0 & 4.4.2) - Yes, I used the correct firmware for my handset.
- Flashed with Kies to the latest firmware
- In desperation, tried the "Bash your power button against a hard, flat surface" trick
- Shouted at the handset
None of these have worked and every post I have found says to put the phone in recovery mode, I CANT. When I try, the blue "Recovery Booting" text is displayed, but just restarts anyway...
Weirdly and at random times, twice, the phone has powered on while plugged into my laptop, but the screen is blank, I get message sounds and the soft keys below the screen light up, but the screen is blank.
Any body have any idea?!?!! I'm vaguely techy, however not with this kind of thing. Any help would be much appreciated. What confuses me is there was no problem before I did the factory reset.
Click to expand...
Click to collapse
Who is your service provider? Is the phone unlocked? Where did you get the stock firmware from?

Cryceratops said:
Who is your service provider? Is the phone unlocked? Where did you get the stock firmware from?
Click to expand...
Click to collapse
Thanks for the reply!
Service Provider - o2 UK
Stock from sanmmob
Phone is not unlocked
I did my best to try & get the firmware for my particular service provider but sammob and a few of the other sites use those awful restricted speed file sharing sites.

didscub said:
Thanks for the reply!
Service Provider - o2 UK
Stock from sanmmob
Phone is not unlocked
I did my best to try & get the firmware for my particular service provider but sammob and a few of the other sites use those awful restricted speed file sharing sites.
Click to expand...
Click to collapse
Did you try the one I linked to you or a different one?

Cryceratops said:
Did you try the one I linked to you or a different one?
Click to expand...
Click to collapse
Only just saw that - I didnt - thank you.
I will try now but may take a while to get back to you while I wait to download.

Try flashing the PIT file along with the stock ROM in ODIN
http://forum.xda-developers.com/attachment.php?attachmentid=2721101&d=1399024091
Extract to .pit - add to PIT section in ODIN, add ROM to AP or PDA section, flash them both at the same time

*Detection* said:
Try flashing the PIT file along with the stock ROM in ODIN
http://forum.xda-developers.com/attachment.php?attachmentid=2721101&d=1399024091
Extract to .pit - add to PIT section in ODIN, add ROM to AP or PDA section, flash them both at the same time
Click to expand...
Click to collapse
Thanks, did that, now the phone has started but it stuck at the first "Powered by Android" screen, not restarting but can't go any further and still cant get into recovery.

didscub said:
Thanks, did that, now the phone has started but it stuck at the first "Powered by Android" screen, not restarting but can't go any further and still cant get into recovery.
Click to expand...
Click to collapse
Try flashing just the ROM again, and then try booting into recovery, and factory reset
Or try flashing TWRP 2.8.7.0 with ODIN, and then boot into recovery and factory reset
Use this guide (Don't worry about the SuperSU part if you don't need root, and ignore the reactivation part as you can't boot the phone yet - start at No.3)
http://forum.xda-developers.com/showpost.php?p=64961009&postcount=2
Are you flashing the latest Lollipop ROM too?
https://mega.nz/#!fVhhzRBC!A79uC8Fgg1mGCZOaujQCzBxcUUN9z_ctVVkigD8ffVM

*Detection* said:
Try flashing just the ROM again, and then try booting into recovery, and factory reset
Or try flashing TWRP 2.8.7.0 with ODIN, and then boot into recovery and factory reset
Use this guide (Don't worry about the SuperSU part if you don't need root, and ignore the reactivation part as you can't boot the phone yet - start at No.3)
http://forum.xda-developers.com/showpost.php?p=64961009&postcount=2
Are you flashing the latest Lollipop ROM too?
https://mega.nz/#!fVhhzRBC!A79uC8Fgg1mGCZOaujQCzBxcUUN9z_ctVVkigD8ffVM
Click to expand...
Click to collapse
flashed TWRP 2.8.7.0 - Doesn't go into revovery:
Recovery is not SEANDROID ENFORCING
Set Warranty Bit : Recovery
I was flashing with G900FXXU1BOJ1_G900FOXA1BOJ1_G900FXXU1BOJ1_HOME.tar.md5

didscub said:
flashed TWRP 2.8.7.0 - Doesn't go into revovery:
Recovery is not SEANDROID ENFORCING
Set Warranty Bit : Recovery
I was flashing with G900FXXU1BOJ1_G900FOXA1BOJ1_G900FXXU1BOJ1_HOME.tar.md5
Click to expand...
Click to collapse
Did you follow the guide I linked?
http://forum.xda-developers.com/showpost.php?p=64961009&postcount=2
Pull the battery after flash, do not allow the phone to reboot first etc?
Because that error is usually associated with you allowing the phone to reboot Automatically after flashing TWRP

*Detection* said:
Did you follow the guide I linked?
http://forum.xda-developers.com/showpost.php?p=64961009&postcount=2
Pull the battery after flash, do not allow the phone to reboot first etc?
Because that error is usually associated with you allowing the phone to reboot Automatically after flashing TWRP
Click to expand...
Click to collapse
Pulled as soon as it said Pass.
This is so confusing, is the Stock firmware that you've linked to in Mega the same as the one I have downloaded?
Will retry with TWRP again. BRB

didscub said:
Pulled as soon as it said Pass.
This is so confusing, is the Stock firmware that you've linked to in Mega the same as the one I have downloaded?
Will retry with TWRP again. BRB
Click to expand...
Click to collapse
BOJ1 yea, same one
Try different versions of ODIN, 3.09 up to 3.10.7 (Maybe even 3.07)

*Detection* said:
Did you follow the guide I linked?
http://forum.xda-developers.com/showpost.php?p=64961009&postcount=2
Pull the battery after flash, do not allow the phone to reboot first etc?
Because that error is usually associated with you allowing the phone to reboot Automatically after flashing TWRP
Click to expand...
Click to collapse
Definitely didt let it reboot & pulled the battery. Tried it twice to make sure.
I am downloading the Stock firmware that you have linked and will try that, is there any reason why it started to reboot constantly after I factory reset? It can't be hardware because there was never a HW problem before I reset it. I don't suppose you want to pop down from Durham and fix it?! lol

didscub said:
Definitely didt let it reboot & pulled the battery. Tried it twice to make sure.
I am downloading the Stock firmware that you have linked and will try that, is there any reason why it started to reboot constantly after I factory reset? It can't be hardware because there was never a HW problem before I reset it. I don't suppose you want to pop down from Durham and fix it?! lol
Click to expand...
Click to collapse
To London? wanna pay the plane fare? lol
If you got that firmware from Sammobile, the one I linked you to is the same one, that's where I got it from, you could try some different droid versions, try a KitKat ROM too
Not sure why it would boot loop after you factory reset it, if reactivation lock was left on, you should still have managed to get to the welcome screen, but then be locked out of the phone until you entered his samsung account login
Sounds like something bugged out during the reset, and didn't reset properly, or corrupted one of the partitions, which the PIT file should have fixed
Stock recovery is cr4p though, I've ended up with a bootloop just clearing caches from it before, and had to flash TWRP to clear them properly, then flash stock on top again just to get it to boot

*Detection* said:
To London? wanna pay the plane fare? lol
If you got that firmware from Sammobile, the one I linked you to is the same one, that's where I got it from, you could try some different droid versions, try a KitKat ROM too
Not sure why it would boot loop after you factory reset it, if reactivation lock was left on, you should still have managed to get to the welcome screen, but then be locked out of the phone until you entered his samsung account login
Sounds like something bugged out during the reset, and didn't reset properly, or corrupted one of the partitions, which the PIT file should have fixed
Stock recovery is cr4p though, I've ended up with a bootloop just clearing caches from it before, and had to flash TWRP to clear them properly, then flash stock on top again just to get it to boot
Click to expand...
Click to collapse
OK - Sorry for the delay but unfortunately I had to do stuff - I would have happily sat and tried to fix it all day.
So, I did spend some time on it earlier and a few things happened.
I reinstalled different firmwares, and also tried TWRP 2.8.7.0 a few times with different versions of Odin but nothing would work.
I reinstalled the firmware BOJ1, nothing
Tried PIT again, nothing
Then, after trying PIT I got the Firmware error and connected to Kies... It worked, but now I just have a blank screen (another seemingly common issue with these paperweights) - Unsure what to do now, the phone is on, i can call it, find it with device manager but the screen is just blank. FML.

didscub said:
OK - Sorry for the delay but unfortunately I had to do stuff - I would have happily sat and tried to fix it all day.
So, I did spend some time on it earlier and a few things happened.
I reinstalled different firmwares, and also tried TWRP 2.8.7.0 a few times with different versions of Odin but nothing would work.
I reinstalled the firmware BOJ1, nothing
Tried PIT again, nothing
Then, after trying PIT I got the Firmware error and connected to Kies... It worked, but now I just have a blank screen (another seemingly common issue with these paperweights) - Unsure what to do now, the phone is on, i can call it, find it with device manager but the screen is just blank. FML.
Click to expand...
Click to collapse
OK, so they phone is working, there's just no display...
OK, try resetting the phone remotely from here first
https://www.google.com/android/devicemanager
If it's not connected to the network - try this
http://forums.androidcentral.com/sa...ory-reset-galaxy-s5-computer.html#post4365754
If that still fails, try flashing a stock KitKat ROM from Sammobile, see if downgrading the OS is a big enough change for it to overwrite whatever is causing the problem
Wondering if TWRP has flashed, but the no screen thing is stopping you from knowing one way or another - if we could get into TWRP, we'd have a lot more options, including custom ROMs
---------- Post added at 10:00 ---------- Previous post was at 09:44 ----------
Uploaded the latest KitKat ROM
Code:
https://mega.nz/#!eIQEAQ6a!ztOhVwFuI2MpD6OBhxC-TtgwUJQCxtwnfDQvFOl3g40

*Detection* said:
OK, so they phone is working, there's just no display...
OK, try resetting the phone remotely from here first
https://www.google.com/android/devicemanager
If it's not connected to the network - try this
http://forums.androidcentral.com/sa...ory-reset-galaxy-s5-computer.html#post4365754
If that still fails, try flashing a stock KitKat ROM from Sammobile, see if downgrading the OS is a big enough change for it to overwrite whatever is causing the problem
Wondering if TWRP has flashed, but the no screen thing is stopping you from knowing one way or another - if we could get into TWRP, we'd have a lot more options, including custom ROMs
---------- Post added at 10:00 ---------- Previous post was at 09:44 ----------
Uploaded the latest KitKat ROM
Code:
https://mega.nz/#!eIQEAQ6a!ztOhVwFuI2MpD6OBhxC-TtgwUJQCxtwnfDQvFOl3g40
Click to expand...
Click to collapse
Thanks,
I'll wait for that to download and try.
So - I used accessibility mode to get into settings and do a factory reset... It was difficult, I even thought that the Dark Screen setting might have mysteriously have been turned on but nope.
Rebooted and got the Bootloader screen with the Samsung logo and Recovery Booting text, after a few minutes the screen went blank and the phone vibrated and then nothing!!! :crying::crying::crying:
I have just put it into download mode (I only know this because the many hours I've spent doing this I noticed that the battery and device goes cool when its in download mode) and will try the KitKat flash once its downloaded - Thank you for that btw.
Its so strange - it cant be an issue with the actual screen because it *sometimes* displays the logo.. What can it be?? Its also odd that from when I originally reset it, it could'nt boot into recovery. I'm worried that everything I have done has screwed it up more? Can the Recovery/Bootloader be "Broken"? Its so confusing, I hate tech that doesn't behave.

didscub said:
Thanks,
I'll wait for that to download and try.
So - I used accessibility mode to get into settings and do a factory reset... It was difficult, I even thought that the Dark Screen setting might have mysteriously have been turned on but nope.
Rebooted and got the Bootloader screen with the Samsung logo and Recovery Booting text, after a few minutes the screen went blank and the phone vibrated and then nothing!!! :crying::crying::crying:
I have just put it into download mode (I only know this because the many hours I've spent doing this I noticed that the battery and device goes cool when its in download mode) and will try the KitKat flash once its downloaded - Thank you for that btw.
Its so strange - it cant be an issue with the actual screen because it *sometimes* displays the logo.. What can it be?? Its also odd that from when I originally reset it, it could'nt boot into recovery. I'm worried that everything I have done has screwed it up more? Can the Recovery/Bootloader be "Broken"? Its so confusing, I hate tech that doesn't behave.
Click to expand...
Click to collapse
Does sound like a possible hardware problem, but unlikely or a huge coincidence that it all started after resetting, so I'd be more inclined to think otherwise
Just remembered about this unbrick image / tutorial
http://forum.xda-developers.com/galaxy-s5/general/g900f-debrick-img-lollipop-t3240626
Might be worth giving that a shot

*Detection* said:
Does sound like a possible hardware problem, but unlikely or a huge coincidence that it all started after resetting, so I'd be more inclined to think otherwise
Just remembered about this unbrick image / tutorial
http://forum.xda-developers.com/galaxy-s5/general/g900f-debrick-img-lollipop-t3240626
Might be worth giving that a shot
Click to expand...
Click to collapse
OK - might be a massive chore rooting and installing busybox.. Worth a shot though. Can I not use it with Odin??

didscub said:
OK - might be a massive chore rooting and installing busybox.. Worth a shot though. Can I not use it with Odin??
Click to expand...
Click to collapse
You don't need busybox, that's for creating your own debrick image, the tutorial stops here:
Flash this Debrick file to your 16GB Micro SD card with Win32DiskImager
*Insert your Micro SD card into your computer (backup any information you may have on it we are going to ERASE, FORMAT it to ex FAT
*Open win32DiskImager
*Navigate to the location where you downloaded the correct Debrick file
*Select your Debrick file by double clicking on it
*In the upper right corner of Win32DiskImager you should make sure that the drive letter assigned to your sd card is selected.
***Which ever drive that is listed will be erased, formatted
*Click write in the bottom right hand side
put the Debrick SD card in the Phone, Pull and Replace the Battery
Plug phone in usb and boot into download mode
yout phone should boot into download mode then flash stock firmware via odin
Download link : https://drive.google.com/file/d/0ByA...ew?usp=sharing
You're saying you can't see anything on screen in download mode, just guessing it's there because it cools down - but that could also mean it's not in any mode
With this method, you might get a display to use, then you can flash normally with ODIN with download mode visible on screen

Phone won't boot, blue screen

Hi guys, so I recently have this problem where I try to turn on my phone and he starts to boot and at the part where the boot animation comes it shows only a blue screen for like 10-15 secs and then turns off. That happend after I was trying to disassemble the phone(long story), anyway I didn't completely disassemble it just took out the screws and then gave up and put the screws back. The blue screen happens only when I get the battery out and back, if I try to boot the phone after the blue screen it just gets to bootloop. Guys, please, I need very fast help because the phone isn't mine(Yes I know im stupid). Anyway thanks for reading this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

xgamer231 said:
Hi guys, so I recently have this problem where I try to turn on my phone and he starts to boot and at the part where the boot animation comes it shows only a blue screen for like 10-15 secs and then turns off. That happend after I was trying to disassemble the phone(long story), anyway I didn't completely disassemble it just took out the screws and then gave up and put the screws back. The blue screen happens only when I get the battery out and back, if I try to boot the phone after the blue screen it just gets to bootloop. Guys, please, I need very fast help because the phone isn't mine(Yes I know im stupid). Anyway thanks for reading this.
Click to expand...
Click to collapse
Google un brick Samsung j5

infixremix said:
Google un brick Samsung j5
Click to expand...
Click to collapse
I have already flashed a stock firmware and still the blue screen.

xgamer231 said:
I have already flashed a stock firmware and still the blue screen.
Click to expand...
Click to collapse
Damn... Try using another ROM. If you can get to the part where the boot logo should be but appears blue screen you migh have a chance...
Get into download mode and flash TWRP trough Odin and one of the custom ROMs around. If it boots into TWRP succesfully and after that it succesfully boots into the ROM you just installed trough TWRP, than it was a software issue. If it doesn't boot and you get the same exact blue screen... It might be either a hardware error or an issue with the bootloader. I'm really saying that because it is one of the more sensitive and important parts of the firmware and the fact that your blue screen color is exactly the same as the download mode (bootloader) might link it to an issue with a bootloader.
@Henkate, I'm summoning you. Maybe you an help this fella as I think you know loads more things about the firmware
BTW: next time don't mess with hardware. Messing with software is easier and safer : )
Also... What were you trying to do by taking the poor guy appart? Replacing the screen maybe? Stuck SIM card?

Amarius1 said:
Damn... Try using another ROM. If you can get to the part where the boot logo should be but appears blue screen you migh have a chance...
Get into download mode and flash TWRP trough Odin and one of the custom ROMs around. If it boots into TWRP succesfully and after that it succesfully boots into the ROM you just installed trough TWRP, than it was a software issue. If it doesn't boot and you get the same exact blue screen... It might be either a hardware error or an issue with the bootloader. I'm really saying that because it is one of the more sensitive and important parts of the firmware and the fact that your blue screen color is exactly the same as the download mode (bootloader) might link it to an issue with a bootloader.
@Henkate, I'm summoning you. Maybe you an help this fella as I think you know loads more things about the firmware
BTW: next time don't mess with hardware. Messing with software is easier and safer : )
Also... What were you trying to do by taking the poor guy appart? Replacing the screen maybe? Stuck SIM card?
Click to expand...
Click to collapse
Well I'll try a custom rom when I get come, but now I will tell you the whole story how it went trough. So when I got this phone it was stuck in a bootloop(it boots up, freezes for 5-10 secs and restarts and so on), and I tried hard reset and putting stock firmware and still nothing. I got to a conclusion, because the phone was drowned in water few days ago, maybe the power button had a short circuit so I went disassembling it to try to dry more the motherboard, when I took of the screws I realized I can't get to the mobo because I needed to get first the display off and I didn't had the tools for that. Anyway I put the screws back and boom blue screen.
The blue color isn't exactly the same like in download mode, the camera I took the picture with is very bad. The blue color is a standard blue blue(like in rgb).
I don't believe it couls be a hardware failure, because I didn't touch anything drastic, one thing I did touch was the display cable under the little panel, I just plug it off.
Btw. Just to mention its the J500FN model.
I really apprechiate the help guys :S

xgamer231 said:
Well I'll try a custom rom when I get come, but now I will tell you the whole story how it went trough. So when I got this phone it was stuck in a bootloop(it boots up, freezes for 5-10 secs and restarts and so on), and I tried hard reset and putting stock firmware and still nothing. I got to a conclusion, because the phone was drowned in water few days ago, maybe the power button had a short circuit so I went disassembling it to try to dry more the motherboard, when I took of the screws I realized I can't get to the mobo because I needed to get first the display off and I didn't had the tools for that. Anyway I put the screws back and boom blue screen.
The blue color isn't exactly the same like in download mode, the camera I took the picture with is very bad. The blue color is a standard blue blue(like in rgb).
I don't believe it couls be a hardware failure, because I didn't touch anything drastic, one thing I did touch was the display cable under the little panel, I just plug it off.
Btw. Just to mention its the J500FN model.
I really apprechiate the help guys :S
Click to expand...
Click to collapse
This looks like hardware failure. I would check the cable for the display you removed is properly connected.
If it is then it may be you've damaged the delicate connector.

ashyx said:
This looks like hardware failure. I would check the cable for the display you removed is properly connected.
If it is then it may be you've damaged the delicate connector.
Click to expand...
Click to collapse
The cable is in place, I don't really believe its the cable because bl and recovery are fine(no graphical disorders).
Just tried to flash TWRP, and I got a auth fail(google says i need to autorize something in dev settings idrk), strange thing I don't get the bootloop anymore when I try to turn on the phone after the blue screen shuts off.
Here's a video:
https://www.youtube.com/watch?v=tWkqTg77rbg

xgamer231 said:
The cable is in place, I don't really believe its the cable because bl and recovery are fine(no graphical disorders).
Just tried to flash TWRP, and I got a auth fail(google says i need to autorize something in dev settings idrk), strange thing I don't get the bootloop anymore when I try to turn on the phone after the blue screen shuts off.
Here's a video:
Click to expand...
Click to collapse
Bro, why don't you go to service somewhere in your city, im sure they wouldn't take much money for that fix since i believe it is minor hardware failure, they have appropriate tools and will get the job done quickly. Don't mess with your phone further more. I know this is not the answer you exoected but this is what i would do since i would rather give up on 20$ and be safe.

xgamer231 said:
The cable is in place, I don't really believe its the cable because bl and recovery are fine(no graphical disorders).
Just tried to flash TWRP, and I got a auth fail(google says i need to autorize something in dev settings idrk), strange thing I don't get the bootloop anymore when I try to turn on the phone after the blue screen shuts off.
Here's a video:
Click to expand...
Click to collapse
But can you enter Recovery? If yes, you can transfer a rom zip file from your computer to phone as adb is working in TWRP. If after flashing the ROM you still get the blue screen... Than it definetelly isn't a software issue, but a hardware one, persisting no matter what you do to the software.

Amarius1 said:
Damn... Try using another ROM. If you can get to the part where the boot logo should be but appears blue screen you migh have a chance...
Get into download mode and flash TWRP trough Odin and one of the custom ROMs around. If it boots into TWRP succesfully and after that it succesfully boots into the ROM you just installed trough TWRP, than it was a software issue. If it doesn't boot and you get the same exact blue screen... It might be either a hardware error or an issue with the bootloader. I'm really saying that because it is one of the more sensitive and important parts of the firmware and the fact that your blue screen color is exactly the same as the download mode (bootloader) might link it to an issue with a bootloader.
@Henkate, I'm summoning you. Maybe you an help this fella as I think you know loads more things about the firmware
BTW: next time don't mess with hardware. Messing with software is easier and safer : )
Also... What were you trying to do by taking the poor guy appart? Replacing the screen maybe? Stuck SIM card?
Click to expand...
Click to collapse
Amarius1 said:
But can you enter Recovery? If yes, you can transfer a rom zip file from your computer to phone as adb is working in TWRP. If after flashing the ROM you still get the blue screen... Than it definetelly isn't a software issue, but a hardware one, persisting no matter what you do to the software.
Click to expand...
Click to collapse
Yea, but I don't have TWRP installed because odin gives me some auth fail. I don't really know to give up or continue with this.

xgamer231 said:
Yea, but I don't have TWRP installed because odin gives me some auth fail. I don't really know to give up or continue with this.
Click to expand...
Click to collapse
It's possible you have damaged the emmc. The bootloader resides on a different part of memory to the rest of the firmware.
However, can you actually boot to stock recovery?

ashyx said:
It's possible you have damaged the emmc. The bootloader resides on a different part of memory to the rest of the firmware.
However, can you actually boot to stock recovery?
Click to expand...
Click to collapse
Yes, everything exept the bot sequence is fine.

Have you tried factory reset in recovery?

It looks for GPU failure, not a software.
Anyway, it happened after disassembly, before as I suppose everything was working so dissamblessing was the most probably cause of this.
As a mate mentioned, go to a service center, they should agree with my opinion. Unfortunately mainboard switch would fix it.
Wysłane z mojego Nexus 5X przy użyciu Tapatalka

xgamer231 said:
Yea, but I don't have TWRP installed because odin gives me some auth fail. I don't really know to give up or continue with this.
Click to expand...
Click to collapse
Right what I suggest you do is re install stock from Odin then download NICK VERSES twrp install that and then install a ROM either RR or cm 13 if that doesn't work take it to a store

infixremix said:
Right what I suggest you do is re install stock from Odin then download NICK VERSES twrp install that and then install a ROM either RR or cm 13 if that doesn't work take it to a store
Click to expand...
Click to collapse
He cant flash anything custom as he can't enable OEM unlock.

ashyx said:
He cant flash anything custom as he can't enable OEM unlock.
Click to expand...
Click to collapse
Ffs take it to a shop then
---------- Post added at 01:50 AM ---------- Previous post was at 01:39 AM ----------
xgamer231 said:
I have already flashed a stock firmware and still the blue screen.
Click to expand...
Click to collapse
http://www.any-data-recovery.com/an...e-blue-screen-of-death-on-samsung-galaxy.html it seems to be a software issue

Okay looks like we're out of solutions, I'll take the phone back to his owner and explain the situation.
Thank you all guys, I really apprechiate the help

Same problem
Got the same problem with my friends device 3 days ago
What should i do i haven't try anything yet but thinking to re assembly it

Hello, i know this threat is very old, but recently i sufer the same problem (Yes i dissambled the phone). My problem was worst because eventually my phone wasn't booting at all. So heres what i do:
1. I took the battery out.
2. I plug in the charger until the phone gets a bit hot.
3. Then (with the charger still plugged) i put the battery back.
4. After that i get the charging screen, so i press the power on button and the phone booting on normally.
Note: While i was doing that process the phone was without the back part (i mean the part where the speaker is) and i reassembled the phone while it was on.
I Hope this help someone!!!!

Recover bricked M3?

Hi guys, wondering if you could help me here.
1) I recently upgraded my M3 to Nougat by mistake and tried to use the "C100B009" full rom to downgrade to MM using "Power + Vol up + Vol down".
2) I was stuck in eRecovery after the update and I realized i missed out the rollback package. So i downloaded and extracted the contents of rollback package to "dload" folder and ran the update again. But it seems afterwards, the tablet was stuck on ""Your device is booting now", and the Power + Vol up + Vol down doesn't work anymore.
3) I managed to get into fastboot and bootloader was locked. So i issued the unlock command based on keys i had saved earlier. The command said it worked and it would reboot and wipe the phone.
4) After the reboot, it seems i'm again stuck in "Your device is booting now". I can't shut down the tablet as it would just reboot, vibrate twice and show the same message again. Eventually, it flat of battery.
5) I also don't seem to be able to go into fastboot anymore. Holding Vol down and plugging into computer still gets me the "Your device is booting now" message. Also, the tablet can't hold a charge. It will blink red. Seem to charge a little after a while, then power itself into "Your device is booting now" message, drain flat, and repeat the cycle again.
Anyone could give any advice on this or would i have to bring down to a service centre for replacement..... :crying:

If you had read here other threads you will be able to solve at least a big part of your problem.

I just had similar situation this weekend while trying updates. I let it die, then tried to boot by plugging into good AC adapter (not PC USB). It showed booting for a while. Eventually it just came up. I had done that dead battery, then little bit of charge multiple times. Good luck.

nostep said:
I just had similar situation this weekend while trying updates. I let it die, then tried to boot by plugging into good AC adapter (not PC USB). It showed booting for a while. Eventually it just came up. I had done that dead battery, then little bit of charge multiple times. Good luck.
Click to expand...
Click to collapse
Hmm, when you said it just came up, did you mean the tablet booted up normally? Or you meant you could go into fastboot after your staggered charging? Because i tried charging with AC adapter before, but the tablet turns itself on after a while, and then just runs itself flat again with the "Your device is booting now" message. I can't seem to trigger fastboot mode off it.

I had previously loaded half of c128b350 and needed to load the second half via twrp. I loaded the wrong twrp (4.1) and it was stuck trying to boot it. I cannot get into fastboot without OS working. Anyway after 10 hours it finally booted the half finished b350 and I managed to get the rest from there.

@fallen_13 do you solve this problems? I've got exactly problem as you
---------- Post added at 11:21 PM ---------- Previous post was at 11:21 PM ----------
[/COLOR @fallen_13 do you solve this problems? I've got exactly problem as you

romeo_coi said:
@fallen_13 do you solve this problems? I've got exactly problem as you
---------- Post added at 11:21 PM ---------- Previous post was at 11:21 PM ----------
[/COLOR @fallen_13 do you solve this problems? I've got exactly problem as you
Click to expand...
Click to collapse
I tried my luck and sent it into service centre. Been a month and still waiting for replacement since they didn't have stock.

fallen_13 said:
I tried my luck and sent it into service centre. Been a month and still waiting for replacement since they didn't have stock.
Click to expand...
Click to collapse
Just messed up with this sh!t 3 days ago
I've tried several ways I can search on xda, 4pda and google.... but still no luck.
The dead battery trick then "Volume (-) + USB plug in to pc" seem to be useless.
According to the confirmation of member MuHuCTP23 in 4pda thread below, there is only one user was able to boot tablet to bootloader after did a "fastboot oem unlock" when in rollback process, What a lucky guy! And him doesn't know how he managed to got device into bootloader.
http://4pda.ru/forum/index.php?showtopic=780572&st=2020#entry64535878
Now I'm reading from this post:
https://forum.xda-developers.com/huawei-p9lite/help/huawei-p9-lite-vns-l31-fastboot-adb-t3590158
And other threads about the "totally bricked Huawei android phone" becasue of "flashing rollback wrong ways".
Some users confirmed the trick "3 button in cold boot": press and hold power button untill device powers off then release power button, quickly press and hold Vol (-) button and connect the usb cable (which is already attached to pc) right before or exactly when device vibrates will able to take device into bootloader mode. But it's really matter about timing when connect the usb cable to device.
So I tried this way and it actually did something difference:
When connect usb cable at "wrong time", device starts with 3 options screen instead of the no option screen. It's a little bit confuse here, there're two bootloop screens:
1- The device shows: Your device is unlock... and under this device is trying to boot direct to recovery.
2- The device shows: Your device is unlock... and there're 3 options choice as normal, but whatever we choice it'll be stucked as well as before :silly:
And when I can connect usb to device at the "right time", it doesn't startup in bootloop but the screen with red bolt alert then again it starts again in bootloop. I think it was tried to boot itself to bootloader mode but due to the low battery it only shows the red bolt alert. This thing is very weird because AFAIK even if You totally drained the battery the bootloader will always show up.
....
After 3 days continous try and try, now I'm thinking about give it up and send it to the store, my tablet is being covered under 30 days return policy. The main problem here is I bought this tab from Japan but I'm living in Vietnam, so Idk if foreign customers will be treated the same way as domestic customers or not. I email to the support and waiting for the reply .

@romeo_coi
I believe you and i went through the same steps. I spent about 3 months researching the subject before giving in and sending to service centre. My guess is that after the unsuccessful rollback, when we unlock the bootloader, the process will erase data from the tablet. But maybe some partition information had changed, so after the erase completes, the tablet becomes hard bricked instead.
Anyway, i wish you luck on the return to Japan. One thing you can try before sending back is to drain the battery fully by taping down the power button. Once that happens, you will no longer see the red bolt alert. Then you can just report as an unable to power on issue.

fallen_13 said:
@romeo_coi
I believe you and i went through the same steps. I spent about 3 months researching the subject before giving in and sending to service centre. My guess is that after the unsuccessful rollback, when we unlock the bootloader, the process will erase data from the tablet. But maybe some partition information had changed, so after the erase completes, the tablet becomes hard bricked instead.
Anyway, i wish you luck on the return to Japan. One thing you can try before sending back is to drain the battery fully by taping down the power button. Once that happens, you will no longer see the red bolt alert. Then you can just report as an unable to power on issue.
Click to expand...
Click to collapse
-I don't think after re-unlock bootloader in rollback processing, it cannot erase data because mine was stucked right after device restart without successfully boot into erase data step. May be it caused due to wrong patritions flashing then some functions not working correctly as it should. And may be with some special tools, Huawei engineers can re-write the partritions and save the device.
-And about drained the battery before contacting the supplier, I think it will no help because they can easily plug a charger into device and found that we're messed arround with system modification. So I explained to them exactly how the deivce is but in another way: after received and used device in some days for testing, then I perform a factory reset to clean it up for my own settings but the device stuck at boot screen.... Hope they accepted and return another tab for me. If not, then I have luxury paperweight
-In this case, it may be weird and hard to believe but trust me, I'm working for a large chain store system in Vietnam (smartphone cate. of course) and people in my country sometimes did something they don't even f**king know what is it. I've seen some devices with the unlocking bootloder processing hasn't done completely by previous user, and the next users are f*cked already because they will never be noticed untill they do something such as update system, unlock bootloader again.. or even just perform a factory reset. Once these processing done (luckily) completely, devices will come back to the original state and safe for use. But in some cases, these processing taking errors then devices will be bricked. I think it's the most reasonable explanation why there're more and more OEMs accepted to covered "devices with software modifications" in warranty policy.
Below is the warranty policy of the Motorola X Pure 2015 for example:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Hi there,
I was in Japan and bought BTV-W09 on 11/29 and just returned back to Canada. (Mediapad M3 is not officially available in Canada.)
And right away I upgraded to Nougat but don't like it, so down graded back to 6.0 through 2 UPDATE.APPs via dload folder method.
I found that after the down grade,the fingerprint sensor/home button not working at all.
So I tried to repeat the process of installing UPDATE.APP again. And ended up exactly the same situation as you guys.
Booting stuck at "Huawei MediaPad" + "Powered by Android" screen. Even with proper charger hooked up, the battery drains and never charge enough to do anything.
I can not force shut down, can't go into recovery or nothing. But I managed to get into some sort of recover screen. ( Press Power till the screen gets blank, then plug USB while pressing Vol-. But the recovery requires HiSuite. Since my PC is Linux and I run Win7 via VirtualBox, without sufficient battery power I can't even utilize this method.
If you guys still trying to unbrick/restore, at least you can try go into that mode by pressing Vol- immediately after pressing Power and plug in USB.
I will leave it a while to see weather the battery charges, then use some native Windows PC and HiSuite and see what happens.
If everything fails, then I have to send back to Huawei Japan for repair or use it as a paper weight!
Please let me know the current status of yours.

x52-curcuma said:
Hi there,
I was in Japan and bought BTV-W09 on 11/29 and just returned back to Canada. (Mediapad M3 is not officially available in Canada.)
And right away I upgraded to Nougat but don't like it, so down graded back to 6.0 through 2 UPDATE.APPs via dload folder method.
I found that after the down grade,the fingerprint sensor/home button not working at all.
So I tried to repeat the process of installing UPDATE.APP again. And ended up exactly the same situation as you guys.
Booting stuck at "Huawei MediaPad" + "Powered by Android" screen. Even with proper charger hooked up, the battery drains and never charge enough to do anything.
I can not force shut down, can't go into recovery or nothing. But I managed to get into some sort of recover screen. ( Press Power till the screen gets blank, then plug USB while pressing Vol-. But the recovery requires HiSuite. Since my PC is Linux and I run Win7 via VirtualBox, without sufficient battery power I can't even utilize this method.
If you guys still trying to unbrick/restore, at least you can try go into that mode by pressing Vol- immediately after pressing Power and plug in USB.
I will leave it a while to see weather the battery charges, then use some native Windows PC and HiSuite and see what happens.
If everything fails, then I have to send back to Huawei Japan for repair or use it as a paper weight!
Please let me know the current status of yours.
Click to expand...
Click to collapse
Can try power + vol up for ~3 seconds, it shuts down, then let go (timing, if you keep holding it'll go back to the loop) and it should boot to this recovery screen with 2 options, restore factory and shutdown (not fastboot or twrp). Least that's what mine does W09.

piloki said:
Can try power + vol up for ~3 seconds, it shuts down, then let go (timing, if you keep holding it'll go back to the loop) and it should boot to this recovery screen with 2 options, restore factory and shutdown (not fastboot or twrp). Least that's what mine does W09.
Click to expand...
Click to collapse
Didn't work for me. It does not charge enough. Auto shut down after about 5 min. stuck at boot then shut down for 3~4 min. of charging, and repeating forever. Just before finishing this charging, press Vol up + USB plug-in takes me into Fastboot & Rescue mode. Seems like it is missing eRecovery. Anyways, it doesn't connect to HiSuite running on native Win7 as it does not give me the required non-debugging mode connection.
Later I will try flash eRecovery image via fastboot. Most likely it will not work though without USB-Debugging on.

Okay, fastboot does not work. I can send BOOT.img, RECOVERY.img etc to W09, but can not write them into it due to lack of debugging. When getting into fastboot & rescue mode it also shows the link for rescue detail, bu the site is non-existing.
Most of the instructions EMUI/Huawei provide are useless anyway.
My remaining options are getting very little now.

I guess there is no solution to this. HiSuite's System Recovery allows you to connect W09 without debugging, but the function supports only Mediapad T2. M3 is more than a year old model but Huawei can not support it is unbelievable!
So, I gave up.

x52-curcuma said:
I guess there is no solution to this. HiSuite's System Recovery allows you to connect W09 without debugging, but the function supports only Mediapad T2. M3 is more than a year old model but Huawei can not support it is unbelievable!
So, I gave up.
Click to expand...
Click to collapse
Ah sorry to hear. You try the sd card method?

piloki said:
Ah sorry to hear. You try the sd card method?
Click to expand...
Click to collapse
Yes, I have tried that as well. Nothing works. The worst part is, aside from poor Huawei support, the battery will not charge more than a few minutes worth.