Develop Bugs

[Q] Problem Downgrading from 4.2.1

I had the offical 4.2.1 and then unlocked bootloader.
Now i wanted to use AOKP Jellybean Milestone 1 (4.1.2) but the rom makes weird things. Does not reboot (when i click it) and the sim card is not recognized (just "no service", i cannot enter my pincode).
I already flashed some radios.
I have an GSM Galaxy Nexus (free) and use it with a german O2 Sim card.
Can anybody help?

Did you go into recovery and make a full wipe then flash the AOKP ROM? If not, then try it this way
Regarding radios, XXLH1 is very fine with me and it is the latest standard european baseband according to this thread.

ahmadallica said:
Did you go into recovery and make a full wipe then flash the AOKP ROM? If not, then try it this way
Regarding radios, XXLH1 is very fine with me and it is the latest standard european baseband according to this thread.
Click to expand...
Click to collapse
I use cwm and i wiped data/factory reset and wiped cache. Or is there a full wipe option?
I am back on 4.2.1 and reflashed the XXLH1 radio. But this doesn't work on 4.1.2

JonnyZaggi said:
I use cwm and i wiped data/factory reset and wiped cache. Or is there a full wipe option?
I am back on 4.2.1 and reflashed the XXLH1 radio. But this doesn't work on 4.1.2
Click to expand...
Click to collapse
That's correct about wiping and you may even wipe "dalvik cache" as well.
XXLH1 was working fine with me on 4.1.2 as far as I remember.
Since you are now on 4.2.1, then go into recovery (which should be latest TWRP or CWM), wipe data, cache, and dalvik, then install a ROM other than AOKP. There are a lot in the development forum and stable ones. If everything went fine and your radio is working on 4.1.2, then again wipe everything and try the AOKP so at least you already confirmed the radio is working fine on 4.1.2

Help my phone is messed

I have a d2can with a d2att recovery and im on Telus network.
So I flashed a ported ROM (MSG CHUBZ) from a sprint s3 which I think is T999 or something, and now everytime I format data and factory reset. my phone calls immediately hang up and texts fail..
Help..?

Adizzzle said:
I have a d2can with a d2att recovery and im on Telus network.
So I flashed a ported ROM (MSG CHUBZ) from a sprint s3 which I think is T999 or something, and now everytime I format data and factory reset. my phone calls immediately hang up and texts fail..
Help..?
Click to expand...
Click to collapse
I flashed that ROM last night also...
Had that problem last night after restoring my paranoid android backup.
I did a full wipe. Cache, dalvik, system, factory reset and than restored my backup and it went away.
Something in that flash stuck around after a wipe. I was really freaked out last night. I never flash tw ROMs and that made me want to never again...
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Adizzzle said:
I have a d2can with a d2att recovery and im on Telus network.
So I flashed a ported ROM (MSG CHUBZ) from a sprint s3 which I think is T999 or something, and now everytime I format data and factory reset. my phone calls immediately hang up and texts fail..
Help..?
Click to expand...
Click to collapse
Just flash a d2can rom. Should fix your problem. Ports are not always reliable and it may not "like" your phones hardware.

aybarrap1 said:
Just flash a d2can rom. Should fix your problem. Ports are not always reliable and it may not "like" your phones hardware.
Click to expand...
Click to collapse
I have flashed a d2can and formatted and factory reset it as well.. any other suggestion please? Cache, dalvik, and fixed permissions too..

Adizzzle said:
I have flashed a d2can and formatted and factory reset it as well.. any other suggestion please? Cache, dalvik, and fixed permissions too..
Click to expand...
Click to collapse
You can always go the long way and it may help. Wipe everything from custom recovery (system, data, cache, dalvik, internal sd card) and then go into download mode and ODIN back to stock. Factory reset then proceed to rooting and installing as you wish.

[Q] Am I missing something?

Short Questions: when I flash any ROM, besides official AOKP, my phone goes into bootloop. I'm using CWM. I do a factory reset/cache etc. then flash the new ROM, i.e. stock koodo, but they all just boot loop.
Long Story: I used to have a samsung galaxy ace, and I followed the same persedure, with CWM, and it always worked. I used CWM on my tablet, but the other touch recover has given me problems and never really worked correctly, it wouldn't even install properly. I prefer CWM. From searching around, there is some super wiper, or infamus whiper that clean the phone properly from the recover before flashing. I'm not sure if we're supose to use that before I flash a new ROM, maybe that's why its bootlooping?
What do you do before you flash a ROM? I know the ROM OP have instructions, but they end in a bootloop too.

I believe you have to be more specific if you want to get help, like the version of CWM, ROM you are trying to install and steps you are taking to insall the ROM.

Click mounts & storage, format system/data, yes. Then do all your other wiping like data and caches. Then flash ROM followed by gapps.

bobiscool07 said:
Short Questions: when I flash any ROM, besides official AOKP, my phone goes into bootloop. I'm using CWM. I do a factory reset/cache etc. then flash the new ROM, i.e. stock koodo, but they all just boot loop.
Long Story: I used to have a samsung galaxy ace, and I followed the same persedure, with CWM, and it always worked. I used CWM on my tablet, but the other touch recover has given me problems and never really worked correctly, it wouldn't even install properly. I prefer CWM. From searching around, there is some super wiper, or infamus whiper that clean the phone properly from the recover before flashing. I'm not sure if we're supose to use that before I flash a new ROM, maybe that's why its bootlooping?
What do you do before you flash a ROM? I know the ROM OP have instructions, but they end in a bootloop too.
Click to expand...
Click to collapse
You are not formatting system before installing a different base(ROM).
If you format system, data, cache, and delvik you should be good to go.

[Q] updating modem/bootloader/kernel/rom to kk4.4

