Related
Hello to everyone. This is my first adventure. I've read until my eyes have bleed but still haven't figured out a solution to my problem so I will ask scaringly...
I have a AT&T Samsung Note II SGH-I317 rooted.
My phone is currently stuck on "Samsung GALAXY Note II" screen after I did a factory reset.
Initially this worked but as I was setting everything back up, I received a ota system update. And it gave me a failure to upgrade error, try again in kies. Kies will not recognize my phone because it's stuck. I've done the hold up volume + home then power a hundred times but it won't let me go into recovery. I've read of everyones success but I'm still stuck! I used stock roms from at least 5 different sources but none have fully recovered my phone. It does however PASS in odin 3.07 and 3.09.
What other options have I missed? Please help....
poochieturner said:
Hello to everyone. This is my first adventure. I've read until my eyes have bleed but still haven't figured out a solution to my problem so I will ask scaringly...
I have a AT&T Samsung Note II SGH-I317 rooted.
My phone is currently stuck on "Samsung GALAXY Note II" screen after I did a factory reset.
Initially this worked but as I was setting everything back up, I received a ota system update. And it gave me a failure to upgrade error, try again in kies. Kies will not recognize my phone because it's stuck. I've done the hold up volume + home then power a hundred times but it won't let me go into recovery. I've read of everyones success but I'm still stuck! I used stock roms from at least 5 different sources but none have fully recovered my phone. It does however PASS in odin 3.07 and 3.09.
What other options have I missed? Please help....
Click to expand...
Click to collapse
Weird, ODIN should usually work without issue. Are you using the custom recovery or a stock recovery? You should be able to flash a new recovery with ODIN I believe.
Are you using the factory USB charging cable? Knock-off cables cause odin and kies errors.
Reply
They were all stock recovery. As I mentioned before, the first time I done it, it worked fine but once I received the update from at&t I've not been able to duplicate that process without get stuck. I can access download and that's it.
Yes, I'm using the usb that came with my phone. ODIN recognizes my phone immediately.
poochieturner said:
They were all stock recovery. As I mentioned before, the first time I done it, it worked fine but once I received the update from at&t I've not been able to duplicate that process without get stuck. I can access download and that's it.
Yes, I'm using the usb that came with my phone. ODIN recognizes my phone immediately.
Click to expand...
Click to collapse
I'm having this same exact problem under very similar circumstances. Has anyone found a solution?
Thanks Man
hylander2126 said:
I'm having this same exact problem under very similar circumstances. Has anyone found a solution?
Click to expand...
Click to collapse
Followed your post and got mine working also.. Bootloader did it! Thanks...
Hey Guys,
I received an update on my unlocked AT&T note II sgh-i317 yesterday. It caused the phone to go blank. I flashed stock firmware UCAL which seem to go well but now the phone will not boot up . It just boots into white Samsung Note II logo. Any suggestions on what to do?. I already pulled battery and tried going into recovery mode and sI still keep getting the same thing.
Thanks
BootLoop due to OTA Update SGH I317
I received the same OTA update last night.
My phone was rooted but had stock Rom.
The update finished and now my phone is in a bootloop. The only option I have to power on the phone is by pulling battery, volume down/power/home. But even then, it will not allow me to fully power on.
I tried Kies software to install the update but was unsuccessful. I will also try unrooting.
Same thing happened to me. Rooted but otherwise stock GN2. Got the update, rebooted and it got stuck at the boot logo. I tried everything. Flashed CWM, then tried a couple different ROM's. Then went to TWRP recovery, and tried the Team Elektron ROM, that got a little farther, boot logo with sound, but it still hung. Tried a modem update, and even the bootloader - nothing worked.
Luckily I had just bought mine ($300 on Amazon right now) so I just sent it back as defective and ordered a new one. Gonna be real careful of the ATT update and maybe even skip it and go right to a custom ROM.
azRisky said:
I received the same OTA update last night.
My phone was rooted but had stock Rom.
The update finished and now my phone is in a bootloop. The only option I have to power on the phone is by pulling battery, volume down/power/home. But even then, it will not allow me to fully power on.
I tried Kies software to install the update but was unsuccessful. I will also try unrooting.
Click to expand...
Click to collapse
Did you guys try clearing your cache?
blknsmth said:
Hey Guys,
I received an update on my unlocked AT&T note II sgh-i317 yesterday. It caused the phone to go blank. I flashed stock firmware UCAL which seem to go well but now the phone will not boot up . It just boots into white Samsung Note II logo. Any suggestions on what to do?. I already pulled battery and tried going into recovery mode and sI still keep getting the same thing.
Thanks
Click to expand...
Click to collapse
In Samsung the word Note 2 is pronounced t0lte.
CharliexCharger said:
Did you guys try clearing your cache?
Click to expand...
Click to collapse
I tired clearing everything, tried flashing everything, nothing worked. When I flashed the Elektron ROM it got a little further, an animated logo with sound, but never fully booted. I then tried all their (Team Elektron) recommended fixes but nothing worked. Finally gave up and shipped it back to Amazon today.
Getting my new one tomorrow, going to root it and not accept any OTA updates and most likely flash a non-AT&T ROM.
I had the same problem and fix it UCUCNE5
Flash odin AT&T UCUCNE5 i317 Stock ODIN Note 2 http://forum.xda-developers.com/gal.../rom-att-i317-ucucne5-mj4-stock-odex-t2802189
root again and block the update withTitanium Backup (FREEZE) AT&T Software update
azRisky said:
I received the same OTA update last night.
My phone was rooted but had stock Rom.
The update finished and now my phone is in a bootloop. The only option I have to power on the phone is by pulling battery, volume down/power/home. But even then, it will not allow me to fully power on.
I tried Kies software to install the update but was unsuccessful. I will also try unrooting.
Click to expand...
Click to collapse
I have posted a fix for those of you who got bricked by this update: see http://forum.xda-developers.com/gal...days-update-soft-bricked-phone-t2939649/page2. I give detailed instructions on how to fix it.
Please spread the word.
pstuart82 said:
I have posted a fix for those of you who got bricked by this update: see http://forum.xda-developers.com/gal...days-update-soft-bricked-phone-t2939649/page2. I give detailed instructions on how to fix it.
Please spread the word.
Click to expand...
Click to collapse
I tried this approach. It didn't work for me. I downloaded the stock rom and flashed it with Odin. My screen is still froze on the logo,and my battery icon is grey as if it's not charging. I charge it now in a battery charger just to be sure it's charged. I can't afford to lose this phone. Can someone please assist.
kcohen67 said:
I tried this approach. It didn't work for me. I downloaded the stock rom and flashed it with Odin. My screen is still froze on the logo,and my battery icon is grey as if it's not charging. I charge it now in a battery charger just to be sure it's charged. I can't afford to lose this phone. Can someone please assist.
Click to expand...
Click to collapse
What message did you receive when trying to flash? Did you flash the 4.4.2 ROM? What had you flashed beforehand
I'm not completely an expert but I've learned enough over the last 48 hours to fix my own phone.
pstuart82 said:
What message did you receive when trying to flash? Did you flash the 4.4.2 ROM? What had you flashed beforehand
I'm not completely an expert but I've learned enough over the last 48 hours to fix my own phone.
Click to expand...
Click to collapse
Odin said the flash was complete and successful, but the phone still won't get passed the logo screen. There is no recovery with this 4.4.2 firmware. I can't do a system wipe without a recovery. I tried flashing a custom recovery but It's not working either. I need a way to flash a complete 4.4.2 stock with recovery.
kcohen67 said:
I tried this approach. It didn't work for me. I downloaded the stock rom and flashed it with Odin. My screen is still froze on the logo,and my battery icon is grey as if it's not charging. I charge it now in a battery charger just to be sure it's charged. I can't afford to lose this phone. Can someone please assist.
Click to expand...
Click to collapse
I believe I am in the exact same boat. My note 2 had no modifications. Never tried to do anything to the phone in the way of new ROMs or rooting or anything. I picked up the phone and hit the home button the other night and the phone restarted, came up on the Samsung Galaxy Note II screen and stuck. Can't factory reset, same grey battery icon, can only power off by removing the battery, similar results when I try using Kies and Odin (assuming I am using them correctly). Will be following your thread and hoping someone can share some further advice...
rollinbonz said:
I believe I am in the exact same boat. My note 2 had no modifications. Never tried to do anything to the phone in the way of new ROMs or rooting or anything. I picked up the phone and hit the home button the other night and the phone restarted, came up on the Samsung Galaxy Note II screen and stuck. Can't factory reset, same grey battery icon, can only power off by removing the battery, similar results when I try using Kies and Odin (assuming I am using them correctly). Will be following your thread and hoping someone can share some further advice...
Click to expand...
Click to collapse
So if you pull battery, then restart with the 3 button combo to get to recovery,
(Hold down Volume Up and Power button and Home button together) you should be able to factory reset from there.
dicksteele said:
So if you pull battery, then restart with the 3 button combo to get to recovery,
(Hold down Volume Up and Power button and Home button together) you should be able to factory reset from there.
Click to expand...
Click to collapse
Thanks for your reply.
I can get to the menu and select the reset option (although i get a slew of red error messages along the way) but when it reboots, im right stuck back at the samsung GNII splash screen.
Check my other thread for more details http://forum.xda-developers.com/gal...reme-noob-gn2-mods-stuck-galaxy-note-t2941965 , if mine is a separate issue i dont want to hijack this thread.
Earlier this evening, after texting a friend, my phone rebooted itself.
It appears to be in a boot loop. It will only reboot into rebooting. Never loads Android. I pulled the battery, let it sit for a few minutes, and tried again with no results.
I've not done modding to the phone (mainly because its locked), and will be returning it to my local AT&T store tomorrow. Thankfully I have insurance on my phone, so I shouldn't have an issue getting a new one.
Anybody else had this issue, however? It's really strange.
Majin Kaioh said:
Earlier this evening, after texting a friend, my phone rebooted itself.
It appears to be in a boot loop. It will only reboot into rebooting. Never loads Android. I pulled the battery, let it sit for a few minutes, and tried again with no results.
I've done modding to the phone (mainly because its locked), and will be returning it to my local AT&T store tomorrow. Thankfully I have insurance on my phone, so I shouldn't have an issue getting a new one.
Anybody else had this issue, however? It's really strange.
Click to expand...
Click to collapse
Read a guide on flashing back to stock. Use ODiN and flash the stock file of your choice in the ATT note 4 forum from Download mode. Google how to boot into download mode. Hold those buttons until phone powers off then keep holding until you see download mode. You will need to install samsung drivers and for ODiN on Windows go to Devices coms and ports and change port to 3 in advanced tab.
sudoBacon said:
Read a guide on flashing back to stock. Use ODiN and flash the stock file of your choice in the ATT note 4 forum from Download mode. Google how to boot into download mode. Hold those buttons until phone powers off then keep holding until you see download mode. You will need to install samsung drivers and for ODiN on Windows go to Devices coms and ports and change port to 3 in advanced tab.
Click to expand...
Click to collapse
I updated my post to add in a missing word. I havn't done any modding. I do not intend to do any flashing to the device.
I'll be returning it to AT&T tomorrow and getting a new one. My question was if anyone has had this issue before. Thanks for your response. Unfortunately, does not address my question.
sudoBacon said:
Read a guide on flashing back to stock. Use ODiN and flash the stock file of your choice in the ATT note 4 forum from Download mode. Google how to boot into download mode. Hold those buttons until phone powers off then keep holding until you see download mode. You will need to install samsung drivers and for ODiN on Windows go to Devices coms and ports and change port to 3 in advanced tab.
Click to expand...
Click to collapse
I have had my share of boot looping experiences, never from not doing any type of experiments with my devices. nonetheless myself and I'm sure many other people just do what was mentioned in the quote to alleviate that problem.
i know you (OP) mentioned you don't plan on doing any flashing, but i would do that before using insurance personally, even if there was no deductible
Majin Kaioh said:
I updated my post to add in a missing word. I havn't done any modding. I do not intend to do any flashing to the device.
I'll be returning it to AT&T tomorrow and getting a new one. My question was if anyone has had this issue before. Thanks for your response. Unfortunately, does not address my question.
Click to expand...
Click to collapse
This process is not dangerous if your phone is in a bootloop. Hell AT&T or whatever carrier probably does this themselves if a phone is in this kind of situation. If not rooted or any mods you will still have OTA updates. If you are worried about carrier recognizing if you modded it or something and they wont take it back dont worry just flash it using ODiN. I've rooted many devices hacked compiled roms flashed them and kernels s-offed etc. You can always get back to stock remove flags and your carrier will take it back no matter what just dont return a device with the actual mods on it.
Why not just try to reset the device from the recovery menu? If it's a stock phone it should fix the bootloop.
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app
jack man said:
Why not just try to reset the device from the recovery menu? If it's a stock phone it should fix the bootloop.
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app
Click to expand...
Click to collapse
It won't fix what sounds like a missing or corrupted boot file, had to deal with it on a LG g3.. restoring a full back up or a plain reset had no effect.. it was either doing a full flash or flashing the boot files
for that phone it would randomly happen when the OTA tried to upgrade the device while it was rooted, took me 3 times of dealing with it before I realized OTA was still live
Small update. My local AT&T store has a replacement being sent to me. I'm unhappy, however, since its apparently a refurbished device. I pay for insurance that covers a new device if something, anything, happens. They're refusing to send me a new one for some reason that they won't explicitly state to me.
My loyalty with AT&T has wavered, and I will probably be on another network in coming months. I'm thinking Sprint so that I can least have an unlocked Note 4.
Regardless, since this device is being sent back, I decided to try and Odin flash it anyways. It did not work. Still boot loops at the Note 4/Android screen. Doesn't even load the AT&T logo. I'm fairly certain something is fundamentally broken with the device. Probably a factory error. It's never been dropped, and has been inside a hard case since day one.
Being that it is a manufacturing error, I'm not to angry about that. These things do happen. AT&T's treatment of me, however, is just unacceptable. I've been a customer for about eight years, and have been on Android since the Motorola Backflip. I upgraded to a Samsung Captivate and never looked at another manufacturor.
Are you able boot to the recovery menu?
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app
i have the bootloop issue before to put *#9090#
the loop is every aprox 3 mins
some sugestion?¡
sudoBacon said:
This process is not dangerous if your phone is in a bootloop. Hell AT&T or whatever carrier probably does this themselves if a phone is in this kind of situation. If not rooted or any mods you will still have OTA updates. If you are worried about carrier recognizing if you modded it or something and they wont take it back dont worry just flash it using ODiN. I've rooted many devices hacked compiled roms flashed them and kernels s-offed etc. You can always get back to stock remove flags and your carrier will take it back no matter what just dont return a device with the actual mods on it.
Click to expand...
Click to collapse
Good evening,
my n910A is stocked in Bootlop ,
I did try also to flash via odin the 4 zipped md5 files from this forum but nothing changed : http://forum.xda-developers.com/note-4-att/general/to-stock-files-latestcoc4-build-t3107391
when I press volume up+power+home it show LRX22C.N910AUCU1COC4 but the version on the label of my box is N910AUCU1ANIE ,
I don't know if I should go back to the previous version and how to do it ?????
or something else??????
please help because I am lost
thanks
thepinkpanter said:
Good evening,
my n910A is stocked in Bootlop ,
I did try also to flash via odin the 4 zipped md5 files from this forum but nothing changed : http://forum.xda-developers.com/note-4-att/general/to-stock-files-latestcoc4-build-t3107391
when I press volume up+power+home it show LRX22C.N910AUCU1COC4 but the version on the label of my box is N910AUCU1ANIE ,
I don't know if I should go back to the previous version and how to do it ?????
or something else??????
please help because I am lost
thanks
Click to expand...
Click to collapse
Try downloading one of sunderwares stock firmwares in a newer 3.10 odin after extracting the zip with contained files. I recommend latest OC4 just re flash it a different one or try again
sudoBacon said:
Try downloading one of sunderwares stock firmwares in a newer 3.10 odin after extracting the zip with contained files. I recommend latest OC4 just re flash it a different one or try again
Click to expand...
Click to collapse
I already did it but by using Odin 3.09 pls. see http://forum.xda-developers.com/note-4-att/general/to-stock-files-latestcoc4-build-t3107391/page5
maybe I did something wrong
or from where can I get / download a different N910AUCU1COC4 ?
thanks again for your kind help
Okay not sure how many people still frequent this forum, but hopefully someone can help. So yesterday my phone was charging up and I decided to reboot it because it was time for a weekly reboot. So I held the power button and selected reboot to reboot it. It shut down then started to boot, the samsung logo appeared then disappeared followed by the galaxy s3 logo.
After that it just shut off. When I tried to turn it on again, all it did was vibrate vibrant and vibrant in a loop every time I pushed the power button. Finally I decided to try recovery mode (stock recovery) and wipe cache...no dice. So I tried download mode and that came up fine. I rebooted out of download mode and plugged the phone in. The charge animation came up as well as the LED red charge light. I let it charge for a few hours then unplugged it, removed the battery for a minute and put it back in and tried to turn it on. I even tried a different/another battery and got the same result.
All it did was the vibrate loop sequence again i mentioned above. I don't want to loose all my stuff I have on it. I heard dirty flashing in ODIN will wipe your data. I'm not sure if the debrick image is for Android 4.4.2 because that's what I'm on. Does anyone know how to fix this or have had similar issues and got it working again?
StoneyJSG said:
Okay not sure how many people still frequent this forum, but hopefully someone can help. So yesterday my phone was charging up and I decided to reboot it because it was time for a weekly reboot. So I held the power button and selected reboot to reboot it. It shut down then started to boot, the samsung logo appeared then disappeared followed by the galaxy s3 logo.
After that it just shut off. When I tried to turn it on again, all it did was vibrate vibrant and vibrant in a loop every time I pushed the power button. Finally I decided to try recovery mode (stock recovery) and wipe cache...no dice. So I tried download mode and that came up fine. I rebooted out of download mode and plugged the phone in. The charge animation came up as well as the LED red charge light. I let it charge for a few hours then unplugged it, removed the battery for a minute and put it back in and tried to turn it on. I even tried a different/another battery and got the same result.
All it did was the vibrate loop sequence again i mentioned above. I don't want to loose all my stuff I have on it. I heard dirty flashing in ODIN will wipe your data. I'm not sure if the debrick image is for Android 4.4.2 because that's what I'm on. Does anyone know how to fix this or have had similar issues and got it working again?
Click to expand...
Click to collapse
You could try reflashing system and boot partition.
iloveoreos said:
You could try reflashing system and boot partition.
Click to expand...
Click to collapse
Is this done in ODIN? Will it wipe all my data? I'm trying to avoid anything like a data factory reset as I want to recover my stuff that wasn't saved to my SD card.
StoneyJSG said:
Is this done in ODIN? Will it wipe all my data? I'm trying to avoid anything like a data factory reset as I want to recover my stuff that wasn't saved to my SD card.
Click to expand...
Click to collapse
I don't know why it would, but I have never tried it on a Samsung. Flashing something like TWRP doesn't erase data when you flash it.
Which ROM is currently on the phone?
AT&T never released a stock ROM for the sgh-i747 after 4.1.1 or 4.1.2. All system updates were pushed to the phone via OTA; therefore, you can't re-flash the ROM using Odin unless you use a file that was specfically create for Odin.
audit13 said:
Which ROM is currently on the phone?
AT&T never released a stock ROM for the sgh-i747 after 4.1.1 or 4.1.2. All system updates were pushed to the phone via OTA; therefore, you can't re-flash the ROM using Odin unless you use a file that was specfically create for Odin.
Click to expand...
Click to collapse
Would the one for sgh i747m work if you just flashed system and boot? You can get that in 4.4.2.
Before flashing anything, I recommend booting into download mode and confirm the the model is SGH-i747 and whether there is a line that makes reference to Knox or warranty bit.
If it is the sgh-i747 and there is reference to warranty bit, you should look at the possibility of flashing a ROM from here: https://forum.xda-developers.com/galaxy-s3-att/general/ucuemjb-to-ucufne4-firmware-update-t2808654
If it is an sgh-i747 with no reference to warranty bit, this means the phone is not running a 4.3 or newer bootloader.
audit13 said:
Before flashing anything, I recommend booting into download mode and confirm the the model is SGH-i747 and whether there is a line that makes reference to Knox or warranty bit.
If it is the sgh-i747 and there is reference to warranty bit, you should look at the possibility of flashing a ROM from here: https://forum.xda-developers.com/galaxy-s3-att/general/ucuemjb-to-ucufne4-firmware-update-t2808654
If it is an sgh-i747 with no reference to warranty bit, this means the phone is not running a 4.3 or newer bootloader.
Click to expand...
Click to collapse
It is on Android 4.4.2 with bootloader NE4. It's the sgh-i747 AT&T variant. My warranty bit is 0. I can boot into download mode and stock recovery fine, just it won't boot into Android. I read somewhere that it might be an IC chip or emmc issue?
Someone took the NE4 OTA and made some ODIN files out of it so I downloaded them. I just want to be able to recover my files from the internal storage so I haven't flashed anything yet.
Glad you are on top of things.
Flashing the same ROM should be fine and it does not normally wipe your data. That being said, there is always a chance that flashing will result in data loss.
If it is an errant app that is causing the issue, you may have no choice but to wipe the data.
Ah ok, that's a bummer. Well I guess I will try flashing the same ROM over it and see what happens. Hopefully my data and apps stay in tact. I thought it might be a chip on the logic board so I took it to a repair shop over the weekend. Now to get it back from them and try flashing the ROM over the ROM.
audit13 said:
Glad you are on top of things.
Flashing the same ROM should be fine and it does not normally wipe your data. That being said, there is always a chance that flashing will result in data loss.
If it is an errant app that is causing the issue, you may have no choice but to wipe the data.
Click to expand...
Click to collapse
Just an update. I managed to fix my phone with Odin. I flashed the NE4 kit kat BL, AP, CSC, and CP files. It did wipe everything and put it back to factory stock like a factor data reset would do, so I lost all my files and apps.
Sorry to hear that the data was wiped.
Thanks for the update.
CrDroid O/S works good on my old Samsung Galaxy S3 i747
audit13 said:
Before flashing anything, I recommend booting into download mode and confirm the the model is SGH-i747 and whether there is a line that makes reference to Knox or warranty bit.
If it is the sgh-i747 and there is reference to warranty bit, you should look at the possibility of flashing a ROM from here: https://forum.xda-developers.com/galaxy-s3-att/general/ucuemjb-to-ucufne4-firmware-update-t2808654
If it is an sgh-i747 with no reference to warranty bit, this means the phone is not running a 4.3 or newer bootloader.
Click to expand...
Click to collapse
Firstly, I am a newbie. I don't understand about this "warranty bit" . The Samsung S3 i747 is a very old phone ( hence no warranty after 8+ years ). Please explain !
---------- Post added at 04:46 PM ---------- Previous post was at 04:37 PM ----------
StoneyJSG said:
Okay not sure how many people still frequent this forum, but hopefully someone can help. So yesterday my phone was charging up and I decided to reboot it because it was time for a weekly reboot. So I held the power button and selected reboot to reboot it. It shut down then started to boot, the samsung logo appeared then disappeared followed by the galaxy s3 logo.
After that it just shut off. When I tried to turn it on again, all it did was vibrate vibrant and vibrant in a loop every time I pushed the power button. Finally I decided to try recovery mode (stock recovery) and wipe cache...no dice. So I tried download mode and that came up fine. I rebooted out of download mode and plugged the phone in. The charge animation came up as well as the LED red charge light. I let it charge for a few hours then unplugged it, removed the battery for a minute and put it back in and tried to turn it on. I even tried a different/another battery and got the same result.
All it did was the vibrate loop sequence again i mentioned above. I don't want to loose all my stuff I have on it. I heard dirty flashing in ODIN will wipe your data. I'm not sure if the debrick image is for Android 4.4.2 because that's what I'm on. Does anyone know how to fix this or have had similar issues and got it working again?
Click to expand...
Click to collapse
I'm not sure how many of us are out there, tinkering around with the 8+ year old Samsung Galaxy S3 i747 . While I am a newbie, I have enjoyed flashing Custom ROM's , from CyanogenMod, thru various versions of Lineage, and now CRdroid.
You spoke of: " . . . dirty flashing in ODIN . . . "
I have always used ODIN to INSTALL a 'recovery' system such as TWRP ( which is a .Tar file )
After TWRP is installed ( using ODIN ) I unplug phone from my computer. Then boot into TWRP recovery ( holding down the three buttons ). I do a clean install (flash) of the newest O/S that I can find ( Android 4.4 is really old ). It is that .Zip file that I flash, then reboot the phone. Always works for me.
Eventually I learned how to back up all my contacts, SMS, logs, photos, etc.
BTW I am totally free of Google; no Google Play Store, no Google Pay, no Google Framework, no Gapps, no Google spyware, no Google bloatware, no Google tracking etc.
I download all my apps as APK's which are readily available on the Net ( Google them . . . just kidding! ).
My older Samsung S3 i747 was a 'd2att' originally locked to Rogers, in Ottawa, Ontario, Canada. Then switched over to MTS (Manitoba Telephone System). Now running on Bell Canada. My replacement is also a Samsung S3 i747, originally running T-Mobile in Arizona, now running on Bell Canada.
These are damn fine phones.
DavidWCS said:
Firstly, I am a newbie. I don't understand about this "warranty bit" . The Samsung S3 i747 is a very old phone ( hence no warranty after 8+ years ). Please explain !.
Click to expand...
Click to collapse
Do you see anything in the download mode screen that has the term "warranty bit"?
Is the phone model in download mode screen shown as an sgh-i747 or sgh-747m?
audit13 said:
Do you see anything in the download mode screen that has the term "warranty bit"?
Is the phone model in download mode screen shown as an sgh-i747 or sgh-747m?
Click to expand...
Click to collapse
Curious, I rebooted my phone into download mode ( holding volume down in the 3 finger format ).
There is nothing in the download mode screen that has the term "warranty bit". Just the WARNING !! A custom OS can cause critical problems . . .
There is no phone model in download mode screen shown as an sgh-i747 or sgh-747m
Sorry, but I still don't understand the importance of warranty in an 8+ year old phone. Am I still missing something?
DavidWCS said:
Curious, I rebooted my phone into download mode ( holding volume down in the 3 finger format ).
There is nothing in the download mode screen that has the term "warranty bit". Just the WARNING !! A custom OS can cause critical problems . . .
There is no phone model in download mode screen shown as an sgh-i747 or sgh-747m
Sorry, but I still don't understand the importance of warranty in an 8+ year old phone. Am I still missing something?
Click to expand...
Click to collapse
You are not in download mode.
The warranty bit term is not about warranty, it is about whether the phone has a locked bootloader.
audit13 said:
You are not in download mode.
The warranty bit term is not about warranty, it is about whether the phone has a locked bootloader.
Click to expand...
Click to collapse
OK, I tried it again. This time I went one step further. Aha! Tiny print on upper left of screen. Have attached a sample photo showing what I see. And yes, I can see what you mean: " Warranty Bit: 1 " . Thank you, it makes sense now.
.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DavidWCS said:
OK, I tried it again. This time I went one step further. Aha! Tiny print on upper left of screen. Have attached a sample photo showing what I see. And yes, I can see what you mean: " Warranty Bit: 1 " . Thank you, it makes sense now.
.View attachment 4991379
Click to expand...
Click to collapse
The phone is not an AT&T S3, it is a T-Mobile s3 sgh-t999?
audit13 said:
The phone is not an AT&T S3, it is a T-Mobile s3 sgh-t999?
Click to expand...
Click to collapse
There are 2 i747 phones; d2Can & T999. In the past, the O/S's that I flashed, were designed for d2att. No difference in how they functioned, as far that I could notice.
DavidWCS said:
There are 2 i747 phones; d2Can & T999. In the past, the O/S's that I flashed, were designed for d2att. No difference in how they functioned, as far that I could notice.
Click to expand...
Click to collapse
Yes, there are two models of the i747: sgh-i747 (AT&T, d2att) and sgh-i747m (non-AT&T, d2can)
The T-Mobile s3 is sgh-t999 (d2tmo).
Hello, just picked up a used tab s t705w bell in good shape. Ive tried to flash the original 5.02 as well as autroot and another original image as well. All of them fail. Im using the latest version of Odin. The connection says its ok as per com port than when it gets to boot.img it stops and fails. Ive tried 2 USB cables as well as all my USB ports to no avail. Please help as to what I'm doing wrong, thanks.
Heres a pic
Update: tried with laptop still same thing, is there anybody that can offer a suggestion? I even unplugged the battery and plugged back in. I also tried several older versions of Odin.
Well since nobody knows what to do my research indicates possibly nand chip has failed meaning hardware issue. Gonna look at returning it.
cesandoid said:
Well since nobody knows what to do my research indicates possibly nand chip has failed meaning hardware issue. Gonna look at returning it.
Click to expand...
Click to collapse
Hi,
Did you end up fixing the issue? I think I have the same issue as yours on a SM T800. It came with 4.4.2 so when I tried to update to Marshmellow it failed and it restarted fine, and it told me to update via my pc using Kies or smarth switch. So I did so and guess what happened Smart Switch failed as well but now it bricked the tablet. So when Smart switch tries to install the recovery, same thing. So I now have a brick! So I am trying to find out if there was a solution or not. If not I will just have to wear it.
Thanks.
hello, identical problem ,ODIN does not complete the procedure,Tablet locked in the emergency screen.... no key combination works........
any ideas?
TEX
tex_kit said:
hello, identical problem ,ODIN does not complete the procedure,Tablet locked in the emergency screen.... no key combination works........
any ideas?
TEX
Click to expand...
Click to collapse
You're saying you can't get it back into the Odin download mode?
Hold HOME+ VOLUME UP+VOLUME DOWN+POWER. (Keep holding)
When the Samsung splash screen comes up, let go of the VOLUME UP button.
When the Odin warning screen comes up, let go of all buttons and click VOLUME UP.
Even when I was sure mine was soft-bricked, I was able to get it into Odin download.
wellersl said:
You're saying you can't get it back into the Odin download mode?
Hold HOME+ VOLUME UP+VOLUME DOWN+POWER. (Keep holding)
When the Samsung splash screen comes up, let go of the VOLUME UP button.
When the Odin warning screen comes up, let go of all buttons and click VOLUME UP.
Even when I was sure mine was soft-bricked, I was able to get it into Odin download.
Click to expand...
Click to collapse
thanks ,executed the procedure and finally I’m back in the Odin screen.Unfortunately the error has recurred ........ the end of the procedure shall be interrupted .....
[/IMG]
end of the test.
More info:last update to Android 6...enter in Odin Mode . I manage to start the installation but towards the end of lock , tried both with FIR. OMN-T805XXU1ANFB-2014,(European generic), both with OMN-T805XXU1CPL1_T805OMN1CPK1-20161212(dedicated version
tex_kit said:
thanks ,executed the procedure and finally I’m back in the Odin screen.Unfortunately the error has recurred ........ the end of the procedure shall be interrupted .....
[/IMG]
end of the test.
More info:last update to Android 6...enter in Odin Mode . I manage to start the installation but towards the end of lock , tried both with FIR. OMN-T805XXU1ANFB-2014,(European generic), both with OMN-T805XXU1CPL1_T805OMN1CPK1-20161212(dedicated version
Click to expand...
Click to collapse
In my limited experience with Odin, I find it to be a very stable, robust, and reliable application. Having said that, and not knowing what version you're using, the usual suggestions are:
Try another (older) version of Odin.
Try another USB cable.
Always use a USB 2 port.
Try a different firmware package making *certain* it's for your model tab. (<- This is what's most suspect - IMHO.)
As long as you can still invoke the Odin downloader on your tab, there's still hope.
Good morning, Sir
News update, detailed search carried out, found the latest specific Samsung Firmware, (XEH-T805XXU1CPL1-20170111202424 with MM.)
The procedure with Odin has been successfully completed. (end of good news) At the end of the operation the tablet remains with the logo samsung bright intermittently . performed hard reset but remains stuck on the initial logo samsung always bright intermittently.
Suggestions?
TEX
tex_kit said:
Good morning, Sir
News update, detailed search carried out, found the latest specific Samsung Firmware, (XEH-T805XXU1CPL1-20170111202424 with MM.)
The procedure with Odin has been successfully completed. (end of good news) At the end of the operation the tablet remains with the logo samsung bright intermittently . performed hard reset but remains stuck on the initial logo samsung always bright intermittently.
Suggestions?
TEX
Click to expand...
Click to collapse
PM SENT.
Yup. Been there. Done exactly that. I fixed it by subscribing to SamMobile, then paying for and downloading the OEM firmware. That's probably the best news, You can always get back to a box-stock condition. If you have the patience, you can download the firmware for free.
EDIT: Once I got back to stock, I looked for and found:
DAMMIT! I keep forgetting we have two different tabs. Obviously Klimtwifi is wrong for you.
lineage-14.1-20200321-UNOFFICIAL-klimtwifi, installed it with Odin3_v3.11.2 (Not sure it matters.)
Then rooted it using Odin: https://android.gadgethacks.com/how-to/android-basics-root-with-cf-auto-root-0167401/
And, once rooted, installed the Official TWRP app from Google Play. I always use the next older version of TWRP (twrp-3.3.0-0-klimtwifi) because TWRP doesn't like me much.
Then, rebooted into recovery and flashed GApps (open_gapps-arm-9.0-nano-20200417)
FWIW - This is from feeble memory, and I still have all the files - both those that worked and those that didn't - all in the same folder. So if something doesn't work for you, I've got what worked for me.
All said, getting LineageOS on this thing was far, far simpler that trying to get it back to stock.
All said, getting LineageOS on this thing was far, far simpler that trying to get it back to stock.???
IS A build guide available ??
The Samsung Galaxy Tab S 10.5 LTE is no longer maintained.
I just thought I’d switch to android 4.4 ....
The problem comes from the loss of boot files?
TEX
tex_kit said:
All said, getting LineageOS on this thing was far, far simpler that trying to get it back to stock.???
IS A build guide available ??
The Samsung Galaxy Tab S 10.5 LTE is no longer maintained.
I just thought I’d switch to android 4.4 ....
The problem comes from the loss of boot files?
TEX
Click to expand...
Click to collapse
This should get you where you want to be: http://www.lineageosdownloads.com/download-galaxy-tab-s-10-5-lte-lineage-os/
I'm not sure what caused the problem in the first place. I was just very relieved to see it boot when i got the stock ROM back on it.
Did you restore yours back to stock? It's good practice.
wellersl said:
This should get you where you want to be: http://www.lineageosdownloads.com/download-galaxy-tab-s-10-5-lte-lineage-os/
I'm not sure what caused the problem in the first place. I was just very relieved to see it boot when i got the stock ROM back on it.
Did you restore yours back to stock? It's good practice.
Click to expand...
Click to collapse
Good morning,
The tablet is Hungarian (made search via samsung and s n), I install unique files (extension .md5).
installed the version K.K. 4 , the only novelty the presence during the first restart of the colored logo, performed manual restart and hard reset /wipe ,
At the end it remains with the Samsung logo bright intermittently (Samsung logo power etc.etc.). Found the multifile firwarware.
Odin does not recognize extension . enc4 and (oddly ) I find nothing to extract Files...
TEX
tex_kit said:
Good morning,
The tablet is Hungarian (made search via samsung and s n), I install unique files (extension .md5).
installed the version K.K. 4 , the only novelty the presence during the first restart of the colored logo, performed manual restart and hard reset /wipe ,
At the end it remains with the Samsung logo bright intermittently (Samsung logo power etc.etc.). Found the multifile firwarware.
Odin does not recognize extension . enc4 and (oddly ) I find nothing to extract Files...
TEX
Click to expand...
Click to collapse
Did you find your model number on the SamMobile website? That's really where you need to start. Once you have the correct OEM firmware, using Odin to install it is a no-brainer. You need to get back to stock before you can move on to custom.
What is your complete model number?
Send me a private message. I think I may be confused and am causing you extra confusion.
wellersl said:
Did you find your model number on the SamMobile website? That's really where you need to start. Once you have the correct OEM firmware, using Odin to install it is a no-brainer. You need to get back to stock before you can move on to custom.
What is your complete model number?
Send me a private message. I think I may be confused and am causing you extra confusion.
Click to expand...
Click to collapse
Good morning,
Downloaded and installed the latest version SM-T805_t805xxu1cpl1_marshmallow(Android 6.0.1)_Xeh_factory Rom (4 File)_20170111.zip.enc4. (decrypted with an earlier version of samfirm (3.9 ).
the installation procedure of the 4 files, AP, BL, CP, CSC, does not involve problems.
Unfortunately at the end of the procedure the Tablet does not restart automatically, and after its hard wipe reset remains locked on the initial logo samsung always bright intermittently.
During the tests I noticed that holding down the power button tries to start. The second samsung logo stands out completely but does not pass the stage.
The feeling he can’t make it.
A new PIT file?
Tex
wellersl said:
Did you find your model number on the SamMobile website? That's really where you need to start. Once you have the correct OEM firmware, using Odin to install it is a no-brainer. You need to get back to stock before you can move on to custom.
What is your complete model number?
Send me a private message. I think I may be confused and am causing you extra confusion.
Click to expand...
Click to collapse
Good morning, first of all
I want to thank you for your patience and time.
Performed yet another installation test with Odin this time with Android 5 (XEH-T805XXU1BOJ1-20151111094815) similar result, you have precedents.
But with a novelty
.At the end of the installation, the tablet remains off, as in the pretending tests, I try to start it normally but nothing, in addition to the ever-present Logo (Samsung Galaxy tab S) flashing intermittently.
I press the power button for several seconds with the result of making the second samsung logo appear (colored) with an Android loading start, release the button, the device turns off.
By re-activating the flashing logo (Samsung Galaxy tab S) normally.
Holding down the power button starts
Android update - optimization of the accompanying application (192 tot), a few minutes later always with the power pressed, the process ends and the installation of applications begins, after a few seconds, the first APP starts., the tablet turns off.
By turning it on again and the intermittent luminous logo (Samsung Galaxy tab S) reappears.
Repeating the procedure (power button pressed continuously) you get colored samsung logo and the writing (alkalmazàsok telepitèese) installation of applications and turns off.
I perform a wipe data / factory reset obtaining:
--wiping data—
Formatting / data ...
Formatting / cache ...
Formatting / sbfs ....
E: unknow volume for path [/ sbfs]
E: unknow volume "/ sbfs"
Complete data wipes.
I run reboot system now.
The tablet turns on with the intermittently lit Logo (Samsung Galaxy tab S).
By repeating the whole procedure previously described, no changes are obtained.
TEX
alkalmazàsok telepitèese?
Neither Google nor I understand that phrase. Do you?
Irrespective of that, I'm at my wit's end. And, assuming you're following the published directions, you may be looking at a hardware failure.
Just to confirm, before all this started for you, this was a working tablet?
wellersl said:
Neither Google nor I understand that phrase. Do you?
Irrespective of that, I'm at my wit's end. And, assuming you're following the published directions, you may be looking at a hardware failure.
Just to confirm, before all this started for you, this was a working tablet?
Click to expand...
Click to collapse
good morning,
the tablet was working, during a game session started to reboot, always and only with the logo (Samsung Galaxy tab S) bright intermittently, performed hard reset, I did not fix anything. The only news, these days, after Odin, is the complete installation of android 5 with the power key pressed all the time.releasing the tablet key turns off . At the next power on I get the logo (Samsung Galaxy tab S) bright intermittently.
thank you for your patience and professionalism
Tex
This is the screen you see *before* you invoke Odin and connect the tab to your PC?
View attachment 5009263