Related
**Resolved.
Hey all,
This could be a quick answer or hopefully something more. First off, I appreciate you reading this - and all XDA does. It's really nice to see development for the Android system.. so thanks for sure.
Deal is, is that I have a Galaxy Tab with build something like gjj7 - I didnt write it down before the flash.. ugh. Anyway, the post i was reading was installing Clockwork Mod, and recommended the forum below (on XDA)
http://forum.xda-developers.com/showthread.php?t=788108
I used the CF-Root-XX_XEU_JPY-v1.3-BusyBox-1.15.3 because the thread talked about using the JPy file if your ‘Build Number’ wasnt listed.
Odin3 looked great - no errors, all green. Tab did not reboot itself though, just hung. I rebooted, and now it doesn't look to start. If i keep hammering away though, it will show the Galaxy Tab intro screen, but then stop again.
I've seen the battery logo come up a few times too - looked grey - though it was a full charge before the flash.
I did check a Google search and went through all the posts I could on XDA, but just didn't see what I'm looking for. Is it indeed bricked, or because it 'kinda works sometimes not really" is it gonna be ok?
THanks for any replies,
** Edit - I put it in the box to put it away for a while - and when I opened it - the Tab turned on with the Android dude holding a sign. Anyone know why thiswould have turned on after being in the box for a while? I have not tested to see if the computer recognized it - but would like to know if you have a stock Galaxy Tab firmware i can reload.
Hey thanks again for any help -
-Kenny
Hi, I'm no expert, but what I think you may have done is load a kernel only, and you'll need to load a ROM on top in order to get the Tab working again.
I say that because I loaded a .tar file onto my Tab and it hung on the Samsung Galaxy Tab screen. Only when I loaded the JJ4 'full flash' (as I saw it referred to) was I successful in getting my Tab back online. The JJ4 has three .tar files included, one for each slot (Modem, PDA, and CSC).
It's pure guesswork on my part, I am still very new at this, but that might be your issue.
In your shoes I would look for threads about combining kernels and ROMs...?
Hope this helps. And I hope someone will correct me if I'm completely off-track.
k3nnynapalm said:
** Edit - I put it in the box to put it away for a while - and when I opened it - the Tab turned on with the Android dude holding a sign. Anyone know why thiswould have turned on after being in the box for a while? I have not tested to see if the computer recognized it - but would like to know if you have a stock Galaxy Tab firmware i can reload.
Hey thanks again for any help -
-Kenny
Click to expand...
Click to collapse
I'm no expert and havn't done any ROMs for my Tab yet, but I am planning to and thus am reading heavily on the subject.
If I'm not mistaken, the "Android dude holding a sign" is an icon for download mode. This means, you havn't done any ROMs yet, just the kernel part. (Same as above reply)
I suggest that you look at this post ---> http://forum.xda-developers.com/showthread.php?t=932082
It's the one I'm planning to follow. Alterbridge86 has done an excellent job on this post. It has a downloadable step-by-step instruction, as well as the necessary links to files you will need. I suggest you print the instructions so your PC can concentrate on the ROM part.
I hope this helps, and if it does, please click on the thanks below..
Treb71, and SelfP - thank you for the replies guys, I really appreciate that. I finally got a chance to sit down with it again, and recharged it.
I got it into that download mode (power and both volume buttons - seems different everywhere i look, but it worked) and have it being recognized as a Samsung USB Composite Device in device manager. Good to see it can still be found eh?
When you mention Kernal only, - that sounds familiar. What is the difference behind this and ROM? Just the ROM is more of the O/S it uses? Is there a benefit to loading a Kernal thats not the default one that I missed? :S
I'm going to load up those links - that puts me on a great start. I don't normally feel like a total n00b around technology (I'm sure most people on XDA know their stuff) but this experience has humbled me hah.
THanks for the replies!
Hot dog -
It worked.
Basically, reading the PDF he gives here -
http://forum.xda-developers.com/attachment.php?attachmentid=578831&d=1303832984
The first 7 pages talk about backing up, i didn't need to worry about that part and went straight to the Odin3 flash.
Here it hung for a bit. Didnt skip past the "setupconnection" after hitting start (after loading the files of course - as stated) but then i realized the dude holding the sign image I was looking at was not the same as the "Download Mode" sign. The one I was referring to was holding up a sign in the top right corner. Didn't think of 2 versions of it come to think of it.
Anyway, rebooting the tab, reloading the files in Odin, and making sure I was indeed in Download mode - went through.
It was in Netherlands though hahah. Upon boot up I just needed to change some Language settings.
We're good!
I'll continue on with the flash tomorrow (it's late here now) and let you know how the custom firmware is - I figure why not, it's all pretty smooth so far.
You've both been a help, if I could hit thanks a couple more times on your posts you know I would. Let me know if you decide to flash, and if you have any questions or thoughts based on my experiences, and I'll do what I can.
Thanks again XDA - bad ass thread you got going on here the more I learn about it.
-Kenny
I have done hours of researching and this isn't my first time i bricked a phone so I kind off have some experince fixing the phone but this seems harder than before.
I first tired to flash a kernel through odin on my captivate because i wanted to try out cyanogen mod but somehow the kernel had failed on me. When i tried to restart my phone, I got the phone---!---pc logo.
So i did some research on how to get the phone out of the soft brick. First thing I did was trying to get into recovery mode with the 3 buttons, but didnt work out. After that I tried to get into download mode and it worked. My first thought was too use odin and reflash, and that is what i did. Now the problem is, I had put the correct pit file and stock rom, because I had reflashed using these two same files before, but the thing is, it gets stuck on "set partition". So I did everything from, trying on different computers to changing usb cables to using different versions of odin and finally to taking out the sim card and sd card and taking out and placing the phones battery back in. And i had everything checked too so that wasn't the problem. The following were checked: Auto Reboot, Check Re-Partition and F.Reset Time.
If anyone knows the solution can you please help me out, thank you in advance!
When you check repartition, you need to load a pit file in the pit slot/tab for Odin. You have two options.
1) Flash froyo stock(kb2), if you don't want/need Gingerbread Bootloaders. The Heimdall package from Adam Outler is an easy 1 click solution.
2) Flash KF1 if you need GB bootloaders. This will also fix ant previous 3 button combo problem you may have. Use the package with a pit file and bootloaders.
It also sounds like you may need ajig to get into download mode, but if you follow the Captivate sig link below, you should be able to find everything you need to get going.
Thank you !
Thanks a lot mrhaley30705 ! I have gone through of some guides and done more research about these two, and I was thinking of flashing kb2 on to my phone but I'm really worried if it might brick my phone, because the captivate I have is the rogers one not the ATT&T one.
I just had a few questions like, before I do the Heimdall One-Click, is it required to install the Zadig file ? because it had came up before I opened up the Heimdall One Click program. I think i had used the Heimdall One-Click before (the video that is posted on youtube) by outleradam, but the thing was, it wasn't recognizing my phone. So I'm guessing it has something to do with Zadig file, because I made sure I ran it as Administrator also so I'm kinda lost.
My other question was, the consequences, if this program would not work for me, would it hard brick my phone? I really want to make sure I go ahead with it.
And my last question is, if I were to go ahead with this, it said on the forum I would have to reset my APN settings, so would that be applying another software to the phone or can i configure that manual ?
And Thanks again for all your help !
If you want the Canadian firmware, search for TRusselo's stock threads. He has a full set of Canadian firmware.
Anytime you flash bootloaders there is a chance of hard bricking your phone, either from an interruption in communication between your phone and computer (think power outage or bad cable) or accidentally mismatching bootloaders (think the old 3 button fix on top of GB bootloaders). Just follow all of the precautions you can when flashing bootloaders.
APN editing is done manually.
Oh alright I got how put the APN information, thank you.
And oh okay, that makes more senses.
And for the Canadian firmwares, that's what I pretty much did with Odin, I took his stock firmware and tried to flash it with Odin but wasn't passing the "set partition" part like I mentioned before. I followed his instructions too. So, that's why I'm a bit confused now, because I'm guessing if Odin doesn't work then I would have to use the Kb2 link that is posted on your Sig. Do you have any suggestions maybe ?
The canadian version of the captivate will flash the US verson, it just changes your boot screen and kernel splash to an att one. I would flash the KB2, then if you absolutley had to have the canadian version, flash it.
Thank you !
Thanks a lot once again ! and I will give it a try and let you know how it goes !
Maybe try NOT checking re-partition. This sometimes can cause a problem, in fact most tutorials i have seen always say DO NOT check re-partition. It's worth a try
Hi everyone,
I have in the past switched roms on my Galaxy S before, therefore the issue of bricking my phone is something that doesn't intimidate me too much. However, this time i'm really stumped, and I turn to the gurus here at the forums, hoping a solution can be found.
I had just gotten my phone back from getting its screen repaired (which makes this especially irritating), and my carriers had flashed my phone back to their stock version of android, meaning gingerbread with a lot of bloatware. I decided straight away that I wanted to root my phone today, although I was away from my PC. I had my laptop with me (Macbook Air), but I had never done any flashing from it before, not to mention ever using Heimdall before (I had always flashed with Odin). I downloaded everything, and then I made my first mistake: I flashed a speed mod kernel (I believe it was a froyo kernel), and after reboot my phone wouldn't go past the splash screen. I could still get into recovery and download mode. Then I decided to try playing it safe, and I downloaded stock firmware packages for Heimdall fro the forums here. I tried flashing JVS on my phone, going exactly by the instructions written in that same thread that I found the packages, but the flash didn't succeed. Instead, I got an error message saying the PIT file didn't reach the end of the transfer (or something like that...) and the phone rebooted. After that attempt, the phone went black. Nothing works anymore except for download mode. Now I thought that as long as download mode works, I'll be ok, so I tried flashing different packages through Heimdall, and eventually when I got home I tried using Odin on my PC. The problem is, my PC doesn't recognize my phone anymore (even though the drivers are installed and I never had an issue with that before), so I'm pretty much stuck with a brick for now.
I really don't want to go back to my carrier again, and hope to get my phone back in working order without paying too much. I still think there's hope as long as download mode works.
Does anybody have any suggestions what I might be able to do? Since my PC doesn't recognize my phone (and therefore Odin doesn't either), the only semi-working option left is using Heimdall somehow, but as to how to use it, I'm in the dark.
I would really appreciate any help you guys can give me. Thanks a lot!
Aaron
first try reinstalling the drivers and try again. if you can get download mode, should be repaired.
Thank you very much!!!
I knew that download mode was a good sign, but I started freaking out as soon as Odin wouldn't recognize my phone, since it never has had that problem. Reinstalling the drivers did the trick, and flashing worked.
Sometimes the simplest solution is the best. Again, thanks a lot!
commandozzz said:
Thank you very much!!!
I knew that download mode was a good sign, but I started freaking out as soon as Odin wouldn't recognize my phone, since it never has had that problem. Reinstalling the drivers did the trick, and flashing worked.
Sometimes the simplest solution is the best. Again, thanks a lot!
Click to expand...
Click to collapse
We are here to help.
Hey guys,
In a bit of a pickle at the moment. I grabbed an S1 off a friend to try and teach myself about rooting and flashing custom ROMs and such using Odin. With the final intent getting it to run ICS. Not a very hard challenge, but evidently it is for me.
I'll explain what I did, and if you can help without investing too much of your time I would be very grateful.
When I got it, it was running 2.3.3, all the tutorials I read told me to update it to 2.3.6 before doing anything more. I managed to root the phone easy enough, no issues there. But when I tried to put 2.3.6 on via Mobile Odin, (which I used to flash my S2 to ICS, long story) it had seemed to freeze on 'flashing flash kernel' for a good 15 or so minutes.
Being the daft monkey that I am, I exited the program...by removing the battery (don't judge me please). When I went to turn it on, it wouldn't load past the "Samsung Galaxy S" screen.
It goes into Download mode fine, and I've tried to flash an abundance of different Gingerbread ROMs onto the phone and Odin has just been getting stuck on the "setup connection" every time I've tried to flash.
I have tried using different USB ports which is readily suggested by most people and seems to work, using my laptop instead, different cords as well. No luck. Nothing happens when I press volume UP + home + lock like it used to, so I can't even factory reset or anything =\
I did find somewhere that suggested adding a PIT file to Odin and selecting repartition but every one yells at each other when 'repartition' gets mentioned, lol.
I hope this is in the right place, please bare with me if I used any wrong terminologies, I am relatively new to this.
Has anyone got some suggestions that may help me with my problem? =\
Thank you!
Taylor
sigh...here's my recovery kit, unzip, read .txt file, proceed
http://db.tt/MOGZx01S
Credits to nitr8 and chainfire
Thanks, sorry for being such a hassle...
Twinning92 said:
Thanks, sorry for being such a hassle...
Click to expand...
Click to collapse
No problems, was teasing ya! You will end up with root and custom recovery, if you then go to slim website and read and follow installation instructions you will then have lush ics
Hi!
This is my first post an I hope I did put it on the right place and I havent found any other post that really matches my problem.
Anyway, I was so happy for being able to bring back stock rom on a rooted SGS2 I9100 who didnt worked proper with its root. In this case, no USB-debugging were necessary.
After this mission I felt ready to try to downgrade the SGS Advance I9070 from stock Jelly Bean to Stock Ginger Bread by mainly following one of all those tutorials about how to do it. And I know its said - enable USB-debugging.
But as I were interupted by my wife just before I were going to proceed, I totally forgot it when I finally went back to my work of downgrading. As I were a bit stressed, I just connected the phone to Odin and slammed the PDA-button like I did with the SGS2. It went smooth all the way through Odin and the green PASS showed up. But when the phone were about to boot up it stuck at the Samsung-logo. Its in a bootloop. After a short time of wondering about what went wrong, it struck my head I forgot to enable USB-debugging. Amen!
So, I forgot debugging while running JB-stock to downgrade to GB-stock. The only thing I can reach now is download-mode except the bootloop Samsung start interface. Its probably occured because I forgot enable debugging, right? And does it mean this device is bricked for real or is there anyway to bring back life?
Best regards // emsoh
emsoh said:
Hi!
This is my first post an I hope I did put it on the right place and I havent found any other post that really matches my problem.
Anyway, I was so happy for being able to bring back stock rom on a rooted SGS2 I9100 who didnt worked proper with its root. In this case, no USB-debugging were necessary.
After this mission I felt ready to try to downgrade the SGS Advance I9070 from stock Jelly Bean to Stock Ginger Bread by mainly following one of all those tutorials about how to do it. And I know its said - enable USB-debugging.
But as I were interupted by my wife just before I were going to proceed, I totally forgot it when I finally went back to my work of downgrading. As I were a bit stressed, I just connected the phone to Odin and slammed the PDA-button like I did with the SGS2. It went smooth all the way through Odin and the green PASS showed up. But when the phone were about to boot up it stuck at the Samsung-logo. Its in a bootloop. After a short time of wondering about what went wrong, it struck my head I forgot to enable USB-debugging. Amen!
So, I forgot debugging while running JB-stock to downgrade to GB-stock. The only thing I can reach now is download-mode except the bootloop Samsung start interface. Its probably occured because I forgot enable debugging, right? And does it mean this device is bricked for real or is there anyway to bring back life?
Best regards // emsoh
Click to expand...
Click to collapse
LOL...:laugh: Wives will remain Wives!
The device is Soft Bricked and can be resurrected..did you follow this procedure: http://forum.xda-developers.com/showthread.php?t=2195673 ?
arneldna said:
LOL...:laugh: Wives will remain Wives!
The device is Soft Bricked and can be resurrected..did you follow this procedure: http://forum.xda-developers.com/showthread.php?t=2195673 ?
Click to expand...
Click to collapse
Haha.. Well, I had to drive her to the shop and that was enough to make me lose my patience of remembering important rules just because I had to go with other important rules. Like the gentleman I am. :fingers-crossed:
Thanx for reply. It makes me glad you do believe its possible to fix this issue. The link you showed is on of those I been looking at before I got started. But after a lot of comparing between several links from i-net, I decided to go with the procedure that the majority declared. For example, in this link its said "re-partition" must be ticked in. The other guides said not. Only "reboot" and "time-reset" to be ticked in.
The stock firmwire I downloaded were from some address connected to Samsung. It means there were only one file with all included just to insert in the PDA. Now, afterwards..I do understand it isent that hard to fill in 3 lines myself instead of one. But it seemed simplier with only one at that time. As I am a newbie about changing software in phones, I were ready to make mistakes but not this mistake and I really dont know what guides who are the best to go with.
Do you think it will make any difference if I go with your link and try again?
Remember, the phone were not rooted. Im really not sure, but I think I read somewhere that if debugging are not enabled on official kernel, theres no way back because cant reach debugging in any way. But I hope its not true.
Now, as far as I understand in my case...what I did was to erase the operation system I had (stock 4.1.2) and filled it up with (stock 2.3.6) but it only reached the gates and not the internal of the phone. It means there are no operating system at all?
Then why Odin shows PASS? And if no communication files can reach the phone, how is it possible that the counter now shows the phone has been rooted? Yes, I tried to root it today and Odin showed PASS again. And as the counter counts, it must mean the phone is not 100% blocked from communication even without debugging enabled?
But still the phone act as described earlier. Only Samsung-logo, bootloop and I can only go forward to download-mode.
:crying:
emsoh said:
Haha.. Well, I had to drive her to the shop and that was enough to make me lose my patience of remembering important rules just because I had to go with other important rules. Like the gentleman I am. :fingers-crossed:
Thanx for reply. It makes me glad you do believe its possible to fix this issue. The link you showed is on of those I been looking at before I got started. But after a lot of comparing between several links from i-net, I decided to go with the procedure that the majority declared. For example, in this link its said "re-partition" must be ticked in. The other guides said not. Only "reboot" and "time-reset" to be ticked in.
The stock firmwire I downloaded were from some address connected to Samsung. It means there were only one file with all included just to insert in the PDA. Now, afterwards..I do understand it isent that hard to fill in 3 lines myself instead of one. But it seemed simplier with only one at that time. As I am a newbie about changing software in phones, I were ready to make mistakes but not this mistake and I really dont know what guides who are the best to go with.
Do you think it will make any difference if I go with your link and try again?
Remember, the phone were not rooted. Im really not sure, but I think I read somewhere that if debugging are not enabled on official kernel, theres no way back because cant reach debugging in any way. But I hope its not true.
Now, as far as I understand in my case...what I did was to erase the operation system I had (stock 4.1.2) and filled it up with (stock 2.3.6) but it only reached the gates and not the internal of the phone. It means there are no operating system at all?
Then why Odin shows PASS? And if no communication files can reach the phone, how is it possible that the counter now shows the phone has been rooted? Yes, I tried to root it today and Odin showed PASS again. And as the counter counts, it must mean the phone is not 100% blocked from communication even without debugging enabled?
But still the phone act as described earlier. Only Samsung-logo, bootloop and I can only go forward to download-mode.
:crying:
Click to expand...
Click to collapse
Don't worry - as long as you have access to download mode you are fine :good:
I am not sure as I never downgraded to GB myself, but from my understanding of posts in here it is partitioning issue.
JB got different sizes or mount points (forgot exactly) of key partitions and that is what is wrong here - it cannot find some components to finish booting.
re-partition is the main thing here.
Get file from this guide.
Key point is:
9)Hit on PIT button and select the PIT file extracted from the downloaded package in first step above (GT-I9070_EUR_XX_8G.pit).
You should be able to use your 1-file-ROM and get it working, as long as you use .pit and tick re-partition.
Worst case scenario - flash JB again (no re-partition needed) and it will be working as before ;]
th3cr0w said:
Don't worry - as long as you have access to download mode you are fine :good:
I am not sure as I never downgraded to GB myself, but from my understanding of posts in here it is partitioning issue.
JB got different sizes or mount points (forgot exactly) of key partitions and that is what is wrong here - it cannot find some components to finish booting.
re-partition is the main thing here.
Get file from this guide.
Key point is:
9)Hit on PIT button and select the PIT file extracted from the downloaded package in first step above (GT-I9070_EUR_XX_8G.pit).
You should be able to use your 1-file-ROM and get it working, as long as you use .pit and tick re-partition.
Worst case scenario - flash JB again (no re-partition needed) and it will be working as before ;]
Click to expand...
Click to collapse
Ok, it makes me a bit more calm and Im starting to believe a bit, theres a way back for the phone to rise again. So you mean it might not be the failure of missed debugging, instead the critical main thing can be re-partiton?! It sounds very possible based on what you said.
The thing now is, ofcourse I would be satisfied if my first plan come true. But right now I really dont care what version it´ll be running, rooted or not. I only want it to act like a smartphone again n matter what´s installed. So I will go with your advise and test it one by one.
Thanx so far! To be continued..
SOLVED Forgot USB-debugging downgrading
I must admit I didnt really believed it wud work even I hoped it wud do. Before I started the new operation I gave it the chances 75% negative and 25% positive. But I was so wrong.
It really passed!!
Im so thankful for the support. To arneldna who made me reconsider this current version and tutorial for firmware downgrade. And to th3cr0w who explained and really pointed out the missing spot in my failure of action during the installing process.
The solution - Just to be sure, I followed the tutorial exactly. When it rebooted it showed up not to be my country region so I did it again with my nordic region all-in-one tar-file. This time just to be safe, I enabled usb-debugging and also unknown sources. Idk if it had any use but just in case of. And Voila..back to my region and everything seems to be as it was the first time I started up the phone when it was new last summer. After that I did a factory reset which I learned is useful to do.
As this was only one of my childrens phones, I actually got 3 more of the same to downgrade to work smooth again. But now I learned another lesson. I hope!
THANX A LOT to both of you! :good:
emsoh said:
I must admit I didnt really believed it wud work even I hoped it wud do. Before I started the new operation I gave it the chances 75% negative and 25% positive. But I was so wrong.
It really passed!!
Im so thankful for the support. To arneldna who made me reconsider this current version and tutorial for firmware downgrade. And to th3cr0w who explained and really pointed out the missing spot in my failure of action during the installing process.
The solution - Just to be sure, I followed the tutorial exactly. When it rebooted it showed up not to be my country region so I did it again with my nordic region all-in-one tar-file. This time just to be safe, I enabled usb-debugging and also unknown sources. Idk if it had any use but just in case of. And Voila..back to my region and everything seems to be as it was the first time I started up the phone when it was new last summer. After that I did a factory reset which I learned is useful to do.
As this was only one of my childrens phones, I actually got 3 more of the same to downgrade to work smooth again. But now I learned another lesson. I hope!
THANX A LOT to both of you! :good:
Click to expand...
Click to collapse
Glad to know you fixed it.. Appreciate your patience and efforts... :thumbup:
You don't care where I sent it from....!