[Q] phone rebooting after ROM upgrade with Kies - Galaxy S I9000 Themes and Apps

Hello,
I have a i9000 Samsung phone. I had v2.2 on it and updated to v2.3 from Kies. Everything went fine but after the reboot my phone is rebooting on its own after 1-10 minutes. No matter what or where I navigate on it, menus, apps, just left <-> right, it reboots between 1 and 10 minutes. If I leave it alone then it stays on and I can even answer calls.
Sometimes when it reboots the phone will keep rebooting for a random number of times, looping. Sometimes is freezing on the "S" logo and then reboots again.
After the Kies upgrade I tried several stock versions from this forum with no luck. I also did several factory defaults, formatted cache, repartition etc.
I have access to the download mode and the phone is stable in that condition, is not rebooting.
I am from Romania, on Orange RO.
What should I do ? I'm a standard user, I do not need advanced options, I was just trying to update my phone to 2.3 from within Kies.
Is there any way to downgrade it back to the original Orange RO firmware so I can take it into service ? I still have warranty on it. Or should I try with other versions ? Could this be a software issue ?
Can anyone guide me in a right direction ? What to do ?
Thanks.

jdaniel19 said:
Hello,
I have a i9000 Samsung phone. I had v2.2 on it and updated to v2.3 from Kies. Everything went fine but after the reboot my phone is rebooting on its own after 1-10 minutes. No matter what or where I navigate on it, menus, apps, just left <-> right, it reboots between 1 and 10 minutes. If I leave it alone then it stays on and I can even answer calls.
Sometimes when it reboots the phone will keep rebooting for a random number of times, looping. Sometimes is freezing on the "S" logo and then reboots again.
After the Kies upgrade I tried several stock versions from this forum with no luck. I also did several factory defaults, formatted cache, repartition etc.
I have access to the download mode and the phone is stable in that condition, is not rebooting.
I am from Romania, on Orange RO.
What should I do ? I'm a standard user, I do not need advanced options, I was just trying to update my phone to 2.3 from within Kies.
Is there any way to downgrade it back to the original Orange RO firmware so I can take it into service ? I still have warranty on it. Or should I try with other versions ? Could this be a software issue ?
Can anyone guide me in a right direction ? What to do ?
Thanks.
Click to expand...
Click to collapse
Sounds like a faulty phone. Flash your original firmware and take it to Samsung. You can find it on Sammobile or with Checckfus.

Try performing a factory data reset first to see if this helps then if not reflash with odin

try factory reset

Thank you all for the answers. As I said in my first post, I already tried a factory reset, several times. After and/or before every firmware installation I did a factory reset.
I used ODIN and flashed firmwares from this forum that had three files (PDA, CSC and PHONE). The ones I find from Orange RO have only the PDA file. Do I need also old versions CSC and PHONE files or am I good with only the PDA file ? Or maybe I'm a moron and I didn't find the right one. Can you please detail what exact firmware should I put on it to be able to take it to Samsung ?
Thanks.

Use 3 files rom + pit file and check the "repartition" when flashing. It will clean everything including the partition scheme. It looks like you updated with kies after u moved to ext3/4
my idea will help for sure if your phone isnt phisycally broken.

I found these that may help me to revert the phone to the original firmware:
http://forum.xda-developers.com/showthread.php?t=1015640
http://forum.xda-developers.com/showthread.php?t=844459&highlight=jp7
OK so now my phone has v2.3.5 on it. In order to go back to 2.2 from the thread above, all I need are the CSC, PDA and PHONE files, right ?
Like a normal "upgrade", well downgrade is this case. There is no special process for the downgrade ?
Many thanks.
edit : just to confirm, when I downgrade from 2.3.5 to 2.2.1 do I need to check "update boot-loader" ? yes/no ?

jdaniel19 said:
just to confirm, when I downgrade from 2.3.5 to 2.2.1 do I need to check "update boot-loader" ? yes/no ?
Click to expand...
Click to collapse
anyone, please ?

Related

[SOLVE] 4 issues remains after restoring to stock rom

