Dead Tablet? - Xperia Z3 Tablet Compact Q&A, Help & Troubleshooti

Hi there,
I think my z3tc just died.
I flashed the z3c firmware (only system) via flashtools in order to gain root with giefroot.
The tablet started, but the root process failed, and I had to hard reset the tablet (vol-,vol+,on/off), after that the device would not start again.
I tried the yellow reset-knob (beside the sim slot) for 10 secs ... nothing
vol-,vol+,on/off for 10 secs ... nothing
plugged it to the original wall-charger with the original cable ... nothing, not even the led shows up.
Has anybody an idea, or is my device a case for the wastebin?
Thanks in advance!

Hansifranzi said:
Hi there,
I think my z3tc just died.
I flashed the z3c firmware (only system) via flashtools in order to gain root with giefroot.
The tablet started, but the root process failed, and I had to hard reset the tablet (vol-,vol+,on/off), after that the device would not start again.
I tried the yellow reset-knob (beside the sim slot) for 10 secs ... nothing
vol-,vol+,on/off for 10 secs ... nothing
plugged it to the original wall-charger with the original cable ... nothing, not even the led shows up.
Has anybody an idea, or is my device a case for the wastebin?
Thanks in advance!
Click to expand...
Click to collapse
You flashed the wrong firmware. You could be hard bricked. Basically if you can't get into flash mode and flash the proper firmware then your screwed.
For future reference quadruple check your firmware before you flash the ftf file.
If your rooting SGP621 then you should have flashed the D6603 .93 firmware because that's the one with the exploit.
Sent from my D6603 using XDA Free mobile app

Thanks for the answer.
I have the SPG611, is it the same firmware to exploit as for the SPG621, namly D6603 .93?

Hansifranzi said:
Thanks for the answer.
I have the SPG611, is it the same firmware to exploit as for the SPG621, namly D6603 .93?
Click to expand...
Click to collapse
No the xploit shouldn't work because the system is quite different. SPG621 is the LTE version and I think 611 is the Wi-Fi version. The 621 runs on cellphone hardware very similar to the Xperia Z3 where the 611 has no LTE connectivity. It wouldn't be wise to flash a D6603 firmware on it because the hardware it too different.
Sent from my D6603 using XDA Free mobile app

I just found this:
http://forum.xda-developers.com/z3-...t-rooting-sgp611-giefroot-bootloader-t3017314
So I think it should also work on the WiFi Version (SPG611).

Dead Z3c Tab
Hansifranzi said:
Hi there,
I think my z3tc just died.
I flashed the z3c firmware (only system) via flashtools in order to gain root with giefroot.
The tablet started, but the root process failed, and I had to hard reset the tablet (vol-,vol+,on/off), after that the device would not start again.
I tried the yellow reset-knob (beside the sim slot) for 10 secs ... nothing
vol-,vol+,on/off for 10 secs ... nothing
plugged it to the original wall-charger with the original cable ... nothing, not even the led shows up.
Has anybody an idea, or is my device a case for the wastebin?
Thanks in advance!
Click to expand...
Click to collapse
This is EXACTLY what happened to me. No LEDs going on - nothing. Device 3 weeks old from Amazon Germany. I sent it in for repair, got it back today with a notice that because I had the bootloader unlocked the warranty is void and they didn´t do anything with it. BUT: When I got it back it was alive again, I could get it into fastboot mode. So I called the technician to ask how they had reset the hardware. They said they hadn´t done anything. I remember having read about a guy who had the same problem, when he packed the tablet to send it in after a couple of days he noticed it would turn on again.
So here is what I think: If you flashed the wrong boot.img or whatever and the Z3c Tab goes completely dead (no charging, no LEDs, no nothing) just wait a couple of days. May be some capacitator has to run flat or I don´t know what but just wait.
Pleas let us know if this works for you, might help other people here and I sure wonder if just letting it sit there can help when everything seems to be f*** up

Thanks for sharing your experience. I also read the post from the guy, who wanted to return it and discovered that it turned back to life.
How many days did it take from returning it to amazon to receiving it back?
Did you connect it to the computer with vol-, and the blue led came back?
It has been three days now, but connecting it to the computer or to the wall-charger didn't change a thing.

Took about 3 days to get it back. May be we have to let the battery discharge?
When I got it back (volume down + USB plugin) was working again, when I sent it in didn't do a thing, no LED. Once you have it back to fastboot mode it's really a piece of cake.

Doolittle Duckbill said:
Took about 3 days to get it back. May be we have to let the battery discharge?
When I got it back (volume down + USB plugin) was working again, when I sent it in didn't do a thing, no LED. Once you have it back to fastboot mode it's really a piece of cake.
Click to expand...
Click to collapse
I also thought about the battery, I will wait at least for monday, and then report back.

Hansifranzi said:
I also thought about the battery, I will wait at least for monday, and then report back.
Click to expand...
Click to collapse
Basically the trick here is to let the battery go dead OR disconnect the battery and reconnect it again but I suppose that would be a hastle.
Also, plugging again and again would charge the device especially if you are trying to discharge the battery fully.
If you are certain that all drivers are fully installed and it does not show any sign at all. I would suggest that hold down power + volume up/down depending on which mode you want to boot. The trick here is KEEP HOLDING POWER AND VOLUME KEY while at the same time plugging in the device to your PC. I am sure the LED would blink or something (I do not have the device but all Sony work this way)
I had a similar incident with a Sony Phone, just like your tablet symptoms but this trick worked for me.
Try that and report back to me, I would like to see what happens and if you need any help, do no hesitate to quote me back!
Good Luck and make sure you flash the RIGHT FTF this time

