Related
Hello, I attempted to install a custom rom to improve my phones performance and stop it being sluggish, but it's backfired.
I was smart enough to back up my phone in Clockwork Recovery, and after I've restored my previous backup, well, my phone isn't booting.
It gets past the white HTC Screen (not Quietly Brilliant, just plain HTC) and for some reason it jumps to a black screen. Doing nothing. Just sitting there. I'm still able to access my HBOOT and Recovery but everything I try seems to get me no where. I tried rebooting and doing a factory reset. I could try another factory reset but I don't know where that would get me.
If anyone has any advise I would greatly appreciate it, thank you.
Daniel.
aLeedsUnitedFan said:
Hello, I attempted to install a custom rom to improve my phones performance and stop it being sluggish, but it's backfired.
I was smart enough to back up my phone in Clockwork Recovery, and after I've restored my previous backup, well, my phone isn't booting.
It gets past the white HTC Screen (not Quietly Brilliant, just plain HTC) and for some reason it jumps to a black screen. Doing nothing. Just sitting there. I'm still able to access my HBOOT and Recovery but everything I try seems to get me no where. I tried rebooting and doing a factory reset. I could try another factory reset but I don't know where that would get me.
If anyone has any advise I would greatly appreciate it, thank you.
Daniel.
Click to expand...
Click to collapse
you can try to flash stock rom..it ll boot for sure..
about your problem it's strange..your backup should hv worked cz you just changed recovery nothing else..
Exactly what I'm thinking, I just done another recovery just to be on the safe side, and now my phone is no longer going to a black screen, instead it's just stuck on the HTC screen. But I'll take up your advise and try a stock rom.
This is the rom I attempted to install: http://forum.xda-developers.com/showthread.php?t=1515120
I followed all the instructions and for some reason it just didn't agree with my phone and wouldn't boot. Hence me restoring my phone.
Never should have bothered and left it as it was. I'll keep you posted.
Thank you
aLeedsUnitedFan said:
Exactly what I'm thinking, I just done another recovery just to be on the safe side, and now my phone is no longer going to a black screen, instead it's just stuck on the HTC screen. But I'll take up your advise and try a stock rom.
This is the rom I attempted to install: http://forum.xda-developers.com/showthread.php?t=1515120
I followed all the instructions and for some reason it just didn't agree with my phone and wouldn't boot. Hence me restoring my phone.
Never should have bothered and left it as it was. I'll keep you posted.
Thank you
Click to expand...
Click to collapse
good luck...if nothing works out..check my work in my signature..you will find flashable stock zips..try anyone just in case..
Right, I just installed the Marvel Stock Rom you have, and it almost boots.
What I mean by this is, it goes through the HTC screen, then reboots.
On the second boot after the HTC screen it throws me back into ClockworkMod. I followed all the instructions you say to do and it still isn't cutting it :-/
aLeedsUnitedFan said:
Right, I just installed the Marvel Stock Rom you have, and it almost boots.
What I mean by this is, it goes through the HTC screen, then reboots.
On the second boot after the HTC screen it throws me back into ClockworkMod. I followed all the instructions you say to do and it still isn't cutting it :-/
Click to expand...
Click to collapse
thats problem...like it's fully stock..something wrong i guess in phone...which version of recovery you have?
ClockworkMod Recovery v5.0.2.8 D-:
aLeedsUnitedFan said:
ClockworkMod Recovery v5.0.2.8 D-:
Click to expand...
Click to collapse
then phone should be boot..my roms are fully stock based..
no idea what to do now...might someone other can help you good luck..
I have to be doing something wrong, but I just don't see what I'm doing wrong. I clear the data off of everything the instructions say and yet when I install the rom, it just doesn't want to know. But thanks for trying
Hello all. Let me first thank you for your time in reading my post. I appreciate it. I'm not a fan of only posting for help but I suppose that the site suggesting to always search first is to thank for that because I am usually able to find answers. So please forgive me if this is posted elsewhere but I really have searched and asked around but haven't seen anything similar to my issue. If there is something like it I do not know what to call it. I at first thought it was a sudden death, but realized I think my device model & the symptoms have disproved this theory.
My story...
I bought my AT&T Galaxy S3 feb 2013. I have had it, spent a month or two stock everything. The past month & a half I have flashed CM 10.1 & most recently PK-2.32 for about 3 weeks. Have ran it and loved it with no issues. Used the kernel that comes with both ROMs.
4 days ago
I was charging my phone at work, picked it up after a while, and it wouldn't turn on. It was stuck in a loop of 2 of the screens in my attachments(the battery screen & the SGS3 logo). The battery screen is not in motion, it is stationary like that so that the circle doesn't move.
I have tested quite a few things in regard to what I thought might be the issue...other batteries, chargers, cables pull sim & SD and still no luck...etc.
While the phone is unplugged I get no indication of life. Only when I plug it in will it show me the battery symbol & the logo.
After some playing with it while it is plugged in I have been able to get it into download mode quite frequently with no issue as seen in the third attachment.
So yes I can get into download mode but I'm still "fairly new" and not sure where to proceed from here. I'm not sure what my options are as this is new to me and I can't find anything related, nor can my much more experience friend who is not so new at it that got me into wanting to load custom ROMs.
And yes, as you can see it has tripped my flash counter up once, from what I've read there's only one way to fix that if I need to send it in.
So...If you are able and willing to help I would greatly appreciate it and any options you might give me. I'm willing to try almost anything as my phone is of no use to me at this moment.
if you can access download mode,one option is to connect the device to your PC and flash the stock firmware via odin. untick the Auto Reboot option. once you get a PASS, pull the battery, replace and immediately hit vol up + home + power button. when the device vibrates, release just the power button. in recovery, wipe data/factory reset, wipe cache. reboot.
first, can you boot into recovery at all?
xBeerdroiDx said:
if you can access download mode,one option is to connect the device to your PC and flash the stock firmware via odin. untick the Auto Reboot option. once you get a PASS, pull the battery, replace and immediately hit vol up + home + power button. when the device vibrates, release just the power button. in recovery, wipe data/factory reset, wipe cache. reboot.
first, can you boot into recovery at all?
Click to expand...
Click to collapse
First of all, thank you for your reply. I will definitely use your suggestion if that turns out to be my best option.
Secondly, it's funny you should ask about recovery. I have tried and tried to get into recovery, I have only been able to boot into it one time while it is on a charger, did not try anything because I thought that if I could get in it once I could get in it again, but since then no I have not...
UNTIL just now when you asked, I tried again and I am in TWRP. It is still in recovery at this moment, again only because I have it plugged in so I am open to your advice.
Well, since you're in recovery, I would consider wiping data/factory reset, wipe cache and dalvik, flash rom again and gapps. Reboot to see if that got you cleared up. This would mean you have to reset up your phone for the most part.
You could also consider wiping cache and dalvik, and flashing the rom and gapps. maybe this would correct your issue without wiping the device data.
Sou your device just did this? You weren't trying to flash a new kernel or anything?
moose0003 said:
First of all, thank you for your reply. I will definitely use your suggestion if that turns out to be my best option.
Secondly, it's funny you should ask about recovery. I have tried and tried to get into recovery, I have only been able to boot into it one time while it is on a charger, did not try anything because I thought that if I could get in it once I could get in it again, but since then no I have not...
UNTIL just now when you asked, I tried again and I am in TWRP. It is still in recovery at this moment, again only because I have it plugged in so I am open to your advice.
Click to expand...
Click to collapse
You have a few options at this point. You can access recovery and download mode so this is good. You can try and flash a new ROM through TWRP. You can also go into download mode and install a stock rom to start over. With TWRP choose a ROM of your choice (as long it is intended for your model). You could just restore a nandroid of one that you know worked...if you made any.
xBeerdroiDx said:
Well, since you're in recovery, I would consider wiping data/factory reset, wipe cache and dalvik, flash rom again and gapps. Reboot to see if that got you cleared up. This would mean you have to reset up your phone for the most part.
You could also consider wiping cache and dalvik, and flashing the rom and gapps. maybe this would correct your issue without wiping the device data.
Sou your device just did this? You weren't trying to flash a new kernel or anything?
Click to expand...
Click to collapse
Thanks again for your reply. I will try this and check back.
You are correct, it just did this, no kernel or anything. I will try wiping the device the data doesn't bother me. I won't lose much.
Have you or anyone else heard of this happening or know a cause? I could not find anything.
aybarrap1 said:
You have a few options at this point. You can access recovery and download mode so this is good. You can try and flash a new ROM through TWRP. You can also go into download mode and install a stock rom to start over. With TWRP choose a ROM of your choice (as long it is intended for your model). You could just restore a nandroid of one that you know worked...if you made any.
Click to expand...
Click to collapse
Thanks for your reply. I have a few backups. I will try stock first and see where that takes me and go from there.
Sorry about the delay. I was in recovery but I could not get it to recognize my SD card. So I took it out to try to load it in the computer and I'm having the worst time getting either of my computers to recognize either SD card I have even with 2 different readers. Still working on it though...
moose0003 said:
Sorry about the delay. I was in recovery but I could not get it to recognize my SD card. So I took it out to try to load it in the computer and I'm having the worst time getting either of my computers to recognize either SD card I have even with 2 different readers. Still working on it though...
Click to expand...
Click to collapse
Ouch sounds like your sd card is corrupted, you may not be able to get any info off it. You may have to use Odin to flash a stock ROM. You can still get to Download right?
metalsnakebite said:
Ouch sounds like your sd card is corrupted, you may not be able to get any info off it. You may have to use Odin to flash a stock ROM. You can still get to Download right?
Click to expand...
Click to collapse
Thanks for commenting. You were correct, my sd card was corrupted. Had my 4gb card that was working so I was able to determine that was the case.
Latest update
I was frustrated at the most recent attempt to load recovery, which I never succeeded in doing. I then decided to load a stock ROM from odin. Started this process, and it was going well until the reboot phase, which is what I was fearing the most.
Once it attempted the reboot, it attempted to reboot, then would just vibrate shortly over and over and over, with nothing on the screen.
Unplugged the device hoping for the best, yet nothing happened upon my attempts to power on.
Plugged back in and would initiate the same sequence in my original post, with the image of the battery, to the image of the SGS3 logo.
So...hoping for any good news someone has to offer, but have come to terms with the worst.
Again, appreciate any comments toward the struggles with my phone.
xBeerdroiDx said:
Well, since you're in recovery, I would consider wiping data/factory reset, wipe cache and dalvik, flash rom again and gapps. Reboot to see if that got you cleared up.......
Click to expand...
Click to collapse
Forgot to mention in my last post...I did the steps above while in recovery then I tried to reboot with nothing happening still. I did this before doing anything in ODIN.
moose0003 said:
Forgot to mention in my last post...I did the steps above while in recovery then I tried to reboot with nothing happening still. I did this before doing anything in ODIN.
Click to expand...
Click to collapse
after flashing stock via odin, you generally have to boot into stock recovery to wipe data/factory reset and wipe cache. reboot.
moose0003 said:
Thanks for commenting. You were correct, my sd card was corrupted. Had my 4gb card that was working so I was able to determine that was the case.
Latest update
I was frustrated at the most recent attempt to load recovery, which I never succeeded in doing. I then decided to load a stock ROM from odin. Started this process, and it was going well until the reboot phase, which is what I was fearing the most.
Once it attempted the reboot, it attempted to reboot, then would just vibrate shortly over and over and over, with nothing on the screen.
Unplugged the device hoping for the best, yet nothing happened upon my attempts to power on.
Plugged back in and would initiate the same sequence in my original post, with the image of the battery, to the image of the SGS3 logo.
So...hoping for any good news someone has to offer, but have come to terms with the worst.
Again, appreciate any comments toward the struggles with my phone.
Click to expand...
Click to collapse
Well usually after a fresh Stock Install using Odin you need to to go into the recovery and wipe data, cache/dalvic cache, factory reset. That should fix your problem.
Lol...beerdroid bro i didnt hit the next page you said what i just did.
metalsnakebite said:
Lol...beerdroid bro i didnt hit the next page you said what i just did.
Click to expand...
Click to collapse
haha. i've done that before. cheers, buddy.
xBeerdroiDx said:
after flashing stock via odin, you generally have to boot into stock recovery to wipe data/factory reset and wipe cache. reboot.
Click to expand...
Click to collapse
metalsnakebite said:
Well usually after a fresh Stock Install using Odin you need to to go into the recovery and wipe data, cache/dalvic cache, factory reset. That should fix your problem.
Lol...beerdroid bro i didnt hit the next page you said what i just did.
Click to expand...
Click to collapse
Thanks for the input guys. I'm having a difficult time to get it to stay into recovery now again. It acts like it wants to go in but it will just reboot. I will keep trying and if I need anymore help I will come back. Thanks so much again.
Back again. So I kept playing and was finally able to get into recovery as you guys suggested. Once I got in it finished the odin process and actually booted up! First time in a week. So ran through setup and then was able to determine that wifi is not working with stock ROM. Not sure if it's the phone or the ROM.
After it booted up and turned on was able actually do most functions, didn't test a lot wanted to see if it would work without being plugged in...this answer was no.
So after much testing I think what determines what will power it on and off is determined by what it is plugged into. I still think it is having hardware issues though because of the lack of powering on, but I am fairly certain that I can start it every time with a certain cable/charging dock.
I think the next thing I might try since I can get it to turn on is to root it again, load TriangleAway from an SD card, fix flash counter, unroot, load stock & see if they will warranty for hardware issues on the battery connection or whatever it is.
Haven't done this yet but will start tonight & have it finished by tomorrow is the plan. If anyone has any better suggestions I would gladly take them.
So this should be my last post unless a question arises for me.
moose0003 said:
.....I think the next thing I might try since I can get it to turn on is to root it again, load TriangleAway from an SD card, fix flash counter, unroot, load stock & see if they will warranty for hardware issues on the battery connection or whatever it is.....
Click to expand...
Click to collapse
This is what I said I was going to try to do. Took it to work and found time to do the above. TriangleAway worked a lot better than I ever thought it would. Flash counter reset, loaded unrooted stock and have a replacement on the way. Went very smoothly.
So doubt I will root & rom again until out of warranty. I appreciate everyone's help with my issue.
XDA is a great place.
Hello all, so yesterday I went on my tablet (Nexus 7 2013 WIFI ver.) and browsed the net a bit and went to sleep. I recall having around 30% battery power. This morning I wake up to an apparently flat battery (power button didn't turn on anything) so I just plugged it in and did something else. After a while, I took my tablet and started it with the power button. However, it got stuck on the Google logo and never fired up anything. I've rooted the tablet quite some time ago (months) so the cause is not from there.
Things I haven't recently done:
Installing an app.
Rooting or flashing anything.
Updating an app.
Things I have tried doing to fix the problem:
Booting into FASTBOOT then trying the recovery mode = still stuck on the Google logo.
Booting a custom recovery image using Wug's toolkit = frozen at the team logo (TWRP) / black screen (CWM).
Flash Stock + Unroot (Soft-Bricked/Bootloop) = FAILED (flash write failure).
So now I'm really stuck and desperate to make the device work again. I've been reading all day long and trying all sorts of solutions to no avail. And it seems far-fetched to me for a device like this to just instantly brick itself without any reason at all.
Can anyone help me with this case ? Or does anyone has any idea what just happened to my tablet ? :crying:
EDIT: I'm afraid that warranty might not work as the device was unlocked and rooted so it's the last solution for me.
Bumpity bump
No one has any idea what happened to the tablet and how to fix it ? I've tried doing some more flashing but to no avail. It just refuses to flash and keeps failing to write the files.
I think you need to leave out on the charger for 1/2hr without doing anything with it. You are probably using what little power it has charged by trying to reboot it, etc.
I had to do that once and it did the trick.
Sent from my Nexus 7 using XDA Free mobile app
There is no reason you should not be able to get in to recovery (power and volume down).
You could call Motorola. They have good tech support.
The exact same thing happened to me. I rooted it months ago and haven't changed a thing since then. It just froze up a few days ago. I restarted and it just gets stuck on the google screen. I can get into the bootloader, but when I try to go to recovery, the google screen comes up and won't go away. I've tried every method I can find for flashing the stock image and absolutely nothing is working. I just get stuck on the google screen.
Please update this if you find a solution!
Do u guys have the most up to date version of whatever particular recovery that you're on?
Yep. I've flashed the stock recovery multiple times to no avail. :/
nexusjas said:
Yep. I've flashed the stock recovery multiple times to no avail. :/
Click to expand...
Click to collapse
If you can't get into recovery or flash any images it sounds to me like a hardware failure. Bad memory maybe? If you've tried everything then RMA to Asus before the one year warranty runs out.
Have you tried to see if your computer sees your N7 by typing fastboot devices if you have the sdk installed?
wantabe said:
If you can't get into recovery or flash any images it sounds to me like a hardware failure. Bad memory maybe? If you've tried everything then RMA to Asus before the one year warranty runs out.
Click to expand...
Click to collapse
Not what I wanted to hear, but you're probably right. Thanks :/
nexusjas said:
Not what I wanted to hear, but you're probably right. Thanks :/
Click to expand...
Click to collapse
I was to slow with my update. Does your computer see your N7 with fastboot?
wantabe said:
I was to slow with my update. Does your computer see your N7 with fastboot?
Click to expand...
Click to collapse
Yes, I can get into the bootloader just fine and I can use fastboot. I go through the flashing process and the command prompt says everything flashed successfully, but when I restart the device, it hangs on the google logo. The same thing happens when I try to boot into recovery.
nexusjas said:
Yes, I can get into the bootloader just fine and I can use fastboot. I go through the flashing process and the command prompt says everything flashed successfully, but when I restart the device, it hangs on the google logo. The same thing happens when I try to boot into recovery.
Click to expand...
Click to collapse
If you fastboot flashed the factory image and can't boot up then it sounds like a hardware problem. Out of ideas, sorry.
wantabe said:
If you fastboot flashed the factory image and can't boot up then it sounds like a hardware problem. Out of ideas, sorry.
Click to expand...
Click to collapse
I'm not sure what happened, but I just ran this little utility again (I've done it many times over the last week or so to no avail) and it actually worked. Hopefully it keeps working!
Thanks for your help!
Hi there. My fire TV is rooted and has the following installed:
clockwork mod custom recovery
51.1.4.0_514006420 updated 10/30/2014 Custom rom
I was initially experiencing strange behaviour with my external hard drive converting to a read only drive after a while for no apparent reason so decided to do a factory restore
I tried to factory restore the device but for some reason after the factory restore and watching the funny cartoon on set up the device said I only had 2.5gb of hard drive space left of the 5.5 gb available so I decided to try formatting the data on the clockwork mod restore but it still didn't work so I then formatted the sd but as soon as I did this I thought that can't be right as surely the recovery image is on that but it was too late. After it rebooted the fire TV no longer works. It just hangs on the White amazon logo. I've tried the "ALT-PRNT SCREEN-I" option to try get it to restore but with no luck, it just constantly stays on the White amazon logo so I'm kinda thinking I've totally wiped the fire TV and have therefore bricked it. It does respond to "control-alt-delete" but that just reboots the device.
Can anyone advise if this is indeed the case so I don't waste any of my time trying to fix this. I can't return the product as I purchased it on a recent holiday to usa and I'm from uk so a bit gutted.
Many thanks in advance
Paul1672
Sounds like you wiped your /system. If so, then yes you are soft bricked.
I have soft bricked this unit before and managed to restore it but that was before I installed the clockwork mod and custom rom.
If it is soft bricked surely I would be able to restore it still? I have tried several times to get it to return to the clockwork mod restore using the "ALT-PRINTSCREEN-i" method but all I get is the constant white Amazon logo. It feels like I've totally wiped the entire system including all sign of clockwork mod
Can anyone advise if I have indeed totally messed it up or is there any hope for me?
Paul
Anybody got any advice or opinion be it good or bad?
Before I bin the unit
Paul
Paul1672 said:
Anybody got any advice or opinion be it good or bad?
Before I bin the unit
Paul
Click to expand...
Click to collapse
Yes, I have some advice. Don't do that crap again. Be smart. And I'm a bit curious, you talk about an external harddrive and you then talk about wiping the SD card. You mean the /sdcard directory in the AFTV? Seriously? If that is the case, I have some better advice for you. Don't tinker with stuff you don't understand.
So I can assume from your reply I have indeed wiped the entire system and there is in fact no way to repair/restore the device? Totally agree with all you said and I did realise my error literally as soon as I did it a harsh lesson learnt I think and believe me it's not one I will be repeating.
Was just hoping I may be lucky and find someone who has a way of solving my issue but it appears not
Paul
Hi
What's your suggestion or advice be to resolve the problem that was presented.
Cheers
nyder said:
Yes, I have some advice. Don't do that crap again. Be smart. And I'm a bit curious, you talk about an external harddrive and you then talk about wiping the SD card. You mean the /sdcard directory in the AFTV? Seriously? If that is the case, I have some better advice for you. Don't tinker with stuff you don't understand.
Click to expand...
Click to collapse
Paul1672 said:
So I can assume from your reply I have indeed wiped the entire system and there is in fact no way to repair/restore the device? Totally agree with all you said and I did realise my error literally as soon as I did it a harsh lesson learnt I think and believe me it's not one I will be repeating.
Was just hoping I may be lucky and find someone who has a way of solving my issue but it appears not
Paul
Click to expand...
Click to collapse
Naw, you didn't brick you device. Sorry, was in some sort of mood when posted.
http://www.aftvnews.com/how-to-unbr...ry-mode-and-factory-reset-the-amazon-fire-tv/
That link gives information. You need to get into recovery mode and a factory restore. If the factory restore doesn't work, then just use the same firmware you had before you deleted the stuff. You can put any firmware on a usb stick and read it from that.
Most of this has been covered in the various threads, I suggest you browse thru them, lots of good stuff.
good luck, and sorry I didn't include this in my last post, i should of.
Are u sure mate? I've tried the Alt-prntscreen-I method without any success. The fire tv won't boot into the clockwork mod recovery at all and I'm wondering if I've formatted it somehow. I guess until I get into the restore screen I can't do a thing I did have clockwork mod installed and a custom rom, wud that make a difference as I did indeed format the fire tv sd partition.
Appreciate your help
Paul
Paul1672 said:
Are u sure mate? I've tried the Alt-prntscreen-I method without any success. The fire tv won't boot into the clockwork mod recovery at all and I'm wondering if I've formatted it somehow. I guess until I get into the restore screen I can't do a thing I did have clockwork mod installed and a custom rom, wud that make a difference as I did indeed format the fire tv sd partition.
Appreciate your help
Paul
Click to expand...
Click to collapse
You should be able to get to a recovery screen from what you did, I would think, unless maybe if you deleted everything from the root directory, not the sdcard directory. I am not an expert on that though. It's our thanksgiving holiday here in the states, so the peeps that know might not be around.
Sorry I can't be more helpful then that.
You copy your recovery.img to the sdcard only as an interim step for flashing. It then gets stored in a separate partition that CWM won't wipe. If you have done the changes you mention from CWM, then CWM is still present on the device. I had to get in to my system with the alt-prtscreen-I method as well, and it took a few tries, spamming the keeps after unplugging and replugging the device. Also if you are using a k400 or some other keyboard with a FN key you may have to push that as well to make sure it gets the proper key sequence. I'm fairly confident your device is only softbricked and can be recovered. you may need to adb sideload or copy a zip to usb to load the firmware, but it should be doable.
well, I've tried constantly rebooting and pressing alt-printscreen-I simultaneously for the last half hour with no luck wotsoever all I get is the constant white amazon logo. in fact, the logo appears as soon as I connect the power lead and just hangs there until I either remove the lead or press control-alt-delete at which point the device reboots.
something tells me I've done something a lot more serious than just wipe the sd partition but I'm a little surprised if clockwork mod would allow it.
kinda giving up now as I have soft bricked the device before but that was before I installed clockwork mod and it went to factory restore just fine doing the alt-printscreen-i method that time.
thanks for all the advice guys. I really do appreciate any help I have had. I'm willing to try anything to try get this unit to work. the way I see it, I have nothing to lose right now. just seems strange the unit no longer shows any sign of changing from the constant white amazon logo. there's definitely no sign of the colourful amazon logo that usually appears at some point during the boot process which kinda gives me the impression I've somehow completely wiped the whole system.
is that even possible guys?
If you are saying that ctrl-alt-del reboots your box then the alt -sysrq-i should get you to recovery. Try using a wired keyboard and maybe a different keyboard than you have been using.
Ive tried a wired keyboard and now when I press ALT-PRNTSCREEN-i the fire tv just reboots. I've followed the guide that is in a previous reply which I have been able to do on a previous unrelated soft brick I managed but this time each time I do the ALT-PRINTSCREEN-i combo it just reboots and nothing else. Just a white AMAZON logo. I have done the method like 5 times and still no joy
Paul1672 said:
Ive tried a wired keyboard and now when I press ALT-PRNTSCREEN-i the fire tv just reboots. I've followed the guide that is in a previous reply which I have been able to do on a previous unrelated soft brick I managed but this time each time I do the ALT-PRINTSCREEN-i combo it just reboots and nothing else. Just a white AMAZON logo. I have done the method like 5 times and still no joy
Click to expand...
Click to collapse
Call Amazon and play stupid saying it just hangs at the logo, I did that once and they send me a replacement free of charge.
Wish I could but i purchased it whilst on holiday in Florida and I'm from the uk
Anybody got any more advice? It seems really strange that I can't get the factory reset to work. Still stuck on the White Amazon logo which boots instantly as soon s I power the device. I've managed to get the device to power cycle using ALT-PRNTSCREEN-i method bit it's does it going on 20 times with absolutely no sign of the failed update screen so it looks like the device just doesn't have anything on it. Is it possible I've somehow completely wiped the clockwork mod recovery? And if I have shud the device revert back to factory restore or may I of wiped that too?
Paul1672 said:
Anybody got any more advice? It seems really strange that I can't get the factory reset to work. Still stuck on the White Amazon logo which boots instantly as soon s I power the device. I've managed to get the device to power cycle using ALT-PRNTSCREEN-i method bit it's does it going on 20 times with absolutely no sign of the failed update screen so it looks like the device just doesn't have anything on it. Is it possible I've somehow completely wiped the clockwork mod recovery? And if I have shud the device revert back to factory restore or may I of wiped that too?
Click to expand...
Click to collapse
no its not possible that you wiped recovery from what you did in cwm.. its located on a different partition, if you cant connect via ADB or cant get recovery to load your out of luck.. so did you install the newest prerooted rom? what about the boot menu?
I had the following pre-rooted rom installed:
51.1.4.0_514006420 updated
Sounds like I've messed it up then
Paul1672 said:
I had the following pre-rooted rom installed:
51.1.4.0_514006420 updated
Sounds like I've messed it up then
Click to expand...
Click to collapse
no need for the boot menu on that update iirc. i think you need to just keep trying to get to recovery, i think its still there.. the key command is just not registering.. keep trying i guess.
Just got the XL on Friday. Loved it.
Unlocked the bootloader about 45 minutes ago. Wiped upon reboot (as normal). Google logo displayed with progress bar but the animation never stopped.
Downloaded the factory image from Nov. Ran the flash-all.bat from bootloader. No errors. Rebooted. Got a "Your device is corrupt" error. Phone stuck on the Google boot screen. Going into recovery just gives me a dead droid.
Attempting to flash the 8.1 developer preview results in the same issue. As of right now, nothing seems to boot at all. I've changed USB-C cables, since I've read about those causing issues, but still the same.
derekr44 said:
Just got the XL on Friday. Loved it.
Unlocked the bootloader about 45 minutes ago. Wiped upon reboot (as normal). Google logo displayed with progress bar but the animation never stopped.
Downloaded the factory image from Nov. Ran the flash-all.bat from bootloader. No errors. Rebooted. Got a "Your device is corrupt" error. Phone stuck on the Google boot screen. Going into recovery just gives me a dead droid.
Attempting to flash the 8.1 developer preview results in the same issue. As of right now, nothing seems to boot at all. I've changed USB-C cables, since I've read about those causing issues, but still the same.
Click to expand...
Click to collapse
I have no experience with your issue but it sounds like a soft brick. Im sure if you follow this guide ypu can fix it. https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418 hopefully this helps until someone who really knows can help you.
Dielahn said:
I have no experience with your issue but it sounds like a soft brick. Im sure if you follow this guide ypu can fix it. https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418 hopefully this helps until someone who really knows can help you.
Click to expand...
Click to collapse
That simple thread actually gave me an idea. I grabbed the latest SDK tools. Presto!
Note to anyone else with this issue...
derekr44 said:
Just got the XL on Friday. Loved it.
Unlocked the bootloader about 45 minutes ago. Wiped upon reboot (as normal). Google logo displayed with progress bar but the animation never stopped.
Downloaded the factory image from Nov. Ran the flash-all.bat from bootloader. No errors. Rebooted. Got a "Your device is corrupt" error. Phone stuck on the Google boot screen. Going into recovery just gives me a dead droid.
Attempting to flash the 8.1 developer preview results in the same issue. As of right now, nothing seems to boot at all. I've changed USB-C cables, since I've read about those causing issues, but still the same.
Click to expand...
Click to collapse
By the way, the dead Droid is recovery, from that screen, hold power and press up for recovery menu, in case you ever get stuck again
And just for future reference for others who may be in a similar issue and stumble across this thread...
As long as you've successfully unlocked your bootloader and "fastboot devices" successfully pulls up your device, you'll be just fine. You just gotta take a step back, breath and then make sure your SDK tools are updated before moving forward.
if the flash tool isn't working, use my script:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
i know this is probably going to sound really stupid but somehow i bricked my phone as well....not exactly sure what happened but it had to do with something after installing/booting TWRP. anyway, i am stuck with nothing on my phone and can't seem to do anyting....derek, how did you use sdk to fix???
*edit I can't even have fastboot devices pull my phone....am i really f'ed?
warlord1352 said:
i know this is probably going to sound really stupid but somehow i bricked my phone as well....not exactly sure what happened but it had to do with something after installing/booting TWRP. anyway, i am stuck with nothing on my phone and can't seem to do anyting....derek, how did you use sdk to fix???
*edit I can't even have fastboot devices pull my phone....am i really f'ed?
Click to expand...
Click to collapse
If you cannot get the Bootloader to load, then you are seriously SOL. You have a hard bricked device.
Only thing you can do now is raise a support case with Google and hope that allow you to get a replacement with the only explanation being, "The phone restarted on it's own and never came back up." Or something similar and vague without expressly telling them what you did.
warlord1352 said:
i know this is probably going to sound really stupid but somehow i bricked my phone as well....not exactly sure what happened but it had to do with something after installing/booting TWRP. anyway, i am stuck with nothing on my phone and can't seem to do anyting....derek, how did you use sdk to fix???
*edit I can't even have fastboot devices pull my phone....am i really f'ed?
Click to expand...
Click to collapse
Make sure you try a different cable to connect your phone to your PC.. I had the same issue, and I try two different cable before my device accepted the flash-all
Okay, so somehow fortunately I was able to get back into my TWRP 1 last time and able to push my files I needed to boot it back up...
Raistline said:
If you cannot get the Bootloader to load, then you are seriously SOL. You have a hard bricked device.
Only thing you can do now is raise a support case with Google and hope that allow you to get a replacement with the only explanation being, "The phone restarted on it's own and never came back up." Or something similar and vague without expressly telling them what you did.
Click to expand...
Click to collapse
The funny thing is I was able to and was in bootloader but I couldn't use any commands from my computer (as far as I know) which is why I was freaking out.
I should've but I didn't actually try using other cables. I did try other usb ports but that didn't do anything.
I still kind of believe that my phone (somehow) got messed up from loading TWRP. I don't know if it's because it is still beta or what but I am like 99% sure it was from that as I can't see anything else being the problem.
warlord1352 said:
i know this is probably going to sound really stupid but somehow i bricked my phone as well....not exactly sure what happened but it had to do with something after installing/booting TWRP. anyway, i am stuck with nothing on my phone and can't seem to do anyting....derek, how did you use sdk to fix???
*edit I can't even have fastboot devices pull my phone....am i really f'ed?
Click to expand...
Click to collapse
just install the lastest fastboot and adb drivers from google and flash the factory image using commands or use any script .
after that everytime my phone got stuck on google logo .
how i fixed - Temporary boot twrp beta2 recovery using cmd (fastboot boot abc.img) "here abc refers to the correct name of the img file" and once booted into recovery go to advanced and select Partition A and reboot.
It will boot up just fine
Here is the link for a script that will flash both partitions with stock image
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
derekr44 said:
Just got the XL on Friday. Loved it.
Unlocked the bootloader about 45 minutes ago. Wiped upon reboot (as normal). Google logo displayed with progress bar but the animation never stopped.
Downloaded the factory image from Nov. Ran the flash-all.bat from bootloader. No errors. Rebooted. Got a "Your device is corrupt" error. Phone stuck on the Google boot screen. Going into recovery just gives me a dead droid.
Attempting to flash the 8.1 developer preview results in the same issue. As of right now, nothing seems to boot at all. I've changed USB-C cables, since I've read about those causing issues, but still the same.
Click to expand...
Click to collapse
Something similar for me but with different reason for starting all this. When I did sideload of 8.1 all went well but my camera wasn't working (I saw the same thing in 8.1 DP) so I needed to go back to 8.0 but you can't sideload downgrade. I went to Google to get replacement sent and figure I might try to sort things out with this one in the meantime. I had to unlock to be able to just flash the factory 8.0 image so did that with both the unlock commands, then after that and after update I just got hung on the white screen with google logo. I was able to get back to bootloader with the power button + volume from off and from there I would get to the screen with the android and the exclamation point - I think you hold volume up and then power to go to sideload. Once there I just sideloaded 8.0 and all was good. I do still get the warning about corrupt whatever and have to hit power on reboot or fresh power up but I could redo the locks and whatnot and all seems fine now with camera working.
At the least I got camera back while waiting for replacement.
b4db0ys said:
just install the lastest fastboot and adb drivers from google and flash the factory image using commands or use any script .
after that everytime my phone got stuck on google logo .
how i fixed - Temporary boot twrp beta2 recovery using cmd (fastboot boot abc.img) "here abc refers to the correct name of the img file" and once booted into recovery go to advanced and select Partition A and reboot.
It will boot up just fine
Here is the link for a script that will flash both partitions with stock image
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
This cleaned things up for me - still no camera in 8.1 but I got the replacement coming.
So I'm in the same boat as the OP but my bootloader is locked. Am I totally screwed? Is there a way to do any of this when the device won't show up in ADB?
Deuces said:
if the flash tool isn't working, use my script:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
can you just develop some scripts that working on locked bootloader ?
i have a bricked Pixel xl with locked bootloader and oem locked
If you can boot twrp but can't connect to a pc, a type c flash drive comes in handy. Load it with the needed ota, twrp installer zip and Just mount it and you're good to go.