Related
Hello.
I have a GS3 SGH-I747M on rogers. The last one I was trying to get Cyanogenmod 10 on kept getting (Status 7) error. Nothing screwed up at all, until I attempted to unlock the boot loader with some stupid app that said it was safe wit my phone. I finally got a new one, found a solution to my issue (I have to use a different version of clockworkmod) and was wondering if it is safe to do. I mean no chance of risk if I follow instructions (no bricks, etc).
TL;DR: I have an SGH-i747M on rogers and want to out cyanogenmod 10 on with no chance of brick. Could you give me instructions on how to, or tell me if it is safe/unsafe?
Thanks a lot,
Edwin
Flash a newer recovery prior to flashing CM10.
EdwinForTheWin said:
Hello.
I have a GS3 SGH-I747M on rogers. The last one I was trying to get Cyanogenmod 10 on kept getting (Status 7) error. Nothing screwed up at all, until I attempted to unlock the boot loader with some stupid app that said it was safe wit my phone. I finally got a new one, found a solution to my issue (I have to use a different version of clockworkmod) and was wondering if it is safe to do. I mean no chance of risk if I follow instructions (no bricks, etc).
TL;DR: I have an SGH-i747M on rogers and want to out cyanogenmod 10 on with no chance of brick. Could you give me instructions on how to, or tell me if it is safe/unsafe?
Thanks a lot,
Edwin
Click to expand...
Click to collapse
Sent from my SGH-I747M using xda premium
such as
SaneinOne said:
Flash a newer recovery prior to flashing CM10.
Sent from my SGH-I747M using xda premium
Click to expand...
Click to collapse
Such as...
EdwinForTheWin said:
Hello.
I have a GS3 SGH-I747M on rogers. The last one I was trying to get Cyanogenmod 10 on kept getting (Status 7) error. Nothing screwed up at all, until I attempted to unlock the boot loader with some stupid app that said it was safe wit my phone. I finally got a new one, found a solution to my issue (I have to use a different version of clockworkmod) and was wondering if it is safe to do. I mean no chance of risk if I follow instructions (no bricks, etc).
TL;DR: I have an SGH-i747M on rogers and want to out cyanogenmod 10 on with no chance of brick. Could you give me instructions on how to, or tell me if it is safe/unsafe?
Thanks a lot,
Edwin
Click to expand...
Click to collapse
I suggest that you take a look at these first before trying to root your phone:
http://forum.xda-developers.com/showthread.php?t=1739426
http://forum.xda-developers.com/showthread.php?t=1725839
Second, I have Cyanogenmod 10 and I can say that it's playing safe so far - the only disadvantages that you would have are: Samsung's gestures are not functional and CM10 is kinda unstable for games and apps. I also experienced the Status 7 error and from experience, it's caused by using an 'old' version of CWM Recovery. Download the latest one from here (Samsung Galaxy S3 AT&T): http://www.clockworkmod.com/rommanager and download the Cyanogenmod 10 M2 from the CM site.
Assuming that you know how to setup the custom recovery for your phone, delete the current recovery.img on your phone and replace it with the new one that you downloaded. Then just do what you did to setup your custom recovery. I also suggest that you follow the ROM flashing guide on this page: http://wiki.cyanogenmod.com/wiki/Samsung_Galaxy_S_III:_Full_Update_Guide as it is what I followed to ensure that a brick wouldn't happen on my phone. Just a reminder, also wipe the Dalvik cache just to be sure.
TL;DR Flashing and rooting is safe as long as you're patient and you thoroughly follow guides on rooting/flashing your phone.
okay
GlassRaven said:
I suggest that you take a look at these first before trying to root your phone:
http://forum.xda-developers.com/showthread.php?t=1739426
http://forum.xda-developers.com/showthread.php?t=1725839
Second, I have Cyanogenmod 10 and I can say that it's playing safe so far - the only disadvantages that you would have are: Samsung's gestures are not functional and CM10 is kinda unstable for games and apps. I also experienced the Status 7 error and from experience, it's caused by using an 'old' version of CWM Recovery. Download the latest one from here (Samsung Galaxy S3 AT&T): http://www.clockworkmod.com/rommanager and download the Cyanogenmod 10 M2 from the CM site.
Assuming that you know how to setup the custom recovery for your phone, delete the current recovery.img on your phone and replace it with the new one that you downloaded. Then just do what you did to setup your custom recovery. I also suggest that you follow the ROM flashing guide on this page: http://wiki.cyanogenmod.com/wiki/Samsung_Galaxy_S_III:_Full_Update_Guide as it is what I followed to ensure that a brick wouldn't happen on my phone. Just a reminder, also wipe the Dalvik cache just to be sure.
TL;DR Flashing and rooting is safe as long as you're patient and you thoroughly follow guides on rooting/flashing your phone.
Click to expand...
Click to collapse
Thanks for the response, do you recommend that I flash another ROM before flashing cyanogenmod 10?
EdwinForTheWin said:
Thanks for the response, do you recommend that I flash another ROM before flashing cyanogenmod 10?
Click to expand...
Click to collapse
I don't really recommend that as that could cause unwanted trouble. From my experience, I just followed the rooting guide that I posted, flash a custom recovery, and flashed the Cyanogenmod 10. Another tip, if you don't want to lose your contacts, make a backup of it before flashing a ROM. Preferrably you write them in a paper so it would be easier. If you have important messages, use an SMS/MMS backup tool to save them. As for applications, make a list of applications that you consider are essential for you so you could just redownload them. Starting out in a custom ROM is really hard at first but you'll get used to it.
Its safety is directly proportional to your ability to follow directions.
Your first mistake was you used the app to unlock the VERIZON S3 bootloader.
All other versions of the GS 3 have unlocked bootloaders.
You should definitely do some more research before you attempt root and custom recovery.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Can you just use ROM Manager after rooting and flashing the stock ROM to download CWM, then CM10? And is the CM10 you're using on your Rogers phone compatible? I don't see a Rogers version on the CM site. Did you use the AT&T one?
Yes for the ROM manager, but the free version doesn't install latest touch recovery. The at&t version is compatible with all Canadian i747m. You can get the latest version here: http://get.cm/?device=d2att
tonymtl said:
Yes for the ROM manager, but the free version doesn't install latest touch recovery. The at&t version is compatible with all Canadian i747m. You can get the latest version here: http://get.cm/?device=d2att
Click to expand...
Click to collapse
What does touch recovery do? And do I have to use that link to flash it, or can I use ROM Manager? And if I were to use that link, I would DL the zip, boot my phone into download mode, plug in, open Odin, make sure auto reboot and F reset time are checked, load the .tar into the PDA, and click start? What happens to the previous ROM that was there?
And when I first root my phone, and load the stock rom, do all of my apps remain? I haven't rooted yet, for my Rogers phone.
A touch recovery lets you touch the screen as apposed to using the volume rocker.
You will keep all your data.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Thanks for the help! Another question, if I would like to unroot my phone, and decrease the flash counter, is there a thread I should see for the I747MVLLH1? I know about triangle away, but Rogers/my model isn't supported for that.
Triangle away does support Rogers gs3
Thanks! So should I flash CM10 through ROM Manager, or through the link that was posted? I'm not exactly clear on how to flash the ROM through the link though. Does flashing a new ROM erase the previous ROM? And 'wiping cache' doesn't wipe your data/apps right, only 'wipe Data and Cache'? And I don't really need to bother with kernels too right?
If you going from stock to cm10 wipe everything: cash, data, dalvik cash. Don't flash kernels unless you want to overclock and undervolt, cm10 comes with kernel and I get pretty good battery life with it. You can flash from ROM manager, and yes it will erase your previous ROM, so do a backup before flashing.
tonymtl said:
If you going from stock to cm10 wipe everything: cash, data, dalvik cash. Don't flash kernels unless you want to overclock and undervolt, cm10 comes with kernel and I get pretty good battery life with it. You can flash from ROM manager, and yes it will erase your previous ROM, so do a backup before flashing.
Click to expand...
Click to collapse
And when I flash it through ROM Manager, it would give me the option to wipe everything right?
The backup that I would do through ROM Manager, thats just incase anything goes wrong right? It's not to get back my apps once I flash from stock to CM10? Other than manually installing them after flash, is there any way to quickly get back my apps/files?
And does the CM10 flash from ROM Manager include the GAPPS file?
Yes it will ask you if you want to wipe, if you download cm10 ROM from ROM manager it will ask you if you want the latest gapps. You can get ROM toolbox or titanium backup to backup your apps and restore them after flashing rom. Backup is just in case but you can always flash stock ROM later if anything goes wrong.
ily112 said:
And when I flash it through ROM Manager, it would give me the option to wipe everything right?
The backup that I would do through ROM Manager, thats just incase anything goes wrong right? It's not to get back my apps once I flash from stock to CM10? Other than manually installing them after flash, is there any way to quickly get back my apps/files?
And does the CM10 flash from ROM Manager include the GAPPS file?
Click to expand...
Click to collapse
You should probably flash through your cwm recovery instead of ROM Manager, but yea you can do a backup in recovery or ROM Manager, and I recommend Titanium backup it's easy to use and free.
s0ulja said:
You should probably flash through your cwm recovery instead of ROM Manager, but yea you can do a backup in recovery or ROM Manager, and I recommend Titanium backup it's easy to use and free.
Click to expand...
Click to collapse
How exactly would I flash through cwm recovery?
Hey guys, I was having some trouble with a rom and switched my recovery to CWM6.0.1.2 and it's no longer booting recovery and CM is not working either just getting boot errors with gapps and setup crashes.
Basically I can't do anything with my phone unless I can wipe it and flash stock or correctly flash CM. Does anyone have any suggestions on a way to wipe my rom through odin? Currently downloading stock just incase that may help me down the road.
Where is that stock rom? Looking for it
Sent from my SGH-T999 using xda premium
Download CWM from my signature and flash it through Odin.
Gapps crashing means you flashed a mismatched version for your rom.
Aerowinder said:
Download CWM from my signature and flash it through Odin.
Gapps crashing means you flashed a mismatched version for your rom.
Click to expand...
Click to collapse
That might have happened, I got CWM working and flashed my old rom with a lot of issues, specifically stock apps crashing. Going to flash full stock via odin and start from scratch. Really stoked to try a 4.2 CM AOKP rom :good:
Are there files I can manually delete/modify to bring my device fully back to stock?
Familiar Joe said:
That might have happened, I got CWM working and flashed my old rom with a lot of issues, specifically stock apps crashing. Going to flash full stock via odin and start from scratch. Really stoked to try a 4.2 CM AOKP rom :good:
Are there files I can manually delete/modify to bring my device fully back to stock?
Click to expand...
Click to collapse
Delete or wipe via recovery is highly recommened and flash via odin. You cant do to all system files and delete them individually; thats too much of work.
Everything is golden thanks guys
tl;dr: What happens if I upgrade to CWM 6 after having used Darkside Superwipe on CWM 5?
And now the long explanation of what happened:
I have a Telus T989D, and I had installed the stock Telus JB ROM from this thread: http://forum.xda-developers.com/showthread.php?t=2343748
I previously had CWM, but as per the instructions in the thread I installed TWRP, ran the Infamous Superwipe zip file, and then proceeded to flash the ROM.
Then today I decided to install CM 10.1. The first thing I did was flash CWM 6.x (I forget the exact version, but it was the latest one) from ODIN. Then I downloaded the latest stable build (CM 10.1.2). I then ran the Infamous Superwipe zip file again, and flashed CM 10.1. The result was that the phone would get stuck on the Cyanogenmod circle logo. I did some Googling and found out some people who had bootloops after installing Cyanogenmod, and it was suggested that this was due to a bad wipe, and that using Darkside Superwipe would fix the problem. So I proceeded to give Darkside Superwipe a try... Of course at the time I hadn't realized that 1) What I had was not actually a boot loop (it wasn't rebooting, it was just stuck at the logo), and 2) that Darkside Superwipe should not be used with CWM 6. After flashing the Darkside file, my CWM 6 would load up but would fail to flash ANY zip file that I selected (it would just get stuck on the first line, "Installing xxx.zip"). It would also fail to wipe the /cache partition (would freeze at "wiping /cache partition").
After soft-bricking my phone by trying to flash a different recovery from Heimdall, I ended up following a guide on this forum to flash the stock Gingerbread ROM from Odin. I then flashed CWM 5.0.2.7, did the Darkside Superwipe, installed CM 10.1, and now thankfully the phone works.
My question is... Does anybody know what happened here? And any ideas what will happen if I try to upgrade my CyanogenMod later on? Will I have any issues running CWM 5.x with CM 10.1 or 10.2? I'm a bit afraid of updating to CWM 6 since I have no idea what the result will be.
I later learned that Infamous Wipe is only to be used with TW-based 4.1.2 ROMs, since it adds a preload partition. Did I end up somehow messing up my partitions by using the Infamous & Darkside Superwipe files?
Sorry for the long post... I just figured I should give as much information as possible! I'd really appreciate it if anybody has an explanation for what happened (messed up partitions?) and how to fix it!
OK so what u need to do first is stop flashing all these recoveries, DL twrp2.6.1.0 and flash that with Odin, stay with this recovery, cwm is OK but not updated frequently enough to keep up with newer flashing scripts, now don't use superwipe/super cache wipes with twrp, they will cause loops, do a full wipe with twrp, mount to USB move all files off SD cards and format them, replace any/all files from SD card that u want, now flash ROM, flash gapps, reboot and let sit ten min, this should fix ur issues, as far as what happens, u used superwipe scripts on 6.x+cwm, those scripts were meant for cwm5x, it'll loop every time...
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
soupysoup said:
OK so what u need to do first is stop flashing all these recoveries, DL twrp2.6.1.0 and flash that with Odin, stay with this recovery, cwm is OK but not updated frequently enough to keep up with newer flashing scripts, now don't use superwipe/super cache wipes with twrp, they will cause loops, do a full wipe with twrp, mount to USB move all files off SD cards and format them, replace any/all files from SD card that u want, now flash ROM, flash gapps, reboot and let sit ten min, this should fix ur issues, as far as what happens, u used superwipe scripts on 6.x+cwm, those scripts were meant for cwm5x, it'll loop every time...
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks soupysoup! I will do that the next time I update the phone. And just another quick question: do you know if TWRP is safe to use with CyanogenMod (since it seems that they recommend CWM)?
Faruk88 said:
Thanks soupysoup! I will do that the next time I update the phone. And just another quick question: do you know if TWRP is safe to use with CyanogenMod (since it seems that they recommend CWM)?
Click to expand...
Click to collapse
Yes, actually I reccomend twrp to everyone for every ROM, the only way a ROM could be recovery specific would be if the ROM called for specific flashing scripts a certain recovery used/ran but twrp is updated a lot and always uses the newest flashing scripts in there builds, plus the recovery itself is very user friendly, the newest version is 2.6.1.0, go check that out n fully 4.3 compatible
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
soupysoup said:
Yes, actually I reccomend twrp to everyone for every ROM, the only way a ROM could be recovery specific would be if the ROM called for specific flashing scripts a certain recovery used/ran but twrp is updated a lot and always uses the newest flashing scripts in there builds, plus the recovery itself is very user friendly, the newest version is 2.6.1.0, go check that out n fully 4.3 compatible
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Perfect, thanks! Just one last question, then: In your previous post you said to flash TWRP through Odin. Does it matter if I flash through Odin or if I just download Goo manager and switch to TWRP from there? Which one of the two options is safer/better?
Faruk88 said:
Perfect, thanks! Just one last question, then: In your previous post you said to flash TWRP through Odin. Does it matter if I flash through Odin or if I just download Goo manager and switch to TWRP from there? Which one of the two options is safer/better?
Click to expand...
Click to collapse
U can use goo manager if u want, but I will say this, sometimes too can cause soft bricks, in which case u would need Odin to recover , so in my professional opinion I would suggest using Odin from scratch
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
So I'm currently running Cyanogenmod version 10.2.0 .. Android 4.3.1.
I've updated to the newest version of TWRP.
I factory wipe, then try to install a different ROM.. for example I've tried PA & AOKP.
Every time I try this it fails within 1 second and I have to restore a backup and go back to Cyanogenmod.
EDIT: I have a T-Mobile Galaxy S3
I have attached an image of when I get an error when I try to flash.
UPDATE:
Alright so I was able to get past that error by going into advanced wipe and selecting "System". Now when I flash I get a new error. I am attaching a new picture.
You need to give more info on the error
Sent from my SGH-M919 using Tapatalk
serio22 said:
You need to give more info on the error
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
I'm at work now. I'll post and update with the error later.
Do you have a t-mobile s3? If you are from a different carrier such as wind mobile I could know the problem. I also had a problem flashing 4.3 Roms with my t999v wind s3.
Sent from my SGH-T999 using xda app-developers app
spartan268 said:
Do you have a t-mobile s3? If you are from a different carrier such as wind mobile I could know the problem. I also had a problem flashing 4.3 Roms with my t999v wind s3.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Mine is T-Mobile. I'm still at work til 2AM EST. I'll probably post my error tomorrow.
Alright guys, I attached a screenshot (picture lol) of my phone and the error I am getting when I try to flash different ROMs. Any help?
Alright guys.. I was able to get past that other error but now I have a new one when trying to install a new ROM.
Here is a screenshot of the error.
Shallwhat said:
Alright guys.. I was able to get past that other error but now I have a new one when trying to install a new ROM.
Here is a screenshot of the error.
Click to expand...
Click to collapse
Update your recovery. You're using TWRP 2.5.5.0 when the latest one is 2.6.3.1. If you can't boot into Android, Odin the TWRP recovery. Also, make sure you completely wipe your internal storage before flashing a custom ROM. If that custom ROM isn't working for you, try another one to see if that flashes since that would indicate that the custom ROM you're trying to flash could potentially be a bad download.
You also need to post more information about your phone.
Which custom ROM are you using?
Which kernel are you using or trying to use?
etc etc.
Noobiologist said:
Update your recovery. You're using TWRP 2.5.5.0 when the latest one is 2.6.3.1. If you can't boot into Android, Odin the TWRP recovery. Also, make sure you completely wipe your internal storage before flashing a custom ROM. If that custom ROM isn't working for you, try another one to see if that flashes since that would indicate that the custom ROM you're trying to flash could potentially be a bad download.
You also need to post more information about your phone.
Which custom ROM are you using?
Which kernel are you using or trying to use?
etc etc.
Click to expand...
Click to collapse
I've tried flashing multiple ROMS.. Slimbeam.. AOKP.. ParanoidAndroid.. I've downloaded from GOOManager and I've also downloaded from external links and put on my external SD card. Nothing works. Like I said in the OP I am running Cyanogenmod 10.2.. Android 4.3.1. I'm using the Ktweaker kernel.
I updated my TWRP from Goomanager and it only updated to 2.5.5.0. How do I get it to update to 2.6.3.1?
So I just went to update TWRP from goomanager again and when it went to download it failed because "invaid MD5 sum".
Edit: So I tried updating again and it said it was successful. I rebooted into recovery and it still says 2.5.0.0
I'm lost.
Same problem happened to me last night, I tried to install the modem again but the same error keep coming up.
To everyone with issues updating recovery. Goo has a openrecovery script issue. Your best bet is to flash latest Recovery using Odin. You may choose to use Mobile Odin if you feel like it.
Can't restore anything except Kitkat
I keep getting the same error, except I can't flash or restore any rom that isn't kitkat (all the kitkat roms are buggy so i want 4.3 back). I reflashed twrp 2.6.3.1 with odin but its still not letting me flash anything.
Also if it helps I can't copy anything from the internal SD to the external SD using twrp file manager.
Older Rom's backups can't be restored due to file system changes. You will have to wipe everything and flash fresh if you want 4.3
I tried the latest version of TWRP, and I'm on StockROM by TeamInferno. I got V7 and I saw an update on it last night (V8) so I downloaded it and tried to install it fom Clockworkmod recovery and it didn't work so I tried TWRP and the same thing happened. Do I have to wipe everything to update my ROM?
Nothing will flash except Kitkat
Perseus71 said:
Older Rom's backups can't be restored due to file system changes. You will have to wipe everything and flash fresh if you want 4.3
Click to expand...
Click to collapse
Ive tried that multiple times. once the Odin flashable tw 4.3 downloads, I'm going to try that but I can't flash any fresh roms using twrp except 4.4 (Jellybam to be specific).
I tried Stockorama 4.3 tw, but it would just reboot after getting past the "samsung galaxy sIII" screen (tried insecure kernal too). I'm wondering if I'm in a weird soft brick or something
Shallwhat said:
So I just went to update TWRP from goomanager again and when it went to download it failed because "invaid MD5 sum".
Edit: So I tried updating again and it said it was successful. I rebooted into recovery and it still says 2.5.0.0
I'm lost.
Click to expand...
Click to collapse
Did odin flash of the most current recovery take care of your issue?
Hastily spouted for your befuddlement
GodLik3 said:
I tried the latest version of TWRP, and I'm on StockROM by TeamInferno. I got V7 and I saw an update on it last night (V8) so I downloaded it and tried to install it fom Clockworkmod recovery and it didn't work so I tried TWRP and the same thing happened. Do I have to wipe everything to update my ROM?
Click to expand...
Click to collapse
What was the specific error message when flashing ?
QuatroQuatro said:
Ive tried that multiple times. once the Odin flashable tw 4.3 downloads, I'm going to try that but I can't flash any fresh roms using twrp except 4.4 (Jellybam to be specific).
I tried Stockorama 4.3 tw, but it would just reboot after getting past the "samsung galaxy sIII" screen (tried insecure kernal too). I'm wondering if I'm in a weird soft brick or something
Click to expand...
Click to collapse
What is your TWRP Version ? Also what is your Bootloader version ? (No its not the baseband)
My bootloader is T999UVUEMJC
My baseband is uvuemjc
TWRP is version 2.6.3.1 (I've also tried 2.6.3.0)
I think it got updated bootloader/baseband when I odin flashed stock tw 4.3 (the only jellybean ROM that works)
I also made a backup of my 4.4, but it wouldn't let me restore even that.
You have been talking about 2 different things.
1. Flash a New Rom - Either Touchwiz or AOSP. $.3 or newer.
2. Restore a Rom - I think you are talking about a Nandroid Restore.
If you are referring to Point 1 as "Restore Rom" then you need to change terminology in order to help us understand your problem correctly. Re-Flashing a rom that you used to have is still Flashing not "Restore".
With that UVUEMJC Bootloader, you can completely forget about flashing previous Touchwiz Firmwares such as UVDMD5 or UVDLJC. If you tried them, you WILL brick your phone. If you tried Custom Touchwiz Roms based on those 2 firmwares, it may or may not work.
Now if you are trying to flash a AOSP Rom, either 4.3 or Kitkat 4.4, and you do have latest TWRP, (2.6.3.1), please specify the error message in detail.
You must do Factory Reset and Wipe Dalvik + Cache in the Recovery before flashing the AOSP Roms.
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.