A while back i unlocked my bootloader and installed TWRP 2.8 (via fastboot) but that was way back ago. Later i tried installing the OTA update via the phone directly which didn't work so i didn't bother as it didn't affect much. But today i was about to install a new rom but i couldn't boot into recovery(booting into recovery via advanced power options, it just didn't work anyway) I thought i might as well reflash recovery using the fastboot method again but when i used fastboot oem unlock command ( I know i used it before i thought i had to do it again im so sorry) it just flashed the one plus logo, vibrated and redid the same thing again and again with no chance of booting.....after using command fastboot continue it booted ! ( God thank you !) but the phone only boots via fastboot continue command I need to get it back to normal !
Also I checked fastboot device info, it said device unlocked and device verified =false ?!
So my BOOTLOADER is locked on its own ? plus recovery isnt available ? AND it doesn't even boot the normal way?
Im really worried now ! please assist me ?
Link used for tutorial : https://forums.oneplus.net/threads/...-custom-recovery-root-efs-backup-more.345478/
Use the usual Qualcomm factory restore to revert everything back to working Lollipop software. From there you can try anything except OxygenOS 3.0 Beta or latest HydrogenOS without having to change to compatible recovery for those bootloaders.
Next time, at least try to use the search function, your case is nothing new and has already been answered many times over since the release of OOS3 beta and HydrogenOS Marshmallow ROM.
Problems with rooting, loading ROM then recovery & download images -some solutions
I started with stock LG v20 T-Mobile H91810P and followed this step by step & the original threads. I loaded the latest stock Oreo from H91820H from here instead of latest Nougat H91810U - Pie & some other versions had too many things not working.
In the process there were a few problems -the major ones are following with solutions, some from here:
1) The file H91810p rom (H91810p_00_0717.kdz) downloaded from here.
2) I lost root several times, but had TWRP. So I used adb sideload like:
Boot/start TWRP and the start ADB Sideload
Download Magisk-v16.0.zip and copy to adb directory.
On Windows PC connect Cell with USB and in CMD window type (copy/paste):
adb start-server
adb sideload "Magisk-v16.0.zip"And never update migisk after installing from above or will lose root. Also no need for SU.
3. Camera did not work and people could not hear me nor could I hear them when I picked up a call - A reboot/restart fixed it.
4. No need to download UPPERCUT (that is hard to download), because LGUP works fine without UPPERCUT.
I have 4 problems remaining -any help for solutions here is appreciated - especially exact type help please:
1) On LAF/Boot (original download) partition: Vol+ & connect to USB caused the download mode to come on for about 2 seconds and then TWRP (however I am glad that TWRP is here) -Prefer this to be the original download mode.
2) On Recovery patition: Vol- & connect to USB causes fastboot to come up. Flashed the recovery-twrp-h918-2018-10-18.img (renamed to recovery.img) to recovery partition using flashify and TWRP unsuccessfully. -Prefer this to be TWRP.
3) TWRP cannot access the Data partition. Rebuilt and reformatted Data from TWRP without success. -Prefer access to Data from TWRP.
4) At boot time: I like to get rid of the warning that my bootloader is unlocked. -I can live with this one.
After thoughts: Now that I am rooted on the latest stock Oreo H91820H -I am not sure what I want to load that I could not before?! overclocking the CPU or changing the hue on the display is not a big deal for me at all. & Yes I will uninstall some bloatware - but that is not so bad on this phone anyhow. Any good ideas or a better/later rom than H91820H that has all things working, do please let me know. I am glad that I rooted, ahh the challenge, but if I have no other reason such as to load a program then I think I will revert back to stock and unlock the bootloader & let the ROM updates come from T-Mobile & LG.
-Shahin
shahinman said:
I started with stock LG v20 T-Mobile H91810P and followed this step by step & the original threads. I loaded the latest stock Oreo from H91820H from here instead of latest Nougat H91810U - Pie & some other versions had too many things not working.
In the process there were a few problems -the major ones are following with solutions, some from here:
1) The file H91810P that needs to be reloaded was missing in original links - I think I downloaded from here.
2) I lost root several times, but had TWRP. So I used adb sideload like:
Boot/start TWRP and the start ADB Sideload
Download Magisk-v16.0.zip and copy to adb directory.
On Windows PC connect Cell with USB and in CMD window type (copy/paste):
adb start-server
adb sideload "Magisk-v16.0.zip"
And never update migisk after installing. Also no need for SU.
3. Camera did not work and people could not hear me nor could I hear them when I picked up a call - A reboot/restart fixed it.
I have 4 problems remaining -any help for solutions here is appreciated - especially exact type help please:
1) On LAF/Boot (original download) partition: Vol+ & connect to USB caused the download mode to come on for about 2 seconds and then TWRP (however I am glad that TWRP is here) -Prefer this to be the original download mode.
2) On Recovery patition: Vol- & connect to USB causes fastboot to come up. Flashed the recovery-twrp-h918-2018-10-18.img (renamed to recovery.img) to recovery partition using flashify and TWRP unsuccessfully. -Prefer this to be TWRP.
3) TWRP cannot access the Data partition. Rebuilt and reformatted Data from TWRP without success. -Prefer access to Data from TWRP.
4) At boot time: I like to get rid of the warning that my bootloader is unlocked. -I can live with this one.
After thoughts: Now that I am rooted on the latest stock Oreo H91820H -I am not sure what I want to load that I could not before?! overclocking the CPU or changing the hue on the display is not a big deal for me at all. & Yes I will uninstall some bloatware - but that is not so bad on this phone anyhow. Any good ideas or a better/later rom than H91820H that has all things working, do please let me know. I am glad that I rooted, ahh the challenge, but if I have no other reason such as to load a program then I think I will revert back to stock and unlock the bootloader & let the ROM updates come from T-Mobile & LG.
-Shahin
Click to expand...
Click to collapse
You can restore download mode by flashing the zip in the original lafexploit thread, but make sure you have twrp on the recovery partition. Make sure you are on the latest version of twrp, when you flashed twrp, you were supposed to format the data partition before flashing the rom.
Sent from my LG-H910 using XDA Labs
For access to Data in TWRP: In the original thread there is nothing about formatting, but in step by step guide there is and I followed - however it does not specify what partition to format. I also ran ./step2.sh script per instructions.
Anyhow as I mentioned above I rebuilt and reformatted the Data partition and that did not give me access. I am on the TWRP 3.2.1-3. What partitions do I need to reformat anyhow?
To flash recovery: I used TWRP and flashify to flash recovery-twrp-h918-2018-10-18.img and it flashes but does not work - I get to fastboot with Vol- & USB.
shahinman said:
Problems with rooting, loading ROM then recovery & download images -some solutions
I started with stock LG v20 T-Mobile H91810P and followed this step by step & the original threads. I loaded the latest stock Oreo from H91820H from here instead of latest Nougat H91810U - Pie & some other versions had too many things not working.
In the process there were a few problems -the major ones are following with solutions, some from here:
1) The file H91810p rom (H91810p_00_0717.kdz) downloaded from here.
2) I lost root several times, but had TWRP. So I used adb sideload like:
Boot/start TWRP and the start ADB SideloadDownload Magisk-v16.0.zip and copy to adb directory.On Windows PC connect Cell with USB and in CMD window type (copy/paste):adb start-serveradb sideload "Magisk-v16.0.zip"
And never update migisk after installing from above or will lose root. Also no need for SU.
3. Camera did not work and people could not hear me nor could I hear them when I picked up a call - A reboot/restart fixed it.
4. No need to download UPPERCUT (that is hard to download), because LGUP works fine without UPPERCUT.
I have 4 problems remaining -any help for solutions here is appreciated - especially exact type help please:
1) On LAF/Boot (original download) partition: Vol+ & connect to USB caused the download mode to come on for about 2 seconds and then TWRP (however I am glad that TWRP is here) -Prefer this to be the original download mode.
2) On Recovery patition: Vol- & connect to USB causes fastboot to come up. Flashed the recovery-twrp-h918-2018-10-18.img (renamed to recovery.img) to recovery partition using flashify and TWRP unsuccessfully. -Prefer this to be TWRP.
3) TWRP cannot access the Data partition. Rebuilt and reformatted Data from TWRP without success. -Prefer access to Data from TWRP.
4) At boot time: I like to get rid of the warning that my bootloader is unlocked. -I can live with this one.
After thoughts: Now that I am rooted on the latest stock Oreo H91820H -I am not sure what I want to load that I could not before?! overclocking the CPU or changing the hue on the display is not a big deal for me at all. & Yes I will uninstall some bloatware - but that is not so bad on this phone anyhow. Any good ideas or a better/later rom than H91820H that has all things working, do please let me know. I am glad that I rooted, ahh the challenge, but if I have no other reason such as to load a program then I think I will revert back to stock and unlock the bootloader & let the ROM updates come from T-Mobile & LG.
-Shahin
Click to expand...
Click to collapse
I had this same situation and ended up bricking the phone, can't get into recovery, stuck in boot loop. This was months ago, just got another v20 and ready to try again. Previously I'd successfully done 3 v20's.
TWRP Custom Recovery for the Onn Android Tablet series
This is the first fully-featured custom recovery for Walmart's MediaTek-based Onn tablets: ONA19TB002, ONA19TB003 and ONA19TB007. TWRP needs no introduction. If you have come here, you probably have some idea of what it is and what it's used for. This TWRP build does not need the bootloader unlocked or VBMeta verification disabled, although it's recommended that you at least unlock the bootloader.
DISCLAIMER
Everything described in this thread is done at your own risk. No one else will be responsible for any data loss, corruption or damage of your device, including that which results from bugs in this software.
FEATURES
Decrypted data partition
All USB modes functional: MTP, ADB, Mass Storage, OTG, Charging
Fast boot time
Adoptable storage mounting
Firmware image backup and restore
Works under locked bootloader
Android 9 build fits within the 16MB recovery partition -- no compromises or partition resizing necessary
INSTALLATION METHOD 1
Download the recovery to your PC and unzip the image
Unlock the bootloader (skip if you have already done this)
Enable OEM Unlock in Developer Options in Android Settings
Boot into fastboot mode either by holding vol. up+power to power it on and selecting "Fastboot mode", or by running the 'adb reboot bootloader' command from within Android.
Install fastboot and appropriate drivers on your PC if you have not set those up
Unlock the bootloader with the command
Code:
fastboot flashing unlock
...and follow the instructions on the screen. This will wipe your data.
Flash the custom recovery with
Code:
fastboot flash recovery twrp-3.3.1-ONA19TB002.img
(use the right file name path for your device)
Reboot to recovery with
Code:
fastboot oem reboot-recovery
INSTALLATION METHOD 2
This assumes you are familiar with SP Flash Tool or can figure it out on your own
Download the recovery to your PC and unzip the image
Get the appropriate scatter file for your device. The scatter file may be found in the device's firmware under /system/data/misc.
Set up SPFT Download tab as Download Only. Load your scatter file.
Under the recovery line, double-click Location and open your TWRP image.
Click Download and connect your powered-off tablet to your PC. SPFT will automatically flash the recovery to the emmc and disconnect when finished.
INSTALLATION METHOD 3
Head over to Amazing Temp Root for MediaTek ARMv8, read the requirements and directions, and grab the latest mtk-su.
Open a root shell with mtk-su
Flash the (unzipped) recovery with the command:
Code:
dd bs=1048576 if=twrp-3.3.1-0-ONA19TB002.img of=/dev/block/by-name/recovery
(replace the if= file name with your appropriate recovery image path)
Exit root shell
START RECOVERY
Three methods:
On a powered off tablet, hold Vol. up+power for about 3 seconds. In the menu that appears, select "Recovery mode"
With Android ADB, use the command 'adb reboot recovery'
From Android root shell, use the command 'reboot recovery' or just use any root app with OS reboot features
NOTES
Kind of important: Make a backup of your Crypto Footer as soon as you can. This is the encryption key to your data partition. When accessed from TWRP, this key can get "upgraded" so that you will get locked out of Android. TWRP uses a hacky workaround that saves and restores the original footer on every /data decrypt. But that method is not what I would call 100% reliable.
Make sure you have a backup of the untouched stock system and vendor images. There are no official firmware packages available to download.
Only mount system/vendor partitions in read/write mode if you have unlocked the bootloader. It is recommended to choose to leave system read-only at the startup prompt unless you have a specific reason to modify it. If the bootloader is locked, then dm-verity is enforced.* So merely mounting it once in r/w will cause a boot loop.
It's currently not possible to install incremental OTA updates using this TWRP. Use the stock recovery to update the FW. That will only work if you have never mounted system/vendor in write mode.
DOWNLOAD (Nov. 30, 2019)
Current version: 3.3.1-1
ONA19TB002 - Onn 8" model
ONA19TB003 - Onn 10.1" model
ONA19TB007 - Onn 10.1" w/keyboard model
Source code
ONA19TB002 | ONA19TB003 | ONA19TB007
ACKNOWLEDGEMENTS
The team behind TWRP & OmniROM
@tek3195 for testing and feedback on the 8" model
Please post feedback since these are still pretty new and not exhaustively tested. Let me know if I should port it to other models in the series.
Reserved also
grabbing this one too cuz why not
Very nice! I'll download and test the 003 one soon.
I also have a 007 model to experiment with.
I tried about a dozen times to build TWRP and failed miserably LOL. Closest I got was one that would boot but the rotation was all messed up, USB wouldn't work, didn't mount some partitions... Yeah, it was a hot mess.
Do you happen to have sources available?
Hi @NFSP G35,
I'll have the source code soon. Most of the tricks involved patching bootable/recovery. So I need to commit those changes and include the proper patch set from my tree....
Amazing!! Gonna install and test 8" right now.
Has anyone tried a GSI on these tablets yet?
MishaalRahman said:
Has anyone tried a GSI on these tablets yet?
Click to expand...
Click to collapse
I do know @tek3195 , the Onn 8 thread starter, has tried many of them as well as others here, somewhere on that thread he listed his tests and opinion of several of them.
I'm pretty sure others on that thread have also tried GSI's.
MishaalRahman said:
Has anyone tried a GSI on these tablets yet?
Click to expand...
Click to collapse
I did try both Phhuson vanilla and also Liquid Remix (I'm keeping this one for now). I didn't flash them through twrp, but using fastboot via bootloader.
WoW! AwEsOmE! I cannot wait to try this! THANK YOU!!!!!!
Hey,
This is a neat thing to see for the Onn tablets. I have a question though. I own a device based on the mt8163, and am trying to help people with another device I don't own (the powkiddy x18 which also uses the mt8163). One of the things I wanted to do was to make a custom rom for the x18, since it's stock firmware is horrible. And of course, one of the first steps to custom roms is twrp. So I have a question for you that I hope you can answer for me. How did you make this build of twrp? I have seen no device trees for this device so I was kinda curious. If you can help me in any way, I'd be so grateful, and I'm sure the other people with the x18 would be grateful for help.
@diplomatic
Is there a different procedure for installing TWRP on a locked bootloader?
I can confirm that using SP Flash to load your TWRP.img will produce a bootloop when installing to a device with the BL locked. Reflashing the original recovery.img makes the problem go away. You mentioned in the OP that this TWRP will work on a locked BL so I thought I would share my case study with you in following the procedure you defined.
MY SINCERE GRATITUDE FOR YOUR EFFORTS IN PORTING THIS TO THE ONN!
You're welcome, @Spatry.... Can you describe how you ended up with a locked BL? Was it unlocked before? Have you ever tweaked vbmeta? Also, when you say bootloop, do you mean for Android or just for recovery? I'm not going to insist that it works under locked BL. I tested it once and it did boot up...
diplomatic said:
You're welcome, @Spatry.... Can you describe how you ended up with a locked BL? Was it unlocked before? Have you ever tweaked vbmeta? Also, when you say bootloop, do you mean for Android or just for recovery? I'm not going to insist that it works under locked BL. I tested it once and it did boot up...
Click to expand...
Click to collapse
Presently, I am running stock with Magisk patched BOOT on locked bootloader, stock vbmeta. The boot loop was at the ONN Android screen, I could not get it to even boot into recovery.
At one time I did run with the bootloader unlocked (with --disable-verification on stock vbmeta) and I ran Phusson's AOSP, Liquid Remix and Bliss. I found there was no benefit to me in running the other mods so I reverted back to stock courtesy of @CaffeinePizza and the bootloader re-locked to get rid of that annoying 5 second orange state.
In each instance, I always used SP Flash tools to load all .img files. I only used fastboot to install magisk_patched.img onto the stock installation. Unlocking the bootloader erases all data and I did not feel like reinstalling everything again, so I figured I would try to install TWRP per your instruction to see if it would work while the BL was still locked... Restoring the original recovery got rid of the bootloop. I do want to try your TWRP so I will try it with BL unlocked when I get some free time to do so.
Spatry said:
Presently, I am running stock with Magisk patched BOOT on locked bootloader, stock vbmeta. The boot loop was at the ONN Android screen, I could not get it to even boot into recovery.
Click to expand...
Click to collapse
This sounds like you might have flashed a wrong/corrupt image to recovery. It may have to do with AVB checks rather than bootloader lock. But those conditions might be interdependent somehow so I can't tell you for sure. The fact that you are able to boot a patched image on a locked BL says it doesn't care too much about verification. I can tell you for sure that any recovery image must have avb metadata, not necessarily the required hash, for both Android and recovery to boot. Can you try to unzip the image file and flash it over again?
Hmm, the situation with the bootloader lock sounds eerily similar to the Nabi SE. The latter also had a similar implementation where there's not much in the way of locking things down, other than an (easily circumvented) SP Flash Tool signature check and different preloader keys. And here's the real kicker: the nearly-identical Fisher Price Nabi also ran on the MT8163, so it makes me wonder if it's possible to boot Pie on it, or perhaps a GSI assuming that Treble can be tacked onto it.
Also, do you have the source repo to this TWRP port of yours?
If anyone here gave me an XDA ad-free subscription, thanks a lot! I didn't get a notification of who it was. Using this site is a lot more bearable now.
diplomatic said:
If anyone here gave me an XDA ad-free subscription, thanks a lot! I didn't get a notification of who it was. Using this site is a lot more bearable now.
Click to expand...
Click to collapse
Where do I find crypto footer to backup
diplomatic said:
If anyone here gave me an XDA ad-free subscription, thanks a lot! I didn't get a notification of who it was. Using this site is a lot more bearable now.
Click to expand...
Click to collapse
Kinda cool without the ads isn't it. I know I sent one about a week ago or so. I think everybody ought to send you one, you deserve it. THANKS and AWESOME work.
Alright here goes another post from another stupid user who did things without understanding
I know there are hundreds of other threats with the same question,I tried to check them but they are damn many and I am confused. I hope no moderator gets angry at me.
I have PRA-LX1 which had EMUI 8 working fine. and then I decided that I am too young to have an old Android and decided to go for LineageOS 17.1 from DarkJoker360. After couple of unsuccessful attempts and some minor things I ave a phone that goes into fastboot, but not TWRP. keeps bootlooping (I tried a stock recovery for oreo and then was able to shut it down when it prompted eRecovery page, otherwise it kept looping). Bootloader unlocked. (I was able to get so many different TWRPs to work on the phone just few hours ago, and I guess I did not do anything that bad either. )
I saw these posts about getting the boot.img and other images from some Huawei Firmware finder, but not sure how to get them and I am not sure how can I check the exact model of the phone (I guess it is PRA-LX1xxxxxx)
Sorry if I am not giving enough info, I would appreciate if you ask
Resolved. I am not sure what was the issue, but I did followings (writing down just in case this will be helpful).
PRA-LX1 c464. Bootloader unlocked. I was not able to get into TWRP. I was able to get into fastboot. eRecovery from Huawei was not doing anything (cannot get info from server it said).
Then I downloaded the FullOTA-MF
dload method was getting interrupted after 5%.
Then I extracted System.img kernel.img, recovery_ramdis.img and ramdiks.img. and flashed these in order.
System – fastboot flash system SYSTEM.IMG
Ramdisk – fastboot flash ramdisk RAMDISK.IMG
Kernel – fastboot flash kernel KERNEL.IMG
Recovery – fastboot flash recovery_ramdisk RECOVERY_RAMDIS.IMG
Then at reboot it was getting stuck at 0% loading (Warning To avoid system error please do not press and hold the power button) on some EMUI page. Waited for half an hour and rebooted. again stuck. went into bootloader and flashed a TWRP. this time I get into TWRP.
From there dload method to go back to EMUI and installed LineageOS afterwards.