Related
Anyone with a bricked phone from flashing the gsm boot image, flash this via Odin as a PDA.
It will flash a stock boot image back to your device.
1. Extract Odin files to a folder from the attachment.
How to get into Download Mode (For Odin)
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME DOWN' buttons and press the 'POWER' button for about 2 seconds until a WARNING! Screen appears. Press the 'VOLUME UP' button to enter Download Mode.
2. Tick 'Auto Reboot' and 'F. Reset Time' in Odin and nothing else.
3. Download the boot image and load into Odin as a PDA.
4. Click on Start to flash the image.
http://www.mediafire.com/download.php?crhj889aj2tricz
DO NOT UNZIP THE BOOT TAR FILE, FLASH IT AS IT IS.
Mark.
It worked perfectly on my AT&T Galaxy S3, thanks a lot mskip!!!
mskip, you are a lifesaver!!
thanks man we already had one in root guide but 2 is even better xD
Awesome, this is what I was waiting for before trying root. Thanks!
It worked perfectly on my at&t Galaxy S3!!
Thanks man, you are a lifesaver!!
Haha mskip, see what you started Thanks for getting involved. Sorry it happened in the wrong order... Needed the correct rootkit first
Ok...Looks like I'm having problems. I did the root process, seemed to work fine. Booted up fine. Installed Busybox, etc. After that, I rebooted and it won't go past the "Samsung Galaxy SIII" screen. Not responsive. I have to pull the battery. I wiped data and factor reset via CWM, but still won't boot. Installed this, nothing.
Any ideas?
What if your screen doesnt even turn on after istalling international rom?
all i get is a red led light.
vince24L said:
What if your screen doesnt even turn on after istalling international rom?
all i get is a red led light.
Click to expand...
Click to collapse
Have you unplugged the usb cable, pulled the battery, replaced it then tried to boot into download mode?
If you have flashed a gsm rom then you are going to need to flash custom recovery with external sd support then copy a cwm rom across and restore it.
Mark.
CZ Eddie said:
Awesome, this is what I was waiting for before trying root. Thanks!
Click to expand...
Click to collapse
Wait, I just noticed the file is only 10MB.
So this is not the factory operating system image then.
Good thing I did a nandroid before wiping everything.
Anyone know if anyone is able to flash TMO ROM's?
My flash-finger is trembling.
I unplugged, removed battery, tried every combination.
I honestly dont have a clue how to do what you just said.. copy it only an external sd card but how would i carry it over and restore from it if it wont boot up?
vince24L said:
I unplugged, removed battery, tried every combination.
I honestly dont have a clue how to do what you just said.. copy it only an external sd card but how would i carry it over and restore from it if it wont boot up?
Click to expand...
Click to collapse
Your other option is to take it back to the store and tell them it wouldnt boot up after you charged it. Play dumb and they should exchange it at the shop.
Mark.
mine says fail in 1st box in odin
---------- Post added 24th June 2012 at 12:00 AM ---------- Previous post was 23rd June 2012 at 11:55 PM ----------
my phone is basically bricked, i take out battery and it says i need to open kies and go into recovery mode...?
nay12x said:
mine says fail in 1st box in odin
---------- Post added 24th June 2012 at 12:00 AM ---------- Previous post was 23rd June 2012 at 11:55 PM ----------
my phone is basically bricked, i take out battery and it says i need to open kies and go into recovery mode...?
Click to expand...
Click to collapse
The phone says that with the battery out?
What did you do to brick it in the first place? Flash a boot image or Rom?
Try Odin a few times it may go through eventually.
Mark.
mskip said:
Try Odin a few times it may go through eventually.
Mark.
Click to expand...
Click to collapse
When all else fails...this has always brought my sgs 2 back to life.
SGS3 awaiting some dev love
Life saver!!!!! Thanks!!!
mskip said:
Your other option is to take it back to the store and tell them it wouldnt boot up after you charged it. Play dumb and they should exchange it at the shop.
Mark.
Click to expand...
Click to collapse
Is that XDA's stance on the risks of flashing/modding phone? Play dumb? Isn't that how this thread got started?
Surprised a senior moderator would suggest that.
I think we all know the risks...and when mistakes are made...the person making the mistake should pay. Not the company who plays no fault or the customers who's rates are hiked because of fraudulent claims.
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2
Well I am a royal idiot. I flashed the omega rom v6 and now my GS3 will not even turn on!!! Is there any hope for me...? Some people haven't even received their phones so I can't get another one soon...
baublitz said:
Well I am a royal idiot. I flashed the omega rom v6 and now my GS3 will not even turn on!!! Is there any hope for me...? Some people haven't even received their phones so I can't get another one soon...
Click to expand...
Click to collapse
Can you get into the Download mode or is it just totally dead (no lights, no power when you turn it on)?
Mark.
Hello everyone.
To make a long story short, I let was stupid and let me 1 year old daughter play with my phone while I changed her. She started to chew on it and now the screen wont work. It boots up just fine and I can enter TWPR recovery just fine, but since the screen isn't working I don't know how to do anything.
Do you guys know how to fix this?
If there is no way to fix it, do I have to reset my phone back to stock before sprint will look at it? If that is the case, then how do I get back to stock without having to use the touch screen?
I tried to do some searching before making this post, but everything I saw told me to use the volume up and down button while in recovery, but that doesn't seem to work.
Any help or advice is greatly appreciated, I'm a noob when it comes to these things.
Thanks.
fmjswitch said:
Hello everyone.
To make a long story short, I let was stupid and let me 1 year old daughter play with my phone while I changed her. She started to chew on it and now the screen wont work. It boots up just fine and I can enter TWPR recovery just fine, but since the screen isn't working I don't know how to do anything.
Do you guys know how to fix this?
If there is no way to fix it, do I have to reset my phone back to stock before sprint will look at it? If that is the case, then how do I get back to stock without having to use the touch screen?
I tried to do some searching before making this post, but everything I saw told me to use the volume up and down button while in recovery, but that doesn't seem to work.
Any help or advice is greatly appreciated, I'm a noob when it comes to these things.
Thanks.
Click to expand...
Click to collapse
If your screen is unresponsive you and use odin to go back to stock with a .tar file if you can find the right one.
Or buy a 3rd party screen with digitizer and replace it yourself. Their are tutorials on youtube for this.
Sent from a planet far far away.
You need to go into download mode. I dont remember the button combo, but its either VolUp+Power or VolDown+Power (hold it) while the phone is off to get into download mode and be able to see it in ODIN.
CNexus said:
You need to go into download mode. I dont remember the button combo, but its either VolUp+Power or VolDown+Power (hold it) while the phone is off to get into download mode and be able to see it in ODIN.
Click to expand...
Click to collapse
Is VolDown+Home+Power
Sent from my SPH-L710
Speedin07si said:
If your screen is unresponsive you and use odin to go back to stock with a .tar file if you can find the right one.
Or buy a 3rd party screen with digitizer and replace it yourself. Their are tutorials on youtube for this.
Sent from a planet far far away.
Click to expand...
Click to collapse
A new problem has occurred. For some reason it wont let me access recovery or download mode, it just boots up like normal..... how screwed am I now....
Your backup would be a good place to start, actually. I would certainly do that if I were you. If that does not fix it, I would say you might have hardware issues, and you may need to replace the screen.
---------- Post added at 09:29 PM ---------- Previous post was at 09:25 PM ----------
fmjswitch said:
A new problem has occurred. For some reason it wont let me access recovery or download mode, it just boots up like normal..... how screwed am I now....
Click to expand...
Click to collapse
Use Volume Up+Home+Power to get into CWM or TWRP recovery. Vol Down+Home+Power should get you into stock recovery, or Odin mode as I call it. Also, pull the battery if you cannot get into it. Sometimes that helps.
fmjswitch said:
Hello everyone.
To make a long story short, I let was stupid and let me 1 year old daughter play with my phone while I changed her. She started to chew on it and now the screen wont work. It boots up just fine and I can enter TWPR recovery just fine, but since the screen isn't working I don't know how to do anything.
Do you guys know how to fix this?
If there is no way to fix it, do I have to reset my phone back to stock before sprint will look at it? If that is the case, then how do I get back to stock without having to use the touch screen?
I tried to do some searching before making this post, but everything I saw told me to use the volume up and down button while in recovery, but that doesn't seem to work.
Any help or advice is greatly appreciated, I'm a noob when it comes to these things.
Thanks.
Click to expand...
Click to collapse
Try THIS.
I got stuck at the boot screen with no OS installed.
Google is finding me ways to reboot but can't find anything on how to do a hard shutdown from here.
EDIT:
Okay one suggestion was to plug the phone into charge, then force a reboot (power + both volume buttons held down 10+ seconds).
Then when it shuts off, you disconnect the power cable after seeing a "battery" on the screen and the tab will remain turned off.
That did not work for me with computer data charging cable.
But it did work with the stock charger. :good:
This helped me get into download using the download mode button shortcuts. But I can't figure out how to get into recovery mode from here? The recovery mode buttons don't work (volume up + power + home).
It looks like this thread has the answer on how to get into recovery mode again.
Too bad I didn't find it before I did an ODIN back to stock.
http://forum.xda-developers.com/galaxy-tab-s/help/to-event-soft-brick-disaster-t2838473
Actually its even easier than that and have done it countless times.
Next time just hold POWER +VOL DOWN + HOME. As soon as the screen goes blank change to VOL UP whilst still holding POWER +HOME.
Works every time to get into recovery.
ashyx said:
Actually its even easier than that and have done it countless times.
Next time just hold POWER +VOL DOWN + HOME. As soon as the screen goes blank change to VOL UP whilst still holding POWER +HOME.
Works every time to get into recovery.
Click to expand...
Click to collapse
Confirmed - this worked for me. Thanks!
I'm in the same situation where all of a sudden my tablet went into reboot and got stuck on the logo screen. I tried the combinations suggested such as : Power butto +Volume down then Volume up when screen is black to get to reboot mode but it just brings me back to the logo screen. Is there some other way I can access the safe mode or recovery mode to try and get this thing working again? I wasn't running any apps for it to cause this either, just checking email. Any help would be much appreciated
casual167 said:
I'm in the same situation where all of a sudden my tablet went into reboot and got stuck on the logo screen. I tried the combinations suggested such as : Power butto +Volume down then Volume up when screen is black to get to reboot mode but it just brings me back to the logo screen. Is there some other way I can access the safe mode or recovery mode to try and get this thing working again? I wasn't running any apps for it to cause this either, just checking email. Any help would be much appreciated
Click to expand...
Click to collapse
You're not following the instructions properly. Read post 3 again and hold ALL 3 buttons until recovery boots.
Do not let go of any of the buttons until you see the recovery screen.
ashyx said:
You're not following the instructions properly. Read post 3 again and hold ALL 3 buttons until recovery boots.
Do not let go of any of the buttons until you see the recovery screen.
Click to expand...
Click to collapse
Nevermind, I actually got it to work. What do I do after it says "downloading" to fix this issue of it not getting past the boot screen? Please help, I'm not too good with this kind of stuff
casual167 said:
Nevermind, I actually got it to work. What do I do after it says "downloading" to fix this issue of it not getting past the boot screen? Please help, I'm not too good with this kind of stuff
Click to expand...
Click to collapse
Well, downloading is not the recovery.
In download mode you would use ODIN to re-flash the firmware from a computer.
In recovery, you would do a factory reset to reset back to defaults to see if that helps boot back into the existing firmware. You'll probably lose everything.
CZ Eddie said:
Well, downloading is not the recovery.
In download mode you would use ODIN to re-flash the firmware from a computer.
In recovery, you would do a factory reset to reset back to defaults to see if that helps boot back into the existing firmware. You'll probably lose everything.
Click to expand...
Click to collapse
Yeah I just figured out I was in the wrong mode. I couldn't get it to the recovery mode for some reason but eventually it worked. So I have to go into wipe data/factory reset option? There's nothing else I can do on that screen to fix this without losing everything? I see other opions to Wipe Cache, reboot to bootloader, reboot system now etc..
casual167 said:
Yeah I just figured out I was in the wrong mode. I couldn't get it to the recovery mode for some reason but eventually it worked. So I have to go into wipe data/factory reset option? There's nothing else I can do on that screen to fix this without losing everything? I see other opions to Wipe Cache, reboot to bootloader, reboot system now etc..
Click to expand...
Click to collapse
Well, you're not really giving enough info for us to properly help you.
If you have stock recovery then you can try clearing cache but it probably won't fix a no-boot situation.
If you have TWRP recovery then you can try clearing cache and dalvik and fix permissions which probably won't help but gives you a better chance.
Also, if you had TWRP then you could simply re-flash your ROM zip and not lose a whole lot.
CZ Eddie said:
Well, you're not really giving enough info for us to properly help you.
If you have stock recovery then you can try clearing cache but it probably won't fix a no-boot situation.
If you have TWRP recovery then you can try clearing cache and dalvik and fix permissions which probably won't help but gives you a better chance.
Also, if you had TWRP then you could simply re-flash your ROM zip and not lose a whole lot.
Click to expand...
Click to collapse
Sorry about that. It's like I said, I'm not too inclined on this type of stuff. Here's what I got and hopefully it helps you more. The tab is completely stocked, never rooted because I wouldn't even know how to do that really. I was on it fine last night and all I did was put it down for literally 30 sec to get something to drink and when I came back it was stuck on the Samsung logo screen. Only apps I had open was gmail, chrome and a word document. There was nothing dowloading, system wise or apps. It's already had Lollipop on it for a week or two and I didn't get any update notices or anything. So I'm guessing the problem is it's somehow stuck in a "boot loop" from what I found searching on google and I don't understand why or what could be causing it so that's the issue I'm trying to fix. I can't get past that screen no matter how many times I restart it. Does that help some?
casual167 said:
Does that help some?
Click to expand...
Click to collapse
Yeah, so unfortunately your options are very limited and you're kinda stuck with losing everything.
Try clearing cache first but I doubt it will help.
Then reset to factory defaults. That should work and you probably lose everything.
If not, then search this forum for "ODIN" and "firmware" or let me know and I'll guide you when I get back to my computer in a couple hours.
CZ Eddie said:
Yeah, so unfortunately your options are very limited and you're kinda stuck with losing everything.
Try clearing cache first but I doubt it will help.
Then reset to factory defaults. That should work and you probably lose everything.
If not, then search this forum for "ODIN" and "firmware" or let me know and I'll guide you when I get back to my computer in a couple hours.
Click to expand...
Click to collapse
Ok I'll give that a try, thanks. Should I take out my SD card before I reset everything
---------- Post added at 04:52 PM ---------- Previous post was at 04:15 PM ----------
casual167 said:
Ok I'll give that a try, thanks. Should I take out my SD card before I reset everything
Click to expand...
Click to collapse
So I did the factory reset, it started up now and it's as if I just took it out of the box. Unfortunately I'm at work though so I can't connect to a wifi to complete the set up process so I'll have to wait until tonight when I get home but thanks again for your help. If you could still help me later though with the Odin and firmware stuff I would appreciate it.
casual167 said:
So I did the factory reset, it started up now and it's as if I just took it out of the box. Unfortunately I'm at work though so I can't connect to a wifi to complete the set up process so I'll have to wait until tonight when I get home but thanks again for your help. If you could still help me later though with the Odin and firmware stuff I would appreciate it.
Click to expand...
Click to collapse
The factory reset should not touch the external SD card at all. So no worries about leaving it in during that process.
Yeah, starting over.
As long as you're doing that, this is a great time to flash a rooted ROM so you can install Titanium Backup and do regular backups of your apps in case you ever need to reset to factory again.
What model tab do you have? Like, mine is a T705.
If it's an LTE tab, who is your carrier?
The ODIN process depends on this info.
CZ Eddie said:
The factory reset should not touch the external SD card at all. So no worries about leaving it in during that process.
Yeah, starting over.
As long as you're doing that, this is a great time to flash a rooted ROM so you can install Titanium Backup and do regular backups of your apps in case you ever need to reset to factory again.
What model tab do you have? Like, mine is a T705.
If it's an LTE tab, who is your carrier?
The ODIN process depends on this info.
Click to expand...
Click to collapse
So I left for lunch and tablet was functional and in the set up process and when I came back, it's back at that damn Samsung logo screen and haven't been able to get back to the recover page. Any idea or suggestions on what to do now? How could that same problem still be here if I did the factory reset?
---------- Post added at 07:00 PM ---------- Previous post was at 06:59 PM ----------
casual167 said:
So I left for lunch and tablet was functional and in the set up process and when I came back, it's back at that damn Samsung logo screen and haven't been able to get back to the recover page. Any idea or suggestions on what to do now? How could that same problem still be here if I did the factory reset?
Click to expand...
Click to collapse
Actually, I just got into the recovery page now
---------- Post added at 07:02 PM ---------- Previous post was at 07:00 PM ----------
What should I do ?
CZ Eddie said:
What model tab do you have? Like, mine is a T705.
If it's an LTE tab, who is your carrier?
The ODIN process depends on this info.
Click to expand...
Click to collapse
casual167 said:
How could that same problem still be here if I did the factory reset?
Click to expand...
Click to collapse
Who knows, something is not happy though.
You could try another reset.
Is your battery greater than 50%?
Under a certain percentage, the battery savings feature could possible do weird things.
CZ Eddie said:
Who knows, something is not happy though.
You could try another reset.
Is your battery greater than 50%?
Under a certain percentage, the battery savings feature could possible do weird things.
Click to expand...
Click to collapse
Lol yea no kidding. The battery has been plugged in the whole time. I'm actually at 100% now. I was really trying to avoid having to bring it to Geek squad. If I do the reset and it does it again, will going to the download mode and doing the custom OS help at all?
casual167 said:
If I do the reset and it does it again, will going to the download mode and doing the custom OS help at all?
Click to expand...
Click to collapse
Unless it's a hardware issue, then re-flashing the firmware via ODIN could definitely help!
You can ODIN the stock, unrooted firmware or you can ODIN a TWRP recovery and flash any ROM you want for your phone.
Would still need to know the model # I asked for a couple times above.
CZ Eddie said:
Unless it's a hardware issue, then re-flashing the firmware via ODIN could definitely help!
You can ODIN the stock, unrooted firmware or you can ODIN a TWRP recovery and flash any ROM you want for your phone.
Would still need to know the model # I asked for a couple times above.
Click to expand...
Click to collapse
My bad, its SM-T800
---------- Post added at 08:02 PM ---------- Previous post was at 07:46 PM ----------
Leaving now but I'll be back in a couple hrs
casual167 said:
My bad, its SM-T800
Click to expand...
Click to collapse
Okay great, so you can ODIN a TWRP recovery and then flash a nice ROM. Same ROM I use on my phone. It's stock Touch Wiz that has been rooted and some small things have been improved. Very stable. IronROM.
Or you can download the stock firmware from sammobile.com and ODIN back to stock.
My Pixel XL is now dead. Won't turn on when pressing or long pressing or long pressing the power button for 5 minutes.
Long pressing the volume down and power button leads to vibration feedback but the screen is black, can't even get to the bootloader.
Last thing before it bricked is browsing through my photos, my phone suddenly froze as usual. And then it powered off automatically. After that, I can't get into the system, neither the bootloader.
Anybody know how to fix hard bricked Pixel?
Thx.
Queentus said:
My Pixel XL is now dead. Won't turn on when pressing or long pressing or long pressing the power button for 5 minutes.
Long pressing the volume down and power button leads to vibration feedback but the screen is black, can't even get to the bootloader.
Last thing before it bricked is browsing through my photos, my phone suddenly froze as usual. And then it powered off automatically. After that, I can't get into the system, neither the bootloader.
Anybody know how to fix hard bricked Pixel?
Thx.
Click to expand...
Click to collapse
try this one here
if not, call harware support for a possible rma
reyscott said:
try this one here
if not, call harware support for a possible rma
Click to expand...
Click to collapse
Won't work cause I can't even get to the bootloader. Thx anyway.
call google support to initiate RMA.
There is no laymans method to fix a hard bricked Pixel.
Only soft bricks.
CZ Eddie said:
There is no laymans method to fix a hard bricked Pixel.
Only soft bricks.
Click to expand...
Click to collapse
Thanks for the reply.
My Pixel is already on it's way to RMA.
My Pixel XL shut down this morning. After several attempts to restart, it hung on the Google splash screen. I got into bootloader and tried to reflash OPR3 with flash-all.bat. It got a little ways but quit with “remote: flash write failure”. I got into bootloader again and tried the reflash again. It got the same error earlier in the process and ever since, no button combinations will get it to turn on and I get no lights or battery image when plugged in.
When I plug it into my computer, I get the connection beep from the computer, but no evidence of a connection in Device Manager or in remove media. Since my computer recognizes the phone somehow, is there a way to retrieve data from my phone? I have seen many references to programs that can do this, but I am skeptical. My warranty replacement has been ordered, but I'd like to get whatever I can before it gets here.
Same thing happened to me last night. RMA is on its way, but this month old Pixel XL is dead.
CZ Eddie said:
There is no laymans method to fix a hard bricked Pixel.
Only soft bricks.
Click to expand...
Click to collapse
do you have an advanced guide to fix it? I have pixel past warranty that has the same problem
JimSmith94 said:
My Pixel XL shut down this morning. After several attempts to restart, it hung on the Google splash screen. I got into bootloader and tried to reflash OPR3 with flash-all.bat. It got a little ways but quit with “remote: flash write failure”. I got into bootloader again and tried the reflash again. It got the same error earlier in the process and ever since, no button combinations will get it to turn on and I get no lights or battery image when plugged in.
When I plug it into my computer, I get the connection beep from the computer, but no evidence of a connection in Device Manager or in remove media. Since my computer recognizes the phone somehow, is there a way to retrieve data from my phone? I have seen many references to programs that can do this, but I am skeptical. My warranty replacement has been ordered, but I'd like to get whatever I can before it gets here.
Click to expand...
Click to collapse
There are 2 things you can try 1.) Go-to you folder where you have adb & fastboot. Download factory zip and unzip into adb & fastboot folder. Plug phone into PC. Open a cmd window that's NOT the administrator one try adb devices, then fastboot reboot bootloader. Click once to advance in cmd, then double click flash-all.bat and let it run through the install process. It will stop a few time, but just ignore, may even spit out an error, just ignore and let it keep installing, it may keep doing this stop and start thing,let it run. It will eventually boot up. It will wipe phone and you will have to do a new phone install. Then you can go into bootloader mode and fastboot twrp and twrp installer and go back and install super su go back and install suhide 109.
When installing TWRP I would recommend the previous version of December 1, I think and not the Dec. 15 version. Same with twrp installer.
The other thing you can try is to (if you can turn phone off) hold down power button for 5 seconds then press volume UP , that should put you in the Android on it's back and say No Command. Then you can use the options given you.
Good luck
fiverings said:
There are 2 things you can try 1.) Go-to you folder where you have adb & fastboot. Download factory zip and unzip into adb & fastboot folder. Plug phone into PC. Open a cmd window that's NOT the administrator one try adb devices, then fastboot reboot bootloader. Click once to advance in cmd, then double click flash-all.bat and let it run through the install process. It will stop a few time, but just ignore, may even spit out an error, just ignore and let it keep installing, it may keep doing this stop and start thing,let it run. It will eventually boot up. It will wipe phone and you will have to do a new phone install. Then you can go into bootloader mode and fastboot twrp and twrp installer and go back and install super su go back and install suhide 109.
When installing TWRP I would recommend the previous version of December 1, I think and not the Dec. 15 version. Same with twrp installer.
The other thing you can try is to (if you can turn phone off) hold down power button for 5 seconds then press volume UP , that should put you in the Android on it's back and say No Command. Then you can use the options given you.
Good luck
Click to expand...
Click to collapse
My post was over three months ago and as I said, I got a refurb replacement, which I have since sold and have a Pixel 2 XL. Guess I should have said that although my computer recognized it, adb didn't. That's why I was asking if there was any other way to retrieve the data. I ended up using a week old backup so it wasn't too bad.
I tried to install a custom rom, and it didn't boot, so I tried to restore backup with twrp. Now no power, no vibration. PC doesn't recognize it. I wonder if it's on, and just has to run out of power, to be able to boot back to recovery. I thought it was weird my twrp backup didn't take very long. Any other advice? I got mine Verizon unlocked refurbished off amazon.
---------- Post added at 07:30 PM ---------- Previous post was at 06:53 PM ----------
perfectswanson said:
I tried to install a custom rom, and it didn't boot, so I tried to restore backup with twrp. Now no power, no vibration. PC doesn't recognize it. I wonder if it's on, and just has to run out of power, to be able to boot back to recovery. I thought it was weird my twrp backup didn't take very long. Any other advice? I got mine Verizon unlocked refurbished off amazon.
Click to expand...
Click to collapse
I was able to get it to boot into twrp. Should be OK from here. Thank you.
perfectswanson said:
I tried to install a custom rom, and it didn't boot, so I tried to restore backup with twrp. Now no power, no vibration. PC doesn't recognize it. I wonder if it's on, and just has to run out of power, to be able to boot back to recovery. I thought it was weird my twrp backup didn't take very long. Any other advice? I got mine Verizon unlocked refurbished off amazon.
---------- Post added at 07:30 PM ---------- Previous post was at 06:53 PM ----------
I was able to get it to boot into twrp. Should be OK from here. Thank you.
Click to expand...
Click to collapse
Even i am facing the same issue on the Verizon unlocked phone. What did you do to get into twrp??
nikinnikin said:
Even i am facing the same issue on the Verizon unlocked phone. What did you do to get into twrp??
Click to expand...
Click to collapse
I'm sorry I should have responded sooner. I don't remember much, but I had a feeling that it was still running because it was warm so I left it alone for a couple hours to see if it would die and then I could try to boot it again it's exactly what I did but what was funny was that it still had battery life when I turned it back on I hope you had some some luck.
nikinnikin said:
Even i am facing the same issue on the Verizon unlocked phone. What did you do to get into twrp??
Click to expand...
Click to collapse
Son of a gun. I did it again! Today. I followed a guide telling me to uninstall magisk with twrp before flashing 9.0. Now I have the same problem again. Goddamn TWRP. It told me no OS installed. Then I realized I forgot to put the magisk uninstaller file on my Verizion Pixel XL. Last time I just let my phone sit for a few hours or so, and it boot again. Not sure if it needs to run out of power, so it can boot again or what. Do you remember what you did when it happened to you?
perfectswanson said:
Son of a gun. I did it again! Today. I followed a guide telling me to uninstall magisk with twrp before flashing 9.0. Now I have the same problem again. Goddamn TWRP. It told me no OS installed. Then I realized I forgot to put the magisk uninstaller file on my Verizion Pixel XL. Last time I just let my phone sit for a few hours or so, and it boot again. Not sure if it needs to run out of power, so it can boot again or what. Do you remember what you did when it happened to you?
Click to expand...
Click to collapse
I couldnt switch it on at all. I'm planning to take it to Ubreakifix store, I guess they are the official google pixel repair people.
nikinnikin said:
Even i am facing the same issue on the Verizon unlocked phone. What did you do to get into twrp??
Click to expand...
Click to collapse
nikinnikin said:
I couldnt switch it on at all. I'm planning to take it to Ubreakifix store, I guess they are the official google pixel repair people.
Click to expand...
Click to collapse
You gotta be kidding me. Last time I left the phone alone, and my hunch was that it would run out of power, and then you can atleast get into the bootloader. I fixed it before. I wish I could get a hold of software those guys use to repartition, or however they do it. We have Pixel 3 leaks, but no repair software. All I did was install TWRP, and it said no OS installed. It just kept booting up into TWRP. Then I switched slots to see if that would change it, but I think that might have been what screwed it up.
---------- Post added at 01:37 PM ---------- Previous post was at 01:36 PM ----------
What version of TWRP did you use?
---------- Post added at 01:50 PM ---------- Previous post was at 01:37 PM ----------
I just got back into the bootloader. After a dozen times I just held down and power for like five seconds. Should I try recovery and try to remove Magisk, or should I just try to flash 9.0?
---------- Post added at 01:53 PM ---------- Previous post was at 01:50 PM ----------
What I did this time that was different, and I don't know if this is what helped or what, but this time I plugged in headphones and held power and vol down.
Putting the headphones in worked, or maybe it was just a fluke, but it worked on the first try. I got into Bootloader, "fastboot boot twrp.img", then I flashed the magisk uninstaller zip, the booted back to bootloader, and did flash-all.bat. It said it failed on the vendor partition, but everything still works.
Geez i wish haahwhahai would have a working erecovery. This is maddening.
I've been there before. I was able to use the method involving connecting / disconnecting the usb to get into fastboot, adb the recoveries, and reboot, being immediately prompted to factory restore. I don't know if that's helpful at all.
johncro13 said:
I've been there before. I was able to use the method involving connecting / disconnecting the usb to get into fastboot, adb the recoveries, and reboot, being immediately prompted to factory restore. I don't know if that's helpful at all.
Click to expand...
Click to collapse
Do you have a link to this method of restoring kind sir?
Thanks!
If possible, turn the phone completely off.
Plug the USB cable into the phone
Hold vol down
Hold power and IMMEDIATELY plug the other end of the USB cable into the PC.
This should get you into fastboot. From here, you should be able to use ADB.
Here's the thread that helped me most.
johncro13 said:
If possible, turn the phone completely off.
Plug the USB cable into the phone
Hold vol down
Hold power and IMMEDIATELY plug the other end of the USB cable into the PC.
This should get you into fastboot. From here, you should be able to use ADB.
Here's the thread that helped me most.
Click to expand...
Click to collapse
What should i use after i'm in fastboot? I've downloaded the latest full firmware that's out there, but it seems to be corrupt.
lowspeed said:
What should i use after i'm in fastboot? I've downloaded the latest full firmware that's out there, but it seems to be corrupt.
Click to expand...
Click to collapse
Is your bootloader unlocked?
smokinjoe2122 said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
Relocked
lowspeed said:
Relocked
Click to expand...
Click to collapse
I'm not sure how much you can do if the device is locked...A guess a few questions (In my tech support voice):
1.) How did it get to that point?
2.) Can you re-open the bootloader, and if you can, are you opposed to it?
3.) What was the last firmware you installed on it?
smokinjoe2122 said:
I'm not sure how much you can do if the device is locked...A guess a few questions (In my tech support voice):
1.) How did it get to that point?
2.) Can you re-open the bootloader, and if you can, are you opposed to it?
3.) What was the last firmware you installed on it?
Click to expand...
Click to collapse
1) I don't recall.
2) I could probably unlock it again. i'll give it a try.
3) it had some weird restore that i used, but that rom didn't have any update option.
I must sound retarded....
lowspeed said:
1) I don't recall.
2) I could probably unlock it again. i'll give it a try.
3) it had some weird restore that i used, but that rom didn't have any update option.
I must sound retarded....
Click to expand...
Click to collapse
Well most of the time, if it's a software issue, it's fixable. I don't know as much about this phone as I'd like, but I do know there's update packages out there you can use to your benefit if you can get the bootloader unlocked. I believe the Update.APP can even be unzipped or decompiled to get the main imgs from it, such as boot, recovery, and system.
im gonna go ahead and throw this out there. i just returned from the hardest brick i have ever done. i managed to make it so the phone wouldnt boot it would bootloop twice and go to erecovery and fail to restore. then i tried flashing the stock img's extracted from the update.app inside twrp and that made it worse. the screen went completely black and wouldnt do ****, the computer recognized it in bootloader mode but i couldnt flash a single thing as it would say i didnt have permission to or something like that(acting as if the bootloader was locked even though it was unlocked, or locked frp) i was about to give up and put my sim card back in my nexus as no matter what i did i couldnt get the screen to even turn on.
Well i found a post on the mate 9 sub-forum about someone who did the same thing and fixed it with dc-phoenix but costed him 18$, i decided 18 was worth it if it meant i had a working phone. and sure enough 5 minutes after paying and clicking flash update.app in the software it was up and running. now i have no idea how dc-phoenix can flash images when adb couldnt...but it works. if your out of options i would 100% say try it as 18$ is much better than a new phone.
---------- Post added at 07:55 PM ---------- Previous post was at 07:54 PM ----------
something i did notice as the software did the commands to flash each image i noticed it started its commands with some kind of backdoor command. so maybe they know a backdoor to bypass a locked bootloader/frp
darkmage1991 said:
im gonna go ahead and throw this out there. i just returned from the hardest brick i have ever done. i managed to make it so the phone wouldnt boot it would bootloop twice and go to erecovery and fail to restore. then i tried flashing the stock img's extracted from the update.app inside twrp and that made it worse. the screen went completely black and wouldnt do ****, the computer recognized it in bootloader mode but i couldnt flash a single thing as it would say i didnt have permission to or something like that(acting as if the bootloader was locked even though it was unlocked, or locked frp) i was about to give up and put my sim card back in my nexus as no matter what i did i couldnt get the screen to even turn on.
Well i found a post on the mate 9 sub-forum about someone who did the same thing and fixed it with dc-phoenix but costed him 18$, i decided 18 was worth it if it meant i had a working phone. and sure enough 5 minutes after paying and clicking flash update.app in the software it was up and running. now i have no idea how dc-phoenix can flash images when adb couldnt...but it works. if your out of options i would 100% say try it as 18$ is much better than a new phone.
---------- Post added at 07:55 PM ---------- Previous post was at 07:54 PM ----------
something i did notice as the software did the commands to flash each image i noticed it started its commands with some kind of backdoor command. so maybe they know a backdoor to bypass a locked bootloader/frp
Click to expand...
Click to collapse
Which files did you flash in DC Phoenix?
Thanks for posting this!
JDBarlow said:
Which files did you flash in DC Phoenix?
Thanks for posting this!
Click to expand...
Click to collapse
downloaded the latest update on firmware finder for my device(l24) and used winrar to pull the update.app from the zip. then you select that in dc phoenix to do the restore/flash