Related
During an attempt to flash a rom using odin to my rooted sgs2, odin crashed and closed before it was finished. I tried restarting odin, wouldnt see phone.
Removed battery from phone, reconnected to odin and tried using the one click odin to reflash back to stock. Also tried using odin with other roms to flash back.
Heres my problem.
When i power on the phone, it says the Galazy S2 i9100 for a few seconds, then just turns off.
I can open odin, or odin one click, plug in phone, shows me yellow w/com and added. I click start, it gets to Setupconnection and then just sits there.
I have tried
- Different roms and both one click and normal odin.
- Different usb cables
- Different usb ports
- Multiple computers
Is there any way to get past this? God i hope someone can either point me somewhere or help me out.
Reinstall Samsung Kies to your laptop or pc so the proper drivers are re-installed. Once complete with that install, plug your phone into the pc and put the phone into USB mode, hopefully the pc will recognize your phone and install the NEW DEVICE drivers after a few moments. Depending on your pc, sometimes it takes many seconds for your pc to recognize and bring up the drop down menu for the newly recognized drive. BE PATIENT. If the pc does recognize your phone, start Odin again. If Odin also see's your phone, which it now should, you should see a COM:# connection in the ID:COM box of Odin. Doesn't matter what COM # is, as long as something is there. You can now use Odin because it see's your phone. Once you start Odin flashing, make sure not to disconnect anything until you see the upper left GREEN PASS box in Odin. Once its GREEN with PASS in that box, you're finished. You can d/c your phone from the pc and the phone is probably rebooting anyway.
OFC, if your phone will not stay power'd up, all of the above is for nought. Wish I could be more helpful.
Keep in mind that I do not intend to insult intelligence but everyone has limits in experience and I always try to explain in the simplest way I can. No disrespect intended.
Good Luck!
R
Thanks for the reply,
How am i supposed to put the phone in usb mode when i cant boot it?
That does create a problem, I would do some research on a USB Jig for your phone. Search at eBay for: Samsung Galaxy S2 Epic 4G Touch USB Jig
I'm not sure if this will help a phone that will not power up but it does have its uses for Root'd phone especially using Odin to flash and to remover that nasty YELLOW Triangle that comes from ROOT ROMS that are unsign'd.
Wish I could help you further.
R
Scribes said:
Thanks for the reply,
How am i supposed to put the phone in usb mode when i cant boot it?
Click to expand...
Click to collapse
Try to put in download mode if not try a jig ... If that fails it's sprint or jtag
Sent from my SPH-D710 using xda premium
It does power on, basically shows the sgs boot logo (black backgroud w/ white text) then goes dark, but its actually still on cause it gets hot.
I can get it into download mode and i can get it into the android recovery.
Theres gotta be a way to recover with an update.zip from the android recovery via the sd card........
There you go, you have two of us saying about the same thing. Just make sure you get the correct JIG if you go that route. It's like $2.00 and arrives from China in like 2 weeks.
http://www.ebay.com/sch/i.html?_fro...e+for+Samsung+Galaxy+S2/i9100/i9000/T959/i897
---------- Post added at 09:41 AM ---------- Previous post was at 09:37 AM ----------
humm, an idling phone shouldn't get hot. That tells me you've got something going on. I think you just progress'd passed my pay grade my friend.
Heres another thing, as i mentioned in my first post.
The boot logo says i-9100....
and this is a sprint phone, isnt it a d710?
So im gussing in my late night haze i screwed myself by loading an i9100 rom/bootloader/whatever the hell that is.
Samsung calls it: I9100
Sprint calls it: SPH710
We call it: Epic 4G Touch
I see, so thats not the problem?
Im just gonna keep posting here while i mess with this incase i trigger someones mind for a fix.
(picture was here apparently i cannot post an external link yet. Was just a picture of device manager and odin sitting at SetupConnection)
The only way to get odin to see my phone, is if i open odin, put phone in download mode, plug phone in, then uninstall the com port via device manager, reinstall it. When i rescan for hardware changes, odin goes yellow as seen in the picture, i click start, then it sits at SetupConnection all day, so im guessing its losing the connection after it finds it.
My only solution here is via usb card i think, but i cant find a signed package. Cant someone just pull theirs from a stock phone? Why wouldnt that work?
Well, if you can get Odin to work, unroot to full stock with this:
http://www.megaupload.com/?d=ISD9AOP0
Right, getting odin to work is the real problem though i think.
Stuck at SetupConnection forever
This is super frustrating... going without a phone is impossible, work emails, texts, calls, ahhhh
..and there is no way to completely reload the entire phone using an update.zip off the sd card, one that is signed?
I know i used to do that on my droid, and all though i know this is a totally different game, i still have android recovery, one would think it would be possible if the package was signed. unsigned ones just fail, but at least i can attempt to run them from there.
If someone can find a way to do that, and it works for my phone, i will paypal $50
Let me see what I can find for ya....
I have searched two different Forums for a flashable unroot to stock with NO luck. Everything I found requires Odin. Sorry Buddy.
Correct me if I'm wrong but isn't the i-9100 a whole different phone??? Looking at the specs and release date I would believe so. Sounds like he did an ics update for a phone that wasn't the Sph-d710 or something..
http://www.gsmarena.com/samsung_i9100_galaxy_s_ii-3621.php
Sent from my SPH-D710 using XDA App
not sure, all I know it by is: SPH 710
~ via My Epic 4G Touch & XDA'a app ~
Have you tried just flashing a kernel only in Odin
Sent from my SPH-D710 using xda premium
You tried flashing ICS on your phone, didn't you? B/C I'm pretty sure that's why you are seeing I9100 while booting up. If that is the case, do a search here as there are multiple people who have done this, and none of them have been able to fix it.
Sorry, your only solution is exchange at Sprint if you can, or JTAG.
help
beezar said:
You tried flashing ICS on your phone, didn't you? B/C I'm pretty sure that's why you are seeing I9100 while booting up. If that is the case, do a search here as there are multiple people who have done this, and none of them have been able to fix it.
Sorry, your only solution is exchange at Sprint if you can, or JTAG.
Click to expand...
Click to collapse
does not mean he flashed ICS when you odin a kernel that is not signed ie with CWM you will get yellow triangle and it will say i9100 too ..... so does not mean he flashed ics ... if odin sees the phone on a com port he probably didnt .... try flashing a working kernel from our phone
I did attempt to flash ICS. I could find where i got it, but it was supposedly for the Epic 4G touch, aka sprint sgs2 variant.
I am a network and systems admin, i should have known better. I jumped the gun and got ahead of myself. I have rooted and put roms on the og droid, and the droid x, samsung is a different beast all together.
However, i went in to sprint the day after i did this, they looked at it, no insurance, no replacement warranty, they didnt ask me anything, and THEY determined it was a factory defect , they had me sign a sheet that said "After researching found phone to be a factory defect and the solution from SPRINT is to replace the phone. $37.41, and 22 hours later i had a brand new SGS2 in my hand.
They hadnt sent my phone in yet. I honestly am not sure if they are going to be able to tell if i did anything to it or not, i may have just hosed the bootloader enough that odin wont connect, so they probably will have to use something like jtag in house to reflash it, or replace the chip or whatever they do. Even so, if they do see that i was messing with it, and say it voided my warranty, i have a signed receipt showing my payment and agreeing to pay for the replacement at $37.41, and that THEY determined the flaw. My brother in law is a lawyer, so i asked him, because i was curious if they would look at my phone at the service center or hub or whatever, and determine it was my fault. He assured me they could try, but it would all fall back to the employee who had me sign the agreement, so even if they dont like what i did, they are beyond doing anything about it.
I doubt they will even notice it, im sure they will try to boot it, then just flash it or however they do it.
Either way, im not worried anymore.
So...someone wanna point my idiot ass to an actual good rom, with a good method, that works for my phone? lol. I cant stand touchwiz, huge icons and cant replace them ....wtf is that all about.
Hi guys! I want to send my Nexus 7 (2013) to warranty service because it's bricked and I think the motherboard is destroyed. Will the service understand that the device is unlocked (bootloader) and rooted?
I could be wrong so wait for confirmation from someone else but if it won't even power on I don't think they would know, however if it powers on as far as the white Google logo you can see it is unlocked by the white padlock that is opened at the bottom, or closed lock for locked boot loader.
Sounds like it won't power on though if the main board is dead so I doubt they could know...
If it helps i had an iphone 4 that i jailbroke and it ended up bricked. It wouldnt connect to the computer or anything else. I had the same worry you have and when it was sent off i thought theyd find out. They didnt, and i got a replacement. If it doesnt connect to a computer they just dismantle them for parts. A repair engineer is more expensive to employ than a few idiots with screw drivers.
May be I am wrong about the mainboard. Yeah, I can turn it on, but I can go only to boatloader. It can be connected to computer (only fastboot mode) and there is unlocked padlock.
I guess need to lock the bootloader. But the device does not see any space (free or used) - I was connected it to computer and used a recovery mode with Skipsoft application. May be the memory is dead. It shows that cannot mount any partition. I don't know. Is there any way to lock the bootloader?
I am guessing you used Wug's root toolkit to unlock. I have seen others relock there's when there has been problems similar to yours, maybe check his thread out and ask in there.
Yep, I used his toolkit. But I tried every button in the application but nothing worked. I'll try to search deeper. I'm so afraid because I bought the device 1 month ago.
ryderbg said:
Yep, I used his toolkit. But I tried every button in the application but nothing worked. I'll try to search deeper. I'm so afraid because I bought the device 1 month ago.
Click to expand...
Click to collapse
Yeah I know the feeling
I am always worried about devices failing but after I have had it for about a year I wont be so scared and will take more risks with it usually. Only had mine for around 2 weeks and am also worried it could go off at anytime as mine is unlocked and rooted. Lots of people seem to have had problems with this device, my Xperia S never had problems
ryderbg said:
Yep, I used his toolkit. But I tried every button in the application but nothing worked. I'll try to search deeper. I'm so afraid because I bought the device 1 month ago.
Click to expand...
Click to collapse
Try this... http://www.android.gs/restore-un-br...4-3-jelly-bean-twrp-and-root-guides-included/
It might at least get it locked for you....
Thank you! I will try that as soon as I go home...
This is pretty much what danvee posted but still..
If you can use fastboot that's a good sign. You probably don't even need to send it in. Try this: http://forum.xda-developers.com/showthread.php?t=2469508&highlight=stock
You say something about no space? If the above link doesn't get you running again try this first: http://forum.xda-developers.com/showthread.php?t=2380913 Worked for me.
You can just flash twrp with "fastboot flash recovery recoveryname.img"(without quotes), wipe, then use the steps in the first link.
If that doesn't work it probably is some kind of hardware problem.
I just locked the bootloader. I used the command fastboot oem lock and there is no padlock now. Also Lock state changed to locked. I think now I can return the tablet in the shop.
ryderbg said:
I just locked the bootloader. I used the command fastboot oem lock and there is no padlock now. Also Lock state changed to locked. I think now I can return the tablet in the shop.
Click to expand...
Click to collapse
heres a funny story but what it resulted in and how i fixed it seem to apply to the problem you have.
i have a cracked screen on my nexus and it was registering a touch at intermittent intervals making the device unusable. i posted in here about the same time you did for help. while i was waiting to see if anyone knew if i could just disconnect the screen and use a bluetooth mouse with a hdmi adapter (slimport not mhl, thanks meekrawb) i connected a usb mouse with an otg cable. the mouse worked but i couldnt see how to turn off touch screen as an imput. as kitkat has been release and i hadnt updated i thought i would give it a try and see if that would reset the screen and stop the touch. It downloaded the update and when it rebooted it opened up a mod recovery screen (i forgot that i had rooted it). it asked me to slide a bar on the bootloader screen to continue. The usb mouse cursor was not present on this screen and the touch screen doesnt work so i couldnt get past it. i turned the device off and on again (what else do you do when your stuck) and it would open the google screen with the unlocked padlock but then just stay on a completely black screen. same as yours. I connected it to the computer and it recognised it. i opened wugfresh's root tool kit (old apple jb's sometimes had recovery abilities built into them so i thought this may aswell) i clicked on flash stock and unroot with the radial button on soft bricked and followed the instructions. now my device is unbricked and even the touch has stopped. Happy days hey. you'll need to unlock your boot loader again but its worth a try before going to the store, you can always lock the bootloader again if it doesnt work.
i know it didnt need all this to say "connect it to the root tool kit and try that" but i thought you would enjoy a laugh
Funny story. But my issue is hardware. The device doesn't show any space in it. No free nor used. I think the memory is dead. Also I relocked the bootloader, but now I cannot unlock it again because there is no space
Now when the tablet is with locked bootloader, it is unrooted, right?
Tommorow I will visit the warranty service and hope they don't understand about rooting and unlocking.
according to an email from "google play support India" , the device will be accepted under warranty as long as it has a stock firmware installed when you send in the device to claim the warranty.
I seem to be having tons of problems with this new phone =( HTCdev unlock failed work and now the phone has bricked while trying to do an update.
It is stuck on the "HTC powered by android" splash screen. The screen wont turn off and the phone does not change. Is there some way to fix this or am I farked? The phone is literally 3 days old and I hope there is a way to save it.
I can shut it down with Power and vol+ but when it restarts it just locks up. computer does not recognize it though it did install some form of driver.
Dlome said:
I seem to be having tons of problems with this new phone =( HTCdev unlock failed work and now the phone has bricked while trying to do an update.
It is stuck on the "HTC powered by android" splash screen. The screen wont turn off and the phone does not change. Is there some way to fix this or am I farked? The phone is literally 3 days old and I hope there is a way to save it.
I can shut it down with Power and vol+ but when it restarts it just locks up. computer does not recognize it though it did install some form of driver.
Click to expand...
Click to collapse
I would return it
Since I cant do anything until Monday I decided to mess with the phone a little more, I was able to get a custom recovery installed finally so hopefully all I need to do is install a new rom but the problem is the recovery is unable to mount my SD card to perform the install. I can read the sd card when it is in my old phone but not on the HTC One. Currently have Philz Touch installed as the recovery.
Is there any way to fix this or even bypass it all together?
Edit: I have been able to side load CM11 Nightly onto the phone so now it is functioning. I am having an issue with sound though so hopefully I can fix that.
clsA said:
I would return it
Click to expand...
Click to collapse
Warranty returns are for manufacturing defects, not botched mods done by the owner. The phone is completely recoverable.
redpoint73 said:
Warranty returns are for manufacturing defects, not botched mods done by the owner. The phone is completely recoverable.
Click to expand...
Click to collapse
This sounded like a hardware problem to me
I seem to be having tons of problems with this new phone =( HTCdev unlock failed work and now the phone has bricked while trying to do an update.
Click to expand...
Click to collapse
it's hard to mess the phone up when you can't even get the bootloader unlocked
clsA said:
it's hard to mess the phone up when you can't even get the bootloader unlocked
Click to expand...
Click to collapse
User error. The phone wasn't bricked (if the screen comes on, its not bricked) and 99% of the time when folks here say the phone is bricked, its just not booting. As you can see from his subsequent post, he was obviously able to get bootloader unlocked, custom recovery and custom ROM. Of course, you could have not known that when you made your previous post. But failed bootloader unlock, and then the phone won't boot, is a big red flag that the user just did something wrong.
redpoint73 said:
User error. The phone wasn't bricked (if the screen comes on, its not bricked) and 99% of the time when folks here say the phone is bricked, its just not booting. As you can see from his subsequent post, he was obviously able to get bootloader unlocked, custom recovery and custom ROM. Of course, you could have not known that when you made your previous post. But failed bootloader unlock, and then the phone won't boot, is a big red flag that the user just did something wrong.
Click to expand...
Click to collapse
Fair enough ... I read it wrong I guess
clsA said:
Fair enough ... I read it wrong I guess
Click to expand...
Click to collapse
Naw, really looks more like a matter of the OP needs being clear enough, and not giving enough info. If anything, best to get clarification before suggesting warranty service (especially once mods have been started - but again it was hard from the OP's description to know how far it got). Although if it was in fact a hardware defect, of course a warranty claim is valid.
So, My device got bricked. I didn't do root or anything. Recently the device got Android 7.1.2 update so I started the installation via OTA but (I DONT KNOW WHY) something gone wrong and the device gone into bootloop. My device was fully stock and had a locked bootloader but the device was still in 7.1.1 so I downloaded the 7.1.2 Update from the Google Developer page and sideloaded via ADB. The device finally rebooted into Home screen. So I was setting it up but suddenly it hanged and rebooted and the device was boot looped again but now its on a different case. Before, I was able to get the device back by Sideloading via ADB in recovery mode. But now when I tried to go into recovery mode the recovery mode DOESN'T EVEN APPEAR. It goes straight into the Google logo and goes to bootloop. Now I can't even access the recovery mode to sideload.
Please someone help
Dipto509 said:
So, My device got bricked. I didn't do root or anything. Recently the device got Android 7.1.2 update so I started the installation via OTA but (I DONT KNOW WHY) something gone wrong and the device gone into bootloop. My device was fully stock and had a locked bootloader but the device was still in 7.1.1 so I downloaded the 7.1.2 Update from the Google Developer page and sideloaded via ADB. The device finally rebooted into Home screen. So I was setting it up but suddenly it hanged and rebooted and the device was boot looped again but now its on a different case. Before, I was able to get the device back by Sideloading via ADB in recovery mode. But now when I tried to go into recovery mode the recovery mode DOESN'T EVEN APPEAR. It goes straight into the Google logo and goes to bootloop. Now I can't even access the recovery mode to sideload.
Please someone help
Click to expand...
Click to collapse
I believe you have the infamous bootloop issue.
Try to unlock bootloader if you can and flash everything manually. If that does not help, claim warranty or approach the place you purchased the device.
Dipto509 said:
So, My device got bricked. I didn't do root or anything. Recently the device got Android 7.1.2 update so I started the installation via OTA but (I DONT KNOW WHY) something gone wrong and the device gone into bootloop. My device was fully stock and had a locked bootloader but the device was still in 7.1.1 so I downloaded the 7.1.2 Update from the Google Developer page and sideloaded via ADB. The device finally rebooted into Home screen. So I was setting it up but suddenly it hanged and rebooted and the device was boot looped again but now its on a different case. Before, I was able to get the device back by Sideloading via ADB in recovery mode. But now when I tried to go into recovery mode the recovery mode DOESN'T EVEN APPEAR. It goes straight into the Google logo and goes to bootloop. Now I can't even access the recovery mode to sideload.
Please someone help
Click to expand...
Click to collapse
How did you manage to sideload without unlocking the bootloader?
Did you try just holding power and volume down while it was off until it booted and entered fastboot mode?
If you enter fastboot mode, use the arrow keys and power button to enter recovery mode.
ADB
Omnitrix4m3 said:
How did you manage to sideload without unlocking the bootloader?
Did you try just holding power and volume down while it was off until it booted and entered fastboot mode?
If you enter fastboot mode, use the arrow keys and power button to enter recovery mode.
Click to expand...
Click to collapse
I sideloaded via ADB in the recovery. But now the recovery wont even showing
indian84 said:
I believe you have the infamous bootloop issue.
Try to unlock bootloader if you can and flash everything manually. If that does not help, claim warranty or approach the place you purchased the device.
Click to expand...
Click to collapse
Ok the device suddenly boot up. I acted fast and unlocked the bootloader. But when everything is going fine. THE DEVICE BOOTLOOPED AGAIN. But now my bootloader is unlocked. So I flashed 6.0.1 it booted up and again bootlooped :crying:
Same here.
Are you part of the Beta program? Because I am, and after the latest "June 2017" update I suddenly started to have bootloops.
I can only reach bootloader but Recovery isn't starting at all, it just reboot and get into the loop again.
I've tried with the Nexus Root Toolkit, but the phone always get lost after the first reboot the toolkit requests to the device.
Any help here? It NEVER had any issues like that one, I've heard LG claimed it to be hardware related, but I got it after a software update.
This sounds like the infamous bootloop that many other people have encountered with the 5x. It is a problem with the actual hardware and isn't really permanently fixable by messing with the software. If your device is still under warranty, contact LG and they might be able to repair it. I had the infamous bootloop and they replaced the main board (free with warranty).
iSimon said:
Same here.
Are you part of the Beta program? Because I am, and after the latest "June 2017" update I suddenly started to have bootloops.
I can only reach bootloader but Recovery isn't starting at all, it just reboot and get into the loop again.
I've tried with the Nexus Root Toolkit, but the phone always get lost after the first reboot the toolkit requests to the device.
Any help here? It NEVER had any issues like that one, I've heard LG claimed it to be hardware related, but I got it after a software update.
Click to expand...
Click to collapse
LG never claimed it was a hardware issue for the 5X officially. Though due to some lawsuits they are extending the warranty on a case by case basis. The did acknowledge a hardware issue for the G4, which started production around the same time as the 5X.
What seems to happen is the later OS updates expose a hardware issue. Maybe by running a bit hotter. Some people, like me, had slightly reduced battery life after 7.1.2, which means the phone was drawing more power and heating up slightly more than before. My phone was on 7.1.2 for about 2 weeks before it just died while I was using it. Didn't seem to be a bootloop issue at first, but after fiddling around with it, and trying to fix it, that's what it ended up doing. Mine would never get into recovery either, until I used a hair dryer to heat the CPU on the motherboard since I didn't have a heat gun. I managed to reinstall the OS, but it took a heat gun to actually to get it to boot again. However, it lasted 9 hours then started bootlooping.
synesthete said:
This sounds like the infamous bootloop that many other people have encountered with the 5x. It is a problem with the actual hardware and isn't really permanently fixable by messing with the software. If your device is still under warranty, contact LG and they might be able to repair it. I had the infamous bootloop and they replaced the main board (free with warranty).
Click to expand...
Click to collapse
well I guess if it has been rooted ever then that voids any warranty. [excuse my language] god ****ing dammit then it's not fixable, christ LG are ****s.
aerolock said:
well I guess if it has been rooted ever then that voids any warranty. [excuse my language] god ****ing dammit then it's not fixable, christ LG are ****s.
Click to expand...
Click to collapse
I had mine fixed for free under warranty, so you should too, as long as it doesn't have significant other damage from drops or water, etc. I had rooted, unlocked and flashed many times. I did send it in stock, though, by flashing the stock factory images (mainly to clear personal data). I don't know what the official rules are about rooting and warranties, but I think that usually the Nexus phones allow you to unlock the bootloader and flash third party software without completely voiding the warranty. They are partly made as affordable developer units, anyway. Obviously, if you brick the phone by doing that stuff it is your fault, but if it is due to a defective part in your device, then they should be responsible to fix it. Even in the past I have been able to get an HTC phone repaired that was fully rooted/unlocked, because it had nothing to do with the hardware issue. Even if they say that your warranty is voided in the fine print from unlocking, sometimes companies will do the right thing and remedy issues that they are at fault for. Contact them, be polite, explain the problem/symptoms and ask if there is something they can do to help. When I contacted LG on their web chat system, I basically told them that the symptoms were most likely caused by a hardware issue and it seemed that the flash chip was failing. I told them that Google recognized the issue and has been refunding customers with the problem. I asked LG if they could repair, replace or refund my phone. The process went as smoothly as it could have gone for a situation like that (Other than unrelated issues with Fedex).
I would recommend just contacting LG, if you device is otherwise in good condition (aside from the bootloop). It can't hurt to try. Just know that the process of shipping it out, repairing, and shipping back might take about a week. Good Luck!
Ok, so when I went to the store I bought it from I said it was the nexus 5x bootloop issue thats with the hardware, then he asked me if I had done anything to the phone like rooting and I said I had rooted it once then removed the root, all he basically said then was dont waste our time asshole go somewhere else, so the previous root is the reason I can't get it fixed. But are you saying that if I call LG and dont mention anything about root then they'll fix it if I send it in? Luckily I found a spare phone so Im not handicapped but I love my 5x.
aerolock said:
Ok, so when I went to the store I bought it from I said it was the nexus 5x bootloop issue thats with the hardware, then he asked me if I had done anything to the phone like rooting and I said I had rooted it once then removed the root, all he basically said then was dont waste our time asshole go somewhere else, so the previous root is the reason I can't get it fixed. But are you saying that if I call LG and dont mention anything about root then they'll fix it if I send it in? Luckily I found a spare phone so Im not handicapped but I love my 5x.
Click to expand...
Click to collapse
I bought mine brand new on eBay. I rooted, Rommed, and otherwise tinkered with it unapologetically then ran into this bootloop issue almost a year later. I was able to contact LG support, send them a copy of my invoice from eBay showing that it was bought new and the date. I sent it off and they fixed it for free (replaced the main board) under warranty. Just go through LG support and they will almost certainly get you taken care of. It took a little over a week, but it sounds like you have a phone you can use during that time.
I purchased a 5x through Amazon over year ago and it is now bootlooping. I have tried all known fixes. I am in the US and I purchased the international version unknowingly. The LG US support site does not recognize my H791 version and I doubt that I can send it overseas. Am I out of luck getting this phone fixed?
Sent from my Nexus 6P using XDA-Developers Legacy app
my phone died on me. first it started to normal, or slow charge instead of fast charge and then it wouldnt charge at all. after sometime waiting it charged for a few days and then started saying the usb port ist moist and now it doesent charge at all again. if never been in the rain with the phone though. good for me is that it will stay on in twrp and download modus. i guess it charges just a little bit so it dont goes off. long story short i want to revert back to a samsung stock rom or at least to stock recovery and send the phone to a samsung repair center. i know u guys are thinking that with root my warrenty is void but back then with my note 1, s4 which where also rooted samsung made no fuse about it. a bit of googling revealed that alot of users had the same expirience with their note8/galaxy s8.
See if you can get into Download Mode then flash stock with Odin 3.13.1
windows says unrecognized usb device. i red that there are apps like mobile odin or flashfire but both are not developed anymore
Download Devbase ROM and put no root mode on and flash in TWRP
Extract recovery.img from stock firmware and put on phone and go to install and > images in TWRP and select the recovery.img of stock ROM and swipe to flash it to the recovery partition
Simple method and done!!
could not boot. invalid kernel lenght. thx very much for this! now samsung wont repair it for sure!!!!! you should be held accountable for the nonsense you posted!
k2828 said:
could not boot. invalid kernel lenght. thx very much for this! now samsung wont repair it for sure!!!!! you should be held accountable for the nonsense you posted!
Click to expand...
Click to collapse
I told you to flash the stock recovery.img to the recovery partition, if you are recieving this error you flashed to the system partition most likely, In that case, Try to clean your port and get download mode going , This would of worked fine if you flashed it to recovery.
k2828 said:
you should be held accountable for the nonsense you posted!
Click to expand...
Click to collapse
Actually the opposite is true, YOU are responsible for anything you do to your phone, regardless of it being posted here, stated many times throughout the forum
Do not ever listen to this guy euardo i flashed the the recovery.img to the recovery partition and this happend.
k2828 said:
Do not ever listen to this guy euardo i flashed the the recovery.img to the recovery partition and this happend.
Click to expand...
Click to collapse
Don't flash your phone custom if you don't know how to fix it afterwards, no-ones fault but your own, no-one forced you to do anything
Use IPA (alchohol) and a toothbrush to clean your port. Get in there with a light or a macro lens on a camera and see if there is dirt or a bad gold plate connector.Let it air out for a few minutes after the alchohol. Leave your phone plugged into the wall and see if it will charge.
@alvinator94 thx but i think its a bad component on the chargin port board. it charges every 50th try but on the pc i get the error usb device mallfunctioning.
@detection i know how ti fix it. just change the port and flash it via odin. just dont wanted to give up warrenty for possibloe touch issues. and given wrong advice instructions is indeed punishable. otherwise you wouldnt find any disclaimer etc in the OPs
k2828 said:
and given wrong advice instructions is indeed punishable. otherwise you wouldnt find any disclaimer etc in the OPs
Click to expand...
Click to collapse
No it's not, disclaimers mean that whatever YOU do is YOUR responsibility
And if you know how to fix it, why are you wasting everyone's time here?
Odin does not void warranty, you already did that by flashing TWRP
*Detection* said:
No it's not, disclaimers mean that whatever YOU do is YOUR responsibility
And if you know how to fix it, why are you wasting everyone's time here?
Odin does not void warranty, you already did that by flashing TWRP
Click to expand...
Click to collapse
wrong again. changing the software of a device you own doesent void warrenty. samsung would need to prrof that the damaged you want to remedy is coused by root. which should be preety hard. this is so in the usa and in the eu as well. send in alot of phone rooted phones to samsung and the internet is full of statements underlining my expirience. stop the circus please.
k2828 said:
wrong again. changing the software of a device you own doesent void warrenty. samsung would need to prrof that the damaged you want to remedy is coused by root. which should be preety hard. this is so in the usa and in the eu as well. send in alot of phone rooted phones to samsung and the internet is full of statements underlining my expirience. stop the circus please.
Click to expand...
Click to collapse
Flashing custom = tripping e-fuse knox = void warranty
Time to put you on ignore
yeah right. go on belive the corporates instead of curt judgments.
Back from repair and guess what....its repaired for free by samsung