[Working] - A2SD (Apps2SD) v2.7 Update 3r1 on Aria - See Post #9 - HTC Aria Themes and Apps

Hi Everyone,
Has anyone gotten A2SD from this thread:
http://forum.xda-developers.com/showthread.php?t=670087
To work on an Aria.
Please let me know.

I would love to know too. I'm tempted to try it, worst case scenario, I have to restore a backup.

It won't work with the stock kernel. Unless you can build a kernel to support it which I do not know how to it will not work for you.

this would be great, thinking of toying around with it myself.

I just go gave it a quick run through to no avail using rom manager to format the sd card into the proper partitions and then flashing the zip file in clock work as directed. I will try it again tomorrow when I'm not so damn tired. Apparently it works on the stock sprint hero 2.1 rom so maybe I'll research more into how that was accomplished as there is no reason this method needs a specialized kernel.
Sent from my HTC Liberty using XDA App

I've been playing with it a little this morning. It appears it is having trouble initializing a mount point in /system/SD. I will try a symlink from /sdcard to a created sir named /syste/SD until I figure out why the userland differs so much from the other ''stock'' 2.1 roms this appears to run on.
Sent from my HTC Liberty using XDA App

It won't work, the stock htc kernel does not support it.

Quit being a naysayer and read the list of stock based roms that support this particular method. There are several app2sd methods and there is no reason this one shouldn't support the stock kernel unlike the cyanogen style methods. I may not be able to do it yet but I defer the possibility of figuring it out to users who may be more skilled than myself rather than regurgitating the same thing over and over without research.
Sent from my HTC Liberty using XDA App

I have a2sd working on attn's liberated_aria b005
step 1: download Rom Manager from the Market
step 2: select partition sd card; select whichever size ext partition you desire (you can also create larger ext partitions doing this manually on a linux box but I won't cover it.
step 3: reboot phone into clockwork recovery; select partitions menu and mount /system.
step 4 (borrowed from Semigon at SmartQ MID forums):
Create a file called install-recovery.sh at <your android SDK installation>/tools/ on your PC with this code (MAKE SURE YOU CAN SAVE IT AS UNIX, ANSI TEXT , I use TextPad to do this [or TextWrangler for OS X] ) :
*
*
Code:
#!/system/bin/sh
mount -t ext2 /dev/block/mmcblk0p2 /system/sd
Step 5:
Plugin your cable and connect your aria to your computer so ready to use ADB
at prompt type:
"adb push install-recovery.sh /system/etc/install-recovery.sh" <-- push file to your aria
"adb shell" <-- shell to your phone.
*
*
Code:
* * #cd /system/etc/
* * #chmod 555 install-recovery.sh* * * * * *
* * #mkdir /system/sd
* * #mount -t ext2 /dev/block/mmcblk0p2 /system/sd* * * * *
* * #mount* * * * * * * *
( if everything is ok, you should see something like this:
/dev/block/mmcblk0p2 /system/sd ext2 rw,errors=continue 0 0 )
now type #exit
Step 6: Test to make sure that it will be automounted after reboot.
on your PC, from command prompt you can type: "adb reboot"
Step 7: After rebooted, you can either use adb or use "Terminal Emulator" to see if your SD EXT2 partition is mounted.
Connect as in step 1)
On your PC, from command prompt: "adb shell"
# mount
"/dev/block/mmcblk0p2 /system/sd ext2 rw,errors=continue 0 0" means you EXT2 partition is mounted after reboot.
Step 8: download Darktremor Apps2SD 2.7 Update 3r1 and place it at the root of your sd card.
Step 9: boot into recovery and select flash zip from sdcard
Step 10: In flash zip from sdcard, select the a2sd package file you downloaded earlier. Press home to flash; now reboot your phone
Step 11: now reconnect to your phone through adb.
#su
#a2sd install
Don't panic-- your phone will reboot as the script finishes
Step 12: adb back to your phone and type ls -l /data
You should see
lrwxrwxrwx root root 2010-07-27 14:56 app-private -> /system/sd/app-private
lrwxrwxrwx root root 2010-07-27 14:56 app -> /system/sd/app
Now check your phone storage. You should see that you have significantly more available then you did before. If you see it slowly decrease this is because the dalvik cache is still on the internal memory. This too, however, can be moved to the sd.
The following is from tkirton's main set of instructions found at hxxp://forum.xda-developers.com/showpost.php?p=7021325&postcount=2
If you want to move the dalvik-cache to the sd card, type:
a2sd cachesd (move dalvik to sd card)
a2sd cachepart (move dalvik to cache partition)
Now you should have even more internal space left. Enjoy.
Note: moving dalvik to sd card may produce instability in certain apps or force quits. If it isn't working for you just pull up "adb nocache" to move it back to internal storage while still installing apps to the ext partition on your sd card.
Credits to semigod, tkirton and thanks to attn1 (for making good stuff for us)
mosamjc

mosamjc said:
step 1: download Rom Manager from the Market
step 2: select partition sd card; select whichever size ext partition you desire (you can also create larger ext partitions doing this manually on a linux box but I won't cover it.
step 3: reboot phone into clockwork recovery; select partitions menu and mount /system.
step 4 (borrowed from Semigon at SmartQ MID forums):
Create a file called install-recovery.sh at <your android SDK installation>/tools/ on your PC with this code (MAKE SURE YOU CAN SAVE IT AS UNIX, ANSI TEXT , I use TextPad to do this ) :
*
*
Code:
#!/system/bin/sh
mount -t ext2 /dev/block/mmcblk0p2 /system/sd
Step 5:
Plugin your cable and connect your aria to your computer so ready to use ADB
at prompt type:
"adb push install-recovery.sh /system/etc/install-recovery.sh" <-- push file to your SmartQ
"adb shell" <-- shell to your SmartQ. Now you are at your SmartQ shell
*
*
Code:
* * #cd /system/etc/
* * #chmod 555 install-recovery.sh* * * * * *
* * #mkdir /system/sd
* * #mount -t ext2 /dev/block/mmcblk0p2 /system/sd* * * * *
* * #mount* * * * * * * *
( if everything is ok, you should see something like this:
/dev/block/mmcblk0p2 /system/sd ext2 rw,errors=continue 0 0 )
now type #exit
Step 6: Test to make sure that it will be automounted after reboot.
on your PC, from command prompt you can type: "adb reboot"
Step 7: After rebooted, you can either use adb or use "Terminal Emulator" to see if your SD EXT2 partition is mounted.
Connect as in step 1)
On your PC, from command prompt: "adb shell"
# mount
"/dev/block/mmcblk0p2 /system/sd ext2 rw,errors=continue 0 0" means you EXT2 partition is mounted after reboot.
Step 8: download Darktremor Apps2SD 2.7 Update 3r1 and place it at the root of your sd card.
Step 9: boot into recovery and select flash zip from sdcard
Step 10: In flash zip from sdcard, select the a2sd package file you downloaded earlier. Press home to flash; now reboot your phone
Step 11: now reconnect to your phone through adb.
#su
#a2sd install
Don't panic-- your phone will reboot as the script finishes
Step 12: dab back to your phone and type ls -l /data
You should see
lrwxrwxrwx root root 2010-07-27 14:56 app-private -> /system/sd/app-private
lrwxrwxrwx root root 2010-07-27 14:56 app -> /system/sd/app
Now check your phone storage. You should see that you have significantly more available then you did before. If you see it slowly decrease this is because the dalvik cache is still on the internal memory. This too, however, can be moved to the sd.
The following is from tkirton's main set of instructions found at hxxp://forum.xda-developers.com/showpost.php?p=7021325&postcount=2
If you want to move the dalvik-cache to the sd card, type:
a2sd cachesd (move dalvik to sd card)
a2sd cachepart (move dalvik to cache partition)
Now you should have even more internal space left. Enjoy.
Credits to semigod, tkirton and thanks to attn1 (for making good for us)
mosamjc
Click to expand...
Click to collapse
way to stick to your guns, ill try this later after i return from dinner

Please do. I'd like to know if it works for others as well. I can wait for a fully fleshed cm6 port with all working features (or a legitimate froyo for that matter), but additional space for applications is something that I desperately needed now (and now I do).

mosamjc said:
Please do. I'd like to know if it works for others as well. I can wait for a fully fleshed cm6 port with all working features (or a legitimate froyo for that matter), but additional space for applications is something that I desperately needed now (and now I do).
Click to expand...
Click to collapse
Just so happens this is the same day that CM6 from attn1 came out so i jumped the gun and ended up playing with his alpha Rom. So i have not validated this, BUT I can confirm apps2sd work on Attn1's new rom

Ha. I picked a hell of a day to try get creative. Hopefully it will be of use to someone until the cm6 build gets all its bugs ironed out.
Sent from my HTC Liberty using XDA App

dalvik cache issue
All of this worked fine, except for the dalvik cache part which had an error about not enough space while copying files.
How can moving dalvik cache be undone? It doesn't seem that "adb nocache" is a valid command.
Edit: Oh it should be "a2sd nocache" that seems to have fixed it

Well, I'm glad I have at least one happy customer. The cache transfered over fine for me but caused highly irregular behavior in 90% of the apps that cleared up the second I transfered it back. Could be a permissions issue or simply one that could be solved by reinstalling all your apps into the new sd environment. I'm not terribly concerned as installing the apps on the sd leaves plenty of space free for the caches to do their thing.

I am not very linux or android savy, but I will have to give this a try. It was the only thing missing from the Liberated rom. Now all is well. Thanks!
Hopefully, next we can get a Froyo w/ Sense UI! And our Arias can keep on rocking.

You may try the 2.7.5 RC1 and see if that helps the issue. There were fixes regarding copying files (permission issue...didn't tell it to retain permissions...didn't see that until 2.7.5 PF4A).
Glad to see you guys progressing on this. If someone knows the boot image base address for the Aria, I will modify a stock boot image for apps2sd.
Need any help, feel free to ask me. Any help I can give you to getting this program working on your rom I will be happy to do.
mosamjc said:
Well, I'm glad I have at least one happy customer. The cache transfered over fine for me but caused highly irregular behavior in 90% of the apps that cleared up the second I transfered it back. Could be a permissions issue or simply one that could be solved by reinstalling all your apps into the new sd environment. I'm not terribly concerned as installing the apps on the sd leaves plenty of space free for the caches to do their thing.
Click to expand...
Click to collapse

