Related
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.
I am unable to install the following ROM, continue to get this error (E:error (Status 7) Installation Aborted):
http://forum.xda-developers.com/showthread.php?t=2634672
The ROM I choose is the'd2spr' and I have used several other (d2spr) ROMs that work, for my 'Sprint Samsung Galaxy S III' (SPH-L710).
Anyone able to advise/assist?
Things already attempted..
1) Updated to the latest CWM recovery
2) Updated to the latest PHILZ recovery
3) Toggled 'signature Verification' to "on"
4) Tried several other ROM's from the same developer that were d2spr
..all resulted in the same error, above.
matg55 said:
I am unable to install the following ROM, continue to get this error (E:error (Status 7) Installation Aborted):
http://forum.xda-developers.com/showthread.php?t=2634672
The ROM I choose is the'd2spr' and I have used several other (d2spr) ROMs that work, for my 'Sprint Samsung Galaxy S III' (SPH-L710).
Anyone able to advise/assist?
Things already attempted..
1) Updated to the latest CWM recovery
2) Updated to the latest PHILZ recovery
3) Toggled 'signature Verification' to "on"
4) Tried several other ROM's from the same developer that were d2spr
..all resulted in the same error, above.
Click to expand...
Click to collapse
Which baseband you currently running?
sent from my GS3
matg55 said:
i am unable to install the following rom, continue to get this error (e:error (status 7) installation aborted):
http://forum.xda-developers.com/showthread.php?t=2634672
the rom i choose is the'd2spr' and i have used several other (d2spr) roms that work, for my 'sprint samsung galaxy s iii' (sph-l710).
Anyone able to advise/assist?
Things already attempted..
1) updated to the latest cwm recovery
2) updated to the latest philz recovery
3) toggled 'signature verification' to "on"
4) tried several other rom's from the same developer that were d2spr
..all resulted in the same error, above.
Click to expand...
Click to collapse
joeyhdownsouth said:
which baseband you currently running?
Sent from my gs3
Click to expand...
Click to collapse
l710vpucmk3
matg55 said:
l710vpucmk3
Click to expand...
Click to collapse
I am also having this issue
Which recovery are you guys using? If it isn't Philz Touch, switch NOW! Then, under Wipe Data/Factory Reset, choose Clean to Install New ROM, and then flash whatever version of Carbon you want. If it helps to get you started, here is my download of the very first KitKat nightly that Carbon released, the assert lines have been removed in order to make it compatible for Virgin Mobile/Boost, and it is guaranteed to flash if all else is equal (as in you are using Philz Touch and did a proper wipe; I flashed this version just fine, otherwise I would not post it).
http://d-h.st/KTA
And the link to the Philz thread:
http://forum.xda-developers.com/showthread.php?t=2446393
Make sure to give @Phil3759 a "Thanks" while you are there!
Mr. Struck said:
Which recovery are you guys using? If it isn't Philz Touch, switch NOW! Then, under Wipe Data/Factory Reset, choose Clean to Install New ROM, and then flash whatever version of Carbon you want. If it helps to get you started, here is my download of the very first KitKat nightly that Carbon released, the assert lines have been removed in order to make it compatible for Virgin Mobile/Boost, and it is guaranteed to flash if all else is equal (as in you are using Philz Touch and did a proper wipe; I flashed this version just fine, otherwise I would not post it).
http://d-h.st/KTA
And the link to the Philz thread:
http://forum.xda-developers.com/showthread.php?t=2446393
Make sure to give @Phil3759 a "Thanks" while you are there!
Click to expand...
Click to collapse
Thank You.. I do have the latest Philz Touch installed and did the full "new rom" wipe while trying the other Carbon ROM's, with the same error.
However, the ROM link you shared does work.. just hoping to be able to maintain the latest nightlies; wonder if I just have to remove the assert lines. Anyway, thanks again!
matg55 said:
Thank You.. I do have the latest Philz Touch installed and did the full "new rom" wipe while trying the other Carbon ROM's, with the same error.
However, the ROM link you shared does work.. just hoping to be able to maintain the latest nightlies; wonder if I just have to remove the assert lines. Anyway, thanks again!
Click to expand...
Click to collapse
Which carrier are you on?
Mr. Struck said:
Which carrier are you on?
Click to expand...
Click to collapse
Sprint... and have tried the latest 'd2spr'
matg55 said:
Sprint... and have tried the latest 'd2spr'
Click to expand...
Click to collapse
That is strange; as a Virgin Mobile user, I have to modify or delete the assert lines for any Sprint ROM that is AOSP based, but for a Sprint user the ROM should have downloaded and flashed just fine. That's a shame too, because in my opinion, Carbon is the best ROM available.
So I initially used cyanogenmod installer from stock to install cyanogenmod from stock and all was fine and dandy until the phone booted into cyanogen mod and the android is upgrading... popup showed just to have the phone reboot endlessly as soon as it finishes. I tried aokp. Same. other 4.4 aosp roms. Same. I odin'd back to stock (that worked fine) and tried flashing from stock and still no cigar. My radios are up to date enough i think since the stock i was/am running is 4.1.2 and I even tried twrp since its selinux compatible (what does selinux compatible even mean anyway?) and still no cigar! Any Ideas, I really need at least some sort of aosp to get my nav bar working nice since my nav touch buttons went out. I did this same method with another s2 exactly the same, hercules model and all and cyanogenmod installer worked. So this seems phone specific. Any ideas?
blu422 said:
So I initially used cyanogenmod installer from stock to install cyanogenmod from stock and all was fine and dandy until the phone booted into cyanogen mod and the android is upgrading... popup showed just to have the phone reboot endlessly as soon as it finishes. I tried aokp. Same. other 4.4 aosp roms. Same. I odin'd back to stock (that worked fine) and tried flashing from stock and still no cigar. My radios are up to date enough i think since the stock i was/am running is 4.1.2 and I even tried twrp since its selinux compatible (what does selinux compatible even mean anyway?) and still no cigar! Any Ideas, I really need at least some sort of aosp to get my nav bar working nice since my nav touch buttons went out. I did this same method with another s2 exactly the same, hercules model and all and cyanogenmod installer worked. So this seems phone specific. Any ideas?
Click to expand...
Click to collapse
Did you format /system? You can't just "Full Wipe" to upgrade from one ROM to the next, you need to format /system (I do it with Clockworkmod Recovery)
ShaDisNX255 said:
Did you format /system? You can't just "Full Wipe" to upgrade from one ROM to the next, you need to format /system (I do it with Clockworkmod Recovery)
Click to expand...
Click to collapse
yes I did I have some experience with flashing ROMs and that stuff
What version of twrp?
kj2112 said:
What version of twrp?
Click to expand...
Click to collapse
2.7.0.0 I also tried the latest clockworkmod
Well, try twrp 2.6.1.0. And take a nandroid after you install it. Then try again. Make sure to wipe system, data, cache and dalvik cache. Then ROM, then gapps. Maybe wipe caches again before rebooting.
I'm trying to update my E975 to v20A (kitkat) using software update app on the device. 1st try, I get notification that my phone is rooted and installation cannot continue, so I use Framaroot to unroot my phone, then I tried again to update my phone and I get, "installation error" msge and not knowing what cause the error.
what should I do?
frans3q said:
I'm trying to update my E975 to v20A (kitkat) using software update app on the device. 1st try, I get notification that my phone is rooted and installation cannot continue, so I use Framaroot to unroot my phone, then I tried again to update my phone and I get, "installation error" msge and not knowing what cause the error.
what should I do?
Click to expand...
Click to collapse
You should either flash back to original stock from your region or root your phone again, install CWM and install artmod - I suggest the latter.
http://forum.xda-developers.com/opt...om-e97520a-eu-4-4-2-artmodv3-0-te-10-t2811342
nchc said:
You should either flash back to original stock from your region or root your phone again, install CWM and install artmod - I suggest the latter.
http://forum.xda-developers.com/opt...om-e97520a-eu-4-4-2-artmodv3-0-te-10-t2811342
Click to expand...
Click to collapse
means you suggest I should use the artmod?
well, I used CM11 before, but I think 4.1.2 stockrom is better, and I use QSlide a lot. Then I flash using KDZ back to my original stock ROM. (that my current ROM, 4.1.2 stock rom)
then I read about official Kitkat release and I think the v20a official update will included all previous LG feature so I decided to try it.
But now I'm experiencing a lot of problem, the software update didnt works, so I download the .zip from this thread : http://forum.xda-developers.com/showthread.php?t=2784649 but it didnt work, and I'm having a bootloop.
I dont know, should I re-lock my bootloader before trying to update / flashing the official ROM?
I had try flashing CM11, and no problem.
Try again and if you didn't before do a very clean install i.e. factory reset,clear cache and dalvik cache, format system. Stock KitKat has a different partition setup compared to stock jb,I'd say that's what's causing errors.
nchc said:
Try again and if you didn't before do a very clean install i.e. factory reset,clear cache and dalvik cache, format system. Stock KitKat has a different partition setup compared to stock jb,I'd say that's what's causing errors.
Click to expand...
Click to collapse
thx. looks like I need a very clean install... software update method still wont work, but installing .zip from CWM work was working.
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.