Hnk1 said:
Basically the trick here is to let the battery go dead OR disconnect the battery and reconnect it again but I suppose that would be a hastle.
Also, plugging again and again would charge the device especially if you are trying to discharge the battery fully.
If you are certain that all drivers are fully installed and it does not show any sign at all. I would suggest that hold down power + volume up/down depending on which mode you want to boot. The trick here is KEEP HOLDING POWER AND VOLUME KEY while at the same time plugging in the device to your PC. I am sure the LED would blink or something (I do not have the device but all Sony work this way)
I had a similar incident with a Sony Phone, just like your tablet symptoms but this trick worked for me.
Try that and report back to me, I would like to see what happens and if you need any help, do no hesitate to quote me back!
Good Luck and make sure you flash the RIGHT FTF this time
Click to expand...
Click to collapse
Thanks for the answer!
I just plugged the tablet into the usb-port of my laptop while holding VOL- and POWER, the led showed no signs, same as computer, also no signs. I will try again on Monday, the battery is surely dead until then. Hope dies last.

That guy must have been me Had the exact same story happening with a Galaxy Tab S. Looked like hard bricked, back to Media Markt with it, no, no, we won't lift a finger you evil tinkerer - and then it suddenly worked again. I had realized they must have done something. Because how would the see that my device's software had been tampered with if they didn't turn it on?!
Anyway, I tried that convoluted rooting method on my brand spanking new Z3Tc (is that the official abbrev.?) However, managed to get into flash mode somehow. It's embarassing for somebody like me but I'm on unrooted stock now... after about 20 Android devices, none of which wasn't rooted or an alternative ROM all the way
Good luck on reviving your tablet!

Hansifranzi said:
Thanks for the answer!
I just plugged the tablet into the usb-port of my laptop while holding VOL- and POWER, the led showed no signs, same as computer, also no signs. I will try again on Monday, the battery is surely dead until then. Hope dies last.
Click to expand...
Click to collapse
Led or any othehr signs are useless as long as the device is detected. Had it ?
Try power + volume up as well while flashtool running. It'd give you a better idea of detection. Even try power + both volume up and down.
Also plug in to Sony Official tool and see if that can help you repair it ? It might detect it as well.

Hnk1 said:
Led or any othehr signs are useless as long as the device is detected. Had it ?
Try power + volume up as well while flashtool running. It'd give you a better idea of detection. Even try power + both volume up and down.
Also plug in to Sony Official tool and see if that can help you repair it ? It might detect it as well.
Click to expand...
Click to collapse
When my Tab was dead none of the above worked, also "lsusb" in linux showed that it was not detected.
Concerning the question of what the technicians at MediaMarkt or support.com might have done: I know they used the "emma" software from the sony developer homepage to read out my z3c Tab. That apparently gave them the readout that the bootloader was unlocked. They sent me the screenshot together with the notice that they did not repair anything. So may be download "emma" for Windoze and hook it up to that... I use Linux with FlashTool which is supposed to be the same software (?). However, when my Tab was dead, FlashTool just said no device connected.
BTW: This is also the first (of many) Android devices that I now use UNROOTED. All others were rooted. It was also DEFINITELY the last-ever Sony device I ever bought. The hardware is nice, I need it waterproof because I use it on my motorbike. But this stupid rooting procedure is so screwed up that I will never ever buy Sony Android again!
I was really up and going for Sony, checking the internet on when the new z4 phone comes out, but my z3c tab user "experience" has now taught me better: Never again Sony!!!!!!!!!!!

Thanks for all the responses.
Using Windows 8.1 I tried:
USB-Plugging with all combinations of Power, Vol+, Vol- running
PC Companion
Emma
Flashtool
No Reaction at all.
Maybe the battery is still not empty.
Hope dies last.

Doolittle Duckbill said:
When my Tab was dead none of the above worked, also "lsusb" in linux showed that it was not detected.
Concerning the question of what the technicians at MediaMarkt or support.com might have done: I know they used the "emma" software from the sony developer homepage to read out my z3c Tab. That apparently gave them the readout that the bootloader was unlocked. They sent me the screenshot together with the notice that they did not repair anything. So may be download "emma" for Windoze and hook it up to that... I use Linux with FlashTool which is supposed to be the same software (?). However, when my Tab was dead, FlashTool just said no device connected.
BTW: This is also the first (of many) Android devices that I now use UNROOTED. All others were rooted. It was also DEFINITELY the last-ever Sony device I ever bought. The hardware is nice, I need it waterproof because I use it on my motorbike. But this stupid rooting procedure is so screwed up that I will never ever buy Sony Android again!
I was really up and going for Sony, checking the internet on when the new z4 phone comes out, but my z3c tab user "experience" has now taught me better: Never again Sony!!!!!!!!!!!
Click to expand...
Click to collapse
I will look into rooting Z3 compact without pre-rooted firmware / flashing any zip via recovery. There are few methods and Lollipop is a bit hard to crack but we would find it out soon enough! I will put up a guide in few hours and you can see if it works for you!
I think the support for your tablet is lacking and a need for an actual developer to sort things out.
I am not sure about EMMA much but usually I know about JTAG is used to recover hard brick devices. Giving it to Sony is always better option with an impression that you left it charge over night and it wouldn't turn on again. Always works!
Don't worry. It wouldn't be the first tablet hopefully!

Forgot to mention in my previous posts: when I got my tablet back from service, the battery was almost empty (<2%). That gives some support to the notion that you have to drain the battery to unbrick.
Note to would-be buyers who need root: stay away from this tablet (and probably Sony in general). The rooting procedure described in several threads here will drive you mad. It´s catch-22 all the way. (... after step 28 do step 11 unless your device is not LTE then do step 31 and you´re screwed with bootloop or hardbrick...) What a pile of sh**t!

Just tried again to plug it in,
sadly neither the computer nor the tablet showed any reactions in emma or flashtool.
Will try again in a few days.
Hope still is not dead.

Doolittle Duckbill said:
Forgot to mention in my previous posts: when I got my tablet back from service, the battery was almost empty (<2%). That gives some support to the notion that you have to drain the battery to unbrick.
Note to would-be buyers who need root: stay away from this tablet (and probably Sony in general). The rooting procedure described in several threads here will drive you mad. It´s catch-22 all the way. (... after step 28 do step 11 unless your device is not LTE then do step 31 and you´re screwed with bootloop or hardbrick...) What a pile of sh**t!
Click to expand...
Click to collapse
Nah you just need to read all the threads stick to the one you most understand and be cautious on every step
in my case i thought i needed root but after all the process and setting up my device it didnt feel right so I went back to stock the nice thing is that i have a backup of the TA partition just in case :victory:

