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.
Related
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!
Hello,
I have a unique issue. I'm having a problem installing any custom rom on my t999 (tmobile). I have been using a custom rom for over a year. Always used TWRP. Started with Paranoid Android and for the last few months I've been using PAC-Man (nightly) roms. I was having gps lock issues, I decided to upgrade the modem to a leaked UVUEMJC, this fixed the gps lock issue. But after the reboot, I was stuck on bootloader screen. The only way I could get the rom to work was to backup the rom, flash the system and data, and after that, the rom would work until reboot. I did this a few times until it stopped working. My efs was corrupted, IMEI missing, To recover it, I went into download mode, and noticed in red Warranty bit =1. I used odin to flashed a rooted cf 4.3 samsung touchwiz rom (root66_TMO_T999UVUEMJC). All imei/efs issues were fixed. I decided to try installing a custom rom again, PAC-Man rom, it installed just fine, all EFS/IMEI info was intact, but at reboot, I got stuck on the CM bootlogo. This happens everytime. IF I recover a backup, it gets stuck on the boot logo. I'm using TWRP v2.6.3.
Anybody have any suggestions on how to fix this issue?
Thanks!
Install TWRP 2.6.3.1. Then take a Nandroid.
Next wipe /Data. Then flash your Custom Rom. Wipe Dalvik + Cache after the Flash. Reboot and report.
Perseus71 said:
Install TWRP 2.6.3.1. Then take a Nandroid.
Next wipe /Data. Then flash your Custom Rom. Wipe Dalvik + Cache after the Flash. Reboot and report.
Click to expand...
Click to collapse
Thanks for the reply Perseus71. I'll give it a shot!
acedik said:
Thanks for the reply Perseus71. I'll give it a shot!
Click to expand...
Click to collapse
Upgrading to the newest TWRP did the trick! Everything is working fine now. :good:
Thanks for the help!
I'm also having trouble flashing PAC-man.
SGH-T999LUVUBMK4
Factory reset everything, wiped SD card.
Tried latest TWRP and CWM.
Suggestions?
D
Donny Orbit said:
I'm also having trouble flashing PAC-man.
SGH-T999LUVUBMK4
Factory reset everything, wiped SD card.
Tried latest TWRP and CWM.
Suggestions?
D
Click to expand...
Click to collapse
You need to post info about the error
Sent from my SGH-M919 using Tapatalk
It says
E: Error executing updater binary in zip '/external
Error flashing zip '/external_sd/pac_d2tmo-night
I tried flashing the Rom that doc fixed specifically for the T999LTE for the CM10.1.2 also with no avail.
Same problem.
D
wipe Dalvik and Cache before trying the rom again. If
I'm currently using the stock 4.1.2 rom from Sprint, have TWRP 2.6.3 installed and the phone rooted. Every 4.4.2 rom I've tried to install fails and I have to restore my TWRP recovery.
I've tried CM 11, AOKP, Pac-Man and a few others. I've been copying the rom and recommended GAPPS to the internal storage, rebooting to TWRP/recovery, doing a factory wipe then 'Installing' the new rom. Most fail almost immediately, I'm really not sure what I'm doing wrong.
omnipotentclown said:
I'm currently using the stock 4.1.2 rom from Sprint, have TWRP 2.6.3 installed and the phone rooted. Every 4.4.2 rom I've tried to install fails and I have to restore my TWRP recovery.
I've tried CM 11, AOKP, Pac-Man and a few others. I've been copying the rom and recommended GAPPS to the internal storage, rebooting to TWRP/recovery, doing a factory wipe then 'Installing' the new rom. Most fail almost immediately, I'm really not sure what I'm doing wrong.
Click to expand...
Click to collapse
Make sure the TWRP you're using is for KK. You'll find them in the TWRP thread or the root guide.
Sent from my LG-LS970 using XDA Premium 4 mobile app
I have now tried both CM11 and Slimkat 4.4, both ROMs, after flashing leave the device with no audio output at all. No ringtone, music, headphone output, call audio, nothing. Device is ATT S3 i747. Flashed back to stock JB 4.3 and audio issue is fixed every time. I really would like to run a custom ROM on my phone, but this issue makes it impossible. Does anyone know what could be causing the issue. Does it sound like a kernel or bootloader issue?
Try this:
1) wipe cache, Dalvik, data, and system before installing the ROM;
2) install ROM and, before rebooting, wipe cache and Dalvik again;
3) boot into the rom.
audit13 said:
Try this:
1) wipe cache, Dalvik, data, and system before installing the ROM;
2) install ROM and, before rebooting, wipe cache and Dalvik again;
3) boot into the rom.
Click to expand...
Click to collapse
Definitely followed that process to a T just now. Still no audio on anything. grrr.
MeatyFingers said:
Definitely followed that process to a T just now. Still no audio on anything. grrr.
Click to expand...
Click to collapse
Just to be certain, what is your recovery. I would recommend twrp 2.7.0.0. Maybe you have an old recovery that's messing with flashing ROMs. Idk just a guess.
UnXKnown0 said:
Just to be certain, what is your recovery. I would recommend twrp 2.7.0.0. Maybe you have an old recovery that's messing with flashing ROMs. Idk just a guess.
Click to expand...
Click to collapse
I am running Clockworkmod 6.0.4.7 touch version which I found on the clockworkmod website under ATT s3
MeatyFingers said:
I am running Clockworkmod 6.0.4.7 touch version which I found on the clockworkmod website under ATT s3
Click to expand...
Click to collapse
Try flashing Validus 13's ROM. I have that on my s3 and it works fine.
try this out !!
Personally i find philz touch recovry the best when it comes to flashing kitkar roms.. It might be wierd but basically i flashed the recovery from 'smart phone revolution-aroma bloat installer'
http://forum.xda-developers.com/galaxy-s3/development/rom-smart-phone-revolution-rom-v7-0-t2541054
I then use the option of "yes I'm flashing a new rom" in factory reset..
Try it out !!
Hope it helps..
Hi, I'm on the 4.4.2 version of the Sickness, with the MDL bootloader. I've updated the modem to NH7.
Do I need to go through the whole process of updating the firmware, re-rooting, etc., or can I just do a full wipe and update to the Sickness' 4.4.4 V3?
I tried a full wipe and installing it today, but I ran into bootloops/other failures.
its better to use the latest recovery like twrp becuz in twrp 2.8.0.1 which is the latest recovery you can choose wipe and then advance wipe and choose dalvik cache,system,data and cache then wipe and that normally takes care of the boot loops
rblckmnjr84 said:
its better to use the latest recovery like twrp becuz in twrp 2.8.0.1 which is the latest recovery you can choose wipe and then advance wipe and choose dalvik cache,system,data and cache then wipe and that normally takes care of the boot loops
Click to expand...
Click to collapse
CWM and Philz also allow you to wipe system, data, cache, and even the non-existent Dalvik cache partition.... Your post makes it sound like TWRP is the only recovery that does that Just saying..
jonnyboy2040 said:
Hi, I'm on the 4.4.2 version of the Sickness, with the MDL bootloader. I've updated the modem to NH7.
Do I need to go through the whole process of updating the firmware, re-rooting, etc., or can I just do a full wipe and update to the Sickness' 4.4.4 V3?
I tried a full wipe and installing it today, but I ran into bootloops/other failures.
Click to expand...
Click to collapse
As to your question; you should be able to do a full wipe (system/data/cache and even though it literally does nothing because the partition doesn't exist, dalvik) and then flash with no problems. I would say that since you're still one of us few lucky ones still with MDL bootloaders, try to keep an official update as a very last option!
Were you trying to flash a kernel or any other mods along with the ROM? If so, flash only the ROM itself and see how it works.
You say bootloops/other failures... that means you bootloop a lot, and when you don't bootloop something else happens. Could you be more specific on the "other failures?" Any error messages? Were you able to pull a logcat? Did you compare the MD5's? Doesn't sound like a bad download, but you never know...
i understand what you saying however i ran into the same problem using philz touch and got the latest twrp and havent got stuck in boot loops since i read a forum on this and using older recovery to flash kitkat roms has been having people phones stuck in a boot loop and throwing errors after flashing and they updated the recovery to fix it
Sh*t, I have TWRP 2.6 and never have a problem. IMO (and some others) newer versions don't seem to play well with others. That goes for all Recoveries.
As for your issue, you might have a bad DO. Try re downloading the ROM, full wipe and then flash.
well my phone didn't like philz touch it works better with the latest twrp recovery
I actually ran into this last night with philz.. I tried flashing insane 4.4.4 v3 and got stuck in a bootlooop I couldn't recover from. It flashed v1 just fine, but it just wasn't having any of v3. I had to use Odin to flash the latest TWRP and have had no problems.... :/
lordcheeto03 said:
I actually ran into this last night with philz.. I tried flashing insane 4.4.4 v3 and got stuck in a bootlooop I couldn't recover from. It flashed v1 just fine, but it just wasn't having any of v3. I had to use Odin to flash the latest TWRP and have had no problems.... :/
Click to expand...
Click to collapse
Sickness mentioned something about a script that was causing bootlegs when flashing