I just did the regedit trick and downloaded the froyo update but when i go into the phone i just keep getting error messages about launcher not loading etc.
I have factory resent and cleaned cache but still wont work. I cant download the old updates through kies any more how do i get it back to how it was with the old software? I am stuck and freaking out lol
guess you have to flash an older FW like JM2 with Odin ... check out FAQ in this section (sticky).
I really stuffed it up now i somehow flashed a captivate rom onto it from atnt and now it wont even go past the white screen. I cant use the 3 buttons to get it into recovery mode or download mode. And the computer is not recognising the phone. Have i stuffed it for good?
try volume up + volume down + power
the AT&T / Tmobile version uses that combination
instead of Volume down + home + power
Go into recovery mode and factory wipe if you have issues such as services force quitting.
livefree2x said:
I really stuffed it up now i somehow flashed a captivate rom onto it from atnt and now it wont even go past the white screen. I cant use the 3 buttons to get it into recovery mode or download mode. And the computer is not recognising the phone. Have i stuffed it for good?
Click to expand...
Click to collapse
Captive rom onto Galaxy phone? Curious how did you do that as these two are two different phone. You are not the first one but reading from the posts from people who did the same mistake, I'd say you have bricked it. Sorry to be the bearer of the bad news
i have
I have tried all combinations of keys and it just keeps loading up with white att international phone and then that screen just flashes every few seconds and doesnt go any futher. It wont go into downloadin or recovery.
im thinking of doing the update
did you do anything eles besides the update to cause this
Look, the only possible way to brick the phone (that i know of) is to flash others phone rom(Captivate being the usual suspect) into Galaxy.
This changed the button combo to enter download mode in Galaxy (as Captivate has different combo for download mode) so it is not possible to enter the download mode and reflash. Therefore you are stuck and cant do nothing Im afraid
Just curious , why so many people flashing Samsung Captivate rom into their Galaxy?
Some other examples
http://forum.xda-developers.com/showthread.php?t=749546&highlight=captivate
http://forum.xda-developers.com/showthread.php?t=751712&highlight=captivate
http://forum.xda-developers.com/showthread.php?t=767420&highlight=bricked
ok with that said then will the JPC update work on the bell galaxy s GT-I9000M
Bobler420 said:
ok with that said then will the JPC update work on the bell galaxy s GT-I9000M
Click to expand...
Click to collapse
Since it is the same Galaxy S i9000, I'd say It'll work. But I could be wrong To be on the safe side, you could ask for other Bell Galaxy users' feedback. Dont know about Bell, but Romanian Orange users are getting their phone locked after the flash.
usualy when something wrong w/0 3 buttons
usualy when something wrong w/0 3 buttons the phone rebooting in recovery mode itself to reboot it in download mode install correct adb drivers and use command "adb reboot download"
decided
I have just decided i am going to take it to one of the local Samsung repair centres i explained it over the phone and they said they could fix it for $49.95 or they could try and push for warantee but i told them i would just pay it will take longer for them to apply for warantee get rejected and then i pay anyways.
I miss it already i had to go back to my nokia N95 which was from a few phones ago now lol
i think the benfiets can wait till the official release ryanza lagfix fix all the lag problems that i had how important is flash really use your computer
Please explain exactly where you got the rom from so we don't make a similar mistake.
I'd pay the 50 too instead of waiting weeks and weeks :\
I got
I got the original rom through samsung kies using the reg edit trick that was shown in one of the threads. After a factory reset and a cleared cache it loaded up but started coming up with all these pop ups that things wont load and need to be forced shut etc.
So i decided to just flash it back using Odin but at 12 at night and in a panicy state thinking i have stuffed my phone for good i clicked on a captivate rom without looking at the heading of the thread that a link took me to for the galaxy s.
But as i said before for 49.95 to get it fixed is easier then me trying all these other things and getting in more of a panic about doing worse things to it. I assume it will be easy for them to fix it. A friend said he had a nokia he bricked where USB wasnt connecting and the screen wouldnt come on etc and they just used a computer that does something and fixes it.
got
Just got the phone call they managed to fix my galaxy for $49 and getting it back tomorrow oh how i have missed it i had to go back to a old old phone the nokia 95 lol.
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.
I downloaded the Jedi Mind Trick JB 2 ROM and installed it via clocwork mod recovery .. That went fine but it took me a few days to realize I didnt have a working video camera anymore on my phone.. so I thought to flash a stock ROOTed rom instead...
Then I found this threat about an updated version of Jedi Mind Trick's ROM labled JB 3.. So I wiped as much as I could in recovery and chose to format all the options it gave me in recover , Format system , data , cache , emms(or something) .. and now when I boot the phone , it shows the first flash screen , and the samsung logo starts to shimmer then it reboots back to the splash screen and repeats this process everal times before just going black and sitting there..
So I've successfully bootlooped my phone doing this..
MY PROBLEM -- I don't know how to charge my phone or connect to it to install anything else..
Is this a serious problem? How can I charge my phone to continue troubleshooting it? It still has some battery to try some things but I don't know how to hook it up to transfer any other roms to it via USB cable and PC in it's current state..
I'm very computer savvy but I'm trying to learn this phone modding stuff and I realy hope I didn't brick my phone in this process.
Can someone please help me out here? I'll be on the forums religiously until I figure this out.
What should I start doing first??
Any help would be greatly appreciated!! Thanks!
still working at it
I think I'm at the point of having to use ODIN to flash a new rom since i cannot simply copy this rom to the sdcard to use clockwork to flash it .. Am I correct on this ?
For some reason this rom I found (should be stock rooted tmobile gSII rom) does not want to open from ODIN's PDA button cause its in .zip and not .tar or anything... I'm not sure how to flash this rom with ODIN ( I'm not even 100% sure this is how its supposed to go) Any suggestions ?
phew
UPDATE - So I managed to research enough to find out that there is no way to flash a CUSTOM rom with ODIN.. SO I had to download a stock (presumably rooted) t-mobile rom and flash THAT ...
Now I'm back up with a rooted rom and will begin re-installing clockwork and then my custom deodexed rooted rom afterward.
Thanks for all who almost kinda tried to care to reply in this past 2 hours =) -- As previously mentioned.. I am a nerd.. I just suck at phone modding. Haha
So , looks like I'm in the clear now and don't need any more support on this particular topic yet.
zarklon said:
UPDATE - So I managed to research enough to find out that there is no way to flash a CUSTOM rom with ODIN.. SO I had to download a stock (presumably rooted) t-mobile rom and flash THAT ...
Now I'm back up with a rooted rom and will begin re-installing clockwork and then my custom deodexed rooted rom afterward.
Thanks for all who almost kinda tried to care to reply in this past 2 hours =) -- As previously mentioned.. I am a nerd.. I just suck at phone modding. Haha
So , looks like I'm in the clear now and don't need any more support on this particular topic yet.
Click to expand...
Click to collapse
Is this true? Through a recommendation (haven't done anything to my phone from rooting/flashing KANGSJUGGERNAUT2 years ago), I tried to flash CM10 and ended up with a bootloop myself. Tried flashing through ODIN but it kept crashing; does anyone know why?
Afterward, I tried to reflash it through CWM and from then on bootloops into a installation process that never completes.
For some reason my CWM turned super slow, freezes/hangs and reboots after a few minutes.
I gave the phone to a friend who does this stuff on the regular but he said my initial flash wasn't complete cause in download mode says I'm still running official? No clue.
I was told this via email/chat: "No luck, it won't even boot anymore, I think I'll just bring it back tmrw morn
10:43 PM
Sorry I'm at a wedding (yea I know random) I left my phone with coat check
OK I've narrowed down the reason but not the solution, you had an AOKP based ROM which fundamentally is based on CyanogenMod, but it wasn't correctly flashed as the phone still thought it has factory ROMs still running
11:10 PM
Clockworkmod(even though it was working before) wasn't accessing the partitions of the phone correctly so it wasn't properly wiping or flashing properly.
11:12 PM
So basically from the first time you flashed cwm it didn't flash properly then the next time you flashed using the new recovery it didn't flash anything it was supposed to do itself properly , so basically it was a chain of events in addition to a bad boot loader, that's why it never went to recovery or download mode correctly
11:13 PM
That's something that had to do with the way the phone was built meaning you may of had a bad bootloader from the very begin and are now feeling the synptoms
Basically, and I would hate to be the reason or partially the reason you have a dead phone, basically it was a matter of coincedencr that it happened as this could of happened at anytime, once you have a bad boot loader its pretty much down hill from there"
Any helpful insight as how I can rectify this? is my phone truly dead? Sorry about the quoted format, it was copied and pasted.
If I were in your boat, I'd use Odin and flash the stock 4.1.2 ROM.
Sent from my Nexus 7 using Tapatalk 4 Beta
tronmech said:
If I were in your boat, I'd use Odin and flash the stock 4.1.2 ROM.
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
The phone won't turn on, unable to go into recovery and download mode; plugged in usb (hear connection beep but pressing power button plays disconnect button) to no avail. What can I do to unbrick?
Stock 4.1.2? Possible over a hardbricked T989 with old 2.3.6?
JahJahLoO said:
The phone won't turn on, unable to go into recovery and download mode; plugged in usb (hear connection beep but pressing power button plays disconnect button) to no avail. What can I do to unbrick?
Stock 4.1.2? Possible over a hardbricked T989 with old 2.3.6?
Click to expand...
Click to collapse
sorry but i have to assume that you are not doing the 3 button recovery or download mode right.
Pull battery, put battery back in, hold power button & Vol +/- untill you see SAMSUNG on the screen ---> let go off power button(keep holding
Vol +/- button) .....u will see recovery. (assuming you did flash cwm before).
Let me know.
hit thanks.
sam.balia1012 said:
sorry but i have to assume that you are not doing the 3 button recovery or download mode right.
Pull battery, put battery back in, hold power button & Vol +/- untill you see SAMSUNG on the screen ---> let go off power button(keep holding
Vol +/- button) .....u will see recovery. (assuming you did flash cwm before).
Let me know.
hit thanks.
Click to expand...
Click to collapse
I believe I am doing it correct, I have been entering recovery and download mode many times, right before I soft bricked it.
And sorry, no, I've tried many times, many methods and my phone is confirmed as entirely hard bricked.
SUPAR SAD, but thank you!
dont give up
JahJahLoO said:
I believe I am doing it correct, I have been entering recovery and download mode many times, right before I soft bricked it.
And sorry, no, I've tried many times, many methods and my phone is confirmed as entirely hard bricked.
SUPAR SAD, but thank you!
Click to expand...
Click to collapse
you can try using adb and put the phone in dl mode.
sometimes its as easy as pull battery and wait awhile (20 min or more) and try again.
if you've exhausted all possibilities, you can use a jig to force a dl mode.
let me know
sam.balia1012 said:
you can try using adb and put the phone in dl mode.
sometimes its as easy as pull battery and wait awhile (20 min or more) and try again.
if you've exhausted all possibilities, you can use a jig to force a dl mode.
let me know
Click to expand...
Click to collapse
I don't know what adb is, or how to use it; I have, however seen my friend RDP to my desktop and do something and used the term 'adb' in his attempt to code through the phone.
I've done that battery waiting period, for nearly an hour and still no result.
After doing some researching, I have found that many people have stated a USB JIG would not be applicable to a 'hard bricked' phone. I really wanted to try as it looked like the most, simple and inexpensive solution.
JahJahLoO said:
I don't know what adb is, or how to use it; I have, however seen my friend RDP to my desktop and do something and used the term 'adb' in his attempt to code through the phone.
I've done that battery waiting period, for nearly an hour and still no result.
After doing some researching, I have found that many people have stated a USB JIG would not be applicable to a 'hard bricked' phone. I really wanted to try as it looked like the most, simple and inexpensive solution.
Click to expand...
Click to collapse
If you know for a fact that you bricked your s2, maybe wrong rom or kernel that u flashed by accident then.....
contact these guys.... http://brickedmyphone.com/contact-me/
good like and click thanks if you agree.
sam.balia1012 said:
If you know for a fact that you bricked your s2, maybe wrong rom or kernel that u flashed by accident then.....
contact these guys.... http://brickedmyphone.com/contact-me/
good like and click thanks if you agree.
Click to expand...
Click to collapse
Lols, you're really fishing for them "Thanks"; you got it buddy. Very swift responses. :cyclops:
Anyway, I'm still searching the net for anymore possible solutions.
Thanks.
JahJahLoO said:
Lols, you're really fishing for them "Thanks"; you got it buddy. Very swift responses. :cyclops:
Anyway, I'm still searching the net for anymore possible solutions.
Thanks.
Click to expand...
Click to collapse
fishing for them ???????
what the hell does that even mean? it seems that brick did hit u in the head!!!
sam.balia1012 said:
fishing for them ???????
what the hell does that even mean? it seems that brick did hit u in the head!!!
Click to expand...
Click to collapse
It might as well have... :crying:
I've done my fair share of searching and I couldn't come up with much so I strongly believe I have a unique problem. I hope someone can point me in the right direction
Im have a rooted GS3 747 running Paranoid Android. A couple days ago the phone wouldn't charge. I tried different cables and batteries and after some testing with other GS3's I realized that my phone's charging port was broken. As a result I couldn't even connect my phone to the computer to unroot it with odin. I want to unroot so I can send in the phone for repair under warranty. So I downloaded mobile odin pro and proceeded to unroot my phone. I copied the original rogers rom to the external sd, followed the instructions and started the process. Everything looked like it was going fine until I got stuck on the samsung screen. Did some more research and learned that I had to do a factory data restart by booting into recovery mode. Did that. By now I'm feeling pretty good about all this. I followed the instructions all the way and I'm thinking that I'm gonna get a stock phone shortly. Wrong! The phone was still stuck on the samsung screen.
Now since I cant connect my phone to the PC cuz the charging port is broken I dont know what to do. I would have just flashed Clockwork Mod like I did when I first rooted and started all over but I cant.
If no one has a solution then Im just thinking of sending it in as is. Maybe they wont be able to see that the phone is rooted since they wont be able to connect it their PC without swapping out the motherboard to fix the problem.
I should add that I went to a repair store to try and fix it and they told me that the only way would be swap out your mobo.
machdown said:
I've done my fair share of searching and I couldn't come up with much so I strongly believe I have a unique problem. I hope someone can point me in the right direction
Im have a rooted GS3 747 running Paranoid Android. A couple days ago the phone wouldn't charge. I tried different cables and batteries and after some testing with other GS3's I realized that my phone's charging port was broken. As a result I couldn't even connect my phone to the computer to unroot it with odin. I want to unroot so I can send in the phone for repair under warranty. So I downloaded mobile odin pro and proceeded to unroot my phone. I copied the original rogers rom to the external sd, followed the instructions and started the process. Everything looked like it was going fine until I got stuck on the samsung screen. Did some more research and learned that I had to do a factory data restart by booting into recovery mode. Did that. By now I'm feeling pretty good about all this. I followed the instructions all the way and I'm thinking that I'm gonna get a stock phone shortly. Wrong! The phone was still stuck on the samsung screen.
Now since I cant connect my phone to the PC cuz the charging port is broken I dont know what to do. I would have just flashed Clockwork Mod like I did when I first rooted and started all over but I cant.
If no one has a solution then Im just thinking of sending it in as is. Maybe they wont be able to see that the phone is rooted since they wont be able to connect it their PC without swapping out the motherboard to fix the problem.
I should add that I went to a repair store to try and fix it and they told me that the only way would be swap out your mobo.
Click to expand...
Click to collapse
You will want to be sure that your flash counter says 0. This can be found by entering download mode (vol down, home, power) and you will see "custom binary count". that is how they will tell that you have rooted. Have you entered recovery and done a factory reset to get past the boot screen? If you can full wipe/ factory reset and get back into Android, I recommend you use "triangle away" app to clear your flash counter.
BCSC said:
You will want to be sure that your flash counter says 0. This can be found by entering download mode (vol down, home, power) and you will see "custom binary count". that is how they will tell that you have rooted. Have you entered recovery and done a factory reset to get past the boot screen? If you can full wipe/ factory reset and get back into Android, I recommend you use "triangle away" app to clear your flash counter.
Click to expand...
Click to collapse
I entered download mode and dont see flash counter anywhere. I got the warning screen were you have the option to restart or download.
Ya I entered recovery and did a factory reset but nothing. Really cant do anything with charging port broken.
I sent it in anyways for repairs. Hopefully they just replace it
I'm having the same problem with my Gs3 with CM10 4.2.2 running. Thought this would help.
Sent from my SPH-L710 using xda app-developers app
So I left my phone on the charger in the car because it was dying, came outside and it was stuck on the Galaxy Note II screen with the green light on. I unplugged the cord, the phone refused to come on so I did a battery pull. Upon powering it back on, I get this screen that looks like Poltergeist and phone does nothing. When in Poltergeist, I can't get the computer to see my phone, so that I can back it up before formatting. Volume up, menu, power doesn't get me into recovery mode. I can't get into safe mode either. ican however boot volume down, menu, power it into the mode where I can flash it, Odin will see it, but going straight to flashing means I lose everything.
Does anyone have an idea beforehand? I know I'm asking a lot, but these forums have gotten way over my head over the years. This is an isolated incident, so if you could even attach the file directly that I can attempt to flash vids Odin to fix my booting issue vs saying goto X thread because every thread seems to have it's own multiple files. I just wanna recover it so it'll come on, back up it and then I'll research on my own how to flash it completely. It's 6am my time and I've gotta be up by 1130am for work, so please reply for dummies as much as possible
Thank you ahead of time.
PS - phone is stock on 4.1.2 rooted using CF Auto Root and that's it.
Morning bump...no quick advice?
60 readings, no one comment? "Hey, flash XXXXX and see if the display drivers come back", etc? It'll boot into flash mode, looks normal and the compputer sees it. Safe mode or normal boot give me Poltergeist and the computer wont see it so that I can try to backup everything before flashing....that's a lot of boobies pics (just trying to get some sympathy here) to have deleted
79 views...for the love of god, someone throw me a bone here. I get it, these are old phones now, these forums are full of know-it-alls who can't be bothered (devs) and "search" nazis (me being one of them) as I should just figure it out on my own...but I'm not. I've got versions of ODIN, I've got CWM Recovery files, stock MC2 and NE2 ROM's, I even found myself a PIT file. NONE OF THEM ARE WORKING. No matter which ODIN I use, they all stick at PIT regardless of whether I have re-partition checked or not. I've tried flashing PIT, CWM recovery, stock recovery, CF Auto Root and/or stock 4.1.2 - 4.4 ROM's in just about any combination of one or two together using each version of ODIN. No bueno.
I've got a very nice and thick 24/28awg cord I'm using, I can boot into dowloader mode but can not go into safe, recovery or boot normally. I've watched brick recovery videos on YouTube, I've downloaded files from here on the forums and www.galaxynote2root.com using various downloading I have included a picture of.
Someone, somethg...
10 attempts later...
Holy crap you forget how nice the Note is when you're back on a Epic for two days while working 12hr days and going through 6 batteries each day...
m5james said:
Holy crap you forget how nice the Note is when you're back on a Epic for two days while working 12hr days and going through 6 batteries each day...
Click to expand...
Click to collapse
Did you ever get this figured out? I'm in the same boat with the L900 Sprint Note 2...
Solved it by getting a working logic board from eBay
I broke down and bought a Note 3 off Craigslist for $300 but I'd still like to fix the Note 2 to make it into my backup instead of pulling the Epic outta the box again.
ok so bottom line is, I was in the middle of flashing official rom when at about 25% it failed. Don't ask why! (i still had recovery at this point) so I went ahead and cleaned absolutely everything thinking i'll just try and reflash as before. Now with power lead out it won't switch on at all and when power is supplied it shows message "An error has occured while udating the device software." loops at approx 3 sec intervals cant do anything with it.
Ive tried everything I can think of all to no avail! yes its my own fault bla bla bla just wondering if i act have f***** it.
Thanks to anyone with any ideas
You probably going to get a better help at TAB S2 board this is for the tab S1.
If it is hard bricked there is JTAG methods that can help, just need to find one for your device, not easy though.
But all I can do is share my experience with something like this, in a more "cheap" way than JTAGs, dunno if it helps:
I never had a similar problem on the tab S. But in the past a galaxy player 5.0 of mine had a very similar problem (as far I remember the screen just powered the back light but without any letters or simbols)
in 2012, I bricked it trying to mount a swap partition (280mb RAM ftw) accidentally pointing the wrong partition, and got the entire internal storage corrupted.. everything.. system, bootloader, recovery etc
My player was turning on only connected to a USB or charger, like yours. in fact It was hard bricked
I was able to recover it using Linux (because it is the only system able to communicate with the bricked device I had)
The problem is that everything need to be very specific, for example I used a software made for the galaxy s1 to "revive" my player 5 (both have the same hardware) it just made the device be detected via ADB. So I needed to prepare a SD with the same size as the internal storage (in this case 8gb) using the Linux terminal to mount in the SD an exactly schematic of the internal memory using a dump of another device that a xda user shared, (the dump was empty only with the bootloader, recovery etc) but it still had 8gb decompressed. So after that I used ADB to push the SD card content to the internal memory. And it get back to life \○/
Well.. it took me 1 week with a guide!! On the trial and error method. But it worked.. not perfectly, I get bootloops every time I try to flash a rom via Odin, but recovery works, and I have the device working until today
Hi, I Greatly appreciate your reply and advice. Think tho that your solution is a bit beyond my know how I know a little about ADB etc but i would have difficulties in compiling necessary files to sideload. Also many tanks for the link din't realise. Thanks Pal!
Alpha1BA said:
ok so bottom line is, I was in the middle of flashing official rom when at about 25% it failed. Don't ask why! (i still had recovery at this point) so I went ahead and cleaned absolutely everything thinking i'll just try and reflash as before. Now with power lead out it won't switch on at all and when power is supplied it shows message "An error has occured while udating the device software." loops at approx 3 sec intervals cant do anything with it.
Ive tried everything I can think of all to no avail! yes its my own fault bla bla bla just wondering if i act have f***** it.
Thanks to anyone with any ideas
Click to expand...
Click to collapse
If you can get it in to download mode you can flash stock rom back on it.......refer to xda samsung tab s2 for more details on this........
thx for reply but it reboots approx every 3 seconds so I dont have enough time to do anything with it :/
Alpha1BA said:
thx for reply but it reboots approx every 3 seconds so I dont have enough time to do anything with it :/
Click to expand...
Click to collapse
Plug in changer and push power and volume up and down all together and you will see the battery charger icon then you can get it in to download mode from there.....
stinka318 said:
Plug in changer and push power and volume up and down all together and you will see the battery charger icon then you can get it in to download mode from there.....
Click to expand...
Click to collapse
Stinka ure a superstar (atm!) I did as you suggest to no avail but I noticed a slight increase in the time it took to start rebooting again. I do not know which buttons did this but some 20 later it lasted long enough for me to be able to flash twrp. Now i havent actually tried that as yet as i wanted to check with you first... I have the battery logo on screen, i tried recovery and it started as it should but then rebooted, now im unsure at this time whether the battery is almost dead or not so i got it on charge and have the grey battery with a white flash inside... is this what i want for now until its charged? if so i'll keep you informed thamnks more than u know if uve helped me fix this, the reason i was flashing was because when i received it (no warranty!!) the screen sometimes flickered and it would constaly end up rebboting after digging around re that im lead to believe it need a new battery and for the connecting wires to be resoldered. Anyways thanks again n as I say i'll keep this updated
Cheers
Tony
one of the probs i hab/have with this unit is that it takes approx a day to fully charge!!! when i received it the screen flickered on the odd occasion but it was rebooting much more frequently. It came with stock n not messed with previously (i new this prior to purchase so got it for right price thinking it only needed flashing, how wrong was I!!!) so I flashed and encountered the above mentioned problems! thanks to stinka I surprisingly managed to flash a recovery... now provided all goes to plan, which rom would one suggest for stability and generally hassle free and prusuming the aforementioned probs, rebooting etc are still there what could i try to stop that? other than a debloated stock I found Lineage an excellent rom but still the problems got so bad the unit became unusable and was lucky not to go out the window. Im thinking do i start with a replacement battery and check the wires etc or could this still be a software issue??
if i endevoured to do the hardware myself would I attempt it by removing screen or the base for access to battery/connector??
Thanks again
In the tab s1 the best way is removing the back cover, but for some reason tab s2 seen to be the screen... at least in this guide: https://www.ifixit.com/Guide/Samsung+Galaxy+Tab+S2+Battery+Replacement/56616
Look like alot more complex than the s1 :/
RoIlingThunder said:
In the tab s1 the best way is removing the back cover, but for some reason tab s2 seen to be the screen... at least in this guide: https://www.ifixit.com/Guide/Samsung+Galaxy+Tab+S2+Battery+Replacement/56616
Look like alot more complex than the s1 :/
Click to expand...
Click to collapse
Thanks for that!!!
Tony
does look somewhat OTT!!!
will i have to odin stock first then flash rom i want or will it go straight from first flash via twrp considering there is absolutely nothing on phone at mo apart from twrp.
Alpha1BA said:
if i endevoured to do the hardware myself would I attempt it by removing screen or the base for access to battery/connector??
Thanks again
Click to expand...
Click to collapse
My guess is your issue is lack of charge in the device. That's the reason for the flashing failure and the reboot loop with the firmware error.
Bang it on charge for a while then irrespective of what it's doing, whether it's looping or not, hold POWER + HOME + VOL DOWN until download mode appears.
Reflash the stock firmware with odin.
swapped battery and reflashed stock via odin. It has helped although the issues are all still there its just they happen less frequently which doesnt mean its any less frustrating.