I made this for my own use, after getting annoyed with laggy browser using XXKG1. I like the stock browser, and wanted to "fix" it.
Thanks LeoMar75, I used your odexed files
Flash via CWM.
http://www.multiupload.com/ZNCSCHO5F1
Enjoy!
~Rawat
NOTE: this will NOT work if you use a mod that has made changes to some of your framework files. e.g. madmack.
As always, do a nandroid before flashing.
Reserving this.
Is this basically just an odexed browser? What other files does it touch?
Sent from my GT-I9100 using XDA Premium App
Odexed browser and framework files. Apart from that, it wipes cache. That's it.
So this will overwrite anything that touches the framework like battery mods?
It's a shame there isn't an easier way to do mods than buggering around with the apk's
Thanks for the info!
Sent from my GT-I9100 using XDA Premium App
You can actually open up the zip, and delete framework-res.apk from the framework folder, and then apply it, and your battery mod will stay
And will it still work? This is on a deodexed rom.
Sent from my GT-I9100 using XDA Premium App
Tried it with lite pro rom v2.2 and it got stuck on first boot logo.. Fortunately i did a nandroid backup first :/
I'm playing around with this as we speak.
VR 2.0 LITE.
So .. first problem I encountered: browser always crashed when I start it up BUT it does work with some kinks. Witch I think I can solve.
So how does it work? Well I am a arstechnica reader. In pulse rss reader (if not a subscriber to ars) you get a few lines from the artikel with a button to read the rest of the artikel in the browser. If you press it, you stay in Pulse reader but the engine of the browser is used to display the artikel at it's correct url.
The engine (with all it's hw-acc glory) works. As in: I can browse the page on ars, the comments, even with video's no problem. No laggy **** what so ever.
But ... the frameworks screws **** up a bit. (I think ) So I tried flashing back my old frameworks ... but it didn't work I screwed up my phone
So as we speak I'm reflashing vr2.0 lite.
So what I'll be trying is flashing JUST the browser part (without the frameworks). Lets see if that helps.
Which files does the browser need to work btw? As in: what files should I keep from frameworks? Or is it possible to just delete the whole frameworks folder?
I don't know what happened here! I took my risk and tried to flash it on cognition rom...I delete first framework apk and when I flashed I got an error E: bla bla bla message..I reboot and....no lag at the browser? I don't get it really I don't! Thanks anyway!
Sent from Galaxy!
veyka said:
And will it still work? This is on a deodexed rom.
Sent from my GT-I9100 using XDA Premium App
Click to expand...
Click to collapse
Yes. Do a nandroid before hand to be sure
@people having problems with FCs. Not sure why you'd be having that problem, I didn't have any ._.
I'd suggest wiping dalvik and cache and updating if you still get FCs.
many issues with android can be related to caching mechanism...
My script *should* be wiping it anyway.
For myself, I did it manually.
Hey Rawat, I have always been under the impression that mixing odex and dex was not a good idea and has caused problems before when I was working on sgs roms.
Care to give any insight as to how this is not breaking everything? Very curious as I really don't want to load my rom with dolphin browser.
tonysac said:
I don't know what happened here! I took my risk and tried to flash it on cognition rom...I delete first framework apk and when I flashed I got an error E: bla bla bla message..I reboot and....no lag at the browser? I don't get it really I don't! Thanks
Click to expand...
Click to collapse
Confirmed, this works on Cognition 1.13!
designgears said:
Hey Rawat, I have always been under the impression that mixing odex and dex was not a good idea and has caused problems before when I was working on sgs roms.
Care to give any insight as to how this is not breaking everything? Very curious as I really don't want to load my rom with dolphin browser.
Click to expand...
Click to collapse
From http://www.netmite.com/android/mydroid/dalvik/docs/dexopt.html:
There are at least three different ways to create a "prepared" DEX file, sometimes known as "ODEX" (for Optimized DEX):
The VM does it "just in time". The output goes into a special dalvik-cache directory. This works on the desktop and engineering-only device builds where the permissions on the dalvik-cache directory are not restricted. On production devices, this is not allowed.
Click to expand...
Click to collapse
So, if I understand correctly the odexed file is optimized, but you don't _need_ to have it as the OS will take care of it with some added CPU cycles (which we have enough to go around ) and swap it out to cache. But having the pre-odexed code would do no harm - as I take it - as it is preferred in terms of CPU time, but not necessary. By deodexing firmware you're not taking the odex interpreting code out, just taking out the odex itself. Please correct any ignorance in my thoughts, but I don't really see why you couldn't mix and match.
Am I making any sense at this hour with my medication?
on VR2.0, flashed via CWM and it does not say its done? it just reboots itself to ROM.. the app is there, but FCs after a few sec.. tried deleting framework res, clear cache and dalvik too.. if any VR2.0 user managed to use it flawless, do share how did u managed to
Hmm, taking out the framework apk didn't allow the browser to work unfortunately.. Android loads fine, but the browser force closes as soon as I attempt to scroll a webpage.. Looks like this will only work with an unmodded framework apk like you mentioned.
Sent from my SGS2
So i have been toying around with getting this to work on VR2.0 lite ... but as my earlier post (#9) said .. something is screwing the browser app up.
The engine runs pretty sweet. In multiple apps that use the browser engine to display content on the web everything works fine.
But the browser fc every time I scroll a page.
I read in some post that mixing odex & deodex stuff in the rom is not appreciated by the os. So it could be just a known thing I'm diving into. (I need a second phone to start experimenting since I really don't want to brik my phone)
So .. until I have time and the patience to actually learn how this works under the hood .. I have bad news
Related
Hey guys I've been using my trusty htc Hero for about 2 years now and lately I've been noticing it's no longer what it quite used to be..
That being that it doesn't run smoothly the latest apps and can't perform some simple tasks decently enough for that matter.
Also, a very important thing is that all the latest ROMs are heavily loaded with apps I just don't need. What I want is a very lightweight ROM with only the essential apps installed on it so that I would be able to customize it exactly the way I want.
I once tried to manually modify a ROM with a kitchen, but it's too much hassle and for some reason the ROM kept crashing and lagging.
Please suggest some lightweight ROM (2.1 or higher preferable) that only has the most essential stuff in it.
Thanks so much in advance!!
Open the zip of the Rom you want, delete apks you don't want in system - app then sign it (i use autosigner) voila you have a light Rom
Sent from my HTC Hero using XDA App
you can do that ^
Or you install rootexplorer on your phone, browse to "/system/app/" and delete everything you don't need. Then reboot the phone, and wipe cache and dalvik. (not needed, just in case)
It's basically the same, just.. another method ^^
ybinnenweg said:
you can do that ^
Or you install rootexplorer on your phone, browse to "/system/app/" and delete everything you don't need. Then reboot the phone, and wipe cache and dalvik. (not needed, just in case)
It's basically the same, just.. another method ^^
Click to expand...
Click to collapse
Yep, its what I do, I use ESFile Explorer and delete everything I do not need, including the launcher and the standard SMS app to replace them with my personal choices. I am running Elelinux Speedmachine 4 and applied the changes I mentioned now and it runs smooth as hell, no crashes, no problems whatsoever.
Because of the Cyanogen Mod I do not even need SetCPU anymore.
The autosigning for me somehow never really worked, thats why I went to this method.
I would however like a very basic rom where only the real necessary stuff is installed and you can custom install what you want on top of it then...
[MOD][9/14/11][FIXED] GB Touchwiz (Stock/PW) Camera v1.0: Power Button->Shutter Key
[SIZE=+1]EDIT (9/14): I've had the wrong link posted for days, but it's now corrected. Sorry about that! If you had trouble with force closes, please re-download and replace the file. (I had the froyo version posted instead of the gingerbread version, doh!)
[/SIZE]Current Functionality over stock Camera.apk:
Settings menu option to enable/disable GPS tagging for pictures (ported from EH09)
Power Button in Camera mode becomes functionally the same as the touchscreen Shutter Key
[SIZE=+1]GB Touchwiz Camera Mod v1.0 - APK version[/SIZE]
Camera.apk - Download @ MediaFire.com
Installation: Since this is a system app, it cannot be installed using the Package Installer. Camera.apk must replace /system/app/Camera.apk. You can accomplish this many different ways. Two common methods are: 1) use ADB to push it ("adb push Camera.apk /system/app/Camera.apk"); or 2) copy Camera.apk to your SD card, then use a program like Root Explorer to move it to "/system/app/". If you are running a Stock GB rom, you will want to delete any camera.odex files in /system/app/, clear dalvik cache and reboot. For most deodexed roms, a reboot is only necessary if the camera is not working correctly after installation.For more information, feel free to read through the Froyo camera mod thread.
[SIZE=+1]
I have tested this on my phone with PWGB Version 2.0 (Beta 3). Please use at your own risk, and please post any successes, failures, bugs, feature request, etc. Also, please post what ROM you are using.
The more feedback I receive, the more likely I will continue this project with new features, CWM files, updated camera files, etc.[/SIZE]
Also, since I'm currently broke and looking for a job, donations might tempt me into spending more time around here . Let me know if there is anything that needs hackin'!
Would this functionality be possible for the miui camera?
Fascinatemtd MIUI 1.9.2
Joshuaboyzn said:
Would this functionality be possible for the miui camera?
Fascinatemtd MIUI 1.9.2
Click to expand...
Click to collapse
I'm sure it would be. Of course, they actually have the source code for MIUI, so they wouldn't need to do byte-code hacking in order to accomplish it.
I would try the MIUI.us forums. Maybe someone would be able to point you in the right direction. Maybe it's already been done...
good to see ya again gizmodroid!
nitsuj17 said:
good to see ya again gizmodroid!
Click to expand...
Click to collapse
Thanks man, I've been trying to get back here for months. Pesky "life" has foiled my plans...
Copied over the top of my camera.apk file using root explorer. Rebooted and wiped Davlik. Now shortcut is missing so I tried to readd it and it is missing from the app list. My dumbass didn't rename the camera.apk file before copying the new one so I cannot restore original. Any quick suggestions?
Sent from my SCH-I500 using XDA Premium App
What rom are you using?
CM 7.1 7/17 I can pull the camera.apk from the rom, just being lazy and hoping there is an easy fix.
Sent from my SCH-I500 using XDA Premium App
Haha, nope, that's the easiest fix.
This camera relies on the touchwiz libraries which are only found on Samsung based roms. It won't work on CM7/MIUI/ASOP roms.
Haha I figured. Me dumbass.
I swore my camera had the button feature, but it was not working lastnight. Guess I will restore the file from my rom.
Sent from my SCH-I500 using XDA Premium App
ED05 report...
Working perfectly with PowerWash V1.2, GeeWiz v1.1 Kernel, CFQ and OC'ed to 1.4GHz.
Thanks for the feedback!
beray5 said:
Working perfectly with PowerWash V1.2, GeeWiz v1.1 Kernel, CFQ and OC'ed to 1.4GHz.
Click to expand...
Click to collapse
Actually, that's interesting. Powerwash v1.2 was Froyo based. I never considered that the app might be compatible with Gingerbread and Froyo roms.
I guess I didn't need to open a new thread... hmm. Well, maybe I'll do some rearranging sometime soon.
EDIT (9/14): No wonder it worked, I had the froyo version linked! Whoops!
Im running PWGB v2.0 b3 and i just installed this and everytime i go to take a pic either with power button or on screen the flash just goes off then i get a force close message:
The application Camera (process com.sec.android.app.camera) has stopped unexpectedly. Please try again
Any ideas?
If not could someone please post the stock camera apk so i dont have to redo all over again.
Thanks
Interesting... that's the rom I used when developing this hack.
How did you install the camera.apk?
The stock camera can be pulled out of the powerwash rom. Or I can upload it later when I'm at the computer.
GizmoDroid said:
I'm sure it would be. Of course, they actually have the source code for MIUI, so they wouldn't need to do byte-code hacking in order to accomplish it.
I would try the MIUI.us forums. Maybe someone would be able to point you in the right direction. Maybe it's already been done...
Click to expand...
Click to collapse
Gizmo, i have tried on the miui forums, doesn't seem like there is anything yet. How likely would you be to do a aosp/miui version? I'd be happy to donate.
OK, I look into it in the next couple days. I am working on an old computer so I doubt I'll be building it from source, but I might be able to work up a quick hack.
GizmoDroid said:
Interesting... that's the rom I used when developing this hack.
How did you install the camera.apk?
The stock camera can be pulled out of the powerwash rom. Or I can upload it later when I'm at the computer.
Click to expand...
Click to collapse
Thanks for the quick reply!
I installed by placing on SD Card and then using Root Explorer to replace in system/app
I tried to extract the camera apk but the file is a .tar odin file and i couldnt find an "app" folder anywhere in it.
I tried the camera.apk from ComRom GB and it works half the time.
One thing i did do after flashing PWGB Rom was run the permissions.zip from the op because i was having problems with Google Maps..wonder if that has anything to do with it....
briguyy said:
Thanks for the quick reply!
I installed by placing on SD Card and then using Root Explorer to replace in system/app
I tried to extract the camera apk but the file is a .tar odin file and i couldnt find an "app" folder anywhere in it.
I tried the camera.apk from ComRom GB and it works half the time.
One thing i did do after flashing PWGB Rom was run the permissions.zip from the op because i was having problems with Google Maps..wonder if that has anything to do with it....
Click to expand...
Click to collapse
Hmm, that should have worked. I'd love to see a debug report or logcat from when it crashes, if you have the time and know-how.
Otherwise, here is the the stock, unmodified powerwash camera:
http://www.mediafire.com/?225yhhc8wrsh70m
GizmoDroid said:
Hmm, that should have worked. I'd love to see a debug report or logcat from when it crashes, if you have the time and know-how.
Otherwise, here is the the stock, unmodified powerwash camera:
http://www.mediafire.com/?225yhhc8wrsh70m
Click to expand...
Click to collapse
Thanks! Just before you posted i reflashed again thinking a fresh install would fix it. So i flashed, ran the permissions zip put in your apk and same thing, force close....i dont know how to create a logcat or debug but can research it.
Please politely direct me if this topic has its own section already but I couldn't find it easily.
I know this has been asked and answered somewhere in this forum but things get buried in forums that end up many with many pages of different specific questions all piled together ie in the 2.3.5 topics......
I have a general idea about Odex and Deodex roms.
Now my stock rom is an odex rom from my understanding and theming generally doesn't work because of the technical reasons behind the difference betweeen odex and deodex roms.
But is there a way to remove the vibration icon without going to a deodex rom? I rooted my phone but it doesn't seem so useful with the stock rom apart from being able do full backups.... Oh and being able to change the overglow effect and crt effect which are minor things for me.
I came from a long history with windows mobile which involved down the custom rom and ported roms path since i got fed up with the stock experience.
But I'm not at that stage with Android and quite content with the stock samsung/google experience with independent apps seeming to fix any annoyances I have experienced so far....
There is a mod in sicopat's Rom thread that will remove it for you. Here is the direct link to the download http://www.multiupload.com/DRXS2HIPZ7
You will need cwm to flash the file. If you don't have cwm, you can also unzip the file and drop the systemUI.odex file into system/app manually using root explorer or something similar then reboot the phone
Thankyou. I will give that a shot!
Well using cwm to install said everything went fine but on reboot nothing had changed.
And I cleared both lots of cache. Even tried twice.
But manually extracting and copying the file worked.
Not sure why but at least it worked.
Thanks again.
Sent from my GT-I9100 using XDA App
I think i can't use this Patch for the KI8...right?
can anybody please create it for the new KI8 Firmware?
Thanks
downset
I was surprised when I launched the new Samsung stock browser and it lacked flash support!! Well, shouldn't say surprised since this phone released with JB 4.2.2 which does not support flash... so not much support given in the thread of flash playing, just for getting it installed.
So, with root... I solved this issue and now so can you!
I used the files from from Nexus 7. As soon as we get something that is more for our device, I will change the source.
Requirements:
1) ROOT - http://forum.xda-developers.com/showthread.php?t=2252248
2) Grab the Browser - http://forum.xda-developers.com/attachment.php?attachmentid=1753139&d=1361590018 ( thanks to sikagoon7 - http://forum.xda-developers.com/showpost.php?p=38356096&postcount=354)
3) Grab ChromeBookmarkSyncAdapter if you want it - http://forum.xda-developers.com/attachment.php?attachmentid=1980058&d=1369154901
4) Grab the flash apk (current: 11.1.115.58) - http://helpx.adobe.com/flash-player/kb/archived-flash-player-versions.html
Steps to do:
1) Push the files to sdcard
2) Rename Browserproxyprovider files by adding .bak to end of the file name (or remove the file) in /system/app
3) Push Browser.apk to /system/app and change the file permission rw-r--r--
4) Push ChromeBookmarkSyncAdapter.apk to /system/app and change the file permission rw-r--r--
5) Install flash
6) Reboot (IMPORTANT: purpose of Browserproxyprovider is to block other browsers so AOSP will crash if you do not reboot after install)
7) Launch browser
If having issues, grab terminal emulator and clear dalvik cache and reboot
Code:
su
cd /data/dalvik-cache
rm *
reboot
Works great! Thanks. Glad I can still use the stock browser too!
Sent from my Galaxy S 4!
scoot05redss said:
Works great! Thanks. Glad I can still use the stock browser too!
Sent from my Galaxy S 4!
Click to expand...
Click to collapse
The only problem that I've noticed is that media bar is not showing up for me, so I can't go full screen or skip ahead. Let me know if you see this too.
I plan on trying out other sources for AOSP browsers this weekend. Just wanted to put a guide up for now.
nakedninja42 said:
The only problem that I've noticed is that media bar is not showing up for me, so I can't go full screen or skip ahead. Let me know if you see this too.
I plan on trying out other sources for AOSP browsers this weekend. Just wanted to put a guide up for now.
Click to expand...
Click to collapse
Same here. But not a biggie for me. Forward is an option in the menu. I like it.
Sent from my Galaxy S 4!
This is huge for me, thanks!!! I absolutely HATED the browsing experience from the stock browser and Chrome.
Big thanks!
Just got my s4 yesterday and this was a huge annoyance to me. Great post
Can I rename Browserproxyprovider back after I reboot?
ChronoReverse said:
Can I rename Browserproxyprovider back after I reboot?
Click to expand...
Click to collapse
Hit thanks instead of reply
You can certainly try and see what happens, as far as I know the purpose of the file is to block browsers (that's the behavior on my nexus 7). So it might crash the AOSP browser if it loads.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4 Beta
Okay tested. If you rename Browser.Provider.Proxy.apk back to normal AFTER you've confirmed Browser runs properly, it won't cause a crash.
Is this safe to delete altogether? Does anyone know what it does?
ChronoReverse said:
Okay tested. If you rename Browser.Provider.Proxy.apk back to normal AFTER you've confirmed Browser runs properly, it won't cause a crash.
Is this safe to delete altogether? Does anyone know what it does?
Click to expand...
Click to collapse
I have it removed on my devices. I haven't seen any repercussion yet in removing, only with it installed (AOSP browser not running). Afaik, the real purpose for the is just to be annoying not allowing for extra browsers in /system partition. :silly:
https://dl.dropboxusercontent.com/u/16473596/AOSP_Browser.zip
Okay, I've packaged up the bookmark adapter and browser into a flashable zip. It will also delete BrowserProviderProxy.apk (https://dl.dropboxusercontent.com/u/16473596/BrowserProviderProxy.apk is the backup of my copy).
Just to let you know this works excellent also!!
https://play.google.com/store/apps/details?id=de.mkrtchyan.aospinstaller&hl=es
Sent from my SGH-I337M using xda premium
In order to get proper reflow of text on doubleclick, I have resorted to using browser from my note 8 and while that crashes now on my phone on doubleclick and bookmarks, the third party app quick ics browser that uses it as a base, works flawlessly now.
JKAY DELUXE [I9300 JB 4.1.2]
Boat Browser, as well as Dolphin browser will do text reflow as well. So will my new favorite browser Sleipnir. The previous three browsers mentioned all use the old browser engine (non Chrome) that is still included with the stock rom.
I take it back, looks like smart reflow (doubleclick to reflow after pinch to zoom, without taking you back to overview) works with aosp as well. Apologies.
JKAY DELUXE [I9300 JB 4.1.2]
Updated OP with Chromesync for 4.2.2 and also a new Flash apk is available in the link provided in OP.
ChronoReverse said:
https://dl.dropboxusercontent.com/u/16473596/AOSP_Browser.zip
Okay, I've packaged up the bookmark adapter and browser into a flashable zip. It will also delete BrowserProviderProxy.apk (https://dl.dropboxusercontent.com/u/16473596/BrowserProviderProxy.apk is the backup of my copy).
Click to expand...
Click to collapse
So installing this new AOSP browser will still let me keep S4 stock browser??
It shouldn't remove it since it just adds the APK but no guarantees even if it kills your dog.
I gave the OP a "thanks". This stock browser works great per the instructions. I can once again sync my Bookmarks with Google and I now have Flash.
The stock browser in my I9505 was lagging on some sites with java scripts. Beside, while in full screen mode the navigation bar was not auto hiding.
This solved my problems. Thx.
It took nearly 24 hours to upload due to my dreadful internet connection but here it is, the latest Android version for the galaxy Mega I9200 AKA Kit Kat I9200XXUDNE4, repacked with a full Knox free bootloader.:good:
DISCLAIMER
I'm not responsible for anything, as usual procede only if you know what you do, and make a backup beforehands in case things go out of control.
This said since this ROM is Knox free you will be able to get back to 4.2.2 or to whatever ROM you want in case you don't like Kit Kat.
IMPORTANT
You can flash this ROM ONLY if you come from a non Knox Rom.
It means that if you were on a ROM that had Knox, like the latest 4.2.2 versions, you can't flash this ROM and in that case you'll have to go for the regular 4.4.2 Knox version available at sammobile.
BEFORE TO FLASH
Get a custom recovery, cuz this ROM comes without any recovery.
Why?
Because at the time I was testing it I kept my custom recovery to see if I could reuse it with Kit Kat, and since it worked, and since I don't want to loose again 24 hours to upload an other ROM with a recovery, you'll have to go like this.
There are plenty of custom recoveries on the forum, as for me I use that one:
http://forum.xda-developers.com/showthread.php?t=2415294
but you can use any one you like, it doesn't matter as long as it has been installed BEFORE to flash Kit Kat.
Edit
If for some reasons you want to stick to stock recovery head to post #5, I've attached it there with some instructions.
THE FLASH
Download the ROM, unrar it and you'll get a tar.md5 file.
Open ODIN 3.04, put the file in the PDA section.
On your phone, enter download mode (press volume down and start at the same time), then connect it to your computer.
Once it has been recognized by Odin (it gets blue on the left upper case) start the flash.
It will take approx 5 mns before it reboots, that's it.
If everything goes ok it will reboot twice and then it will enter the set up wizard.
It could be that some app forces close and that it reboots one more time, in that case you'll have to enter recovery and format /data (and since you have a custom recovery you can do so without erasing your sd card contents).
ROOT
Easy, download the latest SuperSU_1.94.zip from the master chainfire, flash it from recovery, reboot, voila.
REMOVING THE LAST KNOX TRACES:
This has to be done manually (I could have done it and repacked/uploaded a new pre rooted ROM with everything done but sorry, my connection is too slow )
There are some Knox apps in the /system/app folder and in the system/priv-app folder:
-the ones that have Knox in their name are easy to guess;
-one is called KLMSAgent and should be deleted as well, and so too ContainerAgent.apk, ContainerAgent.odex, ContainerEventsRelayManager.apk and ContainerEventsRelayManager.odex.
In the /system/lib folder delete libknoxdrawglfunction.so.
Delete completely the system/preloadedkiosk folder and the system/preloadedsso folder.
In data/data delete the com.sec.knox.seandroid folder and the com.sec.knox.store, and the other com.sec.knox whatever folders there are.
Enjoy!!!:silly:
Stay tuned, in the coming days I will put some mods here...
I already made a deodexed version but I don't think I will upload it since it takes too long (24 hours again), so if anyone with a better connection feels like doing it he or she is welcome!
THE LINK?
Here it is:cyclops::
https://mega.co.nz/#!6lhzGaab!zIFiED3APN7_lHAT5YRPbgJqb6lyrLZJwjs-gw9kLEQ
CREDITS
@SilviuMik for the tuto
@Chainfire for the root
@XDA for the opportunities it gives to all of us
Reserved, for some hopefully soon to come stuff
I'm guessing we can't jsut flash this in recovery, right?
unclefab said:
-cut-
Get a custom recovery, cuz this ROM comes without any recovery.
Why?
Because at the time I was testing it I kept my custom recovery to see if I could reuse it with Kit Kat, and since it worked, and since I don't want to loose again 24 hours to upload an other ROM with a recovery, you'll have to go like this.
-cut-
Click to expand...
Click to collapse
I expect you are ready for udate and version WITH recovery already started to upload? Please be serious of your work!
trurl3 said:
I expect you are ready for udate and version WITH recovery already started to upload? Please be serious of your work!
Click to expand...
Click to collapse
Yep, I have to be serious:cyclops: so here it is, I packed a stock recovery in case someone needs it for some reason (s).
It took (only) 15 mns to upload (not bad for a 10 mb file )...
Download the file, open Odin 3.04, put the file in PDA, flash, now you have KK's stock recovery, boooooo:laugh:
http://d-h.st/PGb
@bnb25
nope, you can't flash the ROM from recovery.
If some people are interested I can upload the deodexed version in the coming days when I have time, unless someone else does it before
I flashed somr stock rooted Rom awhile ago on the gf's phone. I been waiting on this update b4 doing anything. The phone acts up. Performance issues. She keeps ot close to full. Moving to sdcard doesn't work anymore. (That broke b4 filling the phone up. But didn't know that when we bought a 16gb sdcard.) So....thus has knox removed. You mentioned stock recovery as an option. You mean the stock kitkat recovery for the phone? Meaning that will introduce knox if you choose it? And if you do choose stock recovery with knox it can be rooted right? Just saying cause usually when first comes out it takes a lil time for someone to root it.
Sent from my SM-N900P using Tapatalk
i try this rom for 10 minutes and it keep restarting..
so i flash again with ODIN 3.04, and it keep restarting again..
i have wipe data and cache+dalvik, i use twrp recovery.
can you troubleshoot this problem?
thank you :good:
sorry for my bad english...
Works fine for me. I had latest official 4.2.2 rom; I then flash a custom recovery and a rooted rom before I flash this rom via odin. After flashing this rom, I wiped it factory reset. All is well for me. 24hrs now. Thumbs up me general.....
Sent from my GT-I9200 using XDA Premium 4 mobile app
@ninja_unmatched:
the recovery I attached is the stock KK recovery, and AFAIK it doesn't have Knox in it. About rooting a Knox cursed ROM, some people say it's easy but I don't have any personal experience on that matter.
But anyway, why don't you want to use a custom recovery?
I kept the CWM I had on 4.2.2, and after I upgraded to 4.4.2 it took me 2 minutes to root with Chainfire's SuperSu_1.94.zip...
So now I'm on Knox free KK, with custom recovery and root.
@congquer:
do a full factory reset and see if it helps.
@fpage:
nice to read that it works fine for you!:good:
@all:
if you are rooted and want to enable quad multi windows view (up to 4 apps opened at once on the same screen, fully resizable), check my thread in the themes and apps section..:
One of the best KK's new features cool:...
works like a charm, i've installed via odin, but lost root for some reason
Well the girl is like any other nooby internet user. She knows enough to get it infected over and over....lol. Knox actually helps a lil with that. I used to use my phone (Note 3) to check questionable sites out for clients. Knox would do its pop ups alerting me to there being something going on that I do not want. It has actually helped....weird thing sort of. Now of course it doesn't do that anymore but for her......it might lower my headaches if you know what I mean?
But...no I'm about to try it out now anyways after I backup her phone.
Sent from my SM-N900P using Tapatalk
It could be that some app forces close and that it reboots one more time, in that case you'll have to enter recovery and format /data
This step right here causes the same boot loop mentioned. An app forces closes just like you said. soon as you format /data after a reboot it goes into a boot loop. I am also using TWRP 2.7
You have to clear cache not data. Even with that alot of apps just force close.
Sent from my SM-N900P using Tapatalk
I am rooted and working like a charm. Quad window working and alot of modules via xposed installer.
Sent from my GT-I9200 using XDA Premium 4 mobile app
Well it didn't work for me. And the supersu only caused freezing then reboot. I just went and flashed stock. Maybe I'll root it later. The process also messed with the sdcard. Made it unreadable. So I used an app (Called Photorec) to recover some of the files from the 16gb sdcard she has.
Sent from my SM-N900P using Tapatalk
whenever I want to delete knox from system/app, it always failed to delete.
I wonder why?
@ninja_unmatched:
your girl seems to be like mine, willy to use the phone but messing it all the time, and then calling her man to fix it:cyclops:.
But you are worse tham me cuz you use her phone as a guinea pig!
The problem with SuperSu is that at first you can't install it a a system app.
In order to fix this you'll need either twrp recovery or aroma file manager ( http://forum.xda-developers.com/showthread.php?t=1646108 ) and do as follows:
-download SuperSu zip,
-extract the app from the zip but keep the zip intact,
-flash the SuperSu zip,
-do not reboot but go to your file system while still in recovery, either from the twrp menu or by flashing the aroma file manager file,
-delete SuperSu from the system/app folder,
-reboot,
-install the SuperSu apk manually as you would with any apk.
Now you are rooted, and your SuperSu being on your data/app folder it doesn't force close anymore.
Later you can convert SuperSu into a system app from the apk's settings.
But this force close is a problem on KK, cuz everytime an app FC (not only SuperSu) the phone reboots, pretty annoying and definitely a deal breaker for me.
The messing with the files is another problem, it's because somehow KK uses another format than JB. But this one is easy to overcome, just connect your phone to your computer and copy the files to it, or you can copy them from recovery/aroma file manager (that's what I did, at first I thought it was gone but nope, it's just a format stoy) to anywhere on your phone.
@fpage:
I'm happy for you if everything works:good:
@serpentlord:
salaam manis dari Jowo!:laugh:
Are you rooted? Sorry if the question sounds obvious, but if you are then deleting the Knox apks shouldn't be a problem.
Otherwise if it doesn't work, use aroma file manager (see above, and don't forget to push thanks for @amarullz our dev from Bandung!) and delete the Knox stuff from within recovery.
That said I went back to 4.2.2, this KK is plagued with bugs and I don't like the new multi windows implementation, so until they make a more stable version and until I find out whether I can implement some of JB's multi windows functions in it or not I'll stick to 4.2.2...
I'll make soon a thread about specific KK's bugs, hopefully sammy will listen but don't hold your breath
A guinea pig....lol. yeah. Only thing I ever did was flash a stock 4.2.2 rooted Rom. For wifi tethering purposes. It was fine for awhile. She starts complaining about it....I find she filled the thing up. Apps, apps, apps, mad games. I move some of the apps to the 8gb card. That helped. Later she fills it up again. I get a 16gb card and then find out it won't move anything to the card. Broke that somewhere after the 8gb card move. She goes on facebook and clicks on those questionable site posts and jave you sign up while giving them permission to post on your profile and all sorts if sites I find are questionable. That and apps from blackmart and from that site that offers hacked android games/apps.
So far now she seems fine on the stock official 4.4.2. It has a few widgets and apps in Russian. I've seen a few bugs that clear up on their own.
1. The lock screen took a bit to update. (What I mean is this. I know when playing music will say Milk it will show also on the lock screen. It wasn't doing that. Had to reboot to get that going.)
2. There is an app called Wish. It allows you to send something you think another person would be interested in that also has wish. That feature doesn't work to well. You can choose facebook or google+. FB no work at all. I think that is some other reason for that one. Google+ works but only if you choose the regular browser. Through chrome the page doesn't pop up woth the option to use the app to open the link.
And generally I've just run into these lil quarks that eventually just start working. Or partially work enough to get by.
Sent from my SM-N900P using Tapatalk
unclefab said:
salaam manis dari Jowo!:laugh:
Are you rooted? Sorry if the question sounds obvious, but if you are then deleting the Knox apks shouldn't be a problem.
Otherwise if it doesn't work, use aroma file manager (see above, and don't forget to push thanks for @amarullz our dev from Bandung!) and delete the Knox stuff from within recovery.
That said I went back to 4.2.2, this KK is plagued with bugs and I don't like the new multi windows implementation, so until they make a more stable version and until I find out whether I can implement some of JB's multi windows functions in it or not I'll stick to 4.2.2...
I'll make soon a thread about specific KK's bugs, hopefully sammy will listen but don't hold your breath
Click to expand...
Click to collapse
Salam manis dari Jakarta! :laugh:
Yes, my device is rooted. I've tried root browser, root explorer and soon. but it ends with the same result. I wonder why.
And my device also keep restarting every 10 minutes. Is it a bug?
@ninja_unmatched:
I can't tell about this wish.apk and widgets, at the time I was still on 4.4.2 I had stripped the Rom down to only about 20 system apps.
I allways do this on my ROMs cuz I don't like stock apps, I rather uninstall all that stuff and replace it by third part apps that are easier to manage and not so much on the spying/bloatware side...
@serpentlord:
what happens is probably that you have an app that forces closes, and this is what makes the phone reboot. I had the same problem and in my case it was youtube, in your case it could be any other app.
Just start your phone and keep an eye on it until it says "sorry app whatever has closed". Then if it reboots you know from wish app it comes and you can uninstall it and/or replace it with another app or another version from the same app.