Related
First of all, this is not my work. I only compiled it.
This is the usual ClockworkMod recovery, compiled from the CM7 sources with additions/modifications by j_r0dd. What I've done is only to compile it for the HTC Desire. For details, check out the link to j_r0dd's original thread for the Nexus S.
The credits go to Koush for the recovery itself and to j_r0dd for the modifications.
j_r0dd said:
This is based on the latest CM7 source which I modified for myself. I take no credit for the recovery whatsoever, but I will take all the blame for my mods . We all know this is Koush's hard work. Just some things were driving me crazy personally. First was the confirmation menu. I really got sick of scrolling through all those "No"s just to flash something, so i changed it for me personally and just thought I would share. I also created a proper wipe menu. I got sick of some wipes in the main menu and the rest in the "advanced" menu. I made this more Amon_RA like. See the attached screenshot for my changes. That change has led to a few others by me. flash with fastboot or flash_image. THESE ARE NOT IN ROM MANAGER. Also if you have an issue with this take it up with me NOT Koush.
Click to expand...
Click to collapse
Original Nexus S thread with changelog here.
Download:
recovery-clockwork-5.0.2.7.111102-j_r0dd_mod-bravo.zip
(old) recovery-clockwork-5.0.2.7.111027-j_r0dd_mod-bravo.zip
Change log:
02-Nov-2011 (v5.0.2.7):
Merged 5.0.2.7 sources from CM7 repo again (some bugfixes)
Added option to wipe cache partition and dalvik cache at the same time
27-Oct-2011 (v5.0.2.7):
Merged 5.0.2.7 sources from CM7 repo (support for internal/external sdcard in backup/restore)
07-Oct-2011 (v5.0.2.6):
Rearranged wipe menu to avoid accidental factory wipes
Added "Reboot Bootloader"
Moved SD Card partitioning into a function of its own for both int/ext SD card
Merged 5.0.2.6 sources from CM7 repo
Added a menu choice of ext2/ext3/ext4 when partitioning SD card
25-Sep-2011 (v5.0.2.3):
Updated to j_r0dd's 5.0.2.3 version. Currently no changes made by myself.
17-Jun-2011 (v4.0.0.5):
Moved the "Wipe data/factory reset" to the bottom of the wipe menu to reduce the risk of accidental factory wipes.
19-Jun-2011 (v4.0.0.5):
Added "Reboot bootloader" option in advanced menu.
Added the ext4 modifications kindly supplied by roalex. Needs testing. Please make a proper nandroid backup with a proven working recovery version before trying this.
20-Jun-2011 (v4.0.0.5):
Added "Show log" in the advanced menu. This can help when reporting errors here. Use it.
21-Jun-2011 (v4.0.0.5.z110621):
Reverted and correctly added roalex's ext4 additions.
Modified recovery.fstab for ext4 support on some devices.
23-Jun-2011 (v4.0.0.5.z110623):
Removed NULL ext3 in recovery.fstab to hopefully get ext4 working properly.
06-Jul-2011 (v4.0.0.5.z110706):
Added "Advanced backup". Now you can backup/restore individual partitions.
Some other commits from other devs in github
Changed file limit from 10000 to 50000 in unyaffs. Should help when restoring large data partitions fails.
17-Jul-2011 (v4.0.1.0.110717):
Rebased completely on j_r0dd's 4.0.1.0 source and removed roalex's ext4 additions, as it wasn't working for everyone. Now trying with the original ext4 support which is included in CWM.
20-Jul-2011 (v4.0.1.4.110720):
Bug fixes
Disclaimer
These recoveries are compiled using the latest commits from koush, j_r0dd and others. That means they haven't been thoroughly tested and might have minor/major issues. I take no responsibility for any damages this thing might cause, but most things should work as intended. If you want something guaranteed to work, I think you should stick with one of the older versions.
Source code available here.
it works... thank you
suiller said:
it works... thank you
Click to expand...
Click to collapse
Superb! I'll change the OP to confirmed then.
bit hesitant to flash this, had a few usb bricks from recent clockworks. reckon some people who have flashed it could nandroid backup then restore and check it all works?
sjknight413 said:
bit hesitant to flash this, had a few usb bricks from recent clockworks. reckon some people who have flashed it could nandroid backup then restore and check it all works?
Click to expand...
Click to collapse
Well, like I said, I can't guarantee that it works, especially since I have no Desire to test it on. I've used j_r0dd's source which is based on Koush's source for the official CM7 3.2.0.0 ClockworkMod recovery. It might work, or it might not work. Testing it is up to each person.
zyonee said:
Well, like I said, I can't guarantee that it works, especially since I have no Desire to test it on. I've used j_r0dd's source which is based on Koush's source for the official CM7 3.2.0.0 ClockworkMod recovery. It might work, or it might not work. Testing it is up to each person.
Click to expand...
Click to collapse
dont get me wrong, i didnt mean any disrespect looks like you have done good work! but i have only had my desire 4 days and already had 2 usb bricks! will probably test in a couple of days
sjknight413 said:
dont get me wrong, i didnt mean any disrespect looks like you have done good work! but i have only had my desire 4 days and already had 2 usb bricks! will probably test in a couple of days
Click to expand...
Click to collapse
Don't worry about it, I wasn't offended in any way. I'm wondering though if the USB bricks are caused by flashed (.img) recoveries. As I remember it, USB bricks were common with the earliest attempts to run recoveries by uploading the recovery binary to the phone's RAM while having to keep it plugged in to the computer.
well i know i got the usb bricks whilst restoring nandroids when my phone wasn't plugged in. that help in any way?
sjknight413 said:
well i know i got the usb bricks whilst restoring nandroids when my phone wasn't plugged in. that help in any way?
Click to expand...
Click to collapse
Maybe your misc partition got overwritten with garbage. In my opinion, nandroid shouldn't touch this partition. The USB brick issue is usually caused by a corrupt misc partition.
Sent from my Nexus S using Tapatalk
yeah i dont really know why it does, its easily fixable by reflashing the mtd0.img file generated from your cid and rom version though, its just a massive nuisance!
sjknight413 said:
yeah i dont really know why it does, its easily fixable by reflashing the mtd0.img file generated from your cid and rom version though, its just a massive nuisance!
Click to expand...
Click to collapse
You should check your nandroid backup folder. If there's a misc.img or something like it, maybe you should move that file elsewhere. That way, nandroid shouldn't overwrite your misc (mtd0) partition. I'm only guessing that it does handle that partition.
Is it wiping sd-ext correctly? "Official" 3.2.0.0 posted here some times ago restarted recovery upon sd-ext wipe.
teorouge said:
Is it wiping sd-ext correctly? "Official" 3.2.0.0 posted here some times ago restarted recovery upon sd-ext wipe.
Click to expand...
Click to collapse
No idea, not using sd-ext in any of my phones.
teorouge said:
Is it wiping sd-ext correctly? "Official" 3.2.0.0 posted here some times ago restarted recovery upon sd-ext wipe.
Click to expand...
Click to collapse
I'd like to know this too. Can anyone who's upgraded to this version of 3.2.0.0 let us know their findings?
Jameswgm said:
I'd like to know this too. Can anyone who's upgraded to this version of 3.2.0.0 let us know their findings?
Click to expand...
Click to collapse
It'll probably behave the same way, seeing as this one only changes the menus, I think.
Updated OP to version 4.0.0.0.
Thanks, please see http://forum.xda-developers.com/showpost.php?p=14598355&postcount=357 .
You should mod 3.1.0.1, no later CWM worked ok.
teorouge said:
Thanks, please see http://forum.xda-developers.com/showpost.php?p=14598355&postcount=357 .
You should mod 3.1.0.1, no later CWM worked ok.
Click to expand...
Click to collapse
Yeah, I got that even on my Nexus S.. I'm just cloning & compiling. Got no idea how to downgrade to an earlier version. Limited programming skills.
I fixed the SD card mounting bug. Please re-download 4.0.0.0.
Still buggy. Each time you leave a file list, you'll need to "adb shell umount /sdcard" from your computer. Looking into it.
Added back the 3.2.0.0 version in the OP so you won't have the /sdcard mounting issue. Hopefully it can be resolved soon, so we can start using the 4.0.0.0 version. Sorry for the inconvenience.
****** USE AT YOUR OWN RISK *******
This is NOT SUPPORTED SOFTWARE. This is purely for my amusement and entertainment. I'm making it available to download for those who might like to examine my work, but if you install it, you are on your own. I can't even test this myself. (I don't have a GT-P6200.)
Seriously - this has not been tested enough for me to be happy with it, and I'm unable to test it myself. Please read the thread for the GT-P6210 for instructions, known issues, warnings, etc.
If you do decide to install this anyway, please let me know how it works out for you. If no one is using it, I WILL NOT MAINTAIN IT AND WILL DROP IT.
If people do start using it, and the reports are that everything is working okay, then it'll get merged into what I'm already doing with the other two 7 plus models (meaning it'll get updated as needed when they do.)
Again, PLEASE READ the thread for the 6210 for everything you need to know: http://forum.xda-developers.com/showthread.php?t=1379532
..and here's a link for a CWM recovery.
Link: http://www.mediafire.com/download.php?do5jkna3dpas1tq
Take care
Gary
Hi! I'm a placeholder.
garyd9 said:
Hi! I'm a placeholder.
Click to expand...
Click to collapse
Hi, Placeholder. I'm a placeholder, too. Good meeting you here.
Pm'ed you. went straight in CWM, looks nice. able to make a full backup and md5. fails to restore in the middle of restoring /data
also getting UDIDs are inconsistent , fixing permission is supposed to take care of this.
and Im pretty much factory reset after reboot.
EDIT: appears as if Location cache map app by remy in market I had set to block wifi and cell caches. restoring a backup in CWM got permissions error, trestoring /data fails and Im left with pretty much a factory reset. went back to market and reinstalled suspicious app, installed and still says caches blocked removed app, rebooted, made back up and successful restore! woo hoo! Thank You Gary!
Note: should we make a note for 7+ CWM users beware blocked location caches, or re-write recovery to take care of this, and/or email the app dev?
anyways, pretty excited. Thanks so much Gary.
Anyone else want to help test the CWM Recovery for this tablet? (GT-P6200 only)
The current tester has had mixed results, but it _may_ have been the result of a third party app causing problems. I'd like to get someone else to test in addition to ensure there aren't any other issues.
In order to test, I need someone who has "adb" installed on their PC, is comfortable with linux commands, already knows how to use adb for commands such as "adb shell, adb push, and adb pull", doesn't mind using ODIN to restore their tablet to a factory state if it soft-bricks, and already knows how to use ODIN and CWM Recovery.
As a side-note; the third party app that MIGHT have been causing the problem is "Location Cache" by "remydemy." I don't use this app myself, but apparently it has some function to block the google/android location caches and it appears to do that by messing with the permissions on the files... which is somehow causing an error when the recovery tries to clean the /data directory in order to restore.
Thanks
Gary
link posted for testing.
thanks again gary loving it.
when I select wipe dalvik cache in CWM options it says dalvik cache wiped awfully fast. and after reboot and removing some bloatware.apks there are still loads of .dex files in /data/dalvik-cache including bloat that i removed.
So i just used root ecplorer to delete entire contents of folder. : )
is this not linked properly or CWM issue, or is this normal function?
thanks so much for your help.
chrisrotolo said:
when I select wipe dalvik cache in CWM options it says dalvik cache wiped awfully fast. and after reboot and removing some bloatware.apks there are still loads of .dex files in /data/dalvik-cache including bloat that i removed.
Click to expand...
Click to collapse
I'll look into it. Please try this alternative to test that function: Boot your phone normally, and then reboot into recovery. Using the recovery menu, mount the /data partition. Then use 'adb shell' to shell into the device and manually look in the /data/dalvik-cache directory. Then "cd /" and from within recovery choose the advanced->wipe dalvik-cache. Then look in /data/dalvik-cache directory again to see if it did what it should have done.
It's possible, based on the ordering of your above description, that the dalvik cache rebuilt after you wiped it (during the reboot) but before you removed your bloatware.
Take care
Gary
thank you. Gary tried not to get Banned OK? we need you buddy. lol
chrisrotolo said:
thank you. Gary tried not to get Banned OK? we need you buddy. lol
Click to expand...
Click to collapse
Where you able to run those tests yet?
thanks
Gary
not as of yet, sometime today though.
---------- Post added at 03:13 PM ---------- Previous post was at 02:23 PM ----------
so yeah, you must be right. dalvik-cache was full with /data mounted. cd / then wiped dalvik from CWM, which finishes in a split second; a list (ls) shows no dalvik-cache folder after wiping, completly gone.
Answers my question.
One other issue I ran into, that you're may be aware of is somehow I disabled the power button in CWM, it said something about back button disabled. I think I had to hold power for 10 sec. to reset device.
Thanks.
chrisrotolo said:
...somehow I disabled the power button in CWM, it said something about back button disabled.
Click to expand...
Click to collapse
That one I'm not sure of and really can't help much with. No 'power' button means you can't select anything which would really be annoying.
it works great! instant root and cwm within 2 minutes! i highly recommend gary's method than the other one. i also don't seem to lose root access by clearing ram memory. SWEET.
Not working:
- format internal sd-card
- update CSC
- installing pre-apps
how to remove CWMRecovery and install stock recovery?
lvsw said:
Not working:
- format internal sd-card
- update CSC
- installing pre-apps
how to remove CWMRecovery and install stock recovery?
Click to expand...
Click to collapse
formatting the internal SDCard isn't going to happen with this version of CWM (that's designed for GB.) Honeycomb devices don't have a seperate /sdcard partition to format. Formatting the "internal sdcard" can be done from within the settings menu via a factory reset.
The other two items aren't broken - they simply don't exist in CWM recovery, and probably never will... Is having the pre-loaded samsgung sample video and music files repushed to your device over and over actually more important to you than the ability to do a nandroid backup? Do you even know what the CSC is that isn't being updated?
Have you bothered to seach around BEFORE installing this? Have you bothered to search around AFTER installing it to find out how to restore to factory?
I'm NOT going to answer your specific question on the basis that it's been answered already and I honestly feel that a user of XDA needs to have the ability to SEARCH before posting.
Take care
Gary
worked like a charm...backup and restore works perfectly...
thanks gary !!!
Hey Gary-
Question -
Is it possible to get ROM manager to recognize the recovery flashed here? I'd like to flash the new version of CWM, which claims to fix the internal SD card problem, but when I install ROM Manager it doesn't recognize that I have CWM flashed.
I could just flash a new recovery from ROM Manager, but I don't want to screw anything up.
Thanks!
Sent from my Galaxy Tab Plus using Tapatalk
jeffcavicchi said:
Is it possible to get ROM manager to recognize the recovery flashed here? I'd like to flash the new version of CWM, which claims to fix the internal SD card problem, but when I install ROM Manager it doesn't recognize that I have CWM flashed.
Click to expand...
Click to collapse
This recovery is CWM Based - it is not an official ROM Manager supported recovery. I have no idea what "internal SD card problem" you are referring to, as I had internal sd card issues resolved with this CWM-based recovery before I posted it (there's only a single version for the P6200.)
I'd actually advise against using the "ROM Manager" program on this device. It's not a supported device, and things can go terribly wrong when messing with recovery and firmware partitions that aren't explicitly supported.
Take care
Gary
garyd9 said:
This recovery is CWM Based - it is not an official ROM Manager supported recovery. I have no idea what "internal SD card problem" you are referring to, as I had internal sd card issues resolved with this CWM-based recovery before I posted it (there's only a single version for the P6200.)
I'd actually advise against using the "ROM Manager" program on this device. It's not a supported device, and things can go terribly wrong when messing with recovery and firmware partitions that aren't explicitly supported.
Take care
Gary
Click to expand...
Click to collapse
Got it - sort of what I figured.
Am I wrong that Recovery still sees the external SD card as an internal SD card? I thought the last time I flashed a zip (boot animation) Recovery showed it as being on the internal card, even though it was actually on the external card. I could be wrong, though - and I don't have the device in front of me to check.
Not a big deal either way - thanks for the response, and your hard work!
*Edit*
Just realized I posted this in the wrong thread like an idiot - I have a P6210. guess that's what happens when you start posting things bc (before coffee).
Hey XDA ! =D
I'm still interested in installing Cyanogenmod 10 on my LG Optimus One P500h, but I want to make sure I follow the steps properly first - this is my first time installing a custom ROM, and when I heard it was possible to install Android 4.0 on the P500h, I performed a backup from ROM Manager, and I "bricked" my device a few days ago. XD
I wouldn't want this to happen again, but at least, I must say I have more experience now, and learned a lesson.
Did many searches on how to install CWM with Cyanogenmod 10, I found many different ways to do it, and I'm still unsure of which procedure follow.
Read the FAQ and that was really helpful.
I will list the procedure that I would normally try - please correct me if I forget anything:
0. Root the device
Done that already. I'm on Android 2.3. When I flashed the KDZ on my LG (and so to my surprise, got me updated from 2.2 to 2.3.3) , I've used V20A_00.KDZ, so I *assume* this is the second baseband.
1. Compact/Trim Cyanogenmod ROM
Downloaded CM10 here. This look correct: http://forum.xda-developers.com/showthread.php?t=1811325
January 8: Build 7/Final
I chose C10 over C11 because more things are compatible I believe - was it Bluetooth that did not worked under C11, but does on C10 ?
Anyways, that solve a known problem: many users said they loose network after the ROM installation. Shinobisoft confirmed it was because of the lack of space on the System partition, right ? Compacting the ROM would also fix problems for installing Link2SD ?
I've downloaded the tool "OOne ROM Editor" and opened it - it doesn't look complicated at all. What apps are safe to delete ? Will converting them to "user app" save space for system apps (I'm not sure - Where are the apps stored when defined as "User"? SD card rather than /System ?) ? Can I delete fonts without problems (I don't see why I can't keep ONLY 3-4 fonts, not 10) ? Then how much space will be left on the device ?
Read I cannot delete LatinIME.apk. Is this the default keyboard? 20MB is huge, there's no way to compact this file, right ?
Assuming there's like 10MB free, network will work, but I will have no choice but to use Link2SD to install apps fully on SD card, is this correct ?
2. Baseband stuff
Ehm, what are we referring to as "baseband" in first place?
All ROMs starting with CM7 are new baseband. If your device had Android 2.2 prior to flashing, you are on old-baseband. There is a patch for that also in the LG Optimus One FAQ on the first page, not sure which post off the top of my head tho. If your device had Android 2.3 on it then you have a new baseband device which shouldn't require any patches.
Click to expand...
Click to collapse
Allright, this should make this a lot easier - as I said, I originally was on Android 2.2, when I bricked the phone, I flashed "V20A_00" throught KDZ Updated, then I rebooted as 2.3.3, so I shouldn't do anything, right ?
In "About Phone", it's listed "Software Version: LG-P500h-v20a".
3. Install ClockworkMod Recovery
This look like the tricky part.
A lot of people on other sites said to use ROM Manager...
shinobisoft said:
First, serious word of advice. Stay away from ROM Manager. It does not handle this device correctly.
Click to expand...
Click to collapse
ROM Manager's way of flashing recovery is broken by design. Do NOT use it unless you are comfortable with rescuing your phone via ADB/fastboot like many people before.
Click to expand...
Click to collapse
Yes, ROM Manager is completely broken in this regard. It needs to download a signed ZIP and discard it and report an error when verification fails. Heck, ZIP format has even its own CRC check. What ROM Manager is doing (download whatever .IMG and flash it no matter what) is a nice WTF! Broken by design, go rewrite from scratch!
Click to expand...
Click to collapse
I don't trust the use of ROM Manager anymore on my device, and I'm not comfortable with using it again. I actually wonder: When I press VolumeUp-Home-Power, the phone perform a factory reset (Many people asked already why. This apparently mean that CWM is not installed).
But is it really installed? ROM Manager actually says: "Actual Recovery: ClockworkMod Recover 5.0.2.0". What? Am I supposed to press VolumeUp-Home-Power to verify, only to do another factory reset?
So what would the non-ROM-Manager method be ? I found this one here:
http://forum.xda-developers.com/showthread.php?t=1146566
I know about the Android Terminal Emulator already, and as a Linux user on PC, the commands "su", "cat", "chmod", "mount" are not unknow to me. I should be able to do this... That's not risky ?
So when CWM will be installed, I should be able to boot in it using "VolumeUp-Home-Power"; in theory, this is a bootloader, so if the ROM get screwed up, I *should* be able to access the bootloader to restore the ROM (I compare this to a PC BIOS - the OS is screwed, but BIOS remain accesible) ?
How could I explain that when I bricked my device with ROM Manager, I couldn't perform a factory reset, and only had access to Emergency Mode (I assume there is not such thing as a "Recovery Mode" on a P500h stock, new/untouched. The equivalent immediatly perform a factory reset) ?
All Android devices have a recovery partition. This is essentially a section of the device’s memory devoted to a very basic recovery system that is separate from the normal operating system. This is normally used by manufacturers for recovering a broken device (as even if the operating system crashes, the recovery image has a chance of still being access and used to reflash the operating system, etc.).
Click to expand...
Click to collapse
By default, the LG P500h recovery partition perform an immediate factory reset - CWM will be installed here, so I should be able to access it if the ROM freak out. But why couldn't I access the factory reset, when I bricked the device? That's what I wonder.
4. Access CWM and do a Nandroid Backup to SD Card
I will now have the files boot, cache, data, recovery and system, as well as"nandroid.md5" on SD card.
5. Wipe everything, clean SD Card
Perform "Wipe data/factory reset". This will format the /data, /cache, /sdext, and .android_secure
Select the "Advanced" option and on the next screen select "Wipe Dalvik Cache". Confirm the wipe.
Not necessary but I do it anyway, in the "Advanced" screen select "Wipe battery stats" and the confirm that wipe
For a clean installation I recommend formatting the system partition too. From CWM home screen select "mounts and storage". On the next screen select "format /system" and then confirm the format.
Press the back button until you are back in the CWM home screen. Select "Install zip from sdcard" and then select "Choose zip from sdcard". Browse your sdcard for the ROM to install and select it. Confirm the installation. Now wait for the install to finish.
Go back to CWM's home screen. Select "reboot system now" option and let the device boot. The initial boot will take a couple of minutes. Don't panic.
Click to expand...
Click to collapse
6. Partition SD card (?)
Is this at that point that I should do it, in CWM ? Or wait until I access Cyanogenmod and use a software on PC to partition ?
Assuming I don't partition, I guess I definitely will lack space for applications (Due to the space of Android 4.0) ?
I will do "Partition SD Card>EXT4 1024MB>Swap:64MB. Is this correct?
7. Install Cyanogenmod
Install ZIP from SD Card, choose the CM ZIP;
8. Install Google Apps
Once the install is done, I won't reboot and immediately install Google Apps, with "Install ZIP from SD card". I chose this package (Working on JellyBean):
http://forum.xda-developers.com/showthread.php?t=1917411
Then I should reboot in CyanogenMod and finally install Link2SD, I believe.
***
..Did I forgot anything ?
I *believe* that makes sense, but this is my first time installing a ROM - I doesn't look *that* hard, I did researches, but things can go wrong... :/
What should I do if I screw things up? Use KDZ Updater again ?
I'm still a little worried about that baseband thing, and the lost network connection.
Thanks for the input, cheers!
1) Use FlashImageGUI app to flash recovery/or use Recovery.IMG flasher by @shinobisoft
2) Forget the baseband stuff
3) Factory reset is the default action when you boot into stock recovery
4) If you partition SD card your data will be wiped anyway
Sent from my GT-I9082 using Tapatalk
akiratoriyama said:
1) Use FlashImageGUI app to flash recovery/or use Recovery.IMG flasher by @shinobisoft
2) Forget the baseband stuff
3) Factory reset is the default action when you boot into stock recovery
4) If you partition SD card your data will be wiped anyway
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
1) I've checked FlashImage GUI, it look really simple to use. This is what I see now:
https://dl.dropboxusercontent.com/u/67605655/snap20140216_103936.png
For flashing a recovery image, should I select Clear Dalvik & Clear Cache ? Do I have to enable USB Debugging?
Where can I find the recovery image for CWM ? Here maybe: http://forum.xda-developers.com/showthread.php?t=1523050
I don't know, I would download CWM v5.0.2.7_Touch_p500-Build 4.zip.
Would the terminal emulator method would be easier (I still need to find recovery.img)?
Code:
$ su
# mount -o remount rw /system
# cat /sdcard/flash_image > /system/xbin/flash_image
# chmod 755 /system/xbin/flash_image
# flash_image recovery /sdcard/recovery.img
# mount -o remount ro /system
# reboot recovery
Since I have no Nandroid backup (I cannot do it until CWM is installed), what could I do if something goes wrong ?
2-3) Excellent, thank you.
4) I plan on partitionning, but at which point shoud I preferably do it?
Thank you, I appreciate the help - sorry for all the newbie questions.
1) Recovery image is in the zip fie itself. Extract it
The terminal method you're telling is just what FlashImage GUI does (notice the word 'GUI' )
2) Partition it whenever you want. Just backup your stuff before doing it.
3) As much I hate to say, the thanks button is there for a reason
Regards,
akiratoriyama.
Sent from my GT-I9082 using Tapatalk
akiratoriyama said:
1) Use FlashImageGUI app to flash recovery/or use Recovery.IMG flasher by @shinobisoft
2) Forget the baseband stuff
3) Factory reset is the default action when you boot into stock recovery
4) If you partition SD card your data will be wiped anyway
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
akiratoriyama said:
1) Recovery image is in the zip fie itself. Extract it
The terminal method you're telling is just what FlashImage GUI does (notice the word 'GUI' )
2) Partition it whenever you want. Just backup your stuff before doing it.
3) As much I hate to say, the thanks button is there for a reason
Regards,
akiratoriyama.
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
Ok, so I've downloaded ClockworkMod_5.0.2.0_Recovery_ThunderG_Official here: http://forum.xda-developers.com/showthread.php?t=1523050
Extracted the ZIP and put the file recovery.img at the root of the SD Card (USB storage); so now all I have to do would be to start FlashImage GUI, select "Recovery Image", browse and choose the file recovery.img, then flash (I won't select Clear Dalvik & Clear Cache unless I have to (It's not selected by default, so I assume it's not require - although I've backed up my stuff already).
It's that simple?
I'm still in a learning stage, I bricked the device once with ROM Manager, so if that work, I should be more confident for the rest (I will take a Nandroid backup). Thanks for all the great explanations - Will press the thanks button soon
(How much thanks can I give per thread?)
GameX2 said:
Ok, so I've downloaded ClockworkMod_5.0.2.0_Recovery_ThunderG_Official here: http://forum.xda-developers.com/showthread.php?t=1523050
Extracted the ZIP and put the file recovery.img at the root of the SD Card (USB storage); so now all I have to do would be to start FlashImage GUI, select "Recovery Image", browse and choose the file recovery.img, then flash (I won't select Clear Dalvik & Clear Cache unless I have to (It's not selected by default, so I assume it's not require - although I've backed up my stuff already).
It's that simple?
I'm still in a learning stage, I bricked the device once with ROM Manager, so if that work, I should be more confident for the rest (I will take a Nandroid backup). Thanks for all the great explanations - Will press the thanks button soon
(How much thanks can I give per thread?)
Click to expand...
Click to collapse
Don't worry you won't brick it.
(Talking from my experience of completely hard bricking aka dead booting my device due to kdz)
Just flash it.
It's that simple
Sent from my GT-I9082 using Tapatalk
akiratoriyama said:
Don't worry you won't brick it.
(Talking from my experience of completely hard bricking aka dead booting my device due to kdz)
Just flash it.
It's that simple
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
Allright, I got it!
I saw the success message, then used the keys to reboot in recovery, that worked!
At the boot, I can read "ClockworkMod Recovery v5.0.2.0 E: Bad boot message "recovery ".
I believe the "E: Bad boot message "recovery " is a known issue, and but is not a problem - please let me know if I have to do anything about this.
So now I will compact the Cyanogenmod ROM (I don't know how much space I should free, but I'll try to free a decent ammount), and perform a Nandroid backup to SD card.
I believe the hardest/scariest is done. From now, if the ROM install fail, I could just restore the backup, I guess.
Are they any case when CWM is unaccessible (When I bricked my device, I had no access to stock recovery (which only perform factory reset) but just Emergency Mode. Why was that?) ?
Thank you, I will let you know about the rest.
(Will press the thanks button at the end I don't know if it's OK to thanks on multiple posts on one thread, on this forum)
EDIT:
That error message means you dont have SD-ext. Ignore it.
Click to expand...
Click to collapse
EDIT 2: Nandroid backup succesfully taken! I now have the files .android_secure.vfat.tar, boot.img, cache.yaffs2.img, data.yaffs2.img, nandroid.md5, recovery.img and system.yaffs2.img. Will backup these on my PC.
It's OK to thanks on multiple post.You just have a limit of 8 thanks per day.
ROM manager made anything inaccessible except emergency mode or fast boot mode for some people.
(When I flashed my Oone with CWM, ROM manager worked like a charm)
You can flash the ROM now
Regards,
akiratoriyama.
Sent from my GT-I9082 using Tapatalk
akiratoriyama said:
Don't worry you won't brick it.
(Talking from my experience of completely hard bricking aka dead booting my device due to kdz)
Just flash it.
It's that simple
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
akiratoriyama said:
It's OK to thanks on multiple post.You just have a limit of 8 thanks per day.
ROM manager made anything inaccessible except emergency mode or fast boot mode for some people.
(When I flashed my Oone with CWM, ROM manager worked like a charm)
You can flash the ROM now
Regards,
akiratoriyama.
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
I appreciate the information;
It's quite akwards that ROM Manager broke everything (And I asked for a BACKUP - that's so broken, it brick the device when you want to BACKUP <__<) - when it rebooted, it was in Fastboot mode, and I never saw that mode before. Tried a few recommended commands without problems, but when I rebooted, I only had access to Emergency Mode.
What would be informative for me to know, is that ROM Manager seems to not only have screwed the ROM, but the stock bootloader as well. Weird.
Shinobisoft said we need to compact the CM10 ROM with his utility first, because the System partition is too small (Otherwise, I will have no network). I will do that, I have the tool, that doesn't look complicated.
From now, I am backing up my SD Card content (DATA is backed up too) with Nandroid present on SD, so I could start formatting, immediately followed by SD partitioning.
I guess I should be fine at that point - if anything goes wrong, I should have the option to restore the Nandroid backup.
Will let you know when I'll have the ROM compacted (Probably today).
EDIT: YAY !
Everything worked as we expected! I saved my SD Card on my computer, wiped it, partition it from CWM (EXT: 1024MB, SWAP: 64MB. I have a 16 Micro SD, class 4 (Can't afford higher class much, for now), then installed the compacted ROM. Immediately after, I installed Gapps, then rebooted.
That worked !! This ROM is DOPE ! Totally worth upgrading ! Blazing fast !! (Will be slower with apps installed, but well)
I also have a working network!
There is one thing that "failed", I cannot get Link2SD to work. It always says "cannot create mount script". I checked with Windows (I know by experience that I should absolutely not edit Unix partitions in Windows, I just check), and the FAT32 partition is the first, then I have a EXT4 partition, then the Linux-Swap, I don't know why it doesn't work.
I used Gparted to format the EXT4 partition to EXT2, but same problem, "cannot create mount script". What am I supposed to do ?
Thanks youuu !! =D
I'm really happy to have done this on my own, with help - I now have more experience with Android, I have experience with Windows, Linux OS and OS X, but never did I tried flashing a ROM yet.
@GameX2
Just woke up to see this post
How much free space is there on your /system partition ?
Link2SD should be working.
Sent from my GT-I9082 using Tapatalk
akiratoriyama said:
@GameX2
Just woke up to see this post
How much free space is there on your /system partition ?
Link2SD should be working.
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
Hi,
Tanks for replying. out of 200mb, I have 70Mb free, but on /data. Last time i checked, /system was almost full (where can i check system size?).
Seems like lot of people have this link2sd issue.
@GameX2 use root explorer, it will tell you the remaining system space
@xu3sno or @ibub can you please help me ?
Sent from my GT-I9082 using Tapatalk
akiratoriyama said:
@GameX2 use root explorer, it will tell you the remaining system space
@xu3sno or @ibub can you please help me ?
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
That's what I've thought, according to "Storage Analyzer", /sysem has as minimum free space of 84KB (!) and a maximum of 4.63 MB.
Did not experience any weird stuff, for now.
sd-ext folder doest exist at root, but it's empty.
GameX2 said:
That's what I've thought, according to "Storage Analyzer", /sysem has as minimum free space of 84KB (!) and a maximum of 4.63 MB.
Did not experience any weird stuff, for now.
sd-ext folder doest exist at root, but it's empty.
Click to expand...
Click to collapse
Link2SD needs at least a MB to create mount scripts.
Delete some system apps like TerminalEmulator, CM File manager, Email, Exchange services.
Also use mini LatinIME.
Sent from my GT-I9082 using Tapatalk
akiratoriyama said:
@GameX2 use root explorer, it will tell you the remaining system space
@xu3sno or @ibub can you please help me ?
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
@akiratoriyama
Yes, that's right. You can check /system space by using Root Explorer. Or go to
Settings>About phone>Partition info.
I got 10+MB space left on /system partiton after trimmed the ROM and installed mini gapps.
You're right, Link2SD only works if there is 3MB, at least, left in system partition.
Sent from my LG-P500 using xda app-developers app
GameX2 said:
That's what I've thought, according to "Storage Analyzer", /sysem has as minimum free space of 84KB (!) and a maximum of 4.63 MB.
Did not experience any weird stuff, for now.
sd-ext folder doest exist at root, but it's empty.
Click to expand...
Click to collapse
Once you have success with link2sd creating mount scripts, you can access at /data/sdext. Been a long time since I ran Jan 8 cm-10, but I seem to recall that partition info is not in settings/about phone. But link2sd will have it. Or there are other apps. When viewing storage info from settings menu, don't confuse internal memory with /system (190mb). Internal that is shown there is/data (200mb).
Sent from my LG-P509 using Tapatalk 2
Link2SD needs at least a MB to create mount scripts.
Delete some system apps like TerminalEmulator, CM File manager, Email, Exchange services.
Also use mini LatinIME.
Click to expand...
Click to collapse
It worked !!
Geez, I went to 170MB of internal MB to 1GB, that's just plain insaneee !
Now I can use my LG P500h for an extra 2 years.
ibub said:
Once you have success with link2sd creating mount scripts, you can access at /data/sdext. Been a long time since I ran Jan 8 cm-10, but I seem to recall that partition info is not in settings/about phone. But link2sd will have it. Or there are other apps. When viewing storage info from settings menu, don't confuse internal memory with /system (190mb). Internal that is shown there is/data (200mb).
Sent from my LG-P509 using Tapatalk 2
Click to expand...
Click to collapse
Thank you! I was confused, because sd-ext2 at root is empty - nice to find it in /data/sdext2.
Suceess !!
Thanks !!
How Do I Install?
GameX2 said:
1) I've checked FlashImage GUI, it look really simple to use. This is what I see now:
https://dl.dropboxusercontent.com/u/67605655/snap20140216_103936.png
For flashing a recovery image, should I select Clear Dalvik & Clear Cache ? Do I have to enable USB Debugging?
Where can I find the recovery image for CWM ? Here maybe: http://forum.xda-developers.com/showthread.php?t=1523050
I don't know, I would download CWM v5.0.2.7_Touch_p500-Build 4.zip.
Would the terminal emulator method would be easier (I still need to find recovery.img)?
Code:
$ su
# mount -o remount rw /system
# cat /sdcard/flash_image > /system/xbin/flash_image
# chmod 755 /system/xbin/flash_image
# flash_image recovery /sdcard/recovery.img
# mount -o remount ro /system
# reboot recovery
Since I have no Nandroid backup (I cannot do it until CWM is installed), what could I do if something goes wrong ?
2-3) Excellent, thank you.
4) I plan on partitionning, but at which point shoud I preferably do it?
Thank you, I appreciate the help - sorry for all the newbie questions.
Click to expand...
Click to collapse
A bit new to installing a recovery and custom ROM on this LG Optimus One (very familiar with Sony phones though), apologies for the newbie-ness. I have all of the files as per this thread, but how do I install the GUI app without a file manager app?
Drachinos said:
A bit new to installing a recovery and custom ROM on this LG Optimus One (very familiar with Sony phones though), apologies for the newbie-ness. I have all of the files as per this thread, but how do I install the GUI app without a file manager app?
Click to expand...
Click to collapse
Install some file manager from play store. In phone settings (not file manager) choose security. Then choose to allow installation from unknown sources. Then open your file manager, scroll to sdcard/downloads/ ,and click on flashimage GUI.apk. Installation process will start.
Sent from my LG-P509 using Tapatalk 2
ibub said:
Install some file manager from play store. In phone settings (not file manager) choose security. Then choose to allow installation from unknown sources. Then open your file manager, scroll to sdcard/downloads/ ,and click on flashimage GUI.apk. Installation process will start.
Sent from my LG-P509 using Tapatalk 2
Click to expand...
Click to collapse
I guess I was thinking too much (or not at all!) Simplicity is the key a lot of times!
I tried all of the points in this thread and now this Optimus One has root, recovery and a new ROM. Thanks everyone! :good:
TWRP 2.8.2.0Team Win Recovery Project 2.x, or twrp2 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.
This is not an official TeamWin TWRP build. I used TWRP sources found HERE, device tree that I created for TWRP that can be found HERE along with many trial and error builds that took just as many hours to get it right...
Changelog:
CHANGELOG for 2.8.2.0:
-Pull in all changes from Android 5.0 lollipop into TWRP
-Add decrypt support for Android 5.0 lollipop encrypted partitions including automatic decrypt when the default_password is in use
-Revert some changes to exFAT that were breaking exFAT support on some devices
-Other minor fixes and updates
Note: At this time we do not have a GUI representation for pattern unlock. You can still decrypt patterns though by translating the pattern dots to numbers. The pattern dots correspond to numbers in the following pattern:
1 2 3
4 5 6
7 8 9
So an upper-case L would translate to a password of 14789 entered on the keyboard. Eventually we plan to add a proper pattern unlock to TWRP but it is a relatively low priority at this point.
More info and changelog can be found on the official TWRP website HERE
Install Instructions:
You will need root which you can find HERE by @autoprime
With custom recovery already installed.
Download
Place zip file on phone
Reboot into recovery
Flash zip file through recovery
Reboot
With stock recovery - Need ADB installed.
Download zip file
Extract recovery.zip to your device's SD Card, not external but internal memory.
Open terminal window/command prompt to execute following commands
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
exit
exit
adb reboot recovery
You should be in your updated recovery now
Download:
Download HERE
Credits:
@Dees_Troy
TeamWin
Everyone involved with TWRP.
2.8.2.0 changelog isn't on TWRPs site or am I blind? Lol.
17akota said:
2.8.2.0 changelog isn't on TWRPs site or am I blind? Lol.
Click to expand...
Click to collapse
I added the changelog, it is not up on their site yet.
TWRP
AndroidUser00110001 said:
I added the changelog, it is not up on their site yet.
Click to expand...
Click to collapse
seems to be working with all my old backups and i can finally move my 12 gigs of backups to external sd , awesome work me and my G3 thank the dev
Haha Good job man!:good:
Works great. Great work. Sucks I just formatted my card to FAT less than 24 hours ago.
Where is the option for exfat formatting?
Sent from my LG-D850 using Tapatalk
Anyone else when backing up or flashing that the bar doesn't feel up and there's a line to the left that fills up?
Sent from my LG-D850 using XDA Free mobile app
Roseysdaddy said:
Where is the option for exfat formatting?
Sent from my LG-D850 using Tapatalk
Click to expand...
Click to collapse
He means that SD Cards formatted to ExFat are supported in recovery now. You can backup and install from an SD Card formatted to ExFat.
So can we keep sd card to fat32 or should we switch back?
Sent from my LG-D850 using XDA Free mobile app
jaybird38 said:
So can we keep sd card to fat32 or should we switch back?
Sent from my LG-D850 using XDA Free mobile app
Click to expand...
Click to collapse
You can keep it formatted to FAT32 but, there is a 4GB file size limit on the FAT32 file system. I would recommend switching to ExFat as it is a faster file system and doesn't have the file size limitations that FAT32 has.
Ok, I guess what I'm asking is, how do I format the SD card to exfat? I can format it to fst32 with twrp but not the other way that I can see.
Sent from my LG-D850 using Tapatalk
-Add decrypt support for Android 5.0 lollipop encrypted partitions including automatic decrypt when the default_password is in use
Click to expand...
Click to collapse
So i know nexus devices are encrypted by default now, but are most lollipop roms (like cm12) encrypted too? also, if we reflash another lollipop rom after decrypting will revert back to being encrypted?
Anyone else's twrp status bar not filling up properly and actually in a line to the left??
Sent from my LG-D850 using XDA Free mobile app
Thank you very much for this.
Confirmed exfat working.
coletague said:
Anyone else's twrp status bar not filling up properly and actually in a line to the left??
Sent from my LG-D850 using XDA Free mobile app
Click to expand...
Click to collapse
I am sure everyone's status bar is doing that
DraginMagik said:
Thank you very much for this.
Confirmed exfat working.
Click to expand...
Click to collapse
You welcome!
Also confirming ExFat working here with SanDisk 64Gb, finally, woot! Many thanks
Sent from my LG-D850 using Tapatalk
For some reason my phone doesn't restart into the system. Gets back to TWRP. Power off, battery pull and power on still gets it back to recovery. Backup restore didn't help.
I flashed recovery with Flashify, created backup, got back into the system. And overnight something happened.
arcticrobot said:
For some reason my phone doesn't restart into the system. Gets back to TWRP. Power off, battery pull and power on still gets it back to recovery. Backup restore didn't help.
I flashed recovery with Flashify, created backup, got back into the system. And overnight something happened.
Click to expand...
Click to collapse
Same here. This morning woke up to find my phone in TWRP recovery and would not boot system. Stuck in a loop that takes it straight to TWRP recovery. I have a feeling a system update did this because one showed up from AT&T that even though I did not install it, must have self-installed overnight and caused this. Ideas?
arcticrobot said:
For some reason my phone doesn't restart into the system. Gets back to TWRP. Power off, battery pull and power on still gets it back to recovery. Backup restore didn't help.
I flashed recovery with Flashify, created backup, got back into the system. And overnight something happened.
Click to expand...
Click to collapse
DraKuL71 said:
Same here. This morning woke up to find my phone in TWRP recovery and would not boot system. Stuck in a loop that takes it straight to TWRP recovery. I have a feeling a system update did this because one showed up from AT&T that even though I did not install it, must have self-installed overnight and caused this. Ideas?
Click to expand...
Click to collapse
Are you guys on stock based ROMs?
[RECOVERY] TWRP 2.8.7.0 - TeamWin Recovery Project
TeamWin is proud to present TWRP v3.0.2.0 for the LG G Pad X 8.0 (V521, V522, V525)
Youtube video: http://www.youtube.com/watch?v=RIvWVS_Rkxo
Full TeamWin credits are on the TWRP page on the TeamWin website: http://teamw.in/project/twrp2
Introduction:
Team Win Recovery Project or twrp for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's 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.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Decryption of /data
Easy selection of internal/external storage
See changelog below for new features
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe cache & dalvik, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/omnirom/android_bootable_recovery
Gerrit for TWRP Official Device Configs - http://gerrit.twrp.me
Gerrit Instance - http://gerrit.omnirom.org
If you have made your own twrp build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
b3 Device Config: https://github.com/Shabbypenguin/android_device_lge_b3
DOWNLOAD:
http://www.t2h-gh0st-is-garbage.xyz/TWRP-V521-3.0.2.0.img
Support:
Only ask for support in the chat for general twrp issues, not device specific problems.
Click http://webchat.freenode.net/?channels=twrp for live support or join us in #twrp on Freenode IRC servers[/QUOTE]
8/21/2016
updated the link, same file name fixed internal storage mount and a few other minor issues
8/20/2016 - initial release
Youll need to use flashify to flash the image after rooting. this should work on all b3 models, aka lg v525, v521 etc
For the test version i had of 2.7.8.0 i had to do this, since i have already done it i cant confirm if you need to on 3.0.2.0 or not. ----- data/internal storage wont mount/work until you go to wipe> format data and format without encryption reboot recovery and then do a factory reset. this will wipe your ENTIRE device but allow you to use twrp normally.
Thanks a lot, i'll flash it soon. Any idea if xposed would work on this device?
shabby is the man
emilyrugburn said:
Thanks a lot, i'll flash it soon. Any idea if xposed would work on this device?
Click to expand...
Click to collapse
I dont use or follow xposed development (my last 3 personal phones werent even rooted) i dont see any reason why it wouldnt we have twrp as well as stock kdz so you can mess things up pretty bad and still recover.
shabbypenguin said:
I dont use or follow xposed development (my last 3 personal phones werent even rooted) i dont see any reason why it wouldnt we have twrp as well as stock kdz so you can mess things up pretty bad and still recover.
Click to expand...
Click to collapse
Xposed looks to work just fine. Thanks again
emilyrugburn said:
Xposed looks to work just fine. Thanks again
Click to expand...
Click to collapse
glad to hear it
i grabbed the tablet as it was a great deal and ive loaded it up with apps for my daughter who is the primary user for it so i wont be doing much with it but its good to see the community finally taking off .
Please add the installation instructions - http://www.xda-developers.com/how-to-install-twrp/
Also, add a 'Donation' segment if you're interested in accepting them
avishah395 said:
Please add the installation instructions - http://www.xda-developers.com/how-to-install-twrp/
Also, add a 'Donation' segment if you're interested in accepting them
Click to expand...
Click to collapse
there is a donate to me button under my name and those instructions dont apply to this device. i specify how to use this in the second post.
IF POSSIBLE, please add your thread to our device ET so we can get a full thread eventually - http://forum.xda-developers.com/t/lg-g-padx
Also, update the version number in the title. I was able to get TWRP working, you do still need to wipe to clear the encryption (it says it does this in red). Then, you can continue using it normally.
avishah395 said:
IF POSSIBLE, please add your thread to our device ET so we can get a full thread eventually - http://forum.xda-developers.com/t/lg-g-padx
Also, update the version number in the title. I was able to get TWRP working, you do still need to wipe to clear the encryption (it says it does this in red). Then, you can continue using it normally.
Click to expand...
Click to collapse
i was on that page and clicked new thread, not sure why it didnt work or how exactly you are supposed to do it as that logically made the most sense to me.
i know you need to wipe to clear the encryption, but i wasnt sure if you needed to clear the encryption in order to use twrp properly as i had already done it on an older version. good catch on the version number
shabbypenguin said:
i was on that page and clicked new thread, not sure why it didnt work or how exactly you are supposed to do it as that logically made the most sense to me.
i know you need to wipe to clear the encryption, but i wasnt sure if you needed to clear the encryption in order to use twrp properly as i had already done it on an older version. good catch on the version number
Click to expand...
Click to collapse
I'm not entirely sure about clearing encryption to use TWRP. I know when I did it, TWRP functioned normally.
Ill ask XDA about the ET, maybe it has a second page that isn't showing.
UPDATE: To add our tag, look for "Edit Tags" (CTRL+F) or use this URL http://forum.xda-developers.com/threadtag.php?t= {add thread id - yours is 3443944}. Our ET/tag is "lg-g-padx"
If it could be made as flashable .dz or .tot, that would be excellent.
mingkee said:
If it could be made as flashable .dz or .tot, that would be excellent.
Click to expand...
Click to collapse
as previously mentioned, only people who have leaked lg tools can make flashable tots etc. i spent hours researching it, testing out different methods and reflashing stock kdz a bunch of times.
the only way i could streamline this is if i submitted this to be made official so once rooted you could use twrp manager, but the submission process isnt exactly one that is a lot of fun to do. especially considering with flashify you only have to do like 3 clicks anyways.
Got something for you, shabbypenguin.
My intitial partitions-being-unmountable-due-to-unknown-error-150 likely because of faulty .tot file. the 1.4GB one works. of course after flashing 10c
Device still reports as LG V510 via MTP. Not a huge deal.
In TWRP file browser, internal storage is mounted as /emmc ?!
SD Card will not mount, log attached. Complete. /external_sd is not /dev/block/mmcblk0p1. It's /dev/block/mmcblk1p1 I manually mounted it there and it works.
Some errors about /sdcard as well. Probably cant mount /data/media/0 there. is my guess.
OTG does not mount properly as well, in recovery it shows up at /dev/block/sda1, recovery's fstab points at /usb-otg?
Was gonna put the output of mount/df from recovery and android but thought that wouldn't help.
eriklion said:
Got something for you, shabbypenguin.
My intitial partitions-being-unmountable-due-to-unknown-error-150 likely because of faulty .tot file. the 1.4GB one works. of course after flashing 10c
Device still reports as LG V510 via MTP. Not a huge deal.
In TWRP file browser, internal storage is mounted as /emmc ?!
SD Card will not mount, log attached. Complete. /external_sd is not /dev/block/mmcblk0p1. It's /dev/block/mmcblk1p1 I manually mounted it there and it works.
Some errors about /sdcard as well. Probably cant mount /data/media/0 there. is my guess.
OTG does not mount properly as well, in recovery it shows up at /dev/block/sda1, recovery's fstab points at /usb-otg?
Was gonna put the output of mount/df from recovery and android but thought that wouldn't help.
Click to expand...
Click to collapse
thanks for the info, my sdcard is provisioned as internal storage so it doesnt show up as a micro sdcard in recovery, not sure how i got it so mixed up but ill push an updated version out later tonight
what do you mean it shows up as emmc?
shabbypenguin said:
thanks for the info, my sdcard is provisioned as internal storage so it doesnt show up as a micro sdcard in recovery, not sure how i got it so mixed up but ill push an updated version out later tonight
what do you mean it shows up as emmc?
Click to expand...
Click to collapse
When you're browsing for things to flash/etc, theres the path/directory /emmc, you enter it and it contains things that are supposed to be in /data/media/0
Confused About Install Instructions
shabbypenguin said:
8/20/2016 - initial release
Youll need to use flashify to flash the image after rooting. this should work on all b3 models, aka lg v525, v521 etc
For the test version i had of 2.7.8.0 i had to do this, since i have already done it i cant confirm if you need to on 3.0.2.0 or not. ----- data/internal storage wont mount/work until you go to wipe> format data and format without encryption reboot recovery and then do a factory reset. this will wipe your ENTIRE device but allow you to use twrp normally.
Click to expand...
Click to collapse
I have flashed TWRP many times in the past on many devices. Yet for the 1st time after using Flashify, it obviously did not install properly as it didn't mount internal storage on this pad. It doesn't even recognize show that there's anything available in internal storage to back up to. Frankly, I don't understand your above instructions on how to property install it.
Typing clear instructions would be greatly appreciated as I can't use it. But do appreciate the time you put into it and will make a donation once this has been fixed.
pressmoon said:
I have flashed TWRP many times in the past on many devices. Yet for the 1st time after using Flashify, it obviously did not install properly as it didn't mount internal storage on this pad. It doesn't even recognize show that there's anything available in internal storage to back up to. Frankly, I don't understand your above instructions on how to property install it.
Typing clear instructions would be greatly appreciated as I can't use it. But do appreciate the time you put into it and will make a donation once this has been fixed.
Click to expand...
Click to collapse
you need to go to wipe > format data. your devices data is by default encrypted and twrp cant decrypt it. once youve wiped data, reboot recovery and then do a factory reset. your device will boot and function as normal and youll have a fully working twrp
eriklion said:
When you're browsing for things to flash/etc, theres the path/directory /emmc, you enter it and it contains things that are supposed to be in /data/media/0
Click to expand...
Click to collapse
ive uplaoded a version taht fixed that, but im unable to mount external_sd or usb otg. sda1 doesnt show up for me in /dev/block and even manually trying to mount sdcard to mccblk1p1 fails due to an invalid arguement, how did you mount yours?