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!!!!
Related
hi everyone..
i think i bricked my phone yesterday.. after update of the radio (6.35.08.29) the phone now wont start...
the only thing i get is the htc hero boot logo (a phone with a green arrow on left side and a gray arrow on right, with the text HTC underneeth) and after some time it (about half an hour the phone turns off)
i am planning to take the phone to repair, and saying it happend during one of the htc updates..
but if someone out there could help me unbrick i would really appreciate it.
BTW, phone cant get into fastboot, HBoot and recovery mode.. i tried almost everything
heeelp me..
thx everyone i bow before the community
IstBarP said:
hi everyone..
i think i bricked my phone yesterday.. after update of the radio (6.35.08.29) the phone now wont start...
the only thing i get is the htc hero boot logo (a phone with a green arrow on left side and a gray arrow on right, with the text HTC underneeth) and after some time it (about half an hour the phone turns off)
i am planning to take the phone to repair, and saying it happend during one of the htc updates..
but if someone out there could help me unbrick i would really appreciate it.
BTW, phone cant get into fastboot, HBoot and recovery mode.. i tried almost everything
heeelp me..
thx everyone i bow before the community
Click to expand...
Click to collapse
I had almost exactly the same problem, nothing works for me. Phone keeps rebooting after HTC logo. recovery is no go.
HTC service center needs to replace the motherboard in the end.
good luck
Are you certain that you cannot even get into fastboot? Take battery out, unplug the usb cable and put the battery back in to stop it from getting stuck in a reboot cycle and then hold back and power on.
If you cannot even get into Fastboot then thats about as bricked as you can get i'm afraid.
I performed a SPL flash, the phone rebooted ,it took long time rebooting so i got panicked i pulled out the battery ( wasn't a smart move ).
tried to start the phone.. now i was stuck at the first splash screen.
-pulled out the battery and back again start the phone... stuck at the first splash screen or boot looping endlessly,
-did all possible key combinations to get in fastboot, recovery mode... nothing.
-cried for help, got directed to a post similar to mo my case... worked for me hope it dose for everyone else.
here is what i did (followed):
-On the PC, i ran the command 'fastboot boot recoveryimage.img'.
-At this point the command says 'waiting for device' (or something like that).
-I removed the battery.
-went sleep
-woke up in the morning, went back to my old duct taped SE phone
-came home in the evening
-I Connected USB.
-I inserted the battery.
-I booted the phone while holding the HOME key.
-The phone still froze at the first splash screen, but then suddenly, the waiting fastboot command detected the phone and booted the recovery image!
flashed again but this time checked all steps twice before i check them a third time, and flashed the SPL and radio and the rom.
IstBarP said:
hi everyone..
i think i bricked my phone yesterday.. after update of the radio (6.35.08.29) the phone now wont start...
the only thing i get is the htc hero boot logo (a phone with a green arrow on left side and a gray arrow on right, with the text HTC underneeth) and after some time it (about half an hour the phone turns off)
i am planning to take the phone to repair, and saying it happend during one of the htc updates..
but if someone out there could help me unbrick i would really appreciate it.
BTW, phone cant get into fastboot, HBoot and recovery mode.. i tried almost everything
heeelp me..
thx everyone i bow before the community
Click to expand...
Click to collapse
sounds like you may have not installed radio/spl in the proper order.. shouldnt be a problem if you can get into fastboot... please tell us exactly what you did, and in what order..
hey,.. sorry for the long time since last time..
i sended in my phone
i couln't get into either fastboot or nothing else.. the CMD said waiting for device when tried to fastboot while in logo..
the only thing i could get into (that booted otherwise) was the action + power
i first updated followed a toturial where i updated my phone.. first spl, then radio, and then recovery img..
but since i read about people having probs with a radio where the phone boots but after a 4 secs restart i installed a new radio and thats where the probs started happening.. and then i could not get past the boot logo..
thx for the many answers and sorry i first come back now to see ..
if they cant fix my phone i will try follow ur guide Ch3w
BTW
as soon as i get my phone back i am up for another go i think..
i got a sapphire 32a.. can anyone give a link to a good tutorial?
thx
From my limited knowledge, u are always supposed to update radio first then spl then recovery.
http://forum.xda-developers.com/showthread.php?t=605239
yeah
achillies400 said:
From my limited knowledge, u are always supposed to update radio first then spl then recovery.
Click to expand...
Click to collapse
I followed that exact one.. but when the 6.35.10.18 failed (kept reboot every 3-5 sec) i decided to install the 6.35.08.29 instead and thats where it failed.. :/
THIS! NOW! COME ON!
This is my problem also! Please help me to un-brick.
As I saw on youtube, it's a 'semi-brick'.
It's not a brick if you can go into fastboot.
Riffbox unbrick
Sent from my HTC Desire using XDA App
Sorry to hear mate, hope it gets fixed. Don't really have any helpful suggestions for the un-bricking part, but next time upgrading radio etc., I'd suggest using Eyegor's radio switcher. Although if you sent it to the dealer, you'll probably have to re-root if they fixed it (but I know, that you know how to do that, you helped me in my early days )
I'll keep my fingers crossed!
Try this. i tried and it worked for me. press the power button and home together and push the battery in at that time. it would take you to recovery .
Ok, the guy I sent it to, couldn't make something, so the phone will return to me, possibly tomorrow.
rensenin said:
Try this. i tried and it worked for me. press the power button and home together and push the battery in at that time. it would take you to recovery .
Click to expand...
Click to collapse
It didn't work :\
Hi i had the same prblem with mine ,, push power when you see the Htc logo push the Back button and hold it there until you get in to Fastboot ,, worked for me
Whiskas2009 said:
Hi i had the same prblem with mine ,, push power when you see the Htc logo push the Back button and hold it there until you get in to Fastboot ,, worked for me
Click to expand...
Click to collapse
Didn't work for me.
I'm also stuck after flashing Radio update....
Now i got 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"
}
And now nothing else shows up. Not fastboot, not recovery, nothing. Just this damn icon.
Ideas?
Phk said:
I'm also stuck after flashing Radio update....
Now i got this:
And now nothing else shows up. Not fastboot, not recovery, nothing. Just this damn icon.
Ideas?
Click to expand...
Click to collapse
try installing a normal RUU .. that should do it .. depends on your computer some times finding the phone though..
this thread died more than a half year ago when i created it :/.. in the end I send my phone to the repair shop
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!!!
Hey guys, long time lurker. I've never needed to post before but this is beyond me. Flashed JK's new hybrid rom, following his post exactly:
https://forum.xda-developers.com/verizon-s7-edge/development/rom-t3569416
It rebooted into aroma, ran, and on reboot showed the samsung lock screen, flashed a few times and now says "recovery booting". It's been trying to "boot" recovery for a day now. Flashes the blue text on and off. I've tried the button presses as much as I can to get it into download mode. It will stop flashing when I press Home+Down Vol, but upon release it comes back flashing again. Nothing seems to work, and it never connects to the PC to try Odin or any ADB method of rebooting/forcing download mode. Maybe I can try to drain the battery and go from there? Although that may take days at this point..
Just trying to avoid going to big red at this point.
Thanks!
nightwolf0829 said:
Hey guys, long time lurker. I've never needed to post before but this is beyond me. Flashed JK's new hybrid rom, following his post exactly:
https://forum.xda-developers.com/verizon-s7-edge/development/rom-t3569416
It rebooted into aroma, ran, and on reboot showed the samsung lock screen, flashed a few times and now says "recovery booting". It's been trying to "boot" recovery for a day now. Flashes the blue text on and off. I've tried the button presses as much as I can to get it into download mode. It will stop flashing when I press Home+Down Vol, but upon release it comes back flashing again. Nothing seems to work, and it never connects to the PC to try Odin or any ADB method of rebooting/forcing download mode. Maybe I can try to drain the battery and go from there? Although that may take days at this point..
Just trying to avoid going to big red at this point.
Thanks!
Click to expand...
Click to collapse
first of all were you trying this with a non verizon phone and did you use firmware in my OP or were you trying to flash verizon firmware. Hold Volume Key Down PWR Button and Home Key you have to press all three this take you to download mode reflash eng boot.img with odin then start over. If that dont work flash full firmware in Odin
jrkruse said:
first of all were you trying this with a non verizon phone and did you use firmware in my OP or were you trying to flash verizon firmware. Hold Volume Key Down PWR Button and Home Key you have to press all three this take you to download mode reflash eng boot.img with odin then start over. If that dont work flash full firmware in Odin
Click to expand...
Click to collapse
Hey jrkruse, I've got the Verizon branded S7 Edge. (bought in store.). I was using everything listed in your OP and made sure I got everything correct (the FlashFire settings and sequence as well). I've been running your roms+tweaks forever now, and was previously running the "Echoe" rom rooted and running well enough. (I think I've been using your stuff since my S3/S5 days a long time ago. Never had any issues following your methods until now. )
This exact setup/rom is what I was coming from:
https://forum.xda-developers.com/ve...t/g935-g930-echoerom-multicarrierusa-t3458535
The problem is the phone doesn't respond any key inputs. I've tried everything I can find for the key presses, and it always goes back to "Starting recovery..." text on a black screen. I let it just go for the entire day, and now that the battery is drained I do get an icon to plug it into the charger (so maybe it's not bricked totally yet?). As soon as I try to plug it in it tries to start the "Recovery" boot again without accepting my button inputs. ADB also still doesn't see the phone at all. I assume that some part of the BL is corrupt and it's stuck trying to start it still.. Is there a key press that I can do WHILE plugging it into the usb of my PC or charger to force download mode no matter what? (Like the HTC and maybe the s3 had?). I get the feeling my issue is just because I can't do a full "battery pull" with the soft keys anymore, so it never actually restarts the actual BL and all.
Would some pictures help explain?
Thanks again for all your work!
Here are a couple of pictures to explain a bit more:
The "Booting Recovery.." text that flashes briefly:
{
"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"
}
The "Charge your phone" picture I get once it's too low on battery:
nightwolf0829 said:
Here are a couple of pictures to explain a bit more:
The "Booting Recovery.." text that flashes briefly:

The "Charge your phone" picture I get once it's too low on battery:
The "Charge your phone" picture I get once it's too low on battery:

Click to expand...
Click to collapse
Pull your sim and sdcard out. Hold the volume down home and power button while phone is dead then plug in while holding those three
Tried that, still doesn't do anything it seems. The second I let go of home, it tried recovery again. Maybe it's just not fully dead somehow? I make-shifted a zip-tie to make the 'No Power, plug in' flash until it -should- be an otherwise dead phone. Am I right in thinking it should be a brick after this, and plugging in 'should' allow me to use Home,Pwr,and Vol Down to get into Odin mode?
Like suffocating your pc,maybe there is a better way to drain the battery all the way?:
Thanks again!
nightwolf0829 said:
Tried that, still doesn't do anything it seems. The second I let go of home, it tried recovery again. Maybe it's just not fully dead somehow? I make-shifted a zip-tie to make the 'No Power, plug in' flash until it -should- be an otherwise dead phone. Am I right in thinking it should be a brick after this, and plugging in 'should' allow me to use Home,Pwr,and Vol Down to get into Odin mode?
Like suffocating your pc,maybe there is a better way to drain the battery all the way?:
Thanks again!
Click to expand...
Click to collapse
Have you tried holding Volume UP + HOME +PWR
That just brings the "Booting Recovery..." flashing again... I also noticed it also doesn't vibrate at all, like they normally do on a startup. The "bzz" letting you know you can let go of PWR doesn't seem to happen ever either.
nightwolf0829 said:
That just brings the "Booting Recovery..." flashing again... I also noticed it also doesn't vibrate at all, like they normally do on a startup. The "bzz" letting you know you can let go of PWR doesn't seem to happen ever either.
Click to expand...
Click to collapse
Give me a run down on what happened during flash. Including firmware you were on etc. Maybe I can at least keep this from happening too someone else
---------- Post added at 08:41 PM ---------- Previous post was at 08:36 PM ----------
I'm thinking flashfire must have failed in flashing the bootloaders
Makes sense, so this is actually a brick I suppose?
S7 was running your Echoe Rom Port (the AROMA_Version 1.5, as in the OP of that thread.) No updates or changes other than updates to FlashFire and installed apps. Was previously a MM rooted phone before flashing the Echoe Rom. Ran the engineering boot setup from early 2017 (if there are any differences, I can only find the one root method). Sorry I cant open my FlashFire backup in order to check the versions of my BL/Firmware/Modem/etc. I can post the zip somewhere and send you if if there is a way to extract my software versions?
Followed your exact setup to Flash over to your TMO Hybrid rom as in your OP of this thread:
https://forum.xda-developers.com/verizon-s7-edge/development/rom-t3569416
I made sure to have the installs in the correct order and check all of the folders (and uncheck injection of SuperSU).
Phone rebooted up to the "Samsung S7" white unlock logo a couple of times, then rebooted into the "Recovery booting..." loop.
Side note, would the 300 Ohm USB dongle trick possibly work in this case? Or is the BL probably gone/corrupt and I'm fully bricked?
Thanks!
nightwolf0829 said:
Makes sense, so this is actually a brick I suppose?
S7 was running your Echoe Rom Port (the AROMA_Version 1.5, as in the OP of that thread.) No updates or changes other than updates to FlashFire and installed apps. Was previously a MM rooted phone before flashing the Echoe Rom. Ran the engineering boot setup from early 2017 (if there are any differences, I can only find the one root method). Sorry I cant open my FlashFire backup in order to check the versions of my BL/Firmware/Modem/etc. I can post the zip somewhere and send you if if there is a way to extract my software versions?
Followed your exact setup to Flash over to your TMO Hybrid rom as in your OP of this thread:
https://forum.xda-developers.com/verizon-s7-edge/development/rom-t3569416
I made sure to have the installs in the correct order and check all of the folders (and uncheck injection of SuperSU).
Phone rebooted up to the "Samsung S7" white unlock logo a couple of times, then rebooted into the "Recovery booting..." loop.
Side note, would the 300 Ohm USB dongle trick possibly work in this case? Or is the BL probably gone/corrupt and I'm fully bricked?
Thanks!
Click to expand...
Click to collapse
In settings in Flashfire did you check allow flashing bootloader then when you added the zip did you check to mount system
Not that this helps, but my galaxy tab 4 did something similar.
Installed the update firmware in Odin, rebooted, and it didn't get past the Samsung splash screen. Next reboot, exactly what you said... recovery rebooting after that.
The recovery was gone, but I could boot into download mode that gave me an error stating to use kies to install the firmware. Kies wouldn't recognize the device. Any flash attempt of os systems in Odin resulted in fails.
My issue was that the system partition got completely erased and set to 0. Therefore, it had no space to install anything.
Next, I flashed a stock recovery, but had the error on writing system due to the partition corruption. I had to flash twrp and change the system partition from 0 to whatever it should have been. After that, I could Odin firmware and was back in business.
Long story short, this probably doesn't help because we can't flash recoveries, but I wonder if your system partition got corrupted?
Sent from my SM-G930P using XDA-Developers Legacy app
jrkruse said:
In settings in Flashfire did you check allow flashing bootloader then when you added the zip did you check to mount system
Click to expand...
Click to collapse
Pretty sure I did, but I'm honestly unsure at this point. I tried following your post exactly, as always, but it is possible I skipped that step. I really don't think so as I checked it all multiple times.
Sorry I can't recall better.
Does this change any options I may of had for recovery? I'm sure it's super unlikely to repair at this point as Odin, and Windoze never sees the device at any point of any restart. I also opened it up and manually disconnected the battery just-in-case, as I figured it wasn't actually turning off. Still the same, wont boot into Download mode, Recovery just displays the blue booting text.
Let me know if anything I can get from the phone would help before I try to get it replaced one way or another.
lvpre said:
Not that this helps, but my galaxy tab 4 did something similar.
Installed the update firmware in Odin, rebooted, and it didn't get past the Samsung splash screen. Next reboot, exactly what you said... recovery rebooting after that.
The recovery was gone, but I could boot into download mode that gave me an error stating to use kies to install the firmware. Kies wouldn't recognize the device. Any flash attempt of os systems in Odin resulted in fails.
My issue was that the system partition got completely erased and set to 0. Therefore, it had no space to install anything.
Next, I flashed a stock recovery, but had the error on writing system due to the partition corruption. I had to flash twrp and change the system partition from 0 to whatever it should have been. After that, I could Odin firmware and was back in business.
Long story short, this probably doesn't help because we can't flash recoveries, but I wonder if your system partition got corrupted?
Sent from my SM-G930P using XDA-Developers Legacy app
Click to expand...
Click to collapse
I totally think something low-level is corrupt/gone. I bet it's the BL just based on the fact it shows only a black screen when I do the key press. I'm betting it's a brick, but I'm waiting to make sure jrkruse has anything he needs to stop this happening to anyone else before I try to replace it.
nightwolf0829 said:
I totally think something low-level is corrupt/gone. I bet it's the BL just based on the fact it shows only a black screen when I do the key press. I'm betting it's a brick, but I'm waiting to make sure jrkruse has anything he needs to stop this happening to anyone else before I try to replace it.
Click to expand...
Click to collapse
I put a warning and a work around in my thread
---------- Post added at 10:45 PM ---------- Previous post was at 10:43 PM ----------
nightwolf0829 said:
Pretty sure I did, but I'm honestly unsure at this point. I tried following your post exactly, as always, but it is possible I skipped that step. I really don't think so as I checked it all multiple times.
Sorry I can't recall better.
Does this change any options I may of had for recovery? I'm sure it's super unlikely to repair at this point as Odin, and Windoze never sees the device at any point of any restart. I also opened it up and manually disconnected the battery just-in-case, as I figured it wasn't actually turning off. Still the same, wont boot into Download mode, Recovery just displays the blue booting text.
Let me know if anything I can get from the phone would help before I try to get it replaced one way or another.
Click to expand...
Click to collapse
Tell big red that the nougat update fried your phone. Hopefully they will replace. Keep me updated
jrkruse said:
I put a warning and a work around in my thread
---------- Post added at 10:45 PM ---------- Previous post was at 10:43 PM ----------
Tell big red that the nougat update fried your phone. Hopefully they will replace. Keep me updated
Click to expand...
Click to collapse
Will do! Thanks again! Hope my phone was just a fluke thing.
nightwolf0829 said:
Makes sense, so this is actually a brick I suppose?
S7 was running your Echoe Rom Port (the AROMA_Version 1.5, as in the OP of that thread.) No updates or changes other than updates to FlashFire and installed apps. Was previously a MM rooted phone before flashing the Echoe Rom. Ran the engineering boot setup from early 2017 (if there are any differences, I can only find the one root method). Sorry I cant open my FlashFire backup in order to check the versions of my BL/Firmware/Modem/etc. I can post the zip somewhere and send you if if there is a way to extract my software versions?
Followed your exact setup to Flash over to your TMO Hybrid rom as in your OP of this thread:
https://forum.xda-developers.com/verizon-s7-edge/development/rom-t3569416
I made sure to have the installs in the correct order and check all of the folders (and uncheck injection of SuperSU).
Phone rebooted up to the "Samsung S7" white unlock logo a couple of times, then rebooted into the "Recovery booting..." loop.
Side note, would the 300 Ohm USB dongle trick possibly work in this case? Or is the BL probably gone/corrupt and I'm fully bricked?
Thanks!
Click to expand...
Click to collapse
Which version of his Hybrid ROM did you install?
I don't recall if the USB dongle is compatible with the S7, but I have one laying around and will see if it works on the S7.
You are using an S7 Edge, not a flat, right?
I can confirm that the USB jig does not work on my S7 flat.
Try holding down power, BOTH volume and and down and the home key. all at the same time.. dont release any buttons... just wait about 8-10 seconds... that brings up a different boot option screen. (reboot normal, safe boot. wipe
... I was under the impression I could flash the Hybrid mode running any rom if I was rooted and had flashfire.. I tried flashing Hybrid rom running Stang rom.. and also encountered boot loop.. and above it how I stopped the bootloop. Good luck and hope this works for you also.
ronschuck said:
Try holding down power, BOTH volume and and down and the home key. all at the same time.. dont release any buttons... just wait about 8-10 seconds... that brings up a different boot option screen. (reboot normal, safe boot. wipe
... I was under the impression I could flash the Hybrid mode running any rom if I was rooted and had flashfire.. I tried flashing Hybrid rom running Stang rom.. and also encountered boot loop.. and above it how I stopped the bootloop. Good luck and hope this works for you also.
Click to expand...
Click to collapse
Hey thanks for trying but I tried everything on that phone. Had to go to big red and get a replacement. Luckily they got me one without having to go through Assurion.
Had been rooted my phone before, didn't like it because I couldn't use my banking apps. Back to official firmware via Kies, been using for few months... no problem until yesterday. I charged my phone up to 92%, I unplugged and unlocked my phone, it restarted itself then never come back live again.
I used Smart Switch for another stock firmware flashing with no luck. The software skipped downloading from 85% to 100% immediately, it was ok installing system update on Smart Switch but when the phone completed and restarted, on the screen it shown "erasing" and "installing system up to 32%", it won't get pass above 32% except a blue dead android with loading icon, it freezes every time.
Full Album here, so you might get some ideas of what's going on...
http://imgur.com/a/Ad6dV
{
"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"
}
I went to Samsung store yesterday, however once they see knox has been tripped, they refused to fix my phone unless I pay for a new motherboard which will cost me £220. :crying:
I have been trying to flash any official firmware using both Smart Switch, Samsung Kies and Odin, Android 6.0 or 7.0 and every tools lead to blue led black screen or boot looping. I have tried at least 10 times of each methods, even ADB mode, but ADB won't offer much choices except 'adb sideload' commands but it verify each package. So I cannot install TWRP recovery and so on... Odin won't install TWRP recovery as well, it failed every time.
It is sad to see this phone die on me. I have never dropped this phone and it has 0 scratch on it... still looks brand new! If anyone of you could help me out getting this baby alive, I could pay you little money.
Thanks for your time!
lovetv said:
Had been rooted my phone before, didn't like it because I couldn't use my banking apps. Back to official firmware via Kies, been using for few months... no problem until yesterday. I charged my phone up to 92%, I unplugged and unlocked my phone, it restarted itself then never come back live again.
I used Smart Switch for another stock firmware flashing with no luck. The software skipped downloading from 85% to 100% immediately, it was ok installing system update on Smart Switch but when the phone completed and restarted, on the screen it shown "erasing" and "installing system up to 32%", it won't get pass above 32% except a blue dead android with loading icon, it freezes every time.
Full Album here, so you might get some ideas of what's going on...
http://imgur.com/a/Ad6dV
I went to Samsung store yesterday, however once they see knox has been tripped, they refused to fix my phone unless I pay for a new motherboard which will cost me £220. :crying:
I have been trying to flash any official firmware using both Smart Switch, Samsung Kies and Odin, Android 6.0 or 7.0 and every tools lead to blue led black screen or boot looping. I have tried at least 10 times of each methods, even ADB mode, but ADB won't offer much choices except 'adb sideload' commands but it verify each package. So I cannot install TWRP recovery and so on... Odin won't install TWRP recovery as well, it failed every time.
It is sad to see this phone die on me. I have never dropped this phone and it has 0 scratch on it... still looks brand new! If anyone of you could help me out getting this baby alive, I could pay you little money.
Thanks for your time!
Click to expand...
Click to collapse
Take a look here https://forum.xda-developers.com/s7-edge/help/s7-edge-bug-t3331878/page12
post #114
mrsmtt said:
Take a look here https://forum.xda-developers.com/s7-edge/help/s7-edge-bug-t3331878/page12
post #114
Click to expand...
Click to collapse
I've tried this solution more than 10 times with no luck
Have you tried flashing the boot.img recovery.img ect separately? I had this kind of thing on a different Samsung and i fixed it by flashing each one separate.
Clarkiieh said:
Have you tried flashing the boot.img recovery.img ect separately? I had this kind of thing on a different Samsung and i fixed it by flashing each one separate.
Click to expand...
Click to collapse
That's good idea, which option should I use in Odin? Should be AP option right?
The files should work with their own options I'm not too sure which ones work with which, and there is a set order to flash in as well which I'm not sure about either.
---------- Post added at 03:47 PM ---------- Previous post was at 03:38 PM ----------
They all have their own button I think pal
What about fastboot flash?
I finally revived my phone!!! I'm so happy right now
I'll provide these solutions if anyone has the same issue like me. What I did altogether was:
1.0) Remove devices from your Google accounts (I had 2), wait for 48 hours to cool down? Although not sure if this option caused the bootloop, might be useful for someone...
1.1) Downloading the oldest firmware from https://www.sammobile.com flash it using Odin 3.11.1
1.2) Upload BL, AP, CP and CSC files, but I uploaded the correct Pit file too! WARNING: Be sure you know what you doing before trying to mess with this! Otherwise don't try pit file! Leave the options by default! Unless you ran out of choices!!! but I've ticked auto reboot, re-partition, f.reset time, nano erase all and bootloader update for my case. Then start to flash of course.
2.0) Phone were still crashing upon system update... I waited out the battery to drain up. Until next day... Tips: If there's no led light, try to sense it with your face if there's any temperature
2.1) Plugged in ur phone and see if there's the battery charging icon. If there is, you're in luck.
2.2) Charge until 100%, turn it on. Hopefully you can boot up now but I couldn't...
3.0) My phone was still in boot looping (Samsung Logo), I had to turn on recovery mode and wipe + format system then mount /system for whatever reason... then restart using the recovery mode...
3.1) At this time, I finally past through the boot loop which I'll be in the Google sign in screen!
4.0) Phone was in the oldest firmware, of course I will update the official firmware automatically, however the first update didn't make it, and stucked on Samsung logo again!
4.1) All I did was wait a little bit about (25mins) and reset again... somehow it fixed the issue and boot back in.
4.2) Then system update every single firmware up to the latest, boom! I'm on the latest firmware again and everything is up and running!
5.0) Extra tips: Make sure you have up to 60% battery life before turning on recovery mode, but I had to charge up to 100% for my case.
5.1) Remove FRP lock (google accounts, remove devices) might help?
5.2) On recovery mode, wipe cache and format system again might help too!
Good luck guys, I was about to give up trying after 20 flashes (Smart Switch, Kies, and Odin with different pc too!) and had to wait for battery to drain everytime if it stucks! Which annoys me but I made it!!
Glad you got it sorted ?
I would recommend Batman ROM if your willing to flash again.
Same happen to my Phone many times!
Solution!
After a few Reboots your Phone will stuck with screen of or may a blue led on (pulsing) or without any reaction (black screen, all led off) !
Now you have to wait until your battery will be empty compl. Can be up to 18 hours and more! depend how much your Mobile was loaded! or until Led light is off! is your phone still warm? Than it is still draining!You have to wait untill it is complet off and getting cool. Or, if u can, get it in the download mode, with sreen on it will be decharged faster! but mostly your phone will stay death.
After all that, Phone is cold and no Led is illuminated, plug your Phone to usb charging! Wait a little time until you can see the normal charging screen and orange Led is illuminated! (if charging screen will not upper, you have to wait longer!for decharging battery)
let it charge untill it is complet full! Dont touch! Wait at leasst 8 hours and more with charger still connected ! Best is overnight.
after this usely your phone will start normaly , without loosing any data!
Thats what helped me many times!
All my tries with bootloader, software brought nothing, just lots of waisted time and lost Data! you not need to del your phone at google!
Try this, it will work
Vollidiot said:
Same happen to my Phone many times!
Solution!
After a few Reboots your Phone will stuck with screen of or may a blue led on (pulsing) or without any reaction (black screen, all led off) !
Now you have to wait until your battery will be empty compl. Can be up to 18 hours and more! depend how much your Mobile was loaded! or until Led light is off! is your phone still warm? Than it is still draining!You have to wait untill it is complet off and getting cool. Or, if u can, get it in the download mode, with sreen on it will be decharged faster! but mostly your phone will stay death.
After all that, Phone is cold and no Led is illuminated, plug your Phone to usb charging! Wait a little time until you can see the normal charging screen and orange Led is illuminated! (if charging screen will not upper, you have to wait longer!for decharging battery)
let it charge untill it is complet full! Dont touch! Wait at leasst 8 hours and more with charger still connected ! Best is overnight.
after this usely your phone will start normaly , without loosing any data!
Thats what helped me many times!
All my tries with bootloader, software brought nothing, just lots of waisted time and lost Data! you not need to del your phone at google!
Try this, it will work
Click to expand...
Click to collapse
My phone turned out to be a faulty motherboard, went to Samsung support centre and they repaired for me within 3 working days. Now I got a sort of a new phone, it has 0 scratch since I bought it last year Feb, so it's like a new phone to me :laugh::good:
But yeah, motherboard was acting weird, was lasting a week then breaks again... finally motherboard was dead, so I could repair it without seeing the knox being triggered. Phew
I recently updated my Poco M3, it updated correctly but after that, it doesn't turn on anymore, I searched about it and I found that it was a problem with the update. I managed to turn on my phone again by pressing 13 seconds the power button, after that, I received a new update so I thought the update fixed that but when the phone rebooted to install the new update it doesn't turn on anymore. I've tried to enter fast boot mode but doesnt't works.
I don't know what should I do, I've tried again to hold on the power button and I also tried to enter fast boot but as I said it doesn't work. Also when I plug my phone to charge it, nothing happens
I hope someone can help me, and sorry for my bad English.
you need to drain your battery first. same happen to my poco m3. after that you need to flash your firmware or else it will happen again after you reboot.
vinzikidz said:
you need to drain your battery first. same happen to my poco m3. after that you need to flash your firmware or else it will happen again after you reboot.
Click to expand...
Click to collapse
And how can I flash the firmware? I've tried using the Xiaomi Flash tool but it asks me for a Mi account that is valid for the process.
charecktowa said:
And how can I flash the firmware? I've tried using the Xiaomi Flash tool but it asks me for a Mi account that is valid for the process.
Click to expand...
Click to collapse
unlock bootloader. install twrp. flash firmware
charecktowa said:
I recently updated my Poco M3, it updated correctly but after that, it doesn't turn on anymore, I searched about it and I found that it was a problem with the update. I managed to turn on my phone again by pressing 13 seconds the power button, after that, I received a new update so I thought the update fixed that but when the phone rebooted to install the new update it doesn't turn on anymore. I've tried to enter fast boot mode but doesnt't works.
I don't know what should I do, I've tried again to hold on the power button and I also tried to enter fast boot but as I said it doesn't work. Also when I plug my phone to charge it, nothing happens
I hope someone can help me, and sorry for my bad English.
Click to expand...
Click to collapse
Drain out your battery and then just plug the charger then wait.
I had this happen to me 2 times now,it would take days if your phone fully charged like mine,it takes 5 days.
After that,
make sure to backup your phone,unlock your bootloader and then re-flash the stock rom with Mi-Flash or just use another rom to your liking.
The truth is I like the stock MIUI than any other rom but if this kind of problem keep happening,I rather just flash another rom.
Hopes this help fixing your phone,sorry for the rant there.
Biggest problem with this phone is , there's no way to force reset the phone. I literally tried everything from vol up + power and volume down + power and everything else Buying this phone is prolly one of the biggest regret of my life. And the youtuber xiaomi slaves didnt help. But my real question is.... Will flashing custom rom fix this problem?
yankee77 said:
Biggest problem with this phone is , there's no way to force reset the phone. I literally tried everything from vol up + power and volume down + power and everything else Buying this phone is prolly one of the biggest regret of my life. And the youtuber xiaomi slaves didnt help. But my real question is.... Will flashing custom rom fix this problem?
Click to expand...
Click to collapse
Same question...i have experienced deadboot in this poco m3 4 times already...the only option is to remove the battery and put it back again...then hold power button to turn it on...no fastboot...no recovery mode...i dont have a choice but to open it and remove the battery...now...my question is...What if i flashed a custom rom...will it fix deadboot issue on this phone?
charecktowa said:
I recently updated my Poco M3, it updated correctly but after that, it doesn't turn on anymore, I searched about it and I found that it was a problem with the update. I managed to turn on my phone again by pressing 13 seconds the power button, after that, I received a new update so I thought the update fixed that but when the phone rebooted to install the new update it doesn't turn on anymore. I've tried to enter fast boot mode but doesnt't works.
I don't know what should I do, I've tried again to hold on the power button and I also tried to enter fast boot but as I said it doesn't work. Also when I plug my phone to charge it, nothing happens
I hope someone can help me, and sorry for my bad English.
Click to expand...
Click to collapse
have you try test point?
Hopefully this doesnt happen to anyone.. saw this vid on youtube. Basically poco m3 doesnt turn on even when battery connectors removed.
yankee77 said:
yankee77 said:
Hopefully this doesnt happen to anyone.. saw this vid on youtube. Basically poco m3 doesnt turn on even when battery connectors removed.
Click to expand...
Click to collapse
It did happen to me and I did pull the battery connector even pull the display connector while doing it.I read a post on reddit about it,pull the battery and display connector and then try connect it back while pushing the power button,the guy said the phone did turned on but whenever he tried to restart,phone would not boot and he would repeat that unplug,plug,hold power thinggy .I did try the method but nothing happened.Plug in to pc would only detect it as in EDL mode,with a locked bootloader theres nothing I can really do as flashing it would only met with this and that error.Then I read someone on a forum said to just let the phone fully discharged and try to plug in charger and wait for the battery empty logo pop on screen then the phone would boot as normal.It did work for me but I gone through nearly 5 days as my phone was fully charged.Its been like 4-5 days now and eventhough I already downloaded the latest ota for miui global,Im still dreading to install it as Im afraid the same problem would occurs again.Maybe I should unlock my bootloader first so the next time my phone goes EDL mode again,things would get easier to do.Sorry if this rants of mine a bit too long.
Click to expand...
Click to collapse
i did a factory reset.... but the phone didnt turned back on. i did do the ota update three times prior to this one which failed three times. .. the first one prolly broke the recovery and fastboot mode ... im not sure what to do after this. since i cant go to recovery or fastboot mode. this is prolly the first time i experienced this. where the ota itself which is supposed to make the phone better broke the phone. it will prolly turn on after it got drained but im not sure how to update firmware without recovery or fastboot and yes this is a ****ty phone and company alright. i send my logs to xiaomi. and still no response from them.
tnx sa share boss malaking tulong
when i heat ( about 3 to 5 sec. or more with soldering iron and flux) camera power ic under ( Power Control IC PMI632-902 ) the phone boots up
HCBE AKD written on this ic
in some other m3 phones that text is different
it has 4*3 pin under lower left side of shield
phone boots up with this method one time
if you use flux phone will be good till 1 hour power off then problem comes back
i neeeeeed schematic diagram of this phone's motherboard...
in some cases when you unplug battery
then short circuit with power key
then plug pc usb till flashing screen
after that i connect battery with holding down power key and usb connected
phone powers on from edl mode to normal mode (in some cases lcd flashes in some other battery icon shows rapidly and gets off)
ow in cit mode #27-charger test some phones we have red text battery test fail insted blue text that ask reverse plug usb type c connection)
is there another test or somting else???
{
"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"
}
does the phone go to fastboot with adb
Any update on this?
I have this same problem
How can I drain the batter ?
vinzikidz said:
you need to drain your battery first. same happen to my poco m3. after that you need to flash your firmware or else it will happen again after you reboot.
Click to expand...
Click to collapse
after you reflashed, did you encounter the same problems again?
pidliget said:
does the phone go to fastboot with adb
Click to expand...
Click to collapse
no just edl mode
phone current in charge is about 100 mAmp
if you heat motherboard phone turns on get charge normally and every thing is ok till you get reboot or turn phone off
vinzikidz said:
you need to drain your battery first. same happen to my poco m3. after that you need to flash your firmware or else it will happen again after you reboot.
Click to expand...
Click to collapse
How do I drain the battery
ArcherXY said:
How do I drain the battery
Click to expand...
Click to collapse
Poco m3 drains battery by itself. General rule of the thumb
1-10% - 0 to 1 day
11-20% - 2 days
Basically 1 day is around 10% of battery
I think the motherboard is on but for some odd reason the display board and basically the whole thing doesnt turn on on. But it still is draining battery even when turned off. Removing the battery doesnt fix it. I tried several times