Start by giving cred to the devs:
Antibyte at samdroid who made this possible
Seraphimserapis that implementd it first on SGS roms.
I tried it with I9000XWJG5 deoxed rom: modaco R3
Should be compatible wit all deoxed rom (but make sure to make a nandroid backup first)
Install from Clockwork recovery
Ps: JIT is not fully stable....
Update, you may need to put the 2 folders in your custom rom to make this functional...
{
"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"
}
Thank you, just what I was looking for - will be downloading and flashing just after I finish work
Does the qudrant finish on this one? I know it didnt on previous implementation.
Any real improvement in speed? and Any known bugs?
BTW, Do I just copy zip to/sdcard, reboot using rom manager and flash it from there?
dupel said:
Does the qudrant finish on this one? I know it didnt on previous implementation.
Any real improvement in speed? and Any known bugs?
BTW, Do I just copy zip to/sdcard, reboot using rom manager and flash it from there?
Click to expand...
Click to collapse
There is some problems with the current JIT implemention for SGS.
Some benchmark software will crash, incl quadrant.
Depending on your rom, you can flash it from Clockwork recovery OR in some cases you need to edit your full custom rom and put the 2 folders inside and resign the rom.
MAKE sure u take a nandroid backup. May save some work
DocRambone said:
There is some problems with the current JIT implemention for SGS.
Some benchmark software will crash, incl quadrant.
Depending on your rom, you can flash it from Clockwork recovery OR in some cases you need to edit your full custom rom and put the 2 folders inside and resign the rom.
MAKE sure u take a nandroid backup. May save some work
Click to expand...
Click to collapse
Yup, just did a back up
Downloading SamSet ROM right now (if im not mistaken the only deodexed ROM for JM2).
So, I will report success/failure in probably an hour.
PS. If we have kernel for ext4 stall fix, do we have to reapply the second (adb) part of the fix to recreate the link with sd card, or everything should be left unaffected?
dupel said:
PS. If we have kernel for ext4 stall fix, do we have to reapply the second (adb) part of the fix to recreate the link with sd card, or everything should be left unaffected?
Click to expand...
Click to collapse
Should be fine, at least with Modaco R3 it was...
I flashed this on JM2 using clockwork 'install zip'
It doesn't seem to have had much effect, 50 points on quadrant at most.
Which combined with the sdcard fix is now about 1750
android53 said:
I flashed this on JM2 using clockwork 'install zip'
It doesn't seem to have had much effect, 50 points on quadrant at most.
Which combined with the sdcard fix is now about 1750
Click to expand...
Click to collapse
Do you have an Deoxed rom, eg samset?
samset 1.6 yes. i dont think this has worked. i still only get 8.5 MFLOPS in linpack
android53 said:
samset 1.6 yes. i dont think this has worked. i still only get 8.5 MFLOPS in linpack
Click to expand...
Click to collapse
Then you have to install samset again with the 2 folders from JIT incorporated.
Open the samset.zip with winrar (or similiar), and drop the 2 folders from JIT into /system, resign the zip and install again.
i have JM2 with Samset 1.6 and the ext4 sdcard fix.
I backed up with nandroid, placed the zip in the root directory on the phone. ran clockwork recovery, advanced, apply zip.
All fine, rebooted up no problem
It hasn't worked though
*edit*
Ill try that
android53 said:
i have JM2 with Samset 1.6 and the ext4 sdcard fix.
I backed up with nandroid, placed the zip in the root directory on the phone. ran clockwork recovery, advanced, apply zip.
All fine, rebooted up no problem
It hasn't worked though
*edit*
Ill try that
Click to expand...
Click to collapse
Ok, i have not tried it in any jm2 rom, may or may not be functional.
Good luck tho
i just repacked samset and updated it.
No change to MFLOPS
The update went very quickly for something thats 100mb+ (5 seconds or less)
maybe clockwork 'install zip from file' isn't working properly
android53 said:
i just repacked samset and updated it.
No change to MFLOPS
The update went very quickly for something thats 100mb+ (5 seconds or less)
maybe clockwork 'install zip from file' isn't working properly
Click to expand...
Click to collapse
It's a known bug, you need to use the standard samsung recovery method, by renaming the modified rom as update.zip.
How did you resign the rom?
If i replace the update.zip in the root directory that means i cant use nandroid to backup if things go wrong surely
android53 said:
If i replace the update.zip in the root directory that means i cant use nandroid to backup if things go wrong surely
Click to expand...
Click to collapse
backup using clockworkmod, then move the update.zip into the root
i replaced the root one, its updating and taking much longer this time. i wont be able to recover though
DocRambone said:
Then you have to install samset again with the 2 folders from JIT incorporated.
Open the samset.zip with winrar (or similiar), and drop the 2 folders from JIT into /system, resign the zip and install again.
Click to expand...
Click to collapse
Yup, the same issue - didn't work.
Two questions - can we manually drop the 2 folders (bin and lib) to system ourselves?
and how do we sign the zip file?
android53 said:
i replaced the root one, its updating and taking much longer this time. i wont be able to recover though
Click to expand...
Click to collapse
did you not take a backup previously? I took a standalone backup using clockworkmod, so if anything goes wrong, I can reflash back to stock, root the phone, reinstall clockworkmod and restore my backup before trying again
it worked this time. You have to use the standard android boot menu and use the update.zip in the root, clockwork one doesn't work.
It is somewhat unstable in benchmarks, quadrant wont complete, but goes through the cpu tests about twice as fast as before
Superpi is at about 1.8k ms
linpack is anywhere between 12 and 13 MFLOPS
linpack crashed once, need to do some stability testing
Also strangely setcpu long bench time has actually got worse, but short bench time has improved
Related
{
"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"
}
ClockworkMod 5.0.2.8 Based
-Rogue Touch Recovery v1.5.0-
Presented By-
TDR
Bazar6
Steady Hawkin
General-
This recovery brings the following game changing features to the table:
Full Touch support
Overhauled UI
Backup/Restore and flash from USB Drive
Backup/Restore and flash from internal storage (/sdcard)
See Changelog for full list
Important Info-
By default your Xoom will your MicroSD card for nandroids and flashing. To use a USB drive or your internal storage, go to Mounts and Storage and select the location of your choice. *Please note, although you can use your internal storage for nandroids, it is not recommended.*
By default /data/media (/sdcard) will be skipped during wipe, backup, and restore.
This recovery does not support encrypted partitions, do not use this recovery if you use device encryption in ICS
Install Instructions-
-Make a nandroid in your current recovery then proceed
-Download zip file from link below
-Place zip on Micro SDcard
-Reboot into existing recovery
-Choose install zip and select the Rogue Recovery
-Confirm file, wait for it to finish flashing, then reboot
-Reboot back into recovery and bask in the Rogue glory!
Download-
Rogue Recovery v1.5.0 (RC3)
Source-
Can be found on Github- HERE
Thank You-
Koush
CyanogenMod Team
j-r0dd
Donate to Team Rogue HERE
Stay Tuned For Future Releases!!!
-Partial Changelog-
1.5.0 (RC3)
+Updated base to CWR 5.0.2.8
+Full touch support
**touch menu selections, use on screen buttons, or use volume rockers and power button
***swipe cursor movement (swipe left or right to go back)
+New CM style blue theme
+Large Roboto font
*Fixed text flow
+Changed menu style and layout
+Large backups (>2.1GB) should work now
*Note: 4GB FAT32 limit still applies
+Updated kernel, busybox
+UMS supported
+Fixed script assert toggle (thanks Sam Mortimer)
-Removed backup internal storage (buggy, storage limits)
-Removed partition storage (dangerous)
1.3.0
+Updated base to CWR 5.0.2.7
+Revised backup menu with option to switch to internal storage
*Fixed battery level display
*Using the wipe menu no longer dumps you back to the main menu automatically
1.2.0
+Based on ClockworkMod Recovery v5.0.2.3 + Rogue Kernel 1.3.1N
+New tar-based nandroid images
+Option to flash zips from internal storage directly in the Install menu
+Confirmation screen when storage free space might be too low
*Progress indication disabled by default again for speed (create /sdcard/clockworkmod/.hidenandroidprogress to enable progress)
**Old yaffs-based images still supported
1.1.1
*Fixed Advanced Backup
1.1.0
+Added option to mount USB drive on /sdcard without needing to remove the micro SD card (Mount menu > Mount USB drive on /sdcard)
+Ability to toggle between internal and regular storage (Mount menu)
+Warning before backing up to internal storage
+Disabled formatting, partitioning and USB mounting of internal storage
*Upstream patches
1.0.0
+Based on ClockworkMod Recovery v4.0.1.5 & Launchpad kernel 1.3.0
+New menus from j-r0dd's Nexus S recovery (fewer clicks!)
+Recovery will try to mount external USB drives (FAT format only) as long as Micro SDcard is removed
+Handle /data/media (thanks solarnz)
+Added a toggle to switch on or off backup/restore of /data/media (off by default)
+Will try to mount a USB drive if no micro SD card is present
+Battery level notification in confirmation screen
-Big Thanks To The People Who Donated-
goldiefish
***If you make a donation, please post your name so we can thank you***
awesome. will be trying this on my wife's xoom. i think this my first time posting first (after the OP of course)!!!
Wow!!!! Thanks a lot!!!
Sent from my MZ601 using xda premium
Nice one! Cheers Steady
flashed it. looks nice. getting the following error:
E:Can't mount /cache/recovery/command
is that alright?
Max_Pain said:
flashed it. looks nice. getting the following error:
E:Can't mount /cache/recovery/command
is that alright?
Click to expand...
Click to collapse
When are you getting that error?
First time I booted into recovery after flashing it. In the main page.
Sent from my HTC Evo 3D on the MetroPCS 1x network...
Max_Pain said:
First time I booted into recovery after flashing it. In the main page.
Sent from my HTC Evo 3D on the MetroPCS 1x network...
Click to expand...
Click to collapse
Make sure your micro sdcard is in your xoom and try rebooting into recovery.
Will have to try this thx Steady. See you in #xoom.
Steady Hawkin said:
Make sure your micro sdcard is in your xoom and try rebooting into recovery.
Click to expand...
Click to collapse
the card was already in the xoom. i rebooted into recovery again and this time i didnt get the message. maybe because it was the first time booting into it? seems to be fine now.
Looks sweet. Really dig the Team Rogue logo.
Max_Pain said:
the card was already in the xoom. i rebooted into recovery again and this time i didnt get the message. maybe because it was the first time booting into it? seems to be fine now.
Click to expand...
Click to collapse
Strange, let me know if it happens again.
gerald410 said:
Will have to try this thx Steady. See you in #xoom.
Click to expand...
Click to collapse
Lookin forward to it G!
musashiken said:
Looks sweet. Really dig the Team Rogue logo.
Click to expand...
Click to collapse
Thanks for your support
couple noob questions...can we get screen shots? Lol
Also does this recovery play nice for those not using launchpad kernel?
Can I rename my backup using this? When I manually change my backup names with my current recovery they end up having a md5 error and I can't use them anymore
Finally does this mean xoomers can use ROM manager without horrible consequences or is the sd card location still the main problem for us?
Awesome! Thanks to you guys for all of your hard work.
rockhumper said:
couple noob questions...can we get screen shots? Lol
Also does this recovery play nice for those not using launchpad kernel?
Can I rename my backup using this? When I manually change my backup names with my current recovery they end up having a md5 error and I can't use them anymore
Finally does this mean xoomers can use ROM manager without horrible consequences or is the sd card location still the main problem for us?
Click to expand...
Click to collapse
-I might try and post a screenshot later.
-It plays nice with LP or Tiamat
-I have not had any issues renaming backups in either recovery, are you using a program like Root Explorer to change it? Make sure your using correct punctuation.
-I personally do not use Rom Manager, but I have not heard of issues with either recovery using Rom Manager. Just make sure your on either this recovery, or Solarnz recovery.
Steady Hawkin said:
-I might try and post a screenshot later.
-It plays nice with LP or Tiamat
-I have not had any issues renaming backups in either recovery, are you using a program like Root Explorer to change it? Make sure your using correct punctuation.
-I personally do not use Rom Manager, but I have not heard of issues with either recovery using Rom Manager. Just make sure your on either this recovery, or Solarnz recovery.
Click to expand...
Click to collapse
Thanks steady. The ROM manager thing is when flashing updates...it actually makes back up a finebut they end up on the internal sd card...but anyways I will just just stock with the current recovery I think. the naming thing is being done through root explorer but I am not sure why changing the name makes the file inaccessible...oh well, not trying to side track your thread. Thanks for the great work
rockhumper said:
Thanks steady. The ROM manager thing is when flashing updates...it actually makes back up a finebut they end up on the internal sd card...but anyways I will just just stock with the current recovery I think. the naming thing is being done through root explorer but I am not sure why changing the name makes the file inaccessible...oh well, not trying to side track your thread. Thanks for the great work
Click to expand...
Click to collapse
No worries bro, I think I know what the issue is. Try and get in the habit of booting into recovery and using the backup option inside recovery to make your nandroids. After that, use root explorer to change the name. If you do that, you should be golden.
Steady Hawkin said:
No worries bro, I think I know what the issue is. Try and get in the habit of booting into recovery and using the backup option inside recovery to make your nandroids. After that, use root explorer to change the name. If you do that, you should be golden.
Click to expand...
Click to collapse
Yeah that is what I have been doing because in my current recovery when I make a back up it does not let me name the back up. It just assigns a date and time name to it. I don't typically use ROM manager with the Xoom at this point. The name change shows up when I boot back into recovery but then when I load it I get md5 sum error.
Maybe I will mess with it tonight some to find the problem.thanks guy!
New Recovery for are phone and i must say because im the first to use it i will be using it instead of CWM
Heres the background form the Developer Raidzero
raidzero said:
---------------------------------
BACKGROUND
---------------------------------
Last year I made RZRecovery for the original Droid. It was a huge success, since then I have been asked to port to other devices. So here,
about 1 year later (after a lot of work... Remember, I *do not* know C), I have done just that. This will bring all the features of the old
RZR plus a few new ones including the epic rom.tgz install format from the days of yore to any device. I have built this recovery
specifically to handle all devices without the need for a recompile (except for Tegra2-based devices, they have to be recompiled because of
some libc bugs). I have made img files for a few devices to start with:
Click to expand...
Click to collapse
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"
}
---------------------------------
WALKTHROUGH
---------------------------------
Volume up/down - scroll (can hold down to repeat scroll)
HTC - touch screen - scroll
Home - select
Back/Power - back
Recovery Menus
Code:
Main screen
Reboot android
Reboot recovery
Reboot bootloader
Power off
Wipe menu
Wipe all - wipe everything on the device except recovery
Wipe system (the ROM)
Wipe data (your applications and settings)
Wipe .android-secure (other applications and settings on sdcard)
Wipe boot (the main android kernel)
Wipe cache
Wipe battery stats
Wipe dalvik cache (cache of optimized dalvik executables)
Mount menu
Mount/unmount system (the ROM)
Mount/unmount data (apps and settings)
Mount/unmount sdcard
Enable/Disable USB Mass storage
Nandroid menu
Nandroid Backup
Perform backup
choose boot,data,android-secure,system,cache to back up
select if you want to auto reboot upon successful backup
Nandroid restore
Choose backup
choose boot,data,android-secure,system,cache to restore
select if you want to auto reboot upon successful restore
Compress existing backup
Choose backup
perform compression
Delete backup
Choose backup
Perform deletion
Install from sdcard
choose item to install:
APK, ZIP, IMG, (must end in rec.img or boot.img) .TAR, .TGZ
Preinstall Menu
Toggle backup before install (make a quick backup of the device naming it preinstall-date-time)
Toggle wipe data
Toggle wipe cache
Add to install queue
Clear install queue
Abort install
Perform install(s)
if(APK)
Abort APK install
Install to system
Install to data
Extras menu
Custom Colors
Random - randomly generated color, will save to sdcard
Any other color - will save to sdcard
Rave mode - a totally random color each time the screen is redrawn (every key press)
Show battery status - will show charge status, level, temperature if available
Recovery overclocking
Kernel will report the available CPU slots, pick one and it will set the max to your selection. Saves to sdcard
Plugins (if plugins are installed)
Download Link
http://www.rzdroid.com/ftp/recovery/gingerbread/2.1.4/RZR-2.1.4-marvel-update.zip
Source
http://rootzwiki.com/topic/7309-recovery-rzrecovery-many-devices/
Looks pretty comprehensive. Does it support ROM manager, titanium backup and ROM toolbox for rebooting into and auto start backups/restores?
d33ps1x said:
Looks pretty comprehensive. Does it support ROM manager, titanium backup and ROM toolbox for rebooting into and auto start backups/restores?
Click to expand...
Click to collapse
I don't no haven't tested that yet
Sent from my HTC Wildfire S using Tapatalk
eoghan2t7 said:
I don't no haven't tested that yet
Sent from my HTC Wildfire S using Tapatalk
Click to expand...
Click to collapse
I don't see support for backing up sd ext in there...
Do I ask enough questions?
Sent from my HTC Wildfire S A510e using Tapatalk
d33ps1x said:
I don't see support for backing up sd ext in there...
Do I ask enough questions?
Sent from my HTC Wildfire S A510e using Tapatalk
Click to expand...
Click to collapse
Yes it can backup and restore sdext.img
Sent from my HTC Wildfire S using Tapatalk
woot woot
That's what I'm talkin' about. You have offered the wildfire s users choice. God bless you sir.
Kick in the pants [to me] to get working on 4ext porting
Regards,
Rob
Anybody tried this yet?
Sent from somewhere too far away from my computer
me im using it now
eoghan2t7 said:
me im using it now
Click to expand...
Click to collapse
ROM manager working ?
Sent from somewhere too far away from my computer
havent tested it with rom manager yet mate
eoghan2t7 said:
havent tested it with rom manager yet mate
Click to expand...
Click to collapse
Download and test. Will update post.
It works and its cool. But its slow and doesn't have that many new things.
Sent from somewhere too far away from my computer
Direct link added
Sent from my HTC Wildfire S using Tapatalk
WFS CDMA
Works Great on CDMA thankss
Will not work with ROM manager. install some plugins if you want to see something new..
http://rzdroid.com/ftp/recovery/gingerbread/plugins/RZR-plugins-bundle-update.zip
tested working
raidzero said:
Will not work with ROM manager. install some plugins if you want to see something new..
http://rzdroid.com/ftp/recovery/gingerbread/plugins/RZR-plugins-bundle-update.zip
Click to expand...
Click to collapse
Installing it now. Always interested in something new.
I rarely ask questions anymore but how does this install. I get an install error in CWM Recovery doing it as a zip.
It's a bad image file when I extract and rename to PG76.IMG.
Sorry for the silly question.
DS
d33ps1x said:
Installing it now. Always interested in something new.
I rarely ask questions anymore but how does this install. I get an install error in CWM Recovery doing it as a zip.
It's a bad image file when I extract and rename to PG76.IMG.
Sorry for the silly question.
DS
Click to expand...
Click to collapse
In recovery. I know what you mean. I was thinking that I installed other recoverys through pg67img thing but this one is just a flashable zip.
Op... could you have instructions on first post please?
Sent from somewhere too far away from my computer
benjamingwynn said:
In recovery. I know what you mean. I was thinking that I installed other recoverys through pg67img thing but this one is just a flashable zip.
Op... could you have instructions on first post please?
Sent from somewhere too far away from my computer
Click to expand...
Click to collapse
I'll add a guide when the drink exits my liver lmao
Sent from my HTC Wildfire S using Tapatalk
eoghan2t7 said:
I'll add a guide when the drink exits my liver lmao
Sent from my HTC Wildfire S using Tapatalk
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=974590
More or less.
is it support for s on device
Sent from my HTC Wildfire S A510e using XDA App
[TUTORIAL][S-OFF!]290 MB Data Partition!!! & Installing CyanogenMod 7 Step By Step!
Now with a video tutorial for download!!!
A while ago I came across a great scrip from Firerat and I figured it was time to highlight it again as he's updated it constantly.
I thought I would take the time to put together a tutorial on how to do the following:
1/ Change the size of your /System, /Data, and /Cache partitions to give you a HUGE amount more /Data space for efficiently sized ROM's like CyanogenMod 7.x
2/ Show you how to install CyanogenMod 7.x with these custom partition sizes and verify that they are as expected.
What you will need:
A prerequisite is a custom recover, preferably Alquez's Unofficial CWM Recovery 5.0.2.6
1/ To download and place on your SD Card the latest build of Alquez's CM7.x. (Do not unzip!)
2/ Google apps (GAPPS) for CyanongenMod 7.x, which you will also place on your SD card (Do not unzip!)
3/Firerat's 1.5.8 MTD Boot Script which you will also place on you SD card (Do not unzip!)
4/ Firerat's 1.5.8 MTD Recovery Script which you will also place on you SD card (Do not unzip!)
5/ The custom mtdpart.txt file that defines your custom partition sizes. Place this on your SD card in the same folder as the boot and recovery scripts. For ease of explanation let's just put all the required files on the root of your SD card.
Now you have all the files that you are going to need it's time to begin:
1/ Alter the txt file to suit your need but do not hit enter. Make sure there is no carriage return taking you to a second linein the file.
{
"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"
}
2/Now save it as "mtdpartmap.txt" (For CM7x you can use 145 20 with no worries). Don't listen to people telling you that 125 5 is a good setting. They don't know what CM7.x you are using and I do. Trust me.
3/ As mentioned earlier download and opy the recovery file, the boot file, the mtdpartmap.txt, Alquez's latest CM7.x nightly, and the latest version of GAPPS to the root of your SD card
5/Remove the rear cover of your phone
6/ Remove your phone's battery and replace it while unplugged
7/ Ensure you have a good charge before you begin (Say 30% or more)
8/ Press and hold Volume Down+Power at the same time to reboot into CWM or Razor recovery. (We will be using CWM Unofficial 5.0.2.6 for this tutorial)
9/ Perform a Nandroid backup of your current ROM to make sure you have something to go back to should you wish!!!
10/ Choose wipe data/Factory reset from the menu and follow the prompts.
11/ Go to the Mounts and Storage Menu and follow the prompts to format your system partition.
12/ Go back to the main menu and choose Install zip from SD card and follow the prompts to install the Recovery zip that will set your mount points for your partitions and give you the space you are looking for. (WHEN DONE BE CAREFUL! THERE IS ANOTHER IMPORTANT STEP TO PERFORM HERE IN THE NEXT STEP!!!)
**Notice it now says to wipe system, cache, and data partitions then reboot to recovery. Very important! This is the #1 reason why this fails for people. Read it carefully.
Now here's how to do it!:
1/ Return to the Mounts and Storage Menu
2/ Format the Cache, Data, and System partitions by following the prompts. (DO NOT FORMAT ANYTHING ELSE AND BE CAREFUL TO CHOOSE SYSTEM NOT SD CARD!!!)
Now for part three...
Part 3:..
1/ Go to advanced menu and reboot to recovery
2/ If you are restoring a NANDROID backup do so now using backup/restore and restoring the NANDROID backup you wish to put on the new partitions but beware about trying to restore something onto the new cache and system partitions that is too big for them!!!
**Note! From here on in we are going to skip the screen shots of Install zip from SD, and confirming it. If you haven't gotten this down by now it's perhaps time to head to your local nerd and get him/her or he-she to do this for you.
3/ Installing CM7.x install zip from SD
4/ Install the Google apps GAPPS zip from the SD
5/ Install the boot portion of the script from the SD card. This portion allows your device to find the right start and end points for the newly resized partitions that you created.
**NOTE!!! You must rerun this portion of the script every time you do a wipe and install or wipe and NANDROID restore! If you do not your device will become stuck at the boot splash screen. So keep this script file on your SD card!
6/ Return to recovery main menu and reboot device and enjoy your roomy CM7.x install!
Now:
Let's confirm through Terminal Emulator that your partitions are actually changed!
-Click on the centre home button on the bottom of your screen to bring up the all apps list.
-Scroll across to the T's and load Terminal Emulator by clicking on it.
-Once inside Terminal Emulator type the following followed by Return/Enter on your virtual keyboard:
"busybox df -h"
-This will bring up the list of all the partitions on your system and as you can see your Data partition is now 290 MB, your Cache partition is now 20 MB and your System partition is now 145 MB with 8.8 MB remaining on your system partition. Just enough for integrating updates to your system apps into the System partition.
So that's it!
Now how about moving ahead to my LINK2SD prepping and configuring tutorial and my Speed up your GPS CWM flash update to top it all off!
Well done!
IF THIS TUTORIAL HELPED YOU PLEASE CLICK THANKS!!!
Excelent tutorial, thx.
really good tutorial but i didn't get it what advantages i got from this ?
speed or more space in internal memory
hanynemesis said:
really good tutorial but i didn't get it what advantages i got from this ?
speed or more space in internal memory
Click to expand...
Click to collapse
Well CM7 is a speedy ROM as it's well tweaked to begin with and obviously has a low overhead due to the size.
This gives you an additional 120 MB of internal memory! Combine that with LINK2SD and you've got a phone virtually unlimited for apps.
Glad the tutorial helped.
One more thing...
Even though the tutorial show 1.58 beta files the linked files are actually 1.58 final. A little added bonus.
Thanks for the PM question so I could clarify that and please click THANKS if if you appreciate this tutorial.
D
So, overall this increases the internal memory for apps am I right?
Great tutorial mate, will do this on next nightly update with a kernal.
Check this out...
Now with a video tutorial for download!!!
See the first post...
isn`t it easier to flash cm, then just boot into recovery and install data 2 sd, after partitioning your sd card ext4 1 gb + rest fat32 ?
What exactly do you have to do with 1.5.8 MTD Boot Script zip file?
I try to install another ROM (circle battery - change the battery icon) and when I was going to reboot, my phone get stucked at the CyanogenMod logo. It reproduced it again and again. Should I reinstall 1.5.8 MTD Boot Script zip file after doing this or what? Do you know the correct way to install it?
Besides, I pretty good tutorial. Too clearly explanated.
You have too flash the boot script after you flash a new ROM or a backup. That's explained.
Sent from my cm7.2 Wildfire S
b02 said:
isn`t it easier to flash cm, then just boot into recovery and install data 2 sd, after partitioning your sd card ext4 1 gb + rest fat32 ?
Click to expand...
Click to collapse
Do what you wish of course.
I prefer link2sd and a load of internal fast memory for booting and important apps. A distinguishing feature that data2sd doesn't have.
If your SD card fails you still have your most important stuff with you. Can't say that for DATA2SD or DATA2WHATEVER, etc...
Sent from my cm7.2 Wildfire S
not working for my htc wildfire s a510e after doing all steps and "busybox df -h" show me the data partition size 150 mb and 40 mb was used (
d33ps1x said:
You have too flash the boot script after you flash a new ROM or a backup. That's explained.
Sent from my cm7.2 Wildfire S
Click to expand...
Click to collapse
Ok. That's what I thought but I think I did it wrong or something. So the steps are this:
1. Install new ROM or backup.
2. Go to install zip from sd and select the boot.
3. Install it.
4. Reboot the phone.
ROMTesting said:
Ok. That's what I thought but I think I did it wrong or something. So the steps are this:
1. Install new ROM or backup.
2. Go to install zip from sd and select the boot.
3. Install it.
4. Reboot the phone.
Click to expand...
Click to collapse
Yes. Of course this is for a backup or different rom or something. You still have to do the recovery scrip to resize for your initial resizing.
d33ps1x said:
Do what you wish of course.
I prefer link2sd and a load of internal fast memory for booting and important apps. A distinguishing feature that data2sd doesn't have.
If your SD card fails you still have your most important stuff with you. Can't say that for DATA2SD or DATA2WHATEVER, etc...
Sent from my cm7.2 Wildfire S
Click to expand...
Click to collapse
i just asked, and i just hope that sd card wont crash (didnt happen since i first flashed cm)
though, a GREAT guide mate, very well explained ...
p.s. guys click thanks for this, cos' that takes some time to be made, even if oyu dont use it
You know, I've tried (probably) every single method posted on these boards about flashing CM7, and yet I can't get it to work properly. This is really the most step-by-step tutorial I've seen and I thought it would work, but no, still no data connection.
With other methods I've tried, they've either disabled both Wi-Fi and mobile data connection, just one of the two, or there's a missing phone/dialer app.
With this one, the Wi-Fi's working, but I still have no data connection. Any ideas as to why this could be?
johnnyspritz said:
You know, I've tried (probably) every single method posted on these boards about flashing CM7, and yet I can't get it to work properly. This is really the most step-by-step tutorial I've seen and I thought it would work, but no, still no data connection.
With other methods I've tried, they've either disabled both Wi-Fi and mobile data connection, just one of the two, or there's a missing phone/dialer app.
With this one, the Wi-Fi's working, but I still have no data connection. Any ideas as to why this could be?
Click to expand...
Click to collapse
Did you try the libril fix? What is your radio version?
http://forum.xda-developers.com/showthread.php?p=21147430#post21147430
If you have a different RUU that Euro 2.3.5 then grab your own libril.so from /system/lib on your RUU install and save it to your SD.
Re-install CM7 and replace and set permissions on libril.so
I've followed this tut d33p, but my phone still displays total 150mb internal storage, why?
Strange, I've used this mod also a month ago and it works great.
However I've used slightly different instructions.
Here we go:
put all the required data on the root of your sd card
reboot in recovery
take nandroid backup
go to mounts - format system
factory reset
advanced - wipe dalvic cache
install custom recovery script
reboot in recovery
restore nandroid backup
install custom boot script
reboot
This worked for me, don't know if it works for you guys.
Say it
I'm having problems w/ my GS3 after accidentally restarting w/ no OS.
See original post here: http://forum.xda-developers.com/showpost.php?p=41306538&postcount=5979
I got a response, here: http://forum.xda-developers.com/showpost.php?p=41306968&postcount=5980
I'm unsure of what exactly they meant in the response, but I found a walkthrough, here: http://www.androidjunkies.com/how-to-unroot-att-galaxy-s3-flash-stock-ucdlk3-firmware/
I feel like I've done this, but I'll try it out anywho. I'm wondering:
1. Could it an issue of kernels?
2. Would it help if I wiped everything on my sd card(s)? If so, how do I do that?
3. Could it be an issue of having/not having my sd cards mounted?
Thank you for your generous help.
hoss9009 said:
I'm having problems w/ my GS3 after accidentally restarting w/ no OS.
See original post here: http://forum.xda-developers.com/showpost.php?p=41306538&postcount=5979
I got a response, here: http://forum.xda-developers.com/showpost.php?p=41306968&postcount=5980
I'm unsure of what exactly they meant in the response, but I found a walkthrough, here: http://www.androidjunkies.com/how-to-unroot-att-galaxy-s3-flash-stock-ucdlk3-firmware/
I feel like I've done this, but I'll try it out anywho. I'm wondering:
1. Could it an issue of kernels?
2. Would it help if I wiped everything on my sd card(s)? If so, how do I do that?
3. Could it be an issue of having/not having my sd cards mounted?
Thank you for your generous help.
Click to expand...
Click to collapse
I installed triangleaway and it's saying that I'm not rooted, but somehow still have access to CMW.
Thoughts?
I'm going to try all the other steps.
hoss9009 said:
I installed triangleaway and it's saying that I'm not rooted, but somehow still have access to CMW.
Thoughts?
I'm going to try all the other steps.
Click to expand...
Click to collapse
CMW or any recovery for that matter has nothing to do with any rom or whatever you are running. Recoveries on this device are on their own partition.
If you are trying to go back to stock:
1.) Go here and download the correct firmware for your device. http://forum.xda-developers.com/showthread.php?t=1968625
2.) Flash that firmware with odin.
3.) After that's done, reboot into recovery and factory reset.
4.) After that's done you will be fully stock.
5.) You should really consider reading up on all of this stuff. If you don't, you take the risk of bricking your expensive device and rendering it useless.
task650 said:
If you are trying to go back to stock:
1.) Go here and download the correct firmware for your device.
2.) Flash that firmware with odin.
3.) After that's done, reboot into recovery and factory reset.
4.) After that's done you will be fully stock.
5.) You should really consider reading up on all of this stuff. If you don;t you take the risk of bricking your expensive device and rendering it useless.
Click to expand...
Click to collapse
Thank you so much. I know some, but not everything. I'm missing pieces to the puzzle.
I just tried to make a nandroid of my stock rom as is right now and I got the error:
Code:
No /sdcard/ .android_secure found. Skipping backup of applications on external storage. No sd-ext found. Skipping backup of sd-ext. Generating md5 sum... Backup complete!
Why would it say that about my sd card? I feel like directories on my sd card(s) aren't lining up w/ what android wants.
Thoughts?
hoss9009 said:
Thank you so much. I know some, but not everything. I'm missing pieces to the puzzle.
I just tried to make a nandroid of my stock rom as is right now and I got the error:
Code:
No /sdcard/ .android_secure found. Skipping backup of applications on external storage. No sd-ext found. Skipping backup of sd-ext. Generating md5 sum... Backup complete!
Why would it say that about my sd card? I feel like directories on my sd card(s) aren't lining up w/ what android wants.
Thoughts?
Click to expand...
Click to collapse
That's not an error. CMW or any recovery for that matter will not make nandroids of anything on your external sdcard partition. Its supposed to say that.
task650 said:
That's not an error. CMW or any recovery for that matter will not make nandroids of anything on your external sdcard partition. Its supposed to say that.
Click to expand...
Click to collapse
No no, I tried to make a nandroid backup OF my system and put it on ON my sd card (which I've done a billion times before).
task650 said:
That's not an error. CMW or any recovery for that matter will not make nandroids of anything on your external sdcard partition. Its supposed to say that.
Click to expand...
Click to collapse
Is there a way to wipe/format both sd cards? i have everything backup on my comp.
hoss9009 said:
Is there a way to wipe/format both sd cards? i have everything backup on my comp.
Click to expand...
Click to collapse
Use your comp to format your external sdcard. Wipe the internal in recovery.
task650 said:
Use your comp to format your external sdcard. Wipe the internal in recovery.
Click to expand...
Click to collapse
Thanks. Really hoping this works. I don't know why it says that I'm not rooted when I can access CMW.
hoss9009 said:
Thanks. Really hoping this works. I don't know why it says that I'm not rooted when I can access CMW.
Click to expand...
Click to collapse
You're not reading what I posted is why you don't understand. Its very simple. Root has nothing to do with recovery. CMW is a recovery. Not a root method. Just because you have a custom recovery doesn't mean you have root. You have to root your device if you want it rooted.
task650 said:
You're not reading what I posted is why you don't understand. Its very simple. Root has nothing to do with recovery. CMW is a recovery. Not a root method. Just because you have a custom recovery doesn't mean you have root. You have to root your device if you want it rooted.
Click to expand...
Click to collapse
Ah, ok. I've always that they were synonymous.
But here's where I'm confused. I've used oden and have unroot/rooted about 5 times in the last few days. Also, while using Oden, it gives me the i9300 label at the top. Is that normal/correct?
hoss9009 said:
Ah, ok. I've always that they were synonymous.
But here's where I'm confused. I've used oden and have unroot/rooted about 5 times in the last few days. Also, while using Oden, it gives me the i9300 label at the top. Is that normal/correct?
Click to expand...
Click to collapse
You don't want to use anything i9300 related. Please only use what I've linked you in an earlier post. All of this is very simple and I've given you all of the steps to do this correctly. There's no need for you to be making this complicated. Everything you need is all right in front of you here.
task650 said:
You don't want to use anything i9300 related. Please only use what I've linked you in an earlier post. All of this is very simple and I've given you all of the steps to do this correctly. There's no need for you to be making this complicated. Everything you need is all right in front of you here.
Click to expand...
Click to collapse
Thank you so much. But I don't get why it says my phone is a i9300. It's an ATT phone. When I plug into my comp, oden tells me it's a i9300 phone. I'm afraid I really messed it up.
I just wiped my cache and it says
Code:
Formatting /cache
Cache wipe complete.
E:unknown volume for path [sd-ext]
Dalvik Cache wiped
Should I be concerned if it says "E:unknown volume for path [sd-ext]"??
hoss9009 said:
Thank you so much. But I don't get why it says my phone is a i9300. It's an ATT phone. When I plug into my comp, oden tells me it's a i9300 phone. I'm afraid I really messed it up.
I just wiped my cache and it says
Code:
Formatting /cache
Cache wipe complete.
E:unknown volume for path [sd-ext]
Dalvik Cache wiped
Should I be concerned if it says "E:unknown volume for path [sd-ext]"??
Click to expand...
Click to collapse
Also, in the "Mounts and Storage Menu" of CMW, I get this:
Code:
- mount /system
- unmount /data
- unmount /cache
- mount /emmc
- mount /sdcard
(all format options below these)
Should I be concerned w/ the "unmounted" items?
hoss9009 said:
Also, in the "Mounts and Storage Menu" of CMW, I get this:
Code:
- mount /system
- unmount /data
- unmount /cache
- mount /emmc
- mount /sdcard
(all format options below these)
Should I be concerned w/ the "unmounted" items?
Click to expand...
Click to collapse
This is what I was talking about...
{
"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"
}
hoss9009 said:
This is what I was talking about...
View attachment 1957243
Click to expand...
Click to collapse
OK.... so I'm assuming the oden I was using was not the best to use. I found this article: http://gs3.wonderhowto.com/how-to/root-your-samsung-galaxy-s3-and-flash-stock-roms-using-odin-for-windows-0142713/, and have it working now.
This oden looked different:
I don't know why, but I got it to work this time. I'll attempt to install AOKP and see what happens....
hoss9009 said:
OK.... so I'm assuming the oden I was using was not the best to use. I found this article: http://gs3.wonderhowto.com/how-to/root-your-samsung-galaxy-s3-and-flash-stock-roms-using-odin-for-windows-0142713/, and have it working now.
This oden looked different: View attachment 1957279
I don't know why, but I got it to work this time. I'll attempt to install AOKP and see what happens....
Click to expand...
Click to collapse
Ok, @Task650. Everything's working :victory:
hoss9009 said:
Ok, @Task650. Everything's working :victory:
View attachment 1957376
Click to expand...
Click to collapse
My recommendation: do not try to root until you know all of the common problems that are encountered for the device model your using. Your problems here should have been able to been resolved within 15 to 20 minutes (not including setting your phone back up). Had you done your due diligence beforehand and learned more, this would have been easy and never an issue.
I would highly suggest you stick with the stock rom until you have thoroughly educated yourself. While I am not a developer, I respect those who are. As such I take upon myself to learn as much as I can so I do not have to bug them about any problems I run into.
I'm rooted on stock Nougat ROM (I think... I rooted it a couple years ago), bootloader unlocked.
A few days ago my phone just stopped booting up correctly. It boots to the blue Moto screen with the boot animation but stays there forever.
I can get into TWRP and view all of the files in system, Internal SD card, and External SD card. I've backed up a bit of it just in case but I'm hoping someone here can tell me what to try to get it to boot correctly.
Is there a quick or obvious way to fix this that anyone is aware of?
I have an old TWRP backup and when I go into "Restore" I have the option to restore System, Data (excl. storage), Boot, Recovery, EFS, and logo... so is worth it to try restoring one of these (such as boot or system)?
I'm looking to try the safest things first... I really don't want to have to wipe my device or worse, brick it.
Thanks
Well, if you don't have any important data in the phone (you can copy files via USB), you can just do factory reset and see
Klen2 said:
Well, if you don't have any important data in the phone (you can copy files via USB), you can just do factory reset and see
Click to expand...
Click to collapse
Well, I have some important data but I can backup my /data/ folder. The problem (other than the fact that it will take a lot of time) is that I'm not sure how to restore the apps and data once I factory reset it.
It would be different if they were Titanium Backup backups but I don't know of a way to restore an app with just having the apps data folders.
What will happen if I go into TWRP and Install the stock rom zip file? Will I lose data or root or mess with anything important?
More generally:
a) your problem may be in system - then reflashing system would help. It can be done without loosing data
b) your problem may be in data (which is more likely) - you have to wipe data
a) Reflashing system can be done by flashing correct images via fastboot (using script that doesn't wipe data) or in recovery if you have flashable zip of your rom (I'm not sure whether there are any). However, even after flashing system, it still may not work because of some conflicts with data so wiping data may be unavoidable
b)how to minimalize losses: what kind of important data do you have? If it is files, they can be copied easily. If it is app data, it's harder. However, if you have Google Backup turned on, most apps use it to backup their data. What particular app's data do you need to save, if you don't mind telling?
I know there used to be app that was able to extract individual app's data from TWRP backup and restore it. Maybe it was Titanium Backup Pro. But as nowadays non-cloud backups aren't a thing anymore, these apps quite vanished or their development stopped and they also may not work with new android versions.
You can download stock firmware here: https://mirrors.lolinet.com/firmware/moto/albus/official/
Nougat is available for RETAIL, RETLA, RETRU, RETUS and VZW. Where did you buy your phone? It is best to flash the ROM for the same region to avoid problems if you want to keep data. But you can flash any.
Klen2 said:
More generally:
a) your problem may be in system - then reflashing system would help. It can be done without loosing data
b) your problem may be in data (which is more likely) - you have to wipe data
a) Reflashing system can be done by flashing correct images via fastboot (using script that doesn't wipe data) or in recovery if you have flashable zip of your rom (I'm not sure whether there are any). However, even after flashing system, it still may not work because of some conflicts with data so wiping data may be unavoidable
b)how to minimalize losses: what kind of important data do you have? If it is files, they can be copied easily. If it is app data, it's harder. However, if you have Google Backup turned on, most apps use it to backup their data. What particular app's data do you need to save, if you don't mind telling?
I know there used to be app that was able to extract individual app's data from TWRP backup and restore it. Maybe it was Titanium Backup Pro. But as nowadays non-cloud backups aren't a thing anymore, these apps quite vanished or their development stopped and they also may not work with new android versions.
You can download stock firmware here: https://mirrors.lolinet.com/firmware/moto/albus/official/
Nougat is available for RETAIL, RETLA, RETRU, RETUS and VZW. Where did you buy your phone? It is best to flash the ROM for the same region to avoid problems if you want to keep data. But you can flash any.
Click to expand...
Click to collapse
Honestly, what I needed to recover were unread messages/whatsapp messages I never read and mostly just to avoid the headache or starting over but I'm over that. And what you said about using Titanium Backup to restore individual apps from a nandroid backup... that's exactly what I read about yesterday and was planning on doing.
Just now I tried restoring an old system backup and and a recent data/system backup but both times it got stuck at boot... so I think I'm either going to just flash my stock rom or do a restore of my system/data from last year...
My phone was running "Albus 7.1.1/NPS26.118-24/25" and I found a zip named "ALBUS_C_NPS26.118-24_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" (which has SW listed as "SW Version: albus_c-user 7.1.1 NPS26.118-24 25 release-keysM8953P_23.33.07.34R") so I think I found the right one.
Would you recommend restoring system and data from a working (but old) backup in TWRP or just flashing my rom again?
Also, I'm not sure if I need to reflash magisk or flash the no-verity-opt-encrypt zip (or wipe something).
Either way, I'm going to just try one of those once I hear you recommendation.
Thanks
SMS may be backed up by Google, WhatsApp not if you didn't have automatic backup turned on (or done backup manually).
First of all, I would flash just system and other stuff except data. I don't recommend flashing official zips in recovery. If the phone is rooted, they will fail anyway and they may delete data. It is better to flash via fastboot. Do you remember your update channel Do you have US retail device? Then you may try the zip you found. But not in recovery. It is not a recovery flashable zip. Extract it and I will send you a .bat file to flash via fastboot.
Klen2 said:
SMS may be backed up by Google, WhatsApp not if you didn't have automatic backup turned on (or done backup manually).
First of all, I would flash just system and other stuff except data. I don't recommend flashing official zips in recovery. If the phone is rooted, they will fail anyway and they may delete data. It is better to flash via fastboot. Do you remember your update channel Do you have US retail device? Then you may try the zip you found. But not in recovery. It is not a recovery flashable zip. Extract it and I will send you a .bat file to flash via fastboot.
Click to expand...
Click to collapse
It's an unlocked, US, Moto Z2 Play (XT1710-01). I ordered it from motorola's website. I never updated it, I just followed these instructions (https://gist.github.com/eexit/e6d5fc0984e1c7f25376d3dafa819792) to unlock bootloader, boot TWRP, back it up, and flash magisk.
extract your zip, place there fastboot.exe from attachment if you don't have one and run the bat. It will install the rom without wiping data. It is made for newest Nougat 'XT1710-01_ALBUS_C_7.1.1_NPSS26.118-24-23_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip' rom from here: https://mirrors.lolinet.com/firmware/moto/albus/official/RETUS/
Klen2 said:
extract your zip, place there fastboot.exe from attachment if you don't have one and run the bat. It will install the rom without wiping data. It is made for newest Nougat 'XT1710-01_ALBUS_C_7.1.1_NPSS26.118-24-23_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip' rom from here: https://mirrors.lolinet.com/firmware/moto/albus/official/RETUS/
Click to expand...
Click to collapse
So place your bat file in the extracted folder and run the bat file? Does my phone need to be in fast boot and do any of these files need to be on my phone or I can just do it from my PC?
All files in the same folder, phone in fastboot. Then run the bat
Klen2 said:
All files in the same folder, phone in fastboot. Then run the bat
Click to expand...
Click to collapse
I gave it a go but it's still hanging on boot.
Here's what the command window showed...
{
"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"
}
Then you'll probably have to wipe data. Backup them (to SD) and then try wipe
If you have unlocked bootloader and TWRP backup it is almost impossible to brick your Z2 Play, just flash Stock Nougat, Stock Oreo or Stock Pie and your phone should boot again.
By the way it looks, you will lose all your personal information.
If the classic wipes haven't worked you gotta try flash Stock ROM through fastboot.