Related
Hello all.
I've compiled the latest ClockworkMod recovery for the Tattoo. In addition to the normal features it has, this is using a custom smaller font, so the text fits better on a QVGA screen.
If you're already rooted, you can flash it with "flash_image recovery recovery.img" (after running "su" first) from a terminal shell prompt, or from adb shell.
v2.5.1.8 is the last version included in CyanogenMod 6 sources
v3.0.0.5 is the new recovery from CyanogenMod 7 sources
How to flash instructions
Credits:
CM Team/Koush
KalimochoAz
NForce2506.02.2011 - Repack of 3.0.0.5 with advanced backup and wipe all function. Wipe all will completely format and erase all partitions.
Can you please tell me, in what way exactly is this Recovery better than Amon-RA?
They both do the same basic things. What I find better with ClockworkMod is:
Can turn off signature verification (faster to install roms, and can install unsigned zip files)
Can select zip files in subfolders
Individually select which NAND partition to restore
Can use joy button and back key to navigate
Smaller font (in this special version), so you get to see all text on screen on QVGA devices
arco68 said:
They both do the same basic things. What I find better with ClockworkMod is:
Can turn off signature verification (faster to install roms, and can install unsigned zip files)
Can select zip files in subfolders
Individually select which NAND partition to restore
Can use joy button and back key to navigate
Smaller font (in this special version), so you get to see all text on screen on QVGA devices
Click to expand...
Click to collapse
Is possible to add Ps3 Jailbreaking?
francians said:
Is possible to add Ps3 Jailbreaking?
Click to expand...
Click to collapse
You would need to ask the ClockworkMod author for that feature I'm afraid, but I doubt he well add it. Take a look here though.
arco68 said:
You would need to ask the ClockworkMod author for that feature I'm afraid, but I doubt he well add it. Take a look here though.
Click to expand...
Click to collapse
I asked a couple of weeks ago, but no answer.. I realy like clockworkmod and I'm afraid to change recovery.
Thanks. Good job!
Amazing recovery
Thank you very very much for this recovery. ROM Manager now works properly. BTW, where do I download ClockworkMod Recoveries for HTC Wildfire with my computer? I dont want to use my expensive 3G connection to download and want to use the school network.
sunitknandi said:
BTW, where do I download ClockworkMod Recoveries for HTC Wildfire with my computer? I dont want to use my expensive 3G connection to download and want to use the school network.
Click to expand...
Click to collapse
Only available through ROM Manager as far as I know, unless someone compiled it and made it available over at the Wildfire forums.
ROM manager does not work with me although I´ve installed this recovery... It seems that the rom manager does not recognize it and it keeps asking me to download clockwork recovery again, and there is no Clockwork recovery for tattoo in that menu????
What seems to B the problem??
ClockworkMod recovery for the Tattoo isn't added to ROM Manager yet. Until now Tattoo owners had to use the Wildfire/Buzz recovery. I'll contact the author and ask if he can add this recovery for the Tattoo, so it's available from ROM Manager.
Downloading images
arco68 said:
Only available through ROM Manager as far as I know, unless someone compiled it and made it available over at the Wildfire forums.
Click to expand...
Click to collapse
If I knew where the images were hosted, I could fetch them through PC.
sorhe said:
ROM manager does not work with me although I´ve installed this recovery... It seems that the rom manager does not recognize it and it keeps asking me to download clockwork recovery again, and there is no Clockwork recovery for tattoo in that menu????
What seems to B the problem??
Click to expand...
Click to collapse
Press menu button and select "manually installed clockworkmod" or similar option.
sunitknandi said:
Press menu button and select "manually installed clockworkmod" or similar option.
Click to expand...
Click to collapse
That doesn´t help!
With clockworkmod recovery I cannot flash some roms which flashed fine with maverick recovery. The installation aborted with this error:
E:Board does not support mtd utils.E:Failure at line 420:
write_raw_image PACKAGE:boot.img BOOT:
The rom is actually flashed, and only boot.img not. So I can boot the rom after manually flash the boot.img.
Is there any way to include mtd utils future in this recovery, or must to return to maverick?
I think it's a bug in clockworkmod. They changed some detection routines in the latest versions, which seems to have broken flashing to mtd when rom is using update-script instead of updater-script. I've heard that 2.5.0.9 is the latest which it worked correctly with. I'll look into it at some point unless they release a new version which fixes it.
clockworkmod 2.5.1.4 seems to be already out!
arco68 please could you take a look here: https://github.com/klutsh/android_bootable_recovery
or here: https://github.com/klutsh/psfreedom-kernels-patch
could you add psFreedom support?
edit: please fix also the font size for the tattoo screen
I suppose it can be done, so I'll take a look. Thanks for the links.
Ran into some problems with the psfreedom recovery. Patching the kernel and compiling the recovery wasn't a problem, but mounting usb mass storage doesn't work. As far as I can see, there seems to be some bits missing in one of the files for the kernel patch for the Tattoo. I could have used the code from one of the other phones kernel patches, but unfortunately the kernel for the Tattoo is just too different from the other ones, that it can't be easily done. Dunno who the hell coded the board sources for the Tattoo, but I suspect he got fired or something, because sources for all other phones after the Tattoo are much more organized and similar to each other.
arco68 said:
Ran into some problems with the psfreedom recovery. Patching the kernel and compiling the recovery wasn't a problem, but mounting usb mass storage doesn't work. As far as I can see, there seems to be some bits missing in one of the files for the kernel patch for the Tattoo. I could have used the code from one of the other phones kernel patches, but unfortunately the kernel for the Tattoo is just too different from the other ones, that it can't be easily done. Dunno who the hell coded the board sources for the Tattoo, but I suspect he got fired or something, because sources for all other phones after the Tattoo are much more organized and similar to each other.
Click to expand...
Click to collapse
I think is very hard find what's missing to make it works.. can you do it?
I know you are workin' also on a wonderful rom, but also psfreedom is a nice project that need a skilled man
I see the kernel patches for the Tattoo is no longer there. When he adds a working patch I'll try again.
I've been trying to install milaq's 4.4 ROM on my Touchpad and I'm getting a bit stuck.
I've removed my previous 4.0.4 build so that I could start fresh and get my head around the data/media build. I've tried following the text guide and Roland's video guides but keep getting stuck at the same point.
I put the following files in the "cminstall" folder on my touchpad and ran ACMEinstaller5M:
cm-11-20140223-UNOFFICIAL-tenderloin
gapps-kk-20140105
recovery-clockwork-6.0.4.7-tenderloin
moboot_038-tenderloin
update-cm-tenderloin-data_resize_12228-0.1
So far I get the moboot menu and am able to get into the CWM-Based Recovery v6.0.4.7. This is where I'm stumped, I have no idea how to install the milaq ROM. I've had experience putting various CM Android builds on different devices (HD2, Defy+, Touchpad) but I'm struggling with this one. I know that I won't be able to install it the way I'm used to but I've tried searching and can't find what I'm supposed to do next.
I know this is a bit of a simple request but could anyone help me out with the next step? Once I'm past that, it'll be plain sailing I'm sure.
Thanks in advance.
yeoldgreat1 said:
I've been trying to install milaq's 4.4 ROM on my Touchpad and I'm getting a bit stuck.
I've removed my previous 4.0.4 build so that I could start fresh and get my head around the data/media build. I've tried following the text guide and Roland's video guides but keep getting stuck at the same point.
I put the following files in the "cminstall" folder on my touchpad and ran ACMEinstaller5M:
cm-11-20140223-UNOFFICIAL-tenderloin
gapps-kk-20140105
recovery-clockwork-6.0.4.7-tenderloin
moboot_038-tenderloin
update-cm-tenderloin-data_resize_12228-0.1
So far I get the moboot menu and am able to get into the CWM-Based Recovery v6.0.4.7. This is where I'm stumped, I have no idea how to install the milaq ROM. I've had experience putting various CM Android builds on different devices (HD2, Defy+, Touchpad) but I'm struggling with this one. I know that I won't be able to install it the way I'm used to but I've tried searching and can't find what I'm supposed to do next.
I know this is a bit of a simple request but could anyone help me out with the next step? Once I'm past that, it'll be plain sailing I'm sure.
Thanks in advance.
Click to expand...
Click to collapse
I just inherited an already rooted/android touch pad, so I'm in your same shoes right now. So i'm following close! haha.
I'm very new to the whole webos stuff here, but very experienced with rooting android.
But at this point, don't you just start flashing the .zips in clockwork after a full wipe (wipe factory, cache, davlik)?
BRUTAL BROCK said:
I just inherited an already rooted/android touch pad, so I'm in your same shoes right now. So i'm following close! haha.
I'm very new to the whole webos stuff here, but very experienced with rooting android.
But at this point, don't you just start flashing the .zips in clockwork after a full wipe (wipe factory, cache, davlik)?
Click to expand...
Click to collapse
That's what I thought but the ACMEinstaller wipes everything in the cminstall folder. Also, CWM only has the option to install zips from the sdcard which isn't there.
AcmeInstaller won't install the zip that resizes your partitions, and when you flash a data/media rom, the sdcard or media partitions are only accessible thru the rom itself so you won't be able to see them in recovery.
I think you will have to start again. Installing a data/media rom from a fresh install is, to be honest, a pain in the ass! You need to have a non-data/media build installed, ie. Jelly Bean/CM10.x, then resize partitions, etc, etc.
If you want to install kitkat from a fresh start, go for flintman's non-data/media version in the link in this post, and this recovery (20121215). Rename rom update-xxx, same for recovery, include moboot, and also have appropriate gapps to flash.
Hope this helps.
Oh yeah, and don't use AcmeInstaller5M, use the one ending in 5E =)
Data media install guide
Additional resources:
[ROM GUIDE] How to install Android on the HP TouchPad "The Easy Way"
[ROM GUIDE] How to install Android 4.4.2 Data Media builds on the HP TouchPadhttp://forum.xda-developers.com/showpost.php?p=42505399&postcount=2http://forum.xda-developers.com/showpost.php?p=42505399&postcount=2
RolandDeschain79 said:
You can't install CM11 data media builds with the ACMEInstaller. Here is my newest thread that explains how to get them fully installed. Please leave some feedback once you get it setup. :highfive:
[ROM GUIDE] How to install Android 4.4.2 Data Media builds on the HP TouchPad
Click to expand...
Click to collapse
That guide has been really helpful so far. I'm stuck at the last bit though.
I've installed PhilZ Clockworkmod but I don't know what to do from there. When I turn on the USB Drive, my PC can only see one SDcard (the WebOS one it sees normally) so I can't copy over the CM11 files to the Android one.
Any ideas?
If anyone is still having problems, this thread helped me. The instructions are in post #7 but you should read the preceding posts for background info.
Hello everyone, recently i switched my Main Android to AOKP from the build at RootzWiki for Kitkat and choose to remove WebOS. At the first flash i tried Pacman rom but the sound problem was the main reason i tried AOKP. When i flashed pacman, i was using the Touchpad Toolbox and removed the WebOS stuff tried the roms for some stuff and decide to revert to a stable Kitkat one.
So my main problem was the default boot option was Cyanogenmod, as i know, i just need to go to the boot menu and erase the two file for cm based build. After rebooting, the main option was the recovery... I tried to switch recovery and between the 3 recommended in TP Toolbox OP and always the same result, recovery by default... Is there any tool in Android for doing this ? I know there is one in WebOS and if i wanted to keep it i could have used it.
Also, is there any utility to the media partition used for sharing between WebOS and Android in non data/media build ? It is a good 800mb partition wasted in my mind, idk if this was used for the boot menu or anything for recovery. If in result i need to use the toolbox again for reflashing the AOKP build, will it erase my personal data ? I don't mind for doing a partial data erasing (android app) or doing a dirty flash but i just don't want to transfert all my data back from my computer.
Thank for your answer guys.
Atari-San said:
Hello everyone, recently i switched my Main Android to AOKP from the build at RootzWiki for Kitkat and choose to remove WebOS. At the first flash i tried Pacman rom but the sound problem was the main reason i tried AOKP. When i flashed pacman, i was using the Touchpad Toolbox and removed the WebOS stuff tried the roms for some stuff and decide to revert to a stable Kitkat one.
So my main problem was the default boot option was Cyanogenmod, as i know, i just need to go to the boot menu and erase the two file for cm based build. After rebooting, the main option was the recovery... I tried to switch recovery and between the 3 recommended in TP Toolbox OP and always the same result, recovery by default... Is there any tool in Android for doing this ? I know there is one in WebOS and if i wanted to keep it i could have used it.
Also, is there any utility to the media partition used for sharing between WebOS and Android in non data/media build ? It is a good 800mb partition wasted in my mind, idk if this was used for the boot menu or anything for recovery. If in result i need to use the toolbox again for reflashing the AOKP build, will it erase my personal data ? I don't mind for doing a partial data erasing (android app) or doing a dirty flash but i just don't want to transfert all my data back from my computer.
Thank for your answer guys.
Click to expand...
Click to collapse
1)Go back to the boot folder open moboot.default and change CM to AOKP.
2)Jcsullins TPToolbox can see the media partition and access it, so can his CM11 rom or the Evervolv rom. Take a look at this video and thread, it should clear up most of the info for you.
New Super Easy Way Guide and video available
[ROM GUIDE]How to use the TouchPad Toolbox to install Android "The Super Easy Way"(DM & Non-DM)
RolandDeschain79 said:
1)Go back to the boot folder open moboot.default and change CM to AOKP.
Click to expand...
Click to collapse
Thank you, i did not know we could open this file as a plain text file. Thank you. ^_^
Gonna watch the video too. Thank. ^_^
So, after watching your video and mounting the media partition from the TP Toolbox (because my rom cannot open it), it seem there is not anything worth in this partition and it seem there is no delete option while resizing it. So i guess the old commandline recovery could help me to delete the media partition and i could use the toolbox for resizing it to the max. I still don't know if it is safe to delete but seem there's only android stuff in the partition. Thank Rolland for the info again. :highfive:
I recently started playing pokemon go and I am getting really frustrated while playing because it lags soo much and my phone is generally quite slow now. I have been told rooting and installing a good ROM can help with this and I have never attempted this, could someone please explain what rooting and ROMs are and their benefits and a how to guide for this phone and also the best ROM?
I know there are loads of threads on this but if someone could link me best threads I would be eternally gratefull!!
First of all, which variant of LG L90 is your phone (D4xx)? And could you go to Menu > General > About Phone > Software Information and tell me your "version" (v10x or v20x)?
Root is the ability for the user to take total control of his phone, from doing as little as automate 3G activation when an app is open to instaling custom ROMs, which are custom firmwares that you can install in your device, just like the stock one you're currently in, but with some modifications made by its creators. As for advantages, with root you have more freedom over your device, and with Custom ROMs you have some tweaks, which change depending on the ROM you choose to install, going from just porting newer firmwares to older devices to being an entire new OS (Operational System, in case you don't know).
Hyoretsu said:
First of all, which variant of LG L90 is your phone (D4xx)? And could you go to Menu > General > About Phone > Software Information and tell me your "version" (v10x or v20x)?
Root is the ability for the user to take total control of his phone, from doing as little as automate 3G activation when an app is open to instaling custom ROMs, which are custom firmwares that you can install in your device, just like the stock one you're currently in, but with some modifications made by its creators. As for advantages, with root you have more freedom over your device, and with Custom ROMs you have some tweaks, which change depending on the ROM you choose to install, going from just porting newer firmwares to older devices to being an entire new OS (Operational System, in case you don't know).
Click to expand...
Click to collapse
Thank you soo much for your reply and sorry about my late reply. My variant is LG-D405n and software version is V20c-234-30. I think I understand what Root and ROM is thx.
So could you link me to the best method to root and install ROM on my phone?
And what is the best ROM for my device to free up the RAM and CPU used on my device to increase my phone speed?
First of all, install these required apps:
http://king.myapp.com/myapp/kdown/img/NewKingrootV4.9.6_C151_B309_en_release_2016_08_18_105203.apk (For rooting)
https://play.google.com/store/apps/details?id=com.cgollner.flashify (For flashing the Custom Recovery)
https://play.google.com/store/apps/details?id=jackpal.androidterm (For terminal emulation)
Custom Recovery:
TWRP: http://forum.xda-developers.com/devdb/project/dl/?id=18679&task=get
Personally recommended Custom ROM, CyanogenMod (Ports Android updates to older phones plus some tweaks) and Gapps (Google Apps, it's needed to have things like calculator, play store, etc):
CM13: https://download.cyanogenmod.org/get/jenkins/175208/cm-13.0-20160820-SNAPSHOT-ZNH5YAO0J8-w7.zip
Gapps: http://opengapps.org/ (Go to this link, select ARM in platform, 6.0 in android and Nano in variant, then just click the download image button)
Put the TWRP img, the CM13 rom img and gapps on microSD or internal storage. Open Kingroot and click on the green button after the 3 introduction images. After a few minutes, your device will be rooted. Grab this file: http://forum.xda-developers.com/lg-...0w7xxshoxx-t2826150/post54358527#post54358527 (D405n_v20a_patched_aboot, don't worry, it's okay if you flash a different software version aboot as long as it's the same device as yours. The only "problem" you can have is to have your software version changed to v20c, which if I remember correctly, can be fixed using Bootstacks), transfer it to your phone and open Terminal Emulator. Then input the following commands:
su
dd if=(aboot.bin storage directory) of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Then, go to flashify and flash your custom recovery image (TWRP or CWM) in the flash recovery img option. After this, reboot into recovery by pressing Volume Down + Power and when you see the LG Logo, let go of the Power button and press it again. Then select yes two times with the volume keys for selection and power button to actually select the options (Don't worry, your device won't be factory resetted if you successfully installed custom recovery). Then, if you want, make a backup of your entire phone (recommended, just in case something goes wrong or if you just want your apps back when the process is done) in the Backup section and then do a factory reset through the Wipe option (Don't select anything, just swipe the bar). Select the Install option and select your ROM zip. After this, do the same process as the ROM installation but this time with Gapps zip. There you go, now you have CM13 installed. If you want root again, you don't have to install Kingroot again this time, as CM13 has built-in root, just enable Developer options and activate root and you're ready to go. Also, if you want the apps you had before the installation, just restore your backup (ONLY THE DATA PARTITION, otherwise CM13 will be uninstalled and replaced with stock ROM). If something goes wrong and you accidentally brick your device, just reply and I'll help you fix it. (If helped, click the Thanks! button)
Hyoretsu said:
Grab this file: http://forum.xda-developers.com/lg-...0w7xxshoxx-t2826150/post54358527#post54358527 (D405n_v20a_patched_aboot, don't worry, it's okay if you flash a different software version aboot as long as it's the same device as yours. The only "problem" you can have is to have your software version changed to v20c, which if I remember correctly, can be fixed using Bootstacks), transfer it to your phone and open Terminal Emulator. Then input the following commands:
su
dd if=(aboot.bin storage directory) of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Click to expand...
Click to collapse
Hi, thank you so much, I finally rooted my device but I am having problems with the script part of the terminal emulator.
I wrote upto msm_sd and then this happen automatically:
View attachment 3865360
View attachment 3865361
View attachment 3865362
View attachment 3865363
I don't know what to do here..
EDIT: Also am I meant to have the SuperSU/SuperUser app installed once rooted? Then get a popup in the terminal emulator for permission for its root access?
Firebird3334 said:
Hi, thank you so much, I finally rooted my device but I am having problems with the script part of the terminal emulator.
I wrote upto msm_sd and then this happen automatically:
View attachment 3865360
View attachment 3865361
View attachment 3865362
View attachment 3865363
I don't know what to do here..
EDIT: Also am I meant to have the SuperSU/SuperUser app installed once rooted? Then get a popup in the terminal emulator for permission for its root access?
Click to expand...
Click to collapse
You have to change "(aboot.bin storage directory) with the directory in which aboot.bin is stored. And no, you don't need SuperSU, when you use the su command, a KingRoot window will open, just say yes.
EDIT: Wahay! It works! Thank you soo much for your help!
EDIT 2: I can't seem to find the option to edit my recent button in settings. What can I do?
Firebird3334 said:
EDIT: Wahay! It works! Thank you soo much for your help!
EDIT 2: I can't seem to find the option to edit my recent button in settings. What can I do?
Click to expand...
Click to collapse
If it's the menu button, I don't know of any way to change them, as Android updates change them. For example, my phone in KitKat used the home button for recent apps, in Lollipop it used the menu button for recent apps, and when I installed CM13, it used the home button again.
EDIT: Browsing LG L90 xda, I found this: http://forum.xda-developers.com/lg-l90/themes-apps/mod-button-remaps-l90-t3145146
Hyoretsu said:
If it's the menu button, I don't know of any way to change them, as Android updates change them. For example, my phone in KitKat used the home button for recent apps, in Lollipop it used the menu button for recent apps, and when I installed CM13, it used the home button again.
EDIT: Browsing LG L90 xda, I found this: http://forum.xda-developers.com/lg-l90/themes-apps/mod-button-remaps-l90-t3145146
Click to expand...
Click to collapse
You have helped me out so much already! Thank you so much!
But just one more thing though, could you explain how to install magisk and xposed in layman's term so I can use Android Pay?
I don't know what magisk is nor layman's term, but to install Xposed just go to this thread: http://forum.xda-developers.com/showthread.php?t=3034811, download both Xposed installer apk and xposed zip. Install xposed apk and flash xposed zip
Hello,
Help me please I'm getting Error 7 and after twrp reflash Error executing updater binary in zip
I did all the previus steps phone LG L90 d405n is rooted and bootloader is unlocked and rom downgraded to KK v10b
Now I want to flash CM or RR rom but I simply can't!
First I was getting error 7 when flashing I found out that I need TWRP 2.8.7 build 2 to flash so I found it and flashed. Now I'm getting ''error executing updater binary in zip twrp'' and I can't flash any rom.?*
I tried deleting first assert lines in updater-script from this?*thread?*but It didn't helped in any way...
Any ideas? Why the hell it is so ****ing complicated to flash custom on this ****ty device? Can't it work like Nexus4 or any other normal device??*
Thanks in advance for any tips&trics
PS. I can't open new thread dunno why...
amonlb said:
Hello,
Help me please I'm getting Error 7 and after twrp reflash Error executing updater binary in zip
I did all the previus steps phone LG L90 d405n is rooted and bootloader is unlocked and rom downgraded to KK v10b
Now I want to flash CM or RR rom but I simply can't!
First I was getting error 7 when flashing I found out that I need TWRP 2.8.7 build 2 to flash so I found it and flashed. Now I'm getting ''error executing updater binary in zip twrp'' and I can't flash any rom.?*
I tried deleting first assert lines in updater-script from this?*thread?*but It didn't helped in any way...
Any ideas? Why the hell it is so ****ing complicated to flash custom on this ****ty device? Can't it work like Nexus4 or any other normal device??*
Thanks in advance for any tips&trics
PS. I can't open new thread dunno why...
Click to expand...
Click to collapse
First of all, you don't need to use that TWRP build, you can use the latest one. To fix the only errors that should appear (Updater error 7 and 6), delete the first lines of updater-script until you reach the ui_print part (the first line of your file should be "ui_print("Target: 1471683591");"). Also, delete any double spaces that exist (there should be two, one before "abort" at line 27 and the other before "abort" at line 30). If it still gives the same error, try wiping Cache, data, system and dalvik-cache partitions, try to install the ROM, it'll give the error. Now, reboot your phone and try to install without wiping anything. (To properly see the line indications, open the file using Notepad++)
Hello all,
First of all, I'm not very familiar with recovery/rooting on phones. Although my daytime job is customizing embedded linux, so I have some knowledge
I got my hand on a few Alcatel 5033d devices, on which I want to run a software I created. However, this software needs access the notifications. And Android GO doesn't allow that. So I need to change the low-ram flag in build.prop. If possible I also want to remove the google apps from it and make my app a system app. But for the rest I'm happy, so don't need linageos or anything.
Is there a way to make a custom system.img, based on the original one, with only build.prop changed and load this complete firmware via the original recovery mode? I already saw you could load things via sdcard (adb doesn't work in stock recovery -> authentication required).
I already tried mtk-su (worked on a tablet before), but I guess that flaw is already patched
Something to try
This is from my head so if this doesnt work im sorry
1. install a custom rom.
2. install magisk onto the custom rom.
3. make a copy of the boot image
4. use "Mobile upgrade S" from alcatel to restore your phone
5. flash the backed up boot image from before.
6. if your lucky you may have root on the original system partition.
P.S i would use https://forum.xda-developers.com/alcatel-1/development/alcatel-1-root-achieved-t3970713 rom because it doesnt touch the boot partition.