Related
Does anyone know how to get Clockwork Recovery on the Xoom so I can flash .zip's? And make nandroid backups. Thx in advance.
Koush is not going to release it until the sdcard works. Making backups to the internal memory is pointless and flashing from internal memory to internal memory is not a great solution at the moment.
-Bauxite
Sent from my Evo 4G
Damn....while agree that making a backup to the internal memory is pointless I just wanted to flash a .zip so that I can get a live wallpaper working. But thanks for the answer.
Sent from my Xoom using XDA App
you dont need to use 'install' zip to install things in the zip, generally flashing zips just cp src dst... take apart the zip, find the updater-script and see if you can just do those steps manually via adb shell (or adb hell if you're feeling evil)
backup to nfs share? smb share? .. would be even nicer
cifs/nfs backup sounds like a project... time to checkout the cwm source!
removed. I had incorrect information.
youngproguru said:
Koush's website indicates that it is now possible to install Zip's directly from ROM manager without having the recovery installed. I'm not sure if this appies to Xoom, however I dont see why not (if you are rooted)
ROM manager does "run: on Xoom.
Check it out:
http://www.koushikdutta.com/2011/01/rom-manager-any-recovery.html
Click to expand...
Click to collapse
This is taken a bit out of context I believe. Koush was stating that you no longer need CWM to do the flashes. He's implemented code that will allow ROM Manager to reboot into other custom recovery mods to do the flashing. At this point though, you still need the recovery mod developer to enable the functionality.
Yep, I think you are correct.
Hey everyone - I figured this might help some folks. It is a CWM installable zip that will restore your system to a completely stock UEKHA (the US retail build for P7310). This includes the stock kernel and recovery image as well.
Heres the instructions:
1) Download this file: http://www.multiupload.com/1KRF1M4CQZ
2) Put the file on your internal storage.
3) Reboot into recovery
4) Execute the Wipe Data/Factory Reset option
5) Choose Install Zip from SD Card
6) Choose Choose Zip from SD Card
7) Select the P7310UEKHA_Restock_v1.zip
8) Sit back, wait about 5 minutes
9) Once the script completes and says "Done", reboot.
10) Welcome to a completely stock US Retail tab
Enjoy.
I just want to ask: Can we flash this on other 8.9s from other regions (namely, an Asian model)?
I'm used to how it is in Maemo where the only differences between firmwares is localization and some preinstalled programs.
Yes you could flash it onto another 8.9 as well, although it should be a P7310 (Wifi only). Just like Maemo, the only differences between regions are localizations and pre-installed apps.
This stock image would not support 3G functionality however, so it would be a bad idea to install it on a P7300.
That's great. Going to flash Clockwork and this once I pick up my P7310 on Tuesday.
Which reminds me - how are Samsung kernels built? I heard that they need to use an initrd (or can the modules be compiled straight into the kernel? or is there a kernel size limitation, which is why an initrd is needed?)
I am truly grateful for this as I rooted and debloated my Tab the very first day lol. This is a great step!
Just flashed my tab with the ROM, works great! Originally had asian ROM on the tab.
Thank you very much! I needed some of the stock original loadable modules after some prior tweaks .
Thanks for the good work!
I was checking the system script used, and I was wondering if this CWM preserve the file/folder permissions as out of the box state or is just 7777 state?
mramirezusa said:
Thanks for the good work!
I was checking the system script used, and I was wondering if this CWM preserve the file/folder permissions as out of the box state or is just 7777 state?
Click to expand...
Click to collapse
Permissions should be out of the box state...the system image was taken from my stock tab directly, and the extract script should leave all permissions in tact.
Hey alterbridge86, it's great to hear you have a GT 8.9 now, that's good news for us
Quick question, how did you dump the ROM and the recovery? I have a GT 8.9 3G from Orange France and I'd like to dump everything before installing CWM to be able to restore to stock if needed.
Thanks! And again, great work!
masterludo said:
Hey alterbridge86, it's great to hear you have a GT 8.9 now, that's good news for us
Quick question, how did you dump the ROM and the recovery? I have a GT 8.9 3G from Orange France and I'd like to dump everything before installing CWM to be able to restore to stock if needed.
Thanks! And again, great work!
Click to expand...
Click to collapse
I ended up dumping it using the CWM I posted in the other thread. The new clockworkmod stores its backups in .tar format, so it makes it really easy to manipulate. Simply create a backup, then if you're feeling adventurous, you can take this flashable zip, replace system.tar and boot.img with the ones created by your backup. The stock recovery is same on all devices, so you can leave the one that is in this package and itwill work for you
Sounds good, thanks I'll give it a try when I have a little more time to play
Hey guys, i did something really stupid today to my 8.9 p7310...I installed that Asia update to it and it placed the tab into a loop and crashes in the settings app when it first starts up. Cant access SD card to install this firmware. I need the Odin firmware to put back to stock I think. Any ideas?
shatty said:
Hey guys, i did something really stupid today to my 8.9 p7310...I installed that Asia update to it and it placed the tab into a loop and crashes in the settings app when it first starts up. Cant access SD card to install this firmware. I need the Odin firmware to put back to stock I think. Any ideas?
Click to expand...
Click to collapse
When you installed the Asian firmware at ODIN, did you remember putting the CSC, PIT, BOOTLOADER to their corresponding places along with the biggest file being at PDA? If you just used the PDA file and not the other files...there's your issue. Once you successfully ODIN, flash this specific CWM Recovery and then you can either choose Stock (this thread) or the Overcome ROM.
Yea just did the pda. The instructions only said the pda. Doesnt matter anyway i am back to stock used adb to load the stock zip to sdcard and loaded
shatty said:
Yea just did the pda. The instructions only said the pda. Doesnt matter anyway i am back to stock used adb to load the stock zip to sdcard and loaded
Click to expand...
Click to collapse
Good to know you made it. The same happened to another user. Those instructions aren't correct.
Sent from my GT-P7310
Help getting China based GT-7310 to US stock
Hello,
I recently bought a GT-7310 in China, and want to get this to stock US using your method. I had a question on step #2.
2) Put the file on your internal storage.
How do I get the file to the internal storage and where is that location? I don't see an /SDCARD folder anywhere when browsing the tab in Windows 7. I have the latest USB drivers installed. I tried to push the file to /SDCARD using ADB but Android SDK tools doesn't recognize my tab. Are there any other ways to get the file to internal storage?
Thanks.
zinzino said:
Hello,
I recently bought a GT-7310 in China, and want to get this to stock US using your method. I had a question on step #2.
2) Put the file on your internal storage.
How do I get the file to the internal storage and where is that location? I don't see an /SDCARD folder anywhere when browsing the tab in Windows 7. I have the latest USB drivers installed. I tried to push the file to /SDCARD using ADB but Android SDK tools doesn't recognize my tab. Are there any other ways to get the file to internal storage?
Thanks.
Click to expand...
Click to collapse
When you plug in the tab, it connects via MTP to Windows. Then you can only get to the internal storage, just drop it in there. You'll see all the default folders (music, videos, etc.) so you'll know your in the right place.
Thank you. I got the file to SD Card, went into recovery, executed the wipe data/factory reset option. After the wipe data/factory reset is complete, I selected the option "apply update from /sdcard". I selected that and I get the following error:
E:error opening /data/media: No such file or directory
Any ideas?
Thanks.
You need to use CWM recovery, not the stock recovery.
Hello,
I don't know if you noticed but JCSullins made a new cwm6 based recovery.
If you want to give it a try I've made a cwm flashable update archive,
**Removed - wait for JCSullins official release**
menthe said:
Hello,
I don't know if you noticed but JCSullins made a new cwm6 based recovery.
If you want to give it a try I've made a cwm flashable update archive,
https://www.dropbox.com/s/hzxb7fswws5l0ss/update-cwm6_tenderloin-20121204.zip
Click to expand...
Click to collapse
For those not in the know, it is recommended to update your recovery and essential if you plan to update to cm10. This fixes s file system corruption bug that shows up when expanding the partition in preparation for cm10.
Sent from my HP TouchPad using Tapatalk 2
menthe said:
Hello,
I don't know if you noticed but JCSullins made a new cwm6 based recovery.
If you want to give it a try I've made a cwm flashable update archive,
https://www.dropbox.com/s/hzxb7fswws5l0ss/update-cwm6_tenderloin-20121204.zip
Click to expand...
Click to collapse
Thanks for your installable zip! I had been trying to get things updated and couldn't get the uImage written to the /boot dir on my TP.
Went through adb (reinstalling drivers, connecting,etc.) then tried renaming and copying to /boot through ES File explorer with SU permissions, but it still wouldn't let me write to the /boot folder. I'm not quite sure why - I thought SU permissions allowed me to write to the /boot folder, but I guess not... I'll have to further investigate. I'm still noobish on quite a lot here.
Needless to say, your zip file helped and was finally able to get CWM6 updated on my TP. Thanks button pressed! :good:
"Went through adb (reinstalling drivers, connecting,etc.) then tried renaming and copying to /boot through ES File explorer with SU permissions, but it still wouldn't let me write to the /boot folder. I'm not quite sure why - I thought SU permissions allowed me to write to the /boot folder, but I guess not... I'll have to further investigate. I'm still noobish on quite a lot here."
Click to expand...
Click to collapse
Open terminal
type
su
umount -o remount,rw /boot
then use es file explorer.
chadster1976 said:
Thanks for your installable zip! I had been trying to get things updated and couldn't get the uImage written to the /boot dir on my TP.
Went through adb (reinstalling drivers, connecting,etc.) then tried renaming and copying to /boot through ES File explorer with SU permissions, but it still wouldn't let me write to the /boot folder. I'm not quite sure why - I thought SU permissions allowed me to write to the /boot folder, but I guess not... I'll have to further investigate. I'm still noobish on quite a lot here.
Needless to say, your zip file helped and was finally able to get CWM6 updated on my TP. Thanks button pressed! :good:
Click to expand...
Click to collapse
Rom Toolbox lite will allow you to .
*sigh*
"... At this point I'm just putting out a uImage to allow those who are
comfortable swapping out the uImage to test." (less than 24 hrs ago on rootzwiki)
I was hoping to get some feedback from the "more advanced" users testing this before creating an
installable zip and unleashing it on everyone. So far, virtually no feedback.
I flashed it and now I'm soft bricked. Can't boot into sk8's CWR6, CM10 or anything.
Lesson learned, ask developers before posting there work
Sent from my Galaxy Nexus using xda app-developers app
It likely not the CWM6 that did it but the boot partition full. If you have an extra webos kernel, some moboot themes, TWRP, and then this new larger uImage for CWM you will likely run out of space.
Probably should put that warning here it's pretty important people realize it and/or add a script to remove TWRP, to prevent issues with this zip.
@jcsullins +1 Feedback. Installed your CWM uImage manually. Mounted as mass storage in CWM, copied files, Installed latest CM10 12/05(over older CM10 installed with Acme3), Installed Gapps, Installed Camera Preview 3 patch, Installed WEBCM10, cleared both caches in CWM and noticed no issues during all the processes.
I ACMEU wiped and ACME3'd the whole deal back on w/new recovery. It needed the clean up anyways and I had a NAND from yesterday.
Nice, thanks JC.
Roland Makes oopsy
jcsullins said:
*sigh*
"... At this point I'm just putting out a uImage to allow those who are
comfortable swapping out the uImage to test." (less than 24 hrs ago on rootzwiki)
I was hoping to get some feedback from the "more advanced" users testing this before creating an
installable zip and unleashing it on everyone. So far, virtually no feedback.
Click to expand...
Click to collapse
Thank you for taking the time to create this great new CWM6. I have been really enjoying the new looks and graphics. I have tested flashing different zips and Roms. I have made and restored Nandroid backups and even restored older CWM5 backups with CWM6. I do this to try and help but sometimes I really step in $#@# trying to help, like with the 4.2gapps.
Sorry about being so anxious to get this out to the public. I have had a lot of complaints about Bricked TouchPads and would like to get the word out about the problem and how to fix/prevent it.
I feel very responsible for the people affected due to me making an install video without knowledge of the corruption issue beforehand.
I wanted to make a video explaining that there was an issue but to fix it they can, Backup, uninstall, reinstall and restore. To prevent future issues I want to included this in my install instructions. They would of course need your New CWM6 to do this and I have been eagerly awaiting this fix.
Sorry about all my stupid mistakes, I get a bit over excited about Tech stuff at times. Please accept my sincerest apologies.
jcsullins said:
*sigh*
"... At this point I'm just putting out a uImage to allow those who are
comfortable swapping out the uImage to test." (less than 24 hrs ago on rootzwiki)
I was hoping to get some feedback from the "more advanced" users testing this before creating an
installable zip and unleashing it on everyone. So far, virtually no feedback.
Click to expand...
Click to collapse
I'm sorry, but I didn't see your post in Rootzwiki or I would have posted there.
This cwm has worked flawlessly. I haven't had a chance to try all the new features, but the ones I did try worked fine.
Thanks so much for this. The old 5.0.2.6 was starting to show its age. I hope this cwm does away with the sporadic partitioning problems I'd been seeing.
jcsullins said:
*sigh*
"... At this point I'm just putting out a uImage to allow those who are
comfortable swapping out the uImage to test." (less than 24 hrs ago on rootzwiki)
I was hoping to get some feedback from the "more advanced" users testing this before creating an
installable zip and unleashing it on everyone. So far, virtually no feedback.
Click to expand...
Click to collapse
In my limited testing to this point, I've not uncovered any issues. I flashed a couple of different roms, gapps and misc zipfiles and all were fine. I also made a nandroid and a subsequent restore which also worked fine.
I like the idea that that the default backup method was tar as opposed to dup, as I am more comfortable with that. Also, was pleasantly surprised to find that USB storage mount was working, I thought that this was "broken" in CWM 6.x. I transferred files back & forth on my PC with no problem.
The only oddity I came across was when trying to view the files in my nandroid backup folder in ES File Explorer, or the stock CM File Manager, the 2 android_secure.vfat.tar files were not visible. Yet they were visible in Root Explorer and of course, when I transferred it over to my PC for safekeeping, they were there.
That's about it for now. Great job as always, JC. Thanks.
Mike T
New Backup Options
I am just trying some of the new backup options. It seems that we have a choice in the backup we make now, the Default is Tar and the 2nd option is Dup. There is also a "free unused backup data" option, since the backups appears to be in several files. I wanted to backup my backups but I am in over my head here and don't know much about the new backup options. Has anyone else had a chance to take a look? I like the spinning ball animation in the Androids stomach while I make and restore my backups:good: I can use my old CWM5 backups but now I don't know what to do about the new ones. Could anyone more experienced help me out please:fingers-crossed:
webdroidmt said:
In my limited testing to this point, I've not uncovered any issues. I flashed a couple of different roms, gapps and misc zipfiles and all were fine. I also made a nandroid and a subsequent restore which also worked fine.
I like the idea that that the default backup method was tar as opposed to dup, as I am more comfortable with that. Also, was pleasantly surprised to find that USB storage mount was working, I thought that this was "broken" in CWM 6.x. I transferred files back & forth on my PC with no problem.
The only oddity I came across was when trying to view the files in my nandroid backup folder in ES File Explorer, or the stock CM File Manager, the 2 android_secure.vfat.tar files were not visible. Yet they were visible in Root Explorer and of course, when I transferred it over to my PC for safekeeping, they were there.
That's about it for now. Great job as always, JC. Thanks.
Mike T
Click to expand...
Click to collapse
I was having the same issues trying to view the files from ES File Explorer, and from the PC. I feel like such a noob
RolandDeschain79 said:
I am just trying some of the new backup options. It seems that we have a choice in the backup we make now, the Default is Tar and the 2nd option is Dup. There is also a "free unused backup data" option, since the backups appears to be in several files. I wanted to backup my backups but I am in over my head here and don't know much about the new backup options. Has anyone else had a chance to take a look? I like the spinning ball animation in the Androids stomach while I make and restore my backups:good: I can use my old CWM5 backups but now I don't know what to do about the new ones. Could anyone more experienced help me out please:fingers-crossed:
I was having the same issues trying to view the files from ES File Explorer, and from the PC. I feel like such a noob
Click to expand...
Click to collapse
Hi Roland, hope all is well with you. I am not having a problem viewing my nandroid files on my PC, just from the apps I mentioned within Android.
Anyway, just a quick blurb on the 2 backup methods of .tar & .dup. Tar is what we are used to with the older CWM version, .dup is something new to CWM and fairly similar to the way a windows PC does backups. I'm no expert but in a nutshell, .tar backs up everthing each time you do a nandroid, .dup does incremental backups each time and stores the data in "blob" files which become very large. With the .dup method, because it's only doing incremental, backup time is faster than .tar but with the large "blob" folders of data, it's a PITA to move to your PC for safekeeping.
With all the flashing I do, I'm constantly moving nandroids back & forth, so I prefer .tar at this time. But as usual, YMMV. Take care.
Mike T
.dup & .tar enlightenment
webdroidmt said:
Hi Roland, hope all is well with you. I am not having a problem viewing my nandroid files on my PC, just from the apps I mentioned within Android.
Anyway, just a quick blurb on the 2 backup methods of .tar & .dup. Tar is what we are used to with the older CWM version, .dup is something new to CWM and fairly similar to the way a windows PC does backups. I'm no expert but in a nutshell, .tar backs up everthing each time you do a nandroid, .dup does incremental backups each time and stores the data in "blob" files which become very large. With the .dup method, because it's only doing incremental, backup time is faster than .tar but with the large "blob" folders of data, it's a PITA to move to your PC for safekeeping.
With all the flashing I do, I'm constantly moving nandroids back & forth, so I prefer .tar at this time. But as usual, YMMV. Take care.
Mike T
Click to expand...
Click to collapse
Thank you very much for the detailed response. I’m feeling good now that I am starting to understand the new recovery. I also really liked having those individual .tar backups:good:, I made one for each version of CM. I wonder how .dup backups will affect the free space on my device. I also backup a lot but I did find that i was able to restore the older CWM5 backups without a problem. I will probably just keep the older CWM5 .tars for CM7, CM9 and do my CM10 backing up with the newer .dup. Time to transfer some backups:victory:
Can we maybe get rid of the link in op? Jc has stated this was only for testing, you shouldn't host a devs work without permission, and maybe for the fact of it will soft brick a TP? Just saying....
Sent from my HTC VLE_U using xda app-developers app
Sorry for possibly misunderstanding but is it recommended to use this yet due to possible corruption issues with older versions of CWM or only intended for testing atm? I've been meaning to ACME uninstall the TP and reinstall CM10 clean again and if this newer version of recovery is recommended for flashing I'll throw it on there while I'm at it
Thx JCSullins! :fingers-crossed:
jcsullins said:
*sigh*
"... At this point I'm just putting out a uImage to allow those who are
comfortable swapping out the uImage to test." (less than 24 hrs ago on rootzwiki)
I was hoping to get some feedback from the "more advanced" users testing this before creating an
installable zip and unleashing it on everyone. So far, virtually no feedback.
Click to expand...
Click to collapse
Hello,
Sorry for that :/
I haven't seen your rootzwiki post and so far I was just willing to help users to install it
easily (seems that was my mistake :x) because after I gave it a try it solved the issues
I was having with the previous CWM one. There is just one thing that disturb me, in
Backup and Restore menu, 'choose backup format' should be rename in something like
"choose default backup format".
That's just my 2cents and besides this all functions work well, thanks for your hard work.
I'll remove the link from the OP post and wait for your public release
Sincerely, menthe.
Has anyone tried the adb sideload yet?
When attempting to sideload I get: * failed to write data 'protocol fault (no status)' *
Any other adb commands I issue are met with "error:closed"
I am stuck here because I don't have a power button to do a hard reset... please someone tell me this function is working and I am just doing something wrong. My TP has a full charge and I don't feel like waiting 8hrs for it to die so it can be reset.
Edit: just took the whole thing apart and pulled the battery
WARNING: BEFORE YOU DO ANYTHING PLEASE READ THIS THREAD AND MAKE SURE YOU KNOW WHAT YOU ARE DOING. I AM NOT RESPONSIBLE FOR ANY DAMAGE TO YOUR PHONE.
A few days ago I came across this thread which made me think and try. At the beginning I couldn't flash the zips necessary for making backups without rebooting to recovery .
What you will need:
1.Bootloader unlocked and a rooted phone . If you don't have any of them please read here and here
2.Busybox
3.A root explorer of your choice
4.A terminal emulator app
5.The 2 files from the zip attached
6.Patience
Open your root explorer extract and copy the 2 files attached to /system/bin and set permissions 755( that's rwxr-xr-x).
Reboot your phone.
Open Terminal app and type su to obtain root followed by onandroid.
Sit back and relax while the script backs up your rom.
All thanks go to ameer1234567890 who gave us the Online Nandroid . I only found the thread and also found the method to copy the files to Razr I.
When i'll have some time i'll try to make a flashable zip for the lazy ones
As promised here are the zips for flashing from recovery with update binary working with the Razr I. I have only tested with CWM, but they should work with TWRP as well.
I suppose everyone knows what to do, but just in case someone new tries it:
-copy the 2 zips to you internal storage or external sdcard
-reboot to recovery
-select install zip from sdcard(now choose the location of your files)
-select zip
-install
-reboot
Enjoy
nandroid,etc, assistance
free2live said:
As promised here are the zips for flashing from recovery with update binary working with the Razr I. I have only tested with CWM, but they should work with TWRP as well.
I suppose everyone knows what to do, but just in case someone new tries it:
-copy the 2 zips to you internal storage or external sdcard
-reboot to recovery
-select install zip from sdcard(now choose the location of your files)
-select zip
-install
-reboot
Enjoy
Click to expand...
Click to collapse
Is this the best way to do a " nandroid " - I have been part of this site for quite some time , read numerous sites, but i have a very bad memory problem and that's why i have many text documents setup to the point i am confused. Right now I have an AT&T S4 which has a bad IMEI, so I want to use it as a test phone, but it has been updated to 4.3 -which from what I understand I would need to downgrade back to 4.1.2 order to unlock the phone via the dial pad. I was able to accomplish that one time when I first got a Samsung S4 and did it via the dial pad before the OTA came out for 4.3.
I also own a S3, also AT&T, so i can learn how to to root and unlock and use CWR or TWRP and than learn ROMS. I know I need to make a backup before I do anything, and also constantly reading the " Noob " general forums for both phones. I also am familiar with Samsung Kies, which does a backup but I don't think it's the same as this nandroid i have been reading about.
Thank you or taking out the time and reading my post. I will check back to see if anyone had some time to give me some direction or an answer to my problem with " nandroid" or if someone even could touch up on any subjects I have mentioned. Please don't think I haven't spent hrs of time on YouTube, Google, Howard forums and especially here on XDA.
DISCLAIMER
The process of flashing a custom recovery/kernel/firmware may and will trigger your device's Knox Counter. Neither XDA nor I can be held responsible for your actions. Proceed with caution. During this process you will lose all your settings and apps. As long as you follow the instructions, your device's storage, internal and external, won't be touched
Still not compatible with x64 systems! Not compatible with Samsung 5.1.x (sdk22) ROMs!
Hello, Ladies and Gentleman
Many people seem to have a hard time to understand how all of this here on XDA works. I constantly get PM's from users, asking how to do the most basic stuff like flashing a .zip or stock firmware via Odin. Usually, I don't even read them and just hit delete. I know it's not ok to deny people help, so I decided to show you how you can get Xposed working on your TW based stock or custom ROM since it's the most frequently asked question I get.
It's nothing you couldn't do if you'd just....
We're going to use @arter97's customized Xposed Framework as the one made by @darkera13 needs the user to manually modify and replace files which may be too complicated for some.
Preparation
-READ EVERYTHING OVER AND OVER AGAIN.
-A custom recovery System like TWRP or CWM (PhilZ or Stock)
-A deodexed ROM. It's the only way to go. YOU NEED A DEODEXED ROM. If your ROM is not deodexed and you flash the framework, you'll end up in a bootloop. To deodex your existing ROM carefully follow Post #2
Here are a few made by XDA Senior Member @_alexndr
Stock deodexed for SM-N9005 Galaxy Note 3 International Qualcomm.
Stock deodexed for SM-G900F Galaxy S5 International Qualcomm
-And the framework itself from here
[UNOFFICIAL] Xposed for Samsung Lollipop by arter97
-Flash a custom recovery system of your choice. This is listed under preperation on purpose since this guide is about getting Xposed on your TW Lollipop device. A guide on how to get a custom recovery system is most certainly available in your device's forum.
-Store the ROM and the Framework in an easy to find folder, which we're gonna call "folder x". It doesn't matter where you store it (ext. SD or int. SD)
The Fun Part
-Boot into your custom recovery and make a full wipe:
TWRP users: "Wipe>Advanced Wipe> Tick System, Data, Cache, Dalvik Cache> Slide to format.CWM users: "Mounts and Storage> hit Format /System; hit Format /Data; hit Format /Cache.
-Still in recovery system, install, or flash the files we put in folder x;
TWRP users: "Install> Navigate to folder x and choose the ROM file first> Add Zip> now choose the Xposed Framework from folder x> Slide to flash.CWM users: "Install Zip> Choose zip from /sdcard if folder x is on internalt storage or /storage/sdcard1 if folder x is on ext. storage (SD-Card)>choose the ROM file first> -Yes - install ROMXY.zip.Do the same with the Xposed Framework zip file.
-Still in recovery system, reboot device and wait for it to boot. It can take up to 20 minutes. Enjoy Xposed on your Samsung TouchWiz Lollipop ROM.
-Stuck in a bootloop? Try this and repeat the process.
XDA Senior Member @Honzze kindly pointed out to keep following in mind; You have to start JoelDroid Lollipop Batch Deodexer with Admin permissions. Otherwise this error might return "path variable" of Java "is not set".
Deodexing your existing ROM without having to flash an entire ROM
As the title says, with this awesome guide by XDA Senior Member @townsenk you don't have to reflash an entire new ROM to your device. Instead, youll just deodex those parts of your System which need to be modified in order to get Xposed working. You don't necessarily have to perform a full wipe if you do it this way. But if you encounter fc's or end up in a bootloop, you know what to do
Guide for this guide:
Regarding point 1: "...launch a DOS shell..." just means, you need to open the so called "CMD" programm in Windows. To "launch a DOS shell" or CMD from within a folder, you simply have to hold down the shift key and right click in that folder. The context menu will show an entry "open command window here". And that's it! (Windows XP users may have to search the internet for another solution)
For Galaxy S5 and Note 3 users: If ADB returns "device offline" or an empty line after "List of devices attached" make sure your using a USB 2.0 data cable on a USB 2.0 port
townsenk said:
How to DeOdex YOUR (...) 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.
(...)
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 (...) 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.
Click to expand...
Click to collapse
Since I no longer own this device, I'm retiring from this thread as of now. Hope I could help you.
Don't know if someone can help me as you stated that you're retired from this thread.
I did every step you do mentioned here (for self deodexing existing rom)
I did everything successfully and deodexed my files with 2.5 deodexer, putted files in the system folder to the 7zip folder and sent to my device and flashed zip, cleaned cache and dalvik and it stuck on booting for about 15 minutes. I know, it takes alot time during rebuildup of cache, but guys, it's 15 minutes! for me, if i cleanup cache and the dalvik/art cache, it just takes 1minute on boot screen to show up the image of each apps cache, but i just sat there with lots of patient for 15 minutes or a bit more and still same, stuck in same crappy booting logo.
I did restore my system files, now i'll try to retry it and send it again. Im suspicious of the zip file being corrupted during trasmitting to Device, however install was a big success so im very sure it wasnt corrupted. I'll do 2nd test and see it again if it's happening again.
If it does, i'll most likely try to figure out other ways to deodex as there is already deodexed roms out there, so they must have done is somehow.
Thanks, hope someone can help me out with this.
P.S: My adb works fine, i got usb drivers for my device, i got usb debug on, i got lots of space on phone, i got TWRP recovery which got very high compatibility when it comes to install anything from zip via recovery where almost all roms do work stable with TWRP.
omg brilliant @nitrous² ! thanks so much! its been days i keep trying to deodex with others tool...
Sachitoge said:
Don't know if someone can help me as you stated that you're retired from this thread.
I did every step you do mentioned here (for self deodexing existing rom)
I did everything successfully and deodexed my files with 2.5 deodexer, putted files in the system folder to the 7zip folder and sent to my device and flashed zip, cleaned cache and dalvik and it stuck on booting for about 15 minutes. I know, it takes alot time during rebuildup of cache, but guys, it's 15 minutes! for me, if i cleanup cache and the dalvik/art cache, it just takes 1minute on boot screen to show up the image of each apps cache, but i just sat there with lots of patient for 15 minutes or a bit more and still same, stuck in same crappy booting logo.
I did restore my system files, now i'll try to retry it and send it again. Im suspicious of the zip file being corrupted during trasmitting to Device, however install was a big success so im very sure it wasnt corrupted. I'll do 2nd test and see it again if it's happening again.
If it does, i'll most likely try to figure out other ways to deodex as there is already deodexed roms out there, so they must have done is somehow.
Thanks, hope someone can help me out with this.
P.S: My adb works fine, i got usb drivers for my device, i got usb debug on, i got lots of space on phone, i got TWRP recovery which got very high compatibility when it comes to install anything from zip via recovery where almost all roms do work stable with TWRP.
Click to expand...
Click to collapse
Same happened to me.... Did you solved this problem?
Maurizio1953 said:
Same happened to me.... Did you solved this problem?
Click to expand...
Click to collapse
Nope, i ended up using CM12 (at that time, right now i got cm13 update).
Well i had to deodex apps to get xposed on TouchWiz, but i failed and didn't get headache because of the Xposed modules being not really well compatible on TouchWiz, so i jumped to CM, i find it more stable, and the CM13 is insane because it saves so much battery at stand by, compared to lollipop, the Android 6.0.1 Marshmallow is the biggest update in android history, that saves hell lot of battery (it can be also maybe because i don't have Xposed Framework in recent rom).
Anyway, im tired of it, and i don't need to hassle with Link2Sd because of Android Marshmallow offering to mount the SD Card, in the end, all my needs are being offered in this (for me) huge, best android update, being Marshmallow.
Try it i would say, so amazing.
Ok i would like to go to cm13 as you but i stil need the support to the gear s smartwatch so i decided to stay with touchwiz without xposed.