Hey everyone, I'm working on making my dad's phone usable again. He has an S3 that was previously mine that had been running custom roms and was rooted. My brother installed an OTA update that, while not hard bricking the phone (after fixing a soft brick), made cell service nonexistent.
Basically, my baseband, IMEI, network, and phone number all are unknown. In my brother's diagnosis, he tried replacing the rom (as it was originally soft bricked) , and I believe downgrading to 4.1.1 from 4.3. Right now it is running a 4.1.1 rom called The Devils Reject v7.
I've tried installing basebands, going back to stock (I'm not sure if I've been doing it right, though), and installing CM. Some problems I'm encountering are Status 7 errors when flashing stock Roms through the recovery, or for that matter, CM roms. It is definitely still rooted and I have Philz v. 6.0.7.
I really have no idea what to do, so if anyone has any ideas at all, I'd be very appreciative.
Thank you so much.
Status 7 errors can be caused by an outdated recovery.
The latest Philz can be found here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Before flashing any more basebands, flash philz, flash cm11, determine the bootloader on the phone, and flash a matching modem.
audit13 said:
Status 7 errors can be caused by an outdated recovery.
The latest Philz can be found here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Before flashing any more basebands, flash philz, flash cm11, determine the bootloader on the phone, and flash a matching modem.
Click to expand...
Click to collapse
Thank you so much for your input
Unfortunately, after flashing the latest Philz you linked to, I'm still encountering the Status 7 error when trying to flash CM11. I think the D2ATT one is correct, no?
You should be flashing ROMs and recoveries made for the d2lte.
Which Philz did you flash?
audit13 said:
You should be flashing ROMs and recoveries made for the d2lte.
Which Philz did you flash?
Click to expand...
Click to collapse
Oh wow, can't believe I was installing the wrong version. I tried the latest CM11 for the D2LTE model and am still seeing a status 7 error when flashing. I'm running the latest Philz for D2LTE also. Strange right?
Try flashing an leer version of cm10.2 or cm11.
audit13 said:
Try flashing an leer version of cm10.2 or cm11.
Click to expand...
Click to collapse
Some good news! After a "Clean for new rom install" option in Philz I was successfully able to install CM11 D2LTE. Still no baseband, IMEI, etc. Should I try to flash a modem now?
Flashed the 4.4 modem (UCUFNE4) and it seems to be working! Thanks so much for your help, seriously. I really, really appreciate it.
Awesome! Glad you got it all working.
Related
I don't recall specifically what caused this, I'm quite sure it didn't happen after a flash of anything though, which is quote odd.
ATT i747
ROM: http://forum.xda-developers.com/showthread.php?t=1766684
Keneral: http://forum.xda-developers.com/showthread.php?t=1756776
Firmware: I747UCUEMJ2 (As far as I can recall)
I've already tried flashing multiple modems though TWRP. No Luck.
I've gone into recovery (TWRP) and tried a "Factory Reset" and flashing a rom/kernel. No Luck.
I've gone into recovery and tried a very full wipe (pretty much everything except USB-OTG and External SD) and flashing a rom/kernel. No Luck.
I've already tried both of the last two and restoring various backups I had. No Luck.
What additional information would you need to assist me?
Any idea on what I could do to repair this?
I've searched and come across a lot of dead ends.
YoHoJo said:
I don't recall specifically what caused this, I'm quite sure it didn't happen after a flash of anything though, which is quote odd.
ATT i747
ROM: http://forum.xda-developers.com/showthread.php?t=1766684
Keneral: http://forum.xda-developers.com/showthread.php?t=1756776
Firmware: I747UCUEMJ2 (As far as I can recall)
I've gone into recovery (TWRP) and tried a "Factory Reset" and flashing a rom/kernel. No Luck.
I've gone into recovery and tried a very full wipe (pretty much everything except USB-OTG and External SD) and flashing a rom/kernel. No Luck.
I've already tried both of the last two and restoring various backups I had. No Luck.
What additional information would you need to assist me?
Any idea on what I could do to repair this?
I've searched and come across a lot of dead ends.
Click to expand...
Click to collapse
Your modem is probably lost or corrupt. You may try downloading the modem from the link below and flashing via (custom) recovery.
http://www.androidfilehost.com/?fid=23212708291680823
Larry2999 said:
Your modem is probably lost or corrupt. You may try downloading the modem from the link below and flashing via (custom) recovery.
http://www.androidfilehost.com/?fid=23212708291680823
Click to expand...
Click to collapse
Ah forgot to mention, already tried flashing multiple modems with no luck :'(
Thanks for the tip!
YoHoJo said:
Ah forgot to mention, already tried flashing multiple modems with no luck :'(
Thanks for the tip!
Click to expand...
Click to collapse
Why don't you try a full (stock) firmware restore then? If you have MJ2 , you can upgrade to full stock 4.3JB. I also learnt from a very reliable source that you can Odin safely to 4.1.1 from the (modified) MJ2 as long as you don't have the MJB bootloader.
Larry2999 said:
Why don't you try a full (stock) firmware restore then? If you have MJ2 , you can upgrade to full stock 4.3JB. I also learnt from a very reliable source that you can Odin safely to 4.1.1 from the (modified) MJ2 as long as you don't have the MJB bootloader.
Click to expand...
Click to collapse
That's a bit of my question, I'm, not sure what firmware I'm on currently, how can I check?
OR which one is the newest, I can flash from anything to the newest one correct?
I'm ready to do that, but worried on what bootloader I have, and which to flash to safely.
I've seen a lot of old guides, dead guides, 404 DL links, etc :/.
I just don't want to flash anything incorrect in my attempts to repair it, and brick it. :silly:
Boot into download mode and tell us what it says on the screen. This information will determine whether you have a stock 4.3 bootloader on your phone.
Larry2999 said:
Why don't you try a full (stock) firmware restore then? If you have MJ2 , you can upgrade to full stock 4.3JB. I also learnt from a very reliable source that you can Odin safely to 4.1.1 from the (modified) MJ2 as long as you don't have the MJB bootloader.
Click to expand...
Click to collapse
audit13 said:
Boot into download mode and tell us what it says on the screen. This information will determine whether you have a stock 4.3 bootloader on your phone.
Click to expand...
Click to collapse
ODIN MODE
PRODUCT NAME: SGH-I747
CUSTOM BINARY DOWNLOAD: Yes (8 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
QUALCOM SECUREBOOT: ENABLE
Warrenty Bit: 1
BOOTLOADER AP SWEV: 2
Click to expand...
Click to collapse
No bootloader info on there?
That's all it says on download mode.
It looks like you are running the stock 4.3 AT&T bootloader. I based this conclusion of the fact that your warranty counter has been changed to 1 from 0.
I suggest installing the latest version of Philz TOuch via Odin and flash a custom Kit Kat ROM. Try that and see if the modem works.
BTW, you should use the mjb modem as other modems probably won't work.
audit13 said:
It looks like you are running the stock 4.3 AT&T bootloader. I based this conclusion of the fact that your warranty counter has been changed to 1 from 0.
I suggest installing the latest version of Philz TOuch via Odin and flash a custom Kit Kat ROM. Try that and see if the modem works.
BTW, you should use the mjb modem as other modems probably won't work.
Click to expand...
Click to collapse
I've tried flashing a few different ROMs and Modems w/o any luck, I'll try specifically an MJB modem and see what's up.
Mind linking to a thread w/ more info about Philz Touch for att i747? What exatly is this?
Edit:
Seems like Philz Touch is a custom recovery? Why install this when I have latest TWP already?
Edit:
Flashing MJ2 bootloader via TWRP right now, seeing how that goes.
YoHoJo said:
I've tried flashing a few different ROMs and Modems w/o any luck, I'll try specifically an MJB modem and see what's up.
Mind linking to a thread w/ more info about Philz Touch for att i747? What exatly is this?
Edit:
Seems like Philz Touch is a custom recovery? Why install this when I have latest TWP already?
Click to expand...
Click to collapse
I recommend Philz Touch because it is easy to flash it using Odin. I used to have TWRP and had problems flashing ROMs. Once I switched to Philz, I didn't have anymore problems.
The best modem in your case would be the mjb version. Even though the Canadian and US versions of the s3 are identical hardware wise, the bootloaders and modems are not interchangeable.
audit13 said:
I recommend Philz Touch because it is easy to flash it using Odin. I used to have TWRP and had problems flashing ROMs. Once I switched to Philz, I didn't have anymore problems.
The best modem in your case would be the mjb version. Even though the Canadian and US versions of the s3 are identical hardware wise, the bootloaders and modems are not interchangeable.
Click to expand...
Click to collapse
I've used TWRP for a long time/flashed many files without issue, thanks for the suggestion.
So what exactly would you like me to flash though (links would be nice if you could)?
As I've said, I've already tried various ROMs/Modems etc, the problem is deeper than that.
Edit: Flashed MB2
All of the same issues still occur. :'(
SOLVED:
Flashed Firmware:
I747UCUEMJB_2024954_REV04_user_low_ship.tar.md5.zip (I guess this is what you were telling me to do all along huh?)
All good.
Thanks everyone!
YoHoJo said:
I've used TWRP for a long time/flashed many files without issue, thanks for the suggestion.
So what exactly would you like me to flash though (links would be nice if you could)?
As I've said, I've already tried various ROMs/Modems etc, the problem is deeper than that.
Edit: Flashed MB2
All of the same issues still occur. :'(
Flashed Firmware:
I747UCUEMJB_2024954_REV04_user_low_ship.tar.md5.zip (I guess this is what you were telling me to do all along huh?)
All good.
Thanks everyone!
Click to expand...
Click to collapse
Maybe I had issues with TWRP because mine was outdated or perhaps it's just my phone, I'm not sure. I use TWRP on my Nexus 4 and it's perfect.
Glad you got things working:good:
YoHoJo said:
I've used TWRP for a long time/flashed many files without issue, thanks for the suggestion.
So what exactly would you like me to flash though (links would be nice if you could)?
As I've said, I've already tried various ROMs/Modems etc, the problem is deeper than that.
Edit: Flashed MB2
All of the same issues still occur. :'(
SOLVED:
Flashed Firmware:
I747UCUEMJB_2024954_REV04_user_low_ship.tar.md5.zip (I guess this is what you were telling me to do all along huh?)
All good.
Thanks everyone!
Click to expand...
Click to collapse
I flashed the same firmware with Odin and was then able to successfully root and flash my s3 with 4.4.2 PACman. Was having the same issue before this where I had no service, no sound, and YouTube, etc.. wouldn't play.
Hello all. I just received a galaxy s3 from my sister in law running 4.4.2. I am aware I can't downgrade the complete firmware using Odin. The phone it's rooted. My question is what can I do with this thing as far as playing with roms and what not? Can I only install 4.4.2 based roms? Can I even unroot? I have been rooting and installing roms for years now but never have a phone felt more unfriendly before this. Thanks in advance.
Is the phone running stock 4.4.2?
You can install a custom recovery to the phone, copy some custom ROMs to an external SD card, and try out a bunch of ROMs.
Yeah its stock 4.4.2 rooted with clockwork mod recovery. Do the roms have to be 4.4 or 4.4.2 based? Tried cyanogenmod 4.3 and failed. I pretty much would like to flash via odin to go back to stock unrooted but 4.4.2 was over the air. Got 4.3 via sammobile but that fails. Kies won't show my device for firmware recovery. Shows it as normal to sync.
What error did you get when trying to flash CM10.2? Is your CWM up to date?
I would have assumed that CM10.2 would be comaptible with your KK bootloader and modem.
Do not make anymore attempts to flash 4.3 via Odin. This could result in a bricked phone because a KK modem on a 4.3 bootloader cannot be fixed using any method available on XDA.
Yeah I'm aware of the boot loader and modem downgrade issue. Tried odin once and just left it as is.
Is your CWM up to date? What error did you get when trying to flash CM10.2?
I don't remember the error. According to Rom manager, my recovery is up to date
What version is the cwm? I prefer to manually flash a custom recovery instead of relying on ROM manager.
Cwm 6.0.4.7. I've always used rom manager except for my galaxy nexus. Flashed with windows terminal and fastboot.
Since CWM is up to date, try flashing the most recent CM11.
Older cm roms, and any older roms should run fine on NE4. Some may not flash though, such as cm10. This is because the updater script doesn't include NE4 as it wasn't out when the rom was built. If you edit the script to make it flash, any of the available roms should run just fine.
As it stands though, the easiest thing would be to do as audit13 suggested and flash cm11. That and most other recent roms should flash just fine w/o any extra work.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
well, after downloading the most recent cm11 nightly and gapps, rebooted into recovery and wiped. when trying to flash cm11, sd card not mounting. couldn't mount, restored a backup only to be greeted to a display that would not go to sleep and a fury of app and processes stopping pop ups. settings-accounts-backup and reset-factory data reset-etc did nothing but ask for a password. did it through recovery to a perfectly working phone with baseband version: unknown, IMEI: unknown, IMEISV: unknown. flashed the NE4 modem Doc posted in another forum, no dice. same message from cm as before. this time i remember. it was a bunch of basebands not including NE4.
And getprop ro.bootloader says NE4. first said unknown but maybe i typed it wrong.
Got it all back running. tried the S3Rx NE4 aroma zip that would end with installation aborted. found enewman17's post on updating using a stock-rooted 4.4.2 zip after flashing Doc's modem zip. all is well! So thank you DocHoliday77, and thank you enewman17!
Glad you got it working!
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Hello
I am currently running the latest version of TWRP (openrecovery-twrp-2.8.1.0-d2att) and I am trying to flash CM 11, but I get an error in red "Failed"
I am even getting a failed error as well when flashing the bootloader in the thread below.
I have successfully been able to flash SlimKat 4.4.4 and Dirty Unicorn with no problems. I think I had the same problems as well when trying to flash Paranoid Android.
I have tried flashing the files from both the external SD card and Internal. No go.
This is the thread I am following: http://forum.xda-developers.com/showthread.php?t=2682905
Here is the error I get when flashing:
You cannot flash from your current bootloader. Current version: I747MVLUEFNE6
E: Error executing updater binary in zip '/external_sd/Flash/CM/1/boot_CWM_I747MVLUEMK5.zip'
Try using the latest version of Philz Touch for the d2lte to flash files.
You can flash the most recent zip from TWRP.
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
audit13 said:
Try using the latest version of Philz Touch for the d2lte to flash files.
You can flash the most recent zip from TWRP.
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Click to expand...
Click to collapse
Ok, so I flashed the latest zip using the TWRP App rebooted into PhilZ Recovery and tried to flash the bootloader ( boot_CWM_I747MVLUEMK5.zip) from here: http://forum.xda-developers.com/showthread.php?t=2321310
Still got an error: Please upgrade to latest binary...You cannot flash from your current bootloader. Current version: I747MLUFNE6
E: Error in /storage/sdcard1/Flash/CM/1/boot_CWM_I747MVLUENK5.zip (Status 7) Installation aborted
Do not flash any bootloader to your phone. It is good that it did not flash mk5 over ne6. This will brick for phone.
audit13 said:
Do not flash any bootloader to your phone. It is good that it did not flash mk5 over ne6. This will brick for phone.
Click to expand...
Click to collapse
Ok thanks. Where can I find the latest boot-loader for my device? I was trying to follow this guide to flash CM11 and it told me to download the latest boot-loader and update it: http://forum.xda-developers.com/showthread.php?t=2682905
I guess the thread I wrote above is an outdated guide to flashing CM11. Would you happen to know the steps I should take to flash cm11 for my device with my current bootloader?
BTW I still can't flash the CM11 Rom in Philz Touch Recovery.
Iv never had any issues using philz touch to flash.
drakemiller40 said:
Ok thanks. Where can I find the latest boot-loader for my device? I was trying to follow this guide to flash CM11 and it told me to download the latest boot-loader and update it: http://forum.xda-developers.com/showthread.php?t=2682905
I guess the thread I wrote above is an outdated guide to flashing CM11. Would you happen to know the steps I should take to flash cm11 for my device with my current bootloader?
BTW I still can't flash the CM11 Rom in Philz Touch Recovery.
Click to expand...
Click to collapse
You have the ne6 bootloader. Do you have an i747m or i747? It will make a difference when it comes to flashing an updated bootloader and modem.
Are you downloading the latest CM11 from the cyanogen site?
audit13 said:
You have the ne6 bootloader. Do you have an i747m or i747? It will make a difference when it comes to flashing an updated bootloader and modem.
Are you downloading the latest CM11 from the cyanogen site?
Click to expand...
Click to collapse
Thanks for helping out so far. My Model number that shows up in "About Device" in my phone's settings say SGH-I747M. Yes I am downloading the latest CM11 Nightly build here : http://download.cyanogenmod.org/?device=d2lte
P.S.
Will I bay able to go back to stock if I don't like CM11? I heard that it will brick my phone from rolling back the boot loaders. What if I restore from a nandroid backup, will that work to restore to stock without bricking my device?
With a custom recovery, you can create a backup, flash your ROM, and you can restore the backup if you don't like cm11.
audit13 said:
With a custom recovery, you can create a backup, flash your ROM, and you can restore the backup if you don't like cm11.
Click to expand...
Click to collapse
Ok thats good. Though I still have the problem of flashing CM11. It still fails on me on TWRP or Philz Touch Recovery. Any ideas on how to fix this problem?
What error are you getting? What cm11 ROM are you flashing?
audit13 said:
What error are you getting? What cm11 ROM are you flashing?
Click to expand...
Click to collapse
Never mind, found out that I had to run the factory reset in PhilZ Touch first then flash the rom. Alls good, but didn't like CM11.
Though why didn't it work on TWRP?
I had issues with TWRP flashing ROMs too. Once I switched to Philz which is based on CWM, I had no issues flashing the same ROMs that TWRP would not flash.
I recently got a Samsung Galaxy S3 (running KitKat 4.4.2, stock, unrooted) and I consider installing CyanogenMod 13 on it, as I did with my Note 2.
Is it safe to install, as is? I read somewhere that the bootloader is locked after 4.3, which prevents installing other roms than ones based on stock.
And if it is, does it worth it? Is there major issues which makes it not usable on a daily basis? For the matter, I was satisfied with CM13 on my Note 2.
Thanks!
To flash cm13, just flash twrp via Odin, boot into twrp, perform a full wipe, flash cm13, gapps, reboot.
The bootloader is not locked regardless of the bootloader version from what I have read and seen for the t999 and t999v.
audit13 said:
To flash cm13, just flash twrp via Odin, boot into twrp, perform a full wipe, flash cm13, gapps, reboot.
The bootloader is not locked regardless of the bootloader version from what I have read and seen for the t999 and t999v.
Click to expand...
Click to collapse
It worked like a charm. Thank you.
Glad it worked. We're all here to help and learn.
scottmada said:
It worked like a charm. Thank you.
Click to expand...
Click to collapse
Hi, scottmada.
Which build (tmo, att, etc.) have you used? I also have a SGH-T999V that is currently rooted and running the latest d2lte CM11 snapshot build. I am considering performing a "safe" upgrade to CM13 and would like to know what has worked for others.
Thanks.
p.s. Sorry for replying a month later to this thread.
Hi, I'm currently using this method to flash roms, and I've flashed OctOS M a total of 3 times using this method, but for some reason, after a bit of time the ROM gets really buggy.
Is there a better way of flashing this ROM, or is it the ROM itself causing these issues.
Thanks,
Which phone do you have? For the i747 and i747m can be flashed with TWRP from Odin. The custom ROM and Gapps and then flashed from TWRP.
audit13 said:
Which phone do you have? For the i747 and i747m can be flashed with TWRP from Odin. The custom ROM and Gapps and then flashed from TWRP.
Click to expand...
Click to collapse
Currently have an i747m
its just that for some reason, at first OctOS M works perfect, and then starts to have tons of issues overtime, which other people dont seem to have.
I remember somebody telling me to wipe data and cache about 3 times before installing the ROM in TWRP, even tho i usually just do it once. Is that the proper way to do it?
Thanks,
The phone is running the latest KK bootloader and modem/baseband?
Did you use TWRP to wipe system as well before installing the custom ROM?
audit13 said:
The phone is running the latest KK bootloader and modem/baseband?
Did you use TWRP to wipe system as well before installing the custom ROM?
Click to expand...
Click to collapse
Not sure how i can check if im running the latest bootloader or modem/baseband.
Yea, I had also wiped system, and delvik cache.
You can install the Samsung Phone Info App from the play store which will tell you the bootloader and modem/baseband version in the phone. I think FOB3 is the latest.
audit13 said:
You can install the Samsung Phone Info App from the play store which will tell you the bootloader and modem/baseband version in the phone. I think FOB3 is the latest.
Click to expand...
Click to collapse
My bootloader and modem/baseband end in FOB3.
Okay, then that's not causing the problem. It may be a bug that's unique to your particular phone. The only way to tell for sure may be to install a different ROM to see what happens.