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..!
Related
Hello XDA! This is kind of long winded, but I'm at the end of my tether with this and all I want is a functioning GS2 back in my hands!
I have an international GS2 that i've owned since they appeared in the UK. I rooted it after a month of running stock and then started flashing ROMs pretty soon after that. I have flashed many many ROMs, all with success and no issue whatsoever.
However....
I now have a GS2 that boots into recovery, boots into download and will boot into a ROM. Once booted into a ROM, it will freeze, either instantly or after a period of minutes. The screen becomes non-responsive yet the ROM seems to function, calls come in and continue and it still connects to a PC to browse storage etc.
I've wiped and flashed a multiple of ROMs - CM, RR, PA, multiple official stocks. Followed all the install instructions as per usual. Never took any shortcuts or whatever.
Inbetween all this the power button stopped working. Took this to my local store, they showed me the water damage, they replaced the button and that was rectified, working again.
So....basically no ROM would work properly at all. I assumed that this was a soft brick of some sort and gave up hope of getting this fixed myself. Took it back to the phone shop, explained the issue and he said it should be repairable, good chance it was just a software issue and that if worst came to the worst it would go on the JTAG and be flashed back to stock and I would lose everything but have a working phone.
Obviously the phone was picked up today and it's still the same. Boot into stock ROM and pretty much freezes instantly.
The phone shop dude said he tried a new screen to see if that was issue, it wasn't. They tested all the connections on the board and there where no shorts apparently. They had it on the JTAG multiple times, that didn't fix it.....
Doe's anyone have any idea what could be the cause. Do I just let it RIP or is there a chance someone out there can fix this.....
Thanks in advance and sorry for the rambling post. I thought I better lay out all that's happened with the phone and the work that has been carried out on it.
G
Did they check the battery?
I assume they did.
Nuke scripts can clean all previous ROMs leftovers and format system will get your device all cleaned up.
If those 2 don't work, hardware it is, swap shops and see.
Sent from the little guy
Could be a GPU issue. If it is then you will need a mobo replacement or replace GPU if possible.
Alternatively you should do a complete clean install or rom which means make sure all the old files and partitions are cleaned before installing a rom. First simply try using a rom/kernel cleaning script and the flash custom or stock rom. Another way would be to format internal and external sd cards via CWM and then flash rom.
If you still have issues after doing above then you have a hardware issue and will need new mobo.
Hey all, before I say my problem, firstly I have no idea if this is the right section in the forums so apologies in advance, secondly, I have held out for 3 days trying to work out various issues before I posted. I probably did just miss one thing or misread another but no matter how much I look, no idea what as new to this. Thanks in advance for your help.
Basically, wanted to flash some custom firmware to my phone, I have been having many issues with backing up on Kies, seems to be something related to my USB's and my computer, it keeps failing during the backing up of programs. I ended up giving up on this, made a titanium pro back up of System files and of programs, also made a Nandroid backup, both on my internal phone memory I believe. Have root access, installed busy box and such, backed up some other stuff using EFS Pro, now I am completely confused, I have followed a few guides dotted around the internet, tried to install some custom firmware, it was Carbon Rom 4.2 I believe. I went into the CMW menu, wiped data/factory reset, wiped partition cache, and wiped dalvik cache, installed the rom from my internal phone memory, as it would not find it on the memory card when I tried, and now after two attempts of it seemingly doing it, on rebooting the phone, I go back to the Samsung firmware.
I have tried to read up as much as I can but obviously I am missing something here and no amount of guides or google searches have hinted at my problem, could anyone help? I know people asking constantly for information on how to put on custom firmware will be irritating, but I have genuinely taken this as far as I can alone Cheers
Now after formating something under mount/system, my phone is stuck on the logo screen, reinstalling the ROM does not work either, no idea what to do now
reflash rom, wipe data and voila.
Hey, thanks for the reply. By reflash rom, which way do you mean, am pretty confused still. The rom I download basically bricked my phone, I don't know why, I think to recover it I use ODIN and get my stock software, so is that what you mean? Or can I somehow use my Nandroid back up..?
deancolt45 said:
Hey, thanks for the reply. By reflash rom, which way do you mean, am pretty confused still. The rom I download basically bricked my phone, I don't know why, I think to recover it I use ODIN and get my stock software, so is that what you mean? Or can I somehow use my Nandroid back up..?
Click to expand...
Click to collapse
If you have a Nandroid restore that or flash your original firmware via Odin .
Never restore system files after a firmware change with TB .
jje
Ok here is the situation now, I have made things 100 times worse, I possibly should not of been doing it this late... I followed guides exactly though and there is definitely something not working right with this phone, I just don't know what, all I know is its very temperamental with connecting to computers and will fail doing the custom firmware flashes half the time, no matter what I use, even using the stock ROM i got from samimobile has caused many problems. It might be me, I don't know, but in my frustration followed some advice on a forum and I think I formatted the mount/system. SO obviously I lost both my back up's. My fault and can live with that, phone was bricked and had to do that to get past it I think..
But now no matter what kernel I use and have tried quite a few including my original one, I am unable to connect to my home wifi. It definitely is not the wifi, it worked just fine before I flashed the phone and has been working with it for 4 months, now whenever I set up the phone its constantly stuck in this obtaining network ip infinite loop. No fixes I have used have helped at all so far Sorry to keep asking stuff, I am just literally at the end of my tether, was up until 7am messing with it to no avail.
Just to reiterate a point, the reason I wanted custom firmware was because the phone was crashing randomly and just dying on me and also the speaker had lost like 90% of the volume when I wanted to play music, also it would not connect to my computer with ease, now obviously before I did anything it had issues. So that is why I feel something might be wrong, not saying I did not break anything myself, just the process of flashing the firmware has been pretty straight forward once I did it a couple of times, it has just been failing and bricking every other time, so I am not sure what the problem actually is, did I miss a step, did I mess it up? If not what has. Please helps guys. Regards.
I formatted the mount/system. SO obviously I lost both my back up's
Click to expand...
Click to collapse
formatting system wouldn't touch your backups
deancolt45 said:
Just to reiterate a point, the reason I wanted custom firmware was because the phone was crashing randomly and just dying on me and also the speaker had lost like 90% of the volume when I wanted to play music, also it would not connect to my computer with ease, now obviously before I did anything it had issues. So that is why I feel something might be wrong, not saying I did not break anything myself, just the process of flashing the firmware has been pretty straight forward once I did it a couple of times, it has just been failing and bricking every other time, so I am not sure what the problem actually is, did I miss a step, did I mess it up? If not what has. Please helps guys. Regards.
Click to expand...
Click to collapse
Usual reply if you did not know what and why and had never bothered to read the faqs and guides before flashing .Then its nearly always user error .
Best take it to a service centre and pay for a repair .
jje
edinghn are
Close thread please
Found out something really handy
Hi guys,
TheGS3 has 1 huge trick when u got stuck in firmware, CSC, etc.
Especially when u used some super usefull toolkit (like me)
I used the Galaxy S3 Toolkit, option4 (ALL in ONE) just push enter 2 times
1 to start and the last one to exit...
Got all the issues i read on hundreds of pages searching for the solution.
Accidentialy i found this morning (its 4:45am right now and busy with it since 15:00)
Start Kies, connect GS3 with USB kabel and when it says not connected take out USB
Dont plug in USB for a while...
In KIES go to Tools and irmware upgrade.. Remember, DONT plug in USB
It will ask u for your model nr which is printed on sticker in baterycover
Confirm and it will ask u S / N' which is printed on same sticker
It will start downloading firmware and u will be guided through update progress
Good Luck to y'all.. Time to go to bed.......
Hello,
I have a Samsung Galaxy S2.
After reading this post http://forum.xda-developers.com/showthread.php?t=2382579 I decided to root my phone.
So I went ahead and started with this step http://forum.xda-developers.com/showthread.php?t=1118693 because I was unsure if I had a kernel with the MMC-SUPERBRICK-BUG.
After I flashed CWM-SuperSU-v0.97.zip using Odin version 1.85 and after the phone rebooted it was stuck at the "triangle screen" for a few seconds then the display went black and I couldn't do anything further.
Up to this point the phone was still accessible in download mode (volume up, power and center button). I believe this is called "download mode". Sorry but I am a complete noob with rooting phones, etc...
So I panicked and took the phone to a repair shop (big mistake). The guy ran it in download mode then tried to flash something onto the phone (I think he used all 4 fields: Bootloader, PDA, Phone and CSC.
Then, in the middle of the operation, Odin froze when writing "setting up connection". Then the phone died ! pressing the 3 famous buttons does nothing and the phone just stays dead.
I had to leave the phone there as the guy said they will try to bypass stuff and try to connect to the CPU directly (sorry again if this sounds noobish). I did update my modem firmware and my computer BIOS in the past... but I guess this one was more complicated.
At the shop, they asked me to check again in 3 days. I am lost here. I don't know what to do anymore.
Is the phone hard bricked ? Should they bear all expenses for what they did ? I would bring back my phone and try something like this http://forum.xda-developers.com/showthread.php?t=1878255 or even a stock flash but I am afraid I cannot do that as the phone isn't even powering up anymore after they tried to repair it at the shop.
Any advice is appreciated.
Nope. You borked it. You tried to flash custom firmware to the phone & obviously failed spectacularly at it. Instead of trying to flash it yourself via download mode (which you could easily have done unless the NAND was borked), you paid them to do it. Sometimes flashes go bad. Sounds like that's what happened in this case.
Reading between the lines they sound like they're going to try & JTAG it (or have someone else do it). And if that fails I presume they'll change motherboards. You could always get the phone back & take it to someone who does JTAGs if that shop doesn't themselves.
MistahBungle said:
Nope. You borked it. You tried to flash custom firmware to the phone & obviously failed spectacularly at it. Instead of trying to flash it yourself via download mode (which you could easily have done unless the NAND was borked), you paid them to do it. Sometimes flashes go bad. Sounds like that's what happened in this case.
Reading between the lines they sound like they're going to try & JTAG it (or have someone else do it). And if that fails I presume they'll change motherboards. You could always get the phone back & take it to someone who does JTAGs if that shop doesn't themselves.
Click to expand...
Click to collapse
Yes I know I failed at it
Or maybe the shop technician is the one who broke it. At least when I had the phone with me I was still able to boot in Odin mode.
Do you think I could have recovered my phone if I had kept it with me and it was booting in download mode ?
I feel so pissed that I took it to that shop. I just wish I hadn't panicked and I had tried, instead, to fix it at home by asking for more help.
Anyway I still haven't paid them anything so far.
We agreed that they will pay for the motherboard because I brought in a working phone (that would power up at least). The owner of the shop was nice enough to agree that he would only charge me fees for installing new software on the phone (even if they have to change the motherboard) because he knows the phone was booting in Odin mode when I came in to the shop and his technician flashed the wrong firmware.
I also wrote down the board serial number so I can be sure they changed it (if they say they did that). So you are telling me the phone can still be fixed ? What does JTAG mean ?
Even if it is fixed I think I will be too scared to try and root it again. Unless I can understand in advance, step by step, what I need to do and what file version(s) I need to use.
Ok, I got my phone today in good working condition.
According to the shop, they had to replace an IC (I don't know what damaged the IC, I am assuming this happened when they tried to electrically jolt the phone) then JTAG it to get it to work again. They charged me a small fee (and they did end up bearing more than 50% of the expenses) because I brought in a phone that was booting in download mode and they take responsibility for what happened after that (flashing wrong files which caused the phone to completely stop booting).
Anyway, long story short, this was my first attempt to root a mobile phone and I learned my lesson.
I am running the following:
Model Number: GT-I9100
Android Version: 4.0.3 (which I will need to upgrade to 4.1.2 of course)
Baseband Version: I9100XXLPW
I know you will say read the sticky posts or the guides but the truth is, that's exactly what I did (you can see the links to the guide I tried to follow in my original post) and I still ended up failing at rooting/installing cyanogen on my phone right after installing Clockwork Mod.
The truth is I am scared to try again and mess up the phone. So this time I would rather be safe than sorry.
What can I do, this time, to safely root it and install a mod like Cyanogen.
Detailed steps are appreciated:
- Do I need to upgrade to 4.1.2 before rooting as 4.0.3 might have the superbrick bug ?
- How to backup the phone.
- Odin version to use, ClockWork Mod version to use, Cyanogen version to use
- How to connect the phone, how to reboot in download mode and all the necessary actions to avoid bricking my phone.
No spoon feeding aloud on XDA.better to read and learn how to do this and that but before you flash anything after learning how to do that learn how to fix it if it doesn't work. :thumbup:
andrewwright said:
No spoon feeding aloud on XDA.better to read and learn how to do this and that but before you flash anything after learning how to do that learn how to fix it if it doesn't work. :thumbup:
Click to expand...
Click to collapse
Fair enough, I figured I'd get that reply from someone and it's normal to be honest.
I decided not to try anything on my phone before I re-read the guides and be sure I know what I am doing.
I will also keep the phone running on stock firmware (after upgrading to JB 4.1.2) to check the battery consumption behavior which, I hope, will be fine since someone tampered with my phone's electronic components at the shop.
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).
Sorry for a very strange problem.... My wife still uses her old S III (I9300), although it is so outdated and partly broken. Some time ago we flashed CM 12, so that some apps who need a more up-to-date android can be used. But the phone is too slow, there is a crack in the display and sometimes it starts to reboot without any reason. There is not enough memory to install additional apps and without LTE it is no fun.
=> I want to buy a new smartphone for her, but she doesn't want to. She wants to save money and use it, until it is not usable any more.
Of course I could give it a good strike with a hammer or give it a treatment in the microwave oven, but I would prefer only a temporary lack of functions, so that perhaps later I can use it as backup phone for the kids. Therefore I am looking for some trick, app or system setting to SIMULATE, that the phone is broken. When she is happy with her new phone, I intend to "repair" it "by chance"....
Any ideas? How can I simulate, that the phone is broken? Thanks!
You need to hardbrick it.I dont know how to but you can Google it.
ArdaCsknn said:
You need to hardbrick it.I dont know how to but you can Google it.
Click to expand...
Click to collapse
Thanks for the reply! I googled, but i think i want to SOFTbrick it, not to hardbrick it. As I wrote above, I want to "revive" it after some time....
I think the simplest way may be to take the phone, create a backup of all data, put the phone into download mode, start flashing a stock ROM, remove the USB cable when it starts to flash the final file, and reboot the phone. Hopefully, the phone will display the "firmware upgrade encountered an error" message which can be resolved by re-flashing the stock ROM with Odin.
Based on my experience with flashing a stock ROM over a stock ROM, this procedure always leaves the data and apps intact.
cm_new said:
Thanks for the reply! I googled, but i think i want to SOFTbrick it, not to hardbrick it. As I wrote above, I want to "revive" it after some time....
Click to expand...
Click to collapse
Ah,sorry I read it but while replying I forgot somehow.Yeah, then you need to soft brick it .It can be achieved by deleting some system files.So phone can got into bootloop.If your wife doesnt now how to get in to recovery then you should be ok.
Stock rooted phone needed for this, activate factory app. It will give a black window with device information over everything onscreen. Disable factory app to remove it later on.
By flashing the stock firmware in an attempt to make it all better gives the perfect opportunity to pretend the process buggered it.
Put some clear tape on the battery contacts ?