My device is YU YU4711 , rooted, then I flashed TWRP via fastboot, then using TWRP I backed up the stock ROM , and then flashed RR ROM (7.1.2), it was working fine , but then I thought of flashing RR ROM (6.0) , In the process to do so I couldn't erase the system to flash new ROM (failed to mount system) , so I was on TWRP and I accidentally changed my partition format and since then I have no ROM installed , no internal storage partition , I have TWRP and it shows internal storage (0 mb), I have checked other threads too but found no solution . please please help me .
I'll soon post snaps of the TWRP , and let me know if you need any other information
zap456 said:
My device is YU YU4711 , rooted, then I flashed TWRP via fastboot, then using TWRP I backed up the stock ROM , and then flashed RR ROM (7.1.2), it was working fine , but then I thought of flashing RR ROM (6.0) , In the process to do so I couldn't erase the system to flash new ROM (failed to mount system) , so I was on TWRP and I accidentally changed my partition format and since then I have no ROM installed , no internal storage partition , I have TWRP and it shows internal storage (0 mb), I have checked other threads too but found no solution . please please help me .
Click to expand...
Click to collapse
Hello...!
Try googling "YU YU4711 stock rom". There seem to be enough answers there to your problem.
Most likely you will need:
1. stock firmware
2. Qualcomm USB Driver
3. YU USB Driver
4. Qualcomm Flash Image Loader (QFIL)
Take a look here also!!! https://forum.xda-developers.com/yu-yunique/development/guide-flashing-stock-rom-yu-yunique-t3219897
r&xp said:
Hello...!
Try googling "YU YU4711 stock rom". There seem to be enough answers there to your problem.
Most likely you will need:
1. stock firmware
2. Qualcomm USB Driver
3. YU USB Driver
4. Qualcomm Flash Image Loader (QFIL)
Take a look here also!!! https://forum.xda-developers.com/yu-yunique/development/guide-flashing-stock-rom-yu-yunique-t3219897
Click to expand...
Click to collapse
Thanks for the quick reply , I will download these files asap and flash the firmware , A question , does flashing the stock firmware fixes the partition problem , there are no /internal storage or /data partitions to be mounted .
I had this problem before , it's so simple , learn how to use the ADB SIDE LOAD method so u can push the ROM into the phone storage from PC.
Sent from my VS987 using Tapatalk
zap456 said:
Thanks for the quick reply , I will download these files asap and flash the firmware , A question , does flashing the stock firmware fixes the partition problem , there are no /internal storage or /data partitions to be mounted .
Click to expand...
Click to collapse
To my knowledge, flashing using the QFIL method (and using correct stock firmware) almost completely wipes and repartitions the device to the new (stock firmware). (the correct flashing software is QFIL since your device's processor belongs to the Qualcomm famiy)
You will see pretty soon, if you get on with is, that a scatter file is required for completing the flashing process. If you take a look at the file with a text editor, you might get a better idea of how you device will be partitioned (most likely from scratch).
Look a little bit more around, just to get a better idea on how to use QFIL. There are options on the software to force format/ wipe if nothing else works, or there is also the option to either download or upgrade. You will see once you get the program running.
My concern is that you don't just rush to flash the firmware. Try to understand the process as much as you can, and then give it a go!
r&xp said:
To my knowledge, flashing using the QFIL method (and using correct stock firmware) almost completely wipes and repartitions the device to the new (stock firmware). (the correct flashing software is QFIL since your device's processor belongs to the Qualcomm famiy)
You will see pretty soon, if you get on with is, that a scatter file is required for completing the flashing process. If you take a look at the file with a text editor, you might get a better idea of how you device will be partitioned (most likely from scratch).
Look a little bit more around, just to get a better idea on how to use QFIL. There are options on the software to force format/ wipe if nothing else works, or there is also the option to either download or upgrade. You will see once you get the program running.
My concern is that you don't just rush to flash the firmware. Try to understand the process as much as you can, and then give it a go!
Click to expand...
Click to collapse
I Couldn't connect my phone to the flashing software on the Pc, i followed the guide , but the guide asks to enable usb debugging , which i can't as the phone is off . Nyways thanks for the help .
zap456 said:
I Couldn't connect my phone to the flashing software on the Pc, i followed the guide , but the guide asks to enable usb debugging , which i can't as the phone is off . Nyways thanks for the help .
Click to expand...
Click to collapse
I am not sure if you really need to have enabled usb debugging for this particular method to work. Perhaps more experienced members can chip in here??? Heeeelp!!!!
Still there are a couple of things you can try, provided that you have correctly installed the drivers to enable at least some communication between your phone and the computer.
1. Try just connecting the phone to computer (powered off) after having pressed the download button in QFIL.
2. Try holding the volume up button and connecting the phone to PC (powered off phone) after having pressed the download button in QFIL.
3. Try holding the volume down button and connecting the phone to PC (powered off phone) after having pressed the download button in QFIL.
For all of the above, it would really help if the battery was out of your device (if it is removable).
I really do hope that you will get a chance to revive your device... For the time being, I am out of ideas myself... I wish you the best!
Related
Hi all, well I think I have all but wrecked my 16gb shield tv. I unlocked bootloader, installed twrp and rooted, all was working fine. Then I decided to flash the full android rom that is on the forum . before doing so, i used twrp and made a backup. I installed the full android rom, although it seemed to work fine, i was not crazy about it and decided to go back to the original OS, so I booted up in twrp and went to the restore function, there were no backups to restore , I guess when I installed the system img for the full android it erased my backup somehow. anyway, I next went to nvidia website and downloaded the restore image for the 16gb shield tv, i booted in to bootloader and was following the instructions to restore the shield. all seems to go fine until I try to flash the system img, then I get the error "invalid sparse file format at unknown block 0000" it tries to continue but fails, afterwards the system will not boot at all, I can get back to twrp recovery an flash the full android rom just fine, but am not able to flash back the original os without that error. any suggestions would be greatly appreciated, as I am stuck at this point as what to attempt next. thanks. Here is a pic of the errors i am getting.
Use a windows pc or the last fastboot version from android sdk or a better otg cable.
Is just a connection problem or the extracted system.img was corrupted when extracted.
If you not solve download again the stock firmware and unzip with a decent tool. Is possoble that when you extracted the archive your stock system.img was corrupted.
I flashed my Shield a million times with no problem. Also the ridiculous stock firmware just to do some logcat.
Shield Console is solid as a rock, you can do anything.
Thanks for the reply zulu, I will re download the img and try again, although I'm concerned something is wrong with the partition, as I was able to flash the full android rom, but now can no longer flash it either. I will let you know the results as soon as I'm able to retry.
cdsn99 said:
Thanks for the reply zulu, I will re download the img and try again, although I'm concerned something is wrong with the partition, as I was able to flash the full android rom, but now can no longer flash it either. I will let you know the results as soon as I'm able to retry.
Click to expand...
Click to collapse
Don't worry all is ok. I'm here to help you step by step if necessary.
my friend had a problem like this with another device, another firmware. He used a MAC OS to extract the firmware, and the system.img was not extracted well.
What are you using ? MAC, Windows, Linux ? what is your fastboot version ? do you use an usb otg cable ? what is your precise procedure to go in the bootloader ?
i use an usb otg cable to use fastboot from my PC.
to go in bootloader, I connect the usb otg cable to Shield, that is already connected also to my PC usb port, after i insert the power cable to Shield, and after i press quickly the power button for 5 seconds.
From Windows, if i try to install with the normal micro usb cable (exspecially the one that come with Shield), i have problems similar to your problem.
you can try also to install only the stock system.img to see what happen.
fastboot flash system system.img
fastboot -w (this clear user data, but is necessary when you switch from a firmware to another)
fastboot reboot
i installed the stock and the full Android many many times. If the Shield resist to me, can resist to all
zulu99 said:
Don't worry all is ok. I'm here to help you step by step if necessary.
my friend had a problem like this with another device, another firmware. He used a MAC OS to extract the firmware, and the system.img was not extracted well.
What are you using ? MAC, Windows, Linux ? what is your fastboot version ? do you use an usb otg cable ? what is your precise procedure to go in the bootloader ?
i use an usb otg cable to use fastboot from my PC.
to go in bootloader, I connect the usb otg cable to Shield, that is already connected also to my PC usb port, after i insert the power cable to Shield, and after i press quickly the power button for 5 seconds.
From Windows, if i try to install with the normal micro usb cable (exspecially the one that come with Shield), i have problems similar to your problem.
you can try also to install only the stock system.img to see what happen.
fastboot flash system system.img
fastboot -w (this clear user data, but is necessary when you switch from a firmware to another)
fastboot reboot
i installed the stock and the full Android many many times. If the Shield resist to me, can resist to all
Click to expand...
Click to collapse
Hi Zulu, thanks for the help, I don't have an otg cable, I just use the cable that came with the shield tv. Anyway, you were right, i re downloaded the image and all flashed well, who would have thought. wow, thanks so much for the info, hopefully I won't screw it up again. I like exploring new roms, but panic when I mess things up, I have been trying to re flash this thing for days, with all partitions flashing fine except for the system partition, anyway, downloading the new file must have fixed it , I also went into factory recovery and did a factory reset, maybe that had something to with it also, i really don't know. anyway, thanks again for your assistance.
cdsn99 said:
Hi Zulu, thanks for the help, I don't have an otg cable, I just use the cable that came with the shield tv. Anyway, you were right, i re downloaded the image and all flashed well, who would have thought. wow, thanks so much for the info, hopefully I won't screw it up again. I like exploring new roms, but panic when I mess things up, I have been trying to re flash this thing for days, with all partitions flashing fine except for the system partition, anyway, downloading the new file must have fixed it , I also went into factory recovery and did a factory reset, maybe that had something to with it also, i really don't know. anyway, thanks again for your assistance.
Click to expand...
Click to collapse
I'm at disposal. Thanks also to you to report back to me.
cdsn99 said:
Thanks for the reply zulu, I will re download the img and try again, although I'm concerned something is wrong with the partition, as I was able to flash the full android rom, but now can no longer flash it either. I will let you know the results as soon as I'm able to retry.
Click to expand...
Click to collapse
I had that issue before in a different device. The recovery had botched formatting the system partition. I tried to sideload the whole operating system, but in the end I just had to boot the recovery and format system again. It fixed my problem.
tooandrew said:
I had that issue before in a different device. The recovery had botched formatting the system partition. I tried to sideload the whole operating system, but in the end I just had to boot the recovery and format system again. It fixed my problem.
Click to expand...
Click to collapse
Yea I've experienced that too, I think the last time it happened it was on my Nexus 6. Try and execute this while in fastboot fastboot format system and then reflashing the system image.
I just rooted my phone lenovo k4 note using golden twrp and flashed resurrection remix with open gapps. Unfortunately the gapps zip file was corrupted and I wasn't able to fix that.
So I booted my phone to the new os , took the new feeling but later realised the gapps are mandatory.
So I downloaded a new file and tried to go to twrp recovery mode. But I wasn't able to. I thought the bootloader must've locked itself up so I unlocked it again, flashed the twrp recovery IMG file with adb and booted my phone to recovery. But still twrp didn't start.
BUT THEN I SAW THAT I HAD NO INTERNAL STORAGE
Just the SD card
Later I was able to wipe the custom rom from twrp and I flashed the resurrection remix and gapps.
Still internal storage was missing. Can anybody help me please?
ParagTheGre8 said:
Later I was able to wipe the custom rom from twrp and I flashed the resurrection remix and gapps.
Still internal storage was missing. Can anybody help me please?
Click to expand...
Click to collapse
Try flashing the stock ROM, see if your storage reappears on your stock ROM.
Also, do you get any information about your internal storage in Settings>Storage on your current ROM?
I don't know if it will help, but in TWRP recovery, go in Advanced>Fix permission
I feel like the OS doesn't have permission to internal storage, in the best case it will fix your issue in the worst case it will do nothing
But safest and easiest way to fix those kinds of issues is to wipe every thing and flash official ROM
Andrew_Geo said:
Try flashing the stock ROM, see if your storage reappears on your stock ROM.
Also, do you get any information about your internal storage in Settings>Storage on your current ROM?
Click to expand...
Click to collapse
Settings>Storage just shows the is size that's is roughly around 7gb
It says 7.11gb used of 7.15gb.
It should have been 16gb
I usually have around 10 GB free internal storage
DevALT said:
I don't know if it will help, but in TWRP recovery, go in Advanced>Fix permission
I feel like the OS doesn't have permission to internal storage, in the best case it will fix your issue in the worst case it will do nothing
But safest and easiest way to fix those kinds of issues is to wipe every thing and flash official ROM
Click to expand...
Click to collapse
So I tried to go to twrp, but the same problem occurred.
It seems my phone is unable to go to recovery.
I did the one with power button and volume keys, and it tries to go to recovery but the ROM boots up.
I also used the is function of reboot to recovery but by this too the ROM boots up and not twrp
ParagTheGre8 said:
So I tried to go to twrp, but the same problem occurred.
It seems my phone is unable to go to recovery.
I did the one with power button and volume keys, and it tries to go to recovery but the ROM boots up.
I also used the is function of reboot to recovery but by this too the ROM boots up and not twrp
Click to expand...
Click to collapse
Ok first of all makes sure ADB is enabled in your settings just in case something goes wrong you will be able to fix it without swearing
Once ADB connect your phone to your PC and use CMD/terminal command to reboot your phone in bootloader
Then reflash TWRP using the CMD/terminal
Once it's done reboot your phone and try to go to the recovery
EDIT: I made some search
And I need you to provide me some more information
RR ROM you flashed, I need the Android version (Lollypop/5.x or Marshmallow/6.x.x or Nougat/7.x.x)
And please provide me the link to the TWRP recovery you used (if you found the TWRP recovery not on XDA, DM me the link instead, follow the rules.)
I might need the phone model/or code if applicable
(Ex: I have a Huawei Nexus 6P but codename is angler) you can see this in the bootloader
EDIT 2: seems like your issue already been answered heads on this thread
https://forum.xda-developers.com/k4-note/how-to/fixed-missing-internal-storage-nougat-t3657798
DevALT said:
Ok first of all makes sure ADB is enabled in your settings just in case something goes wrong you will be able to fix it without swearing
Once ADB connect your phone to your PC and use CMD/terminal command to reboot your phone in bootloader
Then reflash TWRP using the CMD/terminal
Once it's done reboot your phone and try to go to the recovery
EDIT: I made some search
And I need you to provide me some more information
RR ROM you flashed, I need the Android version (Lollypop/5.x or Marshmallow/6.x.x or Nougat/7.x.x)
And please provide me the link to the TWRP recovery you used (if you found the TWRP recovery not on XDA, DM me the link instead, follow the rules.)
I might need the phone model/or code if applicable
(Ex: I have a Huawei Nexus 6P but codename is angler) you can see this in the bootloader
EDIT 2: seems like your issue already been answered heads on this thread
https://forum.xda-developers.com/k4-note/how-to/fixed-missing-internal-storage-nougat-t3657798
Click to expand...
Click to collapse
Thanks for the help but I found what was the concern (my problem is not fully solved)
The recovery was very stubborn to just start up.
So I used the official twrp app and flash booted through my phone.
Fortunately it worked.
I wiped everything including internal storage and the storage just showed up in my pc.
I flashed the ROM and Gapps again and the problem got solved.
There just one thing now, the internal storage is there when I go to Settings>Storage but cant access through File Explorer or pc.
The apps got downloaded to the internal storage only so its not much of a problem though.
I am having the same issue.
DevALT said:
Ok first of all makes sure ADB is enabled in your settings just in case something goes wrong you will be able to fix it without swearing
Once ADB connect your phone to your PC and use CMD/terminal command to reboot your phone in bootloader
Then reflash TWRP using the CMD/terminal
Once it's done reboot your phone and try to go to the recovery
EDIT: I made some search
And I need you to provide me some more information
RR ROM you flashed, I need the Android version (Lollypop/5.x or Marshmallow/6.x.x or Nougat/7.x.x)
And please provide me the link to the TWRP recovery you used (if you found the TWRP recovery not on XDA, DM me the link instead, follow the rules.)
I might need the phone model/or code if applicable
(Ex: I have a Huawei Nexus 6P but codename is angler) you can see this in the bootloader
EDIT 2: seems like your issue already been answered heads on this thread
https://forum.xda-developers.com/k4-note/how-to/fixed-missing-internal-storage-nougat-t3657798
Click to expand...
Click to collapse
I have a huawei Gr5 KII-L21 / kiwi mobile. Initially there was 16GB internal memory now it is just showing 2GB internal memory. I flashed stock rom yet the problem is there. I tried to flash stock rom in bootloader mode from window command prompt. Is there any method to get bak my internal memory?
This is basically a copy of my Z380M TWRP thread adopted for the ZenPad 10. I decided to start a new one since the OP of justshaun's original recovery/rooting thread has gone stale, even as I had posted several new releases of TWRP over the months. Its instructions are also a little outdated. I've also compiled a version for the new Z301M(F) models and needed a place to post it. This is where I will be posting TWRP updates from now on.
In addition to this thread, referring to the Z380M TWRP thread and the original Z300M thread (links above) may be helpful. These models share the same hardware and software base, so most things that apply to one tablet also apply to the others.
DISCLAIMER
As usual, you do anything described in this post at your own risk. No one but you is responsible for any data loss, bricking or damage of your device.
REQUIREMENTS
Windows or Linux PC
SP Flash Tool version 5.1532 (only this version will bypass security checks)
MediaTek VCOM drivers (available through Windows Update)
ZenPad 10 scatter file for SPFT, attached (choose the one for your tablet)
Recovery image, attached (choose the one for your tablet)
ZenPad Z300M, Z301M or Z301MF tablet upgraded to Android N
This won't be a guide on how to use SP Flash Tool. There are plenty of good guides out there like this one on how to set up drivers, load scatter files, flash and make backups with SP Flash Tool. If you're not familiar with this software or how to flash MediaTek devices in general, please do your research before attempting this. I will just get straight to the specifics about the ZenPad 10.
FIRST TIME INSTALLATION
For a locked bootloader:
At this point you should have your tablet powered off, the drivers installed, all of your data backed up, and SP Flash Tool v5.1532's Download tab open and loaded with the tablet's scatter file. Open the download agent file DA_PL.bin, replacing the default MTK_AllInOne_DA.bin. (You can use the AllInOne DA if you want, but the procedure involves extra steps as described below.) Load the extracted TWRP recovery image for your device (twrp-3.2.1-0-z30*m.img) under the recovery partition line in the partition table. Click the Download button inside SPFT. Now just connect the USB cable to your tablet and your computer's USB port. It should start the download process automatically and disconnect when finished.
Alternative Method:
If you're using MTK_AllInOne_DA.bin, you have to hold the Volume Up key as you insert the cable, which puts the device into an emergency download mode. In addition, you will need to have the stock preloader*.bin file loaded inside SPFT for it to be able to communicate with your tablet. The preloader is available inside the official zip file download. Do not flash the preloader (untick the box) or any partitions other than recovery. You just need to have a valid bin file selected under the Preloader line.
For an unlocked bootloader:
If you have used the Asus unlock tool to unlock your device, you will still not be able to use fastboot flash to install a custom recovery. However, you can do a "hot boot" or a tethered boot of TWRP. This method doesn't require SP Flash Tool. Download the TWRP image, put your tablet in fastboot mode and connect to PC. Then run this command to boot TWRP dynamically:
fastboot boot twrp-3.2.1-0-z30*m.img
Once inside TWRP, flash twrp-3.2.1-0-z30*m.img to Recovery using Install -> Install Image. Then reboot to recovery. You may be able to use TWRP in the tethered boot mode, but that could result in glitches due to different parameters passed by the bootloader to the kernel. That's why flashing is recommended.
To update from your installed TWRP version to a new one, just transfer the image to your tablet, then boot to TWRP and install it by going to Install -> Install Image and flashing to Recovery.
START RECOVERY
With the tablet powered off, hold the Volume Up and Power keys together until you get to a menu where you can select "recovery". On the Z301M/Z301MF, that option is labeled Factory Reset. Use Vol. Up to scroll and Vol. Dn to select. If you have a locked bootloader, it will show a Yellow State message because the recovery is not signed by the OEM. Just press volume up to boot it. On the welcome screen of TWRP it will ask you about modifying the system partition, I suggest you go with Keep System Read-only. Doing otherwise will complicate your OTA updates.
WARNING: Never start the stock recovery from the bootloader menu on this device. It is programmed by the bootloader to instantly wipe your data without any warning. Also, be aware that Android installs the stock recovery at every normal boot cycle. So you either have to flash the TWRP every time you want to run it, or disable the automatic recovery installation in the stock firmware. Any kind of mod to the boot image will prevent the automatic recovery installation. If you're not sure which recovery you have installed, you can always do a 'adb reboot recovery' from Android without risk of data loss.
WARNING 2: Make sure you use the correct scatter file for your device (i.e. don't mix up the Z300 and Z301 files). For the initial flash, there is no check for scatter file correctness. If you use the wrong one, SP Flash Tool will alter and lock your GPT to that scatter file layout, possibly bricking your device. It will not be easy to restore it. Flashing with the correct scatter file later on will not work because Flash Tool will not allow you to use a different file than the one you used initially.
What works: Basically everything... access to major partitions, decrypted userdata partition, decrypted adoptable storage, external SD card, ADB, USB-OTG, touch interface, splash screen, installing stock Asus OTA/web FW updates
What doesn't work: (no known problems yet, but please report any)
Not guaranteed to work: factory reset
DOWNLOAD
SP Flash Tool v5.1532
Z300M Scatter file for all storage sizes (right click, Save link as...) -- do not use for other models
Z300M TWRP 3.2.1-0 image -- updated March 15, 2018
Z301M(F) series Scatter file for all storage sizes (right click, Save link as...) -- do not use for Z300M or other devices
Z301M TWRP 3.2.1-0 image -- updated March 13, 2018
Z301MF TWRP 3.2.3-0 image -- updated August 29, 2018
Development and experimental files
Source code
P.S. The thanks button doesn't bite.
Heya, thanks for the new thread..
Stupid question(coming from Samsung flashing)
Ive got Zenpad S3 10 P027, is this TRWP not ideal for this?
Currently, have some su (root) issues. Recovery shows Android icon chest with ! and says "No Command"
When running su in Terminal ADB via PC, says command not recognized.
Looks like I need to reflash recovery. When in TRWP (launched via fastboot boot twrp on PC) I flashed stock recovery but had system mounted read only. Could that be the problem?
Bro, I think you need to do some more homework on root, su, dm-verity, mods, etc. and read the instructions more carefully before applying these hacks. You are making a lot of simple mistakes and ending up shooting yourself in the foot for it. I don't think there's anything wrong with the Z500 TWRP. It can handle installing the stock firmware just fine. The problem is elsewhere. The unlock tool also works fine in TWRP as well in my testing.
The No Command screen is normal. That's been answered many times... you need to hold power+vol. up (or down) to get to the menu. There is no way the stock recovery image can be broken and still boot up.
The su thing, IDK what the problem is, but I'm sure if you install Magisk Manager and make your own patched image from your currently installed firmware, and fastboot-boot with it, you will have su functionality. Just like what it says in the unlock tool instructions.
Lastly and most important, never mount system in read-write mode, as I've repeated several times and exactly as it says in the directions:
7. At the TWRP welcome screen, do not select to modify the system partition and touch Keep System Read-only instead. Doing otherwise will render your tablet unbootable.
8. Mount system in TWRP (in read-only mode)
Click to expand...
Click to collapse
The only time you can mount it in read-write mode is when you are absolutely sure you have disabled dm-verity in your boot image.
I've successfully installed TWRP on Z301M using the instructions from the first post, but then I somehow managed to lose the system. Yes, I should have backed up like the OP suggests.
I thought I should be able to reinstall the original firmware downloaded from Asus (e.g. UL-ASUS_P028_1-WW-3.3.12.0-user.zip) but both the 'adb sideload' method and the TWRP failed to install that firmware zip. My device looks bricked. The only thing I can do is to boot into TWRP (I actually need to select Factory Reset on the bootloader screen to get into TWRP). The folder 'system' is empty.
Can anyone suggest what I am doing wrong when trying to restore the Asus firmware?
When I try to sideload the zip, setting TWRP in the sideload mode, the computer begins uploading but after a few seconds gives the message "Total xfer: 0.01x" and stops, while Android errors with "set boot part fail. can not open misc-sd".
When I install the firmware zip from TWRP it also starts installing fine but shortly gives the same error "set boot part fail. can not open misc-sd".
Thanks
@ahacker, first of all, thank you for the feedback on the Z301M platform. You are literally the first person to have said anything about that version of TWRP.
To see the files on system, you first have to mount the system partition. Did you do that? If not, I suggest mounting it read-only. If there was any corruption on it, then reinstalling the firmware should have fixed it. The "misc-sd" errors are normal. Pretty sure they happen on stock recovery too. The stock firmware does not have dm-verity enabled, so letting TWRP modify system to prevent overwriting recovery should not have caused any problems.
At which point did it stop booting? Also, did you use the scatter file from first post? And can you tell me if the touch screen works fine in TWRP on your tablet?
I'm not sure what the deal is with adb sideload. I don't think I've ever actually tried it....
diplomatic, thanks for replying!
diplomatic said:
[MENTION=4776997]
To see the files on system, you first have to mount the system partition. Did you do that?
Click to expand...
Click to collapse
I do mount the system partition. It appears empty. When I reboot into system TWRP says that the OS is not installed.
I don't remember the details of how I lost the system partition. First time I entered into TWRP it asked for a password, probably to mount some partition. I pressed cancel or something. Then I might have cleaned the caches. But I am sure I haven't wiped system. I might have pressed Factory Reset somewhere, because I don't have any data yet on the new tablet.
I would indeed try to mount the system read only. This is not the first Android system I rooted (maybe fifth), and I was always able to restore the system either from sideload or recovery. But here it seems Asus is making us jump extra hoops to do that.
diplomatic said:
[MENTION=4776997]
Reinstalling the firmware should have fixed it.
Click to expand...
Click to collapse
That seems to be my main problem now. I cannot reinstall the Asus firmware. It may look like I might be installing a wrong version, but I am positive that I have Z301M tablet. This is what I bought and what the boot-loader says. I download Z301M firmware from the Asus website (e.g.). So it must be a correct firmware.
diplomatic said:
[MENTION=4776997]
The "misc-sd" errors are normal. Pretty sure they happen on stock recovery too. The stock firmware does not have dm-verity enabled, so letting TWRP modify system to prevent overwriting recovery should not have caused any problems.
Click to expand...
Click to collapse
Thank you for the information.
diplomatic said:
[MENTION=4776997]
Also, did you use the scatter file from first post? Does the touch screen work fine in TWRP on that tablet?
Click to expand...
Click to collapse
Yes. I found that to be the only scatter file that worked. I tried scatter.txt from the firmware zip, but the Flash Tool refuses tio pick it up. TWRP seems to be working fine with touches working as expected.
diplomatic said:
[MENTION=4776997]
I'm not sure what the deal is with adb sideload. I don't think I've ever actually tried it....
Click to expand...
Click to collapse
This is the unbricking method described here. It probably does the same thing as the "Install Zip" from recovery, because the errors that both methods give are the same.
---------- Post added at 01:19 AM ---------- Previous post was at 12:57 AM ----------
Now system refuses to mount
ahacker said:
I don't remember the details of how I lost the system partition. First time I entered into TWRP it asked for a password, probably to mount some partition. I pressed cancel or something. Then I might have cleaned the caches. But I am sure I haven't wiped system. I might have pressed Factory Reset somewhere, because I don't have any data yet on the new tablet.
Click to expand...
Click to collapse
Er, the password should have been for decrypting your userdata. If you didn't have one set up, there might be something wrong there.... Or possibly just unformatted.
ahacker said:
That seems to be my main problem now. I cannot reinstall the Asus firmware. It may look like I might be installing a wrong version, but I am positive that I have Z301M tablet. This is what I bought and what the boot-loader says. I download Z301M firmware from the Asus website (e.g.). So it must be a correct firmware.
Click to expand...
Click to collapse
Yeah, that has to be the right one. The installation script has to match the model name reported by the recovery. Otherwise it would simply abort.
ahacker said:
Yes. I found that to be the only scatter file that worked. I tried scatter.txt from the firmware zip, but the Flash Tool refuses tio pick it up. TWRP seems to be working fine with touches working as expected.
Click to expand...
Click to collapse
Great! Guess my kernel patch was on the dot and the partition layout has not changed from the Z300.
ahacker said:
This is the unbricking method described here. It probably does the same thing as the "Install Zip" from recovery, because the errors that both methods give are the same.
Click to expand...
Click to collapse
When you installed the zip, did you unmount system completely? BTW, when you mentioned the errors, the installation does keep going for like 5 to 10 minutes afterwards, right?
If you still can't resurrect it, please post or send me the recovery & kernel log that has your installation attempt.
diplomatic said:
When you installed the zip, did you unmount system completely? BTW, when you mentioned the errors, the installation does keep going for like 5 to 10 minutes afterwards, right?
Click to expand...
Click to collapse
I've tried both ways, with and without system mounted, a few times. The installation would fail after something like 5 seconds.
diplomatic said:
If you still can't resurrect it, please post or send me the recovery & kernel log that has your installation attempt.
Click to expand...
Click to collapse
I think I am giving up on this cheap tablet. I cannot even format it in the Flash Tool: it says "To format code area is forbidden on this phone". Asus is forbidding too much for me to ever buy it again. Attached the logs.
Thanks, diplomatic
OK, found the problem. Check your PMs, ahacker.
diplomatic said:
OK, found the problem. Check your PMs, ahacker.
Click to expand...
Click to collapse
I have replied (twice), but the reply does not appear in my Sent Items. I hope it has reached you. If not, I'll paste the reply here, if you don't mind.
i not understand... i have Asus ZenPad 10 LTE Z301MFL.. a root method has been released ???
@diplomatic
Would this be compatible with Z0310M ? can't find anything for this damn model...
Hi, NeBouse,
Are you sure you have the correct information? It looks like just a misspelling of Z301M, aka P028....
I have z301m.
One thing that was a surprise for me is that the TWRP recovery flashed with the method described in the original post does not stick. You have to flash it each time you use it. If you are like me this information is important, because the original recovery plainly wipes your data without asking or warning.
After you have flashed TWRP on the device, to go to the recovery mode you have to chose "Factory Reset" in the bootloader. Then it will complain about wrong OS, which is the sign that flashing TWRP worked; choose 'yes'. The first thing you should do in TWRP is a ful nandroid backup. (Not listening the OP's advice about backing up when Installing TWRP with a wrong scatter file almost cost me the device. Thankfully diplomatic managed to remotely fix my problem, probably spending a lot of his personal time. The scatter file in the original post is a correct one now.)
Creating a nandroid backup in TWRP takes unusually long time, I even once decided that it hanged. Taking long time, like 10-30 minutes, for a full backup is normal.
Asus Z300M , Magisk 16.3 (beta) and FW 5.3.19 WW now works!
z301m, WW-3.3.12.0 firmware
For rooting I've installed in TWRP Magisk v15.3 (diplomatic warned against 16.x, someone else against 15.4) - link.
Installed in TWRP xPosed framework 88.2 - link, and xPosed Installer apk from within Android - link.
So far, so good.
What I've found is that TWRP seems to have problems with external sd cards (lots of fs corruption). I found it safer to unmount by hand by unticking the sd card checkbox in "Mount". Not very conclusive about this though.
Thanks, ahacker. Good feedback. Although to be fair, I didn't say to avoid Magisk 16.x. I said 16.0. I'm pretty sure whatever bug it had is already fixed in the latest version.
Now that you've installed root, TWRP will stick around on the emmc. The stock recovery only gets installed if you have the original unpatched boot image on it. I mean, this is not unique to these devices. That's been standard Android functionality since some 4.x or 5.x version. And this is essentially what's in the warning on the OP.
The backup I'm talking about in the installation method is done with the SP Flash Tool readback function. That will pull the partition tables and your device's "metadata" that's unique to your unit. I don't think nandroid covers that...
Oh, and what is this SD corruption you're talking about? What file system is it formatted in? Have you checked your card for errors in Windows?
Asus releases so many difference Z301M model, so I am curious if this also works on Z301MF model?
Notice Z300MF has the MTK8163BA (or MTK8163A?) CPU model while Z301M uses : 8163B
Anyone tested that already? Thanks.
my zenpad 10 has frp lock. it this a solution to remove the frp lock?
Pls help how i flash original software via fastboot ?????
Hello everyone, after a long attempt at unlocking the bootloader i finally got it, i flashed TWRP and got a prompt for encryption password, and my password wasn't working and i also tried default_password,so i read that the format data option will decrypt the phone and people said wouldn't do anything to system, so i did it and now everytime i reboot it boots straight into recovery no matter what i try, it will also boot into fastboot, so i tried to find a stock ROM for TA-1056 but couldn't find it anywhere, the only the i found was a single ROM for the TA-1060, can anyone help? i really appreciate it!
Completely Bricked
Me too need a stock rom of ta 1056. Please help if you could manage to provide a helping hand... ?
I had the same issue like yours, looping in twrp. then i tried to flash it with a so called stock rom from net, guess what it went completely bricked and I donnow what to do. ??
mrabudi said:
Hello everyone, after a long attempt at unlocking the bootloader i finally got it, i flashed TWRP and got a prompt for encryption password, and my password wasn't working and i also tried default_password,so i read that the format data option will decrypt the phone and people said wouldn't do anything to system, so i did it and now everytime i reboot it boots straight into recovery no matter what i try, it will also boot into fastboot, so i tried to find a stock ROM for TA-1056 but couldn't find it anywhere, the only the i found was a single ROM for the TA-1060, can anyone help? i really appreciate it!
Click to expand...
Click to collapse
It's simple. just get the stock recovery (and boot, optional) to flash it with fastboot and go to recovery and wipe it and you'll be ok.
and also using the twrp on this phone is not a great idea to wipe.
if you wanna wipe. please use "fastboot -w" to wipe the phone while bootloader is unlocked. or stock recovery to wipe.
Because twrp built this recovery with only formatting option was ext4 to /data and /cache. So the phone cannot operate properly. Which leads to fake failed decryption notification.
Data partition must need to be formatted under f2fs format.
And finding rom for this phone is pretty easy. Just find some nb0 file for this phone (any variant of this phone should work) and extract it with "nb0 extractor" and then flash it with SP Flash tool by mediatek.
That's my way. I don't know how will you do. But normally you only need the nb0 file and then flash it with OST LA (Nokia's flash tool based off Intel's SUT L1/L3 tool).
My Nokia 1 TA-1047 stuck at Nokia logo screen
Hi guys, sorry I'm newbie so after a long time surfing for solutions, I couldn't solve my own problem. That's why I come here to ask for your supports
Firstly I unlocked bootloader, installed TWRP and rooted my device and enjoyed it. But after decided to wipe (factory reset) this phone with TWRP, and my problem began...
1. I got stuck in TWRP loop booting. After that I tried to fastboot system.bin, cache.bin and recovery.bin from Stock Firmware but it still hung at Nokia logo booting
2. I still kept trying with SP Flash Tool, Miracle Box but there was still no hope:
- SP Flashtool v5_1548 gave me error: BROM ERROR: S_BROM_CMD_STARTCMD_FAIL (2005)
- Miracle Box 2.27A told me there was an error (i don't remember the code) occured in the location (i can't remember its code either)...
Anyone can solve it please help!!!! I love this phone much and as of now still suffering day by day since I can't do anything with it.
Kindly appreciate any suggestion and solution.
Thank you all!
cuantonhonhoi said:
Hi guys, sorry I'm newbie so after a long time surfing for solutions, I couldn't solve my own problem. That's why I come here to ask for your supports
Firstly I unlocked bootloader, installed TWRP and rooted my device and enjoyed it. But after decided to wipe (factory reset) this phone with TWRP, and my problem began...
1. I got stuck in TWRP loop booting. After that I tried to fastboot system.bin, cache.bin and recovery.bin from Stock Firmware but it still hung at Nokia logo booting
2. I still kept trying with SP Flash Tool, Miracle Box but there was still no hope:
- SP Flashtool v5_1548 gave me error: BROM ERROR: S_BROM_CMD_STARTCMD_FAIL (2005)
- Miracle Box 2.27A told me there was an error (i don't remember the code) occured in the location (i can't remember its code either)...
Anyone can solve it please help!!!! I love this phone much and as of now still suffering day by day since I can't do anything with it.
Kindly appreciate any suggestion and solution.
Thank you all!
Click to expand...
Click to collapse
So here's the thing. The rom you downloaded from internet (about 2 GB) or ripped from your phone and reflashing from flash tool will NOT WORK.
The first reason you can't flash the ROM was:
You got into flashing mode but you didn't do the right way so it failed the downloading DA for the phone. Try again and it should work (Don't go into fastboot mode)
2nd reason:
Because of the unsupported chip that MiracleBox read. It said the phone was 6573 or something while the phone chip is 6737M.
So the app will create the wrong version of the scatter for the phone. Leads to the flash tool app downloading the wrong command and Download Agent for the phone makes the phone can't be flashed.
You need to get the official nb0 file for this phone (TA-1060 or 66 should also works, mine was TA-1047. Since it's a universal ROM so any variant of the phone can also work) and then extract the ROM. Then you can get the scatter text file from that nb0 ROM and then flash it over flash tool (version 5 recommended, version 3 more likely not work).
Remember to look at line with partition "metadata" and then edit "boundary_check" to false.
PLUS:
If you flash it with your own dumped EMMC rom or flash it by dd-ing the partition in recovery will kinda work. But when you update the ROM over OTA (Google Play services's System Update app)
It will most likely bootlooped the phone when it's trying to verify the 2nd partition of the same recovery or kernel flashed into the phone (https://source.android.com/security/verifiedboot) and flash the updated one.)
So flashing from official ROM is mandatory.
And you can flash it over Intel's (Nokia modified) flash tool app SUTL3 (aka. OST LA) but I can't get it to work so you just stick with Flash Tool v5 from MediaTek and you'll be good.
Link:
The nb0 ROM (Security update around May 2018): https://drive.google.com/file/d/1XqwEAGG7GMaspzV2J_yzCxnRei8zsOJd/view
(Source: https://romprovider.com/2018/09/nokia-1-ta-1060-firmware/)
nb0 extractor, requires java installed (If extracting hurts your hard disk performance aka. frozen or lag. Don't worry, It actually works, DON'T DO ANYTHING. It will notify you once it's done.): https://forum.xda-developers.com/general/general/tool-unpack-repack-nb0-rom-t3495091
Smart Phone Flash Tool from MediaTek: https://spflashtools.com/
My fixed scatter file that actually works from nb0 file: https://drive.google.com/open?id=1gRoADGHBm4vIAw3NeDyc_h9QWj12XUrC
And don't use twrp for wiping the phone. Use "fastboot -w" to wipe or use stock recovery.
TWRP will wipe the data parition but in ext4 format and make the phone bootlooped. We need f2fs in order to make the phone's /data partition run correctly. (Unless you know how to make the phone not having encryption flag when booting up every first time. Or modify TWRP to wipe the /data partition with make_f2fs and not make_ext4 app. Or using make_f2fs in recovery to directly wipe /data partition over terminal, the actual partition is in /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/userdata.)
Or you just do this (I'm not tested it yet): Google "twrp f2fs format"
kutiz21 said:
So here's the thing. The rom you downloaded from internet (about 2 GB) or ripped from your phone and reflashing from flash tool will NOT WORK.
The first reason you can't flash the ROM was:
You got into flashing mode but you didn't do the right way so it failed the downloading DA for the phone. Try again and it should work (Don't go into fastboot mode)
2nd reason:
Because of the unsupported chip that MiracleBox read. It said the phone was 6573 or something while the phone chip is 6737M.
So the app will create the wrong version of the scatter for the phone. Leads to the flash tool app downloading the wrong command and Download Agent for the phone makes the phone can't be flashed.
You need to get the official nb0 file for this phone (TA-1060 or 66 should also works, mine was TA-1047) and then extract the ROM. Then you can get the scatter text file from that nb0 ROM and then flash it over flash tool (version 5 recommended, version 3 more likely not work).
Remember to hide/delete line with partition "metadata" in scatter.txt and you can flash it perfectly.
PLUS:
If you flash it with your own dumped EMMC rom or flash it by dd-ing the partition in recovery will kinda work. But when you update the ROM over OTA (Google Play services's System Update app)
It will most likely bootlooped the phone when it's trying to verify the 2nd partition of the same recovery or kernel flashed into the phone (https://source.android.com/security/verifiedboot) and flash the updated one.)
So flashing from official ROM is mandatory.
And you can flash it over Intel's (Nokia modified) flash tool app SUTL3 (aka. OST LA) but I can't get it to work so you just stick with Flash Tool v5 from MediaTek and you'll be good.
Link:
The nb0 ROM (Security update around May 2018): https://drive.google.com/file/d/1XqwEAGG7GMaspzV2J_yzCxnRei8zsOJd/view
(Source: https://romprovider.com/2018/09/nokia-1-ta-1060-firmware/)
nb0 extractor, requires java installed (If extracting hurts your hard disk performance aka. frozen or lag. Don't worry, It actually works, DON'T DO ANYTHING. It will notify you once it's done.): https://forum.xda-developers.com/general/general/tool-unpack-repack-nb0-rom-t3495091
Smart Phone Flash Tool from MediaTek: https://spflashtools.com/
My fixed scatter file that actually works from nb0 file: https://drive.google.com/open?id=1gRoADGHBm4vIAw3NeDyc_h9QWj12XUrC
And don't use twrp for wiping the phone. Use "fastboot -w" to wipe or use stock recovery.
TWRP will wipe the data parition but in ext4 format and make the phone bootlooped. We need f2fs in order to make the phone's /data partition run correctly. (Unless you know how to make the phone not having encryption flag when booting up every first time. Or modify TWRP to wipe the /data partition with make_f2fs and not make_ext4 app. Or using make_f2fs in recovery to directly wipe /data partition over terminal, the actual partition is in /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/userdata.)
Or you just do this (I'm not tested it yet): Google "twrp f2fs format"
Click to expand...
Click to collapse
Thanks for your comment. I have recently bought that version (TA-1047) and I see that is more complicated to root it securely than I thought… Your comment gave me hope to try it. So, could you please say me if it is posible to do it without breaking it? I will read your comment when I have more time but I thank you for it!
As I see there is only stock rom for TA-1060 version, but as you say it is posible to recover it in case of breaking it, isn't it?
Thanks. :fingers-crossed:
pabloluih said:
Thanks for your comment. I have recently bought that version (TA-1047) and I see that is more complicated to root it securely than I thought… Your comment gave me hope to try it. So, could you please say me if it is posible to do it without breaking it? I will read your comment when I have more time but I thank you for it!
As I see there is only stock rom for TA-1060 version, but as you say it is posible to recover it in case of breaking it, isn't it?
Thanks. :fingers-crossed:
Click to expand...
Click to collapse
It's really easy to root the phone actually. Just unlock bootloader, install twrp recovery and install magisk.
And if you broke the phone's ROM. Just bring it to Nokia. Or flash it by yourself with the ROM I linked above by SP Flash Tool software.
Anyway the ROM is universal. So any variant of the phone can be flashed. (Proves that the elabel partition has 5 certifications images for 5 different models)
Just take sometime and read my words there.
kutiz21 said:
It's really easy to root the phone actually. Just unlock bootloader, install twrp recovery and install magisk.
And if you broke the phone's ROM. Just bring it to Nokia. Or flash it by yourself with the ROM I linked above by SP Flash Tool software.
Anyway the ROM is universal. So any variant of the phone can be flashed. (Proves that the elabel partition has 5 certifications images for 5 different models)
Just take sometime and read my words there.
Click to expand...
Click to collapse
Many thanks! At the moment I achieved to root it with twrp. OEM unlock > installed twrp > fastboot -w > magisk.
At the moment all is okey but I have not been able to unencrypt DATA partition (I have done fastboot -w, but with no success, I have not tried TWRP format because of your advice). That's the only point I can complain about.
I hope I do not have to use the stock rom to unbrick, but I have your advice if I do.
Thanks again!
pabloluih said:
Many thanks! At the moment I achieved to root it with twrp. OEM unlock > installed twrp > fastboot -w > magisk.
At the moment all is okey but I have not been able to unencrypt DATA partition (I have done fastboot -w, but with no success, I have not tried TWRP format because of your advice). That's the only point I can complain about.
I hope I do not have to use the stock rom to unbrick, but I have your advice if I do.
Thanks again!
Click to expand...
Click to collapse
That's weird. If you unlocked the bootloader and install adb/fastboot (must be latest version. Older version will not recognize the phone, download platform-tools from google dev site, don't download adb tools off XDA) + Nokia's driver from emulated CD drive (every time you plug the phone to computer with official rom, you'll see it) properly then it should be able to work.
You need to check the fastboot device driver Device Manager (devmgmt.msc) and see if the driver is properly installed yet.
You can only use "fastboot -w" once the bootloader is unlocked. And booting up the phone. It will say the bootloader is in Orange state.
You need to unlock oem bootloader from developer settings when the stock rom is there. And in fastboot too
Here is how you unlock it:
Enable oem unlock from dev settings
Then reboot to fastboot mode (bootloader)
Do this:
"fastboot oem key "serial number string converted to md5, not imei strings" "
"fastboot oem unlock"
Volume up
Then you are actually unlocked the bootloader.
Unlock from developer settings only will not do the trick. It only allows you to have ability unlock the bootloader in fastboot.
If you stuck on the Encryption unsuccessful screen. Try wipe it with stock recovery or "fastboot -w" (if you properly unlocked the bootloader)
If you think you can't do anything anymore. Just flash the ROM provided you above.
If you need the extracted ROM for SP flash tool and the fastboot driver. I can link it to you.
Most of all drivers will automatically install off Windows Update if you're on Windows 10 (except the fastboot driver, and yes. SP flash tool drivers are also provided by Windows 10 too)
Also. You should update the phone to the latest software update when flashing stock rom too. Because newer builds for this phone is compatible-friendly with GSI rom (Treble ROMs like AOSP Android 9 or 8.1 by phhusson)
Updates on Android 9/10
pabloluih said:
Many thanks! At the moment I achieved to root it with twrp. OEM unlock > installed twrp > fastboot -w > magisk.
At the moment all is okey but I have not been able to unencrypt DATA partition (I have done fastboot -w, but with no success, I have not tried TWRP format because of your advice). That's the only point I can complain about.
I hope I do not have to use the stock rom to unbrick, but I have your advice if I do.
Thanks again!
Click to expand...
Click to collapse
Nokia might harden the security of the device so you can't use Magisk on stock rom.
NOTE: Will just clarify, probably am an idiot and messed up a simple thing, so please do take everything I say here with a grain of salt.
The phone was rooted with Magisk v25.1, and I had also installed the unofficial TWRP from this very forum. I also believe I was on 11.0.4.0 of OxygenOS. It is the factory unlocked version.
I was following a guide to update the phone through fastboot, since stock recovery was just showing a screen with a keyboard, which appeared to be impossible to get past. Said guide is here.
Linked in the guide above is the 8th step of that guide, where you then flash the files from the OTA file after extracting them with payload_dumper. I believe the version I was extracting was 11.0.7.0, but to be honest, it was whatever I downloaded off of the Oxygen Updater app, so I'm not entirely certain. I had installed "boot.img", "dtbo.img", and "modem.img", then getting to "abl.img", before receiving an error: Flashing is not allowed for Critical Partitions. "Well," I thought, "I suppose I just can't do it then. *shrug*. Back to this version of OxygenOS I go." That was before remembering to attempt doing "fastboot flashing unlock_critical", which, gave me: Device already unlocked! Well, clearly not, as I should've been able to write abl.img. Attempting to flash again gave me nothing, so, I said screw it.
Well, upon trying to hit start in fastboot, I noticed the phone were now bootlooping back to fastboot over and over. So, I'm lead to a few conclusions:
a) I'm gonna need "dtbo.img" and "modem.img" (I already have boot.img) from the 11.0.4.0 stock image. I cannot find the actual image, so I'm lead to now needing some help here.
b) There has to be some way to continue flashing the files in fastboot (that is, if that is the correct course of action; I am assuming, please feel free to correct me).
c) There is a different way to fixing this than I am thinking.
d) Worst case scenario, this thing has to go back to OnePlus.
Would really hate to have to get to Step D, as this phone was a birthday present to me, and I'd find it wholly embarrassing to throw my hands up in the air a single day after getting the damn thing for my birthday just to need to send it back already, but if nobody can help me out here, then that's where I'm at.
Would appreciate any and all help/suggestions! Thanks.
EDIT: Phone is stuck in Qualcomm Crashdump mode now, bootable into fastboot with vol up+down+power. Looks like it's irreparable. Already working with OnePlus to get it replaced.
EDIT 2: Fixed it!! Big thanks to this thread for the help.
1)get a usb otg and pendrive
2)download and tranfer pixel experience full build zip file in you pendrive
3)go to fastboot and flash twrp recovery misc and vbmeta and boot to recovery
4)insert pendrive in usb otg and connect it to phone
5)click on install then click on select storage usb otg and flash the pixel experience like you flash other files
6)reboot the phone
7)after setting up download the rom you want to and go to fastboot then flash twrp again 3rd step
8)flash the rom you want to install and flash g-apps reboot your phone
9)complete all steps and you have your phone with custom os/rom
Raghaov said:
1)get a usb otg and pendrive
2)download and tranfer pixel experience full build zip file in you pendrive
3)go to fastboot and flash twrp recovery misc and vbmeta and boot to recovery
4)insert pendrive in usb otg and connect it to phone
5)click on install then click on select storage usb otg and flash the pixel experience like you flash other files
6)reboot the phone
7)after setting up download the rom you want to and go to fastboot then flash twrp again 3rd step
8)flash the rom you want to install and flash g-apps reboot your phone
9)complete all steps and you have your phone with custom os/rom
Click to expand...
Click to collapse
No offense, but this is a pretty dumb response. I don't think you're very familiar with how TWRP is on this device, nor the state of my own. I cannot mount storage, and even if I could, I don't even believe this rom exists for the N200 5G. Along with that, why would a USB OTG be necessary when there's.. I don't know, an SD card slot that works fine and is readable?
Also step 3 is a little laughable. That's why I'm even here in the first place; I couldn't flash every damn thing!
I'll share Oxygen OS 12 if you want it, and let me know if I should keep searching.
Just use payload dumper go to dump the payload and then flash the files with this guide.
Edit: Uploading it via xda didn't work, so here's the google drive link.
justauserthatusesaphone said:
I'll share Oxygen OS 12 if you want it, and let me know if I should keep searching.
Just use payload dumper go to dump the payload and then flash the files with this guide.
Edit: Uploading it via xda didn't work, so here's the google drive link.
Click to expand...
Click to collapse
Do you have one for metro T-MO variant?
Tyreethetruth said:
Do you have one for metro T-MO variant?
Click to expand...
Click to collapse
Nope, I also don't know how to get it, unfortunately.
sounds to me like you dont want a real answer i mean at least respect the one person that replied to your post, not our fault you got yourself in this situation.