Related
i have a bell galaxy note 2, after i flashed some custom ROM, my phone stop working, i have found similar problem on the sprint form, but doesn't know how to fix, please help.
Problem #1:
After flashing a ROM, the GN2 is unable to activate the radio/modem. The following read "Unknown" in the "About Phone" menu:
Baseband, Network, Mobile Network Type, MEID, IMEI, ICCID.....etc. Basically anything to do with the mobile network.
Problem #2:
When booted up and running, PC will not recognize the phone as usual (unable to copy files to phone).
i try odin a bell stock still doesn't work, and when i boot into recovery it keep saying is a RWC rogers phone, does that have something to do with the problem? i also try kies too, still no luck.
minghaoji said:
i have a bell galaxy note 2, after i flashed some custom ROM, my phone stop working, i have found similar problem on the sprint form, but doesn't know how to fix, please help.
Problem #1:
After flashing a ROM, the GN2 is unable to activate the radio/modem. The following read "Unknown" in the "About Phone" menu:
Baseband, Network, Mobile Network Type, MEID, IMEI, ICCID.....etc. Basically anything to do with the mobile network.
Problem #2:
When booted up and running, PC will not recognize the phone as usual (unable to copy files to phone).
i try odin a bell stock still doesn't work, and when i boot into recovery it keep saying is a RWC rogers phone, does that have something to do with the problem? i also try kies too, still no luck.
Click to expand...
Click to collapse
This has nothing to do with development.
However unless you have a backup. You'll need to return your phone for a new one.
antiochasylum said:
This has nothing to do with development.
However unless you have a backup. You'll need to return your phone for a new one.
Click to expand...
Click to collapse
sorry i posted wrong place, where can i get help, i am new to this, and how do i delete this post
Make sure you odin a rom that included the radio and kernel. Preferably a return to stock type thing. If that didn't work did you back up your efs partition?
Also what did you flash exactly?
OP please read the Forum Rules on posting in the correct Section, Moved & Thank You
I had same situation as you few days ago, I messed up my Rogers note ii with flashed 7100 rom to my i317m. I lost baseband, network imei. Luckily, after I flashed root injected FACTORY Stock rom to my rogers phone, the problem had been fixed, here is the link where you can download the root injected FACTORY Stock rom for you phone. Hopefully, you will get your phone fixed
http://forum.xda-developers.com/showthread.php?t=2004650
jjzeng said:
I had same situation as you few days ago, I messed up my Rogers note ii with flashed 7100 rom to my i317m. I lost baseband, network imei. Luckily, after I flashed root injected FACTORY Stock rom to my rogers phone, the problem had been fixed, here is the link where you can download the root injected FACTORY Stock rom for you phone. Hopefully, you will get your phone fixed
http://forum.xda-developers.com/showthread.php?t=2004650
Click to expand...
Click to collapse
Yeah i flashed this one no lucks, i think my parition is messed up, wonder if anyone has a back up efs file for my phone
Aridon said:
Make sure you odin a rom that included the radio and kernel. Preferably a return to stock type thing. If that didn't work did you back up your efs partition?
Also what did you flash exactly?
Click to expand...
Click to collapse
i flashed a rogers rooted stock version rom on my phone, so now after i did recovery it just keep on shows is a RWC in the recovery mode doesn't matter which stock rom i flash, and its saying a BMC in the download more product name. so its really messed up. because i unlocked the phone from bell, so the guy at bell told me i void the warranty on it. now i don't know what i can do to fix my phone.
Pit CSC file
any idea where i can find a pit file for my bell note 2 so i can repartion it, or that's something only samsung has it
This was a big issue with the gs3 and they've come up with a solution in that thread so given the similarities I would think that would work with some tweaking for the different partitions on the note 2. Check out the gs3 forum & maybe get in touch.. they might be able to help.
Sent from my SGS3 using my finger
Hello everyone i have an galaxy s3 at&t version and i was trying to install a rom and the rom said it needed a certain bootloader so i download it and flash it and now my phone won reconize my sim or network state nor imei and i need help please !!!
!!!!!
ive tried odin and try reflashing back to stock but odin failed
ImJusDatGuy said:
Hello everyone i have an galaxy s3 at&t version and i was trying to install a rom and the rom said it needed a certain bootloader so i download it and flash it and now my phone won reconize my sim or network state nor imei and i need help please !!!
!!!!!
Click to expand...
Click to collapse
Definitely more info needed.
What ROM is on your device?
What bootloader did you install?
What modem/baseband/radio is on your device?
What method did you use to try to install the bootloader?
Is your phone still showing the correct IMEI in settings or 0 ? (Compare between that shown in settings and under the battery.)
It may be as simple as updating your modem, but I/we can't tell yet.
dawgdoc said:
Definitely more info needed.
What ROM is on your device?
What bootloader did you install?
What modem/baseband/radio is on your device?
What method did you use to try to install the bootloader?
Is your phone still showing the correct IMEI in settings or 0 ? (Compare between that shown in settings and under the battery.)
It may be as simple as updating your modem, but I/we can't tell yet.
Click to expand...
Click to collapse
the rom i have at the moment is the restored verison of the rooted rom i have which is stock 4.1.1 with root
the bootloader i install is I747UCUEMJB
my phone says baseband verison is unknown
i install the bootloader through cwm
the imei is unknown also my phone number to and network and roaming says not roaming mobile network state is disconnected.
everything is messed up thanks for the quick reply man i need help.
ImJusDatGuy said:
the rom i have at the moment is the restored verison of the rooted rom i have which is stock 4.1.1 with root
the bootloader i install is I747UCUEMJB
my phone says baseband verison is unknown
i install the bootloader through cwm
the imei is unknown also my phone number to and network and roaming says not roaming mobile network state is disconnected.
everything is messed up thanks for the quick reply man i need help.
Click to expand...
Click to collapse
I'm new at this, in fact I have flashed by old Captivate several times but yet to flash my SGS3. Anyhow, I have spent many hours reading. Before doing anything I suggest, read, and read some more.
Don't flash back to 4.1.1 or 4.1.2 at this point. They will install an older bootloader than is currently on your phone. From what I have read, you narrowly escaped bricking your phone. You might want to read some of the threads regarding the 4.3 stock ROM and unbricking before making any changes in restoring your device.
You can probably fix this by flashing the modem that goes with the 4.3 series ROMs. It would also be the MJB flavor, although the MJ2 would probably work. Several of the 4.3 TouchWiz ROMs in the development forum have download links for the MJB modem. I would guess you were probably going to install one of them. I would recommend flashing the modem to see if that solves your issues before going ahead with the ROM flash.
dawgdoc said:
Definitely more info needed.
What ROM is on your device?
What bootloader did you install?
What modem/baseband/radio is on your device?
What method did you use to try to install the bootloader?
Is your phone still showing the correct IMEI in settings or 0 ? (Compare between that shown in settings and under the battery.)
It may be as simple as updating your modem, but I/we can't tell yet.
Click to expand...
Click to collapse
dawgdoc said:
I'm new at this, in fact I have flashed by old Captivate several times but yet to flash my SGS3. Anyhow, I have spent many hours reading. Before doing anything I suggest, read, and read some more.
Don't flash back to 4.1.1 or 4.1.2 at this point. They will install an older bootloader than is currently on your phone. From what I have read, you narrowly escaped bricking your phone. You might want to read some of the threads regarding the 4.3 stock ROM and unbricking before making any changes in restoring your device.
You can probably fix this by flashing the modem that goes with the 4.3 series ROMs. It would also be the MJB flavor, although the MJ2 would probably work. Several of the 4.3 TouchWiz ROMs in the development forum have download links for the MJB modem. I would guess you were probably going to install one of them. I would recommend flashing the modem to see if that solves your issues before going ahead with the ROM flash.
Click to expand...
Click to collapse
Could you provide an link by any chance please i dont want to install anything wrong and btw im on jb 4.1.1 do i need to install a 4.3 rom also ? or ?
ImJusDatGuy said:
Could you provide an link by any chance please i dont want to install anything wrong and btw im on jb 4.1.1 do i need to install a 4.3 rom also ? or ?
Click to expand...
Click to collapse
The reason I didn't put a link in the previous posts was to get you to read about what you were doing as you searched for the modem. I am offering advice on things I have yet to experience on this device and only speaking second hand. My advice is only based on what I have read not on anything I have had to correct myself.
In truth I think you just stopped too soon in the process of what you were doing earlier. You said you installed the 4.3 bootloader in preparation to installing a 4.3 or later ROM that required the up to date bootloader. You didn't mention installing the current modem/baseband. You didn't mention trying to flash whatever ROM you had been considering.
You may be able to correct your device simply by installing the 4.3 modem. HERE is the modem thread, it is in the General Forum for our device. Make sure you pick the correct one. I don't know if your device will work well on the MJB bootloader and modem with a 4.1.1 ROM, from something I seem to recall reading I suspect it will.
Take this in steps. Install the correct modem, the one that matches your bootloader. See if that corrects you sim, data, and IMEI problems. If it does correct the issues, the next step is to decide if you want to stay on the 4.1.1 ROM or change to whatever ROM you had been considering. If you decide to change, make backups first. If it doesn't fix the problem while on 4.1.1 you may want to flash the version of the official 4.3 ROM enewman17 has provided on the development thread.
Take it one step at a time. Read about what you are about to do until you understand it well, all before doing anything. Make backups sequentially as you make each corrective step.
HTH.
dawgdoc said:
The reason I didn't put a link in the previous posts was to get you to read about what you were doing as you searched for the modem. I am offering advice on things I have yet to experience on this device and only speaking second hand. My advice is only based on what I have read not on anything I have had to correct myself.
In truth I think you just stopped too soon in the process of what you were doing earlier. You said you installed the 4.3 bootloader in preparation to installing a 4.3 or later ROM that required the up to date bootloader. You didn't mention installing the current modem/baseband. You didn't mention trying to flash whatever ROM you had been considering.
You may be able to correct your device simply by installing the 4.3 modem. HERE is the modem thread, it is in the General Forum for our device. Make sure you pick the correct one. I don't know if your device will work well on the MJB bootloader and modem with a 4.1.1 ROM, from something I seem to recall reading I suspect it will.
Take this in steps. Install the correct modem, the one that matches your bootloader. See if that corrects you sim, data, and IMEI problems. If it does correct the issues, the next step is to decide if you want to stay on the 4.1.1 ROM or change to whatever ROM you had been considering. If you decide to change, make backups first. If it doesn't fix the problem while on 4.1.1 you may want to flash the version of the official 4.3 ROM enewman17 has provided on the development thread.
Take it one step at a time. Read about what you are about to do until you understand it well, all before doing anything. Make backups sequentially as you make each corrective step.
HTH.
Click to expand...
Click to collapse
i've read this one thread and ive downloaded the modem and the rom ive tried to instal was a kitkat version of quatom v3.3 and it say get prop bootloader and i looked up the error everyone said to update your bootloader and thats how i got into this mess. :'( but thank you bro i really appreciate you took the time out of your day to help me.
ImJusDatGuy said:
i've read this one thread and ive downloaded the modem and the rom ive tried to instal was a kitkat version of quatom v3.3 and it say get prop bootloader and i looked up the error everyone said to update your bootloader and thats how i got into this mess. :'( but thank you bro i really appreciate you took the time out of your day to help me.
Click to expand...
Click to collapse
thanks man for telling me what was wrong your an amazing human being and i love you (no homo) and thanks again a million thanks bro.
Did that modem fix some of the problems?
If your on 4.1.1 shouldn't you flash the DKL3 version or can't you just flash thru Odin the DLK3 stock ROM thru Odin Amd start all over again
I've been on 4.3 with that bootloader Amd have flashed back to 4.1 back to the baseband version DLK3 firmware. I would think being on 4.1 you should be able to reflash using Odin to fix the issue or flash the modem for 4.1 .
Q&A for [Baseband] ALL T999, T999L, T999V, T999N Modems! w/ MAP and Data Tweaks!
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
modem T999VVLUFNH2
Hi everybody,
I try to find the updated modem for my S3 (videotron SGH-T999v)
I have the modem T999VVLUFNF1 (ROM LS 3.1 stable KK 4.4.4, KT747 kernel)
When I unzip the official ROM of samsung (older like 4.1.2 and the last samsung update from september 2014) , I only find the file NON-HLOS.bin
According to sammobile the last videotron modem is T999VVLUFNH2, but I cannot find the file. This is the first time I try to update the modem because I have a poor reception in my house.
Thank you for your help
I haven't decided if I will post those or not. Too great a risk with the 4.4.2 modems. If you want to try the latest I can only recommend fully updating as a safe way to do so.
If you really want to be the one to test if it's safe, I'll get it uploaded for you, but understand there is a chance it could hard brick the phone beyond repair.
Reason for all of this is because we know if you flash a 4.4.2 modem on 4.3 it'll permanently brick it. I have no idea if flashing an older or newer 4.4.2 modem on 4.4.2 firmware (like you want to do) will result in the same. Normally, I would guess it wouldn't be the case, but it seems a lot has changed in these new builds that no one understands, and there have already been too many bricks for me to be comfortable trying something new like this without exercising great caution.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Thank you for your reply and your advise.
As I don't have enought money to take the risk, I will keep my actual modem.
Thank again
Don't blame you a bit! But don't forget, you can still fully update and that may help. (From what I've seen, flashing older modems on 4.4.2 doesn't brick, so i think if you updated, it should be ok to flash the NF1 modem if the newer one doesn't help. It might not work, but I don't think it would cause any harm. Just food for thought, but again, I can't guarantee anything with these latest modems...)
If it's a bad signal issue that you did not have before, call your carrier and ask if there are any tower/network/account issues they are aware of.
Your carrier probably doesn't do this, but Tmobile will sometimes give customers a signal booster for home use only. You can buy them online too, but I'm not sure how my h they are these days. (Just make sure it boosts the frequencies used by your carrier if you look into this.)
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Just noticed today that my phone is on T999VVLUFNF1 but that there is a newer 4.4.2 release for the T999V phone that is T99VVLUFNH2. Would it be good to update via Odin to this? Is it just a newer modem?
I have a T mobile T999 that is currently flashed with CyanogenMod 11-20141008-SNAPSHOT-M11-d2lte which is kitkat 4.4.4. The baseband version is T999UVDMD5. I have a Lebara sim card in it now, and I'm in France. I'm not getting any signal and I suspect it is because the baseband version mismatch. Is there anything I can do to make this setup work or do I have to downgrade to a different version of CM? Is there and updated modem I can flash on this device or any way to make it work?
abetterlie said:
I have a T mobile T999 that is currently flashed with CyanogenMod 11-20141008-SNAPSHOT-M11-d2lte which is kitkat 4.4.4. The baseband version is T999UVDMD5. I have a Lebara sim card in it now, and I'm in France. I'm not getting any signal and I suspect it is because the baseband version mismatch. Is there anything I can do to make this setup work or do I have to downgrade to a different version of CM? Is there and updated modem I can flash on this device or any way to make it work?
Click to expand...
Click to collapse
Latest baseband is NC2, flash it, and if the device still does not pick up service flash back to MD5 firmware and see if it will pick it up. If not then it might incompatible with your provider..
Thanks!!!! Also Those using T999 switched to ATT
Just wanted to say thank you!!!
Also just wanted to say for those who have a T999 that switched to AT&T this works (I wasn't sure if this would work since it didn't say anything about AT&T working with it. To be perfectly honest I didn't read everything but again THANKS!!!!!!
Hi Guys,
I got the OTA update ( T999UVUENC2 ) about a month back and since then, my Wifi has stopped working. It stays greyed out when I try to turn it on. Just won't turn on.
The logcat says that the "WiFi driver is unstable".
What I have tried so far (with no success):
1) Flash the same build again (T999UVUENC2).
2) Flash the root666_T999UVUENC2 build. (Currently, I am on this)
3) Flash Cyanogenmod 11.
4) Factory reset.
5) Pull the battery out when the phone is on and put it back again.
6) Modify/delete the wpa_supplicant.conf file.
Can someone please give any directions on how the "Wifi driver can be fixed"? I understand from going through the forums that downgrading from 4.3 to 4.2 can cause a brick. However, can I downgrade to the previous T-Mobile 4.3 build (T999UVUEMJC ) without causing a brick? Do you guys think that can help fix the Wifi?
Any help would be greatly appreciated.
Could you point me to what one exactly i need for T999LUVUBNF4
SGH-T999L Will Not Mount Ext Sd/No root or load file from .zip to root
I always get stuck at the boot screen where I am supposed to Update from Zip, but my phone NEVER lets me Mount the External SD card, I have a 64GB card, failed, 16 GB card, failed, what am I missing. All the good tutorials, ESPECIALLY yours, get me to that point but being unable to load that .zip file from sd just murders me. The Phone is on 4.3 and I believe I loaded your stock 4.3 firmware after failing to get this part done and then trying every single rom possible (didn't realize this had murdered me) until I managed to get back to this stock rom. Why does it not want to load from ext sd? Is it the file system? I've never had any issues with any of these sd cards, and they aren't generic cards, one is a samsung other a sandisk,
I'm really frustrated. I've been trying to update this Galaxy S3 for days now with no success. Currently I am running on Slimkat 7.0. It's sometimes slow and buggy and needs some updating.
For reference, this is the phone at its current state:
- Bootloader: i747ucalh9 (literally taken from the fail message when trying to update to any other bootloader)
- Modem/firmware (?): I747UCLH9
Here's what has happened, greatly summarized (note I'm using CM6.0.4.7 for all of these operations, and when I say "update", I mean "flash"):
- I tried updating to Slimkat 9 but received no signal. I gave up on it entirely for a while
- I tried installing various LP ROMs, including CM12.1.
- I had 12.1 running for a bit, but I had no connectivity. LTE, 3G,H+ nothing.
- I tried installing a newer modem (this thread. Finally at MJB, I could actually get connectivity in some of the newer ROMs (including Slimkat 9)... but it was very erratic. It would just randomly oscillate between LTE and 3G and H+. This also broke CM12.1 entirely.
- Again, the above problem was always present. Most of the LP ROMs would just bootloop me, though. The only one that worked was Cyanide L... which I didn't really like.
- I thought maybe the issue was the bootloader. My bootloader is still i747ucalh9. So I tried updating it to various bootloaders from here, but none of the updates will work. Literally, they give me error 6 or 7 and pretty much essentially tell me that I can't do it.
- So after repeating the cycle of "let me try to update this" several times and having the update fail on me, I'm still stuck at Slimkat 7 as the only thing that worked on LTE (note the past tense). Worse yet, I tried simply downgrading my modem to match my current bootloader version, but that made things worse than better. I am now stuck at 3G... which just recently went back to LTE. Talk about erratic.
- I also tried going full stock by flashing this: http://forum.xda-developers.com/showthread.php?t=2363882 But it expects 5 arguments for format, and got 3... or something. Failed hard.
So, I'm pretty much at the end of my rope here. I really might just go and grab a new phone at this point. I just really don't want to because this thing still works fine.... I guess I got unlucky and am at a version of the bootloader that is difficult to update from. I can't seem to go anywhere with this thing. Anyone have any ideas? Do I need to use a different recovery?
Thanks...
First and foremost, verify your bootloader. Install the Samsung phone info app, or in a terminal app or adb shell enter:
Code:
getprop ro.bootloader
If you're on any of the older bootloaders (the ones that do not end in MJB, NE4, or NJ1) there are two ways you can go (you probably will be given the age of your modem). If you're on any of the ones that end in MJB, NE4, or NJ1 you've got to be a lot more careful because downgrading them will hard brick your phone (Odin back to stock is not an option anymore).
Option 1: If you're on the older bootloaders, you can go to sammobile.com, grab the 4.1.1 firmware from there and flash it with Odin. Do not do this if your bootloader ends in MJB, NE4, or NJ1 (can't stress that enough). This will reset your phone completely to stock. You should now start getting OTA updates. They will be incremental updates, you'll have to take at least three or four to get up to date on bootloader and modem and they're big downloads. They will come every 24 hours, but you can cheat that by setting your system time forward 1 day to make them a little more rapid fire. This is a nice, safe way to get your firmware current. Once you're up to NJ1 firmware you can use Odin to flash a custom recovery and get back to custom ROMs; I'd recommend TWRP 2.8.6 if you're going to be flashing newer ROMs as CWM and Philz aren't as up to date and sometimes give problems with newer ROMs.
Option 2: I'm pretty sure your version of CWM is a big part of your problem. If you're going to be flashing lollipop you ought to update your recovery to TWRP 2.8.6; easiest way to get it is just use the Flashify app. I'd get that recovery up to date before messing with bootloaders too. Next get your firmware up to date. If your bootloader version is before MJB, then you have to start with MJB. Then update to NE4. Then update to NJ1. It has to be done incrementally, and the bootloader and modem must match on the newer firmwares, or you'll hard brick. This thread has recovery flashable MJB and NE4 bootloaders/modems; the bootloader and modem are packaged together in the same zip so you can't get out of sync. This thread has recovery flashable NJ1 bootloader/modem. This will get your firmware all up to date, and data should start behaving on newer kitkat and lollipop ROMs. This route is a lot more risky than the OTA route described above because of all the manual steps you have to take, but you could get it done quite a bit faster if you're confident in your abilities. Just read those linked threads very, very carefully and make certain you understand.
Good luck.
jason2678 said:
First and foremost, verify your bootloader. Install the Samsung phone info app, or in a terminal app or adb shell enter:
Code:
getprop ro.bootloader
If you're on any of the older bootloaders (the ones that do not end in MJB, NE4, or NJ1) there are two ways you can go (you probably will be given the age of your modem). If you're on any of the ones that end in MJB, NE4, or NJ1 you've got to be a lot more careful because downgrading them will hard brick your phone (Odin back to stock is not an option anymore).
Option 1: If you're on the older bootloaders, you can go to sammobile.com, grab the 4.1.1 firmware from there and flash it with Odin. Do not do this if your bootloader ends in MJB, NE4, or NJ1 (can't stress that enough). This will reset your phone completely to stock. You should now start getting OTA updates. They will be incremental updates, you'll have to take at least three or four to get up to date on bootloader and modem and they're big downloads. They will come every 24 hours, but you can cheat that by setting your system time forward 1 day to make them a little more rapid fire. This is a nice, safe way to get your firmware current. Once you're up to NJ1 firmware you can use Odin to flash a custom recovery and get back to custom ROMs; I'd recommend TWRP 2.8.6 if you're going to be flashing newer ROMs as CWM and Philz aren't as up to date and sometimes give problems with newer ROMs.
Option 2: I'm pretty sure your version of CWM is a big part of your problem. If you're going to be flashing lollipop you ought to update your recovery to TWRP 2.8.6; easiest way to get it is just use the Flashify app. I'd get that recovery up to date before messing with bootloaders too. Next get your firmware up to date. If your bootloader version is before MJB, then you have to start with MJB. Then update to NE4. Then update to NJ1. It has to be done incrementally, and the bootloader and modem must match on the newer firmwares, or you'll hard brick. This thread has recovery flashable MJB and NE4 bootloaders/modems; the bootloader and modem are packaged together in the same zip so you can't get out of sync. This thread has recovery flashable NJ1 bootloader/modem. This will get your firmware all up to date, and data should start behaving on newer kitkat and lollipop ROMs. This route is a lot more risky than the OTA route described above because of all the manual steps you have to take, but you could get it done quite a bit faster if you're confident in your abilities. Just read those linked threads very, very carefully and make certain you understand.
Good luck.
Click to expand...
Click to collapse
Thanks a lot for the help! I actually did/tried a majority of this an hour or two before you posted that, except the latest firmware update link you supplied. I knew it existed and I had seen that thread before, but I couldn't dig up the link again before I had to go to work. Thing is I kind of wanted to avoid Odin for some reason but I finally gave up and used it. And yeah I already knew my bootloader version. The phone told me when it failed to update the bootloader lol.
Here's what happened thus far:
- I used Odin to flash the sammobile 4.1.1. The flashing worked just fine, but booting into it did not. It hung on the Samsung logo. So, OTA updates were out the window.
- I have no idea why, so I just used Odin to flash TWRP onto it afterwards (from here)
- I tried one of the ROMS. Data still didn't work.
- I used the thread you linked to update to MJB bootloader and whatnot. The update went fine.
- Tried another few ROMs. Data worked, but LTE was still erratic.
- Updated to NE4 and then grabbed the deoxed stock ROM.
- The deoxed stock rom failed to boot (stuck at ATT globe logo). For some reason my phone can't use stock ROMs.
- So again used Odin to put TWRP onto the phone
- Installed various LP ROMS. Again the data was erratic and plus the battery life was horrid.
- Tried getting the ktoonsez kernel. My service was murdered.
- Gave up on LP. Tried Slim 9.0. Erratic data.
- Tried Liquidsmooth 4.4.4 instead.
Currently that's kind of where I'm at. The LTE data works fine (takes a bit to get up and running after reboot though) and thus far everything is okay (though that can quickly change considering I haven't done much of anything), so I don't even know if I want to mess with it anymore. It looks like this specific ROM includes a custom kernel. So I'm guessing it's an incompatibility between the kernel and the firmware version on the other ROMs. It seems like most of the LP roms have horrible battery life (back of my phone feels like a furnace on them), so I'm not even sure if I want to do that last firmware update to use them.
It'd be kind of nice to use the OTA but apparently my ability to go stock in any form or fashion is just totally borked.
Thanks for the post though, that's pretty gold. I'm sure someone in a situation like me where they have a super old firmware will find this thread of some use as it has actual instructions and links to what you need to do to get up and running. Before you posted that, I had to go digging around pretty much everywhere figuring out what and where was going wrong.
Glad you've got it mostly working.
You might have been able to get that stock ROM to boot if you had booted into the stock recovery and run a full wipe. Touchwiz ROMs can be tough to get running after being on AOSP. As a general progression try to format internal storage with TWRP (the wipe where you have to type "yes" to confirm), if that doesn't work try a wipe with Philz, and if that doesn't work nothing, not even Odin, is effective as a wipe in the stock recovery.
Thanks for typing all this out I believe it will help me put cm12.1 official on a friends phone.
Are these the steps?
1) verify latest software
2) twrp via Odin
Alt 2) root via apk then use rashr or similar to flash twrp
3)wipe
4)In twrp install official d2att from cm website
5) install current gapps
6) profit
I'm not new to this at all but I've never even touched an att gs3 and I know most devices have their quirks and I don't want to brick.
Also does towel root work on this? I don't mind Odin but I can do this on the fly I think if I can attain root.
Sent from my DROID RAZR M using XDA Free mobile app
mrkhigh said:
Thanks for typing all this out I believe it will help me put cm12.1 official on a friends phone.
Are these the steps?
1) verify latest software
2) twrp via Odin
Alt 2) root via apk then use rashr or similar to flash twrp
3)wipe
4)In twrp install official d2att from cm website
5) install current gapps
6) profit
I'm not new to this at all but I've never even touched an att gs3 and I know most devices have their quirks and I don't want to brick.
Also does towel root work on this? I don't mind Odin but I can do this on the fly I think if I can attain root.
Sent from my DROID RAZR M using XDA Free mobile app
Click to expand...
Click to collapse
Yep. You've got it. If you're on the latest and greatest firmware I think the towelroot exploit has been patched, unless geohot has retaken the lead in that arms race.
Easiest way to root on this phone since the bootloaders are unlocked is to just use Odin to flash a custom recovery then use the custom recovery to flash SuperSU. There's just a little trick to it. Store SuperSU.zip somewhere on your phone before flashing the custom recovery. Uncheck everything but f.reset time when you use Odin; don't let it auto reboot. Upon success pull battery. Replace battery and boot straight into recovery with vol up + home + power. If you mess up and boot into unrooted stock ROM with a custom recovery it will get overwritten with a stock recovery and you'll have to Odin custom recovery back onto it and try again.
I would do this to root your stock ROM just to execute this command in a terminal app or adb shell before any more serious flashing:
Code:
su
reboot nvbackup
That fixes a derp and gives you a working efs backup on a few backup partitions built into your phone instead of a blank one. Highly recommended before doing any ROM flashing. This will just look like a pretty normal reboot. You might see a quick flash of tiny blue text if you're watching for it.
Then you're ready to make a nandroid backup (just in case), wipe, and flash away. Take a look at LiquidSmooth if you're looking for a good lollipop ROM.
Nice... So the recovery partition gets rewritten every boot up until a custom ROM is installed and the efs can disappear... This is why you always ask questions.
Thanks for the suggestion on the ROM but I think I'll stick to official cm12.1 it's not my phone and that should be a nice readily updatable bland flavor of lollipop.
Sent from my DROID RAZR M using XDA Free mobile app
mrkhigh said:
Nice... So the recovery partition gets rewritten every boot up until a custom ROM is installed and the efs can disappear... This is why you always ask questions.
Click to expand...
Click to collapse
At the Android 4.3 update it was noticed that flashing a custom recovery would be overwritten by the stock recovery on the initial reboot unless following the method Jason described. Another solution was to delete two lib or .so files. On devices still on stock recovery, stock recovery does not overwrite itself.
There is a blank EFS partition on the device intended for a backup. The nvbackup command populates that partition with an image which will rebuild your EFS if it is lost during a modem update or ROM flash. The loss of EFS does happen. I believe wanam, of the xposed module fame, created an EFS backup tool for Samsung devices. I don't believe he updates it any longer because he rolled the functionality into a partition backup tool, the later is in the PlayStore listed under a different creator name, yet it's still him.
So I'm finally going to take the plunge, and update my boot loader/modem.. I never messed with it because all the Roms I used always worked.. I want to try lollipop, but due to old bootloader my phone won't boot with those Roms..
I'm on UCDLK3 bootloader/modem.. I know I have to upgrade to MJB, NE4, then NJ1 in that order in increments..
So my question: can I upgrade from LK3 straight to MJB with out any problems?? Or is there something I need to flash before I can get to MJB?? I think I can go straight to MJB, but better safe then sorry..
I know downgrading after upgrade most likely will brick.. Any information is appreciated... Oh, its an ATT I747..
coolwhipp420 said:
So I'm finally going to take the plunge, and update my boot loader/modem.. I never messed with it because all the Roms I used always worked.. I want to try lollipop, but due to old bootloader my phone won't boot with those Roms..
I'm on UCDLK3 bootloader/modem.. I know I have to upgrade to MJB, NE4, then NJ1 in that order in increments..
So my question: can I upgrade from LK3 straight to MJB with out any problems?? Or is there something I need to flash before I can get to MJB?? I think I can go straight to MJB, but better safe then sorry..
I know downgrading after upgrade most likely will brick.. Any information is appreciated... Oh, its an ATT I747..
Click to expand...
Click to collapse
Since you are on LK3 you may want to considr applying the free sim/carrier unlock method before upgrading; that is if you are on stock LK3 and you have not previously carrier unlocked your device.
There was an OTA release for the MG2 stock ROM, I believe that was 4.1.2. You may want to go to that before MJB. Did you make the nvbackup suggested by Jason?
Why would I do a carrier unlock, if I'm not switching carriers?? And if I do it, will I be able to use the same carrier?? Just seems like a waisted step for me.. But idk..
Jason's first post, option 2 is how I was planing to update.. And no, I haven't done the nvbackup yet.. How would I apply that backup if things go wrong? Not really sure what a nvbackup is..
Any information is appreciated..
coolwhipp420 said:
Why would I do a carrier unlock, if I'm not switching carriers?? And if I do it, will I be able to use the same carrier?? Just seems like a waisted step for me.. But idk..
Jason's first post, option 2 is how I was planing to update.. And no, I haven't done the nvbackup yet.. How would I apply that backup if things go wrong? Not really sure what a nvbackup is..
Any information is appreciated..
Click to expand...
Click to collapse
There is a command to manually trigger the restore routine. I think it's
Code:
reboot nvrestore
but don't hold me to that. I'd never execute that command except if in dire need. The problem with this phone is there is an automatic routine that can be triggered in the event of a bad flash that will overwrite your nvram with the backup, even if the backup is blank. I don't think the backup stores anything modem specific, but I've never been able to confirm that. So I've always done it again after updating modems (only had to once).
Having the phone sim unlocked can be nice if you plan on traveling internationally. Otherwise, potential future carrier hopping or added resale value are the only reasons to do it.
coolwhipp420 said:
Why would I do a carrier unlock, if I'm not switching carriers?? And if I do it, will I be able to use the same carrier?? Just seems like a waisted step for me.. But idk..
Jason's first post, option 2 is how I was planing to update.. And no, I haven't done the nvbackup yet.. How would I apply that backup if things go wrong? Not really sure what a nvbackup is..
Any information is appreciated..
Click to expand...
Click to collapse
If you will never be switching carriers, nor ever sell/give/trade the phone to someone who will switch, then it is an unecessary step to do the carrier unlock.
I see Jason beat me to answering both of your questions.
I've got a different issue here. I was running SlimKat 4.4.4 with BMS kernel on my d2att. I was on the CUEMJB Bootloader and Modem, so I thought that I can directly flash the rom. First, what I did was flash UCUEMJB_to_UCUFNE4_Firmware_update.zip. It flashed perfectly till the end. Then I flash the I747UCUFNE4_Stock_Rooted_Deodex_3-31-15.zip, which had an error that I had forgotten. It apparently is caused by my BMS kernel, so I went on and reinstall SlimKat 4.4.4 to remove the kernel. It flashed perfectly, but when I rebooted my phone, it did not power on. I was thinking, what's inside the UCUEMJB_to_UCUFNE4_Firmware_update.zip, are they the bootloaders and modem for CUFNE4 ? If so, is my phone dead like all the others who flashed 4.4.2 modem over 4.3 ? Please, I need my phone bad.
Did you follow this thread: http://forum.xda-developers.com/showthread.php?t=2789917 ?
Since you were already on the mjb bootloader, you flashed the UCUEMJB_to_UCUFNE4_Firmware_update.zip file? Any errors when flashing this?
Before installing NE4 firmware, did you do a full wipe as instructed in step 3 of the thread I linked?
audit13 said:
Did you follow this thread: http://forum.xda-developers.com/showthread.php?t=2789917 ?
Since you were already on the mjb bootloader, you flashed the UCUEMJB_to_UCUFNE4_Firmware_update.zip file? Any errors when flashing this?
Before installing NE4 firmware, did you do a full wipe as instructed in step 3 of the thread I linked?
Click to expand...
Click to collapse
Hey yeah. No errors occurred when I flashed it. The only I have gotten was from the OTA update zip itself. I can't remember what it is, but it prevented me from updating my phone to UCUFNE4. So I reinstalled Slimkat and booted properly but at the time I've rebooted, it's all dead.
And also, yes. That is the post that I've followed. I checked if my bootloader and modem are CUEMJB, and they are. So I figured that the firmware update should've not ruin it.
NOTE : I am running on a debrick card UCUEMJB if that helps with the information. I can't seem to boot off the eMMC itself, so I always kept the SD card on the slot. That, until it died.
I really think that my bootloader is messed up because of the UCUEMJB_to_UCUFNE4_Firmware_update.zip. I think it borked my bootloader, that's why I can't use any debrick images to recover it. Please, help. I'm short on funds, and losing this phone is a big cut on my budget.
I heard that the i747m users recovered theirs by pulling out the 128mb file. So if any of you i747 users running at the NE4 version could just pull out the bootloader partition, that would be great. enewman's debrick doesn't seem to work for me.
The bootloader for the i747 and i747m are not compatible even though they phones appear to have the same hardware.
So the phone does not boot at all with the mjb debrick image?
audit13 said:
The bootloader for the i747 and i747m are not compatible even though they phones appear to have the same hardware.
So the phone does not boot at all with the mjb debrick image?
Click to expand...
Click to collapse
It does not. Not even with the 4.4.2 debrick image. Help
If it used to boot with the debrick image and it doesnt boot now, a jtag service may be the only way to revive it.
May I just know what happened to my phone before it had gone bananas? A little information might help. Also, Im planning to buy a board for T999. Will it fit with the I747 chassis ?
I really don't know what happened to cause this problem with your phone. When flashing a phone, there is always an element of risk. I have pooched a few phones in my life too. I even damaged a couple of sim slots by using sim adapters too.
When your phone was able to boot with the debrick image, you could have tried reflashing the mjb bootloader and modem but it's a moot point now.