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
Related
i tried to install any rom and when wiping or installing this comes up on twrp
E: error opening /data/lost+found
i flashed stock rom via odin and wiped internal data.
still says error and never boots when flashing custom roms.
any help?
i have tried multiple roms both tw and cm. still wont boot.
bstylz911 said:
i tried to install any rom and when wiping or installing this comes up on twrp
E: error opening /data/lost+found
i flashed stock rom via odin and wiped internal data.
still says error and never boots when flashing custom roms.
any help?
i have tried multiple roms both tw and cm. still wont boot.
Click to expand...
Click to collapse
I suggest you try one of these options:
- Do a complete wipe, system, data, cache, davlik,....everything but sd card of course. Make sure the backup is on ext sd card
- Change customer recovery from TWRP to CWM. Go get the latest on the CWM site and use odin to flash it
- give this method a shot : http://forum.xda-developers.com/showpost.php?p=39497772&postcount=3
- fun fsck fix from the toolbox listed in the sticky thread in dev
Does this happen on stock based rom's or just when going from stock to custom?
It happens in both stock and custom.
I tried that method but still happens.
I even my wiped my whole phone and unroofed and flashed stock. But still error when trying to flash a different rom
Sent from my SGH-T999 using xda app-developers app
bstylz911 said:
i tried to install any rom and when wiping or installing this comes up on twrp
E: error opening /data/lost+found
i flashed stock rom via odin and wiped internal data.
still says error and never boots when flashing custom roms.
any help?
i have tried multiple roms both tw and cm. still wont boot.
Click to expand...
Click to collapse
Go into the folder specified and create the folder it's looking for lost+found
Had this issue once. Once I did that and rebooted into recovery everything worked fine.
Sent from my SGH-I747 using xda app-developers app
I had that issue with TWRP when wiping not flashing and i went over to CWM and it works perfectly.
Will try this later tonight.
Sent from my SGH-T999 using xda app-developers app
i tried to install any rom and when wiping or installing this comes up on twrp
E: error opening /data/lost+found
i flashed stock rom via odin and wiped internal data.
still says error and never boots when flashing custom roms.
any help?
i have tried multiple roms both tw and cm. still wont boot.
I was on a cm ROM and I tried flashing a tw ROM when this started to happen.
Help please
Sent from my SGH-T999 using xda app-developers app
I would reflash the recovery. Are you on the current TWRP?
Sent from my Wicked T999
Go back into recovery and wipe Cache and Dalvik, then fix permissions. it should boot. The Lost+Found folder can't be found because you deleted it when you flashed with ODIN. Not really needed for what you are trying to do anyways.
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 am have been trying to flash a new custom rom on my Note II. I have tried to flash Dirty Unicorns new build w/ TWRP and keep getting "fail" message. I also tried flashing CyanogenMod rom using RomManager and TWRP and its stuck on the boot image and the rom never loads. Any suggestions??
jha84 said:
I am have been trying to flash a new custom rom on my Note II. I have tried to flash Dirty Unicorns new build w/ TWRP and keep getting "fail" message. I also tried flashing CyanogenMod rom using RomManager and TWRP and its stuck on the boot image and the rom never loads. Any suggestions??
Click to expand...
Click to collapse
Dump twrp and use philz recovery. Also make sure you wipe everything. If you use philz choose factory reset option the wipe for new ROM option. Also on main menu choose mounts then wipe data data/media. This will wipe your internal sd card so make sure you back it up first.
Sent from my SPH-L900 using XDA Premium 4 mobile app
jlmancuso said:
Dump twrp and use philz recovery. Also make sure you wipe everything. If you use philz choose factory reset option the wipe for new ROM option. Also on main menu choose mounts then wipe data data/media. This will wipe your internal sd card so make sure you back it up first.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
thanks! but how do i dump TWRP? I tried flashing CWM custom recovery but for some reason TWRP still overrides it when I go into recovery mode.
jha84 said:
thanks! but how do i dump TWRP? I tried flashing CWM custom recovery but for some reason TWRP still overrides it when I go into recovery mode.
Click to expand...
Click to collapse
Edit: Philz recovery worked. Flashed rom w/o any issues. Thanks!
No problem. Enjoy.
Sent from my SPH-L900 using XDA Premium 4 mobile app
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.