Sending 8$ on pp for de-brick on Teamviewer - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

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

Related

[Q] APN not listed and cannot add

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.

[Q] Trying to restore to stock, won't boot.

I was attempting to restore to stock. Saw in a couple of threads that if you had an updated bootloader that the return to stock instructions could brick your phone. Decided to downgrade bootloader using Restore_Bootloader_XXBLFB.
Flashed from recover and got a black screen and nothing. Now phone won't boot.
How do I recover from this?
The phine is the ATT s3 i747?
What bootloader was on your phone before you downgraded? If you had the 4.3 or newer bootloader, downgrading the bootloader will brick the phone. Also, an incompatible bootloader/modem combination will also brick the phone.
Without being able to boot I don't remember. I would imagine it was 4.3 or newer. so no recovery at all possible?
If the phone is running 4.3, there is no know way to dowgrade the bootloader.
Sounds like you need to use a de-brick method: http://forum.xda-developers.com/showthread.php?t=2549068
Ok using a debrick img I am able to get it to boot using an sd card. Now I have to use Odin to re-write a correct boot image?
ehupp said:
Ok using a debrick img I am able to get it to boot using an sd card. Now I have to use Odin to re-write a correct boot image?
Click to expand...
Click to collapse
You need to flash at least a bootloader and modem. Then, you can flash a custom recovery such as Philz or TWRP, and flash a custom ROM to at least get your phone up an running.
Having screwed up so royally so far what bootloader/modem should I use.
Second question, the instructions to use Odin to flash it aren't very clear. When I boot the phone with the sd card in I am able to access the internal memory for the phone via usb cable. Should I just load the bootloader/modem directly to that and not use the sd card?
Here is a screenshot from toolkit
http://imgur.com/DLQgAVu
Fixed it.
Thanks to people pointing me in the right direction I have restored it and saved my ass with my wife.
In case someone else has a problem like this and they are on a 4.4.2 build here is what I used.
I got the debrick img from here. First debrick at 128mb
https://www.androidfilehost.com/?w=files&flid=15759
put this on an sd card with WinDiskImager
http://sourceforge.net/projects/win32diskimager/
That got me booted.
So I knew I was going in the right direction.
Downloaded Odin 3.09
Then flashed this bootloader/modem
I747UCUEMJB_2024954_REV04_user_low_ship.tar.rar
http://forum.xda-developers.com/showpost.php?p=56371606&postcount=639
unzipped it and loaded it via Odin.
Load completed. Phone rebooted.
Booted right to setup/homescreen.
Thanks for the points in the right direction folks.
I am not at home right now but you need to boot the phone into download mode, launch Odin, flash custom recovery, boot to recovery, flash modem and bootloader.
You can find the bootloader and modem zip in the general thread. You should flash mob modem and bootloader since that is what you had before downgrading.

ready to breath new life on my s3-sgh i747m

SGH-I747M rooted, but still original rom
Carrier - Rogers
Ready to ditch my original Samsung/Rogers rom and flash a new one
Can someone please refer me to their choices
Hopefully no cellular/modem problem and no camera and sd card problems
Thanks in advance, any other tips will be appreciated
Research a bit,
first unlock for free from Rogers if you're still on 4.1.1. After you've moved up it costs.
Then update bootloader, I'm no expert, research.
I would highly recommend. Matrixzones L with a twist. It's for our phone specifically.
Works awesomely for me.
Sips at the battery. Every thing works fine for me, and I've tried a few
The safest way to move to a new ROM is to confirm the bootloader and modem currently installed on your phone. Once you know that, you can then determine if you can unlock your phone using the free method and which ROMs will work with the bootloader that is currently on your phone.
Okay, getting closer and confident
Device type - d2can
Bootloader/Baseband/PDA- I747MVLDLK4
Modem board- MSM8960
Will use EZ-Ulock to unlock the bootloader
Phone was rooted long tome ago
CWM-based Recovery v5.5.0.4
After a few more search, ill go with the suggestion of using matrixzone
Not sure if I still need to update my bootloader
Thanks for any more tips
well my confident just drop down
i have 4.1.1firmware so i installed the ez-unlock app to unlock my bootloader
i thought everything went well - "that was easy", but now it wont turn on
hopefully someone here can help
Have you tried the holding down volume up, home and power buttons at same time to get into recovery, then restore back up?
---------- Post added at 12:21 PM ---------- Previous post was at 12:17 PM ----------
I'm no expert but I understand you have to have original Samsung firmware running on phone then rogers has to do it for free, chime in anyone who knows more. I'm at knowledge threshold.
The bootloader on the i747m and i747 was never locked and using the bootloader unlock app bricked your phone. You will need to unbrick the phone using the method described in the unbrick thread or have the phone repaired via jtag service.
http://forum.xda-developers.com/showthread.php?t=2549068
With the i747m or i747, you could have flashed a custom recovery and then a custom ROM.
audit13 said:
The bootloader on the i747m and i747 was never locked and using the bootloader unlock app bricked your phone. You will need to unbrick the phone using the method described in the unbrick thread or have the phone repaired via jtag service.
http://forum.xda-developers.com/showthread.php?t=2549068
With the i747m or i747, you could have flashed a custom recovery and then a custom ROM.
Click to expand...
Click to collapse
well i really messed up now
i did bricked my phone
i did followed the instruction you provided and able to boot from my sd card -no data or cell signal
boot to download mode and used odin to install the stock rogers from this site
http://forum.xda-developers.com/showthread.php?t=1739426
odin started and fail - now i have the "firmware upgrade encountered an issue..." message
help please
i think i just need the right firmware to place in odin and flash to my phone
chris_j11 said:
well i really messed up now
i did bricked my phone
i did followed the instruction you provided and able to boot from my sd card -no data or cell signal
boot to download mode and used odin to install the stock rogers from this site
http://forum.xda-developers.com/showthread.php?t=1739426
odin started and fail - now i have the "firmware upgrade encountered an issue..." message
help please
i think i just need the right firmware to place in odin and flash to my phone
Click to expand...
Click to collapse
What error did you get in Odin? Sounds like you tried to flash an older ROM over your existing ROM. Try downloading and flashing the latest ROM from sammobile.com.
what is latest rom i can download and install - my rom was 4.1.1 before i messed up badly
well i just tried the next up - 4.1.2 Rogers Image and still Fail! (auth)
I will now try to latest from SamMobile - 4.4.2 and hopefully this work
well sucess - download the latest sammobile 4.4.2 and used Odin to install.
after 30mins my phones back to normal
thanks for all the help - now i'm more confident
now i will try to root / install cwm / and continue with matrixzone w/ a twist - hope to have a better result
No need to root first. You can install custom recovery and flash a rom.
can someone please provide insight on how to root my phone
i'm seeing a instruction to use Odin and CF-Auto-Root.tar
is this safe - since now im on 4.4.2
thanks again
Try installing a custom recovery and flash SuperSU from recovery.

