Question Bricked Pixel 6 ( Android 13 ) - Google Pixel 6

So I was on android 13 and tried rooting the device. I did this at 4 am in the morning don't even know why but any help would be greatly appreciated. The screen is completely black nothing comes up no matter what manner I hold the power/volume keys. I don't have a warranty because this device was imported.

ghostechful said:
So I was on android 13 and tried rooting the device. I did this at 4 am in the morning don't even know why but any help would be greatly appreciated. The screen is completely black nothing comes up no matter what manner I hold the power/volume keys. I don't have a warranty because this device was imported.
Click to expand...
Click to collapse
Did you still have A12 on your inactive slot before doing this? If so, sounds like you ran into the new ARB/eFuse problem and your phone may be bricked (this forum of full of discussions about this).
I'm not really knowledgeable about repair policies when importing a phone, but if possible, I would still call Google and explain to them the situation and see what they can do. Maybe others who have imported phones can provide a better option.
On the positive side, it seems like people who are running into this problem are having no trouble having Google either replace or repair their device.

Thanks for your input

Related

Hero G3

Hi all!
Ok here goes. I bought on ebay a Hero G3 running windows mobile. I think this thing is a clone but it seems pretty identical to the htc, although this phone does not say htc anywhere on it. Behind the battery G3 Hero A6288 is listed.
link : (dropped the h, new users are not allowed to post links) ttp://desoons.en.made-in-china.com/product/yMYnVCGrgocJ/China-Hero-G3-Windows-Mobile-6-5-GPS-WiFi-MSN-PDA.html
It came with Windows Mobile 6.5. Although it's a clone, is it still possible that it could run android?
Hardware seems pretty much exactly the same. However from what i've seen from looking around I would need Android installed first off in order to update?
Also somehow last night (I was drunk) the phone has somehow set a password in Windows Mobile and I do not know what the password is and so i am stuck big time! Tried following instructions to do a hard reset but these don't seem to work unless i'm doing something wrong? Windows mobile just boots up.
Is there anyway around this? Is there any ROMs of Windows Mobile out there from this thing that I could put on it to get around the password?
Please help, I have been looking all day for a solution to this and it's driving me crazy!
new link
ttp://rofen.en.alibaba.com/product/304037216-209334738/HTC_HERO_G3_Windows_6_5_2_SIM_Smart_Phone.html
You _might_ be able to load one of the WM "android kits" onto it which are kicked off post boot up, but it is a China counterfeit handset and thus undoubtedly cannot run it natively
Hi all!
Ok here goes. I bought on ebay a Hero G3 running windows mobile. I think this thing is a clone but it seems pretty identical to the htc, although this phone does not say htc anywhere on it. Behind the battery G3 Hero A6288 is listed.
link : (dropped the h, new users are not allowed to post links) ttp://desoons.en.made-in-china.com/product/yMYnVCGrgocJ/China-Hero-G3-Windows-Mobile-6-5-GPS-WiFi-MSN-PDA.html
It came with Windows Mobile 6.5. Although it's a clone, is it still possible that it could run android?
Hardware seems pretty much exactly the same. However from what i've seen from looking around I would need Android installed first off in order to update?
Also somehow last night (I was drunk) the phone has somehow set a password in Windows Mobile and I do not know what the password is and so i am stuck big time! Tried following instructions to do a hard reset but these don't seem to work unless i'm doing something wrong? Windows mobile just boots up.
Is there anyway around this? Is there any ROMs of Windows Mobile out there from this thing that I could put on it to get around the password?
Please help, I have been looking all day for a solution to this and it's driving me crazy!
Click to expand...
Click to collapse
Highly doubtful, the processors are most likely totally different
Sent from my HTC Hero using the XDA mobile application powered by Tapatalk
Sorry for bringing back from the dead this thread.
I recently aquired a hero clone, an a6288 with the same specs as the one mentioned in this thread.
The phone after a few days of fooling around cannot boot. It hangs during boot up, right after it plays the windows opening sound. I am trying to hard reset it but I cannot find the correct key combination, can anyone help me with that?
Thanks in advance!
eloydark said:
Sorry for bringing back from the dead this thread.
I recently aquired a hero clone, an a6288 with the same specs as the one mentioned in this thread.
The phone after a few days of fooling around cannot boot. It hangs during boot up, right after it plays the windows opening sound. I am trying to hard reset it but I cannot find the correct key combination, can anyone help me with that?
Thanks in advance!
Click to expand...
Click to collapse
On the real hero, it's menu, call and end call
But the fake is likely completely different.
Also based upon Windows not Android - so it could be anything - have you tried Ctrl + Alt + Del?
btdag said:
Also based upon Windows not Android - so it could be anything - have you tried Ctrl + Alt + Del?
Click to expand...
Click to collapse
That seems to be the problem. The combination is different, I've tried every forum I can find, in russian, chinese, italian and pretty much anything google can give but no key combination seems to work. The company I bought it from seems to be irresponsible on the matter, and every responce I got from them was wrong.
Is there another way I can force the phone to reset? Through a computer via windows or linux?
eloydark said:
That seems to be the problem. The combination is different, I've tried every forum I can find, in russian, chinese, italian and pretty much anything google can give but no key combination seems to work. The company I bought it from seems to be irresponsible on the matter, and every responce I got from them was wrong.
Is there another way I can force the phone to reset? Through a computer via windows or linux?
Click to expand...
Click to collapse
No idea. Pull the battery for a while? I honestly haven't a clue about these fakes. They are cheap for a reason I'm afraid
Try pressing every key and seeing what happens, try seeing if there is a pin slot as well and push that whilst trying all sorts of combos. Other the that, my only advice is to never buy a fake.
What did you do that broke it?
You must use the button of ignition and the key Volume + and Volume-.
We touch the key of volume and simultaneously you ignite the cel and it was entering Hard Rest.
i have the same china HERO G3 im newbie and i want to know if is possible to switch fro windows to android!thanks a lot
yannilupo said:
i have the same china HERO G3 im newbie and i want to know if is possible to switch fro windows to android!thanks a lot
Click to expand...
Click to collapse
If it's a proper HTC Hero, it runs Android. If it's a fake, it runs WinMo.
So this doesn't sound to be a HTC Hero Which means no android for you afaik.
For those who want to know, after many emails with the company I bought it from, I came to understanding that even they don't know how to hard reset it. The final solution they provided was to return the product to them to fix it (if possible) or to replace it. So either way, I will do that, although I now have no trust on the device (it hanged for no apparent reason) and will probably never use it for anything more than a backup phone.
Final conclusion: Cheap chinese phones? NO-GO!
hello i have same phone with itallian language
i want move it into English ..
any one help how we can change this phone into english ?
Regards
Hi,
Anyone have a english rom for this phone?
home+menu+power on is the hard reset for this phone
volume down + reset button ( up ) and power
bumping a dead thread.
Trying to fix a friends phone, I installed a simple HTC cab and now the phone won't boot up.
It says Hero, but then doesnt start.
The hard reset keys listed so far don''t seem to be working.
Anyone know any other hard reset combos that might work?
Have any of you tried pressing ALL of the keys available?
The counterfit market is ridiculous.People should research before buying...My wife-to-be nearly got me a nexus one (fake) for £50 thinking it was a real N1 they even call them the Nexus one and Hero so surely that's patent copyright breach?I think they even say HTC on them!

