Related
Hello folks!
Apparently the official TWRP recovery 3.0.2 has some sort of problems with android 7.1.1 Nougat, so this unofficial recovery was created to work around those issues in the meantime.
The official hosting of this unofficial recovery is in this thread: http://forum.xda-developers.com/nex...recovery-twrp-2-8-7-0-touch-recovery-t3234976
It is buried almost all the way at the end.
For sake of convenience, I am making it available here for those that wish to get going with it quickly. Note that I am not the developer of this nor am I the maintainer. This is here for easy reference only. You should speak with TWRP Grand Poobah Dees_Troy in the above thread for further details.
twrp-3.0.2-3-angler.zip 14.2 MB
https://mega.nz/#!tdcUAa4a!G-bGMWznEUAkE3Ih3ioaHq2Fx0NdzGnIlhY-nuPg__s
Installation instructions are straightforward:
1. Decompress the zip file so you have the .img file. Do not flash the zip file!
2. Place the recovery image in the same folder as your ADB / fastboot apps.
3. Put your phone in boot loader mode: Power button + volume down button.
4. Pull open a console in this directory and type fastboot devices. Proceed when you a serial number and "fastboot" next to it.
5. Type fastboot flash recovery twrp-3.0.2-3-angler.img. If all goes well you should see a success message of some sort.
6. Reboot and enjoy!
I've been using this for a few ROM installs already and haven't seen any problems.
Best of luck to you!
Guess I'll give this a go and report back later on heh. Will this recovery actually stay after a restart?
Sent from my Nexus 6P using XDA-Developers mobile app
Hmm, seems to be working ok for me on the 7.1.1 DP2 release.
Sent from my Pixel XL using Tapatalk
PearsonDKA said:
Guess I'll give this a go and report back later on heh. Will this recovery actually stay after a restart?
Click to expand...
Click to collapse
Like some others have mentioned, I keep seeing it disappear after restarting the phone once, twice or a few times, so I have to re-flash it almost every time I need it.
Not sure what the hangup is. Size-related?
CaptShaft said:
Like some others have mentioned, I keep seeing it disappear after restarting the phone once, twice or a few times, so I have to re-flash it almost every time I need it.
Not sure what the hangup is. Size-related?
Click to expand...
Click to collapse
You need to flash either Root or a modified boot image for it to stay
jaytv said:
You need to flash either Root or a modified boot image for it to stay
Click to expand...
Click to collapse
Good to know. 2 questions:
1) What modifications to a regular boot image do we need to make to keep it?
2) Are all boot images the same? Can we all use the same modified boot image or does it differ depending on the ROM?
CaptShaft said:
Good to know. 2 questions:
1) What modifications to a regular boot image do we need to make to keep it?
2) Are all boot images the same? Can we all use the same modified boot image or does it differ depending on the ROM?
Click to expand...
Click to collapse
Sounds like time for you to do some reading as to what root and boot images are. Search works great. I suggest the threads on SuperSU (a form of root) and also looking at the many wonderful custom boot images and Roms that are floating around in this forum.
The simple answer is flash Super Su or find a modified boot image for the current release and flash that.
Also, Heisenberg's excellent beginner's thread in Nexus 6p general is a great place to start.
Enjoy!
Just what I was looking for.
I was in TWRP loop forever and couldn't figure it out till this thread. No issues now
I've installed the one from the main thread and it's working for me.
I just wanted to mention what the bugs are:
shadowstep said:
TWRP versions 3.0.2-1 and above work with Android Nougat 7.0's encryption, TWRP 3.0.2-0 and below don't. Also, both versions 3.0.2-1 and 3.0.2-2 are buggy at the moment, but none of those bugs are along the lines of encryption. Read the end of this post for more information.
(Replies snipped)
EFS partition is never needed to be restored under any general circumstance. It is the partition where the phone stores its IMEI information, MAC address, product code, etc. and will never be needed to be modified or changed in any way. Even if you're flashing a stock factory image (be it of 6.0.1 or 7.0, whenever it is out), it would never touch this partition. You should just backup it once, store it away for emergency purposes and never backup or restore it again.
Okay now moving onto important notes and the bugs:
1. TWRP 3.0.2-0: Is stable and has no known bugs. However, it has not been updated to handle Android Nougat 7.0's encryption. Hence, if you're on 7.0 and you're encrypted, it will keep asking for an encryption password even if you don't have one or if you have one and are inputting it correctly, it will refuse to accept it. If you're on 7.0 and you're unencrypted, then this version should be fine.
2. TWRP 3.0.2-1: Is not stable and has a known bug. The bug would affect those who are restoring their EFS partition using this version of TWRP. The EFS partition has two subparts to it, i.e. /efs1 and /efs2. So, when you check EFS at the backup option menu in TWRP, it backups /efs1 to efs1.emmc.win and /efs2 to efs2.emmc.win, which is fine. However, while restoring (and here is when the bug comes in), it restores efs1.emmc.win to /efs1 but restores the same backup of efs1.emmc.win to /efs2 as well (which it shouldn't be doing and instead it should be restoring the corresponding efs2emmc.win to /efs2). This can brick your phone. Hence, the fatal bug.
This version, however, supports Android Nougat 7.0's encryption. Therefore, as long as you don't backup/restore EFS with this version, you should be good using it with either Android Marshmallow 6.0.1 or Android Nougat 7.0, encrypted or unencrypted.
3. TWRP 3.0.2-2: Is not stable and has a known bug (with the EFS bug most likely fixed in this version, but this is unconfirmed since there is no changelog available yet). The bug would affect those who are backing up their data using this version. TWRP creates the backups of your selected partitions as tar files. The bug that is present in this version would give you an error (most likely the one that @stankyou got) as it is unable to write the second tar file after processing approximately 1 GB of data and would cancel the backup. Hence, the bug.
This version, however, also supports Android Nougat 7.0's encryption. Therefore, as long as you don't create backups with this version, you should be good using it with either Android Marshmallow 6.0.1 or Android Nougat 7.0, encrypted or unencrypted.
4. @jcadduono has created unofficial builds (versions 3.0.2-3) for the Nexus 6P (Angler) and Nexus 5X (Bullhead) without the broken patches. They are up-to-date, but have the adb backup patches rebased out until the bugs are solved. These builds are untested, and he recommends sticking with 3.0.2-0 instead for the time being.
Click to expand...
Click to collapse
TL;DR 3.0.2-0 doesn't support Nougat encryption. 3.0.2-1 has bug restoring EFS. 3.0.2-2 has bug creating backups over 1GB.
ADB sideload is not working in TWRP 3.0.2-3 (twrp-3.0.2-3-angler.img - MD5 2fcc19da388ab727aac69b6165ac7888), not sure if this is @jcadduono or not. It's working in previous build IIRC. Is this expected? Thank you.
vibranze said:
ADB sideload is not working in TWRP 3.0.2-3 (twrp-3.0.2-3-angler.img - MD5 2fcc19da388ab727aac69b6165ac7888), not sure if this is @jcadduono or not. It's working in previous build IIRC. Is this expected? Thank you.
Click to expand...
Click to collapse
I had a few failures with it in TWRP, yes.
Until fixed, you'll have to do ADB push instead and then load from TWRP install.
Alternately, you can do fastboot flash commands while in the bootloader.
Grospolina said:
I've installed the one from the main thread and it's working for me.
I just wanted to mention what the bugs are:
TL;DR 3.0.2-0 doesn't support Nougat encryption. 3.0.2-1 has bug restoring EFS. 3.0.2-2 has bug creating backups over 1GB.
Click to expand...
Click to collapse
I noticed that bug yesterday restoring a backup. TWRP appeared to hang whilst restoring, I left it a further five minutes, then hard reset the power button. When the phone loaded up, I found it had restored correctly.
3.0.2-4 twrp ?
Anybody have the capabilities to roll the 3.0.2-3 version in with The Flash's 3.0.2-0_F2FS version lol; and make a version compatible with Nougat encryption as well as F2FS (and without EMS restore problem, nor backup error issue) ?
I know I sure don't, and now that I'm on christmas break I am just sitting around - in fact if anybody could point me to a resource, I have the time and I'm sure I could pick it up quick, I could try and compile it! I've been wanting to give back to this great community since I joined; maybe now that I've done a couple years of engineering school and been searching thru the forums, I can help throw this together.
I'm going to assume that I look up those two builds sources on GitHub, then use Parallels Windows to use a Linux distro (because I'm on a Macbook Pro) to combine the sources and make a build? Honestly, if I could get any advice, I'd love to jump on it.
3.0.3.0 is out. Anyone know the changelog ?
Here's the link: https://dl.twrp.me/angler/twrp-3.0.3-0-angler.img.html
Would be nice to know a changelog
ariefabuzaky said:
3.0.3.0 is out. Anyone know the changelog ?
Click to expand...
Click to collapse
Unfortunately, the answer is here. I did not expect to see a nag screen after making a backup!
bkkzak said:
Here's the link: https://dl.twrp.me/angler/twrp-3.0.3-0-angler.img.html
Would be nice to know a changelog
Click to expand...
Click to collapse
You can always look at their repository
Since 2016-09-01:
- Change version to 3.0.3 to support the app release - 27 hours ago
- Update Ukraine language translation (via jemmini) - 27 hours ago
- Add TWRP app install via TWRP recovery - 29 hours ago
- TWRP Language Update - 7 days ago
- Change handling of /cache due to AB devices not having cache - 7 days ago
- Support backup/restore of FBE policies - 8 days ago
- Support File Based Encryption - 10 days ago
- Add boot slot support - 12 days ago
- Support new AB OTA zips - 12 days ago
- Copy Kernel Logs - 5 months ago
- Improve backup & wipe exclusion handling - 2 weeks ago
- Fix adb shell in 7.0 tree - 6 weeks ago
- Check if mount point is dir during startup - 6 weeks ago
- MD5 verification sanity - 8 weeks ago
- Fix image flashing: attempt 2 - 8 weeks ago
- Fix image flashing - 3 months ago
- Update to android-7.1 - 4 weeks ago
- Fix libcrypto dependency in 6.0 trees - 3 months ago
- Clean up PartitionSettings - 3 months ago
- Fix compressed backups with split archives - 3 months ago
- Fix restore of subpartitions - 4 months ago
Unfortunately for me, I still have issues decrypting an encrypted phone on TWRP 3.0.2-3 and 3.0.3-0. TWRP prompts for a password and won't take my PIN.
Running the latest ResurrectionRemix (CM-based), which enables device encryption. I'm still searching around to see what I need to do about this.
Edit: Update: Huh, weird, got it to mount.
I rebooted back into Android, went in to Security and set a device encryption password with "Change encryption password".
I hadn't set one before. It requests my screen lock PIN then to enter an alphanumeric encryption password.
Attempted to remove it again immediately (it doesn't show any feedback when I tap "Replace encryption password" then enter my screen lock PIN), and rebooted into recovery.
TWRP prompted again for an encryption password but now accepts my device lock PIN and it mounts!
Rebooted again, and now the phone requests a PIN unlock during boot >.<
Went back in to Security and went straight to "Replace encryption password", entered my PIN, and saw no feedback again. Rebooted back into Recovery.
TWRP prompts again but accepts my PIN. Rebooting to Android again, I am prompted again on boot to enter my screen PIN to finish the boot process. Sooo now I guess I have to figure out how to disable the device encryption PIN, or something. Oh well. I'll update if I make progress.
The end goal is to reach a point where TWRP will mount (even if it's manually with an entered PIN), and to not have a phone that requires a PIN unlock during boot. But I guess that's still safer and I can live with it. It's just different from how the ROM originally behaved, is all.
Edit: Update again!
Disabled my PIN/security altogether, rebooted into recovery. TWRP mounts without any prompts. Nice. Reboot int system, it boots fine. Also nice.
Set a new screen lock PIN, do not select to use it on bootup, and set my fingerprints again. Apps work immediately fine after, I did not have to reset them to use that auth method. Woot, nice.
Restart into TWRP, no prompt, good. Restart into System again, no prompt during boot.
So I guess in the end you have to disable and re-enable device screen locking security if you hit this issue in TWRP on a 6P? It could be my ROM as well.
CaptShaft said:
Hello folks!
Apparently the official TWRP recovery 3.0.2 has some sort of problems with android 7.1.1 Nougat, so this unofficial recovery was created to work around those issues in the meantime.
The official hosting of this unofficial recovery is in this thread: http://forum.xda-developers.com/nex...recovery-twrp-2-8-7-0-touch-recovery-t3234976
It is buried almost all the way at the end.
For sake of convenience, I am making it available here for those that wish to get going with it quickly. Note that I am not the developer of this nor am I the maintainer. This is here for easy reference only. You should speak with TWRP Grand Poobah Dees_Troy in the above thread for further details.
twrp-3.0.2-3-angler.zip 14.2 MB
https://mega.nz/#!tdcUAa4a!G-bGMWznEUAkE3Ih3ioaHq2Fx0NdzGnIlhY-nuPg__s
Installation instructions are straightforward:
1. Decompress the zip file so you have the .img file. Do not flash the zip file!
2. Place the recovery image in the same folder as your ADB / fastboot apps.
3. Put your phone in boot loader mode: Power button + volume down button.
4. Pull open a console in this directory and type fastboot devices. Proceed when you a serial number and "fastboot" next to it.
5. Type fastboot flash recovery twrp-3.0.2-3-angler.img. If all goes well you should see a success message of some sort.
6. Reboot and enjoy!
I've been using this for a few ROM installs already and haven't seen any problems.
Best of luck to you!
Click to expand...
Click to collapse
tu 2: is that recovery image the same as under point one? and where is the ADB /fastbootfolder? these not exist
This is basically a copy of my Z380M TWRP thread adopted for the ZenPad 10. I decided to start a new one since the OP of justshaun's original recovery/rooting thread has gone stale, even as I had posted several new releases of TWRP over the months. Its instructions are also a little outdated. I've also compiled a version for the new Z301M(F) models and needed a place to post it. This is where I will be posting TWRP updates from now on.
In addition to this thread, referring to the Z380M TWRP thread and the original Z300M thread (links above) may be helpful. These models share the same hardware and software base, so most things that apply to one tablet also apply to the others.
DISCLAIMER
As usual, you do anything described in this post at your own risk. No one but you is responsible for any data loss, bricking or damage of your device.
REQUIREMENTS
Windows or Linux PC
SP Flash Tool version 5.1532 (only this version will bypass security checks)
MediaTek VCOM drivers (available through Windows Update)
ZenPad 10 scatter file for SPFT, attached (choose the one for your tablet)
Recovery image, attached (choose the one for your tablet)
ZenPad Z300M, Z301M or Z301MF tablet upgraded to Android N
This won't be a guide on how to use SP Flash Tool. There are plenty of good guides out there like this one on how to set up drivers, load scatter files, flash and make backups with SP Flash Tool. If you're not familiar with this software or how to flash MediaTek devices in general, please do your research before attempting this. I will just get straight to the specifics about the ZenPad 10.
FIRST TIME INSTALLATION
For a locked bootloader:
At this point you should have your tablet powered off, the drivers installed, all of your data backed up, and SP Flash Tool v5.1532's Download tab open and loaded with the tablet's scatter file. Open the download agent file DA_PL.bin, replacing the default MTK_AllInOne_DA.bin. (You can use the AllInOne DA if you want, but the procedure involves extra steps as described below.) Load the extracted TWRP recovery image for your device (twrp-3.2.1-0-z30*m.img) under the recovery partition line in the partition table. Click the Download button inside SPFT. Now just connect the USB cable to your tablet and your computer's USB port. It should start the download process automatically and disconnect when finished.
Alternative Method:
If you're using MTK_AllInOne_DA.bin, you have to hold the Volume Up key as you insert the cable, which puts the device into an emergency download mode. In addition, you will need to have the stock preloader*.bin file loaded inside SPFT for it to be able to communicate with your tablet. The preloader is available inside the official zip file download. Do not flash the preloader (untick the box) or any partitions other than recovery. You just need to have a valid bin file selected under the Preloader line.
For an unlocked bootloader:
If you have used the Asus unlock tool to unlock your device, you will still not be able to use fastboot flash to install a custom recovery. However, you can do a "hot boot" or a tethered boot of TWRP. This method doesn't require SP Flash Tool. Download the TWRP image, put your tablet in fastboot mode and connect to PC. Then run this command to boot TWRP dynamically:
fastboot boot twrp-3.2.1-0-z30*m.img
Once inside TWRP, flash twrp-3.2.1-0-z30*m.img to Recovery using Install -> Install Image. Then reboot to recovery. You may be able to use TWRP in the tethered boot mode, but that could result in glitches due to different parameters passed by the bootloader to the kernel. That's why flashing is recommended.
To update from your installed TWRP version to a new one, just transfer the image to your tablet, then boot to TWRP and install it by going to Install -> Install Image and flashing to Recovery.
START RECOVERY
With the tablet powered off, hold the Volume Up and Power keys together until you get to a menu where you can select "recovery". On the Z301M/Z301MF, that option is labeled Factory Reset. Use Vol. Up to scroll and Vol. Dn to select. If you have a locked bootloader, it will show a Yellow State message because the recovery is not signed by the OEM. Just press volume up to boot it. On the welcome screen of TWRP it will ask you about modifying the system partition, I suggest you go with Keep System Read-only. Doing otherwise will complicate your OTA updates.
WARNING: Never start the stock recovery from the bootloader menu on this device. It is programmed by the bootloader to instantly wipe your data without any warning. Also, be aware that Android installs the stock recovery at every normal boot cycle. So you either have to flash the TWRP every time you want to run it, or disable the automatic recovery installation in the stock firmware. Any kind of mod to the boot image will prevent the automatic recovery installation. If you're not sure which recovery you have installed, you can always do a 'adb reboot recovery' from Android without risk of data loss.
WARNING 2: Make sure you use the correct scatter file for your device (i.e. don't mix up the Z300 and Z301 files). For the initial flash, there is no check for scatter file correctness. If you use the wrong one, SP Flash Tool will alter and lock your GPT to that scatter file layout, possibly bricking your device. It will not be easy to restore it. Flashing with the correct scatter file later on will not work because Flash Tool will not allow you to use a different file than the one you used initially.
What works: Basically everything... access to major partitions, decrypted userdata partition, decrypted adoptable storage, external SD card, ADB, USB-OTG, touch interface, splash screen, installing stock Asus OTA/web FW updates
What doesn't work: (no known problems yet, but please report any)
Not guaranteed to work: factory reset
DOWNLOAD
SP Flash Tool v5.1532
Z300M Scatter file for all storage sizes (right click, Save link as...) -- do not use for other models
Z300M TWRP 3.2.1-0 image -- updated March 15, 2018
Z301M(F) series Scatter file for all storage sizes (right click, Save link as...) -- do not use for Z300M or other devices
Z301M TWRP 3.2.1-0 image -- updated March 13, 2018
Z301MF TWRP 3.2.3-0 image -- updated August 29, 2018
Development and experimental files
Source code
P.S. The thanks button doesn't bite.
Heya, thanks for the new thread..
Stupid question(coming from Samsung flashing)
Ive got Zenpad S3 10 P027, is this TRWP not ideal for this?
Currently, have some su (root) issues. Recovery shows Android icon chest with ! and says "No Command"
When running su in Terminal ADB via PC, says command not recognized.
Looks like I need to reflash recovery. When in TRWP (launched via fastboot boot twrp on PC) I flashed stock recovery but had system mounted read only. Could that be the problem?
Bro, I think you need to do some more homework on root, su, dm-verity, mods, etc. and read the instructions more carefully before applying these hacks. You are making a lot of simple mistakes and ending up shooting yourself in the foot for it. I don't think there's anything wrong with the Z500 TWRP. It can handle installing the stock firmware just fine. The problem is elsewhere. The unlock tool also works fine in TWRP as well in my testing.
The No Command screen is normal. That's been answered many times... you need to hold power+vol. up (or down) to get to the menu. There is no way the stock recovery image can be broken and still boot up.
The su thing, IDK what the problem is, but I'm sure if you install Magisk Manager and make your own patched image from your currently installed firmware, and fastboot-boot with it, you will have su functionality. Just like what it says in the unlock tool instructions.
Lastly and most important, never mount system in read-write mode, as I've repeated several times and exactly as it says in the directions:
7. At the TWRP welcome screen, do not select to modify the system partition and touch Keep System Read-only instead. Doing otherwise will render your tablet unbootable.
8. Mount system in TWRP (in read-only mode)
Click to expand...
Click to collapse
The only time you can mount it in read-write mode is when you are absolutely sure you have disabled dm-verity in your boot image.
I've successfully installed TWRP on Z301M using the instructions from the first post, but then I somehow managed to lose the system. Yes, I should have backed up like the OP suggests.
I thought I should be able to reinstall the original firmware downloaded from Asus (e.g. UL-ASUS_P028_1-WW-3.3.12.0-user.zip) but both the 'adb sideload' method and the TWRP failed to install that firmware zip. My device looks bricked. The only thing I can do is to boot into TWRP (I actually need to select Factory Reset on the bootloader screen to get into TWRP). The folder 'system' is empty.
Can anyone suggest what I am doing wrong when trying to restore the Asus firmware?
When I try to sideload the zip, setting TWRP in the sideload mode, the computer begins uploading but after a few seconds gives the message "Total xfer: 0.01x" and stops, while Android errors with "set boot part fail. can not open misc-sd".
When I install the firmware zip from TWRP it also starts installing fine but shortly gives the same error "set boot part fail. can not open misc-sd".
Thanks
@ahacker, first of all, thank you for the feedback on the Z301M platform. You are literally the first person to have said anything about that version of TWRP.
To see the files on system, you first have to mount the system partition. Did you do that? If not, I suggest mounting it read-only. If there was any corruption on it, then reinstalling the firmware should have fixed it. The "misc-sd" errors are normal. Pretty sure they happen on stock recovery too. The stock firmware does not have dm-verity enabled, so letting TWRP modify system to prevent overwriting recovery should not have caused any problems.
At which point did it stop booting? Also, did you use the scatter file from first post? And can you tell me if the touch screen works fine in TWRP on your tablet?
I'm not sure what the deal is with adb sideload. I don't think I've ever actually tried it....
diplomatic, thanks for replying!
diplomatic said:
[MENTION=4776997]
To see the files on system, you first have to mount the system partition. Did you do that?
Click to expand...
Click to collapse
I do mount the system partition. It appears empty. When I reboot into system TWRP says that the OS is not installed.
I don't remember the details of how I lost the system partition. First time I entered into TWRP it asked for a password, probably to mount some partition. I pressed cancel or something. Then I might have cleaned the caches. But I am sure I haven't wiped system. I might have pressed Factory Reset somewhere, because I don't have any data yet on the new tablet.
I would indeed try to mount the system read only. This is not the first Android system I rooted (maybe fifth), and I was always able to restore the system either from sideload or recovery. But here it seems Asus is making us jump extra hoops to do that.
diplomatic said:
[MENTION=4776997]
Reinstalling the firmware should have fixed it.
Click to expand...
Click to collapse
That seems to be my main problem now. I cannot reinstall the Asus firmware. It may look like I might be installing a wrong version, but I am positive that I have Z301M tablet. This is what I bought and what the boot-loader says. I download Z301M firmware from the Asus website (e.g.). So it must be a correct firmware.
diplomatic said:
[MENTION=4776997]
The "misc-sd" errors are normal. Pretty sure they happen on stock recovery too. The stock firmware does not have dm-verity enabled, so letting TWRP modify system to prevent overwriting recovery should not have caused any problems.
Click to expand...
Click to collapse
Thank you for the information.
diplomatic said:
[MENTION=4776997]
Also, did you use the scatter file from first post? Does the touch screen work fine in TWRP on that tablet?
Click to expand...
Click to collapse
Yes. I found that to be the only scatter file that worked. I tried scatter.txt from the firmware zip, but the Flash Tool refuses tio pick it up. TWRP seems to be working fine with touches working as expected.
diplomatic said:
[MENTION=4776997]
I'm not sure what the deal is with adb sideload. I don't think I've ever actually tried it....
Click to expand...
Click to collapse
This is the unbricking method described here. It probably does the same thing as the "Install Zip" from recovery, because the errors that both methods give are the same.
---------- Post added at 01:19 AM ---------- Previous post was at 12:57 AM ----------
Now system refuses to mount
ahacker said:
I don't remember the details of how I lost the system partition. First time I entered into TWRP it asked for a password, probably to mount some partition. I pressed cancel or something. Then I might have cleaned the caches. But I am sure I haven't wiped system. I might have pressed Factory Reset somewhere, because I don't have any data yet on the new tablet.
Click to expand...
Click to collapse
Er, the password should have been for decrypting your userdata. If you didn't have one set up, there might be something wrong there.... Or possibly just unformatted.
ahacker said:
That seems to be my main problem now. I cannot reinstall the Asus firmware. It may look like I might be installing a wrong version, but I am positive that I have Z301M tablet. This is what I bought and what the boot-loader says. I download Z301M firmware from the Asus website (e.g.). So it must be a correct firmware.
Click to expand...
Click to collapse
Yeah, that has to be the right one. The installation script has to match the model name reported by the recovery. Otherwise it would simply abort.
ahacker said:
Yes. I found that to be the only scatter file that worked. I tried scatter.txt from the firmware zip, but the Flash Tool refuses tio pick it up. TWRP seems to be working fine with touches working as expected.
Click to expand...
Click to collapse
Great! Guess my kernel patch was on the dot and the partition layout has not changed from the Z300.
ahacker said:
This is the unbricking method described here. It probably does the same thing as the "Install Zip" from recovery, because the errors that both methods give are the same.
Click to expand...
Click to collapse
When you installed the zip, did you unmount system completely? BTW, when you mentioned the errors, the installation does keep going for like 5 to 10 minutes afterwards, right?
If you still can't resurrect it, please post or send me the recovery & kernel log that has your installation attempt.
diplomatic said:
When you installed the zip, did you unmount system completely? BTW, when you mentioned the errors, the installation does keep going for like 5 to 10 minutes afterwards, right?
Click to expand...
Click to collapse
I've tried both ways, with and without system mounted, a few times. The installation would fail after something like 5 seconds.
diplomatic said:
If you still can't resurrect it, please post or send me the recovery & kernel log that has your installation attempt.
Click to expand...
Click to collapse
I think I am giving up on this cheap tablet. I cannot even format it in the Flash Tool: it says "To format code area is forbidden on this phone". Asus is forbidding too much for me to ever buy it again. Attached the logs.
Thanks, diplomatic
OK, found the problem. Check your PMs, ahacker.
diplomatic said:
OK, found the problem. Check your PMs, ahacker.
Click to expand...
Click to collapse
I have replied (twice), but the reply does not appear in my Sent Items. I hope it has reached you. If not, I'll paste the reply here, if you don't mind.
i not understand... i have Asus ZenPad 10 LTE Z301MFL.. a root method has been released ???
@diplomatic
Would this be compatible with Z0310M ? can't find anything for this damn model...
Hi, NeBouse,
Are you sure you have the correct information? It looks like just a misspelling of Z301M, aka P028....
I have z301m.
One thing that was a surprise for me is that the TWRP recovery flashed with the method described in the original post does not stick. You have to flash it each time you use it. If you are like me this information is important, because the original recovery plainly wipes your data without asking or warning.
After you have flashed TWRP on the device, to go to the recovery mode you have to chose "Factory Reset" in the bootloader. Then it will complain about wrong OS, which is the sign that flashing TWRP worked; choose 'yes'. The first thing you should do in TWRP is a ful nandroid backup. (Not listening the OP's advice about backing up when Installing TWRP with a wrong scatter file almost cost me the device. Thankfully diplomatic managed to remotely fix my problem, probably spending a lot of his personal time. The scatter file in the original post is a correct one now.)
Creating a nandroid backup in TWRP takes unusually long time, I even once decided that it hanged. Taking long time, like 10-30 minutes, for a full backup is normal.
Asus Z300M , Magisk 16.3 (beta) and FW 5.3.19 WW now works!
z301m, WW-3.3.12.0 firmware
For rooting I've installed in TWRP Magisk v15.3 (diplomatic warned against 16.x, someone else against 15.4) - link.
Installed in TWRP xPosed framework 88.2 - link, and xPosed Installer apk from within Android - link.
So far, so good.
What I've found is that TWRP seems to have problems with external sd cards (lots of fs corruption). I found it safer to unmount by hand by unticking the sd card checkbox in "Mount". Not very conclusive about this though.
Thanks, ahacker. Good feedback. Although to be fair, I didn't say to avoid Magisk 16.x. I said 16.0. I'm pretty sure whatever bug it had is already fixed in the latest version.
Now that you've installed root, TWRP will stick around on the emmc. The stock recovery only gets installed if you have the original unpatched boot image on it. I mean, this is not unique to these devices. That's been standard Android functionality since some 4.x or 5.x version. And this is essentially what's in the warning on the OP.
The backup I'm talking about in the installation method is done with the SP Flash Tool readback function. That will pull the partition tables and your device's "metadata" that's unique to your unit. I don't think nandroid covers that...
Oh, and what is this SD corruption you're talking about? What file system is it formatted in? Have you checked your card for errors in Windows?
Asus releases so many difference Z301M model, so I am curious if this also works on Z301MF model?
Notice Z300MF has the MTK8163BA (or MTK8163A?) CPU model while Z301M uses : 8163B
Anyone tested that already? Thanks.
my zenpad 10 has frp lock. it this a solution to remove the frp lock?
Pls help how i flash original software via fastboot ?????
Hey there,
it seems like it's a very bad day for me. After some problems with my psyche, which is nothing new, i decided to flash a new ROM. This is what always makes me happy, try out new features and just messing arround with the system. Turns out, today i messed to much but i think it shouldn't... Here's what i did and happend (coming from RR 7.0):
-downloaded Superior OS from https://forum.xda-developers.com/lg-v30/development/post-t3909765
-downloaded the GAPPS package (first time with AROMA)
-moved both files to the SD-Card
-backed up my data, wiped system, dalvik, cache, data, internal storage
-installed the Superior OS zip
-installed the GAPPS zip
This is where it all got messy. The zip didn't finished, it stopped after 2 seconds and the H930 rebooted directly to recovery. There was no screen with the LG standard boot screen, it went straight to recovery. I rewiped everything and i got an error message which said: can't wipe data partition because device or resource is busy. I tried to repair it via wipe > advanced > selecting data > change or repair filesystem and tried to resize, repair and change file system. it always returns the error that it can't mount the partition. After the script, TWRP returns script succeeded, but fails to mount /data.
If i try to install RR 7.0, the script returns E3004: This package is for device : v30,joan,h930; this device is .
After all, i can't restore the backup i had from AOSP extended. I tried to flash the following two files TWRP-JOAN_H930_OPEN_EU-21w.zip and H93020R(TWRP).zip which started with the error E: Legacy property environment did not initialize succesfully. Properties may not be detected.
TWRP Version: 3.2.3-7
I would appreciate any help on this topic, even if i'm one of the xda profits who don't really gives a thank to the threads an just tries out until my devices work as i want them to do (i'm just honest). It's not because i don't appreciate the work of the dev's, they do really nice work which deffinetly is too much for myself to do. I'm just a messy person when it comes to interpersonal relationships. I'm sorry for my kind of awkward english, that's how i am...
I don't have a lot of knowledge about programming itself but i know how to use adb and fastboot, since i had some issues with my HTC one M7 on which i wasn't able to restore the IMEI due to too much messing arround. I think i started a thread about it, but i got it replaced even with a custom rom installed for free which will be my driver for the next couple days.
Kind regards
mrstupidus
I'm still new to this phone but, can you use LGUP to reinstall stock. Then just start over.
Sent from my LG-US998 using Tapatalk
Thanks for the reply,
i would if I could access download mode (forgot to mention it), seems like i'm not able to since the device only boots to recovery, the LG V30 bootscreen never shows up.
It seems like my device data is corrupted or lost, since different scripts in TWRP report that I have no device number. Also if I shut down the device trough TWRP, it boots to TWRP again and makes no attempt to shut down. I haven't tried to access download mode, I had to go to bed for work today. I still have to go tomorrow but one night without sleep will be worth it.
As far as I remember I have a backup of my EFS lying around, I will try to flash it this evening. I'll keep you guys updated if I find a way to get my v30 working, since it could help others too.
Regards
mrstupidus
mrstupidus said:
Thanks for the reply,
i would if I could access download mode (forgot to mention it), seems like i'm not able to since the device only boots to recovery, the LG V30 bootscreen never shows up.
It seems like my device data is corrupted or lost, since different scripts in TWRP report that I have no device number. Also if I shut down the device trough TWRP, it boots to TWRP again and makes no attempt to shut down. I haven't tried to access download mode, I had to go to bed for work today. I still have to go tomorrow but one night without sleep will be worth it.
As far as I remember I have a backup of my EFS lying around, I will try to flash it this evening. I'll keep you guys updated if I find a way to get my v30 working, since it could help others too.
Regards
mrstupidus
Click to expand...
Click to collapse
Have you tried going into download mode manually with the hardware buttons?
Press and hold the Volume Up key on your LG V30.
While still holding this button connect your phone to the USB cord on your computer.
The download mode should now be displayed on your device.
You can release the Volume Up key and resume the update / downgrade operation.
Click to expand...
Click to collapse
You are going to have to have to flash boot and system via fastboot:
* Download the ROM you want to flash and extract it. It will have boot.img or boot.image ... boot.something (depends on the ROM), and system.SOMETHING.
* Open an elevated command prompt in the directory you extracted the ROM in.
* From TWRP choose reboot / bootloader. If it wants to be a PITA and reboot back to TWRP, then you will have to wait till the phone dies and then use the vol down + plug in the USB cable method
* In the command prompt type:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot boot boot.img
Obviously replace boot.img and system.img with the names of the boot and system files.
To solve your /data issue (and you might want to do this first actually):
While in TWRP
Code:
adb shell
umount /data
umount /sdcard
mkfs.ext2 /dev/block/bootdevice/by-name/userdata
Repeat those two umount, and that is umount NOT unmount, until you get an error. If it isn't unmounted, when you try to format it, mkfs.ext2 will throw an error.
-- Brian
runningnak3d said:
You are going to have to have to flash boot and system via fastboot:
* Download the ROM you want to flash and extract it. It will have boot.img or boot.image ... boot.something (depends on the ROM), and system.SOMETHING.
* Open an elevated command prompt in the directory you extracted the ROM in.
* From TWRP choose reboot / bootloader. If it wants to be a PITA and reboot back to TWRP, then you will have to wait till the phone dies and then use the vol down + plug in the USB cable method
* In the command prompt type:
Code:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot boot boot.img
Obviously replace boot.img and system.img with the names of the boot and system files.
To solve your /data issue (and you might want to do this first actually):
While in TWRP
Code:
Code:
adb shell
umount /data
umount /sdcard
mkfs.ext2 /dev/block/bootdevice/by-name/userdata
Repeat those two umount, and that is umount NOT unmount, until you get an error. If it isn't unmounted, when you try to format it, mkfs.ext2 will throw an error.
-- Brian
Click to expand...
Click to collapse
Thank's a lot for you're efforts, it turned out that i didn't needed to flash the system.img and boot.img
ChazzMatt said:
Have you tried going into download mode manually with the hardware buttons?
Click to expand...
Click to collapse
Thanks a lot too for you're effort's, this really helped me out in a unecpected way
So here's what the issue was: a corrupted Gapps package. It failed to install and was still active in the recovery while the recovery "rebooted" (it just flashed off and started again with no normal boot between, kind of awkward to explain). The Phone itself never really rebooted into recovery, i have no idea how that happened. The /data partition was still in use from the Gapps script, but the script wasn't visible anymore and i was able to use the recovery as normal. So i ended up with an error everytime i tried to install a zip, restore a backup or wiping the /data partition.
Something i forgot yesterday in the spiral my mind was, forcing the phone to shut down via holding the power and volume down button. I then booted to recovery and i was able to wipe the /data partition. I then tried to install RR and the script suceeded with no error, then the Gapps package with AROMA and i was at the same point as yesterday. So forcing the phone to shut down and back to installing RR now without Gapps. I'm now going to install a .KDZ to start from the original firmware, so i can update the whole firmware and then moving on to unlock the bootloader and install TWRP and a rom with the working Gapps package i have
Thank's a lot for the help
Regards Simon
PS: I hope i will be more focused the next time i encounter issues with my phone and myself, this thread probably put's me in the place i deserve :silly:
That's crazy, I made the exact same mistake you did just now and I was just about stumped on what to do.
Thanks for saving me from a small panic attack, the Power + Vol (-) did the trick.
i tried to convert my sprint v30 to h930 and worked but since i didnt get signal decided to convert to us998 but know it dosent relock the bootloader and when i reflash our restore it gets to setup menú and reboot… i can enter download,fastboot and recovery but dont seem to stop it from rebooting..i dindt want to start a new thread.help please
dami00976 said:
i tried to convert my sprint v30 to h930 and worked but since i didnt get signal decided to convert to us998 but know it dosent relock the bootloader and when i reflash our restore it gets to setup menú and reboot… i can enter download,fastboot and recovery but dont seem to stop it from rebooting..i dindt want to start a new thread.help please
Click to expand...
Click to collapse
It'd be better if you provided the roms and versions you were using.
In between tho, try flashing the last US998 rom you used again but in refurbish mode instead of DL. I had an almost similar bootlooping issue last night and 2nd refurb flash got it to stop.
dami00976 said:
i tried to convert my sprint v30 to h930 and worked but since i didnt get signal decided to convert to us998 but know it dosent relock the bootloader and when i reflash our restore it gets to setup menú and reboot… i can enter download,fastboot and recovery but dont seem to stop it from rebooting..i dindt want to start a new thread.help please
Click to expand...
Click to collapse
Why would you try to convert LS998 to H930? North America variant should only be cross flashed to other North America variants, when using LGUP. Through LGUP, you can't completely Frankenstein a North American phone to a non-North American phone and at the worst you will have a brick.
You need to read the Frankenstein instructions on how to convert LS998 to US998. You either didn't flash US998 Nougat first or you didn't do the Master Reset step in between Nougat and Oreo:
ChazzMatt said:
FRANKENSTEIN - CONVERTING ANY NORTH AMERICA V30/V30+ (except T-mobile H932) TO US998 OREO
SHORT VERSION:
1) Go into download mode (power off completely, then hold volume up button while plugging in USB cable)
2) THEN open patched LGUP and flash NOUGAT US998 to DL PARTITION. In the pop up box "Select All". Use the attached patched LGUP in this post.
3) Master Reset (post 101)
4) Flash Oreo US998 in LGUP UPGRADE MODE. (Make SURE you are choosing Oreo US998 and not accidentally re-flashing Nougat US998 again!)
(For bootloader unlock purposes, use the US998 KDZ versions with pre-July 2018 security patch: 20a or 20b. You can always update to newer US998 firmware later, AFTER bootloader is unlocked.)
5) DONE.
NOTE: For Canadian H933 to convert to US998, @cre4per says you have to use DL Partition for both stages (Nougat and Oreo KDZ)
Click to expand...
Click to collapse
Those instructions work for all North American variants -- except T-mobile H932 -- but were written specifically with screenshots while me personally doing Sprint LS998.
________
neocyke said:
In between tho, try flashing the last US998 rom you used again but in refurbish mode instead of DL. I had an almost similar bootlooping issue last night and 2nd refurb flash got it to stop.
Click to expand...
Click to collapse
Refurbish has its uses. But to be honest I think you just didn't follow the Frankenstein directions. Master Reset stabilizes the bootlooping when flashing US998 Nougat before then flashing US998 Oreo. Has worked for everyone for over a year.
Unless the phone you got which you said was already Chinese Frankensteined was messed up due to whatever they did to it.
ChazzMatt said:
Refurbish has its uses. But to be honest I think you just didn't follow the Frankenstein directions. Master Reset stabilizes the bootlooping when flashing US998 Nougat before then flashing US998 Oreo. Has worked for everyone for over a year.
Unless the phone you got which you said was already Chinese Frankensteined was messed up due to whatever they did to it.
Click to expand...
Click to collapse
Honestly, i gots no idea how they did it and didn't really care at that point. Just needed to get the phone working again.
I actually did the master reset. Several times in fact. Never worked once. Longest it'd hold is for me to input wifi pw. It was the only other thing i could get to other than download mode.. I got the refurb step from either this or the WTF thread. Someone else had the same problem and refurb was their fix. Just so happens same for mine.. So, yeah..
I figured it out,but bricked that one lucky I have a spare and I didn't brick that one....but it wasn't de lg up our software. Through the process of reverting electricity went off in the process of flash and now is on black screen oh well
Is there a way to fix the bricked LG v30?
I have a weird issue. Not sure whats going on. Tab S3 is on Android 7.0. I'M running the stock rom but had rooted and installed twrp many months ago. Disabled updates on the device. For some reason yesterday it rebooted and now boots to a screen citing ( Security Error: This device has been flashed with unauthorized software & is locked. Call your mobile operator for additional support. " There is another small message on top , "Custom binary blocked by FRP. (boot.img). I did not change any OEM unlocking toggle. I'm the only one who uses the tablet so no one else did either. Any Ideas ? It does not let me boot to recovery, I cant turn the device off either it just keeps rebooting. The only screen i can get to successfully is download mode.
From some basic ideas I'm thinking maybe flash twrp again in odin and try to flash magisk again or the no-verity-opt-encrypt-6.0 file to see if it will boot up. I want to recover the device without formatting everything but if no one has nay ideas i guess I will try re-flashing the current firmware again to stock. I still have the odin files for the current firmware.
Don't panic, I had this too after upgrading the bootloader. I thougt it was soft-bricked...
- Flash a legit Samsung update with Odin
- The trick of the seven days (read further)
- Flash TWRP with Odin
- IMMEDIATELY reboot in recovery
If you use a custom ROM do as usual
- Delete DATA, wipe everything
- Flash custom ROM AND Magisk
If you want to keep Samsung OS and TWRP without Magisk, I believe you need to
- Flash a dm-verity patch.
Hope you have backup eveything as I did...
The option to disable OEM lock disappear from developper menu, even if it is activated. It seems you have to wait for seven days before the option show up again. During this time you're enable to use a custom ROM or a custom RECOVERY.
- Disable time by network
- Set date 8 days in the past
- Do a manual check update
- Reboot
- Set the actual date
- Check for updates again
Now the OEM option is present, now you can do what you want.
You're right but there's new security zip to flash together with dm-verity patch it is RMM bypass. https://forum.xda-developers.com/galaxy-a8-2018/samsung-galaxy-a8-2018-guides-news--discussion/guide-root-install-twrp-samsung-january-t3760975 .
Note: After flashing both files Data format is necessary not data wipe/factory reset.
I have similar security issues weeks back.
Tips?
samsuffit said:
Don't panic, I had this too after upgrading the bootloader. I thougt it was soft-bricked...
- Flash a legit Samsung update with Odin
- The trick of the seven days (read further)
- Flash TWRP with Odin
- IMMEDIATELY reboot in recovery
If you use a custom ROM do as usual
- Delete DATA, wipe everything
- Flash custom ROM AND Magisk
If you want to keep Samsung OS and TWRP without Magisk, I believe you need to
- Flash a dm-verity patch.
Hope you have backup eveything as I did...
The option to disable OEM lock disappear from developper menu, even if it is activated. It seems you have to wait for seven days before the option show up again. During this time you're enable to use a custom ROM or a custom RECOVERY.
- Disable time by network
- Set date 8 days in the past
- Do a manual check update
- Reboot
- Set the actual date
- Check for updates again
Now the OEM option is present, now you can do what you want.
Click to expand...
Click to collapse
Geoz said:
You're right but there's new security zip to flash together with dm-verity patch it is RMM bypass. https://forum.xda-developers.com/galaxy-a8-2018/samsung-galaxy-a8-2018-guides-news--discussion/guide-root-install-twrp-samsung-january-t3760975 .
Note: After flashing both files Data format is necessary not data wipe/factory reset.
I have similar security issues weeks back.
Click to expand...
Click to collapse
I still had the odin files from when i first rooted this. I flashed the same files ( BL, AP, HOME_CSC ). Device booted back up with all data intact but now the device is no longer rooted. Any way to root without losing data again ( Ex. Factory reset). I had to re-enable OEM Unlock even though i never disabled it don't know what happened there. Also device is still on Android 7.0
naruto.ninjakid said:
I still had the odin files from when i first rooted this. I flashed the same files ( BL, AP, HOME_CSC ). Device booted back up with all data intact but now the device is no longer rooted. Any way to root without losing data again ( Ex. Factory reset). I had to re-enable OEM Unlock even though i never disabled it don't know what happened there. Also device is still on Android 7.0
Click to expand...
Click to collapse
To root you may need to flash magisk with TWRP, I don't know if there's any other way.
If TWRP you have to format data after flashing security files so everything including internal storage will be wiped.
Hi guys, dealing with a H933 --> US998.
TL;DR - stuck on LG logo, no download mode, no fastboot, master reset does not work, LGUP (patched or unpatched) doesn't recognize phone, computer doesn't recognize it either.
----
Frankenstein method followed correctly, and had unlocked bootloader + root.
Followed H933 specific steps to install AOSP/Linage ROMS. Attempted to install Lineage 16.0 and flashed Lunar kernel. Booted to animation logo and didn't get past that.
Decided to revert back to stock Pie by flashing one of the US998 kdz's. To be honest with you, I tried a few different ones and everything was working fine (I went from Nougat --> Oreo --> Pie in order to bring myself back to Pie firmware to try Lineage install once more but with stock kernel).
This time, phone wouldn't move past the LG animation (right after the logo).
At this point, I lost access to download mode - but I still had fastboot. Installed TWRP again through fastboot and attempted to flash TWRP-JOAN_H933_CANADA_20i.
Lost unlocked bootloader image - lost access to fastboot and recovery - and still didn't have download mode (it would not pass the original download mode image) and would not be recognized by LGUP (patched or unpatched). The phone would be stuck at LG logo, and keep rebooting.
At that point I decided to try a Master Reset. On the second YES, it would hang, and then go back to the LG logo bootloop. Phone does not get recognized by computer.
I know I messed up in numerous points. I got overzealous and likely didn't pay enough attention. Spent all night trying to resurrect it, but to no avail. Any advice for me? Or is the device fully bricked? :crying:
Greatly appreciate any feedback and assistance. Thank you in advance.
Sorry to hear that. I think you have four options.
1) Reach out on the telegram v30 forum to someone with an Octoplus box to remotely resurrect your device.
2) Send it in for "repair".
3) Do it yourself, see https://forum.xda-developers.com/g4/general/guide-unbrick-via-external-sdcard-qfil-t3748946.
4) Buy a new phone.
The third option isn't hard, but may involve a lot of work so I'd go with the first one.
don"t worry too much, that phone is almost unbrickable, at least you are really unlucky, you will revive it. Wait for @ChazzMatt to give you some help before giving up hope entirely
Meanwhile, I can give you some advice because I was stuck one time on LG Logo, you were on which firmware when it last booted up?
While it is bootlooping, connect it to the pc, do a soft reset with power and volume down buttons, release them when the screen goes black and immediately press the volume up button to access fastboot menu, and if PC doesnt recognize it, shut down the phone by selecting it with volume button.
Deconnecting the phone and press volume down while reconnecting it to the pc to try to go to download mode and kdz your phone.
Somewhat working
Hey guys - brief update. I got back to US998 Oreo with bootloader unlocked and root. I tried to upgrade to US998 Pie by flashing US99830b.zip in TWRP following all the steps, and now the phone doesn't boot again and gets stuck on the LG Logo. Download mode shows "Now waiting For Any Connection" and doesn't detect PC. Any idea how to get this to work so I can flash back to US998 Oreo and just stick there?
Update: Flashed US99820H and back in running order. I still wonder how to get my phone onto Pie while keeping bootloader unlocked and have root, without having the phone get stuck.
Ergo-sum said:
Update: Flashed US99820H and back in running order.
Click to expand...
Click to collapse
Glad you got your phone working again!
Ergo-sum said:
I still wonder how to get my phone onto Pie while keeping bootloader unlocked and have root, without having the phone get stuck.
Click to expand...
Click to collapse
Thoroughly discussed in the US998 Pie KDZ thread. Top of post #2 (one method), all of post #6 (three different workarounds).
If none of the 4 methods work for you, there are no other answers and you have to wait for another US998 Pie KDZ.
I've struggle for a couple days and finally i can flash pie stock rom to my us998. What i did :
1.Refurbish us99820h lgup, boot os
2.flash and boot twrp via fastboot
3.flash magisk,dm verity, rctd, via twrp...format data reboot format data then magisk again
4. Boot OS
5. Boot recovery then shutdown
6. Partition DL h93310h lgup except RECOVERY AND RECOVERYBAK
7. Boot OS .... Once your lg logo appeared ( BEFORE LG ANIMATION ) press and hold vol down + power. Release power and hold it again IMMEDIATELY once you see LG LOGO ( BEFORE LG ANIMATION ) click the "yes" and "yes"
8. You got the twrp
9. Flash us99820e + magisk via twrp , boot up
10. Refurbish us99820h, boot up
11. Do step 2 and 3
12. Boot OS
13. Boot recovery
14. Flash us99830b via twrp then flash magisk
15. Done u should have pie now
What you are describing is Method #3 in post #6 of the US998 KDZ Pie thread.
It's the workaround which has the most success but is also most complicated.
havetolearn said:
I've struggle for a couple days and finally i can flash pie stock rom to my us998. What i did :
1.Refurbish us99820h lgup, boot os
2.flash and boot twrp via fastboot
3.flash magisk,dm verity, rctd, via twrp...format data reboot format data then magisk again
4. Boot OS
5. Boot recovery then shutdown
6. Partition DL h93310h lgup except RECOVERY AND RECOVERYBAK
7. Boot OS .... Once your lg logo appeared ( BEFORE LG ANIMATION ) press and hold vol down + power. Release power and hold it again IMMEDIATELY once you see LG LOGO ( BEFORE LG ANIMATION ) click the "yes" and "yes"
8. You got the twrp
9. Flash us99820e + magisk via twrp , boot up
10. Refurbish us99820h, boot up
11. Do step 2 and 3
12. Boot OS
13. Boot recovery
14. Flash us99830b via twrp then flash magisk
15. Done u should have pie now
Click to expand...
Click to collapse
ChazzMatt said:
What you are describing is Method #3 in post #6 of the US998 KDZ Pie thread.
It's the workaround which has the most success but is also most complicated.
Click to expand...
Click to collapse
I heard that i will got many problem if i flash aosp rom after upgrade to pie.... Can i fix it with that method?
havetolearn said:
I heard that i will got many problem if i flash aosp rom after upgrade to pie.... Can i fix it with that method?
Click to expand...
Click to collapse
Yes.
What you are talking about is you can't run LOS-16 ROMs on stock Pie. You have to downgrade back to Oreo, and even then you will forever have to run permissive kernel with Oreo firmware for camera/flashlight to work since you once flashed stock Pie.
You would downgrade to Oreo 20h, flash all those steps (H933 Nougat, etc) and eventually get back to US998 20h and then stay there.
More commentary here about stock Pie:
https://forum.xda-developers.com/showpost.php?p=80876797&postcount=65
ChazzMatt said:
Yes.
What you are talking about is you can't run LOS-16 ROMs on stock Pie. You have to downgrade back to Oreo, and even then you will forever have to run permissive kernel with Oreo firmware for camera/flashlight to work since you once flashed stock Pie.
You would downgrade to Oreo 20h, flash all those steps (H933 Nougat, etc) and eventually get back to US998 20h and then stay there.
More commentary here about stock Pie:
https://forum.xda-developers.com/showpost.php?p=80876797&postcount=65
Click to expand...
Click to collapse
Man there are so many broken oreo's firmware after update to pie.... Hmm, i think i will stay at pie because i need lg screen recording feature. It can record screen and system sound together. Thx for replying ChazzMatt
ChazzMatt said:
Yes.
What you are talking about is you can't run LOS-16 ROMs on stock Pie. You have to downgrade back to Oreo, and even then you will forever have to run permissive kernel with Oreo firmware for camera/flashlight to work since you once flashed stock Pie.
You would downgrade to Oreo 20h, flash all those steps (H933 Nougat, etc) and eventually get back to US998 20h and then stay there.
More commentary here about stock Pie:
https://forum.xda-developers.com/showpost.php?p=80876797&postcount=65
Click to expand...
Click to collapse
Uhh sorry Chazz.. Can you help me? I found my phone have trouble with wifi... Whenever i try to connect it just told me "saved"
havetolearn said:
Uhh sorry Chazz.. Can you help me? I found my phone have trouble with wifi... Whenever i try to connect it just told me "saved"
Click to expand...
Click to collapse
1) On my backup V30+ which is on stock US998 30b Pie (but doesn't have a SIM card inserted nor even signed into my Google account), it's connected fine to my home Wi-Fi network so I know it's not a stock US998 Pie issue...
2) This happens even on public free Wi-Fi networks? (Here in the U.S. we have McDonalds, Starbucks?) That would give you clue whether it's one particular router or all your phone has problem with. Or possibly problem with the type of encryption you have on your router.
Usually that message means the router is rejecting the device. You just have to figure out why. But is it one router or all?
3) If one particular router, try rebooting the Wi-Fi router itself.
4) Make sure you don't have any kind of router whitelist for certain devices or MAC addresses and your phone is not included. Or that you don't have some older b/g Wi-Fi chipset standard set; this one is not likely but I had that happen for an older Wi-Fi printer when I had "N" or higher set on my router.
5) On the phone, try forgetting the Wi-Fi network and refinding it. Enter in the password again.
6) Almost last, on the phone try the Network Settings Reset. (See screenshot from US998 30b Pie.) It will reset all network settings including Wi-Fi, Bluetooth.
7) Last, try Factory Reset?
In the same boat
Ergo-sum said:
Hi guys, dealing with a H933 --> US998.
TL;DR - stuck on LG logo, no download mode, no fastboot, master reset does not work, LGUP (patched or unpatched) doesn't recognize phone, computer doesn't recognize it either.
----
Frankenstein method followed correctly, and had unlocked bootloader + root.
Followed H933 specific steps to install AOSP/Linage ROMS. Attempted to install Lineage 16.0 and flashed Lunar kernel. Booted to animation logo and didn't get past that.
Decided to revert back to stock Pie by flashing one of the US998 kdz's. To be honest with you, I tried a few different ones and everything was working fine (I went from Nougat --> Oreo --> Pie in order to bring myself back to Pie firmware to try Lineage install once more but with stock kernel).
This time, phone wouldn't move past the LG animation (right after the logo).
At this point, I lost access to download mode - but I still had fastboot. Installed TWRP again through fastboot and attempted to flash TWRP-JOAN_H933_CANADA_20i.
Lost unlocked bootloader image - lost access to fastboot and recovery - and still didn't have download mode (it would not pass the original download mode image) and would not be recognized by LGUP (patched or unpatched). The phone would be stuck at LG logo, and keep rebooting.
At that point I decided to try a Master Reset. On the second YES, it would hang, and then go back to the LG logo bootloop. Phone does not get recognized by computer.
I know I messed up in numerous points. I got overzealous and likely didn't pay enough attention. Spent all night trying to resurrect it, but to no avail. Any advice for me? Or is the device fully bricked? :crying:
Greatly appreciate any feedback and assistance. Thank you in advance.
Click to expand...
Click to collapse
How did you unbrick your phone? I'm in the same boat as you. I can get to the Download mode, but not past the blue dot image. If I try to master reset, the phone just restarts after the second time I select yes. It's been bootlooping like this for a while now. For context, I was on US99820H(dirty flashed via twrp) when I tried to flash H93330k. @ChazzMatt, I know this is a long shot as what I did was incredibly stupid, but is there anyway I can get out of this?
Ergo-sum said:
Hey guys - brief update. I got back to US998 Oreo with bootloader unlocked and root. I tried to upgrade to US998 Pie by flashing US99830b.zip in TWRP following all the steps, and now the phone doesn't boot again and gets stuck on the LG Logo. Download mode shows "Now waiting For Any Connection" and doesn't detect PC. Any idea how to get this to work so I can flash back to US998 Oreo and just stick there?
Click to expand...
Click to collapse
But, how did you do that if you cant (couldnt) access to fastboot or recovery? Im crazy ?
please. help me.
Ergo-sum said:
Hey guys - brief update. I got back to US998 Oreo with bootloader unlocked and root. I tried to upgrade to US998 Pie by flashing US99830b.zip in TWRP following all the steps, and now the phone doesn't boot again and gets stuck on the LG Logo. Download mode shows "Now waiting For Any Connection" and doesn't detect PC. Any idea how to get this to work so I can flash back to US998 Oreo and just stick there?
Click to expand...
Click to collapse
Please help me, I am the same as you. please
phamtuyenk7d said:
Please help me, I am the same as you. please
Click to expand...
Click to collapse
See this post for Recovery of botched US998 30B upgrade:
https://forum.xda-developers.com/showpost.php?p=81728547&postcount=641