I didn't touch the device for a week now.
But nothing has changed, still bricked. I will sell it as broken.
Hope has died. :crying:

Related

[Q] Is my Vibrant dead?

So I plugged my Vibrant into Odin to revert to stock. Apparently everything went wrong, and now my phone is stuck at the Phone---!---computer screen. It seems that my phone won't respond to hardware methods of entering download mode, so am I screwed?
Keep reading on here. This has happened to many people. Keep trying things and hopefully you will get it.
1. Remove SD and SIM card
2. Remove battery
3. plugged the phone into USB (connected to PC)
4. held down vol-up and vol-down
5. popped the battery back in while holding vol buttons
I've tried that, and many other methods, multiple times already. It seems that none of the volume/power methods do anything for my phone. I'm certain that if hardware-locks do exist for certain vibrants, mine just so happens to be one of them (Date on box is August 13). I just want to know if anyone with a similarly dated phone has ever been able to access download mode without adb.
If anyone knows of more methods, please post them. If all else fails, I'll go complain in my local T-Mobile store that my phone died. I have no idea if that'll get me anywhere, but it's worth a shot.
Does anyone who has had a problem similar to mine know of any fix? By that I mean, has someone who has had a presumably hardware-locked phone ever been able to boot it into download mode without adb? I'd really like to know if I can salvage this thing, or if I have to try my luck with T-Mobile.
Try holding volume down and holding power button and plug in USB while this is happening.
Sadly, I've tried that method as well, thank you though for responding. I will continue trying since it seems not to be a 100% thing for some people. Anyway, for the Volume keys + Power method, can anyone provide a more precise time of releasing power than "When it goes black". I'm hoping my inability to enter download mode is human-error, so I'd like as much input on this as possible. Thanks in advance.
Generic112 said:
Sadly, I've tried that method as well, thank you though for responding. I will continue trying since it seems not to be a 100% thing for some people. Anyway, for the Volume keys + Power method, can anyone provide a more precise time of releasing power than "When it goes black". I'm hoping my inability to enter download mode is human-error, so I'd like as much input on this as possible. Thanks in advance.
Click to expand...
Click to collapse
When you see the " !---> (pc)" symbol, plug your USB in. Hold down volume +, volume -, and power. As soon as the screen turns black release the power button only. Continue holding Vol + and Vol -. You'll enter Download mode.
I've tried that multiple times, but I will continue to try it. It seems as though my phone won't register that buttons are being pressed. All that happens is the phone reboots to the Phone--!--Computer screen every time the power is held and released (As it should). No combination of buttons seems to have any affect on this. Oh well, I'll continue trying and hopefully someone will post a working method.
I have the same problem and the hardware button method isn't working and I am stuck at the Phone ! Computer screen, and I read around the forums and they say that some Vibrant's have the hardware method locked, so you can't boot into Download mode from using the buttons. Since adb cannot find the phone when its stuck at this screen it seems we are both screwed. I have found no other solution other than returning it Tmo, not sure if they will exchange since it might be a violation of warranty.
I'm just going to play dumb when I go to T-Mobile. I'll say it just booted into that screen, and I can't get out of it. The hardware lock appears to be a defect, since it's not present on most Vibrants, so that should be able to warrant the replacement phone. I've been with T-Mobile awhile, and they're usually pretty good with replacements. Besides, the phone would be easily fixed if it wasn't broken in the first place.
But before I go to T-Mobile, I'm going to try and talk to Customer Service. If it's a common problem, then I'm sure it can be covered under warranty (Even though MOST ways of getting it require voiding warranty). Again, on the basis that this wouldn't be a big deal if my phone worked like a normal Vibrant. Besides, I'm sure T-Mobile can flash it without requiring the hardware method, so even if they only charge me some sort of service fee, I won't really mind.
As final moral reassurance for myself, I only tried to flash it because apps started FC on me and the phone constantly acted weird. The only thing I've done is root it, so it's not like I really set it up to fail.
Let me know how it goes with Customer Service. I would to get this problem resolved as well with the least amount of trouble. I don't want to have a brick and have to pay like $500 for a new phone. And I think the hardware buttons thing might actually be a defect. I tried doing the hardware buttons thing to get to recovery mode once before and it worked. I did this to install an update.zip to root the phone. It only worked that one time and now the buttons don't boot into recovery mode or download mode. It if works once then not again, there has to be something wrong.
I'll be trying them tomorrow (It's 10PM where I am). If all goes well, I'll try and contact you. I'm pretty sure I'll be safe so long as I don't mention rooting it. The firmware flash they'll have to do should help me on that front, so unless they catch on, I should be safe. Anyway, hopefully tomorrow I'll be good news, otherwise expect some post from me on Monday or Tuesday, depending on whether I have the time to deal with them or not.
Hey Generic112, I got with T-Mobile customer service. I told them about the screen I was seeing but did not mention rooting or attempting to flash the phone. They said they will replace my phone by shipping me a new Vibrant, but I have to return the one I have. I am not sure if they will do a check to verify if the Vibrant was rooted or not after they receive it, but I will have my new Vibrant before they receive the one I have. I won't know what will happen for awhile because its going to take a week for the new phone to arrive and when it does then I will be returning the one with the phone ! computer problem, unless someone thinks it is a better idea to tell them what happened and have them repair it?
I am also struck with the same problem
Hi,
I am also struck with the same problem. Please let me know if you guys got any method to resolve the problem or T-Mobile was able to help.
the3dman said:
Keep reading on here. This has happened to many people. Keep trying things and hopefully you will get it.
1. Remove SD and SIM card
2. Remove battery
3. plugged the phone into USB (connected to PC)
4. held down vol-up and vol-down
5. popped the battery back in while holding vol buttons
Click to expand...
Click to collapse
This method actually worked for me. I was beginning to think I'd have to build the USB jig, but tried this as a last ditch. Thanks!
The above method has worked for me numerous times with the same problem, my old bricked one, and my new one. Try holding down power button as well once or twice, never know. You have to keep the volume buttons pressed the whole time for it to work.
Sent from my SGH-T959 using XDA App
ViralCipher said:
Hey Generic112, I got with T-Mobile customer service. I told them about the screen I was seeing but did not mention rooting or attempting to flash the phone. They said they will replace my phone by shipping me a new Vibrant, but I have to return the one I have. I am not sure if they will do a check to verify if the Vibrant was rooted or not after they receive it, but I will have my new Vibrant before they receive the one I have. I won't know what will happen for awhile because its going to take a week for the new phone to arrive and when it does then I will be returning the one with the phone ! computer problem, unless someone thinks it is a better idea to tell them what happened and have them repair it?
Click to expand...
Click to collapse
In some cases that I've read they say, TMo charged them 600$ for the Replacement after finding out that it was bricked due to hacking. Before replacing try to get it repaired by them.
I would also like people whose phones were replaced to confirm what I've said above.
ech419 said:
In some cases that I've read they say, TMo charged them 600$ for the Replacement after finding out that it was bricked due to hacking. Before replacing try to get it repaired by them.
I would also like people whose phones were replaced to confirm what I've said above.
Click to expand...
Click to collapse
He should be able to get the phone woking again, what happened is not a big deal. If he sends it in the way it's sitting right now, t'Mo's techs won't have a problem getting it working again. (IMO) Especially if they find out the phone's rooted, I wouldn't be surprised if he gets charged.
I bricked my phone so bad, it was beyond recovery. I erased the bootloader, therefore it was completelly dead. No life. I got a replacement under warranty for free, never got charged for it.
My advice would be to try and get to work again before sending it in.