[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] An issue triggers the Tab 10.1 touchscreen not responding.

Please don't try anything mentioned below, if you are not familiar with flashing roms and programming ! You've been warned !
The following steps had been done in 4 sets of Galaxy Tab 10.1 (from different sources), all touchscreens become unresponsive within a minute. The system is still running, volumn keys are working, orientation sensor is operational, even the clock and wifi signal is fine. The only problem is the touchscreen. All 4 devices are not rooted, brand new, fully charged, and now returned to Samsung for inspection.
WARNING !!! The following steps may cause you trouble ! I share these steps only because I think some experts here may be able to solve it ! I'm also looking for some proof, if the same problem occurs to Samsung Tab 10.1 devices in different countries.
The steps to trigger an unresponsive touchscreen :
(1). Download and install any file manager from the Market (skip if you already have).
(2). Browse to "/sys/devices/virtual/sec/sec_touch/".
(3). Select all files (excluding folders).
(4). Copy and paste to any other location that have write permission (such as sdcard). Some of the files are not allowed to be copied, so just skip it.
And then, in a short while, the touchscreen will not respond anymore.
The files mentioned in step 2, are some driver files of Atmel mxt1386 (the touchscreen hardware). It seems that users of Acer Iconia also have touchscreen issue, turned out to be using the same hardware.
I know that there are also many users that do not have any touchscreen problem. This may only because those files are not accidentally accessed yet. I'd rather hope that you have a different version of the hardware driver that does not have such problem.
I'd like to ask for help from experts and developers here. But please don't try it if you are not absolutely confident to at least restore the system. Please don't blame me if your Tab becomes un-usable.
For those who are willing to try (at your own risk), I'm much appreciated. And I'd like to say thank you to all of you. Your effort may be helping a lots of users who have this problem.
Hey idsam,
have you got any ideas how to fix touchscreen broken this way?
Im sorry, I dont get this.
To me its like saying "I removed my battery and now my device won't turn on"
So, if I dont mess around with my system files and touch screen drivers, then my touch screen will be fine?
If you mean something else, please explain
Yeah, you got wrong.
Topic starter made too complicated example. The simple description is: if you try to read files from /sys/devices/virtual/sec/sec_touch/ directory - you'll got broken touchscreen. Looks like this operation damages touchscreen firmware, though this won't happen with properly configured/written (by manufacturer) system.
So who wants to read from those files? Any software for any reason. E.g. a lot of users have bricked their devices by doing a full system scan with Dr.Web for Android antivirus.
Sorry for the complicated example. I just tried to provide as much information as I could.
Feedback from Samsung is that it need hardware replacement (which is weird due to a software issue). But when they have a lots to sell, they simply says that they don't have parts for replacement at this moment. And they confirmed that flashing rom does not recover the device.
Yes. In most cases, we won't touch those files, except using any kind of antivirus software. I don't think it is limited to one brand, unless the antivirus software doesn't scan system files at all.
Besides, I also noticed that some Tablet users talked about unresponsive touchscreen : some said it happened suddenly; some said after charging for a while; some said having a useless device when woke up in the morning. It is hard to believe that all caused by the same antivirus software, right ?
What I've mentioned in the first post, is a way to trigger the problem. There may be other causes I'm not aware of. Some experts here may be interested in this issue. But it will be quite difficult for them, if they don't know how to replicate the case. This is why I posted the steps in the first place, and hope someone can help.
idsam said:
Sorry for the complicated example. I just tried to provide as much information as I could.
Feedback from Samsung is that it need hardware replacement (which is weird due to a software issue). But when they have a lots to sell, they simply says that they don't have parts for replacement at this moment. And they confirmed that flashing rom does not recover the device.
Yes. In most cases, we won't touch those files, except using any kind of antivirus software. I don't think it is limited to one brand, unless the antivirus software doesn't scan system files at all.
Besides, I also noticed that some Tablet users talked about unresponsive touchscreen : some said it happened suddenly; some said after charging for a while; some said having a useless device when woke up in the morning. It is hard to believe that all caused by the same antivirus software, right ?
What I've mentioned in the first post, is a way to trigger the problem. There may be other causes I'm not aware of. Some experts here may be interested in this issue. But it will be quite difficult for them, if they don't know how to replicate the case. This is why I posted the steps in the first place, and hope someone can help.
Click to expand...
Click to collapse
When the touchscreen goes unresponsive, do other parts of the device still function? For example, when you hold down the power button, will the shutdown menu appear? When you rotate the device will the orientation change?
I have had an unresponsive touchscreen many many times. I'm not sure it is the same unresponsive touchscreen you talk about here. When mine goes unresponsive I can still use the power button and if I rotate the screen a few times it eventually becomes responsive again.
Yes. The power and volume up/down buttons work, orientation sensor also works as a normal device. I tried to rotate the screen, discharge and recharge the battery, but it aside for hours and tried again, nothing helps.
And it is actually confirmed by Samsung that hardware replacement is needed. They said that they tried to recover the device by flashing rom, but failed.
so I have the same problem. Quite frustrating. Not only that, I've noticed that there is a vertical 1-2 inch area from top to bottom of the screen that doesn't ever respond to touch.
I'm sending it to Samsung
Hi Idsam, I'm from Russia and have a same problem. After full scan by Dr. Web the touchscreen not responding and now I don't know what to do, beacause I've bought my Samsung in USA in Bestbuy, but now I'm at home in Russia, no warranty, no service, nothing. May be somebody can give me advise?
To be honest, it seems that Samsung doesn't have a solution yet. And probably worse, Samsung did not modify the driver at all, which means Atmel is responsible to fix the problem. No matter what, you can wait, but who knows how long it takes.
I think Best Buy has refund policy. You should discuss with them asap, as this kind of policy is normally time limited. You may consider to pay for delivery, in order to minimize your lost. If they refuse to refund for you, then you may need to contact Samsung Russia. I'm sure they know about this issue, and perhaps you may discuss with them. Still, you may need to consider to pay a little more as repair service charge.
BUT, I'm not saying you should pay more for what they've done wrong. It is only a suggestion, in order to speed up the process and at least minimize your lost.
The last option, I think, is to wait until Samsung announce a solution. If the method to fix it doesn't require hardware exchange, perhaps you may get information from Samsung and try to solve it by yourself.
As I know, when the touchscreen issue occurred, the Android system is actually still running WITHOUT problem. It means that you may still control the device by using ADB via USB. So, if Samsung can provide a patch, it may be easily fixed. I'm not sure if it is possible or not, just hope it will be as simple as that.
I think I heard to get it on hold the lock button for 10 seconds then touch the screen the it should turn bk on try it let me know if it works
Thanks for your answer. As I understood we have to wait patch from Samsung and when they provide this patch then problem can be fix without hdd replacement?
---------- Post added at 07:28 AM ---------- Previous post was at 07:23 AM ----------
oawalker said:
I think I heard to get it on hold the lock button for 10 seconds then touch the screen the it should turn bk on try it let me know if it works
Click to expand...
Click to collapse
No, it doesn't help. Only one method left - use the hammer.
oawalker said:
I think I heard to get it on hold the lock button for 10 seconds then touch the screen the it should turn bk on try it let me know if it works
Click to expand...
Click to collapse
Thanks for your suggestion, which I tried before and didn't help. Actually, I wouldn't start this thread if it is that simple. But probably too risky for anyone to try to fix this.
AlexNovoross said:
Thanks for your answer. As I understood we have to wait patch from Samsung and when they provide this patch then problem can be fix without hdd replacement?
Click to expand...
Click to collapse
I can't say if hardware replacement is needed or not. I just *HOPE* that a patch will be able to fix the problem, which should be the best news for all of us.
idsam said:
Thanks for your suggestion, which I tried before and didn't help. Actually, I wouldn't start this thread if it is that simple. But probably too risky for anyone to try to fix this.
I can't say if hardware replacement is needed or not. I just *HOPE* that a patch will be able to fix the problem, which should be the best news for all of us.
Click to expand...
Click to collapse
I hope Samsung can patch this up when they update to 3.2 if that update comes
Does this mean i Lost my Tap if that patch did't come out..
!!!???
Honestly, only Samsung can answer your question. But my steps can help you to show proof to them that it is a design flaw, and force them to admit that it is their responsibility to provide solution.
This is, unfortunately, the known issue with all mxt1386, mxt224 and qt64-blah-something touchscreens. I have wasted a week debugging my iconia and have experienced tons of butthurt. To put it simple, when an error occurs in the touchscreen controller, it does not report proper ID, but an error code instead. Some versions of drivers (like Asus one) just return -ENODEV in that case. Acer's driver was intended to handle it, but was written poorly and died in a deadlock in such an event. My solution was to comment out semaphores and other synchronization techniques and that got past the device detection and cleared error bits.
You can read more in http://forum.xda-developers.com/showthread.php?t=1143892 and try to use the drivers from iconia (the patched drivers are also uploaded and there's a link in that thread)
I have the same problem with my Galaxy Tab P1010. I can get into download and recovery mode i can move the selection using the volume button but i can't press the power to enter my selected option. I have already tried re-installing the latest available firmware for my device using ODIN 1.7. Eventually everything seems to be ok until i reach the point where you select the language. I can't select any option mainly because the touchscreen is unresponsive. All along i thought this problem is only software? Hopefully somebody can find the solution to this.
sp3dev said:
This is, unfortunately, the known issue with all mxt1386, mxt224 and qt64-blah-something touchscreens. I have wasted a week debugging my iconia and have experienced tons of butthurt. To put it simple, when an error occurs in the touchscreen controller, it does not report proper ID, but an error code instead. Some versions of drivers (like Asus one) just return -ENODEV in that case. Acer's driver was intended to handle it, but was written poorly and died in a deadlock in such an event. My solution was to comment out semaphores and other synchronization techniques and that got past the device detection and cleared error bits.
You can read more in http://forum.xda-developers.com/showthread.php?t=1143892 and try to use the drivers from iconia (the patched drivers are also uploaded and there's a link in that thread)
Click to expand...
Click to collapse
It seems that the second link is invalid. Besides, it is necessary to root the device and flash CWM recovery first, right ?
I mean, it may be a bit risky. I read your post before, but not sure if it is the same issue. If it is not, and the device is rooted, the official warranty may be voided too.
I have updated the links but the recovery image is only valid for the Iconia tablet. I mean, one could try using the attached driver sources and add them to the kernel but that will require at least flashing custom kernel. Samsung seems to be releasing a firmware update to fix this issues but people familiar with linux kernel development may try experimenting with the driver from acer.

