I'm trying manually install 4.1.2 on my rooted Nexus 7 with CMW.
I downloaded the zip, placed it on my Nexus 7, proceeded regularly to install zip
i selected the zip and it aborted, says Status 7.
Thanks to the community below are solutions to get the update to flash.
EDIT
Thanks to Logic_
You can flash this .zip instead which disables all the checks but do it at your own risk as it can brick your tablet
https://www.dropbox.com/s/isqpvb0w26....1.2edited.zip
This is the update with the checks disabled. I didn't make this, got it off another forum, I just used it because I had moved an update to chrome into my /system and there was no easy way to revert it.
I wouldn't advise using this if you made build.prop modifications, but it is useful if your update is failing over some apps like google wallet.
Once again, I didn't make this and I'm not responsible if you for some reason use this to flash the update over some heavily modded rom
It's from JRO03D btw.
Click to expand...
Click to collapse
EDIT 2
osm0sis method to get the update to work is simpler and possibly risk free.
osm0sis said:
For those who've done some modding and can't remember what they did to pass the OTA asserts, all you need to do is dirty flash the system.img from 4.1.2 factory image in fastboot and eveything should work.
Click to expand...
Click to collapse
Did you try to redownload the zip?
Sent from my Nexus 7 using xda app-developers app
I got a similar error for build.prop file. I had changed it to enable/force auto rotation of the home screen when I was on 4.1.1. When I reverted the build.prop to its original file, it worked for me.
I see the error code is the same in your case as well. Is there a chance that you would have changed BrowserProviderProxy.apk?
mayoor_rao said:
I got a similar error for build.prop file. I had changed it to enable/force auto rotation of the home screen when I was on 4.1.1. When I reverted the build.prop to its original file, it worked for me.
I see the error code is the same in your case as well. Is there a chance that you would have changed BrowserProviderProxy.apk?
Click to expand...
Click to collapse
I didn't edit it which is weird, I don't think this matters but I did sideload aosp browser as I'm not a fan of chrome
Sent from my Nexus 7 using Tapatalk 2
Sebianoti said:
I didn't edit it which is weird, I don't think this matters but I did sideload aosp browser as I'm not a fan of chrome
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
It's from the side loading of the browser. I had this too. You have to restore those mentioned browser proxy file(s) to their original state. I also temporarily removed the browser apk from the system/app folder as well, although I'm not sure if this was required. The update installed fine after doing this.
Sent from my Nexus 7 using XDA Premium HD app
nyijedi said:
It's from the side loading of the browser. I had this too. You have to restore those mentioned browser proxy file(s) to their original state. I also temporarily removed the browser apk from the system/app folder as well, although I'm not sure if this was required. The update installed fine after doing this.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Oh okay, how would I restore those files to their original state though?
Sent from my Nexus 7 using Tapatalk 2
I'm having the same problem. I cannot seem to flash the update with CWM. I haven't edited any of the system files or anything like that. Is it the fact that I'm using a different launcher that's causing the problem?
Sebianoti said:
Oh okay, how would I restore those files to their original state though?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I'd like to know too. I get the Build.prop error too.
You've made no changes whatsoever? What about the kernel? Worst case just use mskip's toolkit to flash back to stock 4.1.1. Check the lag thread I posted what I did and it worked like butter.
Sent from my Nexus 7 using xda premium
Hi all.....
I'm currently using stock Nexus 7 and did all ways possible here to update and nothing worked, last thing I did was go to setting, backup and restore and hit factory data reset and buala automatically got the update to 4.1.2
Nota: this is not a recommendation but if u wanna try do a Backup and good luck.
Sent from my Nexus 7 using xda premium
I deleted the original browser files in the system/app folder too.
Found them on the rootwiki site here....
http://rootzwiki.com/topic/35089-can-someone-hook-me-up-with-browserproviderproxyapk/
Worked perfectly after
modded build.prob / update problems to 4.1.2
i have similar Problem
Picture
h**p://i49.tinypic.com/w979qt.jpg
i modded my build.prob to Landsape mode. I guess that i corrupt the Md5 hash
(deleting the row with the added contend didnt solve it....)
I tried a factory reste and an Temp Wipe in clockwork. I thought this should solve the problem but i l get the sam error ....
What should i do ?
Flash a facotory Image ?
How do i get back my root, if the factory image is my only option?
Thanks a lot for your help
greets Razzor
I also had the same problem then remembered that I use FullScreenToggle to get rid of the nav bar. I just had to re-enable it and it installed fine.
If you are getting the error on 'build.prop' look in the /System folder with Root Explorer or the ES explorer. If you see a build.prop.bak, that is probably your original file. Rename build.prop to something else and rename build.prop.bak to build.prop. Restart and then try taking the update again.
If you side-loaded the gnex browser so you could use flash, go to the /System/App folder and make sure you have BrowserProviderProxy.apk and BrowserProviderProxy.odex named properly. As stated earlier, rename browser.apk to browser.apk.bak. Restart and then try taking the update again. I had that problem. After getting the OTA installed, I renamed the browserproviderproxy files again, and made it browser bak file browser.apk. Now I have flash working perfectly again on the gnex stock browser.
Okay i managed to fix the browser proxy thing, turns out i had 10.apk at the end of it for some reason
and i renamed browser.apk to browser.apk.bak so that worked,
but now i got the same problem but with wallet
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I remember having to jack around with Wallet to get the original update which allowed other credit/debit cards to be added. Some offered a solution where you could download a modified wallet.apk that would work instead of going through the other hoops. If you did that, the apk probably doesn't pass the verification. If you used a modified Wallet.apk did you backup the original one first?
Groid said:
I remember having to jack around with Wallet to get the original update which allowed other credit/debit cards to be added. Some offered a solution where you could download a modified wallet.apk that would work instead of going through the other hoops. If you did that, the apk probably doesn't pass the verification. If you used a modified Wallet.apk did you backup the original one first?
Click to expand...
Click to collapse
I didn't, and i did use a modified APK, but i deleted that, then i downloaded an original but still not working
build.prob error
Fixing steps for build.prob error :
VERY IMPORTANT: You will los all of your data, please make a backup befor you following this stepps ^^
Error Message apply_patch_check("/system/build.prob - "Numbers" , "Numbers")
My way which worked for me
1.)
The only way, if you dont have any backup of the original build prob file youl have to flash a copy of the factory IMAGE.
In my case i used the Nexus Toolkit 3.2 V - with this marvelous tool I copied the Factory Image 4.1.1 on it
2.)
After the factory Image you will lose your root. Install Clockwork or a other custom recovery image. Then its easy too get back your root with the Toolkit (follow the steps)
3.) If your not able to receve the OTA update to 4.1.2, download it and copy the ZIP to your Nexus 7
After this, go back to Fastboot and install the Updates using the up an down Volium buttons to navigate
Now the updating process should go very smooth
greets Razzor
I have the same error when installing from CWM and the ONLY CHANGES I made to my N7 are:
- Unlock
- Root
- CWM
- Battery Icon
Any other ideas? Will installing from ADB and Android own Recovery will work?
EDIT: I tried the update on my SECOND N7, which have all the above EXCEPT the battery icon mod and it works. So looks like the battery icon mod is the issue! Anyone know how to revert back to the original battery icon?
Also, since the first update failed, when I clicked on "Check" under SYstem Update, now my N7 said the system is up to date. How do I force the update to run again?
The system checks are there for a reason and I am in no way responsible if anyone bricks their device with this but...
https://www.dropbox.com/s/isqpvb0w26kqjdx/4.1.2edited.zip
This is the update with the checks disabled. I didn't make this, got it off another forum, I just used it because I had moved an update to chrome into my /system and there was no easy way to revert it.
I wouldn't advise using this if you made build.prop modifications, but it is useful if your update is failing over some apps like google wallet.
Once again, I didn't make this and I'm not responsible if you for some reason use this to flash the update over some heavily modded rom
It's from JRO03D btw.
Related
For those of you who may not have taken kindly to Asus' skinning of our beloved Honeycomb OS, you will be happy to know that it's possible to change some aspects of the UI to make it look more "stock". The most notable change that Asus has made, was with the replacement of the stock Honeycomb navigation keys with icons that seem less sleek and frankly, just don't flow with the holographic theme of the OS.
To combat Asus' lack of taste, it's possible, with some hackery, to get the stock navigation icons that you would find on the Motorola Xoom. If you are at all confused of what icons I am speaking of, it's the back, home and multitasking icon located at the bottom left of the screen; they will be changed to look like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
While I do enjoy the custom Asus widgets that were included in the Transformer, I would much rather prefer the navigation buttons native to a stock Honeycomb OS. I am always "pro-vanilla" when it comes to Android because system updates will most likely be pushed out faster to the user if the manufacturer didn't have to waste more time putting in their little touches to the user interface-I digress.
The procedure is simple but it does require you HAVE ROOT! The easiest way, believe it or not, is to use ADB and the command prompt to effectively change the necessary files. You can install ADB from the official Android development site:
http://developer.android.com
For your convenience, I have already made a backup of the file you will be replacing (see the end of the article) such that, if you ever need to revert to the "stock" Asus theme, then you just need to download the file and use the same procedure below.
Lets get started! All credit goes to XDA member JaiaV. I am simply making a how-to & we are not responsible if you brick your device.
1) Download this file if you are on Android 3.0.1:
Modified SystemUI.apk
Download this file if you are on Android 3.1:
http://dl.dropbox.com/u/2993232/modified/3.1/SystemUI.apk
Prime 1.4
http://db.tt/UI10NAk
Thanks Andrew2511
thanks xformulax
Put this file inside the folder that contains the adb.exe (probably quicker if you just search for it using the native Windows search tool). If you are using the newest version of the developer tools then the folder that contains the ADB.exe should be called "Platform-tools"; put the file in the Platform-tools folder. This way, when you run the ADB command below, the system will know where the file you just downloaded is, which makes everyone's life easier.
2) Enable USB Debugging on your tablet by going into your settings > Applications > Development
3) Plug your Transformer into your Windows machine
4) Launch up your command prompt
5) **REMEMBER, YOU NEED TO HAVE ADB INSTALLED PRIOR TO DOING THIS**
Type in:
Code:
adb devices
you should see your device connected. It should look like this:
6) Once you know your device is connected properly, type in:
Code:
adb remount
7) Next, you just have to type in:
Code:
adb push SystemUI.apk /system/app
8 ) Lastly, to reboot your system quickly, type in:
Code:
adb reboot
If for some reason you would like to go back to stock, its pretty simple. All you have to do is download the file below:
For 3.0.1:
Stock SystemUI.apk
For 3.1:
http://db.tt/eQkoYIk
Then just repeat the procedure above (starting from number 6) and you are all set to go! Just a quick way to make your Asus Transformer look just a bit more awesome!
perhaps this should be in themes...
Sent from my Transformer
www.AsusTransform.com
www.AsusTransform.com/forum
xda doesnt support html.
my mistake, rushed it. fixed
It's pretty easy to do this for yourself for w/e version of the FW you happen to be using. Just adb pull your SystemUI.apk, open it up in your favorite zip/rar application, navigate to the /res/drawable-mdpi folder, and backup the ic_sysbar_home/back/recent/menu images. Should be default/pressed for each. Then move the Xoom/stock images from my SystemUI.apk (made from a deodexed Prime 1.3 SystemUI.apk, thanks to Roach and DC13, I just changed the button images) or a stock Xoom rom into your SystemUI.apk, save. Then push your modded SystemUI.apk into /system/app and you're done.
If you use a rom you can also switch out the modded SystemUI.apk in the zip file you flash, that way if you have to reinstall (or before you install a new image) you don't have to manually move the apk in afterwards. I suggest using the SystemUI.apk that came with the FW version of the rom you're using, as there can be some inconsistencies between a few.
personally i like the icons asus made better, but i don't like that they're white. too bright compared to everything else on the dock.
luckily thats a quick fix once i finally root.
i can adb devices
can someone please help me. i can not get past "adb remount"
gives me an error: "remount failed: operation not permitted"
BBjaiBev said:
i can adb devices
can someone please help me. i can not get past "adb remount"
gives me an error: "remount failed: operation not permitted"
Click to expand...
Click to collapse
You need root.
this doesn't work on 3.1. Any chance of an update?
Sent from my Transformer TF101 using XDA Premium App
mattykellyuk said:
this doesn't work on 3.1. Any chance of an update?
Sent from my Transformer TF101 using XDA Premium App
Click to expand...
Click to collapse
I'd like them on 3.1 too...
djdevine2 said:
I'd like them on 3.1 too...
Click to expand...
Click to collapse
updated! enjoy.
neok44 said:
personally i like the icons asus made better, but i don't like that they're white. too bright compared to everything else on the dock.
luckily thats a quick fix once i finally root.
Click to expand...
Click to collapse
+1, not to harp on the OP, but the Asus Icons (even the Samsung TouchWiz Icons) are much more visually appealing and intuitive to me.
But that's a personal preference. This guide should be useful to anyone looking to make custom icons.
Yep, this thread shows quite nicely that nothing is right for everyone. Me, if there was one thing about the Transformer's styling I would change, it's the stock Google clock font. To me, it looks like cheap and amateurish, and the styling doesn't really fit or match anything else in the OS (other than perhaps the buttons that Asus changed.)
I hope in a future release, Google makes these things user-styleable. I'd much rather have a different font for the clock, which could make it instantly more readable while saving valuable screen space to boot.
But obviously other people are perfectly happy with it...
I flashed the Xoom ones which worked fine but I didn't like them to pushed the original ASUS ones back, however SystemUI.apk force closes constantly and I have lost the status bar. I'm on 3.1 and used the right files.
djdevine2 said:
I flashed the Xoom ones which worked fine but I didn't like them to pushed the original ASUS ones back, however SystemUI.apk force closes constantly and I have lost the status bar. I'm on 3.1 and used the right files.
Click to expand...
Click to collapse
try pushing this file back. thats the original one for 3.1.
http://db.tt/eQkoYIk
ok will give it a shot!
Still force closing..... weird
djdevine2 said:
Still force closing..... weird
Click to expand...
Click to collapse
are you pushing it through adb? Can u try something like root explorer?
ayman07 said:
are you pushing it through adb? Can u try something like root explorer?
Click to expand...
Click to collapse
I've been using root explorer as don't have PC with me at the moment, weird that Xoom worked at first, don't worry too much about it, I'll try with ADB in morning. (It's 10:40 in UK)
djdevine2 said:
I've been using root explorer as don't have PC with me at the moment, weird that Xoom worked at first, don't worry too much about it, I'll try with ADB in morning. (It's 10:40 in UK)
Click to expand...
Click to collapse
make sure you check your permissions.
also, i just skimmed the guide, but i'd probably put a permissions change in the instructions just to ensure everyone has proper permissions on install.
not sure if anyone is interested, but i plan on taking the stock asus and changing just the colors to match honeycomb (versus changing the actual icons)
xformulax said:
make sure you check your permissions.
also, i just skimmed the guide, but i'd probably put a permissions change in the instructions just to ensure everyone has proper permissions on install.
not sure if anyone is interested, but i plan on taking the stock asus and changing just the colors to match honeycomb (versus changing the actual icons)
Click to expand...
Click to collapse
I use root explorer, after i moved it to system/app reboot and work fine.
It doesn't hurt to check permission though. rw,r,r
Edit: I just moved my original systemUI.apk back using root explorer and sems permission
Was changed. I set it to rw,r,r reboot and origin icons are back no FCs
Sent from my Transformer TF101 using Tapatalk
hi guys
Here is flashable zip to enable on screen buttons in hep-happy's CM9 build
i have resized the navigation bar height
before it was 48, now it is changed to 32.
zip is attached (onscreen_resized_32.zip)
(Last release as cm has already implemented this feaure)
For hephappys loveme
http://db.tt/m9Alm5PC
ScreenShots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Instructions :-
Reboot into recovery
backup your current rom (i.e. Nandroid backup)
flash ONSCREEN_RESIZED_32.zip (height = 32)
or
FLASH ENABLE_ONSCREENBUTTONS.zip (height = 48)
REBOOT and your done
NOTE -
If your doing a clean install then after flashing ROM reboot your phone then reboot into recovery again and then flash the zip or you'll get bootloops.
Credits
evilisto
Can't wait for this to be an option in CM settings...
How can I disable it?
_____________________
Swypnięte z LG-P500 przy użyciu Forum Runner
sQuAshPL said:
How can I disable it?
_____________________
Swypnięte z LG-P500 przy użyciu Forum Runner
Click to expand...
Click to collapse
Just flash
remove_onscreenbuttons.zip
Sent from my LG-P500 using XDA
vlt96 said:
Can't wait for this to be an option in CM settings...
Click to expand...
Click to collapse
Yea seriously
Sent from my LG-P500 using XDA
Isnt our phone a bit too small to also have onscreen buttons
Though even I would love to see this as an option in settings.
Thanks, my back button stopped working a couple months back. I couldn't enable softkeys on hephappy's build, so you saved my day!
But I believe it is too wide, it screwed a bit my homescreen. I read somewhere (don't remember, sorry) that it should be 36 pxls in height.
hope it helps
thanks!
pedrosa1 said:
Thanks, my back button stopped working a couple months back. I couldn't enable softkeys on hephappy's build, so you saved my day!
But I believe it is too wide, it screwed a bit my homescreen. I read somewhere (don't remember, sorry) that it should be 36 pxls in height.
hope it helps
thanks!
Click to expand...
Click to collapse
Lol sometimes my back button also doesn't work
Ok I'll try to change its height
Sent from my LG-P500 using XDA
rishabh22 said:
Isnt our phone a bit too small to also have onscreen buttons
Though even I would love to see this as an option in settings.
Click to expand...
Click to collapse
Many of us having buttons problem. So its good to have on screen buttons instead.
Sent from my LG-P500 using XDA
Yeah even I have a problem with the back button.
Does this work with lupo's test build?
Im getting bootloops :/
Edit
Im getting bootloop even on flashing the remove...zip :-(
Luckily I had manually backed up my own framework-res.apk. Can you please make a flashable zip for it(attached)?
rishabh22 said:
Yeah even I have a problem with the back button.
Does this work with lupo's test build?
Im getting bootloops :/
Edit
Im getting bootloop even on flashing the remove...zip :-(
Luckily I had manually backed up my own framework-res.apk. Can you please make a flashable zip for it(attached)?
Click to expand...
Click to collapse
I have tested it with hep-happy build so may it works with it only
Ok 2morow I'll give you the flashable zip
Sent from my LG-P500 using XDA
seriousia said:
I have tested it with hep-happy build so may it works with it only
Ok i'll give you flashable zip for framework you have attached 2morow.
Sent from my LG-P500 using XDA
Click to expand...
Click to collapse
Never mind that zip. I restored my framework-res using android commander(it lets u manipulate system files using pc) but it still wont boot
I had initially tried to replace the frameres app manually using root browser(first deleting the orig one after backing up) that might have caused the prob.
I am getting bootloops whatever I do
Why did I not backup my rom before trying this :'(
rishabh22 said:
Never mind that zip. I restored my framework-res using android commander(it lets u manipulate system files using pc) but it still wont boot
I had initially tried to replace the frameres app manually using root browser(first deleting the orig one after backing up) that might have caused the prob.
I am getting bootloops whatever I do
Why did I not backup my rom before trying this :'(
Click to expand...
Click to collapse
Which rom your using ?
Try to pull framework-res.apk from rom zip and push it in the system
Edit: did you changed the permission after pushing original framework.apk to system ?
Sent from my LG-P500 using XDA
seriousia said:
Which rom your using ?
Try to pull framework-res.apk from rom zip and push it in the system
Sent from my LG-P500 using XDA
Click to expand...
Click to collapse
Im using lupo's testing kang..
Let me explain the whole thing that happened...
1.I used root browser in rom manager to manually backup the framework-res.apk
2.I deleted the my orig framework-res.apk(yeah that was stupid)
3.The phone started giving me weird errors but root browser was still open.
4.When I tried to copy the framres from ur zip it gave me an error that the memory was full(and arnd half the file was copied).
5.I by mistake closed the root browser(I wanted to check storage from stock app manager).
After that nothing would open..opening any app would give an error.
6.I rebooted my phone but it got stuck at the lg screen.
7.I removed and reinserted the battery and booted into recovery.
8.Flashed your zip from recovery.
Thereafter my phone is getting stuck at bootloop whatever I do
rishabh22 said:
Im using lupo's testing kang..
Let me explain the whole thing that happened...
1.I used root browser in rom manager to manually backup the framework-res.apk
2.I deleted the my orig framework-res.apk(yeah that was stupid)
3.The phone started giving me weird errors but root browser was still open.
4.When I tried to copy the framres from ur zip it gave me an error that the memory was full(and arnd half the file was copied).
5.I by mistake closed the root browser(I wanted to check storage from stock app manager).
After that nothing would open..opening any app would give an error.
6.I rebooted my phone but it got stuck at the lg screen.
7.I removed and reinserted the battery and booted into recovery.
8.Flashed your zip from recovery.
Thereafter my phone is getting stuck at bootloop whatever I do
Click to expand...
Click to collapse
The framework.apk that you have attached is from lupo testing build ?
If yes then i can provide you flashable zip for it.
Sent from my LG-P500 using XDA
seriousia said:
The framework.apk that you have attached is from lupo testing build ?
If yes then i can provide you flashable zip for it.
Sent from my LG-P500 using XDA
Click to expand...
Click to collapse
Yes it is from lupo's. But I tried putting it with android commander from my pc.
Does it make a diff if it is a flashable zip?
rishabh22 said:
Yes it is from lupo's. But I tried putting it with android commander from my pc.
Does it make a diff if it is a flashable zip?
Click to expand...
Click to collapse
What about permission ?
Never used it so i dont know if have to set permission manually or not
Try fixing permission in recovery and then reboot
EDIT:
Okay here is you flashable zip
Try it and report please
http://qfs.mobi/f116517
Sent from my LG-P500 using XDA
seriousia said:
What about permission ?
Never used it so i dont know if have to set permission manually or not
Try fixing permission in recovery and then reboot
EDIT:
Okay here is you flashable zip
Try it and report please
http://qfs.mobi/f116517
Sent from my LG-P500 using XDA
Click to expand...
Click to collapse
Fixed permissions, wiped cache,dalvik...Still bootloop
Edit
Sorry hadn't refreshed the page so did not see ur zip.Will try and tell
---------- Post added at 01:16 AM ---------- Previous post was at 01:04 AM ----------
Um this is weird. Still bootlooping.
I guess something else got messed up during the time the framework was missing :/
rishabh22 said:
Fixed permissions, wiped cache,dalvik...Still bootloop
Edit
Sorry hadn't refreshed the page so did not see ur zip.Will try and tell
---------- Post added at 01:16 AM ---------- Previous post was at 01:04 AM ----------
Um this is weird. Still bootlooping.
I guess something else got messed up during the time the framework was missing :/
Click to expand...
Click to collapse
Hmm so you have to do a clean install now.
But before that make your nandroids backup with TWRP recovery
Then install the rom and then restore only /data from nandroid backup
In this way you wont lose any of your data, setting etc.
Sent from my LG-P500 using XDA
thank you very much for the patch, i had been really looking forward to it, but the buttons feel too big for our tiny screen. Do you think you can resize them?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Always do a backup!!For GT-N8013 Tablets
N8010XXUDNE4!! /N8013/ GT-N8010 WiFi Only ROMDownload>>> N8010XXUDNE4_N8010BTUDNF1_BTU_N8013.tar.zip
Download>>> UPDATE-SuperSU-v2.01.zip for Root
Installing ROM
Requires a Factory Reset (Wipe) Thanks to @pre4speed
1. Unzip N8010XXUDNE4_N8010BTUDNF1_BTU_N8013.tar.zip
2. Install N8010XXUDNE4_N8010BTUDNF1_BTU_N8013.tar.md5 with included Odin 3.07
3. Skip through setup (WiFi won't work Yet)
4. Get back in download mod, and install philz_touch_6.41.6-n8013.tar.md5 ,openrecovery-twrp-2.7.1.0-gt-n8000.tar or N8013-CWM-Touch-6.0.3.6.tar.md5 (Your Choice)
5. Copy GT-N8013-KK-WiFi-Fix.zip, Stock-GT-N8000-leaked-KK-Boot.img-CWR-installer.zip and UPDATE-SuperSU-v2.01.zip to your sdcard
6. Reboot phone into recovery( Hold [power][volume-up] button until in recovery) Install Stock-GT-N8000-leaked-KK-Boot.img-CWR-installer.zip,GT-N8013-KK-WiFi-Fix.zip to fix WiFi
7. Install UPDATE-SuperSU-v2.01.zip to get root Thanks to @pre4speed
8. Reboot and you should have Wifi
9. Recommend doing a backup after you complete setting up your phone, before applying any add-ons
Files In download zip
**********************************************************************************************************************************************************************************************************************
N8000XXUDNE4!! /N8013/ GT-N8010 NON WiFi ROMThis is NON Wifi Tablet N8000 ROM
WARNING!! N8000/N8010/N8012 this Contains the GT-N8013 BootloaderDownload>>> N8000XXUDNE4_N8000OXADNE4_GT-N8013.tar.zip
Mega Link >>> N8000XXUDNE4_N8000OXADNE4_GT-N8013.tar.zip
Contains all files needed for GT-N8013
GT-N8013-KK-WiFi-Fix.zip........................................... .......................WiFi Work Around Fix.. Install this last after installing root
N8000XXUDNE4_N8000OXADNE4_GT-N8013.tar.md5................................Offic ial KK Firmware with Leaked Boot.img and JB bootloader files
N8013.pit .................................................. .....................................Only need if you want to reformat phone
Odin307.zip....................................... ...............................................Odi n
Recovery's You choose the one you want, Install with Odin
N8013-CWM-Touch-6.0.3.6.tar.md5................................... ..................CWM Recovery
openrecovery-twrp-2.7.0.0-gt-n8013.tar......................................... .....TWRP Recovery
philz_touch_6.41.6-n8013.tar.md5..................................... ...................Philz CWM touch recovery with eztra stuff
SystemUI_Remove_Signal_Icons_Official_KK_CWR_insta ller.zip...................Removes No Signal Circle from task bar
UPDATE-SuperSU-v1.94.zip......................................... ........................Used to Root and Give Root access to files
WiFi_Only_Remove_Phone_Service_N8013_Custom_Recovery_Installer.zip.... Removes phone apps...suppose to save battery from tablet not searching for towers Use Updated attached below
********************************************************************************************************************************************************************************************************
Running N8000XXUDNE4 on GT-N8013Only tested on GT-N8013 Tablet
Unzip N8000XXUDNE4_N8000OXADNE4_GT-N8013.tar.zip with 7-zip
Install with Odin and Skip through the settings then boot back to Download mode and install:
Install Custom Recovery
I used philz_touch_6.41.6-n8013.tar.md5
Install with Recovery UPDATE-SuperSU-v1.94.zip to get Root
SuperSU Home Page
ROOT GUIDE OFFICIAL STOCKROM N8000XXUDNE4 KitKat (4.4.2)
Install this for wifi fix
GT-N8013-KK-WiFi-Fix.zip
Removing Data Signal From Task Bar
SystemUI_Remove_Signal_Icons_Official_KK_CWR_installer.zip
Only removes No Data (Circle Icon)
Manually Unpacking Official Firmware
Download For Official KitKat Firmware
N8000XXUDNE4_N8000OXADNE4_DBT
Unzip N8000XXUDNE4_N8000OXADNE4_DBT.zip with 7-zip
Unzip N8000XXUDNE4_N8000OXADNE4_N8000XXUDNE1.tar.md5
Remove modem.bin,sboot.bin, boot.img and tz.img,
Use Boot.img from Leaked KK
I Used TAR_MD5_PACKAGER to repack the rest of the files and the leaked KK boot.img
Fix Screen Mirroring KitKat official 4.4.2 GT-N8013 by vickoc
Removing Phone Service
Phone apps removed should fix battery drain issue ( phone searching for towers)
SecPhone.apk ( Removes Cell Search Activity)
SecPhone.odex ( Removes Cell Search Activity)
SecMms_Tablet_Upgrade.apk
SecMms_Tablet_Upgrade.odex
SecTelephonyProvider.apk
SecTelephonyProvider.odex
Stk.apk
Stk.odex
Stop cell tower search battery usage
Install with Your Custom Recovery
WiFi_Only_Remove_Phone_Service_N8013_Custom_Recovery_Installer.zip
You can use Disable Application to disable (Freeze)any apps temporary not wanted to see in app Drawer
You can also use ADB to disable (Freeze)any other apps temporary not wanted to see in app Drawer
Code:
C:\Users\carl>adb shell
[email protected]:/ $ su
su
[email protected]:/ # pm list packages
pm list packages
package:com.sec.android.app.ringtoneBR
package:com.sec.android.app.phoneutil
package:com.android.defcontainer
package:com.samsung.android.scloud.quota
package:com.sec.android.gallery3d
package:com.android.phone
package:com.sec.android.fotaclient
package:com.sec.android.motions.settings.panningtutorial
package:com.fmm.dm
package:android.googleSearch.googleSearchWidget
package:com.sec.android.app.bluetoothtest
package:com.android.bluetooth
package:com.android.providers.calendar
package:com.vlingo.midas
package:com.sec.android.widgetapp.notificationwidget
package:com.sec.factory
package:com.samsung.android.app.divx
package:com.samsung.android.scloud.sync
package:com.android.browser
package:com.sec.android.allshare.service.fileshare
package:com.samsung.pickuptutorial
package:com.sec.android.app.snotebook
package:com.smartapp.appfreezer
package:com.android.providers.downloads.ui
package:com.gd.mobicore.pa
package:com.android.documentsui
package:com.android.vpndialogs
package:com.peel.app
package:com.android.providers.media
package:com.sec.android.widgetapp.at.yahoostock.stockclock
package:com.sec.android.app.lcdtest
package:com.sec.android.nearby.mediaserver
package:com.sec.android.widgetapp.analogclocksimple
package:com.siso.app.generic
package:com.sec.android.cloudagent
package:com.google.android.setupwizard
package:com.samsung.sec.sketch
package:com.sec.android.widgetapp.favoriteswidget
package:com.monotype.android.font.samsungsans
package:com.hu1.wallpaper.aurora2
package:com.android.settings
package:com.sec.android.service.cm
package:com.sec.pcw
package:com.google.android.street
package:air.com.adobe.pstouch.oem1
package:com.sec.android.widgetapp.webmanual
package:com.google.android.googlequicksearchbox
package:mobi.xperiacle.mwappsmanager
package:com.android.exchange
package:com.sec.app.samsungprintservice
package:com.sec.android.providers.tasks
package:com.google.android.backuptransport
package:com.sec.android.gesturepad
package:com.samsung.groupcast
package:com.sec.allsharecastplayer
package:com.wssyncmldm
package:com.google.android.apps.maps
package:com.android.wallpapercropper
package:com.sec.android.app.FileShareClient
package:com.android.providers.settings
package:com.sec.msc.learninghub
package:com.sec.android.app.mobileprint
package:com.sec.android.provider.snote
package:com.google.android.apps.docs
package:com.android.providers.downloads
package:com.smlds
package:net.woostudio.sqliteeditor
package:com.android.phasebeam
package:com.sec.android.fwupgrade
package:com.sec.android.app.wallpaperchooser
package:com.tgrape.android.radar
package:com.sec.android.widgetapp.at.hero.accuweather
package:com.google.android.videos
package:com.sec.bcservice
package:com.monotype.android.font.cooljazz
package:com.sec.android.app.popupuireceiver
package:com.android.inputdevices
package:com.orange.authentication.simcard.permission
package:com.sec.android.provider.logsprovider
package:com.sec.android.app.popupcalculator
package:com.google.android.configupdater
package:com.sec.enterprise.mdm.vpn
package:com.sec.android.app.FileShareServer
package:com.samsung.topicwall
package:com.sec.android.app.sysscope
package:com.samsung.music
package:com.sec.android.band
package:com.sec.android.app.samsungapps
package:android
package:com.android.providers.contacts
package:com.acrodea.crayonphysics
package:com.sec.android.app.servicemodeapp
package:com.epson.mobilephone.samsungprintservice
package:com.google.android.apps.uploader
package:com.android.externalstorage
package:com.sec.android.widgetapp.SPlannerAppWidget
package:com.android.providers.applications
package:com.samsung.android.sdk.spenv10
package:com.samsung.android.scloud.proxy.contacts
package:com.siriusapplications.quickboot
package:com.google.android.apps.plus
package:com.android.vending
package:com.sec.android.app.mt
package:com.sec.android.providers.downloads
package:com.sec.android.drmpopup
package:com.android.keychain
package:com.sec.android.widgetapp.at.hero.accuweather.widget
package:eu.chainfire.supersu
package:com.sec.android.mmapp
package:com.google.android.apps.magazines
package:com.wsomacp
package:com.samsung.klmsagent
package:com.sec.android.app.music
package:com.sec.android.app.minimode.res
package:com.google.android.gsf
package:com.android.keyguard
package:com.sec.android.widgetapp.ap.yahoonews
package:com.monotype.android.font.chococooky
package:com.android.shell
package:com.sec.usbsettings
package:com.google.android.syncadapters.contacts
package:com.fixmo.isa
package:com.samsung.scrc.idi.server
package:com.sec.phone
package:com.sec.android.app.wfdbroker
package:com.fmm.ds
package:com.android.providers.partnerbookmarks
package:com.android.contacts
package:com.sec.android.app.gamehub
package:com.samsung.everglades.video
package:com.siso.photoWall
package:com.android.htmlviewer
package:com.dama.paperartist
package:com.sec.android.app.parser
package:com.google.android.gsf.login
package:com.sec.android.inputmethod
package:com.sec.android.daemonapp.ap.accuweather
package:com.sec.android.directconnect
package:com.sec.android.widgetapp.dualclockanalog
package:com.android.calendar
package:com.sec.android.daemonapp.ap.yahoostock.stockclock
package:com.sec.android.provider.badge
package:com.samsung.SMT
package:com.sec.android.app.selftestmode
package:com.sec.android.app.factorymode
package:com.samsung.android.scloud.backup
package:com.android.sharedstoragebackup
package:com.adobe.air
package:com.sec.android.allshare.service.controlshare
package:com.google.android.marvin.talkback
package:com.android.certinstaller
package:com.siso.app.genericprintservice
package:com.monotype.android.font.rosemary
package:com.sec.spp.push
package:com.google.android.gms
package:com.sec.android.app.launcher
package:com.samsung.shareshot
package:com.android.dreams.phototable
package:com.sec.android.app.worldclock
package:com.sec.android.allshare.service.mediashare
package:org.simalliance.openmobileapi.service
package:com.dropbox.android
package:com.sec.enterprise.knox.attestation
package:air.SQLEditor
package:com.sec.android.app.SecSetupWizard
package:com.hp.android.printservice
package:com.sec.enterprise.mdm.services.simpin
package:com.sec.spen.flashannotate
package:com.sec.android.SamsungDrmProvider
package:com.sec.android.app.sns3
package:com.sec.android.providers.security
package:com.google.android.music
package:com.visionobjects.resourcemanager
package:com.android.wallpaper.livepicker
package:com.sec.android.directshare
package:com.sec.automation
package:com.diotek.mini_penmemo
package:com.android.packageinstaller
package:com.sec.app.RilErrorNotifier
package:com.sec.pcw.device
package:com.samsung.helphub
package:com.sec.android.app.wlantest
package:com.android.noisefield
package:com.android.email
package:com.sec.spen.flashannotatesvc
package:com.sec.android.app.FlashBarService
package:com.android.location.fused
package:com.android.backupconfirm
package:com.sec.android.widgetapp.programmonitorwidget
package:com.wssnps
package:com.android.musicfx
package:com.google.android.apps.books
package:com.sec.android.daemonapp.ap.yahoonews
package:com.android.soundrecorder
package:com.samsung.clipboardsaveservice
package:com.lifevibes.trimapp
package:com.sec.android.app.SPenKeeper
package:com.google.android.partnersetup
package:com.sec.tcpdumpservice
package:com.sec.android.app.GlanceView
package:com.android.proxyhandler
package:com.sec.msc.nts.android.proxy
package:com.sec.android.app.ve
package:com.sec.android.app.camera
package:com.sec.android.preloadinstaller
package:com.google.android.feedback
package:com.sec.dsm.phone
package:com.sec.phone.fake
package:com.sec.android.app.keyguard
package:com.google.android.talk
package:com.samsung.android.scloud.proxy.snote
package:com.sec.smartcard.manager
package:com.sec.android.app.myfiles
package:com.sec.chaton
package:com.android.providers.userdictionary
package:com.samsung.android.scloud.proxy.calendar
package:com.samsung.android.providers.context
package:com.sec.android.widgetapp.digitalclock
package:com.osp.app.signin
package:com.sec.android.Preconfig
package:com.android.pacprocessor
package:com.sec.android.cloudagent.dropboxoobe
package:com.samsung.android.scloud.auth
package:com.samsung.videohub
package:com.samsung.android.mdm
package:com.sec.android.app.mediasync
package:com.sec.android.app.controlpanel
package:com.android.printspooler
package:com.google.android.syncadapters.calendar
package:com.LocalFota
package:com.samsung.android.scloud.proxy.browser
package:com.samsung.android.MtpApplication
package:com.android.dreams.basic
package:com.google.android.play.games
package:com.sec.android.app.clockpackage
package:com.sec.android.app.personalization
package:com.android.systemui
package:com.samsung.sec.android.application.csc
package:com.infraware.polarisoffice5tablet
package:com.samsung.android.livewallpaper.deepsea
package:com.sec.android.app.videoplayer
package:com.sec.android.app.DataCreate
package:com.sec.android.app.SuggestionService
package:com.speedsoftware.sqleditor
package:com.google.android.gm
package:com.sec.android.widgetapp.dualclockdigital
package:com.estrongs.android.pop
package:com.samsung.android.livewallpaper.luminousdots
package:com.henry.sqliteqa_litte
package:com.android.chrome
package:com.sec.android.Kies
package:com.sec.dsm.system
package:com.sec.knox.seandroid
package:com.sec.android.contextaware
package:com.sec.esdk.elm
[email protected]:/ # pm disable com.android.phone
pm disable com.android.phone
Package com.android.phone new state: disabled
[email protected]:/ #
Install Attached SecPhone.apk_Official_KK_CWR_installer.zip if you want phone app back
Failed on my N8010.
Checked GT-N8013-KK-WiFi-Fix.zip and cannot understand how it worked. What's the function of the files which are put into /data?
And if this doesn't work on N8010, is there another way I can try?
This worked for me
Smart-X said:
Failed on my N8010.
Checked GT-N8013-KK-WiFi-Fix.zip and cannot understand how it worked. What's the function of the files which are put into /data?
And if this doesn't work on N8010, is there another way I can try?
Click to expand...
Click to collapse
Try this:
http://forum.xda-developers.com/showpost.php?p=53065121&postcount=77 (just ignore the Tip)
I tried in on a N8010 and this worked for me, but I think it's essentially the same. I assume the only difference is that the boot.img from the leaked ROM is inlcuded in the tar in this guide and not in a flashable zip as in the guide from the other thread.
Also did you check, if one of your files was corrupted. If so, just redownload and retry
Smart-X said:
Failed on my N8010.
Checked GT-N8013-KK-WiFi-Fix.zip and cannot understand how it worked. What's the function of the files which are put into /data?
And if this doesn't work on N8010, is there another way I can try?
Click to expand...
Click to collapse
The /data files some how fix the IP address issue.
Did you root your phone yet? it may have to be rooted to copy to your userdata partition
When you install the ROM did you have to set it up? If you did not then you did not install on a clean system and that may cause issues.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Yes I Wiped almost everything before installing the ROM.
And yes I had to set it up at the first boot after installation.
And yes I root my phone with SuperSU 1.99r3.
So those files fix the IP address issue.
Can they be used on N8010 too?
Anyway I'll try it again later.
Smart-X said:
Yes I Wiped almost everything before installing the ROM.
And yes I had to set it up at the first boot after installation.
And yes I root my phone with SuperSU 1.99r3.
So those files fix the IP address issue.
Can they be used on N8010 too?
Anyway I'll try it again later.
Click to expand...
Click to collapse
did you install the leaked boot.img? I had to install it to get wifi going, it would not work with the Official KK boot.img
I do not know about 8010, sorry
carl1961 said:
did you install the leaked boot.img? I had to install it to get wifi going, it would not work with the Official KK boot.img
I do not know about 8010, sorry
Click to expand...
Click to collapse
I failed yesterday with installing both the leaked boot.img and GT-N8013-KK-WiFi-Fix.zip.
I'll try the whole installation again When I got my N8010 later today.
Thanks for your answers.
Just installed and it works great! Now I don't have to wait!
Update OP
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Please simplify post.
First, Thank you so much. In the words of the song Thrift Shop "This is freakin awsome!"
There is a lot of stuff going on in the OP. I haven't flashed in a while so I am rusty. This is what I am seeing:
Mega Link has all of the files that I need.
Install ROM using Odin (skip through settings and boot back to Download mode)
Use Odin to install Custom Recovery
Use recovery to install wifi fix, wifi only remove phone service and systemUI remove system icons
Finish.
What about the other files in zip? Do i need them? (N8013 pit), (CWM Touch), (Open Recovery)
Can I use Mobile Odin?
I just want to get it right before I flash this awesomeness.
carl1961 said:
Install with Odin and Skip through the settings then boot back to Download mode and install:
Click to expand...
Click to collapse
I'm not very familiar with using odin. Which files are we putting into odin and where do I put them in? Also, is the PIT file required?
TimDotThomas said:
First, Thank you so much. In the words of the song Thrift Shop "This is freakin awsome!"
There is a lot of stuff going on in the OP. I haven't flashed in a while so I am rusty. This is what I am seeing:
Mega Link has all of the files that I need.
Install ROM using Odin (skip through settings and boot back to Download mode)
Use Odin to install Custom Recovery
Use recovery to install wifi fix, wifi only remove phone service and systemUI remove system icons
Finish.
What about the other files in zip? Do i need them? (N8013 pit), (CWM Touch), (Open Recovery)
Can I use Mobile Odin?
I just want to get it right before I flash this awesomeness.
Click to expand...
Click to collapse
GT-N8013-KK-WiFi-Fix.zip..................................................................WiFi Work Around Fix.. Install this last after installing root
N8000XXUDNE4_N8000OXADNE4_GT-N8013.tar.md5................................Official KK Firmware with Leaked Boot.img and JB bootloader files
N8013.pit .......................................................................................Only need if you want to reformat phone
Odin307.zip......................................................................................Odin
Recovery's You choose the one you want, Install with Odin
N8013-CWM-Touch-6.0.3.6.tar.md5.....................................................CWM Recovery
openrecovery-twrp-2.7.0.0-gt-n8013.tar..............................................TWRP Recovery
philz_touch_6.41.6-n8013.tar.md5........................................................Philz CWM touch recovery with eztra stuff
SystemUI_Remove_Signal_Icons_Official_KK_CWR_installer.zip...................Removes No Signal Circle from task bar
UPDATE-SuperSU-v1.94.zip.................................................................Used to Root and Give Root access to files
WiFi_Only_Remove_Phone_Service_N8013_Custom_Recovery_Installer.zip.... Removes phone apps...suppost to save battery from tablet not searching for towers
link6155 said:
I'm not very familiar with using odin. Which files are we putting into odin and where do I put them in? Also, is the PIT file required?
Click to expand...
Click to collapse
N8000XXUDNE4_N8000OXADNE4_GT-N8013.tar.md5 Install this with Odin, Click on (PDA) and select file to install, All install here
N8013.pit Only need if you want to reformat phone
Install Recovery with Odin ( Only need one of these)
N8013-CWM-Touch-6.0.3.6.tar.md5
openrecovery-twrp-2.7.0.0-gt-n8013.tar
philz_touch_6.41.6-n8013.tar.md5
All these you copy to SD card and install with Recovery
SystemUI_Remove_Signal_Icons_Official_KK_CWR_installer.zip
UPDATE-SuperSU-v1.94.zip
WiFi_Only_Remove_Phone_Service_N8013_Custom_Recovery_Installer.zip
carl1961 said:
N8000XXUDNE4_N8000OXADNE4_GT-N8013.tar.md5 Install this with Odin, Click on (PDA) and select file to install, All install here
N8013.pit Only need if you want to reformat phone
Install Recovery with Odin ( Only need one of these)
N8013-CWM-Touch-6.0.3.6.tar.md5
openrecovery-twrp-2.7.0.0-gt-n8013.tar
philz_touch_6.41.6-n8013.tar.md5
All these you copy to SD card and install with Recovery
SystemUI_Remove_Signal_Icons_Official_KK_CWR_installer.zip
UPDATE-SuperSU-v1.94.zip
WiFi_Only_Remove_Phone_Service_N8013_Custom_Recovery_Installer.zip
Click to expand...
Click to collapse
Install (recovery) one at a time starting with SuperSu or can this recovery do multiple flashes?
TimDotThomas said:
Install (recovery) one at a time starting with SuperSu or can this recovery do multiple flashes?
Click to expand...
Click to collapse
I would install one at a time say root then what ever other's, and then I would do a reboot then install wifi fix last after a reboot with root working
Cool. Now in my haste I did not click re-partition. Is that a problem? Should I reflash?
Sent from my Nexus 5 using XDA Free mobile app
TimDotThomas said:
Cool. Now in my haste I did not click re-partition. Is that a problem? Should I reflash?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
no you do not check that
if you install the pit file it will auto check
Working on my N8013
Just installed this and it's working fine for the most part
Warning
I decided to do a factory reset. BIG MISTAKE! I think I bricked my device. It is force closing in another language. When I flash the ROM again, it still does not work. It is getting late. Tomorrow I will flash stock ROM and then reflash this new one. Hope that works. Any suggestions?
TimDotThomas said:
I decided to do a factory reset. BIG MISTAKE! I think I bricked my device. It is force closing in another language. When I flash the ROM again, it still does not work. It is getting late. Tomorrow I will flash stock ROM and then reflash this new one. Hope that works. Any suggestions?
Click to expand...
Click to collapse
Before installing do a factory reset then use the pit file with install, repatriation should be checked like picture on op.
Sent from my GT-N8000 using XDA Premium 4 mobile app
How to DeOdex YOUR 0A6 Rom.
I would like to note that I appreciate all the work that developers have put forth in creating and maintaining modified Roms. there are some awesome feature rich implementations available. My intentions are not to be critical of any specific Rom or mod. Without the developers we would have nothing.
Firt off, Let me explain why I'm writing this guide of sorts. I've always enjoyed an essentially stock ODEXED rom with a minnimum of tweaks.
When 0A6 arrived with ART support odexing is not currently possible. I attempted to use prepared deoxed varietys but there was always something that was a dealbreaker for me. I have nothing against features but a ROM completely loaded with bells and whistles tends to allow bugs and stability issues creep in. and the requirements to wipe 15 times and do a clean flash while singing a gregorian chant just to get it to boot didn't settle well with me.
Using one of the DeOdexed varietys, I was having problems with duplicate apk's being created in /data/app and erronoius Play store updates compounding this issue. There was also an issue with Private Mode and a variety of FC's. In frustration I reverted to a stock rooted configuration and my phone was rock solid.
BUT, I really missed a few mods that I had grown very accustomed to having namely,
5-Way Reboot
Hotspot Mod
PRL Write
Extra Toggles
So instead of trying to install clean why not create a way for me to Custom DeOdex *MY* rom? and not have to start from scratch everytime allowing a dirty flash without creating some crazy stability issue.
This method is very common knowledge I thought I'd just explain it in an easy to understand way.
Here is what you need.
A stock 0A6 ROOTED configurated phone. Debloat as needed. Set the phone up exactly how you like it with apps and such.
Make sure it's stable. (If you have issues before DeOdexing they will be there afterward!)
Here's the files you may need to make this happen
LBD2.4.zip
7-Zip
Installer template (at end of post)
1> Make sure ADB is working on your computer. USB debugging turned on. Create a folder to store your soon to be download system files and launch a DOS shell from that working folder. Working folder name should NOT contain spaces. With the phone hooked up you should be able to type adb shell and get a prompt.
2> Type these commands
adb pull /system/app app/
adb pull /system/priv-app/ priv-app/
adb pull /system/framework framework/
This will take awhile and you will be left with three folders
Create a new folder named "system" and place these three folders inside.
3> Extract and launch LBD2.4 (This is the DeOdexer and is AWESOME). Point it at your recently created "system" folder and let it do it's thing.
I'll assume this will occur without errors as I have never had any.
4> At this point you can manually apply modded apk's to the system folder but I don't really recommend it. They can be applied afterward using the seperate installer zips.
5> with 7-Zip installed open the provided Installer template. Do not Extract it. Just open it in the 7-Zip file browser using the right click context menu in windows.
Drag-Drop the contents of your system folder into the empty system folder in the 7-Zip browser It should be the three folders previously created but now they are Deodexed. Close the 7-zip file manager and select Yes if it asks you to save.
Note: The provided installer template has been modified to only wipe and replace the three system directories.
6. Copy the created installer to your sdcard and install with recovery. Wipe cache and Dalvik before rebooting.
Go have lunch. You will sit at a boot screen for about 10 minutes. Then another 20 to rebuild caches. Time varies.
7. Your system will now be Deodexed! At this point you can install your mods one at a time, I recommend this so you can test your system between installs to determine if a specific mod is creating problems.
This method has so far removed ALL of my stability issues.
The InstallerTemplate is valid for other devices? E.g. Samsung S4.
Thanks.
quinielascom said:
The InstallerTemplate is valid for other devices? E.g. Samsung S4.
Thanks.
Click to expand...
Click to collapse
I, too, would like to know if I can use this on my Note 4 (N910G).
Now I haven't used adb in a while but every time I try to run 'adb pull /system/app app/' it runs for about 4 seconds then quits. Then I try to run any other command and it says the device is offline. I have everything up to date, so I'm at a loss right now.
EDIT: So I couldn't get adb to work right so I pulled the folders using ES file manager then copied them to my PC. When I run the deoxeder I get two errors, Invalid Application Directory -"Application folder and Rom folder should not have spaces" and Error -"Invalid Rom Folder"
EDIT: I had a space at the end of a folder title, currently running, will test, and report back.
stuck
stuck on boot :S s5 g900h
so confused, i dont know what to do
I am on a Sprint Samsung Galaxy S5 running stock lolipop 5.0. I want to deodex my Rom so that I can intall xposed. After 8 hours I am practically in tear because absolutely NO-one can help
I dont know what to do for Rom System Path. I followed alll the instruction to detail and eveytime I click run it tells me that there is no space or something.. Here is the path I have no idea whre to go from here
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The rom system path would be what you did in step two:
2> Type these commands
adb pull /system/app app/
adb pull /system/priv-app/ priv-app/
adb pull /system/framework framework/
This will take awhile and you will be left with three folders
Create a new folder named "system" and place these three folders inside.
So you would click 'browse' then go to the system folder you made and place the other three folders in.
Pulling files via adb gave me errors, so I downloaded it by root explorer
Now I'm deodexed, thanks a lot
daswahnsinn said:
The rom system path would be what you did in step two:
2> Type these commands
adb pull /system/app app/
adb pull /system/priv-app/ priv-app/
adb pull /system/framework framework/
This will take awhile and you will be left with three folders
Create a new folder named "system" and place these three folders inside.
So you would click 'browse' then go to the system folder you made and place the other three folders in.
Click to expand...
Click to collapse
Zhekin said:
Pulling files via adb gave me errors, so I downloaded it by root explorer
Now I'm deodexed, thanks a lot
Click to expand...
Click to collapse
How have you guys replaced back the three deodexed folders???
Sent from my Samsung Galaxy S3 GT-i9300 using Tapatalk 4
PIRATA! said:
How have you guys replaced back the three deodexed folders???
Sent from my Samsung Galaxy S3 GT-i9300 using Tapatalk 4
Click to expand...
Click to collapse
There's an update zip in the OP's first thread. Now that being said I have a Note 3 and haven't tried it yet. Been a little busy but I have a complete deodex'd the three folders w/o errors.
Boot loop. SM-G900M
I got stuck on boot scrren, and my recovery can't format cache partition in the recovery.
daswahnsinn said:
There's an update zip in the OP's first thread. Now that being said I have a Note 3 and haven't tried it yet. Been a little busy but I have a complete deodex'd the three folders w/o errors.
Click to expand...
Click to collapse
Did you pulled with device rooted or not? Is it the same to pull with root or no root?
I am doing that now with no root and I had some skipping special file 'xxxxxxx.so' at the beginning of pulling the /app/ folder.
Is that ok??
PIRATA! said:
Did you pulled with device rooted or not? Is it the same to pull with root or no root?
I am doing that now with no root and I had some skipping special file 'xxxxxxx.so' at the beginning of pulling the /app/ folder.
Is that ok??
Click to expand...
Click to collapse
I couldn't get ADB to pull the folders/files so I used a root file explorer. So, yes I did use a rooted device. I don't know if it's the same as if it weren't rooted but it should be. I would say some files may not get pulled for some reason but I'd retry. I'm not a dev so I'm not much help. I tinker with things until I other break it or make what I what work.
daswahnsinn said:
I couldn't get ADB to pull the folders/files so I used a root file explorer. So, yes I did use a rooted device. I don't know if it's the same as if it weren't rooted but it shouldn't be. I would say some files may not get pulled for some reason but I'd retry. I'm not a dev so I'm not much help. I tinker with things until I other break it or make what I what work.
Click to expand...
Click to collapse
Mmmh.... but I've read that a lot of people does it without rooting.....or not??
About your situation, have you extracted the same exact folder so, right?
Tnx.
tiago.rici said:
I got stuck on boot scrren, and my recovery can't format cache partition in the recovery.
Click to expand...
Click to collapse
I used Root Explorer and did a manual copy of these folders (instead use adb pull). And worked!
Now I'm waiting 1st boot.
---------- Post added at 02:57 PM ---------- Previous post was at 02:49 PM ----------
Zhekin said:
Pulling files via adb gave me errors, so I downloaded it by root explorer
Now I'm deodexed, thanks a lot
Click to expand...
Click to collapse
How long have you waited on boot scrren? I'm about almost 20 minutes and still nothing. :fingers-crossed:
problems with the process on my SM-T530NU with stock 5.0.2 ROM
Hi,
Sorry to bother you, but if its not too much trouble, can you please answer a few questions for me about the deodex process?
I tried to adb pull the 3 system folders, /system/app, /system/framework, and /system/priv-app, but some of the files gave me an error on copying. So I tried copying them with es explorer to my external SD which worked OK.
Next, I tried copying the 3 folders to my PC. I copied the correct amount of files (894), but the amount of directories went down from 1013 to 506. Is this correct?
I then tried running the folders through ldb 2.5. most of the files were successful, but there were a few which failed. (Maps, services, and a few others.) is this OK? Can I still use the output to burn to my Tab4?
Thanks for any help that you can give.
Motisu
motisu said:
Hi,
Sorry to bother you, but if its not too much trouble, can you please answer a few questions for me about the deodex process?
I tried to adb pull the 3 system folders, /system/app, /system/framework, and /system/priv-app, but some of the files gave me an error on copying. So I tried copying them with es explorer to my external SD which worked OK.
Next, I tried copying the 3 folders to my PC. I copied the correct amount of files (894), but the amount of directories went down from 1013 to 506. Is this correct?
I then tried running the folders through ldb 2.5. most of the files were successful, but there were a few which failed. (Maps, services, and a few others.) is this OK? Can I still use the output to burn to my Tab4?
Thanks for any help that you can give.
Motisu
Click to expand...
Click to collapse
I've just ben informed test the correct way should be to extract those folders from a stock firmware downloaded.
Other method but risky, as you could also get extra apps not natively born with your device, is to copy them or pull them from recovery using a file manager like Aroma File Manager or TWRP integrated file manager, or use adb from recovery.
Other "while system is running" methods are not preferred as they could give errors back.
Cheers.
Sent from my Samsung Galaxy S3 GT-i9300 using Tapatalk 4
PIRATA! said:
I've just ben informed test the correct way should be to extract those folders from a stock firmware downloaded.
Other method but risky, as you could also get extra apps not natively born with your device, is to copy them or pull them from recovery using a file manager like Aroma File Manager or TWRP integrated file manager, or use adb from recovery.
Other "while system is running" methods are not preferred as they could give errors back.
Cheers.
Sent from my Samsung Galaxy S3 GT-i9300 using Tapatalk 4
Click to expand...
Click to collapse
OK, I did exactly as you recommended and got exactly the same result. I used the advanced file manager in TWRP recovery to make copies oof the 3 subfolders and then copied the copies to my PC. I got exactly the same results. still missing folders and getting errors in LBD.
motisu said:
OK, I did exactly as you recommended and got exactly the same result. I used the advanced file manager in TWRP recovery to make copies oof the 3 subfolders and then copied the copies to my PC. I got exactly the same results. still missing folders and getting errors in LBD.
Click to expand...
Click to collapse
Use Total Commander for transferring in Windows ambient.
It's good also for coping from micro-sb to hard-disk.
Enable hidden files!
Sent from my Samsung Galaxy S3 GT-i9300 using Tapatalk 4
thank you
Thank you very much for this well detailed explanation. I am not developer. It took me 2 wks searching, working on how to deodex my rom untill finally found this tutorial. It help me a lot.???
Guide: Getting Xposed RunningThis morning, I finally managed to get Xposed up and running on my Turbo. So I thought I'd write up a guide as to how!
What you'll need:
A paid copy of Mofo (obviously)
Either a modified system image containing Xposed already, or if you like, you can modify one yourself as described in this tutorial. I've already created a modified system image to include Xposed as well as Wifi Tethering and a modified hosts file for ad blocking.
The Xposed Installer apk
Xposed Installer needs to be installed on your phone
Terminal Emulator and ES File Explorer from the play store need to be installed on your phone
A rooted image flashed to your phone
Before flashing anything, this is what you need to do:
On your computer, find your de.robv.android.xposed.installer_v33_36570c.apk and rename it to be a .zip file.
Open this .zip file and extract /assets/XposedBridge.jar and, if you're modifying your own system image, extract /assets/arm/app_process_xposed_sdk16 as well.
Put XposedBridge.jar somewhere on your phone, I like to use the Downloads folder so I don't lose track of it later.
In ES File Explorer, navigate to /data (NOT SDCARD/DATA)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Make sure it doesn't say sdcard > data!
Create a folder called "xposed"
Long press the folder, select properties, and set permissions to 755
Set the owner of the folder to root and the group to shell
Move XposedBridge.jar into the xposed folder we just created.
Make the permissions of XposedBridge.jar 644
As before, make the owner root and the group shell.
Open the Xposed Installer app on your phone.
Open terminal emulator and type
Code:
ps | grep xposed
This will return a pattern like the following. Make a note of the first seven characters, as shown (the first is a lowercase u)
Return to /data/xposed
Create two new files: modules.list and modules.whitelist
Make the permissions on both files 644 as above
Set the owner to the seven characters we noted down earlier and the group to shell on both files
If you're flashing a pre-compiled image with Xposed, you're done here! Go ahead and flash, and enjoy!
If you're modifying your own system image, you've got some more work to do. Take app_process_xposed_sdk16 from the Xposed apk and rename it to app_process.
In your turbo system image, navigate to /bin/ and replace app_process with the one from Xposed Framework. Make sure its permissions are set to 755:
Code:
sudo chmod 755 /path/to/img/bin/app_process
Linux does not allow setting the group of a file to a nonexistent group, so on your pc you'll have to make a shell group:
Code:
sudo groupadd shell
Change the group of app_process to shell:
Code:
sudo chgrp shell /path/to/img/bin/app_process
You're ready to flash!
NOTE: If XposedBridge.jar reports problems, try setting installation mode in the Xposed installer app to recovery (flash manually) and hitting install, then reboot.
You're done! Xposed should show up as installed! Don't use any modules that require system write access, such as replacing system icons, but most modules (ie GravityBox) work fine without it.
Ekkoria said:
This morning, I finally managed to get Xposed up and running on my Turbo. So I thought I'd write up a guide as to how!
Click to expand...
Click to collapse
Gahhh I was working all day on getting Xposed baked in
Thanks for the write up! I'm finding modifying the image file and flashing it to be just as addictive if not more than flashing someones prebuilt roms on other devices. I never got into compiling android so this feels like a way to tinker on my own without jumping into the deep end of code.
ntxct said:
Gahhh I was working all day on getting Xposed baked in
Thanks for the write up! I'm finding modifying the image file and flashing it to be just as addictive if not more than flashing someones prebuilt roms on other devices. I never got into compiling android so this feels like a way to tinker on my own without jumping into the deep end of code.
Click to expand...
Click to collapse
Same here! When I finally opened Xposed Installer and saw it read the framework as installed, I've almost never been so excited about something Android.
i dont need it but its a great guide, easy, short and with pictures!
Does the phone need to be flashed with a rooted image, like that in the tutorial of how to modify system images? I can't write to /data, presumably because I don't have the rooted image flashed yet. Also my /data directory is empty.
I have a copy of mofo, and copies of the rooted system image and your already compiled system image. Is there something I am missing? Thank you in advance.
Thanks so much man, about to flash. Will let you know how it goes.
Ah damn, I actually just did a bit different process of installing Xposed on a image for myself, (which involved baking it into the rom that didn't have it) totally got it working and I've rebooted 3 times so far and everything sticks. Loving having battery percentage now! I can write a quick tutorial writing xposed files into a fresh rooted image via Virtualbox and such... Took me a few hours
It did not work for xposedbridge.jar
aven1357 said:
Does the phone need to be flashed with a rooted image, like that in the tutorial of how to modify system images? I can't write to /data, presumably because I don't have the rooted image flashed yet. Also my /data directory is empty.
I have a copy of mofo, and copies of the rooted system image and your already compiled system image. Is there something I am missing? Thank you in advance.
Click to expand...
Click to collapse
Yes, you will need to be rooted first to perform these actions. Apologies for not originally including this. OP updated
savagebunny said:
Ah damn, I actually just did a bit different process of installing Xposed on a image for myself, (which involved baking it into the rom that didn't have it) totally got it working and I've rebooted 3 times so far and everything sticks. Loving having battery percentage now! I can write a quick tutorial writing xposed files into a fresh rooted image via Virtualbox and such... Took me a few hours
Click to expand...
Click to collapse
Yes please do so. I'd be very interested.
Sent from my XT1254 using XDA Free mobile app
I am having trouble with es file explr it tells me the operation failed when trying to do anything I have root and I enabled root for ES it seemed to work on root browser fine (I reset my device and just installed es so far)
edit checked and the root enhancement options are greyed out?
After following directions for all files and then subsequent flashing of your pre-built image xposed installer still reports framework problem. I've gone back and double checked the user:group and perm masks and everything looks good. Any ideas what else I should check?
I am having same problem as u smokie
smokie75 said:
After following directions for all files and then subsequent flashing of your pre-built image xposed installer still reports framework problem. I've gone back and double checked the user:group and perm masks and everything looks good. Any ideas what else I should check?
Click to expand...
Click to collapse
What's reporting a problem? Is it XposedBridge.jar?
If so, try setting the installation mode to recovery (flash manually) and hitting install, then reboot.
Ekkoria said:
What's reporting a problem? Is it XposedBridge.jar?
If so, try setting the installation mode to recovery (flash manually) and hitting install, then reboot.
Click to expand...
Click to collapse
Thanks! That worked!
Thanks for this , works great , now we just need one with busybox preinstalled
Stuck at this point any help?[/ATTACH]
Ekkoria said:
What's reporting a problem? Is it XposedBridge.jar?
If so, try setting the installation mode to recovery (flash manually) and hitting install, then reboot.
Click to expand...
Click to collapse
so will doing this enable gravitybox to work on the turbo?
hmltnjrmy7 said:
Stuck at this point any help?[/ATTACH]
Click to expand...
Click to collapse
You should be able to foloow the instruction you quoted from that point. You should go back and check your permissions, ownership and group for the 4 files. first
Do the change in install mode to manual. Hit install and go to recovery
recovery should give you the dead droid an then reboot
Also don't worry if the group "shell" shows up as something else in app_proces
rayjr13 said:
You should be able to foloow the instruction you quoted from that point. You should go back and check your permissions, ownership and group for the 4 files. first
Do the change in install mode to manual. Hit install and go to recovery
recovery should give you the dead droid an then reboot
Also don't worry if the group "shell" shows up as something else in app_proces
Click to expand...
Click to collapse
Lol the dead droid freaked me out at first, but I'm so happy xposed finally works!!!