Here is a slightly modified version, mainly just changed formatting and fixed a few typos. Also my phone didn't automatically reboot after step 11. Thanks for the great guide!
Step 1: Download Rom Manager from the Market
Step 2: Select partition sd card; select whichever size ext partition you desire (you can also create larger ext partitions doing this manually on a linux box but I won't cover it.
Step 3: Reboot phone into clockwork recovery; select partitions menu and mount /system.
Step 4 (borrowed from Semigon at SmartQ MID forums):
Create a file called install-recovery.sh at <your android SDK installation>/tools/ on your PC with this code (MAKE SURE YOU CAN SAVE IT AS UNIX, ANSI TEXT , I use TextPad to do this ) :
Code:
Code:
#!/system/bin/sh
mount -t ext2 /dev/block/mmcblk0p2 /system/sd
Step 5:
Plug in your cable and connect your Aria to your computer so it is ready to use ADB. At prompt type:
Code:
adb push install-recovery.sh /system/etc/install-recovery.sh # push file to your Aria
adb shell # shell to your Aria. Now you are at your Aria shell
Code:
Code:
cd /system/etc/
chmod 555 install-recovery.sh
mkdir /system/sd
mount -t ext2 /dev/block/mmcblk0p2 /system/sd
mount
If everything is ok, you should see something like this:
Code:
/dev/block/mmcblk0p2 /system/sd ext2 rw,errors=continue 0 0
Now type:
Code:
exit
Step 6: Test to make sure that it will be automounted after reboot. On your PC, from command prompt you can type:
Code:
adb reboot
Step 7: After rebooting, you can either use adb or use "Terminal Emulator" to see if your SD EXT2 partition is mounted.
Connect as in step 1)
On your PC, from command prompt:
Code:
adb shell
mount
If your EXT2 partition has been mounted after reboot you will see:
Code:
/dev/block/mmcblk0p2 /system/sd ext2 rw,errors=continue 0 0
Step 8: Download Darktremor Apps2SD 2.7 Update 3r1 and place it in the root of your sd card.
Step 9: Boot into recovery and select "install zip from sdcard"
Step 10: Select the a2sd package file you downloaded earlier. Press power button to flash; now reboot your phone
Step 11: Now reconnect to your phone through adb:
Code:
adb shell
su
a2sd install
Don't panic-- your phone may reboot as the script finishes
Step 12: Connect with adb back to your phone:
Code:
adb shell
Then type:
Code:
ls -l /data
You should see
Code:
lrwxrwxrwx root root 2010-07-27 14:56 app-private -> /system/sd/app-private
lrwxrwxrwx root root 2010-07-27 14:56 app -> /system/sd/app
Now check your phone storage. You should see that you have significantly more available then you did before. If you see it slowly decrease this is because the dalvik cache is still on the internal memory. This too, however, can be moved to the sd.
The following is from tkirton's main set of instructions found at hxxp://forum.xda-developers.com/showpost.php?p=7021325&postcount=2
If you want to move the dalvik-cache to the sd card, type:
Code:
a2sd cachesd # move dalvik to sd card
a2sd cachepart # move dalvik to cache partition
Now you should have even more internal space left. Enjoy.
Note: moving dalvik to sd card may produce instability in certain app or force quits. If it isn't working for you then move it back to internal storage while still installing apps to the ext partition on your sd card with:
Code:
a2sd nocache
Credits to semigod, tkirton and thanks to attn1 (for making good for us)
mosamjc
Click to expand...
Click to collapse
mosamjc said:
Well, I'm glad I have at least one happy customer. The cache transfered over fine for me but caused highly irregular behavior in 90% of the apps that cleared up the second I transfered it back. Could be a permissions issue or simply one that could be solved by reinstalling all your apps into the new sd environment. I'm not terribly concerned as installing the apps on the sd leaves plenty of space free for the caches to do their thing.
Click to expand...
Click to collapse
Sounds very similar to what happened for me. The script completed even with a few copy errors, but then many applications had FC after reboot. There is more than enough space from moving the apps, so it was not a big problem.
tkirton said:
You may try the 2.7.5 RC1 and see if that helps the issue. There were fixes regarding copying files (permission issue...didn't tell it to retain permissions...didn't see that until 2.7.5 PF4A).
Glad to see you guys progressing on this. If someone knows the boot image base address for the Aria, I will modify a stock boot image for apps2sd.
Need any help, feel free to ask me. Any help I can give you to getting this program working on your rom I will be happy to do.
Click to expand...
Click to collapse
Will give the the newer version a try, by installing the new zip then running the cachesd and cachepart commands again. Thanks!

@MikeChelen Way to polish the tutorial. Looking good! I hammered that out in in only a few minutes originally after pulling together all the parts that made it tick for me. I just wanted to release it to the masses quickly to prove jznomoney wrong (am I a bad sport? Probably).
@Tkirton I will give the new version a go after lunch and see what happens. As far as the boot image address, I believe it is the same as the Legend, as almost all legend roms flash and boot successfully on the Aria. So I would give 0x12c00000 a try on Attn1's Liberated_Aria.

mosamjc said:
@MikeChelen Way to polish the tutorial. Looking good! I hammered that out in in only a few minutes originally after pulling together all the parts that made it tick for me. I just wanted to release it to the masses quickly to prove jznomoney wrong (am I a bad sport? Probably).
@Tkirton I will give the new version a go after lunch and see what happens. As far as the boot image address, I believe it is the same as the Legend, as almost all legend roms flash and boot successfully on the Aria. So I would give 0x12c00000 a try on Attn1's Liberated_Aria.
Click to expand...
Click to collapse
Haha, well I am glad you did! It meant the guide was available for me a little sooner. Score another point for stubborn resolve
It was more than clear enough for me to follow, hopefully the edits will help newer users though.
It might also be worth noting that ANSI is not an encoding itself, but a set of encodings? The normal Linux text editors seem to use US-ASCII or UTF-8 and these should probably both work.
Assuming other users don't have any problems, hope this gets added to the Aria sticky topic ^_^
Thanks again everyone!

Related

[SOLVED]I can't root RC29