[Q] Galaxy GIO (S5660) bricked, I am unsure.

Hello everyone,
Firstly, I did not find a board dedicated to the S5660. So I posted it here.
Today, I tried to backup my current installation of Android to my SD. I used
a guide on androidpolice(dot)com, while searching for "complete android backup" in Google.
My phone had to be rooted, which it was, so I went on to download and install Clockworkmod's ROM Manager. I opened it up, fixed the permissions and made a backup. Before I could make one, I had to pick a phone model. However, these were all very strange types or brands I never even heard of.
I randomly picked one, and my phone NOT being listed should have served as a warning but alas, and the app started backing up. After it was done, it all seemed normal so I pressed "home" to go back to my main screen and pressed the "lock/power" button so my screen would turn off. I put the phone in my pocket.
Exactly 2 minutes later, I pull out my phone and I notice the screen is black, I push the lock/power button: nothing happens. I hold the lock/power button in the expectation that the phone will boot up since it might have been shut down accidentally. Nothing happens.
I remove battery, re-insert battery. I repeat this over a dozen or so times to no avail. I try the download or safe boot key-combinations (volume down + home + power) and nothing helps.
It's as if either all the keys are broken, something went seriously wrong in the interior hardware or hopefully, (the most simple possibility) my battery gave the ghost.
I went to the shop where I bought the Galaxy Gio and told them about the issues I had, they said they were going to send it to a Samsung Service Center for repairs. After I went home and had browsed the Internet for some possible solutions, I returned to the shop to try out several of the tricks that were listed (inserting battery on the exact same time when you press the buttons), nothing worked.
Does this smell to bricking or just a dead battery?
Before any conclusions are made (it sounds like its bricked though)...dead battery?... Did you try charging it?
Theonew said:
Before any conclusions are made (it sounds like its bricked though)...dead battery?... Did you try charging it?
Click to expand...
Click to collapse
It happened while I was at school, I immediately went to the shop and the guy helping me said he had plugged it in for a short while. I guess I believe him since I did not see it but he said the phone did nothing.
But how come a software malfunction can mess up the physical buttons like the power/volume or lock buttons?
Darmvlinder said:
But how come a software malfunction can mess up the physical buttons like the power/volume or lock buttons?
Click to expand...
Click to collapse
If the software of a device is corrupted, then the hardware won't work properly (if at all). Example: you flash a rom for a device with one button and your device has five, then of course the software wouldn't recognize the other buttons (this is just an example of the hardware part cause if you actually did that, your device wouldn't even start). Also, you said that you just randomly chose one made for another device, for future reference: NEVER flash a kernel, rom, etc. not made for your device or atleast not stated to work on your device.
Theonew said:
If the software of a device is corrupted, then the hardware won't work properly (if at all). Example: you flash a rom for a device with one button and your device has five, then of course the software wouldn't recognize the other buttons (this is just an example of the hardware part cause if you actually did that, your device wouldn't even start). Also, you said that you just randomly chose one made for another device, for future reference: NEVER flash a kernel, rom, etc. not made for your device or atleast not stated to work on your device.
Click to expand...
Click to collapse
Yes, I figured this when I tried to do the actual backup but it seems I was too stupid to stop the entire process.
I have already given it to the store as they will send the phone to a Samsung Service Center. Do you know how the processes of repairing for such phones work?
Also, if the phone is a total brick, it cannot be recovered whatsoever?
Darmvlinder said:
Yes, I figured this when I tried to do the actual backup but it seems I was too stupid to stop the entire process.
I have already given it to the store as they will send the phone to a Samsung Service Center. Do you know how the processes of repairing for such phones work?
Also, if the phone is a total brick, it cannot be recovered whatsoever?
Click to expand...
Click to collapse
The best thing to do is hope they can't repair it . If they happen to get it to work and find out you rooted it, they will just return it to you the way it is now. I hope you didn't tell the guy how this happened...
P.S. - No, I don't know the process they use to recover something like this. I'm no expert in recovering hard bricks (know a few stuff, but not in this case).
Theonew said:
The best thing to do is hope they can't repair it . If they happen to get it to work and find out you rooted it, they will just return it to you the way it is now. I hope you didn't tell the guy how this happened...
P.S. - No, I don't know the process they use to recover something like this. I'm no expert in recovering hard bricks (know a few stuff, but not in this case).
Click to expand...
Click to collapse
The guy asked me whether I had ever let the phone come into contact with water or fluids or if I ever let it fall down to the floor, neither of which have happened in the past. I also told him an update through Kies went awry and caused the system to be unstable till the crash of today.
The dude seemed pretty confident in that the warranty would cover. I don't know. I feel like a giant moron, to be honest.
Darmvlinder said:
The guy asked me whether I had ever let the phone come into contact with water or fluids or if I ever let it fall down to the floor, neither of which have happened in the past. I also told him an update through Kies went awry and caused the system to be unstable till the crash of today.
The dude seemed pretty confident in that the warranty would cover. I don't know. I feel like a giant moron, to be honest.
Click to expand...
Click to collapse
Another future reference (although you dodged the bullet here): never tell your manufacturer (or whoever is supposed to look after the warranty of your device,etc.) that you rooted (or even tried to root) your device. Well, you just have to hope for the best now .
Theonew said:
Another future reference (although you dodged the bullet here): never tell your manufacturer (or whoever is supposed to look after the warranty of your device,etc.) that you rooted (or even tried to root) your device. Well, you just have to hope for the best now .
Click to expand...
Click to collapse
I just sat through a Live Chat session with Samsung. Even though Google does not oppose rooting, Samsung effectively makes a deal out of it. I told him the same story, that an update through Kies made several things pop up on my phone which I did not understand etc. etc.
I am hoping for the best. But I am befriended with someone working in the store that sold the phone to me. He said most techs won't bother with low-budget smartphones (as in trying to grab you by the balls) and will much rather flash the phone with Samsung stock ROM.

[q]hard-brick from entering download-mode

hello all, i just bought a new i9300, already downloaded a bunch of roms, but didn't even had the chance to install any of them.
first of all i want to say this is my third i9300 i done things with(installed recovery kernels and others), also had 2 i9100 and lots of other android phones, so i'm much familiar with ROMs, Kernels, CWM and TWRP, etc.. and also reads carefully every time i do something new (while this one was already done by me to friends devices)
this time something really really strange happened and my new device is now completely dead
i came home, turned it on, everything fine.
installed new drivers, run toolkit v.7, recognized and everything is ok
after all the steps it was in download mode, but Odin didn't show anything.
tried another PC, restarting the device, nothing. odin won't recognize it.
then i tried entering download mode with the key combination, Home button + Power Button + Volume Down.
entered download mode just fine, but still, no odin.
i tried 3 times, first with the cable disconnected, second with the cable connected, and third with the cable disconnected.
on third time something just so weird happen, it entered a different stage, something i don't know, and didn't find anything about it while googling.
all i remember is 4 rows written in red and green
when i turned off the device, it refuse to wake. nothing. no download mode no recovery no indicator for battery charging. just plain nothing
reminding you this is brand new device which was never even massed with odin. just some stage i never seen in my life.
can someone tell what was that stage i was on? why it massed my device in an instant? how in the world i managed to enter a boot-stage i can't find any information about
also to state, the i read about the sdcard mode (need the device opened and to short something) and it's defiantly not this stage.
hope someone can help
thank you very much
return for warranty claim if it has never been messed with is the sensible thing to do
slaphead20 said:
return for warranty claim if it has never been messed with is the sensible thing to do
Click to expand...
Click to collapse
thanks for replay, but the thing is i bought this device from regular shop not samsung distributor in my country
so i don't know if i can even call them
and the shop i bought from don't want any part with it (saying its my fault)
Looks like SDS
The vendor is responsible for warranty repairs not Samsung .
Samsung offer the user an extra limited warranty .
jje
Give it for warranty saying that the phone hanged up then died and you can't even turn it on. Not a word about download mode or anything, act like you know nothing about flashing
As much as i want, the seller refused to take it
so im in bad shape, new device just going to trash
I hope someone can provide information for how a button combination can destroy my device completly.
now im afraid to buy a new one
Sent from my GT-I9100 using Tapatalk 2
What country are you in?
You could take it to Samsung service centre if you have one nearby.
Noambugo11 said:
As much as i want, the seller refused to take it
so im in bad shape, new device just going to trash
I hope someone can provide information for how a button combination can destroy my device completly.
now im afraid to buy a new one
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
This is one of the risks we all run when we mod our devices. just going into download mode should not have done this to your device. Look in your device manager and see if it is even being seen by the pc. Could be the SDS that alot of people have seen
zelendel said:
This is one of the risks we all run when we mod our devices. just going into download mode should not have done this to your device. Look in your device manager and see if it is even being seen by the pc. Could be the SDS that alot of people have seen
Click to expand...
Click to collapse
Hey, if it was the SDS, then i would been triggered anyway from anywhere,
this situation is far more complex, as i said, by the same button combination it entered a different boot stage and not the normal download mode (nor recovery mod), iv'e been searching the hole web just to find a clew to what the hell is this stage, and why it massed my device so badly.
i'm from israel, and i don't think we have samsung service center, just a representer or something.
if i can i will defently send it to samsung all over the world, i just need a phone number or something to contact with them,
do any think samsung will take this device? if so where can i contact them?
Noambugo11 said:
Hey, if it was the SDS, then i would been triggered anyway from anywhere,
this situation is far more complex, as i said, by the same button combination it entered a different boot stage and not the normal download mode (nor recovery mod), iv'e been searching the hole web just to find a clew to what the hell is this stage, and why it massed my device so badly.
i'm from israel, and i don't think we have samsung service center, just a representer or something.
if i can i will defently send it so samsung all over the world, i just need a phone number or something to contact with them,
do any think samsung will take this device? if so where can i contact them?
Click to expand...
Click to collapse
This reminds me of a case we saw just the other day here in the threads. The DL screen was not the normal download screen and it turned out to be a clone device. Think this may have been the case?
zelendel said:
This reminds me of a case we saw just the other day here in the threads. The DL screen was not the normal download screen and it turned out to be a clone device. Think this may have been the case?
Click to expand...
Click to collapse
thanks a lot for your kind answers, when you say clone device you mean not a real i9300? cause if so them i 100% sure it's a real one and not a fake.
i was able to enter download mode while in the toolkit (enebling USB debugging first), but odin didn't show the device at all, then i tried the button combination; Power button + Home Button + Vol Down.
first it entered fine, still odn didn't catch it, second time also into the right download mode
third time, different stage, 3 rows written in red 1 row in green (much like sd-mode, but i'm quite sure it wasn't it, and even if is, how the world i managed to enter it by button combination only?)
i can't remember what was written, i think the word emmc been there, but can't be sure
this thing drive me crazy, i've done it 3 times with other i9300, i did it for i9100, i did 3 galaxy ace, also i9000, did some htc phone,replace many screen for phones and massed with this kinda of stuff a lot, in the PC world, iphones, everything. i can't consider myself noob or even close to it, i never rush into things before reading carefully.
and the matter that no-one know even what i'm talking about making me really think i wan't really responsible for it, but got a bad luck with a faulty device or something. and now i'm stuck with it cause nothing is connected between me and samsung (unless someone here some kind of idea)
Noambugo11 said:
thanks a lot for your kind answers, when you say clone device you mean not a real i9300? cause if so them i 100% sure it's a real one and not a fake.
i was able to enter download mode while in the toolkit (enebling USB debugging first), but odin didn't show the device at all, then i tried the button combination; Power button + Home Button + Vol Down.
first it entered fine, still odn didn't catch it, second time also into the right download mode
third time, different stage, 3 rows written in red 1 row in green (much like sd-mode, but i'm quite sure it wasn't it, and even if is, how the world i managed to enter it by button combination only?)
i can't remember what was written, i think the word emmc been there, but can't be sure
this thing drive me crazy, i've done it 3 times with other i9300, i did it for i9100, i did 3 galaxy ace, also i9000, did some htc phone,replace many screen for phones and massed with this kinda of stuff a lot, in the PC world, iphones, everything. i can't consider myself noob or even close to it, i never rush into things before reading carefully.
and the matter that no-one know even what i'm talking about making me really think i wan't really responsible for it, but got a bad luck with a faulty device or something. and now i'm stuck with it cause nothing is connected between me and samsung (unless someone here some kind of idea)
Click to expand...
Click to collapse
I have never seen this screen myself. The fact that you were able to get it to the screen the first few times is really odd. Sounds like one of the partitions got fried. I would send it back to samsung. This may end up costing you to have it repaired as well as shipping to the closest repair center, Here is the site that may help
http://www.samsung.com/il/#latest-home

Categories

Resources