[Q] First time rom user = now i have a brick

Hi XDA, firstly wow...great site, lots and lots and lots of info, seems like a great community.
My phone: SGH-T959 (Samsung S Vibrant)
My issue: After flashing Axura 2.2.7 my phone doesn't turn on...at all...ever!
History: I'll say up front that I'm a long time android user with a technical background (Windows, Cisco networking, light Linux, etc) but first time rom flash experience. I bought a used SGH-T959 off Ebay, came stock with android 2.1 stock, I used Samsung Kies (straight off the official site) to upgrade to android 2.2. Well the phone slowed down, a lot. I felt ready to try my hand at flashing a Rom.
I first did a lot of reading, got Odin and my 2.1 and 2.2 stock files, flashed to 2.2 just to get a little comfortable. Worked fine. I charged my battery to full and then started the process of rooting my phone, again worked fine. I then updated to E2 boot loader (if I remember correctly) so I could work in recovery mode. I rebooted for good measure after going to E2 and all was still well.
**Issues incoming***
Using Clockwork I rebooted into recovery, flashed Axura 2.2.7 and the phone froze. Almost in a panic I pulled the battery and the phone was fine, still in stock 2.2. I booted to recovery again via Clockwork and attempted to flash Axura again, completed this time so I rebooted. That's the last time my phone did anything but look like a shiny rock. Will not power on.
Things I have tried:
* Holding many, many different combos of buttons after reinserting the battery
* Bought a usb Jig off ebay, nothing happened when inserted (tried holding many different combos of buttons while inserting it and while inserting the battery)
* Holding many, many different combos of buttons after connecting the USB cable to my computer with known good USB drivers (from when I used Odin)
* Used a known good battery from another T959 phone (co-worker that has same phone)
* Just for kicks I registered the device with Samsung, had two days left on the one year manufactures warranty so shipped it back to them, they returned saying the phone had experienced water or corrosion damage and the warranty was void.
As to Samsung's response I would like some feedback as to the possibility (it was a used phone after all). Just seems very unlikely that the phone would die just as I flashed it...
I am at a loss, I would love to get some helpful hints, tricks or anything else I could possibly do to get my phone back into download mode. I feel confident that if I could get the phone to that state I could get the process right.
Tell me I didn't waste my money on a now dead phone, give me some hope.
your best option is taking it to repair shop
don't know the point of using kies. Don't think it's a necessary step.
try these instructions: http://rootzwiki.com/topic/605-guid...nja-apps-everything/page__p__11106#entry11106
You can probably start on step 2 since you have nothing to back up. This will bring you back to stock and try flashing again. I use these instructions all the time before i flash a new rom
Good luck and keep us posted
Thanks for the link, however as I said in my OP, I have used Odin before and am comfortable with it, the phone doesn't turn on, aka no download mode)
It seems Jtag repair is my last hope (unless anybody gets creative and surprises me), anybody recommend one?
I searched and found one for $40 - mobiletechvideos.mybigcommerce.com/samsung-vibrant-jtag-brick-repair
Anybody review or offer an alternative?
TRY THIS
1) pull the battery out
2) plug ur usb wire to ur pc and ur phone
3) hold volume up+ wolume down
4) insert the battery in
GOOD LUCK...
try to odin back to stock
1. Start Odin
2. Plug USB cable into pc
3. Power off the Phone.
3. Pull the Battery.
5. Plug USB cable into Phone.
6. Press and Hold: Volume UP + Volume DOWN + Power, all at the same time.
7. Re-insert the battery.
8. The phone will power now, when the screen starts a cycle of going to a BLACK screen, release ONLY the POWER button.
9. When you see the download icon release the volume buttons,
10. Odin back to stock by putting the PIT file into the appropriate area and the .tar in the PDA area.
Or try that same method without holding the power button, just the volume rocker (up and down) when plugging into usb that works for some ppl
The vibrant is tough to hard brick so keep trying
I'm not really aware of the "E2 Bootloader" link maybe.... The only bootloader that I'm aware of is the Gingerbread bootloader. Either way I just posted this maybe it will be of help to you as well.
http://forum.xda-developers.com/showthread.php?p=19481353#post19481353
Keep in mind to have ODIN up when trying to get into download mode, if the phone screen is dead the only way to know you are in download mode will be the yellow box in ODIN when your device connects.
Good luck!
did you try with the battery IN:
volume UP + HOME key + POWER......?
I don't really see many people mentioning that option for DL mode....
Want to say thanks to everybody for the sugestions.
At this point after trying all the above and many more, I'm still dead in the water, I'm deciding between the $40 unbrickable mod install + flash to stock and the $40 JTag fix repair from mobiletechvideos.com
Anybody have experience with either service?
No, but this could be throwing good money after bad, however scorpn on the tw web site has a 8.00 roughly jtag, on a blackscreened brick it may not work. But it might, probly shouldnt be pimping another website, but thats where it is.
mog44net said:
Want to say thanks to everybody for the sugestions.
At this point after trying all the above and many more, I'm still dead in the water, I'm deciding between the $40 unbrickable mod install + flash to stock and the $40 JTag fix repair from mobiletechvideos.com
Anybody have experience with either service?
Click to expand...
Click to collapse
The only experience I have is a JIG. Have you seen his youtube channel? He has a lot of good info. He really knows his stuff. I learned how use ODIN and the FFC Mod from his videos. I think he has a video showing how to fix your phone or if you ship to him, he will fix it for you.
Try send a PM to him...his username is "connexion2005"
Let me know what happens or if you were able to fix your phone....
Sugartibbs said:
No, but this could be throwing good money after bad, however scorpn on the tw web site has a 8.00 roughly jtag, on a blackscreened brick it may not work. But it might, probly shouldnt be pimping another website, but thats where it is.
Click to expand...
Click to collapse
Yeah, if it were a straight $40 I would just dump the phone, bite the bullet and purchase another device. However on the site it says if the phone ends up being non repairable there is only a $10 charge to cover return shipping.
If I can install the unbrickable mod for $40, flash it back to stock, ship it back to me then I can drop whatever rom I want on it, all the while being able to use unbrickable mod apps to one click restore it...sounds worth a $10 loss chance to me.
Closfig1 said:
The only experience I have is a JIG. Have you seen his youtube channel? He has a lot of good info. He really knows his stuff. I learned how use ODIN and the FFC Mod from his videos. I think he has a video showing how to fix your phone or if you ship to him, he will fix it for you.
Try send a PM to him...his username is "connexion2005"
Let me know what happens or if you were able to fix your phone....
Click to expand...
Click to collapse
I actually did buy a USB Jig (OP), still nada on the display and ODIN com check.