General info ...
Update from:
Bootloader: (???same as modem???)
Modem: I747UCDMG2 (http://forum.xda-developers.com/showthread.php?t=1831898)
ROM: CM 10.2 (http://download.cyanogenmod.org/?device=d2att)
GAPPS: 20130813 (http://wiki.cyanogenmod.org/w/Gapps)
TO
Bootloader: I747UCUEMJB (http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23)
Modem: I747UCUEMJB (http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23)
ROM: CM 11 nightlies (http://download.cyanogenmod.org/?device=d2att)
GAPPS: 20131119 (http://wiki.cyanogenmod.org/w/Gapps)
Does this setup look alright? Will it work?
Any danger of incompatibities/brick?
Any need for I747UCUEMJB kernel? Or, is it included/superseeded by CM 11? (http://forum.xda-developers.com/showpost.php?p=47816011&postcount=18)
Thanks!

You can flash any ROM you want after upgrading your boot loader. Just do not try to downgrade your boot loader to anything below 4.3 as it will result in a hard brick.

Can't Flash anything
I was on stock 4.3 and i decided to upgrade to the [ROM][9.15.14] LikeWise Galaxy S5 | TouchWiz 4.4.2 | NE4 | Version 4.1.
It didn't work. It gets stuck on the s5 samsung logo boot. I decided to return to 4.3 but it doesn't work it gives the status 7 error.
Files i have
1. d2att_I747UCUEMJB_modem.zip
2. I747UCUEMJB_bootloader.............. I am not able to flash this
3. att-LikeWise-v4.1-NE4-9-15-14
4. update43

Status 7 errors can happen with an outdated bootloader.
I highly recommend Philz Touch which can be flashed in Odin or from your existing custom recovery.

audit13 said:
Status 7 errors can happen with an outdated bootloader.
I highly recommend Philz Touch which can be flashed in Odin or from your existing custom recovery.
Click to expand...
Click to collapse
yea i used philz_touch_6.07.9. I also tried flashing I747UCUEMJB_bootloader because i suspected that i couldn't revert to 4.3 because of an outdated bootloader, but that didn't work either.
I will really love that S5 ROM but now i can't even flash anything.
I can view my recovery and download mode.

I suggest downloading a CM11 for a d2lte and flash it in recovery. Before flashing, I recommend that you wipe cache, dalvik, data, and system. After flashing, wipe cache, data, and dalvik again just to be sure everything has been cleared, then boot the phone.

audit13 said:
I suggest downloading a CM11 for a d2lte and flash it in recovery. Before flashing, I recommend that you wipe cache, dalvik, data, and system. After flashing, wipe cache, data, and dalvik again just to be sure everything has been cleared, then boot the phone.
Click to expand...
Click to collapse
Please how do i even know if my s3 at&t is d2att or d2lte?

Slemgen07 said:
Please how do i even know if my s3 at&t is d2att or d2lte?
Click to expand...
Click to collapse
Hey!!! I've installed the CM11 d2lte and it's running perfectly.
Quick one, i'm still interested in installing the likewise S5 ROM. Now that i'm on the CM11, how do i go about it?
Thanks for your assistance, it was highly helpful.

Make sure you have the latest custom recovery on your phone. Copy the custom ROM to your phone, boot into recovery and create a nandroid backup of your current ROM. Once the backup is complete, wipe cache, dalvik, and flash the custom ROM.
Make note of any errors messages you get when flashing the new ROM.

audit13 said:
Make sure you have the latest custom recovery on your phone. Copy the custom ROM to your phone, boot into recovery and create a nandroid backup of your current ROM. Once the backup is complete, wipe cache, dalvik, and flash the custom ROM.
Make note of any errors messages you get when flashing the new ROM.
Click to expand...
Click to collapse
The mistake i was making was that i didn't mount the system after i flashed the Likewise ROM. The moment i did it, it booted correctly. Almost everything is working perfectly fine. If i try to change the lockscreen wallpaper and it brings out the Gallery, wallpaper and err... some other option, when i select the wallpapers for the lockscreen the settings crashes.
You guys are just awesome. Thanks!

Updating SGH-I747 from 4.1.1 to 4.3

I've looked around a bit and can't quite find someone that has had my specific situation.
I have a AT&T S3 SGH-I747 that is rooted running stock 4.1.1 with CWM 6.0.4.7. I have updated the modem and bootloader (Baseband - I747UCUEMJB and Build # JRO03L.I747UCDLK3).
I have tried to flash custom and stock ROMS with CWM but get stuck on the glowing Samsung logo. I have tried to follow the instructions listed here but I cannot flash the stock ROM with ODEN.
I am not sure as to what to attempt next. I first want to be able to update to 4.3/4.4.2 and then try custom builds.
I have all my apps and data backed up with MyBackup and a Nandroid backup as well.
Thank you.

Are you wiping the cache, davilk, and data before of after flashing the ROM?

I wipe/format before the flash. I factory reset, clear cache, clear davilk, format data, and format system then flash the ROM. I've tried several combinations of clearing/formatting. The flash always goes well and then I reboot. The boot goes and then just sits at the Samsung logo (It does make the AT&T sound during this time)

Hubbins said:
I wipe/format before the flash. I factory reset, clear cache, clear davilk, format data, and format system then flash the ROM. I've tried several combinations of clearing/formatting. The flash always goes well and then I reboot. The boot goes and then just sits at the Samsung logo (It does make the AT&T sound during this time)
Click to expand...
Click to collapse
Try to factory reset once the flash is done if it doesn't boot after 5-10min.

Thanks. I'll give it a shot and we'll see how it goes.

Unfortunately that tip did not appear to help. I still got stuck on the glowing Samsung logo.
I was final able to flash 4.3 using the method here using odin.