Related
Is bricking your device easy to happen? I'm scared of bricking my phone. Can the phone still brick when you do everything correctly?
Anything is possible.
I took chances on all my phones and never had a problem .
sent from the Dark §¡3€
MarsHD2 said:
Is bricking your device easy to happen? I'm scared of bricking my phone. Can the phone still brick when you do everything correctly?
Click to expand...
Click to collapse
If you do everything correctly, most likely not. A lot of bricks occurs because of user error. Flashing the wrong Galaxy s2 ROM/recovery etc, on our devices... there are a total of 5 variants i think.. only two works with ours.. skyrocket and hercules (i727 and t989)
I haven't heard of any bricks that occurs for doing everything correctly.
I have read up on some rare cases where a phone just blacks out from normal use... from heating up... or just random stuff.. some of the users aren't even rooted. That is purely the fault of the hardware simply giving up.
It is very easy to Root our phone:
ODIN
Flash Recovery
Flash ROM or Superuser
you can even mess up on flashing the recovery but you can actually recover from it. You will get the message where it says "firmware update failed, please connect to kies and recover," this is easily recoverable.. You just go back to ODIN Mode and flash recovery again.
The only way you can BRICK the phone:
1. Flash a ROM that doesn't belong to our device.
2. Mess up on Flashing a Stock ROM (user fault) such as battery falling out.. battery dying.. cable falls out. cable is loose etc.. while in the middle of flashing.
I remember reading that people tried to flash a Modem that didn't belong to our device, but ODIN either prevented this from happening or you get the "firmware update failed..." message.
TL;DR: No it is fairly safe and the only chances of bricking is when flashing something that isn't for our phone.
1. Flash a ROM that doesn't belong to our device.
2. Mess up on Flashing a Stock ROM (user fault) such as battery falling out.. battery dying.. cable falls out. cable is loose etc.. while in the middle of flashing.
Click to expand...
Click to collapse
I still don't see how those two things can mess up the phone? Can't you just use odin to reflash? You would think that they make the download portion of the phone non-writable so you can always use it with odin to reflash in any state. I must be missing something here. Does flashing a ROM mess with the "Download" partition also?
It is normally unwritable to prevent such problems. By using odin, you are bypassing the safety feature of the ROM area. By interrupting the process mid-way, you might not do not copy over all the 'necessary' files for the phone to function at it's lowest levels of operation. IE turn on when you tell it to. Flashing a rom doesn't mess with the user accessible partition.
Is using ClockWorkMod to flash any safer?
Catch-22.
If you want to use the ClockWorkMod app to flash, you will need to grant it superuser permissions. How do you get superuser? You need to be rooted by installing ClockWorkMod.. odin is pretty safe. Make sure to have a half-way charged battery (at least), and click the pda button.
True but how about subsequent flashes
Look bro its hard to brick these samsung but its not impossible trust me i know from experience, my first ever phone i rooted and played with was the galaxy s 4g and lets just say i bricked the **** out of it. think of it like this you flash a rom for a phone that is not yours this phone has a physical keyboard and the only way that phone can get into download mode is a combination of keys on the keyboard (this is just hypothetical) and the only way to get odin to recognize device is to be in DL mode...How can you be in DL with a phone that doesnt have physical keyboard but requires use of it to get into DL mode.
I've never bricked. Been in a bootloop, but just had to wipe and flash again
Sent from my SGH-T989 using xda premium
jdubb1106 said:
Look bro its hard to brick these samsung but its not impossible trust me i know from experience, my first ever phone i rooted and played with was the galaxy s 4g and lets just say i bricked the **** out of it. think of it like this you flash a rom for a phone that is not yours this phone has a physical keyboard and the only way that phone can get into download mode is a combination of keys on the keyboard (this is just hypothetical) and the only way to get odin to recognize device is to be in DL mode...How can you be in DL with a phone that doesnt have physical keyboard but requires use of it to get into DL mode.
Click to expand...
Click to collapse
Get a jig?
Sent from my SGH-T989 using XDA App
jig didnt work on my sgs4g. And all that example was purely hypothetical, just using as example so op understands what people are trying to say.
Sent from my SGH-T989 using xda premium
jordanishere said:
Get a jig?
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
I tried to flash a kernel and a rom for the i9100 on mine using cwm. Flash went through just fine, went to reboot.... Nuthin. Not even a jig brought it back. Just be sure of what you're flashing and you'll be good. I've been flashing roms since the razr v3, and this is my first brick.
Sent from my Nexus One using Tapatalk
zak rabbit said:
I tried to flash a kernel and a rom for the i9100 on mine using cwm. Flash went through just fine, went to reboot.... Nuthin. Not even a jig brought it back. Just be sure of what you're flashing and you'll be good. I've been flashing roms since the razr v3, and this is my first brick.
Sent from my Nexus One using Tapatalk
Click to expand...
Click to collapse
Its tough with all the diff varients. doesnt help that they all have the exact same name too.
Props for not being one of the whiners who blames their brick on xda. hope you get a new t989.
Sent from my SGH-T989 using XDA App
Just to throw this in there - if your phone does ANYTHING when you try to turn it on (soft keys light up/some sort of response from the screen), or plug it in, it is a soft brick in which you should be able to recover the phone. Many times it takes multiple tries (due to picky button combos) but it will come back. Coming from the Vibrant 3g, I can tell you from experience that you know when you have a hard brick because the phone does not respond AT ALL. It doesn't do anything when it's plugged in or when buttons are pressed. The ONLY time I've legitimately bricked a sgs was when I flashed a rom on a low battery not knowing that the phone does not charge in recovery. The battery died during reboot and the phone would not respond to anything. This is a true hard brick.
Also i'm not sure if this has been said but I would never flash anything without art least 50% battery life
The galaxy is pretty cool because of how easy it is to unbrick. All you have to do it load the stock kernel from Odin and plug up the USB, mount the sd, and place the ROM onto the sd and unmount then flash it. In the case that you install a bad ROM, if it's just the kernel then just load the stock kernel with Odin then use the one you want.
Sent from my SGH-T989 using xda premium
iwasblown said:
The galaxy is pretty cool because of how easy it is to unbrick. All you have to do it load the stock kernel from Odin and plug up the USB, mount the sd, and place the ROM onto the sd and unmount then flash it. In the case that you install a bad ROM, if it's just the kernel then just load the stock kernel with Odin then use the one you want.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
that was very confusing, but I'm not sure if you really know what a true hard brick is, which is really hard to unbrick and need to do the jtag stuff.
what you addressed is a softbrick (i don't even consider this a brick because the phone turns on), which is flashing an incomplete rom or kernel that is for our device, however if it was another device's than it might lead to a hardbrick.
Teo032 said:
that was very confusing, but I'm not sure if you really know what a true hard brick is, which is really hard to unbrick and need to do the jtag stuff.
Click to expand...
Click to collapse
A true hard brick cannot be unbricked. With a true hard brick the phone won't turn on and therefore, you cannot use Odin. Jtag also won't work if the phone does not turn on/the hardware buttons don't work.
OK, so, my phone started displaying a static like image when I unlocked it, then eventually led to only working if I slid the screen up. I decided this may be a problem with the firmware so went to install Cyanogen 7.2 (I think it was) so I formatted system and the Cyanogen mod didn't install. Now my CWM only works when it feels like it, other times it sticks on the DoomKernal screen. If I try and put my phone into flash/fastboot mode the LED on the top will flash the colour which corresponds to the right mode, but after that it goes back to the DoomKernal screen.
Is there any way to fix this?
Pocoryu said:
OK, so, my phone started displaying a static like image when I unlocked it, then eventually led to only working if I slid the screen up. I decided this may be a problem with the firmware so went to install Cyanogen 7.2 (I think it was) so I formatted system and the Cyanogen mod didn't install. Now my CWM only works when it feels like it, other times it sticks on the DoomKernal screen. If I try and put my phone into flash/fastboot mode the LED on the top will flash the colour which corresponds to the right mode, but after that it goes back to the DoomKernal screen.
Is there any way to fix this?
Click to expand...
Click to collapse
Seems like a hardware issue. Might wanna check your flex cable. As for the CWM issue, my Play did that after being water damaged. Only certain ROMs would flash and my touch screen didn't work :S
Sent from my R800x using xda premium
CTU_Loscombe said:
Seems like a hardware issue. Might wanna check your flex cable. As for the CWM issue, my Play did that after being water damaged. Only certain ROMs would flash and my touch screen didn't work :S
Sent from my R800x using xda premium
Click to expand...
Click to collapse
Thanks man, I did discover that even when CWM looks like it isn't working, it's actually running but the screen hasn't changed
Installed CWM Recovery (recovery-clockwork-6.0.4.8-m8.img) using Fastboot,
and then installed UPDATE-SuperSU-v1.94.zip
then took a nandroid backup.
Booted into Android - no problems.
But now :
- when I power down it reboots straight into CWM Recovery.
- when I select the advanced options of CWM Recovery / Power Down,
it reboots into CWM Recovery.
- when I select Fastboot/Power Down it also reboots into CWM Recovery.
From CWM Recovery I can
Boot System Now
and it boots into the system,
But when I power down, it reboots again into CWM Recovery.
ie, I can't power down.
The above only happens if a power or usb cable is connected.
If no power cable is connected, it shuts down normally.
But, if after it is fully shut down, I connect a power cable,
it again boots, by itself, into CWM Recovery !!
Notes:
- A restart from Android does an actual restart into the phone OS, not into CWM Recovery.
- if I turn back on Power/Fastboot, then I can shutdown properly even with power connected,
so the problem happens when Fastboot is off.
Anybody have any idea what is causing this
and what I can do about it?
some things I can think of trying
but I don't want to make things worse.
Have done this before on a Galaxy Nexus with no problems,
and have put CyM on an S3 with no problems.
[previously posted in the wrong forum (M7) moved here.]
undecidable said:
Installed CWM Recovery (recovery-clockwork-6.0.4.8-m8.img) using Fastboot,
and then installed UPDATE-SuperSU-v1.94.zip
then took a nandroid backup.
Booted into Android - no problems.
But now :
- when I power down it reboots straight into CWM Recovery.
- when I select the advanced options of CWM Recovery / Power Down,
it reboots into CWM Recovery.
- when I select Fastboot/Power Down it also reboots into CWM Recovery.
From CWM Recovery I can
Boot System Now
and it boots into the system,
But when I power down, it reboots again into CWM Recovery.
ie, I can't power down.
The above only happens if a power or usb cable is connected.
If no power cable is connected, it shuts down normally.
But, if after it is fully shut down, I connect a power cable,
it again boots, by itself, into CWM Recovery !!
Notes:
- A restart from Android does an actual restart into the phone OS, not into CWM Recovery.
- if I turn back on Power/Fastboot, then I can shutdown properly even with power connected,
so the problem happens when Fastboot is off.
Anybody have any idea what is causing this
and what I can do about it?
some things I can think of trying
but I don't want to make things worse.
Have done this before on a Galaxy Nexus with no problems,
and have put CyM on an S3 with no problems.
[previously posted in the wrong forum (M7) moved here.]
Click to expand...
Click to collapse
Well I haven't had this happen to me ever so, not sure how much help I'll be but...
Have you tried reflashing CWM? Perhaps clear the cache? Try to flash TWRP and see if it does the same, can always flash CWM again afterwards.
BerndM14 said:
Well I haven't had this happen to me ever so, not sure how much help I'll be but...
Have you tried reflashing CWM? Perhaps clear the cache? Try to flash TWRP and see if it does the same, can always flash CWM again afterwards.
Click to expand...
Click to collapse
Yes, me neither.
My next step was the same as your suggestions,
a system reset, clear cache etc and to try flashing TWRP.
My worry is this powering on to recovery when I plug in the cable.
I was hoping to understand that a bit before trying too many things.
It is easier to make things worse than better!
undecidable said:
Yes, me neither.
My next step was the same as your suggestions,
a system reset, clear cache etc and to try flashing TWRP.
My worry is this powering on to recovery when I plug in the cable.
I was hoping to understand that a bit before trying too many things.
It is easier to make things worse than better!
Click to expand...
Click to collapse
Don't think a system reset is necessary just yet. First try to clear the cache and re-flashing CWM to see what it does. If nothing then you can try TWRP to see if it does the same thing.
Have you tried searching for a similar problem in the CWM thread if it's recovery related?
---------- Post added at 06:21 AM ---------- Previous post was at 06:10 AM ----------
undecidable said:
Yes, me neither.
My next step was the same as your suggestions,
a system reset, clear cache etc and to try flashing TWRP.
My worry is this powering on to recovery when I plug in the cable.
I was hoping to understand that a bit before trying too many things.
It is easier to make things worse than better!
Click to expand...
Click to collapse
I also just noticed the version number for the CWM you're using, are you sure that's the right version? What device variant are you using, International, Verizon etc?
I see only these versions for international
philz_touch_6.25.5-m8.img
philz_touch_6.26.6-m8.img
philz_touch_6.41.6-m8.img
philz_touch_6.43.6-m8.img
Maybe you have wrong version if you use international version.
Download newest one here and reflash. That is IF you use international.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/m8
BerndM14 said:
Don't think a system reset is necessary just yet. First try to clear the cache and re-flashing CWM to see what it does. If nothing then you can try TWRP to see if it does the same thing.
Have you tried searching for a similar problem in the CWM thread if it's recovery related?
Click to expand...
Click to collapse
A system reset is no problem. I already did one before starting, and it is new. So no data/apps to lose.
Yes, spent about 6 hours searching last night. Haven't come across anything like it.
Plus, there doesn't seem to be a CWM thread for the HTC One M8 - there are threads for TWRP and Philz (CWM Advanced).
got info below nevermind =oD
I also just noticed the version number for the CWM you're using, are you sure that's the right version? What device variant are you using, International, Verizon etc?
I see only these versions for international
philz_touch_6.25.5-m8.img
Click to expand...
Click to collapse
I'm not using philz, I'm using standard CWM:
http://clockworkmod.com/rommanager
which is the recommendation in the Cyanogenmod instructions:
http://wiki.cyanogenmod.org/w/Install_CM_for_m8
So I think my version of CWM is correct.
BerndM14 said:
Yeah just linked the same to you now as well. Where did you get that version from then?
Nevermind, I got where you downloaded it from http://forum.xda-developers.com/showthread.php?t=2708520
So you're on Verizon?
Click to expand...
Click to collapse
No, I have the international version, and the recovery is from
http://clockworkmod.com/rommanager
the last line on the page, labelled M8.
I think it is the official version.
Well it seems we're back to square one then, erase cache.
Hook up device to PC, go into fastboot, adb reboot bootloader
fastboot erase cache
If it doesn't work then try another recovery, Philz or TWRP. Did you want to flash CM hence why you followed their tutorial?
BerndM14 said:
Well it seems we're back to square one then, erase cache.
Hook up device to PC, go into fastboot, adb reboot bootloader
fastboot erase cache
If it doesn't work then try another recovery, Philz or TWRP. Did you want to flash CM hence why you followed their tutorial?
Click to expand...
Click to collapse
I always read about 20 tutorials first: some are vague, some unreliable, some incomplete, some assume you have more experience, to make sure I fully understand what I have to do.
I chose CWM because I've used it before on a Galaxy Nexus and an S3 and it has been reliable.
I will install Cyanogenmod as soon as it goes to Stable for the M8. I have it on the S3 and am over-the-moon happy with it. However that could be a year.
Might wait a day before I try flashing TWRP. See if I can discover more, or if anyone has an insight to offer. I mean, why would it boot when you plug in the power cable?! Too strange to not be cautious.
undecidable said:
I always read about 20 tutorials first: some are vague, some unreliable, some incomplete, some assume you have more experience, to make sure I fully understand what I have to do.
I chose CWM because I've used it before on a Galaxy Nexus and an S3 and it has been reliable.
I will install Cyanogenmod as soon as it goes to Stable for the M8. I have it on the S3 and am over-the-moon happy with it. However that could be a year.
Might wait a day before I try flashing TWRP. See if I can discover more, or if anyone has an insight to offer. I mean, why would it boot when you plug in the power cable?! Too strange to not be cautious.
Click to expand...
Click to collapse
It seems like it's an old issue with CWM though on various devices.
HTC Desire S same problem as you also CWM recovery.
Desire Z same problem also with CWM recovery.
Desire HD same problem ALSO CWM.
Don't know if there is a problem with CWM and HTC devices maybe...Those 3 are all for HTC devices. Though doing a google search you do get the same problem with different manufacturer phones also with CWM
BerndM14 said:
It seems like it's an old issue with CWM though on various devices.
HTC Desire S same problem as you also CWM recovery.
Desire Z same problem also with CWM recovery.
Desire HD same problem ALSO CWM.
Don't know if there is a problem with CWM and HTC devices maybe...Those 3 are all for HTC devices. Though doing a google search you do get the same problem with different manufacturer phones also with CWM
Click to expand...
Click to collapse
wow! Clearly the issue! And it seems changing recoveries fixes it. Will try in the next hour.
what was the search phrase you used? All I tried returned irrelevent results, though mostly I was using G not XDA.
As my father used to say, your blood is worth bottling (its a compliment).
thankyou!
undecidable said:
wow! Clearly the issue! And it seems changing recoveries fixes it. Will try in the next hour.
what was the search phrase you used? All I tried returned irrelevent results, though mostly I was using G not XDA.
As my father used to say, your blood is worth bottling (its a compliment).
thankyou!
Click to expand...
Click to collapse
https://www.google.co.za/search?q=w...ite:forum.xda-developers.com&biw=1920&bih=979
Tossed in plenty of keywords into google, of course doing it normally gives a lot of results from other sites too but I just decided to narrow it down to xda(Most sites refer help questions to xda anyways so...)
I think it's better to use Google for searches anyways, it records info from a lot of sites. XDA works on a "keyword" basis it seems and most people when making threads don't really add any keywords to it so finding it is difficult. Heck, I even had issues finding HTC__622 in a thread where I knew for a FACT HTC__622 was mentioned at least 4 times, the results in xda itself turned up nothing.
I didn't even bother to try and search within xda for this issues, went the Google route and narrowing it down to xda, much better :good:
Back to the issue though, it would still be interesting to know what actually causes it to boot into recovery when it gets plugged in, it's strange and I'm curious about it. I also think flashing either Philz or TWRP should help, there are quite a few people on here using Philz and I can't recall an issue like this being mentioned before so perhaps it's not a problem with Philz.
BerndM14 said:
Back to the issue though, it would still be interesting to know what actually causes it to boot into recovery when it gets plugged in, it's strange and I'm curious about it. I also think flashing either Philz or TWRP should help, there are quite a few people on here using Philz and I can't recall an issue like this being mentioned before so perhaps it's not a problem with Philz.
Click to expand...
Click to collapse
Thanks. I did try an XDA search from G, but you are just better at it
There is code that gets executed when you plug in the power cable:
it shows the battery charging.
The battery charging icon that is showing just before boot into CWM recovery is different from the normal battery charging icon (that I can see when I have settings /power / fastboot on).
I wonder if CWM changes that code? If that is the case, flashing TWRP might not fix it - will soon know.
Flashed TWRP
(openrecovery-twrp-2.7.1.0-m8.img)
much healthier but not completely normal.
Now, when I power-off,
1. initially this funny black/white battery charging logo appears
with words in red at the bottom like:
This build is for Developement Purposes only
Do not distribute outside of HTC
without HTC Permission...
Click to expand...
Click to collapse
2. Then the normal green battery icon appears
3. but then the TWRP screen appears and disappears.
4. For about 2 secs the TWRP screen may flash back briefly
before returning to the green battery icon with the backlight.
5. Then it settles on the green battery icon,
and the backlight stays on for about 10 secs.
6. then the screen switches off
and it really appears to be powered off.
But if I quickly 'touch' the power button
the TWRP screen briefly appears (with a lock over it) once
and then the green battery screen reappears.
If I unplug then replug in power,
the same things happens: steps 1-6 above.
Tried flashing TWRP 3 times - no change.
Will now try flashing philz.
undecidable said:
Flashed TWRP
(openrecovery-twrp-2.7.1.0-m8.img)
much healthier but not completely normal.
....
Will now try flashing philz.
Click to expand...
Click to collapse
Philz does exactly the same as CWM - not surprising given that it is CWM based.
So have returned to TWRP, which is at least usable.
Any idea how to file a bug against CWM?
Philz I can do on their forum here.
undecidable said:
Flashed TWRP
(openrecovery-twrp-2.7.1.0-m8.img)
much healthier but not completely normal.
Now, when I power-off,
1. initially this funny black/white battery charging logo appears
with words in red at the bottom like:
2. Then the normal green battery icon appears
3. but then the TWRP screen appears and disappears.
4. For about 2 secs the TWRP screen may flash back briefly
before returning to the green battery icon with the backlight.
5. Then it settles on the green battery icon,
and the backlight stays on for about 10 secs.
6. then the screen switches off
and it really appears to be powered off.
But if I quickly 'touch' the power button
the TWRP screen briefly appears (with a lock over it) once
and then the green battery screen reappears.
If I unplug then replug in power,
the same things happens: steps 1-6 above.
Tried flashing TWRP 3 times - no change.
Will now try flashing philz.
Click to expand...
Click to collapse
Well removing the red development purposes text is easy enough if you have S-OFF. Remove Red Text on Splash screen
I'm not sure if the same issue with CWM is applicable to all or most users of Philz on here, like I said before, I haven't noticed any threads popping up discussing the issue, unless they discussed it in Philz thread itself.
I myself haven't noticed the issue you have with TWRP, will look into it more as I get some time, gonna be a hectic week Personally I only use custom recovery when I need it, which isn't that often, not a big "flasher" of ROMs etc, so I'm on stock recovery.
BerndM14 said:
Well removing the red development purposes text is easy enough if you have S-OFF. Remove Red Text on Splash screen
I'm not sure if the same issue with CWM is applicable to all or most users of Philz on here, like I said before, I haven't noticed any threads popping up discussing the issue, unless they discussed it in Philz thread itself.
I myself haven't noticed the issue you have with TWRP, will look into it more as I get some time, gonna be a hectic week Personally I only use custom recovery when I need it, which isn't that often, not a big "flasher" of ROMs etc, so I'm on stock recovery.
Click to expand...
Click to collapse
Yes, found the post for Remove Red Text on Splash screen early this morning. Seems to be related to Root, and separate from the TWRP issue.
I have to wonder if the TWRP problems aren't caused by the initial flashing of CWM. Anyway will post the issue on the TWRP forum tomorrow and see what they say.
Seems Philz has had this problem before, it comes from CWM, and fixed it before.
I have to say, this is the last HTC phone I buy - Samsungs are so much friendlier to flashing. Also I greatly dislike the big Tampered sign.
Reason for flashing recovery this time is I wanted root so I could remove garbage from the phone.
I don't flash ROMs much. High learning curve and risky. I do just one flash: from stock to CyangenMod. so much nicer it is worth it. I have to say if I had to choose between my old S3 with CyanogenMod and a stock M8, it would be the S3. If I can't get the garbage off the M8, I will just put it in a drawer till CyM goes stable for it.
Solved: Power Down reboots into Recovery
undecidable said:
Seems Philz has had this problem before, it comes from CWM, and fixed it before.
Click to expand...
Click to collapse
The solution! From the Philz M8 thread.
http://forum.xda-developers.com/showthread.php?p=53464839
An earlier version of Philz: 6.26.6-m8.zip.
The earlier version doesn't have the problem.
Thanks to @donmarkoni
So I've kinda ****ed up.
I've been rooted for a while now and this is the first time I've broken anything. I'd just flashed a clean install of Pure Nexus 7.0 using TWRP and went back to install elemental x. I'd installed that but before rebooting decided to reflash the surround speakee mod, and this is where I **** up. "It'll be fine" I think, so I reboot, stuck in a bootloop, so I go back into TWRP and try to flash the recovery something about incorrect partition. ****. So in a last ditch effort I go back and wipe everything, now I just get stuck at the google logo. My phone sits on my desk powered of completly, any help would be much appreciated thanks.
Edit: Thanks guys, I flashed the stock image using fastboot (already had it installed anyway) and my phones back.. I'm typing this out on it. Thanks.
Revert to Stock
This post should fix your problems.
goo [dot] gl/u1GCXe
replace the [dot] with an actual period to get the url. It's basically just instructions for fixing soft-brick via Wugfresh's root toolkit
Chill mate, this has happened to me many times because I'm a ROM lover! Simply flash a stock img and everything will be just fine. If you're looking for an easy way then Google "Nexus toolkit" (latest version) and download it. Plug in your phone and relax. Or if your looking for a manual method then just go on to this thread! :good: http://forum.xda-developers.com/nexus-5x/general/tutorial-flash-factory-images-unroot-t3231627
DougleBi said:
So I've kinda ****ed up.
I've been rooted for a while now and this is the first time I've broken anything. I'd just flashed a clean install of Pure Nexus 7.0 using TWRP and went back to install elemental x. I'd installed that but before rebooting decided to reflash the surround speakee mod, and this is where I **** up. "It'll be fine" I think, so I reboot, stuck in a bootloop, so I go back into TWRP and try to flash the recovery something about incorrect partition. ****. So in a last ditch effort I go back and wipe everything, now I just get stuck at the google logo. My phone sits on my desk powered of completly, any help would be much appreciated thanks.
Click to expand...
Click to collapse
Strangely and inexplicably, this happens to me all the time, like every third boot or so(phone doesn't shut off too often). Normally, I just have to hold the power button(and sometimes vol down as well) for 20-30 seconds and the phone will reboot as usual, meaning I was actually never bricked and the boot loader is just tripping/glitching for whatever reason, probably over the encryption. If that doesn't work then before you get to the google logo(at boot splash screen) try rebooting into 'download mode', the option to enter download mode is 'hold volume down'(I think, could be 'hold vol up', it will say on screen) while booting. Go into download mode and flash the stock image with android studio. If that doesn't work(which it really should) then you're basically SOL, but I have to say it's nearly impossible to fully brick this phone. You'd literally have to be trying to brick it to make it FUBAR, so relax man. Just follow what people on here have said. You'll be back to flashing in no time.
rogerdcruz said:
Chill mate, this has happened to me many times because I'm a ROM lover! Simply flash a stock img and everything will be just fine. If you're looking for an easy way then Google "Nexus toolkit" (latest version) and download it. Plug in your phone and relax. Or if your looking for a manual method then just go on to this thread! :good: http://forum.xda-developers.com/nexus-5x/general/tutorial-flash-factory-images-unroot-t3231627
Click to expand...
Click to collapse
@ the op:
Good info here!! I suggest anyone who owns a Nexus learn how to install SDK and platform tools or at the least adb and fastboot and learn to use them. It's very simple and it's one of the great things about owning a Nexus. We don't have to use other things...I'm not a fan of toolkits and whatnot because if I were to just always use them I'd never learn and I like to learn even though I'm somewhat of a slow leaner. ;p I'll slap a link up in a few with detailed instructions on how to install just adb and fastboot in 20 seconds on Windows.... Super easy!!!! One more thing If your talking about the surround sound mod that allows both speakers to play my advice is be careful many things can mess up our phones. I've seen reports of that blowing the speaker. Just saying... Brb with link to 20 sec installer..
My bad it's 15 seconds. ;p
http://forum.xda-developers.com/showthread.php?t=2588979&page=89
Sent from my Nexus 5X using XDA Labs
ok so bottom line is, I was in the middle of flashing official rom when at about 25% it failed. Don't ask why! (i still had recovery at this point) so I went ahead and cleaned absolutely everything thinking i'll just try and reflash as before. Now with power lead out it won't switch on at all and when power is supplied it shows message "An error has occured while udating the device software." loops at approx 3 sec intervals cant do anything with it.
Ive tried everything I can think of all to no avail! yes its my own fault bla bla bla just wondering if i act have f***** it.
Thanks to anyone with any ideas
You probably going to get a better help at TAB S2 board this is for the tab S1.
If it is hard bricked there is JTAG methods that can help, just need to find one for your device, not easy though.
But all I can do is share my experience with something like this, in a more "cheap" way than JTAGs, dunno if it helps:
I never had a similar problem on the tab S. But in the past a galaxy player 5.0 of mine had a very similar problem (as far I remember the screen just powered the back light but without any letters or simbols)
in 2012, I bricked it trying to mount a swap partition (280mb RAM ftw) accidentally pointing the wrong partition, and got the entire internal storage corrupted.. everything.. system, bootloader, recovery etc
My player was turning on only connected to a USB or charger, like yours. in fact It was hard bricked
I was able to recover it using Linux (because it is the only system able to communicate with the bricked device I had)
The problem is that everything need to be very specific, for example I used a software made for the galaxy s1 to "revive" my player 5 (both have the same hardware) it just made the device be detected via ADB. So I needed to prepare a SD with the same size as the internal storage (in this case 8gb) using the Linux terminal to mount in the SD an exactly schematic of the internal memory using a dump of another device that a xda user shared, (the dump was empty only with the bootloader, recovery etc) but it still had 8gb decompressed. So after that I used ADB to push the SD card content to the internal memory. And it get back to life \○/
Well.. it took me 1 week with a guide!! On the trial and error method. But it worked.. not perfectly, I get bootloops every time I try to flash a rom via Odin, but recovery works, and I have the device working until today
Hi, I Greatly appreciate your reply and advice. Think tho that your solution is a bit beyond my know how I know a little about ADB etc but i would have difficulties in compiling necessary files to sideload. Also many tanks for the link din't realise. Thanks Pal!
Alpha1BA said:
ok so bottom line is, I was in the middle of flashing official rom when at about 25% it failed. Don't ask why! (i still had recovery at this point) so I went ahead and cleaned absolutely everything thinking i'll just try and reflash as before. Now with power lead out it won't switch on at all and when power is supplied it shows message "An error has occured while udating the device software." loops at approx 3 sec intervals cant do anything with it.
Ive tried everything I can think of all to no avail! yes its my own fault bla bla bla just wondering if i act have f***** it.
Thanks to anyone with any ideas
Click to expand...
Click to collapse
If you can get it in to download mode you can flash stock rom back on it.......refer to xda samsung tab s2 for more details on this........
thx for reply but it reboots approx every 3 seconds so I dont have enough time to do anything with it :/
Alpha1BA said:
thx for reply but it reboots approx every 3 seconds so I dont have enough time to do anything with it :/
Click to expand...
Click to collapse
Plug in changer and push power and volume up and down all together and you will see the battery charger icon then you can get it in to download mode from there.....
stinka318 said:
Plug in changer and push power and volume up and down all together and you will see the battery charger icon then you can get it in to download mode from there.....
Click to expand...
Click to collapse
Stinka ure a superstar (atm!) I did as you suggest to no avail but I noticed a slight increase in the time it took to start rebooting again. I do not know which buttons did this but some 20 later it lasted long enough for me to be able to flash twrp. Now i havent actually tried that as yet as i wanted to check with you first... I have the battery logo on screen, i tried recovery and it started as it should but then rebooted, now im unsure at this time whether the battery is almost dead or not so i got it on charge and have the grey battery with a white flash inside... is this what i want for now until its charged? if so i'll keep you informed thamnks more than u know if uve helped me fix this, the reason i was flashing was because when i received it (no warranty!!) the screen sometimes flickered and it would constaly end up rebboting after digging around re that im lead to believe it need a new battery and for the connecting wires to be resoldered. Anyways thanks again n as I say i'll keep this updated
Cheers
Tony
one of the probs i hab/have with this unit is that it takes approx a day to fully charge!!! when i received it the screen flickered on the odd occasion but it was rebooting much more frequently. It came with stock n not messed with previously (i new this prior to purchase so got it for right price thinking it only needed flashing, how wrong was I!!!) so I flashed and encountered the above mentioned problems! thanks to stinka I surprisingly managed to flash a recovery... now provided all goes to plan, which rom would one suggest for stability and generally hassle free and prusuming the aforementioned probs, rebooting etc are still there what could i try to stop that? other than a debloated stock I found Lineage an excellent rom but still the problems got so bad the unit became unusable and was lucky not to go out the window. Im thinking do i start with a replacement battery and check the wires etc or could this still be a software issue??
if i endevoured to do the hardware myself would I attempt it by removing screen or the base for access to battery/connector??
Thanks again
In the tab s1 the best way is removing the back cover, but for some reason tab s2 seen to be the screen... at least in this guide: https://www.ifixit.com/Guide/Samsung+Galaxy+Tab+S2+Battery+Replacement/56616
Look like alot more complex than the s1 :/
RoIlingThunder said:
In the tab s1 the best way is removing the back cover, but for some reason tab s2 seen to be the screen... at least in this guide: https://www.ifixit.com/Guide/Samsung+Galaxy+Tab+S2+Battery+Replacement/56616
Look like alot more complex than the s1 :/
Click to expand...
Click to collapse
Thanks for that!!!
Tony
does look somewhat OTT!!!
will i have to odin stock first then flash rom i want or will it go straight from first flash via twrp considering there is absolutely nothing on phone at mo apart from twrp.
Alpha1BA said:
if i endevoured to do the hardware myself would I attempt it by removing screen or the base for access to battery/connector??
Thanks again
Click to expand...
Click to collapse
My guess is your issue is lack of charge in the device. That's the reason for the flashing failure and the reboot loop with the firmware error.
Bang it on charge for a while then irrespective of what it's doing, whether it's looping or not, hold POWER + HOME + VOL DOWN until download mode appears.
Reflash the stock firmware with odin.
swapped battery and reflashed stock via odin. It has helped although the issues are all still there its just they happen less frequently which doesnt mean its any less frustrating.