Dear Experts,
Is there anybody that can help me to resolve these problems.
I just got my Note 2 3 weeks ago and last week I tried to use custom rom by Hypernote v0.4. While using it, some issues had arises. So, I thought that I should go back to stock hoping that the issues will dissappear. Unfortunately, after flashing stock rom via Odin and did a factory reset after that. Those issues remains, the issues are:-
1. Keyboard stop responding after a while.
2. Bluetooth not turning on.
3. USB to PC connection not detected. (Samsung USB driver installed on PC)
4. After screen auto shut down, cannot turn back on. Have to restart or reboot.
I have been searching high and low on the net on how to resolve it....
Hope something positive can be obtain here from the XDA experts.TQ in advance for any of your attention.:fingers-crossed:
Have you tried wiping everything after installing stock ?if not then try it.
nm8 said:
Have you tried wiping everything after installing stock ?if not then try it.
Click to expand...
Click to collapse
yup, did that. factory reset, wipe cache, wipe dalvik. still the same. thanks anyway for the respond.
I found out on HTC Desire thread they mention about "USB Brick" that cause the problems. I suspect it is the same thing is happening here but I can't follow the guide they gave for HTC device. Can any experts here convert it into Note 2 use.TQ.
Just for updated info.
I've manage to resolve the 1st issue of keyboard stop responding.
What I did was I flash back stock rom provided by dr.ketan link and together with pit file. Using Odin 307, I checked the repartition and nand erase. put the pit file on pit section and the tar file on pda section.
First boot stuck on samsung logo screen, reboot to recovery and factory reset.
Normal first boot procedure, keyboard working fine. but the other 3 issues still remain. still hunting for solution at the moment.
SOLVE
Thank to The Almighty God, finally I have got back my Note 2 on the track.
I upgrade my firmware with Stock 4.1.2 leaked by eybee. Flash with Odin 304 that come with it and repartition with the pit file that also come together with it.

[Q] GT-N7100 stuck when get into stand by.

