Hey everybody, I flashed the revolution rom from TWRP. It went through the setup menu and then finished flashing and went to reboot. Nothing. No button combinations have been able to start the phone and when I put the battery in the camera flash blinks once and thats it. If I charge the phone without the battery I get a solid red LED on the front but still no boot. I tried the unbrick by sd card method and that doesn't work either. What happened?
Thanks for your help!
Are you sure the rom was for an i747, i747m, or d2lte?
Do you have a link to the ROM?
audit13 said:
Are you sure the rom was for an i747, i747m, or d2lte?
Do you have a link to the ROM?
Click to expand...
Click to collapse
Yes,
This is the page that led me to the ROM:
http://joyofandroid.com/10-best-custom-roms-samsung-galaxy-s3/
And this is the actual ROM:
http://forum.xda-developers.com/gal...m-android-revolution-hd-52-0-android-t1797334
I noticed on the ROM page it says "improved CPU support". There were a bunch of tweak apps I checked in the installation menu. Not sure if it's possible they cooked the CPU?
Thanks for taking the time to help me.
The ROM you linked is for the international version of the s3 (i9300, i9305, look at the top of the forum heading), not the North American version.
What happens when you connect the phone to your computer with the USB cable? Do you see this in device manager: qhsusb_dload ?
audit13 said:
The ROM you linked is for the international version of the s3 (i9300, i9305, look at the top of the forum heading), not the North American version.
What happens when you connect the phone to your computer with the USB cable? Do you see this in device manager: qhsusb_dload ?
Click to expand...
Click to collapse
After your post I also noticed it wasnt the right model number. Unfortunately the USB only worked for charging. I bought the phone with a known bad usb port, replaced it with a new usb and it only worked for charging after that. I have been flashing roms from the SD Card. Is there a way to unbrick other than JTAG (if that will even work)?
What ROM was on your phone before you flashed Revolution? You could try following one of the debrick threads.
http://forum.xda-developers.com/showthread.php?t=2549068&page=3
audit13 said:
What ROM was on your phone before you flashed Revolution? You could try following one of the debrick threads.
http://forum.xda-developers.com/showthread.php?t=2549068&page=3
Click to expand...
Click to collapse
I had Dirty Unicorns on there before. I tried the solution in the link but the phone behaves exactly the same with the SD Card in or out. I have been flashing roms for years and never bricked a phone but it looks like I got too careless. Do you know if a working USB is required for a Jtag repair and return to stock rom to work?
For JTAG, I don't think they use the USB port. They need to get access to the rom chip to program it.
http://www.forensicswiki.org/wiki/JTAG_Samsung_Galaxy_S3_(SGH-I747M)
ughhh
I believe I just did the same thing as you. I followed the same link and go to the same page.
Downloaded from here http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
Now my phone wont even turn on, red charging light comes on with battery out and plugged into PC.
I do see : qhsusb_dload in device manager... I thought my phone was i9300, should've double checked. Was just in such a rush to try something new because my phone was pretty horrible with Cyanogenmod on there.
79TAKid said:
ughhh
I believe I just did the same thing as you. I followed the same link and go to the same page.
Downloaded from here http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
Now my phone wont even turn on, red charging light comes on with battery out and plugged into PC.
I do see : qhsusb_dload in device manager... I thought my phone was i9300, should've double checked. Was just in such a rush to try something new because my phone was pretty horrible with Cyanogenmod on there.
Click to expand...
Click to collapse
Looks to me like your phone is hard-bricked. You could always try booting the phone with a de-brick image.
audit13 said:
Looks to me like your phone is hard-bricked. You could always try booting the phone with a de-brick image.
Click to expand...
Click to collapse
Thanks, I had read about this in another thread. I gave it a shot and used a debrick image on a 16gb micro SD... it booted! :laugh:
I was able to get into the phone and follow the guide to move the debricked bootloader over to the internal storage (phone would then boot without SD card). After that I used ODIN and got it to load a stock 4.1.1 image to the phone. Phone is up and running but IMEI is '0' and serial is wrong so 4g is not working... Trying to figure out how to fix this now.
I'll try to post the links I used here shortly to help others out.
Congratulations on getting it to work.
What is the bootloader on your phone? The imei is probably 0 because your bootloader is not compatible with your modem.
audit13 said:
Congratulations on getting it to work.
What is the bootloader on your phone? The imei is probably 0 because your bootloader is not compatible with your modem.
Click to expand...
Click to collapse
Is there any easy way to check which boot loader i'm using?
In case this helps, here is what I did last night to get my phone going again:
I followed these instructions
http://forum.xda-developers.com/showthread.php?t=2660566
(grabbing the AT&T unbrick image here https://drive.google.com/folderview?id=0B612qYHFMILfWUlMTTEwdUstcXM&usp=sharing )
That got me back up and running into Cyanogenmod (I believe version 4.4?) From there I continued on with the steps
"Restoring stock bootloader
1) You were able to boot into the ROM
2) Plug your phone into a computer and use MTP mode
3) Move the debrick file onto your internal sdcard (/sdcard/debrick.bin)
4) Disconnect your phone
5) Open up a Terminal Emulator on your phone and input this code
Code:
su
dd if=/sdcard/debrick.bin of=/dev/block/mmcblk0
Click to expand...
Click to collapse
I then flashed I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5 with Odin.
I've tried a few little quick things i've read about typing in a *# number to get into service mode but that didn't change anything or fix IMEI. I also just rooted it (a few walkthroughs I was starting to look into required a rooted phone.
I also read a few times that people said to just flash the stock rom/modem onto the phone again? I'm just being very cautious this time around :silly:
Install terminal emulator and type this in: "getprop ro.bootloader" without the quotes but with the spaces. Press enter and let us know what it says on the screen.
The LK3 firmware is 4.1.1. What is the baseband on your phone? If your baseband is LK3 and your bootloader is MJB, this may be why you have no imei.
audit13 said:
install terminal emulator and type this in: "getprop ro.bootloader" without the quotes but with the spaces. Press enter and let us know what it says on the screen.
The lk3 firmware is 4.1.1. What is the baseband on your phone? If your baseband is lk3 and your bootloader is mjb, this may be why you have no imei.
Click to expand...
Click to collapse
i747ucdlk3
79TAKid said:
i747ucdlk3
Click to expand...
Click to collapse
SO your phone now boots from internal storage and the bootloader is LK3. What is the baseband?
audit13 said:
SO your phone now boots from internal storage and the bootloader is LK3. What is the baseband?
Click to expand...
Click to collapse
Sorry yes, after I used the command to copy the bootloader over from the debrick file, I was then able to use the phone without a SD card from that point on.
Baseband says I747UCDLK3 as well..
{
"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"
}
Weird that you have no IMEI when you bootloader matches your modem.
If you still have Philz on your phone, create a nandroid backup and try a custom ROM to see if anything changes.
If nothing changes, you may need to use nvwriter to inject the imei.
http://forum.xda-developers.com/showthread.php?t=1804117
audit13 said:
Weird that you have no IMEI when you bootloader matches your modem.
If you still have Philz on your phone, create a nandroid backup and try a custom ROM to see if anything changes.
If nothing changes, you may need to use nvwriter to inject the imei.
http://forum.xda-developers.com/showthread.php?t=1804117
Click to expand...
Click to collapse
Thanks for the advice, I will try this when I get time (at work right now). I've never used Philz, had to look up what it was! I've always used CWM. Would you recommend I use Philz? I will get a backup before I do anything else and reply back.
Philz is based on CWM but with a few advanced features. Either version should do the job.
Related
Hey guys, I'm new here and im really new to Android, i decided to switch over from apple because they are lame... I bought a samsung galaxy s3 AT&T 16gb, roughly 2 n a half weeks ago. I was looking at the OMEGA rom and i read that i had to be rooted first so i tried to root my phone and when i used odin, it said my phone was incompatible with the root file. I then unplugged and tried to reastart my phone but it put me at the recovery screen that says i need to plug my phone into kies for restoration, i did that and my phone wasn't detected... It wouldn't let me start the phone back up and the only thing i could do was the download transfer... I then tried to fix it by doing this ...
http://forum.xda-developers.com/showthread.php?t=1506330
I open odin and used that tar file and it said everything was successful, and that my phone was reastarting, but it started up to the words Samsung and turned off... It won't power on for the reset volume up+ home + power. It starts to start up once i do those keys but not always, and if it starts up it says SAMSUNG and at the top left there is a blue text ( words ) that say something but i cant read them in time and the phone turns off.. I am still able to get into the DOWNLOAD mode but it also doesn't let me sometimes only if it's connected to the computer and when i hold volume down plus power it goes into the download mode. I'm really upset, i know it takes time to fully understand all of the techniques to flashing, roms, and other things.. Im a noob and i really hope to get my phone working again... I really would appreciate if someone could help me out.. I didn't understand how to back it up and thats where i went wrong i should of spent time figuring it out but i didnt....
My phone is AT&T sgh 1747.
Please guys, help me out. I am willing to donate a couple bux for someone that can guide me through this process of fixing my phone and putting it back to exactly stock and brand new like out of the box from att.
Update* Those blue words in the right hand corner say Recovery Booting, but then the phone kicks back off again.
Go into download mode and flash a stock rooted ROM... use Odin. Reinstall drivers and use OEM cord to connect with if it's giving you problems. Windows 7? If you can get into download mode your not bricked.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
blaker13 said:
Go into download mode and flash a stock rooted ROM... use Odin. Reinstall drivers and use OEM cord to connect with if it's giving you problems. Windows 7? If you can get into download mode your not bricked.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thank you for your reply, Like i said im a noob currently with roms am flashing an all that stuff could you please guide
Me step by step? I dont really understand what drivers i would have to reinstall? and yes i am on windows 7. Also what options would i set in odin to do this?
First off are you releasing the buttons as soon as you see the screen with the blue words, if your not you should be, if you are and still get reboots I would suggest you follow the directions in the thread I will link below. The image you will need is the AT&T image ending with I747UCALG1.
http://forum.xda-developers.com/showthread.php?t=1739426
[HOWTO] [ROOT] No Tripping Flash Counter - [ATT / Bell / Telus / Rogers / Sasktel]
This will give you stock with root only. Then if you so choose you can follow the third option in that thread to install a custom recovery.
jethro650 said:
First off are you releasing the buttons as soon as you see the screen with the blue words, if your not you should be, if you are and still get reboots I would suggest you follow the directions in the thread I will link below. The image you will need is the AT&T image ending with I747UCALG1.
http://forum.xda-developers.com/showthread.php?t=1739426
[HOWTO] [ROOT] No Tripping Flash Counter - [ATT / Bell / Telus / Rogers / Sasktel]
This will give you stock with root only. Then if you so choose you can follow the third option in that thread to install a custom recovery.
Click to expand...
Click to collapse
When i click PDA it's not locating the file unless i type it in into where the file is written in the text box.. Once its in odin, i click pda load that file.. and its saying this...
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<OSM> All threads completed. (succeed 0 / failed 1)
Why is it doing this?
In that thread i dont see a stock odin tar which is says to use first. Im currently looking for a stock odin tar for my 1747 att if anyone already has it please post it.
{
"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"
}
here's a screen shot.
Update.. I re- did it again.. I used this file I click on PDA and put this in pda-odin-att-stock-kernel.tar.. after that was done. the phone still keeps doing the same thing.. Im trying to use this file root69_ATT_I747UCALG1.7z but its not working?
update* I used http://forum.xda-developers.com/showthread.php?t=1727443 and now it does the same thing but now it shows Samsung Galaxy s3, and it shows on my computer drivers installing... But then after like 30 seconds it says drivers stopped installing and the fone vibrates and i still can't get it to boot into recovery.. i can still get it into download mode... The only thing it fixed was now i can see Samsung Galaxy S3 which it didn't do until i used his file... Mine is the international gsm att 1747 model. Ugh.. I really need to get it fixed.
You need to unzip the .7z file you download so that it ends in .tar then it should work, that is step two in the link I posted for you. Your screenshot shows you trying to flash the .7z file, BUT....did I see you mention international version....that's a completely different phone or did I read your post wrong?
twistedpwnsj00 said:
Mine is the international gsm att 1747 model. Ugh.. I really need to get it fixed.
Click to expand...
Click to collapse
I don't think that a international model exists in AT&T's line up. I747 is a US variant. If you have AT&T stick with the AT&T forum. Using files from a different carrier can potentially brick your phone.
Plug in the oem usb cable into the phone after its connected to the computer and after the phone is in download mode. It will recognize it. You just need the right files and ODIN will do the rest.
You can fix it via Kies too, but you'll have to look in the help section. It explains how to do it. I searched in help to find the answer.
AT&T GS3
Rom: AOCP
Kernel: KT747
jethro650 said:
You need to unzip the .7z file you download so that it ends in .tar then it should work, that is step two in the link I posted for you. Your screenshot shows you trying to flash the .7z file, BUT....did I see you mention international version....that's a completely different phone or did I read your post wrong?
Click to expand...
Click to collapse
Please disregard that i don't know why i included that... It's not international i just double checked.
im trying to unzip that file now.
jethro650 said:
First off are you releasing the buttons as soon as you see the screen with the blue words, if your not you should be, if you are and still get reboots I would suggest you follow the directions in the thread I will link below. The image you will need is the AT&T image ending with I747UCALG1.
http://forum.xda-developers.com/showthread.php?t=1739426
[HOWTO] [ROOT] No Tripping Flash Counter - [ATT / Bell / Telus / Rogers / Sasktel]
This will give you stock with root only. Then if you so choose you can follow the third option in that thread to install a custom recovery.
Click to expand...
Click to collapse
I did everything and the phone booted up and works now!!!!! Thank you so much!!!!!!!!!! Does this mean its fully stock now an i dont have to factory reinstall? or should i?
twistedpwnsj00 said:
I did everything and the phone booted up and works now!!!!! Thank you so much!!!!!!!!!! Does this mean its fully stock now an i dont have to factory reinstall? or should i?
Click to expand...
Click to collapse
Use root checker from the play store to see if you're rooted. If not you'll have to try again. You are most likely in stock.
AT&T GS3
Rom: AOCP
Kernel: KT747
twistedpwnsj00 said:
I did everything and the phone booted up and works now!!!!! Thank you so much!!!!!!!!!! Does this mean its fully stock now an i dont have to factory reinstall? or should i?
Click to expand...
Click to collapse
You are fully stock(system,kernel,recovery,apps) just with root. Look in your app drawer and see if superuser or superSU is there, if not then go to the play store and get superSU, and install that to control what gets root access and what doesn't.
Or just stay stock till you read more of the forums....
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Ok so i bought a Galaxy S3 For tmobile, i installed the 4.3 update ota. then i tryed rooting phone it all whent through Green Pass On Odin but Knox kept blocking SuperSu so i wasnt able to grant root permisions to any app. i then installed CWM Recovery and tryed to flash a custom rom it gave me a status 7 error so i did some research and i read on a thread that i had to update the bootloader. once i flashed the bootloader the phone just shut down and never came back on. I believe its hardbricked cant get into recovery or download mode, just a black screen and red led comes on when connected to charger with no battery And it connects to my pc as QHSUSB_DLOAD. If anybody has any idea what i can do to get my phone running again Please let me know asap
Your Efuse has blown after flashing another bootloader on top of the 4.3 bootloader. I seriously doubt you can recover. Try the De-Bricking Thread in Android Development sub forum.
Will the SD Card DeBricking Method work ?
Probably will. But if you have already flashed the 4.3 update you will probably have to use the 4.3 debrick.img.
Im going to give it a try, Do you know if a Class 10 SD Card Manditory
I know class 6 works. Not sure about lower but some have said no they won't work
DocHoliday77 said:
Probably will. But if you have already flashed the 4.3 update you will probably have to use the 4.3 debrick.img.
Click to expand...
Click to collapse
I went through the same tiresome process over the weekend after bricking my device. You need to use the 4.3 debrick image so that you can odin back to the TW 4.3. Make sure you remove the debrick SD after you get the download mode b4 you odin. Good luck
By any chance do you have a Link to the TW 4.3 i cant find it anywhere
ChinoSupreme23 said:
Ok so i bought a Galaxy S3 For tmobile, i installed the 4.3 update ota. then i tryed rooting phone it all whent through Green Pass On Odin but Knox kept blocking SuperSu so i wasnt able to grant root permisions to any app. i then installed CWM Recovery and tryed to flash a custom rom it gave me a status 7 error so i did some research and i read on a thread that i had to update the bootloader. once i flashed the bootloader the phone just shut down and never came back on. I believe its hardbricked cant get into recovery or download mode, just a black screen and red led comes on when connected to charger with no battery And it connects to my pc as QHSUSB_DLOAD. If anybody has any idea what i can do to get my phone running again Please let me know asap
Click to expand...
Click to collapse
Check this post, it may help http://forum.xda-developers.com/showthread.php?t=2439367
So i bought the Required Sd Card And did the Windows method but it didnt work still no respond, Does anybody know if the Linux/Ubuntu Method will fix it for sure?
So I did everything and copied the 4.3 debrick IMG to my sd card from Linux terminal but still no response when trying to boot the phone with the debrick sd card, the only type of response is when I insert the sd card and then insert the battery the camera flash blinks once really fast, that's about it
Sent from my iPhone using Tapatalk
DocHoliday77 said:
I know class 6 works. Not sure about lower but some have said no they won't work
Click to expand...
Click to collapse
{
"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"
}
would this one work ?
Sent from my iPhone using Tapatalk
ChinoSupreme23 said:
would this one work ?
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Yes it should work as it is 16 gb looking class 10
Sent from my SGH-T999 using XDA Premium 4 mobile app
I did everything and the phone doesn't do anything doesn't boot normally , in recovery or download mode, all it does is the camera flash blinks once really fast as soon as the battery makes contact with the pins other then that no response
Sent from my iPhone using Tapatalk
anil2653 said:
Yes it should work as it is 16 gb looking class 10
Sent from my SGH-T999 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I did everything and the phone doesn't do anything doesn't boot normally , in recovery or download mode, all it does is the camera flash blinks once really fast as soon as the battery makes contact with the pins other then that no response
Sent from my iPhone using Tapatalk
Are you using the 4.3 debrick.img?
DocHoliday77 said:
Are you using the 4.3 debrick.img?
Click to expand...
Click to collapse
Yes I am
Sent from my iPhone using Tapatalk
I hope I hope I hope yours isn't the same as mine!
Try redoing everything, but this time without formatting. Rewrite the image over the one already there.
DocHoliday77 said:
I hope I hope I hope yours isn't the same as mine!
Try redoing everything, but this time without formatting. Rewrite the image over the one already there.
Click to expand...
Click to collapse
Retry over and over on both Windows and Linux I'm about to give up
Sent from my iPhone using Tapatalk
I went through the exact same problem here.
When you set up the SD card, in Windows, make sure to use win32diskimager.
Next, I would advise that you take out the battery, put the SD card in, and then put the battery in.
At that point, the phone should boot by itself within 15 - 30 seconds. If not, try getting it into download mode (Home + Volume Down + Power for about 15 seconds).
If it doesn't boot, rewrite the debrick image and keep trying.
I also found this to be a huge help. Just make sure to use the T999 4.3 debrick image.
I followed the instructions listed here.
androidorigin. c o m /samsung-galaxy-note-4-root-how-to/
It did not work and I am now stuck on the screen that says "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again.
I tried Kies and it says it is not compatible.
Anyone have the stock rom or know of a way to get this root?
I am fairly tech savvy but this is my first time rooting.
travr6 said:
I followed the instructions listed here.
androidorigin. c o m /samsung-galaxy-note-4-root-how-to/
It did not work and I am now stuck on the screen that says "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again.
I tried Kies and it says it is not compatible.
Anyone have the stock rom or know of a way to get this root?
I am fairly tech savvy but this is my first time rooting.
Click to expand...
Click to collapse
There are no Roms or stock image files that I am aware of. When someone releases one or the other. Flash TWRP in Odin and flash new rom through TWRP or Odin stock image.
Sent from my SPH-L900 using XDA Free mobile app
http://shabbypenguin.com/?developer=Sprint_Note_4-trltespr&folder=Stock-NIE
^^^^ this guy just saved your ****!
Sent from my SPH-L900 using XDA Free mobile app
fatboypup said:
http://shabbypenguin.com/?developer=Sprint_Note_4-trltespr&folder=Stock-NIE
Click to expand...
Click to collapse
when you flash via odin, do you see the message 1 succeeded and 0 failed of do you see 0 for both?
Thanks but I think I figured it out.
I tried using 4 different versions of ODIN.
I also used different versions of the MD5 files.
I finally got one to stick and I appear to be rooted.
http://www.sammobile.com/firmwares/
{
"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"
}
travr6 said:
Thanks but I think I figured it out.
I tried using 4 different versions of ODIN.
I also used different versions of the MD5 files.
I finally got one to stick and I appear to be rooted.
Click to expand...
Click to collapse
Anyway you could share what you did and which links worked for you? Don't be greedy with detailed info! =)
TheTOBster87 said:
Anyway you could share what you did and which links worked for you? Don't be greedy with detailed info! =)
Click to expand...
Click to collapse
Just for everyone's info: the stock tar is located in the "general" section of this forum (Sprint galaxy note 4)... Easy to find.
Cf-auto-root is here:
http://forum.xda-developers.com/showthread.php?t=2897428
Instructions are in the OP.
Just odin the one you need for your purposes (stock tar or auto root) and your good to go (Phone must be in download mode of course).
jhill110 said:
Just for everyone's info: the stock tar is located in the "general" section of this forum (Sprint galaxy note 4)... Easy to find.
Cf-auto-root is here:
http://forum.xda-developers.com/showthread.php?t=2897428
Instructions are in the OP.
Just odin the one you need for your purposes (stock tar or auto root) and your good to go (Phone must be in download mode of course).
Click to expand...
Click to collapse
I already tried rooting before I found XDA, and now my Note 4 is bricked or soft bricked? idk. Can you or anyone provide the direct links to what I need to download?
http://androidromupdate.com/2015/03...axy-note-4-5-0-1-lollipop-stock-firmware-tar/
TheTOBster87 said:
View attachment 3330055
I already tried rooting before I found XDA, and now my Note 4 is bricked or soft bricked? idk. Can you or anyone provide the direct links to what I need to download?
Click to expand...
Click to collapse
Stock OB7 tar here:
http://forum.xda-developers.com/showthread.php?t=3056478
Use Odin to flash it. If you can boot to custom recovery now... Do it and wipe everything but internal & external storage first x 3.
Then:
Odin Cf-auto-root as in my prior post
Then:
TWRP Recovery here:
https://twrp.me/
Use Odin to flash it. You WILL be good to go.
Now re-setup your phone.
Hard Bricked Note 4 Sprint
I have a hard Bricked note 4 from sprint that just landed in my possession. Phone appears dead but when I plug into the computer i get the Qualcomm driver not found. Wondering if anyone can point me to a solution. Thank you of course in aadvance.
gamethriller said:
I have a hard Bricked note 4 from sprint that just landed in my possession. Phone appears dead but when I plug into the computer i get the Qualcomm driver not found. Wondering if anyone can point me to a solution. Thank you of course in aadvance.
Click to expand...
Click to collapse
If you can get into download mode (volume down, home button & power button at the same time) then go to this link, read the OP carefully, follow the instructions and and you should be ok.
http://forum.xda-developers.com/showthread.php?t=3176288
jhill110 said:
If you can get into download mode (volume down, home button & power button at the same time) then go to this link, read the OP carefully, follow the instructions and and you should be ok.
http://forum.xda-developers.com/showthread.php?t=3176288
Click to expand...
Click to collapse
Ok guys Ive tried every post I can find on getting TWRP on my phone. I have the latest Odin3 v3.10.6.exe, the latest TWRP, twrp-2.8.7.0-trltespr.img.tar and tried, openrecovery-twrp-2.8.5.0-trltespr.img.tar, I have followed the posts and pulled the usb, then the battery for 30 seconds. I have unchecked the auto reboot, left it checked, tried it in the AP and BL slots and I cant get a custom recovery to stick. Here is the stats on my phone, Im at my wits end with this any help or suggestions would be much grateful. Ive already bricked it with cf autoroot and reinstalled the stock rom. Im wondering if I shouldn't of let it auto activate? Does sprint have a kill mode now for TWRP?
Software Version, N910PVPU4COG5
HARDWARE VERSION N90P.O5
ANDROID VERSION 5.1.1
BASEBAND VERSION SAME AS SOFTWARE VERSION
KERNEL VERSION
3.10.40-530320
DPI!SWHE8820 #1
BUILD NUBMER
LMY47X.N910PVPU4COG5
SECURITY SOFTWARE VERSION
MDF V2.0 RELEASE 1
VPN V1.4 RELEASE 5.2
KNOX VERSION
KNOX 2.4.1
Where am I missing it???
jhill110 said:
If you can get into download mode (volume down, home button & power button at the same time) then go to this link, read the OP carefully, follow the instructions and and you should be ok.
http://forum.xda-developers.com/showthread.php?t=3176288
Click to expand...
Click to collapse
No the phone won't get into anything or show anything. It's hard Bricked not soft bricked.
Johniex said:
Ok guys Ive tried every post I can find on getting TWRP on my phone. I have the latest Odin3 v3.10.6.exe, the latest TWRP, twrp-2.8.7.0-trltespr.img.tar and tried, openrecovery-twrp-2.8.5.0-trltespr.img.tar, I have followed the posts and pulled the usb, then the battery for 30 seconds. I have unchecked the auto reboot, left it checked, tried it in the AP and BL slots and I cant get a custom recovery to stick. Here is the stats on my phone, Im at my wits end with this any help or suggestions would be much grateful. Ive already bricked it with cf autoroot and reinstalled the stock rom. Im wondering if I shouldn't of let it auto activate? Does sprint have a kill mode now for TWRP?
Click to expand...
Click to collapse
Ok, how exactly did you get to 5.1.1? OTA?
Would someone mind helping me out, I cant use my phone any more. The last thing I did was install Emotion OS and then I installed the Emotion Kernel, upon reboot the phone was stuck on the emotion boot screen after restarting the phone Im not sure how it happened however the phone went from TWRP to some recovery that looks like the lineageos logo, I cant install any updates from this recovery and my phone via USB in download mode or ADB is not detected by any computer I have tried 3 computers in my house. I have never seen this recovery screen and I do not know what to do. I downloaded a stock MM firmware and converted it to a zip file from a tutorial on here however I keep getting an error message from this recovery. I really need my phone back up and running Im not sure what the heck happened.
Continued from other posts
Quote:
Originally Posted by shadeau
Do you have any options in recovery? Even if you could perform a "factory reset" with lineage OS you'd at least be able to enable ADB and reinstall TWRP. Also, when you say that the phone isn't recognized by the computer does that mean ADB, ODIN, and your OS don't recognize the phone?
So I do have options in this Lineage Recover but I cant get anything to work, Here are my options Reboot System Now, Apply Update, Factory Reset, Advanced. I have already tried factory reset however I may have deleted the OS all together with the Wipe Data Option. When I reboot the phone it stays on the the Samsung Galaxy Note 4 Screen with the little padlock that shows my bootloader is unlocked. I was messing around with flashing betwen several roms, I went from CM 14.1 to Lineage to Emotion OS, I then flashed the emotion kernel. If I select Apply update it gives me these several options, Apply from ADB choose from emulated (no typo) choose from sdcard1. I have tried to sideload via adb shell and my pc ( have tried multiple computers) does not detect the device. I even went to the extent of reinstalling windows and all Samsung USB and ADB drivers. Selecting choose from sdcard1 I can see the various zip files on my sd card however when it goes to install any roms it fails and just says error. There is a error log however it will not let me view these. My phone before this stopped connecting to any pc's I could plug the phone in via usb and it would charge but I would not get any notifications from windows! I will seriously send money to who ever can hlep me out I do not want to shell out for a new phone. Placing the phone in download mode still works however odin will not detect the phone either lol what the heck is going on here. I do have a micro sd card reader for the mc so i can place files on the phones card but I dont know what kind of file this recovery is looking for. I do not know how this recovery even got on here as I have been using TWRP from the very beginning. Please help me
I have never seen this recovery it has the lineage os logo and just says RECOVERY. I wish I could take a picture of the screen.
I have also tried renaming files on my sd card as update.zip and this does not help. It comes back with an error every time.
ziggsta2 said:
I have also tried renaming files on my sd card as update.zip and this does not help. It comes back with an error every time.
Click to expand...
Click to collapse
Are you using the Samsung OEM USB cord?
quinciebee said:
Are you using the Samsung OEM USB cord?
Click to expand...
Click to collapse
good questions will try another usb cable all I have is 1 for right now
quinciebee said:
Are you using the Samsung OEM USB cord?
Click to expand...
Click to collapse
Do you know what recovery this is? It has the lineage symbol! I cant find a picture of it any where if someone knew what recovery it was maybe then I could research info from the name
ziggsta2 said:
Do you know what recovery this is? It has the lineage symbol! I cant find a picture of it any where if someone knew what recovery it was maybe then I could research info from the name
Click to expand...
Click to collapse
It sounds likes it's the default factory recovery, you probably lost TWRP when you flashed the rom. When Odin recognizes your phone again, just Odin TWRP in there through download mode and you should be good to go.
quinciebee said:
It sounds likes it's the default factory recovery, you probably lost TWRP when you flashed the rom. When Odin recognizes your phone again, just Odin TWRP in there through download mode and you should be good to go.
Click to expand...
Click to collapse
When I plug my phone into a USB port I get a grey battery icon however it doesn't appear that its doing anything, is it possible I have a bad usb port on my phone? Odin wont recognize it, I have yet to find a single computer to see my phone, and I have now tried multiple USB cables.
ziggsta2 said:
When I plug my phone into a USB port I get a grey battery icon however it doesn't appear that its doing anything, is it possible I have a bad usb port on my phone? Odin wont recognize it, I have yet to find a single computer to see my phone, and I have now tried multiple USB cables.
Click to expand...
Click to collapse
Try unplugging your phone completely, pull the battery, boot into download mode, then plug it into your computer using the Samsung USB cord.
quinciebee said:
Try unplugging your phone completely, pull the battery, boot into download mode, then plug it into your computer using the Samsung USB cord.
Click to expand...
Click to collapse
I wish that was the fix, I have tried everything at this point, for the life of me i cannot get any pc to recognize this phone. If I could get odin to detect the phone I would be all set
ziggsta2 said:
I wish that was the fix, I have tried everything at this point, for the life of me i cannot get any pc to recognize this phone. If I could get odin to detect the phone I would be all set
Click to expand...
Click to collapse
CHECK THIS OUT People are having the same issues
https://forum.xda-developers.com/android/help/phone-stuck-bootloop-t3510266
{
"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"
}
ziggsta2 said:
Click to expand...
Click to collapse
In the advanced menu is there an option to "mount system" or something? Also see if there's a setting in there for chmod
I actually ordered a new note 4 I believe my device is dead I will have to charge it as when I try to boot into recovery the words no command flash very quickly on the bottom of the screen, I do know I saw mount system I remember trying it and it didn't do anything but I will charge it tonight and try it. I have read about the nexus 6p and how 7.1.1 has bricked alot of devices, do you think upgrading to Emotion Os 7.1 was the culprit?
ziggsta2 said:
I actually ordered a new note 4 I believe my device is dead I will have to charge it as when I try to boot into recovery the words no command flash very quickly on the bottom of the screen, I do know I saw mount system I remember trying it and it didn't do anything but I will charge it tonight and try it. I have read about the nexus 6p and how 7.1.1 has bricked alot of devices, do you think upgrading to Emotion Os 7.1 was the culprit?
Click to expand...
Click to collapse
I just tried EmotionOS over the weekend and had no issues so I'm not sure that's the culprit. I think you accidentally flashed something into the recovery partition that broke it. Another possibility is that the latest EmotionOS build is specifically designed for the custom TWRP that @hsbadr made. I used that to flash EmotionOS then returned to stock TWRP to flash a different ROM.
shadeau said:
I just tried EmotionOS over the weekend and had no issues so I'm not sure that's the culprit. I think you accidentally flashed something into the recovery partition that broke it. Another possibility is that the latest EmotionOS build is specifically designed for the custom TWRP that @hsbadr made. I used that to flash EmotionOS then returned to stock TWRP to flash a different ROM.
Click to expand...
Click to collapse
You know what you might be right I don't remember ever changing TWRP, what is weird is that I lost all usb connectivity too a point that could be due to a damaged usb port, too many unknowns at this point. It was a little embarrassing in the household when I had to admit that I bricked my phone. I was asked if I was going to mess with my new phone......I will have it rooted and unlocked TONIGHT lol
ziggsta2 said:
You know what you might be right I don't remember ever changing TWRP, what is weird is that I lost all usb connectivity too a point that could be due to a damaged usb port, too many unknowns at this point. It was a little embarrassing in the household when I had to admit that I bricked my phone. I was asked if I was going to mess with my new phone......I will have it rooted and unlocked TONIGHT lol
Click to expand...
Click to collapse
Well, good luck! Send me a PM if you have trouble finding the links to unlocking and rooting.
Ha I got there too man . pretty cool recovery wish I wouldn't have fixed it so fast might try duplicate your accident. OK its an easy fix just flash twrp in Odin for our device then boot back into twrp and do a complete wipe (might not be possible if u can't see sdcard if that is case wipe data system cache art/cache then install then wipe the internal after ROM flash . at this point I would factory reset and backup but hey that's me . anyway should be fine from here. BTW did you select the DL recovery option in dev options? I was wondering if that's how I got there the (lineage recovery) the first time. Lol your post made me want to check it out. Omg bud i almost forgot and this is crucial. Aosp ROMs like emotion take a long long time to boot the first time(damn near 15 mins) ! The last thing you want to do is mistake this for a bootloop
mojoswagger1980 said:
Ha I got there too man . pretty cool recovery wish I wouldn't have fixed it so fast might try duplicate your accident. OK its an easy fix just flash twrp in Odin for our device then boot back into twrp and do a complete wipe (might not be possible if u can't see sdcard if that is case wipe data system cache art/cache then install then wipe the internal after ROM flash . at this point I would factory reset and backup but hey that's me . anyway should be fine from here. BTW did you select the DL recovery option in dev options? I was wondering if that's how I got there the (lineage recovery) the first time. Lol your post made me want to check it out. Omg bud i almost forgot and this is crucial. Aosp ROMs like emotion take a long long time to boot the first time(damn near 15 mins) ! The last thing you want to do is mistake this for a bootloop
Click to expand...
Click to collapse
Ouch ! I kinda failed to take into account the very real possibility the ROM you wished to flash might not be on your device and you may have no means to get it there.....in which case flash twrp then you need (if you don't want relock bootloader) to flash a system only image . vague I know I'm thinking .....bottom line is whatever you flash cannot contain aboot image or you will relock boot loader. If on 6.0.1 boot loader there is a safeupgrade to the most recent firmware that won't relock if on 5.1.1 (bpa1 ) idk if there is one . I think there is . in fact I'm sure there is hsbrad made Odin flashable IMG for all Verizon note 4 firmware broth dev and retail . look under his profile on XDA should link you to it
ziggsta2 said:
Do you know what recovery this is? It has the lineage symbol! I cant find a picture of it any where if someone knew what recovery it was maybe then I could research info from the name
Click to expand...
Click to collapse
That is the lineage os recovery it comes in every build, you must have hit update recovery in the developer options of the settings menu. You just need to reflash twrp like you did when you unlocked your bootloader.
weard1212 said:
That is the lineage os recovery it comes in every build, you must have hit update recovery in the developer options of the settings menu. You just need to reflash twrp like you did when you unlocked your bootloader.
Click to expand...
Click to collapse
Yeah ty I went ahead and tried last night cause I was bored ....meh lack luster . oh and I did it intentionally and just restored recovery with flashify and I just realized this probably wasn't directed at me but yep lineage
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).