At a Loss. Nextbook NX16A10132S Ares 10A Stock Rom? - Android Q&A, Help & Troubleshooting

Ok So I have a Nextbook NX16A10132S Ares 10A
I have TWRP custom recovery installed on it that I used from the Ares 8A.
I've tried flashing the Ares 8A rom, the Remix OS rom for it but no luck.
https://forum.xda-developers.com/remix/supported-devices/port-remix-os-2-0-nextbook-ares-8-t3498015
gives an error does not installed..FML.
So then I found a site with a option to restore this backup for TWRP after just putting it in the backup folder for TWRP.
This I was able to do, it installs the system not the boot part of this backup, but it still doesnt boot into the system.
Literally if anyone has a Ares 10A 11A any ****ing that close to this system that they have TWRP/root on and woul back it up so I can restore it..you will literally have my eternal thanks. Or really anyone else that could get a rom that would work for this intel atom based android tablet that has driven me insane.

I am also at a loss with this Nextbook tablet as well. A customer of mine brought me one that has an activation lock on it. She got ripped off and bought it 2nd hand and didn't know about the lock until it was too late and seller disappeared on her. So now i'm trying to help her figure out a way to at least bypass the activation in anyway. I tried using remix OS but that didn't work, so I am trying Pheonix OS.

have same tablet and twrp backup
i have the same tablet just been playing with it i have a twrp backup image if you need it its incomplete as my version of twrp cant backup the data partition let me know how and where to get the image file to you guys
mi useing twrp meant for ares 8 tablet it works almost perfectly i also have a image file made with nandroid overthe air app but the backup files it makes are too llarge not broken up into 1 gig partials like twrp does
can contact me directly at [email protected]

I gave a working system image made from my unencrypted rooted ares 10a If your bricked you cand hold volume down buttom while plug in usb to carde keep holding vol down button and tablet will boot into recovery from ther you can data wipe or factory restore and make a backipimage vamprila has a good root solution that supplies restore and boot images to flash as well

Decrypt ares 10a
Could you explain how I decrypt my ares 10a I can't find any steps on xda

Nextbook 10
killainferno said:
I am also at a loss with this Nextbook tablet as well. A customer of mine brought me one that has an activation lock on it. She got ripped off and bought it 2nd hand and didn't know about the lock until it was too late and seller disappeared on her. So now i'm trying to help her figure out a way to at least bypass the activation in anyway. I tried using remix OS but that didn't work, so I am trying Pheonix OS.
Click to expand...
Click to collapse
I have a similar problem. I bought this one second hand. And what a bargain it's been. I can't get past the activation lock. Please help. It's nice to know I'm not alone in this Savage world lol

trying to root nx16a10132s need twrp stock boot.img
read thru the root ares 8A with android 6.0.1 thread read it all then this rooting stuff starts to make sense does anyone have the stock boot.img and or stock sys.img you can use the twrp from this post 8A's twrp but HAVE TO HAVE a fixed boot.img before you do anything but twrp backup the boot.img and the sys.img and data.img (the data.img is complicated to get right) another member says he'll fix the 8A boot.img he may do the same thing for us if we can get hmi the 10a boot.img maybe but i think its any of ours only hope. cant really root with out it being modified. the boot file should be areound 30Mb so if you have a stook boot contact me and i'll walk you thru temp twrp extracting it nextbook has changed up thier security measures soo DONT change anything until we all get the modifies boot.img if some one is dareing there are posts on how to modify or repack the boot.img i aint that good yet its beyond me still but it can be done by someone who is a little more knowledgeable also post whick build your device is what kernal it uses blah blah all the stuff under settings>about tablet> these numbers are important if you dont use the matching versions you will end up with no wifi no bleutooth and no sound I've seen posts on how to get around the activation code on the thread i mentioned READ the WHOLE threade before you do anything by the time you finish it LOTS more stuff will make sense and you'll say F**K i so luck i aint really screwed my tablet up

