What's the best recovery for i9505 for fastest roms performance? Slow performance has the TWRP recovery.. I'm with Clockworkmod now, but it is the fastest one? I want performance on my S4...
Sent from my GT-I9505 using Tapatalk
velizarcho123 said:
What's the best recovery for i9505 for fastest roms performance? Slow performance has the TWRP recovery.. I'm with Clockworkmod now, but it is the fastest one? I want performance on my S4...
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
Your recovery has no bearing on the performance of the ROM or your device.
Sent from my SPH-L720 using Tapatalk
mattzeller said:
Your recovery has no bearing on the performance of the ROM or your device.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
Nope. I tried TWRP and all roms have slow performance. This ia because TWRP formats the phone with slow filesystem. Clockwork formats with a better fs and all roms works more fast than an one installed by TWRP.. can I use official CM recovery to install CM10.1? I tried CM11 recovery but it can't install CM under version 11.. when I try to flash cm10.1 it says "assert failed" ...
Sent from my GT-I9301I using Tapatalk
velizarcho123 said:
Nope. I tried TWRP and all roms have slow performance. This ia because TWRP formats the phone with slow filesystem. Clockwork formats with a better fs and all roms works more fast than an one installed by TWRP.. can I use official CM recovery to install CM10.1? I tried CM11 recovery but it can't install CM under version 11.. when I try to flash cm10.1 it says "assert failed" ...
Sent from my GT-I9301I using Tapatalk
Click to expand...
Click to collapse
What file system do you think TWRP formats it in that is slow that CWM accomplishes?
Sent from my SCH-R220
It says "Formatting data using make_ext2fs function" , I dont't know, maybe ext2. CWM says only "wiping data", I don't know what fs formats in, but the performance in any rom is more fast than rom flashed via TWRP. I don't know, I'm now with cwm 6 and CM10.1, works good now..
Sent from my GT-I9505 using Tapatalk
velizarcho123 said:
It says "Formatting data using make_ext2fs function" , I dont't know, maybe ext2. CWM says only "wiping data", I don't know what fs formats in, but the performance in any rom is more fast than rom flashed via TWRP. I don't know, I'm now with cwm 6 and CM10.1, works good now..
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
By default they both format with the same file system. I have used both recoveries flashing the same ROMs and there has been 0 difference in ROM performance, including f2fs. Tried on Stock and CM based Lollipop ROMs as well as multiple Marshmallow ROMs.
Sent from my SCH-R220
velizarcho123 said:
It says "Formatting data using make_ext2fs function" , I dont't know, maybe ext2. CWM says only "wiping data", I don't know what fs formats in, but the performance in any rom is more fast than rom flashed via TWRP. I don't know, I'm now with cwm 6 and CM10.1, works good now..
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
wait, make_ext2fs?
Have you updated your TWRP recovery in a while? I did a fresh install of TWRP (3.0.2) on a SGS4 last night, and it used make_ext4fs.
Most modern versions of Android use either ext4 or f2fs, so that could be your problem.
It could also just as easily be a mistake in the installation scripts in the rom itself, have you looked through the comments on the specific rom you're trying to install for anyone else having this issue?
Recoveries have no effect on the ROM's performance. The recovery is just a way of installing the ROM.
acrumpet said:
wait, make_ext2fs?
Have you updated your TWRP recovery in a while? I did a fresh install of TWRP (3.0.2) on a SGS4 last night, and it used make_ext4fs.
Most modern versions of Android use either ext4 or f2fs, so that could be your problem.
It could also just as easily be a mistake in the installation scripts in the rom itself, have you looked through the comments on the specific rom you're trying to install for anyone else having this issue?
Click to expand...
Click to collapse
I had S4, it's now a past. I have S3 Neo with CM11 and CWM recovery. It works like a charm, no lag and glitch. My second device is Galaxy J5 2016 with Marshmallow 6.0.1. Let's rock!!!
Related
hi to all. is anyone having issus with latest DLL7?
what i mean is that i made a clean install of LL7. after rooting with autoroot i installed TWRP 2.3.2.3 cause latest gave me only black screen.
but if i want to update from 2.3.2.3 to 2.3.3.1 it does never boot to recovery bur instead it gives broken Samsung n7100 screen.
it is the same if installing any CWM recovery. so Sammy has made some really weird changes with this update.
any other info. maybe bootloader downgrade just as in S3 thread. Advices
This is a little bit like my problems but I have random reboots instead. They occur almost immediately on a clean XLL7 install flashed from Odin without any root or apps installed.
Everything works perfectly in 4.1.1.
sorry to hear that. but this is nothing like that. to me this looks pretty serious. it seems like plus in security from Sammy.
as for you you can try re-install the stock rom for your phone using Kies.
all you have to do is open kies go to tools- and sellect the 2 or 3 option with your phone not connected.
write GT-N7100 and right after the serial number from your phone, follow instructins on screen.
bear in mind. this will wipe your phone.
mariosraptor said:
sorry to hear that. but this is nothing like that. to me this looks pretty serious. it seems like plus in security from Sammy.
as for you you can try re-install the stock rom for your phone using Kies.
all you have to do is open kies go to tools- and sellect the 2 or 3 option with your phone not connected.
write GT-N7100 and right after the serial number from your phone, follow instructins on screen.
bear in mind. this will wipe your phone.
Click to expand...
Click to collapse
I will try that and see what will happen.
Do not flash any recovery !!!!!!!!
They updated the bootloader so it is very dangers to flash untested mods and stuff.
Sent from my GT-N7100 using xda app-developers app
UtkarshGupta said:
Do not flash any recovery !!!!!!!!
They updated the bootloader so it is very dangers to flash untested mods and stuff.
Click to expand...
Click to collapse
I've flash the last ARHD rom 8.o which have last dll7 firmware and after note2core kernel 2.21 and all works fine. Now I won't install anything else until it's proved working on dll7.
JCVD_ said:
I've flash the last ARHD rom 8.o which have last dll7 firmware and after note2core kernel 2.21 and all works fine. Now I won't install anything else until it's proved working on dll7.
Click to expand...
Click to collapse
do not worry. he means with stock rom.
in ARHD and other custom roms bootloader is left ou of flash.
anyway. i think that sammy has changed the some partitions. twrp works but only 2.3.2.3
No the roms who are based on dll7 are safe.
The recovery imao needs to be updated.
Sent from my GT-N7100 using xda app-developers app
Do you mean that it is dangerous to flash the CWM recovery to the device when it runs XXDLL7?
I flashed the root and CWM package after flashing XXDLL7 and it seems to work (my random reboot problem is unrelated I guess since it happened even with just stock recovery in place).
Now, I have the new bootloader and radio and flashed BatteryPlus 0.2 from CWM without any problems. I flashed the CWM-root-package through Odin after flashing XXDLL7, also from Odin.
So the question is: is there a problem with CWM and other custom recoveries and the XXDLL7?
Or are we talking about flashing mods?
No it can be an issue. It's not recommended at this stage.
Sent from my GT-N7100 using xda app-developers app
If there is a problem with CWM and XXDLL7, that could perhaps explain my reboot problem in that case.
If so, I will hold off for a while and stay on my current configuration.
I have the new bootloader and radio already.
i have noticed that 4.1.2 isnt so friendly with custom recovery. I had cwm recovery and going into it, took a lot of time with 4.1.2 firmware. Maybe samsung is trying to make some higher security in 4.1.2 against custom recoveries and etc.
If they wanted they could have made it absolutely protected. No I don't think they actually wanted to increase security.
I just think the new bootloader isn't friendly with the old recovery.
Sent from my GT-N7100 using xda app-developers app
I've been searching for the stock kernal for at&t users for s bit now, can't find it I'm trying to fix the annoying "updating camera firmware,please wait..." message. Unless there's a better way, I'll just assume you have to flash the sock kernal to update it. But if you flash the sock Kernal, wouldn't the phone fail on boot?
Sent from my GT-I9505 using xda app-developers app
bubblebuddyi said:
I've been searching for the stock kernal for at&t users for s bit now, can't find it I'm trying to fix the annoying "updating camera firmware,please wait..." message. Unless there's a better way, I'll just assume you have to flash the sock kernal to update it. But if you flash the sock Kernal, wouldn't the phone fail on boot?
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
What ROM are you running? Omega?
Sent from my GT-I9505 using xda app-developers app
rcklss1 said:
What ROM are you running? Omega?
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
No, I'm running Wanamlite v1.0.
I just reinstalled the stock AT&T rom to allow the camera to update, but when I ran the camera, no update appeared. So I figured it was all set. After re-rooting, I re-installed Wanamlite and KT kernal, open up the camera, and sure enough the message re-appears. I didn't perform any wipes. But it looks like I'll have to because all the AT&T bloatware was re-installed again.
bubblebuddyi said:
No, I'm running Wanamlite v1.0.
I just reinstalled the stock AT&T rom to allow the camera to update, but when I ran the camera, no update appeared. So I figured it was all set. After re-rooting, I re-installed Wanamlite and KT kernal, open up the camera, and sure enough the message re-appears. I didn't perform any wipes. But it looks like I'll have to because all the AT&T bloatware was re-installed again.
Click to expand...
Click to collapse
Your mistake was reinstalling Wanamlite again. Here's how you install non AT&T ROMs
1. Root your phone. I used the one click TWRP and Loki method.
2. Factory Reset and install custom ROM.
3. Install AT&T kernel. Let it boot up. Open Camera.
4. Reboot to recovery. Install custom kernel. Wipe cache and Dalvik. Fix Permissions.
5. Reboot. All done.
Sent from my Galaxy S4
Baldilocks said:
Your mistake was reinstalling Wanamlite again. Here's how you install non AT&T ROMs
1. Root your phone. I used the one click TWRP and Loki method.
2. Factory Reset and install custom ROM.
3. Install AT&T kernel. Let it boot up. Open Camera.
4. Reboot to recovery. Install custom kernel. Wipe cache and Dalvik. Fix Permissions.
5. Reboot. All done.
Sent from my Galaxy S4
Click to expand...
Click to collapse
Thanks, you're right about my mistake lol I ended up just installing someone else's ROM and it works perfectly. I'm a bit lost reading your instructions, It was my understanding that custom ROM's would not load with stock kernel?
bubblebuddyi said:
Thanks, you're right about my mistake lol I ended up just installing someone else's ROM and it works perfectly. I'm a bit lost reading your instructions, It was my understanding that custom ROM's would not load with stock kernel?
Click to expand...
Click to collapse
You need a carrier kernel for your custom ROM.
Sent from my Galaxy S4
Baldilocks said:
You need a carrier kernel for your custom ROM.
Sent from my Galaxy S4
Click to expand...
Click to collapse
can you link to a stock kernel for the AT&T i337?
xxhorseriderxxx said:
can you link to a stock kernel for the AT&T i337?
Click to expand...
Click to collapse
Exactly, its nice he can recommend installing a stock kernel, but they are not to be found. I asked in another thread and didn't get an answer. I somehow got it to work just wiping and installing Omega 5.0 Then to get wifi to work I installed ktoonez kernel.
Sent from my GT-I9505 converted SGH-I337
highaltitude said:
Exactly, its nice he can recommend installing a stock kernel, but they are not to be found. I asked in another thread and didn't get an answer. I somehow got it to work just wiping and installing Omega 5.0 Then to get wifi to work I installed ktoonez kernel.
Sent from my GT-I9505 converted SGH-I337
Click to expand...
Click to collapse
okay, assuming you're using the AT&T variant, I did this:
I got the looping "installing camera firmware" and tried faux an ktoonsez with no luck
I flashed this tmobile stock kernel and the camera firmware updated successfully by going into the camera app.
I then just flashed faux kernel back and everything worked great.
http://forum.xda-developers.com/showthread.php?t=2271976
I use shabbypenguin's auto loki CWM recovery, but you'll have to definitely flash the loki patch after the tmo kernel to make this work.
http://forum.xda-developers.com/showthread.php?t=2291956
I flashed a Kit Kat rom, and before I was having problems with recovery. Now I'm having problems flashing a new ROM. Every time I try to flash a different rom, it says it flashes but it just goes back to the 4.4 rom I flashed first. I can restore a backup just fine, but even from the backup it does the same thing.
Sent from my Nexus 4 using xda app-developers app
EggosEvo said:
I flashed a Kit Kat rom, and before I was having problems with recovery. Now I'm having problems flashing a new ROM. Every time I try to flash a different rom, it says it flashes but it just goes back to the 4.4 rom I flashed first. I can restore a backup just fine, but even from the backup it does the same thing.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
My MAC address keeps changing after reboot, and wifi is screwy no matter what I do. Full Wipe, factory reset, Factory image restore. Its seems the 4.4 roms change things that cant be undone. I now have to have my phone replaced.
Gah. I'd rather not have to have my phone replaced. I feel as if its just 4.4 ROMs though.
Sent from my Nexus 4 using Tapatalk
Bump. I need this fixed.
Sent from my Nexus 4 using xda app-developers app
EggosEvo said:
Bump. I need this fixed.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Try reflasing your recovery. If that doesn't work, then flash the 4.3 factory images.
EggosEvo said:
Bump. I need this fixed.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I had 4.4 ported from n5, and then i flashed a 4.3 custom rom and didn't have any problems...
What custom recovery are u using ?
sergiu9my said:
I had 4.4 ported from n5, and then i flashed a 4.3 custom rom and didn't have any problems...
What custom recovery are u using ?
Click to expand...
Click to collapse
I'm on the latest CWM touch, I believe 6.0.4.3. I haven't actually tried going from the 4.4 rom to a 4.3, but I know I can't go from 4.4 to a different 4.4 rom, or from 4.3 rom to a different 4.4 rom, it just goes to the first one I flashed.
EggosEvo said:
I'm on the latest CWM touch, I believe 6.0.4.3. I haven't actually tried going from the 4.4 rom to a 4.3, but I know I can't go from 4.4 to a different 4.4 rom, or from 4.3 rom to a different 4.4 rom, it just goes to the first one I flashed.
Click to expand...
Click to collapse
Try using the latest twrp.
sergiu9my said:
Try using the latest twrp.
Click to expand...
Click to collapse
Haven't there been people having issues flashing 4.4 with TWRP? Or has Team Win updated it since then?
EggosEvo said:
Haven't there been people having issues flashing 4.4 with TWRP? Or has Team Win updated it since then?
Click to expand...
Click to collapse
Yes it's updated.
http://forum.xda-developers.com/showthread.php?t=2002326
sergiu9my said:
Yes it's updated.
http://forum.xda-developers.com/showthread.php?t=2002326
Click to expand...
Click to collapse
GooManager is telling me that there is no recovery available for my device. That's odd.
If all else fails, download the stock 4.3 image and fastboot flash it, then try whatever other ROM you wanted.
EggosEvo said:
GooManager is telling me that there is no recovery available for my device. That's odd.
Click to expand...
Click to collapse
Here is the flashable zip: https://www.dropbox.com/s/n8li9hq74weq8t6/TWRP-2.6.3.2-mako_flashable.zip
Flash it in recovery and then twrp will be ure default recovery.
Then try to flash a 4.3 rom.
sergiu9my said:
Here is the flashable zip: https://www.dropbox.com/s/n8li9hq74weq8t6/TWRP-2.6.3.2-mako_flashable.zip
Flash it in recovery and then twrp will be ure default recovery.
Then try to flash a 4.3 rom.
Click to expand...
Click to collapse
Successfully flashed PAC with TWRP. Tested PA 4.4, and still flashed the first 4.4 rom i flashed.
EggosEvo said:
Successfully flashed PAC with TWRP. Tested PA 4.4, and still flashed the first 4.4 rom i flashed.
Click to expand...
Click to collapse
Try doing what I suggested if you're still having the revert to original 4.4 issue.
orangekid said:
Try doing what I suggested if you're still having the revert to original 4.4 issue.
Click to expand...
Click to collapse
I won't have access to a computer with ADB until late tonight. But I'll try that and report back either tonight or tomorrow.
Sent from my Nexus 4 using xda app-developers app
EggosEvo said:
I won't have access to a computer with ADB until late tonight. But I'll try that and report back either tonight or tomorrow.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
The only other thing you might try now is flashing any 4.3 or 4.2.2 ROM, reboot, and see if it's now on that one or still on 4.4...
Or is that what you already did with PAC?
You can also manually format /system then /data from TWRP or CWM then manually flash your new ROM.
orangekid said:
The only other thing you might try now is flashing any 4.3 or 4.2.2 ROM, reboot, and see if it's now on that one or still on 4.4...
Or is that what you already did with PAC?
You can also manually format /system then /data from TWRP or CWM then manually flash your new ROM.
Click to expand...
Click to collapse
That's what I did. I went from 4.4 to PAC, and it booted into PAC. Same with CM 10.2. It seems to just be happening with 4.4 roms.
EggosEvo said:
That's what I did. I went from 4.4 to PAC, and it booted into PAC. Same with CM 10.2. It seems to just be happening with 4.4 roms.
Click to expand...
Click to collapse
just manual format /system /data and /boot is the only thing I can think of besides what I've already mentioned.
weird issue...
orangekid said:
just manual format /system /data and /boot is the only thing I can think of besides what I've already mentioned.
weird issue...
Click to expand...
Click to collapse
I just wiped /system and /data, and now the 4.4 PA fails to flash, but CM 10.2 flashed. I'm gonna switch to CWM to see if it'll flash there.
UPDATE: CWM would NOT let me go back to the previous option when asking me to reflash recovery when booting, and it didn't flash PA, so now I'm stuck on the first 4.4 build with no GApps until 9 or 10 tonight. First thing I'm doing when I get home is flashing the factory image.
So i just bought my Lg G2 a few days ago, i instantely rooted it and installed Vanir, things have been great minus a few small bugs...but being i am a crack flasher i tried a few other roms such as Omni, Beanstalk and more but when i try these other roms i have no issues except that they always boot themselves on when you charge them..you can turn the rom off, plug it in and surely enough it automatically boots itself up, i've tried plugging it in then turning it off and the results are the same. the only rom that will charge while off and remain off is Vanir but i have experienced a few small bugs on then
ANYWAY the main resaon I started this thread is because every and any kernel i try to flash doesnt flash, they all fail...can anyone shed some light as to why all the kenels are failing on me?
Which kernels are you flashing? Which variant are they for? Erich variant do you have?
Sent from my LG-D800 using Tapatalk
If you are using TWRP, flash Philz touch recovery (see android original development). It may be a recovery issue.
Sent from my LG-D802 using XDA Premium 4 mobile app
tdevaughn said:
Which kernels are you flashing? Which variant are they for? Erich variant do you have?
Sent from my LG-D800 using Tapatalk
Click to expand...
Click to collapse
The Kernels in the Lg G2 Verizon section and a couple other, the names escape me at the moment but they are for the vzw G2 which is what I have/
Life Engineer said:
If you are using TWRP, flash Philz touch recovery (see android original development). It may be a recovery issue.
Sent from my LG-D802 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i was on the latest twrp and tried flashing and it didnt work, i now am on philz touch cwm recover and i still get the fail.
there is also one rom that fails to flash to which is odd because a mass of people swear they flash it no issue
Deleted
Sent from my LG-D800 using Tapatalk
Bump
Does anyone have any idea why I can flash majority of the roms available but I cannot flash one single custom kernel?
I've tried the latest TWRP. an earlier version and i've tried Philz touch...none of which will allow me to flash any of these custom kernels available for my VS980....and yes the kernels are meant for said device. There is also maybe one or two roms that won't flash either
sorry to bump this again but i still cannot get any kernels to flash
I am certainly rooted as i have flashed multiple roms but are there any other steps or processes i need to do in order to flash a kernel on this phone? i've owned about 9 android phones and every time i've rooted and unlocked the bootloader, installed a custom recovery i was able to flash roms and kernels with ease...as i've mentioned i've tried different versions of recoveries and everythng and no mattter what every kernel i try to flash fails...its not the end of the world but i would really like to try some of these custom kernels out and dunno how to do it...
am i missing something?
Hi,
Yesterday I went to flash CyanogenMod 11 on my Galaxy s4 (GT19505) and it wouldn't work. The first time, it started then went to a black screen. I turned my phone back on to find it wouldn't boot up at all (I waited over 10 minutes for it). I can access recovery mode, and when I did it again, it said md5 couldn't be found.
I used Odin to flash the most recent CT auto root and then moved over TWRP (with Odin) and I had no trouble with these.
I accidentally moved TWRP 2.5 over instead of 2.7. I was running 4.4 KitKat on my phone. Could it be 2.7 isn't compatible with CM 11?
Help!?
It should just work.
Flash the latest TWRP or Philz.
Perform a full wipe.
Flash Cyanogenmod.
What version are you trying to flash from Cyanogenmod? Use the nightlys and if one doesn't work try the version before that one.
ps you can skip the step nexttime about flashing cf-auto root. You don't have to do this. You can just flash the recovery you want.
3593483
Lennyz1988 said:
It should just work.
Flash the latest TWRP or Philz.
Perform a full wipe.
Flash Cyanogenmod.
What version are you trying to flash from Cyanogenmod? Use the nightlys and if one doesn't work try the version before that one.
ps you can skip the step nexttime about flashing cf-auto root. You don't have to do this. You can just flash the recovery you want.
Click to expand...
Click to collapse
I'm using a stable version. I haven't downloaded any latest ones. How would i do that if I can't access the phone? Boot it to download then go from there?
are you sure you (even) flashed a (compatible) kernel?
Sent from my GT-I9505 using XDA Premium 4 mobile app on OmegaRom v19
Is there any difference between 19500 and 19505? I'll try a new CM download...knowing my uncertainty I probably got an incompatible rom.
How stable are the nightlies?
Manganese said:
Is there any difference between 19500 and 19505? I'll try a new CM download...knowing my uncertainty I probably got an incompatible rom.
How stable are the nightlies?
Click to expand...
Click to collapse
You should only flash a rom for YOUR model phone, and for me the nightlies were stable enough to use.
dwarfer66 said:
You should only flash a rom for YOUR model phone, and for me the nightlies were stable enough to use.
Click to expand...
Click to collapse
So I redid TWRP, now what about CM 11? TWRP uses the jfltexx in its name...do I just use Odin to move CM?
So, I installed TWRP 2.7 and it worked. All is good, currently enjoying CM!!!
Now the battery is saying it's at 0%...how do I fix that?
Now my password isn't working for some reason. I did a restore with TWRP and now I can get into my phone. Fix?
Now my password isn't working for some reason. I did a restore with TWRP and now I can get into my phone. Fix?
Did you wipe before restoring?
Lennyz1988 said:
Did you wipe before restoring?
Click to expand...
Click to collapse
No. I just tried it and the same problem occurred. It's no biggie, I can reformat the settings myself. Thanks for the help.
dude, google it
Sent from my GT-I9505 using XDA Premium 4 mobile app