Hi, I'm a bit stuck with a problem on my S2 HD LTE SHV-E120K. While once playing a game the phone heated up pretty much (the charger was connected). After that it rebooted. I thought that the stock ROM got corrupted so I changed the recovery from Tegrak (phone was rooted with this a while back) to CWM 6.0.3.6 and loaded CM10.2 (cm-10.2-20131027-NIGHTLY-dalikt). To my surprise its still rebooting. But when I disconnect the charger the phone reboots and at times when charging it also reboots. If the charger is not connected the phone does not boot up.
Can anyone say what or where the problem may be?:crying:
Sounds like USB board on the fritz. I don't know for certain if your specific variant uses the exact same boards as the I9100, but have a look at KeithRoss39's guide to replacing the USB board in General (search for 'replacing USB charger board').
You'll probably find Keith's how-to will hold true for your model as well (so far as following the same procedure goes), you just have to ensure you order the correct replacement part - and the way you do that is by removing the board currently in the phone, noting the revision or part number, and making sure you order the exact same part.
Wow! I did suspect this but never thought it could be the case. I'll look at that article. But anymore suggestions are welcome.
But if the battery is fully charged then the phone should boot up without a problem right? But it doesn't It needs the charger to be connected for it to boot.
When you say USB board would you be able to say if you mean the USB port specifically or some small chip on the USB board assembly?
The board has the port attached and is really cheap to replace (~US$10 or so), and quite replaceable by most people if you follow Keith's guide. When the board starts acting up, it often shows symptoms you're describing. And as it's a cheap/easy fix, that's what I'd be doing. Try a clean install of stock first (even if you've come from stock recently) to absolutely rule out a rom-side problem if you want to. I'd be surprised if it's still not the same though.
As to specifically what component on the board is causing the issue, no way to say for certain, and it's not really relevant here; the fix is still replacing the entire board given the modular design of phones these days & the low cost of doing so.
I saw Keith post to another thread in Q&A just now, I'm sure he'll also post to this thread & give you a bit more info (he's the resident expert on these things here).
Ok got you. I have not been able to find any links to stock rom downloads. Do you have any? Also, what recovery is to be used with the stock rom? My phone was bought from Korea on ebay. It displays ''Olleh'' in the boot image. Just to let you know so you may be able to figure out which stock rom this is.
I've checked Samfirmware, and they don't have firmware for your device specifically, so I have no idea (beyond Googling) where you might find stock firmware or if you can use firmware from other devices in the same 'SHV' family. I honestly don't know.
I gave you advice about the USB board because it's generic & quite likely the source of your problems, but I'm not even a little familiar with your device so I can't give you detailed/specific help with it.
Given how little traffic the S2 forums get these days & how few people here have SHV devices, your best bet (other than waiting, and it could be a very long wait) is to trawl through the forums here with XDA searches (or Google searches with XDA appended to your search terms, XDA search isn't the best at times) to find the info you need.
Would you know how to remove CWM recovery and get it back to stock recovery after I install the stock rom?
If you flash a stock rom, stock recovery will overwrite CWM. Everything will be stock (recovery, kernel, etc).
Edit - Assuming your phone is similar to the I9100 in having recovery baked into the kernel (unlike more recent Samsung phones which have the kernel & recovery in separate partitions).
Related
I used Oden to flash a Samsung Galaxy S II rom to it and now, it only shows the Samsung logo at bootup. No recovery menu. If I try to access the recovery menu, it kicks me out and reboots. Samsung galaxy player 5.0 All Touch Buttons including home.
If you can get into download mode by holding volume down at boot, you can just reflash stock.
Sent from my YP-G70 using Tapatalk
Um, okay, for future reference NEVER FLASH ANYTHING NOT SPECIFICALLY MADE FOR YOUR DEVICE! I learned that the hard way, so not saying your stupid, just think a little more before you try to flash a rom for a dual core phone that's only resemblence to a Galaxy player is the word Galaxy. I find that for some reason, each phone has to have a different strain of android, and their roms never, NEVER, mix. So, I am stating this just to warn others new to android, not to make you look bad (I made a similar mistake of trying to flash cwm that someone assured me couldn't possibly brick my device, what a noob I was!).
Yup... NEVER flash something not designed for your device unless you know EXACTLY what the hardware differences are and how to deal with them, or you've been given specific instructions on how to port firmwares to your device.
(I9100 ROMs are so easy to run on I777 that they can be autoported with a CWM-flashable package now, but that's because the I777 is 95% identical to I9100. There will be nothing that can be "hellraised" to the Players, except possibly being able to creat "common" ROMs that target both International and US with a small zip file containing the differences flashable in CWM.)
Mate, I'm in the same boat where you used to be. Just a little worse.
Long story short: flashed, by mistake, the entire i9000 rom, including boot loaders, through Odin. Got a "black screen", "no reaction" brick. Computer won't detect no matter what button combo I throw at it.
Samsung Galaxy Wi-Fi 5.0"
YP-GB70CWXAZ (8GB) brazilian edition
I need some details about jtag and the micro-usb port. Also, in the current state, can I try to format a sd card & see if the player recovers from it? Like the Samsung Development Board? When everything is screwed, the usb pins can be used as a jtag port to avoid opening the device, even though I already did it.
PS: I've already located the 12 pins (jtag) & another 4 points on the main board. Just don't know how to check if the second ones are also jtag. The blue coating is also scrapped & ready.
Thanks.
Peace.
You might want to try AdamOutler oneclickrecovery before messing with JTAG. You can find it here.
This will upload a bootloader so you can re-flash the device with odin.
I have tried to recover my YP-GB70 (32gb korean version) with AdamOutler tools with 80% success.
Anyway thanks a lot for the tool and your great help.
What I did:
under odin I flashed original YP-GB70 32gb PIT plus the provided "AdamOutler bootloader and the latest korean firmware (pb is the same with any earlier FW version)
The result i got is almost perfect, i passed SAMSUNG logo, the boot ring tone and went the GALAXY sky where it stay looping. (All wipes where done before.)
My questions are:
-What is missing in this Flash process?
-Is the bootloader specific for US version or device related?
-Any idea of what I should do to succeed?
You are welcome to expertize this issue because a solution will be a good tool for many imprudent guys like me.
attached picks of 3 diferent trials done lately.
best regards from France
Lolo9393
Full story: Sold my phone, tried unrooting, soft brick, went back to stock, flashed Cameleon ROM 3.0.2, starts acting weird (more frequent freezes and reboots, vibrates for about 5-10 seconds when it's been off for a while), charge and boot up this morning, and now phone refuses to connect to any network. IMEI's not blocked or anything. TriangleAway formatted my internal SD, so no backups. Also said the battery was at 100% every time I rebooted, even though it was ~85%. Clean flashing CM10.1 didn't help. I've searched everywhere and nothing seems to help. Warranty's out long ago. I'm incredibly frustrated and desperate for a solution
Who knew running low on battery could cause this?
Running on low battery didn't cause it, tho it could be a simple case of needing a new battery. Might want to try that first, tho it does sounds like the USB board is on the way out. This gets discussed here all the time, search for these threads & read them very carefully. There's 4 different revisions of the board; you need to order the same one that's currently in the phone or your phone may not work properly. Other than that, it's quick/cheap to replace yourself.
So if a new battery doesn't do it, replace the USB board.
Edit - Re: the phone not connecting to networks, how do you know for certain the IMEI isn't blocked ?
MistahBungle said:
Running on low battery didn't cause it, tho it could be a simple case of needing a new battery. Might want to try that first, tho it does sounds like the USB board is on the way out. This gets discussed here all the time, search for these threads & read them very carefully. There's 4 different revisions of the board; you need to order the same one that's currently in the phone or your phone may not work properly. Other than that, it's quick/cheap to replace yourself.
So if a new battery doesn't do it, replace the USB board.
Edit - Re: the phone not connecting to networks, how do you know for certain the IMEI isn't blocked ?
Click to expand...
Click to collapse
Of course, I don't know for certain. I used AMTA's checker, and apparently it's not blocked.
I'll try repairing the board. In the meantime, I'll contact the police to find out about the IMEI. Thanks!
Something similar happened to me, try to flash your device with an official ROM, preferable Android 2.3 root your device, then search the GB's Modem or baseband, find the one compatible for your network or country and then you need to flash it via CWM recovery of course you need to be rooted, do a full wipe before you flash anything. Doing this you device should be fully functional and then you can install any Custom Rom. Hope that helps..!
A relative of mine has a cheap tablet and it's pretty beaten up. However, he wants to give it to his niece and isn't of a mind to buy a better one. He got it second hand, and the thing turns on, and goes to an "android" screen. There, it does nothing. It freezes and stays that way until it dies. I was wondering what the best way to go about trying to fix this thing. Would identifying it be the first thing and if so, could anyone offer some guidance? I'm no stranger to rooting and flashing custom roms and the like, just not sure where I'd start. Any help would be greatly appreciated.
Bump
ninjames, have you checked if this device has a recovery installed. If you are lucky and find the correct buttons to boot to recovery maybe resetting to factory defauls will bring it back to life.
Can post a link to a picture of your device (front and back). Maybe someone will recognize it and will point you to a stock rom which you can reflash.
- Identify the device (OEM, model etc.)
- If it's a "known" OEM, it probably has its own forum section here, so check that out for more help if that's the case.
- Try to google "device name + model + bootloader buttons", and if you're lucky, the bootloader will have its own stock recovery (like Samsungs, LGs etc.)
Hello,
Before anybody gives me the "Use search" or "Here's this link, it solves everything" : I tried all of that !
I read countless number of posts, I tried many things !
So here is what I have :
- Samsung Galaxy S II (GT-i9100) not booting (Stuck at Logo + recovery mod not working (Download mode is))
- Can flash (Tried many different ROMS
- Stock ROM "Ice Cream Sandwich XWLP7 (4.0.3)"
- Stock recovery mod not working but ClockWorkMod's one works when I put it
What I tried :
- Tried to delete data/reset user factory
- Tried to put different versions of CyanogenMod's ROM
- Tried to put different versions of Stock ROM
- Used a stock pit file to repartition using Heimdall
I'm out of clue, if somebody has an idea what I can try ...
Thank you very much !
Edit : Forgot to say, I have access to adb interface
Given you say you've tried 'everything', what exactly do you expect anyone here to suggest ? Motherboard replacement; new one by Samsung service centre (expensive option), 2nd hand one you source online & either swap yourself or pay a local mobile repair shop to swap (cheaper option).
MistahBungle said:
Given you say you've tried 'everything', what exactly do you expect anyone here to suggest ? Motherboard replacement; new one by Samsung service centre (expensive option), 2nd hand one you source online & either swap yourself or pay a local mobile repair shop to swap (cheaper option).
Click to expand...
Click to collapse
Thanks for the answer, I hope I didn't get too patronizing in my post
So basically my phone is bricked? Can't do anything about it?
Yeah, you did. And that's why I gave you that response.
Right...Now that we have that out of the way, search for Hopper8's 'Odin troubleshooting' thread. I don't think the link to 3 part firmware in the thread is live anymore, but the first thing I'd be doing is trying to hunt down any I9100 3 part stock firmware (not 4.0.4 though) & flashing that. Rationale being as it will wipe your phone, maybe it will remove remnants of what was previously on the phone & which may be causing problems. It's a longshot, but worth trying given the alternatives.
I'd also keep flashing stock firmwares (as many different ones as you can download), and go through all the troubleshooting steps in Hopper's thread. There's always a chance something simple/obvious is being overlooked which is tripping you up, which is easy to do if you've been at it for ages & have had no joy getting it fixed.
If after having done those things the situation hasn't changed, take it to someone who does JTAG's, and if they're prepared to have a look at it on the basis of 'you only pay them if a JTAG is possible' (I know a couple of repairers near me who do this, YMMV though), try that. It's unlikely to work/be possible, but worth trying.
If it isn't JTAG'able, then you either look at motherboard replacement as per my PP, or a new phone, as it's obviously a case of NAND corruption.
The 3 part firmware in hoppers guide is good........I'm hosting it now.....
Try the mediafire link before the dropbox one......
This might be my S2, or it might be my W...but it's definitely CM
Good news Might grab a copy myself in case it ever goes AWOL.
No probs MB.....that's what it's there for....
This might be my S2, or it might be my W...but it's definitely CM
Thank you very much for the 3 part stock firmware but it didn't solve my problem :x
I still have the phone not booting and the recovery mode bootlooping
I'll try option 2, I downloaded a bunch of stock firmwares from Sammobile and will flash my phone over and over
But I'm starting to get the impression that it's not gonna work...
I'll start asking around me if anybody has a not-working SG2 to get his motherboard
Definitely keep trying, but yeah unfortunately, you might want to start looking for that 2nd hand board.
Hello.
A year or two ago I purchased this Samsung Galaxy S2 GT i9100 from Ebay, which came to me in Chinese. I changed it to english, eventually, but I could never get it to update firmware, which was a minor contrivance. I continued using it for a long time, with some reservations.
Though two days ago, I finally got around to giving a workaround a shot, which didn't work. I tried another, and another; and nothing worked until I gave up and then all of a sudden, kies decided it would update the firmware out of the blue - without me actually doing anything.
Go figure.
Anyway, the phone started working great until I did some updates on my apps, I lost my "Navigation" app which I am told, most likely got put back into google maps (as it was a part of it) and the phone has crashed twice, frozen for several seconds several times and been quite slow in general since. I googled a bit and found that the culprit was likely the /data/logs - but I cannot get to them as the phone isn't rooted. I deleted some apps to make room on the phone, as it was 1.8/2gig (wouldn't let me update half of my apps at one point!), bringing it down to 1.4 but that had very little affect on the phones performance, and I still have half a dozen Gigs left on the USB. So the logs seem to be the culprit at this point.
Further googling indicated to me that I should err on side of caution and factory reset the phone, but I was unsure whether I should do it before or after rooting the phone, which caused me to find out about this "brickbug".
And I also found out, by an "eMMC brickbug checker" app, that I have a:
Type: VYLOOM
FwRev: 0x19
Brickbug? YES. Insane Chip.
Which leads me to asking you guys what the best process for me to go about this is, considering that I need to not brick my phone as I return to university in two days, but cannot continue with phone locking up and crashing?
Should I skip on the factory reset and just root phone, and if so which process is best, there are so many?
If further info, which update etc, is needed to select proper method I require, please let me know how/where to find it, and I'll post it asap.
Thank you in advance,
Don.
Whether you have a susceptible chip or not is largely irrelevant; the brick bug is triggered by running rooted stock 4.0.4 & doing a factory reset, anything else & you're fine.
I'm not sure why you think rooting the phone is going to fix the problems you're describing ? I'd only be rooting the phone if you have a specific reason to do it. Also, if you absolutely cannot be without your phone, don't root or flash anything to it ever. Sometimes stuff goes wrong, and you simply can't completely remove that risk regardless of what some people on here might tell you (even tho that risk is very very small for a given flash).
So...If I were in your situation, first up a factory reset. If that doesn't help, find Hopper8's 'Odin troubleshooting' guide stickied in the General section, download the 3 part firmware linked in the thread, flash it with Odin. This will wipe your phone. I'd then download a stock rom for your country/carrier from Samfirmware (anything but 4.0.4) & flash that with Odin. This will give you a clean installation & should resolve your issues. If it doesn't, you're probably looking at either something on the app side not playing nice, or a hardware issue.
If you want to root the phone or flash a custom rom from there, that's up to you, but be mindful of the potential for stuff to go wrong. So far as methods to do these things go, this stuff has been/asked answered thousands of times here over the past 2.5 yrs. We have stickied threads near the top of Q&A & also a thread with a multitude of guides/tutorials stickied near the top of the General section. If you do go down this path, taking as much time as you need to read/learn/understand methods on your own (as opposed to someone regurgitating a bunch of steps you don't understand the consequences of) before you do anything should limit the chance of 'accidents' happening.