Code:
billybleu97 said:
read thru the root ares 8A with android 6.0.1 thread read it all then this rooting stuff starts to make sense does anyone have the stock boot.img and or stock sys.img you can use the twrp from this post 8A's twrp but HAVE TO HAVE a fixed boot.img before you do anything but twrp backup the boot.img and the sys.img and data.img (the data.img is complicated to get right) another member says he'll fix the 8A boot.img he may do the same thing for us if we can get hmi the 10a boot.img maybe but i think its any of ours only hope. cant really root with out it being modified. the boot file should be areound 30Mb so if you have a stook boot contact me and i'll walk you thru temp twrp extracting it nextbook has changed up thier security measures soo DONT change anything until we all get the modifies boot.img if some one is dareing there are posts on how to modify or repack the boot.img i aint that good yet its beyond me still but it can be done by someone who is a little more knowledgeable also post whick build your device is what kernal it uses blah blah all the stuff under settings>about tablet> these numbers are important if you dont use the matching versions you will end up with no wifi no bleutooth and no sound I've seen posts on how to get around the activation code on the thread i mentioned READ the WHOLE threade before you do anything by the time you finish it LOTS more stuff will make sense and you'll say F**K i so luck i aint really screwed my tablet up
Click to expand...
Click to collapse
I am shocked that the custom twrp, that vampirefo made, that I provided in my ares 8a thread for the nextbook ares 8a, would even work for this tablet?
temp booting twrp is used to create a backup of the original boot.img.
I then unpack it and remove the encryption flag and dm-verity flags, then repack it.
In order for the data partition to be unencypted after this, the data partition must be deleted. you will loose all data on the data partition.
when the tablet is booted with the new, modified boot.img, a new, unencrypted, data partition is created. your old data partition is not magically unecrypted, so you need to backup any important files through, for example and mtp connection to a computer. that also means that only certain types of data can be backed up this way from the internal sd card and the external sd card. any apps you have will have to be reinstalled from scratch. any game and app data will probably be lost also unless you can back it up also some way.
deleting your existing data partition so a new, unencypted on can be created, is the only way I know how to do this.
The user who found a solution as to how to disable the activation of the tablet said he would post how he did it in my thread, but never did and I don't know how to do it. I bought mine from the only legitimate source I know that sells it: Walmart. I purchased my tablets from the store I work at. An activation code is printed on the receipt, and is unique to each tablet.
There are some bits and pieces of what he did to defeat activation, in my thread, but they are somewhat vague. Maybe you can PM him to get him to answer.
Most of the users I have helped and modified boot.images for different versions of the 8a, have taken my modified boot.imgs and ran, no longer to be seen.
When I asked them for supersu systemless, patched images, they never even had the courtesy to even respond to me.
I have become disillusioned by ungrateful xda members who feel entitled and don't give to the community in return.
However I am still, irregardless, trying to help if possible.
I tried to learn how how build twrp myself, but it is a very, very steep learning curve to do it. And it can only be done with a linux computer with lots of disk space to download the twrp source files. That is way beyond my abilities, currently. However, I do run Linux Mint Mate, most of the time now, as it boots and runs much faster than my windows 7 drive, despite being on a persistent, casper-rw, usb key, 32gb.
---------- Post added at 02:51 AM ---------- Previous post was at 02:20 AM ----------
A backed up data partition from the original, stock tablet, doesn't work on the rooted ares 8a either, because it is an encrypted backup. A modified boot.img removes the encyption flag and verified boot, but this does not decrypt an existing data backup in twrp. Hence the need to:
Code:
fastboot format userdata
, hit return
Code:
fastboot format cache
, hit return
Can you successfully flash supersu systemless with vampirefos twrp for the 8a on your 10a and gain sucessful root access? And of course the userdata must be deleted with the above commands, in fastboot mode, if supersu can be sucessfully flashed and works. I use jrummy's root test app, from the play store. I also always flash yds busybox in twrp, also, after supersu flash.
UPDATE: I think you need to delete userdata in fastboot, before you flash supersu in twrp, not after. I am tired so my memory is not as good, so I believe that is the safer way to do it, not after flashing supersu.
I have not written this in the 8a thread, but currently I recommend supersu in its default systemless mode: supersu 2.82 SR5, from the supersu beta thread.
I previously recommended the unoffical, systemmode supersu for the 1.0.8, 1.1.1 and 1.2.0 versions of the 8a.
UPDATE: upon looking at the specs of the ares 10a they are the same as the 8a with it having twice the internal storage space as the 8a: 32gbs vs. the 8a's 16gbs. I am not sure how this would affect the 8a twrp build if used on the 10a the android partitions are more than likely a different size.
a good android utility for determining the partition sizes is called diskinfo.
Here are the partitions for the ares 8a:
system
cache
data
metadata
boot
recovery
misc
bootloader
bootloader2
persistent
config
metadata
sd card
external SD
There are others, but those above are the main ones
PLEASE NOTE: THIS MAY NOT WORK FOR YOUR 10A. THIS MAY BRICK YOUR DEVICE. IT IS ALL THEORY BASED ON THE 8A, WHICH HAS ALMOST IDENTICAL HARDWARE EXCEPT FOR ONLY HALF OF THE 10A'S 32GB STORAGE SPACE.
SINCE VAMPIREFO'S TWRP WAS BUILT FOR THE 8A, THERE MAY BE UNEXPECTED CONSEQUENCES!
YOU HAVE BEEN WARNED! DANGER, WILL ROBINSON! (A LOST IN SPACE REFERENCE, FOR THE YOUNG.)
the bootloader must first be unlocked. See my ares 8a thread for very detailed info on how to do the below steps. One updated change from it though: YOU MUST USE THE OFFICIAL SUPERSU.ZIP, WHICH INSTALLS AS SYSTEMLESS. IT WILL ALSO PATCH YOUR BOOT.IMG TO DISABLE ENCRYPTION AND DISABLE DM_VERITY (ANDROID VERIFIED BOOT), SO NO NEED FOR A USER MODIFIED BOOT.IMG.
THE ORIGINAL UNOFFICIAL SYSTEMMODE SUPERSU I HAD PREVIOUSLY PROVIDED DOES NOT PATCH THE BOOT.IMG TO REMOVE ENCRYPTION AND DM_VERITY.
Code:
fastboot format userdata
hit enter, wait to complete.
Code:
fastboot format cache
hit enter, wait to complete.
this will delete all user data so a new, unencrypted data partition can be created.
Of course, any data will be deleted so a backup is needed through, for example, mtp to a computer. user apps will have to be reinstalled. System apps will still be there.
it look like on should then be able to temp boot the 8a twrp recovery in fastboot mode by issuing:
Code:
fastboot boot Ares8A_recovery_twrp.img
then once into twrp hit the install button and select the SR5-SuperSU-v2.82-SR5-20171001224502.zip systemless and flash it. it must already be on the internal sd card, or the external sd card. If all goes well you should see a message in twrp that supersu has successfully patched your boot.img and backed up the original to a new folder created in the root of the device, called .subackup. the files in that are the originals extracted from your stock boot.img.
The next step is to reboot. The first boot will take a very long time. The last time I did it on one of my 8a's, it took ~5 minutes to get past the animated nextbook animation before going to the android security, usb debugging prompt and setup screen.
See my ares 8a root thread, for better details

Question about ares 10a nextbook
i have brand new ares 10a but dont have an activation code anyway around it? Can i install rom are what? thanks god bless

there was someone who uninstalled one of the system apps and it help get rid of activation code need read thru root ares8 thread there was another person that installed a differnt rom and did the same thing but i wouldnt advise that for the ares10a..thers a link on the nextbook site that is supposed to give you the code if you put in a number from the tablets box but i dont know if thats a 100% solution either but its a starting place to look

thanks I'll check into it once i can someone on ebay is sale the code $15 and info he needs is I believe its all done online for free. LOL
I'll need some information from the tablet itself
YOU WILL NEED
1. a mini-usb cable that plugs into the tablet - this is the same type of cable that charges most android phones (not an apple cord) or a playstation 4 charging cable will work too
2. Laptop or desktop computer with internet access - preferably running windows 8 or windows 10 (you can use windows 7, but you may have to download drivers for it to recognize the tablet)
I will need you to copy a file from the tablet to your desktop and open it - the copy and paste it into this message for me along with your serial number
are you able to do this?
If so, then you can go ahead and pay and i will send the rest of the instructions

my experiance dont trust ebay
I've been looking for some solutions for my ares 10a for months now but NEVER have i seen anything like this ebay guy is offerong... sound to good to be true.....read thru the ares 8a threads 2 hrs of reading may save you a brick tablet or just keep you from getting screwed by a stranget from ebay if you dont find anythig then give em a ty if you risk it
tone4life said:
thanks I'll check into it once i can someone on ebay is sale the code $15 and info he needs is I believe its all done online for free. LOL
I'll need some information from the tablet itself
YOU WILL NEED
1. a mini-usb cable that plugs into the tablet - this is the same type of cable that charges most android phones (not an apple cord) or a playstation 4 charging cable will work too
2. Laptop or desktop computer with internet access - preferably running windows 8 or windows 10 (you can use windows 7, but you may have to download drivers for it to recognize the tablet)
I will need you to copy a file from the tablet to your desktop and open it - the copy and paste it into this message for me along with your serial number
are you able to do this?
If so, then you can go ahead and pay and i will send the rest of the instructions
Click to expand...
Click to collapse

I had the same issue with "/data" not being mountable. I used twrp to wipe that partition and make a new one. There's something wierd with it because i wasn't able to root and install twrp in the recovery partition until I did the wipe. It would default back to stock image when it had issues booting

oxendine9381 said:
I had the same issue with "/data" not being mountable. I used twrp to wipe that partition and make a new one. There's something wierd with it because i wasn't able to root and install twrp in the recovery partition until I did the wipe. It would default back to stock image when it had issues booting
Click to expand...
Click to collapse
My guess would be that your original data was not mounted because it is encrypted. With a modified boot.img to remove encryption and dm-verity, the userdata must be wiped to create a new, unencrypted, data partition, on next boot.
I do not own an Ares 10A, as was stated a few posts above, but I was wondering if any of the info I provided concerning the Ares 8A was useful in getting root on your 10A's?
Thanks

