I've got a Wifi 2012 Nexus 7 (GROUPER) that I've been playing around with. It is abysmally slow with stock on it, and I've been reading that an F2FS recovery, with an F2FS kernel and an F2FS ROM and F2FS GApps work pretty drokking well, so well that it's like having a new, factory fresh Nexus 7 and it's supposed to run a lot smoother to boot.
That may be hyperbole I've read, though. But between here, Reddit, Droid Life and other sources, I've read enough compelling evidence that doing this on my tablet would be in my best interests.
However I spent a good couple of hours last night trying to flash the M-Kernel with AllF2FS support as well as an AllF2FS ROM, after flashing the FixFilesystem zip, rebooting recovery (TWRP 2.7.0.0 F2FS) which was recommended, and then I flashed ROM THEN GApps THEN Kernel, which I've learned you want to do in that order because ROMs oftentimes have their own embedded kernel. The M-Kernel gives F2FS support, so I went with that.
Well, I tried everything and every order I could, but I cannot get either the ROM or the kernel to flash in TWRP, nor can I get any success with using the N7 Rootkit tool.
I've given it multiple attempts, even tried other kernels and other ROMs but I haven't had any success.
Are there any experts on this who can either pound out a step-by-step or point me in the direction of one that already exists? I searched the forums a bit but I didn't find anything usable that wasn't outdated by several months.
Thanks,
shaddz said:
I've got a Wifi 2012 Nexus 7 (GROUPER) that I've been playing around with. It is abysmally slow with stock on it, and I've been reading that an F2FS recovery, with an F2FS kernel and an F2FS ROM and F2FS GApps work pretty drokking well, so well that it's like having a new, factory fresh Nexus 7 and it's supposed to run a lot smoother to boot.
That may be hyperbole I've read, though. But between here, Reddit, Droid Life and other sources, I've read enough compelling evidence that doing this on my tablet would be in my best interests.
However I spent a good couple of hours last night trying to flash the M-Kernel with AllF2FS support as well as an AllF2FS ROM, after flashing the FixFilesystem zip, rebooting recovery (TWRP 2.7.0.0 F2FS) which was recommended, and then I flashed ROM THEN GApps THEN Kernel, which I've learned you want to do in that order because ROMs oftentimes have their own embedded kernel. The M-Kernel gives F2FS support, so I went with that.
Well, I tried everything and every order I could, but I cannot get either the ROM or the kernel to flash in TWRP, nor can I get any success with using the N7 Rootkit tool.
I've given it multiple attempts, even tried other kernels and other ROMs but I haven't had any success.
Are there any experts on this who can either pound out a step-by-step or point me in the direction of one that already exists? I searched the forums a bit but I didn't find anything usable that wasn't outdated by several months.
Thanks,
Click to expand...
Click to collapse
It should be pretty straightforward.
I would start by upgrading TWRP to the latest, as it has the fixfilesystem stuff built in, so you wont need to do that step.
Download a ROM that has AllF2FS support, and dont worry about the kernel for now, and grab it's associated gapps
reboot to recovery(I am running 2.8.2.0), and under wipe->advanced wipe, there is an option for repair or change filesystem. Highlight System, Cache and Data, and change to F2FS. Run a repair on all 3 after it finishes, just to be safe.
Now you'll need an OTG cable, or micro-USB adapter for a flash drive with your ROM & Gapps - install both like you would normally.
Reboot when finished, and you are done. Easy-Peasy. . . You can go back and flash your kernel if you want
Thanks for that!
I will give it a try later; The tutorials I read before suggested using the 2.7.0.0 F2FS version. I'll try the UTD version.
shaddz said:
Thanks for that!
I will give it a try later; The tutorials I read before suggested using the 2.7.0.0 F2FS version. I'll try the UTD version.
Click to expand...
Click to collapse
If you are flashing a lollipop rom, be sure to be on the latest twrp.
thonl said:
It should be pretty straightforward.
I would start by upgrading TWRP to the latest, as it has the fixfilesystem stuff built in, so you wont need to do that step.
Download a ROM that has AllF2FS support, and dont worry about the kernel for now, and grab it's associated gapps
reboot to recovery(I am running 2.8.2.0), and under wipe->advanced wipe, there is an option for repair or change filesystem. Highlight System, Cache and Data, and change to F2FS. Run a repair on all 3 after it finishes, just to be safe.
Now you'll need an OTG cable, or micro-USB adapter for a flash drive with your ROM & Gapps - install both like you would normally.
Reboot when finished, and you are done. Easy-Peasy. . . You can go back and flash your kernel if you want
Click to expand...
Click to collapse
Hey quick question man, I am finally getting around to this - When I select System, Cache and Data and try to tap Change to F2FS, it says "invalid partition selection" and clears the boxes.
shaddz said:
Hey quick question man, I am finally getting around to this - When I select System, Cache and Data and try to tap Change to F2FS, it says "invalid partition selection" and clears the boxes.
Click to expand...
Click to collapse
Change only one at a time, that worked for me.
thonl said:
It should be pretty straightforward.
I would start by upgrading TWRP to the latest, as it has the fixfilesystem stuff built in, so you wont need to do that step.
Download a ROM that has AllF2FS support, and dont worry about the kernel for now, and grab it's associated gapps
reboot to recovery(I am running 2.8.2.0), and under wipe->advanced wipe, there is an option for repair or change filesystem. Highlight System, Cache and Data, and change to F2FS. Run a repair on all 3 after it finishes, just to be safe.
Now you'll need an OTG cable, or micro-USB adapter for a flash drive with your ROM & Gapps - install both like you would normally.
Reboot when finished, and you are done. Easy-Peasy. . . You can go back and flash your kernel if you want
Click to expand...
Click to collapse
Never mind, apparently you can do it within the recovery via usb -> pc
Related
I've been downloading some custom roms off of the chinese forums, but many of them don't have google apps. If I can't sync my contacts and calender to gmail, I won't use the rom.
I downloaded GAPPS, which is meant to go with Cyanogenmod. I flashed it through recovery, but it didn't work.
I'd really like to use some of these Chinese roms, like V7, but I have to have GAPPS.
When installing any ROM I'm fairly sure you do it in this order:
1. Backup
2. Wipe Data/Factory reset
3. Flash ROM
4. Manually mount /system
5. Flash GAPPS
6. Wipe Dalvik and Batterystats (optional)
7. Reboot
I have done it this way with the CM6 and CM7 ROMS and GAPPS works fine for me.
Yes need to mount /system manually before flashing, probably need to install GAPPS before first boot.
Some devs put the GAPPS for their ROM on the forum also. Like Genokolar. You can look at the ROM post for instructions.
Ok. How do you manually mount the system?
@simplistian: where he posts the gaps? i can only find something called gms! or thats it?
http://bbs.goapk.com/thread-2280290-1-1.html
iakoboss7 said:
@simplistian: where he posts the gaps? i can only find something called gms! or thats it?
http://bbs.goapk.com/thread-2280290-1-1.html
Click to expand...
Click to collapse
Yes it is GMS. Flash it after you flash the ROM before the first boot. No need to mount /system.
typci said:
Ok. How do you manually mount the system?
Click to expand...
Click to collapse
With a custom recovery. There is an option of mounting different partitions.
Simplistian, thanks. You've been a great help. I'm going to stick with the B136 for now, and it runs great, and handles high end games without any problems. Next time I flash, I'll probably go with genokolar's V7 like you recommended.
Hey guys, just a quick question, do I have to wipe userdata when installing a new ROM? Should I install a rom and hope it works? And then suffer the consequences? I'm running stock with Trinity kernel, trying to go to latest cm 10 or whatever it is.
Thanks
-Micro
You can get away with over-flashing (or "dirty flashing") very closely related ROMs.
For instance if you were testing CM nightlies from night to night.
In general though it is not a good idea, and even in the case of closely-related ROMs there really are no guarantees. It is certainly not a good idea for a random pairing of before/after ROMs.
BTW the "wipe" that you want is a wipe of /data that clears everything but /data/media (so the "/sdcard" doesn't get nuked), plus a wipe of /cache. In TWRP this is called "factory reset"; I'm not sure what it is called by CWM (note that in the stock recoveries all of /data gets wiped by the "factory reset", so the term means slightly different things in different contexts)
good luck
Hey thanks a lot. Did not know it would't erase the "sdcard" so I installed cwm cm and trinity kernel. Then reinstalled all my apps with titanium. Okay one more question. How exactly do I install cm and trinity kernel? Here's how I did it. I went into ROM manger, downloaded cm, added gapps and then clicked the add zip and selected trinity kernel.. Is this right? Does it matter what order you go in? How would I get rid of trinity kernel? If I were to get rid of trinity kernel, I would have to install a different kernel right? Cm doesn't come with a kernel since its just a ROM right? Also does the cm 10 come with a boot animation? Since I installed trinity second, I have trinity boot animation..
Thanks again!
-Micro
Whew that's a lot of questions - I'll answer a few but not all. (I don't ever use ROM manager.)
By convention, all dev ROMs come with a boot image (which contains a kernel and ram disk), so if you combine an arbitrary ROM and kernel, the kernel needs to be flashed after the ROM.
If you don't like that kernel and want to revert to the one the comes with the ROM, just dirty-flash the ROM again. (This is an example where dirty-flashing should be completely safe - it's the identical ROM! /system won't change even though it is being flashed... unless you customized the ROM since you installed it. FYI some root-aware apps & even TiBu can do this depending how you use it... so dirty-flashing could bust things in that circumstance).
An even safer method would be to get a nandroid backup of the ROM before you flash the kernel mod. TWRP allows you to the option to restore only individual partitions, and this would allow you to restore only the boot partition. I'm not sure if you have this kind of flexibility in CWM or ROM manager.
Backups give you freedom and confidence. Make sure you are making them, and getting copies of them off the tablet, as it is easy to make a mistake and accidentally wipe all of /data including the pseudo-SD card.
I updated my phone to latest liquidsmooth rom two days ago and the phone freezes and restarts/reboots randomly like sometimes when im on phone/ playing a game/ using browser/ connected to charger. Yesterday I changed rom to latest carbon rom. Did install (3 wipes) as told in the thread but im still having the reboots.
Im using TWRP recovery and had used Utility 1.10 to go back to stock from Energy rom with safestrap recovery.
Can tell me whats the prob? Is it the kernel problem?
Have you tried upgrading or reflashing TWRP and then doing a clean install of Carbon? Its probably worth doing a fresh download of each first just to make sure you cover all your bases. These reboots were happening to me a few months ago and it drove me mad. following these steps fixed it for me.
jcxmej said:
I updated my phone to latest liquidsmooth rom two days ago and the phone freezes and restarts/reboots randomly like sometimes when im on phone/ playing a game/ using browser/ connected to charger. Yesterday I changed rom to latest carbon rom. Did install (3 wipes) as told in the thread but im still having the reboots.
Im using TWRP recovery and had used Utility 1.10 to go back to stock from Energy rom with safestrap recovery.
Can tell me whats the prob? Is it the kernel problem?
Click to expand...
Click to collapse
Honestly, if you're using SafeStrap, that might be your problem. Remove SS and flash the ROM in TWRP. If your bootloader is unlocked, you don't really want to use SS. Also, make a stock backup in TWRP, prior to flashing. This way, it will be easier for you to recover in the future, and you won't need to go through the painful process of fastboot.
RikRong said:
Honestly, if you're using SafeStrap, that might be your problem. Remove SS and flash the ROM in TWRP. If your bootloader is unlocked, you don't really want to use SS. Also, make a stock backup in TWRP, prior to flashing. This way, it will be easier for you to recover in the future, and you won't need to go through the painful process of fastboot.
Click to expand...
Click to collapse
Like I said on first post Im using TWRP now. Previously I was using safestrap. I removed it and installed TRWP. Anyways thanks.
PantherVT said:
Have you tried upgrading or reflashing TWRP and then doing a clean install of Carbon? Its probably worth doing a fresh download of each first just to make sure you cover all your bases. These reboots were happening to me a few months ago and it drove me mad. following these steps fixed it for me.
Click to expand...
Click to collapse
Thanks man. I will upgrade TWRP or reinstall it first. Thanks for that tip. Will post again if it doesnt work.
Still having those restarts. Really irritating. Froze and rebooted 4 5 times today morning while I was on call and trying to message. I reflashed reinstalled everything. I used both Utility 1.10 and 1.20. Im getting reboots even the stock ROM after using the Utility. I am confused which Utility I should be using. I had no issue of rebooting before flashing using Utility. Can someone give me exact procedure to reflash so that i know i am not missing out anything.
jcxmej said:
Still having those restarts. Really irritating. Froze and rebooted 4 5 times today morning while I was on call and trying to message. I reflashed reinstalled everything. I used both Utility 1.10 and 1.20. Im getting reboots even the stock ROM after using the Utility. I am confused which Utility I should be using. I had no issue of rebooting before flashing using Utility. Can someone give me exact procedure to reflash so that i know i am not missing out anything.
Click to expand...
Click to collapse
you might need to do a clean install.
- what version of TWRP are you using (anything other than 2.4 should be fine)?
- to perform the clean install, mount system, then try wiping everything (system, factory reset, & internal storage) - DO NOT WIPE external SD (I presume this is where you store the ROM files
- after wiping, reboot recovery, then install whichever 4.2.2 ROM you want follow by the GApps (use the 3/2013 version)
jco23 said:
you might need to do a clean install.
- what version of TWRP are you using (anything other than 2.4 should be fine)?
- to perform the clean install, mount system, then try wiping everything (system, factory reset, & internal storage) - DO NOT WIPE external SD (I presume this is where you store the ROM files
- after wiping, reboot recovery, then install whichever 4.2.2 ROM you want follow by the GApps (use the 3/2013 version)
Click to expand...
Click to collapse
Since TWRP wasnt working for me, I tried flashing with CWM recovery by hashcode. Still had reboots. I was using TWRP 2.3.2.3
When you say wipe everything, does it include 'modem' and 'pds'? Saw these two options also inside Mount/Format menu of CWM recovery.
Also there was an option 'Mount sdcard' (internal I suppose) but when i click it nothing happens it remains as Mount sdcard. Rest of it changes from Mount to Unmount. Is there some problem with that?
Do I have to just Mount system only? Also after rebooting recovery do I have to mount system again?
I try again as you said meanwhile.
jcxmej said:
Since TWRP wasnt working for me, I tried flashing with CWM recovery by hashcode. Still had reboots. I was using TWRP 2.3.2.3
When you say wipe everything, does it include 'modem' and 'pds'? Saw these two options also inside Mount/Format menu of CWM recovery.
Also there was an option 'Mount sdcard' (internal I suppose) but when i click it nothing happens it remains as Mount sdcard. Rest of it changes from Mount to Unmount. Is there some problem with that?
Do I have to just Mount system only? Also after rebooting recovery do I have to mount system again?
I try again as you said meanwhile.
Click to expand...
Click to collapse
nope, just system/factory reset/internal storage.
yes, make sure everything is mounted (checked) so that they read "unmount"
jco23 said:
nope, just system/factory reset/internal storage.
yes, make sure everything is mounted (checked) so that they read "unmount"
Click to expand...
Click to collapse
Did exactly like said. Got into CWM recovery. Mounted system. Formatted system, data, cache, sdcard. Did factory reset and wiped the caches. Then rebooted recovery. Then installed the ROM, 3/13 gapps, gsm fix. Reboot system. Still no use. I got 2 reboots in 5 mins in the ROM. I checked the md5 of the files and its ok. Dont know what else to try?
jcxmej said:
Did exactly like said. Got into CWM recovery. Mounted system. Formatted system, data, cache, sdcard. Did factory reset and wiped the caches. Then rebooted recovery. Then installed the ROM, 3/13 gapps, gsm fix. Reboot system. Still no use. I got 2 reboots in 5 mins in the ROM. I checked the md5 of the files and its ok. Dont know what else to try?
Click to expand...
Click to collapse
which ROM are you trying to install?
jco23 said:
which ROM are you trying to install?
Click to expand...
Click to collapse
LiquidSmooth v2.9 by DHacker29
http://forum.xda-developers.com/showthread.php?t=2373703
I have also tried Carbon ROM but was having reboots with that too. I liked liquidsmooth better so trying to make this work.
jcxmej said:
LiquidSmooth v2.9 by DHacker29
http://forum.xda-developers.com/showthread.php?t=2373703
I have also tried Carbon ROM but was having reboots with that too. I liked liquidsmooth better so trying to make this work.
Click to expand...
Click to collapse
are you flashing a kernel at the same time?
I would recommend trying a basic 4.2.2 ROM right now - like unoffical AOKP.
another problem could be the GApps or GSM fix. try installing just the ROM without the GApps perhaps?
carbon was very solid too. unfortunately, I can't help you with the GSM fix, as I am CDMA.
jco23 said:
are you flashing a kernel at the same time?
I would recommend trying a basic 4.2.2 ROM right now - like unoffical AOKP.
another problem could be the GApps or GSM fix. try installing just the ROM without the GApps perhaps?
carbon was very solid too. unfortunately, I can't help you with the GSM fix, as I am CDMA.
Click to expand...
Click to collapse
Okay i will try but had this reboot issue even with the stock ROM after flashing with Utility 1.20.
jcxmej said:
Okay i will try but had this reboot issue even with the stock ROM after flashing with Utility 1.20.
Click to expand...
Click to collapse
hmm.... not really sure then. perhaps you lost root? try re-installing SuperSU - I'm just grasping at straws here.
someone mentioned a similar issue:
http://forum.xda-developers.com/showthread.php?p=44317692#post44317692
jco23 said:
hmm.... not really sure then. perhaps you lost root? try re-installing SuperSU - I'm just grasping at straws here.
someone mentioned a similar issue:
http://forum.xda-developers.com/showthread.php?p=44317692#post44317692
Click to expand...
Click to collapse
I think I have root access I had no issue with it. Okay maybe I will check the thread you gave. Anyways I tried Eclipse ROM which is based AOKP. Still had reboots. So I switched back to liquid. Anyways Im gonna keep trying the basics. If anyone has any suggestions I could try its welcome.
PS. Should I flash another kernel with the ROM just in case ? I have been only installing ROM and gapps only till now.
jcxmej said:
I think I have root access I had no issue with it. Okay maybe I will check the thread you gave. Anyways I tried Eclipse ROM which is based AOKP. Still had reboots. So I switched back to liquid. Anyways Im gonna keep trying the basics. If anyone has any suggestions I could try its welcome.
PS. Should I flash another kernel with the ROM just in case ? I have been only installing ROM and gapps only till now.
Click to expand...
Click to collapse
I don't think changing the kernel will do it.... I suspect the issue is with your recoveries - will respond in other thread....
As some of you already know, version 4.4 BETA 1 of Paranoid Android is problematic — it results in a boot loop, with recovery mode being unaccessible.
(I was stupid enough to perform a flash without bothering to check PA's dedicated thread. I know, dumb move.)
Now, download mode is still available, but my computer will not recognize my phone. Therefore, Odin is unusable, I have installed Samsung's USB driver for mobile phone version 1.5.34, but my phone was still not recognized after that.
Any ideas?
same thing happened to me but I downloaded odin 3.09 and booted to download than I succed to flash philz kernel with recovery and restored my backup.
And I think you my have problem with OS, usb port or usb cable.
Try reboot PC, change windows profile, usb port.
Good luck
waro470 said:
As some of you already know, version 4.4 BETA 1 of Paranoid Android is problematic — it results in a boot loop, with recovery mode being unaccessible.
(I was stupid enough to perform a flash without bothering to check PA's dedicated thread. I know, dumb move.)
Now, download mode is still available, but my computer will not recognize my phone. Therefore, Odin is unusable, I have installed Samsung's USB driver for mobile phone version 1.5.34, but my phone was still not recognized after that.
Any ideas?
Click to expand...
Click to collapse
These are the drivers that you downloaded?:
http://downloadcenter.samsung.com/c...Driver_for_Mobile_Phones_v1.5.23.0-retail.exe
What operating system you are using?
If you are using Win 8, I recommend using odin 3:07 or 3:09. Also work well with win7
Odin all versions:
http://www74.zippyshare.com/v/18196321/file.html
panamera2011 said:
These are the drivers that you downloaded?:
http://downloadcenter.samsung.com/c...Driver_for_Mobile_Phones_v1.5.23.0-retail.exe
What operating system you are using?
If you are using Win 8, I recommend using odin 3:07 or 3:09. Also work well with win7
Odin all versions:
http://www74.zippyshare.com/v/18196321/file.html
Click to expand...
Click to collapse
I guess I'll make a rule about not flashing my phone after soccer... Too tired to even think straight. Well, it turns out I was using the wrong version of USB driver and Odin, too.
I will keep you guys updated. Thanks for the quick replies, everyone!
[EDIT]: Awesome. I've been able to install Philz's recovery (using Odin v3.07), but not the latest version. I'm under the impression that that old version of the recovery is not letting me install Kitkat-based PA ROMs.
Should I flash PA 3.99 first, and then upgrade to PA 4?
waro470 said:
I guess I'll make a rule about not flashing my phone after soccer... Too tired to even think straight. Well, it turns out I was using the wrong version of USB driver and Odin, too.
I will keep you guys updated. Thanks for the quick replies, everyone!
[EDIT]: Awesome. I've been able to install Philz's recovery (using Odin v3.07), but not the latest version. I'm under the impression that that old version of the recovery is not letting me install Kitkat-based PA ROMs.
Should I flash PA 3.99 first, and then upgrade to PA 4?
Click to expand...
Click to collapse
Recovery is build into the kernel, so flash a kernel instead of a full rom.
I recommend Forest-CM11
This kernel and recovery will be overwritten by the rom anyway.
waro470 said:
I guess I'll make a rule about not flashing my phone after soccer... Too tired to even think straight. Well, it turns out I was using the wrong version of USB driver and Odin, too.
I will keep you guys updated. Thanks for the quick replies, everyone!
[EDIT]: Awesome. I've been able to install Philz's recovery (using Odin v3.07), but not the latest version. I'm under the impression that that old version of the recovery is not letting me install Kitkat-based PA ROMs.
Should I flash PA 3.99 first, and then upgrade to PA 4?
Click to expand...
Click to collapse
If you want to try last PA KK, you must first install Forest CM11 kernel V3B, Wipe data / factory reset, wipe cache, wipe davlik cache, then install PA KK, reinstall Forest CM11 V3B kernel, wipe cache, wipe davlik cache reboot.
But now, I recommend to wait for new updates
If you want to try a great rom KK, I recommend using CarbonRom KitKat, I'm testing latest nightly, and it works really great.
Go to in recovery
install, Forest CM11 kernel V3B http://www.mediafire.com/download/t1imczaknfmid69/Forest-CM11-kernel-V3b.zip
Wipe data / factory reset
wipe cache
wipe davlik cache
install rom https://carbonrom.org/mirrors/?file=n7000/nightly/CARBON-KK-NIGHTLY-20140603-1127-n7000.zip
install pa gapps modular http://goo.im/devs/paranoidandroid/roms/gapps-full
Reboot
enjoy
For some reason, I thought it wasn't logical to flash a recovery while being in recovery mode... Anyhow, it's been a smooth ride thanks to you guys.
(Going back to my old Nokia 5230 sure was a scarring experience...)
waro470 said:
For some reason, I thought it wasn't logical to flash a recovery while being in recovery mode... Anyhow, it's been a smooth ride thanks to you guys.
(Going back to my old Nokia 5230 sure was a scarring experience...)
Click to expand...
Click to collapse
Why was it not logical? You just installed a new kernel to get the recent version of cwm which is selinux compatible, abki to flash 4.4 roms.
nokiamodeln91 said:
Why was it not logical? You just installed a new kernel to get the recent version of cwm which is selinux compatible, abki to flash 4.4 roms.
Click to expand...
Click to collapse
I know practically nothing about Android when it comes to under the hood stuff. That and I always have the worst scenario in mind. Since kernel flashing hasn't been trouble-free for me under Linux generally speaking (except for Manjaro), I tend to be careful, and imagine that there could be conflicts.
Firest kernel does not provide a tar version... only the zip file which can only be flashed from recovery
and the problem is exactly this that we cannot access recovery now (after flashing pa 4.4.3)
please suggest a way of getting back my phone again
odin 3.07 is stuck at NAND write start ... i am trying to flash philz recovery 6.07.9 from the source mentioned above
cant seem to fix my phone..pleas Help
Azeazezar said:
Recovery is build into the kernel, so flash a kernel instead of a full rom.
I recommend Forest-CM11
This kernel and recovery will be overwritten by the rom anyway.
Click to expand...
Click to collapse
Here is what i would do in your situation. Note that i am not an expert.
If odin doesnt flash your file, download it again, and try again maybe its a bad download.
If it still does not work try heimdall
If that does not help, include a pit file in odin. <- Can be rather dangerous.
I tried falshing a pit file...even that failed
Azeazezar said:
Here is what i would do in your situation. Note that i am not an expert.
If odin doesnt flash your file, download it again, and try again maybe its a bad download.
If it still does not work try heimdall
If that does not help, include a pit file in odin. <- Can be rather dangerous.
Click to expand...
Click to collapse
Hi all
Got an I9505 on O2 and since lollipop update it restarted a few times by itself. Now it keeps going into a loop where it will restart and the home screen loads, you can use it for about 20-30 seconds and it will reboot again!
Initially when I researched I though it was an app problem but couldn't find the culprit. Then I took it into the Samsung repair centre and they said it needed a clean flash by them. This didn't work and they fitted a new mother board and this still hasn't worked.
I can say that it has twice happened when the Wifi hasn't been working properly so I have turned it off but other than that I have no idea!
Also I have tried rebooting into safe mode but it still does it, aaarrrggghhhh!!!
Any ideas where I can go from here please?
P
Return to kitkat if you can. Otherwise use a custom rom. These would be my suggestions. Since Samsung's repair couldn't fix it, warranty should not be a problem anymore.
Thanks, I am more than willing to try a Custom ROM. Any recommendations? And how easy is it as never done before!
PJBXDA said:
Thanks, I am more than willing to try a Custom ROM. Any recommendations? And how easy is it as never done before!
Click to expand...
Click to collapse
It's fairly easy. Depending on what S4 model you have. Some models have a locked bootloader and that makes the whole thing trickier.
This is what I did:
1) Root with CF-Auto-Root. Thread here.
2) Backup all my apps.
3) Install a custom recovery (TWRP). Download and instructions here.
4) Flash custom rom. Most roms have their own instructions.
You can skip 1 and 2 if you don't want to backup.
Installing a custom recovery can be done using Odin. I recommend TWRP since it's the only one I've used.
Lollipop GPE rom. I've used this rom and didn't have any issues. CM12 seems a bit faster, but the GPE was more stable and bug-free.
Thanks I tried to install the CM12 before you posted using the instructions there but it failed, I assume that it needs to be rooted.
PJBXDA said:
Thanks I tried to install the CM12 before you posted using the instructions there but it failed, I assume that it needs to be rooted.
Click to expand...
Click to collapse
You need a custom recovery to install any rom. It doesn't matter if it's rooted or not.
Get a custom recovery. Get all the necessary zip files (rom, gapps, etc). Place all the zip files on the external sd card. Boot into the custom recovery. Wipe /data, /cache and /dalvik-cache.
Go to Install (if on TWRP), go to the location where you saved the downloaded rom zip and select it. The swipe the slider to begin flashing. Afterwards flash the gapps zip. Reboot.
Also, don't use the recovery posted in the CM12 thread. It was specially made by the dev and will convert your file system to f2fs. What it basically means is that it will wipe your internal storage completely.
GDReaper said:
You need a custom recovery to install any rom. It doesn't matter if it's rooted or not.
Get a custom recovery. Get all the necessary zip files (rom, gapps, etc). Place all the zip files on the external sd card. Boot into the custom recovery. Wipe /data, /cache and /dalvik-cache.
Thanks, doing that now
Click to expand...
Click to collapse
PJBXDA said:
GDReaper said:
You need a custom recovery to install any rom. It doesn't matter if it's rooted or not.
Get a custom recovery. Get all the necessary zip files (rom, gapps, etc). Place all the zip files on the external sd card. Boot into the custom recovery. Wipe /data, /cache and /dalvik-cache.
Thanks, doing that now
Click to expand...
Click to collapse
On the CF-Root page it says to open Odin and click on the PDA button but I cannot find a PDA button!
Edit: It is the AP button on the newer version!
Click to expand...
Click to collapse
GDReaper said:
You need a custom recovery to install any rom. It doesn't matter if it's rooted or not.
Get a custom recovery. Get all the necessary zip files (rom, gapps, etc). Place all the zip files on the external sd card. Boot into the custom recovery. Wipe /data, /cache and /dalvik-cache.
Go to Install (if on TWRP), go to the location where you saved the downloaded rom zip and select it. The swipe the slider to begin flashing. Afterwards flash the gapps zip. Reboot.
Also, don't use the recovery posted in the CM12 thread. It was specially made by the dev and will convert your file system to f2fs. What it basically means is that it will wipe your internal storage completely.
Click to expand...
Click to collapse
When you say go to install, do you mean install update... in the recovery menu? I do not have an install from zip option
PJBXDA said:
When you say go to install, do you mean install update... in the recovery menu? I do not have an install from zip option
Click to expand...
Click to collapse
You don't have a custom recovery installed. That is probably the stock recovery. You can't flash a rom using the stock recovery.
You absolutely need a custom recovery if you want to flash a custom rom.
Custom recoveries are: TWRP (Team Win Recovery Project), CWM (ClockworkMod Recovery) and PhilZ Touch Recovery. Either one should work. But you necessarily need one.
GDReaper said:
You don't have a custom recovery installed. That is probably the stock recovery. You can't flash a rom using the stock recovery.
You absolutely need a custom recovery if you want to flash a custom rom.
Custom recoveries are: TWRP (Team Win Recovery Project), CWM (ClockworkMod Recovery) and PhilZ Touch Recovery. Either one should work. But you necessarily need one.
Click to expand...
Click to collapse
Thanks I have installed TWRP, then it asked me to install Busybox which I did. Tried to Install from Zip and it went back to the original recovery and now when I am trying to restart the phone I just get messages telling me things have stopped working (Google play, settings etc etc) and a black screen!
Currently factory resetting and will try again
PJBXDA said:
Thanks I have installed TWRP, then it asked me to install Busybox which I did. Tried to Install from Zip and it went back to the original recovery and now when I am trying to restart the phone I just get messages telling me things have stopped working (Google play, settings etc etc) and a black screen!
Currently factory resetting and will try again
Click to expand...
Click to collapse
Follow the link I gave you. They have several instrunctions on how to install TWRP. You can install TWRP with Odin too.
Here, There are 3 ways to install. Use Odin. It doesn't require root and should be the easier one. Just UNTICK auto-reboot in Odin before flashing. Once it's done, turn the phone off and use the key combo to get into TWRP recovery.
GDReaper said:
Follow the link I gave you. They have several instrunctions on how to install TWRP. You can install TWRP with Odin too.
Here, There are 3 ways to install. Use Odin. It doesn't require root and should be the easier one. Just UNTICK auto-reboot in Odin before flashing. Once it's done, turn the phone off and use the key combo to get into TWRP recovery.
Click to expand...
Click to collapse
I think I am in, got through to the TWRP recovery and flashed the files but now I have a blue face with a pulsing white light behind it and have had for about 10 minutes. Any idea what is happening please?
PJBXDA said:
I think I am in, got through to the TWRP recovery and flashed the files but now I have a blue face with a pulsing white light behind it and have had for about 10 minutes. Any idea what is happening please?
Click to expand...
Click to collapse
I guess that's the CM12 logo. First boot after flashing always takes some time because the rom is configuring stuff.
If you still don't get into android, turn off the device and turn it on again. If you've done everything correctly there is no reason why it shouldn't boot.
GDReaper said:
I guess that's the CM12 logo. First boot after flashing always takes some time because the rom is configuring stuff.
If you still don't get into android, turn off the device and turn it on again. If you've done everything correctly there is no reason why it shouldn't boot.
Click to expand...
Click to collapse
It is their logo but it seems to be taking forever, any idea how long a first boot should take?
PJBXDA said:
It is their logo but it seems to be taking forever, any idea how long a first boot should take?
Click to expand...
Click to collapse
It shouldn't take that long. For me it always took under 5 minutes. Tell me exactly what you did.
GDReaper said:
It shouldn't take that long. For me it always took under 5 minutes. Tell me exactly what you did.
Click to expand...
Click to collapse
Did as you said, in the end I tried flashing the other GPE ROM and that has worked but I do not really like it. Trying the Cynogen again by downloading direct to the SD card and not copying it over. I want to say a very big thank you GDReaper for all your help, it is and has been very much appreciated.
PJBXDA said:
Did as you said, in the end I tried flashing the other GPE ROM and that has worked but I do not really like it. Trying the Cynogen again by downloading direct to the SD card and not copying it over. I want to say a very big thank you GDReaper for all your help, it is and has been very much appreciated.
Click to expand...
Click to collapse
No problem. You could try a different build. Or you could try a CM12 based rom. SaberMod worked fine for me. And it's the closest to the actual CM12 you can get.
GDReaper said:
No problem. You could try a different build. Or you could try a CM12 based rom. SaberMod worked fine for me. And it's the closest to the actual CM12 you can get.
Click to expand...
Click to collapse
Cheers, I have CM12 up and running now. Downloaded the files straight to the SD card and they worked. Seems OK but might try others, how do I go about trying SaberMod, do I need to flash that? Sorry to keep asking what are no doubt pretty obvious questions but I'm pretty new to this!
Want to get rid of the google search box for starters!
PJBXDA said:
Cheers, I have CM12 up and running now. Downloaded the files straight to the SD card and they worked. Seems OK but might try others, how do I go about trying SaberMod, do I need to flash that? Sorry to keep asking what are no doubt pretty obvious questions but I'm pretty new to this!
Want to get rid of the google search box for starters!
Click to expand...
Click to collapse
SaberMod is a rom. SaberMod CM12.1.
They are very similar. The difference is how they tackle optimizations.
Yes, you will have to flash it. But you can also stick with normal CM12 if you don't have any issues.
The google search box from the home screen or the recents?
You can change the launcher to get rid of it from the home screen.
To remove it from the recents there is an option somewhere in the settings.