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
Related
I have the LG v10 from T-Mobile. I bought the phone a few weeks ago and it had Marshmallow installed. Somehow I managed to install TWRP/SuperSU, but then had issues and flashed the official/stock MM image with LGUP. Afterwards I discovered that MM for this device is not currently rootable, and TWRP cant be flashed via fastboot because MM blocks it. So I returned the device to T-Mo store, lied and said it force-upgrade to MM and had began freezing up. They did an in-store trade for an identical model that had 5.1.1 Lollipop.
The device is currently still in factory condition in every way, with the exceptions that I unlocked the bootloader via fastboot and installed TWRP. Nothing else is modified yet and no custom ROMs have been flashed.
I recently became aware that there is no stock LP image for the T-Mo v10, only MM images are available. After all the issues I've had, I'm now paranoid and want to have a complete dump of the phone's entire contents (partitions, bootloader, system, etc) that is in KDZ or TOT format, and can be reflashed with the standard tools available. Since there is nothing official then I would have to do this myself. This would be useful in the event that I run into lots of issues and need to do a emergency stock restore.
I found a thread by XDA user @tungkick, in which he created a modified dump of the device while it was running LP. However, because it was unofficial and he didn't disclose this upfront, his thread was shut down. His file bricked multiple MM users. I assume it would work if one was still on LP and hadn't upgraded to MM. Not to mention that I cant seem to find his file anywhere. So I figure the safest way is to do this myself. I would be willing to make this file available to the community when finished, with full disclosure that it is unofficial. But the problem is, I don't know how.
I know that the Linux dd command can be used to dump images of various things, and I have read that this can be done on PC by connecting to the device via ADB or fastboot. This would hopefully result in an image file that contained the contents of all the device's partitions.
But another issue would be converting it to KDZ or TOT. And it would have to be done in such a way that it would be flashable with the standard tools.
Can someone please give me a technical understanding of the tools and knowledge I would need to undertake this? Would it be too complicated for someone like myself that has little Android/Linux experience (but is generally competent with computers/technology)?
Thanks for any advice!
Noone can help me with this?
To the mods/admins: I think maybe I posted this in an area where it is unlikely to get any useful answers. Can someone move the thread to the Help& Troubleshooting area of the general LG v10 forum (not here in the T-Mobile subforum)? Thanks!
I think it's just that if that could. have been done someone would have done it already. Even tungkick didn't make one for tmobile for some reason. I think because he made his root injected files from official lg files and lg has not released a kdz or tot for tmobile LP.
Just my observation... I could be wrong.
Sent from my pretty nifty brand new LG V10
@ planetbeen: I don't see why it wouldn't be possible. Linux's dd program can dump almost any connected device that it can see. But then it needs to be converted into a standard TOT/KDZ that can be flashed with any standard software. Which is why I want to create an unofficial backup of the entire phone before modifying it further, so I can do an emergency restore if necessary. I just need the right instructions from people who have the technical expertise.
I had trouble with my old LG v10, I had used LG's LGUP program to flash it to Marshmallow from my PC, only to realize that it couldn't be rooted or have a custom recovery. And I also discovered that I couldn't downgrade to Lollipop. So I returned the phone to the store and exchanged it for an identical model that still had LP. I just told them it had auto-upgraded to MM and started crashing. They exchanged, no questions. Before this I had various issues, like GPS crashing randomly when turning it on, Bluetooth also doing the same thing, and the Settings app also crashed sometimes when accessing the Security menu. I had flashed multiple ROMs, but stock-based and CM/AOSP-based, but kept running into issues, oftentimes the same ones. So I figured that something in the phone had become corrupt and figured that flashing stock MM would fix everything. Big mistake. I'll never let this phone upgrade again until MM is solidly hacked, which from what I've read may be a long time away. I paid enough for this phone and I really value hackability. I'm not the average Joe that just uses my phone for Facebook, etc. To me, if a phone cant be hacked, then buying/owning it is a waste of time/money. Same thing with every computer/electronics device I've ever owned.
Thanks again!
It looks like I'm going to have problems getting answers from knowledgable people, so instead of waiting, I'm going to take a little initiative and at least try to do the dump with dd. I found a post by @tungkick that says to enable USB debugging and make a backup file via dd with the 'adb shell' and 'su' commands. Is the following syntax correct?
dd if=/dev/block/mmcblk0 of=/sdcard/H901.bin bs=1024 count=6291456
Do I run these commands from a PC via command line while connected via USB? Or directly on the device in a terminal emulator? Or do I need to run the command while in fastboot/bootloader mode, while Android is powered down?
Thanks again!
Stock use tool extract kdz then choose file dz (use lgup)
remember can not flash if phone update 6.0
Never downgrade because phone brick now.
version 5.1.1
https://drive.google.com/file/d/0B_Hol5T47S-bQkJVemgzMDV0Nzg/view?usp=sharing
@ tungkick: Thanks for the info. I had used the dd command to dump my phone to external SD before, but the file was 6GB! I was unable to use Tool KDZ Extract to extract the *.dz from the *.kdz file you provided. I was able to flash your KDZ with LGUP, but it boots me into TWRP recovery near the end.
Do you mind if I publicly distribute a mirror copy of your file on my Dropbox, so that it will be available to others that need the stock LP firmware for this device?
Thanks again!
I just wanted to say that flashing your KDZ has possibly screwed up my device permanently. Your image has TWRP, not the stock recovery, and is pre-rooted with SuperSU. Normally this would be good but...............
Near the end of LGUP, the device boots into TWRP. System and MicroSD are mounted, but nothing else (data, cache, dalvik, etc). I was able to obtain a stock recovery *.img, then copied it over to my MicroSD while in recovery. Then I flashed it, booted the phone into stock recovery, and performed a factory reset. Afterwards I booted into system, and all looked good, until it got to the "Checking connection" screen, then a lot of apps started force-closing repeatedly. Because of this I can't get to the Home screen, and no amount of factory reset is working. It just keeps happening over and over again.
How to get out of this mess, anyone?
Help please!!!
Still looking for a solution and would really appreciate any help!
My theory is that the /cache and /data partitions somehow got corrupted during the flash. So I tried booting into FastBoot mode and issueing the commands:
fastboot erase cache
fastboot format cache
fastboot erase userdata
fastboot format userdata
It just says something something along the lines of "remote: cant format/erase in an unlocked state". If I relock the bootloader, it says that it cant erase/format in a locked state.
TWRP still cant read those partitions (they won't mount and cant be mounted), and the apps still start force-closing almost immediately after rebooting into system, before I can complete the setup, preventing me from getting to the home screen.
@ tungkick: Is there any possibility we can arrange a TeamViewer meeting to fix this?
Thanks!
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.
I can turn this into a guide if we get the right info.
I have used DC-Unlocker to unlock bootloader and FRP.
I installed v20 Phh Generic System Image via fastboot flash system.
my FRP is locked now and bootloader unlocked, and oem unlock greyed out.
i am investigating a solution and maybe it can help others.
Recovery:
can flash updates if bootloader and frp is unlocked
eRecovery:
i can connect to wifi, but no firmware is found
DLOAD:
updates performed with vol down+up+power
using the update extractor i can get the UPDATE.APP from the official firmware (SHT-W09C432B151 (8.0.0.151) i think for me)
but UPDATE.APP is over fat32 4GB limit. so i cant put it on the SDCard - and im not sure if the recovery can read exFat.
i tried with both but they fail immediately.
placing the files in the internal storage with DLOAD folder seems to send update to 5% then fail.
HWOTA:
seems to be a method used on older devices - not sure if it will work to flash this device.
the sh. script seems fairly straightforward so maybe it can be modded to work with this device
Device: SHT-W09 M5 8.4 (eu)
Build Number: 8.0.0.151 (C432)
OS: Stock 151 with Phh GSI applied
ive never had a device this difficult to recover. samsung had odin to flash firmware, nexus 5/7/9 always had a way out - when i was building roms for moto xoom it wasnt this difficult.
Good luck man, it seems like when this thing bootloops, it activates some sort of defense mechanism that makes recovery particularly challenging.
I bootlooped after editing my vendor/build.prop file. DLoad method failed. Flashing partitions via fastboot failed. Stock recovery failed. TWRP became available, and I got it working...but no partitions would mount r/w. I paid to use Funky Huawei's unbrick tool, and it failed.
Funky Huawei's eRecovery method is basically all that worked for me. But I paid to use it (I still have a few weeks remaining on a pass).
These instructions, which don't involve payment to Funky Huawei, might or might not work:
https://forum.xda-developers.com/mate-9/how-to/funky-huawei-erecovery-solution-100-t3620165
Thanks for the alternative method.
I tried with hisuite using firmware finder, it uses the same funky DNS server. When I start the process the download works fine then on hisuite it says installing, does nothing then fails. After I reboot (usb in pc, all 3 buttons) it shows a usb symbol - installing but hangs at 5% for ages.
I tried with a portable router with ERecovery and it did not work unfortunately still failed to get info
I had to result to funkyhuawei who have now added SHT-W09C432 to their system.
In the 30 days I have this I'm tdetermined to find alternative solutions to fix this issue like all other devices tend to have.
I battled it out with Huawei support and there's no chance of an frp key - at least first 3 attempts. Also tried to get them tonexplqin ERecovery but said it's for insiders only just for service repairs. They have no regard for helping developers.
I was trying to figure out where the file get stored on ERecovery so if we could adb push to it and hold vol down + up + power to recover the device. I found i could pull from /dload (not internal/externalsd) which contained firmware_update_dload.zip but when uncompressed e enwbti be referenced to Qualcomm chips.
Any ideas on patching the recovery or boot image to prevent frp lock?
I also tried to see if there is a way from adb (while OS is running) to flip the OEM unlock back to on but there's nothing in system/global/settings that represents that.
It's strange because frp should not lock if you log back into the same account.
LOGMD said:
DLOAD:
updates performed with vol down+up+power
using the update extractor i can get the UPDATE.APP from the official firmware (SHT-W09C432B151 (8.0.0.151) i think for me)
but UPDATE.APP is over fat32 4GB limit. so i cant put it on the SDCard - and im not sure if the recovery can read exFat.
i tried with both but they fail immediately.
placing the files in the internal storage with DLOAD folder seems to send update to 5% then fail.
.
Click to expand...
Click to collapse
Any conclusions why this metod isnt working? On older device this works everytime if you do it right but not on this device? is it a Oreo thing or is it because the UPDATE.APP is so big?
omaga said:
Any conclusions why this metod isnt working? On older device this works everytime if you do it right but not on this device? is it a Oreo thing or is it because the UPDATE.APP is so big?
Click to expand...
Click to collapse
In my experience using the Huawei P9 the only time I was successful upgrading the firmware from the dload folder was when the firmware version ended with MF-PV (Public Version). Even though Huawei releases versions of the firmware without the MF-PV extension from what I read these versions are for testing purposes only.
In addition to my reply to you in the 8.0.0.163 firmware update thread there is a tool called HuRUpdater that has a similar upgrade procedure to the one I described when I upgraded the firmware on my SHT-AL09 from 151 to 163.
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
OK, thanks for this info, of course I thought that this device would be as easy to utdate then my much older M2-801L via dload which worked every time. And thanks for the tool tip, I'm looking into that thread as well :good:
Butch1326 said:
In my experience using the Huawei P9 the only time I was successful upgrading the firmware from the dload folder was when the firmware version ended with MF-PV (Public Version). Even though Huawei releases versions of the firmware without the MF-PV extension from what I read these versions are for testing purposes only.
In addition to my reply to you in the 8.0.0.163 firmware update thread there is a tool called HuRUpdater that has a similar upgrade procedure to the one I described when I upgraded the firmware on my SHT-AL09 from 151 to 163.
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
Click to expand...
Click to collapse
Thank You for the info.
Used it to update my CMR-AL19 and worked like a charme
omaga said:
Any conclusions why this metod isnt working? On older device this works everytime if you do it right but not on this device? is it a Oreo thing or is it because the UPDATE.APP is so big?
Click to expand...
Click to collapse
Sorry for the late reply had some busy months!
So from what I remember it's because the UPDATE.APP was too big. I tried recreating the update.app without the non-essentials but I couldn't get it working.
Huawei support when I asked about how to update via recovery just kept saying it's only for technicians at Huawei so they won't help me in any way!
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
Credit to @user_ScoTTT
1. First of all, you need to sign up and login on the official website of Oppo in China. (Use Google Translate if you need to)
https://bbs.coloros.net/graphic?id=1498611
2. Follow the links and download the unlock program of Oppo Find x2 /x2 pro
3. Install the apk on your phone
4. Ensure your device has the latest version of your ROM installed.
5. Click "Start Applying" on the Unlock App. You will need to wait about a month. After a month, open the application, and if "Approved" is displayed, please go to the next step.
If not, Force Close the Application several times over and over, and maybe it will display "Approved".（Some Chinese citizens reported a similar situation.）If you still can't, please contact oppo online customer service, they can solve this problem for you.
6. Next, please back up your data.
7. After receiving the 'Approval' in the app.
Go to Settings - about mobile phone - version information - version number Click here five times.
Go to settings - other settings - Developer options then Check OEM unlock.
8. Once again, open the Deep Test application and click "Start the Depth Test". The phone will automatically restart and enter Bootloader mode.
9. Connect your phone to the computer.
10. Open the command prompt browse to your adb/fastboot location and enter
"fastboot flashing unlock"
then confirm. At this time, the mobile phone will give some warning information. Please read it carefully before making a decision.
If you decide, choose "unlock the bootloader" and press the power key to restart. It is worth noting that the phone will be formatted here. If you have opened "find my phone" before, you need to enter your oppo account password to start your phone.
11. You now setup your phone as normal though with an unlocked bootloader.
12. If you wish to Root then please see this guide: https://forum.xda-developers.com/find-x2-pro/how-to/magisk-root-install-unlocked-bootloader-t4157327
can i flash global rom after unlocked bootloader ?
i was wondering the same thing. i dont see why not. give it a shot and let us know. you have nothing to lose it will simply not let you flash if it doesnt work and your existing ROM/Phone will be unaffected.
Ok, so I've unlocked my Chinese Find X2 Pro using the official method, which is by using the depth testing app and waiting for approval, then unlocking via Fastboot.
But I still can't flash the global ROM using the stock ColorOS recovery. I've tried various versions, just either get the 'Installation failed' or 'The installed version is lower than current' error.
Do I need to wait until TWRP is available for the X2 Pro or is there another way? I don't want to root, just install the stock ROM from another region. Will Magisk allow me to do this?
Was really hoping unlocking the bootloader would do it, guess it's a good start
bugger.. it would appear that the ColorOS Recovery is preventing the install. So yes you would need TWRP or someone to hack the ColorOS recovery to flash without the check.
though with an unlocked bootloader you can flash TWRP as soon as it's been developed by someone.. or risk flashing a twrp from a similiar phone?
Bugger indeed, I've bricked it! Tried various ways to do it as really need to get rid of this Chinese ROM. I flashed a Boot image from a global version, didn't work. Then flashed the Chinese version back.
So then in a bold (stupid) move I tried to flash other images from the global ROM - now won't load into recovery at all. With nothing to lose I tried loading TWRP recovery from one of the latest Realme phones this morning, didn't fix it.
What is weird is in Oppo / Realme ROMs there is no recovery image - not sure if it's part of the boot image?
Does anyone know how to obtain a recovery image? I think this is what I'm missing. Thinking maybe it's not part of the ROM on these devices.
---------- Post added at 04:27 PM ---------- Previous post was at 04:22 PM ----------
And FYI, I've been using a python tool to decrypt the ozip files. Have looked in multiple ROMs, beta and standard, Chinese and global and even a few Realme ROMs.
I'm starting to hate Oppo, it's even more of a pain in the ass than Samsung! :silly:
I bought a Xiaomi Mi Mix 3 5G yesterday off eBay just to get me by for the time being, it was a carrier version and I managed to get the stock global ROM with MI12 on it in 30 minutes using fastboot and flashing all the images. Refreshingly easy
klanbo78 said:
Bugger indeed, I've bricked it! Tried various ways to do it as really need to get rid of this Chinese ROM. I flashed a Boot image from a global version, didn't work. Then flashed the Chinese version back.
So then in a bold (stupid) move I tried to flash other images from the global ROM - now won't load into recovery at all. With nothing to lose I tried loading TWRP recovery from one of the latest Realme phones this morning, didn't fix it.
What is weird is in Oppo / Realme ROMs there is no recovery image - not sure if it's part of the boot image?
Does anyone know how to obtain a recovery image? I think this is what I'm missing. Thinking maybe it's not part of the ROM on these devices.
---------- Post added at 04:27 PM ---------- Previous post was at 04:22 PM ----------
What method were you using to flash mate?
I had a look at the extract of the Global ROM and can see a heap of img files.. though your right there is no obvious Recovery image file.
That is strange. As the device has a Recovery mode. It would be very strange to make it part of the Boot Image. Surely Oppo has a recover tool that just puts everything back to default?
Click to expand...
Click to collapse
Sage said:
What method were you using to flash mate?
Click to expand...
Click to collapse
Just using the adb toools via command prompt on my PC and phone on fastboot mode.
I.e. fastboot flash boot boot.img
There's no system image either, only vbmeta_system.img which I don't think it's the same thing. Watching YouTube videos and searching the internet now to try and figure out
Finally managed to get the phone back up and running after brushing up on Linux and downloading various tools. Basically this thread saved me!! https://forum.xda-developers.com/realme-x50-pro/help/stock-recovery-image-t4111477/page6
As mentioned, the recovery image is not to be found in the firmware. So once you decrypt the Ozip file (using python tool like the one in the above post), you'll see the boot.img file along with various others, but no system, vendor or recovery images. Using the UR-Tool mentioned and a simple linux command I managed to create a recovery image.
Flased it using fastboot and now all working - still on Chinese ROM though. Next step is to try to flash the global image onto this Chinese variant - expect I'll brick it again
klanbo78 said:
Finally managed to get the phone back up and running after brushing up on Linux and downloading various tools. Basically this thread saved me!! https://forum.xda-developers.com/realme-x50-pro/help/stock-recovery-image-t4111477/page6
As mentioned, the recovery image is not to be found in the firmware. So once you decrypt the Ozip file (using python tool like the one in the above post), you'll see the boot.img file along with various others, but no system, vendor or recovery images. Using the UR-Tool mentioned and a simple linux command I managed to create a recovery image.
Flased it using fastboot and now all working - still on Chinese ROM though. Next step is to try to flash the global image onto this Chinese variant - expect I'll brick it again
Click to expand...
Click to collapse
Impressive mate well done! And thanks for posting the solution! With a recovery.img file you are now free to experiment! I hope you get the Global Working! Please keep us up to date!
Can you upload the recovery.img to help the community?
Sage said:
Impressive mate well done! And thanks for posting the solution! With a recovery.img file you are now free to experiment! I hope you get the Global Working! Please keep us up to date!
Can you upload the recovery.img to help the community?
Click to expand...
Click to collapse
You will be the first person in the world to have an unlocked bootloader on the Global ROM!
surely with some combination of Global and Chinese it will work!
Chinese Recovery -> Global Boot -> Global ROM -> Chinese Vendor
Global Recovery -> Global Boot -> Global System -> Chinese Vendor
Chinese Recovery -> Chinese Boot -> Global System -> Global Vendor
etc
etc
Sage said:
You will be the first person in the world to have an unlocked bootloader on the Global ROM!
surely with some combination of Global and Chinese it will work!
Chinese Recovery -> Global Boot -> Global ROM -> Chinese Vendor
Global Recovery -> Global Boot -> Global System -> Chinese Vendor
Chinese Recovery -> Chinese Boot -> Global System -> Global Vendor
etc
etc
Click to expand...
Click to collapse
Thanks for your support
I'll upload the recovery images for the global and Chinese variants once I'm back on my desktop later.
So the issue I'm facing now is it this phone doesn't have a system, vendor or product partition. My assumption is that I need to flash the global system image, as that's the one that basically contains the OS.
I think that these images are contained within the "super" partition which appears to be a dynamically resizable partition. I have no idea how to flash to these!
I'm trying to make sense of it all but fastbootd has come up a few times, which apparently is needed to flash to userspace which is where this super partition resides.
I can see in the ROM there is an updater script file that refers to these images, create groups in the super partition and resizes them as necessary. It seems to use the vb_meta_system image in some way. I have no idea how to replicate this script in fastboot though or if it's even possible?
Can anyone help?
---------- Post added at 08:59 AM ---------- Previous post was at 08:46 AM ----------
A bit of info on dynamic partitions...
https://source.android.com/devices/tech/ota/dynamic_partitions/implement
vbmeta.img removes the boot verification so you definitely want to use that. see this thread for its use.
https://forum.xda-developers.com/find-x2-pro/how-to/magisk-root-install-unlocked-bootloader-t4157327
I downloaded the depth testing app but the submit application is greyed out. Any tips on what to do?
golemagg said:
I downloaded the depth testing app but the submit application is greyed out. Any tips on what to do?
Click to expand...
Click to collapse
I know they have a monthly quota, perhaps it's been reached this month.
Or maybe the servers are down? there were a few days during my application that I couldn't check the status, just assumed the server was offline - perhaps it's something like that.
Maybe just wait a few days and see.
Where is you download the app from? And do you have the Chinese variant?
klanbo78 said:
I know they have a monthly quota, perhaps it's been reached this month.
Or maybe the servers are down? there were a few days during my application that I couldn't check the status, just assumed the server was offline or something like that - perhaps it's something like that.
Maybe just wait a few days and see.
Where is you download the app from? And do you have the Chinese variant?
Click to expand...
Click to collapse
Understood. I'll keep monitoring it. Thanks a lot for the information.
klanbo78 said:
Finally managed to get the phone back up and running after brushing up on Linux and downloading various tools. Basically this thread saved me!! https://forum.xda-developers.com/realme-x50-pro/help/stock-recovery-image-t4111477/page6
As mentioned, the recovery image is not to be found in the firmware. So once you decrypt the Ozip file (using python tool like the one in the above post), you'll see the boot.img file along with various others, but no system, vendor or recovery images. Using the UR-Tool mentioned and a simple linux command I managed to create a recovery image.
Flased it using fastboot and now all working - still on Chinese ROM though. Next step is to try to flash the global image onto this Chinese variant - expect I'll brick it again
Click to expand...
Click to collapse
Can you please upload the recovery.img for people to use?
any other progress to report?
Sage said:
Can you please upload the recovery.img for people to use?
any other progress to report?
Click to expand...
Click to collapse
Yeah, that would be really nice. I couldn't boot also in recovery after android 11 beta:silly:
Sage said:
Can you please upload the recovery.img for people to use?
any other progress to report?
Click to expand...
Click to collapse
Here's the link to the recovery (and boot) images, have zipped them as they're quite large. I've included both variants (so PDEM30 and CPH2025).
https://drive.google.com/drive/folders/1HkNeQSuzsPDdue4KqRbDWLah0YH-CSwb?usp=sharing
In terms of progress, there is none. I got a bit adventurous and decided to flash all of the partitons on my PDEM30 with the images from the CPH2025 (manaully as there is no "flash-all.bat" file in the OTA ROM). I think it would have worked as it has for phones I've flashed this way in the past, but as I now know phones that launced with Android 10 are quite different due to having a dynamic "super" partition. This super partition contains the system, product, vendor image, etc. It should not (can't be) be flashed from fastboot as it's held in the "user space" of the phone and fastboot doesn't know how to deal with these partition types.
Pixel devices have a program called fastbootd which I think can be used for this, but Oppo doesn't appear to have that mode. Basically the phone now won't boot to recovery at all, I can only get into fastboot mode.
Not even worth holding out for TWRP as as of right now, TWRP doesn't support these dynamic partions (so any phone launced with Android 10). I contacted Oppo UK support and they said I could send in for repair, but then got told by the company who would be doing the repair (SBE UK) that they only support UK and EU devices. So looks like it might be going back to China for a repair (just need to find a freind who speaks Chinese )
Before that though I'm going to see if I can edit the recovery.img in Android Kitchen, to see if I can find the bit that's responsible for it not booting into recovery mode. I think at this point I have nothing to lose!!
I can't download unlock program of Oppo Find x2 / x2 pro, can you help me download it, thanks