Downgrading from Android 5.1.1 to Android 4.1

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.

Softbricked to download mode, unsure which versions are in my phone

I have a few specific questions at the bottom, but first, here's the long details:
I ran the custom ROM Hyperdrive RLS 16 (4.1.2) for years and loved it, but the past week I felt it was time to upgrade to a new ROM that was more up to date. I started to try out R3ARMED (4.4.2), did a full wipe in CWM and installed the zip files provided (the ROM and a d2att specific file).
Unfortunately, in my excitement I forgot to make sure that I had a 4.4 bootloader and modem, which seems to be rather essential for this particular ROM. The install failed and I thought I may have bricked the device, but I was able to update CWM and get back into recovery mode. This time, I got through the AROMA installer for the new ROM, but on reset I got stuck in a hard bootloop. It's pretty nasty--I can't use the key combination to reboot into recovery or download mode, and I only get as far as the opening "SAMSUNG" screen before the device blacks out. However, I can use a USB jig to force reboot into download mode--it's the only interface I can get with the phone at this point. ODIN recognizes the device, and when I use Heimdall and its drivers, I'm able to use those tools to interact with the phone. So I hope I'm not completely lost, but not being able to access CWM recovery mode definitely hurts.
Here's what I've tried so far to fix it:
- Without a USB jig, load recovery images onto a 16 GB SD card, insert into phone and power up (no successes, some images actually made it so the "SAMSUNG" screen no longer showed, others corrected this issue)
- Re-flash CWM with heimdall (failed)
- Used the Ultimate Android Toolkit to convert the CWM img into a tar that ODIN can flash, and tried to load it (failed)
I'm looking into trying to flash a full recovery onto the phone to see if that can fix it. But I have a few concerns:
1. I know that once my phone gets a 4.4 bootloader and modem, I can't go back to an earlier stock version.
2. I had an unsuccessful 4.1 -> 4.4 install attempt in the process of bricking updating my phone.
3. I have no idea if the install impacted the bootloader--so I don't know whether I can try a 4.3 stock flash or need to use some of the more recent phone dumps.
My first question is, as usual, what is the best route to take to recover this phone?
My second is, are there tools I can use for a phone in ODIN mode to check the version of the bootloader/modem, check on the integrity of the file system, etc. etc.?
I have a replacement phone on its way, but I view this as an excellent learning opportunity, and would love to hear some advice.
You have an i747 or i747m?
Do you see anything about warranty bit in download mode?
On the positive side, flashing the R3ARMED rom would not have changed your bootloader and modem. If you were on 4.1.2 before the flash, you should still be on 4.1.2 bootloader and modem.
There is at least one MJB_MJB Odin flashable stock ROM with active download links, it is for the i747. If you have the i747 and not the i747M you could try it.
If you have the i747M there are Odin packages for all of the stock ROMs at sammobile.com. Or, you could extract the system.img from the i747 ROM and flash it with Heimdall. BUT only if you are careful to avoid all of the files pertaining to bootloaders, radios, etc. (*.mbn, non-HLOS.bin, etc.) This route may not be for the faint of heart, but I promise I am not the only one to have done so. I didn't do so until I read of others having done this.
dawgdoc said:
On the positive side, flashing the R3ARMED rom would not have changed your bootloader and modem. If you were on 4.1.2 before the flash, you should still be on 4.1.2 bootloader and modem.
There is at least one MJB_MJB Odin flashable stock ROM with active download links, it is for the i747. If you have the i747 and not the i747M you could try it.
If you have the i747M there are Odin packages for all of the stock ROMs at sammobile.com. Or, you could extract the system.img from the i747 ROM and flash it with Heimdall. BUT only if you are careful to avoid all of the files pertaining to bootloaders, radios, etc. (*.mbn, non-HLOS.bin, etc.) This route may not be for the faint of heart, but I promise I am not the only one to have done so. I didn't do so until I read of others having done this.
Click to expand...
Click to collapse
It's a regular i747, not i747M. Thanks for the advice... you've given me a few things to try now! Will report back later with results.

Categories

Resources