Hello Guys,
Sorry that I post this here, but I don´t know where to put this else.
I have an Asus Zenfone Selfie ZD551KL and wanted to root it. It was still on Android Lollipop and I tried it according to a guide for Android Marshmellow. As expected it didn´t work. So I tried to flash a prerooted system with adb. That didn´t work either but now I don´t have a running system left, just access to fastboot and recovery. Recovery.img (version WW_user_1.15.40.1582_20160510) and boot.img got flashed in the process, system.img failed "FAILED (remote:size too large)". Even with the command -S300 (don´t know which parameters to use, think those should be right), it didn´t work.
So I tried to flash the original ROM from asus. I tried the newest version "UL-Z00T-WW-21.40.0.1923-user.zip" and an older version according to the recovery version "UL-Z00T-WW-51.15.40.1582-user.zip". Both didn´t work, neither with adb sideload, nor with updating from SDCard. When I try to flash the newer version, I get the message "patching system image unconditionally" and in the DOSBox the flash process just stucks at 83% every time (faced same procedure with other ROM´s too).
The older version gives me another errormessage "System update fails with status 0, fota return code 409"
I wiped data and cache partition before every try.
Sadly Bootloader isn´t unlocked and I cant unlock it with ADB, as every command, which should unlock it, doesn´t work.
Every firmware I tried was WW SKU, as recovery log says my phone is WW, when I try to flash a ROM. But I bought this smartphone from china, so should I try CN ROM? Asus Website just has Lollipop CN ROM and I don´t think I could find a way to root the phone, when needing to flash CN ROM. But Root is what I need on it....
I hope you are able to read the text. English is a foreign language to me.
I would appreciate help alot!
Greetings
BrickedGuy
Hello, recently i tried to root my phone using a method through twrp that I saw in the internet. After that my phone just bricked then I searched for informations online and I saw some forum thread saying to go to wipe and clear System. So I did that. Now I cant flash another rom in my phone and my phone wont start
Please help me. I still can acces Fastboot and TWRP
In repair system in TWRP is saying that the size of system is 0mb. Help me
Phone: Asus Zenfone 2 Laser ZE500KL
Don't need help anymore. I figured out how to do it myself. I just needed the system.img then open fastboot in my Asus. Then I typped fastboot flash system system.img then i wat around 3 minutes and its done
Hi All,
I flashed oreo to my Mate 9 today, all was well until I tried to root.
Now it won't boot, stuck in bootloop. I can get to Fastboot and TWRP Recovery.
Tried to reflash, but now no bootloop - just got fastboot and TWRP.
When in TWRP device is not showing up in ADB devices, so can't push anything.
Any ideas as to how to come back from this?
Thanks.
Things are worse now... it won't reboot to recovery. Can still get fastboot though.
When reboot to recovery it just sits on "your device is booting now..." and doesn't seem to progress. I have re-flashed TWRP via fastboot... but still the same.
Wallace44 said:
Hi All,
I flashed oreo to my Mate 9 today, all was well until I tried to root.
Now it won't boot, stuck in bootloop. I can get to Fastboot and TWRP Recovery.
Tried to reflash, but now no bootloop - just got fastboot and TWRP.
When in TWRP device is not showing up in ADB devices, so can't push anything.
Any ideas as to how to come back from this?
Thanks.
Click to expand...
Click to collapse
Device shows phone and FRP as unlocked.
I have extracted the oreo update using a Perl script i found on another thread. Flashing system, kernel, recovery_ramdisk has made no difference.
Anyone able to help please?
What root did u use magisk or su?
Why don't you use this method?
Its safe and no more side effects.
Then after you can root with magisk.
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
Thanks
[email protected]@n
Mate-10
I was trying to flash modified recovery image using magisk after that my phone is dead almost.
My phone don't boot in to android. I can't charge my phone because I get message on the beginning
my system is moddifyed my phone shut down automatically after 5 seconds, also i can't unlock bootloader via fastboot i get information "unlock operation is not allowed" .
I have Leeco 650x with mtk helio x27.
I only flashed modified recovery in magisk after that I disabled usb debug and oem unclock. after restart my phone I can't unlock my bootloader and I can't continue bootup to android.All I need to do is restore somehow original recovery.
But how to do that without unlocked bootloader in my situation?
I try to flash new Rome using flash tool but I have error 0xC0030003
Is here any powerful person to solve the problem.
It looks like you flashed firmware for wrong device. Settings say x650 instead of x720 (I am assuming you have x720). I think your best bet is probably the QFIL restore.
https://www.google.com/amp/s/forum....to/guide-unbrick-le-pro3-tested-t3622340/amp/
If you do not have an x720, please disregard this post.
I have 650x with mtk processor 100 procent. I only flashed modified recovery in magisk after that I disabled usb debug and oem unclock. after restart my phone I can't unlock my bootloader and I can't continue bootup to android.All I need to do is restore somehow original recovery.
But how to do that without unlocked bootloader in my situation?
I try to flash new Rome using flash tool but I have error 0xC0030003
LucasNoob said:
I have 650x with mtk processor 100 procent. I only flashed modified recovery in magisk after that I disabled usb debug and oem unclock. after restart my phone I can't unlock my bootloader and I can't continue bootup to android.All I need to do is restore somehow original recovery.
But how to do that without unlocked bootloader in my situation?
I try to flash new Rome using flash tool but I have error 0xC0030003
Click to expand...
Click to collapse
You need to find the LETV X650 Scatter file. I do not know those phones very well. A X600 file may work, you will need to do a lot of research before attempting or you can damage your partitions.
Here is a link for the firmware. https://fapgem.com/video/4tnZoa0H9Q...-firmware-eui-5925s-install-via-fastboot.html
There is a chance that if you can get your PC to see the phone that you may be able to flash the stock firmware. It will not hurt to try it. Again , read extensively before doing anything.
There is a website called Android brick. They have an article on unbricking your phone but I could not access the link. Just Google, or use DuckDuck Go and search Letv X650 Scatter file unbrick.
I just now found this, which may be your solution: https://stephaniefulke.blogspot.com/2015/09/how-to-flash-unbrick-your-mediatek.html
Good luck
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.