Hi guys so after a long time I finally present to you the Clockworkmod recovery made for the ASUS MemoPad (ME172V)
Please note that this is a RC version and still needs a few more adjustments. However it's functional and mostly safe to use.
Now before you do anything read the guide carefully first and after that continue to flashing.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
What you need:
1.A ME172V tablet charged at least to 50%
2.A USB cable for transferring files.
3.A minimum 4GB microSD card formated to FAT32 (If it's formated to NTFS you'll have to reformat it)
4.A microSD computer adapter (optional)
1. ROOT
Ok so first you are gonna need to root this tablet.
For that we will use frank_que's root utility which can be found here http://forum.xda-developers.com/showpost.php?p=42047570&postcount=263
You extract the root zip on the root of your SD card. After you've done that, power off your tablet and insert the card now power it up again. The tablet will show a blue screen with 3 options. Using volume buttons go to root me172v and confirm via the power button. After that just follow the onscreen instructions and you will be fine.
2. SYSTEM DUMP
After that you're gonna have to create a dump of your current system files. This time we will use frank_que's system dump utility which can also be found on the link above (get version 2). So you do the same thing as you did for root (NOTE that you have to delete the root script from the SD card first) only this time instead of root you should select create dump. After a while the device will shut itself down.
3.RECOVERY
Once you have the dump, remove the SD card and turn the tablet on. In the meantime open the SD card and inside you will see a me172v folder and inside it a folder named dump. In the dump folder replace the mmcblk1p3.img file with the one you got here.
After that, power off the tablet and insert the SD card into it. Now power on the tablet, and when the blue screen shows select restore a previously saved dump and confirm with power. Now it will restore the partition backups made earlier only this time it will restore a modified recovery partition. After that is complete again the tablet will shut down. You remove the SD card and power it on.
In order to boot to recovery, you have to use adb since there is no button combo (yet). To do that use
Code:
adb shell
su
reboot recovery
You can do that with the terminal emulator on the tablet itself too (just without the adb shell command).
Now it should boot into a touch-enabled CWM.
Note 1: In order to flash system files, you have to go to Mounts and storage and manually mount the /system partition.
Note 2: For now you can only install zips from the internal memory. Installation from the SD card is being worked on.
Note 3: Remember to delete the script from the SD card because if you don't when you restart your tablet with that SD card inside it will start up the script.
Download: http://d-h.st/vgk
Credits:
Many thanks to franq_que for making the dump and root utilites, then thanks to crazykiddo for testing this recovery and last but not least to cybojenix for teaching me everything I know about Android as well as making some edits to this recovery.
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
reserved 2
Does it Influence future system updates?
Thanks for your perfekt work!
Gesendet von meinem ME172V mit Tapatalk 2
supertomi said:
Does it Influence future system updates?
Thanks for your perfekt work!
Gesendet von meinem ME172V mit Tapatalk 2
Click to expand...
Click to collapse
Not as far as we know. However if we get a full custom ROM, then it will.
will this CWM work for the ME173x model as well?
nycionx said:
will this CWM work for the ME173x model as well?
Click to expand...
Click to collapse
No...I really doubt it.
Sent from my Nexus 4 using XDA Premium 4 mobile app
If any developer is interested in creating CyanogenMOD for this device take a look at this thread http://forum.xda-developers.com/showthread.php?p=48827140
@nerotNS could you build a cwm for aus memo pad 10 (me102a)…?
That would be wonderful...:thumbup:
spyne82 said:
@nerotNS could you build a cwm for aus memo pad 10 (me102a)…?
That would be wonderful...:thumbup:
Click to expand...
Click to collapse
Well I could try, but I don't own the device making development for it difficult.
Many thanks ... I could assist you.... My tab is softbricked... But fastboot works...
Is there any plan to bring this to newest firmware? @nerotNS
i assume the reason we cant enter cwm via a button combo is because the stock recovery does not even have one? -nice way to drop the ball there asus lol.... unless someone knows something i dont :-/ but hey if the op ever needs a tester or any dev for that matter with this device pm here ill be happy to help
oh btw nice work to the op
Buddy.. other Dev. show me something useful to you from Malasya Blog and than i found the Original Dev on Facebook Group... CMW / TWRP recovery to WM8850/WM8950 - ICS / JB ROM's .. the sources is FB Group, Blog (TWRP ICS) (TWRP JB) (CWM) ... some mirrors links to files -> CMW / TWRP JB
---
This other Dev already tested this on WM8880 and for our surprise that works... i don't know if have bugs but works =D
fundre said:
Is there any plan to bring this to newest firmware? @nerotNS
Click to expand...
Click to collapse
Perhaps, but at some later point, right now I'm working on 5.0 for the S3
darkensx said:
i assume the reason we cant enter cwm via a button combo is because the stock recovery does not even have one? -nice way to drop the ball there asus lol.... unless someone knows something i dont :-/ but hey if the op ever needs a tester or any dev for that matter with this device pm here ill be happy to help
oh btw nice work to the op
Click to expand...
Click to collapse
The bootloader is the one to blame for not being able to boot with button combo, since they're not defined. I'm surprised why asus is locking it up so much...
DvDwx. said:
Buddy.. other Dev. show me something useful to you from Malasya Blog and than i found the Original Dev on Facebook Group... CMW / TWRP recovery to WM8850/WM8950 - ICS / JB ROM's .. the sources is FB Group, Blog (TWRP ICS) (TWRP JB) (CWM) ... some mirrors links to files -> CMW / TWRP JB
---
This other Dev already tested this on WM8880 and for our surprise that works... i don't know if have bugs but works =D
Click to expand...
Click to collapse
I'll check this out later and see what they have. Thanks for the tip
Sent from my Nexus 4 using XDA Premium 4 mobile app
dump recovery
this is my first time posting to a forum, so i hope i'm doing it right. i rooted my memo and it went correctly. then i did the dump. it saved to my sd, i changed out the file and then restarted. however, there are only the three options i have when i do the dump. create dump, reboot, power off. there is no option to recovery a saved dump. have i missed a step?
i have attached(assuming i did it correctly) a pic of the screen
nvr mind. i found the 2nd ver file and it has the recover option
How I can make full backup of my filesystem with apps and its settings to an external microSD, not internal memory?
Related
*please hold off use of safe strap until further notice. I promise you we are hard at work on it************************************************************There is a new version at the bottom of the post. Please uninstall recovery from with in your currently installed v.1 then uninstall safestrap app. Download and install v.2 and install recovery. If you already have a safe system installed you will need to reflash the zip and wipe data/factory reset. Thanks Jim for the fix! There are now 2 different versions 1 for those not running jims webtop hack and one for those of you that are. Please download the safestrap appropriate for your setup at the bottom of the page. ********************************************************************************************************************************************************************************
What works?
-Everything except mounting usb in recovery.
-Cant seem to format safe system /data
Here it is!!! Our very own Unofficial safestrap recovery!
Whats this mean? Custom rom's!!! CM7 CM9 etc! And no more fxz or cwm on every boot just to save from a softbrick.
How'd we do it?
This was a pain in the A**, Jimbridgeman and myself have worked our butts off on this. We changed the recovery.fstab around so that we are able to use the sd card as a mount point to install the /system partition as well as a separate partition for /data. So in laymen's terms, were booting from the sd.
How to Install -(From Windows)
(Partition sizes are up to you but ext3 partition should be no less then 350mb and the second fat partition should be not less then 500mb)
1.Backup your sdcard
2.Format your sdcard from your phone under settings-storage
3.Put your sdcard into some kind of card reader and place into computer
4.Download, install, and open Mini Tool http://www.partitionwizard.com/free-partition-manager.html
5. Right click on your sd card, click resize
{
"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"
}
6. Re size so that you have at least 850mb left "Unallocated"
7.Click OK
8.Click apply changes
9.Right click on unallocated partition and select create
10. Click Yes
11.I went with 1gb, this is the data partition, It needs to be at least 500mb and your settings must match mine. Primary,Fat32
12.Click apply changes
13.Right click on unallocated space, select create
14.Click Yes
15. This is the System partition and needs to be at least 350mb, Your settings must match mine. Ext3,Primay
16.Click on apply changes.
17.Click Yes.
18.You are all done! Should look something like this.
Now to install the safestrap
http://db.tt/y6xKucmg (V.2)
http://db.tt/RzY6VJTi (V.2-Running webtob hack)
Special thanks to jimbridgeman and hashcode. (JIM... I LOVE YOU!!!)
Head down below and click the thanks button, then head over to jimbridgeman's profile and click thanks again!
**You do not need to quick toggle safe system to wipe/format anymore in v.2**
Omg yes
Sent from my MB865 using XDA App
One noob question so the safe system is on the mobile internal memory or on the SD card? If on SD card is it fast enough not to cause performance issues?
Sent from my MB865 using XDA App
alcatel444 said:
One noob question so the safe system is on the mobile internal memory or on the SD card? If on SD card is it fast enough not to cause performance issues?
Sent from my MB865 using XDA App
Click to expand...
Click to collapse
The safe system is stored to the sd card, no real performance issues.. 5500ish in antutu running cm7 for the droid 3!
And with that strap i can remove my main stock rom not just install a 2nd rom on sd card ?
Thanks alot to you and jim and hashcode for your grest work i will make sure to press the thanks button alot when i get on my pc
Sent from my MB865 using XDA App
I'm assuming that like with the razr if you are using the bootstrap with on boot you have to remove it before installing the safe strap version?
Thank you
I knew it was only a matter of time!!!!!!
Thank you guys
A link worth sharing http://hash-of-codes.blogspot.com/p/how-to-safestrap.html , this is the original safestrap for D3 and RAZR done by hashcode , take a look at his blog to understand more about safestrap if you are a noob like me.
but there is only one question i need to understand using this hack can we install roms on the 1st system ( device memory ) or just on the 2nd system ( SD Card ) ?
This is what I have been using instead of the bootstrap, to use my custom ROMS... it will allow you to use your paid version of CWM the way it should be used. You can now go into CWM and select boot to CWM or flash from sdcard while still in android, and it will boot you into CWM and start flashing....
Thanks for all your hard work!
Jim
Sent from my MB865 using xda premium
So essentially, this is a dual boot system of sorts? This allows me to install a custom ROM and run it in Safe mode then go back to my factory ROM by turning off Safe mode?
lilhaiti said:
So essentially, this is a dual boot system of sorts? This allows me to install a custom ROM and run it in Safe mode then go back to my factory ROM by turning off Safe mode?
Click to expand...
Click to collapse
Yes, that pretty much sums it up.
Will this work for something like, flashing a them to the stock rom on the internal system?
same question
lilhaiti said:
Will this work for something like, flashing a them to the stock rom on the internal system?
Click to expand...
Click to collapse
Yea i have same question will this hack help us flash a rom on internal system or just on the 2nd boot
alcatel444 said:
Yea i have same question will this hack help us flash a rom on internal system or just on the 2nd boot
Click to expand...
Click to collapse
This will not work to flash ANYTHING to your internal system. It will only flash to the safe system.
Got it thanks!!!
MOD please sticky this thread.
lfaber06 said:
MOD please sticky this thread.
Click to expand...
Click to collapse
great works，and thanks for that
lfaber06 said:
*************************************************************I found a bug in the safestrap that prevents us from being able to wipe the * *dalvik cache, I beleive it is in the way i set up the partitions, I will have a re-work and a new apk out by tomorrow night hopefully********************* 1/4/2010*****************************************************************************************************************
Click to expand...
Click to collapse
great work man
but is it ... 2012 ?
Should I wait to setup safestrap until you get this fixed, or can I go ahead with it and just replace the .apk later?
mathk said:
great work man
but is it ... 2012 ?
Click to expand...
Click to collapse
Opps... lol
Calundle said:
Should I wait to setup safestrap until you get this fixed, or can I go ahead with it and just replace the .apk later?
Click to expand...
Click to collapse
I'm working on it now so it'd probably be easier to wait.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Nothing really "new", just a dedicated thread for the updated CWM.
People will no longer need to look for it in the CM11 Thread
Installation:
Make sure you have a JB bootloader (and not ICS)
flash it with flashify from play store or via fastboot using following command:
Code:
fastboot flash recovery recovery-cwm-shreps-6.0.5.0-a510.img
Download:
recovery-cwm-shreps-6.0.5.0-a510-a511.img [2ad0a1c72dcfce5ba617b408971130a4] (LZMA Compression+LVM support enabled){based on CM11/Android 4.4.4}
recovery-cwm-shreps-6.0.4.9-a510-a511-lvm.img [781d89a6ed452255cc77a1c12187e892] (LZMA Compression+LVM support enabled){based on CM11/Android 4.4.4}
Warning !
Booting on CWM with LVM enable will format /system and remount it using LVM => /system will be 677MB free space instead of 350MB
Make a backup before flashing & booting on it !
Only ROM with LVM support will be compatible with this Recovery.
To get back to normal "/system", flash a regular CWM or TWRP recovery and format /system
Then restore a backup or flash a "normal" ROM (without LVM)
Click to expand...
Click to collapse
Download (old build):
recovery-cwm-shreps-6.0.4.9-a510-a511.img [4bb1324a9f977cb3265c4ed99918d620] (LZMA Compression enabled){based on CM11/Android 4.4.3}
recovery-cwm-shreps-6.0.4.7-a510-a511.img [870a8e341afc7b0fab7cd665d6772c57]{based on CM11/Android 4.4.2}
recovery-cwm-shreps-6.0.4.5-a510-a511.img [82ad171363dbc897dac4501729ea3209]{based on CM11/Android 4.4.1}
CWM 6.0.1.9 by NoThrills{based on CM10/Android 4.1}
Additional info:
My Github
credits to @pawitp, @NoThrills and CM Team
credits to @Elibl for LVM implementation !
just press thanks
XDA:DevDB Information
CWM Recovery for A510/A511, Tool/Utility for the Acer Iconia A700 and A510
Contributors
Shreps
Version Information
Status: Stable
Created 2014-07-01
Last Updated 2014-10-26
any advise on "remove_recovery_from_rom.zip"
Hi Shreps,
do you advise on any particular "remove_recovery_from_rom.zip", if coming from stock?
Many thanks for your work/help/answer
best regards
m
meikelrix said:
Hi Shreps,
do you advise on any particular "remove_recovery_from_rom.zip", if coming from stock?
Many thanks for your work/help/answer
best regards
m
Click to expand...
Click to collapse
Hi,
yes, it's like all other custom Recovery for A510, if you are on a stock ROM you have to remove the stock recovery by flashing the "remove_recovery_from_rom.zip" script
Shreps said:
Hi,
yes, it's like all other custom Recovery for A510, if you are on a stock ROM you have to remove the stock recovery by flashing the "remove_recovery_from_rom.zip" script
Click to expand...
Click to collapse
Hi Shreps,
thanks for the answer. I was more asking, if there's a preferred "remove_recovery_from_rom.zip" script => if there's only one script, I guess it's the one, that is in the NoThrills thread (CWM-based recovery 6.0.1.9 for the Acer Iconia TAB A510)?
Many thanks for your work and help
best regads
Shreps said:
Download:
recovery-cwm-shreps-6.0.4.7-a510-a511.img [870a8e341afc7b0fab7cd665d6772c57]
recovery-cwm-shreps-6.0.4.5-a510-a511.img [4da9d7f716aeb347336682079697960a]
Click to expand...
Click to collapse
Both downloads doesn`t work ....
Can you fix it pls ?
THX
Working fine for me
Try to use another web browser ?
Shreps said:
Working fine for me
Try to use another web browser ?
Click to expand...
Click to collapse
Very interessting,
I can download everything from your downloadpage except this 2 cwm recovery links.
If i try with "save target as..." it saves only a .htm file.
When i direct click the downloadlink - it will open the .img in the browser. !?!
My browser is latest IE11
Edit: Now downloaded with Opera but 6.0.4.7 MD5 not matching, 6.0.4.5 is ok!
Thanks for the updated recovery. The MD5 on this thread is incorrect. I downloaded the recovery a few times on different devices and each time got the same different MD5 so figured flashing it was safe. It was and I am now on the new recovery.
MD5 should now be fixed
After lots of hair-pulling, I learned that this recovery version can not flash the original Acer images, including the nothrills customized one. Maybe it is not made to work with anything pre-JellyBean?
I was trying to flash back to Acer rom in order to update the bootloader to the JB version and had no luck with this recovery. Kept getting error status 6 and 7.
After I went back to the nothrills recovery (older version), I was able to flash without any issue.
Just a heads up for anyone trying the same.
It was my first time to use Flashify, and wow, that was easy.
Came from NoThrill's 6.0.1.x CWM Recovery. On my stock rooted JB rom (on JB Bootloader too).
Thanks @Shreps!
Updated to 6.0.4.9
Changelog on Github by CM team : https://github.com/CyanogenMod/android_bootable_recovery/commits/cm-11.0
Added the latest version with LVM support !
Please read FP.
oh yeah the crappy recovery of the year.....
it ****s my tablet, entered in eternal loop after flash...
whats this message?
{
"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"
}
unable to reflash the recovery adb says unauthorized.....
grrrrrrrrrrrr! !!!!!!:crying:
harmakhis said:
oh yeah the crappy recovery of the year.....
it ****s my tablet, entered in eternal loop after flash...
whats this message?
unable to reflash the recovery adb says unauthorized.....
grrrrrrrrrrrr! !!!!!!:crying:
Click to expand...
Click to collapse
You have an old update.zip on your sdcard, the recovery try to flash it.
Flashing a recovery is done via Fastboot/Bootloader, not ADB.
Did you read carefully FP ? Did you flash the correct version ?
CWM with LVM is compatible only with ROM with LVM.
yes i dit that as always adb devices for correct usb link and flash after that with fastboot
but now the recovery is on eternal loop and search update.zip i dont have any on sd card
it doesnt show the normal menu as 6.0.4.7 directy tryin' his crappy update.zip
before that tablet always on adb devices connected but now she is offline or unauthorized
Boot in fastboot with hardware key, and you will be able to boot or flash any Recovery you want
Shreps said:
Boot in fastboot with hardware key, and you will be able to boot or flash any Recovery you want
Click to expand...
Click to collapse
hmmmm yeah, and how to do that?
Don't have my tab with me, but try :
Volume- (two dots) and Poweron and then toggle the rotation switch on and off a few times
Shreps said:
Don't have my tab with me, but try :
Volume- (two dots) and Poweron and then toggle the rotation switch on and off a few times
Click to expand...
Click to collapse
tried that and reflash with lvm img but still the same bug
trin' another img
---------- Post added at 03:41 PM ---------- Previous post was at 03:34 PM ----------
hmmmm
erased the recovery still searching the update
erasing of internad sd possible?
formated internal sd no success always searching update.zip no zip anywhere
flashing the 6.0.4.7 its ok
DO NOT FIX ROOT WHEN REBOOT
So I think it's finally stable enough for using. It uses the latest CWM Recovery for Kitkat version and almost every problem like SD Card mounting and touch error has been gone.
For those who don't know what CWM is, you might want to take a look at this site: http://forum.xda-developers.com/wiki/ClockworkMod_Recovery
*DISCLAIMER*
I have no responsible for your bricked device if anything goes wrong!!!
Click to expand...
Click to collapse
NOTE: THIS IS FOR THE LG G PAD 7.0 WIFI ONLY aka V400, not LG G PAD 7.0 LTE.
{
"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"
}
CHANGELOG:
There are many versions before but I will not mention them.
+Latest CWM for Kitkat.
+Swipe supports
+SD Card and SD Ext works now
+ADB sideload also works
Install:
+Make sure you have root access
+Download the image
+Put it in your SD-card
+From your device, go to Play Store and download an app called Flashify
+Open Flashify, in Flash section, choose Recovery image
+In the dialog, press Choose a file
+Navigate to the file you've just put in your SD Card. Confirm by choosing Yup!
+You can choose reboot now to go directly to the Recovery.
Download:
[1]
MD5: c6b863c701ad5a832a17f243d5d8059a
Source: http://github.com/bangprovn
*CREDITS*
TEAM CODEFIRE for BUMP which helps me a lot in signing image.
@hcgonzalezpr for his invalueable help.
If you like my work, don't forget to buy me a beer !
Go back to stock recovery.
It's easy. Instead of using the CWM Recovery, using this https://drive.google.com/file/d/0B3XLPG3BygIrbGNZeG5xVno2Q1E/view?usp=sharing
Follow the instruction above. It will work.
Has this been tested or expected to work safely on v-410 LG pad 7.0?
AT&T S4 i337 > SafeRoot > SafeStrap 3.71 > HyperDrive RLS12
Tasker-ized
@bangprovn
Nice, I will update my sources and publish for the V410.
When doing a backup does it backup to the internal sdcard does it backup to /sdcard/data or /sdcard/data/0/ ?
Also I will try your recovery img on my V410 to see if they are compatible enough to boot the same image.
Update: Same image wont boot, we need custom images for each device.
hcgonzalezpr said:
@bangprovn
Nice, I will update my sources and publish for the V410.
When doing a backup does it backup to the internal sdcard does it backup to /sdcard/data or /sdcard/data/0/ ?
Also I will try your recovery img on my V410 to see if they are compatible enough to boot the same image.
Click to expand...
Click to collapse
SDcard now mounts at folder 0, not data/media anymore, BTW, CM11 for v400 is almost ready, it boots but have some graphic glitches.
bangprovn said:
SDcard now mounts at folder 0, not data/media anymore, BTW, CM11 for v400 is almost ready, it boots but have some graphic glitches.
Click to expand...
Click to collapse
No Destiny game play for me today.
I'm going to have a look at all the difference between my device tree and yours so we can have both V400 and V410 CWM images.
great news!! much thanks..
Ok, tested in my v400 and it works perfectly. Gonna make a backup to try it too. Thanks a lot.
Now I'm waiting for CM
Great news and good work.
Sent from my SPH-L900 using XDA Free mobile app
Also waiting for CM11
Tks
Build this forV700 10.1 WIFI please!? ?
---------- Post added at 01:42 AM ---------- Previous post was at 01:37 AM ----------
schwem said:
Build this forV700 10.1 WIFI please!? ?
Click to expand...
Click to collapse
I will buy you a few beers!
hcgonzalezpr said:
No Destiny game play for me today.
I'm going to have a look at all the difference between my device tree and yours so we can have both V400 and V410 CWM images.
Click to expand...
Click to collapse
Do you have a thread started or will you make a thread when you have a successful CWM for the v410?
Glad someone is getting one going
bangprovn said:
DO NOT FIX ROOT WHEN REBOOT
So I think it's finally stable enough for using. It uses the latest CWM Recovery for Kitkat version and almost every problem like SD Card mounting and touch error has been gone.
For those who don't know what CWM is, you might want to take a look at this site: http://forum.xda-developers.com/wiki/ClockworkMod_Recovery
NOTE: THIS IS FOR THE LG G PAD 7.0 WIFI ONLY aka V400, not LG G PAD 7.0 LTE.
CHANGELOG:
There are many versions before but I will not mention them.
+Latest CWM for Kitkat.
+Swipe supports
+SD Card and SD Ext works now
+ADB sideload also works
Install:
+Make sure you have root access
+Download the image
+Put it in your SD-card
+From your device, go to Play Store and download an app called Flashify
+Open Flashify, in Flash section, choose Recovery image
+In the dialog, press Choose a file
+Navigate to the file you've just put in your SD Card. Confirm by choosing Yup!
+You can choose reboot now to go directly to the Recovery.
Download:
[1]
MD5: c6b863c701ad5a832a17f243d5d8059a
Source: http://github.com/bangprovn
*CREDITS*
TEAM CODEFIRE for BUMP which helps me a lot in signing image.
@hcgonzalezpr for his invalueable help.
If you like my work, don't forget to buy me a beer !
Click to expand...
Click to collapse
Thanks man for you work and time, only wait for cm11 or cm12.
Thanks, it works flawlessly on my v400.
If you make a v700 version I will be happy to help test.
Anyone working on a V410 Lte Ver?
bangprovn said:
DO NOT FIX ROOT WHEN REBOOT
So I think it's finally stable enough for using. It uses the latest CWM Recovery for Kitkat version and almost every problem like SD Card mounting and touch error has been gone.
For those who don't know what CWM is, you might want to take a look at this site: http://forum.xda-developers.com/wiki/ClockworkMod_Recovery
NOTE: THIS IS FOR THE LG G PAD 7.0 WIFI ONLY aka V400, not LG G PAD 7.0 LTE.
CHANGELOG:
There are many versions before but I will not mention them.
+Latest CWM for Kitkat.
+Swipe supports
+SD Card and SD Ext works now
+ADB sideload also works
Install:
+Make sure you have root access
+Download the image
+Put it in your SD-card
+From your device, go to Play Store and download an app called Flashify
+Open Flashify, in Flash section, choose Recovery image
+In the dialog, press Choose a file
+Navigate to the file you've just put in your SD Card. Confirm by choosing Yup!
+You can choose reboot now to go directly to the Recovery.
Download:
[1]
MD5: c6b863c701ad5a832a17f243d5d8059a
Source: http://github.com/bangprovn
*CREDITS*
TEAM CODEFIRE for BUMP which helps me a lot in signing image.
@hcgonzalezpr for his invalueable help.
If you like my work, don't forget to buy me a beer !
Click to expand...
Click to collapse
Sir, I love you work, you can make cm12 rom for v400? Please [emoji122]
v410. LTE. NEEEEEEEDS CM11.
Much good Karma and beer shall come to he who bringeth this. Indeed.
I'll test :good:
Hi, can someone help to do recovery on LG G3s! (D724)
Here are all my data about the phone !!! DEVICE INFO
Please help somebody !!!
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired. Please
* do some research if you have any concerns about features included in this Recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
{
"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"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Changelogs:
What's new in 3.1.1-0:
- Backups will now include adopted storage keys (Dees_Troy)
- Fixed an adb restore issue (bigbiff)
- Fixed rebooting when no OS is present (Dees_Troy)
- Fixed line wrapping in the GUI terminal (_that)
- Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)Updated TWRP source code to AOSP 7.1.2
Screenshots
Credits:
built from source by AMRDev
Downloads:TWRP3.1.1-0_POP3(5015)
Works perfect
Thank you !!!
easy to install - when you eventually remember to allow OEM Unlocks within Developer options (as well as USB debugging obviously)
:good:
I had a few hiccups, ie. it wouldn't wipe the system or data , but I simply converted them to FAT and then straight back to ext4 and it wiped them ready for Custom ROMS
CFKod said:
Thank you !!!
easy to install - when you eventually remember to allow OEM Unlocks within Developer options (as well as USB debugging obviously)
:good:
I had a few hiccups, ie. it wouldn't wipe the system or data , but I simply converted them to FAT and then straight back to ext4 and it wiped them ready for Custom ROMS
Click to expand...
Click to collapse
Great! :highfive:
You're Welcome.
@ZonaRMR How to install this? Because using standard commands gives error. I mean, first "adb reboot bootloader" and then "fastboot flash recovery recovery.img". And second command gives error, something like "download for recovery partition is not allowed". OEM Unlock and Debugging turned on, of course.
Dawidus520 said:
@ZonaRMR How to install this? Because using standard commands gives error. I mean, first "adb reboot bootloader" and then "fastboot flash recovery recovery.img". And second command gives error, something like "download for recovery partition is not allowed". OEM Unlock and Debugging turned on, of course.
Click to expand...
Click to collapse
Flash with SP flashtool using the mt6580 scatter file(I put in the attachment).
for all variants?
first of all i would like to thank you for your effeorts towards this device.you're awesome man :good: secondly i would like to ask if this recovery is for all 5015 variants? i would also like to flash your unofficial CM build for this device (which i know is for all variants) so would you be a legend and give us the stock rom for this device if god forbid anything does go wrong.
bananaman016 said:
first of all i would like to thank you for your effeorts towards this device.you're awesome man :good: secondly i would like to ask if this recovery is for all 5015 variants? i would also like to flash your unofficial CM build for this device (which i know is for all variants) so would you be a legend and give us the stock rom for this device if god forbid anything does go wrong.
Click to expand...
Click to collapse
Yeah it's for all 5015 variants also for 5016.
Hello, congratulations for the project. I need of Rom Original, someone could send me? thank you.
I finally found the ROM STOCK !!!... I just installed and now works !!...but i don't know how can I put file here...
SIMO94307 said:
I finally found the ROM STOCK !!!... I just installed and now works !!...but i don't know how can I put file here...
Click to expand...
Click to collapse
where did you find it?any links please?
Here is the link: https://yadi.sk/d/m6TcJJyTnvZnV
Flash with SP FLASH TOOL !!
A thing to say: Don't worry if it takes a long time...don't touch anything during flash and boot...It'll work !!!:good::victory:
Let me know..
anybody know if this can be used for 5.5 version?
vet90pavle said:
anybody know if this can be used for 5.5 version?
Click to expand...
Click to collapse
Go to my another TWRP recovery thread: http://forum.xda-developers.com/android/development/recovery-twrp-3-0-2-0-alcatel-pop-35-5-t3396816
Nevermind, it works like a champ. Thanks in advance.
Any supersu zip file to flash for this model?
i_am_fresco said:
Nevermind, it works like a champ. Thanks in advance.
Any supersu zip file to flash for this model?
Click to expand...
Click to collapse
Try this https://download.chainfire.eu/696/supersu/
ZonaRMR said:
Try this https://download.chainfire.eu/696/supersu/
Click to expand...
Click to collapse
Thanks for the reply but I alredy tried with that one and the lastest one (2.78) wihtout luck. I have the 5016a. Any suggestion please?
Hi All,
This recovery will work with the 5015A model?
Thanks!
milerx said:
Hi All,
This recovery will work with the 5015A model?
Thanks!
Click to expand...
Click to collapse
It should work.
Sent from my Sony Xperia M4 Aqua using XDA Labs
i'm sorry, but i need your help.
i really don't know what went wrong but now my phone loops into this and im not able to start into fastboot or something else.
michazrael said:
i'm sorry, but i need your help.
i really don't know what went wrong but now my phone loops into this and im not able to start into fastboot or something else.
Click to expand...
Click to collapse
I had the same issue, it ended up that now device is dead (can't even go to fastboot, doesn't turns on). Flashing stock FW should help, but I couldn't find any.
Sent from my Huawei G620S using XDA Labs
{
"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"
}
Code:
*** Disclamer
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
WARNING: The stock boot image has dm-verity, which prevents you from booting if you swipe to enable system modifications!
SOLUTION: Flash a root such as SuperSU or phh-superuser. You can also flash no-verity-opt-encrypt.zip.
Prerequisites :
YOUR BOOTLOADER MUST BE UNLOCKED
How to unlock the bootloader :
1-enable oem unlock in the developer settings
2-reboot to fastboot [adb reboot bootloader] then issue this command [fastboot oem unlock]
note: this will wipe your data]
Click to expand...
Click to collapse
-If you have problems with the device drivers installed , you will need to install lg bridge, you can download it from here:
http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=PWZO7A26B9UW
How to flash Twrp:
BOOT INTO FASTBOOT MODE:
With your phone off, connect your usb cable to your phone while holding VOLUME DOWN to boot into fastboot mode or just type [adb reboot bootloader] in the adb terminal
ONCE YOU ARE IN FASTBOOT MODE:
Open a command prompt and type "fastboot flash recovery <path_to_recovery.img>” without the quotation marks.
Example: fastboot flash recovery C:/Users/John/Desktop/recovery.img
[don't forget to extract the downloaded recovery zip to get the recovery.img]
WHEN THE FLASH COMPLETES: (Takes about 2 seconds)
On your phone, unplug the usb cable and power it off by taking out the battery and putting it back in.
BOOT INTO RECOVERY MODE FOR THE FIRST TIME
HOLD VOLUME DOWN + POWER until you see the LG logo and then temporarily release the POWER button, immediately pressing and holding it back down until you see the white prompt [factory reset] screen. You will NEVER release the volume down button in this process!
Use the hard keys to select "YES" and then "YES" again to boot into TWRP
How to Disable encryption and flash super su [Install Root]:
1. In TWRP, go to Wipe > Format Data. Enter the keyword ‘yes‘, in the provided space and enter. This will wipe the automatically encrypted filesystem, and decrypt it.
2. Once the wiping is done, reboot back into recovery. Go to Reboot > Recovery.
3. When the recovery boots again, connect your phone to the PC and Enable MTP under the Mount section.
4. Transfer the downloaded ‘no-verity-opt-encrypt-**.zip’ and ‘SR1-SuperSU-v2.78-SR1-20160915123031.zip to your internal storage or EXTSD
5. Disconnect the device now.
6. Tap on Install. Now, navigate your phone’s storage and select ‘no-verity-opt-encrypt-**.zip’. Finally swipe the ‘Swipe to confirm Flash’ button on the bottom of the screen.
7. The flashing process will merely take a few seconds. And when it’s done, follow the same method to flash the root package – SR1-SuperSU-v2.78-SR1-20160915123031.zip [/B]
Wait 1 or 2 minutes after the zip files are done flashing then reboot system and PROFIT! Your phone may take 3-5 minutes to boot the first time and it might boot-loop once or twice at the Metro PCS splash screen but don’t worry this is expected.
Click to expand...
Click to collapse
Downloads :
#1
https://www.mediafire.com/download/uxquk880q8pkurl
Additional Downloads :
SuperSU stable by Chainfire
dm-verity and force encryption disabler
Notice: After the TWRP splash screen you will see the option to type in the password to decrypt the filesystem just ignore it and press the cancel button.
Credits :
TeamWin, Me
Please hit the thanks button and conider to donate if you appreciate my work :highfive:
Paypal donation link: https://paypal.me/messi2050
What version of TWRP is this
brad2192 said:
What version of TWRP is this
Click to expand...
Click to collapse
Same as aristo 1
So, you made it from what source?
brad2192 said:
So, you made it from what source?
Click to expand...
Click to collapse
Are you investigating me :laugh: , ported it from my aristo 1 recovery.
messi2050 said:
Are you investigating me :laugh: , ported it from my aristo 1 recovery.
Click to expand...
Click to collapse
Just strange that a TWRP recovery just came out for the same device 2 hours previous to your post.
brad2192 said:
Just strange that a TWRP recovery just came out for the same device 2 hours previous to your post.
Click to expand...
Click to collapse
Ah actually is strange that the one you are talking about came directly after i posted on your topic saying I posted test twrp for aristo 2 on my blog (posted 4 days ago on my blog)
https://forum.xda-developers.com/showpost.php?p=75558782&postcount=16
https://messi2050.blogspot.com.eg
I was not aware of that friend, my apologies.
I'm having an issue, Instagram Twitter and Facebook refuse to update after using magisk, so I switched to SuperSU and I still have the same problem. The only way to get it to work is to remove root. I can't even connect to them through the browser it keeps saying failed to uodate
KyleBryant said:
I'm having an issue, Instagram Twitter and Facebook refuse to update after using magisk, so I switched to SuperSU and I still have the same problem. The only way to get it to work is to remove root. I can't even connect to them through the browser it keeps saying failed to uodate
Click to expand...
Click to collapse
That's probably because of adblock or similar sw
Tried it again no adblock and then google play services kept crashing I couldn't even add my account
Fixed it, forgot I had removed chrome and that was the issue for some reason
when i try to flash twrp i get the response "error can not load" plz. help
ive been having trouble flashing a rom to the aristo 2 because of the buildprop device values being incorrect. how can this be fixed?
messi2050 said:
Same as aristo 1
Click to expand...
Click to collapse
3.0.3.0
Trying this, I get an error "Failed to mount '/data' (No such device)"
tge101 said:
Trying this, I get an error "Failed to mount '/data' (No such device)"
Click to expand...
Click to collapse
Sounds like your partition table is hosed, brother.
Follow this post to restore your phone:
https://forum.xda-developers.com/showpost.php?p=76799751&postcount=91
tecknight said:
Sounds like your partition table is hosed, brother.
Follow this post to restore your phone:
https://forum.xda-developers.com/showpost.php?p=76799751&postcount=91
Click to expand...
Click to collapse
I got it restored eventually but im still having the same issur that made me try a factory reset in the first place. Half the time, i need to reboot for my phone to charge and some of those times the notifications that its charging and that debug is on stay in the status bar. Im at my wits end.
I just grabbed an Aristo 2 and though I don't know how long I'll have it, in my free time ( which is limited ) I'm going to be working on getting a full rom package with kernel compiled. What would you guys like to see? I primarily focus on flagships, and this is definitely a budget device but it's been working well for me despite the snapdragon 425 and only 2gb ram...I'd like to see some development for this thing and though I've only spent about 20 minutes looking around on xda it seems it's very limited (which is to be expected)...Can someone give me a brief rundown on where we are with the device and what yet needs accomplished to be ready for a compile? Are sources available (kernel source, etc)? I thought I read back in another post (messi2050?) that some sources had been obtained? I'm going to go back over it and see what else is needed....do we have defconfig and whatnot to build? Any info you guys can paraphrase will make this all a lot faster since I've got very limited time to research but access to a poweredge r330 blade with 32GB and a 3.4ghz octa to compile on....I've already set up the VM with linux and am waiting to see what else I find that I'm going to need and decide on a build (lineage, cm, stock rooted, etc) before I take the time to download android source....I've only got a 50mbps line coming into the server so a 40gb source download isn't exactly fast and I work construction so I'm in and out but never seem to have EXTENDED periods of time to sit down and burn the keyboard up....
Thanks guys....I'm about to install Tapatalk on the device and I'll be out-n-about checking on jobs in the field but if anyone wants to DM me and bring me up to speed I'll be sure to reply....In the meantime as time allows I can remote the server at the office if need be....
-Rx8driver
I've also noticed that driver issues are pretty noticeable using win10 in fastboot mode...i had to load the Google driver manually to get fastboot mode working... if you're having issues take a close look thru the device manager and make sure the lg driver is properly loaded when the device is in fastboot and download modes if you're running win10...
Sent from my LM-X210(G) using Tapatalk