Need help. Bricked device over real stupid reason I would never imagine.

Hey guys,
So, I think I officially join the club of the bricked Razr Max people today.
It happened like this.. Everything was running fine, created a few restore points of different roms in SafeStrap. Two under SafeSystem Enabled and one with it Disabled. So, I go ahead like a newb apparently and try to load my first restored image from the original OS / Stock, and I forgot SafeSystem is Enabled while loading it, mind you, this Restore point was made with SafeSystem Disabled when I was new to SafeSystem. Low and behold, the phone started up, "Dual Core Logo" showed for about ten seconds, and the went right to black screen and I can't get it out of there. Nothing I can do will start up the device. I have the charger in meanwhile and the phone isn't even recognizing a charge.
What do I do? Am I f*cked beyond immeasurable repair? Let me know.
Thanks
Ok I'm short on time, but this should help!
http://aashrey99razr.wordpress.com/disaster-recovery/
Aashrey99 said:
Ok I'm short on time, but this should help!
You know what though? I can't even power up into Bootloader that's how bad it is. Like, I am left with holding down the power button to absolutely nothing functioning. Screen won't turn on or off, nothing. I mean this is deeply off. Thanks for the guide though, but isn't his method for steps 5 to 8 only valid if you can get into the boot loader?
Click to expand...
Click to collapse
Wow. Problem fixed. It was as simple as holding the two volume buttons down at the same time while pressing the power button. Back in the bootloader and restoring to original state. This time PROPERLY. let's see if this works.
**My serotonin levels have just risen after this. Don't you all hate that feeling of a bricked phone when you don't know much about unbricking them? Almost a powerless feeling**
bnbrazr said:
Wow. Problem fixed. It was as simple as holding the two volume buttons down at the same time while pressing the power button. Back in the bootloader and restoring to original state. This time PROPERLY. let's see if this works.
**My serotonin levels have just risen after this. Don't you all hate that feeling of a bricked phone when you don't know much about unbricking them? Almost a powerless feeling**
Click to expand...
Click to collapse
I am sure your device is hard bricked, and nothing can make it work
only motorola can help u, so go there and tell them that u put ur device for full night charging and now it wont turn on.
They wont catch ur root cause they will have to change the motherboard revive the device
it happened with me and i also did the same
so cheer up
therazrguy said:
I am sure your device is hard bricked, and nothing can make it work
only motorola can help u, so go there and tell them that u put ur device for full night charging and now it wont turn on.
They wont catch ur root cause they will have to change the motherboard revive the device
it happened with me and i also did the same
so cheer up
Click to expand...
Click to collapse
He's device isn't hard bricked. I would find it incredibly hard to hard brick. You can't hard brick a motorola. If you think you did. You didn't try all possible solutions
Ask us any Android Related Question @FeraLabsDevs on Twitter
MattyOnXperiaX10 said:
He's device isn't hard bricked. I would find it incredibly hard to hard brick. You can't hard brick a motorola. If you think you did. You didn't try all possible solutions
Ask us any Android Related Question @FeraLabsDevs on Twitter
Click to expand...
Click to collapse
I couldnt hard brick my Blackberry,Samsung Charge. Think most recover. Maybe after alot of work.
therazrguy said:
I am sure your device is hard bricked, and nothing can make it work
only motorola can help u, so go there and tell them that u put ur device for full night charging and now it wont turn on.
They wont catch ur root cause they will have to change the motherboard revive the device
it happened with me and i also did the same
so cheer up
Click to expand...
Click to collapse
Same as Matty, You can't hard brick a Motorola. If they didn't provide a PC counterpart to the phone for restoration, they made sure that a user could pretty damn well not hard brick it.
Aashrey99 said:
Same as Matty, You can't hard brick a Motorola. If they didn't provide a PC counterpart to the phone for restoration, they made sure that a user could pretty damn well not hard brick it.
Click to expand...
Click to collapse
Agreed!. I mean. there was a time where the solutions didn't work so I removed my SD and I was put into the home launcher. There is always a solution to bricking
Ask us any Android Related Question @FeraLabsDevs on Twitter
All you need is fastboot files, RSD Lite and maybe, the factory cable. Just so everyone knows there are ways to get around everything!
Let's say you messed up your phone and it won't boot up. All you can do is get into fastboot and the bootloader. Problem is, your battery is too low to flash anything. Too easy:
Press and hold the vol down and power button until you see the screen flicker, let go of those buttons and quickly press and hold all 3 buttons on the side (power and both volume buttons). Once in the bootloader, plug in your wall charger. Now hit volume down until you highlight the SBF option and press volume up to select it. Now press and hold the power button for about 3 seconds and release it. Your phone will power down and should begin to charge. Once you get a full charge, repeat the process to get into fastboot, use RSD Lite and the fastboot files, viola!!
It's virtually impossible to hard brick a Moto phone unless there is a hardware issue or the bootloader gets corrupt somehow.
Umm, so out of curiosity. What might one do if the bootloader gets corrupted? I already sent it back to Moto and they claimed this new phone suffered water damage. (I've personally seen that the 3 stickers are non activated, 2 on board and 1 visible. So much for their theory). Just curious. And Jtag's seem quite costly and then there's the issue of correct pinout and finding the firmware. Any other solutions?

Broken power button/stuck in recovery

I dropped my phone a few days ago and the power button stopped working. Reboot ed into recovery from Rom Manager and realized that I couldn't select anything because I need the power button (tried every other button as well; nothing works). Took the battery out and put it back in (the only way to turn it off now) and it instantly booted into recovery. I can't send it to AT&T because I have at least 10 counts and they'll instantly see that CWM is on there.
Please help me!
kancheek1995 said:
I dropped my phone a few days ago and the power button stopped working. Reboot ed into recovery from Rom Manager and realized that I couldn't select anything because I need the power button (tried every other button as well; nothing works). Took the battery out and put it back in (the only way to turn it off now) and it instantly booted into recovery. I can't send it to AT&T because I have at least 10 counts and they'll instantly see that CWM is on there.
Please help me!
Click to expand...
Click to collapse
You dropped your phone. Samsung/AT&T warranty doesn't cover accidents, so there's no sense in worrying about your flash count. You're SOL. But you are free to try of course. Reverting to stock is very easy. What would you even do in recovery mode to revert to stock? Did you bother to look around the forum? There is a guide in the general forum on how to do that.
Out of curiosity, I did a google search to see what the repair options were for a broken power button. Saw that Mobile Tech Videos does it for $35 + shipping. Might be one of the better options at this point. As for the counter, just buy or make a jig to reset it.
mzaur said:
You dropped your phone. Samsung/AT&T warranty doesn't cover accidents, so there's no sense in worrying about your flash count. You're SOL. But you are free to try of course. Reverting to stock is very easy. What would you even do in recovery mode to revert to stock? Did you bother to look around the forum? There is a guide in the general forum on how to do that.
Click to expand...
Click to collapse
They wouldn't know that I dropped it unless I told them that, so as of right now the button stopped working by itself. I reverted to stock a while ago when I thought I bricked it, but I need to get it into download mode which can't be done without the power button.
kancheek1995 said:
They wouldn't know that I dropped it unless I told them that, so as of right now the button stopped working by itself. I reverted to stock a while ago when I thought I bricked it, but I need to get it into download mode which can't be done without the power button.
Click to expand...
Click to collapse
Recovery mode requires the power button. Download mode only requires the two volume buttons. With the phone off, while holding down vol- & vol+ plug in USB cable.
Lawrence of a Labia said:
Out of curiosity, I did a google search to see what the repair options were for a broken power button. Saw that Mobile Tech Videos does it for $35 + shipping. Might be one of the better options at this point. As for the counter, just buy or make a jig to reset it.
Click to expand...
Click to collapse
Good info if I ever need this
Has anybody used mobile tech videos to get their power button fixed? Mine stopped working out of the blue today, my phone is long out of warranty, and it refuses to connect to my computer at all so I can't revert to stock (I'm running AOKP 6.27.12 Build right now). I don't want to just send my phone off to some place that isn't reputable.
elementlaxer said:
Has anybody used mobile tech videos to get their power button fixed? Mine stopped working out of the blue today, my phone is long out of warranty, and it refuses to connect to my computer at all so I can't revert to stock (I'm running AOKP 6.27.12 Build right now). I don't want to just send my phone off to some place that isn't reputable.
Click to expand...
Click to collapse
It's still got to be in warranty with Samsung. The first units were shipped just under 9 months ago.
Mobile tech videos is considered to be quite reputable. I have only seen good reports about them, and the owner posts actively on the XDA-Developers boards.
You should be able to enter download mode. You don't need the power button for that.
Darn I didn't realize how long Samsung's warranties were. I made the switch back in October from Apple products so I'm used to crappy warranties.
I've already shipped to mobile tech videos because I searched around the forums a bit and found out that he is in fact reputable.
And I know how to get into download mode, I can do that no problem. My computer always pops up saying there is some problem with the device and I'm not sure how to fix it. I have the drivers installed correctly and it has worked in the past, but not recently. I would try to replicate it now but I don't have the phone in my possession, and at the moment it isn't really causing me an issue.
If you can't get Odin to recognize the phone once connected to the computer in download mode, then it is most likely a driver problem, or less likely a problem with the USB cable or ports. Once you get the phone back, if you still have the problem, that is where to look first.
I just wanted to point out that the broken power button would not prevent you from returning the phone to stock, although it can be a bit of a problem that you can't use recovery.
Yeah I was a bit worried that if I tried to go through Odin and something got messed up I wouldn't be able to get back into recovery to restore from a backup.
Thanks for all the help! I feel like a total noob and I appreciate your patience haha
In case you haven't already tried, in some versions of CWM (even non-touch) the search button (softkey) works like enter. Try all of the softkeys, one of them might work for you.
Yes, but if you Odin back to stock with a broken power button, that leaves you with stock 3e recovery. Even if you use adb reboot recovery to get into 3e recovery, you can't select anything without the power button.

