Related
NOTE: I am not the developer of this rom! I am only posting it on XDA with the permission of the Bonsai Team. The download link is on the Bonsai website, they use a checkout system to track downloads and to present you with an easy way to donate if you choose. YOU DO NOT HAVE TO DONATE TO DOWNLOAD! I will do my best to keep this post updated with change logs.
Custom tuned and ready for your sleek new Samsung tablet. The Bonsai ROM provides superior battery life and performance delivering on the promise of the Android OS for mobile devices.
This is an early beta release Bonsai for your Samsung Galaxy Tab 10.1 based from the stock Android Honeycomb v3.1 release. We’ve consolidated the latest Android community developments and rolled in the Bonsai magic to produce a replacement Android OS that will double your stock tablet performance.
Note: Due to going to some shell scripting where we have richer language and can control the install better, we are not able to update the progress bar while in this stage of running the install.
Some of the features of this release include: (credits below)
Android Kernel updated to v2.6.36.4
Overclockable kernel
Kernel module support for tun, cifs, aufs, ntfs, bluetooth mouse, xbox joystick
Voodoo Sound v9 (first release for Galaxy Tab 10.1) (Updated to v10)
init.d initialization script support
Ext4 filesystems can be configured without journaling enabled
New ROM packaging and install reduces package size by 20%
Deodexed and png graphics optimized
v0.1.5 Changes:
Update to Voodoo sound v10
Fixed problem with Plex app not streaming video
Kernel tuning which has raised MFlops from about 50 to 80 (AnTuTu score around 5800)
Changed init.d script permissions to accomodate “challenged” editor apps
Install script changes to accomodate more device variations
Known to run on Locked and Unlocked retail Tablets and I/O Tablets
Fixed problem where tablet would not boot with USB cable attached
Reduced delay seen when booting the device
Known Issues:
A few users have reported issues with boot animations in most cases the device seems to boot fine.
There seems to be a problem with CWM when its flashed via Rom Manager.
Google I/O Devices are currently not working. (There are instructions in post 121)
Install Instructions:
Download the ROM
Move the .zip to /sdcard
Unplug anything connected to the Tab
Reboot to Recovery
Make a nandroid backup
Wipe cache
Wipe dalvik
Flash the .zip
Reboot
Please be patient and wait for it to boot it it can take a while
Enjoy
If you want to change the OC settings, you will need to edit the file, /etc/init.d/24-cpufreq to set these values. The values are in the top of the file as follows:
Code:
FREQGOV=’ondemand’
MAXFREQ=’1000000’
MINFREQ=’216000’
Change these values as you wish. The parameters are applied on reboot.
Credits:
kernel: @pershoot []
voodoo sound: @supercurio []
Along with those changes that were provided in earlier releases, we are providing a number of changes that have been backported from the nVidia Tegra development. Changes include:
Tegra CPU power control
Add Tegra CPU perfmon context for power
Redisgn of Tegra CPU reset handling
Various Tegra CPU (cortex-A9) cache handling fixes
Fix memory leak in video driver
Tegra shared clock cleanup
Please flash this file after installing the 0.1.5 ROM package.
0.2.4 KERNEL UPDATE
DOWNLOAD HERE
NOTE: TouchWiz UX version includes the v0.2.4 Kernel. This ROM package is double the size of the non-TouchWiz, now weighing in at 350MB. Please help us conserve bandwidth. If for some reason you believe the ROM package to be corrupt, please double check your package using the md5sum command. The md5 checksum of this package is: 484a758563e661a7731aeed4a1e880f0
This is an early beta release Bonsai for your Samsung Galaxy Tab 10.1 based from the stock Android Honeycomb v3.1 release which includes TouchWiz. We’ve consolidated the latest Android community developments and rolled in the Bonsai magic to produce a replacement Android OS that will more than double your stock tablet performance.
WITH TOUCHWIZ UX DOWNLOAD HERE
----------------------------------------
you can use setcpu to change cpu frq.
Bug report: if you turn off your tab and plug into the charger to enable charging mode, it causes reboot loop (therefore you can't charge it while off)
antonyfl said:
you can use setcpu to change cpu frq.
Bug report: if you turn off your tab and plug into the charger to enable charging mode, it causes reboot loop (therefore you can't charge it while off)
Click to expand...
Click to collapse
Thanks for the bug report. As for the setcpu thing, while you can do that the system is configured with its own governor of sorts and setcpu fights with it and can cause some slowdowns so its not recommend to use it.
Currently the best way is to adjust it in an init script located in /etc/init.d/24-cpufreq
Any idea why I get a scrambled picture when i reboot that hangs before booting?
it seems like a boot logo/animation crapping out
DroidHam said:
Any idea why I get a scrambled picture when i reboot that hangs before booting?
Click to expand...
Click to collapse
so far no, however the dev is looking into this issue, as well as the kernel panic issue.
I am enjoying this ROM, glad an official thread was made
i'll add my issue in hopes someone can help. tried to load rom yesterday. it boot looped at the initial "samsung galaxy tab" screen. powered down then into upload mode, kernel panic. got into fastboot and booted cwm. tried to restore my last nandroid and it boot looped at the samsung animation screen. tried another nandroid and got error at data. i get either of these responses. i've tried to factory reset and still get boot loops. repeated all these a hundred times and boot loop at either of those screens. any ideas on how to get this thing back running. at this point i don't even care so much about a nandroid, i'd settle for any type of working tab.
bodiecon said:
i'll add my issue in hopes someone can help. tried to load rom yesterday. it boot looped at the initial "samsung galaxy tab" screen. powered down then into upload mode, kernel panic. got into fastboot and booted cwm. tried to restore my last nandroid and it boot looped at the samsung animation screen. tried another nandroid and got error at data. i get either of these responses. i've tried to factory reset and still get boot loops. repeated all these a hundred times and boot loop at either of those screens. any ideas on how to get this thing back running. at this point i don't even care so much about a nandroid, i'd settle for any type of working tab.
Click to expand...
Click to collapse
Have you tried to use odin to restore the tab to stock? i would suggest you try this first.
this ODIN version: HERE
this pda md5: HERE
Also I would like to add that when flashing the Bonsai ROM make sure your tab is not connected to anything including the charger and usb.
I have had ZERO issues at all with this ROM
Tried install on a rooted 16G running pershoot's latest oc kernel......
Wiped dalvik/cache
installed
reboot
never got past the gt 10.1 screen, was able to get back to recovery and restored my nandroid backup
maybe it was a bad flash, going to try one more time unless anyone has suggestions or sees something I missed
mark1962nc said:
Tried install on a rooted 16G running pershoot's latest oc kernel......
Wiped dalvik/cache
installed
reboot
never got past the gt 10.1 screen, was able to get back to recovery and restored my nandroid backup
maybe it was a bad flash, going to try one more time unless anyone has suggestions or sees something I missed
Click to expand...
Click to collapse
Reread the instructions because I added an additional step, also if the problem persist try going back to a stock kernel first and let me know how that goes.
Also keep in mind the first boot takes a very long time, my first boot took almost 15mins, and about five of that was on the first boot screen.
djrajir said:
Reread the instructions because I added an additional step, also if the problem persist try going back to a stock kernel first and let me know how that goes.
Also keep in mind the first boot takes a very long time, my first boot took almost 15mins, and about five of that was on the first boot screen.
Click to expand...
Click to collapse
The first time I rebooted to recovery through Rom Manager (which I don't generally do), this wouldn't affect anything would it?
mark1962nc said:
The first time I rebooted to recovery through Rom Manager (which I don't generally do), this wouldn't affect anything would it?
Click to expand...
Click to collapse
I'm not sure, it shouldn't however there have been issues like this before which is why i always manually reboot my device into recovery (such as what is currently going on with Galaxy S 4g devices)
what is journaling?
Also i flashed this (over pershoots kernel)
and now its stuck on Samsung Tab 10.1 at boot
I flashed following the instructions and everything installed fine except I keep getting fc on most of the apps I try to run. Anyone else having that issue?
lollee76 said:
I flashed following the instructions and everything installed fine except I keep getting fc on most of the apps I try to run. Anyone else having that issue?
Click to expand...
Click to collapse
How did you reinstall apps? Market or TiBu?
SS2006 said:
what is journaling?
Also i flashed this (over pershoots kernel)
and now its stuck on Samsung Tab 10.1 at boot
Click to expand...
Click to collapse
Please let me know if you get it to work (this was my experience as well)....I'm going to give it another shot after dl'ing.
I cant seem to turn it on anymore cause battery died while it was frozen
i pluged it in, at one time it showed the battery charge indiciator
now its just not turning on
mark1962nc said:
How did you reinstall apps? Market or TiBu?
Click to expand...
Click to collapse
The first time I tried I did the whole wipe data/factory,cache,dalvik and re-installed apps using My Backup and got fc like crazy...so then I restored my nandroid backup and started over (Note I did test one app with TiBu by installing from the market and restoring just the data to that app using TiBu and it just hung up).
This morning I read this post and restored my nandroid again and tried the directions in OP and only wiped cache and dalvik which left my apps as is.
I also want to note I was using pershoots kernel before flashing this ROM.
Hey y'all.
Please help me. My P990 is stuck right after the LG logo on bootup.
First of all, this is what ive done:
1. Rooting the phone - succesful
2. Following the guide to install CyanogenMod 7.1.0 (stable) ROM - succesfull
- Nandroid backup
- Wipe all data + cache
- Can't remember it all really lol, but i had cyanogenmod working succesfully!
3. I wanted "voodoo sound", therefor i was told i had to flash a new kernel, which was working to cyanogenmod - thats why i chosed this kernel: vorkKernel-OC/UV Kernel for CM[20111105] which can be found here on xda, sorry i cant link yet - so what i did was downloading the .apk file, and in there, i could choose some things to get with it, and then download the .zip to flash from recovery mode. So i downloaded, flashed it from Clockworkmod recovery and it finished succesfully. So i rebooted my phone, it came with the "LG", then the logo (without animation) and then just black screen.
I feel like i cant do anything. As always when i try to open recoverymode (power + vol. down) it comes with: "S/W Update" (while flashing and nandroid backuping ive used ROM Manager's function "Boot to recovery".)
Ive tried to press any buttons.
Ive tried to plug my phone to the computer, no effekt.
Im really lost! Please help me
Thanks.
curzey said:
Hey y'all.
Please help me. My P990 is stuck right after the LG logo on bootup.
First of all, this is what ive done:
1. Rooting the phone - succesful
2. Following the guide to install CyanogenMod 7.1.0 (stable) ROM - succesfull
- Nandroid backup
- Wipe all data + cache
- Can't remember it all really lol, but i had cyanogenmod working succesfully!
3. I wanted "voodoo sound", therefor i was told i had to flash a new kernel, which was working to cyanogenmod - thats why i chosed this kernel: vorkKernel-OC/UV Kernel for CM[20111105] which can be found here on xda, sorry i cant link yet - so what i did was downloading the .apk file, and in there, i could choose some things to get with it, and then download the .zip to flash from recovery mode. So i downloaded, flashed it from Clockworkmod recovery and it finished succesfully. So i rebooted my phone, it came with the "LG", then the logo (without animation) and then just black screen.
I feel like i cant do anything. As always when i try to open recoverymode (power + vol. down) it comes with: "S/W Update" (while flashing and nandroid backuping ive used ROM Manager's function "Boot to recovery".)
Ive tried to press any buttons.
Ive tried to plug my phone to the computer, no effekt.
Im really lost! Please help me
Thanks.
Click to expand...
Click to collapse
Sounds like a boot loop. Check filesystem compatibility of the kernel you flashed. Might not be compatible with the one previously used by CM.
you should wipe cache and wipe dalvik cache if you want to flash the kernel. and in order to get work your phone again, you should nvflash cause your phone can't do anything
You're trying to enter recovery wrong. Hold both power and vol- for around 10secs. If you're getting S/W Update, you're only holding volume down.
vokkernal, how to make it work?
Hi, even I tried that, I got the same error... Can anyone suggest a way to make it work, or if any step is missing?
By the way, I used the latest Version on Cynogenmod (stable) (update-cm-7.1.0-Optimus2X-signed.zip), vokkernal app.
Thanks
Very sorry for slow answer!
Anyone can link a guide for a working NVFlash ? ive tried but it comes up with an "uid read fail" ind the cmd box, after the "Nvflash started" ???
here you are
http://forum.xda-developers.com/showthread.php?t=1007825
Click to expand...
Click to collapse
hmm, I had the same problem trying to enter recovery, You have to press vol down and then power. If you do it at the same time sometimes doesnt work. So try pressing it before power and keep them pressed until you see the LG Logo (but the one with a bit of blue light) then you can't unpress them.
Download smartflash and download stock rom along with baseband and flash it using smartflash by pulling out battery from phone press volumedown and insert usb cable and soon check procedure in xda forum.i garuntee you it will work as i faced same issue
Sent from my LG-P990 using XDA App
Hey guys.
I want to flash the latest CM9 (beta5) on my unmodded factory Galaxy S plus.
This is my plan of attack:
1- Backup Sdcard on PC (pictures, music, videos, etc)
2- Clear Sdcard
3- With Odin, flash FeaModRecovery 1.2
4- Backup everything with CWM on Sdcard then copy backup to PC
5- Format phone and Sdcard (dalvik cache, /system, /data, /cache etc)
6- With Odin, install recovery-clockwork 6.0.1.5
7- Flash CM9 beta5
8- Flash gapps as said here: http://forum.xda-developers.com/showthread.php?t=1825260
9- Reboot phone and voila
I didn't knew anything about flashing my phone up until a couple of hours ago. I've been reading a lot on how it's done and this is what I came up with.
Is this ok??
edit: or do I have to install recovery clockwork 6.0.1.5 first and then start formatting everything?
Install clockworkmod and then format everything. Otherwise that's right so do it like that.
monkeywithbanana said:
Install clockworkmod and then format everything. Otherwise that's right so do it like that.
Click to expand...
Click to collapse
Thanks!
Going to start in a few minutes Can't wait to have ICS!
i've recommend to install cwm 5.5.0.4. doesn't have bugs but it's your choice. Good luck !
I made it to step 3 and even installed recovery cw 6.0.1.5 but I simply can't get into CWM ... It says I have to press volume up + power button for 10 seconds but if I do it just stays at the samsung logo and when I release the buttons it boots the phone normally. If I keep pressing the buttons for, say 1 minute, it loops the samsung logo until I release them and it boots normally. What gives?
edit: nevermind, I made it. Turns out you have to press them in order and release them in order. On to next step now.
cryptedvick said:
I made it to step 3 and even installed recovery cw 6.0.1.5 but I simply can't get into CWM ... It says I have to press volume up + power button for 10 seconds but if I do it just stays at the samsung logo and when I release the buttons it boots the phone normally. If I keep pressing the buttons for, say 1 minute, it loops the samsung logo until I release them and it boots normally. What gives?
Click to expand...
Click to collapse
vol up+power buton for 10 seconds ( when see samsung after 2-3 sec you can release buttons)
So I have done it!
I am now running ICS but I have a problem with the camera.
The video recording quality is horribleeee. With inside lighting it lags like hell. It used to run flawless before with 2.3.6 and with great quality. Now its completely horrible. This alone might make me to go back.... Is there any fix??
I have selected 480p then back to 720p and now it works just like on 2.3.6 ... man this thing still has a lot of bugs
It seems like the camera doesn't work like on GB.
In low light condition the video quality is horrible. MUCH worse than on latest GB.
Video bitrate is ~5mb compared to 12mb that I have on videos recorded before the flash.
I have tried with some apps (lgCamcorder, Camera ICS) and it either freezes or it lags like hell during recording (ala i8910 720p recording). I can't seem to find almost anything related to this except an old thread and a few mentions here and there but nothing taken seriously.
Is there any way to increase video bit rate? To at least make the vide quality like on GB?
in the future it will be fixed . as you see cm9 it's alpha. Congratulations :good:
P.S: you can try castagnaIT kernel
Laurentyu1995 said:
in the future it will be fixed . as you see cm9 it's alpha. Congratulations :good:
P.S: you can try castagnaIT kernel
Click to expand...
Click to collapse
It seems like theres a new version out. RC1 and on the changelog it says that it reverts latest Adreno libs for 720p. I wonder if that will do it.
Other than that, the phone runs pretty smoothly.
Also, I am running castagnalIT kernel 5.9 with my CPU going all the way up to 1804Mhz which is great! :good:
PS: salutari din Timisoara
edit: Just tried the RC1 version and now the camera is even worse!!! It skips horribly while recording in 720p. Even worse than the i8910 when it came out. It used to record soo nice with GB.....
Hi guys, I need help please!
I am using Samsung Note 3 SM-N9005 ARMv7 Lollipop 5.0. Rooted it with Kingoroot. "installed" TWRP through Flashify.
I downloaded Xposed Framework xposed-v86-sdk21-arm.zip onto my phone and installed it through TWRP in Flashify. Everything seemed fine, got the message install successful, I selected "reboot" instead of "clear cache/dalvik". Phone went into reboot...Samsung Note 3...Samsung logo...and stuck there. I understand that it takes some time for first boot, and I waited, but almost an hour and its still showing the same screen. So I tried to power off the phone, but it restarted again and stuck in the same logo screen. I tried to go into recovery mode hoping to get TWRP to do a reset or something, but no TWRP! Was only given option of "volume up - continue(to odin mode)" and "volume down - cancel(restart phone)". No option for factory reset either. So i booted odin, and tried to flash openrecovery-twrp-2.6.3.7-hlte.img.tar, got the messaged passed, phone rebooted and again stuck in Samsung logo. Tried recovery mode and still no TWRP! Please help!!:crying: :crying: :crying:
p.s. phone won't power off, only way to do it is to remove the battery.
Samsung phones stock ROMs need an special version of Xposed framework. Geez, it is on the official thread:
Known issues:
- Bootloops on Samsung stock ROMs. That's due to Samsung's changes to ART. There are unofficial builds that work around this by deodexing and adjusting the ROM.
Click to expand...
Click to collapse
Archy12 said:
Hi guys, I need help please!
I am using Samsung Note 3 SM-N9005 ARMv7. Rooted it with Kingoroot. "installed" TWRP through Flashify.
I downloaded Xposed Framework xposed-v86-sdk21-arm.zip onto my phone and installed it through TWRP in Flashify. Everything seemed fine, got the message install successful, I selected "reboot" instead of "clear cache/dalvik". Phone went into reboot...Samsung Note 3...Samsung logo...and stuck there. I understand that it takes some time for first boot, and I waited, but almost an hour and its still showing the same screen. So I tried to power off the phone, but it restarted again and stuck in the same logo screen. I tried to go into recovery mode hoping to get TWRP to do a reset or something, but no TWRP! Was only given option of "volume up - continue(to odin mode)" and "volume down - cancel(restart phone)". No option for factory reset either. So i booted odin, and tried to flash openrecovery-twrp-2.6.3.7-hlte.img.tar, got the messaged passed, phone rebooted and again stuck in Samsung logo. Tried recovery mode and still no TWRP! Please help!!:crying: :crying: :crying:
p.s. phone won't power off, only way to do it is to remove the battery.
Click to expand...
Click to collapse
When you flash TWRP, you have to have reset unchecked in Odin, when the flash finishes you pull the battery and then boot into recovery via button combo. If you don't do that TWRP doesn't stick. From there flash the Xposed uninstaller so you can boot properly.
Sent from my SCH-R220
io_gh0st said:
Samsung phones stock ROMs need an special version of Xposed framework. Geez, it is on the official thread:
Click to expand...
Click to collapse
Thank you for you reply. Yes, I understand that, which was why I have been trying to find the correct version. Did a few searches using my phone type and version and found a list of sdk21.zips...so i selected the latest version..
mattzeller said:
When you flash TWRP, you have to have reset unchecked in Odin, when the flash finishes you pull the battery and then boot into recovery via button combo. If you don't do that TWRP doesn't stick. From there flash the Xposed uninstaller so you can boot properly.
Sent from my SCH-R220
Click to expand...
Click to collapse
Thank you for your reply, I'll try that now.
mattzeller said:
When you flash TWRP, you have to have reset unchecked in Odin, when the flash finishes you pull the battery and then boot into recovery via button combo. If you don't do that TWRP doesn't stick. From there flash the Xposed uninstaller so you can boot properly.
Sent from my SCH-R220
Click to expand...
Click to collapse
I tried it, unchecked "reboot", flashed TWRP, power off. When I tried button combo, I can't boot into recovery. It either keep giving me the restarting loop (power on, samsung note 3..then power off, and on again..) or if i let go of the power button at note 3, it goes to the samsung logo and stuck there.
update: I kept trying, and finally got a little different response. I pressed volume up + home + power buttons, and got 3 small lines of colorful words...
Recovery booting
Recovery is not seandroid enforcing
Set warranty bit : recovery
and then the phone turns off and start again
Tried different combinations, so far only the volume up sequence showed something a little different.
Archy12 said:
I tried it, unchecked "reboot", flashed TWRP, power off. When I tried button combo, I can't boot into recovery. It either keep giving me the restarting loop (power on, samsung note 3..then power off, and on again..) or if i let go of the power button at note 3, it goes to the samsung logo and stuck there.
update: I kept trying, and finally got a little different response. I pressed volume up + home + power buttons, and got 3 small lines of colorful words...
Recovery booting
Recovery is not seandroid enforcing
Set warranty bit : recovery
and then the phone turns off and start again
Tried different combinations, so far only the volume up sequence showed something a little different.
Click to expand...
Click to collapse
If you your phone does not boot into TWRP right after you flash it it will not stick and you need to flash it again. To get into recovery is power+home+volume up
Sent from my SCH-R220
mattzeller said:
If you your phone does not boot into TWRP right after you flash it it will not stick and you need to flash it again. To get into recovery is power+home+volume up
Sent from my SCH-R220
Click to expand...
Click to collapse
Could it be the TWRP versions doesn't work on my phone?
I tried openrecovery-twrp-2.6.3.7-hlte.img.tar and also twrp-2.8.7.0-hlte-4.4.img.tar both getting the same results "recovery is not seandroid enforcing" when I pressed vol up + home + power
Archy12 said:
Could it be the TWRP versions doesn't work on my phone?
I tried openrecovery-twrp-2.6.3.7-hlte.img.tar and also twrp-2.8.7.0-hlte-4.4.img.tar both getting the same results "recovery is not seandroid enforcing" when I pressed vol up + home + power
Click to expand...
Click to collapse
That is ok, you get that when you have modified system/recovery. Means your are not fully stock. If you had full stock unrooted unmodified system and recovery that goes away, nothing to worry about. If you are still having problems follow these step exactly:
1) Pull battery out of phone then put it back in
2) boot to download mode (power+home+volume down)
3) open Odin on computer (run as admin)
4) plug phone into computer
5) Uncheck a. Reboot and f. Reset time in Odin
6) flash TWRP (TWRP.img file goes in AP)
7) after successful flash unplug phone and pull battery
8) put battery back in and boot directly to recovery (power+home+volume up)
If you let it boot normally without going into TWRP first, it does not stick
Sent from my SCH-R220
mattzeller said:
That is ok, you get that when you have modified system/recovery. Means your are not fully stock. If you had full stock unrooted unmodified system and recovery that goes away, nothing to worry about. If you are still having problems follow these step exactly:
1) Pull battery out of phone then put it back in
2) boot to download mode (power+home+volume down)
3) open Odin on computer (run as admin)
4) plug phone into computer
5) Uncheck a. Reboot and f. Reset time in Odin
6) flash TWRP (TWRP.img file goes in AP)
7) after successful flash unplug phone and pull battery
8) put battery back in and boot directly to recovery (power+home+volume up)
If you let it boot normally without going into TWRP first, it does not stick
Sent from my SCH-R220
Click to expand...
Click to collapse
Thank you very much!!! I am finally able to boot into TWRP and did a restore, now my phone is back on!! Strange though, I was doing exactly those steps earlier but not successful. Anyways, Thank you very much!! <3
Oh, since I'm here, can you give me advise on which version xposed framework I should get? (Although I don't think my phone is touchwiz, is there a way to find out/confirm? I'm a noob as you can see)
Archy12 said:
Thank you very much!!! I finally able to boot into TWRP and did a restore, now my phone is back on!! Strange though, I was doing exactly those steps earlier but not successful. Anyways, Thank you very much!! <3
Oh, since I'm here, can you give me advise on which version framework I should get? (Although I don't think my phone is touchwiz, is there a way to find out? I'm a noob as you can see)
Click to expand...
Click to collapse
Ok, now that TWRP is on there things should be easier. You are on Stock ROM, it is TouchWiz. You will need to flash a custom ROM that is deodexed. If you like the stock look, feel, and options look in the threads for your device for a stock deodexed ROM. Or you can flash CM. Depending on what version of Android you decide to run will dictate which version of Xposed you install.
Sent from my SCH-R220
I am getting a note3 and wanted to install xposed on it. the phone is running 4.3. with that version there is no need for flashing correct? simply download apk and install?
mattzeller said:
Ok, now that TWRP is on there things should be easier. You are on Stock ROM, it is TouchWiz. You will need to flash a custom ROM that is deodexed. If you like the stock look, feel, and options look in the threads for your device for a stock deodexed ROM. Or you can flash CM. Depending on what version of Android you decide to run will dictate which version of Xposed you install.
Sent from my SCH-R220
Click to expand...
Click to collapse
I am quite used to the look and functionity of the current version I am using...which is lollipop 5.0. My phone is Samsung Note 3 SM-N9005 ARMv7 international Qualcomm. I'll need to flash custom ROM and then get a "matching" xposed framework,correct? Could you please direct me as to how to get xposed framework to work please?
Archy12 said:
I am quite used to the look and functionity of the current version I am using...which is lollipop 5.0. My phone is Samsung Note 3 SM-N9005 ARMv7 international Qualcomm. I'll need to flash custom ROM and then get a "matching" xposed framework,correct? Could you please direct me as to how to get xposed framework to work please?
Click to expand...
Click to collapse
Just go to the threads for your device and flash a TouchWiz based deodexed ROM
Sent from my SCH-R220
---------- Post added at 07:41 AM ---------- Previous post was at 07:38 AM ----------
trulosdoulos said:
I am getting a note3 and wanted to install xposed on it. the phone is running 4.3. with that version there is no need for flashing correct? simply download apk and install?
Click to expand...
Click to collapse
Correct, you would need this one:
http://dl-xda.xposed.info/modules/de.robv.android.xposed.installer_v33_36570c.apk
Sent from my SCH-R220
There is now an Xposed framework package supporting Stock (odexed) TouchWiz ROMS: http://forum.xda-developers.com/showpost.php?p=65373013&postcount=3960
I am currently stuck for 45+ minutes at the google reboot splashscreen (4 colorful spinning dots that eventually should turn into the word android once reboot is complete).
I followed an update procedure that I have used many times (last done November 16), although some of the files involved are somewhat old.
Starting from November 16 update for Marshmallow:
1 - Fastboot-Flashed that March 2017 factory image for Marshmallow (yes, there is still a Marshmallow... I dont' want Nougat yet). Flashed all partitions except data and recovery.
2 - Reboot directly into TWRP (I believe it is TWRP 3.0.2... I haven'te changed it recently)
3 - In TWRP: Flash superuser BETA-SuperSU-v2.65-20151226141550 i
4 - In TWRP: Clear space from app/system by deleting foreign language directories (to make room for xposed)
5 - IN TWRP: Flash xposed xposed-v79-sdk23-arm
6 - In TWRP - initiate reboot to system.
7 - As system rebooted, I entered my PIN.
That's where I am now. Note I never saw a screen for "optimizing apps" that was expected. I
Note I never rebooted to android system, so I'm not sure which step caused the problem (it was a method I developed to update quicker although in retrospect rebooting each step to check would be smarter).
I have some ideas of what to do eventually: (retry my flash one step at a time)
BUT, I don't know how to do anything with a phone that is stuck on the splashscreen:
* It does not respond to key combination on/volume-down (which normally goes to fastboot)
* When plugged into pc, it does not respond to fastboot devices
* There is no battery pull option on this phone.
What to do next to get control of my phone... let the battery run out on the splash screen?
Hmmm. Weird. Just held power-on and vol-down and it took me briefly to a different screen (android?) and then promprted for PIN, then back to splashscreen.
I kept pressing that combo and eventually did get into fastboot.
Now I'll flash again.
electricpete1 said:
I kept pressing that combo and eventually did get into fastboot.
Now I'll flash again.
Click to expand...
Click to collapse
Hello. Not sure what caused your problem. Also, i don't use Xposed...
Just a heads up... Your SuperSU is really really old. Just use this one:
https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip
Good luck...
The version of SuperSU he used likely was the cause of the bootloop.
5.1 said:
Hello. Not sure what caused your problem. Also, i don't use Xposed...
Just a heads up... Your SuperSU is really really old. Just use this one:
https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip
Good luck...
Click to expand...
Click to collapse
I reflashed the system and then flashed newer files:
SR3-SuperSU-v2.79-SR3-20170114223742.zip
xposed-v87-sdk23-arm
(with a reboot between flashing SU and flashing xposed).
Everything booted up fine.
Problem solved.
Thanks for the help!
Aren't you supposed to fastboot boot, not flash the su with marshmallow?