Related
This is a simplified guide for those new to rooting & flashing a custom ROM on the Optimus V. No need to type complex commands that are hard to follow and prone to mistakes. Basically there are 3 main steps: Root, Install custom recovery, & flash custom ROM.
Windows Drivers for the Optimus V (Optional but suggested):
http://www.lg-phones.org/wp-content/uploads/LG-Optimus-V.zip
Rooting
Rooting is the process of gaining administrative rights to the phone so one can do customizations that aren't normally allowed. Root by itself doesn't do anything interesting, unless there's an app that needs it. The fancy stuff comes from custom ROMs. Just remember Virgin Mobile Activation only works on Froyo ROMs, so do it before going to Gingerbread. The easiest way to root nowadays is to use GingerBreak. It can be found here:
[26.04.2011][v1.2] GingerBreak APK (root for GingerBread) - xda-developers
Instruction Steps:
1. Turn on USB Debugging (Settings - Applications - Development)
2. Copy the GingerBreak.apk to a /sdcard dir, then using a 'file manager' app (search for one in Android Market) install it like a regular app.
3. It can take up to 10 minutes, and will reboot automatically when complete (rooted), if attempt fails, reboot manually & run it again.
Install custom recovery image
The recovery image is an alternative bootup instead of normal Android Operating System. It allows low-level operations such as backup/restore a ROM, wipe partitions, and flash ROMs.
4. Download and copy the recovery image VM670NH_recovery.img (works with new & old OV screens) onto your /sdcard.
5. Install the Flash Image GUI app (save the .apk to a /sdcard directory, then open it with file manager) Run the app & select 'Recovery Image' option with the file above.
Flash Custom ROM
I.H.O CyanogenMod 7 ROM (Gingerbread)
6. Copy the unextracted ROM .zip that you wish to install to the /sdcard dir. Also if installing a CyanogenMod Gingerbread ROM, the unextracted gapps.zip also needs to be placed in the same dir to flash right after the ROM .zip.
7. Boot into Clockworkmod recovery mode (From powered off state, hold vol-down, home, and power button until the LG logo appears).
8. FIRST, BACKUP ORIGINAL ROM! Don't continue until this is successful. Use vol-up/down, camera, & back keys to navigate in recovery.
9. Wipe Data/Factory Reset, wipe cache partition. Under Advanced submenu, wipe dalvik-cache. Then uner Mounts & Storage submenu, format all partitions EXCEPT /sdcard.
10. Flash the custom ROM.zip from sdcard and gapps.zip too if going to a CyanogenMod ROM
11. Reboot and enjoy the new ROM, the first boot takes longer than usual, also some problems may disappear after rebooting.
NOTES:
- NEVER use Android Settings 'Factory Reset' from now on, only do factory reset & wipes from within recovery mode. Most ROMs should have this option removed from the Android settings.
- Some newer Optimus V screens hardware changed, see link: [FIX]Black screen with custom recovery and custom roms (BobZHome's IHO recovery from the Wiki binary -> recovery page also works with newer screens.)
- If restoring a backed up ROM in CWM recovery gives 'MD5 mismatch' error (likely caused by renaming a ROM backup). Try this fix:
# cd /sdcard/clockworkmod/backup/<name_of_backup>
# rm nandroid.md5
# md5sum *img > nandroid.md5
- If you ever want to restore to original stock ROM (ONLY on OV's with older screen), with original recovery and UNrooted:
http://www.prepaidandroid.org/index...e_your_Optimus_V_to_almost_original_condition
titanium backup?
Excellent guide for the likes of me (noob), you might wanna mention titanium backup too
help
Hey u have a great step by step guide, however when I run gingerbreak to root it gives me an error I kno u said reboot manually and I did twice and I couldn't get it to work, any thoughts of to why it did this twice thanks
Zachary droid said:
Hey u have a great step by step guide, however when I run gingerbreak to root it gives me an error I kno u said reboot manually and I did twice and I couldn't get it to work, any thoughts of to why it did this twice thanks
Click to expand...
Click to collapse
What is the exact error you're getting? I believe you have to keep retrying, maybe up to 10 times.
Thanks a lot.Real helpful
Will this work for LG Optimus S? It's been difficult to find specific information for this phone.
Thanks.
KidGusto said:
Will this work for LG Optimus S? It's been difficult to find specific information for this phone.
Thanks.
Click to expand...
Click to collapse
the windows drivers and gingerbreak will work.
you'll need an optimus S custom recovery and rom, though. If you use optimus V software, your home and menu keys will be backwards, and there may be other little issues with the network.
look on android central forums for optimus S development and you'll find roms and recoveries no problem.
Thank you for this. The Rom manager method is great, i was afraid not to brick my optimus one with the adb shell crap and pc connection. They should make a nici sticky like this in the euro section, not with adb crap.
Can this guide by updated, with more details?
The menu options in ROM manager are not the same anymore, and I am flailing around trying to figure out which options to hit.
I'm stuck at the LG logo boot up screen after doing what I think is flashing the bumblebee ROM step. (step 10 in the guide).
I used these steps and they worked great for rooting, but I'm having a problem with recovery. I flashed CWM 3.2.0.1 from ROM Manager and it appeared to work fine, but when I try to boot into recovery I just get a blank screen.
I have done the following:
Busybox 1.19.2 from Stericson, installed to /system/bin
Superuser from market, updated to 2.3.6.3, su is 2.3.2-efgh
Used ROM Manager 4.4.0.7 to flash CWM recovery 3.2.0.1
I've tried getting to recovery using Home+Vol Dn+Power, or the reboot menu option in rom manager, and just get the blank screen.
Anyone run into this or have suggestions?
cobraextreme said:
I used these steps and they worked great for rooting, but I'm having a problem with recovery. I flashed CWM 3.2.0.1 from ROM Manager and it appeared to work fine, but when I try to boot into recovery I just get a blank screen.
I have done the following:
Busybox 1.19.2 from Stericson, installed to /system/bin
Superuser from market, updated to 2.3.6.3, su is 2.3.2-efgh
Used ROM Manager 4.4.0.7 to flash CWM recovery 3.2.0.1
I've tried getting to recovery using Home+Vol Dn+Power, or the reboot menu option in rom manager, and just get the blank screen.
Anyone run into this or have suggestions?
Click to expand...
Click to collapse
[fix]black screen in custom recovery or custom roms
you probably have the newer screen type, which it appears the older custom kernels need a .config setting changed before building to support.
you'll have to use flash_image in adb or terminal.
probably. full instructions and downloads at that link.
yay, you didn't flash a rom through rom manager at the same time! or it'd be a lot harder.
bigsupersquid said:
[fix]black screen in custom recovery or custom roms
you probably have the newer screen type, which it appears the older custom kernels need a .config setting changed before building to support.
you'll have to use flash_image in adb or terminal.
probably. full instructions and downloads at that link.
yay, you didn't flash a rom through rom manager at the same time! or it'd be a lot harder.
Click to expand...
Click to collapse
That did the trick! Thanks!
It would be great to get a sticky about this in here. It's pretty easy to miss the newer display issue if you're just now looking into this forum and don't check AC first.
cobraextreme said:
That did the trick! Thanks!
It would be great to get a sticky about this in here. It's pretty easy to miss the newer display issue if you're just now looking into this forum and don't check AC first.
Click to expand...
Click to collapse
Updated original post with link for the new OV screens.
lamenramen said:
Can this guide by updated, with more details?
The menu options in ROM manager are not the same anymore, and I am flailing around trying to figure out which options to hit.
I'm stuck at the LG logo boot up screen after doing what I think is flashing the bumblebee ROM step. (step 10 in the guide).
Click to expand...
Click to collapse
ROM Manager is only supposed to be use to flash the Clockworkmod recovery image, then everything else is done by booting into the recovery mode. ROM manager's other features should not be used on the OV.
Whyzor said:
Updated original post with link for the new OV screens.
...
Click to expand...
Click to collapse
the only big problem left is getting the "back to stock" up to par for the newer OV's...
if someone could upload the critical part of a nandroid made from the newer stock system after rooting but before installing a custom rom, a more up-to-date back to stock guide could be put up with the newer files, or at least the older files patched with the newer kernel.
anyone want to upload the boot.img from a first nandroid backup off of a newer ov? the boot.img doesn't have any personal info, and it's got the newer kernel, which is all that's needed to fix up the older back-to-stock nandroid files.
bigsupersquid said:
the only big problem left is getting the "back to stock" up to par for the newer OV's...
if someone could upload the critical part of a nandroid made from the newer stock system after rooting but before installing a custom rom, a more up-to-date back to stock guide could be put up with the newer files, or at least the older files patched with the newer kernel.
anyone want to upload the boot.img from a first nandroid backup off of a newer ov? the boot.img doesn't have any personal info, and it's got the newer kernel, which is all that's needed to fix up the older back-to-stock nandroid files.
Click to expand...
Click to collapse
I think there's about an 85% chance that this contains the kernel that you're looking for; not sure if you have some way to deal with that 15% uncertainty but hopefully it's helpful.
Questions about ROM Manager
Hi, can I get a clear clarification about installing the ROM Manager on my LG Optimus p500, when your about to install the ClockwordMod Recovery you would have to select the phone model. LG p500 is not listed. Is there an alternative to it?
luwizwiz said:
Hi, can I get a clear clarification about installing the ROM Manager on my LG Optimus p500, when your about to install the ClockwordMod Recovery you would have to select the phone model. LG p500 is not listed. Is there an alternative to it?
Click to expand...
Click to collapse
This thread is under the Optimus V development section, you should ask questions about the p500 in this forum section:
http://forum.xda-developers.com/forumdisplay.php?f=839
Thanks, i didn't notice that its for Optimus V, i have a Optimus One. many thanks
Complete noob here, I mean a complete noob...first cell phone.
I was hoping to tether my new OV, but i quickly found out i have software version 2.2.2 which does not allow me to turn on hot spots. So I heard I can root my phone to get around this. I did stes 1-3 without issue, now I am stuck on step 3a. When i try to install busybox (not sure what this does for me?), i get the follow error/message "It looks like you have Busybox installed, but there are multiple copies still installed. /system/bin/ is currently as RW. This means that something may have gone wrong in the installation process. Please verify on your end that everything is correctly installed and working.
What do I verify? There is no Busybox app to run, only to install so it looks like the install failed?
ct200 said:
Complete noob here, I mean a complete noob...first cell phone.
I was hoping to tether my new OV, but i quickly found out i have software version 2.2.2 which does not allow me to turn on hot spots. So I heard I can root my phone to get around this. I did stes 1-3 without issue, now I am stuck on step 3a. When i try to install busybox (not sure what this does for me?), i get the follow error/message "It looks like you have Busybox installed, but there are multiple copies still installed. /system/bin/ is currently as RW. This means that something may have gone wrong in the installation process. Please verify on your end that everything is correctly installed and working.
What do I verify? There is no Busybox app to run, only to install so it looks like the install failed?
Click to expand...
Click to collapse
If you go into 'adb shell' from the PC with phone connected, or open the app 'terminal emulator' to get a unix prompt, and type 'busybox', you should see a list of commands. If you get a no command found, then it's not installed. It's suggested to install so you can run unix commands, but not really needed. Root & custom recovery are the important ones. You're probably safe to continue, just make sure to make a backup in recovery mode before doing anything else.
I've got an HTC One M9 (Rogers) that I've rooted and installed CM13 (13.0-20160221-nightly-himaul). I'm reasonably experienced with custom ROMs and such having played with all of this stuff on several Samsung devices (Captivate, Galaxy Nexus, SGS3), but this is my first go on an HTC device and first time running TWRP as opposed to Clockworkmod. I attempted to update my TWRP from 2.8.4 to 3.0.0-2 by booting to recovery. Not sure how and where I went wrong in that process but I can no longer boot to recovery, the phone starts up just fine and is usable. I can still access download mode and the bootloader, device is S-on (and has never been s-off). I have since attempted to reinstall TWRP via ADB commands as per the below post. The flash seems to take, no errors but still I'm unable to access recovery. I'm at somewhat of a loss as to what if anything I can try next.
http://forum.xda-developers.com/one-m9/general/guide-root-install-twrp-htc-one-m9-t3061133
the0f said:
I've got an HTC One M9 (Rogers) that I've rooted and installed CM13 (13.0-20160221-nightly-himaul). I'm reasonably experienced with custom ROMs and such having played with all of this stuff on several Samsung devices (Captivate, Galaxy Nexus, SGS3), but this is my first go on an HTC device and first time running TWRP as opposed to Clockworkmod. I attempted to update my TWRP from 2.8.4 to 3.0.0-2 by booting to recovery. Not sure how and where I went wrong in that process but I can no longer boot to recovery, the phone starts up just fine and is usable. I can still access download mode and the bootloader, device is S-on (and has never been s-off). I have since attempted to reinstall TWRP via ADB commands as per the below post. The flash seems to take, no errors but still I'm unable to access recovery. I'm at somewhat of a loss as to what if anything I can try next.
http://forum.xda-developers.com/one-m9/general/guide-root-install-twrp-htc-one-m9-t3061133
Click to expand...
Click to collapse
Are you running 3.x firmware? TWRP 3.0+ only works on firmware 3.x (i.e., the firmware that comes with Marshmallow). Flash TWRP 2.8x using fastboot and it should work just fine.
efrant said:
Are you running 3.x firmware? TWRP 3.0+ only works on firmware 3.x (i.e., the firmware that comes with Marshmallow). Flash TWRP 2.8x using fastboot and it should work just fine.
Click to expand...
Click to collapse
You sir are my hero, that definitely worked. So now to update that firmware so that I can update everything else. By chance do you know of a guide on how to update to that newer firmware version?
the0f said:
You sir are my hero, that definitely worked. So now to update that firmware so that I can update everything else. By chance do you know of a guide on how to update to that newer firmware version?
Click to expand...
Click to collapse
The only way I know how to do it with S-ON is to restore your device to stock (i.e., the version of stock before you flashed CM), take the OTA update, then flash the ROM you want.
efrant said:
The only way I know how to do it with S-ON is to restore your device to stock (i.e., the version of stock before you flashed CM), take the OTA update, then flash the ROM you want.
Click to expand...
Click to collapse
Sorry to be a bother and ask for any form of hand holding, but any idea where I can source the files for the return to stock? Currently have 2.11.631.2 on there (checked in the bootloader). Either that or a way to go S-OFF, I've been unable to find a guide on how to accomplish this without sunshine, which won't work on Cyanogenmod. If that required flashing even to something more similar to stock (IE Android Revolution) that's not the end of the world. Just kind of at a loss as to how to go about that process from where I am now.
the0f said:
Sorry to be a bother and ask for any form of hand holding, but any idea where I can source the files for the return to stock? Currently have 2.11.631.2 on there (checked in the bootloader). Either that or a way to go S-OFF, I've been unable to find a guide on how to accomplish this without sunshine, which won't work on Cyanogenmod. If that required flashing even to something more similar to stock (IE Android Revolution) that's not the end of the world. Just kind of at a loss as to how to go about that process from where I am now.
Click to expand...
Click to collapse
1) Make sure you have an sdcard formatted exfat in your device.
2) Boot into TWRP and back up your boot image to the sdcard. (You are doing this to get TWRP to create the proper directory structure.)
3) Find your back up that you just created and delete the files in the folder, i.e., the boot image and the md5 file.
4) Make sure TWRP has the option to keep system read-only checked (in the mounts menu).
5) Go here and download the three files (boot, recovery, system_image) for 2.11.631.2 and place them in the folder on your sdcard mentioned in point #3 above.
6) Restore the files using TWRP and reboot your device into Android.
7) You'll get an OTA notification. Accept it and update your device. (It'll take a while and reboot multiple times.)
8) Once updated, you'll get a second OTA notification to update you to Marshmallow. Accept it and update your device. (It'll take a while and reboot multiple times.)
9) Once updated, you can go ahead and flash TWRP 3.0+ and do what you want.
http://forum.xda-developers.com/one-m9/general/guide-return-to-stock-canadian-htc-one-t3108236
efrant said:
1) Make sure you have an sdcard formatted exfat in your device.
2) Boot into TWRP and back up your boot image to the sdcard. (You are doing this to get TWRP to create the proper directory structure.)
3) Find your back up that you just created and delete the files in the folder, i.e., the boot image and the md5 file.
4) Make sure TWRP has the option to keep system read-only checked (in the mounts menu).
5) Go here and download the three files (boot, recovery, system_image) for 2.11.631.2 and place them in the folder on your sdcard mentioned in point #3 above.
6) Restore the files using TWRP and reboot your device into Android.
7) You'll get an OTA notification. Accept it and update your device. (It'll take a while and reboot multiple times.)
8) Once updated, you'll get a second OTA notification to update you to Marshmallow. Accept it and update your device. (It'll take a while and reboot multiple times.)
9) Once updated, you can go ahead and flash TWRP 3.0+ and do what you want.
http://forum.xda-developers.com/one-m9/general/guide-return-to-stock-canadian-htc-one-t3108236
Click to expand...
Click to collapse
Thank you again sir, I'll give that a try this evening when I get back home. The help and the hand holding is very much appreciated. I thought that I knew a fair bit about android phones and custom ROMs from my time with my old Samsung devices, and have had to do a lot of learning when it's come to the One M9. Never had a device with the S-ON feature before and have had a lot of trouble trying to find info on what I need to do. I did find that forum post you linked, but wasn't sure if that applied to my device or not. Again VERY much appreciated.
Yup, 6.0 stock is installed and working, TWRP 3.0.0-2 installed and working as well. This time took a system backup and stored it in a safe place (as I expect much the same trouble when Android N or any other major update happens). Thank you again for all of your assistance in getting my phone fixed and updated.
I'm using stock oos and root with magisk
Everytime I get an ota it removes root.
Does anyone have any ideas
It happens because if you choose to update over System Settings it somehow knows that your phone is rooted / has an unlocked BL.
Therefore, Oneplus only offers the full Image. There is a way to inspect this full Image.
The way I'm doing it whenever I'm updating is:
download the newest FW over PC, inspect zip... delete something that says "recovery" on it.
Because that is the one, that will return you to stock recovery, instead of keeping TWRP installed.
After flashing that zip; TWRP should still be available for you, from there you can re-flash the magisk zip and you should all be rooted then.
moeq123 said:
It happens because if you choose to update over System Settings it somehow knows that your phone is rooted / has an unlocked BL.
Therefore, Oneplus only offers the full Image. There is a way to inspect this full Image.
The way I'm doing it whenever I'm updating is:
download the newest FW over PC, inspect zip... delete something that says "recovery" on it.
Because that is the one, that will return you to stock recovery, instead of keeping TWRP installed.
After flashing that zip; TWRP should still be available for you, from there you can re-flash the magisk zip and you should all be rooted then.
Click to expand...
Click to collapse
After that do you only loose root? Is your data, apps, customizations still there? Other than magisk root what else got deleted? Please answer i wanna do it your way.
Also where do you download FW file?
nadiration said:
After that do you only loose root? Is your data, apps, customizations still there? Other than magisk root what else got deleted? Please answer i wanna do it your way.
Also where do you download FW file?
Click to expand...
Click to collapse
Firmwares should be available on manufactures site.
For Oneplus 5T it should be that link: https://downloads.oneplus.com/devices/oneplus-5t/
Honestly, I can't tell what's inside These files; as I don't have one of them at Hand; and I'm not allowed to download and open such files here at work.
If you want I can expect them later after work (4 hours or something) or you download one and post me the Folder tree as a text here.
I know, that if you remove this one recovery file/Folder/entry that it passes the flashing of the recovery Partition.
If I recall correctly (from my Knowledge of devices and roms other than op5t) inside of These downloaded firmwares there should be a file called "Image.zip"
inside that Image.zip there should be Folders or files like "boot", "recovery" "system Images", and "userdata".
Delete recovery and userdata, repack it to "Image.zip" and repack that zip to the previously downloaded zip...
flashing that pack should prevent you from your data being wiped.
I don't know if magisk will work without flashing magisk.zip over.
Before you do all that stuff, back up your data, try it, and please - let us know if that has worked.
[Edit]: TL;DR - In the end, it just wipes your data and installs another recovery because it has been told to do so inside of these Firmware Images.
Download that Firmware, inspect everything, and delete stuff that tells him to do stuff that you don't like.
LG Joan H933 GLOBAL CANADA 20i ROM
DO NOT USE THIS ZIP FOR CONVERTING YOUR MODIFIED TO US998 PHONE BACK TO H933!
Your phone needs to be on H933 software with TWRP kept via LGUP partition dl mode (leaving recovery partition out when flashing kdz). Have a look at the second post, @cloud1250000 wrote a guide for that with an massive amount of help from @christopherrrg.
Also, there's a Telegram Group Chat available for H933 users only, for sorting out eventually arising problems:
LG V30 H933 Canada
Hi!
This Rom is 100% Stock. Most recent TWRP should first be installed. Then you can install this Rom and have Oreo with working TWRP.
This zip is created from the original KDZ. It contains almost the complete 20i firmware, but the partition table rewriting part and recovery image (beside five to eight other images) is removed. I changed the system.img, so you do not have to reinstall TWRP (recovery-from-boot.p deleted) when ROM once booted. I also changed the partition size of system.img, so the vendorized people can install this too without having problems because of a too small system partition.
This is a continuation of westwood24's idea and work, I've updated it to the newest fw version and edited it a bit. I followed his idea and made this for users who can not take OTA's because they have Custom Recovery / Root installed.
Features
Stock build made from official KDZ
Stock Build.prop
Unrooted
system.img modified to keep TWRP
System image size shrunk for being able to flash this on a smaller system partition, mainly caused by vendorizing
Removed dm-verity
Removed rctd (LG's root checker tool daemon)
Enabled opt-encrypt, it's your choice now if you want to encrypt your phone, it's no more forced. TWRP now is capable of decryption (both AOSP and stock) since a few versions
VoLTE and VoWiFi critical OP partition separate download, flashable via TWRP (Download / MD5: add01810ddb6da99ace26645acfb5d97)
Separate OP Partition download available here
Installation
What you need
Unlocked Bootloader[/URL]
Working TWRP installed [Link to newest unofficial TWRP]
When you need Root, flash latest Magisk afterwards [Download]
The zip!
How to install
When you are still on Nougat,
you should start fresh: Reboot to recovery using button combo or reboot app (needs root; btw, Magisk offers this possibility too: Menu -> Modules -> three dot menu top right - Reboot to recovery)
Then flash this latest TWRP.img via image flashing function in TWRP, reboot to recovery again (for fully working new recovery) and do a backup, then copy this backup to your PC.
Then initiate a factory reset. Wipe your system partition too in TWRP advanced wiping menu, copy the 20i firmware zip to your SD and install it. Reboot and enjoy
From Oreo:
For clean install: Factory reset and wipe system
You can also keep your data by simply dirty flashing the zip. *Be aware that problems may occure, maybe you need to do a factory reset to start fresh*
Flash the 20i zip, then Magisk zip when you need root, then reboot to System = you're DONE
At the first time you boot to system, it can be TWRP says No OS installed. You can ignore it.
If TWRP asks if you want to install SU, hit no (in newest TWRP SU is disabled, and the option to install the TWRP app is disabled too.)
Just give a thanks if you like the zip! :good:
@christopherrrg wrote a "little guide" for the peoples, who may ever have thought about going back to h33 original (rooted or not) sw. Give him some thanks pls, he's now a few nerves lost in this procedure i can imagine :good: thanks!
Here it is:
Okay so the steps below are for AFTER using the WTF thread to convert device and unlock bootloader; these steps are for canadian model users who would prefer to go back to stock canadian kdz with working root and twrp intact.
Step 1 - Attach converted US998 (bl unlocked and twrp installed) to LGUP.
Step 2 - PARTITION DL the canadian kdz but do not include recovery.
Step 3 - Let phone boot right from kdz flash and it will automatically boot TWRP.
Step 4 - While in TWRP; 1st factory reset AND AFTER format data then reboot recovery. (If not done TWRP has mount issues with cache and or system.)
Step 5 - After TWRP is rebooted flash no-verity-opt-encrypt-6.0.zip + lg-rctd-disabler-1.0.zip and afterwards flash magisk.
Step 6 - While still in TWRP use the option to power device down.
Step 7 - Attach device to PC while holding vol+ and it will automatically start download mode.
Step 8 - PARTITION DL the canadian kdz again EXCEPT uncheck everything BUT stock recovery; let it flash and reboot.
Step 9 - Should reboot 3 - 4 times.
Step 10 - Once booted to setup; get past then activate USB debugging, also open magisk and click yes as many times as it asks you. (Magisk remains because only RECOVERY is flashed at this point)
Step 11 - Download TWRP and rename to just twrp then place it in the root directory of your internal storage.
Step 11 - Connect device to android debug bridge, and start a shell with 'adb shell' command.
Step 12 - then type 'su' and hit enter in order to gain root privilege. (Will have to click accept on super user on device)
Step 13 - then type 'dd if=/sdcard/twrp.img of=/dev/block/bootdevice/by-name/recovery'
If done correctly you should see flashing (almost like fastboot) however you will not have anything happen to your device graphically SO open magisk and click modules then click reboot to recovery and profit!
You should be on H933 kdz with TWRP and root.
However for some weird reason, cloud is correct as the battery drain is abysmal. My phone used to go from 9am 100% to about 60% by the time I get home at 5pm. Today it's gone down to 22% from 100% at 9am and it's only 2pm. @cloud1250000's brain was mostly picked for this so he deserves any and all credit; I just confirmed and wrote this up for reference.
Enjoy!
Credits to @cloud1250000
hey, it's cold out there, what about a chilled-out evening on an open fire and flashing new software on your phone...? a tester is welcome this doesn't brick your phone...
I edited this right out. For my excitement I skipped almost every single thing in the thread and I apologize however I'm willing to test and will report my findings right away!
ok, link follows via pm :good:
christopherrrg said:
I edited this right out. For my excitement I skipped almost every single thing in the thread and I apologize however I'm willing to test and will report my findings right away!
Click to expand...
Click to collapse
Someone else PM'ed me so we have two testers.
seadersn said:
LG Joan H933 GLOBAL CANADA 20G ROM
DO NOT USE THIS ZIP FOR MODEL CONVERSIONS!Hi!
This Rom is 100% Stock. Most recent TWRP should first be installed. Then you can install this Rom and have Oreo with working TWRP.
This needs testing first, please hit me a PM for getting the link.
This zip is created from the original KDZ (H93320g_00_OPEN_CA_OP_0910.kdz). It contains almost the complete 20G firmware, but the partition table rewriting part and recovery image (beside five to eight other images) is removed. I changed the system.img, so you do not have to reinstall TWRP (recovery-from-boot.p deleted) when ROM once booted. I also changed the partition size of system.img, so the vendorized people can install this too without having problems because of a too small system partition.
This is a continuation of westwood24's idea and work, I've updated it to the newest fw version and edited it a bit. I followed his idea and made this for users who can not take OTA's because they have Custom Recovery / Root installed.
Features
Stock build made from official KDZ
Stock Build.prop
Unrooted
system.img modified to keep TWRP
System image size shrunk for being able to flash this on a smaller system partition, mainly caused by vendorizing
Removed dm-verity
Removed rctd (LG's root checker tool daemon)
Enabled opt-encrypt, it's your choice now if you want to encrypt your phone, it's no more forced. TWRP now is capable of decryption (both AOSP and stock) since a few versions
Installation
What you need
Unlocked Bootloader [How to do]
Working TWRP installed (should be installed already, otherwise you wouldn't need this zip )[Link to newest unofficial TWRP]
When you need Root, Latest Magisk [Download]
The zip!
How to install
When you are still on Nougat,
you should start fresh: Reboot to recovery using button combo or reboot app (needs root; btw, Magisk offers this possibility too: Menu -> Modules -> three dot menu top right - Reboot to recovery)
Then flash this latest TWRP.img via image flashing function in TWRP, reboot to recovery again (for fully working new recovery) and do a backup, then copy this backup to your PC.
Then initiate a factory reset. Wipe your system partition too in TWRP advanced wiping menu, copy the 20G firmware zip to your SD and install it. Reboot and enjoy
From Oreo:
For clean install: Factory reset and wipe system
You can also keep your data by simply dirty flashing the zip. *Be aware that problems may occure, maybe you need to do a factory reset to start fresh*
Flash the 20G zip, then Magisk zip when you need root, then reboot to System = you're DONE
At the first time you boot to system, it can be TWRP says No OS installed. You can ignore it.
If TWRP asks if you want to install SU, hit no (in newest TWRP SU is disabled, and the option to install the TWRP app is disabled too.)
Rom Version
Android Version: 8.0 Oreo
Android security patch level: 2018-09-1
Just give a thanks if you like the zip! :good:
You want to help me with a [donation?] Not asking for it, I have fun doing this for you, but feel free...
Click to expand...
Click to collapse
Please can you explained me something, you wrote DO NOT USE THIS ZIP FOR MODEL CONVERSIONS!, but we must convert the H933 to US988 in order to install TWRP and root. So now I can install it, go back from US988 to H933 and keep TWRP and root ?
Thanks
so actually; as the above user is mentioning I attempted a partition DL flash of the kdz minus recovery and it constantly boots to recovery after flash (which i'm sure is totally normal as stock will not boot with custom recovery without no verity etc) buuuuut my stupid behind didn't flash those and assumed it would not work so decided to panic and flash the us998 kdz back in order to restore my backup and I think I screwed up my download mode as it now shows download mode for 2 seconds then reboots right into recovery; I believe I may have corrupted my laf partition and am now currently working on getting back to a functioning device; luckily the bootloader is still unlocked and I can still flash things as system and data both mount no problem.
my apologies for the lengthly message but or anyone else who is planning to test please remember if you're flashing back from US998 to H933 not to do as i've done and remember no verity etc so it can at least boot so you can THEN flash this zip here.
after all of that i've still got nothing to report as flashing it seems to look great but because I kdz back to us998 i'm afraid to use this zip until I get a booting phone again; also please dont take this as me flaming or anything. i'm sure i'll fix my device with fastboot soon and shall resume testing.
christopherrrg said:
so actually; as the above user is mentioning I attempted a partition DL flash of the kdz minus recovery and it constantly boots to recovery after flash (which i'm sure is totally normal as stock will not boot with custom recovery without no verity etc) buuuuut my stupid behind didn't flash those and assumed it would not work so decided to panic and flash the us998 kdz back in order to restore my backup and I think I screwed up my download mode as it now shows download mode for 2 seconds then reboots right into recovery; I believe I may have corrupted my laf partition and am now currently working on getting back to a functioning device; luckily the bootloader is still unlocked and I can still flash things as system and data both mount no problem.
my apologies for the lengthly message but or anyone else who is planning to test please remember if you're flashing back from US998 to H933 not to do as i've done and remember no verity etc so it can at least boot so you can THEN flash this zip here.
after all of that i've still got nothing to report as flashing it seems to look great but because I kdz back to us998 i'm afraid to use this zip until I get a booting phone again; also please dont take this as me flaming or anything. i'm sure i'll fix my device with fastboot soon and shall resume testing.
Click to expand...
Click to collapse
Thanks for the update, good luck recovering the phone. Maybe ou can try LG software from recovery ....
[email protected] said:
Please can you explained me something, you wrote DO NOT USE THIS ZIP FOR MODEL CONVERSIONS!, but we must convert the H933 to US988 in order to install TWRP and root. So now I can install it, go back from US988 to H933 and keep TWRP and root ?
Thanks
Click to expand...
Click to collapse
Yes you must be on a global Canadian kdz that is BEFORE this version.
when you convert back make sure you use partition DL and uncheck recovery; then when you flash canadian kdz and boot up flash dm no verity and the other zip to make stock kdz boot with twrp still intact; then once system boots at least once you reboot into twrp with the master reset combo and then use the zip provided by these gentlemen. ( at least now that my phone is down for the moment this is my theory ) heh:silly:
christopherrrg said:
Yes you must be on a global Canadian kdz that is BEFORE this version.
when you convert back make sure you use partition DL and uncheck recovery; then when you flash canadian kdz and boot up flash dm no verity and the other zip to make stock kdz boot with twrp still intact; then once system boots at least once you reboot into twrp with the master reset combo and then use the zip provided by these gentlemen. ( at least now that my phone is down for the moment this is my theory ) heh:silly:
Click to expand...
Click to collapse
Thanks again, but flashing back the H933 will relock the bootloader ?
[email protected] said:
Thanks again, but flashing back the H933 will relock the bootloader ?
Click to expand...
Click to collapse
nope! it remains unlocked.
I did manage to recover my device and my download mode (thanks to Matts amazing WTF guide.)
so give me about an hour or so and i'll retry; just going to take a quick shower.
Edit - had quite a few issues. Can't seem to get TWRP to actually work after doing partition DL all except recovery. (TWRP acts as if there is no system and when I try to boot it just reboots back into recovery.) Almost as if my Canadian device WANTS to stay US998 lol I got some issues to sort but will report back once I figure out how to make twrp flash AFTER full Canadian kdz, not sure if it's possible to flash recovery without fastboot is it?
recovery *would* be flashable with a rooted system and the dd (diskdump) command from within booted android.
so h933 is a device which needs conversion. this zip can then only be used when:
- you converted your h933 to us998 to get the fastboot commands and install twrp etc.
- your phone is then *converted back* to h933 with original h933 kdz, but with keeping twrp via partition dl mode of lgup.
- this way you lose fastboot commands (which normaly shouldn't be needed anymore), but can keep twrp and flash roms.
this method should work. because bootloader remains unlocked and is writable by twrp, even if you are on full h933 firmware, except recovery partition.
looks like we really need to work this out, carefully not that one of you nice testers have a non working phone because of this zip used in the wrong place (with us998 kdz installed) and moment (before full h933 kdz is installed with keeping twrp).
we need to try too, if this zip is installable on a converted to us998 phone and then at least boots as usual, or if sth. gets mixed up then (because it then has mixed partitions, ⅔ of the phones partitions are h933 fw then, and ⅓ is us998 partitions).
christopherrrg said:
nope! it remains unlocked.
I did manage to recover my device and my download mode (thanks to Matts amazing WTF guide.)
so give me about an hour or so and i'll retry; just going to take a quick shower.
Edit - had quite a few issues. Can't seem to get TWRP to actually work after doing partition DL all except recovery. (TWRP acts as if there is no system and when I try to boot it just reboots back into recovery.) Almost as if my Canadian device WANTS to stay US998 lol I got some issues to sort but will report back once I figure out how to make twrp flash AFTER full Canadian kdz, not sure if it's possible to flash recovery without fastboot is it?
Click to expand...
Click to collapse
this may be because of a differing partition table. *may*, i don't know this. i would like to have such a device for intensive testing... or visit canada and a person who's willing to drink much beer while testing this out :good:
seadersn said:
recovery *would* be flashable with a rooted system and the dd (diskdump) command from within booted android.
so h933 is a device which needs conversion. this zip can then only be used when:
- you converted your h933 to us998 to get the fastboot commands and install twrp etc.
- your phone is then *converted back* to h933 with original h933 kdz, but with keeping twrp via partition dl mode of lgup.
- this way you lose fastboot commands (which normaly shouldn't be needed anymore), but can keep twrp and flash roms.
this method should work. because bootloader remains unlocked and is writable by twrp, even if you are on full h933 firmware, except recovery partition.
looks like we really need to work this out, carefully not that one of you nice testers have a non working phone because of this zip used in the wrong place (with us998 kdz installed) and moment (before full h933 kdz is installed with keeping twrp).
we need to try too, if this zip is installable on a converted to us998 phone and then at least boots as usual, or if sth. gets mixed up then (because it then has mixed partitions, ⅔ of the phones partitions are h933 fw then, and ⅓ is us998 partitions).
Click to expand...
Click to collapse
I got my phone fully working again and my backup restored. (US998)
So I think what I'm going to attempt today is flashing FULL canadian kdz (fresh stock including recovery) and let it boot then I'm gonna try to dd the recovery to get TWRP access.
And go from there.
I got your PM and will need to pull out my nexus 4 for telegram but will set it up after work today and join you guys.
---------- Post added at 01:17 PM ---------- Previous post was at 01:15 PM ----------
seadersn said:
this may be because of a differing partition table. *may*, i don't know this. i would like to have such a device for intensive testing... or visit canada and a person who's willing to drink much beer while testing this out :good:
Click to expand...
Click to collapse
Heheh I'm willing to drink much beer wish I had my 2nd device because I'd have mailed you guys this H933 to crack.
We will get it soon, a lot more H933 people coming out of hiding really helps. ?
V
[email protected] said:
Thanks for the update, good luck recovering the phone. Maybe ou can try LG software from recovery ....
Click to expand...
Click to collapse
What actually got me out of the loop was Westwoods stock US998 TWRP ROM zip. I believe it restored my LAF partition and download mode worked no problem in order to use LGUP.
However these issues were of my own accounts; essentially from step 1 this is what the full procedure I assume will be like for us H933 users.
Step 1. Convert H933 to US998 and unlock bootloader using WTF guide.
Step 2. Using LGUP, 'REFURBISH' US998 device back into H933 kdz (accept partition layout changes) [attempted to use partition DL with all partitions minus recovery; however stock system won't boot with custom recovery unless rooted and no decrypt and dm verity flashed before system boots {failed to try this due to panic and forgetfulness so this may work but I'd like to attempt using dd from fresh stock also.}]
Step 3. Attempt dd recovery flash on bootloader unlocked H933 due to missing fastboot etc.
Step 4. Hope for profit? ?
I also apologize to you all for the lengthly posts as well but from all my years here on this website it's reading through the users problems where solutions are generally found so even though I followed wrong directions at first it's up to show everyone how I messed up and can be avoided.
christopherrrg said:
V
What actually got me out of the loop was Westwoods stock US998 TWRP ROM zip. I believe it restored my LAF partition and download mode worked no problem in order to use LGUP.
However these issues were of my own accounts; essentially from step 1 this is what the full procedure I assume will be like for us H933 users.
Step 1. Convert H933 to US998 and unlock bootloader using WTF guide.
Step 2. Using LGUP, 'REFURBISH' US998 device back into H933 kdz (accept partition layout changes) [attempted to use partition DL with all partitions minus recovery; however stock system won't boot with custom recovery unless rooted and no decrypt and dm verity flashed before system boots {failed to try this due to panic and forgetfulness so this may work but I'd like to attempt using dd from fresh stock also.}]
Step 3. Attempt dd recovery flash on bootloader unlocked H933 due to missing fastboot etc.
Step 4. Hope for profit? ?
I also apologize to you all for the lengthly posts as well but from all my years here on this website it's reading through the users problems where solutions are generally found so even though I followed wrong directions at first it's up to show everyone how I messed up and can be avoided.
Click to expand...
Click to collapse
absolutely ok, the more info the better so when one wants to stay stock h933, steps are
step 1: jep
step 2: jep, partition dl with *recovery excluded* to h933 kdz (after unlocking via us998). twrp should be present and bootable after that.
step 3: boot recovery, format data, reboot to recovery, flash opt-encrypt, no verity and make sure, /system/recovery-from-boot.py is deleted or renamed. and eventually flash magisk and then boot to rom, jep.
could imagine that this works, but, i know too little about frankensteined phones. there may be hassles and hiccups. first boot up and test, then trying a restore, in hope it will be succesful :good:
seadersn said:
absolutely ok, the more info the better so when one wants to stay stock h933, steps are
step 1: jep
step 2: jep, partition dl with *recovery excluded* to h933 kdz (after unlocking via us998). twrp should be present and bootable after that.
step 3: boot recovery, format data, reboot to recovery, flash opt-encrypt, no verity and make sure, /system/recovery-from-boot.py is deleted or renamed. and eventually flash magisk and then boot to rom, jep.
could imagine that this works, but, i know too little about frankensteined phones. there may be hassles and hiccups. first boot up and test, then trying a restore, in hope it will be succesful :good:
Click to expand...
Click to collapse
WOW; there it is.
Format Data. Another neglected procedure on my end grrr.
Saves the whole issue of using DD period.
And would explain why TWRP also half worked.
Gonna give it another crack as soon as I'm home. I'll also have telegram set up as to not spam this thread much further.
@cloud1250000 has posted a way to have a rooted canadian ROM https://forum.xda-developers.com/lg...odem-to-converted-us998-t3824769/post77613655 but from his instructions. He said he installed magisk to the canadian system to ensure root in order to use adb shell to install twrp. But I can't for the life of me figure out how he kept magisk but nothing else... so maybe he can help us.
No matter what I do after conversion of US998; H933 will not boot with TWRP on stock unless it's 100% stock. (Even after attempting dm verity, no encrypt and root) by trying your advice and tinkering with a bit of my own. LGUP also still reports the H933 device as a US99820d
Basically if he can help explain how he got magisk on there or I can figure it out then unfortunately at the moment we can't really flash this as we need a working recovery and sadly he's the only Canadian user reported so far having working twrp, root and lte working no problem.
Thing's I've tried so far:
- converted US998 to H933 with PARTITION DL and unchecked RECOVERY; recovery sticks however after formatting data then rebooting into recovery I then remove /system/recovery-bak (may have spelt that wrong but you get what I mean) I try flashing no encrypt and dm verity then flash root everything works (no red error messages of any kind) Boots back to recovery.
- converted US998 to H933 with PARTITION DL and made sure ALL checkboxes were checked. Phone booted but obviously no working recovery and no (at the current moment) known method of rooting without fastboot commands.
So sadly until we figure that I think we're stuck. ?
Will PM you my telegram info in the next few minutes.
So...
I have no clue why but when going back to the h933 from the us998... There's an extra partition called OP where, I assume, information about the carriers/modem can be found.
You should be aware that in canada now... there's no carrier locked phone anymore... so my guess is... this OP partition is configured on the first boot by looking at the sim that was inserted in the phone.
The problem.
TWRP doesn't have the command to setup the OP partition correctly and the phone do send this command to the recovery on first boot..
(found by looking at recovery log)
So what I did was...
1. Keep TWRP and use LGUP to go back to H933.
2. Boot into twrp and flash all needed zip (root + the other 2)
3. Flash the stock recovery and allow the phone to setup the OP partition correctly upon reboot (there will be a weird circle with "erasing" text on the screen)
4. Boot in the phone and launch the magisk app. Say yes a bunch of time.
5. Use a rooted adb shell to flash back twrp.
6. Profit/Enjoy
In my original guide, I did flash a bunch of partition that I got from a working h933.. so maybe it's missing some steps in order to work.
https://forum.xda-developers.com/lg...rted-us998-t3824769/post77613655#post77613655
Good luck.
cloud1250000 said:
So...
I have no clue why but when going back to the h933 from the us998... There's an extra partition called OP where, I assume, information about the carriers/modem can be found.
You should be aware that in canada now... there's no carrier locked phone anymore... so my guess is... this OP partition is configured on the first boot by looking at the sim that was inserted in the phone.
The problem.
TWRP doesn't have the command to setup the OP partition correctly and the phone do send this command to the recovery on first boot..
(found by looking at recovery log)
So what I did was...
1. Keep TWRP and use LGUP to go back to H933.
2. Boot into twrp and flash all needed zip (root + the other 2)
3. Flash the stock recovery and allow the phone to setup the OP partition correctly upon reboot (there will be a weird circle with "erasing" text on the screen)
4. Boot in the phone and launch the magisk app. Say yes a bunch of time.
5. Use a rooted adb shell to flash back magisk.
6. Profit/Enjoy
In my original guide, I did flash a bunch of partition that I got from a working h933.. so maybe it's missing some steps in order to work.
https://forum.xda-developers.com/lg...rted-us998-t3824769/post77613655#post77613655
Good luck.
Click to expand...
Click to collapse
Yeah I got lost on your step about dd recovery I was like uh wait how did he retain root?!
Thanks so much for your input! Very much appreciated.:highfive:
Also if we figure this out; that's an enormous contribution towards us getting custom ROMs working; thank you again!
Hello everyone !
I have a xiaomi Mi A2 lite for few days, based on Pie 9.0. I decided to install a custom rom on it (resurrection or lineage OS16) so I unlocked the bootloader, rooted properly the phone, and then tryed to use TWRP to install a new ROM.
Unfortunatly, I never succeeded to do so: each time I tried, the installation failed, showing an "error 1".
Trying to fix this issue, I unfortunatly deleted the OS of my phone, and still can't install a new ROM. I tried to flash a stock ROM from xiaomi site, following this thread: https://forum.xda-developers.com/mi-a2-lite/help/os-image-please-help-t3885625/page3 , but Mi flash tool doesn't work well on my computer (it's still showing an "unhandled exception" error, whatever I'm trying to do.
Here we are, I've got two problems and I don't really know what to do, despite my searching on the web. My phone is now unusable (I can access to the TWRP recovery, can use fastboot, but that's all..)
Do you have any advice to clean up all the mess I did ?
Thank you a lot for your time !
Download the stock rom (preferably 10.0.3.0) extract it along with adb and fastboot into the same folder, install the drivers, boot into fastboot, connect it to PC and run flash_all.bat and you should be back onto stock rom! If you want to install a custom rom follow this: github. com/tkchn/daisyinstall/blob/master/README.md
Armandpewpew said:
Hello everyone !
I have a xiaomi Mi A2 lite for few days, based on Pie 9.0. I decided to install a custom rom on it (resurrection or lineage OS16) so I unlocked the bootloader, rooted properly the phone, and then tryed to use TWRP to install a new ROM.
Unfortunatly, I never succeeded to do so: each time I tried, the installation failed, showing an "error 1".
Trying to fix this issue, I unfortunatly deleted the OS of my phone, and still can't install a new ROM. I tried to flash a stock ROM from xiaomi site, following this thread: https://forum.xda-developers.com/mi-a2-lite/help/os-image-please-help-t3885625/page3 , but Mi flash tool doesn't work well on my computer (it's still showing an "unhandled exception" error, whatever I'm trying to do.
Here we are, I've got two problems and I don't really know what to do, despite my searching on the web. My phone is now unusable (I can access to the TWRP recovery, can use fastboot, but that's all..)
Do you have any advice to clean up all the mess I did ?
Thank you a lot for your time !
Click to expand...
Click to collapse
Are you sure that you followed the procedure to install a custom rom? Can you tell which steps did you do? And about the error of MiFlash you can try with other version so there are many versions uploaded that don´t match well.
If you can't use the fastboot u need to force EDL Mode.. The best and simple way to install the ROM stock is using MI Flash Tool, u can find a tutorial in here or in YouTube it's easy if you follow all the steps! Good Luck
Armandpewpew said:
Hello everyone !
I have a xiaomi Mi A2 lite for few days, based on Pie 9.0. I decided to install a custom rom on it (resurrection or lineage OS16) so I unlocked the bootloader, rooted properly the phone, and then tryed to use TWRP to install a new ROM.
Unfortunatly, I never succeeded to do so: each time I tried, the installation failed, showing an "error 1".
Trying to fix this issue, I unfortunatly deleted the OS of my phone, and still can't install a new ROM. I tried to flash a stock ROM from xiaomi site, following this thread: https://forum.xda-developers.com/mi-a2-lite/help/os-image-please-help-t3885625/page3 , but Mi flash tool doesn't work well on my computer (it's still showing an "unhandled exception" error, whatever I'm trying to do.
Here we are, I've got two problems and I don't really know what to do, despite my searching on the web. My phone is now unusable (I can access to the TWRP recovery, can use fastboot, but that's all..)
Do you have any advice to clean up all the mess I did ?
Thank you a lot for your time !
Click to expand...
Click to collapse
The first problem with TWRP Error code :1 - the problem is with twrp itself- install a different version ,i am using 3.3.1-0 by offain ,i've had this error on allmost every twrp besides the offain versions and dees_troy.
The second problem : with the deleted os : you have 2 options :
1. Download the latest MiFlash from the official site and install it ,on the top left of the screen, you can see Drivers button ,click on install. Then navigate to stock rom folder ,go in fastboot mode on your device and connect to PC ,hit refresh ,then flash.
2. If this doesn't help ,custom rom is an option ,there are 2 links
https://daisyfiles.pp.ua/Firmwares/MIUI/ - from here download miui version Golden Master 1.1
https://forum.xda-developers.com/mi...ol-one-driversunlocktwrpfactory-t3866191/amp/ - download this all in one tool, you can lock ,relock ,install twrp recovery ,custom roms ,it is perfect!
For the installation - put the rom on sd card ,install twrp version that doesnt give Error 1 code ,then format data,system,cache,dalvik/art ,internal storage.
And the last thing - install the ROM zip and try MIUI 10.5 This is the best temporary solution,until you set MiFlash the right way ,or on another PC
Hello !
First of all, thank you very much for your quick and complete answer
I finally succedeed to flash a stock ROM on the phone, using Mi flash tool, so I'm back on track ! About the "unhandled exception" error, i've just fixed it by creating a "log folder" in the MI flash tool folder, it's good to know, maybe It will help someone else one day ^^
When I tried to install a custom ROM last time, I used the 3.3.1 version of TWRP. Because it didn't work (error 1), I used the 3.3.0 one and I had the same exact error code. Do you think I should try older versions one by one ?
I'm going to unlock it and root it right now,
Thank you again,
Arnaud
PS: Oh, last thing, when TWRP recovery will be properly installed on my phone, shall I root it by using magisk ?
Armandpewpew said:
I'm going to unlock it and root it right now,
Click to expand...
Click to collapse
Updating my situation:
So I successfully installed TWRP 3.3.3-0 on the phone and did a huge backup to avoid deleting my OS again.
Now I'm confused about what to do: I did understand that I need to root my phone (using magisk) BEFORE trying to install a custom ROM, but I'm really not sure about it, should I ?
I tried, and it still doesn't work (error1), I noticed that error 1 shows some interresting details:
"error installing zip file '/sdcard/TWRP/RR-P-v7.0.2-20190907-daisy-Official.zip' "
The point is I do not have any sd card in my phone (for the moment), is it possible that it can't install the ROM because TWRP is trying to install the ROM on an non-existing storage ? I will try to get an sdcard somewhere to check how it behave.
Thank you again,
Armandpewpew said:
Updating my situation:
So I successfully installed TWRP 3.3.3-0 on the phone and did a huge backup to avoid deleting my OS again.
Now I'm confused about what to do: I did understand that I need to root my phone (using magisk) BEFORE trying to install a custom ROM, but I'm really not sure about it, should I ?
I tried, and it still doesn't work (error1), I noticed that error 1 shows some interresting details:
"error installing zip file '/sdcard/TWRP/RR-P-v7.0.2-20190907-daisy-Official.zip' "
The point is I do not have any sd card in my phone (for the moment), is it possible that it can't install the ROM because TWRP is trying to install the ROM on an non-existing storage ? I will try to get an sdcard somewhere to check how it behave.
Thank you again,
Click to expand...
Click to collapse
Nope ,as i said ,error code is with the version of twrp ,i am using TWRP 3.3.3-1 dees_troy ,i've had the same problem as yours ,i was trying to flash from internal memory ,tried flash from sd card,the problem was the same.So i have tried 3 or 4 different versions ,3.3.3-0 (2 different versions ) gave me error 7 ,another 3.3.3-0 destroyed my system image ,3.2.3-0 don't show my sd card in twrp .So download TWRP 3.3.3-1by dees_troy ,i am using it right now ,but i am using the all in one tool ,that i have mentioned in my previous post - no errors ,no mistakes
Okay, I will try the TWRP 3.2.3 then, this is the only one I didn't try
What about magisk ?
SubwayChamp said:
Are you sure that you followed the procedure to install a custom rom? Can you tell which steps did you do? And about the error of MiFlash you can try with other version so there are many versions uploaded that don´t match well.
Click to expand...
Click to collapse
Hi !
I basically followed the procedure here: https://www.the***********.com/install-twrp-recovery-root-xiaomi-mi-a2-a2-lite/
And then https://gmtechweb.com/resurrection-remix-v7-galaxy-s6/
Thanks for your time
Error 1 is for use official twrp, please read before, only twrp for custom ROMs is offain's twrp 3.3-1.0
Os_Herdz said:
Error 1 is for use official twrp, please read before, only twrp for custom ROMs is offain's twrp 3.3-1.0
Click to expand...
Click to collapse
Sorry I didn't undestand that at all
I will follow the ghitub step by step by using all pieces they provide. Only one thing, they give the Offain TWRP 3.3.0-0. Do you know where I can find the 3.3.3-1 you're all talking about ?
Armandpewpew said:
Hi !
I basically followed the procedure here: https://www.the***********.com/install-twrp-recovery-root-xiaomi-mi-a2-a2-lite/
And then https://gmtechweb.com/resurrection-remix-v7-galaxy-s6/
Thanks for your time
Click to expand...
Click to collapse
The first link did take me to any place and the second is for other completely different device, I don´t know why following a procedure for a device with a different scheme partition.
It could be that previously you must have a determined firmware as base before to flash any custom rom, in this case you have to flash it using MiFlash tool checking on "clean all" option (preferably)
The moves basically are these:
1.- Boot to twrp-daisy-3.3.1-0-offain.img using fastboot (just boot to, don´t flash it)
2.- Wipe system, dalvik/cache, data from the previous.
3.- In the case is indicated by developer Format data.
4.- Flash the desired rom.
5.- Flash the twrp-daisy-3.3.1-0-offain installer zip (it´s not the same that the boot image) you can use adb sideload or previously move the file to your external SDCard or then to format data transfer the file to your internal SDCard.
6.- Go to the main menu on TWRP and in reboot options change to the other slot from A to B and viceversa, then to switch reboot again to recovery.
7.- Now flash the Disable-Force-Encryption.
8.- In the case (most likely you want) Flash the GApps and flash Magisk at last, then reboot normally.
The links for TWRP are these:
https://androidfilehost.com/?fid=6006931924117887098
https://androidfilehost.com/?fid=6006931924117887097
Hi !
They are too many flashing procedures everywhere, it's a giant mess and it's really hard to find the proper one when we don't use to it
Anyway, I finally succeeded to properly install a custom ROM on my phone by using this procedure: https://github.com/tkchn/daisyinstall/blob/master/README.md
Everything is now working well, thank you all for your help, you saved my day
HELP! I am getting the same error message, i know what I need to do, download the Offain version of TWRP, but none of the links work! Android File Host DOES NOT WORK for some reason. Can someone upload these files somewhere else for me? Please? I have no other way of getting these files, they don't exist anywhere else on the web... I have already tried every other available versions of TWRP and am getting the same error message (1) as OP.
Tipsymario said:
Download the stock rom (preferably 10.0.3.0) extract it along with adb and fastboot into the same folder, install the drivers, boot into fastboot, connect it to PC and run flash_all.bat and you should be back onto stock rom! If you want to install a custom rom follow this: github. com/tkchn/daisyinstall/blob/master/README.md
Click to expand...
Click to collapse
hey sir , i download 10.0.13 sinc emy internet sucks i can't just go and download another 1.5go of 10.0.3.0 , the probleme is i can't find flash_all.bat even miflash and all in one tool say they can't find flash_all.bat can u help me here where can i find it or build it ?
Alecjasonn said:
HELP! I am getting the same error message, i know what I need to do, download the Offain version of TWRP, but none of the links work! Android File Host DOES NOT WORK for some reason. Can someone upload these files somewhere else for me? Please? I have no other way of getting these files, they don't exist anywhere else on the web... I have already tried every other available versions of TWRP and am getting the same error message (1) as OP.
Click to expand...
Click to collapse
Try using this link if AFH is not working : https://daisyfiles.pp.ua/TWRP/