Related
so i have a stock rooted a500 i got yesterday new.
have a problem..
10 minutes ago i was setting a wallpaper to a picture of my car. i cropped and set..wallpaper stayed black, so i did it again, still black. so i tried a different picture.
Crash
restarted, now stuck at lock screen, lock button doesnt slide, once you shut screen off, wont turn back on. clock doesnt move either. help?
Snag a paperclip
Hit that reset button.
Failing that, i'm at a loss. Never had anything remotely similar happen.
entropy.of.avarice said:
Hit that reset button.
Failing that, i'm at a loss. Never had anything remotely similar happen.
Click to expand...
Click to collapse
niether have i, i have a custom evo. reset button only restarts it
i didnt flash recovery yet, though i can access the files via usb when its locked at lock screen, so im going to try adb push
Good move
Or you can always toss a full stock ROM image on microSD and flash without custom recovery.
entropy.of.avarice said:
Or you can always toss a full stock ROM image on microSD and flash without custom recovery.
Click to expand...
Click to collapse
ok, adb sees no devices, so ill have to do it that way
where can i find a stock full rom for USA? seems full package links are dead
skullzaflare said:
where can i find a stock full rom for USA? seems full package links are dead
Click to expand...
Click to collapse
Not sure - never done any full package flashes, only update packages. Pretty sure I've seen a bunch of them around these fourms.
Best of luck - hope you don't have a dead tab.
entropy.of.avarice said:
Not sure - never done any full package flashes, only update packages. Pretty sure I've seen a bunch of them around these fourms.
Best of luck - hope you don't have a dead tab.
Click to expand...
Click to collapse
so far it seems i do, tried a update, and still does the same thing
it would be fine if i didnt have a custom boost animation in the system/media
i still have 12 more days warrenty.
is there a way to delete it via computer?
not sure if anyone knew about the hard reset, i contacted acer and played dumb, though i told them what happened.
i was instructed to
Power down the device
hold Vol Up + Power for 3 sec
continue holding Vol up, and keep switch the screen lock back and forth until "erasing cache" comes up on the acer screen
at which point you stop and let it run its course.
said it would take 30 minutes. i fell asleep, 2hrs later i checked it, still same. recontacted acer, another tech said to do the default hard restart with the push pin
worked like a charm
in process of rooting, installing CWM and making backup lol
skullzaflare said:
not sure if anyone knew about the hard reset, i contacted acer and played dumb, though i told them what happened.
i was instructed to
Power down the device
hold Vol Up + Power for 3 sec
continue holding Vol up, and keep switch the screen lock back and forth until "erasing cache" comes up on the acer screen
at which point you stop and let it run its course.
said it would take 30 minutes. i fell asleep, 2hrs later i checked it, still same. recontacted acer, another tech said to do the default hard restart with the push pin
worked like a charm
in process of rooting, installing CWM and making backup lol
Click to expand...
Click to collapse
Hello ,
Did have the same problem and solved it by flashing the update.zip found on this site.
I've put it on the root of the SD card , push start and holding vol down , and then perform the update .
Can you explain me tough what you men by " do the default hard restart with the push pin " .
Thanks
BerreZ said:
Hello ,
Did have the same problem and solved it by flashing the update.zip found on this site.
I've put it on the root of the SD card , push start and holding vol down , and then perform the update .
Can you explain me tough what you men by " do the default hard restart with the push pin " .
Thanks
Click to expand...
Click to collapse
the reboot is for if it stops responding, like a reset button on a computer. its under the usb port
flashing any update zip didnt work for me
skullzaflare said:
flashing any update zip didnt work for me
Click to expand...
Click to collapse
Did you get it from a local retail location? If so, I would just march back there with my receipt and not give too many details - i was working on a picture and it broke and I have no idea what is wrong, etc - they should just give you a new one.
Have you tried clearing the cache? There is a combo with holding power / volume up when booting and using the rotation lock switch, not quite sure how it is done but i think you just hold both and flip the switch like mad - totally sure I have seen the process posted here somewhere.
If you got it via online order, you still should be able to just return it.
Or call acer - they might be able to work some magic.
Best of luck, hope you get it going or at least get a new one. Really sounds like you have a defective unit, I rooted mine the day after I bought it, have had it for nearly two months and multiple rootings/unrootings/rom flashes and have had no issues at all.
My G2 suddenly just stopped working yesterday. When I try to power it on the phone either freezes shortly after the boot screen, gets to the homescreen then shuts off, or boots to an all blue screen. I can access TWRP but haven't been able to fix it with anything I've found. My pc isn't recognizing the phone so don't know if I can flash another rom. Also tried factory reset with no luck. Any help please this is driving me crazy!!!
The same thing just happened to me! Someone please help us! IS there a solution to this?
dsljk2009 said:
My G2 suddenly just stopped working yesterday. When I try to power it on the phone either freezes shortly after the boot screen, gets to the homescreen then shuts off, or boots to an all blue screen. I can access TWRP but haven't been able to fix it with anything I've found. My pc isn't recognizing the phone so don't know if I can flash another rom. Also tried factory reset with no luck. Any help please this is driving me crazy!!!
Click to expand...
Click to collapse
colbyrainey said:
The same thing just happened to me! Someone please help us! IS there a solution to this?
Click to expand...
Click to collapse
Ok, since there is little to no information out there I thought I would share how I created and fixed this problem.
I received a new phone under warranty because of a failing sim card reader. Naturally, the first thing I did once I received it was root it. Next, I thought I would be slick and use flashify to flash a custom recovery (TWRP). Little did I know, with the new version of Android, our phones have a locked bootloader. I freaked out when I saw some weird error messages about it and tried to power off the device in the middle of it booting. BIG MISTAKE. In hindsight, I am assuming that it was re-flashing the factory recovery when I powered it off.
It gave me a solid blue screen for two hours, unless I held the power button for 10 seconds, which would just repeat the process from black screen to solid blue screen repeatedly. I tried to reboot into recovery for 2 hours by holding volume down and power. 2 HOURS!
At that point, I realized that I may have some luck getting it into download mode by powering it off, then powering it on with volume up and power and plugging in a USB cable. VOILA! It booted up normally (somehow) and I got it running the OS.
After that, I made sure that I did a factory reset by reverting to stock using the LG Software Upgrade tool.
The moral of this story is, if you are going to try to install a custom recovery on 4.4.2, make sure you know what you're doing. It turns out an app called AutoRec did the trick for me.
dsljk2009 - I hope this message helps you, or anyone else who may think they've bricked their phones.
CHEERS LADS!
If this post helped you be sure to hit thanks!
colbyrainey said:
Ok, since there is little to no information out there I thought I would share how I created and fixed this problem.
I received a new phone under warranty because of a failing sim card reader. Naturally, the first thing I did once I received it was root it. Next, I thought I would be slick and use flashify to flash a custom recovery (TWRP). Little did I know, with the new version of Android, our phones have a locked bootloader. I freaked out when I saw some weird error messages about it and tried to power off the device in the middle of it booting. BIG MISTAKE. In hindsight, I am assuming that it was re-flashing the factory recovery when I powered it off.
It gave me a solid blue screen for two hours, unless I held the power button for 10 seconds, which would just repeat the process from black screen to solid blue screen repeatedly. I tried to reboot into recovery for 2 hours by holding volume down and power. 2 HOURS!
At that point, I realized that I may have some luck getting it into download mode by powering it off, then powering it on with volume up and power and plugging in a USB cable. VOILA! It booted up normally (somehow) and I got it running the OS.
After that, I made sure that I did a factory reset by reverting to stock using the LG Software Upgrade tool.
The moral of this story is, if you are going to try to install a custom recovery on 4.4.2, make sure you know what you're doing. It turns out an app called AutoRec did the trick for me.
dsljk2009 - I hope this message helps you, or anyone else who may think they've bricked their phones.
CHEERS LADS!
If this post helped you be sure to hit thanks!
Click to expand...
Click to collapse
Hey,
How did you power off your G2 before putting it into download mode? Im experiencing the same problem.
Please assist me.
jocyrus said:
Hey,
How did you power off your G2 before putting it into download mode? Im experiencing the same problem.
Please assist me.
Click to expand...
Click to collapse
I didn't get the blue screen but I kept getting the security error screen on my d802. To turn it off, I kept holding down the power button for about 10 seconds after the screen went blank. This caused the phone to remain powered off. After that, I was able to boot into download mode. Maybe this method will work for your phone.
audit13 said:
I didn't get the blue screen but I kept getting the security error screen on my d802. To turn it off, I kept holding down the power button for about 10 seconds after the screen went blank. This caused the phone to remain powered off. After that, I was able to boot into download mode. Maybe this method will work for your phone.
Click to expand...
Click to collapse
It didn't work. Any other suggestions? :|
jocyrus said:
It didn't work. Any other suggestions? :|
Click to expand...
Click to collapse
Don't know of any other methods because holding down the power button got the phone to turn off and allow me to get into download mode. From download mode, I was able to restore a stock 5.01 ROM to my phone via LG Mobile Support Tools.
LG G2 Bluescreen then no boot after disconnecting battery
Found my LG G2 with a completely blue screen. It would not turn off. Took it apart and disconnected the battery. Reconnected the battery and there was only a blank black screen and the phone would not boot. Zilch. Even with pressing the power button with the volume down to boot into recovery.....still zilch.
I sucessfully got my phone to work again using a hair dryer trick on an LG G3, which I found here.
1. I took the back off the phone, disconnected the battery, and removed the SIM card.
2. I then used a hairdryer on high heat and blew the heat over the uncovered areas for 10 minutes.
3. I let the phone from hot to warm, reconnected the battery and put it all back together with the SIM card replaced.
4. I booted into recovery and restored a TWRP backup, and my LG G2 is working like a champ again.
Hey Guys,
I have a dead phone(kind of). All it displays is
"Have been in Factory Mode. long press power button and Normal boot"
And in very tiny font, there is a line saying
"=>Tool DL Image Load Fail!"
This stays for a few seconds then it turns off, and repeat, again the same this comes up on the screen.
What I have tried:
1) Flash the stock ROM using SP Flash Tools several times
2) Cleaned the power button from the inside a bit, because some thread said there might be a sticky button.
Flashing with SP Flash Tools shows that the flash is successful, but it didn't help.
EDIT: Now it displays something as "eFuse blow: Success". Damn!
PraneethMv said:
Hey Guys,
I have a dead phone(kind of). All it displays is
"Have been in Factory Mode. long press power button and Normal boot"
And in very tiny font, there is a line saying
"=>Tool DL Image Load Fail!"
This stays for a few seconds then it turns off, and repeat, again the same this comes up on the screen.
What I have tried:
1) Flash the stock ROM using SP Flash Tools several times
2) Cleaned the power button from the inside a bit, because some thread said there might be a sticky button.
Flashing with SP Flash Tools shows that the flash is successful, but it didn't help.
EDIT: Now it displays something as "eFuse blow: Success". Damn!
Click to expand...
Click to collapse
Have you set it to format all in sp?
Try it maybe it will work
If didnt i think its hardware issue
crazylife said:
Have you set it to format all in sp?
Try it maybe it will work
If didnt i think its hardware issue
Click to expand...
Click to collapse
Hey, Thank you for replying.
Have tried that method, its just the same thing, but now it is not displaying that tiny line.
Now it goes into the factory mode and shows some options in Chinese. And it stays there till i select something.
The last option, i know is "Reboot To Phone" (Via Google Translate).
When i select that option it goes back into the Factory mode again.
Can you flash twrp and boot in to recovery...May be..And then do something from there?:
sandeep101 said:
Can you flash twrp and boot in to recovery...May be..And then do something from there?:
Click to expand...
Click to collapse
Tried to flash TWRP through SP, it returns an error:
ERROR: S_SECURITY_SECURE_USB_DL_IMAGE_SIGN_HEADER_NOT_FOUND(6045)
MSP ERROR CODE:0x00.
Make sure volume + button is not pressed.
During boot can you boot in to stock recovery,
press POWER BUTTON + VOLUME UP + VOLUME DOWN until Lenovo logo appear, then continue press VOLUME UP + VOLUME DOWN
Thanks all. I somehow got it to work... and now my phone is all good.
As crazylife told, there was some hardware issue. Apparently, there was a tini-tiny bit of a circuit which, due to water allegedly, got short. I had it cleaned by some local phone shop.( He also claimed that the phone work anyway ,though). After that i flashed the stock rom, and it worked.
And btw, how do i mark the thread solved?
Hi, even I'm stuck with the same problem.
PraneethMv said:
Thanks all. I somehow got it to work... and now my phone is all good.
As crazylife told, there was some hardware issue. Apparently, there was a tini-tiny bit of a circuit which, due to water allegedly, got short. I had it cleaned by some local phone shop.( He also claimed that the phone work anyway ,though). After that i flashed the stock rom, and it worked.
And btw, how do i mark the thread solved?
Click to expand...
Click to collapse
Hi, even I'm stuck with the same problem.
Even the lenovo service center guys raised their hands saying it's an hardware problem and I've to replace the entire PCB to slove the issue. Could you be more specific on how to resolve this issue? if possible could you please let me know at which place you got your mobile fixed? Thanks
Regards,
Jagan ([email protected])
Jaganathan.S said:
Hi, even I'm stuck with the same problem.
Even the lenovo service center guys raised their hands saying it's an hardware problem and I've to replace the entire PCB to slove the issue. Could you be more specific on how to resolve this issue? if possible could you please let me know at which place you got your mobile fixed? Thanks
Regards,
Jagan ([email protected])
Click to expand...
Click to collapse
I had a problem with the Motherboard due to water getting in, and apparently it caused a short-circuit near the power button module. Actually speaking, I was really dissatisfied with the kind of service the Lenovo guys give to its customers, because first they told me that they will clean, and claimed that the board must be changed. The only thing which needed to be done in my phone was to clean that part of the board with White Petrol(you can ask the local mobile shop guys, they will have it, but just be careful). That solved my problem. And thanks to few threads, i got it working.
P.S: I am from Hyderabad, so had it solved here in a local shop.
Hi, Thanks for your reply. Was able to come out of that situation after 3 days, but had left my mobile with the local service center for 2 days (At the time, when i took my mobile from service center, my mobile was not working, was informed that the mobile is dead) I thought of giving a last try and plugged in the charger on 3rd day it started working . My mobile had a new problem display was broken (from inside) and speakers were not working, when i asked that guy his reply was " how can i know, your mobile was dead, when u brought in hear, my job was to fix it, why will i break it?" though my mobile was back to normal I had to pay a huge price of display and speakers. Hope everyone got to know the take away from my story. Crazy world; lesson learnt.
The same is happening to me!
And my phone keeps vibrating, also I don't know how to select one of those Chinese options, can you please help me sir?
Pok25dhw said:
The same is happening to me!
And my phone keeps vibrating, also I don't know how to select one of those Chinese options, can you please help me sir?
Click to expand...
Click to collapse
Hey!
My phone had some water damage issue, hence the loop. Opened the phone and cleaned it a bit. Yours might be different problem, try flashing stock firmware, or going into fastboot mode and flashing recovery. Currently don't have this phone so can't help that much.
PraneethMv said:
Hey!
My phone had some water damage issue, hence the loop. Opened the phone and cleaned it a bit. Yours might be different problem, try flashing stock firmware, or going into fastboot mode and flashing recovery. Currently don't have this phone so can't help that much.
Click to expand...
Click to collapse
Oh. Yes my phone too got wet in rain. I went to some shop and they helped me out. But thanks to you I realize that it was repairable and that too without loosing any data. Thanks so much for saving my thousands of ruppees that'd have been wasted to get a new phone. Also yes this model in general is pretty old so I can understand that most of the people don't use it anymore. Again thank you very much for saving all the stuff I had on this phone and the money. ??
I was given a Fire HD 7th Gen. I cannot get into recovery on it.
The story is that is was on 5.6.2.0 and accidentally downgraded to 5.6.1.0, which in turn never booted.
My diagnosis is...
I plugged it into my pc and I can hear the windows usb connect chime every 10 seconds or so and 2 seconds after a usb disconnect chime.
I cannot do any key combo to get into recovery as i only have a black screen and no more.
Have adb (and am familiar with) installed and the bin downloaded ready to sideload...
any help is appreciated, thanks!!
Did you try holding all the buttons - Volume UP, Volume DOWN and POWER - together for 30 seconds? That may get you back to power on or to recovery.
Did you verify that you can downgrade from 5.6.2.0 to 5.6.1.0 without bricking due to different bootloaders or recoveries? That tablet may now be bricked.
mdvanness said:
I was given a Fire HD 7th Gen. I cannot get into recovery on it.
The story is that is was on 5.6.2.0 and accidentally downgraded to 5.6.1.0, which in turn never booted.
My diagnosis is...
I plugged it into my pc and I can hear the windows usb connect chime every 10 seconds or so and 2 seconds after a usb disconnect chime.
I cannot do any key combo to get into recovery as i only have a black screen and no more.
Have adb (and am familiar with) installed and the bin downloaded ready to sideload...
any help is appreciated, thanks!!
Click to expand...
Click to collapse
donslade said:
Did you try holding all the buttons - Volume UP, Volume DOWN and POWER - together for 30 seconds? That may get you back to power on or to recovery.
Did you verify that you can downgrade from 5.6.2.0 to 5.6.1.0 without bricking due to different bootloaders or recoveries? That tablet may now be bricked.
Click to expand...
Click to collapse
Yes, I have tried that combination to no effect. From what I have read it cannot be downgraded from 5.6.2.0 to anything.
black screen
donslade said:
Did you try holding all the buttons - Volume UP, Volume DOWN and POWER - together for 30 seconds? That may get you back to power on or to recovery.
Did you verify that you can downgrade from 5.6.2.0 to 5.6.1.0 without bricking due to different bootloaders or recoveries? That tablet may now be bricked.
Click to expand...
Click to collapse
my partner was playing a game put it down for a few mins and screen is black. tried power button method nothing. tried with volume and power button and it wont hard reset. hes even taken out the battery ( its 7th gen 10 inch with alexa) any ides what we can do please. i cant contact amazon as i put google play on it. thanks
von1uk said:
my partner was playing a game put it down for a few mins and screen is black. tried power button method nothing. tried with volume and power button and it wont hard reset. hes even taken out the battery ( its 7th gen 10 inch with alexa) any ides what we can do please. i cant contact amazon as i put google play on it. thanks
Click to expand...
Click to collapse
If still under warranty, return it to Amazon for replacement or refund. Otherwise you can try flashing stock firmware back to it. That's assuming you know what version of fire OS it was on.
mdvanness said:
I was given a Fire HD 7th Gen. I cannot get into recovery on it.
The story is that is was on 5.6.2.0 and accidentally downgraded to 5.6.1.0, which in turn never booted.
My diagnosis is...
I plugged it into my pc and I can hear the windows usb connect chime every 10 seconds or so and 2 seconds after a usb disconnect chime.
I cannot do any key combo to get into recovery as i only have a black screen and no more.
Have adb (and am familiar with) installed and the bin downloaded ready to sideload...
any help is appreciated, thanks!!
Click to expand...
Click to collapse
I have the same problem with my amazon fire hd 10 now downgraded it and screen is black same thing with usb sound when plugged into PC tried every possible buttons compilation to enter recovery still nothing happens device not recognized by ADB which I'm very familiar with as well..tried opening the device and unplugged the battery cable from inside then still nothing totally dissembled it and assembled it again same result please let me know if you find a way to bypass this problem..
Mahmud92 said:
I have the same problem with my amazon fire hd 10 now downgraded it and screen is black same thing with usb sound when plugged into PC tried every possible buttons compilation to enter recovery still nothing happens device not recognized by ADB which I'm very familiar with as well..tried opening the device and unplugged the battery cable from inside then still nothing totally dissembled it and assembled it again same result please let me know if you find a way to bypass this problem..
Click to expand...
Click to collapse
You are permanently bricked. However there will hopefully be a fix in a week or two that would allow you to unbrick any Amazon tablet and unlock the bootloader. I have to run a few small tests on my test devices. I have on bricked HD 10 and it just takes a few minutes to complete the test. If successful, it will immediately boot again. After that we have to modify the zip files and scripts for this device.
DragonFire1024 said:
You are permanently bricked. However there will hopefully be a fix in a week or two that would allow you to unbrick any Amazon tablet and unlock the bootloader. I have to run a few small tests on my test devices. I have on bricked HD 10 and it just takes a few minutes to complete the test. If successful, it will immediately boot again. After that we have to modify the zip files and scripts for this device.
Click to expand...
Click to collapse
I do really appreciate the effort, thanks for the fast reply as well will be waiting for the fix.. :fingers-crossed:
Mahmud92 said:
I do really appreciate the effort, thanks for the fast reply as well will be waiting for the fix.. :fingers-crossed:
Click to expand...
Click to collapse
I can't make any promises. We still need to figure out if its possible. I've only glanced at the board of the 10 and it looks like it will work, but I won't know until I can perform the few tests needed. Hopefully tomorrow I will have time.
Sent from my MotoG3 using XDA Labs
Seems I joined to bricked club today (black screen, USB sound wehen plugging in).
Was on newest version (greather than 5.6.2.0, i think 5.6.3.x) and flashed 5.6.2.0.bin (latest you can download from amazon) via adb sideload for a complete reset and a clean device. I thought downgrading would not work if it would lead to problems - hm seems i was wrong
I bought it on 16.01.2018 so the questions is should i try if i get a replacement from amazon or wait if there will be an solution from DragonFire1024 within the next weeks? Not sure if amazon will replace it without trouble
Bierfreund said:
Seems I joined to bricked club today (black screen, USB sound wehen plugging in).
Was on newest version (greather than 5.6.2.0, i think 5.6.3.x) and flashed 5.6.2.0.bin (latest you can download from amazon) via adb sideload for a complete reset and a clean device. I thought downgrading would not work if it would lead to problems - hm seems i was wrong
I bought it on 16.01.2018 so the questions is should i try if i get a replacement from amazon or wait if there will be an solution from DragonFire1024 within the next weeks? Not sure if amazon will replace it without trouble
Click to expand...
Click to collapse
I'm going as fast as I can to try and unlock this thing apparently I always get the crap end of the stick when it comes to things that are easy I always get the hard part. Until I can get out and get a kit to remove the board, we're stuck where we're at. the motherboard needs to be removed and the only way to do that as a special screwdriver and I do not have the tools. But if the weather lets up I will be able to get them.
Bierfreund said:
Seems I joined to bricked club today (black screen, USB sound wehen plugging in).
Was on newest version (greather than 5.6.2.0, i think 5.6.3.x) and flashed 5.6.2.0.bin (latest you can download from amazon) via adb sideload for a complete reset and a clean device. I thought downgrading would not work if it would lead to problems - hm seems i was wrong
I bought it on 16.01.2018 so the questions is should i try if i get a replacement from amazon or wait if there will be an solution from DragonFire1024 within the next weeks? Not sure if amazon will replace it without trouble
Click to expand...
Click to collapse
Try your luck by contacting Amazons Customer Service they seem quite helpful when I wrote to them, explained the situation about downgrading the version and what happened, they simply asked to do some steps like turning of and button compo etc after making sure its bricked they offered to replace it with a new one right away ..but unfortunately I'm not at USA and they can't ship the replacement to Turkey..so my only hope for now is @DragonFire1024 fix
Mahmud92 said:
Try your luck by contacting Amazons Customer Service they seem quite helpful when I wrote to them, explained the situation about downgrading the version and what happened, they simply asked to do some steps like turning of and button compo etc after making sure its bricked they offered to replace it with a new one right away ..but unfortunately I'm not at USA and they can't ship the replacement to Turkey..so my only hope for now is @DragonFire1024 fix
Click to expand...
Click to collapse
We have download mode on the HD 10 which means we can get our bootloader unlocked once we can execute the payload. There won't be such a thing as a bricked tablet. If you can hold off, we just need execution. We have the recovery already. Everything nearly works aside from the script to load and execute the payload. Hopefully we'll get unlocked today.
Bierfreund said:
Seems I joined to bricked club today (black screen, USB sound wehen plugging in).
Was on newest version (greather than 5.6.2.0, i think 5.6.3.x) and flashed 5.6.2.0.bin (latest you can download from amazon) via adb sideload for a complete reset and a clean device. I thought downgrading would not work if it would lead to problems - hm seems i was wrong
I bought it on 16.01.2018 so the questions is should i try if i get a replacement from amazon or wait if there will be an solution from DragonFire1024 within the next weeks? Not sure if amazon will replace it without trouble
Click to expand...
Click to collapse
Although there are (as yet unrealized) prospects of a hardware unlock/rejunivation I would reach out to Amazon. What can it hurt? You might just score a essentially new refurb vs tearing apart your existing 'brick' with the associated risk of damaging it further. You can still pursue that option if Amazon declines to help. Why hold off...keep all options open.
DragonFire1024 said:
We have download mode on the HD 10 which means we can get our bootloader unlocked once we can execute the payload. There won't be such a thing as a bricked tablet. If you can hold off, we just need execution. We have the recovery already. Everything nearly works aside from the script to load and execute the payload. Hopefully we'll get unlocked today.
Click to expand...
Click to collapse
I got the same problem with my Fire HD 10 after flashing rom. Since I don't live in the US, I can not take it back to Amazon. Hope for the fix from you
see this post
https://forum.xda-developers.com/hd...-fire-hd-10-unbricking-anti-rollback-t3896616
i solved this problem with the post
Mine got a black screen today what do i do?
mdvanness said:
I was given a Fire HD 7th Gen. I cannot get into recovery on it.
The story is that is was on 5.6.2.0 and accidentally downgraded to 5.6.1.0, which in turn never booted.
My diagnosis is...
I plugged it into my pc and I can hear the windows usb connect chime every 10 seconds or so and 2 seconds after a usb disconnect chime.
I cannot do any key combo to get into recovery as i only have a black screen and no more.
Have adb (and am familiar with) installed and the bin downloaded ready to sideload...
any help is appreciated, thanks!!
Click to expand...
Click to collapse
This full solution: https://forum.xda-developers.com/hd8-hd10/orig-development/unlock-fire-hd-10-2017-suez-t3913639
Had the S8 for about 3 to 4 months, rooted it four days after getting it; no issues whatsoever, it worked perfectly. Yesterday, after a day of not using the phone, I attempt to use it and find that everytime I try to boot it, it freezes after 10 seconds and reboots.
I have tried flashing stock rom of android oreo for the device and am currently trying to see if nougat will fix my issue.
Edit: After attempting to go into android recovery, I am told the device "fails to open recovery_cause", with an unknown error.
I'd really appreciate some help with this, as I've done almost everything I can think of to fix it.
Edit 2 (5/9/19): I've successfully flashed a version of android pie, which successfully boots into the initial setup screen. Same issue however, after around 10 seconds, no matter what I do, the s8 freezes and reboots.
Given up with the phone, tech support already recommended to go on here to post a question. A new phone has been ordered, and the S8 will be sold in non-working condition. If anyone has any idea about how to solve this still, please say something; if not, have a great day .
Thank you.
Hello,
I have the same problem.
I contacted Samsung with Samsung Members.
They said that i had an app who make the phone crashing during the boot !
They said the proof is your phone don't crash when you make an secure boot :
Turn the device off.
Press and hold the Power key past the model name screen.
When “SAMSUNG” appears on the screen, release the Power key.
Immediately after releasing the Power key, press and hold the Volume down key.
Continue to hold the Volume down key until the device finishes restarting.
Safe mode will display in the bottom left corner of the screen.
Release the Volume down key when you see Safe Mode.
Uninstall apps that are causing a problem.
Click to expand...
Click to collapse
With this secure boot, no problem during boot
The only problem, is that i have only "official" apps donwloaded with Play Store, and i never find the app that cause the reboot :s