Okay I've been trying to figure this out for 4 and a half hours now, I've downgraded from cupcake to RC29 and now I'm trying to root it, I've tried using this guide - http://forum.xda-developers.com/showthread.php?t=442480
But when I get to here -
"What To Do Now That You Have Root
Now that you have root, you will want to apply "Hard SPL" to your phone. HardSPL is what will allow you to apply flash images from other regions (like UK on US phones, and vice versa), create full backups of your phone, install the latest build from the Android source, and usually resurrect your phone if it is "bricked". You have already downloaded the file to your SD card, so now you can apply it.
1. Power off your phone.
2. Start up in recovery mode by holding home and pressing power.
3. You will now enter recovery mode. You should see an exclamation.
4. If you do not see a menu on screen, press Alt-L to show the menu.
5. Press Alt-S to apply the update from the SD card.
6. After the update is complete, hold Home and press Back to restart.
"
I go into recovery mode but all I see are lines and I try alt-f and alt-s but nothing happens.
Then I tried this guide - http://android-dls.com/wiki/index.php?title=Quick_Root
I get stuck here -
"# In the terminal you opened earlier (with root access) Enter the following commands in to flash the modified recovery
* mount -o remount,rw /dev/block/mtdblock3 /system
* rm -f /system/recovery.img
* flash_image recovery /sdcard/recovery_testkeys.img
"
When I type the second line of commands it says not found or something similar so I'm pretty much stuck and can't figure out how to root RC29, I would really appreciate your help.
Sounds like you didn't flash the recovery image... Are you sure you placed it on your phone and followed the instructions to flash it? the flash_image recovery recovery.img command. Anyways, I have to run to work, I"ll help you more when I get back if you haven't figured it out by then. good luck.
http://www.youtube.com/watch?v=GgJ2VtSqtJY&feature=channel
this viedo help me with my rooting since i learn better thru visual =)
this is part 1 of 3. this dudes videos helped me from stock to root. to another cupcake rom. to jachero rom. it toook me like abt a day to do everything. but then after that it shouldnt take long to start uploading various roms =)
Knightsofwar210 said:
Okay I've been trying to figure this out for 4 and a half hours now, I've downgraded from cupcake to RC29 and now I'm trying to root it, I've tried using this guide - http://forum.xda-developers.com/showthread.php?t=442480
But when I get to here -
"What To Do Now That You Have Root
Now that you have root, you will want to apply "Hard SPL" to your phone. HardSPL is what will allow you to apply flash images from other regions (like UK on US phones, and vice versa), create full backups of your phone, install the latest build from the Android source, and usually resurrect your phone if it is "bricked". You have already downloaded the file to your SD card, so now you can apply it.
1. Power off your phone.
2. Start up in recovery mode by holding home and pressing power.
3. You will now enter recovery mode. You should see an exclamation.
4. If you do not see a menu on screen, press Alt-L to show the menu.
5. Press Alt-S to apply the update from the SD card.
6. After the update is complete, hold Home and press Back to restart.
"
I go into recovery mode but all I see are lines and I try alt-f and alt-s but nothing happens.
Then I tried this guide - http://android-dls.com/wiki/index.php?title=Quick_Root
I get stuck here -
"# In the terminal you opened earlier (with root access) Enter the following commands in to flash the modified recovery
* mount -o remount,rw /dev/block/mtdblock3 /system
* rm -f /system/recovery.img
* flash_image recovery /sdcard/recovery_testkeys.img
"
When I type the second line of commands it says not found or something similar so I'm pretty much stuck and can't figure out how to root RC29, I would really appreciate your help.
Click to expand...
Click to collapse
Well I've had my Original (incorrect radio flash method), 1st Warranty replacement (keyboard too lose for my liking), 2nd Warranty replacement (sending back due to 'ASDF' keys stick), all flashed in past 2 weeks. I've almost memorized the stupid commands. The "flash_image recovery /sdcard/recovery_testkeys.img" had me puzzled on this one. But I've figured it out as the short method vs changing directory.
I think your issue is the last part of copying the recovery image to the phone. I've always used the following:
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# cd sdcard
# flash_image recovery recovery.img
# cat recovery.img > /system/recovery.img
seems Like you're instructions kind of combine the 3rd and 4th and skips the cat command, so i have no ideal how yours is getting the file to the actual phone. I may be wrong, but just looks half done. It may be as simple as copying the image to the /system path with the 'cat' command. Good luck with it tho.
Link: http://forum.xda-developers.com/showthread.php?t=442480
It just won't copy that img file, because I still get the old color boot menu. Nothing I do works.
Oh and I read somewhere I have to upgrade to the latest radio too, where do I get it and install it?
I finally got it to work I was pushing power and camera instead of power and home.
Where do I download the latest rooted build?
Knightsofwar210 said:
I finally got it to work I was pushing power and camera instead of power and home.
Where do I download the latest rooted build?
Click to expand...
Click to collapse
Well, that's your choice
JF 1.51 is just a plain cupcake rom with root
Haykuro's 6.0 sapphire port is very nice, like JF 1.5 but with HTC Dialer, Camera ect
Cyanogen's build is like JF but more heavily modded, has auto Apps2SD and a few other modifications.
Then there's the Hero builds if you want to be adventurous.
Just have a look in the development section and see which best suits your needs
Be aware the Haykuro's ports, Rogers and Hero all require haykuro's SPL (which needs the new radio or you will brick).
Okay well I downloaded Cyanogen's build, so what are the features and how to use them?
Just read through the thread. Most are automatic optimization mods (CPU scaling, audio mods) which just make for a nicer experience. There are also others like the HTC Camera app which is a vast improvement over the stock camera app. APPS2SD is also atomatic so all you need is a second partition on your card formatted to ext3, so you will have much more room for market apps.
* Based on AOSP 1.5r2, various collected patches, and some help from JF-1.51-ADP
* Enhanced ramdisk which uses optimal mount options and smart startup
* Includes E2FSProgs for checking and converting Ext filesystems
* Apps2SD is automatic! All you need is a second partition (ext).
* Includes script to upgrade to ext3 (from recovery mode, see FAQ)
* Supports ext2/ext3/ext4 for Apps2SD
* Includes HTC Framework and various applications
* Includes latest HTC_IME with long-press, calibration, and compact QWERTY.
* Launcher with 5 screens and auto-orientation and compact drawer layout
* Sexy pattern-lock from Sapphire and Stericson's lock screen
* Clean filesystem shutdown at poweroff/reboot, and fsck at boot (no FS corruption!)
* Includes T-Mobile IM application, Amazon MP3 (with Stericson's hack), and updated Google Maps
* Does not require "DangerSPL"
* Highly optimized kernel with many extra modules
* Includes Haykuro's APN list
* Tweaked frequency scaling options to be more responsive
* Maximum CPU scaling frequency set to 528MHz (3.3)
* Various enhancements to the Settings app including extra partition space
* Runs /system/sd/userinit.sh after A2SD setup and before starting the runtime for user scripts
* Microsoft Exchange support (Work Email from myTouch)
* Includes Compcache modules
* Linux cgroups for better app prioritization
Click to expand...
Click to collapse
Knightsofwar210 said:
Okay well I downloaded Cyanogen's build, so what are the features and how to use them?
Click to expand...
Click to collapse
Most of Cyan's features are under the hood. It boosts your CPU speed from 384mHz to 528mHz
You can also use a swap partition to speed it up even more (like a paging file/ram)
http://forum.xda-developers.com/showthread.php?t=531988
You will have to partition your SD card with a swap extension to do this. If you create another partition as an ext2, ext3, ext4 partition, Cyan has a script that will automatically put your apps on the SDcard
If you want the above, you will have to format like this
fat32, ext, linux-swap
inthat order
there are threads that will help you with partitioning
http://forum.xda-developers.com/showthread.php?t=534714
^ very useful for me. Requires cyans recovery
note the ext partition shouldnt be larger than 1.5gb and the swap partition shouldnt be larger than 32 mb (24mb recommended, but im to lazy to repartition mine)
note swap will reduce the life of the sd card (though you will have probably moved on by that time)
Also try out the HTC apps that it comes with, such as the camera and keyboard (keyboard can be used by long pressing on an input area, selecting input method and chosing "Touch Input")
You can also install HTC's Music app from here
http://forum.xda-developers.com/showthread.php?t=530572
Thats all i can think of other than themes. Tehre are others i intentionally left out that you can find yourself after you get more experience with everything
How do I partition my 8GB Micro SDHC with one that is 500mb and is ext3? Thanks.
EDIT - Saw your post above.
B-man007 said:
Most of Cyan's features are under the hood. It boosts your CPU speed from 384mHz to 528mHz
You can also use a swap partition to speed it up even more (like a paging file/ram)
http://forum.xda-developers.com/showthread.php?t=531988
You will have to partition your SD card with a swap extension to do this. If you create another partition as an ext2, ext3, ext4 partition, Cyan has a script that will automatically put your apps on the SDcard
If you want the above, you will have to format like this
fat32, ext, linux-swap
inthat order
there are threads that will help you with partitioning
http://forum.xda-developers.com/showthread.php?t=534714
^ very useful for me. Requires cyans recovery
note the ext partition shouldnt be larger than 1.5gb and the swap partition shouldnt be larger than 32 mb (24mb recommended, but im to lazy to repartition mine)
note swap will reduce the life of the sd card (though you will have probably moved on by that time)
Also try out the HTC apps that it comes with, such as the camera and keyboard (keyboard can be used by long pressing on an input area, selecting input method and chosing "Touch Input")
You can also install HTC's Music app from here
http://forum.xda-developers.com/showthread.php?t=530572
Thats all i can think of other than themes. Tehre are others i intentionally left out that you can find yourself after you get more experience with everything
Click to expand...
Click to collapse
Experience? Ha, this is just like custom firmware for the Playstation Portable. Custom firmware is the equivalent of a rooted build so I do have experience with this type of thing.
I'm stuck at the very last step - http://forum.xda-developers.com/showthread.php?t=534714
At the bottom it says - "part iv - copy rom to sdcard and install, enable swap:
after phone reboots...drop to console
in your win cmd prompt, enter:
adb shell mount /sdcard
adb push /update-path/update.zip /sdcard
on g1 console, enter:
recovery
wipe data (alt + w) <--this one is optional, but i like fresh installs
install rom (alt + s)
to enable swap, see this page!"
http://forum.xda-developers.com/showthread.php?t=531988
but when I try to do this - "2. in terminal or adb shell type:
don't type things in ().
Code:
$su (terminal only)
#mv /sdcard/userinit.sh /system/sd/
#chmod 775 /system/sd/userinit.sh
#sh /system/sd/userinit.sh
"
When I enter the first command "mv /sdcard/userinit.sh /system/sd/" it says file or directly not found.
I want to use this theme too but I'm not sure if it's compatable with my current build model and I'm not sure how to install it.
http://forum.xda-developers.com/showthread.php?t=475917
Knightsofwar210 said:
I'm stuck at the very last step - http://forum.xda-developers.com/showthread.php?t=534714
At the bottom it says - "part iv - copy rom to sdcard and install, enable swap:
after phone reboots...drop to console
in your win cmd prompt, enter:
adb shell mount /sdcard
adb push /update-path/update.zip /sdcard
on g1 console, enter:
recovery
wipe data (alt + w) <--this one is optional, but i like fresh installs
install rom (alt + s)
to enable swap, see this page!"
http://forum.xda-developers.com/showthread.php?t=531988
but when I try to do this - "2. in terminal or adb shell type:
don't type things in ().
Code:
$su (terminal only)
#mv /sdcard/userinit.sh /system/sd/
#chmod 775 /system/sd/userinit.sh
#sh /system/sd/userinit.sh
"
When I enter the first command "mv /sdcard/userinit.sh /system/sd/" it says file or directly not found.
Click to expand...
Click to collapse
use "cp" instead of "mv"
note that /system/sd only exists when you have apps2sd (atleast i think? someone correct me if im wrong)
also make sure you unzipped the userinit.sh
What your going through is experience.....this isn't just flashing psp roms xD
Custom firmware flashing is extremely simple on the g1..... this is like going into the ROM and changing things up. The mods im talking about involve lots of terminal and adb commands and you really shouldnt be using them unless you understand what its doing. If you have plenty of experience in linux,then you should be able to find lots of interesting things to do in the development section.
Knightsofwar210 said:
I want to use this theme too but I'm not sure if it's compatable with my current build model and I'm not sure how to install it.
http://forum.xda-developers.com/showthread.php?t=475917
Click to expand...
Click to collapse
Which build did you install? Its compatible with Cyan 3.6.7-2. The latest is Cyan 3.6.8 which released 4 hours ago
B-man007 said:
Which build did you install? Its compatible with Cyan 3.6.7-2. The latest is Cyan 3.6.8 which released 4 hours ago
Click to expand...
Click to collapse
It's compatible with the one I had, I don't have the latest version of Cyan.
I still need help enabling swap because I have done everything including partition but I still need help enabling it thanks.
Knightsofwar210 said:
It's compatible with the one I had, I don't have the latest version of Cyan.
I still need help enabling swap because I have done everything including partition but I still need help enabling it thanks.
Click to expand...
Click to collapse
use "cp" instead of "mv"
note that /system/sd only exists when you have apps2sd (atleast i think? someone correct me if im wrong)
also make sure you unzipped the userinit.sh
Click to expand...
Click to collapse
Did you already set up apps2sd? (basically partition like i told you and boot up cyans rom? to check if you have it enabled, go to
settings > sd and storage and check if you have secondary system storage
where are you getting stuck? i need a little more info on whats happening if the above didnt work
B-man007 said:
Did you already set up apps2sd? (basically partition like i told you and boot up cyans rom? to check if you have it enabled, go to
settings > sd and storage and check if you have secondary system storage
where are you getting stuck? i need a little more info on whats happening if the above didnt work
Click to expand...
Click to collapse
Yes I have cyan running with a new theme I installed, and yes I do have a secondary system storage, I'm stuck here - http://forum.xda-developers.com/showthread.php?t=531988
B-man007 said:
use "cp" instead of "mv"
note that /system/sd only exists when you have apps2sd (atleast i think? someone correct me if im wrong)
also make sure you unzipped the userinit.sh
Click to expand...
Click to collapse
I'll try this.

[HOW-TO] Have it all - Enomther's 1.5/6.1+Himem+Apps2SD

Tools you'll need:
1. Rooted Nexus
2. sdcard with 2 primary partitions 1. fat32 2. ext2/3 (I did 500mb)---class 6 card highly recommended
3.Enomther's 1.6.1 found here or Enomther's 1.5.1 found here (placed at root of sdcard)
4. Himem 1.6.1 kernel update found here or Himem 1.51 kernel update found here (placed at root of sdcard)
5. Titanium backup (available in the Market...donation key recommended)
6. Be open to frustration (and possibly, but not likely, damage your device) and not hold me responsible!
Steps to take:
If you are already running EM1.5/6.1 WITHOUT the memory kernel hack, you should be able to skip the titanium and wipe part, and skip straight to step #5, however...MAKE SURE YOU NANDROID!!! first.
1. Backup!! (nandroid <most important>/Titanium <recommend donation key, as I don't know free functionality)
2. Wipe
3. Flash 1.5.1 or 1.6.1 (or reflash if already running with himem)
4. Reboot WITHOUT enabling Google backup
5. Lucid in adb shell or terminal emulator (dalvik2sd <lucid -dc -a> optional)
Code:
su
lucid -a -sd
lucid -dc -sd
reboot
6. After full boot, reboot to recovery console
8. Once in recovery, flash Himem, reboot again
7. Install Titanium app from the market
8. Restore Titanium backup made in step 1 (in batch>all apps+data option)
9. Reboot one final time
11. Check everything worked by typing "free" in terminal and verify internal storage in settings (mine says 395332 total memory and 174 free internal memory)
12. <optional> Flash/apply theme or morph
EDIT: Beware!!! This is my 666th post!!!
The basic scenario is to set up apps2sd before flashing the himem kernel...I was getting bootloops performing it any other way than this. Your results may vary.
If you get bootloops and skipped anything, you may need to perform complete process.
Also, if in bootloop (stuck at the X splash screen),
Code:
adb shell reboot recovery
saves having to pull the battery.
Little more info needed for the android newbies out there, e.g. ext partition ect
but overall nice how to, and thanks for the info ill giv it whirl soon
After flashing the highmem it got's stuck at the X splash screen.
lolittle said:
Little more info needed for the android newbies out there, e.g. ext partition ect
but overall nice how to, and thanks for the info ill giv it whirl soon
Click to expand...
Click to collapse
Ahh, yes...sdcard partitions...Post #1 updated. Good looking out.
Breakthecycle2 said:
After flashing the highmem it got's stuck at the X splash screen.
Click to expand...
Click to collapse
Happened to me a couple times in my experiments. Make sure you are not skipping any steps and are not using a different/older copy of the himem...download a fresh copy from the link in the OP as the file has changed in the last few days.
While stuck at the X splash screen (A.K.A. bootloop) do this.
Code:
adb shell reboot recovery
start over from step #2 above.
2. wipe
3. flash 1.5.1...etc.
What is the command to reverse the davlik back to the phone memory?
What wouyld the command be in adb to check if apps2sd and davlik2sd or vice versa actually worked correctly before preceding?
Should be
Code:
su
lucid -dc -g1
reboot
Mikey1022 said:
What is the command to reverse the davlik back to the phone memory?
What wouyld the command be in adb to check if apps2sd and davlik2sd or vice versa actually worked correctly before preceding?
Click to expand...
Click to collapse
Code:
# lucid -a -sd
lucid -a -sd
Nothing was done. /system/sd/app is FOLDER.
Please rm -r /system/sd/app first.
Nothing was done. /system/sd/app-private is FOLDER.
Please rm -r /system/sd/app-private first.
Hmmm doesnt seem like it quit worked out lol
Did what it suggested for mt to remove the two folders and reapplied, worked.
lucid -s confirmed it
Mikey1022 said:
Code:
# lucid -a -sd
lucid -a -sd
Nothing was done. /system/sd/app is FOLDER.
Please rm -r /system/sd/app first.
Nothing was done. /system/sd/app-private is FOLDER.
Please rm -r /system/sd/app-private first.
Hmmm doesnt seem like it quit worked out lol
Did what it suggested for mt to remove the two folders and reapplied, worked.
lucid -s confirmed it
Click to expand...
Click to collapse
So, you got it working?
If not:
Code:
su
lucid -c
will clear your ext partition of app, app-private and dalvik-cache folders. Then you can run lucid -a -sd without issue. You may have to reboot in between, maybe not.
Oh, and thanks for fixing my quote...posted it while driving.
All good now

[Q] How to mount SD partitions from eMMC?

In case it's unclear, I have CM7 on eMMC and am setting up a Honeycomb/Phiremod dual-boot on SD, and would like all three ROMs to use the storage partition (7th in this case) on the card. The following post suggests to me that it's possible:
racks11479 said:
No need to root your stock nook. If you have a CM7 sdcard, root explorer or file expert(free from market), and a terminal emulator app. Which you should have with cm7. Try the following steps.
-using root explorer or file expert. Mount system as R/W
-open up a terminal emulator and run the following commands
Code:
$ su
# mkdir /mnt/nooksys
# mount /dev/block/mmcblk0p5 /mnt/nooksys
-now exit out of terminal emulator
-open up root explorer/file expert
-navigate to /mnt/nooksys
-you should now be able to see the stock nook system partition
-open up the /etc directory
-long press the vold.fstab file.
-it should give you an option to open with text editor
-change the line where it mounts the /sdcard from auto to 4
-exit out of root explorer
-reboot to stock
-it should now mount the 4th partition of your sdcard
Click to expand...
Click to collapse
The file path specified, however, did not work, and I don't know enough about linux in general or the specific file structures to figure out the necessary changes. The system I want to redirect is the CM7.1 beta running dalingren's 5/13 OC kernel.
I also don't know for sure whether the above works for redirecting a stock 1.2 install.

Mods and tweaks for LG Optimus L3 E405

ALL TWEAKS AND MOD FOR E405 WILL BE ADDED HERE TIME TO TIME
SO PLEASE SUBSCRIBE AND PRESS THANX BUTTON IF I'VE HELPED YOU IN ANY MANNER
all these mods are tested by me and/or others. still if any of them bricked ur phone, that will be only ur fault. test or use any of them at ur own risk.
Rooting-
{
"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"
}
Working-tested by me.
PLEASE CHARGE YOUR PHONE AT LEAST 60% BEFORE DOING THIS
No. of steps-10
1. Download and install LG United Drivers From Official Site
Link-http://www.lg.com/in/support-mobile/lg-E405
(see pic to know what to download)
2. Download SuperOneClickv1.7-ShortFuse.zip
Link-http://www.mediafire.com/?6f1sttgi1rc1q72
3. Disable your antivirus as it can block or can delete any file without your permission between the completion of whole process leaving you a soft bricked phone. SuperOneClick will run an exploit, your antivirus can show it as a virus or infection but after the process you can do a full system scan and there will be no virus in your system.
4.Extract SuperOneClick to desktop or any drive.
5. Connect your device to PC through data cable and connect in PC Software Mode.
6. Now go to Settings-> Applications-> Development-> Enable USB Debugging (in your phone)
7. Go to the folder where you have extracted SuperOneClick and run SuperOneClick.exe (see pic) (1)
8. Now select rageagainstthecage (2) as you can see in the pic and click on ROOT (3).
9. Wait for a while till you can see rooted and it will ask you to run a superuser command, say yes or no its up to you. yes is preferred.
10. Close SuperOneClick, Disconnect your Device. You can see a new app in there 'Super User', run it. If it starts.
Congrats, you are rooted but if it get force closed, then just connect device with usb debug enable and run superoneclick again with rageagainstthecage as mentioned above, this time you'l be rooted.
PLEASE SUBSCRIBE, RATE AND PRESS THANX BUTTON IF I'VE HELPED YOU IN ANY MANNER
My Work:
Mods For Lg L3 E405 Dual
Micromax Canvas Music Kernel Development Thread
How to mod lewa os PIM.apk (sms)
Multi Boot MTK Devices
Custom recoveries for Canvas Music A88 and Canvas 2 A110
Micromax Canvas Music Custom Rom's Patches
MT6577 Auto Focus Fix
CWM Recovery
Credits to dansh for build the first version of CWM Recovery for E405, all below versons are mine with changes
(See video tutorial if having any problem, links below)
1. Download terminal emulator from given links and install it to your E405.
(google play)-https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
(apk)-http://www.papktop.com/android-terminal-emulator-1-0-32.html
2. Download the Recovery file from the link.
CWM (normal version for user's not using link2sd and 3 partition system)
http://www.4shared.com/file/PSf8-KOF/cwmrecovery.html?
Stock Recovery
http://www.4shared.com/file/V0-hm93J/recoverystock.html?
3. Connect your E405 to pc in mass storage mode and move/copy 'cwmrecovery.img' to Internal SD (1GB)
4. Run the Terminal Emulator (see video tutorial for ease, links below)
Now, type the following commands-
after $ type
su (press enter) (terminal'll ask for superuser permission, grant it)
you'll see this
#
now type after #
dd(single space here)if=/sdcard/cwmrecovery.img(single space here)of=/dev/block/mmcblk0p17 (press enter)
above command should look like this in terminal-
$ su
# dd if=/sdcard/cwmrecovery.img of=/dev/block/mmcblk0p17
you'll see 'some records in some records out etc etc'
press the back soft-key to exit the terminal.
you can use 'recoverystock.img' by just replacing 'cwmrecovery.img' in all commands.
You can reboot to recovery by pressing and holding volume up (or down, hard reset gone, you can use recovery to reset your phone now) when the device is powering on.
See the images to know how to make a back up using CWM Recovery.
Videos-
Old Recovery Wroking-
http://www.youtube.com/watch?v=y7vckwBHWyY&feature=youtu.be
VIDEO TUTORIAL-
http://www.youtube.com/watch?v=8r8YpHQJTeo&feature=youtu.be
UPDATE:
New CWM Recovery for link2sd and 3 partition system users.
Flash using old CWM Recovery and reboot to recovery.
http://www.mediafire.com/?s1bgcmf80a87xbd
Features of link2sd version-
This will mount and backup in third partition of ur sd card instead of first
1st-fat (smallest size) <--------- Previous recovery backup and mount location
2nd-EXT4/3/2 1gb
3rd-Fat32 (rest of the space) <--------- this recovery mount and backup in this partition.
this version will make backup of
system, data, cache, recovery, boot and also .android-secure
Another version is under testing
Features-
will backup sd-ext (all apps linked by link2sd)
wipe option added for sd-ext
complete backup of the phone (nothing left)
test backup was of size 1.5 gb
will be out soon.
PLEASE SUBSCRIBE, RATE AND PRESS THANX BUTTON IF I'VE HELPED YOU IN ANY MANNER
Link2SD
1. Download and install Link2D from any given link.
2. Root your phone (if not rooted) (guide is previously posted on the page).
3. Download a Partition manager (Link given).
4. Insert your card in card reader and back up all your files to the computer because partitioning will wipe your data.
5. Open Mini Tool (partition manager's name) in your computer. Locate your SD card (be careful in choosing and make sure not to choose the drive of your computer).
6. Right click and choose Delete.
7. Again Right click and create a FAT (not fat32) PRIMARY partition and choose the smallest size possible.
8. Then create a EXT2 PRIMARY partition of 1 GB (not bigger) which will be used with Link2SD.
9. Create a FAT32 partition for the remaining space left on the SD card, by the same way you created EXT2.
10. Click the “Apply” button on the top left corner and wait for it to finish the process. Done.
11. Put back your SD card to your phone and switch it on.
12. Open Link2sd. You will be prompted to choose between ext2, ext3, ext4 and FAT32. Select ext2. (ext4 is also working in my case, try if working for u)
13. It will say mount script created. Reboot your phone now.
14. Open link2sd and if the message doesn’t show up, you succeded.
15. Go to Link2sd>Settings>check the autolink (to automatically move apps upon installation) (Optional).
16. If you already have some apps, select “move to phone” then after moving select “Create Link” (be sure to check the three files: app, dalvic-cache and library files).
Links:-
Partition manager- http://download.cnet.com/MiniTool-Partition-Wizard-Home-Edition/3000-2094_4-10962200.html
Link2SD (google play)- https://play.google.com/store/apps/details?id=com.buak.Link2SD
Link2SD (APK)- http://dl.apktops.com/app/201208/Link2SD_2.2.1.apk
Note: EXT2 is old, EXT4 is the fastest among 3 (EXT2,EXT3,EXT4) but not compatible in all ROMS and often requires kernel that supports EXT4.
So you can/should try all of them and keep the best one that works with your rom.
PLEASE SUBSCRIBE, RATE AND PRESS THANX BUTTON IF I'VE HELPED YOU IN ANY MANNER
Move All Existing Apps to the SD Card (internal sd) WITHOUT ROOTING
NOTE:don't move launchers, widgets and all the apps that you want to keep running when your phone is mounted or when you just switched it on, till external memory prepares. u can not use widgets if the are moved to sd
Tools required-
1. Drivers of your phone
2. Oracle’s Java JDK
3. Android SDk
# As in this tutorial, you have to connect your phone to pc in ‘pc software’ mode, so you have to install all the drivers in your pc, required by your phone. Look on official site of your phone to download the drivers or search for a cd/memory card in the phone box.
For LG Drivers, download and install in pc from here (around 10mb file, see image to know what to download)
Link-http://www.lg.com/in/support-mobile/lg-E405
(see bottom half of the image to know what to download)
1. Enable USB Debugging
Open the Settings screen, tap Applications, and select Development.
Tap the USB Debugging checkbox to enable it.
You may want to disable debug mode after completing this process.
#if USB Debug is grayed and u are not able to tick it, just in case, then plug your device to pc via data cable and connect in 'pc software' mode. now go to above said location in you phone and enable usb debug now.
# (If you don’t already have Oracle’s Java JDK installed on your computer, you’ll have to download and install it before installing the Android SDK ie mentioned in next step)
link for Oracle’s Java JDK-http://www.oracle.com/technetwork/java/javase/downloads/jdk7u9-downloads-1859576.html
(check " Accept License Agreemen" and click "jdk-7u9-windows-i586.exe" on this page)
2. Install the Android SDK
link-http://developer.android.com/sdk/index.html
(click "Download the SDK for Windows")
#note the path of installation, you'll need it later OR change the location of android sdk to a simpler path like root directory (C: or D: etc) for ease.
3. After you’ve installed both, JDK first and then Android SDK,
launch the SDK Manager from your Start menu.
Click on Start-> All Programs-> Android SDK Tools-> SDK Manager
Android SDK will open.
4. Now uncheck all check boxes (if checked by default) and select "Android SDK Platform-tools" and click the Install button to download and install it.
5. After the process completes, connect your Android device to your computer with USB cable (if not connected in step 1 or removed after it, you may have to enable usb debug again, plz refer to step 1 now).
Windows should locate the device and install the appropriate drivers automatically. If it doesn’t, you may have to download and install the appropriate drivers from your Android device’s manufacturer. Do not mount the device after connecting it – just plug it in. Use "PC Software" instead.
6. Open a Windows Explorer window and navigate to the android-sdk\platform-tools folder.
On x64 Windows, you’ll find this folder at C:\Program Files (x86)\Android\android-sdk\platform-tools by default.
Check C:\Program Files\Android\android-sdk\platform-tools if you’re using a 32-bit version of Windows.
#This will be the path where you have Android SDK in step 2.
i've told u to note it.
now plz look where u've installed it.
7. Launch a Command Prompt window (CMD) in this folder.
For this, press and hold shift key, right or left shift doesn't matters
right click anywhere (holding the shift) in empty space and select "Open command window here".
CMD will open.
8. Now type "adb devices" and press Enter.
You should see your connected Android device.
9. Now at last, type the following and press enter to set the default install location to your SD card:
ALL THE COMMANDS ARE CASE SENSITIVE
adb shell pm setInstallLocation 2
If you want to revert this change later and install apps to the internal storage by default, run this command:
adb shell pm setInstallLocation 0
code meanings-
0-auto
1-internal storage
2-external storage
(optional)
to know where the apps will be stored now run the following command
adb shell pm getInstallLocation
the result will be 2, ie external storage.
10. Now close CMD, disconnect your Device and start moving apps to sd without root
In you device, open the Settings screen, tap Applications, and select Manage Applications. Select the app you want to move and tap the Move button on its details screen.
PLEASE SUBSCRIBE, RATE AND PRESS THANX BUTTON IF I'VE HELPED YOU IN ANY MANNER
UNBRICK YOUR LG OPTIMUS L3 E405 and E400 WITH KDZ UPDATER
No. of steps-15
LET THE PHONE CHARGE OR AN HOUR OR TWO OR MORE
DISABLE YOUR ANTIVIRUS TEMPORARILY
1. Download LG Optimus L3 USB Driver
2. Download LG Optimus L3 stock firmware/rom from the page given at the end. (according to your network provider and country)
3. Download and extract KDZ updater on desktop or in any directory.
4. Install Microsoft XML parser (by running msxml.msi in the extracted folder)
5. Restart your computer.
6. Now, switch off your phone (ignore this, as assumed you can't even switch it on kidding)
7. Remove the battery and reinsert it. Press and hold Volume Up button and Volume Down button together. While you are pressing both buttons, press the Power/Lock button. DON'T LEAVE VOLUME UP DOWN BUTTONS TILL YOU GET TO EMERGENCY MODE (yellow screen with Emergency mode written on it). ALSO DON'T REMOVE THE BATTERY ONCE YOU REACHED EMERGENCY MODE.
8. Connect your phone to the computer via the USB Cable.
9. Run KDZ updater as Administrator.
10. Choose the following options in KDZ Updater (also see image):
Type: 3GQCT
Phone Mode: DIAG
KDZ file is the one you downloaded in step 2
CHOOSE CORRECT OPTIONS & RECHECK THEM TWICE OR THRICE!!
(these settings are for l3 only don't try on any other random phone)
11. Click 'Launch Software Update' and pray to god.
12. Go for a walk or talk to the mirror as it will take a while for the rom to be flashed.
13. At last you will se 'Finished'. Your phone will be switched off, switch it on normally. (or it can restart by itself, wait for about half minute before trying to switch it on)
14. It will take more time in switching on once, after that you can use it normally.
15. It is preferable to do a hard reset after flashing by this method.
LG Optimus L3 USB Driver
Link-http://www.lg.com/in/support-mobile/lg-E405
LG Optimus L3 stock firmware/rom
Link-http://lg/-phone-firmware.com/index.php?id_mod=11
KDZ updater
Link-http://www.unclenet.de/files/KDZ_FW_UPD_EN.7z
PLEASE SUBSCRIBE, RATE AND PRESS THANX BUTTON IF I'VE HELPED YOU IN ANY MANNER
How to use game gardian
Wanna cheat in any game???
download game gardian and follow the instructions (pics)
apk:
http://www.mediafire.com/?lumaz3036caain0
mirror:
http://www.mediafire.com/?sdh57bfv9krk559
PLEASE SUBSCRIBE, RATE AND PRESS THANX BUTTON IF I'VE HELPED YOU IN ANY MANNER
MOUNT LINK2SD PARTITION (i.e. EXT PARTITION) AS SYSTEM MEMORY (i.e. 157 mb default)
this is for the partition structure created to use with link2sd (ie fat, ext, fat32)
REMOVE ALL SCRIPTS U ARE USING TO MOUNT EXT PARTITION AND MAKE A TITANIUM BACKUP OF ALL APPS
FLASH THE ATTACHED BOOTINT.IMG USING CWM (DO A NANDROID BACKUP FIRST AND RESTORE DATA ONLY AFTER FLASHING)
OR
extract init.rc of boot.img and edit it. (for extracting u need Cygwin for windows and dsixda-Android-Kitchen or kernel kitchen, google about them)
do the following in init.rc
1. search 'on fs'
on fs
comment out 'mount yaffs2 [email protected] /data nosuid nodev' with #
like this
# mount mtd partitions
# Mount /system rw first to give the filesystem a chance to save a checkpoint
mount yaffs2 [email protected] /system
#mount yaffs2 [email protected] /system ro remount
#mount yaffs2 [email protected] /data nosuid nodev
mount yaffs2 [email protected] /persist nosuid nodev
mount yaffs2 [email protected] /cache nosuid nodev
mount yaffs2 [email protected] /persist nosuid nodev
now on 'on emmc-fs'
replace
wait /dev/block/mmcblk0p21
exec /system/bin/demigod_make_ext4fs -l 160M /dev/block/mmcblk0p21 /data
exec /system/bin/e2fsck -y /dev/block/mmcblk0p21
mount ext4 /dev/block/mmcblk0p21 /data nosuid nodev noatime barrier=1 data=ordered noauto_da_alloc errors=continue
with
wait /dev/block/mmcblk1p2
wait /dev/block/mmcblk1p2
wait /dev/block/mmcblk1p2
exec /system/bin/demigod_make_ext4fs -e /dev/block/mmcblk1p2 /data
exec /system/bin/e2fsck -y /dev/block/mmcblk1p2
mount ext4 /dev/block/mmcblk1p2 /data nosuid nodev noatime barrier=1 data=ordered noauto_da_alloc errors=continue
save it
pack the boot.img and flash it using cwm
if u have any cwm flashable package with u then extract 'META-INF>com>google>android>updater-script' and edit it with notepad++
delete everithing it it and paste this
run_program("/sbin/busybox", "mount", "/system");
package_extract_file("boot.img", "/tmp/boot.img");
assert(run_program("/system/bin/dd", "if=/tmp/boot.img", "of=/dev/block/mmcblk0p9")=="0");
run_program("/sbin/busybox", "umount", "/system");
save it and drag and drop it to it's location, i.e. 'META-INF>com>google>android> here'
now drag and drop boot.img in the zip (no folder, the zip itself)
make a nandroid backup and flash this.
now, advance restore ONLY data using cwm recovery and reboot
PLEASE SUBSCRIBE, RATE AND PRESS THANX BUTTON IF I'VE HELPED YOU IN ANY MANNER
MOUNT EXTERNALSD AS INTERNALSD
THIS MOD IS UNDER TESTING, PLEASE DON'T REPORT BUGS
edit init.rc and do search this
#exec /system/bin/resize2fs /dev/block/mmcblk0p20
now remove all # from
# [START] LGE_USE_INTERNAL_FAT
#wait /dev/block/mmcblk0p20
#exec /system/bin/resize2fs /dev/block/mmcblk0p20
#exec /system/bin/e2fsck -y /dev/block/mmcblk0p20
#mount vfat /dev/block/mmcblk0p20 /mnt/sdcard
# [END] LGE_USE_INTERNAL_FAT
to make it like to like like this
# [START] LGE_USE_INTERNAL_FAT
wait /dev/block/mmcblk1p3
exec /system/bin/resize2fs /dev/block/mmcblk1p3
exec /system/bin/e2fsck -y /dev/block/mmcblk1p3
mount vfat /dev/block/mmcblk1p3 /mnt/sdcard
# [END] LGE_USE_INTERNAL_FAT
add this above "mount vfat /dev/block/mmcblk1p3 /mnt/sdcard" if not mounting
unmount /dev/block/mmcblk0p20
OR FLASH THE ZIP
PLEASE SUBSCRIBE, RATE AND PRESS THANX BUTTON IF I'VE HELPED YOU IN ANY MANNER
ICS THEME FOR STOCK ROM (see images)
THIS IS FOR TESTING ONLY. IF WORKING, PLEASE COMMENT. THEN I'LL UPDATE THE THEME WITH MORE THEMED APP (only UI is themed in this version)
Flashing this is simple as 1, 2 and 3.
1. download and move/copy both zips to internal/external sd card
2. reboot to recovery and make a nandroid backup.
3. flash "1.zip" (from where u've placed it in step 1)
4. reboot.
if there is no bootloops and the phone starts up normally the proceed, otherwise restore cwm backup from recovery.
5. reboot to recovery and flash "2.zip"
6. reboot.
Enjoy
Zips:-
http://www.mediafire.com/?s5jv658c6ujoj4x
http://www.mediafire.com/?a5nr8m75k453ars
PLEASE SUBSCRIBE, RATE AND PRESS THANX BUTTON IF I'VE HELPED YOU IN ANY MANNER
thanks mate .
this is exact what I want!
needs to test some of them
there is one question
are you done all this things on your lg e 405 dual sim and is your phone work still normally? )
and is there any bug after rooting the phone I means some ppl says get buged in wifi or something like that...
thanks
x625 said:
thanks mate .
this is exact what I want!
needs to test some of them
there is one question
are you done all this things on your lg e 405 dual sim and is your phone work still normally? )
and is there any bug after rooting the phone I means some ppl says get buged in wifi or something like that...
thanks
Click to expand...
Click to collapse
i've tested all of them and rotting doesn't caused any bug in my case.
Im very glad to see you support here .
I newly bought a L3 E405 dual and had some trouble with it.
1)
firstly I must thank you for your rooting method (post #1) it worked for me and I my biggest problem solved.. millions of thanks to you my bro.
2)
But after a wile I encountered another major trouble . the phone extremely rapidly get fulled (internal system usable memory is only 157 mb!!! wtf!
although i have bought and installed an external sd card it is completely useless and even using app2sd apps on market many apps leave half of size on system memory some other apps dont support app2sd feat. and in result after installing 10-15 little routine apps (not games just needed essential apps) the phone get notification of low size and hangs and stop wifi and ... I installed external sd card on this phone but it is completely useless coz even app2sd moved apps take size on internal sd card not external!!! why !!!
now how could I overcome this problem with best and simple revertable steps? I know you posted some solution before but I want to know which method you personally recommend duo to you said some method still in test mod and im noob in android & adb & programming and dont want to breik my phone.
my phone has 2 year exchanging guaranty and dont want to void it i Know I already voided it because successfully rooted it with your method before but i think I can unroot it with that button on superoneclick software again.
3)
I only rooted my phone but still having fear to instal CWM on it . is that ok also to install CWM also? I just have low system memory problem and dont want any tweaks on my phone if they aren't necessary for it. my other season of fear is I didnt find my installed firmware county code . my phone is on V10G version sw but there are many E405 V10G firmware in here I dont know which is mine . and my living country in not listed there ( how could i find my firmware locale on my E405??
and more Q
what is the difference & benefit and advantages of link2sd over app2sd apps? I mean why we must use complicated steps of link2sd (partitioning & needs roots and ... when there is simple app2sd feat of our native android phone enhanced with app2sd apps on market? I dont got that ??
in your post #7 line #3 you said :
FLASH THE ATTACHED BOOTINT.IMG
and in end of post #8 you said:
OR FLASH THE ZIP
I cant see any attached ZiP files on that posts where could I find them?
in recovery mod tweak post you said you are preparing another new version of recovery soon . is there any new news ? i m so exited approximate date of release
thank you so so much for your helps
U already helped me so much for rooting my phone
million million tanks!!
and sory for such long story
x625 said:
Im very glad to see you support here .
I newly bought a L3 E405 dual and had some trouble with it.
1)
firstly I must thank you for your rooting method (post #1) it worked for me and I my biggest problem solved.. millions of thanks to you my bro.
2)
But after a wile I encountered another major trouble . the phone extremely rapidly get fulled (internal system usable memory is only 157 mb!!! wtf!
although i have bought and installed an external sd card it is completely useless and even using app2sd apps on market many apps leave half of size on system memory some other apps dont support app2sd feat. and in result after installing 10-15 little routine apps (not games just needed essential apps) the phone get notification of low size and hangs and stop wifi and ... I installed external sd card on this phone but it is completely useless coz even app2sd moved apps take size on internal sd card not external!!! why !!!
now how could I overcome this problem with best and simple revertable steps? I know you posted some solution before but I want to know which method you personally recommend duo to you said some method still in test mod and im noob in android & adb & programming and dont want to breik my phone.
my phone has 2 year exchanging guaranty and dont want to void it i Know I already voided it because successfully rooted it with your method before but i think I can unroot it with that button on superoneclick software again.
3)
I only rooted my phone but still having fear to instal CWM on it . is that ok also to install CWM also? I just have low system memory problem and dont want any tweaks on my phone if they aren't necessary for it. my other season of fear is I didnt find my installed firmware county code . my phone is on V10G version sw but there are many E405 V10G firmware in here I dont know which is mine . and my living country in not listed there ( how could i find my firmware locale on my E405??
and more Q
what is the difference & benefit and advantages of link2sd over app2sd apps? I mean why we must use complicated steps of link2sd (partitioning & needs roots and ... when there is simple app2sd feat of our native android phone enhanced with app2sd apps on market? I dont got that ??
in your post #7 line #3 you said :
FLASH THE ATTACHED BOOTINT.IMG
and in end of post #8 you said:
OR FLASH THE ZIP
I cant see any attached ZiP files on that posts where could I find them?
in recovery mod tweak post you said you are preparing another new version of recovery soon . is there any new news ? i m so exited approximate date of release
thank you so so much for your helps
U already helped me so much for rooting my phone
million million tanks!!
and sory for such long story
Click to expand...
Click to collapse
u can use lik2sd as you are not much familiar with android. i'll recommend to mount a EXT4 partition as your /data as this is better than link2sd (my personal opinion) but link2sd is fine and simple. and mounting EXT4 as /data will also give you large space for application's data also, which is not possible with link2sd. try using link2sd, you'll get to know what i am talking about.
which country do you belong?
CWM is must. as in any case, if you are unable to boot your phone than there is only kdz method to recovery, other then restoring CWM backup. and cwm backup restoration is much easier, better and safe than using kdz. also for flashing/installing .zip, you'll need CWM Recovery.
in any case you want to go back to stock recovery, u r free to do so.
app2sd will only move your apps to internal sd but link2sd will link them on your external sd. in app2sd apps will take a small amount of storage of your system memory while in link2sd only data will remain in system memory.
sorry about the zips. zips of recovery and boot are ready and uploaded on mediafire and on my blog, will add them here if few days.
thanks for quick reply.
you helped me a lot.
idont know how to appriciate you.
I done it (link2sd tweak) . I created ext2 partition on sd with pc partition manager (step1). and then on my phone I run link2sd app and run ext2 scrip (step2). and worked good.
you mentioned I can also use ext4. you meanthat I replace any ext2 with ext4 format in step1 or step 2 only ?? or in both steps must use ext4 choice??
and what is the pros and cons of using ext4 instead of normal ext2 . and is the stock kernel support this format officially?
Im on 2.3.6 with build number GRK39F sofware version V10g 15 nov -2012 . and my country is IRAN .and my phone firmware handle persian (farsi) languge characters (not only arabic) in menu and keyboard and dont want too loose that after update or installing new firmware for this reson I need to find my own phone firmware version but in lg-phone-firmware.com there is no any iran country ?
could you please tell me what is the exact step by step method of reinstalling stock firmware after I mesed up somethig ? you said it is better and safer flash firmware with CWM but i dont know how do that . is that possible to explain more this TWO different ways separately (kdz way and recovery way) . thank a lot .
yes stock kernel support EXT4, you can replace EXT4 in every step your've done with EXT2.
how to flash kdz has been already posted. and for cwm recovery. once you are in cwm recovery, you can see backup and restore. select it to backup to external or internal sd, similarly, use it to restore an old backup.
you can make a backup of current rom, can do anything you want and if anything wrong happens, just restore your backup.
Wow!
Finally i have done it?
Now i have cwm with supported backup to external sd. + link2sd with ext4 . script.
You are my hero sudeep!
Now im waiting for more and more SIMPLE FLASHABE tweaks from you not just working with terminal command.
Maye be you release your final version of your custom rom !!
Anyway i always checks this topic and thanks so so much to you
Sent from my LG-E405 using Tapatalk 2
Another good tweak for gaming
Try using Chainfire3D (Gingerbread)....It improves GPU a lot
Best Regards
Has anyone heard of any other tweaks improving L3 performance on CM9?
Will Chainfire 3D be working on ICS ?
nice
i've rooted my phone like in thread, and i can use apps that needs root perms (like link2sd)
but when i use Android Commander, i get Root Acess: NO
what to do?

[GUIDE] Upgrade 4.5.15 rooted & encrypted -> 5.0.2 WITHOUT DATA/SETTINGS LOSS

as usual, if anything goes wrong, no responsibility etc
The official update tutorial for rooted users doesn't keep app data, only internal storage! This tutorial keeps EVERYTHING
This method allows updating from 4.5.15 (unlocked, encrypted, rooted) to 5.0.2 without any data (sys settings + app data + user data) loss
A FAQ section is present at the end of this post and will be regularly updated.
List of files to download while doing the following steps:
OOS 5.0.2 ROM
Codeworkx TWRP recovery
Latest Magisk
Terms and software used in this guide:
Fastboot / Bootloader = bootloader of the phone, it's a very low level mode of the phone that allows booting into recovery. Can be accessed by using the advanced reboot menu (enable in dev options) or by "adb reboot fastboot".
Recovery = a small operating system on the phone that allows you to do various operations even when the main OS (Android) is broken. This includes flashing ROMs, modifying stuff on the storage, etc. It's the Android swiss army knife. If you can get a phone to boot TWRP, then you can do almost anything.
Magisk = rooting software that uses a systemless method to keep SafetyNet working. Systemless = instead of modifying the system, every change is put in a separate image that is mounted "over" the system. When the system tries to access a file modified by Magisk, instead of reading it from the partition, it reads it from Magisk. It's recommended to use Magisk instead of SuperSU as of 2018.
ADB = tool that allows controlling the phone from your PC through USB. You can use it when you're in Android if USB debugging is enabled in the settings, or when you're in TWRP. Here, we mostly use it for transferring files directly (without MTP) and running commands (using "adb shell")
Note: For this guide you will be required to download and install Magisk. If you don't want your phone to be rooted, then at the end of this guide reboot into TWRP, wipe both caches and re-flash the OS. This will uninstall Magisk and any other root patch. Beware: it will reflash stock recovery, so if you ever want to re-root, you'll need to reboot to fastboot and flash TWRP manually.
Convention for commands that you will have to run:
a command line starting with "C:" means that it should be run on your PC
a command line starting with "~ #" means that it should be run on your phone (through adb shell) while in TWRP
a command line starting with "OnePlus5:/ $" means that it should be run on your phone (through adb shell) while in OxygenOS
Although the commands start with "C:", this is just for readability purposes. You should run everything from inside an empty directory with enough disk space and writing access.
Your phone will have to be plugged in to your PC from the beginning to the end. Also, make sure it has at least 80% battery before beginning, just in case.
I know, the tutorial is huge. This is simply due to the fact that if I just wrote "make a nandroid backup of this and that, flash, and restore the backup while doing this", then some people may encounter problems because not everyone knows how to do a nandroid backup, restore it, etc. Also, there are a lot of things that need to be done precisely that way and not another way, which explains why the tutorial is huge. Also, you may notice that there is a lot of commands to run throughout the tutorial, this is because that way, I'm sure that at the end, you will have done everything like I did it on my phone, so that if you have a problem it's much easier to figure out where it comes from.
Summary of what you need to do (this is only a SUMMARY to give you a preview of what the whole thing looks like, you shouldn't follow it except if you're really an expert since a lot of things need to be done precisely, instead you should follow the easier complete steps below):
Make a Nandroid backup of /data
Backup files on internal storage
Wipe everything (internal storage + /data + system + caches), and then format data (important!)
Push and flash the OOS zip
Wipe caches and reboot (to Oreo!)
When it reboots, make sure everything (features, like Wi-Fi and fingerprint sensor) works. Don't "save anything" though, everything you do will be erased when we'll restore your backup. This is just a "test drive" for Oreo.
Reboot to TWRP, wipe Data and restore the /data backup
Run the three commands to fix Wi-Fi and fingerprints
Reboot (to System) and check everything works (don't do anything, don't change any setting, just make sure it works)
Reboot to TWRP, rename the "Android" folder to "Android_oreo" on sdcard, delete everything else on sdcard and restore your internal files
Rename the freshly restored Android (nougat) folder to "Android_nougat" and rename "Android_oreo" to "Android".
Flash Magisk, wipe dalvik+cache and reboot to System
When in Android, everything should work except some apps won't have their data. This is normal. Open a terminal (either on your phone using Termux or from your PC using adb shell), elevate using su and rename "Android" to "Android_oreo" and "Android_nougat" to "Android" (this is so that it correctly restores permissions)
If everything works fine, delete the "Android_oreo" folder
First, if you have Xposed Framework (systemless or not) installed, uninstall it. Next, if needed, uninstall any Magisk module that is "Nougat-only" to prevent any problems afterwards.
Boot the phone to bootloader/fastboot (either using advanced reboot, or by using volume down button when you start your phone) and boot to the TWRP recovery by doing
Code:
C:\> fastboot boot twrp-3.2.1-0-oreo-8.1-codeworkx-cheeseburger.img
from your PC.
Next, in TWRP, make a backup of /data (using the Backup button). Then, still while in TWRP, run the following commands:
Code:
C:\> adb shell
~ # cd /sdcard
/sdcard # tar cvf twrp.tar TWRP
/sdcard # md5sum twrp.tar
<< md5 checksum of twrp.tar >>
/sdcard # exit
C:\> adb pull -p /sdcard/twrp.tar
When the above command has finished, make sure that the checksum of the received twrp.tar file matches the one previously displayed.
If it doesn't match, delete the file and run adb pull again. Don't continue following this guide until you have received a 1:1 (checksum-wise) backup of /data.
Code:
C:\> adb shell
<< WARNING: dangerous command! double check the following line is correct before pressing enter! >>
~ # rm -rf /sdcard/TWRP
~ # rm /sdcard/twrp.tar
That was for /data. Now, the backup for the internal storage:
Code:
~ # cd /sdcard
/sdcard # du -csh
<< you should see here the total size of sdcard, that'll give you an idea of how long it'll take >>
/sdcard # tar cvf sd.tar element1 element2 element... elementN
<< in the command above, replace "element1..N" by a space-separated list of what you want to have in the backup.
Keep in mind that your list HAS to contain the element "Android" (case is important). It contains the app data.
Let's say for example you want to keep only the photos you have taken (and nothing, nothing else that was on internal storage).
The photos are in the folder DCIM, so the command will look like this:
tar cvf sd.tar Android DCIM
(because you want DCIM, and Android has to be in the list, no matter where)
>>
/sdcard # md5sum sd.tar
<< md5 checksum of sd.tar >>
/sdcard # exit
C:\> adb pull -p /sdcard/sd.tar
When the above command has finished, make sure that the checksum of the received sd.tar file matches the one previously displayed.
If it doesn't match, delete the file and run adb pull again.
Keep in mind that anything you don't put in that list will not be backed up and will be lost!
Now, you have a backup for all the important stuff so we can start doing the real sh*t.
Now, the important step:
Go back to the TWRP home screen, press "Wipe", "Advanced Wipe" and there check "Dalvik / ART Cache", "Cache", "System", "Data" and "Internal Storage". Confirm using the slider at the bottom of the screen. Press the home button, then "Reboot" and "FastBoot". Now, type the same fastboot command as in the previous step to boot the recovery image. You'll enter the recovery as before.
Now, on your PC, in the terminal, type
Code:
adb push -p OnePlus5Oxygen_23_OTA_029_all_1801292040_d71af3d.zip /sideload
(note: here, we are not using "adb sideload", we are really using "adb push"). In TWRP, click Install, in the file manager go to /sideload and select the OOS zip file. Confirm by sliding. If you get an error, go back to home, click Mount and ensure System is not checked. Then try installing again. If it still does not work, reboot to fastboot, type command again, get to the recovery and install again.
When the zip-file is installed, go home, click "Wipe", "Advanced Wipe" and check both caches and confirm. Then, go home, click "Wipe" and then "Format Data". Then, go home, click "Reboot" and then "System". Your phone will now reboot to Oreo. It will take a long time, but do not turn off the phone. Let it run. On my phone, it took on average 2 minutes for that boot.
You'll be greeted by the "first boot" page. It'll ask you if you want to restore a backup or start anew, choose start anew. Connect to your Wi-Fi network and Google account. Follow all the instructions until you get to the home screen. There, make sure everything works (especially Wi-Fi and fingerprint sensor). Don't save your fingerprints yet, they will be erased afterwards. If everything works, you can continue following these instructions. If not, post a comment down there.
Now that you're at the home screen, go in the settings, About Android and click the build number 8 times to enable Developer Options. Go in there and enable advanced reboot. Then, reboot your phone into fastboot/bootloader using the power button. Type the exact same command as before to start TWRP. Once that you are in TWRP, run the following commands:
Code:
C:\> adb push -p twrp.tar /sdcard/
C:\> adb shell
~ # cd /sdcard
/sdcard # tar xvf twrp.tar
/sdcard # cp /data/misc/wifi/WifiConfigStore.xml /sdcard/
In TWRP, click "Wipe", "Advanced Wipe" and check only the "Data" partition. Confirm. Press home, then "Restore" and choose the backup in the list. Confirm to restore. Back to the terminal, we need to run the following commands otherwise Wi-Fi and fingerprints won't work:
Code:
/sdcard # cp WifiConfigStore.xml /data/misc/wifi/
/sdcard # rm /data/misc/wifi/wpa_supplicant.conf
<< WARNING: dangerous command! double check the following line is correct before pressing enter! >>
/sdcard # rm -rf /data/system/users/0/fpdata
/sdcard # rm /data/system/users/0/settings_fingerprint.xml
Note: the command above are ran from your PC in an adb shell while the phone is still in TWRP.
Reboot the phone to system and ensure Wi-Fi and fingerprints are still working. Right now you should already see your old home screen and all your apps, but the internal storage isn't there yet. Reboot in fastboot, run the command to get in TWRP.
Once TWRP has booted, run the following commands:
Code:
C:\> adb push -p sd.tar /sdcard/
C:\> adb shell
~ # cd /sdcard
<< WARNING: dangerous command! double check the following line is correct before pressing enter! >>
/sdcard # rm -rf Alarms Albums DCIM Download Movies Music Notifications Pictures Podcasts Ringtones
/sdcard # ls
<< now, look at the list of files that were printed, and rm anything left that is not called "Android" or "sd.tar"
<< WARNING: dangerous command! double check everything is correct before pressing enter! >>
if when you do rm <the thing> it tells you it's a directory, then do: rm -rf <thething>
if there's a folder called SomeFolder, do "rm -rf SomeFolder"
next, run this:
/sdcard # ls
Android sd.tar <-- expected output
/sdcard # mv Android Android_oreo
/sdcard # tar xvf sd.tar
/sdcard # mv Android Android_nougat
/sdcard # mv Android_oreo Android
If you don't have Magisk somewhere on your sd card, download it and upload it using MTP or adb. Then flash it using the Install button. Clear dalvik/cache and reboot to system.
When the phone has booted (again, it might take time), make sure USB debugging is enabled and run the following commands:
Code:
C:\> adb shell
OnePlus5:/ $ su
<< here, you might see a Magisk screen asking for superuser access. Allow. >>
OnePlus5:/ $ cd /sdcard
OnePlus5:/sdcard $ mv Android Android_oreo && mv Android_nougat Android
Now, try some apps and make sure all the data is there (especially games and Netflix/Hulu/etc). If everything is there, and the phone works properly, go back in the terminal and type:
Code:
OnePlus5:/sdcard $ rm -rf Android_oreo
Optionally, start the TWRP app and flash it, it can always be useful. You can also reboot to fastboot to do that.
Now reboot your phone (normal reboot) one last time.
There, working OOS 5.0.2 / Android 8.0.0 phone with no data loss.
Frequently Asked Questions
How long does the whole thing take?
Highly depends on the amount of data you have on your phone. Since it the USB port only supports USB 2.0, it may take 4 or 5 hours in total.
Will doing this void my warranty?
No.
Will I be able to install future OTA updates using the regular download-reboot-flash-twrp procedure?
Yep. Just use the regular method as you would have on Nougat.
Will I lose my data?
If you follow all the instructions, no. Even if you don't follow them, as soon as you have made a backup of /data and internal storage, then no matter how bad you screw up you could always get a working phone back.
I followed the instructions and now my phone doesn't work
Boot in TWRP, wipe everything, reflash.
questions will be added there in the future
Having WiFi and fingerprint issues
You sure it is a good idea to just delete those files? I would have guessed that I need to replace these (nougat version from backup) with the oreo version to have it working just like before the restore.
Code:
/sdcard # rm /data/misc/wifi/wpa_supplicant.conf
/sdcard # rm -rf /data/system/users/0/fpdata
/sdcard # rm /data/system/users/0/settings_fingerprint.xml
I'm having the issues with wifi and fingerprints. Neither one is working. I'll try to figure out how to fix this.
@zdimension Thanks for this guide, I don't have time to test it yet, but I have a question
pdluke said:
Code:
/sdcard # rm /data/misc/wifi/wpa_supplicant.conf
/sdcard # rm -rf /data/system/users/0/fpdata
/sdcard # rm /data/system/users/0/settings_fingerprint.xml
Click to expand...
Click to collapse
At this point in the procedure, adb shell is still using root (before flashing magisk) ? How is that possible ? Does the adb /sideload preserve root ?
olivier380 said:
@zdimension Thanks for this guide, I don't have time to test it yet, but I have a question
At this point in the procedure, adb shell is still using root (before flashing magisk) ? How is that possible ? Does the adb /sideload preserve root ?
Click to expand...
Click to collapse
These commands should be run while the phone is in TWRP. Also note that adb /sideload is not used here, only adb push.
pdluke said:
You sure it is a good idea to just delete those files? I would have guessed that I need to replace these (nougat version from backup) with the oreo version to have it working just like before the restore.
Code:
/sdcard # rm /data/misc/wifi/wpa_supplicant.conf
/sdcard # rm -rf /data/system/users/0/fpdata
/sdcard # rm /data/system/users/0/settings_fingerprint.xml
I'm having the issues with wifi and fingerprints. Neither one is working. I'll try to figure out how to fix this.
Click to expand...
Click to collapse
If you delete them, they will be generated automatically at the next system boot. But you could also make a backup of those three files before wiping /data, store that somewhere, restore Nougat /data and then restore your backup of those three files. The result would be the same.
Note: actually, not exactly. Erasing the first file won't change anything since it's not used anymore in Oreo, but the two other files contain the fingerprint configuration (list of saved fingerprints). So,
Either you remove the files and you have to save your fingerprints again at next boot
Either you restore them from an Oreo backup and you'll get the fingerprints you had saved during the "first boot" procedure when you rebooted the phone right after flashing the OS
But the result is mostly the same: everything works. Deleting the files ensures you get something clean. If you restore from an Oreo backup I can't guarantee the result (as it may interfere with other files from the Nougat backup).
10 bucks to make a script to do this all for me haha.
@zdimension Thanks for the clarification Another thing you might add to the files to download would be Magisk (optionally). In this kind of guide, I've always find it useful to download everything first.
olivier380 said:
@zdimension Thanks for the clarification Another thing you might add to the files to download would be Magisk (optionally). In this kind of guide, I've always find it useful to download everything first.
Click to expand...
Click to collapse
Oops, forgot to add it
I added the link, and also instructions for how to un-root afterwards for those who would want it.
To improve the guide, here are some ideas :
- You should highlight that rm -rf is a very dangerous command, and that it needs to be checked twice (especially the targeted folder)
- It could be useful to use the du -csh command to check the size of a folder (to estimate the backup time for example).
- As a safety measure, one could md5sum the tar file before and after using adb pull
What do you think ?
olivier380 said:
To improve the guide, here are some ideas :
- You should highlight that rm -rf is a very dangerous command, and that it needs to be checked twice (especially the targeted folder)
- It could be useful to use the du -csh command to check the size of a folder (to estimate the backup time for example).
- As a safety measure, one could md5sum the tar file before and after using adb pull
What do you think ?
Click to expand...
Click to collapse
Thanks for the ideas! I updated the post (and I added a changelog at the bottom for future reference).
Followed guide for successful upgrade from 4.5.15 encrypted, unlocked bootloader w/ Magisk root.
One note, after the first complete wipe and flash of the full ROM, it was getting stuck on first boot and never completed. Discovered that I needed to not just wipe the Data partition but Format it in TWRP, to clear out the old encryption I think. Magisk wouldn't install either until I did this.
@debork thanks for the positive feedback (all the merit goes to @zdimension of course)
@zdimension there are many people in the other thread https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003 that tried (unsucessfully) to upgrade from 4.5.15 to 5.0.1, maybe a link to this topic could be useful for them (if it's not too late).
Regarding the
Go back to the TWRP home screen, press "Wipe", "Advanced Wipe" and there check "Dalvik / ART Cache", "Cache", "System", "Data" and "Internal Storage".
Click to expand...
Click to collapse
I think it should be highlighted in red, since it is the actual "clean flash" (AFAIU, correct me if I'm wrong).
if we only have the BL unlocked non root and stock recovery can we only ota without any loss of data ?
debork said:
Followed guide for successful upgrade from 4.5.15 encrypted, unlocked bootloader w/ Magisk root.
One note, after the first complete wipe and flash of the full ROM, it was getting stuck on first boot and never completed. Discovered that I needed to not just wipe the Data partition but Format it in TWRP, to clear out the old encryption I think. Magisk wouldn't install either until I did this.
Click to expand...
Click to collapse
Thanks for feedback, I will add that to the guide (although it worked with just Wipe for me )
zdimension said:
Thanks for feedback, I will add that to the guide (although it worked with just Wipe for me )
Click to expand...
Click to collapse
Have you rooted the 4.5.15 with Magisk or SuperSU (which is not compatible with Oreo anymore) ?
olivier380 said:
Have you rooted the 4.5.15 with Magisk or SuperSU (which is not compatible with Oreo anymore) ?
Click to expand...
Click to collapse
I stopped using SuperSU when it was sold to that shady company. Also, Magisk is better imo.
quick05 said:
if we only have the BL unlocked non root and stock recovery can we only ota without any loss of data ?
Click to expand...
Click to collapse
Official OnePlus support said that nothing is guaranteed if your bootloader is unlocked. But since you're on stock recovery + non rooted, you could always try. But backup everything first. Some people here on XDA have reported that it doesn't work, though.
Just followed your guide with no problems. Thank you very much!! I can confirm also that you need to format data after the wipe otherwise it gets stuck in a bootloop!
Thanks so much for this. I was able to successfully follow the guide and get upgraded to 5.0.1 without losing any data. In fact, I even messed up one step by failing to include the Android directory in the sdcard.tar backup (perhaps that should be more explicit), but it doesn't seem to have affected everything; all of my apps seem to have retained their data.
A few notes:
1. The file size of twrp.tar was ~14GB but when executing the pull command, it recognized it as only ~1.3 GB. As a result, the pull was not complete until it reached over 1000%. All the more reason to do the md5 check.
2. As others stated, I needed to format the data partition, not just wipe it.
3. I might recommend also including a "summary" version somewhere on what this guide does. Scrolling through the guide the first time, it seemed pretty daunting, but really all that you're doing is: backing up data partition and internal storage; wiping device; flashing Oreo ROM; tweaking a few files; and restoring backed up data and internal storage.
Thank you again so much! Glad to finally be on Oreo.
elight3 said:
Thanks so much for this. I was able to successfully follow the guide and get upgraded to 5.0.1 without losing any data. In fact, I even messed up one step by failing to include the Android directory in the sdcard.tar backup (perhaps that should be more explicit), but it doesn't seem to have affected everything; all of my apps seem to have retained their data.
A few notes:
1. The file size of twrp.tar was ~14GB but when executing the pull command, it recognized it as only ~1.3 GB. As a result, the pull was not complete until it reached over 1000%. All the more reason to do the md5 check.
2. As others stated, I needed to format the data partition, not just wipe it.
3. I might recommend also including a "summary" version somewhere on what this guide does. Scrolling through the guide the first time, it seemed pretty daunting, but really all that you're doing is: backing up data partition and internal storage; wiping device; flashing Oreo ROM; tweaking a few files; and restoring backed up data and internal storage.
Thank you again so much! Glad to finally be on Oreo.
Click to expand...
Click to collapse
Thanks for the feedback! I'll add a summary to the guide.

Categories

Resources