My phone is a 4.3 official Samsung and is properly rooted. I have downloaded CM13 and Gapps onto my external SD card and went into CWM recovery mode. I firstly backed up everything (thankfully) and performed a wipe data/factory reset followed by installing CM13. However when I run CM13 almost immediately an error pops up saying "this package is not for device: this device is d2spr" along those lines. Any help would be appreciated; thanks!
BTW forgot to mention I completely removed Knox from my phone so that I could root it.
I had a similar issue, but with TWRP. As I have a Canadian S3, so I downloaded the "d2can" build of TWRP.
When I tried to flash the CM13 "d2tmo" package, it resulted to an error, saying that it cannot install the package as my device was a "d2can".
I did a quick search on Google to find out that, for TWRP at least, both recovery and package device must match. Maybe a wrong version of the recovery was installed in your case?
Did you use CyanogenMod app? From memory, it seems you can edit the device name. Try to change it to "d2tmo" as explained on the CyanogenMod SGS3 FAQ (search "SGS3FAQ" on Google).
The "d2can" is the moniker for the s3 from Rogers, Telus, and Bell and the d2att is the moniker for the AT&T version of the s3.
The s3 development for the d2can and d2att was unified into the d2lte.
The cm13 for the d2tmo is not installing because the updater script is looking for a particular model.
Did you try flashing twrp for d2tmo?
audit13 said:
The "d2can" is the moniker for the s3 from Rogers, Telus, and Bell and the d2att is the moniker for the AT&T version of the s3.
The s3 development for the d2can and d2att was unified into the d2lte.
The cm13 for the d2tmo is not installing because the updater script is looking for a particular model.
Did you try flashing twrp for d2tmo?
Click to expand...
Click to collapse
Actually, it seems (based on the page "Information: Samsung Galaxy S III LTE ("d2lte")" in the CyanogenMod Wiki) that S3 development was unified into "d2lte" only between CyanogenMod 11 M3 and M12 releases.
The SGS3FAQ page refers explicitly to the "d2tmo" build for the SGH-T999 and SGH-T999V for CM 12.1 and newer releases.
Hmm, seems that cyanogen has gone back to using d2att for newer releases as indicated here: https://download.cyanogenmod.org/?device=d2att
The i747 and i747m should work on d2att builds.
That wiki page was last updated in February, 2014?
I used to have an s3 from wind and I used twrp for the d2tmo to flash ROMs.
audit13 said:
The "d2can" is the moniker for the s3 from Rogers, Telus, and Bell and the d2att is the moniker for the AT&T version of the s3.
The s3 development for the d2can and d2att was unified into the d2lte.
The cm13 for the d2tmo is not installing because the updater script is looking for a particular model.
Did you try flashing twrp for d2tmo?
Click to expand...
Click to collapse
Yeah I just tried with d2tmo, same results. I went to download the d2spr and flash it onto my phone and it worked. Turns out my phone has misleading stickers saying that it is a T model brand; it turns out it is a sprint. So after wiping out my phone completely, including davlik cache and cache partition. After this I flashed Gapps 6.0 ARM and rebooted my phone. After this a bunch of errors start popping up in the setup phase that play store has crashed and google frameworks has crashed etc. The apps are not there in my applications so I can't mess around with the settings and also I am locked out of most of my applications which suddenly crash followed by a rude avalanche of google apps crashing messages. Further assistance is required <3 I am a newbie at this so please be gentle.
Oh and if it helps, I cannot access file manager at all without crashing. So... Yeah.
Does the sprint phone have a locked bootloader? Probably not if it took twrp.
Maybe flash back to stock if possible with Odin and start over?
audit13 said:
Does the sprint phone have a locked bootloader? Probably not if it took twrp.
Maybe flash back to stock if possible with Odin and start over?
Click to expand...
Click to collapse
I would try that thanks. Will tell you results bu tomorrow; kinda busy now
Ok it still doesn't work; after rebooting to the old stable os and then to CM13 is fine, but gapps is still screwing up big time. Any suggestions?
Have you tried different versions of the cm13 gapps?
audit13 said:
Have you tried different versions of the cm13 gapps?
Click to expand...
Click to collapse
Yeah I have, recovery mode just won't boot it at all saying that it is not compatible, and then it would abort then soft brick my phone in a never ending booting loop. So yeah, not fun. I tried installing the gapps of a different version; so far I have only used pico which resulted in the rom working, but all google applications would just crash continuously making it unbearably annoying to do anything with the popup screens.
I have tried micro however it would continuously reboot over and over for about 15 min so I can almost assume that it doesn't work so I reinstalled the stable 4.3 android version that I am at now.
Despite going through hell I have learnt a lot. However I want to get this done so I can enjoy the custom rom. Yet again any more suggestions please bring it up, thanks!
Try banks gapps?
audit13 said:
Try banks gapps?
Click to expand...
Click to collapse
I'll give that a go hang on....
It didn't work. While I was flashing it, it would say:
Finding update package...
Opening update package...
Installing update...
Installation aborted
Any more suggestions ?
This is my screen. The files have somewhat installed but are stored elsewhere?
http://imgur.com/a/v3cIW
http://imgur.com/jrVq6Nd
Hey guys thanks for everything. The problem was solved by installing a different twrp. The old one I was using was apparently corrupted and screwed up my current phone, heh the chances of that?? Lots of love <3<3<3
Related
Hello,
I got this problem trying to install RC4 and RC5 as well, but now still getting it with the fresh CM10.1.0 update. I am running CWM 6.0.3.1 and tried updating CM but got the status 7 error due to the asserts. I checked md5 just to be sure and made sure I have proper d2att file for my phone. I went in and manually removed the 2 assert lines in the beginning of the updater-script file and zipped back up and tried to flash again but now I just get "installation aborted..." right after "installing update..." with no explanation or error at all.
I tried searching, got nothing, anybody seen this before?
Thanks,
J
madtorq said:
Hello,
I got this problem trying to install RC4 and RC5 as well, but now still getting it with the fresh CM10.1.0 update. I am running CWM 6.0.3.1 and tried updating CM but got the status 7 error due to the asserts. I checked md5 just to be sure and made sure I have proper d2att file for my phone. I went in and manually removed the 2 assert lines in the beginning of the updater-script file and zipped back up and tried to flash again but now I just get "installation aborted..." right after "installing update..." with no explanation or error at all.
I tried searching, got nothing, anybody seen this before?
Thanks,
J
Click to expand...
Click to collapse
Are you on a Canadian carrier?
Sent from my SGH-I747 using xda app-developers app
Nope, southern california ATT.
I edited using vim and did it cleanly, no chance of a carriage return or something stupid contributing to this.
Are you on the proper bootloader?
mrhaley30705 said:
Are you on the proper bootloader?
Click to expand...
Click to collapse
I have tried running the zip manually from recovery mode in CWM, tried installing it from Rom Manager where it reboots and automatically selects it and I have tried directly from the CM10 update button within the About Phone settings menu.
Is that what you are referring to?
No. Have you installed the jelly bean bootloader? If not, you will need to update them before cm, or any aosp based Rom, will install.
Also, you need the latest modem too.
mrhaley30705 said:
No. Have you installed the jelly bean bootloader? If not, you will need to update them before cm, or any aosp based Rom, will install.
Also, you need the latest modem too.
Click to expand...
Click to collapse
I do not follow, what is the jelly bean bootloader? I understood it to be an alternative to CWM? Why have I been able to flash every update for CM10 until this?
Link to this jelly bean bootloader update?
Bootloaders are not a type of recovery. Perhaps you should read through this:
http://forum.xda-developers.com/showthread.php?t=1903437
Then this:
http://forum.xda-developers.com/showthread.php?t=2292957
madtorq said:
Hello,
I got this problem trying to install RC4 and RC5 as well, but now still getting it with the fresh CM10.1.0 update. I am running CWM 6.0.3.1 and tried updating CM but got the status 7 error due to the asserts. I checked md5 just to be sure and made sure I have proper d2att file for my phone. I went in and manually removed the 2 assert lines in the beginning of the updater-script file and zipped back up and tried to flash again but now I just get "installation aborted..." right after "installing update..." with no explanation or error at all.
I tried searching, got nothing, anybody seen this before?
Thanks,
J
Click to expand...
Click to collapse
I have the same problem. Guess I'll never get 10.1, because it looks like you have to put a new bootloader on it, not sure why, and it risks a hard brick. It doesn't make any sense to require a new bootloader, seeing as I already have cyanogenmod 10, but the devs chose that for their reasons. I really want the camera in 4.2.
Well, if you've flashed any of the stock ROMS here, rooted or not rooted, you've flashed bootloaders.
well I guess I am confused. I am currently running cm-10.1-20130411-EXPERIMENTAL-d2att-M3.zip with the same bootloader I flashed with Odin back when I got the phone in september 2012. My roomate got the same phone except on sprint and we flashed his with the appropriate CM10.1 experimental release for the sprint phone. Since then we both have been updating via the built in CM updater and he has been able to go to the new stable CM 10.1.0 release today and has not flashed any new boot loader or anything, just updated CWM like I did.
So my question to you mrhaley30705, which no amount of searching or reading links has helped me thus far, is this something specific to the ATT version of the Galaxy S3? I do not understand what changed and why he can do it and I cannot.
More importantly, will flashing the newer boot loader you suggested require a wipe of everything? The only post actually referencing this for my phone is http://forum.xda-developers.com/showpost.php?p=41503727 and it is vague to say the least.
Your answers are much appreciated.
Here is the screen shot of what was posted on g+ by cm. I would say he is on the new bootloader. If you check the second link I posted above, there's a way to tell which bootloader you and your buddy have.
It doesn't wipe anything. You'll probably never notice the difference, with the exception of being able to run aosp based ROMS
thank you, that is informative, but still leaves me confused since I am running 4.2.2 (although the build is before that May release) and I am currently running I747UCLH9.
Checking my roomate's phone he is running XXXXXXLJ7 so either he started with a newer one or something. I guess that clears it up. Also, this thread was very helpful incase anybody searches and stumbles on my posts: http://forum.cyanogenmod.com/topic/73407-how-to-update-bootloader-and-do-i-need-to-do-this/
Have a N7105T on stock 4.1 + root + Philz Touch CWM, and am having trouble flash ROM's other than HashCheck (4.1).
Have tried PACMAN all-in-one (4.3) and Omni (4.4) as both 'N7100' and 't0lte' variants, with similar results for both.
The N7100 variants install but mobile not recognised.
The t0lte variants refuse to install. From what I can tell, it is failing to assert it is on a N7105T. EDIT: The Omni 4.4 ROM reports that I am 't03g'.
My process in each of these cases has been to perfom the installs from recovery: wipe/factory reset (clean for ROM), install zip, install google apps, wipe cache, wipe dalvik, boot to rom. I have an IMEI backup using the QPST tool.
I'm not touching modems at this stage. Also haven't run a stock 4.3 rom yet.
Others are obviously on 4.3/4.4 custom ROM's. I've been scouring xda for help but can't find the relevant advice. What am I doing wrong?
EDIT: after seeing the Omni assert failure reporting 't03g' it now appears 't03g' matches the N7100, but I definitely have a N7105T. Refer: link autoroot.chainfire.eu and teamw.in/project/twrp2/115 where t03g is N7100 variant. As the t0lte ROM variants are aborting due to failing their asserts to identify my phone, is this a ROM build problem? Can't ask this in the dev section because despite being a 3 year member, haven't needed to post before. Can anyone suggest what info I could get from my phone that may be used by the ROM's to identify my phone?
SOLVED: PACMAN and OMNI ROM's hardware assertions for t0lte not including my N7105
norkle said:
Have a N7105T on stock 4.1 + root + Philz Touch CWM, and am having trouble flash ROM's other than HashCheck (4.1).
Have tried PACMAN all-in-one (4.3) and Omni (4.4) as both 'N7100' and 't0lte' variants, with similar results for both.
The N7100 variants install but mobile not recognised.
The t0lte variants refuse to install. From what I can tell, it is failing to assert it is on a N7105T. EDIT: The Omni 4.4 ROM reports that I am 't03g'.
Click to expand...
Click to collapse
Well it would appear the t0lte ROMs failing install at the assertion were the clue. The Omni ROM provided helpful information by advising I had a t03g (N7100) leading me to guess it wasn't detecting correctly.
Went into the Omni t0lte nightly ROM and modified the update-script to include 't03g' in the assertions (note: this is dangerous - t03g is normally the non-LTE N7100's) and installed using PhilzTouch recovery (with gapps and own modem). Modem and WiFi working beautifully, baseband being correctly detected etc. For anyone copying me, remember I had used the QPST to make an IMEI backup and am comfortable working with Odin/recovery etc.
Now, can anyone point me in the right direction to helping identify why my phone variant was failing the assertions, and who I should contact to update ROM's? I presume they are working on something common upstream, eg. CM.
another post
156 views and no input. A guy could feel like a ghost around here.
29445236
I would really appreciate some input on this. Anyone know the likely point of call for fixes in identifying N7105T vs N7105/N7100?
Finally worked out the problem was a N7100 recovery on a N7105 device. Updated recovery, worked and installed ROM, all better.
Info in case others make the same mistake.
Hey Guys,
I just got a new Samsung Galaxy S3 SGH-I747 in the mail and I immediately started to install Cyanogenmod. I have installed it on two S3's in the past, but this time I had no idea about the new bootloader problems after Android 4.3 (I think?). I got CWM touch installed with no problems via Odin, but when I tried to use the Unified Android Toolkit thing to root and stuff I got stuck in a boot loop. The phone would not boot past the Samsung logo, not the animated one with the purple light, but the one that shows the phone model.
I have tried everything I could think of and all that I tried to google for the past couple hours to no avail. I stupidly did not make a backup of my stock ROM, and I couldn't find a stock 4.4.2 ROM except this one that says it is stock but with root. I flashed that ROM and then it booted past the Samsung logo and the animated one, but is now stuck on the AT&T logo. I looked up that problem and couldn't find any real information on that problem except one thread where it said I should install Kies and let it do the Firmware Upgrade and Initialisation option. That failed and then my phone would only turn on straight to download mode.
I reflashed CWM and that worked so I thought that if I tried to install Cyanogenmod 11 it might work because that ROM is 4.4.1 or higher (Again, I think?). Now it's back into the loop where it makes it past the samsung stuff but then gets stuck on the AT&T logo. Is there anything I can do?
Thanks,
Jemimacakes
Did you try wiping cache, data, and Dalvik in CWM?
Did you try installing CM10.2 from CWM?
audit13 said:
Did you try wiping cache, data, and Dalvik in CWM?
Did you try installing CM10.2 from CWM?
Click to expand...
Click to collapse
Yes, I have tried clearing stuff in both CWM and stock recovery. Im not sure about the Dalvik one though, unless that is cleared when you do factory reset and clear cache I didnt do it. I can try flashing CM10.2 ( which I would prefer to have over 11), but my understanding is that my boot loader will not let me install anything that uses any lower versions of android, but I'll give it a shot and let you know.
Ok guys,
I tried to install Cyanogenmod 10.2 and when I put it on my sd card and tried to install it with CWM It threw and ton of errors that look like this.
assert failed: getprop("ro.bootloader") == "I747UCDLK3" || getprop("ro.bootloader") == "I747UCDMG3" || etc etc.
Im not super experienced with programming, but im guessing that CM10.2 can find any bootloader it can use? Im not sure what my bootloader is if that is the case, but I can boot into recovery so I must have something, right?
Anything I can do?
Thanks
Jemimacakes
You should try flashing cm10.2 just to see if you can get your phone to boot. By booting the phone, you can determine your bootloader and modem.
Edit: okay, cm10.2 doesn't work. Are you running the latest version of cwm? Maybe try twrp?
Hey,
I did have the latest version of CWM, but I tried it on TWRP and got the same errors
audit13 said:
You should try flashing cm10.2 just to see if you can get your phone to boot. By booting the phone, you can determine your bootloader and modem.
Edit: okay, cm10.2 doesn't work. Are you running the latest version of cwm? Maybe try twrp?
Click to expand...
Click to collapse
Hey,
I have now tried both custom recoveries and gotten the same errors on both, and I made sure I had the latest version of each. Can I flash the firmware from 4.3 and then install CM10.2? Will that work? I really don't want to hard brick my phone.
EDIT: I installed ADB to find out what my bootloader was, and it returned that I had the NE4 version. Is there a way to get the MJB version safely so I can install 10.2?
At this point I just want it to boot up to anything, so if that is easier to do than get CM to work then im completely open.
You cannot go back to MJB from NE4.
How did you try to install CM the first time? Did you use the install manager or a custom recovery?
The last time I installed CM on a i747 was back when the phone was on 4.1.1. The second phone I installed it on was the international version of the phone, also on 4.1.1. I used a custom recovery both times. I bet if I would have used the new installer on this phone it would have worked, but I was trying some other stuff because I was curious and ended up breaking it.
IT BOOTED!
I reflashed the stock firmware + root, reinstalled stock recovery and wiped everything I got it to boot into its stock ROM. From this point, where do I go? Will the CM installer work or will it just brick it again?
Thanks
Jemimacakes
I would copy a custom rom such as cm11 to the internal and external sd card.
I would then download the latest version of philz touch for the d2lte. Get Odin 3.07. Put the phone in download mode, open Odin, uncheck all options except f reset time. Flash philz, when you see reset in the status window, remove USB cable, remove battery, insert battery, boot into recovery, create a nandroid of your current rom, flash cm11, wipe cache, wipe data, wipe dalvik, reboot.
audit13 said:
I would copy a custom rom such as cm11 to the internal and external sd card.
I would then download the latest version of philz touch for the d2lte. Get Odin 3.07. Put the phone in download mode, open Odin, uncheck all options except f reset time. Flash philz, when you see reset in the status window, remove USB cable, remove battery, insert battery, boot into recovery, create a nandroid of your current rom, flash cm11, wipe cache, wipe data, wipe dalvik, reboot.
Click to expand...
Click to collapse
Which version of CM11 should I get. On the site I see that the last version of CM11 for the I747 (d2att) was released on feburary 16, is this one based on 4.4.2?
EDIT: Also, I should copy CM11 to both the internal and external storage? Why is this?
You should be using roms made for the d2lte.
I suggest both because cwm or twrp may see one but not the other. This doesn't usually happen but I am always paranoid about something going wrong as flashing always involves risk and I like to minimize risks and be prepared for disaster.
audit13 said:
You should be using roms made for the d2lte.
I suggest both because cwm or twrp may see one but not the other. This doesn't usually happen but I am always paranoid about something going wrong as flashing always involves risk and I like to minimize risks and be prepared for disaster.
Click to expand...
Click to collapse
Alright, but I have the at&t version of the phone. Are they both compatible with one another?
EDIT: OK, correct me if im wrong, but my new understanding is that CM now has releases for general versions of phones, so the most recent update of CM for my phone is the d2lte, not d2att?
Before unified builds for the msm8960 were started, the i747 was known as the d2att and the i747m was known as the d2can.
audit13 said:
Before unified builds for the msm8960 were started, the i747 was known as the d2att and the i747m was known as the d2can.
Click to expand...
Click to collapse
Hello again,
Thanks a ton Audit, my phone is up and running with the latest cyanogen nightly! A recap for anyone who might come across with a similar problem.
1. I installed a ROM using an older version of android onto a phone with the new bootloader (NE4), softbricking it.
2. I installed the stock ROM + root from this link using Clockworkmod
https://www.androidfilehost.com/?fid=23501681358550126
3. Installed the stock Recovery from this link and did wiped my data and both caches
https://www.androidfilehost.com/?fid=23681161096070493
4. I rebooted the phone and waited at the AT&T logo for a while, and it booted up normally!
5. I installed the most recent version of Philz Touch Recovery for the d2lte, made a nandroid for safety, and then install the latest nightly of CM11 for the d2lte.
6. It works!
Thanks again to Audit for helping me out!
Jemimacakes
I'm glad it all worked and I was able to help in some way.
It's great that you posted your solution in case it helps other people in a similar situation.
I think i'm in a similar place - a few questions. You used cwm to install the stock ROM? I thought you needed to use odin. Also, why did you need to install the stock recovery (and did you just flash the .zip in cwm)? Also, that stock rom you linked to is 4.4, right? Would that work if I was on 4.3?
Before flashing anything, I suggest you confirm your bootloader and modem. Flashing the wrong combination of modem and bootloader could hard brick your phone.
If your phone does not boot, try flashing Philz Touch for the d2lte and flash the latest cm11. Hoepfully, this will get your phone running so you can confirm the bootloader and modem. CM11 does not flash a modem or bootloader.
Hey folks,
I have tried this with 2 GS 3's, and I have even tried multiple different versions of twrp just to make sure, and I still have the same issue. I flashed Clockwork Mod and twrp using Flashify and Odin, however when I actually go to make Nandroid back up, or flash anything, I get the "can't mount" messages from CWM and an empty folder from twrp. I have attached pictures to show the issue. As I said, I tried multiple methods, and multiple versions, on 2 separate devices, yet came to the same end. Does anyone know anything about this?
Really? No one? lol
ok , just throwing this out there... are you using latest twrp , what about the 'fix permissions' option , tried installing via fastboot from laptop (?). sorry dont have more. still newb-ish myself.
last screenshot says 'no OS' , you have no ROM on your phone(?).
also , are some knowledgeable folks on this thread...
http://forum.xda-developers.com/showthread.php?t=2257421
"all i can really do , is stay out of my own way and let the will of heaven be done"
mrrocketdog said:
ok , just throwing this out there... are you using latest twrp , what about the 'fix permissions' option , tried installing via fastboot from laptop (?). sorry dont have more. still newb-ish myself.
last screenshot says 'no OS' , you have no ROM on your phone(?).
also , are some knowledgeable folks on this thread...
http://forum.xda-developers.com/showthread.php?t=2257421
"all i can really do , is stay out of my own way and let the will of heaven be done"
Click to expand...
Click to collapse
If by fast boot you mean use Odin in my laptop, then Yessir I did. Both with clockwork mod and twrp. Everything downloads and installs fine. It's the actual functionality that is dysfunctional. It says I have no os, but I do have my stock Rom on there and it boots just fine. Thank you so much for actually responding, it means a lot. I'll look into the that and hopefully find some info
Sent from my LG-D852 using XDA Free mobile app
fastboot is run from your computer while phone is plugged into it. very very useful. here's a guide if interested or do a google search.
http://forum.xda-developers.com/showthread.php?t=2225405
"all i can really do , is stay out of my own way and let the will of heaven be done"
Do you have the i747m or i747? If you have the i747m, try re-flashing a completely stock ROM from sammobile.com.
audit13 said:
Do you have the i747m or i747? If you have the i747m, try re-flashing a completely stock ROM from sammobile.com.
Click to expand...
Click to collapse
I have the i747M. A completely stock rom? As in a Samsung stock rom? Would I go about doing it the same way as any other rom? Because my recoveries aren't working so I'm not able to do a Nandroid back up. As such I'd rather not do anything until I am able to do a Nandroid back up.
You're installing the latest recoveries for the d2lte, right?
audit13 said:
Do you have the i747m or i747? If you have the i747m, try re-flashing a completely stock ROM from sammobile.com.
Click to expand...
Click to collapse
audit13 said:
You're installing the latest recoveries for the d2lte, right?
Click to expand...
Click to collapse
d2lte? I don't understand, could you elaborate further?
The only recovery that works for the i747m is made for the d2lte. I think you maybe be flashing the wrong recovery.
audit13 said:
The only recovery that works for the i747m is made for the d2lte. I think you maybe be flashing the wrong recovery.
Click to expand...
Click to collapse
Ooooooooook then. Would you be kind enough to direct me to the right place?
What have you been flashing?
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
audit13 said:
What have you been flashing?
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Click to expand...
Click to collapse
I downloaded CWM and TWRP from a couple pages online. I'll try finding their links.
Is this link the correct version of CWM?
That is the correct link.
audit13 said:
That is the correct link.
Click to expand...
Click to collapse
You, sir, are a God send. Thank you. But I must ask, even within the i747m there are different versions? Why?
Sent from my LG-D852 using XDA Free mobile app
All s3 phones sold in Canada are identical hardware-wise. It's only the carrier customizations that make them appear to be different.
You can flash a stock Rogers 4.4.2 over a stock Telus 4.4.2 with no problems. In fact, I have done it myself.
Prior to unified ROM and recovery builds for the s3, the AT&T s3 was referred to as the d2att while the Bell/Rogers/Telus s3 was referred to as the d2can. With unified builds, they are collectively referred to as d2lte. The only two things that are not interchangeable between the i747 and i747m are the modems and bootloaders.
Installing GS3 Rogers...but not really
Hello,
I tried to use the CM installer app/windows install which appeared to work but upon a first reboot a couple of questions pop up asking about if I want root and that the ROM might request a stock recovery. I answered these questions 7 ways to Sunday but it will not boot to CM. I can get in to the recovery screen but that is about it.
Something wrong?
thanks,
If you are stuck at the CM boot logo, try wiping cache, dalvik, and data in recovery?
audit13 said:
If you are stuck at the CM boot logo, try wiping cache, dalvik, and data in recovery?
Click to expand...
Click to collapse
Hi
I'm not stuck at the CM logo, in fact it just boots in to the stock Rogers environment. I can get in to the recovery menu but all I have is
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
I wiped the cache...no improvement.
I recommend you not use the CM install app as it can be hit and miss for some phones.
Before flashing anything, I recommend you verify the bootloader on your phone and post the version here.
For the past 3 days i've gone through hell and back with this phone.
To start off I rooted the phone, and that was working fine, my buddy was downloading something (idek what it is and I have no way to get ahold of him to ask him) and after that it busted. Then I somehow deleted my whole operating system.
Since then I have downloaded a 4.3 stock rom (os?) and I have successfully unbricked my phone. Now I have no service, and i'm 99% sure it's because all of my IMEI things are unknown. Now I figure that is an easy fix by downloading a modem?
Before I look into fixing my IMEI problems I would like to get back to 4.4.2 (Kit-Kat I think it was?)
I've downloaded countless ROMs, IMG files (converted to tar.md5), and many versions of Odin.
I've messed with Samsung Kies but I can just tell that this is a garbage program, and I have no clue what i'm doing.
What i'm asking here is help to getting me back to stock 4.4.2 (WITHOUT A ROOT) and possibly fix my IMEI problem and the problem I can't get 3g/mobile data working (snapchat/instagram did not work) (APN maybe?) (I haven't looked into these problems yet, could be super hard, could be fairly easy)
Samsung Galaxy S3 AT&T SGH-i747 is the phone i'm currently working with.
The last thing I tried to do is flash with a boot.tar.md5 and system.tar.md5, it did NOT work, as I was not sure where to put those files at in odin. Boot = Bootloader and System = AP/PDA?
Sorry if I come off as a complete noob, this is literally last resort for me (I've been doing this for 3 days....) as I can probably suspect you guys are very tired of all of these help requests.
Thank you to everybody who reads this, and am looking forward to having a normal phone again.
Edit: First post here
Does the phone boot into download mode? Sounds like it does since you can use Odin.
To get the phone running, copy the latest cm11 or cm 12 to an sd card, copy cm11 Gapps or cm12 Gapps (download the version that matches the ROM you intend to flash), flash a custom recovery (I prefer CWM for the d2lte or Philz Touch for the d2lte), boot into recovery, do a full wipe, flash cm, flash Gapps, boot the phone.
audit13 said:
Does the phone boot into download mode? Sounds like it does since you can use Odin.
To get the phone running, copy the latest cm11 or cm 12 to an sd card, copy cm11 Gapps or cm12 Gapps (download the version that matches the ROM you intend to flash), flash a custom recovery (I prefer CWM for the d2lte or Philz Touch for the d2lte), boot into recovery, do a full wipe, flash cm, flash Gapps, boot the phone.
Click to expand...
Click to collapse
sick thanks for the response homie.
i'm not exactly sure which CM to download, I went to the d2ltes since that's the closest thing to my device I found in that list.
I also went to cwm rom managers and downloaded the recovery setup, i'm guessing I convert that and flash it using odin and voila, I have cwm?
and for the cm11 gapps I went to this website and downloaded the zip file, going to just put that on my sd card with the CM (when I figure out which one to download)
am I headed in the right direction?
edit: okay I got cwm recovery on my phone... thats good
edit 2: alright downloading cm12 and alreayd have cmgapps in a zip ready to be put in my sd card. i'll let you know how installing it with cwm goes. thank you for your help man I really appreciate it.
edit 3: how would I go about installing it via owm? everytime I install from sd card it resets my phone, just go back into recovery and install the second zip? or is there a way I can install both at once?
Boot into cwm, wipe cache, wipe data, wipe dalvik, install cm1 from sd card, install gapps, reboot.
The i747 is also known as the d2lte so anything designed for the d2lte is good.
audit13 said:
Boot into cwm, wipe cache, wipe data, wipe dalvik, install cm1 from sd card, install gapps, reboot.
The i747 is also known as the d2lte so anything designed for the d2lte is good.
Click to expand...
Click to collapse
alright! couldn't thank you enough. like I said i'll keep you updated!
edit: i'm in the cwm recovery or w.e and there is a different keyboard as i'm doing this, does this transfer over to be my real keyboard after the cwm recovery stuff? if not, how do I get this keyboard?
edit 2: wow this is totally different, sick.. let me play around with it, i'm sure i'll have some questions.
alright, phone number is still not available, imei and imei sv is still not available, same with everything in the SIM status.
going to try and find a modem for my model.
no luck so far, if someone could help search for a MODEM for SGH-i747 AT&T s3 that would be great..
sorry for being so needy.. thanks for hanging in here and helping me out.
edit: I found this link but it's for 4.4.2... it says do not use it if you're on 4.3.... is it okay if i'm at like 5.1.1 cwm?
well, I cannot post the link and I do not want to find a way around to post the link incase a mod shuts this thread down. if you want the link you may PM me..
edit 2: okay so google play services does NOT work, and I need that in order to open skype.. so that's on another thing on the list of **** to fix. However I just downloaded an apk and I need to put it in system/apps but i'm not sure where to find that... i'll probably end up downloading it on the phone and dropping it in with a file manager.
edit 3: none of this worked, I still need google play services to get installed..
Does the phone boot to the desktop? Which rom did his try? Try the latest cm10.2 for the d2lte.
Are you able to install a terminal app or Samsung phone info app?
Try and find the apk version of the app and just install it from the file browser.
audit13 said:
Does the phone boot to the desktop? Which rom did his try? Try the latest cm10.2 for the d2lte.
Are you able to install a terminal app or Samsung phone info app?
Try and find the apk version of the app and just install it from the file browser.
Click to expand...
Click to collapse
It tells me "It cannot be installed". I will find 10.2 for d2lte... assuming I find the corresponding GApps.
I also could have ran all of the other google apps... "google +, playstore, youtube, etc"
edit: I cannot find cm 10.2, lowest I can find for d2lte is 11. should I try that instead?
These are all the zips i'm installing with cwm when I wipe/reset my phone totally:
Calkulin's Google Play Service modded (so google play services works)
cm-11
gapps-kk-20140606
and I am currently messing with modem files to get my service back, i'm about to try my second one.. wish me luck!
edit: I can't get my baseband model to show, nor my imei numbers to come, they all stay unknown.. if someone would like to do some sort of 1 on 1 that would be awesome.
You could also try the cm for the d2att.
audit13 said:
You could also try the cm for the d2att.
Click to expand...
Click to collapse
trying it now! should I use a specific gapps? maybe for 5.1.1? cause 12.1 uses 5.1.1 if i'm not mistaken.
There are separate gapps for cm10.2, cm11, and cm12.
It sounds to me like there is a problem with the modem and bootloader combination on the phone.
What specific bootloader version is on the phone?
audit13 said:
There are separate gapps for cm10.2, cm11, and cm12.
It sounds to me like there is a problem with the modem and bootloader combination on the phone.
What specific bootloader is on the phone?
Click to expand...
Click to collapse
so after I download cm12.1 and cm12gapps, I should look further into the bootloader/modem problem?
i've tried a few modems for i747 and i've had no luck so far unfortunately, if someone else reading this has had experience or knows someone who has experiences null baseband / imei numbers let me know!
edit: oops, my mistake.. just saw the last part of your post now. i'm not sure how to find out my bootloader.
Use the terminal app and type getprop ro.bootloader.
audit13 said:
use the terminal app and type getprop ro.bootloader.
Click to expand...
Click to collapse
i747ucufnj1
i'm certain the only problem I have now is the IMEI (no sim service) besides that everything is good now!
farkas3 said:
i747ucufnj1
i'm certain the only problem I have now is the IMEI (no sim service) besides that everything is good now!
Click to expand...
Click to collapse
Alright I've now figured out that I do NOT have ANY efs files for samsung galaxy I747UCUFNJ1.
I have the imei number from the back of my phone.
I tried the EFS pro method and when I click "backup" an error pops up and says "Block device does NOT exist"
I'm so confused and I need help lol
wow, I fixed it! I installed the correct modem corresponding to my baseband / bootloader something like that.. wow. most stressful 4 days of my life
ty so much
Glad you got it working. This is why I kept asking about the modem and suggesting that the modem doesn't match the bootloader.