Related
Title says all, i have an att SGH-I747 and i tried to install a custom rom without the phone being rooted (didnt know that was a requirement) and the original stock was 4.3 and i was trying to get it to 4.1 . after doing extensive research ive tried countless different files and such to restock the phone but nothing has helped because on odin, when i hit start, it goes unsuccessful to do auth being bad or something like that. so if someone wants to help a fellow brother out please dont hesitate. add me on skype godlypk101
Can you get into download mode or recovery?
FYI: if you were on stock 4.3 bootloader, trying to get back to stock 4.1.1 can brick your phone.
yes i can
Here's what I would do to at least get a working ROM on the phone:
1) copy the latest version of d2lte cm11 to your external SD card: https://download.cyanogenmod.org/?device=d2lte;
2) flash the latest tar.md5 version of Philz Touch from here: https://goo.im/devs/philz_touch/CWM_...Edition/d2lte/ in the PDA box of Odin;
3) reboot to recovery and flash CM11.
ok, now what if i dont have an ext sd card :S
You had the stock 4.3 ROM on your phone before attempting to downgrade to 4.1.1, correct?
If that's the case, this may help: http://forum.xda-developers.com/showthread.php?t=2722660
yes, will try that method to see if it fixes anything.
in that pack theres 5 files and they start with, AP, BL, CP, CSC, D2 (Pit) where i put these on odin?
UPDATE: Put all the files in the correct spot, started the fix in odin and lets hope it works
ok so now that the phone is working, what are the steps im supposed to take in order to unlock this bad boy? should i refer to a method on xda on custom roms or should i go buy a code from a third party website?
So your phone booted on stock 4.3?
If the phone ever had the 4.3 bootloader, you cannot unlock the phone for free. You will have to purchase an unlock code.
I haven't tried but I think of your rooted then use cm boot loader then mount all partition and wipe then use cm to load new or old system. Think of it like a pc format then install. Simple
I was on CM 10.2.1
I upgraded to CM11 - I get no wireless data. My phone works but I have no APNs and I could not add them.
I tried SlimKat 9.0 same issue with the APN
I upgraded my CWM to 6.4.0.7 as I heard that caused issues when upgrading to CM11.
I bought Mobile Odin and flashed that way as I thought it might help.
Ive done the following to fix my APN
1) Loaded an old one from working CM 10.2.1
2) Run Root Tweak with the fix APN for CM11 checked
3) Done the airplane mode trick
4) Attempt to add one manually
Does anyone know why this is happening and more importantly how to correct this issue?
Yes I did pore through other threads on how to fix this but no avail.
Thank you
What is your bootloader and modem? Do you get data if you re-install your previous ROM?
audit13 said:
What is your bootloader and modem? Do you get data if you re-install your previous ROM?
Click to expand...
Click to collapse
Bootloader = I747UCDLK3
Modem = I747UCDLK3
Yes I get data when I load a backup of CM 10.2.1
Thanks
Data does not work on ROMs beyond cm10.2 because your bootloader and modem to too old.
I recommend flashing back to stock 4.1.1, sim unlock your phone if it is not already sim unlocked, and run OTA updates to at least 4.3, then install recovery and CM11.
audit13 said:
Data does not work on ROMs beyond cm10.2 because your bootloader and modem to too old.
I recommend flashing back to stock 4.1.1, sim unlock your phone if it is not already sim unlocked, and run OTA updates to at least 4.3, then install recovery and CM11.
Click to expand...
Click to collapse
Thanks for the quick reply. That sounds hard. From what I'm reading going back is treacherous.
So these are the steps.
1. Load this firmware via ODIN -> I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.zip -- What about gapps? Is that in this zip?
2. Run triangle away. (Do I need to do this?)
3. Contact my carrier to unlock my sim. (If this is carrier unlocking ie taking my att phone to Sprint etc, why is this needed?)
4. Get OTA updates. Will this come automagically because I'm on 4.1.1 and does it matter if my flash counter is gt 1?
5. Root phone via Odin with this file CF-Auto-Root-d2att-d2uc-samsungsghi747.tar.md5.
6. Install CWM if it went away when I went back to firmware - Of course it would because I'll factory reset my phone in step 1.
7. Flash away to a 4.4.4 Rom
Did I miss anything?
Step 4 is the one that scares me -- That one is out of my control. Either I get the OTA or I dont. Anyway I can "request" the OTA?
Thanks again
Be Well
From your custom ROM, run triangle away to reset counter and change things back to official.
Now flash back to stock 4.1.1 using Odin. If your phone does not boot, you need to get into recovery, do a factory reset, and reboot the phone and go through the set up routine.
After loading stock 4.1.1, do this to sim unlock your phone for free: http://forum.xda-developers.com/showthread.php?t=2529200. If you have a code from ATT, you must be running a stock ROM or a custom ROM that is based on a stock Samsung ROM in order to enter the unlock code.
You must be on a stock ROM in order to take OTA updates. OTA updates are the safest way to obtain an updated bootloader and modem.
After updating to 4.3, you cannot downgrade the bootloader as doing so may brick the phone.
The choice is yours in terms of what you want to do. As you found out, some ROMs will not function properly without an updated bootloader and modem. Mixing modem and bootloader versions may also result in a bricked phone.
audit13 said:
From your custom ROM, run triangle away to reset counter and change things back to official.
Now flash back to stock 4.1.1 using Odin. If your phone does not boot, you need to get into recovery, do a factory reset, and reboot the phone and go through the set up routine.
After loading stock 4.1.1, do this to sim unlock your phone for free: http://forum.xda-developers.com/showthread.php?t=2529200. If you have a code from ATT, you must be running a stock ROM or a custom ROM that is based on a stock Samsung ROM in order to enter the unlock code.
You must be on a stock ROM in order to take OTA updates. OTA updates are the safest way to obtain an updated bootloader and modem.
After updating to 4.3, you cannot downgrade the bootloader as doing so may brick the phone.
The choice is yours in terms of what you want to do. As you found out, some ROMs will not function properly without an updated bootloader and modem. Mixing modem and bootloader versions may also result in a bricked phone.
Click to expand...
Click to collapse
To stick with 10.2 or not to that is the question. Everytime I flash or do anything like this on my phone - I get a small lump in my throat knowing I'm dancing in the razors edge of bricking it.
I know how you feel, but I've done it enough times and just accept the fact that I may brick the phone. Jtag service would cost me around $75 so I'm willing to take the chance. I'd be less willing if the phone still has warranty.
Flashing back to stock and running OTA updates is the safest route.
If you don't sim unlock while on stock 4.1.1 and you want to sim unlock your phone in the future, you will need to be on a stock or virtually stock ROM in order to enter the unlock code.
Used ODIN to go back to stock 4.1.1.
Got the OTA update to 4.3
I have my MMS and cellular data back
I'll stick on stock, unrooted 4.3 for a minute.
I should be available to root and update to CM11 or SlimKat or any 4.4 rom whenever I so desire and still keep cellular data.
My baseband is I747UCUEMJB. How can I find out my bootloader and modem versions on UNROOTED device?
Your help is much appreciated and your instructions were flawless.
ddunleavy2 said:
Used ODIN to go back to stock 4.1.1.
Got the OTA update to 4.3
I have my MMS and cellular data back
I'll stick on stock, unrooted 4.3 for a minute.
I should be available to root and update to CM11 or SlimKat or any 4.4 rom whenever I so desire and still keep cellular data.
My baseband is I747UCUEMJB. How can I find out my bootloader and modem versions on UNROOTED device?
Your help is much appreciated and your instructions were flawless.
Click to expand...
Click to collapse
In a terminal or adb shell you can enter this to check your bootloader:
Code:
getprop ro.bootloader
In a terminal or adb shell you can enter this to check your modem (should match the baseband your phone reports in About):
Code:
getprop gsm.version.baseband
I don't believe either of these commands require root unless stock has getprop locked down tighter that AOSP ROMs; I just entered them in a user shell.
There are a couple of firmware updates for your device beyond MJB, NE4 and NJ1. Some users, myself included, had GPS problems that were a bit of a pain to fix on newer 4.4 AOSP based ROMs with the MJB firmware, but data was ok with MJB. Also, you'll need newer firmware if you decide to test drive the lollipop alphas that are floating around. There are custom recovery flashable firmware updates on XDA from a trusted developer if you decide you need that, or you might want to take a couple more OTAs if you're more comfortable going that route. You're already on MJB so there's no going back
The terminal worked
Bootloader and baseband = I747UCUEMJB
What???? I might need more updates for all the roms out there.....ugggh.
"There are custom recovery flashable firmware updates on XDA from a trusted developer if you decide you need that, or you might want to take a couple more OTAs if you're more comfortable going that route."
If I decide to use these flashable firmware updates on XDA from a trusted developer or OTA its same as this: going forward and NEVER going backward when getting firmware updates?, yes?
yes. downgrading bootloader will almost certainly cause a brick.
"all i can really do , is stay out of my own way and let the will of heaven be done"
---------- Post added at 10:09 PM ---------- Previous post was at 10:07 PM ----------
audit13 said:
Data does not work on ROMs beyond cm10.2 because your bootloader and modem to too old.
I recommend flashing back to stock 4.1.1, sim unlock your phone if it is not already sim unlocked, and run OTA updates to at least 4.3, then install recovery and CM11.
Click to expand...
Click to collapse
+1
"all i can really do , is stay out of my own way and let the will of heaven be done"
You guys are on point.
Last night I received another OTA to 4.4.2.
Baseband now at NE4.
Thanks again for taking the time to answer all this -- Really really appreciate it.
EDIT: Can I still use this to root my phone via ODIN or is there a different process for this baseband?
CF-Auto-Root-d2att-d2uc-samsungsghi747.tar.md5
I load this into ODIN, plug my phone in download mode and root away. Does either the file I use change or do I have to use something other than ODIN?
Thanks again
To get root, I would flash a custom recovery and flash supersu from recovery, then let supersu disable know.
The file you named looks to be outdated as it refers to the s3 as d2att. Since unified builds were released, the s3 is now referred to as the d2lte.
I have ROM Manager installed. It has an option to "Flash Clockworkmod Recovery". I just tried it and it failed and I think thats because I dont have root. In the past I've had to root my phone via ODIN, then flash custom recovery then MOD away.
In the past I rooted the S3 via ODIN. With this new 4.4.2 version do I still root via ODIN provide I find the correct file because -> CF-Auto-Root-d2att-d2uc-samsungsghi747.tar.md5 this one is probably for a 4.1.1 version phone?
I would not flash anything for the d2att at this point.
Try this:
Download the latest tar.md5 file from here: https://goo.im/devs/philz_touch/CWM_...Edition/d2lte/
Download supersu zip from here and place it onto an external SD card or copy it to the phone's internal storage: http://download.chainfire.eu/695/SuperSU/
In Odin, uncheck everything except f.reset time. Flash Philz. When you see reset in the status window, remove USB cable, pull battery, replace battery, boot into recovery, flash supersu, reboot.
I am fairly certain that AOSP, or at least CM, de-unified in the past few months. Not that it matters much, other than for the confusion it causes.
i've samsung note 4 sm-n910p
was working fine ,tried to install firmware but got bricked
i've tried downloading many firmwares all fail
need someone to send the right firmware for my device
attached the error i get
thanks
And here we go again...... What version software was installed before trying to update? Were you rooted?
zjor2000 said:
i've samsung note 4 sm-n910p
was working fine ,tried to install firmware but got bricked
i've tried downloading many firmwares all fail
thanks
Click to expand...
Click to collapse
Try Flashing CF Auto Root through Odin and reboot your phone and report back please.
w7excursion said:
And here we go again...... What version software was installed before trying to update? Were you rooted?
Click to expand...
Click to collapse
Lol, ikr....
done so ,,but nothing keeps restarting ,,,,loop
it needs a new firmware .. OS
zjor2000 said:
done so ,,but nothing keeps restarting ,,,,loop
it needs a new firmware .. OS
Click to expand...
Click to collapse
Were you on the OG5 OTA and tried to root your phone?
rooted thru odin
now i can't get to OS ,just show samsung sign and loops
Flash whatever firmware u was on in odin
zjor2000 said:
rooted thru odin
now i can't get to OS ,just show samsung sign and loops
Click to expand...
Click to collapse
In Odin, Flash the TWRP recovery
Download notarized,cm12 or sacs and put it on your SD card, and reboot to recovery and install your choice of Rom downloaded.
Reboot and relax.
tried to do thru sd card ,but i get :
dm-verity verification failed
can i just go back to 5.1 lollipop with an official stock rom via odin ?
zjor2000 said:
can i just go back to 5.1 lollipop with an official stock rom via odin ?
Click to expand...
Click to collapse
There is no official rom
any firmware can get me back to lollipop with odin !!!
zjor2000 said:
any firmware can get me back to lollipop with odin !!!
Click to expand...
Click to collapse
Here's what I understand as far as recovering with Odin by build:
All these builds NIE, NK2 (KitKat) and first Lollipop (OB7) were downgradeable; you were free to flash in Odin within these builds. Or KIES but not downgrade.
OE1 didn't have a tar, it also locked out the older ones but was compatible with OF5 to flash Odin or KIES to upgrade. Can only go back to OE1 with nandroid backup from OF5. OE1 introduced reactivation lock to prevent flashing over user locked phone as well as preventing the downgrade to escape the feature. Seems dine could recover from a bit loop by flashing CF Auto Root in Odin.
OF5 was released with a supporting tar eventually but it's the same story as OE1. But I'm not sure if CF Auto Root worked to recover boot when looped.
OG5 locks it further. If you don't have a nandroid, recovering from boot loop options may include flashing CWM recovery or a compatible flash that takes you away from OG5 almost entirely. Sacs, Notarized, and CM12 are reportedly working. Reportedly, can't go back to OF5 with Odin and not sure about nandroid, maybe not.
Depending on certain exceptions unclear, Odin and KIES have been reported to work together, flashing stock OB7 ROM, parts of stock tar with Odin with a flash result that won't boot but connecting KIES in recovery and using the emergency recovery method. If KIES doesn't see your phone on recovery, you may try this fix on your Windows PC:
http://forum.xda-developers.com/showpost.php?p=34864154&postcount=14
I'll add this too: flashing L Speed Mod may fix adb with ADB Insecure in booted mode; ADB Insecure wouldn't be needed in recovery anyway so it works without it. I can report this does work for me with the above MTP fix on OB7.
Sent from my SM-N910P using Tapatalk
samep said:
Here's what I understand as far as recovering with Odin by build:
All these builds NIE, NK2 (KitKat) and first Lollipop (OB7) were downgradeable; you were free to flash in Odin within these builds. Or KIES but not downgrade.
OE1 didn't have a tar, it also locked out the older ones but was compatible with OF5 to flash Odin or KIES to upgrade. Can only go back to OE1 with nandroid backup from OF5. OE1 introduced reactivation lock to prevent flashing over user locked phone as well as preventing the downgrade to escape the feature. Seems dine could recover from a bit loop by flashing CF Auto Root in Odin.
OF5 was released with a supporting tar eventually but it's the same story as OE1. But I'm not sure if CF Auto Root worked to recover boot when looped.
OF5 locks it further. If you don't have a nandroid, recovering from boot loop options may include flashing CWM recovery or a compatible flash that takes you away from OG5 almost entirely. Sacs, Notarized, and CM12 are reportedly working. Reportedly, can't go back to OF5 with Odin and not sure about nandroid, maybe not.
Depending on certain exceptions unclear, Odin and KIES have been reported to work together, flashing parts of stock tar with Odin and connecting KIES using the emergency recovery method. If KIES doesn't see your phone on recovery, you may try this fix on your Windows PC:
http://forum.xda-developers.com/showpost.php?p=34864154&postcount=14
I'll add this too: flashing L Speed Mod may fix adb with ADB Insecure in booted mode; ADB Insecure wouldn't be needed in recovery anyway so it works without it. I can report this does work for me with the above MTP fix on OB7.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Was i incorrect in my method of getting him back on his feet? I should suggest CWM instead of TWRP? Now im confused.
The last thing i want to do is tell someone the wrong procedure, only causing more frustration. I thought i read 'Twrp, Install and Viola!' from many users in the other thread.
xxSTARBUCKSxx said:
Was i incorrect in my method of getting him back on his feet? I should suggest CWM instead of TWRP? Now im confused.
The last thing i want to do is tell someone the wrong procedure, only causing more frustration. I thought i read 'Twrp, Install and Viola!' from many users in the other thread.
Click to expand...
Click to collapse
I think your suggestion is consistent with what we're learning as you gave it. It seems to be evolving with trial and error. The CWM suggestion came from a single experience shared.
http://forum.xda-developers.com/showthread.php?p=62196189
The OP was asking for another solution and it wasn't clear where he started from to correctly recovery so tried to answer including all the options for each build. I added some things that may help depending on his situation.
Sent from my SM-N910P using Tapatalk
i managed to find the right fW ,,,if anyone has same problem u can do it your self
https://1fichier.com/dir/IOjXgJUa
and download this file : N910PVPU3BOF5_SPT3BOF5_SPR_Sprint_USA_5.0.1.zip
I have Pac Rom Android 5.1.1 installed on my rooted sg3 and I need to do a carrier unlock. I contacted ATT to get the unlock code and the code they provided didn't work. Now I want to downgrade to Android 4.1 and try the UMTS menu trick as described here http://forum.xda-developers.com/showthread.php?t=2176719
I have tried Odin many times (with many versions, different computers, USB cables, etc) and every time Odin fails to flash Android 4.1. with a Fail AUTH error. I have used Odin successfully in the past many times with this phone but am unable to get it to work this time around.
Does anyone know how to downgrade the sg3 from 5.1.1 to 4.1? Or even better does anyone how to carrier unlock the sg3 when it has 5.1.1 installed on it?
Thanks!
Odin is probably failing because you have a 4.3 or 4.4.2 bootloader on your phone. I recommend you not flash anymore ROMs using Odin as repeat attempts to flash the 4.1.1 ROM via Odin may hard brick the phone.
Once a phone is running and 4.3 or 4.4.2 bootloader, you cannot use the free/hidden menu method to unlock the phone.
You cannot use a custom ROM to enter an unlock code. You'll have to go back to a stock ROM, enter the code, and return to a custom ROM.
Thanks for the reply. Do you know how I can go back to stock 4.1.1 without using Odin?
You need the 4.1.1 bootloader in order to use the free method. Once a phone is on 4.3 bootloader or higher, you can't go back to 4.1.1. Don't try because attempts to do so could brick the phone.
A stock 4.1.1 rom on a 4.3 bootloader will not work.
So you're saying once the sg3 is on a version above 4.3 there is no way to go back to 4.1.1?
slipnslider said:
So you're saying once the sg3 is on a version above 4.3 there is no way to go back to 4.1.1?
Click to expand...
Click to collapse
Once it is on the 4.3 or higher bootloader, there is no going back to an older bootloader and it is the older 4.1.1 bootloader and stock 4.1.1 ROM that is required to unlock using the free method.
Since you have the code, you can flash a stock ROM from recovery.
audit13 said:
Once it is on the 4.3 or higher bootloader, there is no going back to an older bootloader and it is the older 4.1.1 bootloader and stock 4.1.1 ROM that is required to unlock using the free method.
Since you have the code, you can flash a stock ROM from recovery.
Click to expand...
Click to collapse
Thanks. What do you mean by free method?
Also you suggesting if I put the 4.1.1 stock rom .zip on my sg3 I can flash it via CWM just like I would the latest 5.1.1 Pac Rom release?
The free method is the method you linked in your original post. This is the only free method available and it requires a 4.1.1 bootloader that your phone doesn't have. Installing 4.1.1 via cwm is not going to help you unlock it.
Since you have the code, you can flash a stock ROM from recovery.
Click to expand...
Click to collapse
How would I do this? Do I just flash 4.1.1 from cwm?
Flashing 4.1.1 onto your phone will not allow you to enter the code.
Before flashing anything, you need to verify the bootloader that is running on your phone. Until you do that, I would not flash any bootloaders or modems. An incompatible modem/bootloader combination can also brick your phone.
Sorry, one last question.
You'll have to go back to a stock ROM, enter the code, and return to a custom ROM.
Click to expand...
Click to collapse
How can I go back to the stock rom?
You can flash a stock rom from the general thread using twrp or cwm.
Awesome, thanks again. I was worried about going that route since I'm on 5.1.1 but I'll give it a shot
slipnslider said:
Awesome, thanks again. I was worried about going that route since I'm on 5.1.1 but I'll give it a shot
Click to expand...
Click to collapse
When you pick a stock ROM, make sure you pick one with the same bootloader and modem that are currently on your device. You probably have either the NE4 or NJ1 bootloader and modem pair. You DO NOT have a 5.1.1 bootloader and modem, they do not exist for the SGS3. Check your versions from a Terminal Emulator app or check them with the Phone Info - Samsung - app from the PlayStore.
Both NE4 and NJ1 stock ROMs are available in the forum. enewman17 posted them form image dumps, they have been used successfully by many.
The Terminal Emulator commands are:
Code:
getprop ro.bootloader
getprop | grep version.baseband
Thanks, I did this and both the bootloader and modem ended with NJ1 so I downloaded UCUFNJ1_Rooted.zip from enewman17's thread using CWM 6.0.4. The flash was successful but now the phone is frozen at the AT&T logo when I turn it on.
Any thoughts as to why its stuck booting up?
slipnslider said:
Thanks, I did this and both the bootloader and modem ended with NJ1 so I downloaded UCUFNJ1_Rooted.zip from enewman17's thread using CWM 6.0.4. The flash was successful but now the phone is frozen at the AT&T logo when I turn it on.
Any thoughts as to why its stuck booting up?
Click to expand...
Click to collapse
More than once I have seen reports of this happening when going from a 5.x.x ROM back to 4.4.x. The most common solution has been to include formating the internal sdcard before flashing the stock ROM.
If I flash the sd card as well I will lose the UCUFNJ1_Rooted.zip file. So in that case should I use adb via CWM to flash it?
slipnslider said:
If I flash the sd card as well I will lose the UCUFNJ1_Rooted.zip file. So in that case should I use adb via CWM to flash it?
Click to expand...
Click to collapse
Put the zip file on the external sdcard and then flash it with your recovery.
I actually didn't have an external SD card. I wound up taking it to the ATT store that had an ATT repair shop inside it and they reset it back to stock 4.4 for me and now everything works great! After unlocking the carrier on the phone I did have to manually enter the t-mobile APN to get the data connection working but that was simple (the info is listed on t-mobile's site)
slipnslider said:
I actually didn't have an external SD card. I wound up taking it to the ATT store that had an ATT repair shop inside it and they reset it back to stock 4.4 for me and now everything works great! After unlocking the carrier on the phone I did have to manually enter the t-mobile APN to get the data connection working but that was simple (the info is listed on t-mobile's site)
Click to expand...
Click to collapse
Glad to see you are up and running. Also glad to hear the AT&T guys helped out.
I was on one of the latest versions of MM, I was trying to downgrade to 5.1.1. When i tried flashing the 5.1.1 it put me in a fail that i cant get back to 6.0.1. The only .tar i could get to flash is the combination flash that is for troubleshooting all sensors and hardware, I cant get twrp, or any other stock 6.0.1 images to flash back on it without fail on Odin 3.12.3. If anyone has any ideas how to proceed from this purgatory much appreciated.
It's back!
After being very persistent with not being able to flash anything but the combination firmware stock binary, I switched to usb port on back of computer, went backward to Odin 3.9.?, flashed an early MM firmware successfully with the help of a Pit file being flashed with stock firmware. Had recurring fails saying ext4 fail. PIT file fixed that. Back to square 1 now. Was on the latest MM,now on Jun 2016 release of MM. Still hoping to unlock bl and root .
Stowincold said:
After being very persistent with not being able to flash anything but the combination firmware stock binary, I switched to usb port on back of computer, went backward to Odin 3.9.?, flashed an early MM firmware successfully with the help of a Pit file being flashed with stock firmware. Had recurring fails saying ext4 fail. PIT file fixed that. Back to square 1 now. Was on the latest MM,now on Jun 2016 release of MM. Still hoping to unlock bl and root .
Click to expand...
Click to collapse
If your bootloader is locked again I think you're going to have to Odin back to BPA1 and do the bootloader unlock process twice again to get back to MM with unlocked bootloader. What's your bootloader now?
Bootloader Is locked, will try to get back to the 5.1.1 again. Thanks
Hi Sir,
Can I flash stock firmware from 910F European version (GSM) after unlocking bootloader on 910V (CDMA)? Or I need permanent root or TWRP.
Because I just want to convert it to GSM phone but full stock without any customise.
Both versions have same hardware.
Please anyone help me. Is it safe conversion?