Hello
I hope i have posted in the right section and someone can explain too me if this is right or wrong.
I just downloaded the 2.0 version of samsung kies software,when i plugged my phone in it said i could do a firmware upgrade for my phone.
So of course i did so,i first done the backup which was an option in the process.Then pressed ok and it started doing its thing.
Well i left it and came back too see a green android guy on the phone and a message on laptop saying the update had failed and i need too recover the fail by going into emergency firmware recovery mode.
I did this(pressed yes) and it started doing its thing again and rebooted the phone,after it had done it said too disconnect and reconnect my usb cable which i did and the phone was back running again.
The question i have is what basically just happened?
I presume it was a fail on the firmware update since thats what it told me but on checking my stats it had done what it said it was going too and thats upgrade from CSC: JP5 to CSC: JP6.
So it said it failed but on the samsung kies software it now says the csc JP6 and i cant update any firther.
Im sorry i should maybe of checked the code better too be honest i didnt check the full version upgrade, i just thought ok firmware upgrade yup ill do that and flicked through the yes options til the upgrade started.
Thanks for any replies.I have a untouched samsung galaxy S by the way,i not done anything too it except installed apps and games.So no roms,no lag fix,no hacks at all.
Its been a coupleof days now since my post so hope its ok too comment in it again so maybe i can get some help.
Im not sure if my first post explained itself enough so if anyone has any questions i will be happy too answer them.I dont know if my phone will be affected long term but the fail or not.
Csc..what is this why had the software felt it needed too be changed from 5 to 6 ?
the fact it said it failed yet on checking i cannot update again and it has in fact changed from 5 to 6 as it said it would.All my added shortcuts on home screens went but the files stayed.
csc....has anyone also got the changed firmware like i have and gone through the failure too get it.
Im trying too add my own questions in the hope someone has some answers since i see many questions get answered in this section within no time,but mine seems too of stumped some.
thanks for replies guys it will settle my mind and i will of course try too find my own answers and if all else fails i will contact samsung and ask them what went wrong.
Hi,
I installed Kies today and connected my girlfriends cellphone, a Samsung Champ Duos (don't know if it's a phone only for the Philippino market)... Same here, started up first time and Kies prompted me to update the phone's firmware. I followed the steps, something went wrong and I was told to perform an emergency recovery.
I tried, but after 63% an error message appear telling me that something went wrong and "if the problem persists please contact support centre".
I've tried the recovery process maybe 20 times now and same every time. I have already sent an email to the support, but hoping someone here knows how to fix this in the meantime.
Thanks in advance!
Not sure Kies can be unreliable...
Have you tried another computer?
Try the recovery again but hold the usb cable in place, it may have a loose connection
Either way support should answer you shortly and they will sort it out, as it should be under warranty and kies messed it up. They will probably tell you to find your nearest service centre...
@Caz2k11 if you ever read this again and still haven't got your answer, it shouldn't have affected you that there was a problem installing in the first place.
CSC - there is a sticky on the the general section that describes most of this stuff but in brief i think its either country specific code or country service code, something like that. Really its only important if you have problems downloading things from the market, or reception/data related issues. Usually carrier related... Its worth checking you have the correct one when you update as it saves you from changing it later which results in a factory reset.
Ahh damn it...
Got a reply from their support this morning. They apologized and told me I have to send the phone to my nearest service centre. Great for me living in the province and I'll bet the closest service centre is located in Manila....
Does anyone know if the *original rom* is available somewhere on the internet?
Most of us do not use kies to update
You can fiind the latest original ROMs at samfirmware.com
jc
3d_jc said:
Most of us do not use kies to update
You can fiind the latest ROM ar samfirmware.com
jc
Click to expand...
Click to collapse
Hehe no ****
I'm running Andriod on my HTC Leo as well, but this is my girlsfriends phone, still warranty so I'll be a bit careful at the moment.
Have registered on the site mentioned above, not sure which file I'm going to use or anything, since I cannot start the phone to see the current firmware etc. The model no. is GT-E2652W and "SSN" is "E2652WGSMH", does that mean it's a E-series phone?
It means a few things ...
First of all, you are totaly at the wrong place since this forum section is for Samsung Galaxy S, and you Champ Duo , well, isn't a Galaxy S !
Second thing is that this forum, as well as samfirmware, deal mostly with Android phones, which your isn't, I believe. It does somehow look like, but isn't.
Sorry I can't help more
jc
3d_jc said:
It means a few things ...
First of all, you are totaly at the wrong place since this forum section is for Samsung Galaxy S, and you Champ Duo , well, isn't a Galaxy S !
Second thing is that this forum, as well as samfirmware, deal mostly with Android phones, which your isn't, I believe. It does somehow look like, but isn't.
Sorry I can't help more
jc
Click to expand...
Click to collapse
Yes, I'm awared of that. Found this thread when I Google-searched "samsung emergency recovery".
Sure, no arm done, it's just that non android phone have a different way to recover. I did a couple of googling too, but must admit I did not find a great deal of information either,
Sorry and best of luck for bringing your device back to happiness.
jc
Related
Ok here goes... This is my first thread post here but I am in serious need of help.
I have searched and searched the forums for a hopeful answer but I have found it difficult to find the answer I seek.
So here is the story:
Bought a GT second hand from Akihabara in Japan which was locked to NTT DoCoMo. I was using it as a WIFI only Tab and all was wonderful till my IT brain decided it could be better and I began to tinker.
I had been looking around for a way to make my Australian Virgin Mobile SIM to work on the tab and found a lot of good answers but nothing that would make it work.
I then had the brilliant idea to change the firmware with a European firmware so I could get all the features enabled from a fresh start. Which is where it all went wrong.
I first tried to flash the tab using Odin 1.7 with the P1000XXJK5 euro firmware from samfirmware.com
This failed and left my tab with the picture of a phone and a pc with a dotted line and in between them an exclamation point in a triangle.
After a lot of fiddling (I dont remember what I did but I managed to get rid of that screen had something to do with retrying the flash and it was very late last night at this point) I managed to try again but Odin just kept failing on running the updated firmware.
I then decided that it would be a good idea to run the Rotohammer firmware by following the instructions on this thread:
http://forum.xda-developers.com/showthread.php?t=895827&highlight=sc-01c
This is where I once again received errors from Odin and now my tab is somewhat bricked.
I tried reflashing but same errors every time. (I currently dont have the errors from Odin but I will update my post when I get home)
I can still get to the downloading screen (Yellow triangle with the Android digging) so I am hopeful all is not lost.
So now you have heard my sob story I will ask two questions....
1. Has anyone actually successfully flashed a Japanese model Tab?
2. My only thought/hope at the moment can anyone direct me to an original NTT DoCoMo firmware so I can at least go back to having WIFI only Tab?
Thanks in advance if you can help
Alex
Yes , i suggest you to wait until you get a right firmware for it !
That would probably work if the partitions are a match !
What is this model called btw ?
"NTT DoCoMo Japanese Tab" or there is any model ? such as M180 for korean , P1000 , P100 Sprint , I800 Verizon , etc..
Br
Oz
I am searching the an original NTT DoCoMo firmware.
Electroboy said:
Yes , i suggest you to wait until you get a right firmware for it !
That would probably work if the partitions are a match !
What is this model called btw ?
"NTT DoCoMo Japanese Tab" or there is any model ? such as M180 for korean , P1000 , P100 Sprint , I800 Verizon , etc..
Br
Oz
Click to expand...
Click to collapse
Oz the model is SC-01C it has a build date of 2010/12
I was thinking considering I can get into the build/download screen maybe trying an emergency firmware recovery using Kies.
Hi,
I'm a fellow SC01 owner. You can get a backup of the stock firmware here: http://www.megaupload.com/?d=OJAK2UZF
Firmware code is SC01COMJK2
I believe there are newer firmwares (which I haven't installed as some of them contain a new bootloader that only allows for signed firmwares, same as the international units) that I have seen mentioned on various Japanese blogs. Let me know if you want me to try to hunt any down for you.
As for my SC01, I installed the custom kernel by koxudaxi and it's working great. Mind you, I've only changed to this kernel and apart from that am running the stock OS. I got his kernel here which can overclock to 1.4GHz: http://koxudaxi.sakura.ne.jp/
The kernel I installed via Heindall is zImage_ntt_2. It looks like he's built a newer version though, I might check that out. I think what you might want to do, is in download mode try to restore the above backup to your unit. Look up the Roto Backup thread to see how to do this. Hopefully since you can get download mode, all is not lost. I personally think it's quite crummy that there are different hardware versions like this which aren't interchangeable though >_<
I'm going to give the original firmware a go today at lunch time and I will let you know how I go. Thanks anyways for the link if all goes well I'll look at possibly trying the the koxudaxi kernel.
UPDATE: Well I'm not having luck getting the firmware to flash to my tab I keep getting "Failed to retrieve config Descriptor" when trying to flash. I will keep plugging away.
UPDATE: Still getting the same problems using heimdall to flash the tab. Any suggestions as to what I could do next?
Recovering a Docomo Tab
I'm currently running Overcome v1.1.3 ROM and richardtrip's V15 kernel on my SC-01C.
acont said:
UPDATE: Well I'm not having luck getting the firmware to flash to my tab I keep getting "Failed to retrieve config Descriptor" when trying to flash. I will keep plugging away.
Click to expand...
Click to collapse
You're getting this error from Heimdall, right? Have you tried Odin 1.7?
Here's how I recovered my Tab using Odin:
1. Following the instructions in http://forum.xda-developers.com/showthread.php?t=895827, specify the P1_add_hidden.pit in the PIT button and select Re-Partition.
2. Specify the stock Docomo ROM when pressing the PDA button.
3. Ignore the Phone and CSC buttons, as the stock ROM already contain these items.
You should be able to restore your Tab to stock settings using this procedure.
If this doesn't work, you might want to check if the USB connection to your PC is ok, and if everything necessary to run Odin is installed on your PC.
Bugger!
Well thanks for your help all of you but I think I have just made matters worse.
Last night I had success in flashing the original docomo firmware provided to me by zetsurin but I think I shouldn't have included the boot images.
Unfortunately I think it is completely bricked now it now wont turn on and when plugged into power (thinking that the battery had died) it just comes up with a white screen.
I can't boot into download mode and I can hold down the power button till I turn blue in the face... So as Bones would say "It's dead Jim"
Unless any of you have anything else I could try as a last ditch shot I might just have to ship it back to Japan and get them to fix it or maybe try Samsung here in Oz.
Serves me right
Thanks again.
acont said:
Last night I had success in flashing the original docomo firmware provided to me by zetsurin but I think I shouldn't have included the boot images.
Click to expand...
Click to collapse
What exactly happened?
The SC01COMJK2 firmware does not contain protected bootloaders, by the way.
acont said:
Unfortunately I think it is completely bricked now it now wont turn on and when plugged into power (thinking that the battery had died) it just comes up with a white screen.
Click to expand...
Click to collapse
I've heard about this happening when the battery runs out. Try connecting the Tab to your PC (not your AC adapter) and let it trickle-charge for an hour or so. If successful, you should see the download screen.
fury1sog unfortunately that didnt work
spoke to the samsung repairers here in Aus and they said they can take a look at it for me hopefully bring life back into my unit and then I will never touch it again
Any thoughts?
Hopefully this post is still being looked at but has anyone got any ideas as to what I could do before I fork out $374 to my tab repaired by Samsung Australia?
According to the repair guys its a faulty board (not an idiot that tried to flash it) and needs to be replaced. Not sure if this is worth my trouble considering I could buy a brand new tab for $599.
There is a positive out of this, the MB will be an Australian MB and I will have a working "Australian" tab instead of the Japanese version.
Considering the unfortunate tragedy in Japan I am not sure I should try and get my friend in Japan to fix it for me.
Thoughts anyone?
I know someone who can unlock it, I have mine unlocked by them.
I was afraid of flashing it myself so I paid to have it unlocked, cost was $20.
I think you better go for the MB replacement, it's cheaper.
For what it's worth, I went to reset my tab to factory using a rotohammer backup I made when I first bought it, and got stuck in a boot loop. So I then used ODIN. Still got a boot loop. Then I tried ODIN repartition... it hung for hours. Knowing the thing was likely bricked I pulled the plug and now I am in the situation as you: I have a crappy icon of a phone + an exclamation + computer image. Dead.
I think the best thing I can do for this junk is to toss it unceremoniously in the bin. Fortunately I also have an iPad which has resumed full-time service.
EDIT: Some signs of hope in here: http://forum.xda-developers.com/showthread.php?t=903257
Try "heimdall close-pc-screen" to see if your tab can get kicked back into the boot loop at least. Mine has failed a repartition, but I can still get it into the boot loop, which is a start. Will experiment over the weekend.
EDIT 2: Well my tab is back up and runing. I reflashed my original roto backup using ODIN with repartition on, then I went into recovery and did a factory restore. Back up like stock now. I think I'm going to sell it though, since it's been badly dis-owned by Samsung.
zetsurin said:
Hi,
I'm a fellow SC01 owner. You can get a backup of the stock firmware here: http://www.megaupload.com/?d=OJAK2UZF
Firmware code is SC01COMJK2
I believe there are newer firmwares (which I haven't installed as some of them contain a new bootloader that only allows for signed firmwares, same as the international units) that I have seen mentioned on various Japanese blogs. Let me know if you want me to try to hunt any down for you.
As for my SC01, I installed the custom kernel by koxudaxi and it's working great. Mind you, I've only changed to this kernel and apart from that am running the stock OS. I got his kernel here which can overclock to 1.4GHz: http://koxudaxi.sakura.ne.jp/
The kernel I installed via Heindall is zImage_ntt_2. It looks like he's built a newer version though, I might check that out. I think what you might want to do, is in download mode try to restore the above backup to your unit. Look up the Roto Backup thread to see how to do this. Hopefully since you can get download mode, all is not lost. I personally think it's quite crummy that there are different hardware versions like this which aren't interchangeable though >_<
Click to expand...
Click to collapse
hi zetsurin!
thanks for teaching me how to unlock the tab.
problem now is, im not able to successfully flash any rom. keeps saying write fail, using odin.
stuck at docomo logo when rebooted.
need help.
also used heimdall. starts downloading. but stuck almost at the end of the tab's progress bar.
argh...
me too ! samsung galaxy tab m180 Korean .... huhu
What ROM is best for a SC-01C?
Hi Guys
I picked up a 2nd hand SC-01C from Yahoo Auction, and am wondering what the best ROM to use with it is...
Looks like this guy has got an Overcome ROM on it OK, (http://chaki-ramone.blogspot.com/2011/06/galaxytabsc-01cgingerbreadromovercome.html), so I wonder if the latest version (http://forum.xda-developers.com/showthread.php?t=1205990) will work OK - anyone tried? (is the SC-01C a GSM-based model??)
I'm not going to use a SIM with it, so I'm not bothered about unlocking - but just want it rooted & want a good balance between speed & battery life. If you were going from scratch with an SC-01C, what would you do? Any suggestions greatfully received!
Thanks in advance?
PS - I'm an iPhone / iPad / Ideos 8150 / Notion Ink Adam owner, all jailbroken / rooted. So I'm not scared about rooting per-se, just worried about trying something that will not work because of anything docomo has done to the Tab!
Acont you could be coma bricked try pluginging it into THE MAINS for at least 4 hours if nothing come up your hard bricked.
Sent from my GT-P1000 using XDA Premium App
zetsurin said:
For what it's worth, I went to reset my tab to factory using a rotohammer backup I made when I first bought it, and got stuck in a boot loop. So I then used ODIN. Still got a boot loop. Then I tried ODIN repartition... it hung for hours. Knowing the thing was likely bricked I pulled the plug and now I am in the situation as you: I have a crappy icon of a phone + an exclamation + computer image. Dead.
I think the best thing I can do for this junk is to toss it unceremoniously in the bin. Fortunately I also have an iPad which has resumed full-time service.
EDIT: Some signs of hope in here: http://forum.xda-developers.com/showthread.php?t=903257
Try "heimdall close-pc-screen" to see if your tab can get kicked back into the boot loop at least. Mine has failed a repartition, but I can still get it into the boot loop, which is a start. Will experiment over the weekend.
EDIT 2: Well my tab is back up and runing. I reflashed my original roto backup using ODIN with repartition on, then I went into recovery and did a factory restore. Back up like stock now. I think I'm going to sell it though, since it's been badly dis-owned by Samsung.
Click to expand...
Click to collapse
Can anyone pls help,, my galaxy tab 7inch gt-p1000r is stuck on phone+pc logo, can't go to download mode, can't go to recovery mode,, can't do anything,, pls someone help me,, I am desperate..
huylang280285 said:
me too ! samsung galaxy tab m180 Korean .... huhu
Click to expand...
Click to collapse
unbricking M180 is done long time ago
Here is a video for you
http://www.ort-jtag.com/blog/?e=15
udhtari said:
Can anyone pls help,, my galaxy tab 7inch gt-p1000r is stuck on phone+pc logo, can't go to download mode, can't go to recovery mode,, can't do anything,, pls someone help me,, I am desperate..
Click to expand...
Click to collapse
What about this P1000R , what is special or different ?
I know P1000L was for south american edition !
lemmy_0 said:
hi zetsurin!
thanks for teaching me how to unlock the tab.
problem now is, im not able to successfully flash any rom. keeps saying write fail, using odin.
stuck at docomo logo when rebooted.
need help.
Click to expand...
Click to collapse
Docomo solution is very soon !
That TAB need JTAGging thats the only way ..
I have the good and dead device in hand , we will release for ORT-JTAG probably this week ..
Best Regards
Oz.
So I was retarded and followed the instructions (or started to) on androidadvices dot com/how-to-update-samsung-galaxy-tab-to-stable-gingerbread-2-3-3-firmware
My Tablet will not boot past the T-Mobile logo.......... they are being assholes and telling me i need to deal with samsung ......... who told me it would be 6-8 weeks for a replacement........ is there ANYONE out there that can help me with just resetting it???
If you can get to the T_Mobile logo, you probably have a working bootloader and that mean you just need to flash the correct firmware for you device.
In short words, go to samfirmware.com and download the right firmware for your tablet model.
Once you have the firmware, flash them to your tablet with 'odin' (flash software, that you can also get in the mentioned website).
This should solve the problem.
If this works I will love you.
So i am obviously more retarded than I thought pedrohfsd ........ I have an SGH-T849 and i cannot FIND the firmware on that site..... seriously? UGH
pm me i'll tell you what to do , with th stock firmware for Tmobile , i helped someone before 2days he had same tab with you ) and same problem
pedrohfsd said:
If you can get to the T_Mobile logo, you probably have a working bootloader and that mean you just need to flash the correct firmware for you device.
In short words, go to samfirmware.com and download the right firmware for your tablet model.
Once you have the firmware, flash them to your tablet with 'odin' (flash software, that you can also get in the mentioned website).
This should solve the problem.
Click to expand...
Click to collapse
You sir, are brilliant.
I wasn't able to locate the firmware on the samfirmware.com but I DID find it on XDA from another user. Put phone into download mode... waited till the little box in Odin turned yellow and loaded that badboy on there. After about 5 minutes it was back into the 2.2 OS again. The only problem that I had was with programs that had been installed before and loaded at boot (Just had to uninstall / reinstall) But for the most part its back to the way it was.
Thanks so much for your help!
You too Kosh, as I am sure you were going to walk me through exactly what I fumbled through on my own (I'm lucky I didn't blow anything up haha)
NO more attempts to get 2.3 on this badboy!
Thanks again all <3
I'm glad to hear that KalKainen, the first time i soft bricked my phone i got desperate too.
But after some weeks i saw the inumerous progressions that people develop in custom roms here in xda, and flashed the whole thing again =P.
pedrohfsd said:
I'm glad to hear that KalKainen, the first time i soft bricked my phone i got desperate too.
But after some weeks i saw the inumerous progressions that people develop in custom roms here in xda, and flashed the whole thing again =P.
Click to expand...
Click to collapse
Amen man..... desprate is about right.. haha... now if i could only figure out why i have to CONSTANTLY reboot it in order to restore network service (Even though I have 3g and full bars... no text messages send / come in and programs that use data error out... ) I would be happy. This has been happening for the last 4 months badly enough that I can have to reset it 10 times in a 2 hour period >.< I cant even put it into flight mode.... but after I TRY putting it into flight mode and then reboot it... it comes BACK in flight mode.... I hoped the reinstall of the firmware would fix it.. but alas..... still plagued. AT LEAST IT WORKS THOUGH!!
Connected my Samsung Galaxy Tab 8.9 to Kies yesterday and was informed there was a major firmware update (I live in Norway btw). Started the familiar process, all going well until 62% into the installation to the Tab. And there it froze... After a very long time I disconnected, tried the process recommended for emergency recovery. It stopped after 72% (or there around).
Now my device can't reboot, not even hard reset. All is lost and it has to be sent in for service Samsung says. When calling Support they said they were surprised Ice Cream Sandwich was released at this time for the device (sounded like they didn't know it was). Me too - I would have preferred to wait if I could have avoided this!!!
How do you know it was ICS.
Sent from my GT-P7310 using Tapatalk
I don't know it was (can't remember the version number displayed, stupid me!). When I called Samsung Support they said they were "surprised ICS was released now". I didn't claim it was when I called...
You are full of it.
Sent from my GT-P7310 using Tapatalk
Sorry? I'm just trying to report what happened to me so that it can be recorded if more experience the same. If I'm the only one with this problem then that is great (for the rest).
spirous said:
Sorry? I'm just trying to report what happened to me so that it can be recorded if more experience the same. If I'm the only one with this problem then that is great (for the rest).
Click to expand...
Click to collapse
You're the only one saying the Samsung have released ICS.
varsas said:
You're the only one saying the Samsung have released ICS.
Click to expand...
Click to collapse
See the question mark in the title of my post? I don't know or claim this was ICS, I'm trying to find out if it was and is only reporting what I experienced. I did so here assuming I get rational feedback and advice on it.
If it was ICS then others should also have it in Kies now, if nobody else has then it most likely wasn't. But I have seen no reports from others that they have got firmware upgrades to their 8.9 device on Kies now and ICS has been rumored to be around the corner. What did happen was that I got a firmware upgrade - no matter if that was ICS or not.
The idiotic thing was that I was so excited when I saw there was an upgrade on Kies that I ignored taking backup before proceeding. How stupid can you be...
Were you really not able to go recovery mode? When was the last time you used kies before you tried this? Maybe it was an older firmware?
The recovery mode also stopped, after 70-something percent. Might have been a few weeks since I checked Kies last, but not a very long time.
After the recovery mode also hanged, the device only displayed the firmware error page. When trying to hard reset (volume up & start button) I got an Android logo saying it was downloading (which it couldn't have been as it was not connected to anything).
Got it back from repair and it has Android 3.2 (2.6.36.3).
spirous said:
After the recovery mode also hanged, the device only displayed the firmware error page. When trying to hard reset (volume up & start button) I got an Android logo saying it was downloading (which it couldn't have been as it was not connected to anything).
Click to expand...
Click to collapse
Isn't that download mode....As in what you'd want to flash a rom with ODIN?
Did you try flashing the stock firmware back on it before you sent it in for repair?
I kinda messed up my i957 last week when playing around with it. I wasn't paying attention to the 3g vs LTE so it was my bad. Tried some stuff out and the tablet was whacky!
Wound up going to Samsung support page and hunted down original firmware and flashed with ODIN and all was well again.
Glad your back up and running
Morning all,
I apologise if this is in the wrong section but I am new to the forum and in a bit of pickle.
Around a week ago I rooted my lovely new note 3 to hopefully one day install some nice new ROM to get rid of the horrid touch wiz and actually see the full potential of the phones power. However, for some silly reason while I was using titanium backup on my phone I thought it would be a good idea to uninstall touch wiz thinking it would magically go back to basic android however it didn't. It is completely broken now, woops. The first issue I had was it would boot up and stick to the Samsung logo and just glow so I thought it would be an idea to install stock ROM via ODIN to try and revert it back to normal. Once I downloaded the correct stock ROM it was uploading through download mode however at the last minute it failed with a ext4 error which I think it means it's bricked? Not sure, completely new to this. I am now a bit stuck as I am not 100% sure what to do next.
The phone will only boot into either the firmware upgrade has encountered an issue, basically Odin mode or download mode. I have tried recovering it through kies however it cant connect to it. It knows it is there as it will start searching for it when it's connected however says it can't find it.
My phone is a note 3 SN SN-9005. The system status is custom, reactivation lock is off, Knox kernel lock 0x0, Knox warranty void 0x1 and write protection is enabled.
Obviously I would like to get the phone back to normal, I don't care if it has to be completely wiped and brought back to normal I would like it to just work. I've been an complete idiot and fiddled with something I'm not 100% sure on and I would like to not have a 600 quid paper weight hehe.
I will greatly appreciate any help or feedback.
You won't get the best feedback for a 9005 model here. We are the 900A version stuck on AT&T. Yes, however, we have plenty of intelligent people here. It's best to post your question here in the main Samsung Galaxy Note 3 thread next time:
http://forum.xda-developers.com/galaxy-note-3/help
Next, since you've voided your warranty as Knox being 0x1 - you're pretty much screwed for a refund or replacement based on PRESENT development from what I have read all over the AT&T threads. Understand this. Now, that being said, did you install a custom recovery or have your original recovery?
Here's my input/help. Forget about ODIN. You don't need that if all you did was remove your touch wiz.
Take out your battery, put it back in and hold VOLUME UP, POWER, and HOME together until you reach a recovery. Then if it's the stock recovery, wipe your cache partition, then wipe data/factory reset. Then reboot and you're good back to starting over. Check with a rooting application to see if you still have or not. If not, then obviously reroot
Also, don't ever do anything like that again without thinking what it could do, lol . Always tread carefully whenever you are new to something. Just my two cents for you. If you came here to root and learn it, don't be afraid to ask questions about applications and expanding your knowledge. No one will ignore you if you ask a simple question in the right manner/thread.
Good luck!
Thank you for the feedback. I have defiantly learnt from my mistake with this one. I have usually been lucky diving into things blindly hehe. I have tried to put it into recovery mode however it just vibrates like it should and then comes back up to firmware upgrade issue with the two computer screens an a attention sign in the middle. Is there anyway to get recovery mode back.
apdnote said:
Thank you for the feedback. I have defiantly learnt from my mistake with this one. I have usually been lucky diving into things blindly hehe. I have tried to put it into recovery mode however it just vibrates like it should and then comes back up to firmware upgrade issue with the two computer screens an a attention sign in the middle. Is there anyway to get recovery mode back.
Click to expand...
Click to collapse
Wish you had come here when you deleted touchwiz only instead of playing with Odin. Looks like you messed it up even further and have to now use Odin to reinstall your firmware. I'm about to go to sleep, but do this.
1) Take out battery and put it back in. Then press and hold VOLUME DOWN + HOME + POWER at the same time until you reach DOWNLOAD MODE.
2) Follow the steps here and use your odin or latest odin (shouldn't matter):
http://www.androidrootz.com/2013/10/how-to-unrootunbrick-galaxy-note-3.html
Oh, and google is your friend. It's how I learned things over the years...READING, then tinkering....you're welcome .
I wish I did as well. I will try this when I get back from uni this evening and post back results.
Thank you again.
apdnote said:
I wish I did as well. I will try this when I get back from uni this evening and post back results.
Thank you again.
Click to expand...
Click to collapse
You're very welcome, bro.
opasha said:
You're very welcome, bro.
Click to expand...
Click to collapse
I used what you have said to do and downloaded the correct firmware however when I try and install it via odin in download mode I get a FAIL(SIZE!) message at the end. Its not an ext4 error anymore but im worried at what is going on now. I have tried searching it up on google however nothing has come up. Looks like ive completely broken it... ='(
apdnote said:
I used what you have said to do and downloaded the correct firmware however when I try and install it via odin in download mode I get a FAIL(SIZE!) message at the end. Its not an ext4 error anymore but im worried at what is going on now. I have tried searching it up on google however nothing has come up. Looks like ive completely broken it... ='(
Click to expand...
Click to collapse
You have the 9005 right? I think you have the wrong file to odin. What is the exact model number of your phone and where are you located in the world? (reason I ask is there are different regions to choose from)
agent929 said:
You have the 9005 right? I think you have the wrong file to odin. What is the exact model number of your phone and where are you located in the world? (reason I ask is there are different regions to choose from)
Click to expand...
Click to collapse
SSN: SM-N9005GSMH
S/N: RF1D96B6ELB
United Kingdom Vodafone.
Im sure I downloaded the 9005 for samsung in the uk but I wil try again from a different site that specficly says what country and code.
If not would you be able to post me a link to the exact one?
Many thanks
Thank you so much everyone for your input. I hunted out the correct EU snapdragon firmware and booted it on, emptied the cache and restored to factory settings and its finally running! Only took 2 days hehe but at least its working. Thanks again everyone
Good to hear!
apdnote said:
Thank you so much everyone for your input. I hunted out the correct EU snapdragon firmware and booted it on, emptied the cache and restored to factory settings and its finally running! Only took 2 days hehe but at least its working. Thanks again everyone
Click to expand...
Click to collapse
Your welcome, don't forget to hit the thanks button for anyone that helped you!
apdnote said:
Thank you so much everyone for your input. I hunted out the correct EU snapdragon firmware and booted it on, emptied the cache and restored to factory settings and its finally running! Only took 2 days hehe but at least its working. Thanks again everyone
Click to expand...
Click to collapse
Hi, I am using same SSN. Can you please confirm the working rom download URL? Appreciate your help.
Thank you.
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....!