With the recent update of CWM/PBJ kernel I'd like to update to the latest ones and I'd also like to switch ROMs to test some other ones out. Can someone guide me through this? I've never switched before I just followed (http://forum.xda-developers.com/showthread.php?t=1122657), that's it(as far as flashing and such goes). I'd just like an easy to follow guide on updating the Kernel/CWM and installing a new ROM(If and when I'd need to disable Voodoo, if flashing something will reset all my contacts/apps, etc) I'd really appreciate it and thanks will be in order for anyone and everyone who is helpful :]
Info: I'm running 6/15 PBJ OC kernel with 1.8.5 Gummycharged ROM
There's not much to it. kernel and Rom can be updated in CWM.
Download the rom you want to flash to /sdcard (root of your sdcard)
reboot into recovery. If you do not have the option holding down the power button and hitting restart. Dl a terminal emulator and type:
Code:
$su (to gain root)
#reboot recovery
Wipe Cache and factory data reset
Go to advanced: Wipe Dalvik cache and battery settings
scroll to flash with a zip
choose: select zip from sdcard
choose the zip that you downloaded
once the install is complete reboot phone. let rom install
Follow same thing for Kernel. Just make sure you remember what the name of your kernel is.
dragonstalker said:
There's not much to it. kernel and Rom can be updated in CWM.
Download the rom you want to flash to /sdcard (root of your sdcard)
reboot into recovery. If you do not have the option holding down the power button and hitting restart. Dl a terminal emulator and type:
Code:
$su (to gain root)
#reboot recovery
Wipe Cache and factory data reset
Go to advanced: Wipe Dalvik cache and battery settings
scroll to flash with a zip
choose: select zip from sdcard
choose the zip that you downloaded
once the install is complete reboot phone. let rom install
Follow same thing for Kernel. Just make sure you remember what the name of your kernel is.
Click to expand...
Click to collapse
That works a treat thank you.
Easier way to get into CWM: hold down Power+Volume Up+Home until you see SAMSUNG, let go, and you'll boot straight into recovery. No need to mess around with terminal commands.
Also, when flashing a kernel only (not a ROM), there's no need to wipe data.
I'm running CM7 on my G2X alongside Trinity kernel. I've got ROM Manager Premium on my phone to check nightlies. Whenever I get an update notification I do the following:
1) download the nightly
2) reboot into recovery
3) format /system
4) format Dalvik
5) format cache
6) install nightly
7) install google apps
8) install Trinity
I would like to find a way to automate steps 3-8 in ClockworkMod. I'm currently running 4.0.0.2. Does anybody know of a way to accomplish this?
mastermindg said:
I'm running CM7 on my G2X alongside Trinity kernel. I've got ROM Manager Premium on my phone to check nightlies. Whenever I get an update notification I do the following:
1) download the nightly
2) reboot into recovery
3) format /system
4) format Dalvik
5) format cache
6) install nightly
7) install google apps
8) install Trinity
I would like to find a way to automate steps 3-8 in ClockworkMod. I'm currently running 4.0.0.2. Does anybody know of a way to accomplish this?
Click to expand...
Click to collapse
You format system for every nightly? Good Lord, man....just wipe dalvik and cache...in fact, if you just use Rom Manager, and hit the options to only wipe dalvik and install gapps, it will do the rest for you.
I'm not just installing the nightly...hence the reason for this post. I'm also installing a custom kernel as well. This needs to be done alongside the nightly.
And...for the record...formatting /system is only one additional step in 8 steps and it's not even the longest one.
mastermindg said:
I'm not just installing the nightly...hence the reason for this post. I'm also installing a custom kernel as well. This needs to be done alongside the nightly.
And...for the record...formatting /system is only one additional step in 8 steps and it's not even the longest one.
Click to expand...
Click to collapse
No need to format even if reinstalling the kernel. You should
1)wipe dalvik/cache
2)flash nightly
3)flash kernel
Lol...
Hi there,
A few weeks ago I rooted my tf101 and installed clockworkmod 5. Installing the rom from Raymanfx isn't a problem, but it doesn't run very smoothly. So I wanted to try the ROM of EOS4. Installed both nightly's .93 and .92, but both don't work. I've wiped the cache, but it still stays stuck in bootscreen. I'm wondering, how can I find out the problem and how can I solve it?
Thx in advance!
Yours sincerely,
Anderverhaal
Any time you flash a different ROM (from a different DEV), for best results you should wipe:
Cache
Davlik Cache
System (ROM)
Factory Reset (will not wipe the /data/media/ aka /sdcard/ directory, just the apps installed in the /data/ directory).
Failing to do a factory reset, there may be some system settings from your previous ROM that are still lingering and causing issues with the TeamEOS 4.
Also, I would HIGHLY recommend using TWRP 2.3.2.3 for EOS 4. The new multi-user file structure does not work well with CWM 5.X.
If you want to update, you can boot to CWM, connect to your tablet via ADB, push the latest TWRP blob and use the ADB shell command to dd it to the recovery partition.
Otherwise, install a ROM that boots, then install GooManager and then choose the Install OpenRecovery Script.
I want to flash SlimROM, but I think I messed up.
I installed CWM, and wiped everything I needed to (factory, data, cache, system) WITHOUT putting the SlimROM zips in ahead.
Right now I can get into fastboot and CWM.
I tried installing with adb sideload, but the device turn to unknown device (Android > Nexus 5) when I access the adb sideload function.
Is there a driver somewhere that I missed?
Any help would be great!
ADB Driver Installer
Don't use CWM, support has been discontinued. Use TWRP 2.8.1.0 instead.
Samsung Galaxy Tab 2
AOSP - Project
This Rom is based on AOSP to give the user a pure AOSP feeling.
The builds only includes device specific changes to compile and get a booting AOSP!
Code:
#include
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear
* war, or the current economic crisis caused by you following these
* directions. YOU are choosing to make these modifications, and
* if you point your finger at me for messing up your device, I will
* laugh at you.
*/
Downloads:
ROM Downloads for all supported devices can be found here
(Those who have a repartitioned system partition use "not-block-based" builds! Other builds won't be flashable on those devices!)
[#DONATETOME]
FAQ
Q: Will there be any updates?
A: Yes, there will, but only if i can fix a bug or AOSP releases an Update - else there's no update needed.
Q: There's a nice feature in XXX-Rom and i like to have this included - ADD IT!
A: Sorry, i'lll keep this Rom Stock-AOSP as possible. Maybe XXX-Rom is a better choice for you, if you really need this feature.
Q: How to enable root?
A: This Rom doesn't have root included. Why? Because root isn't part of AOSP. You can find the way to SuperSU Thread from @Chainfire and download SuperSU as flashable-ZIP if you need root.
Q: Is it possible to overclock the kernel?
A: Yes and no. First of all you need root and a Kernel-App like KernelAdiutor. After that you can slight OC the CPU & GPU - this Rom includes latest SlimLP Kernel.
Q: I found a bug.
A: Nice finding my friend Please provide needed logs - ADB will be your best friend, if you are replying in a development thread
There's a lot of tutorials out on YouTube or XDA on how to setup and use ADB - it's really simple!
At least you should tell step by step how to reproduce the issue.
I started creating a gerneral FAQ on my github - it includes instructions how to flash a Rom, how to get proper logs, etc. etc. etc., you can find it here
Changelog
Code:
2015-11-08 It's stock AOSP as released by Google (Android 5.1.1 R29 LVY48I), only additions
- screenshot: quick delete action
- advanced reboot menu
- Launcher3 instead Launcher2
- BootMessage: Show each app name being optimized during boot
- Show application's package name in the "App info" screen.
- Open app when clicking on icon in App Info screen
(... forgot about the releases between ...)
2015-08-07 based on Android 5.1.1_r9
XDA:DevDB Information
[P51xx][5.1.1] Samsung Galaxy Tab 2 AOSP-Project, ROM for the Samsung Galaxy Tab 2
Contributors
Android-Andi
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: AOSP
Version Information
Status: Testing
Created 2015-08-07
Last Updated 2017-04-30
Thank you Andi! I've been hoping for this! Up and running, really really smooth.
Sent from my GT-P5110 using Tapatalk
Thank you Sir.. Can't wait to try it out.
Sent from my Nexus 6 using XDA Premium HD app
stuck at samsung galaxy tab page
Is it normal that it stuck at samsung galaxy tab page for the first boot after flashed? i only flashed the rom and a minimal gapps, using the latest twrp 2.8.7.1. waited for like 30mins but it still there
luckywang95 said:
Is it normal that it stuck at samsung galaxy tab page for the first boot after flashed? i only flashed the rom and a minimal gapps, using the latest twrp 2.8.7.1. waited for like 30mins but it still there
Click to expand...
Click to collapse
No. Data or cache on f2fs? If yes format them back to ext 4.
Also make sure you did a clean install.
Try without gapps maybe, if it boots you can flash gapps after that.
Hello
p5110
installed no problem
thanks
regards
Android-Andi said:
No. Data or cache on f2fs? If yes format them back to ext 4.
Also make sure you did a clean install.
Try without gapps maybe, if it boots you can flash gapps after that.
Click to expand...
Click to collapse
I reformat everything including data, cache, internal storage, system.... all in ext4... :crying:
luckywang95 said:
I reformat everything including data, cache, internal storage, system.... all in ext4... :crying:
Click to expand...
Click to collapse
Wipe data, system, cache, dalvic.
Reboot recovery once.
Flash rom.
(Any error messages visible?)
Reboot.
If it boots, boot back into recovery and flash gapps.
If still not work, start clean flash again and get a recovery.log directly after flashing.
Android-Andi said:
Wipe data, system, cache, dalvic.
Reboot recovery once.
Flash rom.
(Any error messages visible?)
Reboot.
If it boots, boot back into recovery and flash gapps.
If still not work, start clean flash again and get a recovery.log directly after flashing.
Click to expand...
Click to collapse
I tried wipe everything to ext4 again and reflashed the rom with and without gapps. also tried using twrp 2.8.4.1 to flash the rom but still the same. No error message given. Im trying one more time now... :crying:
luckywang95 said:
I tried wipe everything to ext4 again and reflashed the rom with and without gapps. also tried using twrp 2.8.4.1 to flash the rom but still the same. No error message given. Im trying one more time now... :crying:
Click to expand...
Click to collapse
It's important sometimes to reboot the recovery once after wipe.
Latest twrp you also need to confirm to allow changes on system partition (you'll be asked on booting twrp)
After flashing please use adb to pull the log
adb pull /tmp/recovery.log while still in TWRP
What's your device? P5100 or p5110?
Android-Andi said:
It's important sometimes to reboot the recovery once after wipe.
Latest twrp you also need to confirm to allow changes on system partition (you'll be asked on booting twrp)
After flashing please use adb to pull the log
adb pull /tmp/recovery.log while still in TWRP
What's your device? P5100 or p5110?
Click to expand...
Click to collapse
yes. i chose allow changes. my device is p5100. installation failed. i will get recovery.log now and upload to u soon.
---------- Post added at 10:45 AM ---------- Previous post was at 10:31 AM ----------
Android-Andi said:
It's important sometimes to reboot the recovery once after wipe.
Latest twrp you also need to confirm to allow changes on system partition (you'll be asked on booting twrp)
After flashing please use adb to pull the log
adb pull /tmp/recovery.log while still in TWRP
What's your device? P5100 or p5110?
Click to expand...
Click to collapse
I have a new problem. Im still a new member so im not allow to pots a link or attach any file to here. how am i able to send the log file to you?
luckywang95 said:
I have a new problem. Im still a new member so im not allow to pots a link or attach any file to here. how am i able to send the log file to you?
Click to expand...
Click to collapse
Copy it on pastebin.com , posting here remove the http:/www and you'll be able to send
Android-Andi said:
Copy it on pastebin.com , posting here remove the http:/www and you'll be able to send
Click to expand...
Click to collapse
i have sent it to you through private message. i will do it again here.
drive.google.com/file/d/0B3WN3t7uFUZvcFh1cTRlVzdacEU/view?usp=sharing
its google drive.
Tried flashing from different path?
/external_sd/[ROM][P5100][AOSP]
Maybe all th [ and ] in the path aren't good. Can't see any issue in the log...
If still not work:
On Galaxy Tab 2 logo you'll be able after some seconds to get adb access.
Please take a logcat & dmesg
and for your information. i tried flashed the latest cm12.1 by you as well. no problem on booting and now booted to homescreen. :good:
luckywang95 said:
and for your information. i tried flashed the latest cm12.1 by you as well. no problem on booting and now booted to homescreen. :good:
Click to expand...
Click to collapse
Good to know... Mh... Could you get me a logcat and dmesg?
I had a similar issue on p3110, but i am sure i fixed it on p5100 before compiling... Maybe something else is wrong then...
Android-Andi said:
Tried flashing from different path?
/external_sd/[ROM][P5100][AOSP]
Maybe all th [ and ] in the path aren't good. Can't see any issue in the log...
If still not work:
On Galaxy Tab 2 logo you'll be able after some seconds to get adb access.
Please take a logcat & dmesg
Click to expand...
Click to collapse
but i have the same directory when i flash the cm12?
---------- Post added at 11:58 AM ---------- Previous post was at 11:12 AM ----------
Android-Andi said:
Tried flashing from different path?
/external_sd/[ROM][P5100][AOSP]
Maybe all th [ and ] in the path aren't good. Can't see any issue in the log...
If still not work:
On Galaxy Tab 2 logo you'll be able after some seconds to get adb access.
Please take a logcat & dmesg
Click to expand...
Click to collapse
well... i tried for quite a long time. when it stuck at samsung logo, it doesnt connect to my computer. just now the recovery.log i was using my external sd card...
luckywang95 said:
but i have the same directory when i flash the cm12?
.
Click to expand...
Click to collapse
ok, then it's not the cause
well... i tried for quite a long time. when it stuck at samsung logo, it doesnt connect to my computer. just now the recovery.log i was using my external sd card...
Click to expand...
Click to collapse
Adb should work, have you tried?
You can check on:
adb devices
You'll see if it detects the device.
Maybe download minimal adb and fastboot, easy to use
Android-Andi said:
ok, then it's not the cause
Adb should work, have you tried?
You can check on:
adb devices
You'll see if it detects the device.
Maybe download minimal adb and fastboot, easy to use
Click to expand...
Click to collapse
its not connected to computer... i cant use adb.... i tried installing all driver... but still cannot... adb devices shows nothing..:crying:
---------- Post added at 12:23 PM ---------- Previous post was at 12:04 PM ----------
Android-Andi said:
ok, then it's not the cause
Adb should work, have you tried?
You can check on:
adb devices
You'll see if it detects the device.
Maybe download minimal adb and fastboot, easy to use
Click to expand...
Click to collapse
sorry, just now is my usb hub not working. not the device. dmesg and logcat i uploaded to google drive. in this folder. it included the recovery.log just now.
https://drive.google.com/open?id=0B...9Ydkw3T0VfZUhWS0ticHdtYnhOQ1hWTFhhRkVtSEh3QVE
logcat is empty. but it is still in the folder.
Hello AndroidAndi
First, thank you for this rom and I have not had any problems during installation.
Full wipe (data, cache, dalvik, format system) and installation of Gapps tk_gapps micro-modular-5.1.1.
If you want sreens? :
Sorry for my English
Dirk