My phone finally passed the one year mark - no more warranty now so naturally, it's time to root and have some fun. I got root and bought the latest CWM touch recovery and have it installed and functioning properly. However, when I try flashing the latest CM10.1, I get a status 7 error. I've read all kinds of things about the phone being classified as a d2can, not d2att and changing the build.prop or update script but haven't the slightest clue as to how to do it. All the threads I've searched vaguely say how the people bypassed this error and not how to do it. I never ran into this problem with my old Optimus G2X so this is foreign land to me.
So I have a Bell GS3 i747M running the latest (rooted) 4.12 i747MVLDMF1 update with CWM 6.0.3.1. I'm also running Windows 7 if that makes any difference.
If anyone can help me out I'd really appreciate it!
Thanks,
Spike
53Spike said:
My phone finally passed the one year mark - no more warranty now so naturally, it's time to root and have some fun. I got root and bought the latest CWM touch recovery and have it installed and functioning properly. However, when I try flashing the latest CM10.1, I get a status 7 error. I've read all kinds of things about the phone being classified as a d2can, not d2att and changing the build.prop or update script but haven't the slightest clue as to how to do it. All the threads I've searched vaguely say how the people bypassed this error and not how to do it. I never ran into this problem with my old Optimus G2X so this is foreign land to me.
So I have a Bell GS3 i747M running the latest (rooted) 4.12 i747MVLDMF1 update with CWM 6.0.3.1. I'm also running Windows 7 if that makes any difference.
If anyone can help me out I'd really appreciate it!
Thanks,
Spike
Click to expand...
Click to collapse
Hi there, just would like to direct you to the Q&A forum as this thread belongs there, just a heads up so you know where to find it when it get's moved by a forum moderator, so for next time now you know where this kind of post belongs
Have you updated to the latest bootloader? what was the last stock firmware you flashed in odin?
also to edit build.prop for newer users, easiest way would be to download rom toolbox and inside there is a feature for "build.prop" edit,
changed I747M to I747, d2can to d2att and d2uc to d2v1 in the first few lines of the build.prop then save and reboot. once you are rebooted update you're recovery to get a d2att recovery.
cheers
Please read forum rules before posting
Questions and help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Danvdh said:
Hi there, just would like to direct you to the Q&A forum as this thread belongs there, just a heads up so you know where to find it when it get's moved by a forum moderator, so for next time now you know where this kind of post belongs
Have you updated to the latest bootloader? what was the last stock firmware you flashed in odin?
also to edit build.prop for newer users, easiest way would be to download rom toolbox and inside there is a feature for "build.prop" edit,
changed I747M to I747, d2can to d2att and d2uc to d2v1 in the first few lines of the build.prop then save and reboot. once you are rebooted update you're recovery to get a d2att recovery.
cheers
Click to expand...
Click to collapse
Thanks for telling me about the proper forum location and I apologize for a late reply, work got hectic the last couple of days, but alas, the long weekend is ahead!
I've updated my phone to the most recent Bell stock build so I'd assume the bootloader is recent as well. I then flashed the most recent stock ROM with root injected from here: http://forum.xda-developers.com/showthread.php?t=1739426 so build I747MVLDMF1.
With regards to the build.prop changes, I selected the d2att CWM recovery when I went to install one so I figured installing the d2att recovery would do the same as changing the build.prop parameters then installing the d2att recovery, no?
Thanks,
Spike
I just want to bump this in case anyone can help me out.
Related
So I am running the stock rom but have root access. the update pops up every 5 minutes to remind me to install it. I let it install and about 3 second in i get a yeild sign with an exclamation point in it. and the phone stops there. I waited for about 3 hours and nothing happened. Anybody know what I need to do here? I used Galaxy Nexus root toolkit v1.3 to root my phone. BTW i am with verizon
For as far as i now you cant update a rooted device. i sugest unrooting an try to update agian.
reply
yea that's what I thought I was going to have to do. but wanted to see if there was an update package someone had made for rooted devices like some others had.
nvm i think im going to trade the phone
So no one has an answer on this?
jordi97 said:
For as far as i now you cant update a rooted device. i sugest unrooting an try to update agian.
Click to expand...
Click to collapse
Yes you can. You can't update a phone with CWM recovery though.
Sent from my Galaxy Nexus using xda premium
Correct a rooted phone can update but not with any custom recovery. You need to flash back to the factory stock recovery.
Sent from a phone...
OK so looks like everyone is here was incorrect. The 4.04 rooted update is here in the XDA forums all i needed to do was flash it and the new antenna and everything is working fine now. here are the links.
4.04 http://forum.xda-developers.com/showthread.php?t=1631796
radio http://forum.xda-developers.com/showthread.php?t=1630438
Thank you Brandon for helping me out with this.
There are no stupid questions only stupid answers.
Sdalton19 said:
OK so looks like everyone is here was incorrect. The 4.04 rooted update is here in the XDA forums all i needed to do was flash it and the new antenna and everything is working fine now. here are the links.
4.04 http://forum.xda-developers.com/showthread.php?t=1631796
radio http://forum.xda-developers.com/showthread.php?t=1630438
Thank you Brandon for helping me out with this.
There are no stupid questions only stupid answers.
Click to expand...
Click to collapse
Your right, stupid answers, that's not an ota update you did. That was pulled from a phone which was updated and packaged into a flashable file to use on a rooted device. But a carrier ota update as your device was asking you to update will not work without stock recovery.
Sent from a phone...
Isn't that exactly what i asked for second post in? Point is if you knew that, why didn't you say so? Look there's nothing wrong with being wrong every once in a while but be graceful about it. And if your going to give advice make sure you fully read the question and offer decent advice. You were saying there was no way to update it without unrooting and flashing back to stock. That was after I asked "yea that's what I thought I was going to have to do. but wanted to see if there was an update package someone had made for rooted devices like some others had." Is that not exactly what I asked for????
Sdalton19 said:
Isn't that exactly what i asked for second post in? Point is if you knew that, why didn't you say so? Look there's nothing wrong with being wrong every once in a while but be graceful about it. And if your going to give advice make sure you fully read the question and offer decent advice. You were saying there was no way to update it without unrooting and flashing back to stock. That was after I asked "yea that's what I thought I was going to have to do. but wanted to see if there was an update package someone had made for rooted devices like some others had." Is that not exactly what I asked for????
Click to expand...
Click to collapse
Well, you are right that there are a lot of partially right and partially wrong answers in this thread. But what are you saying is not exactly right either.
1) There is a difference between updating your existing build (like what you had asked to do in the first post) and flashing an entirely new build.
2) There is a difference between running a stock ROM (like what you were running before) and running a ROM that looks like it's stock, but is not (like what you are running now).
3) Root has NO impact whatsoever on your ability to install OTA updates on your stock ROM.
4) An OTA update will NOT install with a stock recovery UNLESS you are using the stock recovery version that came with the build you are using. (It seems like a lot of toolkits are flashing non-matching stock recoveries).
5) An OTA update file can EASILY be installed if you have CWM installed. See here.
6) Your phrase "unrooting and flashing back to stock" is silly, as flashing back to stock replaces your ROM, so why would you need to "unroot" your current ROM only to flash a stock ROM overtop? You don't root a device - you root an Android OS build. The phrase "root my device" does not make any sense.
Okay i am not new to flashing and rooting but i am really stuck right now lol, i bought my galaxy S3 two days ago and i wanted to root it and flash cm 10.1 on it.. i got it rooted and flashed the recovery and every time i load up the recovery it shows that's it cannot get the partition size and cannot read/write cache.. am i doing something wrong? I used the Samsung GS3 toolkit V.7.0.0 and even downgraded the firmware from 4.1.2 to 4.1.1 thinking that it was the root of the problem but that didn't work either.. I also noticed that when i flashed the TWRP recovery it prompted me to use a password as if the cache is encrypted..
any advice would be great!
(P.S. if there is already a thread that i haven't found about on this topic sorry!)
The new S3 have added security measures built in by Samsung or Sprint but the recoveries had to be modded in order for them to work. It appears to affect newer than 2 months. Here is the thread you will need http://forum.xda-developers.com/showthread.php?p=44262749 also CM roms or AOSP style roms seem to not flash. There's something they have to figure out what else was modded on the new phones.
And yes there's been a whole help of threads on this topic, most locked by mods as this has been covered in the threads for the recoveries themselves.
Sent from the future via Tapatalk 4
edfunkycold said:
The new S3 have added security measures built in by Samsung or Sprint but the recoveries had to be modded in order for them to work. It appears to affect newer than 2 months. Here is the thread you will need http://forum.xda-developers.com/showthread.php?p=44262749 also CM roms or AOSP style roms seem to not flash. There's something they have to figure out what else was modded on the new phones.
And yes there's been a whole help of threads on this topic, most locked by mods as this has been covered in the threads for the recoveries themselves.
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
Awesome thank you so much I was thinking that I messed up and locked my phone
So it's been a while since I last rooted a phone. Last time I rooted my phone was back when I had my GS1.
I have the Sprint L710, hence why I'm posting here.
I believe I've successfully rooted my phone as Root Checker says so.
Anyway, I want to flash ROMs but I've forgotten how to do them now.
Is the next step installing CWM? If so, can anyone find me the thread or links on how to do it?
I've completely lost touch on how to do these things. I'm just hoping someone would be able to help me out as I type this out.
SPH-L710
4.1.2
Kernel version - 3.0.31-1130792
Thanks in advance!
If you have a new s3 then you need to use one of these recoveries, flashed through odin
http://forum.xda-developers.com/showthread.php?t=2391616
New recoveries for new phones that won't mount storage!!
Other than that, the process for flashing a rom has not changed.
I've got a t999 (not LTE) with UVDMD5 build running 4.1.2. I have been trying all evening to root for the first time, but I just can't seem to get it. I first went with High On Android's method and all went smoothly until I tried to open the .zip file in ClockworkModRecovery - phone just goes into plain old Android recovery mode.
I thought downloading mskip's Unified Toolkit would solve all my life's problems, but 7.0 doesn't appear to support my particular model and the comments about how to get version 7.5 may as well be in German for all I understand. I've searched all over the forums and found similar issues, but the ones I've seen with replies were equally difficult to understand. I'm still pretty nooby here.
I don't care about resetting the counter - I don't have any kind of warranty to deal with. Has someone rooted a t999 running 4.1.2 who can help me figure out what I'm doing wrong in plain English?
Download and flash the MD5 firmware from here http://forum.xda-developers.com/showthread.php?t=1949687 and flash it with Odin
Sent from my SGH-T999 using Tapatalk
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 .