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

[AOKP] IceColdJelly421 2.0, HBOOT 1.12

Hello,
since I had ICJ 1.5 on my HOX I wanted to do an update to ICJ 2.0.
I have HBOOT 1.12 and my CID is H3G__106. I already tried to install ICJ 2.0 on it, but it gets stuck at the boot animation (the cross^^).
Are there any possibilities to do the update or do I have to live with 1.5 forever?
cheers,
z3xi0n

I'd imagine you need a Jellybean hboot(1.3x), as 2.0 is running on the newer 3.10 kernel.
You could try flashing the rom, and then a 2.6 kernel (http://forum.xda-developers.com/showthread.php?t=1873615) in the same process?

did you fastboot flash the boot.img from the new 2.0 zip?
remember, you need to move all sdcard\0 files to sdcard\
i did it in recovery

i did the following steps..
nandroid backup
full wipe (data, cache, dalik cache)
erase fastboot cache
fastboot flash boot boot.img (from the 2.0 zip)
erase fastboot cache
moved sdcard/0 into sdcard/
flashed the rom
flashed gapps
now it gets stuck at the boot animation (the cross does not glow). after this i tried 1.7.2 and it works perfect

I first had installed a RUU to update my hboot from 1.12 to 1.36, after that i unlocked my hox again and put the new ICJ on it

z3xi0n said:
i did the following steps..
nandroid backup
full wipe (data, cache, dalik cache)
erase fastboot cache
fastboot flash boot boot.img (from the 2.0 zip)
erase fastboot cache
moved sdcard/0 into sdcard/
flashed the rom
flashed gapps
now it gets stuck at the boot animation (the cross does not glow). after this i tried 1.7.2 and it works perfect
Click to expand...
Click to collapse
everything seems right, fastboot erase cache < right? hmm
maybe you want to re download the boot.img?
i actually cleared out all sdcard data, full wiped, install rom + gapps, full wipe again, copy sdcard data and booted

tarreltje said:
I first had installed a RUU to update my hboot from 1.12 to 1.36, after that i unlocked my hox again and put the new ICJ on it
Click to expand...
Click to collapse
Any links for tutorials or something to do the update? Didn't found any Maybe used the wrong search terms ^^
@stevvy: ofc fastboot erase cache ^^

ncx v13
I installed ICJ 2.1, i didnt upgrade my hboot, i am on 1.12. I wanted to use the old kernel. I repacked it, everything was fine.Booted, and was working,but then I installed gapps, and it didnt boot up anymore. I did all the necessary full wipe+dalvik+cache wipe. Any suggestions?

sol81 said:
I installed ICJ 2.1, i didnt upgrade my hboot, i am on 1.12. I wanted to use the old kernel. I repacked it, everything was fine.Booted, and was working,but then I installed gapps, and it didnt boot up anymore. I did all the necessary full wipe+dalvik+cache wipe. Any suggestions?
Click to expand...
Click to collapse
Did u use gapps for 4.2? For note..lowest hboot support at 1.28..
OneX Fueled by Tegra 3 Driven by IceColdJelly
---------- Post added at 12:56 AM ---------- Previous post was at 12:45 AM ----------
z3xi0n said:
Any links for tutorials or something to do the update? Didn't found any Maybe used the wrong search terms ^^
@stevvy: ofc fastboot erase cache ^^
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=32539598 try read here...maybe there can help you out..
OneX Fueled by Tegra 3 Driven by IceColdJelly

[Q] from CyanogenMod 4.2.2 to An older rom

Hi,
I am willing to flash and try CyanogenMod 10 4.2.2, But i am afraid that I won't be able to flash an 4.1.1 custom rom like Viperx afterwards,
After I flash CyanogenMod, can I re-flash an older android version rom ,
there is anyone that have dont it before ?
thank you very much : )

Yes, you can flash a 4.1.1 version after using the 4.2.2.. Make sure you wipe everything before changing the rom!

regullary ? nothing special to do ?

Nothing special to do!
Flash boot.img, erase cache. Go to recovery wipe data/cache/dalvic and then flash rom.zip. Reboot!