[Q] Bricked during SIM activation?

Hello everyone,
I seem to be facing a singular issue, but I imagine it is much my fault, and just wanted a confirmation from those more experienced with the device...
I bought an Incredible 4G from eBay, that already had the a copy of Avatar on it, I believe almost the latest update. So when I confirmed the device worked after charging the battery, I flashed the latest copy of Avatar and the JB Gapps, and everything seemed hunkydory.
So, after that, I put in my old SIM, deactivated as I was using a non-4g device, and put it in the Incredible 4G. I started the activation process on the phone, following prompts to reboot the phone (Note: I did not know about CM10.1's issue regarding activation at the time, so one of the possible problems.)
After seemingly failing to activate after the first reboot, I "tried again" and it went down for another reboot. And it stayed down. Completely. I cannot get the phone to start, after charging the battery separately, cannot get into bootloader, nothing. I get QHSUSB_DLOAD when plugged into a computer using USB, but that's it.
A few notes: first time I started up, the screen went to recovery. I didn't think that was an issue; I factory reset from there, and rebooted into Avatar. Second issue: I used ROM updater on the phone to download and install the recovery, as I imagined that there was an automatic checksum done in the process (perhaps it was imagined?), and so when it went to flash, it had some issue, which didn't seem like a problem with the download, and I went through flashing it normally through recovery. Sorry I can't provide more details on that, but everything seemed to work all right after rebooting.
Finally, and this may be irrelevant, I put a 64GB SDXC card in the phone, I had already realized that it could not natively support exFAT, and so left the card in the device until the next time I could boot to recovery to partition it, and went through the activation process with the card inserted and not recognized.
So, I imagine that I have a hard brick, but can't tell if it's completely my fault, because it bricked in a peculiar fashion, at least from what I can tell, as no one seems to have encountered a similar issue after searching for the last 5 days.
If there's any hope for recovery, I would really appreciate some help regarding the device. I'm willing to provide some more info if necessary, and I'd like to find out sooner rather than later if it's a lost cause.
Thanks for any help you guys can give. XDA devs are awesome.
Quite the predicament. Just to clarify, have you tried the following?
1) Remove that super-big MicroSD
2) Remove SIM
3) Remove battery and wait a few minutes; also press the power button while phone is off
4) Only re-inserting the battery, hold vol-down and then hold power until screen comes on (then release power but keep holding vol-down)
I have tried them all; no SIM or SD card has been in there since the issue started. I hadn't tried pushing the power button while the battery was out, but it doesn't seem to change anything. So far, no reaction whatsoever even when holding power + vol down for a few minutes.
ChiqOmar said:
I have tried them all; no SIM or SD card has been in there since the issue started. I hadn't tried pushing the power button while the battery was out, but it doesn't seem to change anything. So far, no reaction whatsoever even when holding power + vol down for a few minutes.
Click to expand...
Click to collapse
Looks like you have a very hard to solve brick, I would like to help, have you tried using fastboot, I mean connected to pc and on that screen issue a fastboot command, also upload a picture of it please since this is new kind of brick, also I found this, our device is supported,
http://unlimited.io/qhsusbdload.htm
Sent from my ADR6410LVW using xda app-developers app
jose51197 said:
Looks like you have a very hard to solve brick, I would like to help, have you tried using fastboot, I mean connected to pc and on that screen issue a fastboot command, also upload a picture of it please since this is new kind of brick, also I found this, our device is supported,
http://unlimited.io/qhsusbdload.htm
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
You can't do fastboot if you can't reach the bootloader, and I've been assured the unlimited.io tool will not help for DLOAD resulting from non-racun related procedures.
Reading forum posts about QHSUSB_DLOAD suggest either jtag is necessary (which might not be worth it considering the phone can be purchased for $150 on ebay) or some strange strokes of luck after letting the phone sit for a bit. ChiqOmar, sorry I don't have great advice; do all the reading you can about QHSUSB_DLOAD mode.
jose51197 said:
Looks like you have a very hard to solve brick, I would like to help, have you tried using fastboot, I mean connected to pc and on that screen issue a fastboot command, also upload a picture of it please since this is new kind of brick, also I found this, our device is supported,
http://unlimited.io/qhsusbdload.htm
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
yes sounds like he is stuck in QSHUSB_DLOAD mode, but i don't know if the resolutiion on unlimited.io will help him or not.they say it's not supported for other reasons other than from running their exploit. it might work though.
mdmower said:
You can't do fastboot if you can't reach the bootloader, and I've been assured the unlimited.io tool will not help for DLOAD resulting from non-racun related procedures.
Reading forum posts about QHSUSB_DLOAD suggest either jtag is necessary (which might not be worth it considering the phone can be purchased for $150 on ebay) or some strange strokes of luck after letting the phone sit for a bit. ChiqOmar, sorry I don't have great advice; do all the reading you can about QHSUSB_DLOAD mode.
Click to expand...
Click to collapse
Maybe port HTC unbricking project to our device, and try to help him using it, since he can't do nothing about it right now, ChiqOmar, you ok with testing it ?, btw download ubuntu connect phone and see if the partitions get mounted, btw looks like you need to flash hboot from that mode, that's all then ruu, I have all the tools to do it if you want to
Sent from my ADR6410LVW using xda app-developers app
mdmower said:
You can't do fastboot if you can't reach the bootloader, and I've been assured the unlimited.io tool will not help for DLOAD resulting from non-racun related procedures.
Reading forum posts about QHSUSB_DLOAD suggest either jtag is necessary (which might not be worth it considering the phone can be purchased for $150 on ebay) or some strange strokes of luck after letting the phone sit for a bit. ChiqOmar, sorry I don't have great advice; do all the reading you can about QHSUSB_DLOAD mode.
Click to expand...
Click to collapse
i was able to bring my rezound back after a hard brick with a hex edited hboot that went bad with this tool but ported for rezound. its worth a try?
Thanks for the help everyone. Yes, although it states quite clearly that the Unlimited.io tool is only meant for devices bricked using their tool, I tried it anyway; obviously, nothing changed.
Though JTAG sounds interesting, I have no idea how to get started with that...nor do I really know if I want to travel down that route just now.
The HTC Unbricking Project sounds promising, but also no idea how to get started as it has not been ported for our device. The partitions don't get mounted in Ubuntu, as I connected it to the computer to use the Unlimited.io tool.
Finally, regarding the nature of the brick itself, I really wish I could pinpoint the issue better to help others if a similar issue happens in the future.
I am actually waiting on a battery, (ordered before I got the phone) and so will try that to see if anything changes.
Thanks again everyone. I've got a feeling I might have to write this one off pretty soon.
ChiqOmar said:
Hello everyone,
I seem to be facing a singular issue, but I imagine it is much my fault, and just wanted a confirmation from those more experienced with the device...
I bought an Incredible 4G from eBay, that already had the a copy of Avatar on it, I believe almost the latest update. So when I confirmed the device worked after charging the battery, I flashed the latest copy of Avatar and the JB Gapps, and everything seemed hunkydory.
So, after that, I put in my old SIM, deactivated as I was using a non-4g device, and put it in the Incredible 4G. I started the activation process on the phone, following prompts to reboot the phone (Note: I did not know about CM10.1's issue regarding activation at the time, so one of the possible problems.)
After seemingly failing to activate after the first reboot, I "tried again" and it went down for another reboot. And it stayed down. Completely. I cannot get the phone to start, after charging the battery separately, cannot get into bootloader, nothing. I get QHSUSB_DLOAD when plugged into a computer using USB, but that's it.
A few notes: first time I started up, the screen went to recovery. I didn't think that was an issue; I factory reset from there, and rebooted into Avatar. Second issue: I used ROM updater on the phone to download and install the recovery, as I imagined that there was an automatic checksum done in the process (perhaps it was imagined?), and so when it went to flash, it had some issue, which didn't seem like a problem with the download, and I went through flashing it normally through recovery. Sorry I can't provide more details on that, but everything seemed to work all right after rebooting.
Finally, and this may be irrelevant, I put a 64GB SDXC card in the phone, I had already realized that it could not natively support exFAT, and so left the card in the device until the next time I could boot to recovery to partition it, and went through the activation process with the card inserted and not recognized.
So, I imagine that I have a hard brick, but can't tell if it's completely my fault, because it bricked in a peculiar fashion, at least from what I can tell, as no one seems to have encountered a similar issue after searching for the last 5 days.
If there's any hope for recovery, I would really appreciate some help regarding the device. I'm willing to provide some more info if necessary, and I'd like to find out sooner rather than later if it's a lost cause.
Thanks for any help you guys can give. XDA devs are awesome.
Click to expand...
Click to collapse
Just got same issue, though for me I installed avatar rom, then rebooted at some point, but instead it hard bricked, can't charge pull battery out/in boot back up removed sim sd card didn't help me either. Any progress yet, or help?
Ill try to get a working htc unbriking Project soon for you guys to try, both please use ubuntu and have a working USB cable, I'm gonna try to reinstall hboot, also have teamviewr installed, also please tell me if you guys are supercid, also no usb 3.0 cable or port please
Sent from my ADR6410LVW using xda app-developers app
Some Information
jose51197 said:
Ill try to get a working htc unbriking Project soon for you guys to try, both please use ubuntu and have a working USB cable, I'm gonna try to reinstall hboot, also have teamviewr installed, also please tell me if you guys are supercid, also no usb 3.0 cable or port please
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
I'm on Ubuntu 13.04 64 Bit, I have a usb cable, Anker Battery Expert separate battery charger. And my Phone is S-OFF DirtyRacun Currently still hard bricked (Not by the Racun though) don't have any 3.0's, i have a onn usb cable and the stock, I also have a Ubuntu 12.04.2 LTS 32 Bit Live DVD. Battery Charging using a battery pack charger. Won't charge through USB
OldNut5 said:
I'm on Ubuntu 13.04 64 Bit, I have a usb cable, Anker Battery Expert separate battery charger. And my Phone is S-OFF DirtyRacun Currently still hard bricked (Not by the Racun though) don't have any 3.0's, i have a onn usb cable and the stock, I also have a Ubuntu 12.04.2 LTS 32 Bit Live DVD.
Click to expand...
Click to collapse
pm me with gtalk email and ill see what i can do, also install teamviewr
OldNut5 said:
I'm on Ubuntu 13.04 64 Bit, I have a usb cable, Anker Battery Expert separate battery charger. And my Phone is S-OFF DirtyRacun Currently still hard bricked (Not by the Racun though) don't have any 3.0's, i have a onn usb cable and the stock, I also have a Ubuntu 12.04.2 LTS 32 Bit Live DVD. Battery Charging using a battery pack charger. Won't charge through USB
Click to expand...
Click to collapse
I lost my first Dinc 4G LTE after I installed CM10.1, was working great for a while and just blinked off, never to recover. No charge light, no response to power button. I also had an aftermarket battery (Hyperion), but it would get so hot charging I replaced it with an OEM HTC battery. I think that damaged the phone.
Since I work with analog electronics, I assume something in the power path physically burned out. I never tried to talk to it via USB, but just cabling it to a computer generates no response.
I went back to the Stock RUU.zip from the unlimited.io site to get the firmware update. During the update it just sort of died. Now I can't get it to charge or get into the bootloader. Help! Please!:crying:

Categories

Resources