Folks,
After install the image, Thunder Lite (http://forum.xda-developers.com/showthread.php?t=2415582) something went down on my Note 2, I re-installed the original image for international phone, that by the way is working perfecly in another note 2,
Every time that the I turn on the device its works well but when the screen turn off and the device stuck, and only pressing home and power button, to force the restart the device comes back.
In the beggining the the led was in red collor, after I install the original PIT file and the bootloader file, the led turned off but the device keeps with the same behavior. http://forum.xda-developers.com/showthread.php?t=1896696
I raise the time to turn off the screen, and the device keeps working until turn off the screen.
I am trying at least back to original installing the OTA image, but the problem didnt solve.
please I need to know hoe to solve this or at least how to start to solve this.
Best Regards
Robson Barros
robson-dasilva said:
Folks,
After install the image, Thunder Lite (http://forum.xda-developers.com/showthread.php?t=2415582) something went down on my Note 2, I re-installed the original image for international phone, that by the way is working perfecly in another note 2,
Every time that the I turn on the device its works well but when the screen turn off and the device stuck, and only pressing home and power button, to force the restart the device comes back.
In the beggining the the led was in red collor, after I install the original PIT file and the bootloader file, the led turned off but the device keeps with the same behavior. http://forum.xda-developers.com/showthread.php?t=1896696
I raise the time to turn off the screen, and the device keeps working until turn off the screen.
I am trying at least back to original installing the OTA image, but the problem didnt solve.
please I need to know hoe to solve this or at least how to start to solve this.
Best Regards
Robson Barros
Click to expand...
Click to collapse
Another thing, seems to me that the USB debugging is not working.
Using the Note2 Toolkit the cell phone is not detecting, even with usb debugging turned on.
Into download mode shows to me:
ODIN MODE
PRODUCT NAME: GT-N7100
CUSTOM BINARY DOWNLOAD: YES (6 COUNTS)
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
At first did u try to make a clean installation without user data?
If the problem persists you can flash a factory firmware: DOWNLOAD_N7100XXDLJ2_OXA_FACTORY. If you try this method don't forget to upgrade to a recent firmware. (protection against exynos exploit & sds).
Primokorn said:
At first did u try to make a clean installation without user data?
If the problem persists you can flash a factory firmware: DOWNLOAD_N7100XXDLJ2_OXA_FACTORY. If you try this method don't forget to upgrade to a recent firmware. (protection against exynos exploit & sds).
Click to expand...
Click to collapse
Thanks for you help,
I solved typing this command at dial pad.
*#7284# - Phone Util
change the configuration from modem to PDA, after that the phone didnt stuck anymore.
Best Regards
Primokorn said:
At first did u try to make a clean installation without user data?
If the problem persists you can flash a factory firmware: DOWNLOAD_N7100XXDLJ2_OXA_FACTORY. If you try this method don't forget to upgrade to a recent firmware. (protection against exynos exploit & sds).
Click to expand...
Click to collapse
I tried this image, but didnt work.
with and without teh pit file.
Anyway, I have installed the origianl firmware from my telecom comapny operator.
Best Regards
Robson Barros

[Q] Rebooting at "Samsung Galaxy Grand Duos GT-I9082"

Hi,
I am new here. the problem similar to which I mentioned has been discussed here already.
the history of the problem is as below:
I had disabled some android built in apps even including google play(by mistake), including some other system app- because I was trying to speed up my phone. I got this remedy (disabling the system apps) from some website. It gave me some problems such as I wasn't able to update or install any apps anymore.
due to this, I used kies to update my phone. This operation failed. Then I tried the emergency recovery. but now kies will not accept the model/serial combination.
having this, I used ODIN to flash a stock ROM. This operations failed at BcmCP.img. I tried several environments for flashing. (tried from 4 different PCs, windows 7 and windows 8, having fresh installation of windows etc. none of them succeed.
I was able to flash Philz recovery and able to enter the recovery mode, but it couldnt solve my issue.(even after wiping cache/dalvin with Philz.)
I tried different version of stock with different versions of ODIN.
finally, I extracted the stock rom in to individual images and converted them to tar.md5 and flashed them immediately. I flashed all images except bcmCP.img. still it didnt solve my issue, but after this even I couldnt enter the Recovery mode.
Later I tried flashing with Philz again. It flashes successfully, but didnt allow me to boot in to recovery. Now I am completely stuck as my phone keeps restarting at the model name.
Please help me to restore my phone.
sorry for the long post, but hope it will explain my problem.
starpluss said:
Hi,
I am new here. the problem similar to which I mentioned has been discussed here already.
the history of the problem is as below:
I had disabled some android built in apps even including google play(by mistake), including some other system app- because I was trying to speed up my phone. I got this remedy (disabling the system apps) from some website. It gave me some problems such as I wasn't able to update or install any apps anymore.
due to this, I used kies to update my phone. This operation failed. Then I tried the emergency recovery. but now kies will not accept the model/serial combination.
having this, I used ODIN to flash a stock ROM. This operations failed at BcmCP.img. I tried several environments for flashing. (tried from 4 different PCs, windows 7 and windows 8, having fresh installation of windows etc. none of them succeed.
I was able to flash Philz recovery and able to enter the recovery mode, but it couldnt solve my issue.(even after wiping cache/dalvin with Philz.)
I tried different version of stock with different versions of ODIN.
finally, I extracted the stock rom in to individual images and converted them to tar.md5 and flashed them immediately. I flashed all images except bcmCP.img. still it didnt solve my issue, but after this even I couldnt enter the Recovery mode.
Later I tried flashing with Philz again. It flashes successfully, but didnt allow me to boot in to recovery. Now I am completely stuck as my phone keeps restarting at the model name.
Please help me to restore my phone.
sorry for the long post, but hope it will explain my problem.
Click to expand...
Click to collapse
if u disable some system apps u must enable it..the best solution for that is go to a technician and let them see ur phone
Hi,
Thank you for your reply.
I approached the technical service of samsung. they advised me that the phone has been roote and thus the motherboard needs replacement and it will cost almost one third of the cost of the phone.
I dont think I have done any harm to the hardware.
could you please advise me if there is any other option than replacing the motherboard?
Many thanks..
starpluss said:
Hi,
Thank you for your reply.
I approached the technical service of samsung. they advised me that the phone has been roote and thus the motherboard needs replacement and it will cost almost one third of the cost of the phone.
I dont think I have done any harm to the hardware.
could you please advise me if there is any other option than replacing the motherboard?
Many thanks..
Click to expand...
Click to collapse
ahm try to wipe data/factory reset,wipe cache and dalvik cache.if bootloop happen again then its better to buy a new one because if u buy a motherboard for 1/3 of its price its not a good one in new ur sure that it will boot up
Rommel Espinosa said:
ahm try to wipe data/factory reset,wipe cache and dalvik cache.if bootloop happen again then its better to buy a new one because if u buy a motherboard for 1/3 of its price its not a good one in new ur sure that it will boot up
Click to expand...
Click to collapse
I cant enter the recovery mode. it restarts even before that stage.
If I remove and put the battery, it will be in the off state. When I plug the charger, it will automatically start and restart even before I can goto recovery mode.
last day I was able to boot to recovery using Philz. but now I cant. pressing and holding the volumeup+home buttons has no effect.
starpluss said:
I cant enter the recovery mode. it restarts even before that stage.
If I remove and put the battery, it will be in the off state. When I plug the charger, it will automatically start and restart even before I can goto recovery mode.
last day I was able to boot to recovery using Philz. but now I cant. pressing and holding the volumeup+home buttons has no effect.
Click to expand...
Click to collapse
Hi,
I found a solution to flash the stock ROM. I checked the model name on the motherboard and it is GT-9082i, while kies detects my phone as GT-9082 only. dont know why. When checked for the stock ROM for GT-I9082i, I found that it is a chinese model and all the stock ROM listed was CHU. the phone is locked to some chinese operator I think.
I need to change this stock ROM anyway or need to unlock the phone.
Could you please help me for that?
starpluss said:
I cant enter the recovery mode. it restarts even before that stage.
If I remove and put the battery, it will be in the off state. When I plug the charger, it will automatically start and restart even before I can goto recovery mode.
last day I was able to boot to recovery using Philz. but now I cant. pressing and holding the volumeup+home buttons has no effect.
Click to expand...
Click to collapse
hold power,vol up and home simultaniously
Rommel Espinosa said:
hold power,vol up and home simultaniously
Click to expand...
Click to collapse
Thank you. That will take me to recovery mode.
there is correction in my previous reply. the operator is not locked. I can use my operator SIM. since the version is Chines, most of the apps use chinese language.
I know that only due to the difference in "modem" it didnt accept any other stock ROMs. when I purchase the phone, the region of the phone was set to United Arab Emirates. (I have written down the OS details from the "About" menu )
can somebody help me to restore a ROM for my region itself?
I am sure that the phone will not accept the ROm for my region as it fails always at BcmCP.img (the modem).
Many Thanks.
starpluss said:
Thank you. That will take me to recovery mode.
there is correction in my previous reply. the operator is not locked. I can use my operator SIM. since the version is Chines, most of the apps use chinese language.
I know that only due to the difference in "modem" it didnt accept any other stock ROMs. when I purchase the phone, the region of the phone was set to United Arab Emirates. (I have written down the OS details from the "About" menu )
can somebody help me to restore a ROM for my region itself?
I am sure that the phone will not accept the ROm for my region as it fails always at BcmCP.img (the modem).
Many Thanks.
Click to expand...
Click to collapse
u may download the stock rom in for ur region mate
Rommel Espinosa said:
u may download the stock rom in for ur region mate
Click to expand...
Click to collapse
OK, Thank you. I will try it later. Now anyhow it is working and I changed the language to English. Hope my post is helpful for those who fail while they flash stock ROM.

Failed to mount /data and frozen after factory reset, HELP!

I have what's probably a unique situation, though I hope not. For background info, I bought two I747s, one white and one blue, each with issues, but I intended to put parts together to end up with one good one.
When I did a factory reset on the blue one via the recovery menu, it returned a bunch of errors along the lines of "failed to mount /data." Then when it rebooted it would hang on the Samsung logo. Back in recovery mode it returns more of the same errors just booting into recovery mode, and factory reset still returns more of the same errors and doesn't fix anything. I flashed 4.3 with Odin in an attempt to fix it, but I got the boards mixed up, and that one had 4.4 on it, not 4.1 like I thought. I'm pretty sure it's hard bricked now (that whole can't downgrade thing) because it's unresponsive to everything. Though my computer does recognize that it's plugged in, more on that later.
So I figured, fine, I screwed up, I'll just use the other board with 4.1 on it from the white phone. Except when I did a factory reset on that one, it did the exact same thing! Same errors, same problem stuck at the Samsung logo. Except this time I'm not flashing sh*t until I know exactly what I need to do to fix it. In another post where the guy had the same issue with 4.1.1, it was solved by flashing 4.3 with Odin. And another post where the guy had no idea what version he had, he just knew it was lower than 4.3, his problem was also solved by flashing 4.3, But since my last efforts failed miserably, I'm very reluctant to try it until I get some knowledgeable input. I don't remember exactly which version is on there, it's 4.1.something. I'd also prefer not to upgrade beyond 4.1 because I'd like to unlock it and from what I'm reading you can only do it for free if you're on 4.1. So I guess I need a link to an Odin flashable 4.1 package?
As for the poor blue phone that used to have 4.4.something, and was mistakenly flashed with 4.3, I've heard about JTAG but I don't quite understand it, and I'm not sure it would work in my case since a lot of what I'm reading says that bricking which occurs from downgrading is often unfixable. However, Windows recognizes that a device is plugged in when I attach it via USB. It shows up in the Device Manager as QHSUSB_DLOAD. I am currently researching more on this and the method of booting from an SD card, except I don't have an SD card reader at the moment.
Any assistance, advice, links, information, and plain ole encouragement are always welcome and appreciated.
For the phone running 4.1, flash any stock rom in Odin. After flashing, boot into recovery and perform a factory reset, then boot the phone and use the free method to sim unlock. The important thing is to have the stock 4.1.1 dialler in order to access the hidden menu options?
For home hard bricked phone, you will have to try the debrick image method. If it doesn't work, a jtag service should be able to force flash a rom to the phone.
Wow, that was like a crazy fast reply!
What if the phone is 4.1.2? Can I still flash 4.1.1? I'm on the hunt for a 4.1.1 stock rom now.
Yes, you can flash 4.1.1 from 4.1.2.
audit13 said:
Yes, you can flash 4.1.1 from 4.1.2.
Click to expand...
Click to collapse
Apparently not always. I downloaded and flashed 4.1.1 with Oden 3.07, it rebooted, showed the android image like it was updating, progress bar finished, and then it just went blank. Now both phones are in the same condition of being hard bricked and showing QHSUSB_DLOAD in the device manager.
This is strange. I have downgraded approximately 10 i747m phones from 4.1.2 to 4.1.1, unlocked using the free method, and re-flashed back to 4.1.2 after unlocking.
http://forum.xda-developers.com/showthread.php?t=2371897
What options did you check in Odin? Where did you get the 4.1.1 ROM? I ask because the stock ATT 4.1.1 rom was apparently removed from sammobile.com.
How did you confirm that the phone was running 4.1.2?
I checked only auto reboot in Odin.
I found this link sammobile.com/firmwares/database/SGH-I747/ in this thread http://forum.xda-developers.com/galaxy-s3-att/help/downgrade-att-running-stock-4-4-2-rom-t3170938 , 7th post
The download was going absurdly slow, so I googled the exact file name being downloaded which was, I747UCDLK3_I747ATTDLK3_ATT, and found a google drive link at https://drive.google.com/file/d/0B_UTWXKFnZoNVFdSVjJEZlMwZjA/edit which was the first result after searching for the file name if that link doesn't work. I'm downloading the slow one now to compare it to the one I got from google drive.
I'm unsure if the phone was 4.1.1 or 4.1.2, that's why I asked if it's possible to flash 4.1.1 on top of 4.1.2. I was only trying to do a factory reset originally and had no intentions of flashing anything. I just wanted to wipe out all the crap on it from the previous user so I had only glanced at the version out of curiosity to see if it was unlockable via the free method. I remember it was 4.1.something.
I have an SD card reader on order. Hopefully I'll be able to unbrick one of them.
Do you, or anyone else, have any idea why a simple factory reset would cause errors like I described and then hang on reboot? At that point both phones were 100% factory and I hadn't done anything to them except put a battery in them to power them on. I've done a factory reset on four other S3s and this didn't happen.
It is definitely possible to flash 4.1.1 over 4.1.2 because the bootloader could not be downgraded until the mjb version.
That's what I've been reading. So where did I go wrong? Any idea why a factory reset would screw up like that?
Did you confirm the bootloader before flashing?
audit13 said:
Did you confirm the bootloader before flashing?
Click to expand...
Click to collapse
No, because I had no intentions of flashing it when I tried to do a factory reset. Then after that went bad it wouldn't boot, and I don't know how to check the boatloader when a phone will only go into recovery mode.
Where did you see reference to 4.1? It's possible that the modem or baseband was 4.1 but the bootloader was 4.3.
Under about device and then Android version. The one where if you tap it a lot you get the jellybean android that pops up. It wasn't the baseband version because that's a much longer number with the model number in it.
That screen doesn't tell you the bootloader.
As I said, I didn't check for the bootloader version before I ran into trouble because I only wanted to do a factory reset and I didn't intend to flash anything. I wouldn't imagine that it would have a different bootloader than the OS version unless that can happen without any user intervention because the previous owner was only concerned with selfies and games. She certainly didn't modify anything.
I cant explain what happened. This has never happened to me after flashing about 10 phones.
I believe it has something to do with the errors that were produced while trying to do a factory reset. What bothers me is that both phones did the exact same thing. Normally I'd say it was something I did, except that I didn't do anything but put a battery in them, boot up, find lots of junk installed, and then attempt a factory reset. On the first phone, I rebooted into recovery and tried it from there. On the second phone I tried it from inside the OS. Same results on both. The phones ran fine before that.
Any advice on how to do the boot from an SD card, or how to do the JTAG thing? I've been reading a lot but the information jumps around a lot. I'm comfortable with soldering and have an IT background if that helps.
It's possible that the recovery was corrupt or the partitions were corrupt.
Whenever I factory reset a phone, I always boot into recovery to do that, not from within the ROM.
Sounds to me like you did nothing wrong.
Did the previous owner have the phone from the time it was new?
Edit: for the phone that you flashed with 4.1.1, Odin said "pass" in the status window and the it auto rebooted?
audit13 said:
Did the previous owner have the phone from the time it was new?
Edit: for the phone that you flashed with 4.1.1, Odin said "pass" in the status window and the it auto rebooted?
Click to expand...
Click to collapse
I don't know for sure if she had it from new. Yes, for both phones Odin said pass in the window and then it rebooted. I had walked away when Odin finished with the first phone. I came back and it was dead. The second one I watched and it showed the android with the wireframe in his guts and the progress bar which moved across, and then it just went blank.
There were error messages about the partitions when I did the factory reset IIRC. Perhaps the recovery or the partition was corrupted like you said. It's just odd that both had the exact same identical problem with the exact same results. That's why I think that it must have been something I did, except that I didn't DO anything other than initiate a factory reset.
I took an i747m and reflashed stock the Telus 4.4.2 ROM.
In download mode, you should see the green Android guy with the words "Downloading...Do not turn off target" and a blue progress bar moving from left to right.
I did not check reset in Odin. Once it finished flashing the ROM, I removed the USB cable, removed the battery, replaced the battery, and booted the phone. I the Android guy with the wire frame for a few seconds, the screen went blank, and the phone started up with the Samsung logo.
Since you were getting errors with mounting the different partitions, you may have needed to flash the PIT and PDA files but I can't really say for sure as I have never encountered this problem.
I normally verify everything before I use Odin because phones that I have been given to fix have had all sorts of weird configurations.
You'll have to try the debrick guide. of use a jtag service. You could also do what I did and that is to look for people with phones that have a damaged screen and buy they at a steep discount.

[Samsung] Galaxy Tab 3 SM-T210 / "Firmware upgrade encountered an issue"

Hello!
Few days ago i found my Samsung Tab 3, and decided to charge it and biit it up.
It got stuck on Samsung logo when i booted it.
So i did a factory reset using the recovery mode.
After i did that the device booted up. with lots of errors.
I was on the setup screen for my device and these errors appeard and said like core has stopped working and every like preinstalled app on my samsung device aswell (NAME has stopped working). So i was not able to fullfill the setup of my device.
I read about it online and a firmware upgrade could fix the problem ( Like the easiest way i read )
So i did some googling and downloaded Odin and a firmware. Followed a guide and did everything right. BUT the process faild like 8min into the flash.
And now my device is stuck on "download mode" but with the error "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I cant get the phone to turn off, nor get into recovery mode or anything else. I tried flash again but no luck.
I also tried another firmware i found. still same problem.
How do i fix this and how can i use my samsung tab 3 again.
WHen i bought it years ago i never really used it. So it's in "new shape" and has never really been used. And now i wanna give it to my little sister for some kids games to play at Xmas.
I hope we can solve this problem.
Thanks in advance
Regards
Timmie
Hyldran0 said:
Hello!
Few days ago i found my Samsung Tab 3, and decided to charge it and biit it up.
It got stuck on Samsung logo when i booted it.
So i did a factory reset using the recovery mode.
After i did that the device booted up. with lots of errors.
I was on the setup screen for my device and these errors appeard and said like core has stopped working and every like preinstalled app on my samsung device aswell (NAME has stopped working). So i was not able to fullfill the setup of my device.
I read about it online and a firmware upgrade could fix the problem ( Like the easiest way i read )
So i did some googling and downloaded Odin and a firmware. Followed a guide and did everything right. BUT the process faild like 8min into the flash.
And now my device is stuck on "download mode" but with the error "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I cant get the phone to turn off, nor get into recovery mode or anything else. I tried flash again but no luck.
I also tried another firmware i found. still same problem.
How do i fix this and how can i use my samsung tab 3 again.
WHen i bought it years ago i never really used it. So it's in "new shape" and has never really been used. And now i wanna give it to my little sister for some kids games to play at Xmas.
I hope we can solve this problem.
Thanks in advance
Regards
Timmie
Click to expand...
Click to collapse
That depends on various things, such as the Android version, kernel and change ID. Than also the Odin version you've used and/or the settings during the attempt of flashing. I found that using the wrong Odin version on a particular Android version, that may prevent the flash of being successfull. B.t.w, did you format both user and cache partition while trying to reset to factory default?
xdausernl said:
That depends on various things, such as the Android version, kernel and change ID. Than also the Odin version you've used and/or the settings during the attempt of flashing. I found that using the wrong Odin version on a particular Android version, that may prevent the flash of being successfull. B.t.w, did you format both user and cache partition while trying to reset to factory default?
Click to expand...
Click to collapse
Yeah, I've found out what Odin version to use that worked for others. I've downloaded lots of different firmwares and such and tried. ALL fails.
When i did a factory reset i also cleared cash and user.
Now i cant even turn off the damn thing. If i charge it up and start, it just goes directly to the screen where it says "Firmware upgrade encountered an issue" and if i try to turn it off, it just reboots and goes back. And i cant even return to factory reset page.
I think that my Micro-USB cable might not work for this, or is that a thing? Do i need a good cable from PC to Phone for this? Or does any cable work?
I just want this tab to work. been trying for weeks.
Thanks for your reply. I hope we can sort this out.
Hyldran0 said:
Yeah, I've found out what Odin version to use that worked for others. I've downloaded lots of different firmwares and such and tried. ALL fails.
When i did a factory reset i also cleared cash and user.
Now i cant even turn off the damn thing. If i charge it up and start, it just goes directly to the screen where it says "Firmware upgrade encountered an issue" and if i try to turn it off, it just reboots and goes back. And i cant even return to factory reset page.
I think that my Micro-USB cable might not work for this, or is that a thing? Do i need a good cable from PC to Phone for this? Or does any cable work?
I just want this tab to work. been trying for weeks.
Thanks for your reply. I hope we can sort this out.
Click to expand...
Click to collapse
It is quite easy to turn the device off, for that to happen you have to press and hold the on/off button. You'll see that the device will shutdown and try to reboot and then finally shuts down again and stay off, then release the on/off button.
Are you sure trying to flash the correct firmware with correct changes, etc??
Please share with us the device and Android version, as well as the stock ROM version with changes you're trying to flash.
Put (copy and paste) the output of Odin below.
Another way to get the firmware flashed is by using Heimdall, but for that to happen you first need to rename the extension of the stock ROM (remove .md5 and leave .tar) and than extract all seperate pieces that are contained within the stock ROM.
All those extracted pieces from the stock ROM you have to upload seperately onto Heimdall and try to flash them to your tablet, one by one.
Heimdall you'll find 'here' or use FWUL instead which has Heimdall pre installed, download is to be found 'here' and install it on a USB medium a stick, to put FWUL onto USB, use Balena-Etcher and the download is to be found 'here'.
Micro USB cable does work, but if you're unsure, try another one and make sure using the correct drivers too.
Using Odin, make sure the tablet is recognised and 'connected' in Odin, also make sure 'repartitioning' is unchecked.
If you've used the wrong Odin version, flashing will fail!
You have Discord by any chance?
If so, please add me @Hyldran0#8832
Thank you for you time man!
Hyldran0 said:
You have Discord by any chance?
If so, please add me @Hyldran0#8832
Thank you for you time man!
Click to expand...
Click to collapse
You're welcome.
Hi, complete novice here, does anyone know where I can get a working Firmware for my Tab 3 v7 (SM-210)?
I have searched through various forum articles here, and tried to install with several builds but none will install. The only one that gets anywhere near is the JASBR build by gr8nole. It appears to install, but on restart, the TAB just sits on the "Samsung Tab3" start screen.
I read that I may need to flash the firmware 4.4.4 (Kit Kat), but can't find it!
The unit is not totally bricked (yet), as I can run TWRP 2.8, with which I created a backup of the original build, but when I try to restore the backup, it fails at just over 31%.
Can anyone help please?

Categories

Resources