[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!

[Solved] D2LTE builds Stuck on Boot

Is anyone having an issue with the new D2LTE builds that have been built recently?
I have tried to flash a few (carbon and c-rom) and just get stuck at kernel splash page. I am on the newest TWRP(2.7), the lk3 modem/bootloader and wiped data,cache, dalvik, and reformatted my internal sd card.
If anyone else is experiencing this, what was done to resolve it?
Edit: I have now also tried
1. Restoring to original stock touchwiz 4.1.1
2. Wiping cache from original recovery
3.Rerooting
4.Restoring a backup of 4.3
5.Attempted to update to C-Rom, Carbonrom, Resurrection Remix -- No Luck Fails

Corvetrims77 said:
Is anyone having an issue with the new D2LTE builds that have been built recently?
I have tried to flash a few (carbon and c-rom) and just get stuck at kernel splash page. I am on the newest TWRP(2.7), the lk3 modem/bootloader and wiped data,cache, dalvik, and reformatted my internal sd card.
If anyone else is experiencing this, what was done to resolve it?
Click to expand...
Click to collapse
I'd like to know myself. I'm stuck too. I can flash a 4.3 rom and everything works, but when I reboot, it gets stuck. All was fine until I flashed Wicked rom and flashed " MJ2 bootloader MJB" Now every time I reboot it gets stuck. Also If I try a reflash, the only way to get it to bootup is to format before flashing.

Try using Philz Touch as your recovery program.

audit13 said:
Try using Philz Touch as your recovery program.
Click to expand...
Click to collapse
I had cwm when I originally started out, switched to twrp to see if the recovery was the issue.

I assume you were running the latest version of cwm before you switched to twrp so it can't be the recovery.
Are you doing a full wipe of the system, cache, data, and Dalvik before installing the ROM?

Yea every time I wiped data, cache, dalvik , I even reformatted once. I have managed to boot up into tasl650AOKP which is a d2lte build but no other ROMs. I mean at this point it looks like I should just wait a bit to see if it is something with the ROMs interacting with my phone(as per all phones are made different)
Sent from my d2lte using Tapatalk

Are you wiping the system before installing? Have you tried wiping system, dalvik, data, cache, install the rom, wipe and re-install the same ROM a second time without trying to boot the ROM in between the 1st and 2nd ROM install?

audit13 said:
Are you wiping the system before installing? Have you tried wiping system, dalvik, data, cache, install the rom, wipe and re-install the same ROM a second time without trying to boot the ROM in between the 1st and 2nd ROM install?
Click to expand...
Click to collapse
Yeah I gave it a shot still no dice. I keep seeing other people having similar issues, so I am still leaning it has to do with the differences in d2lte builds vs dtatt builds
Sent from my d2lte using Tapatalk

d2att ROMs are okay? Just not any d2lte?

audit13 said:
d2att ROMs are okay? Just not any d2lte?
Click to expand...
Click to collapse
As I stated before I am able to boot int Task650AOKP(Which is a d2lte build), any of the others that I have tried have not worked. There are some updates out today, I am going to attempt again and post back results.

As a test, I flashed my i747m back to stock 4.1.2 via Odin. I then installed the latest version of Philz Touch for the d2lte and installed the d2lte version of Validus. Validus booted without any problems.
Edit: just tried the lastest nightly Pac-Rom and Resurrection ROM. Both ROMs had no problem booting to the desktop.

audit13 said:
As a test, I flashed my i747m back to stock 4.1.2 via Odin. I then installed the latest version of Philz Touch for the d2lte and installed the d2lte version of Validus. Validus booted without any problems.
Edit: just tried the lastest nightly Pac-Rom and Resurrection ROM. Both ROMs had no problem booting to the desktop.
Click to expand...
Click to collapse
Thanks for the help, I actually was just able to boot into C-Rom by following the same steps except I am using TWRP. No idea really what caused the Roms to get stuck on boot. Quite annoying.

I had TWRP on my phone but I was having problems installing ROMs when I first got the phone in January.As soon as I switched to CWM or Philz, no problems at all except for ROMs based on a stock 4.3 ROM.