Related
This thread is here to inform people that if they try to flash anything through rom tools of any type they might "brick" or "soft brick" their phone or have a bootloader loop with samsung logo as I do. As of right now I am working on unsoftbricking my phone because I tryed flashing fonts and a bootloading screen. While the chance there is that it will softbrick vs flashing successfully.since I had several flash fonts go off without a problem and just never stuck, I assumed everything was ok. After deleting my current rom and going back to my stock rom i thought back at what steps i took to arrive at my bootloader loop it was after a few apps I downloaded from the market.Oden Flasher (not saying in anyway that was the cause) was one of them (blue android with black lighting down the middle). Now I am unsure if this is the "root" cause (pun intended, for those that think im talking about root access im not its just a joke). I am tyring to load a stock rom ATM via "Samsung Galaxy S3 ToolKit v2.3.0". So far no luck and it still stays at the samsung screen. I can get into Odin mode and get into recovery mode. when i try to manually load a rom i get e: signature verification failed and it aborts install. the only answer i have found was from an s2 device to basically create and load a temp recovery made by adb programing. I beleive i can do it but i havent seen anything on the SIII device for sprint and really dont want to try it unless i know that is the right way to go. Ill keep everyone posted so if they have or had the same problem this might be an answer. I will gladly take advice from someone with the right knowlege please. Thank you.
***UPDATE*** IM STILL LEARNING AND I HAVE CONTINUALLY SEARCHED THESE FORUMS FOR ANSWERS UNSURE OF.
***UPDATE*** INSURE YOUR PHONE!!!
I was finally able to recover a new phone. Sprint was actually the one that suggested this to me...
If you screw up your phone and don’t have insurance to replace the one bricked or soft brick revert back to a prior model phone that you used past before your Samsung galaxy s3. Then activate your old phone. Activate insurance when you complete activation wait a day or two and bring in the one you messed up and have it replaced by acting as if you have no idea what happened. Tell them a friend that used to work for sprint tried to fix the phone and you have no idea if it was rooted or have any clue what root is and that he was using Odin to try and fix it (ONLY if they ask it was ever rooted even then you should act as if you have no clue). They should replace the device. This is not 100% guarantee but it worked for me. For all of you who messed up like I did I hope this information helps you acquire a new or factory refurbished phone. Good luck. I have made sure to back up every aspect of the phone as I was excited to receive this new device I knew nothing about and realized out of my own stupidity I only did a nandroid back up and it would never flash back because of careless mistakes and greedy want to have another cool rom all the time.
Thank you to all of you who devoted some time to help me with my stupidity!
I'm trying to figure out why you were trying to use Rom toolbox to change your boot logo.........
You clearly got this screen before it let you attempt changing it.....which device did you choose???
Rom toolbox is a very noob friendly way of doing small mods and the ONLY thing that is going to brick you under the "interface" menu is going to be the boot logo changer, and you STILL have to intentionally select a device you are not using to do it........
^^^Add that info to your OP so everyone knows you tried to flash it even tho it clearly shows not S3 compatibility
---------- Post added at 01:57 AM ---------- Previous post was at 01:53 AM ----------
Did you notify the app developer of his app shortcomings before attempting to chop into his revenues????
NOT VERY COOL MAN....:what:
---------- Post added at 02:00 AM ---------- Previous post was at 01:57 AM ----------
Did you notify the app developer of his app shortcomings before attempting to chop into his revenues????
NOT VERY COOL MAN....:what:
Put phone in download mode
Flash stock Odin
Done
And don't use the term brick....a brick is a useless lump of mass that has no power.
If you really have to use it...yours would be what some call a soft brick.
Sent from my SPH-L710 using xda app-developers app
I'm fairly certain if you flash anything using anything that can flash, you Might brick your device. Unless you know what your doing and even then **** happens.
Sent from Pluto.
Thanks for the info. It didn't brick my phone, but flashing a font from room toolbox cause my S3 to freeze at the boot logo, and I had to flash my back up
Sent from my SPH-L710 using xda premium
18th.abn said:
I'm trying to figure out why you were trying to use Rom toolbox to change your boot logo.........
You clearly got this screen before it let you attempt changing it.....which device did you choose???
Click to expand...
Click to collapse
no. I did not use that or get that screen. i never had that option and i never would have selected a device that was not of the same origin.
00mred00 said:
Put phone in download mode
Flash stock Odin
Done
And don't use the term brick....a brick is a useless lump of mass that has no power.
If you really have to use it...yours would be what some call a soft brick.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
done that nothing has happend. so when i finally was able to get back into my bootloader (after i have already restored it by flashing a boot image... even though i apperently dont know how to do that) everytime i tryed to manually flash the rom i got a sig ver fail. Im having a hard time trying to get a soft brick (sorry for the confusion im not good on terminologies) ive researched and come up with an answer from the s2 device when it comes to verification but i feel its a bit risky by loading a temp boot and then restoring cwm boot (actually making a temp bootloading program looks fun to me and plausable) but learning how to do all this is fun and experimental since i cant find a single post on what to do about my situation. im not just doing it to do it. i could just go buy a new phone but Im doing all this to learn it. i would appriciate it if people would stop harrassing me and just help me since i am willing to learn.
pitbull292006 said:
Thanks for the info. It didn't brick my phone, but flashing a font from room toolbox cause my S3 to freeze at the boot logo, and I had to flash my back up
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
your welcome. I do appologize since ive used the wrong terms. but that is exactly what happend to me and nothing i have tried or what i have researched has worked. ive tryed to flash my back up and i cant get it to work i just hangs. i tryed flashing a custom flash to get adb access and i still cant flash my backup. Ive flashed a few times using font flashes but everytime i tryed it i always restored my main back up first
Speedin07si said:
I'm fairly certain if you flash anything using anything that can flash, you Might brick your device. Unless you know what your doing and even then **** happens.
Sent from Pluto.
Click to expand...
Click to collapse
yes i am aware. that is why i am about to go into adb on my own and write out manually. I know how to do that. its just i dont know what to do to get it back. this is my problem. but i want to learn this stuff because i like doing it.
How the heck are you guys messing up switching fonts with RomToolbox. Never once had an issue and have changed it about once a week as the rom i'm on updates.
If you ODIN'd back to stock, it should work.
Did you ensure that everything got flashed in ODIN? Make sure you're flashing system, data, user data, boot/kernel etc.
Then repartition in Odin and flash those again.
It should work after rebooting. If it doesn't, I suspect its hardware failure and that you can get it replaced by going into the store.
Sent from my Sprint SGS3
yousefak said:
If you ODIN'd back to stock, it should work.
Did you ensure that everything got flashed in ODIN? Make sure you're flashing system, data, user data, boot/kernel etc.
Then repartition in Odin and flash those again.
It should work after rebooting. If it doesn't, I suspect its hardware failure and that you can get it replaced by going into the store.
Sent from my Sprint SGS3
Click to expand...
Click to collapse
yes. odin even said pass and it was green after all was completed. at this point I was starting to think it was hardware related and was going to reset the counter before turining it in for factory warrenty.
Thread cleaned
A little ribbing and fun when someone screws up is fine
But outright flaming and disrespect will NOT be tolerated
Thank you for your cooperation
Friendly Neighborhood Moderator
kennyglass123 said:
Thread cleaned
A little ribbing and fun when someone screws up is fine
But outright flaming and disrespect will NOT be tolerated
Thank you for your cooperation
Friendly Neighborhood Moderator
Click to expand...
Click to collapse
thank you! most appriciated
VenomousViper said:
yes. odin even said pass and it was green after all was completed. at this point I was starting to think it was hardware related and was going to reset the counter before turining it in for factory warrenty.
Click to expand...
Click to collapse
That seems like a solid course of action. Make sure you play dumb when you bring it into the store - Just say you left it on your nightstand, the charger wasn't plugged in, but it still wouldn't get past the boot screen in the morning.
The regular procedure is that they take out battery, reboot, check water damage, etc. without actually going into Download Mode.
Well... tbh I dont understand nothing. But try to abd install twrp2 instead CWM. And try to flash any ROM you have in your phone.
Sent from my phone...
Pull battery, reinsert, press and hold (in this order) vol (+), physical home button, then power. Hold all 3 until screen blinks a couple times, let off of power button but continue to hold vol (+) and Home. If you have a custom recovery, this should get you there.......
Problem being, if like u said in op you also flashed a boot logo(splash screen)different than boot animation - the boot logo is earlier in the boot process than recovery and when it gets corrupted, recovery options don't apply because the device won't be able to access it since the boot process is corrupted before the recovery
If it was ONLY a font that got you here, then you WILL be able to access recovery. Fonts are flashed to the /system partition, and if there in a problem , /system is the final step in the boot process and CANNOT NO-WAY cause ANY harm early enough in the boot process to prevent you from accessing recovery. So give it a try.
---------- Post added at 06:34 AM ---------- Previous post was at 06:21 AM ----------
The pic shows ROM toolbox font installer- highlighted is the default location for flashing the fonts
Below is root explorer showing the s3 filesystem fonts are in the correct directory as set as default for ROM toolbox.
So like I was saying, if it was just a font this is a very simple fix for you. Boot into recovery, flash a ROM which formats and writes /system, fixing any kind of error that installing a font could have caused
Personally if you have certain fonts you like to flash and after a successful change of fonts with what ever apps you use. I would then create a zip file with your fonts to flash in recovery when changing roms. Its what I have done without issue. I have even added the fonts folder to gapps for easy install
18th.abn said:
Pull battery, reinsert, press and hold (in this order) vol (+), physical home button, then power. Hold all 3 until screen blinks a couple times, let off of power button but continue to hold vol (+) and Home. If you have a custom recovery, this should get you there.......
Problem being, if like u said in op you also flashed a boot logo(splash screen)different than boot animation - the boot logo is earlier in the boot process than recovery and when it gets corrupted, recovery options don't apply because the device won't be able to access it since the boot process is corrupted before the recovery
If it was ONLY a font that got you here, then you WILL be able to access recovery. Fonts are flashed to the /system partition, and if there in a problem , /system is the final step in the boot process and CANNOT NO-WAY cause ANY harm early enough in the boot process to prevent you from accessing recovery. So give it a try.
---------- Post added at 06:34 AM ---------- Previous post was at 06:21 AM ----------
The pic shows ROM toolbox font installer- highlighted is the default location for flashing the fonts
Below is root explorer showing the s3 filesystem fonts are in the correct directory as set as default for ROM toolbox.
So like I was saying, if it was just a font this is a very simple fix for you. Boot into recovery, flash a ROM which formats and writes /system, fixing any kind of error that installing a font could have caused
Click to expand...
Click to collapse
Thank you for your advice. Ill try that before I turn it in. If i dont have insurance they will still replace it if i act dumb right? Just incase I will make sure i have insurance before going in. Thanks for helping me everyone with my screw up i never had this issue with HTC evo's and ive rooted, and flashed 2 of them and other HTC varients with out an issue. this is the first samsung and i cant figure it out on my own!
I continue get e: signature verification failed every time i try to load my recovery image, stock sprint imgs (every official one i can find), and still get the message every time. Ive never had this issue with HTC.
Have OneX which I applied Vendor/Supplier ICS/JB update too... resulted in ROM not bootable and only access to fastboot. Device can be sent for warranty but issue is Data Recovery for me (or the wife in this case) so happy to loose any warranty if I can access the Media/Photos etc.
Have run through HTC Dev site to get unlock code, my hope is that I can flash CWM Recovery to then enable mounting of 'SDCard' or media to PC to recover data. At present Fastboot connects to phone via PC and can run any command but ADB does not show any devices. As I've only worked with cooked ROMs on GalaxyS the HTC OneX is new ball park for me.
I have the All-in-one pack... would be interested to know if unlocking alone will allow ADB to work and in turn allow me to 'pull' data from the device? Alternatively I would then be looking to flash CWM to the device as next option...
HBoot is 1.12
Ver-main 2.17.980.6
Any ideas/help/direction to recovery the data is greatly appreciated.
yes you can unlock the bootloader and flash this recovery
http://db.tt/Krlm4dPs
Then enter it, go to mounts & storage - mount as usb mass storage (last option in the list)
What i did was, i enabled the autoupload of pictures to dropbox .....nice feature and maybe something that could help you too
Yeah data = priceless as it's our Baby girls first Xmas phots's etc... have just moved all PCs @ home to Ubuntu so hadn't quite got to figuring out data bakups etc. Warranty is only about another 3or4 months so would happily dismantle the phone if needed... will also get me out of the dog-house with the wife if I get the photo's back.
So the recovery rom in dropbox is CWM or something specific to this HBoot etc?
No its a general custom recovery that can be used on every hboot......and yeah those pictures are indeed priceless ! :thumbup:
Champion... any recommendations/links to a good guide to follow once I've been able to get data off the device as the Vendor/Carrier ROM is dead and i'll need to flash a full custom ROM next.
Here is a full guide........detailed questions can be posted here
http://forum.xda-developers.com/showthread.php?t=1843585
Hi... reading through that guide they've indicated that unlocking bootloader will wipe the phone? Are they meaning that flashing a new ROM will wipe the data... I've not been able to test process yet as phone went flat.
Yes it will wipe the phone to factory state.....don't know for sure if it will wipe sdcard, didn't think of that in the beginning
Any chance I can apply a Custom recovery without unlocking bootloader
If this was a Galaxy wouldn't be an issue as they obviously do something different with the OneX... I've read in places that it's called a /sdcard but the flash used is not that separate and factory reset may or maynot wipe that data? As the ROM is not accessible I can't get to enable usb debug mode and although flashboot responds at present I've never been able to get adb to display the OneX as a device...
Benatio99 said:
Any chance I can apply a Custom recovery without unlocking bootloader
Click to expand...
Click to collapse
Nope ! :thumbdown:
Can anyone confrim that a 'factory reset' wipes the personal phone data but leaves /sdcard alone?
I've relocked/unlocked the bootloader several times and never lost any data on sdcard.
Maybe adb only works in bootloader only on newer hboot versions? I gotta try on 1.39 when I get home...
---------- Post added at 05:01 PM ---------- Previous post was at 04:32 PM ----------
TToivanen said:
I've relocked/unlocked the bootloader several times and never lost any data on sdcard.
Maybe adb only works in bootloader only on newer hboot versions? I gotta try on 1.39 when I get home...
Click to expand...
Click to collapse
Edit: missed the last page again
I really don't know about the factory reset...
Adb in recovery and running os. Fastboot in bootloader
Success... thanks for the help. With CWM recovery was able to get adb working and pull all the media which will save me great pain. Now to get a new ROM loaded... after I had got everything off rebooted the phone now it's sitting @ HBoot: Checking SD Card upate...
Dunno if it thinks it's going to try and apply the update that made the mess in the first place?
Edit: Seems like it just didn't like the USB charging cable being plugged in. Now I just have to figure on how to restore someones backup or find a RUU...
I have pressed the force stop of music player and cleared the data and also clicked force stop on gallery and cleared the data ...all images and vedios and my music is deleted can I recover data pls help me :'(
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.
Hey guys,
So this is very stupid but I think my phone is ultra hard bricked.
Long story short: I updated to 5.1.1 and wiped cache afterward and boom nothing works now.
Before people are coming with solutions I'll tell you guys what I did and tried.
First of all the phones bootloader is locked and fastboot tells me I can't flash in a locked state.
I tried the Unbricking tool.
I tried Power reset
I tried reflashing all I could in fastboot but won't let me because of the locked state.
I can only access Fastboot (sometimes) and it can get to the start up screen where it says powered by android and then it shuts off again.
Maybe its worth mentioning - the LED notification is blue all the time.
I don't know what to do.... I can't send it in for RMA since I'm going on vacation in a few days and it would be impossible to go without it.
So if anyone got something in their sleeves please let me know. :crying:
Best regards
Christoffer
Contact 1+ support, a technician may make a remote session to rescue your device
---------- Post added at 12:53 AM ---------- Previous post was at 12:52 AM ----------
but did the unbricking tool say successul after a few minutes, or it failed?
You should be able to flash a stock image without OEM unlock or ADB enabled on the phone in fastboot using the stock recovery. If you can't access the recovery on the phone I would boot the stock recovery on your PC and attempt to flash a stock image from it.
As long as you can get to fastboot, you should be able to recover. From there you should be able to boot into recovery. If your on stock you can just factory reset, or try sideloading OTA- all.zip. A hard-brick is when your device doesn't power on, and you could still recover from that also.
Sent from my ONEPLUS A5010 using XDA Labs
A hard brick or even a brick by what u state means u have no life in the phone. U even stated your phone responds at times. Which means it's not bricked.
ChrisBG said:
Hey guys,
So this is very stupid but I think my phone is ultra hard bricked.
Long story short: I updated to 5.1.1 and wiped cache afterward and boom nothing works now.
Before people are coming with solutions I'll tell you guys what I did and tried.
First of all the phones bootloader is locked and fastboot tells me I can't flash in a locked state.
I tried the Unbricking tool.
I tried Power reset
I tried reflashing all I could in fastboot but won't let me because of the locked state.
I can only access Fastboot (sometimes) and it can get to the start up screen where it says powered by android and then it shuts off again.
Maybe its worth mentioning - the LED notification is blue all the time.
I don't know what to do.... I can't send it in for RMA since I'm going on vacation in a few days and it would be impossible to go without it.
So if anyone got something in their sleeves please let me know. :crying:
Best regards
Christoffer
Click to expand...
Click to collapse
When you get to fastboot try to boot TWRP, not install and then flash stock firmware first (there is some compiled one's here on xda without the whole rom).
If that doesnt work, try to flash a stock boot image.