Related
****** 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:
Below are links to full backups that can be restored in TWRP for the H910 after the Dirty Santa exploit. This is useful for restoring a bad install once you have access to TWRP. I will outline three methods for install below that will help in putting back the TWRP backups, a good method for installing it, and a few suggestions I have from restoring my device about 10 times now. So without further ado.
UPDATE: I bricked my device and had to send it off for repair (turns out I can't just flash US996 firmware for funsies) I received my phone back with the still rootable OTA 10L and yesterday I rooted it again and uploaded the new firmware. So if you're an AT&T user who wants the second latest update (10M dropped 04-15 but it isn't rootable as far as I know) then you can grab this and run it along with the stock kernel I made a backup of. I'll update the links below to reflect this. Stock 10L kernel located in tips section. Not flashable, you must extract and install as image and immediately install SuperSU 2.79 or greater or your device won't boot!
How to Install and Restore Stock Images and Boot (Kernel) Image
1.) DOWNLOAD - https://www.androidfilehost.com/?fid=673368273298948069 (Updated to 10L) download the file and verify the MD5sum of the zip matches the file you downloaded. (System image link for devs posted at the bottom)
1a) Download the latest SuperSU 2.79 flashable zip from here: http://www.supersu.com/download
2.) EXTRACT --This is not a flashable zip-- extract the zip file wherever you would like so that it can be copied to the device
3.) COPY - The extracted folder to TWRP > BACKUPS > (paste here) on either the MicroSD card (preferable) or internal storage (This will be wiped when you format data)
4.) REBOOT TO RECOVERY - Once the folders are copied to the backup directory you can reboot to TWRP to begin the restore process.
5.) WIPE - This is getting two sections in order to account for two situations
5a) MICROSD - If you have a MicroSD card and copied the restore files to it wipe everything: Data, Cache, Dalvik/ART, Internal Storage, and System.
5b) INTERNAL STORAGE - If you don't have a MicroSD card installed only wipe the following: Data, Cache, Dalvik/ART, and System.
6.) REBOOT TO RECOVERY - Once you have wiped everything, especially if you wiped internal storage, you should reboot TWRP before you start the restore process
7.) RESTORE - Back in TWRP Choose Restore from the main menu and if you can't see your restore file choose "Select Storage" at the bottom and inside that folder uncheck RECOVERY unless you want to overwrite TWRP (which I recommend against).
7a) I would recommend checking the box "Enable MD5 Verification of Backup Files" which is a little slower but ensures a good restoration
8.) SWIPE - Swipe to begin the operation and it will alert you upon completion. You will need a very large amount of space on your card to do it since the system image is split into 3 packages
9.) ROOT - Do not reboot until you have rooted! The unlocked bootloader will prevent booting on the stock kernel. The stock kernel can be used if it is rooted first, otherwise you will be stuck on the LG Boot logo.
10.) REBOOT TO SYSTEM - The phone will reboot itself! Don't panic, this is part of the standard rooting procedure. Now, see tips at the bottom for best performance.
TIPS!
- This is the 10L update stock kernel made during dirty santa method. This kernel has all features working minus the static on boot being gone, but Wifi calling, comfort view, FM radio, etc are fixed using this kernel. https://www.androidfilehost.com/?fid=817550096634762281 (You must flash SuperSU 2.79 or greater after flashing this kernel before you reboot! Not Flashable, must extract)
- To use the above kernel, download his ROM and extract the boot.img file from that archive. Save it to your device, boot to TWRP, choose Install, Install Image, and click the boot.img file. Then choose the checkbox for "boot" and swipe to flash. Really important to install SuperSU again after installing the custom kernel.
- Boot-up static can be cleared by allowing phone to boot to screen off, placing it face down to turn of second screen, and then flipping it back over. Static will be gone until next boot.
- Using fstrim after wiping in TWRP is good for increasing flash drive performance. Go to TWRP > Advanced > Terminal and type fstrim -v /data/
- You can do fstrim on /system and /cache as well to get all three partitions running clean
- Some of the AT&T apps that you can remove with TiBu are tied to bootup. Be careful what you remove if you like to get past the AT&T logo.
- The button combo to get into TWRP from powered off is Vol Down + Power until the LG Logo appears then let go of power and immediately press power again.
- That button combo boots you to a screen asking it you want to wipe your device. Answering 'yes' to both questions boots you to TWRP.
10L System Image Link for ROM creation (In TWRP emmc format): https://www.androidfilehost.com/?fid=745425885120724506
THANKS!
Google - Because, Android
@me2151 for the unlock and root method (and bricking his phone for us; sorry that happened to your device)
@glitschi667 for the work he did on Dirty Santa with me2151
@jcadduono for getting TWRP ready for us despite not having a V20 at all
@Tilde88 for compiling the kernel sources and creating an excellent ROM for all rooted variants of the device!
@EMSpilot for the debug phone!
@elliwigy for helping everyone troubleshoot and test everything recently
If I forgot you, and believe me a lot of people deserve to be here, let me know and I'll add you
9.) ROOT - Do not reboot until you have rooted! The unlocked bootloader will prevent booting on the stock kernel. The stock kernel can be used if it is rooted first, otherwise you will be stuck on the LG Boot logo. [/QUOTE] What exact method of rooting do you mean, without rebooting? Do you mean just flashing SuperSU? Can you clarify? THANKS for everything! Hoping this gets me out of my semi-brick. No matter what I flash...it keeps reverting back to TWRP.
EDIT: I did this, exactly...and yet again...I'm stuck in the phone autobooting back to TWRP. Any suggestions? Is this bricked?
jreed3786 said:
9.) ROOT - Do not reboot until you have rooted! The unlocked bootloader will prevent booting on the stock kernel. The stock kernel can be used if it is rooted first, otherwise you will be stuck on the LG Boot logo. What exact method of rooting do you mean, without rebooting? Do you mean just flashing SuperSU? Can you clarify? THANKS for everything! Hoping this gets me out of my semi-brick. No matter what I flash...it keeps reverting back to TWRP.
EDIT: I did this, exactly...and yet again...I'm stuck in the phone autobooting back to TWRP. Any suggestions? Is this bricked?
Click to expand...
Click to collapse
If you do a battery pull and can get to TWRP you are not bricked. However, I have no idea what you did to get a bootloop. What kernel did you install: the stock one from TWRP or Tilde88's kernel from his ROM? Either way, if you did this:
Wipe > Restore (Boot and System) > Install SuperSU 2.79 zip > Reboot
then you did the correct steps. The issue of not having SuperSU installed on my device was not booting past the LG logo and never rebooting. However, the method I most recently followed was:
Wipe > Restore (boot and system) > Install Tilde88 kernel > Flash SuperSU > Reboot
and my phone has been running extremely well. I need way more info from you before I can help you further.
AlkaliV2 said:
If you do a battery pull and can get to TWRP you are not bricked. However, I have no idea what you did to get a bootloop. What kernel did you install: the stock one from TWRP or Tilde88's kernel from his ROM? Either way, if you did this:
Wipe > Restore (Boot and System) > Install SuperSU 2.79 zip > Reboot
then you did the correct steps. The issue of not having SuperSU installed on my device was not booting past the LG logo and never rebooting. However, the method I most recently followed was:
Wipe > Restore (boot and system) > Install Tilde88 kernel > Flash SuperSU > Reboot
and my phone has been running extremely well. I need way more info from you before I can help you further.
Click to expand...
Click to collapse
Shoot...I think I followed your instructions in Tilde88's thread....and hit reboot instead of flashing his kernel. I then went back in to TWRP to reflash the entire thing...and the kernel...and I was given crap about encryption. Then, that's when the bootloop started. Right now, I'm sitting on TWRP. I've tried flashing everything, per instructions....but I guess, what I'm asking, is...since I'm on TWRP...and it's bootlooping because of encryption...what would you personally do? Shoot...I'll pay ya if you can fix this! LOL. I just really never dealt with the encryption thing until this phone...never really had problems till now.
---------- Post added at 09:28 AM ---------- Previous post was at 09:12 AM ----------
FLASHED EXACTLY THE WAY YOU DID (WITHOUT THE REBOOTING TO RECOVERY IN THE OP)...NOW, IT GETS TO STATIC, THEN LG SCREEN, REBOOTS ONCE TO STATIC THEN BOOTS UP!!! YAY!!! :good::highfive:
I guess there's no need to REBOOT TO RECOVERY if a person faces encryption issues and is trying to fix their phone. Even after decrypting, I came up with issues. Now let's see if this this asks for my PIN on reboot. THAT was another issue!
IT WORKED!!! THANKS! I'LL now try to go back into TWRP and flash the Tilde's boot.img
So...by flashing your STOCK TWRP backup...per your instructions, I was TOTALLY FIXED...I then didn't even flash Tilde88's kernel...I immediately rebooted back to TWRP, and DID NOT WIPE...but immediately flashed his ROM....and BOOM! Google Now/Always On works flawlessly, zero lag! AWESOME!
So, to all that are having issues with no Google Now/Always On...follow this instructional on this thread and DO NOT wipe after flashing Tilde's rom.
BTW, I shot you a PM, bro! :highfive::good:
jreed3786 said:
So...by flashing your STOCK TWRP backup...per your instructions, I was TOTALLY FIXED...I then didn't even flash Tilde88's kernel...I immediately rebooted back to TWRP, and DID NOT WIPE...but immediately flashed his ROM....and BOOM! Google Now/Always On works flawlessly, zero lag! AWESOME!
So, to all that are having issues with no Google Now/Always On...follow this instructional on this thread and DO NOT wipe after flashing Tilde's rom.
BTW, I shot you a PM, bro! :highfive::good:
Click to expand...
Click to collapse
Nothing like some good news to start the day. I wanted to let you know that the reason this worked is that it is essentially a dirty flash that replaces the stock kernel and adds his ROM tweaks into my stock system. So once it had booted and you flashed over it you were able to keep the stock files needed to get screen off Google Now working while adding his audio tweaks and build.prop because they overwrite the stock files. Since my stock files are odexed and his are not I'm not sure how well all your system files will function since they've been overwritten but if you have no issues then no harm, no foul.
I'm glad this got sorted and to anyone else if you follow this guide and you have any confusion about the instructions just do an @AlkaliV2 and I will do my best to help and I will also fix up the guide so that it is less confusing. Just let me know.
Stuck again....in TWRP.
Delete please
Same issue
i followed it to the letter yet i still keep being returned to team win recovery no matter what i do.
Great step by step instructions. Thanks!
sikiro said:
i followed it to the letter yet i still keep being returned to team win recovery no matter what i do.
Click to expand...
Click to collapse
Try booting into your bootloader (fastboot) and type:
fastboot erase misc
fastboot erase cache
fastboot erase fota
fastboot reboot
See if that helps you at all. Make sure you have a valid ROM flashed correctly though.
im having trouble, i downloaded the file, and i put the extracted folder into TWRP>BACKUPS but when i go to restore on TWRP theres no files to be open, am i supposed to keep the file as a zip or?
prlatorre said:
im having trouble, i downloaded the file, and i put the extracted folder into TWRP>BACKUPS but when i go to restore on TWRP theres no files to be open, am i supposed to keep the file as a zip or?
Click to expand...
Click to collapse
I was having the same issue, do a backup(choose something small) from TWRP. It will create the TWRP>Backups Folder for you and then you can place the extracted zip. from this thread into that folder and it will see it.
ajairola said:
I was having the same issue, do a backup(choose something small) from TWRP. It will create the TWRP>Backups Folder for you and then you can place the extracted zip. from this thread into that folder and it will see it.
Click to expand...
Click to collapse
i've tried what you suggested, and still nothing seems to show up, i made a back up in both internal and micro sd
prlatorre said:
i've tried what you suggested, and still nothing seems to show up, i made a back up in both internal and micro sd
Click to expand...
Click to collapse
So you created a backup of let's say the EFS partition in TWRP. You backed it up once to the internal SD card and once to the external sd card. Then you extracted the zip from step one, placed the folder inside of the backups folder and it does not appear?
how can i use this file if i i'm not rooted? My phone is being weird and i would like to reload the stock software on it.
truwrxtacy said:
how can i use this file if i i'm not rooted? My phone is being weird and i would like to reload the stock software on it.
Click to expand...
Click to collapse
You cant all you can do is factory reset on stock
jerrycoffman45 said:
You cant all you can do is factory reset on stock
Click to expand...
Click to collapse
Does the factory reset to stock also reset the recovery? Want to root phone but will most likely trade in to ATT once I'm eligible for upgrade(with trade in).
Manbot27 said:
Does the factory reset to stock also reset the recovery? Want to root phone but will most likely trade in to ATT once I'm eligible for upgrade(with trade in).
Click to expand...
Click to collapse
right now the root method for the h910 does not allow you to go back to stock
My 8gb sdcard ran out of space during step #8. Can I copy the contents of the sdcard to a bigger card and redo the full restoration from step 1?
---------- Post added at 01:27 PM ---------- Previous post was at 01:06 PM ----------
AlkaliV2 said:
So you created a backup of let's say the EFS partition in TWRP. You backed it up once to the internal SD card and once to the external sd card. Then you extracted the zip from step one, placed the folder inside of the backups folder and it does not appear?
Click to expand...
Click to collapse
Having the same issue. I copied the folder over to the microsd card and the folder I copied over isnt showing up in restore. I cant do anything or wipe anything if I cant see a backup right?
Im going to try and do the internal storage copy. No other choice.
cwis said:
My 8gb sdcard ran out of space during step #8. Can I copy the contents of the sdcard to a bigger card and redo the full restoration from step 1?
---------- Post added at 01:27 PM ---------- Previous post was at 01:06 PM ----------
Having the same issue. I copied the folder over to the microsd card and the folder I copied over isnt showing up in restore. I cant do anything or wipe anything if I cant see a backup right?
Im going to try and do the internal storage copy. No other choice.
Click to expand...
Click to collapse
If you create a backup of anything on the Microsd card before you attempt to put the folder in it, it will create the directories for you and all you have to do is copy and paste at that point.
I was frustrated by the huawei encryption and decided to get rid of it once and for all.
At first I faced many bootloops but i finally figured out what was going on. Formatting user data through TWRP is not enough because after booting the device, encryption is still there. This happens because the kernel encrypts the device when booting up. Simply modifying the boot.img file to remove file encryption also doesn't work because you still boot into an already encrypted stock user data. So the answer was pretty obvious by now.
The trick is to format data using TWRP AND THEN boot to bootloader to flash a modified boot without encryption. So let's get to it.
How to create a modified boot.img without file encryption/dm-verity
1. Find and download your current firmware from Huawei Firmware Finder Dtabase (Team MT), or from a source that you trust. (Using a firmware with different cust version or a different update will most likely not work).
2. Download Huawei Update Extractor and use it to extract the stock boot.img file from UPDATE.APP
3. Download ASSAYYED_KITCHEN.
4. Place your stock boot.img file in the "WORK" folder of ASSAYYED_KITCHEN.
5. Launch ASSAYYED and select the 12th option (KERNEL/RECOVERY MENU) and then the 1st one (Unpacking Kernel).
6. The ASSAYYED options don't work for me so i did it manually. Go to your work folder and open the folder boot_unpacked\ramdisk.
7. You will see a file named "fstab.qcom", open it using WordPad.
8. Find the line:
Code:
/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,inline_data,inline_xattr wait,check,fileencryption
and delete ",fileencryption".It should now look like that:
Code:
/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,inline_data,inline_xattr wait,check
9. (This step is optional,follow it only if you also want dm-verity removed) Use the same method to remove dm-verity.
Code:
/dev/block/bootdevice/by-name/system /system ext4 ro,barrier=1 wait, verify
/dev/block/bootdevice/by-name/vendor /vendor ext4 ro,barrier=1 wait, verify
/dev/block/bootdevice/by-name/product /product ext4 ro,barrier=1 wait, verify
(Just delete the ",verify" part.)
10. Save the file.
11. Launch ASSAYYED and select the 12th option (KERNEL/RECOVERY MENU) and then the 2nd one (Packing Kernel).
12. Follow the instructions below to properly flash your modified boot.img and get rid of encryption.
Removing file encryption/dm-verity from the device
1. Unlock your device.
2. Flash this TWRP on AGS-W09 or the appropriate custom recovery for your device.
3. Boot to TWRP and FORMAT user data (note that it is very important to format data and not just wipe it). •WARNING• this will delete all your data!
4. Go back to the reboot menu of TWRP and select reboot booloader (it's important to not allow your device to boot into system yet).
5. Using fastboot, flash your modified boot.img that you created earlier.
6. Reboot your device (you might get a bootloop on the first boot but force rebooting your device again by holding the power button will fix that).
7. After booting up, your device should not be encrypted anymore.
8. You can now use the root method that you like to root your device and internal storage should be visible on TWRP. TWRP backup should also work normally.
How to fix Magisk modules not showing up on Magisk Manager (! /data/adb/magisk_merge.img mount failed error)
I am not going to get into the technical staff you can find more info here
Edit: As of Magisk 19.0, the following method becomes obsolete. Magisk modules should now work as expected without issues. This method now concerns those who want to stick to an older version of Magisk
1. Download f2fsfix-2018.9.2.zip provided by VR25 on the thread above.
2. Download all the magisk modules that you need to flash and place them on your device.
3. Download the latest Magisk uninstaller along with the latest installer.
4. Boot to TWRP and flash Magisk uninstaller. (If you don't have Magisk already installed, skip this step)
5. Wipe Davlik Cache.
6. Install the latest Magisk.
7. Wipe Davlik Cache.
8. Flash the "f2fsfix-2018.9.2.zip" immediately followed by your modules.
9. Reboot (it should take more than usual).
10. Open Magisk Manager and check your Modules. Hopefully they'll show as installed and function correctly.
Note: This method should also work on similar devices. Just make sure you know how to recover your device in case something goes wrong.
I can confirm this worked for me. I was able to run a full nandroid, but haven't tried to restore. Wasn't running any magisk modules, so haven't tried that part of the guide. Flashed Xposed in TRWP and installed greenify, etc Seems to be working. So far no errors. Be warned, this is like a restore. You'll be starting from scratch again.
Also thanks for the boot image trick Thanostsak. I couldn't find stock fimware for my version (AGS-L03) anywhere. He suggested to use the Magisk's boot image backup. Worked like a charm. Still looking for AGS-L03 stock if anyone has one, knows where to get one please post!
TRS_80 said:
I can confirm this worked for me. I was able to run a full nandroid, but haven't tried to restore. Wasn't running any magisk modules, so haven't tried that part of the guide. Flashed Xposed in TRWP and installed greenify, etc Seems to be working. So far no errors. Be warned, this is like a restore. You'll be starting from scratch again.
Also thanks for the boot image trick Thanostsak. I couldn't find stock fimware for my version (AGS-L03) anywhere. He suggested to use the Magisk's boot image backup. Worked like a charm. Still looking for AGS-L03 stock if anyone has one, knows where to get one please post!
Click to expand...
Click to collapse
Glad it worked for you. Yes this is the downside. The device already comes with an encrypted userdata, so it needs to be formatted. So anything you do before that becomes obsolete. That's why this procedure is much more convenient when it happens after the unlock,when the userdata is wiped by the stock recovery to get a stock condition.
AGS-L09 LTE
I just followed your detailed guide to my tablet and finished all the processes perfectly.
Working..Twrp, Magisk, removed encryption & verify from boot.img and from Data successfully.
A big THANKS for your guide, links and trick all in one post!!!!.
Thanks for the info.
I am new to android (but have jailbroken iOS for years).
I have received a Huawei MediaPad T3 AGS-W09 (AGS-W09C100B278) today.
I have managed to unlock and install TWRP 3.2.1 but also want to install SuperSU, but of course the filesystem is encrypted, which brings me here.
I have searched all over for Huawei MediaPad T3 AGS-W09 (AGS-W09C100B278) firmware which contains boot.img but cannot find it. Even the rom on the AGS-W09 thread on this forum doesnt contain the .img file. Am I missing something ?
Any help is appreciated.
Thanks again
mr_fingy said:
Thanks for the info.
I am new to android (but have jailbroken iOS for years).
I have received a Huawei MediaPad T3 AGS-W09 (AGS-W09C100B278) today.
I have managed to unlock and install TWRP 3.2.1 but also want to install SuperSU, but of course the filesystem is encrypted, which brings me here.
I have searched all over for Huawei MediaPad T3 AGS-W09 (AGS-W09C100B278) firmware which contains boot.img but cannot find it. Even the rom on the AGS-W09 thread on this forum doesnt contain the .img file. Am I missing something ?
Any help is appreciated.
Thanks again
Click to expand...
Click to collapse
I strongly suggest using Magisk to root your device instead of SuperSU. The good thing about Magisk is that everything happens systemlessly, so it doesn't matter if the kernel is encrypted in order of it to work. If you still want to use SuperSU though, my guide should provide all the info you need.
To answer your question you can find two OTA firmware updates for your device here. If that doesn't work (if the OTA updates don't include the boot.img file ) i will let you know how to use magisk to get a copy of your current boot.img
Thanostsak said:
I strongly suggest using Magisk to root your device instead of SuperSU. The good thing about Magisk is that everything happens systemlessly, so it doesn't matter if the kernel is encrypted in order of it to work. If you still want to use SuperSU though, my guide should provide all the info you need.
To answer your question you can find two OTA firmware updates for your device . If that doesn't work (if the OTA updates don't include the boot.img file ) i will let you know how to use magisk to get a copy of your current boot.img
Click to expand...
Click to collapse
Thanks for the info.
I have been looking down the Magisk avenue too.
My plan is, decrypt is then root it.
I did download those firmware files earlier but as you say, no .img files.
I have tried to follow a guide on youtube from rootjunky but got as far as running the info gathering piece to gather mount points, but it fell over. Don;t know if thats because I was using adb sideloading via TWRP .. ?
I attempted to run the commands from the batch file direct but no joy.
It would be really appreciated if you could point me to a guide to extract the img. It's my day 1 of this device and Android (already voided warranty from Amazon within 1 hour ha) but as I say, I have experience in most of what is needed from my iOS jailbreaking and bringing phones back from bootloops and the brink of bricks.
When you mention rooting with Magisk .. Can that be achieved in the state my device is in now, which is TWRP'd but encrypted ?
I also notice the "Ultimate Backup Tool, No Root Required" thread (cant put URL's yet as I'm a n00b member). Could that export my boot.img ?
I am done for today. I am working from home and it the device got delivered at 9:30 ish. I was hacking around with it all day and did about 20 min work. I'm fried now :-O
Thanks again
mr_fingy said:
Thanks for the info.
I have been looking down the Magisk avenue too.
My plan is, decrypt is then root it.
I did download those firmware files earlier but as you say, no .img files.
I have tried to follow a guide on youtube from rootjunky but got as far as running the info gathering piece to gather mount points, but it fell over. Don;t know if thats because I was using adb sideloading via TWRP .. ?
I attempted to run the commands from the batch file direct but no joy.
It would be really appreciated if you could point me to a guide to extract the img. It's my day 1 of this device and Android (already voided warranty from Amazon within 1 hour ha) but as I say, I have experience in most of what is needed from my iOS jailbreaking and bringing phones back from bootloops and the brink of bricks.
When you mention rooting with Magisk .. Can that be achieved in the state my device is in now, which is TWRP'd but encrypted ?
I also notice the "Ultimate Backup Tool, No Root Required" thread (cant put URL's yet as I'm a n00b member). Could that export my boot.img ?
I am done for today. I am working from home and it the device got delivered at 9:30 ish. I was hacking around with it all day and did about 20 min work. I'm fried now :-O
Thanks again
Click to expand...
Click to collapse
I get what you are saying. Going from iOS to android is a big step. Since the firmware files don't contain the boot.img and having in mind that you want to decrypt, getting a boot.img file is a must.
There are ways to get the boot.img without root but the ones i tried don't work. But there is an easy way that i know of that requires installing Magisk. When you flash Magisk from TWRP it roots your device. However, apart from rooting it also creates a backup of your boot.img in case something goes wrong.
Decrypting requires formatting your device, so Magisk will be removed too. So its only purpose for now is to provide you with a boot.img file.
Here is what you need to do
1. Download the latest magisk installer from the magisk threat
2. Save the file in your SD card (internal storage is encrypted)
3. Flash the Magisk installer from TWRP
4. Boot your device and navigate to /data
5. There should be a stock boot_xxx.img.gs file in there. Copy it to your storage, move it to a computer and extract it. You should get a boot.img file that you could use to decrypt.
6. Follow my guide to decrypt the boot.img and then flash it from bootloader
7. Since your device is now formatted from the decryption, you can choose the root method that you like.
Thanostsak said:
I get what you are saying. Going from iOS to android is a big step. Since the firmware files don't contain the boot.img and having in mind that you want to decrypt, getting a boot.img file is a must.
There are ways to get the boot.img without root but the ones i tried don't work. But there is an easy way that i know of that requires installing Magisk. When you flash Magisk from TWRP it roots your device. However, apart from rooting it also creates a backup of your boot.img in case something goes wrong.
Decrypting requires formatting your device, so Magisk will be removed too. So its only purpose for now is to provide you with a boot.img file.
Here is what you need to do
1. Download the latest magisk installer from the magisk threat
2. Save the file in your SD card (internal storage is encrypted)
3. Flash the Magisk installer from TWRP
4. Boot your device and navigate to /data
5. There should be a stock boot_xxx.img.gs file in there. Copy it to your storage, move it to a computer and extract it. You should get a boot.img file that you could use to decrypt.
6. Follow my guide to decrypt the boot.img and then flash it from bootloader
7. Since your device is now formatted from the decryption, you can choose the root method that you like.
Click to expand...
Click to collapse
Makes total sense. I just installed Magisk now from SD, thing is, the only spare SD I had was 128MB !! So I dont know if the .img was saved correctly. I will look into it tomorrow. My other large SD is corrupted but I have a 32GB one in the dashcam I will use tomorrow.
That leads me to a question. Is the auto created .img saved on the card or the internal storage ? I am assuming its card but I could not see it.
Will look more tomorrow.
Thanks
mr_fingy said:
Makes total sense. I just installed Magisk now from SD, thing is, the only spare SD I had was 128MB !! So I dont know if the .img was saved correctly. I will look into it tomorrow. My other large SD is corrupted but I have a 32GB one in the dashcam I will use tomorrow.
That leads me to a question. Is the auto created .img saved on the card or the internal storage ? I am assuming its card but I could not see it.
Will look more tomorrow.
Thanks
Click to expand...
Click to collapse
It is actually on the internal storage. Now that you are rooted you can use a root file explorer to get it. (128mb should be enough for this task)
Thanostsak said:
It is actually on the internal storage. Now that you are rooted you can use a root file explorer to get it. (128mb should be enough for this task)
Click to expand...
Click to collapse
On it now before work
Extracted stock_boot_(IDremoved).img.gz which contains the img
Will run your guide against this img
---------- Post added at 09:20 AM ---------- Previous post was at 08:33 AM ----------
All done. Nice and easy
No issues other than sweaty palms on Huawei long boot screen after flash :silly:
No reboot loop and no Magisk errors
Much appreciated for the help
Correction,
Magisk is giving the the errors when installing modules.
Followed your guide and all good
mr_fingy said:
Correction,
Magisk is giving the the errors when installing modules.
Followed your guide and all good
Click to expand...
Click to collapse
Great! If you need anything feel free to ask.
Well... I followed your steps to remove force encryption and install Magisk, everything seems to be perfect. The Magisk and modules are funtional. However after reboot all modules are dispeared, but magisk is still recognized by magisk manager. I don't know where is the problem...
Model: AGS-W09
f2sffix version: 2018.10.9
magisk version: 17.2 (At first I used the latest 18.0 version, but after this problem appeared, I noticed that f2sffix-20181009 only support magisk version 17.2 or older, so I retry your method with magisk 17.2, but the problem remains.)
TimYuan said:
Well... I followed your steps to remove force encryption and install Magisk, everything seems to be perfect. The Magisk and modules are funtional. However after reboot all modules are dispeared, but magisk is still recognized by magisk manager. I don't know where is the problem...
Model: AGS-W09
f2sffix version: 2018.10.9
magisk version: 17.2 (At first I used the latest 18.0 version, but after this problem appeared, I noticed that f2sffix-20181009 only support magisk version 17.2 or older, so I retry your method with magisk 17.2, but the problem remains.)
Click to expand...
Click to collapse
You should use the latest version of f2sffix (10.9) and then follow the procedure again. After your first boot follow VR25's recommendation and you should be good to go.
VR25 said:
Those getting everything broken after a second reboot, try the following workaround...
After the first reboot (right after installing), remove </sbin/.core/img/f2fs*bla*bla/service.sh>, </data/adb/magisk_merge.img> and </cache/magisk_merge_.img>.
Note that after doing this, you'll only be able to install modules and update Magisk from TWRP.
Click to expand...
Click to collapse
Thanostsak said:
You should use the latest version of f2sffix (10.9) and then follow the procedure again. After your first boot follow VR25's recommendation and you should be good to go.
Click to expand...
Click to collapse
It works!!! You are my hero!
TimYuan said:
It works!!! You are my hero!
Click to expand...
Click to collapse
Glad it worked for you.
Kudos to VR25 for making this amazing module even though he is not personally benefited by it.
Thanostsak said:
Glad it worked for you.
Kudos to VR25 for making this amazing module even though he is not personally benefited by it.
Click to expand...
Click to collapse
what if there is no fstab.qcom in kernel but stored in vendor/etc partition?
i've already edited the fstab, but still my system partition become ro (read only) when i made a change in system. all file manager error even previously has root.
please take a look at attachment . thanks in advance
an-_-dro said:
what if there is no fstab.qcom in kernel but stored in vendor/etc partition?
i've already edited the fstab, but still my system partition become ro (read only) when i made a change in system. all file manager error even previously has root.
please take a look at attachment . thanks in advance
Click to expand...
Click to collapse
I believe that what you are missing is after changing forceencrypt=footer into encryptable=footer you should also do a full data format through TWRP.
Thanostsak said:
I believe that what you are missing is after changing forceencrypt=footer into encryptable=footer you should also do a full data format through TWRP.
Click to expand...
Click to collapse
encryption is not a problem. since the first place already done with that data partition.
my problem is system partition, every time i made a change to system (for example deleting chrome.apk), something triggered that makes my system weird (magisk forceclose, all file manager become malfunction because system become read only). something lock my system partition if system change.
i thought change fstab.qcom <mnt_flags and options> ro,errors=panic to >> errors=continue (deleting ro/read only) will change my system behaviour, but it's not
So ive searched for an answer to this but couldnt find it with google/xda.
I tried to install a custom rom.
My first rom install attempt ever on android
It failed with a signal 11 error
So after lots of trouble shooting trying any "fix" I could find suggested.
I read wiping before a rom install was required.
So I made a twrp backup, placed it on my pc, this is where I messed up and nobody in the countless threads I read said
I deleted the twrp backup on device
Then wiped with twrp, following the era proper directions for device allegedly.
Which was wipe everything but internal storage, also read to format in the many topics I perused.
Then found everything was wiped, including /sdcard, and system/OS
WELL I STILL GOT SIGNAL 11 on rom flash attempt via sideload, since the zip got erased on sd.
I did manage to flash a rom, but wouldnt you know it, its a rom that cant connect to pc through usb.
If I try to push the twrp backup folder, it just says error in cmd while in sideload
Anybody know the proper way to do that? Or is it just a case of murphys law getting a right good laugh at my devices expense.
I did read I could use a micro usb to external storage to mount, but I lack that.
I need to restore twrp because I think I need to pull the vendor directory off device to try to overcome the signal 11 error.
Anyway any advice is appreciated and hopefully can serve others in the future.
Thanks and cheers
Re-flash Stock ROM.
Well I dont think the device in question has a stock rom. Or I cant find one at first glance.
I had to roll back the version to unlock bootloader and root.
But that .bin wouldnt help I think.. hmm
Back to the drawing board I guess.
Perks of a decade old device.
Apparently androidmtk.com has stock roms available, but is that site safe to use?
Sorry for my noobiness.
Edit: actually that bin is the stock firmware apparently. I hope at least.
Will try and report back.
Thanks jwoegerbauer
Edit2: that worked flashing the bin. Was able to mount on pc and add the backup back up.
Did have a stumble as without making a backup there wasnt a backups folder. I tried to manually create one, but twrp couldnt see the folder I made.
Not sure if it was the naming. I tried "Backups" but twrp created "BACKUPS"
I just backed up efs since it was smallest to get twrp to make it.
Cool. Now I can backup vendor for rom comparison. Was overstressed for half the day about it, but the solution was simple and right there in front of me.
Thanks again Jwoegerbauer
what do you mean "it's a rom that can't connect to pc through usb"?
what do you mean "was able to mount on pc"?
you have backup of old ROM on pc. what do you want to do with?
No worries alecxs
Yeah I was able to sideload a custom rom but that rom had broken/missing usb drivers so mtp on pc failed.
That was before I knew I had the stock rom.
I needed stock rom to be able to restore with twrp in order to pull vendor folder off original device.
(I need vendor folder to try to fix that broken custom rom)
Just me being a noob. Sorry again.
you're welcome. just asking for clarity.
you have answered one question, so let me give you hint on guesswork.
you can connect device with usb-debugging from developer options. adb is the recommended way to transfer files. MTP is a faulty implemented Microsoft protocol I wouldn't use for large amount of data (for small files is okay).
Android devices cannot mounted since Android 5.0.1 Lollipop as UMS has been dropped in favour of MTP. /sdcard is no longer separate FAT partition but emulated storage in /data/media.
Bear in mind TWRP backup does not include /data/media so one have to backup pictures manually. this can be done from adb.
Code:
adb pull -a /sdcard
For the same reason you will lose /sdcard every time you format /data.
If you're interested to restore backup to different ROM, you cannot use TWRP. backup of /data can only restored to the exact same ROM.
For restoring backup to different ROM use Migrate.
[APP][ROOT][5.0+][1st Nov 2020] Migrate - custom ROM migration tool
Jumping from one custom ROM to another can be a challenging task. So I decided to make an app to simplify the process. Introducing Migrate! Migrate-GPE (v4.0) is on Google Play It was temporarily suspended. Read more here...
forum.xda-developers.com