Develop Bugs

[Q] Pretty huge Arc Problem, can't install Cyanogenmod or get anything else working

Hi all
My first post here. And unfortunately it's because I seem to have messed up badly.
I recently successfully unlocked the bootloader and installed Cyanogenmod 7.1.01.
Yesterday I wanted to upgrade to 7.1.0.2 and I went through the exact same steps as when I installed Cyanogen the first time. Everything seemed to go smoothly. But when booting the phone it began to boot loop.
I then tried using Flashtool to relock the bootloader so I could get it back to stock and start over. But Flashtool won't recognize the phone. I can get it into flash mode (blue led). And I've put the LT15.sin file in the loaders folder. I've tried using the two latest versions of Flashtool with no luck.
Then I tried using Fastboot to wipe the phone. I found a page on XDA I think, which had a command listed for doing so. Can't find the page now though.
It seemed to work, well, the command completed. But now when I try to install Cyanogenmod through ClockworkMod Recovery it doesn't work. It aborts and gives me this message:
"assert failed: getpropt("ro.product.device") == "LT81i" || getprop(ro.build.product") == "LT81i" (there's loads more. further down in the text it says "LT15i" - should I write it all?)
And then at the end it says E:Error in /sdcard/filename
I'm stumped. And pretty frustrated. I must have screwed up big at some point
If you guys could offer some help I would be very, very happy.

Bobbles D said:
Hi all
My first post here. And unfortunately it's because I seem to have messed up badly.
I recently successfully unlocked the bootloader and installed Cyanogenmod 7.1.01.
Yesterday I wanted to upgrade to 7.1.0.2 and I went through the exact same steps as when I installed Cyanogen the first time. Everything seemed to go smoothly. But when booting the phone it began to boot loop.
I then tried using Flashtool to relock the bootloader so I could get it back to stock and start over. But Flashtool won't recognize the phone. I can get it into flash mode (blue led). And I've put the LT15.sin file in the loaders folder. I've tried using the two latest versions of Flashtool with no luck.
Then I tried using Fastboot to wipe the phone. I found a page on XDA I think, which had a command listed for doing so. Can't find the page now though.
It seemed to work, well, the command completed. But now when I try to install Cyanogenmod through ClockworkMod Recovery it doesn't work. It aborts and gives me this message:
"assert failed: getpropt("ro.product.device") == "LT81i" || getprop(ro.build.product") == "LT81i" (there's loads more. further down in the text it says "LT15i" - should I write it all?)
And then at the end it says E:Error in /sdcard/filename
I'm stumped. And pretty frustrated. I must have screwed up big at some point
If you guys could offer some help I would be very, very happy.
Click to expand...
Click to collapse
Are you using latest CM7 kernel and check .zip file md5 checksum.
Edit: 7.1.0.1 and 7.1.0.2 had different kernel.
Sent from my MT15i using Tapatalk

I don't really know how to check the MD5. I downloaded from download.cyanogenmod.com.

Bobbles D said:
I don't really know how to check the MD5. I downloaded from download.cyanogenmod.com.
Click to expand...
Click to collapse
Www.google.com wil help you "how to check md5 checksum"
What about kernel, are you flashed latest what was included into zip what you downloaded??
Sent from my MT15i using Tapatalk

Noted
The checksums are different with both downloads. 7.1.0.1 and 7.1.0.2.
What does it mean?
I'm not sure about kernel. I've just used the packages I've downloaded.
I'm new to all this so it's probably something obvious I've missed.
Edit: I've looked through the 7.1.0.2 folder and can't find anything related to kernel. What should I look for?

Bobbles D said:
Noted
The checksums are different with both downloads. 7.1.0.1 and 7.1.0.2.
What does it mean?
I'm not sure about kernel. I've just used the packages I've downloaded.
I'm new to all this so it's probably something obvious I've missed.
Click to expand...
Click to collapse
Are you comparing downloaded files md5 and that number what is cynogen website....
If yes then just redownload those files and check agen..then copy zip your sdcard and Check agen.
And unzip this zip..this includes kernel and readme also.
Sent from my MT15i using Tapatalk

taaviu said:
Are you comparing downloaded files md5 and that number what is cynogen website....
If yes then just redownload those files and check agen..then copy zip your sdcard and Check agen.
And unzip this zip..this includes kernel and readme also.
Sent from my MT15i using Tapatalk
Click to expand...
Click to collapse
EDIT: im messed FXP and offical CM7 bootloops coming almost evry time if you dont had right kernel.
Look development section and give a try FXP rom. There is nice guide how to install and what orders.
Sent from my MT15i using Tapatalk

Ahh, I'm stupid. The checksums match now.
I've unzipped the zip on my SD card. But I can't find a read me or kernel.
Hmm. What am I doing wrong.

taaviu said:
EDIT: im messed FXP and offical CM7 bootloops coming almost evry time if you dont had right kernel.
Look development section and give a try FXP rom. There is nice guide how to install and what orders.
Sent from my MT15i using Tapatalk
Click to expand...
Click to collapse
OK, I'll check it out and give it a try.
BTW, I tried installing Cyanogen again. But it gives me the same error as before and aborts. Will the proper kernel fix this?
And thanks a million for your help so far

Is the boot.img file the kernel? I've already flashed the phone using Fastboot. I used the boot.img from the Cyanogenmod 7.1.0.2 zip. Is this the right thing to do?

Bobbles D said:
Is the boot.img file the kernel? I've already flashed the phone using Fastboot. I used the boot.img from the Cyanogenmod 7.1.0.2 zip. Is this the right thing to do?
Click to expand...
Click to collapse
YES. Evry new relase includes new kernel. Flash it via fastboot and then wipe all and install that zip
Sent from my MT15i using Tapatalk

taaviu said:
YES. Evry new relase includes new kernel. Flash it via fastboot and then wipe all and install that zip
Sent from my MT15i using Tapatalk
Click to expand...
Click to collapse
Thx
But.....
It doesn't work. It gives me the same error message. I've wiped everything. But it still aborts and won't install.
Oh boy..

So: apparently when I tried to update I hadn't flashed the phone with the new kernel. Which caused the bootlooping.
And then, somehow afterwards, I broke something which means that it won't install Cyanogenmod.

Bobbles D said:
So: apparently when I tried to update I hadn't flashed the phone with the new kernel. Which caused the bootlooping.
And then, somehow afterwards, I broke something which means that it won't install Cyanogenmod.
Click to expand...
Click to collapse
Try flash another rom and kernel and then try agen install CM7
Sent from my MT15i using Tapatalk

If you're still not sorted, have a look HERE

Thanks guys. I'll give it another shot later. Bit busy now, got a friend over.
Thanks again.

So... I managed to flash the phone and now the Cyanogenmod is installed again. But it still bootloops. I flashed the kernel from the 7.1.0.2 package and installed the 7.1.0.2 package afterwards.
Isn't this supposed to work? What can I do now?
Man, I'm pulling my hair out right now. LOL.

Have you tried flashing the complete 4.0.2.A.0.42 rom ( from http://forum.xda-developers.com/showpost.php?p=14265967&postcount=3 )
with flashtool? And then Start from the beginning with the CM install.

Galomtala said:
Have you tried flashing the complete 4.0.2.A.0.42 rom ( from http://forum.xda-developers.com/showpost.php?p=14265967&postcount=3 )
with flashtool? And then Start from the beginning with the CM install.
Click to expand...
Click to collapse
Yeah, tried that. The problem is that Flashtool can't find my phone.

I've also tried some of the stuff here:
http://forum.xda-developers.com/showthread.php?t=1116970
Is there a way to completely wipe the phone and return it to stock?

[q] Please, need a little help here.

Hi everyone, i just had my Xperia Arc stuck at the bootscreen after doing these steps.
I previously had the Generic firmware of Xperia Arc S for my Arc, on Ice Cream Sandwich flavor of Android.
Today i started trying to figure out how to flash the CM 9 Rom, because i have it on my Kindle fire, but it failed.
I've did all the steps to Unlock my bootloader, and, even tho my phone is eligible for that ( i checked it on the services menu ), i could not Unlock it.
After retrieving the Key and running the fastboot i had the Message "Remote: oem unlock failed".
After giving up to unlock it, i decided to install "X-Parts" and install the CMW so i could flash the .zip file of the CM9 Right from the SDCard.
Ok, thats what i did:
1. Installed CMW
2. Wiped Data / Factory Reset
3. Wiped Cache
4. Flashed .zip from SDCARD
5. Zip Installed
6. Repeated steps 2 and 3 again
7. Rebooted
Since them, i am stuck at the Bootscreen with the word "Sony" on it, which leads me to think that the rom was not flashed properly, otherwise i would see the cyan / black bootscreen.
Also, i can't manage to boot into "recovery mode" again, i am pressing Power + Volume Down but it is not working.
Any idea of what can i do now ?
How can i install cm9 properly and unstuck my phone ?
Do i need to unlock my BL in order to install CM9 ?
Thanks in advance and sorry about this, but i am sort of desperate this time

Just tried to Flash the "boot.img" file found at the CM9 zip folder using FLASHTOOL, but it says:
"20/016/2012 15:16:27 - INFO - FASTBOOT Output:
sending 'boot' (4916 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.001s"
My device IS rooted, and i can garantee it.

Just extracted the Kernel.sin file from the .ftf Generic Firmware of ICS Android rom and tried to Flash using the Flashtool via Fastboot mode.
Same error saying that my device must be rooted.

marcelloLins said:
Just extracted the Kernel.sin file from the .ftf Generic Firmware of ICS Android rom and tried to Flash using the Flashtool via Fastboot mode.
Same error saying that my device must be rooted.
Click to expand...
Click to collapse
If the problem resides in rooting your phone, try this http://forum.xda-developers.com/showthread.php?t=1653188 remember, SEARCH is a friend!

in order to flash kernels via fastboot you need your bootloader unlocked
it is bootlooping on CM because you arent using right kernel
not too sure why your having issues unlocking it, but this is probably the first thing you need to tackle
all i can recommend is to keep trying
but im sure someone more helpfull will be along soon!!
and just FYI, just because nobody is answering doesnt mean you need to start a new thread in another section, especially development as its hard enough to navigate without usless threads. just search or use google!

firedeimos said:
If the problem resides in rooting your phone, try this http://forum.xda-developers.com/showthread.php?t=1653188 remember, SEARCH is a friend!
Click to expand...
Click to collapse
Do you understand that i can't even boot my phone ?
How am i supposed to Root it if i can't even make it boot ?
Please, any help here is welcome.
By the way, i AM searching, alot, for more than 4 hours already

its also worth noting that when it says device must be rooted, it is in relation to bootloader not being unlocked (as far as im aware)

yo-meister said:
its also worth noting that when it says device must be rooted, it is in relation to bootloader not being unlocked (as far as im aware)
Click to expand...
Click to collapse
So you are saying that i must try to Unlock my bootloader first, even tho i can't seem to make it boot ?
Not trying to be an ass, but i just can't seem to find a way to do it.
I have my IMEI wrote in a notepad file, but, once i try to unlock it's bootloader, it gives me an error. : "Remote: oem unlock failed!"
Not sure why this is happening, i am following the instructions on Sony Website...

to use a rom like CM, you need a custom kernel and to install a custom kernel you need to unlock bootloader
there are a few that dont require unlock but i havent personally tried these as mine is unlocked
its been a while since i unlocked mine but i seem to remember that you leave the last digit off when typing it in, someone confirm?
i was confused when i was putting in the number as it was longer than what was requested

yo-meister said:
to use a rom like CM, you need a custom kernel and to install a custom kernel you need to unlock bootloader
there are a few that dont require unlock but i havent personally tried these as mine is unlocked
its been a while since i unlocked mine but i seem to remember that you leave the last digit off when typing it in, someone confirm?
i was confused when i was putting in the number as it was longer than what was requested
Click to expand...
Click to collapse
I Love You.
Yes, i just did what you said.
We must ignore the LAST digit of IMEI, i was ignoring the first, since it was ZERO i thought that it would not matter.
Now that i have a new Bootloader Code, i used it and it worked.
Thanks a bunch, now, i must try to continue the process.
I will keep you guys updated
Update 1: The Bootloader is unlocked.
I tried to Flash the kernel.sin using the flashtool and seems like it was flashed correctly but i am still stuck in bootscreen.
Also, i still can't manage to boot in Recovery Mode to flash the CM9 from the SDCARD.
Any ideas?
Update 2: Flashed DoomKernel V04 Successfuly now i am trying to get into Recovery mode so that i can Finally Flash the cm9 rom in the sdcard.
wish me luck
Update 3: After booting into recovery mode, and trying to flash the CM9 .zip file, there is an error.
"Assert Failed: getprop..." From what i know of programming, this looks like the rom trying to assert that the values from the build.prop file must match either "LT18a","LT15i","LT15a" or "anzu".
Is there any way i can fix the file in order to make this "assert" directive works correctly ?

ha your welcome
i lost all my contacts when i first started all this, didnt backup with google account lol
now its just a case of...
put rom on SD CARD
BACKUP
wipe
flash kernel
flash rom
flash wifi modules (if required)
BOOT
and this is the first time i feel like i can say this...hit thanks if i helped haha

Just tried to Toggle the Assert Directives OFF from the DoomKernel but it is still checking for the asserts when trying to flash the Rom.
Any suggestions?

Just tried to Connect VIA ADB with the Phone in Recovery mode, and it worked.
My plan was to Pull the Build.prop file so i could edit and them, paste it back to the phone system so that the assert might work.
Here is the command i tried :
adb devices (OK)
adb pull /system/build.prop c:\build.prop
Error Message : remote object 'system/build.prop' does not exist
What can i do now ?
UPDATE 1: On Recovery Mode i just mounted the System and Data And Ext 2 Partitions and i still cannot seem to PULL the Build.prop File.
UPDATE 2: Flashed the Right kernel from the CM9 Pack, which is the FXP Team Kernel.
Tried to Flash again, now without assert verifications and i am receiving an error : E: Failed to Load Keys

marcelloLins said:
Just tried to Connect VIA ADB with the Phone in Recovery mode, and it worked.
My plan was to Pull the Build.prop file so i could edit and them, paste it back to the phone system so that the assert might work.
Here is the command i tried :
adb devices (OK)
adb pull /system/build.prop c:\build.prop
Error Message : remote object 'system/build.prop' does not exist
What can i do now ?
UPDATE 1: On Recovery Mode i just mounted the System and Data And Ext 2 Partitions and i still cannot seem to PULL the Build.prop File.
UPDATE 2: Flashed the Right kernel from the CM9 Pack, which is the FXP Team Kernel.
Tried to Flash again, now without assert verifications and i am receiving an error : E: Failed to Load Keys
Click to expand...
Click to collapse
So did you manage to get it work?
If not,this is what i would do:
1.Reflash stock fw
2.Root it
3.Install CWM
4.Try it,is it working,if yes flashed custom kernel for rom that i'm trying to flash
5.Then go to CWM and install rom and modules
6.Reboot the phone from CWM Menu and that should be it.It has to work.
I think these steps are easy to follow and no need to be a professional with programing to do it.Hope it will work for you.Cheers

pren22 said:
So did you manage to get it work?
If not,this is what i would do:
1.Reflash stock fw
2.Root it
3.Install CWM
4.Try it,is it working,if yes flashed custom kernel for rom that i'm trying to flash
5.Then go to CWM and install rom and modules
6.Reboot the phone from CWM Menu and that should be it.It has to work.
I think these steps are easy to follow and no need to be a professional with programing to do it.Hope it will work for you.Cheers
Click to expand...
Click to collapse
You mean Stock Firmware from Sony Ericson ?
Where can i find it ?
Is this one ?
http://uploaded.net/file/lpdhtmqi/LT15i_4.0.2.A.0.62_Generic Global World.ftf
I will try to flash it and see where i can get.
I just tried another flavor of CM9 (A nightly build) and i had the same error

marcelloLins said:
Just extracted the Kernel.sin file from the .ftf Generic Firmware of ICS Android rom and tried to Flash using the Flashtool via Fastboot mode.
Same error saying that my device must be rooted.
Click to expand...
Click to collapse
Try to flash an entire official firwmare with flashtool in flashmode mode (a 4.0.3 for easy rooting). So you ended with a working phone in a good mood. After that, root, install recovery, check if phone is always unlocked and try again with CM9.

spidermoon said:
Try to flash an entire official firwmare with flashtool in flashmode mode (a 4.0.3 for easy rooting). So you ended with a working phone in a good mood. After that, root, install recovery, check if phone is always unlocked and try again with CM9.
Click to expand...
Click to collapse
I am downloading this one :
http://uploaded.net/file/lpdhtmqi/LT15i_4.0.2.A.0.62_Generic Global World.ftf
Is there any problem with that ?
Update: These steps solved my problems:
1. Flash the 4.0.3 Android ICS Stock Firmware
2. Flash the Kernel from CM9
3. Wipe Factory and Cache
4. Flash the CM9
5. Flash Gapps
Reboot.
Thanks for all the help guys

[Q] Error code 7 when flashing Rom

So i was currently running an older version of AOKP and it suddenly got stuck in the boot animation (its done this before might i add) so i went into recovery and attempted to wipe and factory reset and now when i try to flash a new rom i get the "E:error in /sdcard/aokp_toro_jb_build-3.zip (status 7)". Was wondering if anyone had any ideas or if im just doing something really stupid. I would upload a new rom from the internet but my phone is no longer recognized by my computer.

mjv5117 said:
I would upload a new rom from the internet but my phone is no longer recognized by my computer.
Click to expand...
Click to collapse
Meaning that you cannot use ADB sideload for pushing files? Do you have any other ROM on the phone's memory you can flash? Have you tried updating your recovery?
If none of the above works, you probably need to do an ODIN flash. But be careful with that... Don't check the wrong settings :silly:

Yes
I have other ROMS on my phone but whenever i try to flash those i also get the error code 7. And im not entirely sure what you mean by ADB sideload but whenever i connect my phone to my computer the device isn't recognized and i can't use it like a storage device in order to put a different, and more updated Rom
boype said:
Meaning that you cannot use ADB sideload for pushing files? Do you have any other ROM on the phone's memory you can flash? Have you tried updating your recovery?
If none of the above works, you probably need to do an ODIN flash. But be careful with that... Don't check the wrong settings :silly:
Click to expand...
Click to collapse

mjv5117 said:
So i was currently running an older version of AOKP and it suddenly got stuck in the boot animation (its done this before might i add) so i went into recovery and attempted to wipe and factory reset and now when i try to flash a new rom i get the "E:error in /sdcard/aokp_toro_jb_build-3.zip (status 7)". Was wondering if anyone had any ideas or if im just doing something really stupid. I would upload a new rom from the internet but my phone is no longer recognized by my computer.
Click to expand...
Click to collapse
This happened to me and when I flashed a new kernel (a compatible one) it worked....try flashing a new kernel like lean kernel or Glados and let us know what happens....an incompatible kernel "usually" causes boot loops or restoring data on an incompatible ROM

Thanks
Somehow managed to find an old trinity kernel on my phone which i flashed first, and then somehow flashed an even older version of AOKP over top of it in order to connect so i can flash an even newer ROM. All in all flashing the kernel worked thanks for all the help. That is also the second time that my AOKP ROM just randomly got stuck in boot.

Zip signature error - only when flashing kernels

I'm having a strange problem when I flash kernels (tried for Xcelerate and Beast kernels on both CM11, CM12.1), TWRP 2.8.6 gives the "e:Zip signature verification failed: 1" error message . The zip files for the kernels are perfectly fine - tested fine using archiver app and I don't face the same problem when flashing roms (MIUI/CM11/12/etc).
Turning zip verification off in TWRP allows the flashing process to complete normally but checking the kernel version under settings shows that it hasn't changed (still shows kratos/jsevi for CM11/12.1).
Any ideas?

barrack1 said:
I'm having a strange problem when I flash kernels (tried for Xcelerate and Beast kernels on both CM11, CM12.1), TWRP 2.8.6 gives the "e:Zip signature verification failed: 1" error message . The zip files for the kernels are perfectly fine - tested fine using archiver app and I don't face the same problem when flashing roms (MIUI/CM11/12/etc).
Turning zip verification off in TWRP allows the flashing process to complete normally but checking the kernel version under settings shows that it hasn't changed (still shows kratos/jsevi for CM11/12.1).
Any ideas?
Click to expand...
Click to collapse
FYI, i never ticked/marked the zip signature while flashing beast or xcelerate kernel, and all of them works fine with the rom.
after clean install, i reboot to rexovery and i flash the kernel and reboot, never wipe anything

presetz said:
FYI, i never ticked/marked the zip signature while flashing beast or xcelerate kernel, and all of them works fine with the rom.
after clean install, i reboot to rexovery and i flash the kernel and reboot, never wipe anything
Click to expand...
Click to collapse
I did a clean install several times with different rom-kernel combinations and I keep running into the same problem. I think its related my other problem of looping in recovery (twrp) after performing a factory reset in cm11/12.1.

barrack1 said:
I did a clean install several times with different rom-kernel combinations and I keep running into the same problem. I think its related my other problem of looping in recovery (twrp) after performing a factory reset in cm11/12.1.
Click to expand...
Click to collapse
did you flashed twrp recovery.img to boot option, instead of recovery option?
if that case, youll get looping to twrp, instead of system. IMO

presetz said:
did you flashed twrp recovery.img to boot option, instead of recovery option?
if that case, youll get looping to twrp, instead of system. IMO
Click to expand...
Click to collapse
I don't know what you mean there. I flashed twrp using fastboot.
I have no problems with using TWRP to flash customs roms multiple times (except for flashing kernels).
edit-
Steps I took to flash kernel-
- start twrp recovery and wipe everything except for external sdcard and usb otg
- flash rom cm11/12.1/etc
- wipe cache/dalvik
- reboot to system and check that everything is fine etc
- power off and start in twrp to flash kernel
- get error msg as stated in my OP

barrack1 said:
I don't know what you mean there. I flashed twrp using fastboot.
I have no problems with using TWRP to flash customs roms multiple times (except for flashing kernels).
edit-
Steps I took to flash kernel-
- start twrp recovery and wipe everything except for external sdcard and usb otg
- flash rom cm11/12.1/etc
- wipe cache/dalvik
- reboot to system and check that everything is fine etc
- power off and start in twrp to flash kernel
- get error msg as stated in my OP
Click to expand...
Click to collapse
sorry, just my experienced with twrp looping that i encountered once.
i dont know if it help, but i moved the kernel.zip in the internal storage before i flashed it.
edit: just curious, before you flashed kernel, had you double checked, if the zip verification was unmarked in twrp>setting ?

presetz said:
sorry, just my experienced with twrp looping that i encountered once.
i dont know if it help, but i moved the kernel.zip in the internal storage before i flashed it.
edit: just curious, before you flashed kernel, had you double checked, if the zip verification was unmarked in twrp>setting ?
Click to expand...
Click to collapse
I think so but I make sure zip verification is always toggled on in the install menu. There is no reason to turn it off since verification is very quick and doesn't cost anything.
But even when I turn it off, the kernel doesn't seem to have changed from what I see in the kernel version info under settings after I reboot the phone - as stated in the OP.

barrack1 said:
I think so but I make sure zip verification is always toggled on in the install menu. There is no reason to turn it off since verification is very quick and doesn't cost anything.
But even when I turn it off, the kernel doesn't seem to have changed from what I see in the kernel version info under settings after I reboot the phone - as stated in the OP.
Click to expand...
Click to collapse
okay, last i remembered,i once encountered no changed on kernel, but i saw some posting at xcelerate thread, that it had to flashed on top of stock boot.img, the file extracted from the rom.zip,
flashed the boot.img first then straight to flash the kernel.zip.
if you already tried that and still had the issued, then im wondering why too...

presetz said:
okay, last i remembered,i once encountered no changed on kernel, but i saw some posting at xcelerate thread, that it had to flashed on top of stock boot.img, the file extracted from the rom.zip,
flashed the boot.img first then straight to flash the kernel.zip.
if you already tried that and still had the issued, then im wondering why too...
Click to expand...
Click to collapse
Is the boot.img from CM11/12.1 or miui rom? From what I understand, the boot.img flash is only if the kernel is other than cm11/12.1 like Beast/Xcelerate/Carbon. Since I'm only on on CM11 or 12.1 on a clean flash without any other modifications theres no point in flashing boot.img (from CM11/12.1).

barrack1 said:
Is the boot.img from CM11/12.1 or miui rom? From what I understand, the boot.img flash is only if the kernel is other than cm11/12.1 like Beast/Xcelerate/Carbon. Since I'm only on on CM11 or 12.1 on a clean flash without any other modifications theres no point in flashing boot.img (from CM11/12.1).
Click to expand...
Click to collapse
yup, thats true, i have encountered that after clean install while still on cm12 and the procedure was worked for me.

presetz said:
yup, thats true, i have encountered that after clean install while still on cm12 and the procedure was worked for me.
Click to expand...
Click to collapse
Err what do you mean? Encountered what? Did you still have to flash boot.img from cm11/12.1 or miui?

barrack1 said:
Err what do you mean? Encountered what? Did you still have to flash boot.img from cm11/12.1 or miui?
Click to expand...
Click to collapse
sorry my mistaken, thought that my problem was the same with yours with no changed kernel after flashin custom kernel while back at cm12
and no, i didnt need to flashed boot.img first before custom kernel ever since cm12.1 clean install

[Q] Need help in solving "Unfortunately, settings have stopped working" error

[Q] Need help in solving "Unfortunately, settings have stopped working" error
Problem: My unrooted SGH-I747 model AT&T GS3 recently gave me this error whenever trying to access the settings. The error shows up even after a full factory reset and I can no longer access my phone. Stuck a little after the language selection in the beginning stages of the setup.
Attempted fixes: Obviously, the initial factory reset. Then clearing the cache + factory reset.
After those failed to work, I tried to flash to a AT&T stock rom from this forum (http://forum.xda-developers.com/showthread.php?p=33570269#post33570269) using Odin. I tried to use the first row of downloads but the first row but it did not have a MD5 file, so I used the second row of downloads instead but this rom failed to install. My guess is that it may be too old of a version.
I would appreciate any help.
[SOLVED]
The problem may have arose from a critical error in the phone's software that had affected the OS system of the phone. I resolved the issue by flashing a new custom OS (cyanogenmod) to my phone. These are the steps that I took:
1. Installing Odin (http://forum.xda-developers.com/showthread.php?t=1722686)
2. Rooting my cellphone with CFAutoRoot using Odin (http://forum.xda-developers.com/showthread.php?t=1725839)
3. Installing a custom recovery TWRP -- highly recommended very user friendly (http://forum.xda-developers.com/showthread.php?t=1793224)
4. Installing a new custom rom through TWRP-- used Cyanogen (http://forum.xda-developers.com/showthread.php?t=1778270)
5. Installing gapps (http://opengapps.org/?api=5.1&variant=nano)
6. Identifying the correct bootloader by downloading and installing Samsung Phone Info by vndnguyen through the Play Store.
7. Installing the correct bootloader and modem (http://forum.xda-developers.com/galaxy-s3-att/general/rooted-ucufnj1-stock-rom-t2985006)
Please refer to respective installation guides for more instructions regarding installation of any new software.
I hope this helps anyone who may have run into the same problem.

Before attempting to flash anything, confirm the bootloader on your phone. An easy way to determine if the bootloader is 4.3 or newer, boot into download mode. If you see anything about warranty bit, your phone has at least a 4.3 bootloader and no attempts should be made to flash anything from sammobile.com.
If you have a 4.3 or newer bootloader, I recommend flashing a custom recovery such as TWRP, and then flashing a stock ROM from recovery.

First off, thank you for the reply audit!
Now I have officially rooted my phone using CF-Autoroot and have installed TWRP. I have also confirmed that the bootloader is at least 4.3 because it does show the warranty bit.
Which of the stock roms are compatible with this bootloader?

Do you want to stay on a stock ROM? If not, you could flash a custom ROM such as cm12.1 using TWRP. Once you have flashed a custom ROM, you can look under settings to determine the baseband on the phone which is another clue as to which bootloader is on your phone.

audit13 said:
Do you want to stay on a stock ROM? If not, you could flash a custom ROM such as cm12.1 using TWRP. Once you have flashed a custom ROM, you can look under settings to determine the baseband on the phone which is another clue as to which bootloader is on your phone.
Click to expand...
Click to collapse
Just to be clear, cm12.1 is the cyanogenMod nightly?

Yup. If you flash it, your baseband may be unknown which tells me you are probably not running a 4.4.2 bootloader and modem.

audit13 said:
Yup. If you flash it, your baseband may be unknown which tells me you are probably not running a 4.4.2 bootloader and modem.
Click to expand...
Click to collapse
I'll try it out and see if I can get past the language screen this time.

Got the latest Cyanogenmod Zip file onto my phone. Tried flashing it through TWRP with the install option but it failed.
Log reads that no MDS file was found, detected filesystem ext4 for /dev/block/platform msm_sdcc.1/byname system. Can't install this package on top of incompatible data.

CM12.1 won't have an md5 file. You're trying to install cm12.1 for the d2att or d2lte? You're running the latest TWRP which I believe is 2.8.7.0? or 2.8.7.1?

5K posts.
"all i can really do , is stay out of my own way and let the will of heaven be done"

I'm pretty sure that CM de-unified the variants for CM 12.
From: https://wiki.cyanogenmod.org/w/D2lte_Info
Note: Unified device
Between the release of CM 11 M3 and CM11 M12, all Qualcomm-based variants of this device were merged into a single build: d2lte. The device information pages for the individual variants should be used to reference any device-specific unlock instructions, download recoveries, to build CM 10.2, or to install CM 12.1: d2att, d2cri, d2mtr, d2spr, d2tmo, d2usc, d2vzw.
Click to expand...
Click to collapse
I think this was just to make searching a bit harder/ more complicated.

audit13 said:
CM12.1 won't have an md5 file. You're trying to install cm12.1 for the d2att or d2lte? You're running the latest TWRP which I believe is 2.8.7.0? or 2.8.7.1?
Click to expand...
Click to collapse
For d2att and running 2.8.7.0 for TWRP.

You should be good then.

The file should be left unzipped/unrared when using it right? I'm using it as such but it keeps returning the same error message saying that it won't install it.

Yes, leave it zipped. What is the TWRP error message?

The error log:
detected filesystem ext4 for /dev/block/platform msm_sdcc.1/byname system.
Can't install this package on top of incompatible data.
Please try another package or run a factory reset
E: Error executing updater binary in zip '/sdcard/Download/cm-12.12015913-NIGHTLY-dtatt.zip
Error flashing zip '/sdcard/Download/cm-12.120150913-NIGHTLY-D2att.zip

Weird, did you do a full wipe before trying to install?

Can't believe it was that simple. I thought I had already made the wipe when I did it with the original recovery but making a second wipe through TWRP actually helped make it happen. I finally got through and have full access to my phone.
Unfortunately, the cell service doesn't seem to work but I'm guessing that I need to do more for the set up?
Edit: Not recognizing the sim card for some reason

Sounds like you need to update the bootloader and modem to the older KK version which I think is ne4.

Sorry for the late reply I've been busy the past week. I'm guessing the modem won't work without the proper bootloader? I've tried flashing the latest and original modem from the Modem list (http://forum.xda-developers.com/showthread.php?t=1831898). While they installed successfully I still don't get a signal.
I was worried which bootloader to take because it may lead to bricking. Which one are you referring to and are they in the Bootloader updates topic here? (http://forum.xda-developers.com/showthread.php?t=2321310)