eternal2u said:
Ok So I have a Nextbook NX16A10132S Ares 10A
I have TWRP custom recovery installed on it that I used from the Ares 8A.
I've tried flashing the Ares 8A rom, the Remix OS rom for it but no luck.
https://forum.xda-developers.com/remix/supported-devices/port-remix-os-2-0-nextbook-ares-8-t3498015
gives an error does not installed..FML.
So then I found a site with a option to restore this backup for TWRP after just putting it in the backup folder for TWRP.
This I was able to do, it installs the system not the boot part of this backup, but it still doesnt boot into the system.
Literally if anyone has a Ares 10A 11A any ****ing that close to this system that they have TWRP/root on and woul back it up so I can restore it..you will literally have my eternal thanks. Or really anyone else that could get a rom that would work for this intel atom based android tablet that has driven me insane.
Click to expand...
Click to collapse
GO TO [email protected] FOR FAST HELP

Can rooting help Nextbook NX16A10132S Ares 10A...
Do we have a forum for fixing the bad implementation of Android 6 on the nx16a10132s,—PC Windows 7 sees it as an mp3 player, and its file Modification dates are fake Creation dates of every Move/Copy... 14 GB of these useless Modification dates, of 17 GB usable of 24 GB listed by the filename-abbreviating file manager 'garbage-on-top-of-garbage' of 32 GB advertised... (Rooting doesn't fix this, Or, does it,—Rooting just makes it hang faster—true, or not, true...)

I have a next book 10a and I don't have the activation code. What can I do. PLEASE HELP ME OUT

I was able to get the offending lock-screen app passcode program in the Nextbook NX16A10132S Ares 10A removed. On kernel 3.14.64-x86_64 android 6.0.1 -- This method erased all user data on the device and returned it to factory settings -- only without the lock screen program.
With the device turned off and unplugged, I hold down the power and the volume button that's farther from the power button until the system boots into the fastboot screen. I plug in the USB to the computer and use the Android Developer tool: Fastboot to unlock the boot loader:
fastboot flashing unlock
fastboot format userdata
fastboot format cache
I then tell the device to shutdown.
I Download and Extract the Ares8A_recovery_twrp.img from this thread, and put it into the computer's working directory I'm using fastboot from:
https://forum.xda-developers.com/showpost.php?p=72970060&postcount=82
I unplug the USB and start it back up with the power and volume button again until the fastboot screen appears again. I then plug in the USB and run :
fastboot boot Ares8A_recovery_twrp.img
Once TWRP is running, I click the Mount button on the tablet and check the box to mount System.
Then I use ADB SHELL to rename the bad application:
adb shell mv /system/app/VUDUStartWizard/VUDUStartWizard.apk /system/app/VUDUStartWizard/VUDUStartWizard.apk.bak
Then I shutdown the device, and start it back up normally. Then it works for me with no lock screen.

Ok originally I had come in here because of boot loop caused after removal of specific apps. This has been an issue even before I managed to get it rooted, I still wouldn't mind a streamlined fast alternate rom for my nxa10 but figured out the boot loop issue. Just go back into twrp and factory reset... it wont replace the apps you removed... kind of a weird roundabout way to debloat but hey if it works haha.

Me too!!! I need an Ares 10a ROM
I trashed the system partition on my Ares 10a. I just need A ROM... any working rooted ROM for a 10a. I had a ROM for an 8a that worked just fine... until I killed it.
So please, if anyone knows where to get a working 10a or 8a ROM would you let me know? Thanks.

Related

Kogan Agora 6 Plus root method? one click root style apps not working, any others?

Kogan agora 6 plus.
android 6.0
i tried, kingoroot, towelroot and kingroot.
All failed, i am now asking around the community on a way to root it for various reasons.
will provide more info about it when it charges.
edit:
Model number: Kogan Agora 6Plus
android version: 6.9
baseband version: MOLY.LR11.W1539.MD.MP.V10.P6, 2016/07/29 14:46
kernal version: 3.18.22
Build number: M1_PLUS_N_AU_KG_M_MT6755_65U_V1.8
custom build version: alps-mp-m0-mp7-v1.5_mlt6755.65u.m_p11
In the developer options, there is a toggle called OEM unlocking. Try toggling it and try rooting again.
I got my device rooted... it's an algerian clone of your device and you can check by yourself (google "iris next e"
At first, I thought that this device is unrootable as I tried every rooting sofrware out there and no one sorked, then I tried some adb methods and neither worked also, but then I tried the last bullet in my gun and that worked
I repacked a TWRP recovery to be compatible with the device and rooted systemlessly with supersu... now I even have exposed and magisk working
If you can make the recovery yourself then do it, if you don't I can share my repacked TWRP with you and show you step by step what to do
On the technical side, what I discovered was that there is no adbd neither adb bridge in stock recovery mode (I even looked for it in the ramdisk and found out it's not loaded) so the repacked TWRP recovery (I got the source TWRP from a Xiaomi m3 forum, the M3 has the same SoC -mt6755- which made it easy to port), I booted the recovery from fastboot and it worked like a charm
p.s: if you dont know what all I said means, don't try it, you might brick your phone!! and please don't try the m3 recovery without porting it cause it will brick your phone for sure!!
I can confirm they device looks identical, I am not very familiar with repacking TWRP, but would be appreciative if you were happy to share.
Jimmy Mossiba Floyd said:
I got my device rooted... it's an algerian clone of your device and you can check by yourself (google "iris next e"
At first, I thought that this device is unrootable as I tried every rooting sofrware out there and no one sorked, then I tried some adb methods and neither worked also, but then I tried the last bullet in my gun and that worked
I repacked a TWRP recovery to be compatible with the device and rooted systemlessly with supersu... now I even have exposed and magisk working
If you can make the recovery yourself then do it, if you don't I can share my repacked TWRP with you and show you step by step what to do
On the technical side, what I discovered was that there is no adbd neither adb bridge in stock recovery mode (I even looked for it in the ramdisk and found out it's not loaded) so the repacked TWRP recovery (I got the source TWRP from a Xiaomi m3 forum, the M3 has the same SoC -mt6755- which made it easy to port), I booted the recovery from fastboot and it worked like a charm
p.s: if you dont know what all I said means, don't try it, you might brick your phone!! and please don't try the m3 recovery without porting it cause it will brick your phone for sure!!
Click to expand...
Click to collapse
ok then: what you'll need to download is:
1. adb minimal drivers (you can find it here on xda)
2. supersu latest systemless zip (2.79 I think it's the latest version) after you've downloaded it, put it in the device's internal memory (yeah just right-click the zip file, chose "send-to" then chose your device)
3. the recovery file which is compressed in zip (unzip it and put the img file in the folder where you've installed adb - c:\adb\ )
after that, when you've got everything set, restart your device in fastboot mode: shut down the phone then put it on by hitting the power button and volume up button.. you're gonna have a three-choices menu that you're gonna scroll with the volume up button, when you've got the cursor on "fastboot" press the volume down button... the device will be put on fastboot mode.
Now back to your pc, open a command prompt, then brows to c:\adb. When you have your command prompt on adb, write this (including the quotes):
fastboot boot "TWRP 3.0.2 by Jemmini.img"
Hit enter... wait a little (while the recovery boots) and then... voila!! all you've got to do is to flash the supersu zip through the recovery and reboot: congratulations your device is now rooted
p.s: I suggest you make a full backup for all the partitions from TWRP before you do anything... you'll thank me for that
Thanks for the elaborate explanation,but I am stuck on:
Jimmy Mossiba Floyd said:
fastboot boot "TWRP 3.0.2 by Jemmini.img"
Click to expand...
Click to collapse
Cmd says that it successfully pushed and booted the image
Code:
downloading 'boot.img'...
OKAY [ 0.717s]
booting...
OKAY [ 0.070s]
finished. total time: 0.799s
...but after a couple of seconds, it reboots to system.
Any Ideas what is happening?
Long time no see hhhhh
ummm really have no idea since it works flawlessly for me but ummmm tell me: do you care if you lose the stock recovery?
I would like to try to flash it but there is a chance that it would not work , therefore having no recovery. I have unlocked my bootloader though.
Ok so instead of:
fastboot boot "TWRP 3.0.2 by Jemmini.img"
Try:
fastboot flash boot "TWRP 3.0.2 by Jemmini.img"
This is only if you're gonna take the risk... If not, just give me time maybe I'm gonna find something for you
Sorry, but I don't want to take the risk. I think the problem is that I am running Android 7.0 which differs from other versions. I have contacted Kogan to see if I can access the source code, but judging by previous threads on Kogan, it is not going to be easy.
Ah ok then I must be wrong! Because my device runs on Marshmallow 6.0 and ther must be a difference between the two (software-side)
I don't know if you can do it but, can I have a system dump so that I can bring you a fix for rooting the device?
P.S: I can assist you to make one if you want!
I am not quite sure how to dump the system (Is it "adb pull /system <whatever path>"). I have run the command, and it seems that adb can't access the /system/bin folder. Is it required for recovery porting? If not I will upload the system.
Sorry for being late, I have no DSL where I live and my data plan came to an end!! I will look for a method to dump the whole system for you. Stay tuned
Kogan has replied back and the kernel is released to the public.
https://assets.kogan.com/files/support_files/KAPHN4G6PA_Kernel/kernel-3.18.tar.gz
I am not very experienced with compiling from the kernel so some help would be nice.
I'm not really into compiling kernels... I wish I could... Gonna see with some developers in the samsung forums may be they'll be willing to help
P.S: I'm really really sorry for being late to help you with rooting the phone.. my only pc is bricked and I need it to send you the files I used to pull and push recovery to the phone
In case it's not much asking, is there a possibility to have the link for the stock firmware from kogan?
Unfortunately, Kogan did not release the stock firmware, just the kernel. I'll too go to the other forums and see if they can help.
Thank you very much for your help, and I hope that you can un-brick your pc.
Installed TWRP but it can't read internal storage.
Also wanting to root my agora 6 plus BUMP
looking for help to root
Goals:
Installing a custom recovery like trwp
Rooting
Flashing Xposed.
its on Nougat (7.0)
I can access the bootloader, fastboot and the default installed "recovery" which when loaded say something macros the lines of no commands give by booting the phone and holding both vol up and the lock/power buttons.
I'm available to talk on discord to speed things up.
I've got a bit of experience rooting the z2 and an old htc pico back in the day but i'm consider me a noob as i haven't done this kinda thing in years and don't even know where to begin.
Cryptic Bore said:
looking for help to root
Goals:
Installing a custom recovery like trwp
Rooting
Flashing Xposed.
its on Nougat (7.0)
I can access the bootloader, fastboot and the default installed "recovery" which when loaded say something macros the lines of no commands give by booting the phone and holding both vol up and the lock/power buttons.
I'm available to talk on discord to speed things up.
I've got a bit of experience rooting the z2 and an old htc pico back in the day but i'm consider me a noob as i haven't done this kinda thing in years and don't even know where to begin.
Click to expand...
Click to collapse
The thing is that I have a similar (identic) phone but Algerian brand that makes the phone is still on marshmallow!
I've still got the phone, but I don't know if my TWRP would work for you!
Quick questions:
0. Is it your daily driver phone? do you have a backup for your photos/data/important files on internal storage? just to put you in the image: I lost all my internal storage as I was playing with ramdisk modifications, hopefully my photos were cloud backed up. So be warned
1. Is your phone's bootloader unlocked?
2. Are you familiar with flashing or booting recoveries or kernels from fastboot?
after you answer I'll guide you through it
Hey thanks for the reply im thinking of teaching myself to build my own port of trwp.
0. It is my daily driver but i only just got it the other day ie. nothing important on there besides two factor authentication which even that i can reset up fairly easily. or just take the sim card out and use sms for that.
I also like to live on the edge a bit place austinpowers.jpg here(my first smart phone i got for my birthday from my rents: i got into a boot loop through flashing with in a week of receiving it and fixed on the fly at uni using the libary computers without my rents knowing my phone was broken xD)
1. Is the boot loader unlocked not sure how to check it on this phone, I do however have dev options unlocked with usb debuging etc turned on aswell as tickbox for "OEM Unlocking" with the description: allow the bootloader to be unlocked which i just have turned on .
2. Yes i do but im a bit out of practice its been years since ive messed around with root on android. Ive got logcat dumps through adb and have got fast boot working (as far as i can tell with the "fastboot" devices query) Got some help from a FB friend who is also going to try helping me make this happen. My previous experience was a HTC pico (the first smart phone i referenced earlier) and a Sony z2 which recently died dropping it which had a duel boot setup with carbon rom being the daily driver/rom.
Jimmy Mossiba Floyd said:
The thing is that I have a similar (identic) phone but Algerian brand that makes the phone is still on marshmallow!
I've still got the phone, but I don't know if my TWRP would work for you!
Quick questions:
0. Is it your daily driver phone? do you have a backup for your photos/data/important files on internal storage? just to put you in the image: I lost all my internal storage as I was playing with ramdisk modifications, hopefully my photos were cloud backed up. So be warned
1. Is your phone's bootloader unlocked?
2. Are you familiar with flashing or booting recoveries or kernels from fastboot?
after you answer I'll guide you through it
Click to expand...
Click to collapse

Unbrick Assistance Thread

Bricked your M5? Post here. I am one of three posters who have posted threads requesting assistance - we might as well create one thread where we can try and help each other.
My model? SHT-AL09 (C636). My story? I apparently made a bad change to my build.prop file, and had USB debugging disabled. I then probably dug myself a deeper hole trying to recover. I don't even get boot animation anymore. I'd happily pay someone to unbrick me.
The only potential progress I have made, is that I was able to install and successfully boot TWRP - although TWRP detects that I have no operating system installed and I am unable to mount any partitions except for my external SD card. Using TWRP's file manager, I can see that the system partition, for example, has not been entirely wiped, but many files seem to be missing. At the very least, TWRP allows me to turn the screen off without seeking to contantly reboot thereafter.
To install TWRP, I followed these instructions intended for Mate 9 owners:
duraaraa said:
This is TWRP to Mate 9/Android O, brought to you by FunkyHuawei.
It's just a preliminary build so I can't promise anything/everything will work! Keep that in mind. I'm not responsible if you brick your device.
EDIT: Does not work with Mate 10 series.
DOWNLOAD LINK:
https://drive.google.com/open?id=0B45NCsO2AL_1NEh2aDFLM3JlYkU
It works on the Android O build here:
https://www.reddit.com/r/FunkyHuawei/comments/75uwkd/october_12_first_official_android_o_beta_for/
and the official European beta.
To install:
First, have Android O running. Unlock the bootloader. Download the twrp image.
Then, run in fastboot mode:
fastboot flash recovery_ramdisk twrp_android_o_mate9_a1.img
Then, reboot holding volume up, and you've got TWRP!
Note: With the Android O update, it is no longer possible to flash the recovery2 partition. Furthermore, the names of the partitions have changed. Please keep that in mind, and don't mess around too much with TWRP, to be sure you don't brick your system!
Click to expand...
Click to collapse
Hmm ... I wanted to ask you whether you have the full OTA package for your device? So you should be able to extract all the partition images from there and to fastboot flash them. But I checked on HFF and I do not see a full OTA package matching your device yet.
AndDiSa said:
Hmm ... I wanted to ask you whether you have the full OTA package for your device? So you should be able to extract all the partition images from there and to fastboot flash them. But I checked on HFF and I do not see a full OTA package matching your device yet.
Click to expand...
Click to collapse
I've tried flashing system.img/ramdisk.img from the c00 package. Maybe I have to wait for c636 firmware, or maybe I have to flash additional .imgs. I am pretty sure that the specs and hardware I have are the same as the c00.
I've tried flashing the entire update.zip file in TWRP...but as noted TWRP is unable to mount internal storage. I'm not sure if I need to wipe and reformat first. I also have no clue whether the TWRP build I installed is properly compatible with the device. I had nothing to lose by giving it a shot.
thref23 said:
I've tried flashing system.img/ramdisk.img from the c00 package. Maybe I have to wait for c636 firmware, or maybe I have to flash additional .imgs. I am pretty sure that the specs and hardware I have are the same as the c00.
Click to expand...
Click to collapse
This will not work as the boot chain will be broken due to mismatching checksums. You need to have the correct images. To flash a OTA image you also need to have the standard recovery image installed ...
So...will someone correct please correct me if this is wrong?
If I were to flash a c00 oeminfo file, I could then install a c00 update.zip via dload folder?
Would c432 work as well (with a flashed oeminfo), even though the Euro hardware has different bands than my hardware?
There is now a full OTA on FF for C635.....still nothing for c636...
Finally, a full OTA is available for c636.
But the 'dload' method (update.app on an sd card) failed at 5%. And flashing ramdisk/recovery/erecovery/system images also failed.
Is this possibly because the OTA is B153, whereas my M5 was shipped B121?
(I hate to be that guy bumping his own thread, sorry)
I'm unbricked!
For those in a similar spot, looking to rebrand, or otherwise interested...
I finally e-mailed Funky Huawei for assistance. Their unbrick tool did not work. However, their e-recovery method worked perfectly (basically, you point your router's DNS to Funky Huawei, enter stock recovery and connect to wi-fi, and Funky Huawei's servers mimic Huawei's servers. If they do not have your firmware on their server, they will add it by request (provided it exists on the internet).
I paid $65 for a 30 day pass - a little steep, but I was impatient. I'm not sure if I could have gotten away with paying less. If you want to try and use my FH account over the next 30 days PM me (although I don't want to get carried away with that).
For those looking to rebrand, if you can flash an OEMinfo file successfully (FH has a rebrand tool and I have no clue how well it works), you should be able to use FH's erecovery method to flash firmware (don't blame me if something goes wrong).
One reason for the trouble I was having, if because I bootlooped after making a change to the vendor/build.prop file. This file was on the vendor partition, not the system partition, and for whatever reason the vendor partition cannot be flashed via fastboot (in theory it can be flashed, in reality it returns an error that doesn't have to do with the size of the partition).
Before reverting to FH, I finally got TWRP installled and functioning, and after all the attempts I made to recover my device, the same build.prop file which initially caused a bootloop was still in the /vendor folder. And TWRP wouldn't mount the system and vendor partitions as read/writeable - that was frustrating.
Now off to experiment with AOSP GSIs while I feel like I have little to lose...
Please help me
hello everyone,
i tried to rebrand my m5pro with help of ministryofsolutions. Something went wrong and my tablet (CMR-AL19) is stucked in the recovery mode. how can i fix it? Someone who ca help me? I will pay
Greeztings
Luigi
thref23 said:
Bricked your M5? Post here. I am one of three posters who have posted threads requesting assistance - we might as well create one thread where we can try and help each other.
My model? SHT-AL09 (C636). My story? I apparently made a bad change to my build.prop file, and had USB debugging disabled. I then probably dug myself a deeper hole trying to recover. I don't even get boot animation anymore. I'd happily pay someone to unbrick me.
The only potential progress I have made, is that I was able to install and successfully boot TWRP - although TWRP detects that I have no operating system installed and I am unable to mount any partitions except for my external SD card. Using TWRP's file manager, I can see that the system partition, for example, has not been entirely wiped, but many files seem to be missing. At the very least, TWRP allows me to turn the screen off without seeking to contantly reboot thereafter.
To install TWRP, I followed these instructions intended for Mate 9 owners:
Click to expand...
Click to collapse

Trying to port TWRP to 7.2 - Help needed

I might have found a quick and dirty Method to Port TWRP to the newest 7.2 shield experience. It's not guaranteed, but it's a chance im going to try. But as I didn't upgraded my own shield yet, I need some files from someone who has rooted his shield already.
1. Is an recovery.img
2. The build.prop
If I can get hands on these files I might be able to bring up a testing version asap
Enough. Seriously.....
Keep it clean, and on-topic... The rules are there for a reason. Don't remember them? HERE you go.
Adromir said:
I might have found a quick and dirty Method to Port TWRP to the newest 7.2 shield experience. It's not guaranteed, but it's a chance im going to try. But as I didn't upgraded my own shield yet, I need some files from someone who has rooted his shield already.
1. Is an recovery.img
2. The build.prop
If I can get hands on these files I might be able to bring up a testing version asap
Click to expand...
Click to collapse
If you want the files
Then can you please update your Sheild tv to the latest firmware for us 7.2.2
An back up the recovery.img
An back up your build.prob
Because I can't help you! I refuse!
Thx again have a great day
i hope you can port the twrp to nvidia sheild tv thx
Foster_e (Shield TV 2015 16GB) - 7.2.2 (30.7.130.7)
recovery.img + build.prop
https://drive.google.com/open?id=18E_u8as1E9dstmRtRwPb97hALdmsrdsc
The recovery is dumped directly from
Code:
/dev/block/platform/sdhci-tegra.3/by-name/SOS -> /dev/block/mmcblk0p16
No offense but quick and dirty does not do it on the new kernel.
You can port as much as you like and it might work for the older models but certainly not for the 2017 model.
And if you have no clue how to get the required files by simply exctracting the firmware files that you can download then I wonder how you will be able to actually modify the recovery image.
People with quite some experience tried and failed, so unless you compile TWRP from source he proper way it won't work (at least not on the 2017).
And even if compiled correctly there is no garantee it will be usable with the secure boot restrictions still in place.
You need a fully rooted device to fully use TWRP and you can not root the 7.2 in the simple way anymore.
Fully rooted the normal TWRP will work just fine.
Downunder35m said:
No offense but quick and dirty does not do it on the new kernel.
You can port as much as you like and it might work for the older models but certainly not for the 2017 model.
And if you have no clue how to get the required files by simply exctracting the firmware files that you can download then I wonder how you will be able to actually modify the recovery image.
People with quite some experience tried and failed, so unless you compile TWRP from source he proper way it won't work (at least not on the 2017).
And even if compiled correctly there is no garantee it will be usable with the secure boot restrictions still in place.
You need a fully rooted device to fully use TWRP and you can not root the 7.2 in the simple way anymore.
Fully rooted the normal TWRP will work just fine.
Click to expand...
Click to collapse
So if I understand you correctly the only way that a recent version of TWRP would work on 7.21 and above are if you have a "rooted" developer image? I have stayed with 7.1 (rooted with a flashed TWRP recovery) My expectation is that Ill stay with it until a stable version is released.
Odd thing is every OTA notification I get refuses to install. It just boots to TWRP without updating. I even opted in for the 7.2.2 beta updates and the shield refuses to update. Kinda thankful as others seem to have so many issues, just not worth it until 7.3 is released perhaps?
Any decent update is worth applying.
But if you ask if it is worth it for those really needing full root access then the answer is no.
The cummunity behind the shield might not be as big as behing Samsung devices but I am sure something will be figured out sooner or later.
@Downunder35m : As I mentioned in a deleted Post, I know how to get these Files from the recovery images. But they are Still 7.2.1 and as 7.2.2 already I didn't see a point in starting with already Outdated Files.
What kind of Things have you been trying already? My Approach was, that maybe TWRP hangs itself, because it can't find the Vendor and system Partition. After unpacking the recovery.img i found out, that the partitions still get mounted, but not over over the fstab anymore but single commands in some init scripts. So my Idea was to patch the kernel of the recovery image with a proper fstab and then use that to build a twrp around it, with the modified boot image. But sadly the resulting TWRP exceeded the Partitionsize. But i didn't set up the Source Tree to compile correctly, because I assumed that with such a breaking approach nvidia did at least moved onward to Android 8.1 ..
A real life job sadly limits my time far more than what I would like.
So maybe my failures are of use to you...
Lets start with the basics:
(All for the 2017 model!)
Firstly, the bootloader has changed and now enforces basically everything Google has on offer.
This means you can not just boot into a custom recovery because the bootloader does not accept it as genuine.
Lets say you get around this problem by, dor example, compiling TWRP from source and with the not yet realesed NVidia 7.2 sources.
There might be other ways but right now I think we can't get around compiling it from scratch.
Once you are able to somehow properly boot into TWRP there is more problems:
A lot if not all special rights and permissions are now handled almost exclusively by the DTB, or to be precise the DTS, which is compiled during boot.
By default TWRP does not make any use of the DTB but instead relies only on the FSTAB configuration.
And since TWRP is not an authorised service, task or app the bootloader won't provide the required rights.
The system partition stays invisible, the vendor part locked and since TWRP is required to copy or store at least some things somewhere this is detected as a possible intrusion.
As that the bootloader now marks the entire system as compromised - the dreaded corrupted system message appears and the system fails to boot.
You could tweak the init files, get the complete FSTAB info from the plat - and nonplat_file_contexts and even fiddle with the rest.
Then you get this happy feeling of a booting TWRP, pull a backup and think all is fine.
That it until you try to reboot and nothing works anymore.
The backup is useless as firstly you can not write it back and secondly it will be encrypted or otherwise corrupt.
To be able to use TWRP ADBD must be able to run in root mode, this is not possible by default on a user or release build, which NVidia now provides as a "developer" firmware.
A bootloader set to enforce all SeLinux and DM-Verity funtions will not allow any vital modifications to any vital part of the system.
In theory you must first at least free the bootloader (we can not do that) or destroy the safety, like by using a modified DTB.
Then you must make sure that you modifiy the prop files so full ADB and ADBD rights are available where they are needed.
After that TRWP will run just fine but it creates a cricle that first needs to be broken somehow
No root rights means no TWRP, no TWRP means no mods to the system.
Magisk currently fails to help us as it does not make use of DTB features at this stage.
And if you ask me then messing with the DTB can backfire badly.
Unlike normal firmwares we won't get a DTB partition included in the boot image or kernel image.
So once the dTB is stuffed too much it will be hard to impossible to install a genuine or custom firmware.
Once Pie comes out this will be worse.
Here the DTB too will be protected and generated/checked during boot.
Unless NVidia wakes up and removes these restrictions from the developer firmwares we will be locked out until someone finds a way to restore full root rights.
Right now I am hopin they will still release the full sources one day.
With a massive effors one could then just compile a normal userdebug firmware and all is fine once more.
Any luck yet? I upgraded one of my Shield TV to 7.2.2 from 7.2.1 dev root and want to install Magisk....
Thanks!
Here you go TWRP recovery for Shield TV 2017 running 7.2.3
UPDATE: Boots but not working correctly so removed links
leezaal said:
Here you go TWRP recovery for Shield TV 2017 running 7.2.3
https://www.androidfilehost.com/?fid=6006931924117905072
---------- Post added at 07:06 PM ---------- Previous post was at 07:05 PM ----------
Here you go TWRP recovery for Shield TV 2017 running 7.2.3
https://www.androidfilehost.com/?fid=6006931924117905072
Click to expand...
Click to collapse
Every time i open recovery it works, but after trying to reboot it bootloops at nvidia. I flash-all and it works again until i enter recovery (then botloops again on reboot). Am i missing something? (shield 2017 7.2.3 dev edition)
Here's twrp 3.3.1-0 for Shield TV. It seems to work properly on my shield pro running 7.2.3, I was able to flash magisk with it, but I don't have the 2017 model to test on. Please let me know how it works and report any errors in as detailed a manner as possible. As ever, this is experimental and you flash at your own risk :good:
https://drive.google.com/file/d/1BCfXg9pUpFm_3sPXp_nEwBlkNU9nelkg/view?usp=sharing
rootfan said:
Here's twrp 3.3.1-0 for Shield TV. It seems to work properly on my shield pro running 7.2.3, I was able to flash magisk with it, but I don't have the 2017 model to test on. Please let me know how it works and report any errors in as detailed a manner as possible. As ever, this is experimental and you flash at your own risk :good:
https://drive.google.com/file/d/1REnehReTaA5BamUBDe8XmBMyZG6zQkFB/view?usp=sharing
Click to expand...
Click to collapse
there is always the bug for 4k screen display?
rootfan said:
Here's twrp 3.3.1-0 for Shield TV. It seems to work properly on my shield pro running 7.2.3, I was able to flash magisk with it, but I don't have the 2017 model to test on. Please let me know how it works and report any errors in as detailed a manner as possible. As ever, this is experimental and you flash at your own risk :good:
https://drive.google.com/file/d/1REnehReTaA5BamUBDe8XmBMyZG6zQkFB/view?usp=sharing
Click to expand...
Click to collapse
Many thanks i renamed this to recovery.img and renamed magisk boot img to boot.img reflashed both as part of the whole 7.2.3 dev OS shield tv 2017 image.
booted into TWRP via adb from my pc it loads up fine on my LG 43" 4k tv no problem rebooted and got back into 7.2.3 also without any issues
UPDATE: TWRP will not let me wipe system / data or anything else or mount any partitions in order to wipe before trying to install anything making this sadly kinda useless right now
twrp seems complicated to be functional lately, the same on my mi max 3, but orange Fox might be better on Shield
leezaal said:
UPDATE: TWRP will not let me wipe system / data or anything else or mount any partitions in order to wipe before trying to install anything making this sadly kinda useless right now
Click to expand...
Click to collapse
Well that makes sense because I was overwriting the emmc fstab with the sata one. I've updated my original post with a link to a new twrp that should have this problem fixed. If you're still having issues please click on the menu button to the right of the home button in twrp and tell me what the log says. Do this when first booting into twrp before doing anything else. It should say something like the following with no mounting complaints if everything is working right.
Shield Debug: Hardware variant is darcy
Shield Debug: Using emmc fstab
Shield Debug: Found required fstab
rootfan said:
Well that makes sense because I was overwriting the emmc fstab with the sata one. I've updated my original post with a link to a new twrp that should have this problem fixed. If you're still having issues please click on the menu button to the right of the home button in twrp and tell me what the log says. Do this when first booting into twrp before doing anything else. It should say something like the following with no mounting complaints if everything is working right.
Shield Debug: Hardware variant is darcy
Shield Debug: Using emmc fstab
Shield Debug: Found required fstab
Click to expand...
Click to collapse
Thanks for the great feedback will DL the updated TWRP and give it a go will report back shortly
UPDATE: 100% working ! Amazing work all partitions mount etc no problem FULLY working TWRP on my 4k TV too

Huawei p30 lite root

Hello everybody.
I have a simple Question about root on this model, is it possible to do?
And if it is possible, tell me how Please.
Best regards
Wojtek
I am looking for the same too
Me too... Looks like it is still impossible
Only paid method and who knows it will be work on my p30 lite......hmm
Hello ppl,
I know this might be a little old.. any way just for the knowledge lets bring this thread back.
I had the same concern for a while, and kind of eager to get mine rooted.. until now.
I managed to unlock mine, and root it succesfully. Latest version of magisk, safty net passed, root essentials running like a charm, I can ADB in to it and su yey!
How? main issue here is my p30 lite MAR-LX3A was already in emui10, and somehow this little sucker wont allow the unlock of the bootloader regardless. I used a unlock tool that is advised to work for this model using testpoint short. how ever it was not working for me, until I read the EMUI had to be downgraded to 9.1.
Once runnig EMUI9.1 I didnt had to re-run the tool it was already unlocked. weird.
Any how the unlocker tool I used was not the ABD/fastboot tools, it was a paid app in case you are still interested in getting it done I can tell you how. Just keep in mind you will need to Open the back cover of the device.
Think is there is no custom recovery image available that works, neither a custom ROM, so all you have is pretty much root access.
I beleive this to be a pretty decent phone so I dont want just to ditch it, I am working to get a TWRP image, if I a managed to so I will get a ROM done as well. Think the whole device has been off the track for dedicated modders and devs, so it has just not been worked on.
which me luck. I'll keep you posted
I used an unlock bootloader service for 15$. First i had to downgrade my emui from 10 to 9.
I can run magisk without problem. My only problem is that i wan't super su. I was able to flash TWRP Recovery 3.2.1.0 (HiSilicon Kirin 710). But i couldn't use it because the folder are encrypted. So if anyone has any idea how to decrypt this let me know
aka_max said:
I used an unlock bootloader service for 15$. First i had to downgrade my emui from 10 to 9.
I can run magisk without problem. My only problem is that i wan't super su. I was able to flash TWRP Recovery 3.2.1.0 (HiSilicon Kirin 710). But i couldn't use it because the folder are encrypted. So if anyone has any idea how to decrypt this let me know
Click to expand...
Click to collapse
I'm gonna look for that TWRP img, I didnt find a working one acutally. is there a specific reason why you rather use super su ?
about encryption you usually need to make sure there is no password configured, I read somewhere about a guy that had his Face recognition still configured, and that was the reason he was unable to unencrypt. there are some zips you can flash somwhere around, but never tried them
blzbh said:
I'm gonna look for that TWRP img, I didnt find a working one acutally. is there a specific reason why you rather use super su ?
about encryption you usually need to make sure there is no password configured, I read somewhere about a guy that had his Face recognition still configured, and that was the reason he was unable to unencrypt. there are some zips you can flash somwhere around, but never tried them
Click to expand...
Click to collapse
I deactivated all passwords etc. But it didn't work for me. The only reason i need supersu is because i wan't recover some deleted contacts and mails after factory reset. And those Windows applications with real deep scan not works with magisk.
aka_max said:
I deactivated all passwords etc. But it didn't work for me. The only reason i need supersu is because i wan't recover some deleted contacts and mails after factory reset. And those Windows applications with real deep scan not works with magisk.
Click to expand...
Click to collapse
why dont you try getting an image of the partition with DD, convert it and mount it in the PC directly, I beleive using the scan software directly against the phone is more complicated than just scanning a directly attached block device.
Hello
Is there any way to decrypt the Huawei P30 Lite?I haven't found anything anywhere.
i have twrp on it but the system is encrypted :-(
i have read some posts about wipe data.. use stock rom etc... But i am to lazy to test it. Let me know if it will works. Be sure to make a backup before playing around
nominator64 said:
Hello
Is there any way to decrypt the Huawei P30 Lite?I haven't found anything anywhere.
i have twrp on it but the system is encrypted :-(
Click to expand...
Click to collapse
there are a few things to try... you can go to wipe menu in TWRP then use the fix/repair option against the system encrypted partition..
-try reparing it
-try changing the partition from ext4 (check first the type usually ext4) to ext2, then change it back to what it was, ext4
last resource:
-wipe all data/factory reset ***** You WILL loose all your personal data if you do this **** just make a backup MANUALLY before doing this.. if you use TWP backup pbby your back will be encrypted too...
I manage to get mine unencrypted with this last step, took a few attempts, but had to reflash Stock so its back to encryption
Maybe we should create our own TWRP version for the p30 lite. There are many tutorials ^^
aka_max said:
Maybe we should create our own TWRP version for the p30 lite. There are many tutorials ^^
Click to expand...
Click to collapse
agreed I have been working on one that truely works, but there are a few blanks about how TWRP really works.. and its boot process. I have learned a little this past week, but still think gonna have to reverse engineer a working img to get some answers.... I was actually thinking on building a orange fox image better not sure what would be easier..
I have lots of work so I do this in my free time, but let me know if you want a help perhaps we can get something and port a nice ROM that's worth the device
.
blzbh said:
there are a few things to try... you can go to wipe menu in TWRP then use the fix/repair option against the system encrypted partition..
-try reparing it
-try changing the partition from ext4 (check first the type usually ext4) to ext2, then change it back to what it was, ext4
last resource:
-wipe all data/factory reset ***** You WILL loose all your personal data if you do this **** just make a backup MANUALLY before doing this.. if you use TWP backup pbby your back will be encrypted too...
I manage to get mine unencrypted with this last step, took a few attempts, but had to reflash Stock so its back to encryption
Click to expand...
Click to collapse
thank you for the suggestions. unfortunately does not work :-(
Please keep us posted, really excited to see a custom rom for this phone, also could you elaborate on the process of unlocking the bootloader? My back cover is already broken so I have to open it up anyways
k.r.o.o.k said:
Please keep us posted, really excited to see a custom rom for this phone, also could you elaborate on the process of unlocking the bootloader? My back cover is already broken so I have to open it up anyways
Click to expand...
Click to collapse
Sure, ive been busy but will try my best.. about the unlock process I end up paying 19 euros... But try using fastboot unlock first.. may save you the money not sure...
1. Downgrade to emui 9.1 .. just plug the p30 lite to PC, install hsuite... Go for the firmware/software update... A pop up screen will show up with some small letters buttom rigth.. older releases or revert to older firmware something like that.. you will get too choose 9.1 only ... Choose that and apply.. Keep an eye out.. this will delete everything in your phone... Next boot you will be in 9.1.. avoid the automatic upgrade.
2. Turn the phone off, take the back cover and locate the testpoints.. short by using metal wire... The small aluminium wire wraps that come with bread and other bags for easy close are usefull just remove some plastic in each side... connect the usb cable to PC.. leave the phone side unplugged.. Touch test point with the wire while the other side touches a metal cover in the phone.. while doing it plug the phone to the USB cable.. the charging animation should not appear . . . Screen must stay black.. otherwise do it again.. if done right the device manager will detect COM port for your device
Identify the point with this video
3. use either app you want to detect testpoint mode and unlock... I managed to do it with a 3 day unlimited license for HCU client.. that did the trick their website have some tutorials easy to follow.
Hi all,
I have the same problem like a few other people. I unlocked the phone with HCU, and after I tried to root with magisk (by trwp) But the main issue, the phone is encrypted and the installation proccess of the magisk by the trwp got failed. How can I root this phone? Anybode has success with this?
Thank you!
huawei p30 lite device root support please

SOLVED!!!! [MTK][Bricked] Flashed incompatible TWRP on a rooted TCL 20 XE, bootloops now.

SOLVED!!! Thanks to tankmc in post #6 and #7, I was able to get my device booted back up.
I used MTKClient to root and unlock the bootloader of my TCL 20 XE, however, the TCL 20 XE is just so uncommon in the modding and hacking community (and only really known as a cheap burner phone) that there was no official guide nor official custom ROMs or recoveries. I used twrp-3.2.1-0-twrp.img to try and flash TWRP. I tried using the official TWRP app to flash it with root with Magisk, however it didn't boot up. I then used MTKClient to try to flash the same file and it still bootlooped. It didn't even show me the Orange State warning that shows on devices with unlocked bootloaders without the patch. It wouldn't boot when I held Power+VolUp, Power+VolDn, Power+VolUp+VolDn, and just power. I was only able to shut the device down with python mtk reset on MTKClient. It doesn't seem to boot to Android at all, and just shows a black screen. I have a Magisk module called Nexus Media, so I will tell if it touched Android at all, and no this module didn't break anything.
The TCL 20 XE has 3 GB of RAM, an MediaTek MT6762, and Android 11 on TCL UI 1.0.PB7NUBN2. This model is locked to Boost Mobile and the model number is 5087z. It is sometimes referenced to as an Alcatel TCL 20 XE.
This is a link to 4 photos of the TCL 20 XE showing Magisk, Root Checker Basic, and Device Info. This may be useful but I don't think so.
Here is another 3 links to the phone on Walmart, some may give more info on the phone than the others but this may be useful too: Link 1 | Link 2 | Link 3
I might be able to fix this if I can get ahold of the stock recovery.img and vbmeta_system.img as I can easily flash those to the partition and probably fix my problem.
I don't know how, but it now shows the Orange State warning, and how it bootloops is it shows the TCL powered by Android screen with the bugdroid, and then shows a black screen, vibrates, and goes back to the TCL powered by Android screen, and repeats unless stopped by MTKClient or a dead battery.
3 GB RAM -> less is hardly possible, IMO.
I'm pretty sure I do have the original recovery saved in /sdcard/Documents/stock-recovery.img, but I can't use ADB to try and pull the file, however running "python mtk r userdata Documents/stock-recovery.img" does seem to be running and pulling the file.
I might just need to flash this and be done, nvm.
jwoegerbauer said:
3 GB RAM -> less is hardly possible, IMO.
Click to expand...
Click to collapse
wow......thanks i guess...??
Nostii said:
I'm pretty sure I do have the original recovery saved in /sdcard/Documents/stock-recovery.img, but I can't use ADB to try and pull the file, however running "python mtk r userdata Documents/stock-recovery.img" does seem to be running and pulling the file.
I might just need to flash this and be done, nvm.
Click to expand...
Click to collapse
Doesn't work, I am unable to pull the file and reflash. I need to buy or borrow another TCL 20 XE to grab the recovery and pull it, unless someone has a computer with MtkClient and a TCL 20 XE and is willing to rip the recovery off, I might just need to go to my local Walmart and pick one of these phones up, however it might just be easier to buy a phone that is better known in the Android hacking community.
This is the boot, recovery and vbmeta from my TCL 20 XE. The vbmeta_empty.img is from the mtkclient zip that is used when rooting. The boot img is rooted. This phone is funny with root tho. It loses root when you open the super user tab in magisk and I've had no luck mounting it rw. But I can change build.prop with the resetprop cmd in terminal thru magisk, among other workarounds . Flash the recovery to hopefully unbrick it.
Oh and the vbmeta_system that you requested. Good Luck
tankmc said:
This is the boot, recovery and vbmeta from my TCL 20 XE. The vbmeta_empty.img is from the mtkclient zip that is used when rooting. The boot img is rooted. This phone is funny with root tho. It loses root when you open the super user tab in magisk and I've had no luck mounting it rw. But I can change build.prop with the resetprop cmd in terminal thru magisk, among other workarounds . Flash the recovery to hopefully unbrick it.
Click to expand...
Click to collapse
Thank you so much!! I didn't think anyone else here on XDA had a 20 XE, and the internet didn't have anything for me.
Commands below are the commands I ran with MTKC 1.6.1 to get my device back up:
python mtk w vbmeta_system vbmeta_system.bin
python mtk w recovery recovery.bin
python mtk w vbmeta vbmeta_empty.img
Thanks again!! I thought I would have to buy another TCL to restore this one or throw this one away and root the new one (or better yet, get a phone known in the modding community). I kinda wish I didn't wipe my userdata now since thats all I had to do

Categories

Resources